WO2020135799A1 - Vnf服务实例化方法及装置 - Google Patents

Vnf服务实例化方法及装置 Download PDF

Info

Publication number
WO2020135799A1
WO2020135799A1 PCT/CN2019/129578 CN2019129578W WO2020135799A1 WO 2020135799 A1 WO2020135799 A1 WO 2020135799A1 CN 2019129578 W CN2019129578 W CN 2019129578W WO 2020135799 A1 WO2020135799 A1 WO 2020135799A1
Authority
WO
WIPO (PCT)
Prior art keywords
caas
container service
cluster
vnf
manager
Prior art date
Application number
PCT/CN2019/129578
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 EP19906357.9A priority Critical patent/EP3893438A4/en
Publication of WO2020135799A1 publication Critical patent/WO2020135799A1/zh
Priority to US17/356,874 priority patent/US12020055B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
    • G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
    • G06F9/5033—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals considering data affinity
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/34—Signalling channels for network management communication
    • H04L41/342—Signalling channels for network management communication between virtual entities, e.g. orchestrators, SDN or NFV entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • H04L41/5051—Service on demand, e.g. definition and deployment of services in real time
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • H04L41/5054—Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components
    • 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
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2209/00—Indexing scheme relating to G06F9/00
    • G06F2209/50—Indexing scheme relating to G06F9/50
    • G06F2209/503—Resource availability
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2209/00—Indexing scheme relating to G06F9/00
    • G06F2209/50—Indexing scheme relating to G06F9/50
    • G06F2209/505—Clust
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0896—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities
    • H04L41/0897—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities by horizontal or vertical scaling of resources, or by migrating entities, e.g. virtual resources or entities

Definitions

  • This application relates to the field of cloud computing technology, and in particular to a method and device for instantiating a virtual network function (Virtual Network Function, VNF) service.
  • VNF Virtual Network Function
  • NFV Network Function Virtualization
  • COTS Commercial-off-the- shelf
  • NFV technology is used to transform each network element used in a telecommunications network into an independent application, which can be flexibly deployed on a unified infrastructure platform built on standards-based servers, storage, switches, and other devices, and through virtualization technology, the infrastructure Hardware device resource pooling and virtualization, providing virtual resources to upper-layer applications, decoupling applications and hardware, so that each application can quickly increase virtual resources to achieve the purpose of quickly expanding system capacity, or can quickly reduce virtual resources to achieve shrinkage
  • the purpose of system capacity is to greatly improve the flexibility of the network.
  • a common COTS server is used to form a shared resource pool. Newly developed services do not require separate hardware equipment deployment, greatly reducing the time for new services to go online.
  • NFV technology includes cloud computing technology and virtualization technology.
  • General COTS computing/storage/networking and other hardware devices can be decomposed into multiple virtual resources through virtualization technology for various applications at the upper layer.
  • virtualization technology Through virtualization technology, the decoupling between applications and hardware is achieved, which greatly increases the supply speed of virtual resources; through cloud computing technology, elastic scaling of applications can be achieved, and virtual resources can be matched with business loads, which not only improves the virtual resources Use efficiency, and improve the response rate of the system.
  • Container as a service Container as Service, CaaS
  • PaaS Platform as a Service
  • Containers are an operating system-level virtualization technology that uses operating system isolation technologies such as CGroup and NameSpace under Linux to isolate different processes.
  • Container technology is different from hardware virtualization technology. It does not specifically perform hardware virtualization processing, and there is no independent operating system inside the container. Resource sharing is only achieved through process isolation and resource use restrictions. Because of this important feature of container technology, containers are lighter than virtual machines and more convenient to manage. In the running state of the container, a set of common management operations are defined, such as: start, stop, pause, and delete, etc., to perform unified life cycle management of the container.
  • Telecommunication services have high requirements for reliability, and there is a general need for disaster recovery in different places; network elements come from multiple vendors, and they may each run on their own container management platform.
  • Current IoT, edge computing and other scenarios also put forward requirements for edge cloud deployment.
  • a central data center plus multiple edge clouds is a common deployment solution.
  • the current mainstream container orchestration tools (such as K8S) can manage a limited scale. For example, the latest version of K8S currently supports management of up to 5000 nodes.
  • K8S Cluster multi-container service sites
  • Embodiments of the present invention provide a method, device, and system for instantiating a VNF service. Compared with the prior art, the process and interface of a multi-container service site in an NFV system are clearly described.
  • An embodiment of the present invention provides a virtual network function VNF instantiation method, which is executed by a network function virtualization orchestrator NFVO or a virtual network function manager VNFM, including:
  • the VNFM obtains the corresponding VNFD from the database according to the VNF instantiation request message, and obtains the deployment information of the corresponding container service instance from the VNFD.
  • the deployment information of the container service instance includes one or more of the following:
  • the specified Cluster name or
  • the deployment weight of each CaaS Cluster In the deployment of multiple CaaS Clusters, the deployment weight of each CaaS Cluster, the number or limit of container service instances deployed by each CaaS Cluster.
  • An embodiment of the present invention provides a virtual network function VNF instantiation device, including:
  • the receiving unit is used to receive a virtual network function VNF instantiation request message
  • a processing unit configured to obtain deployment information of a container service instance to be invoked by the VNF instantiation, and determine one or more container service sites CaaS Cluster according to the deployment information of the container service instance;
  • a sending unit configured to send a container service instance creation request to the container service manager CaaS Manager in the one or more CaaS Clusters, respectively;
  • the receiving unit is also used for the CaaS Manager to receive a success message of container service instance creation.
  • An embodiment of the present invention provides a virtual network function VNF instantiation system, including a virtual network function VNF service instantiation device and one or more container service managers CaaS Manager, wherein,
  • the VNF service instantiation device is used to receive a VNF instantiation request message, obtain deployment information of a container service instance to be called for the VNF instantiation; determine one or more CaaS Clusters according to the deployment information of the container service instance, and send The container service manager CaaS Manager in one or more CaaS Clusters sends a container service instance creation request; receives a container service instance creation success message from the CaaS Manager.
  • the CaaS Manager is used to receive the device service instance creation request, create a corresponding container service instance, and send a container service instance creation success message to the VNF service instantiation device.
  • An embodiment of the present invention also provides an apparatus for instantiating a virtual network function VNF service.
  • the apparatus includes a processor and a memory; the memory is used to store a program that executes the method as described above, and stores data related to the method. Data; the processor is used to execute the program stored in the memory.
  • An embodiment of the present invention further provides a computer-readable storage medium that stores executable program instructions, and when the executable program instructions are executed, the steps involved in the above method are performed.
  • An embodiment of the present invention also provides a computer program product, which is used to execute the method steps described above when the computer product is executed.
  • the above embodiments are proposed under the MANO architecture for one or more CaaS Cluster scenarios.
  • the above solution solves the problem of cross-site deployment and management of container services in the NFV scenario, so that VNF container services can be deployed in different CaaS Clusters.
  • one or more CaaS clusters can be controlled and managed in a unified manner.
  • FIG. 1 is a schematic diagram of an NFV architecture provided by an embodiment of the present invention.
  • FIG. 2 is a schematic diagram of an NFV architecture in which CaaS Cluster is deployed according to an embodiment of the present invention
  • FIG. 3 is a schematic diagram of a VNF instantiation process provided by an embodiment of the present invention.
  • FIG. 4 is a schematic flowchart of batch query/update/delete of a container service instance provided by an embodiment of the present invention
  • FIG. 5 is a schematic flowchart of a state maintenance of a container service instance provided by an embodiment of the present invention.
  • FIG. 6 is a schematic diagram of a VNF instantiation device provided by an embodiment of the present invention.
  • FIG. 7 is a schematic diagram of a VNF instantiation system provided by an embodiment of the present invention.
  • FIG. 8 is a hardware schematic diagram of a VNF instantiation device provided by an embodiment of the present invention.
  • FIG. 1 is a schematic diagram of an NFV architecture provided by an embodiment of the present application.
  • the NFV system architecture can be applied to various types of networks, for example, an operator communication network or a local area network.
  • the NFV architecture mainly includes a MANO entity 110, NFVI 120, multiple VNFs 130, multiple network element management (Element Management, EM) 140, and a business support management system (Operation Support System/Business Support System, OSS/BSS) 150 etc.
  • the MANO entity 110 also includes a network function virtualization orchestrator (NFV) 110a, one or more virtual network function managers (Virtualised Network Function Manager, VNFM) 110b, and a virtualized infrastructure manager (Virtualized) Infrastructure Manager, VIM) 110c.
  • NFV network function virtualization orchestrator
  • VNFM Virtualised Network Function Manager
  • VIM Virtualized infrastructure manager
  • NFVO 110a is used to implement the management and processing of Network Service Descriptors (NSD), virtual network function forwarding graph (VNF Forwarding Graph, VNFFG), network service life cycle management, and VNFM to realize the life cycle of VNF Global view function for management and virtual resources.
  • NSD Network Service Descriptors
  • VNFFG virtual network function forwarding graph
  • VNFM network service life cycle management
  • VNFM 110b is used to realize the life cycle management of VNF, including the management of virtualized network function descriptor (VNFD) files, the instantiation of VNF, and the elastic scaling of VNF instances (including scaling Scaling out/up and scaling Scaling). /down), the healing of VNF instances (Healing) and the end of VNF instances, etc.
  • VNFM also supports receiving flexible scaling (scaling) strategies defined in NFVO delivery or VNFD to achieve automated VNF flexible scaling.
  • VIM 110b is used to manage the infrastructure layer hardware resources, virtualized resources management (including reservation and allocation), virtual resource status monitoring and fault reporting, and provide virtualized resource pools for upper-layer applications.
  • OSS/BSS 150 refers to the operator's existing operation and maintenance system OSS/BSS.
  • EM140 is used to perform traditional fault, configuration, user, performance and security management (FaultManagement, ConfigurationManagement, AccountManagement, PerformanceManagement, SecurityManagement, FCAPS) functions for VNF130.
  • FaultManagement, ConfigurationManagement, AccountManagement, PerformanceManagement, SecurityManagement, FCAPS faultManagement, ConfigurationManagement, AccountManagement, PerformanceManagement, SecurityManagement, FCAPS
  • VNF 130 corresponds to physical network functions (PNF) in traditional non-virtualized networks, such as virtualized 4G core network (Evolved Packet Core, EPC) EPC nodes, such as mobility management entities (Mobility Management Entity, MME) , Service Gateway (Serving Gateway, SGW), Packet Data Gateway (Packet Data Network Gateway, PGW), etc.
  • EPC Evolved Packet Core
  • MME Mobility Management Entity
  • SGW Service Gateway
  • PGW Packet Data Gateway
  • PGW Packet Data Network Gateway
  • VNF 130 can be composed of multiple VNF components (VNF Components, VNFC). Therefore, in practical applications, one VNF 130 can be deployed on multiple virtual machines (Virtual Machine, VM), each VM carrying a VNF component Function. Of course, a VNF 130 can also be deployed on a VM.
  • VNF Components VNFC
  • NFVI 120 is composed of hardware resources, virtual resources, and virtualization layer. From the perspective of VNF 130, the virtualization layer and hardware resources seem to be a complete entity that can provide the required virtual resources.
  • FIG. 2 is a schematic diagram of an NFV architecture deployed with one or more container service sites (CaaS Cluster) provided by an embodiment of the present application.
  • CaaS Cluster container service sites
  • One or more CaaS Clusters are connected to the NFVO and/or VNFM in the MANO system.
  • Each CaaS Cluster is deployed with a container manager (CaaS Manager).
  • the CaaS Manager instantiates the container service in the CaaS Cluster where it is located, and Container service instances are managed and scheduled.
  • NFVO or VNFM can connect to the CaaS Manager in each CaaS Cluster to obtain the container resource status information in each CaaS Cluster and send a container service request to the CaaS Cluster.
  • VNFD field of the VNF mainly includes deployment and flavour and VduProfile and other parameters in the deployment and flavour.
  • deploymentflavour is used to describe a specific deployment scheme during VNF deployment, which includes various deployment requirements, such as the virtual resource specifications required for deployment (such as the number of virtual machine CPUs, memory size; the number of container CPUs, etc.), VNF supports lifecycle management operations, affinity/anti-affinity relationships between components, supported monitoring indicators and scaling parameters, etc.
  • VduProfile is used to describe the specifications and deployment number of virtual machines/containers. The functions of the above parameters have been described in the existing standards, and will not be repeated here.
  • deployment information for the container service instance in the VNFD field of the prior art describing VNF which may include but is not limited to the following types of information:
  • CaaS Clusters which one or several CaaS Clusters are specifically deployed, they can be identified by the CaaS Cluster name, ID, or Label.
  • each CaaS Cluster is deployed as a part.
  • the deployment weight is used to instruct the VNFM to allocate the container service instance to be deployed to each CaaS Cluster according to the defined weight ratio. For example, a specific container service instance needs to be deployed in Cluster A, B, and C, and the deployment weights are respectively 6, 3, 1, then 60% (6/(6+3+1)) of all container service instances are deployed in Cluster A, and 30% and 10% of container service instances are deployed in B and C, respectively.
  • the number of container service instances is used to directly specify the number of instances required to be deployed in each CaaS Cluster, such as specifying 2, 3, and 5 container service instances deployed in Cluster A, B, and C, respectively.
  • the quota is used to specify the maximum number of container service instances that each CaaS Cluster can deploy.
  • VDU Virtualization Deployment Unit
  • the affinity/anti-affinity rules can refer to the following methods:
  • NFVO or VNFM After receiving the virtual network function VNF instantiation request message and before sending the service request to CaaS Manager, NFVO or VNFM needs to obtain the corresponding VNFD from the database, and obtain the container service instance deployment information from it, and then based on the locally deployed CaaS Cluster information, including quantity, processing capacity and other information (the above information can be obtained in advance by query, or based on external configuration), select the appropriate CaaS Cluster, and then send a service request to the CaaS Manager of the qualified CaaS Cluster, including: creating a container, updating , Query and delete.
  • NFVO or VNFM In addition to initiating a service request to CaaS Manager, NFVO or VNFM also needs to maintain the status of each CaaS Cluster, that is, periodically query the CaaS Manager of each CaaS Cluster to check the status of the current VNF instance. If it is inconsistent with the status described in VNFD, then Trigger the corresponding service application, create/delete/update the container, etc., so that the actual state is consistent with the description in VNFD. In addition, NFVO and VNFM can also provide DNS and load balancing services between different CaaS Clusters, so that cross-site deployment of VNF can successfully complete business communication between sites.
  • FIG. 3 is a flowchart of VNF instantiation, which specifically includes the instantiation of container service instances and the corresponding initial configuration of VNF instances. The steps are as follows:
  • VNFM receives a VNF instantiation request message from Sender.
  • Sender may be NFVO or EM; or NFVO needs to instantiate VNF during the process of instantiating a network service (NS) request; or NFVO receives a VNFM initiated request Granting request to authorize VNF instantiation.
  • NS network service
  • NFVO or VNFM obtains the deployment information of the container service instance from the VNFD corresponding to the VNF to be instantiated.
  • the deployment information of the container service instance may include: deployment location information of the container service instance; affinity/anti-affinity rules; deployment weight of CaaS Cluster (deployment of instances in proportion to weight), number, limit, etc.
  • NFVO or VNFM determines one or more container service sites CaaS Cluster according to the container deployment information.
  • NFVO or VNFM selects the appropriate CaaS Cluster based on the container service instance deployment information obtained in VNFD and the CaaS Cluster information stored locally.
  • the deployment information of the container service instance includes the name or ID of the CaaS Cluster, select the corresponding Cluster; if the label specified by the CaaS Cluster is specified, traverse the managed CaaS Cluster to find the CaaS Cluster that contains the corresponding label.
  • NFVO or VNFM can apply to VIM for physical server or virtual machine resources and access the CaaS corresponding to the CaaS Cluster In Manager management, increase its capacity.
  • NFVO or VNFM respectively sends a container service instance creation request to the container or service manager CaaS manager in the one or more CaaS Clusters.
  • the CaaS Manager inside each CaaS Cluster receives the request and then creates (instantiates) the container service instance.
  • Each CaaS Cluster sends a container service instance creation success response message to NFVO or VNFM.
  • NFVO or VNFM stores the deployment information of the container service instance locally, and then directly or notifies the EMS to initialize the configuration of the VNF instance.
  • NFVO or VNFM sends a VNF instantiation success response message to the initiator who initiated the VNF instance creation request.
  • FIG. 4 is a flow chart of VNF instance query/update/delete. The specific steps include:
  • VNFM receives the VNF query/update/delete request message from Sender.
  • Sender may be NFVO or EM; or NFVO needs to query/update the container service instance of VNF during the process of instantiating NS (Network Service) request /delete.
  • NS Network Service
  • NFVO or VNFM obtains the deployment location information of the VNF container service instance from the local storage information, that is, in which CaaS Clusters are deployed.
  • NFVO or VNFM initiates a query/update/delete request for the container service instance to the corresponding CaaS Manager.
  • the CaaS Manager inside each CaaS Cluster After receiving the request, the CaaS Manager inside each CaaS Cluster performs corresponding query/update/delete operations, and feeds back the results to NFVO or VNFM.
  • NFVO or VNFM updates the local information according to the feedback information and feeds it back to the request originator.
  • FIG. 5 is a flowchart of the maintenance of a VNF container service instance. The specific steps include:
  • NFVO or VNFM periodically inquires the CaaS Manager in the managed CaaS Cluster, or each CaaS Manager periodically reports the current container instance status to NFVO/VNFM.
  • NFVO or VNFM compares the obtained container service instance deployment information with the container service instance deployment information described in VNFD.
  • NFVO or VNFM initiates a corresponding container service instance operation request to the corresponding CaaS Manager. For example, if the number of actually deployed container service instances in a CaaS Cluster is less than the number specified in the VNFD, then NFVO or VNFM needs to initiate a container service instance creation request to the CaaS Cluster to make the actual deployment number consistent with the demand.
  • NFVO or VNFM needs to re-select the appropriate CaaS Cluster according to the container service instance deployment requirements in VNFD and locally stored CaaS Cluster information (see the figure)
  • the process of 3 is similar). Deploy the container service instance required by the faulty cluster to the newly selected CaaS Cluster, so that the overall deployment result is consistent with the requirements in the VNFD.
  • NFVO or VNFM receives the feedback result.
  • the above method embodiments are proposed under the MANO architecture for one or more CaaS Cluster scenarios.
  • the above method flow solves the cross-site deployment and management of container services in the NFV scenario, so that the VNF container services can be deployed in different In the CaaS Cluster, the MANO system can centrally control and manage one or more CaaS Clusters under management.
  • VNF instantiation device includes:
  • the receiving unit 610 is configured to receive a virtual network function VNF instantiation request message
  • the processing unit 620 is configured to obtain deployment information of the container service instance to be called by the VNF instantiation, and determine one or more container service sites CaaS Cluster according to the container deployment information;
  • the sending unit 630 is configured to send a container service instance creation request to the container or service manager CaaS Manager in the one or more CaaS Clusters, respectively;
  • the receiving unit 610 is also used for the CaaS Manager to receive a successful response message of container service instance creation.
  • VNF instantiation system includes:
  • VNF instantiation device and one or more CaaS Cluster, where,
  • the VNF service instantiation device is used for receiving a VNF instantiation request message, acquiring the container service site CaaS Cluster capability information to be invoked for the VNF instantiation; determining one or more CaaS Clusters according to the CaaS Cluster capability information, and submitting to the One or more containers in the CaaS Cluster, that is, the service manager CaaS manager, sends a container service instance creation request; receives a container service instance creation success message from the CaaS Manager.
  • the one or more CaaS managers are used to create corresponding container service instances based on the CaaS Cluster capability information, and send a container service instance creation success message to the VNF service instantiation device.
  • the virtual network function VNF service instantiation device is a network function virtualization orchestrator NFVO or a virtual network function manager VNFM.
  • FIG. 8 is a hardware diagram of a VNF instantiation device provided by an embodiment of the present invention.
  • the device 80 may include a processor, a communication interface, and a memory.
  • the processor 81 may include one or more processing units, and the processing unit may be a central processing unit (English: central processing unit, CPU) or a network processor (English: network processor, NP), or the like.
  • the processing unit may be a central processing unit (English: central processing unit, CPU) or a network processor (English: network processor, NP), or the like.
  • the communication interface 84 is used to connect and communicate with other communication devices, including receiving and sending corresponding messages; the network device 80 may also include a memory 83, and the processor 81 may be connected to the memory 83 and the communication interface 84 via a bus.
  • the memory 83 may be used to store a software program, which may be executed by the processor 81 to implement the method steps performed by the VNFM in the embodiment shown in FIG. 3.
  • the memory 83 can also store various types of business data or user data, including status data of various application instances and services in the above method steps.
  • the apparatus 80 may further include an output device 85 and an input device 88.
  • the output device 85 and the input device 88 are connected to the processor 81.
  • the output device 85 may be a display for displaying information, a power amplifier device or a printer for playing sound, and the output device 85 may further include an output controller to provide output to a display screen, a power amplifier device or a printer.
  • the input device 88 may be a device such as a mouse, keyboard, electronic stylus, or touch panel for the user to input information.
  • the input device 88 may also include an output controller for receiving and processing data from the mouse, keyboard, electronic Input from devices such as stylus or touch panel
  • the above device hardware diagram is also applicable to the CaaS Cluster device.
  • the difference is that the software program stored in the memory 83 is executed by the processor 81 to implement the method steps performed by the CaaS Cluster in the embodiment shown in FIG. 3, and will not be repeated here. .
  • the computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on the computer, all or part of the processes or functions described in the embodiments of the present application are generated.
  • the computer may be a general-purpose computer, a dedicated 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 from a website site, computer, server or data center Transmit to another website, computer, server or data center by wired (for example: coaxial cable, optical fiber, digital subscriber line (Digital Subscriber Line, DSL)) or wireless (for example: infrared, wireless, microwave, etc.).
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device including a server, a data center, and the like integrated with one or more available media.
  • the available media may be magnetic media (for example: floppy disk, hard disk, magnetic tape), optical media (for example: Digital Versatile Disc (DVD)), or semiconductor media (for example: Solid State Disk (SSD) )Wait.
  • the program may be stored in a computer-readable storage medium.
  • the mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk.

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服务实例化的方法和装置，所述方法由网络功能虚拟化编排器NFVO或虚拟网络功能管理器VNFM执行，所述方法包括：接收虚拟网络功能VNF实例化请求消息；获取所述VNF实例化需调用的容器服务实例的部署信息；根据所述容器服务实例的部署信息确定一个或多个容器服务站点CaaS Cluster，并分别向所述一个或多个CaaS Cluster中的容器服务管理器CaaS Manager发送容器服务实例创建请求；从所述CaaS Manager接收容器服务实例创建成功消息。通过上述方案解决了NFV场景下容器服务的跨站点部署以及管理问题。

Description

VNF服务实例化方法及装置 技术领域
本申请涉及云计算技术领域，特别涉及一种虚拟网络功能(Virtual Network Function,VNF)服务实例化的方法及装置。
背景技术
网络功能虚拟化(Network Function Virtualization，NFV)技术可以简单地理解为将电信网络中使用的各个网元的功能从目前的专用硬件平台迁移至通用的商用货架产品(COTS,Commercial-off-the-shelf)服务器上。通过NFV技术将电信网络中使用的各个网元转变成为独立的应用，可以灵活部署在基于标准的服务器、存储以及交换机等其他设备构建的统一基础设施平台上，并通过虚拟化技术，对基础设施硬件设备资源池化及虚拟化，对上层应用提供虚拟资源，实现应用、硬件解耦，使得每一个应用能够快速增加虚拟资源以实现快速扩展系统容量的目的，或者能够快速减少虚拟资源以实现收缩系统容量的目的，大大提升网络的弹性。采用通用的COTS服务器组成共享的资源池，新开发的业务，不需要单独部署硬件设备，大大缩短新业务上线时间。
NFV技术的基础包含云计算技术和虚拟化技术。通用的COTS计算/存储/网络等硬件设备通过虚拟化技术可以分解为多种虚拟资源，以供上层各种应用使用。通过虚拟化技术，实现应用与硬件之间的解耦，使得虚拟资源供给速度大大增加；通过云计算技术，可以实现应用的弹性伸缩，实现虚拟资源与业务负荷相匹配，不仅提升了虚拟资源的利用效率，而且改善了系统的响应速率。
虚拟化的电信网络功能逐渐进行容器化演进，容器即服务(Container as a Service，CaaS)是一种特定类型的平台即服务(Platform as a Service，PaaS)服务。容器是一种操作系统级别的虚拟化技术，通过操作系统隔离技术如Linux下的CGroup和NameSpace，将不同的进程隔离开来。容器技术不同于硬件虚拟化技术，并没有专门对硬件做虚拟化处理，容器内部也没有独立的操作系统，只通过进程隔离、资源使用限制等手段实现资源共享。正是由于容器技术的这个重要特点，使得容器相比虚拟机更轻量，管理也更方便。在容器的运行态，定义了一组公共的管理操作，例如：启动、停止、暂停和删除等，对容器进行统一的生命周期管理。
电信业务对可靠性要求较高，普遍存在异地容灾需求；网元来自于多个厂商，可能各自运行在自己的容器管理平台上。当前IoT、边缘计算等场景对边缘云部署也提出了需求，一个中心数据中心加多个边缘云是常见的部署方案。此外，当前主流容器编排工具(如K8S)所能管理的规模有限，比如最新版本的K8S当前支持最多5000个节点的管理。上述因素导致NFV业务场景下，多容器服务站点(CaaS Cluster)的部署和管理成为一个基础需求。
但当前标准和现有方案对多容器服务站点的部署和管理的支持能力不足。现有标准中，NFV管理平台对容器的管理方案尚在讨论之中，没有成熟的解决方案，K8S对虚拟机和容器混合编排的场景没有具体的解决方案。
发明内容
本发明实施例提供了一种VNF服务实例化的方法、装置和系统，相对于现有技术，对NFV系统中多容器服务站点流程和接口进行了明确描述。
本发明实施例提供了一种虚拟网络功能VNF实例化方法，所述方法由网络功能虚拟化编排器NFVO或虚拟网络功能管理器VNFM执行，包括：
接收虚拟网络功能VNF实例化请求消息；
获取所述VNF实例化需调用的容器服务实例的部署信息；
根据所述容器服务实例的部署信息确定一个或多个容器服务站点CaaS Cluster，并分别向所述一个或多个CaaS Cluster中的容器服务管理器CaaS Manager发送容器服务实例创建请求；
从所述CaaS Manager接收容器服务实例创建成功消息。
VNFM根据所述VNF实例化请求消息，在数据库中获取相应的VNFD，并在所述VNFD中获取相应的容器服务实例的部署信息。
所述容器服务实例的部署信息包括下面的一项或多项：
指定的Cluster名称，或
亲和/反亲和规则，或
在多CaaS Cluster部署时各CaaS Cluster的部署权重、各CaaS Cluster的部署的容器服务实例数量或限额。
如果所选的CaaS Cluster资源不足，则向虚拟化基础设施管理器VIM申请物理服务器或者虚拟机资源，增加所选CaaS Cluster的资源。
本发明实施例提供了一种虚拟网络功能VNF实例化装置，包括：
接收单元，用于接收虚拟网络功能VNF实例化请求消息；
处理单元，用于获取所述VNF实例化需调用的容器服务实例的部署信息，根据所述容器服务实例的部署信息确定一个或多个容器服务站点CaaS Cluster；
发送单元，用于分别向所述一个或多个CaaS Cluster中的容器服务管理器CaaS Manager发送容器服务实例创建请求；
所述接收单元，还用于所述CaaS Manager接收容器服务实例创建成功消息。
本发明实施例提供了一种虚拟网络功能VNF实例化系统，包括虚拟网络功能VNF服务实例化装置和一个或多个容器服务管理器CaaS Manager，其中，
VNF服务实例化装置用于接收VNF实例化请求消息，获取所述VNF实例化需调用的容器服务实例的部署信息；根据所述容器服务实例的部署信息确定一个或多个CaaS Cluster，并 向所述一个或多个CaaS Cluster中的容器服务管理器CaaS Manager发送容器服务实例创建请求；从所述CaaS Manager接收容器服务实例创建成功消息。
所述CaaS Manager用于接收所述器服务实例创建请求，创建相应的容器服务实例，并向VNF服务实例化装置发送容器服务实例创建成功消息。
本发明实施例还提供了一种虚拟网络功能VNF服务实例化装置，所述装置包括处理器和存储器；所述存储器用于存储执行如上所述方法的程序，以及存储用于上述方法所涉及的数据；所述处理器用于执行所述存储器中存储的程序。
本发明实施例还提供了一种计算机可读存储介质，该计算机可读存储介质存储有可执行程序指令，所述可执行程序指令被运行时，用于执行上述方法涉及的步骤。
本发明实施例还提供了一种计算机程序产品，当该计算机产品被执行时，用于执行上面所述的方法步骤。
上述实施例是在MANO架构下针对一个或多个CaaS Cluster的场景提出的，通过上述方案解决了NFV场景下容器服务的跨站点部署以及管理问题，使得VNF的容器服务可以部署在不同的CaaS Cluster中，MANO系统可以对所管理的一个或多个CaaS Cluster进行统一控制和管理。
附图说明
图1是本发明实施例提供的一种NFV架构示意图；
图2是本发明实施例提供的一种部署有CaaS Cluster的NFV架构示意图；
图3是本发明实施例提供的一种VNF实例化流程示意图；
图4是本发明实施例提供的一种容器服务实例批量查询/更新/删除的流程示意图；
图5是本发明实施例提供的一种容器服务实例状态维护的流程示意图；
图6是本发明实施例提供的一种VNF实例化装置示意图；
图7是本发明实施例提供的一种VNF实例化系统示意图；
图8是本发明实施例提供的一种VNF实例化装置硬件示意图。
具体实施方式
为使本申请的目的、技术方案和优点更加清楚，下面将结合附图对本申请实施方式作进一步地详细描述。
在对本申请实施例作进一步地详细描述之前，先对本申请实施例的应用场景进行介绍。
由于本申请实施例的容器管理器(CaaS Manager)部署在NFV架构中，因此，在此先对NFV架构进行介绍。图1是本申请实施例提供的一种NFV架构示意图，该NFV系统架构能够应用于各种类型的网络中，譬如，可以应用于运营商通信网络或局域网络中等。
如图1所示，该NFV架构主要包括有MANO实体110、NFVI 120、多个VNF 130、多个网元管理(Element Management，EM)140以及业务支持管理系统(Operation Support System/Business Support System，OSS/BSS)150等。其中，该MANO实体110还包括有网络功能虚拟化编排器(NFV Orchestrator，NFVO)110a、一个或者多个虚拟网络功能管理器(Virtualised Network Function Manager,VNFM)110b以及虚拟化基础设施管理器(Virtualized Infrastructure Manager，VIM)110c。
为了后续便于说明，接下来对图1中NFV架构中的各个模块的功能进行介绍。
NFVO 110a用于实现网络服务描述符(Network Service Descriptors，NSD)，以及虚拟网络功能转发图(VNF Forwarding Graph，VNFFG)的管理及处理、网络服务生命周期的管理、与VNFM配合实现VNF的生命周期管理和虚拟资源的全局视图功能。
VNFM 110b用于实现VNF的生命周期管理，包括虚拟化网络功能描述符(VNF Descriptor，VNFD)文件的管理、VNF的实例化、VNF实例的弹性伸缩(包括扩容Scaling out/up和缩容Scaling in/down)、VNF实例的治愈(Healing)以及VNF实例的终结等。VNFM还支持接收NFVO下发或VNFD中定义的弹性伸缩(Scaling)策略，实现自动化的VNF弹性伸缩。
VIM 110b用于负责基础设施层硬件资源、虚拟化资源的管理(包括预留和分配)、虚拟资源状态的监控和故障上报、面向上层应用提供虚拟化资源池。
OSS/BSS 150是指运营商现有的运行维护系统OSS/BSS。
EM 140用于针对VNF 130执行传统的故障、配置、用户、性能和安全管理(Fault Management、Configuration Management、Account Management、Performance Management、Security Management，FCAPS)功能。
VNF 130对应于传统非虚拟化网络中的物理网络功能(Physical Network Function，PNF)，如虚拟化的4G核心网络(Evolved Packet Core，EPC)EPC节点，比如移动管理实体(Mobility Management Entity，MME)、服务网关(Serving Gate Way，SGW)、分组数据网关(Packet Data Network Gateway，PGW)等。其中，网络功能的功能性行为和状态与虚拟化与否无关，NFV技术的需求是希望VNF和PNF拥有相同的功能性行为和外部接口。
另外，VNF 130可以由多个VNF组件(VNF Component，VNFC)来组成，因此，实际应用中，一个VNF 130可以部署在多个虚拟机(Virtual Machine，VM)上，每个VM承载一个VNF组件的功能。当然，一个VNF 130也可以部署在一个VM上。
NFVI 120是由硬件资源和虚拟资源以及虚拟化层组成，从VNF 130的角度来说，虚拟化层和硬件资源看起来是一个能够提供所需虚拟资源的完整实体。
图2是本申请实施例提供的一种部署有一个或多个容器服务站点(CaaS Cluster)的NFV架构示意图。
一个或多个CaaS Cluster与MANO系统中的NFVO和/或VNFM对接，每个CaaS Cluster中分别部署一个容器管理器(CaaS Manager)，CaaS Manager在各自所在的CaaS Cluster内实例化容器服务，并对容器服务实例进行管理和调度。NFVO或VNFM通过与各CaaS Cluster 中的CaaS Manager连接，可以获取各个CaaS Cluster中的容器资源状态信息并向CaaS Cluster发送容器服务请求。
现有技术描述VNF的VNFD字段主要包括deployment flavour以及deployment flavour中的VduProfile等参数。deployment flavour用于描述VNF部署时的一种特定部署方案，其包含各种部署时的需求，比如部署所需的虚拟资源规格(例如虚拟机的cpu数量、内存大小；容器的cpu数量等)、VNF所支持的生命周期管理操作、组件间的亲和/反亲和关系、支持的监控指标和扩缩容参数等等。VduProfile用于描述虚拟机/容器的规格信息、部署数量等。上述参数的作用在现有标准已有描述，这里不再赘述。
但在本发明实施例中实际部署时，需要在现有技术中描述VNF的VNFD字段中增加对容器服务实例的部署信息，可以包括但不限于以下几种信息：
1.容器服务实例部署位置信息。
如具体部署在哪一个或几个CaaS Cluster中，可以通过CaaS Cluster名称，ID或Label等进行标识。
2.亲和/反亲和规则。
如VNF内部分为两部分，互为主备，要求在两个CaaS Cluster间反亲和部署，即每个CaaS Cluster部署一部分。
3.各CaaS Cluster的部署权重(按权重比例部署实例)、各CaaS Cluster部署的容器服务实例数量或限额等。
其中，部署权重用于指示VNFM按照定义的权重比例来将所需部署的容器服务实例分配到各个CaaS Cluster中，比如特定容器服务实例需要部署在Cluster A、B、C中，其部署权重分别为6、3、1，则Cluster A中部署所有容器服务实例中60％(6/(6+3+1))的实例，B和C分别部署30％和10％的容器服务实例。容器服务实例数量用于直接指定各CaaS Cluster中所需部署的实例数目，比如指定Cluster A、B、C中分别部署2、3、5个容器服务实例。限额用于指定各CaaS Cluster所能部署容器服务实例数量的最大值，比如指定Cluster A、B、C中分别最多部署10、15、5个容器服务实例，在初始部署及后续的生命周期管理(如扩容)当中，在各CaaS Cluster中部署的容器服务实例数量不能超过限额指定的数目。
上述在VNFD字段中增加容器服务实例部署信息可采用两种方式实现：
1)增加专门的字段描述容器服务实例部署信息。
2)重用和增加VNFD中现有的虚拟化部署单元(Virtual ization Deployment Unit，VDU)字段，它在现有标准中用于描述虚拟机的资源需求，重用这个字段用于描述容器的资源需求，在其中增加对CaaS Cluster的部署需求。
关于上述方式1)具体如何实施，可参考如下方式：
Figure PCTCN2019129578-appb-000001
其中，在容器部署场景中亲和/反亲和规则可以参考如下方式：
Figure PCTCN2019129578-appb-000002
针对上述方式2)，可参考如下方式：
Figure PCTCN2019129578-appb-000003
其中，亲和/反亲和规则可参考方式1)。
NFVO或者VNFM接收虚拟网络功能VNF实例化请求消息后，以及在向CaaS Manager发送服务请求之前，需要先从数据库中获取相应的VNFD，并从中获取容器服务实例部署信息，然后根据本地已部署的CaaS Cluster信息，包括数量、处理能力等信息(上述信息可通过查询事先获取，或基于外部配置)选择合适的CaaS Cluster，再向符合条件的CaaS Cluster的CaaS Manager发送服务请求，包括：创建容器、更新、查询和删除等。
除向CaaS Manager发起服务请求之外，NFVO或VNFM还需要对各个CaaS Cluster状态进行维护，即定期向各个CaaS Cluster的CaaS Manager查询当前VNF实例的状态，如果与VNFD中所描述的状态不一致，则触发相应的服务申请，对容器进行创建/删除/更新等，使实际状态与VNFD中描述一致。另外，NFVO、VNFM还可以提供不同CaaS Cluster间的DNS和负载均衡服务，使得跨站点部署的VNF可以顺利完成站点间的业务通信。
下面通过几个具体实施例来对本发明的技术方案作进一步描述。
图3是VNF实例化流程图，具体包括容器服务实例的实例化以及VNF实例的相应初始化配置，所述步骤具体如下：
301：VNFM接收来自Sender的VNF实例化请求消息，Sender可以是NFVO或EM；或者NFVO在处理实例化网络服务(Network Service，NS)请求过程中需要进行VNF实例化；或者NFVO接收到VNFM发起的授权(Granting)请求，要求对VNF实例化进行授权。
302：NFVO或VNFM从所需实例化的VNF所对应的VNFD中获取容器服务实例的部署信息。所述容器服务实例的部署信息，如上所述可以包括：容器服务实例部署位置信息；亲和/反亲和规则；CaaS Cluster的部署权重(按权重比例部署实例)、数量、限额等。
303：NFVO或VNFM根据所述容器部署信息确定一个或多个容器服务站点CaaS Cluster。
具体地，NFVO或VNFM根据VNFD中获取的容器服务实例部署信息，以及本地存储的各CaaS Cluster信息，选择合适的CaaS Cluster。
如果容器服务实例部署信息包括CaaS Cluster名称或ID，则选取对应的Cluster；如指定CaaS Cluster具有的label，则遍历所管理的CaaS Cluster，查找包含对应label的CaaS Cluster等。
可选地，如果所选的CaaS Cluster资源不足，且NFVO或VNFM具备向VIM申请CaaS Cluster资源的能力，则NFVO或VNFM可向VIM申请物理服务器或者虚拟机资源，接入到对应CaaS Cluster的CaaS Manager管理中，增加其容量。
304：NFVO或VNFM分别向所述一个或多个CaaS Cluster中的容器即服务管理器CaaS manager发送容器服务实例创建请求。
305：各个CaaS Cluster内部的CaaS Manager接收到请求后，进行容器服务实例的创建(实例化)操作，
306.各个CaaS Cluster发送容器服务实例创建成功响应消息至NFVO或VNFM。
307：NFVO或VNFM将容器服务实例的部署信息存储在本地，然后直接或通知EMS对VNF实例进行初始化配置。
308.NFVO或VNFM向发起VNF实例创建请求的发起方发送VNF实例化成功响应消息。
图4是VNF实例查询/更新/删除的流程图，具体步骤包括：
401：VNFM接收来自Sender的VNF查询/更新/删除请求消息，Sender可以是NFVO或EM；或者NFVO在处理实例化NS(Network Service，网络服务)请求过程中需要进行VNF的容器服务实例查询/更新/删除。
402：NFVO或VNFM从本地存储信息中获取VNF的容器服务实例部署位置信息，即部署在哪些CaaS Cluster中。
403：NFVO或VNFM向对应的CaaS Manager发起查询/更新/删除容器服务实例的请求。
404：各个CaaS Cluster内部的CaaS Manager接收请求后，进行相应的查询/更新/删除操作，并将结果反馈至NFVO或VNFM。
405：NFVO或VNFM根据反馈信息进行本地信息更新，并反馈给请求发起方。
图5是VNF的容器服务实例维护流程图，具体步骤包括：
501：NFVO或VNFM定期向所管理的CaaS Cluster中的CaaS Manager进行状态查询，或者由各CaaS Manager定期向NFVO/VNFM上报当前容器实例状态。
502：NFVO或VNFM根据获取到的容器服务实例状态与VNFD中所描述的容器服务实例部署信息进行比较。
503：如果一致不做任何处理。如果状态不一致，则NFVO或VNFM向对应的CaaS Manager发起相应容器服务实例操作请求。例如，某个CaaS Cluster中实际部署的容器服务实例数量 少于VNFD中规定的数量，则NFVO或VNFM需要向所述CaaS Cluster发起容器服务实例创建请求，以使实际部署数量与需求一致。
如果发生CaaS Cluster整体异常，NFVO或VNFM无法与相应的CaaS Manager建立通信，则NFVO或VNFM需要根据VNFD中的容器服务实例部署需求和本地存储的CaaS Cluster信息，重新选择合适的CaaS Cluster(跟图3的流程类似)，将故障Cluster所需承载的容器服务实例部署到新选择的CaaS Cluster中，以使得整体部署结果和VNFD中的需求保持一致。
504：在所述CaaS Cluster创建容器服务实例完成后，NFVO或VNFM接收其反馈结果。
上述各个方法实施例是在MANO架构下针对一个或多个CaaS Cluster的场景提出的，通过上述方法流程解决了NFV场景下容器服务的跨站点部署以及管理问题，使得VNF的容器服务可以部署在不同的CaaS Cluster中，MANO系统可以对所管理的一个或多个CaaS Cluster进行统一控制和管理。
下面对上述方法实施例中涉及的相关装置或设备进行进一步的描述，具体如下：
图6是一种虚拟网络功能VNF实例化装置示意图，该装置包括：
接收单元610，用于接收虚拟网络功能VNF实例化请求消息；
处理单元620，用于获取所述VNF实例化需调用的容器服务实例的部署信息，根据所述容器部署信息确定一个或多个容器服务站点CaaS Cluster；
发送单元630，用于分别向所述一个或多个CaaS Cluster中的容器即服务管理器CaaS Manager发送容器服务实例创建请求；
所述接收单元610，还用于所述CaaS Manager接收容器服务实例创建成功响应消息。
上述各个单元的具体步骤和功能可以参考上述图3-图5所示方法步骤的描述，这里不再重复。
图7是一种VNF实例化系统示意图，该系统包括：
VNF实例化装置，以及一个或多个CaaS Cluster,其中，
VNF服务实例化装置用于接收VNF实例化请求消息，获取所述VNF实例化需调用的容器服务站点CaaS Cluster能力信息；根据所述CaaS Cluster能力信息确定一个或多个CaaS Cluster，并向所述一个或多个CaaS Cluster中的容器即服务管理器CaaS manager发送容器服务实例创建请求；从CaaS Manager接收容器服务实例创建成功消息。
所述一个或多个CaaS管理器用于根据所述CaaS Cluster能力信息创建相应的容器服务实例，并向VNF服务实例化装置发送容器服务实例创建成功消息。
其中，虚拟网络功能VNF服务实例化装置为网络功能虚拟化编排器NFVO或虚拟网络功能管理器VNFM。
上述各个装置的具体步骤和功能可以参考上述图3-图5方法步骤的描述，这里不再重复。
图8是本发明实施例提供的VNF实例化装置硬件图，所述装置80可以包括：处理器、通 信接口以及存储器。
处理器81可以包括一个或者一个以上处理单元，该处理单元可以是中央处理单元(英文：central processing unit，CPU)或者网络处理器(英文：network processor，NP)等。
通信接口84用于跟其他通信设备连接和信息交互，包括接收和发送相应的消息；该网络设备80还可以包括存储器83，处理器81可以通过总线与存储器83和通信接口84相连。存储器83可用于存储软件程序，该软件程序可以由处理器81执行，以实现图3中所示实施例中由VNFM执行的方法步骤。此外，该存储器83中还可以存储各类业务数据或者用户数据,包括上述方法步骤中的各种应用实例和服务的状态数据等。
可选地，该装置80还可以包括输出设备85以及输入设备88。输出设备85和输入设备88与处理器81相连。输出设备85可以是用于显示信息的显示器、播放声音的功放设备或者打印机等，输出设备85还可以包括输出控制器，用以提供输出到显示屏、功放设备或者打印机。输入设备88可以是用于用户输入信息的诸如鼠标、键盘、电子触控笔或者触控面板之类的设备，输入设备88还可以包括输出控制器以用于接收和处理来自鼠标、键盘、电子触控笔或者触控面板等设备的输入
同样地，上述装置硬件图也适用于CaaS Cluster装置，区别是存储器83存储的软件程序由处理器81执行，以实现图3中所示实施例中由CaaS Cluster执行的方法步骤，这里不再重复。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意结合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如：同轴电缆、光纤、数据用户线(Digital Subscriber Line，DSL))或无线(例如：红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如：软盘、硬盘、磁带)、光介质(例如：数字通用光盘(Digital Versatile Disc，DVD))、或者半导体介质(例如：固态硬盘(Solid State Disk，SSD))等。
本领域普通技术人员可以理解实现上述实施例的全部或部分步骤可以通过硬件来完成，也可以通过程序来指令相关的硬件完成，所述的程序可以存储于一种计算机可读存储介质中，上述提到的存储介质可以是只读存储器，磁盘或光盘等。
以上所述为本申请提供的实施例，并不用以限制本申请，凡在本申请的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本申请的保护范围之内。

Claims (20)

  1. 一种虚拟网络功能VNF实例化方法，所述方法由网络功能虚拟化编排器NFVO或虚拟网络功能管理器VNFM执行，其特征在于，包括：
    接收虚拟网络功能VNF实例化请求消息；
    获取所述VNF实例化需调用的容器服务实例的部署信息；
    根据所述容器服务实例的部署信息确定一个或多个容器服务站点CaaS Cluster，并分别向所述一个或多个CaaS Cluster中的容器服务管理器CaaS Manager发送容器服务实例创建请求；
    从所述CaaS Manager接收容器服务实例创建成功消息。
  2. 根据权利要求1所述的方法，其特征在于，获取所述VNF实例化需调用的容器服务的部署信息包括：
    VNFM根据所述VNF实例化请求消息，在数据库中获取相应的VNFD，并在所述VNFD中获取相应的容器服务实例的部署信息。
  3. 根据权利要求1所述的方法，其特征在于，所述容器服务实例的部署信息包括下面的一项或多项：
    指定的Cluster名称，或
    亲和/反亲和规则，或
    在多CaaS Cluster部署时各CaaS Cluster的部署权重或各CaaS Cluster部署的容器服务实例数量或限额。
  4. 根据权利要求1所述的方法，其特征在于，
    如果所选的CaaS Cluster资源不足，则向虚拟化基础设施管理器VIM申请物理服务器或者虚拟机资源，增加所选CaaS Cluster的资源。
  5. 根据权利要求1所述的方法，其特征在于，所述方法进一步包括：
    将容器服务实例的部署信息存储在本地，对VNF实例进行初始化配置，创建相应的VNF实例。
  6. 根据权利要求5所述的方法，其特征在于，所述方法进一步包括：
    接收VNF查询/更新/删除请求消息；
    从本地存储信息中获取容器服务部署的CaaS Cluster，所述CaaS Cluster为一个或多个；
    向对应的CaaS Cluster中的CaaS Manager发起查询/更新/删除容器服务实例的请求；
    在CaaS Manager进行相应的容器操作后，接收CaaS Manager反馈的信息并进行本地信息更新。
  7. 根据权利要求1所述的方法，其特征在于，所述方法进一步包括：
    向CaaS Cluster中的CaaS Manager进行状态查询或者接收CaaS Manager周期性上报的当前容器服务实例状态；
    根据获取到的容器实例状态与VNFD中的部署信息进行比较，如果状态不一致，则向对应的CaaS Manager发起相应的容器实例操作请求。
  8. 根据权利要求1或5所述的方法，其特征在于，所述方法进一步包括：
    向CaaS Cluster中的CaaS Manager进行状态查询；
    如果发生CaaS Cluster故障，则根据VNFD中的容器服务实例的部署信息和/或本地存储的容器服务实例的部署信息，重新选择合适的CaaS Cluster，将故障CaaS Cluster承载的容器服务实例部署到新选择的CaaS Cluster中。
  9. 一种虚拟网络功能VNF实例化装置，其特征在于，包括：
    接收单元，用于接收虚拟网络功能VNF实例化请求消息；
    处理单元，用于获取所述VNF实例化需调用的容器服务实例的部署信息，根据所述容器服务实例的部署信息确定一个或多个容器服务站点CaaS Cluster；
    发送单元，用于分别向所述一个或多个CaaS Cluster中的容器服务管理器CaaS Manager发送容器服务实例创建请求；
    所述接收单元，还用于所述CaaS Manager接收容器服务实例创建成功消息。
  10. 根据权利要求9所述的装置，其特征在于，获取所述VNF实例化需调用的容器服务的部署信息包括：
    VNFM根据所述VNF实例化请求消息，在数据库中获取相应的VNFD，并在所述VNFD中获取相应的容器服务实例的部署信息。
  11. 根据权利要求9所述的装置，其特征在于，所述容器服务实例的部署信息包括下面的一项或多项：
    指定的Cluster名称，或
    亲和/反亲和规则，或
    在多CaaS Cluster部署时各CaaS Cluster的部署权重、各CaaS Cluster部署的容器服务实例数量或限额。
  12. 根据权利要求9所述的装置，其特征在于，如果所选的CaaS Cluster资源不足，则向虚拟化基础设施管理器VIM申请物理服务器或者虚拟机资源，增加所选CaaS Cluster的资源。
  13. 根据权利要求9所述的装置，其特征在于，
    所述处理单元还用于将容器服务实例的部署信息存储在本地，对VNF实例进行初始化配 置，创建相应的VNF实例。
  14. 一种虚拟网络功能VNF实例化系统，包括虚拟网络功能VNF服务实例化装置和一个或多个容器服务管理器CaaS Manager，其特征在于，
    VNF服务实例化装置用于接收VNF实例化请求消息，获取所述VNF实例化需调用的容器服务实例的部署信息；根据所述容器服务实例的部署信息确定一个或多个CaaS Cluster，并向所述一个或多个CaaS Cluster中的容器服务管理器CaaS Manager发送容器服务实例创建请求；从所述CaaS Manager接收容器服务实例创建成功消息；
    所述CaaS Manager用于接收所述器服务实例创建请求，创建相应的容器服务实例，并向VNF服务实例化装置发送容器服务实例创建成功消息。
  15. 根据权利要求14所述的系统，其特征在于，获取所述VNF实例化需调用的容器服务的部署信息包括：
    VNFM根据所述VNF实例化请求消息，在数据库中获取相应的VNFD，并在所述VNFD中获取相应的容器服务实例的部署信息。
  16. 根据权利要求14所述的系统，其特征在于，所述容器服务实例的部署信息包括下面的一项或多项：
    指定的Cluster名称，或
    亲和/反亲和规则，或
    在多CaaS Cluster部署时各CaaS Cluster的部署权重、各CaaS Cluster部署的容器服务实例数量或限额。
  17. 根据权利要求14所述的系统，其特征在于，如果所选的CaaS Cluster资源不足，则向虚拟化基础设施管理器VIM申请物理服务器或者虚拟机资源，增加所选CaaS Cluster的资源。
  18. 根据权利要求14所述的系统，其特征在于，
    所述VNF服务实例化装置还用于将容器服务实例的部署信息存储在本地，对VNF实例进行初始化配置，创建相应的VNF实例。
  19. 一种虚拟网络功能VNF服务实例化装置，其特征在于，所述装置包括处理器和存储器；
    所述存储器用于存储执行权利要求1-8任一项所述方法的程序，以及存储用于实现权利要求1-8任一项所述方法所涉及的数据；
    所述处理器用于执行所述存储器中存储的程序。
  20. 一种计算机可读存储介质，该计算机可读存储介质存储有可执行程序指令，所述可执行程序指令被运行时，用于执行上述1-8中的任一权利要求所述的步骤。
PCT/CN2019/129578 2018-12-28 2019-12-28 Vnf服务实例化方法及装置 WO2020135799A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP19906357.9A EP3893438A4 (en) 2018-12-28 2019-12-28 Vnf service instantiation method and device
US17/356,874 US12020055B2 (en) 2018-12-28 2021-06-24 VNF service instantiation method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201811624936.6 2018-12-28
CN201811624936.6A CN111385114B (zh) 2018-12-28 2018-12-28 Vnf服务实例化方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/356,874 Continuation US12020055B2 (en) 2018-12-28 2021-06-24 VNF service instantiation method and apparatus

Publications (1)

Publication Number Publication Date
WO2020135799A1 true WO2020135799A1 (zh) 2020-07-02

Family

ID=71129169

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/129578 WO2020135799A1 (zh) 2018-12-28 2019-12-28 Vnf服务实例化方法及装置

Country Status (4)

Country Link
US (1) US12020055B2 (zh)
EP (1) EP3893438A4 (zh)
CN (1) CN111385114B (zh)
WO (1) WO2020135799A1 (zh)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113918268A (zh) * 2020-07-07 2022-01-11 华为技术有限公司 一种多租户管理方法及装置
WO2022199825A1 (en) 2021-03-25 2022-09-29 Telefonaktiebolaget Lm Ericsson (Publ) Separation of network function and its realization
CN115599410A (zh) * 2022-12-15 2023-01-13 杭州数列网络科技有限责任公司（Cn） 一种大规模java探针管理的方法及系统
WO2023046026A1 (zh) * 2021-09-27 2023-03-30 华为技术有限公司 一种容器化vnf的部署方法及装置
WO2023169175A1 (zh) * 2022-03-08 2023-09-14 北京字节跳动网络技术有限公司 一种请求处理方法、装置、计算机设备和存储装置

Families Citing this family (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114880078A (zh) * 2018-06-05 2022-08-09 华为技术有限公司 管理容器服务的方法和装置
CN112583625B (zh) * 2019-09-30 2023-12-08 中兴通讯股份有限公司 网络资源管理方法、系统、网络设备和可读存储介质
US11836225B1 (en) * 2020-08-26 2023-12-05 T-Mobile Innovations Llc System and methods for preventing unauthorized replay of a software container
CN112463535B (zh) * 2020-11-27 2024-05-10 中国工商银行股份有限公司 多集群异常处理方法及装置
JP2024501005A (ja) * 2020-12-28 2024-01-10 華為技術有限公司 コンテナクラスタのための管理方法および装置
CN113535385A (zh) * 2021-06-21 2021-10-22 广州杰赛科技股份有限公司 虚拟网络功能部署方法、装置、设备及存储介质
CN116016229A (zh) * 2021-10-21 2023-04-25 华为技术有限公司 一种部署容器服务的方法及装置
TWI786908B (zh) * 2021-10-28 2022-12-11 中華電信股份有限公司 用於優化網路功能管理之系統、方法及其電腦可讀媒介
CN113938930B (zh) * 2021-12-16 2022-03-25 中国船舶重工集团公司第七二二研究所 适应5g网络多业务场景的虚拟网络功能转发图的构建方法
WO2023137712A1 (en) * 2022-01-21 2023-07-27 Zte Corporation Method, device and computer program product for wireless communication
CN114610446B (zh) * 2022-03-11 2023-01-03 北京基调网络股份有限公司 一种自动注入探针的方法、装置及系统
CN116841689A (zh) * 2022-03-25 2023-10-03 华为技术有限公司 一种部署vnf的方法、装置及设备
CN115412440B (zh) * 2022-08-19 2024-07-09 浪潮思科网络科技有限公司 一种vnf设备分布式部署方法及设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105550130A (zh) * 2015-12-14 2016-05-04 中电科华云信息技术有限公司 基于容器的应用环境动态编排的方法及其应用系统
US20170257432A1 (en) * 2011-02-09 2017-09-07 Cliqr Technologies Inc. Apparatus, systems and methods for container based service deployment
WO2017157156A1 (zh) * 2016-03-14 2017-09-21 阿里巴巴集团控股有限公司 一种用户请求的处理方法和装置
CN108304250A (zh) * 2018-03-05 2018-07-20 北京百度网讯科技有限公司 用于确定运行机器学习任务的节点的方法和装置

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105812171B (zh) * 2014-12-31 2019-06-11 华为技术有限公司 一种虚拟化的网络功能vnf控制方法和设备
KR102178225B1 (ko) * 2015-01-20 2020-11-12 후아웨이 테크놀러지 컴퍼니 리미티드 Ｎｆｖ 관리 및 편성을 위한 방법 및 장치
WO2017144094A1 (en) * 2016-02-24 2017-08-31 Telefonaktiebolaget Lm Ericsson (Publ) Managing planned adjustment of allocation of resources in a virtualised network
WO2017166136A1 (zh) * 2016-03-30 2017-10-05 华为技术有限公司 一种vnf的资源分配方法及装置
CN106161603B (zh) * 2016-06-28 2019-09-20 华为技术有限公司 一种组网的方法、设备及架构
US10856183B2 (en) * 2016-11-10 2020-12-01 Huawei Technologies Co., Ltd. Systems and methods for network slice service provisioning
CN108400998B (zh) * 2017-02-07 2020-03-20 华为技术有限公司 一种部署vnf的方法和系统
US10761896B2 (en) * 2017-02-22 2020-09-01 Cisco Technology, Inc. System and method of lightweight decentralized NFV orchestration
EP3593494B1 (en) * 2017-03-09 2021-10-06 Telefonaktiebolaget LM Ericsson (publ.) Configuration generation for virtual network functions (vnfs) with requested service availability
US20200012510A1 (en) * 2017-03-24 2020-01-09 Nokia Technologies Oy Methods and apparatuses for multi-tiered virtualized network function scaling
CN107426109B (zh) * 2017-06-27 2020-10-09 上海华为技术有限公司 一种流量调度方法、vnf模块及流量调度服务器

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170257432A1 (en) * 2011-02-09 2017-09-07 Cliqr Technologies Inc. Apparatus, systems and methods for container based service deployment
CN105550130A (zh) * 2015-12-14 2016-05-04 中电科华云信息技术有限公司 基于容器的应用环境动态编排的方法及其应用系统
WO2017157156A1 (zh) * 2016-03-14 2017-09-21 阿里巴巴集团控股有限公司 一种用户请求的处理方法和装置
CN108304250A (zh) * 2018-03-05 2018-07-20 北京百度网讯科技有限公司 用于确定运行机器学习任务的节点的方法和装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3893438A4 *

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113918268A (zh) * 2020-07-07 2022-01-11 华为技术有限公司 一种多租户管理方法及装置
WO2022007631A1 (zh) * 2020-07-07 2022-01-13 华为技术有限公司 一种多租户管理方法及装置
EP4177742A4 (en) * 2020-07-07 2023-12-06 Huawei Technologies Co., Ltd. METHOD AND DEVICE FOR MANAGING MULTI-TENANT CAPABILITY
WO2022199825A1 (en) 2021-03-25 2022-09-29 Telefonaktiebolaget Lm Ericsson (Publ) Separation of network function and its realization
WO2023046026A1 (zh) * 2021-09-27 2023-03-30 华为技术有限公司 一种容器化vnf的部署方法及装置
WO2023169175A1 (zh) * 2022-03-08 2023-09-14 北京字节跳动网络技术有限公司 一种请求处理方法、装置、计算机设备和存储装置
CN115599410A (zh) * 2022-12-15 2023-01-13 杭州数列网络科技有限责任公司（Cn） 一种大规模java探针管理的方法及系统

Also Published As

Publication number Publication date
US12020055B2 (en) 2024-06-25
EP3893438A1 (en) 2021-10-13
CN111385114B (zh) 2022-04-26
EP3893438A4 (en) 2021-12-29
US20210326167A1 (en) 2021-10-21
CN111385114A (zh) 2020-07-07

Similar Documents

Publication Publication Date Title
WO2020135799A1 (zh) Vnf服务实例化方法及装置
US10701139B2 (en) Life cycle management method and apparatus
US11947697B2 (en) Method and system to place resources in a known state to be used in a composed information handling system
WO2018024059A1 (zh) 一种虚拟化网络中业务部署的方法和装置
US10700947B2 (en) Life cycle management method and device for network service
KR102059251B1 (ko) 노드 시스템, 서버 장치, 스케일링 제어 방법 및 프로그램
US11611481B2 (en) Policy management method and system, and apparatus
WO2015131696A1 (zh) 一种虚拟化网络功能管理的方法和装置
WO2020135228A1 (zh) 云平台部署方法、装置、服务器及存储介质
WO2016121834A1 (ja) ネットワーク機能仮想化管理方法とシステムと装置とプログラム
WO2016197346A1 (zh) 一种虚拟网络功能的生命周期管理方法，及装置
WO2020211652A1 (zh) 多租户场景下的租户资源管理方法和装置
WO2019047835A1 (zh) 虚拟网络功能的实例化方法
WO2019129118A1 (zh) Vnf服务实例化方法及装置
WO2020140945A1 (zh) 基于容器的虚拟资源管理方法、装置及系统
US11442756B2 (en) Common service resource application method, related device, and system
US12073258B2 (en) Configuration map based sharding for containers in a machine learning serving infrastructure
WO2022140945A1 (zh) 容器集群的管理方法和装置
CN109905258B (zh) PaaS的管理方法、装置及存储介质
CN110413369A (zh) 用于虚拟化环境中的备份的系统和方法
CN112889247B (zh) Vnf服务实例化方法及装置
WO2022198524A1 (zh) 服务实例部署方法、节点间的负载均衡方法及系统
CN111045778B (zh) 一种虚拟机的创建方法、装置、服务器及存储介质
CN112015515A (zh) 一种虚拟网络功能的实例化方法及装置
WO2018120222A1 (zh) 一种管理vnffg的方法、装置和系统

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

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

Country of ref document: EP

Effective date: 20210705