WO2021129868A1

WO2021129868A1 - Network service instantiation method and network function virtualization orchestrator

Info

Publication number: WO2021129868A1
Application number: PCT/CN2020/140046
Authority: WO
Inventors: 李世涛
Original assignee: 华为技术有限公司
Priority date: 2019-12-27
Filing date: 2020-12-28
Publication date: 2021-07-01
Also published as: CN113055211B; CN113055211A; CN115361291A

Abstract

Provided are an NS instantiation method and an NFVO apparatus. The method comprises: receiving a composite NS instantiation request, wherein the composite NS instantiation request comprises deployment position information of a nested NS needing to be instantiated; according to the deployment position information of the nested NS and nested NFVO information that supports the nested NS, determining a corresponding nested NFVO; and sending a nested NS instantiation request to the nested NFVO. In the embodiments of the present invention, by means of specifying a deployment position of a nested NS in an NS request, and in conjunction with the range of nested NSs managed by NFVO-Ns, an appropriate NFVO-N is selected to execute a deployment request of a corresponding nested NS.

Description

Method for instantiating network service and network function virtualization orchestrator

This application claims the priority of a Chinese patent application filed with the State Intellectual Property Office of China, the application number is 201911378927.8, and the invention title is "Network Service Instantiation Method and Network Function Virtualization Orchestrator" on December 27, 2019, all of which The content is incorporated in this application by reference.

Technical field

This application relates to the field of communications, and in particular to a method for instantiating a network service (NS, network service) and a network function virtualization orchestrator (NFVO, network function virtualization orchestrator) device.

Background technique

NFV (Network Function Virtualization), that is, network function virtualization. By using general-purpose hardware equipment and virtualization technology to carry the functions of the special equipment in the traditional network, the expensive cost caused by the deployment of special equipment is reduced. Through the decoupling of software and hardware, network device functions no longer depend on dedicated hardware. At the same time, using the characteristics of cloud computing, resources can be fully and flexibly shared, rapid development and deployment of new services are realized, and automatic deployment, elastic scaling, fault isolation, and self-healing are carried out based on actual business needs. The party that can receive the virtualization request and perform virtualization processing on the corresponding service according to the request is generally called the virtualization service provider, and the party that initiates the virtualization request is generally called the service requester.

The virtualized network service in NFV is called an NS (Network Service), such as an IP Multimedia Subsystem (IMS) network service, or a next-generation mobile core network EPC (Evolved Packet Core) service. One NS may also include several virtualized network function modules (VNFs). When an NS is deployed in virtualization, the service requester first needs to submit the description of the service to the service provider, which is called NSD (Network Service Descriptor), also known as NS deployment template. NSD mainly describes the topological structure of the service And the description information (VNFD, VNF Descriptor) of each VNF included, where the virtual connection information VLD (Virtual Link Descriptor) is used in the topology information to describe the connection between the VNFs. VNFD is the description information of a VNF, also called the deployment template of VNF. It contains information such as virtual deployment unit VDU (Virtualisation Deployment Unit), connection point CP (Connection Point), virtual connection VL (Virtual Link), among which VDU can Represents a virtual machine with application software installed. The description of the VDU will contain a description of the requirements for all virtual resources of the virtual machine. CP represents the connection information on the virtual machine. For example, it can be virtual network card information, which can be an IP address or Represented by MAC address, VL is a virtual connection connecting multiple VDUs within a VNF, which can be represented by information such as connection type and bandwidth.

Summary of the invention

To solve the above-mentioned technical problems in the prior art, embodiments of the present application provide a method for instantiating a composite NS, an NFVO device, and a system.

The embodiment of the present application provides a method for instantiating NS, the method is applied to the composite network function virtualization orchestrator NFVO, and the method includes:

Receiving a request to instantiate a composite NS, where the instant composite NS request includes deployment location information of the nested NS that needs to be instantiated;

Determine the corresponding nested NFVO according to the deployment location information of the nested NS and the nested NFVO information supporting the nested NS;

Send a request to instantiate the nested NS to the nested NFVO.

The nested NFVO information supporting the nested NS includes: nested NFVO information capable of processing the network service descriptor NSD of the nested NS.

Before the receiving the instantiation composite NS request, the method further includes:

Receiving registration information of the nested NFVO, where the registration information includes deployment location information of the nested NS managed by the nested NFVO;

The network service descriptor NSD information of the nested NS of the composite NS is received, and the NSD includes the nested NFVO information capable of processing the NSD.

The nested NFVO information supporting the nested NS includes: nested NSD information supported by the nested NFVO.

Receive registration information of the nested NFVO, where the registration information includes the deployment location information of the nested NS managed by the nested NFVO and the nested NSD information supported by the nested NFVO.

The embodiment of the present application also provides a composite network function virtualization orchestrator NFVO, which includes:

The receiving unit is configured to receive a request to instantiate a composite NS, where the instant composite NS request includes deployment location information of the nested NS that needs to be instantiated;

A processing unit, configured to determine the corresponding nested NFVO according to the deployment location information of the nested NS and the nested NFVO information supporting the nested NS;

The sending unit is configured to send a request to instantiate a nested NS to the nested NFVO.

The embodiment of the present application also provides an NFVO system, including composite NFVO and nested NFVO,

The composite NFVO is used for,

Sending a request to instantiate the nested NS to the nested NFVO;

The nested NFVO is used to determine one or more VNFs included in the nested NS, and initiate a request to instantiate the one or more VNFs to the VNFM managed by it, so that the VNFM can instantiate each VNF by completing the instantiation of each VNF化The nested NS.

The embodiment of the present application also provides a computer-readable storage medium for storing instructions. When the instructions are executed by the processor of the computing device, the computing device realizes the requirements described in any one of claims 1 to 7. The method described.

An embodiment of the present application also provides a computing device, including a memory and a processor, the memory stores executable code, and when the processor executes the executable code, any one of claims 1 to 7 is implemented. The method described in the item.

The embodiments of the present application also provide a computer program product. The computer program product includes computer program code. When the computer program code runs on a computing device, the computing device executes the above-mentioned first aspect. Any of the methods.

The solution of the embodiment of the present invention solves the problem that NFVO-C cannot correctly select NFVO-N in the nested NS scenario in the prior art; the embodiment of the present invention specifies the deployment position of the nested NS in the NS request and combines it with NFVO -N manages the range of nested NS to select the appropriate NFVO-N to execute the deployment request of the corresponding nested NS.

Description of the drawings

The following briefly introduces the drawings needed in the description of the embodiments or the prior art.

Fig. 1 is a framework diagram of an NFV system provided by an embodiment of the application.

FIG. 2 is a schematic diagram of a module for instantiating NS in an NFVO system provided by an embodiment of the application.

FIG. 3 is a schematic flow chart of instantiating NS in an NFVO system according to an embodiment of the application.

FIG. 4 is a schematic diagram of the process of instantiating NS in another NFVO system according to an embodiment of the application.

FIG. 5 is a schematic diagram of an NFVO device module provided by an embodiment of the application.

FIG. 6 is a schematic diagram of an NFVO system module provided in Embodiment 2 of this application.

Detailed ways

The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application.

Fig. 1 is a system framework diagram of an NFV system to which an embodiment of this application is applicable. As shown in Figure 1, the NFV system 100 mainly includes the following functional entities:

NFVO102 is mainly used for life cycle management of NS, and for the allocation and scheduling of virtual resources in network functions virtualization infrastructure (NFVI, network functions virtualization infrastructure) 104. The NFVO 102 may communicate with one or more VNFM 106 to perform related operations of instantiating the NS, such as sending corresponding configuration information to the VNFM 106, and requesting the status information of one or more VNF 108 from the VNFM 106. In addition, the NFVO 102 can also communicate with a virtual infrastructure manager (VIM, virtualized infrastructure manager) 110 to perform allocation and/or reservation of various resources in the NFVI 104, and exchange resource configuration and status information.

The VNFM106 is mainly responsible for the lifecycle management of one or more VNF108, such as instantiating the VNF108, updating the VNF108, querying the VNF108, scaling the VNF108, and terminating the VNF108. The VNFM106 can communicate with the VNF108 to manage the life cycle of the VNF108 and exchange configuration information and status information with the VNF. It can be understood that the NFV system 100 may include one or more VNFMs 106, and each VNFM 106 performs life cycle management on different types of VNFs 108 respectively.

NFVI104 refers to the infrastructure of the NFV system 100, which includes hardware components, software components and their combination to establish a virtualized environment, and deploy, manage, and implement VNF108 in the virtualized environment. NFVI104 can at least include computing hardware 1041, storage hardware 1042, network hardware 1043; the virtualization layer 1044 of NFVI104 can abstract the aforementioned hardware, decouple each hardware and VNF108, and obtain corresponding virtual computing resources 1045, virtual storage resources 1046, and virtual network resources 1047, so as to provide virtual machines and other forms of virtualized containers for the VNF 108.

The VIM 110 is mainly used to control and manage the interaction between the VNF 108 and the computing hardware 1041, the storage hardware 1042, the network hardware 1043, the virtual computing resources 1045, the virtual storage resources 1046, and the virtual network resources 1047. For example, the VIM 110 can perform resource management functions, such as adding corresponding virtual resources to virtual machines or other forms of virtual containers, and collecting fault information of the NFVI 104 during system operation. In addition, the VIM 110 can communicate with the VNFM 106, such as receiving a resource allocation request from the VNFM 106, and feeding back resource configuration and status information to the VNFM 106.

VNF 108, VNF 108 includes one or more VNFs (usually multiple VNFs), which can run one or more virtual machines or other forms of virtual containers, corresponding to a set of network functions originally implemented by dedicated devices.

The equipment management system (EMS, equipment management system) 112 may be used to configure and manage the VNF 108, and initiate life cycle management operations such as the instantiation of a new VNF 108 to the VNFM 106. It can be understood that one or more EMS 112 may be included in the NFV system 100.

The operations support system (OSS, operations support system) or the business support system (BSS, business support system) 114 can support various end-to-end telecommunication services. Among them, the management functions supported by OSS can include network configuration, service provision, fault management, etc.; BSS can be used for order processing, payment, income and other related services, and supports product management, order management, revenue management, and customer management functions. It should be noted that the OSS/BSS114 can be used as the service requester to request the NFVO to instantiate the NS, and the computing device on which the OSS/BSS114 or OSS/BSS114 depends can generally be referred to as the service requester.

It can be understood that, in the NFV system 100 shown in FIG. 1, each of the aforementioned functional entities may be deployed in different computing devices, or some functional entities may be integrated into the same computing device.

As shown in Figure 2, NFVO-C is the entire network NFVO (also called composite NFVO), responsible for the management of the entire network NS and VNF. NFVO-N is the NFVO in the sub-administrative domain (also called nested NFVO), which is only responsible for the management of NS and VNF in its administrative domain. The number of NFVO-N may be one or more, and NFVO-N has a communication interface with NFVO-C. As shown in Figure 1, the composite NS_A is a large network service, which includes different VNFs and a nested network service Nested NS_1. Nested NS_1 belongs to the management category of the sub-administrative domain. The sub-administrative domain is managed by NFVO_N, including: Nested NS_1 allocates resources, manages the entire life cycle, and so on. NFVO-C is responsible for the management of the entire NS_A network. When NS_A is deployed, when operations on Nested NS_1 are involved, such as instantiation, NFVO-C requests completion from NFVO-N.

NFVO-N is a management orchestrator in an autonomous domain. An autonomous domain can have multiple different NFVO-Ns, which belong to different equipment vendors. When NFVO-C needs to deploy a nested NS (Nested NS) service, how to choose which NFVO-N in which autonomous domain to deploy the service is not mentioned in the prior art, and there is no relevant standard to define how NFVO-C It can determine in which NFVO-N to deploy the nested NS service, so as to notify the corresponding NFVO-N.

Embodiment 1 of the present application provides a method for instantiating NS, as shown in FIG. 3, the specific steps are as follows:

301. One or more nested NFVO (NFVO-N) registers their management domain information with the composite NFVO (NFVO-C), which includes the location information of the NS managed by NFVO-N and the equipment corresponding to NFVO-N Quotient information.

For a better understanding, this step and the subsequent steps are illustrated in Figure 2. Multiple NFVO-N (such as NFVO-N1, NFVO-N2 or NFVO-N3, only NFVO-N1 is shown in the figure) to NFVO-C After registration, the management domain information of NFVO-N stored on NFVO-C includes the following information:

NFVO-N1:

vendor: equipment vendor 1

Location:Location 1

NFVO-N2:

vendor: equipment vendor 2

Location:Location 1

NFVO-N3:

vendor: equipment vendor 1

Location:Location 3

Among them, Equipment Vendor 1 and Equipment Vendor 2 are equipment providers of NFVO-N1 and NFVO-N2 respectively. Location is a piece of physical location information. For example, location 1 can be: Shanghai, China, location 2 is: Beijing, China, location 3 Yes: Shenzhen, China. In addition, you can refer to the city and location codes defined in the international standards RFC 4776 and ISO 3166 to indicate specific location information.

The registration request can also be sent to the subscription mechanism. NFVO-C subscribes to the management domain information of the newly accessed NFVO-N, and NFVO-C sends a subscription request to NFVO-N, and NFVO-N replies to the notification and sends the information it manages. The address location information of NS is reported to NFVO-C.

302. OSS/BSS uploads the NSD (composite NSD) of the composite NS and the NSD (nested NSD) information of the nested NS that need to be instantiated. The nested NSD contains nfvoInfo, which can be presented in the form of a list. Indicates the ability or authorization to process the NFVO information of the nested NSD.

Referring to Figure 2, the nested NS that needs to be instantiated is Nested_NS_1, and the information contained in the nfvoInfo of the NSD is NFVO-N1 and NFVO-N3, indicating that the NFVO-N1 and NFVO-N3 of the equipment vendor 1 can manage the deployment and other life of the Nested_NS_1 Cycle management operations. Among them, different equipment vendors individually design NSDs, and different equipment vendors do not share the same NSD. For example, the NFVO-N2 of equipment vendor 2 cannot use the NSD designed by equipment vendor 1. The nfvoInfo of the NSD may also include equipment vendor information, which means that the NFVO-N of the equipment vendor can manage the deployment of the Nested_NS_1 and other life cycle management operations.

303. The OSS/BSS sends a request to NFVO-C to instantiate a composite NS, the request includes the instance identifier of the composite NS that needs to be instantiated, and the instance identifier includes the field NsLocationConstraint, which is used to indicate each of the composite NS instances The deployment location information of the nested NS.

Referring to FIG. 2, the instantiation composite NS request includes the instance identifier of the composite NS_A, and the instance identifier includes the field NsLocationConstraint, which is used to indicate the deployment location information of the nested NS (ie Nested_NS_1) in the composite NS_A instance, such as Location 1 .

If the NS to be instantiated includes multiple Nested NSs, the instance identifier includes multiple NsLocationConstraint fields, respectively indicating deployment location information of the multiple Nested NSs. At the same time, in step 302, the OSS/BSS uploads the NSD information of multiple nested NSs that need to be instantiated, and each NSD contains its own nfvoInfo, indicating that the NFVO information of the NSD can be processed. Step 302 and step 303 are in no order, and step 302 may occur after step 303.

304. NFVO-C obtains the NSD information of the corresponding composite NS according to the instance identifier contained in the instant composite NS request received in step 303 (the NSD information is uploaded by OSS/BSS in step 302), and parses the NSD information , And obtain the NSD identifiers of one or more nested NSs contained therein, so as to obtain the corresponding NSD information of each nested NS (as described in step 302 above, the NSD information of each nested NS is uploaded by OSS/BSS to NFVO-C), and obtain the NFVO information that can process the NSD according to the nfvoInfo information contained therein.

Referring to Figure 2, NFVO-C obtains the NSD information of the corresponding NS_A according to the instance ID of NS_A contained in the received instantiation composite NS request, and parses the NSD information of NS_A, and obtains the NSD ID of Nested_NS_1 contained in the NSD of NS_A , And obtain the NSD information of Nested_NS_1 according to the NSD identifier of Nested_NS_1, and obtain the NFVO information that can process the NSD according to the nfvoInfo information contained therein is NFVO-N1 and NFVO-N3.

Further, NFVO-C obtains the deployment location information of the nested NS according to the NsLocationConstraint information in the NS instantiation request in step 303, and combines it with the NFVO information of the NSD that can process the nested NS obtained in the above steps, as in step 301 The nested NFVO (NFVO-N) matches the information of the management domain registered with the composite NFVO (NFVO-C) to determine the NFVO-N that meets the requirements.

Referring to Figure 2, NFVO-C determines that Nested_NS_1 needs to be deployed in Location1 according to the NsLocationConstraint in the NS instantiation request, and then combines the registration information of NFVO-N in the first step to determine that the NFVO at Location1 has NFVO-N1 and NFVO-N2 , And according to the above obtained NFVO that can process the NSD information of Nested_NS_1 are NFVO-N1 and NFVO-N3, and NFVO-C, so as to determine that the qualified NFVO-N1 is.

305. The NFVO-C obtains Virtual Link (VL) information connected to the nested NS according to the obtained NSD information of the composite NS instance, and instantiates the VL. The specific process of instantiating the VL is in the prior art. The basic process is that NFVO-C requests the VIM managed by it to instantiate the network resources required by the VL. After the VL is instantiated, the VIM sends a request to NFVO-C. C returns the information of the VL instance.

Referring to Fig. 2, NFVO-C obtains VL_2 information connected to Nested_NS_1 according to the obtained NSD information of NS_A, and then instantiates the VL_2. There is no sequence between this step and the above steps, for example, it can be performed before steps 302-304.

306. The NFVO-C sends a request to the corresponding NFVO-N to instantiate the nested NS, which contains the instance identifier of the corresponding nested NS and the VL information connected to the nested NS.

Referring to FIG. 2, specifically, NFVO-C sends an instantiation request for Nested_NS_1 to NFVO-N1, the request includes an instance identifier of Nested_NS_1, and the request also includes connection information of VL_2 connected to Nested_NS_1.

307. The NFVO-N is to determine each VNF contained in the nested NS, select appropriate VIM access information for it, and initiate a VNF instantiation request to the VNFM it manages, including the selected VIM Access information.

Referring to Figure 2, Nested_NS_1 contains two VNFs, VNF_4 and VNF_5. NFVO-C selects suitable VIM access information for it, and initiates a VNF instantiation request to the VNFM it manages.

308. The VNFM completes the instantiation process of each VNF. After the VNFM completes the instantiation of the VNF, the NFVO-N establishes the connection between each VNF through the VL, thereby completing the instantiation of the nested NS.

Referring to Figure 2, VNFM completes the instantiation of VNF_4 and VNF_5, and NFVO-N1 connects them through VL_3, thereby completing the instantiation of Nested_NS_1.

309. After the instantiation of the nested NS is completed, NFVO-N establishes a connection between the nested NS instance and the VL according to the VL connection information in step 306. Further, NFVO-C completes the instantiation of other VNFs included in the composite NS_A, connects through VL, and then establishes a connection with the nested NS through VL, thereby completing the instantiation of the entire NS_A.

Referring to FIG. 2, specifically, NFVO-N1 establishes a connection between Nested_NS_1 and the VL_2 instance according to the connection information of VL_2 in step 306. Further, NFVO-C completes the instantiation of other parts of the composite NS_A, such as the instantiation of VNF1, VNF2, and VNF3, and internally connects to each other through VL_1, and then establishes a connection with the VL_2 instance, thereby completing the instantiation of the entire NS_A.

The instantiation of other parts of the composite NS_A by the NFVO-C may be performed before the instantiation of the Nested_NS_1 is completed, or may be performed before steps 305-306, in no particular order.

In addition, the present invention also provides another embodiment 2, as shown in FIG. 4, the specific steps are as follows:

401. One or more nested NFVO (NFVO-N) registers their management domain information with the composite NFVO (NFVO-C). The difference from Embodiment 1 is that the information includes the information of the NS managed by NFVO-N Location information and NSD information supported by NFVO-N.

For a better understanding, this step and the subsequent steps are also illustrated in Figure 2. After multiple NFVO-N (NFVO-N1, NFVO-N2, NFVO-N3) are registered with NFVO-C, they will be saved on NFVO-C. The management domain information of NFVO-N includes the following information:

NFVO-N1:

Location: Location 1

nsd: NSD-1, NSD-2, NSD-3

NFVO-N2:

Location: Location 1

nsd: NSD-4, NSD-5, NSD-6

NFVO-N3:

Location: Location 3

nsd: NSD-1, NSD-2

The registration request can also be sent to the subscription mechanism. NFVO-C subscribes to the management domain information of the newly accessed NFVO-N, and NFVO-C sends a subscription request to NFVO-N, and NFVO-N replies to the Notification, and transfers the management domain information it manages. The address location information of NS is reported to NFVO-C.

402. The OSS/BSS uploads the NSD (composite NSD) of the composite NS and the NSD (nested NSD) of the nested NS that need to be instantiated. The nested NSD may not include the nfvoInfo as described in step 302 in embodiment 1. information.

403. Same as step 303 in Example 1.

404. NFVO-C obtains the NSD information of the corresponding composite NS according to the instance identifier contained in the instant composite NS request received in step 403, parses the NSD information, and obtains the NSD of one or more nested NSs contained therein Logo.

Referring to Figure 2, NFVO-C obtains the NSD information of the corresponding NS_A according to the instance ID of NS_A contained in the received instantiation composite NS request, and parses the NSD information of NS_A, and obtains the NSD ID of Nested_NS_1 contained in the NSD of NS_A NSD-1.

Further, NFVO-C obtains the deployment location information of the nested NS according to the NsLocationConstraint information in the NS instantiation request in step 403, and manages the registration of the nested NFVO (NFVO-N) with the composite NFVO (NFVO-C) in step 401 The domain information is matched to determine the NFVO-N that meets the requirements.

Referring to Figure 2, NFVO-C determines that Nested_NS_1 needs to be deployed in Location1 according to the NsLocationConstraint in the NS instantiation request, and then combines the registration information of NFVO-N in step 401 to determine that the NFVO at Location1 has NFVO-N1 and NFVO-N2 and It is determined that the NFVOs that can process the NSD-1 information of Nested_NS_1 are NFVO-N1 and NFVO-N3, and NFVO-C is determined to meet the conditions is NFVO-N1.

405-409. Same as steps 305-309 in Example 1.

The solution of the above-mentioned embodiment of the present invention solves the problem that NFVO-C cannot correctly select NFVO-N in the nested NS scenario in the prior art; the embodiment of the present invention specifies the deployment position of the nested NS in the NS request, And combined with the range of nested NS managed by NFVO-N to select the appropriate NFVO-N to execute the deployment request of the corresponding nested NS.

In addition, the present invention also provides a composite network function virtualization orchestrator NFVO device 50, and the composite NFVO device 50 includes:

The receiving unit 501 is configured to receive a request to instantiate a composite NS, where the instant composite NS request includes deployment location information of a nested NS that needs to be instantiated;

The processing unit 502 is configured to determine the corresponding nested NFVO according to the deployment location information of the nested NS and the nested NFVO information supporting the nested NS;

The sending unit 503 is configured to send a request to instantiate a nested NS to the nested NFVO.

Before the receiving the instantiation composite NS request, the receiving unit 501 is further configured to:

The processing unit 502 is further configured to obtain the NSD of the corresponding composite NS according to the composite NS request, and obtain the virtual link VL information of the nested NS that needs to be instantiated and other NSs according to the composite NSD, and Instantiate the VL;

Establish a connection between the nested NS instance and the VL instance according to the virtual link VL information.

The above description is only a general description of the composite NFVO, and its specific execution steps and actions are the same as those performed by the NFVO-C in the foregoing

method embodiments

1 and 2, and will not be repeated here.

In addition, the present invention also provides an NFVO system 60, including a composite NFVO 601 and a nested NFVO 602,

The composite NFVO 601 is used for,

Receive an instantiated composite NS request, the instantiated composite NS request includes the deployment position of the nested NS to be instantiated

Set information;

According to the deployment location information of the nested NS and the nested NFVO information that supports the nested NS, the corresponding

Nested NFVO 602;

Send a request to instantiate the nested NS to the nested NFVO 602;

The nested NFVO 602 is used to:

One or more VNFs included in the nested NS are determined, and a request to instantiate the one or more VNFs is initiated to the VNFM managed by the VNFM, so that the VNFM instantiates the nested NS by completing the instantiation of each VNF.

The composite NFVO 601 is also used to obtain the NSD of the corresponding composite NS according to the composite NS request, and obtain the virtual link VL information of the nested NS that needs to be instantiated and other NSs according to the composite NSD, and Instantiate the VL;

Similarly, the above description is only a general description of the composite NFVO system, and its specific execution steps and actions are the same as those performed by NFVO-C and NFVO-N in the foregoing

method embodiments

1 and 2, and will not be repeated here.

An embodiment of the present application also provides a computer-readable storage medium for storing instructions. When the instructions are executed by a processor of a computing device, the computing device realizes the example provided in any one of the embodiments of the present application. The method of NS.

An embodiment of the application provides a computer program product. The computer program product includes computer program code. When the computer program code runs on a computing device, the computing device executes any one of the embodiments provided in this application. The method of instantiating NS.

An embodiment of the present application provides a computing device, including a memory and a processor, the memory stores executable code, and when the processor executes the executable code, it implements the method provided in any one of the embodiments of the present application. Method to instantiate NS.

The embodiment of the present application also provides a chip system, which includes a processor, which is used to implement the function of the NFVO described in any embodiment of the present application, for example, to receive or process the function of any one of the embodiments of the present application. The data and/or information involved in the method of instantiating NS. In a possible design, the chip system further includes a memory, and the memory is used to store program instructions and/or data. The chip system can be composed of chips, and can also include chips and other discrete devices.

A person of ordinary skill in the art may realize that the units and algorithm steps of the examples described in combination with the embodiments disclosed herein can be implemented by electronic hardware or a combination of computer software and electronic hardware. Whether these functions are executed by hardware or software depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered as going beyond the scope of the embodiments of the present application.

It should be understood that, in the various embodiments of the embodiments of the present application, the size of the sequence number of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not be dealt with. The implementation process of the embodiments of this application constitutes any limitation.

Those skilled in the art can clearly understand that, for the convenience and conciseness of description, the specific working process of the above-mentioned network device can refer to the corresponding process in the foregoing method embodiment, which will not be repeated here.

It can be understood that the device embodiments described above are illustrative, for example, the division of the modules/units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components may be It can be combined or integrated into another system, or some features can be ignored or not implemented. In addition, the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.

The above are only specific implementations of the embodiments of the present application, but the protection scope of the embodiments of the present application is not limited thereto. Any person skilled in the art can easily think of changes or changes within the technical scope disclosed in the embodiments of the present application. Replacement shall be covered within the scope of protection of the embodiments of this application

Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the application, but not to limit them; although the application has been described in detail with reference to the foregoing embodiments, a person of ordinary skill in the art should understand that it is still possible to The technical solutions provided in the foregoing embodiments are modified, or some of the technical features are equivalently replaced, and these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the spirit of the technical solutions provided in the various embodiments of the application And scope.

Claims

A method for instantiating a network service NS, characterized in that the method is applied to a composite network function virtualization orchestrator NFVO, and the method includes:

Receiving a request to instantiate a composite NS, where the instant composite NS request includes deployment location information of the nested NS that needs to be instantiated;

Determine the corresponding nested NFVO according to the deployment location information of the nested NS and the nested NFVO information supporting the nested NS;

Send a request to instantiate the nested NS to the nested NFVO.
The method according to claim 1, wherein the nested NFVO information supporting the nested NS comprises: nested NFVO information capable of processing the network service descriptor NSD of the nested NS.
The method according to claim 2, characterized in that, before the receiving a request to instantiate a composite NS, the method further comprises:

Receiving registration information of the nested NFVO, where the registration information includes deployment location information of the nested NS managed by the nested NFVO;

The network service descriptor NSD information of the nested NS of the composite NS is received, and the NSD includes the nested NFVO information capable of processing the NSD.
The method according to claim 1, wherein the nested NFVO information supporting the nested NS comprises: nested NSD information supported by the nested NFVO.
The method according to claim 4, characterized in that, before the receiving a request to instantiate a composite NS, the method further comprises:

Receive registration information of the nested NFVO, where the registration information includes the deployment location information of the nested NS managed by the nested NFVO and the nested NSD information supported by the nested NFVO.
The method according to claim 1, wherein after the nested NFVO receives the instantiation nested NS request sent by the composite NFVO, the method further comprises:

The nested NFVO determines one or more VNFs included in the nested NS, and initiates a request to instantiate the one or more VNFs to the VNFM managed by the nested NFVO;

The VNFM and nested NFVO instantiate the nested NS by instantiating the VNF and its connection.
The method according to claim 6, wherein the method comprises:

Obtain the NSD of the corresponding composite NS according to the composite NS request, and obtain the virtual link VL information of the nested NS that needs to be instantiated and other NSs according to the composite NSD, and instantiate the VL;

Establish a connection between the nested NS instance and the VL instance according to the virtual link VL information.
A composite network function virtualization orchestrator NFVO, which is characterized in that it includes:

The receiving unit is configured to receive a request to instantiate a composite NS, where the instant composite NS request includes deployment location information of the nested NS that needs to be instantiated;

A processing unit, configured to determine the corresponding nested NFVO according to the deployment location information of the nested NS and the nested NFVO information supporting the nested NS;

The sending unit is configured to send a request to instantiate a nested NS to the nested NFVO.
The composite NFVO according to claim 8, characterized in that it comprises: the nested NFVO information supporting the nested NS includes: the nested NFVO information capable of processing the network service descriptor NSD of the nested NS.
The composite NFVO according to claim 9, characterized in that, before the receiving the instantiation composite NS request, the receiving unit is further configured to:

Receiving registration information of the nested NFVO, where the registration information includes deployment location information of the nested NS managed by the nested NFVO;

The network service descriptor NSD information of the nested NS of the composite NS is received, and the NSD includes the nested NFVO information capable of processing the NSD.
The composite NFVO according to claim 8, wherein the nested NFVO information supporting the nested NS comprises: nested NSD information supported by the nested NFVO.
The composite NFVO according to claim 11, wherein, before the receiving the instantiation composite NS request, the receiving unit is further configured to:

Receive registration information of the nested NFVO, where the registration information includes the deployment location information of the nested NS managed by the nested NFVO and the nested NSD information supported by the nested NFVO.
The composite NFVO according to claim 8, wherein the processing unit is further used for:

Obtain the NSD of the corresponding composite NS according to the composite NS request, and obtain the virtual link VL information of the nested NS that needs to be instantiated and other NSs according to the composite NSD, and instantiate the VL;

Establish a connection between the nested NS instance and the VL instance according to the virtual link VL information.
An NFVO system, including composite NFVO and nested NFVO, characterized in that:

The composite NFVO is used for,

Receiving a request to instantiate a composite NS, where the instant composite NS request includes deployment location information of the nested NS that needs to be instantiated;

Determine the corresponding nested NFVO according to the deployment location information of the nested NS and the nested NFVO information supporting the nested NS;

Sending a request to instantiate the nested NS to the nested NFVO;

The nested NFVO is used to,

One or more VNFs included in the nested NS are determined, and a request to instantiate the one or more VNFs is initiated to the VNFM managed by the VNFM, so that the VNFM instantiates the nested NS by completing the instantiation of each VNF.
The NFVO system according to claim 14, wherein the composite NFVO is also used for:

Obtain the NSD of the corresponding composite NS according to the composite NS request, and obtain the virtual link VL information of the nested NS that needs to be instantiated and other NSs according to the composite NSD, and instantiate the VL;

Establish a connection between the nested NS instance and the VL instance according to the virtual link VL information.
A computer-readable storage medium for storing instructions, which when executed by a processor of a computing device, enable the computing device to implement the method according to any one of claims 1 to 7.
A computing device includes a memory and a processor, the memory stores executable code, and when the processor executes the executable code, the method according to any one of claims 1 to 7 is implemented.