WO2020186911A1 - Procédé et dispositif de gestion de ressources pour fonction de réseau virtualisé, vnf, conteneurisée - Google Patents

Procédé et dispositif de gestion de ressources pour fonction de réseau virtualisé, vnf, conteneurisée Download PDF

Info

Publication number
WO2020186911A1
WO2020186911A1 PCT/CN2020/071246 CN2020071246W WO2020186911A1 WO 2020186911 A1 WO2020186911 A1 WO 2020186911A1 CN 2020071246 W CN2020071246 W CN 2020071246W WO 2020186911 A1 WO2020186911 A1 WO 2020186911A1
Authority
WO
WIPO (PCT)
Prior art keywords
resource
container
container node
resource pool
vnf
Prior art date
Application number
PCT/CN2020/071246
Other languages
English (en)
Chinese (zh)
Inventor
夏海涛
Original Assignee
华为技术有限公司
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 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2020186911A1 publication Critical patent/WO2020186911A1/fr

Links

Images

Classifications

    • 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/0896—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR 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
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR 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/0893—Assignment of logical groups to network elements
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR 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

Definitions

  • This application relates to the field of communications technology, and in particular to a method and device for resource management of a containerized virtual network function VNF.
  • the network function virtualization (NFV) technology and the container as a service (CaaS) technology are two different stages of the telecom network operator’s cloudification transformation towards Internet technology (IT) Virtualization technology.
  • NFV technology means that telecom network operators learn from the virtualization technology in the IT field and decouple the software and hardware of telecom network functions to deploy and operate part of the telecom network on low-cost hardware devices such as general servers, switches, and storage. Functional technology.
  • CaaS technology refers to the decomposing of a single network function into multiple container services.
  • the container service can be directly invoked by a virtualized network function (VNF), or it can be invoked by a public service or a proprietary service invoked by the VNF.
  • VNF virtualized network function
  • the containerized VNF realizes the management of the containerized VNF through the management of the life cycle of the container service.
  • NFV technology can deploy and run some telecom network functions on low-cost hardware devices such as general-purpose servers, switches, and storage devices, it can reduce the cost of purchasing special equipment in telecom networks.
  • CaaS technology only involves processes. Compared with NFV technology, the container technology is lighter in weight and more convenient to manage. Therefore, a method of combining CaaS technology and NFV technology is proposed in the prior art.
  • the container service is closely related to the life cycle of the VNF that calls the container service.
  • the life cycle of the container service cannot be as fast in and out as the container application and container service in CaaS technology (that is, Quickly establish a container service, and then quickly delete the container service after using the container service for a specific container application), but like a VNF, it has a longer life cycle. Therefore, when CaaS technology is applied to NFV technology, the node resource pool of the container will not frequently allocate and reclaim container resources, but will form a situation where the content container service is always occupied by a type of VNF for a long period of time. In this case, how to manage the node resources of the containerized VNF is a technical problem that needs to be solved urgently.
  • the embodiments of the present application provide a resource management method and device of a containerized virtual network function VNF, which are used to meet the differentiated requirements of node resources of the telecommunication network function.
  • a method for resource management of a virtualized network function VNF is provided.
  • the VNFM accesses the virtualized network function descriptor VNFD corresponding to the VNF, from the VNFD Acquire description information of a resource specification of at least one virtual machine VM resource required for instantiating the VNF.
  • the resource specification may include a resource type and/or a resource capacity.
  • the VNFD may include at least one virtualization deployment unit VDU, and each VDU includes a resource specification for describing at least one VM resource corresponding to the VDU.
  • the VNFM divides the VM resources with the same resource specifications (determined by the VDU corresponding to the VM) into a container node resource pool according to the resource specifications of each VM resource, thereby according to at least one VM required for instantiating the VNF Resources, generating at least one container node resource pool, and each container node resource pool includes one VM resource or each container node resource pool includes at least two VM resources with the same resource specifications.
  • the VNFM sends the generated information of at least one container node resource pool to the container as a service manager.
  • the container as a service manager takes over the at least one container node resource pool to perform container resource management.
  • the VNFM refers to the VM resources of different resource specifications used to instantiate the VNF by referring to its VDU definition in the VNFD, creates at least one container node resource pool at the NFVI layer, and then Sending the information of the at least one container node resource pool to the container as a service manager can realize seamless connection between the container node resource pool managed by the container as a service manager and the VM resource of the VNF.
  • the container-as-a-service manager can create required container services for different components (VNFC) that make up the VNF on the resource pools of container nodes with different resource specifications, so that container services serving different telecom network functions can be based on different resource specifications
  • VNFC components
  • the management and arrangement of the container node resource pool can meet the differentiated requirements of the node resources of the telecommunications network function, and can improve the adaptability of the container node resources to the telecommunications network function.
  • each container node resource pool includes at least one of the following information:
  • the number of VM resources included in the container node resource pool is the number of VM resources included in the container node resource pool
  • the above information is only an example of the information of the container node resource pool, and the information of the container node resource pool may also include other content, which is not limited here.
  • the VNFM determines the mapping relationship between the VDU and the at least one container node resource pool based on the VM resources included in each container node resource pool and the corresponding relationship between the VDU and the VM resource .
  • the VNFM can send the stored mapping relationship between the VDU and the container node resource pool to the container-as-a-service manager, so that the content can be quickly restored.
  • the VNFM receives the first scaling request for instructing to add VM resources to the VNF. Then, the VNFM obtains the resource specifications of the increased VM resources, and adds the increased VM resources to the resource specifications of the VM resources. The added VM resource is in the first container node resource pool with the same resource specification, and the information of the first container node resource pool is updated.
  • the VNFM receives a second scaling request for instructing to reduce VM resources for the VNF, and then, the VNFM obtains the resource specifications of the reduced VM resources, from the resource specifications of the VM resources and the resources of the reduced VM resources In the second container node resource pool with the same specification, the reduced VM resource is deleted, and the information of the second container node resource pool is updated.
  • VM resources can also be deleted from the container node resource pool according to the scaling request.
  • the VNFM sends to the container-as-a-service manager a change request including information about the VM resource changed in the resource pool of the first container node, or, the VNFM sends to the container-as-a-service manager including A change request for the information of the VM resource changed in the resource pool of the second container node.
  • the container as a service manager can maintain synchronization with the information of the container node resource pool in the VNFM according to the change request sent by the VNFM.
  • the VNFM after the VNFM receives a termination request for instructing to release the VM resources used to instantiate the VNF, the VNFM sends to the container-as-a-service manager an instruction to de-configure and instantiate the VNF used
  • the de-configuration request of the container node resource of the VNF includes information of at least one container node resource pool corresponding to the VNF.
  • multiple container node resource pools created for the VNF can also be configured to recover the VM resources.
  • the container-as-a-service manager is an independently deployed entity for managing container node resources, or, the container-as-a-service manager is a VNF created by the VNFM according to the VNF instantiation request Instance.
  • the container as a service manager can be established in a variety of ways, which can increase the flexibility of the system.
  • a method for creating a virtual network function VNF is provided.
  • a virtual network function manager VNFM uses a virtual network function descriptor VNFD corresponding to the VNF, and , The mapping relationship between the pre-stored VDU and the container node resource pool determines the container node resource pool corresponding to the container service required to create the VNF, and at least one first virtualization deployment unit VDU included in the VNFD.
  • the VNFM sends a container service creation request to the container as a service manager.
  • the container service creation request includes the identifier of the container service required to create the VNF and the identifier of the resource pool corresponding to the container service.
  • the container as a service After receiving the creation request, the manager instantiates the container service required by the VNF on the resource pool corresponding to the container service, and after completing the creation, sends a response message to the VNFM, the response message is used to indicate the completion of the instance During the process of transforming the container service required by the VNF, the VNFM determines that the VNF is successfully created.
  • the VNFM determines the container node resource pool required by the VNF to be created, it can send the container node resource pool information required by the VNF to the container-as-a-service manager, so that the container-as-a-service manager can Creating the VNF on the corresponding container node resource pool can improve the efficiency of VNF creation.
  • an embodiment of the present application provides a communication device, which has the function of implementing the VNFM in the foregoing method.
  • the function can be realized by hardware, or by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above-mentioned functions.
  • the structure of the communication device includes a processor and a transceiver, and the processor is configured to process the communication device to perform corresponding functions in the foregoing method.
  • the transceiver is used to implement the communication between the above-mentioned communication device and the container as a service manager.
  • the communication device may further include a memory, which is used for coupling with the processor and stores the necessary program instructions and data of the communication device.
  • a processor and transceiver are included, where:
  • the transceiver receives the instantiation request of the virtualized network function VNF under the control of the processor;
  • the processor obtains the virtualized deployment unit VDU corresponding to the functional component used to instantiate the VNF, where the VDU includes virtual resource description information, and the virtual resource
  • the description information is used to determine the resource specifications of the virtual machine VM resources required to deploy the functional components, where the resource specifications include resource types and/or resource capacities; and at least one container node resource pool is created based on at least one VM resource, each A container node resource pool includes one VM resource or multiple VM resources with the same resource specifications, the at least one VM resource is determined by the virtualization infrastructure management VIM according to the VDU, and the at least one VM resource is used for deployment The VNF;
  • the transceiver Under the control of the processor, the transceiver sends the information of the at least one container node resource pool to the container-as-a-service manager, and the container-as-service manager takes over the at least one container node resource pool to perform container resource management.
  • the information of the resource pool of each container node is the same as the corresponding content in the first aspect, which is not repeated here.
  • the processor determines the VDU and the at least one container node resource pool based on the VM resources included in each container node resource pool and the correspondence between the VDU and the VM resource The mapping relationship.
  • the transceiver receives a first scaling request under the control of the processor, and the first scaling request is used to instruct to add VM resources to the VNF; the processor obtains the increased VM Resource specifications of the resources, adding the added VM resources to the first container node resource pool, and the resource specifications of the VM resources in the first container node resource pool are the same as the resource specifications of the added VM resources; and To update the information of the resource pool of the first container node.
  • the transceiver receives a second scaling request under the control of the processor, and the second scaling request is used to instruct to reduce VM resources for the VNF; the processor, the acquiring module, and Used to obtain the resource specification of the reduced VM resource, delete the reduced VM resource from the second container node resource pool, the resource specification of the VM resource in the second container node resource and the resource of the reduced VM resource
  • the specifications are the same; and, the information of the resource pool of the second container node is updated.
  • the transceiver sends a change request to the container as a service manager, where the change request includes information about the changed VM resource in the first container node resource pool.
  • the transceiver sends a change request to the container as a service manager, where the change request includes information about the changed VM resource in the second container node resource pool.
  • the transceiver under the control of the processor, receives a VNF termination request, where the termination request is used to instruct the release of VM resources used to instantiate the VNF; and, to the container That is, the service manager sends a de-configuration request, the de-configuration request is used to instruct to configure the container node resources used to instantiate the VNF, and the de-configuration request includes at least one container node resource pool corresponding to the VNF Information.
  • the container as a service manager is an independently deployed entity for managing container node resources, or the container as a service manager is created by the VNFM according to the VNF instantiation request VNF instance.
  • an embodiment of the present application provides a communication device, which has the function of implementing NFVO in the foregoing method.
  • the communication device may include corresponding functional modules, such as a receiving module, an acquiring module, a creating module, and a sending module, which are respectively used to implement the steps in the above method.
  • it includes a receiving module, an acquiring module, a creating module, and a sending module, where:
  • the receiving module is used to receive the instantiation request of the virtualized network function VNF;
  • the obtaining module is configured to obtain, according to the virtualized network function descriptor VNFD corresponding to the VNF, a virtualized deployment unit VDU corresponding to the functional component used to instantiate the VNF, the VDU includes virtual resource description information, and the virtual The resource description information is used to determine the resource specifications of the virtual machine VM resources required to deploy the functional components, where the resource specifications include resource types and/or resource capacities;
  • the creation module is configured to create at least one container node resource pool based on at least one VM resource, each container node resource pool includes one VM resource or multiple VM resources with the same resource specifications, and the at least one VM resource is the foundation of virtualization
  • the facility management VIM is determined according to the VDU, and the at least one VM resource is used to deploy the VNF;
  • the sending module is configured to send the information of the at least one container node resource pool to the container as a service manager, and the container as the service manager takes over the at least one container node resource pool to perform container resource management.
  • the information of the resource pool of each container node is the same as the corresponding content in the first aspect, which is not repeated here.
  • the creation module is also used to:
  • the mapping relationship between the VDU and the at least one container node resource pool is determined.
  • the receiving module is further configured to receive a first scaling request, where the first scaling request is used to instruct to add VM resources to the VNF;
  • the acquiring module is also used to acquire the resource specifications of the added VM resource;
  • the creation module is further configured to add the added VM resources to the first container node resource pool, the resource specifications of the VM resources in the first container node resource pool and the resource specifications of the added VM resources Same; and, update the information of the first container node resource pool.
  • the receiving module is further configured to receive a second scaling request, where the second scaling request is used to instruct to reduce VM resources for the VNF;
  • the acquiring module is also used to acquire the resource specifications of the reduced VM resources;
  • the creation module is further configured to delete the reduced VM resource from the second container node resource pool, and the resource specification of the VM resource in the second container node resource is the same as the resource specification of the reduced VM resource; And, update the information of the resource pool of the second container node.
  • the sending module is also used to:
  • the sending module is also used to:
  • the receiving module is further configured to receive a termination request of the VNF, where the termination request is used to instruct the release of VM resources used to instantiate the VNF;
  • the sending module is further configured to send a de-configuration request to the container as a service manager, where the de-configuration request is used to instruct to de-configure the container node resources used to instantiate the VNF, and the de-configuration request includes Information of at least one container node resource pool corresponding to the VNF.
  • the container-as-a-service manager is an independently deployed entity for managing container node resources, or the container-as-a-service manager is created by the VNFM according to the VNF instantiation request VNF instance.
  • an embodiment of the present application provides a communication device, which has the function of implementing the container as a service manager in the foregoing method.
  • the function can be realized by hardware, or by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above-mentioned functions.
  • the structure of the communication device includes a processor and a transceiver, and the processor is configured to process the communication device to perform corresponding functions in the foregoing method.
  • the transceiver is used to implement the communication between the above-mentioned communication device and the VNFM.
  • the communication device may further include a memory, which is used for coupling with the processor and stores the necessary program instructions and data of the communication device.
  • a processor and transceiver are included, where:
  • the transceiver receives information about at least one container node resource pool sent by the virtualized network function manager VNFM, and each container node resource pool includes one VM resource or multiple VMs with the same resource specifications Resource, the resource specification includes resource type and/or resource capacity;
  • the processor takes over the at least one container node resource pool and performs container resource management.
  • the information of the resource pool of each container node is the same as the corresponding content in the first aspect, which is not repeated here.
  • the transceiver receives a change request sent by the VNFM under the control of the processor, and the change request includes the change in the first container node resource pool or the second container node resource pool.
  • VM resource information, the at least one container node resource pool includes the first container node resource pool and the second container node resource pool.
  • the transceiver receives a de-configuration request sent by the VNFM under the control of the processor, and the de-configuration request is used to instruct to de-configure the container node resources used to instantiate the VNF ,
  • the de-configuration request includes information about at least one container node resource pool to be configured;
  • the processor releases the management of the at least one container node resource pool that is de-configured, and releases the VM resources in the at least one container node resource pool that is de-configured.
  • an embodiment of the present application provides a communication device that has the function of implementing the container as a service manager in the above method.
  • the communication device may include corresponding functional modules, such as a receiving module and a processing module, etc., which are respectively used to implement the steps in the above method.
  • it includes a receiving module and a processing module, where:
  • the receiving module is configured to receive information about at least one container node resource pool sent by the virtualized network function manager VNFM, each container node resource pool includes one VM resource or multiple VM resources with the same resource specifications, and the resource specifications Including resource type and/or resource capacity;
  • the processing module is also used to take over the at least one container node resource pool and perform container resource management.
  • the information of the resource pool of each container node is the same as the corresponding content in the first aspect, which is not repeated here.
  • the receiving module is further configured to receive a change request sent by the VNFM, and the change request includes the change of the VM resource in the first container node resource pool or the second container node resource pool.
  • the at least one container node resource pool includes the first container node resource pool and the second container node resource pool.
  • the receiving module is further configured to receive a de-configuration request sent by the VNFM, and the de-configuration request is used to instruct to de-configure the container node resources used to instantiate the VNF, and the The de-configuration request includes information about at least one container node resource pool to be configured;
  • the processing module is further configured to release the management of the at least one container node resource pool that has been unconfigured, and release the VM resources in the at least one container node resource pool that has been unconfigured.
  • an embodiment of the present application provides a communication device that has the function of implementing a VNFM or a container as a service manager in the method of the second aspect.
  • the function can be realized by hardware, or by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above-mentioned functions.
  • the structure of the communication device includes a processor and a transceiver, and the processor is configured to process the communication device to perform corresponding functions in the foregoing method.
  • the transceiver is used to implement the communication between the above-mentioned communication device and the container as a service manager.
  • the communication device may further include a memory, which is used for coupling with the processor and stores the necessary program instructions and data of the communication device.
  • an embodiment of the present application provides a communication device that has the function of implementing a VNFM or a container as a service manager in the method of the second aspect.
  • the communication device may include corresponding functional modules, such as a processing module, a sending module, and a receiving module, which are respectively used to implement the steps in the method of the second aspect.
  • an embodiment of the present application also provides a computer-readable storage medium, including instructions, which when run on a computer, cause the computer to execute the method executed by the VNFM or container-as-a-service manager in the first aspect.
  • an embodiment of the present application also provides a computer-readable storage medium, including instructions, which when run on a computer, cause the computer to execute the method executed by the VNFM or the container-as-a-service manager in the second aspect.
  • an embodiment of the present application also provides a computer program product, including instructions, which when run on a computer, cause the computer to execute the method executed by the VNFM or container-as-a-service manager in the first aspect.
  • the embodiments of the present application also provide a computer program product, including instructions, which when run on a computer, cause the computer to execute the method executed by the VNFM or the container-as-a-service manager in the second aspect.
  • an embodiment of the present application provides a chip system, which includes a processor and may also include a memory, for implementing the method executed by the VNFM or the container as a service manager in the first aspect.
  • the chip system can be composed of chips, or can include chips and other discrete devices.
  • an embodiment of the present application provides a chip system, which includes a processor and may also include a memory, for implementing the method executed by the VNFM or the container-as-a-service manager in the second aspect.
  • the chip system can be composed of chips, or can include chips and other discrete devices.
  • an embodiment of the present application provides a system that includes the communication device described in the third aspect and the communication device described in the fifth aspect, or includes the communication device described in the fourth aspect and the sixth aspect.
  • the communication device described in the aspect may include the communication device described in the seventh aspect and the communication device described in the eighth aspect.
  • Figure 1 is a schematic diagram of an NFV architecture provided in an embodiment of the application.
  • Fig. 2 is an architecture diagram of a kubernetes container management orchestration system provided by an embodiment of the application;
  • FIG. 3 is a schematic diagram of a deployment use case of a container service provided in an embodiment of the application.
  • FIG. 4 is a flowchart of a method for resource management of a virtual network function VNF provided in an embodiment of the application
  • FIG. 5 is a flowchart of a processing method of a virtual network function VNF resource management method in a capacity expansion scenario provided by an embodiment of the application;
  • FIG. 6 is a flowchart of a method for processing a virtual network function VNF resource management method in a scale-down scenario according to an embodiment of the application;
  • FIG. 7 is a flowchart of a processing method in a resource recovery scenario of a resource management method of a virtual network function VNF provided by an embodiment of the application;
  • FIG. 8 is a flowchart of a method for creating a virtual network function VNF according to an embodiment of the application
  • FIG. 9 is a mapping relationship between a VDU and a container node resource pool maintained locally by a VNFM in an embodiment of the application.
  • FIG. 10 is a schematic diagram of an example of a communication device provided by an embodiment of this application.
  • FIG. 11 is a schematic diagram of another example of a communication device provided by an embodiment of the application.
  • FIG. 12 is a schematic diagram of another example of a communication device provided by an embodiment of this application.
  • FIG. 13 is a schematic diagram of another example of a communication device provided by an embodiment of the application.
  • “multiple” refers to two or more than two. In view of this, “multiple” may also be understood as “at least two” in the embodiments of the present application. “At least one” can be understood as one or more, for example, one, two or more. For example, including at least one refers to including one, two or more, and does not limit which ones are included. For example, including at least one of A, B, and C, then the included can be A, B, C, A and B, A and C, B and C, or A and B and C.
  • ordinal numbers such as “first” and “second” mentioned in the embodiments of the present application are used to distinguish multiple objects, and are not used to limit the order, timing, priority, or importance of multiple objects.
  • FIG. 1 is a schematic diagram of an NFV architecture.
  • the NFV architecture can implement a variety of networks, such as a local area network (LAN), an internet protocol (IP) network, or an evolved packet core (EPC) network.
  • LAN local area network
  • IP internet protocol
  • EPC evolved packet core
  • the NFV architecture may include NFV management and orchestration system (NFV-MANO) 110, one or more operation support systems/business support systems (operation support system/business support system, OSS) /BSS) 120, multiple element manager (EM) 130, multiple VNF 140, and NFV infrastructure (NFV infrastructure, NFVI) 150.
  • NFV-MANO NFV management and orchestration system
  • OSS operation support system/business support system
  • BSS business support system
  • EM element manager
  • VNF 140 multiple VNF 140
  • NFV infrastructure NFV infrastructure
  • the NFV-MANO 110 may include an NFV orchestrator (NFVO) 111, one or more VNFMs 112, and a virtualized infrastructure manager (VIM) 113.
  • NFVO NFV orchestrator
  • VNFM virtualized infrastructure manager
  • NFVO network service descriptor
  • network service descriptor network service descriptor
  • VNF forwarding graph VNFFG
  • processing network service life cycle management
  • VNFM virtual network function forwarding graph
  • VNFM implements VNF lifecycle management, including virtualized network function descriptor (VNF Descriptor, VNFD) management, VNF instantiation, and VNF instance elastic scaling (including scaling out/up) and scaling (scaling in/ down)), healing of the VNF instance and termination of the VNF instance.
  • VNFM also supports receiving the scaling strategy issued by NFVO to realize automatic VNF elastic scaling.
  • VIM is mainly responsible for infrastructure layer hardware resources, virtualized resource management (including reservation and allocation), virtual resource status monitoring and fault reporting, and virtualized resource pools for upper-level applications.
  • OSS/BSS 120 is mainly for telecom service operators, providing comprehensive network management and business operation functions, including network management (such as fault monitoring, network information collection, etc.), billing management, and customer service management.
  • network management such as fault monitoring, network information collection, etc.
  • billing management billing management
  • customer service management customer service management
  • the EM 130 is used to perform traditional fault management, configuration management, account management, performance management, security management, and FCAPS (fault management, configuration management, account management, performance management, security management, FCAPS) functions for VNFs.
  • FCAPS fault management, configuration management, account management, performance management, security management, FCAPS
  • VNF 140 corresponds to the physical network function (PNF) in traditional non-virtualized networks, such as virtualized packet core (evolved packet core, EPC) nodes (for example, mobility management entity (MME)). ), serving gateway (serving gateway, SGW), public data network gateway (public data network gateway, PGW), etc.).
  • EPC virtualized packet core
  • MME mobility management entity
  • SGW serving gateway
  • PGW public data network gateway
  • PGW public data network gateway
  • the VNF 140 may be composed of one or more VNF components (VNF components, VNFC) of lower functional levels. Therefore, one VNF can be deployed on multiple virtual machines (VMs), each VM carries the function of a VNFC, and the VNF can also be deployed on one VM.
  • VNF components VNF components, VNFC
  • the NFVI 150 may include a virtual resource layer, a virtualization layer, and a hardware resource layer.
  • the virtual resource layer may include multiple VMs, or may also include virtual storage and virtual networks (not shown in FIG. 1).
  • the hardware resource layer may include computing hardware, storage hardware, network hardware, etc. (not shown in FIG. 1).
  • the hardware in the hardware resource layer may include a dedicated processor or a general-purpose processor for providing processing and computing functions, such as a central processing unit (CPU), and a device for providing storage capabilities, such as a disk or Network attached storage (NAS); and, switches, routers and/or other network equipment.
  • a dedicated processor or a general-purpose processor for providing processing and computing functions such as a central processing unit (CPU), and a device for providing storage capabilities, such as a disk or Network attached storage (NAS); and, switches, routers and/or other network equipment.
  • CPU central processing unit
  • NAS Network attached storage
  • the virtual resource layer may be provided to the VNF 140 in the form of a virtual machine, for example, one or more virtual machines form a VNF 140.
  • the virtualization layer forms a virtual network through the hardware in the hardware resource layer to implement communication between multiple virtual machines.
  • the virtual network can be virtualized through a virtual local area network (VLAN), virtual private LAN service (VPLS), virtual extensible local area network (VxLAN), or a general routing encapsulation network Technology (NVGRE) (nerwork virtualization using generic routing encapsulation, NVGRE).
  • VLAN virtual local area network
  • VPLS virtual private LAN service
  • VxLAN virtual extensible local area network
  • NVGRE general routing encapsulation network Technology
  • the virtualization layer in NFVI 150 is used to abstract the hardware resources of the hardware resource layer, decouple the VNF 140 from the physical layer to which the hardware resources belong, and provide virtual resources to the VNF.
  • NFV-MANO 110 can be used to realize the monitoring and management of VNF 140 and NFVI 150.
  • the NFVO 111 can communicate with one or more VNFM 112 to implement resource-related requests, send configuration information to the VNFM 112, and collect status information of the VNF 140.
  • the NFVO 111 can also communicate with the VIM 113 to realize resource allocation, and/or to realize the reservation and exchange of configuration information and status information of virtualized hardware resources.
  • the VNFM 112 may be used to manage one or more VNFs 140, and perform various management functions, such as initializing, updating, querying, and/or terminating the VNF 140.
  • VIM 113 can be used to control and manage the interaction of virtual resources and hardware resources in VNF 140 and NFVI. For example, VIM 113 may be used to perform resource allocation operations to VNF 140.
  • VNFM 112 and VIM 113 can communicate with each other to exchange virtualized hardware resource configuration and status information.
  • CaaS technology is a virtualization technology at the operating system level, through which different processes in the operating system are isolated, for example, the control group (CGroup) mechanism or the name space under the Linux operating system Mechanism etc. Since the CaaS technology has no virtual hardware, no operating system, and only processes, the CaaS technology is lighter and easier to manage than the NFV technology.
  • Figure 2 is an example of CaaS technology, the architecture diagram of kubernetes (K8S) container management orchestration system.
  • Kubernetes divides the devices in the cluster into a kubernetes master node (master) and a group of working nodes (node).
  • master master
  • node a group of working nodes
  • a set of processes related to cluster management are running on the master node, such as application programming interface service (application programming interface server, API server), replication controller (replication controller, RC), etc., these processes realize the entire cluster Management functions such as resource management, pod scheduling, elastic scaling, security control, system monitoring and error correction.
  • Run the three components of kubelet, proxy, and docker on each Node responsible for managing the life cycle of the Pod on this node, and realizing the function of service proxy.
  • the API Server provides the only operation entry for the resource object, and all other components must operate the resource data through the API interface it provides, and complete related business functions through "full query” and "change monitoring” of related resource data .
  • the controller manager is the management control center of the cluster, and its main purpose is to realize the fault detection and recovery automation of the kubernetes cluster.
  • the pod can be copied or removed according to the definition of RC to ensure that the number of pod instances conforms to the definition of RC.
  • the management relationship between the service and the pod the creation and update of the endpoints of the service, node Discovery, management and status monitoring of, as well as cleaning of local cached image files.
  • the kubelet component is responsible for the full lifecycle management of pod creation, modification, monitoring, and deletion on the node. At the same time, Kubelet regularly reports the status information of the node to the API Server.
  • the proxy component is used to implement load balancing between the service proxy and software mode.
  • the docker component is the operating environment of the container.
  • a platform as a service (PaaS) layer is added to the NFV MANO system, and the PaaS layer is located between VNF 140 and NFVI 150 in the NFV MANO system.
  • Container service for example, dedicated service, common service, or container infrastructure service
  • container service management for example, service management or container infrastructure service management) infrastructure service management
  • the container service can be directly invoked by the VNF, or it can be invoked by a public service or a proprietary service invoked by the VNF to form a containerized VNF.
  • the container service management function in the NFV MANO system to realize the life cycle management of the containerized VNF by the NFV MANO system.
  • the container-as-a-service manager shown in Figure 3 may be a management node in a container management orchestration system in CaaS technology.
  • the container management orchestration system is kubernetes
  • the container-as-a-service manager is The kubernetes master node can also be the container infrastructure service management function in the ETSI NFV IFA029 research report.
  • the current management mode of kubernetes for container services is a fast-forward and fast-out management method, it can be guaranteed that the node resource pool that provides resources (storage resources, computing resources, etc.) for the container service can always provide sufficient resource margin for allocation.
  • the container service is closely related to the life cycle of the VNF that invokes the container service.
  • the life cycle of the container service cannot be fast in and out like the container application and container service in the kubernetes system, but is related to the VNF. Same, has a long life cycle. Therefore, when containerization technology is applied to NFV, the node resource pool of the container will not frequently allocate and reclaim container resources, but will form a situation where the content container service is always occupied by a type of VNF for a long period of time.
  • the resource pool needs to be expanded or contracted as needed. How to manage the node resources of containerized VNFs is a technical problem that needs to be solved urgently.
  • the embodiments of the present application provide a resource management method of a virtual network function VNF.
  • the VNFM refers to VM resources of different resource specifications used to instantiate the VNF in the process of VNF instantiation.
  • the VDU definition in VNFD creates at least one container node resource pool at the NFVI layer, and then sends the information of the at least one container node resource pool to the container-as-a-service manager, which can realize the container node managed by the container-as-service manager
  • the resource pool and the VM resource of the VNF are seamlessly connected.
  • the container-as-a-service manager can create required container services for different components (VNFC) that make up the VNF on the resource pools of container nodes with different resource specifications, so that container services serving different telecom network functions can be based on different resource specifications
  • VNFC components
  • the management and arrangement of the container node resource pool can meet the differentiated requirements of the node resources of the telecommunications network function, and can improve the adaptability of the container node resources to the telecommunications network function.
  • the embodiment of the present application provides a resource management method of a virtual network function VNF. Please refer to FIG. 4, which is a flowchart of the method.
  • the following container as a service manager may be the container as a service manager shown in Figure 3, for example, the container That is, the service manager can be the kubernetes master node.
  • the method can be executed by two communication devices, such as a first communication device and a second communication device, where the first communication device may be a VNFM or a communication capable of supporting the functions required by the VNFM to implement the method.
  • the device can of course also be other communication devices, such as a chip system. The same is true for the second communication device.
  • the second communication device may be a container-as-a-service manager or a communication device capable of supporting functions required by the container-as-a-service manager, or may be a chip system. There are no restrictions on the implementation of the first communication device and the second communication device.
  • the VNFM receives a VNF instantiation request, and the VNFM executes the VNF instantiation process.
  • the VNF instantiation request may be initiated by EM or NFVO in the NFV architecture shown in FIG. 3, and the initiator of the VNF instantiation request is not restricted here.
  • the VNF instantiation request may carry the VNF identifier.
  • the VNFM After the VNFM receives the instantiation request of the VNF, it can verify the correctness of the instantiation request of the VNF. For example, it can be verified whether the identity of the VNF is correct, and after the verification is passed, the VNFM performs the VNF instantiation process.
  • the VNFM determines the resources required for instantiating the VNF.
  • the VNFM After the VNFM obtains the VNF instantiation request, it can determine the virtualized network function descriptor VNFD corresponding to the VNF according to the VNF identifier carried in the VNF instantiation request.
  • the VNFD may include information about one or more VDUs.
  • the information of a VDU specifies a resource specification of a VDU, such as at least one of the resource type and resource capacity of the VDU.
  • the resource types of VDUs may include, but are not limited to, three types. For example, they may include the type of VDU used to form the control plane function of the telecommunication network, the type of VDU used to form the user plane function of the telecommunication network, and the type of VDU used to form the user plane function of the telecommunication network.
  • the type of the VDU for the management plane function of the telecommunication network.
  • the resource type and resource capacity of the VDU can be used to characterize the number of central processing units (CPU) of the VM forming the VDU, CPU performance, memory size, bandwidth, storage size, and other information to form a Multiple VM resources of a type of VDU have the same resource specifications.
  • One type of VDU may include at least one VM resource. For example, a VDU forming a control plane function of a telecommunication network requires 5 VM resources, a VDU forming a user plane function of a telecommunication network requires 3 VM resources, and so on.
  • the VNFM sends a request message for allocating resources to the VIM, and the VIM receives the request message for allocating resources.
  • the VNFM After the VNFM determines the VM resource specifications required for implementing the VNF, it sends a request message for allocating resources to the VIM.
  • the request message carries information for determining the resources required for instantiating the VNF.
  • the request message for allocating resources is used as an example to request the allocation of computing resources, that is, the request message for VM resources.
  • the VIM obtains the information of the VM resource created for the VNF.
  • the information of the VM resource may be an identifier (ID) of the VM, or an index number, etc.
  • ID identifier
  • the information of the VM resource is the ID of the VM resource as an example.
  • the VIM can allocate the required VM resources for the VNF, or it can also obtain the information of the VM resources through interaction with the NFVI, and the manner in which the VIM obtains the information of the VM resources is not limited here.
  • the VIM may send an invocation message for invoking computing resources to the NFVI, and the invocation information includes information used to instantiate the VM resources required by the VNF.
  • the call information includes 3 types of VDUs, namely, the type of VDU used to form the control plane function of the telecommunication network, marked as VDU1, and the type of VDU used to form the user plane function of the telecommunication network, marked as VDU2 ,
  • the type of VDU used to form the management plane function of the telecommunication network, marked as VDU3, and VDU1 forming the control plane function of the telecommunication network requires 5 VM resources
  • VDU2 forming the user plane function of the telecommunication network requires 3 VMs Resources
  • the VDU3 that forms the management plane function of the telecommunications network requires 1 VM resource.
  • the NFVI After obtaining the call information, the NFVI creates the VM resources required by each VDU, and obtains the information of each VM resource, such as the identification (ID number or index number) of each VM resource. For example, NFVI creates VM1 to VM9, where VM1 to VM5 are VM resources required by VDU1, VM6 to VM8 are VM resources required by VDU2, and VM9 are VM resources required by VDU3. Then, the NFVI returns information indicating the VM resource to the VIM, so that the VIM obtains the information of the VM resource created for the VNF.
  • the VIM sends the VM resource information to the VNFM, and the VNFM receives the VM resource information.
  • the VNFM After the VNFM receives the VM resource information, it obtains the ID of the VM required to instantiate the VNF according to the VM resource information.
  • a VNFM is used to send a request message for allocating resources to the VIM, so as to obtain information for instantiating at least one VM resource required by the VNF.
  • the VNFM may also obtain the information of at least one VM resource required for instantiating the VNF in other ways. For example, VNFM sends a request message for allocating resources to NFVO. Then, NFVO instructs VIM to perform the operation of allocating computing resources, and then obtains the information of VM resources allocated to the instantiated VNF. Finally, NFVO will use it to instantiate the VNF. The information of VM resources required by the VNF is sent to the VNFM. In the embodiments of the present application, there is no restriction on the manner in which the VNFM obtains the information of at least one VM resource required to instantiate the VNF.
  • the VNFM generates a container node resource pool according to the allocated at least one VM resource.
  • the VNFM After the VNFM obtains the information of at least one VM resource required to implement the VNF, the VNFM then concatenates the VM resources with the same resource specifications into a container node resource according to the VDU information corresponding to each VM resource in the VNFD Pool.
  • the VM resources obtained by the VNFM to instantiate the VNF are VM1 ⁇ VM9, where VM1 ⁇ VM5 are VM resources defined by VDU1, VM6 ⁇ VM8 are VM resources defined by VDU2, and VM9 are defined by VDU3 VM resources. Therefore, the VNFM connects VM1 to VM5 into a container node resource pool, labeled NodePool1, connects VM6 to VM8 into a container node resource pool, labeled NodePool2, and VM9 forms a container node resource pool, labeled NodePool3. That is, each container node resource pool includes at least one VM resource, and when the container node resource pool includes multiple VM resources, the resource specifications of the multiple VM resources are the same.
  • the VNFM divides the at least one VM resource required by the VNF into at least one container node resource pool according to different VDUs.
  • the VNF may also be allocated The required at least one VM resource is divided into different container node resource pools according to the specifications of the VNFD.
  • a VNF may include one VNFD, and the VNFM may include at least one of the VNFDs according to the specifications of the VNFD corresponding to each VNF.
  • VM resources are concatenated into a container node resource pool.
  • the VNFM may also divide the container node resource pool according to other information. In the embodiment shown in FIG. 4, the division of the VNFM according to different VDUs is taken as an example.
  • the same VM resource may be reused by different VNFs, and then the same VM resource may appear in different container node resource pools. For example, if VNF1 and VNF2 reuse VM2, VM2 will appear in the container node resource pool corresponding to VNF1, and VM2 will also appear in the container node resource pool corresponding to VNF2.
  • a VM resource may belong to only one container node resource pool, or may belong to multiple container node resource pools, which is not limited here.
  • the VNFM establishes a mapping relationship between the VDU and the resource pool of the container node.
  • each VDU and the container node resource can be established according to the VM resources included in each container node resource pool and the corresponding relationship between the VDU and the VM resource
  • the mapping relationship of the pool may be a mapping relationship between the identifier of the VDU and the identifier of the container node resource pool.
  • VNFM can obtain the mapping relationship shown in Table 1.
  • VDU1 corresponds to NodePool1
  • VDU2 corresponds to NodePool2
  • VDU3 corresponds to NodePool3.
  • VDU logo The identifier of the container node resource pool VDU1 NodePool1 VDU2 NodePool2 VDU3 NodePool3
  • mapping relationship may also take other forms.
  • mapping relationship may be in the form of a description file, etc., and the specific form of the mapping relationship is not limited herein.
  • VNFM divides different container node resource pools according to the VNFD specifications
  • the VNFM needs to establish a mapping relationship between the VNFD identifier and the container node resource pool identifier.
  • VNFD 1 corresponds to NodePool 1
  • VNFD 2 corresponds to NodePool 2 etc.
  • the mapping relationship changes accordingly, and no examples are given here.
  • step S407 is an optional step, that is, it is not necessary to be performed.
  • the purpose of this application can be achieved without step S407.
  • the VNFM can store The mapping relationship between the VDU and the resource pool of the container node is sent to the container as a service manager, so that the content can be quickly restored.
  • the VNFM sends the information about the resource pool of at least one container node to the container as a service manager, and the container as a service manager receives the information about the resource pool of the at least one container node.
  • each container node resource pool may include, but is not limited to, the identifier of the container node resource pool; the number of at least one VM resource in the container node resource pool; at least one VM in the container node resource pool Any one or combination of resource specifications.
  • the VNFM sends the information of three container node resource pools to the container-as-a-service manager.
  • the identifiers of the three container node resource pools are NodePool1 ⁇ NodePool3, where NodePool1 includes 5 VM resources, and the NodePool1
  • the resource specifications of VM resources in the middle are the specifications required to form the control plane of the telecommunications network;
  • NodePool2 includes 3 VM resources, and the resource specifications of the VM resources in the NodePool2 are the specifications required to form the user plane of the telecommunications network;
  • NodePool3 includes One VM resource and the resource specifications of the VM resource in the NodePool3 are specifications required to form the management plane of the telecommunication network.
  • the control plane, user plane, or management plane all have their own quality of service (QoS) requirements, and the resource specifications correspond to their respective QoS requirements.
  • QoS quality of service
  • the QoS requirement is reflected by the calculation speed of different VM resources, and the resource specifications of each container node resource pool can be divided according to the calculation speed of the VM resources, for example, the VM resources included in NodePool1 It is a VM resource with a calculation speed of 100 instructions per second.
  • the VM resource included in NodePool2 is a VM resource with a calculation speed of 150 instructions per second.
  • the VM resource included in NodePool3 is a calculation speed per second.
  • the container as a service manager may be an independently deployed entity for managing container node resources.
  • it may be independently deployed in the NFV-MANO architecture. Deploy a kubernetes master node, and manage the PaaS layer through the kubernetes master node.
  • the kubernetes master node is the container as a service manager.
  • the container as a service manager may also be an instance created by the VNFM according to the instantiation request of the VNF.
  • a VNF can be composed of at least one VNFC, so that the container as a service manager can be used as a VNFC of the VNF and can be described in the VNFD of the VNF.
  • the instantiation order of the VNFC used to instantiate the container-as-a-service manager is the first VNFC that needs to be instantiated, and the other VNFCs need to be instantiated after the VNFC used to instantiate the container-as-a-service manager is started. .
  • step S409 may be performed first, that is, the container as a service manager is instantiated, and then step S406 and subsequent steps are performed.
  • step S409 is an optional step, that is, it is not necessary to be performed. Therefore, step S409 is a dotted line in FIG. 4 to indicate that this step is an optional step.
  • the container as a service manager manages the resources in the resource pool of each container node.
  • the container-as-a-service manager After obtaining the information of the node resource pool corresponding to different resource specifications, the container-as-a-service manager maintains the information of each container node resource pool locally.
  • the node controller (node controller) component in the kubernetes master node can be used to monitor the running status of the node resources (that is, VM resources) in the resource pool of each container node.
  • the running status can include health status or Abnormal state.
  • the node controller component can trigger the recovery of the node resource, that is, return the node resource to the manager that initially allocated the resource, such as VIM.
  • the VNFM creates at least one container node resource pool on the NFVI layer in the NFV MANO system, and then sends the information of the at least one container node resource pool to the container-as-a-service manager.
  • the container node resource pool managed by the service manager seamlessly connects with the VM resource of the VNF.
  • the container-as-a-service manager can create required container services based on the VNF on the container node resource pools of different resource specifications, so that container services serving different telecom network functions can be performed based on the container node resource pools of different resource specifications Management and orchestration can meet the differentiated requirements of node resources for telecom network functions, and can improve the adaptability of container node resources to telecom network functions.
  • a VNF instantiation scenario is taken as an example to describe the resource management method provided in the embodiment of the present application.
  • the VM resources in the container node resource pool may increase, or the VNF may also need to be expanded.
  • FIG. 5 provides a flowchart of a processing method of a virtual network function VNF resource management method in a capacity expansion scenario according to an embodiment of this application. A detailed description will be given below with reference to steps S501 to S512.
  • the NFVO sends a first scaling request
  • the VNFM receives the first scaling request.
  • the first scaling request is used to instruct the VNF to increase VM resources.
  • the NFVO sends a first scaling request to the VNFM, and the first scaling request carries the identification of the VNF that needs to be expanded and the identification of the VDU corresponding to the VNFC that needs to be expanded.
  • first scaling request may also be sent by the EM, and the sender of the first scaling request is not restricted here.
  • the VNFM determines, according to the VDU corresponding to the VNFC that needs to be expanded, the increased resources required for expansion.
  • the VNFM When the VNFM receives the first scaling request, it obtains the VNFD corresponding to the VNF according to the VNF identifier in the first scaling request, and then determines the VDU to be expanded according to the VDU identifier in the first scaling request Information.
  • the specific process is similar to the corresponding content in step S402, and will not be repeated here.
  • the VNFM sends a request message for allocating resources to the VIM, and the VIM receives the request message for allocating resources.
  • the VIM obtains the information of the VM resource created for the VNF.
  • the VIM sends the VM resource information to the VNFM, and the VNFM receives the VM resource information.
  • Steps S503 to S505 are similar to steps S403 to S405, and will not be repeated here.
  • the VNFM After the VNFM receives the instruction information, it determines the VM resources allocated in the VDU1 according to the instruction information. For example, the VM resources allocated by the VDU1 are VM1 to VM5 and VM10.
  • the VNFM can store the VM resource information allocated by the VDU1 last time. For example, the VM resources allocated last time by the VDU1 are VM1 to VM5, so that the VNFM determines the information of the added VM resources. As an example, the information of the added VM resource is VM10.
  • the VNFM determines the resource specification of the added VM resource.
  • the VNFM determines that the ID of the added VM resource is VM10, it determines the resource specification of the VM resource according to the information of the VDU obtained in step S502. For example, if the identifier of the VDU to be added is VDU1, the VNFM determines that the resource specification of VM10 is the resource specification corresponding to VDU1.
  • the VNFM adds the increased VM resources to the first container node resource pool.
  • the resource specification of at least one VM resource in the first container node resource pool is the same as the resource specification of the added VM resource.
  • the VNFM determines to add VM10 to the container node resource pool corresponding to VDU1, that is, to add VM10 to NodePool1.
  • the VNFM updates information about the resource pool of the first container node.
  • NodePool1 Because VNFM adds VM110 to NodePool1, the number of VM resources included in NodePool1 and the identification of the included VM resources have changed. After the expansion, NodePool1 includes VM1 ⁇ VM5 and VM10, and the number of VM resources has changed from 5 to 5. 6 pcs.
  • the VNFM sends a change request to the container-as-service manager, and the container-as-service manager receives the change request.
  • the change request includes the updated information of the resource pool of the first container node.
  • the change request carries the VM resources included in the expanded NodePool1 and the number of VM resources.
  • the embodiment shown in FIG. 5 takes a VNF capacity expansion scenario as an example to describe the resource management method provided in the embodiment of the present application.
  • the following describes the VNF scaling scenario.
  • FIG. 6 provides a flowchart of a processing method of a virtual network function VNF resource management method in a scale-down scenario according to an embodiment of this application. The detailed description will be given below with reference to steps S601 to S612.
  • the NFVO sends a second scaling request, and the VNFM receives the second scaling request.
  • the second scaling request is used to instruct the VNF to reduce VM resources.
  • the NFVO sends a second scaling request to the VNFM.
  • the second scaling request carries the identification of the VNF that needs to be scaled down and the identification of the VDU corresponding to the VNFC that needs to be scaled down.
  • the VNFM determines, according to the VDU corresponding to the VNFC that needs to be scaled down, the resources to be reduced for the scale down.
  • the VNFM sends a request message for allocating resources to the VIM, and the VIM receives the request message for allocating resources.
  • the VIM obtains the information of the VM resource created for the VNF.
  • the VIM sends the VM resource information to the VNFM, and the VNFM receives the VM resource information.
  • Steps S603 to S605 are similar to steps S403 to S405, and will not be repeated here.
  • the information of the reduced VM resource is VM5.
  • the VNFM determines the resource specification of the reduced VM resource.
  • the VNFM determines that the reduced VM resource is VM5
  • the resource specification of VM5 is the resource specification corresponding to VDU1 according to the information of the VDU obtained in step S502.
  • the VNFM deletes the reduced VM resource from the second container node resource pool.
  • the VNFM determines to delete VM5 from the container node resource pool corresponding to VDU1.
  • the first container node resource and the second container node resource pool may be the same container node resource pool, or may be different container node resource pools, and there is no limitation here.
  • the VNFM updates the information about the resource pool of the second container node.
  • the VNFM deletes VM5 from NodePool1, the number of VM resources included in NodePool1 and the identification of the included VM resources have changed.
  • the reduced NodePool1 includes VM1 to VM4, and the number of VM resources has changed from 5 to 4 .
  • the VNFM sends a change request to the container as a service manager, and the container as a service manager receives the change request.
  • the change request includes the updated information of the resource pool of the second container node.
  • the change request carries the VM resources included in the expanded NodePool1 and the number of VM resources.
  • the embodiment shown in FIG. 6 takes a VNF scaling scenario as an example to describe the resource management method provided in the embodiment of the present application.
  • the following describes the resource recovery scenario of the VNF.
  • FIG. 7 provides a flowchart of a processing method of a resource management method of a virtual network function VNF in a resource recovery scenario according to an embodiment of this application.
  • the NFVO sends a VNF termination request to the VNFM, and the VNFM receives the VNF termination request.
  • the VNF termination request carries the VNF identifier, for example, the VNF identifier is VNF1.
  • the termination request is used to instruct the VNFM to release the VM resources used to instantiate the VNF.
  • the VNFM configures the mapping relationship between the VDU and the NodePool used by the VNF to be terminated.
  • the VNFM determines that the VNF1 needs to be terminated
  • the VDU and NodePool corresponding to the VNF1 are deleted.
  • the VNFD corresponding to VNF1 includes VDU1 to VDU3, where VDU1 corresponds to NodePool1, VDU2 corresponds to NodePool2, VDU3 corresponds to NodePool3, and the VNFM deletes the mapping relationship between VDU1 and NodePool1, the mapping relationship between VDU2 and NodePool2, and the mapping relationship between VDU3 and NodePool3.
  • the VNFM sends a de-configuration request to the container-as-service manager, and the container-as-service manager receives the de-configuration request.
  • the de-configuration request is used to instruct the container as a service manager to configure the container node resources used to instantiate the VNF.
  • the de-configuration request includes information of at least one container node resource pool corresponding to the VNF.
  • the de-configuration request includes the identifiers of NodePool1, NodePool2, and NodePool3.
  • the container-as-a-service manager After receiving the de-configuration request, the container-as-a-service manager will release the VM resources in the three container node resource pools, NodePool1, NodePool2, and NodePool3, and then The VM resources in the resource pools of the three container nodes, that is, VM1 to VM9, will be recycled by VIM, so that the VM1 to VM9 are managed by VIM.
  • Figs. 4 to 7 describe possible interaction processes involved in the resource management method of the VNF.
  • the following describes the VNF resource allocation scenario.
  • FIG. 8 provides a flowchart of a method for creating a virtual network function VNF according to an embodiment of this application.
  • the operator calculates the required resource objects based on the system specifications and fills in the VNFD. For example, if the operator determines that a VNF needs to be instantiated, the configuration information of the VNF can be filled in the VNFD. Then, the operator manually uploads the VNFD to the VNFM, or, alternatively, the OSS/BSS or other network management entities in the NFV architecture upload the VNFD to the VNFM through NFVO.
  • the VNFM receives the instantiation request of the VNF.
  • the VNFM determines the container node resource pool corresponding to the container service required to instantiate the VNF.
  • the VNFM determines to create the VNF according to the virtualized network function descriptor VNFD corresponding to the VNF, at least one first VDU included in the VNFD, and the mapping relationship between the pre-stored VDU and the container node resource pool The required resource pool of container nodes.
  • VDU1 and VDU4 correspond to NodePool1
  • VDU2 corresponds to NodePool2
  • VDU3 corresponds to NodePool3.
  • the VNFM determines that the VNF includes 3 VNFCs and the container service invoked by each VNFC, where VNFC1 corresponds to VDU1, VNFC2 corresponds to VDU2, and VNFC3 corresponds to VDU3. Then, the VNFM determines the location of the container node resource pool that needs to be deployed for the container service invoked by the VNFC deployed by the VDU based on the locally maintained mapping relationship between the VDU and the container node resource pool identifier. In the embodiment of the present application, the container node The location of the resource pool is also the identifier of the container node resource pool. For example, the VNFM determines that the container node resource pool required to instantiate the VNF is NodePool1 to NodePool3.
  • the VNFM sends a container service creation request to the container as a service manager, and the container as a service manager receives the container service creation request.
  • the container service creation request includes the identifier of the container service required to create the VNF and the identifier of the resource pool corresponding to each container service.
  • the identifiers of container services required to create a VNF are container service 1 to container service 4, where container service 1 and container service 2 correspond to NodePool 1, container service 3 corresponds to NodePool 2, and container service 4 corresponds to NodePool 3.
  • the container as a service manager instantiates the container service required by the VNF on the resource pool corresponding to the container service.
  • the container-as-a-service manager After receiving the container service creation request, the container-as-a-service manager instantiates the corresponding container service in the resource pool of the container node corresponding to each container service. For example, instantiate container service 1 and container service 2 on NodePool1, and then in NodePool2 Instantiate container service 3, and instantiate container service 4 in NodePool3.
  • the container service may be a pod in the kubernetes system.
  • the container-as-service manager sends a response message, and the VNFM receives the response message.
  • the response message is used to indicate the completion of the process of instantiating the container service required by the VNF.
  • the VNFM receives the response message from the container as a service manager, it is determined that the VNF instantiation process is successfully completed .
  • the methods provided by the embodiments of the present application are introduced from the perspectives of VNFM, container-as-a-service manager, and interaction between the two.
  • the VNFM and the container-as-a-service manager may include a hardware structure and/or a software module, which is implemented in the form of a hardware structure, a software module, or a hardware structure plus a software module Each function. Whether one of the above-mentioned functions is executed in a hardware structure, a software module, or a hardware structure plus a software module depends on the specific application and design constraint conditions of the technical solution.
  • FIG. 10 shows a schematic structural diagram of a communication device 1000.
  • the communication device 1000 may be a VNFM, which can implement the function of the VNFM in the method provided in the embodiment of the present application; the communication device 1000 may also be a device that can support the VNFM to implement the function of the VNFM in the method provided in the embodiment of the present application.
  • the communication device 1000 may be a hardware structure, a software module, or a hardware structure plus a software module.
  • the communication device 1000 may be implemented by a chip system. In the embodiments of the present application, the chip system may be composed of chips, or may include chips and other discrete devices.
  • the communication device 1000 may include a processing module 1001 and a communication module 1002.
  • the processing module 1001 may be used to perform step S401, step S402, step S406, and step S407 in the embodiment shown in FIG. 4, or may be used to perform step S502, step S506 to step S508 in the embodiment shown in FIG. , Or can be used to execute step S602, step S606 to step S608 in the embodiment shown in FIG. 6, or can be used to execute step S702 in the embodiment shown in FIG. 7, or can be used to execute step S702 in the embodiment shown in FIG. Steps S801 to S803 in the embodiment of, and/or other processes used to support the technology described herein.
  • the communication module 1002 can be used to perform step S403, step S405, step S409, and step S408 in the embodiment shown in FIG. 4, or can be used to perform step S501, step S503, and step S505 in the embodiment shown in FIG.
  • step S509 may be used to perform step S601, step S603, step S605, and step S609 in the embodiment shown in FIG. 6, or may be used to perform step S701 and step S703 in the embodiment shown in FIG. 7, Or it can be used to perform step S804 and step S806 in the embodiment shown in FIG. 8, and/or other processes used to support the technology described herein.
  • the communication module 1002 is used for the communication device 1000 to communicate with other modules, and it may be a circuit, a device, an interface, a bus, a software module, a transceiver, or any other device that can implement communication.
  • FIG. 11 shows a schematic structural diagram of a communication device 1100.
  • the communication device 1100 may be a container-as-a-service manager, which can realize the function of the container-as-a-service manager in the method provided in this embodiment of the application;
  • the container is the device for the function of the service manager.
  • the communication device 1100 may be a hardware structure, a software module, or a hardware structure plus a software module.
  • the communication device 1100 may be implemented by a chip system. In the embodiments of the present application, the chip system may be composed of chips, or may include chips and other discrete devices.
  • the communication device 1100 may include a processing module 1101 and a communication module 1102.
  • the processing module 1101 may be used to perform step S410 in the embodiment shown in FIG. 4, or may be used to perform step S805 in the embodiment shown in FIG. 8, and/or used to support other processes of the technology described herein .
  • the communication module 1102 may be used to perform step S409 and step S408 in the embodiment shown in FIG. 4, or may be used to perform step S509 in the embodiment shown in FIG. 5, or may be used to perform the implementation shown in FIG.
  • Step S609 in the example may be used to perform step S703 in the embodiment shown in FIG. 7, or may be used to perform step S804 and step S806 in the embodiment shown in FIG. 8, and/or used to support this article Other processes of the described technique.
  • the communication module 1102 is used for the communication device 1100 to communicate with other modules, and it may be a circuit, a device, an interface, a bus, a software module, a transceiver, or any other device that can implement communication.
  • the division of modules in the embodiments of the present application is illustrative, and is only a logical function division. In actual implementation, there may be other division methods.
  • the functional modules in the various embodiments of the present application may be integrated into one process. In the device, it can also exist alone physically, or two or more modules can be integrated into one module.
  • the above-mentioned integrated modules can be implemented in the form of hardware or software functional modules.
  • FIG. 12 shows a communication device 1200 provided by an embodiment of the application, where the communication device 1200 may be the VNFM in the embodiment shown in FIG. 4 or FIG. 5 to FIG. 8, which can implement the method provided in the embodiment of the application
  • the function of the VNFM; the communication device 1200 may also be a device capable of supporting the VNFM to implement the function of the VNFM in the method provided in the embodiments of the present application.
  • the communication device 1200 may be a chip system.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • the communication device 1200 includes at least one processor 1220, which is configured to implement or support the communication device 1200 to implement the VNFM function in the method provided in the embodiment of the present application.
  • the processor 1220 may determine the resources required for instantiating the VNF. For details, refer to the detailed description in the method example, which is not repeated here.
  • the communication device 1200 may further include at least one memory 1230 for storing program instructions and/or data.
  • the memory 1230 and the processor 1220 are coupled.
  • the coupling in the embodiments of the present application is an indirect coupling or communication connection between devices, units, or modules, and may be in electrical, mechanical or other forms, and is used for information exchange between devices, units or modules.
  • the processor 1220 may cooperate with the memory 1230 to operate.
  • the processor 1220 may execute program instructions stored in the memory 1230. At least one of the at least one memory may be included in the processor.
  • the communication device 1200 may further include a communication interface 1210 for communicating with other devices through a transmission medium, so that the device used in the communication device 1200 can communicate with other devices.
  • the other device may be a control device.
  • the processor 1220 may use the communication interface 1210 to send and receive data.
  • connection medium between the aforementioned communication interface 1210, the processor 1220, and the memory 1230 is not limited in the embodiment of the present application.
  • the memory 1230, the processor 1220, and the communication interface 1210 are connected by a bus 1240.
  • the bus is represented by a thick line in FIG. 12, and the connection mode between other components is only for schematic illustration. , Is not limited.
  • the bus can be divided into address bus, data bus, control bus, etc. For ease of representation, only one thick line is used to represent in FIG. 12, but it does not mean that there is only one bus or one type of bus.
  • the processor 1220 may be a general-purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component. Or execute the methods, steps, and logical block diagrams disclosed in the embodiments of the present application.
  • the general-purpose processor may be a microprocessor or any conventional processor. The steps of the method disclosed in the embodiments of the present application may be directly embodied as being executed and completed by a hardware processor, or executed and completed by a combination of hardware and software modules in the processor.
  • the memory 1230 may be a non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), etc., or a volatile memory (volatile memory), For example, random-access memory (RAM).
  • the memory is any other medium that can be used to carry or store desired program codes in the form of instructions or data structures and that can be accessed by a computer, but is not limited thereto.
  • the memory in the embodiments of the present application may also be a circuit or any other device capable of realizing a storage function, for storing program instructions and/or data.
  • FIG. 13 shows a communication device 1300 provided by an embodiment of this application, where the communication device 1300 may be a container as a service manager, which can implement the function of the container as a service manager in the method provided by the embodiment of the application; the communication device 1300 It may also be a device capable of supporting the container-as-a-service manager to realize the function of the container-as-a-service manager in the method provided in the embodiments of the present application.
  • the communication device 1300 may be a chip system.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • the communication device 1300 includes at least one processor 1320, which is configured to implement or support the communication device 1300 to implement the function of the container as a service manager in the method provided in the embodiment of the present application.
  • the processor 1320 may manage the resources in the resource pool of each container node. For details, refer to the detailed description in the method example, which is not repeated here.
  • the communication device 1300 may further include at least one memory 1330 for storing program instructions and/or data.
  • the memory 1330 and the processor 1320 are coupled.
  • the coupling in the embodiments of the present application is an indirect coupling or communication connection between devices, units, or modules, and may be in electrical, mechanical or other forms, and is used for information exchange between devices, units or modules.
  • the processor 1320 may cooperate with the memory 1330 to operate.
  • the processor 1320 may execute program instructions stored in the memory 1330. At least one of the at least one memory may be included in the processor.
  • the communication device 1300 may further include a communication interface 1310 for communicating with other devices through a transmission medium, so that the device used in the device 1300 can communicate with other devices.
  • the other device may be an associated access point.
  • the processor 1320 may use the communication interface 1310 to send and receive data.
  • the embodiment of the present application does not limit the specific connection medium between the communication interface 1310, the processor 1320, and the memory 1330.
  • the memory 1330, the processor 1320, and the communication interface 1310 are connected by a bus 1340.
  • the bus is represented by a thick line in FIG. 13, and the connection mode between other components is only for schematic illustration. , Is not limited.
  • the bus can be divided into address bus, data bus, control bus, etc. For ease of presentation, only one thick line is used in FIG. 13, but it does not mean that there is only one bus or one type of bus.
  • the processor 1320 may be a general-purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component. Or execute the methods, steps, and logical block diagrams disclosed in the embodiments of the present application.
  • the general-purpose processor may be a microprocessor or any conventional processor. The steps of the method disclosed in the embodiments of the present application may be directly embodied as being executed and completed by a hardware processor, or executed and completed by a combination of hardware and software modules in the processor.
  • the memory 1330 may be a non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), etc., and may also be a volatile memory (volatile memory). For example, random-access memory (RAM).
  • the memory is any other medium that can be used to carry or store desired program codes in the form of instructions or data structures and that can be accessed by a computer, but is not limited thereto.
  • the memory in the embodiments of the present application may also be a circuit or any other device capable of realizing a storage function, for storing program instructions and/or data.
  • An embodiment of the present application also provides a computer-readable storage medium, including instructions, which when run on a computer, cause the computer to execute the method executed by the VNFM in the embodiments shown in FIGS. 4 to 8.
  • An embodiment of the present application also provides a computer-readable storage medium, including instructions, which when run on a computer, cause the computer to execute the method executed by the container-as-a-service manager in the embodiments shown in FIGS. 4-8.
  • the embodiments of the present application also provide a computer program product, including instructions, which when run on a computer, cause the computer to execute the method executed by the VNFM in the embodiments shown in FIGS. 4 to 8.
  • An embodiment of the present application also provides a computer program product, including instructions, which when run on a computer, cause the computer to execute the method executed by the container-as-a-service manager in the embodiments shown in FIGS. 4 to 8.
  • the embodiment of the present application provides a chip system.
  • the chip system includes a processor and may also include a memory for realizing the function of the VNFM in the foregoing method.
  • the chip system can be composed of chips, or can include chips and other discrete devices.
  • the embodiment of the present application provides a chip system, which includes a processor and may also include a memory, configured to implement the function of the container as a service manager in the foregoing method.
  • the chip system can be composed of chips, or can include chips and other discrete devices.
  • the embodiment of the present application provides a system including the aforementioned VNFM and a container as a service manager.
  • the methods provided in the embodiments of the present application may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software or firmware it can be implemented in the form of a computer program product in whole or in part.
  • the computer program product includes one or more computer instructions.
  • the computer may be a general-purpose computer, a dedicated computer, a computer network, network equipment, user equipment, or other programmable devices.
  • the computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website, computer, server, or data center.
  • a computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc., integrated with one or more available media.
  • the available medium may be a magnetic medium (for example, a floppy disk, hard disk, Magnetic tape), optical media (for example, digital video disc (DVD for short)), or semiconductor media (for example, SSD).

Landscapes

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

Abstract

L'invention concerne un procédé et un dispositif de gestion de ressources pour une fonction de réseau virtualisé, VNF, conteneurisée. Dans le procédé, un gestionnaire de fonction de réseau virtualisé, VNFM, lors de l'exécution du processus d'instanciation de VNF, se réfère à des définitions de VDU dans VNFD pour des ressources de VM utilisées pour instancier la VNF de différentes spécifications de ressource, crée au moins un groupe de ressources de noeud de conteneur au niveau de la couche de NFVI, puis, envoie les informations dudit au moins un groupe de ressources de noeud de conteneur à un conteneur en tant que gestionnaire de service, qui peut réaliser une connexion continue entre le groupe de ressources de noeud de conteneur géré par le conteneur en tant que gestionnaire de service et les ressources de VM de la VNF. Le conteneur en tant que gestionnaire de service peut créer les services de conteneur requis pour différents composants qui constituent la VNF sur les groupes de ressources de nœuds de conteneur de différentes spécifications de ressources, de sorte que les services de conteneur remplissant différentes fonctions de réseau de télécommunication puissent être gérés et agencés sur la base des groupes de ressources de noeud de conteneur de différentes spécifications de ressource, ce qui peut améliorer l'adaptabilité des ressources de noeud de conteneur à des fonctions de réseau de télécommunication.
PCT/CN2020/071246 2019-03-15 2020-01-09 Procédé et dispositif de gestion de ressources pour fonction de réseau virtualisé, vnf, conteneurisée WO2020186911A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910195790.6A CN111698112B (zh) 2019-03-15 2019-03-15 一种容器化虚拟网络功能vnf的资源管理方法及装置
CN201910195790.6 2019-03-15

Publications (1)

Publication Number Publication Date
WO2020186911A1 true WO2020186911A1 (fr) 2020-09-24

Family

ID=72475713

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/071246 WO2020186911A1 (fr) 2019-03-15 2020-01-09 Procédé et dispositif de gestion de ressources pour fonction de réseau virtualisé, vnf, conteneurisée

Country Status (2)

Country Link
CN (1) CN111698112B (fr)
WO (1) WO2020186911A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112468325A (zh) * 2020-11-11 2021-03-09 广州鲁邦通物联网科技有限公司 一种可复用的vpn架构和vpn调度方法
CN113839995A (zh) * 2021-09-06 2021-12-24 阿里巴巴（中国）有限公司 跨域资源纳管系统、方法、设备及存储介质
CN115914402A (zh) * 2022-11-09 2023-04-04 中国联合网络通信集团有限公司 算力资源节点的确定方法、装置、设备以及存储介质

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4226590A1 (fr) * 2020-11-09 2023-08-16 ZTE Corporation Procédé, dispositif et système de redimensionnement de groupe de conteneurs
WO2022188150A1 (fr) * 2021-03-12 2022-09-15 华为技术有限公司 Procédé de mise à l'échelle ascendante automatique, procédé de mise à l'échelle descendante automatique et dispositif
CN116016229A (zh) * 2021-10-21 2023-04-25 华为技术有限公司 一种部署容器服务的方法及装置
CN114189270B (zh) * 2021-10-25 2024-05-03 西安空间无线电技术研究所 一种部署UPF的星载gNB基站及其数据处理方法
WO2023150950A1 (fr) * 2022-02-10 2023-08-17 Zte Corporation Contrôleur de réseau de conteneurs
CN115145690B (zh) * 2022-06-30 2023-08-04 小米汽车科技有限公司 集群资源伸缩方法、装置及容器集群管理系统

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014176105A1 (fr) * 2013-04-22 2014-10-30 Cisco Technology, Inc. Portail de stockage d'applications pour le déploiement d'un pointage-cliquage de fonctions réseau virtualisées de tierce partie
CN105703927A (zh) * 2014-11-25 2016-06-22 华为软件技术有限公司 一种资源分配方法、网络设备和网络系统
CN105760214A (zh) * 2016-04-19 2016-07-13 华为技术有限公司 一种设备状态及资源信息监测方法、相关设备及系统
CN106209402A (zh) * 2015-04-30 2016-12-07 华为技术有限公司 一种虚拟网络功能的伸缩方法和设备
CN106664259A (zh) * 2015-07-17 2017-05-10 华为技术有限公司 虚拟网络功能扩容的方法和装置

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3602292A4 (fr) * 2017-03-24 2020-11-04 Nokia Technologies Oy Procédés et appareils pour mise à l'échelle de fonction de réseau virtualisé à plusieurs niveaux

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014176105A1 (fr) * 2013-04-22 2014-10-30 Cisco Technology, Inc. Portail de stockage d'applications pour le déploiement d'un pointage-cliquage de fonctions réseau virtualisées de tierce partie
CN105703927A (zh) * 2014-11-25 2016-06-22 华为软件技术有限公司 一种资源分配方法、网络设备和网络系统
CN106209402A (zh) * 2015-04-30 2016-12-07 华为技术有限公司 一种虚拟网络功能的伸缩方法和设备
CN106664259A (zh) * 2015-07-17 2017-05-10 华为技术有限公司 虚拟网络功能扩容的方法和装置
CN105760214A (zh) * 2016-04-19 2016-07-13 华为技术有限公司 一种设备状态及资源信息监测方法、相关设备及系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
HUAWEI: "Add VNF Expansion Procedure", 3GPP DRAFT; S5-151372, 6 February 2015 (2015-02-06), Taipei Taiwan, pages 1 - 2, XP050964943 *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112468325A (zh) * 2020-11-11 2021-03-09 广州鲁邦通物联网科技有限公司 一种可复用的vpn架构和vpn调度方法
CN113839995A (zh) * 2021-09-06 2021-12-24 阿里巴巴（中国）有限公司 跨域资源纳管系统、方法、设备及存储介质
CN115914402A (zh) * 2022-11-09 2023-04-04 中国联合网络通信集团有限公司 算力资源节点的确定方法、装置、设备以及存储介质
CN115914402B (zh) * 2022-11-09 2024-03-19 中国联合网络通信集团有限公司 算力资源节点的确定方法、装置、设备以及存储介质

Also Published As

Publication number Publication date
CN111698112B (zh) 2021-09-14
CN111698112A (zh) 2020-09-22

Similar Documents

Publication Publication Date Title
WO2020186911A1 (fr) Procédé et dispositif de gestion de ressources pour fonction de réseau virtualisé, vnf, conteneurisée
US10298439B2 (en) Network functions virtualization network system and data processing method, and apparatus
US20210326167A1 (en) Vnf service instantiation method and apparatus
WO2018058579A1 (fr) Procédé de gestion de tranche de réseau et unité de gestion
US20180302337A1 (en) Resource configuration method and network device thereof
WO2016121834A1 (fr) Procédé, système, dispositif et programme pour gérer une virtualisation de fonction de réseau
WO2019137516A1 (fr) Procédé et appareil de déploiement de tranche de réseau
CN109995552B (zh) Vnf服务实例化方法及装置
WO2019047835A1 (fr) Procédé d'instanciation pour une fonction de réseau virtuel
US20220350637A1 (en) Virtual machine deployment method and related apparatus
WO2016183832A1 (fr) Procédé et dispositif d'instanciation de service de réseau
EP4177742A1 (fr) Procédé et appareil de gestion multi-occupants
WO2022140945A1 (fr) Procédé et appareil de gestion de groupe de conteneurs
KR20220104241A (ko) 네트워크 작업 방법, 장치, 설비 및 저장매체
WO2022198524A1 (fr) Procédé de déploiement d'instance de service, et procédé et système d'équilibrage de charge entre nœuds
EP4191907A1 (fr) Procédé et appareil d'instanciation de vnf
WO2021022947A1 (fr) Procédé de déploiement d'une machine virtuelle et dispositif associé
WO2020249080A1 (fr) Procédé et appareil de déploiement de fonction réseau virtuelle (vnf)
WO2020077585A1 (fr) Procédé et appareil d'instanciation de service de vnf
JP7450072B2 (ja) 仮想化ネットワーク・サービス配備方法及び装置
WO2018120222A1 (fr) Procédé, dispositif et système de gestion de vnffg
EP4224332A1 (fr) Procédé et dispositif de mise en miroir de flux de données
WO2023066224A1 (fr) Procédé et appareil de déploiement d'un service de conteneur
CN112015515B (zh) 一种虚拟网络功能的实例化方法及装置
CN113098705B (zh) 网络业务的生命周期管理的授权方法及装置

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: 20773767

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20773767

Country of ref document: EP

Kind code of ref document: A1