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 RECOVERY OF CONFIGURATION IN NETWORK MANAGEMENT SYSTEM”
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 RECOVERY OF CONFIGURATION IN NETWORK MANAGEMENT SYSTEM
TECHNICAL FIELD
[0001] Embodiments of the present disclosure generally relate to network performance management systems. More particularly, embodiments of the present disclosure relate to method and system for recovery of configuration in a network management system.
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. 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.
[0004] For existing solutions, managing and securing configurations for multiple network instances can be complex and error prone. Errors in configuration or unintentional changes can disrupt the network, leading to significant downtime and potential loss of data. Many existing systems don't have a robust system in place for securing configuration changes or for managing issues related to configuration data. If the configuration data is corrupted or lost, it can be challenging to restore the system to its previous state. The risk of causing system instability or data loss may inhibit users from trying different configurations. Without an easy method to restore prior configurations, users may be hesitant to modify settings, limiting innovation and optimization. Further, in many systems, a significant level of technical knowledge is required to perform backups, plan automated backups, and conduct restores. This creates barriers for administrators who may not have extensive technical expertise. Without an efficient system in place, frequent manual interventions may be necessary to manage configuration changes and backups, which can lead to higher administrative costs. Existing systems don't support on-demand or scheduled backups, which limits the flexibility and control that the users have over managing configuration changes. Similarly, these systems may not allow for easy configuration restoration on a network-instance basis. Further, in the case of backup or restoration failures, existing systems don't provide detailed logs, making it difficult for users to identify and address the causes of the failures.
[0005] Thus, there exists a need in the art to solve the above-mentioned problems, which the present disclosure aims to address.
SUMMARY
[0006] 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.
[0007] An aspect of the present disclosure may relate to a method for recovery of configuration in a network management system. The method comprises receiving, by a transceiver unit, via a user interface (UI), a configuration data comprising a plurality of entries corresponding to information associated with one or more network nodes. The method further comprises determining, by a determining unit, based on a user input, at least one of an on-demand backup and a scheduled backup of configuration for the plurality of entries in the configuration data. The method further comprises initiating, by a processing unit, a backup process for each of the plurality of entries listed in the configuration data. The method further comprises storing, by a storage unit, a backup data associated with the configuration, for each of the plurality of entries in a database (DB). And the method finally comprises rendering, by a display unit, a final status of the backup process to a user.
[0008] In an exemplary aspect of the present disclosure, the method further comprises receiving, by the transceiver unit, via the user interface (UI), the configuration data for restoration comprising the plurality of entries corresponding to the information associated with the one or more network nodes. The method further comprises initiating, by the processing unit, a restoration process for each of the plurality of entries listed in the configuration data. The method further comprises updating, by the processing unit, the restored configuration for each of the plurality of entries in the DB. And the method further comprises rendering, by the display unit, a final status of the restoration process to the user.
[0009] In an exemplary aspect of the present disclosure, the method further comprises rendering, by the display unit, failure logs to the user for a set of entries for which the restoration failed.

[0010] In an exemplary aspect of the present disclosure, the information associated with one or more network nodes comprises at least one of a node name and a list of SAP IDs that need to be at least one of being backed up and being restored.
[0011] In an exemplary aspect of the present disclosure, the backup data is stored in the DB in association with a corresponding SAP ID to allow for precise restoration.
[0012] In an exemplary aspect of the present disclosure, the recovery of configuration corresponds to a scheduled backup and restoration of configuration associated with the SAP IDs.
[0013] In an exemplary aspect of the present disclosure, the SAP IDs correspond to identifiers associated with the Service Access Point (SAP).
[0014] Another aspect of the present disclosure may relate to a system for recovery of configuration in a network management system. The system comprises a transceiver unit configured to receive a configuration data comprising a plurality of entries corresponding to information associated with one or more network nodes. The system further comprises a determining unit connected to at least the transceiver unit, the determining unit is configured to determine, based on a user input, at least one of an on-demand backup and a scheduled backup of configuration for the plurality of entries in the configuration data. The system further comprises a processing unit connected to at least the determining unit. The processing unit is configured to initiate a backup process for each of the plurality of entries listed in the configuration data. The system further comprises a storage unit connected to at least the processing unit. The storage unit is configured to store a backup data associated with the configuration for each of the plurality of entries in a database (DB). And the system further comprises a display unit connected to at least the storage unit. The display unit is configured to render a final status of the backup process to a user.

[0015] Another aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing instructions for recovery of configuration in a network management system, the instructions include executable code which, when executed by a one or more units of a system, cause: a transceiver unit of the system to receive a configuration data comprising a plurality of entries corresponding to information associated with one or more network nodes. The instructions which, when executed, further cause a determining unit of the system to determine, based on a user input, at least one of: an on-demand backup and a scheduled backup of configuration for the plurality of entries in the configuration data. The instructions which, when executed, further cause a processing unit of the system to initiate a backup process for each of the plurality of entries listed in the configuration data and a storage unit of the system to store a backup data associated with the configuration for each of the plurality of entries in a database (DB). The instructions which, when executed, further cause a display unit of the system to render a final status of the backup process to a user.
OBJECTS OF THE DISCLOSURE
[0016] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.
[0017] One primary object of the disclosure is to simplify the process of managing and securing configurations for multiple network instances, thereby reducing the potential for errors.
[0018] The disclosure aims to provide a robust system that allows for secure backup and efficient restoration of configuration data. This can help minimize potential data corruption and maintain the integrity of configuration data.

[0019] By ensuring precise restoration of previous configurations, the disclosure intends to encourage users to experiment with different settings without fear of system instability or data loss.
[0020] The disclosure is designed to provide a user-friendly interface that enables administrators to easily manage backups and restoration processes without requiring substantial technical knowledge.
[0021] By automating backups and restoration, the disclosure seeks to minimize the need for frequent manual interventions, thereby reducing administrative costs and potential expenses related to system outages and data loss.
[0022] The disclosure intends to offer flexibility by supporting both on-demand and scheduled backup and restoration of configurations for individual network instances.
[0023] In the case of failures in the backup or restoration process, the disclosure aims to provide detailed logs, making it easier for users to identify and rectify issues.
[0024] The system is designed to automatically back up configurations during version upgrades, ensuring data preservation and allowing for smoother transitions between software versions.
[0025] The disclosure strives to ensure seamless business operations, minimizing downtime in the event of system failures or data loss.
DESCRIPTION OF THE DRAWINGS
[0026] 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
5 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 drawings includes disclosure of electrical components or circuitry commonly used to implement such components. 10
[0027] FIG. 1 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 [0028] FIG. 2 illustrates an exemplary block diagram of a system for recovery of
configuration in a network management system, in accordance with exemplary implementations of the present disclosure.
[0029] FIG. 3 illustrates a method flow diagram for recovery of configuration in a
20 network management system, in accordance with exemplary implementations of
the present disclosure.
[0030] FIG. 4 illustrates an exemplary flow chart for managing configurations of
multiple SAP IDs in a network management system, in accordance with exemplary
25 embodiments of the present disclosure.
[0031] FIG. 5 illustrates an exemplary system architecture for managing configurations of multiple SAP IDs in a network management system, in accordance with exemplary embodiments of the present disclosure. 30
8

[0032] The foregoing shall be more apparent from the following more detailed description of the disclosure.
DETAILED DESCRIPTION
5
[0033] 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. Some of the problems discussed above might not be fully addressed by any of the features described herein. Example embodiments of
15 the present disclosure are described below, as illustrated in various drawings in
which like reference numerals refer to the same parts throughout the different drawings.
[0034] The ensuing description provides exemplary embodiments only, and is not
20 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
arrangement of elements without departing from the spirit and scope of the
25 disclosure as set forth.
[0035] It should be noted that the terms "mobile device", "user equipment", "user
device", “communication device”, “device” and similar terms are used
interchangeably for the purpose of describing the disclosure. These terms are not
30 intended to limit the scope of the disclosure or imply any specific functionality or
limitations on the described embodiments. The use of these terms is solely for
9

convenience and clarity of description. The disclosure is not limited to any particular type of device or equipment, and it should be understood that other equivalent terms or variations thereof may be used interchangeably without departing from the scope of the disclosure as defined herein. 5
[0036] 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
specific details. For example, circuits, systems, processes, and other components
10 may be shown as components in block diagram form in order not to obscure the
embodiments in unnecessary detail. In other instances, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail in order to avoid obscuring the embodiments.
15 [0037] 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 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
20 is terminated when its operations are completed but could have additional steps not
included in a figure.
[0038] The word “exemplary” and/or “demonstrative” is used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the
25 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 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
30 “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.
[0039] As used herein, an “electronic device”, or “portable electronic device”, or
5 “user device” or “communication device” or “user equipment” or “device” refers
to any electrical, electronic, electromechanical, and computing device. The user device is capable of receiving and/or transmitting one or parameters, performing function/s, communicating with other user devices, and transmitting data to the other user devices. The user equipment may have a processor, a display, a memory,
10 a battery, and an input-means such as a hard keypad and/or a soft keypad. The user
equipment may be capable of operating on any radio access technology including but not limited to IP-enabled communication, Zig Bee, Bluetooth, Bluetooth Low Energy, Near Field Communication, Z-Wave, Wi-Fi, Wi-Fi direct, etc. For instance, the user equipment may include, but not limited to, a mobile phone,
15 smartphone, virtual reality (VR) devices, augmented reality (AR) devices, laptop,
a general-purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other device as may be obvious to a person skilled in the art for implementation of the features of the present disclosure.
20 [0040] Further, 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 purpose processor, a conventional processor, a digital signal processor, a plurality of microprocessors, one or more microprocessors in
25 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, input/output processing, and/or any other functionality that enables the working of the system according to the present
30 disclosure. More specifically, the processor or processing unit is a hardware
processor.
11

[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
5 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,
tablet computer, wearable device or any other computing device which is capable
10 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.
15 [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 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
20 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.
[0043] As used herein “interface” or “user interface refers to a shared boundary
25 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 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. 30
12

[0044] All modules, units, components used herein, unless explicitly excluded
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
5 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.
[0045] As used herein the transceiver unit include at least one receiver and at least
10 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.
[0046] As discussed in the background section, the current known solutions have
15 several shortcomings. The present disclosure aims to overcome the above-
mentioned and other existing problems in this field of technology by providing method and system of recovery of configuration in a network management system.
[0047] FIG. 1 illustrates an exemplary block diagram of the computing device
20 [100] 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 [100] may also implement a method [300]
(as shown in FIG. 3) for recovery of configuration in a network management
system (NMS) [200N] (as shown in FIG. 2) utilising a system [200] (as shown in
25 FIG. 2) and system [500] (as shown in FIG. 5). In another implementation, the
computing device [100] may implement the method [300] via the flow chart [400]
(as shown in FIG. 4) depicting the process for managing configurations of multiple
SAP IDs. In another implementation, the computing device [100] itself implements
the method [300] for recovery of configuration in a network management system
30 [200N] using one or more units configured within the computing device [100],
wherein said one or more units are capable of implementing the features as
13

disclosed in the present disclosure. The computing device [100] (as shown in FIG. 1) may reside in the system [200]. In an implementation, the computing device [100] may be connected to the system [200] to perform the present disclosure.
5 [0048] The computing device [100] may include a bus [102] or other
communication mechanism for communicating information, and a hardware
processor [104] coupled with bus [102] for processing information. The hardware
processor [104] may be, for example, a general-purpose microprocessor. The
computing device [100] may also include a main memory [106], such as a random-
10 access memory (RAM), or other dynamic storage device, coupled to the bus [102]
for storing information and instructions to be executed by the processor [104]. The
main memory [106] also may be used for storing temporary variables or other
intermediate information during execution of the instructions to be executed by the
processor [104]. Such instructions, when stored in non-transitory storage media
15 accessible to the processor [104], render the computing device [100] into a special-
purpose machine that is customized to perform the operations specified in the
instructions. The computing device [100] further includes a read only memory
(ROM) [108] or other static storage device coupled to the bus [102] for storing static
information and instructions for the processor [104].
20
[0049] A storage device [110], such as a magnetic disk, optical disk, or solid-state
drive is provided and coupled to the bus [102] for storing information and
instructions. The computing device [100] may be coupled via the bus [102] to a
display [112], such as a cathode ray tube (CRT), Liquid crystal Display (LCD),
25 Light Emitting Diode (LED) display, Organic LED (OLED) display, etc. for
displaying information to a computer user. An input device [1014], including
alphanumeric and other keys, touch screen input means, etc. may be coupled to the
bus [102] for communicating information and command selections to the processor
[104]. Another type of user input device may be a cursor controller [116], such as
30 a mouse, a trackball, or cursor direction keys, for communicating direction
information and command selections to the processor [104], and for controlling
14

cursor movement on the display [112]. 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.
5 [0050] The computing device [100] 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 [100] causes or programs the computing device [100] to be a special-purpose machine. According to one implementation, the techniques herein are performed by the
10 computing device [100] in response to the processor [104] executing one or more
sequences of one or more instructions contained in the main memory [106]. Such instructions may be read into the main memory [106] from another storage medium, such as the storage device [110]. Execution of the sequences of instructions contained in the main memory [106] causes the processor [104] to perform the
15 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.
[0051] The computing device [100] also may include a communication interface
20 [118] coupled to the bus [102]. The communication interface [118] provides a two-
way data communication coupling to a network link [120] that is connected to a
local network [122]. For example, the communication interface [118] 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
25 telephone line. As another example, the communication interface [118] 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 [118] sends and receives electrical,
electromagnetic, or optical signals that carry digital data streams representing
30 various types of information.
15

[0052] The computing device [100] can send messages and receive data, including
program code, through the network(s), the network link [120] and the
communication interface [118]. In the Internet example, a server [130] might
transmit a requested code for an application program through the Internet [128], the
5 ISP [126], the host [124], the local network [122] and the communication interface
[118]. The received code may be executed by the processor [104] as it is received, and/or stored in the storage device [110], or other non-volatile storage for later execution.
10 [0053] Referring to FIG. 2, an exemplary block diagram of the system [200] for
recovery of configuration in a network management system (NMS) [200N], is shown, in accordance with the exemplary implementations of the present disclosure. The configuration here refers to setting up and arranging various network components and parameters in the NMS [200N]. The configuration may
15 include defining and adjusting settings/ values of critical parameters for various
network components and their working, interaction with other components to ensure optimal performance of the NMS [200N]. It is to be noted that the critical parameters may include but not limited to network elements (such as base stations, core network functions, etc.), quality of services (QoS) (such QoS policies, network
20 traffic management, etc.), security (such as authentication, encryption, etc.),
network operation (fault management, etc.), and network monitoring. The system [200] comprises at least one transceiver unit [201], at least one determination unit [202], at least one processing unit [203], at least one storage unit [204] having at least one database (DB) [204db], and at least one display unit [205]. Also, all the
25 components/ units of the system [200] 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. 2 only a few units are shown, however, the system [200] may comprise multiple such units or the system [200] may comprise any such numbers of said units, as required
30 to implement the features of the present disclosure. In an implementation, the
system [200] may reside in a server or a network entity such as but not limited to a
16

network management system (NMS) [200N]. In yet another implementation, the
system [200] may be in communication with one or more network nodes [207]
being managed by the NMS [200N]. In another implementation, the one or more
network nodes [207] may reside in the NMS [200N]. In yet another implementation,
5 the system [200] may reside partly in the server/ network entity such as but not
limited to the NMS [200N]. The system [200] may work in tandem with the system [500] (as shown in FIG. 5) for implementation of the present disclosure.
[0054] The system [200] is configured for recovery of configuration in a network
10 management system, with the help of the interconnection between the
components/units of the system [200]. It is to be noted that the recovery of configuration corresponds to a scheduled backup and restoration of configuration associated with Service Access Point (SAP) IDs. It is to be noted that the SAP ID is an identifier of a Service Access Point.
15
[0055] The transceiver unit [201] is configured to receive, via the user interface (UI) a configuration data comprising a plurality of entries corresponding to information associated with one or more network nodes [207]. It is to be noted that the plurality of entries may include but is not limited to sample configuration sheets
20 having the information associated with the one or more network nodes [207]. It is
further noted that the information associated with the one or more network nodes [207] comprises at least one of a node name and a list of SAP IDs that need to be at least one of being backed up and being restored. The transceiver unit [201] is further configured to receive, via the user interface (UI) the configuration data for
25 restoration comprising the plurality of entries corresponding to the information
associated with the one or more network nodes [207].
[0056] The determining unit [202] is configured to determine, based on a user
input, at least one of an on-demand backup and a scheduled backup of configuration
30 for the plurality of entries in the configuration data. The user input may be an input
for selection of one of the on-demand backup or the scheduled backup.
17

[0057] The processing unit [203] is configured to initiate a backup process for each
of the plurality of entries listed in the configuration data. It is important to note that
the backup process includes saving the plurality of entries in a secured storage such
5 the DB [204db]. The backup process is done to ensure data recovery in case of
system failures or data loss. Further, the processing unit [203] is configured to initiate a restoration process for each of the plurality of entries listed in the configuration data. The processing unit [203] is configured to update the restored configuration for each of the plurality of entries in the DB [204db].
10
[0058] The storage unit [204] is configured to store a backup data associated with the configuration for each of the plurality of entries in the database (DB) [204db]. It is to be noted that the backup data is stored in the DB [204db] in association with a corresponding SAP ID to allow for precise restoration.
15
[0059] The display unit [205] is configured to render a final status of the backup process to a user. The display unit [205] is further configured to render a final status of the restoration process to the user. The display unit [205] is configured to render failure logs to the user for a set of entries for which the restoration failed. The final
20 status is indicative of conclusion of the backup process or the restoration process.
The final status either confirms that the backup process or the restoration process has been completed or not (in case of any failure).
[0060] Referring to FIG. 3, an exemplary method flow diagram [300] for recovery
25 of configuration in a network management system, in accordance with exemplary
implementations of the present disclosure is shown. In an implementation the
method [300] is performed by the system [200]. Further, in an implementation, the
system [200] may be present in a server device to implement the features of the
present disclosure. Furthermore, in an implementation, the system [500] may be
30 present in a server device to implement the method [300] of the present disclosure.
Also, as shown in FIG. 3, the method [300] starts at step [302].
18

[0061] At step [304], the method [300] comprises receiving, by a transceiver unit
[201], via a user interface (UI), a configuration data comprising a plurality of entries
corresponding to information associated with one or more network nodes [207]. It
5 is to be noted that the plurality of entries may include but is not limited to sample
configuration sheets having the information associated with the one or more network nodes [207].
[0062] In an exemplary aspect of the present disclosure, the information associated
10 with the one or more network nodes [207] comprises at least one of a node name
and a list of SAP IDs that need to be at least one of being backed up and being
restored. In an exemplary aspect of the present disclosure, the recovery of
configuration corresponds to a scheduled backup and restoration of configuration
associated with the SAP IDs. In an exemplary aspect of the present disclosure, the
15 SAP IDs correspond to identifiers associated with the Service Access Point (SAP).
[0063] At step [306], the method [300] comprises determining, by a determining
unit [202], based on a user input, at least one of an on-demand backup and a
scheduled backup of configuration for the plurality of entries in the configuration
20 data. The user input may be an input for selection of one of the on-demand backup
or the scheduled backup.
[0064] At step [308], the method [300] comprises initiating, by a processing unit [203], a backup process for each of the plurality of entries listed in the configuration
25 data. It is important to note that the backup process includes saving the plurality of
entries in a secured storage such the DB [204db]. The backup process is done to ensure data recovery in case of system failures or data loss. In an exemplary aspect of the present disclosure, the backup data is stored in the DB [204db] in association with a corresponding SAP ID to allow for precise restoration.
30
19

[0065] At step [310], the method [300] comprises storing, by a storage unit [204],
a backup data associated with the configuration for each of the plurality of entries
in the database (DB) [204db]. It is to be noted that the backup data is stored in the
DB [204db] in association with a corresponding SAP ID to allow for precise
5 restoration.
[0066] At step [312], the method [300] comprises rendering, by a display unit [205], a final status of the backup process to a user. The final status is indicative of conclusion of the backup process or the restoration process. The final status either
10 confirms that the backup process or the restoration process has been completed or
not (in case of any failure). In an exemplary aspect of the present disclosure, the method [300] further comprises receiving, by the transceiver unit [201], via the user interface (UI), the configuration data for restoration comprising the plurality of entries corresponding to the information associated with the one or more network
15 nodes [207]. The method [300] further comprises initiating, by the processing unit
[203], a restoration process for each of the plurality of entries listed in the configuration data. The method [300] further comprises updating, by the processing unit [203], the restored configuration for each of the plurality of entries in the DB [204db]. And the method [300] further comprises rendering, by the display unit
20 [205], a final status of the restoration process to the user. In an exemplary aspect of
the present disclosure, the method [300] further comprises rendering, by the display unit [205], failure logs to the user for a set of entries for which the restoration failed.
[0067] Thereafter, the method [300] terminates at step [314].
25
[0068] Referring to FIG. 4A and 4B, an exemplary flow chart [400A] and [400B] for managing configurations of multiple SAP IDs in a network management system (NMS) [200N] (as shown in FIG. 2) is shown, in accordance with the exemplary embodiments of the present invention.
30
20

[0069] During on-demand or scheduled configuration backup flow, at step 402a, a
user may upload sample configuration sheet from UI containing node name and list
of network instances that need to be backed up. Then, the user has the option of
taking a scheduled backup or an on-demand backup for a provided list of network
5 instances. At step 404a, it is determined whether a scheduled backup option is
selected by the user. If yes, method proceeds to step 406a, where user provides the
interval for backup. At step 408a, it is determined whether the interval is reached.
For example, if user selects hourly backup as the interval, then every hour the
backup is initiated at step 410a. Once the backup initiated, at step 412a, the backup
10 of each network instances configuration is taken and at step 414a, the backup is
stored in DB. In case of scheduled backup, it begins in accordance with the scheduled allocation. At the end, the user can see the final status of the backup profile. The method then terminates at step 416a.
15 [0070] During configuration restoration flow, at step 402b, the user may upload
sample configuration sheet from UI containing Node name and list of network instances that need to be restored. At step 404b, it is checked whether the backup of the node and the network instances is available for restoration. If yes, the method proceeds to step 406b, wherein restoration is initiated. The configurations of each
20 of the network instances is restored and then at step 408b, the restoration is updated
in DB after receiving response from respective nodes. At the end, the user can see the final status of the restore profile. In case of failure, the user can see the failure logs. The method then terminates at step 410b.
25 [0071] Referring to FIG. 5, illustrates an exemplary architecture of a system [500]
for managing configurations of multiple SAP IDs in a network management system (NMS) [200N] (as shown in FIG. 2), in accordance with exemplary embodiments of the present disclosure. It is to be noted that the system [500] is another exemplary module of the network management system [200N] (as shown in FIG. 2) which
30 implements the steps of method [400] (as shown in FIG. 4).
21

[0072] The system [500] for managing configurations of multiple SAP IDs in a
network management system [200N] comprises: a processing unit [502], a user
interface [506], a CMS [508] (also known as NMS), a display unit [504] and a data
repository in form of a database [510]. The processing unit [502] is configured to:
5 receive, via the user interface (UI) [506], a configuration sheet containing a node
name and a list of SAP IDs. The configuration sheet comprises the node name and the list of network instances that need to be backed up or restored.
[0073] Further, the processing unit [502] is configured to determine based on the
10 user input, whether to initiate an on-demand backup or a scheduled backup of
configuration for the plurality of entries in the configuration data. Furthermore, the processing unit [502] is configured to initiate a backup process for each of the SAP IDs listed in the configuration sheet.
15 [0074] The processing unit [502] is configured to store backup data corresponding
to each SAP ID in the database (DB) [510]. The backup data is stored in the DB [510] in association with a corresponding SAP ID to allow for precise restoration. Next, the processing unit [502] is configured to render, via the display unit [504], a final status of the backup process to a user. Further, the processing unit [502] via
20 the display unit [504], is configured to render failure logs to the user for any SAP
ID fails.
[0075] Further, the on-demand network instance wise configuration backup may be created. Furthermore, the network instance wise scheduled configuration backup
25 may also be created. A user may upload sample configuration sheet from the UI
[506] containing node name and list of network instances that need to be backed up. The user has the option of taking the scheduled backup or the on-demand backup for a provided list of network instances. Once the backup is initiated, it begins to take the backup of each network instances configuration and stores it in
30 DB [510]. In case of the scheduled backup, it begins in accordance with the
22

scheduled allocation. At the end, the users can see the final status of the backup profile.
[0076] The present disclosure also encompasses that the processing unit [502] via the UI [506], is configured to receive a configuration sheet for restoration containing the node name and the list of SAP IDs for restoration. The configuration sheet at least comprises a node name and a list of network instances that need to be backed up or restored.
[0077] Further, the processing unit [502], is configured to initiate a restoration process for each of the SAP IDs listed in the restoration configuration sheet.
[0078] Furthermore, the processing unit [502], is configured to update the restored configurations of each SAP ID in the DB [510]. Further, the processing unit [502] is configured to update, the configurations in the DB [510] after receiving a response from respective nodes associated with each SAP ID.
[0079] Next, the processing unit [502] is configured to render, via the display unit [504], a final status of the restoration process to a user. Further, the processing unit [502] via the display unit [504], is configured to render failure logs to the user for any SAP ID fails.
[0080] In another implementation, the system [500] may begin to restore configurations of each network instances and update it in the DB [510] after receiving response from respective nodes. At the end, the user can see the final status of the restore profile. In case of failure, the user can see the failure logs.
[0081] The present disclosure further discloses a non-transitory computer readable storage medium storing instructions for recovery of configuration in a network management system, the instructions include executable code which, when executed by a one or more units of a system, causes: a transceiver unit [201] of the

system [200] to receive a configuration data comprising a plurality of entries corresponding to information associated with one or more network nodes [207]. The instructions further include executable code, which when executed causes a determining unit [202] of the system [200] to determine, based on a user input, at least one of an on-demand backup and a scheduled backup of configuration for the plurality of entries in the configuration data. The instructions further include executable code, which when executed causes a processing unit [203] of the system [200] to initiate a backup process for each of the plurality of entries listed in the configuration data. The instructions further include executable code, which when executed causes a storage unit [204] of the system [200] to store a backup data associated with the configuration for each of the plurality of entries in a database (DB) [204db]. The instructions further include executable code, which when executed causes a display unit [205] of the system [200] to render a final status of the backup process to a user.
[0082] 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 encompassed within the scope of the present disclosure.
[0083] As is evident from the above, the present disclosure provides a technically advanced solution for recovery of configuration in a network management system. The present disclosure ensures that critical configuration parameters are backed up and can be precisely restored. This reduces the potential for data corruption and helps to maintain the integrity of configuration data. Further, the system allows for

quicker recovery in the event of system failures or data losses thanks to automated and reliable backups. This lowers downtime and guarantees seamless business continuity. Furthermore, users can experiment with different configurations with confidence knowing that they can easily go back to previously known functioning settings if necessary, reducing the concern of undesirable effects from modifications. Also, without substantial technical knowledge, administrators can initiate backups, plan automatic backups, and carry out restores more easily with a user-friendly interface. By decreasing the frequency of manual interventions, the system helps reduce administrative costs as well as possible expenditures related to system outages and data loss.
[0084] 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 [300] for recovery of configuration in a network management
system [200N], the method [300] comprising the steps of:
receiving, by a transceiver unit [201], via a user interface (UI), a configuration data comprising a plurality of entries corresponding to information associated with one or more network nodes [207];
determining, by a determining unit [202], based on a user input, at least one of: an on-demand backup and a scheduled backup of configuration for the plurality of entries in the configuration data;
initiating, by a processing unit [203], a backup process for each of the plurality of entries listed in the configuration data;
storing, by a storage unit [204], a backup data associated with the configuration, for each of the plurality of entries in a database (DB) [204db]; and
rendering, by a display unit [205], a final status of the backup process to a user.
2. The method [300] as claimed in claim 1, wherein the method [300] comprises:
receiving, by the transceiver unit [201], via the user interface (UI), the configuration data for restoration comprising the plurality of entries corresponding to the information associated with the one or more network nodes [207];
initiating, by the processing unit [203], a restoration process for each of the plurality of entries listed in the configuration data;
updating, by the processing unit [203], the restored configuration for each of the plurality of entries in the DB [204db]; and
rendering, by the display unit [205], a final status of the restoration process to the user.
3. The method [300] as claimed in claim 2, further comprises rendering, by the
display unit [205], failure logs to the user for a set of entries for which the
restoration failed.

4. The method [300] as claimed in claim 1, wherein the information associated with one or more network nodes [207] comprises at least one of a node name and a list of Service Access Point (SAP) IDs that need to be at least one of: being backed up and being restored.
5. The method [300] as claimed in claim 1, wherein the backup data is stored in the DB [204db] in association with a corresponding SAP ID to allow for precise restoration.
6. The method [300] as claimed in claim 4, wherein the recovery of the configuration corresponds to a scheduled backup and restoration of configuration associated with the SAP IDs.
7. The method [300] as claimed in claim 4, wherein the SAP IDs correspond to identifiers associated with a Service Access Point (SAP).
8. A system [200] for recovery of configuration in a network management system (NMS) [200N], the system [200] comprises:
a transceiver unit [201] configured to receive a configuration data comprising a plurality of entries corresponding to information associated with one or more network nodes [207];
a determining unit [202] connected to at least the transceiver unit [201], the determining unit [202] configured to determine, based on a user input, at least one of: an on-demand backup and a scheduled backup of configuration for the plurality of entries in the configuration data;
a processing unit [203] connected to at least the determining unit [202], the processing unit [203] configured to initiate a backup process for each of the plurality of entries listed in the configuration data;
a storage unit [204] connected to at least the processing unit [203], the storage unit [204] configured to store a backup data associated with the configuration, for each of the plurality of entries in a database (DB) [204db]; and
a display unit [205] connected to at least the storage unit [204], the display unit [205] configured to render a final status of the backup process to a user.

9. The system [200] as claimed in claim 8, wherein the system [200] comprises:
the transceiver unit [201] is further configured to receive the configuration data for restoration comprising the plurality of entries corresponding to the information associated with the one or more network nodes [207];
the processing unit [203] is further configured to:
initiate a restoration process for each of the plurality of entries listed in the configuration data;
update the restored configuration for each of the plurality of entries in the DB [204db]; and
the display unit [205] is configured to render a final status of the restoration process to the user.
10. The system [200] as claimed in claim 9, wherein the display unit [205] is configured to render failure logs to the user for a set of entries for which the restoration failed.
11. The system [200] as claimed in claim 8, wherein the information associated with one or more network nodes [207] comprises at least one of a node name and a list of Service Access Point (SAP) IDs that need to be at least one of: being backed up and being restored.
12. The system [200] as claimed in claim 8, wherein the backup data is stored in the DB [204db] in association with a corresponding SAP ID to allow for precise restoration.
13. The system [200] as claimed in claim 11, wherein the recovery of configuration corresponds to a scheduled backup and restoration of configuration associated with the SAP IDs.
14. The system [200] as claimed in claim 11, wherein the SAP ID is an identifier of a Service Access Point.