WO2012159351A1 - Procédé, dispositif et système d'allocation de label - Google Patents

Procédé, dispositif et système d'allocation de label 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
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2011/077759
Other languages
English (en)
Chinese (zh)
Inventor
孙春霞
张栋
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
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
Priority to CN201180001405.1A priority Critical patent/CN103026667B/zh
Priority to PCT/CN2011/077759 priority patent/WO2012159351A1/fr
Publication of WO2012159351A1 publication Critical patent/WO2012159351A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

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

La présente invention se rapporte à un procédé et à un dispositif d'allocation de label. L'invention appartient au domaine technique des communications. Le procédé selon l'invention consiste : à mettre en correspondance les caractéristiques d'une voie d'acheminement sur la base de conditions de concordance dans le but d'obtenir des résultats de concordance, les conditions de concordance consistant : à déterminer si les caractéristiques de la voie d'acheminement sont des caractéristiques définies, ou non, et/ou si les caractéristiques de différentes voies d'acheminement sont identiques; et à sélectionner un mode d'allocation de label correspondant pour la voie d'acheminement, sur la base des résultats de concordance. Le dispositif selon l'invention comprend un module de mise en correspondance et un module d'exécution. D'après la solution technique de la présente invention, en mettant en correspondance les caractéristiques d'une voie d'acheminement, il est possible de sélectionner un mode d'allocation de label correspondant pour la voie d'acheminement, de réaliser une économie efficace des ressources de labels, et d'accroître de façon avantageuse et flexible le nombre de modes d'allocation de labels en fonction des exigences de divers scénarios de déploiement de réseau.
PCT/CN2011/077759 2011-07-28 2011-07-28 Procédé, dispositif et système d'allocation de label Ceased WO2012159351A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201180001405.1A CN103026667B (zh) 2011-07-28 2011-07-28 一种标签分配方法、装置和系统
PCT/CN2011/077759 WO2012159351A1 (fr) 2011-07-28 2011-07-28 Procédé, dispositif et système d'allocation de label

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2011/077759 WO2012159351A1 (fr) 2011-07-28 2011-07-28 Procédé, dispositif et système d'allocation de label

Publications (1)

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

Family

ID=47216578

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/077759 Ceased WO2012159351A1 (fr) 2011-07-28 2011-07-28 Procédé, dispositif et système d'allocation de label

Country Status (2)

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

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 (zh) * 2021-05-26 2022-11-18 西安热工研究院有限公司 一种多站点级联模式数据传输中间件标签路由的方法

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 (zh) * 2007-02-09 2007-08-08 华为技术有限公司 路由聚合方法、报文转发方法以及自治系统边界路由器
CN101106519A (zh) * 2006-07-12 2008-01-16 华为技术有限公司 自治系统边界路由器路由发布方法及自治系统边界路由器
CN101572669A (zh) * 2009-05-27 2009-11-04 中兴通讯股份有限公司 Vpn报文的转发方法及其路由标签的分配、删除方法

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 (zh) * 2006-07-12 2008-01-16 华为技术有限公司 自治系统边界路由器路由发布方法及自治系统边界路由器
CN101014014A (zh) * 2007-02-09 2007-08-08 华为技术有限公司 路由聚合方法、报文转发方法以及自治系统边界路由器
CN101572669A (zh) * 2009-05-27 2009-11-04 中兴通讯股份有限公司 Vpn报文的转发方法及其路由标签的分配、删除方法

Also Published As

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

Similar Documents

Publication Publication Date Title
CN111865796B (zh) 用于网络业务的路径计算单元中央控制器（pcecc）
CN111510379B (zh) Evpn报文处理方法、设备及系统
WO2020029976A1 (fr) Procédé de mise en oeuvre inter-domaine de réseau privé virtuel, dispositif et noeud frontière
CN103634217B (zh) 路由信息发布的方法、传输报文的方法及装置
WO2018166253A1 (fr) Procédé, dispositif et système de traitement de paquets evpn
CN101090355B (zh) 虚拟专用网隧道的标签交换路径建立方法、系统和设备
JP6030649B2 (ja) ラベルスイッチパス（ｌｓｐ）トンネリングモデルのシグナリング
WO2016066072A1 (fr) Procédé et dispositif d'exécution de communication entre un réseau nvo3 et un réseau mpls
WO2015165311A1 (fr) Procédé permettant de transmettre un paquet de données et dispositif côté fournisseur
WO2018103099A1 (fr) Procédé, dispositif et système d'envoi et de réception de message
WO2013182061A1 (fr) Procédé, dispositif et système de distribution d'étiquettes de réseau
CN103326915A (zh) 实现三层虚拟专用网络的方法、设备及系统
WO2017193733A1 (fr) Procédé de propagation d'itinéraire et nœud
WO2014180153A1 (fr) Procédé, dispositif et système d'établissement d'un chemin commuté par étiquette
WO2017114158A1 (fr) Procédé et dispositif de publication d'acheminement d'occupants dans un réseau nvo3
CN104247346B (zh) 分组交换网络中的伪线路扩展的群组消息传送
CN103634210B (zh) 发现vpls实例的对端pe设备的方法及设备
CN101557334B (zh) Mpls vpn、其vpn多实例用户边缘设备及其实现方法
JP2015512587A (ja) パケット交換網における擬似回線グループ
WO2012159351A1 (fr) Procédé, dispositif et système d'allocation de label
CN102340449B (zh) 一种私网报文传输方法、设备及系统
WO2024001553A1 (fr) Procédé de publication de routage, dispositif électronique et support de stockage lisible par ordinateur
WO2014082430A1 (fr) Procédé et dispositif de contrôle de paquets
WO2012016392A1 (fr) Procédé et système pour pseudo fil multi-segment partageant une bande passante et noeud de bord de fournisseur de ce système
JP2015512590A (ja) パケット交換網における擬似回線拡張グループアクション

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