WO2017080391A1

WO2017080391A1 - Network service deployment method and device

Info

Publication number: WO2017080391A1
Application number: PCT/CN2016/104300
Authority: WO
Inventors: 楚俊生
Original assignee: 中兴通讯股份有限公司
Priority date: 2015-11-09
Filing date: 2016-11-02
Publication date: 2017-05-18
Also published as: CN106685679A

Abstract

The present application relates to the technical field of network function virtualization. Provided are a network service deployment method and device. The method comprises: receiving a network service (NS) instantiation request message, the NS instantiation request message comprising an NS descriptor NSD identifier and NS deployment specification identification information; according to the NS instantiation request message, instantiating virtual network feature (VNF) instances formed by an NS deployment specification, and instantiating virtual link (VL) instances formed by another NS deployment specification; and creating connecting points according to the NS deployment specifications, and connecting the formed VNF instances to the corresponding VL instances so as to realize network service instantiation which is performed according to the selected service deployment specifications and the included component VNF.

Description

Network service deployment method and device

Technical field

The present application relates to the field of network function virtualization technologies, for example, to a network service deployment method and apparatus.

Background technique

With the development of telecom network functions and services, the types and number of network elements deployed in the network are also increasing. The increase in the number and number of network elements has also brought many problems, such as the variety of hardware platforms, complex maintenance; hardware can not be shared, waste of resources; new services require new hardware platform support, increased business time to market (TTM, Time To Market) and so on.

In recent years, cloud computing technology has developed rapidly. Cloud computing supports heterogeneous resources and dynamic expansion, emphasizes resource sharing and on-demand allocation. Cloud computing technology can effectively reduce construction and operation and maintenance costs. Cloud computing hardware platforms generally use general-purpose or customized servers, with small hardware differences, full resource sharing, and reduced equipment procurement costs (CAPEX, CAPital Expenditure); centralized construction, deployment, and maintenance of hardware equipment, reducing operation and maintenance management costs ( OPEX, OPerating Expense); virtualization technology realizes decoupling between software and hardware, allocates resources on demand, improves resource utilization, and dynamically adjusts resources according to service load to meet network function business processing capabilities. At the same time, the virtualization technology enables flexible allocation of resources, automatic distribution of images, and improved service deployment efficiency.

Network Function Virtualization (NFV) technology provides network capabilities on high-capacity servers, high-capacity storage, and high-capacity switching devices based on industry standards to replace dedicated hardware from traditional telecom equipment manufacturers. device. The advantage of this is that on the one hand, standard-based IT (Internet Technology) equipment is low-cost, which can save operators huge investment costs; on the other hand, it provides an open API (Application Programming Interface). Interface) can also help operators to open more telecommunications basic network capabilities, improve return on investment (RIO, return on investment); unified resource scheduling, flexible allocation of resources and deployment of networks to ensure service quality and improve resource utilization efficiency; The deployment enables fast and flexible adjustments to meet system dynamics, real-time capacity expansion and capacity reduction requirements.

When telecom operators adopt IT technologies such as virtualization and cloud computing to realize network function virtualization, It is also desirable to provide a quick way to speed up the deployment of services, such as using Network Service Descriptor (NSD) to describe the composition of network services, such as virtual network features (VNF, Virtual Network Feature), network topology, Information about dependencies between VNFs, link requirements between VNFs, auto-scaling strategies, monitoring parameters, and network service deployment specifications. The network service deployment specification describes the specific deployment requirements of the network service, such as supporting different requirements of users in terms of service capacity and processing capability. Different network service deployment specifications are in the network topology, the number of instantiated network elements, and the QoS of the virtual link. (Quality of Service) requirements are different.

Figure 1 illustrates a NFV architecture framework diagram. The model diagram includes the operation support system/business support system (OSS/BSS), which provides management functions support for operators, including network services (NS, Network service) and virtual network functions (VNF). Registration, NS and VNF lifecycle management, performance and error handling, policy management, etc.; Element Management System (EMS), responsible for application-related errors, configuration, billing running on the VNF FCAPS (Fault Configuration Accounting Performance and Security) management, performance and security; virtual network function 103 (VNF), network function using virtual computing, virtual storage and virtual network resource deployment provided by infrastructure layer; network function virtualization The infrastructure layer 104 (NFVI, NFVI) is responsible for providing infrastructure resources such as virtual computing, virtual storage, and virtual network for the deployment of NS instances and VNF instances; Network Functions Virtualisation Orchestration (NFVO) 105, Responsible for NS and VNF registration, service and resource scheduling , NS and VNF instance lifetime management, etc.; Virtual Network Function Manager 106 (VNFM, Network Functions Virtualisation Management), responsible for VNF instantiation and related lifecycle management, and application-independent configuration, ie virtual resources Configuration; virtual infrastructure manager 107 (VIM, Virtualised Infrastructure Manager), responsible for the virtual computing of the operator's infrastructure domain, virtual storage and network resources control and management, and the storage and management of image files during VNF package registration . The network service, VNF and infrastructure description 108, is responsible for the description information record when the network service is registered, the description information record when the VNF package is registered, the information record of the network service and the VNF instantiation, and the NFVI resource capacity information record.

FIG. 2 is a structural diagram of a Network Service Descriptor (NSD). The NSD 201 is a configuration template that describes the configuration and operation behavior of the network service, and is configured to register, instantiate, and manage the lifetime of the network service instance. In the structure diagram, the NSD includes an NSD-related attribute information such as an NSD identifier, a device vendor, and a version 202; the virtual network function descriptor 203 (VNFD, VNF Descriptor) is configured to describe a virtual network function included in the network service. Virtual network function The VNF Forwarding Graph Descriptor (VNFFGD) is configured to describe the network topology included in the network service, and the forwarding map further includes information such as a VNF, a virtual link, and a network forwarding path. The virtual link description 205 (VLD, Visual LeakDetector), which forms part of the network service, is configured as a network connection between the VNFs; a dependency relationship 206 between the VNFs, describing the dependencies between the VNFs, configured to control the VNF instances when the network services are instantiated The order of instantiation; the service deployment specification 207 is configured to describe the VNF requirements when deploying network services that specify performance requirements such as capacity and processing power. The service deployment specification includes the constructed VNF 220, and each constituent VNF further includes a VNF. Information such as deployment specification 230, redundancy mode 231, affinity 232, and VNF instance number 233; connection point 208 is configured to describe the external interface information of the network service.

Figure 3 illustrates a virtual network function descriptor (VNFD) structure diagram. VNFD 301 is a template that describes virtual network function (VNF) configuration and operational behavior, configured as VNF registration, instantiation, and lifetime management of VNF instances. In the structure diagram, the VNFD includes the VNFD identifier, the device vendor, and the version 302 and other VNFD-related attribute information; the virtual data unit (VDU) 303 is configured to describe the component included in the VNF, that is, the virtual machine resource configuration information. A description template; a virtual link description (VLD) 304, which forms part of the VNF, is configured to describe virtual network connections within the VNF; a dependency 305 between the VDUs, describing the dependencies between the VDUs, configured to control VNF instantiation The VNF deployment specification 306 is configured to describe performance requirements such as deployment of specified capacity and processing capability. The VNF deployment specification includes the constructed VDU information 320, and the constructed VDU also includes the number of VM instances. 321, VM-specific connection point information VNFC 232, etc.; Connection Point (CP) 307, configured to describe the external interface exposed by the VNF to connect to the external virtual network.

Figure 4 illustrates a network diagram of instantiating NS by NSD and its deployment specifications. NSD 401 describes template information for the configuration and operational behavior of certain network services. In this NSD information structure, the NSD includes three different VNFD information 402, namely VNFD4201, VNFD4202, and VNFD4203; the service deployment specification included in the NSD also includes four different deployment specifications, namely, service deployment specification 01 (411), service. Deployment specification 02 (412), service deployment specification 03 (413); each service deployment specification includes the constructed VNF information, such as service deployment specification 01 (411), including the number of instances of VNF 4111, VNF 4112, and VNF 4113 being 1, service The number of instances of the deployment specification 02 including VNF4121, VNF4122, and VNF4123 is 2. The number of instances of the service deployment specification 03 including VNF4131, VNF4132, and VNF4133 is 3. 421 to 423 are respectively instantiated according to the three service deployment specifications corresponding to the NSD. The network topology diagram of the NS can be seen from the network topology diagram. The VNF network side is not specified because of the service deployment specification. Information, so all VNF instances will be connected to the same network plane.

In the network function virtualization environment, the deployment specifications of network services are the configuration requirements for resources, network topology, and links required to describe network service instances with various performance requirements such as capacity and processing capabilities; networks with different deployment specifications. When the service is deployed, the same VNFD is required to instantiate multiple VNF instances; these VNF instances need to be connected to different network planes according to the network service internal network bandwidth, network planning, and service application requirements. Currently, in the description of the VNF deployment specification, the description of each VNF instance that can connect different network planes after instantiating multiple VNF instances is lacking.

Summary of the invention

In order to implement a network service deployment, the VNF connects multiple network planes, and provides a network service deployment method and apparatus.

The technical solution adopted by the embodiment of the present invention is as follows:

A network service deployment method includes:

Receiving an instantiated network service NS request message, where the instantiated NS request message includes an NS descriptor NSD identifier and NS deployment specification identifier information;

Instantiating a virtual network function VNF instance formed by the NS deployment specification and instantiating a virtual network VL instance formed by the NS deployment specification according to the instantiated NS request message;

A connection point is created according to the NS deployment specification and the constructed VNF instance is connected to the corresponding VL instance.

The NS deployment specification corresponding to the NS deployment specification identifier information may include the configured VNF description information and the constructed virtual network VL description information.

The instantiating the NS request message according to the virtualized network function VNF instance and the virtual network VL instance formed by the NS deployment specification may include:

The VNF instance and the constructed VL instance are instantiated according to the constructed VNF description information and the constructed VL description information.

The constructed VNF description information may include the constructed access point information.

Creating a connection point according to the NS deployment specification and connecting the configured VNF instance to the corresponding VL instance may include:

A connection point is created according to the constructed access point information and the constructed VNF instance is sent to the corresponding VL instance.

The configured VNF description information may include one or more of the following: a VNF descriptor VNFD identifier, a VNF deployment specification identifier, a number of VNF instances formed, and access point information associated with the constructed VNF instance.

The VNFD may describe one or more VNF deployment specifications and configuration description information associated with the VNF deployment specification, where the VNF deployment specification may include configuration description information of one or more deployment specifications, the access point information. A set of connection point information in which the constructed VNF instance is connected to the external VL can be described.

A network service deployment device includes:

a receiving module, configured to receive an instantiated network service NS request message, where the instantiated NS request message includes an NS descriptor NSD identifier and NS deployment specification identifier information;

a requesting module, configured to instantiate a virtual network function VNF instance formed by the NS deployment specification according to the instantiated NS request message, and instantiate a virtual network VL instance formed by the NS deployment specification;

The connection module is configured to create a connection point according to the NS deployment specification and connect the constructed VNF instance to the corresponding VL instance.

The requesting module, according to the instantiating the NS request message, instantiating the virtual network function VNF instance formed by the NS deployment specification and instantiating the virtual network VL instance formed by the NS deployment specification, may include:

The VNF description information and the constructed virtual network VL description information included in the NS deployment specification corresponding to the NS deployment specification identifier information are requested to be instantiated by the VNF instance and the instantiated VL instance.

The connecting module creates a connection point according to the NS deployment specification, and connects the configured VNF instance to the corresponding VL instance, which may include:

Creating a connection point according to the constructed access point information in the constructed VNF description information and connecting the constructed VNF instance to the corresponding VL instance.

A non-transitory computer readable storage medium storing computer executable instructions, the computer The executable instructions are set to perform the above method.

An electronic device comprising:

At least one processor;

a memory communicatively coupled to the at least one processor; wherein

The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to cause the at least one processor to perform the method described above.

Compared with the related art, the present invention has the following beneficial effects:

When the network service is deployed, the solution provided by the embodiment of the present invention implements the instantiation of the network service according to the selected service deployment specification and the included VNF. For each VNF instance that is configured, the multi-network plane selection configuration function is provided.

BRIEF abstract

1 is a schematic diagram of a related art network function virtualization framework;

2 is a schematic structural diagram of a related art network service descriptor (NSD);

3 is a schematic structural diagram of a related art virtual network function descriptor (VNFD);

4 is a network diagram of a related art instantiating an NS according to an NSD and its deployment specifications;

FIG. 5 is a flowchart of a network service deployment method according to an embodiment of the present invention; FIG.

FIG. 6 is a schematic structural diagram of a network service deployment apparatus according to an embodiment of the present invention; FIG.

7 is a flowchart of implementing a network service deployment connection multi-network plane according to an embodiment of the present invention;

8 is a plan view of an extended NSD of an embodiment of the present invention to support VNF connection to multiple virtual networks;

9 is a plan view showing an extended VNFD to support VNF connection to multiple virtual networks according to an embodiment of the present invention;

10 is a plan view of a VNF connected to a multi-virtual network described in a network deployment specification according to an embodiment of the present invention;

11 is a VNFD extended information description diagram of a network topology in which a VNF is connected to a multi-virtual network plane according to a network deployment specification according to an embodiment of the present invention;

12 is a NSD extension information description diagram of a network topology in which a VNF is connected to a multi-virtual network plane according to a network deployment specification according to an embodiment of the present invention;

FIG. 13 is a schematic structural diagram of an electronic device according to an embodiment of the present invention.

Embodiments of the invention

In order to make the technical solutions and the beneficial effects of the present invention more clear, the embodiments of the present invention will be described below with reference to the accompanying drawings. The features in the embodiments and the embodiments in the present application may be arbitrarily combined with each other without conflict.

As shown in FIG. 5, an embodiment of the present invention provides a network service deployment method, including:

The NS deployment specification corresponding to the NS deployment specification identifier information includes the configured VNF description information and the constructed virtual network VL description information.

Instantiating the virtual network function VNF instance formed by the NS deployment specification according to the instantiated NS request message and instantiating the virtual network VL instance formed by the NS deployment specification includes:

The VNF description information that is configured includes the configured access point information.

Creating a connection point according to the NS deployment specification and connecting the configured VNF instance to the corresponding VL instance includes:

The constructed VNF description information includes one or more of the following: VNF descriptor VNFD The identifier, the VNF deployment specification identifier, the number of VNF instances formed, and the access point information associated with the constructed VNF instance.

The VNFD describes one or more VNF deployment specifications and configuration description information associated with the VNF deployment specification, where the VNF deployment specification includes configuration description information of one or more deployment specifications, and the access point information description The VNF instance constructed is connected to a set of connection point information of the external VL.

As shown in FIG. 6, the embodiment of the present invention provides a network service deployment apparatus, including:

The request module is configured to:

The connection module is configured to:

Example 1

Figure 7 illustrates the steps to implement the network service deployment specification. The implementation steps include:

501. Add a Connection Point Group (CPG) information describing a network plane in a virtual network function descriptor (VNFD), and each CPG may be configured to describe network interface information corresponding to a VNF instance connected to an external network plane.

502. Set a corresponding CPG for each VNF instance in the component VNF included in the network service deployment specification.

503, Network Function Virtualization Orchestrator (NFVO) root when network service instantiation and elastic scaling According to the CPG information corresponding to the VNF instance in the deployment specification, it is determined whether to increase the network plane and connect the corresponding VNF to the newly added network plane.

Example 2

Figure 8 illustrates an extended NSD to support VNF connections to multiple virtual network planes. The Network Service Descriptor (NSD) 601 refers to the 201 Network Service Descriptor NSD of FIG. 2; the NSD includes an identifier of the NSD, a device vendor and version 602, a VNF Descriptor (VNFD) 603, a Virtual Network Function Forwarding Map Description (VNFFGD) 604, The virtual link description (VLD) 605, the dependency relationship 606 between the VNFs, refer to the description of 202-206 of FIG. 2; the service deployment specification 607 is configured to describe the network service for deploying performance requirements such as specified capacity and processing capability. The VNF requirements include a VNF 620 and a virtual link VL621. Each VNF 620 includes a VNF deployment specification 630, an instance number 631 constituting the VNF, and a corresponding composition of each instance constituting the VNF. Information such as CPG 632; connection point 608 is configured to describe the external interface information of the network service.

Example 3

Figure 9 illustrates an extended VNFD to support VNF connections to multiple virtual network planes. The VNFD 701 refers to the 301 Virtual Network Function Descriptor VNFD of FIG. In the structure diagram, the VNFD includes the identifier of the VNFD, the device vendor and version 702, the virtual data unit (VDU) 703, the virtual link description (VLD) 304, the dependency relationship 705 between the VDUs, and the VNF deployment specification 706. Description of 302 to 306 of 3; The connection point group CPG information 708 is configured to describe CPG information connected to the external VL that may be selected by the VNF instance selected in a certain NS deployment specification.

Example 4

Figure 10 illustrates the VNF connection described by the network deployment specification to the multiple virtual network plane.

The VNFD list and related virtual network description information, such as deployment specifications, etc., included in the Network Service Descriptor (NSD) 801;

NS deployment specification 1 (811) describes the specification information of the corresponding NS. The VNF instances instantiated by VNFD01, VNFD02, and VNFD03 are respectively one, namely VNF1-1, VNF2-1, and VNF3-1, and pass through CP11 and CP12 respectively. And CP13 is connected to the same virtual network VL01;

NS deployment specification 2 (821) describes the specification information corresponding to NS: the VNF instances instantiated with VNFD01, VNFD02, and VNFD03 are respectively 2, namely VNF1-1, VNF1-2, VNF2-1, VNF2-2, VNF3- 1, VNF3-2, and through CP11, CP12, CP13, CP14, CP15 and The CP16 is connected to the same virtual network VL01;

NS deployment specification 3 (822) describes the specification information corresponding to NS: the VNF instances instantiated with VNFD01, VNFD02, and VNFD03 are respectively 2, namely VNF1-1, VNF1-2, VNF2-1, VNF2-2, VNF3- 1. VNF3-2, in which VNF1-1, VNF2-1, and VNF3-1 are connected to the virtual network VL01 through CP11, CP12, and CP13, respectively, and VNF1-2, VNF2-2, and VNF3-2 are respectively connected through CP21, CP22, and CP23. To the virtual network VL02;

NS deployment specification 4 (823) describes the specification information corresponding to NS: the VNF instances instantiated with VNFD01, VNFD02, and VNFD03 are respectively 2, namely VNF1-1, VNF1-2, VNF2-1, VNF2-2, VNF3- 1. VNF3-2, wherein VNF1-1, VNF2-1, and VNF3-1 are connected to the virtual network VL01 through CP11, CP12, and CP13, respectively, and VNF1-2 and VNF2-2 are connected to the virtual network VL02 through CP21 and CP22, respectively. VNF3-2 is configured with 2 connection points, connected to virtual network VL01 through CP14, and connected to virtual network VL02 through CP23;

NS deployment specification 5 (831) describes the specification information of the corresponding NS: the VNF instances instantiated by VNFD01, VNFD02 and VNFD03 are respectively three, namely VNF1-1, VNF1-2, VNF1-3, VNF2-1, VNF2- 2. VNF2-3, VNF3-1, VNF3-2, VNF3-3, wherein VNF1-1, VNF1-2, VNF2-1, and VNF2-2 are connected to the virtual network VL01 through CP11, CP16, CP12, and CP17, respectively. VNF1-3 and VNF2-3 are connected to virtual network VL02 through CP21 and CP23 respectively. VNF3-2 and VNF3-3 are connected to virtual network VL03 through CP32 and CP33 respectively. VNF3-1 is configured with 3 connection points through CP18. Connected to the virtual network VL01, connected to the virtual network VL02 through the CP24, connected to the virtual network VL03 through the CP31;

Example 5

Figure 11 illustrates the implementation of the network topology of Figure 10, VNFD extended information.

Extended VNFD01 (901) increases the connection point group CPG information. According to the embodiment of Fig. 10, the CPG information of VNFD01 needs to be increased:

CPG11 (CP11->VL01) // describes the connection point CP11 connected to the virtual network VL01;

CPG12 (CP14->VL01) // describes the connection point CP14 connected to the virtual network VL01;

CPG13 (CP16->VL01) // describes the connection point CP16 connected to the virtual network VL01;

CPG14 (CP21->VL02) // describes the connection point CP21 connected to the virtual network VL02;

Extended VNFD02 (902) adds CPG information. According to the embodiment of Fig. 10, the CPG of VNFD02 Information needs to be increased:

CPG21 (CP12->VL01) // describes the connection point CP12 connected to the virtual network VL01;

CPG22 (CP15->VL01) // describes the connection point CP15 connected to the virtual network VL01;

CPG23 (CP17->VL01) // describes the connection point CP17 connected to the virtual network VL01;

CPG24 (CP22->VL02) // describes the connection point CP22 connected to the virtual network VL02;

CPG25 (CP23->VL02) // describes the connection point CP23 connected to the virtual network VL02;

Extended VNFD03 (903) adds CPG information. According to the embodiment of Fig. 8, the CPG information of VNFD03 needs to be increased:

CPG31 (CP13->VL01) // describes the connection point CP13 connected to the virtual network VL01;

CPG32 (CP16->VL01) // describes the connection point CP13 connected to the virtual network VL01;

CPG33 (CP23->VL02) // describes the connection point CP23 connected to the virtual network VL02;

CPG34 (CP31->VL03) // describes the connection point CP31 connected to the virtual network VL03;

CPG35 (CP32->VL03) // describes the connection point CP32 connected to the virtual network VL03;

CPG36 (CP33->VL03) // describes the connection point CP33 connected to the virtual network VL03;

CPG37 (CP14->VL01, CP23->VL02) // Describe that the connection point CP14 is connected to the virtual network VL01, and the connection point CP23 is connected to the virtual network VL02;

CPG38 (CP18->VL01, CP24->VL02, CP31-VL03) // The connection point CP18 is connected to the virtual network VL01, the connection point CP24 is connected to the virtual network VL02, and the connection point CP31 is connected to the virtual network VL03.

Example 6

Figure 12 illustrates the implementation of the network topology of Figure 10, NSD extension information.

The Extended Network Service Descriptor (NSD) contains the virtual link VL (1001) description information:

VL01 (CP11, CP12, CP13, CP14, CP15, CP16, CP17, CP18)

VL02 (CP21, CP22, CP23)

VL03 (CP31, CP32, CP33, CP34, CP35, CP36)

The deployment specification for Extended Network Service Descriptor (NSD) contains the constructed virtual link VL and composition Description of the VNF:

Service Deployment Specification 1:

The constructed VNF:

(VNFD01, 1, CPG11); / / According to VNF01 instantiated a VNF instance, the external network connection uses CPG11;

(VNFD02, 1, CPG21);

(VNFD03, 1, CPG31)

The VL:// network service of this specification consists of 1 virtual network VL01

VL01

Service Deployment Specification 2:

The constructed VNF:

(VNFD01, 2, CPG11, CPG12); / / According to VNF01 instantiate two VNF instances, the two VNF instances use CPG11 and CPG12 for external network connection respectively;

(VNFD02, 2, CPG21, CPG22);

(VNFD03, 2, CPG31, CPG32)

The VL:// network service of this specification consists of 2 virtual networks VL01 and VL02

VL01, VL02

Service Deployment Specification 3:

The constructed VNF:

(VNFD01, 2, CPG11, CPG14); / / According to VNF01 instantiate two VNF instances, the two VNF instances use CPG11 and CPG14 for external network connection respectively;

(VNFD02, 2, CPG21, CPG24);

(VNFD03, 2, CPG31, CPG33)

VL01, VL02

Service Deployment Specification 4:

The constructed VNF:

(VNFD02, 2, CPG21, CPG24);

(VNFD03, 2, CPG31, CPG37) // CPG37 contains CP14 and CP23, indicating that the corresponding VNF instance can be connected to the virtual networks VL01 and VL02;

VL01, VL02

Service Deployment Specification 5:

The constructed VNF:

(VNFD01, 3, CPG11, CPG13, CPG14); / / According to VNF01 instantiation of three VNF instances, the three VNF instances of the external network connection using CPG11, CPG13 and CPG14;

(VNFD02, 3, CPG21, CPG23, CPG25);

(VNFD03, 3, CPG31, CPG32, CPG38) // CPG38 contains CP18, CP24 and CP31, indicating that the corresponding VNF instance can be connected to the virtual networks VL01, VL02 and VL03;

The VL:// network service of this specification consists of 3 virtual networks VL01, VL02 and VL03

VL01, VL02, VL03.

The embodiment of the present invention further provides a non-transitory computer readable storage medium storing computer executable instructions, the computer executable instructions being configured to perform the method in any of the above embodiments.

The embodiment of the invention further provides a schematic structural diagram of an electronic device. Referring to FIG. 13, the electronic device includes:

At least one processor 130, one processor 130 is taken as an example in FIG. 13; and a memory (memory) 131 may also include a communication interface 132 and a bus 133. The processor 130, the communication interface 132, and the memory 131 can complete communication with each other through the bus 133. Communication interface 132 can be used for information transfer. The processor 130 can invoke logic instructions in the memory 131 to perform the methods of the above-described embodiments.

In addition, the logic instructions in the memory 131 described above may be implemented in the form of a software functional unit and sold or used as a stand-alone product, and may be stored in a computer readable storage medium.

The memory 131 is a computer readable storage medium, and can be used to store a software program, a computer executable program, and a program instruction/module corresponding to the method in the embodiment of the present invention. The processor 130 executes the function application and the data processing by running the software program, the instruction and the module stored in the memory 131, that is, the network service deployment method in the above method embodiment.

The memory 131 may include a storage program area and an storage data area, wherein the storage program area may store an operating system, an application required for at least one function; the storage data area may store data created according to usage of the terminal device, and the like. Further, the memory 131 may include a high speed random access memory, and may also include a nonvolatile memory.

The technical solution of the embodiment of the present invention may be embodied in the form of a software product stored in a storage medium, including one or more instructions for causing a computer device (which may be a personal computer, a server, or a network) The device or the like) performs all or part of the steps of the method described in the embodiments of the present invention. The foregoing storage medium may be a non-transitory storage medium, including: a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and the like. A medium that can store program code, or a transitory storage medium.

The embodiments disclosed in the present invention are as described above, but the contents thereof are only for the purpose of facilitating understanding of the technical solutions of the present invention, and are not intended to limit the present invention. Any modifications and changes in the form and details of the embodiments may be made by those skilled in the art without departing from the scope of the present invention. It is subject to the scope defined by the appended claims.

Industrial applicability

The invention realizes the instantiation of the network service according to the selected service deployment specification and the included VNF, and provides a multi-network plane selection configuration function for each VNF instance.

Claims

A network service deployment method includes:

Receiving an instantiated network service NS request message, where the instantiated NS request message includes an NS descriptor NSD identifier and NS deployment specification identifier information;

Instantiating a virtual network function VNF instance formed by the NS deployment specification and instantiating a virtual network VL instance formed by the NS deployment specification according to the instantiated NS request message;

A connection point is created according to the NS deployment specification and the constructed VNF instance is connected to the corresponding VL instance.
The method of claim 1, wherein the NS deployment specification corresponding to the NS deployment specification identifier information comprises the constructed VNF description information and the constructed virtual network VL description information.
The method of claim 2, wherein: instantiating the virtual network function VNF instance formed by the NS deployment specification according to the instantiated NS request message and instantiating the virtual network VL instance formed by the NS deployment specification comprises:

The VNF instance and the constructed VL instance are instantiated according to the constructed VNF description information and the constructed VL description information.
The method of claim 2 or 3, wherein the constructed VNF description information includes the constructed access point information.
The method of claim 4, wherein creating a connection point according to the NS deployment specification and connecting the constructed VNF instance to the corresponding VL instance comprises:

A connection point is created according to the constructed access point information and the constructed VNF instance is sent to the corresponding VL instance.
The method of claim 2 or 3 wherein:

The VNF description information includes one or more of the following: a VNF descriptor VNFD identifier, a VNF deployment specification identifier, a number of VNF instances formed, and access point information associated with the constructed VNF instance.
The method of claim 6 wherein

The VNFD describes one or more VNF deployment specifications and configuration description information associated with the VNF deployment specification, where the VNF deployment specification includes configuration description information of one or more deployment specifications. The access point information describes a set of connection point information in which the constructed VNF instance is connected to the external VL.
A network service deployment device includes:

a receiving module, configured to receive an instantiated network service NS request message, where the instantiated NS request message includes an NS descriptor NSD identifier and NS deployment specification identifier information;

a requesting module, configured to instantiate a virtual network function VNF instance formed by the NS deployment specification according to the instantiated NS request message, and instantiate a virtual network VL instance formed by the NS deployment specification;

The connection module is configured to create a connection point according to the NS deployment specification and connect the constructed VNF instance to the corresponding VL instance.
The apparatus according to claim 8, wherein: said requesting module instantiates a virtual network function VNF instance formed by said NS deployment specification according to said instantiated NS request message and instantiates a virtual network VL formed by said NS deployment specification When configured, it is configured to:

The VNF description information and the constructed virtual network VL description information included in the NS deployment specification corresponding to the NS deployment specification identifier information are requested to be instantiated by the VNF instance and the instantiated VL instance.
The apparatus of claim 9, wherein when the connection module creates a connection point according to the NS deployment specification and connects the configured VNF instance to the corresponding VL instance, the connection module is configured to:

Creating a connection point according to the constructed access point information in the constructed VNF description information and connecting the constructed VNF instance to the corresponding VL instance.
A non-transitory computer readable storage medium storing computer executable instructions arranged to perform the method of any of claims 1-7.