WO2012159351A1 - Tag allocating method, device and system - Google Patents

Tag allocating method, device and system Download PDF

Info

Publication number
WO2012159351A1
WO2012159351A1 PCT/CN2011/077759 CN2011077759W WO2012159351A1 WO 2012159351 A1 WO2012159351 A1 WO 2012159351A1 CN 2011077759 W CN2011077759 W CN 2011077759W WO 2012159351 A1 WO2012159351 A1 WO 2012159351A1
Authority
WO
WIPO (PCT)
Prior art keywords
route
label
matching
label allocation
allocation manner
Prior art date
Application number
PCT/CN2011/077759
Other languages
French (fr)
Chinese (zh)
Inventor
孙春霞
张栋
Original Assignee
华为技术有限公司
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 华为技术有限公司 filed Critical 华为技术有限公司
Priority to PCT/CN2011/077759 priority Critical patent/WO2012159351A1/en
Priority to CN201180001405.1A priority patent/CN103026667B/en
Publication of WO2012159351A1 publication Critical patent/WO2012159351A1/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/50—Routing or path finding of packets in data switching networks using label swapping, e.g. multi-protocol label switch [MPLS]

Definitions

  • the present invention relates to the field of communications, and in particular, to a label distribution method, apparatus, and system. Background technique
  • BGP Border Gateway Protocol
  • MPLS Multiprotocol Label Switch
  • VPN Virtual Private Network
  • the route-based label allocation method is to assign a different label to each route learned from a CE (Customer Edge) router on a PE (Provider Edge) router.
  • the VPN-based label allocation method assigns the same label to all routes within a VPN.
  • VPN-based label allocation method is not applicable to scenarios such as the CSC (Carrier Supporting Carrier), the inter-domain Option B scenario, and the inter-AS Option C scenario.
  • CSC Carrier Supporting Carrier
  • inter-domain Option B scenario the inter-domain Option B scenario
  • inter-AS Option C scenario the VPN-based label allocation mode
  • a label distribution method includes: Matching the characteristics of the route according to the matching condition, and obtaining a matching result, where the matching condition includes: whether the feature of the route is a specified feature and/or whether the features of the multiple routes are the same;
  • the label allocation manner includes: a route-based label allocation manner, a VPN-based label allocation manner, an interface-based label allocation manner, and a next hop based How labels are assigned.
  • a label dispensing device comprising:
  • a matching module configured to match a feature of the route according to the matching condition, to obtain a matching result, where the matching condition includes: whether the feature of the route is a specified feature and/or whether the features of the multiple routes are the same;
  • An execution module configured to select, according to the matching result of the matching module, a corresponding label allocation manner for the routing, where the label allocation manner includes: a route-based label allocation manner, a VPN-based label allocation manner, and an interface-based label distribution manner. Mode, and label allocation based on next hop.
  • a label distribution system comprising: a plurality of first provider border routers and a first user border router belonging to a first autonomous system, and a plurality of second provider border routers and a second belonging to a second autonomous system a user border router, at least one of the first provider border router and at least one second provider border router are connected to each other, and the interconnected first provider border router and second provider border router are provided with the foregoing Label dispensing device.
  • the technical solution provided by the embodiment of the present invention has the beneficial effects that: by matching the characteristics of the route to select a corresponding label allocation manner, label resources can be effectively saved.
  • the label allocation mode is matched with the characteristics of the route, so that the label allocation mode can be uniformly managed, and the application is flexible, which is beneficial to adding a new label allocation manner according to the requirements of the network deployment scenario.
  • FIG. 1 is a flowchart of a label distribution method according to Embodiment 1 of the present invention.
  • FIG. 2a is a network architecture diagram of an application of a label distribution method according to Embodiment 2 of the present invention.
  • FIG. 2b is a flowchart of a label distribution method according to Embodiment 2 of the present invention.
  • FIG. 3a is a network architecture diagram of an application of a label distribution method according to Embodiment 3 of the present invention.
  • FIG. 3b is a flowchart of a label distribution method according to Embodiment 3 of the present invention.
  • FIG. 4a is a network architecture diagram of an application of a label distribution method according to Embodiment 4 of the present invention.
  • FIG. 4b is a flowchart of a label distribution method according to Embodiment 4 of the present invention.
  • FIG. 5 is a structural block diagram of a label distribution apparatus according to Embodiment 5 of the present invention. detailed description
  • this embodiment provides a label distribution method, which includes the following steps:
  • the matching condition includes: whether the feature of the route is a specified feature and/or whether the features of the multiple routes are the same.
  • the foregoing routes include: a route prefix, a route mask length, a BGP route attribute, and a VPN label of the route.
  • the foregoing matching condition includes: whether the route mask length is a specified length, whether the route prefix is a specified route prefix, whether the VPN labels of the multiple routes are the same, and whether the next hops of the multiple routes are the same. Or a combination of multiple.
  • the corresponding label allocation mode is selected for routing.
  • the foregoing label allocation manner includes: a route-based label allocation method (per label per label), a VPN-based label allocation method (per VPN per label), an interface-based label allocation method (per interface per label), and based on
  • the label allocation mode of the next hop (per label per next hop), the label allocation method based on the next hop is also called the neighbor-based label allocation method (per neighbor per label).
  • the label resource can be effectively saved.
  • the label allocation mode is matched with the characteristics of the route, so that the label allocation mode can be uniformly managed, and the application is flexible, which is beneficial to adding a new label distribution manner according to the requirements of the network deployment scenario.
  • This embodiment uses a CSC scenario as an example to describe a label allocation method according to an embodiment of the present invention.
  • the CSC scenario refers to a networking model in which some large operators, in addition to providing VPN services directly to customers, also package some network resources for small operators to operate, that is, BGP/MPLS VPN services.
  • the provider's user itself may also be a service provider, in which case the former is called a Tier 1 operator and the latter is called a Tier 2 carrier.
  • the AS Autonomous System
  • the AS 100 corresponds to the carrier
  • CE of the first-level operator such as CE1
  • the PEs issued to the Level 1 carrier such as PE1
  • do not release the routes of the Level 2 carrier customers not shown. That is, for the Level 1 carrier, the route between the PEs of the Level 2 carrier is the VPN-IPv4 route of the Level 1 carrier, and the route of the Level 2 carrier is not visible to the Level 1 carrier. This can reduce the number of routes that need to be maintained in the Level 1 carrier network.
  • the route of the Level 2 carrier customer is invisible to the Level 1 carrier. Therefore, the traffic of the Level 2 carrier customer must be encapsulated, that is, the tunnel can pass through the Level 1 carrier to reach the remote client site. .
  • This requires an end-to-end tunnel between the PEs of the Level 2 carrier, such as PE3 and PE4, and the end-to-end tunnel must be established between the two hosts, that is, the PEs of the Level 1 carrier.
  • Different PEs (32-bit host routes) for the secondary carrier must have different labels to ensure end-to-end tunnel establishment. Therefore, in this case, on the PEs of the Level 1 carrier, different PEs in the same VPN of the Level 2 carrier cannot share a label, otherwise the tunnel cannot be established. That is to say, the VPN-based label allocation mode cannot be deployed on the PEs of the Level 1 carrier. Only the route-based label allocation method can be adopted, and the label consumption is large.
  • the label distribution method of this embodiment includes:
  • the matching condition includes: whether the feature of the route is a specified feature and/or whether the features of the multiple routes are the same.
  • the characteristics of the route are matched on the ABR (Autonomous System Border Router) of the Level 2 carrier, that is, CE1 and CE2 in the figure.
  • the route can be characterized by a route prefix and a route mask length, or only a route mask length.
  • the matching condition includes whether the route prefix is a predetermined prefix and the route mask length is 32 bits, or whether only the route mask length is 32 bits.
  • the specific matching process is as follows: Each route is matched with a route configured in an ACL (Access Control-List).
  • the ACL is configured with a route prefix and a mask length of a 32-bit host route, or only configured with The length of the route mask.
  • the following two matching modes can be used: First, when the ASBR receives the route, it detects the route prefix and mask length of the route, and the route prefix and mask length of the route and the ACL.
  • the configuration in the Access Control-List matches.
  • the configuration in the ACL includes the route prefix and the route mask length of the route on the loopback interface address of the PE of the Level 2 carrier. For example, in the ACL.
  • the route prefix Configure the route prefix to be 1. 1. 1. 1 (mask length is 32), route 2. 2. 2. 2 (mask length is 32). If the matching condition is met, that is, the route prefix and the mask length are both qualified, the route is determined to be a 32-bit host route, that is, the route on the loopback interface address of the PE device of the Level 2 carrier.
  • the ASBR when the ASBR receives the route, it matches the mask length of the route with the configuration in the ACL.
  • the configuration is a 32-bit route with a mask length of 32. If the matching condition is met, that is, the mask length of the route is 32 bits, it is determined whether the route is a 32-bit host route.
  • the former can improve the accuracy of the matching result, that is, the route prefix list accurately matches the route on the loopback interface address of the PE device of the second-level operator, but the configuration parameter quantity is large; Configuration, that is, matching all 32-bit host routes, these two methods can be selected according to actual needs.
  • the matching result is that the route is a 32-bit host route, and the route-based label allocation mode is adopted.
  • the ASBR of the second-level carrier adopts a route-based label allocation mode, and different routes allocate different labels.
  • the matching result is that the route is a network segment route other than a 32-bit host route, and no label is allocated to the network segment route.
  • Route matching is performed on the ASBR of the Level 2 carrier, that is, the CE device of the Level 1 carrier, to implement route-based label distribution for the 32-bit route on the ASBR of the Level 2 carrier.
  • the CE of the Level 1 carrier that is, the route on the loopback interface address of the PE device of the Level 2 carrier on PE1 and PE2 in Figure 2a
  • uses a route-based label allocation method which is different. Routes are assigned different labels. Therefore, different PEs of the Level 2 carrier are distinguished on the CE device of the Level 1 carrier, and different labels are set for different PEs.
  • the PE of the Level 1 carrier receives the 32-bit route from the CE of the Level 1 carrier, because it has different labels, the PE of the Level 1 carrier will also assign different routes for these labels.
  • the label that is, the PE of the Level 1 carrier, the 32-bit host route of the PE of the Level 2 carrier, also uses the route-based label allocation method, so that the PE of the Level 2 carrier can be used. End-to-end tunnels are established between devices, such as PE3 and PE4, to ensure data transmission.
  • the ASBR of the Level 2 carrier that is, the CE of the Level 1 carrier
  • the ASBR of the Level 2 carrier does not assign a label to it. Compared with the existing route-based label allocation method for all routes, the effective saving is achieved.
  • Label resource The ASBR of the Level 2 carrier does not assign labels to other network segments.
  • the label distribution mode based on the VPN instance or the label distribution mode based on the interface is adopted.
  • the ASBR of the Level 2 carrier can distinguish the 32-bit host route of the PEs of the Level 2 carrier and establish a tunnel between the PEs of the Level 2 carrier. Therefore, the PEs of the Level 2 carrier can adopt VPN-based instances.
  • the label allocation mode or the interface-based label allocation mode can also save label resources on the PE equipment of the secondary carrier.
  • the present embodiment uses the cross-domain VPN Option C scenario as an example to describe the label allocation method of the present invention.
  • the ASBR does not maintain or advertise VPN-IPv4 routes.
  • AS 100 and AS: 200 PEs, such as RR-1 (Route Reflector) and RR-2.
  • PEs such as RR-1 (Route Reflector) and RR-2.
  • the ASBR advertises IPv4 label routes to PEs in the ASs through MP-IBGP (Multi-Protocol internal BGP).
  • the IPv4 label route to the PE device in the AS is notified to the ASBR peer of the peer AS.
  • the purpose of the IPv4 label routing is to bond the tunnels in the respective domains to form end-to-end tunnels between PEs in different ASs, such as PE2 and PE4.
  • the ASBR does not maintain the VPN-IPv4 route
  • only the IPv4 label route is advertised. That is, the ASBR cannot know which VPN the route belongs to. Therefore, the VPN-based label allocation mode cannot be adopted. Only the route-based label allocation method can be used. The consumption is large.
  • the label distribution method of this embodiment includes the following steps.
  • the matching condition includes: whether the feature of the route is a specified feature and/or whether the features of the multiple routes are the same.
  • the feature of the route is matched on the ASBR.
  • the route can be characterized by a route prefix and a route mask length, or only a route mask length.
  • the matching condition includes whether the route prefix is a predetermined prefix and the route mask length is 32 bits, or whether only the route mask length is 32 bits.
  • the specific matching process is as follows: Each route is matched with a route configured in the ACL.
  • the access control list is configured with a route prefix and a mask length of a 32-bit host route, or only a route mask length. Further, the following two matching methods can be used:
  • the ASBR when the ASBR receives the route, it detects the route prefix and mask length of the route, and matches the route prefix and mask length of the route with the configuration in the ACL (Access Control-List, Access Control List).
  • the configuration includes the route prefix and the route mask length of the route on the loopback interface address of the PE device.
  • the route prefix configured in the ACL is 1. 1. 1. 1 (mask length is 32), route 2. 2. 2. 2 (mask length is 32). If the matching condition is met, that is, the route prefix and the mask length are both qualified, the route is determined to be a 32-bit host route, that is, the route on the loopback interface address of the PE device.
  • the ASBR when the ASBR receives the route, it matches the mask length of the route with the configuration in the ACL.
  • the configuration is a 32-bit route with a mask length of 32. If the matching condition is met, that is, the mask length of the route is 32 bits, it is determined whether the route is a 32-bit host route.
  • 302 The matching result is that the route is a 32-bit host route, and the route-based label allocation manner is used. For the route matched in step 301, a route-based label allocation manner is used, and different routes are assigned different labels.
  • the label distribution mode based on the VPN instance or the label distribution method based on the interface is adopted.
  • the matching of the routing features on the ASBR matches the 32-bit host route of the PE device, and the route-based label allocation mode is adopted for the 32-bit host route of the PE device, that is, only the PE is applied to the ASBR.
  • the route on the loopback interface address of the device adopts the route-based label allocation mode.
  • different labels are set for different PEs (32-bit host routes) on the ASBR device, so that the PE2 to PE4 end can be established.
  • the tunnel at the end ensures data transmission.
  • no label is allocated or a label allocation method based on the next hop is adopted, which effectively saves label resources compared with the existing route-based label allocation method for all routes.
  • a VPN instance-based label allocation method or an interface-based label allocation method is adopted. due to
  • the ASBR can distinguish the 32-bit host route of the PE device and establish a tunnel between the PE devices. Therefore, the PE device can use the label distribution mode based on the VPN instance or the label distribution mode based on the interface, thereby saving labels on the PE device. Resources.
  • Example 4
  • the cross-domain VPN Option B scenario is taken as an example to describe the label distribution method of the present invention.
  • the ASBRs in different ASs that is, ASBR1 and ASBR2 in the figure, exchange the VPN_IPv4 routes they receive from the PEs of the respective ASs through MP-EBGP (Multi-Protocol Extension BGP).
  • MP-EBGP Multi-Protocol Extension BGP
  • the route learned from the other party is sent to the PE device in the domain.
  • ASBR1 and ASBR2 need to change the next hop of the route when the route is forwarded.
  • ASBR1 forwards the route learned from the PE in the domain to ASBR2 outside the domain, the next hop of the route is changed to ASBR1, and ASBR1 learns from ASBR2.
  • PE devices in each AS can adopt a VPN-based label allocation method or an interface-based label allocation method.
  • a CE device such as CE1 usually connects to ASBR1 through two PE devices, such as PE1 and another PE device, not shown, one of which is used for backup routing.
  • ASBR1 also adopts the VPN-based label allocation method, the routes from the two PE devices will be assigned to the same label.
  • ASBR1 cannot judge the data to be received. Which PE device is given, that is, the tunnel for transmitting data cannot be established.
  • an interface-based label allocation method an interface of the ASBR receives routes from different PE devices. After the same label is assigned to these routes, when the ASBR receives the data, it cannot determine which one to send it to. PE, the tunnel for transmitting data could not be established. Therefore, in this scenario, the prior art can only adopt a route-based label allocation method, and the label consumption is large.
  • the label distribution method of this embodiment includes the following steps.
  • the matching condition includes: whether the feature of the route is a specified feature and/or whether the features of the multiple routes are the same.
  • the VPN label of the learned multiple routes and the next hop of the route are respectively matched on the ASBR to obtain a matching result. If the VPN labels are the same, the routes are from the same VPN instance. If the next hop of the route is the same, the routes are forwarded by the same PE. That is to say, in this embodiment, the matching condition is whether the characteristics of the plurality of routes are the same. Further, the matching condition is whether the VPN labels of the multiple routes are the same and whether the next hops of the multiple routes are the same.
  • next hop based label allocation method also known as the neighbor based label allocation method.
  • the label allocation method in this embodiment performs the matching of the routing features on the ASBR, and uses the label allocation mode based on the next hop for the routes with the same next hop and the same VPN label, because the routes outside the domain need to be labeled on the ASBR.
  • the label is allocated locally. Therefore, the label allocation method based on the next hop can avoid the situation in which the ASBR1 cannot determine which PE device to forward the received data to during the data transmission process, so that the PE can be established.
  • the ASBR is established, and the ASBR is established from the intra-domain ASBR to the ASBR of the out-of-domain. That is, the embodiment of the present invention can effectively save label resources and ensure data transmission under the premise of correct routing.
  • an embodiment of the present invention provides a label distribution apparatus, which includes:
  • the matching module 501 is configured to match the characteristics of the route according to the matching condition, and obtain a matching result, where the matching condition includes: whether the feature of the route is a specified feature and/or whether the features of the multiple routes are the same;
  • the executing module 502 is configured to select a corresponding label allocation manner for the route according to the matching result of the matching module 501.
  • the label allocation manner includes: a route-based label allocation manner, a VPN-based label allocation manner, an interface-based label allocation manner, and a next hop-based label allocation manner.
  • the foregoing routing features include: a route prefix, a route mask length, a border gateway protocol route attribute, and a VPN label of the route.
  • the foregoing matching condition includes: whether the route mask length is a specified length, whether the route prefix is a specified route prefix, whether the VPN labels of the multiple routes are the same, and whether the next hops of the multiple routes are the same. Or a combination of multiple.
  • the matching module 501 includes:
  • the mask length matching unit is configured to match the mask length of each route according to the access control list; or a route prefix matching unit, configured to match each route with a route prefix configured in the access control list.
  • the matching module 501 includes:
  • a label matching unit configured to match a routed VPN label
  • the next hop matching unit is used to match the next hop of the route.
  • the label distribution device in this embodiment is the same as the label distribution in the method embodiment.
  • the specific implementation process is described in the method embodiment, and details are not described herein again.
  • the device can be configured on the PE device or on the ASBR, and can be selected according to different network deployment scenarios.
  • the embodiment of the present invention can effectively save label resources by matching the characteristics of the route to select a corresponding label allocation manner for routing.
  • the label allocation mode is matched with the characteristics of the route, so that the label allocation mode can be uniformly managed, and the application is flexible, which is beneficial to adding a new label distribution manner according to the requirements of the network deployment scenario.
  • An embodiment of the present invention provides a label distribution system, including: a plurality of first provider border routers and a first user border router belonging to the first autonomous system, and a plurality of second providers belonging to the second autonomous system. a border router and a second user border router, at least one of the first provider border router and at least one second provider border router interconnecting, the interconnected first provider border router and second provider border
  • the aforementioned label distribution device is provided on the router.
  • AS: 100 is the first autonomous system
  • AS: 200 is the second autonomous system
  • CE1, CE2, PE3, and PE4 are the first provider border routers
  • PE1 and PE2 are the second provider boundaries.
  • the routers, CE1 and CE2 also represent the first user border router, and the aforementioned label distribution means are provided on CE1 and CE2.
  • AS: 100 is the first autonomous system
  • AS: 200 is the second autonomous system
  • ASBR1, PE1, and PE2 are the first provider border routers
  • CE1 and CE2 are the first user border routers
  • PE4 is a second provider border router
  • CE3 and CE4 are second user border routers
  • the foregoing label distribution devices are disposed on ASBR1 and ASBR2.
  • AS: 100 is the first autonomous system
  • AS: 200 is the second autonomous system
  • ASBR1, PE1, and PE2 are the first provider border routers
  • CE1 and CE2 are the first user border routers
  • PE4 is a second provider border router
  • CE3 and CE4 are second user border routers
  • the foregoing label distribution devices are disposed on ASBR1 and ASBR2.

Landscapes

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

Abstract

Provided are a tag allocating method and device, relating to the field of communications. The method comprises: matching the characteristics of a route according to matching conditions to obtain matching results, the matching conditions comprising: whether the characteristics of the route are set characteristics and/or whether the characteristics of various routes are the same; and a corresponding tag allocation mode is selected for the route according to the matching results. The device comprises: a matching module and an executing module. In the present invention, by matching the characteristics of a route, a corresponding tag allocation mode may be selected for the route, enabling effective saving in tag resources and providing benefits in flexibly increasing new tag allocation modes according to the requirements of network deployment scenarios.

Description

一种标签分配方法、 装置和*** 技术领域  Label distribution method, device and system
本发明涉及通信领域， 特别涉及一种标签分配方法、 装置和***。 背景技术  The present invention relates to the field of communications, and in particular, to a label distribution method, apparatus, and system. Background technique
目前， BGP( Border Gateway Pro说tocol,边界网关协议）/MPLS( Multiprotocol Label Switch, 多协议标签交换） VPN (Virtual Private Network, 虚拟专用网） 技术已经趋于成熟和稳定， 应用也越来越广泛。 在该技术中， 数据是按标签进行分组转发的， 这样就牵涉到标签分配 方式。 现有的标签分配方式有以下两种：  At present, BGP (Bound Gateway Pro-to-collateral, Border Gateway Protocol)/MPLS (Multiprotocol Label Switch) VPN (Virtual Private Network) technology has become mature and stable, and applications are becoming more widespread. . In this technique, data is forwarded by packet, which involves the label allocation method. There are two ways to assign labels:
书  Book
第一、 基于路由的标签分配方式， 该标签分配方式是在 PE (Provider Edge, 提供商边 界）路由器上对从 CE (Customer Edge, 用户边界）路由器学到的每条路由分配一个不同的 标签。  First, the route-based label allocation method is to assign a different label to each route learned from a CE (Customer Edge) router on a PE (Provider Edge) router.
第二、 基于 VPN的标签分配方式， 该标签分配方式是为一个 VPN内部的所有路由分 配同一个标签。  Second, the VPN-based label allocation method assigns the same label to all routes within a VPN.
在实现本发明的过程中， 发明人发现现有技术至少存在以下问题：  In the process of implementing the present invention, the inventors have found that the prior art has at least the following problems:
为了节约标签资源，各种网络部署场景需要尽量采用基于 VPN的标签分配方式。但是， 这种基于 VPN的标签分配方式， 并不适用于 CSC (Carrier Supporting Carrier, 运营商的运 营商） 场景、 跨域 Option B场景和跨域 Option C场景等场景。 在上述场景中， 若各设备上 都采用基于 VPN的标签分配方式， 就无法在 PE设备之间建立隧道以传输数据， 因此， 只 能采用基于路由的标签方式。  In order to save label resources, various network deployment scenarios need to adopt a VPN-based label distribution method. However, the VPN-based label allocation method is not applicable to scenarios such as the CSC (Carrier Supporting Carrier), the inter-domain Option B scenario, and the inter-AS Option C scenario. In the above scenario, if the VPN-based label allocation mode is adopted on each device, tunnels cannot be established between PE devices to transmit data. Therefore, only route-based labeling can be adopted.
在路由量较大的情况下， 前述场景下的 PE设备上的标签资源消耗很大， 并且设备 ILM (Incoming Label Map, 入标签映射表） 需要维护的表项也会增多， 从而对设备容量的要求 很高。 发明内容  In the case of a large amount of traffic, the label resources on the PEs in the preceding scenario are very expensive, and the number of entries that need to be maintained by the device's ILM (Incoming Label Map) is increased. high expectation. Summary of the invention
为了克服现有技术在 CSC场景、跨域 Option B场景和跨域 Option C场景等场景下标签 资源消耗大的缺陷， 本发明提供了一种标签分配方法、 装置和***。 所述技术方案如下： 一种标签分配方法， 所述方法包括： 根据匹配条件匹配路由的特征， 得到匹配结果， 所述匹配条件包括： 所述路由的特征 是否为规定的特征和 /或多条路由的特征是否相同； 及 In order to overcome the defect that the label resource consumption is large in the scenario of the CSC scenario, the inter-domain Option B scenario, and the inter-domain Option C scenario, the present invention provides a label allocation method, apparatus, and system. The technical solution is as follows: A label distribution method, the method includes: Matching the characteristics of the route according to the matching condition, and obtaining a matching result, where the matching condition includes: whether the feature of the route is a specified feature and/or whether the features of the multiple routes are the same;
根据所述匹配结果为所述路由选择相应的标签分配方式， 所述标签分配方式包括： 基 于路由的标签分配方式、 基于 VPN 的标签分配方式、 基于接口的标签分配方式、 和基于下 一跳的标签分配方式。  And performing, according to the matching result, a corresponding label allocation manner for the routing, where the label allocation manner includes: a route-based label allocation manner, a VPN-based label allocation manner, an interface-based label allocation manner, and a next hop based How labels are assigned.
一种标签分配装置， 所述装置包括：  A label dispensing device, the device comprising:
匹配模块， 用于根据匹配条件匹配路由的特征， 得到匹配结果， 所述匹配条件包括： 所述路由的特征是否为规定的特征和 /或多条路由的特征是否相同； 及  a matching module, configured to match a feature of the route according to the matching condition, to obtain a matching result, where the matching condition includes: whether the feature of the route is a specified feature and/or whether the features of the multiple routes are the same;
执行模块， 用于根据所述匹配模块的匹配结果为所述路由选择相应的标签分配方式， 所述标签分配方式包括： 基于路由的标签分配方式、 基于 VPN 的标签分配方式、 基于接口 的标签分配方式、 和基于下一跳的标签分配方式。  An execution module, configured to select, according to the matching result of the matching module, a corresponding label allocation manner for the routing, where the label allocation manner includes: a route-based label allocation manner, a VPN-based label allocation manner, and an interface-based label distribution manner. Mode, and label allocation based on next hop.
一种标签分配***， 所述***包括： 属于第一自治***的多个第一提供商边界路由器 和第一用户边界路由器、 以及属于第二自治***的多个第二提供商边界路由器和第二用户 边界路由器， 至少一个所述第一提供商边界路由器和至少一个第二提供商边界路由器相互 连接， 所述相互连接的所述第一提供商边界路由器和第二提供商边界路由器上设置有前述 的标签分配装置。  A label distribution system, the system comprising: a plurality of first provider border routers and a first user border router belonging to a first autonomous system, and a plurality of second provider border routers and a second belonging to a second autonomous system a user border router, at least one of the first provider border router and at least one second provider border router are connected to each other, and the interconnected first provider border router and second provider border router are provided with the foregoing Label dispensing device.
本发明实施例提供的技术方案的有益效果是： 通过匹配路由的特征来选择相应的标签 分配方式， 可以有效节省标签资源。 此外， 通过将标签分配方式与路由的特征相对应， 从 而可以对标签分配方式进行统一的管理， 应用比较灵活， 有利于根据网络部署场景的需求 增加新的标签分配方式。 附图说明  The technical solution provided by the embodiment of the present invention has the beneficial effects that: by matching the characteristics of the route to select a corresponding label allocation manner, label resources can be effectively saved. In addition, the label allocation mode is matched with the characteristics of the route, so that the label allocation mode can be uniformly managed, and the application is flexible, which is beneficial to adding a new label allocation manner according to the requirements of the network deployment scenario. DRAWINGS
图 1是本发明实施例 1提供的标签分配方法的流程图；  1 is a flowchart of a label distribution method according to Embodiment 1 of the present invention;
图 2a是本发明实施例 2提供的标签分配方法的一个应用的网络架构图；  2a is a network architecture diagram of an application of a label distribution method according to Embodiment 2 of the present invention;
图 2b是本发明实施例 2提供的标签分配方法的流程图；  2b is a flowchart of a label distribution method according to Embodiment 2 of the present invention;
图 3a是本发明实施例 3提供的标签分配方法的一个应用的网络架构图；  FIG. 3a is a network architecture diagram of an application of a label distribution method according to Embodiment 3 of the present invention; FIG.
图 3b是本发明实施例 3提供的标签分配方法的流程图；  FIG. 3b is a flowchart of a label distribution method according to Embodiment 3 of the present invention; FIG.
图 4a是本发明实施例 4提供的标签分配方法的一个应用的网络架构图；  4a is a network architecture diagram of an application of a label distribution method according to Embodiment 4 of the present invention;
图 4b是本发明实施例 4提供的标签分配方法的流程图；  4b is a flowchart of a label distribution method according to Embodiment 4 of the present invention;
图 5本发明实施例 5提供的标签分配装置的结构框图。 具体实施方式 FIG. 5 is a structural block diagram of a label distribution apparatus according to Embodiment 5 of the present invention. detailed description
为使本发明的目的、 技术方案和优点更加清楚， 下面将结合附图对本发明实施方式作 进一步地详细描述。  The embodiments of the present invention will be further described in detail below with reference to the accompanying drawings.
实施例 1  Example 1
如图 1所示， 本实施例提供了一种标签分配方法， 其包括以下步骤：  As shown in FIG. 1 , this embodiment provides a label distribution method, which includes the following steps:
101： 根据匹配条件匹配路由的特征， 得到匹配结果， 匹配条件包括： 所述路由的特征 是否为规定的特征和 /或多条路由的特征是否相同。  101: Match the characteristics of the route according to the matching condition, and obtain a matching result, where the matching condition includes: whether the feature of the route is a specified feature and/or whether the features of the multiple routes are the same.
具体地， 前述路由的特征包括： 路由前缀、 路由掩码长度、 BGP路由属性和路由的 VPN 标签。  Specifically, the foregoing routes include: a route prefix, a route mask length, a BGP route attribute, and a VPN label of the route.
相应地， 前述匹配条件包括： 路由掩码长度是否为规定的长度、 路由前缀是否为规定 的路由前缀、 多条路由的 VPN标签是否相同、 以及多条路由的下一跳是否相同中的一种或 多种的结合。  Correspondingly, the foregoing matching condition includes: whether the route mask length is a specified length, whether the route prefix is a specified route prefix, whether the VPN labels of the multiple routes are the same, and whether the next hops of the multiple routes are the same. Or a combination of multiple.
102： 根据匹配结果为路由选择相应的标签分配方式。  102: According to the matching result, the corresponding label allocation mode is selected for routing.
具体地，前述标签分配方式包括： 基于路由的标签分配方式（每路由每标签）、基于 VPN 的标签分配方式 （每 VPN每标签）、 基于接口的标签分配方式 （每接口每标签）、 和基于下 一跳的标签分配方式 （每下一跳每标签）， 基于下一跳的标签分配方式也称为基于邻居的标 签分配方式 （每邻居每标签）。  Specifically, the foregoing label allocation manner includes: a route-based label allocation method (per label per label), a VPN-based label allocation method (per VPN per label), an interface-based label allocation method (per interface per label), and based on The label allocation mode of the next hop (per label per next hop), the label allocation method based on the next hop is also called the neighbor-based label allocation method (per neighbor per label).
本发明实施例通过匹配路由的特征来选择相应的标签分配方式， 可以有效节省标签资 源。 此外， 通过将标签分配方式与路由的特征相对应， 从而可以对标签分配方式进行统一 的管理， 应用比较灵活， 有利于根据网络部署场景的需求增加新的标签分配方式。 实施例 2  In the embodiment of the present invention, by selecting the corresponding label allocation manner by matching the characteristics of the route, the label resource can be effectively saved. In addition, the label allocation mode is matched with the characteristics of the route, so that the label allocation mode can be uniformly managed, and the application is flexible, which is beneficial to adding a new label distribution manner according to the requirements of the network deployment scenario. Example 2
本实施例以 CSC场景为例说明本发明实施例的标签分配方法。  This embodiment uses a CSC scenario as an example to describe a label allocation method according to an embodiment of the present invention.
CSC场景是指这样一种组网模型：一些大型的运营商除了直接给客户提供 VPN服务以外， 也会把一部分网络资源包给一些小型的运营商进行经营， 也就是说， BGP/MPLS VPN服务提 供商的用户本身也可能是一个服务提供商， 在这种情况下， 前者称为一级运营商， 后者称 为二级运营商。  The CSC scenario refers to a networking model in which some large operators, in addition to providing VPN services directly to customers, also package some network resources for small operators to operate, that is, BGP/MPLS VPN services. The provider's user itself may also be a service provider, in which case the former is called a Tier 1 operator and the latter is called a Tier 2 carrier.
如图 2a所示， AS (Autonomous System, 自治***）： 200对应的运营商为一级运营商， AS : 100对应的运营商为二级运营商。 一级运营商的 CE， 如 CE1只把二级运营商内部的路 由发布给一级运营商的 PE， 如 PE1， 而不发布二级运营商客户 （图未示） 的路由。 也就是 说， 对于一级运营商来说， 二级运营商的 PE设备间的路由是一级运营商的 VPN-IPv4路由， 而二级运营商的路由在一级运营商上不可见。 这样可以减少一级运营商网络中需要维护的 路由数量。 As shown in Figure 2a, the AS (Autonomous System): 200 corresponds to the carrier, and the AS: 100 corresponds to the carrier. CE of the first-level operator, such as CE1, only the internal route of the second-level operator The PEs issued to the Level 1 carrier, such as PE1, do not release the routes of the Level 2 carrier customers (not shown). That is, for the Level 1 carrier, the route between the PEs of the Level 2 carrier is the VPN-IPv4 route of the Level 1 carrier, and the route of the Level 2 carrier is not visible to the Level 1 carrier. This can reduce the number of routes that need to be maintained in the Level 1 carrier network.
由于在该场景下， 二级运营商客户的路由对于一级运营商是不可见的， 所以二级运营 商客户的流量必须经过封装， 也就是通过隧道才能穿越一级运营商到达远端客户站点。 这 就要求在二级运营商的 PE设备， 如 PE3和 PE4之间建立端到端的隧道， 而端到端的隧道 必须建立在两个主机之间， 也就是说， 在一级运营商的 PE设备上对于二级运营商的不同的 PE (32位主机路由）必须有不同的标签才能保证端到端隧道的建立。所以， 在这种情况下， 在一级运营商的 PE设备上， 对于二级运营商的同一个 VPN内的不同 PE设备， 不能共享一 个标签， 否则隧道就无法建立。 也就是说， 在一级运营商的 PE设备上不能部署基于 VPN 的标签分配方式， 只能采用基于路由的标签分配方式， 标签消耗量很大。  In this scenario, the route of the Level 2 carrier customer is invisible to the Level 1 carrier. Therefore, the traffic of the Level 2 carrier customer must be encapsulated, that is, the tunnel can pass through the Level 1 carrier to reach the remote client site. . This requires an end-to-end tunnel between the PEs of the Level 2 carrier, such as PE3 and PE4, and the end-to-end tunnel must be established between the two hosts, that is, the PEs of the Level 1 carrier. Different PEs (32-bit host routes) for the secondary carrier must have different labels to ensure end-to-end tunnel establishment. Therefore, in this case, on the PEs of the Level 1 carrier, different PEs in the same VPN of the Level 2 carrier cannot share a label, otherwise the tunnel cannot be established. That is to say, the VPN-based label allocation mode cannot be deployed on the PEs of the Level 1 carrier. Only the route-based label allocation method can be adopted, and the label consumption is large.
在这种情况下， 如图 2b所示， 本实施例的标签分配方法包括：  In this case, as shown in FIG. 2b, the label distribution method of this embodiment includes:
201： 根据匹配条件匹配路由的特征， 得到匹配结果， 匹配条件包括： 所述路由的特征 是否为规定的特征和 /或多条路由的特征是否相同。  201: Match the characteristics of the route according to the matching condition, and obtain a matching result, where the matching condition includes: whether the feature of the route is a specified feature and/or whether the features of the multiple routes are the same.
具体地，对于本发明实施例，在二级运营商的 ASBR (Autonomous System Border Router, 自治***边界路由器）， 即图中的 CE1和 CE2上匹配路由的特征。 该路由的特征可以为路 由前缀和路由掩码长度、 或仅为路由掩码长度。 相应地， 在本实施例中， 该匹配条件包括 路由前缀是否为预定的前缀和路由掩码长度是否为 32位、 或者仅包括路由掩码长度是否 为 32位。  Specifically, for the embodiment of the present invention, the characteristics of the route are matched on the ABR (Autonomous System Border Router) of the Level 2 carrier, that is, CE1 and CE2 in the figure. The route can be characterized by a route prefix and a route mask length, or only a route mask length. Correspondingly, in this embodiment, the matching condition includes whether the route prefix is a predetermined prefix and the route mask length is 32 bits, or whether only the route mask length is 32 bits.
具体匹配过程为： 将每条路由与 ACL (Access Control-List, 访问控制列表） 中配置 的路由进行匹配， 所述 ACL中配置有 32位主机路由的路由前缀和掩码长度、 或者仅配置 有路由掩码长度。 进一步地， 根据 ACL中配置的不同内容， 可以采用以下两种匹配方式： 第一、 当 ASBR收到路由时， 检测路由的路由前缀和掩码长度， 将路由的路由前缀和 掩码长度与 ACL (Access Control-List, 访问控制列表） 中的配置相匹配， 这里 ACL中的 配置包括二级运营商的 PE 设备的 Loopback接口地址上的路由的路由前缀和路由掩码长 度， 例如， 在 ACL中配置路由前缀为 1. 1. 1. 1 (掩码长度为 32)、 路由 2. 2. 2. 2 (掩码长度 为 32)。 若符合匹配条件， 即路由前缀和掩码长度都符合条件， 则判定该路由为 32位主机 路由， 即二级运营商的 PE设备的 Loopback接口地址上的路由。  The specific matching process is as follows: Each route is matched with a route configured in an ACL (Access Control-List). The ACL is configured with a route prefix and a mask length of a 32-bit host route, or only configured with The length of the route mask. Further, according to the different content configured in the ACL, the following two matching modes can be used: First, when the ASBR receives the route, it detects the route prefix and mask length of the route, and the route prefix and mask length of the route and the ACL. The configuration in the Access Control-List (Access Control List) matches. The configuration in the ACL includes the route prefix and the route mask length of the route on the loopback interface address of the PE of the Level 2 carrier. For example, in the ACL. Configure the route prefix to be 1. 1. 1. 1 (mask length is 32), route 2. 2. 2. 2 (mask length is 32). If the matching condition is met, that is, the route prefix and the mask length are both qualified, the route is determined to be a 32-bit host route, that is, the route on the loopback interface address of the PE device of the Level 2 carrier.
第二、 当 ASBR收到路由时， 将路由的掩码长度与 ACL中的配置相匹配， 这里， ACL中 的配置为掩码长度为 32位的路由， 若符合匹配条件， 即路由的掩码长度为 32位， 则判定 该路由是否为 32位主机路由。 在这两种方式中， 前者可以提高匹配结果的准确度， 即通 过路由前缀列表精确匹配出二级运营商的 PE设备的 Loopback接口地址上的路由， 但是配 置参数量较多； 而后者可以节省配置， 即匹配出所有 32位主机路由， 这两种方式可以根 据实际需要来选择。 Second, when the ASBR receives the route, it matches the mask length of the route with the configuration in the ACL. Here, in the ACL. The configuration is a 32-bit route with a mask length of 32. If the matching condition is met, that is, the mask length of the route is 32 bits, it is determined whether the route is a 32-bit host route. In the above two modes, the former can improve the accuracy of the matching result, that is, the route prefix list accurately matches the route on the loopback interface address of the PE device of the second-level operator, but the configuration parameter quantity is large; Configuration, that is, matching all 32-bit host routes, these two methods can be selected according to actual needs.
202： 匹配结果为所述路由为 32位主机路由， 采用基于路由的标签分配方式。  202: The matching result is that the route is a 32-bit host route, and the route-based label allocation mode is adopted.
具体地， 对于步骤 201 中匹配出的路由， 二级运营商的 ASBR采用基于路由的标签分 配方式， 不同的路由分配不同的标签。  Specifically, for the route that is matched in step 201, the ASBR of the second-level carrier adopts a route-based label allocation mode, and different routes allocate different labels.
203： 匹配结果为所述路由为 32位主机路由之外的网段路由， 对所述网段路由不分配 标签。  203: The matching result is that the route is a network segment route other than a 32-bit host route, and no label is allocated to the network segment route.
通过上述步骤 201-203， 在二级运营商的 ASBR， 即一级运营商的 CE设备上进行路由 特征的匹配， 从而在二级运营商的 ASBR上对 32位路由实现了基于路由的标签分配方式， 也就是说，一级运营商的 CE，即图 2a中的 PE1和 PE2上对二级运营商的 PE设备的 Loopback 接口地址上的路由， 使用了基于路由的标签分配方式， 对不同的路由分配不同的标签。 从 而在一级运营商的 CE设备上区分出二级运营商的不同 PE， 为不同的 PE设置不同的标签。 当一级运营商的 PE收到从一级运营商的 CE来的 32位路由时， 由于其带有不同的标签， 所以一级运营商的 PE会为这些带有不同标签的路由也分配不同的标签， 也就是说， 在一 级运营商的 PE设备上， 对二级运营商的 PE设备的 32位主机路由， 也采用基于路由的标 签分配方式， 这样， 可以在二级运营商的 PE设备之间， 如 PE3和 PE4之间建立端到端的 隧道， 从而保证数据的传输。 同时， 对于其它网段路由， 二级运营商的 ASBR， 即一级运营 商的 CE不为其分配标签， 与现有的对所有的路由都采用基于路由的标签分配方式相比， 有效节省了标签资源。 由于二级运营商的 ASBR不为其他网段路由分配标签， 当一级运营 商的 PE收到一级运营商的 CE发送的路由时， 对于这些不带有标签的路由， 即同一 VPN实 例中的网段路由， 分配同一个标签， 进而在一级运营商的 PE设备上也可以有效节省标签 资源。  Route matching is performed on the ASBR of the Level 2 carrier, that is, the CE device of the Level 1 carrier, to implement route-based label distribution for the 32-bit route on the ASBR of the Level 2 carrier. In other words, the CE of the Level 1 carrier, that is, the route on the loopback interface address of the PE device of the Level 2 carrier on PE1 and PE2 in Figure 2a, uses a route-based label allocation method, which is different. Routes are assigned different labels. Therefore, different PEs of the Level 2 carrier are distinguished on the CE device of the Level 1 carrier, and different labels are set for different PEs. When the PE of the Level 1 carrier receives the 32-bit route from the CE of the Level 1 carrier, because it has different labels, the PE of the Level 1 carrier will also assign different routes for these labels. The label, that is, the PE of the Level 1 carrier, the 32-bit host route of the PE of the Level 2 carrier, also uses the route-based label allocation method, so that the PE of the Level 2 carrier can be used. End-to-end tunnels are established between devices, such as PE3 and PE4, to ensure data transmission. At the same time, for other network segment routes, the ASBR of the Level 2 carrier, that is, the CE of the Level 1 carrier, does not assign a label to it. Compared with the existing route-based label allocation method for all routes, the effective saving is achieved. Label resource. The ASBR of the Level 2 carrier does not assign labels to other network segments. When the PEs of the Level 1 carrier receive the routes sent by the CEs of the Level 1 carrier, the routes with no labels are in the same VPN instance. The network segment routes are assigned the same label, and the label resources can be effectively saved on the PEs of the Level 1 carrier.
在二级运营商的 PE设备上， 则采用基于 VPN实例的标签分配方式或基于接口的标签 分配方式。 由于二级运营商的 ASBR可以区分出二级运营商的 PE设备的 32位主机路由， 在二级运营商的 PE设备之间建立隧道， 所以可以在二级运营商的 PE设备采用基于 VPN实 例的标签分配方式或基于接口的标签分配方式， 进而在二级运营商的 PE设备上也可以节 省标签资源。 实施例 3 On the PEs of the Level 2 carrier, the label distribution mode based on the VPN instance or the label distribution mode based on the interface is adopted. The ASBR of the Level 2 carrier can distinguish the 32-bit host route of the PEs of the Level 2 carrier and establish a tunnel between the PEs of the Level 2 carrier. Therefore, the PEs of the Level 2 carrier can adopt VPN-based instances. The label allocation mode or the interface-based label allocation mode can also save label resources on the PE equipment of the secondary carrier. Example 3
如图 3a所示， 本实施例以跨域 VPN Option C场景为例说明本发明的标签分配方法。 在该场景下， ASBR不维护或发布 VPN-IPv4路由， 不同 AS内， 如图中的 AS : 100和 AS: 200 的 PE， 如 RR-1 ( Route Reflector, 路由反射器） 和 RR-2之间之间建立 Multihop方式的 EBGP连接， 直接交换 VPN-IPv4路由， ASBR通过 MP-IBGP (Multi-Protocol internal BGP, 多协议内部边界网关协议） 向各自 AS内的 PE设备发布 IPv4标签路由， 并将到达本 AS内 PE设备的 IPv4标签路由通知给它在对端 AS的 ASBR对等体。 发布 IPv4标签路由的目的是 为了将各自域内的隧道粘接起来， 从而形成不同 AS域内 PE设备， 如 PE2和 PE4之间的端 到端的隧道。  As shown in FIG. 3a, the present embodiment uses the cross-domain VPN Option C scenario as an example to describe the label allocation method of the present invention. In this scenario, the ASBR does not maintain or advertise VPN-IPv4 routes. In different ASs, AS: 100 and AS: 200 PEs, such as RR-1 (Route Reflector) and RR-2. Establish an EBGP connection in the Multihop mode to directly exchange VPN-IPv4 routes. The ASBR advertises IPv4 label routes to PEs in the ASs through MP-IBGP (Multi-Protocol internal BGP). The IPv4 label route to the PE device in the AS is notified to the ASBR peer of the peer AS. The purpose of the IPv4 label routing is to bond the tunnels in the respective domains to form end-to-end tunnels between PEs in different ASs, such as PE2 and PE4.
由于 ASBR不维护 VPN-IPv4路由， 仅发布 IPv4标签路由， 也就是说， ASBR无法得知路 由属于哪一个 VPN， 所以不能采用基于 VPN的标签分配方式， 只能采用基于路由的标签分配 方式， 标签消耗量大。  As the ASBR does not maintain the VPN-IPv4 route, only the IPv4 label route is advertised. That is, the ASBR cannot know which VPN the route belongs to. Therefore, the VPN-based label allocation mode cannot be adopted. Only the route-based label allocation method can be used. The consumption is large.
在这种情况下， 如图 3b所示， 本实施例的标签分配方法包括以下步骤。  In this case, as shown in FIG. 3b, the label distribution method of this embodiment includes the following steps.
301： 根据匹配条件匹配路由的特征， 得到匹配结果， 匹配条件包括： 所述路由的特征 是否为规定的特征和 /或多条路由的特征是否相同。  301: Match the characteristics of the route according to the matching condition, and obtain a matching result, where the matching condition includes: whether the feature of the route is a specified feature and/or whether the features of the multiple routes are the same.
具体地， 对于本发明实施例， 在 ASBR上匹配路由的特征。 该路由的特征可以为路由前 缀和路由掩码长度、 或仅为路由掩码长度。 相应地， 在本实施例中， 该匹配条件包括路由 前缀是否为预定的前缀和路由掩码长度是否为 32 位、 或者仅包括路由掩码长度是否为 32 位。  Specifically, for the embodiment of the present invention, the feature of the route is matched on the ASBR. The route can be characterized by a route prefix and a route mask length, or only a route mask length. Correspondingly, in this embodiment, the matching condition includes whether the route prefix is a predetermined prefix and the route mask length is 32 bits, or whether only the route mask length is 32 bits.
具体匹配过程为： 将每条路由与访问控制列表中配置的路由进行匹配， 所述访问控制 列表中配置有 32位主机路由的路由前缀和掩码长度、 或者仅配置有路由掩码长度。 进一步 地， 可以采用以下两种匹配方式：  The specific matching process is as follows: Each route is matched with a route configured in the ACL. The access control list is configured with a route prefix and a mask length of a 32-bit host route, or only a route mask length. Further, the following two matching methods can be used:
第一、 当 ASBR收到路由时， 检测路由的路由前缀和掩码长度， 将路由的路由前缀和 掩码长度与 ACL (Access Control-List , 访问控制列表） 中的配置相匹配， 这里 ACL中的 配置包括 PE设备的 Loopback接口地址上的路由的路由前缀和路由掩码长度，例如，在 ACL 中配置路由前缀为 1. 1. 1. 1 (掩码长度为 32)、 路由 2. 2. 2. 2 (掩码长度为 32)。 若符合匹 配条件， 即路由前缀和掩码长度都符合条件， 则判定该路由为 32位主机路由， 即 PE设备 的 Loopback接口地址上的路由。  First, when the ASBR receives the route, it detects the route prefix and mask length of the route, and matches the route prefix and mask length of the route with the configuration in the ACL (Access Control-List, Access Control List). The configuration includes the route prefix and the route mask length of the route on the loopback interface address of the PE device. For example, the route prefix configured in the ACL is 1. 1. 1. 1 (mask length is 32), route 2. 2. 2. 2 (mask length is 32). If the matching condition is met, that is, the route prefix and the mask length are both qualified, the route is determined to be a 32-bit host route, that is, the route on the loopback interface address of the PE device.
第二、 当 ASBR收到路由时， 将路由的掩码长度与 ACL中的配置相匹配， 这里， ACL中 的配置为掩码长度为 32位的路由， 若符合匹配条件， 即路由的掩码长度为 32位， 则判定 该路由是否为 32位主机路由。 302: 匹配结果为所述路由为 32位主机路由， 采用所述基于 路由的标签分配方式对于步骤 301 中匹配出的路由， 使用基于路由的标签分配方式， 不同 的路由分配不同的标签。 而 PE设备上， 则采用基于 VPN实例的标签分配方式或基于接口的 标签分配方式。 Second, when the ASBR receives the route, it matches the mask length of the route with the configuration in the ACL. Here, in the ACL. The configuration is a 32-bit route with a mask length of 32. If the matching condition is met, that is, the mask length of the route is 32 bits, it is determined whether the route is a 32-bit host route. 302: The matching result is that the route is a 32-bit host route, and the route-based label allocation manner is used. For the route matched in step 301, a route-based label allocation manner is used, and different routes are assigned different labels. On the PE, the label distribution mode based on the VPN instance or the label distribution method based on the interface is adopted.
对于其它网段路由， 即非 32位的路由， 可以分配标签 （如采用基于下一跳的标签分配 方式）， 也可以不分配标签。  For other network segment routes, that is, non-32-bit routes, you can assign labels (such as the next hop-based label allocation method), or you can not assign labels.
本实施例通过在 ASBR上匹配路由的特征， 匹配出 PE设备的 32位主机路由， 并为 PE 设备的 32位主机路由采用了基于路由的标签分配方式， 也就是说， 在 ASBR上仅针对 PE设 备的 Loopback接口地址上的路由采用了基于路由的标签分配方式， 这样， 在 ASBR设备上 对于不同的 PE ( 32位主机路由）就设置有不同的标签， 从而可以建立从 PE2到 PE4的端到 端的隧道， 从而保证数据的传输。 同时， 对于其他网段路由， 不分配标签或采用基于下一 跳的标签分配方式， 与现有的对所有的路由都采用基于路由的标签分配方式相比， 有效节 省了标签资源。  In this embodiment, the matching of the routing features on the ASBR matches the 32-bit host route of the PE device, and the route-based label allocation mode is adopted for the 32-bit host route of the PE device, that is, only the PE is applied to the ASBR. The route on the loopback interface address of the device adopts the route-based label allocation mode. In this way, different labels are set for different PEs (32-bit host routes) on the ASBR device, so that the PE2 to PE4 end can be established. The tunnel at the end ensures data transmission. At the same time, for other network segment routes, no label is allocated or a label allocation method based on the next hop is adopted, which effectively saves label resources compared with the existing route-based label allocation method for all routes.
在 PE设备上， 则采用基于 VPN实例的标签分配方式或基于接口的标签分配方式。 由于 On a PE device, a VPN instance-based label allocation method or an interface-based label allocation method is adopted. due to
ASBR可以区分出 PE设备的 32位主机路由， 在 PE设备之间建立隧道， 所以 PE设备上可以 采用基于 VPN实例的标签分配方式或基于接口的标签分配方式， 进而在 PE设备上也节省了 标签资源。 实施例 4 The ASBR can distinguish the 32-bit host route of the PE device and establish a tunnel between the PE devices. Therefore, the PE device can use the label distribution mode based on the VPN instance or the label distribution mode based on the interface, thereby saving labels on the PE device. Resources. Example 4
如图 4a所示， 本实施例以跨域 VPN Option B场景为例说明本发明的标签分配方法。 在该场景下， 不同 AS中的 ASBR， 即图中的 ASBR1和 ASBR2，通过 MP-EBGP (Multi-Protocol extension BGP， 多协议外部边界网关协议） 交换它们从各自 AS的 PE设备接收的 VPN_IPv4 路由， 再把从对方学习到的路由发送给域内的 PE设备。 ASBR1和 ASBR2在传递路由时， 需 要改变路由的下一跳， 即当 ASBR1将从域内 PE学习到的路由转发给域外的 ASBR2时将路由 的下一跳改变为 ASBR1 , 而当 ASBR1将从 ASBR2学习到的路由转发给域内 PE时， 也将下一 跳改变为 ASBR1。 为了节约标签资源， 在各 AS内的 PE设备， 如 PE1可以采用基于 VPN的标 签分配方式或基于接口的标签分配方式。 而为了保证网络的稳定性， 一个 CE设备， 如 CE1 通常会通过两个 PE设备， 如 PE1和另一个未示出的 PE设备， 与 ASBR1连接， 其中一个用 于备份路由。 在这种情况下， 若 ASBR1也采用基于 VPN的标签分配方式， 那么来自这两个 PE设备的 路由将会分配到同一个标签，在数据传输的过程中， ASBR1 无法判断将接收到的数据转发给 哪一个 PE设备， 也就是说， 传输数据的隧道无法建立。 同样的， 若采用基于接口的标签分 配方式， ASBR的一个接口会接收到来自不同 PE设备的路由，为这些路由分配同一个标签后， 当 ASBR收到数据， 同样无法判断将其发送给哪一个 PE， 传输数据的隧道无法建立。 所以在 这种场景下， 现有技术也只能采用基于路由的标签分配方式， 标签消耗量很大。 As shown in FIG. 4a, the cross-domain VPN Option B scenario is taken as an example to describe the label distribution method of the present invention. In this scenario, the ASBRs in different ASs, that is, ASBR1 and ASBR2 in the figure, exchange the VPN_IPv4 routes they receive from the PEs of the respective ASs through MP-EBGP (Multi-Protocol Extension BGP). The route learned from the other party is sent to the PE device in the domain. ASBR1 and ASBR2 need to change the next hop of the route when the route is forwarded. When ASBR1 forwards the route learned from the PE in the domain to ASBR2 outside the domain, the next hop of the route is changed to ASBR1, and ASBR1 learns from ASBR2. When the obtained route is forwarded to the PE in the domain, the next hop is also changed to ASBR1. To save label resources, PE devices in each AS, such as PE1, can adopt a VPN-based label allocation method or an interface-based label allocation method. To ensure the stability of the network, a CE device, such as CE1, usually connects to ASBR1 through two PE devices, such as PE1 and another PE device, not shown, one of which is used for backup routing. In this case, if ASBR1 also adopts the VPN-based label allocation method, the routes from the two PE devices will be assigned to the same label. In the process of data transmission, ASBR1 cannot judge the data to be received. Which PE device is given, that is, the tunnel for transmitting data cannot be established. Similarly, if an interface-based label allocation method is adopted, an interface of the ASBR receives routes from different PE devices. After the same label is assigned to these routes, when the ASBR receives the data, it cannot determine which one to send it to. PE, the tunnel for transmitting data could not be established. Therefore, in this scenario, the prior art can only adopt a route-based label allocation method, and the label consumption is large.
如图 4b所示， 本实施例的标签分配方法包括以下步骤。  As shown in FIG. 4b, the label distribution method of this embodiment includes the following steps.
401： 根据匹配条件匹配路由的特征， 得到匹配结果， 匹配条件包括： 所述路由的特征 是否为规定的特征和 /或多条路由的特征是否相同。  401: Match the characteristics of the route according to the matching condition, and obtain a matching result, where the matching condition includes: whether the feature of the route is a specified feature and/or whether the features of the multiple routes are the same.
具体地， 在 ASBR上分别匹配学习到的多条路由的 VPN标签和路由的下一跳， 得到匹配 结果。 如果 VPN标签相同， 则说明这些路由来自同一 VPN实例， 如果路由的下一跳相同， 则说明这些路由由同一 PE设备转发。 也就是说， 在本实施例中， 匹配条件为多条路由的特 征是否相同。 更进一步地， 匹配条件为多条路由的 VPN标签是否相同和多条路由的下一跳 是否相同。  Specifically, the VPN label of the learned multiple routes and the next hop of the route are respectively matched on the ASBR to obtain a matching result. If the VPN labels are the same, the routes are from the same VPN instance. If the next hop of the route is the same, the routes are forwarded by the same PE. That is to say, in this embodiment, the matching condition is whether the characteristics of the plurality of routes are the same. Further, the matching condition is whether the VPN labels of the multiple routes are the same and whether the next hops of the multiple routes are the same.
402： 根据所述匹配结果为所述路由选择相应的标签分配方式。  402: Select, according to the matching result, a corresponding label allocation manner for the routing.
具体地， 若路由的 VPN标签相同且下一跳相同， 则对下一跳相同且 VPN标签相同的路 由分配同一个标签， 而对于 VPN标签或下一跳不同的路由， 分配不同的标签。 这种分配方 式称为基于下一跳的标签分配方式， 也称为基于邻居的标签分配方式。  Specifically, if the routed VPN labels are the same and the next hops are the same, the same label is assigned to the same route with the same next hop and the same VPN label, and different labels are assigned to the VPN label or the next hop different route. This type of allocation is called the next hop based label allocation method, also known as the neighbor based label allocation method.
本实施例的标签分配方法通过在 ASBR上进行路由特征的匹配， 对于下一跳相同且 VPN 标签相同的路由采用基于下一跳的标签分配方式， 由于域内域外的路由在 ASBR上都需要将 标签变为本地分配的标签， 所以采用基于下一跳的标签分配方式， 可以避免前述在数据传 输的过程中， ASBR1无法判断将接收到的数据转发给哪一个 PE设备的情况， 从而可以建立 从 PE建立到 ASBR， 再从域内 ASBR建立到域外的 ASBR的隧道， 也就是说， 本发明实施例可 以在正确路由的前提下有效节省标签资源， 保证数据的传输。 实施例 5  The label allocation method in this embodiment performs the matching of the routing features on the ASBR, and uses the label allocation mode based on the next hop for the routes with the same next hop and the same VPN label, because the routes outside the domain need to be labeled on the ASBR. The label is allocated locally. Therefore, the label allocation method based on the next hop can avoid the situation in which the ASBR1 cannot determine which PE device to forward the received data to during the data transmission process, so that the PE can be established. The ASBR is established, and the ASBR is established from the intra-domain ASBR to the ASBR of the out-of-domain. That is, the embodiment of the present invention can effectively save label resources and ensure data transmission under the premise of correct routing. Example 5
如图 5所示， 本发明实施例提供了一种标签分配装置， 该装置包括：  As shown in FIG. 5, an embodiment of the present invention provides a label distribution apparatus, which includes:
匹配模块 501， 用于根据匹配条件匹配路由的特征， 得到匹配结果， 匹配条件包括： 所 述路由的特征是否为规定的特征和 /或多条路由的特征是否相同；  The matching module 501 is configured to match the characteristics of the route according to the matching condition, and obtain a matching result, where the matching condition includes: whether the feature of the route is a specified feature and/or whether the features of the multiple routes are the same;
执行模块 502， 用于根据匹配模块 501的匹配结果为该路由选择相应的标签分配方式， 所述标签分配方式包括： 基于路由的标签分配方式、 基于 VPN 的标签分配方式、 基于接口 的标签分配方式、 和基于下一跳的标签分配方式。 The executing module 502 is configured to select a corresponding label allocation manner for the route according to the matching result of the matching module 501. The label allocation manner includes: a route-based label allocation manner, a VPN-based label allocation manner, an interface-based label allocation manner, and a next hop-based label allocation manner.
具体地， 前述路由的特征包括： 路由前缀、 路由掩码长度、 边界网关协议路由属性和 路由的 VPN标签。 相应地， 前述匹配条件包括： 路由掩码长度是否为规定的长度、 路由前 缀是否为规定的路由前缀、 多条路由的 VPN标签是否相同、 以及多条路由的下一跳是否相 同中的一种或多种的结合。  Specifically, the foregoing routing features include: a route prefix, a route mask length, a border gateway protocol route attribute, and a VPN label of the route. Correspondingly, the foregoing matching condition includes: whether the route mask length is a specified length, whether the route prefix is a specified route prefix, whether the VPN labels of the multiple routes are the same, and whether the next hops of the multiple routes are the same. Or a combination of multiple.
可选地， 匹配模块 501包括：  Optionally, the matching module 501 includes:
掩码长度匹配单元， 用于根据访问控制列表对每条路由的掩码长度进行匹配； 或 路由前缀匹配单元， 用于将每条路由与访问控制列表中配置的路由前缀进行匹配。 可选地， 匹配模块 501包括：  The mask length matching unit is configured to match the mask length of each route according to the access control list; or a route prefix matching unit, configured to match each route with a route prefix configured in the access control list. Optionally, the matching module 501 includes:
标签匹配单元， 用于匹配路由的 VPN标签；  a label matching unit, configured to match a routed VPN label;
下一跳匹配单元， 用于匹配路由的下一跳。  The next hop matching unit is used to match the next hop of the route.
本实施例涉及的标签分配装置与方法实施例中的标签分配属于同一构思， 其具体实现 过程详见方法实施例， 这里不再赘述。  The label distribution device in this embodiment is the same as the label distribution in the method embodiment. The specific implementation process is described in the method embodiment, and details are not described herein again.
需要说明的是， 该装置可以配置在 PE设备上， 也可以配置在 ASBR上， 可以根据不同 的网络部署场景选择。  It should be noted that the device can be configured on the PE device or on the ASBR, and can be selected according to different network deployment scenarios.
如前所述， 本发明实施例通过匹配路由的特征来为路由选择相应的标签分配方式， 可 以有效节省标签资源。 此外， 通过将标签分配方式与路由的特征相对应， 从而可以对标签 分配方式进行统一的管理， 应用比较灵活， 有利于根据网络部署场景的需求增加新的标签 分配方式。 实施例 6  As described above, the embodiment of the present invention can effectively save label resources by matching the characteristics of the route to select a corresponding label allocation manner for routing. In addition, the label allocation mode is matched with the characteristics of the route, so that the label allocation mode can be uniformly managed, and the application is flexible, which is beneficial to adding a new label distribution manner according to the requirements of the network deployment scenario. Example 6
本发明实施例提供了一种标签分配***， 该***包括： 属于第一自治***的多个第一 提供商边界路由器和第一用户边界路由器、 以及属于第二自治***的多个第二提供商边界 路由器和第二用户边界路由器， 至少一个所述第一提供商边界路由器和至少一个第二提供 商边界路由器相互连接， 所述相互连接的所述第一提供商边界路由器和第二提供商边界路 由器上设置有前述标签分配装置。 进一步地， 在图 2a中， AS : 100为第一自治***， AS : 200为第二自治***， CE1、 CE2、 PE3、 PE4为第一提供商边界路由器， PE1、 PE2为第二提 供商边界路由器， CE1和 CE2还表示第一用户边界路由器， CE1和 CE2上设置有前述标签分 配装置。 在图 3a中， AS : 100为第一自治***， AS : 200为第二自治***， ASBR1、 PE1、 PE2为 为第一提供商边界路由器， CE1、 CE2 为第一用户边界路由器， ASBR2、 PE3、 PE4 为第二提 供商边界路由器， CE3、 CE4为第二用户边界路由器， ASBR1和 ASBR2上设置有前述标签分 配装置。 An embodiment of the present invention provides a label distribution system, including: a plurality of first provider border routers and a first user border router belonging to the first autonomous system, and a plurality of second providers belonging to the second autonomous system. a border router and a second user border router, at least one of the first provider border router and at least one second provider border router interconnecting, the interconnected first provider border router and second provider border The aforementioned label distribution device is provided on the router. Further, in FIG. 2a, AS: 100 is the first autonomous system, AS: 200 is the second autonomous system, and CE1, CE2, PE3, and PE4 are the first provider border routers, and PE1 and PE2 are the second provider boundaries. The routers, CE1 and CE2 also represent the first user border router, and the aforementioned label distribution means are provided on CE1 and CE2. In Figure 3a, AS: 100 is the first autonomous system, AS: 200 is the second autonomous system, ASBR1, PE1, and PE2 are the first provider border routers, and CE1 and CE2 are the first user border routers, ASBR2, and PE3. PE4 is a second provider border router, CE3 and CE4 are second user border routers, and the foregoing label distribution devices are disposed on ASBR1 and ASBR2.
在图 4a中， AS : 100为第一自治***， AS : 200为第二自治***， ASBR1、 PE1、 PE2为 为第一提供商边界路由器， CE1、 CE2 为第一用户边界路由器， ASBR2、 PE3、 PE4 为第二提 供商边界路由器， CE3、 CE4为第二用户边界路由器， ASBR1和 ASBR2上设置有前述标签分 配装置。 本领域普通技术人员可以理解实现上述实施例的全部或部分步骤可以通过硬件来完 成， 也可以通过程序来指令相关的硬件完成， 所述的程序可以存储于一种计算机可读存储 介质中， 上述提到的存储介质可以是只读存储器， 磁盘或光盘等。 以上所述仅为本发明的较佳实施例， 并不用以限制本发明， 凡在本发明的精神和原则 之内， 所作的任何修改、 等同替换、 改进等， 均应包含在本发明的保护范围之内。  In Figure 4a, AS: 100 is the first autonomous system, AS: 200 is the second autonomous system, ASBR1, PE1, and PE2 are the first provider border routers, and CE1 and CE2 are the first user border routers, ASBR2, and PE3. PE4 is a second provider border router, CE3 and CE4 are second user border routers, and the foregoing label distribution devices are disposed on ASBR1 and ASBR2. A person skilled in the art may understand that all or part of the steps of implementing the above embodiments may be completed by hardware, or may be instructed by a program to execute related hardware, and the program may be stored in a computer readable storage medium. The storage medium mentioned may be a read only memory, a magnetic disk or an optical disk or the like. The above is only the preferred embodiment of the present invention, and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc., which are within the spirit and scope of the present invention, should be included in the protection of the present invention. Within the scope.

Claims

权 利 要 求 书 Claim
1、 一种标签分配方法， 其特征在于， 所述方法包括：  A label distribution method, the method comprising:
根据匹配条件匹配路由的特征， 得到匹配结果， 所述匹配条件包括： 所述路由的特征是 否为规定的特征和 /或多条路由的特征是否相同； 及  Matching the characteristics of the route according to the matching condition, and obtaining a matching result, where the matching condition includes: whether the feature of the route is a specified feature and/or whether the features of the multiple routes are the same;
根据所述匹配结果为所述路由选择相应的标签分配方式， 所述标签分配方式包括： 基于 路由的标签分配方式、 基于 VPN的标签分配方式、 基于接口的标签分配方式、 和基于下一跳 的标签分配方式。  And performing, according to the matching result, a corresponding label allocation manner for the routing, where the label allocation manner includes: a route-based label allocation manner, a VPN-based label allocation manner, an interface-based label allocation manner, and a next hop based How labels are assigned.
2、 如权利要求 1所述的方法， 其特征在于， 所述根据匹配条件匹配路由的特征， 具体包 括- 将每条路由与访问控制列表中配置的路由进行匹配，所述访问控制列表中配置有 32位主 机路由的路由前缀和掩码长度、 或者仅配置有路由掩码长度。 The method according to claim 1, wherein the matching the characteristics of the route according to the matching condition specifically includes: matching each route with a route configured in the access control list, where the access control list is configured The route prefix and mask length of a 32-bit host route, or only the route mask length.
3、 如权利要求 2所述的方法， 其特征在于， 所述根据所述匹配结果为所述路由选择相应 的标签分配方式， 具体包括： The method according to claim 2, wherein the determining, by the matching result, the corresponding label allocation manner for the routing, specifically includes:
若所述匹配结果为所述路由为 32位主机路由， 则采用所述基于路由的标签分配方式。  If the matching result is that the route is a 32-bit host route, the route-based label allocation mode is adopted.
4、 如权利要求 3所述的方法， 其特征在于， 所述根据所述匹配结果为所述路由选择相应 的标签分配方式， 还包括： The method according to claim 3, wherein the determining, by the matching result, the corresponding label allocation manner for the routing, further comprising:
若所述匹配结果为所述路由为 32位主机路由之外的网段路由，则对所述网段路由不分配 标签。  If the matching result is that the route is a network segment route other than the 32-bit host route, no label is allocated to the network segment route.
5、 如权利要求 1所述的方法， 其特征在于， 所述根据匹配条件匹配路由的特征， 具体包 括： The method according to claim 1, wherein the matching the characteristics of the route according to the matching condition comprises:
分别匹配本设备所有路由的虚拟专用网标签和路由的下一跳。  Match the virtual private network labels of all routes of the device and the next hop of the route.
6、 如权利要求 5所述的方法， 其特征在于， 所述根据所述匹配结果为所述路由选择相应 的标签分配方式， 具体包括： The method according to claim 5, wherein the determining, by the matching result, the corresponding label allocation manner for the routing, specifically includes:
若所述匹配结果为所述路由具有相同的虚拟专用网标签且下一跳相同， 则为所述标签分 配同一个标签。 If the matching result is that the route has the same virtual private network label and the next hop is the same, then the label is Match the same label.
7、 一种标签分配装置， 其特征在于， 所述装置包括： 7. A label dispensing device, the device comprising:
匹配模块， 用于根据匹配条件匹配路由的特征， 得到匹配结果， 所述匹配条件包括： 所 述路由的特征是否为规定的特征和 /或多条路由的特征是否相同； 及  a matching module, configured to match a feature of the route according to the matching condition, to obtain a matching result, where the matching condition includes: whether the feature of the route is a specified feature and/or whether the features of the multiple routes are the same;
执行模块， 用于根据所述匹配模块的匹配结果为所述路由选择相应的标签分配方式， 所 述标签分配方式包括： 基于路由的标签分配方式、 基于 VPN的标签分配方式、 基于接口的标 签分配方式、 和基于下一跳的标签分配方式。  An execution module, configured to select, according to the matching result of the matching module, a corresponding label allocation manner for the routing, where the label allocation manner includes: a route-based label allocation manner, a VPN-based label allocation manner, and an interface-based label distribution manner. Mode, and label allocation based on next hop.
8、 如权利要求 7所述的装置， 其特征在于， 所述匹配模块包括： 8. The apparatus according to claim 7, wherein the matching module comprises:
掩码长度匹配单元， 用于根据访问控制列表对每条路由的掩码长度进行匹配； 或 路由前缀匹配单元， 用于将每条路由与访问控制列表中配置的路由前缀进行匹配。  The mask length matching unit is configured to match the mask length of each route according to the access control list; or a route prefix matching unit, configured to match each route with a route prefix configured in the access control list.
9、 如权利要求 7所述的装置， 其特征在于， 所述匹配模块包括： 9. The apparatus of claim 7, wherein the matching module comprises:
标签匹配单元， 用于匹配路由的虚拟专用网标签；  a tag matching unit, configured to match a routed virtual private network label;
下一跳匹配单元， 用于匹配路由的下一跳。  The next hop matching unit is used to match the next hop of the route.
10、 一种标签分配***， 所述***包括： 属于第一自治***的多个第一提供商边界路由 器和第一用户边界路由器、 以及属于第二自治***的多个第二提供商边界路由器和第二用户 边界路由器， 至少一个所述第一提供商边界路由器和至少一个第二提供商边界路由器相互连 接， 其特征在于， 10. A label distribution system, the system comprising: a plurality of first provider border routers belonging to a first autonomous system and a first user border router, and a plurality of second provider border routers belonging to the second autonomous system and a second user border router, at least one of the first provider border routers and at least one second provider border router being interconnected, wherein
所述相互连接的所述第一提供商边界路由器和第二提供商边界路由器上设置有如权利要 求 7-9任一项所述的标签分配装置。  The first provider border router and the second provider border router that are connected to each other are provided with the label allocating device according to any one of claims 7-9.
PCT/CN2011/077759 2011-07-28 2011-07-28 Tag allocating method, device and system WO2012159351A1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2011/077759 WO2012159351A1 (en) 2011-07-28 2011-07-28 Tag allocating method, device and system
CN201180001405.1A CN103026667B (en) 2011-07-28 2011-07-28 A kind of label distribution method, device and system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2011/077759 WO2012159351A1 (en) 2011-07-28 2011-07-28 Tag allocating method, device and system

Publications (1)

Publication Number Publication Date
WO2012159351A1 true WO2012159351A1 (en) 2012-11-29

Family

ID=47216578

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/077759 WO2012159351A1 (en) 2011-07-28 2011-07-28 Tag allocating method, device and system

Country Status (2)

Country Link
CN (1) CN103026667B (en)
WO (1) WO2012159351A1 (en)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10225182B2 (en) * 2017-02-28 2019-03-05 Juniper Networks, Inc. Apparatus, system, and method for facilitating label-identified routing decisions by iBGP peers
CN113315707B (en) * 2021-05-26 2022-11-18 西安热工研究院有限公司 Method for label routing of multi-site cascade mode data transmission middleware

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050117592A1 (en) * 1998-10-30 2005-06-02 Kabushiki Kaisha Toshiba Router device and label switched path control method using upstream initiated aggregation
CN101014014A (en) * 2007-02-09 2007-08-08 华为技术有限公司 Routing aggregation method, packet transmitting method and border router of autonomous system
CN101106519A (en) * 2006-07-12 2008-01-16 华为技术有限公司 Distribution method for boundary routers of autonomous system and boundary router
CN101572669A (en) * 2009-05-27 2009-11-04 中兴通讯股份有限公司 Transmitting method of VPN message as well as allocating and deleting method of the router marks thereof

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050117592A1 (en) * 1998-10-30 2005-06-02 Kabushiki Kaisha Toshiba Router device and label switched path control method using upstream initiated aggregation
CN101106519A (en) * 2006-07-12 2008-01-16 华为技术有限公司 Distribution method for boundary routers of autonomous system and boundary router
CN101014014A (en) * 2007-02-09 2007-08-08 华为技术有限公司 Routing aggregation method, packet transmitting method and border router of autonomous system
CN101572669A (en) * 2009-05-27 2009-11-04 中兴通讯股份有限公司 Transmitting method of VPN message as well as allocating and deleting method of the router marks thereof

Also Published As

Publication number Publication date
CN103026667A (en) 2013-04-03
CN103026667B (en) 2016-05-25

Similar Documents

Publication Publication Date Title
EP3836490B1 (en) Vpn cross-domain implementation method, device, and border node
JP6966419B2 (en) Network service path calculation element Centralized controller (PCECC)
CN108574630B (en) EVPN message processing method, device and system
CN111510379B (en) EVPN message processing method, device and system
CN105939257B (en) Communication means and router
WO2016066072A1 (en) Method and device for realizing communication between nvo3 network and mpls network
JP6030649B2 (en) Label switch path (LSP) tunneling model signaling
WO2015165311A1 (en) Method for transmitting data packet and provider edge device
WO2015070667A1 (en) Method for issuing route information, and method and apparatus for transmitting packet
WO2018103099A1 (en) Method, device and system for sending and receiving message
EP2214352A1 (en) Layer two virtual private network cross-domain implementation (l2vpn) method, system and device
WO2013182061A1 (en) Network label distribution method, device and system
WO2017193733A1 (en) Route propagation method, and node
WO2017114158A1 (en) Method and device for publishing tenant routing in nvo3 network
WO2013139270A1 (en) Method, device, and system for implementing layer3 virtual private network
WO2019205836A1 (en) Data packet forwarding method and apparatus
WO2014180153A1 (en) Method, device and system for establishing label switched path
WO2005114944A1 (en) A method for implementing ipv4 and ipv6 mixing sites virtual private network
WO2011147341A1 (en) Method and network device for distributing multi-protocol label switching labels
EP2832055B1 (en) Pseudowire groups in a packet switched network
JP5913733B2 (en) Pseudowire extended group messaging in packet-switched networks
WO2012159351A1 (en) Tag allocating method, device and system
CN103095578B (en) Routing iinformation control method in MPLS L3VPN network and PE equipment
WO2024001553A1 (en) Routing publishing method, electronic device and computer-readable storage medium
WO2014082430A1 (en) Packet control method and device

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 201180001405.1

Country of ref document: CN

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 11866056

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 11866056

Country of ref document: EP

Kind code of ref document: A1