WO2023155838A1 - 一种虚拟网络功能vnf实例化的方法及装置 - Google Patents

一种虚拟网络功能vnf实例化的方法及装置 Download PDF

Info

Publication number
WO2023155838A1
WO2023155838A1 PCT/CN2023/076484 CN2023076484W WO2023155838A1 WO 2023155838 A1 WO2023155838 A1 WO 2023155838A1 CN 2023076484 W CN2023076484 W CN 2023076484W WO 2023155838 A1 WO2023155838 A1 WO 2023155838A1
Authority
WO
WIPO (PCT)
Prior art keywords
vnf
deployment
information
nfv
template
Prior art date
Application number
PCT/CN2023/076484
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 WO2023155838A1 publication Critical patent/WO2023155838A1/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/45595—Network integration; Enabling network access in virtual machine instances

Definitions

  • the present application relates to the field of communication technologies, and in particular to a method and device for instantiating a virtualized network function (virtualized network function, VNF).
  • VNF virtualized network function
  • VNFV network function virtualization
  • ETSI European Telecommunications Standards Institute
  • ASD application service descriptor
  • VNFD template and the ASD template are mutually incompatible NFV templates.
  • the implementation of containerized VNFs needs to choose between two incompatible templates, which will not only increase the complexity of containerized VNF implementations, but also increase the cost of containerized VNFs. Deployment complexity.
  • the present application provides a VNF instantiation method and device, which are used to flexibly implement VNF instantiation, meet various deployment requirements of VNF, and reduce the complexity of VNF deployment.
  • the present application provides a VNF instantiation method, which may include: a virtualized network function manager (virtualized network function manager, VNFM) receiving a network function virtualization orchestrator (network function virtualization orchestrator, NFVO After the instantiation request of the VNF of ), determine the deployment unit in the first NFV template according to the first information included in the instantiation request of the VNF, and then instantiate the VNF according to the deployment unit, wherein the The first information is used to indicate the deployment mode of the VNF.
  • VNFM virtualized network function manager
  • NFVO network function virtualization orchestrator
  • VNFM can flexibly determine the NFV template that meets the requirements according to the information used to indicate the deployment mode of the VNF, thereby flexibly realizing the instantiation of the VNF and meeting the different deployment requirements of the VNF, such as virtual machines, virtual machine containers or bare metal Containers, etc., reduce the complexity of VNF deployment.
  • the first NFV template may include a metadata (metadata) unit
  • the metadata unit may include a first attribute
  • the first attribute may be used to indicate the deployment mode of the VNF and the configuration of the deployment unit. Combination correspondence.
  • the deployment unit to be used when the VNF is instantiated can be determined through the first attribute.
  • the VNFM determines the part of the first NFV template according to the first information
  • the VNFM may determine, according to the first information, the combination of the deployment units indicated by the first attribute in the first NFV template, the combination of the deployment units and the combination of the deployment units indicated by the first information Corresponds to the above VNF deployment methods.
  • the VNFM can determine the combination of deployment units corresponding to the VNF deployment mode indicated by the first information through the correspondence between the VNF deployment mode indicated by the first attribute and the combination of deployment units, so as to meet the deployment requirements of the VNF .
  • the VNFM when the VNFM determines the deployment units in the first NFV template according to the first information, the VNFM can determine the deployment units in the first NFV template that are indicated by the first information. Combinations of deployment units corresponding to the above VNF deployment modes. In this way, the VNFM may directly determine the combination of deployment units corresponding to the deployment mode of the VNF indicated by the first information according to the correspondence between the deployment mode of the VNF and the combination of the deployment units.
  • the deployment unit in the first NFV template may include one or more of the following units: a virtualization deployment unit (virtualization deployment unit, VDU ) in virtual computing description, VNF external connection point descriptor, virtual link descriptor (virtualization link descriptor, VLD) or deployment flavor (deployment flavor, DF).
  • VDU virtualization deployment unit
  • VLD virtual link descriptor
  • deployment flavor deployment flavor
  • the deployment unit in the first NFV template may include one or more of the following units: container description in VDU, VNF external connection point descriptor, VLD or DF.
  • container description in VDU VNF external connection point descriptor
  • VLD VNF external connection point descriptor
  • DF DF
  • the deployment unit in the first NFV template may include one or more of the following units: information of the second NFV template, VNF external connection One or more container object package files referenced by the point descriptor or information of the second NFV template.
  • the information of the second NFV template may be an ASD, and the ASD includes enhanced cluster capability attributes and deployment item attributes.
  • the first NFV template can be integrated with ASD information, thereby reducing the complexity of VNF instantiation of bare-metal containers, and at the same time, it can solve the existing VNFD template information while retaining the authorization requirements of NFVO to centrally manage and control VNF resource management and orchestration
  • CaaS management flexibly arranges container objects according to the Helm package, and completes the contradiction between the requirements for autonomous management of object resources in the cluster in a closed loop.
  • the container object package file may be a Helm chart.
  • the present application provides a VNF instantiation method, which may include: NFVO determines first information, and sends a VNF instantiation request containing the first information to VNFM, and the first information may It is used to indicate the deployment mode of the VNF; the first information may be used to determine a deployment unit in the first network function virtualization NFV template, and the deployment unit may be used to instantiate the VNF.
  • the VNFM can flexibly determine the NFV template that meets the requirements according to the information used to indicate the deployment mode of the VNF, so as to flexibly realize the instantiation of the VNF and meet the different deployment requirements of the VNF, such as virtual machines, virtual machine containers, or Bare metal containers, etc., reduce the complexity of VNF deployment.
  • the first NFV template may include a metadata unit
  • the metadata unit may include a first attribute
  • the first attribute may be used to indicate a combination of a VNF deployment mode and a deployment unit relation.
  • the first information is used to determine the deployment unit in the first NFV template, and may include: the first information is used to determine the first attribute indication in the first NFV template A combination of deployment units, where the combination of deployment units corresponds to the deployment manner of the VNF indicated by the first information.
  • the VNFM can determine the combination of deployment units corresponding to the VNF deployment mode indicated by the first information through the corresponding relationship between the VNF deployment mode indicated by the first attribute and the combination of deployment units, so as to meet the VNF deployment requirements. need.
  • the first information is used to determine the deployment unit in the first NFV template, which may include: the first information is used to determine the A combination of deployment units corresponding to the indicated deployment mode of the VNF.
  • the VNFM can directly determine the combination of deployment units corresponding to the deployment mode of the VNF indicated by the first information according to the correspondence between the deployment mode of the VNF and the combination of the deployment units.
  • the deployment unit in the first NFV template may include one or more of the following units: virtual computing description in VDU, VNF external connection Point Descriptor, VLD or Deployment Style DF.
  • VDU virtual computing description in VDU
  • VNF external connection Point Descriptor VLD
  • Deployment Style DF Deployment Style DF
  • the deployment unit in the first NFV template may include one or more of the following units: container description in VDU, VNF external connection point descriptor, VLD or DF.
  • container description in VDU VNF external connection point descriptor
  • VLD VNF external connection point descriptor
  • DF DF
  • the deployment unit in the first NFV template may include one or more of the following units: information of the second NFV template, VNF external connection One or more container object package files referenced by the point descriptor or information of the second NFV template.
  • the information of the second NFV template is an application service descriptor (ASD), and the ASD includes enhanced cluster capability attributes and deployment item attributes.
  • ASD application service descriptor
  • the first NFV template can be integrated with ASD information, thereby reducing the complexity of VNF instantiation of bare-metal containers, and at the same time, it can solve the existing VNFD template information while retaining the authorization requirements of NFVO to centrally manage and control VNF resource management and orchestration
  • CaaS management flexibly arranges container objects according to the Helm package, and completes the contradiction between the requirements for autonomous management of object resources in the cluster in a closed loop.
  • the container object package file may be a Helm chart.
  • the present application also provides a device for VNF instantiation, the VNF instantiation device may be a VNFM, and the VNF instantiation device has various possible design examples for realizing the above first aspect or the first aspect function in the method.
  • the functions described above may be implemented by hardware, or may be implemented by executing corresponding software on the hardware.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • the structure of the device instantiated by the VNF includes a communication module and a processing module, and these units can perform corresponding functions in the above-mentioned first aspect or in each possible design example of the first aspect, for details, refer to the method The detailed description in the example is not repeated here.
  • the structure of the device instantiated by the VNF includes a communication interface and a processor, and optionally also includes a memory
  • the communication interface is used to send and receive information or data, and is used to communicate with the The other devices communicate and interact
  • the processor is configured to support the device instantiated by the VNF to execute corresponding functions in the first aspect or in each possible design example of the first aspect.
  • the memory is coupled to the processor, which holds Necessary program instructions and data for devices instantiated by the VNF.
  • the present application also provides a VNF instantiation device, the VNF instantiation device may be NFVO, and the VNF instantiation device has various possible design examples for realizing the above second aspect or the second aspect function in the method.
  • the functions described above may be implemented by hardware, or may be implemented by executing corresponding software on the hardware.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • the structure of the device instantiated by the VNF includes a communication module and a processing module, and these units can perform the corresponding functions in the above second aspect or in each possible design example of the second aspect, for details, refer to the method The detailed description in the example is not repeated here.
  • the structure of the device instantiated by the VNF includes a communication interface and a processor, and optionally also includes a memory
  • the communication interface is used to send and receive information or data, and is used to communicate with the The other devices communicate and interact
  • the processor is configured to support the device instantiated by the VNF to perform corresponding functions in the above second aspect or in each possible design example of the second aspect.
  • the memory is coupled to the processor, and stores necessary program instructions and data for devices instantiated by the VNF.
  • the embodiment of the present application provides a communication system, which may include the VNFM in the above third aspect and the NFVO in the above fourth aspect.
  • the embodiments of the present application provide a computer-readable storage medium, the computer-readable storage medium stores program instructions, and when the program instructions are run on the computer, the computer executes the first aspect and its In any possible design, or the method described in the second aspect and any possible design thereof.
  • Exemplary, computer readable storage media may be any available media that can be accessed by a computer.
  • computer readable media may include non-transitory computer readable media, random-access memory (random-access memory, RAM), read-only memory (read-only memory, ROM), electrically erasable Except for electrically programmable read-only memory (electrically EPROM, EEPROM), CD-ROM or other optical disk storage, magnetic disk storage medium or other magnetic storage device, or can be used to carry or store the desired program code in the form of instruction or data structure and can Any other media accessed by a computer.
  • random-access memory random-access memory
  • read-only memory read-only memory
  • ROM read-only memory
  • the embodiment of the present application provides a computer program product, including computer program codes or instructions, when the computer program codes or instructions are run on a computer, making any possible design of the first aspect or the first aspect , or the method described in the above second aspect or any possible design of the second aspect is executed.
  • the present application also provides a chip, including a processor, the processor is coupled to a memory, and is used to read and execute program instructions stored in the memory, so that the chip realizes the above first aspect Or any possible design of the first aspect, or the method described in the above second aspect or any possible design of the second aspect.
  • FIG. 1 is a schematic diagram of a NFV reference architecture provided by the present application.
  • FIG. 2 is a schematic diagram of an example of a CaaS technology provided by the present application.
  • FIG. 3 is a schematic diagram of two NFV templates supporting containerized VNF provided by the present application.
  • FIG. 4 is a schematic flowchart of a method for instantiating a VNF provided by the present application
  • FIG. 5 is a schematic diagram of the top-level structure of a first NFV template provided by the present application.
  • Fig. 6 is a schematic diagram of an example of the corresponding relationship between the VNF deployment mode indicated by the first attribute and the combination of the deployment unit provided by the present application;
  • FIG. 7 is a schematic structural diagram of a VNF instantiation device provided by the present application.
  • FIG. 8 is a structural diagram of a device for instantiating a VNF provided by the present application.
  • Embodiments of the present application provide a method and device for VNF instantiation, which are used to flexibly implement VNF instantiation and meet various deployment requirements of VNF.
  • the method and the device described in this application are based on the same technical concept. Since the principles of the method and the device to solve the problem are similar, the implementation of the device and the method can be referred to each other, and the repetition will not be repeated.
  • NFV refers to telecom network operators drawing on virtualization technology in the field of information technology (IT), decoupling the software and hardware of telecom network functions, and deploying low-cost hardware such as general-purpose servers, switches and memories. The technology to deploy and run some telecom network functions on the equipment.
  • Container as a service refers to decomposing a VNF into multiple container services.
  • the container service can be directly invoked by the VNF, or can be invoked by the public service or proprietary service invoked by the VNF, and then Assemble to form a containerized VNF, and realize the management of the containerized VNF through the management of the life cycle of the container service.
  • Virtual machine container refers to a type of container service built on virtual machine resources. Usually, virtual machine resources form the nodes in the cluster where the container service runs.
  • Bare metal container refers to a type of container service built on bare metal resources (host or bare metal resources). Usually, bare metal resources constitute the nodes in the cluster where the container service runs.
  • Multiple (individual, species) in the embodiment of the application refers to two (individual, species) or more than two (individual, species), in view of this, in the embodiment of the application, "multiple ( Individual, species)” is understood as "at least two items (individual, species)”. "At least one item (individuals, species)” can be understood as one item (individuals, species) or multiple items (individuals, species), such as one item (individuals, species), two items (individuals, species) or more Multiple items (a, species).
  • including at least one item means including one item (individuals, species), two items (individuals, species) or more items (individuals, species), and does not limit which items are included ( Individuals, species), for example, including at least one of A, B or C (individuals, species), then included may be A, B, C, A and B, A and C, B and C, or A and B and C.
  • a and/or B may indicate: A exists alone, A and B exist simultaneously, and B exists independently.
  • the character "/" unless otherwise specified, generally indicates that the associated objects before and after are in an "or" relationship.
  • Fig. 1 shows a schematic diagram of a NFV reference architecture.
  • the NFV reference architecture can implement various types of communication networks, such as local area network (local area network, LAN), Internet protocol (internet protocol, IP) network or evolved packet core network (evolved packet core, EPC) network, etc.
  • local area network local area network
  • IP Internet protocol
  • EPC evolved packet core network
  • the NFV reference architecture may include an NFV management and orchestration system (NFV management and orchestration system, NFV-MANO) 110, one or more operation support systems/business support systems (operation support system/business support system, OSS/BSS) 120, multiple network element managers (element manager, EM) 130, multiple VNFs 140, and NFV infrastructure (NFV infrastructure, NFVI) 150.
  • NFV management and orchestration system NFV-MANO
  • operation support systems/business support systems operation support system/business support system, OSS/BSS
  • EM network element managers
  • VNFs 140 multiple VNFs 140
  • NFV infrastructure NFV infrastructure
  • the NFV-MANO 110 may include an NFV orchestrator (NFV orchestrator, NFVO) 111, one or more VNF managers (VNF manager, VNFM) 112, and a virtualized infrastructure manager (virtualized infrastructure manager, VIM) 113.
  • NFV orchestrator NFV orchestrator, NFVO
  • VNF manager VNFM
  • VIM virtualized infrastructure manager
  • NFVO 111 can be used to implement network service descriptor (network service descriptor, NSD), virtual network function forwarding graph (VNF forwarding graph, VNFFG) management and processing, network service life cycle management, and, in cooperation with VNFM VNF life cycle management and global view function of virtual resources.
  • network service descriptor network service descriptor, NSD
  • VNF forwarding graph VNFFG
  • VNFM virtual network function forwarding graph
  • VNFM 112 can realize the lifecycle management of VNF, including the management of virtualized network function descriptor (VNF descriptor, VNFD), the instantiation of VNF, and the elastic scaling of VNF instances (including scaling out/up and scaling in/down)), the healing of the VNF instance, and the termination of the VNF instance.
  • VNFM 112 can also support receiving the elastic scaling (scaling) policy issued by the NFVO to realize automatic VNF elastic scaling.
  • VIM 113 is mainly responsible for infrastructure layer hardware resources, management of virtualized resources (including reservation and allocation), monitoring of virtual resource status and fault reporting, and providing virtualized resource pools for upper-layer applications.
  • OSS/BSS 120 is mainly for telecom service operators, providing comprehensive network management and business operation functions, including network management (such as fault monitoring, network information collection, etc.), billing management, and customer service management.
  • network management such as fault monitoring, network information collection, etc.
  • billing management billing management
  • customer service management customer service management
  • the EM 130 is used to perform traditional fault, configuration, user, performance and security management (fault management, configuration management, account management, performance management, security management, FCAPS) functions for the VNF.
  • fault management configuration management, account management, performance management, security management, FCAPS
  • the VNF 140 corresponds to a physical network function (physical network function, PNF) in a traditional non-virtualized network, such as a virtualized packet core network (evolved packet core, EPC) node (for example, a mobility management entity (mobility management entity, MME ), serving gateway (serving gateway, SGW), public data network gateway (public data network gateway, PGW) etc.).
  • EPC virtualized packet core network
  • MME mobility management entity
  • serving gateway serving gateway
  • public data network gateway public data network gateway
  • the VNF 140 may be composed of one or more lower functional level VNF components (VNF component, VNFC). Therefore, a VNF can be deployed on multiple virtual machines (virtual machines, VMs), each VM bears the function of a VNFC, and a VNF can also be deployed on a VM.
  • VNF component VNF component
  • NFVI 150 may include a virtual resource layer, a virtualization layer, and a hardware resource layer.
  • the virtual resource layer may include multiple VMs, or may also include virtual storage, virtual network, etc. (not shown in FIG. 1 ).
  • the hardware resource layer may include computing hardware, storage hardware, and network hardware (not shown in FIG. 1 ).
  • the hardware in the hardware resource layer may include a dedicated processor or a general-purpose processor for providing processing and computing functions, such as a central processing unit (central process unit, CPU), and a device for providing storage capabilities, such as a disk or network attached storage (NAS); and, switches, routers, and/or other network devices.
  • a dedicated processor or a general-purpose processor for providing processing and computing functions such as a central processing unit (central process unit, CPU), and a device for providing storage capabilities, such as a disk or network attached storage (NAS); and, switches, routers, and/or other network devices.
  • the virtual resource layer can be provided to the VNF 140 in the form of a virtual machine, for example, one or more virtual machines form a VNF 140.
  • the virtualization layer forms a virtual network through hardware in the hardware resource layer, and is used to realize communication between multiple virtual machines.
  • the virtual network can be virtualized through a virtual local area network (virtual local area network, VLAN), a virtual private LAN service (virtual private LAN service, VPLS), a virtual extensible local area network (virtual extensible local area network, VxLAN) or a general routing encapsulation network.
  • VLAN virtual local area network
  • VPLS virtual private LAN service
  • VxLAN virtual extensible local area network
  • NVGRE network virtualization using generic routing encapsulation, NVGRE
  • the virtualization layer in NFVI 150 is used to abstract the hardware resources of the hardware resource layer, and the VNF 140 and the hardware resources It decouples the physical layer of the attribute and provides virtual resources to the VNF.
  • NFV-MANO 110 can be used to realize the monitoring and management of VNF 140 and NFVI 150.
  • NFVO 111 can communicate with one or more VNFMs 112 to implement resource-related requests, send configuration information to VNFMs 112, and collect status information for VNFs 140.
  • the NFVO 111 can also communicate with the VIM 113 to implement resource allocation, and/or, implement reservation and exchange of configuration information and status information of virtualized hardware resources.
  • VNFM 112 may be used to manage one or more VNFs 140, performing various management functions, such as initializing, updating, querying, and/or terminating VNFs 140.
  • VIM 113 can be used to control and manage the interaction of virtual resources and hardware resources in VNF 140 and NFVI.
  • the VIM 113 can be used to perform resource allocation operations to the VNF 140.
  • VNFM 112 and VIM 113 can communicate with each other to exchange virtualized hardware resource configuration and status information.
  • CaaS technology is an operating system-level virtualization technology, through which different processes in the operating system are isolated, for example, the control group (control groups, CGroup) mechanism or namespace (name space) under the Linux operating system mechanism etc. Since CaaS technology has no virtual hardware, no operating system, but only processes, CaaS technology is lighter and more convenient to manage than NFV technology.
  • FIG. 2 shows an example of a CaaS technology, an architecture diagram of a kubernetes (K8S) container management and orchestration system.
  • K8S kubernetes
  • Kubernetes divides the devices in the cluster into a kubernetes master node (master node) and a group of working nodes (working nodes).
  • master node master node
  • working nodes working nodes
  • a group of processes related to cluster management are running on the master node, such as application programming interface server (application programming interface server, API server), replication controller (replication controller, RC), etc.
  • Management functions such as resource management, pod scheduling, elastic scaling, security control, system monitoring, and error correction.
  • a pod can include at least one container, and a pod can be understood as a container cabin composed of one or more containers.
  • API Server provides the only operation entry for resource objects, and all other components must operate resource data through the API interface it provides, and complete relevant business functions through "full query” and “change monitoring” of related resource data .
  • the controller manager is the management control center of the cluster, and its main purpose is to realize the automation of fault detection and recovery of the kubernetes cluster. For example, pod replication or removal can be completed according to the definition of RC to ensure that the number of pod instances conforms to the definition of RC. According to the management relationship between service (service) and pod, the creation and update of service endpoint (endpoints) objects can be completed, node Discovery, management and status monitoring, as well as cleaning of locally cached image files, etc.
  • the kubelet component is responsible for the creation, modification, monitoring, and deletion of pods on the node and other life cycle management. At the same time, Kubelet regularly reports the status information of the node to the API Server.
  • the proxy component is used to implement service proxy and load balancing in software mode.
  • the docker component is the running environment of the container.
  • VNF 140 can be composed of one or more container objects, a container object can be understood as a pod in Figure 2, and each pod can be deployed in a container cluster node resource pool, each container cluster node resource pool
  • the resource of can be a virtual machine (virtual machine, VM) or a bare metal (bare metal) server, and each VM hosts one or more container objects.
  • VM virtual machine
  • bare metal bare metal
  • NFV-MANO 110 may also include container infrastructure service management (container infrastructure service management, CISM), container cluster management (container cluster management, CCM) (not shown in FIG. 1 ).
  • container infrastructure service management container infrastructure service management, CISM
  • container cluster management container cluster management, CCM
  • CISM can also be called CaaS management, which is responsible for managing container objects called by VNF, including the creation, update and deletion of container objects, and dispatching container objects to corresponding VMs in the container cluster node resource pool managed by it.
  • the node resources include computing resources, storage resources, and network resources.
  • the corresponding concept of the container object in the ETSI standard is the managed container infrastructure object (managed container infrastructure object, MCIO).
  • the CCM is responsible for managing the container cluster, including the creation of the node resource pool used by the container cluster and the expansion or contraction of the node resource pool.
  • a container cluster is a collection of a management node (for example, the Kubernetes Master in Figure 2) and a series of worker nodes (for example, the nodes in Figure 2).
  • a container cluster is a dynamic system in which multiple containers can be deployed, and the status of these containers and the communication between containers can be monitored by the monitoring and management system.
  • the corresponding concept of container cluster in ETSI standard is container infrastructure service cluster (container infrastructure service cluster, CIS Cluster).
  • CISM and CCM provide NFVO or VNFM with management services to invoke their functions on the northbound interface.
  • the VNF When instantiating the VNF, the VNF needs to be instantiated according to the information description in the NFV template (also called NFV model, NFV template model, etc.).
  • NFV template also called NFV model, NFV template model, etc.
  • VNFD template defined by the ETSI NFV industry standard group
  • ASD template defined by ONAP
  • Both the VNFD template and the ASD template refer to the container object package (such as: Helm) file defined by the open source community, where the container object package is composed of description template files of one or more container objects, and these container objects are referenced by VNF .
  • the container object package such as: Helm
  • both the VNFD template and the Helm package file contain infrastructure resources (also called NFVI resources, including computing resources, storage resources, and network resources), that is to say, the infrastructure defined by the VNFD template and the Helm package file There is redundancy in resources.
  • VNFD defines the resource requirements consumed by the VNF during the life cycle management process
  • the Helm package defines the resource requirements consumed by one or more container objects referenced by the VNF in the management orchestration.
  • the resource definition of VNFD is used to support the resource authorization (granting) operation in the VNF life cycle management process, and the resource definition in the Helm package is used to deploy the container VNF.
  • the task of parsing the container object description template in the Helm package is not completed by NFVO or VNFM, but is handed over to the lower-level container management platform (also known as CaaS management or CISM).
  • the VNFD template has great limitations when supporting containerized VNF deployment.
  • the NFVI resource information used by the VNF is defined in two layers in the VNFD template and the Helm package, which may lead to container management and orchestration of upstream and downstream resource information. Synchronization is difficult, and it is difficult to maintain consistent resource data;
  • NFVO performs resource authorization from the perspective of the overall resource view of the management domain, which will inhibit the cloud-native design principles adopted by containerized VNFs.
  • Cloud-native design principles usually allow CaaS management to autonomously complete the resource expansion and contraction or self-healing process of container objects within a certain resource range, without the need for resource authorization by NFVO for each operation. NFVO also cannot keep up with the rapid changes of container layer resources in time.
  • the ONAP ASD template there is no repeated description of resource information between ASD and Helm packages, and the task of parsing the container object description template in the Helm package can be completed by the upper-layer service orchestrator (SO).
  • SO upper-layer service orchestrator
  • the ASD template and the VNFD template form container VNF templates that are incompatible with each other. If it is necessary to implement the container VNF instantiated by the two templates in the same network operating environment, only the VNFD and ASD branch models can be included in the NSD. This brings inconvenience to template selection for the deployment of containerized VNF, which not only increases the complexity of containerized VNF implementation, but also increases the complexity of containerized VNF deployment.
  • the embodiment of the present application proposes a VNF instantiation method and device, which can flexibly implement VNF instantiation by using a fused VNFD template, so as to meet various deployment requirements of VNF and reduce the complexity of VNF deployment.
  • the embodiment of the present application takes the fusion of VNFD templates and ASD templates as an example for introduction, and this application can also be applied to the fusion of VNFD templates and other templates used for VNF instantiation, and this application can also be applied to the fusion of other various
  • the template used for VNF instantiation is not limited in this application.
  • Fig. 4 shows a method for instantiating a VNF provided in the embodiment of the present application. As shown in Fig. 4, the specific process of the method may include:
  • Step 401 The NFVO determines the first information, and sends a VNF instantiation request to the VNFM, the VNF instantiation request includes the first information, and the first information is used to indicate the deployment mode of the VNF.
  • the first information may be a virtual machine, a virtual machine container, or a bare metal container, which means that the deployment mode of the VNF is a virtual machine, a virtual machine container, or a bare metal container.
  • the deployment mode of the VNF can also be understood as the deployment form of the VNF, that is, the implementation form of the VNF deployment in the network.
  • the VNF instantiation request may also include the VNF instance identifier, so that the NFVO determines the first NFV template to be accessed according to the VNF instance identifier.
  • the determination of the first information by the NFVO may be implemented internally by the NFVO.
  • Step 402 The VNFM determines the deployment unit in the first NFV template according to the first information, that is, the first information is used to determine the deployment unit in the first NFV template.
  • the first NFV template may be a fused VNFD template, for example, information of the second NFV template may be fused on the basis of the current VNFD template, so as to solve the problem that the information of the existing VNFD template does not support NFVO.
  • the second NFV template may be an ASD template, an edge application description template (for example, an application descriptor (application descriptor, APPD), etc.), or other templates, etc., which are not limited in this application.
  • an edge application description template for example, an application descriptor (application descriptor, APPD), etc.
  • other templates etc., which are not limited in this application.
  • the first NFV template includes a metadata (metadata) unit
  • the metadata unit includes VNF-related information, for example, identification information, version, provider, description information, etc. of the first NFV template.
  • the metadata unit may include a first attribute, and the first attribute is used to indicate a correspondence between a VNF deployment mode and a combination of deployment units. That is, the first attribute indicates a combination of deployment units that the VNF needs to use in different deployment modes.
  • the first attribute may be a deployment unit selection ((deployment unit, DU) selection) attribute.
  • the first attribute may also have other names, which are not limited in this application.
  • the first NFV template may also include one or more optional deployment units.
  • the VNFM may determine the first NFV template used to instantiate the VNF according to the first information. deployment unit. For example, the VNFM can select a combination of deployment units corresponding to the first information from one or more selectable deployment units according to the first information (the combination of deployment units corresponding to the first information can be understood as the combination of the VNF indicated by the first information. combination of deployment units in the first NFV template corresponding to the deployment mode). That is, according to different parts of the VNF Combine optional deployment units according to deployment requirements.
  • the VNFM determines the deployment unit in the first NFV template according to the first information, which may be implemented in the following two ways:
  • the VNFM determines a combination of deployment units indicated by the first attribute in the first NFV template according to the first information, The combination of the deployment units corresponds to the deployment manner of the VNF indicated by the first information.
  • the VNFM may determine a combination of deployment units corresponding to the deployment manner indicated by the first information according to the first attribute, so as to meet the deployment requirements of the VNF.
  • the VNFM determines a combination of deployment units in the first NFV template corresponding to the VNF deployment mode indicated by the first information.
  • the corresponding relationship between the deployment mode of the VNF and the combination of the deployment unit may be determined in advance, instead of defining this corresponding relationship in the first NFV template. Therefore, the VNFM can directly determine the combination of deployment units corresponding to the deployment manner of the VNF indicated by the first information.
  • the top-level structure of the first NFV template may be as shown in FIG. 5 .
  • the optional deployment unit included in the first NFV template may include one or more of the following units: virtualization deployment unit (virtualization deployment unit, VDU), VNF external connection point descriptor (external connection point descriptor , ExtCpd), virtual link descriptor (virtualization link descriptor, VLD), deployment style (deployment flavor, DF), second template information (such as ASD), one or more container object package files, container object package files contain One or more container object (eg MCIO) templates.
  • the container object package file can be a Helm chart (Helm chart).
  • the ASD unit may contain information elements not included in the existing VNFD in the open source community model such as ONAP ASD, for example, the ASD may include enhanced cluster capability attributes (enhancedClusterCapabilities ) and/or deployment item properties (deploymentItem).
  • the information in the metadata unit in the ONAP ASD template can be combined with the information in the existing VNFD metadata unit to obtain the metadata unit in the first NFV template, the asdExtCpd unit in the ONAP ASD template and the existing VNFD ExtCpd unit Merge to obtain the optional deployment unit ExtCpd in the first NFV template.
  • the VDU can be used to describe the deployment information of the VNFC and the management information of the life cycle management of the VNFC in the running state.
  • the VNF external connection point descriptor (ExtCpd) can be used to describe the configuration information of the VNF external connection point.
  • the VLD can be used to describe the configuration information of the virtual link used by the VNF.
  • DF can be used to describe resource combination information of VNF deployed in different network topologies.
  • the VNFM determines the deployment unit in the first NFV template according to the first information, it can select the A combination of deployment units conforming to the deployment manner indicated by the first information is selected from the deployment units.
  • the following three examples may be included:
  • the deployment unit in the first NFV template may include one or more of the following units: virtual computing description (virtualComputeDesc) in VDU, VNF external connection point Descriptor, VLD or DF.
  • virtualComputeDesc virtualComputeDesc
  • the deployment unit in the first NFV template may include one or more of the following units: container description (OSContainerDesc) in the VDU, VNF external connection point Descriptor, VLD or DF.
  • container description OSContainerDesc
  • VNF external connection point Descriptor VLD
  • DF DF
  • NFVO and VNFM can still perform centralized management and control of resources for each VNF life cycle management (life cycle management, LCM) operation through the existing resource granting process.
  • VNF life cycle management life cycle management, LCM
  • the deployment unit in the first NFV template may include one or more of the following units: information of the second NFV template, VNF external connection point descriptor, or One or more container object package files referenced by the information of the second NFV template.
  • the information of the second NFV template may be an ASD, and the ASD may include enhanced cluster capability attributes and deployment item attributes.
  • the container object package file may be a Helm chart.
  • NFVO when the information of the second NFV template is ASD, NFVO can no longer authorize resources for each VNF LCM operation, and resource management in VNF LCM operations can depend on VNFM’s control of the container in the Helm package
  • VNFM VNFM
  • the information analysis of the object template forms the number of resources required for each VNF LCM operation through the statistics of the resource definition in the container object template, and reports the resource usage information formed from bottom to top to NFVO as needed.
  • the information of the existing VNFD templates can be preserved, and the authorization requirements for NFVO to centrally manage and control the VNF resource management and orchestration can be retained, and the CaaS management can flexibly arrange container objects according to the Helm package during the VNF cloud-native evolution process, and complete object resource autonomy in the cluster in a closed loop. Manage conflicts between requirements.
  • VNFM should have the ability to parse container object package files (such as Helm Chart).
  • the metadata unit does not include the first attribute
  • the predefined or pre-configured correspondence between the combination of the first information and the deployment unit that is, the correspondence between the deployment mode and the combination of the deployment unit
  • the correspondence between the deployment mode and the combination of the deployment unit For an example of the relationship, reference may also be made to the description of the above-mentioned examples b1-b3, which will not be described in detail here.
  • Step 403 The VNFM instantiates the VNF according to the deployment unit, that is, the deployment unit is used to instantiate the VNF.
  • the interaction between the VNFM and the NFVO determines the VNF
  • the resource management in the instantiation performs granting, and then the VNFM initiates a VM allocation operation to the VIM.
  • the VNFM parses the container object package file (such as Helm Chart) referenced by the information of the second template in the deployment unit (such as the ASD unit)
  • the container object in describes the template, and initiates the process of creating a container object (such as: MCIO) or reusing an existing container object to the CaaS management.
  • the VNFM completes the related configuration of the VNF instance information, and then the VNFM sends a VNF instantiation response message to the NFVO.
  • the VNFM can flexibly determine the NFV template that meets the requirements according to the information used to indicate the deployment mode of the VNF, thereby flexibly realizing the instantiation of the VNF and meeting different deployment requirements of the VNF.
  • each scheme of the VNF instantiation method provided in the embodiments of the present application is introduced from the perspectives of each functional module or device itself and the interaction between each functional module or device.
  • each functional module or device such as the above-mentioned VNFM and NFVO, includes a corresponding hardware structure and/or software module for performing each function in order to realize the above-mentioned functions.
  • the application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software drives hardware depends on the specific application and design constraints of the technical solution. Skilled artisans may use different methods to implement the described functions for each specific application, but such implementation should not be regarded as exceeding the scope of the present application.
  • an apparatus 700 for VNF instantiation may include a communication module 701 and a processing module 702 .
  • the communication module 701 is used for the VNF instantiation device 700 to receive information (message or data) and/or send information (message or data)
  • the processing module 702 is used for the VNF instantiation device 700 700 actions for control and management.
  • the processing module 702 may also control the steps executed by the communication module 701 .
  • the VNF instantiation apparatus 700 may specifically be the VNFM in the above embodiment, a processor in the VNFM, or a chip, or a chip system, or a functional module, etc.; or, the VNF instantiation The apparatus 700 may specifically be the NFVO in the foregoing embodiments, a processor of the NFVO, or a chip, or a chip system, or a functional module, and the like.
  • the VNF instantiation apparatus 700 when used to realize the function of the VNFM in the embodiment described in FIG. 4 above, it may include: the communication module 701 is used to receive the VNF instantiation request from the NFVO , the instantiation request of the VNF includes first information, the first information is used to indicate the deployment mode of the VNF; the processing module 702 is configured to determine the first network function virtualization NFV according to the first information a deployment unit in the template, and instantiate the VNF according to the deployment unit.
  • the first NFV template may include a metadata unit, and the metadata unit may include a first attribute, and the first attribute is used to indicate a combination of a VNF deployment mode and a deployment unit corresponding relationship.
  • the processing module 702 when the processing module 702 determines the deployment units in the first NFV template according to the first information, it may be configured to: determine the deployment units in the first NFV template according to the first information A combination of deployment units indicated by the first attribute, where the combination of deployment units corresponds to the deployment manner of the VNF indicated by the first information.
  • the processing module 702 when the processing module 702 determines the deployment unit in the first NFV template according to the first information, it may be configured to: determine that the first NFV template is related to the first information indication A combination of deployment units corresponding to the deployment manner of the VNF.
  • the deployment unit in the first NFV template may include one or more of the following units: virtual computing description in VDU, VNF external Junction point descriptor, VLD or DF.
  • the deployment unit in the first NFV template may include one or more of the following units: container description in VDU, VNF External join point descriptor, VLD or DF.
  • the deployment unit in the first NFV template may include one or more of the following units: information of the second NFV template, VNF One or more container object package files referenced by the external join point descriptor or information of the second NFV template.
  • the information of the second NFV template may be an ASD, and the ASD includes enhanced cluster capability attributes and deployment item attributes.
  • the container object package file may be a Helm chart.
  • the VNF instantiation apparatus 700 when used to realize the function of NFVO in the embodiment described in FIG. 4 , it may include: the processing module 702 may be used to determine the first information, the The first information is used to indicate the deployment mode of the VNF; the first information is used to determine the deployment unit in the first network function virtualization NFV template, and the deployment unit is used to instantiate the VNF; the communication module 701 may It is used to send the instantiation request of the VNF to the virtualized network function manager VNFM, where the instantiation request of the VNF includes the first information.
  • the processing module 702 may be used to determine the first information, the The first information is used to indicate the deployment mode of the VNF; the first information is used to determine the deployment unit in the first network function virtualization NFV template, and the deployment unit is used to instantiate the VNF; the communication module 701 may It is used to send the instantiation request of the VNF to the virtualized network function manager VNFM, where the instantiation request of the VNF includes
  • the first NFV template may include a metadata unit, and the metadata unit may include a first attribute, and the first attribute is used to indicate a combination of a VNF deployment mode and a deployment unit corresponding relationship.
  • the first information is used to determine the deployment unit in the first NFV template, and may include: the first information is used to determine the deployment unit indicated by the first attribute in the first NFV template A combination of deployment units, where the combination of deployment units corresponds to the deployment manner of the VNF indicated by the first information.
  • the first information is used to determine the deployment unit in the first NFV template, which may include: the first information is used to determine whether the first NFV template is related to the first information A combination of deployment units corresponding to the indicated deployment mode of the VNF.
  • the deployment unit in the first NFV template may include one or more of the following units: virtual computing description in VDU, VNF External join point descriptor, VLD or DF.
  • the deployment unit in the first NFV template may include one or more of the following units: container description in the VDU, VNF external join point descriptor, VLD or DF.
  • the deployment unit in the first NFV template may include one or more of the following units: information about the second NFV template, One or more container object package files referenced by the VNF external connection point descriptor or the information of the second NFV template.
  • the information of the second NFV template may be an ASD, and the ASD includes enhanced cluster capability attributes and deployment item attributes.
  • the container object package file may be a Helm chart.
  • each functional unit in the embodiment of the present application may be integrated into one processing unit, each unit may exist separately physically, or two or more units may be integrated into one unit.
  • the above-mentioned integrated units can be implemented in the form of hardware or in the form of software functional units.
  • the integrated unit is realized in the form of a software function unit and sold or used as an independent product, it can be stored in a computer-readable storage medium.
  • the technical solution of the present application is essentially or part of the contribution to the prior art 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 several instructions to make a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor (processor) execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (read-only memory, ROM), random access memory (random access memory, RAM), magnetic disk or optical disc and other media that can store program codes. .
  • an apparatus 800 for VNF instantiation may include a communication interface 801 and a processor 802 .
  • the apparatus 800 for VNF instantiation may further include a memory 803 .
  • the processor 802 may be a central processing unit (central processing unit, CPU), a network processor (network processor, NP) or a combination of CPU and NP.
  • the processor 802 may further include a hardware chip.
  • the aforementioned hardware chip may be an application-specific integrated circuit (application-specific integrated circuit, ASIC), a programmable logic device (programmable logic device, PLD) or a combination thereof.
  • the aforementioned PLD may be a complex programmable logic device (complex programmable logic device, CPLD), a field-programmable gate array (field-programmable gate array, FPGA), a general array logic (generic array logic, GAL) or any combination thereof.
  • the communication interface 801 , the processor 802 and the memory 803 are connected to each other.
  • the communication interface 801, the processor 802 and the memory 803 are connected to each other through a bus 804;
  • the bus 804 may be a Peripheral Component Interconnect (PCI) bus or an extended industry standard Structure (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 and so on. For ease of representation, only one thick line is used in FIG. 8 , but it does not mean that there is only one bus or one type of bus.
  • the memory 803 is used to store programs and the like.
  • the program may include program code including computer operation instructions.
  • the memory 803 may include RAM, and may also include non-volatile memory (non-volatile memory), such as one or more disk memories.
  • the processor 802 executes the application program stored in the memory 803 to realize the above functions, thereby realizing the functions of the device 800 for VNF instantiation.
  • the VNF instantiation apparatus 800 may be the VNFM in the above embodiment; it may also be the NFVO in the above embodiment.
  • the communication interface 801 can realize the transceiving operation performed by the VNFM in the embodiment shown in FIG. 4 ;
  • the processor 802 may implement other operations performed by the VNFM in the embodiment shown in FIG. 4 except the transceiving operation.
  • the communication interface 801 can realize the transceiving operation performed by NFVO in the embodiment shown in FIG. 4 ;
  • the processor 802 may implement other operations performed by the NFVO in the embodiment shown in FIG. 4 except the transceiving operation.
  • the embodiments of the present application provide a network structure, and the network structure may include the VNFM and NFVO involved in the above embodiments.
  • the embodiment of the present application also provides a computer-readable storage medium, the computer-readable storage medium is used to store a computer program, and when the computer program is executed by a computer, the computer can realize the VNF instantiation provided by the above method embodiment method.
  • the embodiment of the present application also provides a computer program product, where the computer program product is used to store a computer program.
  • the computer program product is used to store a computer program.
  • the computer program When the computer program is executed by a computer, the computer can implement the VNF instantiation method provided by the above method embodiment.
  • the embodiment of the present application also provides a chip, including a processor, the processor is coupled with the memory, and is used to call the The program in the memory enables the chip to realize the VNF instantiation method provided by the method embodiment above.
  • the embodiment of the present application further provides a chip, the chip is coupled with a memory, and the chip is used to implement the method for VNF instantiation provided in the above method embodiment.
  • the 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 combining 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 capable of directing a computer or other programmable data processing apparatus to operate in a specific manner, such that the instructions stored in the computer-readable memory produce an article of manufacture comprising instruction means, the instructions
  • the device realizes the function specified in one or more procedures of the flowchart and/or one or more blocks of the 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)
  • Stored Programmes (AREA)

Abstract

一种虚拟网络功能VNF实例化的方法及装置，用以灵活实现VNF的实例化，满足VNF各种不同的部署需求，降低VNF部署的复杂度。VNFM接收来自NFVO的VNF的实例化请求后，根据VNF的实例化请求中包括的用于指示VNF的部署方式的第一信息，确定第一NFV模板中的部署单元，并根据确定的部署单元对VNF进行实例化。这样VNFM可以根据用于指示VNF的部署方式的信息灵活确定符合需求的NFV模板，从而灵活实现VNF的实例化，并可以满足VNF的不同部署需求，如虚拟机、虚拟机容器或裸机容器等，降低VNF部署的复杂度。

Description

一种虚拟网络功能VNF实例化的方法及装置
相关申请的交叉引用
本申请要求在2022年02月18日提交中国专利局、申请号为202210152182.9、申请名称为“一种虚拟网络功能VNF实例化的方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种虚拟网络功能(virtualised network function，VNF)实例化的方法及装置。
背景技术
容器化VNF的部署所依据的网络功能虚拟化(network function virtualization，NFV)模板存在多种。例如，在电信行业，存在两种NFV模板可以用于容器化VNF的部署，一种是欧洲电信标准协会(European telecommunications standards institute，ETSI)NFV行业标准组定义的虚拟网络功能描述(VNF descriptor，VNFD)模板，另一种是开放网络自动化平台(open network automation platform，ONAP)定义的应用服务描述符(application service descriptor，ASD)模板。
然而，VNFD模板和ASD模板是彼此互不兼容的NFV模板。目前在同一个网络运行环境中部署容器化VNF时，容器化VNF的实现需要在两个不兼容的模板之间选择，不仅会增加容器化VNF实现的复杂度，同时也会增加容器化VNF的部署复杂度。
发明内容
本申请提供一种VNF实例化的方法及装置，用以灵活实现VNF的实例化，满足VNF各种不同的部署需求，降低VNF部署的复杂度。
第一方面，本申请提供了一种VNF实例化的方法，该方法可以包括：虚拟化网络功能管理器(virtualised network function manager，VNFM)接收来自网络功能虚拟化编排器(network function virtualization orchestrator，NFVO)的VNF的实例化请求后，根据所述VNF的实例化请求中包括的第一信息确定第一NFV模板中的部署单元，之后根据所述部署单元对所述VNF进行实例化，其中，所述第一信息用于指示所述VNF的部署方式。
通过上述方法，VNFM可以根据用于指示VNF的部署方式的信息灵活确定符合需求的NFV模板，从而灵活实现VNF的实例化，并可以满足VNF的不同部署需求，如虚拟机、虚拟机容器或裸机容器等，降低VNF部署的复杂度。
在一个可能的设计中，所述第一NFV模板可以包括元数据(metadata)单元，所述元数据单元中可以包括第一属性，所述第一属性可以用于指示VNF部署方式与部署单元的组合的对应关系。这样，当元数据单元中包括第一属性时，可以通过第一属性确定VNF实例化时所需要使用的部署单元。
在一个可能的设计中，所述VNFM根据所述第一信息确定所述第一NFV模板中的部 署单元时，所述VNFM可以根据所述第一信息，确定所述第一NFV模板中所述第一属性指示的部署单元的组合，所述部署单元的组合与所述第一信息指示的所述VNF的部署方式对应。这样，所述VNFM可以通过第一属性指示的VNF部署方式与部署单元的组合的对应关系，确定与第一信息指示的所述VNF的部署方式对应的部署单元的组合，以满足VNF的部署需求。
在一个可能的设计中，所述VNFM根据所述第一信息确定所述第一NFV模板中的部署单元时，所述VNFM可以确定所述第一NFV模板中与所述第一信息指示的所述VNF的部署方式对应的部署单元的组合。这样，所述VNFM可以直接根据VNF的部署方式与部署单元的组合的对应关系，确定第一信息指示的所述VNF的部署方式对应的部署单元的组合。
在一个可能的设计中，当所述第一信息为虚拟机时，所述第一NFV模板中的所述部署单元可以包括以下一项或多项单元：虚拟化部署单元(virtualization deployment unit，VDU)中的虚拟计算描述、VNF外部连接点描述符、虚拟链路描述符(virtualization link descriptor，VLD)或部署风格(deployment flavor，DF)。这样可以准确地确定当VNF部署为虚拟机时，所需要使用的部署单元，以满足VNF的实例化需求。
在一个可能的设计中，当所述第一信息为虚拟机容器时，所述第一NFV模板中的所述部署单元可以包括以下一项或多项单元：VDU中的容器描述、VNF外部连接点描述符、VLD或DF。这样可以准确地确定当VNF部署为虚拟机容器时，所需要使用的部署单元，以满足VNF的实例化需求。
在一个可能的设计中，当所述第一信息为裸机容器时，所述第一NFV模板中的所述部署单元可以包括以下一项或多项单元：第二NFV模板的信息、VNF外部连接点描述符或第二NFV模板的信息引用的一个或多个容器对象包文件。这样可以准确地确定当VNF部署为裸机容器时，所需要使用的部署单元，以满足VNF的实例化需求。
在一个可能的设计中，所述第二NFV模板的信息可以为ASD，所述ASD包含增强的集群能力属性和部署项属性。这样，可以使第一NFV模板融合ASD的信息，从而降低裸机容器VNF的实例化的复杂度，同时可以解决现有的VNFD模板的信息在保留支持NFVO集中对VNF资源管理编排进行管控的授权需求和VNF云原生演进过程中CaaS管理根据Helm包灵活编排容器对象、闭环完成集群中对象资源自治管理需求之间的矛盾。
在一个可能的设计中，所述容器对象包文件可以是Helm图表。
第二方面，本申请提供了一种VNF实例化的方法，该方法可以包括：NFVO确定第一信息，并向VNFM发送包含所述第一信息的VNF的实例化请求，所述第一信息可以用于指示所述VNF的部署方式；所述第一信息可以用于确定第一网络功能虚拟化NFV模板中的部署单元，所述部署单元可以用于实例化所述VNF。
通过上述方法，可以时VNFM根据用于指示VNF的部署方式的信息灵活确定符合需求的NFV模板，从而灵活实现VNF的实例化，并可以满足VNF的不同部署需求，如虚拟机、虚拟机容器或裸机容器等，降低VNF部署的复杂度。
在一个可能的设计中，所述第一NFV模板可以包括元数据单元，所述元数据单元中可以包括第一属性，所述第一属性可以用于指示VNF部署方式与部署单元的组合的对应关系。这样，当元数据单元中包括第一属性时，可以通过第一属性确定VNF实例化时所需要使用的部署单元。
在一个可能的设计中，所述第一信息用于确定所述第一NFV模板中的部署单元，可以包括：所述第一信息用于确定所述第一NFV模板中所述第一属性指示的部署单元的组合，所述部署单元的组合与所述第一信息指示的所述VNF的部署方式对应。这样，可以使所述VNFM通过第一属性指示的VNF部署方式与部署单元的组合的对应关系，确定与第一信息指示的所述VNF的部署方式对应的部署单元的组合，以满足VNF的部署需求。
在一个可能的设计中，所述第一信息用于确定所述第一NFV模板中的部署单元，可以包括：所述第一信息用于确定所述第一NFV模板中与所述第一信息指示的所述VNF的部署方式对应的部署单元的组合。这样，可以使所述VNFM直接根据VNF的部署方式与部署单元的组合的对应关系，确定第一信息指示的所述VNF的部署方式对应的部署单元的组合。
在一个可能的设计中，当所述第一信息为虚拟机时，所述第一NFV模板中的所述部署单元可以包括以下一项或多项单元：VDU中的虚拟计算描述、VNF外部连接点描述符、VLD或部署风格DF。这样可以准确地确定当VNF部署为虚拟机时，所需要使用的部署单元，以满足VNF的实例化需求。
在一个可能的设计中，当所述第一信息为虚拟机容器时，所述第一NFV模板中的所述部署单元可以包括以下一项或多项单元：VDU中的容器描述、VNF外部连接点描述符、VLD或DF。这样可以准确地确定当VNF部署为虚拟机容器时，所需要使用的部署单元，以满足VNF的实例化需求。
在一个可能的设计中，当所述第一信息为裸机容器时，所述第一NFV模板中的所述部署单元可以包括以下一项或多项单元：第二NFV模板的信息、VNF外部连接点描述符或第二NFV模板的信息引用的一个或多个容器对象包文件。这样可以准确地确定当VNF部署为裸机容器时，所需要使用的部署单元，以满足VNF的实例化需求。
在一个可能的设计中，所述第二NFV模板的信息为应用服务描述符ASD，所述ASD包含增强的集群能力属性和部署项属性。这样，可以使第一NFV模板融合ASD的信息，从而降低裸机容器VNF的实例化的复杂度，同时可以解决现有的VNFD模板的信息在保留支持NFVO集中对VNF资源管理编排进行管控的授权需求和VNF云原生演进过程中CaaS管理根据Helm包灵活编排容器对象、闭环完成集群中对象资源自治管理需求之间的矛盾。
在一个可能的设计中，所述容器对象包文件可以是Helm图表。
第三方面，本申请还提供了一种VNF实例化的装置，所述VNF实例化的装置可以是VNFM，该VNF实例化的装置具有实现上述第一方面或第一方面的各个可能的设计示例中的方法的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一个可能的设计中，所述VNF实例化的装置的结构中包括通信模块和处理模块，这些单元可以执行上述第一方面或第一方面的各个可能的设计示例中的相应功能，具体参见方法示例中的详细描述，此处不做赘述。
在一个可能的设计中，所述VNF实例化的装置的结构中包括通信接口和处理器，可选的还包括存储器，所述通信接口用于收发信息或数据，以及用于与通信网络中的其他设备进行通信交互，所述处理器被配置为支持所述VNF实例化的装置执行上述第一方面或第一方面的各个可能的设计示例中的相应的功能。所述存储器与所述处理器耦合，其保存 所述VNF实例化的装置必要的程序指令和数据。
第四方面，本申请还提供了一种VNF实例化的装置，所述VNF实例化的装置可以是NFVO，该VNF实例化的装置具有实现上述第二方面或第二方面的各个可能的设计示例中的方法的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一个可能的设计中，所述VNF实例化的装置的结构中包括通信模块和处理模块，这些单元可以执行上述第二方面或第二方面的各个可能的设计示例中的相应功能，具体参见方法示例中的详细描述，此处不做赘述。
在一个可能的设计中，所述VNF实例化的装置的结构中包括通信接口和处理器，可选的还包括存储器，所述通信接口用于收发信息或数据，以及用于与通信网络中的其他设备进行通信交互，所述处理器被配置为支持所述VNF实例化的装置执行上述第二方面或第二方面的各个可能的设计示例中的相应的功能。所述存储器与所述处理器耦合，其保存所述VNF实例化的装置必要的程序指令和数据。
第五方面，本申请实施例提供了一种通信系统，可以包括如上述第三方面的VNFM和如上述第四方面的NFVO。
第六方面，本申请实施例提供的一种计算机可读存储介质，该计算机可读存储介质存储有程序指令，当程序指令在计算机上运行时，使得计算机执行本申请实施例第一方面及其任一可能的设计中，或第二方面及其任一可能的设计中所述的方法。示例性的，计算机可读存储介质可以是计算机能够存取的任何可用介质。以此为例但不限于：计算机可读介质可以包括非瞬态计算机可读介质、随机存取存储器(random-access memory，RAM)、只读存储器(read-only memory，ROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)、CD-ROM或其他光盘存储、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质。
第七方面，本申请实施例提供一种计算机程序产品，包括计算机程序代码或指令的，当计算机程序代码或指令在计算机上运行时，使得上述第一方面或第一方面任一种可能的设计中，或者上述第二方面或第二方面任一种可能的设计中所述的方法被执行。
第八方面，本申请还提供了一种芯片，包括处理器，所述处理器与存储器耦合，用于读取并执行所述存储器中存储的程序指令，以使所述芯片实现上述第一方面或第一方面任一种可能的设计中，或者上述第二方面或第二方面任一种可能的设计中所述的方法。
上述第三方面至第八方面中的各个方面以及各个方面可能达到的技术效果请参照上述针对第一方面或第一方面中的各种可能方案，或者第二方面或第二方面中的各种可能方案可以达到的技术效果说明，这里不再重复赘述。
附图说明
图1为本申请提供的一种NFV参考架构的示意图；
图2为本申请提供的一种CaaS技术的示例的示意图；
图3为本申请提供的两种支持容器化VNF的NFV模板的示意图；
图4为本申请提供的一种VNF实例化的方法的流程示意图；
图5为本申请提供的一种第一NFV模板的顶层结构示意图；
图6为本申请提供的第一属性指示的VNF部署方式与部署单元的组合的对应关系的一种示例的示意图；
图7为本申请提供的一种VNF实例化的装置的结构示意图；
图8为本申请提供的一种VNF实例化的装置的结构图。
具体实施方式
下面将结合附图对本申请作进一步地详细描述。
本申请实施例提供一种VNF实例化的方法及装置，用以灵活实现VNF的实例化，满足VNF各种不同的部署需求。其中，本申请所述方法和装置基于同一技术构思，由于方法及装置解决问题的原理相似，因此装置与方法的实施可以相互参见，重复之处不再赘述。
下面，先对本申请实施例中的部分用语进行解释说明，以便于本领域技术人员理解。
1、NFV，是指电信网络运营商借鉴信息技术(information technology，IT)领域的虚拟化技术，通过对电信网络功能的软件和硬件进行解耦，在通用的服务器、交换机和存储器等低成本硬件设备上部署和运行部分电信网络功能的技术。
2、容器即服务(container as a service，CaaS)，是指将VNF解构成多个容器服务，容器服务可以被VNF直接调用，也可以被VNF所调用的公共服务或专有服务所调用，然后组装形成容器化VNF，通过对容器服务的生命周期的管理来实现对容器化VNF的管理。
3、虚拟机容器，是指在虚拟机资源上构建的一类容器服务，通常虚拟机资源组成了容器服务运行的集群中的节点。
4、裸机容器，是指在裸机资源(主机或者裸金属资源)上构建的一类容器服务，通常裸机资源组成了容器服务运行的集群中的节点。
5、在本申请的描述中，“第一”、“第二”等词汇，仅用于区分描述的目的，而不能理解为指示或暗示相对重要性，也不能理解为指示或暗示顺序。
6、本申请实施例中“多项(个、种)”是指两项(个、种)或两项(个、种)以上，鉴于此，本申请实施例中也可以将“多项(个、种)”理解为“至少两项(个、种)”。“至少一项(个、种)”，可理解为一项(个、种)或多项(个、种)，例如理解为一项(个、种)、两项(个、种)或更多项(个、种)。例如，包括至少一项(个、种)，是指包括一项(个、种)、两项(个、种)或更多项(个、种)，而且不限制包括的是哪几项(个、种)，例如，包括A、B或C中的至少一项(个、种)，那么包括的可以是A、B、C、A和B、A和C、B和C、或A和B和C。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，字符“/”，如无特殊说明，一般表示前后关联对象是一种“或”的关系。
为了更加清晰地描述本申请实施例的技术方案，下面结合附图，对本申请实施例提供的VNF实例化的方法及装置进行详细说明。
图1示出了一种NFV参考架构的示意图。该NFV参考架构可以实现多种类型的通信网络，例如局域网(local area network，LAN)、互联网协议(internet protocol，IP)网络或者演进分组核心网(evolved packet core，EPC)网络等。
如图1所示，该NFV参考架构可以包括NFV管理和编排系统(NFV management and orchestration system，NFV-MANO)110、一个或多个运营支撑系统/业务支撑系统(operation support system/business support system，OSS/BSS)120、多个网元管理器(element manager， EM)130、多个VNF140以及NFV基础设施(NFV infrastructure，NFVI)150。
NFV-MANO 110可以包括NFV编排器(NFV orchestrator，NFVO)111、一个或多个VNF管理器(VNF manager，VNFM)112，以及虚拟化基础设施管理器(virtualised infrastructure manager，VIM)113。
其中，NFVO 111可以用于实现网络服务描述符(network service descriptor，NSD)，虚拟网络功能转发图(VNF forwarding graph，VNFFG)的管理及处理，网络服务生命周期的管理，以及，和VNFM配合实现VNF的生命周期管理和虚拟资源的全局视图功能。
VNFM 112可以实现VNF的生命周期管理，包括虚拟化网络功能描述符(VNF descriptor，VNFD)的管理、VNF的实例化、VNF实例的弹性伸缩(包括扩容(scaling out/up)和缩容(scaling in/down))、VNF实例的治愈(healing)以及VNF实例的终止。VNFM 112还可以支持接收NFVO下发的弹性伸缩(scaling)策略，实现自动化的VNF弹性伸缩。
VIM 113主要负责基础设施层硬件资源，虚拟化资源的管理(包括预留和分配)，虚拟资源状态的监控和故障上报，面向上层应用提供虚拟化资源池。
OSS/BSS 120主要面向电信服务运营商，提供综合的网络管理和业务运营功能，包括网络管理(例如故障监控、网络信息收集等)、计费管理以及客户服务管理等。
EM 130用于针对VNF执行传统的故障、配置、用户、性能和安全管理(fault management,configuration management,account management,performance management,security management，FCAPS)功能。
VNF 140对应于传统非虚拟化网络中的物理网络功能(physical network function，PNF)，如虚拟化的分组核心网(evolved packet core，EPC)节点(例如，移动性管理实体(mobility management entity，MME)，服务网关(serving gateway，SGW)，公用数据网网关(public data network gateway，PGW)等)。网络功能的功能性行为和状态与虚拟化与否无关，NFV技术需求希望VNF和PNF拥有相同的功能性行为和外部接口。
VNF 140可以由一个或多个更低功能级别的VNF组件(VNF component，VNFC)来组成。因此，一个VNF可以部署在多个虚拟机(virtual machine，VM)上，每个VM承载一个VNFC的功能，VNF也可以部署在一个VM上。
NFVI 150可以包括虚拟资源层、虚拟化层和硬件(hardware)资源层。其中，虚拟资源层中可以包括多个VM，或者还可以包括虚拟存储和虚拟网络等(在图1中未示出)。硬件资源层可以包括计算硬件、存储硬件以及网络硬件等(在图1中未示出)。
硬件资源层中的硬件可以包括专用的处理器或通用的用于提供处理和计算功能的处理器，如中央处理器(central process unit，CPU)，用于提供存储能力的设备，例如，磁盘或网络附属存储(network attached storage，NAS)；以及，交换机、路由器和/或其他网络设备。
虚拟资源层可以以虚拟机的形式向VNF 140提供，例如一个或多个虚拟机组成一个VNF140。虚拟化层通过硬件资源层中硬件形成虚拟网络，用于实现多个虚拟机之间的通信。例如，该虚拟网络可以通过虚拟局域网(virtual local area network，VLAN)、虚拟专用局域网业务(virtual private LAN service，VPLS)、虚拟可扩展局域网(virtual extensible local area network，VxLAN)或通用路由封装网络虚拟化(network virtualization using generic routing encapsulation，NVGRE)等技术实现。
NFVI 150中的虚拟化层用于抽象硬件资源层的硬件资源，将VNF 140和硬件资源所 属的物理层解耦，向VNF提供虚拟资源。
NFV-MANO 110可以用于实现VNF 140和NFVI 150的监控和管理。NFVO 111可以与一个或多个VNFM 112进行通信以实现与资源相关的请求、发送配置信息给VNFM 112、以及收集VNF 140的状态信息。另外，NFVO 111还可以与VIM 113进行通信以实现资源分配，和/或，实现虚拟化硬件资源的配置信息和状态信息的预留和交换。VNFM 112可以用于管理一个或多个VNF 140，执行各种管理功能，例如初始化、更新、查询、和/或终止VNF 140。VIM 113可以用于控制和管理VNF 140和NFVI中的虚拟资源和硬件资源的交互。例如，VIM 113可以用于执行资源向VNF 140的分配操作。VNFM 112和VIM 113可以互相通信以交换虚拟化硬件资源配置和状态信息。
在电信网络中，通常会用到另一种虚拟化技术，即CaaS技术。CaaS技术是一种操作系统级别的虚拟化技术，通过该技术将操作系统中不同的进程隔离开来，例如，Linux操作系统下的控制组(control groups，CGroup)机制或命名空间(name space)机制等。由于CaaS技术没有虚拟硬件，也没有操作系统，只有进程，因此，CaaS技术相比NFV技术更轻量，管理也更方便。
示例性的，图2示出了一种CaaS技术的示例，kubernetes(K8S)容器管理编排系统的架构图。
kubernetes将集群中的设备划分为一个kubernetes主节点(master node)和一群工作节点(working node)。其中，master节点上运行着集群管理相关的一组进程，例如，应用程序编程接口服务(application programming interface server，API server)、复制控制器(replication controller，RC)等，这些进程实现了整个集群的资源管理、容器舱(pod)调度、弹性伸缩、安全控制、系统监控和纠错等管理功能。在每个Node上运行kubelet、proxy、docker三个组件，负责对本节点上的pod的生命周期进行管理，以及实现服务代理的功能。如图2所示，一个pod中可以包括至少一个容器，则一个pod可以理解为一个或多个容器组成的容器舱。
其中，API Server提供了资源对象的唯一操作入口，其他所有组件都必须通过它提供的API接口来操作资源数据，通过对相关的资源数据“全量查询”以及“变化监听”，完成相关的业务功能。
controller manager是集群的管理控制中心，其主要目的是实现kubernetes集群的故障检测和恢复自动化工作。例如，可以根据RC的定义完成pod的复制或移除，以确保pod实例数符合RC的定义、根据服务(service)与pod的管理关系，完成service的端点(endpoints)对象的创建和更新、node的发现、管理和状态监控、以及本地缓存的镜像文件的清理等。
kubelet组件负责本节点上的pod的创建、修改、监控、删除等全生命周期管理，同时Kubelet定时向API Server上报本节点的状态信息。
proxy组件用于实现service的代理与软件模式的负载均衡。
docker组件为容器的运行环境。
随着虚拟化技术的不断发展，业界提出了在NFV-MANO的参考架构内引入容器管理。
例如，VNF 140可以由一个或多个容器对象来组成，一个容器对象可以理解为图2中的pod，而每个pod可以部署在一个容器集群节点资源池中，每个容器集群节点资源池中的资源可以是虚拟机(virtual machine，VM)或者裸金属(bare metal)服务器，每个VM承载一个或多个容器对象。
NFV-MANO 110还可以包括容器基础设施服务管理(container infrastructure service management，CISM)，容器集群管理(container cluster management，CCM)(在图1中没有示出)。
其中，CISM也可以称为CaaS管理，负责管理VNF所调用的容器对象，包括容器对象的创建、更新和删除，并在其纳管的容器集群节点资源池中将容器对象调度到相应的VM对应的节点资源上，该节点资源包括计算资源、存储资源和网络资源等。容器对象在ETSI标准中对应的概念是被管理的容器基础设施对象(managed container infrastructure object，MCIO)。
CCM负责对容器集群进行管理，包括容器集群所使用的节点资源池的创建和节点资源池的扩容或者缩容等。容器集群是由一个管理节点(例如，图2中的Kubernetes Master)和一系列的工作节点(例如，图2中的node)组成的集合。容器集群是一个动态的系统，在容器集群中可以部署多个容器，这些容器的状态和容器之间的通信可以被监控和管理系统所监控。容器集群在ETSI标准中对应的概念是容器基础设施服务集群(container infrastructure service cluster，CIS Cluster)。
CISM和CCM在北向接口上为NFVO或VNFM提供了调用其功能的管理服务。
对VNF实例化时需要依据NFV模板(也称NFV模型、NFV模板模型等)中的信息描述对VNF进行实例化。目前，电信行业中有两种NFV模板支持容器化VNF的部署。一种是ETSI NFV行业标准组定义的VNFD模板，另一种是ONAP定义的ASD模板，例如图3所示，应理解图3仅是一种示例，不作为对两种模板中包括的内容的限定。
无论是VNFD模板还是ASD模板都引用了开源社区定义的容器对象包(如：Helm)文件，其中容器对象包是由一个或多个容器对象的描述模板文件组成，而这些容器对象被VNF所引用。
由图3可以看出VNFD模板和Helm包文件中都包含了基础设施资源(也称为NFVI资源，包括计算资源、存储资源和网络资源)，也就是说VNFD模板和Helm包文件定义的基础设施资源存在冗余。VNFD定义的是VNF在生命周期管理过程中所消耗的资源需求，而Helm包中定义的是VNF所引用的一个或多个容器对象在管理编排中消耗的资源需求。VNFD的资源定义用于支持VNF生命周期管理过程中的资源授权(granting)操作，而Helm包中的资源定义用于部署容器VNF。此外，解析Helm包中的容器对象描述模板的任务不是由NFVO或VNFM来完成，而是交给更下层的容器管理平台(又称为CaaS管理或CISM)。
由此可知，VNFD模板在支持容器化VNF部署时，存在较大的局限性，(1)VNF所使用的NFVI资源信息在VNFD模板和Helm包中双层定义可能导致容器管理编排上下游资源信息同步困难，难以维持一致资源数据；(2)对于容器化VNF生命周期管理的每个操作都由NFVO从管理域整体资源视图角度进行资源授权，会抑制容器化VNF采用的云原生设计原则。云原生设计原则通常允许CaaS管理在一定资源范围内自治完成容器对象的资源扩缩容或自愈过程，无需每个操作由NFVO进行资源授权。NFVO也无法及时跟进容器层资源的快速变化。
在ONAP ASD模板中，ASD和Helm包之间没有重复描述的资源信息，解析Helm包中容器对象描述模板的任务可以由上层的业务编排器(service orchestrator，SO)完成。这样，简洁的ASD模板更有助于部署容器VNF的过程敏捷高效，能够快速响应容器VNF在生命周期管理过程中适配外界环境变化的需求。
ASD模板和VNFD模板形成了彼此互不兼容的容器VNF模板，如果需要在同一个网络运行环境中兼顾实现两个模板实例化的容器VNF，只能在NSD中包含VNFD和ASD两个分支模型，这样为容器化VNF的部署带来模板选择的不便，不仅增加了容器VNF实现的复杂度，同时也会增加容器化VNF部署的复杂性。
基于此，本申请实施例提出一种VNF实例化的方法及装置，通过使用融合的VNFD模板灵活实现VNF的实例化，以满足VNF的各种不同的部署需求，降低VNF部署的复杂度。可以理解的是，本申请实施例以融合VNFD模板和ASD模板为例进行介绍，本申请还可以适用于融合VNFD模板和其他用于VNF实例化的模板，本申请还可以适用于融合其他多种用于VNF实例化的模板，本申请对此不做限定。
图4示出了本申请实施例提供的一种VNF实例化的方法，如图4所示，该方法的具体流程可以包括：
步骤401：NFVO确定第一信息，并向VNFM发送VNF的实例化请求，所述VNF的实例化请求中包括所述第一信息，所述第一信息用于指示所述VNF的部署方式。
可选的，所述第一信息可以为虚拟机、虚拟机容器或者裸机容器，也即表示所述VNF的部署方式为虚拟机、虚拟机容器或者裸机容器。
其中，VNF的部署方式也可以理解为VNF的部署形态，即VNF部署在网络中的实现形态。
示例性的，所述VNF的实例化请求中还可以包括所述VNF的实例标识，以便于NFVO根据所述VNF的实例标识确定要访问的第一NFV模板。
需要说明的是，所述NFVO确定所述第一信息可以为所述NFVO的内部实现。
步骤402：所述VNFM根据所述第一信息确定第一NFV模板中的部署单元，也即所述第一信息用于确定第一NFV模板中的部署单元。
作为一种示例，该第一NFV模板可以为融合的VNFD模板，例如可以为在目前VNFD模板的基础上融合第二NFV模板的信息，以解决现有的VNFD模板的信息在保留支持NFVO集中对VNF资源管理编排进行管控的授权需求和VNF云原生演进过程中CaaS管理根据Helm包灵活编排容器对象、闭环完成集群中对象资源自治管理需求之间的矛盾。
可选的，第二NFV模板可以为ASD模板、边缘应用的描述模板(例如，应用描述符(application descriptor，APPD)等)或其他模板等，本申请不作限定。
其中，所述第一NFV模板包括元数据(metadata)单元，所述元数据单元包含VNF的相关信息，例如，第一NFV模板的标识信息、版本、提供商、描述信息等。
在一种可选的实施方式中，所述元数据单元中可以包括第一属性，所述第一属性用于指示VNF部署方式与部署单元的组合的对应关系。也即，所述第一属性指示VNF在不同的部署方式下所需使用的部署单元的组合。
例如，所述第一属性可以为部署单元选择((deployment unit，DU)selection)属性，当然，所述第一属性还可以有其他名称，本申请对此不作限定。
示例性的，所述第一NFV模板中还可以包括一个或多个可选择的部署单元，在VNF实例化过程中，VNFM可以根据第一信息确定用于实例化该VNF的第一NFV模板中的部署单元。例如，VNFM可以根据第一信息在一个或多个可选择的部署单元中选择该第一信息对应的部署单元的组合(第一信息对应的部署单元的组合可以理解为第一信息指示的VNF的部署方式对应的第一NFV模板中部署单元的组合)。也即可以根据VNF的不同部 署需求将可选择的部署单元进行组合。
在一种可选的实施方式中，所述VNFM根据所述第一信息确定第一NFV模板中的部署单元，可以通过以下两种方式实现：
方式a1、当所述元数据单元中包括所述第一属性的情况下，所述VNFM根据所述第一信息，确定所述第一NFV模板中所述第一属性指示的部署单元的组合，所述部署单元的组合与所述第一信息指示的所述VNF的部署方式对应。
也就是说，在该方式a1中，所述VNFM可以根据所述第一属性确定与所述第一信息指示的部署方式对应的部署单元的组合，从而满足VNF的部署需求。
方式a2、所述VNFM确定所述第一NFV模板中与所述第一信息指示的所述VNF的部署方式对应的部署单元的组合。
在该方式a2中，可以预先确定VNF的部署方式与部署单元的组合的对应关系，而不是在第一NFV模板中定义这种对应关系。从而，VNFM可以直接确定第一信息指示的所述VNF的部署方式对应的部署单元的组合。
作为一种可能的示例，第一NFV模板的顶层结构(即树状结构的根路径)可以如图5所示。如图5所示，第一NFV模板中包括的可选的部署单元可以包括以下一个或多个单元：虚拟化部署单元(virtualization deployment unit，VDU)、VNF外部连接点描述符(external connection point descriptor，ExtCpd)、虚拟链路描述符(virtualization link descriptor，VLD)、部署风格(deployment flavor，DF)、第二模板的信息(例如ASD)、一个或多个容器对象包文件，容器对象包文件包含一个或多个容器对象(例如MCIO)模板。例如容器对象包文件可以为Helm图表(Helm chart)。
其中，当第二模板的信息为所述ASD时，ASD单元中可以包含开源社区模型如ONAP ASD中未被现有的VNFD包含的信息元素，例如所述ASD可以包含增强的集群能力属性(enhancedClusterCapabilities)和/或部署项属性(deploymentItem)。ONAP ASD模板中的metadata单元中的信息可以与现有的VNFD中的metadata单元中的信息合并得到第一NFV模板中的元数据单元，ONAP ASD模板中的asdExtCpd单元与现有的VNFD的ExtCpd单元合并，得到第一NFV模板中的可选择的部署单元ExtCpd。
VDU可以用于描述VNFC的部署信息和VNFC在运行态进行生命周期管理的管理信息。
VNF外部连接点描述符(ExtCpd)可以用于描述VNF外部连接点的配置信息。
VLD可以用于描述VNF所使用的虚拟链路的配置信息。
DF可以用于描述VNF在不同的网络拓扑结构中进行部署的资源组合信息。
沿用上例，根据所述第一信息的不同情况，所述VNFM在根据所述第一信息确定的第一NFV模板中的部署单元时，可以根据第一信息在图5所示的可选择的部署单元中选择符合第一信息指示的部署方式的部署单元的组合。示例性的，可以包含以下三种示例：
示例b1，当所述第一信息为虚拟机时，所述第一NFV模板中的所述部署单元可以包括以下一项或多项单元：VDU中的虚拟计算描述(virtualComputeDesc)、VNF外部连接点描述符、VLD或DF。
示例b2，当所述第一信息为虚拟机容器时，所述第一NFV模板中的所述部署单元可以包括以下一项或多项单元：VDU中的容器描述(OSContainerDesc)、VNF外部连接点描述符、VLD或DF。
在上述示例b1和示例b2的情况下，NFVO和VNFM之间仍然可以通过现有的资源授权(granting)过程对每个VNF生命周期管理(life cycle management，LCM)操作进行资源的集中管控。
示例b3，当所述第一信息为裸机容器时，所述第一NFV模板中的所述部署单元可以包括以下一项或多项单元：第二NFV模板的信息、VNF外部连接点描述符或第二NFV模板的信息引用的一个或多个容器对象包文件。
可选的，在该示例b3中，所述第二NFV模板的信息可以为ASD，所述ASD可以包含增强的集群能力属性和部署项属性。所述容器对象包文件可以是Helm图表。
在上述示例b3中，所述第二NFV模板的信息为ASD的情况下，NFVO可以不再对每个VNF LCM操作进行资源授权，VNF LCM操作中的资源管理可以依赖于VNFM对Helm包中容器对象模板的信息解析，通过容器对象模板中资源定义的统计形成每个VNF LCM操作所需的资源数量，并按需将自下而上形成的资源使用信息报告给NFVO。这样，可以解决现有的VNFD模板的信息在保留支持NFVO集中对VNF资源管理编排进行管控的授权需求和VNF云原生演进过程中CaaS管理根据Helm包灵活编排容器对象、闭环完成集群中对象资源自治管理需求之间的矛盾。
在该示例b3中，VNFM应具有对容器对象包文件(如Helm Chart)的解析能力。
沿用上例，上述描述当所述元数据单元中包括所述第一属性的情况下，所述第一属性指示的VNF部署方式与部署单元的组合的对应关系的一种示例可以如图6所示。图6中示出的三种对应关系的相关描述可以分别参见上述示例b1～b3的描述，此处不再详细描述。
应理解，当所述元数据单元中不包括所述第一属性的情况下，预先定义或预先配置的第一信息与部署单元的组合的对应关系，也即部署方式与部署单元的组合的对应关系的一种示例也可以参见上述示例b1～b3的描述，此处不再详细描述。
步骤403：所述VNFM根据所述部署单元对所述VNF进行实例化，也即所述部署单元用于实例化所述VNF。
在一种可选的实施方式中，当所述第一信息为虚拟机或虚拟机容器时，所述VNFM根据所述部署单元对所述VNF进行实例化时，VNFM和NFVO之间交互对VNF实例化中的资源管理进行授权(granting)，然后VNFM向VIM发起VM分配操作。
在另一种可选的实施方式中，当所述第一信息为裸机容器时，所述VNFM解析部署单元中第二模板的信息(如ASD单元)所引用的容器对象包文件(如Helm Chart)中的容器对象描述模板，并向CaaS管理发起容器对象(如：MCIO)的创建或复用已有的容器对象的过程。
在上述两种可选的实施方式中任一种实施方式之后，所述VNFM完成VNF的实例的信息的相关配置，然后VNFM向NFVO发送VNF实例化应答消息。
采用本申请实施例提供的VNF实例化的方法，VNFM可以根据用于指示VNF的部署方式的信息灵活确定符合需求的NFV模板，从而灵活实现VNF的实例化，并可以满足VNF的不同部署需求，如虚拟机、虚拟机容器或裸机容器等，降低VNF部署的复杂度。
上述本申请提供的实施例中，分别从各个功能模块或设备本身、以及从各个功能模块或设备之间交互的角度对本申请实施例提供的VNF实例化的方法的各方案进行了介绍。可以理解的是，各个功能模块或设备，例如上述VNFM、NFVO为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结 合本申请中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
示例性的，当上述功能模块或者设备通过软件模块来实现相应的功能时，本申请实施例提供的一种VNF实例化的装置可以如图7所示。参阅图7所示，VNF实例化的装置700可以包括通信模块701和处理模块702。其中，所述通信模块701用于所述VNF实例化的装置700接收信息(消息或数据)和/或发送信息(消息或数据)，所述处理模块702用于对所述VNF实例化的装置700的动作进行控制管理。所述处理模块702还可以控制所述通信模块701执行的步骤。
可选的，该VNF实例化的装置700具体可以是上述实施例中的VNFM、所述VNFM中的处理器，或者芯片，或者芯片系统，或者是一个功能模块等；或者，该VNF实例化的装置700具体可以是上述实施例中的NFVO、所述NFVO的处理器，或者芯片，或者芯片系统，或者是一个功能模块等。
在一个实施例中，所述VNF实例化的装置700用于实现上述图4所述的实施例中VNFM的功能时，可以包括：所述通信模块701用于接收来自NFVO的VNF的实例化请求，所述VNF的实例化请求中包括第一信息，所述第一信息用于指示所述VNF的部署方式；所述处理模块702用于根据所述第一信息确定第一网络功能虚拟化NFV模板中的部署单元，并根据所述部署单元对所述VNF进行实例化。
在一种可选的实施方式中，所述第一NFV模板可以包括元数据单元，所述元数据单元中可以包括第一属性，所述第一属性用于指示VNF部署方式与部署单元的组合的对应关系。
一种示例中，所述处理模块702在根据所述第一信息确定所述第一NFV模板中的部署单元时，可以用于：根据所述第一信息，确定所述第一NFV模板中所述第一属性指示的部署单元的组合，所述部署单元的组合与所述第一信息指示的所述VNF的部署方式对应。
另一种示例中，所述处理模块702在根据所述第一信息确定所述第一NFV模板中的部署单元时，可以用于：确定所述第一NFV模板中与所述第一信息指示的所述VNF的部署方式对应的部署单元的组合。
一种可能的实施方式中，当所述第一信息为虚拟机时，所述第一NFV模板中的所述部署单元可以包括以下一项或多项单元：VDU中的虚拟计算描述、VNF外部连接点描述符、VLD或DF。
另一种可能的实施方式中，当所述第一信息为虚拟机容器时，所述第一NFV模板中的所述部署单元可以包括以下一项或多项单元：VDU中的容器描述、VNF外部连接点描述符、VLD或DF。
又一种可能的实施方式中，当所述第一信息为裸机容器时，所述第一NFV模板中的所述部署单元可以包括以下一项或多项单元：第二NFV模板的信息、VNF外部连接点描述符或第二NFV模板的信息引用的一个或多个容器对象包文件。
可选的，所述第二NFV模板的信息可以为ASD，所述ASD包含增强的集群能力属性和部署项属性。
例如，所述容器对象包文件可以是Helm图表。
在另一个实施例中，所述VNF实例化的装置700用于实现上述图4所述的实施例中NFVO的功能时，可以包括：所述处理模块702可以用于确定第一信息，所述第一信息用于指示VNF的部署方式；所述第一信息用于确定第一网络功能虚拟化NFV模板中的部署单元，所述部署单元用于实例化所述VNF；所述通信模块701可以用于向虚拟化网络功能管理器VNFM发送所述VNF的实例化请求，所述VNF的实例化请求中包括第一信息。
在一种可选的实施方式中，所述第一NFV模板可以包括元数据单元，所述元数据单元中可以包括第一属性，所述第一属性用于指示VNF部署方式与部署单元的组合的对应关系。
在一种示例中，所述第一信息用于确定所述第一NFV模板中的部署单元，可以包括：所述第一信息用于确定所述第一NFV模板中所述第一属性指示的部署单元的组合，所述部署单元的组合与所述第一信息指示的所述VNF的部署方式对应。
在另一种示例中，所述第一信息用于确定所述第一NFV模板中的部署单元，可以包括：所述第一信息用于确定所述第一NFV模板中与所述第一信息指示的所述VNF的部署方式对应的部署单元的组合。
在一种可能的实施方式中，当所述第一信息为虚拟机时，所述第一NFV模板中的所述部署单元可以包括以下一项或多项单元：VDU中的虚拟计算描述、VNF外部连接点描述符、VLD或DF。
在另一种可能的实施方式中，当所述第一信息为虚拟机容器时，所述第一NFV模板中的所述部署单元可以包括以下一项或多项单元：VDU中的容器描述、VNF外部连接点描述符、VLD或DF。
在又一种可能的实施方式中，当所述第一信息为裸机容器时，所述第一NFV模板中的所述部署单元可以包括以下一项或多项单元：第二NFV模板的信息、VNF外部连接点描述符或所述第二NFV模板的信息引用的一个或多个容器对象包文件。
可选的，所述第二NFV模板的信息可以为ASD，所述ASD包含增强的集群能力属性和部署项属性。
例如，所述容器对象包文件可以是Helm图表。
需要说明的是，本申请实施例中对单元的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。在本申请的实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)或处理器(processor)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
示例性的，当上述功能模块或者设备通过硬件来实现相应的功能时，本申请实施例提 供的一种VNF实例化的装置可以如图8所示。参阅图8所示，VNF实例化的装置800可以包括通信接口801和处理器802。可选的，所述VNF实例化的装置800中还可以包括存储器803。
具体地，所述处理器802可以是中央处理器(central processing unit，CPU)，网络处理器(network processor，NP)或者CPU和NP的组合。所述处理器802还可以进一步包括硬件芯片。上述硬件芯片可以是专用集成电路(application-specific integrated circuit，ASIC)，可编程逻辑器件(programmable logic device，PLD)或其组合。上述PLD可以是复杂可编程逻辑器件(complex programmable logic device，CPLD)，现场可编程逻辑门阵列(field-programmable gate array，FPGA)，通用阵列逻辑(generic array logic，GAL)或其任意组合。
其中，所述通信接口801、所述处理器802和所述存储器803之间相互连接。可选的，所述通信接口801、所述处理器802和所述存储器803通过总线804相互连接；所述总线804可以是外设部件互连标准(Peripheral Component Interconnect，PCI)总线或扩展工业标准结构(Extended Industry Standard Architecture，EISA)总线等。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图8中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
在一种可选的实施方式中，所述存储器803，用于存放程序等。具体地，程序可以包括程序代码，该程序代码包括计算机操作指令。所述存储器803可能包括RAM，也可能还包括非易失性存储器(non-volatile memory)，例如一个或多个磁盘存储器。所述处理器802执行所述存储器803所存放的应用程序，实现上述功能，从而实现VNF实例化的装置800的功能。
可选的，该VNF实例化的装置800可以是上述实施例中的VNFM；还可以是上述实施例中的NFVO。
在一个实施例中，所述VNF实例化的装置800在实现图4所示的实施例中VNFM的功能时，通信接口801可以实现图4所示的实施例中的由VNFM执行的收发操作；处理器802可以实现图4所示的实施例中由VNFM执行的除收发操作以外的其他操作。具体的相关具体描述可以参见上述图4所示的实施例中的相关描述，此处不再详细介绍。
在一个实施例中，所述VNF实例化的装置800在实现图4所示的实施例中NFVO的功能时，通信接口801可以实现图4所示的实施例中的由NFVO执行的收发操作；处理器802可以实现图4所示的实施例中由NFVO执行的除收发操作以外的其他操作。具体的相关具体描述可以参见上述图4所示的实施例中的相关描述，此处不再详细介绍。
基于以上实施例，本申请实施例提供了一种网络结构，该网络结构可以包括上述实施例涉及的VNFM和NFVO等。
本申请实施例还提供一种计算机可读存储介质，所述计算机可读存储介质用于存储计算机程序，该计算机程序被计算机执行时，所述计算机可以实现上述方法实施例提供的VNF实例化的方法。
本申请实施例还提供一种计算机程序产品，所述计算机程序产品用于存储计算机程序，该计算机程序被计算机执行时，所述计算机可以实现上述方法实施例提供的VNF实例化的方法。
本申请实施例还提供一种芯片，包括处理器，所述处理器与存储器耦合，用于调用所 述存储器中的程序使得所述芯片实现上述方法实施例提供的VNF实例化的方法。
本申请实施例还提供一种芯片，所述芯片与存储器耦合，所述芯片用于实现上述方法实施例提供的VNF实例化的方法。
本领域内的技术人员应明白，本申请的实施例可提供为方法、系统、或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (23)

  1. 一种虚拟网络功能VNF实例化的方法，其特征在于，包括：
    虚拟化网络功能管理器VNFM接收来自网络功能虚拟化编排器NFVO的VNF的实例化请求，所述VNF的实例化请求中包括第一信息，所述第一信息用于指示所述VNF的部署方式；
    所述VNFM根据所述第一信息确定第一网络功能虚拟化NFV模板中的部署单元；
    所述VNFM根据所述部署单元对所述VNF进行实例化。
  2. 如权利要求1所述的方法，其特征在于，所述第一NFV模板包括元数据单元，所述元数据单元中包括第一属性，所述第一属性用于指示VNF部署方式与部署单元的组合的对应关系。
  3. 如权利要求2所述的方法，其特征在于，所述VNFM根据所述第一信息确定所述第一NFV模板中的部署单元，包括：
    所述VNFM根据所述第一信息，确定所述第一NFV模板中所述第一属性指示的部署单元的组合，所述部署单元的组合与所述第一信息指示的所述VNF的部署方式对应。
  4. 如权利要求1所述的方法，其特征在于，所述VNFM根据所述第一信息确定所述第一NFV模板中的部署单元，包括：
    所述VNFM确定所述第一NFV模板中与所述第一信息指示的所述VNF的部署方式对应的部署单元的组合。
  5. 如权利要求2-4任一项所述的方法，其特征在于，当所述第一信息为虚拟机时，所述第一NFV模板中的所述部署单元包括以下一项或多项单元：虚拟化部署单元VDU中的虚拟计算描述、VNF外部连接点描述符、虚拟链路描述符VLD或部署风格DF。
  6. 如权利要求2-4任一项所述的方法，其特征在于，当所述第一信息为虚拟机容器时，所述第一NFV模板中的所述部署单元包括以下一项或多项单元：VDU中的容器描述、VNF外部连接点描述符、VLD或DF。
  7. 如权利要求2-4任一项所述的方法，其特征在于，当所述第一信息为裸机容器时，所述第一NFV模板中的所述部署单元包括以下一项或多项单元：第二NFV模板的信息、VNF外部连接点描述符或所述第二NFV模板的信息引用的一个或多个容器对象包文件。
  8. 如权利要求7所述的方法，其特征在于，所述第二NFV模板的信息为应用服务描述符ASD，所述ASD包含增强的集群能力属性和部署项属性。
  9. 如权利要求7或8所述的方法，其特征在于，所述容器对象包文件是Helm图表。
  10. 一种虚拟网络功能VNF实例化的方法，其特征在于，包括：
    网络功能虚拟化编排器NFVO确定第一信息，所述第一信息用于指示VNF的部署方式；所述第一信息用于确定第一网络功能虚拟化NFV模板中的部署单元，所述部署单元用于实例化所述VNF；
    所述NFVO向虚拟化网络功能管理器VNFM发送所述VNF的实例化请求，所述VNF的实例化请求中包括所述第一信息。
  11. 如权利要求10所述的方法，其特征在于，所述第一NFV模板包括元数据单元，所述元数据单元中包括第一属性，所述第一属性用于指示VNF部署方式与部署单元的组合的对应关系。
  12. 如权利要求11所述的方法，其特征在于，所述第一信息用于确定所述第一NFV模板中的部署单元，包括：
    所述第一信息用于确定所述第一NFV模板中所述第一属性指示的部署单元的组合，所述部署单元的组合与所述第一信息指示的所述VNF的部署方式对应。
  13. 如权利要求10所述的方法，其特征在于，所述第一信息用于确定所述第一NFV模板中的部署单元，包括：
    所述第一信息用于确定所述第一NFV模板中与所述第一信息指示的所述VNF的部署方式对应的部署单元的组合。
  14. 如权利要求10-13任一项所述的方法，其特征在于，当所述第一信息为虚拟机时，所述第一NFV模板中的所述部署单元包括以下一项或多项单元：虚拟化部署单元VDU中的虚拟计算描述、VNF外部连接点描述符、虚拟链路描述符VLD或部署风格DF。
  15. 如权利要求10-13任一项所述的方法，其特征在于，当所述第一信息为虚拟机容器时，所述第一NFV模板中的所述部署单元包括以下一项或多项单元：VDU中的容器描述、VNF外部连接点描述符、VLD或DF。
  16. 如权利要求10-13任一项所述的方法，其特征在于，当所述第一信息为裸机容器时，所述第一NFV模板中的所述部署单元包括以下一项或多项单元：第二NFV模板的信息、VNF外部连接点描述符或所述第二NFV模板的信息引用的一个或多个容器对象包文件。
  17. 如权利要求16所述的方法，其特征在于，所述第二NFV模板的信息为应用服务描述符ASD，所述ASD包含增强的集群能力属性和部署项属性。
  18. 如权利要求16或17所述的方法，其特征在于，所述容器对象包文件是Helm图表。
  19. 一种虚拟网络功能VNF实例化的装置，其特征在于，包括存储器、通信接口和处理器，其中：
    所述存储器用于存储计算机指令；
    所述通信接口用于接收和发送信息；
    所述处理器与所述存储器耦合，用于调用所述存储器中的计算机指令，以通过所述通信接口执行如权利要求1-9任一项所述的方法。
  20. 一种虚拟网络功能VNF实例化的装置，其特征在于，包括存储器、通信接口和处理器，其中：
    所述存储器用于存储计算机指令；
    所述通信接口用于接收和发送信息；
    所述处理器，与所述存储器耦合，用于调用所述存储器中的计算机指令，以通过所述通信接口执行如权利要求10-18任一项所述的方法。
  21. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质中存储有计算机可执行指令，所述计算机可执行指令在被所述计算机调用时以执行如权利要求1-9中任一项所述的方法，或者执行如权利要求10-18中任一项所述的方法。
  22. 一种计算机程序产品，其特征在于，包含指令，当所述指令在计算机上运行时，使得如权利要求1-9中任一项所述的方法，或如权利要求10-18中任一项所述的方法被执行。
  23. 一种芯片，其特征在于，所述芯片与存储器耦合，用于读取并执行所述存储器中存储的程序指令，以实现如权利要求1-9中任一项所述的方法，或者实现如述权利要求10-18中任一项所述的方法。
PCT/CN2023/076484 2022-02-18 2023-02-16 一种虚拟网络功能vnf实例化的方法及装置 WO2023155838A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210152182.9 2022-02-18
CN202210152182.9A CN116661941A (zh) 2022-02-18 2022-02-18 一种虚拟网络功能vnf实例化的方法及装置

Publications (1)

Publication Number Publication Date
WO2023155838A1 true WO2023155838A1 (zh) 2023-08-24

Family

ID=87577545

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/076484 WO2023155838A1 (zh) 2022-02-18 2023-02-16 一种虚拟网络功能vnf实例化的方法及装置

Country Status (2)

Country Link
CN (1) CN116661941A (zh)
WO (1) WO2023155838A1 (zh)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200012510A1 (en) * 2017-03-24 2020-01-09 Nokia Technologies Oy Methods and apparatuses for multi-tiered virtualized network function scaling
CN111221618A (zh) * 2018-11-23 2020-06-02 华为技术有限公司 一种容器化虚拟网络功能的部署方法和装置
CN111416727A (zh) * 2019-01-07 2020-07-14 中国移动通信有限公司研究院 Vnf上载实例化方法及装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200012510A1 (en) * 2017-03-24 2020-01-09 Nokia Technologies Oy Methods and apparatuses for multi-tiered virtualized network function scaling
CN111221618A (zh) * 2018-11-23 2020-06-02 华为技术有限公司 一种容器化虚拟网络功能的部署方法和装置
CN111416727A (zh) * 2019-01-07 2020-07-14 中国移动通信有限公司研究院 Vnf上载实例化方法及装置

Also Published As

Publication number Publication date
CN116661941A (zh) 2023-08-29

Similar Documents

Publication Publication Date Title
US11283684B2 (en) Network slice deployment method and apparatus
US11960915B2 (en) Method and apparatus for creating virtual machine based on parameter information of a virtual network interface card
EP3461087B1 (en) Network-slice resource management method and apparatus
US10397132B2 (en) System and method for granting virtualized network function life cycle management
US11108653B2 (en) Network service management method, related apparatus, and system
US10601666B2 (en) Network functions virtualization management and orchestration policy descriptor management method and apparatus
US20190173802A1 (en) Sla-based resource allocation method and nfvo
CN111683074A (zh) 一种基于nfv的安全网络架构和网络安全管理方法
EP3413511B1 (en) Vnfm determining method and network function virtualization orchestrator
CN112398687B (zh) 云计算网络的配置方法、云计算网络系统以及存储介质
WO2019174000A1 (zh) 用于业务管理的方法和装置
WO2020103925A1 (zh) 一种容器化虚拟网络功能的部署方法和装置
WO2020108443A1 (zh) 一种虚拟化管理方法及装置
WO2019047835A1 (zh) 虚拟网络功能的实例化方法
EP4109251A1 (en) Vnf instantiation method and device
US20220350637A1 (en) Virtual machine deployment method and related apparatus
EP4177742A1 (en) Multitenancy management method and apparatus
US20210326306A1 (en) Method and apparatus for deploying virtualised network function
WO2023155838A1 (zh) 一种虚拟网络功能vnf实例化的方法及装置
WO2020077585A1 (zh) Vnf服务实例化方法及装置
WO2023066224A1 (zh) 一种部署容器服务的方法及装置
CN114124740A (zh) 一种vnf实例化的方法和装置
US20230259387A1 (en) Data flow mirroring method and apparatus
WO2023179580A1 (zh) 一种部署vnf的方法、装置及设备
WO2019011180A1 (zh) 一种License的发送方法和装置

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

Country of ref document: EP

Kind code of ref document: A1