WO2007019788A1 - Procede et systeme de mise en place d'un modele de tuyau d'apres la differenciation de services - Google Patents

Procede et systeme de mise en place d'un modele de tuyau d'apres la differenciation de services Download PDF

Info

Publication number
WO2007019788A1
WO2007019788A1 PCT/CN2006/002017 CN2006002017W WO2007019788A1 WO 2007019788 A1 WO2007019788 A1 WO 2007019788A1 CN 2006002017 W CN2006002017 W CN 2006002017W WO 2007019788 A1 WO2007019788 A1 WO 2007019788A1
Authority
WO
WIPO (PCT)
Prior art keywords
pipe
vpn
resource
differentiated service
service
Prior art date
Application number
PCT/CN2006/002017
Other languages
English (en)
Chinese (zh)
Inventor
Gang Cheng
Original Assignee
Huawei Technologies Co., Ltd.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Publication of WO2007019788A1 publication Critical patent/WO2007019788A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H04L47/2408—Traffic characterised by specific attributes, e.g. priority or QoS for supporting different services, e.g. a differentiated services [DiffServ] type of service

Definitions

  • 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.
  • DiffServ Differentiated Services
  • IETF Internet Engineering Task Force
  • 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.
  • 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.
  • 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.
  • 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.
  • the present invention provides a method for implementing a differentiated service based Pipe model, including:
  • VPN-CRC VPN centralized resource controller
  • 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:
  • 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;
  • Each VPN-CRC maps a user QoS parameter in the Pipe Creation Request to a differentiated service QoS parameter according to the correspondence relationship;
  • Each VPN-CRC determines, according to the mapped differentiated service QoS parameter, an allocatable resource corresponding to the Pipe creation request;
  • 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.
  • 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:
  • the Pipe resource pool is pre-set with the Pipe resource information corresponding to each dynamically differentiated QoS parameter;
  • 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;
  • the VPN-CRC determines the matched Pipe resource information as an allocatable resource corresponding to the Pipe creation request
  • 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:
  • 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:
  • 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:
  • the ingress PE device transmits the service-based Pipe revocation request transmitted by the CE device to each VPN-CRC corresponding to the Pipe;
  • 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;
  • the ingress PE device deletes the corresponding record in the QoS path information table according to the resource release message it receives.
  • 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
  • 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.
  • 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.
  • 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.
  • Figure 1 is a schematic diagram of a QoS-VPN system model
  • FIG. 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.
  • MPLS BVPN Network Based Virtual Private Network
  • 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.
  • VPN-LBN VPN Logical Bearer Network
  • VPN-CRC VPN Centralized Resource Controller
  • 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.
  • 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)
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • each VPN-CRC completes the resource and path selection process that needs to be allocated according to the specific differentiated service QOS function.
  • 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.
  • the VPN-CRC 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • each VPN-CRC 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. .
  • 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.
  • the ingress PE device 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

Ce procédé de mise en place d'un modèle de tuyau d'après la différenciation des services consistent essentiellement: définir l'information de gestion de la connexion du tuyau d'après la différenciation des services dans VPN-CRC et assurer le contrôle par VPN-CRC de VPN-LBN pour gérer la connexion de tuyau selon l'information de gestion de connexion et la demande de tuyau d'après la différenciation des services selon l'entrée PE de VPN-LBN. La gestion de connexion de tuyau comprend notamment la création de connexion de tuyau, l'annulation de connexion de tuyau grâce à l'architecture VPN-CRC et VPN-LBN de manière à garantir la qualité de service VPN, dans le but de réaliser le perfectionnement du modèle de tuyau et d'assurer la qualité des services VPN.
PCT/CN2006/002017 2005-08-19 2006-08-10 Procede et systeme de mise en place d'un modele de tuyau d'apres la differenciation de services WO2007019788A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200510090905.3 2005-08-19
CNB2005100909053A CN100514912C (zh) 2005-08-19 2005-08-19 一种基于区分服务的Pipe模型实现方法

Publications (1)

Publication Number Publication Date
WO2007019788A1 true WO2007019788A1 (fr) 2007-02-22

Family

ID=37738338

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2006/002017 WO2007019788A1 (fr) 2005-08-19 2006-08-10 Procede et systeme de mise en place d'un modele de tuyau d'apres la differenciation de services

Country Status (2)

Country Link
CN (1) CN100514912C (fr)
WO (1) WO2007019788A1 (fr)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107147509B (zh) * 2016-03-01 2022-03-11 中兴通讯股份有限公司 虚拟专用网业务实现方法、装置及通信系统
CN109729006B (zh) * 2017-10-27 2021-08-31 中兴通讯股份有限公司 一种报文处理方法和装置、计算机可读存储介质
CN111711534B (zh) * 2020-05-27 2023-05-05 新浪技术（中国）有限公司 网络服务质量分析方法、装置、系统、设备和存储介质
CN113872998A (zh) * 2020-06-30 2021-12-31 华为技术有限公司 建立管道的方法及装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2003073702A1 (fr) * 2002-02-28 2003-09-04 Cisco Technology, Inc. Systeme et procede de transmission respectant la qualite du service dans un reseau de communications
CN1622529A (zh) * 2003-11-27 2005-06-01 华为技术有限公司 一种有服务质量保障的虚拟专用网的实现方法
CN1649320A (zh) * 2004-01-20 2005-08-03 华为技术有限公司 基于网络的虚拟专用网中保证服务质量的系统及其方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2003073702A1 (fr) * 2002-02-28 2003-09-04 Cisco Technology, Inc. Systeme et procede de transmission respectant la qualite du service dans un reseau de communications
CN1622529A (zh) * 2003-11-27 2005-06-01 华为技术有限公司 一种有服务质量保障的虚拟专用网的实现方法
CN1649320A (zh) * 2004-01-20 2005-08-03 华为技术有限公司 基于网络的虚拟专用网中保证服务质量的系统及其方法

Also Published As

Publication number Publication date
CN100514912C (zh) 2009-07-15
CN1917440A (zh) 2007-02-21

Similar Documents

Publication Publication Date Title
EP1589696B1 (fr) Système et procédé et pour l'allocation de ressources dans un réseau multi-domaine
KR100703499B1 (ko) 다중 프로토콜 레이블 교환 시스템에서 트래픽 엔지니어링기능을 구현하기 위한 데이터구조 및 구축 방법
JP2004529550A (ja) データネットワークにおけるプールに基づいた資源管理
JP2004532545A (ja) データネットワークにおけるルータ間のクラス毎の資源のポリシに基づく同期。
JP2004530340A (ja) データネットワークにおけるエッジに基づくフローごとのＱｏＳ許可制御
US8542580B2 (en) Method and system for transporting service flow securely in an IP network
WO2008046326A1 (fr) Procédé et système de contrôle de service de réseau
US8107373B2 (en) Method, device and system for realizing QoS guarantee in a MPLS network
WO2006069527A1 (fr) Procede, dispositif et reseau permettant de garantir la qualite de service d'un service pour un acces a large bande
WO2006034651A1 (fr) Procede destine a assurer la qualite d'un service de bout-en-bout
WO2007025457A1 (fr) Methode et systeme de fourniture de service differencie
WO2006074593A1 (fr) Procede de mise en oeuvre d'une application de ressources a flux de service multiples
WO2006056099A1 (fr) Procede et systeme permettant de garantir individuellement la qualite de service dans un reseau
Pana et al. A Survey on the Evolution of RSVP
EP1746763B1 (fr) Procede de gestion de ressources interdomaines
Ghanwani et al. A framework for integrated services over shared and switched IEEE 802 LAN technologies
WO2007019788A1 (fr) Procede et systeme de mise en place d'un modele de tuyau d'apres la differenciation de services
WO2009103192A1 (fr) Procédé d'attribution de ressource et procédé de libération de ressource
WO2006058497A1 (fr) Procede de distribution de ressources de reseau support
US8644150B2 (en) Admission control in a telecommunication network
WO2007033612A1 (fr) Systeme et procede de commande de ressource du reseau d'acces
WO2006042464A1 (fr) Procede permettant de gerer les ressources de branchement d'electricite
KR100794363B1 (ko) 웹 서비스를 이용한 인터-도메인 간의 서비스품질 보장형 연결설정 방법 및 시스템
Chen et al. Using policy-based MPLS management architecture to improve QoS on IP network
JP2001527726A (ja) Ａｔｍ通信網におけるマルチメディアサービスを提供する方法とシステム

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application
NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 06775335

Country of ref document: EP

Kind code of ref document: A1