WO2007019788A1

WO2007019788A1 - A method and a system for realizing pipe model based on differentiated services

Info

Publication number: WO2007019788A1
Application number: PCT/CN2006/002017
Authority: WO
Inventors: Gang Cheng
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2005-08-19
Filing date: 2006-08-10
Publication date: 2007-02-22
Also published as: CN1917440A; CN100514912C

Abstract

A method and a system for realizing pipe model based on differentiated services. The kernel of the method includes: Pipe connection management information based on differentiated services is set in VPN-CRC; and VPN-CRC controls the VPN-LBN to carry out Pipe connection management according to the connection management information and Pipe request based on differentiated services from the entrance PE of VPN-LBN. The invention performs pipe connection menagement such as creating pipe connection, repealing pipe connection and so on by using VPN-CRC and VPN-LBN architecture to make sure Qos of VPN services sufficiently, thus realizing the objects of perfecting pipe model realizing method and assuring Qos of VPN services.

Description

Method and system for realizing pipeline model based on differentiated service

The present invention relates to the field of network communication technologies, and in particular, to a method and system for implementing a service model based on a differentiated service.

Background technique

DiffServ (Differentiated Services) technology is proposed by the IETF (Internet Engineering Task Force), also known as the differentiated service model.

The basic idea of the differentiated service model is: classify each packet at the entrance of the network, and mark the corresponding DSCP (DiffServ CodePoint) in the packet to indicate that the packet is inside the network forwarding path. The way the node is processed. The internal node, such as the core router inside the network, only stores the simple DSCP and PHB (per-hop behavior) corresponding mechanism. The core router forwards the data packet according to the DSCP value in the packet header, and the service flow status information The preservation and implementation of the flow control mechanism are performed at the network boundary node, and the internal nodes are independent of the service flow state.

Because the differentiated service has the characteristics of simple implementation and good extensibility, it has been supported by most manufacturers in the IP network. The specific implementation technologies include classification, re-marking, rate limiting, traffic shaping, congestion avoidance, and queue scheduling.

The Pipe model is one of the two VPN service models proposed in the draft standard Y.vpn-qos of ITU-T SG13/Q2. According to the definition of the Pipe model in Y.vpn-qos, the Pipe model is used to ensure point-to-point connection. QoS (Service Quality of Service), VPN users specify the QoS requirements of the Pipe Model network path between VPN endpoints. In the Pipe path between each group of VPN endpoints, the network service provider needs to provide sufficient service bandwidth to ensure that user QoS requirements can be achieved. The resources allocated by the network service provider for the Pipe cannot be used for other traffic. Users need to provide destination-based traffic shaping on the CE (Customer Edge) to ensure the implementation of QoS requirements.

In the draft of Y.vpn-qos published by ITU-T SG13/Q2 in May 2005, it is proposed that the service pipe model in the VPN QoS framework structure can be constructed by DiffServ and InterServ technologies, but no specific implementation method or processing is provided. The description of the process and related technologies is a problem that needs further discussion and needs to be further studied and supplemented. Summary of the invention

The object of the present invention is to provide a method for implementing a service model based on a differentiated service, which utilizes a VPN-CRC and a VPN-LBN architecture to perform Pipe connection management, and improves a service Pipe model in a VPN QoS framework structure.

To achieve the above objective, the present invention provides a method for implementing a differentiated service based Pipe model, including:

a. setting the service connection information based on the differentiated service in the VPN-CRC (VPN centralized resource controller);

b. The VPN-CRC controls the VPN-LBN to perform Pipe connection management according to the connection management information and the service-based Pipe request transmitted by the ingress PE device in the VPN-LBN (VPN Bearer Network).

The Pipe connection management is: creating a management based on the service of the differentiated service; and the step a includes:

The correspondence between the user QoS parameters and the differentiated service QoS parameters is set in each VPN-CRC. The step b specifically includes:

Bl, the ingress PE device transmits the service-based Pipe creation request that carries the user QoS parameter transmitted by the CE device to each VPN-CRC corresponding to the Pipe to be created;

B2. Each VPN-CRC maps a user QoS parameter in the Pipe Creation Request to a differentiated service QoS parameter according to the correspondence relationship;

B3. Each VPN-CRC determines, according to the mapped differentiated service QoS parameter, an allocatable resource corresponding to the Pipe creation request;

B4. Each VPN-CRC determines that a pipe is allowed to be created according to the allocatable resources, and the corresponding pipe creation parameter is transmitted to the ingress PE device, and each VPN-CRC is respectively configured in the VPN-LBN corresponding to the pipe creation request. Intermediate nodes;

B5. The ingress PE device establishes a differentiated service based Pipe connection according to the creation parameters it receives.

The step b3 includes -

The VPN-CRC calculates the resource according to the mapped differentiated service QoS parameter, and determines the allocatable resource corresponding to the pipe creation request according to the resource calculation result. The method further includes:

Set a pipe resource pool and a common resource pool in the VPN-CRC;

The Pipe resource pool is pre-set with the Pipe resource information corresponding to each dynamically differentiated QoS parameter;

And the step b3 includes:

The VPN-CRC determines, according to the mapped differentiated service QoS parameter, whether the Pipe resource pool has the Pipe resource information matched thereto;

If yes, the VPN-CRC determines the matched Pipe resource information as an allocatable resource corresponding to the Pipe creation request;

If not, the VPN-CRC performs resource calculation according to the mapped differentiated service QoS parameter, and determines an allocatable resource corresponding to the Pipe creation request according to the common resource pool and the resource calculation result.

The step b3 further includes:

When it is determined that there is no allocateable resource corresponding to the pipeline creation request according to the resource calculation result, the rejection information of the Pipe creation request is transmitted to the ingress PE device, and the ingress PE device ends the pipeline creation management process based on the differentiated service, and the method ends.

The pipeline creation parameter includes: a creation parameter of the pipeline in each VPN-CRC local domain; and the step b4 further includes:

Each VPN-CRC saves the creation parameters of the Pipe in this domain.

The Pipe creation parameters include: global path information and mapped differentiated service QoS parameters. The step b5 specifically includes:

The ingress PE device stores the full path information and the mapped differentiated service QoS parameter in the QoS path information table, and sets an EXP bit group for the label stack transmitted by the VPN-CRC;

The ingress PE device sends the information that the Pipe successfully establishes to the corresponding CE device, and forwards the data packet according to the content in the path information table and the EXP bit group.

The Pipe connection management is: a service-based Pipe revocation management; and the step a includes:

Set the creation parameters of the Pipe in this domain in each VPN-CRC.

The creation parameters of the Pipe in the local domain include: path information of the Pipe in the VPN-CRC local domain and mapped differentiated service QoS parameters. The step b specifically includes:

Bl', the ingress PE device transmits the service-based Pipe revocation request transmitted by the CE device to each VPN-CRC corresponding to the Pipe;

B2', each VPN-CRC determines the local domain path information corresponding to the revocation request and the mapped differentiated service QoS parameter, and releases the resource, and simultaneously transmits the Pipe resource release message to the ingress PE device;

B3'. The ingress PE device deletes the corresponding record in the QoS path information table according to the resource release message it receives.

When the Pipe resource released by the VPN-CRC is a Pipe resource in the Pipe resource pool, the released Pipe resource is recycled to the Pipe resource pool of the VPN-CRC;

When the pipe resource released by the VPN-CRC is a resource in the common resource pool, the released Pipe resource is recycled to the public resource pool of the VPN-CRC.

Another object of the present invention is to provide a system for implementing a service model based on a differentiated service. Pipeline management is implemented by using a VPN-CRC and a VPN-LBN architecture, and a service pipe model in a VPN QoS framework structure is improved.

In order to achieve the above other object, the present invention provides a system for implementing a service-based Pipe model, which is characterized in that: a CE device in a VPN bearer network is used to send a differentiated service-based pipe creation request; a VPN bearer network An ingress PE device, configured to transmit a pipe creation request from the CE device; and a VPN centralized resource controller, where the service connection based pipe connection management information is set, and according to the connection management information, the VPN bearer The service-based pipe request transmitted by the ingress PE device in the network controls the VPN bearer network to perform pipe connection management.

According to the description of the foregoing technical solution, the present invention can ensure the QoS of the VPN service by using the VPN-CRC and the VPN-LBN architecture to perform the pipe connection management, such as creating a pipe connection and revoking the pipe connection. The simplification of setting the pipe resource pool is simplified. The network resource allocation processing process improves the allocation efficiency of the network resources; thus, the technical solution provided by the present invention achieves the purpose of perfecting the Pipe model implementation method and ensuring the VPN service QoS.

DRAWINGS

Figure 1 is a schematic diagram of a QoS-VPN system model;

2 is a flow chart of a differentiated service based pipe connection creation of the present invention. detailed description

The core of the present invention is: setting differentiated service-based pipe connection management information in a VPN-CRC, and the VPN-CRC is based on the connection management information and the ingress PE (service provider device) device in the VPN-LBN based on the distinction The Pipe request of the service controls the pipe connection management.

The technical solution provided by the present invention is further described below based on the core idea of the present invention. MPLS BVPN (Network Based Virtual Private Network) is a kind of architecture that fully guarantees the QoS of VPN services on MPLS networks. MPLS NBVPN is pre-configured by MPLS technology in the basic IP network. A part of the resources are used by the QoS-VPN. This part of the resource is called a VPN-LBN (VPN Logical Bearer Network) resource, and a control network element, such as a VPN-CRC (VPN Centralized Resource Controller), is added to the current VPN reference model. Maintain the network topology and resources of the VPN-LBN, and the membership information and access relationship information of each QoS-VPN, and perform admission control and path calculation according to the logical bearer network resource status to ensure that the accessed services can obtain their desired information. Quality of Service, Centralized Resource Control QoS MPLS NBVPN is a hierarchical structure that avoids the flattened structure of VPNs, as well as VPN resources and other service sharing resources, and there is a resource competition mechanism between different VPNs.

The QoS-VPN framework is divided into two levels: the bearer layer and the bearer control layer, and the architecture of the QoS-VPN framework (the system that implements the service-based Pipe model). Show.

In Figure 1, the cylindrical icon represents VPN-CRC, the solid black dot indicates PE, the slashed circle indicates ITR (intermediate transmission router), the hollow circle indicates CR (core router), and the square icon indicates CE ( User equipment), the black dotted line indicates the reserved bandwidth LSP.

The VPN-LBN is formed by using the MPLS technology to configure the reserved bandwidth LSP connection PE, CR, and ITR according to the pre-capacity planning. The VPN bearer control layer is composed of a VPN-CRC, and each domain is managed by a VPN-CRC. - CRC manages VPN-LBN network resources such as bandwidth, processor capacity, queue buffer, etc. The VPN CRC can maintain the VPN-LBN network topology. The VPN-CRC can also perform resource calculation, path selection, and send path indication to PE devices. At the same time, the VPN-CRC can allocate resources in the VPN-LBN to implement access control, and maintain a membership information table, a connection relationship information table, and related signaling for each QoS-VPN, so as to implement automatic membership discovery and Single side configuration.

The present invention is a QOS-VPN service architecture in MPLS NBVPN based on centralized resource control to guarantee QoS.

The present invention firstly needs to set the pipe connection management information based on the differentiated service in the VPN-CRC, and the VPN-CRC performs Pipe connection management on the request related to the service-based Pipe connection transmitted from the PE device according to the connection management information. The following is a detailed description of the DiffServ-based Create Pipe Connection Management and Undo Pipe Connection Management of the present invention by taking a service-based Pipe Creation Request and a DiffServ-based Pipe Revocation Request as an example.

When the differentiated service-based Create Pipe connection process is implemented, the differentiated service-based Pipe connection management information preset in each VPN-CRC is: a correspondence between a user QoS parameter and a differentiated service QoS parameter. The user QoS parameters are user-requested QoS parameters, user QoS parameters such as bandwidth, delay, jitter limit, and loss rate limit. Differentiated service QoS parameters such as traffic classification, re-marking, rate limiting, traffic shaping, congestion avoidance, Queue scheduling, etc.

The main process of implementing a differentiated service-based creation Pipe connection is shown in Figure 2:

In FIG. 2, in step 200, the CE device sends a differentiated service-based Pipe creation request to the ingress PE device, where the Pipe creation request carries the QoS parameter requested by the user.

Go to step 210, the ingress PE device transmits the received pipe creation request to the VPN-CRC of the domain in which it is located, and the VPN-CRC of the domain where the ingress PE device is located transmits the received pipe creation request to the VPN related to the pipe to be created. - CRC, that is, if the pipe needs to be established across domains, the pipe creation request needs to be separately transmitted to the VPN-CRC of the domain where the PE device is located at both ends of the pipe and the VPN-CRC _{Q of the} intermediate spanning domain.

In step 220, after receiving the pipe creation request, each VPN-CRC related to the pipe to be created first needs to map the QoS parameters required by the user in the pipe creation request to the differentiated service QoS parameters according to the foregoing correspondence, that is, the user The required QoS parameters are mapped to specific differentiated service QOS functions.

To step 230, each VPN-CRC completes the resource and path selection process that needs to be allocated according to the specific differentiated service QOS function.

There are two main methods for determining the resources to be allocated according to the specific differentiated service QOS function of the VPN-CRC. First, the resource calculation is performed according to the mapped differentiated service QoS parameters to determine the need to allocate. resource of. Second, determine the resources that need to be allocated according to the Pipe resources in the preset Pipe resource pool.

The Pipe resource pool is a resource allocation method proposed by the present invention to facilitate allocation of each VPN-CRC resource. The VPN-CRC can divide the resources it manages into two parts: the Pipe resource pool and the common resource pool. The Pipe resource pool is pre-configured with dynamically assignable and different specifications of Pipe resources. Pipe resources of different specifications correspond to different differentiated service QoS parameters. Pipe resources of different specifications can be pre-customized by network service providers according to customer characteristics.

After receiving the PP creation request, the VPN-CRC first maps the user QoS parameters carried in the Pipe Creation Request to the differentiated service QoS parameters, and then searches the Pipe resource pool for the Pipe resource that most closely matches the differentiated service QoS parameter. When the matching pipe resource is found, the pipe resource is determined as the pipe resource to be allocated. If no matching pipe resource is found, the VPN-CRC performs resource calculation according to the differentiated service QoS parameter, and the public resource is calculated according to the resource calculation result. Identify the Pipe resources that need to be allocated in the pool. The invention simplifies the network resource allocation processing process through the Pipe resource pool, and improves the distribution efficiency of the network resources.

In step 240, according to the method for determining the resources to be allocated, each VPN-CRC performs the permission control, that is, whether it is possible to allocate resources for the Pipe creation request, and if a VPN-CRC cannot allocate resources for the Pipe creation request, If the result of the resource calculation is "Reject", then to step 241, the VPN-CRC needs to transmit the rejected response message to its upstream VPN-CRC until it is transmitted to the ingress PE device. Go to step 260.

In step 240, if each VPN-CRC can allocate resources for the Pipe creation request, for example, each VPN-CRC can allocate resources for the Pipe creation request from the Pipe resource pool, or the resource calculation result is “Allowed”, then the steps are up. 250. Each VPN-CRC needs to transmit its determined creation parameters to the ingress PE device, such as the path information and the differentiated service QoS parameters that meet the requirements of the user QoS parameters are sent to the ingress PE device. Each VPN-CRC also needs to complete the configuration process of the corresponding intermediate node in the domain, that is, the entire path information is also notified to the intermediate node. The path information is, for example, a label stack.

Each VPN-CRC can transmit its determined creation parameters to its upstream VPN-CRC through a response message carrying an "Allow" until it is transmitted to the ingress PE device. Go to step 260.

At step 260, the ingress PE device receives the response message and determines if the response message is carried in the message If the information is "allowed", then in step 270, the ingress PE device obtains the VPN-CRC creation parameters, that is, the full path information and the differentiated service QoS parameter, from the response message, and records the information in the QoS path information table. The EXP group is set for the label stack transmitted by the VPN-CRC. At the same time, the ingress PE device sends a PP creation request success message to the CE device requester, and ends the CE device request to create a Pipe process.

In this way, the ingress PE device can perform traffic classification, queue scheduling, shaping, labeling, MPLS encapsulation on the user traffic according to the content in the QoS path information table, and determine the forwarding path according to the label stack in the EXP bit group.

In step 260, if the ingress PE device receives the response message carrying the "reject" message, then to step 261, the ingress PE device sends a pipe creation request failure message to the CE device requester, and ends the CE device request to create the pipe process.

In the implementation of the differentiated service-based revoked pipe connection process, the pre-set service-based pipe connection management information in each VPN-CRC is: a pipe-created parameter in the VPN-CRC local domain, such as the path information of the pipe in the domain. The mapped differentiated service QoS parameters may be established during the above-described differentiated service based split pipe connection process.

Implementing a differentiated service-based revocation Pipe connection mainly includes the following process - the user CE device sends a DiffServ-based Pipe revocation request to each VPN-CRC related to the Pipe connection that needs to be revoked through the ingress PE device.

After receiving the differentiated service-based PP revocation request of the user CE device, each VPN-CRC searches for a pipe creation parameter in the VPN-CRC local domain corresponding to the differentiated service-based PP revocation request, such as the full path information and the differentiated service QoS parameter. After the pipe creation parameter in the corresponding VPN-CRC domain is found, the release of the allocated resource is completed, and after the resource release is completed, the information about the completion of the resource release is directly transmitted to the ingress PE device through the upstream VPN-CRC. .

If the resource released by the VPN-CRC is a pipe resource allocated from the pipe resource pool, the released resource is reclaimed into the pipe resource pool. If the resource released by the VPN-CRC is a resource allocated from the public resource pool, This released resource is still recycled to the public resource pool for future use.

After receiving the information about the completion of the resource release from the VPN-CRC transmission, the ingress PE device deletes the saved creation parameters of the pipe, such as deleting the corresponding full path information in the QoS path information table. The service QoS parameter is differentiated, and when the record is deleted, the CE device requester sends the information of the cancellation request completion, and the CE device requests to cancel the Pipe process.

While the invention has been described by the embodiments of the present invention, it will be understood that

Claims

Claim

A method for implementing a service-based Pipe model, comprising: a: setting a service connection-based pipe connection management information in a VPN centralized resource controller; b, a VPN-CRC according to the connection management information The service-based Pipe request transmitted by the ingress PE device in the VPN bearer network controls the VPN-LBN to perform pipe connection management.

The method for implementing a differentiated service based Pipe model according to claim 1, wherein the Pipe Connection Management is a service based management of a differentiated service; and in the step a, based on a differentiated service The pipe connection management information includes a correspondence between a user QoS parameter and a differentiated service QoS parameter.

3. The method for implementing a service-based pipeline model according to claim 2, wherein the step b specifically comprises:

Bl, the ingress PE device transmits the service-differentiated Pipe creation request carrying the user QoS parameter transmitted by the CE device to each VPN centralized resource controller corresponding to the Pipe to be created;

B2. The VPN centralized resource controller maps the user QoS parameter in the Pipe creation request to the differentiated service QoS parameter according to the correspondence relationship;

B3. Each VPN centralized resource controller determines, according to the mapped differentiated service QoS parameter, an allocatable resource corresponding to the Pipe creation request.

B4. Each VPN centralized resource controller transmits a corresponding pipe creation parameter to the ingress PE device when the assignable resource is determined to be allowed to create a pipe, and each VPN centralized resource controller separately configures the corresponding pipe creation request. Each intermediate node in the VPN centralized resource controller;

The method for implementing a service-based pipeline model according to claim 3, wherein the step b3 comprises:

The VPN centralized resource controller performs resource calculation according to the mapped differentiated service QoS parameter, and determines an allocatable resource corresponding to the Pipe creation request according to the resource calculation result.

The method for implementing a service-based Pipe model according to claim 3, wherein the method further comprises: Setting a pipe resource pool and a common resource pool in the VPN centralized resource controller;

And the step b3 includes:

The VPN centralized resource controller determines, according to the mapped differentiated service QoS parameter, whether the Pipe resource pool has matching Pipe resource information;

If yes, the VPN centralized resource controller determines the matched Pipe resource information as an allocatable resource corresponding to the Pipe creation request;

If not, the VPN centralized resource controller performs resource calculation according to the mapped differentiated service QoS parameter, and determines the allocatable resource corresponding to the Pipe creation request according to the common resource pool and the resource calculation result.

A method for implementing a service-based pipeline model according to claim 4 or 5, wherein the step b3 further comprises:

When it is determined that there is no allocateable resource corresponding to the Pipe creation request according to the resource calculation result, the rejection information of the Pipe creation request is transmitted to the ingress PE device, and the ingress PE device ends the management process based on the DiffServ pipeline.

The method for implementing a service-based Pipe model according to claim 3, 4 or 5, wherein the Pipe creation parameter comprises: a creation parameter of a Pipe in a domain of each VPN centralized resource controller ;

And the step b4 further includes:

Each VPN centralized resource controller saves the creation parameters of the Pipe in this domain.

8. A method for implementing a service-based Pipe model according to claim 3, 4 or 5, wherein the Pipe creation parameters comprise: full path information and mapped Differentiated Service QoS parameters.

The method for implementing a service-based pipeline model according to claim 8, wherein the step b5 specifically includes:

The ingress PE device stores the global path information and the mapped differentiated service QoS parameter in the QoS path information table, and sets an EXP bit group for the label stack in the path information transmitted by the VPN centralized resource controller; The ingress PE device sends the information that the PP successfully establishes to the corresponding CE device, and forwards the data packet according to the content in the path information table and the EXP bit group.

10. A method of implementing a differentiated service based Pipe model according to any one of claims 1 to 5, characterized in that

In the case of establishing a differentiated service-based Pipe connection according to the above steps a and b, the CE device further requests to perform a differentiated service-based Pipe revocation management, wherein each of the VPN centralized resource controllers has separately set the established Pipe in the local domain. Create parameters in .

The method for implementing a differentiated service-based Pipe model according to claim 10, wherein the creating parameters of the Pipe in the local domain comprise: path information of a pipe in a VPN centralized resource controller domain And mapped differentiated service QoS parameters.

12. The method for implementing a differentiated service-based Pipe model according to claim 11, wherein the differentiated service-based pipe revocation management specifically comprises: -b Γ, the ingress PE device transmits the CE device based on the differentiated service The PP revocation request is transmitted to each VPN centralized resource controller corresponding to the Pipe;

B2\each VPN centralized resource controller determines the local domain path information corresponding to the revocation request and the mapped differentiated service QoS parameter, and releases the resource, and simultaneously transmits the Pipe resource release message to the ingress PE device;

B3 ', the ingress PE device deletes the corresponding record in the QoS path information table according to the resource release message it receives.

13. A method of implementing a differentiated service based Pipe model as claimed in claim 12, wherein:

When the pipe resource released by the VPN centralized resource controller is a Pipe resource in the Pipe resource pool, the released Pipe resource is recycled to the Pipe resource pool of the VPN centralized resource controller;

When the pipe resource released by the VPN centralized resource controller is a resource in the common resource pool, the released Pipe resource is recycled to the common resource pool of the VPN centralized resource controller.

A system for implementing a service-based Pipe model, comprising: a CE device in a VPN bearer network, configured to send a differentiated service-based pipe creation request; and an ingress PE device in the VPN bearer network, configured to a pipe creation request from the CE device for transmission; a VPN centralized resource controller, where a service-based pipe connection management information is set, and the VPN bearer network is controlled according to the connection management information and the service-based Pipe request transmitted by the ingress PE device in the VPN bearer network. Pipe connection management.

15. A system for implementing a differentiated service based Pipe model according to claim 14, wherein said Pipe Connection Management creates management for a differentiated service based Pipe;

In the VPN centralized resource controller, the differentiated service-based Pipe connection management information includes a correspondence between a user QoS parameter and a differentiated service QoS parameter.

16. A system for implementing a differentiated service based Pipe model as claimed in claim 15 wherein:

The ingress PE device transmits a service-differentiating Pipe creation request that carries the user QoS parameter transmitted by the CE device to each VPN-CRC corresponding to the Pipe to be created;

The VPN centralized resource controller maps the user QoS parameter in the pipe creation request to the differentiated service QoS parameter according to the corresponding relationship, and determines the allocatable resource corresponding to the pipe creation request according to the mapped differentiated service QoS parameter, and is assignable When the resource is determined to be allowed to create a pipe, the corresponding pipe creation parameter is transmitted to the ingress PE device, and each intermediate node in the VPN bearer network corresponding to the pipe creation request is respectively configured;

The ingress PE device establishes a differentiated service based Pipe connection based on the creation parameters it receives.

17. A system for implementing a differentiated service based Pipe model as claimed in claim 16 wherein:

In the case of determining the allocatable resource corresponding to the pipeline creation request, the VPN centralized resource controller performs resource calculation according to the mapped differentiated service QoS parameter, and determines the allocatable resource corresponding to the pipeline creation request according to the resource calculation result.

18. A system for implementing a differentiated service based Pipe model according to claim 16 wherein:

a pipeline resource pool and a common resource pool are further configured in the VPN centralized resource controller; the pipeline resource pool corresponding to the dynamically allocated power service QoS parameters is preset in the pipeline resource pool;

And determining, in the case of determining the allocatable resource corresponding to the pipe creation request, the VPN centralized resource controller determining, according to the mapped differentiated service QoS parameter, whether the Pipe resource pool matches the same. Pipe resource information;

19. A system for implementing a differentiated service based Pipe model according to claim 17 or claim 18, wherein

When determining the allocatable resource corresponding to the pipe creation request, the VPN centralized resource controller determines, according to the resource calculation result, that the packet creation request does not have an allocable resource corresponding to the pipe creation request, and transmits the rejection information of the pipe creation request to the ingress PE device. The differentiated service-based Pipe Creation Management Process is terminated by the ingress PE device.

The system for implementing a differentiated service-based Pipe model according to claim 17, 18 or 19, wherein the Pipe creation parameter comprises: a creation parameter of a Pipe in a domain of each VPN centralized resource controller ;

And when each VPN centralized resource controller transmits the corresponding Pipe creation parameter to the ingress PE device, the creation parameters of the Pipe in the domain are saved.

21. A system for implementing a differentiated service based Pipe model according to claim 17, 18 or 19, wherein said Pipe creation parameters comprise: full path information and mapped differentiated service QoS parameters.

22. A system for implementing a differentiated service based Pipe model according to claim 21, wherein:

When the ingress PE device establishes a differentiated service-based Pipe connection, the ingress PE device stores the global path information and the mapped differentiated service QoS parameter in the QoS path information table, and is a path transmitted by the VPN centralized resource controller. The label stack in the message sets the EXP bit group;

23. A system for implementing a differentiated service based Pipe model according to any one of claims 14 to 18, characterized in that In the case that the ingress PE device establishes a service-based pipe connection, the CE device further requests to perform a differentiated service-based pipe revocation management, wherein each of the VPN centralized resource controllers has separately set the established Pipe in the domain. Create parameters.

24. The system for implementing a differentiated service based Pipe model according to claim 23, wherein the creating parameters of the Pipe in the local domain comprise: path information of a pipe in a VPN centralized resource controller local domain. And mapped differentiated service QoS parameters.

25. A system for implementing a differentiated service based Pipe model according to claim 24, wherein the differentiated service based pipe revocation management specifically comprises:

The ingress PE device transmits the service-based Pipe credit request transmitted by the CE device to each VPN centralized resource controller corresponding to the Pipe;

Each VPN centralized resource controller determines the local domain path information corresponding to the revocation request and the mapped differentiated service QoS parameter, and releases the resource, and simultaneously transmits the Pipe resource release message to the ingress PE device;

The ingress PE device deletes the corresponding record in the QoS path information table according to the resource release message it receives.

26. A system for implementing a differentiated service based Pipe model as set forth in claim 25 wherein: