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 FOR INSTANTIATION OF NETWORK FUNCTION COMPONENTS IN A PREDEFINED ORDER
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 network function components and more particularly relates to a method and a system for instantiation of the network function components in a predefined order.
BACKGROUND OF THE INVENTION
[0002] In a network environment, for a call made through a mobile phone, multiple interfaces exist (including HLR interface, etc.). In telecom cloud, multiple interfaces (acting as CNFC) are related to one containerized network function (CNF). Further, there is a chain between the interfaces, such that different interfaces depend on different another interface. In the deployment of the CNF, there is no defined order to deploy them on other systems. In the case of multiple CNFCs, all the multiple CNFCs have to be executed separately, one by one. As such, each system is dependent on another system. Whenever a system tries to communicate with a system which is not instantiated, there are multiple error logs or multiple retry logic. In other words, the CNFCs have to be run independently. Further, care has to be taken as to which CNFC will instantiate first and which will instantiate last. Further, it has to be ensured that the application will not be exposed to the user until all the dependent CNFCs are in running state. Connection re-try logic occurs, if dependent CNFCs are not in running state. This leads to excessive processing time and network failures.
[0003] Therefore, there is a need for a solution for instantiation of CNFCs based on a predefined order.
SUMMARY OF THE INVENTION
[0004] One or more embodiments of the present disclosure provide a method and system for instantiation of network function components in a predefined order.
[0005] In one aspect of the present invention, the system for instantiation of the network function components in the predefined order is disclosed. The system includes a receiving unit configured to receive a request transmitted by a network function-lifecycle manager to instantiate a Cloud Native Function (CNF) comprising multiple network function components. The system further includes a sorting unit, configured to sort the multiple network function components in the predefined order based on the received request. The system further includes an instantiating unit, configured to instantiate, the sorted multiple network function components in container host. The system further includes a transmitting unit, configured to transmit, an instantiation response to the network function lifecycle manager based on instantiating the multiple network function components. The system further includes an updating unit, configured to update, an Inventory Manager (IM) based on transmitting an inventory update request from the network function-lifecycle manager to the IM.
[0006] In an embodiment, the request includes a predefined order of instantiation.
[0007] In an embodiment, the predefined order is set by at least one of a network operator.
[0008] In an embodiment, the predefined order facilitates execution of the multiple network function components automatically in the defined order.
[0009] In an embodiment, upon instantiating the sorted multiple network function components in the predefined order, the information related to that instantiation and associated one or more resources are stored in a database.
[0010] In an embodiment, the CNF is in a running state until each of the multiple network function components are instantiated by the one or more processors in the predefined order.
[0011] In an embodiment, updating the IM includes at least one of, add or release one or more resources which are currently utilized in response to instantiation of each of the multiple network function components.
[0012] In an embodiment, the network function-lifecycle manager communicates with the IM via a communication channel.
[0013] In an embodiment, the communication channel is an interface, wherein the interface is at least one of, a CNFLM _container orchestrator (CM_DS) interface to transmit an inventory update request between the network function-lifecycle manager and the IM.
[0014] In an embodiment, the inventory update request transmitted from the network function-lifecycle manager to the IM pertains to updating one or more resources subsequent to instantiating the sorted multiple network function components in the predefined order.
[0015] In another aspect of the present invention, the method for instantiation of the network function components in the predefined order is disclosed. The method includes the step of receiving a request transmitted by a network function-lifecycle manager to instantiate a Cloud Native Function (CNF) comprising multiple network function components. The method further includes the step of sorting the multiple network function components in the predefined order based on the received request. The method further includes the step of instantiating the sorted multiple network function components in a container host. The method further includes the step of transmitting an instantiation response to the network function lifecycle manager based on instantiating the multiple network function components. The method further includes the step of updating an Inventory Manager (IM) based on transmitting an inventory update request from the network function-lifecycle manager to the IM.
[0016] 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 request transmitted by a network function-lifecycle manager to instantiate a Cloud Native Function (CNF) comprising multiple network function components. The processor is configured to sort the multiple network function components in the predefined order based on the received request. The processor is configured to instantiate the sorted multiple network function components in the container host. The processor is configured to transmit an instantiation response to the network function lifecycle manager based on instantiating the multiple network function components. The processor is configured to update an Inventory Manager (IM) based on transmitting an inventory update request from the network function-lifecycle manager to the IM.
[0017] 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
[0018] 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.
[0019] FIG. 1 is an exemplary block diagram of an environment for instantiation of network function components in a predefined order, according to one or more embodiments of the present invention;
[0020] FIG. 2 is an exemplary block diagram of a system for instantiation of the network function components in the predefined order, according to one or more embodiments of the present invention;
[0021] FIG. 3 is an exemplary block diagram of an architecture implemented in the system of the FIG. 2, according to one or more embodiments of the present invention;
[0022] FIG. 4 is a signal flow diagram for instantiation of the network function components in the predefined order, according to one or more embodiments of the present invention;
[0023] FIG. 5 is a schematic representation of a method for instantiation of the network function components in the predefined order, according to one or more embodiments of the present invention; and
[0024] FIG. 6 illustrates an architecture framework (e.g., MANO architecture framework), in which the present invention can be implemented, in accordance with one or more embodiments of the present invention.
[0025] The foregoing shall be more apparent from the following detailed description of the invention.
DETAILED DESCRIPTION OF THE INVENTION
[0026] 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.
[0027] 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.
[0028] 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.
[0029] The present invention relates to instantiation of a Cloud Native Function (CNF) in a predefined order. The CNF includes multiple Container Network Function Components (CNFCs). Once the execution is triggered, all of the multiple CNFCs are executed automatically in the defined order. As such, the entire system is deployed as a single CNF on a site (for example, by the Docker Swarm Adapter (DSA)).
[0030] FIG. 1 illustrates an exemplary block diagram of an environment 100 for instantiation of network function components 226 (as shown in FIG.2) in a predefined order, according to one or more embodiments of the present disclosure. In this regard, the environment 100 includes a User Equipment (UE) 102, a server 104, the network 106 and a system 108 communicably coupled to each other for instantiation of the network function components in the predefined order.
[0031] In an embodiment, instantiation refers to the process of creating a specific instance of network functions. The instantiation of network function components refers to the process of creating and launching necessary components (like software functions, containers, or virtual machines) that make up a network function. The network functions are specific functions performed within the network 106, such as routing, firewalling, load balancing etc. The container is a lightweight, standalone, and executable software package that includes everything needed to run a piece of software, such as the code, runtime, system tools, libraries, and settings. In an embodiment the network function is at least one of Cloud Native Function (CNF) refers to the network function that is specifically designed and deployed using cloud-native principles. The cloud-native principles refer to a set of architectural and operational guidelines that govern how applications are built, deployed, and managed in modern cloud environments. In another embodiment, the network function is at least one of Container Network Function (CNF) refers to the network function that is deployed and operated within a containerized environment. The CNF is typically composed of multiple Container Network Function Components (CNFCs). In an embodiment the network function components 226 are at least one of, Container Network Function Components (CNFC). The CNFC refers to a network function that has been containerized for deployment in a cloud-native environment. The CNFCs include, but are not limited to, Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Network Repository Function (NRF) etc. The cloud-native environment refers to an infrastructure and set of practices designed to fully leverage cloud computing models for building, deploying, and operating applications.
[0032] In an embodiment, the predefined order refers to a sequence or arrangement that has been determined or established in advance, prior to execution. The predefined order is set by at least one of network operator. The predefined order specifies the exact way in which tasks, actions, or processes should occur, ensuring they are executed in a particular sequence. In particular, the predefined order for the instantiation of the network function components 226 refers to a sequence in which the network function components 226 are set up and activated before the process begins. For example, if the network function requires that a first component be active before a second component is started, the predefined order would ensure that the first component is instantiated before the second component.
[0033] As per the illustrated embodiment and for the purpose of description and illustration, the UE 102 includes, but not limited to, a first UE 102a, a second UE 102b, and a third UE 102c, and should nowhere be construed as limiting the scope of the present disclosure. In alternate embodiments, the UE 102 may include a plurality of UEs as per the requirement. For ease of reference, each of the first UE 102a, the second UE 102b, and the third UE 102c, will hereinafter be collectively and individually referred to as the “User Equipment (UE) 102”.
[0034] In an embodiment, the UE 102 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.
[0035] The environment 100 includes the server 104 accessible via the network 106. The server 104 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.
[0036] The network 106 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 106 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.
[0037] The network 106 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 106 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.
[0038] The environment 100 further includes the system 108 communicably coupled to the server 104 and the UE 102 via the network 106. The system 108 is configured to instantiate the network function components 226 in a predefined order. As per one or more embodiments, the system 108 is adapted to be embedded within the server 104 or embedded as an individual entity.
[0039] Operational and construction features of the system 108 will be explained in detail with respect to the following figures.
[0040] FIG. 2 is an exemplary block diagram of the system 108 for instantiation of the network function components 226 in the predefined order, according to one or more embodiments of the present invention.
[0041] As per the illustrated embodiment, the system 108 includes one or more processors 202, a memory 204, a user interface 206, and a database 208. In an embodiment, the network function component 226, a network function lifecycle manager 220, an Inventory Manager (IM) 222 and a container host 224 is communicably coupled with the system 108.
[0042] For the purpose of description and explanation, the description will be explained with respect to one processor 202 and should nowhere be construed as limiting the scope of the present disclosure. In alternate embodiments, the system 108 may include more than one processor 202 as per the requirement of the network 106. The one or more processors 202, hereinafter referred to as the processor 202 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.
[0043] As per the illustrated embodiment, the processor 202 is configured to fetch and execute computer-readable instructions stored in the memory 204. The memory 204 may be configured to store one or more computer-readable instructions or routines in a non-transitory computer-readable storage medium, which may be fetched and executed to create or share data packets over a network service. The memory 204 may include any non-transitory storage device including, for example, volatile memory such as RAM, or non-volatile memory such as disk memory, EPROMs, FLASH memory, unalterable memory, and the like.
[0044] In an embodiment, the user interface 206 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 206 facilitates communication of the system 108. In one embodiment, the user interface 206 provides a communication pathway for one or more components of the system 108. Examples of such components include, but are not limited to, the UE 102 and the database 208.
[0045] The database 208 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 208 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.
[0046] The network function lifecycle manager 220 is a component within a network management and orchestration framework that is responsible for overseeing the entire lifecycle of the network functions. The network function lifecycle manager 220 includes the creation, configuration, scaling, updating, monitoring, and eventual termination of the network functions. The network function lifecycle manager 220 is at least one of, but not limited to, a Containerized Function Lifecycle Manager (CNFLM). The CNFLM is a specialized component within a network management and orchestration framework designed specifically to manage the lifecycle of containerized network functions (CNFs). The CNFs are network functions that run in lightweight, isolated environments known as containers, which are often orchestrated by platforms like Kubernetes or docker swarm. The network function lifecycle manager 220 is connected to the IM 222 via an interface.
[0047] The IM 222 is a component responsible for tracking, managing, and updating information related to the resources and assets used within the network 106. The IM 222 keeps an up-to-date record of all the network functions, their components, and associated resources. The IM 222 is at least one of a Physical and Virtual Inventory Manager (PVIM). The PVIM is a tool within network management that is responsible for maintaining and managing an up-to-date inventory of both physical and virtual resources within the network 106.
[0048] In order for the system 108 to instantiate the network function components 226 in the predefined order, the processor 202 includes one or more modules. In one embodiment, the one or more modules includes, but not limited to, a receiving unit 210, a sorting unit 212, an instantiating unit 214, a transmitting unit 216, and an updating unit 218 communicably coupled to each other for instantiation of the network function components 226 in the predefined order.
[0049] In one embodiment, the one or more modules includes, but not limited to, the receiving unit 210, the sorting unit 212, the instantiating unit 214, the transmitting unit 216, and the updating unit 218. In one embodiment, each of the receiving unit 210, the sorting unit 212, the instantiating unit 214, the transmitting unit 216, and the updating unit 218 may be used in combination or interchangeably for instantiation of the network function components 226 in the predefined order.
[0050] The receiving unit 210, the sorting unit 212, the instantiating unit 214, the transmitting unit 216, and the updating unit 218 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 202. 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 202 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 204 may store instructions that, when executed by the processing resource, implement the processor. In such examples, the system 108 may comprise the memory 204 storing the instructions and the processing resource to execute the instructions, or the memory 204 may be separate but accessible to the system 108 and the processing resource. In other examples, the processor 202 may be implemented by electronic circuitry.
[0051] In one embodiment, the receiving unit 210 is configured to receive a request by the network function lifecycle manager 220. The request received from the network function lifecycle manager 220 is to instantiate the CNF. Instantiating of the CNF refers to creating and launching an instance of the CNF. The instance refers to deployment or occurrence of the CNF with the network 106. The CNF includes multiple network function components 226. The multiple network function components 226 refer to individual elements or modules that together make up the CNF. Each of the network function components 226 may represent a specific function or part of the overall network service, such as handling data traffic, managing sessions, or providing security features. The request includes the predefined order of instantiation. The predefined order of instantiation refers to a pre-determined sequence in which the multiple network function components 226 of the CNF are created, configured, and activated during the instantiation process.
[0052] In an embodiment, the predefined order includes specific details and instructions that define how and in what sequence the various network function components 226 of the should be created and deployed. In particular, the predefined order includes, but not limited to, component sequence, dependencies, configuration parameters, resource allocation, timing and synchronization, error handling and rollback, operational procedures. The component sequence specifies the exact sequence in which each network function component should be instantiated. For example, component A must be instantiated before component B, and component B before component C. The dependencies include the details of dependencies between the network function components 226. For example, if component B relies on the successful initialization of component A, the predefined order ensures component A is fully operational before component B is instantiated. The configuration parameters are settings or values that define how each network function component should operate within the network 106. The configuration parameters include, but are not limited to, function specific configurations, service parameters such as performance thresholds, service level agreements (SLAs) etc., Central Processing Unit (CPU) and memory limits, storage requirements etc. The resource allocation defines how resources such as CPU, memory and storage should be allocated to each network function component in the predefined order. The timing and synchronization include timing constraints or synchronization requirements to ensure network function components 226 are instantiated at the right time. For example, component A should be fully initialized before component B starts. The error handling and rollback provides guidelines for handling errors or issues that arise during instantiation and rollback includes procedures if a component fails to instantiate correctly. The operational procedures outline any specific operational steps or procedure required during the instantiation process. For example, the operational procedure includes checks or validations that need to be performed after each component is instantiated.
[0053] In an embodiment, the predefined order is set by at least one of a network operator. The network operator is an organization or entity responsible for managing and maintaining the infrastructure, services, and operations of a telecommunications network. The network operator is at least one of, telecom service providers, Internet Service Providers (ISPs), Managed Service Providers (MSPs). The predefined order facilitates execution of the multiple network function components 226 automatically in the defined order. More specifically the predefined sequence specifies how the multiple network function components 226 should be instantiated and activated in a specific, orderly manner. The predefined order helps to automate the deployment process, ensuring that each network function component is initialized in the correct sequence to maintain proper functionality and dependencies.
[0054] Upon receiving the request from the network function lifecycle manager 220, the sorting unit 212 is configured to sort the multiple network function components 226 in the predefined order. In particular, the sorting unit 212 parses or interprets the predefined order included in the request. The predefined order is usually specified in the form of a list or sequence that defines the exact arrangement in which the components should be processed. The sorting unit 212 applies an algorithm or method to arrange the multiple network function components 226 in the predefined order. The algorithm or method includes, but is not limited to, sequence numbering and priority-based sorting.
[0055] Upon sorting the multiple network function components 226 in the predefined order, the instantiating unit 214 is configured to instantiate the sorted multiple network function components 226 in the container host 224. The container host 224 refers to the physical or virtual machine environment where containerized network function components (CNFCs) are deployed, executed, and managed. In an embodiment, the container host 224 is at least one of a docker host. In an embodiment, each of the multiple network function components 226 is instantiated as a container on the container host 224, utilizing the host's resources and runtime environment. The container host 224 ensures that each of the multiple network function components 226 are isolated, secure, and able to communicate as needed to perform their network functions.
[0056] The instantiation of the sorted multiple network function components 226 refers to the process of deploying and initializing these components in a containerized environment based on the predefined order. The instantiating unit 214 instantiates the sorted multiple network function components 226 in a container host by receiving the sorted list of multiple network function components 226 from the sorting unit 212. The sorted list is arranged according to the predefined order specified in the request from the network function lifecycle manager 220. Thereafter, the instantiating unit 214 allocates the necessary resources within the container host to support each network function component. The resources include CPU, memory, storage, and network interfaces. The resources are provisioned based on the requirements of each network function component as defined in the predefined order.
[0057] Subsequently, the instantiating unit 214 instantiates the sorted multiple network functions by pulling a container image, starting the container, and configuring the multiple network function components 226. The pulling of the container image includes retrieving the appropriate container image from a registry or repository for each network function component. The container image is a lightweight, standalone, and executable package that includes everything needed to run a piece of software such as code, runtime, libraries, environment variables, and configuration files. The registry or repository is a storage and distribution system where container images are stored, managed, and retrieved. Upon pulling the appropriate container image for each network function component, the instantiating unit 214 starts the container, which involves loading the image, initializing the runtime environment, and launching the each of the multiple network component. Once the container is running, the instantiating unit 214 applies any necessary configuration settings, such as environment variables, network settings, and resource limits to the container. As each of the multiple network components is instantiated, the instantiating unit 214 ensures that any dependencies between each of the multiple network components are executed. For example, if the component B depends on the component A being fully operational, the instantiating unit 214 may perform health checks on the component A before proceeding to instantiate the component B. In an embodiment, the CNF is in a running state until each of the multiple network function components 226 are instantiated in the predefined order. In particular, the CNF, which consists of multiple network function components 226, remains active or operational during the process of instantiating each of the multiple network function components 226.
[0058] In an embodiment, upon instantiating the sorted multiple network function components 226 in the predefined order, the information related to that instantiation and associated one or more resources are stored in the database 208. The one or more resources refers to the various computing and networking assets or capabilities that are allocated, utilized, or affected during the instantiation of the multiple network function components 226 in the container host 224. The one or more resources includes, but not limited to computing resources, network resources, virtualization resources, service resources, infrastructure resources. The computing resources include, but are not limited to CPU, memory, storage. The network resources include, but are not limited to, Internet Protocol (IP) addresses, bandwidth, network interfaces. The virtualization resources include, but are not limited to virtual machines, containers. The service resources include, but are not limited to, dependencies and configuration parameters.
[0059] Upon instantiating the sorted multiple network function components 226 in the container host 224, the transmitting unit 216 is configured to transmit an instantiation response. The instantiation response is transmitted to the network function lifecycle manager 220. Upon successful instantiation of the multiple network functions, the instantiation response is transmitted to the network function lifecycle manager 220. The instantiation response includes a confirmation or acknowledgment that each of the multiple network function components 226 has been successfully instantiated and is now running in the container host. In an embodiment, the instantiation response also includes status information of each instantiated component. The status information includes, but is not limited to component state, resource allocation, operational metrics.
[0060] Upon receiving the instantiation response, the network function lifecycle manager 220 transmits an inventory update request to the IM 222. The inventory update request pertains to updating one or more resources subsequent to instantiating the sorted multiple network function components 226 in the predefined order. The inventory update request is transmitted from the network function lifecycle manager 220 to the IM 222 via an interface. The interface is at least one of a CNFLM _container orchestrator (CM_DS) interface. The interface refers to the communication channel or protocol that facilitates the exchange of data between the network function lifecycle manager 220 and the IM 222. In an embodiment, the CM_DS interface aids in the exchange of data between the network function lifecycle manager 220 and the container orchestrator 302. The CM_DS interface ensures that information regarding the instantiation of multiple network function components 226 and the subsequent resource updates is accurately transmitted and processed. The CM_DS interface refers to a specific type of interface or protocol used for communication between the network function lifecycle manager 220 and the IM 222.
[0061] In an embodiment, the inventory update request is a communication or command sent by the network function lifecycle manager 220 to the IM 222 after the successful instantiation of the multiple network function components 226. The inventory update request is aimed at updating the inventory records in the IM 222 to reflect the current state of the network resources and multiple network function components 226. The inventory update request serves to synchronize the IM 222 with the latest status of network resources that were allocated or modified during the instantiation of the multiple network function components 226. The inventory update request includes, but not limited to, resource allocation, component details, operational state, release of resources.
[0062] Based on transmitting an inventory update request from the network function-lifecycle manager 220 to the IM 222, the updating unit 218 is configured to update the IM 222. The updating the IM 222 includes at least one of, add or release one or more resources which are currently utilized in response to instantiation of each of the multiple network function components 226.
[0063] Therefore, by sorting and instantiating the multiple network function components 226 in the predefined order, the system 108 ensures that dependencies and execution requirements are met, leading to a more reliable and consistent deployment process. Further, the system 108 enables the automated execution of the multiple network function components 226 in the predefined order, reducing manual intervention and minimizing the risk of human error. Further, the system 108 enhances the reliability, scalability, and manageability of network functions in modern containerized environments.
[0064] FIG. 3 is an exemplary block diagram of an architecture 300 of the system 108 for instantiation of the network function components 226 in the predefined order, according to one or more embodiments of the present invention.
[0065] The architecture 300 includes the user interface 206, the network function lifecycle manager 220, a container orchestrator 302, an infrastructure 304, and the database 208.
[0066] In an embodiment, the container orchestrator 302 is a system or software platform designed to manage the deployment, scaling, networking, and lifecycle of containers in a distributed computing environment. In an embodiment, the infrastructure 304 represents the underlying physical or virtual resources where the containers and network functions are deployed. The infrastructure 304 include servers, virtual machines, storage, and networking resources.
[0067] In an embodiment, the network function lifecycle manager 220 receives the request to instantiate the network function components 226 from the user interface 206. The network function components 226 include multiple network function components 226. The request includes the predefined order of instantiation. The predefined order is set by at least one of the network operators by the user interface 206. The predefined order facilitates execution of the multiple network function components 226 automatically in the defined order.
[0068] Upon receiving the request, the network function lifecycle manager 220 transmits the request received from the user interface 206 to the container orchestrator 302. In an embodiment, the CM_DS interface is established between the network function lifecycle manager 220 and the container orchestrator 302 for communication. Subsequently, the container orchestrator 302 sort the multiple network function components 226 in the predefined order based on the received request. Upon sorting the multiple network function components 226, the container orchestrator 302 instantiates the sorted multiple network function components 226 in the container host. In an embodiment, the container orchestrator 302 instantiates the sorted multiple network function components 226 in the infrastructure 304. In an embodiment, the CNF is in a running state until each of the multiple network function components 226 are instantiated in the predefined order.
[0069] Based on instantiating the multiple network function components 226, the container orchestrator 302 transmits the instantiation response to the network function lifecycle manager 220. The instantiation response includes a confirmation or acknowledgment that each of the multiple network function components 226 has been successfully instantiated and is now running in the container host.
[0070] In an embodiment, upon instantiating the sorted multiple network function components 226 in the predefined order, the information related to that instantiation and associated one or more resources are stored in the database 208.
[0071] Upon receiving the instantiation response from the container orchestrator 302, the network function lifecycle manager 220 transmits an inventory update request to the IM 222. The inventory update request transmitted from the network function-lifecycle manager 220 to the IM 222 pertains to updating one or more resources subsequent to instantiating the sorted multiple network function components 226 in the predefined order.
[0072] Based on transmitting the inventory update request from the network function-lifecycle manager to the IM 222, the container orchestrator 302 updates the IM 222. In an embodiment, the container orchestrator 302 updates the database 208. The updating of the IM 222 includes at least one of, add or release one or more resources which are currently utilized in response to instantiation of each of the multiple network function components 226.
[0073] FIG. 4 is a signal flow diagram for instantiation of the network function components 226 in the predefined order, according to one or more embodiments of the present invention.
[0074] At step 402, the network function-lifecycle manager 220 transmits the request to the container orchestrator 302. The request is to instantiate the CNF. The CNF includes multiple network functions components. The request includes the predefined order of instantiation. The predefined order is set by at least one of the network operators. The predefined order facilitates execution of the multiple network function components 226 automatically in the defined order.
[0075] At step 404, upon receiving the request, the container orchestrator 302 sort the multiple network function components 226 in the predefined order based on the received request. In an embodiment, the CM_DS interface is established between the network function lifecycle manager 220 and the container orchestrator 302 for communication. Upon sorting the multiple network function components 226 in the predefined order, the container orchestrator instantiates the sorted multiple network function components 226 in the container host. The multiple network function components 226 are instantiated at the container host. Thereafter, the container host acknowledges the instantiating of the multiple network function components 226 in the predefined order. In an embodiment, upon instantiating the sorted multiple network function components 226 in the predefined order, the information related to that instantiation and associated one or more resources are stored in the database 208.
[0076] At step 406, upon receiving the acknowledgement of instantiating of the multiple network function components 226 in the predefined order, the container orchestrator 302 transmits the instantiation response to the network function lifecycle manager 220. The instantiation response includes a confirmation or acknowledgment that each of the multiple network function components 226 has been successfully instantiated and is now running in the container host 224.
[0077] At step 408, upon receiving the instantiation response from the container orchestrator 302, the network function lifecycle manager 220 transmits the inventory update request to the IM 222. The updating of the IM 222 includes at least one of, add or release one or more resources which are currently utilized in response to instantiation of each of the multiple network function components 226. In an embodiment, upon updating the IM 222, transmit the acknowledgement to the network function lifecycle manager 220. The acknowledgement pertains to the successful updating of the IM 222.
[0078] FIG. 5 is a flow diagram of a method 500 for instantiation of the network function components 226 in the predefined order, 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.
[0079] At step 502, the method 500 includes the step of receiving the request transmitted by the network function-lifecycle manager 220 to instantiate the CNF by the receiving unit 210. The CNF includes multiple network function components 226. The request includes the predefined order of instantiation. The predefined order is set by at least one of the network operators. The predefined order facilitates execution of the multiple network function components 226 automatically in the defined order.
[0080] At step 504, the method 500 includes the step of sorting the multiple network function components 226 in the predefined order based on the received request by the sorting unit 212.
[0081] At step 506, the method 500 includes the step of instantiating the sorted multiple network function components 226 in the container host 224 by the instantiating unit 214. Upon instantiating the sorted multiple network function components 226 in the predefined order, the information related to that instantiation and associated one or more resources are stored in the database 208. In an embodiment, the CNF is in a running state until each of the multiple network function components 226 are instantiated in the predefined order.
[0082] At step 508, the method 500 includes the step of transmitting the instantiation response to the network function lifecycle manager 220 based on instantiating the multiple network function components 226 by the transmitting unit 216.
[0083] At step 510, the method 500 includes the step of updating the IM 222 by the updating unit 218 based on transmitting an inventory update request from the network function-lifecycle manager to the IM 222. In an embodiment, the network function-lifecycle manager transmits the inventory update request to the IM 222 via the CM_DS interface. The updating of the IM 222 includes at least one of, add or release one or more resources which are currently utilized in response to instantiation of each of the multiple network function components 226.
[0084] FIG. 6 illustrates an architecture framework 600 (e.g., MANO architecture framework), in which the present invention can be implemented, in accordance with one or more embodiments of the present invention. The system architecture 600 includes the user interface 206, a Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) design function module 602, a platform foundation service module 604, a platform core service module 606, and a platform resource adapter and utilities module 608.
[0085] The NFV and SDN design function module 602 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 604 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 604 provides the essential capabilities and resources required for the CNF environment to function effectively.
[0086] The platform core service module 606 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 608 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 608 plays a crucial role in integrating CNFs with underlying infrastructure and services, providing the necessary support for efficient operation, resource utilization, and interoperability.
[0087] The NFV and SDN design function module 602 includes a Virtual Network Function (VNF) lifecycle manager 602a, a VNF catalog 602b, a network service catalog 602c, a network slicing and service chaining manager 602d, a physical and virtual resource manager 602e, and a CNF lifecycle manager 602f.
[0088] The VNF lifecycle manager 602a is responsible for managing the entire lifecycle of VNFs. The VNF lifecycle manager 602a ensures that VNFs or CNFs are deployed, configured, monitored, scaled, and eventually decommissioned effectively. The VNF catalog 602b (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 602b 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 602c 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 602c serves as a central resource for defining, deploying, and managing these services within a containerized network environment.
[0089] The network slicing and service chaining manager 602d is a crucial component responsible for orchestrating and managing network slicing and service chaining functionalities. The network slicing and service chaining 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 602e 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 602e ensures that the necessary resources are allocated efficiently and effectively to meet the performance, availability, and scalability requirements of containerized network functions.
[0090] Further, the CNF lifecycle manager 602f 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 602f ensures that the CNFs are efficiently deployed, monitored, scaled, updated, and removed, facilitating the smooth operation of network services in a containerized environment.
[0091] The platform foundation service module 604 includes a microservice elastic load balancer 604a, an identity and access manager 604b, a command line interface 604c, a central logging manager 604d and an event routing manager 604e.
[0092] The microservice elastic load balancer 604a is a specific type of load balancer designed to dynamically distribute network traffic across a set of microservices running in a containerized environment. The primary purpose of the microservice elastic load balancer 604a 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 604b is a critical component responsible for managing and securing access to containerized network functions and their resources. The identity and access manager 604b 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.
[0093] The central logging manager 604d is a component responsible for aggregating, managing, and analyzing log data from various containerized network functions and associated infrastructure components. The central logging manager 604d 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 604e is a component responsible for handling the distribution and routing of events and notifications generated by various parts of the CNF environment. The event routing manager 604e includes events related to system status, performance metrics, errors, and other operational or application-level events. The event routing manager 604e 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.
[0094] The platform core service module 606 includes an NFV infrastructure monitoring manager 606a, an assurance manager 606b, a performance manager 606c, a policy execution engine 606d, a capacity monitoring manager 606e, a release management repository 606f, a configuration manager and GCT 606g, a NFV platform decision analytics unit 606h, a platform NoSQL DB 606i, a platform scheduler and Cron Jobs module 606j, a VNF backup & upgrade manager 606k, a micro service auditor 606l, and a platform operation, and administration and maintenance manager 606m.
[0095] The NFV infrastructure monitoring manager 606a monitors the underlying infrastructure of NFV environments, including computing, storage, and network resources. The NFV infrastructure monitoring manager 606a provides real-time visibility into resource health, performance, and utilization. Further, the NFV infrastructure monitoring manager 606a detects and alerts infrastructure issues. Further, the NFV infrastructure monitoring manager 606a integrates with monitoring tools to ensure reliable operation of CNFs.
[0096] The assurance manager 606b manages the quality and reliability of network services by ensuring compliance with service level agreements (SLAs) and operational standards. The performance manager 606c optimizes the performance of CNFs by tracking and analyzing key performance indicators (KPIs). The policy execution engine 606d enforces and applies policies within the CNF environment to manage operations and access. Further, the policy execution engine 606d executes policies related to security, resource allocation, and service quality. Further, the policy execution engine 606d executes policies, translates policy rules into actionable configurations and enforces compliance across CNFs.
[0097] The capacity monitoring manager 606e monitors and manages the capacity of resources within the CNF environment to ensure optimal usage and avoid resource shortages. The release management repository 606f stores and manages software releases, configurations, and versions of CNFs. Further, the release management repository 606f keeps track of different versions of CNFs.
[0098] The configuration manager and Generic Configuration Tool (GCT) 606g manages the configuration of CNFs and related infrastructure components. The NFV platform decision analytics unit 606h analyzes data from a NFV platform to support decision-making and strategic planning.
[0099] The platform NoSQL database (DB) 606i 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 606j manage scheduled tasks and periodic operations within the CNF environment. The VNF backup & upgrade manager 606k oversees the backup and upgrade processes for VNFs within the CNF environment.
[00100] The micro service auditor 606l monitors and audits microservices to ensure compliance with operational and security standards. The platform operation, administration and maintenance manager 606m manages the overall operation, administration, and maintenance of the CNF platform.
[00101] The platform resource adapter and utilities module 608 includes a platform external API adaptor and gateway 608a, a generic decoder and indexer 608b, a swarm adaptor 608c, an OpenStack API adaptor 608d and a NFV gateway 608e.
[00102] The platform external API adaptor and gateway 608a facilitates communication between the CNF platform and external systems or services by providing an interface for API interactions. The generic decoder and indexer 608b decode and indexes various types of data and logs within the CNF environment. The swarm adaptor 608c facilitates communication between a swarm cluster and the CNF environment, including container deployment, scaling, and management.
[00103] The OpenStack API adaptor 608d 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 608e manages and facilitates communication between NFV (Network Functions Virtualization) components and external networks or services.
[00104] The interface CM_DS is the interface between the CNF lifecycle manager 602f and the swarm adaptor 608c for communication. The CM_DS interface ensures that information regarding the instantiation of multiple network function components 226 and the subsequent resource updates is accurately transmitted and processed
[00105] 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 202. The processor 202 is configured to receive the request transmitted by the network function-lifecycle manager 220 to instantiate the CNF. The CNF includes multiple network function components 226. The processor 202 is further configured to sort the multiple network function components 226 in the predefined order based on the received request. The processor 202 is further configured to instantiate the sorted multiple network function components 226 in the container host. The processor 202 is further configured to transmit the instantiation response to the network function lifecycle manager 220 based on instantiating the multiple network function components 226. The processor 202 is further configured to update the IM based on transmitting the inventory update request from the network function-lifecycle manager 220 to the IM 222.
[00106] 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.
[00107] The present disclosure incorporates technical advancement of enabling the automated execution of the multiple network function components in the predefined order, reducing manual intervention and minimizing the risk of human error. The automation enhances operational efficiency and accelerates the deployment process. Further, the present invention ensures that dependencies and execution requirements are met, leading to a more reliable and consistent deployment process. Furthermore, the present invention enhances the reliability, scalability, and manageability of network functions in modern containerized environments. The real-time inventory update ensures accurate resource allocation, optimized usage, and better network resource management. Furthermore, the present invention improves the deployment, management, and operational efficiency of network function components within the CNF.
[00108] 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

[00109] Environment- 100
[00110] User Equipment (UE)- 102
[00111] Server- 104
[00112] Network- 106
[00113] System -108
[00114] Processor- 202
[00115] Memory- 204
[00116] User Interface- 206
[00117] Database- 208
[00118] Receiving Unit- 210
[00119] Sorting Unit- 212
[00120] Instantiating Unit- 214
[00121] Transmitting Unit- 216
[00122] Updating Unit- 218
[00123] Network function lifecycle manager- 220
[00124] Inventory Manager (IM)- 222
[00125] Container host – 224
[00126] Network Function Components-226
[00127] Container Orchestrator- 302
[00128] Infrastructure – 304
[00129] NFV and SDN design function module -602
[00130] Virtual Network Function (VNF) lifecycle manager -602a,
[00131] VNF catalog -602b,
[00132] Network service catalog -602c,
[00133] Network slicing and service chaining manager -602d,
[00134] Physical and virtual resource manager -602e,
[00135] CNF lifecycle manager -602f
[00136] Platform foundation service module -604
[00137] Microservice elastic load balancer -604a
[00138] Identity and access manager -604b
[00139] Command line interface -604c
[00140] Central logging manager -604d
[00141] Event routing manager -604e
[00142] Platform core service module -606
[00143] NFV infrastructure monitoring manager -606a,
[00144] Assurance manager -606b,
[00145] Performance manager -606c,
[00146] Policy execution engine -606d,
[00147] Capacity monitoring manager -606e
[00148] Release management repository -606f
[00149] Configuration manager and GCT -606g
[00150] NFV platform decision analytics unit -606h
[00151] Platform NoSQL DB -606i
[00152] Platform scheduler and Cron Jobs module -606j
[00153] VNF backup & upgrade manager -606k
[00154] Micro service auditor -606l
[00155] Platform operation, administration and maintenance manager -606m
[00156] Platform resource adapter and utilities module 608
[00157] Platform external API adaptor and gateway -608a
[00158] Generic decoder and indexer -608b
[00159] Swarm adaptor -608c
[00160] OpenStack API adaptor -608d
[00161] NFV gateway -608e
,CLAIMS:CLAIMS

We Claim:
1. A method (500) for instantiation of network function components in a predefined order, the method (500) comprises the steps of:
receiving, by one or more processors (202), a request transmitted by a network function-lifecycle manager (220) to instantiate a Cloud Native Function (CNF) comprising multiple network function components (226);
sorting, by the one or more processors (202), the multiple network function components (226) in the predefined order based on the received request;
instantiating, by the one or more processors (202), the sorted multiple network function components (226) in a container host (224);
transmitting, by the one or more processors (202), an instantiation response to the network function lifecycle manager (220) based on instantiating the multiple network function components (226); and
updating, by the one or more processors (202), an Inventory Manager (IM) (222) based on transmitting an inventory update request from the network function-lifecycle manager (220) to the IM (222).

2. The method (500) as claimed in claim 1, wherein the request includes a predefined order of instantiation.

3. The method (500) as claimed in claim 1, wherein the predefined order is set by at least one of a network operator.

4. The method (500) as claimed in claim 1, wherein the predefined order facilitates execution of the multiple network function components (226) automatically in the defined order.

5. The method (500) as claimed in claim 1, wherein upon instantiating the sorted multiple network function components (226) in the predefined order, the information related to that instantiation and associated one or more resources are stored in a database (208).

6. The method (500) as claimed in claim 1, wherein the CNF is in a running state until each of the multiple network function components (226) are instantiated by the one or more processors in the predefined order.

7. The method (500) as claimed in claim 1, wherein updating the IM (222) includes at least one of, add or release one or more resources which are currently utilized in response to instantiation of each of the multiple network function components (226).

8. The method (500) as claimed in claim 1, wherein the one or more processors enables the network function-lifecycle manager (220) to communicate with the IM (222) via a communication channel.

9. The method (500) as claimed in claim 8, wherein the communication channel is an interface, wherein the interface is at least one of, a CNFLM _container orchestrator (CM_DS) interface to transmits an inventory update request between the network function-lifecycle manager (220) and the IM (222).

10. The method (500) as claimed in claim 1, wherein the inventory update request transmitted from the network function-lifecycle manager (220) to the IM (222) pertains to updating one or more resources subsequent to instantiating the sorted multiple network function components (226) in the predefined order.

11. A system (108) for instantiation of network function components (226) in a predefined order, the system (108) comprises:
a receiving unit (210), configured to, receive, a request transmitted by a network function-lifecycle manager (220) to instantiate a Cloud Native Function (CNF) comprising multiple network function components (226);
a sorting unit (212), configured to, sort, the multiple network function components (226) in the predefined order based on the received request;
an instantiating unit (214), configured to, instantiate, the sorted multiple network function components (226) in a container host (224);
a transmitting unit (216), configured to, transmit, an instantiation response to the network function lifecycle manager (220) based on instantiating the multiple network function components (226); and
an updating unit (218), configured to, update, an Inventory Manager (IM) (222) based on transmitting an inventory update request from the network function-lifecycle manager to the IM (222).

12. The system (108) as claimed in claim 11, wherein the request includes a predefined order of instantiation.

13. The system (108) as claimed in claim 11, wherein the predefined order is set by at least one of a network operator.

14. The system (108) as claimed in claim 11, wherein the predefined order facilitates execution of the multiple network function components (226) automatically in the defined order.

15. The system (108) as claimed in claim 11, wherein upon instantiating the sorted multiple network function components (226) in the predefined order, the information related to that instantiation and associated one or more resources are stored in a database (208).

16. The system (108) as claimed in claim 11, wherein the CNF is in a running state until each of the multiple network function components (226) are instantiated in the predefined order.

17. The system (108) as claimed in claim 11, wherein updating the IM (222) includes at least one of, add or release one or more resources which are currently utilized in response to instantiation of each of the multiple network function components (226).

18. The system (108) as claimed in claim 11, wherein the network function-lifecycle manager (220) communicates with the IM (222) via a communication channel.

19. The system (108) as claimed in claim 18, wherein the communication channel is an interface, wherein the interface is at least one of, a CNFLM _container orchestrator (CM_DS) interface to transmits an inventory update request between the network function-lifecycle manager (220) and the IM (222).

20. The system (108) as claimed in claim 11, wherein the inventory update request transmitted from the network function-lifecycle manager (220) to the IM (222) pertains to updating one or more resources subsequent to instantiating the sorted multiple network function components (226) in the predefined order.