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

COMPLETE SPECIFICATION
(See section 10 and rule 13)
1. TITLE OF THE INVENTION
SYSTEM AND METHOD FOR DYNAMICALLY MANAGING CONTAINER NETWORK FUNCTION (CNF) RESOURCES
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 generally relates to the field of computer networks and cloud computing, and more particularly relates to a system and method for dynamically managing Container Network Function (CNF) resources.
BACKGROUND OF THE INVENTION
[0002] In modern networking and telecommunications infrastructures, the adoption of Container Network Functions (CNFs) has become increasingly prevalent due to their flexibility and scalability. CNFs, which are software-defined network functions running within containers, offer the agility needed to meet the evolving demands of network services. However, their successful deployment relies heavily on a meticulous instantiation process.
[0003] In this context, the CNF instantiation call flow encompasses several critical steps to ensure the reliable operation of CNFs within the network. Among these steps, CNF resource reservation and policy checks emerge as vital components. The life cycle manager of the CNF takes center stage in this process, responsible for overseeing the creation, scaling, and termination of CNF instances. To guarantee a seamless instantiation, the life cycle manager of the CNF collaborates with the Policy Execution Engine (PEEGN).
[0004] PEEGN plays a pivotal role by orchestrating two key tasks: resource reservation and policy validation. Resource reservation entails securing the necessary CPU, memory, and disk resources required for the CNF instance. Meanwhile, policy checks ensure that the CNF and its associated components adhere to predefined resource constraints, optimizing performance and resource allocation. The significance of this process lies in its ability to avert potential chaos. Consider a scenario where CNF instantiation proceeds without resource reservation and policy checks. In such a case, there is no guarantee of resource availability when the CNF is actually being created. This could result in CNFs being deployed without the essential CPU, memory, or disk resources, resulting in immediate operational failures, network instability, and even system crashes.
[0005] Thus, there exists a need for a solution to pre-check available resources and immediately send a response if found required resources are not available in inventory. With an objective to achieve this solution, the present invention discloses a system and method for managing CNF resource reservation and policy check during CNF instantiation to provide a smooth execution between the life cycle manager of the CNF and Policy Execution Engine (PEEGN).
SUMMARY OF THE INVENTION
[0006] One or more embodiments of the present invention provide a system and method for dynamically managing Container Network Function (CNF) resources. This system and method is characterized by its capability to efficiently allocate and manage resources necessary for the deployment of CNFs, thereby optimizing network functionality and responsiveness.
[0007] In accordance with one embodiment, the system for dynamically managing CNF resources is disclosed. This system comprises several interrelated components, each configured to perform specific functions within the resource management process. These components include a connecting module which is configured to establish a first connection between a life cycle manager of the CNF and a Platform Operations, Administration, and Maintenance Manager (POAM). Additionally, the connecting module is configured to establish a second connection between the POAM and a Policy Execution Engine (PEEGN), facilitating communication and data exchange necessary for CNF instantiation. The system further includes a checking module, configured to determine the availability of at least one policy and to reserve resources at the PEEGN based on a user request utilizing the first and second connections. The system further includes a transceiver. Upon the determination of the availability of the policy and the reserve resources at the PEEGN, the transceiver is configured to transmit a reservation request to a Physical Virtual Inventory Manager (PVIM) to reserve resources. Further, the system includes an instantiate module which is configured to request an orchestrator adaptor to instantiate the CNF.
[0008] The system is further configured to transmit an availability request to the PEEGN to check availability of the at least one policy and the reserve resources based on CNF details provided on a Policy Enforcement – Configuration Management (PE_CM) interface module, wherein the PE_CM interface module is provided between the life cycle manager of the CNF and the PEEGN forming the first connection. In one embodiment, the connecting module is further configured to enable an async event-based implementation to manage the PE_CM interface module to function in a high availability mode in order to engage a next available life cycle manager of the CNF instance when a current life cycle manager of the CNF instance is down. In another embodiment, the instantiate module is configured to request for updating inventory at the PEEGN pertaining to resources in use and reserved based on CNF instantiation response from the orchestrator adaptor, wherein the response comprises CNFC instantiation status. The instantiate module is further configured to transmit a request to the PVIM for inventory management based on the CNFC instantiation status.
[0009] In accordance with another embodiment, a method for dynamically managing Container Network Function (CNF) resources is disclosed. The method includes that step of, firstly, establishing a primary connection between a life cycle manager of the CNF and a Platform Operations, Administration, and Maintenance Manager (POAM) by one or more processors. The POAM includes information of at least one of, availability of the life cycle manager of the CNF instances, PVIM instances and a load balancer. Secondly, establishing a secondary connection between the POAM and a Policy Execution Engine (PEEGN) by one or more processors. Thirdly, determining, by one or more processors, the availability of at least one policy and reserving resources at the PEEGN based on a user request by utilizing the first and second connections. Fourthly, upon determination of the availability of the policy and the reservation of resources at the PEEGN, transmitting, by the one or more processors, a reservation request to a Physical Virtual Inventory Manager (PVIM) for the purpose of reserving the necessary resources. Lastly, requesting, by the one or more processors, an orchestrator adaptor to instantiate the CNF.
[0010] The method further includes transmitting, by the one or more processors, an availability request to the PEEGN to check availability of the at least one policy and the reserve resources based on CNF details provided on a Policy Enforcement – Configuration Management (PE_CM) interface module. This PE_CM interface module is provided between the life cycle manager of the CNF and the PEEGN forming the first connection. In one embodiment, the user request pertains to initiating the CNF operation includes at least one of, instantiation, termination or deletion utilizing a PE_CM interface. The one or more processors further includes enabling an async event-based implementation for managing the PE_CM interface module to function in a high availability mode in order to engage a next available life cycle manager of the CNF instance when a current life cycle manager of the CNF instance is down. The one or more processors further includes requesting for updating inventory at the PEEGN pertaining to resources in use and reserved based on CNF instantiation response from the orchestrator adaptor, wherein the response comprises CNFC instantiation status and transmitting a request to the PVIM for inventory management based on the CNFC instantiation status.
[0011] 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
[0012] The accompanying drawings, which are incorporated herein, and constitute a part of this invention, 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 invention. 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 invention of such drawings includes invention of electrical components, electronic components or circuitry commonly used to implement such components.
[0013] FIG. 1 is an exemplary block diagram of an environment for dynamically managing Container Network Function (CNF) resources, according to various embodiments of the present invention.
[0014] FIG. 2 shows a block diagram for a Life cycle manager of a CNF architecture, according to an exemplary implementation of the present invention.
[0015] FIG. 3 illustrates a system architecture for dynamically managing CNF resource reservations, according to an exemplary implementation of the present invention.
[0016] FIG. 4 is a block diagram of a system for dynamically managing CNF resources, according to various embodiments of the present invention.
[0017] FIG. 5 is a schematic representation of the present system of FIG. 4 workflow, according to an exemplary implementation of the present invention.
[0018] FIG. 6 shows a flow chart of a method for dynamically managing CNF resources, according to an exemplary implementation of the present invention.
[0019] FIG. 7 shows a flow chart of a method for dynamically managing CNF resources, according to an exemplary implementation of the present invention.
[0020] FIG. 8 shows a signal flow chart for dynamically managing the CNF resources, according to an exemplary implementation of the present invention.
[0021] The foregoing shall be more apparent from the following detailed description of the invention.
DETAILED DESCRIPTION OF THE INVENTION
[0022] Some embodiments of the present invention, illustrating all its features, will now be discussed in detail. It must also be noted that as used herein and in the appended claims, the singular forms "a", "an" and "the" include plural references unless the context clearly dictates otherwise.
[0023] Various modifications to the embodiment will be readily apparent to those skilled in the art and the generic principles herein may be applied to other embodiments. However, one of ordinary skill in the art will readily recognize that the present invention including the definitions listed here below are not intended to be limited to the embodiments illustrated but is to be accorded the widest scope consistent with the principles and features described herein.
[0024] A person of ordinary skill in the art will readily ascertain that the illustrated steps detailed in the figures and here below are set out to explain the exemplary embodiments shown, and it should be anticipated that ongoing technological development will change the manner in which particular functions are performed. These examples are presented herein for purposes of illustration, and not limitation. Further, the boundaries of the functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternative boundaries can be defined so long as the specified functions and relationships thereof are appropriately performed. Alternatives (including equivalents, extensions, variations, deviations, etc., of those described herein) will be apparent to persons skilled in the relevant art(s) based on the teachings contained herein. Such alternatives fall within the scope and spirit of the disclosed embodiments.
[0025] A system and method for dynamically managing Container Network Function (CNF) is disclosed. More particularly, dynamically managing the CNF during a CNF instantiation is disclosed. This system and method is characterized by its capability to efficiently allocate and manage resources necessary for the deployment of CNFs, thereby optimizing network functionality and responsiveness.
[0026] Various embodiments of the invention provide a system and a method for dynamically managing CNF resources are disclosed. The present invention describes a solution for CNF status and CNF resource reservation by providing a novel interface, which otherwise called as a Policy Enforcement_Configuration Management (PE_CM) interface, between a life cycle manager of a CNF and a Policy Execution Engine (PEEGN) to provide a smooth execution of CNF resource reservation and policy check during CNF instantiation. The present invention allows to pre-check available resources and to send a negative response immediately if found required resources are not available in inventory.
[0027] Referring to FIG. 1, FIG. 1 is an exemplary block diagram of an environment 100 for dynamically managing CNF resources, according to various embodiments of the present invention. The environment 100 includes a user equipment 110. For the purpose of description and explanation, the description will be explained with respect to one or more user equipment’s (UE) 110, or to be more specific will be explained with respect to a first UE 110a, a second UE 110b, and a third UE 110c, and should nowhere be construed as limiting the scope of the present disclosure.
[0028] In an embodiment, each of the first UE 110a, the second UE 110b, and the third UE 110c is one of, but are not limited to, any electrical, electronic, electro-mechanical or an equipment and a combination of one or more of the above devices such as virtual reality (VR) devices, augmented reality (AR) devices, laptop, general-purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other computing device.
[0029] In accordance with one aspect of the present invention, each of the first UE 110a, the second UE 110b, and the third UE 110c is configured to facilitate the transmission of a request via a communication network 105 for the purpose of availing a variety of services. The scope of said services is inclusive of, but not limited to, engaging with a server 115 for the purpose of submitting a request thereto, initiating a process for the reconstruction of data, and subsequently conducting oversight of the data thus reconstructed, all aforementioned activities being conducted over the communication network 105. This configuration enables a streamlined and efficient interaction between the user equipment and the network resources, thereby enhancing the utility and performance of the communication network 105 in providing said services.
[0030] The server 115 may include by way of example but not limitation, one or more of a standalone server, a server blade, a server rack, a bank of servers, a server farm, hardware supporting a part of a cloud service or system, a home server, hardware running a virtualized server, one or more processors executing code to function as a server, one or more machines performing server-side functionality as described herein, at least a portion of any of the above, some combination thereof. In an embodiment, the entity may include, but is not limited to, a vendor, a network operator, a company, an organization, a university, a lab facility, a business enterprise, a defence facility, or any other facility that provides content.
[0031] The communication 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 communication 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.
[0032] The environment 100 further includes a system 125 communicably coupled to the server 115 and each of the first UE 110a, the second UE 110b, and the third UE 110c via the communication network 105. The system 125 is configured to dynamically manage CNF resource reservation and policy check during CNF instantiation in the communication network 105.
[0033] The system 125 is further configured to employ Transmission Control Protocol (TCP) connection to identify any connection loss in the communication network 105 and thereby improving overall efficiency. The TCP connection is a communication standard enabling applications and the system 125 to exchange information over the communication network 105.
[0034] Operational and construction features of the system 125 will be explained in detail with respect to the following figures.
[0035] FIG. 2 shows a block diagram for a life cycle manager of the CNF 204 architecture 200, according to an exemplary implementation of the present invention. Herein after, the life cycle manager of the CNF is referred to a CNF Life Cyle Manager (CNFLM) 204 without limiting the scope of the invention. The architecture 200 comprises the CNFLM 204 connected to the communication network 105 and a Policy Execution Engine (PEEGN) 206 connected to the CNFLM 204 via the communication network 105. The CNFLM 204 and the PEEGN 206 is configured to form a core management in the present invention. In particular, the PEEGN 206 is a software component that allows an system to create, monitor and enforce policies/rules about the one or more CNF operations such as a CNF instantiation.
[0036] In one embodiment, the architecture 200 comprises a Policy Enforcement_Configuration Management (PE_CM) interface 214 provided between the CNFLM 204 and the Policy Execution Engine (PEEGN) 206 to provide a smooth execution of CNF resource reservation and policy check during CNF instantiation. The PE_CM interface 214 provides a rich user interface to a user, where the user can initiate CNF requests. In one embodiment, the policy is a set of rules that govern the behaviors of the CNFs. The policies facilitates in performing one or more operation related to the CNFs. Herin the policies may be referred to one or more CNF policies or CNF policy which pertains to at least one of, but not limited to, scaling, self-healing, and auto-correction of the CNF configurations.
[0037] In an embodiment of the present invention, the CNFLM 204 may send requests to the PEEGN 206 for checking CNF policy and reserve resources. In one embodiment, the resource is any kind of device, information, or service available across the network. The reserve resources includes at least one of, but not limited to bandwidth, compute capacity, storage. In an alternate embodiment, the reserve resources include at least one of, but not limited to, a Central Processing Unit (CPU), memory components such as Random Access Memory (RAM) and Read Only Memory (ROM). In other words, the reserved resources are the resources that are defined, and their present amount is recognized, but since they are reserved for the future, they are not being used. The PEEGN 206 checks the CNF policy and reserve resources based on provided CNF details on PE_CM interface 214. In case the CNF policy validation is positive, the PEEGN 206 sends requests to reserve the resources. Further the CNFLM 204 may request an orchestrator adaptor to instantiate the CNF. Herin after, the orchestrator adaptor is referred to a Docker Swarm Adaptor (DSA) without limiting the scope of the invention.
[0038] The architecture 200 further comprises an infrastructure module 208 forming a docker Infrastructure and a swarm cluster, wherein the container may be created. The architecture 200 further comprises a user interface layer 202 connected to the core management of the system, a Network Management System (NMS) module 210 and a database 212 connected to the core management system. The NMS module 210 deals with FCAPS related operations, and the database 212 is a persistent database used for storing all data related to the operations.
[0039] FIG. 3 shows a block diagram for the CNFLM 204 architecture 300, according to an exemplary implementation of the present invention. The CNFLM 204 architecture 300 comprises a CNFLM micro service 204, a Docker Swarm Adapter (DSA) 306 (306a, 306b,… 306n), a Physical Virtual Inventory Manager (PVIM) 302, a swarm manager 308 and a Policy Execution Engine 206.
[0040] The CNFLM micro service 204 is configured to capture the details of Vendors, CNFs and CNFCs via Create, Read, and Update API’s exposed by the service itself. The captured details may be stored in the database 212 and may be further used by the DSA 306. In an embodiment, the CNFLM 204 is responsible for creating CNF or individual CNFC instance. The CNFLM 204 also scales out CNFs or individual CNFCs. The CNFLM 204 architecture 300 comprises a graphical user interface (GUI) 202 for obtaining requests to onboard/instantiate/terminate CNF instance for the CNFLM 204.
[0041] In the embodiment of the present disclosure, the DSA 306 is configured to interact with CNFLM 204 to spawn appropriate CNF instances / CNFC instances. The DSA 306 may directly connect to docker host of swarm manager 308 to deploy the docker image to docker host nodes will connect to the swarm manager 308. The DSA 306 may further create Docker Agent manager (DAM) and add docker hosts as swarm worker node in a call flow.
[0042] In an embodiment, the DSA 306 is deployed at a region wise, and all CNF related operations are also happening region wise for every request. The CNFLM 204 may request region related detail to the PEEGN 206 and based on the request, an Elastic Load Balancer (ELB) may route the requests to region specific DSA 306.
[0043] The PVIM 302 is used to obtain the status of instantiated CNF/CNFC upon subscription to CNF-LM Ack event. The PVIM manager 302 is further used to update the inventory mapping from reserved to use. The CNFLM 204 further comprises the PEEGN 206 for supporting scaling policy for CNFC. In an embodiment, the PEEGN 206 checks for CNF INIT policy and reserves resources required to instantiate CNF at PVIM 302 during CNF Instantiation flow.
[0044] The swarm manager 308 comprises a swarm consisting of multiple docker hosts configured to run in swarm mode and act as managers and workers (W1, W2, W3,… Wn). The swarm may act as managers to manage membership and delegation and workers to run swarm services. A given docker host can be a manager, a worker or perform both roles. Further, the DAM facilitates the management of the docker services and containers to act as an intermediary layer that aids in the deployment, scaling, monitoring, and management of docker containers across a cluster of nodes within a docker swarm environment.
[0045] The DAM provides various functionalities such as automating the deployment of containers to the appropriate nodes. The DAM manages the lifecycle of containers across the swarm and monitors the health and status of containers and nodes. The DAM further facilitates the communication and coordination between docker swarm manager nodes and worker nodes and provides a user interface or API for administrators to manage the swarm environment.
[0046] Referring to FIG. 4, FIG. 4 is an exemplary block diagram of the system 125 for dynamically managing CNF resources, according to various embodiments of the present invention. The system 125 is adapted to be embedded within the server 115 or is embedded as an individual entity. However, for the purpose of description, the system 125 is described as an integral part of the server 115, without deviating from the scope of the present disclosure.
[0047] As per the illustrated embodiment, the system 125 includes one or more processors 406, a memory 402, and an I/O Interfaces 404. The one or more processors 406, hereinafter referred to as the processor 406 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. As per the illustrated embodiment, the system 125 includes one or more processors 406. However, it is to be noted that the system 125 may include multiple processors as per the requirement and without deviating from the scope of the present disclosure. Among other capabilities, the processor 406 is configured to fetch and execute computer-readable instructions stored in the memory 402. The memory 402 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 402 may include any non-transitory storage device including, for example, volatile memory such as RAM, or non-volatile memory such as EPROM, flash memory, and the like.
[0048] In an embodiment, the input/output (I/O) interface unit 404 includes a variety of interfaces, for example, interfaces for data input and output devices, referred to as Input/Output (I/O) devices, storage devices, and the like. The I/O interface unit 404 facilitates communication of the system 125. In one embodiment, the I/O interface unit 404 provides a communication pathway for one or more components of the system 125. Examples of such components include, but are not limited to, the UE 110 and a database 212.
[0049] The database 212 is one of, but is not limited to, one of 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 the backend database 212 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.
[0050] Further, the processor 406, in an embodiment, may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processor 205. In the examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processor 205 may be processor-executable instructions stored on a non-transitory machine-readable storage medium and the hardware for processor 205 may comprise a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the memory 210 may store instructions that, when executed by the processing resource, implement the processor 205. In such examples, the system 125 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 125 and the processing resource. In other examples, the processor 205 may be implemented by electronic circuitry.
[0051] In order for the system 125 to dynamically manage CNF resource reservation and policy check during CNF instantiation in the communication network 105, the processor 406 includes a connecting module 408, a checking module 410, an instantiate module 412 and a transceiver 414 communicably coupled to each other.
[0052] The connecting module 408 of the processor 406 is communicably connected to each of the first UE 110a, the second UE 110b, and the third UE 110c via the communication network 105. In particular, the utilizing the UE 110 the user transmits a request for initiating the CNF operation includes at least one of, but not limited to, a CNF instantiation, a CNF termination or a CNF deletion via the PE_CM interface. Accordingly, the connecting module 408 is configured to establish a primary connection interfacing the CNFLM 204 with the POAM. Additionally, the connecting module 408 is equipped to establish a secondary connection between the POAM and the PEEGN 206. Doing so facilitates a dual-channel communication pathway essential for the orchestration of CNF deployment processes.
[0053] In other words, the connecting module 408 is configured to establish a first connection between the CNFLM 204 and the POAM. Thereafter, the connecting module 408 is configured to establish a second connection between the POAM and the PEEGN 206. In one embodiment, the connections between the CNFLM 204 and the POAM, and POAM and the PEEGN 206 is at least one of, but not limited to, a Transmission Control Protocol (TCP) connection.
[0054] In one embodiment, the TCP connection establishment process involves a series of steps, often referred to as a "three-way handshake," process where a first node and a second node establishes a secure and synchronized connection before initiating the actual data transfer. Herin the first node may be at least one of, the CNFLM 204 and the POAM, and the second node may be at least one of, the POAM and the PEEGN 206 without limiting the scope of the invention. In particular, the first node initiates the connection request by sending a TCP packet with the synchronize (SYN) flag set to the second node. The TCP packet indicates that the first nodes desire to establish the connection. Upon receiving the TCP packet, the second node responds with a TCP packet that has both the SYN and acknowledge (ACK) flags set. The TCP packet acknowledges the firsts node request and signals the second node readiness to establish the connection. Finally, the first node sends an acknowledgment (ACK) packet to the second node. The ACK packet acknowledges the second node readiness, and the connection is now established.
[0055] The checking module 410 is configured to determine the availability of one or more CNF policies and to secure the reservation of requisite resources within the PEEGN 206. In particular, the checking module 410 checks for the availability of the one or more CNF policies in the PEEGN 206 by transmitting an availability request to the PEEGN 206 based on CNF details provided on the PE_CM interface module 214. In particular, the availability request may be at least one of, a Hyer Text Transfer Protocol (HTTP) request. In particular, when the user transmits the request for instantiation of the CNF the request includes the CNF details which are provided on the PE_CM interface module 214.
[0056] Based on checking the checking module 410 determines whether there are one or more CNF policies available in the PEEGN 206. Herein, the one or more CNF policies pertains to at least one of, but not limited to, scaling, self-healing, and auto-correction of the CNF configurations. This evaluation and reservation process leverages both the aforementioned first and second connections, drawing upon user requests as the basis for initiating these actions. The checking module 410 plays a pivotal role in ensuring that the necessary policy frameworks and resources are in place for CNF instantiation.
[0057] Upon the checking module's 410 successful determination of both CNF policy availability and resource reservation feasibility within the PEEGN 206, a transceiver 414 is activated. This transceiver 414 is specifically configured to issue a reservation request directed towards the PVIM 302. The primary function of the reservation request is to secure the allocation of the necessary resources earmarked for CNF deployment, thereby facilitating a critical step in the CNF instantiation process.
[0058] An instantiate module 412, which is uniquely configured to engage the DSA 306 with the request to instantiate the CNF. The instantiate module 412 represents the culmination of the system 125 orchestrated efforts, translating the preparatory steps of connections establishment, policy and resource checks, and resource reservation into the concrete action of CNF instantiation. In one embodiment of the present invention, the instantiate module 412 issues the request to the DSA 306 for the purpose of instantiating the CNF. This request initiates a sequence of operations within the DSA 306 designed to allocate, configure, and deploy the necessary resources for the CNF within the docker swarm environment 308. Thereafter, dynamic assessment and provisioning of resources based on the specific requirements of the CNF is instantiated. Doing so advantageously ensures optimal configuration and performance. The DSA 306, upon receiving the instantiation request, engages in a series of interactions with the underlying docker swarm infrastructure to facilitate the deployment of the CNF, including the reservation of network interfaces, the allocation of computational resources, and the establishment of necessary environmental variables and configurations. This process is characterized by its adaptability and responsiveness to the dynamic requirements of CNF instantiation, thereby contributing to the efficient and effective management of CNF resources within a Docker Swarm ecosystem.
[0059] In one embodiment, while performing the CNF operation such as the CNF instantiation, CNF termination or CNF deletion utilizing the PE_CM interface 214, if the processor 406 detects that a current CNFLM instance 204 is down. For example, while performing the CNF instantiation, if the current CNFLM 204 is not able to transmit the request to PEEGN 206 to reserve resources for the CNF instantiation, then the processor 406 detects that a current CNFLM instance 204 is down. Based on the detection, the processor 406 enables an async event-based implementation for managing CNFLM instance 204 via the PE_CM interface module. Herin, managing pertains to engaging a next available CNFLM instance when the current CNFLM 204 instance is down. In order words, the processor 406 replaces the current CNFLM 204 which is down with the next available CNFLM instance. Due to which the CNF instantiation process is not disturbed. In particular, in asynchronous events the execution of one task isn't dependent on another. Multiple tasks can run simultaneously. In an alternate embodiment, the asynchronous programming is a technique that enables program to start a potentially long-running task and still be able to be responsive to other events while that task runs, rather than having to wait until that task has finished.
[0060] FIG. 5 is a schematic representation of the present system of FIG. 4 workflow, according to an exemplary implementation 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 for the purpose of description and illustration and should nowhere be construed as limited to the scope of the present disclosure.
[0061] In an embodiment, the first UE 110a may encompass electronic apparatuses. These devices are illustrative of, but not restricted to, personal computers, laptops, tablets, smartphones (including phones), or other devices enabled for web connectivity. The scope of the first UE 110a explicitly extends to a broad spectrum of electronic devices capable of executing computing operations and accessing networked resources, thereby providing users with a versatile range of functionalities for both personal and professional applications. This embodiment acknowledges the evolving nature of electronic devices and their integral role in facilitating access to digital services and platforms. In an embodiment, the first UE 110a can be associated with multiple users. Each user equipment 110 is communicatively coupled with the processor 406 via the communication network 105.
[0062] The first UE 110a includes one or more primary processors 502 communicably coupled to the one or more processors 406 of the system 125. The one or more primary processors 502 are coupled with a memory unit 504 storing instructions which are executed by the one or more primary processors 502. Execution of the stored instructions by the one or more primary processors 502 enables the first UE 110a to transmit a request from the user via the interface module to the communication network 105, in order to avail the one or more services.
[0063] Furthermore, the one or more primary processors 502 within the UE 110 are uniquely configured to execute a series of steps as described herein. This configuration underscores the processor’s capability to dynamically manage CNF resources during a CNF instantiation process. The operational synergy between the primary processors and the additional processors, guided by the executable instructions stored in the memory, facilitates a seamless initiation of CNF operations. This initiation is critically underpinned by the dynamic resource management capabilities, which includes establishing necessary connections for policy and resource evaluation, determining the availability of CNF policies, reserving resources based on these policies, and ultimately facilitating the instantiation of the CNF.
[0064] Further, the one or more processors 406 of the system 125 is configured to rebuild the data by using the backend database 212. More specifically, the one or more processors 406 of the system 125 is configured to rebuild the data from a kernel 506 of at least one of the first UE 110a in response to dynamically managing the CNF resources during the CNF instantiation.
[0065] The kernel 506 is a core component serving as the primary interface between hardware components of the first UE 110a and the plurality of services at the backend database 212. The kernel 315 is configured to provide the plurality of services on the first UE 110a to resources available in the communication network 105. The resources include one of a Central Processing Unit (CPU), memory components such as Random Access Memory (RAM) and Read Only Memory (ROM).
[0066] In the present embodiment, the processor 406 is configured to cooperate with the first UE 110a. The processor 406 includes the memory 402, the I/O Interfaces 404, the database 212, the connecting module 408, the checking module 410, the transceiver 414 and the instantiate module 412. The functionality and arrangement of the same are as described with respect to FIG. 4, and hence for the sake of brevity will not be repeated. This should, however, not be construed as limiting the scope of the present disclosure.
[0067] In another embodiment of the present invention, embodied within a non-transitory computer-readable medium, are stored computer-readable instructions that, when executed by a processor 406, endow the processor 406 with a multifaceted capability pivotal to the orchestration of the CNF resources. Initially, these instructions facilitate the establishment of a primary connection between the CNFLM 204 and the POAM, followed by the creation of a secondary linkage with the PEEGN 206. This dual connectivity underpins a critical evaluation process, wherein the processor 406 determines the availability of one or more specific CNF policies and the corresponding resource reservation status at the PEEGN 206, leveraging user requests as the basis for this determination. Upon affirmative determination of policy availability and resource reservation feasibility, the instructions further compel the processor to initiate a reservation request towards the PVIM 302 for resource allocation. The culmination of this process sees the processor orchestrating a request to the DSA 306, tasked with the instantiation of the CNF. This sequence of operations, encoded within the computer-readable medium, embodies a comprehensive approach to managing and deploying CNF resources, reflecting a significant advancement in the field of network function virtualization and containerization technologies.
[0068] FIG. 6 shows a flow chart of the method 600 for dynamically managing CNF resources, according to an exemplary implementation of the present invention. The method 600 may be implemented by the system 125. The system 125 comprises the CNFLM 204 connected to the communication network 105, and the PEEGN 206 connected to the CNFLM 204 via the communication network 105, the infrastructure module 208, at least one user interface layer 202 connected to the CNFLM 204 and PEEGN 206, the NMS module 210 and the database 212 connected to the core network.
[0069] The method comprises various steps illustrated in multiple steps for CNF Instantiation.
[0070] At step 605, sending requests to the PEEGN)206 for checking the CNF policy and reserve resources based on the provided CNF details on PE_CM interface 214 by the CNFLM 204. The CNFLM 204 is configured to send requests to the Policy Execution Engine (PEEGN) 206 for checking CNF policy and reserve resources based on the provided CNF details on the PE_CM interface 214.
[0071] At step 610, determining whether the policy validation is positive by the PEEGN 206. The PEEGN 206 is configured to determine whether the policy validation is positive.
[0072] At step 615, sending request to the PVIM 302 to reserve resources if the policy validation is positive by the PEEGN 206. The PEEGN 206 is configured to send request to the PVIM 302 to reserve resources if the policy validation is positive.
[0073] At step 620, requesting the DSA 306 by the CNFLM 204 to instantiate CNF. The CNFLM 204 is configured to request the DSA 306 to instantiate the CNF.
[0074] At step 625, requesting for update inventory based on CNF Instantiation response from the DSA 306 by the CNFLM 204, which comprises all CNFC Instantiation status. The CNFLM 204 is configured to request for updating the inventory based on CNF Instantiation response from the DSA 306.
[0075] At step 630, sending the request to the PVIM 302 by the CNFLM 204 for proper inventory management by the CNFLM 204. The CNFLM 204 is configured to send request to the PVIM 302 by the CNFLM 204 for proper inventory management.
[0076] FIG. 7 shows a flow chart of a method 700 for dynamically managing the CNF resources, according to an exemplary implementation of the present invention. The method comprises various steps illustrated in multiple steps for CNF Instantiation.
[0077] At step 705, establishing a first connection between the CNFLM 204 and the POAM by the connecting module 408. The connecting module 408 is configured to establish the first connection between the CNFLM 204 and the POAM.
[0078] At step 710, establishing the second connection between the POAM and the PEEGN 206 by the connecting module 408. The connecting module 408 is configured to establish the second connection between the POAM and the PEEGN 206.
[0079] At step 715, determining availability of at least one CNF policy and reserve resources at the PEEGN 206 based on the user request utilizing the first connection and the second connection by the checking module 410. The checking module 410 is configured to determine availability of at least one CNF policy and reserve resources at the PEEGN 206 based on the user request utilizing the first connection and the second connection.
[0080] The first connection between the CNFLM 204 and the POAM, and the second connection between the POAM and the PEEGN 206 is established in order to determine availability of at least one CNF policy and one or more reserve resources at the PEEGN 206 based on the user request.
[0081] At step 720, transmitting the reservation request to the PVIM 302 to reserve resources by the transceiver 414 if determined availability of the CNF policy and reserve resources at the PEEGN 206. The transceiver 414 is configured to transmit the reservation request to the PVIM 302 to reserve resources, if determined availability of the CNF policy and reserve resources at the PEEGN 206.
[0082] At step 725, requesting the DSA 306 to instantiate the CNF by the instantiate module 412. The instantiate module 412 is configured to request the DSA 306 to instantiate the CNF based on the availability of the CNF policy and reserve resources at the PEEGN 206.
[0083] FIG. 8 shows a signal flow chart for dynamically managing the CNF resources, according to an exemplary implementation of the present invention.
[0084] At step 802, the CNF instantiation request is transmitted by the user via the PE_CM interface to the CNFLM 204 to instantiate the CNF.
[0085] At step 804, the CNFLM 204 transmits the request to the PEEGN 206 to reserve resources in order to instantiate the CNF.
[0086] At step 806, the PEEGN 206 reserve resources and transmits the reservation acknowledgement to the CNFLM 204. In particular, the reservation acknowledgement may include a repose pertaining to the reserved resources for instantiation of the CNF.
[0087] At step 808, the CNFLM 204 transmits the instantiation request to the orchestrator adaptor such as the DSA 306 subsequent to reserving the resources in the PEEGN 206.
[0088] At step 810, the DSA 306 transmits the instantiation request to the docker host to instantiate the CNF.
[0089] At step 812, the instantiation status is transmitted from the docker host to the DSA 306 subsequent to instantiating the CNF.
[0090] At step 814, the DSA 306 transmits the instantiation acknowledgement to the CNFLM 204 which notifies regarding the instantiated CNF.
[0091] At step 816, the CNFLM 204 transmits the update inventory request to the PVIM 302 to update details pertaining to the instantiated CNF in the PVIM 302.
[0092] At step 818, the PVIM 302 transmits the update inventory acknowledgement to the CNFLM 204 subsequent to updating the details pertaining to the instantiated CNF.
[0093] At step 820, the CNFLM 204 transmits the updated instantiation status to a Release Management Repository (RMR).
[0094] At step 822, the RMR transmits the updated instantiation status acknowledgement to the CNFLM 204 subsequent to storing the updated instantiation status in the RMR.
[0095] At step 824, the CNFLM 204 transmits the CNFLM instantiation acknowledgement to the user which notifies the user regarding the initiated CNF.
[0096] A person of ordinary skill in the art will readily ascertain that the illustrated steps in FIG. 1 to FIG. 8 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.
[0097] The present invention provides a novel interface for smooth execution of CNF resource reservation and policy check during CNF instantiation. The present invention involves an async event-based implementation to utilize the PE_CM interface 214 efficiently. The interface works in a high availability mode and if one CNFLM 204 instance goes down during request processing then the next available instance takes care of the request during fault tolerance for any event failure. The present invention ensures proper resource reservation on CNF and CNFC instantiation process. One of the key advantages of the present method approach is its proactive nature. The resource (CPU, Memory, Disk) constraints are checked before CNF and CNFC instantiation. Further, resource (CPU, Memory, Disk) constraints are checked for change management. By pre-checking available resources and validating policies before initiating the instantiation call to the Docker Swarm Adaptor (DSA), potential resource availability issues are addressed preemptively. This proactive stance empowers the system to promptly reject instantiation requests if the required resources are not available in the inventory, safeguarding network stability and efficiency.
[0098] In accordance with another embodiment of the present invention, a method for dynamically managing CNF resources via a novel interface in accordance with another embodiment of the present invention. The novel interface is a via PE_CM interface 214 as shown in FIG. 2.
[0099] Through its innovative design and functional modules, the disclosed system and method enables efficient and dynamic management of resources for CNF instantiation, enhancing network performance and adaptability. This invention represents a significant advancement in the field of telecommunications, particularly in the deployment and management of containerized network functions.
[00100] In accordance with an embodiment of the method, the operation of determining the availability of at least one Container Network Function (CNF) policy and the reservation of necessary resources at the Policy Execution Engine (PEEGN) 206, predicated upon a specific user requisition, is augmented by an imperative procedural step. This step involves the actuation of one or more processors to initiate the transmission of an availability inquiry directed towards the PEEGN 206. The principal aim of this inquiry is to meticulously verify the presence and accessibility of the specified CNF policy or policies and to confirm the reservation status of the resources required for the CNF deployment. This verification process is critically underpinned by the provision of detailed CNF specifications, which are systematically relayed through the PE_CM interface module 214. This procedure ensures a rigorous and informed evaluation of policy compliance and resource allocation, thereby enhancing the efficiency and effectiveness of CNF instantiation.
[00101] A person of ordinary skill in the art will readily ascertain that the illustrated embodiments and steps in description and drawings 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.
[00102] 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.
[00103] Glossary
- CNF : Container Network Function
- CNFLM : CNF life cycle manager
- PEEGN : Policy Execution Engine
- NMS : Network Management System
- DSA : Docker Swarm Adaptor
- PE_CM : Policy Execution Cycle Manager

REFERENCE NUMERALS
[00104] Environment - 100;
[00105] Communication network – 105
[00106] User Equipments - 110;
[00107] Server – 115
[00108] System -125
[00109] Database - 212;
[00110] CNF Life Cycle Manager (CNFLM) – 204;
[00111] Policy Execution Engine (PEEGN) – 206;
[00112] PE_CM Interface – 214;
[00113] User Interface Layer – 202;
[00114] Infrastructure – 214;
[00115] NMS – 210;
[00116] PVIM – 302;
[00117] RMR – 304;
[00118] DSA – 306;
[00119] Swarm Manager – 308;
[00120] Memory - 402;
[00121] Processor - 406;
[00122] Connecting module - 408;
[00123] Checking module - 410;
[00124] Transceiver - 414;
[00125] Instantiate module – 412;
[00126] I/O Interfaces – 404;
[00127] Primary Processor – 502;
[00128] Memory unit – 504;
[00129] Kernel – 506.
,CLAIMS:CLAIMS
We Claim:
1. A method for dynamically managing Container Network Function (CNF) resources, the method comprises the steps of:
establishing, by one or more processors (406), a first connection between a life cycle manager (204) of a CNF and a Platform Operations, Administration and Maintenance Manager (POAM);
establishing, by the one or more processors (406), a second connection between the POAM and a Policy Execution Engine (PEEGN) (206);
determining availability of at least one policy and reserve resources at the PEEGN (206) based on a user request utilizing the first connection and the second connection;
if determined availability of the policy and reserve resources at the PEEGN (206), transmitting, by the one or more processors, a reservation request to a Physical Virtual Inventory Manager (PVIM) (302) to reserve resources; and
requesting, by the one or more processors (406), an orchestrator adaptor (306) to instantiate the CNF.

2. The method as claimed in claim 1, wherein the step of determining, by the one or more processors (406), availability of at least one policy and reserve resources at the PEEGN (206) based on a user request, includes the step of:
transmitting, by the one or more processors (406), an availability request to the PEEGN (206) to check availability of the at least one policy and the reserve resources based on CNF details provided on a PE_CM interface module (214).

3. The method as claimed in claim 1, wherein the POAM includes information of at least one of, availability of the life cycle manager (204) instances, PVIM (302) instances and a load balancer.

4. The method as claimed in claim 1, wherein a PE_CM interface (214) is provided between the life cycle manager (204) and the PEEGN (206) forming the first connection.

5. The method as claimed in claim 1, wherein the user request pertains to initiating the CNF operation includes at least one of, instantiation, termination or deletion utilizing a PE_CM interface (214).

6. The method as claimed in claim 1, wherein the one or more processors (406) further includes enabling an async event-based implementation for managing the PE_CM interface module (214) to function in a high availability mode in order to engage a next available life cycle manager (204) instance when a current CNFLM (204) instance is down.

7. The method as claimed in claim 1, wherein the step of requesting, by the one or more processors (406), a orchestrator adaptor (306) to instantiate CNF, includes the steps of:
requesting, by the one or more processors (406), for updating inventory at the PEEGN pertaining to resources in use and reserved based on CNF instantiation response from the orchestrator adaptor (306), wherein the response comprises CNFC instantiation status; and
transmitting, by the one or more processors (406), a request to the PVIM (302) for inventory management based on the CNFC instantiation status.

8. The method as claimed in claim 1, wherein the one or more processors (406), establishes the first connection between the life cycle manager (204) and the POAM, and the second connection between the POAM and the PEEGN (206) in order to determine availability of at least one policy and one or more reserve resources at the PEEGN (206) based on the user request.

9. A system (125) for dynamically managing Container Network Function (CNF) resources, the system comprising:
a connecting module (408) configured to:
establish, a first connection between a life cycle manager of a CNF (204) and a Platform Operations, Administration and Maintenance Manager (POAM); and
establish, a second connection between the POAM and a Policy Execution Engine (PEEGN) (206);
a checking module (410) configured to determine availability of at least one policy and reserve resources at the PEEGN (206) based on a user request utilizing the first connection and the second connection;
if determined availability of the policy and reserve resources at the PEEGN (206), a transceiver (414) configured to transmit a reservation request to a Physical Virtual Inventory Manager (PVIM) (302) to reserve resources; and
an instantiate module (412) configured to request an orchestrator adaptor (306) to instantiate the CNF.

10. The system as claimed in claim 9, wherein the checking module (410) that determines availability of at least one policy and reserve resources at the PEEGN, is configured to:
transmit, an availability request to the PEEGN (206) to check availability of the at least one policy and the reserve resources based on CNF details provided on a PE_CM interface module (214).

11. The system as claimed in claim 9, wherein a PE_CM interface (214) is provided between the life cycle manager (204) and the PEEGN (206) forming the first connection.

12. The system as claimed in claim 9, wherein the connecting module (408) is configured to:
enable an async event-based implementation to manage the PE_CM interface module (214) to function in a high availability mode in order to engage a next available life cycle manager (204) instance when a current life cycle manager (204) instance is down.

13. The system as claimed in claim 9, wherein the instantiate module (412) that requests the orchestrator adaptor (306) to instantiate the CNF, is configured to:
request for updating inventory at the PEEGN (206) pertaining to resources in use and reserved based on CNF instantiation response from the orchestrator adaptor (306), wherein the response comprises CNFC instantiation status; and
transmit a request to the PVIM (302) for inventory management based on the CNFC instantiation status.

14. A User Equipment (UE) (110), comprising:
one or more primary processors (502) communicatively coupled to one or more processors (406), the one or more primary processors (502) coupled with a memory (402), wherein said memory stores instructions which when executed by the one or more primary processors (502) causes the UE (110) to:
transmit, a user request to the one or more processors (406) pertaining to initiating a Container Network Function (CNF) operation, and
wherein the one or more processors (406) is configured to perform the steps as claimed in claim 1.