WO2025057229A1

WO2025057229A1 - System and method for managing resources for container network function (cnf) instantiation

Info

Publication number: WO2025057229A1
Application number: PCT/IN2024/051743
Authority: WO
Inventors: Aayush Bhatnagar; Ankit Murarka; Rizwan Ahmad; Kapil Gill; Arpit Jain; Shashank Bhushan; Jugal Kishore; Meenakshi Sarohi; Kumar Debashish; Supriya Kaushik DE; Gaurav Kumar; Kishan Sahu; Gaurav Saxena; Vinay Gayki; Mohit Bhanwria; Durgesh KUMAR; Rahul Kumar
Original assignee: Jio Platforms Ltd
Current assignee: Jio Platforms Ltd
Priority date: 2023-09-13
Filing date: 2024-09-13
Publication date: 2025-03-20
Anticipated expiration: 2026-03-13

Abstract

The present disclosure relates to a method to manage resources for CNF instantiation by processors (202) The method includes requesting a PVIM (406) to provide details of a plurality of hosts and resources available corresponding to each of the plurality of the host based on instantiation request. Further, the method includes receiving details of the plurality of hosts and the resources available corresponding to each of the plurality of the host from the PVIM. Further, the method includes selecting hosts from the plurality of hosts and the resources available with the respective hosts based on pre-defined policies for the instantiation of the CNFs. Further, the method includes transmitting a resource reservation request to the PVIM to reserve the hosts from the plurality of hosts and the resources available with the respective hosts for the instantiation of the CNF.

Description

SYSTEM AND METHOD FOR MANAGING RESOURCES FOR

CONTAINER NETWORK FUNCTION (CNF) INSTANTIATION

FIELD OF THE INVENTION

[0001] The present invention relates to the field of communication network management and, more specifically, to a system and a method for accessing and reserving resources from a network inventory via a dedicated interface to run a network function.

BACKGROUND OF THE INVENTION

[0002] A communication network comprises of many network elements which are configured to operate in specific manners to improve credibility of the communication network. The communication network incorporate inventories to safe-keep resources and mechanism to efficiently distribute resources to all Network Functions (NFs) in the communication network so as to process service requests in the communication network. Inventory Management (IM) service maintains the virtual inventory and limited physical inventory. The IM service maintains the relation between physical and virtual resources with respect to overlay to manage storage memory allocation. Also, it describes physical and virtual resources in view of different attributes (e.g., subscription status, version information, error logs or the like) using updates from external micro-service. Thus, the data accuracy of the inventory depends on the microservices which create, update, and delete the resources (e.g., network link, bandwidth, network node information or the like) and at the same time, the inventory updated an event with the IM service. Other services can query IM relations, attributes etc. using query Application Programming Interface (API) provided by the IM service.

[0003] To optimize network performance, new network function like container network functions (CNF) and/or container network function components (CNFC), virtual network function (VNF) and/or virtual network function components (VNFC) are incorporated by dedicated micro-services which are allocated with resources from inventory by an inventory manager (e.g., Physical and Virtual Resource Manager (PVIM)). The resource allocation requests sent by various NF micro-services are instigated to a Policy Execution Engine (PEEGN) which is configured to assess available resource in a selected region and reserve the resources for operational feasibility. The PEEGN provides an NFV (Network functions virtualization)-SDN (Software-Defined Networking) Platform functionality to support dynamic requirements of resource management and network service orchestration in the virtualized/containerized network. The PEEGN enriches the NFV-SDN Platform with automatic scaling and healing functionality of network components and services. The PEEGN is also configured to provide policies for resource, security, availability, and scalability.

[0004] Presently, there is no dedicated system having an interface which would enable the PEEGN to directly interact with the inventory manager. The PEEGN has to go through alternate communication pathway to obtain required information from inventory and request the inventory manger to reserve required resources which is time consuming. It may happen that during this time, the resource may be allocated to some other micro-service or network function within a time frame as there are multiple users sending requests for resources in the communication network. The PEEGN needs to access resource info quickly and accurately to perform required tasks.

[0005] Therefore, there is a requirement of a system with the dedicated interface enabling direct interaction in between the PEEGN and the inventory manager, to reserve required resource as per the task/request initiated and a method to perform the communication workflow.

[0006] There is a requirement of accessing real time resource data for successful execution of any future request commands and resource allocation. There is a need for an interface solely constructed for sending information and reserving resources from the inventory by the PEEGN for network-function instantiation or scaling request.

SUMMARY OF THE INVENTION

[0007] One or more embodiments of the present disclosure provide a system and a method to manage resources for Container Network Function (CNF) instantiation. [0008] In one aspect of the present invention, the method to manage resources for CNF instantiation is disclosed. The method includes receiving, by one or more processors, an instantiation request from a user for instantiation of one or more CNFs. The instantiation request includes information of the one or more CNFs which are required to be instantiated. Further, the method includes requesting, by the one or more processors, a Physical and Virtual Resource Manager (PVIM) to provide details of a plurality of hosts and one or more resources available corresponding to each of the plurality of the host based on the received instantiation request. Further, the method includes receiving, by the one or more processors, details of the plurality of hosts and one or more resources available corresponding to each of the plurality of the host from the PVIM. Further, the method includes selecting, by the one or more processors, one or more hosts from the plurality of hosts and the one or more resources available with the respective one or more hosts based on one or more pre-defined policies for the instantiation of the one or more CNFs. Further, the method includes transmitting, by the one or more processors, a resource reservation request to the PVIM to reserve the selected one or more hosts from the plurality of hosts and the one or more resources available with the respective one or more hosts for the instantiation of the CNF.

[0009] In an embodiment, the plurality of hosts includes at least one server. The plurality of resources include at least one of: a Central Processing Unit (CPU) and a Random Access Memory (RAM).

[0010] In an embodiment, selecting, one or more resources from the plurality of resources and one or more hosts from the plurality of hosts based on one or more predefined policies for the instantiation of the one or more CNFs, includes the step of filtering, by the one or more processors, the one or more resources from the plurality of resources and the one or more hosts from the plurality of hosts which are compatible with the one or more pre-defined policies.

[0011] In an embodiment, transmitting, a resource reservation request to the PVIM to reserve the selected one or more resources and the corresponding one or more hosts for the instantiation of the CNF, includes the step of receiving, a resource reservation acknowledgment from the PVIM, wherein the resource reservation acknowledgment pertains to the reserved one or more hosts from the plurality of hosts and the one or more resources available with the respective one or more hosts at the PVIM.

[0012] In an embodiment, the one or more hosts are locations where the CNF instantiation occurs utilizing the reserved one or more resources.

[0013] In an embodiment, the method includes the step of transmitting, by the one or more processors, an event request to a Container Network Function Life Cycle Manager (CNFLM) to indicate that the reserved one or more hosts are available for instantiation of the CNF. The CNFLM is a critical component in managing the deployment and operation of the CNFs, ensuring that the CNFs are instantiated efficiently, scaled appropriately, updated smoothly, and terminated safely, all while optimizing resource usage and maintaining service quality. The CNFLM ensures that the CNFs are allocated appropriate resources (such as CPU, memory, storage, and network bandwidth) from the communication network.

[0014] In an embodiment, the one or more processors communicate with the PVIM via a communication channel. In an embodiment, the communication channel is an interface between a PEEGN and the PVIM. In an embodiment, the interface is at least one of, an PVIM_PEEGN (IM_PE) interface.

[0015] In one aspect of the present invention, the system to manage resources for CNF instantiation is disclosed. The system includes a transceiver, a requesting unit and a selecting unit. The transceiver is configured to receive an instantiation request from a user for instantiation of one or more CNFs, wherein the instantiation request includes information of the one or more CNFs which are required to be instantiated. The requesting unit is configured to request a PVIM to provide details of a plurality of hosts and one or more resources available corresponding to each of the plurality of the hosts based on the received instantiation request. Further, the transceiver is configured to receive details of the plurality of hosts and the one or more resources available corresponding to each of the plurality of the hosts from the PVIM. The selecting unit is configured to select one or more hosts from the plurality of hosts and the one or more resources available with the respective one or more hosts based on one or more pre-defined policies for the instantiation of the one or more CNFs. Further, the transceiver is configured to transmit a resource reservation request to the PVIM to reserve the selected one or more hosts from the plurality of hosts and the one or more resources available with the respective one or more hosts for the instantiation of the CNF.

[0016] In one aspect of the present invention, a non-transitory computer-readable medium having stored thereon computer-readable instructions is disclosed. The computer-readable instructions cause the processor to receive an instantiation request from a user for instantiation of one or more CNFs. The instantiation request includes information of the one or more CNFs which are required to be instantiated. Further, the processor requests a PVIM to provide details of a plurality of hosts and one or more resources available corresponding to each of the plurality of the hosts based on the received instantiation request. Further, the processor receives details of the plurality of hosts and the one or more resources available corresponding to each of the plurality of the hosts from the PVIM. Further, the processor selects one or more hosts from the plurality of hosts and the one or more resources available with the respective one or more hosts based on one or more pre-defined policies for the instantiation of the one or more CNFs. Further, the processor transmits a resource reservation request to the PVIM to reserve the selected one or more hosts from the plurality of hosts and the one or more resources available with the respective one or more hosts for the instantiation of the CNF.

[0017] Other features and aspects of this invention will be apparent from the following description and the accompanying drawings. The features and advantages described in this summary and in the following detailed description are not all- inclusive, and particularly, many additional features and advantages will be apparent to one of ordinary skill in the relevant art, in view of the drawings, specification, and claims hereof. Moreover, it should be noted that the language used in the specification has been principally selected for readability and instructional purposes and may not have been selected to delineate or circumscribe the inventive subject matter, resort to the claims being necessary to determine such inventive subject matter.

BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Some drawings may indicate the components using block diagrams and may not represent the internal circuitry of each component. It will be appreciated by those skilled in the art that disclosure of such drawings includes disclosure of electrical components, electronic components or circuitry commonly used to implement such components.

[0019] FIG. 1 is an exemplary block diagram of an environment for managing resources for the CNF instantiation, according to various embodiments of the present disclosure.

[0020] FIG. 2 is a block diagram of a system of FIG. 1, according to various embodiments of the present disclosure.

[0021] FIG. 3 is an example schematic representation of the system of FIG. 1 in which various entities operations are explained, according to various embodiments of the present system. [0022] FIG. 4 illustrates system architecture for sending information and reserving resources from a PVIM by a dedicated interface (e.g., IM_PE interface), according to various embodiments of the present system.

[0023] FIG. 5 illustrates a workflow of an interaction in between the PVIM and a PEEGN micro-service via the IM_PE interface, according to various embodiments of the present system.

[0024] FIG. 6 illustrates an example flow diagram of a method for managing resources for the CNF instantiation, according to various embodiments of the present system

[0025] FIG. 7 illustrates a system architecture (e.g., MANO architecture) depicting an IM_PE interface operation, in accordance with an embodiment of the present invention.

[0026] FIG. 8 is an exemplary flow diagram illustrating the method for managing resources for the CNF instantiation, according to various embodiments of the present disclosure.

[0027] Further, skilled artisans will appreciate that elements in the drawings are illustrated for simplicity and may not have necessarily been drawn to scale. For example, the flow charts illustrate the method in terms of the most prominent steps involved to help to improve understanding of aspects of the present invention. Furthermore, in terms of the construction of the device, one or more components of the device may have been represented in the drawings by conventional symbols, and the drawings may show only those specific details that are pertinent to understanding the embodiments of the present invention so as not to obscure the drawings with details that will be readily apparent to those of ordinary skill in the art having benefit of the description herein.

[0028] The foregoing shall be more apparent from the following detailed description of the invention. DETAILED DESCRIPTION OF THE INVENTION

[0029] 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.

[0030] 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.

[0031] 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.

[0032] Before discussing example, embodiments in more detail, it is to be noted that the drawings are to be regarded as being schematic representations and elements that are not necessarily shown to scale. Rather, the various elements are represented such that their function and general purpose becomes apparent to a person skilled in the art. Any connection or coupling between functional blocks, devices, components, or other physical or functional units shown in the drawings or described herein may also be implemented by an indirect connection or coupling. A coupling between components may also be established over a wireless connection. Functional blocks may be implemented in hardware, firmware, software or a combination thereof.

[0033] Further, the flowcharts provided herein, describe the operations as sequential processes. Many of the operations may be performed in parallel, concurrently or simultaneously. In addition, the order of operations maybe re-arranged. The processes may be terminated when their operations are completed, but may also have additional steps not included in the figured. It should be noted, that in some alternative implementations, the functions/acts/ steps noted may occur out of the order noted in the figured. For example, two figures shown in succession may, in fact, be executed substantially concurrently, or may sometimes be executed in the reverse order, depending upon the functionality/acts involved.

[0034] Further, the terms first, second etc... may be used herein to describe various elements, components, regions, layers and/or sections, it should be understood that these elements, components, regions, layers and/or sections should not be limited by these terms. These terms are used only to distinguish one element, component, region, layer or section from another region, layer, or a section. Thus, a first element, component, region layer, or section discussed below could be termed a second element, component, region, layer, or section without departing form the scope of the example embodiments.

[0035] Spatial and functional relationships between elements (for example, between modules) are described using various terms, including “connected,” “engaged,” “interfaced,” and “coupled.” Unless explicitly described as being “direct,” when a relationship between first and second elements is described in the description below, that relationship encompasses a direct relationship where no other intervening elements are present between the first and second elements, and also an indirect relationship where one or more intervening elements are present (either spatially or functionally) between the first and second elements. In contrast, when an element is referred to as being "directly” connected, engaged, interfaced, or coupled to another element, there are no intervening elements present. Other words used to describe the relationship between elements should be interpreted in a like fashion (e.g., "between," versus "directly between," "adjacent," versus "directly adjacent," etc.).

[0036] The terminology used herein is for the purpose of describing particular example embodiments only and is not intended to be limiting. Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which example embodiments belong. It will be further understood that terms, e.g., those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

[0037] As used herein, the singular forms “a,” “an,” and “the,” are intended to include the plural forms as well, unless the context clearly indicates otherwise. As used herein, the terms “and/or” and “at least one of’ include any and all combinations of one or more of the associated listed items. It will be further understood that the terms “comprises,” “comprising,” “includes,” and/or “including,” when used herein, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

[0038] Unless specifically stated otherwise, or as is apparent from the description, terms such as “processing” or “computing” or “calculating” or “determining” of “displaying” or the like, refer to the action and processes of a computer system, or similar electronic computing device/hardware, that manipulates and transforms data represented as physical, electronic quantities within the computer system's registers and memories into other data similarly represented as physical quantities within the computer system memories or registers or other such information storage, transmission or display devices.

[0039] Various embodiments of the present invention provide a system and method to send and receive information to and from an inventory manger to reserve resources for instantiation or scaling of a VNF/VNFC or CNF/CNFC by means of a dedicated interface. This interface solves the problem of resource allocation to other services or duplicate -resource reservation, to provide the resource information as per the resource requirements, and also reserve the resources for instantiation purpose so the instantiation cannot be failed due to resource constrain.

[0040] The preferred embodiments of the present system and method also relates to a dedicated interface which serves the requirement to get all the server or host details where resources are available and to reserve the resource. The system activities and method steps are performed by using this interface. However, the invention is not to be limited to only these embodiments.

[0041] In the network, at a certain instance multiple requests are sent from multiple users to instantiate or scale a network function (e.g., VNF/VNFC/CNF/CNFC) via a micro-service which sends resource reservation requests to the PVIM. The network function related requests are first sent to PEEGN for policy match. If the policy match is found then, the PEEGN request for region data to assess server or host status for resource reservation requests. If a delay in communication between the PEEGN and the PVIM occurs then, the resource may be allocated to other concurrent requests and may lead to failure of the particular requests for instantiation or scaling.

[0042] To facilitate solution of this problem, in various embodiments of the present invention, discloses a system having a dedicated interface to facilitate the interaction in between the PEEGN and the PVIM and method thereof to access information from the inventory and reserve resources. [0043] FIG. 1 illustrates an exemplary block diagram of an environment (100) for managing resources for the CNF instantiation, according to various embodiments of the present disclosure. The environment (100) comprises a plurality of user equipment’s (UEs) (102-1, 102-2, ,102-n). The at least one UE (102-n) from the plurality of the UEs (102-1, 102-2, > 102-n) is configured to connect to a system (108) via a communication network (106). Hereafter, label for the plurality of UEs or one or more UEs is 102.

[0044] In accordance with yet another aspect of the exemplary embodiment, the plurality of UEs (102) may be a wireless device or a communication device that may be a part of the system (108). The wireless device or the UE (102) may include, but are not limited to, a handheld wireless communication device (e.g., a mobile phone, a smart phone, a phablet device, and so on), a wearable computer device (e.g., a headmounted display computer device, a head-mounted camera device, a wristwatch, a computer device, and so on), a laptop computer, a tablet computer, or another type of portable computer, a media playing device, a portable gaming system, and/or any other type of computer device with wireless communication or Voice Over Internet Protocol (VoIP) capabilities. In an embodiment, the UEs (102) may include, but are not limited to, any electrical, electronic, electro-mechanical or an equipment or a combination of one or more of the above devices such as 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, where the computing device may include one or more in-built or externally coupled accessories including, but not limited to, a visual aid device such as camera, audio aid, a microphone, a keyboard, input devices for receiving input from a user such as touch pad, touch enabled screen, electronic pen and the like. It may be appreciated that the UEs (102) may not be restricted to the mentioned devices and various other devices may be used. A person skilled in the art will appreciate that the plurality of UEs (102) may include a fixed landline, and a landline with assigned extension within the communication network (106). [0045] The communication network (106), may use one or more communication interfaces/protocols such as, for example, Voice Over Internet Protocol (VoIP), 802.11 (Wi-Fi), 802.15 (including Bluetooth™), 802.16 (Wi-Max), 802.22, Cellular standards such as Code Division Multiple Access (CDMA), CDMA2000, Wideband CDMA (WCDMA), Radio Frequency Identification (e.g., RFID), Infrared, laser, Near Field Magnetics, etc.

[0046] The communication network (106) includes, by way of example but not limitation, one or more of a wireless network, a wired network, an internet, an intranet, a public network, a private network, a packet- switched network, a circuit-switched network, an ad hoc network, an infrastructure network, a Public-Switched Telephone Network (PSTN), a cable network, a cellular network, a satellite network, a fiber optic network, or some combination thereof. The communication network (106) may include, but is not limited to, a Third Generation (3G) network, a Fourth Generation (4G) network, a Fifth Generation (5G) network, a Sixth Generation (6G) network, a New Radio (NR) network, a Narrow Band Internet of Things (NB-IoT) network, an Open Radio Access Network (O-RAN), and the like.

[0047] The communication network (106) may also include, by way of example but not limitation, at least a portion of one or more networks having one or more nodes that transmit, receive, forward, generate, buffer, store, route, switch, process, or a combination thereof, etc. one or more messages, packets, signals, waves, voltage or current levels, some combination thereof, or so forth. The communication network (106) may also include, by way of example but not limitation, one or more of a wireless network, a wired network, an internet, an intranet, a public network, a private network, a packet-switched network, a circuit-switched network, an ad hoc network, an infrastructure network, a Public-Switched Telephone Network (PSTN), a cable network, a cellular network, a satellite network, a fiber optic network, a VOIP or some combination thereof. [0048] One or more network elements can be, for example, but not limited to a base station that is located in the fixed or stationary part of the communication network (106). The base station may correspond to a remote radio head, a transmission point, an access point or access node, a macro cell, a small cell, a micro cell, a femto cell, a metro cell. The base station enables transmission of radio signals to the UE (102) or a mobile transceiver. Such a radio signal may comply with radio signals as, for example, standardized by a 3^rd Generation Partnership Project (3GPP) or, generally, in line with one or more of the above listed systems. Thus, a base station may correspond to a NodeB, an eNodeB, a Base Transceiver Station (BTS), an access point, a remote radio head, a transmission point, which may be further divided into a remote unit and a central unit. The 3GPP specifications cover cellular telecommunications technologies, including radio access, core network, and service capabilities, which provide a complete system description for mobile telecommunications.

[0049] The system (108) is communicatively coupled to a server (104) via the communication network (106). The server (104) can be, for example, but not limited to a standalone server, a server blade, a server rack, an application server, a bank of servers, a business telephony application server (BTAS), a server farm, a cloud server, an edge server, home server, a virtualized server, one or more processors executing code to function as a server, or the like. In an implementation, the server (104) may operate at various entities or a single entity (include, but is not limited to, a vendor side, a service provider side, a network operator side, a company side, an organization side, a university side, a lab facility side, a business enterprise side, a defense facility side, or any other facility) that provides service.

[0050] The environment (100) further includes the system (108) communicably coupled to the server (e.g., remote server or the like) (104) and each UE of the plurality of UEs (102) via the communication network (106). The remote server (104) is configured to execute the requests in the communication network (106). [0051] The system (108) is adapted to be embedded within the remote server (104) or is embedded as an individual entity. The system (108) is designed to provide a centralized and unified view of data and facilitate efficient business operations. The system (108) is authorized to access to update/create/delete one or more parameters of their relationship between the requests for the API service, which gets reflected in realtime independent of the complexity of network.

[0052] In another embodiment, the system (108) may include an enterprise provisioning server (for example), which may connect with the remote server (104). The enterprise provisioning server provides flexibility for enterprises, ecommerce, finance to update/create/delete information related to the requests for the API service in real time as per their business needs. A user with administrator rights can access and retrieve the requests for the API service and perform real-time analysis in the system (108).

[0053] The system (108) 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 business telephony application server (BTAS), 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 implementation, system (108) may operate at various entities or single entity (for example include, but is not limited to, a vendor side, service provider side, a network operator side, a company side, an organization side, a university side, a lab facility side, a business enterprise side, ecommerce side, finance side, a defense facility side, or any other facility) that provides service.

[0054] However, for the purpose of description, the system (108) is described as an integral part of the remote server (104), without deviating from the scope of the present disclosure. Operational and construction features of the system (108) will be explained in detail with respect to the following figures. [0055] FIG. 2 illustrates a block diagram of the system (108) provided for managing resources for the CNF instantiation, according to one or more embodiments of the present invention. As per the illustrated embodiment, the system (108) includes the one or more processors (202), the memory (204), an input/output interface unit (206), a display (208), an input device (210), and the database (214). Further the system (108) may comprise one or more processors (202). The one or more processors (202), hereinafter referred to as the processor (202) may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, single board computers, and/or any devices that manipulate signals based on operational instructions. As per the illustrated embodiment, the system (108) includes one processor. However, it is to be noted that the system (108) may include multiple processors as per the requirement and without deviating from the scope of the present disclosure.

[0056] An information related to the request related to the API service may be provided or stored in the memory (204) of the system (108). Among other capabilities, the processor (202) is configured to fetch and execute computer-readable instructions stored in the memory (204). The memory (204) may be configured to store one or more computer-readable instructions or routines in a non-transitory computer-readable storage medium, which may be fetched and executed to create or share data packets over a network service. The memory (204) may include any non-transitory storage device including, for example, volatile memory such as RAM, or non-volatile memory such as disk memory, EPROMs, FLASH memory, unalterable memory, and the like.

[0057] The memory (204) may comprise any non-transitory storage device including, for example, volatile memory such as Random- Access Memory (RAM), or non-volatile memory such as Electrically Erasable Programmable Read-only Memory (EPROM), flash memory, and the like. In an embodiment, the system (108) may include an interface(s). The interface(s) may comprise 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 interface(s) may facilitate communication for the system. The interface(s) may also provide a communication pathway for one or more components of the system. Examples of such components include, but are not limited to, processing unit/engine(s) and the database (214). The processing unit/engine(s) may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processing engine(s).

[0058] The information related to the requests related to the API service may further be configured to render on the user interface (206). The user interface (206) may include functionality similar to at least a portion of functionality implemented by one or more computer system interfaces such as those described herein and/or generally known to one having ordinary skill in the art. The user interface (206) may be rendered on the display (208), implemented using Liquid Crystal Display (LCD) display technology, Organic Light-Emitting Diode (OLED) display technology, and/or other types of conventional display technology. The display (208) may be integrated within the system (108) or connected externally. Further the input device(s) (210) may include, but not limited to, keyboard, buttons, scroll wheels, cursors, touchscreen sensors, audio command interfaces, magnetic strip reader, optical scanner, etc.

[0059] The database (214) may be communicably connected to the processor (202) and the memory (204). The database (214) may be configured to store and retrieve the request pertaining to features, or services or workflow of the system (108), access rights, attributes, approved list, and authentication data provided by an administrator. In another embodiment, the database (214) may be outside the system (108) and communicated through a wired medium and a wireless medium.

[0060] Further, the processor (202), in an embodiment, may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processor (202). In the examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the

Y1 processor (202) may be processor-executable instructions stored on a non-transitory machine-readable storage medium and the hardware for the processor (202) may comprise a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the memory (204) may store instructions that, when executed by the processing resource, implement the processor (202). In such examples, the system (108) may comprise the memory (204) storing the instructions and the processing resource to execute the instructions, or the memory (204) may be separate but accessible to the system (108) and the processing resource. In other examples, the processor (202) may be implemented by an electronic circuitry.

[0061] In order for the system (108) to manage the resources for the CNF instantiation, the processor (202) includes a transceiver (216), a requesting unit (218) and a selecting unit (220). The transceiver (216), the requesting unit (218) and the selecting unit (220) may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processor (202). In the examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processor (202) may be processorexecutable instructions stored on a non-transitory machine-readable storage medium and the hardware for the processor (202) may comprise a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the memory (204) may store instructions that, when executed by the processing resource, implement the processor. In such examples, the system (108) may comprise the memory (204) storing the instructions and the processing resource to execute the instructions, or the memory (204) may be separate but accessible to the system (108) and the processing resource. In other examples, the processor (202) may be implemented by the electronic circuitry.

[0062] In order for the system (108) to manage the resources for the CNF instantiation, the the transceiver (216), the requesting unit (218) and the selecting unit (220) are communicably coupled to each other. The transceiver (216) receives an instantiation request from a user (e.g., service provider, admin of the system (108), an operator or the like) for instantiation of one or more CNFs. The instantiation request includes information of the one or more CNFs which are required to be instantiated. In general, the instantiation request refers to the process of initiating and deploying one or more CNFs based on user input or system requirements. The instantiation request typically includes specifications and parameters necessary for setting up the CNFs, such as their configuration, resource requirements, and deployment details. Also, the instantiation request typically includes a function type, a version and a configuration parameter. The function type indicates a type of network function being deployed (e.g., firewall, load balancer, router or the like). The version indicates a version of the CNF software to be used. The configuration parameter indicates any specific settings or parameters required for the CNF, such as network configurations, operational modes, or feature toggles.

[0063] Based on the received instantiation request, the requesting unit (218) requests the PVIM (406) to provide details of a plurality of hosts and one or more resources available corresponding to each of the plurality of the hosts. The plurality of hosts include the at least one server (104). The one or more hosts are locations where the CNF instantiation occurs utilizing the reserved one or more resources. The plurality of resources include at least one of CPU, a RAM, memory usage, bandwidth or the like. The transceiver (216) receives details of the plurality of hosts and the one or more resources available corresponding to each of the plurality of the hosts from the PVIM (406).

[0064] Further, the selecting unit (220) selects one or more hosts from the plurality of hosts and the one or more resources available with the respective one or more hosts based on one or more pre-defined policies for the instantiation of the one or more CNFs. In an embodiment, the selecting unit (218) filters the one or more hosts from the plurality of hosts and the one or more resources available with the respective one or more hosts which are compatible with the one or more pre-defined policies. The pre-defined policies refer to a set of rules or criteria established in advance to guide the selection and allocation of resources and hosts for deploying CNFs. These policies help ensure that resources are used efficiently and that network functions are deployed according to organizational requirements or operational standards. Also, the policies are set up before deployment and are used by systems to automate and standardize the deployment process, ensuring consistency and compliance with organizational or operational goals. The pre-defined policies may be, for example, but not limited to performance based policies, cost-based policies and availability-based policies.

[0065] The performance based policies allocate resources based on performance requirements (e.g., high-performance resources for critical CNFs). The cost-based policies select resources based on cost constraints or budget limits. The availabilitybased policies choose resources based on their availability and current usage to ensure high availability and reliability.

[0066] In the view of the compatibility, the hosts and resources are suitable for the CNF instantiation based on the following factors such as policy compliance, network requirements, security and compliance. In the resource requirements, the resources available on the host (e.g., CPU, memory) must meet or exceed the requirements specified by the CNF policies. For example, if a CNF requires 4 GB of memory and the host has 8 GB available, the host is considered compatible in terms of memory. For the network requirements, the host must be able to support network configurations required by the CNF. For instance, if the CNF requires specific network bandwidth or IP addresses, the host must be capable of providing these. For the security and compliance, the host must adhere to security and compliance policies such as data encryption, firewall settings, and access controls required by the CNF.

[0067] In short, the selecting unit (220) define the policies clearly. Further, the selecting unit (220) gathers the detailed host and resource data. Further, the selecting unit (220) evaluates each host against the policies. Further, the selecting unit (220) selects the hosts based on how well they meet the requirements. Further, the selecting unit (220) instantiate CNFs on the selected hosts. [0068] The transceiver (216) transmits a resource reservation request to the PVIM (406) to reserve the selected one or more hosts from the plurality of hosts and the one or more resources available with the respective one or more hosts for the instantiation of the CNF. The resource reservation request may include resource specifications and host specifications. The resource specifications indicate the type (e.g., CPU, memory, storage) and amount of resources required. The host specifications indicate information about the type of hosts (e.g., specific servers or virtual machines) and their geographic location or data center.

[0069] Further, the transceiver (216) receives a resource reservation acknowledgment from the PVIM (406). The resource reservation acknowledgment pertains to the reserved one or more hosts and the one or more resources available with the respective one or more hosts at the PVIM (406). Further, the transceiver (216) transmits an event request to a CNFLM (702f) to indicate that the reserved one or more hosts are available for instantiation of the CNF.

[0070] In an example, during instantiation, the IM_PE interface (408)provides the information for all the host for instantiation/scaling purpose where required resource is available. For example: suppose the CNFC needs the resource at the server like 56 GB or RAM, 32 CPU and 500 GB of volume, then host should comply this requirement where the CNFC needs to be instantiated. The PEEGN (402) sends an event for the resource request to the PVIM (406) for providing the resources as needed for the CNFC. Further, the PVIM (406) sends the event ack back as response to the PEEGN (402) with all the available host information where given resource is available for that instantiation flow. From the given resource, the PEEGN (402) selects the best suited hosts to instantiate the CNF and ask the PVIM (406) to reserve the resources on that server via a http event. The PVIM (406) reserves the resources on the given server by the PEEGN (402) and send the ack to the PEEGN (402) confirming that resources have been reserved. After that the PEEGN (402) asks the CNFLM to continue the instantiation process as now servers are ready for instantiation. [0071] The example for managing the resources for the CNF instantiation is explained in FIG. 4 to FIG. 6.

[0072] FIG. 3 is an example schematic representation of the system (300) of FIG. 1 in which various entities operations are explained, according to various embodiments of the present system. It is to be noted that the embodiment with respect to FIG. 3 will be explained with respect to the first UE (102-1) and the system (108) for the purpose of description and illustration and should nowhere be construed as limited to the scope of the present disclosure.

[0073] As mentioned earlier, the first UE (102-1) includes one or more primary processors (305) communicably coupled to the one or more processors (202) of the system (108). 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 UE (102-1). The execution of the stored instructions by the one or more primary processors (305) further enables the UE (102-1) to execute the requests in the communication network (106).

[0074] As mentioned earlier, the one or more processors (202) is configured to transmit a response content related to the API call request to the UE (102-1). More specifically, the one or more processors (202) of the system (108) is configured to transmit the response content to at least one of the UE (102-1). A kernel (315) is a core component serving as the primary interface between hardware components of the UE (102-1) and the system (108). The kernel (315) is configured to provide the plurality of response contents hosted on the system (108) to access resources available in the communication network (106). The resources include one of a Central Processing Unit (CPU), memory components such as Random Access Memory (RAM) and Read Only Memory (ROM). [0075] As per the illustrated embodiment, the system (108) includes the one or more processors (202), the memory (204), the input/output interface unit (206), the display (208), and the input device (210). The operations and functions of the one or more processors (202), the memory (204), the input/output interface unit (206), the display (208), and the input device (210) are already explained in FIG. 2. For the sake of brevity, we are not explaining the same operations (or repeated information) in the patent disclosure. Further, the processor (202) includes the transceiver (216), the requesting unit (218) and the selecting unit (220). The operations and functions of the transceiver (216), the requesting unit (218) and the selecting unit (220) are already explained in FIG. 2. For the sake of brevity, we are not explaining the same operations (or repeated information) in the patent disclosure.

[0076] FIG. 4 illustrates system architecture (400) for sending information and reserving resources from the PVIM (106) by a dedicated interface (e.g., IM_PE interface (408)), according to various embodiments of the present system. In an embodiment, a Policy execution engine (PEEGN) (402) communicates with the PVIM (406) via a communication channel. The communication channel is an interface between the PEEGN (402) and the PVIM (406). The interface is at least one of, PVIM_PEEGN (IM_PE) interface. In an embodiment, the IM_PE interface (408) is also called a policy execution interface. In an embodiment, the system architecture (400) includes the Policy execution engine (PEEGN) (402), the PVIM) (406), and an IM_PE interface (408) having an interaction module (not shown) and a resource reservation module (not shown). The PEEGN (402) analyzes the network function requests like instantiation or scaling requests to find a possible policy match. Then, The PEEGN (402) fetches the resources from inventory and regional server/host data, and reserves the resources for execution of requests. The IM_PE interface (408) enables the PEEGN (402) to send requests to the PVIM (406) for required details and receive information from the PVIM (406) via the interaction module. The IM_PE interface (408) reserves the resources for a selected region via the resource reservation module (not shown). The PVIM (406) is configured to manage and store all available data, the resource, and information in the communication network (106). The system architecture (400) may further include one or more database(s) (214) interacting with the PVIM (406) in a PVIM cluster (414). The IM_PE interface (408) is configured to enable direct interaction in between the PEEGN (402) and the PVIM (406) to gather required resources without any delay for smooth operation of micro-services.

[0077] The system architecture (400) is also capable of interacting with Network Function life cycle manager (NFLM), predefined centralized Platform Operations, Administration and Maintenance Manager (POAM) which provides available PVIM instance and load balancer details, servers and other network elements in the communication network (106). After confirming reservation of requests, the PEEGN (402) sends a response to the NFLM which instantiate or scales the CNF/VNF as required.

[0078] In an example, the user sends requests to the NFLM regarding the VNF/VNFC/CNF/CNFC instantiation or scaling. The NFLM sends a requests to the PEEGN (402) to check for a match for the VNF/VNFC/CNF/CNFC instantiation or scaling. If a match related to the request is found, then the PEEGN (402) asks the PVIM (406) to provide region details, dynamic memory details, CPU capacity details, server space or host resource dynamics. Upon receiving required information from PVIM (406), the PEEGN (402) selects the host region or server and asks the PVIM (406) to reserve the resource as per the request requirement. The PVIM (406) reserves the resources and send an acknowledgment back. The PEEGN (402) then prompts the NFLM to execute user requests. The PEEGN (402) reserves required resources in case other running instances may utilize the resource leading to failure of request execution and send a reservation confirmation to the NFLM. All the interaction in between the PEEGN (402) and the PVIM (406), and resource reservation process is performed by the IM_PE interface (408).

[0079] During instantiation, the IM_PE interface (408) provides the information for all the host for instantiation/scaling purpose where required resource is available. For example: suppose the CNFC needs the resource at the server like 56 GB or RAM, 32 CPU and 500 GB of volume, then host should comply this requirement where the CNFC needs to be instantiated. The PEEGN (402) sends an event for the resource request to the PVIM (406) for providing the resources as needed for the CNFC. Further, the PVIM (406) sends the event ack back as response to the PEEGN (402) with all the available host information where given resource is available for that instantiation flow. From the given resource, the PEEGN (402) selects the best suited hosts to instantiate the CNF and ask the PVIM (406) to reserve the resources on that server via a http event. The PVIM (406) reserves the resources on the given server by the PEEGN (402) and send the ack to the PEEGN (402) confirming that resources have been reserved. After that the PEEGN (402) asks the CNFLM to continue the instantiation process as now servers are ready for instantiation.

[0080] FIG. 5 illustrates an example workflow of an interaction in between the PVIM (406) and the PEEGN via the IM_PE interface (408), according to various embodiments of the present system. In preferred embodiment, the PVIM (406) and the PEEGN (402) as well as user are exchanging information via the IM_PE interface (408) which is receiving request from the PEEGN (402) and sending out the information from the PVIM (406), and reserve resources for network function instantiation or scaling requests.

[0081] In preferred embodiments, the system (108) and the method executed by the said system (108) by means of the PVIM (406) which may be based on Management and orchestration framework which is a teleco-cloud infrastructure interface, as a key element of the network functions virtualization (NFV) architecture. The PVIM (406) may coordinate network resources for cloud-based applications and manage any virtual network functions (VNFs) or container network function (CNF) and/or other network services. The PVIM (406) may be configured to interact with various APIs (application programming interface). [0082] For any operation, the system (108) may implement the API as a medium of communication to communicate with server(s) in the network (106). The system may operates and exchanges information in JSON (JavaScript Object Notation) format.

[0083] FIG. 6 illustrates an example flow diagram of a method for managing resources for the CNF instantiation, according to various embodiments of the present system

[0084] At 602, during instantiation, the IM_PE interface (408) provides the information for all the hosts for instantiation/scaling purpose where required resource is available. At 604, the PEEGN (402) sends the event to the PVIM (406) for providing the resources as needed for CNFC. At 606, the PVIM (406) sends the event ack as response to the PEEGN (402) with all the available host information where given resource is available for that instantiation flow.

[0085] At 608, from the given resource, the PEEGN (402) selects the best suited hosts to instantiate the CNF and ask the PVIM (406) to reserve the resources on that server via http event. At 610, the PVIM (406) reserves the resources on given server by PEEGN and send the ack to PEEGN (402) confirming that resources have been reserved. At 612, the PEEGN (402) asks CNFLM to continue the instantiation process as now servers are ready for instantiation.

[0086] FIG. 7 illustrates a system architecture (700) (e.g., MANO architecture) depicting an IM_PE interface operation, in accordance with an embodiment of the present invention. The system architecture (700) includes the user interface (206), a Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) design function module (702), a platform foundation service module (704), a platform core service module (706), and a platform resource adapter and utilities module (708).

[0087] The NFV and SDN design function module (702) is crucial for modernizing network infrastructure by enabling virtualized, scalable, and programmable network functions and management systems, particularly within the framework of CNFs. The platform foundation service module (704) refers to the underlying services and infrastructure components that support and enable the deployment, operation, and management of containerized network functions. The platform foundation service module (704) provides the essential capabilities and resources required for the CNF environment to function effectively.

[0088] The platform core service module (706) refers to the fundamental services and components that are essential for the core functionality and operation of containerized network functions. These services are critical for the effective deployment, execution, and management of CNFs, providing the necessary support and infrastructure for their operation. The platform resource adapter and utilities module (708) refers to a set of components and tools designed to manage and adapt various resources and services necessary for the operation of CNFs. The platform resource adapter and utilities module (708) plays a crucial role in integrating CNFs with underlying infrastructure and services, providing the necessary support for efficient operation, resource utilization, and interoperability.

[0089] The NFV and SDN design function module (702) includes a VNF lifecycle manger (702a), a VNF catalog (702b), a network service catalog (702c), a network slicing and service chaining manger (702d), a physical and virtual resource manager (702e), and a CNF lifecycle manager (702f).

[0090] The VNF lifecycle manager (702a) is responsible for managing the entire lifecycle of Virtual Network Functions (VNFs). The VNF lifecycle manager (702a) ensures that VNFs or CNFs are deployed, configured, monitored, scaled, and eventually decommissioned effectively. The VNF catalog (702b) (referred to as a CNF catalog) is a repository or registry that stores information about various containerized network functions and their configurations. The VNF catalog (702b) serves as a central reference for managing and deploying CNFs, providing details about their capabilities, requirements, and how they can be used within the network environment. The network service catalog (702c) is a comprehensive repository that organizes and manages the information related to network services composed of multiple CNFs or other network functions. The network service catalog (702c) serves as a central resource for defining, deploying, and managing these services within a containerized network environment. [0091] The network slicing and service chaining manger (702d) is a crucial component responsible for orchestrating and managing network slicing and service chaining functionalities. These functionalities are essential for efficiently utilizing network resources and delivering tailored network services in a dynamic and scalable manner. The physical and virtual resource manager (702e) is a critical component responsible for overseeing and managing both physical and virtual resources required to support the deployment, operation, and scaling of CNFs. The physical and virtual resource manager (702e) ensures that the necessary resources are allocated efficiently and effectively to meet the performance, availability, and scalability requirements of containerized network functions.

[0092] Further, the CNF lifecycle manager (702f) is a component responsible for overseeing the entire lifecycle of containerized network functions. This includes the management of CNFs from their initial deployment through ongoing operation and maintenance, up to their eventual decommissioning. The CNF lifecycle manager (702f) ensures that the CNFs are efficiently deployed, monitored, scaled, updated, and removed, facilitating the smooth operation of network services in a containerized environment.

[0093] The platform foundation service module (704) includes a microservice elastic load balancer (704a), an identity and access manager (704b), a command line interface (704c), a central logging manger (704d) and an event routing manger (704e). [0094] The microservice elastic load balancer (704a) is a specific type of load balancer designed to dynamically distribute network traffic across a set of microservices running in a containerized environment. Its primary purpose is to ensure efficient resource utilization, maintain high availability, and improve the performance of network services by evenly distributing incoming traffic among multiple instances of microservices. The identity and access manager (704b) is a critical component responsible for managing and securing access to containerized network functions and their resources. The identity and access manager (704b) ensures that only authorized users and systems can access specific resources, and it enforces policies related to identity verification, authentication, authorization, and auditing within the CNF ecosystem.

[0095] The central logging manger (704d) is a component responsible for aggregating, managing, and analyzing log data from various containerized network functions and associated infrastructure components. This centralized approach to logging ensures that logs are collected from disparate sources, consolidated into a single repository, and made accessible for monitoring, troubleshooting, and auditing purposes. The event routing manger (704e) is a component responsible for handling the distribution and routing of events and notifications generated by various parts of the CNF environment. This includes events related to system status, performance metrics, errors, and other operational or application-level events. The event routing manger (704e) ensures that these events are efficiently routed to the appropriate consumers, such as monitoring systems, alerting systems, or logging infrastructure, for further processing and action.

[0096] The platform core service module (706) includes an NFV infrastructure monitoring manager (706a), an assurance manager (706b), a performance manger (706c), the policy execution engine (402), a capacity monitoring manger (706e),a release management repository (706f), a configuration manger and GCT (706g), a NFV platform decision analytics unit (706h), a platform NoSQL DB (706i), a platform scheduler and Cron Jobs module (706j), a VNF backup & upgrade manger (706k), a micro service auditor (7061), and a platform operation, administration and maintenance manager (706m).

[0097] The NFV infrastructure monitoring manager (706a) monitors the underlying infrastructure of NFV environments, including computing, storage, and network resources. The NFV infrastructure monitoring manager (706a) provides real-time visibility into resource health, performance, and utilization. Further, the NFV infrastructure monitoring manager (706a) detects and alerts on infrastructure issues. Further, the NFV infrastructure monitoring manager (706a) integrates with monitoring tools to ensure reliable operation of CNFs. [0098] The assurance manager (706b) manages the quality and reliability of network services by ensuring compliance with service level agreements (SLAs) and operational standards. The performance manger (706c) optimizes the performance of CNFs by tracking and analyzing key performance indicators (KPIs). The policy execution engine (402) enforces and applies policies within the CNF environment to manage operations and access. Further, the policy execution engine (402) executes policies related to security, resource allocation, and service quality. Further, the policy execution engine (402) executes policies translates policy rules into actionable configurations and enforces compliance across CNFs.

[0099] The capacity monitoring manger (706e) monitors and manages the capacity of resources within the CNF environment to ensure optimal usage and avoid resource shortages. The release management repository (706f) stores and manages software releases, configurations, and versions of CNFs. Further, the release management repository (706f) keeps track of different versions of CNFs.

[00100] The configuration manger and Generic

Configuration Tool (GCT) (706g) manages the configuration of CNFs and related infrastructure components. The NFV platform decision analytics unit (706h) analyzes data from a NFV platform to support decision-making and strategic planning.

[00101] The platform NoSQL database (DB) (706i) is used for storing and managing large volumes of unstructured or semi-structured data within the CNF environment. The platform scheduler and Cron Jobs module (706j) manages scheduled tasks and periodic operations within the CNF environment. The VNF backup & upgrade manger (706k) oversees the backup and upgrade processes for Virtual Network Functions (VNFs) within the CNF environment.

[00102] The micro service auditor (7061) monitors and audits microservices to ensure compliance with operational and security standards. The platform operation, administration and maintenance manager (706m) manages the overall operation, administration, and maintenance of the CNF platform. [00103] The platform resource adapter and utilities module (708) includes a platform external API adaptor and gateway (708a), a generic decoder and indexer (708b), a swarm adaptor (708c), an opensatck API adaptor (708d) and a NFV gateway (708e).

[00104] The platform external API adaptor and gateway (708a) facilitates communication between the CNF platform and external systems or services by providing an interface for API interactions. The generic decoder and indexer (708b) decodes and indexes various types of data and logs within the CNF environment. The swarm adaptor (708c) facilitates communication between a swarm clusters and the CNF environment, including container deployment, scaling, and management.

[00105] The opensatck API adaptor (708d) provides an interface for the CNF platform to interact with OpenStack APIs, enabling operations such as provisioning, scaling, and managing virtual resources. The NFV gateway (708e) manages and facilitates communication between NFV (Network Functions Virtualization) components and external networks or services.

[00106] FIG. 8 is an exemplary flow diagram (800) illustrating the method for managing resources for the CNF instantiation, according to various embodiments of the present disclosure.

[00107] At 802, the method includes receiving the instantiation request from the user for instantiation of the one or more CNFs. The instantiation request includes information of the one or more CNFs which are required to be instantiated. In an embodiment, the method allows the transceiver (216) to receive the instantiation request from the user for instantiation of the one or more CNFs.

[00108] At 804, the method includes requesting the PVIM (406) to provide details of the plurality of hosts and the one or more resources available corresponding to each of the plurality of the hosts based on the received instantiation request. In an embodiment, the method allows the requesting unit (218) to request the PVIM (406) to provide details of the plurality of hosts and the one or more resources available corresponding to each of the plurality of the hosts based on the received instantiation request.

[00109] At 806, the method includes receiving the details of the plurality of hosts and the one or more resources available corresponding to each of the plurality of the hosts from the PVIM (406). In an embodiment, the method allows the transceiver (216) to receive the details of the plurality of hosts and the one or more resources available corresponding to each of the plurality of the hosts from the PVIM (406).

[00110] At 808, the method includes selecting the one or more hosts from the plurality of hosts and the one or more resources available with the respective one or more hosts based on one or more pre-defined policies for the instantiation of the one or more CNFs. In an embodiment, the method allows the selecting unit (220) to select the one or more hosts from the plurality of hosts and the one or more resources available with the respective one or more hosts based on one or more pre-defined policies for the instantiation of the one or more CNFs.

[00111] At 810, the method includes transmitting the resource reservation request to the PVIM (406) to reserve the selected one or more hosts from the plurality of hosts and the one or more resources available with the respective one or more hosts for the instantiation of the CNF. In an embodiment, the method allows the transceiver (216) to transmit the resource reservation request to the PVIM (406) to reserve the selected one or more hosts from the plurality of hosts and the one or more resources available with the respective one or more hosts for the instantiation of the CNF.

[00112] Below is the technical advancement of the present invention:

[00113] The proposed method minimizes error in the resource reservation-work flow. The proposed method provides accurate resource information for instantiation and scaling purposes. The proposed method reserves the resources for instantiation or scaling so that it should not fail due to resource constraints. The operation is less time consuming. The proposed method provides an async event-based implementation to utilize interface efficiently. The proposed method enables fault tolerance for any event failure, the IM_PE interface (408) works in a high availability mode and if one inventory instance went down during request processing then the next available instance will take care of this request.

[00114] Based on the proposed method, the IM_PE interface (408) works with the PEEGN (402) and the PVIM (406) to speed up resource data gathering and network resources reservation process for the server (104) or host selected by the PEEGN (402) leading to minimization of request failure. The IM_PE interface (408) follows neatly devised steps of the present method to facilitate direct interaction in between the PEEGN (402) and the PVIM (406) and thus improving network performance

[00115] A person of ordinary skill in the art will readily ascertain that the illustrated embodiments and steps in description and drawings (FIGS. 1-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.

[00116] Method steps: A person of ordinary skill in the art will readily ascertain that the illustrated steps 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.

[00117] 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

[00118] Environment - 100

[00119] UEs- 102, 102-1-102-n

[00120] Server - 104

[00121] Communication network - 106

[00122] System - 108

[00123] Processor - 202

[00124] Memory - 204

[00125] User Interface - 206

[00126] Display - 208

[00127] Input device - 210

[00128] Database - 214

[00129] Transceiver- 216

[00130] Requesting unit- 218

[00131] Selecting unit - 220 [00132] System - 300

[00133] Primary processors -305

[00134] Memory- 310

[00135] Kernel- 315

[00136] Example system - 400

[00137] PEEGN - 402

[00138] PVIM cluster - 404

[00139] PVIM - 406

[00140] IM_PE interface - 408

[00141] System architecture - 700

[00142] NFV and SDN design function - 702

[00143] VNF lifecycle manger - 702a

[00144] VNF catalog - 702b

[00145] Network service catalog - 702c

[00146] Network slicing and service chaining manger - 702d

[00147] Physical and virtual resource manager - 702e

[00148] CNF lifecycle manger - 702f

[00149] Platform foundation service module - 704

[00150] Microservice elastic load balancer - 704a

[00151] identity and access manager - 704b

[00152] Command line interface - 704c

[00153] Central logging manger - 704d

[00154] Event routing manger - 704e [00155] platform core service module - 706

[00156] NFV infrastructure monitoring manager - 706a

[00157] Assurance manager - 706b

[00158] Performance manger - 706c

[00159] Capacity monitoring manger - 706e

[00160] Release management repository - 706f

[00161] Configuration manger and GCT - 706g

[00162] NFV platform decision analytics - 706h

[00163] Platform NoSQL DB - 706i

[00164] Platform scheduler and cron Jobs module - 706j

[00165] VNF backup & upgrade manger - 706k

[00166] Micro service auditor - 7061

[00167] Platform operation, administration and maintenance manager - 706m

[00168] Platform resource adapter and utilities module - 708

[00169] Platform External API adaptor and gateway - 708a

[00170] Generic decoder and indexer - 708b

[00171] Swarm adaptor 708c

[00172] Opensatck API adaptor - 708d

[00173] NFV gateway - 708e

Claims

CLAIMS: We Claim

1. A method to manage resources for Container Network Function (CNF) instantiation, the method comprising the steps of: receiving, by one or more processors (202), an instantiation request from a user for instantiation of one or more CNFs, wherein the instantiation request includes information of the one or more CNFs which are required to be instantiated; requesting, by the one or more processors (202), a Physical and Virtual Resource Manager (PVIM) (406) to provide details of a plurality of hosts and one or more resources available corresponding to each of the plurality of the host based on the received instantiation request; receiving, by the one or more processors (202), details of the plurality of hosts and the one or more resources available corresponding to each of the plurality of hosts from the PVIM (406); selecting, by the one or more processors (202), one or more hosts from the plurality of hosts and the one or more resources available with the respective one or more hosts based on one or more pre-defined policies for the instantiation of the one or more CNFs; and transmitting, by the one or more processors (202), a resource reservation request to the PVIM (406) to reserve the selected one or more hosts and the one or more resources available with the respective one or more hosts for the instantiation of the CNF.

2. The method as claimed in claim 1 , wherein the plurality of hosts includes at least one of, a server (104), and the plurality of resources include at least one of, a Central Processing Unit (CPU) and a Random Access Memory (RAM).

3. The method as claimed in claim 1, wherein the step of, selecting, one or more resources from the plurality of resources and one or more hosts from the plurality of hosts based on one or more pre-defined policies for the instantiation of the one or more CNFs, includes the step of: filtering, by the one or more processors (202), the one or more resources from the plurality of resources and the one or more hosts from the plurality of hosts which are compatible with the one or more pre-defined policies.

4. The method as claimed in claim 1 , wherein the step of, transmitting, a resource reservation request to the PVIM (406) to reserve the selected one or more resources and the corresponding one or more hosts for the instantiation of the CNF, includes the step of: receiving, a resource reservation acknowledgment from the PVIM (406), wherein the resource reservation acknowledgment pertains to the reserved one or more hosts and the one or more resources available with the respective one or more hosts at the PVIM (406).

5. The method as claimed in claim 1, wherein the one or more hosts are locations where the CNF instantiation occurs utilizing the reserved one or more resources.

6. The method as claimed in claim 1, wherein the method further comprises the step of: transmitting, by the one or more processors (202), an event request to a Container Network Function Life Cycle Manager (CNFLM) to indicate that the reserved one or more hosts are available for instantiation of the CNF.

7. The method as claimed in claim 1, wherein the one or more processors (202) communicates with the PVIM (406) via a communication channel.

8. The method as claimed in claim 7, wherein the communication channel is an interface between a PEEGN and the PVIM (406).

. The method as claimed in claim 8, wherein the interface is at least one of, an PVIM_PEEGN (IM_PE) interface.

10. A system (108) to manage resources for Container Network Function (CNF) instantiation, the system (108) comprising: a transceiver (216), configured to, receive, an instantiation request from a user for instantiation of one or more CNFs, wherein the instantiation request includes information of the one or more CNFs which are required to be instantiated; a requesting unit (218), configured to, request, a Physical and Virtual Resource Manager (PVIM) (406) to provide details of a plurality of hosts and one or more resources available corresponding to each of the plurality of the hosts based on the received instantiation request; the transceiver (216), configured to, receive, details of the plurality of hosts and the one or more resources available corresponding to each of the plurality of hosts from the PVIM (406); a selecting unit (220), configured to, select, one or more hosts from the plurality of hosts and the one or more resources available with the respective one or more hosts based on one or more pre-defined policies for the instantiation of the one or more CNFs; and the transceiver (216), configured to, transmit, a resource reservation request to the PVIM (406) to reserve the selected one or more hosts and the one or more resources available with the respective one or more hosts for the instantiation of the CNF.

11. The system (108) as claimed in claim 10, wherein the plurality of hosts include at least one of, a server (104), and the plurality of resources include at least one of, a Central Processing Unit (CPU) and a Random Access Memory (RAM).

12. The system (108) as claimed in claim 10, wherein the selecting unit (220), select, one or more resources from the plurality of resources and one or more hosts from the plurality of hosts, by: filtering, the one or more resources from the plurality of resources and the one or more hosts from the plurality of hosts which are compatible with the one or more pre-defined policies.

13. The system (108) as claimed in claim 10, wherein the transceiver (216) is further configured to: receive, a resource reservation acknowledgment from the PVIM (406), wherein the resource reservation acknowledgment pertains to the reserved one or more hosts and the one or more resources available with the respective one or more hosts at the PVIM (406).

14. The system (108) as claimed in claim 10, wherein the one or more hosts are locations where the CNF instantiation occurs utilizing the reserved one or more resources.

15. The system (108) as claimed in claim 10, wherein the transceiver (216) is further configured to: transmit, an event request to a Container Network Function Life Cycle Manager (CNFLM) to indicate that the reserved one or more hosts are available for instantiation of the CNF.

16. The system (108) as claimed in claim 10, wherein the system (108) communicates with the PVIM (406) via a communication channel.

17. The system as claimed in claim 16, wherein the communication channel is an interface between a PEEGN and the PVIM (406).

18. The system as claimed in claim 17, wherein the interface is at least one of, an PVIM_PEEGN (IM_PE) interface.

19. A non-transitory computer-readable medium having stored thereon computer- readable instructions that, when executed by a processor (202), cause the processor (202) to: receive, an instantiation request from a user for instantiation of one or more CNFs, wherein the instantiation request includes information of the one or more CNFs which are required to be instantiated; request, a Physical and Virtual Resource Manager (PVIM) (406) to provide details of a plurality of hosts and one or more resources available corresponding to each of the plurality of the hosts based on the received instantiation request; receive, details of the plurality of hosts and the one or more resources available corresponding to each of the plurality of hosts from the PVIM (406); select, one or more hosts from the plurality of hosts and the one or more resources available with the respective one or more hosts based on one or more pre-defined policies for the instantiation of the one or more CNFs; and transmit, a resource reservation request to the PVIM (406) to reserve the selected one or more hosts and the one or more resources available with the respective one or more hosts for the instantiation of the CNF.

20. A User Equipment (UE) (102), comprising: one or more primary processors (305) communicatively coupled to one or more processors (202), the one or more primary processors (305) coupled with a memory (310), wherein said memory (310) stores instructions which when executed by the one or more primary processors causes the UE (102) to: transmit, an instantiation request, to the one or more processors (202), for instantiation of one or more CNFs; wherein the one or more processors (202) is configured to perform the steps as claimed in claim 1.