Sign In to Follow Application
View All Documents & Correspondence

Method And System For Restoring One Or More Network Functions (Nfs) In A Network Environment

Abstract: The present disclosure relates to a method and a system for restoring one or more network functions (NFs) in a network environment. The method includes receiving, by a transceiver unit [302], from a user interface (UI) [304], a request for restoring at least a network function (NF). The method further includes transmitting, by the transceiver unit [302], from a backup and restore module [306], the request for restoring the NF to a node function. The method further includes transferring, by the transceiver unit [302], data associated with at least the backup NF, from a database [308] storing the data. Finally, the method includes performing, by a processing unit [310], at a docket swarm adapter (DSA) module [312], restoring of at least the NF using the data associated with at least the backup NF. [FIG. 4]

Get Free WhatsApp Updates!
Notices, Deadlines & Correspondence

Patent Information

Application #
Filing Date
09 September 2023
Publication Number
11/2025
Publication Type
INA
Invention Field
COMPUTER SCIENCE
Status
Email
Parent Application

Applicants

Jio Platforms Limited
Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India.

Inventors

1. Aayush Bhatnagar
Reliance Corporate Park, Thane-Belapur Road, Ghansoli, Navi Mumbai, Maharashtra 400701, India.
2. Sandeep Bisht
Reliance Corporate Park, Thane-Belapur Road, Ghansoli, Navi Mumbai, Maharashtra 400701, India.
3. Suman Singh Kanwer
Reliance Corporate Park, Thane-Belapur Road, Ghansoli, Navi Mumbai, Maharashtra 400701, India.
4. Nilesh Sanas
Reliance Corporate Park, Thane-Belapur Road, Ghansoli, Navi Mumbai, Maharashtra 400701, India.
5. Ankur Mishra
Reliance Corporate Park, Thane-Belapur Road, Ghansoli, Navi Mumbai, Maharashtra 400701, India.
6. Lokesh Poonia
Reliance Corporate Park, Thane-Belapur Road, Ghansoli, Navi Mumbai, Maharashtra 400701, India.
7. Abhishek Priyadarshi
Reliance Corporate Park, Thane-Belapur Road, Ghansoli, Navi Mumbai, Maharashtra 400701, India.
8. Manisha Singh
Reliance Corporate Park, Thane-Belapur Road, Ghansoli, Navi Mumbai, Maharashtra 400701, India.
9. Shubham Kumar Naik
Reliance Corporate Park, Thane-Belapur Road, Ghansoli, Navi Mumbai, Maharashtra 400701, India.
10. Mohd. Rijvan Khan Mogia
Reliance Corporate Park, Thane-Belapur Road, Ghansoli, Navi Mumbai, Maharashtra 400701, India.
11. Nitesh Gour
Reliance Corporate Park, Thane-Belapur Road, Ghansoli, Navi Mumbai, Maharashtra 400701, India.
12. Ashish Kumar Pandey
Reliance Corporate Park, Thane-Belapur Road, Ghansoli, Navi Mumbai, Maharashtra 400701, India.

Specification

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 RESTORING ONE OR MORE
NETWORK FUNCTIONS (NFS) IN A NETWORK
ENVIRONMENT”
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 RESTORING ONE OR MORE NETWORK FUNCTIONS (NFS) IN A NETWORK ENVIRONMENT
FIELD OF THE DISCLOSURE
[0001] The present disclosure generally relates to network performance management systems. More particularly, embodiments of the present disclosure relate to a method and system for restoring one or more network functions (NFs) in a network environment.
BACKGROUND
[0002] 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.
[0003] 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. 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.

[0004] Various nodes are connected with a network management system for providing various services related to communication. All such nodes have other internal components. The components are run using some applications which need to be upgraded, downgraded at various instances. Also, the files related to these applications also need to be stored in back-up systems to fetch as and when needed. There may be instances where an upgrade, i.e., switching to a later version, or downgrade, i.e., switching to a previous version, of an application is needed. Similarly, there may be other instances where a downgrade, i.e., switching to a lower version of an application is needed. Also, there may be instances where restoration of files is needed.
[0005] Also, while an application is being restored, the users face downtime. The users may not be able to access the application. Therefore, it is required to restore applications as quickly as possible.
[0006] Further, over the period, various solutions have been developed to improve the performance of communication devices and to perform restoration of files. However, there are certain challenges with existing solutions. The existing solutions are for manual restoration. In manual restoration, the time consumed to restore the applications is large, and the solutions are prone to errors. Further, in manual restoration, there can be issues related to the security of sensitive data related to the applications or the nodes such as Cloud native function (CNF) nodes. In the existing solutions, there is no provision for performing automatic restoration of files.
[0007] Thus, there exists an imperative need in the art to provide a method and a system for restoring one or more network functions (NFs) in a network environment.
SUMMARY

[0008] 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.
[0009] An aspect of the present disclosure may relate to a method for restoring one or more network functions (NFs) in a network environment. The method includes receiving, by a transceiver unit, from a user interface (UI), a request for restoring at least a network function (NF). The method further includes transmitting, by the transceiver unit, from a backup and restore module, the request for restoring the NF to a node function. The method further includes transferring, by the transceiver unit, data associated with at least the backup NF, from a database storing the data. The method further includes performing, by a processing unit, at a docket swarm adapter (DSA) module, restoring of at least the NF using the data associated with at least the backup NF.
[0010] In an exemplary aspect of the present disclosure, the one or more NFs correspond to at least: the one or more cloud native functions (CNFs).
[0011] In an exemplary aspect of the present disclosure, the request comprises at least a backup NF selected from available one or more backup NFs, wherein at least the backup NF is used for restoring at least the NF.
[0012] In an exemplary aspect of the present disclosure, the method further comprises determining, by a determining unit, a status of restoring of at least the NF, wherein the determining is performed at the docket swarm adapter (DSA) module; transmitting, by the transceiver unit, from the DSA module to the backup and restore module, the status of restoring of at least the NF. The status of restoring of at least the NF comprises at least one of a successful restoring of at least the NF, and an unsuccessful restoring of at least the NF.
[0013] In an exemplary aspect of the present disclosure, in response to the status of restoring of at least the NF comprising the successful restoring of at least the NF,

the method further comprises transmitting, by the transceiver unit, from the backup and restore module, a notification indicative of the successful restoring of at least the NF. The notification is transmitted to a physical virtual inventory manager (PVIM) module; and updating, by the processing unit at the PVIM module, data associated with at least the restored NF.
[0014] In an exemplary aspect of the present disclosure, the method comprises transmitting, by the transceiver unit, a request to perform the restoring of at least the NF, to the DSA module.
[0015] Another aspect of the present disclosure may relate to a system for restoring one or more network functions (NFs) in a network environment. The system comprises a transceiver unit configured to receive, from a user interface (UI), a request for restoring at least a network function (NF). The transceiver unit is further configured to transmit from a backup and restore module, the request for restoring at least the NF, to a node function. The transceiver unit is further configured to transfer data associated with at least the backup NF, from a database storing the data. The system further comprises a processing unit configured to perform, at a docket swarm adapter (DSA) module, restoring of at least the NF using the data associated with at least the backup NF.
[0016] Yet another aspect of the present disclosure may relate to a non-transitory computer readable storage medium, storing instructions for restoring one or more network functions (NFs) in a network environment, the instructions include executable code which, when executed by one or more units of a system, causes a transceiver unit to receive, from a user interface (UI), a request for restoring at least a network function (NF). The executable code when executed further causes transceiver unit to transmit, from a backup and restore module, the request for restoring at least the NF, to a node function. The executable code when executed further causes the transceiver unit to transfer data associated with at least the backup NF, from a database storing the data. The executable code when executed further

causes a processing unit to perform, at a docket swarm adapter (DSA) module, restoring of at least the NF using the data associated with at least the backup NF.
OBJECTS OF THE DISCLOSURE
[0017] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.
[0018] It is an object of the present disclosure to provide a method and system for restoring one or more network functions (NFs) in a network environment.
[0019] It is another object of the present disclosure to provide a solution for restoration of a cloud native function node that minimizes downtime and service disruption, allowing applications to resume normal operation quickly after a failure or data loss event.
[0020] It is yet another object of the present disclosure to provide a solution for restoration of a cloud native function node that is able to preserve data integrity and facilitates in ensuring that the restored CNFs are an accurate representation of the previously backed-up state.
[0021] It is yet another object of the present disclosure to provide a solution for restoration of a cloud native function node that reduces the risk of data corruption or inconsistencies.
DESCRIPTION OF THE DRAWINGS
[0022] The accompanying drawings, which are incorporated herein, and constitute 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, 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
disclosure. It will be appreciated by those skilled in the art that disclosure of such
5 drawings includes disclosure of electrical components or circuitry commonly used
to implement such components.
[0023] FIG. 1 illustrates an exemplary block diagram representation of 5th generation core (5GC) network architecture.
[0024] FIG. 2 illustrates an exemplary block diagram of a computing device upon
10 which the features of the present disclosure may be implemented in accordance with
exemplary implementation of the present disclosure.
[0025] FIG. 3 illustrates an exemplary block diagram of a system for restoring one or more network functions (NFs) in a network environment, in accordance with exemplary implementations of the present disclosure.
15 [0026] FIG. 4 illustrates a method flow diagram for restoring one or more network
functions (NFs) in a network environment in accordance with exemplary implementations of the present disclosure.
[0027] FIG. 5 illustrates an exemplary block diagram of a system architecture for
restoring one or more network functions (NFs) in a network environment in
20 accordance with exemplary implementations of the present disclosure.
[0028] FIG. 6 illustrates a process flow diagram for restoring one or more network functions (NFs) in a network environment in accordance with exemplary implementations of the present disclosure.
[0029] The foregoing shall be more apparent from the following more detailed
25 description of the disclosure.
7

DETAILED DESCRIPTION
[0030] 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
5 embodiments of the present disclosure may be practiced without these specific
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.
10 [0031] 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
15 arrangement of elements without departing from the spirit and scope of the
disclosure as set forth.
[0032] Specific details are given in the following description to provide a thorough
understanding of the embodiments. However, it will be understood by one of
ordinary skill in the art that the embodiments may be practiced without these
20 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.
[0033] 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
25 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 included in a figure.
8

[0034] 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
aspect or design described herein as “exemplary” and/or “demonstrative” is not
5 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
description or the claims, such terms are intended to be inclusive—in a manner
10 similar to the term “comprising” as an open transition word—without precluding
any additional or other elements.
[0035] As used herein, a “processing unit” or “processor” or “operating processor” 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
15 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 Integrated Circuits, Field Programmable Gate Array circuits, any other type of integrated circuits, etc. The processor may perform signal coding data processing,
20 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.
[0036] 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”,
25 “a wireless communication device”, “a mobile communication device”, “a
communication device” may be any electrical, electronic and/or computing device 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,
30 tablet computer, wearable device or any other computing device which is capable
9

of implementing the features of the present disclosure. Also, the user device may contain at least one input means configured to receive an input from at least one of a transceiver unit, a processing unit, a storage unit, a detection unit and any other such unit(s) which are required to implement the features of the present disclosure.
5 [0037] As used herein, “storage unit” or “memory unit” refers to a machine or
computer-readable medium including any mechanism for storing information in a
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
10 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 functions.
[0038] As used herein “interface” or “user interface refers to a shared boundary
across which two or more separate components of a system exchange information
15 or data. The interface may also be referred to a set of rules or protocols that define
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.
[0039] All modules, units, components used herein, unless explicitly excluded
20 herein, may be software modules or hardware processors, the processors being a
general-purpose processor, a special purpose processor, a conventional processor,
a 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
25 circuits (FPGA), any other type of integrated circuits, etc.
[0040] 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

[0041] As used herein, network function (NF) is functional building block within a network infrastructure that processes and transmits data packets implemented by a network device.
[0042] As used herein, docket swarm adapter module refers to a container
5 orchestration tool for clustering and scheduling docker containers. With docket
swarm adapter, network administrators can establish and manage a cluster of docker nodes as a single virtual system. docket swarm adapter lets developers join multiple physical or virtual machines into a cluster. These individual machines are known as nodes or daemons.
10 [0043] As used herein, physical virtual inventory manager (PVIM) module refers
to module for backing up the virtual machines (VMs) running in an enterprise environment. PVIMs usually run as guests on hypervisors that emulate a computer system and allow multiple PVIMs to share a physical host hardware system.
[0044] As used herein, cloud native functions (CNFs) refer to a network function
15 (NF) that fulfils network functionalities while adhering to cloud-native design
principles without requiring any hardware.
[0045] As discussed in the background section, the current known solutions have
several shortcomings. The present disclosure aims to overcome the above-
mentioned and other existing problems in this field of technology by providing
20 method and system for restoring one or more network functions (NFs) in a network
environment.
[0046] FIG. 1 illustrates an exemplary block diagram representation of 5th
generation core (5GC) network architecture, in accordance with exemplary
implementation of the present disclosure. As shown in FIG. 1, the 5GC network
25 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 (SCP) [110], an Authentication Server Function (AUSF) [112], a Network Slice Specific
11

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) [126], a
5 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.
[0047] Radio Access Network (RAN) [104] is the part of a mobile
telecommunications system that connects user equipment (UE) [102] to the core
10 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.
[0048] Access and Mobility Management Function (AMF) [106] is a 5G core
network function responsible for managing access and mobility aspects, such as UE
15 registration, connection, and reachability. It also handles mobility management
procedures like handovers and paging.
[0049] Session Management Function (SMF) [108] is a 5G core network function
responsible for managing session-related aspects, such as establishing, modifying,
and releasing sessions. It coordinates with the User Plane Function (UPF) for data
20 forwarding and handles IP address allocation and QoS enforcement.
[0050] Service Communication Proxy (SCP) [110] is a network function in the 5G 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.
25 [0051] Authentication Server Function (AUSF) [112] is a network function in the
5G core responsible for authenticating UEs during registration and providing security services. It generates and verifies authentication vectors and tokens.
12

[0052] Network Slice Specific Authentication and Authorization Function (NSSAAF) [114] is a network function that provides authentication and authorization services specific to network slices. It ensures that UEs can access only the slices for which they are authorized.
5 [0053] Network Slice Selection Function (NSSF) [116] is a network function
responsible for selecting the appropriate network slice for a UE based on factors such as subscription, requested services, and network policies.
[0054] Network Exposure Function (NEF) [118] is a network function that exposes
capabilities and services of the 5G network to external applications, enabling
10 integration with third-party services and applications.
[0055] 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.
[0056] Policy Control Function (PCF) [122] is a network function responsible for
15 policy control decisions, such as QoS, charging, and access control, based on
subscriber information and network policies.
[0057] Unified Data Management (UDM) [124] is a network function that centralizes the management of subscriber data, including authentication, authorization, and subscription information.
20 [0058] Application Function (AF) [126] is a network function that represents
external applications interfacing with the 5G core network to access network capabilities and services.
[0059] User Plane Function (UPF) [128] is a network function responsible for
handling user data traffic, including packet routing, forwarding, and QoS
25 enforcement.
13

[0060] 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.
[0061] FIG. 2 illustrates an exemplary block diagram of a computing device [200]
5 (also referred to herein as computer system [200]) upon which the features of the
present disclosure may be implemented in accordance with exemplary
implementation of the present disclosure. In an implementation, the computing
device [200] may also implement a method for restoring one or more network
functions (NFs) in a network environment utilising the system. In another
10 implementation, the computing device [200] itself implements the method for
restoring one or more network functions (NFs) in a network environment using one or more units configured within the computing device [200], wherein said one or more units are capable of implementing the features as disclosed in the present disclosure.
15 [0062] 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
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-
20 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
intermediate information during execution of the instructions to be executed by the
processor [204]. Such instructions, when stored in non-transitory storage media
25 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
(ROM) [208] or other static storage device coupled to the bus [202] for storing static
information and instructions for the processor [204].
14

[0063] 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
instructions. The computing device [200] may be coupled via the bus [1002] to a
display [212], such as a cathode ray tube (CRT), Liquid crystal Display (LCD),
5 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
[204]. Another type of user input device may be a cursor controller [216], such as
10 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 the device to specify positions in a plane.
15 [0064] 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 or programs the computing device [200] to be a special-purpose machine. According to one implementation, the techniques herein are performed by the
20 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, 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
25 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.
[0065] The computing device [200] also may include a communication interface
[218] coupled to the bus [202]. The communication interface [218] provides a two-
30 way data communication coupling to a network link [220] that is connected to a
15

local network [222]. For example, the communication interface [218] may be an
integrated services digital network (ISDN) card, cable modem, satellite modem, or
a modem to provide a data communication connection to a corresponding type of
telephone line. As another example, the communication interface [218] may be a
5 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, electromagnetic or optical signals that carry digital data streams representing various types of information.
10 [0066] The computing device [200] can send messages and receive data, including
program code, through the network(s), the network link [220] and the 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], the local network [222], host [224] and the communication interface
15 [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 execution.
[0067] The computing device [200] encompasses a wide range of electronic devices capable of processing data and performing computations. Examples of
20 computing device [200] include, but are not limited only to, personal computers,
laptops, tablets, smartphones, servers, and embedded systems. The devices may operate independently or as part of a network and can perform a variety of tasks such as data storage, retrieval, and analysis. Additionally, computing device [200] may include peripheral devices, such as monitors, keyboards, and printers, as well
25 as integrated components within larger electronic systems, showcasing their
versatility in various technological applications.
[0068] Referring to FIG. 3, an exemplary block diagram of a system [300] for restoring one or more network functions (NFs) in a network environment, is shown, in accordance with the exemplary implementations of the present disclosure. The
16

system [300] comprises at least one transceiver unit [302], at least one user interface
[304], at least one backup and restore module [306], at least one database [308], at
least one processing unit [310], at least one docket swarm adapter (DSA) module
[312], at least one determining unit [314], and at least one physical virtual inventory
5 manager (PVIM) module [316]. 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 figures all units shown within the system should also be assumed to be connected to each other. Also, in FIG. 3 only a few units are shown, however, the system [300] may comprise multiple such units or the system [300] may
10 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 be present in a user device to implement the features of the present disclosure. The system [300] may be a part of the user device / or may be independent of but in communication with the user device (may also referred herein as a UE). In another
15 implementation, the system [300] may reside in a server or a network entity. In yet
another implementation, the system [300] may reside partly in the server/ network entity and partly in the user device.
[0069] The system [300] is configured for restoring one or more network functions
(NFs) in a network environment, with the help of the interconnection between the
20 components/units of the system [300].
[0070] The system [300] comprises a transceiver unit [302] configured to receive, from a user interface (UI) [304], a request for restoring at least a network function (NF). In general, the network function (NF) is functional building block within a network infrastructure that processes and transmits data packets implemented by a
25 network device. In an example, the network function may be the RAN [104], the
AMF [106], the SMF [108], the SCP [110], the AUSF [112], the NSSAAF [114], the NSSF [116], the NEF [118], the UDM [124], the AF [126] and the UPF [128] (as explained in FIG. 1). The request further comprises at least a backup NF selected from available one or more backup NFs, wherein at least the backup NF is used for
30 restoring at least the NF. In general, a backup Network Function (NF) refers to a
17

stored copy of a network function’s data, configuration, or state that can be used to restore the network function in the event of a failure, corruption, or other issues.
[0071] The transceiver unit [302] receives the request to restore at least the network
function (NF). In an exemplary aspect, a user or network administrator initiates the
5 request for restoring the network function from the at least the backup NF selected
from available one or more backup selected from available one or more backup NF, by inputting the request through the user interface [304].
[0072] In an exemplary aspect, the user interface refers to the interface used by a user or network administrator to interact with the system [300]. The user Interface
10 (UI) [304] may include a series of pages, screens, buttons, forms, and other visual
elements that are used to interact with the system [300]. The user interface (UI) [304] may display the information in the form of such as but not limited to graphics, tables, charts etc. In an exemplary aspect, the user or network administrator may initiate the request for restoring a specific network function (NF) by selecting a
15 backup profile displayed on the user interface [304] associated with that specific
network function (NF).
[0073] In an exemplary aspect, the one or more NFs correspond to at least: the one or more cloud native functions (CNFs).
[0074] In an exemplary aspect, the one or more NFs relates to the one or more cloud
20 native functions (CNFs). The cloud-native function (CNFs) is the network function
(NF) that fulfils network functionalities while adhering to cloud-native design principles without requiring any hardware.
[0075] The transceiver unit [302] is further configured to transmit from a backup
and restore module [306], the request for restoring at least the NF, to a node
25 function.
[0076] In an exemplary aspect, upon receiving the request for restoring the network function, the transceiver unit [302] transmits the request for restoring at least the
18

NF, to the node function using the backup and restore module [306]. he backup and
restore module [306] To transmit the request to the node function, the transceiver
unit [302] determines the appropriate node function to receive the request. This may
involve looking up for routing information or configuration data to ensure the
5 request is transmitted to the correct node.
[0077] The backup and restore module [306] transmits the request to the identified node function. This transmission could involve sending data over a network, through an inter-process communication mechanism, or via a direct API call.
[0078] In an exemplary aspect, the node function may also include access and
10 mobility function (AMF) [106], session management function (SMF) [108],
network repository function (NRF) [120] etc.
[0079] The transceiver unit [302] is further configured to transfer data associated
with at least the backup NF, from a database [308] storing the data. The data
associated with the backup NF may be configuration data, active sessions
15 information, user data such as user defined services or application logs, and the like.
[0080] The transceiver unit [302] transfers data related to the backup network
function (NF) from the database [308] where such backup data is stored. In an
exemplary aspect, the database [308] stores the data associated with the network
function which may be further used as a backup for restoring that particular network
20 function (NF).
[0081] The system [300] further comprises a processing unit [310] configured to perform, at a docket swarm adapter (DSA) module [312], restoring of at least the NF using the data associated with at least the backup NF.
[0082] Based on the data transferred, by the transceiver unit [302], associated with
25 the network function (NF) from the database [308], the processing unit [310] using
the docket swarm adapter (DSA) module [312], performs restoration of at least the
NF. The processing unit [310] ensures that the network function may be reliably
19

recovered from backup NF data thereby minimizing the downtime and service
disruption, allowing the one or more network functions to resume normal operation
quickly after a failure or data loss event and data integrity is preserved, ensuring
that the restored NFs are an accurate representation of the previously backed-up
5 state.
[0083] The transceiver unit [302] is configured to transmit a request, to perform the
restoring of at least the NF, to the DSA module [312]. The DSA module [312] uses
the data associated with the backup NF to restore the NF to its previous state. This
includes applying the backup data to recreate or repair the NF as it was before a
10 failure or issue occurred.
[0084] In an exemplary aspect, before performing the restoration of at least the NF using the data associated with at least the backup NF at the docket swarm adapter (DSA) module [312], the transceiver unit [302] transmits the request to perform the restoration of at least the NF, to the DSA module [312].
15 [0085] The system [300] further comprises a determining unit [314] is configured
to determine, a status of restoring of at least the NF. The determining is performed at the docket swarm adapter (DSA) module [312]. The determining unit [314] determines the status of restoration that may indicate successful restoration of at least the NF or unsuccessful restoration of at least the NF at the docket swarm
20 adapter (DSA) module [312].
[0086] The transceiver unit [302] is configured to transmit, from the DSA module [312], to the backup and restore module [306], the status of restoring of at least the NF. The status of restoring of at least the NF comprises at least one of a successful restoring of at least the NF, and an unsuccessful restoring of at least the NF.
25 [0087] The transceiver unit [302] transmits the status of restoration of at least the
NF to the backup and restore module [306] from the DSA module [312]. In an exemplary aspect, the status includes various outcomes like "restored" indicating the successful restoration of the at least the NF and "configuration error" indicating
20

unsuccessful restoration of the NF. Furthermore, the term status includes any status that provides information about the restoration's progress or result, ensuring that the system [300] may effectively track and report different scenarios encountered during the restoration process.
5 [0088] In an exemplary aspect, in response to the status of restoring of at least the
NF comprises the successful restoring of at least the NF, the transceiver unit [302]
is configured to transmit from the backup and restore module [306], a notification
indicative of the successful restoring of at least the NF. The notification is
transmitted to a physical virtual inventory manager (PVIM) module [316]. In
10 general, the PVIM [316] is a module in a network environment that is configured
to manage and maintain data related to the physical and virtual assets (such as servers, routers, storage devices, virtual machines, cloud services, etc.) within the network.
[0089] In this exemplary aspect, if the status of the restoration process indicates
15 that the network function (NF) has been successfully restored, the transceiver unit
[302] facilitates the transmission of a notification from the backup and restore module [306] to the physical virtual inventory manager (PVIM) module [316]. This notification confirms that the restoration was successful.
[0090] The processing unit [310] is further configured to update, at the PVIM
20 [316], data associated with at least the restored NF.
[0091] In an exemplary aspect, after receiving notification, confirming the
successful restoration of the at least NF by the transceiver unit [302], the processing
unit [310] updates data associated with at least the restored NF at the PVIM [316].
Furthermore, the processing unit [310] is responsible for modifying the data within
25 the physical virtual inventory manager (PVIM) module [316] to reflect the current
state of the network function (NF) that has been successfully restored, the processing unit [310] ensures that the PVIM's records are accurately updated with relevant information about the restored NF.
21

[0092] Referring to FIG. 4, an exemplary flow diagram of a method [400] for
restoring one or more network functions (NFs) in a network environment, in
accordance with exemplary implementations of the present disclosure is shown. In
an implementation the method [400] is performed by the system [300]. Further, in
5 an implementation, the system [300] may be present in a server device to implement
the features of the present disclosure. Also, as shown in FIG. 4, the method [400] starts at step [402].
[0093] At step [404], the method [400] comprises receiving, by the transceiver unit
[302], from the user interface (UI) [304], a request for restoring at least a network
10 function (NF).
[0094] The transceiver unit [302] receives the request to restore at least the network
function (NF). In an exemplary aspect, a user or network administrator initiates the
request for restoring the network function from at least the backup NF selected from
available one or more backup selected from available one or more backup NF, by
15 inputting the request on the user interface [304].
[0095] In an exemplary aspect, the user interface [304] refers to the interface used
by a user or network administrator to interact with the system [300]. The user
Interface (UI) [304] may include a series of pages, screens, buttons, forms, and
other visual elements that are used to interact with the system [300]. The user
20 interface (UI) [304] may display the information in the form of graphics, tables,
charts, etc. In an exemplary aspect, the user or network administrator may initiate the request for restoring a specific network function (NF) by selecting a backup profile displayed on the user interface [304] associated with that specific network function (NF).
25 [0096] In an exemplary aspect, the one or more NFs correspond to at least: the one
or more cloud native functions (CNFs). The cloud-native function (CNFs) is the network function (NF) that fulfils network functionalities while adhering to cloud-native design principles without requiring any hardware.
22

[0097] At step [406], the method [400] comprises transmitting, by the transceiver unit [302], from the backup and restore module [306], the request for restoring the NF to a node function.
[0098] In an exemplary aspect, upon receiving the request for restoring the network
5 function, the transceiver unit [302] transmits the request for restoring at least the
NF, to the node function using the backup and restore module [306].
[0099] In an exemplary aspect, the node function may also include the access and mobility function (AMF) [106], the session management function (SMF) [108], the network repository function (NRF) [120], and the like.
10 [0100] At step [408], the method [400] comprises transferring, by the transceiver
unit [302], data associated with at least the backup NF, from the database [308] storing the data.
[0101] The transceiver unit [302] transfers data related to the backup network
function (NF) from the database [308] where such backup data is stored. In an
15 exemplary aspect, the database [308] stores the data associated with the network
function which may be further used as a backup for restoring that particular network function (NF).
[0102] At step [410], the method [400] comprises performing, by the processing
unit [310], at the docket swarm adapter (DSA) module [312], restoring of at least
20 the NF using the data associated with at least the backup NF.
[0103] Based on the data transferred, by the transceiver unit [302], associated with
the network function (NF) from the database [308], the processing unit [310] using
the docket swarm adapter (DSA) module [312], performs restoration of at least the
NF. The processing unit [310] ensures that the network function may be reliably
25 recovered from backup NF data thereby minimizing the downtime and service
disruption, allowing the one or more network functions to resume normal operation quickly after a failure or data loss event and data integrity is preserved, ensuring
23

that the restored NFs are an accurate representation of the previously backed-up state.
[0104] The method [400] further comprises transmitting, by the transceiver unit
[302], a request to perform the restoring of at least the NF, to the DSA module
5 [312].
[0105] In an exemplary aspect, before performing the restoration of at least the NF using the data associated with at least the backup NF at the docket swarm adapter (DSA) module [312], the transceiver unit [302] transmits the request to perform the restoration of at least the NF, to the DSA module [312].
10 [0106] The method [400] further comprises determining, by the determining unit
[314], a status of restoring of at least the NF. The determining is performed at the docket swarm adapter (DSA) module [312].
[0107] The determining unit [314] determines the status of restoration that may
indicate successful restoration of at least the NF or unsuccessful restoration of at
15 least the NF at the docket swarm adapter (DSA) module [312].
[0108] The method [400] further comprises transmitting, by the transceiver unit
[302], from the DSA module [312], to the backup and restore module [306], the
status of restoring of at least the NF. The status of restoring of at least the NF
comprises at least one of a successful restoring of at least the NF, and an
20 unsuccessful restoring of at least the NF.
[0109] The transceiver unit [302] transmits the status of restoration of at least the
NF to the backup and restore module [306] from the DSA module [312]. In an
exemplary aspect, the status includes various outcomes like "restored" indicating
the successful restoration of the at least the NF and "configuration error" indicating
25 unsuccessful restoration of at least the NF. Furthermore, the term status includes
any status that provides information about the restoration's progress or result,
24

ensuring that the system [300] may effectively track and report different scenarios encountered during the restoration process.
[0110] In response to the status of restoring of at least the NF comprising the
successful restoring of at least the NF, the method further comprises transmitting,
5 by the transceiver unit [302], from the backup and restore module [306], a
notification indicative of the successful restoring of at least the NF. The notification is transmitted to a physical virtual inventory manager (PVIM) module [316].
[0111] In this exemplary aspect, if the status of the restoration process indicates
that the network function (NF) has been successfully restored, the transceiver unit
10 [302] facilitates the transmission of the notification from the backup and restore
module [306] to the physical virtual inventory manager (PVIM) module [316]. This notification confirms that the restoration was successful.
[0112] The method further comprises updating, by the processing unit [310] at the PVIM module [316], data associated with at least the restored NF.
15 [0113] In an exemplary aspect, after receiving notification confirming the
successful restoration of the at least NF by the transceiver unit [302], the processing unit [310] updates data associated with at least the restored NF at the PVIM [316]. Furthermore, the processing unit [310] is responsible for modifying the data within the physical virtual inventory manager (PVIM) module [316] to reflect the current
20 state of the network function (NF) that has been successfully restored, the
processing unit [310] ensures that the PVIM's module [316] records are accurately updated with relevant information about the restored NF.
[0114] At step [412], the method [400] terminates.
[0115] Referring to FIG. 5, an exemplary block diagram of a system architecture
25 [500] for restoring one or more network functions (NFs) in a network environment,
is shown, in accordance with the exemplary implementations of the present disclosure.
25

[0116] The system architecture [500] comprises the user interface [304] for
selecting the backup to restore NF. In an exemplary aspect, the user or network
administrator may initiate the request for restoring a specific network function (NF)
by selecting a backup profile displayed on the user interface [304] associated with
5 that specific network function (NF). The request is transmitted to the backup and
restore module [306]. The backup and restore module [306] may also be referred to as a virtual backup and restore module (VBRM) [306].
[0117] The virtual backup and restore module (VBRM) [306] fetches the backup
profile from the database [308]. In an exemplary aspect, the database [308] stores
10 the data associated with the network function which may be further used as a backup
for restoring that particular network function (NF).
[0118] The virtual backup and restore module (VBRM) [306] then send the backup file to the docket swarm adapter (DSA) module [312] for initiating the restoration process. Based on the data transferred, by the transceiver unit [302], associated with
15 the network function (NF) from the database [308], the processing unit [310] using
the docket swarm adapter (DSA) module [312], performs restoration of at least the NF. In an exemplary aspect, docket swarm adapter (DSA) module [312] ensures that the network function may be reliably recovered from backup NF data thereby minimizing the downtime and service disruption, allowing the one or more network
20 functions to resume normal operation quickly after a failure or data loss event and
data integrity is preserved, ensuring that the restored NFs are an accurate representation of the previously backed-up state.
[0119] The docket swarm adapter (DSA) module [312] sends back to the VBRM [306] a response indicating whether the restoration process was successful or not.
25 [0120] In this exemplary aspect, after receiving notification confirming the
successful restoration of the at least NF by the VBRM [306], the VBRM [306] further updates data associated with at least the restored NF at the physical virtual inventory manager (PVIM) [316]. In general, the PVIM [316] is a module in a network environment that is configured to manage and maintain data related to the
26

physical and virtual assets (such as servers, routers, storage devices, virtual machines, cloud services, etc.) within the network.
[0121] The physical virtual inventory manager (PVIM) module [316] sends back a
response to the VBRM [306] indicating that the PVIM module [316] has been
5 successfully updated.
[0122] Referring to FIG. 6, an exemplary process [600] flow diagram for restoring
one or more network functions (NFs) in a network environment, in accordance with
exemplary implementations of the present disclosure is shown. In an
implementation the process [400] is performed by the system [300]. Further, in an
10 implementation, the system [300] may be present in a server device to implement
the features of the present disclosure. Also, as shown in FIG. 6, the method [600] starts at step [602].
[0123] At step [604], the process [600] comprises selecting appropriate CNF
backup for restoration which are available within the list of backups in the CNF
15 back system. In an exemplary aspect, the user or network administrator may initiate
the request for restoring a specific network function (NF) by selecting a backup profile displayed on the user interface [304] associated with that specific network function (NF).
[0124] At step [606], after selecting appropriate CNF backup profile from the UI
20 [304], the process [600] comprises sending a request for restoration of at least the
NF to the VBRM [306] (also referred to herein as backup and restore module [306]). In an exemplary aspect, upon receiving the request for restoring the network function, the transceiver unit [302] transmits the request for restoring at least the NF, to the node function using the virtual backup and restore module [306].
25 [0125] At step [608], the VBRM [306] service will move the backup file from a
file transfer protocol (FTP) server to DSA [312] (also referred to herein as DSA module [312]) and ask DSA [312] to start the restoring process for that backup file. In an exemplary aspect, based on the data transferred, by the transceiver unit [302],
27

associated with the network function (NF) from the database [308], the processing unit [310] using the docket swarm adapter (DSA) module [312], performs restoration of at least the NF. The processing unit [310] ensures that the network function may be reliably recovered from backup NF data thereby minimizing the downtime and service disruption, allowing the one or more network functions to resume normal operation quickly after a failure or data loss event and data integrity is preserved, ensuring that the restored NFs are an accurate representation of the previously backed-up state. As used herein, file transfer protocol server (commonly known as FTP Server) is a server that facilitates the secure exchange of files over a transmission control protocol/internet protocol (TCP/IP) network.
[0126] At step [610], after restoring the CNF, DSA [312] may notify the VBRM [306] for successful/unsuccessful restoration status. In an exemplary aspect, the transceiver unit [302] transmits the status of restoration of at least the NF to the virtual backup and restore module [306] from the DSA module [312]. In an exemplary aspect, the status includes various outcomes like "restored" indicating the successful restoration of at least the NF and "configuration error" indicating unsuccessful restoration of at least the NF. Furthermore, the term status includes any status that provides information about the restoration's progress or result, ensuring that the system [300] may effectively track and report different scenarios encountered during the restoration process.
[0127] At step [612], if restoration is successful, the VBRM [306] may notify PVIM [316] and the PVIM [316] (also referred to herein as PVIM module [316]) updates CNFC details in database. In this exemplary aspect, if the status of the restoration process indicates that the network function (NF) has been successfully restored, the transceiver unit [302] facilitates the transmission of the notification from the virtual backup and restore module [306] to the physical virtual inventory manager (PVIM) module [316]. This notification confirms that the restoration was successful. Furthermore, after receiving notification confirming the successful restoration of the at least NF by the transceiver unit [302], the processing unit [310] updates data associated with at least the restored NF at the PVIM [316].

Furthermore, the processing unit [310] is responsible for modifying the data within the physical virtual inventory manager (PVIM) module [316] to reflect the current state of the network function (NF) that has been successfully restored, the processing unit [310] ensures that the PVIM's [316] records are accurately updated with relevant information about the restored NF.
[0128] At step [612], the process [600] terminates.
[0129] The present disclosure further discloses a non-transitory computer readable storage medium, storing instructions for restoring one or more network functions (NFs) in a network environment, the instructions include executable code which, when executed by one or more units of a system, causes a transceiver unit to receive, from a user interface (UI), a request for restoring at least a network function (NF). The executable code when executed further causes the transceiver unit to transmit, from a backup and restore module, the request for restoring at least the NF, to a node function. The executable code when executed further causes a transceiver unit to transfer data associated with at least the backup NF, from a database storing the data. The executable code when executed further causes a processing unit to perform, at a docket swarm adapter (DSA) module, restoring of at least the NF using the data associated with at least the backup NF.
[0130] As is evident from the above, the present disclosure provides a technically advanced solution for restoring one or more network functions (NFs) in a network environment. The present solution enables swift recovery of cloud native functions (CNFs) from backup profiles. Further, the implementation of features of the present invention also minimizes downtime and service disruption, allowing applications to resume normal operation quickly after a failure or data loss event. Also, the present invention is able to preserve data integrity and facilitates in ensuring that the restored CNFs are an accurate representation of the previously backed-up state. Also, by implementing the features of the present solution, one is able to reduce the risk of data corruption or inconsistencies. Also, the solution optimizes resource usage during restoration, ensuring efficient utilization of storage and network

resources. Further, the solution offers an intuitive and user-friendly interface for initiating, monitoring, and managing CNF restoration processes. Also, the solution ensures consistent and efficient restoration processes even in large and complex environments.
[0131] Further, in accordance with the present disclosure, it is to be acknowledged that the functionality described for the various the 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.
[0132] 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.

We Claim:
1. A method for restoring one or more network functions (NFs) in a network
environment, the method comprising:
- receiving, by a transceiver unit [302], from a user interface (UI) [304], a request for restoring at least a network function (NF);
- transmitting, by the transceiver unit [302], from a backup and restore module [306], the request for restoring the NF to a node function;
- transferring, by the transceiver unit [302], data associated with at least the backup NF, from a database [308] storing the data; and
- performing, by a processing unit [310], at a docket swarm adapter (DSA) module [312], restoring of at least the NF using the data associated with at least the backup NF.

2. The method as claimed in claim 1, wherein the one or more NFs correspond to at least: the one or more cloud native functions (CNFs).
3. The method as claimed in claim 1, wherein the request comprises at least a backup NF selected from available one or more backup NFs, wherein at least the backup NF is used for restoring at least the NF.
4. The method as claimed in claim 1, wherein the method comprises:
- determining, by a determining unit [314], a status of restoring of at least
the NF, wherein the determining is performed at the docket swarm
adapter (DSA) module [312]; and
- transmitting, by the transceiver unit [302], from the DSA module [312], to the backup and restore module [306], the status of restoring of at least the NF,

wherein the status of restoring of at least the NF comprises at least one of a successful restoring of at least the NF, and an unsuccessful restoring of at least the NF.
5. The method as claimed in claim 4, wherein, in response to the status of
restoring of at least the NF comprising the successful restoring of at least the
NF, the method comprises:
- transmitting, by the transceiver unit [302], from the backup and restore module [306], a notification indicative of the successful restoring of at least the NF, wherein the notification is transmitted to a physical virtual inventory manager (PVIM) module [316]; and
- updating, by the processing unit [310] at the PVIM module [316], data associated with at least the restored NF.

6. The method as claimed in claim 1, wherein the method comprises transmitting, by the transceiver unit [302], a request to perform the restoring of at least the NF, to the DSA module [312].
7. A system for restoring one or more network functions (CNFs) in a network environment, the system comprising:
- a transceiver unit [302] configured to:
- receive, from a user interface (UI) [304], a request for restoring at least a network function (NF);
- transmit, from a backup and restore module [306], the request for restoring at least the NF, to a node function;
- transfer data associated with at least the backup NF, from a database [308] storing the data; and
- a processing unit [310] configured to:

- perform, at a docket swarm adapter (DSA) module [312], restoring of at least the NF using the data associated with at least the backup NF.
8. The system as claimed in claim 7, wherein the one or more NFs correspond to at least: the one or more cloud native functions (CNFs).
9. The system as claimed in claim 7, wherein the request comprises at least a backup NF selected from available one or more backup NFs, wherein at least the backup NF is used for restoring at least the NF.
10. The system as claimed in claim 7, wherein a determining unit [314] is configured to:
- determine, a status of restoring of at least the NF, wherein the
determining is performed at the docket swarm adapter (DSA) module
[312]; and
the transceiver unit [302] is further configured to:
- transmit, from the DSA module [312], to the backup and restore module
[306], the status of restoring of at least the NF,
wherein the status of restoring of at least the NF comprises at least one of a successful restoring of at least the NF, and an unsuccessful restoring of at least the NF.
11. The system as claimed in claim 10, wherein, in response to the status of
restoring of at least the NF comprising the successful restoring of at least the
NF, the transceiver unit [302] is configured to:
- transmit, from the backup and restore module [306], a notification
indicative of the successful restoring of at least the NF, wherein the
notification is transmitted to a physical virtual inventory manager
(PVIM) module [316]; and

the processing unit [310] is configured to update, at the PVIM [316], data associated with at least the restored NF.
12. The system as claimed in claim 7, wherein the transceiver unit [302] is configured to transmit a request to perform the restoring of at least the NF, to the DSA module [312].

Documents

Application Documents

# Name Date
1 202321060728-STATEMENT OF UNDERTAKING (FORM 3) [09-09-2023(online)].pdf 2023-09-09
2 202321060728-PROVISIONAL SPECIFICATION [09-09-2023(online)].pdf 2023-09-09
3 202321060728-POWER OF AUTHORITY [09-09-2023(online)].pdf 2023-09-09
4 202321060728-FORM 1 [09-09-2023(online)].pdf 2023-09-09
5 202321060728-FIGURE OF ABSTRACT [09-09-2023(online)].pdf 2023-09-09
6 202321060728-DRAWINGS [09-09-2023(online)].pdf 2023-09-09
7 202321060728-Proof of Right [16-01-2024(online)].pdf 2024-01-16
8 202321060728-ORIGINAL UR 6(1A) FORM 1 & 26-050424.pdf 2024-04-15
9 202321060728-FORM-5 [05-09-2024(online)].pdf 2024-09-05
10 202321060728-ENDORSEMENT BY INVENTORS [05-09-2024(online)].pdf 2024-09-05
11 202321060728-DRAWING [05-09-2024(online)].pdf 2024-09-05
12 202321060728-CORRESPONDENCE-OTHERS [05-09-2024(online)].pdf 2024-09-05
13 202321060728-COMPLETE SPECIFICATION [05-09-2024(online)].pdf 2024-09-05
14 202321060728-Request Letter-Correspondence [12-09-2024(online)].pdf 2024-09-12
15 202321060728-Power of Attorney [12-09-2024(online)].pdf 2024-09-12
16 202321060728-Form 1 (Submitted on date of filing) [12-09-2024(online)].pdf 2024-09-12
17 202321060728-Covering Letter [12-09-2024(online)].pdf 2024-09-12
18 202321060728-CERTIFIED COPIES TRANSMISSION TO IB [12-09-2024(online)].pdf 2024-09-12
19 Abstract 1.jpg 2024-09-30
20 202321060728-FORM 3 [07-10-2024(online)].pdf 2024-10-07