FORM 2
THE PATENTS ACT, 1970 (39 OF 1970) & THE PATENT RULES, 2003
COMPLETE SPECIFICATION
(See section 10 and rule 13)
“METHOD AND SYSTEM FOR CREATING BACKUP OF A NETWORK FUNCTION”
We, Jio Platforms Limited, an Indian National, of Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India.
The following specification particularly describes the invention and the manner in which it is to be performed.

METHOD AND SYSTEM FOR CREATING BACKUP OF A NETWORK
FUNCTION
CROSS-REFERENCE
[0001] The present disclosure takes priority from Indian Patent Application No. 202321060700 filed on 9th September 2023, and Indian Patent Application No. 202321060699 filed on 9th September 2023.
FIELD OF THE DISCLOSURE
[0002] Embodiments of the present disclosure generally relate to a field of wireless communication. More particularly, the present disclosure relates to a method and a system for creating backup of a network function.
BACKGROUND
[0003] The following description of the related art is intended to provide background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section is used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of the prior art.
[0004] Wireless communication technology has rapidly evolved over the past few decades, with each generation bringing significant improvements and advancements. The first generation of wireless communication technology was based on analog technology and offered only voice services. However, with the advent of the second generation (2G) technology, digital communication and data services became possible, and text messaging was introduced. The third generation (3G) technology marked the introduction of high-speed internet access, mobile

video calling, and location-based services. The fourth generation (4G) technology revolutionized wireless communication with faster data speeds, better network coverage, and improved security. Currently, the fifth generation (5G) technology is being deployed, promising even faster data speeds, low latency, and the ability to connect multiple devices simultaneously. With each generation, wireless communication technology has become more advanced, sophisticated, and capable of delivering more services to its users.
[0005] The 5G core networks are based on service‐based architecture (SBA) that is centred around network function (NF) services. In the said Service‐Based Architecture (SBA), a set of interconnected Network Functions (NFs) deliver the control plane functionality and common data repositories of the 5G network, where each NF is authorized to access services of other NFs. Particularly, each NF can register itself and its supported services to a Network Repository Function (NRF), which is used by other NFs for the discovery of NF instances and their services. Further, the network functions may include, but not limited to, a cloud-native network function (CNF) and a virtual network function (VNF).
[0006] The CNFs are a set of small, independent, and loosely coupled services such as microservices. These microservices work independently, which may increase speed and flexibility while reducing deployment risk. In 5G communication, cloud-native 5G network offers the fully digitized architecture necessary for deploying new cloud services and taking full advantage of cloud-native 5G features such as edge computing, as well as network slicing and other services. Whereas the VNFs may run in virtual machines (VMs) on common virtualization infrastructure. The VNFs may be created on top of network function virtualization infrastructure (NFVI) which may allocate resources like compute, storage, and networking efficiently among the VNFs. MANO which stands for Management and Orchestration is a key NFV architectural framework that includes all the essential management modules. It coordinates network resources in NFV framework. Further, due to such vast usage and implementation of the CNFs and the VNFs,

there is a need of maintaining such microservices and applications data in a secure way, which may not be lost and may be retained safely from any unwanted incidents such as network service crash, outage, cyber-attacks and any other undesirable incidents.
[0007] Currently, the backup of the CNF and the VNF applications and services are taken by manual procedure, which may take significant amount of time and may also result in some errors. Further, since the CNFs and the VNFs applications or services may be operational on many servers and other supported devices, therefore for taking backups of such CNF applications, user has to backup specific CNF applications separately, which is also cumbersome and time-consuming task.
[0008] Hence, in view of these and other existing limitations, there arises an imperative need to provide an efficient solution to overcome the above-mentioned and other limitations and to provide a method and a system for creating backup of a network function.
SUMMARY
[0009] This section is provided to introduce certain aspects of the present disclosure in a simplified form that are further described below in the detailed description. This summary is not intended to identify the key features or the scope of the claimed subject matter.
[0010] An aspect of the present disclosure may relate to a method for creating backup of a network function. The method comprises creating, by a processing unit, a profile for the network function. The method further comprises sending, by a transceiver unit, a backup creation request of the profile for the network function to a backup module. Further, the method comprises transmitting, by the transceiver unit, the backup creation request from the backup module to a service module. Further, the method comprises creating, by the processing unit, via the service

module, a backup of the profile for the network function. Furthermore, the method comprises transmitting, by the transceiver unit via the service module, to the backup module, details related to the created backup. Thereafter, the method comprises storing, by a storage unit via the backup module, in a database, the created backup of the profile for the network function.
[0011] In an exemplary aspect of the present disclosure, the network function is at least one of a cloud-native network function (CNF) and a virtual network function (VNF).
[0012] In an exemplary aspect of the present disclosure, the service module is a Docker Service Adapter (DSA) microservice if the network function is the CNF.
[0013] In an exemplary aspect of the present disclosure, the service module is an Open Stack Adapter (OSA) microservice if the network function is the VNF.
[0014] In an exemplary aspect of the present disclosure, creating the profile for the network function is based on receiving a request at a user interface.
[0015] In an exemplary aspect of the present disclosure, the request comprises at least one of an on-demand backup request and a scheduled backup request.
[0016] In an exemplary aspect of the present disclosure, sending the backup creation request to the backup module is performed if the request is the on-demand backup request.
[0017] In an exemplary aspect of the present disclosure, if the request is the scheduled backup request, the method further comprises: 1) sending, by the transceiver unit, the backup creation request to a scheduling microservice to handle the scheduling of the backup of the profile; 2) sending, by the transceiver unit, via the scheduling microservice, the backup creation request to the backup module.

[0018] In an exemplary aspect of the present disclosure, the method further comprises: 1) compressing, by the processing unit via the backup module, the created backup of the profile; 2) checking, by the processing unit via the backup module, a free space on a File Transfer Protocol (FTP) server; and 3) moving, by the processing unit via the backup module, the compressed backup of the profile to the FTP server.
[0019] In an exemplary aspect of the present disclosure, the scheduling microservice is a Policy Scheduling Control (PSC) microservice.
[0020] Another aspect of the present disclosure relates to a system for creating backup of a network function. The system comprises a processing unit configured to create a profile for the network function. The system further comprises a transceiver unit connected to at least the processing unit, the transceiver unit is configured to: 1) send, a backup creation request of the profile for the network function to a backup module; and 2) transmit, the backup creation request from the backup module to a service module. Further, the processing unit is configured to create, via the service module, a backup of the profile for the network function. The transceiver unit is further configured to transmit, via the service module, to the backup module, details related to the created backup. Furthermore, a storage unit connected to at least the transceiver unit, the storage unit is configured to store, via the backup module, in a database, the created backup of the profile for the network function.
[0021] Yet another aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing one or more instructions for creating backup of a network function, the instructions include executable code which, when executed by one or more units of a system, causes a processing unit of the system to create a profile for the network function. Further, the executable code when executed causes transceiver unit of the system to send, a backup creation request of the profile for the network function to a backup module. Further, the executable code when executed causes transceiver unit to transmit, the backup creation request

from the backup module to a service module. Further, the executable code when executed causes processing unit to create, via the service module, a backup of the profile for the network function. Furthermore, the executable code when executed causes transceiver unit to transmit, via the service module, to the backup module, 5 details related to the created backup. Thereafter, the executable code when executed causes storage unit of the system to store, via the backup module, in a database, the created backup of the profile for the network function.

10

OBJECTS OF THE DISCLOSURE
[0022] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.

[0023] It is an object of the present disclosure to provide a system and method for 15 creating backup of a network function.
[0024] It is another object of the present disclosure to provide a solution to simplify management of a cloud-native network function (CNF) and a virtual network function (VNF).

20

[0025] It is another object of the present disclosure to provide a solution that allows users to create multiple backup configurations.

[0026] It is yet another object of the present disclosure to provide a solution that 25 improves the data recovery for the users in case of any unexpected outage or failure.
DESCRIPTION OF DRAWINGS
[0027] The accompanying drawings, which are incorporated herein, and constitute
30 a part of this disclosure, illustrate exemplary embodiments of the disclosed methods
and systems in which like reference numerals refer to the same parts throughout the
different drawings. Components in the drawings are not necessarily to scale,
7

emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Also, the embodiments shown in the figures are not to be construed as limiting the disclosure, but the possible variants of the method and system according to the disclosure are illustrated herein to highlight the advantages of the 5 disclosure. It will be appreciated by those skilled in the art that disclosure of such drawings includes disclosure of electrical components or circuitry commonly used to implement such components.
[0028] FIG. 1 illustrates an exemplary block diagram representation of 5th 10 generation core (5GC) network architecture.
[0029] FIG. 2 illustrates an exemplary block diagram of a computing device upon which the features of the present disclosure may be implemented, in accordance with exemplary implementation of the present disclosure.

15

[0030] FIG. 3 illustrates an exemplary block diagram of a system for creating backup of a network function, in accordance with exemplary implementation of the present disclosure.

20 [0031] FIG. 4 illustrates an exemplary method flow diagram for creating backup of a network function, in accordance with exemplary implementation of the present disclosure.
[0032] FIG. 5 illustrates an exemplary system architecture for creating backup of a 25 network function, in accordance with exemplary implementation of the present disclosure.
[0033] FIG. 6 illustrates an exemplary process flow diagram for creating backup of a network function, in accordance with exemplary implementation of the present 30 disclosure.
8

[0034] The foregoing shall be more apparent from the following more detailed description of the disclosure.
DETAILED DESCRIPTION
5
[0035] In the following description, for the purposes of explanation, various specific details are set forth in order to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific 10 details. Several features described hereafter may each be used independently of one another or with any combination of other features. An individual feature may not address any of the problems discussed above or might address only some of the problems discussed above.
15 [0036] The ensuing description provides exemplary embodiments only, and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing an exemplary embodiment. It should be understood that various changes may be made in the function and
20 arrangement of elements without departing from the spirit and scope of the disclosure as set forth.
[0037] Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it will be understood by one of 25 ordinary skill in the art that the embodiments may be practiced without these specific details. For example, circuits, systems, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail.
30 [0038] Also, it is noted that individual embodiments may be described as a process which is depicted as a flowchart, a flow diagram, a data flow diagram, a structure
9

diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations may be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed but could have additional steps not 5 included in a figure.
[0039] The word “exemplary” and/or “demonstrative” is used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. In addition, any
10 aspect or design described herein as “exemplary” and/or “demonstrative” is not necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed
15 description or the claims, such terms are intended to be inclusive in a manner similar to the term “comprising” as an open transition word without precluding any additional or other elements.
[0040] As used herein, a “processing unit” or “processor” or “operating processor” 20 includes one or more processors, wherein processor refers to any logic circuitry for processing instructions. A processor may be a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor, a plurality of microprocessors, one or more microprocessors in association with a Digital Signal Processing (DSP) core, a controller, a microcontroller, Application Specific 25 Integrated Circuits, Field Programmable Gate Array circuits, any other type of integrated circuits, etc. The processor may perform signal coding data processing, input/output processing, and/or any other functionality that enables the working of the system according to the present disclosure. More specifically, the processor or processing unit is a hardware processor.
30
10

[0041] As used herein, “a user equipment”, “a user device”, “a smart-user-device”, “a smart-device”, “an electronic device”, “a mobile device”, “a handheld device”, “a wireless communication device”, “a mobile communication device”, “a communication device” may be any electrical, electronic and/or computing device 5 or equipment, capable of implementing the features of the present disclosure. The user equipment/device may include, but is not limited to, a mobile phone, smart phone, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, wearable device or any other computing device which is capable of implementing the features of the present disclosure. Also, the user device may 10 contain at least one input means configured to receive an input from unit(s) which are required to implement the features of the present disclosure.
[0042] As used herein, “storage unit” or “memory unit” refers to a machine or computer-readable medium including any mechanism for storing information in a
15 form readable by a computer or similar machine. For example, a computer-readable medium includes read-only memory (“ROM”), random access memory (“RAM”), magnetic disk storage media, optical storage media, flash memory devices or other types of machine-accessible storage media. The storage unit stores at least the data that may be required by one or more units of the system to perform their respective
20 functions.
[0043] As used herein “interface” or “user interface refers to a shared boundary across which two or more separate components of a system exchange information or data. The interface may also be referred to a set of rules or protocols that define 25 communication or interaction of one or more modules or one or more units with each other, which also includes the methods, functions, or procedures that may be called.
[0044] All modules, units, components used herein, unless explicitly excluded
30 herein, may be software modules or hardware processors, the processors being a
general-purpose processor, a special purpose processor, a conventional processor, a
11

digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASIC), Field Programmable Gate Array circuits (FPGA), any other type of integrated circuits, etc.
5
[0045] As used herein the transceiver unit include at least one receiver and at least one transmitter configured respectively for receiving and transmitting data, signals, information or a combination thereof between units/components within the system and/or connected with the system.
10
[0046] As discussed in the background section due to such a vast usage and implementation of the CNFs and the VNFs, there is need of maintaining such microservices and applications data in a secure way, which may not be loss and may be retained safely from any unwanted incidents such as network service crash,
15 outage, cyber-attacks and any other undesirable incidents. Also, in the existing solution the backup of the CNF and the VNF applications and services are taken by manual procedure, which may take significant amount of time and may be also result in some errors. Further, since the CNFs and the VNFs applications or services may be operational in many servers and other supported devices, for taking backups
20 of such CNF applications, user has to backup specific CNF applications separately, which is also cumbersome and time-consuming task.
[0047] The present disclosure aims to overcome the above-mentioned and other existing problems in this field of technology by providing method and system for
25 creating backup of a network function. More particularly, the present disclosure provides a solution to simplify the management of a cloud-native network function (CNF) and a virtual network function (VNF). Further, the present disclosure provides a solution that allows users to create multiple backup configurations. Furthermore, the present disclosure provides a solution that improves the data
30 recovery for the users in case of any unexpected outage or failure.
12

[0048] Hereinafter, exemplary embodiments of the present disclosure will be described with reference to the accompanying drawings.
[0049] Referring to FIG. 1 an exemplary block diagram representation of 5th 5 generation core (5GC) network architecture, in accordance with exemplary implementation of the present disclosure is shown. As shown in FIG. 1, the 5GC network architecture [100] includes a user equipment (UE) [102], a radio access network (RAN) [104], an access and mobility management function (AMF) [106], a Session Management Function (SMF) [108], a Service Communication Proxy
10 (SCP) [110], an Authentication Server Function (AUSF) [112], a Network Slice Specific Authentication and Authorization Function (NSSAAF) [114], a Network Slice Selection Function (NSSF) [116], a Network Exposure Function (NEF) [118], a Network Repository Function (NRF) [120], a Policy Control Function (PCF) [122], a Unified Data Management (UDM) [124], an application function (AF)
15 [126], a User Plane Function (UPF) [128], a data network (DN) [130], wherein all the components are assumed to be connected to each other in a manner as obvious to the person skilled in the art for implementing features of the present disclosure.
[0050] Radio Access Network (RAN) [104] is the part of a mobile 20 telecommunications system that connects user equipment (UE) [102] to the core network (CN) and provides access to different types of networks (e.g., 5G network). It consists of radio base stations and the radio access technologies that enable wireless communication.
25 [0051] Access and Mobility Management Function (AMF) [106] is a 5G core network function responsible for managing access and mobility aspects, such as UE registration, connection, and reachability. It also handles mobility management procedures like handovers and paging.
30 [0052] Session Management Function (SMF) [108] is a 5G core network function responsible for managing session-related aspects, such as establishing, modifying,
13

and releasing sessions. It coordinates with the User Plane Function (UPF) for data forwarding and handles IP address allocation and QoS enforcement.
[0053] Service Communication Proxy (SCP) [110] is a network function in the 5G 5 core network that facilitates communication between other network functions by providing a secure and efficient messaging service. It acts as a mediator for service-based interfaces.
[0054] Authentication Server Function (AUSF) [112] is a network function in the 10 5G core responsible for authenticating UEs during registration and providing security services. It generates and verifies authentication vectors and tokens.
[0055] Network Slice Specific Authentication and Authorization Function (NSSAAF) [114] is a network function that provides authentication and 15 authorization services specific to network slices. It ensures that UEs can access only the slices for which they are authorized.
[0056] Network Slice Selection Function (NSSF) [116] is a network function responsible for selecting the appropriate network slice for a UE based on factors 20 such as subscription, requested services, and network policies.
[0057] Network Exposure Function (NEF) [118] is a network function that exposes capabilities and services of the 5G network to external applications, enabling integration with third-party services and applications.
25
[0058] Network Repository Function (NRF) [120] is a network function that acts as a central repository for information about available network functions and services. It facilitates the discovery and dynamic registration of network functions.
14

[0059] Policy Control Function (PCF) [122] is a network function responsible for policy control decisions, such as QoS, charging, and access control, based on subscriber information and network policies.
5 [0060] Unified Data Management (UDM) [124] is a network function that centralizes the management of subscriber data, including authentication, authorization, and subscription information.
[0061] Application Function (AF) [126] is a network function that represents 10 external applications interfacing with the 5G core network to access network capabilities and services.
[0062] User Plane Function (UPF) [128] is a network function responsible for handling user data traffic, including packet routing, forwarding, and QoS 15 enforcement.
[0063] Data Network (DN) [130] refers to a network that provides data services to user equipment (UE) in a telecommunications system. The data services may include but are not limited to Internet services, private data network related services.
20
[0064] Further, the 5G core network is designed as an interconnected system of Network Functions (NFs) that communicate through service-based interfaces or reference point interfaces. Network Functions within the 5G control plane will use service-based interfaces for their interactions. The user plane functions, and radio
25 interactions shall use the reference point interfaces. Each NF exposes specific functionality and provides services to other NFs. Therefore, any communication or routing between NFs or between nodes and NFs takes place through these interfaces. Interfaces are self-contained software modules that are reusable independently of each other and can be thought of as micro services. In an example,
30 a N5 interface is used to connect the PCF (Policy Control Function) [122] and an AF (Application Function) [126].
15

[0065] Referring to FIG. 2 an exemplary block diagram of a computing device [200] upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure is shown. In 5 an implementation, the computing device [200] may implement a method for handling an overload condition in a network by utilising a system [300]. In another implementation, the computing device [200] itself implements the method for handling an overload condition in a network using one or more units configured within the computing device [200], wherein said one or more units are capable of 10 implementing the features as disclosed in the present disclosure.
[0066] The computing device [200] may include a bus [202] or other communication mechanism for communicating information, and a hardware processor [204] coupled with bus [202] for processing information. The hardware
15 processor [204] may be, for example, a general-purpose microprocessor. The computing device [200] may also include a main memory [206], such as a random-access memory (RAM), or other dynamic storage device, coupled to the bus [202] for storing information and instructions to be executed by the processor [204]. The main memory [206] also may be used for storing temporary variables or other
20 intermediate information during execution of the instructions to be executed by the processor [204]. Such instructions, when stored in non-transitory storage media accessible to the processor [204], render the computing device [200] into a special-purpose machine that is customized to perform the operations specified in the instructions. The computing device [200] further includes a read only memory
25 (ROM) [208] or other static storage device coupled to the bus [202] for storing static information and instructions for the processor [204].
[0067] A storage device [210], such as a magnetic disk, optical disk, or solid-state
drive is provided and coupled to the bus [202] for storing information and
30 instructions. The computing device [200] may be coupled via the bus [202] to a
display [212], such as a cathode ray tube (CRT), Liquid crystal Display (LCD),
16

Light Emitting Diode (LED) display, Organic LED (OLED) display, etc. for displaying information to a computer user. An input device [214], including alphanumeric and other keys, touch screen input means, etc. may be coupled to the bus [202] for communicating information and command selections to the processor 5 [204]. Another type of user input device may be a cursor controller [216], such as a mouse, a trackball, or cursor direction keys, for communicating direction information and command selections to the processor [204], and for controlling cursor movement on the display [212]. The input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allow 10 the device to specify positions in a plane.
[0068] The computing device [200] may implement the techniques described herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware and/or program logic which in combination with the computing device [200] causes
15 or programs the computing device [200] to be a special-purpose machine. According to one implementation, the techniques herein are performed by the computing device [200] in response to the processor [204] executing one or more sequences of one or more instructions contained in the main memory [206]. Such instructions may be read into the main memory [206] from another storage medium,
20 such as the storage device [210]. Execution of the sequences of instructions contained in the main memory [206] causes the processor [204] to perform the process steps described herein. In alternative implementations of the present disclosure, hard-wired circuitry may be used in place of or in combination with software instructions.
25
[0069] The computing device [200] also may include a communication interface [218] coupled to the bus [202]. The communication interface [218] provides a two-way data communication coupling to a network link [220] that is connected to a local network [222]. For example, the communication interface [218] may be an 30 integrated services digital network (ISDN) card, cable modem, satellite modem, or a modem to provide a data communication connection to a corresponding type of
17

telephone line. As another example, the communication interface [218] may be a local area network (LAN) card to provide a data communication connection to a compatible LAN. Wireless links may also be implemented. In any such implementation, the communication interface [218] sends and receives electrical, 5 electromagnetic or optical signals that carry digital data streams representing various types of information.
[0070] The computing device [200] can send messages and receive data, including program code, through the network(s), the network link [220] and the
10 communication interface [218]. In the Internet example, a server [230] might transmit a requested code for an application program through the Internet [228], the ISP [226], a host [224], the local network [222] and the communication interface [218]. The received code may be executed by the processor [204] as it is received, and/or stored in the storage device [210], or other non-volatile storage for later
15 execution.
[0071] Referring to FIG. 3 an exemplary block diagram of a system [300] for creating backup of a network function, in accordance with exemplary implementation of the present disclosure is illustrated. The system [300] comprises
20 at least one processing unit [302], at least one transceiver unit [304], at least one storage unit [306], and at least one user interface [308]. Also, all of the components/ units of the system [300] are assumed to be connected to each other unless otherwise indicated below. As shown in the FIG. 3 all units shown within the system [300] should also be assumed to be connected to each other. Also, in FIG. 3 only a few
25 units are shown, however, the system [300] may comprise multiple such units or the system [300] may comprise any such numbers of said units, as required to implement the features of the present disclosure. Further, in an implementation, the system [300] may reside in a server or the network entity or the system [300] may be in communication with the network entity to implement the features as disclosed
30 in the present disclosure.
18

[0072] The system [300] is configured for creating backup of a network function with the help of the interconnection between the components/units of the system [300]. The network function may include such as, but not limited to, an Access and Mobility Function (AMF) [106], a Session Management Function (SMF) [108], a 5 Service Communication Proxy (SCP) [110], etc. The system [300] is configured to provide both on-demand and scheduled backup options within a single profile. This allows users to choose between immediate data protection and automated regular backups, catering to diverse scenarios and preferences. The system [300] creates backup of a network function, once it receives an input from the user to initiate the 10 process of creating the backup.
[0073] In operation, the processing unit [302] creates a profile for the network function. The profile for the network function is created based on a backup request received at a user interface [308]. The request received at the user interface [308]
15 may include data related to the network function. Further, to create the profile for the network function, the processing unit [302] combines the data related to the network function provided at the user interface [308] along with the received request to create the profile. In an example, the data related to the network function may include a name of the network function, a unique identifier of the network
20 function that uniquely identifies the network function from other network functions and the services offered by the network function. In yet another example, the data related to the network function may also include configuration parameters such as, but not limited to, IP address, port numbers used by the network function to communicate in a network. The data related to the network function may also
25 include interfaces and protocols that may be used by the network function to communicate with other network functions. It is to be noted, that the 5G core network is designed as an interconnected system of Network Functions (NFs) that communicate through service-based interfaces or reference point interfaces. NFs within the 5G control plane will use service-based interfaces for their interactions.
30 The user plane functions, and radio interactions shall use the reference point interfaces. Each NF exposes specific functionality and provides services to other
19

NFs. Therefore, any communication or routing between NFs or between nodes and NFs takes place through these interfaces. Interfaces are self-contained software modules that are reusable independently of each other and can be thought of as micro services. As an example, a N5 interface is used to connect the PCF (Policy 5 Control Function) [122] and an AF (Application Function) [126].
[0074] It may be noted that the aforementioned data related to the network function for creating the profile for the network function are only exemplary and in no manner is to be construed to limit the scope of the present subject matter. The 10 received data related to the network function to create the profile for the network function may also include other examples and such examples would also lie within the scope of the present subject matter.
[0075] Continuing further, the network function is at least one of a cloud-native 15 network function (CNF) and a virtual network function (VNF). The CNF is a software implementation of a function, or an application that is traditionally performed on a physical device. Further, the CNFs are designed and implemented to run inside containers. The containers are packages of software that contain all of the necessary elements to run in any environment. In this way, the containers 20 virtualize the operating system and run anywhere. Furthermore, the VNFs are virtualized network services. The VNFs include such as, but not limited to, virtualised directory services, virtualised routers, virtualised firewalls, etc. The VNFs are deployed in Virtual Machines (VMs) on common virtualization infrastructure software such as VMWare or KVM.
25
[0076] Continuing further, once the profile for the network function is created, the transceiver unit [304] sends, the backup creation request of the profile for the network function to a backup module. The backup creation request for the network function is input by a user at the user interface [308]. The transceiver unit [304] 30 forwards the request to the backup module once a profile for the network function has been created by the processing unit [302]. Also, the backup module may be a
20

VNFC Backup and Restore Manager (VBRM). VBRM is a distributed backup restore and disaster recovery manager of VNFs. All data is backed up to secure, redundant offsite facilities by VNF Backup & Upgrade Manager to eliminate problems inherent in VNF crash, costly maintenance, unsecured data and unreliable 5 recovery. The request may be one of an on-demand backup request and a scheduled backup request. In the on-demand backup request the backup module may immediately start the backup of the profile for the network function on receiving the backup creation request. Whereas, in the scheduled backup request a time frame may be defined during which the backup module may start the backup of the profile
10 for the network function. The time frame to backup the profile may be defined by a user. Further, the time frame for backup of the profile may be for e.g. daily, weekly monthly, etc. Further, by scheduling the backup of the profile for the network function, the system automatically ensures that the data is backed up at specified time. automated backup scheduling is an inventive feature. By enabling users to
15 define backup intervals (e.g., daily, weekly, monthly), the system proactively ensures data is backed up at specified times, reducing the risk of data loss and human error.
[0077] Further, in an exemplary aspect of the present disclosure, the backup 20 creation request is sent to the backup module if the request is the on-demand backup request.
[0078] In an exemplary aspect of the present disclosure, if the backup creation request is the scheduled request, the transceiver unit [304] sends the backup creation 25 request to a scheduling microservice to handle the scheduling of the backup of the profile. A microservice is a small, loosely coupled distributed service and each microservice is designed to perform a specific function. Further, each microservice may be developed and deployed independently. Further, the microservice breaks a service into small and manageable components of services.

30

[0079] Continuing further, the scheduling microservice is a Policy Scheduling Control (PSC) microservice. Further, PSC also acts as a centralized platform to
21

schedule jobs for all microservices. The PSC microservice manages the scheduled backup request. PSC microservice is capable of running tasks at pre-defined interval of time configured as per user’s choice. The result of task can be stored in Elastic database or sent in the response. PSC has some inbuilt cron schedulers of 1 5 minute, 15-minute, 1 day or 1 hour and also it can create customized crons. Further, the PSC microservice receives time frames (that may be user defined) in which the profile for the network function may be backed up by the backup module. The PSC microservice at the predefined time automatically initiates the procedure for backup of the profile for the network function. The PSC microservice sends, by the 10 transceiver unit [304], the backup creation request to the backup module automatically at the defined time frame (that may be user defined) to initiate the backup procedure of the profile for the network function.
[0080] Further, the transceiver unit [304] transmits, the backup creation request 15 from the backup module to a service module. Further, in an exemplary aspect of the present disclosure, if the network function is the CNF, the service module may be a Docker Service Adapter (DSA). Furthermore, in an exemplary aspect of the present disclosure, if the network function is the VNF, the service module may be an Open Stack Adapter (OSA). The DSA module lays down the requirements pertaining to 20 Docker Service Adapter, which will directly connect to docker host of swarm manager to deploy the docker image to docker host nodes, which will connect to swarm manager. Furthermore, if the network function is the VNF, the service module may be an Open Stack Adapter (OSA). The OSA microservice acts as an adaptor and exposes the OpenStack APIs for the other microservices in a user-25 friendly mode. All the interaction of NFV platform with OpenStack is via OSA. It exposes the functionality of VM deployment, VM management and CPU flavours CRUD operations.
[0081] Continuing further, the service module is where the backup of the profile
30 for the network function may be created. The processing unit [302] via the service
module creates the backup of the profile for the network function. The service
22

module receives the profile for the network function from the backup module to create the backup of the profile for the network function.
[0082] As would be understood, the backup data is the copy of the original data. 5 Also, the backup data is created to restore or retrieve the original data in case the data is lost. The service module makes a copy of all the data included in the profile for the network function (i.e., the data that was received at the user interface [308] to create the profile for the network function). The service module further assigns a file name to the backup profile created (i.e., a different name to the backup profile 10 than the original profile for the network function).
[0083] Continuing further, the service module transmits, via the transceiver unit [304], details related to the created backup profile for the network function to the backup module. The service module may initiate a command or an operation to 15 forward the details to the backup module. The details related to the created backup profile may include, but not limited to, the file name, path of backup file, etc.
[0084] Thereafter, on receiving the created backup of the profile for the network function from the backup module, the storage unit [306] stores in a database, the 20 created backup of the profile for the network function. The backup module initiates a command or an operation to transmit the backup of the profile to the database via the storage unit [306]. The storage unit [306] then stores/saves in the database, the created backup of the profile for the network function.
25 [0085] Further, the processing unit [302], via the backup module, compresses the created backup of the profile for the network function. The process of compressing involves reducing the size of the file to save space in the server where the file is stored or is to be stored. Also, compressed files may be transferred easily across the internet. The processing unit [302], via the backup module, checks a free space on
30 a File Transfer Protocol (FTP) server to move the compressed backup of the profile for the network function to the FTP server. The backup module may establish a connection with the FTP server and may initiate a command or an operation towards
23

the FTP server, to check for the required space to store the compressed backup of the profile. Once, a response is received from the FTP server, the backup module will transfer the compressed profile to the FTP server. To transfer the compressed profile, the backup module will again initiate a command to the FTP server. The 5 FTP servers are software used for transferring files across the internet. There are two essential functions provides in the FTP server to transfer files across the internet i.e., PUT and GET. The PUT allows users to upload file on the server and the GET allows the user to download the file from the server.
10 [0086] Referring to FIG.4 an exemplary method flow diagram for creating backup of a network function, in accordance with exemplary implementation of the present disclosure is illustrated. In an implementation the method [400] is performed by the system [300]. Also, as shown in FIG. 4, the method [400] initiates at step [402].
15 [0087] At step [404], the method [400] comprises creating, by a processing unit [302], a profile for the network function. The network function may include such as, but not limited to, an Access and Mobility Function (AMF) [106], a Session Management Function (SMF) [108], a Service Communication Proxy (SCP) [110], etc. The profile for the network function is created based on a request received at a
20 user interface [308]. The request of received at the user interface [308] includes data related to the network function. Further, to create the profile for the network function the processing unit [302] combines the data related to the network function provided at the user interface [308] along with the received request to create the profile of the network function.
25
[0088] In an example the data related to the network function may include a name of the network function, a unique identifier of the network function that uniquely identifies the network function from other network functions, the functions of the network function and services offered by the network function. In another example 30 the data related to the network function may also include interfaces and protocols that may be used by the network function to communicate with other network
24

functions. In yet another example the data related to the network function may also include configuration parameters such as, but not limited to, IP address, port numbers used by the network function to communicate in a network.
5 [0089] It may be noted that the aforementioned data related to the network function for creating the profile for the network function are only exemplary and in no manner is to be construed to limit the scope of the present subject matter. The received data related to the network function to create the profile for the network function may also include other examples and such examples would also lie within 10 the scope of the present subject matter.
[0090] Continuing further, the network function is at least one of a cloud-native network function (CNF) and a virtual network function (VNF). The CNF is a software implementation of a function, or an application that is traditionally
15 performed on a physical device. Further, the CNF are designed and implemented to run inside containers. Containers are packages of software that contain all of the necessary elements to run in any environment. In this way, containers virtualize the operating system and run anywhere. Furthermore, the VNF are virtualized network services. The VNF includes such as, but not limited to, virtualised directory
20 services, virtualised routers, virtualised firewalls, etc. The VNFs are deployed in Virtual Machines (VMs) on common virtualization infrastructure software such as VMWare or KVM.
[0091] Next, at step [406], the method [400] comprises sending, by a transceiver 25 unit [304], a backup creation request of the profile for the network function to a backup module. Also, the backup module may be a VNFC Backup and Restore Manager (VBRM). VBRM is a distributed backup restore and disaster recovery manager of VNFs. All data is backed up to secure, redundant offsite facilities by VNF Backup & Upgrade Manager to eliminate problems inherent in VNF crash, 30 costly maintenance, unsecured data and unreliable recovery. The request may be one of an on-demand backup request and a scheduled backup request. In the on-
25

demand backup request the back module may immediately start the backup of the profile for the network function on receiving the backup creation request. Whereas, in the scheduled backup request a time frame may be defined during which the backup module may start the backup of the profile for the network function. The 5 time frame to back up the profile may be defined by a user. Further, the time frame for backup of the profile may be for e.g. daily, weekly monthly, etc. Further, by scheduling the backup of the profile for the network function, the system automatically ensures that the data is backed up at specified time.
10 [0092] Further, in one example the backup creation request is sent to the backup module if the request is the on-demand backup request.
[0093] In another example, if the backup creation request is the scheduled request, the transceiver unit [304] sends the backup creation request to a scheduling 15 microservice to handle the scheduling of the backup of the profile. A microservice is a small, loosely coupled distributed service and each microservice is designed to perform a specific function. Further, each microservice may developed and deployed independently. Further, the microservice breaks a service into small and manageable components of services.
20
[0094] Continuing further, the scheduling microservice is a Policy Scheduling Control (PSC) microservice. PSC also acts as a centralized platform to schedule jobs for all microservices. PSC microservice is capable of running tasks at pre-defined interval of time configured as per user’s choice. The result of task can be
25 stored in Elastic database or sent in the response. PSC has some inbuilt cron schedulers of 1 minute, 15-minute, 1 day or 1 hour and also it can create customized crons. The PSC microservice manages the scheduled backup request. The PSC microservice receives time frames (that may be user defined) in which the profile for the network function may be backed up by the backup module. The PSC
30 microservice, at the predefined time automatically initiates the procedure for backup of the profile for the network function. The PSC microservice sends, by the transceiver unit [304], the backup creation request to the backup module
26

automatically at the defined time frame (that may be user defined) to initiate the backup procedure of the profile for the network function.
[0095] Further, at step [408], the method [400] comprises transmitting, by the 5 transceiver unit [304], the backup creation request from the backup module to a service module. Further, if the network function is the CNF, the service module may be a Docker Service Adapter (DSA). The DSA module lays down the requirements pertaining to Docker Service Adapter, which will directly connect to docker host of swarm manager to deploy the docker image to docker host nodes, which will
10 connect to swarm manager. Furthermore, if the network function is the VNF, the service module may be an Open Stack Adapter (OSA). The OSA microservice acts as an adaptor and exposes the OpenStack APIs for the other microservices in a user-friendly mode. All the interaction of NFV platform with OpenStack is via OSA. It exposes the functionality of VM deployment, VM management and CPU flavours
15 CRUD operations.
[0096] Furthermore, at step [410], the method [400] comprises, creating, by the
processing unit [302], via the service module, a backup of the profile for the
network function. The service module receives the profile for the network function
20 from the backup module to create the backup of the profile for the network function.
[0097] As would be understood, the backup data is the copy of the original data. Also, the backup data is created to restore or retrieve the original data in case the data is lost. The service module makes a copy of all the data included in the profile 25 for the network function (i.e., the data that was received at the user interface [308] to create the profile for the network function). The service module further assigns a file name to the backup profile created (i.e., a different name to the backup profile than the original profile for the network function).
30 [0098] Thereafter, at step [412], the method [400] comprises transmitting, by the transceiver unit [304] via the service module, to the backup module, details related
27

to the created backup. The details related to the created backup profile may include, but not limited to, the file name, path of backup file, etc.
[0099] Moreover, at step [414], the method [400] comprises storing, by a storage 5 unit [306] via the backup module, in a database, the created backup of the profile for the network function. The backup module initiates a command or an operation to transmit the backup of the profile to the database via the storage unit [306]. The storage unit [306] then stores/saves in the database, the created backup of the profile for the network function.
10
[0100] Continuing further, the processing unit [302], via the backup module, compresses the created backup of the profile for the network function. The process of compressing involves reducing the size of the file to save space on the server where the file is stored or is to be stored. Also, compressed files may be transferred
15 easily across the internet. The processing unit [302], via the backup module, checks a free space on a File Transfer Protocol (FTP) server to move the compressed backup of the profile for the network function to the FTP server. The FTP servers are software used for transferring files across the internet. There are two essential functions provides in the FTP server to transfer files across the internet i.e., PUT
20 and GET. The PUT allows users to upload file on the server and the GET allows the user to download the file from the server.

[0101]

The method [400] terminates at step [416].

25 [0102] Referring to FIG. 5, which illustrates an exemplary system architecture for creating backup of a network function, in accordance with exemplary implementation of the present disclosure is illustrated. The system architecture comprises at least one User Interface (UI) [502], at least one VBRM [504], at least one Policy Scheduling Control (PSC) [506], one of a Docker Service Adapter
30 (DSA) [508a] and an Open Stack Adapter (OSA) [508b], at least one database [510] and at least one server [512]. Also, all of the components/ units of the system architecture [500] are assumed to be connected to each other unless otherwise
28

indicated below. As shown in the FIG. 5 all units shown within the system architecture [500] should also be assumed to be connected to each other. Further, in an implementation, the system architecture [500] works in conjunction with the system [300].
5
[0103] Particularly, the UI [502] receives a request to create a backup for the network function. The request received at the UI [502] may include data related to the network function. Further, for creating the backup of the network function, a profile is first created for the network function, which is then used for creating the 10 back up for the network function.
[0104] The UI [502] then transmits the request to create the profile for the network function to the VNFC Backup and Restore Manager (VBRM). VBRM is a distributed backup restore and disaster recovery manager of VNFs. All data is 15 backed up to secure, redundant offsite facilities by VNF Backup & Upgrade Manager to eliminate problems inherent in VNF crash, costly maintenance, unsecured data and unreliable recovery. The VBRM [504] combines all the data received at the UI [502] and creates a profile for the network function. The VBRM [504] also initiates a backup creation request of the profile for the network function.
20
[0105] If the backup request received at the UI [502] is an on-demand request, i.e., to immediately start the backup of the profile for the network function, the VBRM [504] may transfer the backup request to the DSA [508a]/the OSA [508b]. The DSA module lays down the requirements pertaining to Docker Service Adapter, which
25 will directly connect to docker host of swarm manager to deploy the docker image to docker host nodes, which will connect to swarm manager. Furthermore, if the network function is the VNF, the service module may be an Open Stack Adapter (OSA). The OSA microservice acts as an adaptor and exposes the OpenStack APIs for the other microservices in a user-friendly mode. All the interaction of NFV
30 platform with OpenStack is via OSA. It exposes the functionality of VM deployment, VM management and CPU flavours CRUD operations.
29

[0106] Further, if the network function is cloud-native network function (CNF), the request may be transferred to the DSA [508a] to create the backup of the profile for the network function. Further, if the network function is a virtual network function (VNF) [508b], the request may be transferred to the OSA [508b] to create the 5 backup of the profile for the network function.
[0107] In another implementation, if the backup request received at the UI [502] is a scheduled backup request, the backup request may be sent by the VBRM [504] to the Policy Scheduling Control (PSC) [506]. The PSC [506] at the scheduled time 10 (that may be user defined) may trigger the backup request to the VBRM [504]. The VBRM [504] thereafter, may transfer the backup request to the DSA [508a]/the OSA [508b] to create the backup profile for the network function.
[0108] Further, the DSA [508a]/the OSA [508b] creates the backup of the profile 15 for the network function. The DSA [508a]/the OSA [508b] further allocates a new file name to the created backup profile for the network function.
[0109] The VBRM [504] receives the created backup of the profile for the network function along with the file name and the path of the backup file.
20
[0110] The database [510] stores the created backup of the profile for the network function, received from the VBRM [504].
[0111] The VBRM [504] also compresses the created backup of the profile for the 25 network function and moves the compressed file to the server [512]. The server [512] is an FTP server used for transferring files across the internet.
[0112] Referring to FIG. 6 an exemplary process flow diagram for creating backup of a network function, in accordance with exemplary implementation of the present 30 disclosure is illustrated. The process [600] is performed by the system architecture [500] in conjunction with the system [300]. The process [600] starts at step [602].
30

[0113] At step [604], a request to create a backup of a profile for the network function is received by a VBRM [504].
[0114] The step [606] of the process [600] comprises checking whether the 5 received request is an on-demand request or a scheduled request.
[0115] At step [608a], the VBRM [504] will send the request to create the backup of the profile for the network function to a PSC [506], in case the scheduled request is received by the VBRM [504]. PSC microservice is capable of running tasks at 10 pre-defined interval of time configured as per user’s choice. The result of task can be stored in Elastic database or sent in the response. PSC has some inbuilt cron schedulers of 1 minute, 15-minute, 1 day or 1 hour and also it can create customized crons.
15 [0116] At step [608b], at scheduled time, the PSC [506] will trigger the request again to the VBRM [504].
[0117] At [610], the VBRM [504] will send the request to a DSA [508a]/an OSA [508b] for creating the backup of the profile for the network function. The DSA
20 module lays down the requirements pertaining to Docker Service Adapter, which will directly connect to docker host of swarm manager to deploy the docker image to docker host nodes, which will connect to swarm manager. Furthermore, if the network function is the VNF, the service module may be an Open Stack Adapter (OSA). The OSA microservice acts as an adaptor and exposes the OpenStack APIs
25 for the other microservices in a user-friendly mode. All the interaction of NFV platform with OpenStack is via OSA. It exposes the functionality of VM deployment, VM management and CPU flavours CRUD operations.
[0118] Also, as depicted in FIG. 6 if the on-demand request is received by the
30 VBRM [504], the request for creating the backup of the profile for the network
function may be directly sent to the DSA [508a]/the OSA [508b]. Further, in case
the network function is a CNF the request for creating the backup of the profile for
31

the network function may be sent to the DSA [508a] and if the network function is a VNF the request for creating the backup of the profile for the network function may be sent to the OSA [508b].
[0119] Further, at step [612], after successfully taking the backup, the DSA [508a]/the OSA [508b] will share the file name and path to the VBRM [504].
[0120] Furthermore, at step [614], the VBRM [504] compresses the created backup of the profile for the network function and thereafter checks for a free space on the FTP server. After it has checked for free space, the VBRM [504] moves the compressed file to the server [512]. The server [512] is an FTP server used for transferring files across the internet.
[0121] Moreover, at step [616], the process comprises storing the backup of the profile in a database [510].
[0122] Thereafter, the process ends at the step [618].
[0123] The present disclosure further, discloses a non-transitory computer-readable storage medium storing instruction for creating backup of a network function the storage medium comprising executable code which, when executed by one or more units of a system [300], causes processing unit [302] of the system [300] to create a profile for the network function. Further, the executable code when executed causes transceiver unit [304] of the system [300] to send, a backup creation request of the profile for the network function to a backup module. Further, the executable code when executed causes transceiver unit [304] to transmit, the backup creation request from the backup module to a service module. Further, the executable code when executed causes processing unit [302] to create, via the service module, a backup of the profile for the network function. Furthermore, the executable code when executed causes transceiver unit [304] to transmit, via the service module, to the backup module, details related to the created backup. Thereafter, the executable code when executed causes storage unit [306] of the system [300] to store, via the

backup module, in a database, the created backup of the profile for the network function.
[0124] As is evident from the above, the present disclosure provides a technically advanced solution for creating backup of a network function. The present disclosure provides the below listed advantages over the existing solutions:
• Simplified management: Managing CNF backups becomes a simple task with the CNF Backup Profile. The ability to schedule backups eliminates the need for constant manual intervention, freeing up valuable resources and streamlining operations.
• Customizable profiles: CNF backup profiles allow users to create multiple backup configurations, each tailored to a specific CNF. This level of customization ensures that backups are optimized for different use cases and requirements.
• Data Resilience: By using the CNF backup configuration, users greatly improve their data recovery. In a scenario with an unexpected outage, failure, or breach, they can quickly restore their CNFs to its previous state, reducing downtime and ensuring business continuity.
[0125] While considerable emphasis has been placed herein on the disclosed implementations, it will be appreciated that many implementations can be made and that many changes can be made to the implementations without departing from the principles of the present disclosure. These and other changes in the implementations of the present disclosure will be apparent to those skilled in the art, whereby it is to be understood that the foregoing descriptive matter to be implemented is illustrative and non-limiting.
[0126] Further, in accordance with the present disclosure, it is to be acknowledged that the functionality described for the various components/units can be implemented interchangeably. While specific embodiments may disclose a particular functionality of these units for clarity, it is recognized that various

configurations and combinations thereof are within the scope of the disclosure. The functionality of specific units as disclosed in the disclosure should not be construed as limiting the scope of the present disclosure. Consequently, alternative arrangements and substitutions of units, provided they achieve the intended functionality described herein, are considered to be encompassed within the scope of the present disclosure.

We Claim:
1. A method for creating backup of a network function, the method comprising:
- creating, by a processing unit [302], a profile for the network function;
- sending, by a transceiver unit [304], a backup creation request of the profile for the network function to a backup module;
- transmitting, by the transceiver unit [304], the backup creation request from the backup module to a service module;
- creating, by the processing unit [302], via the service module, a backup of the profile for the network function;
- transmitting, by the transceiver unit [304] via the service module, to the backup module, details related to the created backup; and
- storing, by a storage unit [306] via the backup module, in a database, the created backup of the profile for the network function.

2. The method as claimed in claim 1, wherein the network function is at least one of a cloud-native network function (CNF) and a virtual network function (VNF).
3. The method as claimed in claim 2, wherein the service module is a Docker Service Adapter (DSA) microservice if the network function is the CNF.
4. The method as claimed in claim 2, wherein the service module is an Open Stack Adapter (OSA) microservice if the network function is the VNF.
5. The method as claimed in claim 1, wherein creating the profile for the network function is based on receiving a request at a user interface [308].
6. The method as claimed in claim 1, wherein the request comprises one of an on-demand backup request and a scheduled backup request.

7. The method as claimed in claim 5, wherein sending the backup creation request to the backup module is performed if the request is the on-demand backup request.
8. The method as claimed in claim 5, wherein, if the request is the scheduled backup request, the method comprises:

- sending, by the transceiver unit [304], the backup creation request to a scheduling microservice to handle the scheduling of the backup of the profile;
- sending, by the transceiver unit [304], via the scheduling microservice, the backup creation request to the backup module.
9. The method as claimed in claim 1, wherein the method further comprises:
- compressing, by the processing unit [302] via the backup module, the created backup of the profile;
- checking, by the processing unit [302] via the backup module, a free space on a File Transfer Protocol (FTP) server;
- moving, by the processing unit [302] via the backup module, the compressed backup of the profile to the FTP server.

10. The method as claimed in claim 8, wherein the scheduling microservice is a Policy Scheduling Control (PSC) microservice.
11. A system for creating backup of a network function, the system comprising:
- a processing unit [302], configured to:
- create a profile for the network function;
- a transceiver unit [304] connected to at least the processing unit [302],
the transceiver unit [304] is configured to:

- send, a backup creation request of the profile for the network function to a backup module;
- transmit, the backup creation request from the backup module to a service module;
- the processing unit [302], further configured to:
- create, via the service module, a backup of the profile for the
network function;
- the transceiver unit [304] further configured to:
- transmit, via the service module, to the backup module, details
related to the created backup; and
- a storage unit [306] connected to at least the transceiver unit [304], the
storage unit [306] is configured to:
- store, via the backup module, in a database, the created backup
of the profile for the network function.
12. The system as claimed in claim 11, wherein the network function is at least one of a cloud-native network function (CNF) and a virtual network function (VNF).
13. The system as claimed in claim 12, wherein the service module is a Docker Service Adapter (DSA) microservice if the network function is the CNF.
14. The system as claimed in claim 12, wherein the service module is an Open Stack Adapter (OSA) microservice if the network function is the VNF.
15. The system as claimed in claim 11, wherein creating the profile for the network function is based on receiving a request at a user interface [308].
16. The system as claimed in claim 11, wherein the request comprises one of an on-demand backup request and a scheduled backup request.

17. The system as claimed in claim 15, wherein sending the backup creation request to the backup module is performed if the request is the on-demand backup request.
18. The system as claimed in claim 15, wherein, if the request is the scheduled backup request, the transceiver unit [304] is configured to:

- send the backup creation request to a scheduling microservice to handle the scheduling of the backup of the profile;
- send via the scheduling microservice, the backup creation request to the backup module.
19. The system as claimed in claim 11, wherein the processing unit [302] is
further configured to:
- compress, via the backup module, the created backup of the profile;
- check, via the backup module, a free space on a File Transfer Protocol (FTP) server;
- move, via the backup module, the compressed backup of the profile to the FTP server.
20. The system as claimed in claim 18, wherein the scheduling microservice is
a Policy Scheduling Control (PSC) microservice.