Patent information
IP India · live recordAbstract
The present disclosure relates to a method and a system for managing lifecycle of environment variable files. The disclosure being performed encompasses receiving at release management repository (RMR) [1092]/ physical virtual inventory manager (PVIM) [1050], from user interface (UI) [304], a request related to upload/ deletion of environment variable file(s) [312] associated with container network function (CNF) [310]; performing target procedure on the environment variable file(s) [312] associated with the CNF [310]; and managing lifecycle of the environment variable file(s) [312] based on the target procedure. [FIG. 4]
Applicants
1Inventors
17Claims
13Specification
Show full textCollapse
FORM 2 THE PATENTS ACT, 1970 (39 OF 1970) & THE PATENT RULES, 2003 COMPLETE SPECIFICATION (See section 10 and rule 13) “METHOD AND SYSTEM FOR MANAGING LIFECYCLE OF ENVIRONMENT VARIABLE FILES” We, Jio Platforms Limited, an Indian National, of Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India. The following specification particularly describes the invention and the manner in which it is to be performed. 2 METHOD AND SYSTEM FOR MANAGING LIFECYCLE OF ENVIRONMENT VARIABLE FILES FIELD OF THE DISCLOSURE 5
[0001] Embodiments of the present disclosure generally relate to the field of wireless communication systems. More particularly, embodiments of the present disclosure relate to managing lifecycle of environment variable files. 10 BACKGROUND
[0002] The following description of 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 15 disclosure. However, it should be appreciated that this section be used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of prior art.
[0003] Wireless communication technology has rapidly evolved over the past few 20 decades, with each generation bringing significant improvements and advancements. The first generation of wireless communication technology was based on antilog technology and offered only voice services. However, with the advent of the second generation (2G) technology, digital communication and data services became possible, and text messaging was introduced. The third generation 25 (3G) technology marked the introduction of high-speed internet access, mobile video calling, and location-based services. The fourth generation (4G) technology revolutionized wireless communication with faster data speeds, better network coverage, and improved security. Currently, the fifth generation (5G) technology is being deployed, promising even faster data speeds, low latency, and the ability to 30 connect multiple devices simultaneously. With each generation, wireless 3 communication technology has become more advanced, sophisticated, and capable of delivering more services to its users.
[0004] Container Network Functions (CNFs) are applications operating on a cloud 5 server (preferably a telecom cloud) that are beneficial as they have the capability to replace specialized hardware in deploying network infrastructure. CNFs are built using microservice architecture and operate natively over virtual machines hosted on the cloud server. CNFs are an alternative to monolithic model of computing and utilize individual as well as interconnected microservices. These microservices are 10 run in software containers (also known as container nodes/ container network function(s)/ container network function component) which are responsible for providing a run-time environment including the application code, system binaries, and dependencies needed for microservices to operate. 15 [0005] Inventory Manager (IM) micro-service [such as a physical virtual inventory manager (PVIM)] is responsible for maintaining the virtual inventory and limited physical inventory by supervising the relation between physical and virtual resources of the communication network with respect to an overlay. Also, the IM describes the physical and the virtual resources with respect to different attributes 20 using updates from external micro-services. Thus, its data accuracy depends on the micro-services which create, update, delete these resources and at the same time update these events with IM. Other services can query IM relations, attributes etc. using Query application programming interfaces (APIs) provided by the IM. 25 [0006] Further, a Release Management Repository (RMR) micro-service provides version control host binary image and host files in a common shared file storage. The RMR is also responsible for provisioning API to manage those binary images/files. Thus, a common repository is required to store the environment variable files and to be synced with the inventory to assign those environment 30 variables for required CNF’s and manage its lifecycle. 4
[0007] Thus, there exists an imperative need in the art to manage the lifecycle of environment variable files for the CNFs in all the deployment plans and maintaining common share file storage in sync to maintain the environment variable file in real 5 time, which the present disclosure aims to address. OBJECTS OF THE DISCLOSURE
[0008] This section is provided to introduce certain objects and aspects of the 10 present disclosure in a simplified form that are further described below in the description. To overcome at least a few problems associated with the known solutions as provided in the previous section, an object of the present disclosure is to substantially reduce the limitations and drawbacks of the prior arts as described hereinabove. 15
[0009] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.
[0010] It is an object of the present disclosure to provide a system and a method for 20 managing a lifecycle of environment variable files for container network function (CNFs) in all the deployment plans and maintaining common share file storage in sync to maintain the environment variable files in real time.
[0011] It is another object of the present disclosure to provide a solution for storing 25 environment variable files in the common shared file storage.
[0012] It is yet another object of the present disclosure to provide a solution to have an interface (such as an IM_RM interface) for managing the lifecycle of environment variable files for the CNFs in all the deployment plans. 30 5 SUMMARY OF THE DISCLOSURE
[0013] This section is provided to introduce certain aspects of the present disclosure 5 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.
[0014] An aspect of the present disclosure may relate to a method for managing 10 lifecycle of environment variable files. The method comprises receiving, by a transceiver unit at one of: a release management repository (RMR) and a physical virtual inventory manager (PVIM), from a user interface, a request related to one of: an upload and a deletion of one or more environment variable associated with a container network function (CNF). The method further comprises performing, by 15 an analysis unit, a target procedure on the one or more environment variable files associated with the CNF, wherein the target procedure is one of an addition procedure and a deletion procedure. The method further comprises managing, by a management unit, lifecycle of the one or more environment variable files based on the target procedure. 20
[0015] In an exemplary aspect of the present disclosure, the request is received at the PVIM from a set of available PVIMs.
[0016] In an exemplary aspect of the present disclosure, the addition procedure 25 comprises transmitting, by the transceiver unit via the RMR to the PVIM, a request message for receiving a deployment status of the CNF. The addition procedure further comprises receiving, by the transceiver unit at the RMR from the PVIM, a response message comprising the deployment status of the CNF. The addition procedure further comprises storing, by the analysis unit via the RMR, in a common 30 shared storage unit, the one or more environment variable files associated with the 6 CNF. The addition procedure further comprises uploading, by the transceiver unit, at the PVIM, the one or more environment variable files associated with the CNF.
[0017] In an exemplary aspect of the present disclosure, the deployment status 5 corresponds to a current state of the container network function (CNF). The current state of the CNF is one of: deployed CNF, pending CNF, failed CNF, deleted CNF, and updating CNF.
[0018] In an exemplary aspect of the present disclosure, the method comprises 10 transmitting, by the transceiver unit via the PVIM, and to the RMR, a first notification regarding uploading of the one or more environment variable files associated with the CNF. The method further comprises transmitting, by the transceiver unit via the RMR to the user interface, a second notification regarding the uploading of the one or more environment variable files associated with the 15 CNF.
[0019] In an exemplary aspect of the present disclosure, the deletion procedure comprises deleting, by the analysis unit via the PVIM, the one or more environment variable files from a memory unit associated with the PVIM. The deletion 20 procedure further comprises sending, by the transceiver unit via the PVIM to the RMR, a notification regarding the deletion of the one or more environment variable files from the memory unit associated with the PVIM. The deletion procedure further comprises deleting, by the analysis unit via the RMR, the one or more environment variable files from the common shared storage unit. 25
[0020] In an exemplary aspect of the present disclosure, the method comprises transmitting, by the transceiver unit via the RMR to the PVIM, a third notification regarding the deletion of the one or more environment variable files associated with the CNF. The method further comprises transmitting, by the transceiver unit via the 7 PVIM to the user interface, a fourth notification regarding the deletion of the one or more environment variable files associated with the CNF.
[0021] In an exemplary aspect of the present disclosure, managing the lifecycle of 5 the one or more environment variable files comprises at least: monitoring, modification, and deletion of the one or more environment variable files, along with maintaining version control for updates associated with the CNF.
[0022] Another aspect of the present disclosure may relate to a system for 10 managing lifecycle of environment variable files. The system comprises a transceiver unit configured to receive, at one of: a release management repository (RMR) and a physical virtual inventory manager (PVIM), from a user interface (UI), a request related to one of: an upload and a deletion of one or more environment variable files associated with a container network function (CNF). The 15 system further comprises an analysis unit configured to perform a target procedure on the one or more environment variable files associated with the CNF. The target procedure is one of an addition procedure and a deletion procedure. The system further comprises a management unit configured to manage lifecycle of the one or more environment variable files based on the target procedure. 20
[0023] Another aspect of the present disclosure may relate to a non-transitory computer-readable storage medium storing instruction for managing lifecycle of environment variable files, the storage medium comprising executable code which, when executed by one or more units of a system, causes a transceiver unit to receive, 25 at one of: a release management repository (RMR) and a physical virtual inventory manager (PVIM), from a user interface, a request related to one of: an upload and a deletion of one or more environment variable files associated with a container network function (CNF). Further, the executable code which, when executed, causes an analysis unit to perform a target procedure on the one or more 30 environment variable files associated with the CNF. The target procedure here is 8 one of an addition procedure and a deletion procedure. Further, the executable code which, when executed, causes a management unit to manage lifecycle of the one or more environment variable files based on the target procedure. 5 [0024] Yet another aspect of the present disclosure may relate to user equipment (UE) for managing lifecycle of environment variable files. The UE is configured to transmit at one of: a release management repository (RMR) and a physical virtual inventory manager (PVIM), via a user interface (UI), a request related to one of: an upload and a deletion of one or more environment variable files associated with a 10 container network function (CNF). The UE is further configured to perform a target procedure, via the user interface (UI), on the one or more environment variable files associated with the CNF. The target procedure is one of an addition procedure and a deletion procedure. The UE is further configured to manage, via the user interface (UI), lifecycle of the one or more environment variable files based on the target 15 procedure. DESCRIPTION OF DRAWINGS
[0025] The accompanying drawings, which are incorporated herein, and constitute 20 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 25 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. 9
[0026] FIG.1 illustrates an exemplary block diagram representation of a management and orchestration (MANO) architecture, in accordance with an exemplary implementation of the present disclosure. 5 [0027] 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 an exemplary implementation of the present disclosure.
[0028] FIG.3 illustrates an exemplary block diagram of a network environment 10 having a system for managing lifecycle of environment variable files, in accordance with exemplary implementations of the present disclosure.
[0029] FIG.4 illustrates an exemplary method for managing lifecycle of environment variable files, in accordance with exemplary implementations of the 15 present disclosure.
[0030] FIG.5A illustrates an exemplary block diagram of the system having an IM_RM interface in a network environment for managing lifecycle of environment variable files, in accordance with exemplary embodiments of the present disclosure, 20 in accordance with exemplary embodiments of the present disclosure.
[0031] FIG. 5B illustrates another exemplary block diagram of the system for showcasing the interaction between a physical and virtual inventory manager (PVIM) cluster and the release management repository (RMR) for managing the 25 lifecycle of the environment variable files, in accordance with exemplary embodiments of the present disclosure.
[0032] FIG.6A illustrates a call flow indicating the process for managing the lifecycle of the environment variable files by uploading the environment variable 10 files in a common shared storage unit, in accordance with exemplary embodiments of the present disclosure.
[0033] FIG.6B illustrates another call flow indicating the process for managing the 5 lifecycle of the environment variable files by deleting the environment variable files from the common shared storage unit, in accordance with exemplary embodiments of the present disclosure.
[0034] The foregoing shall be more apparent from the following more detailed 10 description of the disclosure. DETAILED DESCRIPTION 15 [0035] 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 can each be used independently of one 20 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. Some of the problems discussed above might not be fully addressed by any of the features described herein. Example embodiments of the present disclosure are described below, as illustrated in various drawings in 25 which like reference numerals refer to the same parts throughout the different drawings.
[0036] The ensuing description provides exemplary embodiments only, and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather, 30 the ensuing description of the exemplary embodiments will provide those skilled in 11 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. 5
[0037] 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, networks, processes, and other 10 components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail. In other instances, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail in order to avoid obscuring the embodiments. 15 [0038] 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 can be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process 20 is terminated when its operations are completed but could have additional steps not included in a figure.
[0039] The word “exemplary” and/or “demonstrative” is used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the 25 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 30 “includes,” “has,” “contains,” and other similar words are used in either the detailed 12 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. 5 [0040] Further, the user device and/or a system as described herein to implement technical features as disclosed in the present disclosure may also comprise a “processor” or “processing unit”, wherein processor refers to any logic circuitry for processing instructions. The processor may be a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor, a 10 plurality of microprocessors, one or more microprocessors in association with a Digital Signal Processor (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 15 working of the system according to the present disclosure. More specifically, the processor is a hardware processor.
[0041] As used herein “interface” or “user interface” refers to a shared boundary across which two or more separate components of a system exchange information 20 or data. The interface may also be referred to a set of rules or protocols that define communication or interaction of one or more modules or one or more units with each other, which also includes the methods, functions, or procedures that may be called. 25 [0042] 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, 13 Application Specific Integrated Circuits (ASIC), Field Programmable Gate Array circuits (FPGA), any other type of integrated circuits, etc.
[0043] As used herein the transceiver unit includes at least one receiver and at least 5 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.
[0044] The present disclosure aims to overcome the issues discussed in the 10 background section and other existing problems in this field of technology by using an IM_RM interface [502] (as shown in FIG.5) that stores environment variable files [312] (as shown in FIG.3) in a common shared storage unit [314] (as shown in FIG.3). The IM_RM interface [502] is a HTTP based interface that allows managing the lifecycle of environment variable files [312] for all container network 15 function (CNFs) [310] in all the deployment plans.
[0045] Hereinafter, exemplary embodiments of the present disclosure will be described with reference to the accompanying drawings. 20 [0046] FIG. 1 illustrates an exemplary block diagram representation of a management and orchestration (MANO) architecture [100], in accordance with exemplary implementation of the present disclosure. The MANO architecture [100] may be developed for managing telecom cloud infrastructure automatically, managing design or deployment design, managing instantiation of network node(s)/ 25 service(s) etc. The MANO architecture [100] 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 [100]. The MANO architecture
[100] may be used to auto-instantiate the VNFs into the corresponding environment 14 of the present disclosure so that it could help in recovery of network function(s) to the platform.
[0047] As shown in FIG. 1, the MANO architecture [100] comprises a user 5 interface layer [102], a network function virtualization (NFV) and software defined network (SDN) design function module [104], a platform foundation services module [106], a platform core services module [108] and a platform resource adapters and utilities module [112]. All the components are assumed to be connected to each other in a manner as obvious to the person skilled in the art for 10 implementing features of the present disclosure.
[0048] The NFV and SDN design function module [104] comprises a VNF lifecycle manager (compute)/ LM module [1042], a VNF catalog [1044], a network services catalog [1046], a network slicing and service chaining manager [1048], a 15 physical and virtual resource manager/ PVIM module [1050] and a CNF lifecycle manager [1052]. The VNF lifecycle manager (compute)/ LM module [1042] may be responsible for deciding on which server of the communication network, the microservice will be instantiated. The VNF lifecycle manager (compute) / LM module [1042] may manage the overall flow of incoming/ outgoing requests during 20 interaction with the user. The VNF lifecycle manager (compute) / LM module
[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 P1 and P2 etc. The VNF catalog [1044] stores the metadata of all the VNFs (also CNFs in 25 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/ physical virtual inventory 30 manager (PVIM) module [1050] stores the logical and physical inventory of the 15 VNFs. Just like the VNF lifecycle manager (compute) / LM module [1042], the CNF lifecycle manager [1052] may be used for the CNFs lifecycle management.
[0049] The platforms foundation services module [106] comprises a 5 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 (ERM)/ ERM module [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 10 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 [100]. These logs are used for debugging purposes. The event routing manager (ERM)/ event 15 routing manger (ERM) module [1070] may be responsible for routing the events i.e., the application programming interface (API) hits to the corresponding services.
[0050] The platforms core services module [108] comprises NFV infrastructure monitoring manager [1082], an assure manager [1084], a performance manager 20 [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/ NPDA module [1096], a platform NoSQL DB [1098]; a platform schedulers and cron jobs
[1100], a VNF backup & upgrade manager [1102], a microservice auditor [1104], 25 and a platform operations, administration and maintenance manager [1106]. The NFV infrastructure monitoring manager [1082] monitors 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 30 the performance counters. The policy execution engine (PEGN)/ PEGN module 16
[1088] may be responsible for managing all of the policies. The capacity monitoring manager (CMM) [1090] may be responsible for sending the request to the PEGN [1088]. The release management (mgmt.) repository (RMR) [1092] may be responsible for managing the releases and the images of all of the vendor's 5 network nodes. The configuration manager & golden configuration template (GCT) [1094] manages the configuration and GCT of all the vendors. The NFV platform decision analytics (NPDA)/ NFV platform decision analytics (NPDA) module [1096] helps in deciding the priority of using the network resources. It may be further noted that the policy execution engine (PEGN) module [1088], the 10 configuration manager & GCT [1094] and the NPDA [1096] work together. The platform NoSQL DB [1098] may be a database for storing all the inventory (both physical and logical) as well as the metadata of the VNFs and CNF. The platform schedulers and cron jobs [1100] schedules the task such as but not limited to triggering of an event, traverse the network graph etc. The VNF backup & 15 upgrade manager [1102] takes backup of the images, binaries of the VNFs and the CNFs and produces those backup 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 [100] may be using the network resources. In such case, the microservice auditor [1104] audits and 20 informs the same so that resources can be released for services running in the MANO architecture [100]. The audit assures that the services only run on the MANO platform [100]. The platform operations, administration and maintenance manager [1106] may be used for newer instances that are spawning. 25 [0051] The platform resource adapters and utilities module [112] 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 adapter
[1128]; and a NFV gateway [1130]. The platform external API adaptor and gateway [1122] may be responsible for handling the external services (to the 30 MANO platform [100]) that requires the network resources. The generic decoder 17 and indexer (XML, CSV, JSON) [1124] gets 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 [100] for communication. The API adapter [1128] may be used to connect with the virtual 5 machines (VMs). The NFV gateway [1130] may be responsible for providing the path to each services going to/incoming from the MANO architecture [100].
[0052] The present disclosure can be implemented on a computing device [200] as shown in FIG. 2. The computing device [200] implements the present disclosure in 10 accordance with the MANO architecture (as shown in FIG. 1). FIG. 2 illustrates an exemplary block diagram of the computing device [200] 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 [200] may also implement a method [400] (as shown in FIG. 4) managing 15 lifecycle of environment variable files. In another implementation, the computing device [200] itself implements the method [400] managing lifecycle of environment variable files in a communication network using one or more units configured within the computing device [200], wherein said one or more units can implement the features as disclosed in the present disclosure. 20
[0053] The computing device [200] may include a bus [202] or other communication mechanism for communicating information, and a hardware processor [204] coupled with bus [202] for processing information. The hardware processor [204] may be, for example, a general-purpose microprocessor. The 25 computing device [200] may also include a main memory [206], such as a randomaccess memory (RAM), or other dynamic storage device, coupled to the bus [202] for storing information and instructions to be executed by the processor [204]. The main memory [206] also may be used for storing temporary variables or other intermediate information during execution of the instructions to be executed by the 30 processor [204]. Such instructions, when stored in non-transitory storage media 18 accessible to the processor [204], render the computing device [200] into a specialpurpose machine that is customized to perform the operations specified in the instructions. The computing device [200] further includes a read only memory (ROM) [208] or other static storage device coupled to the bus [202] for storing static 5 information and instructions for the processor [204].
[0054] A storage device [210], such as a magnetic disk, optical disk, or solid-state drive is provided and coupled to the bus [202] for storing information and instructions. The computing device [200] may be coupled via the bus [202] to a 10 display [212], 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 [214], including alphanumeric and other keys, touch screen input means, etc. may be coupled to the bus [202] for communicating information and command selections to the processor 15 [204]. Another type of user input device may be a cursor controller [216], such as a mouse, a trackball, or cursor direction keys, for communicating direction information and command selections to the processor [204], and for controlling cursor movement on the display [212]. The 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 20 the device to specify positions in a plane.
[0055] The computing device [200] 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 [200] causes 25 or programs the computing device [200] to be a special-purpose machine. According to one implementation, the techniques herein are performed by the computing device [200] in response to the processor [204] executing one or more sequences of one or more instructions contained in the main memory [206]. Such instructions may be read into the main memory [206] from another storage medium, 30 such as the storage device [210]. Execution of the sequences of instructions 19 contained in the main memory [206] causes the processor [204] 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. 5
[0056] The computing device [200] also may include a communication interface
[218] coupled to the bus [202]. The communication interface [218] provides a twoway data communication coupling to a network link [220] that is connected to a local network [222]. For example, the communication interface [218] may be an 10 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 [218] 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 15 implementation, the communication interface [218] sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information.
[0057] The computing device [200] can send messages and receive data, including 20 program code, through the network(s), the network link [220] and the communication interface [218]. In the Internet example, a server [230] might transmit a requested code for an application program through the Internet [228], the ISP [226], the local network [222], the host [224] and the communication interface
[218]. The received code may be executed by the processor [204] as it is received, 25 and/or stored in the storage device [210], or other non-volatile storage for later execution.
[0058] The present disclosure is implemented by the system [300] (as shown in FIG. 3). The system [300] may be implemented using the computing device [200] 20 (as shown in FIG. 2). In an implementation, the computing device [200] may be connected to the system [300] to perform the present disclosure.
[0059] Referring to FIG. 3, an exemplary block diagram of a network environment 5 having a system [300] for managing lifecycle of environment variable files, is shown, in accordance with the exemplary implementations of the present disclosure. The system [300] comprises at least one transceiver unit [302]; at least one analysis unit [306]; at least one management unit [308]; at least one common shared storage unit [314]; at least one user interface [304]; at least one release 10 management repository (RMR) [1092] and at least one physical and virtual inventory manager (PVIM) [1050]. The at least one physical and virtual inventory manager (PVIM) [1050] comprises at last one memory unit [316]. The system [300] is connected to at least one container network function (CNF) [310]. The CNF [310] comprises one or more environment variable files [312]. Also, all the components/ 15 units of the system [300] are assumed to be connected to each other unless otherwise indicated below. As shown in the FIG.3, all units shown within the system [300] should also be assumed to be connected to each other. Also, in FIG. 3 only a few units are shown, however, the system [300] may comprise multiple such units or the system [300] may comprise any such numbers of said units, as required to 20 implement the features of the present disclosure. Further, in an implementation, the system [300] may be present in the user device/ user equipment (UE) [318] via the user interface (UI) [304], to implement the features of the present disclosure. The system [300] may be a part of the UE [318] / or may be independent of but in communication with the UE [318]. In another implementation, the system [300] 25 may reside in a server or a network entity. In yet another implementation, the system
[300] may reside partly in the server/ network entity and partly in the UE [318].
[0060] The system [300] is configured for managing the lifecycle of environment variable files in a network environment, with the help of the interconnection 30 between the components/units of the system [300]. The environment variable files 21 are the variables available to programs/applications of the communication network that are available dynamically during runtime. The value of these variables can come from a range of sources such as but not limited to text files, third-party secret managers, calling scripts, vendors. By being dynamic, the environment variable 5 files can be changed based on the environment that the container network function
[310] is running in. The environment variable files provide a way to configure the network application by securely storing configuration settings, environment variables, and sensitive information. 10 [0061] The transceiver unit [302] is configured to receive, at one of: a release management repository (RMR) [1092] and a physical virtual inventory manager (PVIM) [1050], from a user interface [304], a request related to one of: an upload and a deletion of one or more environment variable files [312] associated with a container network function (CNF) [310]. 15
[0062] Thereafter, the analysis unit [306] is configured to perform a target procedure on the one or more environment variable files [312] associated with the CNF [310]. The target procedure is one of an addition procedure and a deletion procedure. 20
[0063] Thereafter, the management unit [308] is configured to manage lifecycle of the one or more environment variable files [312] based on the target procedure.
[0064] In an implementation of the present disclosure, for performing the addition 25 procedure, the transceiver unit [302] of the system [300] is configured to transmit, via the RMR [1092] to the PVIM [1050], a request message for receiving a deployment status of the CNF [310]. The transceiver unit [302] is further configured to receive, at the RMR [1092] from the PVIM [1050], a response message comprising the deployment status of the CNF [310]. Further, for performing the 30 addition procedure, the analysis unit [306] of the system [300] is configured to 22 store, via the RMR [1092], in a common shared storage unit [314], the one or more environment variable files [312] associated with the CNF [310]. Furthermore, the transceiver unit [302] is configured to upload, at the PVIM [1050], the one or more environment variable files [312] associated with the CNF [310]. The common 5 storage unit [314] refers to a common repository required to store the environment variable files [312] and to be synced with an inventory in order to assign the environment variables files [312] for the CNFs [310] upon managing the lifecycle of the environment variable files [312]. It is to be noted that the inventory here is indicative of the memory space in the memory unit [316] of the PVIM [1050]. 10
[0065] In an implementation of the present disclosure, the transceiver unit [302] is configured to transmit, via the PVIM [1050], and to the RMR [1092], a first notification regarding uploading of the one or more environment variable files [312] associated with the CNF [310]. The transceiver unit [302] is further configured to 15 transmit, via the RMR [1092] to the user interface (UI) [304], a second notification regarding the uploading of the one or more environment variable files [312] associated with the CNF [310].
[0066] In an implementation of the present disclosure, for performing the deletion 20 procedure, the analysis unit [306] of the system [300] is configured to analysis unit
[306] is configured to delete, via the PVIM [1050], the one or more environment variable files [312] from a memory unit [316] associated with the PVIM [1050]. Further, for performing the deletion procedure the transceiver unit [302] of the system [300] is configured to send, via the PVIM [1050] to the RMR [1092], a 25 notification regarding the deletion of the one or more environment variable files
[312] from the memory unit [316] associated with the PVIM [1050]. Furthermore, the analysis unit [306] is further configured to delete, via the RMR [1092], the one or more environment variable files [312] from the common shared storage unit
[314]. 30 23
[0067] In an implementation of the present disclosure, the transceiver unit [302] is configured to transmit, via the RMR [1092] to the PVIM [1050], a third notification regarding the deletion of the one or more environment variable files [312] associated with the CNF [310]. The transceiver unit [302] is further configured to 5 transmit, via the PVIM [1050] to the user interface [304], a fourth notification regarding the deletion of the one or more environment variable files [312] associated with the CNF [310].
[0068] In an implementation of the present disclosure, the request is received at 10 least the PVIM [1050] from a set of available PVIMs. It is to be noted that that set of available PVIMs may form part of a PVIM cluster [504] (as shown in FIG.5B) and thus contain more than one PVIM [1050].
[0069] In an implementation of the present disclosure, the deployment status 15 corresponds to a current state of the container network function (CNF) [310], wherein the current state of the CNF [310] is one of: deployed CNF, pending CNF, failed CNF, deleted CNF, and updating CNF. It is to be noted that the deployed CNF [310] indicates that the CNF [310] is successfully running and operational. Further, the pending CNF refers to the CNF [310] which is in the process of being 20 deployed i.e., ready but not fully operational. The failed CNF marks that the deployment attempt was unsuccessful due to errors or issues. The deleted CNF refers to the CNF [310] that has been removed from the system [300] and is no longer active. The updating CNF refers to the CNF [310] which is undergoing an update or upgrade process. 25
[0070] In an implementation of the present disclosure, for managing the lifecycle of the one or more environment variable files [312], the system [300] is configured to at least: monitor, modify, and delete the one or more environment variable files
[312], along with maintaining version control for updates associated with the CNF 30 [310]. 24
[0071] Referring to FIG. 4, an exemplary method flow diagram [400] for managing lifecycle of environment variable files in a network environment, in accordance with exemplary implementations of the present disclosure is shown. The 5 environment variable files are the variables available to programs/applications of the communication network that are available dynamically during runtime. The value of these variables can come from a range of sources such as but not limited to text files, third-party secret managers, calling scripts, etc. By being dynamic, the environment variable files can be changed based on the environment that the 10 container network function [310] is running in. The environment variable files provide a way to configure the network application by securely storing configuration settings, environment variables, and sensitive information. In an implementation the method [400] is performed by the system [300] (as shown in FIG. 3). Also, as shown in FIG. 4, the method [400] starts at step [402]. 15
[0072] At step [404], the method [400] comprises receiving, by a transceiver unit
[302] at one of: a release management repository (RMR) [1092] and a physical virtual inventory manager (PVIM) [1050], from a user interface [304], a request related to one of: an upload and a deletion of one or more environment variable files 20 [312] associated with a container network function (CNF) [310].
[0073] In an exemplary aspect of the present disclosure, the request is received at least the PVIM [1050] from a set of available PVIMs. It is to be noted that that set of available PVIMs may form part of a PVIM cluster [504] (as shown in FIG.5B) 25 and thus contain more than one PVIM [1050].
[0074] At step [406], the method [400] further comprises performing, by an analysis unit [306], a target procedure on the one or more environment variable files
[312] associated with the CNF [310], wherein the target procedure is one of an 30 addition procedure and a deletion procedure. 25
[0075] In an implementation of the present disclosure, the addition procedure comprises transmitting, by the transceiver unit [302] via the RMR [1092] to the PVIM [1050], a request message for receiving a deployment status of the CNF 5 [310]. The addition procedure further comprises receiving, by the transceiver unit
[302] at the RMR [1092] from the PVIM [1050], a response message comprising the deployment status of the CNF [310]. The addition procedure further comprises storing, by the analysis unit [306] via the RMR [1092], in a common shared storage unit [314], the one or more environment variable files [312] associated with the 10 CNF [310]. The addition procedure further comprises uploading, by the transceiver unit [302], at the PVIM [1050], the one or more environment variable files [312] associated with the CNF [310].
[0076] In an exemplary aspect of the present disclosure, the deployment status 15 corresponds to a current state of the container network function (CNF) [310], wherein the current state of the CNF [310] is one of: deployed CNF, pending CNF, failed CNF, deleted CNF, and updating CNF. It is to be noted that the deployed CNF [310] indicates that the CNF [310] is successfully running and operational. Further, the pending CNF refers to the CNF [310] which is in the process of being 20 deployed i.e., ready but not fully operational. The failed CNF marks that the deployment attempt was unsuccessful due to errors or issues. The deleted CNF refers to the CNF [310] that has been removed from the system [300] and is no longer active. The updating CNF refers to the CNF [310] which is undergoing an update or upgrade process. 25
[0077] In an implementation of the present disclosure, the method [400] comprises transmitting, by the transceiver unit [302] via the PVIM [1050], and to the RMR
[1092], a first notification regarding uploading of the one or more environment variable files [312] associated with the CNF [310]. The method [400] further 30 comprises transmitting, by the transceiver unit [302] via the RMR [1092] to the user 26 interface [304], a second notification regarding the uploading of the one or more environment variable files [312] associated with the CNF [310].
[0078] In an implementation of the present disclosure, the deletion procedure 5 comprises deleting, by the analysis unit [306] via the PVIM [1050], the one or more environment variable files [312] from a memory unit [316] associated with the PVIM [1050]. The deletion procedure further comprises sending, by the transceiver unit [302] via the PVIM [1050] to the RMR [1092], a notification regarding the deletion of the one or more environment variable files [312] from the memory unit 10 [316] associated with the PVIM [1050]. The deletion procedure further comprises deleting, by the analysis unit [306] via the RMR [1092], the one or more environment variable files [312] from the common shared storage unit [314]. The common storage unit [314] refers to a common repository required to store the environment variable files [312] and to be synced with an inventory in order to 15 assign the environment variables files [312] for the CNFs [310] upon managing the lifecycle of the environment variable files [312]. It is to be noted that the inventory here is indicative of the memory space in the memory unit [316] of the PVIM
[1050]. 20 [0079] In an exemplary aspect of the present disclosure, the method [400] comprises transmitting, by the transceiver unit [302] via the RMR [1092] to the PVIM [1050], a third notification regarding the deletion of the one or more environment variable files [312] associated with the CNF [310]. The method [400] further comprises transmitting, by the transceiver unit [302] via the PVIM [1050] 25 to the user interface [304], a fourth notification regarding the deletion of the one or more environment variable files [312] associated with the CNF [310].
[0080] At step [408], the method [400] further comprises managing, by a management unit [308], lifecycle of the one or more environment variable files 30 [312] based on the target procedure. 27
[0081] In an exemplary aspect of the present disclosure, managing the lifecycle of the one or more environment variable files [312] comprises at least: monitoring, modification, and deletion of the one or more environment variable files [312], 5 along with maintaining version control for updates associated with the CNF [310].
[0082] Thereafter, the method [400] terminates at step [410].
[0083] Referring to FIG. 5A, an exemplary block diagram of the system [300] 10 having an IM_RM interface [502] in a network environment for managing the lifecycle of the environment variable files [312] is shown, in accordance with the exemplary embodiments of the present disclosure. Referring to FIG. 5B, an exemplary block diagram of the system [300] for showcasing the interaction between a physical and virtual inventory manager (PVIM) cluster [504] and the 15 release management repository (RMR) [1092] for managing the lifecycle of the environment variable files [312] is shown, in accordance with exemplary embodiments of the present disclosure. The Figures 5A and 5B depicts the interaction between various components involved in the managing the lifecycle of the environment variable files [312]. FIG.5A and FIG. 5B have been explained in 20 conjunction with each other. The PVIM cluster [504] comprises multiple PVIMs
[1050] of which at least one PVIM [1050] is configured to receive a request for uploading/ deleting of the one or more environment variable files [312] for all container network functions (CNFs) [310] in all the deployments. The PVIM [1050] maintains a memory unity [316], from where the one or more environment variable 25 files [312] is deleted for performing the deletion of the one or more environment variable files [312]. The RMR [1092] and the PVIM cluster [504] interact with each other by sending a request for managing the environment variable files [312] via the IM_RM interface [502]. 28
[0084] Referring to FIG.6A, a call flow indicating the process for managing the lifecycle of the environment variable files [312] by uploading the environment variable files [312] (as shown in FIG.3) in the common shared storage unit [314] (as shown in FIG.3) is shown, in accordance with exemplary embodiments of the 5 present disclosure. Referring to FIG.6B, another call flow indicating the process for managing the lifecycle of the environment variable files [312] by deleting the environment variable files from the common shared storage unit [314] is shown, in accordance with exemplary embodiments of the present disclosure. FIG.6A and FIG.6B have been taken together for discussion. 10
[0085] A description of the call flow for uploading the environment variable files
[312] along with various entities having varied functions performed by such entities is provided below: - From a user interface (UI) [304] [whether a graphical user interface (GUI) 15 or command line interface (CLI)], a request for uploading the environment variable files [312] for the container network function(s) (CNFs) [310] to the release management repository (RMR) [1092]. The request is prompted by a notification message that comprises of the information related to uploading of the environment variable file(s) for the CNF [310]. 20 - The RMR [1092] then gets a deployment status of the CNF [310] from the physical and virtual inventory manager (PVIM) [1050]. This is performed when the RMR [1092] transmits, via an IM_RM interface [502] (as shown in FIG.5A) to the PVIM [1050], a query message comprising a request for knowing the deployment status of the CNF [310]. 25 - The RMR [1092] saves the environment variable files [312] in the common shared storage unit [314], associated with the CNFs and deployment status, after the RMR [1092], receives, via the IM_RM interface [502], the RESPONSE, from the PVIM [1050]. This RESPONSE is again a query message response that comprises an update of CNF [310] deployment 30 status. 29 - Thereafter, the RMR [1092] uploads the environment variable file [312] for the CNF [310]. The RMR [1092] then sends the environment variable files
[312] to the PVIM [1050]. The PVIM [1050] reads the file from the common shared storage unit [314] and stores the environment variable files [312] in 5 a memory unit [316] (as shown in FIG.3) and finally sends a SUCCESS RESPONSE. - Upon receipt of the SUCCESS RESPONSE, the RMR [1092] prompts the message “ENVIRONMENT VARIABLE FILE [312] UPLOAD SUCCESS” to the UI [304] i.e., an acknowledgement of the successful 10 uploading of the environment variable files [312]. - Thus, the process of uploading is concluded in the call flow.
[0086] A description of the call flow for deleting the environment variable files
[312] along with various entities having varied functions performed by such entities 15 is provided below: - From a user interface (UI) [304] [whether a graphical user interface (GUI) or command line interface (CLI)], a request for deleting the environment variable files [312] for the CNFs [310] to the PVIM [1050] is sent. The request here refers to a notification message comprising the information 20 related to deletion of the environment variable file [312]. - Upon receiving the request, the PVIM [1050] deletes the environment variable files [312] from and notifies the RMR [1092] about the deletion, via the IM_RM interface [502] (as shown in FIG.5). - Upon receipt of the notification, the RMR [1092] deletes the environment 25 variable files [312] from the common shared storage unit [314] (as shown in FIG.3) and sends RESPONSE to the PVIM [1050] acknowledging the deletion. - The PVIM [1050], via the IM_RM interface [502], receives the acknowledgement response of successful deletion of the environment 30 variable files [312], by the RMR [1092]. 30 - Thereafter, the PVIM [1050] transmits to the UI [304], a notification of successfully deletion of the environment variable files [312]. - Thus, the process of deletion is concluded in the call flow. 5 [0087] Another aspect of the present disclosure may relate to non-transitory computer-readable storage medium storing instruction for managing lifecycle of environment variable files, the storage medium comprising executable code which, when executed by one or more units of a system [300], causes a transceiver unit
[302] to receive, at one of: a release management repository (RMR) [1092] and a 10 physical virtual inventory manager (PVIM) [1050], from a user interface [304], a request related to one of: an upload and a deletion of one or more environment variable files [312] associated with a container network function (CNF) [310]. Further, the executable code which, when executed, causes an analysis unit [306] to perform a target procedure on the one or more environment variable files [312] 15 associated with the CNF [310]. The target procedure here is one of an addition procedure and a deletion procedure. Further, the executable code which, when executed, causes a management unit [308] to manage lifecycle of the one or more environment variable files [312] based on the target procedure. 20 [0088] Yet another aspect of the present disclosure may relate to user equipment (UE) [318] for managing lifecycle of environment variable files [312]. The UE
[318] configured to transmit at one of: a release management repository (RMR)
[1092] and a physical virtual inventory manager (PVIM) [1050], via a user interface (UI) [304], a request related to one of: an upload and a deletion of one or more 25 environment variable files [312] associated with a container network function (CNF) [310]. The UE [318] is further configured to perform a target procedure, via the user interface (UI) [304], on the one or more environment variable files [312] associated with the CNF [310]. The target procedure is one of an addition procedure and a deletion procedure. The UE [318] is further configured to manage, via the 31 user interface (UI) [304], lifecycle of the one or more environment variable files
[312] based on the target procedure.
[0089] Further, in accordance with the present disclosure, it is to be acknowledged 5 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 10 as limiting the scope of the present disclosure. Consequently, alternative arrangements and substitutions of units, provided they achieve the intended functionality described herein, are encompassed within the scope of the present disclosure. 15 [0090] As is evident from the above, the present disclosure provides a technically advanced solution for managing via an IM_RM interface [502], the lifecycle of environment variable files [312] for the CNFs [310] in all the deployment plans and maintaining common shared storage unit [314] in sync to maintain the environment variable files [312] in real time. The present disclosure encompasses many 20 advantages some of which are as follows: • The present disclosure provides IM_RM interface [502] which stores environment variable files [312] in common shared storage unit [314]. • The present disclosure provides an interface that manages the lifecycle of environment variable files [312] for all CNFs [310] in all the deployment 25 plans. • The present disclosure keeps database and common shared storage unit
[314] in sync to maintain the environment variable files [312].
[0091] While considerable emphasis has been placed herein on the disclosed 30 implementations, it will be appreciated that many implementations can be made and 32 that many changes can be made to 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 5 and non-limiting. 33 We Claim: 1. A method [400] for managing lifecycle of environment variable files, the method [400] comprising: receiving, by a transceiver unit [302] at one of: a release 5 management repository (RMR) [1092] and a physical virtual inventory manager (PVIM) [1050], from a user interface [304], a request related to one of: an upload and a deletion of one or more environment variable files
[312] associated with a container network function (CNF) [310]; performing, by an analysis unit [306], a target procedure on the one 10 or more environment variable files [312] associated with the CNF [310], wherein the target procedure is one of an addition procedure and a deletion procedure; and managing, by a management unit [308], lifecycle of the one or more environment variable files [312] based on the target procedure. 15 2. The method [400] as claimed in claim 1, wherein the addition procedure comprises: transmitting, by the transceiver unit [302] via the RMR [1092] to the PVIM [1050], a request message for receiving a deployment status of the 20 CNF [310]; receiving, by the transceiver unit [302] at the RMR [1092] from the PVIM [1050], a response message comprising the deployment status of the CNF [310]; storing, by the analysis unit [306] via the RMR [1092], in a common 25 shared storage unit [314], the one or more environment variable files [312] associated with the CNF [310]; and uploading, by the transceiver unit [302], at the PVIM [1050], the one or more environment variable files [312] associated with the CNF [310]. 34 3. The method [400] as claimed in claim 2, wherein the method [400] comprises: transmitting, by the transceiver unit [302] via the PVIM [1050], and to the RMR [1092], a first notification regarding uploading of the one or 5 more environment variable files [312] associated with the CNF [310]; and transmitting, by the transceiver unit [302] via the RMR [1092] to the user interface [304], a second notification regarding the uploading of the one or more environment variable files[312] associated with the CNF [310]. 10 4. The method [400] as claimed in claim 1, wherein the deletion procedure comprises: deleting, by the analysis unit [306] via the PVIM [1050], the one or more environment variable files [312] from a memory unit [316] associated with the PVIM [1050]; 15 sending, by the transceiver unit [302] via the PVIM [1050] to the RMR [1092], a notification regarding the deletion of the one or more environment variable files [312] from the memory unit [316] associated with the PVIM [1050]; and deleting, by the analysis unit [306] via the RMR [1092], the one or 20 more environment variable files [312] from the common shared storage unit
[314]. 5. The method [400] as claimed in claim 4, wherein the method [400] comprises: 25 transmitting, by the transceiver unit [302] via the RMR [1092] to the PVIM [1050], a third notification regarding the deletion of the one or more environment variable files [312] associated with the CNF [310]; and transmitting, by the transceiver unit [302] via the PVIM [1050] to the user interface [304], a fourth notification regarding the deletion of the 30 one or more environment variable files[312] associated with the CNF [310]. 35 6. The method [400] as claimed in claim 1, wherein the request is received at the PVIM [1050] from a set of available PVIMs. 7. The method [400] as claimed in claim 1, wherein the deployment status 5 corresponds to a current state of the container network function (CNF)
[310], wherein the current state of the CNF [310] is one of: deployed CNF, pending CNF, failed CNF, deleted CNF, and updating CNF. 8. The method [400] as claimed in claim 1, wherein managing the lifecycle of 10 the one or more environment variable files [312] comprises at least: monitoring, modification, and deletion of the one or more environment variable files [312], along with maintaining version control for updates associated with the CNF [310]. 15 9. A system [300] for managing lifecycle of environment variable files, the system [300] comprising: a transceiver unit [302] configured to receive, at one of: a release management repository (RMR) [1092] and a physical virtual inventory manager (PVIM) [1050], from a user interface (UI) [304], a request related 20 to one of: an upload and a deletion of one or more environment variable files [312] associated with a container network function (CNF) [310]; an analysis unit [306] connected to at least the transceiver unit [302], the analysis unit [306] configured to perform a target procedure on the one or more environment variable files [312] associated with the CNF [310], 25 wherein the target procedure is one of an addition procedure and a deletion procedure; and a management unit [308] connected to at least the analysis unit
[306], the management unit [308] configured to manage lifecycle of the one or more environment variable files [312] based on the target procedure. 36 10. The system [300] as claimed in claim 9, wherein for performing the addition procedure, the system [300] comprises: the transceiver unit [302] configured to: transmit, via the RMR [1092] to the PVIM [1050], a request 5 message for receiving a deployment status of the CNF [310]; receive, at the RMR [1092] from the PVIM [1050], a response message comprising the deployment status of the CNF [310]; the analysis unit [306] configured to: store, via the RMR [1092], in a common shared storage unit 10 [314], the one or more environment variable files [312] associated with the CNF [310]; and the transceiver unit [302] further configured to: upload, at the PVIM [1050], the one or more environment variable files [312] associated with the CNF [310]. 15 11. The system [300] as claimed in claim 10, wherein the transceiver unit
[302] is configured to: transmit, via the PVIM [1050], and to the RMR [1092], a first notification regarding uploading of the one or more environment variable 20 files [312] associated with the CNF [310]; and transmit, via the RMR [1092] to the user interface (UI) [304], a second notification regarding the uploading of the one or more environment variable files [312] associated with the CNF [310]. 25 12. The system [300] as claimed in claim 9, wherein, for performing the deletion procedure, the system [300] comprises: the analysis unit [306] configured to: delete, via the PVIM [1050], the one or more environment variable files [312] from a memory unit [316] associated with the 30 PVIM [1050]; 37 the transceiver unit [302] configured to: send, via the PVIM [1050] to the RMR [1092], a notification regarding the deletion of the one or more environment variable files
[312] from the memory unit [316] associated with the PVIM [1050]; 5 and the analysis unit [306] further configured to: delete, via the RMR [1092], the one or more environment variable files [312] from the common shared storage unit [314]. 10 13. The system [300] as claimed in claim 12, wherein the transceiver unit
[302] is configured to: transmit, via the RMR [1092] to the PVIM [1050], a third notification regarding the deletion of the one or more environment variable files [312] associated with the CNF [310]; and 15 transmit, via the PVIM [1050] to the user interface [304], a fourth notification regarding the deletion of the one or more environment variable files [312] associated with the CNF [310]. 14. The system [300] as claimed in claim 9, wherein the request is received at 20 the PVIM [1050] from a set of available PVIMs. 15. The system [300] as claimed in claim 9, wherein the deployment status corresponds to a current state of the container network function (CNF)
[310], wherein the current state of the CNF [310] is one of: deployed CNF, 25 pending CNF, failed CNF, deleted CNF, and updating CNF. 16. The system [300] as claimed in claim 9, wherein to manage the lifecycle of the one or more environment variable files [312], the system [300] is configured to at least: monitor, modify, and delete the one or more 38 environment variable files [312], along with maintaining version control for updates associated with the CNF [310]. 17. A user equipment (UE) [318] for managing lifecycle of environment 5 variable files [312], the UE [318] configured to: transmit at one of: a release management repository (RMR) [1092] and a physical virtual inventory manager (PVIM) [1050], via a user interface (UI) [304], a request related to one of: an upload and a deletion of one or more environment variable files [312] associated with a container 10 network function (CNF) [310]; perform a target procedure, via the user interface (UI) [304], on the one or more environment variable files [312] associated with the CNF
[310], wherein the target procedure is one of an addition procedure and a deletion procedure; and 15 manage, via the user interface (UI) [304], lifecycle of the one or more environment variable files [312] based on the target procedure.