WO2025057194A1 - System and method for handling inventory operation - Google Patents

Abstract

The present disclosure relates to a method for handling an inventory operation by one or more processors (202) The method includes initiating at least one Container Network Function (CNF) operation. Further, the method includes updating one or more available resources at a PVIM subsequent to completion of the at least one CNF operation via a user interface. Further, the method includes adding the one or more available resources to an available pool by using the PVIM based on completion of the at least one CNF operation.

Description

SYSTEM AND METHOD FOR HANDLING INVENTORY OPERATION

FIELD OF THE INVENTION

[0001] The present invention relates to a method and a system for handling an inventory operation.

BACKGROUND OF THE INVENTION

[0002] Traditionally, in Container Network Function (CNF) management and orchestration, the management of physical and virtual resource inventory is the major challenge. There is always a concern with resource inventory while dealing with CNF operations such as instantiation, termination, or deletion of a CNFs or Container Network Function-Life Cycle (CNFC). There is always a possibility after each CNF operations resource inventory is not updated and there will be a mismatch in the inventory.

[0003] An IM_CM interface between a CNF life cycle manager (CNFLM) and a Physical & Virtual Resource Manager (PVIM) deals with problems related to inventory update. After every CNF operation resource inventory gets updated via the IM_CM interface. When CNF deletion flow is successfully executed, the CNFLM informs the PVIM via the IM_CM interface to add the used resources to a free pool. [0004] There is a need to overcome the above mentioned drawbacks.

SUMMARY OF THE INVENTION

[0005] One or more embodiments of the present disclosure provide a system and a method for handling an inventory operation.

[0006] In one aspect of the present invention, the method for handling the inventory operation is disclosed. The method includes initiating, by one or more processors, at least one Container Network Function (CNF) operation. Further, the method includes updating, by the one or more processors, one or more available resources at a Physical & Virtual Resource Manager (PVIM) subsequent to completion of the at least one CNF operation via a user interface. Further, the method includes adding, by the one or more processors, the one or more available resources to an available pool by using the PVIM based on completion of the at least one CNF operation.

[0007] In an embodiment, the CNF operation includes at least one of: a CNF instantiation, a CNF termination, and a CNF deletion.

[0008] In an embodiment, during the CNF instantiation, the method includes transmitting, by the one or more processors, a request to a Policy Execution Engine (PEEGN) to check availability of at least one CNF policy and one or more resources at the PEEGN. Further, the method includes transmitting, by the one or more processors, a reservation request to the PVIM to reserve the one or more resources if availability of the CNF policy and the resources are determined at the PEEGN. Further, the method includes requesting, by the one or more processors, a Swarm Adaptor (SA) to instantiate CNF via the user interface. Further, the method includes requesting, by the one or more processors, to update the inventory at the PVIM based on a CNF instantiation response received from the SA. The CNF instantiation response includes Container Network Function-Life Cycle (CNFC) instantiation status. The CNFC instantiation status represents a different phase of a deployment and operation of CNF instantiation.

[0009] In an embodiment, during the CNF termination, the method includes transmitting, by the one or more processors, a CNF termination request to a SA. Further, the method includes receiving, by the one or more processors, a response from the SA subsequent to performing a termination of running Container-Native Network Function Containers (CNFCs) of a specific CNF. The CNFCs represent a technique to deploy network functions within container network function environments. Further, the method includes checking, by the one or more processors, the status of CNFCs based on the response received from a swarm adaptor. Further, the method includes transmitting, by the one or more processors, an inventory management request to the PVIM via the user interface, subsequent to the creation of an update inventory request based on checking status of the CNFCs.

[0010] In an embodiment, the CNF deletion, further, the method includes transmitting, by the one or more processors, a request to the PVIM via the user interface. The request pertains to checking the status of the CNF and the respective CNFCs. Further, the method includes receiving, by the one or more processors, a response from the PVIM based on checking the existing inventory at the PVIM and the status of the CNF and the respective CNFCs. Further, the method includes determining, by the one or more processors, the status of each CNFC associated with the CNF. In response to determining absence of active CNFCs, the method includes deleting, by the one or more processors, CNF related entries and CNF details. In response to determining availability of active CNFCs, the method includes receiving, by the one or more processors, a negative response from the CNFCs.

[0011] In an embodiment, the user interface includes IM_CM interface.

[0012] In an embodiment, the IM_CM interface engages a next available Container Network Function-Life Cycle Manager (CNFLM) instance in a high availability mode when a current CNFLM instance is down.

[0013] In an embodiment, the available pool includes the one or more resources which are available to be utilized for a subsequent CNF operation.

[0014] In one aspect of the present invention, the system for handling the inventory operation is disclosed. The system includes an operation unit, an update unit and an instruction unit. The operation unit is configured to, initiate at least one CNF operation. Further, the update unit is configured to, update, one or more available resources at a PVIM subsequent to completion of the at least one CNF operation via a user interface. The instruction unit is configured to, add the one or more available resources to an available pool by using the PVIM based on completion of the at least one CNF operation. [0015] In one aspect of the present invention, a non-transitory computer-readable medium having stored thereon computer-readable instructions is provided. The non- transitory computer-readable medium causes the processor to initiate at least one CNF operation. Further, the processor updates one or more available resources at a PVIM subsequent to completion of the at least one CNF operation via a user interface. Further, the processor instructs to add the one or more available resources to an available pool by using the PVIM based on completion of the at least one CNF operation.

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

BRIEF DESCRIPTION OF THE DRAWINGS

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

[0018] FIG. 1 is an exemplary block diagram of an environment for handling an inventory operation, according to various embodiments of the present disclosure.

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

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

[0021] FIG. 4 illustrates an operational flow diagram depicting a process for performing a CNF instantiation flow, in accordance with an embodiment of the present invention.

[0022] FIG. 5 illustrates an operational flow diagram depicting a process for performing a CNF termination flow, in accordance with an embodiment of the present invention.

[0023] FIG. 6 illustrates an operational flow diagram depicting a process for performing a CNF deletion flow, in accordance with an embodiment of the present invention.

[0024] FIG. 7 illustrates an architecture framework (e.g., MANO architecture framework), in which the present invention can be implemented, in accordance with an embodiment of the present invention.

[0025] FIG. 8 illustrates an example diagram depicting operations of an IM_CM interface, in accordance with an embodiment of the present invention.

[0026] FIG. 9 illustrates a block diagram depicting an operations of the CNF, in accordance with an embodiment of the present invention. [0027] FIG. 10 is an exemplary flow diagram illustrating a method for handling the inventory operation, according to various embodiments of the present disclosure.

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

[0029] The foregoing shall be more apparent from the following detailed description of the invention.

DETAILED DESCRIPTION OF THE INVENTION

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

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

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

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

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

[0036] 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.).

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

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

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

[0040] The following glossary are used in the patent disclosure.

UI: User Interface

CNF: Container Network Function-Life

CNFC: Container Network Function-Life Cycle

PVIM: Physical & Virtual Resource Manager

POAM: Platform Operations, Administration and Maintenance Manager

CNFLM: Container Network Function-Life Cycle Manager

PEEG: Policy Execution Engine SA: Swarm Adaptor

[0041] Various embodiments of the invention provide an IM_CM interface for handling a CNF inventory operation. Following are key steps working points for proper inventory update via the IM_CM interface.

1. A CNFLM may connect with a predefined centralized Platform Operations, Administration and Maintenance Manager (POAM). The POAM may provide available CNFLM instance and Load balancer details.

2. A PVIM may connect with the predefined centralized POAM. The POAM will provide available PVIM instance and Load balancer details.

3. Further, the CNFLM and PVIM are available in a management, automation, and network orchestration (MANO) eco-system to work together and an IM_CM interface is open to handle a request in the network.

4. A user initiates CNF operations (e.g., CNF Instantiation, CNF Termination, CNF Deletion) from the UI.

CNF Instantiation

1. The CNFLM may send a request to a Policy Execution Engine (PEEGN) for checking a CNF policy and reserve resources based on provided CNF details. In an example, the CNFLM requests the PEEGN to validate that the CNF’s operational requirements and configurations align with predefined policies (e.g., security policies, performance policies, compliance policies or the like). In another example, the CNFLM requests the PEEGN to allocate necessary resources for the CNF based on the provided details, such as CPU, memory, storage, and network bandwidth. If the CNF policy is ok, the PEEGN send a request to a PVIM to reserve the resources (for example, CPU, memory, storage, and network bandwidth). In another example, the CNFLM receives a request to deploy a new container network function firewall, which includes details such as resource requirements, operational policies, and configuration parameters. The CNFLM sends a request to the Policy Execution Engine (PEEGN) to verify that the firewall’s configuration complies with organizational policies. This might include security policies (e.g., allowed protocols and ports), performance policies (e.g., minimum throughput requirements), and compliance policies (e.g., data handling regulations). Further, the CNFLM asks a Swarm Adaptor (SA) to instantiate the CNF.

2. Further, based on the CNF Instantiation response from the SA, this response has all CNFC Instantiation status based on this CNFLM prepare request for update inventory. By using IM_CM interface, the CNFLM sends a request to the PVIM for proper inventory management.

CNF Termination

1. The CNFLM sends a CNF termination request to the SA. The CNF Termination Request includes a CNF identifier, termination reason, a termination type, and data backup/retention requirements. The CNF identifier ensures that a correct CNF instance is targeted. The termination reason is a reason for terminating the CNF. This could be due to decommissioning, scaling down, policy enforcement, or failure. The termination type specifies whether the termination is a soft shutdown (graceful termination) or a hard shutdown (forceful termination), data backup/retention requirements are instructions related to backing up data or retaining logs before termination. This ensures that important data is not lost.

2. The SA performs a CNF termination operation and terminates all running CNFC’s of this CNF and sends a back response to the CNFLM. 3. The CNFLM checks the status of all CNFC and creates an update inventory request based on the status. In an example, when the CNFLM checks the status of all CNFCs, the CNFLM gathers information about their current state to ensure proper management, maintenance, and updates. Based on this status, the CNFLM creates an update inventory request to adjust configurations and apply updates as necessary. In another example, the CNFLM system sends requests to a management platform or APIs to retrieve the status of each CNFC. This includes checking whether the CNFCs are running, their performance metrics, and any issues reported. Based on the status information, the CNFLM identifies which CNFCs need updates or actions. For instance, if the CNFC is running with high CPU usage or reported issues, it may need a configuration adjustment or resource scaling. Then, the CNFLM submits the update inventory request to a relevant management system or platform for execution. The management system applies the requested updates to the CNFCs, such as adjusting resource limits or applying configuration changes.

4. The CNFLM prepares a request for update inventory and sends the request to the PVIM for proper inventory management using the IM_CM interface.

CNF Deletion

1. Using the IM_CM interface, the CNFLM sends a request to the PVIM to check status of the CNF and its CNFC. The PVIM checks the existing inventory and sends back the CNF status in response. The existing inventory refers to the comprehensive and current record of all CNFs and their associated resources that are managed by the PVIM. In an example, the existing inventory includes a current state of each CNF (e.g., running, stopped, degraded), details on allocated resources (e.g., CPU, memory, storage), information on performance such as CPU and memory usage, a current configuration settings of each CNF, and indicators of any issues or anomalies affecting the CNF.

2. The CNFLM checks the CNF and it’s all CNFC’s status, if all there is no active CNFC available then the CNFLM delete all CNFs related entries and inform all microservices to delete CNF details. 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. For example, in the CNF for a firewall, there might be separate microservices for intrusion detection, traffic filtering, and logging. The CNFLM returns a negative response.

[0042] FIG. 1 illustrates an exemplary block diagram of an environment (100) for handling an inventory 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.

[0043] 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).

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

[0045] 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. [0046] 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.

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

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

[0049] 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).

[0050] 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 inventory operation, which gets reflected in real-time independent of the complexity of network.

[0051] 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 inventory operation in real time as per their business needs. A user with administrator rights can access and retrieve the requests for the inventory operation and perform real-time analysis in the system (108).

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

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

[0054] FIG. 2 illustrates a block diagram of the system (108) provided for handling the inventory 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.

[0055] An information related to the inventory 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

Y1 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.

[0056] 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).

[0057] The information related to the inventory 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. [0058] 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.

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

[0060] In order for the system (108) to handle the inventory operation, the processor (202) includes an operation unit (216), an update unit (218), and an instruction unit (220). The operation unit (216), the update unit (218), and the instruction 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 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. 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.

[0061] In order for the system (108) to handle the inventory operation, the operation unit (216), the update unit (218), and the instruction unit (220) are communicably coupled to each other. The inventory operation refers to the processes involved in managing and maintaining an up-to-date record of all network functions, services, and their corresponding resources within the communication network (106). The inventory operation can be, for example, but not limited to a resource tracking operation, a service discovery operation, and a configuration management operation. The resource tracking operation Keeps an accurate record of all containerized network functions, their configurations, and the resources (such as CPU, memory, and storage) they consume. The service discovery operation identifies and catalogs the network functions and services available in the network. This includes monitoring their status, availability, and health. The configuration management operation manages the configurations of various CNFs to ensure they are up-to-date and consistent with the desired state. This can include updating configurations, applying patches, and managing versioning.

[0062] The operation unit (216) initiates a CNF operation. The CNF operation can be for example, but not limited to a CNF instantiation, a CNF termination, and a CNF deletion (explained above in detail). Further, the update unit (218) updates one or more available resources (e.g. memory, bandwidth or the like) at a PVIM (406) subsequent to completion of the at least one CNF operation via the user interface (206). The instruction unit (220) adds the one or more available resources to an available pool by using the PVIM (206) based on completion of the at least one CNF operation. In an example, when the CNF operation is completed (such as deployment, scaling, or termination), the instruction unit (220) may need to adjust resource allocations accordingly. This involves adding available resources to the resource pool managed by the PVIM (406). The available resources refer to the resources that are free or newly released from CNF operations (e.g., CPU, memory, storage) and are ready to be added to the pool for future use. In another example, after terminating the CNF, the instruction unit (220) instructs the PVIM (406) to add the released CPU, the memory, and the storage to the available pool. The PVIM (406) processes a command and updates the resource pool, making these resources available for future use. The available pool includes the one or more resources which are available to be utilized for a subsequent CNF operation.

[0063] During the CNF instantiation, the operation unit (216) transmits a request to a PEEGN (404) to check availability of at least one CNF policy and one or more resources at the PEEGN (404). If availability of the CNF policy and the resources is determined at the PEEGN (404), the operation unit (216) transmits a reservation request to the PVIM (406) to reserve the one or more resources. Further, the operation unit (216) requests a Swarm Adaptor (SA) (408) to instantiate CNF via the user interface (206). Further, the operation unit (216) requests to update the inventory at the PVIM (406) based on a CNF instantiation response received from the SA (408). The CNF instantiation response includes Container Network Function-Life Cycle (CNFC) instantiation status. The CNFC instantiation status represents a different phase of a deployment and operation of CNF instantiation. More detailed about the CNF instantiation is explained in FIG. 4.

[0064] During the CNF termination, the operation unit (216) transmits a CNF termination request to the SA (408). Further, the operation unit (216) receives a response from the SA subsequent to performing a termination of running CNFCs of a specific CNF, where the CNFCs represent a technique to deploy network functions within cloud-native environments. Further, the operation unit (216) checks status of CNFCs based on the response received from the SA (408). Further, the operation unit (216) transmits an inventory management request to the PVIM (406) via the user interface (206), subsequent to the creation of an update inventory request based on checking status of the CNFCs. More detailed information about the CNF termination is explained in FIG. 5.

[0065] During the CNF deletion, the operation unit (216) transmits a request to the PVIM (406) via the user interface (206). The request pertains to checking the status of the CNF and the respective CNFCs. Further, the operation unit (216) receives a response from the PVIM (406) based on checking the existing inventory at the PVIM (406) and the status of the CNF and the respective CNFCs. Further, the operation unit (216) determines the status of each CNFC associated with the CNF. in response to determining absence of active CNFCs, the operation unit (216) deletes the CNF related entries and CNF details. In response to determining availability of active CNFCs, the operation unit (216) receives a negative response from the CNFCs. More detailed information about the CNF deletion is explained in FIG. 6.

[0066] The user interface (206) (e.g., IM_CM interface or the like) engages a next available CNFLM instance in a high availability mode when a current CNFLM instance is down.

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

[0068] 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).

[0069] As mentioned earlier, the one or more processors (202) is configured to transmit a response content related to the inventory 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).

[0070] 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 operation unit (216), the update unit (218), and the instruction unit (220). The operations and functions of the the operation unit (216), the update unit (218), and the instruction 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.

[0071] FIG. 4 illustrates an operational flow diagram depicting a process (400) for performing the CNF instantiation, in accordance with an embodiment of the present invention. The process (400) may be performed by the system (108). The CNFLM (402) may send request to the PEEGN (404) for checking CNF policy and reserve resources based on the CNF details. If the policy is ok, the PEEGN (404) sends a request to the PVIM (406) to reserve the resources. Further, the CNFLM (402) asks the Swarm Adaptor (SA) (408) to instantiate the CNF.

[0072] Further, based on the CNF Instantiation response from the SA (408), the response has all CNFC Instantiation status. Based on the status, the CNFEM (402) prepares the request for update inventory and sends the request to the PVIM (406) for proper inventory management using the user interface (206).

[0073] For the detailed explanation: At 402, the UI (206) performs the CNF instantiation. At 404, the UI (206) sends the CNF instantiation to the CNFEM (402). At 406, the CNFLM (402) sends a reserve resource and fetch region details to the PEEGN (404). At 408, the PEEGN (404) sends a reservation acknowledgement (ACK) for the reserve resource and fetch region details to the CNFLM (402).

[0074] At 410, the CNFLM (402) sends the instantiate CNF to the SA (408). At 412, the SA (408) forwards the instantiate CNF to the host (410). At 414, the host (410) sends an instantiation status to the SA (408). At 416, the SA (408) sends the instantiation ACK to the CNFLM (402). At 418, the CNFLM (402) sends an update inventory to the PVIM 406. At 420, the PVIM (406) sends an update inventory ACK to the CNFLM (402). At 422, the CNFLM (402) sends an update instantiation status to a Resource Management and Reservation (RMR) (412). At 424, the RMR (412) sends the update instantiation status ACK to the CNFLM (402). At 426, the CNFLM (402) sends the CNF instantiation Ack to the UI (206).

[0075] FIG. 5 illustrates an operational flow diagram depicting a process (500) for performing a CNF termination flow, in accordance with an embodiment of the present invention. The process (500) may include sending by the CNFLM (402) to the SA (408), a CNF termination request. The process (500) may further include performing, by the SA (408), a CNF termination operation and terminating each running CNFC’s of the CNF. Further, a response is sent back to the CNFLM (402). The process (500) may include checking by the CNFLM status of each CNFC and based on status creating an update inventory request. The process (500) may include preparing CNFLM request for update inventory and using the UI (206), sending the request by the UI (206) to the PVIM (406) for proper inventory management.

[0076] For the detailed explanation: At 502, the UI (206) initiates the CNF termination. At 504, the UI (206) sends the CNF termination to the CNFLM (402). At 506, the CNFLM (402) sends a terminate CNF to the SA (408). At 508, the SA (408) sends the terminated CNF to the host (410). At 510, the host (410) sends a termination status to the SA (408). At 512, the SA (408) sends a termination ACK to the CNFLM (402). At 514, the CNFLM (402) sends an update inventory to the PVIM (406). At 516, the PVIM (406) sends an update inventory ACK to the CNFLM (402). At 518, CNFLM (402) sends an update termination status to the RMR 412. At 520, the RMR 412 sends an update termination status ACK to the CNFLM (402). At 522, the CNFLM (402) sends the CNF termination Ack to the UI (206).

[0077] FIG. 6 illustrates an operational flow diagram depicting a process (600) for performing a CNF deletion flow, in accordance with an embodiment of the present invention. By using the UI (206), the CNFLM (402) sends a request to the PVIM (406) to check status of the CNF and its CNFC. The PVIM (406) may check the existing inventory and send back CNF status in response. Further, the process (600) may include checking by CNFLM CNF and status of each CNFC associated with the CNF if there is no active CNFC available, the CNFLM (402) may delete all CNF related entries and inform all other microservices to delete CNF details. Else, a negative response is returned.

[0078] For the detailed explanation: At 602, the UI (206) initiates the CNF deletion. At 604, the UI (206) sends the CNF deletion to the CNFLM (402). At 606, the CNFLM (402) checks the CNF status with the PVIM (406). At 608, the PVIM (406) sends a response to the CNF status to the CNFLM (402). At 610, the CNFLM (402) checks the CNF status and deletes the CNF. At 612, the CNFLM (402) notifies the CNF status to the PVIM (406). At 614, the PVIM (406) sends a response to the notification to the CNFLM (402). At 616, the CNFLM (402) notifies the CNF status to the SA (408). At 618, the SA (408) sends a response to the notification to the CNFLM (402). At 620, the CNFLM (402) notifies the CNF status to the RMR (412). At 622, the RMR (412) sends a response to the notification to the CNFLM (402). At 624, the CNFLM (402) sends CNF deletion Ack to the UI (206).

[0079] FIG. 7 illustrates an architecture framework 700 (e.g., MANO architecture framework), in which the present invention can be implemented, in accordance with an embodiment of the present invention. The architecture framework (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).

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

[0081] 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) refer 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. [0082] 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).

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

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

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

[0086] 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).

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

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

[0089] The platform core service module (706) includes an NFV infrastructure monitoring manager (706a), an assurance manager (706b), a performance manger (706c), a policy execution engine (706d), 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).

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

[0091] 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 (706d) enforces and applies policies within the CNF environment to manage operations and access. Further, the policy execution engine (706d) executes policies related to security, resource allocation, and service quality. Further, the policy execution engine (706d) executes policies translates policy rules into actionable configurations and enforces compliance across CNFs.

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

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

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

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

[0096] 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).

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

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

[0099] FIG. 8 illustrates an example diagram (800) depicting an operations of an IM_CM interface (804), in accordance with an embodiment of the present invention. The user interface (206) is a rich UI from there user can initiate request. The IM_CM interface (804) between the CNF life cycle manager (CNFLM) (702f) and the PVIM (702e) deals with problem related to the inventory update. Actually, the container will be created using a swarm cluster, where the infrastructure is communicated with the CNFLM (702f) and the PVIM (702e). An NMS (802) stands for Network Management System that deals with FCAPS related operations. Here, the database (214) is a persistent database for all data and record keeping. The NMS (802) and the database (214) are communicated with the CNFLM (702f) and the PVIM (702e).

[00100] FIG. 9 illustrates a block diagram (900) depicting an operations of the CNF, in accordance with an embodiment of the present invention. The block diagram (900) may include the CNFLM (402), the UI (206), the SA (402A-402n), the PVIM (406), the PEEGN (404), and the swarm manager(s) (902a-902n). The CNFLM (402) is responsible for creating the CNF or individual CNFC instance. Also, the CNFLM (402) is responsible for scaling out the CNFs or individual CNFCs.

[00101] The CNFLM (402) captures the details of vendors, CNFs and CNFCs via create, read, and update API’s exposed by the service itself. The captured details are stored in the database (214) and can be further used by a SA service. From the UI (206), the CNFLM (402) gets the request to onboard/instantiate/terminate CNF instance. The CNFLM (402) may interact with the SA (408a-408n) to spawn appropriate CNF instances / CNFC instances. The service adapter SA (408a-408n) may directly connect to the host (410) of the swarm manager (902a-902n) to deploy an image to host nodes (not shown) that will connect to the swarm manager (902a- 902n) in workplace (Wl-Wn). The swarm manager (902a-902n) communicates with agent manger(s) (AM) (904a- 904n). The AM (904a- 904n) handles the real-time handling and optimization of containerized applications and services (e.g., automated scaling services, fault tolerance services or the like) within the network (106). The automated scaling services adjust the number of container instances based on current demand or resource utilization. The fault tolerance services ensures that containerized applications can recover from failures or disruptions without impacting overall service quality. In the call flow, the SA (408a-408n) may create swarm manager and add the hosts as swarm worker node. The SA (408a-408n) is deployed at region wise, and all CNF related operations are also happening region wise for every request CNFLM ask region related detail to the PEEGN (404). The ELB routes a request to region specific SA. The PVIM (406) will subscribe to CNFLM Ack event to get the status of instantiated CNF/CNFC and update its inventory mapping from reserved to use. The PEEGN (404) is involved during CNF instantiation flow to check for CNF INIT policy and to reserve resources required to instantiate CNF at the PVIM (406). The PEEGN (404) supports scaling policy for the CNFC. The swarm consists of multiple hosts which run in a swarm mode and act as managers (to manage membership and delegation) and workers (which run swarm services). A given host can be a manager, a worker or perform both roles. When a service is created, a user may want to define its optimal state (number of replicas, network and storage resources available to it, port the service exposes to the outside world, and more).

[00102] FIG. 10 is an exemplary flow diagram (1000) illustrating a method for handling the inventory operation, according to various embodiments of the present disclosure.

[00103] At 1002, the method includes initiating the at least one CNF operation. In an embodiment, the method allows the operation unit (216) to initiate the at least one CNF operation.

[00104] At 1004, the method includes updating one or more available resources at the PVIM (406) subsequent to completion of the at least one CNF operation via the user interface (206). In an embodiment, the method allows the update unit (218) to update the one or more available resources at the PVIM (406) subsequent to completion of the at least one CNF operation via the user interface (206). [00105] At 1006, the method includes adding the one or more available resources to the available pool by using the PVIM (406) based on completion of the at least one CNF operation. In an embodiment, the method allows the instruction unit (220) to add the one or more available resources to an available pool by using the PVIM (406) based on completion of the at least one CNF operation.

[00106] Below is the technical advancement of the present invention: a. Proper resource inventory update on CNF and CNFC instantiation process. b. Resource inventory update during partial CNF instantiation, for example 3 CNFC are present in a CNF and while instantiation 2 CNFC get instantiated successfully and 1 CNFC instantiation fails then, the CNFLM (402) informs these details to the PVIM (406) so that the reserved resources for failed CNFC get moved to free pool. c. During change management inventory is updated properly. d. When a CNF deletion flow executed all resources that was used by CNF get moved to the free pool.

[00107] The proposed method uses an asynchronization event-based implementation to utilize interface efficiently. 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. In the proposed method, the user interface (206) works in a high availability mode and if one CNFLM instance went down during request processing then next available instance may take care of the request. [00108] 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.

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

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

[00111] Environment - 100

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

[00113] Server - 104

[00114] Communication network - 106

[00115] System - 108

[00116] Processor - 202

[00117] Memory - 204

[00118] User Interface - 206

[00119] Display - 208

[00120] Input device - 210

[00121] Database - 214

[00122] Operation unit- 216

[00123] Update unit - 218

[00124] Instruction unit - 220

[00125] System - 300

[00126] Primary processors -305

[00127] Memory- 310

[00128] Kernel- 315

[00129] CNFLM - 402

[00130] PEEGN - 404

[00131] PVIM - 406

[00132] SA - 408 [00133] Host - 410

[00134] RMR - 412

[00135] system architecture - 700

[00136] NFV and SDN design function - 702

[00137] VNF lifecycle manger - 702a

[00138] VNF catalog - 702b

[00139] Network service catalog - 702c

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

[00141] Physical and virtual resource manager - 702e

[00142] CNF lifecycle manger - 702f

[00143] Platform foundation service module - 704

[00144] Microservice elastic load balancer - 704a

[00145] identity and access manager - 704b

[00146] Command line interface - 704c

[00147] Central logging manger - 704d

[00148] Event routing manger - 704e

[00149] platform core service module - 706

[00150] NFV infrastructure monitoring manager - 706a

[00151] Assurance manager - 706b

[00152] Performance manger - 706c

[00153] Policy execution engine - 706d

[00154] Capacity monitoring manger - 706e

[00155] Release management repository - 706f [00156] Configuration manger and GCT - 706g

[00157] NFV platform decision analytics - 706h

[00158] Platform NoSQL DB - 706i

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

[00160] VNF backup & upgrade manger - 706k

[00161] Micro service auditor - 7061

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

[00163] Platform resource adapter and utilities module - 708

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

[00165] Generic decoder and indexer - 708b

[00166] Swarm adaptor 708c

[00167] Opensatck API adaptor - 708d

[00168] NFV gateway - 708e

[00169] NMS - 802

[00170] Swarm manager(s) - 902a-902n

[00171] AM(s) - 904a-904n

Claims

CLAIMS: We Claim:

1. A method for handling an inventory operation, the method comprises the steps of: initiating, by one or more processors (202), at least one Container Network Function (CNF) operation; updating, by the one or more processors (202), one or more available resources at a Physical & Virtual Resource Manager (PVIM) (406) subsequent to completion of the at least one CNF operation via an user interface; and adding, by the one or more processors (202), the one or more available resources to an available pool by using the PVIM based on completion of the at least one CNF operation.

2. The method as claimed in claim 1 , wherein the CNF operation includes at least one of: a CNF instantiation, a CNF termination, and a CNF deletion.

3. The method as claimed in claim 2, wherein the CNF instantiation includes the steps of: transmitting, by the one or more processors (202), a request to a Policy Execution Engine (PEEGN) (404) to check availability of at least one CNF policy and one or more resources at the PEEGN (404); if availability of the CNF policy and the resources are determined at the PEEGN (404), transmitting, by the one or more processors (202), a reservation request to the PVIM (406) to reserve the one or more resources; requesting, by the one or more processors (202), a Swarm Adaptor (SA) (408) to instantiate CNF via the user interface (206); and requesting, by the one or more processors (202), to update the inventory at the PVIM (406) based on a CNF instantiation response received from the SA (408), wherein the CNF instantiation response comprises Container Network Function-Life Cycle (CNFC) instantiation status, wherein the CNFC instantiation status represents a different phase of a deployment and operation of CNF instantiation.

4. The method as claimed in claim 2, wherein the CNF termination includes the steps of: transmitting, by the one or more processors (202), a CNF termination request to the SA (408); receiving, by the one or more processors (202), a response from the SA (408) subsequent to performing a termination of running Cloud-Native Network Function Containers (CNFCs) of a specific CNF, wherein the CNFCs represent a technique to deploy network functions within cloud-native environments; checking, by the one or more processors (202), status of CNFCs based on the response received from the SA (408); and transmitting, by the one or more processors (202), an inventory management request to the PVIM (406) via the user interface (206) , subsequent to the creation of an update inventory request based on checking status of the CNFCs.

5. The method as claimed in claim 3, wherein the CNF deletion includes the steps of: transmitting, by the one or more processors (202), a request to the PVIM (406) via the user interface (206), wherein the request pertains to checking the status of the CNF and the respective CNFCs; receiving, by the one or more processors (202), a response from the PVIM (406) based on checking the existing inventory at the PVIM (406) and the status of the CNF and the respective CNFCs; determining, by the one or more processors (202), the status of each CNFC associated with the CNF; in response to determining absence of active CNFCs, deleting, by the one or more processors (202), the CNF related entries and the CNF details; and in response to determining availability of active CNFCs, receiving, by the one or more processors (202), a negative response from the CNFCs.

6. The method as claimed in claim 1, wherein the user interface (206) includes IM_CM interface (804).

7. The method as claimed in claim 6, wherein the IM_CM interface (804) engages a next available Container Network Function-Life Cycle Manager (CNFLM) instance in a high availability mode when a current CNFLM instance is down.

8. The method as claimed in claim 1, wherein the available pool includes the one or more resources which are available to be utilized for a subsequent CNF operation.

9. A system for handling an inventory operation, the system comprises: an operation unit (216), configured to, initiate, at least one Container Network Function (CNF) operation; an update unit (218), configured to, update, one or more available resources at a Physical & Virtual Resource Manager (PVIM) (406) subsequent to completion of the at least one CNF operation via an user interface (206); and an instruction unit (220), configured to, add the one or more available resources to an available pool by using the PVIM based on completion of the at least one CNF operation.

10. The system as claimed in claim 9, wherein the CNF operation includes at least one of: a CNF instantiation, a CNF termination, and a CNF deletion.

11. The system as claimed in claim 10, wherein the operation unit (216) performs the CNF instantiation, by: transmitting, a request to a Policy Execution Engine (PEEGN) (404) to check availability of at least one CNF policy and one or more resources at the PEEGN (404); if availability of the CNF policy and the resources is determined at the PEEGN (404), transmitting, a reservation request to the PVIM (406) to reserve the one or more resources; requesting, a Swarm Adaptor (SA) (408) to instantiate CNF via the user interface (206); and requesting, to update the inventory at the PVIM (406) based on a CNF instantiation response received from the SA (408), wherein the CNF instantiation response comprises Container Network Function-Life Cycle (CNFC) instantiation status, wherein the CNFC instantiation status represents a different phase of a deployment and operation of CNF instantiation,

12. The system as claimed in claim 10, wherein the operation unit (216) performs the CNF termination, by: transmitting, a CNF termination request to the SA (408); receiving, a response from the SA (408) subsequent to performing a termination of running Cloud-Native Network Function Containers (CNFCs) of a specific CNF, wherein the CNFCs represent a technique to deploy network functions within cloud-native environments; checking, status of CNFCs based on the response received from the SA (408); and transmitting, an inventory management request to the PVIM (406) via the user interface (206), subsequent to the creation of an update inventory request based on checking status of the CNFCs.

13. The system as claimed in claim 10, wherein the operation unit (216) performs the CNF deletion, by: transmitting, a request to the PVIM (406) via the user interface (206), wherein the request pertains to checking the status of the CNF and the respective CNFCs; receiving, a response from the PVIM (406) based on checking the existing inventory at the PVIM (406) and the status of the CNF and the respective CNFCs; determining, the status of each CNFC associated with the CNF; in response to determining absence of active CNFCs, deleting, CNF related entries and CNF details; and in response to determining availability of active CNFCs, receiving, a negative response from the CNFCs.

14. The system as claimed in claim 9, wherein the user interface (206) includes an IM_CM interface (804).

15. The system as claimed in claim 14, wherein the IM_CM interface (804) engages a next available Container Network Function-Life Cycle Manager (CNFLM) instance in a high availability mode when a current CNFLM instance is down.

16. The system as claimed in claim 9, wherein the available pool includes the one or more resources which are available to be utilized for a subsequent CNF operation.

17. A non-transitory computer-readable medium having stored thereon computer- readable instructions that, when executed by a processor (202), causes the processor (202) to: initiate, at least one Container Network Function (CNF) operation; update, one or more available resources at a Physical & Virtual Resource Manager (PVIM) subsequent to completion of the at least one CNF operation via a user interface; and instruct, to add the one or more available resources to an available pool by using the PVIM based on completion of the at least one CNF operation.