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
SYSTEM AND METHOD FOR MANAGING ONE OR MORE NETWORK FUNCTIONS
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 wireless communication networks, more particularly relates to a method and a system for managing one or more Network Functions (NFs).
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. The communication network includes a plurality of network elements which are configured to operate in specific manners to improve credibility of the communication network. The communication network incorporates inventories to safe-keep resources and mechanism to efficiently distribute resources to all Network Functions (NFs) in the network so as to process the service requests.
[0003] Inventory Manager (IM) maintains a virtual inventory and a limited physical inventory. The IM maintains the relation between the physical and virtual resources with respect to overlay to manage storage memory allocation. Also, the IM describes physical and virtual resources in view of different attributes using updates from external micro-service. Thus, data accuracy of the inventory manager is dependent upon the micro-services which create, update, delete the one or more resources and at the same time update these events with the IM. Other services can query IM relations, attributes etc. Using query Application Programming Interface (APIs) provided by the IM. However, as there are thousands of NFs that are running in parallel to process multiple requests within a specific time frame. Therefore, there is a need to properly allocate the one or more resources to each NFs which includes a Container Network Function (CNF) or a Virtual Network Function (VNF) and retract the one or more resources from idle NFs.
[0004] Presently, there is no system and method available to monitor the overall usage of the one or more resources such as CPU, RAM, STORAGE, BANDWIDTH, and COUNTERS for a given VNF/CNF which can be instantiated across any number of hosts and sites. There is no appropriate mechanism in place to track physical resources usage across all instances of the VNF/CNF. So, there is a need to introduce a system and method to monitor, track and allocate the one or more resources to the CNF/VNF so that the network can operate properly. However, if such a system and method are to be carried out by any available interface which is also intended to perform other micro-services, there may be cases when there will be operational errors or downtime or malfunctioning of that particular interface. As resource allocation is crucial for the network elements to work properly, failure to do so may lead to cascaded failure in the network. Therefore, it is imperative that there be a dedicated interface to carry out the monitoring, tracking and allocation of the one or more resources.
[0005] Thus, there is requirement of a system and a method to monitor, track and manage resource allocated to each NF(s) via a single platform or the interface by which all the operations at the IM. The IM can be relied on as a resource/capacity management service and the network may operate with ease, with improved efficacy and without consuming too much time.
SUMMARY OF THE INVENTION
[0006] One or more embodiments of the present disclosure provide a method and a system for managing one or more Network Functions (NFs).
[0007] In one aspect of the present invention, the method for managing the one or more Network Functions (NFs) is disclosed. The method includes the step of receiving, by one or more processors, a request from a user for monitoring of a plurality of network functions in a network. The method includes the step of retrieving, by the one or more processors, from an Inventory Manager (IM), details of the plurality of network functions upon receiving the request from the user. The method includes the step of updating, by the one or more processors, one or more network functions along with associated one or more resources based on analysis of an operational state of each of the plurality of network functions.
[0008] In one embodiment, the details of the plurality of network functions include at least one of, identifier data of each network function, host details and flavor details.
[0009] In another embodiment, the step of, updating, one or more network functions along with associated one or more resources based on analysis of an operational state of each of the plurality of network functions, includes the steps of monitoring, by the one or more processors, via a Capacity Manager (CMP), the operational state of each of the plurality of network functions, wherein the operational state is at least one of, an active state or an inactive state. The step of, updating, one or more network functions along with associated one or more resources based on analysis of an operational state of each of the plurality of network functions, includes the steps of if determined the one or more network functions is in the inactive state based on the monitoring, terminating, by the one or more processors, via the CMP, the one or more network functions along with the associated one or more resources. The step of, updating, one or more network functions along with associated one or more resources based on analysis of an operational state of each of the plurality of network functions, includes the steps of determining, by the one or more processors, if the one or more new network functions are required to be added to the network based on a scaling policy. The step of, updating, one or more network functions along with associated one or more resources based on analysis of an operational state of each of the plurality of network functions, includes the steps ofadding, by the one or more processors, the one or more new networks functions in response to determining that the one or more new network functions are required to be added to the network. The step of, updating, one or more network functions along with associated one or more resources based on analysis of an operational state of each of the plurality of network functions, includes the steps of assigning, by the one or more processors, additional one or more resources corresponding to the added one or more new network functions. .
[0010] In yet another embodiment, the one or more processors communicates with the IM via a communication channel. The communication channel is an interface between the IM and the CMP. The interface is at least one of, an Inventory Manager_ Control Plane (IM_CP) interface.
[0011] In yet another embodiment, the interface initiates a scaling process by sending a task creation event to the CMP. The interface waits for a response from the CMP, which only responds the task creation event has breached.
[0012] In yet another embodiment, the IM interacts with the CMP via the communication channel for enrichment of performance data including at least one of, alarms and counters.
[0013] In another aspect of the present invention, the system for managing the one or more Network Functions (NFs) is disclosed. The system includes a transceiver, configured to receive a request from a user for monitoring of a plurality of network functions in a network. The system includes a retrieving unit, configured to retrieve, from an Inventory Manager (IM), details of the plurality of network functions upon receiving the request from the user. The system includes an updating unit, configured to update, one or more network functions along with associated one or more resources based on analysis of an operational state of each of the plurality of network functions.
[0014] In another aspect of the present invention, a User Equipment (UE) is disclosed. One or more primary processors communicatively coupled to one or more processors. The one or more primary processors coupled with a memory. The said memory stores instructions which when executed by the one or more primary processors causes the UE to transmit a request from a user to the one or more processors for analysis of a plurality of network functions.
[0015] In another aspect of the present invention, a non-transitory computer-readable medium having stored thereon computer-readable instructions that, when executed by a processor is disclosed. The processor is configured to receive a request from a user for monitoring of a plurality of network functions in a network. The processor is configured to retrieve, from an Inventory Manager (IM), details of the plurality of network functions upon receiving the request from the user. The processor is configured to update one or more network functions along with associated one or more resources based on analysis of an operational state of each of the plurality of network functions.
[0016] 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
[0017] 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.
[0018] FIG. 1 is an exemplary block diagram of an environment for managing one or more Network Functions (NFs), according to one or more embodiments of the present disclosure;
[0019] FIG. 2 is an exemplary block diagram of a system for managing the one or more NFs, according to one or more embodiments of the present disclosure;
[0020] FIG. 3a is an exemplary representation of an interface in a network environment, FIG. 3b is a block diagram of an architecture implemented in the system of the FIG. 2 to manage lifecycle of the one or more NFs, according to one or more embodiments of the present disclosure;
[0021] FIG. 4 is a signal flow diagram for managing the one or more NFs, according to one or more embodiments of the present disclosure;
[0022] FIG. 5 illustrates a Management and Orchestration (MANO) architecture framework that can be implemented in the system of FIG.2, according to one or more embodiments of the present disclosure; and
[0023] FIG. 6 is a flow diagram illustrating a method for managing the one or more NFs, according to one or more embodiments of the present disclosure.
[0024] The foregoing shall be more apparent from the following detailed description of the invention.
DETAILED DESCRIPTION OF THE INVENTION
[0025] 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.
[0026] 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.
[0027] 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.
[0028] Various embodiments of the present invention provide a system and method to efficiently monitor information on one or more resources allocated to one or more Network Functions (NFs) in a network and to track the operational data for all running NF(s), i.e., CNF/CNFC or VNF (virtual network function) to avoid request failure. The present invention also discloses a dedicated interface to interact and to notify the resource or capacity management system (i.e., capacity manager (CMP)) during instantiation or termination of any network function. The present interface is configured to perform all required operations at an Inventory Manager (IM) towards the CMP.
[0029] Referring to FIG. 1, FIG. 1 illustrates an exemplary block diagram of an environment 100 for managing one or more Network Functions (NFs) in a network 105, according to one or more embodiments of the present invention. The environment 100 includes the network 105, a User Equipment (UE) 110, a server 115, a system 120, and a plurality of Network Functions (NFs) 125. The UE 110 aids a user to interact with the system 120 for transmitting the one or more requests from the user to one or more processors 205 (shown in FIG. 2) for monitoring of the plurality of NFs 125. In an embodiment, the user is one of, but not limited to, a network operator or a service provider. In an embodiment, the one or more requests include, but not limited to, analysis request, status request, configuration request, performance report request, security audit request, and fault detection request. Herein, managing the one or more NFs pertains to at least one of, but not limited to, a creating, an adding, an updating, a terminating and deleting Container Network Function/ Virtual Network Function (CNF/VNF).
[0030] The environment 100 includes the plurality of NFs 125 refers to multiple individual network components, services, or processes that work together to support the operation of the network 105. The plurality of NFs 125 is responsible for handling specific tasks like data routing, traffic management, security, and session control within the network. Each network function plays a distinct role but collectively contributes to the overall performance, security, and efficiency of the network 105. Analyzing the plurality of NFs 125 refers to multiple, distinct components or services that collectively enable the operation of a data network. Each network function performs specific tasks that contribute to the network's overall functionality, including routing traffic, managing sessions, securing connections, and providing resources.
[0031] For the purpose of description and explanation, the description will be explained with respect to the UE 110, or to be more specific will be explained with respect 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. Each of the UE 110 from the first UE 110a, the second UE 110b, and the third UE 110c is configured to connect to the server 115 via the network 105. In an embodiment, each of the first UE 110a, the second UE 110b, and the third UE 110c 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 smartphones, 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.
[0032] 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.
[0033] 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, a defense facility, or any other facility that provides content.
[0034] The environment 100 further includes the system 120 communicably coupled to the server 115 and each of the first UE 110a, the second UE 110b, and the third UE 110c via the network 105. The system 120 is configured for managing the one or more network functions. The system 120 is adapted to be embedded within the server 115 or is embedded as the individual entity, as per multiple embodiments of the present invention.
[0035] Operational and construction features of the system 120 will be explained in detail with respect to the following figures.
[0036] FIG. 2 is an exemplary block diagram of a system 120 for managing the one or more NFs, according to one or more embodiments of the present disclosure.
[0037] The system 120 includes a processor 205, a memory 210, a user interface 215, and a database 250. For the purpose of description and explanation, the description will be explained with respect to one or more processors 205, or to be more specific will be explained with respect to the processor 205 and should nowhere be construed as limiting the scope of the present disclosure. The one or more processor 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.
[0038] 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 EPROM, flash memory, and the like.
[0039] In one embodiment, the Inventory Manager (IM) 245 includes at least one of, but not limited to, a plurality of Virtual Inventory Managers (VIMs) and a plurality of Physical Virtual Inventory Managers (PVIMs). In one embodiment, the VIM is a component responsible for a process of evaluating, tracking and managing an accurate list of services, equipment’s and related resources used within the network 105. In one embodiment, the PVIM is a component responsible for maintaining and managing the one or more NFs of both physical and virtual network resources. The physical and virtual network resources refer to tangible and intangible components that make up a network infrastructure, providing connectivity and communication capabilities. The physical network resources include, but are not limited to, routers and switches, cables and fibre optics, servers, base stations, data centres. The virtual network resources include, but are not limited to, virtual machines, virtual network functions, cloud-based services, network slices. In one embodiment, the PVIM manages, updates, creates and removes any physical or virtual or graphical or indexing data stored in the inventory 110.
[0040] As per the illustrated embodiment, the user interface 215 acts as a mediator between the one or more NFs and the IM 245. In an embodiment, the one or more NFs refer to individual components or units of functionality that are deployed within the network 110. The one or more NFs are responsible for performing specific tasks or services and can be dynamically managed, scaled, and monitored. The one or more NFs encompass various types of services or functions that can be registered and integrated into the network 110. The one or more NFs pertain to at least one of, network functions, micro-services, or applications running within the network 110. The micro-services are defined as the discrete, modular software component within the network 110 that performs the specific function or service. Each microservice is designed to operate independently and interact with other microservices through well-defined interfaces. The microservices collectively form the larger, distributed system that can be managed and scaled according to the needs of the network 110. The one or more NFs is the specific operational occurrence of the microservice, enabling scalability and management of the microservices deployment. The type of the one or more NFs includes, but not limited to, Virtual Network Function (VNF) instances, database service instances, Container Network Function (CNF) service instances, network slicing, and authentication and authorization services.
[0041] In one embodiment, the one or more NFs are Hypertext Transfer Protocol (“HTTP”) based applications that by design perform a single function. The one or more NFs is an approach to building the application that breaks its functionality into modular components. In one embodiment, the user interface 215 includes a variety of interfaces, for example, a graphical user interface, a web user interface, a Command Line Interface (CLI), and the like. The user interface 215 is used to update and manage data about hosts and sites in the IM 245. In particular, the user interface 215 may be an at least one of, an Inventory Manager Control Plane (IM_CP) interface 305 (as shown in FIG.3a). The IM_CP interface 305 refers to the communication interface used for control signalling between the management entities and the one or more NFs within a control plane of a network architecture. The control plane manages the signalling and control of data sessions, mobility, and services, while the user plane handles the actual data transmission. The IM_CP interface 305 ensures that control plane messages, such as session establishment, policy enforcement, or mobility management, are appropriately exchanged between the one or more NFs.
[0042] The database 250 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 250 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.
[0043] Further, the processor 205, 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 processor 205 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 205. 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.
[0044] In order for the system 120 to manage the one or more network functions, the processor 205 includes a transceiver 220, a retrieving unit 225, an updating unit 235, a Capacity Manager (CMP) 240, and the IM 245 communicably coupled to each other. In an embodiment, operations and functionalities of the transceiver 220, the retrieving unit 225, the updating unit 235, the CMP 240, and the IM 245 can be used in combination or interchangeably.
[0045] Initially, the request transmitted by the user via the UI 215 for retrieving details pertaining to the plurality of NFs 125 in the network 105. In one embodiment, the transceiver 220 is configured to receive the request from the user for monitoring the plurality of NFs 125 in the network 105. In particular, the request is at least one of, a Hypertext Transfer Protocol (HTTP) request. In one embodiment, the details pertaining to the plurality of NFs 125 in the network 105 include at least one of, but not limited to, identifier data of each network function, host details and flavor details. In an alternate embodiment, the request from the user is received for at least one of, creating, updating, terminating and deleting details pertaining to the plurality of NFs 125 in the network 105.
[0046] Upon receiving the requests from the user for monitoring the plurality of NFs 125, the retrieving unit 225 is configured to retrieve the details of the plurality of NFs 125 from the IM 245 based on the received request. In one embodiment, the details pertaining to the plurality of NFs 125 in the network 105 include at least one of, but not limited to, identifier data of each network function, host details and flavor details. The information retrieved by the retrieving unit 225 includes operational and identification details about the one or more NFs. The identifier data of each network function refers to unique identifiers for each network function (e.g., NF ID), which aid in identifying and managing individual network functions. The host details refer to information about where each NF is hosted, such as the server 115, data center, or cloud location. The flavor details include configuration details of the one or more NFs, such as resource allocation (e.g., CPU, memory), service capabilities, or the performance characteristics of the data.
[0047] Upon retrieving the details of the plurality of NFs 125 from the IM 245 based on the received request, the one or more processors 205 communicates with the IM 245 via a communication channel. In an embodiment, the communication channel is an interface between the IM 245 and the CMP 240. In one embodiment, the interface is at least one of, the IM_CP interface 305 through which the communication between the IM 245 and the CMP 240 takes place. The communication channel is designed to send packets/requests across an internet and ensure the successful delivery of data and messages over the network 110. In other words, the communication channel is between a source and a destination, such as the IM 245 and the CMP 240 ensures secure data transmission therebetween. The interface initiates a scaling by transmitting a task creation event to the CMP 240 on detection of a breach. Thereafter, the interface waits for a response from the CMP 240. The response corresponds to the breached response. The IM 245 interacts with the CMP 240 via the communication channel for enrichment of performance data including at least one of, alarms and counters, is transmitted safely, preventing unauthorized access or data breaches.
[0048] The CMP 240 processes and enhances the received data, performing tasks such as correlating alarms with specific events, analyzing counters, and generating insights that can be used to optimize network performance. The enrichment refers to enhancing the performance data by adding context, meaning, and actionable insights. For example, correlating alarms with specific thresholds or using counter data to detect potential issues before the system 120 cause performance degradation. The alarms refer to notifications or alerts triggered when predefined thresholds (e.g., high CPU usage, low memory availability) are breached. The counters refer to metrics that provide detailed performance statistics (e.g., number of packets processed, data throughput, or latency). In an exemplary embodiment, the network is experiencing performance degradation, with certain thresholds being breached, such as high CPU usage or packet loss. The IM 245 collects performance data, including the alarms related to the CPU usage and the counters tracking network traffic. The IM 245 sends the collected performance data to the CMP 240 over the secure communication channel for further analysis. The CMP 240 processes and enriches the data, correlating alarms with specific performance issues and using the counter data to provide recommendations for scaling or load balancing.
[0049] In another embodiment, upon establishing the communication channel between the IM 245 and the CMP 240 for communicating data therebetween, the updating unit 235 is configured to update the one or more NFs along with associated one or more resources based on analysis of an operational state of each of the plurality of network functions 125. The updating unit 235 is responsible for modifying or updating the configuration, software, or one or more resources of the one or more NFs within the network 105, based on the analysis of the current operational state of each of the plurality of NFs 125. In one embodiment, the operational state of each of the plurality of NFs 125 are monitored by the CMP 240. In an embodiment, the operational state is at least one of, an active state or an inactive state. The CMP 240 manages the virtualized resources in the network. When the updating unit 235 determines that the one or more NFs is in the inactive state, the CMP 240 is responsible for terminating the one or more NFs and deallocating the associated resources (such as virtual CPU, memory, storage, etc.).The one or more NFs are terminated along with the associated one or more resources by the CMP 240 if determined the one or more network functions is in the inactive state based on the monitoring.
[0050] In another embodiment, the updating unit 235 is further configured to determine if one or more new NFs are required to be added to the network 105 based on a scaling policy. The one or more new NFs are either deployed from pre-existing templates (e.g., Virtual Machine (VM) images or containers) or instantiated through network orchestration platforms such as a Network Function Virtualization Orchestrator (NFVO). The scaling policy is a set of predefined thresholds, rules and conditions used to determine when and how to adjust the one or more resources allocated to a service, the application, or network function. The updating unit 235 collects one or more metrics from the network 105. The one or more metrics include, but are not limited to, CPU, memory, and bandwidth utilization of existing NFs. The collected metrics are processed to determine the overall network health and efficiency, looking for signs of congestion, resource saturation, or performance degradation. The updating unit 235 compares the real-time one or more metrics against the scaling policy. The scaling policy is to ensure optimal performance, resource utilization, and cost-efficiency by dynamically increasing or decreasing the one or more resources based on the predefined thresholds. The updating unit 235 continuously monitors the one or more NFs and makes decisions about updating, terminating, or removing the one or more NFs based on the network requirements.
[0051] The updating unit 235 also determines whether the one or more new NFs are required to meet network demand based on the scaling policy, which is triggered by changes in traffic volume, latency requirements, or service-level agreements (SLAs). In an exemplary embodiment, if the network 105 experiences a surge in traffic, the updating unit 235 determines additional Session Management Functions (SMFs) or User Plane Functions (UPFs) that are needed to handle the traffic load. Based on the scaling policy, new instances of these NFs will be added to the network 105. The one or more new network functions are added in response to determining that the one or more new network functions are required to be added to the network 105. The updating unit 235 is further configured to assign additional one or more resources corresponding to the added one or more new network functions.
[0052] By managing the one or more NFs, the system 120 enriches the performance data by providing additional information to the CMP 240 using the IM-CP interface, sending details of the one or more NFs, notifies the one or more services about the one or more NFs termination so that the CMP 240 manages and monitors the one or more resources efficiently, and decides whether to scale in/scale out the application based on the scaling policies.
[0053] FIG. 3a is an exemplary representation of an interface in a network environment. FIG.3b is a block diagram of an architecture of the system of FIG. 2 to manage lifecycle of one or more NFs utilizing an Inventory Manager (IM)_Control Plane (CP) interface 305, according to one or more embodiments of the present disclosure.
[0054] The architecture 300 includes the CMP 240, the IM 245, the IM_CP interface 305, and the database 250.
[0055] As shown in FIG. 3a, the communication channel is established between the IM 245 and the CMP 240. In an embodiment, the communication channel is an interface. In an embodiment, the interface is at least one of, an Inventory Manager Control Plane Function (IM_CP) interface 305. The interface 305 is configured to send and receive the data between the IM 245 and the CMP 240. The IM 245 is responsible for managing the virtual infrastructure, handling resource allocation, scaling operations, and interacting with the CMP 240. The CMP 240 handles the creation, updating, and deletion of the one or more NFs. The CMP 240 also monitors the status and performance of the one or more NFs, which reports to the IM 245. The CMP 240 is used to transmit and receive the data between the UE 110 and the IM 245 for resource allocation or deallocation based on the one or more NFs requirements. The UE 110 represents the user device that indirectly benefits from the one or more operations of the one or more NFs deployed and managed by the IM 245 and the CMP 240 provides network services to the UE 110. The interaction between the IM 245 and the CMP 240 ensures that the one or more NFs are efficiently managed, maintaining optimal performance and service availability for the UE 110.
[0056] As shown in the FIG. 3b, the inventory manager 245 maintains detailed records of the plurality of NFs 125 deployed in the network 105, including information like identifiers, host details, and resource configurations. The inventory manager 245 acts as a central repository for NF data, ensuring that the network has up-to-date information about the state of each NF. When information about the one or more NFs is needed, the inventory manager 245 sends the requests to the CMP 240. The requests typically ask the CMP 240 to analyze or provide detailed information regarding the plurality of NFs 125, such as their operational status, resource usage, or configurations.
[0057] Upon receiving the requests from the inventory manager 245, the CMP 240 monitors the operational state of each of the plurality of NFs 125. In an embodiment, the operational state is at least one of, an active state or an inactive state. The CMP 240 manages the virtualized resources in the network 105. When the updating unit 235 determines that the one or more NFs is in the inactive state, the CMP 240 is responsible for terminating the one or more NFs and deallocating its associated resources (such as virtual CPU, memory, storage, etc.). The one or more NFs are terminated along with the associated one or more resources by the CMP 240 if determined the one or more network functions is in the inactive state based on the monitoring.
[0058] The updating unit 235 is further configured to check if the one or more new NFs are required to be added to the network 105 based on the scaling policy. The updating unit 235 continuously monitors the one or more NFs and makes decisions about updating, adding, or removing the one or more NFs based on the network requirements. The updating unit 235 also checks whether one or more new NFs are required to meet network demand based on the scaling policy, which is triggered by changes in traffic volume, latency requirements, or service-level agreements (SLAs). In an exemplary embodiment, if the network experiences a surge in traffic, the updating unit 235 determines that additional Session Management Functions (SMFs) or User Plane Functions (UPFs) are needed to handle the traffic load. Based on the scaling policy, new instances of these NFs will be added to the network 105. The one or more new network functions are added. The updating unit 235 is further configured to assign at least one of, existing one or more resources or new one or more resources to the added one or more new network functions if determined the one or more new network functions are required to be added based on the checking.
[0059] FIG. 4 is a signal flow diagram for managing the one or more NFs, according to one or more embodiments of the present disclosure.
[0060] At S402, Initially, the request is transmitted by the user for monitoring the plurality of NFs 125 in the network 105. In particular, the request is at least one of, a Hypertext Transfer Protocol (HTTP) request. In one embodiment, the details pertaining to the plurality of NFs 125 in the network 105 include at least one of, but not limited to, identifier data of each network function, host details and flavor details. In an alternate embodiment, the request from the user is received for at least one of, creating, updating, terminating and deleting details pertaining to the plurality of NFs 125 in the network 105.
[0061] At S404, upon receiving the requests from the user for monitoring the plurality of NFs 125, the retrieving unit 225 is configured to retrieve the details of the plurality of NFs 125 from the IM 245 based on the received request. In one embodiment, the details pertaining to the plurality of NFs 125 in the network 105 include at least one of, but not limited to, identifier data of each network function, host details and flavor details. The information retrieved by the retrieving unit 225 includes operational and identification details about the one or more NFs. The identifier data of each network function refers to unique identifiers for each network function (e.g., NF ID), which aid in identifying and managing individual network functions. The host details refer to information about where each NF is hosted, such as the server 115, data center, or cloud location. The flavor details include configuration details of the one or more NFs, such as resource allocation (e.g., CPU, memory), service capabilities, or the performance characteristics of the data.
[0062] Upon retrieving the details of the plurality of NFs 125 from the IM 245 based on the received request, the communication channel is an interface between the IM 245 and the CMP 240. In one embodiment, the communication channel is the medium through which the communication between the IM 245, the system 120 and the CMP 240 takes place. The communication channel is designed to send packets/requests across an internet and ensure the successful delivery of data and messages over the network 110. In other words, the communication channel is between a source and a destination, such as the IM 245 and the CMP 240 ensures secure data transmission therebetween. The interface initiates the scaling by transmitting the task creation event to the CMP 240 on detection of the breach. Thereafter, the interface waits for the response from the CMP 240. The response corresponds to the breached response. The breached response refers to overutilization of the resource, and traffic overload. The response often triggers further actions, such as scaling up resources, reallocating tasks, or initiating corrective measures to address the breach and maintain system performance and stability. The IM 245 interacts with the CMP 240 via the communication channel for enrichment of performance data including at least one of, alarms and counters, is transmitted safely, preventing unauthorized access or data breaches.
[0063] The CMP 240 processes and enhances the received data, performing tasks such as correlating alarms with specific events, analyzing counters, and generating insights that can be used to optimize network performance. The enrichment refers to enhancing the performance data by adding context, meaning, and actionable insights. For example, correlating alarms with specific thresholds or using counter data to detect potential issues before the system 120 cause performance degradation. The alarms refer to notifications or alerts triggered when predefined thresholds (e.g., high CPU usage, low memory availability) are breached. The counters refer to metrics that provide detailed performance statistics (e.g., number of packets processed, data throughput, or latency). In an exemplary embodiment, the network is experiencing performance degradation, with certain thresholds being breached, such as high CPU usage or packet loss. The IM 245 collects performance data, including the alarms related to the CPU usage and the counters tracking network traffic. The IM 245 sends the collected performance data to the CMP 240 over the secure communication channel for further analysis. The CMP 240 processes and enriches the data, correlating alarms with specific performance issues and using the counter data to provide recommendations for scaling or load balancing.
[0064] At S408, the updating unit 235 is configured to update the one or more NFs along with associated one or more resources based on analysis of an operational state of each of the plurality of network functions 125. The updating unit 235 is responsible for modifying or updating the configuration, software, or one or more resources of the one or more NFs within the network 105, based on the analysis of the current operational state of each of the plurality of NFs 125. In one embodiment, the operational state of each of the plurality of NFs 125 are monitored by the CMP 240. In an embodiment, the operational state is at least one of, an active state or an inactive state. The CMP 240 manages the virtualized resources in the network. When the updating unit 235 determines that the one or more NFs is in the inactive state, the CMP 240 is responsible for terminating the one or more NFs and deallocating the associated resources (such as virtual CPU, memory, storage, etc.).The one or more NFs are terminated along with the associated one or more resources by the CMP 240 if determined the one or more network functions is in the inactive state based on the monitoring.
[0065] In another embodiment, the updating unit 235 is further configured to determine if the one or more new NFs are required to be added to the network 105 based on a scaling policy. The scaling policy is a set of rules and conditions used to determine when and how to adjust the one or more resources allocated to a service, the application, or network function. The updating unit 235 collects one or more metrics from the network 105. The one or more metrics include, but are not limited to, CPU, memory, and bandwidth utilization of existing NFs. The collected metrics are processed to determine the overall network health and efficiency, looking for signs of congestion, resource saturation, or performance degradation. The updating unit 235 compares the real-time one or more metrics against the scaling policy. The scaling policy is to ensure optimal performance, resource utilization, and cost-efficiency by dynamically increasing or decreasing the one or more resources based on the predefined thresholds. The updating unit 235 continuously monitors the one or more NFs and makes decisions about updating, terminating, or removing the one or more NFs based on the network requirements.
[0066] The updating unit 235 also determines whether one or more new NFs are required to meet network demand based on the scaling policy, which is triggered by changes in traffic volume, latency requirements, or service-level agreements (SLAs). In an exemplary embodiment, if the network experiences a surge in traffic, the updating unit 235 determines that additional Session Management Functions (SMFs) or User Plane Functions (UPFs) are needed to handle the traffic load. Based on the scaling policy, new instances of these NFs will be added to the network 105. The one or more new network functions are added in response to determining that the one or more new NFs are required to meet network demand based on the scaling policy. The updating unit 235 is further configured to assign additional one or more resources to the corresponding added one or more new network functions.
[0067] At S410, upon adding or terminating the one or more new network functions, the updating unit 235 is configured to transmit an acknowledgement to the user for information about details of the one or more NFs via the UI 215.
[0068] FIG. 5 illustrates a Management and Orchestration (MANO) architecture framework 500 that can be implemented in the system of FIG.2, according to the one or more embodiments of the present disclosure. The system architecture 500 includes the user interface 215, a Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) design function module 505, a platform foundation service module 510, a platform core service module 515, and a platform resource adapter and utilities module 520.
[0069] The NFV and SDN design function module 505 is crucial for modernizing network infrastructure by enabling virtualized, scalable, and programmable network functions and management systems, particularly within the framework of CNFs. The platform foundation service module 510 refers to the underlying services and infrastructure components that support and enable the deployment, operation, and management of containerized network functions. The platform foundation service module 510 provides the essential capabilities and resources required for the CNF environment to function effectively.
[0070] The platform core service module 515 refers to the fundamental services and components that are essential for the core functionality and operation of containerized network functions. These services are critical for the effective deployment, execution, and management of CNFs, providing the necessary support and infrastructure for their operation. The platform resource adapter and utilities module 520 refers to a set of components and tools designed to manage and adapt various resources and services necessary for the operation of CNFs. The platform resource adapter and utilities module 520 plays a crucial role in integrating CNFs with underlying infrastructure and services, providing the necessary support for efficient operation, resource utilization, and interoperability.
[0071] The NFV and SDN design function module 505 includes a VNF lifecycle manger 505a, a VNF catalog 505b, a network service catalog 505c, a network slicing and service chaining manger 505d, a physical and virtual resource manager 505e, and a CNF lifecycle manager 505f.
[0072] The VNF lifecycle manager 505a is responsible for managing the entire lifecycle of Virtual Network Functions (VNFs). The VNF lifecycle manager 505b ensures that VNFs or CNFs are deployed, configured, monitored, scaled, and eventually decommissioned effectively. The VNF catalog 505b (referred to as a CNF catalog) is a repository or registry that stores information about various containerized network functions and their configurations. The VNF catalog 505b serves as a central reference for managing and deploying CNFs, providing details about their capabilities, requirements, and how they can be used within the network environment. The network service catalog 505c is a comprehensive repository that organizes and manages the information related to network services composed of multiple CNFs or other network functions. The network service catalog 505c serves as a central resource for defining, deploying, and managing these services within a containerized network environment.
[0073] The network slicing and service chaining manager 505d is a crucial component responsible for orchestrating and managing network slicing and service chaining functionalities. These functionalities are essential for efficiently utilizing network resources and delivering tailored network services in a dynamic and scalable manner. The physical and virtual resource manager 505e is a critical component responsible for overseeing and managing both physical and virtual resources required to support the deployment, operation, and scaling of CNFs. The physical and virtual resource manager 505e ensures that the necessary resources are allocated efficiently and effectively to meet the performance, availability, and scalability requirements of containerized network functions.
[0074] Further, the CNF lifecycle manager 505f is a component responsible for overseeing the entire lifecycle of containerized network functions. This includes the management of CNFs from their initial deployment through ongoing operation and maintenance, up to their eventual decommissioning. The CNF lifecycle manager 505f ensures that the CNFs are efficiently deployed, monitored, scaled, updated, and removed, facilitating the smooth operation of network services in a containerized environment.
[0075] The platform foundation service module 510 includes a microservice elastic load balancer 510a, an identity and access manager 510b, a command line interface 510c, a central logging manager 510d and an event routing manager 510e.
[0076] The microservice elastic load balancer 510a is a specific type of load balancer designed to dynamically distribute network traffic across a set of microservices running in a containerized environment. Its primary purpose is to ensure efficient resource utilization, maintain high availability, and improve the performance of network services by evenly distributing incoming traffic among multiple instances of microservices. The identity and access manager 510b is a critical component responsible for managing and securing access to containerized network functions and their resources. The identity and access manager 510b ensures that only authorized users and systems can access specific resources, and it enforces policies related to identity verification, authentication, authorization, and auditing within the CNF ecosystem.
[0077] The central logging manager 510d is a component responsible for aggregating, managing, and analyzing log data from various containerized network functions and associated infrastructure components. This centralized approach to logging ensures that logs are collected from disparate sources, consolidated into a single repository, and made accessible for monitoring, troubleshooting, and auditing purposes. The event routing manager 510e is a component responsible for handling the distribution and routing of events and notifications generated by various parts of the CNF environment. This includes events related to system status, performance metrics, errors, and other operational or application-level events. The event routing manager 510e ensures that these events are efficiently routed to the appropriate consumers, such as monitoring systems, alerting systems, or logging infrastructure, for further processing and action.
[0078] The platform core service module 515 includes an NFV infrastructure monitoring manager 515a, an assurance manager 515b, a performance manger 515c, a policy execution engine 515d, a capacity monitoring manger 515e, a release management repository 515f, a configuration manger and GCT 515g, a NFV platform decision analytics unit 515h, a platform NoSQL DB 515i, a platform scheduler and Cron Jobs module 515j, a VNF backup & upgrade manger 515k, a micro service auditor 515l, and a platform operation, administration and maintenance manager 515m.
[0079] The NFV infrastructure monitoring manager 515a monitors the underlying infrastructure of NFV environments, including computing, storage, and network resources. The NFV infrastructure monitoring manager 515a provides real-time visibility into resource health, performance, and utilization. Further, the NFV infrastructure monitoring manager 515a detects and alerts infrastructure issues. Further, the NFV infrastructure monitoring manager 515a integrates with monitoring tools to ensure reliable operation of CNFs.
[0080] The assurance manager 515b manages the quality and reliability of network services by ensuring compliance with service level agreements (SLAs) and operational standards. The performance manager 515c optimizes the performance of CNFs by tracking and analyzing key performance indicators (KPIs). The policy execution engine 515d enforces and applies policies within the CNF environment to manage operations and access. Further, the policy execution engine 515d executes policies related to security, resource allocation, and service quality. Further, the policy execution engine 515d executes policies translates policy rules into actionable configurations and enforces compliance across CNFs.
[0081] The capacity monitoring manager 515e monitors and manages the capacity of resources within the CNF environment to ensure optimal usage and avoid resource shortages. The release management repository 515f stores and manages software releases, configurations, and versions of CNFs. Further, the release management repository 515f keeps track of different versions of CNFs.
[0082] The configuration manager and Generic Configuration Tool (GCT) 515g manages the configuration of CNFs and related infrastructure components. The NFV platform decision analytics unit 515h analyzes data from a NFV platform to support decision-making and strategic planning.
[0083] The platform NoSQL database (DB) 515i is used for storing and managing large volumes of unstructured or semi-structured data within the CNF environment. The platform scheduler and Cron Jobs module 515j manage scheduled tasks and periodic operations within the CNF environment. The VNF backup & upgrade manager 515k oversees the backup and upgrade processes for Virtual Network Functions (VNFs) within the CNF environment.
[0084] The micro service auditor 515l monitors and audits microservices to ensure compliance with operational and security standards. The platform operation, administration and maintenance manager 515m manages the overall operation, administration, and maintenance of the CNF platform.
[0085] The platform resource adapter and utilities module 520 includes a platform external API adaptor and gateway 520a, a generic decoder and indexer 520b, a swarm adaptor 520c, an OpenStack API adaptor 520d and a NFV gateway 520e.
[0086] The platform external API adaptor and gateway 520a facilitate communication between the CNF platform and external systems or services by providing an interface for API interactions. The generic decoder and indexer 520b decode and indexes various types of data and logs within the CNF environment. The swarm adaptor 520c facilitates communication between a swarm cluster and the CNF environment, including container deployment, scaling, and management.
[0087] The OpenStack API adaptor 520d provides an interface for the CNF platform to interact with OpenStack APIs, enabling operations such as provisioning, scaling, and managing virtual resources. The NFV gateway 520e manages and facilitates communication between NFV (Network Functions Virtualization) components and external networks or services.
[0088] FIG. 6 is a flow diagram illustrating a method 600 for managing the one or more NFs in the network 105, according to one or more embodiments of the present disclosure. For the purpose of description, the method 600 is described with the embodiments as illustrated in FIG. 2 and should nowhere be construed as limiting the scope of the present disclosure.
[0089] At step 605, the method 600 includes the step of receiving the request from the user for monitoring the plurality of NFs 125 in the network 105. In particular, the request is at least one of, a Hypertext Transfer Protocol (HTTP) request. In one embodiment, the details pertaining to the plurality of NFs 125 in the network 105 include at least one of, but not limited to, identifier data of each network function, host details and flavor details. In an alternate embodiment, the request from the user is received for at least one of, creating, updating, terminating and deleting details pertaining to the plurality of NFs 125 in the network 105.
[0090] At step 610, the method 600 includes the step of retrieving the details of the plurality of NFs 125 from the IM 245 based on the received request by the retrieving unit 225. In one embodiment, the details pertaining to the plurality of NFs 125 in the network 105 include at least one of, but not limited to, identifier data of each network function, host details and flavor details. The information retrieved by the retrieving unit 225 includes operational and identification details about the one or more NFs. The identifier data of each network function refers to unique identifiers for each network function (e.g., NF ID), which aid in identifying and managing individual network functions. The host details refer to information about where each NF is hosted, such as the server 115, data center, or cloud location. The flavor details include configuration details of the one or more NFs, such as resource allocation (e.g., CPU, memory), service capabilities, or the performance characteristics of the data.
[0091] Upon retrieving the details of the plurality of NFs 125 from the IM 245 based on the received request, the one or more processors 205 communicates with the IM 245 via the communication channel. In an embodiment, the communication channel is an interface between the IM 245 and the CMP 240. In an embodiment, the interface is at least one of, IM_CP interface 305. In one embodiment, the communication channel is the medium through which the communication between the IM 245, the system 120 and the CMP 240 takes place. The communication channel is designed to send packets/requests across an internet and ensure the successful delivery of data and messages over the network 110. In other words, the communication channel is between a source and a destination, such as the IM 245 and the CMP 240 ensures secure data transmission therebetween. The IM 245 interacts with the CMP 240 via the communication channel for enrichment of performance data including at least one of, alarms and counters, is transmitted safely, preventing unauthorized access or data breaches.
[0092] The CMP 240 processes and enhances the received data, performing tasks such as correlating alarms with specific events, analyzing counters, and generating insights that can be used to optimize network performance. The CMP 240 processes and enriches the data, correlating alarms with specific performance issues and using the counter data to provide recommendations for scaling or load balancing.
[0093] At step 615, the method 600 includes the step of updating the one or more NFs along with associated one or more resources based on analysis of an operational state of each of the plurality of network functions 125 by the updating unit 235. The updating unit 235 is responsible for modifying or updating the configuration, software, or one or more resources of the one or more NFs within the network 105, based on the analysis of the current operational state of each of the plurality of NFs 125. In one embodiment, the operational state of each of the plurality of NFs 125 are monitored by the CMP 240. In an embodiment, the operational state is at least one of, an active state or an inactive state. The CMP 240 manages the virtualized resources in the network. When the updating unit 235 determines that the one or more NFs is in the inactive state, the CMP 240 is responsible for terminating the one or more NFs and deallocating the associated resources (such as virtual CPU, memory, storage, etc.).The one or more NFs are terminated along with the associated one or more resources by the CMP 240 if determined the one or more network functions is in the inactive state based on the monitoring.
[0094] In another embodiment, the updating unit 235 is further configured to determine if the one or more new NFs are required to be added to the network 105 based on a scaling policy. The scaling policy is a set of rules and conditions used to determine when and how to adjust the one or more resources allocated to a service, the application, or network function. The scaling policy is to ensure optimal performance, resource utilization, and cost-efficiency by dynamically increasing or decreasing the one or more resources based on the predefined thresholds. The updating unit 235 continuously monitors the one or more NFs and makes decisions about updating, terminating, or removing the one or more NFs based on the network requirements.
[0095] The updating unit 235 also determines whether one or more new NFs are required to meet network demand based on the scaling policy, which is triggered by changes in traffic volume, latency requirements, or service-level agreements (SLAs). In an exemplary embodiment, if the network experiences a surge in traffic, the updating unit 235 determines that additional Session Management Functions (SMFs) or User Plane Functions (UPFs) are needed to handle the traffic load. Based on the scaling policy, new instances of these NFs will be added to the network 105. The one or more new network functions are added in response to determining that that one or more new NFs are required to meet network demand based on the scaling policy. The updating unit 235 is further configured to assign additional one or more resources to the corresponding added one or more new network functions.
[0096] In another aspect of the present invention, a non-transitory computer-readable medium having stored thereon computer-readable instructions that, when executed by a processor 205 is disclosed. The processor 205 is configured to receive a request from a user for monitoring of a plurality of network functions in a network. The processor 205 is configured to retrieve, from an Inventory Manager (IM), details of the plurality of network functions upon receiving the request from the user. The processor 205 is configured to update one or more network functions along with associated one or more resources based on analysis of an operational state of each of the plurality of network functions.
[0097] 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.
[0098] The present disclosure provides technical advancement for efficiently monitoring the information on resources allocated to the plurality of NFs in the network and to track the operational data for all running NFs to avoid request failure. The present invention also discloses a dedicated interface to interact and to notify the CMP during instantiation or termination of any network function. The present interface is configured to perform all required operations at the IM towards the CMP. The present system adds the one or more new NFs based on the scaling policy.
[0099] The present disclosure provides an advantage for proper management of resources by the MANO architecture framework for the plurality of NFs, minimizes error in the work flow, consumes less operation time, identifies inactive or non-working one or more resources in the network, enriches the performance data by providing additional information to the CMP service using the IM_CP interface, sends the VNF/CNF instantiation details accurately, notifies the one or more services about the CNF/VNF termination so that CMP manages and monitors actual resources in use, flexibility to decide whether to scale in/scale out the application on the basis of scaling policies, enables fault tolerance for any event failure, the IM_CP interface works in a high availability mode and if one inventory instance went down during request processing then next available instance will take care of this request, prevents the VNF/CNF instantiation failure due to resource mismatch, includes fault tolerance for any event failure, and also works in a high availability mode to accommodate downtime of an inventory, and ensures time and resource efficient by eliminating multiple backend management.
[00100] 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

[00101] Environment - 100
[00102] Network-105
[00103] User equipment- 110
[00104] Server - 115
[00105] System -120
[00106] Plurality of NFs- 125
[00107] Processor - 205
[00108] Memory - 210
[00109] User interface-215
[00110] Transceiver – 220
[00111] Retrieving unit– 225
[00112] Updating unit- 235
[00113] Capacity manager (CMP)- 240
[00114] Inventory Manager- 245
[00115] Database– 250
[00116] Inventory Manager_Control Plane interface- 305
[00117] MANO Architecture framework- 500
[00118] NFV and SDN design function module– 505
[00119] VNF lifecycle manger - 505a
[00120] VNF catalogue - 505b
[00121] Network service catalogue - 505c
[00122] Network slicing and service chaining manger - 505d
[00123] Physical and virtual resource manager - 505e
[00124] CNF lifecycle manger - 505f
[00125] Platform foundation service module - 510
[00126] Microservice elastic load balancer - 510a
[00127] Identity and access manager - 510b
[00128] Command line interface - 510c
[00129] Central logging manager - 510d
[00130] Event routing manger - 510e
[00131] Platform core service module – 515
[00132] NFV infrastructure monitoring manager - 515a
[00133] Assurance manager - 515b
[00134] Performance manger - 515c
[00135] Policy execution engine - 515d
[00136] Capacity monitoring manager - 515e
[00137] Release management repository - 515f
[00138] Configuration manager and GCT - 515g
[00139] NFV platform decision analytics unit- 515h
[00140] Platform NoSQL DB - 515i
[00141] Platform scheduler and cron Jobs module - 515j
[00142] VNF backup & upgrade manager - 515k
[00143] Micro service auditor - 515l
[00144] Platform operation, administration and maintenance manager - 515m
[00145] Platform resource adapter and utilities module – 520
[00146] Platform External API adaptor and gateway - 520a
[00147] Generic decoder and indexer - 520b
[00148] Swarm adaptor - 520c
[00149] OpenStack API adaptor - 520d
[00150] NFV gateway - 520e
,CLAIMS:CLAIMS
We Claim:
1. A method (600) to manage one or more network functions, the method (600) comprising the steps of:
receiving, by one or more processors (205), a request from a user for monitoring of a plurality of network functions (125) in a network (105);
retrieving, by the one or more processors (205), from an Inventory Manager (IM) (245), details of the plurality of network functions (125) upon receiving the request from the user; and
updating, by the one or more processors (205), one or more network functions along with associated one or more resources based on analysis of an operational state of each of the plurality of network functions (125).

2. The method (600) as claimed in claim 1, wherein the details of the plurality of network functions (125) include at least one of, identifier data of each network function, host details and flavor details.

3. The method (600) as claimed in claim 1, wherein the step of, updating, one or more network functions along with associated one or more resources based on analysis of an operational state of each of the plurality of network functions (125), includes the steps of:
monitoring, by the one or more processors (205), via a Capacity Manager (CMP) (240), the operational state of each of the plurality of network functions (125), wherein the operational state is at least one of, an active state or an inactive state;
if determined the one or more network functions is in the inactive state based on the monitoring, terminating, by the one or more processors (205), via the CMP (240), the one or more network functions along with the associated one or more resources;
determining, by the one or more processors (205), if the one or more new network functions are required to be added to the network based on a scaling policy;
adding, by the one or more processors (205), the one or more new networks functions in response to determining that the one or more new network functions are required to be added to the network (105); and
assigning, by the one or more processors (205), additional one or more resources corresponding to the added one or more new network functions.

4. The method (600) as claimed in claim 1, wherein the one or more processors (205) communicates with the IM (245) via a communication channel.

5. The method (600) as claimed in claim 4, wherein the communication channel is an interface between the IM (245) and the CMP (240).

6. The method (600) as claimed in claim 5, wherein the interface is at least one of, an Inventory Manager_ Control Plane (IM_CP) interface (305).

7. The method (600) as claimed in claim 5, wherein a scaling is initiated by transmitting a task creation event to the CMP (240) via the interface, wherein on detection of a breach, the interface waits for a response from the CMP (240), wherein the response corresponds to the breached response.

8. The method (600) as claimed in claim 5, wherein the IM (245) interacts with the CMP (240) via the communication channel for enrichment of performance data including at least one of, alarms and counters.

9. A system (120) to manage one or more network functions, the system (120) comprising:
a transceiver (220), configured to, receive, a request from a user for monitoring of a plurality of network functions (125) in a network (105);
a retrieving unit (225), configured to, retrieve, from an Inventory Manager (IM) (245), details of the plurality of network functions (125) upon receiving the request from the user; and
an updating unit (235), configured to, update, one or more network functions along with associated one or more resources based on analysis of an operational state of each of the plurality of network functions (125).

10. The system (120) as claimed in claim 9, wherein the details of the plurality of network functions include at least one of, identifier data of each network function, host details and flavor details.

11. The system (120) as claimed in claim 9, wherein the updating unit (235), updates, one or more network functions along with associated one or more resources based on analysis of an operational state of each of the plurality of network functions (125), by:
monitor, by a Capacity Manager (CMP) (240), the operational state of each of the plurality of network functions (125), wherein the operational state is at least one of, an active state or an inactive state;
if determined the one or more network functions is in the inactive state based on the monitoring, terminate, via the CMP (240), the one or more network functions along with the associated one or more resources;
determine, if the one or more new network functions are required to be added to the network based on a scaling policy;
add, by the one or more processors (205), the one or more new networks functions in response to determining that the one or more new network functions are required to be added to the network (105); and
assign, by the one or more processors (205), additional one or more resources corresponding to the added one or more new network functions.
.

12. The system (120) as claimed in claim 9, wherein the one or more processors (205) communicates with the IM (245) via a communication channel.

13. The system (120) as claimed in claim 12, wherein the communication channel is an interface between the IM (245) and the CMP (240).

14. The system (120) as claimed in claim 13, wherein the interface is at least one of, an Inventory Manager_ Control Plane (IM_CP) interface (305).

15. The system (120) as claimed in claim 13, wherein the interface initiates a scaling by transmitting a task creation event to the CMP (240), wherein on detection of a breach, wherein the interface waits for a response from the CMP (240), wherein the response corresponds to the breached response.

16. The system (120) as claimed in claim 12, wherein the IM (245) interacts with the CMP (240) via the communication channel for enrichment of performance data including at least one of, alarms and counters.