CN115361291A

CN115361291A - Method for instantiating network service and network function virtualization orchestrator

Info

Publication number: CN115361291A
Application number: CN202210786981.1A
Authority: CN
Inventors: 李世涛
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2019-12-27
Filing date: 2019-12-27
Publication date: 2022-11-18
Also published as: CN113055211B; CN113055211A; WO2021129868A1

Abstract

The application provides a method for instantiating an NS and an NFVO device, and the method comprises the following steps: receiving an instantiated composite NS request, wherein the instantiated composite NS request comprises deployment position information of a nested NS needing to be instantiated; determining a corresponding nested NFVO according to the deployment position information of the nested NS and the nested NFVO information supporting the nested NS; sending an instantiation nested NS request to the nested NFVO. The embodiment of the invention selects a proper NFVO-N to execute the corresponding nested NS deployment request by specifying the deployment position of the nested NS in the NS request and combining the range of the nested NS managed by the NFVO-N.

Description

Network service instantiation method and network function virtualization orchestrator

Technical Field

The present application relates to the field of communications, and in particular, to a method for instantiating a Network Service (NS) and a Network Function Virtualization Orchestrator (NFVO) device.

Background

NFV (Network Function Virtualization), i.e. Network Function Virtualization. The functions of special equipment in the traditional network are borne by using general hardware equipment and virtualization technology, so that the expensive cost caused by the deployment of the special equipment is reduced. By decoupling software and hardware, the functions of the network equipment are not dependent on special hardware. Meanwhile, by utilizing 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 expansion, fault isolation, self-healing and the like are carried out based on actual service requirements. The party capable of receiving the virtualization request and performing virtualization processing on the corresponding service according to the request is generally called a provider of the virtualization service, and the party initiating the virtualization request is generally called a service requester.

The Network Service virtualized in NFV is called an NS (Network Service), such as an IP Multimedia Subsystem IMS (IP Multimedia Subsystem) Network Service, or a next generation mobile Core Network EPC (Evolved Packet Core) Service. A NS may also include several Virtualized Network Function modules VNF (Virtualized Network Function). When a NS performs virtualization deployment, a Service requester first needs to submit description information of the Service to a Service provider, which is called an NSD (Network Service Descriptor), also called an NS deployment template, where the NSD mainly describes a topology of the Service and description information (VNFD, VNF Descriptor) of each VNF included in the Service, and a Virtual connection information VLD (Virtual Link Descriptor) is used in the topology information to describe connections between VNFs. VNFD is description information of a VNF, also referred to as a Deployment template of the VNF, where information such as a Virtual Deployment Unit VDU (virtualization Deployment Unit), a Connection Point CP (Connection Point), and a Virtual Connection VL (Virtual Link) is included, where the VDU may represent a Virtual machine in which application software is installed, a description of the VDU may include a description of requirements for all Virtual resources of the Virtual machine, the CP represents Connection information on the Virtual machine, such as Virtual network card information, and may be represented by an IP address or a MAC address, and the VL is a Virtual Connection in the VNF connecting multiple VDUs, and may be represented by information such as Connection types and bandwidths.

Disclosure of Invention

In order to solve the technical problems in the prior art, embodiments of the present application provide a method, an NFVO device, and a system for instantiating a composite NS.

The embodiment of the application provides a method for instantiating an NS, which is applied to a composite network function virtualization orchestrator NFVO, and comprises the following steps:

receiving an instantiated composite NS request, wherein the instantiated composite NS request comprises deployment position information of a nested NS needing to be instantiated;

determining a corresponding nested NFVO according to the deployment position information of the nested NS and the nested NFVO information supporting the nested NS;

sending an instantiation nested NS request to the nested NFVO.

The nested NFVO information supporting the nested NS comprises: the nested NFVO information of the network service descriptor NSD of the nested NS can be processed.

Prior to the receiving the instantiated composite NS request, the method further comprises:

receiving registration information of a nested NFVO, wherein the registration information comprises deployment position information of a nested NS managed by the nested NFVO;

receiving Network Service Descriptor (NSD) information of a nested NS of a composite NS, wherein the NSD comprises nested NFVO information capable of processing the NSD.

The nested NFVO information supporting the nested NS comprises: nested NFVO supported nested NSD information.

receiving registration information of the nested NFVO, wherein the registration information comprises deployment position information of a nested NS managed by the nested NFVO and nested NSD information supported by the nested NFVO.

The embodiment of the present application further provides a composite network function virtualization orchestrator NFVO, including:

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

the processing unit is used for determining a corresponding nested NFVO according to the deployment position information of the nested NS and the nested NFVO information supporting the nested NS;

a sending unit, configured to send an instantiated nested NS request to the nested NFVO.

The embodiment of the application also provides an NFVO system which comprises a composite NFVO and a nested NFVO,

the composite NFVO is used for preparing a composite NFVO,

determining corresponding nested NFVO information according to the deployment position information of the nested NS and the nested NFVO information supporting the nested NS

Nesting the NFVO;

sending an instantiation nested NS request to the nested NFVO;

the nested NFVO is configured to determine one or more VNFs that a nested NS includes, initiate an instantiation request of the one or more VNFs to a VNFM managed by the nested NS, so that the VNFM instantiates the nested NS by completing the instantiation of each VNF.

Also provided in embodiments herein is a computer-readable storage medium storing instructions that, when executed by a processor of a computing device, cause the computing device to implement the method of any of claims 1 to 7.

The embodiment of the present application further provides a computing device, which includes a memory and a processor, where the memory stores executable codes, and the processor executes the executable codes to implement the method recited in any one of claims 1 to 7.

There is also provided in an embodiment of the present application a computer program product comprising computer program code which, when run on a computing device, causes the computing device to perform the method of any of the first aspects described above.

By the scheme of the embodiment of the invention, the problem that the NFVO-C can not correctly select the NFVO-N under the nested NS scene in the prior art is solved; the embodiment of the invention selects the appropriate NFVO-N to execute the corresponding nested NS deployment request by specifying the deployment position of the nested NS in the NS request and combining the range of the nested NS managed by the NFVO-N.

Drawings

The drawings that accompany the detailed description can be briefly described as follows.

Fig. 1 is a block diagram of an NFV system according to an embodiment of the present disclosure.

Fig. 2 is a block diagram of an instantiated NS in an NFVO system according to an embodiment of the present disclosure.

Fig. 3 is a schematic flow chart of an instantiated NS in an NFVO system according to an embodiment of the present disclosure.

Fig. 4 is a schematic flow chart of an instantiated NS in another NFVO system according to the embodiment of the present application.

Fig. 5 is a schematic diagram of an NFVO device module according to an embodiment of the present disclosure.

Fig. 6 is a schematic block diagram of an NFVO system provided in embodiment 2 of the present application.

Detailed Description

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

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

NFVO102 is mainly responsible for life cycle management of NS, and for allocation and scheduling of virtual resources in Network Function Virtual Infrastructure (NFVI) 104. NFVO102 may communicate with one or more VNFMs 106, perform operations related to instantiating NS, such as sending corresponding configuration information to VNFM106, requesting status information of one or more VNFs 108 from VNFM 106. In addition, NFVO102 may also communicate with a Virtual Infrastructure Manager (VIM) 110 to perform allocation and/or reservation of resources in NFVI104, exchange resource configuration and status information, and the like.

The VNFM106 is primarily responsible for lifecycle management of one or more VNFs 108, such as instantiating (updating) VNFs 108, updating (updating) VNFs 108, querying VNFs 108, scaling (scaling) VNFs 108, terminating (terminating) VNFs 108, and so on. VNFM106 may communicate with VNF108 to manage the lifecycle of VNF108, exchange configuration and status information with the VNF, and the like. It is understood that one or more VNFMs 106 may be included in the NFV system 100, and each VNFM106 performs lifecycle management on different types of VNFs 108.

NFVI104, referring to the infrastructure of NFV system 100, includes hardware components, software components, and combinations thereof to establish a virtualized environment in which VNF108 is deployed, managed, and implemented. The NFVI104 may include at least computing (computing) hardware 1041, storage hardware 1042, network hardware 1043; the virtualization layer 1044 of the NFVI104 may abstract the foregoing hardware, decouple the hardware from the VNF108, and obtain corresponding virtual computing (virtual computing) resources 1045, virtual storage resources 1046, and virtual network resources 1047, thereby providing a virtual machine and other forms of virtualized containers for the VNF108.

VIM110 is mainly configured to control and manage interaction between VNF108 and computing hardware 1041, storage hardware 1042, network hardware 1043, virtual computing resources 1045, virtual storage resources 1046, and virtual network resources 1047. For example, VIM110 may perform resource management functions, such as adding corresponding virtual resources to a virtual machine or other form of virtual container, gathering fault information of NFVI104 during system operation, and so on. In addition, the VIM110 may communicate with the VNFM106, such as receiving resource allocation requests from the VNFM106, feeding back resource configuration and status information to the VNFM106, and so on.

VNF108, VNF108 includes one or more VNFs (typically multiple VNFs) that may run one or more virtual machines or other forms of virtual containers corresponding to a set of network functions that are originally implemented by a dedicated device.

An Equipment Management System (EMS) 112 may be used to configure and manage VNF108 and initiate lifecycle management operations, such as instantiation of a new VNF108, to VNFM 106. It is understood that one or more EMSs 112 may be included in the NFV system 100.

An Operation Support System (OSS) or a Business Support System (BSS) 114 may support various end-to-end telecommunication services. The management functions supported by the OSS may include network configuration, service provision, fault management, and the like; the BSS can be used for processing related services such as orders, payments, incomes, and the like, and support functions such as product management, order management, revenue management, customer management, and the like. It should be noted that OSS/BSS114 may request NFVO to instantiate NS as a service requester, and OSS/BSS114 or the computing device on which OSS/BSS114 depends may be referred to as a service requester.

It is understood that, in the NFV system 100 shown in fig. 1, the aforementioned functional entities may be respectively deployed in different computing devices, or part of the functional entities may be integrated into the same computing device.

As shown in fig. 2, NFVO-C is a network-wide NFVO (also called composite NFVO) and is responsible for the management of network-wide NS, VNF. NFVO-N is an NFVO (also called nested NFVO) within a sub-management domain, and is only responsible for the management of NS and VNF within its management domain. The number of the NFVO-N can be 1 or more, and the NFVO-N and the NFVO-C have communication interfaces. Composite NS _ a is a large network service as shown in fig. 1, which contains different VNFs and a Nested network service Nested NS _1, nested NS _1belonging to the administrative domain of the sub-administrative domain that is under the responsibility of NFVO _ N, including the allocation of resources to Nested NS _1, the management throughout the lifecycle, etc. NFVO-C is responsible for the management of the entire NS _ A network, and when NS _ A is deployed, when an operation involving Nested NS _1, such as instantiation, NFVO-C requests completion from NFVO-N.

The NFVO-N is a management orchestrator in an autonomous domain, and one autonomous domain can have a plurality of different NFVO-N, which belong to different equipment vendors. When an NFVO-C needs to deploy a Nested NS (Nested NS) service, how to select which NFVO-N in which autonomous domain to deploy the service is not mentioned in the prior art, nor is there a relevant standard to define how the NFVO-C can determine at 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 an NS, as shown in fig. 3, the steps specifically include:

301. one or more nested NFVOs (NFVO-N) register information of their management domain, including location information of an NS managed by the NFVO-N and vendor information corresponding to the NFVO-N, with a composite NFVO (NFVO-C).

For better understanding, this step and the subsequent steps are illustrated in fig. 2, and after a plurality of NFVO-ns (such as NFVO-N1, NFVO-N2 or NFVO-N3, only NFVO-N1 is shown in the figure) are registered with NFVO-C, the management domain information of NFVO-N stored on NFVO-C includes the following information:

NFVO-N1：

a vendor: equipment trader 1

Location:Location 1

NFVO-N2:

A vendor: equipment dealer 2

Location:Location 1

NFVO-N3:

A vendor: equipment trader 1

Location:Location 3

Wherein, the device vendor 1 and the device vendor 2 are providers of devices of NFVO-N1 and NFVO-N2, respectively, the Location is specifically a physical Location information, and for example, the Location1 may be: shanghai, china, location 2 is: beijing, china, location 3 is: shenzhen, china, can refer to the cities and location codes defined in the international standards RFC 4776 and ISO 3166 to express specific location information.

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

The oss/BSS uploads NSD (composite NSD) information of the composite NS that needs to be instantiated and NSD (nested NSD) information of the nested NS, where the nested NSD contains nfoinfo, which may be presented in the form of a list (list) indicating the ability or authorization to process NFVO information of the nested NSD.

Referring to fig. 2, the Nested NS to be instantiated is Nested _ NS _1, and nfvoInfo of NSD contains NFVO-N1 and NFVO-N3, which indicate that NFVO-N1 and NFVO-N3 of the device vendor 1 can manage lifecycle management operations such as deployment of the Nested _ NS _ 1. Different vendors do not share the same NSD, for example, NFVO-N2 of vendor 2 cannot use the NSD designed by vendor 1. The nfoinfo of the NSD may also contain equipment vendor information, which indicates that NFVO-N of the equipment vendor may manage lifecycle management operations such as deployment of the Nested _ NS _ 1.

oss/BSS sends an instantiate composite NS request to NFVO-C, the request including an instance identification of the composite NS that needs to be instantiated, the instance identification including a field NsLocationConstraint indicating deployment location information of each nested NS in the composite NS instance.

Referring to fig. 2, the instantiated composite NS request includes an instance identification of composite NS _ a, which includes a field NsLocationConstraint for indicating deployment Location information, such as Location1, of the Nested NS (i.e., nested _ NS _ 1) in the composite NS _ a instance.

If the NS to be instantiated comprises a plurality of Nested NS, the instance identifier comprises a plurality of NsLocationConstrainment fields respectively indicating the deployment position information of the plurality of Nested NS. Meanwhile, in step 302, the OSS/BSS uploads NSD information for a plurality of nested NSs that need to be instantiated, each NSD containing a respective nfvoInfo indicating that NFVO information for the NSD can be processed. Step 302 and step 303 are not in sequence, and step 302 may occur after step 303.

NFVO-C obtains NSD information of the corresponding composite NS according to the instance identifier included in the instantiated composite NS request received in step 303 (the NSD information is uploaded by the OSS/BSS in step 302), parses the NSD information, and obtains NSD identifiers of one or more nested NS included therein, thereby obtaining NSD information of each corresponding nested NS (as described in step 302, the NSD information of each nested NS is uploaded to the NFVO-C by the OSS/BSS), and obtains NFVO information capable of processing the NSD according to nfvoInfo included therein.

Referring to fig. 2, NFVO-C obtains NSD information of corresponding NS _ a according to an instance id of NS _ a included in the received instantiated composite NS request, parses the NSD information of NS _ a, obtains an NSD id of Nested _ NS _1 included in the NSD of NS _ a, obtains NSD information of Nested _ NS _1 according to the NSD id of Nested _ NS _1, and obtains NFVO information that can process the NSD, which are NFVO-N1 and NFVO-N3, according to nfoinfo information included therein.

Further, the NFVO-C acquires deployment location information of the nested NS according to the nlocationconstraint information in the NS instantiation request in step 303, and matches the NFVO information of the NSD that can process the nested NS acquired in the above step with the information of the management domain in which the nested NFVO (NFVO-N) is registered with the composite NFVO (NFVO-C) in step 301 to determine the NFVO-N that meets the requirement.

Referring to fig. 2, NFVO-C determines that Nested _ NS _1 needs to be deployed at Location1 according to nslocation constraint in the NS instantiation request, and then determines that NFVO at Location1 has NFVO-N1 and NFVO-N2 in combination with registration information of NFVO-N in the first step, and determines that NFVO capable of processing NSD information of Nested _ NS _1 is NFVO-N1 and NFVO-N3 according to the obtained NFVO that can process NSD information of Nested _ NS _1, and thus NFVO-C determines that NFVO-N1 meets the condition.

And 305, acquiring Virtual Link (VL) information connected with the nested NS by the NFVO-C according to the acquired NSD information of the composite NS instance, and instantiating the VL. The specific process of instantiating the VL is the prior art, and the basic flow is that NFVO-C requests network resources required for instantiating the VL from the VIM managed by the NFVO-C, and when the VL is instantiated, the VIM returns VL instance information to the NFVO-C.

Referring to fig. 2, nfvo-C acquires VL _2 information connected to Nested _ NS _1 based on the acquired NSD information of NS _ a, and then instantiates VL _2. This step is not in sequence with the above steps and may for example be performed before steps 302-304.

NFVO-C sends an instantiate nested NS request to the corresponding NFVO-N containing the instance identification of the corresponding nested NS and VL information connected to the nested NS 306.

Referring to fig. 2, in particular, NFVO-C sends an instantiation request for Nested _ NS _1 to NFVO-N1, the request containing the identification of the Nested _ NS _1 instance, and the request also contains connection information of VL _2 connected to Nested _ NS _ 1.

307. And the NFVO-N determines each VNF contained by the nested NS, selects proper VIM access information for the VNF, and initiates a VNF instantiation request to a VNFM managed by the VNF, wherein the VNVO-N contains the selected VIM access information.

Referring to FIG. 2, nested _NS _1contains two VNFs, VNF _4 and VNF _5, for which NFVO-C selects the appropriate VIM access information, and initiates a VNF instantiation request to the VNFM it manages.

And 308, the VNFM completes the instantiation process of each VNF, and after the VNFM completes the instantiation of the VNF, the NFVO-N establishes the connection of each VNF through the VL, thereby completing the instantiation of the nested NS.

Referring to FIG. 2, VNFM completes the instantiation of VNF _4 and VNF _5, NFVO-N1 connects them through VL _3, thus 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 instantiation of the other individual VNFs that the composite NS _ a includes, and connects through VL, and then establishes a connection with the nested NS through VL, thereby completing instantiation of the entire NS _ a.

Referring to fig. 2, in particular, NFVO-N1 establishes a connection between Nested _ NS _1 and VL _2 instance according to the connection information of VL _2 in step 306. Further, NFVO-C completes instantiation of other parts of the composite NS _ a, such as VNF1, VNF2, and VNF3, and performs internal interconnection via VL _1, and then establishes connection with VL _2 instance, thereby completing instantiation of the entire NS _ a.

The instantiation of the other parts of the composite NS _ A by the NFVO-C can be carried out before the completion of the instantiation of the Nested _ NS _1, or can be carried out before the steps 305-306, without any difference.

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

401. one or more nested NFVOs (NFVO-N) register information of their management domain with a composite NFVO (NFVO-C), which is different from embodiment 1 in that the information includes location information of an NS managed by the NFVO-N and NSD information supported by the NFVO-N.

For better understanding, this step and the subsequent steps are also exemplified by fig. 2, and after a plurality of NFVO-ns (NFVO-N1, NFVO-N2, NFVO-N3) are registered with NFVO-C, the management domain information of NFVO-N stored on NFVO-C 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 by a subscription mechanism, the NFVO-C subscribes the newly accessed management domain information of the NFVO-N, the NFVO-C sends a subscription Subscribe request to the NFVO-N, the NFVO-N replies Notification, and the address position information of the NS managed by the NFVO-N is reported to the NFVO-C.

The oss/BSS uploads NSD (composite NSD) information of the composite NS that needs to be instantiated and NSD (nested NSD) information of the nested NS, wherein the nested NSD may not contain nfovinfo, etc. information as described in step 302 of example 1.

403. The same procedure as in step 303 of example 1.

nfvo-C obtains the NSD information of the corresponding composite NS according to the instance identifier included in the instantiated composite NS request received in step 403, and parses the NSD information and obtains the NSD identifiers of one or more nested NS included therein.

Referring to fig. 2, nfvo-C obtains NSD information of the corresponding NS _ a according to the instance identification of NS _ a included in the received instantiated composite NS request, parses the NSD information of NS _ a, and obtains NSD identification NSD-1 of Nested _ NS _1 included in the NSD of NS _ a.

Further, the NFVO-C obtains the deployment location information of the nested NS according to the NsLocationConstraint information in the NS instantiation request of step 403, and matches the deployment location information with the information of the management domain registered by the nested NFVO (NFVO-N) to the composite NFVO (NFVO-C) in step 401, thereby determining the NFVO-N meeting the requirements.

Referring to FIG. 2, NFVO-C determines that Nested _ NS _1 needs to be deployed at Location1 according to NsLocation constraint in the NS instantiation request, and then determines that NFVO at Location1 has NFVO-N1 and NFVO-N2 and that NFVO capable of processing NSD-1 information of Nested _ NS _1 is NFVO-N1 and NFVO-N3, and NFVO-C determines that NFVO-N1 is eligible, in combination with the registration information of NFVO-N in step 401.

405-409, in the same manner as in steps 305-309 of example 1.

By the scheme of the embodiment of the invention, the problem that the NFVO-C can not correctly select the NFVO-N in the nested NS scene in the prior art is solved; the embodiment of the invention selects the appropriate NFVO-N to execute the corresponding nested NS deployment request by specifying the deployment position of the nested NS in the NS request and combining the range of the nested NS managed by the NFVO-N.

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

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

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

a sending unit 503, configured to send an instantiation nested NS request to the nested NFVO.

Prior to the receiving of the instantiate composite NS request, the receiving unit 501 is further configured to,

Prior to the receiving the instantiating the composite NS request, the receiving unit 501 is further configured to,

The processing unit 502 is further configured to: acquiring NSD of a corresponding composite NS according to the composite NS request, acquiring virtual link VL information of the nested NS to be instantiated connected with other NS according to the composite NSD, and instantiating the VL;

and establishing the 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 the specific implementation steps and actions thereof are the same as those implemented by NFVO-C in

method embodiments

1 and 2 described above and will not be repeated here.

In addition, the invention also provides an NFVO system 60 which comprises a composite NFVO601 and a nested NFVO 602,

the composite NFVO601 is used for,

receiving an instantiated composite NS request including a deployment bit for a nested NS that requires instantiation

Setting information;

Nesting the NFVO 602;

sending an instantiate nested NS request to the nested NFVO 602;

the nested NFVO 602 is used to,

determining one or more VNFs included by the nested NS, and initiating an instantiation request of the one or more VNFs to a VNFM managed by the VNFM, so that the VNFM instantiates the nested NS by completing the instantiation of each VNF.

The composite NFVO601 is further configured to acquire an NSD of a corresponding composite NS according to the composite NS request, acquire virtual link VL information of the nested NS to be instantiated connected to other NS according to the composite NSD, and instantiate the VL;

Again, the above description is merely a generalized description of the composite NFVO system, and the specific steps and acts performed are the same as those performed by NFVO-C and NFVO-N in

method embodiments

1 and 2 above and will not be repeated here.

Also provided in an embodiment of the present application is a computer-readable storage medium storing instructions that, when executed by a processor of a computing device, cause the computing device to implement the method of instantiating an NS provided in any one of the embodiments of the present application.

A computer program product is provided in an embodiment of the present application, comprising computer program code which, when run on a computing device, causes the computing device to perform a method of instantiating an NS as provided in any of the embodiments of the present application.

The embodiment of the application provides a computing device, which comprises a memory and a processor, wherein the memory stores executable codes, and when the processor executes the executable codes, the method for instantiating the NS, which is provided by any embodiment of the application, is realized.

The embodiment of the present application further provides a chip system, where the chip system includes a processor, and is configured to implement the functions of the NFVO described in any embodiment of the present application, for example, to receive or process data and/or information involved in the method of instantiating the NS described in any embodiment of the present application. In one possible design, the system-on-chip further includes a memory to hold program instructions and/or data. The chip system may be formed by a chip, and may also include a chip and other discrete devices.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the embodiments of the present application.

It should be understood that, in various embodiments of the present application, the sequence numbers of the above-mentioned processes do not imply an order of execution, and the order of execution of the processes should be determined by their functions and inherent logic, and should not limit the implementation processes of the embodiments of the present application.

It can be clearly understood by those skilled in the art that, for convenience and brevity of description, the specific working process of the network device may refer to the corresponding process in the foregoing method embodiment, and is not described herein again.

It will be appreciated that the above-described apparatus embodiments are illustrative, and that the division of the modules/units, for example, is merely one logical division, and that in actual implementation there may be additional divisions, for example, where multiple units or components may be combined or integrated into another system, or where some features may be omitted, or not implemented. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The above embodiments are only specific examples of the present application, but the scope of the embodiments of the present application is not limited thereto, and any person skilled in the art can easily conceive of changes or substitutions within the technical scope of the embodiments of the present application, and all the changes or substitutions should be covered by the scope of the embodiments of the present application

Finally, it should be noted that the above embodiments are only used for illustrating the technical solutions of the present application, and do not limit the same; although the present application has been described in detail with reference to the foregoing embodiments, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined by the appended claims.

Claims

1. A method for instantiating a network service NS, characterized in that it is applied to a composite network function virtualization orchestrator NFVO, and in that it comprises:

receiving an instantiated composite NS request comprising information indicating a deployment location of nested NS in an instance of the composite NS;

determining a corresponding nested NFVO according to the information for indicating the deployment position of the nested NS and the nested NFVO information supporting the nested NS;

sending an instantiation nested NS request to the nested NFVO.

2. The method of claim 1, wherein the nested NFVO information supporting the nested NS comprises: the nested NFVO information of the network service descriptor NSD of the nested NS can be processed.

3. The method of claim 2, wherein prior to said receiving the instantiated composite NS request, the method further comprises:

receiving registration information of a nested NFVO, the registration information including information indicating a deployment location of a nested NS managed by the nested NFVO;

4. The method of claim 1, wherein the nested NFVO information that supports the nested NS comprises: nested NFVO supported nested NSD information.

5. The method of claim 4, wherein prior to said receiving the instantiated composite NS request, the method further comprises:

receiving registration information of the nested NFVO, wherein the registration information comprises information used for indicating a deployment position of a nested NS managed by the nested NFVO and nested NSD information supported by the nested NFVO.

6. The method of claim 1, wherein after the nested NFVO receives an instantiated nested NS request sent by a composite NFVO, the method further comprises:

the nested NFVO determines one or more VNFs that the nested NS includes, and initiates an instantiation request of the one or more VNFs to a VNFM managed by the nested NFVO;

the VNFM and nested NFVO instantiate the nested NS by instantiating the VNF and its connections.

7. The method of claim 6, wherein the method comprises:

acquiring NSD of a corresponding composite NS according to the composite NS request, acquiring virtual link VL information of the nested NS to be instantiated connected with other NS according to the composite NSD, and instantiating the VL;

8. A composite network function virtualization orchestrator NFVO, comprising:

a receiving unit for receiving an instantiated composite NS request including information indicating a deployment location of a nested NS in an instance of the composite NS;

the processing unit is used for determining a corresponding nested NFVO according to the information for indicating the deployment position of the nested NS and the nested NFVO information supporting the nested NS;

9. The composite NFVO of claim 8, comprising: the nested NFVO information supporting the nested NS comprises: the nested NFVO information of the network service descriptor NSD of the nested NS can be processed.

10. The composite NFVO of claim 9, wherein prior to the receiving the instantiating composite NS request, the receiving unit is further to,

11. The composite NFVO of claim 8, wherein the nested NFVO information that supports the nested NS comprises: nested NFVO supported nested NSD information.

12. The composite NFVO of claim 11, wherein prior to the receiving the instantiating composite NS request, the receiving unit is further to,

13. The composite NFVO of claim 8, wherein the processing unit is further to:

14. An NFVO system comprising a composite NFVO and a nested NFVO,

the composite NFVO is used for preparing a composite NFVO,

sending an instantiation nested NS request to the nested NFVO;

the nested NFVO is used to,

15. The NFVO system of claim 14, wherein the composite NFVO is further configured to,

16. A computer-readable storage medium storing instructions that, when executed by a processor of a computing device, cause the computing device to implement the method of any of claims 1 to 7.

17. A computing device comprising a memory having executable code stored therein and a processor that, when executing the executable code, implements the method of any of claims 1 to 7.