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 MANAGING INSTANTIATION OF A CONTAINER NETWORK FUNCTION (CNF) WITHIN A NETWORK.
2. APPLICANT(S)
NAME NATIONALITY ADDRESS
JIO PLATFORMS LIMITED INDIAN OFFICE-101, SAFFRON, NR. CENTRE POINT, PANCHWATI 5 RASTA, AMBAWADI, AHMEDABAD 380006, GUJARAT, INDIA
3.PREAMBLE TO THE DESCRIPTION

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

FIELD OF THE INVENTION
[0001] The present invention relates to a communication network in a broader sense, more particularly relates to, a system and a method for managing instantiation of a Container Network Function (CNF) within a network.
BACKGROUND OF THE INVENTION
[0002] Telecommunications networks rely on agile and flexible network functions that can adapt rapidly to changing demands. Containerization, exemplified by technologies like Docker and Kubernetes, has become a preferred deployment method for network functions due to its ability to provide lightweight, scalable, and portable environments. Container Network Functions (CNFs) are network functions that are encapsulated within containers, making them highly adaptable and suitable for cloud-native and microservices-based architectures.
[0003] CNFs have introduced a paradigm shift in the deployment and management of network functions. Unlike traditional, hardware-based network functions, CNFs can be instantiated, scaled, updated, and decommissioned with great agility. While this flexibility enhances network resource utilization and reduces operational costs, it also introduces significant challenges.
[0004] They introduce challenges requiring users to know all the hosts present within the POD to instantiate CNF in all the host to provide the replication and define policy. Hence, there is a need in the art for a system and a method to enable.
SUMMARY OF THE INVENTION
[0005] One or more embodiments of the present disclosure provide a method and system for managing instantiation of a Container Network Function (CNF) within a network.
[0006] In one aspect of the present invention, the method for managing instantiation of the CNF within the network is disclosed. The method includes the step of a receiving a CNF instantiation request from a user equipment. The method includes the step of a determining the availability of one or more resources associated with the request within each of a plurality of host provided within each of a plurality of pods based on the received request. The method includes the step of a reserving, the one or more resources based on the availability of the one or more resources within each of the plurality of hosts. The method further includes the step of instantiating, by the one or more processors, the CNF in each of the plurality of hosts via a container adaptor.
[0007] In an embodiment, the request includes predefined attributes pertaining to the CNF, the predefined attributes include one of a global and local presence of the CNF and a position of the CNF in each of the plurality of pods.
[0008] In an embodiment, to determine availability of the one or more resources, the method comprises the steps of retrieving, by the one more processors, details pertaining to each of the plurality of host available within each of the plurality of the pods, where the CNF is required to be instantiated.
[0009] In an embodiment, upon instantiation, the method comprises the step of updating, by the one or more processors, an inventory on completion of the instantiation of the CNF based on an instantiation response received from the container adaptor.
[0010] In an embodiment, if one of the inventory fails to process the request, an available inventory instance will process the request, thereby providing fault tolerance during processing of request.
[0011] In an embodiment, if one of the inventory fails to process the request, an available inventory instance will process the request, thereby providing fault tolerance during processing of request.
[0012] In an embodiment, the global presence of the CNF, instantiating by the Service Adaptors (SA) all a Container Network Function Components (CNFCs) for a particular CNF at the plurality of host within the plurality of the pods.
[0013] In another aspect of the present invention, the system for managing instantiation of the CNF within the network is disclosed. The system includes a receiving unit configured to receive a CNF instantiation request from a user equipment. The system includes a determination unit, configured to determine availability of one or more resources associated with the request within each of a plurality of hosts provided within each of a plurality of pods based on the received request. The system further includes a reservation unit, configured to reserve the one or more resources based on the availability of the one or more resources within each of the plurality of hosts. The system includes an instantiating unit, configured to instantiate the CNF in each of the plurality of servers via a container adaptor.
[0014] 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 CNF instantiation request from a user equipment. The processor is configured to determine, availability of one or more resources associated with the request within each of a plurality of host provided within each of a plurality of the pods based on the received request. The processor is configured to reserve, the one or more resources based on the availability of the one or more resources within each of the plurality of host. The processor is configured to instantiate, the CNF in each of the plurality of host via a container adaptor.
[0015] In another aspect of invention, User Equipment (UE) is disclosed. The UE includes one or more primary processors communicatively coupled to one or more processors, the one or more primary processors coupled with a memory. The processor causes the UE to receive a user input via a User Interface (UI) corresponding to a CNF instantiation request. Thereafter, the processors cause the UE to transmit the CNF instantiation request to the one or more processors.
[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 instantiation of a Container Network Function (CNF) within a network, according to one or more embodiments of the present invention;
[0019] FIG. 2 is an exemplary block diagram of a system for managing instantiation of the CNF within the network, according to one or more embodiments of the present invention;
[0020] FIG. 3 is a schematic representation of a workflow of the system of FIG. 1, according to the one or more embodiments of the present invention;
[0021] FIG. 4 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. 5 is a signal flow diagram for managing instantiation of the CNF within the network, according to one or more embodiments of the present invention; and
[0023] FIG. 6 is a schematic representation of a method of processing data in the network, according to one or more embodiments of the present invention.
[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] FIG. 1 illustrates an exemplary block diagram of an environment 100 for managing instantiation of a Container Network Function (CNF) within a network 105, according to one or more embodiments of the present disclosure. In this regard, the environment 100 includes a User Equipment (UE) 110, a server 115, a network 105 and a system 120 communicably coupled to each other for managing instantiation of the CNF within the network 105.
[0029] As per the illustrated embodiment and for the purpose of description and illustration, the UE 110 includes, but not limited to, a first UE 110a, a second UE 110b, and a third UE 110c, and should nowhere be construed as limiting the scope of the present disclosure. In alternate embodiments, the UE 110 may include a plurality of UEs as per the requirement. For ease of reference, each of the first UE 110a, the second UE 110b, and the third UE 110c, will hereinafter be collectively and individually referred to as the “User Equipment (UE) 110”.
[0030] In an embodiment, the UE 110 is one of, but not limited to, any electrical, electronic, electro-mechanical or an equipment and a combination of one or more of the above devices such as a smartphone, virtual reality (VR) devices, augmented reality (AR) devices, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other computing device.
[0031] The environment 100 includes the server 115 accessible via the network 105. The server 115 may include, by way of example but not limitation, one or more of a standalone server, a server blade, a server rack, a bank of servers, a server farm, hardware supporting a part of a cloud service or system, a home server, hardware running a virtualized server, one or more processors executing code to function as a server, one or more machines performing server-side functionality as described herein, at least a portion of any of the above, some combination thereof. In an embodiment, the entity may include, but is not limited to, a vendor, a network operator, a company, an organization, a university, a lab facility, a business enterprise side, a defense facility side, or any other facility that provides service.
[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 network 105 may also include, by way of example but not limitation, at least a portion of one or more networks having one or more nodes that transmit, receive, forward, generate, buffer, store, route, switch, process, or a combination thereof, etc. one or more messages, packets, signals, waves, voltage or current levels, some combination thereof, or so forth. The network 105 may also include, by way of example but not limitation, one or more of a wireless network, a wired network, an internet, an intranet, a public network, a private network, a packet-switched network, a circuit-switched network, an ad hoc network, an infrastructure network, a Public-Switched Telephone Network (PSTN), a cable network, a cellular network, a satellite network, a fiber optic network, a VOIP or some combination thereof.
[0034] The environment 100 further includes the system 120 communicably coupled to the server 115 and the UE 110 via the network 105. The system 120 is configured for managing instantiation of the CNF within the network 105. As per one or more embodiments, the system 120 is adapted to be embedded within the server 115 or embedded as an individual entity.
[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 the system 120 for managing instantiation of the CNF within the network 105, according to one or more embodiments of the present invention.
[0037] As per the illustrated embodiment, the system 120 includes one or more processors 205, a memory 210, a user interface 215, and a database 220. For the purpose of description and explanation, the description will be explained with respect to one processor 205 and should nowhere be construed as limiting the scope of the present disclosure. In alternate embodiments, the system 120 may include more than one processor 205 as per the requirement of the network 105. The one or more processors 205, hereinafter referred to as the processor 205 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, single board computers, and/or any devices that manipulate signals based on operational instructions.
[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 disk memory, EPROMs, FLASH memory, unalterable memory, and the like.
[0039] In an embodiment, the user interface 215 includes a variety of interfaces, for example, interfaces for a graphical user interface, a web user interface, a Command Line Interface (CLI), and the like. The user interface 215 facilitates communication of the system 120. In one embodiment, the user interface 215 provides a communication pathway for one or more components of the system 120. Examples of such components include, but are not limited to, the UE 110 and the database 220.
[0040] The database 220 is one of, but not limited to, a centralized database, a cloud-based database, a commercial database, an open-source database, a distributed database, an end-user database, a graphical database, a No-Structured Query Language (NoSQL) database, an object-oriented database, a personal database, an in-memory database, a document-based database, a time series database, a wide column database, a key value database, a search database, a cache databases, and so forth. The foregoing examples of database 220 types are non-limiting and may not be mutually exclusive e.g., a database can be both commercial and cloud-based, or both relational and open-source, etc.
[0041] In order for the system 120 for managing instantiation of the CNF within the network 105, the processor 205 includes one or more modules. In one embodiment, the one or more modules/units includes, but not limited to, a receiving unit 225, an analysing unit 230, a determination unit 235, a reservation unit 240, an instantiating unit 245, an updating unit 250 communicably coupled to each other for managing instantiation of the CNF within the network 105.
[0042] In one embodiment, the one or more modules may be used in combination or interchangeably for managing instantiation of the CNF within the network 105.
[0043] The receiving unit 225, the analysing unit 230, the determination unit 235, the reservation unit 240, the instantiating unit 245, the updating unit 250, in an embodiment, may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processor 205. In the examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processor 205 may be processor-executable instructions stored on a non-transitory machine-readable storage medium and the hardware for the processor may comprise a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the memory 210 may store instructions that, when executed by the processing resource, implement the processor. In such examples, the system 120 may comprise the memory 210 storing the instructions and the processing resource to execute the instructions, or the memory 210 may be separate but accessible to the system 120 and the processing resource. In other examples, the processor 205 may be implemented by electronic circuitry.
[0044] In an embodiment, the receiving unit 225 is configured to receive the CNF instantiation request from the UE 110. The receiving unit 225 involves handling requests to deploy and/or manage network functions in the containerized environment. In an embodiment, the request includes predefined attributes pertaining to the CNF, the predefined attributes specify the configuration parameters for the instantiation and operation of CNFs.
[0045] In an embodiment, the predefined attributes ensure that CNFs are deployed according to defined operational requirements and performance criteria includes some of, but not limited to, deployment scope, resource allocation, and a pods placement within the container environment. The predefined attributes include one of the global and local presence of the CNF and the position of the CNF in each of the plurality of the platform operating domains (pods) 430 (as shown in fig.4). The pods 430 refers to a logical container that groups multiple network functions, such as, but not limited to, Cloud-Native Functions (CNFs), Virtual Network Functions (VNFs), and associated resources, which are deployed together to provide specific services. The predefined attributes pertaining to the CNF instantiation request includes, but not limited to, global and local presence, position of the CNF, resource requirements, and service availability.
[0046] In an alternative embodiment, the global presence refers to the deployment of the CNF across multiple geographical regions or data centers worldwide. The local presence pertains to scenarios where the CNF is intended to serve users or applications situated within a limited region, enabling enhanced performance, reduced latency, and better resource allocation. The global presence ensures that the CNF is available and operational across the global network, and it may also efficiently handle such, but not limited to, traffic from users around the world, manage large volumes of data, and provide fast access to network services everywhere. Where the local presence refers to deploying the CNF in specific regional data centers or localized areas within the network 105. The local presence of the CNF will operate within the specific region rather than across the entire global. The position of the CNF defines where the CNF should be instantiated within the network 105 or at the edge, specifying whether it's part of the network core, radio access network, or at the edge for specific applications like network slicing. The resource requirements request may include details about the resource needs such as, but not limited to, compute, memory, and network bandwidth that are necessary for the CNF to operate efficiently within the network infrastructure. The service availability in the network 105 ensures high availability and fault tolerance, the CNF instantiation request could also include, but not limited to, parameters related to fault tolerance, replication, and redundancy across multiple hosts and the pods 430.
[0047] In an embodiment, the plurality of the pods 430 is the virtual group of hosts which allow for the grouping of related containers and manage the deployment and scaling. The plurality of pods 430 located in each regional data center might be distributed across plurality of hosts to ensure load balancing and high availability. For example, the pod 1 handles north america, pod 2 manages europe, and pod 3 oversees asia-pacific.
[0048] Upon receiving request from the UE 110, the analysing unit 230 of the system 120 analyses the global presence of the CNF, instantiating by the SA all a Container Network Function Components (CNFCs) for the particular CNF at the plurality of hosts within the plurality of the pods 430. The SA refers to the role of the Service Adapter (SA) in the instantiation process. The SA facilitates communication between the analyzing unit 230 and the various CNFCs during the instantiation process. The analysing unit 230 considers the predefined attributes associated with the CNF, such as, but not limited to, the CNF's resource requirements, the position of the CNF in the network 105, and the network slicing. Additionally, the analysing unit 230 ensures that the CNF's global presence is consistent with SA requirements, ensuring that the CNFCs are instantiated across multiple servers to provide redundancy and fault tolerance.
[0049] Upon analysing the global presence of the CNF and instantiating by the SA all the CNFCs for the particular CNF, the determination unit 235 is configured to determine availability of one or more resources associated with the request within each of the plurality of host provided within each of the plurality of the pods 430 based on the received request. The one or more resource refers to the critical computational and storage resources needed to successfully deploy and operate the CNF. Specifically, the one or more resources include some of, but not limited to, CPU usage, memory availability, and storage capacity on each host within the plurality of the pods 430 where the CNF is to be instantiated. The determination unit 235 is to determine the availability of the one or more resources. The determination unit 235 retrieves details pertaining to each of the plurality of host available within the specific plurality of the pods 430 where the CNF is required to be instantiated.
[0050] Upon determining the availability of the one or more resources, the reservation unit 240 is configured to reserve the one or more resources based on the availability of the one or more resources within each of the plurality of host 435. Before the one or more resources may be reserved, the reservation unit 240 is necessary to first determine if sufficient resources are available and also involves checking the status of the one or more resources like CPU, memory, and storage on plurality of host within the plurality of the pods 430 where the CNF is to be deployed.
[0051] Upon reserving the one or more resources based on the availability, the instantiating unit 245 is configured to instantiate the CNF in each of the plurality of host 435 via a container adaptor 420 (as shown in fig.4). The instantiating unit 245 is responsible for the actual deployment of the CNF on the plurality of host and the process of creating and starting the CNF instances on the allocated resources. The instantiating unit 245 works in coordination with the resource management system to ensure that the reserved resources, such as CPU, memory, storage, and networking, are provisioned in accordance with the CNF's resource profile. The container adaptor 420 facilitates the deployment by acting as a translation layer between the CNF's deployment requirements and the underlying container orchestration platform (such as Kubernetes). The container adaptor 420 abstracts the complexities of container management, enabling seamless deployment, scaling, and monitoring of CNFCs across the network 105.
[0052] Upon instantiating, the updating unit 250 of the system 120 updates the inventory on completion of the instantiation of the CNF based on the instantiation response received from the container adaptor 420. Where, the updating unit 250 involves changing the status of resources from reserve to in use in the inventory. In addition, the updating unit 250 ensures that the resource usage data is accurately reflected in real-time, enabling effective monitoring of the network's performance. The instantiation response from the container adaptor 420 contains key details about the success or failure of the CNF deployment and also includes such as, but not limited to, deployment metrics, configurations, and any issues encountered. The container adaptor 420 confirms the CNF is deployed across plurality of host in the plurality of the pods 430. Further, the updating unit 250 will log all the information in the inventory, marking the CNF as fully instantiated and operational in the relevant regions.
[0053] Further, if one of the inventory fails to process the request, the available inventory instance will process the request, thereby providing fault tolerance during processing of the request. The inventory refers to the resource management system that keeps track of the available and utilized resources in the network 105, particularly within the CNF infrastructure. The inventory is crucial for managing and organizing the network's resources, ensuring that the system 120 knows the status of hosts, pods 430, containers, and related resources at any given time.
[0054] When the CNF instantiation request is made, the CNF instantiation needs to be processed by the inventory system 120 to update records and reflect the deployment accurately. The processing involves tasks such as, but not limited to, updating records, confirming deployment details, and handling any configuration changes.
[0055] If one instance of the inventory system encounters an issues some of, but not limited to, software bug, hardware failure, and temporary malfunction, and fails to process the request, the inventory system may lead to delays or errors in updating deployment records and to keep things running smoothly and reliably, the system has additional inventory instances available. Wherein one of the instance fails another instance takes over and processes the request.
[0056] In an embodiment, the fault tolerance is the ability of the system to continue operating correctly even in the instance failure of some of its components. In this case, the system 120 design includes redundancy and failover mechanisms to handle failures gracefully. Additionally, the system 120 is prepared with automated recovery processes, such as, but not limited to, self-healing capabilities that detect failures and automatically re-instantiate the failed CNFs or containers on alternate hosts or/and pods 430, ensuring continuous operation without manual intervention.
[0057] FIG. 3 describes a preferred embodiment of the system 120 of FIG. 2, according to various embodiments of the present invention. It is to be noted that the embodiment with respect to FIG. 3 will be explained with respect to the first UE 110a and the system 1020 for the purpose of description and illustration and should nowhere be construed as limited to the scope of the present disclosure.
[0058] As mentioned earlier in FIG. 1, each of the first UE 110a, the second UE 110b, and the third UE 110c may include an external storage device, a bus, a main memory, a read-only memory, a mass storage device, communication port(s), and a processor. The exemplary embodiment as illustrated in FIG. 3 will be explained with respect to the first UE 110a without deviating from the scope of the present disclosure and the limiting the scope of the present disclosure. The first UE 110a includes one or more primary processors 305 communicably coupled to the one or more processors 205 of the system 120.
[0059] The one or more primary processors 305 are coupled with a memory 310 storing instructions which are executed by the one or more primary processors 305. Execution of the stored instructions by the one or more primary processors 305 enables the first UE 110a transmit, a CNF instantiation request to the one or more processors.
[0060] As mentioned earlier in FIG. 2, the one or more processors 205 of the system 120 is configured for managing instantiation of the CNF within the network 105. As per the illustrated embodiment, the system 120 includes the one or more processors 205, the memory 210, the user interface 2015, and the database 220. The operations and functions of the one or more processors 205, the memory 210, the user interface 215, and the database 220 are already explained in FIG. 2. For the sake of brevity, a similar description related to the working and operation of the system 108 as illustrated in FIG. 2 has been omitted to avoid repetition.
[0061] Further, the processor 205 includes the receiving unit 225, the analysing unit 230, the determination unit 235, the reservation unit 240, the instantiating unit 245, the updating unit 250. The operations and functions of the receiving unit 225, the analysing unit 230, the determination unit 235, the reservation unit 240, the instantiating unit 245, the updating unit 250 are already explained in FIG. 2. Hence, for the sake of brevity, a similar description related to the working and operation of the system 120 as illustrated in FIG. 2 has been omitted to avoid repetition. The limited description provided for the system 120 in FIG. 3, should be read with the description provided for the system 120 in the FIG. 2 above, and should not be construed as limiting the scope of the present disclosure.
[0062] FIG. 4 is an exemplary block diagram of an architecture 400 of the system 120 for managing instantiation of the CNF within the network 105, according to one or more embodiments of the present invention.
[0063] The architecture 400 includes the user interface 215, a Container Network Function-Life Cycle Manager (CNFLM) 405, a Physical & Virtual Resource Manager PVIM 410, a Policy Execution Engine (PEEGN) 415, a container adaptor 420, the host 425, and the pods 430.
[0064] The user may be enabled to access the user interface 215. The user interface 215 allows the user to interact with the network management system and perform various operations related to CNFs. In the user interface 215, the user sets or adjusts attributes for the CNF, such as, but not limited to, global and local presence, and its placement within the plurality of the pods 430 to manage the CNFs deployment, scaling, and operation based on network 105 requirements. The user interface 215 transmits the defined attributes and configuration details to the CNFLM 405.
[0065] The CNFLM 405 process the attribute information received from the user interface 215, the processing involves configuring the CNF according to the specified attributes and preparing for the deployment. The CNFLM 405 is responsible for managing the lifecycle of CNFs, including the deployment, scaling, and updates. Based on the attributes received, CNFLM 405 initiates the instantiation of the CNF. The CNFLM 405 involves deploying the CNF according to the specified global or local presence, and ensuring it is positioned correctly within the designated plurality of the pods 430 and across the plurality of host. Once the CNFLM 405 has processed and configured the CNF, the CNFLM 405 transmits the relevant attribute information to the PEEGN 415.
[0066] Upon receiving the relevant attribute information form the CNFLM 405, the PEEGN 415 is configures itself to accommodate the new CNF based on the attribute information received from the CNFLM 405. The PEEGN 415 is responsible for managing packet data and might need to be aware of the CNFs attributes to properly handle data routing and processing. The PEEGN 415 facilitates such as, but not limited to, data processing, routing, and other relevant functions are adjusted to include the new CNF and operate efficiently within the network 105. The PEEGN 415 communicates with the PVIM 410 to retrieve the list of all hosts within the specific plurality of the pods 430 where the CNF is to be instantiated from the PVIM 410 for CNF instantiation, facilitating the aware of all available the plurality of host for the deployment. The PEEGN 415 checks whether the necessary resources for the CNF are available on all hosts within plurality of the pods 430 and each of the plurality of host in the plurality of the pods 430 has adequate the one or more resources for the CNF deployment. The PEEGN sends the requests the PVIM 410 to reserve the required resources on the plurality of host in plurality of the pods 430 to allocate and secure the necessary resources for the CNF, preventing conflicts with other processes. Further, the PEEGN 415 requests to the CNFLM 405 to proceed with the CNF instantiation process and move forward with deploying the CNF based on the reserved resources and specified attributes.
[0067] Upon processing the CNF instantiation, the CNFLM 405 requests the container adaptor 420 to instantiate CNFs on all hosts within plurality of the pods 430 to start the deployment of the CNF instances on the plurality of the host 435. The container adaptor 420 deploys CNF instances on the host 425. Once successful, the host 425 reports back to the container adaptor 420 to create and manage container instances for the CNFs on the specified the hosts 425.
[0068] Further, the container adaptor 420 completes the instantiation of CNFs and informs the CNFLM 405 to confirm the CNF deployment complete successfully. The CNFLM 405 sends the request to the PVIM 415 to update the inventory of resources to confirm the resource management system reflects the current usage and availability after CNF deployment.
[0069] Upon completing the instantiation successful process, the user may continue to monitor the CNF through the user interface 215 and make any necessary changes and ensure that ongoing management and optimization of its deployment and operation within the network 105.
[0070] FIG. 5 is a signal flow diagram for managing instantiation of the CNF within the network 105, according to one or more embodiments of the present invention.
[0071] At step 505, the process begins with the user initiating the request for CNF instantiation through the user interface 215. The user interface 215 request is sent to the CNFLM 405 to manage the lifecycle of the CNF.
[0072] At step 510, the CNFLM 405 receives the instantiation request and forwards to the PEEGN 415 to involves validating the request and ensures that aligns with the operational requirements.
[0073] At step 515, the PEEGN 415 queries the PVIM 410 to obtain the list of all hosts within the specific plurality of the pods 430 where the CNF is to be instantiated. the PEEGN 415 checks if required resources for that CNF are present on all the hosts or not. If all the hosts require the one or more resources, then the PEEGN 415 sends request to the PVIM 410 to reserve the resources on all the hosts.
[0074] In response, the PVIM 410 provides detailed information regarding the available hosts to the PEEGN 415.
[0075] At step 520, the PEEGN 415 responds back to the CNFLM 405 includes a list of available hosts with their operational status and resource availability, along with any relevant constraints or errors regarding the instantiation request.
[0076] At step 525, 530, 535, the CNFLM 405 verifies the availability of the necessary resources on the hosts by interacting with the container adaptor 420 and the host 425 to determine if the host may accommodate the CNF. The PEEGN 415 communicates with the container adaptor 420 to initiate the actual instantiation of the CNF on the host 425. The container adaptor 420 completes the instantiation process and reports back to the CNFLM 405 with the instantiation status, indicating whether the instantiation was successful or if any issues occurred.
[0077] At step 540, the CNFLM 405 also sends the request to the PVIM 410 to update the instantiation status, confirming that the CNF has been instantiated correctly. The PVIM 410 responds with an acknowledgment of the updated instantiation status.
[0078] At step 545, upon confirming that the CNF has been instantiated correctly from the PVIM 410, the CNFLM 405 sends updates to a Resource Management Repository (RMR) 555 to reflect the current usage and availability of resources CNF deployment and confirms the system inventory is accurate and up to date. Upon confirming the system inventory is up to date, the RMR 555 response back to the CNFLM 405 with availability of one or more resources. The RMR 555 is essential for maintaining the comprehensive understanding of resource status, facilitating effective management of CNF deployments, and ensuring the network operates optimally.
[0079] At step 550, finally, the CNFLM 405 sends the CNF instantiation acknowledgment back to the user interface 215, signaling that the entire CNF instantiation process has been completed successfully.
[0080] FIG. 6 is a flow diagram of a method 600 for managing instantiation of the CNF within the network 105, according to one or more embodiments of the present invention. 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.
[0081] At step 605, the method 600 includes the step of receiving the CNF instantiation request from the user equipment 110. The request includes predefined attributes pertaining to the CNF, the predefined attributes include one of the global and local presence of the CNF and the position of the CNF in each of the plurality of the pods 430. The one or more processors analyses the global presence of the CNF by instantiating all the CNFCs for the particular CNF at the plurality of host within the plurality of the pods 430.
[0082] At step 610, the method 600 includes the step determining the availability of one or more resources associated with the request within each of the plurality of host provided within each of the plurality of the pods 430 based on the received request. The determining the availability of the one or more resources, the method 600 comprises the steps of retrieving details pertaining to each of the plurality of host available within the specific plurality of the pods 430, where the CNF is required to be instantiated.
[0083] At step 615, the method 600 includes the step reserving the one or more resources based on the availability of the one or more resources within each of the plurality of host. If one of the inventories fails to process the request, an available inventory instance will process the request, thereby providing fault tolerance during processing of request.
[0084] At step 620, the method 600 includes the step of instantiating the CNF in each of the plurality of host via the container adaptor 420. Upon instantiation, updating the inventory on completion of the instantiation of the CNF based on the instantiation response received from the container adaptor 420.
[0085] The present invention further discloses a non-transitory computer-readable medium having stored thereon computer-readable instructions. The computer-readable instructions are executed by the processor 205. The processor 205 is configured to receive the CNF instantiation request from the UE 110. The processor 205 is further configured to determine the availability of one or more resources associated with the request within each of the plurality of host provided within each of the plurality of the pods 430 based on the received request. The processor 205 is further configured to reserve the one or more resources based on the availability of the one or more resources within each of the plurality of hosts. The processor 205 is further configured to instantiate the CNF in each of the plurality of hosts via the container adaptor 420.
[0086] 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.
[0087] The present disclosure includes technical advancements that ensure optimal resource allocation using determination and reservation units. The invention also features fault tolerance and redundancy mechanisms to maintain continuous service. By integrating with the container adaptor, it automates the deployment of Containerized Network Functions (CNFs) and provides ongoing monitoring and updates through the user-friendly interface. The invention is designed to support various network types and geographical regions, offering scalability and flexibility for different deployment scenarios.
[0088] The present invention offers multiple advantages, including optimal resource utilization through its determination and reservation units, which efficiently allocate CPU, memory, and storage resources to enhance deployment efficiency. It features enhanced fault tolerance and service continuity by incorporating redundancy mechanisms that ensure reliable CNF instantiation even during failures. The system integration with container adaptors automates CNF deployment, reducing manual intervention and streamlining the process through technologies. Additionally, it provides the user-friendly interface for ongoing monitoring and management, allowing users to easily track usage and adjust configurations. Its scalability and flexibility support various networks across different geographical regions, making it adaptable to diverse deployment scenarios.
[0089] 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

[0090] Environment- 100
[0091] User Equipment (UE)- 110
[0092] Server- 115
[0093] Network- 105
[0094] System -120
[0095] Processor- 205
[0096] Memory- 210
[0097] User interface- 215
[0098] Database - 220
[0099] Receiving unit - 225
[00100] Analysing unit - 230
[00101] Determination unit - 235
[00102] Reservation unit - 240
[00103] Instantiating unit - 245
[00104] Updating unit - 250
[00105] Container Network Function-Life Cycle Manager (CNFLM) - 405
[00106] Physical & Virtual Resource Manager (PVIM) – 410
[00107] Container Adaptor - 420
[00108] Host - 425
[00109] Platform operating domains (pods) – 430
[00110] Resource Management Repository (RMR) – 555
,CLAIMS:CLAIMS

We Claim:
1. A method (600) of managing instantiation of a Container Network Function (CNF) within a network, the method (600) comprising the steps of:
receiving, by a one or more processors, a CNF instantiation request from a user equipment;
determining, by the one or more processors, availability of one or more resources associated with the request within each of a plurality of hosts provided within each of a plurality of pods based on the received request;
reserving, by the one or more processors, the one or more resources based on the availability of the one or more resources within each of the plurality of hosts;
instantiating, by the one or more processors, the CNF in each of the plurality of hosts via a container adaptor.

2. The method (600) as claimed in claim 1, wherein the request includes predefined attributes pertaining to the CNF, the predefined attributes include one of a global and local presence of the CNF and a position of the CNF in each of the plurality of pods.

3. The method (600) as claimed in claim 1, wherein to determine availability of the one or more resources, the method comprises the steps of retrieving, by the one more processors, details pertaining to each of the plurality of hosts available within each of the plurality of pods (430) where the CNF is required to be instantiated.

4. The method (600) as claimed in claim 1, wherein upon instantiation, the method comprises the step of updating, by the one or more processors, an inventory on completion of the instantiation of the CNF based on an instantiation response received from the container adaptor.

5. The method (600) as claimed in claim 4, wherein if one of the inventory fails to process the request, an available inventory instance will process the request, thereby providing fault tolerance during processing of request.

6. The method (600) as claimed in claim 2, wherein the global presence of the CNF, instantiating by the SA all the CNFCs for a particular CNF at the plurality of hosts within the specified pod.

7. A system (120) for managing instantiation of a Container Network Function (CNF) within a network (105), the system (120) comprising:

a receiving unit (225), configured to, receive, a CNF instantiation request from a user equipment;
a determination unit (235), configured to, determine, availability of one or more resources associated with the request within each of a plurality of host provided within each of a plurality of pods based on the received request;
a reservation unit (240), configured to, reserve, the one or more resources based on the availability of the one or more resources within each of the plurality of host; and
an instantiating unit (245), configured to, instantiate, the CNF in each of the plurality of servers via a container adaptor.

8. The system (120) as claimed in claim 7, wherein the request includes predefined attributes pertaining to the CNF, the predefined attributes include one of a global and local presence of the CNF and a position of the CNF in each of the plurality of pods (430).

9. The system (120) as claimed in claim 7, wherein to determine availability of the one or more resources, the determination unit retrieves details pertaining to each of the plurality of host available within the specific pod where the CNF is required to be instantiated.

10. The system (120) as claimed in claim 7, wherein upon instantiation, an updating unit (250) of the system updates an inventory on completion of the instantiation of the CNF based on an instantiation response received from the container adaptor (420).

11. The system (120) as claimed in claim 7, wherein if one of the inventories fail to process the request, an available inventory instance will process the request, thereby providing fault tolerance during processing of request.

12. The system (120) as claimed in claim 7, wherein an analysing unit (230) of the system analyses the global presence of the CNF, instantiating by the SA all the CNFCs for a particular CNF at the plurality of hosts within each pod.

13. A User Equipment (UE) (110), comprising:
one or more primary processors (305) communicatively coupled to one or more processors (205), the one or more primary processors (305) coupled with a memory (310), wherein said memory stores instructions which when executed by the one or more primary processors (305) causes the UE (110) to:
receive user input corresponding to a CNF instantiation request;
transmit, the CNF instantiation request to the one or more processors (205);
wherein the one or more processors (205) is configured to perform the steps as claimed in claim 1.