DESC:
FORM 2
THE PATENTS ACT, 1970
(39 of 1970)
&
THE PATENTS RULES, 2003

COMPLETE SPECIFICATION
(See section 10 and rule 13)
1. TITLE OF THE INVENTION
METHOD AND SYSTEM TO MANAGE CONTAINER NETWORK FUNCTIONS IN A NETWORK
2. APPLICANT(S)
NAME NATIONALITY ADDRESS
JIO PLATFORMS LIMITED INDIAN OFFICE-101, SAFFRON, NR. CENTRE POINT, PANCHWATI 5 RASTA, AMBAWADI, AHMEDABAD 380006, GUJARAT, INDIA
3.PREAMBLE TO THE DESCRIPTION

THE FOLLOWING SPECIFICATION PARTICULARLY DESCRIBES THE NATURE OF THIS INVENTION AND THE MANNER IN WHICH IT IS TO BE PERFORMED.

FIELD OF THE INVENTION
[0001] The present invention relates to the field of communication network management, more particularly relates to a system and a method to manage Container Network Functions (CNFs) in a network.
BACKGROUND OF THE INVENTION
[0002] With the increase in number of users, a communication network is rapidly evolving to accommodate the surge of request commands and improve user experience. A communication network comprises of many network elements which are configured to operate in specific manner to improve credibility of the communication network. The network incorporates inventories to safe-keep resources required to perform request processing. Inventory Management (IM) service maintains the virtual inventory and limited physical inventory. It maintains the relation between physical and virtual resources with respect to overlay to manage storage memory allocation. Also, it describes physical and virtual resources in view of different attributes using updates from external micro-service. Thus, data accuracy of the inventory management service is dependent upon the micro-services which create, update, delete these resources and at the same time update these events with IM. Other services can query IM relations, attributes etc. using query APIs (application programming interface) provided by IM. However, as there are thousands of network functions running in parallel any discrepancy may lead to failure of our system. This may happen when there is discrepancy in available date like the available data indicates that CNF (container network functions) or CNFC (container network function components) are running in backend when there are not any, or not indicating details of CNF/CNFC running in the backend, or cases where memory allocated and in usage data does not match etc. To avoid this scenario, it’s necessary to implement a system and method to take a proactive approach in preventing data discrepancies, so that inventory should be in sync with the actual infrastructure at backend and in sync with dependent network functions with its resources as well. Presently no such mechanism is available which will enable auto auditing and auto syncing all data from backend and in the inventory.
[0003] Thus, there is requirement of a system and a method to audit every running NF(s) (network functions) and micro-service instances via a single platform or interface by which all the operation at IM can be auto-synced without any possible data-mismatch or discrepancy and the network may operate with ease, with improved efficacy and without consuming too much time.

SUMMARY OF THE INVENTION
[0004] One or more embodiments of the present disclosure provide a method and system for managing Container Network Functions (CNFs) in a network.
[0005] In one aspect of the present invention, the system to manage CNFs in the network is disclosed. The method includes the step of a receiving a list of Container Network Functions (CNFs) from an inventory unit. The method includes the step of recording a CNF identifier for each CNF from the list of CNFs based on the received list of CNFs. The method further includes the step of receiving from the inventory unit a list of CNFCs for each CNF from the list of CNFs in response to transmitting a CNFC request to the inventory unit based on the recorded CNF identifier for the respective CNF. The method further includes the step of comparing the list of CNFs and the list of CNFCs for each CNF from the list of CNFs received from the inventory unit with available data pertaining to the CNFs and the CNFCs present in at least one of, a server or backend running network elements. The method further includes the step of auto syncing the inventory unit with the available data present in at least one of, the server or the backend running network elements pertaining to the CNFs and the CNFCs based on determining a mismatch with the list of CNFs and the list of CNFCs at the inventory unit when compared with the available data.
[0006] In an embodiment, the step of receiving a list of Container Network Functions (CNFs) from an inventory unit includes the step of transmitting a CNF request to the inventory unit to retrieve the list of CNFs from the inventory unit.
[0007] In an embodiment, the step of receiving from the inventory unit a list of Container Network Functions Components (CNFCs) for each CNF from the list of CNFs includes the step of transmitting the CNFC request to the inventory unit to retrieve the list of CNFCs corresponding to the respective CNF wherein the CNFC request includes information of the CNF identifier.
[0008] In an embodiment, the step of comparing the list of CNFs and the list of CNFCs for each CNF from the list of CNFs received from the inventory unit with available data pertaining to the CNFs and the CNFCs at least one of a server or backend running network elements includes the steps of, transmitting a retrieval request to at least one of the server or the backend running network elements. The retrieval request pertains to retrieving available data pertaining to the CNFs and the CNFCs for each of the CNF present in at least one of, the server or the backend running network elements and further comparing each of the CNF from the list of CNFs with the available data pertaining to the CNFs present in at least one of the server or the backend running network elements based on the transmitted retrieval request. Each of the CNF from the list of CNFs is compared with the available data pertaining to the CNFs present in at least one of the server or the backend running network elements utilizing the CNF identifier. When there is a match with the CNFs of the inventory unit with the available data of the CNFs, the list of CNFCs for each of the respective CNF from the list of CNFs is compared with the available data pertaining to the CNFCs in order to determine the mismatch.
[0009] In an embodiment, the inventory unit is auto synced with the available data present in at least one of, the server or the backend running network elements utilizing an interface.
[0010] In an embodiment, step of auto syncing the inventory unit with the available data present in at least one of, the server or the backend running network elements pertaining to the CNFs and the CNFCs further includes the steps of determining whether the inventory unit includes one or more additional CNFCs when compared to the corresponding available data present in at least one of, the server or the backend running network elements. When determined present, removing the data pertaining to the one or more additional CNFCs from the inventory unit.
[0011] In another aspect of the present invention, the system for managing CNFs in the network is disclosed. The system includes a transceiver unit configured to receive a list of Container Network Functions (CNFs) from an inventory unit. The system includes a recording unit configured to record a CNF identifier for each CNF from the list of CNFs based on the received list of CNFs. The transceiver unit configured to a receive from the inventory unit a list of Container Network Functions Components (CNFCs) for each CNF from the list of CNFs in response to transmitting the CNFC request to the inventory unit based on the recorded CNF identifier for the respective CNF. The system includes a comparing unit configured to compare the list of CNFs and the list of CNFCs for each CNF from the list of CNFs received from the inventory unit with available data pertaining to the CNFs and the CNFCs present in at least one of a server or backend running network elements. The system includes a syncing unit configured to auto sync the inventory unit with the available data present in at least one of the server or the backend running network elements pertaining to the CNFs and the CNFCs based on determining a mismatch with the list of CNFs and the list of CNFCs at the inventory unit when compared with the available data.
[0012] In another aspect of the invention, a non-transitory computer-readable medium having stored thereon computer-readable instructions is disclosed. The computer-readable instructions are executed by a processor. The processor is configured to receive a list of Container Network Functions (CNFs) from an inventory unit. The processor is configured to record, a CNF identifier for each CNF from the list of CNFs based on the received list of CNFs. The processor is configured to receive, from the inventory unit, a list of Container Network Functions Components (CNFCs) for each CNF from the list of CNFs in response to transmitting a CNFC request to the inventory unit based on the recorded CNF identifier for the respective CNF. The processor is configured to compare the list of CNFs and the list of CNFCs for each CNF from the list of CNFs received from the inventory unit with available data pertaining to the CNFs and the CNFCs present in at least one of a server or backend running network elements. The processor is configured to auto sync the inventory unit with the available data present in at least one of the server or the backend running network elements pertaining to the CNFs and the CNFCs based on determining a mismatch with the list of CNFs and the list of CNFCs at the inventory unit when compared with the available data.
[0013] Other features and aspects of this invention will be apparent from the following description and the accompanying drawings. The features and advantages described in this summary and in the following detailed description are not all-inclusive, and particularly, many additional features and advantages will be apparent to one of ordinary skill in the relevant art, in view of the drawings, specification, and claims hereof. Moreover, it should be noted that the language used in the specification has been principally selected for readability and instructional purposes and may not have been selected to delineate or circumscribe the inventive subject matter, resort to the claims being necessary to determine such inventive subject matter.
BRIEF DESCRIPTION OF THE DRAWINGS
[0014] 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 disclosure of electrical components, electronic components or circuitry commonly used to implement such components.
[0015] FIG. 1 is an exemplary block diagram of an environment to manage Container Network Functions (CNFs) in a network, according to one or more embodiments of the present invention;
[0016] FIG. 2 is an exemplary block diagram of a system to manage CNFs in the network, according to one or more embodiments of the present invention;
[0017] FIG. 3a is an exemplary representation of an Inventory Manager (IM_AU) interface in a network environment, and FIG.3b is a block diagram of an architecture of the system of FIG. 2 to manage CNFs in the network utilizing the IM_AU interface, according to one or more embodiments of the present invention;
[0018] FIG. 4 is an exemplary flowchart diagram to manage CNFs in the network, according to one or more embodiments of the present invention; and
[0019] FIG. 5 is a flowchart of a method to manage CNFs in the network, according to one or more embodiments of the present invention.
[0020] FIG. 6 is a schematic representation of a workflow diagram to manage CNFs in the network, according to one or more embodiments of the present invention;
[0021] The foregoing shall be more apparent from the following detailed description of the invention.
DETAILED DESCRIPTION OF THE INVENTION
[0022] Some embodiments of the present disclosure, illustrating all its features, will now be discussed in detail. It must also be noted that as used herein and in the appended claims, the singular forms "a", "an" and "the" include plural references unless the context clearly dictates otherwise.
[0023] Various modifications to the embodiment will be readily apparent to those skilled in the art and the generic principles herein may be applied to other embodiments. However, one of ordinary skill in the art will readily recognize that the present disclosure including the definitions listed here below are not intended to be limited to the embodiments illustrated but is to be accorded the widest scope consistent with the principles and features described herein.
[0024] A person of ordinary skill in the art will readily ascertain that the illustrated steps detailed in the figures and here below are set out to explain the exemplary embodiments shown, and it should be anticipated that ongoing technological development will change the manner in which particular functions are performed. These examples are presented herein for purposes of illustration, and not limitation. Further, the boundaries of the functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternative boundaries can be defined so long as the specified functions and relationships thereof are appropriately performed. Alternatives (including equivalents, extensions, variations, deviations, etc., of those described herein) will be apparent to persons skilled in the relevant art(s) based on the teachings contained herein. Such alternatives fall within the scope and spirit of the disclosed embodiments.
[0025] FIG. 1 illustrates an exemplary block diagram of a communication system 100 for Container Network Functions (CNFs) in a network, according to one or more embodiments of the present disclosure. In this regard, the communication system 100 includes a User Equipment (UE) 110, a server 115, a network 105 and a system 120 communicably coupled to each other for manage CNFs in the network 105.
[0026] As per the illustrated embodiment and for the purpose of description and illustration, the UE 110 includes, but not limited to, a first UE 110a, a second UE 110b, and a third UE 110c, and should nowhere be construed as limiting the scope of the present disclosure. In alternate embodiments, the UE 110 may include a plurality of UEs as per the requirement. For ease of reference, each of the first UE 110a, the second UE 110b, and the third UE 110c, will hereinafter be collectively and individually referred to as the “User Equipment (UE) 110”.
[0027] In an embodiment, the UE 110 is one of, but not limited to, any electrical, electronic, electro-mechanical or an equipment and a combination of one or more of the above devices such as a smartphone, virtual reality (VR) devices, augmented reality (AR) devices, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other computing device.
[0028] The communication system 100 includes the server 115 accessible via the network 105. The server 115 may include, by way of example but not limitation, one or more of a standalone server, a server blade, a server rack, a bank of servers, a server farm, hardware supporting a part of a cloud service or system, a home server, hardware running a virtualized server, one or more processors executing code to function as a server, one or more machines performing server-side functionality as described herein, at least a portion of any of the above, some combination thereof. In an embodiment, the entity may include, but is not limited to, a vendor, a network operator, a company, an organization, a university, a lab facility, a business enterprise side, a defense facility side, or any other facility that provides service.
[0029] The network 105 includes, by way of example but not limitation, one or more of a wireless network, a wired network, an internet, an intranet, a public network, a private network, a packet-switched network, a circuit-switched network, an ad hoc network, an infrastructure network, a Public-Switched Telephone Network (PSTN), a cable network, a cellular network, a satellite network, a fiber optic network, or some combination thereof. The network 105 may include, but is not limited to, a Third Generation (3G), a Fourth Generation (4G), a Fifth Generation (5G), a Sixth Generation (6G), a New Radio (NR), a Narrow Band Internet of Things (NB-IoT), an Open Radio Access Network (O-RAN), and the like.
[0030] The network 105 may also include, by way of example but not limitation, at least a portion of one or more networks having one or more nodes that transmit, receive, forward, generate, buffer, store, route, switch, process, or a combination thereof, etc. one or more messages, packets, signals, waves, voltage or current levels, some combination thereof, or so forth. The network 105 may also include, by way of example but not limitation, one or more of a wireless network, a wired network, an internet, an intranet, a public network, a private network, a packet-switched network, a circuit-switched network, an ad hoc network, an infrastructure network, a Public-Switched Telephone Network (PSTN), a cable network, a cellular network, a satellite network, a fiber optic network, a VOIP or some combination thereof.
[0031] The communication system 100 further includes the system 120 communicably coupled to the server 115 and the UE 110 via the network 105. The system 120 is configured to manage CNFs in the network. As per one or more embodiments, the system 120 is adapted to be embedded within the server 115 or embedded as an individual entity.
[0032] Operational and construction features of the system 120 will be explained in detail with respect to the following figures.
[0033] FIG. 2 is an exemplary block diagram of the system 120 to manage CNFs in the network, according to one or more embodiments of the present invention.
[0034] As per the illustrated embodiment, the system 120 includes one or more processors 205, a memory 210, a user interface 215, and a database 220. For the purpose of description and explanation, the description will be explained with respect to one processor 205 and should nowhere be construed as limiting the scope of the present disclosure. In alternate embodiments, the system 120 may include more than one processor 205 as per the requirement of the network 105. The one or more processors 205, hereinafter referred to as the processor 205 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, single board computers, and/or any devices that manipulate signals based on operational instructions.
[0035] As per the illustrated embodiment, the processor 205 is configured to fetch and execute computer-readable instructions stored in the memory 210. The memory 210 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 210 may include any non-transitory storage device including, for example, volatile memory such as RAM, or non-volatile memory such as disk memory, EPROMs, FLASH memory, unalterable memory, and the like.
[0036] In an embodiment, the user interface 215 includes a variety of interfaces, for example, interfaces for a graphical user interface, a web user interface, a Command Line Interface (CLI), and the like. The user interface 215 facilitates communication of the system 120. In one embodiment, the user interface 215 provides a communication pathway for one or more components of the system 120. Examples of such components include, but are not limited to, the UE 110 and the database 220.
[0037] The database 220 is one of, but not limited to, a centralized database, a cloud-based database, a commercial database, an open-source database, a distributed database, an end-user database, a graphical database, a No-Structured Query Language (NoSQL) database, an object-oriented database, a personal database, an in-memory database, a document-based database, a time series database, a wide column database, a key value database, a search database, a cache databases, and so forth. The foregoing examples of database 220 types are non-limiting and may not be mutually exclusive e.g., a database can be both commercial and cloud-based, or both relational and open-source, etc.
[0038] In order for the system 120 for manage CNFs in the network, the processor 205 includes one or more modules. In one embodiment, the one or more modules/units includes, but not limited to, a transceiver unit 225, an inventory unit 230, a recording unit 235, a comparing unit 240, and a syncing unit 245 communicably coupled to each other for manage CNFs in the network 105.
[0039] In one embodiment, the one or more modules includes, but not limited to, the transceiver unit 225, the inventory unit 230, the recording unit 235, the comparing unit 240, and the syncing unit 245 can be used in combination or interchangeably for manage CNFs in the network 105.
[0040] The transceiver unit 225, the inventory unit 230, the recording unit 235, the comparing unit 240, and the syncing unit 245, in an embodiment, may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processor 205. In the examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processor 205 may be processor-executable instructions stored on a non-transitory machine-readable storage medium and the hardware for the processor may comprise a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the memory 210 may store instructions that, when executed by the processing resource, implement the processor. In such examples, the system 120 may comprise the memory 210 storing the instructions and the processing resource to execute the instructions, or the memory 210 may be separate but accessible to the system 120 and the processing resource. In other examples, the processor 205 may be implemented by electronic circuitry.
[0041] In an embodiment, the transceiver unit 225 configured to receive a list of Container Network Functions (CNFs) from an inventory unit 230. The list of the CNFs may include, but not limited to, access and mobility management function, user plane function, session management function, policy control function, and unified data management. The CNF is the network function that is designed to run within a containerized environment. The CNF is typically deployed as part of a microservices architecture, which means the CNF can be independently scaled and managed. The types of CNF includes, but not limited to, Session Management Function (SMF) CNF, Access and Mobility Management Function (AMF) CNF, Network Function Virtualization Orchestrator (NFVO) CNF, and Policy Control Function (PCF) CNF.
[0042] The transceiver unit 225 receives the list of CNFs from the inventory unit 230 by transmitting a CNF request to the inventory unit 230 to retrieve the list of CNFs from the inventory unit 230. The list of the CNFs typically includes, but not limited to, unique identifiers, metadata such as name, version, and specific functions, operational status, network deployment information, and optionally, links to associated a Container Network Functions Components (CNFCs), all of which are crucial for tracking, managing, and understanding the structure and dependencies of each CNF within the network 105. The CNFCs are the specific element or module within the CNF that performs the particular function or task. The CNFCs are individual units within the CNF, each responsible for the distinct part of the overall functionality provided by the CNF. The CNFCs are modular and can be independently updated or replaced. The types of CNFCs include, but not limited to, packet forwarding component within the CNF, session management component within the CNF, policy enforcement component within the CNF, and mobility management component within the CNF.
[0043] The recording unit 235 configured to record the CNF identifier for each CNF from the list of CNFs based on the received list of CNF. The CNF identifier is a unique code, number, or label that distinctly identifies each CNFs within the network 105.The list of CNFs includes collection or inventory of all the CNFs currently present in the network 105, which the system 120 receives from the inventory unit 230. The CNF identifier may include at least one of, a Universally Unique Identifier (UUID), a name, or a specific code associated with each CNF. The list of CNFs is provided by the inventory unit 230 to the system 120, which contains all the CNFs currently recognized by the network 105. The CNF identifier allows for precise tracking, management, and retrieval of information related to each CNF. The CNF identifier ensures that each CNF can be individually recognized and accessed when needed. The process of recording the CNF identifiers refers to the act of storing the CNF identifiers in the database 220, log file, and some other form of persistent storage and ensures that the identifiers are available for future reference and can be used in subsequent operations.
[0044] Further, transceiver unit 225 is configured to receive from the inventory unit 230 the list of CNFCs for each CNF from the list of CNFs in response to transmitting the CNFC request to the inventory unit 230 based on the recorded CNF identifier for the respective CNF. The list of CNFCs may include, but not limited to, service logic modules, interface handlers, security modules, load balancing components, and resource management modules. The transceiver unit 225 acts as both the transmitter and the receiver. The transceiver unit 225 sends out requests and receives responses, facilitating communication between different parts of the system 120. The inventory unit 230 holds information about all the CNFs and CNFCs in the network 105. The CNFs and CNFCs have a hierarchical relationship where the CNF acts as the high-level, self-contained network service or application, encompassing multiple CNFCs. Each CNFC is the modular sub-component within the CNF, responsible for executing specific tasks or functions essential to the CNFs overall purpose. The CNF integrates and manages the CNFCs to deliver comprehensive network services, while CNFCs operate within the CNF to perform specialized roles, contributing to the CNFs overall functionality and effectiveness. The CNFs and CNFCs relationship enables, modularity, scalability, and efficient management of the network functions in the containerized environment.
[0045] The inventory unit 230 is auto synced with the available data present in at least one of, the server or the backend running network elements utilizing an interface. The server or the backend running network elements utilizing the interface refers to the system 120 or infrastructure components responsible for, but not limited to, hosting, managing, and operating the CNFs and associated components CNFCs within the network 105. The backend system is crucial for, but not limited to, the real-time operation, monitoring, and management of the network functions. The interface mentioned facilitates communication and synchronization between the backend system 120 and the inventory unit 230. The server or the backend running network elements includes, but not limited to, kubernetes cluster managing CNFs, open stack managing virtual machines for CNFs, Amazon Web Services (AWS) cloud services hosting CNFs, and Cisco Network Services Orchestrator (NSO) managing network functions.
[0046] In an embodiment, the CNFC request includes information of the CNF identifier. The comparing unit 240 is configured to compare the list of CNFs and the list of CNFCs for each CNF from the list of CNFs received from the inventory unit 230 with available data pertaining to the CNFs and the CNFCs at least one of, a server or backend running network elements. In an embodiment, the available data refers to the existing information related to the CNFs and the CNFCs that is stored in or managed by the server or backend running network elements. The existing information related to CNFs are, at least one of, but not limited to, configuration data, session information records, and operational status logs. The available data is used to verify and compare with the inventory data provided by the inventory unit 230. The available data may include, but not limited to, configuration data to record the previous configurations, including any updates or modifications made to the CNFs and CNFCs over time, operational status logs of past operational states, including any changes in status of CNFs and CNFCs, session information records of previous sessions, including details such as, but not limited to, session duration, connection history, and any session-related issues, and historical data of past information related to the CNFs and the CNFCs.
[0047] The comparing unit 240 compares the list of CNFs and the list of CNFCs for each CNF from the list of CNFs received from the inventory unit 230 with available data pertaining to the CNFs and the CNFCs present in at least one of, the server or the backend running network elements. The comparing unit 240 compares the list of CNFs and the list of CNFCs for each CNF from the list of CNFs by transmitting a retrieval request to at least one of, the server or the backend running network elements. The comparing unit 240 assesses various parameters while comparing the list of CNFs and the list of CNFCs for each CNF with the available data. The various parameters which are compared include, such as for example but not limited to, configuration settings, operational status, session information, historical data, resource allocations, and status updates to ensure consistency and accuracy between the inventory unit 230 and at least one of, the server or the backend running network elements, thereby ensuring that the data managed by the system 120 is reliable and up-to-date. For example, let us consider, the parameter “resource allocation” is compared of the CNFs and the corresponding CNFCs from the inventory unit 230 with the available data of the CNFs and the CNFCs, in this example “resource allocation” present in at least one of, the server or the backend running network elements. In an embodiment, the retrieval request pertains to retrieving available data pertaining to the CNFs and the CNFCs for each of the CNF present in at least one of, the server or the backend running network elements. Thereafter, the comparing unit 240 compares each of the CNF from the list of CNFs with the available data pertaining to the CNFs present in at least one of, the server or the backend running network elements based on the transmitted retrieval request. In an embodiment, each of the CNF from the list of CNFs is compared with the available data pertaining to the CNFs present in at least one of, the server or the backend running network elements utilizing the CNF identifier. In the example indicated above, the parameter “resource allocation” is compared of the CNFs and the CNFCs from the inventory unit 230 with the available data (in this example “resource allocation”) of the CNFs and the CNFCs, present in at least one of, the server or the backend running network elements. If the data related to the “resource allocation” pertaining to the CNFs and the CNFCs of the inventory unit 230 does not match with the available data present in at least one of, the server or the backend running network elements, then the comparing unit 240 makes a decision that there is a mismatch.
[0048] The syncing unit 245 is configured to auto sync the inventory unit 230 with the available data present in at least one of, the server or the backend running network elements pertaining to the CNFs and the CNFCs based on determining the mismatch with the list of CNFs and the list of CNFCs at the inventory unit 230 when compared with the available data. In an embodiment, the mismatch may include discrepancies in operational status such as, active and inactive, configuration settings such as, wrong IP address or security protocol, and missing/extra CNFCs in the inventory compared to the actual running components. Once the mismatch is detected, the syncing unit 245 updates the inventory unit 230 with the correct data from the server or backend running network elements. The auto sync may include updating the status of the CNF, correcting configuration details, and/or adding/removing CNFCs from the inventory based on what is actually present and running in the network 105. In an embodiment, the server or the backend running network elements are centralized or distributed servers that store configuration data, logs, and historical records for CNFs and CNFCs. The server might also maintain the database 220 which includes expected or desired configurations for the network functions. The backend running network elements are the actual network components or infrastructure such as, but not limited to, routers, switches, computer nodes. The backend running network elements run the CNFs in real-time. The backend running network elements provide real-time data about the operational status, configuration, and performance of the CNFs and the components. In an embodiment, the syncing unit 245 determines whether at least one of the server or the backend running network elements includes one or more additional CNFCs when compared to the corresponding available data present in the inventory unit. When determined present, the syncing unit 245 removes the data pertaining to the one or more additional CNFCs from at least one of, the server or the backend running elements. The process involves the comparison between the data in the inventory unit 230 and the data in at least one of the server or backend running network elements to identify any discrepancies, specifically additional CNFCs that exist in the server or backend but not in the inventory unit 230. If such additional CNFCs are found, they are removed from the server or backend.
[0049] The syncing unit 245 is further configured to determine whether the inventory unit 230 includes one or more additional CNFCs when compared to the corresponding available data present in at least one of, the server or the backend running network elements. When the syncing unit 245 determines that the inventory unit 230 includes the CNFCs that are not in the server or backend data, the syncing unit 245 removes the one or more additional CNFCs from the inventory unit 230.
[0050] FIG. 3a is an exemplary block diagram of an interface for example an Inventory Manager_Audit (IM_AU) interface, and FIG. 3b is a block diagram of an architecture 300 of the system 120 to manage CNFs in the network utilizing the interface in the present example, the IM_AU interface 315, according to one or more embodiments of the present invention.
[0051] The architecture 300 includes a Micro-Service Auditor (MAUD) 305 and a Physical and Virtual Inventory Manager (PVIM) 310, an Inventory Manager (IM) interface 315, and the database 220.
[0052] The IM_AU interface 315 as shown in FIG. 3a illustrates the interaction between the PVIM 310 and MAUD 305. The PVIM 310 is responsible for managing virtual infrastructure resources such as Virtual Machines (VMs) and containers, essential for deploying and operating Virtual Network Functions (VNFs) and Container Network Functions (CNFs). The MAUD 305 continuously audits and monitors microservices to ensure that the microservices meet compliance standards and perform efficiently. The IM_AU interface 315 serves as the communication bridge between the PVIM 310 and MAUD 305, facilitating the exchange of data related to the deployment, scaling, and health of the microservices. The IM_AU interface 315 allows the auditor to request resource information from the PVIM 310 and issue updates based on its findings, ensuring the operational quality of microservices in the network 105.
[0053] The PVIM 310 is responsible for managing and integrating both physical and virtual resources essential for network operations. The PVIM 310 ensures accurate inventory management by maintaining detailed records of resource configurations, operational statuses, and lifecycle stages. The PVIM 310 facilitates efficient resource allocation and optimization by balancing workloads and coordinating resource deployment. Additionally, the PVIM 310 synchronizes data with other systems to maintain consistency and supports compliance with network policies.
[0054] The microservices in the MAUD 305 are specialized components designed to handle specific functions related to CNFs and CNFCs management. The microservices in MAUD 305 include, but not limited to, services for data reception, request handling, data comparison, synchronization, and monitoring. Each microservice operates independently but works in concert with others to ensure seamless and accurate management of CNFs and CNFCs data.
[0055] The MAUD 305 is responsible for managing and auto-synchronizing CNF data. The MAUD 305 interacts with the PVIM 310 and the database 220 to ensure consistency and accuracy of the CNF and the CNFC data. The Inventory Manager Audit (IM_AU) interface 315, would facilitate the communication between the MAUD 305, the PVIM 310, and the database 220, ensuring seamless data synchronization across mechanisms. The IM_AU interface 315 as shown in FIG. 3a facilitates the reception of Container Network Function (CNF) lists from the inventory unit 230. It ensures that CNF identifiers are accurately recorded by the MAUD 305. The IM_AU interface 315 has the capability to facilitate real-time synchronization and communication between the PVIM 310 and MAUD 305. By providing the unified interface for data reception, request handling, comparison, and synchronization and ensures that CNF and CNFC data remains accurate and up to date across the PVIM 310 and database 220, overcoming traditional challenges in data consistency and integration.
[0056] The MAUD 305 receives the list of CNFs from the inventory unit 230, records the CNF identifiers, and then transmits requests for CNFCs based on the CNF identifiers. Once the MAUD 305 receives the list, it records the CNF identifiers for further processing and tracking. Further, the MAUD 305 compares the CNF and CNFC data received from the PVIM 310 with the available data in the database 220 to detect any mismatch. When the mismatch is detected, the MAUD 305 automatically synchronizes the PVIM 310 data with correct data from database 220.
[0057] Upon receiving the data from the MAUD 305, the PVIM 310 checks whether the mismatch is detected during the comparison process. When confirmed that the mismatch is detected during the comparison process, the PVIM 310 is auto synced with the database 220 to correct any mismatches. The PVIM 310 serves as the inventory unit 230, stores and manages the data related to CNFs and the CNFCs. The PVIM 310 receives requests from the MAUD 305 for lists of CNFs and CNFCs and responds with the relevant data. The PVIM 310 plays a crucial role in the auto-synchronization process. When the mismatch is detected between the data and the correct data stored in database 220, the PVIM 310 is updated automatically by the MAUD 305, ensuring that the inventory data remains accurate and consistent with the database 220. The PVIM 310 supports various interfaces, including the IM_AU interface 315, which facilitates communication and data exchange between the PVIM 310, the MAUD 305, and database 220.
[0058] The database 220 acts as the backend storage for available data related to CNFs and CNFCs. The database 220 stores data that is compared against the information provided by the PVIM 310. If there is mismatch detected during the comparison, the MAUD 305 auto-syncs the PVIM 310 with the correct data stored in the database 220.
[0059] FIG. 4 is an exemplary flowchart diagram for managing CNFs in the network, according to one or more embodiments of the present invention.
[0060] At step 405, the MAUD 305 sends the inventory of CNFs list via the auto-sync interface to retrieve the list of all the CNFs currently running across the network 105.
[0061] At step 410, upon obtaining the CNF list, the MAUD 305 sends another request through the IN_AU interface 315 to retrieve the CNFC list for each specific CNF identifier.
[0062] At step 415, similarly, the MAUD 305 requests the list from the inventory and subsequently requests the CNFC list for each node through the IM_AU interface 315. This step is crucial for verifying that all CNFCs associated with specific nodes are correctly represented in the inventory, enabling precise tracking and management of the components.
[0063] At step 420, after receiving the list of CNFs from the inventory, the node list is retrieved from the inventory service. For each node from the node list, the request is made to get the CNFC list, ensuring that all components associated with the nodes are accounted for.
[0064] At step 425, after collecting all the necessary CNFs, CNFCs and nodes, the MAUD 305 checks the network resources. If there are discrepancies between the inventory data and the actual resources, the MAUD 305 syncs the inventory to match the actual state of the network resources.
[0065] At step 430, the MAUD 305 checks for any additional or irrelevant VNDF (Vendor Network Function Descriptor) or CNFC details present in the inventory. When any additional or irrelevant VNDF or the CNFC is found, the MAUD 305 deletes the details to ensure the inventory only contains accurate and necessary information.
[0066] At step 435, the process concludes after ensuring that the inventory is properly synced and cleaned of any extraneous data to finalize the process, ensuring the network functions and components are correctly represented in the inventory.
[0067] FIG. 5 is a flowchart of a method 500 to manage CNFs in the network, according to one or more embodiments of the present invention. For the purpose of description, the method 500 is described with the embodiments as illustrated in FIG. 2 and should nowhere be construed as limiting the scope of the present disclosure.
[0068] At step 505, the method 500 includes the step of receiving the list of the CNFs from an inventory unit 230. The step of receiving the list of CNFs from the inventory unit 230 includes the step of transmitting the CNF request to the inventory unit 230 to retrieve the list of CNFs from the inventory unit 230.
[0069] At step 510, the method 500 includes the step of recording the CNF identifier for each CNF from the list of CNFs based on the received list of CNFs.
[0070] The step505, includes the step of transmitting the CNFC request to the inventory unit 230 to retrieve the list of CNFCs corresponding to the respective CNF. The CNFC request includes information of the CNF identifier.
[0071] At step 515, the method 500 includes the step of receiving from the inventory unit 230, the list of the CNFCs for each CNF from the list of CNFs in response to transmitting the CNFC request to the inventory unit 230 based on the recorded CNF identifier for the respective CNF. The inventory unit 230 is auto synced with the available data present in at least one of, the server or the backend running network elements utilizing the interface.
[0072] At step 520, the method 500 includes the step of comparing the list of CNFs and the list of CNFCs for each CNF from the list of CNFs received from the inventory unit with available data pertaining to the CNFs and the CNFCs present in at least one of, the server or backend running network elements. The step of comparing the list of CNFs and the list of CNFCs for each CNF from the list of CNFs, includes the steps of transmitting the retrieval request to at least one of, the server or the backend running network elements. The retrieval request pertains to retrieving available data pertaining to the CNFs and the CNFCs for each of the CNF present in at least one of, the server or the backend running network elements. Further, the step 520 includes the step of, comparing each of the CNF from the list of CNFs with the available data pertaining to the CNFs present in at least one of, the server or the backend running network elements, based on the transmitted retrieval request. In an embodiment, each of the CNF from the list of CNFs is compared with the available data pertaining to the CNFs present in at least one of, the server or the backend running network elements utilizing the CNF identifier. When there is the match with the CNFs of the inventory unit with the available data of the CNFs, the list of CNFCs for each of the respective CNF from the list of CNFs is compared with the available data pertaining to the CNFCs in order to determine the mismatch.
[0073] At step 525, the method 500 includes the step of auto syncing the inventory unit 230 with the available data present in at least one of, the server or the backend running network elements pertaining to the CNFs and the CNFCs based on determining the mismatch with the list of CNFs and the list of CNFCs at the inventory unit 230 when compared with the available data. The step of auto syncing the inventory unit 230 with the available data present at least one of, the server or the backend running network elements pertaining to the CNFs and the CNFCs further includes the steps of determining whether the inventory unit 230 includes one or more additional CNFCs when compared to the corresponding available data present in at least one of, the server or the backend running network elements and when determined present, removing the data pertaining to the one or more additional CNFCs from the inventory unit 230. The step 525 further includes the step of determining whether at least one of the server or the backend running network elements includes one or more additional CNFCs when compared to the corresponding available data present in the inventory unit 230. When determined present, removing the data pertaining to the one or more additional CNFCs from at least one of, the server or the backend running elements.
[0074] FIG. 6 is a schematic representation of a workflow diagram to manage CNFs in the network, according to one or more embodiments of the present invention;
At step 605, VNFC instance for each VNF instance is retrieved from the PVIM 310 and compared with the server ID from Orchestration Service (OSA). The step involves querying the PVIM 310 for its current VNFC instances. Simultaneously, compare the instances with the corresponding server IDs from orchestration service (OSA) to identify any discrepancies or changes between the two systems. At step 610, upon fetching the VNFC instances, depending on the results based on comparison, the VNFC instances, trigger the event to either update or delete VNFCs in the PVIM 310. If VNFCs have been added or updated in the OSA, this step ensures that the changes are reflected in the PVIM 310. Conversely, if the VNFCs have been deleted or are missing in the OSA, this step initiates the removal of the VNFCs from the PVIM 310 to maintain consistency. At step 615, any changes made at step 610 are updated in the MAUD 305 to reflect the changes and involves modifying the MAUD 305 index or database 220 to accurately represent the current state of the VNFCs, ensuring that the MAUD 305 mirrors the latest configurations and statuses from PVIM 310 and the OSA.
At step 620, the list of host aggregates are obtained from the PVIM 310 and compares with the detailed host aggregate list from the OSA.
At step 625, upon identifying any additional hosts or VMs in the PVIM 310 based on comparison at step 620, the events are dispatched to delete any extra resources from the PVIM 310, thereby aligning the PVIM 310 data with the accurate information provided by the OSA.
At step 630, upon dispatching the event at step 625, reflect the removal of any extra hosts or VMs in the MAUD 305 index and thereafter update the index or the database 220 maintained by the MAUD 305 in order to remove references to the deleted resources, ensuring that the MAUD 305 index accurately represents the current state of the hosts and the VMs in OSA.
At step 635, the list of VMs is retrieved from each Virtual Infrastructure Manager (VIM) within the PVIM 310 and compared with the VM list from the OSA. The step ensures that the VM data in the PVIM 310 matches the information provided by the OSA, verifying that all VMs are correctly synchronized between the two systems.
At step 640, the MAUD 305 index is updated to reflect any extra VMs identified in the OSA. If there are VMs in the OSA that are not present in the PVIM 310, these VMs are added to the MAUD 305 index, thereby maintaining the accurate records of all the VMs managed by the OSA.
The present invention further discloses a non-transitory computer-readable medium having stored thereon computer-readable instructions. The computer-readable instructions are executed by the processor 205. The processor 205 is configured to receive the list of the CNFs from the inventory unit 230. The processor 205 is further configured to record the CNF identifier for each CNF from the list of CNFs based on the received list of CNFs. The processor 205 is further configured to receive from the inventory unit 230 the list of the CNFCs for each CNF from the list of CNFs in response to transmitting the CNFC request to the inventory unit 230 based on the recorded CNF identifier for the respective CNF. The processor 205 is further configured to compare the list of CNFs and the list of CNFCs for each CNF from the list of CNFs received from the inventory unit 230 with available data pertaining to the CNFs and the CNFCs present in at least one of, the server or backend running network elements. The processor 205 is further configured to auto sync the inventory unit 230 with the available data present in at least one of, the server or the backend running network elements pertaining to the CNFs and the CNFCs based on determining the mismatch with the list of CNFs and the list of CNFCs at the inventory unit 230 when compared with the available data.
[0075] A person of ordinary skill in the art will readily ascertain that the illustrated embodiments and steps in description and drawings (FIG.1-6) are set out to explain the exemplary embodiments shown, and it should be anticipated that ongoing technological development will change the manner in which particular functions are performed. These examples are presented herein for purposes of illustration, and not limitation. Further, the boundaries of the functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternative boundaries can be defined so long as the specified functions and relationships thereof are appropriately performed. Alternatives (including equivalents, extensions, variations, deviations, etc., of those described herein) will be apparent to persons skilled in the relevant art(s) based on the teachings contained herein. Such alternatives fall within the scope and spirit of the disclosed embodiments.
The present disclosure includes technical advancement to such as, enhanced auto-synchronization mechanisms for real-time consistency. Sophisticated data comparison algorithms leverage machine learning to detect discrepancies. Scalable and flexible database solutions for handling large volumes of data. Unified management interfaces for streamlined monitoring and control. Intelligent reporting and analytics tools that provide actionable insights for network optimization. The present invention collectively improves operational efficiency, accuracy, and scalability in complex network environments.
[0076] The present invention offers multiple advantages for efficient resource and inventory management by auto-synchronizing data, reducing errors, and preventing instantiation failures due to resource mismatch. The present invention uses asynchronous event-based implementation which includes fault tolerance and high availability. The present invention eliminates redundant backend management, ensuring seamless and time-efficient operation. Additionally, the present invention identifies and removes extra VNFs/CNFs, synchronizes resources at both CNF and VNF levels, and minimizes manual intervention by automating inventory updates and error handling.
[0077] The present invention offers multiple advantages over the prior art and the above listed are a few examples to emphasize on some of the advantageous features. The listed advantages are to be read in a non-limiting manner.

REFERENCE NUMERALS

[0078] Environment- 100
[0079] User Equipment (UE)- 110
[0080] Server- 115
[0081] Network- 105
[0082] System -120
[0083] Processor- 205
[0084] Memory- 210
[0085] User interface- 215
[0086] Database – 220
[0087] Transceiver unit - 225
[0088] Inventory unit - 230
[0089] Recording unit - 235
[0090] Comparing unit - 240
[0091] Syncing unit - 245
[0092] Micro-Service Auditor (MAUD) – 305
[0093] Physical and Virtual Inventory Manager (PVIM) – 310
[0094] Inventory Manager_Audit (IM_AU) interface - 315
,CLAIMS:CLAIMS
We Claim:
1. A method (500) to manage Container Network Functions (CNFs) in a network (105), the method (500) comprises the steps of:
receiving, by one or more processors (205), a list of Container Network Functions (CNFs) from an inventory unit (230);
recording, by the one or more processors (205), a CNF identifier for each CNF from the list of CNFs based on the received list of CNFs;
receiving, by the one or more processors (205), from the inventory unit, a list of Container Network Functions Components (CNFCs) for each CNF from the list of CNFs in response to transmitting a CNFC request to the inventory unit (230) based on the recorded CNF identifier for the respective CNF;
comparing, by the one or more processors (205), the list of CNFs and the list of CNFCs for each CNF from the list of CNFs received from the inventory unit (230) with available data pertaining to the CNFs and the CNFCs present in at least one of, a server or backend running network elements; and
auto syncing, by the one or more processors (205), the inventory unit (230) with the available data present in at least one of, the server or the backend running network elements pertaining to the CNFs and the CNFCs based on determining a mismatch with the list of CNFs and the list of CNFCs at the inventory unit (230) when compared with the available data.

2. The method (500) as claimed in claim 1, wherein the step of, receiving, a list of Container Network Functions (CNFs) from an inventory unit (230), includes the step of:
transmitting, by the one or more processors (205), a CNF request to the inventory unit (230) to retrieve the list of CNFs from the inventory unit (230).

3. The method (500) as claimed in claim 1, wherein the step of, receiving, from the inventory unit (230), a list of Container Network Functions Components (CNFCs) for each CNF from the list of CNFs in response to transmitting a request to the inventory unit (230) based on the recorded CNF identifier for the respective CNF, includes the step of:
transmitting, by the one or more processors (205), the CNFC request to the inventory unit (230) to retrieve the list of CNFCs corresponding to the respective CNF, wherein the CNFC request includes information of the CNF identifier.

4. The method (500) as claimed in claim 1, wherein the step of, comparing, the list of CNFs and the list of CNFCs for each CNF from the list of CNFs received from the inventory unit (230) with available data pertaining to the CNFs and the CNFCs at least one of, a server or backend running network elements, includes the steps of:
transmitting, by the one or more processors (205), a retrieval request to at least one of, the server or the backend running network elements, wherein the retrieval request pertains to retrieving available data pertaining to the CNFs and the CNFCs for each of the CNF present in at least one of, the server or the backend running network elements;
comparing, by the one or more processors (205), each of the CNF from the list of CNFs with the available data pertaining to the CNFs present in at least one of, the server or the backend running network elements, based on the transmitted retrieval request, wherein each of the CNF from the list of CNFs is compared with the available data pertaining to the CNFs present in at least one of, the server or the backend running network elements utilizing the CNF identifier; and
when there is a match with the CNFs of the inventory unit (230) with the available data of the CNFs, comparing, by the one or more processors (205), the list of CNFCs for each of the respective CNF from the list of CNFs with the available data pertaining to the CNFCs in order to determine the mismatch.

5. The method (500) as claimed in claim 1, wherein the inventory unit (230) is auto synced with the available data at least one of, the server or the backend running network elements utilizing an interface.

6. The method (500) as claimed in claim 1, wherein the step of, auto syncing, the inventory unit (230) with the available data at least one of, the server or the backend running network elements pertaining to the CNFs and the CNFCs based on determining a mismatch with the list of CNFs and the list of CNFCs at the inventory unit (230) when compared with the available data, further includes the steps of:
determining, by the one or more processors (205), whether the inventory unit (230) includes one or more additional CNFCs when compared to the corresponding available data present in at least one of, the server or the backend running network elements; and
when determined present, removing, by the one or more processors (205), the data pertaining to the one or more additional CNFCs from the inventory unit;
determining, by the one or more processors (205), whether at least one of the server or the backend running network elements includes one or more additional CNFCs when compared to the corresponding available data present in the inventory unit (230),
when determined present, removing, by the one or more processors (205), the data pertaining to the one or more additional CNFCs from at least one of, the server or the backend running elements.

7. A system (120) to manage Container Network Functions (CNFs)in a network (105), the system (120) comprising:
a transceiver unit (225), configured to:
receive, a list of Container Network Functions (CNFs) from an inventory unit (230);
a recording unit (235), configured to, record, a CNF identifier for each CNF from the list of CNFs based on the received list of CNFs; and
the transceiver unit (225) receive, from the inventory unit, a list of Container Network Functions Components (CNFCs) for each CNF from the list of CNFs in response to transmitting a CNFC request to the inventory unit (230) based on the recorded CNF identifier for the respective CNF;
a comparing unit (240), configured to, compare, the list of CNFs and the list of CNFCs for each CNF from the list of CNFs received from the inventory unit (230) with available data pertaining to the CNFs and the CNFCs present in at least one of, a server or backend running network elements; and
a syncing unit (245), configured to, auto sync, the inventory unit (230) with the available data present in at least one of, the server or the backend running network elements pertaining to the CNFs and the CNFCs based on determining a mismatch with the list of CNFs and the list of CNFCs at the inventory unit (230) when compared with the available data.

8. The system (120) as claimed in claim 7, wherein the transceiver unit, receives, the list of CNFs from the inventory unit (230), by:
transmitting, a CNF request to the inventory unit (230) to retrieve the list of CNFs from the inventory unit (230).

9. The system (120) as claimed in claim 7, wherein the transceiver unit (225), receives, from the inventory unit (230), the list of CNFCs for each CNF from the list of CNFs in response to transmitting a request to the inventory unit (230) based on the recorded CNF identifier for the respective CNF, by:
transmitting, the CNFC request to the inventory unit (230) to retrieve the list of CNFCs corresponding to the respective CNF, wherein the CNFC request includes information of the CNF identifier.

10. The system (120) as claimed in claim 7, wherein the comparing unit (240), compares, the list of CNFs and the list of CNFCs for each CNF from the list of CNFs received from the inventory unit (230) with available data pertaining to the CNFs and the CNFCs at least one of, the server or the backend running network elements, by:
transmitting, a retrieval request to at least one of, the server or the backend running network elements, wherein the retrieval request pertains to retrieving available data pertaining to the CNFs and the CNFCs for each of the CNF present in at least one of, the server or the backend running network elements;
comparing, each of the CNF from the list of CNFs with the available data pertaining to the CNFs present in at least one of, the server or the backend running network elements, based on the transmitted retrieval request, wherein each of the CNF from the list of CNFs is compared with the available data pertaining to the CNFs present in at least one of, the server or the backend running network elements utilizing the CNF identifier; and
when there is a match with the CNFs of the inventory unit (230) with the available data of the CNFs, comparing, the list of CNFCs for each of the respective CNF from the list of CNFs with the available data pertaining to the CNFCs in order to determine the mismatch.

11. The system (120) as claimed in claim 7, wherein the inventory unit (230) is auto synced with the available data at least one of, the server or the backend running network elements utilizing an interface.

12. The system (120) as claimed in claim 7, wherein the syncing unit (245), is further configured to:
determine, whether the inventory unit (230) includes one or more additional CNFCs when compared to the corresponding available data present in at least one of, the server or the backend running network elements; and
when determined present, remove, the data pertaining to the one or more additional CNFCs from the inventory unit;
determine, whether at least one of the server or the backend running network elements includes one or more additional CNFCs when compared to the corresponding available data present in the inventory unit (230); and
when determined present, remove, the data pertaining to the one or more additional CNFCs from at least one of, the server or the backend running elements.