System and method for network node configuration management

Abstract

The present disclosure provides a system and method for network node configuration management. The system comprises a memory and one or more processors configured to execute instructions for receiving a configuration change request related to a network node from at least one user equipment. Further, the system is configured for creating a workorder in response to the received request, assigning at least one status to the created workorder, and triggering execution of the created workorder. Further, the system is configured for dynamically updating the status of the created workorder based on the execution and managing the network node configuration based on the dynamically updated status. The system enables efficient tracking, execution, and management of configuration changes in network nodes, particularly in radio access networks, thereby improving network performance and reliability.

Description

SYSTEM AND METHOD FOR NETWORK NODE CONFIGURATION MANAGEMENTRESERVATION OF RIGHTS

[0001] A portion of the disclosure of this patent document contains material, which is subject to intellectual property rights such as, but are not limited to, copyright, design, trademark, Integrated Circuit (IC) layout design, and / or trade dress protection, belonging to Jio Platforms Limited (JPL) or its affiliates (hereinafter referred as owner). The owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all rights whatsoever. All rights to such intellectual property are fully reserved by the owner.FIELD OF THE DISCLOSURE

[0002] The present disclosure relates generally to the field of telecommunications. More particularly, the present disclosure relates to a system and a method for a network node configuration management.DEFINITION

[0003] As used in the present disclosure, the following terms are generally intended to have the meaning as set forth below, except to the extent that the context in which they are used to indicate otherwise.

[0004] Workorder refers to a task or set of tasks created in response to a configuration change request for a network node, which includes details of the requested changes and tracks the progress of the configuration change process. A configuration change request for a network node or a RAN (Radio Access Network) nodes may refer to a formal request to modify the operational parameters, settings, or software configurations of one or more RAN elements, such as base stations (gNB, eNB), Remote Radio Units (RRUs), Centralized Units (CUs), Distributed Units (DUs), or small cells.

[0005] Long term evolution (LTE) operations manager for radio network (also referred to as operations manager) refers to a component responsible for managing and implementing configuration changes in a network node, specifically a radio access network (RAN) node.

[0006] Elastic load balancer (ELB) refers to a component that distributes incoming configuration change requests among multiple operations managers to optimize performance and resource utilization.

[0007] Superset dashboard refers to a user interface that displays consolidated information about workorders, including their statuses and other relevant parameters.

[0008] Service scheduler refers to a component that plans and organizes the execution of services related to network node configuration changes.

[0009] Service execution engine refers to a component that carries out the scheduled services for implementing configuration changes.

[0010] Service monitoring and status update engine refers to a component that tracks the progress of executed services and updates the status of workorders accordingly.

[0011] Distributed file system refers to a distributed storage system used in conjunction with the database to store and process data related to workorders and configuration changes.BACKGROUND OF THE DISCLOSURE

[0012] The following description of 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 be used onlyto enhance the understanding of the reader with respect to the present disclosure, and not as admissions of prior art.

[0013] Wireless communication technology has undergone rapid evolution over the past few decades, progressing from first-generation analog voice services to the current fifth-generation (5G) technology. This progression has been marked by significant advancements in data speeds, network coverage, and service capabilities. As 5G technology continues to be deployed, it promises even faster data speeds, lower latency, and the ability to connect multiple devices simultaneously.

[0014] The radio access network (RAN), a critical component of mobile network infrastructure, has become increasingly complex to meet these advancing technological demands. RANs now must support higher speeds, manage increased interconnected units, and integrate various sub-networks. This complexity is further compounded by the diverse types of data that users now transmit simultaneously, including text, voice, video, and multimedia files.

[0015] The configuration of telecommunications nodes, particularly RAN nodes, plays a crucial role in delivering services to customers. These nodes can be configured in various ways to provide specific calling features or data service levels. However, the dynamic nature of network services necessitates frequent changes to node configurations, either due to newly added services or periodic firmware updates.

[0016] In both new and existing communication networks, a significant challenge lies in efficiently managing these configuration changes while maintaining optimal network performance. Traditional methods for monitoring and implementing telecommunications node configuration changes often require substantial manual effort from telecom operators. This manual approach is not only time-consuming but also prone to errors, potentially leading to network performance degradation.

[0017] Furthermore, identifying the root causes of performance issues in complex RANs has become increasingly difficult with conventional techniques. The inability to accurately detect and address these issues in a timely manner can result in suboptimal network performance and decreased user satisfaction.

[0018] Conventional systems and methods face difficulty in efficiently tracking, implementing, and monitoring configuration changes across multiple RAN nodes while maintaining real-time visibility into the status of these changes. There is, therefore, a need in the art to provide a method and a system that can overcome the shortcomings of the existing prior arts by automating the configuration change process, providing real-time status updates, and optimizing the performance of radio access networks.SUMMARY OF THE DISCLOSURE

[0019] In an exemplary embodiment, a system for network node configuration management is described. The system includes receiving, by a request processing module, a configuration change request related to a network node . A workorder management module creates a workorder in response to the received configuration change request. The workorder management module further assigns at least one status to the created workorder. An execution module triggers an execution of the created workorder. A monitoring and status update module dynamically updates the at least one status of the created workorder based on the execution. A node configuration module manages the network node configuration based on the dynamically updated at least one status of the created workorder.

[0020] In some embodiments, a request distribution module is configured to distribute incoming configuration change requests from the at least one user equipment through a shared load balancer.

[0021] In some embodiments, the request processing module is further configured to process the received configuration change request through a pluralityof web servers and a plurality of application programming interface (API) gateway servers.

[0022] In some embodiments, a microservices module is configured to execute a plurality of microservices to perform specific tasks related to the network node configuration management.

[0023] In some embodiments, the memory comprises a database enabled with a distributed file system for storing and processing data related to the created workorder.

[0024] In some embodiments, a user interface module is configured to display the dynamically updated at least one status of the created workorder on a superset dashboard.

[0025] In some embodiments, a scheduling module is configured to schedule services with service schedulers, execute the scheduled services with a service execution engine. Further, the monitoring and status update module is further configured to monitor the executed services and updating status of the scheduled services with a service monitoring and status update engine.

[0026] In some embodiments, the one or more processor(s) are further configured for distributing load among one or more LTE operations managers for radio network through an elastic load balancer (ELB).

[0027] In some embodiments, the created workorder is generated by a workorder engine in response to the received configuration change request.

[0028] In some embodiments, the network node is a radio access network (RAN) node. Managing the RAN node configuration comprises sending the configuration change request to at least one LTE operations manager (also interchangeably referred to as operations manager) for radio network for implementation on the RAN node.

[0029] In some embodiments, an acknowledgment processing module is configured to receive an acknowledgment from the at least one operations manager in response to the sent configuration change request. Further, the monitoring and status update module is configured to update the at least one status of the created workorder based on the received acknowledgment.

[0030] In some embodiments, the user interface module is further configured to consolidate a plurality of configuration change request workorders on a single user interface, and display, for each consolidated workorder, at least one parameter comprising a workorder identifier, a creator identifier, a creation date, a creation time, an execution date, an execution time, and a requested configuration change count.

[0031] In another exemplary embodiment, a method for network node configuration management is described. The method comprises receiving, by a request processing module, a configuration change request related to a network node . The method further comprises creating, by a workorder management module, a workorder in response to the received configuration change request. The method further comprises assigning, by the workorder management module, at least one status to the created workorder. The method triggers an execution of the created workorder. The method further comprises dynamically updating, by a monitoring and status update module the at least one status of the created workorder based on the execution. The method further comprises managing, by a node configuration module, the network node configuration based on the dynamically updated at least one status of the created workorder.

[0032] In some embodiments, the method further comprises distributing, by a request distribution module, incoming configuration change requests from the at least one user equipment through a shared load balancer.

[0033] In some embodiments, the method further comprises processing, by the request processing module, the received configuration change request througha plurality of web servers and a plurality of application programming interface (API) gateway servers.

[0034] In some embodiments, the method further comprises executing, by a microservices module, a plurality of microservices to perform specific tasks related to the network node configuration management.

[0035] In some embodiments, the method further comprises storing and processing, by a data storage and processing module, data related to the created workorder in a database enabled with a distributed file system (416).

[0036] In some embodiments, the method further comprises displaying, by a user interface module, the dynamically updated at least one status of the created workorder on a superset dashboard.

[0037] In some embodiments, the method further comprises scheduling, by a scheduling module, services with service schedulers, executing, by the scheduling module, the scheduled services with a service execution engine, and monitoring, by a monitoring and status update module, the executed services and updating status of the scheduled services with a service monitoring and status update engine.

[0038] In some embodiments, the method further comprises distributing load among one or more operations manager through an elastic load balancer (ELB).

[0039] In some embodiments, the created workorder is generated by a workorder engine in response to the received configuration change request.

[0040] In some embodiments, the network node is a radio access network (RAN) node. Managing the RAN node configuration comprises sending the configuration change request to at least one operations manager for implementation on the RAN node.

[0041] In some embodiments, the method further comprises receiving, by an acknowledgment processing module, an acknowledgment from the at least one operations manager in response to the sent configuration change request, and updating, by the monitoring and status update module, the at least one status of the created workorder based on the received acknowledgment.

[0042] In some embodiments, the method further comprises consolidating, by the user interface module, a plurality of configuration change request workorders on a single user interface, and displaying, by the user interface module, for each consolidated workorder, at least one parameter comprising a workorder identifier, a creator identifier, a creation date, a creation time, an execution date, an execution time, and a requested configuration change count.

[0043] In a further exemplary embodiment, a computer program product comprising a non-transitory computer-readable medium having a computer- readable program code embodied therein to be executed by one or more processors is described. The program code includes instructions for receiving a configuration change request related to a network node from at least one user equipment, creating a workorder in response to the received configuration change request, assigning at least one status to the created workorder, triggering an execution of the created workorder, dynamically updating the at least one status of the created workorder based on the execution, and managing the network node configuration based on the dynamically updated at least one status of the created workorder.

[0044] The foregoing general description of the illustrative embodiments and the following detailed description thereof are merely exemplary aspects of the teachings of this disclosure, and are not restrictive.OBJECTIVES OF THE DISCLOSURE

[0045] Some of the objective of the present disclosure, which at least one embodiment herein satisfies are as listed herein below.

[0046] An objective of the present disclosure is to provide an improved system and a method for network node configuration management such as a Radio Access Network (RAN) Node, thereby enhancing the efficiency and reliability of network operations.

[0047] An objective of the present disclosure is to provide a central work order and execution user interface (UI), thereby enabling efficient tracking and monitoring of end-to-end RAN node configuration change requests.

[0048] An objective of the present disclosure is to provide complete end-to- end RAN node configuration change execution status through a single UI, thereby improving visibility and control over the configuration change process.

[0049] An objective of the present disclosure is to enable users to pre-plan their day-to-day RAN node configuration changes easily and conveniently using configuration change request status, thereby optimizing resource allocation and reducing downtime.

[0050] An objective of the present disclosure is to optimize the performance of the RAN nodes, thereby enhancing overall network efficiency and user experience.

[0051] An objective of the present disclosure is to automate the process of workorder creation and status updates, thereby reducing manual errors and improving operational efficiency.

[0052] An objective of the present disclosure is to provide real-time status updates of configuration change requests, thereby enabling quick decision-making and problem resolution.

[0053] An objective of the present disclosure is to implement a distributed load balancing system, thereby ensuring efficient utilization of network resources and preventing bottlenecks.

[0054] An objective of the present disclosure is to integrate microservices architecture for configuration management, thereby enhancing scalability and flexibility of the system.

[0055] An objective of the present disclosure is to provide a consolidated view of multiple configuration change requests, thereby simplifying network management for operators.

[0056] Other objects and advantages of the present disclosure will be more apparent from the following description, which is not intended to limit the scope of the present disclosure.BRIEF DESCRIPTION OF DRAWINGS

[0057] 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. Some drawings may indicate the components using block diagrams and may not represent the internal circuitry of each component. It will be appreciated by those skilled in the art that disclosure of such drawings includes the disclosure of electrical components, electronic components or circuitry commonly used to implement such components.

[0058] FIG. 1 illustrates an exemplary network architecture for network node configuration management, in accordance with embodiments of the present disclosure.

[0059] FIG. 2 illustrates an exemplary microservice-based architecture of a system for network node configuration management, in accordance with embodiments of the present disclosure.

[0060] FIG. 3 illustrates an exemplary flow diagram for network node configuration management, in accordance with embodiments of the present disclosure.

[0061] FIG. 4 illustrates a block diagram of the system for Radio Access Network (RAN) node configuration management, in accordance with embodiments of the present disclosure.

[0062] FIG. 5 illustrates an exemplary illustration of a method for network node configuration management, in accordance with embodiments of the present disclosure.

[0063] FIG. 6 illustrates an example computer system in which or with which the embodiments of the present disclosure may be implemented, in accordance with embodiments of the present disclosure.

[0064] The foregoing shall be more apparent from the following more detailed description of the disclosure.LIST OF REFERENCE NUMERALS100 - Network architecture102 - System104 - Network108-1, 108-2... 108-N - User equipment110-1, 110-2...110-N - Users112 - Web Servers114 - Application Program Interface (API) Gateway Servers200 - System Architecture202 - one or more Processor(s)204 - Memory206 - Interfaces208 - Processing engine210 - Database212 - Request distribution module214 - Request processing module216 - Microservices module218 - Execution module220 - Load distribution module222 - Monitoring and status update module224 - Data storage and processing module226 - User interface module228 - Scheduling module230 - Acknowledgment processing module232 - Workorder management module234 - Node configuration module236 - Other Module(s)300 - Method302, 304, 306, 308, 310, 312, and 314 - Steps of method 300400 - System block diagram412 - Shared load balancer414 - Microservices416 - Distributed file system418 - Superset dashboard420 - Service(s) schedulers422 - Service(s) execution engine424 - Service(s) monitoring and status update engine426 - Elastic load balancer (ELB)428 - Workorder Engine430 - operations manager500 - Method502, 504, 506, 508, 510, and 512 - Steps of method 500600 - A computer system610 - External Storage Device620 - Bus630 - Main Memory640 - Read Only Memory650 - Mass Storage Device660 - Communication Port(s)670 - ProcessorDETAILED DESCRIPTION OF THE DISCLOSURE

[0065] 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 can each be used independently of one another or with any combination of other features. An individual feature may not address all 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.

[0066] The ensuing description provides exemplary embodiments only, and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing an exemplary embodiment. It should be understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the disclosure as set forth.

[0067] 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, networks, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail. In other instances, well-knowncircuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail in order to avoid obscuring the embodiments.

[0068] 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 can 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. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination can correspond to a return of the function to the calling function or the main function.

[0069] 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 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 similar to the term “comprising” as an open transition word without precluding any additional or other elements.

[0070] Reference throughout this specification to “one embodiment” or “an embodiment” or “an instance” or “one instance” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present disclosure. Thus, the appearances of the phrases “in one embodiment” or “in an embodiment” in various places throughout this specification are not necessarily all referring to the same embodiment.Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0071] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and / or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof. As used herein, the term “and / or” includes any and all combinations of one or more of the associated listed items.

[0072] The aspects of the present disclosure are directed to a system and method for network node configuration management, particularly for radio access network (RAN) nodes in high-scale 4G and 5G networks and beyond. The present disclosure addresses the challenges associated with tracking and monitoring multiple configuration change requests in complex telecommunications networks. The configuration change request may refer to a formal request to modify the operational parameters, settings, or software configurations of one or more RAN elements, such as base stations (gNB, eNB), Remote Radio Units (RRUs), Centralized Units (CUs), Distributed Units (DUs), or small cells. The content of the configuration change request may include node details, change description which many include configuration parameters to be modified (e.g., PCI, TAC, PRACH settings), justification, and roll back plan.

[0073] The system and method of the present disclosure provide a centralized workorder and execution user interface (UI) that efficiently manages the end-to-end process of RAN node configuration changes. This solution overcomes the limitations of conventional techniques that require significant manual effort and are prone to errors in tracking each configuration change request.

[0074] The present disclosure introduces a comprehensive approach to handling configuration change requests, from creation to completion. It implements a workorder system with real-time status updates, allowing users to monitor the progress of configuration changes through various stages such as 'Created', 'InProgress', 'Success', 'Failed', 'Cancelled', 'Aborted', and 'Completed'. Created stage refers to a state where change request has been initiated but not yet acted upon. InProgress refers to a state where change request has been initiated and change implementation is currently underway. In examples, the network engineers or automated systems are applying the requested configuration changes. Success state refers to a state where configuration change was successfully applied without issues. Failed state refers to a state where the configuration change was attempted but did not complete successfully. The reasons due to failed state may be due to issues or errors that may have occurred during the implementation. In such instances, rollback or corrective actions may be required. Further, cancelled state may be a state where the change request was intentionally withdrawn or stopped before execution. This may be due to changing priorities or resource constraints. Aborted state may be a state where the change process was forcefully terminated during execution. This may be due to unexpected errors, safety triggers, or manual intervention. Completed state may be a state where change request has successfully concluded, regardless of the outcome. The state may include both successful and failed changes, indicating the process is finalized.

[0075] Furthermore, the system incorporates advanced features such as load balancing, microservices architecture, and integration with operations manager to optimize the performance of the RAN. The single user interface consolidates all configuration change request workorders, providing a holistic view of the network configuration status and enabling efficient management of day-to-day RAN node configuration changes.

[0076] The various embodiments throughout the disclosure will be explained in more detail with reference to FIGS. 1-6.

[0077] FIG. 1 illustrates a network architecture (100) of a system (102) for network node configuration management, in accordance with embodiments of the present disclosure.

[0078] In an embodiment, the system (102) may be configured to implement an Operation Support Systems / Business Support Systems (OSS / BSS) service. The system (102) is connected to a network (104), which is further connected to at least one computing devices 108-1, 108-2, . . . 108-N (collectively referred as computing device 108, herein) associated with one or more users 110-1, 110-2, ... 110-N (collectively referred as user (110), herein). The computing device (108) may be personal computers, laptops, tablets, wristwatch, or any custom-built computing device integrated within a modern diagnostic machine that can connect to a network as an loT (Internet of Things) device. In an embodiment, the computing device (108) may also be referred to as User Equipment (UE) or user device. Accordingly, the terms “computing device” and “User Equipment” may be used interchangeably throughout the disclosure. In an aspect, the user (110) is a network operator or a field engineer. Further, the network (104) can be configured with a centralized server (106) that stores compiled data.

[0079] In an embodiment, the system (102) may receive at least one input data from the user (110) via the at least one computing devices (108). In an aspect, the user (110) may be configured to initiate the process of network node configuration management, through an application interface of a mobile application installed in the computing devices (108). The mobile application may be configured to communicate with the network analysis server. In some examples, the mobile application may be a software or a mobile application from an application distribution platform. Examples of application distribution platforms include the App Store for iOS provided by Apple, Inc., Play Store for Android OS provided by Google Inc., and such application distribution platforms. In an embodiment, the computing device (108) may transmit the at least one captured data packet over a point-to-point or point- to-multipoint communication channel or network (104) to the system (102). In an embodiment, the computing device (108) may involvecollection, analysis, and sharing of data received from the system (102) via the network (104). Furthermore, the system (102) may be connected to servers such as web servers (112) and Application Program Interface (API) servers (114) via the network (104). Web servers (112) may be a specialized computers or software applications that host and deliver web content to the computing device (108) over the internet. The web servers (112) are used to host user interfaces, documentation, or other web-based components related to the application distribution platform. Further, the application program interface (API) Servers (114) are dedicated servers that handle requests and responses for the application programming interfaces (APIs). The API servers (114) are responsible for processing requests from the computing devices (108), managing data exchanges between different parts of the system (102), and facilitating integration with external services or platforms.

[0080] In an exemplary embodiment, the network (104) may include, but not be limited to, at least a portion of one or more networks having one or more nodes that transmit, receive, forward, generate, buffer, store, route, switch, process, or a combination thereof, etc. one or more messages, packets, signals, waves, voltage or current levels, some combination thereof, or so forth. In an exemplary embodiment, the network 104 may include, but not be limited to, a wireless network, a wired network, an internet, an intranet, a public network, a private network, a packet- switched network, a circuit- switched network, an ad hoc network, an infrastructure network, a Public-Switched Telephone Network (PSTN), a cable network, a cellular network, a satellite network, a fiber optic network, or some combination thereof.

[0081] Although FIG. 1 shows exemplary components of the network architecture (100), in other embodiments, the network architecture (100) may include fewer components, different components, differently arranged components, or additional functional components than depicted in FIG. 1. Additionally, or alternatively, one or more components of the network architecture (100) may perform functions described as being performed by one or more other components of the network architecture (100).

[0082] FIG. 2 with reference to FIG. 1 , illustrates an exemplary architecture (200) of the system (102) for network node configuration management, in accordance with an embodiment of the present disclosure.

[0083] The system (102) includes one or more processor(s) (202), a memory (204), a processing engine (208), a database (210), and an interface(s) (206). In an exemplary embodiment, the processing engine (208) may include one or more modules / engines selected from any of a request distribution module (212), a request processing module (214), a microservices module (216), a execution module (218), a load distribution module (220), a monitoring and status update module (222), a data storage and processing module (224), a user interface module (226), a scheduling module (228), an acknowledgment processing module (230), a workorder management module (232), a node configuration module (234) and other module(s) (236) having functions that may include but are not limited to receiving data, processing data, testing, storage, and peripheral functions, such as wireless communication unit for remote operation, audio unit for alerts and the like. The database (210) may be enabled with a distributed file system for efficient data storage and processing.

[0084] The one or more processor(s) (202) is configured to initiate the processor of network node configuration management through the application interface of the UE (108). In an embodiment, the application interface is configured to transmit one or more instructions to the one or more processor(s) (202).

[0085] In an embodiment, the one or more processor(s) (202) may be implemented as one or more microprocessors, microcomputers, microcontrollers, edge or fog microcontrollers, digital signal processors, central processing units, logic circuitries, and / or any devices that process data based on operational instructions. Among other capabilities, the one or more processor(s) (202) may be configured to fetch and execute computer-readable instructions stored in the memory (204) of the system (102). The memory (204) may be configured to store one or more computer-readable instructions or routines in a non-transitorycomputer readable storage medium, which may be fetched and executed to create or share data packets over a network service. The memory (204) may comprise any non-transitory storage device including, for example, volatile memory such as Random Access Memory (RAM), or non-volatile memory such as Erasable Programmable Read-Only Memory (EPROM), flash memory, and the like.

[0086] The interface(s) (206) is included within the system (102) to serve as a medium for data exchange, configured to facilitate user interaction with the mobile application. The interface(s) (206) may be composed of interfaces for data input and output devices, storage devices, and the like, providing a communication pathway for the various components of the system (102).

[0087] The interface(s) (206) may comprise a variety of interfaces, for example, interfaces for data input and output devices, referred to as I / O devices, storage devices, and the like. The interface(s) (206) may facilitate communication to / from the system (102). The interface(s) (206) may also provide a communication pathway for one or more components of the system (102). Examples of such components include but are not limited to, the processing unit / engine(s) (208) and the database (210).

[0088] In an embodiment, the processing unit / engine(s) (208) may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processing engine(s) (208). In examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processing engine(s) (208) may be processorexecutable instructions stored on a non-transitory machine-readable storage medium and the hardware for the processing engine(s) (208) may comprise a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the machine-readable storage medium may store instructions that, when executed by the processing resource, implement the processing engine(s) (208). In such examples, the system (102) may comprise themachine-readable storage medium storing the instructions and the processing resource to execute the instructions, or the machine-readable storage medium may be separate but accessible to the system (102) and the processing resource. In other examples, the processing engine(s) (208) may be implemented by electronic circuitry.

[0089] In an embodiment, the database (210) is configured for serving as a centralized repository for storing and retrieving various operational data. The database (210) is designed to interact seamlessly with other components of the system (102) to support the system's functionality effectively. The database (210) may store data that may be either stored or generated as a result of functionalities implemented by any of the components of the one or more processor(s) (202) or the processing engines (208). In an embodiment, the database (210) may be separate from the system (102).

[0090] In an embodiment, the modules of the system (102) for network node configuration management may work together efficiently to manage and track configuration changes in network node such as the radio access network (RAN) nodes. At the core of the system (102) may be the workorder management module (232), which may be responsible for creating, tracking, and updating workorders based on received configuration change requests . In an embodiment, the configuration change requests may be received from a user through a user equipment. In another embodiment, the configuration change requests may be received from a computing device such as a server. In another embodiment, the configuration change requests may be received from any module, service or a hot associated with RAN nodes based on system / process requirement for configuration change. In instances where the configuration change requests are received by module, service or a hot associated with RAN nodes, the configuration change requests may be automatically triggered without user intervention.

[0091] Upon receiving a configuration change request related to a network node from at least one user equipment (108), the workorder management module(232) may create a workorder in response to the received configuration change request. The workorder management module (232) may assign at least one status to the created workorder, which may initially be set as "Created". The workorder management module (232) may be implemented as part of a workorder engine, which may generate the workorder based on the specific details of the received configuration change request.

[0092] In an embodiment, the request distribution module (212), which may be implemented using a shared load balancer. The request distribution module (212) may be responsible for distributing incoming configuration change requests from the at least one user equipment (108) across the system's resources. By efficiently distributing these requests, the system (102) may ensure that no single component becomes overwhelmed, thereby maintaining optimal performance even during periods of high demand.

[0093] In an embodiment, the request processing module (214) may be implemented using a plurality of web servers (112) and a plurality of application programming interface (API) gateway servers (114). The request processing module (214) may process the received configuration change request, breaking the request down into actionable items and preparing the actionable items for execution. In examples, the use of multiple servers may allow for parallel processing of requests, further enhancing the system's efficiency and responsiveness.

[0094] In an embodiment, the microservices module (216) may provision a plurality of microservices designed to perform specific tasks related to the network node configuration management. These microservices may be small, independent processes that work together to accomplish complex tasks. For example, one microservice may be responsible for validating the configuration change request, another for checking resource availability, and yet another for scheduling the change implementation. The microservices module (216) may also provide varioussupporting functions, such as validation and resource checking, to ensure smooth execution of the configuration change.

[0095] In an embodiment, the execution module (218) may be implemented using a service execution engine. The execution module (218) may be responsible for triggering the execution of the created workorder. In one embodiment, the execution may be where the configuration change requests are received by module, service or a hot associated with RAN nodes, the configuration change requests may be automatically triggered without user intervention.

[0096] When the execution is triggered, the execution module (218) may update the status of the workorder from "Created" to "InProgress". The execution module (218) may interact closely with the operations manager to implement the actual configuration changes on the RAN nodes. To ensure efficient utilization of resources, the system (102) may include the load distribution module (220), implemented using an elastic load balancer (ELB). The load distribution module (220) may distribute the load among one or more operations managers, ensuring that the workload is evenly spread and that no single operations manager becomes a bottleneck in the configuration change process. Throughout this process, the load distribution module (220) may ensure that the workload is evenly distributed among the available operations managers.

[0097] Further, the node configuration module (234), which may be implemented as a service monitoring and status update engine, may be responsible for dynamically updating the at least one status of the created workorder based on the execution. The node configuration module (234) may continuously monitor the progress of the configuration change implementation and update the workorder status accordingly. For instance, the node configuration module (234) may update the status from "InProgress" to "Success" or "Failed" based on the execution result. After the execution is finished, the node configuration module (234) may further update the status from "Success" or "Failed" to "Completed".

[0098] Further, the data storage and processing module (224) may be configured for managing the database (210) enabled with a distributed file system. The data storage and processing module (224) may be responsible for storing and processing data related to the created workorder. The use of data storage and processing module (224) may allow for efficient storage and retrieval of large volumes of data, which may be crucial for managing configuration changes in large- scale networks.

[0099] In an embodiment, the user interface module (226), may be responsible for displaying the dynamically updated at least one status of the created workorder. The user interface module (226) may provide a centralized view of all workorders, allowing users to easily track the progress of multiple configuration changes simultaneously.[000100] Further, the scheduling module (228), implemented using service schedulers, may be responsible for planning and organizing the execution of services related to the configuration changes. The scheduling module (228) may work in conjunction with the execution module (218) to ensure that configuration changes are implemented in an orderly and efficient manner. The scheduling module (228) may coordinate the timing of various configuration changes, ensuring that they are implemented in an optimal sequence.[000101] In an embodiment, the acknowledgment processing module (230) may be implemented to handle responses from the operations managers. The acknowledgment processing module (230) may receive an acknowledgment from at least one operations manager in response to the sent configuration change request and may update the at least one status of the created workorder based on the received acknowledgment. This feature may ensure that the system (102) always has up-to-date information on the status of configuration changes. The acknowledgment processing module (230) may also handle responses from the operations managers, updating the workorder status based on these responses.[000102] Further, the user interface module (226) may be responsible for consolidating a plurality of configuration change request workorders on a single user interface. The user interface module (226) may display, for each consolidated workorder, at least one parameter comprising a workorder identifier, a creator identifier, a creation date, a creation time, an execution date, an execution time, and a requested configuration change count. By providing this comprehensive view, the module may allow network operators to easily manage and track multiple configuration changes.[000103] In operation, when a user initiates a configuration change request from their user equipment (108), the request may be received by the request distribution module (212). The request distribution module (212) may then forward the request to the request processing module (214), which may process the request and create a workorder using the workorder management module (232).[000104] The created workorder may then be passed to the execution module (218), which may trigger its execution. As the execution progresses, the monitoring and status update module (222) may continually update the workorder's status. These updates may be stored in the database (210) and displayed to the user via the user interface module (226). The user interface module (226) may provide a comprehensive view of all ongoing and completed configuration changes, allowing network operators to easily manage and track the overall state of the network.[000105] In an embodiment, the system (102) may be specifically designed for network node configuration management, where the network node may be a radio access network (RAN) node.[000106] FIG. 3 illustrates an exemplary flow diagram of a method (300) for RAN node configuration management, in accordance with embodiments of the present disclosure.[000107] At step (302), the method (300) includes creating a workorder after creation and submission of the RAN node configuration change request . In oneembodiment, the RAN node configuration change may be created by a user (for example, operator, technician) through a user equipment. For example, when a network operator uses a tablet to submit a request to adjust the antenna tilt of a specific RAN node from 5° to 3°, a workorder (e.g., W0-RAN-5G-CR-MU-1) is created. Each newly created configuration change request workorder is assigned an initial status of 'Created'. In another embodiment, the RAN node configuration change may be automatically created by a node monitoring unit (not shown). For example, the RAN node antenna tilt might have been disturbed due to strong winds, animal or bird mischief, etc. In such instances, the node monitoring unit may create a RAN node configuration change request to re-tilt the antenna to its original position.[000108] At step (304), the method (300) performs a visualization of all the created workorders to identify valid workorders. The workorders may follow a format such as 'WO-RAN-5G-CR-MU-T, 'WO-RAN-5G-CR-MU-2', and 'WO- RAN-5G-CR-MU-3'. This step helps in filtering out any invalid workorders, for which no further action is taken.[000109] At step (306), for all valid workorders, the method (300) takes action by forwarding the workorder for approval for execution. This step ensures that only authorized changes are implemented. If a workorder does not receive approval, no further action is taken.[000110] At step (308), when a workorder receives approval for execution, the method (300) changes the status of the workorder from 'Created' to 'InProgress'. This status change signifies the beginning of the actual configuration change process.[000111] At step (310), the method (300). when the execution is successfully performed (e.g., the antenna tilt is successfully adjusted), the status of the workorder is changed from 'InProgress' to 'Success'. After all associated tasks are completed, the status further changes from 'Success' to 'Completed'.[000112] At step (312), the method (300) addresses scenarios where the execution of the created configuration change request workorder fails. In such cases, the status of the workorder is changed from 'InProgress' to 'Failed'. This could happen due to various reasons such as hardware limitations or network issues.[000113] At step (314), after the execution, the method (300) finalizes the status of all configuration change request workorders. Workorders with a status of 'Success' or 'Failed' are changed to 'Completed'. This final status update ensures that all workorders, regardless of their execution outcome, are marked as processed and completed in the system.[000114] FIG. 4 illustrates an exemplary system architecture (400) of a system (102) for network node configuration management, in accordance with an embodiment of the present disclosure.[000115] The system architecture includes a plurality of user equipment’s (UEs) (108), a shared load balancer (412), and a network management platform (404).[000116] FIG. 4 illustrates a block diagram (400) of the system (102) for network node configuration management, particularly focusing on radio access network (RAN) nodes, in accordance with an embodiment of the present disclosure.[000117] The system architecture includes a plurality of user equipment(s) (UEs) (108), a shared load balancer (412), and a network management platform (404). The network management platform (404) comprises several key components that work together to facilitate efficient network configuration management. The network management platform (404) comprises the plurality of web servers (112), plurality of application programming interface (API) gateway servers (114), database (210), a shared load balancer (412), microservices (414), a distributed file system (416), a superset dashboard (418), a service(s) schedulers (420), a service(s) execution engine (422), a service(s) monitoring and status update engine (424), anelastic load balancer (ELB) (426), a workorder engine (428), and an operations manager (430).[000118] At the forefront of the platform are a plurality of web servers (112) that facilitate hosting and delivery of web-based applications, services, and content over a network. These servers respond to requests from clients (such as web browsers) by serving web pages with static or dynamically generated content. Working in tandem with the web servers are a plurality of application programming interface (API) gateway servers (114) that serve as an intermediary between clients (such as UEs, applications, or users) and backend services. These servers act as an entry point for all incoming API requests, enhancing the management, security, and control of API interactions.[000119] The heart of the system lies in its plurality of microservices (414), which are loosely coupled and independently deployable services, each configured to perform specific tasks related to network management. These microservices work in an orchestrated manner to provide overall functionality of the platform. To support these services, the system employs a database (210) that operates with a distributed file system (416) for performing various data processing tasks. The distributed file system (416) is designed to run on commodity hardware, providing fault-tolerance and efficient data storage and retrieval.[000120] The database (210) is intricately connected to service schedulers (420), service(s) execution engine (422), and a service monitoring and status update engine (424). These components work in harmony to manage the lifecycle of configuration changes. The service schedulers (420) are configured to schedule services according to operational plans, while the service(s) execution engine (422) executes these services as per the schedule and operational plans. The service monitoring and status update engine (424) continuously monitors the executed services, gathers key performance indicators, and provides status updates.[000121] In an embodiment, to provide visual insight into the system's operations, a superset dashboard (418) offers a comprehensive representation ofdata, providing a quick overview of key performance indicators (KPIs), trends, and insights relevant to end-to-end RAN node configuration change execution status. This dashboard serves as a central point for users to monitor and manage network configurations. In examples, the superset dashboard (418) may be a data visualization and monitoring interface that provides a centralized view of work orders associated with RAN configuration changes across the network. In examples, the superset dashboard (418) may be implemented using business intelligence (BI) tool, to display real-time and historical data related to change order request requests, enabling data-driven insights and operational efficiency. The superset dashboard (418) may provide an overview of change order requests, allows real-time updating and monitoring, provides data visualization, provides performance impact analysis, and user interface options such as filtering, drilldown, etc., to perform analysis at coarse or deep levels. The superset dashboard (418) may help in improved visibility, centralized tracking of all change order requests, allows data-driven decisions, improves operational efficiency and helps error detection.[000122] The system also incorporates an elastic load balancer (ELB) (426) and a workorder engine (428). The ELB (426) plays a crucial role in distributing load among one or more operations manager (430), thereby optimizing network performance, scalability, and reliability. Importantly, the ELB (426) is communicatively coupled to multiple operations managers (430), such as operations manager 1(430-1), operations manager 2 (430-2), ..., operations manager N (430-n). This allows for efficient distribution of workload across multiple network management systems. The operations managers (430) are configured as Element Management Systems (EMS), responsible for monitoring, configuring, and controlling individual network elements or devices, including switches, routers, base stations, optical transport systems, and other telecommunications equipment.[000123] In operation, the shared load balancer (412) receives API requests from the UEs (108) when events related to node configuration change requests are detected. The shared load balancer (412) then transmits these requests to thenetwork management platform (404), distributing the load effectively among various components. The web servers (112) receive the configuration change requests and transmit them to the API gateway servers (114), which are linked to the microservices (414) for further processing.[000124] The ELB (426) sends configuration change requests to the appropriate operations manager (430) for implementation, and the operations manager (430) sends acknowledgments back to the ELB (426). The ELB (426) also sends monitoring requests to the operations managers (430), which respond with callback notifications and status updates.[000125] After creation and submission of a RAN node configuration change request, a workorder entry is created in a workorder and jobs user interface (UI). This UI tracks the status of all created and submitted configuration change requests, continuously adding new requests and updating their statuses. It allows users to view various parameters related to each configuration change request workorder, including execution status, workorder identifier, creator, creation date and time, execution date and time, and requested configuration change count.[000126] The system (102) provides real-time monitoring of configuration change request workorder execution status, including statuses such as 'Created', 'InProgress', 'Completed', 'Success', 'Failed', 'Cancelled', 'Aborted', and others. By consolidating all configuration change request workorders in a single UI and updating each running configuration change request status in real-time, the system offers a comprehensive and efficient solution for network node configuration management, particularly in radio access networks, thereby improving network performance and reliability.[000127] FIG. 5 illustrates an exemplary flow diagram of a method (500) for network node configuration management, in accordance with embodiments of the present disclosure.[000128] At step (502), the method (500) includes receiving by the request processing module (214), a configuration change request related to a network node from at least one user equipment (108). For example, a network operator might use a mobile device to submit a change request to increase the transmission power of a specific RAN node from 20W to 40W to improve coverage in a rural area. This step may involve distributing, by the request distribution module (212), incoming configuration change requests through a shared load balancer (412) to ensure efficient processing of multiple simultaneous requests.[000129] At step (504), the method (500) includes creating, by the workorder management module (232), a workorder in response to the received configuration change request. The workorder may be generated by a workorder engine (428). For instance, a workorder W0-RAN-5G-CR-MU-1 might be created, detailing the requested power increase for the specific RAN node. This step may involve processing, by the request processing module (214), the received configuration change request through a plurality of web servers (112) and a plurality of application programming interface (API) gateway servers (114) to handle user interfaces and request processing respectively.[000130] At step (506), the method (500) includes assigning, by the workorder management module (232), at least one status to the created workorder. Initially, the status may be set as 'Created'. This status indicates that the system has acknowledged the request and generated a workorder, but hasn't yet begun processing it.[000131] At step (508), the method (500) includes triggering, by the execution module (218), an execution of the created workorder. This step may involve scheduling services with service schedulers (420), such as scheduling the power increase during a maintenance window, and executing the scheduled services with a service(s) execution engine (422). The execution may involve executing by the microservices module (216), a plurality of microservices (414) to perform specific tasks related to the network node configuration management, such as validating therequested power level, checking for potential interference, and preparing the actual configuration command.[000132] At step (510), the method (500) includes dynamically updating, by the monitoring and status update module (222), the at least one status of the created workorder based on the execution. This involves monitoring the executed services and updating the status of the scheduled services with a service monitoring and status update engine (424). The status updates may include:[000133] Updating the status from "Created" to "InProgress" when the power increase execution is triggered.[000134] Updating the status from "InProgress" to "Success" if the power increase is successfully implemented, or "Failed" if there's an issue (e.g., hardware limitation).[000135] Updating the status from "Success" or "Failed" to "Completed" after all associated tasks are finished.[000136] At step (512), the method (500) includes managing, by the node configuration module (234), the network node configuration based on the dynamically updated at least one status of the created workorder. This may involve storing and processing by the data storage and processing module (224), the data related to the created workorder in a database (210) enabled with a distributed file system (416), allowing for efficient storage and retrieval of large volumes of configuration change data.[000137] The method (500) further includes displaying, by the user interface module (226), the dynamically updated status of the created workorder on a superset dashboard (418). For example, an operator can see at a glance that WO- RAN-5G-CR-MU-1 (power increase) is "InProgress", while WO-RAN-5G-CR- MU-2 (frequency change) is "Completed" and WO-RAN-5G-CR-MU-3 (antenna tilt adjustment) is "Failed".[000138] If the network node is a radio access network (RAN) node, the process of managing the RAN node configuration comprises sending the configuration change request to at least one operations manager (430) for implementation on the RAN node. The method includes distributing load among one or more operations managers (430) through an elastic load balancer (ELB) (426), ensuring efficient processing if multiple RAN nodes need updating.[000139] The method (500) also includes receiving, by the acknowledgment processing module (230), an acknowledgment from the at least one operations manager (430) in response to the sent configuration change request. For example, after attempting the power increase, the operations manager might send back an acknowledgment like "Change Successful" or "Change Failed - Hardware Limitation". The method then includes updating, by the monitoring and status update module (222), the status of the created workorder based on this received acknowledgment.[000140] Additionally, the method (500) includes consolidating, by the user interface module (226), a plurality of configuration change request workorders on a single user interface. This interface displays by the user interface module (226), for each consolidated workorder, parameters including a workorder identifier (e.g., WO-RAN-5G-CR-MU-1), creator identifier (e.g., Operatorl23), creation date and time (e.g., 2023-07-25 14:30), execution date and time (e.g., 2023-07-26 02:00), and requested configuration change count (e.g., 1 node affected).[000141] The present disclosure provides technical advancement related to network node configuration management, particularly in radio access networks (RANs). This advancement addresses the limitations of existing solutions by introducing a centralized, automated system for managing configuration change requests across multiple network nodes. The disclosure involves a comprehensive workorder management process, real-time status tracking, and intelligent load balancing, which offer significant improvements in efficiency, reliability, and visibility of network configuration changes. By implementing a microservicesarchitecture and distributed processing, the disclosed invention enhances the speed and scalability of configuration management, resulting in reduced downtime, minimized human errors, and improved overall network performance. The system's ability to consolidate multiple configuration changes on a single dashboard and provide real-time status updates enables network operators to manage complex network environments more effectively, leading to optimized network operations and improved service quality for end-users.[000142] While considerable emphasis has been placed herein on the preferred embodiments, it will be appreciated that many embodiments can be made and that many changes can be made in the preferred embodiments without departing from the principles of the disclosure. These and other changes in the preferred embodiments of the disclosure will be apparent to those skilled in the art from the disclosure herein, whereby it is to be distinctly understood that the foregoing descriptive matter to be implemented merely as illustrative of the disclosure and not as limitation.ADVANTAGES OF THE PRESENT DISCLOSURE[000143] The present disclosure provides a centralized workorder and execution user interface (UI) that efficiently tracks and monitors end-to-end RAN node configuration change requests. This centralized approach significantly improves visibility and control over the configuration management process, reducing the likelihood of errors and streamlining operations.[000144] The present disclosure offers a complete end-to-end RAN node configuration change execution status through a single UI. This consolidated view enables network operators to quickly assess the status of multiple configuration changes simultaneously, enhancing decision-making capabilities and reducing response times to potential issues.[000145] The present disclosure allows users to easily and conveniently preplan their day-to-day RAN node configuration changes by utilizing theconfiguration change request status. This feature enables more effective resource allocation and scheduling, minimizing network disruptions and optimizing maintenance windows.[000146] The present disclosure implements an advanced RAN node configuration management system. By automating many aspects of the configuration process and incorporating intelligent load balancing, the system significantly reduces manual effort, minimizes human errors, and improves the overall efficiency of network management.[000147] The present disclosure optimizes the performance of the RAN through its comprehensive approach to configuration management. By ensuring that configuration changes are implemented correctly and efficiently, the system contributes to improved network reliability, enhanced coverage, and better quality of service for end-users.[000148] The present disclosure incorporates a microservices architecture and distributed processing, which enhances the scalability and flexibility of the configuration management system. This design allows the system to handle a large number of configuration requests simultaneously, making it suitable for managing complex, large-scale network environments.[000149] The present disclosure provides real-time status updates and comprehensive logging of configuration changes. This feature not only improves immediate operational awareness but also facilitates better long-term planning and troubleshooting by maintaining a detailed history of network modifications.

Claims

CLAIMS1. A system (102) for network node configuration management, the system (102) comprising: a request processing module (214) configured to receive a configuration change request related to a network node ; a workorder management module (232) configured to: create a workorder in response to the received configuration change request; and assign at least one status to the created workorder; an execution module (218) configured to trigger an execution of the created workorder; a monitoring and status update module (222) configured to dynamically update the at least one status of the created workorder based on the execution; and a node configuration module (234) configured to manage the network node configuration based on the dynamically updated at least one status of the created workorder.

2. The system (102) as claimed in claim 1, wherein the request processing module (214) is further configured to process the received configuration change request through a plurality of web servers (112) and a plurality of application programming interface (API) gateway servers (114).

3. The system (102) as claimed in claim 1, further comprising a user interface module (226) configured to display the dynamically updated at least one status of the created workorder on a superset dashboard (418).

4. The system (102) as claimed in claim 1 , wherein a scheduling module (228) is configured to: schedule services with service schedulers (420); and execute the scheduled services with a service(s) execution engine (422); andwherein the monitoring and status update module (222) is further configured to monitor the executed services and updating status of the scheduled services with a service monitoring and status update engine (424).

5. The system (102) as claimed in claim 1 , wherein the network node is a radio access network (RAN) node, wherein managing the RAN node configuration comprises sending the configuration change request to at least one operations manager (430) for implementation on the RAN node.

6. The system (102) as claimed in claim 1, wherein the user interface module (226) is further configured to: consolidate a plurality of configuration change request workorders on a single user interface; and display, for each consolidated workorder, at least one parameter comprising a workorder identifier, a creator identifier, a creation date, a creation time, an execution date, an execution time, and a requested configuration change count.

7. A method for network node configuration management, the method comprising: receiving, by a request processing module (214), a configuration change request related to a network node ; creating, by a workorder management module (232), a workorder in response to the received configuration change request; assigning, by the workorder management module (232), at least one status to the created workorder; triggering, by an execution module (218), an execution of the created workorder;dynamically updating, by a monitoring and status update module (222), the at least one status of the created workorder based on the execution; and managing, by a node configuration module (234), the network node configuration based on the dynamically updated at least one status of the created workorder.

8. The method as claimed in claim 7, further comprising distributing, by a request distribution module (212), incoming configuration change requests from the at least one user equipment (108) to the request processing module (214) through a shared load balancer (412).

9. The method as claimed in claim 7, further comprising processing, by the request processing module (214), the received configuration change request through a plurality of servers (112, 114) .

10. The method as claimed in claim 7, further comprising displaying, by a user interface module (226), the dynamically updated at least one status of the created workorder on a superset dashboard (418).

11. The method as claimed in claim 13, further comprising: scheduling, by a scheduling module (228), services using service schedulers (420); executing, by the scheduling module (228), the scheduled services with a service(s) execution engine (422); and monitoring, by a monitoring and status update module (222), the executed services and updating status of the scheduled services with a service monitoring and status update engine (424).

12. The method as claimed in claim 7, further comprising distributing load among one or more operations managers (430) through an elastic load balancer (ELB) (426).

13. The method as claimed in claim 7, wherein the created workorder is generated by a workorder engine (428) in response to the received configuration change request.

14. The method as claimed in claim 7, wherein the network node is a radio access network (RAN) node, and wherein managing the RAN node configuration comprises sending the configuration change request to at least one operations manager (430) for implementation on the RAN node.

15. The method as claimed in claim 14, further comprising: receiving, by an acknowledgment processing module (230), an acknowledgment from the at least one operations manager (430) in response to the sent configuration change request; and updating, by the monitoring and status update module (222), the at least one status of the created workorder based on the received acknowledgment.

16. The method as claimed in claim 7, further comprising: consolidating, by the user interface module (226), a plurality of configuration change request workorders on a single user interface; and displaying, by the user interface module (226), for each consolidated workorder, at least one parameter comprising a workorder identifier, a creator identifier, a creation date, a creation time, an execution date, an execution time, and a requested configuration change count.

17. A computer program product comprising a non- transitory computer- readable medium having a computer-readable program code embodied therein to be executed by one or more processors, the program code including instructions for: receiving a configuration change request related to a network node ; creating a workorder in response to the received configuration change request; assigning at least one status to the created workorder;triggering an execution of the created workorder; dynamically updating the at least one status of the created workorder based on the execution; and managing the network node configuration based on the dynamically updated at least one status of the created workorder.

Images