Generic framework for defining and executing control operations to respective southbound

Abstract

Embodiments of the disclosure describe a method 600 for managing, at a configuration management module 240, the one or more control operations includes a first operational state and a second operational state. The method 600 includes generating, in the first operational state, one or more RPC based templates tailored to operational requirements. The method 600 includes transmitting, in the second operational state, one or more execution files, through one or more southbound interfaces to at least one network node, to execute at least one respective operation based on the one or more generated RPC-based templates.

Description

GENERIC FRAMEWORK FOR DEFINING AND EXECUTING CONTROLOPERATIONS TO RESPECTIVE SOUTHBOUNDFIELD

[0001] This application claims priorities to Indian non provisional application No.202411065542, filed on August 30, 2024, the entire contents of which is incorporated herein by reference.FIELD

[0002] The present disclosure relates to a generic framework for defining and executing control operations to respective southbound.BACKGROUND

[0003] The information disclosed in this background section is only for enhancement of understanding of the general background of the disclosure and should not be taken as an acknowledgement or any form of suggestion that this information forms the prior art already known to a person skilled in the art.

[0004] The Element Management System (EMS) in telecommunications is a critical component designed to oversee and manage one or more network devices at a granular level. The EMS encompasses monitoring, configuration, fault management, and performance analysis of the one or more network devices. The EMS facilitates communication with a configuration backend through standardized protocols such as Simple Network Management Protocol (SNMP) and NETCONF, enabling seamless data exchange and configuration updates, as illustrated in FIG. 1. Additionally, the EMS interacts with one or more Network Functions (NFs) via a service-oriented architecture, employing Application Programming Interface (APIs) to ensure real-time data synchronization and command execution. This interaction allows for dynamic provisioning, automated fault detection, and performance optimization of network resources. By leveraging telemetry data, the EMS can generate insights that inform operational strategies and enhance network reliability. Ultimately, the EMS serves as a pivotal interface between network operations and management, ensuring efficient resource utilization and service quality in complex telecommunications environments.SUMMARY

[0005] This summary is provided to introduce a selection of concepts, in a simplified format, that are further described in the detailed description of the disclosure. This summary is neither intended to identify key or essential inventive concepts of the disclosure nor is it intended for determining the scope of the disclosure.

[0006] According to one embodiment of the present disclosure, a method is disclosed. The method includes managing, at a configuration management, one or more control operations comprising at least one of a first operational state and a second operational state. The method further includes generating, in the first operational state, one or more Remote Procedure Call (RPC) based templates tailored to operational requirements. The method further includes transmitting, in the second operational state, one or more execution files. The one or more execution files are transmitted through one or more southbound interfaces to at least one network node, to execute at least one respective operation based on the one or more generated RPC-based templates.

[0007] According to one embodiment of the present disclosure, an apparatus is disclosed. The apparatus is configured to manage, at a configuration management, one or more control operations comprising at least one of a first operational state and a second operational state. The apparatus is further configured to generate, in the first operational state, one or more Remote Procedure Call (RPC) based templates tailored to operational requirements. The apparatus is further configured to transmit, in the second operational state, one or more execution files. The one or more execution files are transmitted through one or more southbound interfaces to at least one network node, to execute at least one respective operation based on the one or more generated RPC-based templates.

[0008] To further clarify the advantages and features of the present disclosure, a more particular description of the disclosure will be rendered by reference to specific embodiments thereof, which are illustrated in the appended drawings. It is appreciated that these drawings depict only typical embodiments of the disclosure and are therefore not to be considered limiting of its scope. The disclosure will be described and explained with additional specificity and detail in the accompanying drawings.BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Features, aspects, and advantages of embodiments of the disclosure will be described below with reference to the accompanying drawings, in which like reference numerals denote like elements, and wherein:FIG. 1 illustrates one or more operations associated with an Element Management System (EMS), according to prior art;FIG. 2 illustrates a block diagram of an electronic device for managing one or more control operations, according to an embodiment as disclosed herein;FIG. 3 illustrates one or more operations associated with a first operational state and a second operational state, according to an embodiment as disclosed herein;FIGS. 4A-4B sequence flow diagrams illustrating a method for managing, by a configuration module of the electronic device, one or more control operations, according to an embodiment as disclosed herein;FIGS. 5A, 5B, 5C, 5D, and 5E illustrate one or more exemplary operations associated with the configuration module;FIG. 6 is a flow diagram illustrating a method for managing the one or more control operations, according to an embodiment as disclosed herein; andFIG. 7 illustrates a diagram of example components of a system, according to an embodiment as disclosed herein.DETAILED DESCRIPTION

[0010] The following detailed description of example embodiments refers to the accompanying drawings. The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the implementations to the precise form disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of the implementations. Further, one or more features or components of one embodiment may be incorporated into or combined with another embodiment (or one or more features of another embodiment). Additionally, the flowchart and description of operations provided below relate to one of the various embodiments. It should be noted that it is possible to make other embodiments that do not exactly match the flowchart and its description. It is understood that in other embodiments one or more operations may be omitted, one or moreoperations may be added, one or more operations may be performed simultaneously (at least in part).

[0011] It will be apparent that systems and / or methods, described herein, may be implemented in different forms of hardware, software, or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems and / or methods is not limiting of the implementations. Thus, the operation and behavior of the systems and / or methods are described herein without reference to specific software code. It is understood that software and hardware may be designed to implement the systems and / or methods based on the description herein.

[0012] Even though particular combinations of features are recited in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of implementations. In fact, many of these features may be combined in ways not specifically recited in the claims and / or disclosed in the specification. Although each dependent claim listed below may directly depend on only one claim, the disclosure of implementations includes each dependent claim in combination with every other claim in the claim set.

[0013] No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles “a” and “an” are intended to include one or more items, and may be used interchangeably with “one or more.” Also, as used herein, the terms “has,” “have,” “having,” “include,” “including,” or the like are intended to be open-ended terms. Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise. Furthermore, expressions such as “at least one of [A] and [B],” “[A] and / or [B],” or “at least one of [A] or [B]” are to be understood as including only A, only B, or both A and B.

[0014] The foregoing disclosure provides illustration and description but is not intended to be exhaustive or to limit the implementations to the precise form disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of the implementations.

[0015] Throughout this disclosure, the terms “configuration management” and “configuration management module” are used interchangeably and mean the same.

[0016] In certain existing systems, all operational tasks in telecommunications were previously handled directly through the Element Management System (EMS), which is connected to Network Functions (NFs), as illustrated in FIG. 1. For example, when a newoperation needs to be executed within the EMS, it typically requires development on an EMS side. Currently, in certain existing systems, all Day 2 operations are conducted directly through the EMS. In this framework, configuration tasks are primarily addressed during the Day 1 / Day 2 phases, where configurations are generated from the CM backend and transmitted to the EMS, which then propagates these configurations to the respective NFs. This setup allowed network administrators to manage configurations, monitor performance, and address faults effectively. However, several problems are encountered in certain existing systems, which are mentioned below.

[0017] The EMS is being phased out from certain existing systems due to limitations in scalability, flexibility, and integration. As networks grow more complex, managing various functions efficiently poses a challenge for the EMS. The rigid design hinders the deployment of modern technologies, while reliance on proprietary protocols complicates compatibility with third-party systems. These issues result in higher operational costs and reduced responsiveness to changing network needs. Additionally, another problem identified herein, certain existing systems do not provide users with direct visibility of Remote Procedure Calls (RPCs) for editing through the user interface.

[0018] Consequently, there is a requirement for alternative technologies, leading to the development of control operations that manage network functions in a more modular and scalable way, enhancing orchestration, automation, and real-time analytics capabilities, as discussed throughout the disclosure.

[0019] In one or more embodiments, the disclosed method introduces a control operation that enhances flexibility by enabling the creation of RPC-based templates tailored to specific operations, which can be reused according to user requirements, as described in conjunction with FIG. 2 to FIG. 7. This control operation is categorized into two distinct functions such as a define operation and an execute operation. The define operation facilitates the creation of one or more templates, while the execute operation is responsible for transmitting the files to one or more Network Functions (NFs). This approach effectively replaces manual processes and establishes a framework that allows RPC execution across multiple Network Elements (NEs).

[0020] A notable advancement over existing systems is the incorporation of a Graphical User Interface (GUI) that enables users to visualize RPCs and make necessary modifications, as described in conjunction with FIGS. 5A, 5B, 5C, 5D, and 5E. This user-friendly interface serves as a versatile operational field, allowing a wide range of operations to be performed and functioning as a generic framework within the system. In contrast to existing systems, which relied on EMS connectivity for configuration and related functions, the disclosed method leverages a Configuration Management (CM) module with Netconf connectivity to the respective Service-Based Network Functions (SB NFs). In addition, the disclosed method supports both Transport Layer Security (TLS) and Secure Shell (SSH) protocols, as described in conjunction with FIGS. 3, 4A, and 4B. The CM module executes the appropriate RPCs to implement changes seamlessly. Furthermore, the disclosed method is designed to accommodate new functionalities without necessitating additional development; users can directly create the relevant templates and execute the corresponding RPCs as needed, as described in conjunction with FIGS. 5A, 5B, 5C, 5D, and 5E.

[0021] Referring now to the drawings, and more particularly to FIGS. 2 to 7, where similar reference characters denote corresponding features consistently throughout the figures, there are shown preferred embodiments.

[0022] FIG. 2 illustrates a block diagram of an electronic device 200 for managing one or more control operations, according to an embodiment as disclosed herein. Examples of the electronic device 200 include, but are not limited to a smartphone, a tablet computer, a Personal Digital Assistance (PDA), etc.

[0023] In an embodiment, the electronic device 200 comprises a system 201. The system 201 may include a memory 210, a processor 220, a communicator 230, and a configuration module 240. In one or more embodiments, the system 201 may be implemented on one or multiple electronic devices (not shown in FIG. 2).

[0024] In one or more embodiments, the memory 210 stores instructions to be executed by the processor 220 for managing one or more control operations, as discussed throughout the disclosure. The memory 210 may include non-volatile storage elements. Examples of such nonvolatile storage elements may include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories. In addition, the memory 210 may, in some examples, be considered a non-transitory storage medium. The term “non-transitory” may indicate that the storage medium is not embodied in a carrier wave or a propagated signal. However, the term “non-transitory” should not be interpreted that the memory 210 is non-movable. In some examples, the memory 210 can be configured to store larger amounts of information than thememory. In certain examples, a non-transitory storage medium may store data that can, over time, change (e.g., in Random Access Memory (RAM) or cache). The memory 210 can be an internal storage unit, or it can be an external storage unit of the electronic device 200, a cloud storage, or any other type of external storage.

[0025] In one or more embodiments, the processor 220 communicates with the memory 210, the communicator 230, and the configuration module 240. The processor 220 is configured to execute instructions stored in the memory 210 and to perform various processes for managing one or more control operations, as discussed throughout the disclosure. The processor 220 may include one or a plurality of processors, a general-purpose processor, such as a Central Processing Unit (CPU), an Application Processor (AP), or the like, a graphics-only processing unit such as a Graphics Processing Unit (GPU), a Visual Processing Unit (VPU), and / or an Artificial Intelligence (Al) dedicated processor such as a Neural Processing Unit (NPU).

[0026] In one or more embodiments, the communicator 230 is configured for communicating internally between internal hardware components and with external devices (e.g., server) via one or more networks (e.g., radio technology). The communicator 230 includes an electronic circuit specific to a standard that enables wired or wireless communication.

[0027] In one or more embodiments, the system 201 may include a display module (not shown in FIG.2). The display module can accept user inputs and is made of a Liquid Crystal Display (LCD), a Light Emitting Diode (LED), an Organic Light Emitting Diode (OLED), or another type of display. The user inputs may include, but are not limited to, touch, swipe, drag, gesture, and so on.

[0028] In one or more embodiments, the configuration module 240 is implemented by processing circuitry such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits, or the like, and may optionally be driven by firmware. The circuits may, for example, be embodied in one or more semiconductor chips, or on substrate supports such as printed circuit boards and the like.

[0029] In one or more embodiments, the configuration module 240 is configured to manage one or more control operations comprising at least one of a first operational state and a second operational state. The first operational state is a define operation and the secondoperational state is an execution operation. The define operation and the execution operation may include multiple operations, as described in conjunction with FIG. 3 and FIGS. 5A, 5B, 5C, 5D, and 5E.

[0030] In one or more embodiments, the configuration module 240 is further configured to generate one or more Remote Procedure Calls (RPC) based templates tailored to operational requirements in the first operational state. To generate the one or more RPCs, the configuration module 240 may execute multiple operations, which are given below.

[0031] The configuration module 240 may receive one or more configuration parameters from a user. Examples of the one or more configuration parameters may include, but are not limited to, domain information, vendor information, technology information, software version information, and operation name information, as illustrated in FIGS. 5B, 5C, 5D, and 5E. Based on the one or more received configuration parameters, the configuration module 240 may configure one or more operational definitions that include a generation of one or more templates, wherein each of the one or more templates includes a predefined RPC, as illustrated in FIGS. 5C and 5D.

[0032] In one or more embodiments, the configuration module 240 is further configured to transmit one or more execution files in the second operational state. The one or more execution files are transmitted through one or more southbound interfaces to at least one network node, to execute at least one respective operation based on the one or more generated RPC-based templates. Examples of network nodes may include, but are not limited to, a Centralized Unit (CU), a Distribution Unit (DU), and a Network Function (NF) node.

[0033] In one or more embodiments, the configuration module 240 is further configured to receive one or more post-execution feedbacks from the at least one network node, as described in conjunction with FIG. 4A. The configuration module 240 is further configured to perform at least one action to manage the one or more control operations based on the one or more received post-execution feedbacks. The one or more post-execution feedbacks may include, but are not limited to, performance metrics and error reports related to one or more executed RPCs associated with the at least one network node. In one embodiment, the at least one action may include regenerating, upon receiving one or more post-execution feedbacks, the one or RPC-based templates tailored to the operational requirements. In one embodiment, the at least one action may include retransmitting one or more execution files through the oneor more southbound interfaces to the at least one network node, to execute the at least one respective operation based on the one or more regenerated RPC-based templates.

[0034] In one or more embodiments, the configuration module 240 may provide a Graphical User Interface (GUI) to display the one or more RPC-based templates for user interaction and configuration, as described in conjunction with FIGS. 5A, 5B, 5C, 5D, and 5E.

[0035] Although FIG. 2 shows various hardware components of the electronic device 200, but it is to be understood that other embodiments are not limited thereon. In other embodiments, the electronic device 200 may include less or more number of components. Further, the labels or names of the components are used only for illustrative purposes and do not limit the scope of the disclosure. One or more components can be combined to perform the same or substantially similar functions to manage the one or more control operations.

[0036] FIG. 3 illustrates one or more operations associated with the first operational state and the second operational state, according to an embodiment as disclosed herein.

[0037] At operations 301-302, the method defines a comprehensive functionality wherein the users can access a configuration manager Graphical User Interface (GUI) associated with the configuration module 240. At operations 303-304, within this interface, the users can navigate to a control operation module, which encompasses two distinct submodules such as define operations and execute operations, which may relate to FIG. 5A.

[0038] In the context of the “define operations” submodule (during the first operational state), at operation 305, the method facilitates the addition of one or more new operations, each accompanied by one or more Remote Procedure Calls (RPCs). At operation 306, subsequently, the method incorporates a mechanism for saving these newly added operations within the configuration management system as one or more RPC-based templates. At operation 307, furthermore, the method enables users to execute various operations on the newly created RPCbased templates, thereby configuring the operational definitions accordingly. Specifically, users with the requisite access privileges can define operations by creating relevant templates that incorporate the associated RPCs, which may relate to FIGS. 5B, 5C and 5D.

[0039] Consider an example scenario where a user intends to restart a virtual Centralized Unit (vCU), a template can be established that aligns with the pertinent domain information, vendor information, and technology information, including the corresponding RPC (e.g., an XML file) within a definition field. These templates can then be saved and reused as necessary across multiple vCUs.

[0040] Consider another example scenario where a network administrator is tasked with managing multiple routers across a large enterprise network. In this example scenario, the network administrator opens the configuration manager GUI and navigates to the control operation module. Within the control operation module, the network administrator selects the “Define Operation” submodule. The network administrator decides to create a new operation for updating a firmware on all routers. The network administrator adds a new operation titled “Firmware Update” and includes several RPCs that correspond to the firmware update process for different router models. After defining the operation, the network administrator saves it as an RPC-based template named “Router Firmware Update Template”. When it is time to perform the firmware update, the network administrator selects the template and executes it across all relevant routers, ensuring consistency and efficiency in the update process.

[0041] Consider another example scenario where a cloud operation engineer is responsible for managing a fleet of virtual machines (VMs) in a cloud environment. In this example scenario, the cloud operation engineer accesses the configuration manager GUI and goes to the Control operation module. The cloud operation engineer selects the “Define Operation” submodule to create a new operation for scaling VMs up or down based on demand. The cloud operation engineer defines an operation called “Scale VM”, which includes RPCs for both increasing and decreasing the resources allocated to the VMs (e.g., CPU and memory adjustments). This operation is saved as an RPC-based template named “VM Scaling Template”. During peak usage, the cloud operation engineer utilizes the template to quickly scale up the resources for multiple VMs, ensuring optimal performance. Conversely, during off-peak hours, the cloud operation engineer can use the same template to scale down resources, optimizing costs.

[0042] During the second operational state: at operation 308, once the one or more operations are defined, they can be executed on the relevant Network Functions (NF) or UHNs. The execute operation involves selecting at least one network node for the operation’s execution. At operation 309, additionally, the execute operation encompasses the selection of at least one operation from a predefined set of RPC-based templates generated during the first operational state. At operation 310, the execute operation also allows for the editing or updating of one or more RPCs based on user requirements. At operations 311-312, following the above- mentioned operations, the selected operation is executed by performing at least one action (e.g.,pressing an execute button), and the status of the executed operation is monitored, which may relate to FIG. 5E.

[0043] The framework for executing operations empowers users to perform the respective operations on the NF while receiving feedback from the corresponding endpoints. In the disclosed method, the users have the capability to edit the relevant RPC (e.g., XML file), and upon finalization, they can execute the respective RPC. Once executed, the users receive feedback from the other end, such as the vCU in 4G scenarios and the vCU or DU in 5G scenarios. In 4G, the CM module 240 connects with the CU, whereas in 5G, it connects directly with both the CU and DU. This ability to edit RPCs and the provision of a generic framework represents a novel advancement in Configuration Management capabilities.

[0044] Consider an example scenario where a telecommunications company is implementing a new feature in a 4G network. In this example scenario, a network engineer defines a new operation to adjust one or more Quality of Service (QoS) parameters for specific users. Then, the network engineer selects the relevant network node, such as an eNodeB (base station), for executing the operation. The network engineer chooses an RPC-based template that outlines the necessary adjustments for the one or more QoS parameters. The network engineer edits the RPC XML file to specify the desired QoS settings based on user feedback. Once the desired QoS settings are finalized, the RPC is executed to apply the changes. After execution, the network engineer then monitors feedback from the vCU, confirming that the adjustments of the one or more QoS parameters have been successfully implemented.

[0045] Consider another example scenario where a service provider is rolling out a new 5G service in a metropolitan area. In this example scenario, a deployment engineer defines an operation to enable network slicing for enhanced service delivery. Then, the deployment engineer selects the appropriate network nodes, including both the CU and DU, for executing the operation. The deployment engineer selects an RPC-based template designed for network slicing configurations. The deployment engineer modifies the RPC XML file to include specific parameters for the new service offerings. After finalizing the edits, the RPC is executed to activate the network slices. The deployment engineer then monitors feedback from both the vCU and DU to ensure that the network slices are functioning as intended and meet performance expectations.

[0046] FIGS. 4A-4B sequence flow diagrams illustrating a method for managing, by the configuration module 240 of the electronic device 200, the one or more control operations,according to an embodiment as disclosed herein. The configuration module 240 comprises three distinct sub-modules: a Configuration Management User Interface (CM UI), a Configuration Management Backend (CM Backend), and a Configuration Management Netconf (CM Netconf). The method may execute multiple operations to manage the one or more control operations, which are given below.

[0047] Referring to FIG. 4A: at operation 401, the CM UI initiates a request to the CM Backend to create and store a backend template. At operation 402, upon receipt of this request, the CM Backend retrieves the necessary stored templates required for execution and forwards them to the CM UI. At operation 403, subsequently, the CM UI issues an execution request targeting the respective Network Element (NE) via the CM Backend. At operation 404, the CM Backend then constructs an RPC request and transmits it to the CM Netconf. This RPC request is processed through the Netconf microservice. At operation 405, the CM Netconf forwards the received RPC request to the appropriate southbound CU or DU 400 A for execution (e.g., at least one network node). At operations 406-407, upon completion of the execution, the respective southbound CU / DU 400A sends a response (e.g., one or more post-execution feedbacks) back to the CM Netconf. The CM Netconf subsequently relays the Network Function (NF) response to the CM Backend. At operation 408, finally, the CM Backend updates the CM UI with the response, completing the configuration process.

[0048] Referring to FIG. 4B: at operation 409, the configuration module 240 operates through a secure TLS / SSH connection between the CM Netconf and the NF 400B (e.g., at least one network node). At operation 410, the CM UI allows users to create various templates. At operation 411, the CM Backend subsequently requests the execution of the respective action on the designated southbound device. At operation 412, the CM Netconf takes over by pushing the appropriate configuration or RPC request to the NF 400B via the Netconf protocol, ensuring secure and efficient communication through the established TLS / SSH connection. This framework facilitates seamless interactions between the CM UI, CM Backend, and CM Netconf, enabling effective configuration management across network functions while maintaining secure connections.

[0049] FIGS. 5A, 5B, 5C, 5D, and 5E illustrate one or more exemplary operations associated with the configuration module 240.

[0050] FIG. 5A illustrates a scenario in which the user can select one or more functionalities associated with the configuration module 240. Examples of these functionalitiesmay encompass, but are not limited to, configuration comparison, event planning, library access, network topology visualization, template management, backup restoration, and control operations. Upon the selection of the control operation 501, two sub-modules are presented on the display of the electronic device 200, as the “Define Operation” and the “Execute Operation”.

[0051] FIG. 5B illustrates the functionalities 502 associated with the “Define Operation” when the user selects this define operation from the control operation. The available functionalities may include a range of filtering options 503 (i.e., configuration parameters) and a user-defined list of operations / templates, which may span multiple pages (e.g., up to 12 pages). The various filtering options 503 may include, but are not limited to, domain information, vendor information, technology information, and software versioning information. Based on the user’s selection of these various filters, the corresponding list of operations / templates is dynamically displayed on the screen of the electronic device 200.

[0052] FIG. 5C illustrates the functionalities 504 associated with the “Define Operation” when the user intends to add a new operation within the control option. To facilitate the addition of a new operation, the user is required to input fundamental details pertinent to one or more configuration parameters. Furthermore, the user may define a new RPC for the newly added operation and save this configuration for future reference.

[0053] FIG. 5D illustrates the functionalities 505 associated with the “Define Operation” when the user seeks to edit an existing operation within the control option. To initiate the editing process, the user may select the relevant basic details associated with the one or more configuration parameters. Upon selection, the corresponding RPC may be displayed on the screen of the electronic device 200. The user may then modify the displayed RPC in accordance with specific requirements and save the changes for future use. Additionally, the user has the option to delete any existing operations under the “Define Operation”, although this functionality is not illustrated in the FIG. 5D.

[0054] FIG. 5E illustrates the functionalities 506 associated with the “Execute Operation” when the user selects this option from the control option, either following the completion of procedures related to the “Define Operation” or independently. The user may perform a variety of actions, including selecting one or more network nodes (e.g., NF / UHNs) for the execution of operations. Alternatively, the user may choose from a predefined set of RPC-based templates generated during the first operational state. Additionally, the user has the capability to edit or update one or more RPCs in alignment with their requirements. The usermay also execute the selected operations and monitor the status of one or more executed operations in real-time.

[0055] FIG. 6 is a flow diagram illustrating a method 600 for managing the one or more control operations, according to an embodiment as disclosed herein. The method 600 may execute multiple operations to manage the one or more control operations, which are given below.

[0056] At step 601, the method includes managing, at the CM module 240, the one or more control operations include the first operational state and the second operational state. At step 602, the method includes generating, in the first operational state, the one or more RPC based templates tailored to operational requirements. At step 603, the method includes transmitting, in the second operational state, the one or more execution files, through one or more southbound interfaces to the at least one network node, to execute at least one respective operation based on the one or more generated RPC-based templates. Further, a detailed description related to the various steps of FIG. 6 is covered in the description related to FIG. 2, FIG. 3, FIGS. 4A-4B, FIGS. 5A, 5B, 5C, 5D and 5E, and is omitted herein for the sake of brevity.

[0057] FIG. 7 illustrates a diagram of example components of a system 700, according to an embodiment as disclosed herein. As shown in FIG. 7, the system 700 comprises a processor 710, a memory 720, a storage component 730, an input component 740, an output component 750, a communication interface 760, and a bus 770. In one embodiment, the system 700 may relate to the electronic device 200, or any other network device.

[0058] The processor 710, as used herein, means any type of computational circuit that may comprise hardware elements and software elements. The processor 710 may be embodied as a multi-core processor, a single core processor, or a combination of one or more multi-core processors and / or one or more single core processors, a distributed processing system, or the like. The processor 710 may be a Central Processing Unit (CPU), a graphics processing unit (GPU), an accelerated processing unit (APU), an application-specific integrated circuit (ASIC), or another type of processing component.

[0059] The memory 720 includes a non-transitory computer readable medium. Memory 720 includes a random-access memory (RAM), a read only memory (ROM), and / or another type of dynamic or static storage device (e.g., a flash memory, a magnetic memory, and / or an optical memory) that stores information and / or instructions for use by processor 710.The memory 720 comprises machine-readable instructions which are executable by the processor 710. These machine-readable instructions when executed by the processor 710 cause the processor 710 to perform one or more method steps of an embodiment described above.

[0060] The storage component 730 stores information and / or software related to the operation and use of the system 700. For example, the storage component 730 may include a hard disk (e.g., a magnetic disk, an optical disk, a magneto-optic disk, and / or a solid-state disk), a compact disc (CD), a digital versatile disc (DVD), a floppy disk, a cartridge, a magnetic tape, and / or another type of non-transitory computer-readable medium, along with a corresponding drive.

[0061] The input component 740 is configured to receive information, such as user input. For example, the input component 740 may include, but not be limited to, a touch screen display, a keyboard, a keypad, a mouse, a button, a switch, and / or a microphone. Additionally, or alternatively, the input component 740 may include a sensor for sensing information (e.g., a global positioning system (GPS), an accelerometer, a gyroscope, and / or an actuator).

[0062] The output component 750 is configured to provide output information from the system 700. For example, the output component 750 may be, but is not limited to, a display, a speaker, instructions to an external device, and / or one or more light-emitting diodes (LEDs).

[0063] The communication interface 760 is an interface that provides a communication connection to other devices, such as external devices and internal devices. The connection by the communication interface 760 can be a wired connection, a wireless connection, or a combination of wired and wireless connections, and can be a direct connection or an indirect connection via a communication network that exists between the system 700 and other devices. In other words, the standard of the communication interface 760 is not limited.

[0064] The bus 770 acts as an interconnect between the processor 710, the memory 720, the storage component 730, the input component 740, the output component 750, and the communication interface 760 of the system 700. The bus 770 may include a wired interconnection or a wireless interconnection.

[0065] The number and arrangement of components shown in FIG. 7 are provided as an example. In practice, the system 700 may include additional components, fewer components, different components, or differently arranged components than those shown in FIG. 7. Additionally, or alternatively, a set of components (e.g., one or more components) of the system 700 may perform one or more functions described as being performed by another set ofcomponents of the system 700. Further, one or more method steps described in any of the embodiments may be performed utilizing the system 700 in communication with one another.

[0066] The disclosed method / system / apparatus (e.g., CM module 240) has several advantages over the existing mechanism, for example, which are stated below. a. The disclosed method operates as a universal architecture applicable across various domains, vendors, and technologies. The disclosed method enables the execution of operations from a centralized platform, facilitating interoperability and integration. For instance, a telecommunications company utilizes this disclosed method to manage services across different network technologies (e.g., 4G, 5G). The operations for service provisioning, monitoring, and management can be executed from a single dashboard, regardless of the underlying technology or vendor. b. The disclosed method provides a graphical representation of the XML Remote Procedure Calls (RPCs) being executed against the respective NFs. This visualization aids users in understanding the interactions between various network devices. For instance, a network engineer can view a real-time graphical map showing one or more active XML / RPC calls made to different NFs within the system. This allows for quick identification of bottlenecks or failures in service requests. c. The users are empowered with the capability to modify the RPCs according to the specific requirements of the respective NFs. This flexibility enhances adaptability to changing operational needs and enhances user experience and operational efficiency. For instance, a developer needs to update an RPC to include additional parameters for a new service feature. The developer can easily modify the existing RPC without the need for extensive coding or system downtime. d. The disclosed method allows users to define various operations, promoting the reuse of templates as needed. This capability streamlines the development process and enhances efficiency. For instance, a developer can create a template for a common service operation, such as user authentication. This template can be reused across multiple projects, reducing the time required to implement similar functionalities.e. By functioning as a generic framework tailored to specific technologies, the disclosed method serves as a comprehensive solution, thereby minimizing operational costs associated with maintaining multiple disparate systems. For instance, a multi-service provider can consolidate their service management tools into one generic framework, reducing licensing fees and maintenance costs associated with multiple vendor solutions. f. The disclosed method incorporates a feedback mechanism within the same user interface, enabling users to receive immediate results and insights. This feature enhances the ability to track performance and make informed decisions swiftly. For instance, after executing an RPC to provision a new service, the user receives instant feedback on the success or failure of the operation, along with performance metrics. This allows for quick troubleshooting and adjustments to improve service delivery.

[0067] According to one embodiment of the present disclosure, a method is disclosed. The method includes managing, at the configuration management module 240, the one or more control operations comprising at least one of the first operational state and the second operational state. The method further includes generating, in the first operational state, the one or more RPC based templates tailored to operational requirements. The method further includes transmitting, in the second operational state, the one or more execution files. The one or more execution files are transmitted through the one or more southbound interfaces to the at least one network node, to execute the at least one respective operation based on the one or more generated RPC-based templates.

[0068] The method described in para

[0066] , the method includes receiving, at the configuration management module 240, the one or more post-execution feedbacks from the at least one network node. The method further includes performing, based on the one or more received post-execution feedbacks, the at least one action to manage the one or more control operations.

[0069] The method described in any one of paragraphs

[0066] -

[0067] , the method includes generating, in the first operational state, the one or more RPC-based templates tailored to the operational requirements comprises receiving, at the configuration management module 240, the one or more configuration parameters from the user. The one or more configuration parameters comprise one or more of domain information, vendor information, technologyinformation, software version information, and operation name information. The method further includes configuring, based on the one or more received configuration parameters, the one or more operational definitions that include the generation of one or more templates. Each of the one or more templates includes the predefined RPC.

[0070] The method described in any one of paragraphs

[0066] -

[0068] , during the first operational state, the method includes one or more operations. In one embodiment, the operation includes adding, at the configuration management module 240, the one or more new operations along with the one or more RPCs. In another embodiment, the operation includes saving, in the configuration management module 240, the one or more added new operations as one or more new RPC-based templates. In another embodiment, the operation includes performing the one or more operations on the one or more new RPC-based templates to configure the one or more operational definitions.

[0071] The method described in any one of paragraphs

[0066] -

[0068] , during the second operational state the method includes one or more operations. In one embodiment, the operation includes selecting the at least one network node for operation execution. In another embodiment, the operation includes selecting at least one operation from a predefined set of RPC-based templates generated during the first operational state. In another embodiment, the operation includes editing or updating the one or more RPCs based on the requirement of the user. In another embodiment, the operation includes executing the at least one selected operation. In another embodiment, the operation includes monitoring one or more statuses of the at least one executed operation.

[0072] The method described in any one of paragraphs

[0066] -

[0070] , for the at least one action the method includes regenerating, upon receiving one or more post-execution feedbacks, the one or RPC-based templates tailored to the operational requirements. The method further includes retransmitting the one or more execution files through the one or more southbound interfaces to the at least one network node. The one or more execution files are utilized for executing the at least one respective operation based on the one or more regenerated RPC-based templates.

[0073] The method described in any one of paragraphs

[0066] -

[0071] , the method includes providing, at the configuration management module 240, the GUI to display the one or more RPC-based templates for the user interaction and configuration.

[0074] The method described in any one of paragraphs

[0066] -

[0072] , the first operational state is the define operation and the second operational state is the execution operation.

[0075] The method described in any one of paragraphs

[0066] -

[0073] , the at least one network node comprises at least one of the CU, the DU, and the NF node.

[0076] The method described in any one of paragraphs

[0066] -

[0074] , the one or more post-execution feedbacks comprise the performance metrics and the error reports related to the one or more executed RPCs associated with the at least one network node.

[0077] According to one embodiment of the present disclosure, the apparatus is disclosed. The apparatus is configured to manage, at a configuration management, one or more control operations comprising at least one of a first operational state and a second operational state. The apparatus is further configured to generate, in the first operational state, one or more Remote Procedure Call (RPC) based templates tailored to operational requirements. The apparatus is further configured to transmit, in the second operational state, one or more execution files. The one or more execution files are transmitted through one or more southbound interfaces to at least one network node, to execute at least one respective operation based on the one or more generated RPC-based templates.

[0078] The embodiments disclosed herein can be implemented through at least one software program running on at least one hardware device and performing network management functions to control the elements. The elements can be at least one of a hardware device or a combination of hardware devices and software modules.

[0079] While specific language has been used to describe the disclosure, any limitations arising on account of the same are not intended. As would be apparent to a person in the art, various working modifications may be made to the method in order to implement the inventive concept as taught herein.

[0080] The drawings and the forgoing description give examples of embodiments. Those skilled in the art will appreciate that one or more of the described elements may well be combined into a single functional element. Alternatively, certain elements may be split into multiple functional elements. Elements from one embodiment may be added to another embodiment. For example, orders of processes described herein may be changed and are not limited to the manner described herein.

[0081] Moreover, the actions of any flow diagram need not be implemented in the order shown; nor do all of the acts necessarily need to be performed. Also, those acts that are not dependent on other acts may be performed in parallel with the other acts. The scope of embodiments is by no means limited by these specific examples. Numerous variations, whether explicitly given in the specification or not, such as differences in structure, dimension, and use of material, are possible. The scope of embodiments is at least as broad as given by the following claims.

[0082] Benefits, other advantages, and solutions to problems have been described above with regard to specific embodiments. However, the benefits, advantages, solutions to problems, and any component(s) that may cause any benefit, advantage, or solution to occur or become more pronounced are not to be construed as a critical, required, or essential feature or component of any or all the claims.

[0083] The foregoing description of the specific embodiments will so fully reveal the general nature of the embodiments herein that others can, by applying current knowledge, readily modify and / or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications should and are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while the embodiments herein have been described in terms of at least one embodiment, those skilled in the art will recognize that the embodiments herein can be practiced with modification within the spirit and scope of the embodiments as described herein.

Claims

CLAIMSWe claim:

1. A method (600) comprises: managing (601), at a configuration management (240), one or more control operations comprise at least one of a first operational state and a second operational state; generating (602), in the first operational state, one or more Remote Procedure Call (RPC) based templates tailored to operational requirements; and transmitting (603), in the second operational state, one or more execution files, through one or more southbound interfaces to at least one network node, to execute at least one respective operation based on the one or more generated RPC-based templates.

2. The method (600) according to claim 1, further comprising: receiving, at the configuration management (240), one or more post-execution feedbacks from the at least one network node; and performing, based on the one or more received post-execution feedbacks, at least one action to manage the one or more control operations.

3. The method (600) according to claim 1 , wherein generating, in the first operational state, the one or more RPC-based templates tailored to the operational requirements comprises: receiving, at the configuration management (240), one or more configuration parameters from a user, wherein the one or more configuration parameters comprise one or more of domain information, vendor information, technology information, software version information, and operation name information; configuring, based on the one or more received configuration parameters, one or more operational definitions that include a generation of one or more templates, wherein each of the one or more template include a predefined RPC.

4. The method (600) according to claim 3, wherein during the first operational state, the method comprises at least one of:adding, at the configuration management (240), one or more new operations along with one or more RPCs; saving, in the configuration management (240), the one or more added new operations as one or more new RPC-based templates; or performing one or more operations on the one or more new RPC-based templates to configure the one or more operational definitions.

5. The method (600) according to claim 1, wherein during the second operational state, the method comprises at least one of: selecting the at least one network node for operation execution; selecting at least one operation from a predefined set of RPC-based templates generated during the first operational state; editing or updating one or more RPCs based on a requirement of a user; executing the at least one selected operation; and monitoring one or more statuses of the at least one executed operation.

6. The method (600) according to claim 2, wherein the at least one action comprises: regenerating, upon receiving one or more post-execution feedbacks, the one or RPC-based templates tailored to the operational requirements; and retransmitting one or more execution files through the one or more southbound interfaces to the at least one network node, to execute the at least one respective operation based on the one or more regenerated RPC-based templates.

7. The method (600) according to claim 1, further comprising: providing , at the configuration management (240), a Graphical User Interface (GUI) to display the one or more RPC-based templates for user interaction and configuration.

8. The method (600) according to claim 1, wherein the first operational state is a define operation and the second operational state is an execution operation.

9. The method (600) according to claim 1, wherein the at least one network node comprises at least one of a Centralized Unit (CU), a Distribution Unit (DU), and a Network Function (NF) node.

10. The method (600) according to claim 2, wherein the one or more post-execution feedbacks comprises performance metrics and error reports related to one or more executed RPCs associated with the at least one network node.

11. An apparatus, wherein the apparatus is configured to: manage, at a configuration management (240), one or more control operations comprise at least one of a first operational state and a second operational state; generate, in the first operational state, one or more Remote Procedure Call (RPC) based templates tailored to operational requirements; and transmit, in the second operational state, one or more execution files, through one or more southbound interfaces to at least one network node, to execute at least one respective operation based on the one or more generated RPC-based templates.

12. The apparatus according to claim 11, the apparatus is further configured to: receive, at the configuration management (240), one or more post-execution feedbacks from the at least one network node; and perform, based on the one or more received post-execution feedbacks, at least one action to manage the one or more control operations.

13. The apparatus according to claim 11, wherein to generate, in the first operational state, the one or more RPC-based templates tailored to the operational requirements, the apparatus is configured to: receive, at the configuration management (240), one or more configuration parameters from a user, wherein the one or more configuration parameters comprise one or more of domain information, vendor information, technology information, software version information, and operation name information;configure, based on the one or more received configuration parameters, one or more operational definitions that include a generation of one or more templates, wherein each of the one or more template include a predefined RPC.

14. The apparatus according to claim 13, wherein during the first operational state, the apparatus is configured to, at least one of: add, at the configuration management (240), one or more new operations along with one or more RPCs; save, in the configuration management (240), the one or more added new operations as one or more new RPC-based templates; or perform one or more operations on the one or more new RPC-based templates to configure the one or more operational definitions.

15. The apparatus according to claim 11, wherein during the second operational state, the apparatus is configured to, at least one of: select the at least one network node for operation execution; select at least one operation from a predefined set of RPC-based templates generated during the first operational state; edit or update one or more RPCs based on a requirement of a user; execute the at least one selected operation; and monitor one or more statuses of the at least one executed operation.

16. The apparatus according to claim 12, wherein the at least one action, the apparatus is configured to: regenerate, upon receiving one or more post-execution feedbacks, the one or RPC-based templates tailored to the operational requirements; and retransmit one or more execution files through the one or more southbound interfaces to the at least one network node, to execute the at least one respective operation based on the one or more regenerated RPC-based templates.

17. The apparatus according to claim 11, the apparatus is further configured to:providing , at the configuration management (240), a Graphical User Interface (GUI) to display the one or more RPC-based templates for user interaction and configuration.

18. The apparatus according to claim 11, wherein the first operational state is a define operation and the second operational state is an execution operation; and wherein the at least one network node comprises at least one of a Centralized Unit (CU), a Distribution Unit (DU), and a Network Function (NF) node.

19. The apparatus according to claim 12, wherein the one or more post-execution feedbacks comprises performance metrics and error reports related to one or more executed RPCs associated with the at least one network node.

20. A non-transitory computer-readable medium storing instructions, the instructions comprising: one or more instructions that, when executed by an apparatus, the apparatus comprising one or more processors, cause the one or more processors to: manage, at a configuration management (240), one or more control operations comprise at least one of a first operational state and a second operational state; generate, in the first operational state, one or more Remote Procedure Call (RPC) based templates tailored to operational requirements; and transmit, in the second operational state, one or more execution files, through one or more southbound interfaces to at least one network node, to execute at least one respective operation based on the one or more generated RPC-based templates.

Images