Method and system for managing environment variables for container network function components in network environment

Abstract

The present disclosure relates to a method and a system for managing environment variables for Container Network Function Components (CNFCs) in a network environment In one example, the method comprises receiving, at a PVIM unit, from a container network function lifecycle manager (CNFLM), a reserve request comprising a set of environment variables for at least a CNFC. The method further comprises setting, by a processing unit at the PVIM unit, a reserved status associated with the set of environment variables based on the reserve request. The method further comprises transmitting, by the transceiver unit at the PVIM unit, to a PEEGN node, details of the set of environment variables and the reserved status. The method further comprises receiving, by the transceiver unit at the PVIM unit, from the CNFLM, an update inventory request associated with one or more environment variables from the set of environment variables. The method further comprises setting, by the processing unit at the PVIM unit, a status of the one or more environment variables based on the update inventory request.

Description

METHOD AND SYSTEM FOR MANAGING ENVIRONMENT VARIABLES FOR CONTAINER NETWORK FUNCTION COMPONENTS IN NETWORK ENVIRONMENTFIELD OF INVENTION

[0001] Embodiments of the present disclosure relate methods and systems for managing environment variables for Container Network Function Components (CNFCs) in a network environment.BACKGROUND

[0002] The following description of the related art is intended to provide background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section is used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of the prior art.

[0003] In communication network such as 5G communication network, different microservices perform different services, jobs and tasks in the network. For instantiating microservices such as Container network function (CNF) / CNFC, environment variables are required to be present in inventory. For a CNF, for example, if it has four or five CNFC components, it is required for environment variables key and value to be present in the inventory for each CNFC components instantiation. Different environment variables may be used such as, system level, operating system level and setting path.

[0004] Such available set of environmental variables needs to be reserved at the time of instantiation. However, after instantiation, it needs to be marked as used, so that same environment variables can’t be used by other CNFC. If any instantiation gets failed, then un-reserving of environment variables of that instantiation is required. Further, at time of termination, set of environment variable needs to be marked as free so that can be used for other CNFC. However, the current available solution for managing environment variables for CNFC components instantiation is not efficient and have complex processing procedure.

[0005] Thus, there exists an imperative need in the art to provide an efficient system and method for allocating and managing environment variables for CNFC.SUMMARY

[0006] This section is provided to introduce certain aspects of the present disclosure in a simplified form that are further described below in the detailed description. This summary is not intended to identify the key features or the scope of the claimed subject matter.

[0007] An aspect of the present disclosure may relate to a method for managing environment variables for Container Network Function Components (CNFCs) in a network environment. The method comprises receiving, by a transceiver unit at a physical & virtual inventory manager (PVIM) unit, from a container network function lifecycle manager (CNFLM), a reserve request comprising a set of environment variables for at least a CNFC. The method further comprises setting, by a processing unit at the PVIM unit, a reserved status associated with the set of environment variables based on the reserve request. The method further comprises transmitting, by the transceiver unit at the PVIM unit, to a Policy Execution Engine (PEEGN) node, details of the set of environment variables and the reserved status. The method further comprises receiving, by the transceiver unit at the PVIM unit, from the CNFLM, an update inventory request associated with one or more environment variables from the set of environment variables. The method further comprises setting, by the processing unit at the PVIM unit, a status of the one or more environment variables based on the update inventory request.

[0008] In an exemplary aspect of the present disclosure, the method further comprises retrieving, by the processing unit at the PVIM unit, from the CNFLM via a service manager, the details of the set of environment variables.

[0009] In an exemplary aspect of the present disclosure, the set of environment variables with at least the CNFC are configured by the service manager during an instantiation of at least the CNFC.

[0010] In an exemplary aspect of the present disclosure, the update inventory request associated with one or more environment variables is transmitted by the CNFLM in an event a successful instantiation of at least the CNFC is performed by a service manager.

[0011] In an exemplary aspect of the present disclosure, the update inventory request associated with one or more environment variables is transmitted by the CNFLM in an event a successful termination of at least the CNFC is performed by a service manager.

[0012] In an exemplary aspect of the present disclosure, the status is updated to the free status in an event the successful termination of at least the CNFC is performed by a service manager.

[0013] In an exemplary aspect of the present disclosure, the status is updated to the free status in an event a failed instantiation of at least the CNFC is performed by a service manager.

[0014] In an exemplary aspect of the present disclosure, the set of environment variables for at least the CNFC is received in a compressed format.

[0015] In an exemplary aspect of the present disclosure, the set of environment variables for at least the CNFC is provided at the CNFLM by a user of the network environment.

[0016] Another aspect of the present disclosure may relate to a system for managing environment variables for Container Network Function Components (CNFCs) in a network environment. The system comprises a physical & virtual inventory manager (PVIM) unit. The PVIM unit comprises a transceiver unit configured to receive, from a container network function lifecycle manager (CNFLM), a reserve request comprising a set of environment variables for at least a CNFC. The system further comprises a processing unit connected to at least the transceiver unit. The processing unit is configured to set a reserved status associated with the set of environment variables based on the reserve request. The transceiver unit is further configured to transmit, to a Policy Execution Engine (PEEGN) node, details of the set of environment variables and the reserved status. The transceiver unit is further configured to receive, from the CNFLM, an update inventory request associated with one or more environment variables from the set of environment variables. The processing unit is further configured to set a status of the one or more environment variables based on the update inventory request.

[0017] Yet another aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing instructions for managing environment variables for Container Network Function Components (CNFCs) in a network environment. The instructions include executable code which, when executed by one or more units of a system, causes a transceiver unit, at a physical & virtual inventory manager (PVIM) unit, of the system to receive a reserve requestfrom a container network function lifecycle manager (CNFLM). The reserve request comprises a set of environment variables for at least a CNFC. Further, the instructions include executable code which, when executed, causes a processing unit, at the PVIM unit, to set a reserved status associated with the set of environment variables based on the reserve request. Further, the instructions include executable code which, when executed, causes the transceiver unit, at the PVIM unit, to transmit details of the set of environment variables and the reserved status to a Policy Execution Engine (PEEGN) node. Further, the instructions include executable code which, when executed, causes the transceiver unit, at the PVIM unit, to receive an update inventory request from the CNFM. The update inventory request is associated with one or more environment variables from the set of environment variables. Further, the instructions include executable code which, when executed, causes the processing unit, at the PVIM unit, to set a status of the one or more environment variables based on the update inventory request.OBJECTS OF THE DISCLOSURE

[0018] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.

[0019] It is an object of the present disclosure to provide a system and a method for managing environment variables for Container Network Function Components (CNFCs) in a network environment.

[0020] It is another object of the present disclosure to provide a system and a method for assigning environment variables at run time to any of required CNFC.

[0021] It is another object of the present disclosure to provide a system and a method for enabling fault tolerance for any event failure, the related managing interface can also work in a high availability mode and if one inventory instance went down during request processing, then next available instance may take care of this request.DESCRIPTION OF THE DRAWINGS

[0022] 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 thedrawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Also, the embodiments shown in the figures are not to be construed as limiting the disclosure, but the possible variants of the method and system according to the disclosure are illustrated herein to highlight the advantages of the disclosure. It will be appreciated by those skilled in the art that disclosure of such drawings includes disclosure of electrical components or circuitry commonly used to implement such components.

[0023] FIG. 1 illustrates an exemplary block diagram representation of a management and orchestration (MANO) architecture.

[0024] FIG. 2 illustrates an exemplary block diagram of a computing device upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure.

[0025] FIG. 3 illustrates an exemplary block diagram of a system for managing environment variables for Container Network Function Components (CNFCs) in a network environment, in accordance with exemplary implementations of the present disclosure.

[0026] FIG. 4 illustrates a method flow diagram for managing environment variables for Container Network Function Components (CNFCs) in a network environment, in accordance with exemplary implementations of the present disclosure.

[0027] FIG. 5 illustrates an exemplary signalling diagram for managing environment variables for Container Network Function Components (CNFCs) in a network environment during CNF instantiation, in accordance with exemplary implementations of the present disclosure.

[0028] FIG. 6 illustrates an exemplary signalling diagram for managing environment variables for Container Network Function Components (CNFCs) in a network environment during CNF termination, in accordance with exemplary implementations of the present disclosure.

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

[0030] In the following description, for the purposes of explanation, various specific details are set forth in order to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter may each be used independently of one another or with any combination of other features. An individual feature may not address any of the problems discussed above or might address only some of the problems discussed above.

[0031] The ensuing description provides exemplary embodiments only, and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing an exemplary embodiment. It should be understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the disclosure as set forth.

[0032] Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it will be understood by one of ordinary skill in the art that the embodiments may be practiced without these specific details. For example, circuits, systems, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail.

[0033] Also, it is noted that individual embodiments may be described as a process which is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations may be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed but could have additional steps not included in a figure.

[0034] The word “exemplary” and / or “demonstrative” is used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. In addition, any aspect or design described herein as “exemplary” and / or “demonstrative” is not necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed description or the claims,such terms are intended to be inclusive — in a manner similar to the term “comprising” as an open transition word — without precluding any additional or other elements.

[0035] As used herein, a “processing unit” or “processor” or “operating processor” includes one or more processors, wherein processor refers to any logic circuitry for processing instructions. A processor may be a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor, a plurality of microprocessors, one or more microprocessors in association with a Digital Signal Processing (DSP) core, a controller, a microcontroller, Application Specific Integrated Circuits, Field Programmable Gate Array circuits, any other type of integrated circuits, etc. The processor may perform signal coding data processing, input / output processing, and / or any other functionality that enables the working of the system according to the present disclosure. More specifically, the processor or processing unit is a hardware processor.

[0036] As used herein, “a user equipment”, “a user device”, “a smart-user-device”, “a smartdevice”, “an electronic device”, “a mobile device”, “a handheld device”, “a wireless communication device”, “a mobile communication device”, “a communication device” may be any electrical, electronic and / or computing device or equipment, capable of implementing the features of the present disclosure. The user equipment / device may include, but is not limited to, a mobile phone, smart phone, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, wearable device or any other computing device which is capable of implementing the features of the present disclosure. Also, the user device may contain at least one input means configured to receive an input from unit(s) which are required to implement the features of the present disclosure.

[0037] As used herein, “storage unit” or “memory unit” refers to a machine or computer-readable medium including any mechanism for storing information in a form readable by a computer or similar machine. For example, a computer-readable medium includes read-only memory (“ROM”), random access memory (“RAM”), magnetic disk storage media, optical storage media, flash memory devices or other types of machine-accessible storage media. The storage unit stores at least the data that may be required by one or more units of the system to perform their respective functions.

[0038] As used herein “interface” or “user interface refers to a shared boundary across which two or more separate components of a system exchange information or data. The interface may also be referred to a set of rules or protocols that define communication or interaction of one or moremodules or one or more units with each other, which also includes the methods, functions, or procedures that may be called.

[0039] All modules, units, components used herein, unless explicitly excluded herein, may be software modules or hardware processors, the processors being a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASIC), Field Programmable Gate Array circuits (FPGA), any other type of integrated circuits, etc.

[0040] As used herein the transceiver unit include at least one receiver and at least one transmitter configured respectively for receiving and transmitting data, signals, information or a combination thereof between units / components within the system and / or connected with the system.

[0041] As discussed in the background section, the current known solutions have several shortcomings. The present disclosure aims to overcome the above-mentioned and other existing problems in this field of technology by providing method and system of managing environment variables for Container Network Function Components (CNFCs) in a network environment.

[0042] The present system and method provide a solution, which assigns environment variables at run time to any of required CNFC. The present system and method enable the maintenance of set of environment variables in inventory for all the CNFC’s of particular CNF, where environment variables are required to be set at the time of instantiation. The present system and method provide a solution, which reserve set of environment variables for instantiation, un-reserve environment variables if instantiation gets failed, mark set of environment variables as ‘used’ for successful instantiation and mark set of environment variables as ‘free’ after successful termination of instantiation. The present system and method provide a solution, which enables to Service Adaptor for using the environment files assigned to particular CNFC at the time of instantiation and set those environment variables as per mentioned key values in file. The present system and method provide a solution, which enables async event-based implementation and auto sync inventory based on instantiation resource usages.

[0043] Hereinafter, exemplary embodiments of the present disclosure will be described with reference to the accompanying drawings.

[0044] FIG. 1 illustrates an exemplary block diagram representation of a management and orchestration (MANO) architecture / platform

[0100] , in accordance with exemplary implementation of the present disclosure. The MANO architecture

[0100] may be developed for managing telecom cloud infrastructure automatically, managing design or deployment design, managing instantiation of a network node(s) etc / service(s). The MANO architecture

[0100] deploys the network node(s) in the form of Virtual Network Function (VNF) and Cloud-native / Container Network Function (CNF). The system as provided by the present disclosure may comprise one or more components of the MANO architecture

[0100] , The MANO architecture

[0100] may be used to automatically instantiate the VNFs into the corresponding environment of the present disclosure so that it could help in onboarding other vendor(s) CNFs and VNFs to the platform. In an implementation, the system may comprise a NFV Platform Decision Analytics (NPDA)

[1096] component.

[0045] As shown in FIG. 1, the MANO architecture

[0100] comprises a user interface layer

[0102] , a network function virtualization (NFV) and software defined network (SDN) design function module

[0104] , a platform foundation services module

[0106] , a platform core services module

[0108] and a platform resource adaptors and utilities module

[0112] All the components may be assumed to be connected to each other in a manner as obvious to the person skilled in the art for implementing features of the present disclosure.

[0046] The NFV and SDN design function module

[0104] comprises a VNF lifecycle manager

[1042] , a VNF catalog

[1044] , a network services catalog

[1046] , a network slicing and service chaining manager

[1048] , a physical and virtual resource manager

[1050] and a CNF lifecycle manager

[1052] , The VNF lifecycle manager

[1042] may be responsible for deciding on which server of the communication network the microservice may be instantiated. The VNF lifecycle manager

[1042] may manage the overall flow of incoming / outgoing requests during interaction with the user. The VNF lifecycle manager

[1042] may be responsible for determining which sequence to be followed for executing the process. For e.g. in an AMF network function of the communication network (such as a 5G network), sequence for execution of processes Pl and P2 etc. The VNF catalog

[1044] stores the metadata of all the VNFs (also CNFs in some cases). The network services catalog

[1046] stores the information of the services that need to be run. The network slicing and service chaining manager

[1048] manages the slicing (an ordered and connected sequence of network service / network functions (NFs)) that must be applied to a specific networked data packet. The physical and virtual resource manager

[1050] stores the logical and physical inventory of the VNFs. Just like the VNF lifecycle manager

[1042] , the CNF lifecycle manager

[1052] may be similarly used for the CNFs lifecycle management.

[0047] The platforms foundation services module

[0106] comprises a microservices elastic load balancer

[1062] , an identity & access manager

[1064] , a command line interface (CLI)

[1066] , a central logging manager

[1068] , and an event routing manager

[1070] , The microservices elastic load balancer

[1062] may be used for maintaining the load balancing of the request for the services. The identity & access manager

[1064] may be used for logging purposes. The command line interface (CLI)

[1066] may be used to provide commands to execute certain processes which requires changes during the run time. The central logging manager

[1068] may be responsible for keeping the logs of every service. These logs are generated by the MANO platform

[0100] , These logs may be used for debugging purposes. The event routing manager

[1070] may be responsible for routing the events i.e., the application programming interface (API) hits to the corresponding services.

[0048] The platforms core services module

[0108] comprises NFV infrastructure monitoring manager

[1082] , an assure manager

[1084] , a performance manager

[1086] , a policy execution engine

[1088] , a capacity monitoring manager

[1090] , a release management (mgmt.) repository

[1092] , a configuration manager & golden configuration template (GCT)

[1094] , an NFV platform decision analytics

[1096] , a platform NoSQL DB

[1098] , a platform schedulers and cron jobs

[1100] , a VNF backup & upgrade manager

[1102] , a micro service auditor

[1104] , and a platform operations, administration and maintenance manager

[1106] , The NFV infrastructure monitoring manager

[1082] may monitor the infrastructure part of the NFs. For e.g., any metrics such as CPU utilization by the VNF. The assure manager

[1084] may be responsible for supervising the alarms the vendor may be generating. The performance manager

[1086] may be responsible for managing the performance counters. The policy execution engine (PEE)

[1088] may be responsible for managing all the policies. The capacity monitoring manager (CMM)

[1090] may be responsible for sending the request to the PEE

[1088] , The release management repository (RMR)

[1092] may be responsible for managing the releases and the images of all of the vendor’s network nodes. The configuration manager & GCT

[1094] manages the configuration and GCT of all the vendors. The NFV platform decision analytics (NPDA)

[1096] helps in deciding the priority of using the network resources. It is further noted that the policy execution engine (PEE)

[1088] , the configuration manager & (GCT)

[1094] and the (NPDA)

[1096] work together. The platform NoSQL DB

[1098] may be a platform database for storing all the inventory (both physical and logical) as well as the metadata of the VNFs and CNF. It may be noted that the platform NoSQL DB

[1098] may be just a narrower implementation of the present disclosure, and any other kind of structure for the database may be implemented for the platformdatabase such as relational or non-relational database. The platform schedulers and cron jobs

[1100] may schedule the task such as but not limited to triggering of an event, traverse the network graph etc. The VNF backup & upgrade manager

[1102] takes backup of the images, binaries of the VNFs and the CNFs and produces those backups on demand in case of server failure. The microservice auditor

[1104] audits the microservices. For e.g., in a hypothetical case, instances not being instantiated by the MANO architecture

[0100] may be using the network resources. In such case, the microservice auditor

[1104] audits and informs the same so that resources can be released for services running in the MANO architecture

[0100] , The audit assures that the services only run on the MANO platform

[0100] , The platform operations, administration and maintenance manager

[1106] may be used for newer instances that are spawning.

[0049] The platform resource adaptors and utilities module

[0112] further comprises a platform external API adaptor and gateway

[1122] , a generic decoder and indexer (XML, CSV, JSON)

[1124] , a service adaptor

[1126] , an API adaptor

[1128] , and aNFV gateway

[1130] , The platform external API adaptor and gateway

[1122] may be responsible for handling the external services (to the MANO platform

[0100] ) that requires the network resources. The generic decoder and indexer (XML, CSV, JSON)

[1124] may get directly the data of the vendor system in the XML, CSV, JSON format. The service adaptor

[1126] may be the interface provided between the telecom cloud and the MANO architecture

[0100] for communication. The Service Adaptor (SA) is a microservices-based system designed to deploy and manage Container Network Functions (CNFs) and their components (CNFCs) across nodes. It offers REST endpoints for key operations, including uploading container images to a registry, terminating CNFC instances, and creating volumes and networks. CNFs, which are network functions packaged as containers, may consist of multiple CNFCs. The Service Adaptor facilitates the deployment, configuration, and management of these components by interacting with API, ensuring proper setup and scalability within a containerized environment. This approach provides a modular and flexible framework for handling network functions in a virtualized network setup.

[0050] The API adaptor

[1128] may be used to connect with the virtual machines (VMs). The NFV gateway

[1130] may be responsible for providing the path to each services going to / incoming from the MANO architecture

[0100] ,

[0051] FIG. 2 illustrates an exemplary block diagram of a computing device

[0200] upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure. In an implementation, the computing device

[0200] mayalso implement a method for managing environment variables for Container Network Function Components (CNFCs) in a network environment, utilising the system. In another implementation, the computing device

[0200] itself implements the method for managing environment variables for Container Network Function Components (CNFCs) in a network environment, using one or more units configured within the computing device

[0200] , wherein said one or more units are capable of implementing the features as disclosed in the present disclosure.

[0052] The computing device

[0200] may include a bus

[0202] or other communication mechanism for communicating information, and a hardware processor

[0204] coupled with bus

[0202] for processing information. The hardware processor

[0204] may be, for example, a general-purpose microprocessor. The computing device

[0200] may also include a main memory

[0206] , such as a random-access memory (RAM), or other dynamic storage device, coupled to the bus

[0202] for storing information and instructions to be executed by the processor

[0204] , The main memory

[0206] also may be used for storing temporary variables or other intermediate information during execution of the instructions to be executed by the processor

[0204] , Such instructions, when stored in non-transitory storage media accessible to the processor

[0204] , render the computing device

[0200] into a special-purpose machine that is customized to perform the operations specified in the instructions. The computing device

[0200] further includes a read only memory (ROM)

[0208] or other static storage device coupled to the bus

[0202] for storing static information and instructions for the processor

[0204] ,

[0053] A storage device

[0210] , such as a magnetic disk, optical disk, or solid-state drive is provided and coupled to the bus

[0202] for storing information and instructions. The computing device

[0200] may be coupled via the bus

[0202] to a display

[0212] , such as a cathode ray tube (CRT), Liquid crystal Display (LCD), Light Emitting Diode (LED) display, Organic LED (OLED) display, etc. for displaying information to a computer user. An input device

[0214] , including alphanumeric and other keys, touch screen input means, etc. may be coupled to the bus

[0202] for communicating information and command selections to the processor

[0204] , Another type of user input device may be a cursor controller

[0216] , such as a mouse, a trackball, or cursor direction keys, for communicating direction information and command selections to the processor

[0204] , and for controlling cursor movement on the display

[0212] , This input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allow the device to specify positions in a plane.

[0054] The computing device

[0200] may implement the techniques described herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware and / or program logic which in combination with the computing device

[0200] causes or programs the computing device

[0200] to be a special-purpose machine. According to one implementation, the techniques herein are performed by the computing device

[0200] in response to the processor

[0204] executing one or more sequences of one or more instructions contained in the main memory

[0206] , Such instructions may be read into the main memory

[0206] from another storage medium, such as the storage device

[0210] , Execution of the sequences of instructions contained in the main memory

[0206] causes the processor

[0204] to perform the process steps described herein. In alternative implementations of the present disclosure, hard-wired circuitry may be used in place of or in combination with software instructions.

[0055] The computing device

[0200] also may include a communication interface

[0218] coupled to the bus

[0202] , The communication interface

[0218] provides a two-way data communication coupling to a network link

[0220] that is connected to a local network

[0222] , For example, the communication interface

[0218] may be an integrated services digital network (ISDN) card, cable modem, satellite modem, or a modem to provide a data communication connection to a corresponding type of telephone line. As another example, the communication interface

[0218] may be a local area network (LAN) card to provide a data communication connection to a compatible LAN. Wireless links may also be implemented. In any such implementation, the communication interface

[0218] sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information.

[0056] The computing device

[0200] can send messages and receive data, including program code, through the network(s), the network link

[0220] and the communication interface

[0218] , In the Internet example, a server

[0230] might transmit a requested code for an application program through the Internet

[0228] , the ISP

[0226] , the local network

[0222] , the host

[0224] and the communication interface

[0218] , The received code may be executed by the processor

[0204] as it is received, and / or stored in the storage device

[0210] , or other non-volatile storage for later execution.

[0057] Referring to FIG. 3, an exemplary block diagram of a system

[0300] for managing environment variables for Container Network Function Components (CNFCs) in a network environment, is shown, in accordance with the exemplary implementations of the present disclosure. In one example, the system

[0300] may be implemented as or within a physical & virtual inventory manager (PVIM) unit.

[0058] In another example, as depicted in FIG. 3, the system

[0300] may include the physical & virtual inventory manager (PVIM) unit [300A], The PVIM unit [300 A] may include at least one transceiver unit

[0302] , at least one processing unit

[0304] , and at least one storage unit

[0306] ,

[0059] The system

[0300] may also include additional components in communication with the physical & virtual inventory manager (PVIM) unit [300A], which have not been depicted in FIG. 3, and would be understood to a person skilled in the art.

[0060] All of the components / units of the system

[0300] are assumed to be connected to each other unless otherwise indicated below. As shown in FIG. 3, all units shown within the system

[0300] should also be assumed to be connected to each other. Also, in FIG. 3 only a few units are shown, however, the system

[0300] may comprise multiple such units or the system

[0300] may comprise any such numbers of said units, as required to implement the features of the present disclosure. Further, in an implementation, the system

[0300] may be present in a user device / user equipment to implement the features of the present disclosure. The system

[0300] may be a part of the user device / or may be independent of but in communication with the user device (may also referred herein as a UE). In another implementation, the system

[0300] may reside in a server or a network entity. In yet another implementation, the system

[0300] may reside partly in the server / network entity and partly in the user device.

[0061] The system

[0300] is configured for managing environment variables for Container Network Function Components (CNFCs) in a network environment, with the help of the interconnection between the components / units of the system

[0300] , The management is made possible through the interconnection and communication between various components of the system

[0300] ,

[0062] It may be further noted that the system

[0300] may be in various network entities / components known to a person skilled in the art, which have not been depicted in FIG. 3 and not explained here.

[0063] In operation, the transceiver unit

[0302] may receive a reserve request from a Container Network Function Lifecycle Manager (CNFLM). The reserve request may include a set of environment variables for at least a CNFC.

[0064] In an implementation of the present disclosure, the PVIM [300A], based on the reserve request, may be responsible for managing the lifecycle of one or more Container Network Functions (CNFCs). A CNFC refers to a network function that is deployed and executed in a containerized environment, often as part of a larger network service infrastructure.

[0065] The reserve request includes a set of environment variables that are important for the instantiation and operation of the CNFC. These environment variables define specific configuration settings, such as memory allocation, networking parameters, and resource limits, which are necessary for deploying the CNFC within the network environment. The PVIM unit [300A] is used for managing both physical and virtual resources across the network.

[0066] In another example, the set of environment variables for at least the CNFC, as included in the reserve request, may be received in a compressed format.

[0067] As would be understood and in the context of the present subject matter, compressed format may indicate that the set of environment variables is transmitted in a reduced size data format. Compression techniques are active to reduce the size of the data package, which is especially useful when dealing with largescale networks or environments with bandwidth limitations.

[0068] Examples of such compressed formats may include, but are not limited to, JSON (JavaScript Object Notation), XML (Extensible Markup Language), TAR (Tape Archive), and ZIP. It may be further noted that such types of compressed formats are only exemplary, and in no manner is construed to limit the scope of the present subject matter in any manner. Any other formats may also be used, and would lie within the scope of the present subject matter.

[0069] In such cases where the environment variables are received in the compressed format, upon receiving the reserve request, the PVIM unit [300 A] may decompress the environment variables. This process restores the environment variables to their original format.

[0070] Continuing further, in one example, the set of environment variables with at least the CNFC may be configured by a service manager during an instantiation of at least the CNFC.

[0071] The service manager refers to the orchestration tool responsible for configuring the environment in which the CNFC will operate. The service manager may act as an intermediary between the CNFLM and the PVIM. The set of environment variables contains configuration dataessential for the functioning of the CNFC, such as network settings, resource allocation, CPU and memory limits, and other operational parameters. The configurations may include details such as container specific resource limits, network configurations, storage requirements, or other dependencies that the CNFC needs to function correctly.

[0072] Examples of such environment variables, as configured by the service manager, may include, but are not limited to, cnfc-name, circle name, product version, ipv4, ipv6, cnfc id, created time, cnfc site name, cnfc site id, env id, status.

[0073] It may be noted that the aforementioned exemplary environment variables may be configured by the service manager during instantiation of the CNFC. For example, the service manager may use ‘cnfc site name’ and ‘cnfc site id’ to locate host and CNFC where the environment variable are to be configured.

[0074] Continuing further, in such cases, the PVIM unit [300A], upon receiving the reserve request and the environment variables (as explained in the previous step), may then retrieve the details of said set of environment variables from the CNFLM via the service manager. The details of the environment variables may be understood as values of the configuration settings of the environment variables as configured by the service manager.

[0075] The retrieval process performed by the PVIM unit is for confirming that the correct configuration is applied to the CNFC. By obtaining the details of the environment variables from the CNFLM through the service manager, the PVIM unit confirms that it has access to the most up to date information needed to allocate and manage resources.

[0076] In another example, the set of environment variables for at least the CNFC may be provided at the CNFLM by a user of the network environment.

[0077] The user refers to a network administrator or operator who manually defines the environment variables required for the deployment or management of the CNFC. In one example, the user of the network environment may interact directly with the CNFLM, using a User Interface, such as a Graphical User Interface (GUI) or a Command Line Interface (CLI). In another example, in the case of the user using a GUI to interact with the CNFLM, the GUI may include a set of already configured deployment profiles. Each of the deployment profile may include a number ofCNFCs and some set of environment variables. In such cases, the user may need to select or opt for one of the already configured deployment profile.

[0078] However, it may be noted that the aforementioned example is only exemplary, and in no manner is construed to limit the scope of the present subject matter in any manner. The user may provide the set of environment variables to the CNFLM in any other manner as well. All such examples would lie within the scope of the present subject matter.

[0079] Once the CNFLM receives the environment variables from the user, it processes them and transmits the same to the Physical & Virtual Inventory Manager (PVIM) unit [300 A] for managing the resources needed for deploying the CNFC.

[0080] Continuing further, once the environment variables are retrieved, the processing unit

[0304] may set a reserved status associated with the set of environment variables based on the reserve request.

[0081] The processing unit

[0304] is responsible for processing the reserve request, which contains the configuration and resource requirements for deploying the CNFC. The reserved status refers to a state in which the environment variables, and the associated resources, are marked as allocated or reserved for the upcoming CNFC instantiation. By setting the reserved status, the processing unit

[0304] signals that the environment variables are now ready for deployment and that the resources associated with them are allocated within the network infrastructure.

[0082] Continuing further, thereafter, the transceiver unit

[0302] may transmit details of the set of environment variables and the reserved status to a Policy Execution Engine (PEEGN) node.

[0083] The Policy Execution Engine (PEEGN) node is responsible for managing and enforcing network policies, which may include resource allocation policies, security protocols, or operational constraints associated with the deployment of network functions, such as the Container Network Function Component (CNFC). The details of the set of environment variables, which defines the configuration parameters of the CNFC (such as memory, CPU, networking settings, and storage), along with the reserved status, indicating that the necessary resources have been allocated, are transmitted to the PEEGN.

[0084] The PEEGN node uses this information to validate whether the resource allocation complies with predefined network policies and whether the CNFC may be instantiated or modified without causing conflicts within the network.

[0085] After the PVIM has transmitted the environment variables and reserved status to the Policy Execution Engine (PEEGN) node, the transceiver unit

[0302] may receive, at the PVIM unit [300A], from the CNFLM, an update inventory request associated with one or more environment variables from the set of environment variables.

[0086] The update inventory request is sent by the CNFLM, which manages the lifecycle of the Container Network Functions (CNFCs). The request indicates that a modification, reconfiguration, or update is required for one or more of the previously defined environment variables. These variables are for the proper functioning of the CNFC within the containerized network.

[0087] The update inventory request signals the need to adjust the resources associated with the CNFC, which could occur for several reasons, such as a change in resource requirements during the lifecycle of the CNFC. Upon receiving this update inventory request, the PVIM unit [300A] will process the changes and update its inventory of resources.

[0088] In an example, the CNFLM is configured to transmit the update inventory request associated with one or more environment variables, in an event a successful instantiation of at least the CNFC is performed by the service manager.

[0089] The instantiation refers to the process of deploying and configuring the CNFC, making it operational within the network. Once the CNFC is successfully instantiated, meaning it has been deployed with the correct settings and is functioning, the CNFLM issues an update inventory request to notify the PVIM unit [300A], The update inventory request communicates that one or more environment variables related to the CNFC may need to be updated. This update may reflect changes in resource usage, updated or any modifications that occurred during the instantiation process.

[0090] In another example, the CNFLM is configured to transmit the update inventory request associated with one or more environment variables, in an event a successful termination of at least the CNFC is performed by the service manager.

[0091] The termination refers to the process of stopping or shutting down the CNFC, confirming that all ongoing processes are completed and resources are released properly. Once the CNFC has been successfully terminated, which indicates that it has finished its tasks without issues, the CNFLM sends an update inventory request to inform the PVIM unit [300A],

[0092] This update inventory request serves to update the PVIM unit [300 A] regarding the state of one or more environment variables associated with the CNFC. The environment variables may need to be adjusted to reflect any changes in the configuration settings that were in effect during the CNFC's operation. This may include updates related to resource allocation, such as freeing up CPU and memory that were previously assigned to the CNFC.

[0093] Upon receiving the update inventory request, the processing unit

[0304] may set a status of the one or more environment variables based on the update inventory request.

[0094] In an example, the status is set to ‘used’ in an event the successful instantiation of at least the CNFC is performed by the service manager. As would be understood, successful instantiation may mean that CNFCs have been successfully instantiated and the resources are utilized by the CNFCs, and may not be available for further use at the moment.

[0095] In another example, the status is set to a free status in an event the successful termination of at least the CNFC is performed by the service manager.

[0096] When the CNFC is successfully terminated, it means that it has been shut down in a controlled manner. This successful termination indicates that the environment variables linked to the CNFC are no longer in use and that the resources previously allocated to it can now be reclaimed.

[0097] Upon receiving confirmation of the successful termination at the CNFLM, the Physical & Virtual Inventory Manager (PVIM) unit [300 A] sets the status of the relevant environment variables to ‘free status’ based on receiving update inventory request from CNFLM.

[0098] In yet another example, the status is set to a ‘free status’ in an event a failed instantiation of at least the CNFC is performed by the service manager.

[0099] When the instantiation of the CNFC fails, it means that the resources that were allocated for this process were not successfully used, and are now available to be used again. The environment variables associated with the CNFC need to be updated to reflect this failure.

[0100] Upon identifying that the instantiation attempt has failed, the PVIM unit [300A] updates the status of the relevant environment variables to free status. This indicates that the resources previously allocated for the failed instantiation are now available for reuse.

[0101] Referring to FIG. 4, an exemplary method flow diagram

[0400] for managing environment variables for Container Network Function Components (CNFCs) in a network environment, in accordance with exemplary implementations of the present disclosure is shown. In an implementation the method

[0400] is performed by the system

[0300] , Further, in an implementation, the system

[0300] may be present in a server device to implement the features of the present disclosure. Also, as shown in FIG. 4, the method

[0400] starts at Step

[0402] .

[0102] At Step

[0404] , the method

[0400] comprises receiving, by a transceiver unit

[0302] at a Physical & Virtual Inventory Manager (PVIM) unit [300A], from a Container Network Function Lifecycle Manager (CNFLM), a reserve request comprising a set of environment variables for at least a CNFC.

[0103] In operation, the transceiver unit

[0302] may receive a reserve request from a Container Network Function Lifecycle Manager (CNFLM). The reserve request may include a set of environment variables for at least a CNFC.

[0104] In an implementation of the present disclosure, the PVIM [300A], based on the reserve request, may be responsible for managing the lifecycle of one or more Container Network Functions (CNFCs).

[0105] The reserve request includes a set of environment variables that are important for the instantiation and operation of the CNFC. These environment variables define specific configuration settings, such as memory allocation, networking parameters, and resource limits, which are necessary for deploying the CNFC within the network environment. The PVIM unit [300A] is used for managing both physical and virtual resources across the network.

[0106] In another example, the set of environment variables for at least the CNFC, as included in the reserve request, may be received in a compressed format. In such cases where the environment variables are received in the compressed format, upon receiving the reserve request, the PVIM unit [300A] may decompress the environment variables. This process restores the environment variables to their original format.

[0107] Continuing further, in one example, the set of environment variables with at least the CNFC may be configured by a service manager during an instantiation of at least the CNFC. In such cases, the PVIM unit [300A], upon receiving the reserve request and the environment variables (as explained in the previous step), may then retrieve the details of said set of environment variables from the CNFLM via the service manager. The details of the environment variables may be understood as values of the configuration settings of the environment variables as configured by the service manager.

[0108] In another example, the set of environment variables for at least the CNFC may be provided at the CNFLM by a user of the network environment. The user of the network environment, using a User Interface, such as a Graphical User Interface (GUI) or a Command Line Interface (CLI) may interact directly with the CNFLM. Once the CNFLM receives the environment variables from the user, it processes them and transmits the same to the Physical & Virtual Inventory Manager (PVIM) unit [300 A] for managing the resources needed for deploying the CNFC.

[0109] At Step

[0406] , the method

[0400] comprises setting, by a processing unit

[0304] at the PVIM unit [300A], a reserved status associated with the set of environment variables based on the reserve request.

[0110] Continuing further, once the environment variables are retrieved, the processing unit

[0304] may set a reserved status associated with the set of environment variables based on the reserve request.[OHl] The processing unit

[0304] is responsible for processing the reserve request, which contains the configuration and resource requirements for deploying the CNFC. The reserved status refers to a state in which the environment variables, and the associated resources, are marked as allocated or reserved for the upcoming CNFC instantiation. By setting the reserved status, the processing unit

[0304] signals that the environment variables are now ready for deployment and that the resources associated with them are allocated within the network infrastructure.

[0112] At Step

[0408] , the method

[0400] comprises transmitting, by the transceiver unit

[0302] at the PVIM unit [300A], to a Policy Execution Engine (PEEGN) ode, details of the set of environment variables and the reserved status.

[0113] Continuing further, thereafter, the transceiver unit

[0302] may transmit details of the set of environment variables and the reserved status to a Policy Execution Engine (PEEGN) node.

[0114] The Policy Execution Engine (PEEGN) node is responsible for managing and enforcing network policies, which may include resource allocation policies, security protocols, or operational constraints associated with the deployment of network functions, such as the Container Network Function Component (CNFC). The details of the set of environment variables, which defines the configuration parameters of the CNFC (such as memory, CPU, networking settings, and storage), along with the reserved status, indicating that the necessary resources have been allocated, are transmitted to the PEEGN.

[0115] The PEEGN node uses this information to validate whether the resource allocation complies with predefined network policies and whether the CNFC may be instantiated or modified without causing conflicts within the network.

[0116] At Step

[0410] , the method

[0400] receiving, by the transceiver unit

[0302] at the PVIM unit [300A], from the CNFLM, an update inventory request associated with one or more environment variables from the set of environment variables.

[0117] After the PVIM has transmitted the environment variables and reserved status to the Policy Execution Engine (PEEGN) node, the transceiver unit

[0302] may receive, at the PVIM unit [300A], from the CNFLM, an update inventory request associated with one or more environment variables from the set of environment variables.

[0118] The update inventory request is sent by the CNFLM, which manages the lifecycle of the Container Network Functions (CNFCs). The request indicates that a modification, reconfiguration, or update is required for one or more of the previously defined environment variables. These variables are for the proper functioning of the CNFC within the containerized network.

[0119] The update inventory request signals the need to adjust the resources associated with the CNFC, which could occur for several reasons, such as a change in resource requirements during the lifecycle of the CNFC. Upon receiving this update inventory request, the PVIM unit [300A] will process the changes and update its inventory of resources.

[0120] In an example, the CNFLM is configured to transmit the update inventory request associated with one or more environment variables in an event a successful instantiation of at least the CNFC is performed by the service manager.

[0121] The instantiation refers to the process of deploying and configuring the CNFC, making it operational within the network. Once the CNFC is successfully instantiated, meaning it has been deployed with the correct settings and is functioning, the CNFLM issues an update inventory request to notify the PVIM unit [300A], The update inventory request communicates that one or more environment variables related to the CNFC may need to be updated. This update may reflect changes in resource usage, updated or any modifications that occurred during the instantiation process.

[0122] In another example, the CNFLM is configured to transmit the update inventory request associated with one or more environment variables in an event a successful termination of at least the CNFC is performed by the service manager.

[0123] The termination refers to the process of stopping or shutting down the CNFC, confirming that all ongoing processes are completed and resources are released properly. Once the CNFC has been successfully terminated, which indicates that it has finished its tasks without issues, the CNFLM sends an update inventory request to inform the PVIM unit [300A],

[0124] This update inventory request serves to update the PVIM unit [300 A] regarding the state of one or more environment variables associated with the CNFC. The environment variables may need to be adjusted to reflect any changes in the configuration settings that were in effect during the CNFC's operation. This may include updates related to resource allocation, such as freeing up CPU and memory that were previously assigned to the CNFC.

[0125] At Step

[0412] , the method

[0400] comprises setting, by the processing unit

[0304] at the PVIM unit [300 A], a status of the one or more environment variables based on the update inventory request.

[0126] Upon receiving the update inventory request, the processing unit

[0304] may set a status of the one or more environment variables based on the update inventory request.

[0127] In an example, the status is set to ‘used’ in an event the successful instantiation of at least the CNFC is performed by the service manager. As would be understood, successful instantiation may mean that CNFCs have been successfully instantiated and the resources are utilized by the CNFCs, and may not be available for further use at the moment.

[0128] In another example, the status is set to a free status in an event the successful termination of at least the CNFC is performed by the service manager.

[0129] When the CNFC is successfully terminated, it means that it has been shut down in a controlled manner. This successful termination indicates that the environment variables linked to the CNFC are no longer in use and that the resources previously allocated to it can now be reclaimed.

[0130] Upon receiving confirmation of the successful termination at the CNFLM, the Physical & Virtual Inventory Manager (PVIM) unit [300 A] sets the status of the relevant environment variables to ‘free status’ based on receiving update inventory request from CNFLM.

[0131] In yet another example, the status is set to a ‘free status’ in an event a failed instantiation of at least the CNFC is performed by the service manager.

[0132] When the instantiation of the CNFC fails, it means that the resources that were allocated for this process were not successfully used, and are now available to be used again. The environment variables associated with the CNFC need to be updated to reflect this failure.

[0133] Upon identifying that the instantiation attempt has failed, the PVIM unit [300A] updates the status of the relevant environment variables to free status. This indicates that the resources previously allocated for the failed instantiation are now available for reuse.

[0134] Thereafter, the method terminates at Step

[0414] .

[0135] FIG. 5 illustrates an exemplary signalling diagram

[0500] for managing environment variables for Container Network Function Components (CNFCs) in a network environment during CNF instantiation, in accordance with exemplary implementations of the present disclosure.

[0136] The process begins when a user (a network administrator or operator) initiates a CNF instantiation request from the user interface

[0502] , This request is the starting point for deploying the Container Network Function Component (CNFC). After the instantiation request is initiated by the user at the UI, it is passed on to the CNFLM

[0504] , as depicted by Step

[0516] , The CNFLM

[0504] refers to the container network function lifecycle manager that manages the resource allocations and lifecycle of the CNFs deployed and configured within the network infrastructure.

[0137] The CNF instantiation request, also referred to as reserve request, may include a set of environment variables that may be important for the instantiation and operation of the CNFC. These environment variables define specific configuration settings, which may be necessary for deploying the CNFC within the network.

[0138] On receiving the request from the User Interface

[0502] and the included environment variables, the CNFLM processes the same and transmits the request to the PVIM

[0508] , This has been depicted by Step

[0518] in FIG. 5.

[0139] Upon receiving the reservation request from the CNFLM

[0504] , the PVIM

[0508] takes control. The PVIM

[0508] handles the actual allocation of physical and virtual resources. The PVIM then sets a reserved status of the environment variables (as associated with CPU, memory, and network configurations). Such ‘reserved status’ may indicate that the environment variables and the associated resources have been marked as allocated or reserved for the upcoming CNFC instantiation. The PVIM then sends a reservation acknowledgement back to the CNFLM, depicted by Step

[0520] , confirming that the ‘reserved status’ for the environment variables has been set.

[0140] Thereafter, as depicted in FIG. 5, the process of instantiation of the CNFC may be initiated.

[0141] The CNFLM

[0504] may transmit the Instantiation Request to the Service Adaptor

[0510] , as depicted by Step

[0522] in FIG. 5.

[0142] The Service Adaptor

[0510] may be referred and understood as the Service Adaptor

[1126] explained in conjunction with FIG. 1. The Service Adaptor

[0510] coordinates the interactionbetween the PVIM

[0508] and the network’s physical host

[0512] to forward the instantiate CNF request message to the Host

[0512] , as depicted by Step

[0524] in FIG. 5.

[0143] The Host is where the CNFC

[0504] is physically located. It is responsible for actually running the CNFC

[0504] within the network infrastructure. Once the CNFC

[0504] is instantiated, the Host

[0512] sends back an instantiation status to the Service Adaptor, as depicted by Step

[0526] in FIG. 5. The Service Adaptor

[0510] may accordingly transmit an acknowledgement to the PVIM

[0508] , depicted by Step

[0528] to update the progress of the deployment.

[0144] Once the instantiation process has been completed, the CNFLM

[0504] may issue an update inventory request to notify the PVIM, as depicted by Step

[0530] in FIG. 5. The update inventory request may notify the PVIM that the CNFC has been initiated, and the resources status may need to be adjusted. On receiving the update inventory request, in the present example, the PVIM unit may set the status of the environment variables to ‘used’ indicating that CNFC has been initiated and the resources are no longer available to be used again at the moment.

[0145] Once the inventory is updated, an update inventory acknowledgement is sent by the PVIM to CNFLM, depicted by Step

[0532] , to confirm the status change.

[0146] Thereafter, the CNFLM transmits the update instantiation status message to a Resource Management Repository (RMR)

[0514] , as depicted by Step

[0534] in FIG. 5, indicating the final status of the CNFC instantiation. The RMR (resource management repository) logs and manages the state of the resources. The RMR

[0514] then sends an acknowledgement back to CNFLM, depicted by Step

[0536] in FIG. 5, confirming that the CNFC

[0504] instantiation status has been successfully updated in the system. After all updates are processed, the CNF instantiation acknowledgement is returned from the CNFLM to the user interface

[0502] , depicted by Step

[0538] , indicating that the CNFC

[0504] has been successfully instantiated and the resources have been allocated and updated as per the reserve request.

[0147] FIG. 6 illustrates an exemplary signalling diagram

[0600] for managing environment variables for Container Network Function Components (CNFCs) in a network environment during CNF termination, in accordance with exemplary implementations of the present disclosure.

[0148] As depicted in FIG. 6, the process begins when a user (a network administrator or operator) initiates a CNF termination request from the user interface

[0502] , This request is the starting pointfor terminating the Container Network Function (CNFC). After the termination request is initiated by the user at the UI, it is passed on to the CNFLM

[0504] , as depicted by Step

[0602] ,

[0149] On receiving the CNF termination request, the CNFLM

[0504] may transmit the Termination Request to the Service Adaptor

[0510] , as depicted by Step

[0604] in FIG. 6.

[0150] The Service Adaptor coordinates the interaction between the PVIM

[0508] and the network’s physical host

[0512] to forward the terminate CNF request message to the Host

[0512] , as depicted by Step

[0606] in FIG. 6.

[0151] Once the CNFC

[0504] is terminated, the Host

[0512] sends back a termination status to the Service Adaptor, as depicted by Step

[0608] in FIG. 6. The Service Adaptor

[0510] may accordingly transmit an acknowledgement to the PVIM

[0508] , depicted by Step

[0610] to update the progress of the termination.

[0152] Once the termination process has been completed, the CNFLM

[0504] may issue an update inventory request to notify the PVIM, as depicted by Step

[0612] in FIG. 6. The update inventory request may notify the PVIM that the CNFC has been terminated, and the resources status may need to be adjusted. On receiving the update inventory request, in the present example, the PVIM unit may set the status of the environment variables to ‘free’ indicating that CNFC has been terminated and the resources are available to be used again.

[0153] Once the inventory is updated, an update inventory acknowledgement is sent by the PVIM to CNFLM, depicted by Step

[0614] , to confirm the status change.

[0154] Thereafter, the CNFLM transmits the update instantiation status message to a Resource Management Repository (RMR)

[0514] , as depicted by Step

[0616] in FIG. 6, indicating the final status of the CNFC termination. As would be understood the RMR (resource management repository) logs and manages the state of the resources. The RMR

[0514] then sends an acknowledgement back to CNFLM, depicted by Step

[0618] in FIG. 6, confirming that the CNFC

[0504] termination status has been successfully updated in the system. After all updates are processed, the CNF termination acknowledgement is returned from the CNFLM to the user interface

[0502] , depicted by Step

[0620] , indicating that the CNFC

[0504] has been successfully terminated and the resources have been freed and updated as per the reserve request.

[0155] The present disclosure further discloses a non-transitory computer readable storage medium storing instructions for managing environment variables for Container Network Function Components (CNFCs) in a network environment. The instructions include executable code which, when executed by one or more units of a system, causes a transceiver unit

[0302] , at a physical & virtual inventory manager (PVIM) unit [300A], of the system to receive a reserve request from a container network function lifecycle manager (CNFLM). The reserve request comprises a set of environment variables for at least a CNFC. Further, the instructions include executable code which, when executed, causes a processing unit

[0304] , at the PVIM unit, to set a reserved status associated with the set of environment variables based on the reserve request. Further, the instructions include executable code which, when executed, causes the transceiver unit

[0302] , at the PVIM unit, to transmit details of the set of environment variables and the reserved status to a Policy Execution Engine (PEEGN) node. Further, the instructions include executable code which, when executed, causes the transceiver unit

[0302] , at the PVIM unit, to receive an update inventory request from the CNFM. The update inventory request is associated with one or more environment variables from the set of environment variables. Further, the instructions include executable code which, when executed, causes the processing unit

[0304] , at the PVIM unit [300A], to set a status of the one or more environment variables based on the update inventory request.

[0156] As is evident from the above, the present disclosure provides a technically advanced solution for managing environment variables for Container Network Function Components (CNFCs) in a network environment. The present system and method provide a solution, which assigns environment variables at run time to any of required CNFC. The present system and method enable the maintenance of set of environment variables in inventory for all the CNFC’s of particular CNF, where environment variables are required to be set at the time of instantiation. The present system and method provide a solution, which reserve set of environment variables for instantiation, un-reserve environment variables if instantiation gets failed, mark set of environment variables as ‘used’ for successful instantiation and mark set of environment variables as ‘free’ after successful termination of instantiation. The present system and method provide a solution, which enables to Service Adaptor for using the environment files assigned to particular CNFC at the time of instantiation and set those environment variables as per mentioned key values in file. The present system and method provide a solution, which enables async event-based implementation and auto sync inventory based on instantiation resource usages.

[0157] While considerable emphasis has been placed herein on the disclosed implementations, it will be appreciated that many implementations can be made and that many changes can be madeto the implementations without departing from the principles of the present disclosure. These and other changes in the implementations of the present disclosure will be apparent to those skilled in the art, whereby it is to be understood that the foregoing descriptive matter to be implemented is illustrative and non-limiting.

[0158] Further, in accordance with the present disclosure, it is to be acknowledged that the functionality described for the various components / units can be implemented interchangeably. While specific embodiments may disclose a particular functionality of these units for clarity, it is recognized that various configurations and combinations thereof are within the scope of the disclosure. The functionality of specific units as disclosed in the disclosure should not be construed as limiting the scope of the present disclosure. Consequently, alternative arrangements and substitutions of units, provided they achieve the intended functionality described herein, are considered to be encompassed within the scope of the present disclosure.

Claims

We Claim:

1. A method for managing environment variables for Container Network Function Components (CNFCs) in a network environment, the method comprising: receiving, by a transceiver unit [302] at a physical & virtual inventory manager (PVIM) unit [300 A], from a container network function lifecycle manager (CNFLM), a reserve request comprising a set of environment variables for at least a CNFC; setting, by a processing unit [304] at the PVIM unit [300A], a reserved status associated with the set of environment variables based on the reserve request; transmitting, by the transceiver unit [302] at the PVIM unit [300A], to a Policy Execution Engine (PEEGN) node, details of the set of environment variables and the reserved status; receiving, by the transceiver unit [302] at the PVIM unit [300 A], from the CNFLM, an update inventory request associated with one or more environment variables from the set of environment variables; and setting, by the processing unit [304] at the PVIM unit [300A], a status of the one or more environment variables based on the update inventory request.

2. The method as claimed in claim 1, further comprising: retrieving, by the processing unit at the PVIM unit [300A], from the CNFLM via a service manager, the details of the set of environment variables.

3. The method as claimed in claim 2, wherein the set of environment variables with at least the CNFC are configured by the service manager during an instantiation of at least the CNFC.

4. The method as claimed in claim 1, wherein the update inventory request associated with one or more environment variables is transmitted by the CNFLM in an event a successful instantiation of at least the CNFC is performed by a service manager.

5. The method as claimed in claim 1, wherein the update inventory request associated with one or more environment variables is transmitted by the CNFLM in an event a successful termination of at least the CNFC is performed by a service manager.

6. The method as claimed in claim 1, wherein the status is set to a free status in an event the successful termination of at least the CNFC is performed by a service manager.

7. The method as claimed in claim 1, wherein the status is set to a free status in an event a failed instantiation of at least the CNFC is performed by a service manager.

8. The method as claimed in claim 1, wherein the set of environment variables for at least the CNFC is received in a compressed format.

9. The method as claimed in claim 1, wherein the set of environment variables for at least the CNFC is provided at the CNFLM by a user of the network environment.

10. A system for managing environment variables for Container Network Function Components (CNFCs) in a network environment, the system comprising a Physical & Virtual Inventory Manager (PVIM) unit [300A], the PVIM unit [300 A] comprising: a transceiver unit [302] configured to receive, from a container network function lifecycle manager (CNFLM), a reserve request comprising a set of environment variables for at least a CNFC; a processing unit [304] connected to at least the transceiver unit [302], wherein the processing unit [304] configured to set a reserved status associated with the set of environment variables based on the reserve request; the transceiver unit [302] further configured to: o transmit, to a Policy Execution Engine (PEEGN) node, details of the set of environment variables and the reserved status; and o receive, from the CNFLM, an update inventory request associated with one or more environment variables from the set of environment variables; and the processing unit [304] further configured to set a status of the one or more environment variables based on the update inventory request.

11. The system as claimed in claim 10, wherein the processing unit is further configured to: retrieve, from the CNFLM via a service manager, the details of the set of environment variables.

12. The system as claimed in claim 11, wherein the set of environment variables with at least the CNFC are configured by the service manager during an instantiation of at least the CNFC.

13. The system as claimed in claim 10, wherein the update inventory request associated with one or more environment variables, the CNFLM configured to transmit in an event a successful instantiation of at least the CNFC is performed by a service manager.

14. The system as claimed in claim 10, wherein the update inventory request associated with one or more environment variables, the CNFLM is configured to transmit in an event a successful termination of at least the CNFC is performed by a service manager.

15. The system as claimed in claim 10, wherein the status is set to a free status in an event the successful termination of at least the CNFC is performed by a service manager.

16. The system as claimed in claim 10, wherein the status is set to a free status in an event a failed instantiation of at least the CNFC is performed by a service manager.

17. The system as claimed in claim 10, wherein the set of environment variables for at least the CNFC is received in a compressed format.

18. The system as claimed in claim 10, wherein the set of environment variables for at least the CNFC is provided at the CNFLM by a user of the network environment.

19. A non-transitory computer-readable storage medium storing instructions for managing environment variables for Container Network Function Components (CNFCs) in a network environment, the instructions comprising executable code which, when executed by one or more units of a system [300], causes: a transceiver unit [302], at a physical & virtual inventory manager (PVIM) unit [300A], to receive, from a container network function lifecycle manager (CNFLM), a reserve request comprising a set of environment variables for at least a CNFC; a processing unit [304], at the PVIM unit [300A], to set a reserved status associated with the set of environment variables based on the reserve request; the transceiver unit [302], at the PVIM unit [300A], to transmit, to a Policy Execution Engine (PEEGN) node, details of the set of environment variables and the reserved status; the transceiver unit [302], at the PVIM unit [300A], to receive, from the CNFLM, an update inventory request associated with one or more environment variables from the set of environment variables; and the processing unit [304], at the PVIM unit [300A], to set a status of the one or more environment variables based on the update inventory request.

Images