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 PERFORMING BULK CONFIGURATION CHANGES OF NETWORK NODES”
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 PERFORMING BULK CONFIGURATION CHANGES OF NETWORK NODES
FIELD OF INVENTION
[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 performing bulk configuration changes of network nodes.
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 (1G) 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] Previous solutions allowed configuration changes only at a single instance level. If one had to change configurations for multiple nodes or instances, it was required to send requests one by one for each instance. This process could be time-consuming and inefficient, especially for large networks. Prior systems did not support batch processing, which would enable multiple configuration changes to be sent simultaneously. This lack of functionality made it difficult to implement changes quickly and could lead to significant delays. In previous solutions, users had trouble tracking the success or failure of their configuration change requests. Without real-time status updates, users could be left in the dark about whether their changes were successfully implemented. If the user wanted to apply the same changes again in the future, they could not reuse the same request sheet, making the process redundant and time-consuming. Responses from nodes, indicating the success or failure of configuration changes, were not stored persistently in the prior systems. This omission might have led to loss of important information and made troubleshooting more challenging. Previously, updated data was not sent to NBI (Northbound Interface) applications. The lack of this integration means that other network management systems could not be easily updated with the changes, leading to inconsistencies, and potentially causing issues in overall network management.
[0005] Therefore, in light of the foregoing discussion, there exists a need to overcome the aforementioned drawbacks and to provide a system and method for performing bulk configuration changes of network nodes.
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 performing bulk configuration changes of network nodes. The method includes receiving, by the transceiver unit a data file, wherein the data file comprises a plurality of configuration change request associated with at least one of a plurality of network nodes, and wherein each of the plurality of configuration change request comprises at least one of a Service Access Point Identifier (SAP-ID) and a parameter name that requires modification. The method further includes parsing, by a processing unit, the data file to check for the plurality of configuration change request based on the SAP-ID and the parameter name. The method furthermore includes sending, by the transceiver unit, the plurality of configuration change request to a corresponding plurality of network nodes based on the SAP-ID and the parameter name. Even further, the method includes receiving, by the transceiver unit, a response from each of the plurality of network nodes indicating a current status of each of the plurality of configuration change request.
[0008] In an exemplary aspect of the present disclosure, each of the plurality of configuration change request further comprises at least one of a data associated with a node type, a software version, a cell number, a parameter type, a parameter category, a parameter value, and a parameter index.
[0009] In another exemplary aspect of the present disclosure, the method further includes storing, by the processing unit, the received response in a repository.
[0010] In yet another exemplary aspect of the present disclosure, the current status of each of the plurality of configuration change request is at least one of a success status, a failure status, and a pending status, based on an implementation of each of the plurality of configuration change request at the corresponding plurality of nodes.

[0011] In yet another exemplary aspect of the present disclosure, the method may further include displaying, by the processing unit via a user interface (UI), the current status of each of the plurality of configuration change request.
[0012] In yet another exemplary aspect of the present disclosure, the method may further include updating, by the processing unit, a configuration data based on the received current status of at least one of the plurality of network nodes.
[0013] In yet another exemplary aspect of the present disclosure, the method may further include transmitting, by the transmitting unit, the updated configuration data to a Northbound Interface (NBI).
[0014] In yet another exemplary aspect of the present disclosure, the method may further include utilising, by the processing unit, a batch mechanism for sending the plurality of configuration change request to the corresponding plurality of network nodes.
[0015] In yet another exemplary aspect of the present disclosure, the batch mechanism is to introduce a configurable delay between each batch of the configuration change requests from the plurality of configuration change request to manage overall load.
[0016] Another aspect of the present disclosure may relate to a system for performing bulk configuration changes of network nodes. The system includes a transceiver unit configured to receive a data file, wherein the data file comprises a plurality of configuration change request associated with at least one of a plurality of network nodes, wherein each of the plurality of configuration change request comprises at least one of a Service Access Point Identifier (SAP-ID) and a parameter name that requires modification. The system further comprises a processing unit connected to at least the transceiver unit, processing unit is

configured to parse the data file to check for the plurality of configuration change request based on the SAP-ID and the parameter name. Further, the transceiver unit is configured to send the plurality of configuration change request to a corresponding plurality of network nodes based on the SAP-ID and the parameter name. Thereafter, the transceiver unit is further configured to receive a response from each of the plurality of network nodes indicating a current status of each of the plurality of configuration change request.
[0017] Yet another aspect of the present disclosure may relate to a User Equipment (UE). The UE may include a memory and a processor coupled to the memory. The processor may be configured to transmit a data file to a system. The data fie may include a plurality of configuration change request associated with at least one of a plurality of network nodes. Each of the plurality of configuration change request may include at least one of a Service Access Point Identifier (SAP-ID) and a parameter name that requires modification. Further, the data file may be used by the system for performing bulk configuration changes of the plurality of network nodes. The system, on receiving the data file, may parse the data file to check for the plurality of configuration change request based on the SAP-ID and the parameter name. The system may then send the plurality of configuration change request to a corresponding plurality of network nodes based on the SAP-ID and the parameter name. Thereafter, the system may receive a response from each of the plurality of network nodes indicating a current status of each of the plurality of configuration change request.
[0018] Yet another aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing instructions for performing bulk configuration changes of network nodes, the instructions include executable code which, when executed by a one or more units of a system, causes: a transceiver unit of the system to receive a data file, wherein the data file comprises a plurality of configuration change request associated with at least one of a plurality of network nodes, wherein each of the plurality of configuration change request comprises at

least one of a Service Access Point Identifier (SAP-ID) and a parameter name that
requires modification. The instructions further include executable code which,
when executed causes a processing unit of the system to parse the data file to check
for the plurality of configuration change request based on the SAP-ID and the
5 parameter name. The instructions further include executable code which, when
executed causes the transceiver unit to: send the plurality of configuration change request to a corresponding plurality of nodes based on the SAP-ID and the parameter name; and to receive a response from each of the plurality of nodes indicating a current status of each of the plurality of configuration change request. 10
OBJECTS OF THE INVENTION
[0019] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below. 15
[0020] It is an object of the present disclosure to provide a system and method for performing bulk configuration changes of network nodes.
[0021] It is another object of the present disclosure to provide a system and method
20 for performing bulk configuration changes of network nodes that allows bulk
configuration changes based on SAP IDs. Instead of making changes one by one, the invention aims to facilitate these alterations in a bulk, more efficient way.
[0022] It is yet another object of the present disclosure to provide a system and
25 method for performing bulk configuration changes of network nodes that simplify
and streamline the process of user requests for configuration changes. It collates all configuration change requests from a user into a single file (files used for spreadsheets or simple formats such as a JSON file, XML file, etc.), thus making it easier to manage and process. 30
7

[0023] It is yet another object of the present disclosure to provide a system and
method for performing bulk configuration changes of network nodes that provides
a user-friendly interface that allows users to track the status of their requests. This
will provide real-time updates on whether the configuration changes have been
5 successful or failed.
[0024] It is yet another object of the present disclosure to provide a system and
method for performing bulk configuration changes of network nodes that seeks to
offer reusability of the configuration change requests. If users want to apply the
10 same changes in the future, they can simply reuse the same data file, making the
process more efficient and less time-consuming.
[0025] It is yet another object of the present disclosure to provide a system and
method for performing bulk configuration changes of network nodes that aims to
15 use persistent storage to save the responses from the respective nodes, improving
data retention and aiding in future troubleshooting or auditing.
[0026] It is yet another object of the present disclosure to provide a system and
method for performing bulk configuration changes of network nodes that plans to
20 use a batch mechanism for sending requests to the nodes, which should increase
efficiency and allow for configurable delays in the batches to better manage network load.
[0027] It is yet another object of the present disclosure to provide a system and
25 method for performing bulk configuration changes of network nodes that send the
updated data to NBI (Northbound Interface) applications. This improves network management by ensuring all systems are updated with the latest changes.
[0028] It is yet another object of the present disclosure to provide a system and
30 method for performing bulk configuration changes of network nodes that increase
8

overall efficiency in managing and modifying network parameters, providing a more effective and user-friendly system for network management.
DESCRIPTION OF THE DRAWINGS
5
[0029] 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,
10 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
15 drawings includes disclosure of electrical components or circuitry commonly used
to implement such components.
[0030] FIG. 1 illustrates an exemplary block diagram representation of 5th generation core (5GC) network architecture. 20
[0031] FIG. 2 illustrates an exemplary block diagram of a computing device upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure.
25 [0032] FIG. 3 illustrates an exemplary block diagram of a system for performing
bulk configuration changes of network nodes, in accordance with exemplary implementations of the present disclosure.
[0033] FIG. 4 illustrates an exemplary method flow diagram for performing bulk
30 configuration changes of network nodes, in accordance with exemplary
implementations of the present disclosure.
9

[0034] FIG. 5 illustrates an exemplary architecture of a system used for performing bulk configuration changes of the plurality of network nodes, in accordance with exemplary implementations of the present disclosure. 5
[0035] FIG. 6 illustrates an exemplary method flow diagram for performing bulk configuration changes of the plurality of network nodes, in accordance with exemplary implementations of the present disclosure.
10 [0036] The foregoing shall be more apparent from the following more detailed
description of the disclosure.
DETAILED DESCRIPTION
15 [0037] 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 details. Several features described hereafter may each be used independently of one
20 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.
[0038] The ensuing description provides exemplary embodiments only, and is not
25 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
30 disclosure as set forth.
10

[0039] 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
5 may be shown as components in block diagram form in order not to obscure the
embodiments in unnecessary detail.
[0040] 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
10 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.
15
[0041] 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
20 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
25 similar to the term “comprising” as an open transition word—without precluding
any additional or other elements.
[0042] As used herein, a “processing unit” or “processor” or “operating processor”
includes one or more processors, wherein processor refers to any logic circuitry for
30 processing instructions. A processor may be a general-purpose processor, a special
purpose processor, a conventional processor, a digital signal processor, a plurality
11

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,
5 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.
[0043] As used herein, “a user equipment”, “a user device”, “a smart-user-device”,
10 “a smart-device”, “an electronic device”, “a mobile device”, “a handheld device”,
“a wireless communication device”, “a mobile communication device”, “a
communication device” may be any electrical, electronic, and/or computing device
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
15 phone, laptop, a general-purpose computer, desktop, personal digital assistant,
tablet computer, wearable device or any other computing device which is capable
of implementing the features of the present disclosure. Also, the user device may
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
20 such unit(s) which are required to implement the features of the present disclosure.
[0044] 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
25 medium includes read-only memory (“ROM”), random access memory (“RAM”),
magnetic disk storage media, optical storage media, flash memory devices or other types of machine-accessible storage media. The storage unit stores at least the data that may be required by one or more units of the system to perform their respective functions.
30
12

[0045] As used herein “interface” or “user interface refers to a shared boundary
across which two or more separate components of a system exchange information
or data. The interface may also be referred to a set of rules or protocols that define
communication or interaction of one or more modules or one or more units with
5 each other, which also includes the methods, functions, or procedures that may be
called.
[0046] All modules, units, components used herein, unless explicitly excluded herein, may be software modules or hardware processors, the processors being a
10 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 circuits (FPGA), any other type of integrated circuits, etc.
15
[0047] 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.
20
[0048] 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 method and system for performing bulk configuration changes of network nodes.
25
[0049] The present disclosure discloses a novel solution that enables functionality of making lots of changes to network nodes all at once. The solution as disclosed by the present disclosure receives a file comprising a bunch of requests for each network node, detailing what needs to be changed and where. Then, the solution
30 reads the file to figure out what needs to be done for each network node. Thereafter,
the solution sends these change requests to each network node based on what needs
13

to be changed. Lastly, it waits to hear back from each network node to see if the changes were successful. This clever method streamlines the process of managing network configurations efficiently and effectively.
5 [0050] 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 architecture (100) includes a user equipment (UE) (102), a radio access network (RAN) (104), an access and mobility management function (AMF) (106), a Session
10 Management Function (SMF) (108), a Service Communication Proxy (SCP) (110),
an Authentication Server Function (AUSF) (112), a Network Slice Specific Authentication and Authorization Function (NSSAAF) (114), a Network Slice Selection Function (NSSF) (116), a Network Exposure Function (NEF) (118), a Network Repository Function (NRF) (120), a Policy Control Function (PCF) (122),
15 a Unified Data Management (UDM) (124), an application function (AF) (126), a
User Plane Function (UPF) (128), a data network (DN) (130), wherein all the components are assumed to be connected to each other in a manner as obvious to the person skilled in the art for implementing features of the present disclosure.
20 [0051] Radio Access Network (RAN) (104) is the part of a mobile
telecommunications system that connects user equipment (UE) (102) to the core network (CN) and provides access to different types of networks (e.g., 5G network). It consists of radio base stations and the radio access technologies that enable wireless communication.
25
[0052] Access and Mobility Management Function (AMF) (106) is a 5G core network function responsible for managing access and mobility aspects, such as UE registration, connection, and reachability. It also handles mobility management procedures like handovers and paging.
30
14

[0053] 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 forwarding and handles IP address allocation and QoS enforcement. 5
[0054] 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. 10
[0055] 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.
15 [0056] 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.
20 [0057] 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.
[0058] Network Exposure Function (NEF) (118) is a network function that exposes
25 capabilities and services of the 5G network to external applications, enabling
integration with third-party services and applications.
[0059] Network Repository Function (NRF) (120) is a network function that acts
as a central repository for information about available network functions and
30 services. It facilitates the discovery and dynamic registration of network functions.
15

[0060] Policy Control Function (PCF) (122) is a network function responsible for policy control decisions, such as QoS, charging, and access control, based on subscriber information and network policies.
5 [0061] Unified Data Management (UDM) (124) is a network function that
centralizes the management of subscriber data, including authentication, authorization, and subscription information.
[0062] Application Function (AF) (126) is a network function that represents
10 external applications interfacing with the 5G core network to access network
capabilities and services.
[0063] User Plane Function (UPF) (128) is a network function responsible for
handling user data traffic, including packet routing, forwarding, and QoS
15 enforcement.
[0064] Data Network (DN) (130) refers to a network that provides data services to user equipment (UE) in a telecommunications system. The data services may include but are not limited to Internet services, private data network related services.
20
[0065] FIG. 2 illustrates an exemplary block diagram of a computing device (200) upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure. In an implementation, the computing device (200) may also implement a method for
25 performing bulk configuration changes of network nodes (506) utilising the system.
In another implementation, the computing device (200) itself implements the method for performing bulk configuration changes of network nodes (506) 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
30 disclosure.
16

[0066] The computing device (200) may include a bus (202) or other
communication mechanism for communicating information, and a hardware
processor (204) coupled with bus (202) for processing information. The hardware
processor (204) may be, for example, a general-purpose microprocessor. The
5 computing device (200) may also include a main memory (206), such as a random-
access memory (RAM), or other dynamic storage device, coupled to the bus (202) for storing information and instructions to be executed by the processor (204). The main memory (206) also may be used for storing temporary variables or other intermediate information during execution of the instructions to be executed by the
10 processor (204). Such instructions, when stored in non-transitory storage media
accessible to the processor (204), render the computing device (200) into a special-purpose machine that is customized to perform the operations specified in the instructions. The computing device (200) further includes a read only memory (ROM) (208) or other static storage device coupled to the bus (202) for storing static
15 information and instructions for the processor (204).
[0067] A storage device (210), such as a magnetic disk, optical disk, or solid-state drive is provided and coupled to the bus (202) for storing information and instructions. The computing device (200) may be coupled via the bus (202) to a
20 display (212), such as a cathode ray tube (CRT), Liquid crystal Display (LCD),
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
25 (204). Another type of user input device may be a cursor controller (216), such as a
mouse, a trackball, or cursor direction keys, for communicating direction information and command selections to the processor (204), and for controlling cursor movement on the display (212). The input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allow
30 the device to specify positions in a plane.
17

[0068] The computing device (200) may implement the techniques described
herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware,
and/or program logic which in combination with the computing device (200) causes
or programs the computing device (200) to be a special-purpose machine.
5 According to one implementation, the techniques herein are performed by the
computing device (200) in response to the processor (204) executing one or more
sequences of one or more instructions contained in the main memory (206). Such
instructions may be read into the main memory (206) from another storage medium,
such as the storage device (210). Execution of the sequences of instructions
10 contained in the main memory (206) causes the processor (204) to perform the
process steps described herein. In alternative implementations of the present disclosure, hard-wired circuitry may be used in place of or in combination with software instructions.
15 [0069] The computing device (200) also may include a communication interface
(218) coupled to the bus (202). The communication interface (218) provides a two-way data communication coupling to a network link (220) that is connected to a local network (222). For example, the communication interface (218) may be an integrated services digital network (ISDN) card, cable modem, satellite modem, or
20 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 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,
25 electromagnetic, or optical signals that carry digital data streams representing
various types of information.
[0070] The computing device (200) can send messages and receive data, including
program code, through the network(s), the network link (220) and the
30 communication interface (218). In the Internet example, a server (230) might
transmit a requested code for an application program through the Internet (228), the
18

ISP (226), the host (224), the local network (222) and the communication interface (218). The received code may be executed by the processor (204) as it is received, and/or stored in the storage device (210), or other non-volatile storage for later execution. 5
[0071] Referring to FIG. 3, an exemplary block diagram of a system (300) for performing bulk configuration changes of network nodes (506), is shown, in accordance with the exemplary implementations of the present disclosure. The system (300) comprises at least one transceiver unit (302) and at least one
10 processing unit (304). In an implementation of the present, disclosure, the system
(300) may also comprise a repository (306). 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
15 shown, however, the system (300) may comprise multiple such units or the system
(300) may comprise any such numbers of said units, as required to implement the features of the present disclosure. The system (300) may in communication with the user device (may also referred herein as a UE). In another implementation, the system (300) may reside in a server or a network entity. In yet another
20 implementation, the system (300) may reside partly in the server/ network entity
and partly in the user device.
[0072] The system (300) is configured for performing bulk configuration changes
of network nodes (506), with the help of the interconnection between the
25 components/units of the system (300).
[0073] It may be noted that as used herein “network node” may be interchangeably used with “node”, and shall be considered to be related to each other.
30 [0074] In a preferred implementation of the present disclosure as disclosed herein,
the transceiver unit (302) may receive a data file. The data file may include a
19

plurality of configuration change request associated with at least one of a plurality of network nodes (506). In one example, the data file may be a text file, which may indicate a list of configuration change requests associated with the plurality of network nodes (506). 5
[0075] In one example, a network administrator may create the data file. In such case, the network administrator may be operating a User Equipment (UE) and the data file may be created using the UE.
10 [0076] In another example, the UE, operated by the network administrator, may
receive a plurality of configuration change requests associated with and from a
plurality of network nodes. On receiving the plurality of configuration change
requests, the network administrator may create the data file. Thereafter, using the
UE, the network administrator may transmit the data file to the system (300).
15
[0077] In yet another example, each of the plurality of nodes in the network i.e.,
network nodes (506) may transmit their respective requested configuration changes
to a centralized server, and the centralized server may thereafter aggregate the
received configuration requests from each of the network nodes (506). Based on a
20 Service Access Point Identifier (SAP-ID) of the respective network nodes (506),
the server may then create a data file, which may then be transmitted to the system
(300).
[0078] However, it may be noted that all such examples of creation and
25 transmission of the data file are exemplary, and not to be construed to limit the
scope of the present subject matter. Any other techniques or system known to a person skilled in the art may be used for creating and transmitting the data file to the system (300).
30 [0079] The configuration change request may further include at least one of a
Service Access Point Identifier (SAP-ID) and a parameter name that requires modification. In one example, the configuration change request may further include
20

at least one of a data associated with a node type, a software version, a cell number,
a parameter type, a parameter category, a parameter value, and a parameter index.
However, it may be noted that the aforementioned examples of the data fields
included within the configuration change request are only exemplary and not to be
5 construed to limit the scope of the present subject matter in any manner. Any other
examples of data field may also be included and will lie within the scope of the
present subject matter. The cell number may refer to a number or an identifier used
for identification of each cell. The network node may have multiple cells for
different frequency bands, and the cell number is used for identification of such
10 cells. For example, there may be 3 cells in the 3500 band, and 3 cells in the 700
band, the cell number would help in identifying the cell which may be further used for implementation of the present disclosure.
[0080] An exemplary description of such data fields has been provided below. It
15 may be again noted that such data fields and their corresponding descriptions are
only exemplary, and in no manner are to limit the scope of the present subject matter.
[0081] SAP-ID (Service Access Point Identifier): SAP-ID is a unique identifier
20 for each network node. The SAP-ID is used to determine the network node at which
a particular configuration change request is sent. Each row in the data file would contain a different SAP-ID for each different network node that is required to be configured.
25 [0082] Node Type: Node type is the type or category of the network node that is
being configured. Node type may be a router, a switch, a base transceiver station (BTS), in the case of a telecommunication network, and may also be any other type of nodes that is being utilized by the network of the system.
30 [0083] Software Version: The software version indicates a version of the software
or a firmware that the particular network node is currently running on. Different
21

software versions might have different available parameters and compatibility, thereby making it crucial to specify this.
[0084] Cell number: The cell number signifies a specific reference number or a
5 code related to the network configuration, such as a change request number. This
will vary depending on the specific systems and processes that are used by the organization.
[0085] Parameter Type (Scalar/Tabular): The parameter type denotes the type of
10 parameter that is being changed. Scalar parameters are single values (like turning a
feature on or off), while tabular parameters might involve multiple related values (like a list of server addresses for the node to connect to).
[0086] Parameter Category: Parameter category may refer to a broader category
15 that the parameter falls into. For example, if the parameter that is being changed is
say a transmission power, the category might be a power setting.
[0087] Parameter Value: The parameter value is the new value that is required to
be set for the parameter. For example, in case of changing transmission power, the
20 parameter value might be the new power level that is required to be sent.
[0088] Parameter Name and Index: The parameter name and index may refer to
the specific name of the parameter that is required to be changed, along with its
index if applicable. For example, the parameter name may be a Transmission Power,
25 and if it is in a tabular parameter, then the parameter index would specify the row
of the table that is being changed.
[0089] Continuing further with the preferred implementation, the processing unit
(304) may then parse the data file to check for the plurality of configuration change
30 request based on the SAP-ID and the parameter name. Any technique known to a
person skilled in the art may be used for parsing the data file. Such techniques have not been explained here for the sake of brevity.
22

[0090] Continuing further with the preferred implementation, the transceiver unit
(302) may then send the plurality of configuration change request to a
corresponding plurality of nodes based on the SAP-ID and the parameter name. For
5 example, corresponding to each of the SAP-IDs associated with the corresponding
nodes, the transceiver unit (302) may send the configuration change requests that
may be mapped to the respective SAP-IDs. In one example, the processing unit
(304) may utilise a batch mechanism for sending the plurality of configuration
change request to the corresponding plurality of nodes. As would be appreciated,
10 such batch mechanism may introduce a configurable delay between each batch of
the configuration change requests from the plurality of configuration change request to manage overall load on a system. In one example, the system may be a Network management system (NMS).
15 [0091] Upon sending the configuration change requests to the corresponding
plurality of nodes, the same may then be implemented at the respective nodes. It may be the case that the configuration change request may be successfully implemented at the respective node, thereby causing a change in at least one of the configurations of the respective node. In another example, it may also be the case
20 that the implementation of the said request may fail, thereby not being able to
change the required configuration of the respective node.
[0092] Continuing further with the preferred implementation, the transceiver unit (302) may then receive a response from each of the plurality of nodes. The response
25 may indicate a current status of each of the plurality of configuration change
request. In one example the current status of each of the plurality of configuration change request is at least one of a success status, a failure status, and a pending status based on an implementation of each of the plurality of configuration change request at the corresponding plurality of nodes. In another example, the system may
30 include a display device (not shown in FIG. 3) communicatively coupled to the
system (300). In yet another example, the system may include a user interface (UI).
23

In such cases, the processing unit (304) may cause to display the current status of each of the plurality of configuration change request through the UI.
[0093] In yet another example, in cases where the current status indicates that the
5 configuration change request has been failed, the transceiver unit (302) may resend
the configuration change request to the corresponding node.
[0094] Continuing further, in yet another example, based on the received current status of at least one of the plurality of nodes, the processing unit (304) may further
10 update a configuration data. For example, in the cases where the configuration
change request has been successfully implemented, the processing unit (304) may update the configuration data based on the successful acknowledgement and the request which was sent. Such updated configuration data, in one example, may be transmitted to a Northbound Interface (NBI). In another example, the updated
15 configuration data may be transmitted to the NBI through a message stream. As
would be understood, the Northbound Interface is a part of the network management system (NMS) that communicates with higher-level systems.
[0095] In one example, the processing unit (304) may thereafter store the received
20 response in a repository (306). In another example, the repository (306) may be a
database managed by the network administrator. In yet another example, the
repository (306) may be implemented on non-volatile memory within or in
communication with the system, also referred to as persistent storage. However, the
repository (306) may be implemented as any other data repository (306) as may be
25 known to a person skilled in the art. All such examples would be covered within the
scope of the present subject matter. As would be further appreciated, such stored
received responses may allow the network management system to track the status
of each configuration request, which in turn may be used by the network
administrator.
30
24

[0096] Referring to FIG. 4, an exemplary method flow diagram (400) for
performing bulk configuration changes of network nodes (506), 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 an
5 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).
[0097] At step 404, the method comprises receiving, by a transceiver unit (302), a
10 data file, wherein the data file comprises a plurality of configuration change request
associated with at least one of a plurality of network nodes (506), and wherein each of the plurality of configuration change request comprises at least one of a Service Access Point Identifier (SAP-ID) and a parameter name that requires modification.
15 [0098] The data file may include a plurality of configuration change request
associated with at least one of a plurality of network nodes (506). In one example, the data file may be a text file, which may indicate a list of configuration change requests associated with the plurality of network nodes (506).
20 [0099] In one example, a network administrator may create the data file. In such
case, the network administrator may be operating a User Equipment (UE) and the data file may be created using the UE.
[0100] In another example, the UE, operated by the network administrator, may
25 receive a plurality of configuration change requests associated with and from a
plurality of network nodes. On receiving the plurality of configuration change requests, the network administrator may create the data file. Thereafter, using the UE, the network administrator may transmit the data file to the system (300).
30 [0101] In yet another example, each of the plurality of nodes in the network i.e.,
network nodes (506) may transmit their respective requested configuration changes to a centralized server, and the centralized server may thereafter aggregate the
25

received configuration requests from each of the network nodes (506). Based on a
Service Access Point Identifier (SAP-ID) of the respective network nodes (506),
the server may then create a data file, which may then be transmitted to the system
(300).
5
[0102] However, it may be noted that all such examples of creation and
transmission of the data file are exemplary, and not to be construed to limit the
scope of the present subject matter. Any other techniques or system known to a
person skilled in the art may be used for creating and transmitting the data file to
10 the system (300).
[0103] The configuration change request may further include at least one of a Service Access Point Identifier (SAP-ID) and a parameter name that requires modification. In one example, the configuration change request may further include
15 at least one of a data associated with a node type, a software version, a cell number,
a parameter type, a parameter category, a parameter value, and a parameter index. However, it may be noted that the aforementioned examples of the data fields included within the configuration change request are only exemplary and not to be construed to limit the scope of the present subject matter in any manner. Any other
20 examples of data field may also be included and will lie within the scope of the
present subject matter. The cell number may refer to a number or an identifier used for identification of each cell. The network node may have multiple cells for different frequency bands, and the cell number is used for identification of such cells. For example, there may be 3 cells in the 3500 band, and 3 cells in the 700
25 band, the cell number would help in identifying the cell which may be further used
for implementation of the present disclosure.
[0104] An exemplary description of such data fields has been provided below. It
may be again noted that such data fields and their corresponding descriptions are
30 only exemplary, and in no manner are to limit the scope of the present subject
matter.
26

[0105] SAP-ID (Service Access Point Identifier): SAP-ID is a unique identifier
for each network node. The SAP-ID is used to determine the network node at which
a particular configuration change request is sent. Each row in the data file would
5 contain a different SAP-ID for each different network node that is required to be
configured.
[0106] Node Type: Node type is the type or category of the network node that is
being configured. Node type may be a router, a switch, a base transceiver station
10 (BTS), in the case of a telecommunication network, and may also be any other type
of nodes that is being utilized by the network of the system.
[0107] Software Version: The software version indicates a version of the software
or a firmware that the particular network node is currently running on. Different
15 software versions might have different available parameters and compatibility,
thereby making it crucial to specify this.
[0108] Cell number: The cell number signifies a specific reference number or a
code related to the network configuration, such as a change request number. This
20 will vary depending on the specific systems and processes that are used by the
organization.
[0109] Parameter Type (Scalar/Tabular): The parameter type denotes the type of
parameter that is being changed. Scalar parameters are single values (like turning a
25 feature on or off), while tabular parameters might involve multiple related values
(like a list of server addresses for the node to connect to).
[0110] Parameter Category: Parameter category may refer to a broader category
that the parameter falls into. For example, if the parameter that is being changed is
30 say a transmission power, the category might be a power setting.
27

[0111] Parameter Value: The parameter value is the new value that is required to be set for the parameter. For example, in case of changing transmission power, the parameter value might be the new power level that is required to be sent.
5 [0112] Parameter Name and Index: The parameter name and index may refer to
the specific name of the parameter that is required to be changed, along with its index if applicable. For example, the parameter name may be a Transmission Power, and if it is in a tabular parameter, then the parameter index would specify the row of the table that is being changed.
10
[0113] At step 406, the method comprises parsing, by a processing unit (304), the data file to check for the plurality of configuration change request based on the SAP-ID and the parameter name. For instance, the processing unit (304) may then parse the data file to check for the plurality of configuration change request based
15 on the SAP-ID and the parameter name. Any technique known to a person skilled
in the art may be used for parsing the data file. Such techniques have not been explained here for the sake of brevity.
[0114] At step 408, the method comprises sending, by the transceiver unit (302),
20 the plurality of configuration change request to a corresponding plurality of nodes
based on the SAP-ID and the parameter name. For instance, the transceiver unit
(302) may then send the plurality of configuration change request to the
corresponding plurality of nodes based on the SAP-ID and the parameter name. For
instance, corresponding to each of the SAP-IDs associated with the corresponding
25 nodes, the transceiver unit (302) may send the configuration change requests that
may be mapped to the respective SAP-IDs. In one example, the processing unit
(304) may utilise a batch mechanism for sending the plurality of configuration
change request to the corresponding plurality of nodes. As would be appreciated,
such batch mechanism may introduce a configurable delay between each batch of
30 the configuration change requests from the plurality of configuration change
28

request to manage overall load on a system. In one example, the system may be a Network management system (NMS).
[0115] Upon sending the configuration change requests to the corresponding
5 plurality of nodes, the same may then be implemented at the respective nodes. It
may be the case that the configuration change request may be successfully
implemented at the respective node, thereby causing a change in at least one of the
configurations of the respective node. In another example, it may also be the case
that the implementation of the said request may fail, thereby not being able to
10 change the required configuration of the respective node.
[0116] At step 410, the method comprises receiving, by the transceiver unit (302), a response from each of the plurality of nodes indicating a current status of each of the plurality of configuration change request. For example, the transceiver unit
15 (302) may then receive a response from each of the plurality of nodes. The response
may indicate the current status of the configuration change request. In one example, the current status of each of the plurality of configuration change request is at least one of a success status, a failure status, and a pending status based on an implementation of each of the plurality of configuration change request at the
20 corresponding plurality of nodes. In another example, the system may include a
display device (not shown in FIG. 3) communicatively coupled to the system. In yet another example, the system may include a user interface (UI). In such cases, the processing unit (304) may cause to display the current status of each of the plurality of configuration change request through the UI.
25
[0117] In yet another instance, in cases where the current status indicates that the configuration change request has been failed, the transceiver unit (302) may resend the configuration change request to the corresponding node.
30 [0118] Continuing further, in yet another instance, based on the received current
status of at least one of the plurality of nodes, the processing unit (304) may further
29

update a configuration data. For example, in the cases where the configuration
change request has been successfully implemented, the processing unit (304) may
update the configuration data based on the successful acknowledgement and the
request which was sent. Such updated configuration data, in one example, may be
5 transmitted to a Northbound Interface (NBI). In another example, the updated
configuration data may be transmitted to the NBI through a message stream. As would be understood, the Northbound Interface is a part of the network management system (NMS) that communicates with higher-level systems.
10 [0119] In one instance, the processing unit (304) may thereafter store the received
response in a repository (306). In another example, the repository (306) may be a database managed by the network administrator. In yet another example, the repository (306) may be implemented on non-volatile memory within or in communication with the system, also referred to as persistent storage. However, the
15 repository (306) may be implemented as any other data repository (306) as may
beknown to a person skilled in the art. All such examples would be covered within the scope of the present subject matter. As would be further appreciated, such stored received responses may allow the network management system to track the status of each configuration request, which in turn may be used by the network
20 administrator.
[0120] Referring to FIG. 5, an exemplary architecture of a system (500) used for
performing bulk configuration changes of the plurality of network nodes (506) is
illustrated. The system (500) comprises at least one repository (306), at least one
25 user interface (502), at least one configuration management module (504), at least
one network node (506), at least one streaming component (508), and at least one north bound interface (510).
[0121] The repository (306) may refer to a database or a storage used for storing
30 information associated with the management of the telecommunication networks.
30

[0122] The user interface (502) may refer to an interface used as a point of interaction between a user (such as a network administrator) and a device (such as User Equipment) used by the user.
5 [0123] The configuration management module (504) may refer to a module used
for management of the configuration associated with one or more network nodes
(506) present in the telecommunication network. For example, the configuration
management module (504) may be used for management of configurations of the
software or firmware that are being used by the one or more network nodes (506)
10 for their functioning. The configuration management module (504) may for
example, send request to the one or more network nodes (506) for performing certain functions.
[0124] The network node (506) may refer to the device used as the endpoints for
15 transmissions and redistribution of data. The network node (506) from the one or
more network nodes (506) may send data based on the request received from the
configuration management module (504). The network node (506) may store a
response (which may be a success or a failure response) of the request received
from the configuration management module (504), in the repository (306).
20
[0125] The streaming component (508) may refer to the component used for
streaming the data sent by the network node (506) to the northbound interface (510).
[0126] The Northbound Interface (NBI) (510) is a part of the network management
25 system that communicates with higher-level systems. The NBI acts as an interface
between the higher-level system and the network management system. The NBI interface (510) may also be a northbound interface (510).
[0127] Referring to FIG. 6, an exemplary method flow diagram (600) for
30 performing bulk configuration changes of the plurality of network nodes, in
accordance with exemplary implementations of the present disclosure is shown. In
an implementation the method (600) is performed by the system (300). Further, in
31

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. 6, the method (600) starts at step (602).
5 [0128] At step (604), the method comprises receiving a data file, wherein the data
file comprises a plurality of configuration change request associated with at least one of a plurality of network nodes, and wherein each of the plurality of configuration change request comprises at least one of a Service Access Point Identifier (SAP-ID) and a parameter name that requires modification.
10
[0129] The data file may include a plurality of configuration change request associated with at least one of a plurality of network nodes. In one example, the data file may be a text file, which may indicate a list of configuration change requests associated with the plurality of network nodes.
15
[0130] In one example, a network administrator may create the data file. In such case, the network administrator may be operating a User Equipment (UE) and the data file may be created using the UE.
20 [0131] In another example, the UE, operated by the network administrator, may
receive a plurality of configuration change requests associated with and from a
plurality of network nodes. On receiving the plurality of configuration change
requests, the network administrator may create the data file. Thereafter, using the
UE, the network administrator may transmit the data file to the system (300).
25
[0132] In yet another example, each of the plurality of nodes in the network i.e.,
network nodes (506) may transmit their respective requested configuration changes
to a centralized server, and the centralized server may thereafter aggregate the
received configuration requests from each of the network nodes (506). Based on a
30 Service Access Point Identifier (SAP-ID) of the respective network nodes (506),
the server may then create a data file, which may then be transmitted to the system
(300).
32

[0133] However, it may be noted that all such examples of creation and
transmission of the data file are exemplary, and not to be construed to limit the
scope of the present subject matter. Any other techniques or system known to a
5 person skilled in the art may be used for creating and transmitting the data file to
the system (300).
[0134] The configuration change request may further include at least one of a Service Access Point Identifier (SAP-ID) and a parameter that requires
10 modification. In one example, the configuration change request may further include
at least one of a data associated with a node type, a software version, a cell number, a parameter type, a parameter category, a parameter value, and a parameter index. However, it may be noted that the aforementioned examples of the data fields included within the configuration change request are only exemplary and not to be
15 construed to limit the scope of the present subject matter in any manner. Any other
examples of data field may also be included and will lie within the scope of the present subject matter. The cell number may refer to a number or an identifier used for identification of each cell. The network node (506) may have multiple cells for different frequency bands, and the cell number is used for identification of such
20 cells. For example, there may be 3 cells in the 3500 band, and 3 cells in the 700
band, the cell number would help in identifying the cell which may be further used for implementation of the present disclosure.
[0135] At step 606, the method comprises validating the data file. The data file may
25 be validated by parsing the data file to check for the plurality of configuration
change request based on the SAP-ID and the parameter name. For instance, the
processing unit (304) may then parse the data file to check for the plurality of
configuration change request based on the SAP-ID and the parameter name. Any
technique known to a person skilled in the art may be used for parsing the data file.
30 Such techniques have not been explained here for the sake of brevity.
33

[0136] At step 608, the method comprises sending the data file and at step 610, the
method then comprises sending the plurality of configuration change request to a
corresponding plurality of nodes based on the SAP-ID and the parameter name. For
instance, the transceiver unit (302) may then send the plurality of configuration
5 change request to the corresponding plurality of nodes based on the SAP-ID and
the parameter name. For instance, corresponding to each of the SAP-IDs associated with the corresponding nodes, the transceiver unit (302) may send the configuration change requests that may be mapped to the respective SAP-IDs. In one example, the processing unit (304) may utilise a batch mechanism for sending the plurality
10 of configuration change request to the corresponding plurality of nodes. As would
be appreciated, such batch mechanism may introduce a configurable delay between each batch of the configuration change requests from the plurality of configuration change request to manage overall load on a system. In an example the system may be a Network management system (NMS).
15
[0137] Upon sending the configuration change requests to the corresponding plurality of nodes, the same may then be implemented at the respective nodes. It may be the case that the configuration change request may be successfully implemented at the respective node, thereby causing a change in at least one of the
20 configurations of the respective node. In another example, it may also be the case
that the implementation of the said request may fail, thereby not being able to change the required configuration of the respective node.
[0138] In an implementation, the method comprises receiving a response from each
25 of the plurality of nodes indicating a current status of each of the plurality of
configuration change request. For example, the transceiver unit (302) may then
receive a response from each of the plurality of nodes. The response may indicate
the current status of the configuration change request. In one example, the current
status of each of the plurality of configuration change request is at least one of a
30 success status, a failure status, and a pending status based on an implementation
each of the plurality of configuration change request at the corresponding plurality
34

of nodes. In another example, the system may include a display device (not shown
in FIG. 3) communicatively coupled to the system. In yet another example, the
system when includes a user interface (UI), then the processing unit (304) may
cause to display the current status of each of the plurality of configuration change
5 request through the UI.
[0139] In yet another instance, in cases where the current status indicates that the configuration change request has been failed, the transceiver unit (302) may resend the configuration change request to the corresponding node.
10
[0140] Continuing further, at step (610), the method further comprises updating a configuration data, based on the received current status of at least one of the plurality of nodes. For example, in the cases where the configuration change request has been successfully implemented, the processing unit (304) may update the
15 configuration data based on the successful acknowledgement and the request which
was sent. Such updated configuration data, in one example, may be transmitted to a Northbound Interface (NBI). In another example, the updated configuration data may be transmitted to the NBI through a message stream. As would be understood, the Northbound Interface is a part of the network management system that
20 communicates with higher-level systems.
[0141] Thereafter, the method (600) further comprises storing the received response in a repository (306). In another example, the repository (306) may be a database managed by the network administrator. In yet another example, the
25 repository (306) may be implemented on non-volatile memory within or in
communication with the system, also referred to as persistent storage. However, the repository (306) may be implemented as any other data repository (306) as may be known to a person skilled in the art. All such examples would be covered within the scope of the present subject matter. As would be further appreciated, such stored
30 received responses may allow the network management system to track the status
35

of each configuration request, which in turn may be used by the network administrator.
[0142] Thereafter, at step (614), the method (600) is terminated. 5
[0143] The present disclosure further discloses a User Equipment (UE). The UE may include a memory and a processor coupled to the memory. The processor may be configured to transmit a data file to a system. The data fie may include a plurality of configuration change request associated with at least one of a plurality of network
10 nodes. Each of the plurality of configuration change request may include at least
one of a Service Access Point Identifier (SAP-ID) and a parameter name that requires modification. Further, the data file may be used by the system for performing bulk configuration changes of the plurality of network nodes. The system, on receiving the data file, may parse the data file to check for the plurality
15 of configuration change request based on the SAP-ID and the parameter name. The
system may then send the plurality of configuration change request to a corresponding plurality of network nodes based on the SAP-ID and the parameter name. Thereafter, the system may receive a response from each of the plurality of network nodes indicating a current status of each of the plurality of configuration
20 change request.
[0144] The present disclosure furthermore discloses a non-transitory computer readable storage medium storing instructions for performing bulk configuration changes of network nodes, the instructions include executable code which, when
25 executed by a one or more units of a system, causes: a transceiver unit (302) of the
system to receive a data file, wherein the data file comprises a plurality of configuration change request associated with at least one of a plurality of network nodes, and wherein each of the plurality of configuration change request comprises at least one of a Service Access Point Identifier (SAP-ID) and a parameter name
30 that requires modification. The instructions further include executable code which,
when executed causes a processing unit (304) of the system to parse the data file to
36

check for the plurality of configuration change request based on the SAP-ID and
the parameter name. The instructions further include executable code which, when
executed causes the transceiver unit (302) to: send the plurality of configuration
change request to a corresponding plurality of nodes based on the SAP-ID and the
5 parameter name; and to receive a response from each of the plurality of nodes
indicating a current status of each of the plurality of configuration change request.
[0145] As is evident from the above, the present disclosure provides a technically advanced solution for performing bulk configuration changes of network nodes.
10 The present solution enhances the bulk set request feature for greater efficiency and
effectiveness in network management. The present disclosure disclosed a novel solution for performing bulk configuration changes of network nodes that allows bulk configuration changes based on SAP IDs. Instead of making changes one by one, the invention aims to facilitate these alterations in a bulk, more efficient way.
15 Further, the solution of the present disclosure provides technical effect by
simplifying and streamlining the process of user requests for configuration changes and by collating all configuration change requests from a user into a single file (files used for spreadsheets or simple formats such as a JSON file, XML file, etc.), thus making it easier to manage and process. The solution of as disclosed herein provides
20 a user-friendly interface that allows users to track the status of their requests. This
will provide real-time updates on whether the configuration changes have been successful or failed. Further, the present solution seeks to offer reusability of the configuration change requests. If users want to apply the same changes in the future, they can simply reuse the same file (files used for spreadsheets such as a JSON file,
25 XML file, etc.), making the process more efficient and less time-consuming, and
aims to use persistent storage to save the responses from the respective nodes, improving data retention and aiding in future troubleshooting or auditing. Furthermore, the solution of as disclosed herein plans to use a batch mechanism for sending requests to the nodes, which should increase efficiency and allow for
30 configurable delays in the batches to better manage network load and send the
updated data to NBI (Northbound Interface) applications which improves network
37

management by ensuring all systems are updated with the latest changes. Also, the present solution increases overall efficiency in managing and modifying network parameters, providing a more effective and user-friendly system for network management. 5
[0146] While considerable emphasis has been placed herein on the disclosed
embodiments, it will be appreciated that many embodiments can be made and that
many changes can be made to the embodiments without departing from the
principles of the present disclosure. These and other changes in the embodiments
10 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.
[0147] Further, in accordance with the present disclosure, it is to be acknowledged
15 that the functionality described for the various components/units can be
implemented interchangeably. While specific embodiments may disclose a
particular functionality of these units for clarity, it is recognized that various
configurations and combinations thereof are within the scope of the disclosure. The
functionality of specific units as disclosed in the disclosure should not be construed
20 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.
38

We Claim:
1. A method (400) for performing bulk configuration changes of a plurality of
network nodes, the method (400) comprising the steps of:
receiving (404), by a transceiver unit (302), a data file, wherein the data file comprises a plurality of configuration change request associated with at least one of a plurality of network nodes (506), and wherein each of the plurality of configuration change request comprises at least one of a Service Access Point Identifier (SAP-ID) and a parameter name that requires modification;
parsing (406), by a processing unit (304), the data file to check for the plurality of configuration change request based on the SAP-ID and the parameter name;
sending (408), by the transceiver unit (302), the plurality of configuration change request to a corresponding plurality of network nodes (506) based on the SAP-ID and the parameter name; and
receiving (410), by the transceiver unit (302), a response from each of the plurality of network nodes (506) indicating a current status of each of the plurality of configuration change request.
2. The method (400) as claimed in claim 1, wherein each of the plurality of configuration change request further comprises at least one of a data associated with a node type, a software version, a cell number, a parameter type, a parameter category, a parameter value, and a parameter index.
3. The method (400) as claimed in claim 1, wherein the method further comprises storing, by the processing unit (304), the received response in a repository (306).
4. The method (400) as claimed in claim 1, wherein the current status of each of the plurality of configuration change request is at least one of a success status, a failure status, and a pending status, based on an implementation of each of the

plurality of configuration change request at the corresponding plurality of network nodes (506).
5. The method (400) as claimed in claim 1, wherein the method further comprises displaying, by the processing unit (304) via a user interface (UI), the current status of each of the plurality of configuration change request.
6. The method (400) as claimed in claim 1, wherein the method further comprises updating, by the processing unit (304), a configuration data based on the received current status of at least one of the plurality of network nodes (506).
7. The method (400) as claimed in claim 6, wherein the method further comprises transmitting, by the transceiver unit (302), the updated configuration data to a Northbound Interface (NBI).
8. The method (400) as claimed in claim 1, wherein the method further comprises utilising, by the processing unit (304), a batch mechanism for sending the plurality of configuration change request to the corresponding plurality of network nodes (506).
9. The method (400) as claimed in claim 8, wherein the batch mechanism is to introduce a configurable delay between each batch of the configuration change requests from the plurality of configuration change request to manage overall load.
10. A system (300) for performing bulk configuration changes of a plurality of network nodes (506), the system (300) comprising:
- a transceiver unit (302) configured to receive a data file, wherein the data file comprises a plurality of configuration change request associated with at least one of a plurality of network nodes (506), wherein each of the plurality of configuration change request comprises at least one of a Service Access

Point Identifier (SAP-ID) and a parameter name that requires modification; and - a processing unit (304) connected to at least the transceiver unit (302), wherein the processing unit (304) is configured to parse the data file to check for the plurality of configuration change request based on the SAP¬ID and the parameter name;
wherein the transceiver unit (302) is further configured to:
send the plurality of configuration change request to a corresponding plurality of nodes based on the SAP-ID and the parameter name, and
receive a response from each of the plurality of nodes indicating a current status of each of the plurality of configuration change request.
11. The system (300) as claimed in claim 10, wherein each of the plurality of configuration change request further comprises at least one of a data associated with a node type, a software version, a cell number, parameter type, a parameter category, a parameter value, and a parameter index.
12. The system (300) as claimed in claim 10, wherein the processing unit (304) is further configured to store the received response in a repository (306).
13. The system (300) as claimed in claim 10, wherein the current status of each of the plurality of configuration change request is at least one of a success status, a failure status, and a pending status based on an implementation of each of the plurality of configuration change request at the corresponding plurality of network nodes (506).
14. The system (300) as claimed in claim 10, wherein the processing unit (304) is further configured to display, via a user interface (UI), the current status of each of the plurality of configuration change request.

15. The system (300) as claimed in claim 10, wherein the processing unit (304) is further configured to update a configuration data based on the received current status of at least one of the plurality of network nodes (506).
16. The system (300) as claimed in claim 15, wherein the transceiver unit (302) is further configured to transmit the updated configuration data to a Northbound Interface (NBI).
17. The system (300) as claimed in claim 10, wherein the processing unit (304) is further configured to utilise a batch mechanism for sending the plurality of configuration change request to the corresponding plurality of nodes.
18. The system (300) as claimed in claim 17, wherein the batch mechanism is to introduce a configurable delay between each batch of the configuration change requests from the plurality of configuration change request to manage overall load.
19. A User Equipment (UE) comprising:
a memory; and
a processor coupled to the memory, wherein the processor is configured to: transmit a data file, comprising a plurality of configuration change request associated with at least one of a plurality of network nodes, to a system (300), wherein each of the plurality of configuration change request comprises at least one of a Service Access Point Identifier (SAP-ID) and a parameter name that requires modification, and wherein the data file is used by the system (300) for performing bulk configuration changes of the plurality of network nodes based on:
on receiving the data file, parsing, by the system (300), the data file to check for the plurality of configuration change request based on the SAP-ID and the parameter name;

sending, by the system (300), the plurality of configuration change request to a corresponding plurality of network nodes (506) based on the SAP-ID and the parameter name; and
receiving, by the system (300), a response from each of the plurality of network nodes indicating a current status of each of the plurality of configuration change request.