System and method for managing network configuration of a network
Patent Information
- Authority / Receiving Office
- EP · EP
- Patent Type
- Applications
- Current Assignee / Owner
- JIO PLATFORMS LTD
- Filing Date
- 2024-08-05
- Publication Date
- 2026-07-01
AI Technical Summary
Current network configuration management systems face challenges in efficiently managing network configurations across multiple vendors, leading to vendor-specific dependencies, inconsistent configurations, and increased operational complexity for telecommunication operators.
A centralized network configuration node is deployed to manage and distribute configuration parameters to various network functions, enabling self-configuration and uniformity across different vendors, while also providing a standardized interface for integration and automation.
The solution enables efficient, automated, and vendor-agnostic network configuration management, reducing manual intervention, minimizing integration efforts, and facilitating faster network deployments and upgrades.
Smart Images

Figure IN2024051459_27022025_PF_FP_ABST
Abstract
Description
SYSTEM AND METHOD FOR MANAGING NETWORK CONFIGURATION OF A NETWORKRESERVATION 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 (herein after 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 to a field of a wireless network, and specifically to a system and a method for managing network configuration of a network.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] The term ‘network function’ as used herein, refers to a functional building block within a telecommunications network that performs specific network functions. The network function can be deployed at various locations such as edge compute sites, central sites, public cloud, or private cloud environments, and can originate from different vendors.
[0005] The term ‘network configuration node or ‘a network configuration function’ as used herein, refers to a centralized server or component responsible for storing, managing, and distributing configuration parameters to various network functions within a network. The network configuration node provides a unified interface for configuration management, ensuring consistency and reducing vendorspecific dependencies.
[0006] The term ‘Management and Orchestration’ as used herein, refers to a framework defined by the European Telecommunications Standards Institute (ETSI) for managing and orchestrating the network functions in a virtualized network environment, including tasks such as resource allocation, lifecycle management, and monitoring the performance and configuration parameters of the network functions.
[0007] The term ‘network configuration parameters’ as used herein, refers to specific settings, values, and instructions required to configure and operate the network functions within a telecommunications network. These network configuration parameters may include both immutable (unchanging) and mutable (site-specific) settings.BACKGROUND
[0008] 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 only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of prior art.
[0009] In general, 5thGeneration (5G) core network, 6thGeneration (6G) core network, or any other generation network may be deployed across multiple locations, such as edge compute sites, central sites, public cloud, and private cloud installations. Multiple Network Functions from different vendors or manufacturers may be in communication with the core network.
[0010] Currently, whenever a network function from a new vendor establishes connection with the core network, an Element Management System (EMS) may be introduced by the vendor, and the EMS may also be onboarded to the network, which may be troublesome for operators. Also, provisioning and configuration parameters of different network functions may vary with vendors. Therefore, for each vendor’s network function, a vendor dependent configurationsystem has to be introduced in the network. Telecommunication operator operations team has to deal with vendor specific configuration applications, tools, and methodologies. Even for a 3rdGeneration Partnership Project (3GPP) defined signalling parameters, the corresponding configuration parameter syntax varies from vendor to vendor.
[0011] 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.OBJECTS OF THE PRESENT DISCLOSURE
[0012] Some of the objects of the present disclosure, which at least one embodiment herein satisfies are as listed herein below.
[0013] An object of the present disclosure is to provide a system and a method for managing network configuration of a network.
[0014] An object of the present disclosure is to provide a system and a method to deploy a single network configuration node, (for example, a network configuration function) for configuring different types of network functions.
[0015] An object of the present disclosure is to deploy the single network configuration node in the network, so that each network configuration function may pull its configuration parameters and self-configure itself, ensuring uniformity of configuration parameters and methodology across different network function vendors.
[0016] An objective of the present disclosure is to enable the single network configuration node to push global parameters to all network functions simultaneously and efficiently.
[0017] An objective of the present disclosure is to configure a highly distributed network function in a shorter amount of time using the single configuration node.
[0018] An objective of the present disclosure is to perform upgrades across a large number of sites more quickly.
[0019] An objective of the present disclosure is to deploy a standardized interface between the network configuration node and the network functions, which minimizes integration effort and time.
[0020] An objective of the present disclosure is to deploy the single network configuration node so that network function configuration may be automated and made vendor-agnostic.SUMMARY OF THE DISCLOSURE
[0021] In an exemplary embodiment, a method for managing network configuration of a network. The method includes receiving, by a server, a primary request for one or more network configuration parameters from at least one network function via a primary interface. The one or more network configuration parameters are associated with the at least one network function. The method includes providing, by the server, the one or more network configuration parameters to the at least one network function based on the primary request. The method includes enabling, by the server, the at least one network function to self-configure in response to providing the one or more network configuration parameters.
[0022] In some embodiments, the method further includes receiving, by the server, a secondary request for the one or more configuration parameters associated with the at least one network function from a management unit via a secondary interface, and providing, by the server, the one or more configuration parameters to the management unit based on the secondary request.
[0023] In some embodiments, the method further includes monitoring, by the management unit, the one or more network configuration parameters associated with the at least one network function in response to providing the requested one or more configuration parameters.
[0024] In some embodiments, at least one of: the primary interface and the secondary interface use a hypertext transfer protocol version 2 (HTTP2) for communicating with the server, the management unit, and the at least one network function.
[0025] In some embodiments, the server includes a network configuration node for storing the one or more configuration parameters associated with the at least one network function.
[0026] In some embodiments, the method further includes maintaining, by the server, the one or more configuration parameters associated with the at least one network function, the one or more configuration parameters includes at least one of: a set of immutable configurations, a set of mutable configurations, and a set of scripts.
[0027] In some embodiments, the method further includes detecting, by the server, a change in the one or more network configuration parameters, and upon detecting the change, automatically notifying, by the server, the at least one network function of the change in the one or more configuration parameters.
[0028] In another exemplary embodiment, a system for managing network configuration of a network is described. The system comprises a server. The server comprises a memory, and a processing engine communicatively coupled with the memory, configured to receive a primary request for one or more network configuration parameters from at least one network function via a primary interface. The one or more network configuration parameters are associated with the at least one network function. The processing engine is configured to provide the one or more network configuration parameters to the at least one network function based on the primary request. The processing engine is configured to enable the at least one network function to self-configure in response to providing the one or more network configuration parameters.
[0029] In some embodiments, the processing engine is configured to receive a secondary request for the one or more configuration parameters associated with the at least one network function from a management unit via a secondary interface and provide the one or more configuration parameters to the management unit based on the secondary request.
[0030] In some embodiments, the processing engine is configured to monitor, by the management unit, the one or more network configuration parameters associated with the at least one network function in response to providing the requested one or more configuration parameters.
[0031] In some embodiments, at least one of: the primary interface and the secondary interface use a hypertext transfer protocol version 2 (HTTP2) for communicating with the server, the management unit, and the at least one network function.
[0032] In some embodiments, the server includes a network configuration node for storing the one or more configuration parameters associated with the at least one network function.
[0033] In some embodiments, the processing engine is configured to maintain the one or more configuration parameters associated with the at least one network function, the one or more configuration parameters includes at least one of: a set of immutable configurations, a set of mutable configurations, and a set of scripts.
[0034] In some embodiments, the processing engine is configured to detect a change in the one or more network configuration parameters, and upon detecting the change, automatically notify the at least one network function of the change in the one or more configuration parameters.
[0035] 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.BRIEF DESCRIPTION OF THE DRAWINGS
[0036] 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.
[0037] FIG. 1 illustrates an exemplary network architecture in which or with which embodiments of the present disclosure may be implemented.
[0038] FIG. 2 illustrates an exemplary block diagram of a server within a system for managing network configuration of a network, in accordance with an embodiment of the present disclosure.
[0039] FIG. 3A illustrates an exemplary flow diagram depicting a communication between a network configuration node and a network function, in accordance with an embodiment of the present disclosure.
[0040] FIG. 3B illustrates an exemplary flow diagram depicting a communication between the configuration node and a management unit, in accordance with an embodiment of the present disclosure.
[0041] FIG. 4 illustrates an exemplary block diagram of the system for managing network configuration of the network, in accordance with an embodiment of the present disclosure.
[0042] FIG. 5 illustrates a flow chart of a method for managing network configuration of the network, in accordance with an embodiment of the present disclosure.
[0043] FIG. 6 illustrates an exemplary computer system in which or with which embodiments of the present disclosure may be implemented.
[0044] The foregoing shall be more apparent from the following more detailed description of the disclosure.LIST OF REFERENCE NUMERALS100 - Network architecture102-1 and 102-2- Network functions104 - Network106 - System108 - Server202 - Processor(s)204 - Memory206 -Interface(s)208, 302, 402 - Network configuration node210 - Processing engine212 - Receiving module214 - Configuration maintaining module216 - Change detecting module218 - Other module(s)220 - Database300A - Flow diagram300B - Flow diagram400 - Block diagram404, 304 - Network function406, 306 - Management unit500: Flow chart502, 504, 506 - Steps600 - Computing system610 - External Storage Device620 - Bus630 - Main Memory640 - Read Only Memory650 - Mass Storage Device660 - Communication Port670 - ProcessorDETAILED DESCRIPTION OF THE DISCLOSURE
[0045] 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 specificdetails. 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.
[0046] 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.
[0047] 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-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail in order to avoid obscuring the embodiments.
[0048] 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.
[0049] 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.
[0050] 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.
[0051] 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.
[0052] The present disclosure may provide a system and a method that deploy a network configuration node (also referred to as a network configuration function), for managing network configuration of a network architecture. Network configuration refers to a process of setting up and adjusting various parameters and settings of network devices and services to ensure proper communication and operation within the network infrastructure. This includes configuring hardware devices such as routers, switches, firewalls, and access points, as well as software settings such as Internet Protocol (IP) addresses, Domain Name System (DNS) settings, Virtual Local Area Network (VLAN) configurations, routing tables, security protocols, and other network-specific parameters. It should be noted that the network configuration function may be applicable for wireless networks which may include, but not limited to, a 4thGeneration (4G), a 5thGeneration (5G), a 6G, and next generation communication networks. The network configuration function may be deployed as a single configuration node, so that multiple network functions may automatically learn its configuration from the network configuration node or the network configuration function.
[0053] The network configuration function may expose a service-based interface, referred to as a Network Configuration Function to Network Function interface (N-Ncf-Nf), so that every network function may pull its specific configuration parameter and self-configure itself. Moreover, whenever there is any change in any configuration parameters, then the network configuration function may notify the changes to all the network functions, if the network functions have subscribed to the network configuration function. In examples, the N-Ncf-Nf may refer to the communication link or protocol that allows the network configuration function to interact with various Network Functions (NFs) within a network.
[0054] A management unit (also referred to as a management and orchestration unit) is responsible for the instantiation of network function containers using a network function image repository. During this instantiation process, the management and orchestration unit may require specific configuration data for the network function containers. A person of ordinary skill in the art willappreciate that the terms “management unit” and “management and orchestration unit” may be used interchangeably throughout the disclosure.
[0055] The network configuration function may expose a service-based interface, referred to as a Network Configuration Function to Management interface (N-Ncf-Mgmt) towards the management and orchestration unit. This interface facilitates the provisioning of specific configuration parameter for the network functions from northbound interfaces. In examples, the N-Ncf-Mgmt may refer to a communication link or protocol that allows the network configuration function to interact with the network management systems or entities responsible for overseeing and controlling the network operations.
[0056] The various embodiments of the present disclosure will be explained in detail with reference to FIGS. 1 to 6.
[0057] FIG. 1 illustrates an exemplary network architecture (100) in which or with which embodiments of the present disclosure may be implemented.
[0058] Referring to FIG. 1, the network architecture (100) may include one or more network functions (104-1, 104-2...104-N). A person of ordinary skill in the art will understand that the one or more network functions (104-1, 104-2. . . 104- N) may be individually referred to as the network function (104) and collectively referred to as the network functions (104-1, 104-2. . . 104-N). The network function (104) may include, but not limited to, an access and mobility management function (AMF), a session management function (SMF), a user plane function (UPF), and a policy control function (PCF).
[0059] Referring to FIG. 1, the network function (104) may communicate with a system (106), for example, a system for managing network configuration, through a network function (104). The system (106) may include a server (108). The server (108) may be configured to manage the network configuration (for example, one or more network configuration parameters) associated with the network functions (104). The server (108) may include a network configurationnode for storing the one or more configuration parameters. In particular, to manage the network configuration, the system (106) may deploy the network configuration node as a single network configuration node so that multiple network functions (104) may automatically learn its specific configuration parameter from the single network configuration node, ensuring uniformity of the configuration parameters and methodology across different network function vendors. Therefore, by deploying the network configuration node, the system (106) may configure a highly distributed network function in a shorter amount of time. Th ensures error free configuration across multiple sites as manual intervention is reduced. Moreover, the system (106) reduces manual efforts and time for multiple sites configuration and commissioning. Additionally, the system (106) eases a backup or restore procedure for a large number of sites.
[0060] In an embodiment, the network (106) may include at least one of a 4G network, 5G network, 6G network, or the like. The network (106) may enable the network functions (104) to communicate with other devices in the network architecture (100) and / or with the system (108). The network (106) may include a wireless card or some other transceiver connection to facilitate this communication. In another embodiment, the network (106) may be implemented as, or include any of a variety of different communication technologies such as a wide area network (WAN), a local area network (LAN), a wireless network, a mobile network, a Virtual Private Network (VPN), the Internet, the Public Switched Telephone Network (PSTN), or the like.
[0061] As will be described in greater detail in conjunction with FIG. 1 to FIG. 6, in order to the manage network configuration, the server (108) may initially receive a primary request for one or more network configuration parameters from at least one network function via a primary interface. Based on the request, the server (108) may further provide the one or more network configuration parameters to the at least one network function. The server (108) may further enable the at least one network function to self-configure in response to providing the one or more network configuration parameters.
[0062] 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).
[0063] FIG. 2 illustrates an exemplary block diagram (200) of the server (108) within the system (106), in accordance with an embodiment of the present disclosure.
[0064] In an aspect, the server (108) may include one or more processor(s) (202). 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, one or more processor(s) (202) may be configured to fetch and execute computer-readable instructions stored in a memory (204) of the system (108). The memory (204) may be configured to store one or more computer-readable instructions or routines in a non-transitory computer-readable storage medium, which may be fetched and executed to create or share data packets over a network service. The memory (204) may include 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.
[0065] In an embodiment, the server (108) may include one or more interface(s) (206). The one or more interface(s) (206) may be a primary interface (e.g., a N-Ncf-Nf) and a secondary interface (e.g., N-Ncf-Mgmt). Alternatively, in some embodiments, the one or more interface(s) (206) may include a variety of interfaces, for example, interfaces for data input and output devices, referred to asI / O devices, storage devices, and the like. The one or more interface(s) (206) may facilitate communication of the server (108). The one or more interface(s) (206) may also provide a communication pathway for one or more components of the server (108). Examples of such components include, but are not limited to, a network configuration node (208), a processing engine (210), and a database (220).
[0066] The processing engine (210) may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processing engine (210). 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 (210) may be processor-executable instructions stored on a non- transitory machine-readable storage medium and the hardware for the processing engine (210) may include 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 (210). In such examples, the server (108) may include the machine -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 server (108) and the processing resource. In other examples, the processing engine (210) may be implemented by an electronic circuitry.
[0067] In an embodiment, the processing engine (210) may include one or more modules selected from any of a receiving module (212), a configuration maintaining module (214), a change detecting module (216) and other module(s) (218) having functions that may include, but are not limited to, testing, storage, and peripheral functions, such as a wireless communication unit for remote operation, a display unit for visualization, a notification unit for notifying network functions, and the like.
[0068] In order to manage the network configuration, initially the receivingmodule (212) may receive a primary request for one or more network configuration parameters from at least one network function. The one or more network configuration parameters may be associated with the at least one network function. The primary request may be the request made by the at least one network function to the receiving module (212) of the server (108) to obtain its specific configuration parameters. The network configuration node (208) (also referred to as a network configuration function) may store the one or more configuration parameters associated with the at least one network function. The primary request is thus a direct interaction between the at least one network function and the network configuration node (208) to obtain necessary configuration information. As will be appreciated, the terms ‘network configuration node’ and ‘network configuration function’ are used interchangeably throughout the disclosure.
[0069] The primary request may be received via the primary interface (e.g., the N-Ncf-Nf). The primary interface (N-Ncf-Nf) is used for the communication between the network configuration function and the at least one network function. Through the primary interface, the network configuration function may send the necessary configuration parameters to the at least one network function.
[0070] Upon receiving the request, the processing engine (210) may communicate with the network configuration function to provide the one or more network configuration parameters to the at least one network function. The at least one network function uses the one or more network configuration parameters to configure itself and operate correctly within the network.
[0071] More particularly, in response to providing the one or more network configuration parameters, the processing engine (210) may enable the at least one network function to self-configure itself. The term ‘self-configure’ means that the network function is able to automatically adjust and set up its own operational parameters based on the configuration parameters provided by the server (108) or the network configuration function. The automatic setup includes adjusting settings, initializing processes, and preparing to handle network traffic as per the providedconfiguration.
[0072] The self-configuration process ensures that the network function settings are consistent with the overall network architecture and requirements, reducing the risk of configuration errors that may occur with manual setup. Further, the network function may adapt to changes in the network configuration dynamically. For example, if there is an update in the configuration parameters, the network function may automatically adjust its settings accordingly to maintain optimal performance and compatibility within the network.
[0073] In some embodiments, the receiving module (212) may also receive a secondary request for the one or more configuration parameters associated with the at least one network function from a management unit. The secondary request may be received via the secondary interface (e.g., N-Ncf-Mgmt). The secondary interface (N-Ncf-Mgmt) is used for the communication between the network configuration function and the management unit. Through the secondary interface, the network configuration function may send the necessary configuration parameters to the management unit. The secondary request may be a request made by the management unit (for example, a management and orchestration unit) to the receiving module (212) of the server (108) to obtain the specific configuration parameters of the at least one network function.
[0074] Upon receiving the request, the processing engine (210) may communicate with the network configuration node (208) to provide the one or more configuration parameters to the management unit. The management unit needs the configuration information to manage the at least one network function effectively. Therefore, the secondary request represents an indirect interaction where the management unit is querying the network configuration node (208) for the configuration parameters that the at least one network function uses, for monitoring and orchestration purposes. The management unit continuously monitors for the status of the one or more configuration parameters, ensuring that any changes or updates are properly managed and applied.
[0075] The configuration maintaining module (214) may be configured to maintain the one or more configuration parameters associated with the at least one network function. The one or more configuration parameters may include a set of immutable configurations (e.g., immutable golden configurations), a set of mutable configurations (e.g., mutable site-specific configurations), and a set of scripts or commands responsible for health checks and upgrades of the at least one network function.
[0076] Immutable golden configurations are configurations which do not change and are uniform. For example, in the immutable golden configuration, the network configuration function may configure, but not limited to, a Data Network Name (DNN), a 3rdGeneration Partnership Project (3GPP) timer (e.g., idle timeout), a log file size, and a like.
[0077] Mutable site-specific configurations are configurations which change from one cloud site to another and may even change within a given cloud site / pod. For example, in the mutable site-specific configurations, the network configuration function may configure, but not limited to, an Internet Protocol (IP) address, a hostname, a virtual local area network (VLAN), and a like.
[0078] The set of commands or scripts may be used for cell site health checks and upgrades. These scripts are responsible for checking the performance and reliability of the network functions. For example, health check scripts may monitor various parameters such as CPU usage, memory usage, and network connectivity to detect any anomalies or potential issues. These scripts may run diagnostics, perform routine maintenance tasks, and generate reports on the health status of the network functions. Upgrade scripts, on the other hand, may automate the process of updating software and firmware across the network functions, which includes downloading the latest updates, verifying their integrity, and applying them in a controlled manner to minimize downtime and disruptions.
[0079] Thus, the configuration maintaining module (214) securely stores these configurations necessary for the operation of the network functions. Theconfiguration maintaining module (214) actively monitors the stored configurations to ensure that these configurations remain up to date and relevant. When a network function requests its corresponding configurations, the configuration maintaining module (214) may retrieve and deliver the appropriate configuration settings, ensuring that the network function is configured according to the defined parameters. Additionally, the configuration maintaining module (214) may execute scripts and commands related to health checks and software upgrades, automating tasks such as resource monitoring and the application of updates. By consistently applying the correct configurations and running necessary scripts, the configuration maintaining module (214) ensures that the network functions operate efficiently, minimizing the risk of errors or disruptions. Furthermore, the configuration maintaining module (214) may dynamically updates configurations as needed, ensuring that any changes are reflected and applied to the relevant network functions, maintaining consistency and performance across the network.
[0080] The change detecting module (216) may be configured to detect a change in the one or more network configuration parameters. Examples of the change may include, but not limited to, an update to an IP address, a modification in virtual local area network (VLAN) configurations, a change in security policies, and an update to a routing information. Upon detecting the change, the change detecting module (216) may automatically notify the at least one network function of the change in the one or more configuration parameters. The term “automatically” signifies that the change detecting module (216) of the server (108) performs the detection of changes in the one or more network configuration parameters and the subsequent notification is send to the network function without requiring any manual intervention.
[0081] In a more elaborative way, the at least one network function in the network (106) may subscribe to the network configuration function to pull a standard configuration from the server (108) and self-configure. The change detecting module (216) may notify the network functions whenever there is a change in any of the configuration parameters upon subscription using the primaryinterface, also known as a service-based interface (e.g., the N-Ncf-Nf). This N-Ncf- Nf interface follows the network function configuration pull and the subscribe- notify signaling pattern.
[0082] In an embodiment, the database (220) may include data (e.g., configuration parameters, vendor-specific settings, records of configuration changes and updates, monitoring data, etc.,) that may be either stored or generated as a result of functionalities implemented by any of the components of the processor(s) (202) or the processing engine (210) or the server (108).
[0083] Although FIG. 2 shows an exemplary block diagram (200) of the server (108), in other embodiments, the server (108) may include fewer components, different components, differently arranged components, or additional functional components than depicted in FIG. 2. Additionally, or alternatively, one or more components of the server (108) may perform functions described as being performed by one or more other components of the server (108).
[0084] FIG. 3A illustrates an exemplary flow diagram (300A) depicting a communication between a network configuration node (302) and a network function (304), in accordance with an embodiment of the present disclosure.
[0085] In an embodiment, the network configuration node (302) or the network configuration function (302) may communicate with the at least one network function (304) via a primary interface (e.g., a N-Ncf-Nf). The primary interface is responsible for the initial configuration exchange between the network configuration node (302) and the at least one network function (304).
[0086] Referring to FIG. 3A, the communication begins with the at least one network function (304) sending a Hypertext Transfer Protocol version 2 (HTTP2) request for configuration to the network configuration node (302). This request may include various configuration parameters necessary for the at least one network function (304) to operate within the network. The configuration parameters may include a set of immutable configurations, a set of mutable configurations, and a setof scripts responsible for health checks and upgrades of the at least one network function (304).
[0087] Upon receiving the HTTP2 request for configuration, the network configuration node (302) processes the request and determines whether the provided configuration parameters are acceptable or not.
[0088] The network configuration node (302) then responds to the at least one network function (304) with an HTTP2 response code. This response code indicates whether the configuration request has been accepted or rejected. If the response code signifies acceptance, the at least one network function (304) proceeds to use the provided configuration parameters to configure itself and begin its operations within the network. If the response code indicates rejection, the at least one network function (304) does not apply or receive the configuration parameters and further actions may be required to resolve any issues or provide alternative configurations.
[0089] FIG. 3B illustrates an exemplary flow diagram (300B) depicting a communication between the network configuration node (302) and a management unit (306), in accordance with an embodiment of the present disclosure.
[0090] In an embodiment, the network configuration node (302) initiates communication with the management unit (306) (e.g., a management and orchestration unit) via a secondary interface (e.g., the N-Ncf-Mgmt). The secondary interface facilitates the exchange of configuration information between the network configuration node (302) and the management unit (306).
[0091] The communication begins with the management unit (306) sending an HTTP2 request for configuration to the network configuration node (302). This request contains various configuration parameters that are necessary for the management unit (306) to effectively monitor and manage the network functions.
[0092] Upon receiving the HTTP2 request for configuration, the networkconfiguration node (302) processes the request to determine whether the provided configuration parameters meet its requirements and may be applied for managing the network functions (304).
[0093] The network configuration node (302) then responds to the management unit (306) with an HTTP2 response code. This response code indicates whether the configuration request has been accepted or rejected. If the response code signifies acceptance, the management unit (306) proceeds to use the provided configuration parameters to monitor and manage the network functions (304). If the response code indicates rejection, the management unit (306) does not apply the configuration parameters, and further actions may be required to resolve any issues or provide alternative configurations.
[0094] In a more elaborative way, the management and orchestration unit (306) plays an essential role in managing the lifecycle of the network functions deployed as containers. More specifically, the management and orchestration unit (306) is responsible for orchestrating the instantiation, configuration, scaling, and termination of these network function containers, ensuring efficient and automated management.
[0095] The management and orchestration unit (306) uses a network function image repository to instantiate network function containers. This process involves creating container instances based on pre-defined templates or images that includes necessary software and configuration settings for the network functions.
[0096] Once the network function containers are instantiated, the management and orchestration unit (306) interacts with the network configuration function (302) through the secondary interface, referred to as the N-Ncf-Mgmt. This interface allows the management and orchestration unit (306) to request and provision specific configuration parameters required for the proper operation of the network functions (304). The network configuration function (302) provides the necessary configuration parameters to the management and orchestration unit (306), which are then applied to the network function containers to ensure theyoperate correctly within the network.
[0097] In addition to initial provisioning, the management and orchestration unit (306) monitors the change detected by the network configuration function (302) in the configuration parameters. Furthermore, the management and orchestration unit (306) manages the entire lifecycle of the network function containers, from deployment to decommissioning. This includes scaling the network functions up or down based on demand, performing health checks, and applying necessary updates or upgrades.
[0098] FIG. 4 illustrates an exemplary block diagram (400) of the system (106) for managing network configuration of the network, in accordance with an embodiment of the present disclosure. The block diagram (400) depicts a communication pathways and interactions between a management unit (406), a network configuration node (402), and at least one network function (404), ensuring efficient management and configuration of network functions within the system (106). It should be noted that the management unit (406), the network configuration node (402), and the at least one network function (404) may be analogous to the management unit (306), the network configuration node (302), and the at least one network function (304), respectively.
[0099] The management unit (406) (e.g., a management and orchestration unit) is responsible for overseeing and orchestrating the overall network configuration. The management unit (406) communicates with the network configuration node (402) via a secondary interface. The secondary interface facilitates the exchange of configuration parameters and management information between the management unit (406) and the network configuration node (402). This interface is used primarily for the management unit (406) to send configuration requests and receive responses from the network configuration node (402).
[0100] The network configuration node (402) acts as an intermediary between the management unit (406) and the network function (404). The network configuration node (402) stores and manages the configuration parameters requiredby the network function (404). The network configuration node (402) also processes requests from both the management unit (406) and the network function (404) to ensure that the correct configuration parameters are applied.
[0101] The network function (404) is the operational element within the network that requires configuration. The network function (404) communicates with the network configuration node (402) via the primary interface. The primary interface allows the network function (404) to request configuration parameters from the network configuration node (402) and receive the necessary settings to self-configure.
[0102] The primary interface between the network function (404) and the network configuration node (402) facilitates direct communication for obtaining configuration parameters. The secondary interface between the management unit (406) and the network configuration node (402) ensures that the management unit (406) may oversee and manage the configuration of the network function (404) by providing necessary configuration parameters and receiving status updates. It should be noted that the primary interface and the secondary interface use the HTTP2 for communicating with the network configuration node (402), the management unit (406), and the at least one network function (404).
[0103] FIG. 5 illustrates a flow chart of a method (500) for managing network configuration of the network, in accordance with an embodiment of the present disclosure.
[0104] The method (500), at step 502 includes receiving, by a server, a primary request for one or more network configuration parameters from at least one network function via a primary interface. The one or more network configuration parameters are associated with the at least one network function. In some embodiments, the server may include a network configuration node for storing the one or more configuration parameters associated with the at least one network function.
[0105] The method (500), at step 504 includes providing, by the server, the one or more network configuration parameters to the at least one network function based on the request. The one or more configuration parameters may include at least one of: a set of immutable configurations, a set of mutable configurations, and a set of scripts responsible for health checks and upgrades of the at least one network function. In some embodiments, the method (500) includes maintaining, by the server, the one or more configuration parameters associated with the at least one network function.
[0106] The method (500), at step 506 includes enabling, by the server, the at least one network function to self-configure in response to providing the one or more network configuration parameters. In some embodiments, the method (500) includes detecting, by the server, a change in the one or more network configuration parameters; and upon detecting the change, automatically notifying, by the server, the at least one network function of the change in the one or more configuration parameters.
[0107] In some embodiments, the method (500) includes receiving, by the server, a secondary request for the one or more configuration parameters associated with the at least one network function from a management unit via a secondary interface; and providing, by the server, the one or more configuration parameters to the management unit. In some embodiments, the method (500) further includes monitoring, by the management unit, the one or more network configuration parameters associated with the at least one network function in response to providing the requested one or more configuration parameters. The primary interface and the secondary interface use a HTTP2 for communicating with the server, the management unit, and the at least one network function. The complete process for managing the network configuration is already explained in detail in conjunction with the FIGS. 2 - 4.
[0108] FIG. 6 illustrates an exemplary computer system (600) in which or with which embodiments of the present disclosure may be implemented. As shownin FIG. 5, the computer system (600) may include an external storage device (610), a bus (620), a main memory (630), a read only memory (640), a mass storage device (650), a communication port (660), and a processor (670). A person skilled in the art will appreciate that the computer system (600) may include more than one processor (670) and communication ports (660). Processor (670) may include various modules associated with embodiments of the present disclosure.
[0109] In an embodiment, the communication port (660) may be any of an RS-232 port for use with a modem-based dialup connection, a 10 / 100 Ethernet port, a Gigabit or 10 Gigabit port using copper or fiber, a serial port, a parallel port, or other existing or future ports. The communication port (660) may be chosen depending on a network, such a Local Area Network (LAN), Wide Area Network (WAN), or any network to which the computer system (600) connects.
[0110] In an embodiment, the memory (630) may be Random Access Memory (RAM), or any other dynamic storage device commonly known in the art. Read-only memory (640) may be any static storage device(s) e.g., but not limited to, a Programmable Read Only Memory (PROM) chips for storing static information e.g., start-up or Basic Input / Output System (BIOS) instructions for the processor (670).
[0111] In an embodiment, the mass storage (650) may be any current or future mass storage solution, which may be used to store information and / or instructions. Exemplary mass storage solutions include, but are not limited to, Parallel Advanced Technology Attachment (PATA) or Serial Advanced Technology Attachment (SATA) hard disk drives or solid-state drives (internal or external, e.g., having Universal Serial Bus (USB) and / or Firewire interfaces), one or more optical discs, Redundant Array of Independent Disks (RAID) storage, e.g., an array of disks (e.g., SATA arrays).
[0112] In an embodiment, the bus (620) communicatively couples the processor(s) (670) with the other memory, storage and communication blocks. The bus (620) may be, e.g., a Peripheral Component Interconnect (PCI) / PCI Extended(PCI-X) bus, Small Computer System Interface (SCSI), Universal Serial Bus (USB) or the like, for connecting expansion cards, drives and other subsystems as well as other buses, such a front side bus (FSB), which connects the processor (670) to the computer system (600).
[0113] Optionally, operator and administrative interfaces, e.g., a display, keyboard, joystick, and a cursor control device, may also be coupled to the bus (620) to support direct operator interaction with the computer system (600). Other operator and administrative interfaces may be provided through network connections connected through the communication port (660). Components described above are meant only to exemplify various possibilities. In no way should the aforementioned exemplary computer system (600) limit the scope of the present disclosure.
[0114] The present disclosure provides technical advancement related to network configuration management of wireless networks. This advancement addresses the limitations of existing solutions by introducing a centralized and standard network configuration node that supports the self-configuration of various network functions from multiple vendors. The disclosure involves the deployment of a single network configuration node, which offers improvements in uniformity, efficiency, and vendor-agnostic configuration management. By implementing the service-based interface for both the network functions and management unit, the disclosed technique enhances the provisioning and monitoring of network configuration parameters, resulting in efficient configuration processes, reduced integration efforts, and faster network deployments.
[0115] While the foregoing describes various embodiments of the present disclosure, other and further embodiments of the present disclosure may be devised without departing from the basic scope thereof. The scope of the present disclosure is determined by the claims that follow. The present disclosure is not limited to the described embodiments, versions, or examples, which are included to enable a person having ordinary skill in the art to make and use the present disclosure whencombined with information and knowledge available to the person having ordinary skill in the art.ADVANTAGES OF THE PRESENT DISCLOSURE
[0116] The present disclosure provides the network configuration node, for example, the network configuration function for managing configuration of different types of the network functions.
[0117] The present disclosure deploys the single network configuration node in the network, so that each network function may pull its configuration parameters and self-configure itself, ensuring uniformity of configuration parameters and methodology across different network function vendors.
[0118] The present disclosure deploys the single network configuration node to push global parameters to all the network functions simultaneously and efficiently.
[0119] The present disclosure configures a highly distributed network functions in less amount of time, using the single configuration node.
[0120] The present disclosure rolls out software upgrades across large number of sites in a faster manner as repeated steps like pre / post health check, additional configuration may be done in a short time.
[0121] The present disclosure ensures error free configuration across multiple nodes or sites as manual intervention is reduced.
[0122] The present disclosure reduces manual efforts and time for site or node configuration and commissioning, and also eases a backup or restore procedure for large number of sites.
[0123] The present disclosure deploys standardized interfaces between thenetwork configuration node and the network functions, and the network configuration node and the management and orchestration unit, which minimizes integration effort and time.
[0124] The present disclosure deploys the single network configuration node, so that the network functions configuration may be automated as well as made vendor agnostic.
Claims
We Claim:
1. A method (500) for managing network configuration, the method (500) comprising: receiving (502), by a server (108), a primary request for one or more network configuration parameters from at least one network function (304) via a primary interface, wherein the one or more network configuration parameters are associated with the at least one network function (304); providing (504), by the server (108), the one or more network configuration parameters to the at least one network function (304) based on the primary request; and enabling (506), by the server (108), the at least one network function (304) to self-configure in response to providing the one or more network configuration parameters.
2. The method (500) as claimed in claim 1, further comprising: receiving, by the server (108), a secondary request for the one or more configuration parameters associated with the at least one network function (304) from a management unit (306) via a secondary interface; and providing, by the server (108), the one or more configuration parameters to the management unit (306) based on the secondary request.
3. The method (500) as claimed in claim 2, further comprising: monitoring, by the management unit (306), the one or more network configuration parameters associated with the at least one network function (304) in response to providing the requested one or more configuration parameters.
4. The method (500) as claimed in claim 2, wherein at least one of: the primary interface and the secondary interface use a hypertext transfer protocol version 2 (HTTP2) for communicating with the server (108), the management unit (306), and the at least one network function (304).
5. The method (500) as claimed in claim 1 , wherein the server (108) comprises a network configuration node (302) for storing the one or more configuration parameters associated with the at least one network function (304).
6. The method (500) as claimed in claim 1, further comprising: maintaining, by the server (108), the one or more configuration parameters associated with the at least one network function (304), wherein the one or more configuration parameters comprises at least one of: a set of immutable configurations, a set of mutable configurations, and a set of scripts.
7. The method (500) as claimed in claim 1, further comprising: detecting, by the server (108), a change in the one or more network configuration parameters; and upon detecting the change, automatically notifying, by the server (108), the at least one network function (304) of the change in the one or more configuration parameters.
8. A system (106) for managing network configuration of a network, the system (106) comprising: a server (108), wherein the server (108) comprises: a memory (204); and a processing engine (210) communicatively coupled with the memory (204), configured to: receive a primary request for one or more network configuration parameters from at least one network function (304) via a primary interface, wherein the one or more network configuration parameters are associated with the at least one network function (304);provide the one or more network configuration parameters to the at least one network function (304) based on the primary request; and enable the at least one network function (304) to selfconfigure in response to providing the one or more network configuration parameters.
9. The system (106) as claimed in claim 8, wherein the processing engine (210) is configured to: receive a secondary request for the one or more configuration parameters associated with the at least one network function (304) from a management unit (306) via a secondary interface; and provide the one or more configuration parameters to the management unit (306) based on the secondary request.
10. The system (106) as claimed in claim 9, wherein the processing engine (210) is configured to: monitor, by the management unit (306), the one or more network configuration parameters associated with the at least one network function (304) in response to providing the requested one or more configuration parameters.
11. The system (106) as claimed in claim 9, wherein at least one of: the primary interface and the secondary interface use a hypertext transfer protocol version 2 (HTTP2) for communicating with the server (108), the management unit, and the at least one network function (304).
12. The system (106) as claimed in claim 8, wherein the server (108) comprises a network configuration node (302) for storing the one or more configuration parameters associated with the at least one network function (304).
13. The system (106) as claimed in claim 8, wherein the processing engine (210) is configured to: maintain the one or more configuration parameters associated with the at least one network function (304), wherein the one or more configuration parameters comprises at least one of: a set of immutable configurations, a set of mutable configurations, and a set of scripts.
14. The system (106) as claimed in claim 8, wherein the processing engine (210) is configured to: detect a change in the one or more network configuration parameters; and upon detecting the change, automatically notify the at least one network function (304) of the change in the one or more configuration parameters.
15. A computer program product comprising a non-transitory computer- readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to execute a method (500) for managing network configuration of a network, the method (500) comprising: receiving (502), by a server (108), a primary request for one or more network configuration parameters from at least one network function (304) via a primary interface, wherein the one or more network configuration parameters are associated with the at least one network function (304); providing (504), by the server (108), the one or more network configuration parameters to the at least one network function (304) based on the primary request; and enabling (506), by the server (108), the at least one network function (304) to self-configure in response to providing the one or more network configuration parameters.