WO2020228838A1 - 容器化vnf的部署方法和相关设备 - Google Patents

容器化vnf的部署方法和相关设备 Download PDF

Info

Publication number
WO2020228838A1
WO2020228838A1 PCT/CN2020/090915 CN2020090915W WO2020228838A1 WO 2020228838 A1 WO2020228838 A1 WO 2020228838A1 CN 2020090915 W CN2020090915 W CN 2020090915W WO 2020228838 A1 WO2020228838 A1 WO 2020228838A1
Authority
WO
WIPO (PCT)
Prior art keywords
container object
container
instance
identifier
vnf
Prior art date
Application number
PCT/CN2020/090915
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 华为技术有限公司
Priority to EP20806603.5A priority Critical patent/EP3964953A4/en
Publication of WO2020228838A1 publication Critical patent/WO2020228838A1/zh
Priority to US17/527,121 priority patent/US11928522B2/en

Links

Images

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/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5061—Partitioning or combining of resources
    • G06F9/5077—Logical partitioning of resources; Management or configuration of virtualized resources
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
    • 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 field of communication technology, and in particular to a deployment method and related equipment of a containerized VNF.
  • Network function virtualization means that telecom network operators draw on virtualization technology in the field of information technology (IT, Information Technology), and integrate part of telecom network functions in common servers, switches, and storage devices.
  • IT information technology
  • core network function decouples software and hardware, so as to realize the rapid and efficient deployment and operation of network services (NS, Network Service), and at the same time, achieve the goal of saving network investment costs and operating costs.
  • NFV Network Function Virtualization
  • telecommunication network functions are implemented in software, and can be run on general-purpose server hardware, which can be migrated, instantiated, and deployed in different physical locations on the network as required, without the need to install new equipment.
  • the container as a service can be regarded as a specific type of platform as a service (PaaS, Platform as a Service) service, for example.
  • a container is an operating system-level virtualization technology that isolates different processes through operating system isolation technologies such as CGroup and NameSpace under Linux.
  • Container technology is different from hardware virtualization (Hypervisor) technology. There is no virtual hardware, and there is no operating system inside the container, only processes. Because of this important feature of container technology, containers are lighter and easier to manage than virtual machines.
  • a set of common management operations are defined, such as start, stop, pause, and delete, etc., to carry out unified life cycle management for the container.
  • containerized VNFs Due to the service-oriented or micro-service-oriented application forms supported by containerized VNFs, the deployment mechanism of containerized VNFs is generally more complicated to implement.
  • the embodiment of the present application provides a containerized VNF deployment method and related equipment, which is beneficial to reduce the deployment complexity of the containerized VNF.
  • the first aspect of the embodiments of the present application provides a containerized VNF deployment method, including:
  • the network function virtualization orchestrator sends the first VNF instantiation request to the virtual network function manager (VNFM, VNF Manager).
  • the virtual network function manager receives the first VNF instantiation request from the network function virtualization orchestrator (NFVO).
  • the first VNF instantiation request carries a first VNF instance identifier and a first virtualized network function descriptor (VNFD, VNF Descriptor) identifier.
  • the VNFM determines the container object package identifier referenced by the VNFD represented by the first VNFD identifier (the container object package is, for example, a managed container infrastructure object package (MCIOP)).
  • MCIOP managed container infrastructure object package
  • the VNFM sends a container object package management request to a container management entity (the container management entity is, for example, a container infrastructure service management entity CISM), and the container object package management request carries the container object package identifier.
  • the VNFM receives a container object package management response from the container management entity, where the container object package management response is used to indicate a container object instance in the container object package represented by the container object package identifier (wherein, the container object, for example, Created successfully for the managed container infrastructure object (MCIO).
  • the container object package management response may carry, for example, the container object instance identifier of the successfully created container object instance.
  • the VNFM creates the VNF instance represented by the first VNF instance identifier, and maintains (for example, locally maintains) the mapping relationship between the first VNF instance identifier and the container object package identifier.
  • the container object package management request may be used to trigger the container management entity to create a container object instance in the container object package indicated by the container object package identifier according to the container object package identifier.
  • the creation of the container object instance in the container object package represented by the container object package identifier by the container management entity according to the container object package identifier may include, for example, determining the container object package referenced by the container object package identifier.
  • a container object package file which creates a container object instance (for example, a container infrastructure object) in the container object package according to the container object package file, and can schedule the created container object instance to the container runtime used by it
  • An instance (the container runtime instance is, for example, a container infrastructure service (CIS) instance).
  • CIS container infrastructure service
  • the container object package contains one or more container objects, and each container object can be mapped to an object in an open source de facto standard, for example.
  • the container object may be mapped to a Kubernetes object, for example, the Kubernetes object may include Pod, Service, or Deployment.
  • the container object package file may be mapped to Helm Chart, for example, and the container object package instance may be mapped to Helm Release, for example.
  • the container object is visible to the container management entity but not to the management and orchestration entity.
  • the VNFD model is enhanced so that the VNFD can refer to the container object package identifier, so that the VNFD supports the deployment of the containerized VNF.
  • the VNFM initiates the management operation of the corresponding container object package to the container management entity, and there is no need to deal with container objects and infrastructure resources (VM or bare metal) on the interface between the VNFM and the container management entity. Management operations. Due to the increased compatibility of VNFDs for the deployment of containerized VNFs, it is beneficial to promote smoother evolution of VM-based VNFs in existing networks to containerized VNFs, thereby reducing the deployment complexity of containerized VNFs.
  • the method before the VNFM sends a container object package management request to the container management entity, the method further includes: the VNFM sends a container object package creation request to the container management entity, and the container object package creation request carries The name and/or access address of the container object package file used to create the container object package.
  • the VNFM receives a container object package creation response from the container management entity, and the container object package creation response carries the container object package identifier of the container object package created by the container management entity.
  • the container object package creation request for example, can be used to trigger the container management entity to obtain the container object package file according to the name and/or access address of the container object package file after receiving the container object package creation request, and use the The container object package file creates the container object package; and sends a container object package creation response to the VNFM, where the container object package creation response carries the container object package identifier of the container object package created by the container management entity.
  • the VNFM may receive a VNF instance termination request from the NFVO, and the VNF instance termination request carries a second VNF instance identifier; the VNFM determines that it has a mapping with the second VNF instance identifier The container object package identifier of the relationship; the VNFM sends a container object package delete request to the container management entity, and the container object package delete request carries the determined container object package identifier.
  • the container object package deletion request may be used, for example, to trigger the container management entity to terminate the container object instance in the container object package indicated by the container object package identifier, and release the container used by the terminated container object instance Runtime instance.
  • an infrastructure resource pool may also be created in the following manner.
  • the method further includes: the VNFM receives a second VNF instantiation request from NFVO, where the second VNF instantiation request The VNF instantiation request carries a second VNF instance identifier (wherein the second VNF instance identifier is the VNF instance identifier of the VNF instance to be terminated) and a second VNFD identifier; the VNFM is derived from the VNFD indicated by the second VNFD identifier
  • the number of VM resources and VM resource specifications required by the infrastructure resource pool to be created are obtained in the database; the VNFM sends a resource allocation request to the virtualization infrastructure manager VIM, where the resource allocation request carries the infrastructure resources to be created The VM resource specifications and the number of VM resources of the pool; the VNFM receives a resource allocation response from the VIM, and the resource allocation response carries the VM instance identifier of the allocated VM instance; the VNFM tags the
  • the VNFD may also include a virtualization deployment unit (VDU) identifier.
  • VDU virtualization deployment unit
  • the VNF is a VM-based VNF
  • the VDU attributes contained in the VNFD are allowed to be used, and the container object package attributes referenced by the VNFD are prohibited from being used;
  • the VNF is a containerized VNF
  • the VDU attributes contained in the VNFD are allowed or prohibited to be used,
  • the container object package attribute referenced by the VNFD is allowed to be used.
  • the flow direction of resource allocation can be better controlled, which is beneficial to simplify the processing complexity.
  • VNFM virtual network function manager
  • the receiving unit is configured to receive a first virtual network function VNF instantiation request from NFVO, where the first VNF instantiation request carries a first VNF instance identifier and a first virtualized network function descriptor VNFD identifier.
  • the determining unit is used to determine the container object package identifier referenced by the VNFD represented by the first VNFD identifier.
  • the sending unit is configured to send a container object package management request to a container management entity, where the container object package management request carries the container object package identifier.
  • the receiving unit is further configured to receive a container object package management response from the container management entity, wherein the container object package management response is used to indicate the container object in the container object package indicated by the container object package identifier The instance was created successfully.
  • the creation management unit is configured to create the VNF instance represented by the first VNF instance identifier, and locally maintain the mapping relationship between the first VNF instance identifier and the container object package identifier.
  • the container object package management request for example, can be used to trigger the container management entity to create a container object package file according to the container object package file after determining the container object package file referenced by the container object package identifier.
  • the container object instance in the container object package is described, and the created container object instance is scheduled to the container runtime instance used by it.
  • the sending unit may be further configured to send a container object package creation request to the container management entity before sending the container object package management request to the container management entity, and the container object package creation request carries The name and/or access address of the container object package file used to create the container object package.
  • the receiving unit is further configured to receive a container object package creation response from the container management entity, where the container object package creation response carries the container object package identifier of the container object package created by the container management entity.
  • the receiving unit is further configured to receive a VNF instance termination request from the NFVO, where the VNF instance termination request carries a second VNF instance identifier.
  • the determining unit may also be used to determine a container object package identifier that has a mapping relationship with the second VNF instance identifier.
  • the sending unit is further configured to send a container object package delete request to the container management entity, where the container object package delete request carries the determined container object package identifier, wherein the container object package delete request is used to trigger
  • the container management entity terminates the container object instance in the container object package indicated by the container object package identifier, and releases the container runtime instance used by the terminated container object instance.
  • the receiving unit is further configured to receive a second VNF instantiation request from NFVO, where the second VNF instantiation request carries the second VNF instance identifier and the second VNFD identifier.
  • the VNFM further includes an obtaining unit, configured to obtain the number of VM resources and VM resource specifications required by the infrastructure resource pool to be created from the VNFD indicated by the second VNFD identifier.
  • the sending unit is further configured to send a resource allocation request to the virtualization infrastructure manager VIM, where the resource allocation request carries the VM resource specifications and the VM resource quantity of the infrastructure resource pool to be created.
  • the receiving unit is further configured to receive a resource allocation response from the VIM, where the resource allocation response carries the VM instance identifier of the allocated VM instance.
  • the VNFM also includes a labeling unit for labeling the VM instance, and the label is used to indicate that the VM instance is used as a virtual resource for creating a container runtime instance in the infrastructure resource pool.
  • the sending unit is further configured to send the VM instance identifier to the container management entity for management.
  • the container object package file is mapped to Helm Chart, and the container object package instance is mapped to Helm Release.
  • the VNFD further includes a virtualized deployment unit VDU identifier.
  • VDU identifier when the VNF is a VM-based VNF, the VDU attributes contained in the VNFD are allowed to be used, and the container object package attributes referenced by the VNFD are prohibited from being used.
  • VNF when the VNF is a containerized VNF, the VDU attribute contained in the VNFD is allowed or prohibited to be used, and the container object package attribute referenced by the VNFD is allowed to be used.
  • the container object package contains one or more container objects, and each container object is, for example, mapped to an object in an open source de facto standard.
  • the container object is mapped to a Kubernetes object, and the Kubernetes object includes Pod, Service, or Deployment.
  • the container object is, for example, visible to the container management entity and invisible to the management and orchestration entity.
  • the third aspect of the embodiments of the present application also provides a resource pool creation method, including: a virtual network function manager VNFM receives a second virtual network function VNF instantiation request from a network function virtualization orchestrator NFVO, the second VNF instance The transformation request carries the second VNF instance identifier and the second virtualized network function descriptor VNFD identifier.
  • the VNFM obtains the number of VM resources and VM resource specifications required by the infrastructure resource pool to be created from the VNFD indicated by the second VNFD identifier.
  • the VNFM sends a resource allocation request to the virtualized infrastructure manager VIM, where the resource allocation request carries the VM resource specifications and the VM resource quantity of the infrastructure resource pool to be created.
  • the VNFM receives a resource allocation response from the VIM, and the resource allocation response carries the VM instance identifier of the allocated VM instance.
  • the VNFM tags the VM instance, and the tag is used, for example, to indicate that the VM instance is used as a virtual resource for creating a container runtime instance in an infrastructure resource pool.
  • the VNFM sends the VM instance identifier to the container management entity for management.
  • the above example scheme reuses and expands the NFV MANO system’s ability to manage VM resources.
  • the VM resource pool required to deploy a containerized VNF can be regarded as a special type of VNF, and the infrastructure resource pool deployed by the containerized VNF is created through the VNF instantiation process. After the infrastructure resource pool is successfully created, the VNF instantiation process can be further executed.
  • the fourth aspect of the embodiments of the present application also provides a virtual network function manager VNFM, including:
  • the receiving unit is configured to receive a second virtual network function VNF instantiation request from NFVO, where the second VNF instantiation request carries a second VNF instance identifier and a second virtualized network function descriptor VNFD identifier.
  • the acquiring unit is configured to acquire the number of VM resources and VM resource specifications required by the infrastructure resource pool to be created from the VNFD indicated by the second VNFD identifier.
  • the sending unit is configured to send a resource allocation request to the virtualization infrastructure manager VIM, where the resource allocation request carries the VM resource specifications and the VM resource quantity of the infrastructure resource pool to be created;
  • the receiving unit is further configured to receive a resource allocation response from the VIM, where the resource allocation response carries the VM instance identifier of the allocated VM instance.
  • the labeling unit is used to label the VM instance, and the label is used to indicate that the VM instance is used as a virtual resource for creating a container runtime instance in the infrastructure resource pool.
  • the sending unit is further configured to send the VM instance identifier to the container management entity for management.
  • the fifth aspect of the embodiments of the present application also provides a containerized VNF deployment method, including:
  • the VNFM receives the first virtual network function VNF instantiation request from the NFVO, where the first VNF instantiation request carries the first VNF instance identifier and the first VNFD identifier.
  • the VNFM determines the container object package identifier referenced by the VNFD represented by the first VNFD identifier.
  • the VNFM sends a container object package management request to a container management entity, and the container object package management request carries the container object package identifier.
  • the container management entity After receiving the container object package management request, the container management entity creates a container object instance in the container object package indicated by the container object package identifier according to the container object package identifier. Send a container object package management response to the VNFM, where the container object package management response is used to indicate that the container object instance in the container object package is successfully created.
  • the VNFM receives the container object package management response from the container management entity, the VNFM creates the VNF instance represented by the first VNF instance identifier, and maintains (for example, local maintenance) the first VNF instance identifier and the The mapping relationship between the container object package identifiers.
  • creating the container object instance in the container object package represented by the container object package identifier according to the container object package identifier may include, for example, determining the container object referenced by the container object package represented by the container object package identifier
  • the package file creates a container object instance in the container object package according to the container object package file, and schedules the created container object instance to the container runtime instance it uses.
  • the method before the VNFM sends a container object package management request to the container management entity, the method further includes: the VNFM sends a container object package creation request to the container management entity, the container object package creation request Carry the name and/or access address of the container object package file used to create the container object package; the container management entity, after receiving the container object package creation request, according to the name and/or access address of the container object package file Obtain the container object package file, use the container object package file to create the container object package; send a container object package creation response to the VNFM, the container object package creation response carrying the container management entity created The container object package identifier of the container object package.
  • the method may further include: the VNFM receives a VNF instance termination request from the NFVO, wherein the VNF instance termination request carries a second VNF instance identifier; the VNFM determines and The second VNF instance identifies a container object package identifier with a mapping relationship; the VNFM sends a container object package delete request to the container management entity, and the container object package delete request carries the determined container object package identifier.
  • the container management entity After receiving the container object package delete request, the container management entity terminates the container object instance in the container object package indicated by the container object package identifier, and releases the container runtime used by the terminated container object instance Instance.
  • the sixth aspect of the embodiments of the present application further provides a communication system, including: a VNFM and a container management entity.
  • the VNFM is used to receive the first virtual network function VNF instantiation request from the NFVO, and the first VNF instantiation request carries the first VNF instance identifier and the first VNFD identifier.
  • the container management entity is configured to, after receiving the container object package management request, create a container object instance in the container object package indicated by the container object package identifier according to the container object package identifier; and send to the VNFM The container object package management response, wherein the container object package management response is used to indicate that the container object instance in the container object package is successfully created.
  • the VNFM is further configured to receive a container object package management response from the container management entity, the VNFM creates the VNF instance indicated by the first VNF instance identifier, and maintains (for example, maintains locally) the first VNF The mapping relationship between the instance identifier and the container object package identifier.
  • creating the container object instance in the container object package represented by the container object package identifier according to the container object package identifier may include, for example, determining the container object referenced by the container object package represented by the container object package identifier
  • the package file creates a container object instance in the container object package according to the container object package file, and schedules the created container object instance to the container runtime instance it uses.
  • the VNFM is also used to send a container object package creation request to the container management entity before sending a container object package management request to the container management entity, and the container object package creation request carries the creation location. State the name and/or access address of the container object package file used by the container object package.
  • the container management entity is further configured to, after receiving the container object package creation request, obtain the container object package file according to the name and/or access address of the container object package file, and use the container object package file to create the Container object package; sending a container object package creation response to the VNFM, the container object package creation response carrying the container object package identifier of the container object package created by the container management entity.
  • the VNFM is further configured to receive a VNF instance termination request from the NFVO, and the VNF instance termination request carries a second VNF instance identifier; determining that it has a mapping relationship with the second VNF instance identifier The container object package identifier; sends a container object package delete request to the container management entity, and the container object package delete request carries the determined container object package identifier.
  • the container management entity is further configured to, after receiving the container object package delete request, terminate the container object instance in the container object package indicated by the container object package identifier, and release the container object instance used by the terminated container object instance The runtime instance of the container.
  • the seventh aspect of the embodiments of the present application provides a method for deploying a containerized VNF, which includes: a container management entity receives a container object package management request from a virtual network function manager VNFM, wherein the container object package management request carries a virtualized The container object package identifier referenced by the network function descriptor VNFD;
  • the container management entity sends a container object package management response to the VNFM, where the container object package management response is used to indicate that the container object instance in the container object package indicated by the container object package identifier is successfully created.
  • the creating the container object instance in the container object package represented by the container object package identifier according to the container object package identifier may include: determining that the container object package represented by the container object package identifier is referenced The container object package file; create the container object instance in the container object package according to the container object package file; schedule the created container object instance to the container runtime instance it uses.
  • An eighth aspect of the embodiments of the present application provides a container management entity, including:
  • the receiving unit is configured to receive a container object package management request from the virtual network function manager VNFM, where the container object package management request carries the container object package identifier referenced by the virtual network function descriptor VNFD.
  • the creating unit is used for the container management entity to create, according to the container object package identifier, a container object instance in the container object package indicated by the container object package identifier.
  • the sending unit is configured to send a container object package management response to the VNFM, where the container object package management response is used to indicate that the container object instance in the container object package indicated by the container object package identifier is successfully created.
  • the creating the container object instance in the container object package represented by the container object package identifier according to the container object package identifier may include: determining that the container object package represented by the container object package identifier is referenced The container object package file; create the container object instance in the container object package according to the container object package file; schedule the created container object instance to the container runtime instance it uses.
  • the ninth aspect of the embodiments of the present application provides a virtual network function manager VNFM, including: a processor and a memory coupled to each other; wherein the processor is used to call a computer program stored in the memory to complete the embodiments of the present application Part or all of the steps of any method executed by the VNFM.
  • VNFM virtual network function manager
  • a tenth aspect of the embodiments of the present application provides a container management entity including: a processor and a memory coupled with each other; the processor is used to call a computer program stored in the memory to complete the execution of the container management entity in the embodiment of the present application Part or all of the steps of any method.
  • the eleventh aspect of the embodiments of the present application provides a computer-readable storage medium that stores a computer program that is completed when the computer program is executed by a processor to complete the execution of the VNFM in the embodiments of the present application Part or all of the steps of any method.
  • the twelfth aspect of the embodiments of the present application provides a computer-readable storage medium that stores a computer program that is completed when the computer program is executed by a processor to complete the container management entity in the embodiment of the present application. Part or all of the steps of any method performed.
  • Fig. 1-A is a schematic structural diagram of a communication system provided by an embodiment of the present application.
  • FIG. 1B is a schematic diagram of an ETSI NFV MANO standard architecture provided by an embodiment of the present application.
  • Fig. 2 is a schematic diagram of a VM-based VNF information model provided by an embodiment of the present application.
  • FIG. 3 is a schematic diagram of a Kubernetes container management orchestration architecture provided by an embodiment of the present application.
  • FIG. 4 is a schematic diagram of an information model of a containerized VNF provided by an embodiment of the present application.
  • Fig. 5 is a schematic diagram of an enhanced containerized VNFD provided by an embodiment of the present application.
  • FIG. 6 is a schematic flowchart of a method for deploying a containerized VNF provided by an embodiment of the present application.
  • FIG. 7 is a schematic flowchart of a method for instantiating a containerized VNF provided by an embodiment of the present application.
  • FIG. 8 is a schematic flowchart of a method for terminating a containerized VNF instance provided by an embodiment of the present application.
  • FIG. 9 is a schematic flowchart of a method for creating a resource pool provided by an embodiment of the present application.
  • FIG. 10 is a schematic diagram of a VNFM architecture provided by an embodiment of the present application.
  • FIG. 11 is a schematic diagram of another VNFM architecture provided by an embodiment of the present application.
  • FIG. 12 is a schematic diagram of the architecture of a container management entity provided by an embodiment of the present application.
  • FIG. 13 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • NFV standardization work mainly focuses on virtual network functions (VNF, Virtualized Network Function), network services and dynamic management and orchestration of virtual resources (MANO, MAN agement and Orchestration).
  • VNF virtual network functions
  • MANO MAN agement and Orchestration
  • IFA InterFace and Architecture
  • ETSI European Telecommunications Standards Institute
  • NFV orchestrator (NFVO, NFV Orchestrator) can be used to implement network service descriptors (NSD, NS Descriptor), virtual network function forwarding graphs (VNFFG, VNF Forwarding Graph) management And processing, network service life cycle management, cooperate with VNFM to realize VNF life cycle management and have the function of global view of virtual resources.
  • NSD network service descriptor
  • VNFFG virtual network function forwarding graphs
  • VNFF VNF Forwarding Graph
  • VNFM VNF Manager
  • VNFM VNF Manager
  • VNFD virtualized network function descriptor
  • VNFD virtualized network function descriptor
  • instantiation of VNF instantiation of VNF
  • elastic scaling of VNF instances including Scaling out/up and scaling in/down
  • healing of VNF instances and termination of VNF instances also supports receiving the elastic scaling strategy issued by NFVO to realize automatic VNF elastic scaling.
  • Virtualized Infrastructure Manager (VIM, Virtualised Infrastructure Manager) is mainly responsible for the management (including reservation and allocation) of virtualized resources (including virtual computing, storage, and network resources) at the infrastructure layer, the monitoring of virtual resource status, and fault reporting.
  • the upper application provides a virtualized resource pool.
  • Operation and business support systems can refer to the existing operation and maintenance system OSS/BSS of operators.
  • the element management system (EM, Element Manager) performs traditional fault (Fault), user (Account) and configuration (Configuration), performance (Performance) and security (Security) management (referred to as FCAPS management) functions for VNFs.
  • VNF Virtualized network function
  • PNF physical network function
  • EPC nodes packet gateway, service gateway, etc.
  • NFV technical requirements hope that VNF and PNF have the same functional behavior and external interface.
  • NFV Infrastructure is the infrastructure layer of NFV functions, consisting of hardware resources, virtual resources, and a virtualization layer. From the perspective of VNF, the virtualization layer and hardware resources are a complete entity that can provide the required virtual resources.
  • the management object information model in the NFV field is described around the function model, deployment model and resource model of the VNF, which can be specifically shown in Figure 2.
  • the highest-level management object in the NFV field is the network service (NS), and each NS can be composed of one or more VNFs. Further, each VNF may be composed of one or more lower functional level VNF components (VNFC, VNF Component). NS is only visible to NFVO, while VNF is visible to both NFVO and VNFM, and VNFC is only visible to VNFM.
  • NS network service
  • VNF lower functional level VNF components
  • VNFs of the same type for example, vMME or vPGW, etc.
  • VNFD VNF Descriptor File
  • the VNFD may include one or more virtualized deployment units (VDU, Virtualized Deployment Unit) of finer granularity, where each VDU uniquely corresponds to a type of VNFC, which contains the description information required for the deployment and operation of this type of VNFC.
  • VDU virtualized deployment unit
  • the virtualization layer of NFVI abstracts and encapsulates the underlying hardware resources (or physical resources) as a virtual machine (VM, Virtual Machine).
  • the VNF can be deployed on multiple VMs, and each VM uniquely carries the function of a VNFC. Of course, the VNF can also be deployed on one VM.
  • each VDU describes a type of VNFC's demand for infrastructure layer virtual resources (Infrastructure Resources), and the VM allocated by VIM encapsulates the information of infrastructure layer virtual resources that meet this demand.
  • a one-to-one mapping relationship is formed between VNFC, VDU and VM.
  • the host is a hardware resource, and one or more VM instances can be split and created on a host.
  • VM is visible to both NFVO and VNFM, while host resources are not visible to NFVO and VNFM.
  • Kubernetes (K8S) container cluster management technology based on the open source platform. Its core idea is "everything is service-centric, everything revolves around services”. Following this idea, container application systems built on Kubernetes can not only run independently on physical machines, virtual machines or enterprise private clouds, but also be Hosted to the public cloud. Another feature of Kubernetes is automation, a service can be self-scalable, self-diagnostic, and easy to upgrade.
  • the Kubernetes container management orchestration can be shown as an example in Figure 3.
  • Container management orchestration is an important base architecture enhancement feature in the evolution of telecommunications network function virtualization (NFV) to cloud native (CloudNative). It forms interoperability by connecting the NFV MANO system with mature container management platforms (such as Kubernetes) in the industry. Standardized scenarios, from the architecture function to ensure the continuous delivery of containerized VNF in DevOps.
  • the prior art has not yet conducted a detailed analysis of the enhancement of the NFV management object information model after the introduction of the container.
  • An information model of a containerized VNF provided by an embodiment of the present application may be as shown in FIG. 4.
  • the resource model of the containerized VNF introduces an abstract logical resource layer composed of container objects (such as Pod, Service, or Deployment objects in Kubernetes) (such as the server resource in the resource model in Figure 4).
  • the logical resource layer isolates infrastructure resources (such as VM resources) from container-based VNFs.
  • the NFV MANO system manages container objects in the logical resource layer without the need to manage infrastructure resources. The management of infrastructure resources is left to NFVI.
  • Containerized NFV no longer pays attention to which infrastructure resources the VNF functions are deployed on, which makes the deployment of containerized VNFs very different from traditional VM-based VNF deployments.
  • the information model of a containerized VNF and a VM-based VNF are incompatible with each other, when the same type of VNF (such as vMME, etc.) evolves from a VM-based VNF to a containerized VNF, two things are required.
  • An independent VNFD model is used to support the VNF instantiation process, which undoubtedly increases the complexity of VNF deployment.
  • the solution of the embodiment of this application proposes some containerized VNF deployment methods, which can be compatible with supporting VM-based VNF deployment and containerized VNF deployment in a unified VNFD, and promote the smooth evolution of VM-based VNFs in existing networks to containerized VNFs, reducing The complexity of containerized VNF deployment.
  • the resource model of the VNF encapsulates an abstract logical resource layer composed of container objects on the infrastructure resources, that is, service resources.
  • the service resource contains abstracted container objects called Managed Container Infrastructure Objects (MCIO, Managed Container Infrastructure Object).
  • MCIO Managed Container Infrastructure Object
  • the container objects such as Pod, Service, Deployment or ReplicaSets, StatefulSets, etc. in Kubernetes.
  • MCIO or similar objects may also be collectively referred to as container objects, that is, a name of a container object may be MCIO, or may have other names.
  • MCIO is further composed of one or more OS containers.
  • OS containers forms a many-to-many mapping relationship with virtual machines (VM) or bare machines (host) in infrastructure resources.
  • VM virtual machines
  • host bare machines
  • Each MCIO can be deployed on one or more virtual machines or bare machines, and one virtual machine or bare machine can also be deployed One or more MCIOs.
  • VNFC is no longer used in the functional model of containerized VNF, and replaced by VNF service, that is, the function of containerized VNF is service-oriented or micro-service-oriented.
  • MCIOP managed container infrastructure object package
  • VNF Package containerized VNF package file
  • MCIOP is an abstract container object package concept, which can be specifically mapped to container objects that are the de facto standard for containers in the open source field, such as Chart in Helm. MCIOP or similar objects can also be collectively referred to as container object packages. That is, one name of the container object package may be MCIO, of course, the container object package may also have other names.
  • VNFD containerized VNF descriptor file
  • VNFD VNF Descriptor
  • FIG. 5 An enhanced form of a containerized VNF descriptor file (VNFD, VNF Descriptor) can be shown as an example in FIG. 5.
  • the branch of the left VDU in Figure 5 remains unchanged, based on the existing ETSI NFV standard (IFA011GS) definition.
  • a new branch is introduced on the right side of Figure 5 to support the deployment of containerized VNFs.
  • the definition of MCIOP is outside the VNFD, and the VNFD can point to one or more definitions of MCIOP through the index.
  • MCIOP further points to one or more MCIO descriptors or configuration files in MCIOP through the index
  • MCIO descriptors or configuration files further point to the container infrastructure services (CIS, Container Infrastructure) required by each MCIO runtime through the index. Service) description file.
  • the container infrastructure service can also be understood as a container runtime environment (CRE, Container Runtime Environment).
  • the environment encapsulates the requirements for computing/storage/network resources required for container operation and can be mapped to the node object in the open source field Kubernetes.
  • CIS or similar objects can be collectively referred to as container runtime instances.
  • FIG. 1-A is a schematic diagram of a 5G network architecture exemplified in an embodiment of the present application.
  • the 5G network splits certain functional network elements of the 4G network (for example, Mobility Management Entity (MME, Mobility Management Entity), etc.), and defines an architecture based on a service-oriented architecture.
  • MME Mobility Management Entity
  • MMF Session Management Function
  • UE User Equipment
  • DN Data Network
  • the Access and Mobility Management Function is a control plane network element in the 3GPP network, which is mainly responsible for the access control and mobility management of the UE accessing the operator's network.
  • the security anchor function SEAF, Security Anchor Function
  • SEAF may be deployed in the AMF, or the SEAF may also be deployed in another device different from the AMF.
  • the SEAF is deployed in the AMF as an example.
  • SEAF and AMF can be collectively referred to as AMF.
  • the session management function is a control plane network element in the 3GPP network. Among them, the SMF is mainly used to manage the data packet (PDU, Packet Data Unit) session of the UE.
  • the PDU session is a channel used to transmit PDUs.
  • the UE can send PDUs to each other through the PDU session and the DN.
  • SMF is responsible for management work such as establishment, maintenance and deletion of PDU sessions.
  • DN Data Network
  • PDN Packet Data Network
  • a certain DN is a private network of a smart factory, sensors installed on the smart factory workshop play the role of UE, and the sensor control server is deployed in the DN.
  • the UE communicates with the control server. After the UE obtains an instruction from the control server, it can transmit the collected data to the control server according to the instruction.
  • a DN is a company's internal office network, and the terminal used by the company's employees can play the role of a UE, and this UE can access the company's internal information and other resources.
  • the unified data management network element (UDM, Unified Data Management) is also a control plane network element in the 3GPP network.
  • UDM is mainly responsible for storing the subscription data, credential and persistent identity of the subscriber (UE) in the 3GPP network.
  • Identity SUPI, Subscriber Permanent Identifier, etc. These data can be used to authenticate and authorize the UE to access the operator's 3GPP network.
  • the authentication server function (AUSF, Authentication Server Function) is also a control plane network element in the 3GPP network, and the AUSF is mainly used for the first level authentication (that is, the 3GPP network authenticates its subscribers).
  • the Network Exposure Function (NEF, Network Exposure Function) is also a control plane network element in the 3GPP network.
  • NEF is mainly responsible for opening the external interface of the 3GPP network to third parties in a safe manner.
  • NEF when network elements such as SMF need to communicate with third-party network elements, NEF can be used as a communication relay.
  • NEF when relaying, NEF can translate internal and external logos. For example, when sending the UE's SUPI from the 3GPP network to a third party, the NEF can translate the SUPI into its corresponding external identity (ID, Identity). Conversely, NEF can translate the external identity ID into the corresponding SUPI when sending it to the 3GPP network.
  • ID external identity
  • the network storage function (NRF, Network Repository Function) is also a control plane network element in the 3GPP network. It is mainly responsible for storing the configuration service profile of the accessible network function (NF) and providing it for other network elements. Discovery service for network functions.
  • User Plane Function is the gateway for the communication between the 3GPP network and the DN.
  • the Policy Control Function (PCF, Policy Control Function) is a control plane function in the 3GPP network, which is used to provide the SMF with the policy of the PDU session.
  • Policies can include billing, quality of service (QoS, Quality of Service), authorization-related policies, etc.
  • the Access Network (AN, Access Network) is a sub-network of the 3GPP network. To access the 3GPP network, the UE first needs to go through the AN. In the radio access scenario, AN is also called Radio Access Network (RAN, Radio Access Network), so the two terms RAN and AN are often mixed without distinction.
  • RAN Radio Access Network
  • the 3GPP network refers to a network that complies with 3GPP standards.
  • the part other than UE and DN in Figure 1-A can be regarded as a 3GPP network.
  • 3GPP networks are not limited to 5G networks defined by 3GPP, but can also include 2G, 3G, and 4G networks.
  • 3GPP networks are operated by operators.
  • N1, N2, N3, N4, N6, etc. in the architecture shown in FIG. 1-A respectively represent reference points between related network elements/network functions. Nausf, Namf... etc. respectively represent service-oriented interfaces of related network functions.
  • 3GPP networks and non-3GPP networks may coexist, and some network elements in the 5G network may also be used in some non-5G networks.
  • part or all of the core network functions in the 5G architecture shown in Figure 1-A can be virtualized.
  • Part or all of the core network functions in 3G or 4G or other network architectures can also be virtualized, and no examples are given here.
  • the following provides related processes such as the deployment method of the containerized VNF and the termination method of the containerized VNF instance.
  • FIG. 6 is a schematic flowchart of a method for deploying a containerized VNF according to an embodiment of the application.
  • the method for deploying a containerized VNF may include:
  • the NFVO sends a first VNF instantiation request to the VNFM, where the first VNF instantiation request carries the first VNF instance identifier and the first VNFD identifier.
  • the first VNF instance listed by the first VNF instance identifier is the VNF instance to be instantiated.
  • the VNFM receives the first virtual network function VNF instantiation request from the NFVO, and the VNFM determines the container object package identifier referenced by the VNFD represented by the first VNFD identifier.
  • the VNFM sends a container object package management request to a container management entity, where the container object package management request carries the container object package identifier.
  • the container management entity in the embodiment of the present application may be, for example, a container infrastructure service manager (CISM, Container Infrastructure Service Management) in the ETSI NFV standard.
  • CISM Container Infrastructure Service Management
  • the container management entity receives a container object package management request from the VNFM, and the container management entity creates a container object instance in the container object package represented by the container object package identifier according to the container object package identifier.
  • creating the container object instance in the container object package represented by the container object package identifier according to the container object package identifier may include, for example, determining the container object referenced by the container object package represented by the container object package identifier
  • the package file creates a container object instance in the container object package according to the container object package file, and schedules the created container object instance to the container runtime instance it uses.
  • the container management entity sends a container object package management response to the VNFM, where the container object package management response is used to indicate that the container object instance in the container object package indicated by the container object package identifier is successfully created.
  • the VNFM receives a container object package management response from a container management entity, the VNFM creates a VNF instance represented by the first VNF instance identifier, and maintains (for example, local maintenance or non-local maintenance) the first VNF The mapping relationship between the instance identifier and the container object package identifier.
  • the VNFM sends a first VNF instantiation response for responding to the first VNF instantiation request to the NFVO.
  • the container object's requirements for infrastructure resources can be described in the descriptor file corresponding to the container object in the container object package.
  • the scheduler in the container management entity can schedule the container object to a container runtime instance with the infrastructure resource capability (for example, a node of Kubernetes).
  • the VNFD model is enhanced so that the VNFD model can refer to the container object package identifier, so that the VNFD supports the deployment of the containerized VNF.
  • the VNFM initiates the management operation of the corresponding container object package to the container management entity according to the reference relationship of the VNFD to the container object package, and there is no need to deal with the management of container objects and infrastructure resources (VM or bare metal) on the interface between the VNFM and the container management entity. operating. Due to the increased compatibility of VNFDs for the deployment of containerized VNFs, it is beneficial to promote smoother evolution of VM-based VNFs in existing networks to containerized VNFs, thereby reducing the deployment complexity of containerized VNFs.
  • the container object package file may be mapped to Helm Chart, and the container object package instance may be mapped to Helm Release.
  • the VNFD may also include a virtualization deployment unit (VDU) identifier.
  • VDU virtualization deployment unit
  • the VNF is a VM-based VNF
  • the VDU attributes contained in the VNFD are allowed to be used, and the container object package attributes referenced by the VNFD are prohibited from being used.
  • the VNF is a containerized VNF
  • the VDU attribute contained in the VNFD is allowed or prohibited to be used, and the container object package attribute referenced by the VNFD is allowed to be used.
  • the container object package may contain one or more container objects, and each container object is, for example, mapped to an object in an open source de facto standard.
  • the container object may be mapped to a Kubernetes object, where the Kubernetes object includes Pod, Service, or Deployment, for example.
  • the container object is visible to the container management entity but not to the management and orchestration entity.
  • the method further includes: the VNFM sends a container object package creation request to the container management entity, and the container object package creation request carries the creation of the container object package The name and/or access address of the container object package file used.
  • the container management entity obtains the container object package file according to the name and/or access address of the container object package file, and uses the container object package file to create the container object package;
  • the VNFM sends a container object package creation response, and the container object package creation response carries the container object package identifier of the container object package created by the container management entity.
  • the VNFM receives a container object package creation response from the container management entity.
  • the VNF instance can also be terminated.
  • the VNFM receives a VNF instance termination request from the NFVO, and the VNF instance termination request carries the second VNF instance identifier.
  • the VNFM determines a container object package identifier that has a mapping relationship with the second VNF instance identifier.
  • the VNFM sends a container object package delete request to the container management entity, the container object package delete request carries the determined container object package identifier, and the container object package delete request is used to trigger the container management entity to terminate the
  • the container object package identifier indicates the container object instance in the container object package, and the container runtime instance used by the terminated container object instance is released.
  • the VNFM can also create an infrastructure resource pool, and the infrastructure resource pool can provide virtual resources for creating container runtime instances.
  • the VNFM receives a second VNF instantiation request from the NFVO, and the second VNF instantiation request carries the second VNF instance identifier and the second VNFD identifier.
  • the VNFM obtains the number of VM resources and VM resource specifications required by the infrastructure resource pool to be created from the VNFD indicated by the second VNFD identifier.
  • the VNFM sends a resource allocation request to the virtualized infrastructure manager VIM, where the resource allocation request carries the VM resource specifications and the VM resource quantity of the infrastructure resource pool to be created.
  • the VNFM receives a resource allocation response from the VIM, and the resource allocation response carries the VM instance identifier of the allocated VM instance.
  • the VNFM tags the VM instance, and the tag is used to indicate that the VM instance is used as a virtual resource for creating a container runtime instance in the infrastructure resource pool.
  • the VNFM sends the VM instance identifier to the container management entity for management.
  • FIG. 7 is a schematic flowchart of a method for instantiating a containerized VNF provided by an embodiment of the application.
  • the method may include:
  • the NFVO sends a VNF instantiation request to the VNFM, where the VNF instantiation request carries the requested VNF identification and the VNFD identification.
  • the VNFM receives the VNF instantiation request from the NFVO, and the VNFM parses the VNF instantiation request to obtain the VNF identification and the VNFD identification carried in the VNF instantiation request.
  • the VNFM determines the MCIOP identifier referenced by the VNFD represented by the VNFD identifier.
  • the VNFM sends an MCIOP management request to the CISM, where the MCIOP management request carries the determined MCIOP identifier.
  • the MCIOP files indexed by MCIOP can all be included in the VNF package file, and the loading process of the VNF package file has been completed.
  • the VNF package file is in the corresponding directory library ( Catalog) is ready.
  • the CISM receives the MCIOP management request from the VNFM.
  • CISM can access the MCIOP indicated by the MCIOP identifier, determine the MCIOP file indexed in the MCIOP accessed (such as the MCIO descriptor file and the MCIO configuration file), use the MCIOP file root to create the MCIO instance in MCIOP, The created MCIO instance is scheduled to its CIS instance.
  • the CISM sends a MCIOP management response for responding to the MCIOP management request to the VNFM, where the container object package management response is used to indicate that the MCIO instance in the MCIOP is successfully created.
  • the VNFM receives the MCIOP management response from the CISM for responding to the MCIOP management request, the VNFM creates the VNF instance represented by the VNF instance identifier, and locally maintains the mapping relationship between the VNF instance identifier and the MCIOP identifier.
  • the VNFM sends a VNF instantiation response for responding to the VNF instantiation request to the NFVO.
  • the VNF instantiation response can be used to notify the end of the VNF instantiation process.
  • VNFD the VNFD model is enhanced to make the container object package identifier that the VNFD model can refer to, so that the VNFD supports the deployment of containerized VNF.
  • VNFM initiates management operations corresponding to MCIOP to CISM according to the reference relationship of VNFD to MCIOP, and there is no need to process management operations for MCIO and infrastructure resources (VM or bare metal) on the VNFM and CISM interfaces. Due to the increased compatibility of VNFDs for the deployment of containerized VNFs, it is beneficial to promote smoother evolution of VM-based VNFs in existing networks to containerized VNFs, thereby reducing the deployment complexity of containerized VNFs.
  • FIG. 8 is a schematic flowchart of a method for terminating a containerized VNF instance provided by an embodiment of the application, and the method may include:
  • the NFVO sends a VNF instance termination request to the VNFM, and the VNF instance termination request carries the VNF instance identifier of the VNF instance to be terminated.
  • the VNFM receives the VNF instance termination request from NFVO, and the VNFM obtains the MCIOP corresponding to the VNF instance to be terminated through the mapping relationship between the VNF instance identifier and the MCIOP identifier maintained locally.
  • the VNFM sends an MCIOP deletion request to the CISM, where the MCIOP deletion request carries the MCIOP identifier.
  • the CISM receives the MCIOP delete request from the VNFM, and the CISM terminates the MCIO instance in the MCIOP and releases the CIS instance used by the MCIO instance (for example, in Kubernetes, the node resource used by the Pod object is released back to the node resource pool).
  • the CISM sends an MCIOP deletion response to the VNFM to respond to the MCIOP deletion request.
  • the VNFM receives the MCIOP deletion response from the CISM.
  • the VNFM can further terminate the VNF instance and release the mapping relationship between the VNF instance identifier and the MCIOP table. Further, the VNFM sends a VNF instance termination response for responding to the VNF instance termination request to the NFVO, and the VNF instance termination response is used to notify the termination of the VNF instance termination process.
  • FIG. 9 is a schematic flowchart of a method for creating an infrastructure resource pool deployed by a containerized VNF according to an embodiment of the application.
  • the method may include:
  • the NFVO initiates a VNF instantiation request to the VNFM, where the VNF instantiation request carries the VNF instance identifier and the VNFD identifier.
  • the VNFM receives the VNF instantiation request from the NFVO, and the VNFM accesses the VNFD indicated by the VNFD identifier, and obtains the number of VM resources and the VM resource specifications required to create the infrastructure resource pool from the VNFD.
  • the VNFM sends a resource allocation request to the VIM, where the resource allocation request carries the VM resource specifications and the VM resource quantity of the infrastructure resource pool to be created.
  • the VIM receives the resource allocation request from the VNFM, and the VIM sends a resource allocation response for responding to the resource allocation request to the VNFM.
  • the resource allocation response carries the VM instance identifier of the allocated VM instance.
  • the VNFM receives the resource allocation response from the VIM, and the VNFM tags the VM instance allocated by the VIM.
  • the label is used to indicate that the VM instance is used as a virtual resource used to create a CIS instance in the infrastructure resource pool (for example, in the corresponding Kubernetes Node resource pool), and send the identities of these VM instances to the CISM for management (ie entrusted management).
  • the VNFM sends a VNF instantiation response message for responding to the VNF instantiation request to the NFVO.
  • the VNF instantiation response can be used to notify the end of the infrastructure resource pool creation process.
  • this embodiment reuses and expands the NFV MANO system's ability to manage VM resources, creating deployments The infrastructure resource pool required for containerized VNF.
  • this embodiment regards the VM resource pool required to deploy the containerized VNF as a special VNF, and creates the infrastructure resource pool deployed by the containerized VNF through the VNF instantiation process. After the infrastructure resource pool is successfully created, the VNF instantiation process shown in FIG. 7 can be further executed.
  • an embodiment of the present application also provides a VNFM 1000, including:
  • the receiving unit 1010 is configured to receive a first virtual network function VNF instantiation request from NFVO, where the first VNF instantiation request carries a first VNF instance identifier and a first virtualized network function descriptor VNFD identifier.
  • the determining unit 1020 is configured to determine the container object package identifier referenced by the VNFD represented by the first VNFD identifier.
  • the sending unit 1030 is configured to send a container object package management request to a container management entity, where the container object package management request carries the container object package identifier.
  • the receiving unit 1010 is further configured to receive a container object package management response from the container management entity, where the container object package management response is used to indicate the container object instance in the container object package indicated by the container object package identifier Created successfully.
  • the creation management unit 1040 is configured to create the VNF instance represented by the first VNF instance identifier, and maintain the mapping relationship between the first VNF instance identifier and the container object package identifier.
  • the container object package management request is used to trigger the container management entity to create, according to the container object package identifier, a container object instance in the container object package indicated by the container object package identifier. Specifically, for example, the container object package file referenced by the container object package indicated by the container object package identifier is determined, the container object instance in the container object package is created according to the container object package file, and the created container The object instance is dispatched to the container runtime instance it uses.
  • the sending unit 1030 is further configured to send a container object package creation request to the container management entity before sending the container object package management request to the container management entity, the container object package creation request Carry the name and/or access address of the container object package file used to create the container object package.
  • the receiving unit 1010 is further configured to receive a container object package creation response from the container management entity, where the container object package creation response carries the container object package identifier of the container object package created by the container management entity.
  • the receiving unit 1010 is further configured to receive a VNF instance termination request from the NFVO, where the VNF instance termination request carries a second VNF instance identifier.
  • the determining unit 1020 is further configured to determine a container object package identifier that has a mapping relationship with the second VNF instance identifier;
  • the sending unit 1030 is further configured to send a container object package delete request to the container management entity, where the container object package delete request carries the determined container object package identifier, wherein the container object package delete request is used for
  • the container management entity is triggered to terminate the container object instance in the container object package indicated by the container object package identifier, and release the container runtime instance used by the terminated container object instance.
  • the receiving unit 1010 is further configured to receive a second VNF instantiation request from NFVO, where the second VNF instantiation request carries a second VNF instance identifier and a second VNFD identifier.
  • the VNFM further includes an obtaining unit 1050, configured to obtain the number of VM resources and VM resource specifications required by the infrastructure resource pool to be created from the VNFD indicated by the second VNFD identifier.
  • the sending unit 1030 is further configured to send a resource allocation request to the virtualization infrastructure manager VIM, where the resource allocation request carries the VM resource specifications and the number of VM resources of the infrastructure resource pool to be created.
  • the receiving unit 1010 is further configured to receive a resource allocation response from the VIM, where the resource allocation response carries the VM instance identifier of the allocated VM instance.
  • the VNFM further includes a labeling unit 1060, which is used to label the VM instance, and the label is used to indicate that the VM instance is used as a virtual resource used to create a container runtime instance in the infrastructure resource pool.
  • a labeling unit 1060 which is used to label the VM instance, and the label is used to indicate that the VM instance is used as a virtual resource used to create a container runtime instance in the infrastructure resource pool.
  • the sending unit 1030 is further configured to send the VM instance identifier to the container management entity for management.
  • the container object package file is mapped to Helm Chart, and the container object package instance is mapped to Helm Release.
  • the VNFD further includes a virtualized deployment unit VDU identifier; where, when the VNF is a VM-based VNF, the VDU attributes contained in the VNFD are allowed to be used, and the container object package attributes referenced by the VNFD are prohibited Use: When the VNF is a containerized VNF, the VDU attributes contained in the VNFD are allowed or prohibited to be used, and the container object package attributes referenced by the VNFD are allowed to be used.
  • the container object package contains one or more container objects, and each container object is mapped to an object in the open source de facto standard.
  • the container object is mapped to a Kubernetes object, the Kubernetes object includes Pod, Service, or Deployment, and the container object is visible to the container management entity but not to the management and orchestration entity.
  • each functional module of the VNFM 1100 can be implemented with reference to the methods shown in Figure 6-9 for example.
  • the receiving unit 1010 may perform the actions performed by the VNFM in steps 901 and 904.
  • the sending unit 1030 can perform the actions performed by the VNFM in steps 903 and 906,
  • the creation management unit 1040 can perform the actions performed by the VNFM in step 606, and so on.
  • an embodiment of the present application also provides another VNFM 1100, including:
  • the receiving unit 1110 is configured to receive a second virtual network function VNF instantiation request from NFVO, where the second VNF instantiation request carries a second VNF instance identifier and a second virtualized network function descriptor VNFD identifier.
  • the obtaining unit 1120 is configured to obtain the number of VM resources and VM resource specifications required by the infrastructure resource pool to be created from the VNFD indicated by the second VNFD identifier.
  • the sending unit 1130 is configured to send a resource allocation request to the virtualization infrastructure manager VIM, where the resource allocation request carries the VM resource specifications and the VM resource quantity of the infrastructure resource pool to be created.
  • the receiving unit 1110 is further configured to receive a resource allocation response from the VIM, where the resource allocation response carries the VM instance identifier of the allocated VM instance.
  • the labeling unit 1140 is configured to label the VM instance, and the label is used to indicate that the VM instance is used as a virtual resource for creating a container runtime instance in the infrastructure resource pool.
  • the sending unit 1130 is further configured to send the VM instance identifier to the container management entity for management.
  • each functional module of the VNFM 1100 can be implemented with reference to the method shown in FIG. 9 for example.
  • the receiving unit 1110 may perform the actions performed by the VNFM in steps 901 and 904.
  • the sending unit 1130 can perform the actions performed by the VNFM in steps 903 and 906, and so on.
  • an embodiment of the present application further provides a container management entity 1200, including:
  • the receiving unit 1210 is configured to receive a container object package management request from the virtual network function manager VNFM, where the container object package management request carries the container object package identifier referenced by the virtual network function descriptor VNFD.
  • the creating unit 1220 is used for the container management entity to create a container object instance in the container object package indicated by the container object package identifier according to the container object package identifier.
  • the sending unit 1230 is configured to send a container object package management response to the VNFM, where the container object package management response is used to indicate that the container object instance in the container object package indicated by the container object package identifier is successfully created.
  • the creating the container object instance in the container object package represented by the container object package identifier according to the container object package identifier may include: determining that the container object package represented by the container object package identifier is referenced The container object package file; create the container object instance in the container object package according to the container object package file; schedule the created container object instance to the container runtime instance it uses.
  • Each functional module can cooperate to perform part or all of the actions performed by the container management entity (such as CISM).
  • an embodiment of the present application also provides a general communication device 1300, which can implement the functions of the VNFM, NFVO or container management entity provided in the above embodiments, and specifically includes:
  • the processor 1310 and the memory 1320 are coupled to each other.
  • the processor 1310 is used to call a computer program stored in the memory 1320 to complete part or all of the steps of any method executed by the VNFM in the embodiment of the present application.
  • processor 1310 may also call different computer programs stored in the memory 1320 to complete part or all of the steps of any method executed by the NFVO or the container management entity in the embodiment of the present application.
  • the processor 1310 is also called a central processing unit (CPU, Central Processing Unit).
  • the components of the image prediction device are coupled together, for example, through a bus system.
  • the bus system may include a power bus, a control bus, and a status signal bus in addition to a data bus.
  • the methods disclosed in the foregoing embodiments of the present application may be applied to the processor 1310 or implemented by the processor 1310.
  • the processor 1310 may be an integrated circuit chip with signal processing capabilities. In some implementation processes, part or all of the steps of the foregoing method may be completed by an integrated logic circuit of hardware in the processor 1310 or instructions in the form of software.
  • the processor 1310 may be a general-purpose processor, a digital signal processor, an application specific integrated circuit, an off-the-shelf programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component.
  • the processor 1310 can implement or execute the methods, steps, and logical block diagrams disclosed in the embodiments of the present application.
  • the general-purpose processor 1310 may be a microprocessor or the processor may also be any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present application can be directly embodied as being executed and completed by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a mature storage medium in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory or registers.
  • the storage medium is located in the memory 1320.
  • the processor 1310 can read information in the memory 1320 and complete some or all of the steps of the foregoing method in combination with its hardware.
  • the embodiment of the present application also provides a computer-readable storage medium, the computer-readable storage medium stores a computer program, the computer program is executed by hardware (such as a processor, etc.), and is executed by any device in the embodiment of the present application Part or all of the steps of any method.
  • the embodiments of the present application also provide a computer program product including instructions, which when the computer program product runs on a computer device, cause the computer device to perform part or all of the steps of any one of the above aspects.
  • the computer program product includes one or more computer instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website, computer, server, or data center.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or data center integrated with one or more available media.
  • the usable medium may be a magnetic medium (such as a floppy disk, a hard disk, and a magnetic tape), an optical medium (such as an optical disk), or a semiconductor medium (such as a solid state hard disk).
  • the disclosed device may also be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components can be combined or integrated. To another system, or some features can be ignored or not implemented.
  • the displayed or discussed indirect coupling or direct coupling or communication connection between each other may be through some interfaces, indirect coupling or communication connection between devices or units, and may be in electrical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed to multiple network units. . Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • the functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the above-mentioned integrated unit may be implemented in the form of hardware, or may also be implemented in the form of software functional unit.
  • the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium.
  • the technical solution of the application essentially or the part that 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,
  • a number of instructions are included to enable a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application.
  • the aforementioned storage medium may include, for example: U disk, mobile hard disk, Read-Only Memory (ROM), Random Access Memory (RAM, Random Access Memory), magnetic disks or optical disks and other storable program codes. Medium.

Landscapes

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

Abstract

一种容器化VNF的部署方法和相关设备。其中，一种容器化VNF的部署方法包括：VNFM接收来自NFVO的第一VNF实例化请求，其中，第一VNF实例化请求携带第一VNF实例标识和第一虚拟化网络功能描述符VNFD标识；确定第一VNFD标识所表示的VNFD所引用的容器对象包标识；向容器管理实体发送容器对象包管理请求，接收来自容器管理实体的容器对象包管理响应，容器对象包管理响应用于指示容器对象包中的容器对象实例创建成功；创建第一VNF实例标识所表示的VNF实例，维护第一VNF实例标识与容器对象包标识之间的映射关系。所述方法有利于降低容器化VNF的部署的复杂度。

Description

容器化VNF的部署方法和相关设备 技术领域
本申请涉及通信技术领域，尤其涉及容器化VNF的部署方法和相关设备。
背景技术
网络功能虚拟化(NFV,Network Function Virtualization)是指电信网络运营商借鉴了信息技术(IT,Information Technology)领域的虚拟化技术，在通用的服务器、交换机和存储器等设备中将部分电信网络功能(例如：核心网功能)的实现进行软件和硬件解耦，从而实现网络服务(NS,Network Service)快速、高效部署和运营，同时，达到节省网络投资成本和运营成本的目标。通过应用NFV技术，电信网络功能以软件方式实现，并可以在通用的服务器硬件上运行，可以根据需要来进行迁移、实例化、部署在网络的不同物理位置，并且不需要安装新设备。
其中，容器即服务(CaaS,Container as a Service)例如可看作是一种特定类型的平台即服务(PaaS,Platform as a Service)服务。通常而言，容器(Container)是一种操作***级别的虚拟化技术，通过操作***隔离技术如Linux下的CGroup和NameSpace，将不同的进程隔离开来。容器技术不同于硬件虚拟化(Hypervisor)技术，并没有虚拟硬件，容器内部也没有操作***，只有进程。由于容器技术的这个重要特点，使得容器相比虚拟机更轻量，管理也更方便。在容器的运行态，定义了一组公共的管理操作，具体例如：启动、停止、暂停和删除等等，对容器进行统一的生命周期管理。
由于容器化VNF支撑的应用形态服务化或者微服务化，通常容器化VNF的部署机制实现复杂度较高。
发明内容
本申请实施例提供容器化VNF的部署方法和相关设备，有利于降低容器化VNF的部署复杂度。
本申请实施例第一方面提供一种容器化VNF的部署方法，包括：
网络功能虚拟化编排器(NFVO)向虚拟网络功能管理器(VNFM,VNF Manager)发送第一VNF实例化请求。虚拟网络功能管理器(VNFM)接收来自网络功能虚拟化编排器(NFVO)的第一VNF实例化请求。其中，所述第一VNF实例化请求携带第一VNF实例标识和第一虚拟化网络功能描述符(VNFD,VNF Descriptor)标识。所述VNFM确定所述第一VNFD标识所表示的VNFD所引用的容器对象包标识(容器对象包例如为被管理的容器基础设施对象包(MCIOP))。
所述VNFM向容器管理实体(容器管理实体例如为容器基础设施服务管理实体CISM)发送容器对象包管理请求，所述容器对象包管理请求携带所述容器对象包标识。所述VNFM接收来自所述容器管理实体的容器对象包管理响应，所述容器对象包管理响应用于指示所述容器对象包标识所表示的容器对象包中的容器对象实例(其中，容器对象例如为被管理的容器基础设施对象(MCIO))创建成功。其中，容器对象包管理响应例如可携带创建成功的容器对象实例的容器对象实例标识等。
所述VNFM创建所述第一VNF实例标识所表示的VNF实例，并维护(例如本地维护)所述第一VNF实例标识与所述容器对象包标识之间的映射关系。
其中，所述容器对象包管理请求例如可用于触发所述容器管理实体根据所述容器对象包标识创建所述容器对象包标识所表示的容器对象包中的容器对象实例。所述容器管理实体根据所述容器对象包标识创建所述容器对象包标识所表示的容器对象包中的容器对象实例例如可包括：确定所述容器对象包标识所表示的容器对象包所引用的容器对象包文件，根据所述容器对象包文件创建所述容器对象包中的容器对象实例(例如为容器基础设施对象)，并可将创建的所述容器对象实例调度到其使用的容器运行时实例(容器运行时实例例如为容器基础设施服务(CIS)实例)上。
所述容器对象包内包含一个或多个容器对象，每个容器对象例如可映射为开源事实标准中的对象。其中，所述容器对象例如可映射为Kubernetes对象，所述Kubernetes对象例如包括Pod、Service或Deployment等。
在一些可能的实施方式中，所述容器对象包文件例如可映射为Helm Chart，容器对象包实例例如可映射为Helm Release。
在一些可能的实施方式中，例如所述容器对象对容器管理实体可见且对管理和编排实体不可见。
可以看出，本申请实施例提供的容器化VNF的部署方案中，通过对VNFD进行模型增强而使得VNFD可引用容器对象包标识，进而使VNFD支持容器化VNF的部署。VNFM根据VNFD对容器对象包的引用关系，来向容器管理实体发起对应容器对象包的管理操作，且在VNFM和容器管理实体接口上可无需处理面向容器对象和基础设施资源(VM或裸机)的管理操作。由于增加了VNFD对容器化VNF的部署的兼容支持，有利于促使现网中基于VM的VNF更平滑的向容器化VNF演进，进而降低容器化VNF的部署复杂度。
在一些可能实施方式中，VNFM向容器管理实体发送容器对象包管理请求之前，所述方法还包括：所述VNFM向所述容器管理实体发送容器对象包创建请求，所述容器对象包创建请求携带创建所述容器对象包所使用的容器对象包文件的名称和/或访问地址。所述VNFM接收来自所述容器管理实体的容器对象包创建响应，所述容器对象包创建响应携带所述容器管理实体创建的所述容器对象包的容器对象包标识。其中，容器对象包创建请求例如可用于触发所述容器管理实体在接收所述容器对象包创建请求之后，根据容器对象包文件的名称和/或访问地址获取所述容器对象包文件，使用所述容器对象包文件创建所述容器对象包；向所述VNFM发送容器对象包创建响应，所述容器对象包创建响应携带所述容器管理实体创建的所述容器对象包的容器对象包标识。
当需要终结某些VNF实例，例如可基于如下流程来进行VNF实例终结。在一些可能的实施方式中，所述VNFM可接收来自所述NFVO的VNF实例终结请求，所述VNF实例终结请求携带第二VNF实例标识；所述VNFM确定与所述第二VNF实例标识具有映射关系的容器对象包标识；所述VNFM向所述容器管理实体发送容器对象包删除请求，所述容器对象包删除请求携带确定的所述容器对象包标识。其中，所述容器对象包删除请求例如可用于触发所述容器管理实体终结所述容器对象包标识所表示的容器对象包中的容器对象实例，并释放终结的所述容器对象实例所使用的容器运行时实例。
在一些可能的实施方式中，还可通过如下方式来创建基础设施资源池，举例来说，所述方法还包括：所述VNFM接收来自NFVO的第二VNF实例化请求，其中，所述第二VNF实例化请求携带第二VNF实例标识(其中，第二VNF实例标识则为要终结的VNF实例的VNF实例标识)和第二VNFD标识；所述VNFM从所述第二VNFD标识所表示的VNFD中获取待创建的基础设施资源池所需的VM资源数量和VM资源规格；所述VNFM向虚拟化基础设施管理器VIM发送资源分配请求，其中，所述资源分配请求携带待创建的基础设施资源池的VM资源规格和VM资源数量；所述VNFM接收来自所述VIM的资源分配响应，所述资源分配响应中携带所分配的VM实例的VM实例标识；所述VNFM给所述VM实例打标签，所述标签用于指示所述VM实例作为基础设施资源池中创建容器运行时实例所使用的虚拟资源；所述VNFM将所述VM实例标识发送给容器管理实体进行纳管(即委托容器管理实体管理这些VM资源)。
在一些可能实施方式中，所述VNFD还可包含虚拟化部署单元(VDU)标识。当VNF为基于VM的VNF，所述VNFD包含的VDU属性允许使用，所述VNFD引用的容器对象包属性禁止使用；当VNF为容器化VNF，所述VNFD包含的VDU属性允许使用或禁止使用，所述VNFD引用的容器对象包属性允许使用。
其中，通过上述举例的属性使用约束，可以更好控制资源分配的流程走向，有利于简化处理复杂度。
本申请实施例第二方面提供一种虚拟网络功能管理器VNFM，包括：
接收单元，用于接收来自NFVO的第一虚拟网络功能VNF实例化请求，所述第一VNF实例化请求携带第一VNF实例标识和第一虚拟化网络功能描述符VNFD标识。
确定单元，用于确定所述第一VNFD标识所表示的VNFD所引用的容器对象包标识。
发送单元，用于向容器管理实体发送容器对象包管理请求，所述容器对象包管理请求携带所述容器对象包标识。
所述接收单元还用于，接收来自所述容器管理实体的容器对象包管理响应，其中，所述容器对象包管理响应用于指示所述容器对象包标识所表示的容器对象包中的容器对象实例创建成功。
创建管理单元，用于创建所述第一VNF实例标识所表示的VNF实例，并本地维护所述第一VNF实例标识与所述容器对象包标识之间的映射关系。
其中，所述容器对象包管理请求例如可用于触发所述容器管理实体在确定所述容器对象包标识所表示的容器对象包所引用的容器对象包文件之后，根据所述容器对象包文件创建所述容器对象包中的容器对象实例，并将创建的所述容器对象实例调度到其使用的容器运行时实例上。
在一些可能实施方式中，所述发送单元可还用于，在向容器管理实体发送容器对象包管理请求之前，向所述容器管理实体发送容器对象包创建请求，所述容器对象包创建请求携带创建所述容器对象包所使用的容器对象包文件的名称和/或访问地址。
所述接收单元还用于，接收来自所述容器管理实体的容器对象包创建响应，所述容器对象包创建响应携带所述容器管理实体创建的所述容器对象包的容器对象包标识。
在一些可能实施方式中，接收单元还用于接收来自所述NFVO的VNF实例终结请求，所述VNF实例终结请求携带第二VNF实例标识。
其中，所述确定单元还可用于，确定与所述第二VNF实例标识具有映射关系的容器对象包标识。
所述发送单元还用于，向所述容器管理实体发送容器对象包删除请求，所述容器对象包删除请求携带确定的所述容器对象包标识，其中，所述容器对象包删除请求用于触发所述容器管理实体终结所述容器对象包标识所表示的容器对象包中的容器对象实例，并释放终结的所述容器对象实例所使用的容器运行时实例。
在一些可能实施方式中，接收单元还用于接收来自NFVO的第二VNF实例化请求，所述第二VNF实例化请求携带第二VNF实例标识和第二VNFD标识。
所述VNFM还包括获取单元，用于从所述第二VNFD标识所表示的VNFD中获取待创建的基础设施资源池所需的VM资源数量和VM资源规格。
所述发送单元还用于，向虚拟化基础设施管理器VIM发送资源分配请求，所述资源分配请求携带待创建的基础设施资源池的VM资源规格和VM资源数量。
所述接收单元还用于，接收来自所述VIM的资源分配响应，所述资源分配响应中携带所分配的VM实例的VM实例标识。
所述VNFM还包括标签单元，用于给所述VM实例打标签，所述标签用于指示所述VM实例作为基础设施资源池中创建容器运行时实例所使用的虚拟资源。
所述发送单元还用于将所述VM实例标识发送给容器管理实体进行纳管。
在一些可能实施方式中，所述容器对象包文件映射为Helm Chart，容器对象包实例映射为Helm Release。
在一些可能的实施方式中，所述VNFD还包含虚拟化部署单元VDU标识。其中，当VNF为基于VM的VNF，所述VNFD包含的VDU属性允许使用，所述VNFD引用的容器对象包属性禁止使用。当VNF为容器化VNF，所述VNFD包含的VDU属性允许使用或禁止使用，所述VNFD引用的容器对象包属性允许使用。
在一些可能实施方式中，所述容器对象包内包含一个或多个容器对象，每个容器对象例如映射为开源事实标准中的对象。
在一些可能实施方式中，所述容器对象映射为Kubernetes对象，所述Kubernetes对象包括Pod、Service或Deployment。
在一些可能实施方式中，所述容器对象例如对容器管理实体可见且对管理和编排实体不可见。
本申请实施例第三方面还提供一种资源池创建方法，包括：虚拟网络功能管理器VNFM接收来自网络功能虚拟化编排器NFVO的第二虚拟网络功能VNF实例化请求，所述第二VNF实例化请求携带第二VNF实例标识和第二虚拟化网络功能描述符VNFD标识。
所述VNFM从所述第二VNFD标识所表示的VNFD中获取待创建的基础设施资源池所需的VM资源数量和VM资源规格。
所述VNFM向虚拟化基础设施管理器VIM发送资源分配请求，所述资源分配请求携带待创建的基础设施资源池的VM资源规格和VM资源数量。
所述VNFM接收来自所述VIM的资源分配响应，所述资源分配响应中携带所分配的VM实例的VM实例标识。所述VNFM给所述VM实例打标签，所述标签例如用于指示所述VM实 例作为基础设施资源池中创建容器运行时实例所使用的虚拟资源。所述VNFM将所述VM实例标识发送给容器管理实体进行纳管。
可以看出，为降低容器化VNF所部属的基础设施资源池管理的复杂度，提高基础设施资源池管理的效率和可靠性，上述举例方案复用和扩展NFV MANO***对VM资源管理的能力，创建部署容器化VNF所需的基础设施资源池。具体可将署容器化VNF所需的VM资源池看作是一种特殊的VNF，通过VNF实例化过程创建容器化VNF所部署的基础设施资源池。在基础设施资源池创建成功之后，可进一步执行VNF实例化过程。
本申请实施例第四方面还提供一种虚拟网络功能管理器VNFM，包括：
接收单元，用于接收来自NFVO的第二虚拟网络功能VNF实例化请求，所述第二VNF实例化请求携带第二VNF实例标识和第二虚拟化网络功能描述符VNFD标识。
获取单元，用于从所述第二VNFD标识所表示的VNFD中获取待创建的基础设施资源池所需的VM资源数量和VM资源规格。
发送单元，用于向虚拟化基础设施管理器VIM发送资源分配请求，所述资源分配请求携带待创建的基础设施资源池的VM资源规格和VM资源数量；
所述接收单元还用于，接收来自所述VIM的资源分配响应，所述资源分配响应中携带所分配的VM实例的VM实例标识。
标签单元，用于给所述VM实例打标签，所述标签用于指示所述VM实例作为基础设施资源池中创建容器运行时实例所使用的虚拟资源。
所述发送单元还用于，将所述VM实例标识发送给容器管理实体进行纳管。
本申请实施例第五方面还提供一种容器化VNF的部署方法，包括：
VNFM接收来自NFVO的第一虚拟网络功能VNF实例化请求，所述第一VNF实例化请求携带第一VNF实例标识和第一VNFD标识。
所述VNFM确定所述第一VNFD标识所表示的VNFD所引用的容器对象包标识。
所述VNFM向容器管理实体发送容器对象包管理请求，所述容器对象包管理请求携带所述容器对象包标识。
所述容器管理实体在接收所述容器对象包管理请求之后，根据所述容器对象包标识创建所述容器对象包标识所表示的容器对象包中的容器对象实例。向所述VNFM发送容器对象包管理响应，所述容器对象包管理响应用于指示所述容器对象包中的容器对象实例创建成功。
所述VNFM接收来自所述容器管理实体的容器对象包管理响应，所述VNFM创建所述第一VNF实例标识所表示的VNF实例，并维护(例如本地维护)所述第一VNF实例标识与所述容器对象包标识之间的映射关系。
其中，根据所述容器对象包标识创建所述容器对象包标识所表示的容器对象包中的容器对象实例，例如可包括：确定所述容器对象包标识所表示的容器对象包所引用的容器对象包文件，根据所述容器对象包文件创建所述容器对象包中的容器对象实例，将创建的所述容器对象实例调度到其使用的容器运行时实例上。
在一些可能的实施方式中，VNFM向容器管理实体发送容器对象包管理请求之前，所述方法还包括：所述VNFM向所述容器管理实体发送容器对象包创建请求，所述容器对象包创 建请求携带创建所述容器对象包所使用的容器对象包文件的名称和/或访问地址；所述容器管理实体在接收所述容器对象包创建请求之后，根据容器对象包文件的名称和/或访问地址获取所述容器对象包文件，使用所述容器对象包文件创建所述容器对象包；向所述VNFM发送容器对象包创建响应，所述容器对象包创建响应携带所述容器管理实体创建的所述容器对象包的容器对象包标识。
在一些可能的实施方式中，所述方法还可包括：所述VNFM接收来自所述NFVO的VNF实例终结请求，其中，所述VNF实例终结请求携带第二VNF实例标识；所述VNFM确定与所述第二VNF实例标识具有映射关系的容器对象包标识；所述VNFM向所述容器管理实体发送容器对象包删除请求，所述容器对象包删除请求携带确定的所述容器对象包标识。
所述容器管理实体在接收所述容器对象包删除请求之后，终结所述容器对象包标识所表示的容器对象包中的容器对象实例，并且释放终结的所述容器对象实例所使用的容器运行时实例。
本申请实施例第六方面还提供一种通信***，包括：VNFM和容器管理实体。
其中，VNFM用于接收来自NFVO的第一虚拟网络功能VNF实例化请求，所述第一VNF实例化请求携带第一VNF实例标识和第一VNFD标识。确定所述第一VNFD标识所表示的VNFD所引用的容器对象包标识。向容器管理实体发送容器对象包管理请求，所述容器对象包管理请求携带所述容器对象包标识。
所述容器管理实体用于，在接收所述容器对象包管理请求之后，根据所述容器对象包标识创建所述容器对象包标识所表示的容器对象包中的容器对象实例；向所述VNFM发送容器对象包管理响应，其中，所述容器对象包管理响应用于指示所述容器对象包中的容器对象实例创建成功。
所述VNFM还用于，接收来自所述容器管理实体的容器对象包管理响应，所述VNFM创建所述第一VNF实例标识所表示的VNF实例，并维护(例如本地维护)所述第一VNF实例标识与所述容器对象包标识之间的映射关系。
其中，根据所述容器对象包标识创建所述容器对象包标识所表示的容器对象包中的容器对象实例，例如可包括：确定所述容器对象包标识所表示的容器对象包所引用的容器对象包文件，根据所述容器对象包文件创建所述容器对象包中的容器对象实例，将创建的所述容器对象实例调度到其使用的容器运行时实例上。
在一些可能的实施方式之中，VNFM还用于，在向容器管理实体发送容器对象包管理请求之前，向所述容器管理实体发送容器对象包创建请求，所述容器对象包创建请求携带创建所述容器对象包所使用的容器对象包文件的名称和/或访问地址。
所述容器管理实体还用于，在接收所述容器对象包创建请求之后，根据容器对象包文件的名称和/或访问地址获取所述容器对象包文件，使用所述容器对象包文件创建所述容器对象包；向所述VNFM发送容器对象包创建响应，所述容器对象包创建响应携带所述容器管理实体创建的所述容器对象包的容器对象包标识。
在一些可能的实施方式中，所述VNFM还用于接收来自所述NFVO的VNF实例终结请求，所述VNF实例终结请求携带第二VNF实例标识；确定与所述第二VNF实例标识具有映射关系的容器对象包标识；向所述容器管理实体发送容器对象包删除请求，所述容器对象包删 除请求携带确定的所述容器对象包标识。
所述容器管理实体还用于，在接收所述容器对象包删除请求之后，终结所述容器对象包标识所表示的容器对象包中的容器对象实例，并且释放终结的所述容器对象实例所使用的容器运行时实例。
本申请实施例第七方面提供一种容器化VNF的部署方法，包括：容器管理实体接收来自虚拟网络功能管理器VNFM的容器对象包管理请求，其中，所述容器对象包管理请求携带被虚拟化网络功能描述符VNFD引用的容器对象包标识；
所述容器管理实体根据所述容器对象包标识创建所述容器对象包标识所表示的容器对象包中的容器对象实例；
所述容器管理实体向所述VNFM发送容器对象包管理响应，所述容器对象包管理响应用于指示所述容器对象包标识所表示的容器对象包中的容器对象实例创建成功。
举例来说，所述根据所述容器对象包标识创建所述容器对象包标识所表示的容器对象包中的容器对象实例，可包括：确定所述容器对象包标识所表示的容器对象包所引用的容器对象包文件；根据所述容器对象包文件创建所述容器对象包中的容器对象实例；将创建的所述容器对象实例调度到其使用的容器运行时实例上。
本申请实施例第八方面提供一种容器管理实体，包括：
接收单元，用于接收来自虚拟网络功能管理器VNFM的容器对象包管理请求，所述容器对象包管理请求携带被虚拟化网络功能描述符VNFD引用的容器对象包标识。
创建单元，用于所述容器管理实体根据所述容器对象包标识创建所述容器对象包标识所表示的容器对象包中的容器对象实例。
发送单元，用于向所述VNFM发送容器对象包管理响应，所述容器对象包管理响应用于指示所述容器对象包标识所表示的容器对象包中的容器对象实例创建成功。
举例来说，所述根据所述容器对象包标识创建所述容器对象包标识所表示的容器对象包中的容器对象实例，可包括：确定所述容器对象包标识所表示的容器对象包所引用的容器对象包文件；根据所述容器对象包文件创建所述容器对象包中的容器对象实例；将创建的所述容器对象实例调度到其使用的容器运行时实例上。
本申请实施例第九方面提供一种虚拟网络功能管理器VNFM，包括：相互耦合的处理器和存储器；其中，所述处理器用于调用所述存储器中存储的计算机程序，以完成本申请实施例中由VNFM执行的任意一种方法的部分或全部步骤。
本申请实施例第十方面提供一种容器管理实体包括：相互耦合的处理器和存储器；所述处理器用于调用所述存储器中存储的计算机程序，以完成本申请实施例中由容器管理实体执行的任意一种方法的部分或全部步骤。
本申请实施例第十一方面提供一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序，所述计算机程序被处理器执行时完成以完成本申请实施例中由VNFM执行的任意一种方法的部分或全部步骤。
本申请实施例第十二方面提供一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序，所述计算机程序被处理器执行时完成以完成本申请实施例中由容器管理实体执行的任意一种方法的部分或全部步骤。
附图说明
下面将对本申请实施例涉及的一些附图进行说明。
图1-A是本申请实施例提供的一种通信***的架构示意图。
图1-B是本申请实施例提供的一种ETSI NFV MANO标准架构的示意图。
图2是本申请实施例提供的一种基于VM的VNF信息模型的示意图。
图3是本申请实施例提供的一种Kubernetes容器管理编排架构示意图。
图4是本申请实施例提供的一种容器化VNF的信息模型的示意图。
图5是本申请实施例提供的一种增强的容器化VNFD的示意图。
图6是本申请实施例提供的一种容器化VNF的部署方法的流程示意图。
图7是本申请实施例提供的一种容器化VNF的实例化方法的流程示意图。
图8是本申请实施例提供的一种容器化VNF实例的终结方法的流程示意图。
图9是本申请实施例提供的一种资源池创建方法的流程示意图。
图10是本申请实施例提供的一种VNFM的架构示意图。
图11是本申请实施例提供的另一种VNFM的架构示意图。
图12是本申请实施例提供的一种容器管理实体的架构示意图。
图13是本申请实施例提供的一种通信设备的架构示意图。
具体实施方式
下面结合本申请实施例中的附图对本申请实施例方案进行描述。
NFV标准化工作主要集中在虚拟网络功能(VNF,Virtualized Network Function)、网络服务和虚拟资源的动态管理和编排(MANO,MAN agement and Orchestration)。一般由欧洲通信标准协会(ETSI,European Telecommunications Standards Institute)之下的NFV行业标准组的接口与架构(IFA,InterFace and Architecture)工作组来完成MANO框架内的功能制订工作等，其功能架构可如图1-B所示。
其中，在图1-B所示架构中，NFV编排器(NFVO,NFV Orchestrator)可以用于实现网络服务描述符(NSD,NS Descriptor)，虚拟网络功能转发图(VNFFG,VNF Forwarding Graph)的管理和处理，网络服务生命周期的管理，和VNFM配合实现VNF的生命周期管理并具有虚拟资源的全局视图功能。
VNF管理器(VNFM,VNF Manager)可执行虚拟化网络功能VNF的生命周期管理，包括虚拟化网络功能描述符(VNFD,VNF Descriptor)的管理、VNF的实例化、VNF实例的弹性伸缩(可包括扩容Scaling out/up和缩容Scaling in/down)、VNF实例的治愈(healing)和VNF实例终止。VNFM还支持接收NFVO下发的弹性伸缩(scaling)策略，实现自动化的VNF弹性伸缩。
虚拟基础设施管理器(VIM,Virtualised Infrastructure Manager)主要负责基础设施层虚拟化资源(包括虚拟计算、存储和网络资源)的管理(包括预留和分配)，虚拟资源状态的监控和故障上报，面向上层应用提供虚拟化资源池。
运营和商务支撑***(OSS/BSS,Operations and Business Support Systems)可指运营商现有的运行维护***OSS/BSS。
网元管理***(EM,Element Manager)针对VNF执行传统的故障(Fault)、用户(Account)和配置(Configuration)、性能(Performance)和安全(Security)的管理(可简称：FCAPS管理)功能。
虚拟化网络功能(VNF,Virtualized Network Function)对应于传统非虚拟化网络中的物理网络功能(PNF)，如虚拟化的EPC节点(分组网关，服务网关等)。其中，网络功能的功能性行为和状态与虚拟化与否无关，NFV技术需求希望VNF和PNF拥有相同的功能性行为和外部接口。
NFV基础架构(NFVI,NFV Infrastructure)是NFV功能的基础设施层，由硬件资源和虚拟资源以及虚拟化层组成。从VNF的角度来说，虚拟化层和硬件资源是一个能够提供所需虚拟资源的完整实体。
NFV领域的管理对象信息模型围绕VNF的功能模型、部署模型和资源模型来描述，具体可如图2所示。
在功能模型(也称为功能视图)中，NFV领域最高阶的管理对象是网络服务(NS)，每个NS可以由一个或者多个VNF组成。进一步地，每个VNF又可以由一个或多个更低功能级别的VNF组件(VNFC,VNF Component)来组成。NS仅对NFVO可见，而VNF对NFVO和VNFM都可见，VNFC仅对VNFM可见。
在部署模型(也称为部署视图)中，同一类的VNF(例如vMME或vPGW等等)唯一对应VNF描述符文件(VNFD)，并使用该VNFD创建一个或多个VNF实例。在VNFD中可包含一个或多个更细颗粒的虚拟化部署单元(VDU,Virtualized Deployment Unit)，其中，每个VDU唯一对应一类VNFC，其中包含该类VNFC部署和运行所需的描述信息。
在资源模型(也称为资源视图)中，NFVI的虚拟化层将底层的硬件资源(或称物理资源)抽象并封装为虚拟机(VM,Virtual Machine)。VNF可部署在多个VM上，每个VM唯一承载一个VNFC的功能，当然VNF也可部署在一个VM上。在VNFD中，每个VDU描述一类VNFC对基础设施层虚拟资源(Infrastructure Resource)的需求，而VIM分配的VM则封装了满足该需求的基础设施层虚拟资源的信息。从功能模型到部署模型到资源模型，VNFC和VDU、VM之间形成了一一映射关系。其中，主机(host)是硬件资源，在一个主机上可以切分创建一个或多个VM实例。VM对NFVO和VNFM都可见，而主机资源对NFVO和VNFM不可见。
CaaS架构在电信网络功能云化进程中的引入,为电信行业的开发运维(DevOps)带来了敏捷性的变革。其中，与之相呼应的变化是，传统大颗粒单体网络功能逐渐被解构进行服务化，甚至进一步进行微服务化。每个服务化的功能独立进行开发、交付和维护，版本的升级变得更加频繁；但另一方面，容器化网络功能数量的激增，并不会对互操作测试带来指数级工作量的增长，稳定的API接口定义保证了接口功能调用的一致性和可靠性。
当前在容器管理编排领域最流行的应用是Google公司基于开源平台的Kubernetes(简称K8S)容器集群管理技术。它的核心思想是“一切以服务为中心，一切围绕服务运转”，遵循这一思想，在Kubernetes上构建的容器应用***不仅可以独立运行在物理机、虚拟机或企业私有云上，也可以被托管到公有云上。Kubernetes的另一个特点是自动化，一个服务可自我扩缩容、自我诊断，并且容易升级。Kubernetes容器管理编排可如图3举例所示。
容器管理编排是电信网络功能虚拟化(NFV)向云原生(CloudNative)演进中的一个重要 的底座架构增强特性，通过连接NFV MANO***和业内应用成熟的容器管理平台(如Kubernetes)形成互操作的标准化场景，从架构功能保障容器化VNF在DevOps的持续交付。现有技术尚未对引入容器后的NFV管理对象信息模型的增强展开详细分析。
本申请实施例提供的一种容器化VNF的信息模型可如图4所示。其中，容器化VNF的资源模型引入了由容器对象(例如：Kubernetes中的Pod、Service或Deployment对象)组成抽象的逻辑资源层(如图4中的资源模型中的server resource)。逻辑资源层将基础设施资源(例如VM资源)和基于容器实现的VNF隔离，NFV MANO***管理逻辑资源层的容器对象，而无需管理基础设施资源，基础设施资源的管理留给NFVI实现。
由于容器化VNF只对抽象的逻辑资源层的容器对象可见。容器化NFV不再关注VNF的功能部署在哪些基础设施资源上，使得容器化VNF的部署和传统基于VM的VNF部署有很大区别。另一方面，当容器化VNF和基于VM实现的VNF的信息模型互不兼容，则当同一类型的VNF(例如vMME等等)从基于VM的VNF实现向容器化VNF实现演变时，需有两套独立的VNFD模型来支持进行VNF的实例化过程，这无疑增加了VNF部署的复杂度。
本申请实施例方案提出一些容器化VNF的部署方法，可在统一的VNFD中兼容支持基于VM的VNF部署和容器化VNF的部署，促使现网中基于VM的VNF平滑向容器化VNF演进，降低容器化VNF部署的复杂度。
与基于图2所示的VM的VNF信息模型相比，VNF的资源模型在基础设施资源上封装了抽象的由容器对象组成的逻辑资源层，即服务资源(service resource)。
具体例如图4举例所示，服务资源中包含了经过抽象的容器对象称被管理的容器基础设施对象(MCIO,Managed Container Infrastructure Object)，这些抽象的容器对象,可以具体映射为开源领域容器事实标准的容器对象，具体例如Kubernetes中的Pod、Service、Deployment或ReplicaSets、StatefulSets等等。其中，MCIO或类似对象也可统称为容器对象，即容器对象的一种名称可为MCIO，也可具有其他名称。
通常，MCIO如何映射为开源领域容器事实标准中的容器对象，本申请不做限定。在服务资源层，MCIO进一步由一个或多个OS container组成。MCIO与基础设施资源中的虚机(VM)或裸机(host)形成多对多的映射关系，每个MCIO可部署在一个或多个虚机或裸机上，而一个虚机或裸机也可部署一个或多个MCIO。
容器化VNF的功能模型中不再使用VNFC，取而代之的是VNF服务，即：容器化VNF的功能服务化或微服务化。
并且，容器化VNF的部署模型也可不再强制使用VDU概念，取而代之的是被管理的容器基础设施对象包(MCIOP,Managed Container Infrastructure Object Package)。MCIOP由资源模型中一个或多个MCIO组成，MCIOP中包含了这些MCIO的描述符文件和配置文件，并放入容器化VNF的包文件(VNF Package)中。VNF服务和MCIOP之间没有显式的映射关系，通常在VNFD中通过索引(例如指针)指向放在VNF包中的一个或多个MCIOP。其中，MCIOP是抽象的容器对象包概念，它可具体映射为开源领域容器事实标准的容器对象，例如Helm中的Chart。MCIOP或类似对象也可统称为容器对象包。即容器对象包的一种名称可为MCIO，当然容器对象包也可具有其他名称。
容器化VNF描述符文件(VNFD,VNF Descriptor)的一种增强形态可如图5举例所示。图5 中左侧VDU的分支仍然保持不变，基于现有ETSI NFV标准(IFA011GS)定义。并且，图5中右侧引入新的分支，用于支持容器化VNF的部署。MCIOP的定义位于VNFD之外，VNFD可以通过索引指向一个或多个MCIOP的定义。其中，MCIOP进一步通过索引指向MCIOP中一个或多个MCIO的描述符或配置文件，MCIO的描述符或配置文件，进一步通过索引指向每个MCIO运行时所需的容器基础设施服务(CIS,Container Infrastructure Service)的描述文件。容器基础设施服务也可以理解为容器运行时环境(CRE,Container Runtime Environment)，环境中封装了容器运行所需的计算/存储/网络资源的需求，可映射为开源领域Kubernetes中的node对象。CIS或类似对象可统称为容器运行时实例。
下面举例一些可能存在网络功能虚拟化的网络架构。
参见图1-A，图1-A是本申请实施例举例的一种5G网络架构的示意图。其中，5G网络对4G网络的某些功能网元(例如移动性管理实体(MME，Mobility Management Entity)等等)进行了一定拆分，并定义了基于服务化架构的架构。在图1-A所示网络架构中，类似4G网络中的MME的功能，被拆分成了接入与移动性管理功能(AMF,Access and Mobility Management Function)和会话管理功能(SMF,Session Management Function)等等。
下面对其他一些相关网元/实体进行介绍。
用户设备(UE，User Equipment)通过接入运营商网络来访问数据网络(DN，Data Network)等等，使用DN上的由运营商或第三方提供的业务。
接入与移动性管理功能(AMF)是3GPP网络中的一种控制面网元，主要负责UE接入运营商网络的接入控制和移动性管理。其中，安全锚点功能(SEAF,Security Anchor Function)可以部署于AMF之中，或SEAF也可能部署于不同于AMF的另一设备中，图1-A中以SEAF被部署于AMF中为例。当SEAF被部署于AMF中时，SEAF和AMF可合称AMF。
会话管理功能(SMF)是3GPP网络中的一种控制面网元，其中，SMF主要用于负责管理UE的数据包(PDU,Packet Data Unit)会话。PDU会话是一个用于传输PDU的通道，UE可以通过PDU会话与DN互相发送PDU。SMF负责PDU会话的建立、维护和删除等管理工作。
数据网络(DN,Data Network)也称为分组数据网络(PDN,Packet Data Network)，是位于3GPP网络之外的网络。其中，3GPP网络可接入多个DN，DN上可部署运营商或第三方提供的多种业务。例如，某个DN是一个智能工厂的私有网络，安装在智能工厂车间的传感器扮演UE的角色，DN中部署了传感器的控制服务器。UE与控制服务器通信，UE在获取控制服务器的指令之后，可根据这个指令将采集的数据传递给控制服务器。又例如，DN是一个公司的内部办公网络，该公司员工所使用的终端则可扮演UE的角色，这个UE可以访问公司内部的信息和其他资源。
其中，统一数据管理网元(UDM，Unified Data Management)也是3GPP网络中的一种控制面网元，UDM主要负责存储3GPP网络中签约用户(UE)的签约数据、信任状(credential)和持久身份标识(SUPI,Subscriber Permanent Identifier)等。这些数据可以被用于UE接入运营商3GPP网络的认证和授权。
认证服务器功能(AUSF,Authentication Server Function)也是3GPP网络中的一种控制面网元，AUSF主要用于第一级认证(即3GPP网络对其签约用户的认证)。
其中，网络开放功能(NEF,Network Exposure Function)也是3GPP网络之中的一种控制 面网元。NEF主要负责以安全的方式对第三方开放3GPP网络的对外接口。其中，在SMF等网元需要与第三方网元通信时，可以以NEF为通信的中继。其中，中继时，NEF可以进行内外部标识的翻译。比如，将UE的SUPI从3GPP网络发送到第三方时，NEF可以将SUPI翻译成其对应的外部身份标识(ID,Identity)。反之，NEF可以将外部身份ID在发送到3GPP网络时，将其翻译成对应的SUPI。
其中，网络存储功能(NRF,Network Repository Function)也是3GPP网络中的一种控制面网元，主要负责存储可被访问的网络功能(NF)的配置额服务资料(profile)，为其他网元提供网络功能的发现服务。
用户面功能(UPF,User Plane Function)是3GPP网络与DN通信的网关。
策略控制功能(PCF,Policy Control Function)是3GPP网络中的一种控制面功能，用于向SMF提供PDU会话的策略。策略可包括计费、服务质量(QoS,Quality of Service)、授权相关策略等。
接入网(AN，Access Network)是3GPP网络的一个子网络，UE要接入3GPP网络，首先需要经过AN。在无线接入场景下AN也称无线接入网(RAN,Radio Access Network),因此RAN和AN这两个术语经常不做区分的混用。
其中，3GPP网络是指符合3GPP标准的网络。其中，图1-A中除了UE和DN以外的部分可看作是3GPP网络。3GPP网络不只局限于3GPP定义的5G网络，还可包括2G、3G、4G网络。通常3GPP网络由运营商来运营。此外，在图1-A所示架构中的N1、N2、N3、N4、N6等分别代表相关网元/网络功能之间的参照点(Reference Point)。Nausf、Namf...等分别代表相关网络功能的服务化接口。当然，3GPP网络和非3GPP网络可能共存，5G网络的中的一些网元也可能被运用到一些非5G网络中。
例如图1-A所示5G架构中的部分或全部核心网功能均可被虚拟化。3G或4G或其他网络架构中部分或全部核心网功能也可被虚拟化，此处不再一一举例。
基于上述举例的架构和概念，下面提供容器化VNF的部署方法和容器化VNF实例的终结方法等的相关流程。
参见图6，图6为本申请实施例提供的一种容器化VNF的部署方法的流程示意图，容器化VNF的部署方法方法可包括：
601.NFVO向VNFM发送第一VNF实例化请求，所述第一VNF实例化请求携带第一VNF实例标识和第一VNFD标识。
其中，第一VNF实例标识所表的第一VNF实例为待实例化的VNF实例。
602.VNFM接收来自NFVO的第一虚拟网络功能VNF实例化请求，所述VNFM确定第一VNFD标识所表示的VNFD所引用的容器对象包标识。
603.所述VNFM向容器管理实体发送容器对象包管理请求，所述容器对象包管理请求携带所述容器对象包标识。
其中，本申请实施例中的容器管理实体例如可以是ETSI NFV标准中的容器基础设施服务管理器(CISM,Container Infrastructure Service Management)。
604.容器管理实体接收来自VNFM的容器对象包管理请求，容器管理实体根据所述容器对象包标识创建所述容器对象包标识所述表示的容器对象包中的容器对象实例。
其中，根据所述容器对象包标识创建所述容器对象包标识所述表示的容器对象包中的容器对象实例例如可包括：确定所述容器对象包标识所表示的容器对象包所引用的容器对象包文件，根据所述容器对象包文件创建所述容器对象包中的容器对象实例，并将创建的所述容器对象实例调度到其使用的容器运行时实例上。
605.容器管理实体向VNFM发送容器对象包管理响应，所述容器对象包管理响应用于指示所述容器对象包标识所表示的容器对象包中的容器对象实例创建成功。
606.所述VNFM接收来自容器管理实体的容器对象包管理响应，所述VNFM创建所述第一VNF实例标识所表示的VNF实例，并维护(例如本地维护或非本地维护)所述第一VNF实例标识与所述容器对象包标识之间的映射关系。
607.VNFM向NFVO发送用于响应第一VNF实例化请求的第一VNF实例化响应。
其中，容器对象对基础设施资源(例如：VM)的需求,可以在容器对象包中对应该容器对象的描述符文件中描述。当容器管理实体创建容器对象时，容器管理实体中的调度器可将容器对象调度到具有该基础设施资源能力的容器运行时实例上(例如Kubernetes的node)。
可以看出，上述容器化VNF的部署方案中，通过对VNFD模型进行增强而使得VNFD模型可引用容器对象包标识，进而使得VNFD支持容器化VNF的部署。VNFM根据VNFD对容器对象包的引用关系来向容器管理实体发起对应容器对象包的管理操作，且在VNFM和容器管理实体接口上可无需处理面向容器对象和基础设施资源(VM或裸机)的管理操作。由于增加了VNFD对容器化VNF的部署的兼容支持，有利于促使现网中基于VM的VNF更平滑的向容器化VNF演进，进而降低容器化VNF的部署复杂度。
在一些可能实施方式中，所述容器对象包文件可映射为Helm Chart，容器对象包实例可映射为Helm Release。
在一些可能实施方式中，所述VNFD还可以包含虚拟化部署单元(VDU)标识。当VNF为基于VM的VNF，VNFD包含的VDU属性允许使用，所述VNFD引用的容器对象包属性禁止使用。当VNF为容器化VNF，所述VNFD包含的VDU属性允许使用或禁止使用，所述VNFD引用的容器对象包属性允许使用。
在一些可能实施方式中，容器对象包内可包含一个或多个容器对象，每个容器对象例如映射为开源事实标准中的对象。
举例来说，所述容器对象例如可映射为Kubernetes对象，其中，所述Kubernetes对象例如包括Pod、Service或Deployment。
举例来说，所述容器对象例如对容器管理实体可见且对管理和编排实体不可见。
进一步的，VNFM向容器管理实体发送容器对象包管理请求之前，方法还包括：所述VNFM向所述容器管理实体发送容器对象包创建请求，所述容器对象包创建请求携带创建所述容器对象包所使用的容器对象包文件的名称和/或访问地址。容器管理实体在接收所述容器对象包创建请求之后，根据容器对象包文件的名称和/或访问地址获取所述容器对象包文件，使用所述容器对象包文件创建所述容器对象包；向所述VNFM发送容器对象包创建响应，所述容器对象包创建响应携带所述容器管理实体创建的所述容器对象包的容器对象包标识。所述VNFM接收来自所述容器管理实体的容器对象包创建响应。
进一步的，还可对VNF实例进行终结。具体例如：VNFM接收来自所述NFVO的VNF实例终 结请求，所述VNF实例终结请求携带第二VNF实例标识。VNFM确定与所述第二VNF实例标识具有映射关系的容器对象包标识。所述VNFM向所述容器管理实体发送容器对象包删除请求，所述容器对象包删除请求携带确定的所述容器对象包标识，所述容器对象包删除请求用于触发所述容器管理实体终结所述容器对象包标识所表示的容器对象包中的容器对象实例，并释放终结的所述容器对象实例所使用的容器运行时实例。
进一步的，VNFM还可创建基础设施资源池，基础设施资源池可为创建容器运行时实例提供虚拟资源。
具体例如，所述VNFM接收来自NFVO的第二VNF实例化请求，所述第二VNF实例化请求携带第二VNF实例标识和第二VNFD标识。所述VNFM从所述第二VNFD标识所表示的VNFD中获取待创建的基础设施资源池所需的VM资源数量和VM资源规格。所述VNFM向虚拟化基础设施管理器VIM发送资源分配请求，所述资源分配请求携带待创建的基础设施资源池的VM资源规格和VM资源数量。所述VNFM接收来自所述VIM的资源分配响应，所述资源分配响应中携带所分配的VM实例的VM实例标识。所述VNFM给所述VM实例打标签，所述标签用于指示所述VM实例作为基础设施资源池中创建容器运行时实例所使用的虚拟资源。所述VNFM将所述VM实例标识发送给容器管理实体进行纳管。
参见图7，图7为本申请实施例提供的一种容器化VNF的实例化方法的流程示意图，方法可以包括：
701.NFVO向VNFM发送VNF实例化请求，其中，所述VNF实例化请求携带请求VNF标识和VNFD标识。
702.VNFM接收来自NFVO的VNF实例化请求，VNFM解析所述VNF实例化请求以得到所述VNF实例化请求携带的VNF的标识和VNFD标识。所述VNFM确定所述VNFD标识所表示的VNFD所引用的MCIOP标识。
703.VNFM向CISM发送MCIOP管理请求，其中，所述MCIOP管理请求携带确定的所述MCIOP标识。
在本步骤之前，MCIOP所索引的MCIOP文件(如MCIO描述符文件和MCIO配置文件)可都包含在VNF包文件中，并已经完成VNF包文件的加载过程，VNF包文件在相应的目录库(Catalog)中就绪。
704.CISM接收来自VNFM的MCIOP管理请求。
其中，CISM可访问所述MCIOP标识所表示的MCIOP，确定访问的所述MCIOP中所索引的MCIOP文件(如MCIO描述符文件和MCIO配置文件)，使用MCIOP文件根创建MCIOP中的MCIO实例，将创建的所述MCIO实例调度到其CIS实例上。
705.CISM向VNFM发送用于响应MCIOP管理请求的MCIOP管理响应，所述容器对象包管理响应用于指示所述MCIOP中的MCIO实例创建成功。
706.接收来自CISM的用于响应MCIOP管理请求的MCIOP管理响应，VNFM创建所述VNF实例标识所表示的VNF实例，并本地维护所述VNF实例标识与所述MCIOP标识之间的映射关系。VNFM向NFVO发送用于响应VNF实例化请求的VNF实例化响应。VNF实例化响应可用于通知VNF实例化过程结束。
可以看出，上述容器化VNF的实例化方案中，通过对VNFD模型进行增强而使得VNFD模型 可引用的容器对象包标识，进而使得VNFD支持容器化VNF的部署。VNFM根据VNFD对MCIOP的引用关系来向CISM发起对应MCIOP的管理操作，且在VNFM和CISM接口上可无需处理面向MCIO和基础设施资源(VM或裸机)的管理操作。由于增加了VNFD对容器化VNF的部署的兼容支持，有利于促使现网中基于VM的VNF更平滑的向容器化VNF演进，进而降低容器化VNF的部署复杂度。
参见图8，图8为本申请实施例提供的一种容器化VNF实例的终结方法的流程示意图，方法可包括：
801.NFVO向VNFM发送VNF实例终结请求，VNF实例终结请求中携带要终结的VNF实例的VNF实例标识。
802.VNFM接收来自NFVO的VNF实例终结请求，VNFM通过本地维护的VNF实例标识与MCIOP标识之间的映射关系，获取要终结的VNF实例对应的MCIOP。
803.VNFM向CISM发送MCIOP删除请求，所述MCIOP删除请求携带MCIOP标识。
804.CISM接收来自VNFM的MCIOP删除请求，CISM终结MCIOP中的MCIO实例，并释放MCIO实例所使用的CIS实例(具体例如：在Kubernetes中将Pod对象所使用的node资源释放回节点资源池)。
805.CISM向VNFM发送用于响应MCIOP删除请求的MCIOP删除响应。
806.VNFM接收来自CISM的MCIOP删除响应，VNFM可进一步终结VNF实例，并释放VNF实例标识和MCIOP表之间的映射关系。进一步的，VNFM向NFVO发送用于响应VNF实例终结请求的VNF实例终结响应，VNF实例终结响应用于通知VNF实例的终结过程结束。
可以看出，上述流程提供了一种便捷的VNF实例的终结机制，使得VNF实例的终结变得简单易操作。
参见图9，图9为本申请实施例提供的一种容器化VNF所部署的基础设施资源池创建方法的流程示意图，方法可包括：
901.NFVO向VNFM发起VNF实例化请求，其中，所述VNF实例化请求携带VNF实例标识和VNFD标识。
902.VNFM接收来自NFVO的VNF实例化请求，VNFM访问所述VNFD标识所表示的VNFD，从所述VNFD中获取创建基础设施资源池所需的VM资源数量和VM资源规格。
903.VNFM向VIM发送资源分配请求，所述资源分配请求携带待创建的基础设施资源池的VM资源规格和VM资源数量。
904.VIM接收来自VNFM的资源分配请求，VIM向VNFM发送用于响应资源分配请求的资源分配响应，资源分配响应中携带所分配的VM实例的VM实例标识。
905.VNFM接收来自VIM的资源分配响应，VNFM将VIM分配的VM实例打上标签，所述标签用于指示所述VM实例作为基础设施资源池中创建CIS实例所使用的虚拟资源(如对应Kubernetes中的节点资源池)，并将这些VM实例的标识发送给CISM进行纳管(即委托管理)。
906.VNFM向NFVO发送用于响应VNF实例化请求的VNF实例化响应消息，VNF实例化响应可用于通知基础设施资源池创建过程结束。
其中，为了降低容器化VNF所部属的基础设施资源池管理的复杂度，提高基础设施资源池管理的效率和可靠性，本实施例复用和扩展NFV MANO***对VM资源管理的能力，创建部 署容器化VNF所需的基础设施资源池。其中，本实施例将署容器化VNF所需的VM资源池看作是一种特殊的VNF，通过VNF实例化过程创建容器化VNF所部署的基础设施资源池。在基础设施资源池创建成功之后，可进一步执行图7举例所示的VNF实例化过程。
下面还提供一些设备实施例。
参见图10，本申请实施例还提供一种VNFM 1000，包括：
接收单元1010，用于接收来自NFVO的第一虚拟网络功能VNF实例化请求，所述第一VNF实例化请求携带第一VNF实例标识和第一虚拟化网络功能描述符VNFD标识。
确定单元1020，用于确定所述第一VNFD标识所表示的VNFD所引用的容器对象包标识。
发送单元1030，用于向容器管理实体发送容器对象包管理请求，所述容器对象包管理请求携带所述容器对象包标识。
所述接收单元1010还用于，接收来自所述容器管理实体的容器对象包管理响应，所述容器对象包管理响应用于指示所述容器对象包标识所表示的容器对象包中的容器对象实例创建成功。
创建管理单元1040，用于创建所述第一VNF实例标识所表示的VNF实例，并维护所述第一VNF实例标识与所述容器对象包标识之间的映射关系。
其中，所述容器对象包管理请求用于触发所述容器管理实体根据所述容器对象包标识创建所述容器对象包标识所表示的容器对象包中的容器对象实例。具体例如，确定所述容器对象包标识所表示的容器对象包所引用的容器对象包文件，根据所述容器对象包文件创建所述容器对象包中的容器对象实例，并将创建的所述容器对象实例调度到其使用的容器运行时实例上。
在一些可能的实施方式中，所述发送单元1030还用于，在向容器管理实体发送容器对象包管理请求之前，向所述容器管理实体发送容器对象包创建请求，所述容器对象包创建请求携带创建所述容器对象包所使用的容器对象包文件的名称和/或访问地址。
所述接收单元1010还用于，接收来自所述容器管理实体的容器对象包创建响应，所述容器对象包创建响应携带所述容器管理实体创建的所述容器对象包的容器对象包标识。
在一些可能的实施方式中，所述接收单元1010还用于，接收来自所述NFVO的VNF实例终结请求，所述VNF实例终结请求携带第二VNF实例标识。
所述确定单元1020还用于，确定与所述第二VNF实例标识具有映射关系的容器对象包标识；
所述发送单元1030还用于，向所述容器管理实体发送容器对象包删除请求，所述容器对象包删除请求携带确定的所述容器对象包标识，其中，所述容器对象包删除请求用于触发所述容器管理实体终结所述容器对象包标识所表示的容器对象包中的容器对象实例，并释放终结的所述容器对象实例所使用的容器运行时实例。
在一些可能的实施方式中，
接收单元1010还用于，接收来自NFVO的第二VNF实例化请求，所述第二VNF实例化请求携带第二VNF实例标识和第二VNFD标识。
所述VNFM还包括获取单元1050，用于从所述第二VNFD标识所表示的VNFD中获取待创建的基础设施资源池所需的VM资源数量和VM资源规格。
所述发送单元1030还用于，向虚拟化基础设施管理器VIM发送资源分配请求，所述资源分配请求携带待创建的基础设施资源池的VM资源规格和VM资源数量。
所述接收单元1010还用于，接收来自所述VIM的资源分配响应，所述资源分配响应中携带所分配的VM实例的VM实例标识。
所述VNFM还包括标签单元1060，用于给所述VM实例打标签，所述标签用于指示所述VM实例作为基础设施资源池中创建容器运行时实例所使用的虚拟资源。
所述发送单元1030还用于，将所述VM实例标识发送给容器管理实体进行纳管。
在一些可能的实施方式中，所述容器对象包文件映射为Helm Chart，容器对象包实例映射为Helm Release。
在一些可能的实施方式中，所述VNFD还包含虚拟化部署单元VDU标识；其中，当VNF为基于VM的VNF，所述VNFD包含的VDU属性允许使用，所述VNFD引用的容器对象包属性禁止使用；当VNF为容器化VNF，所述VNFD包含的VDU属性允许使用或禁止使用，所述VNFD引用的容器对象包属性允许使用。
在一些可能的实施方式中，所述容器对象包内包含一个或多个容器对象，每个容器对象映射为开源事实标准中的对象。
在一些可能的实施方式中，所述容器对象映射为Kubernetes对象，所述Kubernetes对象包括Pod、Service或Deployment，并且，所述容器对象对容器管理实体可见且对管理和编排实体不可见。
其中，VNFM 1100的各功能模块的功能可参考图6-图9举例所示方法来具体实施。例如接收单元1010可执行步骤901和904中由VNFM执行的动作。发送单元1030可执行步骤903和906中由VNFM执行的动作，创建管理单元1040可执行步骤606中由VNFM执行的动作，以此类推。
参见图11，本申请实施例还提供另一种VNFM 1100，包括：
接收单元1110，用于接收来自NFVO的第二虚拟网络功能VNF实例化请求，所述第二VNF实例化请求携带第二VNF实例标识和第二虚拟化网络功能描述符VNFD标识。
获取单元1120，用于从所述第二VNFD标识所表示的VNFD中获取待创建的基础设施资源池所需的VM资源数量和VM资源规格。
发送单元1130，用于向虚拟化基础设施管理器VIM发送资源分配请求，所述资源分配请求携带待创建的基础设施资源池的VM资源规格和VM资源数量。
所述接收单元1110还用于，接收来自所述VIM的资源分配响应，所述资源分配响应中携带所分配的VM实例的VM实例标识。
标签单元1140，用于给所述VM实例打标签，所述标签用于指示所述VM实例作为基础设施资源池中创建容器运行时实例所使用的虚拟资源。
所述发送单元1130还用于，将所述VM实例标识发送给容器管理实体进行纳管。
其中，VNFM 1100的各功能模块的功能可参考图9举例所示方法来具体实施。例如接收单元1110可执行步骤901和904中由VNFM执行的动作。发送单元1130可执行步骤903和906中由VNFM执行的动作，以此类推。
参见图12，本申请实施例还提供一种容器管理实体1200，包括：
接收单元1210，用于接收来自虚拟网络功能管理器VNFM的容器对象包管理请求，所述容器对象包管理请求携带被虚拟化网络功能描述符VNFD引用的容器对象包标识。
创建单元1220，用于所述容器管理实体根据所述容器对象包标识创建所述容器对象包标识所表示的容器对象包中的容器对象实例。
发送单元1230，用于向所述VNFM发送容器对象包管理响应，所述容器对象包管理响应用于指示所述容器对象包标识所表示的容器对象包中的容器对象实例创建成功。
举例来说，所述根据所述容器对象包标识创建所述容器对象包标识所表示的容器对象包中的容器对象实例，可包括：确定所述容器对象包标识所表示的容器对象包所引用的容器对象包文件；根据所述容器对象包文件创建所述容器对象包中的容器对象实例；将创建的所述容器对象实例调度到其使用的容器运行时实例上。
容器管理实体1200的各功能模块的功能可参考图6-图9举例所示方法来具体实施。各功能模块可配合执行由容器管理实体(如CISM)执行的部分或全部动作。
参见图13，本申请实施例还提供一种通用的通信设备1300，该通信设备1300可以实现以上实施例提供的VNFM、NFVO或容器管理实体的功能，具体包括：
相互耦合的处理器1310和存储器1320。
其中，处理器1310用于调用存储器1320存储的计算机程序，以完成本申请实施例中由VNFM执行的任意一种方法的部分或全部步骤。
此外，处理器1310也可以调用存储器1320中存储的不同计算机程序，完成本申请实施例中由NFVO或容器管理实体执行的任意一种方法的部分或全部步骤。
其中，处理器1310还称中央处理单元(CPU，Central Processing Unit)。具体的应用中图像预测装置的各组件例如通过总线***耦合在一起。其中，总线***除了可包括数据总线之外，还可包括电源总线、控制总线和状态信号总线等。上述本申请实施例揭示的方法可应用于处理器1310中，或由处理器1310实现。处理器1310可能是一种集成电路芯片，具有信号的处理能力。在一些实现过程之中，上述方法的部分或全部步骤可通过处理器1310中的硬件的集成逻辑电路或者软件形式的指令完成。处理器1310可以是通用处理器、数字信号处理器、专用集成电路、现成可编程门阵列或其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。处理器1310可实现或执行本申请实施例中公开的各方法、步骤及逻辑框图。通用处理器1310可为微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可直接体现为硬件译码处理器执行完成，或用译码处理器中的硬件及软件模块组合执行完成。软件模块可位于随机存储器，闪存、只读存储器，可编程只读存储器、电可擦写可编程存储器或寄存器等等本领域成熟的存储介质之中。该存储介质位于存储器1320，例如处理器1310可读取存储器1320中的信息，结合其硬件完成上述方法的部分或全部步骤。
本申请实施例还提供一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序，所述计算机程序被硬件(例如处理器等)执行，以本申请实施例中由任意设备执行的任意一种方法的部分或全部步骤。
本申请实施例还提供了一种包括指令的计算机程序产品，当所述计算机程序产品在计算机设备上运行时，使得所述这个计算机设备执行以上各方面的任意一种方法的部分或者 全部步骤。
在上述实施例中，可全部或部分地通过软件、硬件、固件、或其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线)或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如软盘、硬盘、磁带)、光介质(例如光盘)、或者半导体介质(例如固态硬盘)等。在上述实施例中，对各个实施例的描述都各有侧重，某个实施例中没有详述的部分，可以参见其他实施例的相关描述。
在上述实施例中，对各实施例的描述都各有侧重，某个实施例中没有详述的部分，可以参见其他实施例的相关描述。
在本申请所提供的几个实施例中，应该理解到，所揭露的装置，也可以通过其它的方式实现。例如以上所描述的装置实施例仅仅是示意性的，例如所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可结合或者可以集成到另一个***，或一些特征可以忽略或不执行。另一点，所显示或讨论的相互之间的间接耦合或者直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者，也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例的方案的目的。
另外，在本申请各实施例中的各功能单元可集成在一个处理单元中，也可以是各单元单独物理存在，也可两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，或者也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可为个人计算机、服务器或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质例如可包括：U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或光盘等各种可存储程序代码的介质。

Claims (18)

  1. 一种容器化VNF的部署方法，其特征在于，包括：
    虚拟网络功能管理器VNFM接收来自网络功能虚拟化编排器NFVO的第一虚拟网络功能VNF实例化请求，其中，所述第一VNF实例化请求携带第一虚拟化网络功能描述符VNFD标识；
    所述VNFM根据所述第一VNFD标识所表示的VNFD确定待实例化的VNF所引用的容器对象包标识；
    所述VNFM向容器管理实体发送管理请求，所述管理请求携带所述容器对象包标识；
    所述VNFM接收来自所述容器管理实体的管理响应，所述管理响应用于指示所述容器对象包标识所表示的容器对象包所对应的容器对象实例创建成功；
    所述VNFM根据所述容器对象实例完成VNF实例化过程，并维护VNF实例化而得到的VNF实例的标识与所述容器对象实例的标识之间的映射关系。
  2. 根据权利要求1所述的方法，其特征在于，所述管理请求用于触发所述容器管理实体确定所述容器对象包标识所表示的容器对象包所引用的容器对象包文件，根据所述容器对象包文件创建容器对象实例，并将创建的所述容器对象实例调度到其使用的容器运行时实例上。
  3. 根据权利要求1或2所述的方法，其特征在于，所述VNFM向容器管理实体发送管理请求之前，所述方法还包括：
    所述VNFM向所述容器管理实体发送容器对象创建请求，所述容器对象创建请求携带创建所述容器对象实例所使用的容器对象包文件的名称和/或访问地址；所述VNFM接收来自所述容器管理实体的容器对象创建响应，所述容器对象创建响应携带所述容器管理实体基于所述容器对象包创建的容器对象实例的标识。
  4. 根据权利要求1至3任意一项所述的方法，其特征在于，所述方法还包括：
    所述VNFM接收来自所述NFVO的VNF实例终结请求，所述VNF实例终结请求携带第二VNF实例标识；
    所述VNFM确定与所述第二VNF实例标识具有映射关系的容器对象实例标识；
    所述VNFM向所述容器管理实体发送容器对象删除请求，所述容器对象删除请求携带确定的所述容器对象实例标识，其中，所述容器对象删除请求用于触发所述容器管理实体终结所述容器对象实例标识所表示的容器对象实例，并释放所述容器对象实例所使用的容器运行时实例。
  5. 根据权利要求1至4任意一项所述的方法，其特征在于，所述方法还包括：
    所述VNFM接收来自NFVO的第二VNF实例化请求，所述第二VNF实例化请求携带第二VNF实例标识和第二VNFD标识；
    所述VNFM从所述第二VNFD标识所表示的VNFD中获取待创建的基础设施资源池所需的VM资源数量和VM资源规格；
    所述VNFM向虚拟化基础设施管理器VIM发送资源分配请求，所述资源分配请求携带待创建的基础设施资源池的VM资源规格和VM资源数量；
    所述VNFM接收来自所述VIM的资源分配响应，所述资源分配响应中携带所分配的VM实例的VM实例标识；
    所述VNFM给所述VM实例打标签，所述标签用于指示所述VM实例作为基础设施资源池中创建容器运行时实例所使用的虚拟资源；
    所述VNFM将所述VM实例标识发送给容器管理实体进行纳管。
  6. 根据权利要求1至5任意一项所述的方法，其特征在于，所述容器对象包文件映射为Helm Chart。
  7. 根据权利要求1至5任意一项所述方法，其特征在于，所述VNFD还包含虚拟化部署单元VDU标识；当VNF为基于VM的VNF，所述VNFD包含的VDU属性允许使用，所述VNFD引用的容器对象包属性禁止使用；当VNF为容器化VNF，所述VNFD包含的VDU属性允许使用或禁止使用，所述VNFD引用的容器对象包属性允许使用。
  8. 根据权利要求1至7任意一项所述的方法，其特征在于，所述容器对象包内包含一个或多个容器对象，其中，每个容器对象映射为开源事实标准中的对象。
  9. 根据权利要求8所述方法，其特征在于，所述容器对象映射为Kubernetes对象，所述Kubernetes对象包括Pod、Service或Deployment，并且，所述容器对象对容器管理实体可见。
  10. 一种容器化VNF的部署方法，其特征在于，包括：容器管理实体接收来自虚拟网络功能管理器VNFM的管理请求，其中，所述管理请求携带被虚拟化网络功能描述符VNFD引用的容器对象包标识；
    所述容器管理实体根据所述容器对象包标识所表示的容器对象包创建所对应的容器对象实例；
    所述容器管理实体向所述VNFM发送管理响应，所述管理响应用于指示所述容器对象包标识所表示的容器对象包所对应的容器对象实例创建成功。
  11. 根据权利要求10所述方法，其特征在于，所述根据所述容器对象包标识创建所述容器对象包标识所表示的容器对象包所对应的容器对象实例，包括：
    确定所述容器对象包标识所表示的容器对象包所引用的容器对象包文件；根据所述容器对象包文件创建所述容器对象包所对应的容器对象实例；将创建的所述容器对象实例调 度到其使用的容器运行时实例上。
  12. 一种容器化VNF的部署方法，其特征在于，包括：
    虚拟网络功能管理器VNFM接收来自网络功能虚拟化编排器NFVO的第一虚拟网络功能VNF实例化请求，其中，所述第一VNF实例化请求携带第一虚拟化网络功能描述符VNFD标识；
    所述VNFM根据所述第一VNFD标识所表示的VNFD确定待实例化的VNF所引用的容器对象包标识；
    所述VNFM向容器管理实体发送管理请求，所述管理请求携带所述容器对象包标识；
    所述容器管理实体在接收所述管理请求之后，根据所述容器对象包标识所表示的容器对象包创建所对应的容器对象实例，向所述VNFM发送管理响应，所述管理响应用于指示所述容器对象包标识所表示的容器对象包所对应的容器对象实例创建成功；
    所述VNFM接收来自所述容器管理实体的管理响应，所述VNFM根据所述容器对象实例完成VNF实例化过程，并维护VNF实例化而得到的VNF实例的标识与所述容器对象的标识之间的映射关系。
  13. 根据权利要求12所述的方法，其特征在于，所述VNFM向容器管理实体发送管理请求之前，所述方法还包括：
    所述VNFM向所述容器管理实体发送容器对象创建请求，所述容器对象创建请求携带创建所述容器对象实例所使用的容器对象包文件的名称和/或访问地址；
    所述容器管理实体在接收所述容器对象创建请求之后，根据容器对象包文件的名称和/或访问地址获取所述容器对象包文件，使用所述容器对象包文件创建所述容器对象实例；向所述VNFM发送容器对象创建响应，所述容器对象创建响应携带所述容器管理实体创建的所述容器对象实例的标识。
  14. 根据权利要求12或13所述的方法，其特征在于，所述方法还包括：
    所述VNFM接收来自所述NFVO的VNF实例终结请求，所述VNF实例终结请求携带第二VNF实例标识；
    所述VNFM确定与所述第二VNF实例标识具有映射关系的容器对象实例标识；
    所述VNFM向所述容器管理实体发送容器对象删除请求，所述容器对象删除请求携带确定的所述容器对象实例标识，
    所述容器管理实体在接收所述容器对象包删除请求之后，终结所述容器对象实例标识所表示的容器对象实例，并且释放所述容器对象实例所使用的容器运行时实例。
  15. 根据权利要求12至14任一项所述的方法，其特征在于，
    所述容器管理实体根据所述容器对象包标识所表示的容器对象包创建所对应的容器对象实例包括：所述容器管理实体确定所述容器对象包标识所表示的容器对象包所引用的容 器对象包文件，根据所述容器对象包文件创建所述容器对象包所对应的容器对象实例，并将创建的所述容器对象实例调度到其使用的容器运行时实例上。
  16. 一种虚拟网络功能管理器VNFM，其特征在于，包括：
    相互耦合的处理器和存储器；
    其中，所述处理器用于调用所述存储器中存储的计算机程序，以完成权利要求1至11任意一项所述的方法。
  17. 一种容器管理设备，其特征在于，包括：
    相互耦合的处理器和存储器；
    其中，所述处理器用于调用所述存储器中存储的计算机程序，以完成权利要求12至15任意一项所述的方法。
  18. 一种计算机可读存储介质，其特征在于，
    所述计算机可读存储介质存储有计算机程序，所述计算机程序被处理器执行时完成权利要求1至15任意一项所述的方法。
PCT/CN2020/090915 2019-05-16 2020-05-18 容器化vnf的部署方法和相关设备 WO2020228838A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP20806603.5A EP3964953A4 (en) 2019-05-16 2020-05-18 CONTAINERIZED VNF DEPLOYMENT METHOD AND ASSOCIATED DEVICE
US17/527,121 US11928522B2 (en) 2019-05-16 2021-11-15 Containerized VNF deployment method and related device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910407713.2A CN111949364A (zh) 2019-05-16 2019-05-16 容器化vnf的部署方法和相关设备
CN201910407713.2 2019-05-16

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/527,121 Continuation US11928522B2 (en) 2019-05-16 2021-11-15 Containerized VNF deployment method and related device

Publications (1)

Publication Number Publication Date
WO2020228838A1 true WO2020228838A1 (zh) 2020-11-19

Family

ID=73288950

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/090915 WO2020228838A1 (zh) 2019-05-16 2020-05-18 容器化vnf的部署方法和相关设备

Country Status (4)

Country Link
US (1) US11928522B2 (zh)
EP (1) EP3964953A4 (zh)
CN (1) CN111949364A (zh)
WO (1) WO2020228838A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114721746A (zh) * 2022-06-06 2022-07-08 杭州玳数科技有限公司 一种Trino catalog热加载方法和***
WO2023137712A1 (en) * 2022-01-21 2023-07-27 Zte Corporation Method, device and computer program product for wireless communication

Families Citing this family (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111722906A (zh) * 2019-03-22 2020-09-29 华为技术有限公司 一种部署虚拟机和容器的方法及装置
CN112583625B (zh) * 2019-09-30 2023-12-08 中兴通讯股份有限公司 网络资源管理方法、***、网络设备和可读存储介质
US11630700B2 (en) * 2020-03-23 2023-04-18 T-Mobile Usa, Inc. Local edge device
JP2024501005A (ja) * 2020-12-28 2024-01-10 華為技術有限公司 コンテナクラスタのための管理方法および装置
WO2022199825A1 (en) * 2021-03-25 2022-09-29 Telefonaktiebolaget Lm Ericsson (Publ) Separation of network function and its realization
CN115883283A (zh) * 2021-09-27 2023-03-31 华为技术有限公司 一种容器化vnf的部署方法及装置
US20230094120A1 (en) * 2021-09-27 2023-03-30 Vmware, Inc. Runtime customization of nodes for network function deployment
CN116016229A (zh) * 2021-10-21 2023-04-25 华为技术有限公司 一种部署容器服务的方法及装置
CN116094912A (zh) * 2021-11-05 2023-05-09 华为技术有限公司 通信方法和装置
WO2023150950A1 (en) * 2022-02-10 2023-08-17 Zte Corporation Container network controller
CN116841689A (zh) * 2022-03-25 2023-10-03 华为技术有限公司 一种部署vnf的方法、装置及设备
CN118057776A (zh) * 2022-11-18 2024-05-21 华为技术有限公司 部署虚拟化网络功能的方法和通信装置

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107547237A (zh) * 2016-06-29 2018-01-05 中兴通讯股份有限公司 虚拟网络功能vnf更新方法、装置和vnf包
CN108011846A (zh) * 2017-11-03 2018-05-08 华为技术有限公司 网络功能虚拟化架构中管理业务的方法及装置
US20180191607A1 (en) * 2016-12-29 2018-07-05 Juniper Networks, Inc. Network service application and customer-aware virtualized network function placement
CN108345490A (zh) * 2017-01-24 2018-07-31 华为技术有限公司 一种nfv中部署虚拟机的方法和***
CN109347716A (zh) * 2018-09-25 2019-02-15 中国联合网络通信集团有限公司 消费者vnf的实例化方法及装置
CN109639460A (zh) * 2018-11-19 2019-04-16 中国联合网络通信集团有限公司 Nfv资源管理的方法和装置

Family Cites Families (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106533935B (zh) * 2015-09-14 2019-07-12 华为技术有限公司 一种在云计算***中获取业务链信息的方法和装置
US10985997B2 (en) * 2016-05-06 2021-04-20 Enterpriseweb Llc Systems and methods for domain-driven design and execution of metamodels
US10944627B2 (en) * 2016-11-02 2021-03-09 Apple Inc. Lifecycle management parameter modeling for virtual network functions
US10469359B2 (en) * 2016-11-03 2019-11-05 Futurewei Technologies, Inc. Global resource orchestration system for network function virtualization
EP4195608A1 (en) * 2016-11-17 2023-06-14 Huawei Technologies Co., Ltd. Network service life cycle management grant method and apparatus
CN108347343B (zh) * 2017-01-25 2020-07-14 华为技术有限公司 一种策略管理方法、装置和***
CN108462592A (zh) 2017-02-20 2018-08-28 华为技术有限公司 基于sla的资源分配方法和nfvo
WO2018174897A1 (en) * 2017-03-24 2018-09-27 Nokia Technologies Oy Methods and apparatuses for multi-tiered virtualized network function scaling
US10469317B1 (en) * 2017-03-29 2019-11-05 Juniper Networks, Inc. Virtualized network function descriptors for virtualized network function configuration
FR3071948A1 (fr) * 2017-09-29 2019-04-05 Orange Procede et dispositif de traitement d'une requete d'instanciation d'un service reseau.
CN112202673B (zh) * 2017-11-21 2022-01-04 华为技术有限公司 一种配置方法及装置
JP7173041B2 (ja) * 2017-11-29 2022-11-16 日本電気株式会社 管理装置、上位装置、管理方法及びプログラム
EP4170991A1 (en) * 2017-12-29 2023-04-26 Huawei Technologies Co., Ltd. Network service management system
GB2573283B (en) * 2018-04-26 2020-04-29 Metaswitch Networks Ltd Improvements relating to network functions virtualization
CN114880078A (zh) * 2018-06-05 2022-08-09 华为技术有限公司 管理容器服务的方法和装置
CN111641515B (zh) * 2019-03-01 2021-11-19 华为技术有限公司 Vnf的生命周期管理方法及装置
CN114944979A (zh) * 2019-09-02 2022-08-26 华为技术有限公司 一种多管理域的通信方法和装置
CN112583615B (zh) * 2019-09-29 2022-04-29 北京华为数字技术有限公司 Vnf实例化方法、nfvo、vim、vnfm及***
CN115412439A (zh) * 2019-11-29 2022-11-29 北京华为数字技术有限公司 一种管理网络服务的方法、设备及***

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107547237A (zh) * 2016-06-29 2018-01-05 中兴通讯股份有限公司 虚拟网络功能vnf更新方法、装置和vnf包
US20180191607A1 (en) * 2016-12-29 2018-07-05 Juniper Networks, Inc. Network service application and customer-aware virtualized network function placement
CN108345490A (zh) * 2017-01-24 2018-07-31 华为技术有限公司 一种nfv中部署虚拟机的方法和***
CN108011846A (zh) * 2017-11-03 2018-05-08 华为技术有限公司 网络功能虚拟化架构中管理业务的方法及装置
CN109347716A (zh) * 2018-09-25 2019-02-15 中国联合网络通信集团有限公司 消费者vnf的实例化方法及装置
CN109639460A (zh) * 2018-11-19 2019-04-16 中国联合网络通信集团有限公司 Nfv资源管理的方法和装置

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023137712A1 (en) * 2022-01-21 2023-07-27 Zte Corporation Method, device and computer program product for wireless communication
CN114721746A (zh) * 2022-06-06 2022-07-08 杭州玳数科技有限公司 一种Trino catalog热加载方法和***
CN114721746B (zh) * 2022-06-06 2022-09-09 杭州玳数科技有限公司 一种Trino catalog热加载方法和***

Also Published As

Publication number Publication date
EP3964953A1 (en) 2022-03-09
CN111949364A (zh) 2020-11-17
EP3964953A4 (en) 2022-07-13
US20220075666A1 (en) 2022-03-10
US11928522B2 (en) 2024-03-12

Similar Documents

Publication Publication Date Title
WO2020228838A1 (zh) 容器化vnf的部署方法和相关设备
US11354167B2 (en) Container service management method and apparatus
US10701139B2 (en) Life cycle management method and apparatus
US20220217045A1 (en) Method and node for using templates
CN111221618B (zh) 一种容器化虚拟网络功能的部署方法和装置
US11108653B2 (en) Network service management method, related apparatus, and system
WO2017080391A1 (zh) 一种网络服务部署方法和装置
US11303526B2 (en) Network slice deployment method and apparatus
CN107222324B (zh) 网络服务的业务配置方法和装置
JP2020510384A (ja) ネットワークスライス管理方法、ユニット、及びシステム
CN109428764B (zh) 虚拟网络功能的实例化方法
US11871280B2 (en) VNF instantiation method, NFVO, VIM, VNFM, and system
WO2020108443A1 (zh) 一种虚拟化管理方法及装置
WO2017140191A1 (zh) 基站硬件虚拟化方法、装置和基站
JP2022550402A (ja) ネットワークリソース管理方法、システム、ネットワーク機器と可読記憶媒体
US20230261950A1 (en) Method of container cluster management and system thereof
US20230342183A1 (en) Management method and apparatus for container cluster
WO2021004320A1 (zh) 服务资源许可管理方法和相关设备
WO2019109948A1 (zh) PaaS的管理方法、装置及存储介质
CN116800616A (zh) 虚拟化网络设备的管理方法及相关装置
CN112015515B (zh) 一种虚拟网络功能的实例化方法及装置
US9668082B2 (en) Virtual machine based on a mobile device
WO2021129520A1 (zh) 网络业务的生命周期管理的授权方法及装置
CN113760374B (zh) 一种处理器的绑定方法、装置及电子设备
WO2024027398A1 (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: 20806603

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2020806603

Country of ref document: EP

Effective date: 20211130