CN109587024B

CN109587024B - Resource processing method and related device

Info

Publication number: CN109587024B
Application number: CN201710908685.3A
Authority: CN
Inventors: 冯爱娟; 夏海涛
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2017-09-29
Filing date: 2017-09-29
Publication date: 2020-12-22
Anticipated expiration: 2037-09-29
Also published as: CN109587024A

Abstract

The application discloses a method for processing resources, which is applied to a resource processing system and comprises the following steps: a first NFVO receives an instantiation request of a network service NS; the first NFVO reserves resources required by a first Virtual Network Function (VNF) and a first Virtual Link (VL) according to the instantiation request; the first NFVO sends a resource reservation request to the second NFVO, wherein the resource reservation request is used for indicating the second NFVO to reserve resources required by the second VNF and the second VL; if the resource reservation of the first NFVO and the second NFVO is successful, the first NFVO allocates the reserved resources to the first VNF and the first VL; the first NFVO sends an instantiation request to the second NFVO, where the instantiation request is used to instruct the second NFVO to allocate the reserved resources to the second VNF and the second VL. The method and the device can avoid all rollback of operations that are successfully instantiated or are currently instantiated due to insufficient resources of the NFVO.

Description

Resource processing method and related device

Technical Field

The present application relates to the field of communications technologies, and in particular, to a resource processing method and a related apparatus.

Background

Based on the modern virtualization technology, many operators have initiated and established the European Telecommunications Standards Institute (ETSI) Network Function Virtualization (NFV) Industry Specification Group (ISG). NFV makes network elements soft, so that the network elements can run on various general hardware, and realizes automation of network element deployment process through a management and organization (MANO) system, and an operator can rapidly and dynamically perform capacity expansion according to business needs.

In an actual NFV application, there may be a scenario where multiple Network Function Virtualization Orchestrator (NFVO) management domains are interconnected, for example, an operator may operate an independent NFVO management domain in different provincial companies, and the multiple Network Function Virtualization Orchestrator (NFVO) management domains jointly form a large operator network. Of course, the operator may also deploy independent NFVO management domains in each country, and form a complete operator network through interconnection. In some scenarios, there may be a Network Service (NS) formed across network services between two or more NFVO domains. Taking a top-down instantiation of a composite NS as an example, please refer to fig. 1, and fig. 1 is a schematic diagram illustrating a top-down instantiation process of the composite NS in a conventional scheme, in which resource management of the composite NS and a nested NS is mainly distributed as needed in the conventional scheme, and a Virtual Network Function (VNF) in a local domain of a plurality of nested NS and NFVO-1 can be instantiated synchronously.

Due to the need to synchronously instantiate VNFs within the local domain of multiple nested NSs and NFVO-1, if cross-domain resources of one of NFVO-2 are insufficient, steps 107 to 116 need to be re-executed to allocate corresponding virtual resources for composite NS instantiation again, thereby causing all instantiation operations of each domain to be rolled back.

Disclosure of Invention

The application provides a resource processing method and a related device, which can avoid all rollback of operations of successful instantiation or ongoing instantiation caused by insufficient resources of NFVO.

A first aspect of an embodiment of the present application provides a method for resource processing, where the method is applied to a resource processing system, and the resource processing system includes a first NFVO and a second NFVO, and how to perform resource reservation will be described below:

first, an OSS or BSS sends an instantiation request of a composite NS to a first NFVO, and the first NFVO receives the instantiation request of the NS, where the instantiation request is used to trigger the first NFVO to send a resource reservation request to a second NFVO, and the second NFVO may reserve resources required by a second VNF and a second VL according to the resource reservation request. It should be noted that the manner of reserving resources by the second NFVO may be that the first NFVO tells the second NFVO that resources (index to the nestdNsdId) need to be reserved, then the second NFVO finds the nestdNSD according to the nestdNsdId, and finally calculates how many resources need to be reserved. In addition, the second NFVO may reserve resources in a manner that the first NFVO directly tells the second NFVO what the resources that need to be reserved are, so that the second NFVO directly performs resource reservation.

Meanwhile, the first NFVO reserves resources required by the first VNF and the first VL according to the instantiation request. VNFs are proposed by a consortium of operators who, in order to speed up the deployment of new network services, tend to abandon heavy and expensive dedicated network devices, instead using standard IT virtualization techniques to split the network functional modules, while VLs are direct virtual network connections of the network devices.

At this time, if the reservation of the resources of both the first NFVO and the second NFVO is successful, the first NFVO allocates virtual resources on the reserved resources for the first VNF and the first VL, and this allocation formula is called "indirect mode". It should be noted that, in an actual situation, there is also a "direct mode" allocation manner, that is, a first VNF manager (VNF manager, VNFM) allocates virtual resources on the reserved resources for the first VNF and the first VL. For the operator, it is possible to select whether to allocate the virtual resources in the direct mode or in the indirect mode, depending on the situation. However, reserving resources can only be done by NFVO.

The first NFVO sends an instantiation request to the second NFVO, where the instantiation request indicates that the second NFVO allocates virtual resources on the reserved resources for the second VNF and the second VL. Of course, similar to the first MANO, there are two modes for allocating virtual resources in the other MANO, namely "direct mode" and "indirect mode". Wherein "direct mode" refers to the allocation of virtual resources by the second VNFM on the reserved resources for the second VNF and the second VL. The "indirect mode" allocates virtual resources for the second NFVO on the reserved resources for the second VNF and the second VL. Likewise, for the operator, whether to allocate the virtual resources in the direct mode or in the indirect mode may be selected according to the situation.

The VNFM may manage a lifecycle of the VNF, such as online, offline, and status monitoring. The VNFM manages VNFs based on VNF descriptors (VNFDs). The NFV is used to manage the NS lifecycle, coordinate management of the VNF lifecycle (supported by the VNFM), coordinate management of various resources (supported by the virtualized infrastructure manager VIM) of the NFV infrastructure layer (NFVI), and thus ensure optimal configuration of various required resources and connections. The NFVO runs based on a Network Service Descriptor (NSD) which includes a service chain, NFV, and a presentation target.

As can be seen, in the embodiment of the present application, after the first NFVO receives the instantiation request, resources may be reserved for the instantiation operation first, and the second NFVO is also instructed to reserve resources for the subsequent instantiation operation, so that it is possible to avoid that the NFVO causes all rollback of the operations that have been successfully instantiated or are currently instantiated due to insufficient resources.

In a possible design, in a first implementation manner of the first aspect of the embodiment of the present application, the first NFVO and the second NFVO may further determine which resources need to be reserved by establishing a mapping relationship when reserving the resources. Specifically, it may be that the first NFVO receives an instantiation request of the network service that the first NFVO receives an instantiation request of the composite NS. The instantiation request is used for triggering the first NFVO to send a resource reservation request to the second NFVO, the resource reservation request is used for indicating the second NFVO to establish a second mapping relationship, the second mapping relationship comprises a composite NS resource identifier, a second resource group identifier and a corresponding relationship between the second resource reservation identifier, the composite NS resource identifier is used for identifying an instance of the composite NS, the second resource group identifier is used for identifying a second VNF and a second VL, and the first resource reservation identifier is used for identifying resources reserved for the second VNF and the second VL. Meanwhile, the first NFVO also establishes a first mapping relationship according to the instantiation request, where the first mapping relationship includes a correspondence between a composite NS resource identifier, a first resource group identifier, and a first resource reservation identifier, the first resource group identifier is used to identify the first VNF and the first VL, and the first resource reservation identifier is used to identify resources reserved for the first VNF and the first VL.

Similarly, the first NFVO may determine the first VNF and the first VL according to the composite NS resource identifier and the first mapping relationship, and allocate virtual resources on the reserved resources for the first VNF and the first VL, where the allocation manner is referred to as an "indirect mode". In the direct mode, the first VNFM determines the first VNF and the first VL according to the composite NS resource identifier and the first mapping relationship, and allocates virtual resources on the reserved resources for the first VNF and the first VL.

The first NFVO sends an instantiation request to the second NFVO, wherein the instantiation request carries a composite NS resource identifier, and the instantiation request is used for indicating the second NFVO to determine a second VNF and a second VL according to the composite NS resource identifier and a second mapping relation, and allocate virtual resources on reserved resources for the second VNF and the second VL. This allocation is referred to as an "indirect mode". And in the direct mode, the second VNFM determines the second VNF and the second VL according to the composite NS resource identifier and the second mapping relationship, and allocates virtual resources on the reserved resources for the second VNF and the second VL.

It can be seen that, in the embodiment of the present application, the NFVO in different domains may determine the required virtual resources through the mapping relationship, and allocate the virtual resources for the instantiation operation, on one hand, a feasible manner is provided for determining the virtual resources of each domain, which is beneficial to improving the practicability of the scheme, and on the other hand, all rollback of operations that have been instantiated successfully or are being instantiated due to insufficient resources of the NFVO can be avoided.

In a possible design, in a second implementation manner of the first aspect of the embodiment of the present application, whether the first NFVO or the second NFVO, the already reserved resources may be released as long as a resource reservation failure occurs when reserving resources, where the resource reservation failure may be generally a timeout or an insufficient resource.

Specifically, if the resource reservation of the first NFVO and/or the second NFVO fails, the first NFVO releases the virtual resources reserved for the first VNF and the first VL according to the composite NS resource identifier and the first mapping relationship. Of course, in addition to the first NFVO releasing the reserved virtual resources, the second NFVO also releases the virtual resources, it is understood that the number of the second NFVO may be one or more, and the application does not limit the number of the second NFVO.

The first NFVO sends the resource release request to the second NFVO according to a third mapping relationship, where the third mapping relationship includes the composite NS resource identifier, the second NFVO identifier, and the resource reservation identifier, that is, the first NFVO can know, through the third mapping relationship, which second NFVO resources are successfully reserved and which second NFVO resources are unsuccessfully reserved. The first NFVO sends a resource release request to the second NFVO with the failed reservation, so that the second NFVO releases the resources reserved for the second VNF and the second VL according to the resource release request, the composite NS resource identifier, and the second mapping relationship.

As can be seen, in the embodiment of the present application, as long as resource reservation of one domain fails, all domains release the reserved virtual resources, and do not perform the lifecycle management operation of the composite NS any more. By adopting the mode, through the cross-domain resource reservation, the problem that the instantiation operation of the composite NS fails due to insufficient resources of a certain domain is solved, and then the problem of operation rollback of a plurality of domains is solved.

In a possible design, in a third implementation manner of the first aspect of the embodiment of the present application, how to judge the resource reservation situation according to the resource reservation identifier in the third mapping relationship is further described.

The first NFVO acquires the resource reservation identifier from the third mapping relationship, and it can be understood that there are various ways of representing the resource reservation identifier, for example, a single identifier or multiple identifiers. Wherein, the single identifier indicates that the resource reservation can be usually explained by using one identifier, for example, "1" indicates that the resource reservation is successful, and "0" indicates that the resource reservation is failed. And the multi-identifier flag determines whether the resource reservation is successful or not in multiple dimensions, for example, if the resource reservation timeout is represented as "1", the resource reservation non-timeout is represented as "0", and the resource reservation is sufficiently represented as "1", and the resource reservation insufficiency is represented as "0", the first NFVO determines that the resource reservation of the first NFVO and/or the second NFVO fails (i.e., the resource reservation is considered to fail) if the resource reservation flag indicates that the current resource reservation state is the resource reservation timeout or the resource reservation insufficiency. On the contrary, if the resource reservation flag indicates that the current resource reservation state is that the resource reservation is completed and the resource reservation is sufficient, the first NFVO determines that the resource reservation of the first NFVO and the second NFVO is successful (i.e., the resource reservation is considered to be successful).

As can be seen, in the embodiment of the present application, the resource reservation condition may also be determined by using the resource reservation identifier in the third mapping relationship, and the current resource reservation success may only be determined when the resource reservation is completed and the resource reservation is sufficient. By the mode, the feasibility and operability of the scheme can be improved.

In a possible design, in the fourth implementation manner of the first aspect of the embodiment of the present application, in practical applications, the virtual function in one MANO domain may be further divided into a plurality of sub-functions, for example, data that calls 20 terminal devices is required to call the processor in the MANO-1, and then each sub-function may be data that calls 5 terminal devices, so that one total virtual resource may be divided into a plurality of sub-virtual resources, and each sub-virtual resource is used to perform a part of functions.

Specifically, in the scenario of dividing sub-virtual resources, both the resource group identifier and the resource reservation identifier need to be divided into multiple sub-identifiers, that is, the first resource group identifier includes multiple first sub-resource group identifiers, the first sub-resource group identifier is used to identify a first sub-VNF and a first sub-VL, the first resource reservation identifier includes multiple first sub-resource reservation identifiers, the first sub-resource reservation identifier is used to identify resources reserved for the first sub-VNF and the first sub-VL, the first VNF includes multiple first sub-VNFs, and the first VL includes multiple first sub-VLs. Similarly, the second resource group identifier includes a plurality of second sub-resource group identifiers, the second sub-resource group identifiers are used to identify a second sub-VNF and a second sub-VL, the second resource reservation identifier includes a plurality of second sub-resource reservation identifiers, the second sub-resource reservation identifier is used to identify resources reserved for the second sub-VNF and the second sub-VL, the second VNF includes a plurality of second sub-VNFs, and the second VL includes a plurality of second sub-VLs.

At this time, the whole instantiation process is that the first NFVO receives an instantiation request of the composite NS sent by the OSS or BSS, where the instantiation request is used to trigger the first NFVO to send a resource reservation request to the second NFVO, the resource reservation request is used to indicate the second NFVO to establish a second mapping relationship, and the second mapping relationship includes a correspondence relationship between the composite NS resource identifier, the plurality of second sub-resource group identifiers, and the plurality of second sub-resource reservation identifiers.

It should be noted that the manner of reserving resources by the second NFVO may be that the first NFVO tells the second NFVO that resources (index to the nestdNsdId) need to be reserved, then the second NFVO finds the nestdNSD according to the nestdNsdId, and finally calculates how many resources need to be reserved. In addition, the second NFVO may reserve resources in a manner that the first NFVO directly tells the second NFVO what the resources that need to be reserved are, so that the second NFVO directly performs resource reservation.

And the second NFVO firstly creates a composite NS resource identifier according to the instantiation request, and then establishes a second mapping relation according to the composite NS resource identifier, the plurality of second sub-resource group identifiers and the plurality of second sub-resource reservation identifiers.

Therefore, in the embodiment of the application, resources can be respectively reserved for each sub-object in a domain, and a mapping relation is established according to each sub-object, so that the feasibility and operability of establishing the mapping relation are improved.

In a possible design, in a fifth implementation manner of the first aspect of the embodiment of the present application, in a scenario including reservation of multiple sub-virtual resources, if reservation of resources of the first NFVO and/or the second NFVO fails, the first NFVO may release resources reserved for the first sub-VNF and the first sub-VL according to the composite NS resource identifier and the first mapping relationship. Similar to the scenario of reserving the total virtual resources, the first NFVO may also send a resource release request to the second NFVO according to the third mapping relationship, where the resource release request carries the composite NS resource identifier, and the resource release request is used to indicate the second NFVO to release the resources already reserved for the second sub-VNF and the second sub-VL or to release the resources currently reserved for the second sub-VNF and the second sub-VL according to the composite NS resource identifier and the second mapping relationship.

It is understood that there are various ways of representing the resource reservation identifier in the third mapping relationship, such as a single identifier representation or a multiple identifier representation, similar to the above description, and is not limited herein.

It can be seen that, in the embodiment of the present application, as long as there is a resource reservation failure of an object in a domain, the virtual resources of the object are released, and the virtual resources include resources already reserved or resources being reserved. By adopting the mode, the virtual resource reserved by a certain object can be released in a targeted manner, so that the operability and the accuracy of resource release are improved, and the efficiency of resource reservation is effectively improved.

In one possible design, in a sixth implementation of the first aspect of the embodiment of the present application, there are also two resource allocation modes for the sub-virtual resources in each MANO domain, the first mode is to allocate virtual resources by NFVO, and the second mode is to allocate virtual resources by VNFM.

If the NFVO allocates the virtual resource, specifically, if the resource reservation of the first NFVO and the second NFVO is successful, the first NFVO determines the first sub-VNF and the first sub-VL according to the composite NS resource identifier and the first mapping relationship, and allocates the virtual resource on the reserved resource for the first sub-VNF and the first sub-VL. Then, the first NFVO sends an instantiation request to the second NFVO, where the instantiation request carries the composite NS resource identifier, and after receiving the instantiation request, the second NFVO may determine the second sub-VNF and the second sub-VL according to the composite NS resource identifier and the second mapping relationship, and allocate virtual resources to the reserved resources for the second sub-VNF and the second sub-VL.

If the VNFM allocates the virtual resource, specifically, if the resource reservation of the first NFVO and the second NFVO is successful, the first VNFM determines the first sub-VNF and the first sub-VL according to the composite NS resource identifier and the first mapping relationship, and allocates the virtual resource on the reserved resource for the first sub-VNF and the first sub-VL. Then, the first VNFM sends an instantiation request to the second VNFM, where the instantiation request carries the composite NS resource identifier, and after the second VNFM receives the instantiation request, the second VNFM may determine the second sub-VNF and the second sub-VL according to the composite NS resource identifier and the second mapping relationship, and allocate virtual resources to the second sub-VNF and the second sub-VL on the reserved resources.

Therefore, in the embodiment of the application, the NFVO may also allocate corresponding virtual resources to each object according to the mapping relationship, so that feasibility and practicability of resource allocation are improved.

In a possible design, in a seventh implementation manner of the first aspect of the embodiment of the present application, after the first NFVO sends the resource release request to the second NFVO, the first NFVO further updates the first mapping relationship, and of course, the second NFVO page correspondingly updates the second mapping relationship. The updated content includes, but is not limited to, updating the resource reservation identification.

Therefore, in the embodiment of the application, after the reserved virtual resources are released, the mapping relationship needs to be further updated, and in the above manner, the mapping relationship can be updated in time according to the use condition of the virtual resources, so that the practicability and feasibility of the scheme are improved.

In a possible design, in an eighth implementation manner of the first aspect of the embodiment of the present application, the first NFVO further needs to determine whether instantiation of the current composite NS is successful according to the second NFVO and a result fed back by the first NFVO.

Specifically, after the first NFVO sends the resource allocation request to the second NFVO, the second NFVO may perform an instantiation operation on the allocated virtual resources, and after the instantiation operation is successful, the second NFVO sends an instantiation success message to the first NFVO, and at this time, the first NFVO can determine that the nested NS instantiation of the second NFVO is successful. In addition, for the first NFVO, an instantiation operation is also performed on the resources corresponding to the first VNF and the first VL, and after the instantiation operation is successful, the first NFVO determines that the instantiation of the composite NS is successful.

As can be seen, in the embodiment of the present application, if the second NFVO sends the instantiation success message, it indicates that the second NFVO has completed the instantiation operation, and in addition, if the first NFVO also completes the instantiation operation, it can be determined that the composite NS is successfully instantiated, and through the above manner, whether the instantiation of each domain is successful or not can be accurately determined, so that the practicability and feasibility of the scheme are improved.

In a possible design, in a ninth implementation manner of the first aspect of the embodiment of the present application, after the first NFVO determines that the instantiation across-domain NS is successful, if the composite NS needs to expand or contract, the virtual resource also needs to be expanded or contracted synchronously. Wherein, for the capacity reduction operation, the resource is updated by updating the reserved resource after the capacity reduction of the object is completed. For the capacity expansion operation, the resource is updated before the object capacity expansion operation.

First, a first NFVO receives a composite NS update request or a composite NS capacity expansion and contraction request, and then the first NFVO sends a capacity expansion and contraction request to a second NFVO according to the composite NS update request or the composite NS capacity expansion and contraction request. And the second NFVO performs resource capacity expansion or resource capacity reduction operation on the reserved (or quota) resources according to the capacity expansion and reduction request, and obtains the first resource to be updated. The first resource to be updated is used to instruct the second NFVO to update (i.e., expand or contract) the reserved resources of the second VNF and the second VL. Likewise, the first NFVO determines a second resource to be updated according to the composite NS update request or the composite NS scaling request, and updates (i.e., scales or scales) the resources reserved by the second VNF and the second VL according to the second resource to be updated.

Therefore, in the embodiment of the application, after the composite NS is successfully instantiated, the virtual resource can be further updated according to the composite NS update request or the composite NS capacity expansion and reduction request, so that the virtual resource can be correspondingly adjusted according to different instantiation requirements, and the practicability and flexibility of the scheme are improved.

In one possible design, in a tenth implementation manner of the first aspect of the embodiment of the present application, after the instantiation operation is finished, both the first NFVO and the second NFVO may reclaim the virtual resource.

Specifically, if the first NFVO receives the composite NS instantiation completion request, the first NFVO releases resources reserved for the first VNF and the first VL according to the composite NS resource identifier and the first mapping relationship. In addition, the first NFVO may also send a resource release request to the second NFVO, where the resource release request carries the composite NS resource identifier, and the resource release request is used to instruct the second NFVO to release resources reserved for the second VNF and the second VL according to the composite NS resource identifier and the second mapping relationship.

Therefore, in the embodiment of the application, after the instantiation is completed, the reserved virtual resources can be released according to the mapping relation, so that the virtual resources can be vacated for subsequent instantiation operations, the virtual resources can be reused, and the practicability of the virtual resources is improved.

A second aspect of the embodiments of the present application provides a method for resource processing, where the method is applied to a resource processing system, and the resource processing system includes a first NFVO and a second NFVO, and how to perform resource quota is described as follows:

first, an OSS or a BSS sends a resource quota request of a composite NS to a first NFVO, and the first NFVO receives the resource quota request and then configures required resources for a first VNF and a first VL according to the resource quota request. Then, the first NFVO may send a resource quota request to the second NFVO, where the resource quota request is used to indicate that the second NFVO configures required resources for the second VNF and the second VL. VNFs are proposed by a consortium of operators who, in order to speed up the deployment of new network services, tend to abandon heavy and expensive dedicated network devices, instead using standard IT virtualization techniques to split the network functional modules, while VLs are direct virtual network connections of the network devices.

At this time, if the quotas of the resources of both the first NFVO and the second NFVO are successful, the first NFVO allocates virtual resources on the quotad resources for the first VNF and the first VL, and this allocation is called "indirect mode". It should be noted that, in an actual situation, there is also a "direct mode" allocation manner, that is, a first VNFM allocates a virtual resource on a quota of resources for a first VNF and a first VL. For the operator of either the first MANO or the second MANO, the operator may choose to allocate the quota-good virtual resources in a direct mode or in an indirect mode, depending on the situation. However, quota resources this operation can only be done by NFVO.

Finally, the first NFVO sends an instantiation request to the second NFVO, so that the second NFVO performs resource management operations required for instantiation on the allocated quota resources (i.e., the second VNF and the second VL) according to the instantiation request.

It is understood that the first MANO includes a first NFVO and a first VNFM and the second MANO includes a second NFVO and a second VNFM.

In an embodiment of the present application, a method for processing resources is provided, where first, an NFVO receives a resource quota request, then configures required resources for a first VNF and a first VL according to the resource quota request, the NFVO sends the resource quota request to a second NFVO, where the resource quota request is used to indicate the second NFVO to configure the required resources for a second VNF and a second VL, and if the resource quota is successful, the NFVO allocates virtual resources for the first VNF and the first VL on the configured resources, and finally, the NFVO sends an instantiation request to the second NFVO, where the instantiation request is used to indicate the second NFVO to allocate virtual resources for the second VNF and the second VL on the configured resources. With the above apparatus, the NFVO may configure resources for instantiation operations first, and instruct the second NFVO to also configure resources for subsequent instantiation operations, so that it is possible to avoid that the NFVO causes all rollback of operations that have been instantiated successfully or are being instantiated due to insufficient resources.

A third aspect of an embodiment of the present application provides an NFVO, where the NFVO is applied to a resource processing system, the resource processing system further includes a second NFVO, and the NFVO includes:

a receiving module for receiving an instantiation request of the NS;

a reservation module, configured to reserve, according to the instantiation request received by the receiving module, resources required by the first virtual network function VNF and the first virtual link VL;

a sending module, configured to send a resource reservation request to the second NFVO, where the resource reservation request is used to instruct the second NFVO to reserve resources required by the second VNF and the second VL;

the allocation module is configured to, if the resource reservation of the first NFVO and the second NFVO is successful, the first NFVO allocates the reserved resources to the first VNF and the first VL that are reserved by the reservation module;

a sending module, configured to send an instantiation request to the second NFVO, where the instantiation request is used to instruct the second NFVO to allocate the reserved resources to the second VNF and the second VL.

A fourth aspect of the embodiment of the present application provides an NFVO, where the NFVO is applied to a resource processing system, the resource processing system further includes a second NFVO, and the NFVO includes:

a receiving module, configured to receive a resource quota request;

the quota module is used for configuring required resources for the first virtual network function VNF and the first virtual link VL according to the resource quota request received by the receiving module;

a sending module, configured to send, to the second NFVO, the resource quota request received by the receiving module, where the resource quota request is used to indicate that the second NFVO configures required resources for the second VNF and the second VL;

an allocating module, configured to allocate reserved resources to a first VNF and a first VL if resource quotas of the first NFVO and the second NFVO are successful;

a sending module, configured to send an instantiation request to the second NFVO, where the instantiation request is used to instruct the second NFVO to perform resource management operations required for instantiation on the allocated quota resources.

A fifth aspect of the present application provides an NFVO, comprising: a memory, a transceiver, a processor, and a bus system;

wherein, the memory is used for storing programs;

the processor is used for executing the program in the memory, and comprises the following specific steps:

receiving an instantiation request of the NS;

reserving resources required by the first VNF and the first VL according to the instantiation request;

sending a resource reservation request to the second NFVO, where the resource reservation request is used to instruct the second NFVO to reserve resources required by the second VNF and the second VL;

if the resource reservation of the first NFVO and the second NFVO is successful, allocating the reserved resources to the first VNF and the first VL;

sending an instantiation request to a second NFVO, wherein the instantiation request is used for indicating the second NFVO to allocate the reserved resources to a second VNF and a second VL;

the bus system is used for connecting the memory, the transceiver and the processor so as to enable the memory, the transceiver and the processor to communicate.

A sixth aspect of the present application provides an NFVO, comprising: a memory, a transceiver, a processor, and a bus system;

wherein, the memory is used for storing programs;

receiving a resource quota request;

configuring required resources for the first VNF and the first VL according to the resource quota request;

sending a resource quota request to a second NFVO, where the resource quota request is used to indicate that the second NFVO configures required resources for a second VNF and a second VL;

if the resource quotas of the first NFVO and the second NFVO are successful, allocating reserved resources to the first VNF and the first VL;

sending an instantiation request to a second NFVO, wherein the instantiation request is used for indicating the second NFVO to perform resource management operation required by instantiation on the allocated quota resource;

In a seventh aspect, an embodiment of the present application provides a computer device, including: a processor, a memory, a bus, and a communication interface; the memory is used for storing computer execution instructions, the processor is connected with the memory through the bus, and when the server runs, the processor executes the computer execution instructions stored by the memory so as to enable the server to execute the method according to any one of the aspects.

In an eighth aspect, embodiments of the present application provide a computer-readable storage medium for storing computer software instructions for the method described above, which when executed on a computer, enable the computer to perform the method of any one of the above aspects.

In a ninth aspect, embodiments of the present application provide a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of any of the above aspects.

In addition, for technical effects brought by any one of the design manners of the third aspect to the ninth aspect, reference may be made to technical effects brought by different design manners of the first aspect and the second aspect, and details are not described here.

According to the technical scheme, the method has the following advantages:

in an embodiment of the present application, a method for resource processing is provided, where the method is applied to a resource processing system, and the resource processing system includes a first NFVO and a second NFVO, where the first NFVO receives an instantiation request of a network service NS, then the first NFVO reserves resources required by a first VNF and a first VL according to the instantiation request, and then the first NFVO sends a resource reservation request to the second NFVO, where the resource reservation request is used to indicate the second NFVO to reserve resources required by a second VNF and a second VL, if the resource reservation of the first NFVO and the second NFVO is successful, the first NFVO allocates the reserved resources to the first VNF and the first VL, and finally the first NFVO sends an instantiation request to the second NFVO, where the instantiation request is used to indicate the second NFVO to allocate the reserved resources to the second VNF and the second VL. In this way, after the first NFVO receives the instantiation request, resources may be reserved for the instantiation operation first, and the second NFVO is also instructed to reserve resources for the subsequent instantiation operation, so that it is possible to avoid that the NFVO causes all rollback of the operations that have been instantiated successfully or are being instantiated due to insufficient resources.

Drawings

FIG. 1 is a schematic diagram illustrating a top-down instantiation process of a composite NS in a conventional solution;

FIG. 2 is a schematic diagram of a composite NS and a nested NS in the cross-domain network service of the present application;

FIG. 3 is a diagram of the management architecture between network function virtualization orchestrators in a cross-domain NS according to the present application;

FIG. 4 is a diagram of a network function virtualization architecture in an embodiment of the present application;

FIG. 5 is a structural view of the NS in the embodiment of the present application;

FIG. 6 is a schematic structural diagram of NFVO in the embodiment of the present application;

FIG. 7 is a diagram of an embodiment of a method for resource processing in an embodiment of the present application;

fig. 8 is a schematic flowchart of resource reservation performed by taking intra-domain total resources as objects in an application scenario of the present application;

fig. 9 is a schematic flow chart illustrating resource reservation for each sub-object in a domain in an application scenario of the present application;

FIG. 10 is a schematic diagram of another embodiment of a method for resource processing in an embodiment of the present application;

fig. 11 is a schematic flowchart of resource quota setting performed by taking total resources in a domain as an object in an application scenario of the present application;

fig. 12 is a schematic flowchart of resource quota setting for each sub-object in a domain in an application scenario of the present application;

FIG. 13 is a schematic view of a process for resource update and recovery in an application scenario of the present application;

FIG. 14 is a schematic diagram of an embodiment of NFVO in the examples of the present application;

fig. 15 is a schematic diagram of another embodiment of the NFVO in the embodiment of the present application;

fig. 16 is a schematic diagram of another embodiment of the NFVO in the embodiment of the present application;

fig. 17 is a schematic diagram of another embodiment of the NFVO in the embodiment of the present application;

FIG. 18 is a schematic diagram of an embodiment of NFVO in the examples of the present application;

fig. 19 is a schematic diagram of another embodiment of the NFVO in the embodiment of the present application.

Detailed Description

The terms "first," "second," "third," "fourth," and the like in the description and in the claims of the present application and in the drawings described above, if any, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the application described herein are, for example, capable of operation in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

It should be understood that the present application is mainly applied to a cross-domain NS scenario, and in an actual NFV application, there may be a scenario where multiple NFVO management domains are interconnected, such as: in china and the united states, companies located in different provinces in an operator may each operate an independent NFVO management domain, which together make up a large operator network. In europe, operators with larger scale may also deploy independent NFVO management domains in various countries, forming a complete operator network through interconnection. In some scenarios, there may be a composite NS (composite NS) formed across network services between two or more NFVO domains, and for ease of understanding, referring to fig. 2, fig. 2 is a schematic diagram of a composite NS and a nested NS in the cross-domain network service of the present application, and as shown, NS a and NS B in fig. 2 are nested NS (nested NS) with respect to a composite NS X.

In the scenario of the cross-domain NS, please further refer to fig. 3, where fig. 3 is a management architecture diagram between network function virtualization organizers in the cross-domain NS of the present application, as shown in the figure, an umbrella-shaped management architecture is formed by NFVOs of multiple management domains, a top-level NFVO is defined as NFVO-1, NFVO-1 is mainly responsible for orchestration management of a composite NS, an NFVO of a specific management domain is defined as NFVO-2, and NFVO-2 is mainly responsible for orchestration management of each nested NS, and they complete lifecycle management of the composite NS across NFVO domains through an Or-Or interface.

It can be appreciated that one premise of the cross-domain NS scenario for virtual resource management applications is that the NFVO in one management domain is unaware of both the VNF and the Virtualized Infrastructure Manager (VIM) in another management domain.

It should be understood that the NFVO provided by the present application is applied to the NFV architecture, and a conventional telecommunication system is composed of various dedicated hardware devices, and different applications adopt different hardware devices. With the increase of network scale, the system becomes more complex, and a plurality of challenges are brought, including development online of new services, operation and maintenance of the system, resource utilization rate and the like. In order to meet these challenges and utilize virtualization technology and cloud computing technology in IT industry, 13 major telecommunication operators in the world have jointly issued NFV white papers on "Software Defined Network (SDN) world meeting" held by day 22/10/2012, and announced that an NFV ISG is established in ETSI, and the demand and technical framework of NFV are formulated to promote the development of NFV.

NFV technology is simply understood to migrate the functionality of various network elements used in telecommunications networks from the current dedicated hardware platform to a common commercial-off-the-shelf (COTS) server. Each network element used in the telecommunication network is converted into independent application through NFV technology, the network element can be flexibly deployed on a unified infrastructure platform constructed by other equipment such as a standard server, a storage and a switch, the resources of infrastructure hardware equipment are pooled and virtualized through virtualization technology, virtual resources are provided for upper-layer application, application and hardware decoupling is achieved, each application can rapidly increase the virtual resources to achieve the purpose of rapidly expanding the system capacity, or the virtual resources can be rapidly reduced to achieve the purpose of shrinking the system capacity, and the elasticity of the network is greatly improved. A shared resource pool is formed by adopting a universal COTS server, newly developed services do not need to be independently deployed with hardware equipment, and the online time of the new services is greatly shortened.

The foundation of NFV technology includes cloud computing technology and virtualization technology. Hardware devices such as a general COTS (chip on the fly) calculation/storage/network and the like can be decomposed into a plurality of virtual resources through a virtualization technology so as to be used by various upper-layer applications. The decoupling between the application and the hardware is realized through a virtualization technology, so that the virtual resource supply speed is greatly increased; by the cloud computing technology, elastic expansion of application can be achieved, matching of virtual resources and service loads is achieved, utilization efficiency of the virtual resources is improved, and response rate of a system is improved.

Fig. 4 is a system architecture diagram of an NFV, which NFV system 200 may be used in various networks, such as implemented in a data center network, an operator network, or a local area network. The NFV system 200 includes an NFV management and orchestration system (NFV MANO)101, an NFV infrastructure layer (NFV vi)230, a plurality of Virtual Network Functions (VNFs) 208, a plurality of Element Management (EM) 222, an NS, a VNF, and an infrastructure description (VNF and infrastructure description)226, and an operation-support system/configuration support system (OSS or BSS) 224. The NFV management and orchestration system 201 includes, among other things, an NFVO202, one or more VNFMs (VNF managers) 204, and a VIM 206. NFVI 230 includes computing hardware 212, storage hardware 214, network hardware 216, virtualization layer (virtualization layer), virtual computing 210, virtual storage 218, and virtual network 220. Network services, VNF and infrastructure description 226 and OSS/BSS 224 are discussed further in the ETSI GS NFV 002V1.1.1 standard.

NFV management and orchestration system (NFV MANO)201 is used to perform monitoring and management of VNF 208 and NFVI 230. NFVO202 may implement network services (e.g., L2 and L3 VPN services) on NFVI 230, and may also perform resource-related requests from one or more VNFMs 204, send configuration information to VNFMs 204, and collect VNF 208 state information. Additionally, NFVO202 may communicate with VIM 206 to enable allocation and/or reservation of resources and exchange configuration and status information for virtualized hardware resources. The VNFM 204 may manage one or more VNFs 208. VNFM 204 may perform various management functions such as instantiating, updating, querying, scaling, and/or terminating VNF 208, etc. VIM 206 may perform functions for resource management, such as managing allocation of infrastructure resources (e.g., adding resources to virtual containers) and operational functions (e.g., collecting NFVI fault information). The VNFM 204 and VIM 206 may communicate with each other for resource allocation and exchange configuration and status information for virtualized hardware resources.

The NFVI 230 includes hardware resources, software resources, or a combination of both to complete the deployment of the virtualized environment. In other words, the hardware resources and virtualization layer are used to provide virtualized resources, e.g., as virtual machines and other forms of virtual containers, for VNF 208. The hardware resources include computing hardware 212, storage hardware 214, and network hardware 216. The computing hardware 212 may be commercially available hardware and/or custom hardware to provide processing and computing resources. The storage hardware 214 may be storage capacity provided within a network or storage capacity residing within the storage hardware 214 itself (local storage located within a server). In one implementation, the resources of the computing hardware 212 and the storage hardware 214 may be pooled together. Network hardware 216 may be a switch, router, and/or any other network device configured with switching functionality. Network hardware 216 may span multiple domains and may include multiple networks interconnected by one or more transport networks.

A virtualization layer within NFVI 230 may abstract hardware resources from the physical layer and decouple VNF 208 in order to provide virtualized resources to VNF 208. The virtual resource layer includes virtual compute 210, virtual memory 218, and virtual network 220. Virtual computing 210 and virtual storage 218 may be provided to VNF 208 in the form of virtual machines, and/or other virtual containers. For example, one or more VNFs 208 may be deployed on one Virtual Machine (VM). The virtualization layer abstracts the network hardware 216 to form a virtual network 220, and the virtual network 220 may include Virtual Switches (VS) that are used to provide connections between virtual machines and other virtual machines. In addition, the transport network in the network hardware 216 may be virtualized using a centralized control plane and a separate forwarding plane (e.g., a software defined network). As shown in fig. 4, VNFM 204 may interact with VNF 208 and EM 222 to manage the VNF's lifecycle and exchange configuration and status information. VNF 208 may be configured to virtualize at least one network function performed by one physical network device. For example, in one implementation, the VNF 208 may be configured to provide functions provided by different network elements in the IMS network, such as a proxy-call session control function (P-scff), a serving-call session control function (S-CSCF), or a network function of a Home Subscriber Server (HSS), etc. EM 222 is configured to manage one or more VNFs 208.

The integrator or the operator plans the network and presents the result of the network planning in an NS information model descriptor (NSD). The NSD is put on shelf (on-board) to the NFVO, and the network planning result described by the NSD is instantiated into an NS instance as required. The basic components of the NS are shown in fig. 5, where fig. 5 is a structural view of the NS in the embodiment of the present application, the NS includes a VNF, a Virtual Link (VL), and a Connection Point (CP), VNF1 is connected to VNFs in other NS through VL1, VNF1 is connected to VNF3 through VL3, VNF1 is connected to VNF2 through VL2, VNF2 is connected to VNF3 and VNF1 through VL2, VNF3 is connected to VNF2 through VL2, VNF3 is connected to VNF1 through VL3, and VNF3 is connected to VNFs in other NS through VL 4.

Fig. 6 is a schematic structural diagram of an NFVO according to an embodiment of the present application, where the NFVO300 may have relatively large differences due to different configurations or performances, and may include one or more Central Processing Units (CPUs) 322 (e.g., one or more processors) and a memory 332, and one or more storage media 330 (e.g., one or more mass storage devices) for storing applications 342 or data 344. Memory 332 and storage media 330 may be, among other things, transient storage or persistent storage. The program stored on storage medium 330 may include one or more modules (not shown), each of which may include a sequence of instructions operating on the NFVO. Still further, central processor 322 may be configured to communicate with storage medium 330 to execute a series of instruction operations in storage medium 330 on NFVO 300.

NFVO300 may also include one or more power supplies 326, one or more wired or wireless network interfaces 350, one or more input-output interfaces 358, and/or one or more operating systems 341, such as Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, etc.

The steps performed by NFVO in the following examples may be based on the NFVO structure shown in fig. 6. The NFVO functions mainly to implement NS lifecycle management (such as deployment, capacity expansion, capacity reduction, offline, and the like) in an operator domain, and NFV infrastructure (NFVI) resource orchestration and policy management. The NFVO can decompose the requirements on each VNF according to the NSD, and cooperate with the VNFM to realize the deployment of the VNF.

For the convenience of understanding, the following will use two embodiments to describe the resource processing method in detail, specifically:

in the first embodiment, resources are reserved;

referring to fig. 7, fig. 7 is a schematic diagram of an embodiment of a method for resource processing in an embodiment of the present application, the method for resource processing is applied to a resource processing system, the resource processing system includes a first NFVO and a second NFVO, and the embodiment of the method for resource processing in the embodiment of the present application includes:

401. a first NFVO receives an instantiation request of a network service;

in this embodiment, the OSS or BSS sends an instantiation request of the composite NS to the first NFVO. The OSS and the BSS are integrated support systems of telecommunication operators, the BSS usually refers to charging, settlement, accounting, customer service, business and other systems, and the OSS can maintain interaction between virtualized application and a scheduler besides the traditional management function.

It is understood that the first NFVO is the top NFVO, the second NFVO is the lower NFVO, the first NFVO is responsible for orchestration and management of composite NS, and the second NFVO is responsible for orchestration and management of nested NS.

The first NFVO belongs to one MANO and also includes a VIM, and the second NFVO belongs to another MANO, which also includes another VIM. In general, there are a plurality of second NFVOs, the number of the second NFVOs is not limited in this application, and the second NFVOs may be in a parallel relationship or a top-bottom relationship, but all the second NFVOs belong to the lower NFVO of the first NFVO.

402. The first NFVO reserves resources required by the first VNF and the first VL according to the instantiation request;

in this embodiment, the first NFVO may establish a first mapping relationship according to the instantiation request, where the first mapping relationship includes a correspondence between a composite NS resource identifier, a first resource group identifier, and a first resource reservation identifier, where the first resource group identifier is used to identify the first VNF and the first VL, and the first resource reservation identifier is used to identify resources reserved for the first VNF and the first VL.

403. The first NFVO sends a resource reservation request to the second NFVO;

in this embodiment, the first NFVO sends a resource reservation request to the second NFVO according to the received instantiation request, so as to inform the second NFVO that a certain virtual resource needs to be reserved for the instantiation operation.

404. The second NFVO reserves resources required by the second VNF and the second VL according to the resource reservation request;

in this embodiment, the second NFVO reserves corresponding virtual resources for the second VNF and the second VL that are required for instantiation according to the resource reservation request. One possible way is to directly carry the identifier of the second VNF and the identifier of the second VL in the resource reservation request, and determine which resources need to be reserved through the identifiers. Another possible way is to reserve resources by establishing a mapping relationship.

Specifically, the second NFVO establishes a second mapping relationship according to the resource reservation request, where the second mapping relationship includes a correspondence between a composite NS resource identifier, a second resource group identifier, and a second resource reservation identifier, the composite NS resource identifier is used to identify an instance of the composite NS, the second resource group identifier is used to identify a second VNF and a second VL, and the second resource reservation identifier is used to identify resources reserved for the second VNF and the second VL.

405. If the resource reservation of the first NFVO and the second NFVO is successful, the first NFVO allocates the reserved resources to the first VNF and the first VL;

in this embodiment, the first NFVO acquires the resource reservation identifier from a third mapping relationship, where the third mapping relationship is used to indicate a resource reservation state of each virtual resource, please refer to table 1, and table 1 is an illustration of the third mapping relationship.

TABLE 1

NFVO identification	Whether resource reservation is timed out	Whether resource reservation is sufficient
			NFVO 1	0	1
NFVO 2	1	1
			NFVO 3	0	0
NFVO 4	1	1
			NFVO 5	0	0

It is understood that table 1 is only an illustration of the third mapping relationship, and the NFVO id is used to represent different NFVOs, "0" represents "no" and "1" represents "yes". If the resource reservation identifier indicates that the current resource reservation state is resource reservation overtime and/or insufficient, the first NFVO determines that the resource reservation of the current virtual resource fails, otherwise, if the resource reservation identifier indicates that the current resource reservation state is resource reservation completed and the resource reservation is sufficient, the first NFVO determines that the resource reservation of the virtual resource succeeds.

If the resource reservation is successful, the first NFVO allocates virtual resources to the first VNF and the first VL on the reserved resources, specifically, the first NFVO determines the first VNF and the first VL according to the composite NS resource identifier and the first mapping relationship, and allocates corresponding virtual resources to the first VNF and the first VL on the reserved resources.

406. The first NFVO sends an instantiation request to the second NFVO;

in this embodiment, after receiving the instantiation request, the first NFVO sends the instantiation request to the second NFVO.

407. The second NFVO allocates the reserved resources to the second VNF and the second VL according to the instantiation request.

In this embodiment, the second NFVO may allocate virtual resources on the reserved resources for the first VNF and the first VL according to the instantiation request. Specifically, the instantiation request carries the composite NS resource identifier, so that the second NFVO can determine the first VNF and the first VL according to the composite NS resource identifier and the first mapping relationship, and can allocate corresponding virtual resources to the first VNF and the first VL on the reserved resources.

Optionally, on the basis of the embodiment corresponding to fig. 7, in a first optional embodiment of the method for resource processing provided in the embodiment of the present application, if the reservation of resources of the first NFVO and/or the second NFVO fails, the first NFVO releases resources reserved for the first VNF and the first VL according to the composite NS resource identifier and the first mapping relationship;

the first NFVO sends a resource release request to a second NFVO according to a third mapping relation, wherein the third mapping relation includes a composite NS resource identifier, a second NFVO identifier and a resource reservation identifier, the second NFVO is used for identifying the second NFVO, the resource reservation identifier is used for identifying a resource reservation state, the resource release request carries the composite NS resource identifier, and the resource release request is used for indicating the second NFVO to release resources reserved for the second VNF and the second VL according to the composite NS resource identifier and the second mapping relation.

In this embodiment, when the virtual resource reservation of the first NFVO and/or the second NFVO fails, the first NFVO determines, from the first mapping relationship, resources reserved for the first VNF and the first VL in a table lookup manner. Referring to fig. 2, table 2 shows an example of the first mapping relationship.

TABLE 2

Composite NS resource identification	Resource group identification	Resource reservation identification
			NS 1	1	A
NS 1	2	B
			NS 1	3	C
NS 1	4	D
			NS 2	1	A
NS 2	2	B
			NS 2	3	C

It is understood that table 2 is only an illustration of the first mapping relationship and should not constitute a limitation of the first mapping relationship. The first NFVO determines the composite NS identifier according to the first mapping relationship, then finds a corresponding resource group identifier, obtains a resource reservation identifier corresponding to the resource group identifier, and finally releases a virtual resource (i.e., a resource reserved by the first VNF and the first VL) corresponding to the resource reservation identifier.

The first NFVO sends a resource release request to the second NFVO according to the third mapping relationship, where the resource release request carries the composite NS resource identifier, please refer to table 3, where table 3 is another illustration of the third mapping relationship, and it is assumed that the composite NS resource identifier is "NS 1".

TABLE 3

Composite NS resource identification	Second NFVO identity	Whether resource reservation is timed out	Whether resource reservation is sufficient
				NS 1	NFVO 1	0	1
NS 1	NFVO 2	1	1
				NS 1	NFVO 3	0	0
NS 1	NFVO 4	1	1

It is understood that table 3 is only an illustration of the third mapping relationship, where the second NFVO id is used to represent a different second NFVO, "0" represents "no" and "1" represents "yes". First, the first NFVO determines, according to the third mapping relationship, second NFVO identifiers corresponding to each second NFVO, and determines, through the resource reservation identifiers, the resource reservation states of the second NFVOs, and if the resource reservation of the first NFVO and/or the second NFVO fails, the first NFVO sends a resource release request to the second NFVO. Referring to fig. 4, table 4 shows an example of the second mapping relationship.

TABLE 4

It is understood that table 4 is only an illustration of the second mapping relationship and should not constitute a limitation of the second mapping relationship. The second NFVO parses the resource release request to determine the composite NS resource identifier, then finds a corresponding resource group identifier according to the composite NS resource identifier and the second mapping relationship, obtains a resource reservation identifier corresponding to the resource group identifier, and finally releases the virtual resource (i.e., the resource reserved by the second VNF and the second VL) corresponding to the resource reservation identifier.

Secondly, in the embodiment of the present application, as long as there is a failure in resource reservation of one domain, all domains release the reserved virtual resources and do not perform the lifecycle management operation of the composite NS any more. By adopting the mode, through the cross-domain resource reservation, the problem that the instantiation operation of the composite NS fails due to insufficient resources of a certain domain is solved, and then the problem of operation rollback of a plurality of domains is solved.

For convenience of understanding, a detailed description is given below of a resource processing method in the present application in a specific application scenario, please refer to fig. 8, where fig. 8 is a schematic flowchart of a resource reservation process performed by taking total resources in a domain as an object in the application scenario, specifically:

in step a1, NFVO-1 receives an instantiation request of the composite NS sent by the OSS or BSS, where the instantiation request may include a plurality of parameters, such as (composite) nsInstanceId and flavourld, where the (composite) nsInstanceId is an identifier of the composite network service instance and the flavourld is an identifier of a network topology.

In step a2, NFVO-1 obtains the corresponding (composite) NSD through (composite) nsInstanceId or NsdId, analyzes the (composite) NSD, and obtains VNFD, VLD, NsdId and transdomain nestedid belonging to the NFVO-1 local domain. And determining the flavourd information of VNFD, VLD and nested NSD of each object according to the flavourd. NFVO-1 creates a resource identifier with the composite NS instance as an object, wherein the resource identifier is a composite NS resource ID, is used for indexing information related to the composite NS instance resource, and can be only an instance for a tenant to uniquely identify the composite NS.

In step a3, NFVO-1 parses VNFD, VLD, NsdId and transdomain nestedld of the present domain according to each object template (VNFD, VLD and nestedsd) and the flavourd in the present domain to obtain total resources required in the present domain, and creates a resource group ID for the composite NS for identifying the reserved resources in the present domain in the composite NS.

In step A4, NFVO-1 uses resource group ID to reserve resources for VIM-1 as composite NS, so as to obtain resource reservation ID.

In step a5, after VIM-1 successfully reserves, a resource reservation ID is returned, and the resource reservation ID is used by the subsequent NFVO-1 when applying for creating resources from VIM-1.

In step a6, NFVO-1 needs to create a mapping between 3 IDs (i.e., a mapping between a compound NS resource ID, a resource group ID of a compound NS object within a local domain, and a reserved resource ID of a compound NS object within a local domain). By this time, the resource reservation in the local domain is completed, and the resource reservation across the domains is performed from step a 7.

In step a7, NFVO-1 sends a resource reservation request to NFVO-2 for resource reservation for the composite NS, where the parameters included in the resource reservation request include a composite NS resource ID, a nested NsdId, and a (nested NS) flavourId, and it is understood that the resource reservation request may also include other parameters, such as an affinity requirement parameter and a location requirement parameter.

In step A8, NFVO-2 obtains and parses the nested NSD according to the nested nsdld to obtain VNFD, VLD, and nestedndsid belonging to the domain, and parses each object (VNF, VL, and nestedndsd) of the domain according to the flavourld of the nested NS to obtain the total resources required by the nested NS in the domain, and creates a resource group ID for the nested NS for identifying the resources reserved by the nested NS.

In step a9, NFVO-2 performs resource reservation for the nested NS to VIM-2 with a resource group ID to obtain a resource reservation ID.

In step a10, after VIM-2 is successfully reserved, a resource reservation ID is returned, and the resource reservation ID is used by the subsequent NFVO-2 when applying for creating resources from VIM-2.

In step a11, NFVO-2 needs to create a mapping relationship between 3 IDs (i.e. a mapping relationship between the identity of a composite NS resource, the resource group ID of an object (nested NS, etc. within this domain), and the reserved resource ID of an object (nested NS, etc. within this domain)).

It can be understood that the mapping tables established by NFVO-1 and NFVO-2 need to have global uniqueness, and the composite NS resource ID, the object resource group IDs, and the object reserved resource IDs can both ensure uniqueness within their own domain. When the composite NS resource ID can ensure the global uniqueness, the three IDs are combined; when the composite NS resource ID can only guarantee the uniqueness of the MANO-1 domain, the information of NFVO-1 or MANO-1 can be added in the mapping table, and the global uniqueness is guaranteed through the (NFVO-1 or MANO-1) composite NS resource ID; when multiple nested NS or nested (NS + VNF) combinations exist in the same domain in a composite NS, information about the identification of the nested NS and/or VNF resources may be added to the mapping.

In step A12, the resource reservation is successful, and NFVO-2 returns a composite NS reservation resource response to NFVO-1.

It should be noted that steps A3 through A6 are the processing flows in the MANO-1 domain, steps A7 through A12 are the processing flows in the MANO-2 domain, and the processing flows in the two domains can be performed synchronously or asynchronously, which is not limited herein. In addition, the reserved resource response may or may not carry the ID of each object reserved resource, because each domain manages its own resources and does not need to be perceived by other domains.

In step a13, assuming that the resource reservation of a domain fails, all reserved resources are released and the composite NS instantiation is considered to fail. At this time, NFVO-1 sends a request for releasing reserved resources to VIM-1, where the request for releasing reserved resources includes the ID of each object reserved resources in the local domain.

In step A14, after the release is completed, VIM-1 returns a reserved resource release response to NFVO-1.

In step a15, NFVO-1 sends a request for releasing reserved resources to NFVO-2, the optional parameter includes a composite NS resource ID, and when the composite NS reserved resource response carries the reserved resource ID of the nested NS object, the request for releasing reserved resources may carry the reserved resource ID of the nested NS object.

In step a16, NFVO-2 searches the mapping table established in step a11 according to the composite NS resource identifier in the reserved resource release request, and determines the reserved resource ID of the corresponding nested NS object.

In step A17, NFVO-2 sends a request for release of reserved resources to VIM-2.

In step A18, after VIM-2 release is completed, VIM-2 returns a reserved resource release response to NFVO-1.

In step a19, NFVO-1 simultaneously sends a composite NS instantiation failure response to the OSS, and after releasing the resources, both NFVO-1 and NFVO-2 need to update the corresponding mapping tables.

In step a20, when the resource reservation of all domains is successful, an instantiation operation is initiated. Specifically NFVO-1, initiates instantiation of objects within the domain. When NFVO-1 receives the permission request, it determines that the object corresponding to the instantiation request is a composite NS, obtains the resource group ID and the resource reservation ID of the object in the mapping table in step A6, does not execute the actions from step A2 to step A4 any more, and returns the obtained resource reservation ID after the instantiation is authorized. The VNFM-1 performs a resource allocation operation with this resource reservation ID.

Of course, the reserved resource ID may also be carried in the instantiation request sent by NFVO-1 to VNFM-1, and VNFM-1 no longer needs to request permission for the resource, as long as the operation is authorized.

In step a21, NFVO-1 requests to create a nested NS instance ID from NFVO-2, which may include the parameter nested NsdId.

In step A22, NFVO-2 returns the instance ID of the nested NS, such as the nested nsInstanceId.

In step a23, NFVO-1 requests NFVO-2 to perform nested NS instantiation, where the request needs to include nested nsInstanceId and composite NS resource identifier.

In step A24, NFVO-2 initiates instantiation of a nested NS within the domain where it is located, which is broken down into instantiations of VNFs and VLs. When NFVO-2 receives the permission request of VNFM-2 in step a1, it determines that the object corresponding to the permission request is a child object of the nested NS, obtains the resource group ID and the resource reservation ID in the mapping table of the nested NS object in step a11, does not perform the actions from step a2 to step a4 any more, and returns the obtained resource reservation ID after authorizing the permission request. VNFM-2 performs resource allocation operations with this resource reservation ID.

Of course, NFVO-2 may also carry the reserved resource ID in the instantiation request sent to VNFM-2, and VNFM-2 no longer needs to request permission authorization for the resource, as long as the operation is authorized.

In step A25, NFVO-2 returns a nested NS instantiation response to NFVO-1.

In step A26, NFVO-1 returns a composite NS instantiation success response to the OSS.

Optionally, on the basis of the first embodiment shown in fig. 7 and corresponding to fig. 7, in a second optional embodiment of the method for processing resources provided in this embodiment of the present application, the first resource group identifier includes multiple first sub-resource group identifiers, where the first sub-resource group identifier is used to identify the first sub-VNF and the first sub-VL, the first resource reservation identifier includes multiple first sub-resource reservation identifiers, the first sub-resource reservation identifier is used to identify resources reserved for the first sub-VNF and the first sub-VL, the first VNF includes multiple first sub-VNFs, and the first VL includes multiple first sub-VLs;

the second resource group identifier comprises a plurality of second sub-resource group identifiers, the second sub-resource group identifiers are used for identifying a second sub-VNF and a second sub-VL, the second resource reservation identifier comprises a plurality of second sub-resource reservation identifiers, the second sub-resource reservation identifiers are used for identifying resources reserved for the second sub-VNF and the second sub-VL, the second VNF comprises a plurality of second sub-VNFs, and the second VL comprises a plurality of second sub-VLs;

the first NFVO establishes a first mapping relationship according to the instantiation request, which may include:

the first NFVO creates a composite NS resource identifier according to the instantiation request;

the first NFVO establishes a first mapping relation according to the composite NS resource identifier, the plurality of first sub-resource group identifiers and the plurality of first sub-resource reservation identifiers;

the sending, by the first NFVO, the resource reservation request to the second NFVO may include:

the first NFVO sends a resource reservation request to a second NFVO, wherein the resource reservation request is used for indicating the second NFVO to establish a second mapping relationship, and the second mapping relationship comprises a corresponding relationship among the composite NS resource identifier, the plurality of second sub-resource group identifiers and the plurality of second sub-resource reservation identifiers.

In this embodiment, for a virtual resource in a domain, a plurality of sub virtual resources may be used, for example, a total virtual resource of a domain may be used to call a processor, and each sub virtual resource may be used to call a different function in the processor. Each sub-virtual resource also has a sub-VNF and a sub-VL, and thus it can be seen that the first resource group identifier includes a plurality of first sub-resource group identifiers, the first resource reservation identifier includes a plurality of first sub-resource reservation identifiers, the second resource group identifier may also include a plurality of second sub-resource group identifiers, and the second resource reservation identifier includes a plurality of second sub-resource reservation identifiers.

Then, after receiving the instantiation request of the network service, the first NFVO may parse the instantiation request to create and obtain the composite NS resource identifier, and then establish the first mapping relationship according to the composite NS resource identifier, the plurality of first sub-resource group identifiers, and the plurality of first sub-resource reservation identifiers. Similarly, the second NFVO receives the resource reservation request sent by the first NFVO, and then establishes a second mapping relationship according to the composite NS resource identifier, the plurality of second sub-resource group identifiers, and the plurality of second sub-resource reservation identifiers.

Similar to steps 405 to 407 in the embodiment corresponding to fig. 7, the first NFVO may obtain the resource reservation identifier from a third mapping relationship, where the third mapping relationship is used to indicate a resource reservation status of each virtual resource. If the resource reservation of the first NFVO and/or the second NFVO fails, the first NFVO may release the resources reserved for the first sub-VNF and the first sub-VL according to the composite NS resource identifier and the first mapping relationship, the first NFVO sends a resource release request to the second NFVO according to the third mapping relationship, and the second NFVO releases the resources already reserved for the second sub-VNF and the second sub-VL or releases the resources currently reserved for the second sub-VNF and the second sub-VL according to the composite NS resource identifier and the second mapping relationship. On the contrary, if the virtual resources of the first NFVO and the second NFVO are both successfully reserved, the first NFVO determines the first sub-VNF and the first sub-VL according to the composite NS resource identifier and the first mapping relationship, allocates the virtual resources on the reserved resources for the first sub-VNF and the first sub-VL, and then the first NFVO sends an instantiation request to the second NFVO, where the instantiation request carries the composite NS resource identifier, and the second NFVO determines the second sub-VNF and the second sub-VL according to the composite NS resource identifier and the second mapping relationship, and allocates the virtual resources on the reserved resources for the second sub-VNF and the second sub-VL.

In the embodiment of the present application, it is introduced that resources may be respectively reserved for each sub-object in a domain, and a mapping relationship is established according to each sub-object, so that feasibility and operability of establishing the mapping relationship are improved.

For convenience of understanding, the following describes another resource processing method in the present application in a specific application scenario in detail, please refer to fig. 9, and fig. 9 is a schematic flow chart illustrating resource reservation for each sub-object in a domain in the application scenario of the present application, specifically:

in step B1, NFVO-1 receives an instantiation request of the composite NS sent by the OSS or BSS, where the instantiation request may include a plurality of parameters, such as (composite) nsInstanceId and flavourld, where the (composite) nsInstanceId is a composite network service instance identifier and the flavourld is a network topology identifier.

In step B2, NFVO-1 obtains the corresponding (composite) NSD through (composite) nsInstanceId or NsdId, and analyzes the (composite) NSD to obtain VNFD, VLD, NsdId belonging to the NFVO-1 local domain and mesdnsdid of the cross-domain. And determining the flavourd information of VNFD, VLD and nested NSD of each object according to the flavourd. NFVO-1 creates a resource identifier with the composite NS instance as an object, wherein the resource identifier is a composite NS resource ID, is used for indexing information related to the composite NS instance resource, and can be only an instance for a tenant to uniquely identify the composite NS.

In step B3, NFVO-1 parses VNFD, VLD, NsdId and transdomain nestedld of the local domain according to each object template (VNFD/VLD/nestedsd) and the flavourd in the local domain, obtains resources required by each object in the local domain, and creates resource group IDs for each object, respectively, for identifying resources reserved by each object.

In step B4, NFVO-1 performs resource reservation for each object to VIM-1 by using each resource group ID, so as to obtain a resource reservation ID.

In step B5, after VIM-1 successfully reserves, it sends a reservation response, i.e. returns a resource reservation ID, and the subsequent NFVO-1 uses the resource reservation ID when applying for creating resources to VIM-1.

In step B6, NFVO-1 needs to create a mapping relationship between 3 IDs (i.e. composite NS resource ID, resource group ID of object (VNF, VL, and nestnds, etc. within this domain), and reserved resource ID of object (VNF, VL, and nestnds, etc. within this domain)). By this time, the resource reservation in the local domain is completed, and the resource reservation across the domains is performed from step B7.

In step B7, NFVO-1 sends a request for reserving resources to NFVO-2 for resource reservation for the nested NS, where the parameters included in the request for reserving resources include a composite NS resource identifier, nested NsdId, and (nested NS) flavourId, and the optional parameters include: other parameters may also be included, such as affinity requirement parameters and location requirement parameters.

In step B8, NFVO-2 obtains and parses the nested NSD according to the nested nsdld to obtain VNFD, VLD, and nestedndsid belonging to the domain, and parses the objects (VNF, VL, and nestedndsd) of the domain according to the flavourld of the nested NS to obtain the resources required by the objects in the domain, and creates resource group IDs for the objects respectively for identifying the resources reserved by each object.

In step B9, NFVO-2 performs resource reservation for each object to VIM-2 by using each resource group ID, to obtain a resource reservation ID.

In step B10, after VIM-2 is successfully reserved, a resource reservation ID is returned, and the resource reservation ID is used by the subsequent NFVO-2 when applying for creating resources from VIM-2.

In step B11, NFVO-2 needs to create a mapping between 3 IDs (i.e. a mapping between the composite NS resource identity, the resource group ID of the (intra-domain VNF, VL and nestdns) object and the reserved resource ID of the (intra-domain VNF, VL and nestdns) object).

In step B12, the resource reservation is successful, and NFVO-2 returns a nested NS reservation resource response to NFVO-1.

It should be noted that steps B3 through B6 are the processing flows in the MANO-1 domain, steps B7 through B12 are the processing flows in the MANO-2 domain, and the processing flows in the two domains may be performed synchronously or asynchronously, which is not limited herein. In addition, the reserved resource response may or may not carry the ID of each object reserved resource, because each domain manages its own resources and does not need to be perceived by other domains.

In step B13, assuming that the resource reservation of a domain fails, all reserved resources are released and the composite NS instantiation is considered to fail. At this time, NFVO-1 sends a request for releasing reserved resources to VIM-1, where the request for releasing reserved resources includes the reserved resource ID of each object in the local domain.

In step B14, after the release is completed, VIM-1 returns a reserved resource release response to NFVO-1.

In step B15, NFVO-1 sends a request for releasing reserved resources to NFVO-2, where the optional parameters in the request for releasing reserved resources include a composite NS resource ID, and when the composite NS reserved resource response carries the reserved resource ID of the nested NS object, the request for releasing reserved resources may carry the reserved resource ID of the nested NS object.

In step B16, NFVO-2 searches the mapping table established in step B11 according to the composite NS resource identifier in the request for releasing reserved resources, and determines the ID of each corresponding object reserved resource.

In step B17, NFVO-2 sends a request for release of reserved resources to VIM-2.

In step B18, after the VIM-2 release is completed, a reserved resource release response is returned to NFVO-1.

In step B19, NFVO-1 sends a composite NS instantiation failure response to the OSS at the same time, and after releasing the resources, NFVO-1 and NFVO-2 both need to update the corresponding mapping tables.

In step B20, when the resource reservation of all domains is successful, an instantiation operation is initiated. Specifically NFVO-1, initiates instantiation of objects within the domain. When NFVO-1 receives the permission request of VNFM-1, it determines the object corresponding to the instantiation request, obtains the resource group ID and resource reservation ID of the object in the mapping table in step B6, does not execute the actions from step B2 to step B4 any more, and returns the obtained resource reservation ID after permission of the instantiation operation. The VNFM-1 performs a resource allocation operation with this resource reservation ID.

In step B21, NFVO-1 requests to create a nested NS instance ID from NFVO-2, which may contain the parameter nested NsdId.

In step B22, NFVO-2 returns the instance ID of the nested NS, such as the nested nsInstanceId.

In step B23, NFVO-1 requests NFVO-2 for nested NS instantiation, which needs to include the nested nsInstanceId and the composite NS resource ID.

In step B24, when performing resource reservation, NFVO-2 adopts NFVO-1 as the VNF in this domain to perform resource reservation. The nested NS instantiation within the domain where NFVO-2 initiates is broken down into instantiations of VNF and VL. When the NFVO-2 receives the permission request of the VNFM-2, the object corresponding to the permission request is determined, the resource group ID and the resource reservation ID in the mapping table of the object in B11 are obtained, the actions from step B2 to step B4 are no longer performed, and the obtained resource reservation ID is returned after the permission request is authorized. VNFM-2 performs resource allocation operations with this resource reservation ID.

In step B25, NFVO-2 returns a nested NS instantiation response to NFVO-1.

In step B26, NFVO-1 returns a composite NS instantiation success response to the OSS.

It is understood that the two manners described in the application scenario corresponding to fig. 8 and the application scenario corresponding to fig. 9 may be used in different domains, and the same manner is not necessarily used in each domain.

Optionally, on the basis of the first or second embodiment corresponding to fig. 7 and fig. 7, in a third optional embodiment of the method for processing resources provided in this embodiment of the present application, after the first NFVO sends the resource release request to the second NFVO according to the third mapping relationship, the method may further include:

the first NFVO updates the first mapping relation;

after the first NFVO sends the instantiation request to the second NFVO, the method may further include:

if the first NFVO receives an instantiation success message sent by the second NFVO, the first NFVO determines that the nesting NS of the second NFVO is successfully instantiated;

if the instantiation of the second VNF and the second VL of the first NFVO is successful, the first NFVO determines that the instantiation of the composite NS is successful.

In this embodiment, after releasing the virtual resources, the first NFVO and the second NFVO update the mapping relationships respectively maintained, for example, after the first VNF and the first VL in the first NFVO are released, the first NFVO resets the first mapping relationship, that is, the identifier of the first VNF and the identifier of the first VL are cleared. If the first NFVO receives the instantiation success message sent by the second NFVO, the first NFVO determines that the instantiation of the nested NS of the second NFVO is successful, and if the instantiation of both the first VNF and the first VL of the first NFVO is successful, the first NFVO determines that the instantiation of the composite NS is successful, and thus, it is determined that the instantiation of the cross-domain NS is successful.

After the first NFVO determines that the cross-domain NS instantiation is successful, if the composite NS needs to expand or contract, the virtual resources also need to synchronously expand or contract. Wherein, for the capacity reduction operation, the resource is updated by updating the reserved resource after the capacity reduction of the object is completed. For the capacity expansion operation, the resource is updated before the object capacity expansion operation.

First, the first NFVO receives the composite NS update request or the composite NS capacity expansion and reduction request, and then the first NFVO sends the capacity expansion and reduction request to the second NFVO according to the composite NS update request or the composite NS capacity expansion and reduction request. And the second NFVO performs resource capacity expansion or resource capacity reduction operation on the reserved (or quota) resources according to the capacity expansion and reduction request, and obtains the first resource to be updated. The first resource to be updated is used to instruct the second NFVO to update (i.e., expand or contract) the resources reserved by the second VNF and the second VL. Likewise, the first NFVO determines a second resource to be updated according to the composite NS update request or the composite NS scaling request, and updates (i.e., scales or scales) the resources reserved by the first VNF and the first VL according to the second resource to be updated.

The above describes how to perform the capacity expansion and reduction operation on the resource, and the following describes how to recycle the resource.

If the first NFVO receives the composite NS instantiation completion request, the first NFVO releases resources reserved for the first VNF and the first VL according to the composite NS resource identifier and the first mapping relationship. In addition, the first NFVO may also send a resource release request to the second NFVO, where the resource release request carries the composite NS resource identifier, and the resource release request is used to instruct the second NFVO to release resources reserved for the second VNF and the second VL according to the composite NS resource identifier and the second mapping relationship.

Further, in the embodiment of the present application, after the composite NS is successfully instantiated, the virtual resource may be further updated according to the composite NS update request or the composite NS capacity expansion and reduction request, so that the virtual resource may be correspondingly adjusted according to different instantiation requirements, thereby improving the practicability and flexibility of the scheme. Meanwhile, after instantiation is completed, the reserved virtual resources can be released according to the mapping relation, and therefore the virtual resources can be vacated for subsequent instantiation operation, the virtual resources can be reused, and the practicability of the virtual resources is improved.

Embodiment two, resource quotas;

referring to fig. 10, fig. 10 is a schematic diagram of another embodiment of a method for resource processing in an embodiment of the present application, where the method for resource processing is applied to a resource processing system, and the resource processing system includes a first NFVO and a second NFVO, and the embodiment of the method for resource processing in the embodiment of the present application includes:

501. a first NFVO receives a resource quota request;

in this embodiment, first, the first NFVO receives a resource quota request of the composite NS, where the reserved resources generally refer to how many virtual resources are configured for instantiating the required virtual resources, and the quota resources are reserved for instantiating the virtual resources in advance, and the reserved virtual resources may be redundant.

502. The first NFVO configures required resources for the first VNF and the first VL according to the resource quota request;

in this embodiment, the first NFVO configures, according to the received resource quota request, the required virtual resources for the first VNF and the first VL. One possible configuration manner is to directly carry the identifier of the first VNF and the identifier of the second VL in the resource quota request, and determine which resources need to be configured through the identifiers. Another possible way is to configure the resources by establishing a mapping relationship.

Specifically, the first NFVO establishes a first mapping relationship according to the resource quota request, where the first mapping relationship includes a composite network service NS resource identifier and a first resource group identifier, the composite NS resource identifier is used to identify an instance of the composite NS, and the first resource group identifier is used to identify resource quotas of the first VNF and the first VL. And then, the first NFVO sends the resource quota request to a second NFVO, and the second NFVO establishes a second mapping relationship according to the second NFVO, where the second mapping relationship includes a composite NS resource identifier and a second resource group identifier, and the second resource group identifier is used to identify resource quotas of a second VNF and a second VL. The first NFVO may determine the first VNF and the first VL according to the composite NS resource identifier and the first mapping relationship, and allocate virtual resources on configured resources for the first VNF and the first VL.

The first NFVO sends an instantiation request to the second NFVO, and after receiving the instantiation request, the second NFVO may determine the second VNF and the second VL according to the composite NS resource identifier and the second mapping relationship, and allocate virtual resources on configured resources for the second VNF and the second VL.

It can be understood that the first mapping relationship and the second mapping relationship are similar to those described in the first embodiment, except that the first mapping relationship and the second mapping relationship in the second embodiment do not include the resource reservation identifier, and thus the details are not repeated herein.

503. A first NFVO sends a resource quota request to a second NFVO;

in this embodiment, a first NFVO sends a resource quota request to a second NFVO.

504. The second NFVO configures required resources for a second VNF and a second VL according to the resource quota request;

in this embodiment, the second NFVO determines, according to the resource quota request sent by the first NFVO, virtual resources that need to be configured for the second VNF and the second VL.

505. If the resource quotas of the first NFVO and the second NFVO are successful, the first NFVO allocates the reserved resources to the first VNF and the first VL;

in this embodiment, the first NFVO may obtain the resource reservation identifier from a third mapping relationship, where the third mapping relationship is used to indicate a resource reservation state of each virtual resource, and if the resource reservation identifier indicates that the current resource reservation state is resource reservation overtime and/or resource reservation insufficient, the first NFVO determines that resource reservation of the current virtual resource fails, otherwise, if the resource reservation identifier indicates that the current resource reservation state is resource reservation completed and resource reservation is sufficient, the first NFVO determines that resource reservation of the virtual resource succeeds.

506. The first NFVO sends an instantiation request to the second NFVO;

in this embodiment, the first NFVO further sends an instantiation request to the second NFVO.

507. And the second NFVO performs instantiation operation on the second VNF and the second VL quota resource according to the instantiation request.

In this embodiment, the second NFVO may allocate virtual resources on the configured resources for the second VNF and the second VL according to the instantiation request. Specifically, the instantiation request carries the composite NS resource identifier, so that the second NFVO can determine the second VNF and the second VL according to the composite NS resource identifier and the second mapping relationship, allocate corresponding virtual resources to the configured resources for the second VNF and the second VL, and finally perform instantiation operation on the virtual resources with a high quota according to the instantiation request.

In an embodiment of the present application, a method for resource processing is provided, where a first NFVO receives a resource quota request, then configures required resources for a first VNF and a first VL according to the resource quota request, and the NFVO sends the resource quota request to a second NFVO, where the resource quota request is used to indicate that the second NFVO configures the required resources for a second VNF and a second VL, and if the resource quota is successful, the first NFVO allocates virtual resources on the configured resources for the first VNF and the first VL, and finally the first NFVO sends an instantiation request to the second NFVO, where the instantiation request is used to indicate that the second NFVO allocates virtual resources on the configured resources for the second VNF and the second VL. In this way, the first NFVO may configure resources for the instantiation operation first, and instruct the second NFVO to also configure resources for the subsequent instantiation operation, so that it is possible to avoid that the NFVO causes all rollback of the operations that have been instantiated successfully or are being instantiated due to insufficient resources.

Optionally, on the basis of the embodiment corresponding to fig. 10, in a first optional embodiment of the method for resource processing provided in the embodiment of the present application, if the resource quota of the first NFVO and/or the second NFVO fails, the first NFVO releases the resource quota of the first VNF and the first VL according to the composite NS resource identifier and the first mapping relationship;

and the first NFVO sends a resource release request to the second NFVO, wherein the resource release request carries the composite NS resource identifier, and the resource release request is used for indicating the second NFVO to release the resource quotas of the second VNF and the second VL according to the composite NS resource identifier and the second mapping relation.

In this embodiment, when the virtual resource reservation of the first NFVO and/or the second NFVO fails, the first NFVO determines, from the first mapping relationship, resources reserved for the first VNF and the first VL in a table lookup manner. And the first NFVO determines a composite NS identifier according to the first mapping relation, then finds a corresponding resource group identifier, and finally releases a resource quota corresponding to the resource group identifier. And the first NFVO sends a resource release request to the second NFVO according to the third mapping relation, wherein the resource release request carries the composite NS resource identifier, similarly, the second NFVO determines the composite NS identifier according to the second mapping relation, then finds the corresponding resource group identifier, and finally releases the resource quota corresponding to the resource group identifier.

Secondly, in the embodiment of the present application, as long as a resource quota of one domain fails, all domains release the pre-configured virtual resource and do not perform the lifecycle management operation of the composite NS any more. By adopting the mode, the problem of the operation rollback of a plurality of domains is solved by solving the problem of the instantiation operation failure of the composite NS caused by insufficient resources of a certain domain through the cross-domain resource quota.

For convenience of understanding, another resource processing method in the present application is described in detail below with reference to a specific application scenario, please refer to fig. 11, where fig. 11 is a schematic flowchart of a resource quota setting process performed in the application scenario by taking total resources in a domain as an object, specifically:

in step C1, NFVO-1 receives a request for creating a resource quota for the composite NS from the OSS or BSS, where the necessary parameters include, but are not limited to, (composite) nsenstanceid, NsdId, and flavourd, where (composite) nsenstanceid is an identifier of the composite network service instance and flavourd is an identifier of a network topology. Meanwhile, the request for creating the resource quota for the composite NS may further include an affinity parameter and a location requirement parameter.

In step C2, NFVO-1 obtains the corresponding (composite) NSD through (composite) nsInstanceId and NsdId, and parses VNFD, VLD, (nested) NsdId and transdomain nested NsdId that belong to the domain. The flavourld information for each object (VNFD, VLD and nested NSD) is determined from the composite flavourld. And NFVO-1 creates a resource identification with the composite NS instance as an object.

In step C3, NFVO-1 parses each object template (VNFD, VLD, and nested NSD) and the flavourld in the present domain to obtain the total resources required in the present domain, and creates a resource group ID for the composite NS, where the resource group ID is used to identify the resource quota of the composite NS in the present domain.

In step C4, NFVO-1 creates a resource quota for the composite NS to VIM-1 with the resource group ID.

In step C5, after the VIM-1 successfully sets the quota, a response is returned to NFVO-1, and then NFVO-1 applies for creating a resource from VIM-1 using a resource group ID.

In step C6, NFVO-1 needs to create a mapping relationship between 2 IDs (i.e. the composite NS resource ID and the resource group ID of the composite NS object (within the local domain)), and NFVO-1 sends a notification to VNFM-1 that has subscribed to quota notification.

In step C7, NFVO-1 sends a resource quota request to NFVO-2, where the resource quota request includes the composite NS resource identifier, the nested NsdId, and the nested NS flavourld, and the resource quota request may further include an affinity requirement parameter and a location requirement parameter.

In step C8, NFVO-2 obtains and parses (nested) NSD according to (nested) NsdId to obtain VNFD, VLD and nested NsdId belonging to the domain, NFVO-2 parses (VNFD, VLD and nested NSD) each object of the domain according to the flavourd to obtain total resources required in the domain, and creates a resource group ID for the nested NS object to identify a resource quota required in the composite NS in the domain.

In step C9, NFVO-2 sets a resource quota for the VIM-2 with the resource group ID.

In step C10, after VIM-2 successfully reserves, a resource quota response is returned, and a resource group ID is used by the subsequent NFVO-2 when applying for creating a resource from VIM-2.

In step C11, NFVO-2 needs to create a mapping between 2 IDs (i.e. the composite NS resource identity and the resource group ID of the (nested NS) object), and NFVO-2 sends a notification to VNFM-2 that has subscribed to quota notifications.

In step C12, the NFVO-2 returns a resource quota response for creating resources to the NFVO-1, and optionally, each resource group ID may be carried in the resource quota response, or each object reservation resource ID may not be carried in the resource quota response, because each domain manages its own resources and does not need to be perceived by other domains.

Steps C3 through C6 are performed in the MANO-1 domain, steps C7 through C12 are performed in the MANO-2 domain, and the processing in both domains may be performed synchronously or asynchronously, which is not limited herein.

In step C13, assuming that the resource quota creation of a domain fails, all created resource quotas are released, and the composite NS instantiation is considered to fail. At this time, NFVO-1 sends a quota resource release request to VIM-1, where the quota resource release request includes a reserved resource ID of each object in the local domain.

In step C14, the release is completed, and VIM-1 returns a quota resource release response to NFVO-1.

In step C15, NFVO-1 sends a quota resource release request to NFVO-2, where the quota resource release request includes the composite NS resource ID.

In step C16, NFVO-2 searches the mapping table established in step C11 according to the composite NS resource identifier in the quota resource release request, and determines the resource group ID of the corresponding nested NS object.

In step C17, NFVO-2 sends a quota resource release request to VIM-2.

In step C18, after the release of VIM-2 is completed, VIM-2 returns a reserved resource release response to NFVO-1.

In step C19, NFVO-1 simultaneously sends a composite NS instantiation failure response to the OSS, and after releasing the resources, both NFVO-1 and NFVO-2 need to update the corresponding mapping tables.

In step C20, when the resource quotas of all domains are successful, an instantiation operation is initiated. Specifically NFVO-1, initiates instantiation of objects within the domain. The VNFM-1 can directly use the resource group ID to perform resource allocation operation when each object is instantiated according to the received subscription notification. The VNFM-1 can also actively inquire corresponding quota information to the NFVO-1, the NFVO-1 acquires a corresponding resource group ID according to the mapping table and informs the corresponding resource group ID to the VNFM-1, and the VNFM-1 applies for resources.

In step C21, NFVO-1 requests to create a nested NS instance ID from NFVO-2, which may include the parameter nested NsdId.

In step C22, NFVO-2 returns the instance ID of the nested NS, such as the nested nsInstanceId.

In step C23, NFVO-1 requests NFVO-2 to perform nested NS instantiation, where the request needs to include nested nsInstanceId and composite NS resource identifier.

In step C24, NFVO-2 initiates instantiation of nested NS within the domain, which is broken down into instantiations of VNF and VL. The VNFM-2 can directly use the resource group ID to perform resource allocation operation when each object is instantiated according to the received subscription notification. The VNFM-2 can also actively inquire corresponding quota information to the NFVO-2, the NFVO-2 acquires a corresponding resource group ID according to the mapping table and informs the corresponding resource group ID to the VNFM-2, and the VNFM-2 applies for resources.

In step C25, NFVO-2 returns a nested NS instantiation response to NFVO-1.

In step C26, NFVO-1 returns a composite NS instantiation success response to the OSS.

For convenience of understanding, another resource processing method in the present application is described in detail below with reference to a specific application scenario, please refer to fig. 12, where fig. 12 is a schematic flowchart of a resource quota setting process performed on each sub-object in a domain in the application scenario of the present application, specifically:

in step D1, NFVO-1 receives a request for creating a resource quota for the composite NS from the OSS or BSS, where the necessary parameters include, but are not limited to, (composite) nsenstanceid, NsdId, and flavourd, where (composite) nsenstanceid is an identifier of a composite network service instance, and flavourd is an identifier of a network topology. Meanwhile, the request for creating the resource quota for the composite NS may further include an affinity parameter and a location requirement parameter.

In step D2, NFVO-1 obtains the corresponding (composite) NSD from the (composite) nsInstanceId and NsdId, and parses VNFD, VLD, (nested) NsdId and transdomain nested NsdId that belong to the domain. The flavourld information for each object (VNFD, VLD and nested NSD) is determined from the composite flavourld. And NFVO-1 creates a resource identification with the composite NS instance as an object.

In step D3, NFVO-1 performs parsing according to each object template (VNFD, VLD, and nested NSD) and the flavourd in the domain to obtain resources required by each object in the domain, and creates a resource group ID for each object, where the resource group ID is used to identify a resource quota of each object in the domain.

In step D4, NFVO-1 creates resource quotas for each object to VIM-1 using the resource group ID.

In step D5, after the VIM-1 successfully sets the quota, a response is returned to NFVO-1, and then NFVO-1 applies for creating a resource from the VIM-1 by using a resource group ID.

In step D6, NFVO-1 needs to create a mapping relationship between 2 IDs (i.e. the composite NS resource ID and the resource group ID of each object (composite NS in this domain)), and NFVO-1 sends a notification to VNFM-1 that has subscribed to quota notification.

In step D7, NFVO-1 sends a resource quota request to NFVO-2, where the resource quota request includes the composite NS resource identifier, the nested NsdId, and the nested NS flavourld, and the resource quota request may also include an affinity requirement parameter and a location requirement parameter.

In step D8, NFVO-1 obtains and parses (nested) NSD according to (nested) NsdId to obtain VNFD, VLD and nested NsdId belonging to the local domain, NFVO-2 parses each sub-object of the local domain according to the flavourld of the nested NS to obtain the resource needed by each sub-object in the local domain, and creates a resource group ID for each sub-object, where the resource group ID is used to identify the resource quota needed in the local domain in each sub-object.

In step D9, NFVO-2 sets a resource quota for the VIM-2 with the resource group ID.

In step D10, after VIM-2 successfully reserves, a resource quota response is returned, and a resource group ID is used by the subsequent NFVO-2 when applying for creating a resource from VIM-2.

In step D11, NFVO-2 needs to create a mapping relationship between 2 IDs (i.e. the composite NS resource identity and the resource group ID of each child object), and NFVO-2 sends a notification to VNFM-2 that has subscribed to quota notification.

In step D12, the NFVO-2 returns a resource quota response for creating resources to the NFVO-1, and optionally, each resource group ID may be carried in the resource quota response, or each object reservation resource ID may not be carried in the resource quota response, because each domain manages its own resources and does not need to be perceived by other domains.

Steps D3 through D6 are performed in the MANO-1 domain, steps D7 through D12 are performed in the MANO-2 domain, and the processing in the two domains may be performed synchronously or asynchronously, which is not limited herein.

In step D13, assuming that the resource quota creation of a domain fails, all created resource quotas are released, and the composite NS instantiation is considered to fail. At this time, NFVO-1 sends a quota resource release request to VIM-1, where the quota resource release request includes reserved resource IDs of each child object in the local domain.

In step D14, after the release is completed, VIM-1 returns a quota resource release response to NFVO-1.

In step D15, NFVO-1 sends a quota resource release request to NFVO-2, where the quota resource release request includes the composite NS resource ID.

In step D16, the NFVO-2 searches the mapping table established in step D11 according to the composite NS resource identifier in the quota resource release request, and determines the resource group ID of each corresponding child object.

In step D17, NFVO-2 sends a quota resource release request to VIM-2.

In step D18, after the release of VIM-2 is completed, VIM-2 returns a reserved resource release response to NFVO-1.

In step D19, NFVO-1 sends a composite NS instantiation failure response to the OSS or BSS at the same time, and after releasing the resources, both NFVO-1 and NFVO-2 need to update the corresponding mapping tables.

In step D20, when the resource quotas of all domains are successful, an instantiation operation is initiated. Specifically NFVO-1, initiates instantiation of objects within the domain. The VNFM-1 can directly use the resource group ID to perform resource allocation operation when each object is instantiated according to the received subscription notification. The VNFM-1 can also actively inquire corresponding quota information to the NFVO-1, the NFVO-1 acquires a corresponding resource group ID according to the mapping table and informs the corresponding resource group ID to the VNFM-1, and the VNFM-1 applies for resources.

In step D21, NFVO-1 requests to create a nested NS instance ID from NFVO-2, which may include the parameter nested NsdId.

In step D22, NFVO-2 returns the instance ID of the nested NS, such as the nested nsInstanceId.

In step D23, NFVO-1 requests NFVO-2 to perform nested NS instantiation, where the request needs to include nested nsInstanceId and composite NS resource identifier.

In step D24, NFVO-2 initiates instantiation of nested NS within the domain, which is broken down into instantiations of VNF and VL. The VNFM-2 can directly perform resource allocation operation using the resource group ID when performing instantiation operation on each sub-object according to the subscription notification received before. The VNFM-2 can also actively inquire corresponding quota information to the NFVO-2, the NFVO-2 acquires a corresponding resource group ID according to the mapping table and informs the corresponding resource group ID to the VNFM-2, and the VNFM-2 applies for resources.

In step D25, NFVO-2 returns a nested NS instantiation response to NFVO-1.

In step D26, NFVO-1 returns a composite NS instantiation success response to the OSS.

In addition, for both the first embodiment and the second embodiment, resource updating and resource recycling can be performed, for convenience of understanding, another method for processing resources in the present application is described in detail below with reference to a specific application scenario, please refer to fig. 13, where fig. 13 is a schematic flow diagram illustrating resource updating and recycling in the application scenario of the present application, it can be understood that the flow takes a scaling capacity as an example, and does not distinguish whether a total resource is taken as an object or each sub-object is taken as an object, specifically:

in step E1, NFVO-1 receives a capacity expansion request of the composite NS sent by the OSS or BSS, where the capacity expansion request parameter includes (composite) nsenstanceid and a new flavourd, and the flavourd is a network topology identifier.

In step E2, the NFVO-1 obtains the new flavanoid of each object according to the new flavanoid of the composite NS, and analyzes the new flavanoid to obtain a new resource requirement.

In step E3, NFVO-1 sends a request for updating reserved resources to VIM-1.

In step E4, VIM-1 returns a reserved resource update response to NFVO-1.

In step E5, NFVO-1 sends a request for updating reserved resources to NFVO-2, and performs resource reservation updating for the composite NS, where the request for updating reserved resources includes the following parameters: the composite NS resource ID, nested NsdId, and the new flavourd of the (nested NS), in addition to which affinity requirement parameters and location requirement parameters, etc. may be included.

In step E6, NFVO-2 obtains the new flavanoid of each object through the new flavanoid of the nested NS, and may obtain a new resource requirement after parsing.

In step E7, NFVO-2 sends a reserved resource update request to VIM-2.

In step E8, VIM-2 returns a reserved resource update response to NFVO-2.

In step E9, NFVO-2 returns a reserved resource update response to NFVO-1.

The resource reservation is similar to the resource quota, and the new resource also needs to be resolved with reference to the new flavourd, and then the update operation is performed.

In step E10, the OSS or BSS sends a network service termination request to NFVO-1.

In step E11, after the instantiation of the composite NS objects is completed, the virtual resources may also be released.

In step E12, NFVO-1 sends a request for releasing reserved resources to VIM-1, where the request for releasing reserved resources includes the reserved resource ID of each object in the local domain.

In step E13, the VIM-1 release is completed, and the VIM-1 returns a reserved resource release response to the NFVO-1.

In step E14, NFVO-1 sends a request for releasing reserved resources to NFVO-2.

In step E15, the VIM-2 release is completed, and the VIM-2 returns a reserved resource release response to the NFVO-2.

In step E16, NFVO-2 returns a reserved resource release response to NFVO-1.

As described in detail below for an NFVO corresponding to an embodiment of the present application, where the NFVO is applied to a resource processing system, the resource processing system further includes a second NFVO, please refer to fig. 14, where an NFVO 60 in an embodiment of the present application includes:

a receiving module 601, configured to receive an instantiation request of an NS;

a reserving module 602, configured to reserve resources required by the first virtual network function VNF and the first virtual link VL according to the instantiation request received by the receiving module 601;

a sending module 603, configured to send a resource reservation request to the second NFVO, where the resource reservation request is used to instruct the second NFVO to reserve resources required by the second VNF and the second VL;

an allocating module 604, configured to, if the resource reservation of the first NFVO and the second NFVO is successful, the first NFVO allocates the reserved resources to the first VNF and the first VL reserved by the reserving module 602;

the sending module 603 is configured to send the instantiation request to the second NFVO, where the instantiation request is used to instruct the second NFVO to allocate the reserved resources to the second VNF and the second VL.

In this embodiment, a receiving module 601 receives an instantiation request of an NS, a reservation module 602 reserves resources required by a first virtual network function VNF and a first virtual link VL according to the instantiation request received by the receiving module 601, a sending module 603 sends a resource reservation request to the second NFVO, where the resource reservation request is used to indicate that the second NFVO reserves resources required by a second VNF and a second VL, if the resource reservation of the first NFVO and the second NFVO is successful, an allocating module 604 allocates reserved resources to the first VNF and the first VL reserved by the reservation module 602 by the first NFVO, and the sending module 603 sends the instantiation request to the second NFVO, where the instantiation request is used to indicate that the second NFVO allocates reserved resources to the second VNF and the second VL by the second NFVO.

In this embodiment, an NFVO is provided, that is, a first NFVO, first receives an instantiation request of a network service NS, then the first NFVO reserves resources required by a first VNF and a first VL according to the instantiation request, and then the first NFVO sends a resource reservation request to a second NFVO, where the resource reservation request is used to instruct the second NFVO to reserve resources required by a second VNF and a second VL, and if the resource reservation of the first NFVO and the second NFVO is successful, the first NFVO allocates the reserved resources to the first VNF and the first VL, and finally the first NFVO sends an instantiation request to the second NFVO, where the instantiation request is used to instruct the second NFVO to allocate the reserved resources to the second VNF and the second VL. With the adoption of the device, after the NFVO receives the instantiation request, resources can be reserved for the instantiation operation, and the second NFVO is indicated to reserve resources for the subsequent instantiation operation, so that the situation that the NFVO has successful instantiation or all operations in instantiation are returned due to insufficient resources can be avoided.

Optionally, on the basis of the embodiment corresponding to fig. 14, in another embodiment of the NFVO 60 provided in this embodiment of the present application, the reservation module 602 is specifically configured to establish a first mapping relationship according to the instantiation request, where the first mapping relationship includes a correspondence relationship among the composite NS resource identifier, a first resource group identifier and a first resource reservation identifier, the first resource group identifier is used to identify a first VNF and a first VL, and the second resource reservation identifier is used to identify resources reserved for the first VNF and the first VL;

the sending module 603 is specifically configured to send a resource reservation request to the second NFVO, where the resource reservation request is used to instruct the second NFVO to establish a second mapping relationship, the second mapping relationship includes a composite NS resource identifier, a second resource group identifier, and a correspondence between the second resource reservation identifiers, the composite NS resource identifier is used to identify an instance of a composite NS, the second resource group identifier is used to identify a second VNF and a second VL, and the second resource reservation identifier is used to identify resources reserved for the second VNF and the second VL;

the allocating module 604 is specifically configured to, if the resource reservation of the first NFVO and the second NFVO is successful, determine the first VNF and the first VL according to the composite NS resource identifier and the first mapping relationship, and allocate reserved resources to the first VNF and the first VL;

the sending module 603 is specifically configured to send the instantiation request to the second NFVO, where the instantiation request carries the composite NS resource identifier, and the instantiation request is used to instruct the second NFVO to determine the second VNF and the second VL according to the composite NS resource identifier and the second mapping relationship, and allocate the reserved resources to the second VNF and the second VL.

Optionally, on the basis of the embodiment corresponding to fig. 14, please refer to fig. 15, in another embodiment of the NFVO 60 provided in the embodiment of the present application, the NFVO 60 further includes a release module 605;

the releasing module 605 is configured to release, if the resource reservation of the first NFVO and/or the second NFVO fails, resources reserved for the first VNF and the first VL according to the composite NS resource identifier and the first mapping relationship;

the sending module 603 is further configured to send, by the first NFVO, a resource release request to the second NFVO according to a third mapping relationship, where the third mapping relationship includes the composite NS resource identifier, a second NFVO identifier, and a resource reservation identifier, the second NFVO identifier is used to identify the second NFVO, the resource reservation identifier is used to identify a resource reservation state, the resource release request carries the composite NS resource identifier, and the resource release request is used to instruct the second NFVO to release resources reserved for the second VNF and the second VL according to the composite NS resource identifier and the second mapping relationship.

Optionally, on the basis of the embodiment corresponding to fig. 14, please refer to fig. 16, in another embodiment of the NFVO 60 provided in the embodiment of the present application, the NFVO 60 further includes an obtaining module 606 and a determining module 607;

the obtaining module 606 is configured to obtain the resource reservation identifier from the third mapping relationship by the first NFVO;

the determining module 607 is configured to determine that the resource reservation of the first NFVO and/or the second NFVO fails if the resource reservation identifier acquired by the acquiring module 606 indicates that the current resource reservation state is resource reservation overtime or resource reservation insufficient;

the determining module 607 is configured to determine that the resource reservation of the first NFVO and the second NFVO is successful if the resource reservation identifier obtained by the obtaining module 606 indicates that the current resource reservation state is that the resource reservation is completed and the resource reservation is sufficient.

Optionally, on the basis of the embodiment corresponding to fig. 14, fig. 15, or fig. 16, in another embodiment of the NFVO 60 provided in this embodiment of the present application, the first resource group identifier includes multiple first sub-resource group identifiers, where the first sub-resource group identifiers are used to identify a first sub-VNF and a first sub-VL, the first resource reservation identifier includes multiple first sub-resource reservation identifiers, the first sub-resource reservation identifier is used to identify resources reserved for the first sub-VNF and the first sub-VL, the first VNF includes multiple first sub-VNFs, and the first VL includes multiple first sub-VLs;

the second resource group identifier includes a plurality of second sub-resource group identifiers, the second sub-resource group identifiers are used for identifying a second sub-VNF and a second sub-VL, the second resource reservation identifier includes a plurality of second sub-resource reservation identifiers, the second sub-resource reservation identifier is used for identifying resources reserved for the second sub-VNF and the second sub-VL, the second VNF includes a plurality of the second sub-VNFs, and the second VL includes a plurality of the second sub-VLs;

the reservation module 602 is specifically configured to create the composite NS resource identifier according to the instantiation request;

establishing the first mapping relation according to the composite NS resource identifier, the plurality of first sub-resource group identifiers and the plurality of first sub-resource reservation identifiers;

the sending module 603 is specifically configured to send a resource reservation request to the second NFVO, where the resource reservation request is used to instruct the second NFVO to establish the second mapping relationship, and the second mapping relationship includes a composite NS resource identifier, the plurality of second sub-resource group identifiers, and a correspondence between the plurality of second sub-resource reservation identifiers.

Optionally, on the basis of the embodiment corresponding to fig. 14, fig. 15, or fig. 16, in another embodiment of the NFVO 60 provided in this embodiment of the present application, the releasing module 605 is specifically configured to release, if the reservation of resources of the first NFVO and/or the second NFVO fails, resources reserved for the first sub-VNF and the first sub-VL according to the composite NS resource identifier and the first mapping relationship;

the sending module 603 is specifically configured to send the resource release request to the second NFVO according to the third mapping relationship, where the resource release request carries the composite NS resource identifier, and the resource release request is used to instruct the second NFVO to release, according to the composite NS resource identifier and the second mapping relationship, resources already reserved for the second sub-VNF and the second sub-VL, or resources currently reserved for the second sub-VNF and the second sub-VL.

Optionally, on the basis of the embodiment corresponding to fig. 14, fig. 15, or fig. 16, in another embodiment of the NFVO 60 provided in this embodiment of the present application, the allocating module 604 is specifically configured to determine the first sub-VNF and the first sub-VL according to the composite NS resource identifier and the first mapping relationship if the resource reservation of the first NFVO and the second NFVO is successful, and allocate reserved resources to the first sub-VNF and the first sub-VL;

the sending module 603 is specifically configured to send the instantiation request to the second NFVO, where the instantiation request carries the composite NS resource identifier, and the instantiation request is used to instruct the second NFVO to determine the second sub-VNF and the second sub-VL according to the composite NS resource identifier and the second mapping relationship, and allocate the reserved resources to the second sub-VNF and the second sub-VL.

Optionally, on the basis of the embodiment corresponding to fig. 14, fig. 15, or fig. 16, referring to fig. 17, in another embodiment of the NFVO 60 provided in this embodiment of the present application, the NFVO further includes an update module 608;

the updating module 608 is configured to update the first mapping relationship after the sending module 603 sends the resource release request to the second NFVO according to the third mapping relationship.

Optionally, on the basis of the embodiment corresponding to fig. 14, fig. 15, or fig. 16, in another embodiment of the NFVO 60 provided in this embodiment of the present application, the determining module 607 is further configured to, after the sending module 603 sends the instantiation request to the second NFVO, determine that the instantiation of the nested NS of the second NFVO is successful if the first NFVO receives an instantiation success message sent by the second NFVO;

the determining module 607 is further configured to determine that the instantiation of the composite NS is successful if the instantiation of the first VNF and the first VL of the first NFVO is successful.

Optionally, on the basis of the embodiment corresponding to fig. 14, fig. 15, or fig. 16, in another embodiment of the NFVO 60 provided in this embodiment of the present application, the receiving module 601 is further configured to receive a composite NS update request or a composite NS scaling request after the determining module 607 determines that instantiation of the composite NS is successful, where the composite NS update request or the composite NS scaling request is used to trigger the first NFVO to send a scaling request to the second NFVO, the scaling request is used to instruct the second NFVO to perform resource scaling or resource scaling operation to obtain a first resource to be updated, and the first resource to be updated is used to instruct the second NFVO to update resources reserved in the second VNF and the second VL;

the determining module 607 is further configured to determine a second resource to be updated according to the composite NS update request;

the updating module 608 is further configured to update the resources reserved by the first VNF and the first VL according to the second resource to be updated.

Optionally, on the basis of the embodiment corresponding to fig. 14, fig. 15, or fig. 16, in another embodiment of the NFVO 60 provided in this embodiment of the present application, the releasing module 605 is further configured to release, if the first NFVO receives a composite NS instantiation completion request, resources reserved for the first VNF and the first VL according to the composite NS resource identifier and the first mapping relationship;

the sending module 603 is further configured to send a resource release request to the second NFVO, where the resource release request carries the composite NS resource identifier, and the resource release request is used to instruct the second NFVO to release resources reserved for the second VNF and the second VL according to the composite NS resource identifier and the second mapping relationship.

As described in detail below with respect to an NFVO corresponding to another embodiment of the present application, where the NFVO is applied to a resource processing system, the resource processing system further includes a second NFVO, please refer to fig. 18, where an NFVO 70 in an embodiment of the present application includes:

a receiving module 701, configured to receive a resource quota request;

a configuring module 702, configured to configure required resources for a first virtual network function VNF and a first virtual link VL according to the resource quota request received by the receiving module 701;

a sending module 703 is configured to send, to the second NFVO, the resource quota request received by the receiving module 701, where the resource quota request is used to indicate that the second NFVO configures required resources for a second VNF and a second VL;

an allocating module 704, configured to allocate reserved resources to the first VNF and the first VL if the resource quotas of the NFVO and the second NFVO are successful;

the sending module 703 is further configured to send an instantiation request to the second NFVO, where the instantiation request is used to instruct the second NFVO to perform an instantiation operation according to the second VNF and the second VL-quota resource.

In this embodiment, a receiving module 701 receives a resource quota request, a configuring module 702 configures required resources for a first virtual network function VNF and a first virtual link VL according to the resource quota request received by the receiving module 701, a sending module 703 sends the resource quota request received by the receiving module 701 to the second NFVO, where the resource quota request is used to indicate that the second NFVO configures the required resources for a second VNF and a second VL, if resource quotas of the NFVO and the second NFVO are successful, an allocating module 704 allocates reserved resources to the first VNF and the first VL, and the sending module 703 sends an instantiation request to the second NFVO, where the instantiation request is used to indicate that the second NFVO performs instantiation operation according to the second VNF and the second VL quota resources.

In an embodiment of the present application, an NFVO is provided, where the NFVO receives a resource quota request, configures required resources for a first VNF and a first VL according to the resource quota request, and the NFVO sends the resource quota request to a second NFVO, where the resource quota request is used to indicate the second NFVO to configure the required resources for a second VNF and a second VL, and if the resource quota is successful, the NFVO allocates virtual resources for the first VNF and the first VL on the configured resources, and finally the NFVO sends an instantiation request to the second NFVO, where the instantiation request is used to indicate the second NFVO to allocate virtual resources for the second VNF and the second VL on the configured resources. With the above apparatus, the NFVO may configure resources for instantiation operations first, and instruct the second NFVO to also configure resources for subsequent instantiation operations, so that it is possible to avoid that the NFVO causes all rollback of operations that have been instantiated successfully or are being instantiated due to insufficient resources.

Optionally, on the basis of the embodiment corresponding to fig. 18, in another embodiment of the NFVO 70 provided in this embodiment of the present application, the configuration module 702 is specifically configured to establish a first mapping relationship according to the resource quota request, where the first mapping relationship includes a composite network service NS resource identifier and a first resource group identifier, the composite NS resource identifier is used to identify an instance of a composite NS, and the first resource group identifier is used to identify the resource quotas of the first VNF and the first VL;

the sending module 703 is specifically configured to send the resource quota request to the second NFVO, where the resource quota request is used to instruct the second NFVO to establish a second mapping relationship, where the second mapping relationship includes the composite NS resource identifier and a second resource group identifier, and the second resource group identifier is used to identify resource quotas of the second VNF and the second VL;

the allocating module 704 is specifically configured to determine the first VNF and the first VL according to the composite NS resource identifier and the first mapping relationship, and allocate the reserved resources to the first VNF and the first VL;

the sending module 703 is specifically configured to send an instantiation request to the second NFVO, where the instantiation request is used to instruct the second NFVO to determine the second VNF and the second VL according to the composite NS resource identifier and the second mapping relationship, and allocate the reserved resources to the second VNF and the second VL.

It can be seen that, in the embodiment of the present application, the NFVO in different domains may determine the required virtual resources through the mapping relationship, and allocate the virtual resources for the instantiation operation, on one hand, a feasible way is provided for determining the virtual resources of each domain, which is beneficial to improving the practicability and flexibility of the scheme, and on the other hand, all rollback of operations that have been successfully instantiated or are being instantiated due to insufficient resources of the NFVO can be avoided.

Optionally, on the basis of the embodiment corresponding to fig. 18, please refer to fig. 19, in another embodiment of the NFVO 70 provided in the embodiment of the present application, the NFVO 70 further includes a release module 705;

the release module 705 is configured to release the resource quotas of the first VNF and the first VL according to the composite NS resource identifier and the first mapping relationship if the resource quotas of the NFVO and/or the second NFVO fail;

the sending module 703 is further configured to send a resource release request to the second NFVO, where the resource release request carries the composite NS resource identifier, and the resource release request is used to instruct the second NFVO to release the resource quotas of the second VNF and the second VL according to the composite NS resource identifier and the second mapping relationship.

As can be seen, in the embodiment of the present application, as long as a resource quota of one domain fails, all domains release the preconfigured virtual resources, and do not perform the lifecycle management operation of the composite NS any more. By adopting the mode, the problem of the operation rollback of a plurality of domains is solved by solving the problem of the instantiation operation failure of the composite NS caused by insufficient resources of a certain domain through the cross-domain resource quota.

In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product.

The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the invention to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored on a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website, computer, server, or data center to another website, computer, server, or data center via wire (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that a computer can store or a data storage device, such as a server, a data center, etc., that is integrated with one or more available media. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. 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 units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed to by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a read-only memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

The above embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions in the embodiments of the present application.

Claims

1. A method for resource processing, the method being applied to a resource processing system including a first network function virtualization orchestrator NFVO and a second NFVO, the method comprising:

the first NFVO receives an instantiation request of a network service NS;

the first NFVO reserves resources required by a first Virtual Network Function (VNF) and a first Virtual Link (VL) according to the instantiation request;

the first NFVO sends a resource reservation request to the second NFVO, where the resource reservation request is used to instruct the second NFVO to reserve resources required by a second VNF and a second VL;

if the resource reservation of the first NFVO and the second NFVO is successful, the first NFVO allocates the reserved resources to the first VNF and the first VL;

the first NFVO sends the instantiation request to the second NFVO, wherein the instantiation request is used for instructing the second NFVO to allocate reserved resources to the second VNF and the second VL.

2. The method of claim 1, wherein the first NFVO reserves resources required by the first VNF and the first VL according to the instantiation request, including:

the first NFVO establishes a first mapping relation according to the instantiation request, wherein the first mapping relation comprises a corresponding relation among a composite NS resource identifier, a first resource group identifier and a first resource reservation identifier, the first resource group identifier is used for identifying a first VNF and a first VL, and the first resource reservation identifier is used for identifying resources reserved for the first VNF and the first VL;

the first NFVO sending a resource reservation request to the second NFVO, including:

the first NFVO sends a resource reservation request to the second NFVO, where the resource reservation request is used to instruct the second NFVO to establish a second mapping relationship, the second mapping relationship includes a composite NS resource identifier, a second resource group identifier, and a correspondence between the second resource reservation identifiers, the composite NS resource identifier is used to identify an instance of a composite NS, the second resource group identifier is used to identify a second VNF and a second VL, and the second resource reservation identifier is used to identify resources reserved for the second VNF and the second VL;

if the resource reservation of the first NFVO and the second NFVO is successful, the allocating, by the first NFVO, the reserved resources to the first VNF and the first VL includes:

if the resource reservation of the first NFVO and the second NFVO is successful, the first NFVO determines the first VNF and the first VL according to the composite NS resource identifier and the first mapping relationship, and allocates reserved resources to the first VNF and the first VL;

the first NFVO sending the instantiation request to the second NFVO, including:

the first NFVO sends the instantiation request to the second NFVO, where the instantiation request carries the composite NS resource identifier, and the instantiation request is used to instruct the second NFVO to determine the second VNF and the second VL according to the composite NS resource identifier and the second mapping relationship, and allocate the reserved resources to the second VNF and the second VL.

3. The method of claim 2, further comprising:

if the resource reservation of the first NFVO and/or the second NFVO fails, the first NFVO releases the resources reserved for the first VNF and the first VL according to the composite NS resource identifier and the first mapping relationship;

the first NFVO sends a resource release request to the second NFVO according to a third mapping relationship, where the third mapping relationship includes the composite NS resource identifier, a second NFVO identifier, and a resource reservation identifier, the second NFVO identifier is used to identify the second NFVO, the resource reservation identifier is used to identify a resource reservation state, the resource release request carries the composite NS resource identifier, and the resource release request is used to instruct the second NFVO to release resources reserved for the second VNF and the second VL according to the composite NS resource identifier and the second mapping relationship.

4. The method of claim 3, further comprising:

the first NFVO acquires the resource reservation identifier from the third mapping relation;

if the resource reservation identifier indicates that the current resource reservation state is resource reservation overtime or insufficient, the first NFVO determines that the resource reservation of the first NFVO and/or the second NFVO fails;

if the resource reservation identifier indicates that the current resource reservation state is that resource reservation is completed and sufficient resource reservation is available, the first NFVO determines that the resource reservation of the first NFVO and the second NFVO is successful.

5. Method according to any of claims 3 to 4, wherein said first resource group identity comprises a plurality of first sub-resource group identities, said first sub-resource group identity identifying a first sub-VNF and a first sub-VL, said first resource reservation identity comprises a plurality of first sub-resource reservation identities, said first sub-resource reservation identity identifying resources reserved for said first sub-VNF and said first sub-VL, said first VNF comprises a plurality of said first sub-VNFs, said first VL comprises a plurality of said first sub-VLs;

the first NFVO establishes a first mapping relation according to the instantiation request, and the first mapping relation comprises the following steps:

the first NFVO creates the composite NS resource identifier according to the instantiation request;

the first NFVO establishes the first mapping relation according to the composite NS resource identifier, the first sub-resource group identifiers and the first sub-resource reservation identifiers;

the first NFVO sends a resource reservation request to the second NFVO, where the resource reservation request is used to instruct the second NFVO to establish the second mapping relationship, and the second mapping relationship includes a composite NS resource identifier, the plurality of second sub-resource group identifiers, and a correspondence between the plurality of second sub-resource reservation identifiers.

6. The method according to claim 5, wherein if the resource reservation of the first NFVO and/or the second NFVO fails, the first NFVO releases the resources reserved for the first sub-VNF and the first sub-VL according to the composite NS resource identifier and the first mapping relationship;

the sending, by the first NFVO, the resource release request to the second NFVO according to a third mapping relationship, including:

the first NFVO sends the resource release request to the second NFVO according to the third mapping relationship, where the resource release request carries the composite NS resource identifier, and the resource release request is used to instruct the second NFVO to release the resources already reserved for the second sub-VNF and the second sub-VL or to release the resources currently reserved for the second sub-VNF and the second sub-VL according to the composite NS resource identifier and the second mapping relationship.

7. The method of claim 5, wherein if the reservation of resources by the first NFVO and the second NFVO is successful, the first NFVO determining the first VNF and the first VL based on the composite NS resource identifier and the first mapping relationship, and allocating reserved resources to the first VNF and the first VL, comprises:

if the resource reservation of the first NFVO and the second NFVO is successful, the first NFVO determines the first sub-VNF and the first sub-VL according to the composite NS resource identifier and the first mapping relationship, and allocates reserved resources to the first sub-VNF and the first sub-VL;

the first NFVO sending the instantiation request to the second NFVO, including:

the first NFVO sends the instantiation request to the second NFVO, where the instantiation request carries the composite NS resource identifier, and the instantiation request is used to instruct the second NFVO to determine the second sub-VNF and the second sub-VL according to the composite NS resource identifier and the second mapping relationship, and allocate the reserved resources to the second sub-VNF and the second sub-VL.

8. The method according to any of claims 3 to 4, wherein after the first NFVO sends a resource release request to the second NFVO according to a third mapping relationship, the method further comprises:

and the first NFVO updates the first mapping relation.

9. The method according to any of claims 2 to 4, wherein after the first NFVO sends the instantiation request to the second NFVO, the method further comprises:

if the first VNF and the first VL of the first NFVO are instantiated successfully, the first NFVO determines that the instantiation of the composite NS is successful.

10. The method of claim 9, wherein after the first NFVO determines that instantiation of the composite NS is successful, the method further comprises:

the first NFVO receives a composite NS update request or a composite NS scaling request, where the composite NS update request or the composite NS scaling request is used to trigger the first NFVO to send a scaling request to the second NFVO, the scaling request is used to instruct the second NFVO to perform resource scaling or resource scaling operation to obtain a first resource to be updated, and the first resource to be updated is used to instruct the second NFVO to update resources reserved by the second VNF and the second VL;

the first NFVO determines a second resource to be updated according to the composite NS updating request;

the first NFVO updates the resources reserved by the first VNF and the first VL according to the second resource to be updated.

11. The method according to any one of claims 2 to 4, further comprising:

if the first NFVO receives a composite NS instantiation completion request, the first NFVO releases resources reserved for the first VNF and the first VL according to the composite NS resource identifier and the first mapping relationship;

the first NFVO sends a resource release request to the second NFVO, where the resource release request carries the composite NS resource identifier, and the resource release request is used to instruct the second NFVO to release resources reserved for the second VNF and the second VL according to the composite NS resource identifier and the second mapping relationship.

12. A method for resource processing, the method being applied to a resource processing system including a first network function virtualization orchestrator NFVO and a second NFVO, the method comprising:

the first NFVO receives a resource quota request;

the first NFVO configures required resources for a first Virtual Network Function (VNF) and a first Virtual Link (VL) according to the resource quota request;

the first NFVO sends the resource quota request to the second NFVO, where the resource quota request is used to indicate that the second NFVO configures required resources for a second VNF and a second VL;

if the resource quotas of the first NFVO and the second NFVO are successful, the first NFVO allocates reserved resources to the first VNF and the first VL;

the first NFVO sends an instantiation request to the second NFVO, where the instantiation request is used to instruct the second NFVO to perform resource management operations required for instantiation on allocated quota resources.

13. The method of claim 12, wherein the first NFVO configuring required resources for a first virtual network function VNF and a first virtual link VL according to the resource quota request, comprises:

the first NFVO establishes a first mapping relationship according to the resource quota request, where the first mapping relationship includes a composite network service NS resource identifier and a first resource group identifier, the composite NS resource identifier is used to identify an instance of a composite NS, and the first resource group identifier is used to identify resource quotas of the first VNF and the first VL;

the sending, by the first NFVO, the resource quota request to the second NFVO, including:

the first NFVO sends the resource quota request to the second NFVO, where the resource quota request is used to instruct the second NFVO to establish a second mapping relationship, where the second mapping relationship includes the composite NS resource identifier and a second resource group identifier, and the second resource group identifier is used to identify resource quotas of the second VNF and the second VL;

the first NFVO allocating reserved resources to the first VNF and the first VL, including:

the first NFVO determines the first VNF and the first VL according to the composite NS resource identifier and the first mapping relationship, and allocates reserved resources to the first VNF and the first VL;

the first NFVO sending an instantiation request to the second NFVO, including:

the first NFVO sends an instantiation request to the second NFVO, where the instantiation request is used to instruct the second NFVO to determine the second VNF and the second VL according to the composite NS resource identifier and the second mapping relationship, and allocate the reserved resources to the second VNF and the second VL.

14. The method of claim 13, further comprising:

if the resource quotas of the first NFVO and/or the second NFVO fail, the first NFVO releases the resource quotas of the first VNF and the first VL according to the composite NS resource identifier and the first mapping relationship;

the first NFVO sends a resource release request to the second NFVO, where the resource release request carries the composite NS resource identifier, and the resource release request is used to instruct the second NFVO to release the resource quotas of the second VNF and the second VL according to the composite NS resource identifier and the second mapping relationship.

15. A first network function virtualization orchestrator NFVO, wherein the first NFVO is applied to a resource processing system, the resource processing system further comprising a second NFVO, the first NFVO comprising:

a receiving module, configured to receive an instantiation request of a network service NS;

a reservation module, configured to reserve, according to the instantiation request received by the receiving module, resources required by a first virtual network function VNF and a first virtual link VL;

an allocating module, configured to, if the resource reservation of the first NFVO and the second NFVO is successful, allocate, by the first NFVO, the reserved resources to the first VNF and the first VL that are reserved by the reserving module;

the sending module is configured to send the instantiation request to the second NFVO, where the instantiation request is used to instruct the second NFVO to allocate the reserved resources to the second VNF and the second VL.

16. The first NFVO of claim 15,

the reservation module is specifically configured to establish a first mapping relationship according to the instantiation request, where the first mapping relationship includes a correspondence between a composite NS resource identifier, a first resource group identifier, and a first resource reservation identifier, where the first resource group identifier is used to identify a first VNF and a first VL, and the first resource reservation identifier is used to identify resources reserved for the first VNF and the first VL;

the sending module is specifically configured to send a resource reservation request to the second NFVO, where the resource reservation request is used to instruct the second NFVO to establish a second mapping relationship, the second mapping relationship includes a composite NS resource identifier, a second resource group identifier, and a correspondence between the second resource reservation identifiers, the composite NS resource identifier is used to identify an instance of the composite NS, the second resource group identifier is used to identify a second VNF and a second VL, and the second resource reservation identifier is used to identify resources reserved for the second VNF and the second VL;

the allocating module is specifically configured to determine the first VNF and the first VL according to the composite NS resource identifier and the first mapping relationship if the resource reservation of the first NFVO and the second NFVO is successful, and allocate reserved resources to the first VNF and the first VL;

the sending module is specifically configured to send the instantiation request to the second NFVO, where the instantiation request carries the composite NS resource identifier, and the instantiation request is used to instruct the second NFVO to determine the second VNF and the second VL according to the composite NS resource identifier and the second mapping relationship, and allocate the reserved resources to the second VNF and the second VL.

17. The first NFVO of claim 16, wherein the first NFVO further comprises a release module;

the release module is configured to release, if the resource reservation of the first NFVO and/or the second NFVO fails, resources reserved for the first VNF and the first VL according to the composite NS resource identifier and the first mapping relationship;

the sending module is further configured to send, by the first NFVO, a resource release request to the second NFVO according to a third mapping relationship, where the third mapping relationship includes the composite NS resource identifier, a second NFVO identifier, and a resource reservation identifier, the second NFVO identifier is used to identify the second NFVO, the resource reservation identifier is used to identify a resource reservation state, the composite NS resource identifier is carried in the resource release request, and the resource release request is used to instruct the second NFVO to release resources reserved for the second VNF and the second VL according to the composite NS resource identifier and the second mapping relationship.

18. The first NFVO of claim 17, further comprising an obtaining module and a determining module;

the obtaining module is configured to obtain the resource reservation identifier from the third mapping relationship by the first NFVO;

the determining module is configured to determine that the resource reservation of the first NFVO and/or the second NFVO fails if the resource reservation identifier acquired by the acquiring module indicates that the current resource reservation state is resource reservation overtime or resource reservation insufficient;

the determining module is configured to determine that the resource reservation of the first NFVO and the second NFVO is successful if the resource reservation identifier obtained by the obtaining module indicates that the current resource reservation state is that the resource reservation is completed and the resource reservation is sufficient.

19. The first NFVO of any one of claims 17-18, wherein the first resource group identifier comprises a plurality of first sub-resource group identifiers, the first sub-resource group identifiers being configured to identify a first sub-VNF and a first sub-VL, the first resource reservation identifier comprises a plurality of first sub-resource reservation identifiers, the first sub-resource reservation identifier is configured to identify resources reserved for the first sub-VNF and the first sub-VL, the first VNF comprises a plurality of the first sub-VNFs, and the first VL comprises a plurality of the first sub-VLs;

the reservation module is specifically configured to create the composite NS resource identifier according to the instantiation request;

the sending module is specifically configured to send a resource reservation request to the second NFVO, where the resource reservation request is used to instruct the second NFVO to establish the second mapping relationship, and the second mapping relationship includes a composite NS resource identifier, the plurality of second sub-resource group identifiers, and a correspondence relationship between the plurality of second sub-resource reservation identifiers.

20. The first NFVO of claim 19,

the release module is specifically configured to release, if the resource reservation of the first NFVO and/or the second NFVO fails, resources reserved for the first sub-VNF and the first sub-VL according to the composite NS resource identifier and the first mapping relationship;

the sending module is specifically configured to send the resource release request to the second NFVO according to the third mapping relationship, where the resource release request carries the composite NS resource identifier, and the resource release request is used to instruct the second NFVO to release, according to the composite NS resource identifier and the second mapping relationship, resources already reserved for the second sub-VNF and the second sub-VL, or resources currently reserved for the second sub-VNF and the second sub-VL.

21. The first NFVO of claim 19,

the allocating module is specifically configured to determine the first sub-VNF and the first sub-VL according to the composite NS resource identifier and the first mapping relationship if the resource reservation of the first NFVO and the second NFVO is successful, and allocate reserved resources to the first sub-VNF and the first sub-VL;

the sending module is specifically configured to send the instantiation request to the second NFVO, where the instantiation request carries the composite NS resource identifier, and the instantiation request is used to instruct the second NFVO to determine the second sub-VNF and the second sub-VL according to the composite NS resource identifier and the second mapping relationship, and allocate the reserved resources to the second sub-VNF and the second sub-VL.

22. The first NFVO of any one of claims 17-18, wherein the first NFVO further comprises a refresh module;

the updating module is configured to update the first mapping relationship after the sending module sends the resource release request to the second NFVO according to the third mapping relationship.

23. The first NFVO of any one of claims 16-17, wherein the first NFVO further comprises a determining module;

the determining module is configured to determine that the nested NS instantiation of the second NFVO is successful if the first NFVO receives an instantiation success message sent by the second NFVO after the sending module sends the instantiation request to the second NFVO;

the determining module is further configured to determine that the instantiation of the composite NS is successful if the instantiation of the first VNF and the first VL of the first NFVO is successful.

24. The first NFVO of claim 23, wherein the first NFVO further comprises a refresh module;

the receiving module is further configured to receive a composite NS update request or a composite NS scaling request after the determining module determines that the instantiation of the composite NS is successful, where the composite NS update request or the composite NS scaling request is used to trigger the first NFVO to send a scaling request to the second NFVO, the scaling request is used to instruct the second NFVO to perform resource scaling or resource scaling operation so as to obtain a first resource to be updated, and the first resource to be updated is used to instruct the second NFVO to update resources reserved by the second VNF and the second VL;

the determining module is further configured to determine a second resource to be updated according to the composite NS update request;

the update module is configured to update the resources reserved for the first VNF and the first VL according to the second resource to be updated.

25. The first NFVO of claim 18,

the determining module is further configured to determine that the nested NS instantiation of the second NFVO is successful if the first NFVO receives an instantiation success message sent by the second NFVO after the sending module sends the instantiation request to the second NFVO;

26. The first NFVO of claim 25, wherein the first NFVO further comprises a refresh module;

27. The first NFVO of any of claims 17 to 18,

the release module is further configured to release, if the first NFVO receives a composite NS instantiation completion request, resources reserved for the first VNF and the first VL according to the composite NS resource identifier and the first mapping relationship;

the sending module is further configured to send a resource release request to the second NFVO, where the resource release request carries the composite NS resource identifier, and the resource release request is used to instruct the second NFVO to release resources reserved for the second VNF and the second VL according to the composite NS resource identifier and the second mapping relationship.

28. A first network function virtualization orchestrator NFVO, wherein the first NFVO is applied to a resource processing system, the resource processing system further comprising a second NFVO, the first NFVO comprising:

a receiving module, configured to receive a resource quota request;

a quota module, configured to configure, according to the resource quota request received by the receiving module, a required resource for a first virtual network function VNF and a first virtual link VL;

a sending module, configured to send, to the second NFVO, the resource quota request received by the receiving module, where the resource quota request is used to indicate that the second NFVO configures required resources for a second VNF and a second VL;

an allocating module, configured to allocate reserved resources to the first VNF and the first VL if the resource quotas of the first NFVO and the second NFVO are successful;

the sending module is configured to send an instantiation request to the second NFVO, where the instantiation request is used to instruct the second NFVO to perform resource management operations required for instantiation on allocated quota resources.

29. The first NFVO of claim 28, wherein,

the quota module is specifically configured to establish a first mapping relationship according to the resource quota request, where the first mapping relationship includes a composite network service NS resource identifier and a first resource group identifier, the composite NS resource identifier is used to identify an instance of a composite NS, and the first resource group identifier is used to identify resource quotas of the first VNF and the first VL;

the sending module is specifically configured to send the resource quota request to the second NFVO, where the resource quota request is used to instruct the second NFVO to establish a second mapping relationship, where the second mapping relationship includes the composite NS resource identifier and a second resource group identifier, and the second resource group identifier is used to identify resource quotas of the second VNF and the second VL;

the allocating module is specifically configured to determine the first VNF and the first VL according to the composite NS resource identifier and the first mapping relationship, and allocate a reserved resource to the first VNF and the first VL;

the sending module is specifically configured to send an instantiation request to the second NFVO, where the instantiation request is used to instruct the second NFVO to determine the second VNF and the second VL according to the composite NS resource identifier and the second mapping relationship, and allocate reserved resources to the second VNF and the second VL.

30. The first NFVO of claim 29, wherein the first NFVO further comprises a release module;

the release module is configured to release the resource quotas of the first VNF and the first VL according to the composite NS resource identifier and the first mapping relationship if the resource quotas of the first NFVO and/or the second NFVO fail;

the sending module is further configured to send a resource release request to the second NFVO, where the resource release request carries the composite NS resource identifier, and the resource release request is used to instruct the second NFVO to release the resource quotas of the second VNF and the second VL according to the composite NS resource identifier and the second mapping relationship.

31. A network function virtualization orchestrator NFVO, comprising: a memory, a transceiver, a processor, and a bus system;

wherein the memory is to store programs and instructions;

the transceiver is used for receiving or sending information under the control of the processor;

the processor is used for executing the program in the memory;

the bus system is used for connecting the memory, the transceiver and the processor so as to enable the memory, the transceiver and the processor to communicate;

the processor is configured to call program instructions in the memory to perform the method of any of claims 1 to 11.

32. A network function virtualization orchestrator NFVO, comprising: a memory, a transceiver, a processor, and a bus system;

wherein the memory is to store programs and instructions;

the processor is used for executing the program in the memory;

the processor is configured to call program instructions in the memory to perform the method of any of claims 12 to 14.

33. A computer-readable storage medium comprising instructions that, when executed on a computer, cause the computer to perform the method of any of claims 1 to 11, or perform the method of any of claims 12 to 14.