WO2023179580A1 - 一种部署vnf的方法、装置及设备 - Google Patents

一种部署vnf的方法、装置及设备 Download PDF

Info

Publication number
WO2023179580A1
WO2023179580A1 PCT/CN2023/082655 CN2023082655W WO2023179580A1 WO 2023179580 A1 WO2023179580 A1 WO 2023179580A1 CN 2023082655 W CN2023082655 W CN 2023082655W WO 2023179580 A1 WO2023179580 A1 WO 2023179580A1
Authority
WO
WIPO (PCT)
Prior art keywords
vnf
cluster
information
cism
mciop
Prior art date
Application number
PCT/CN2023/082655
Other languages
English (en)
French (fr)
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 WO2023179580A1 publication Critical patent/WO2023179580A1/zh

Links

Classifications

    • 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
    • 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
    • G06F2009/45562—Creating, deleting, cloning virtual machine instances
    • 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/4557—Distribution of virtual machine instances; Migration and load balancing
    • 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 technical field of network function virtualization (NFV), and in particular to a method, device and equipment for deploying virtualized network functions (virtual network function (VNF)).
  • NFV network function virtualization
  • VNF virtual network function
  • NFV refers to the use of common hardware devices and virtualization technology to carry the functions of dedicated devices in traditional networks, thereby reducing the expensive costs of deploying dedicated devices.
  • decoupling software and hardware that is, software is not tied to proprietary hardware
  • network device functions no longer depend on dedicated hardware.
  • the characteristics of cloud computing are used to fully and flexibly share resources, realize rapid development and deployment of new services, and perform automatic deployment, elastic scaling, fault isolation and self-healing based on actual business needs.
  • the resource information required for container deployment may not be consistent with the container resources defined in the deployment package managed by the container management platform.
  • the container resources defined by the deployment package managed by the container management platform are greater than the resource information required for container deployment, the resources selected based on the resource information required for container deployment may be smaller than the container resources defined by the deployment package managed by the container management platform, thus The container resource cannot be created, causing deployment to fail.
  • the NFV orchestrator (NFVO) will Deploy the required resource information to select a container infrastructure service management (CISM).
  • MCIOP managed container infrastructure object packages
  • NFVO NFV orchestrator
  • VNFM VNF manager
  • the resource information required for container deployment is not consistent with the container resources defined by MCIOP.
  • the resources managed by the selected CISM may be smaller than the container resources defined by MCIOP, so container resources cannot be created, causing deployment to fail.
  • embodiments of the present application provide a method for deploying VNF.
  • the method includes: after obtaining the first information, the NFVO can obtain the connection information of the CISM used to manage the first cluster according to the first information; wherein the first information can be used to indicate the requirements of the VNF to be deployed for cluster resources; One cluster can meet the VNF's requirements for cluster resources. Then, the NFVO can send the first message containing the connection information to the VNFM to trigger the VNFM to Deploy VNF on the first managed cluster.
  • NFVO can obtain the connection information of the CISM that manages the first cluster that meets the requirements according to the VNF's requirements for cluster resources, and send the connection information to the VNFM; in this way, after obtaining the connection information, the VNFM can request
  • the CISM deploys the VNF on the first cluster. Since the container is deployed on the cluster, the first cluster can meet the VNF's requirements for the cluster and must also be able to meet the requirements for container deployment. Therefore, deploying VNF through this method can increase the possibility of successful VNF deployment.
  • Method 1 NFVO obtains the first information in VNFD.
  • NFVO can obtain the first information in the VNFD by parsing the VNFD.
  • Method 2 NFVO receives the first information from VNFM.
  • the VNFM may obtain the VNFD from the NFVO, and after obtaining the first information in the VNFD by parsing the VNFD, send the first information to the NFVO.
  • This design provides multiple ways to obtain the first information; through this design, NFVO can easily obtain the first information.
  • NFVO can obtain the first information in the VNF node information contained in VNFD.
  • the VNF node information may not include container resource information (for example, osContainerDesc as shown in Figure 5 below), but may include the first information used to indicate the VNF's requirements for cluster resources, thereby avoiding the need for containers in the VNFD.
  • Resource information conflicts with deployment packages managed by the container management platform, thereby increasing the possibility of successful VNF deployment.
  • the VNFD may also include: at least one manageable container base object package MCIOP, and information indicating the sequence of the at least one MCIOP. In this way, VNFM can deploy the at least one MCIOP according to the order of the at least one MCIOP.
  • NFVO can obtain the connection information of the CISM used to manage the first cluster in one of the following ways:
  • Method 1 When the first information indicates that the VNF is exclusive to the cluster, the NFVO may send a second message to the CCM to request the CCM to create a first cluster for the VNF that meets the requirements indicated by the first information; after creating the first cluster, the CCM may Send the connection information of the CISM used to manage the first cluster to the NFVO. Correspondingly, the NFVO may receive the connection information of the CISM used to manage the first cluster from the CCM.
  • NFVO can promptly trigger the creation of the first cluster that meets the VNF's requirements for cluster resources; in this way, when the VNF is deployed on the first cluster, the possibility of successful VNF deployment can be improved. sex.
  • Method 2 When the first information indicates that the VNF can share the cluster, the NFVO can select the first cluster for the VNF that meets the requirements indicated by the first information based on the first information, and obtain the connection information of the CISM used to manage the first cluster. .
  • NFVO when the VNF can share the cluster, NFVO can quickly select the first cluster that meets the VNF's requirements for cluster resources; in this way, when the VNF is deployed on the first cluster, the possibility of successful VNF deployment can be improved .
  • the NFVO before sending the first message to the VNFM, can also select a VNFM that supports the MCIOP type according to the MCIOP type of the VNF.
  • the MCIOP type includes: Helm; NFVO can select a VNFM that can parse the Helm.
  • NFVO selects VNFMs that can support MCIOP types to deploy VNFs, thereby increasing the likelihood of successful deployment of VNFs.
  • the NFVO may also send information to the VNFM indicating authorization to deploy the VNF in the first cluster.
  • the NFVO can conveniently indicate that VNFM has been authorized to deploy VNF in the first cluster.
  • the VNF's requirements for cluster resources may include: the number of resource nodes in the cluster where the VNF is deployed, and the resource size of each resource node in the cluster where the VNF is deployed. In this way, NFVO can determine the cluster resources required to deploy the VNF, thereby effectively determining the cluster used to deploy the VNF.
  • the VNF's requirements for cluster resources also include at least one of the following: the type of cluster where the VNF is deployed, the specifications of the cluster where the VNF is deployed, and whether the VNF shares the cluster.
  • the VNF's requirements for cluster resources can be flexibly designed, and NFVO can effectively determine the cluster to deploy the VNF accordingly.
  • embodiments of the present application provide a method for deploying VNF.
  • the method includes:
  • the VNFM may send a third message to the CISM based on the CISM's connection information.
  • the CISM manages the first cluster that meets the cluster resource requirements of the VNF to be deployed; the third message is used to request the CISM to deploy the VNF on the first cluster.
  • the CISM manages the first cluster that meets the VNF's requirements for cluster resources, and the VNFM requests the CISM to deploy the VNF on the first cluster. Since the container is deployed on the cluster, the first cluster can meet the VNF's requirements for the cluster and must also be able to meet the requirements for container deployment. Therefore, deploying VNF through this method can increase the probability of successful VNF deployment.
  • VNFM before receiving the first message from NFVO, VNFM can obtain the first information in VNFD and send the first information to NFVO; where the first information can be used to indicate VNF's requirements for cluster resources. .
  • VNFM can send the first information to NFVO; in this way, NFVO can obtain the connection information of the CISM that manages the first cluster that meets the requirements based on the first information, and trigger the VNFM to request to deploy VNF on the first cluster. Since the container is deployed on the cluster, the first cluster can meet the VNF's requirements for the cluster and must also be able to meet the requirements for container deployment. Therefore, deploying VNF through this method can increase the possibility of successful VNF deployment.
  • the VNFM can obtain the first information in the VNF node information contained in the VNFD.
  • the VNF node information may not include container resource information (for example, osContainerDesc as shown in Figure 5 below), but may include the first information used to indicate the VNF's requirements for cluster resources, thereby avoiding the need for containers in the VNFD.
  • Resource information conflicts with deployment packages managed by the container management platform, thereby increasing the possibility of successful VNF deployment.
  • the above method further includes: after the VNFM obtains at least one manageable container basic object package MCIOP in the VNFD and the information indicating the order of the at least one MCIOP, the VNFM may, according to the information indicating the order of the at least one MCIOP, MCIOP sequence information, deploy at least one MCIOP.
  • VNFM can effectively deploy at least one MCIOP in this order.
  • the VNFM may receive information from the NFVO indicating authorization to deploy the VNF in the first cluster. Through this design, VNFM can know that it has been authorized to deploy VNF in the first cluster.
  • the VNF's requirements for cluster resources may include: the number of resource nodes in the cluster where the VNF is deployed, and the resource size of each resource node in the cluster where the VNF is deployed. This design accurately indicates the cluster resources required to deploy the VNF.
  • the VNF's requirements for cluster resources may also include at least one of the following: the type of cluster where the VNF is deployed, the specifications of the cluster where the VNF is deployed, and whether the VNF shares the cluster.
  • embodiments of the present application provide an apparatus for deploying a VNF, including a unit for performing each step in any of the above aspects.
  • embodiments of the present application provide a device for deploying VNF, including at least one processor and at least one memory, wherein the at least one memory is used to store programs and data, and the at least one processor is used to read and execute the memory
  • the programs and data stored in the application enable the method provided by any of the above aspects of this application to be implemented.
  • embodiments of the present application provide a system for deploying VNFs, including: an NFVO for executing the method provided by the first aspect, and a VNFM used for executing the method provided by the second aspect.
  • embodiments of the present application also provide a computer program, which when the computer program is run on a computer, causes the computer to execute the method provided in any of the above aspects.
  • embodiments of the present application also provide a computer-readable storage medium.
  • a computer program is stored in the computer-readable storage medium. When the computer program is executed by a computer, it causes the computer to execute any of the above. methods provided.
  • embodiments of the present application also provide a chip, which is used to read the computer program stored in the memory and execute the method provided in any of the above aspects.
  • embodiments of the present application also provide a chip system.
  • the chip system includes a processor and is used to support a computer device to implement the method provided in any of the above aspects.
  • the chip system further includes a memory, and the memory is used to store necessary programs and data of the computer device.
  • the chip system can be composed of chips or include chips and other discrete devices.
  • FIG. 2 is a schematic diagram of the connection between K8S and Helm provided by the embodiment of this application;
  • Figure 3 is a schematic diagram of another NFV architecture provided by an embodiment of the present application.
  • Figure 4 is a flow chart of a method of deploying VNF
  • FIG. 5 is a schematic diagram of VNFD in the method shown in Figure 4.
  • Figure 6 is a flow chart of a method for deploying VNF provided by an embodiment of the present application.
  • Figure 7 is a flow chart of another method of deploying VNF provided by the embodiment of the present application.
  • Figure 8 is a schematic diagram of a possible VNFD in the method shown in Figure 7;
  • Figure 9 is a flow chart of another method of deploying VNF provided by the embodiment of the present application.
  • Figure 10 is a structural diagram of a device for deploying VNF provided by an embodiment of the present application.
  • Figure 11 is a structural diagram of a device for deploying VNF provided by an embodiment of the present application.
  • This application provides a method, device and equipment for deploying VNF to improve the possibility of successful VNF deployment.
  • the method, device and equipment are conceived based on the same technology. Since the principles of solving problems are similar, the device, device and equipment are similar. The implementation of equipment and methods can be referred to each other, and repeated descriptions will not be repeated.
  • the NFVO can obtain the connection information of the CISM used to manage the first cluster according to the first information; wherein the first information can be used to indicate the VNF's use of cluster resources. requirements, the first cluster can meet the VNF's requirements for cluster resources. Then, the NFVO may send the first message containing the connection information to the VNFM. After obtaining the connection information, the VNFM may request the CISM to deploy the VNF on the first cluster. Since the container is deployed on the cluster, the first cluster can meet the VNF's requirements for the cluster and must also be able to meet the requirements for container deployment. Therefore, deploying VNF through this method can increase the possibility of successful VNF deployment.
  • a network element can be a physical device in the network, or a device that integrates the functions of multiple physical devices.
  • the network element described in the embodiments of this application can also be a logical concept, such as a software module in a physical device, or a network function corresponding to the service provided by each network device.
  • the network function can be understood as a virtualization implemented using virtualization technology. function, etc.
  • Network service (NS) deployment template also known as network service descriptor (NSD)
  • NSD network service descriptor
  • NS can be, but is not limited to, an Internet protocol (internet protocol) multimedia subsystem (IP multimedia subsystem, IMS) network service, or a fifth generation (the 5th generation, 5G) core network network.
  • IP multimedia subsystem IP multimedia subsystem
  • 5G fifth generation core network network
  • An NS can contain one or more VNFs. Therefore, the NSD may include the topology information of the NS and the virtualization network functions descriptor (VNFD) of each VNF included in the NS.
  • the topology information may include virtualization connection information (for example, network service virtual link descriptor (NsVld)).
  • the virtualization connection information may be used to describe the connection between VNFs, for example, describing the connection. Type, bandwidth and other information.
  • VNFD For the content of VNFD, please refer to the explanation of VNFD in the explanation of terms below, which will not be expanded upon here.
  • the NSD can be provided by the service requester to the service provider.
  • the service requester may be the network element that initiates the virtualization request;
  • the service provider may be the network element that can receive the virtualization request and virtualize the corresponding service according to the virtualization request.
  • VDU Virtualization deployment unit
  • VDU When virtual machine (VM) technology is used to deploy VNF, one VDU can represent a virtual machine.
  • a virtual machine refers to a complete computer system with complete hardware system functions simulated by software and running in a completely isolated environment.
  • multiple virtual machines can be installed on a physical host (for example, a computer), and these virtual machines can share physical host resources.
  • one VDU can represent a group of containers; the containers in the group have the same resource requirements and can share the same network information.
  • each container can be deployed on a virtual machine or a physical machine (also called bare metal in this application).
  • VNFD also known as VNF deployment template
  • VNFD can be used to provide description information of VNF.
  • VNFD can include VDU, connection point descriptor (CPD), virtual link descriptor (VLD), etc. The information included in VNFD is described in detail below.
  • VDU When a VDU represents a virtual machine, the VDU may include resource requirement description information of the virtual machine, such as the resource types required to create the virtual machine and the number of resources of each resource type.
  • the VDU When a VDU When representing a group of containers, the VDU may include the resource requirement description information of this group of containers (which may also be called container resource information), which is used to represent the resource information required to deploy this group of containers.
  • CPD Can include type information and resource parameters for each type of external connection point in the VNF.
  • external connection points can be used for communication between VNF and external nodes.
  • the type information of the external connection point can be used to indicate the type of the external connection point.
  • external connection points can be divided into one major type (type): virtual connection point (virtual Cp).
  • Virtual connection points can be implemented through services, which include types such as node ports, load balancers, and external names.
  • the resource parameter of an external connection point can be used to indicate the resources required to create an external connection point of that type.
  • the resource parameters of the external connection point may include an address representation of the external connection point (eg, address representation as an IP address).
  • the resource parameters of the external connection point also include the types of functions supported by the external connection point.
  • VLD Can describe the virtual network connection requirements between VDUs, such as connection type and/or bandwidth and other information.
  • Container technology is a technology that uses virtualization technology to isolate different processes running on the host, thereby achieving mutual isolation and non-influence between processes and between processes and the host operating system.
  • This mutually isolated process is a container, and each container has its own set of file system resources and slave processes.
  • the number of nouns means “singular noun or plural noun", that is, “one or more”, unless otherwise specified.
  • “At least one” means one or more, and “plurality” means two or more.
  • “And/or” describes the relationship between associated objects, indicating that there can be three relationships.
  • a and/or B can mean: A alone exists, A and B exist simultaneously, and B alone exists.
  • the character “/” generally indicates that the related objects are in an “or” relationship.
  • A/B means: A or B.
  • “At least one of the following” or similar expressions refers to any combination of these items (items), including any combination of a single item (items) or a plurality of items (items).
  • the NFV architecture can implement a variety of networks, such as local area network (LAN), IP network or evolved packet core (EPC) network.
  • the NFV architecture may include an NFV management and orchestration system (NFV management and orchestration system, NFV-MANO) 110, an NFV infrastructure (NFV infrastructure, NFVI) 150, multiple VNFs 140, and multiple device management (element) management (EM) 130, and one or more operation support systems/business support systems (OSS/BSS) 120.
  • NFV-MANO 110 may include NFVO 111, one or more VNFMs 112, one or more virtualized infrastructure managers (VIM) 113, and one or more container infrastructure managers (container infrastructure service management, CISM)114.
  • NFVO111 Mainly responsible for handling the life cycle management of virtualization services, as well as the allocation and scheduling of virtual infrastructure and virtual resources in NFVI.
  • NFVO111 can communicate with one or more VNFM112 to perform resource-related requests, send configuration information to VNFM112, and collect status information of VNF140.
  • NFVO 111 can also communicate with VIM 113 to perform resource allocation and/or reservation, and exchange virtualized hardware resource configuration and status information.
  • VNFM112 Mainly responsible for the life cycle management of one or more VNFs, for example, deploying or instantiating VNF140, updating VNF140, querying VNF140, elastic scaling (scaling) VNF140, terminating VNF140 .
  • VNFM112 can communicate with VNF140 to complete VNF life cycle management and exchange configuration and status information.
  • VIM113 Mainly responsible for controlling and managing the interaction between VNF140 and computing hardware 1521, storage hardware 1522, network hardware 1523, virtual computing 1511 (such as VM), virtual storage 1512 and virtual network 1513.
  • VIM113 can also perform resource management functions, including managing infrastructure resources, allocating resources (for example, adding virtual resources to containers), and operating functions (for example, collecting NFVI fault information).
  • VIM 113 can communicate with VNFM 112, for example, allocate resources based on requests from VNFM 112, and exchange virtualization hardware resource configuration and status information with VNFM 112.
  • CISM114 It is a container management platform in the NFV architecture. It is mainly responsible for the management of container resources, including container creation, updating, query, elastic scaling and termination. When the VNF is deployed in the form of a container, CISM114 can create container resources based on the request of VNFM112.
  • CISM114 can be a common container management platform in the industry, such as kubernetes (hereinafter referred to as K8S).
  • K8S is currently the most widely used container management platform.
  • a K8S can manage a cluster, which can contain one or more physical machine resources and virtual machine resources. If K8S manages physical machine resources, K8S can deploy the created container on the physical machine; or if K8S manages virtual machine resources, K8S can deploy the created container on the virtual machine.
  • K8S uses pods as the smallest unit to create containers within the managed cluster.
  • a pod can include one or more containers.
  • NFVI150 It is the infrastructure layer of NFV, used to establish a virtualized environment, deploy, manage and implement VNF140.
  • NFVI 150 may include a hardware resource layer and/or a virtual resource layer (which may also be referred to as a software resource layer).
  • NFVI150 can also include a virtualization layer.
  • the hardware resource layer may include computing hardware 1521, storage hardware 1522, and network hardware 1523.
  • the computing hardware 1521 in the hardware resource layer can be a dedicated processor or a general-purpose processor used to provide processing and computing functions, such as a central processing unit (CPU); the storage hardware 1522 is used to provide storage capabilities, storage Hardware 1522 is, for example, a disk or network attached storage (NAS); network hardware 1523 can be a switch, router, and/or other network device.
  • the resources of computing hardware 1521 and storage hardware 1522 can be pooled together.
  • the virtualization layer in NFVI150 can be used to abstract the hardware resources of the hardware resource layer, decouple the VNF140 from the physical layer to which the hardware resources belong, and provide a virtualized environment, such as a virtual machine or other forms of virtual containers, to the VNF140.
  • the virtual resource layer may include virtual computing 1511, virtual storage 1512, and virtual network 1513.
  • Virtual computing 1511 and virtual storage 1512 can provide virtual resources to VNF 140 in the form of virtual machines or other virtual containers.
  • one or more virtual machines constitute a VNF 140.
  • the virtualization layer forms a virtual network 1513 by abstracting network hardware 1523 .
  • the virtual network 1513 may be used to implement communication between multiple virtual machines, or between multiple other types of virtual containers hosting VNFs.
  • EM130 It is a system used to configure and manage equipment in traditional telecommunications systems; in the NFV architecture, EM130 can also be used to configure and manage VNFs, and initiate the deployment of new VNFs to VNFM112 or Lifecycle management operations such as instantiation.
  • OSS/BSS120 Supports various end-to-end telecommunications services.
  • management functions supported by OSS include: network configuration, service provision, fault management, etc.; BSS handles orders, payments, revenue, etc., and supports product management, order management, revenue management and customer management.
  • VNF140 Corresponds to the physical network function (PNF) in traditional non-virtualized networks.
  • a virtualized packet core network (evolved packet core, EPC) node can correspond to at least one of the following: mobility management entity (mobility management entity, MME), serving gateway (serving gateway, SGW), public data network gateway (public data network gateway) data network gateway, PGW), etc.
  • mobility management entity mobility management entity
  • MME mobility management entity
  • serving gateway serving gateway
  • SGW serving gateway
  • public data network gateway public data network gateway
  • PGW public data network gateway
  • VNF140 can be implemented using virtual machine technology or containerization technology. If VNF 140 is implemented using virtual machine technology, the VNF component (VNF component, VNFC) included in the VNF can be deployed on one or more virtual machines. If VNF140 is implemented using container technology, the VNFC included in the VNF can be deployed on one or more containers.
  • VNF component VNF component, VNFC
  • Figure 3 is a schematic diagram of another NFV architecture applicable to the embodiment of the present application, or can be understood as a schematic diagram of another NFV architecture that introduces a container management platform.
  • the NFV architecture shown in Figure 3 also includes a container cluster manager (container identification system cluster manager, CCM) 115.
  • CCM115 can communicate with NFVO111 and CISM114 respectively.
  • CCM115 can cooperate with NFVO111 to manage CISM114.
  • the functions of other network elements except the CCM in Figure 3 can refer to the contents described in Figure 1 and will not be described again here.
  • Figure 4 shows a method of deploying VNFs. This approach can be used in the NFV architecture shown in Figure 1 or Figure 3. As shown in Figure 4, the method may include:
  • NFVO sends an instantiation request to VNFM to request deployment or instantiation of the VNF.
  • the instantiation request may include the identification of the VNF.
  • Deploying or instantiating a VNF can be understood as: allocating or creating the resources required for the VNF to implement corresponding functions (for example, creating a virtual machine or container for the VNF), and deploying the VNFC included in the VNF on the created virtual machine or container.
  • VNFM sends a request to the NFVO to obtain the VNFD (hereinafter referred to as the VNFD request).
  • the VNFM may obtain the identifier of the VNFD corresponding to the identifier of the VNF, and send a VNFD request containing the identifier of the VNFD to the NFVO.
  • NFVO may send the VNFD to the VNFM after obtaining the VNFD corresponding to the VNFD identifier.
  • the VNFD may include: container resource information and MCIOP referenced by the container management platform deployment template.
  • the container resource information can be an operating system container description template (osContainerDesc); each osContainerDesc can correspond to a container and mainly represents the resource information required to deploy the container.
  • the osContainerDesc may include at least one of the following: maximum CPU resources, minimum CPU resources, maximum memory resources, minimum memory resources, container images, etc. required to deploy the container corresponding to the VNF.
  • MCIOP can for example deploy packages for helm charts used by K8S.
  • VNFD may include: one or more VDUs (for example, VDU1 and VDU2 in Figure 5), one or more MCIOPs, and VNF node information.
  • VDUs for example, VDU1 and VDU2 in Figure 5
  • MCIOPs can correspond to one or more VDUs.
  • VNF node information may include basic information of VNFD, such as identification (identity, ID), name (name), version (version) and other information.
  • VNFM parses VNFD and obtains container resource information.
  • VNFM can parse osContainerDesc as container resource information in VNFD.
  • osContainerDesc may contain the following information:
  • requested_cpu_resources and cpu_resource_limit respectively indicate the minimum and maximum CPU resources required to deploy a container corresponding to the VNF.
  • requested_memory_resources and memory_resource_limit respectively indicate the minimum and maximum memory resources required to deploy the container.
  • sw_image is required to deploy the container. mirror information.
  • VNFM sends a resource authorization request to NFVO to request authorization for the resources indicated by the container resource information.
  • the resource authorization request may include: one or more container resource information corresponding to the VNF, or the total resources indicated by one or more container resource information corresponding to the VNF.
  • VNFM will request NFVO for authorization for the resource information described by each osContainerDesc.
  • NFVO sends a resource authorization response to VNFM to indicate successful authorization.
  • the resource authorization response may also be called an authorization success response.
  • NFVO can send a resource authorization response to VNFM after judging that CISM meets the requirements for creating a container corresponding to VMF.
  • NFVO can determine whether CISM meets the requirements for creating a container corresponding to VMF based on the remaining resources currently managed by CISM and the total resources indicated by one or more container resource information corresponding to the VNF. For example, when the remaining resources currently managed by CISM are greater than or equal to the total resources indicated by one or more container resource information corresponding to the VNF, NFVO determines that CISM meets the requirements for creating the container corresponding to the VMF; otherwise, NFVO determines that CISM does not meet the requirements for creating the container corresponding to the VNF. Requirements for containers corresponding to VMF.
  • the resource authorization response may include the CISM's connection information (for example, the CISM's address information or interface information of the CISM).
  • VNFM sends a container resource creation request to CISM based on the CISM connection information.
  • the container resource creation request contains MCIOP in VNFD.
  • the MCIOP may include:
  • some values can refer to the values.yaml file included in the Helm Chart, which can contain:
  • the cpu in limits can indicate the maximum CPU resources required by MCIOP
  • the memory in limits can indicate the maximum memory resources required by MCIOP
  • the cpu in requests can indicate the minimum CPU resources required by MCIOP
  • the memory in requests can indicate The minimum memory resources required by MCIOP.
  • the image describes the image information required by MCIOP to deploy the container.
  • CISM uses MCIOP to create container resources.
  • NFVO selects the CISM based on the resource information indicated by osContainerDesc.
  • NFVO authorizes the requested container resources based on the resource information indicated by osContainerDesc.
  • CISM creates container resources based on MCIOP. The resource information indicated by osContainerDesc may not be consistent with the container resources defined by MCIOP.
  • the container resources defined by MCIOP are greater than the sum of resources indicated by all osContainerDesc; at this time, the remaining resources managed by the selected CISM may be smaller than the container resources defined by MCIOP, that is, the resource requirements of MCIOP cannot be met, thus The container resource cannot be created, causing deployment to fail.
  • VNFM may also request the creation of container resources through deployment packages managed by other container management platforms.
  • the resources selected based on the resource information required for container deployment may also be smaller than those defined by deployment packages managed by other container management platforms.
  • Container resources so the container resources cannot be created, causing the deployment to fail.
  • the embodiment of this application provides a method for deploying VNF, which can be applied to the architecture shown in Figure 1 or Figure 3. Referring to the flow chart shown in Figure 6, the flow of this method will be described in detail below.
  • the requirements of the VNF on cluster resources can be understood as the requirements of the VNF to be deployed or the VNF to be instantiated on the cluster resources, that is, the requirements that the cluster resources used to deploy or instantiate the VNF need to meet.
  • VNF requirements for cluster resources may include:
  • the number of resource nodes in the cluster where VNF is deployed The number can be the minimum number of resource nodes required by the cluster where VNF is deployed, or it can be the range of the number of resource nodes required by the cluster where VNF is deployed.
  • each resource node in the cluster where VNF is deployed for example, the maximum CPU resource of each resource node in the cluster where VNF is deployed, the minimum CPU resource of each resource node in the cluster where VNF is deployed, At least one of the maximum memory resources of each resource node and the minimum memory resource of each resource node in the cluster where the VNF is deployed.
  • the VNF's requirements for cluster resources may also include, but are not limited to, at least one of the following:
  • the type of cluster where VNF is deployed For example, this type can be a virtual machine or a physical machine.
  • VNF shares the cluster It can be used to indicate whether the VNF can share the cluster with other VNFs. In other words, it can be used to indicate whether the VNF can exclusively occupy the cluster.
  • the first information may indicate the VNF's requirements for cluster resources in the following manner.
  • the number of resource nodes in the cluster where the VNF is deployed can be indicated by the first field of the first information.
  • the value of the first field may directly be the number of resource nodes in the cluster where the VNF is deployed; for example, the value of the first field is 6, indicating that the number of resource nodes in the cluster where the VNF is deployed is 6.
  • the first field may also indirectly indicate the number of resource nodes in the cluster where the VNF is deployed; for example, when the value of the first field is the first value, it indicates that the number of resource nodes in the cluster where the VNF is deployed is 6.
  • Each resource node in the cluster where the VNF is deployed can be indicated by the second field of the first information.
  • the value of the second field can directly be the resource size of each resource node in the cluster where the VNF is deployed; for example, the second field is the deployment The field corresponding to the minimum memory resource of the first resource node in the VNF cluster.
  • the value of the second field is 4GB, it means that the minimum memory resource of the first resource node in the cluster where the VNF is deployed is 4GB.
  • the type of cluster in which the VNF is deployed can be indicated by the third field in the first information.
  • the value of the third field may directly be the type of cluster where the VNF is deployed; for example, the value of the third field may be a virtual machine or a physical machine.
  • the third field can also indirectly indicate the type of cluster where the VNF is deployed; for example, when the value of the third field is the second value, it indicates that the type of the cluster where the VNF is deployed is a virtual machine. For example, when the value of the third field is the second value, it indicates that the type of the cluster where the VNF is deployed is a virtual machine. When the value is three, it indicates that the type of cluster where VNF is deployed is a physical machine. 4.
  • Whether the VNF shares the cluster can be indicated through the fourth field of the first information. For example, when the value of the fourth field is the fourth value (for example, true), it means that the VNF can share the cluster with other VNFs; when the value of the fourth field is the fifth value (for example, false (false) ), it means that the VNF cannot share the cluster with other VNFs.
  • the specifications of the cluster where the VNF is deployed can be indicated by the fifth field of the first information.
  • the value of the fifth field can directly be the specification of the cluster where the VNF is deployed; for example, the fifth field is the field corresponding to the specification of the memory used by the cluster where the VNF is deployed.
  • the value of the fifth field is 1GB, it means that the VNF is deployed.
  • the memory specification used by the cluster is 1GB.
  • NFVO obtains the connection information of the CISM used to manage the first cluster based on the first information. Among them, the first cluster can meet the VNF's requirements for cluster resources.
  • the CISM connection information may, but is not limited to, include at least one of the following: CISM address information, CISM interface information, etc.
  • the following example illustrates that the first cluster meets the VNF's requirements for cluster resources.
  • the VNF's requirements for cluster resources indicated by the first information include: the type of the cluster where the VNF is deployed is a virtual machine, and the maximum memory resource and the minimum memory resource required by the cluster where the VNF is deployed are both 4GB.
  • the first cluster may be a cluster composed of virtual machines, and the remaining memory resources of the first cluster are 4GB.
  • the VNF's requirements for cluster resources indicated by the first information include: the maximum memory resource required by the cluster where the VNF is deployed is 6GB, the minimum memory resource required by the cluster where the VNF is deployed is 2GB, and the VNF does not share the cluster.
  • the first cluster may be a cluster exclusive to the VNF, and the remaining memory resources of the first cluster may be any value between 2GB and 6GB (such as 3GB).
  • NFVO sends the first message to VNFM.
  • the first message may include CISM connection information and may be used to trigger the VNFM to deploy or instantiate the VNF on the first cluster managed by the CISM.
  • the first message may be an existing message (for example, an instantiation request or a resource authorization response, etc.) or a new message, which is not limited in this application.
  • the VNFM sends the third message to the CISM based on the CISM connection information.
  • the third message may be used to request CISM to deploy the VNF on the first cluster.
  • the VNFM may send the third message to the address indicated by the address information.
  • the connection information of the CISM includes the interface information of the CISM
  • the VNFM may send the third message to the interface indicated by the interface information.
  • the third message may be an existing message (for example, a container resource creation request) or a new message, which is not limited in this application.
  • the third message may also include the MCIOP of the VNF.
  • the CISM can deploy according to MCIOP on the first cluster, or instantiate the VNF.
  • NFVO obtains the connection information of the CISM that manages the first cluster according to the VNF's requirements for the cluster, and sends the connection information to the VNFM. Among them, the first cluster meets this requirement.
  • the VNFM can request the CISM to deploy the VNF on the first cluster. Since the container is deployed on the cluster, the first cluster can fully If it meets the requirements of VNF for clustering, it will also be able to meet the requirements of container deployment. Therefore, deploying VNF through this method can increase the probability of successful VNF deployment.
  • S601 can be implemented in one of the following ways:
  • Method 1 NFVO obtains the first information in the VNFD of the VNF.
  • NFVO can obtain the VNFD from the service requester when the service requester initiates the deployment of VNF.
  • the service requester can be, but is not limited to, a user or an EM.
  • NFVO can obtain the first information in the VNFD by parsing the VNFD.
  • the first information may also be included in the VNF node information in the VNFD; at this time, in the first method, NFVO may obtain the first information in the VNF node information.
  • the VNF node information may not include container resource information (for example, osContainerDesc shown in Figure 5), but may include the first information used to indicate the VNF's requirements for cluster resources, thereby avoiding the need for container resources in the VNFD. Information conflicts with deployment packages managed by the container management platform, thereby increasing the possibility of successful VNF deployment.
  • VNFM sends the first information to NFVO, and accordingly, NFVO receives the first information from VNFM.
  • the second method may include steps A1-A2:
  • VNFM obtains the first information in VNFD.
  • VNFM can obtain the VNFD from NFVO.
  • the VNFM can obtain the VNFD through the methods in S401-S403. Then, the VNFM can obtain the first information by parsing the VNFD.
  • the first information may be included in the VNF node information in the VNFD; at this time, in step A1, the VNFM may obtain the first information in the VNF node information.
  • the VNF node information may not include container resource information (for example, osContainerDesc shown in Figure 5), but may include the first information used to indicate the VNF's requirements for cluster resources, thereby avoiding the need for container resources in the VNFD. Information conflicts with deployment packages managed by the container management platform, thereby increasing the possibility of successful VNF deployment.
  • VNMF sends the first information to NFVO.
  • the first information may be carried in an existing message (for example, a resource authorization request) or in a new message, which is not limited in this application.
  • NFVO can easily obtain the first information.
  • S602 can be implemented in one of the following ways:
  • Method 1 When the first information indicates that the VNF is exclusive to the cluster (that is, the cluster is not shared), NFVO can trigger the creation of the first cluster and obtain CISM connection information used to manage the first cluster.
  • method 1 may include steps B1-B3:
  • the NFVO may send the second message to the CCM.
  • the second message may be used to request the CCM to create a first cluster for the VNF that meets the requirements indicated by the first information.
  • the second message may also include all the content in the first information, or may include information in the first information other than the information used to indicate whether the VNF shares the cluster.
  • the second message may be an existing message or a new message, which is not limited in this application.
  • the CCM creates the first cluster for the VNF that meets the requirements indicated by the first information.
  • the CCM may obtain connection information of the CISM used to manage the first cluster.
  • the CCM can create the first cluster through the CISM; during the creation process, the CCM can obtain the connection information of the CISM through interaction with the CISM.
  • CCM sends the connection information of the CISM used to manage the first cluster to NFVO.
  • the NFVO receives connection information from the CCM for managing the CISM of the first cluster.
  • the CISM connection information may be included in an existing message or a new message, which is not limited in this application.
  • NFVO can promptly trigger the creation of the first cluster that meets the VNF's requirements for cluster resources; in this way, when the VNF is deployed or instantiated on the first cluster, the success of VNF deployment can be improved possibility.
  • Method 2 When the first information indicates that the VNF can share cluster resources, the NFVO may select the first cluster that can meet the requirements indicated by the first information, and obtain the connection information of the CISM used to manage the first cluster.
  • method 2 may include steps C1-C2:
  • the NFVO can select the first cluster for the VNF that meets the requirements indicated by the first information based on the first information.
  • NFVO can select the first cluster based on the information of each cluster and the first information.
  • the information of each cluster may be obtained in advance, or may be obtained from the CISM that manages each cluster after receiving the first information.
  • the following example illustrates how NFVO selects the first cluster.
  • the VNF's requirements for cluster resources indicated by the first information include: the type of the cluster where the VNF is deployed is a virtual machine, the maximum and minimum memory resources required for the cluster where the VNF is deployed are both 4GB, and the VNF can share the cluster.
  • the cluster information obtained by NFVO includes: the type of cluster 1 is a virtual machine, and the remaining memory resources of cluster 1 are 4GB; the type of cluster 2 is a physical machine, and the remaining memory resources of cluster 2 are 4GB. At this time, NFVO can select cluster 1 as the first cluster.
  • the VNF's requirements for cluster resources indicated by the first information include: the type of the cluster where the VNF is deployed is a virtual machine, the maximum memory resource required by the cluster where the VNF is deployed is 5GB, and the minimum memory resources required by the cluster where the VNF is deployed are 5GB.
  • the VNF can share the cluster.
  • the cluster information obtained by NFVO includes: the type of cluster 1 is a virtual machine, and the remaining memory resources of cluster 1 are 4GB; the type of cluster 2 is a virtual machine, and the remaining memory resources of cluster 2 are 2GB. At this time, NFVO can select cluster 1 as the first cluster.
  • NFVO may randomly select one of them as the first cluster, or may select the one with the most remaining resources as the first cluster.
  • the method in Mode 1 can also be used to create a first cluster that can meet the requirements indicated by the first information.
  • C2 NFVO obtains the connection information of the CISM used to manage the first cluster.
  • the NFVO may include a corresponding relationship between the first cluster and the connection information of the CISM used to manage the first cluster. According to the corresponding relationship, the NFVO may obtain the connection information of the CISM used to manage the first cluster.
  • the expression form of the correspondence relationship may be a correspondence relationship table or other expression forms, which is not limited in this application.
  • NFVO can quickly select the first cluster that meets the VNF's requirements for cluster resources; in this way, when the VNF is deployed or instantiated on the first cluster, the cost of VNF deployment can be improved. possibility of success.
  • the method before S603, the method also includes:
  • NFVO selects a VNFM that supports the MCIOP type according to the MCIOP type of the VNF.
  • the MCIOP type may include but is not limited to: Helm; NFVO may select a VNFM capable of parsing the Helm.
  • the MCIOP type is included in the VNFD.
  • it can be included in the VNF node information in the VNFD or in the VNFM information (Vnfminfo) parameter.
  • the VnfmInfo parameter can also be included in VNFD.
  • the Vnfminfo parameter may include a first indication field used to indicate the MCIOP type.
  • the first indication field may be an existing cell in the Vnfminfo parameter or a new one in the Vnfminfo parameter. of cells.
  • the value of the first indication field is a sixth value (for example, VNFM-helm), it may be indicated that VNFM needs to be able to parse Helm.
  • the NFVO can first execute S605 and then send the VNFD to the VNFM.
  • NFVO selects a VNFM that can support MCIOP type to deploy VNF, thereby increasing the probability of successful deployment of VNF.
  • the method after S602, the method also includes:
  • the NFVO sends information to the VNFM indicating authorization to instantiate the VNF in the first cluster.
  • the information about instantiating the VNF in the first cluster can also be understood as the information about deploying the VNF in the first cluster.
  • the information indicating authorization to instantiate the VNF in the first cluster may be a message or an information element in the message.
  • the information used to indicate authorization to instantiate the VNF in the first cluster may reuse an existing message (for example, an instantiation request or resource authorization response), or it can be a new information element in an existing message.
  • the information element may be a second indication field (for example, grant information (grantInfo)).
  • the value of the second indication field is a seventh value (for example, approved), it may indicate that the authorization is in the first cluster.
  • the information element can be VIM connection information (VimConnectionInfo, used for the creation of a virtual machine VNF) or CISM Connection information; for example, when the information element is VimConnectionInfo, VimConnectionInfo can include connection information (for example, access address uniform resource locator (URL), user name, password, authentication parameters during access) etc.) and information indicating whether to authorize instantiation of the VNF in the first cluster.
  • VIM connection information VIM connection information
  • CISM Connection information CISM Connection information
  • connection information for example, access address uniform resource locator (URL), user name, password, authentication parameters during access) etc.
  • this application does not limit the execution order of S603 and S606.
  • S603 may be executed first and then S606;
  • S606 may be executed first and then S603;
  • S603 and S606 may also be executed simultaneously.
  • information indicating authorization to instantiate the VNF in the first cluster may be carried in the first message.
  • NFVO can conveniently indicate that VNFM has been authorized to deploy or instantiate VNF in the first cluster.
  • the above method may also include steps D1-D2:
  • the VNFM obtains at least one MCIOP in the VNFD, and information indicating the order of the at least one MCIOP.
  • the VNFD may include at least one MCIOP and information indicating the order of the at least one MCIOP.
  • the VNFD can be the VNFD in mode one or mode two; for the specific content of MCIOP, please refer to Figure 5 The description will not be repeated here.
  • the information indicating the order of the at least one MCIOP may directly or indirectly indicate the deployment order of the at least one MCIOP (which may also be referred to as the execution order).
  • the information indicating the order of the at least one MCIOP indirectly indicates the deployment order of the at least one MCIOP
  • the information indicating the order of the at least one MCIOP may indicate the dependence of the VNF on the at least one MCIOP.
  • the VNFM deploys at least one MCIOP according to the information indicating the order of the at least one MCIOP.
  • the VNFM may determine a deployment sequence of at least one MCIOP based on information indicating the sequence of at least one MCIOP, and deploy the MCIOPs according to the deployment sequence.
  • the following describes how the VNFM determines the deployment sequence of at least one MCIOP based on the information indicating the sequence of at least one MCIOP.
  • the information indicating the order of at least one MCIOP may indicate the deployment order of at least one MCIOP; the VNMF may determine the deployment order of at least one MCIOP by reading the information.
  • at least one MCIOP included in the VNFD is MCIOP 1 and MCIOP 2
  • the information indicating the order of at least one MCIOP indicates: the deployment order of MCIOP 1 is 1, and the deployment order of MCIOP 2 is 2; at this time, VNFM can determine to deploy first MCIOP 1, then deploy MCIOP 2.
  • the deployment order may be related to the VNF's dependency on at least one MCIOP (eg, dependency order). Therefore, the information indicating the order of the at least one MCIOP may indicate the deployment order of the at least one MCIOP by indicating the dependency of the VNF on the at least one MCIOP.
  • at least one MCIOP included in VNFD is MCIOP 1 and MCIOP 2.
  • the dependency relationship is: VNF first depends on MCIOP 1, and then depends on MCIOP 2; at this time, VNFM can determine to deploy MCIOP 1 first, and then deploy MCIOP 2.
  • VNFM deploys MCIOP according to this deployment sequence.
  • the VNFM may send the third message containing the corresponding MCIOP to the CISM in sequence according to the deployment sequence.
  • at least one MCIOP included in the VNFD is MCIOP 1 and MCIOP 2
  • the information used to indicate the order of the at least one MCIOP is: deploy MCIOP 1 first, and then deploy MCIOP 2.
  • VNFM first sends a third message containing MCIOP 1 to CISM, requesting CISM to deploy or instantiate VNF according to MCIOP 1 on the first cluster; then, sends a third message containing MCIOP 2 to CISM, requesting CISM to deploy or instantiate VNF according to MCIOP 2 on the first cluster. 2Deploy or instantiate VNF. In this way, CISM can deploy MCIOP 1 first and then deploy MCIOP 2.
  • the VNFM may send a third message to the CISM, the third message including at least one MCIOP in the VNFD and information indicating the sequence of the at least one MCIOP.
  • CISM can deploy at least one MCIOP in this order.
  • the manner in which CISM determines the deployment sequence of at least one MCIOP may refer to the manner in which VNFM determines the deployment sequence of at least one MCIOP, which will not be described again here.
  • VNFM can effectively deploy at least one MCIOP in the indicated sequence.
  • the method shown in Figure 7-8 mainly introduces the possible situation one, that is, NFVO parses the first information in the VNFD and obtains the CISM connection information based on the first information; the method shown in Figure 9 mainly introduces one of them.
  • the second possible scenario is that after the VNFM parses the first information in the VNFD, it sends the first information to the NFVO, and the NFVO obtains the CISM connection information based on the first information.
  • Figure 7 shows a method of deploying VNF, which can be applied to the architecture shown in Figure 1 or Figure 3. Referring to the flow chart shown in Figure 7, the flow of this method will be described in detail below.
  • NFVO obtains cluster capability (ClusterCapabilities) information in the VNFD.
  • the ClusterCapabilities information may be the first information in the method shown in Figure 6.
  • the ClusterCapabilities information may include cluster resource information and/or information indicating whether the VNF shares the cluster.
  • the cluster resource information may be used to indicate at least one of the following: the type of the cluster where the VNF is deployed, the resource size of the cluster where the VNF is deployed, the resource size of each resource node in the cluster where the VNF is deployed, and the specifications of the cluster where the VNF is deployed. For specific content, please refer to S601 and will not be repeated here.
  • FIG. 8 shows a possible implementation of the VNFD.
  • the VNFD may include at least one of the following: VNF node information including ClusterCapabilities information, one or more MCIOPs, and information indicating the order of MCIOPs.
  • ClusterCapabilities information describes the cluster resource requirements for VNF deployment.
  • the container corresponding to the VNF is deployed on the cluster managed by CISM. If the cluster is composed of virtual machines, the containers are deployed on the virtual machines (the containers deployed in this deployment method can be called virtual machine containers); if the cluster is composed of physical machines, the containers are deployed on the physical machines (the containers deployed in this deployment method are The container may be called a bare metal container).
  • the ClusterCapabilities information includes one or more items of the information shown in Table 1.
  • one VNF node information can correspond to one or more MCIOPs.
  • the VNFD may include information indicating the order of the multiple MCIOPs, and the order may be the deployment order of the multiple MCIOPs.
  • the information indicating the order of the plurality of MCIOPs may include requirement 1 (requirement_1) and requirement 2 (requirement_2).
  • requirement_1 can indicate that the deployment order of MCIOP_1 is 1
  • requirement_2 can indicate that the deployment order of MCIOP_2 is 2; that is to say, requirement_1 can indicate that when multiple MCIOPs are deployed, the first MCIOP to be deployed is MCIOP_1, and requirement_2 can indicate that multiple MCIOPs are deployed.
  • the MCIOP of the second deployment is MCIOP_1.
  • S702 NFVO obtains CISM connection information based on ClusterCapabilities information.
  • NFVO can obtain CISM connection information through one of the following implementation methods.
  • Implementation method 1 When the sharingIndicator parameter in ClusterCapabilities is false, NFVO requests The CCM creates a new cluster (ie, the first cluster in mode 1 of the method shown in Figure 6), and obtains the connection information of the CISM used to manage the first cluster.
  • this implementation method 1 may include:
  • S702a1 NFVO sends a message to CCM requesting the creation of the first cluster.
  • the message can include type and ResourceDefinition in ClusterCapabilities.
  • S702a2 After creating the first cluster that satisfies type and ResourceDefinition, CCM sends the connection information of the CISM that manages the first cluster to NFVO.
  • NFVO selects a CISM that can meet the needs of the cluster among the resources it manages. For example, select a CISM that manages clusters that satisfy type and ResourceDefinition (that is, the first cluster in mode 2 of the method shown in Figure 6). Then, NFVO can obtain the connection information of the CISM.
  • NFVO selects a VNFM that supports the MCIOP type based on the MCIOP type of the VNF.
  • the instantiation request contains CISM connection information.
  • the instantiation request may also include an indication of authorization passing. Since containers are deployed on clusters, meeting the requirements of the cluster means that the requirements for container deployment have also been met. Therefore, you can include an indication of authorization in the instantiation request.
  • the indication of authorization passing may be the information authorizing the instantiation of the VNF in the first cluster in the method shown in Figure 6. For specific content, please refer to S606, which will not be described again here.
  • the VNFM determines the deployment sequence of MCIOPs based on the information in the VNFD used to indicate the sequence of the multiple MCIOPs.
  • step D2 For the specific content of S705, please refer to step D2, which will not be described again here.
  • VNFM requests CISM to deploy MCIOP according to the deployment sequence.
  • VNFM can sequentially parse the MCIOP in VNFD through the Helm tool in VNFM according to the deployment sequence; then, according to the CISM connection information (for example, calling the CISM interface (such as K8S interface) indicated by the connection information), request CISM deploys MCIOP according to this deployment sequence.
  • CISM connection information for example, calling the CISM interface (such as K8S interface) indicated by the connection information
  • multiple MCIOPs are MCIOP 1 and MCIOP 2, information indicating the order of at least one MCIOP: deploy MCIOP 1 first, and then deploy MCIOP 2.
  • VNFM can first parse MCIOP 1 and then MCIOP 2 through the Helm tool in the VNFM; then, VNFM can call the CISM interface (such as the K8S interface) indicated by the CISM's connection information, first request CISM to deploy MCIOP 1, and then request CISM to deploy MCIOP 2.
  • CISM sends a container resource creation response to VNFM to indicate that the container resource is successfully created.
  • the VNFM sends an instantiation response to the NFVO to indicate successful deployment or instantiation of the VNF.
  • S705 is an optional step, and S706 can be replaced by VNFM. Request CISM to deploy MCIOP.
  • NFVO can parse the VNF's requirements for the cluster, and obtain the connection information of the CISM that manages the first cluster that meets the requirements based on the requirements; after receiving the connection information from the NFVO, the VNFM can request that the CISM manage the first cluster that meets the requirements.
  • cluster capability information is added to the VNF to replace the capacity Container resource information, thereby avoiding conflicts between container resource information in VNFD and MCIOP. Since the container is deployed on the cluster, the first cluster can meet the VNF's requirements for the cluster and must also be able to meet the requirements for container deployment. Therefore, deploying VNF through this method can increase the possibility of successful VNF deployment.
  • the VNFD contains information indicating whether the VNF shares a cluster, thereby enabling the VNF to deploy an exclusive cluster or a shared cluster.
  • Figure 9 shows a method of deploying VNF, which can be applied to the system architecture shown in Figure 1 or Figure 3. Referring to the flow chart shown in Figure 9, the flow of this method will be described in detail below.
  • VNFD the specific content of VNFD can be found in S701 and will not be repeated here.
  • NFVO selects a VNFM that supports the MCIOP type based on the MCIOP type in the VNFD.
  • NFVO sends an instantiation request to VNFM to request deployment or instantiation of the VNF.
  • VNFM sends a resource authorization request to NFVO.
  • the resource authorization request may include ClusterCapabilities information.
  • ClusterCapabilities information For the specific content of ClusterCapabilities information, please refer to S701 and will not be described again here.
  • VNFM can send a resource authorization request to NFVO after obtaining VNFD.
  • the method for VNFM to obtain VNFD can refer to S402-S403, which will not be described again here.
  • S905 NFVO obtains CISM connection information based on ClusterCapabilities information.
  • NFVO sends CISM connection information to VNFM.
  • CISM connection information can be included in the resource authorization response.
  • the VNFM determines the deployment sequence of MCIOPs based on the information in the VNFD used to indicate the sequence of the multiple MCIOPs.
  • VNFM requests CISM to deploy MCIOP according to the deployment sequence.
  • CISM sends a container resource creation response to VNFM to indicate that the container resource is successfully created.
  • the VNFM sends an instantiation response to the NFVO to indicate successful deployment or instantiation of the VNF.
  • VNFM can parse VNF's requirements for the cluster and pass the requirements through NFVO; NFVO can obtain the connection information of the CISM that manages the first cluster based on the requirements, where the first cluster meets the requirements; VNFM receives the request from After obtaining the connection information of the NFVO, the CISM can be requested to deploy the VNF on the first cluster.
  • cluster capability information is added to the VNF to replace the container resource information, thereby avoiding conflicts between the container resource information in the VNFD and MCIOP. Since the container is deployed on the cluster, the first cluster can meet the VNF's requirements for the cluster and must also be able to meet the requirements for container deployment. Therefore, deploying VNF through this method can increase the probability of successful VNF deployment.
  • the VNFD contains information indicating whether the VNF shares a cluster, thereby enabling the VNF to deploy an exclusive cluster or a shared cluster.
  • the embodiment of the present application provides a device for deploying VNF through Figure 10, which can be used to perform the functions of the relevant steps in the above method embodiment.
  • the functions described can be implemented by hardware, or can be implemented by software or hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • the structure of the device for deploying VNF is shown in Figure 10, including a communication unit 1001 and a processing unit 1002.
  • the device 1000 for deploying VNF can be applied to NFVO or VNFM in the architecture shown in Figure 1 or Figure 3, and can implement the methods provided by the above embodiments and examples of the present application.
  • the functions of each unit in the device 1000 for deploying VNF are introduced below.
  • the communication unit 1001 is used to receive and send data.
  • the communication unit 1001 can be implemented through a physical interface, a communication module, a communication interface, and an input and output interface.
  • the device 1000 for deploying VNF can connect to a network cable or cable through the communication unit 1001, and then establish a physical connection with other devices.
  • the processing unit 1002 may be configured to support the device 1000 for deploying VNF in performing the processing actions in the above method embodiment.
  • the processing unit 1002 may be implemented by a processor.
  • the processor can be a central processing unit (CPU), or other general-purpose processor, digital signal processor (DSP), application specific integrated circuit (ASIC) , field programmable gate array (FPGA) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • a general-purpose processor can be a microprocessor or any conventional processor.
  • the device 1000 for deploying VNF is applied to the NFVO in the embodiment of the present application shown in any one of Figures 6 to 9.
  • the specific functions of the processing unit 1002 in this embodiment will be introduced below.
  • the processing unit 1002 is configured to: obtain first information, which is used to indicate the requirements for cluster resources of the VNF to be deployed; and obtain a connection to the CISM used to manage the first cluster according to the first information. information, the first cluster meets the VNF's requirements for cluster resources; the first message is sent to the VNFM through the communication unit 1001, the first message contains the connection information of the CISM, and the first message is used to Triggering the VNFM to deploy the VNF on the first cluster managed by the CISM.
  • the processing unit 1002 is specifically configured to: obtain the first information in the VNFD; and/or receive the first information from the VNFM through the communication unit 1001.
  • the processing unit 1002 is specifically configured to obtain the first information in the VNF node information contained in the VNFD.
  • the VNFD further includes: at least one manageable container base object package MCIOP, and information indicating the order of the at least one MCIOP.
  • the processing unit 1002 is specifically configured to: when the first information indicates the VNF exclusive cluster, send a second message to the CCM through the communication unit 1001, where the second message is used to request the VNF exclusive cluster.
  • the CCM creates the first cluster that meets the requirements for the VNF; and receives connection information from the CCM for managing the CISM of the first cluster through the communication unit 1001.
  • the processing unit 1002 is specifically configured to: when the first information indicates that the VNF can share a cluster, select the first cluster that meets the requirement for the VNF according to the first information. ; Obtain connection information of the CISM used to manage the first cluster.
  • the processing unit 1002 is specifically configured to: before sending the first message to the VNFM, select the VNFM that supports the MCIOP type according to the MCIOP type of the VNF.
  • the MCIOP type is included in the Vnfminfo parameter.
  • the processing unit 1002 is specifically configured to: after acquiring the connection information of the CISM used to manage the first cluster, send to the VNFM through the communication unit 1001 a message indicating authorization in the first cluster. Deploy the VNF information.
  • the VNF's requirements for cluster resources include: the number of resource nodes in the cluster where the VNF is deployed, and the resource size of each resource node in the cluster where the VNF is deployed.
  • the VNF's requirements for cluster resources also include at least one of the following: the type of cluster in which the VNF is deployed, the specifications of the cluster in which the VNF is deployed, and whether the VNF shares a cluster.
  • the device 1000 for deploying VNF is applied to the VNFM in the embodiment of the present application shown in any one of Figures 6 to 9.
  • the specific functions of the processing unit 1002 in this embodiment will be introduced below.
  • the processing unit 1002 is configured to: receive a first message from the NFVO through the communication unit 1001, where the first message contains connection information for managing the CISM of the first cluster, and the first cluster meets the requirements to be deployed. VNF's requirements for cluster resources; according to the connection information of the CISM, send a third message to the CISM through the communication unit 1001, the third message is used to request the CISM to deploy all the resources on the first cluster. Describe VNF.
  • the processing unit 1002 is specifically configured to: before receiving the first message from the NFVO, obtain the first information in the VNFD, where the first information is used to indicate the VNF's requirements for cluster resources; through the The communication unit 1001 sends the first information to the NFVO.
  • the processing unit 1002 is specifically configured to obtain the first information in the VNF node information contained in the VNFD.
  • the processing unit 1002 is specifically configured to: obtain at least one manageable container basic object package MCIOP in the VNFD, and information used to indicate the order of the at least one MCIOP; according to the method used to indicate the Information on the order of at least one MCIOP, deploying the at least one MCIOP.
  • the processing unit 1002 is specifically configured to: before sending the third message to the CISM, receive through the communication unit 1001 a message from the NFVO indicating authorization to deploy the VNF in the first cluster. information.
  • the VNF's requirements for cluster resources include: the number of resource nodes in the cluster where the VNF is deployed, and the resource size of each resource node in the cluster where the VNF is deployed.
  • the VNF's requirements for cluster resources also include at least one of the following: the type of cluster in which the VNF is deployed, the specifications of the cluster in which the VNF is deployed, and whether the VNF shares a cluster.
  • each function in each embodiment of the present application can be integrated into one processing unit, or they can exist physically alone, or two or more units can be integrated into one unit.
  • the above integrated units can be implemented in the form of hardware or software functional units.
  • the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it may be stored in a computer-readable storage medium.
  • the technical solution of the present application is essentially or contributes to the existing technology, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium , including a number of instructions for causing a computer device to (It can be a personal computer, a server, or a network device, etc.) or a processor (processor) to execute all or part of the steps of the methods described in various embodiments of this application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk and other media that can store program code. .
  • the embodiment of the present application provides a device for deploying VNF as shown in Figure 11, which can be used to perform relevant steps in the above method embodiment.
  • the device for deploying VNF can be applied to NFVO or VNFM in the architecture shown in Figure 1 or Figure 3, can implement the methods provided in the above embodiments and examples of this application, and has the function of the device for deploying VNF shown in Figure 10.
  • the device 1100 for deploying VNF includes: a communication module 1101 , a processor 1102 and a memory 1103 .
  • the communication module 1101, the processor 1102 and the memory 1103 are connected to each other.
  • the communication module 1101, the processor 1102 and the memory 1103 are connected to each other through a bus 1104.
  • the bus 1104 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc.
  • PCI peripheral component interconnect
  • EISA extended industry standard architecture
  • the bus can be divided into address bus, data bus, control bus, etc. For ease of presentation, only one thick line is used in Figure 11, but it does not mean that there is only one bus or one type of bus.
  • the communication module 1101 is used to receive and send data to implement communication interaction with other devices.
  • the communication module 1101 can be implemented through a physical interface, a communication module, a communication interface, and an input and output interface.
  • the processor 1102 may be configured to support the device 1100 deploying the VNF to perform the processing actions in the above method embodiment. When the device 1100 for deploying VNF is used to implement the above method embodiment, the processor 1102 may also be used to implement the function of the above processing unit 1002.
  • the processor 1102 may be a CPU, or other general-purpose processor, DSP, ASIC, FPGA or other programmable logic device, transistor logic device, hardware component or any combination thereof.
  • a general-purpose processor can be a microprocessor or any conventional processor.
  • the device 1100 for deploying VNF is applied to the NFVO in the embodiment of the present application shown in any one of Figures 6 to 9.
  • the processor 1102 is specifically used to:
  • the first information is used to indicate the requirements of the VNF for cluster resources; according to the first information, obtain the connection information of the CISM used to manage the first cluster, the first cluster satisfies the VNF's requirements for cluster resources; send a first message to VNFM through the communication module 1101, the first message contains the connection information of the CISM, and the first message is used to trigger the VNFM to perform the operation of the VNFM under the management of the CISM.
  • the VNF is deployed on the first cluster.
  • the device 1100 for deploying VNF is applied to the VNFM in the embodiment of the present application shown in any one of Figures 6 to 9.
  • the processor 1102 is specifically used to:
  • the first message from the NFVO is received through the communication module 1101.
  • the first message contains the connection information of the CISM used to manage the first cluster.
  • the first cluster meets the VNF's requirements for cluster resources; according to the CISM connection information, and sends a third message to the CISM through the communication module 1101.
  • the third message is used to request the CISM to deploy the VNF on the first cluster.
  • processor 1102 For the specific functions of the processor 1102, please refer to the description in the above embodiments of the present application and the methods provided by the examples, as well as the specific functional description of the device 1000 for deploying VNF in the embodiment of the present application shown in Figure 10, which is not mentioned here. Again.
  • the memory 1103 is used to store program instructions and data.
  • program instructions may include program code
  • the program code includes computer operating instructions.
  • the memory 1103 may include RAM, and may also include non-volatile memory (non-volatile memory), such as at least one disk memory.
  • the processor 1102 executes the program instructions stored in the memory 1103, and uses the data stored in the memory 1103 to implement the above functions, thereby implementing the above method provided by the embodiment of the present application.
  • the memory 1103 in Figure 11 of this application can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories.
  • the non-volatile memory can be ROM, programmable ROM (PROM), erasable programmable read-only memory (Erasable PROM, EPROM), electrically erasable programmable read-only memory (Electrically EPROM) ,EEPROM) or flash memory.
  • Volatile memory can be RAM, which acts as an external cache.
  • RAM static random access memory
  • DRAM dynamic random access memory
  • DRAM synchronous dynamic random access memory
  • SDRAM double data rate synchronous dynamic random access memory
  • Double Data Rate SDRAM DDR SDRAM
  • enhanced SDRAM ESDRAM
  • Synchlink DRAM SLDRAM
  • Direct Rambus RAM Direct Rambus RAM
  • embodiments of the present application also provide a computer program, which when the computer program is run on a computer, causes the computer to execute the method provided in the above embodiments.
  • embodiments of the present application also provide a computer-readable storage medium.
  • the computer-readable storage medium stores a computer program.
  • the computer program When the computer program is executed by a computer, it causes the computer to execute the method provided in the above embodiments. .
  • the storage medium may be any available medium that can be accessed by the computer. Taking this as an example but not limited to: computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage media or other magnetic storage devices, or can be used to carry or store instructions or data structures. Any other medium that contains the desired program code and is capable of being accessed by a computer.
  • embodiments of the present application also provide a chip, which is used to read the computer program stored in the memory and implement the method provided in the above embodiments.
  • the chip system includes a processor and is used to support the computer device to implement the functions involved in each device in the above embodiments.
  • the chip system further includes a memory, and the memory is used to store necessary programs and data of the computer device.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • embodiments of the present application provide a method, device and equipment for deploying VNF.
  • the NFVO can obtain the CISM for managing the first cluster based on the first information.
  • the connection information wherein, the first information can be used to indicate the requirements of the VNF to be deployed for cluster resources, and the first cluster can meet the VNF's requirements for cluster resources.
  • the NFVO may send the first message containing the connection information to the VNFM.
  • the VNFM may request the CISM to deploy the VNF on the first cluster. Since the container is deployed on the cluster, the first cluster can meet the VNF's requirements for the cluster and must also be able to meet the requirements for container deployment. Therefore, deploying VNF through this method can increase the probability of successful VNF deployment.
  • embodiments of the present application may be provided as methods, systems, or computer program products. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment that combines software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.
  • computer-usable storage media including, but not limited to, disk storage, CD-ROM, optical storage, etc.
  • These computer program instructions may also be stored in a computer-readable memory that causes a computer or other programmable data processing apparatus to operate in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction means, the instructions
  • the device implements the functions specified in a process or processes of the flowchart and/or a block or blocks of the block diagram.
  • These computer program instructions may also be loaded onto a computer or other programmable data processing device, causing a series of operating steps to be performed on the computer or other programmable device to produce computer-implemented processing, thereby executing on the computer or other programmable device.
  • Instructions provide steps for implementing the functions specified in a process or processes of a flowchart diagram and/or a block or blocks of a block diagram.

Landscapes

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

Abstract

本申请公开了一种部署VNF的方法、装置及设备，用于提高VNF部署成功的可能性。该方法为：NFVO在获取第一信息之后，可根据第一信息，获取用于管理第一集群的CISM的连接信息；其中，第一信息可用于指示待部署的VNF对集群资源的要求，第一集群可满足VNF对集群资源的要求。然后，NFVO可向VNFM发送包含该连接信息的第一消息，VNFM在获取该连接信息后，可请求该CISM在第一集群上部署该VNF。由于容器是部署在集群上的，第一集群能够满足VNF对集群的要求，也必然能够满足容器部署的要求。因此，通过该方法部署VNF，可提高VNF部署成功的可能性。

Description

一种部署VNF的方法、装置及设备
相关申请的交叉引用
本申请要求在2022年03月25日提交中国专利局、申请号为202210305866.8、申请名称为“一种部署VNF的方法、装置及设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及网络功能虚拟化(network function virtualization，NFV)技术领域，尤其涉及一种部署虚拟化网络功能(virtual network function，VNF)的方法、装置及设备。
背景技术
NFV指通过使用通用的硬件设备及虚拟化技术，来承载传统网络中专用设备的功能，从而降低部署专用设备带来的昂贵成本。通过软硬件解耦(即软件不与专有硬件绑定)，可使网络设备功能不再依赖于专用硬件。同时利用云计算的特点，使资源可以充分灵活共享，实现新业务的快速开发和部署，并基于实际业务需求进行自动部署、弹性伸缩、故障隔离和自愈等。
目前，当VNF以容器形式部署时，容器部署所需的资源信息和容器管理平台所管理的部署包所定义的容器资源可能并不一致。当容器管理平台管理的部署包所定义的容器资源大于容器部署所需的资源信息时，根据容器部署所需的资源信息选择的资源可能小于容器管理平台管理的部署包所定义的容器资源，从而不能创建容器资源，导致部署失败。
例如，当容器管理平台所管理的部署包为可管理的容器基础对象包(managed container infrastructure object packages，MCIOP)(也可称为MCIOP部署包)时，NFV编排器(NFV orchestrator，NFVO)根据容器部署所需的资源信息来选择容器基础设施管理器(container infrastructure service management，CISM)。在实际部署时，VNF管理器(VNF manager，VNFM)根据MCIOP来请求选择的CISM创建容器资源，从而部署VNF。但是，容器部署所需的资源信息和MCIOP所定义的容器资源并不一致。当MCIOP所定义的容器资源大于容器部署所需的资源信息时，选择的CISM所管理的资源可能小于MCIOP所定义的容器资源，从而不能创建容器资源，导致部署失败。
因此，需要一种优化的部署VNF的方法，提高VNF部署成功的可能性。
发明内容
有鉴于此，本申请提供了一种部署VNF的方法、装置及设备，用于提高VNF部署成功的可能性。
第一方面，本申请实施例提供了一种部署VNF的方法。该方法包括：NFVO在获取第一信息之后，可根据第一信息，获取用于管理第一集群的CISM的连接信息；其中，第一信息可用于指示待部署的VNF对集群资源的要求，第一集群可满足VNF对集群资源的要求。然后，NFVO可向VNFM发送包含该连接信息的第一消息，以触发VNFM在该CISM 管理的第一集群上部署VNF。
通过该方法，NFVO可根据VNF对集群资源的要求，获取管理满足该要求的第一集群的CISM的连接信息，并将该连接信息发送给VNFM；这样，VNFM在获取该连接信息后，可请求该CISM在第一集群上部署该VNF。由于容器是部署在集群上的，第一集群能够满足VNF对集群的要求，也必然能够满足容器部署的要求。因此，通过该方法部署VNF，可提高VNF部署成功的可能性。
在一种可能的设计中，NFVO可通过如下方式之一获取第一信息：
方式一：NFVO获取VNFD中的第一信息。例如，NFVO可通过解析VNFD来获取VNFD中的第一信息。
方式二：NFVO接收来自VNFM的第一信息。例如，VNFM可以从NFVO获取VNFD，在通过解析VNFD来获取VNFD中的第一信息之后，向NFVO发送该第一信息。
该设计提供了多种获取第一信息的方式；通过该设计，NFVO可方便的获取到第一信息。
在一种可能的设计中，NFVO可获取VNFD包含的VNF节点信息中的第一信息。在该设计中，VNF节点信息中可不包含容器资源信息(例如，下文图5所示的osContainerDesc)，而是包含用于指示VNF对集群资源的要求的第一信息，从而可避免VNFD中的容器资源信息和容器管理平台所管理的部署包的冲突，进而提高VNF部署成功的可能性。
在一种可能的设计中，VNFD还可包含：至少一个可管理的容器基础对象包MCIOP，以及用于指示至少一个MCIOP的顺序的信息。这样，VNFM可根据至少一个MCIOP的顺序，部署该至少一个MCIOP。
在一种可能的设计中，NFVO可通过以下方式之一获取用于管理第一集群的CISM的连接信息：
方式1：当第一信息指示VNF独占集群时，NFVO可向CCM发送第二消息，以请求CCM为VNF创建满足第一信息所指示的要求的第一集群；CCM在创建第一集群之后，可向NFVO发送用于管理第一集群的CISM的连接信息，相应的，NFVO可接收来自CCM的用于管理第一集群的CISM的连接信息。
通过该方式1，当VNF不共享集群时，NFVO可及时触发创建满足VNF对集群资源的要求的第一集群；这样，当在该第一集群上部署该VNF时，可提高VNF部署成功的可能性。
方式2：当第一信息指示VNF能够共享集群时，NFVO可根据第一信息，为VNF选择满足第一信息所指示的要求的第一集群，并获取用于管理第一集群的CISM的连接信息。
通过该方式2，当VNF能够共享集群时，NFVO可快速选择满足VNF对集群资源的要求的第一集群；这样，当在该第一集群上部署该VNF时，可提高VNF部署成功的可能性。
在一种可能的设计中，在向VNFM发送第一消息之前，NFVO还可根据VNF的MCIOP类型，选择支持MCIOP类型的VNFM。例如，该MCIOP类型包括：Helm；NFVO可选择能够解析该Helm的VNFM。
可选的，该MCIOP类型可包含在Vnfminfo参数中。
通过该设计，NFVO选择能够支持MCIOP类型的VNFM来部署VNF，从而可提高部署VNF成功的可能性。
在一种可能的设计中，在获取用于管理第一集群的CISM的连接信息之后，NFVO还可向VNFM发送用于指示授权在第一集群中部署VNF的信息。通过该设计，NFVO可以方便的指示VNFM已授权在第一集群中部署VNF。
在一种可能的设计中，VNF对集群资源的要求可包括：部署VNF的集群中资源节点的数量、部署VNF的集群中每个资源节点的资源大小。这样，NFVO可确定部署VNF所需的集群资源，从而有效确定用于部署该VNF的集群。
在一种可能的设计中，VNF对集群资源的要求还包括以下至少一项：部署VNF的集群的类型、部署VNF的集群的规格、VNF是否共享集群。通过该设计，可灵活设计VNF对集群资源的要求，NFVO可据此有效确定用于部署该VNF的集群。
第二方面，本申请实施例提供了一种部署VNF的方法。该方法包括：
VNFM在接收到来自NFVO的包含CISM的连接信息的第一消息之后，可根据CISM的连接信息，向CISM发送第三消息。其中，CISM管理满足待部署的VNF对集群资源的要求的第一集群；第三消息用于请求CISM在第一集群上部署VNF。
在该方法中，CISM管理满足VNF对集群资源的要求的第一集群，VNFM请求该CISM在第一集群上部署VNF。由于容器是部署在集群上的，第一集群能够满足VNF对集群的要求，也必然能够满足容器部署的要求。因此，通过该方法部署VNF，可提高VNF部署成功的可能性。
在一种可能的设计中，在接收来自NFVO的第一消息之前，VNFM可获取VNFD中的第一信息，并向NFVO发送第一信息；其中，第一信息可用于指示VNF对集群资源的要求。通过该设计，VNFM可向NFVO发送第一信息；这样，NFVO可根据第一信息获取管理满足该要求的第一集群的CISM的连接信息，并触发VNFM请求在该第一集群上部署VNF。由于容器是部署在集群上的，第一集群能够满足VNF对集群的要求，也必然能够满足容器部署的要求。因此，通过该方法部署VNF，可提高VNF部署成功的可能性。
在一种可能的设计中，VNFM可获取VNFD包含的VNF节点信息中的第一信息。在该设计中，VNF节点信息中可不包含容器资源信息(例如，下文图5所示的osContainerDesc)，而是包含用于指示VNF对集群资源的要求的第一信息，从而可避免VNFD中的容器资源信息和容器管理平台所管理的部署包的冲突，进而提高VNF部署成功的可能性。
在一种可能的设计中，上述方法还包括：VNFM在获取VNFD中的至少一个可管理的容器基础对象包MCIOP，以及用于指示至少一个MCIOP的顺序的信息之后，可根据用于指示至少一个MCIOP的顺序的信息，部署至少一个MCIOP。通过该设计，VNFM可按照该顺序有效部署至少一个MCIOP。
在一种可能的设计中，在向CISM发送第三消息之前，VNFM可接收来自NFVO的用于指示授权在第一集群中部署VNF的信息。通过该设计，VNFM可获知已得到在第一集群中部署VNF的授权。
在一种可能的设计中，VNF对集群资源的要求可包括：部署VNF的集群中资源节点的数量、部署VNF的集群中每个资源节点的资源大小。通过该设计，可准确指示部署VNF所需的集群资源。
在一种可能的设计中，VNF对集群资源的要求还可包括以下至少一项：部署VNF的集群的类型、部署VNF的集群的规格、VNF是否共享集群。通过该设计，可灵活设计VNF 对集群资源的要求。
第三方面，本申请实施例提供了一种部署VNF的装置，包括用于执行以上任一方面中各个步骤的单元。
第四方面，本申请实施例提供了一种部署VNF的设备，包括至少一个处理器和至少一个存储器，其中该至少一个存储器用于存储程序和数据，该至少一个处理器用于读取并执行存储器中存储的程序和数据，以使得本申请以上任一方面提供的方法被实现。
第五方面，本申请实施例提供了一种部署VNF的系统，包括：用于执行第一方面提供的方法的NFVO，用于执行第二方面提供的方法的VNFM。
第六方面，本申请实施例还提供了一种计算机程序，当所述计算机程序在计算机上运行时，使得所述计算机执行上述任一方面提供的方法。
第七方面，本申请实施例还提供了一种计算机可读存储介质，所述计算机可读存储介质中存储有计算机程序，当所述计算机程序被计算机执行时，使得所述计算机执行上述任一方面提供的方法。
第八方面，本申请实施例还提供了一种芯片，所述芯片用于读取存储器中存储的计算机程序，执行上述任一方面提供的方法。
第九方面，本申请实施例还提供了一种芯片系统，该芯片系统包括处理器，用于支持计算机装置实现上述任一方面提供的方法。在一种可能的设计中，所述芯片系统还包括存储器，所述存储器用于保存该计算机装置必要的程序和数据。该芯片系统可以由芯片构成，也可以包含芯片和其他分立器件。
上述第三方面至第九方面中任一方面可以达到的技术效果可以参照上述第一方面或第二方面中任一方面中任一种可能设计可以达到的技术效果说明，重复之处不予论述。
附图说明
图1为本申请实施例提供的一种NFV架构示意图；
图2为本申请实施例提供的一种K8S与Helm的连接示意图；
图3为本申请实施例提供的另一种NFV架构示意图；
图4为一种部署VNF方法的流程图；
图5为图4所示方法中的VNFD的示意图；
图6为本申请实施例提供的一种部署VNF的方法的流程图；
图7为本申请实施例提供的另一种部署VNF的方法的流程图；
图8为图7所示方法中的一种可能的VNFD的示意图；
图9为本申请实施例提供的又一种部署VNF的方法的流程图；
图10为本申请实施例提供的一种部署VNF的装置的结构图；
图11为本申请实施例提供的一种部署VNF的设备的结构图。
具体实施方式
本申请提供一种部署VNF的方法、装置及设备，用于提高VNF部署成功的可能性。其中，方法、装置和设备是基于同一技术构思的，由于解决问题的原理相似，因此装置、 设备与方法的实施可以相互参见，重复之处不再赘述。
通过本申请实施例提供的方案，NFVO在获取第一信息之后，可根据第一信息，获取用于管理第一集群的CISM的连接信息；其中，第一信息可用于指示所述VNF对集群资源的要求，第一集群可满足VNF对集群资源的要求。然后，NFVO可向VNFM发送包含该连接信息的第一消息，VNFM在获取该连接信息后，可请求该CISM在第一集群上部署该VNF。由于容器是部署在集群上的，第一集群能够满足VNF对集群的要求，也必然能够满足容器部署的要求。因此，通过该方法部署VNF，可提高VNF部署成功的可能性。
以下，对本申请实施例中的部分用语进行解释说明，以便于本领域技术人员理解。
1、网元，可以为网络中的一个物理设备，或者为集成了多个物理设备的功能的装置。本申请实施例所述的网元还可以是逻辑概念，例如为物理设备中的软件模块，或者为与各个网络设备提供的服务对应的网络功能，网络功能可以理解为采用虚拟化技术实现的虚拟化功能等。
2、网络服务(network service，NS)部署模板，也可称为网络服务描述模板(network service descriptor，NSD)，可用于提供NS的描述信息。
其中，NS可以但不限于为一个互联网协议(internet protocol)多媒体子系统(IP multimedia subsystem，IMS)网络业务，或一个第五代(the 5th generation，5G)核心网网络。
一个NS中可包含一个或多个VNF。因此，NSD可包含该NS的拓扑结构信息以及该NS包含的每个VNF的虚拟化网络功能描述模板(virtualization network functions descriptor，VNFD)。其中，拓扑结构信息中可包含虚拟化连接信息(例如，网络服务虚拟化连接模板(network service virtual link descriptor，NsVld))，该虚拟化连接信息可用于描述VNF之间的连接，例如，描述连接类型、带宽等信息。VNFD的内容可参考下面名词解释中对VNFD的说明，此处暂不展开。
在实际部署时，该NSD可由业务请求方提供给业务提供方。其中，业务请求方可为发起虚拟化请求的网元；业务提供方可为能够接收该虚拟化请求，并根据该虚拟化请求对相应业务进行虚拟化处理的网元。
3、虚拟部署单元(virtualization deployment unit，VDU)，可为用于描述部署VNF的单元。
当采用虚拟机(virtual machine，VM)技术部署VNF时，一个VDU可代表一个虚拟机。其中，虚拟机是指通过软件模拟的具有完整硬件系统功能的、运行在一个完全隔离环境中的完整计算机系统。一般情况下，一台物理主机(例如，电脑)上可以安装多个虚拟机，这些虚拟机可共享物理主机资源。
当采用容器化技术部署VNF时，一个VDU可代表一组容器；组内容器具有相同的资源需求，并且可共用相同的网络信息。采用容器化技术时，每个容器可部署在虚拟机上，也可以部署在物理机(在本申请中，也可称为裸金属(bare metal))中。
4、VNFD，又可以称为VNF的部署模板，可用于提供VNF的描述信息。VNFD可包括VDU、连接点模板(connection point descriptor，CPD)和虚拟连接模板(virtual link descriptor，VLD)等。下面对VNFD包括的信息进行具体说明。
VDU：当一个VDU代表一个虚拟机时，该VDU可包括该虚拟机的资源需求描述信息，例如，创建该虚拟机所需的资源类型以及每种资源类型的资源数量等。当一个VDU 代表一组容器时，该VDU可包括这一组容器的资源需求描述信息(也可以称为容器资源信息)，用于表示部署这组容器所需的资源信息。
CPD：可包括该VNF中每种类型外部连接点的类型信息和资源参数。其中，外部连接点可用于VNF与外部节点之间的通信。外部连接点的类型信息可用于指示外部连接点的类型。其中，外部连接点可以分为虚拟连接点(virtual connection point，virtual Cp)这一大类型(type)。虚拟连接点可以通过服务实现，服务包括节点端口、负载均衡器和外部名称等类型。外部连接点的资源参数可用于指示创建该类型的外部连接点所需的资源。例如，外部连接点的资源参数可包括外部连接点的地址表示形式(例如，以IP地址表示地址)。可选的，外部连接点的资源参数还包括外部连接点支持的功能的类型。
VLD：可描述VDU之间的虚拟网络连接需求，例如连接类型和/或带宽等信息。
5、容器技术，是通过虚拟化技术来隔离运行在主机上的不同进程，从而达到进程之间、进程和宿主操作系统之间相互隔离、互不影响的技术。这种相互隔离的进程即为容器，每个容器有自己的一套文件系统资源和从属进程。
本申请实施例中，对于名词的数目，除非特别说明，表示“单数名词或复数名词”，即“一个或多个”。“至少一个”是指一个或者多个，“多个”是指两个或两个以上。“和/或”描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。字符“/”一般表示前后关联对象是一种“或”的关系。例如，A/B，表示：A或B。“以下至少一项(个)”或其类似表达，是指这些项(个)中的任意组合，包括单项(个)或复数项(个)的任意组合。
另外，需要理解的是，在本申请的描述中，“第一”、“第二”等词汇，仅用于区分描述的目的，而不应理解为指示或暗示相对重要性，也不应理解为指示或暗示顺序。
参见图1，为本申请实施例提供的一种NFV架构示意图。该NFV架构可以实现多种网络，例如局域网(local area network，LAN)、IP网络或者演进分组核心网(evolved packet core，EPC)网络。如图1所示，该NFV架构可以包括NFV管理和编制系统(NFV management and orchestration system，NFV-MANO)110，NFV基础设施(NFV infrastructure，NFVI)150，多个VNF140，多个设备管理(element management，EM)130，以及一个或多个运营支撑系统/业务支撑系统(operation support system/business support system，OSS/BSS)120。其中，NFV-MANO 110可以包括NFVO111，一个或多个VNFM112，一个或多个虚拟基础设施管理器(virtualized infrastructure manager，VIM)113，以及一个或多个容器基础设施管理器(container infrastructure service management，CISM)114。
下面分别对NFV架构中所包括的各个部分进行介绍。
(1)NFVO111：主要负责处理虚拟化业务的生命周期管理，以及虚拟基础设施及NFVI中虚拟资源的分配和调度等。NFVO111可以与一个或多个VNFM112通信，以执行资源相关请求，发送配置信息给VNFM112，收集VNF140的状态信息。另外，NFVO111也可与VIM113通信，以执行资源分配和/或预留、交换虚拟化硬件资源配置和状态信息。
(2)VNFM112：主要负责一个或多个VNF的生命周期管理，例如，部署或者说实例化(instantiating)VNF140、更新(updating)VNF140、查询VNF140、弹性伸缩(scaling)VNF140、终止(terminating)VNF140。VNFM112可以与VNF140通信，以完成VNF生命周期管理及交换配置和状态信息。在NFV架构中VNFM可以有多个，负责对不同类型 的VNF进行生命周期管理。
(3)VIM113：主要负责控制和管理VNF140与计算硬件1521、存储硬件1522、网络硬件1523、虚拟计算1511(例如VM)、虚拟存储1512和虚拟网络1513的交互。VIM113还可执行资源管理功能，包括管理基础设施资源、分配资源(例如，为容器增加虚拟资源)及运行功能(例如，收集NFVI故障信息)。VIM113可与VNFM112通信，例如，基于VNFM112的请求分配资源，与VNFM112交互虚拟化硬件资源配置和状态信息。
(4)CISM114：为NFV架构中的容器管理平台，主要负责容器资源的管理，包括容器的创建、更新(updating)、查询、弹性伸缩(scaling)和终止(terminating)等。当VNF以容器形式部署时，CISM114可基于VNFM112的请求创建容器资源。
CISM114可为业界通用的容器管理平台，例如，kubernetes(下面简称为K8S)。K8S是目前应用最广的容器管理平台。一个K8S可管理一个集群，集群内可包含一个或多个物理机资源、虚拟机资源。如果K8S管理的是物理机资源，则K8S可将创建的容器部署在物理机上；或者，如果K8S管理的是虚拟机资源，则K8S可将创建的容器部署在虚拟机上。K8S以豆荚(pod)为最小单元在所管理的集群内创建容器，一个豆荚可包括一个或者多个容器。
Helm是K8S的包管理器，主要负责管理用于部署应用的部署包(也称为Helm Chart)，Helm Chart中可封装K8S原生应用程序的一系列仍是一种置标语言(yet another markup language，YAML)文件。Helm可以包含在K8S中，也可以是独立的包管理工具。如图2所示，当Helm为独立的包管理工具时，Helm可通过调用K8S的原生应用程序编程接口(application programming interface，API)与K8S进行通信。目前，管理和编制系统(management and orchestration system，MANO)架构中的CISM里可以同时包含Helm和K8S。
(5)NFVI150：为NFV的基础设施层，用于建立虚拟化环境，部署、管理及实现VNF140。NFVI150可以包括硬件资源层和/或虚拟资源层(也可称为软件资源层)。另外，NFVI150还可包含虚拟化层。
硬件资源层可以包括计算硬件1521、存储硬件1522、网络硬件1523。硬件资源层中的计算硬件1521可以为专用的处理器或通用的用于提供处理和计算功能的处理器，如中央处理器(central process unit，CPU)；存储硬件1522用于提供存储能力，存储硬件1522例如为磁盘或网络附属存储(network attached storage，NAS)；网络硬件1523可以是交换机、路由器和/或其他网络设备。在一种可选的方式中，计算硬件1521和存储硬件1522的资源可以集中在一起。
NFVI150中的虚拟化层可用于抽象硬件资源层的硬件资源，将VNF140和硬件资源所属的物理层解耦，向VNF140提供虚拟化环境，例如，虚拟机或其他形式的虚拟容器。
虚拟资源层可以包括虚拟计算1511、虚拟存储1512和虚拟网络1513。虚拟计算1511、虚拟存储1512可以以虚拟机或其他虚拟容器的形式向VNF140提供虚拟资源，例如一个或多个虚拟机组成一个VNF140。虚拟化层通过抽象网络硬件1523形成虚拟网络1513。虚拟网络1513可用于实现多个虚拟机之间，或多个承载VNF的其他类型的虚拟容器之间的通信。
(6)EM130：是传统电信系统中用于对设备进行配置、管理的系统；在NFV架构中，EM130也可以用于对VNF进行配置和管理，以及向VNFM112发起新的VNF的部署或者 实例化等生命周期管理操作。
(7)OSS/BSS120：支持各种端到端的电信业务。例如，OSS支持的管理功能包括：网络配置、业务提供、故障管理等；BSS处理订单、付费、收入等，支持产品管理、订单管理、收益管理及客户管理。
(8)VNF140：对应于传统非虚拟化网络中的物理网络功能(physical network function，PNF)。例如，虚拟化的分组核心网(evolved packet core，EPC)节点可对应以下至少一项：移动性管理实体(mobility management entity，MME)、服务网关(serving gateway，SGW)、公用数据网网关(public data network gateway，PGW)等。网络功能的功能性行为和状态与虚拟化与否无关，NFV技术需求希望VNF和PNF拥有相同的功能性行为和外部接口。
VNF140可以采用虚拟机技术或容器化技术实现。如果VNF140采用虚拟机技术实现，该VNF包括的VNF组件(VNF component，VNFC)可以部署在一个或多个虚拟机上。如果VNF140采用容器技术实现，该VNF包括的VNFC可以部署在一个或多个容器上。
请参考图3，为本申请实施例适用的另一种NFV架构的示意图，或者可以理解为另一种引入了容器管理平台的NFV架构的示意图。与图1不同的是，图3所示的NFV架构中还包括容器集群管理器(container identification system cluster manager，CCM)115。CCM115可以分别与NFVO111和CISM114进行通信。CCM115可以与NFVO111配合实现对CISM114进行管理。图3中除了CCM之外的其他网元的功能可以参照图1所述的内容，此处不再赘述。
应理解，图1和图3介绍的各个网元(如NFVO、VNFM、CISM、CCM等)仅为示例而非限定，在标准演进的过程中，上述各网元的名称可以发生变化，各网元执行的功能可以被进一步地拆分或组合，本申请实施例不做限制。
图4示出了一种部署VNF的方法。该方法可用于图1或图3所示的NFV架构中。如图4所示，该方法可以包括：
S401：NFVO向VNFM发送实例化请求，以请求部署或实例化VNF。
其中，该实例化请求可包括该VNF的标识。
部署或实例化VNF可以理解为：为VNF分配或创建实现相应功能所需的资源(例如，为该VNF创建虚拟机或容器)，并在创建的虚拟机或容器上部署该VNF包括的VNFC。
S402：VNFM向NFVO发送请求获取VNFD的请求(下面简称为VNFD请求)。
其中，VNFM可在接收到实例化请求之后，可获取与该VNF的标识对应的VNFD的标识，并向NFVO发送包含该VNFD的标识的VNFD请求。
S403：NFVO向VNFM发送VNFD。
可选的，NFVO可在获取该VNFD的标识所对应的VNFD之后，向VNFM发送VNFD。
其中，该VNFD可包含：容器资源信息和容器管理平台部署模板所引用的MCIOP。其中，容器资源信息可为操作系统容器描述模板(osContainerDesc)；每个osContainerDesc可对应一个容器，主要表示部署容器所需的资源信息。例如，该osContainerDesc可包括以下至少一项：部署VNF对应的容器所需的最大CPU资源、最小CPU资源、最大内存资源、最小内存资源、容器镜像等。MCIOP例如可以为K8S使用的helm chart部署包。
图5示出了该VNFD一种可能的实现方式。如图5所示，VNFD可以包含：一个或多个VDU(例如，图5中的VDU1和VDU2)、一个或多个MCIOP、VNF节点信息。其中， 每个VDU可对应K8S的一个Pod，并包含一个或多个osContainerDesc。一个MCIOP可以对应一个或多个VDU。VNF节点信息可包含VNFD的基础信息，例如，标识(identity，ID)，名称(name)，版本(version)等信息。
S404：VNFM对VNFD进行解析，得到容器资源信息。
具体的，VNFM可解析VNFD中作为容器资源信息的osContainerDesc。示例性的，一个osContainerDesc可能包含如下信息：
其中，requested_cpu_resources和cpu_resource_limit分别指示部署VNF对应的一个容器所需的最小CPU资源和最大CPU资源，requested_memory_resources和memory_resource_limit分别指示部署该容器所需的最小内存资源和最大内存资源，sw_image为部署该容器所需的镜像信息。
S405：VNFM向NFVO发送资源授权请求，以请求获得针对容器资源信息所指示的资源的授权。
其中，资源授权请求中可包含：VNF所对应的一个或多个容器资源信息，或者VNF所对应的一个或多个容器资源信息所指示的总资源。这样，当VNFD包含多个osContainerDesc时，对于每个osContainerDesc所描述的资源信息，VNFM都会请求NFVO进行授权。
S406：NFVO向VNFM发送资源授权响应，以指示授权成功。该资源授权响应也可以称为授权成功响应。
其中，NFVO可在判断CISM满足创建VMF对应的容器的需求之后，向VNFM发送资源授权响应。NFVO可根据CISM当前管理的剩余资源以及VNF所对应的一个或多个容器资源信息所指示的总资源，判断CISM是否满足创建VMF对应的容器的需求。例如，当CISM当前管理的剩余资源大于或等于VNF所对应的一个或多个容器资源信息所指示的总资源时，NFVO判断CISM满足创建VMF对应的容器的需求；否则，NFVO判断CISM不满足创建VMF对应的容器的需求。
另外，该资源授权响应中可包含该CISM的连接信息(例如，该CISM的地址信息或 该CISM的接口信息)。
S407：VNFM根据CISM的连接信息，向CISM发送容器资源创建请求。
其中，该容器资源创建请求包含VNFD中的MCIOP。示例性的，当该MCIOP基于helm chart时，该MCIOP可包含：
可选的，上述示例中，部分取值可引用Helm Chart中包含的values.yaml文件，该文件可以包含：
其中，limits中的cpu可指示MCIOP所需的最大CPU资源，limits中的memory可指示MCIOP所需的最大内存资源，requests中的cpu可指示MCIOP所需的最小CPU资源，requests中的memory可指示MCIOP所需的最小内存资源，image中描述了MCIOP所需的部署容器所需的镜像信息。
S408：CISM使用MCIOP来创建容器资源。
在该方法中，NFVO根据osContainerDesc指示的资源信息来选择CISM，换句话说，NFVO根据osContainerDesc指示的资源信息对请求的容器资源进行授权。在实际部署时，CISM根据MCIOP来创建容器资源。osContainerDesc指示的资源信息和MCIOP所定义的容器资源可能并不一致。例如，可能存在MCIOP所定义的容器资源大于所有osContainerDesc指示的资源之和的情况；此时，选择的CISM所管理的剩余资源可能小于MCIOP所定义的容器资源，即不能满足MCIOP的资源需求，从而不能创建容器资源，导致部署失败。
另外，图4所示方法是以容器管理平台管理的部署包为MCIOP为例进行说明的。在实际部署时，VNFM也可能通过其他容器管理平台管理的部署包来请求创建容器资源。当容器部署所需的资源信息和其他容器管理平台管理的部署包所定义的容器资源不一致时，根据容器部署所需的资源信息选择的资源也可能小于其他容器管理平台管理的部署包所定义的容器资源，从而不能创建容器资源，导致部署失败。
下面结合附图对本申请提供的方案进行说明。
本申请实施例提供了一种部署VNF的方法，该方法可应用于图1或图3所示的架构中。下面参阅图6所示的流程图，对该方法的流程进行具体说明。
S601：NFVO获取第一信息。其中，第一信息可用于指示VNF对集群资源的要求。
可以理解的是，VNF对集群资源的要求可以理解为待部署的VNF或者待实例化的VNF对集群资源的要求，即用于部署或者用于实例化该VNF的集群资源需要满足的要求。
其中，VNF对集群资源的要求可包括：
1、部署VNF的集群中资源节点的数量：其中，该数量可为部署VNF的集群所需的资源节点的最少数量，也可为部署VNF的集群所需的资源节点的数量区间。
2、部署VNF的集群中每个资源节点的资源大小：例如，部署VNF的集群中每个资源节点的最大CPU资源、部署VNF的集群中每个资源节点的最小CPU资源、部署VNF的集群中每个资源节点的最大内存资源、部署VNF的集群中每个资源节点的最小内存资源中的至少一项。
可选的，VNF对集群资源的要求还可以但不限于包括以下至少一项：
3、部署VNF的集群的类型：例如，该类型可为虚拟机或物理机。
4、VNF是否共享集群：可用于表示该VNF是否能够和其他VNF共享集群，换句话说，可用于表示该VNF是否能够独占集群。
5、部署VNF的集群的规格：例如，虚拟机规格或者物理机规格，比如，CPU，内存，存储等规格，或操作系统(operating system，OS)版本等。
可选的，第一信息可通过如下方式指示VNF对集群资源的要求。
1、部署VNF的集群中资源节点的数量可通过第一信息的第一字段指示。其中，第一字段的取值可直接为部署VNF的集群中资源节点的数量；例如，第一字段的取值为6，表示部署VNF的集群中资源节点的数量为6。第一字段也可间接指示部署VNF的集群中资源节点的数量；例如，第一字段的取值为第一值时，表示部署VNF的集群中资源节点的数量为6。
2、部署VNF的集群中每个资源节点可通过第一信息的第二字段指示。其中，第二字段的取值可直接为部署VNF的集群中每个资源节点的资源大小；例如，第二字段为部署 VNF的集群中第一资源节点的最小内存资源对应的字段，当第二字段的取值为4GB时，表示部署VNF的集群中第一资源节点的最小内存资源为4GB。
3、部署VNF的集群的类型可通过第一信息中的第三字段指示。其中，第三字段的取值可直接为部署VNF的集群的类型；例如，第三字段的取值为虚拟机或物理机。第三字段也可以间接指示部署VNF的集群的类型；例如，第三字段的取值为第二值时，表示部署VNF的集群的类型为虚拟机，又例如，第三字段的取值为第三值时，表示部署VNF的集群的类型为物理机。4、VNF是否共享集群可通过第一信息的第四字段指示。例如，当第四字段的取值为第四值(例如，真(ture))时，表示VNF可与其他VNF共享集群；当第四字段的取值为第五值(例如，假(false))时，表示该VNF不能与其他VNF共享集群。
5、部署VNF的集群的规格可通过第一信息的第五字段指示。第五字段的取值可直接为部署VNF的集群的规格；例如，第五字段为部署VNF的集群所使用的内存的规格对应的字段，当第五字段的取值为1GB时，表示部署VNF的集群所使用的内存的规格为1GB。
S602：NFVO根据第一信息，获取用于管理第一集群的CISM的连接信息。其中，第一集群可满足VNF对集群资源的要求。
其中，该CISM的连接信息可以但不限于包括以下至少一项：CISM的地址信息、CISM的接口信息等。
下面举例说明第一集群满足VNF对集群资源的要求。
例如，第一信息指示的VNF对集群资源的要求包括：部署VNF的集群的类型为虚拟机，部署VNF的集群所需的最大内存资源和最小内存资源均为4GB。第一集群可为由虚拟机构成的集群，且第一集群的剩余内存资源为4GB。
又例如，第一信息指示的VNF对集群资源的要求包括：部署VNF的集群所需的最大内存资源为6GB，部署VNF的集群所需的最小内存资源均为2GB，VNF不共享集群。第一集群可为该VNF独占的集群，且该第一集群的剩余内存资源可为2GB-6GB之间的任一值(如3GB)。
S603：NFVO向VNFM发送第一消息。其中，第一消息可包含CISM的连接信息，可用于触发VNFM在CISM管理的第一集群上部署或者说实例化VNF。
其中，该第一消息可为现有的消息(例如，实例化请求或资源授权响应等)，也可以为新的消息，本申请对此不作限定。
S604：VNFM根据CISM的连接信息，向CISM发送第三消息。其中，第三消息可用于请求CISM在第一集群上部署VNF。
可选的，当CISM的连接信息包括CISM的地址信息时，VNFM可向该地址信息所指示的地址发送第三消息。当该CISM的连接信息包括CISM的接口信息时，VNFM可向该接口信息所指示的接口发送第三消息。
其中，第三消息可为现有的消息(例如，容器资源创建请求)，也可以为新的消息，本申请对此不作限定。
另外，第三消息还可包含该VNF的MCIOP。CISM在接收到第三消息之后，可在第一集群上按照MCIOP来部署，或者说实例化VNF。
通过该方法，NFVO根据VNF对集群的要求来获取管理第一集群的CISM的连接信息，并向VNFM发送该连接信息。其中，第一集群满足该要求。VNFM在获取该连接信息后，可请求该CISM在第一集群上部署该VNF。由于容器是部署在集群上的，第一集群能够满 足VNF对集群的要求，也必然能够满足容器部署的要求。因此，通过该方法部署VNF，可提高VNF部署成功的可能性。
可选的，在上述方法的一种实施场景中，S601可通过以下方式之一实现：
方式一：NFVO获取该VNF的VNFD中的第一信息。
其中，NFVO可在业务请求方发起部署VNF的过程中，获取来自业务请求方的VNFD。其中，该业务请求方可以但不限于为用户或EM。
可选的，NFVO可通过解析VNFD来获取VNFD中的第一信息。
此外，第一信息还可包含在VNFD中的VNF节点信息中；此时，在该方式一中，NFVO可获取VNF节点信息中的第一信息。在该方法中，VNF节点信息中可不包含容器资源信息(例如，图5所示的osContainerDesc)，而是包含用于指示VNF对集群资源的要求的第一信息，从而可避免VNFD中的容器资源信息和容器管理平台所管理的部署包的冲突，进而提高VNF部署成功的可能性。
方式二：VNFM向NFVO发送第一信息，相应的，NFVO接收来自VNFM的第一信息。
可选的，在该方式二可包括步骤A1-A2：
A1：VNFM获取VNFD中的第一信息。
其中，VNFM可从NFVO获取该VNFD。例如，VNFM可通过S401-S403中的方法获取该VNFD。然后，VNFM可通过解析该VNFD获取第一信息。
此外，第一信息可包含在VNFD中的VNF节点信息中；此时，在步骤A1中，VNFM可获取VNF节点信息中的第一信息。在该方法中，VNF节点信息中可不包含容器资源信息(例如，图5所示的osContainerDesc)，而是包含用于指示VNF对集群资源的要求的第一信息，从而可避免VNFD中的容器资源信息和容器管理平台所管理的部署包的冲突，进而提高VNF部署成功的可能性。
A2：VNMF向NFVO发送第一信息。
其中，第一信息可承载在现有的消息(例如，资源授权请求)中，也可以承载在新的消息中，本申请对此不作限定。
通过上述方法，NFVO可方便的获取第一信息。
可选的，在上述方法的一种实施场景中，S602可通过以下方式之一实现：
方式1：当第一信息指示VNF独占集群(即不共享集群)时，NFVO可触发创建第一集群，并获取用于管理第一集群的CISM连接信息。
可选的，方式1可包括步骤B1-B3：
B1：当第一信息指示VNF独占集群(即不共享集群)时，NFVO可向CCM发送第二消息。其中，第二消息可用于请求CCM为VNF创建满足第一信息所指示的要求的第一集群。
可选的，第二消息还可包括第一信息中的全部内容，也可以包含第一信息中用于指示VNF是否共享集群的信息之外的信息。
另外，第二消息可以是现有的消息，也可以是新的消息，本申请对此不作限定。
B2：CCM为VNF创建满足第一信息所指示的要求的第一集群。
其中，第一集群满足VNF对集群资源的要求的示例可参考S602，此处不再赘述。
另外，在创建第一集群时，CCM可获取用于管理该第一集群的CISM的连接信息。例如，CCM可通过CISM来创建第一集群；在创建过程中，CCM可通过与该CISM的交互获取该CISM的连接信息。
B3：CCM向NFVO发送用于管理第一集群的CISM的连接信息。相应的，NFVO接收来自CCM的用于管理第一集群的CISM的连接信息。
其中，该CISM的连接信息可包含在现有的消息中，也可以包含在新的消息中，本申请对此不作限定。
通过该方式，当VNF不共享集群时，NFVO可及时触发创建满足VNF对集群资源的要求的第一集群；这样，当在该第一集群上部署或者实例化该VNF时，可提高VNF部署成功的可能性。
方式2：当第一信息指示VNF能够共享集群资源时，NFVO可选择能够满足第一信息指示的要求的第一集群，并获取用于管理第一集群的CISM的连接信息。
可选的，方式2可包括步骤C1-C2：
C1：当第一信息指示VNF能够共享集群时，NFVO可根据第一信息，为VNF选择满足第一信息所指示的要求的第一集群。
可选的，NFVO可根据各个集群的信息和第一信息，来选择第一集群。其中，各个集群的信息可以是预先获取的，也可以是在接收到第一信息之后，从管理各个集群的CISM获取的。
下面举例说明NFVO如何选择第一集群。
例如，第一信息指示的VNF对集群资源的要求包括：部署VNF的集群的类型为虚拟机，部署VNF的集群所需的最大内存资源和最小内存资源均为4GB，VNF能够共享集群。NFVO获取的集群的信息包括：集群1的类型为虚拟机，集群1的剩余内存资源为4GB；集群2的类型为物理机，集群2的剩余内存资源为4GB。此时，NFVO可选择集群1作为第一集群。
又例如，第一信息指示的VNF对集群资源的要求包括：部署VNF的集群的类型为虚拟机，部署VNF的集群所需的最大内存资源为5GB，部署VNF的集群所需的最小内存资源均为3GB，VNF能够共享集群。NFVO获取的集群的信息包括：集群1的类型为虚拟机，集群1的剩余内存资源为4GB；集群2的类型为虚拟机，集群2的剩余内存资源为2GB。此时，NFVO可选择集群1作为第一集群。
另外，当满足第一信息所指示的要求的集群有多个时，NFVO可从中随机选择一个作为第一集群，也可以从中选择剩余资源最多的一个作为第一集群。
此外，当NFVO未找到能够满足第一信息所指示的要求的集群时，也可以采用方式1中的方法来创建能够满足第一信息所指示的要求的第一集群。
C2：NFVO获取用于管理第一集群的CISM的连接信息。
其中，NFVO中可包含第一集群和用于管理该第一集群的CISM的连接信息的对应关系，根据该对应关系，NFVO可获取用于管理第一集群的CISM的连接信息。其中，该对应关系的表现形式可为对应关系表，也可以为其他表现形式，本申请对此不作限定。
通过该方式，当VNF能够共享集群时，NFVO可快速选择满足VNF对集群资源的要求的第一集群；这样，当在该第一集群上部署或者实例化该VNF时，可提高VNF部署成 功的可能性。
可选的，在上述方法的一种实施场景中，在S603之前，该方法还包括：
S605：NFVO根据VNF的MCIOP类型，选择支持该MCIOP类型的VNFM。
其中，该MCIOP类型可以但不限于包括：Helm；NFVO可选择能够解析该Helm的VNFM。
可选的，MCIOP类型包含在VNFD中，例如，可包含在VNFD中的VNF节点信息中，也可以包含在VNFM信息(Vnfminfo)参数中。其中，该VnfmInfo参数也可包含在VNFD中。当MCIOP类型包含在Vnfminfo参数中时，Vnfminfo参数中可包含用于指示该MCIOP类型的第一指示字段，该第一指示字段可为Vnfminfo参数中现有的信元，也可以为Vnfminfo参数中新的信元。示例性的，当该第一指示字段的取值为第六值(例如，VNFM-helm)时，可指示VNFM需要能够解析Helm。
另外，当本步骤与上述方式二结合时，NFVO可先执行S605，再向VNFM发送VNFD。
通过该方法，NFVO选择能够支持MCIOP类型的VNFM来部署VNF，从而可提高部署VNF成功的可能性。
可选的，在上述方法的一种实施场景中，在S602之后，该方法还包括：
S606：NFVO向VNFM发送用于指示授权在第一集群中实例化VNF的信息。
其中，在第一集群中实例化VNF的信息也可以理解为在第一集群中部署VNF的信息。
其中，该用于指示授权在第一集群中实例化VNF的信息可以为消息，也可以为消息中的信元。具体地，当用于指示授权在第一集群中实例化VNF的信息为信元时，用于指示授权在第一集群中实例化VNF的信息可以复用现有消息(例如，实例化请求或资源授权响应)中的信元，也可以是现有消息中的新的信元。例如，该信元可以为第二指示字段(例如，授权信息(grantInfo))，当该第二指示字段取值为第七值(例如，通过(approved))时，可以指示授权在第一集群中实例化VNF的信息。又例如，当用于指示授权在第一集群中实例化VNF的信息复用现有消息中的信元时，该信元可以为VIM连接信息(VimConnectionInfo，用于虚拟机VNF的创建)或者CISM连接信息；示例性的，当该信元为VimConnectionInfo时，VimConnectionInfo可包含连接信息(例如，接入地址统一资源定位符(uniform resource locator，URL)，接入时的用户名，密码，鉴权参数等)以及用于指示是否授权在第一集群中实例化VNF的信息。
另外，本申请对S603和S606的执行顺序不作限定，可以先执行S603，再执行S606；也可以先执行S606，再执行S603；还可同时执行S603和S606。当同时执行S603和S606时，用于指示授权在第一集群中实例化VNF的信息可携带在第一消息中。
通过该方法，NFVO可以方便的指示VNFM已授权在第一集群中部署或者实例化VNF。
可选的，在上述方法的一种实施场景中，上述方法还可包括步骤D1-D2：
D1：VNFM获取VNFD中的至少一个MCIOP，以及用于指示至少一个MCIOP的顺序的信息。
可选的，VNFD中可包含至少一个MCIOP，以及用于指示至少一个MCIOP的顺序的信息。其中，该VNFD可为方式一或方式二中的VNFD；MCIOP的具体内容可参考对图5 的说明，此处不再赘述。用于指示至少一个MCIOP的顺序的信息可以直接或间接指示至少一个MCIOP的部署顺序(也可称为执行顺序)。当用于指示至少一个MCIOP的顺序的信息间接指示至少一个MCIOP的部署顺序时，用于指示至少一个MCIOP的顺序的信息可指示VNF对至少一个MCIOP的依赖关系。
D2：VNFM根据用于指示至少一个MCIOP的顺序的信息，部署至少一个MCIOP。
在一些可能的方式中，VNFM可根据用于指示至少一个MCIOP的顺序的信息确定至少一个MCIOP的部署顺序，并根据该部署顺序来部署MCIOP。
下面对VNFM根据用于指示至少一个MCIOP的顺序的信息确定至少一个MCIOP的部署顺序进行说明。
指示至少一个MCIOP的顺序的信息可指示至少一个MCIOP的部署顺序；VNMF可通过读取该信息，确定至少一个MCIOP的部署顺序。例如，VNFD中包含的至少一个MCIOP为MCIOP 1和MCIOP 2，指示至少一个MCIOP的顺序的信息指示：MCIOP 1的部署顺序为1，MCIOP 2的部署顺序为2；此时，VNFM可确定先部署MCIOP 1，再部署MCIOP 2。
可选的，该部署顺序可与VNF对至少一个MCIOP的依赖关系(例如，依赖顺序)有关。因此，指示至少一个MCIOP的顺序的信息可通过指示VNF对至少一个MCIOP的依赖关系来指示至少一个MCIOP的部署顺序。例如，VNFD中包含的至少一个MCIOP为MCIOP 1和MCIOP 2，该依赖关系为：VNF先依赖MCIOP 1，再依赖MCIOP 2；此时，VNFM可确定先部署MCIOP 1，再部署MCIOP 2。
下面说明VNFM根据该部署顺序来部署MCIOP。
VNFM可按照该部署顺序，依次向CISM发送包含对应的MCIOP的第三消息。例如，VNFD中包含的至少一个MCIOP为MCIOP 1和MCIOP 2，用于指示至少一个MCIOP的顺序的信息指示：先部署MCIOP 1，再部署MCIOP 2。VNFM先向CISM发送包含MCIOP1的第三消息，请求CISM在第一集群上按照MCIOP 1部署或者实例化VNF；然后，向CISM发送包含MCIOP 2的第三消息，请求CISM在第一集群上按照MCIOP 2部署或者实例化VNF。这样，CISM可先部署MCIOP 1，再部署MCIOP 2。
在另一些可能的方式中，VNFM可向CISM发送第三消息，该第三消息包含VNFD中的至少一个MCIOP，以及用于指示至少一个MCIOP的顺序的信息。这样，CISM可按照该顺序部署至少一个MCIOP。CISM确定至少一个MCIOP的部署顺序的方式可参考VNFM确定至少一个MCIOP的部署顺序的方式，此处不再赘述。
通过该方法，VNFM可按照指示的顺序有效的部署至少一个MCIOP。
下面分别通过图7-图9所示的方法详细介绍图6所示的方法中的具体的实现方式。其中，图7-图8所示的方法主要介绍其中的可能的情况一，即NFVO解析VNFD中的第一信息，并根据第一信息获取CISM的连接信息；图9所示的方法主要介绍其中的可能的情况二，即VNFM解析VNFD中的第一信息之后，向NFVO发送该第一信息，NFVO再根据第一信息获取CISM的连接信息。
图7示出了一种部署VNF的方法，该方法可应用于图1或图3所示的架构中。下面参阅图7所示的流程图，对该方法的流程进行具体说明。
S701：NFVO获取VNFD中的集群能力(ClusterCapabilities)信息，该ClusterCapabilities信息可为图6所示方法中的第一信息。
其中，该ClusterCapabilities信息中可包含集群资源信息和/或用于指示VNF是否共享集群的信息。其中，该集群资源信息可用于指示以下至少一项：部署VNF的集群的类型，部署VNF的集群的资源大小，部署VNF的集群中每个资源节点的资源大小，部署VNF的集群的规格。具体内容可参考S601，此处不再赘述。
示例性的，图8示出了该VNFD的一种可能的实现方式。如图8所示，该VNFD可以包含以下至少一项：包含ClusterCapabilities信息的VNF节点信息、一个或多个MCIOP、用于指示MCIOP的顺序的信息。
其中，ClusterCapabilities信息描述了VNF部署对集群资源的需求。VNF所对应的容器是部署在CISM所管理的集群上的。如果集群由虚拟机构成，则容器部署在虚拟机上(这种部署方式部署的容器可称为虚拟机容器)；如果集群由物理机构成，则容器部署在物理机上(这种部署方式部署的容器可称为裸金属容器)。
可选的，ClusterCapabilities信息包括表1所示的信息中的一项或多项。
表1
VNF节点信息中除ClusterCapabilities信息之外的内容可参考S403，此处不再赘述。
其中，一个VNF节点信息可与一个或多个MCIOP对应。当一个VNF节点信息与多个MCIOP对应时，该VNFD可包含用于指示该多个MCIOP的顺序的信息，该顺序可为多个MCIOP的部署顺序。例如，如图8所示，用于指示该多个MCIOP的顺序的信息可包含需求1(requirement_1)和需求2(requirement_2)。其中，requirement_1可指示MCIOP_1的部署顺序为1，requirement_2可指示MCIOP_2的部署顺序为2；也就是说，requirement_1可指示部署多个MCIOP时第一个部署的MCIOP为MCIOP_1，requirement_2可指示部署多个MCIOP时第二个部署的MCIOP为MCIOP_1。
S702：NFVO根据ClusterCapabilities信息，获取CISM的连接信息。
其中，NFVO可通过以下实现方式之一来获取CISM的连接信息。
实现方式1：当ClusterCapabilities里的sharingIndicator参数为false时，NFVO请求 CCM创建新的集群(即图6所示方法中的方式1中的第一集群)，并获取用于管理该第一集群的CISM的连接信息。
可选的，该实现方式1可包括：
S702a1：NFVO向CCM发送用于请求创建第一集群的消息。
其中，该消息可包含ClusterCapabilities中type和ResourceDefinition。
S702a2：CCM在创建满足type和ResourceDefinition的第一集群后，向NFVO发送管理该第一集群的CISM的连接信息。
该实现方式1的具体内容可参考图6所示方法中的方式1，此处不再赘述。
实现方式2：当ClusterCapabilities里的sharingIndicator参数为true时，NFVO在所管理的资源中选择能够满足集群需求的CISM。例如，选择管理满足type和ResourceDefinition的集群(即图6所示方法中的方式2中的第一集群)的CISM。然后，NFVO可获取该CISM的连接信息。
该实现方式2的具体内容可参考图6所示方法中的方式2，此处不再赘述。
S703：NFVO根据VNF的MCIOP类型，选择支持该MCIOP类型的VNFM。
S703的具体内容可参考S605，此处不再赘述。
S704：NFVO向VNFM发送实例化请求。
其中，该实例化请求中包含CISM的连接信息。
可选的，该实例化请求中还可包含授权通过的指示。由于容器是部署在集群上的，集群满足需求意味着容器部署的需求也已经满足。因此，可在实例化请求中包含授权通过的指示。其中，该授权通过的指示可为图6所示方法中的授权在第一集群中实例化VNF的信息，具体内容可参考S606，此处不再赘述。
S705：VNFM根据VNFD中用于指示该多个MCIOP的顺序的信息，确定MCIOP的部署顺序。
S705的具体内容可参考步骤D2，此处不再赘述。
S706：VNFM根据该部署顺序，请求CISM部署MCIOP。
其中，VNFM可按照该部署顺序，通过VNFM中的Helm工具依次对VNFD中的MCIOP进行解析；然后，根据CISM的连接信息(例如，调用该连接信息指示的CISM接口(如K8S接口))，请求CISM按照该部署顺序来部署MCIOP。
例如，多个MCIOP为MCIOP 1和MCIOP 2，用于指示至少一个MCIOP的顺序的信息指示：先部署MCIOP 1，再部署MCIOP 2。VNFM可通过该VNFM中的Helm工具先解析MCIOP 1，再解析MCIOP 2；然后，VNFM可调用CISM的连接信息指示的CISM接口(如K8S接口)，先请求CISM部署MCIOP 1，再请求CISM部署MCIOP 2。
S707：CISM向VNFM发送容器资源创建响应，以指示成功创建容器资源。
S708：VNFM向NFVO发送实例化响应，以指示成功部署或者实例化VNF。
可选的，当VNFD中不包含用于指示MCIOP的顺序的信息(例如，当VNFD中仅包含一个MCIOP时，不需要指示MCIOP的顺序)时，S705是可选的步骤，S706可替换为VNFM请求CISM部署MCIOP。
通过该方法，NFVO可解析VNF对集群的要求，并根据该要求来获取管理满足该要求的第一集群的CISM的连接信息；VNFM在接收来自NFVO的该连接信息后，可请求该CISM在第一集群上部署该VNF。在该方法中，通过在VNF中增加集群能力信息来代替容 器资源信息，从而可避免VNFD中的容器资源信息和MCIOP的冲突。由于容器是部署在集群上的，第一集群能够满足VNF对集群的要求，也必然能够满足容器部署的要求。因此，通过该方法部署VNF，可提高VNF部署成功的可能性。
另外，在该实施例中，VNFD中包含指示VNF是否共享集群的信息，从而可实现了VNF部署独占集群或者共享集群。
图9示出了一种部署VNF的方法，该方法可应用于图1或图3所示的系统架构中。下面参阅图9所示的流程图，对该方法的流程进行具体说明。
S901：NFVO获取VNFD。
其中，VNFD的具体内容可参考S701，此处不再赘述。
S902：NFVO根据VNFD中的MCIOP类型，选择支持该MCIOP类型的VNFM。
S902的具体内容可参考S703，此处不再赘述。
S903：NFVO向VNFM发送实例化请求，以请求部署或者实例化VNF。
S903的具体内容可参考S401，此处不再赘述。
S904：VNFM向NFVO发送资源授权请求。
其中，资源授权请求中可包含ClusterCapabilities信息。ClusterCapabilities信息的具体内容可参考S701，此处不再赘述。
可选的，VNFM可在获取VNFD之后，向NFVO发送资源授权请求。其中，VNFM获取VNFD的方式可参考S402-S403，此处不再赘述。
S905：NFVO根据ClusterCapabilities信息，获取CISM的连接信息。
S905的具体内容可参考S702，此处不再赘述。
S906：NFVO向VNFM发送CISM的连接信息。其中，CISM的连接信息可包含在资源授权响应中。
S907：VNFM根据VNFD中用于指示该多个MCIOP的顺序的信息，确定MCIOP的部署顺序。
S908：VNFM根据该部署顺序，请求CISM部署MCIOP。
S907-S908的具体内容可参考S705-S706，此处不再赘述。
S909：CISM向VNFM发送容器资源创建响应，以指示成功创建容器资源。
S910：VNFM向NFVO发送实例化响应，以指示成功部署或者实例化VNF。
通过该方法，VNFM可解析VNF对集群的要求，并通过NFVO该要求；NFVO可根据该要求来获取管理第一集群的CISM的连接信息，其中，第一集群满足该要求；VNFM在接收到来自NFVO的连接信息后，可请求该CISM在第一集群上部署该VNF。在该方法中，通过在VNF中增加集群能力信息来代替容器资源信息，从而可避免VNFD中的容器资源信息和MCIOP的冲突。由于容器是部署在集群上的，第一集群能够满足VNF对集群的要求，也必然能够满足容器部署的要求。因此，通过该方法部署VNF，可提高VNF部署成功的可能性。
另外，在该实施例中，VNFD中包含指示VNF是否共享集群的信息，从而可实现了VNF部署独占集群或者共享集群。
此外，图6-图9所示方法是以容器管理平台管理的部署包为MCIOP为例进行说明的。应理解，本申请也可应用于其他容器管理平台管理的部署包，此时，可将图6-图9所示方 法中的MCIOP替换为其他容器管理平台管理的部署包。
基于与图6-图9方法实施例相同的发明构思，本申请实施例通过图10提供了一种部署VNF的装置，可用于执行上述方法实施例中相关步骤的功能。所述功能可以通过硬件实现，也可以通过软件或者硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。该部署VNF的装置的结构如图10所示，包括通信单元1001和处理单元1002。该部署VNF的装置1000可以应用于图1或图3所示的架构中的NFVO或VNFM，并可以实现以上本申请实施例以及实例提供的方法。下面对所述部署VNF的装置1000中的各个单元的功能进行介绍。
所述通信单元1001，用于接收和发送数据。
当所述部署VNF的装置1000应用于NFVO或VNFM时，所述通信单元1001可以通过物理接口、通信模块、通信接口、输入输出接口实现。所述部署VNF的装置1000可以通过该通信单元1001连接网线或电缆，进而与其他设备建立物理连接。
所述处理单元1002可用于支持所述部署VNF的装置1000执行上述方法实施例中的处理动作。所述处理单元1002可以是通过处理器实现。例如，所述处理器可以为中央处理单元(central processing unit，CPU)，还可以是其它通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现场可编程门阵列(field programmable gate array，FPGA)或者其它可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。通用处理器可以是微处理器，也可以是任何常规的处理器。
在一种实施方式中，所述部署VNF的装置1000应用于图6-图9任一项所示的本申请实施例中的NFVO。下面对该实施方式中的所述处理单元1002的具体功能进行介绍。
所述处理单元1002，用于：获取第一信息，所述第一信息用于指示待部署的VNF对集群资源的要求；根据所述第一信息，获取用于管理第一集群的CISM的连接信息，所述第一集群满足所述VNF对集群资源的要求；通过所述通信单元1001向VNFM发送第一消息，所述第一消息包含所述CISM的连接信息，所述第一消息用于触发所述VNFM在所述CISM管理的所述第一集群上部署所述VNF。
可选的，所述处理单元1002具体用于：获取VNFD中的所述第一信息；和/或，通过所述通信单元1001接收来自所述VNFM的所述第一信息。
可选的，所述处理单元1002具体用于：获取所述VNFD包含的VNF节点信息中的所述第一信息。
可选的，所述VNFD还包含：至少一个可管理的容器基础对象包MCIOP，以及用于指示所述至少一个MCIOP的顺序的信息。
可选的，所述处理单元1002具体用于：当所述第一信息指示所述VNF独占集群时，通过所述通信单元1001向CCM发送第二消息，所述第二消息用于请求所述CCM为所述VNF创建满足所述要求的所述第一集群；通过所述通信单元1001接收来自所述CCM的用于管理所述第一集群的所述CISM的连接信息。
可选的，所述处理单元1002具体用于：当所述第一信息指示所述VNF能够共享集群时，根据所述第一信息，为所述VNF选择满足所述要求的所述第一集群；获取用于管理所述第一集群的所述CISM的连接信息。
可选的，所述处理单元1002具体用于：在向VNFM发送第一消息之前，根据所述VNF的MCIOP类型，选择支持所述MCIOP类型的所述VNFM。
可选的，所述MCIOP类型包含在Vnfminfo参数中。
可选的，所述处理单元1002具体用于：在获取用于管理第一集群的CISM的连接信息之后，通过所述通信单元1001向所述VNFM发送用于指示授权在所述第一集群中部署所述VNF的信息。
可选的，所述VNF对集群资源的要求包括：部署所述VNF的集群中资源节点的数量、部署所述VNF的集群中每个资源节点的资源大小。
可选的，所述VNF对集群资源的要求还包括以下至少一项：部署所述VNF的集群的类型、部署所述VNF的集群的规格、所述VNF是否共享集群。
在一种实施方式中，所述部署VNF的装置1000应用于图6-图9任一项所示的本申请实施例中的VNFM。下面对该实施方式中的所述处理单元1002的具体功能进行介绍。
所述处理单元1002，用于：通过所述通信单元1001接收来自NFVO的第一消息，所述第一消息包含用于管理第一集群的CISM的连接信息，所述第一集群满足待部署的VNF对集群资源的要求；根据所述CISM的连接信息，通过所述通信单元1001向所述CISM发送第三消息，所述第三消息用于请求所述CISM在所述第一集群上部署所述VNF。
可选的，所述处理单元1002具体用于：在接收来自NFVO的第一消息之前，获取VNFD中的第一信息，所述第一信息用于指示所述VNF对集群资源的要求；通过所述通信单元1001向所述NFVO发送所述第一信息。
可选的，所述处理单元1002具体用于：获取所述VNFD包含的VNF节点信息中的所述第一信息。
可选的，所述处理单元1002具体用于：获取VNFD中的至少一个可管理的容器基础对象包MCIOP，以及用于指示所述至少一个MCIOP的顺序的信息；根据所述用于指示所述至少一个MCIOP的顺序的信息，部署所述至少一个MCIOP。
可选的，所述处理单元1002具体用于：在向所述CISM发送第三消息之前，通过所述通信单元1001接收来自NFVO的用于指示授权在所述第一集群中部署所述VNF的信息。
可选的，所述VNF对集群资源的要求包括：部署所述VNF的集群中资源节点的数量、部署所述VNF的集群中每个资源节点的资源大小。
可选的，所述VNF对集群资源的要求还包括以下至少一项：部署所述VNF的集群的类型、部署所述VNF的集群的规格、所述VNF是否共享集群。
需要说明的是，本申请以上实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备 (可以是个人计算机，服务器，或者网络设备等)或处理器(processor)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
基于相同的技术构思，本申请实施例通过图11所示提供了一种部署VNF的设备，可用于执行上述方法实施例中相关的步骤。所述部署VNF的设备可以应用于图1或图3所示的架构中的NFVO或VNFM，可以实现以上本申请实施例以及实例提供的方法，具有图10所示的部署VNF的装置的功能。参阅图11所示，所述部署VNF的设备1100包括：通信模块1101、处理器1102以及存储器1103。其中，所述通信模块1101、所述处理器1102以及所述存储器1103之间相互连接。
可选的，所述通信模块1101、所述处理器1102以及所述存储器1103之间通过总线1104相互连接。所述总线1104可以是外设部件互连标准(peripheral component interconnect，PCI)总线或扩展工业标准结构(extended industry standard architecture，EISA)总线等。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图11中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
所述通信模块1101，用于接收和发送数据，实现与其他设备之间的通信交互。例如，所述通信模块1101可以通过物理接口、通信模块、通信接口、输入输出接口实现。
所述处理器1102可用于支持所述部署VNF的设备1100执行上述方法实施例中的处理动作。当所述部署VNF的设备1100用于实现上述方法实施例时，处理器1102还可用于实现上述处理单元1002的功能。所述处理器1102可以是CPU，还可以是其它通用处理器、DSP、ASIC、FPGA或者其它可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。通用处理器可以是微处理器，也可以是任何常规的处理器。
在一种实施方式中，所述部署VNF的设备1100应用于图6-图9任一项所示的本申请实施例中的NFVO。所述处理器1102具体用于：
获取第一信息，所述第一信息用于指示所述VNF对集群资源的要求；根据所述第一信息，获取用于管理第一集群的CISM的连接信息，所述第一集群满足所述VNF对集群资源的要求；通过所述通信模块1101向VNFM发送第一消息，所述第一消息包含所述CISM的连接信息，所述第一消息用于触发所述VNFM在所述CISM管理的所述第一集群上部署所述VNF。
在一种实施方式中，所述部署VNF的设备1100应用于图6-图9任一项所示的本申请实施例中的VNFM。所述处理器1102具体用于：
通过所述通信模块1101接收来自NFVO的第一消息，所述第一消息包含用于管理第一集群的CISM的连接信息，所述第一集群满足所述VNF对集群资源的要求；根据所述CISM的连接信息，通过所述通信模块1101向所述CISM发送第三消息，所述第三消息用于请求所述CISM在所述第一集群上部署所述VNF。
所述处理器1102的具体功能可以参考以上本申请实施例以及实例提供的方法中的描述，以及图10所示本申请实施例中对所述部署VNF的装置1000的具体功能描述，此处不再赘述。
所述存储器1103，用于存放程序指令和数据等。具体地，程序指令可以包括程序代码， 该程序代码包括计算机操作指令。存储器1103可能包含RAM，也可能还包括非易失性存储器(non-volatile memory)，例如至少一个磁盘存储器。处理器1102执行存储器1103所存放的程序指令，并使用所述存储器1103中存储的数据，实现上述功能，从而实现上述本申请实施例提供的方法。
可以理解，本申请图11中的存储器1103可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是ROM、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是RAM，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(Synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DR RAM)。应注意，本文描述的系统和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
基于以上实施例，本申请实施例还提供了一种计算机程序，当所述计算机程序在计算机上运行时，使得所述计算机执行以上实施例提供的方法。
基于以上实施例，本申请实施例还提供了一种计算机可读存储介质，该计算机可读存储介质中存储有计算机程序，所述计算机程序被计算机执行时，使得计算机执行以上实施例提供的方法。
其中，存储介质可以是计算机能够存取的任何可用介质。以此为例但不限于：计算机可读介质可以包括RAM、ROM、EEPROM、CD-ROM或其他光盘存储、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质。
基于以上实施例，本申请实施例还提供了一种芯片，所述芯片用于读取存储器中存储的计算机程序，实现以上实施例提供的方法。
基于以上实施例，本申请实施例提供了一种芯片系统，该芯片系统包括处理器，用于支持计算机装置实现以上实施例中各设备所涉及的功能。在一种可能的设计中，所述芯片系统还包括存储器，所述存储器用于保存该计算机装置必要的程序和数据。该芯片系统，可以由芯片构成，也可以包含芯片和其他分立器件。
综上所述，本申请实施例提供了一种部署VNF的方法、装置及设备，在该方法中，NFVO在获取第一信息之后，可根据第一信息，获取用于管理第一集群的CISM的连接信息；其中，第一信息可用于指示待部署的VNF对集群资源的要求，第一集群可满足VNF对集群资源的要求。然后，NFVO可向VNFM发送包含该连接信息的第一消息，VNFM在获取该连接信息后，可请求该CISM在第一集群上部署该VNF。由于容器是部署在集群上的，第一集群能够满足VNF对集群的要求，也必然能够满足容器部署的要求。因此，通过该方法部署VNF，可提高VNF部署成功的可能性。
在本申请的各个实施例中，如果没有特殊说明以及逻辑冲突，不同的实施例之间的术语和/或描述具有一致性、且可以相互引用，不同的实施例中的技术特征根据其内在的逻辑关系可以组合形成新的实施例。
本领域内的技术人员应明白，本申请的实施例可提供为方法、系统、或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (22)

  1. 一种部署虚拟化网络功能VNF的方法，其特征在于，应用于网络功能虚拟化编排器NFVO，所述方法包括：
    获取第一信息；其中，所述第一信息用于指示待部署的VNF对集群资源的要求；
    根据所述第一信息，获取用于管理第一集群的容器基础设施管理器CISM的连接信息；其中，所述第一集群满足所述VNF对集群资源的要求；
    向虚拟化网络功能管理器VNFM发送第一消息；其中，所述第一消息包含所述CISM的连接信息，所述第一消息用于触发所述VNFM在所述CISM管理的所述第一集群上部署所述VNF。
  2. 根据权利要求1所述的方法，其特征在于，获取第一信息，包括以下至少一项：
    获取虚拟化网络功能描述模板VNFD中的所述第一信息；
    接收来自所述VNFM的所述第一信息。
  3. 根据权利要求2所述的方法，其特征在于，获取VNFD中的所述第一信息，包括：
    获取所述VNFD包含的VNF节点信息中的所述第一信息。
  4. 根据权利要求2或3所述的方法，其特征在于，所述VNFD还包含：
    至少一个可管理的容器基础对象包MCIOP，以及用于指示所述至少一个MCIOP的顺序的信息。
  5. 根据权利要求1至4任一项所述的方法，其特征在于，当所述第一信息指示所述VNF独占集群时，根据所述第一信息，获取用于管理第一集群的CISM的连接信息，包括：
    向容器集群管理器CCM发送第二消息；其中，所述第二消息用于请求所述CCM为所述VNF创建满足所述要求的所述第一集群；
    接收来自所述CCM的用于管理所述第一集群的所述CISM的连接信息。
  6. 根据权利要求1至4任一项所述的方法，其特征在于，当所述第一信息指示所述VNF能够共享集群时，根据所述第一信息，获取用于管理第一集群的CISM的连接信息，包括：
    根据所述第一信息，为所述VNF选择满足所述要求的所述第一集群；
    获取用于管理所述第一集群的所述CISM的连接信息。
  7. 根据权利要求1至6任一项所述的方法，其特征在于，在向VNFM发送第一消息之前，所述方法还包括：
    根据所述VNF的MCIOP类型，选择支持所述MCIOP类型的所述VNFM。
  8. 根据权利要求7所述的方法，其特征在于，所述MCIOP类型包含在虚拟化网络功能管理器信息Vnfminfo参数中。
  9. 根据权利要求1至8任一项所述的方法，其特征在于，在获取用于管理第一集群的CISM的连接信息之后，所述方法还包括：
    向所述VNFM发送用于指示授权在所述第一集群中部署所述VNF的信息。
  10. 根据权利要求1至9任一项所述的方法，其特征在于，所述VNF对集群资源的要求包括：
    部署所述VNF的集群中资源节点的数量、部署所述VNF的集群中每个资源节点的资源大小。
  11. 根据权利要求10所述的方法，其特征在于，所述VNF对集群资源的要求还包括以 下至少一项：
    部署所述VNF的集群的类型、部署所述VNF的集群的规格、所述VNF是否共享集群。
  12. 一种部署虚拟化网络功能VNF的方法，其特征在于，应用于虚拟化网络功能管理器VNFM，所述方法包括：
    接收来自网络功能虚拟化编排器NFVO的第一消息；其中，所述第一消息包含用于管理第一集群的容器基础设施管理器CISM的连接信息，所述第一集群满足待部署的VNF对集群资源的要求；
    根据所述CISM的连接信息，向所述CISM发送第三消息；其中，所述第三消息用于请求所述CISM在所述第一集群上部署所述VNF。
  13. 根据权利要求12所述的方法，其特征在于，在接收来自NFVO的第一消息之前，所述方法还包括：
    获取虚拟化网络功能描述模板VNFD中的第一信息；其中，所述第一信息用于指示所述VNF对集群资源的要求；
    向所述NFVO发送所述第一信息。
  14. 根据权利要求13所述的方法，其特征在于，获取VNFD中的第一信息，包括：
    获取所述VNFD包含的VNF节点信息中的所述第一信息。
  15. 根据权利要求12至14任一项所述的方法，其特征在于，所述方法还包括：
    获取VNFD中的至少一个可管理的容器基础对象包MCIOP，以及用于指示所述至少一个MCIOP的顺序的信息；
    根据所述用于指示所述至少一个MCIOP的顺序的信息，部署所述至少一个MCIOP。
  16. 根据权利要求12至15任一项所述的方法，其特征在于，在向所述CISM发送第三消息之前，所述方法还包括：
    接收来自NFVO的用于指示授权在所述第一集群中部署所述VNF的信息。
  17. 根据权利要求12至16任一项所述的方法，其特征在于，所述VNF对集群资源的要求包括：
    部署所述VNF的集群中资源节点的数量、部署所述VNF的集群中每个资源节点的资源大小。
  18. 根据权利要求17所述的方法，其特征在于，所述VNF对集群资源的要求还包括以下至少一项：
    部署所述VNF的集群的类型、部署所述VNF的集群的规格、所述VNF是否共享集群。
  19. 一种部署虚拟化网络功能VNF的装置，其特征在于，包括：
    通信单元，用于接收和发送数据；
    处理单元，用于通过所述通信单元，执行如权利要求1-18任一项所述的方法。
  20. 一种部署虚拟化网络功能VNF的系统，其特征在于，包括：
    网络功能虚拟化编排器NFVO，用于实现如权利要求1-11任一项所述的方法；
    虚拟化网络功能管理器VNFM，用于实现如权利要求12-18任一项所述的方法。
  21. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质中存储有计算机程序，当所述计算机程序在计算机上运行时，使得所述计算机执行权利要求1-18任一项所述的方法。
  22. 一种芯片，其特征在于，所述芯片与存储器耦合，所述芯片读取所述存储器中存储的计算机程序，执行权利要求1-18任一项所述的方法。
PCT/CN2023/082655 2022-03-25 2023-03-21 一种部署vnf的方法、装置及设备 WO2023179580A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210305866.8 2022-03-25
CN202210305866.8A CN116841689A (zh) 2022-03-25 2022-03-25 一种部署vnf的方法、装置及设备

Publications (1)

Publication Number Publication Date
WO2023179580A1 true WO2023179580A1 (zh) 2023-09-28

Family

ID=88099955

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/082655 WO2023179580A1 (zh) 2022-03-25 2023-03-21 一种部署vnf的方法、装置及设备

Country Status (2)

Country Link
CN (1) CN116841689A (zh)
WO (1) WO2023179580A1 (zh)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109995571A (zh) * 2018-01-02 2019-07-09 中国移动通信有限公司研究院 服务器配置与vnf应用匹配的方法及装置
US20190334781A1 (en) * 2018-04-26 2019-10-31 Metaswitch Networks Ltd. Network functions virtualization
US20200084110A1 (en) * 2018-09-06 2020-03-12 Foundation Of Soongsil University-Industry Cooperation System and method for configuring cluster of virtualization network functions
CN111371616A (zh) * 2020-03-05 2020-07-03 南京大学 一种面向numa架构服务器的虚拟网络功能链部署方法和系统
CN111385114A (zh) * 2018-12-28 2020-07-07 华为技术有限公司 Vnf服务实例化方法及装置
CN111949364A (zh) * 2019-05-16 2020-11-17 华为技术有限公司 容器化vnf的部署方法和相关设备

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109995571A (zh) * 2018-01-02 2019-07-09 中国移动通信有限公司研究院 服务器配置与vnf应用匹配的方法及装置
US20190334781A1 (en) * 2018-04-26 2019-10-31 Metaswitch Networks Ltd. Network functions virtualization
US20200084110A1 (en) * 2018-09-06 2020-03-12 Foundation Of Soongsil University-Industry Cooperation System and method for configuring cluster of virtualization network functions
CN111385114A (zh) * 2018-12-28 2020-07-07 华为技术有限公司 Vnf服务实例化方法及装置
CN111949364A (zh) * 2019-05-16 2020-11-17 华为技术有限公司 容器化vnf的部署方法和相关设备
CN111371616A (zh) * 2020-03-05 2020-07-03 南京大学 一种面向numa架构服务器的虚拟网络功能链部署方法和系统

Also Published As

Publication number Publication date
CN116841689A (zh) 2023-10-03

Similar Documents

Publication Publication Date Title
US10701139B2 (en) Life cycle management method and apparatus
JP7074880B2 (ja) ネットワーク・スライスの展開方法および装置
US20210004258A1 (en) Method and Apparatus for Creating Virtual Machine
EP3291499B1 (en) Method and apparatus for network service capacity expansion
WO2018024059A1 (zh) 一种虚拟化网络中业务部署的方法和装置
US10397132B2 (en) System and method for granting virtualized network function life cycle management
EP3723325B1 (en) Network service management method, related device and system
WO2020177564A1 (zh) Vnf的生命周期管理方法及装置
US20190196878A1 (en) Resource Pool Processing Method and Apparatus, and Device
US11301284B2 (en) Method for managing VNF instantiation and device
WO2017185251A1 (zh) Vnfm的确定方法和网络功能虚拟化编排器
WO2022007631A1 (zh) 一种多租户管理方法及装置
CN109995552B (zh) Vnf服务实例化方法及装置
WO2021185083A1 (zh) Vnf实例化方法及装置
WO2016131171A1 (zh) 一种针对vnf包进行操作的方法及装置
CN112764873A (zh) 实例化ns的方法及nfvo
US11360824B2 (en) Customized partitioning of compute instances
WO2023046026A1 (zh) 一种容器化vnf的部署方法及装置
WO2023179580A1 (zh) 一种部署vnf的方法、装置及设备
WO2023030218A1 (zh) 网络业务部署方法、nfvo以及nfv系统
WO2021232860A1 (zh) 通信方法、装置及系统
CN109257201B (zh) 一种License的发送方法和装置
WO2023155838A1 (zh) 一种虚拟网络功能vnf实例化的方法及装置
WO2024114645A1 (zh) 一种虚拟化网络功能vnf的实例化方法及装置
WO2024114630A1 (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: 23773827

Country of ref document: EP

Kind code of ref document: A1