WO2025069100A1 - Procédé et système de gestion de variables d'environnement pour des composantes de fonction de réseau de conteneurs dans un environnement de réseau - Google Patents

Procédé et système de gestion de variables d'environnement pour des composantes de fonction de réseau de conteneurs dans un environnement de réseau Download PDF

Info

Publication number
WO2025069100A1
WO2025069100A1 PCT/IN2024/051897 IN2024051897W WO2025069100A1 WO 2025069100 A1 WO2025069100 A1 WO 2025069100A1 IN 2024051897 W IN2024051897 W IN 2024051897W WO 2025069100 A1 WO2025069100 A1 WO 2025069100A1
Authority
WO
WIPO (PCT)
Prior art keywords
environment variables
cnfc
unit
pvim
environment
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/IN2024/051897
Other languages
English (en)
Inventor
Aayush Bhatnagar
Ankit Murarka
Rizwan Ahmad
Kapil Gill
Arpit Jain
Shashank Bhushan
Jugal Kishore
Meenakshi Sarohi
Kumar Debashish
Supriya Kaushik DE
Gaurav Kumar
Kishan Sahu
Gaurav Saxena
Vinay Gayki
Mohit Bhanwria
Durgesh KUMAR
Rahul Kumar
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Jio Platforms Ltd
Original Assignee
Jio Platforms Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Jio Platforms Ltd filed Critical Jio Platforms Ltd
Publication of WO2025069100A1 publication Critical patent/WO2025069100A1/fr
Anticipated expiration legal-status Critical
Pending legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/445—Program loading or initiating
    • G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0895—Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G06F2009/45595—Network integration; Enabling network access in virtual machine instances
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/34—Signalling channels for network management communication
    • H04L41/342—Signalling channels for network management communication between virtual entities, e.g. orchestrators, SDN or NFV entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities

Definitions

  • Embodiments of the present disclosure relate methods and systems for managing environment variables for Container Network Function Components (CNFCs) in a network environment.
  • CNFCs Container Network Function Components
  • CNF Container network function
  • CNFC Container network function
  • environment variables are required to be present in inventory.
  • CNF Container network function
  • 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.
  • 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.
  • PEEGN Policy Execution Engine
  • 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.
  • 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.
  • the set of environment variables with at least the CNFC are configured by the service manager during an instantiation of at least the CNFC.
  • 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.
  • 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.
  • 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.
  • 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.
  • the set of environment variables for at least the CNFC is received in a compressed format.
  • the set of environment variables for at least the CNFC is provided at the CNFLM by a user of the network environment.
  • 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.
  • PEEGN Policy Execution Engine
  • 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
  • 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 request from a container network function lifecycle manager (CNFLM).
  • the reserve request comprises a set of environment variables for at least a CNFC.
  • 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.
  • 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.
  • 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.
  • 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.
  • CNFCs Container Network Function Components
  • FIG. 1 illustrates an exemplary block diagram representation of a management and orchestration (MANO) architecture.
  • MANO management and orchestration
  • 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.
  • 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.
  • CNFCs Container Network Function Components
  • 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.
  • CNFCs Container Network Function Components
  • 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.
  • CNFCs Container Network Function Components
  • 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.
  • CNFCs Container Network Function Components
  • 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.
  • 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.
  • 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.
  • DSP Digital Signal Processing
  • 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.
  • a user equipment 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.
  • 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.
  • 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.
  • 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.
  • 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 more modules or one or more units with each other, which also includes the methods, functions, or procedures that may be called.
  • 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.
  • DSP digital signal processor
  • ASIC Application Specific Integrated Circuits
  • FPGA Field Programmable Gate Array circuits
  • 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.
  • 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.
  • CNFCs Container Network Function Components
  • 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.
  • FIG. 1 illustrates an exemplary block diagram representation of a management and orchestration (MANO) architecture/platform [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 a network node(s) etc/service(s).
  • the MANO architecture [100] deploys the network node(s) in the form of Virtual Network Function (VNF) and Cloud-native/ Container Network Function (CNF).
  • VNF Virtual Network Function
  • CNF Cloud-native/ Container Network Function
  • 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 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.
  • the system may comprise a NFV Platform Decision Analytics (NPDA) [1096] component.
  • NPDA NFV Platform Decision Analytics
  • the MANO architecture comprises a user 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 adaptors and utilities module [112] 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.
  • NFV network function virtualization
  • SDN software defined network
  • the NFV and SDN design function module [104] 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.
  • 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.
  • the CNF lifecycle manager [1052] may be similarly used for the CNFs lifecycle management.
  • the platforms foundation services module [106] 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 [100], 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.
  • API application programming interface
  • the platforms core services module [108] 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.
  • 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.
  • 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 platform database 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 [100] 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 [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.
  • the platform resource adaptors 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 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 [100]) 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 [100] for communication.
  • the Service Adaptor 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.
  • 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 [100],
  • FIG. 2 illustrates an exemplary block diagram of a computing device [200] upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure.
  • the computing device [200] may also implement a method for managing environment variables for Container Network Function Components (CNFCs) in a network environment, utilising the system.
  • the computing device [200] 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 [200], wherein said one or more units are capable of implementing the features as disclosed in the present disclosure.
  • CNFCs Container Network Function Components
  • 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 computing device [200] may also include a main memory [206], such as a random-access 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 processor [204], Such instructions, when stored in non-transitory storage media accessible to the processor [204], render the computing device [200] into a special-purpose 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 information and instructions for the processor [204],
  • ROM read only memory
  • 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 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.
  • 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].
  • 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.
  • 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 or programs the computing device [200] to be a special-purpose machine.
  • 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, such as the storage device [210], Execution of the sequences of instructions contained in the main memory [206] causes the processor [204] to perform the process steps described herein.
  • hard-wired circuitry may be used in place of or in combination with software instructions.
  • the computing device [200] also may include a communication interface [218] coupled to the bus [202], The communication interface [218] provides a two-way data communication coupling to a network link [220] that is connected to a local network [222],
  • the communication interface [218] 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.
  • the communication interface [218] may be a local area network (LAN) card to provide a data communication connection to a compatible LAN.
  • LAN local area network
  • Wireless links may also be implemented.
  • the communication interface [218] sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information.
  • the computing device [200] can send messages and receive data, including program code, through the network(s), the network link [220] and the communication interface [218],
  • 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, and/or stored in the storage device [210], or other non-volatile storage for later execution.
  • FIG. 3 an exemplary block diagram of a system [300] 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.
  • the system [300] may be implemented as or within a physical & virtual inventory manager (PVIM) unit.
  • the system [300] may include the physical & virtual inventory manager (PVIM) unit [300A],
  • the PVIM unit [300 A] may include at least one transceiver unit [302], at least one processing unit [304], and at least one storage unit [306],
  • the system [300] 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.
  • PVIM physical & virtual inventory manager
  • system [300] All of the components/ units of the system [300] are assumed to be connected to each other unless otherwise indicated below. As shown in 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 implement the features of the present disclosure. Further, in an implementation, the system [300] may be present in a user device/ user equipment to implement the features of the present disclosure. The system [300] 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 [300] 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 user device.
  • the system [300] 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 [300], The management is made possible through the interconnection and communication between various components of the system [300],
  • CNFCs Container Network Function Components
  • system [300] 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.
  • the transceiver unit [302] 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.
  • 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.
  • 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.
  • the set of environment variables for at least the CNFC, as included in the reserve request may be received in a compressed format.
  • 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.
  • 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.
  • the PVIM unit [300 A] may decompress the environment variables. This process restores the environment variables to their original format.
  • 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.
  • 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 data essential 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.
  • Examples of such environment variables 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.
  • the aforementioned exemplary environment variables may be configured by the service manager during instantiation of the CNFC.
  • 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.
  • 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.
  • 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 refers to a network administrator or operator who manually defines the environment variables required for the deployment or management of the CNFC.
  • 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).
  • GUI Graphical User Interface
  • CLI Command Line Interface
  • the GUI may include a set of already configured deployment profiles. Each of the deployment profile may include a number of CNFCs 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.
  • 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.
  • PVIM Physical & Virtual Inventory Manager
  • the processing unit [304] may set a reserved status associated with the set of environment variables based on the reserve request.
  • the processing unit [304] 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 [304] signals that the environment variables are now ready for deployment and that the resources associated with them are allocated within the network infrastructure.
  • the transceiver unit [302] may transmit details of the set of environment variables and the reserved status to a Policy Execution Engine (PEEGN) node.
  • PEEGN Policy Execution Engine
  • 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.
  • 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.
  • the transceiver unit [302] 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.
  • 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.
  • 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.
  • the PVIM unit [300A] Upon receiving this update inventory request, the PVIM unit [300A] will process the changes and update its inventory of resources.
  • 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.
  • the instantiation refers to the process of deploying and configuring the CNFC, making it operational within the network.
  • 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.
  • 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.
  • 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.
  • the CNFLM sends an update inventory request to inform the PVIM unit [300A],
  • 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.
  • the processing unit [304] may set a status of the one or more environment variables based on the update inventory request.
  • the status is set to ‘used’ in an event the successful instantiation of at least the CNFC is performed by the service manager.
  • 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.
  • 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.
  • the CNFC 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • FIG. 4 an exemplary method flow diagram [400] 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.
  • the method [400] is performed by the system [300], Further, in an implementation, the system [300] may be present in a server device to implement the features of the present disclosure. Also, as shown in FIG. 4, the method [400] starts at Step [402].
  • the method [400] comprises receiving, by a transceiver unit [302] 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.
  • PVIM Physical & Virtual Inventory Manager
  • CFLM Container Network Function Lifecycle Manager
  • the transceiver unit [302] 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.
  • the PVIM [300A] may be responsible for managing the lifecycle of one or more Container Network Functions (CNFCs).
  • CNFCs Container Network Functions
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • GUI Graphical User Interface
  • CLI Command Line Interface
  • 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.
  • PVIM Physical & Virtual Inventory Manager
  • the method [400] comprises 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.
  • the processing unit [304] may set a reserved status associated with the set of environment variables based on the reserve request.
  • the processing unit [304] 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 [304] signals that the environment variables are now ready for deployment and that the resources associated with them are allocated within the network infrastructure.
  • the method [400] comprises transmitting, by the transceiver unit [302] at the PVIM unit [300A], to a Policy Execution Engine (PEEGN) ode, details of the set of environment variables and the reserved status.
  • PEEGN Policy Execution Engine
  • the transceiver unit [302] may transmit details of the set of environment variables and the reserved status to a Policy Execution Engine (PEEGN) node.
  • PEEGN Policy Execution Engine
  • 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).
  • CNFC Container Network Function Component
  • 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.
  • 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.
  • Step [410] the method [400] receiving, by the transceiver unit [302] 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.
  • the transceiver unit [302] 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.
  • 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.
  • 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.
  • the PVIM unit [300A] Upon receiving this update inventory request, the PVIM unit [300A] will process the changes and update its inventory of resources.
  • 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.
  • the instantiation refers to the process of deploying and configuring the CNFC, making it operational within the network.
  • 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.
  • 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.
  • 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],
  • 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.
  • the method [400] comprises setting, by the processing unit [304] 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 [304] may set a status of the one or more environment variables based on the update inventory request.
  • the status is set to ‘used’ in an event the successful instantiation of at least the CNFC is performed by the service manager.
  • 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.
  • 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.
  • the CNFC 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.
  • 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.
  • 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.
  • the PVIM unit [300A] 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.
  • FIG. 5 illustrates an exemplary signalling diagram [500] 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.
  • CNFCs Container Network Function Components
  • the process begins when a user (a network administrator or operator) initiates a CNF instantiation request from the user interface [502], This request is the starting point for deploying the Container Network Function Component (CNFC).
  • CNFC Container Network Function Component
  • the instantiation request is initiated by the user at the UI, it is passed on to the CNFLM [504], as depicted by Step [516],
  • the CNFLM [504] 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.
  • 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.
  • the CNFLM On receiving the request from the User Interface [502] and the included environment variables, the CNFLM processes the same and transmits the request to the PVIM [508], This has been depicted by Step [518] in FIG. 5.
  • the PVIM [508] Upon receiving the reservation request from the CNFLM [504], the PVIM [508] takes control.
  • the PVIM [508] 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 [520], confirming that the ‘reserved status’ for the environment variables has been set.
  • the CNFLM [504] may transmit the Instantiation Request to the Service Adaptor [510], as depicted by Step [522] in FIG. 5.
  • the Service Adaptor [510] may be referred and understood as the Service Adaptor [1126] explained in conjunction with FIG. 1.
  • the Service Adaptor [510] coordinates the interaction between the PVIM [508] and the network’s physical host [512] to forward the instantiate CNF request message to the Host [512], as depicted by Step [524] in FIG. 5.
  • the Host is where the CNFC [504] is physically located. It is responsible for actually running the CNFC [504] within the network infrastructure. Once the CNFC [504] is instantiated, the Host [512] sends back an instantiation status to the Service Adaptor, as depicted by Step [526] in FIG. 5. The Service Adaptor [510] may accordingly transmit an acknowledgement to the PVIM [508], depicted by Step [528] to update the progress of the deployment.
  • the CNFLM [504] may issue an update inventory request to notify the PVIM, as depicted by Step [530] 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.
  • 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.
  • the CNFLM transmits the update instantiation status message to a Resource Management Repository (RMR) [514], as depicted by Step [534] in FIG. 5, indicating the final status of the CNFC instantiation.
  • RMR Resource Management Repository
  • the RMR resource management repository
  • the RMR [514] then sends an acknowledgement back to CNFLM, depicted by Step [536] in FIG. 5, confirming that the CNFC [504] instantiation status has been successfully updated in the system.
  • the CNF instantiation acknowledgement is returned from the CNFLM to the user interface [502], depicted by Step [538], indicating that the CNFC [504] has been successfully instantiated and the resources have been allocated and updated as per the reserve request.
  • FIG. 6 illustrates an exemplary signalling diagram [600] 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.
  • CNFCs Container Network Function Components
  • the process begins when a user (a network administrator or operator) initiates a CNF termination request from the user interface [502], This request is the starting point for 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 [504], as depicted by Step [602],
  • the CNFLM [504] may transmit the Termination Request to the Service Adaptor [510], as depicted by Step [604] in FIG. 6.
  • the Service Adaptor coordinates the interaction between the PVIM [508] and the network’s physical host [512] to forward the terminate CNF request message to the Host [512], as depicted by Step [606] in FIG. 6.
  • the Host [512] sends back a termination status to the Service Adaptor, as depicted by Step [608] in FIG. 6.
  • the Service Adaptor [510] may accordingly transmit an acknowledgement to the PVIM [508], depicted by Step [610] to update the progress of the termination.
  • the CNFLM [504] may issue an update inventory request to notify the PVIM, as depicted by Step [612] 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.
  • 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.
  • the CNFLM transmits the update instantiation status message to a Resource Management Repository (RMR) [514], as depicted by Step [616] in FIG. 6, indicating the final status of the CNFC termination.
  • RMR Resource Management Repository
  • the RMR resource management repository
  • the RMR [514] then sends an acknowledgement back to CNFLM, depicted by Step [618] in FIG. 6, confirming that the CNFC [504] termination status has been successfully updated in the system.
  • 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 [302], 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.
  • the instructions include executable code which, when executed, causes a processing unit [304], at the PVIM unit, to set a reserved status associated with the set of environment variables based on the reserve request.
  • the instructions include executable code which, when executed, causes the transceiver unit [302], at the PVIM unit, to transmit details of the set of environment variables and the reserved status to a Policy Execution Engine (PEEGN) node.
  • PEEGN Policy Execution Engine
  • the instructions include executable code which, when executed, causes the transceiver unit [302], 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.
  • the instructions include executable code which, when executed, causes 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.
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

La présente divulgation concerne un procédé et un système de gestion de variables d'environnement pour des composantes de fonction de réseau de conteneur (CNFC) dans un environnement de réseau dans un exemple, le procédé consistant à recevoir, au niveau d'une unité PVIM, de la part d'un gestionnaire de cycle de vie de fonction de réseau de conteneur (CNFLM), une demande de réserve contenant un ensemble de variables d'environnement pour au moins une CNFC. Le procédé consiste également à définir, par une unité de traitement au niveau de l'unité PVIM, un état réservé associé à l'ensemble de variables d'environnement sur la base de la demande de réserve. Le procédé consiste de même à transmettre, par l'unité d'émission-réception au niveau de l'unité PVIM, à un nœud PEEGN, des détails de l'ensemble de variables d'environnement et de l'état réservé. Le procédé consiste aussi à recevoir, par l'unité d'émission-réception au niveau de l'unité PVIM, de la part du CNFLM, une demande d'inventaire de mise à jour associée à une ou plusieurs variables d'environnement à partir de l'ensemble de variables d'environnement. Le procédé consiste en outre à définir, par l'unité de traitement au niveau de l'unité PVIM, un état desdites une ou plusieurs variables d'environnement sur la base de la demande d'inventaire de mise à jour.
PCT/IN2024/051897 2023-09-28 2024-09-28 Procédé et système de gestion de variables d'environnement pour des composantes de fonction de réseau de conteneurs dans un environnement de réseau Pending WO2025069100A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
IN202321065359 2023-09-28
IN202321065359 2023-09-28

Publications (1)

Publication Number Publication Date
WO2025069100A1 true WO2025069100A1 (fr) 2025-04-03

Family

ID=95201427

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IN2024/051897 Pending WO2025069100A1 (fr) 2023-09-28 2024-09-28 Procédé et système de gestion de variables d'environnement pour des composantes de fonction de réseau de conteneurs dans un environnement de réseau

Country Status (1)

Country Link
WO (1) WO2025069100A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020140938A1 (fr) * 2019-01-02 2020-07-09 中国移动通信有限公司研究院 Procédé, dispositif et système de gestion de ressources virtuelles basée sur un conteneur
IN201921030943A (fr) * 2019-07-31 2021-02-05
CN114629794A (zh) * 2020-12-09 2022-06-14 华为技术有限公司 硬件资源管理方法及通信装置
EP3807760B1 (fr) * 2018-06-18 2023-09-13 Orange Procédé d'installation d'une fonction réseau virtualisée

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3807760B1 (fr) * 2018-06-18 2023-09-13 Orange Procédé d'installation d'une fonction réseau virtualisée
WO2020140938A1 (fr) * 2019-01-02 2020-07-09 中国移动通信有限公司研究院 Procédé, dispositif et système de gestion de ressources virtuelles basée sur un conteneur
IN201921030943A (fr) * 2019-07-31 2021-02-05
CN114629794A (zh) * 2020-12-09 2022-06-14 华为技术有限公司 硬件资源管理方法及通信装置

Similar Documents

Publication Publication Date Title
US20230342183A1 (en) Management method and apparatus for container cluster
WO2025069101A1 (fr) Procédé et système permettant de gérer des ressources de réseau
WO2025074405A1 (fr) Procédé et système de gestion d'un ou de plusieurs services
WO2025069100A1 (fr) Procédé et système de gestion de variables d'environnement pour des composantes de fonction de réseau de conteneurs dans un environnement de réseau
WO2025069099A1 (fr) Procédé et système de gestion de ressources de fonction de réseau virtuel (vnf)
WO2025062452A1 (fr) Procédé et système permettant de surveiller des opérations se rapportant à des fonctions de réseau dans un environnement de réseau
WO2025062462A1 (fr) Procédé et système de gestion d'opérations d'inventaire dans un environnement de réseau
WO2025074400A1 (fr) Procédé et système de réservation de ressources dans un réseau
WO2025062461A1 (fr) Procédé et système permettant d'exécuter au moins une tâche de service
WO2025069085A1 (fr) Procédé et système pour effectuer une ou plusieurs opérations sur une ou plusieurs fonctions de réseau dans un réseau
WO2025069113A1 (fr) Procédé et système de gestion d'un ou de plusieurs nœuds de fonction réseau conteneurisée (cnf)
WO2025069082A1 (fr) Procédés et systèmes d'attribution d'une ou de plusieurs ressources de réseau dans un réseau de télécommunication
WO2025074437A1 (fr) Procédé et système de surveillance d'utilisation de ressources par des composants de nœud de réseau
WO2025069064A1 (fr) Procédé et système de gestion d'un hôte pour des composants de fonction de réseau de conteneur
WO2025074399A1 (fr) Procédé et système de gestion d'événement(s) concernant des politiques relatives à une ou à plusieurs opérations
WO2025062455A1 (fr) Procédé et système de gestion de ressources dans un environnement de réseau
WO2025069108A1 (fr) Procédé et système pour gérer l'inventaire d'un réseau
WO2025062451A1 (fr) Procédé et système d'évaluation d'une hystérésis pour un événement d'erreur
WO2025069073A1 (fr) Procédé et système de gestion de contraintes de ressources dans un réseau
WO2025069081A1 (fr) Procédés et systèmes de gestion d'opérations de base de données dans un réseau
WO2025057239A1 (fr) Procédé et système de réception d'un ensemble de paramètres de configuration cibles
WO2025069094A1 (fr) Procédé et système pour effectuer une gestion de ressources pour une instanciation de fonction de réseau virtuel (vnf)/composant de vnf
WO2025062450A1 (fr) Procédé et système de mise en œuvre d'actions correctives pendant un événement d'erreur de seuil de ressource
WO2025062459A1 (fr) Procédé et système de fourniture d'informations relatives à des ressources de réseau dans un environnement de réseau
WO2025069055A1 (fr) Procédé et système de gestion de groupe de protocole internet (ip)

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 24871261

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2024871261

Country of ref document: EP