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 TO MANAGE RESOURCES FOR CONTAINER NETWORK FUNCTION (CNF) OPERATIONS

2. APPLICANT(S)
NAME NATIONALITY ADDRESS
JIO PLATFORMS LIMITED INDIAN OFFICE-101, SAFFRON, NR. CENTRE POINT, PANCHWATI 5 RASTA, AMBAWADI, AHMEDABAD 380006, GUJARAT, INDIA
3.PREAMBLE TO THE DESCRIPTION

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

FIELD OF THE INVENTION
[0001] The present invention relates to the field of communication network management and, more specifically, to a system and a method to manage resources for Container Network Function (CNF) operations.
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 incorporates inventories to safe-keep resources and mechanism to efficiently distribute resources to all NFs (Network Functions) in the communication network so as to process service requests. Inventory Management (IM) service maintains a virtual inventory and limited physical inventory. The IM maintains the relation between physical and virtual resources with respect to overlay to manage storage memory allocation. Also, the IM describes physical and virtual resources in view of different attributes using updates from an external microservice. The IM service maintains the virtual inventory and limited physical inventory. Thus, a data accuracy of the inventory depends on the micro-services which create, update, delete these resources and at the same time update these events with the IM. Other services can query IM relations, attributes etc. using Query APIs provided by the IM.
[0003] To optimize network performance, new network function like container network functions (CNF) and/or container network function components (CNFC) are incorporated and this is achieved by creating nodes by a container service module (e.g., swarm adapter (SA)). A micro service of the container service module is used for creating the containers on sites as a swarm service. The CNF are managed by a CNF life-cycle manager (CNFLM). The CNFLM sends a CNF request with CNFC details to the container service module. Every CNFC can be deployed on different sites as per request with at least one replication. When container runs successfully, an Agent Manager (AM) sends a response to the container service module per CNF and then the container service module sends a final response to the CNFLM.
[0004] However, after every CNF or CNFC related request like instantiation, scaling, termination or deletion etc. is processed the inventory data needs to be updated. Sometimes it may happen that a partial instantiation occurs where several CNFC of a CNF are not successfully instantiated. Every detail of CNF and CNFC must be updated in the inventory for proper system operation.
[0005] Hence, there is a requirement of synchronizing real time CNF-CNFC data with the stored data for successful execution of any future request commands and resource allocation. There is need of a system and a method therefore to update the data related to the CNF/CNFC after processing of each and every request related to the CNF-CNFC life cycle. There is a need for an interface solely constructed for updating the inventory by the CNF micro-service like CNFLM for any incurred changes in any CNF/CNFC.
SUMMARY OF THE INVENTION
[0006] One or more embodiments of the present disclosure provide a system and a method to manage resources for a Container Network Function (CNF) operation.
[0007] In one aspect of the present invention, the method to manage resources for the CNF operation is disclosed. The method includes receiving, by one or more processors, a CNF operation request from a user to perform the CNF operation. Further, the method includes identifying, by the one or more processors, a type of the CNF operation to perform the CNF operation based on the received CNF operation request. Further, the method includes determining one or more actions to be performed based on the identified type of the CNF operation. Further, the method includes transmitting, by the one or more processors, the CNF operation request to a container service module to perform the CNF operation based on the identified type of the CNF operation. Upon receiving an acknowledgment from the container service module pertaining to completion of the CNF operation, the method includes updating, by the one or more processors, a Physical and Virtual Resource Manager (PVIM) with a status of a resource in a network.
[0008] In an embodiment, the step of determining, one or more actions to be performed based on the identified type of the CNF operation includes the step of if the type of the CNF operation identified is a CNF instantiation, performing, by the one or more processors, the one or more actions of reserving one or more resources for performing the CNF instantiation based on transmitting a resource reservation request to a Policy Exchange Engine (PEEGN).
[0009] In an embodiment, the CNF operation request pertains to performing at least one of: the CNF instantiation, a CNF termination and a CNF deletion.
[0010] In an embodiment, the step of, transmitting, the CNF operation request to the container service module to perform the CNF operation includes the step of: if the type of the CNF operation identified is the CNF instantiation, transmitting, by the one or more processors, the CNF operation request along with details of the one or more resources reserved for the CNF instantiation.
[0011] In an embodiment, the step of, updating, the PVIM with a status of resources, includes at least one of the steps of: if the CNF operation completed is the CNF instantiation, updating, by the one or more processors, the status of the resource corresponding to the CNF as occupied. If the CNF operation completed is the CNF termination, the method includes updating, by the one or more processors, the status of the resource corresponding to the CNF as unoccupied. If the CNF operation completed is the CNF deletion, the method includes updating, by the one or more processors, the status of the resource corresponding to the CNF as unoccupied.
[0012] In an embodiment, the method further comprises the step of: if the CNF instantiation is partially completed, the method includes updating, by the one or more processors, the PVIM with the status of the resource as unoccupied when corresponding one or more Container Network Function Components (CNFCs) failed to instantiate.
[0013] In an embodiment, the one or more processors communicates with the inventory via a communication channel. In an embodiment, the communication channel is an interface between an inventory and a CNF lifecycle manager. In an embodiment, the interface is at least one of, an Inventory Manager _CNF lifecycle manager (IM_CM) interface.
[0014] In an embodiment, the method further comprises the step of transmitting, by the one or more processors, a CNF operation completion acknowledgement to a user subsequent to completion of the CNF operation.
[0015] In one aspect of the present invention, the system to manage resources for the CNF operation is disclosed. The system includes a transceiver, an identification unit, a determining unit and an updating unit. The transceiver is configured to receive a CNF operation request from a user to perform a CNF operation. The identification unit is configured to identify a type of the CNF operation to perform the CNF operation based on the received CNF operation request. The determining unit is configured to determine one or more actions to be performed based on the identified type of the CNF operation. Further, the transceiver is configured to transmit the CNF operation request to a container service module to perform the CNF operation based on the identified type of the CNF operation. Upon receiving an acknowledgment from the container service module pertaining to completion of the CNF operation, the updating unit is configured to update the PVIM with a status of the resource in a network.
[0016] In one aspect of the present invention, a non-transitory computer-readable medium having stored thereon computer-readable instructions is provided. The computer-readable instructions, when executed by a processor, cause the processor to receive a CNF operation request from a user to perform a CNF operation. Further, the processor identifies a type of the CNF operation to perform the CNF operation based on the received CNF operation request. Further, the processor determines one or more actions to be performed based on the identified type of the CNF operation. Further, the processor transmits the CNF operation request to a container service module to perform the CNF operation based on the identified type of the CNF operation. Upon receiving an acknowledgment from the container service module pertaining to completion of the CNF operation, the processor updates a PVIM with a status of the resource in a network.
[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 to manage resources for a CNF operation, 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 an example system to manage the resources for the CNF operations by a dedicated interface (e.g., IM_CM interface), and components of the system in accordance with some embodiments.
[0023] FIG. 5 illustrates a flow diagram of a method including the steps to update CNF/CNFC data in the inventory by the CNFLM after instantiation of a CNF-CNFC, synchronize live data with stored data in the inventory by the dedicated interface, and the components of the said system in accordance with some embodiments.
[0024] FIG. 6 illustrates a flow diagram of a method including the steps to update CNF/CNFC data in the inventory by CNFLM after termination of the CNF-CNFC, synchronize live data with stored data in inventory by the dedicated interface, and the components of the said system in accordance with some embodiments.
[0025] FIG. 7 illustrates a flow diagram of a method including the steps to update CNF/CNFC data in the inventory by CNFLM after deletion of a CNF-CNFC, synchronize live data with stored data in inventory by the dedicated interface, and the components of the said system in accordance with some embodiments.
[0026] FIG. 8 is an exemplary flow diagram illustrating the method for managing resources for the CNF operation, according to various embodiments of the present disclosure.
[0027] FIG. 9 illustrates an architecture framework (e.g., MANO architecture framework), in which the present invention can be implemented.
[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] Various embodiments of the present invention provide a system and method to update CNF/CNFC data after processing of every CNF-CNFC related requests, synchronize live data with stored data in inventory by means of a dedicated interface.
[0033] The present system and method also configured to relay requests initiated by user to various CNF based micro-services like CNF life cycle manager (CNFLM), and container service module (e.g., swarm adapter (SA) or the like), to process CNF instantiation, scaling, termination or deletion requests and to update and synchronize CNFC information in the inventory in a network to achieve optimum resource and data management without any discrepancy, possible down time or service disruption to minimize request failure cases due to data discrepancy. The system activities and method steps are performed by using the dedicated interface. However, the invention is not to be limited to only these embodiments. In an embodiment, the Container Network Function (CNF) refers to the network function that is deployed and operated within a containerized environment. The CNFLM is a specialized component within a network management and orchestration framework designed specifically to manage the lifecycle of CNFs. The container service module is a key component that facilitates the execution of various CNF operations. The container service module is responsible for executing CNF operations such as CNF instantiation, termination, and deletion.
[0034] The CNF/CNFC data update is important for request processing and resource distribution in a network. Any discrepancy in live CNF/CNFC data and stored data may lead to failure in CNF/CNFC instantiation or termination requests as the CNF-CNFC data changes each time CNFLM processes a request related to the CNF-CNFC. If the current CNF-CNFC data is not in sync with the inventory data then any related requests may fail.
[0035] FIG. 1 illustrates an exemplary block diagram of an environment (100) to manage resources for a CNF operation, 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.
[0036] 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 head-mounted 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).
[0037] 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.
[0038] 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.
[0039] 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. The 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.
[0040] 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 3rd 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.
[0041] 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.
[0042] 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).
[0043] 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 a CNF operation, which gets reflected in real-time independent of the complexity of network.
[0044] 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 CNF operation in real time as per their business needs. A user with administrator rights can access and retrieve the requests for the CNF operation and perform real-time analysis in the system (108).
[0045] 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.
[0046] 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.
[0047] FIG. 2 illustrates a block diagram of the system (108) provided for managing the resources for the CNF operation, 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.
[0048] An information related to the request related to the CNF operation 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.
[0049] 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).
[0050] The information related to the requests related to the CNF operation 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.
[0051] 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.
[0052] 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 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.
[0053] In order for the system (108) to manage the resources for the CNF operation, the processor (202) includes a transceiver (216), an identification unit (218), an updating unit (220) and a determining unit (222).
[0054] In order for the system (108) to manage resources for the CNF operation, the transceiver (216), the identification unit (218), the updating unit (220) and the determining unit (222) are communicably coupled to each other. In an embodiment, a communication channel (e.g., IM_CM interface (406) (as shown in FIG. 4)) is established between the system (106) and a PVIM (404) to send and receive data to manage a resource (for example, CPU, memory, storage, and network bandwidth or the like) for the CNF operation (e.g., CNF instantiation, CNF termination and CNF deletion). The IM_CM interface (406) relays the updates received from the CNFLM (402) to the PVIM (404). Also, the IM_CM interface (406) is configured to enable direct interaction between the CNFLM (402) and the PVIM (404) relating updates in the CNFC information. Also, the IM_CM interface (408) enables the CNFLM (402) to update the inventory about the status of the CNF and related CNFC even when partial instantiation occurs. The transceiver (216) receives a CNF operation request from a user (e.g., operator, admin of the system (108), service provider or the like) to perform the CNF operation. The CNF operation request includes an operation type, a metadata, a configuration, deployment detail, and a scaling information. In an example, the operation type indicates a request to deploy a new CNF or scale up an existing deployment. In an example, the operation type indicates request to stop or scale down a CNF. In an example, the operation type indicates request to completely remove a CNF and associated resources. The metadata includes a unique identifier for the CNF (e.g., name, ID), and a version of the CNF being deployed or updated. The configuration includes CPU, memory, and storage requirements for the CNF, network Configuration: Details on network settings, such as IP addresses, ports, and protocols and information about persistent storage or volumes required by the CNF. The scaling information includes policies for auto-scaling or manual scaling of CNF instances.
[0055] The identification unit (218) identifies a type of the CNF operation to perform the CNF operation based on the received CNF operation request. The type of the CNF operation can be, for example, but not limited to an instantiation type, a termination type, a deletion type and an update type. The instantiation type requests to deploy a new CNF or scale up the existing deployment. The termination type stops or scales down the CNF. The deletion type completely removes the CNF and associated resources. The update type modifies or updates the CNF configuration or image.
[0056] Further, the determining unit (222) determines one or more actions to be performed based on the identified type of the CNF operation. In an example, if the type of the CNF operation identified is the CNF instantiation, the determining unit (222) performs the one or more actions of reserving, one or more resources for performing the CNF instantiation based on transmitting a resource reservation request to a Policy Exchange Engine (PEEGN) (504). In an example, the CNFLM (402) sends the request to the PEEGN (506) for checking the CNF policy and reserve resources based on provided CNF details. If the policy is ok then, the PEEGN (506) sends the request to the PVIM (404) to reserve the resources. The resource reservation request reserves specific computational resources (such as CPU, memory, and storage) and/or networking resources (such as bandwidth and IP addresses) to support the deployment, execution, and operation of CNFs. This ensures that the required resources are available and allocated before or during the deployment of the CNF.
[0057] The transceiver (216) transmits the CNF operation request to the container service module (506) to perform the CNF operation based on the identified type of the CNF operation. In an embodiment, the transceiver (216) transmits the CNF operation request along with details (e.g., requestor details, usage context, and priority and QoS) of the resources reserved for the CNF instantiation, if the type of the CNF operation identified is the CNF instantiation. The requestor details indicates information about a service requesting the resources. The usage context indicates information about the CNF or application that will use the resources. The priority and quality-of-service (QoS) indicates any specified priorities or quality-of-service (QoS) requirements for the reservation.
[0058] Upon receiving an acknowledgment from the container service module (506) pertaining to completion of the CNF operation, the updating unit (220) updates the PVIM (404) with the status of the resources in the communication network (106).
[0059] In an embodiment, the updating unit (220) updates the status of the resources corresponding to the CNF as occupied if the CNF operation completed is the CNF instantiation. In other words, the updating unit (220) plays a crucial role in resource management by updating the status of resources to "occupied" once the CNF instantiation is complete. This ensures that the system (108) accurately reflects the current usage of resources and helps in managing resource availability effectively. The updating process involves monitoring CNF deployment status and making appropriate updates in resource tracking systems or databases.
[0060] In another embodiment, the updating unit (220) updates the status of the resources corresponding to the CNF as unoccupied if the CNF operation completed is the CNF termination. When the CNF termination operation is completed, the updating unit (220) updates the status of the resources associated with the CNF to "unoccupied." This ensures that resources previously used by the CNF are marked as available and ready for allocation to other CNFs or applications. The updating process involves detecting the termination of the CNF and making appropriate updates in the resource tracking system or database to reflect the new status of the resources.
[0061] In another embodiment, the updating unit (220) updates the status of the resources corresponding to the CNF as unoccupied if the CNF operation completed is the CNF deletion. If the CNF instantiation is partially completed, in an embodiment, the updating unit (220) updates the PVIM with the status of the resources as unoccupied when corresponding CNFCs failed to instantiate.
[0062] Further, the transceiver (216) transmits a CNF operation completion acknowledgement to a user subsequent to completion of the CNF operation. The CNF operation completion acknowledgement is a crucial part of CNF management, providing confirmation that a CNF operation has been completed. The CNF operation completion acknowledgement typically includes the type of operation, status, relevant details, and the method of notification. The CNF operation completion acknowledgement ensures that all parties involved are aware of the outcome and that the system accurately reflects the current state of the CNF and associated resources.
[0063] 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.
[0064] 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 first UE (102-1). The execution of the stored instructions by the one or more primary processors (305) further enables the first UE (102-1) to execute the requests in the communication network (106).
[0065] As mentioned earlier, the one or more processors (202) is configured to transmit a response content related to the CNF operation 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).
[0066] 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 identification unit (218), the updating unit (220) and the determining unit (222). The operations and functions of the transceiver (216), the identification unit (218), the updating unit (220) and the determining unit (222) 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.
[0067] FIG. 4 illustrates an example system (400) to manage the resources for the CNF operations by a dedicated interface (e.g., IM_CM interface) (406) (also called as the communication channel), in accordance with some embodiments. The CNFLM (402) manages to design, deployment, instantiation, scaling, termination and deletion of the CNF and related CNFCs. The container service module (506) (as shown in FIG. 5) creates hosts (508) (as shown in FIG. 5) for CNF request processing. The present system (108) is also capable of interacting with servers and other network elements, an Agent Manager (AM) (not shown), an NMS (network management system) (408) to obtain data, manage design, deployment, instantiation and termination of the CNF/CNFCs. The NMS refers to the overall system responsible for managing and orchestrating the CNF operations and resources within a network. The NMS ensures the efficient execution of CNF operations such as instantiation, termination, and deletion, while also keeping track of the network resources used by these CNFs. The AM ensures that the CNFs are efficiently managed, with appropriate resource allocation, lifecycle management, networking configuration, and monitoring. This helps in maintaining the performance and reliability of network services in the communication network (106). The IM_CM interface (406) relays the updates received from the CNFLM (402) to the PVIM (404). The PVIM (404) is configured to manage and store all available data, resource, and information in the network (106). The present system may further include one or more database(s) (214) interacting with the PVIM (404). In an embodiment, the system (108) communicates with the inventory via a communication channel. The communication channel is an interface between an inventory and a CNF lifecycle manager (402). In particular, the IM_CM interface (406) is configured to enable direct interaction between the CNFLM (402) and the PVIM (404) relating updates in the CNFC information.
[0068] In an example, when the user or the operator requests for make any changes to the CNF/CNFCs in the network (106) then the user interface (206) sends a Hypertext Transfer Protocol (HTTP) request to the CNFLM (402) to execute the request command and the CNFLM (402) then sends an event request to the PVIM (404) to update the details for that CNF/CNFC. The PVIM (404) updates the details and notifies the CNFLM (402). The CNFLM (402) then sends a confirmation to the user. The CNFLM (402) and the PVIM (404) communicate via the IM_CM interface (406). The IM_CM interface (406) between the CNFLM (402) and the PVIM (404) deals with problem related to inventory update. Further, the inventory gets updated via this interface (406). When the CNF deletion flow is successfully executed, the CNFLM (402) inform to the PVIM (404) via the IM_CM interface (406) to add used resources to the free pool. The update happens after the CNF instantiation, the CNF scaling, the CNF termination and the CNF deletion.
[0069] When the CNFLM (402) initiate managing certain CNF/CNFC then it connects with a predefined centralized Platform Operations, Administration and Maintenance Manager (POAM) (not shown). The POAM is configured to provide available CNFLM instance and Load balancer details. Similarly, when the PVIM (404) requires details of the instances, it connects with the POAM. The POAM will provide available PVIM instance and load balancer details. Further, the CNFLM (402) and the PVIM (404) are configured to interact with a MANO (management and orchestration) eco-system (not shown) to work together and the IM_CM interface (406) in configured to handle requests initiated by both CNFLM (402) and the PVIM (404). The user initiates CNF operations like instantiation, termination or deletion from the user interface (206) and prompts the CNFLM (402) to process the requests. The IM_CM interface (408) enables the CNFLM (402) to update the inventory about the status of the CNF and related CNFC even when partial instantiation occurs. The CNFLM micro service captures the details of vendors, CNFs and CNFCs via create, read, and update API’s exposed by the service. The captured details are stored in elastic search and can be further used by a micro service of the container service module. The CNFLM (402) is responsible for creating a CNF or individual CNFC instances. Also, it is responsible for Healing and Scaling out CNF’s or individual CNFC’s.
[0070] The user sends requests to the CNFLM (402) regarding the CNF-CNFC instantiation, scaling, termination or deletion. The CNFLM (402) sends the requests to a Policy execution engine (PEEGN) (504) to check for a match. If a match related to request is found, then the PEEGN (504) asks the PVIM (404) to provide regional details. Upon receiving required information from the PVIM (404), the PEEGN (504) 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 CNFLM (402). The CNFLM (402) then sends request to the container service module (506) to perform the activity by creating a host (508). After receiving confirmation from the container service module (506), the CNFLM (402) sends a completion message to user and sends a http request to the PVIM (404) to update the CNF-CNFC details by the IM_CM (406).
[0071] For any operation, the system (108) may implement API as a medium of communication to communicate with server(s) (104) in the network (106). The system (108) may operate and exchange information in JSON (JavaScript Object Notation) format.
[0072] In various embodiments, and as per FIG. 5 to FIG. 9 of the description, the method disclosed in the present invention may include various steps to execute user requests, relay request from the CNFLM (402) and interact with the inventory manager in the communication network (106) by means of the interface (406) to update CNF/CNFC data. The method further includes various steps to initiate the workflow of the interface to efficiently manage request commands from the CNFLM (402) to the PVIM (404). The method also includes the steps executed by the interface (406) to update CNF/CNFC data. The method includes, however not limited to, the below steps:
[0073] The CNF INSTANTIATION includes, however not limited to, the below steps:
a. Upon receiving a user command, the CNFLM (402) sends the request to the PEEGN (506) for checking the CNF policy and the reserve resources based on provided CNF details. If the policy is ok then the PEEGN (506) sends the request to the PVIM (404) to reserve the resources. The user command is an instruction or request issued by the user or an external system to perform a specific action related to the lifecycle or management of CNFs. These actions can include tasks such as deploying, scaling, updating, or deleting the CNFs.
b. Further, the CNFLM (402) requests the container service module (506) to instantiate CNF.
c. Based on the CNF Instantiation response from the container service module (506), this response has all CNFC Instantiation status based on this CNFLM prepare request for update inventory and using the IM_CM interface (406) sends request to the PVIM (404) for proper inventory management.
[0074] The CNF TERMINATION includes, however not limited to, the below steps:
a. The CNFLM (402) sends the CNF termination request to the container service module (506).
b. The container service module (506) performs the CNF termination operation and terminates all running CNFC’s of this CNF and sends back response to the CNFLM (402).
c. The CNFLM (402) checks the status of all CNFC and based on status creates an update inventory request.
d. The CNFLM (402) prepares the request for update inventory and using IM_CM interface (406) sends request to the PVIM (404) for proper inventory management.
[0075] The CNF DELETION includes, however not limited to, the below steps:
a. Using the IM_CM interface (406), the CNFLM (402) send the request to the PVIM (404) to check status of CNF and its CNFC.
b. The PVIM (404) checks the existing inventory and sends back CNF status in the response.
c. The CNFLM (402) checks the CNF and the associated CNFC’s status if all there is no active CNFC is available then the CNFLM (402) deletes all CNF related entries and informs all other micro-services to delete CNF details else return a negative response.
[0076] In preferred embodiments, the system (108) and method may be executed in a manner where for any operation, an application programming interface (API) is considered a medium of communication and every operation may be performed via http request, for communication between user and other network elements like server; information exchanges is performed in JSON format.
[0077] In preferred embodiments, the method may also include various steps to collect information from network elements like servers and other network functions, trigger consecutive operational procedures etc. and may not be considered strictly limited to the above steps.
[0078] FIG. 5 illustrates an operational flow diagram depicting a process (500) for performing the CNF instantiation, in accordance with an embodiment of the present invention.
[0079] At 502, the UI (206) performs the CNF instantiation. At 504, the UI (206) sends the CNF instantiation to the CNFLM (402). At 506, the CNFLM (402) sends the reserve resource and fetches the region details from the PEEGN (504). At 508, the PEEGN (504) sends a reservation acknowledgement (ACK) for the reserve resource and fetching the region details to the CNFLM (402).
[0080] At 510, the CNFLM (402) sends the instantiate CNF to the container service module (506). At 512, the container service module (506) forwarded the instantiate CNF to the host (508). At 514, the host (508) sends an instantiation status to the container service module (506). At 516, the container service module (506) sends the instantiation ACK to the CNFLM (402). At 518, the CNFLM (402) sends an update inventory to the PVIM (404). At 520, the PVIM (404) sends an update inventory ACK to the CNFLM (402). At 522, the CNFLM (402) sends an update instantiation status to a Resource Management and Reservation (RMR) (510). At 524, the RMR (510) sends the update instantiation status ACK to the CNFLM (402). At 526, the CNFLM (402) sends the CNF instantiation Ack to the UI (206).
[0081] FIG. 6 illustrates an operational flow diagram depicting a process (600) for performing a CNF termination flow, in accordance with an embodiment of the present invention. FIG. 6 illustrates a flow diagram of a method including the steps to update CNF/CNFC data in the inventory by the CNFLM (402) after termination of the CNF-CNFC, synchronize the live data with stored data in inventory by means of the dedicated interface (406), and the components of the said system in accordance with some embodiments.
[0082] At 602, the UI (206) initiates the CNF termination. At 604, the UI (206) sends the CNF termination to the CNFLM (402). At 606, the CNFLM (402) sends a terminates CNF to the container service module (506). At 608, the container service module (506) sends the terminated CNF to the host (508). At 610, the host (508) sends a termination status to the container service module (506). At 612, the container service module (506) sends a termination ACK to the CNFLM (402). At 614, the CNFLM (402) sends an update inventory to the PVIM (404). At 616, the PVIM (404) sends an update inventory ACK to the CNFLM (402). At 618, CNFLM (402) sends an update termination status to the RMR (510). At 620, the RMR (510) sends an update termination status ACK to the CNFLM (402). At 622, the CNFLM (402) sends the CNF termination Ack to the UI (206).
[0083] FIG. 7 illustrates a flow diagram (700) of a method including the steps to update CNF/CNFC data in the inventory by CNFLM after deletion of a CNF-CNFC, synchronize live data with stored data in inventory by the dedicated interface, and the components of the said system in accordance with some embodiments. FIG. 7 illustrates an operational flow diagram depicting a process (700) for performing a CNF deletion flow, in accordance with an embodiment of the present invention.
[0084] At 702, the UI (206) initiates the CNF deletion. At 704, the UI (206) sends the CNF deletion to the CNFLM (402). At 706, the CNFLM (402) checks the CNF status with the PVIM (404). At 708, the PVIM (404) sends a response to the CNF status to the CNFLM (402). At 710, the CNFLM (402) checks the CNF status and deletes the CNF. At 712, the CNFLM (402) notifies the CNF status to the PVIM (404). At 714, the PVIM (404) sends a response to the notification to the CNFLM (402). At 716, the CNFLM (402) notifies the CNF status to the container service module (506). At 718, the container service module (506) sends a response to the notification to the CNFLM (402). At 720, the CNFLM (402) notifies the CNF status to the RMR (510). At 722, the RMR (510) sends a response to the notification to the CNFLM (402). At 724, the CNFLM (402) sends CNF deletion Ack to the UI (206).
[0085] FIG. 8 is an exemplary flow diagram (800) illustrating the method for managing resources for the CNF operation, according to various embodiments of the present disclosure.
[0086] At 802, the method includes receiving the CNF operation request from the user to perform the CNF operation. The method allows the transceiver (216) to receive the CNF operation request from the user to perform the CNF operation.
[0087] At 804, the method includes identifying at least one type of the CNF operation to perform the CNF operation based on the received CNF operation request. The method allows the identification unit (218) to identify at least one type of the CNF operation to perform the CNF operation based on the received CNF operation request.
[0088] At 806, the method includes determining the one or more actions to be performed based on the identified type of the CNF operation. The method allows the determining unit (222) to determine the one or more actions to be performed based on the identified type of the CNF operation.
[0089] At 808, the method includes transmitting the CNF operation request to the container service module (506) to perform the CNF operation based on the identified type of the CNF operation. The method allows the transceiver (216) to transmit the CNF operation request to the container service module (506) to perform the CNF operation based on the identified type of the CNF operation.
[0090] Upon receiving the acknowledgment from the container service module (506) pertaining to completion of the CNF operation, at 810, the method includes updating the PVIM with a status of the resources in the network (106). Upon receiving the acknowledgment from the container service module (506) pertaining to completion of the CNF operation, the method allows the updating unit (220) to update the PVIM with the status of the resources in the network (106).
[0091] In preferred embodiments, the system and method executed by the said system by means of the inventory manager which may be based on Management and orchestration framework which is a telecom-cloud infrastructure interface, as a key element of the network functions virtualization (NFV) architecture. The inventory manager 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 inventory manager may be configured to interact with various APIs (application programming interface).

[0092] FIG. 9 illustrates an architecture framework 900 (e.g., MANO architecture framework), in which the present invention can be implemented. The system architecture (900) includes the user interface (206), a Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) design function module (902), a platform foundation service module (904), a platform core service module (906), and a platform resource adapter and utilities module (908).
[0093] The NFV and SDN design function module (902) 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 (904) 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 (904) provides the essential capabilities and resources required for the CNF environment to function effectively.
[0094] The platform core service module (906) 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 (908) 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 (908) plays a crucial role in integrating CNFs with underlying infrastructure and services, providing the necessary support for efficient operation, resource utilization, and interoperability.
[0095] The NFV and SDN design function module (902) includes a VNF lifecycle manger (902a), a VNF catalog (902b), a network service catalog (902c), a network slicing and service chaining manger (902d), a physical and virtual resource manager (902e), and a CNF lifecycle manager (902f).
[0096] The VNF lifecycle manager (902a) is responsible for managing the entire lifecycle of Virtual Network Functions (VNFs). The VNF lifecycle manager (902a) ensures that VNFs or CNFs are deployed, configured, monitored, scaled, and eventually decommissioned effectively. The VNF catalog (902b) (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 (902b) 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 (902c) 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 (902c) serves as a central resource for defining, deploying, and managing these services within a containerized network environment.
[0097] The network slicing and service chaining manger (902d) 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 (902e) 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 (902e) ensures that the necessary resources are allocated efficiently and effectively to meet the performance, availability, and scalability requirements of containerized network functions.
[0098] Further, the CNF lifecycle manager (902f) 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 (902f) ensures that the CNFs are efficiently deployed, monitored, scaled, updated, and removed, facilitating the smooth operation of network services in a containerized environment.
[0099] The platform foundation service module (904) includes a microservice elastic load balancer (904a), an identity and access manager (904b), a command line interface (904c), a central logging manger (904d) and an event routing manger (904e).
[00100] The microservice elastic load balancer (904a) 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 microservices refer to an architectural style where a network function is broken down into small, independently deployable services, each of which performs a specific function within the communication network (106). The identity and access manager (904b) is a critical component responsible for managing and securing access to containerized network functions and their resources. The identity and access manager (904b) 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.
[00101] The central logging manger (904d) 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 (904e) 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 (904e) 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.
[00102] The platform core service module (906) includes an NFV infrastructure monitoring manager (906a), an assurance manager (906b), a performance manger (906c), a policy execution engine (906d), a capacity monitoring manger (906e),a release management repository (906f), a configuration manger and GCT (906g), a NFV platform decision analytics unit (906h), a platform NoSQL DB (906i), a platform scheduler and Cron Jobs module (906j), a VNF backup & upgrade manger (906k), a micro service auditor (906l), and a platform operation, administration and maintenance manager (906m).
[00103] The NFV infrastructure monitoring manager (906a) monitors the underlying infrastructure of NFV environments, including computing, storage, and network resources. The NFV infrastructure monitoring manager (906a) provides real-time visibility into resource health, performance, and utilization. Further, the NFV infrastructure monitoring manager (906a) detects and alerts on infrastructure issues. Further, the NFV infrastructure monitoring manager (906a) integrates with monitoring tools to ensure reliable operation of CNFs.
[00104] The assurance manager (906b) manages the quality and reliability of network services by ensuring compliance with service level agreements (SLAs) and operational standards. The performance manger (906c) optimizes the performance of CNFs by tracking and analyzing key performance indicators (KPIs). The policy execution engine (906d) enforces and applies policies within the CNF environment to manage operations and access. Further, the policy execution engine (906d) executes policies related to security, resource allocation, and service quality. Further, the policy execution engine (906d) executes policies translates policy rules into actionable configurations and enforces compliance across CNFs.
[00105] The capacity monitoring manger (906e) monitors and manages the capacity of resources within the CNF environment to ensure optimal usage and avoid resource shortages. The release management repository (906f) stores and manages software releases, configurations, and versions of CNFs. Further, the release management repository (906f) keeps track of different versions of CNFs.
[00106] The configuration manger and Generic Configuration Tool (GCT) (906g) manages the configuration of CNFs and related infrastructure components. The NFV platform decision analytics unit (906h) analyzes data from a NFV platform to support decision-making and strategic planning.
[00107] The platform NoSQL database (DB) (906i) 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 (906j) manages scheduled tasks and periodic operations within the CNF environment. The VNF backup & upgrade manger (906k) oversees the backup and upgrade processes for Virtual Network Functions (VNFs) within the CNF environment.
[00108] The micro service auditor (906l) monitors and audits microservices to ensure compliance with operational and security standards. The platform operation, administration and maintenance manager (906m) manages the overall operation, administration, and maintenance of the CNF platform.
[00109] The platform resource adapter and utilities module (908) includes a platform external API adaptor and gateway (908a), a generic decoder and indexer (908b), a swarm adaptor (908c), an opensatck API adaptor (908d) and a NFV gateway (908e).
[00110] The platform external API adaptor and gateway (908a) facilitates communication between the CNF platform and external systems or services by providing an interface for API interactions. The generic decoder and indexer (908b) decodes and indexes various types of data and logs within the CNF environment. The swarm adaptor (908c) facilitates communication between a swarm clusters and the CNF environment, including container deployment, scaling, and management.
[00111] The opensatck API adaptor (908d) 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 (908e) manages and facilitates communication between NFV (Network Functions Virtualization) components and external networks or services.
[00112] Below is the technical advancement of the present invention:
[00113] The proposed method minimizes error in the update-work flow. The proposed method performs the accurate resource inventory update on CNF and CNFC instantiation process. The proposed method manages the resource inventory update during partial CNF instantiation, for example if there are 3 CNFC in a CNF and while instantiation 2 CNFC are get instantiated successfully and 1 CNFC instantiation failed then CNFLM inform these details to PVIM via the IM_CM interface so that reserved resources for failed CNFC get moved to free pool. The proposed method performs synchronization of real time CNF-CNFC data and the inventory data. The proposed method performs Synchronization of CNF-CNFC data generated due to any event at backend this and the data stored in the inventory so that overall working and service of MANO may not get impacted. The operation is less time consuming. When a CNF deletion flow is executed all resources that was used by CNF get moved to the free pool
[00114] The asynchronization event-based implementation in the CNFs leverages asynchronous, event-driven communication to manage interactions and operations within a containerized network function environment. This approach enhances system flexibility, scalability, and resilience by decoupling components and enabling them to operate independently through event generation, handling, and processing. It supports dynamic scaling, fault tolerance, and efficient communication across various CNF components and services. Async event-based implementation to utilize interface efficiently. The proposed method performs enables a fault tolerance for any event failure, this interface works in a high availability mode and if one inventory instance went down during request processing then next available instance will take care of this request.
[00115] After processing user request for instantiation, scaling, termination and deletion of the CNF /CNFC the details need to be updates in the inventory so that the resources are properly freed up and any upcoming request may not experience failure. The CNF_CNFC related requests are processed by CNF life cycle manager (CNF_LM) services and the present system provides a CNF manger interface to enable direct communication in between the CNFLM and inventory manager in order to facilitate update without time delay and thus improving efficiency of resource management. The interface follows the steps of the present method and provides an efficient CNF-CNFC details update after each instantiation, partial instantiation, scaling, termination and deletion, and thus improving network performance.
[00116] A person of ordinary skill in the art will readily ascertain that the illustrated embodiments and steps in description and drawings (FIGS. 1-10) 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] 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.
[00118] 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
[00119] Environment - 100
[00120] UEs– 102, 102-1-102-n
[00121] Server - 104
[00122] Communication network – 106
[00123] System – 108
[00124] Processor – 202
[00125] Memory – 204
[00126] User Interface – 206
[00127] Display – 208
[00128] Input device – 210
[00129] Database – 214
[00130] Transceiver - 216
[00131] Identification unit – 218
[00132] Updating unit – 220
[00133] Determining unit - 222
[00134] System - 300
[00135] Primary processors -305
[00136] Memory– 310
[00137] Kernel– 315
[00138] Example system – 400
[00139] CNFLM – 402
[00140] PVIM – 404
[00141] IM_CM interface – 406
[00142] NMS – 408
[00143] PEEGN – 504
[00144] Container service module – 506
[00145] Host – 508
[00146] RMR - 510
[00147] System architecture – 900
[00148] NFV and SDN design function – 902
[00149] VNF lifecycle manger - 902a
[00150] VNF catalog - 902b
[00151] Network service catalog - 902c
[00152] Network slicing and service chaining manger - 902d
[00153] Physical and virtual resource manager - 902e
[00154] CNF lifecycle manger - 902f
[00155] Platform foundation service module - 904
[00156] Microservice elastic load balancer - 904a
[00157] Identity and access manager - 904b
[00158] Command line interface - 904c
[00159] Central logging manger - 904d
[00160] Event routing manger - 904e
[00161] Platform core service module – 906
[00162] NFV infrastructure monitoring manager - 906a
[00163] Assurance manager - 906b
[00164] Performance manger - 906c
[00165] Policy execution engine - 906d
[00166] Capacity monitoring manger - 906e
[00167] Release management repository - 906f
[00168] Configuration manger and GCT - 906g
[00169] NFV platform decision analytics - 906h
[00170] Platform NoSQL DB - 906i
[00171] Platform scheduler and cron Jobs module - 906j
[00172] VNF backup & upgrade manger - 906k
[00173] Micro service auditor - 906l
[00174] Platform operation, administration and maintenance manager - 906m
[00175] Platform resource adapter and utilities module – 908
[00176] Platform External API adaptor and gateway - 908a
[00177] Generic decoder and indexer - 908b
[00178] Swarm adaptor - 908c
[00179] Opensatck API adaptor - 908d
[00180] NFV gateway - 908e

,CLAIMS:CLAIMS
We Claim:
1. A method to manage resources for Container Network Function (CNF) operations, the method comprising the steps of:
receiving, by one or more processors (202), a CNF operation request from a user to perform the CNF operation;
identifying, by the one or more processors (202), at least one of, a type of the CNF operation to perform the CNF operation based on the received CNF operation request;
determining, by the one or more processors (202), one or more actions to be performed based on the identified type of the CNF operation;
transmitting, by the one or more processors (202), the CNF operation request to a container service module (506) to perform the CNF operation based on the identified type of the CNF operation; and
upon receiving an acknowledgment from the container service module (506) pertaining to completion of the CNF operation, updating, by the one or more processors (202), a Physical and Virtual Resource Manager (PVIM) (404) with a status of the one or more resources in a network (106).

2. The method as claimed in claim 1, wherein the step of, determining, one or more actions to be performed based on the identified type of the CNF operation, includes the step of:
if the type of the CNF operation identified is a CNF instantiation, performing, by the one or more processors (202), the one or more actions of reserving one or more resources for performing the CNF instantiation based on transmitting a resource reservation request to a Policy Exchange Engine (PEEGN) (504).

3. The method as claimed in claim 1, wherein the CNF operation request pertains to performing at least one of, the CNF instantiation, a CNF termination and a CNF deletion.

4. The method as claimed in claim 1, wherein the step of, transmitting, the CNF operation request to a container service module (506) to perform the CNF operation, includes the step of:
if the type of the CNF operation identified is the CNF instantiation, transmitting, by the one or more processors (202), the CNF operation request along with details of the one or more resources reserved for the CNF instantiation.

5. The method as claimed in claim 1, wherein the step of, updating, the Physical and Virtual Resource Manager (PVIM) (404) with the status of resources, includes at least one of the steps:
if the CNF operation completed is the CNF instantiation, updating, by the one or more processors (202), the status of one or more resources corresponding to the CNF as occupied;
if the CNF operation completed is the CNF termination, updating, by the one or more processors (202), the status of the one or more resources corresponding to the CNF as unoccupied; and
if the CNF operation completed is the CNF deletion, updating, by the one or more processors (202), the status of the one or more resources corresponding to the CNF as unoccupied.

6. The method as claimed in claim 1, wherein the method further comprises the step of:
if the CNF instantiation is partially completed, updating, by the one or more processors (202), the PVIM (404) with the status of the resources as unoccupied when corresponding one or more Container Network Function Components (CNFCs) failed to instantiate.

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

8. The method as claimed in claim 7, wherein the communication channel is an interface between an inventory and a CNF lifecycle manager (402).

9. The method as claimed in claim 8, wherein the interface is at least one of, an Inventory Manager _CNF lifecycle manager (IM_CM) interface.

10. The method as claimed in claim 1, wherein the method further comprises the step of:
transmitting, by the one or more processors (202), a CNF operation completion acknowledgement to a user subsequent to completion of the CNF operation.

11. A system (108) to manage resources for Container Network Function (CNF) operations, the system (108) comprising:
a transceiver (216), configured to, receive, a CNF operation request from a user to perform a CNF operation;
an identification unit (218), configured to, identify, at least one of, a type of the CNF operation to perform the CNF operation based on the received CNF operation request;
a determining unit (222), configured to, determine, one or more actions to be performed based on the identified type of the CNF operation;
the transceiver (216), configured to, transmit, the CNF operation request to a container service module (506) to perform the CNF operation based on the identified type of the CNF operation; and
upon receiving an acknowledgment from the container service module (506) pertaining to completion of the CNF operation, an updating unit (220), configured to, update, a Physical and Virtual Resource Manager (PVIM) (404) with a status of the resources in a network (106).

12. The system (108) as claimed in claim 11, wherein the determining unit (222), determines, one or more actions to be performed based on the identified type of the CNF operation, by:
if the type of the CNF operation identified is a CNF instantiation, performing the one or more actions of reserving, one or more resources for performing the CNF instantiation based on transmitting a resource reservation request to a Policy Exchange Engine (PEEGN) (504).

13. The system (108) as claimed in claim 11, wherein the CNF operation request pertains to performing at least one of, the CNF instantiation, a CNF termination and a CNF deletion.

14. The system (108) as claimed in claim 11, wherein the transceiver (216), is configured to, transmit, the CNF operation request to the container service module (506) to perform the CNF operation, by:
transmitting, the CNF operation request along with details of the one or more resources reserved for the CNF instantiation, if the type of the CNF operation identified is the CNF instantiation,

15. The system (108) as claimed in claim 11, wherein the updating unit (220) is configured to update, the PVIM (404) with status of the resources, by:
updating, the status of the resources corresponding to the CNF as occupied, if the CNF operation completed is the CNF instantiation,
updating, the status of the resources corresponding to the CNF as unoccupied, if the CNF operation completed is the CNF termination; and
updating, the status of the resources corresponding to the CNF as unoccupied, if the CNF operation completed is the CNF deletion.

16. The system (108) as claimed in claim 11, wherein the updating unit (220) is further configured to:
if the CNF instantiation is partially completed, update, the PVIM with the status of the resources as unoccupied when corresponding one or more Container Network Function Components (CNFCs) failed to instantiate.

17. The system (108) as claimed in claim 11, wherein the system communicates with the inventory via a communication channel.

18. The system (108) as claimed in claim 17, wherein the communication channel is an interface between an inventory and a CNF lifecycle manager (402).

19. The system (108) as claimed in claim 18, wherein the interface is at least one of, an Inventory Manager _CNF lifecycle manager (IM_CM) interface.

20. The system (108) as claimed in claim 11, wherein the transceiver (216) is further configured to:
transmit, a CNF operation completion acknowledgement to the user subsequent to completion of the CNF operation.

21. A User Equipment (UE) (102), comprising:
one or more primary processors (305) communicatively coupled to one or more processors (202) of a system (108), 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 (305) causes the UE (102-1) to:
transmit, a CNF operation request to the one or more processers (202);
wherein the one or more processors (202) is configured to perform the steps as claimed in claim 1.