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

COMPLETE SPECIFICATION
(See section 10 and rule 13)
1. TITLE OF THE INVENTION
METHOD AND SYSTEM FOR MANAGING A CONTAINER NETWORK FUNCTION (CNF) OPERATION
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 an interface for a custom command Instantiation of CNF, more particularly the present invention relates to a system and a method for managing a Container Network Function (CNF) operation
BACKGROUND OF THE INVENTION
[0002] Traditionally, commands pertaining to Container Network Function Components (CNFC) help Network Function (NF) vendors to apply ready to move commands tested in their environment. This feature supports special requirement for NF which is not supported by legacy Network Functions Virtualization (NFV) systems.
[0003] The CNFC commands are often limited to pre-defined, tested configurations that are applied in a vendor's environment. While these legacy NFV systems support standard command sets, they fall short in accommodating the specialized requirements and dynamic nature of modern network functions.
[0004] In rapidly evolving network environments, such as those driven by 5G, vendors often face the challenge of deploying and configuring Network Functions (NFs) with unique or non-standard requirements that legacy NFV systems cannot address. These systems generally lack the flexibility needed to handle customized commands that adapt to the specific needs of new applications or services.
[0005] To address these limitations, there is a pressing need for a solution that supports custom command instantiation for CNFCs. Such a solution would enable vendors to deploy network functions that are not only tailored to their specific needs but also adaptable to emerging technologies and requirements. By overcoming the constraints of legacy systems, this approach facilitates more agile and efficient network management, allowing for better support of specialized services and dynamic network conditions. There is a need to overcome the above-mentioned drawbacks.
SUMMARY OF THE INVENTION
[0006] One or more embodiments of the present disclosure provide a method and system for managing a Container Network Function operation.
[0007] In one aspect of the present invention, the system for managing a Container Network Function (CNF) operation is disclosed. The system includes a transceiver unit configured to transmit a custom command operation request to an orchestrator adaptor over a first interface to initiate the CNF operation based on the custom command operation request received from a vendor. The system further includes an updating unit configured to update inventory at a Physical & Virtual Resource Manager (PVIM) pertaining to one or more resources in use and one or more resources reserved based on a CNF operation status response received from the orchestrator adaptor. The transceiver unit is further configured to transmit an inventory management request via a second interface to the PVIM to manage inventory based on the CNF operation status.
[0008] In an embodiment, the system includes prior to transmitting the custom command operation request to the orchestrator adaptor over the first interface to initiate the CNF operation, the transceiver unit is configured to transmit, the request to a Policy Execution Engine (PEEGN) to check availability of at least one CNF policy and one or more reserve resources at the PEEGN and receive an update of availability the at least one CNF policy and the one or more reserve resources from the PEEGN.
[0009] In an embodiment, the system includes a customization unit of the system configured to allow the vendor to customize the CNF operation based on the custom command operation request received from the vendor. The vendor is required to provide minimum information in order to customize the CNF operation.
[0010] In an embodiment, the custom command operation request relates to the vendor providing information to customize the CNF operation.
[0011] In an embodiment, the first interface is at least one of, an CM_OA interface and the second interface is at least one of, an IM_CM interface.
[0012] In an embodiment, the at least one CNF operation includes at least one of, a CNF instantiation, a CNF termination, and a CNF deletion utilizing the first interface.
[0013] In an embodiment, the transceiver is configured to receive the CNF operation status response from the orchestrator adaptor, upon the orchestrator adaptor checking for the status of the resources at the PVIM.
[0014] In an embodiment, the transceiver is further configured to receive an inventory management acknowledgement from the PVIM in response to the transmitted inventory management request.
[0015] In an embodiment, the CNF operation status comprises status of all Containerized Network Function Components (CNFC) instantiation status.
[0016] In another aspect of the present invention, the method for managing a Container Network Function operation is disclosed. The method includes the step of transmitting, by one or more processors, a custom command operation request to an orchestrator adaptor over a first interface to initiate the CNF operation based on the custom command operation request received from a vendor. The method further includes the step of updating inventory at a Physical & Virtual Resource Manager (PVIM) pertaining to one or more resources in use and one or more resources reserved based on a CNF operation status response received from the orchestrator adaptor. The method further includes the step of transmitting an inventory management request via a second interface to the PVIM to manage inventory based on the CNF operation status.
[0017] In another aspect of the invention, a non-transitory computer-readable medium having stored thereon computer-readable instructions is disclosed. The computer-readable instructions are executed by a processor. The processor is configured to transmit, a custom command operation request to an orchestrator adaptor over a first interface to initiate the CNF operation based on the custom command operation request received from a vendor. The processor is configured to update, inventory at a Physical & Virtual Resource Manager (PVIM) pertaining to one or more resources in use and one or more resources reserved based on a CNF operation status response received from the orchestrator adaptor. The processor is configured to transmit, an inventory management request via a second interface to the PVIM to manage inventory based on the CNF operation status.
[0018] In another aspect of the invention, a User Equipment (UE) is disclosed. The UE includes one or more primary processors communicatively coupled to one or more processors. The one or more primary processors are coupled with a memory. The primary processors cause the UE to transmit, a custom command operation request to the one or more processors pertaining to initiating a CNF operation.
[0019] 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
[0020] 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.
[0021] FIG. 1 is an exemplary block diagram of an environment for managing a Container Network Function (CNF) operation, according to one or more embodiments of the present invention;
[0022] FIG. 2 is an exemplary block diagram of a system for managing the CNF operation, according to one or more embodiments of the present invention;
[0023] FIG. 3 is a schematic representation of a workflow of the system of FIG. 1, according to the one or more embodiments of the present invention;
[0024] FIG. 4 is an exemplary block diagram of an architecture implemented in the system of the FIG. 2, according to one or more embodiments of the present invention;
[0025] FIG. 5 is a signal flow diagram for managing the CNF operation, according to one or more embodiments of the present invention; and
[0026] FIG. 6 is a schematic representation of a method for managing the CNF operation, according to one or more embodiments of the present invention.
[0027] 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.
[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] FIG. 1 illustrates an exemplary block diagram of an environment 100 for managing a Container Network Function (CNF) operation, according to one or more embodiments of the present disclosure. In this regard, the environment 100 includes a network 105 a User Equipment (UE) 110, a system 115, a server 120 communicably coupled to each other for processing data in the network 106.
[0033] As per the illustrated embodiment and for the purpose of description and illustration, the UE 110 includes, but not limited to, a first UE 110a, a second UE 110b, and a third UE 110c, and should nowhere be construed as limiting the scope of the present disclosure. In alternate embodiments, the UE 110 may include a plurality of UEs as per the requirement. For ease of reference, each of the first UE 110a, the second UE 110b, and the third UE 110c, will hereinafter be collectively and individually referred to as the “User Equipment (UE) 110”.
[0034] In an embodiment, the UE 110 is one of, but not limited to, any electrical, electronic, electro-mechanical or an equipment and a combination of one or more of the above devices such as a smartphone, virtual reality (VR) devices, augmented reality (AR) devices, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other computing device.
[0035] The environment 100 includes the server 120 accessible via the network 105. The server 120 may include, by way of example but not limitation, one or more of a standalone server, a server blade, a server rack, a bank of servers, a server farm, hardware supporting a part of a cloud service or system 115, a home server, hardware running a virtualized server, one or more processors executing code to function as a server, one or more machines performing server-side functionality as described herein, at least a portion of any of the above, some combination thereof. In an embodiment, the entity may include, but is not limited to, a vendor, a network operator, a company, an organization, a university, a lab facility, a business enterprise side, a defense facility side, or any other facility that provides service.
[0036] The network 105 includes, by way of example but not limitation, one or more of a wireless network, a wired network, an internet, an intranet, a public network, a private network, a packet-switched network, a circuit-switched network, an ad hoc network, an infrastructure network, a Public-Switched Telephone Network (PSTN), a cable network, a cellular network, a satellite network, a fiber optic network, or some combination thereof. The network 105 may include, but is not limited to, a Third Generation (3G), a Fourth Generation (4G), a Fifth Generation (5G), a Sixth Generation (6G), a New Radio (NR), a Narrow Band Internet of Things (NB-IoT), an Open Radio Access Network (O-RAN), and the like.
[0037] The network 105 may also include, by way of example but not limitation, at least a portion of one or more networks having one or more nodes that transmit, receive, forward, generate, buffer, store, route, switch, process, or a combination thereof, etc. one or more messages, packets, signals, waves, voltage or current levels, some combination thereof, or so forth. The network 105 may also include, by way of example but not limitation, one or more of a wireless network, a wired network, an internet, an intranet, a public network, a private network, a packet-switched network, a circuit-switched network, an ad hoc network, an infrastructure network, a Public-Switched Telephone Network (PSTN), a cable network, a cellular network, a satellite network, a fiber optic network, a VOIP or some combination thereof.
[0038] The environment 100 further includes the system 115 communicably coupled to the server 120 and the UE 110 via the network 105. The system 115 is configured for managing the CNF operation. As per one or more embodiments, the system 115 is adapted to be embedded within the server 120 or embedded as an individual entity.
[0039] Operational and construction features of the system 115 will be explained in detail with respect to the following figures.
[0040] FIG. 2 is an exemplary block diagram of the system 115 for managing the CNF operation, according to one or more embodiments of the present invention.
[0041] As per the illustrated embodiment, the system 115 includes one or more processors 200, a memory 205, a user interface 210, and a database 215. For the purpose of description and explanation, the description will be explained with respect to one processor 200 and should nowhere be construed as limiting the scope of the present disclosure. In alternate embodiments, the system 115 may include more than one processor 200 as per the requirement of the network 105. The one or more processors 200, hereinafter referred to as the processor 200 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.
[0042] As per the illustrated embodiment, the processor 200 is configured to fetch and execute computer-readable instructions stored in the memory 205. The memory 205 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 205 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.
[0043] In an embodiment, the user interface 210 includes a variety of interfaces, for example, interfaces for a graphical user interface, a web user interface, a Command Line Interface (CLI), and the like. The user interface 210 facilitates communication of the system 115. In one embodiment, the user interface 210 provides a communication pathway for one or more components of the system 115. Examples of such components include, but are not limited to, the UE 110 and the database 215.
[0044] The database 215 is one of, but not limited to, a centralized database, a cloud-based database, a commercial database, an open-source database, a distributed database, an end-user database, a graphical database, a No-Structured Query Language (NoSQL) database, an object-oriented database, a personal database, an in-memory database, a document-based database, a time series database, a wide column database, a key value database, a search database, a cache databases, and so forth. The foregoing examples of database 215 types are non-limiting and may not be mutually exclusive e.g., a database can be both commercial and cloud-based, or both relational and open-source, etc.
[0045] In order for the system 115 for managing the CNF operation, the processor 200 includes one or more modules. In one embodiment, the one or more modules includes, but not limited to, a transceiver unit 220, an updating unit 225, and a customization unit 230 communicably coupled to each other for managing the CNF operation.
[0046] In one embodiment, the one or more modules includes, but not limited to, the transceiver unit 220, the updating unit 225, and the customization unit 230 can be used in combination or interchangeably for managing the CNF operation.
[0047] The transceiver unit 220, the updating unit 225, and the customization unit 230, 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 200. 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 200 may be processor-executable instructions stored on a non-transitory machine-readable storage medium and the hardware for the processor may comprise a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the memory 205 may store instructions that, when executed by the processing resource, implement the processor. In such examples, the system 115 may comprise the memory 205 storing the instructions and the processing resource to execute the instructions, or the memory 205 may be separate but accessible to the system 115 and the processing resource. In other examples, the processor 200 may be implemented by electronic circuitry.
[0048] The transceiver unit 220 is configured to transmit the custom command operation request to an orchestrator adaptor 410 (as shown and explained in FIG. 4) over a first interface to initiate a Container Network Function (CNF) operation based on a custom command operation request received from a vendor. The CNF operation status encompasses the operational details of all the Containerized Network Function Components (CNFCs), which may include the instantiation status, whether each component has been successfully deployed. The CNF operation status includes the instantiation status of all the CNFCs, indicating whether they are running, failed, initializing, terminated, pending, or restarting. The CNF operation status reflect the current state of CNFCs, such as, but not limited to, the Network Slice Selection Function Component (UPF-CNFC) running to handle data traffic or the access and Mobility Management Function Component (AMF-CNFC) initializing connections for device mobility. The failed status may indicate resource issues, while the pending status shows that the CNFC is awaiting resources. Terminated and restarting statuses reflect the end of the CNFCs lifecycle or its recovery from errors. Monitoring the CNF operation status helps to optimize resource utilization and ensure seamless network operations.

[0049] The orchestrator adaptor 410 is a component in managing the CNF operations such as, for example, providing status updates, and facilitating communication. The orchestrator adaptor 410 coordinates the CNF operations by interacting with the CNFLM microservice to initiate, manage, and control tasks such as instantiation, termination, and deletion. The orchestrator adaptor 410 provides status updates by sending CNF operation status responses back to the CNFLM 405, which include details about the current state of the CNF and a Containerized Network Function Components (CNFC) instances, as well as updates about one or more resources in use and reserved.
[0050] In an embodiment, the CNFCs are responsible for executing specific tasks or functions within the larger CNF architecture, allowing for the more flexible, scalable, and efficient deployment of network services.
[0051] The orchestrator adaptor 410 facilitates communication by acting as an intermediary between the CNFLM 405 and the underlying infrastructure and ensuring smooth management of CNF instance lifecycles and interacting with a Physical & Virtual Resource Manager (PVIM) 505 (as shown in the FIG.5) for inventory management.
[0052] In an embodiment, the vendor refers to an organization or a company which supplies the custom command operation request which is required to be executed by the system 115. The custom command operation request is the specific instruction provided by the vendor to customize the behavior of the CNF operation according to requirements.
[0053] In one embodiment, the first interface is at least one of, a Container network function lifecycle Management - Orchestration Adaptor (CM_OA) interface 415 and the second interface is at least one of, an Inventory Management - Container network function lifecycle Management (IM_CM) interface.
[0054] The CM_OA interface 415 between the CNFLM 405 and the orchestrator adaptor 410 is primarily designed for managing the aggregation and orchestration of data related to network resources. The CM_OA interface 415 collects data from distributed resources like edge nodes, network slices, and core network components, consolidating into the single view for the CNFLM 405. The CM_OA interface 415 ensures that CNF operations are aligned with the overall network orchestration, allowing network services to be scaled, adjusted, or terminated as required by real-time conditions.
[0055] The IM_CM interface between the CNFLM 405 and the PVIM 510 is focused on managing and configuring network resources based on the inventory data. The PVIM 510 is responsible for maintaining the accurate inventory of virtualized resources such as, but not limited to, virtual machines (VMs), containers, and storage within the network 105. The PVIM 510 is essential for the CNFLM 405 to effectively manage the CNFs running across the infrastructure. The IM_CM interface allows the CNFLM 405 to interact with the PVIM 510 to configure and modify network resources dynamically. For example, if the CNFLM 405 determines that the particular CNF requires more compute power or storage to meet the demands of the network application, the CNFLM 405 may use the IM_CM interface to communicate with the PVIM 510 and allocate additional resources. The CNFLM 405 ensures that the CNFs are provisioned and configured based on real-time inventory data, optimizing resource utilization in the highly dynamic network environment.
[0056]
[0057] In an embodiment, prior to transmitting the custom command operation request to the orchestrator adaptor 410 over the first interface to initiate the CNF operation, the transceiver unit 220 is configured to transmit the request to a Policy Execution Engine (PEEGN) 505 (as shown and explained in FIG. 5) to check availability of at least one CNF policy and one or more reserve resources at the PEEGN 505 and receive the update of availability of the at least one CNF policy and the one or more reserved resources from the PEEGN 505. The CNF policy is essential for ensuring that CNFs operate efficiently, securely, and reliably, while also meeting the specific requirements of the network. The CNF policy is specific for the CNF in order to perform tasks such as, auto scaling, self-healing, geo-redundancy, disaster recovery, auto-correction of configurations.
[0058] The one or more reserve resources are the network resources that are reserved in advance to ensure availability when the PEEGN 505 is needed. The reserve resource may include, but not limited to bandwidth, compute capacity, storage, and other critical network elements.
[0059] In an embodiment, the transceiver unit 220 receives the CNF operation status response from the orchestrator adaptor 410, upon the orchestrator adaptor 410 checking for the status of the one or more resources at a Physical & Virtual Resource Manager (PVIM) 510 (as shown and explained in FIG. 5).
[0060] Upon receiving the CNF operation status response from the orchestrator adaptor 410 at the PVIM 510, the updating unit 225 is configured to update an inventory at the PVIM 510 pertaining to the one or more resources in use and the one or more resources reserved based on the CNF operation status response received from the orchestrator adaptor 410. The components within the PVIM 510 system are responsible for processing and applying updates to the inventory based on the information received. The components involved in the process within the PVIM 510 system includes the orchestrator adaptor 410, which manages and coordinates the operations and sends status responses back to the PVIM 510, and the updating unit 225, which is responsible for processing the status responses and updating the inventory to reflect the current state of one or more resources in use.
[0061] In an embodiment, the customization unit 230 of the system 115 is configured to allow the vendor to customize the CNF operation based on the custom command operation request received from the vendor, the vendor is required to provide minimum information in order to customize the CNF operation. The minimum information required for customizing the CNF operation includes, but not limited to, information of the CNF identifier, which specifies the targeted CNF, operational parameters defining resource limits and performance criteria, deployment location indicating where the CNF should be deployed, policy selection referencing the applicable predefined policies, resource requirements specifying compute power, storage, or bandwidth, and execution schedule indicating when the CNF operation should be executed. In an embodiment, the custom command operation request relates to the vendor providing information to customize the CNF operation.
[0062] In an embodiment, the information provided by the vendor includes the details that the vendor needs to provide in order to customize the operation of the CNF in the network environment. The information is necessary to ensure that the CNF is tailored to meet specific network demands or performance requirements. The information may include, but not limited to, CNF identifier, operational parameters, deployment location, and resource requirements.
[0063] In an embodiment, the at least one CNF operation includes at least one of, a CNF instantiation, a CNF termination, and a CNF deletion utilizing the first interface. The CNF instantiation is the process of creating and deploying the new CNF instance within the network 105. The CNF instantiation operation involves allocating resources and configuring the CNF to start functioning as part of the network 105. The CNF termination is the process of shutting down and deactivating the existing CNF instance. The CNF termination involves releasing the resources allocated to the CNF and removing them from the active service of the CNF. The CNF deletion is the process of completely removing the CNF instance and all associated configurations from the network 105. The CNF deletion includes not only shutting down the CNF instance but also deleting any related data and configurations.
[0064] Upon updating the inventory at the PVIM 510, the transceiver unit 220 is configured to transmit an inventory management request via the second interface to the PVIM 510 to manage inventory based on the CNF operation status.
[0065] In an embodiment, the CNF operation status comprises status of all (CNFC instantiation status. The CNFC performs specific functions required for the overall operation of the CNF in the network 105. The CNFC includes, but not limited to virtualized firewall component, virtualized load balancer component, virtualized network function for user authentication, virtualized network function for network slicing, virtualized network function for session management.
[0066] In an embodiment, the transceiver unit 220 is further configured to receive an inventory management acknowledgement from the PVIM 510 in response to the transmitted inventory management request. The transceiver unit 220 transmits the inventory management request to the PVIM 510 to perform the inventory-related action, such as, but not limited to updating or/and querying network the one or more resource status. The PVIM 510 processes the request and sends the acknowledgement back to the transceiver unit 220. The PVIM 510 confirms the request has been received and processed, and provides details on the outcome.
[0067] FIG. 3 describes a preferred embodiment of the system 115 of FIG. 2, according to various embodiments of the present invention. It is to be noted that the embodiment with respect to FIG. 3 will be explained with respect to the first UE 110a and the system 115 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 in FIG. 1, each of the first UE 110a, the second UE 110b, and the third UE 110c may include an external storage device, a bus, a main memory, a read-only memory, a mass storage device, communication port(s), and a processor. The exemplary embodiment as illustrated in FIG. 3 will be explained with respect to the first UE 110a without deviating from the scope of the present disclosure and limiting the scope of the present disclosure. The first UE 110a includes one or more primary processors 305 communicably coupled to the one or more processors 200 of the system 115.
[0069] The one or more primary processors 305 are coupled with a memory 310 storing instructions which are executed by the one or more primary processors 305. Execution of the stored instructions by the one or more primary processors 305 enables the first UE 110a to transmit a custom command operation request to the one or more processors 200 pertaining to initiating a CNF operation.
[0070] As mentioned earlier in FIG. 2, the one or more processors 200 of the system 115 is configured for managing the CNF operation. As per the illustrated embodiment, the system 115 includes the one or more processors 200, the memory 205, the user interface 210, and the database 215. The operations and functions of the one or more processors 200, the memory 205, the user interface 210, and the database 215 are already explained in FIG. 2. For the sake of brevity, a similar description related to the working and operation of the system 115 as illustrated in FIG. 2 has been omitted to avoid repetition.
[0071] Further, the processor 200 includes the transceiver unit 220, the updating unit 225, the customization unit 230. The operations and functions of the transceiver unit 220, the updating unit 225, the customization unit 230 are already explained in FIG. 2. Hence, for the sake of brevity, a similar description related to the working and operation of the system 115 as illustrated in FIG. 2 has been omitted to avoid repetition. The limited description provided for the system 115 in FIG. 3, should be read with the description as provided for the system 115 in the FIG. 2 above, and should not be construed as limiting the scope of the present disclosure.
[0072] FIG. 4 is an exemplary block diagram of an architecture 400 of the system 115 for managing the CNF operation, according to one or more embodiments of the present invention.
[0073] The architecture 400 includes a User Interface (UI) 210, a Container Network Function-Life Cycle Manager (CNFLM) 405, an orchestrator adaptor 410, an infrastructure 420, the database 215.
[0074] The UI 215serves as an interaction layer between the user and the system. The UI 215 interacts with the CNFLM 405and the orchestrator adaptor 410 to manage user requests and data processing.
[0075] The CNFLM 405 communicates with the orchestrator adaptor 410 to coordinate control functions and data analytics. The CNFLM 405 is a microservice which is designed to manage and handle details related to vendors, CNF and CNFC via an Application Programming Interface (API). The captured details may be stored in the database 215 and may be further used by the orchestrator adaptor 410 microservice. The CNFLM 405 provides Application Programming Interface (API) endpoints for creating new entries, retrieving details, and updating existing information for vendors, the CNF and the CNFC. The CNFLM 405 microservice receives requests from the UI 215 to onboard, instantiate, or terminate CNF instances.
[0076] The CNFLM 405 and the orchestrator adaptor 410 depend on the infrastructure 420 to perform the operations, which includes network resources and computing capabilities. The infrastructure 420 represents the underlying physical and virtual infrastructure that supports the platform. Upon receiving the requests from the UI 215 to onboard, instantiate, or terminate CNF instances, the CNFLM 405 microservice interacts with the orchestrator adaptor 410 to spawn the appropriate CNF and CNFC instances as needed.
[0077] The orchestrator adaptor 410 service handles deployment of the CNF operation by directly connecting to a container host 515 (explained in FIG. 5) of a swarm manager and deploys a container image to the container host 515 nodes via the swarm manager. The container image is deployed in the nodes of the container host 515 within the container swarm environment by the orchestrator adaptor 410, enabling the CNF or the CNFC to operate within the network infrastructure. The container image essentially serves as the blueprint for creating and running containerized instances of the network functions.
[0078] The orchestrator adaptor 410 connects to the database 215 to store and retrieve necessary data. The orchestrator adaptor 410 service may create the container swarm manager and add the container host 515 as swarm worker nodes, while the PVIM 510 subscribes to CNFLM 405 acknowledgment events to obtain the status of instantiated CNFs or CNFCs and update the inventory mapping from reserved to in-use. The given container host 515 may function as either the manager, the worker or perform both roles.
[0079] During the CNF instantiation process, the PEEGN 505 checks the at least one CNF policy and one or more resources at the PVIM 510 and supports the scaling policy for the CNFC. When the the CNF or the CNFC is created, its optimal state is defined by specifying parameters such as, but not limited to the number of replicas, the network and storage resources available, and the ports exposed to the outside world.
[0080] FIG. 5 is a signal flow diagram for managing the CNF operation, according to one or more embodiments of the present invention.
[0081] The UI 215 sends custom command instantiation request after design phase to the CNFLM 405. The CNFLM 405 is responsible for creating the CNF instances or the individual CNFC instances and for scaling out the CNF or the individual CNFC.
[0082] At step 525, upon receiving the request from UI 215, the CNFLM 405 sends reserve resources request to the PEEGN 505. The PEEGN 505 is involved in the CNF instantiation flow to check the CNF initialization policy and to reserve the resources required to instantiate the CNF at the PVIM 510.
[0083] At step 530, upon receiving the reserve request from the CNFLM 405, the PEEGN 505 will respond back to the CNFLM 405 with the update on the availability of the reserved one or more resource and supports scaling policy for CNF components.
[0084] At step 535, the CNFLM 405 transmits custom command instantiation request to the orchestrator adaptor 410 to instantiate the CNF. During design time, the network function product provides the custom command and also facilitates the CNF will be instantiated using the custom command. The network function product refers to the custom set of functionalities and specifications that define how the CNF should be instantiated, configured, and operated within the network 105. The network function products include, but not limited to, custom commands, configuration details, and operational guidelines.
[0085] At step 540, upon instantiation the CNF in the container host 515, the container host 515 transmits the instantiation status response to the orchestrator adaptor 410. The orchestrator adaptor 410 will directly connect to the container host 515 of the swarm manager to deploy the container image to the nodes of the container host 515 and manage connections with the swarm manager.
[0086] At step 545, the CNFLM 405 receives the CNF instantiation response from the orchestrator adaptor 410 service. Based on the CNFC instantiation status, the CNFLM 405 prepares the request to update the inventory.
[0087] At step 550, upon preparing the request in the CNFLM 405, the CNFLM 405 uses the IM_CM interface to send the inventory update request to the PVIM 510.
[0088] At step 555, upon receiving the inventory update request from the CNFLM 405, the PVIM 510 facilitates accurate inventory management to reflect the current state of the instantiated CNF components.
[0089] At step 560, upon receiving the accurate inventory management data from the PVIM 510, the CNFLM 405 will update the instantiation status in the Release Management Repository (RMR) 520 for the future reference and transmit the response back to the CNFLM 405 to acknowledge the update. In an embodiment, the RMR 520 refers to the centralized system or tool designed to handle and coordinate the release of, but not limited to software, firmware, and configuration updates for network elements, and also includes, but not limited to core network functions, radio access networks, and network management system.
[0090] At step 565, upon receiving the updated acknowledgement from the CNFLM 405¸ the UI 210 will receive the acknowledgement for the CNF operation The user thereafter may initiate the CNF operations, such as instantiation, termination, or deletion, from the UI 215.
[0091] FIG. 6 is a flow diagram of a method 600 for managing the CNF operation, according to one or more embodiments of the present invention. For the purpose of description, the method 600 is described with the embodiments as illustrated in FIG. 2 and should nowhere be construed as limiting the scope of the present disclosure.
[0092] At step 605, the method 600 includes the step of transmitting the custom command operation request to the orchestrator adaptor 410 over the first interface to initiate the CNF operation based on the custom command operation request received from the vendor. The first interface is at least one of, an CM_OA interface and the second interface is at least one of, an IM_CM interface. The CNF operation status response is received from the orchestrator adaptor 410 upon the orchestrator adaptor 410 checking for the status of the resources at the PVIM 510.
[0093] At step 610, the method 600 includes the step of updating inventory at the PVIM pertaining to the one or more resources in use and the one or more resources reserved based on the CNF operation status response received from the orchestrator adaptor 410. The at least one CNF operation includes at least one of, the CNF instantiation, the CNF termination, and the CNF deletion utilizing the first interface.
[0094] At step 615, the method 600 includes the step of transmitting the inventory management request via the second interface to the PVIM 510 to manage inventory based on the CNF operation status. Further the method includes receiving the inventory management acknowledgement from the PVIM 510 in response to the transmitted inventory management request. The step of transmitting the inventory management request via the second interface to the PVIM 510 to manage inventory based on the CNF instantiation status, further includes the step of receiving the inventory management acknowledgment from the PVIM 510 in response to the transmitted inventory management request.
[0095] FIG. 7 illustrates a system architecture 700 (e.g., MANO architecture) depicting an CM_OA interface 415 operation, in accordance with an embodiment of the present invention. The system architecture 700 includes the user interface 215, a Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) design function module 705, a platform foundation service module 710, a platform core service module 715, and a platform resource adapter and utilities module 720.
[0096] The NFV and SDN design function module 705 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 710 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 710 provides the essential capabilities and resources required for the CNF environment to function effectively.
[0097] The platform core service module 715 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 720 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 720 plays a crucial role in integrating CNFs with underlying infrastructure and services, providing the necessary support for efficient operation, resource utilization, and interoperability.
[0098] The NFV and SDN design function module 710 includes a VNF lifecycle manger 705a, a VNF catalog 705b, a network service catalog 705c, a network slicing and service chaining manger 705d, the PVIM 510, and the CNFLM 405.
[0099] The VNF lifecycle manager 705a is responsible for managing the entire lifecycle of Virtual Network Functions (VNFs). The VNF lifecycle manager 705a ensures that VNFs or CNFs are deployed, configured, monitored, scaled, and eventually decommissioned effectively. The VNF catalog 705b (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 705b 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 705c 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 705c serves as a central resource for defining, deploying, and managing these services within a containerized network environment.
[00100] The network slicing and service chaining manager 705d 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 510 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 510 ensures that the necessary resources are allocated efficiently and effectively to meet the performance, availability, and scalability requirements of containerized network functions.
[00101] Further, the CNF lifecycle manager 405 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 405 ensures that the CNFs are efficiently deployed, monitored, scaled, updated, and removed, facilitating the smooth operation of network services in a containerized environment.
[00102] The platform foundation service module 710 includes a microservice elastic load balancer 710a, an identity and access manager 710b, a command line interface 710c, a central logging manager 710d and an event routing manager 710e.
[00103] The microservice elastic load balancer 710a 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 710b is a critical component responsible for managing and securing access to containerized network functions and their resources. The identity and access manager 710b 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.
[00104] The central logging manger 710d 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 manager 710e 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 manager 710e 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.
[00105] The platform core service module 715 includes an NFV infrastructure monitoring manager 715a, an assurance manager 715b, a performance manger 715c, the PEEGN 505, a capacity monitoring manger 715e, the RMR 520, a configuration manger and GCT (715g), a NFV platform decision analytics unit 715h, a platform NoSQL DB 715i, a platform scheduler and Cron Jobs module 715j, a VNF backup & upgrade manger 715k, a micro service auditor 715l, and a platform operation, administration and maintenance manager 715m.
[00106] The NFV infrastructure monitoring manager 715a monitors the underlying infrastructure of NFV environments, including computing, storage, and network resources. The NFV infrastructure monitoring manager 715a provides real-time visibility into resource health, performance, and utilization. Further, the NFV infrastructure monitoring manager 715a detects and alerts infrastructure issues. Further, the NFV infrastructure monitoring manager (715a) integrates with monitoring tools to ensure reliable operation of CNFs.
[00107] The assurance manager 715b manages the quality and reliability of network services by ensuring compliance with service level agreements (SLAs) and operational standards. The performance manager 715c optimizes the performance of CNFs by tracking and analyzing key performance indicators (KPIs). The policy execution engine 505 enforces and applies policies within the CNF environment to manage operations and access. Further, the policy execution engine 505 executes policies related to security, resource allocation, and service quality. Further, the policy execution engine 505 executes policies translates policy rules into actionable configurations and enforces compliance across CNFs.
[00108] The capacity monitoring manager 715e monitors and manages the capacity of resources within the CNF environment to ensure optimal usage and avoid resource shortages. The release management repository (RMR) 520 stores and manages software releases, configurations, and versions of CNFs. Further, the RMR 520 keeps track of different versions of CNFs.
[00109] The configuration manager and Generic Configuration Tool (GCT) 715g manages the configuration of CNFs and related infrastructure components. The NFV platform decision analytics unit 715h analyzes data from a NFV platform to support decision-making and strategic planning.
[00110] The platform NoSQL database (DB) 715i 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 715j manage scheduled tasks and periodic operations within the CNF environment. The VNF backup & upgrade manager 715k oversees the backup and upgrade processes for Virtual Network Functions (VNFs) within the CNF environment.
[00111] The micro service auditor 715l monitors and audits microservices to ensure compliance with operational and security standards. The platform operation, administration and maintenance manager 715m manages the overall operation, administration, and maintenance of the CNF platform.
[00112] The platform resource adapter and utilities module 720 includes a platform external API adaptor and gateway 720a, a generic decoder and indexer 720b, the orchestrator adaptor 410, an opensatck API adaptor 720 and a NFV gateway 720e.
[00113] The platform external API adaptor and gateway 720a facilitate communication between the CNF platform and external systems or services by providing an interface for API interactions. The generic decoder and indexer 720b decode and indexes various types of data and logs within the CNF environment. The orchestrator adaptor 410 facilitates communication between a swarm clusters and the CNF environment, including container deployment, scaling, and management.
[00114] The opensatck API adaptor 720d 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 720e manages and facilitates communication between NFV (Network Functions Virtualization) components and external networks or services.
[00115] The present invention further discloses a non-transitory computer-readable medium having stored thereon computer-readable instructions. The computer-readable instructions are executed by the processor 200. The processor 200 configures to transmit the custom command operation request to the orchestrator adaptor 415 over the first interface to initiate the CNF operation based on the custom command operation request received from the vendor. The processor 200 is configured to update inventory at the PVIM 510 pertaining to one or more resources in use and one or more resources reserved based on the CNF operation status response received from the orchestrator adaptor 415. The processor 200 is further configured to transmit the inventory management request via the second interface to the PVIM 510 to manage inventory based on the CNF operation status.
[00116] A person of ordinary skill in the art will readily ascertain that the illustrated embodiments and steps in description and drawings (FIG.1-6) are set out to explain the exemplary embodiments shown, and it should be anticipated that ongoing technological development will change the manner in which particular functions are performed. These examples are presented herein for purposes of illustration, and not limitation. Further, the boundaries of the functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternative boundaries can be defined so long as the specified functions and relationships thereof are appropriately performed. Alternatives (including equivalents, extensions, variations, deviations, etc., of those described herein) will be apparent to persons skilled in the relevant art(s) based on the teachings contained herein. Such alternatives fall within the scope and spirit of the disclosed embodiments.
[00117] The present disclosure incorporates technical advancement to manage CNF operations via custom commands transmitted to the orchestrator adaptor. This flexibility supports a range of CNF operations such as instantiation, termination, and deletion, which can be tailored based on vendor-specific requests. The approach enables dynamic management of the CNF operations, accommodating custom configurations and requirements provided by vendors. The invention represents the significant advancement by integrating flexible and automated CNF management with policy and resource management systems. It facilitates customization for vendors, ensures accurate inventory management, provides detailed status reporting, and facilitates UE integration. This approach improves the overall efficiency, reliability, and adaptability of CNF operations within the network.
[00118] The present invention offers multiple advantages such as enabling rapid deployment of new services, adaptability to diverse use cases, optimized resource utilization, enhanced scalability and flexibility, support for advanced network slicing, efficient handling of network function lifecycle. The custom instantiation commands enable rapid deployment of new services, such as High Definition (HD) streaming or Internet of Things (IoT) applications, reducing time-to-market by minimizing pre-configuration and optimizing the high-speed data, URLLC applications. Integration with the PVIM ensures efficient, dynamic resource allocation in the network, optimizing performance and reducing waste during peak time or high-density areas. The solution ensures efficient CNF lifecycle management—instantiation, termination, and updates—critical for maintaining network stability and quality as services evolve.

REFERENCE NUMERALS

[00119] Environment- 100
[00120] Network- 105
[00121] User Equipment (UE)- 110
[00122] Server- 120
[00123] Processor- 200
[00124] Memory- 205
[00125] User Interface- 210
[00126] Database- 215
[00127] Transceiver unit - 220
[00128] Updating unit - 225
[00129] Customization unit – 230
[00130] Primary processors - 305
[00131] Primary memory - 310
[00132] Container Network Function-Life Cycle Manager (CNFLM) - 405
[00133] Orchestrator adaptor- 410
[00134] Infrastructure - 420
[00135] Policy Execution Engine (PEEGN) - 505
[00136] Physical & Virtual Resource Manager (PVIM) – 510
[00137] Container host - 515
[00138] Release Management Repository (RMR) - 520
,CLAIMS:CLAIMS:
We Claim:
1. A method (600) for managing a Container Network Function (CNF) operation, the method (600) comprises the steps of:
transmitting, by one or more processors (205), a custom command operation request to an orchestrator adaptor (415) over a first interface to initiate the CNF operation based on the custom command operation request received from a vendor;
updating, by the one or more processors (205), inventory at a Physical & Virtual Resource Manager (PVIM) (510) pertaining to one or more resources in use and one or more resources reserved based on a CNF operation status response received from the orchestrator adaptor (415); and
transmitting, by the one or more processors (205), an inventory management request via a second interface to the PVIM (510) to manage the inventory based on the CNF operation status.

2. The method (600) as claimed in claim 1, wherein prior to transmitting, the custom command operation request to the orchestrator adaptor (415) over the first interface to initiate the CNF operation, the method (600) includes the steps of:
transmitting, by the one or more processors (205), the request to a Policy Execution Engine (PEEGN) (505) to check availability of at least one CNF policy and one or more reserve resources at the PEEGN (505); and
receiving, by the one or more processors (205), an update of availability the at least one CNF policy and the one or more reserve resources from the PEEGN (505).

The method (600) as claimed in claim 1, wherein the one or more processors (205) is configured to allow the vendor to customize the CNF operation based on the custom command operation request received from the vendor.
3. The method (600) as claimed in claim 1, wherein the custom command operation request relates to the vendor providing information to customize the CNF operation.

4. The method (600) as claimed in claim 1, wherein the first interface is at least one of, an CM_OA interface (415) and the second interface is at least one of, an IM_CM interface.

5. The method (600) as claimed in claim 1, wherein the at least one CNF operation includes at least one of, a CNF instantiation, a CNF termination, and a CNF deletion utilizing the first interface.

6. The method (600) as claimed in claim 1, wherein the one or more processors (205), receives the CNF operation status response from the orchestrator adaptor (410) upon the orchestrator adaptor (410) checking for the status of the resources at the PVIM (510).

7. The method (600) as claimed in claim 1, wherein the step of, transmitting, an inventory management request via the second interface to the PVIM (510) to manage inventory based on the CNF instantiation status, further includes the step of:
receiving, by the one or more processors (205), an inventory management acknowledgement from the PVIM (510) in response to the transmitted inventory management request.

8. The method (600) as claimed in claim 1, wherein the CNF operation status comprises status of all Containerized Network Function Components (CNFC) instantiation status.

9. A system (120) for managing a Container Network Function (CNF) operation, the system comprising:
a transceiver unit (225), configured to, transmit, a custom command operation request to an orchestrator adaptor (410) over a first interface to initiate the CNF operation based on the custom command operation request received from a vendor;
an updating unit (230), configured to, update, inventory at a Physical & Virtual Resource Manager (PVIM) (510) pertaining to one or more resources in use and one or more resources reserved based on a CNF operation status response received from the orchestrator adaptor (410); and
the transceiver unit (225), configured to, transmit, an inventory management request via a second interface to the PVIM (510) to manage the inventory based on the CNF operation status.

10. The system (120) as claimed in claim 10, wherein prior to transmitting, the custom command operation request to the orchestrator adaptor (410) over the first interface to initiate the CNF operation, the transceiver unit (225) is configured to:
transmit, the request to a Policy Execution Engine (PEEGN) (505) to check availability of at least one CNF policy and one or more reserve resources at the PEEGN (505); and
receive, an update of availability the at least one CNF policy and the one or more reserve resources from the PEEGN (505).

11. The system (120) as claimed in claim 10, wherein a customization unit (235) of the system (120) is configured to allow the vendor to customize the CNF operation based on the custom command operation request received from the vendor.

12. The system (120) as claimed in claim 10, wherein the custom command operation request relates to the vendor providing information to customize the CNF operation.

13. The system (120) as claimed in claim 10, wherein the first interface is at least one of, an CM_OA interface (415) and the second interface is at least one of, an IM_CM interface.

14. The system (120) as claimed in claim 10, wherein the at least one CNF operation includes at least one of, a CNF instantiation, a CNF termination, and a CNF deletion utilizing the first interface.

15. The system (120) as claimed in claim 10, wherein the transceiver unit (225), receives the CNF operation status response from the orchestrator adaptor (410) upon the orchestrator adaptor (410) checking for the status of the resources at the PVIM (510).

16. The system (120) as claimed in claim 10, wherein the transceiver unit (225), is further configured to:
receive an inventory management acknowledgement from the PVIM (510) in response to the transmitted inventory management request.

17. The system (120) as claimed in claim 10, wherein the CNF operation status comprises status of all Containerized Network Function Components (CNFC) instantiation status.

18. A User Equipment (UE) (110), comprising:
one or more primary processors (305) communicatively coupled to one or more processors (205), the one or more primary processors (305) coupled with a memory (310), wherein said memory stores instructions which when executed by the one or more primary processors (205) causes the UE (110) to:
transmit, a custom command operation request to the one or more processors pertaining to initiating a CNF operation, and
wherein the one or more processors (205) is configured to perform the steps as claimed in claim 1.