WO2019129118A1

WO2019129118A1 - Vnf service instantiation method and device

Info

Publication number: WO2019129118A1
Application number: PCT/CN2018/124158
Authority: WO
Inventors: 冯爱娟
Original assignee: 华为技术有限公司
Priority date: 2017-12-29
Filing date: 2018-12-27
Publication date: 2019-07-04
Also published as: CN109995552A; CN109995552B

Abstract

Disclosed are a VNF service instantiation method and device. The method comprises: a VNFM receiving a VNF instantiation request message; acquiring a virtual network function information model describer (VNFD), and generating a virtual machine (VM) according to the VNFD, wherein the VNFD comprises a service group identifier; and the VNFM sending a service group instantiation request to a platform as a service (PaaS) platform, wherein the request comprises a VM identifier and the service group identifier, so that the PaaS platform performs instantiation, in the VM, on services contained in a service group corresponding to the service group identifier. By means of the method, services in a service group are not presented for a VNFM, and the VNFM only needs to send a service group identifier to a PaaS platform without parsing and knowing which specific services are in the service group, and the requirements of different operators are satisfied.

Description

VNF service instantiation method and device

This application claims the priority of the Chinese Patent Application filed on Dec. 29, 2017, the Chinese National Intellectual Property Office, the application number is 201711483185.6, and the invention is entitled "VNF Service Instantiation Method and Apparatus", the entire contents of which are incorporated herein by reference. In the application.

Technical field

The present application relates to the field of cloud computing technologies, and in particular, to a method and an apparatus for instantiating a virtual network function (VNF) service.

Background technique

Platform as a Service (PaaS, Platform as a Service) refers to providing the server as a service to users, so that users can implement network functions such as development, testing, and online deployment of applications on the Internet. At present, the implementation of PaaS is mainly through Network Function Virtualization (NFV) technology, that is, the PaaS is deployed in the NFV architecture, and the virtualized network function (VNF) in the NFV architecture is in the instance. When the service deployed on the PaaS needs to be invoked, the service is instantiated to implement the network function corresponding to the service. Among them, instantiation refers to the process of configuring virtual resources for services or VNFs through the Network Function Virtualization Infrastructure (NFVI) in the NFV architecture.

A typical PaaS platform should provide the following functions: 1) Application runtime environment: including distributed computing runtime environment, multiple types of data storage, dynamic resource scaling; application lifecycle support: including development of SDK, IDE, etc. Develop, test, and deploy. 2) Public service: Provide public services in the form of API, such as queue service, storage service and cache service, monitor, manage and measure: provide resource pool, application system management and monitoring functions, accurate measurement; 3) integration, composite application Building capabilities: including connectivity services, integration services, messaging services, and process services.

With the continuous development of NFV technology, the original VNF representation based on the NFVI layer virtual machine (VM) incorporates new features, supporting cloud-native VNF and converged PaaS platform. The cloud-based architecture of services will become a new trend in the development of telecom clouds. Since cloud-based architecture concepts such as cloud native and PaaS come from the field of IT applications, how these concepts can be applied after adaptation in the field of telecom NFV still needs to explore a viable industrial development path.

In December 2016, Swisscom Telecom proposed the NFV PaaS project in the ETSI NFV Industry Standards Group to determine the impact on the existing NFV architecture when the IFA Working Group studies the service capabilities of the PaaS platform and the VNFs that conform to the cloud's native design principles. Currently, the IFA working group discussed basic concepts in the NFV PaaS scenario, such as Micro Service, Common Service, and Dedicated Service, and reached a preliminary consensus on the definition of these concepts. From the IFA029 existing UseCase process, the call level relationship between the PaaS platform service and the VNF application is highlighted, but the current IFA029 has no clear process and interface description.

Summary of the invention

The present application provides a method, an apparatus, and a system for instantiating a VNF service. The process and the interface are clearly described in relation to the prior art, and the technical solution of the method is as follows:

The virtual network function manager (VNF Manager, VNFM) receives the virtual network function VNF instantiation request message;

The VNFM acquires a virtual network function information model descriptor (VNF Descriptor, VNFD), and generates a virtual machine VM according to the VNFD, wherein the VNFD includes a service group identifier;

The VNFM sends a service group instantiation request to a Platform as a Service (PaaS) platform, where the request includes a VM identifier and a service group identifier, so that the PaaS platform identifies the service corresponding to the service group identifier in the VM. The services contained in the group are instantiated.

Specifically, the VNF instantiation request message includes a Flavour ID, and the VNFM searches for a corresponding virtual deployment unit (VDU) identifier (Identifier, ID) according to the Flavour ID in the VNFD, and then generates a corresponding virtual The machine VM, wherein the VNFD includes a service group identifier corresponding to the VDU ID.

The Flavour ID in the VNFD corresponds to the first VDU ID and the second VDU ID, and the first VDU ID corresponds to the first service group identifier, and the second VDU ID corresponds to the second service group identifier, where the method specifically includes:

The VNFM searches for the corresponding first VDU ID and the second VDU ID according to the Flavour ID in the VNFD.

The VNFM generates a first VM according to the first VDU ID;

The VNFM generates a second VM according to the second VDU ID;

The VNFM sends a first service group instantiation request to the PaaS platform, the request including the first VM identifier, and the first service group identifier, so that the PaaS platform corresponds to the first service group identifier in the first VM The services included in the service group are instantiated;

The VNFM sends a second service group instantiation request to the PaaS platform, where the request includes a second VM identifier and a second service group identifier, so that the PaaS platform corresponds to the second service group identifier in the second VM. The services included in the service group are instantiated.

Further, the method further includes: the VNFM receives the VNF expansion request message, and determines, according to the expansion request message and the VNFD, that the third VDU needs to be added to generate a corresponding third VM; and according to the third VDU ID in the VNFD. Determining a corresponding third service group identifier;

The VNFM sends a third service group instantiation request to the PaaS platform, where the request includes a third VM identifier, and a third service group identifier, so that the PaaS platform corresponds to the third service group identifier in the third VM. The services included in the service group are instantiated.

Further, the method further includes: receiving, by the VNFM, a VNF contraction request message, and determining, according to the shrink request message and the VNFD, a VM that needs to be terminated;

The VNFM sends a final service group request to the PaaS platform, the request including the VM identifier to be terminated, so that the PaaS platform terminates the service included in the service group in the VM to be terminated.

An embodiment of the present invention further provides a VNF service instantiation device, including:

a receiving unit, configured to receive a virtual network function VNF instantiation request message;

a processing unit, configured to acquire a virtual network function information model descriptor VNFD, and generate a virtual machine VM according to the VNFD, where the VNFD includes a service group identifier;

a sending unit, configured to send a service group instantiation request to the platform as a service PaaS platform, where the request includes a VM identifier and a service group identifier, so that the PaaS platform includes the service group corresponding to the service group identifier in the VM The service is instantiated.

Further, the VNF instantiation request message includes a Flavour ID, and the processing unit is configured to search for a corresponding VDU ID according to the Flavour ID in the VNFD, and then generate a corresponding virtual machine VM, where the VNFD includes and Service group ID corresponding to the VDU ID.

The embodiment of the present invention further provides a VNF service instantiation system, including a virtual network function manager VNFM and a platform as a service PaaS platform, where

The VNFM is configured to receive a virtual network function VNF instantiation request message, obtain a virtual network function information model descriptor VNFD, and generate a virtual machine VM according to the VNFD, wherein the VNFD includes a service group identifier, and sends a service to the platform as a service PaaS platform. The group instantiates the request, the request including the VM identifier and the service group identifier;

The PaaS platform is configured to receive a service group instantiation request, and instantiate, in the VM, a service included in the service group corresponding to the service group identifier.

The embodiment of the present invention further provides a virtual network function VNF service instantiation device, the device comprising a processor and a memory; the memory is configured to store a program for performing the method of any one of claims 1-7, and store Data for implementing the method of any of claims 1-7;

The processor is configured to execute a program stored in the memory.

The embodiment of the present invention further provides a computer readable storage medium storing executable program instructions for executing the method steps described above when the executable program instructions are executed.

Embodiments of the present invention also provide a computer program product for performing the method steps described above when the computer product is executed.

In the embodiment of the present invention, since the VDU presents requirements for virtual resources, an operating system (OS), a service group identifier, and the like, the services within the service group are not presented to the VNFM, and the VNFM may not need to parse and know which specific services exist within the service group. Simply send the service group ID to the PaaS platform to meet the requirements of different operators.

DRAWINGS

FIG. 1 is a schematic diagram of an NFV architecture according to an embodiment of the present invention;

2 is a schematic diagram of an NFV architecture deployed with PaaS according to an embodiment of the present invention;

3 is a schematic diagram of a VNF service instantiation process according to an embodiment of the present invention;

4 is a schematic diagram of a logical structure of an example of a VDU according to an embodiment of the present invention;

FIG. 5 is a schematic diagram of a VNF service expansion process according to an embodiment of the present invention; FIG.

FIG. 6 is a schematic diagram of a VNF service shrinking process according to an embodiment of the present invention; FIG.

FIG. 7 is a schematic structural diagram of a VNF service instantiation system according to an embodiment of the present invention; FIG.

FIG. 8 is a schematic diagram of a device for instantiating a VNF service according to an embodiment of the present invention; FIG.

FIG. 9 is a schematic diagram of hardware of a VNF service instantiation device according to an embodiment of the present invention.

Detailed ways

In order to make the objects, technical solutions and advantages of the present application more clear, the embodiments of the present application will be further described in detail below with reference to the accompanying drawings.

Before the embodiments of the present application are further described in detail, the application scenarios of the embodiments of the present application are introduced.

Since the PaaS of the embodiment of the present application is deployed in the NFV architecture, the NFV architecture is first introduced herein. 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, to an operator communication network or a local area network.

As shown in FIG. 1 , the NFV architecture mainly includes a MANO entity 110, an NFVI 120, multiple VNFs 130, multiple Element Management (EM) 140, and an Operation Support System/Business Support System (Operation Support System/Business Support System). OSS/BSS) 150 and so on. The MANO entity 110 further includes a network function virtualization orchestrator (NFVO) 110a, one or more VNFMs 110b, and a virtualized infrastructure manager (VIM) 110c.

For the convenience of the description, the functions of each module in the NFV architecture in FIG. 1 are introduced.

NFVO 110a is used to implement Network Service Descriptors (NSD), and management and processing of VNF Forwarding Graph (VNFFG), management of network service life cycle, and VNFM to achieve VNF life cycle. Management and global view capabilities of virtual resources.

VNFM 110b is used to implement VNF lifecycle management, including management of virtualized network function descriptors (VNFD) files, instantiation of VNFs, and elastic scaling of VNF instances (including expansion of Scaling out/up and shrinking Scaling in). /down), healing of the VNF instance and the end of the VNF instance. VNFM also supports the elastic scaling mechanism delivered by NFVO to implement automated VNF elastic scaling.

The VIM 110b is responsible for managing the infrastructure layer hardware resources, virtualized resources (including reservation and allocation), monitoring and fault reporting of virtual resource status, and providing virtualized resource pools for upper-layer applications.

OSS/BSS 150 refers to the operator's existing operation and maintenance system OSS/BSS.

The EM 140 is used to perform traditional fault, configuration, user, performance, and security management (Fault Management, Configuration Management, Account Management, Performance Management, Security Management, FCAPS) functions for the VNF 130.

The VNF 130 corresponds to a Physical Network Function (PNF) in a traditional non-virtualized network, such as a virtualized 4G core network (Evolved Packet Core, EPC) EPC node, such as a Mobility Management Entity (MME). , Serving Gate Way (SGW), Packet Data Network Gateway (PGW), etc. Among them, the functional behavior and state of network functions are not related to virtualization. The requirement of NFV technology is that VNF and PNF have the same functional behavior and external interfaces.

In addition, the VNF 130 can be composed of multiple VNF components (VNFCs). Therefore, in practical applications, one VNF 130 can be deployed on multiple virtual machines (VMs), each VM carrying a VNF component. The function. Of course, a VNF 130 can also be deployed on a VM.

NFVI 120 is composed of hardware resources and virtual resources and a virtualization layer. From the perspective of VNF 130, the virtualization layer and hardware resources appear to be a complete entity capable of providing the required virtual resources.

2 is a schematic diagram of an NFV architecture deployed with PaaS according to an embodiment of the present application. As shown in FIG. 2, the NVF architecture shown in FIG. 2 further includes a PaaS platform 160, as shown in FIG. The PaaS platform 160 includes a plurality of services and PaaS management for managing the plurality of services.

In addition, the PafS platform deployed in the NFV architecture and the VNFM entity in the NFV architecture are used to perform the methods of the embodiments of the present application. The main processes of the method include:

The VNFM receives the VNF instantiation request message;

The VNFM acquires a virtual network function information model descriptor VNFD, and generates a virtual machine VM according to the VNFD, wherein the VNFD includes a service group identifier;

The VNFM sends a service group instantiation request to the platform as a service PaaS platform, where the request includes a VM identifier and a service group identifier, so that the PaaS platform performs an instance of the service included in the service group corresponding to the service group identifier in the VM. Chemical.

The following is a detailed explanation of the foregoing process. FIG. 3 is a flowchart of an NFV service instantiation provided in the embodiment of the present application. The method is applied to the NFV architecture deployed in the PaaS platform shown in FIG. 2, and the method includes the following steps. :

301. The VNFM receives the instantiated VNF request message, where the request message carries a Flavour ID.

The instantiated VNF request message may be sent by the NFVO, or may be sent by other NFV entities.

302. The VNFM searches for the corresponding VDU ID according to the Flavour ID in the VNFD, allocates a virtual resource, and loads the OS, and completes startup of the virtual machine VM.

Before step 301, the VNFM receives the corresponding VNFD ID information sent by the NFVO, such as by receiving a Create VNF Identifier request sent by the NFVO to obtain the VNFD ID included in the request. Since the above steps belong to the existing process, reference may be made to IFA007V2.3.1, which is not described in detail herein. In step 302, the VNFM obtains the virtual network function information model descriptor VNFD through the VNFD ID, and finds the corresponding VDU ID according to the Flavour ID in the VNFD, determines the VDU to be deployed, allocates the virtual resource, loads the OS, and then generates Virtual machine VM.

The following steps are specifically described in conjunction with Table 1. Table 1 is a schematic diagram of the VNFD, including various fields, such as Flavour ID, VDU ID, service group identifier, etc., where:

The Flavour ID is mainly used to describe a network topology, which VDUs are required, the maximum and minimum number of instances of each VDU deployment, internal network connection relationships, and so on.

The VDU describes a virtual deployment unit of a specification of the VNF. The VDUs of different specifications may have different virtual machine specifications and software. A VDU instance is mapped to a VM.

The service group corresponding to the service group identifier includes one or more different services, and the service may be a container-based service or a non-container-based service, and the service within the service group is not presented to the VNFM, that is, VNFM. I don't know what specific services are included in the service group.

Table 1

If the Flavour ID received by the VNFM is Flavour_1, then in Table 1, Flavour_1 corresponds to VDU-1 and VDU-2, respectively, and the VNFM determines that the VDU types to be deployed are VDU-1 and VDU-2, if VDU-1 and VDU -2 corresponds to an instance, then the VNFM allocates the corresponding virtual resources and loads the operating system OS to generate VM1 and VM2 respectively; if VDU-1 and VDU-2 correspond to multiple instances respectively, the VNFM allocates the corresponding virtual resources and The operating system OS is loaded, and a corresponding plurality of VM1s and multiple VM2s are respectively generated.

4 is a schematic diagram of a logical structure of a VDU instance, in which a VDU instance contains or corresponds to only one service group, and the service group includes one or more services. In a VNFD, a VDU ID identifies a VDU type. One type of VDU can deploy one or more VDU instances, depending on the information carried in the VNFD. A VDU instance generates a VM and only one instance in the VM. A service in a service group.

303. The VNFM sends a service group instantiation request to the platform as a service PaaS platform, the request including a VM identity and a service group identity.

Continuing with Table 1 in step 302 as an example, the VNFM sends a first service group instantiation request to the PaaS platform, the request including the VM identity VM1, the service group identity SG-1; then the VNFM sends a second to the PaaS platform. The service group instantiates a request, the request including a VM identity VM2, a service group identity SG-2. Here, as a common general knowledge, the "identity" includes a series of commonly used identifiers such as an IP address, a name, and an ID, as long as the "target object" can be uniquely identified.

304. The PaaS platform receives the service group instantiation request, and instantiates a service included in the service group corresponding to the service group identifier in the VM.

The PaaS platform receives the first service group instantiation request sent by the VNFM, determines each service in the SG-1, and instantiates each service included in the SG-1 in the VM1. Then, the PaaS platform receives the second service sent by the VNFM. The group instantiates the request, determines each service within the SG-2, and instantiates each service included in the SG-2 within the VM2.

305. PaaS returns a service group instantiation completion response message to the VNFM.

After the PaaS completes the service group instantiation and returns the service group instantiation completion response message to the VNFM, the subsequent VNFM operates according to the existing technical process. For example, after all the VDU instantiations are completed, the virtual network connection is established, and the details are not detailed here. Said. See the standard standard IFA029 for details.

Since the VDU presents requirements for virtual resources, OS, service group identification, etc., the services inside the service group are not presented to the VNFM. The VNFM can analyze and know which specific services exist within the service group, and only need to send the service group identifier to the PaaS platform. Yes, thus meeting the requirements of different operators.

FIG. 5 is a flowchart of expanding an NFV service according to an embodiment of the present invention. The expansion process is similar to the NFV service instantiation process. The specific steps are as follows:

501. The VNFM receives the VNF expansion request message.

502. The VNFM determines the VDU to be added and the corresponding virtual resource according to the capacity expansion request message and the VNFD, allocates the corresponding virtual resource, and loads the OS to complete the startup of the virtual machine.

The capacity expansion mentioned here refers to the expansion of the VM and the expansion of the VM by the VNFM. At this time, the VNFM combines the VNFD, the existing instance information, and the expansion information in the request to determine the VDU instance to be added and the corresponding virtual Resource requirements, and complete the corresponding resource allocation and OS loading to complete the virtual machine startup.

503. The VNFM determines the service group identifier in each VDU, and initiates an instantiation request of the service group in each VM to the PaaS platform, and requests to carry the VM identifier and the corresponding service group identifier.

If multiple VDUs need to be added in step 502, the VNFM initiates an instantiation request for the service group within the VM to the PaaS platform, similar to step 303.

504. The PaaS platform determines the service that needs to be instantiated according to the service group identifier, and completes the instantiation operation of each service in the corresponding VM.

505. The PaaS platform returns a service group instantiation completion response message to the VNFM.

FIG. 6 is a flowchart of a NFV service shrinkage according to an embodiment of the present invention. The shrink process is similar to the NFV service instantiation process. The specific steps are as follows:

601. The VNFM receives the VNF contraction request message.

602. The VNFM determines the VDU to be reduced and determines the corresponding VM according to the shrink request message and the VNFD.

603. The VNFM determines the service group identifier in each VDU, and initiates an instantiation request of each service group in the terminating VM to the PaaS platform, where the request carries the VM identifier and the service group identifier.

604. The PaaS platform terminates the services included in the corresponding service group in the VM according to the VM identifier and the service group identifier.

In step 603, the instantiation request may only carry the VM identifier and does not carry the service group identifier. In step 604, the PaaS platform may find the corresponding VM according to the VM identifier, and then determine which service groups in the VM are available. Service instances and then terminate those service instances.

In addition, as a special case of the shrinkage, the process of terminating the VNF service is similar to that of the shrinkage. The difference is that the PaaS platform terminates the service instances in all VMs according to the VNFM's final service group request message, which will not be described in detail here.

7 is a schematic diagram of a VNF service instantiation system architecture according to an embodiment of the present invention, where the system includes a virtual network function manager VNFM and a platform as a service PaaS platform, where

Specifically, the VNF instantiation request message includes a Flavour ID, where the VNFM is used to search for a corresponding VDU ID according to the Flavour ID in the VNFD, and then generate a corresponding virtual machine VM, where the VNFD includes the VDU The service group ID corresponding to the ID.

The VNFM can be configured to perform the various method steps performed by the VNFM in the method steps described above.

FIG. 8 is a schematic diagram of a virtual network function VNF service instantiation device, the device includes:

Specifically, the VNF instantiation request message includes a Flavour ID, and the processing unit is configured to search for a corresponding VDU ID according to the Flavour ID in the VNFD, and then generate a corresponding virtual machine VM, where the VNFD includes a Indicates the service group ID corresponding to the VDU ID.

Further, the Flavour ID in the VNFD corresponds to the first VDU ID and the second VDU ID, and the first VDU ID corresponds to the first service group identifier, and the second VDU ID corresponds to the second service group identifier.

a processing unit, configured to generate a first VM according to the first VDU ID, and generate a second VM according to the second VDU ID;

a sending unit, configured to send a first service group instantiation request to the PaaS platform, where the request includes a first VM identifier, and a first service group identifier, so that the PaaS platform accesses the first service in the first VM The service included in the service group corresponding to the group identifier is instantiated; the second service group instantiation request is sent to the PaaS platform, the request includes a second VM identifier, and the second service group identifier, so that the PaaS platform is in the The service included in the service group corresponding to the second service group identifier is instantiated in the second VM.

If the receiving unit receives the VNF expansion request message;

Then, the processing unit is configured to determine, according to the expansion request message and the VNFD, that the third VDU needs to be added, generate a corresponding third VM, and determine a corresponding third service group identifier according to the third VDU ID in the VNFD;

The sending unit is configured to send a third service group instantiation request to the PaaS platform, where the request includes a third VM identifier, and a third service group identifier, so that the PaaS platform accesses the third service group in the third VM Identifies the services contained in the corresponding service group for instantiation.

If the receiving unit further receives the VNF contraction request message;

Then, the processing unit is configured to determine, according to the volume reduction request message and the VNFD, a VM that needs to be terminated;

The sending unit is configured to send a final service group request to the PaaS platform, where the request includes a VM identifier to be terminated, so that the PaaS platform terminates the service included in the service group in the VM to be terminated.

FIG. 9 is a hardware diagram of a VNF service instantiation device according to another embodiment of the present invention. The device may include: a processor, a communication interface, and a memory.

The processor 91 may include one or more processing units, which may be a central processing unit (CPU) or a network processor (NP).

The communication interface 94 is used for connection and information exchange with other communication devices, including receiving and transmitting corresponding messages; the network device 90 may further include a memory 93, and the processor 91 may be connected to the memory 93 and the communication interface 94 via a bus. The memory 93 can be used to store software programs that can be executed by the processor 91 to implement the method steps in the embodiments shown in Figures 3, 5 and 6. In addition, the memory 93 can also store various types of service data or user data, including various application examples and status data of the service in the above method steps.

Optionally, the network device 90 may further include an output device 95 and an input device 97. Output device 95 and input device 97 are coupled to processor 91. The output device 95 can be a display for displaying information, a power amplifier device for playing sound, or a printer, etc. The output device 95 can also include an output controller for providing output to a display screen, a power amplifier device, or a printer. The input device 97 may be a device such as a mouse, a keyboard, an electronic stylus or a touch panel for inputting information by the user, and the input device 97 may further include an output controller for receiving and processing from the mouse, the keyboard, the electronic Input from devices such as stylus or touch panel

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, it may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present application are generated in whole or in part. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transfer to another website site, computer, server, or data center by wire (eg, coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.). The computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media. The usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a digital versatile disc (DVD)), or a semiconductor medium (for example, a solid state disk (SSD)). )Wait.

A person skilled in the art may understand that all or part of the steps of implementing the above embodiments may be completed by hardware, or may be instructed by a program to execute related hardware, and the program may be stored in a computer readable storage medium. The storage medium mentioned may be a read only memory, a magnetic disk or an optical disk or the like.

The above description of the embodiments of the present application is not intended to limit the application, and any modifications, equivalents, improvements, etc. made within the spirit and principles of the present application are included in the scope of the present application. Inside.

Claims

A virtual network function VNF service instantiation method, comprising:

The virtual network function manager VNFM receives the virtual network function VNF instantiation request message;

The VNFM acquires a virtual network function information model descriptor VNFD, and generates a virtual machine VM according to the VNFD, wherein the VNFD includes a service group identifier;

The VNFM sends a service group instantiation request to the platform as a service PaaS platform, where the request includes a VM identifier and a service group identifier, so that the PaaS platform performs an instance of the service included in the service group corresponding to the service group identifier in the VM. Chemical.
The method according to claim 1, wherein the VNF instantiation request message includes a Flavour ID,

The step of generating, by the VNFM, the virtual machine VM according to the VNFD includes:

The VNFM searches for a corresponding VDU ID according to the Flavour ID in the VNFD, and then generates a corresponding virtual machine VM, where the VNFD includes a service group identifier corresponding to the VDU ID.
The method according to claim 2, wherein the Flavour ID in the VNFD corresponds to the first VDU ID and the second VDU ID, and the first VDU ID corresponds to the first service group identifier, and the second VDU ID corresponds to the second Service group identifier, the method specifically includes:

The VNFM searches for the corresponding first VDU ID and the second VDU ID according to the Flavour ID in the VNFD.

The VNFM generates a first VM according to the first VDU ID;

The VNFM generates a second VM according to the second VDU ID;

The VNFM sends a first service group instantiation request to the PaaS platform, the request including the first VM identifier, and the first service group identifier, so that the PaaS platform corresponds to the first service group identifier in the first VM The services included in the service group are instantiated;

The VNFM sends a second service group instantiation request to the PaaS platform, where the request includes a second VM identifier and a second service group identifier, so that the PaaS platform corresponds to the second service group identifier in the second VM. The services included in the service group are instantiated.
The method of claim 3, wherein the method further comprises:

The VNFM receives the VNF expansion request message, and determines that the third VDU needs to be added according to the expansion request message and the VNFD to generate a corresponding third VM; and determines a corresponding third service group identifier according to the third VDU ID in the VNFD;

The VNFM sends a third service group instantiation request to the PaaS platform, where the request includes a third VM identifier, and a third service group identifier, so that the PaaS platform corresponds to the third service group identifier in the third VM. The services included in the service group are instantiated.
The method according to any one of claims 1 to 4, wherein the method further comprises:

The VNFM receives the VNF contraction request message, and determines the VM that needs to be terminated according to the shrink request message and the VNFD;

The VNFM sends a final service group request to the PaaS platform, the request including the VM identifier to be terminated, so that the PaaS platform terminates the service included in the service group in the VM to be terminated.
The method according to any one of claims 1 to 4, wherein the method further comprises:

The VNFM receives the service group instantiation completion response message returned by the PaaS platform;

After all VDUs are instantiated, the VNFM establishes a virtual network connection operation.
A method according to any one of claims 1 to 4, characterized in that

Services within the service group are not presented to the VNFM.
A virtual network function VNF service instantiation device, comprising:

a receiving unit, configured to receive a virtual network function VNF instantiation request message;

a processing unit, configured to acquire a virtual network function information model descriptor VNFD, and generate a virtual machine VM according to the VNFD, where the VNFD includes a service group identifier;

a sending unit, configured to send a service group instantiation request to the platform as a service PaaS platform, where the request includes a VM identifier and a service group identifier, so that the PaaS platform includes the service group corresponding to the service group identifier in the VM The service is instantiated.
The apparatus according to claim 8, wherein the VNF instantiation request message includes a Flavour ID,

The step of generating, by the VNFM, the virtual machine VM according to the VNFD includes:

And a processing unit, configured to search for a corresponding VDU ID according to the Flavour ID in the VNFD, and then generate a corresponding virtual machine VM, where the VNFD includes a service group identifier corresponding to the VDU ID.
The device according to claim 9, wherein the Flavour ID in the VNFD corresponds to the first VDU ID and the second VDU ID, and the first VDU ID corresponds to the first service group identifier, and the second VDU ID corresponds to the second Service group ID,

a processing unit, configured to generate a first VM according to the first VDU ID, and generate a second VM according to the second VDU ID;

a sending unit, configured to send a first service group instantiation request to the PaaS platform, where the request includes a first VM identifier, and a first service group identifier, so that the PaaS platform accesses the first service in the first VM The service included in the service group corresponding to the group identifier is instantiated; the second service group instantiation request is sent to the PaaS platform, the request includes a second VM identifier, and the second service group identifier, so that the PaaS platform is in the The service included in the service group corresponding to the second service group identifier is instantiated in the second VM.
The device of claim 10 wherein:

a receiving unit, configured to receive a VNF expansion request message;

a processing unit, configured to determine, according to the expansion request message and the VNFD, that a third VDU needs to be added, generate a corresponding third VM, and determine, in the VNFD, a corresponding third service group identifier according to the third VDU ID;

a sending unit, configured to send a third service group instantiation request to the PaaS platform, where the request includes a third VM identifier, and a third service group identifier, so that the PaaS platform accesses the third service in the third VM The service contained in the service group corresponding to the group ID is instantiated.
A device according to any one of claims 8-11, wherein

a receiving unit, configured to receive a VNF contraction request message;

a processing unit, configured to determine, according to the volume reduction request message and the VNFD, a VM that needs to be terminated;

And a sending unit, configured to send a final service group request to the PaaS platform, where the request includes a VM identifier to be terminated, so that the PaaS platform terminates the service instance included in the service group in the VM to be terminated.
A virtual network function VNF service instantiation system, comprising a virtual network function manager VNFM and a platform as a service PaaS platform, wherein

The VNFM is configured to receive a virtual network function VNF instantiation request message, obtain a virtual network function information model descriptor VNFD, and generate a virtual machine VM according to the VNFD, wherein the VNFD includes a service group identifier, and sends a service to the platform as a service PaaS platform. The group instantiates the request, the request including the VM identifier and the service group identifier;

The PaaS platform is configured to receive a service group instantiation request, and instantiate, in the VM, a service included in the service group corresponding to the service group identifier.
The system according to claim 13, wherein the VNF instantiation request message includes a Flavour ID, and the VNFM generates the virtual machine VM according to the VNFD, including:

The VNFM is configured to search for a corresponding VDU ID according to the Flavour ID in the VNFD, and then generate a corresponding virtual machine VM, where the VNFD includes a service group identifier corresponding to the VDU ID.
The system according to claim 14, wherein the Flavour ID corresponds to the first VDU ID and the second VDU ID, and the first VDU ID corresponds to the first service group identifier, and the second VDU ID corresponds to the second service group identifier. ,

The VNFM is configured to generate a first VM according to the first VDU ID, and generate a second VM according to the second VDU ID;

The VNFM is configured to send a first service group instantiation request to the PaaS platform, where the request includes a first VM identifier, and a first service group identifier;

The PaaS platform is configured to receive the first service group instantiation request, and instantiate, in the first VM, a service included in the service group corresponding to the first service group identifier;

The VNFM is configured to send a second service group instantiation request to the PaaS platform, where the request includes a second VM identifier, and a second service group identifier;

The PaaS platform is configured to receive the second service group instantiation request, and instantiate, in the second VM, a service included in the service group corresponding to the second service group identifier.
The system of claim 15 wherein:

The VNFM is configured to receive the VNF expansion request message, and determine, according to the expansion request message and the VNFD, that the third VDU needs to be added to generate a corresponding third VM, and determine, in the VNFD, the corresponding third service group according to the third VDU ID. Identification

The VNFM is configured to send a third service group instantiation request to the PaaS platform, where the request includes a third VM identifier, and a third service group identifier;

The PaaS platform is configured to receive the third service group instantiation request, and instantiate, in the third VM, a service included in the service group corresponding to the third service group identifier.
A system according to any of claims 13-16, wherein

The VNFM is configured to receive a VNF contraction request message, and the VNFD determines a VM that needs to be terminated;

The VNFM is configured to send a final service group request to the PaaS platform, where the request includes a VM identifier to be terminated;

The PaaS platform is configured to receive the terminating service group request, and terminate the service instance included in the service group in the VM to be terminated.
A virtual network function VNF service instantiation device, characterized in that the device comprises a processor and a memory;

The memory is for storing a program for performing the method of any one of claims 1-7, and storing data for implementing the method of any one of claims 1-7;

The processor is configured to execute a program stored in the memory.
A computer readable storage medium storing executable program instructions, the executable program instructions being operative to perform the steps of any of the preceding claims 1-7.