CN106921977B

CN106921977B - Service quality planning method, device and system based on service flow

Info

Publication number: CN106921977B
Application number: CN201510989481.8A
Authority: CN
Inventors: 李少盈
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2015-12-26
Filing date: 2015-12-26
Publication date: 2020-11-06
Anticipated expiration: 2035-12-26
Also published as: CN106921977A

Abstract

The embodiment of the invention discloses a service quality planning method and a device based on service flow, wherein the method comprises the following steps: receiving an instantiation request for the NS; determining the data center position deployed for the VNF according to the residual resource amount of each data center; sending a resource reservation request to the VIM, wherein the resource reservation request is used for indicating that network resources required by the VL and the VNF are reserved; when receiving resource reservation success response information fed back by the VIM responding to the resource reservation request, sending instantiation requests of VL and VNF to the VIM; and receiving instantiation response information fed back by the VIM response pair VL and the instantiation request of the VNF. By adopting the embodiment of the invention, the service quality of the service flow can be ensured by adjusting the position of the data center of the virtual network function.

Description

Service quality planning method, device and system based on service flow

Technical Field

The present invention relates to the field of communications technologies, and in particular, to a service quality planning method, apparatus, and system based on a service flow.

Background

A unified network platform, which supports connectivity communication services of different functions and quality of service (QoS) using dynamic, secure network slices, is a basic capability of a 5G network. A network slice, i.e., a "5G slice," supports a communication service of a particular connection type and provides control plane and user plane specific processing methods for this service. A 5G slice consists of a set of 5G network functions together with specific RAT settings in order to support a specific use case or business model. The network slices adopt a virtualization technology, so that the isolation among different slices is realized from the resource aspect, and different multiple networks are virtualized according to diversified requirements. Network Function Virtualization (NFV) uses a virtualization technology to allocate required virtual resources (virtual computing, storage, and Network) to a Network application through a Network Function Virtualization Orchestrator (NFVO), and automatically deploys the application to a virtual machine in a data center. Taking the schematic structure of the NFV Management and organization (NFV MANO) architecture shown in fig. 1A as an example, the NFV MANO may include an NFVO, a Virtual Network Function Manager (VNFM), and a Virtual Infrastructure Manager (VIM). The NFVO is used for lifecycle management of Network communication across multiple data centers, orchestration of resource usage, and coexistence of multiple Virtual Network Function (VNF) instances using policies for total resource usage or priority, etc. The VNFM is used for lifecycle management of VNF instances. VIM is used for Network Function Virtualization Infrastructure (NFVI) computation, storage, and control and management of Network resources. A Service executed based on NFVI is called a Network Service (NS), which includes all elements constituting this Network Service. In order to describe the network service and the elements constituting the network service, a cell including the above elements is introduced. In the top network service cell, there are four cells: a VNF cell, a Physical Network Function (PNF) cell, a Virtual Link (VL) cell, and a Virtual Network Function Forwarding Graph (VNFFG) cell. When the NFV MANO architecture is used for network slicing, a deployment process across multiple data centers is absent in the NS/VNFFG instance lifecycle management process, which results in a method and a process for lacking QoS guarantee in the NS/VNFFG instance lifecycle management process, and a great influence is brought to latency.

Disclosure of Invention

The application provides a service quality planning method and device based on service flow, which can ensure the service quality of the service flow by adjusting the position of a virtual network function.

A first aspect provides a service flow-based quality of service planning method, which is applied to NFVO, and includes:

the NFVO receives an instantiation request for the NS.

And the NFVO determines the data center position deployed for the VNF according to the residual resource amount of each data center.

The NFVO sends a resource reservation request to the VIM indicating reservation of network resources required by the VL and VNF.

And when receiving resource reservation success response information fed back by the VIM in response to the resource reservation request, the NFVO sends instantiation requests of the VL and the VNF to the VIM.

And the NFVO receives instantiation response information fed back by the VIM responding to the VL and the instantiation request of the VNF.

In this solution, all VLs of one NS constitute one network link topology. VNFFG may refer to other cells in the network traffic, such as PNF, VL, VNF. The VNFFG also includes a network networking path element that describes the traffic chain aspects of the VNFFG. The NS, VNF, and PNF cells contain attachment point attributes describing the relationship between NS, VNF, or PNF and VL. Cells can be used in two different contexts: a descriptor of a directory or template, or an instance record in the NFV. The NFVO can record the number of data centers administered and the location of each data center. The NFVO may also record the relationship between the VIMs and the data centers, for example, different VIMs manage different data centers, that is, one VIM manages one data center, another example is that one VIM manages at least two data centers, and another example is that one VIM manages one data center and another example is that one VIM manages at least two data centers. NFVO may also record a delay index that can be reached by each VL based on location, and the delay produced by a VL may include: VL latency between different hosts (hosts) in each data center, VL latency between the same hosts in each data center, typical latency between different data centers, and typical latency from a data center portal to the PNF. After receiving the instantiation request for the NS or VNFFG, the NFVO may determine a service flow instance according to parameter information carried by the instantiation request, determine a data center position deployed for the VNF according to the remaining resource amount of each data center, estimate a time delay to be generated by the service flow instance according to the data center position deployed for the VNF, send a resource reservation request to the VIM, and instantiate the VL, the VNF, and the VPN when receiving resource reservation success response information fed back by the VL, the VNF, and the VPN in response to the resource reservation request, and may ensure QoS of the service flow by adjusting the data center position of the VNF.

In one possible design, the instantiation request may carry parameter information, and after the NFVO receives the instantiation request for the NS, the NFVO may determine the service flow instance according to the parameter information.

In one possible design, the NFVO determines the service flow instance according to the parameter information, which may specifically be: the NFVO determines a deployment template in a Network Service description information block (NSD) of the NS, where the deployment template includes instance identification information for different VNF instances of the same type, and determines a Service flow instance according to the instance identification information in the deployment template.

In a specific implementation, the NFVO may assign different instance identification information to different VNF instances of the same type in each deployment template (navigator) in the NSD. When the instantiation request received by the NFVO carries description block identification information of an NSD, the NSD corresponding to the description block identification information may be determined, and the service flow instance may be determined according to instance identification information in a deployment template of the NSD.

The elements constituting the NS may include an NSD, which is a template and may be used to indicate the description information block referred to by the NS.

In one possible design, the NFVO determines the service flow instance according to the parameter information, which may specifically be: the NFVO determines a deployment template in the NSD of the NS, the deployment template comprises instance identification information of different VL instances of the same type, and the service flow instance is determined according to the instance identification information in the deployment template.

In specific implementation, the NFVO may add VL to each navigator of the NSD, and assign different instance identification information to different VL instances of the same type. When the instantiation request received by the NFVO carries description block identification information of an NSD, the NSD corresponding to the description block identification information may be determined, and the service flow instance may be determined according to instance identification information in a deployment template of the NSD.

In one possible design, the NFVO determines the service flow instance according to the parameter information, which may specifically be: the NFVO determines an NFP in a virtual network function forwarding graph information description block (VNFFG Descriptor, VNFFGD), where the NFP is used to indicate a deployment template in the NS, and determines a service flow instance according to the NFP.

In a specific implementation, the NSD may be used to indicate VNFFGD referenced by the NS, and the VNFFGD may define a traffic flow instance NFP for each of the flavors in the NSD, where the CP is a junction point between the VL instance and the VNF instance. The NFP thus described is a definite service flow instance, which can describe, for example, that a Base Transceiver Station (BTS) needs to connect to a specified Base Station Controller (BSC), or that a BSC needs to connect to a specified Mobile Switching Center (MSC). When the instantiation request received by the NFVO carries description block identification information of VNFFGD, it may determine VNFFGD corresponding to the description block identification information, further determine NFP in VNFFGD, and determine a service flow instance according to NFP.

In one possible design, the NFVO determines the service flow instance according to the parameter information, which may specifically be: the NFVO determines demand parameters of the NFP in the VNFFGD, wherein the demand parameters comprise time delay, bandwidth and jitter, and determines a service flow instance according to the demand parameters.

In a specific implementation, a requirement parameter of end-to-end QoS may be added in the NFP of VNFFGD in advance, where the requirement parameter may include latency, bandwidth, jitter, and the like. The NFVO may determine a demand parameter of the NFP in the VNFFGD, and determine the service flow instance according to the demand parameter.

In one possible design, after the NFVO determines the data center location to be deployed to the VNF according to the remaining resource amount of each data center, the following operations may be further performed:

the delay that will occur to a traffic flow instance, including at least one VNFFG, is estimated based on the data center location.

And when the time delay of each VNFFG meets the corresponding time delay requirement, sending a resource reservation request to the virtual infrastructure manager.

And when the time delay of at least one VNFFG does not meet the corresponding time delay requirement, determining the data center position deployed for the VNF according to the residual resource amount of each data center.

In one possible design, when a service flow instance includes at least two service flow NFP instances, the NFVO determines, according to the service flow instance, a data center location deployed to the VNF, which may specifically be:

and sequencing each service flow NFP instance according to the time delay required by at least two service flow NFP instances.

And acquiring a deployment scheme of the service flow instance meeting the minimum time delay.

In the deployment scheme of the service flow instance meeting the minimum time delay, the deployment schemes of other service flow instances except the service flow instance meeting the minimum time delay are obtained.

And determining the position of the data center deployed on the VNF according to the acquired deployment schemes of other service flow instances except the service flow instance meeting the minimum time delay.

In a specific implementation, when a service flow instance includes a first service flow NFP instance, a second service flow NFP instance, and a third service flow NFP instance, and a delay time required by each service flow NFP instance is 1ms, 100ms, and 10ms, respectively, then the NFVO may rank the service flow NFP instances according to the delay time required by each service flow NFP instance, for example, the service flow NFP instance with the minimum required delay time is arranged at the forefront, that is, the arranged service flow NFP instances are: a first traffic flow NFP instance, a third traffic flow NFP instance, and a second traffic flow NFP instance.

Further, the smaller the delay required by the NFP instance of the traffic flow, the higher the requirement on the deployment location of the VNF. The NFVO may obtain, by using a traversal method, a deployment scenario that satisfies a service flow instance with a minimum delay, that is, a deployment scenario that satisfies a first service flow NFP instance, and a deployment scenario that satisfies a third service flow NFP instance in the deployment scenario that satisfies the first service flow NFP instance. Optionally, after the NFVO obtains the deployment scheme that satisfies the third service flow NFP instance in the deployment scheme that satisfies the first service flow NFP instance, the NFVO may also obtain the deployment scheme that satisfies the second service flow NFP instance in the deployment scheme that satisfies the third service flow NFP instance.

Further, the NFVO may determine a data center location where the VNF is deployed according to the obtained deployment scheme of the service flow instance that satisfies the other time delays other than the minimum time delay. For example, after the NFVO acquires the deployment scenario satisfying the third traffic flow NFP instance from the deployment scenario satisfying the first traffic flow NFP instance, the NFVO may determine the data center location deployed to the VNF according to the acquired deployment scenario satisfying the third traffic flow NFP instance. For another example, after the NFVO acquires the deployment scheme satisfying the second service flow NFP instance from the deployment scheme satisfying the third service flow NFP instance, the NFVO may determine the data center location deployed to the VNF according to the acquired deployment scheme satisfying the second service flow NFP instance.

and sequencing each service flow NFP instance according to the hop counts of at least two service flow NFP instances.

And acquiring a deployment scheme of the service flow instance meeting the maximum hop count.

In the deployment scheme of the service flow instance meeting the maximum hop count, the deployment schemes of other service flow instances except the service flow instance meeting the maximum hop count are obtained.

And determining the position of the data center deployed on the VNF according to the acquired deployment schemes of other service flow instances except the service flow instance meeting the maximum hop count.

In a specific implementation, when a service flow instance includes a first service flow NFP instance, a second service flow NFP instance, and a third service flow NFP instance, and the hop count of each service flow NFP instance is 10 hops, 1 hop, and 5 hops, respectively, then the NFVO may rank, according to the hop count of each service flow NFP instance, for example, the service flow NFP instance with the largest hop count is arranged at the forefront, that is, the ranked service flow NFP instance is: a first traffic flow NFP instance, a third traffic flow NFP instance, and a second traffic flow NFP instance.

Further, the larger the hop count of the traffic NFP instance, the higher the requirement on the deployment location of the VNF. The NFVO may obtain, by using a traversal method, a deployment scenario of the service flow instance that satisfies the maximum hop count, that is, a deployment scenario that satisfies the first service flow NFP instance, and a deployment scenario that satisfies the third service flow NFP instance in the deployment scenario that satisfies the first service flow NFP instance. Optionally, after the NFVO obtains the deployment scheme that satisfies the third service flow NFP instance in the deployment scheme that satisfies the first service flow NFP instance, the NFVO may also obtain the deployment scheme that satisfies the second service flow NFP instance in the deployment scheme that satisfies the third service flow NFP instance.

Further, the NFVO may determine a data center location where the VNF is deployed according to the obtained deployment scheme of the service flow instance that satisfies the hop count other than the maximum hop count. For example, after the NFVO acquires the deployment scenario satisfying the third traffic flow NFP instance from the deployment scenario satisfying the first traffic flow NFP instance, the NFVO may determine the data center location deployed to the VNF according to the acquired deployment scenario satisfying the third traffic flow NFP instance. For another example, after the NFVO acquires the deployment scheme satisfying the second service flow NFP instance from the deployment scheme satisfying the third service flow NFP instance, the NFVO may determine the data center location deployed to the VNF according to the acquired deployment scheme satisfying the second service flow NFP instance.

And sequencing the service flow NFP instances with the same time delay according to the hop counts of at least two service flow NFP instances.

And acquiring a deployment scheme of the service flow instance meeting the minimum delay and the maximum hop count, and taking the acquired deployment scheme of the service flow instance meeting the minimum delay and the maximum hop count as a first deployment scheme.

And acquiring the deployment schemes of other service flow instances except the service flow instance meeting the minimum delay and the maximum hop count in the first deployment scheme, and taking the acquired deployment schemes of other service flow instances except the service flow instance meeting the minimum delay and the maximum hop count as a second deployment scheme.

According to a second deployment scenario, a data center location for a VNF deployment is determined.

In a specific implementation, when a service flow instance includes a first service flow NFP instance, a second service flow NFP instance, a third service flow NFP instance, and a fourth service flow NFP instance, a delay time required by each service flow NFP instance is 1ms, 100ms, 10ms, and 1ms, and a hop count of each service flow NFP instance is 10 hops, 1 hop, 5 hops, and 5 hops, respectively, then the NFVO may rank the service flow NFP instances according to the delay time and the hop count required by each service flow NFP instance, for example, the service flow NFP instance with the minimum required delay time and the maximum hop count is ranked at the forefront, that is, the ranked service flow NFP instance is: the first service flow NFP instance, the fourth service flow NFP instance, the third service flow NFP instance, and the second service flow NFP instance.

Further, the NFVO may obtain, by using a traversal method, a deployment scenario that satisfies a minimum delay and a maximum hop count of the service flow instance, that is, a deployment scenario that satisfies a first service flow NFP instance, and obtain, in the first deployment scenario, a deployment scenario that satisfies a fourth service flow NFP instance, and obtain, in the first deployment scenario, a deployment scenario that satisfies the fourth service flow NFP instance, and obtain, as a second deployment scenario, a deployment scenario that satisfies the fourth service flow NFP instance. Optionally, after the NFVO acquires the deployment scheme meeting the fourth service flow NFP instance in the first deployment scheme, the NFVO may further acquire the deployment scheme meeting the third service flow NFP instance in the deployment scheme meeting the fourth service flow NFP instance, and use the deployment scheme meeting the third service flow NFP instance in the deployment scheme meeting the fourth service flow NFP instance as a second deployment scheme. Optionally, after the NFVO acquires the deployment scheme satisfying the third service flow NFP instance in the deployment scheme satisfying the fourth service flow NFP instance, the NFVO may also acquire the deployment scheme satisfying the second service flow NFP instance in the deployment scheme satisfying the third service flow NFP instance, and use the deployment scheme satisfying the second service flow NFP instance in the deployment scheme satisfying the third service flow NFP instance as the second deployment scheme.

Further, the NFVO may determine a data center location for VNF deployment according to the second deployment scenario. For example, the second deployment scenario is a deployment scenario satisfying the fourth traffic flow NFP instance in the first deployment scenario, and the NFVO may determine the data center location deployed to the VNF according to the second deployment scenario. For another example, the second deployment scheme is a deployment scheme that satisfies the NFP instance of the third service flow in a deployment scheme that satisfies the NFP instance of the fourth service flow, and the NFVO may determine the data center location deployed to the VNF according to the second deployment scheme. For another example, the second deployment scheme is a deployment scheme that satisfies the second traffic flow NFP instance in a deployment scheme that satisfies the third traffic flow NFP instance, and the NFVO may determine the data center location deployed to the VNF according to the second deployment scheme.

and sequencing the forwarding path instances of each service flow network according to the hop counts of the forwarding path instances of at least two service flow networks.

And sequencing the forwarding path instances of the service flow network with the same hop number according to the time delay required by at least two forwarding path instances of the service flow network.

And acquiring a deployment scheme of the service flow instance meeting the maximum hop count and the minimum time delay, and taking the acquired deployment scheme of the service flow instance meeting the maximum hop count and the minimum time delay as a first deployment scheme.

And acquiring the deployment schemes of other service flow instances except the service flow instance meeting the maximum hop count and the minimum time delay in the first deployment scheme, and taking the acquired deployment schemes of other service flow instances except the service flow instance meeting the maximum hop count and the minimum time delay as a second deployment scheme.

And determining the position of the data center for the virtual network function deployment according to the second deployment scheme.

In a specific implementation, when a service flow instance includes a first service flow NFP instance, a second service flow NFP instance, a third service flow NFP instance, and a fourth service flow NFP instance, the hop count of each service flow NFP instance is 10 hops, 1 hop, 5 hops, and the delay required by each service flow NFP instance is 1ms, 100ms, 10ms, and 1ms, respectively, then the NFVO may rank the service flow NFP instances according to the hop count and the delay required by each service flow NFP instance, for example, the service flow NFP instance with the largest hop count and the smallest delay required is ranked at the forefront, that is, the ranked service flow NFP instance is: the first service flow NFP instance, the fourth service flow NFP instance, the third service flow NFP instance, and the second service flow NFP instance.

It should be noted that the NFVO may preset priorities of the four schemes for determining the data center position deployed to the VNF, for example, the scheme for ordering the NFP instance of the service flow according to the delay has the highest priority, which is the first priority; the priority of the scheme for sequencing the NFP instances of the service flow according to the hop count is a second priority; the priority of the first scheme for sequencing the NFP instances of the service flow according to the time delay and the hop count is a third priority; the priority of the second scheme for ordering the NFP instances of the traffic flow according to the delay and the number of hops is a fourth priority. If the scheme of the first priority is implemented, the deployment schemes of other service flow instances except the service flow instance satisfying the minimum delay cannot be obtained from the deployment schemes of the service flow instances satisfying the minimum delay, or the data center position deployed to the VNF cannot be determined according to the deployment schemes of other service flow instances except the service flow instance satisfying the minimum delay, and the NFVO may implement the scheme of the second priority. If the second priority scheme is implemented, the deployment schemes of other service flow instances except the service flow instance satisfying the maximum hop count cannot be obtained from the deployment schemes of the service flow instances satisfying the maximum hop count, or the data center position deployed to the VNF cannot be determined according to the deployment schemes of other service flow instances except the service flow instance satisfying the maximum hop count, and the NFVO may implement the third priority scheme. If the third priority scheme is implemented, the deployment schemes of other service flow instances except the service flow instance satisfying the minimum delay and the maximum hop count cannot be obtained from the deployment schemes of the service flow instances satisfying the minimum delay and the maximum hop count, or the data center position deployed to the VNF cannot be determined according to the deployment schemes of other service flow instances except the service flow instance satisfying the minimum delay and the maximum hop count, and the NFVO may implement the fourth priority scheme.

Further, if the NFVO determines the data center location deployed to the VNF according to the deployment schemes of the other service flow instances other than the service flow instance satisfying the minimum latency when implementing the scheme of the first priority, the NFVO does not need to implement other schemes for determining the data center location deployed to the VNF. If the NFVO determines the data center location deployed to the VNF according to the deployment schemes of other service flow instances other than the service flow instance satisfying the maximum hop count when implementing the scheme of the second priority, the NFVO does not need to implement other schemes of determining the data center location deployed to the VNF. If the NFVO determines the data center location deployed to the VNF according to the deployment schemes of other service flow instances other than the service flow instance satisfying the minimum delay and the maximum hop count when implementing the third-priority scheme, the NFVO does not need to implement other schemes for determining the data center location deployed to the VNF. If the NFVO determines the data center location deployed to the VNF according to the deployment schemes of other service flow instances other than the service flow instance satisfying the maximum hop count and the minimum delay when implementing the scheme of the fourth priority, the NFVO does not need to implement other schemes of determining the data center location deployed to the VNF.

In one possible design, the NFVO sends the resource reservation request to the VIM, which may specifically be:

the method comprises the steps that a resource reservation request is sent to the VIM through resource reservation generation operation of a virtual resource management interface, so that the VIM detects whether network resources required by VNF interconnection are available or not according to the data center position of the VNF, when the network resources required by the VNF interconnection are available, the network resources required by the VNF interconnection are reserved by the VIM, the VIM conducts pretesting on the reserved network resources, and when the QoS of the VL meets the requirement, the VIM feeds back resource reservation success response information.

In a specific implementation, the NFVO may determine the data center position of the VL according to the data center position of the VNF. If two VNFs are deployed in the same data center managed by the VIM, the VIM may assign the VL between the two VNFs to the data center positions of the two VNFs, that is, the data center position of the VL is the same as the data center position of the VNF. Further, the NFVO may send a resource reservation request to the VIM through a resource reservation operation generated by a virtual resource management interface, the VIM detects whether a network resource required by VNF interconnection is available according to the data center position of the VNF, when the network resource required by VNF interconnection is available, the VIM reserves the network resource required by VNF interconnection, performs pretesting on the reserved network resource, and when the QoS of the VL meets the requirement, the VIM feeds back resource reservation success response information.

when the pre-allocated VNF instance list is determined and comprises at least one VNF instance, whether resources required by the instantiation of the VNF are effective or not is detected according to the data center position of the VNF.

When the VNF instantiation required resources are valid, a resource reservation request is sent to the VIM.

In one possible design, NFVO sends an instantiation request for VL to VIM, which may specifically be:

and sending a VL network connection request to the VIM through resource application or resource updating operation of the virtual resource management interface so that the VIM instantiates the connection network required by the NS.

In one possible design, the NFVO sends an instantiation request for the VNF to the VIM, which may specifically be:

sending a VNF network connection request to the VIM through a resource application or resource update operation of the virtual resource management interface, so that the VIM connects to an external interface of the VNF and connects a required Virtual Deployment Unit (VDU) to a connection network required by the NS.

In a specific implementation, if all VNF instances are valid, for a VNF that is not already connected to the network, the NFVO may request the VIM to connect the VNF to the network by applying for a resource or updating a resource operation through the virtual network resource management interface. For example, the NFVO may request the VIM to connect to an external interface of the VNF, or to connect the needed VDU to the connectivity network of the NS, and the VIM may connect the needed VDU to the network and confirm that the connection is complete.

In one possible design, after the NFVO receives the resource reservation success response information fed back by the VIM in response to the resource reservation request, the following operations may be further performed:

when the pre-allocated VNF instance list is determined and the VNF instance list includes at least one VNF instance, adding location parameter information in a process of invoking an instantiation VNF operation of the VNF lifecycle management interface, the location parameter information including a data center location of the VNF, to instantiate the VNF.

In one possible design, the NFVO may also perform the following operations:

and when receiving a capacity expansion request or a capacity reduction request to the NS, carrying out capacity expansion or capacity reduction on the NS at a corresponding position of a network element related to the NS.

In a specific implementation, if the capacity expansion request for the NS is to apply for more resources for the NS, or the capacity reduction request for the NS is to release part of resources for the NS, the NFVO may assume that the duration of message processing by the network element is not affected by the capacity expansion or capacity reduction for the NS, the duration of all service flows of the entire network is not changed, and the NFVO may perform capacity expansion or capacity reduction for the NS at a corresponding position of the network element related to the NS. For example, if the capacity of the network element associated with the NS is smaller than the preset threshold, the NFVO may add a network element of the same type at the location of the network element, so as to implement capacity expansion of the NS.

In one possible design, the NFVO may also perform the following operations:

when an expansion request for the NS is received, determining that the residual resource amount of the data center where the VNF is located is smaller than a preset threshold.

An instantiation request for the corresponding NS is generated.

In a specific implementation, if the remaining resource amount of the data center location to which each network element corresponding to the NS belongs is smaller than a preset threshold, the NFVO may expand the NS, where the data center location where the original network element is located remains unchanged, and the network element to be added may be deployed by the service flow-based quality of service planning method described in the first aspect, and the like.

from the data center location of the VNF, a data center location of the VL is determined.

In one possible design, the NFVO determines the data center position of the VL according to the data center position of the VNF, which may specifically be:

when two VNFs are deployed in the same VIM-managed data center, the data center location of the VL between the two VNFs is the same as the data center location of the two VNFs.

When two VNFs are deployed in different VIM-managed datacenters, the datacenter location of the VL between the two VNFs is WIM-determined.

and sending a resource reservation request to the WIM, wherein the resource reservation request is used for indicating that Network resources required by a Virtual Private Network (VPN) are reserved.

And when receiving resource reservation success response information fed back by the WIM in response to the resource reservation request, sending an instantiation request of the VPN to the WIM.

And receiving instantiation response information fed back by the WIM in response to the instantiation request of the VPN.

and sending a resource reservation request to the WIM so that the WIM detects whether VPN network resources among the data centers are available according to the data center position of the VNF, when the VPN network resources among the data centers are available, the WIM reserves the VPN network resources among the data centers, the WIM performs pretest on the reserved network resources, and when the QoS of the VPN meets the requirement, the WIM feeds back resource reservation success response information.

In one possible design, NFVO sends an instantiation request for VPN to WIM, which may specifically be:

and sending a VPN network connection instantiation request to the WIM through resource application or resource updating operation of the virtual resource management interface so that the WIM instantiates the connection network required by the NS.

A second aspect provides a traffic flow based quality of service planning apparatus operable to perform some or all of the steps in conjunction with the first aspect.

A third aspect provides a service quality planning system for a traffic flow, which includes NFVO and VIM, where the NFVO and VIM may be used to implement some or all of the steps in conjunction with the first aspect.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

FIG. 1A is a block diagram of an NFV MANO framework provided in an embodiment of the present invention;

fig. 1B is a schematic diagram of a framework of an NFP provided in an embodiment of the present invention;

fig. 2 is a block diagram of a VIM managing a data center according to an embodiment of the present invention;

fig. 3 is a schematic flow chart of a service flow-based quality of service planning method provided in an embodiment of the present invention;

fig. 4 is a block diagram of a VIM framework for managing at least two data centers according to an embodiment of the present invention;

fig. 5 is a flowchart illustrating a method for service flow-based quality of service planning according to another embodiment of the present invention;

FIG. 6 is a schematic structural diagram of a network function virtualization orchestrator provided in an embodiment of the present invention;

fig. 7 is a schematic structural diagram of a service flow-based quality of service planning apparatus provided in an embodiment of the present invention.

Detailed Description

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

Referring to fig. 2, fig. 2 is a schematic diagram of a framework of a VIM managing a Data Center according to an embodiment of the present invention, where the VIM1 manages a Data Center (DC) 1, the VIM2 manages DC2, and the VNFFG1 and the VNFFG2 may refer to other cells in the NS, such as PNF, VL, and VNF. VNFFG1 contains network networking path elements that describe the traffic chain aspects of VNFFG 1. VNFFG2 contains network networking path elements that describe the traffic chain aspects of VNFFG 2. The NS, VNF, and PNF cells contain attachment point attributes describing the relationship between NS, VNF, or PNF and VL.

Taking the schematic frame diagram of the NFP shown in fig. 1B as an example, the latency of each NFP is composed of three parts: the time delay TnL generated by VL, the time delay TnV generated by VNF, and the time delay TnP generated by the external network, in the embodiment of the present invention, a Tnfp field may be added to the NFP of VNFFGD to obtain the time delay of the NFP. Specifically, a field TL describing QoS delay requirements may be added to the VLD, and the VL delay may be ensured by virtual network resource allocation, for example, an application accelerator. The embodiment of the invention can also add a delay index field TV reaching the VNF in the VNFD. Assuming that a VNF instance is deployed in a data center, as long as the system satisfies resources required by VNFD, it can be guaranteed that the delay index of VNF is reached. The resources required by the VNFD may include Central Processing Unit (CPU) resources, memory resources, or accelerator resources. In addition, the delay index of the external network is ensured by a way that a network controller allocates VPN resources, the delay of the external network is TP, wherein TP needs to satisfy the following conditions:

Tnfp1≥T01L+T02L+T03L+T01V+T02V+T01P+T02P

Tnfp2≥T01L+T02L+T03L+T04L+T05L+T01V+T02V+T03V+T04V+T05V+T01P+T02P+T03P

then in the framework diagram of fig. 2 where one VIM manages one data center, NFVO needs to determine the relationship between each VIM and the physical location, e.g., VIM1 manages DC1 and VIM2 manages DC 2. NFVO needs to interact with VIM and WIM to reserve resources for VL, VNF, and VPN allocations.

The NFVO needs to determine whether resource allocation to the VNF is successful according to the data center position of the deployed VNF, for example, the NFVO may obtain a delay of each NFP, and when the following requirements are met, the NFVO may determine the data center position where the VNF is successfully deployed:

Tvnffg1≥T01L+T02L+T03L+T01V+T02V+T01P+T02P

Tvnffg2≥T01L+T02L+T03L+T04L+T05L+T01V+T02V+T03V+T04V+T05V+T01P+T02P+T03P

wherein, Tvnffg1 is used to indicate the time delay generated by VNFFG1, Tvnffg2 is used to indicate the time delay generated by VNFFG2, TnL is used to indicate the time delay generated by VLn, TnV is used to indicate the time delay generated by VNFn, TnP is used to indicate the time delay generated by external network, for example, T01P is used to indicate the time delay generated by PNF1, T02P is used to indicate the time delay generated by PNF2, T03P is used to indicate the time delay generated by PNF3, and n is a numerical value.

In a specific implementation, the NFVO receives an instantiation request for the NS, where the instantiation request carries parameter information.

And the NFVO determines a service flow instance according to the parameter information.

And the NFVO estimates the time delay generated by the service flow instance according to the data center position deployed to the VNF.

The NFVO sends resource reservation requests for the VL and VNFs to the VIM.

The VIM allocates reserved resources to the VL and VNF.

NFVO sends a resource reservation request for VPN to WIM.

The WIM allocates reserved resources to the VPN.

The VIM instantiates VL and VNF.

The WIM instantiates the VPN.

Referring to fig. 3, fig. 3 is a schematic flow chart of a service flow-based service quality planning method provided in an embodiment of the present invention, where the method may be applied to a framework of a VIM managing a data center shown in fig. 2, and as shown in the drawing, the service flow-based service quality planning method in the embodiment of the present invention at least may include:

s301, the NFVO receives an instantiation request for the NS, where the instantiation request carries parameter information.

The NFVO may receive an instantiation request for the NS sent by the sender over an instantiation network traffic operation of the network traffic lifecycle management interface. The instantiation request may carry parameter information, and the parameter information may include description block identification information of the NSD or description block identification information of the VNFFGD, and the like.

S302, the NFVO determines a service flow instance according to the parameter information.

The NFVO may determine the service flow instance according to the parameter information. For example, the NFVO may determine a deployment template in the NSD of the NS, where the deployment template includes instance identification information for different VNF instances of the same type, and determine the service flow instance according to the instance identification information in the deployment template. For another example, the NFVO may determine a deployment template in the NSD of the NS, where the deployment template includes instance identification information for different VL instances of the same type, and determine the service flow instance according to the instance identification information in the deployment template. As another example, the NFVO may determine the NFP in VNFFGD, where the NFP is used to indicate a deployment template in the NS, and determine the traffic flow instance according to the NFP. For another example, the NFVO may determine demand parameters of the NFP in the VNFFGD, where the demand parameters include latency, bandwidth, and jitter, and determine the service flow instance according to the demand parameters.

In a specific implementation, the NFVO may determine the boundary condition before determining the service flow instance according to the parameter information. Boundary conditions, known conditions to solve the problem. From a network deployment perspective, known conditions may include:

and deploying or expanding the needed Flavor, and assuming that the needed Flavor is calculated according to the traffic model. The flag will indicate the required VNF and the size and number of VLs. When there are a plurality of VNFs or VLs of the same type, VNFs or VLs of the same type may be distinguished by adding an instance identifier.

The Qos requirements of each traffic flow NFP are explicit (e.g. latency, bandwidth and jitter) and the traffic flow path NFP is deterministic (participating in determining the traffic flow instance related content).

The data center location of the PNF to be connected is determined. The PNF may include a gateway (Gate Way), a radio frequency transmitting device of a base station (e.g., a tower).

The time delay generated by each VNF is determined. And under the condition that the resources required by each VNF can be ensured, determining the message processing time and determining the time delay generated by the VNF.

In an alternative embodiment, the NFVO may detect whether the instantiation request is valid. For example, the NFVO may detect whether the sender is authorized, i.e., whether the sender is conditioned to send an instantiation request for the NS. As another example, the NFVO may detect whether the parameters carried by the instantiation request satisfy technical level correctness and policy level compliance. Wherein if the NS includes multiple VNFFGs and policy rules, the policy rules may result in only a portion of the VNFFGs being valid for the service instance.

And S303, the NFVO determines the data center position deployed to the VNF according to the residual resource amount of each data center.

In a specific implementation, when a service flow instance includes a service flow NFP instance, the NFVO may obtain a time delay of the service flow NFP instance, obtain a deployment scheme of the service flow instance that meets the time delay, and determine a data center location deployed to the VNF according to the obtained deployment scheme. Optionally, the NFVO may obtain the hop count of the NFP instance of the service flow, obtain a deployment scheme of the service flow instance that meets the hop count, and determine a data center location deployed to the VNF according to the obtained deployment scheme.

When the service flow instances comprise at least two service flow NFP instances, the NFVO may sort the service flow NFP instances according to the time delay required by the at least two service flow NFP instances, obtain a deployment scheme of the service flow instance satisfying the minimum time delay, obtain a deployment scheme of other service flow instances except the service flow instance satisfying the minimum time delay in the deployment scheme of the service flow instance satisfying the minimum time delay, and determine a data center position deployed to the VNF according to the obtained deployment schemes of other service flow instances except the service flow instance satisfying the minimum time delay.

When the service flow instances comprise at least two service flow NFP instances, the NFVO may sort the service flow NFP instances according to the hop counts of the at least two service flow NFP instances, obtain a deployment scheme of the service flow instance satisfying the maximum hop count, obtain a deployment scheme of other service flow instances except the service flow instance satisfying the maximum hop count in the deployment scheme of the service flow instance satisfying the maximum hop count, and determine a data center position deployed to the VNF according to the obtained deployment schemes of other service flow instances except the service flow instance satisfying the maximum hop count.

When the service flow instance comprises at least two service flow NFP instances, the NFVO may determine, based on the latency required by the at least two service flow NFP instances, sequencing each service flow NFP instance, according to the hop count of at least two service flow NFP instances, sequencing the NFP instances of the service flows with the same time delay, acquiring a deployment scheme of the NFP instances of the service flows meeting the minimum time delay and the maximum hop count, taking the deployment scheme of the NFP instances of the service flows meeting the minimum time delay and the maximum hop count as a first deployment scheme, and acquiring a deployment scheme of other service flow instances except the service flow instance meeting the minimum delay and the maximum hop count in the first deployment scheme, taking the acquired deployment scheme of other service flow instances except the service flow instance meeting the minimum delay and the maximum hop count as a second deployment scheme, and determining the data center position deployed to the VNF according to the second deployment scheme.

When the service flow instance comprises at least two service flow NFP instances, the NFVO may determine, based on the number of hops of the at least two service flow NFP instances, sequencing each service flow NFP instance, according to the time delay required by at least two service flow NFP instances, sequencing the NFP instances of the service flows with the same hop count, acquiring a deployment scheme of the NFP instances of the service flows meeting the maximum hop count and the minimum time delay, taking the deployment scheme of the NFP instances of the service flows meeting the maximum hop count and the minimum time delay as a first deployment scheme, and acquiring the deployment schemes of other service flow instances except the service flow instance meeting the maximum hop count and the minimum time delay in the first deployment scheme, taking the acquired deployment schemes of other service flow instances except the service flow instance meeting the maximum hop count and the minimum time delay as a second deployment scheme, and determining the data center position deployed to the VNF according to the second deployment scheme.

It should be noted that, if the current data center position deployed by the NFVO on the VNF is different from the data center position where the VNF is located before the instantiation request is received, the NFVO may further estimate the time delay generated by each service flow instance according to the data center position deployed on the VNF; if the current data center position deployed by the NFVO on the VNF is the same as the data center position where the VNF is located before the instantiation request is received, the instantiation of the NS fails, and the NFVO sends instantiation failure information to the sender, where the instantiation failure information may be used to describe a reason for the instantiation failure.

In an optional embodiment, the NFVO may predict the time delay generated by each service flow instance according to the data center location deployed to the VNF. Taking the frame schematic diagram of fig. 2 in which a VIM manages a data center as an example, the NFVO may respectively estimate the time delays generated by the VNFFG1, the VNFFG2, and each NFP, and detect whether the time delay generated by the VNFFG1 satisfies the following conditions:

Tvnffg1≥T01L+T02L+T03L+T01V+T02V+T01P+T02P

NFVO may also detect whether the latency incurred by VNFFG2 satisfies the following condition:

Tvnffg2≥T01L+T02L+T03L+T04L+T05L+T01V+T02V+T03V+T04V+T05V+T01P+T02P+T03P

if the latency generated by VNFFG1 satisfies the above condition and the latency generated by VNFFG2 also satisfies the above condition, NFVO may further perform step S304; if the delay generated by VNFFG1 does not satisfy the above condition, or the delay generated by VNFFG2 does not satisfy the above condition, the NFVO may re-determine the data center location deployed to the VNF according to the remaining resource amount of each data center.

S304, the NFVO sends a resource reservation request to the VIM.

The NFVO may send resource reservation requests to the VIM for the VL and VNFs. Wherein the VIM may include VIM1 and VIM 2.

In an alternative embodiment, the NFVO may perform a feasibility check of the VNF intercommunication setup. In a specific implementation, the NFVO may determine the location of the VL according to the location of the VNF. For example, if two VNFs are deployed in a data center managed by the same VIM, the VIM may assign a VL between the two VNFs to data center positions of the two VNFs, that is, the data center position of the VL is the same as the data center position of the VNF. If two VNFs are deployed in different VIM-managed datacenters, the WIM may assign a datacenter location to the VL. Further, the NFVO may send a resource reservation request for the VL and the VNF to the VIM through a resource reservation generation operation of the virtual resource management interface.

It should be noted that, if there are multiple VNFFGs in the framework applied in the embodiment of the present invention, steps S304 to S313 are repeatedly executed for each VNFFG.

In an optional embodiment, when the pre-allocated VNF instance list is determined and the VNF instance list includes at least one VNF instance, the NFVO may detect whether resources required for VNF instantiation are valid according to a data center location of the VNF, and when the resources required for VNF instantiation are valid, the NFVO may send a resource reservation request to the VIM through a resource reservation generation operation of the virtual resource management interface.

S305, the VIM reserves network resources required by the VL and VNF.

In an optional embodiment, after receiving the resource reservation request for the VL and the VNF, the VIM may detect whether network resources required for VNF interconnection are available according to a data center position of the VNF, when the network resources required for VNF interconnection are available, the VIM reserves the network resources required for VNF interconnection, performs a pretest on the reserved network resources, and when the QoS of the VL meets the requirement, the VIM feeds back resource reservation success response information.

S306, the NFVO sends a resource reservation request to the WIM.

The NFVO may send a resource reservation request for the VPN to the WIM.

S307, the WIM reserves the network resources required by the VPN.

In an alternative embodiment, the NFVO may perform a feasibility check of the inter-data center connectivity setup. In a specific implementation, after receiving a resource reservation request sent by the NFVO, the WIM may detect whether VPN network resources between the data centers are available according to the data center position of the VNF, and when VPN network resources between the data centers are available, the WIM may reserve the network resources. Further optionally, after the WIM reserves the network resource, the network resource reserved may be pretested, and when the QoS of the VPN meets the requirement, the WIM feeds back resource reservation success response information to the NFVO.

S308, the NFVO sends a VL network connection instantiation request to the VIM.

When the NFVO needs to instantiate VL network resources of the NS-plane, a VL network connection instantiation request may be sent to the VIM. For example, when a VL network connection exists, the NFVO may send a VL network connection instantiation request to the VIM through an update resource operation of the virtual resource management interface. For another example, when there is no VL network connection, NFVO may send a VL network connection instantiation request to VIM through a resource application operation of the virtual resource management interface.

In a specific implementation, before the NFVO sends the VL network connection instantiation request to the VIM, the location of the VL may be determined according to the location of the VNF. For example, if two VNFs are deployed in a data center managed by the same VIM, the VIM may assign a VL between the two VNFs to data center positions of the two VNFs, that is, the data center position of the VL is the same as the data center position of the VNF. If two VNFs are deployed in different VIM-managed datacenters, the WIM may assign a datacenter location to the VL.

S309, the VIM instantiates the VL network connection.

After receiving the VL network connection instantiation request sent by the NFVO, the VIM may instantiate the VL network connection, i.e., instantiate the connection network required by the NS.

In an alternative embodiment, after the VIM instantiates the VL network connection, VL instantiation response information may be sent to the NFVO, where the VL instantiation response information is used to indicate confirmation that the VL network connection application is complete.

S310, NFVO sends VPN network connection instantiation request to WIM.

When the NFVO needs to instantiate the VPN network resources of the NS layer, it may send a VPN network connection instantiation request to the WIM. For example, when a VPN network connection exists, the NFVO may send a VPN network connection instantiation request to the WIM through an update resource operation of the virtual resource management interface. For another example, when there is no VPN network connection, the NFVO may send a VPN network connection instantiation request to the WIM through a resource application operation of the virtual resource management interface.

S311, the WIM instantiates the VPN network connection.

After receiving the VPN network connection instantiation request sent by the NFVO, the WIM may instantiate the VPN network connection, i.e., instantiate the connection network required by the NS.

In an optional embodiment, after the WIM instantiates the VPN network connection, VPN instantiation response information may be sent to the NFVO, where the VPN instantiation response information is used to indicate that the VPN network connection application is confirmed to be completed.

S312, the NFVO sends a VNF network connection instantiation request to the VIM.

When the NFVO needs to connect the VNF to the network, a VNF network connection instantiation request may be sent to the VIM. For example, when a VNF network connection exists, the NFVO may send a VNF network connection instantiation request to the VIM through an update resource operation of the virtual resource management interface. For another example, when there is no VNF network connection, the NFVO may send a VNF network connection instantiation request to the VIM through a resource application operation of the virtual resource management interface.

In an optional embodiment, for each VNF instance required by the NS, the NFVO detects whether a VNF instance meeting the requirement exists through a VNF query operation of a VNF lifecycle management interface with the VNFM, and if so, the NFVO may invoke the VNF instance through the VNF lifecycle management interface with the VNFM; if not, the NFVO may request the VIM to instantiate the VNF. The embodiment of the invention does not need to instantiate the VNF after receiving the instantiation request every time, and can improve the resource utilization rate.

In an optional embodiment, when determining a pre-allocated VNF instance list, and the VNF instance list includes at least one VNF instance, the NFVO may detect whether there is a VNF instance currently required to be instantiated in the VNF instance list, and when there is no VNF instance currently required to be instantiated in the VNF instance list, the NFVO may instantiate the VNF instance currently required to be instantiated by invoking an instantiation VNF operation of the VNF lifecycle management interface. In a specific implementation, the NFVO may add a parameter of a data center location deployed to the VNF in a process of invoking an instantiation VNF operation of the VNF lifecycle management interface to instantiate the VNF.

S313, the VIM instantiates the VNF network connection.

After receiving the VNF network connection instantiation request sent by the NFVO, the VIM may instantiate the VNF network connection. In a specific implementation, the VIM may connect the external interface of the VNF and connect the required VDU to the connection network required by the NS.

In an optional embodiment, after the VIM instantiates the VNF network connection, VNF instantiation response information indicating that the VNF network connection application is confirmed to be completed may be sent to the NFVO.

In an alternative embodiment, after the VIM instantiates the VNF network connection, the NFVO may send a VNF connection request to the NM, which may connect an external interface of the VNF with the PNF interface. The Network Manager (NM) may include an Operations Support System (OSS), an element Management System (EM), a Network Management System (NMs), a WIM, or the like.

In an optional embodiment, after the NFVO confirms that VL, VPN, and VNF are instantiated, NS instantiation response information may be sent to the sender.

In an optional embodiment, when a capacity expansion request or a capacity reduction request for a service flow instance is detected, the NFVO may perform capacity expansion or capacity reduction on the service flow instance at a corresponding location of a network element associated with the service flow instance. For example, when the network element needs to be scaled, the NFVO may assume that the scaling of the network element does not affect the time length for processing the message by the network element, so that the time lengths of all service flows of the entire network remain unchanged, and the NFVO may add or delete the network element in the data center where the network element is located. For another example, when the capacity of the network element is smaller than the first preset threshold, the NFVO may add the same type of network element to the data center location where the network element is located, so as to ensure that the duration of all traffic flows of the entire network remains unchanged.

In an optional embodiment, when a capacity expansion request for a service flow instance is detected, the NFVO may determine that the remaining resource amount of the data center to which the VNF belongs is smaller than a preset threshold, where the capacity expansion request carries a network element to be added, and the NFVO may instantiate a newly added network element by using the service flow-based quality of service planning method according to the embodiment of the present invention.

In the service quality planning method based on service flow shown in fig. 3, NFVO receives an instantiation request for NS, determines a service flow instance according to parameter information carried by the instantiation request, determines a data center position deployed for VNF according to a remaining resource amount of each data center, NFVO sends a resource reservation request to VIM, VIM reserves network resources required by VL and VNF, NFVO sends a resource reservation request to WIM, WIM reserves network resources required by VPN, NFVO sends a VL network connection instantiation request to VIM, VIM instantiates VL network connection, NFVO sends a VPN network connection instantiation request to WIM, WIM instantiates VPN network connection, NFVO sends a VNF network connection instantiation request to WIM, and the VIM instantiates VNF network connection, and can guarantee QoS of the service flow by adjusting the data center position of VNF.

Referring to fig. 4, fig. 4 is a block diagram of a VIM managing at least two data centers according to an embodiment of the present invention, where the VIM manages DC1 and DC2, and VNFFG may refer to other cells in NS, such as PNF, VL, and VNF. The VNFFG contains network networking path elements that describe the traffic chain aspects of the VNFFG. The NS, VNF, and PNF cells contain attachment point attributes describing the relationship between NS, VNF, or PNF and VL.

VL3 is located across data centers, i.e., VL3 is located in DC1 and DC 2. The VIM may assign the VNF and the VL to the designated data centers according to the location information, affinity, and anti-affinity principles of each data center provided by the NFVO.

Tvnffg≥T01L+T02L+T03L+T04L+T05L+T01V+T02V+T03V+T04V+T05V+T01P+T03P

where Tvnffg is used to indicate the delay caused by VNFFG, TnL is used to indicate the delay caused by VLn, TnV is used to indicate the delay caused by VNFn, TnP is used to indicate the delay caused by external network, for example, T01P is used to indicate the delay caused by PNF1, T03P is used to indicate the delay caused by PNF3, and n is a numerical value.

The NFVO sends resource reservation requests for the VL and VNFs to the VIM.

The VIM allocates reserved resources to the VL and VNF.

The VIM instantiates VL and VNF.

Referring to fig. 5, fig. 5 is a flowchart illustrating a service flow-based service quality planning method according to an embodiment of the present invention, where the method may be applied to a framework in which a VIM manages at least two data centers shown in fig. 4, where the service flow-based service quality planning method according to the embodiment of the present invention at least includes:

s501, the NFVO receives an instantiation request for the NS, and the instantiation request carries parameter information.

S502, the NFVO determines a service flow instance according to the parameter information.

And S503, the NFVO determines the data center position deployed to the VNF according to the residual resource amount of each data center.

In an optional embodiment, the NFVO may predict the time delay generated by each service flow instance according to the data center location deployed to the VNF. Taking the frame schematic diagram of fig. 4 in which one VIM manages at least two data centers as an example, the NFVO may estimate the delay generated by the VNFFG and each NFP, and detect whether the delay generated by the VNFFG satisfies the following condition:

Tvnffg≥T01L+T02L+T03L+T04L+T05L+T01V+T02V+T03V+T04V+T05V+T01P+T03P

if the delay generated by VNFFG satisfies the above condition, NFVO may further perform step S504; if the delay generated by the VNFFG does not satisfy the above condition, the NFVO may re-determine the data center location deployed to the VNF according to the remaining resource amount of each data center.

S504, the NFVO sends a resource reservation request to the VIM.

The NFVO may send resource reservation requests to the VIM for the VL and VNFs.

In an alternative embodiment, the NFVO may perform a feasibility check of the VNF intercommunication setup. In a specific implementation, the NFVO may send a resource reservation request for the VL and the VNF to the VIM through a resource reservation generation operation of the virtual resource management interface.

It should be noted that, if there are multiple VNFFGs in the framework applied in the embodiment of the present invention, steps S504 to S509 will be repeatedly executed for each VNFFG.

S505, the VIM reserves network resources required by the VL and the VNF.

S506, the NFVO sends a VL network connection instantiation request to the VIM.

S507, the VIM instantiates the VL network connection.

S508, the NFVO sends a VNF network connection instantiation request to the VIM.

S509, the VIM instantiates the VNF network connection.

In an alternative embodiment, after the VIM instantiates the VNF network connection, the NFVO may send a VNF connection request to the NM, which may connect an external interface of the VNF with the PNF interface. NMs may include OSS, EM, NMS, or WIM, among others.

In the service quality planning method based on service flows shown in fig. 5, NFVO receives an instantiation request for NS, determines a service flow instance according to parameter information carried by the instantiation request, determines a data center position deployed for VNF according to a remaining resource amount of each data center, NFVO sends a resource reservation request to VIM, VIM reserves network resources required by VL and VNF, NFVO sends a VL network connection instantiation request to VIM, VIM instantiates VL network connection, NFVO sends a VNF network connection instantiation request to VIM, VIM instantiates VNF network connection, and can guarantee QoS of service flows by adjusting the data center position of VNF.

It should be noted that, if the NFVO is used for lifecycle management of network communication across at least three data centers, and the VIMs interacting with the NFVO includes at least two VIMs, where there is one VIM managing one data center and there is also one VIM managing at least two data centers, the service flow-based service quality planning method in the embodiment of the present invention may be combined with part or all of the flows in the embodiment of the service flow quality planning method described in fig. 3 and fig. 5. For example, NFVO may interact with a VIM managing one data center in combination with the quality of service planning method for the traffic flow shown in fig. 3 to implement instantiation of VNF, VL, and VPN, and NFVO may interact with a VIM managing at least two data centers in combination with the quality of service planning method for the traffic flow shown in fig. 5 to implement instantiation of VNF and VL.

Referring to fig. 6, fig. 6 is a schematic structural diagram of an NFVO according to an embodiment of the present invention. As shown in fig. 6, the NFVO may include: a processor 601, a memory 602, an input device 603, and an output device 604. The processor 601 is connected to a memory 602, an input device 603 and an output device 604, for example, the processor 601 may be connected to the memory 602, the input device 603 and the output device 604 through a bus.

The processor 601 may be a CPU, a Network Processor (NP), or the like.

The memory 602 may be specifically configured to store data blocks, data block version numbers corresponding to the data blocks, and the like. The memory 602 may include volatile memory (volatile memory), such as random-access memory (RAM); the memory may also include a non-volatile memory (non-volatile memory), such as a read-only memory (ROM), a flash memory (flash memory), a Hard Disk Drive (HDD), or a solid-state drive (SSD); the memory may also comprise a combination of memories of the kind described above.

The input device 603 may optionally include a standard wired interface, a wireless interface (e.g., WI-FI interface), etc.

The output device 604 may optionally include a standard wired interface, a wireless interface (e.g., WI-FI interface), etc.

The processor 601, the input device 603, and the output device 604 call the program code stored in the memory 602, and can perform the following operations:

an input 603 for receiving an instantiation request for the NS.

The processor 601 is configured to determine a data center location deployed for the VNF according to the remaining resource amount of each data center.

An output means 604 for sending a resource reservation request to the VIM, the resource reservation request indicating that network resources required for the VL and the VNF are reserved.

The output device 604 is further configured to send an instantiation request of VL and VNF to the VIM when receiving resource reservation success response information fed back by the VIM in response to the resource reservation request.

The input device 603 is further configured to receive instantiation response information fed back by the VIM response to the VL and the instantiation request of the VNF.

Specifically, the NFVO described in the embodiment of the present invention may be used to implement part or all of the processes in the embodiment of the method for planning quality of service based on service flows described in conjunction with fig. 3 or fig. 5.

Referring to fig. 7, fig. 7 is a schematic structural diagram of a service flow-based service quality planning apparatus provided in an embodiment of the present invention, where the service flow-based service quality planning apparatus provided in the embodiment of the present invention may be combined with the processor 601 in fig. 6, and as shown in the drawing, the service flow-based service quality planning apparatus in the embodiment of the present invention may at least include a request receiving unit 701, a position determining unit 702, a request sending unit 703, and an information receiving unit 704, where:

a request receiving unit 701, configured to receive an instantiation request for the NS.

A location determining unit 702, configured to determine, according to the remaining resource amount of each data center, a data center location deployed for the VNF.

A request sending unit 703 is configured to send a resource reservation request to the VIM, where the resource reservation request is used to indicate that network resources required by the VL and the VNF are reserved.

The request sending unit 703 is further configured to send an instantiation request for VL and VNF to the VIM when receiving resource reservation success response information fed back by the VIM in response to the resource reservation request.

An information receiving unit 704, configured to receive instantiation response information fed back by the VIM in response to instantiation requests of the VL and the VNF.

In an optional embodiment, the instantiation request carries parameter information, and the service flow-based quality of service planning apparatus in the embodiment of the present invention may further include:

an instance determining unit 705, configured to determine the service flow instance according to the parameter information after the request receiving unit 701 receives the instantiation request for the NS.

In an alternative embodiment, the instance determining unit 705 is specifically configured to:

a deployment template in the NSD of the NS is determined, the deployment template including instance identification information for different VNF instances of the same type.

And determining the service flow instance according to the instance identification information in the deployment template.

a deployment template in the NSD of the NS is determined, the deployment template including instance identification information for different VL instances of the same type.

an NFP in VNFFGD is determined, the NFP to indicate a deployment template in the NS.

And determining a service flow instance according to the NFP.

and determining demand parameters of the NFP in the VNFFGD, wherein the demand parameters comprise time delay, bandwidth and jitter.

And determining the service flow instance according to the demand parameters.

In an optional embodiment, the service flow-based quality of service planning apparatus in the embodiment of the present invention may further include:

a delay estimation unit 706, configured to estimate, by the location determination unit 702, a delay to be generated by a service flow instance, according to the data center location after determining the data center location deployed for the VNF according to the remaining resource amount of each data center, where the service flow instance includes at least one VNFFG.

The request sending unit 703 is further configured to send a resource reservation request to the VIM when the latency of each VNFFG meets the corresponding latency requirement.

The position determining unit 702 is further configured to, when the latency of at least one VNFFG does not meet the corresponding latency requirement, determine a data center position deployed to the VNF according to the remaining resource amount of each data center.

In an alternative embodiment, the service flow instance includes at least two service flow NFP instances, and the position determining unit 702 is specifically configured to:

And sequencing the service flow NFP instances with the same hop count according to the time delay required by at least two service flow NFP instances.

In an optional embodiment, the request sending unit 703 sends a resource reservation request to the VIM, where the resource reservation request is specifically used to:

In an alternative embodiment, the request sending unit 702 sends an instantiation request for VL to the VIM, specifically to:

and sending a VL network connection instantiation request to the VIM through resource application or resource updating operation of the virtual resource management interface so that the VIM instantiates the connection network required by the NS.

In an alternative embodiment, the request sending unit 702 sends an instantiation request of the VNF to the VIM, specifically to:

and sending a VNF network connection instantiation request to the VIM through resource application or resource updating operation of the virtual resource management interface so that the VIM is connected with an external interface of the VNF and is connected with a required VDU to a connection network required by the NS.

an instantiation unit 707, configured to, after the information receiving unit 704 receives resource reservation success response information fed back by the VIM in response to the resource reservation request, when determining a pre-allocated VNF instance list and the VNF instance list includes at least one VNF instance, add location parameter information in a process of invoking an instantiation VNF operation of the VNF lifecycle management interface, where the location parameter information includes a data center location of the VNF, so as to instantiate the VNF.

the scaling unit 708 is configured to, when receiving a capacity expansion request or a capacity reduction request for the NS, perform capacity expansion or capacity reduction on the NS at a corresponding position of a network element related to the NS.

the resource amount determining unit 709 is configured to determine, when an expansion request for the NS is received, that a remaining resource amount of the data center where the VNF is located is smaller than a preset threshold.

A request generating unit 710 for generating an instantiation request for the NS.

In an alternative embodiment, after determining the data center position deployed to the VNF according to the remaining resource amount of each data center, the position determining unit 702 is further configured to determine the data center position of the VL according to the data center position of the VNF.

In an alternative embodiment, the position determining unit 702 determines the data center position of the VL according to the data center position of the VNF, and is specifically configured to:

when two VNFs are deployed in the data center of the same VIM, the data center position of the VL between the two VNFs is the same as the data center position of the two VNFs.

In an optional embodiment, the request sending unit 703 is further configured to, after the location determining unit 702 determines the location of the data center deployed to the VNF according to the remaining resource amount of each data center, send a resource reservation request to the WIM, where the resource reservation request is used to indicate that network resources required by the VPN are reserved.

The request sending unit 703 is further configured to send an instantiation request for the VPN to the WIM when receiving the resource reservation success response information fed back by the WIM in response to the resource reservation request.

The information receiving unit 704 is further configured to receive instantiation response information fed back by the WIM in response to the instantiation request of the VPN.

In an optional embodiment, the request sending unit 703 sends the resource reservation request to the WIM, which may specifically be:

and sending a resource reservation request to the WIM so that the WIM detects whether VPN resources among the data centers are available according to the data center position of the VNF, when the VPN resources among the data centers are available, the WIM reserves the VPN resources among the data centers, the WIM performs pretest on the reserved network resources, and when the QoS of the VPN meets the requirement, the WIM feeds back resource reservation success response information.

In an alternative embodiment, the request sending unit 703 sends an instantiation request for a VPN to the WIM, which may specifically be:

Specifically, the service flow-based service quality planning apparatus described in the embodiment of the present invention may be used to implement part or all of the processes in the embodiment of the service flow-based service quality planning method described in conjunction with fig. 3 or fig. 5 of the present invention.

In the description herein, references to the description of the term "one embodiment," "some embodiments," "an example," "a specific example," or "some examples," etc., mean that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the invention. In this specification, the schematic representations of the terms used above are not necessarily for the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, various embodiments or examples and features of different embodiments or examples described in this specification can be combined and combined by one skilled in the art without contradiction.

Furthermore, the terms "first", "second" and "first" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one such feature. In the description of the present invention, "a plurality" means at least two, e.g., two, three, etc., unless specifically limited otherwise.

The logic and/or steps represented in the flowcharts or otherwise described herein, such as a program listing of executable instructions that can be considered to implement logical functions, can be embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. For the purposes of this description, a "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of the computer-readable medium would include the following: an electrical connection (electronic device) having one or more wires, a portable computer case (magnetic device), a random access memory, a read only memory, an erasable programmable read only memory, an optical fiber device, and a portable compact disc read only memory. Additionally, the computer-readable medium could even be paper or another suitable medium upon which the program is printed, as the program can be electronically captured, via for instance optical scanning of the paper or other medium, then compiled, interpreted or otherwise processed in a suitable manner if necessary, and then stored in a computer memory.

It should be understood that portions of the present invention may be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, the various steps or methods may be implemented in software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, any one or combination of the following techniques, which are known in the art, may be used: a discrete logic circuit having a logic gate circuit for implementing a logic function on a data signal, an application specific integrated circuit having an appropriate combinational logic gate circuit, a programmable gate array, a field programmable gate array, or the like.

In addition, the modules in the embodiments of the present invention may be implemented in the form of hardware, or may be implemented in the form of software functional modules. The integrated module, if implemented in the form of a software functional module and sold or used as a separate product, may also be stored in a computer readable storage medium.

Although embodiments of the present invention have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting the present invention, and that variations, modifications, substitutions and alterations can be made to the above embodiments by those of ordinary skill in the art within the scope of the present invention.

Claims

1. A service quality planning method based on service flow is characterized in that the method is applied to a network function virtualization orchestrator, and the method comprises the following steps:

receiving an instantiation request for a network service; determining the position of a data center for deploying the virtual network function according to the residual resource amount of each data center;

sending a resource reservation request to a virtual infrastructure manager, wherein the resource reservation request is used for indicating the virtual infrastructure manager to reserve network resources required by the virtual connection and the virtual network function according to the position of a data center of the virtual network function;

when receiving resource reservation success response information fed back by the virtual infrastructure manager in response to the resource reservation request, sending an instantiation request of the virtual connection and a virtual network function to the virtual infrastructure manager;

receiving instantiation response information fed back by the virtual infrastructure manager in response to the instantiation request of the virtual connection and the virtual network function.

2. The method of claim 1, wherein the instantiation request carries parameter information;

after receiving the instantiation request of the network service, the method further comprises the following steps:

and determining a service flow instance according to the parameter information.

3. The method of claim 2, wherein said determining a traffic flow instance based on said parameter information comprises:

determining a deployment template in a network service description information block of the network service, wherein the deployment template comprises instance identification information of different virtual network function instances of the same type;

4. The method of claim 2, wherein said determining a traffic flow instance based on said parameter information comprises:

determining a deployment template in a network service description information block of the network service, wherein the deployment template comprises instance identification information of different virtual connection instances of the same type;

5. The method of claim 2, wherein said determining a traffic flow instance based on said parameter information comprises:

determining a network forwarding path in the virtual network function forwarding graph description information block, wherein the network forwarding path is used for indicating a deployment template in the network service;

and determining the service flow instance according to the network forwarding path.

6. The method of claim 2, wherein said determining a traffic flow instance based on said parameter information comprises:

determining requirement parameters of a network forwarding path in the virtual network function forwarding graph description information block, wherein the requirement parameters comprise time delay, bandwidth and jitter;

and determining the service flow instance according to the demand parameter.

7. The method according to any one of claims 2 to 6, wherein before determining the data center position for virtual network function deployment according to the remaining resource amount of each data center, the method further comprises:

according to the position of the data center, predicting the time delay generated by the service flow example, wherein the service flow example comprises at least one virtual network function forwarding graph;

when the time delay of each virtual network function forwarding graph meets the corresponding time delay requirement, sending the resource reservation request to the virtual infrastructure manager;

and when the time delay of at least one virtual network function forwarding graph does not meet the corresponding time delay requirement, executing the step of determining the position of the data center deployed for the virtual network function according to the residual resource amount of each data center.

8. A method for service quality planning based on traffic, characterized in that the method has all the features of the method of any of claims 2 to 7, and the traffic instances comprise at least two traffic network forwarding path instances;

before determining the data center position for virtual network function deployment according to the remaining resource amount of each data center, the method further includes:

sequencing the forwarding path instances of the service flow networks according to the time delay required by the forwarding path instances of the at least two service flow networks;

acquiring a deployment scheme of a service flow instance meeting the minimum time delay;

acquiring a deployment scheme of other service flow instances except the service flow instance meeting the minimum time delay from the deployment scheme of the service flow instance meeting the minimum time delay;

and determining the position of the data center for deploying the virtual network function according to the acquired deployment schemes of other service flow instances except the service flow instance meeting the minimum time delay.

9. A method for service quality planning based on traffic flows, characterized in that the method has all the features of the method of any of claims 2 to 7, and that the traffic flow instances comprise at least two traffic flow network forwarding path instances;

sequencing the forwarding path instances of the service flow networks according to the hop counts of the forwarding path instances of the at least two service flow networks;

acquiring a deployment scheme of a service flow instance meeting the maximum hop count;

acquiring a deployment scheme of other service flow instances except the service flow instance meeting the maximum hop count from the deployment scheme of the service flow instance meeting the maximum hop count;

and determining the position of the data center for the virtual network function deployment according to the acquired deployment schemes of other service flow instances except the service flow instance meeting the maximum hop count.

10. A method for service quality planning based on traffic flows, characterized in that the method has all the features of the method of any of claims 2 to 7, and that the traffic flow instances comprise at least two traffic flow network forwarding path instances;

sequencing the forwarding path instances of the service flow network with the same time delay according to the hop counts of the forwarding path instances of the at least two service flow networks;

acquiring a deployment scheme of a service flow instance meeting the minimum delay and the maximum hop count, and taking the acquired deployment scheme of the service flow instance meeting the minimum delay and the maximum hop count as a first deployment scheme;

acquiring deployment schemes of other service flow instances except the service flow instance meeting the minimum delay and the maximum hop count in the first deployment scheme, and taking the acquired deployment schemes of other service flow instances except the service flow instance meeting the minimum delay and the maximum hop count as a second deployment scheme;

11. A method for service quality planning based on traffic flows, characterized in that the method has all the features of the method of any of claims 2 to 7, and that the traffic flow instances comprise at least two traffic flow network forwarding path instances;

sequencing the forwarding path instances of the service flow network with the same hop number according to the time delay required by the forwarding path instances of the at least two service flow networks;

acquiring a deployment scheme of a service flow instance meeting the maximum hop count and the minimum time delay, and taking the acquired deployment scheme of the service flow instance meeting the maximum hop count and the minimum time delay as a first deployment scheme;

acquiring deployment schemes of other service flow instances except the service flow instance meeting the maximum hop count and the minimum delay in the first deployment scheme, and taking the acquired deployment schemes of other service flow instances except the service flow instance meeting the maximum hop count and the minimum delay as a second deployment scheme;

12. A method for traffic flow based quality of service planning, characterized in that the method has all the features of any one of claims 1 to 11, and in that said sending a resource reservation request to a virtual infrastructure manager comprises:

the resource reservation request is sent to the virtual infrastructure manager through resource reservation generation operation of a virtual resource management interface, so that the virtual infrastructure manager detects whether network resources required by virtual network function interconnection are available according to the position of a data center of the virtual network function, when the network resources required by the virtual network function interconnection are available, the virtual infrastructure manager reserves the network resources required by the virtual network function interconnection, the virtual infrastructure manager performs pretesting on the reserved network resources, and when the service quality of virtual connection meets the requirement, the virtual infrastructure manager feeds back successful resource reservation response information.

13. A method for traffic flow based quality of service planning, characterized in that the method has all the features of the method of any of claims 1 to 12, and in that said sending a resource reservation request to a virtual infrastructure manager comprises:

when a pre-distributed virtual network function instance list is determined and the virtual network function instance list comprises at least one virtual network function instance, detecting whether resources required by instantiation of the virtual network function are effective or not according to the position of a data center of the virtual network function;

when the virtual network function instantiation required resource is effective, the resource reservation request is sent to the virtual infrastructure manager.

14. A method for traffic flow based quality of service planning, characterized in that it has all the features of the method of any of claims 1 to 13, and in that said sending of an instantiation request for said virtual connection to said virtual infrastructure manager comprises:

sending a virtual connection network connection instantiation request to the virtual infrastructure manager through resource application or resource updating operation of a virtual resource management interface so that the virtual infrastructure manager instantiates a connection network required by the network service.

15. A method for traffic flow based quality of service planning, characterized in that the method has all the features of the method of any one of claims 1 to 14, and in that said sending of an instantiation request for said virtual network function to said virtual infrastructure manager comprises:

sending a virtual network function network connection instantiation request to the virtual infrastructure manager through resource application or resource updating operation of a virtual resource management interface so that the virtual infrastructure manager is connected with an external interface of the virtual network function and a required virtual deployment unit is connected to a connection network required by the network service.

16. A method for service quality planning based on traffic flow, the method having all the features of any one of claims 1 to 14, and the method further comprising, after receiving resource reservation success response information fed back by the virtual infrastructure manager in response to the resource reservation request:

when a pre-allocated virtual network function instance list is determined and the virtual network function instance list comprises at least one virtual network function instance, adding position parameter information in the operation process of calling the instantiated virtual network function of a virtual network function lifecycle management interface, wherein the position parameter information comprises the data center position of the virtual network function so as to instantiate the virtual network function.

17. A method for traffic flow based quality of service planning, characterized in that the method has all the features of the method of any one of claims 1 to 16, and in that the method further comprises:

and when receiving a capacity expansion request or a capacity reduction request for the network service, performing capacity expansion or capacity reduction on the network service at a position corresponding to a network element related to the network service.

18. A method for traffic flow based quality of service planning, characterized in that the method has all the features of the method of any one of claims 1 to 16, and in that the method further comprises:

when a capacity expansion request for the network service is received, determining that the residual resource amount of a data center where the virtual network function is located is smaller than a preset threshold value;

an instantiation request for the network traffic is generated.

19. A method for service quality planning based on traffic flows, the method having all the features of any one of claims 1 to 18, and the method further comprising, after determining a data center location for virtual network function deployment based on the remaining resource amount of each data center:

and determining the data center position of the virtual connection according to the data center position of the virtual network function.

20. The method of claim 19, wherein determining the data center location of the virtual connection based on the data center location of the virtual network function comprises:

when two virtual network functions are deployed in a data center managed by the same virtual infrastructure manager, the data center position of virtual connection between the two virtual network functions is the same as the data center position of the two virtual network functions;

when two virtual network functions are deployed in data centers managed by different virtual infrastructure managers, the data center location of the virtual connection between the two virtual network functions is determined by the wide area network infrastructure manager.

21. A method for service quality planning based on traffic flows, the method having all the features of any one of claims 1 to 20, and the method further comprising, after determining a data center location for virtual network function deployment based on the remaining resource amount of each data center:

sending a resource reservation request to a wide area network infrastructure manager, the resource reservation request indicating reservation of network resources required by a virtual private network;

when receiving resource reservation success response information fed back by the wide area network infrastructure manager in response to the resource reservation request, sending an instantiation request of the virtual private network to the wide area network infrastructure manager;

receiving instantiation response information fed back by the wide area network infrastructure manager in response to the instantiation request of the virtual private network.

22. The method of claim 21, wherein said sending a resource reservation request to a wide area network infrastructure manager comprises:

sending the resource reservation request to a wide area network infrastructure manager so that the wide area network infrastructure manager detects whether virtual private network resources between the data centers are available according to the data center positions of the virtual network functions, when the virtual private network resources between the data centers are available, reserving the virtual private network resources between the data centers by the wide area network infrastructure manager, pre-testing the reserved network resources by the wide area network infrastructure manager, and when the service quality of the virtual private network meets the requirement, feeding back resource reservation success response information by the wide area network infrastructure manager.

23. The method of claim 21 or 22, wherein said sending an instantiation request for the virtual private network to the wide area network infrastructure manager comprises:

and sending a virtual private network connection instantiation request to the wide area network infrastructure manager through resource application or resource updating operation of a virtual resource management interface so that the wide area network infrastructure manager instantiates a connection network required by network service.

24. A service flow-based qos planning apparatus, comprising:

a request receiving unit for receiving an instantiation request for a network service;

the position determining unit is used for determining the position of the data center deployed for the virtual network function according to the residual resource amount of each data center;

a request sending unit, configured to send a resource reservation request to a virtual infrastructure manager, where the resource reservation request is used to instruct the virtual infrastructure manager to reserve network resources required by the virtual connection and the virtual network function according to a location of a data center of the virtual network function;

the request sending unit is further configured to send an instantiation request for the virtual connection and a virtual network function to the virtual infrastructure manager when receiving resource reservation success response information fed back by the virtual infrastructure manager in response to the resource reservation request;

an information receiving unit, configured to receive instantiation response information fed back by the virtual infrastructure manager in response to the instantiation request for the virtual connection and the virtual network function.

25. The apparatus of claim 24, wherein the instantiation request carries parameter information, the apparatus further comprising:

and the example determining unit is used for determining the service flow example according to the parameter information after the request receiving unit receives the instantiation request of the network service.

26. The apparatus of claim 25, wherein the instance determination unit is specifically configured to:

27. The apparatus of claim 25, wherein the instance determination unit is specifically configured to:

28. The apparatus of claim 25, wherein the instance determination unit is specifically configured to:

29. The apparatus of claim 25, wherein the instance determination unit is specifically configured to:

and determining the service flow instance according to the demand parameter.

30. The apparatus of any one of claims 25 to 29, further comprising:

a delay pre-estimating unit, configured to pre-estimate, by the location determining unit, a delay to be generated by the service flow instance according to the location of the data center before determining, according to the remaining resource amount of each data center, the location of the data center deployed for the virtual network function, where the service flow instance includes at least one virtual network function forwarding graph;

the request sending unit is further configured to send the resource reservation request to the virtual infrastructure manager when the time delay of each virtual network function forwarding graph meets a corresponding time delay requirement;

the position determining unit is further configured to, when the time delay of at least one virtual network function forwarding graph does not meet the corresponding time delay requirement, execute the determining according to the remaining resource amount of each data center, and determine the data center position deployed for the virtual network function.

31. An apparatus for traffic-based quality of service planning, wherein the apparatus has all the features of the apparatus of any one of claims 25 to 30, and wherein the traffic instances comprise at least two traffic network forwarding path instances;

the position determining unit is specifically configured to:

32. An apparatus for traffic-based quality of service planning, wherein the apparatus has all the features of the apparatus of any one of claims 25 to 30, and wherein the traffic instances comprise at least two traffic network forwarding path instances;

the position determination unit is further configured to:

33. An apparatus for traffic-based quality of service planning, wherein the apparatus has all the features of the apparatus of any one of claims 25 to 30, and wherein the traffic instances comprise at least two traffic network forwarding path instances;

the position determination unit is further configured to:

34. An apparatus for traffic-based quality of service planning, wherein the apparatus has all the features of the apparatus of any one of claims 25 to 30, and wherein the traffic instances comprise at least two traffic network forwarding path instances;

the position determination unit is further configured to:

35. An apparatus for traffic flow based quality of service planning, characterized in that the apparatus has all the features of the apparatus of any of claims 24 to 34, and in that the request sending unit sends a resource reservation request to the virtual infrastructure manager, in particular for:

36. An apparatus for traffic flow based quality of service planning, characterized in that the apparatus has all the features of the apparatus of any of claims 24 to 35, and in that the request sending unit sends a resource reservation request to the virtual infrastructure manager, in particular for:

37. An apparatus for traffic-based quality of service planning, characterized in that the apparatus has all the features of the apparatus of any of claims 24 to 36, and in that the request sending unit sends to the virtual infrastructure manager an instantiation request for the virtual connection, in particular for:

38. An apparatus for traffic-based quality of service planning, characterized in that the apparatus has all the features of the apparatus of any of claims 24 to 37, and in that the request sending unit sends to the virtual infrastructure manager an instantiation request for the virtual network function, in particular for:

39. An apparatus for traffic-based quality of service planning, characterized in that the apparatus has all the features of the apparatus of any one of claims 24 to 37, and in that the apparatus further comprises:

an instantiation unit, configured to, after receiving resource reservation success response information fed back by the virtual infrastructure manager in response to the resource reservation request, when a pre-allocated virtual network function instance list is determined and the virtual network function instance list includes at least one virtual network function instance, add location parameter information in an operation process of invoking an instantiated virtual network function of a virtual network function lifecycle management interface, where the location parameter information includes a data center location of the virtual network function, so as to instantiate the virtual network function.

40. An apparatus for traffic-based quality of service planning, characterized in that the apparatus has all the features of the apparatus of any one of claims 24 to 39, and in that the apparatus further comprises:

and the expansion and contraction unit is used for expanding or contracting the network service at the corresponding position of the network element related to the network service when receiving an expansion request or a contraction request of the network service.

41. An apparatus for traffic-based quality of service planning, characterized in that the apparatus has all the features of the apparatus of any one of claims 24 to 39, and in that the apparatus further comprises:

a resource amount determining unit, configured to determine that, when a capacity expansion request for the network service is received, a remaining resource amount of a data center where the virtual network function is located is smaller than a preset threshold;

a request generating unit for generating an instantiation request for the network service.

42. An apparatus for traffic-based quality of service planning, characterized in that the apparatus has all the features of the apparatus of any one of claims 24 to 41 and,

the position determining unit is further configured to determine the data center position of the virtual connection according to the data center position of the virtual network function after determining the data center position of the virtual network function deployment according to the remaining resource amount of each data center.

43. The apparatus according to claim 42, wherein the location determining unit is configured to determine, based on the data center location of the virtual network function, the data center location of the virtual connection, and is specifically configured to:

44. An apparatus for traffic-based quality of service planning, characterized in that the apparatus has all the features of the apparatus of any one of claims 24 to 43 and,

the request sending unit is further configured to send a resource reservation request to a wide area network infrastructure manager after the location determining unit determines the location of the data center deployed for the virtual network function according to the remaining resource amount of each data center, where the resource reservation request is used to indicate that network resources required by the virtual private network are reserved;

the request sending unit is further configured to send an instantiation request for the virtual private network to the wide area network infrastructure manager when receiving resource reservation success response information fed back by the wide area network infrastructure manager in response to the resource reservation request;

the information receiving unit is further configured to receive instantiation response information fed back by the wide area network infrastructure manager in response to the instantiation request for the virtual private network.

45. The apparatus as claimed in claim 44, wherein the request sending unit sends the resource reservation request to the WAN infrastructure manager by:

46. The apparatus according to claim 44 or 45, wherein the request sending unit sends the instantiation request of the virtual private network to the wide area network infrastructure manager, which may be specifically:

47. A computer-readable storage medium, characterized in that it stores a computer program which, when executed by hardware, is capable of implementing the method of any one of claims 1 to 23.