WO2015149623A1 - 一种业务隧道建立方法及设备 - Google Patents

一种业务隧道建立方法及设备 Download PDF

Info

Publication number
WO2015149623A1
WO2015149623A1 PCT/CN2015/074488 CN2015074488W WO2015149623A1 WO 2015149623 A1 WO2015149623 A1 WO 2015149623A1 CN 2015074488 W CN2015074488 W CN 2015074488W WO 2015149623 A1 WO2015149623 A1 WO 2015149623A1
Authority
WO
WIPO (PCT)
Prior art keywords
tunnel
edge device
service
vpn service
request identifier
Prior art date
Application number
PCT/CN2015/074488
Other languages
English (en)
French (fr)
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 华为技术有限公司
Publication of WO2015149623A1 publication Critical patent/WO2015149623A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4633—Interconnection of networks using encapsulation techniques, e.g. tunneling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]

Definitions

  • the present invention relates to the field of network technologies, and in particular, to a method and a device for establishing a service tunnel.
  • EPC evolved Packet Core
  • CSG Cell Site Gateway
  • PE Provider Edge
  • AS autonomous system
  • S1 service connection needs to be established between the base station and the EPC.
  • the bearer network can better carry the LTE S1 service.
  • the industry currently considers the seamless multiprotocol label switch (Seamless Multiprotocol Label Switch).
  • the Seamless MPLS solution is a relatively optimized bearer solution.
  • the entire network is carried by the Seamless MPLS solution.
  • the user-side PE User-end
  • UPE Provider Edge
  • NPE Network Provider Edge
  • UPE-2 advertises a Border Gateway Protocol (BGP) label route to UPE-1, and establishes an end-to-end border gateway protocol label switching path between UPE-1 and UPE-2.
  • BGP Border Gateway Protocol
  • UPE-1 sends a BGP label route to UPE-2, and a BGP LSP that reaches UPE-1 is established between UPE-2 and UPE-1. All the services are iterated on the established BGP LSP, and then the BGP LSP is carried on the three segmented tunnels to implement the end-to-end bearer of the service.
  • the present invention provides a method and an apparatus for establishing a service tunnel.
  • the method and apparatus provided by the present invention solve all the services in the prior art, and only one tunnel can be selected to be carried in one domain, and different services cannot be implemented by using different tunnels.
  • the present invention provides a method for establishing a service tunnel, the method comprising:
  • the destination edge device that receives the label route corresponding to the VPN service is received.
  • the destination edge device uses the obtained tunnel request identifier to match the tunnel already established in the area to which the tunnel belongs, and if the matching result of the tunnel request identifier and any one of the established tunnels satisfies a preset condition, the target edge device selects The any tunnel carries the VPN service.
  • the destination edge device uses the obtained tunnel requirement identifier to match the established tunnel in the area to which the user belongs:
  • the destination edge device performs an operation result on the tunnel request identifier and the identifier of the tunnel that has been established by using the preset algorithm, and determines an established tunnel that needs to carry the VPN service according to the operation result.
  • the tunnel request identifier is a service affinity attribute
  • the established tunnel includes: matching the calculation result with the tunnel management attribute stored by the destination edge device, and determining an established tunnel that needs to carry the VPN service according to the matching result.
  • the method further includes:
  • the second edge device obtains a transit tunnel from the label route, and iteratively forms the transit tunnel to form a complete service tunnel of the first edge device to the second edge device, where the transit tunnel is the The tunnel selected by other edge devices carried in the label route.
  • the method further includes:
  • the tunnel request identifier is matched with the tunnel request identifier corresponding to the established tunnel. If the tunnel request identifier is the same as the tunnel request identifier corresponding to any tunnel, the VPN service is sent by using the tunnel determined by the matching.
  • the present invention provides another method for establishing a service tunnel, the method comprising:
  • the first edge device of the first area When the first edge device of the first area needs to open a virtual private network VPN service between the at least one intermediate area and the second edge device of the second area, the first edge device will use a tunnel corresponding to the VPN service. Adding an identifier to the label route corresponding to the VPN service;
  • the edge device that receives the label route obtains the tunnel request identifier from the label route, and the edge device that receives the label route uses the tunnel request identifier to match the area to which the label belongs. If the matching result of the tunnel request identifier and any one of the established tunnels meets a preset condition, the tunnel is selected to carry the VPN service.
  • the present invention provides an edge device, the edge device comprising:
  • An acquiring unit configured to receive a label corresponding to the VPN service, when a first edge device of the first area needs to open a virtual private network VPN service between the at least one intermediate area and the second edge device of the second area Routing, and obtaining a tunnel request identifier corresponding to the VPN service from the label route;
  • a tunnel selection unit configured to use the acquired tunnel request identifier to match an already established tunnel in the area to which the tunnel belongs, if the tunnel request identifier is associated with any tunnel in the established tunnel If the matching result meets the preset condition, the any tunnel is selected to carry the VPN service.
  • the tunnel selection unit is further configured to perform an operation result on the tunnel request identifier and the identifier of the tunnel that has been established by using a preset algorithm, according to an operation result, according to The operation result determines an already established tunnel that needs to carry the VPN service.
  • the tunnel requirement is identified as a service affinity attribute
  • the tunnel selection unit is further configured to store the calculation result and the self.
  • the tunnel management attributes are matched, and the established tunnel that needs to carry the VPN service is determined according to the matching result.
  • the edge device when the edge device is the second edge device, the edge device further includes:
  • a tunneling iteration unit configured to obtain a transit tunnel from the label route, and iteratively form the transit tunnel to form a complete service tunnel of the first edge device to the second edge device, where the transit tunnel is The tunnel selected by other edge devices carried in the label route.
  • the edge device further includes:
  • a service matching unit configured to acquire the tunnel request identifier from the VPN service route when receiving the VPN service route sent by the first edge device, and use the tunnel request identifier to identify a tunnel request corresponding to the established tunnel The identifier is matched. If the tunnel request identifier is the same as the tunnel request identifier corresponding to any tunnel, the VPN service is sent by using the tunnel determined by the matching.
  • the present invention further provides another edge device, wherein the edge device is a first edge device of the first region, wherein when the first edge device spans at least one intermediate region and a second edge of the second region
  • the first edge device includes:
  • An identifier adding unit configured to add a tunnel requirement identifier corresponding to the VPN service to a label route corresponding to the VPN service;
  • a forwarding unit configured to forward the label routing, so that the edge of the label routing is received
  • the foregoing method provided by the embodiment of the present invention initiates an edge device of a virtual private network (VPN) service, and allocates a corresponding tunnel request identifier to different services according to requirements of different services for the tunnel, and identifies the tunnel request identifier. Carrying in the label route corresponding to the service, and then enabling the edge device receiving the label route to select a required tunnel for the VPN service according to the tunnel requirement. Therefore, the method provided by the embodiment of the present invention enables different services to be carried in different domains in different domains, and the tunnel can be dynamically mapped between different domains to ensure that after the service enters the corresponding domain, Hosted on the correct tunnel. Therefore, different services can flexibly select tunnels, which greatly improves the bandwidth utilization of the network link.
  • VPN virtual private network
  • FIG. 1 is a schematic diagram of a network structure in which a whole network adopts a Seamless MPLS solution to carry services in the prior art
  • FIG. 2 is a schematic flowchart of a method for establishing a service tunnel according to Embodiment 1 of the present invention
  • Embodiment 3 is a network topology diagram applicable to the solution provided by Embodiment 2 and Embodiment 3 of the present invention
  • FIG. 4 is a schematic flowchart of a method for establishing a service tunnel according to Embodiment 2 of the present invention.
  • FIG. 5 is a schematic flowchart of a method for establishing a service tunnel according to Embodiment 3 of the present invention.
  • Embodiment 6 is a network topology diagram applicable to a solution provided by Embodiment 4 and Embodiment 5 of the present invention
  • FIG. 7 is a schematic flowchart of a method for establishing a service tunnel according to Embodiment 4 of the present invention.
  • FIG. 8 is a schematic flowchart of a method for establishing a service tunnel according to Embodiment 5 of the present invention.
  • FIG. 9 is a schematic flowchart of a method for establishing a service tunnel according to Embodiment 6 of the present invention.
  • FIG. 10 is a schematic structural diagram of an edge device according to Embodiment 7 of the present invention.
  • FIG. 11 is a schematic structural diagram of an edge device according to Embodiment 8 of the present invention.
  • FIG. 12 is a schematic structural diagram of a service tunnel establishing apparatus according to Embodiment 8 of the present invention.
  • the present invention provides a service tunnel establishment method, including:
  • the destination edge device that receives the label route corresponding to the VPN service is received.
  • the destination edge device uses the obtained tunnel request identifier to match the tunnel already established in the area to which the tunnel belongs, and if the matching result of the tunnel request identifier and any one of the established tunnels satisfies a preset condition, the target edge device selects The any tunnel carries the VPN service.
  • the edge device that initiates the VPN service allocates a corresponding tunnel request identifier to different services for the service, and carries the tunnel request identifier in the label route corresponding to the service. Then, the edge device that receives the label routing can enable the tunnel to be selected for the VPN service according to the tunnel request identifier. Therefore, the method provided by the embodiment of the present invention enables different services to be carried in different domains in different domains, and the tunnel can be dynamically mapped between different domains to ensure that after the service enters the corresponding domain, Can be carried on the correct tunnel. Therefore, different services can flexibly select tunnels, which greatly improves the bandwidth utilization of the network link.
  • an embodiment of the present invention provides a method for establishing a service tunnel, where the method specifically includes the following steps:
  • Step 201 When a first edge device of the first area needs to open a virtual private network VPN service between the at least one intermediate area and the second edge device of the second area, receiving a label route corresponding to the VPN service.
  • the destination edge device obtains a tunnel request identifier corresponding to the VPN service from the label route.
  • the edge device (which may be a UPE) that initiates the VPN service is configured for different services
  • different label routes are allocated to different VPN services, so that the edge device receiving the label route can be configured according to the foregoing. Label routing to select a tunnel that meets the needs of each VPN service to carry each VPN service.
  • the area is an independent network management subset, and specifically refers to an area formed by a combination of a set number and a network coverage area of a network device at a specific location.
  • a first service provider core network edge device NPE-1
  • NPE-2 second service provider core network edge device
  • Zone 2 consists of NPE-1, NPE-2, NPE-3 and NPE-4
  • the third zone is formed by NPE-3, NPE-4 and UPE-2.
  • the edge device mentioned in the embodiment of the present invention refers to a device that provides services for two regions at the same time. Among them, each area has an independent network topology database and network topology map of the area. For each region, its network topology is invisible outside the region. Similarly, the routers in each region are not aware of the rest of the network structure outside the domain.
  • Step 202 The destination edge device uses the obtained tunnel request identifier to match the tunnel that has been established in the area to which the tunnel belongs, and if the matching result of the tunnel request identifier and any of the established tunnels meets the preset condition, And selecting any of the tunnels to carry the VPN service.
  • the second edge device when the second edge device receives the label route, the second edge device may determine the complete path of the first edge device to the second edge device by using the edge device that the label is routed through. So when the edge device is the second edge device, the second edge device also needs Determining a complete service tunnel of the first edge device to the second edge device according to the received label route, so the method includes:
  • the second edge device obtains a transit tunnel from the label route, and iteratively forms the transit tunnel to form a complete service tunnel of the first edge device to the second edge device, where the transit tunnel is the The tunnel selected by other edge devices carried in the label route.
  • the second edge device needs to establish a corresponding relationship between the established service tunnel and the corresponding VPN service, after the first edge device establishes a service tunnel with the second device, and needs to use the established service tunnel to carry the corresponding VPN service. Therefore, the second edge device determines the tunnel of the first edge device to the second edge device according to the label route, and further includes:
  • the tunnel request identifier is matched with the tunnel request identifier corresponding to the established tunnel. If the tunnel request identifier is the same as the tunnel request identifier corresponding to any tunnel, the VPN service is sent by using the tunnel determined by the matching.
  • the specific requirements of the tunnel request identifier may be implemented in multiple manners.
  • the following provides several optional manners for detailed description, specifically:
  • the edge device needs to determine that the tunnel request identifier corresponds to itself according to a certain algorithm.
  • the established tunnel so after the edge device receives the label route, it uses the obtained tunnel request identifier to match the established tunnel in the area to which it belongs:
  • the destination edge device performs an operation result on the tunnel request identifier and the identifier of the tunnel that has been established by using the preset algorithm, and determines an established tunnel that needs to carry the VPN service according to the operation result.
  • the tunnel requirement identifier corresponds to a tunnel identifier that the VPN service wants to carry.
  • the specific implementation manner in which the edge device matches the calculation result with the identifier of the tunnel that has been established by the edge device may be: the tunnel request The identifier is a service affinity attribute, and the determining, according to the operation result, the established tunnel that needs to carry the VPN service includes: matching the calculation result with a tunnel management attribute stored by the destination edge device, and matching according to the As a result, an established tunnel that needs to carry the VPN service is determined.
  • the service affinity attribute is calculated by using RFC3209, and then the calculation result is used to match the tunnel management group.
  • the tunnel selection method provided by the embodiment of the present invention is further described, wherein the tunnel used in each domain may be a TE LSP, and the first node of the three segments of the TELSP in the respective AREA in the following figure They are UPE-1, NPE-1, and NPE-3.
  • VPN route is released: UPE-2 ⁇ UPE-1.
  • the NPE acts as the route reflector (RR) of the adjacent UPE.
  • the NPEs are mutually RR and the client. Therefore, the VPN route can be reflected from the remote UPE through multiple RRs to reach the local UPE.
  • the UPE-2 VPN route can reach UPE-1.
  • the method for setting up a BGP LSP and selecting each tunnel in the VPN1 between UPE-2 and UPE-1 includes (as shown in Figure 4):
  • step 401 the UPE-2 configures the service affinity attribute X1 for the instance where the VPN1 is located, and the UPE-2 advertises the BGP label route carrying the service affinity attribute X1 to the NPE-3.
  • Step 402 The NPE-3 receives the BGP label route advertised by the UPE-2, and matches the tunnel management attribute of the TE tunnel on the device according to the affinity attribute carried in the label route to further find the corresponding TE LSP: tunnel 3 -1;
  • Step 403 NPE-3 modifies the next hop in the BGP label route to NPE-3, and does not change the original service affinity attribute, and sends it to NPE-1.
  • Step 404 The NPE-1 receives the BGP label route advertised by the NPE-3, and matches the tunnel management attribute of the TE tunnel on the device according to the affinity attribute carried in the label route to further find the corresponding TE LSP: tunnel 2 -1;
  • Step 405 NPE-1 modifies the next hop in the BGP label route to NPE-1, and does not change the original service affinity attribute, and sends it to UPE-1.
  • Step 406 The UPE-1 receives the BGP label route advertised by the NPE-1, and matches the tunnel management attribute of the TE tunnel on the device according to the affinity attribute carried in the label route to further find the corresponding TE LSP: tunnel 1 -1;
  • a BGP LSP for example, BGP LSP1
  • BGP LSP1 for example, BGP LSP1
  • step 407 the instance where the VPN1 is located advertises the VPN route from the UPE-2 to the UPE-1.
  • the VPN route also carries the affinity attribute X1 and iterates to the BGP LSP1 in the UPE-1.
  • a specific implementation manner for carrying a Service Affinity Property Attribute in the label routing may be implemented in the following manner.
  • the newly added BGP attribute is used to indicate the service affinity attribute of the VPN service.
  • the service affinity attribute is an optional transition attribute, and the meanings of the three fields in the attribute Value are consistent with RFC3209, but the length is not limited.
  • This attribute can be sent along with BGP label routing and VPN routing. It can be used in various scenarios where BGP routes are required to carry this attribute.
  • the LDP mapping message includes many types/lengths/values (Type/Length/Value, TLV for short):
  • the Service Affinity Property TLV is advertised along with the LDP Mapping message and carries the service affinity attribute.
  • the LDP extension of the solution of the embodiment of the present invention is designed with the service affinity attribute TLV, which is used for the service affinity attribute (Service Affinity Property) of the L2VPN service setting, and its specific format is as follows. under:
  • the U-bit of the TLV is set to 1. When the TLV is received but cannot be recognized, it is ignored.
  • the F-bit of this TLV is set to 1, and this bit is only used when the U-bit is set to 1. Setting to 1 means that the TLV is received, even if it is not recognized, the TLV is forwarded forward.
  • the following takes the network structure provided in FIG. 1 as an example.
  • the specific implementation of the method for implementing tunnel selection by using the service affinity attribute and the management group attribute matching in the embodiment of the present invention may be:
  • the affinity attribute can be set to the following format: service affinity property properties[mask mask-value];
  • the corresponding matching attribute needs to be added in the edge device management group attribute of the receiving label route, and the matching attribute can be set as: tunnel administrative group[value ].
  • VPN1 is enabled between UPE-2 and UPE-1, and UPE-2 is configured with the service affinity attribute X1 for the instance of VPN1. If X1 is specifically configured as: service affinity Property 10011 mask 11101;
  • the management group identifier of tunnel 3-1 is 10010, and the management group of tunnel 3-2 is 10101.
  • the specific process of the NPE-3 selecting a tunnel according to X1 may be:
  • the overall matching rule is: the bit in the result of the administrative group&mask is 1 and the corresponding bit in the Affinity&mask result is also 1, which is considered to be a match.
  • NPE-3 receives the BGP label route carrying affinity attribute from UPE-2 and calculates it on NPE-3:
  • the PW1 service is enabled between UPE-2 and UPE-1 to trigger the establishment of a BGP LSP and select the processing flow of each tunnel (as shown in Figure 5):
  • the UPE-2 configures the service affinity attribute X6 for the instance where the PW1 is located, and the UPE-2 advertises the BGP label route carrying the service affinity attribute X6 to the NPE-3.
  • Step 502 The NPE-3 receives the BGP label route advertised by the UPE-2, and matches the tunnel management attribute of the TE tunnel on the device according to the affinity attribute carried in the label route to further find the corresponding TE LSP: tunnel 3 -3;
  • Step 503 NPE-3 modifies the next hop in the BGP label route to NPE-3, and does not change the original service affinity attribute, and sends it to NPE-1.
  • Step 504 The NPE-1 receives the BGP label route advertised by the NPE-3, and matches the tunnel management attribute of the TE tunnel on the device according to the affinity attribute carried in the label route to further find the corresponding TE LSP: Tunnel 2 -2;
  • Step 505 NPE-1 modifies the next hop in the BGP label route to NPE-1, and does not change the original service affinity attribute, and sends it to UPE-1.
  • Step 506 The UPE-1 receives the BGP label route advertised by the NPE-1, and matches the tunnel management attribute on the TE tunnel on the device according to the affinity attribute carried in the label route, and further searches for Go to the corresponding TE LSP: Tunnel 1-6; to this step, establish a BGP LSP from UPE-1 to UPE-2 (for example, BGP LSP6), and iterate from left to right to tunnel 1-6 and tunnel 2-2. Tunnel 3-3;
  • step 507 the instance of the PW1 is advertised from the UPE-2 to the UPE-1, and the message carries the service affinity attribute TLV.
  • the UPE-1 matches the corresponding BGP LSP according to the service affinity attribute, matches and iterates to BGP LSP6.
  • the TE LSP is used in each domain.
  • the first nodes of the three TE LSPs in the respective AREAs are UPE-1, NPE-1, and NPE-3.
  • BGP label route advertisement direction UPE-2 ⁇ NPE-3 ⁇ NPE-1 ⁇ UPE-1 (also can be UPE-2 ⁇ NPE-4 ⁇ NPE-2 ⁇ UPE-1).
  • VPN route is released: UPE-2 ⁇ UPE-1.
  • the NPE acts as the RR of the neighboring UPE (the route reflector).
  • the NPEs are the relationship between the RR and the client. Therefore, the VPN route can be reflected from the remote UPE through multiple RRs to reach the local UPE.
  • the UPE-2 VPN route can reach UPE-1.
  • the process of establishing a BGP LSP and selecting each tunnel in the VPN between UPE-2 and UPE-1 includes (as shown in Figure 7):
  • the UPE-2 configures a preferred tunnel request identifier list for the instance where the VPN1 is located, and the id: 1 is in the list, and the UPE-2 advertises the BGP label route carrying the service preference identifier attribute to the NPE-3.
  • Step 702 The NPE-3 receives the BGP label route advertised by the UPE-2, matches the tunnel management identifier of the device according to the service preference identifier attribute carried in the label route, and finds the corresponding TELSP: tunnel 3-1 (tunnel 3) -1 is configured with management id: 1 ⁇ 2);
  • the NPE-3 After receiving the BGP label route, the NPE-3 detects that the service preference identifier attribute in the label route is id:1, and the tunnel ID 3-1 in the tunnel established by the NPE-3 is configured with the management ID: 1 to 2. So id:1 matches tunnel 3-1;
  • Step 703 NPE-3 modifies the next hop of the BGP label route to NPE-3, and does not change the original The service preference identifier attribute is sent to NPE-1.
  • Step 704 The NPE-1 receives the BGP label route advertised by the NPE-3, matches the tunnel management identifier of the device according to the service preference identifier attribute carried in the label route, and finds the corresponding TELSP: tunnel 2-1 (tunnel 2) -1 is configured with management ID: 1 to 4);
  • Step 705 NPE-1 modifies the next hop in the BGP label route to NPE-1, and does not change the original service preference identifier attribute, and sends it to UPE-1.
  • the UPE-1 receives the BGP label route advertised by the NPE-1, and matches the tunnel management identifier of the device according to the service preference identifier attribute carried in the label route, and further finds the corresponding TE LSP: tunnel 1-1 (
  • the tunnel ID 1-1 is configured with the management ID: 1); to this step, the BGP LSPs of the UPE-1 to UPE-2 (for example, BGP LSP1) are established, and the TE LSPs are tunneled from left to right: tunnel 1-1.
  • Step 707 The instance where the VPN1 is located advertises the VPN route from the UPE-2 to the UPE-1, and the VPN route also carries the service preference identifier attribute, and matches the service preference identifier attribute of the BGP LSP according to the attribute, and matches on the UPE-1. Iterate to BGP LSP1.
  • the process of establishing a BGP LSP and selecting each tunnel in the PW service between UPE-2 and UPE-1 includes: (As shown in Figure 8):
  • Step 801 UPE-2 configures a preferred tunnel request identifier list for the instance where the PW1 is located, and the id:6 is in the list, and the UPE-2 advertises the BGP label route carrying the service preference identifier attribute to the NPE-3.
  • Step 802 The NPE-3 receives the BGP label route advertised by the UPE-2, matches the tunnel management identifier of the device according to the service preference identifier attribute carried in the label route, and finds the corresponding TELSP: tunnel 3-3 (tunnel 3) -3 is configured with management ID: 5 ⁇ 6);
  • the UPE-2 modifies the next hop of the BGP label route to the NPE-3, and does not change the original service preference identifier attribute to the NPE-1.
  • the NPE-1 receives the BGP label route advertised by the NPE-3, matches the tunnel management identifier of the device according to the service preference identifier attribute carried in the label route, and finds the corresponding TELSP: tunnel 2-2 (tunnel 2) -2 is configured with management ID: 5 ⁇ 8);
  • Step 805 NPE-1 modifies the next hop in the BGP label route to NPE-1, and does not change the original service preference identifier attribute, and sends it to UPE-1.
  • the UPE-1 receives the BGP label route advertised by the NPE-1, and matches the tunnel management identifier of the device according to the service preference identifier attribute carried in the label route, and further finds the corresponding TE LSP: tunnel 1-6 ( Tunnel 1-6 is configured with the management ID: 6); at this step, the BGP LSPs of the UPE-1 to UPE-2 (for example, BGP LSP6) are established, and iteratively transitions from left to right to the TE LSP: tunnels 1-6, Tunnel 2-2, tunnel 3-3;
  • Step 807 The instance in which the PW1 is located advertises the LDP mapping message from the UPE-2 to the UPE-1, and the message also carries the service preference identifier TLV, and matches the identifier in the TLV and the service preference identifier attribute of the BGP LSP, in the UPE- Match 1 and iterate to BGP LSP6.
  • the embodiment of the present invention further provides another method for establishing a service tunnel, where the method includes:
  • Step 901 When the first edge device of the first area needs to open a virtual private network VPN service between the at least one intermediate area and the second edge device of the second area, the first edge device and the VPN service The corresponding tunnel request identifier is added to the label route corresponding to the VPN service;
  • Step 902 Forward the label route, so that the edge device that receives the label route obtains the tunnel request identifier from the label route, and the edge device that receives the label route uses the tunnel request identifier to match If the matching result of the tunnel request identifier and any one of the established tunnels meets a preset condition, the tunnel is selected to carry the VPN service.
  • the method provided by the first embodiment of the present invention further provides an edge device 1000, the edge device comprising:
  • the obtaining unit 1001 is configured to receive a virtual private network VPN service when the first edge device of the first area needs to open a virtual private network VPN service between the at least one intermediate area and the second edge device of the second area. a label route corresponding to the VPN service, and obtaining a tunnel request identifier corresponding to the VPN service from the label route;
  • the tunnel selection unit 1002 is configured to use the acquired tunnel request identifier to match the tunnel that has been established in the area to which the tunnel belongs, and if the matching result of the tunnel request identifier and any one of the established tunnels meets a preset condition, Then, the any tunnel is selected to carry the VPN service.
  • the solution provided by the present invention uses the acquired tunnel request identifier to match the tunnel already established in the area to which the user belongs:
  • the tunnel selection unit 1002 is further configured to perform an operation result on the tunnel request identifier and the identifier of the tunnel that has been established by using a preset algorithm, and determine, according to the operation result, that the VPN service needs to be carried. Tunnel.
  • the tunnel requirement identifier may be a plurality of implementation manners, where the main one may be a service affinity attribute, and the calculation result is matched with the identifier of the tunnel that has been established by itself: the tunnel selection unit 1002 is further used to: The calculation result is matched with the tunnel management attribute stored in the self, and the established tunnel that needs to carry the VPN service is determined according to the matching result.
  • the label routing is forwarded to the destination edge device via the edge devices of the multiple intermediate areas, and the intermediate area is
  • the main task of the edge device is to select the tunnel that carries the VPN service according to the tunnel requirement identifier, and then forward the label route.
  • the destination edge device that establishes the VPN service after the label route is received, the path of the label route forwarding needs to be iterated to form a complete bearer tunnel; and the relationship between the tunnel and the corresponding VPN service is also required to be established.
  • the edge device that receives the label route is the destination edge device (the second edge device in this embodiment)
  • the edge device provided by the embodiment further includes:
  • the edge device needs to iterate the path through which the label route is forwarded to form a complete tunnel that carries the VPN service, where the device includes:
  • a tunnel iteration unit configured to obtain a transit tunnel from the label route, and the transit tunnel The iteratively forms a complete service tunnel of the first edge device to the second edge device, where the transit tunnel is a tunnel selected by other edge devices carried in the label route.
  • the edge device further includes:
  • a service matching unit configured to acquire the tunnel request identifier from the VPN service route when receiving the VPN service route sent by the first edge device, and use the tunnel request identifier to identify a tunnel request corresponding to the established tunnel The identifier is matched. If the tunnel request identifier is the same as the tunnel request identifier corresponding to any tunnel, the VPN service is sent by using the tunnel determined by the matching.
  • the embodiment of the present invention further provides another edge device 1100, where the edge device is a first edge device of a first area, where when the first edge device crosses When the virtual private network VPN service needs to be opened between the at least one intermediate area and the second edge device of the second area, the first edge device 1100 includes:
  • the identifier adding unit 1101 adds a tunnel request identifier corresponding to the VPN service to the label route corresponding to the VPN service;
  • the forwarding unit 1102 is configured to forward the label route, so that the edge device that receives the label route obtains the tunnel request identifier from the label route, and the edge device that receives the label route uses the tunnel
  • the identifier is required to match the tunnel that has been established in the area to which the tunnel belongs. If the matching result of the tunnel request identifier and any of the established tunnels meets a preset condition, the tunnel is selected to carry the VPN service. .
  • the present invention further provides a service tunnel establishing apparatus 120, which is configured to perform the service tunnel establishing method in the foregoing various embodiments, where the service tunnel establishing apparatus includes at least one processor 1201 (for example, a CPU), at least one Network interface 1202 or other communication interface, memory 1203, and at least one communication bus 1204 are used to effect connection communication between these devices.
  • the processor 1201 is configured to execute an executable module, such as a computer program, stored in the memory 1203.
  • the memory 1203 may include a high speed random access memory (RAM), and may also include a non-volatile memory such as at least one disk memory.
  • Pass The communication connection between the system gateway and at least one other network element may be implemented through at least one network interface 1202 (which may be wired or wireless), and may use an Internet, a wide area network, a local network, a metropolitan area network, or the like.
  • the memory stores a program 12031, the program being executable by the processor, the program comprising: opening between the first edge device of the first region and the second edge device of the second region
  • the program comprising: opening between the first edge device of the first region and the second edge device of the second region
  • the label route corresponding to the VPN service is received, and the tunnel request identifier corresponding to the VPN service is obtained from the label route; and the obtained tunnel request identifier is used to match the area to which the VPN service belongs. If the matching result of the tunnel request identifier and any one of the established tunnels meets a preset condition, the tunnel is selected to carry the VPN service.
  • the edge device that initiates the VPN service allocates a corresponding tunnel request identifier to different services for the service, and carries the tunnel request identifier in the label route corresponding to the service. Then, the edge device that receives the label routing can enable the tunnel to be selected for the VPN service according to the tunnel request identifier. Therefore, the method provided by the embodiment of the present invention enables different services to be carried in different domains in different domains, and the tunnel can be dynamically mapped between different domains to ensure that after the service enters the corresponding domain, Can be carried on the correct tunnel. Therefore, different services can flexibly select tunnels, which greatly improves the bandwidth utilization of the network link.
  • the user can plan to establish different tunnels according to the situation of different domains, and the mapping between the tunnels can be dynamically completed, and the operation and maintenance is simple.
  • the client to explicitly and end-to-end plan the correspondence between the service instance and the tunnel.

Landscapes

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

Abstract

本发明公开了一种业务隧道建立方法及设备，本发明公开的方法包括当第一区域的第一边缘设备跨至少一个中间区域与第二区域的第二边缘设备之间需要开通一虚拟专用网VPN业务时，接收到与所述VPN业务对应的标签路由的目的边缘设备从所述标签路由中获取与所述VPN业务对应的隧道要求标识；所述目的边缘设备利用获取到的隧道要求标识匹配自身所属区域中已经建立的隧道，如果所述隧道要求标识与所述已建立的隧道中的任一隧道的匹配结果满足预设条件，则选择所述任一隧道承载所述VPN业务。本发明实施例所提供的方案，使得不同的业务在不同的域可以选用不同或相同的隧道来承载，保证在业务进入对应的域后，可以承载在正确的隧道上。

Description

一种业务隧道建立方法及设备
本申请要求于2014年4月4日提交中国专利局、申请号为CN201410136102.6、发明名称为“一种业务隧道建立方法及设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明涉及网络技术领域，尤其涉及一种业务隧道建立方法及设备。
背景技术
各种功能强大的移动终端设备的出现，使得数据业务逐渐成为移动网的主要业务类型，同时空口技术也不断发展，带宽也越来越宽，这就出现了很多大数据量应用的增长：音乐、视频、游戏以及社交网络等。这些应用驱动了数据流量的巨大增长。在2G/3G的时候通常使用同步数字体系(Synchronous Digital Hierarchy，SDH)承载移动业务，但是SDH的架构无法支持规模和流量带宽的增长的需求。移动承载采用IP和以太技术才能既满足流量增长的需求，同时降低运营商的建网成本。全网跑IP协议(ALL IP)已经成为业界公认的趋势，在长期演进(Long Term Evolution，LTE)时代，无线网络架构发生了很大的改变，把演进的分组核心网(Evolved Packet Core，EPC)放到了很高的位置，一个EPC域可以管理很多基站，这样连接基站的基站侧网关(Cell Site Gateway，CSG)设备和连接EPC的服务提供商边缘设备(Provider Edge，PE)就不定在一个Area(区域)或AS(自治系统)内，但基站与EPC之间需要建立S1业务连接，承载网如何能更好的承载LTE S1业务，业界目前认为无缝多协议标签交换(Seamless Multiprotocol Label Switch，Seamless MPLS)方案是一个比较优化的承载方案。
同时，随着移动承载网络带宽的急剧增长和IP化承载，很多运营商为了节省建网成本，将固定业务和移动业务采用同一张IP网络来承载，这使得IP承载网络的业务也越来越复杂，种类越来越多，业务的接入点也越来越灵活， 这样对IP承载网也提出更高的要求。业界目前普通认可的承载方案就是Seamless MPLS方案，这种方案业务与传输隧道层解耦，业务只需要在接入点进行配置，运维比较简单。但当前的Seamless MPLS解决方案还存在一些问题，不能满足运营商的需求，如下需求就是一个典型的需求：
如图1所示，全网采用Seamless MPLS解决方案来承载，UPE-1和UPE-2之间有多种业务要承载，为了能充分利用网络的链路带宽，在用户侧PE(User-end Provider Edge，UPE)和网络侧PE(Network Provider Edge，NPE)之间建立很多条隧道，希望不同的业务能承载在不同的隧道，并且在不同域建立的隧道数量不同，所以需要隧道能互相映射，针对图1所示的网络结构，则UPE-1和UPE-2之间建立的隧道，可以是以下各种情况：
隧道1-1-------隧道2-1-----隧道3-1
隧道1-2-------隧道2-1-----隧道3-1
隧道1-3-------隧道2-1-----隧道3-2
隧道1-4-------隧道2-1-----隧道3-2
隧道1-5-------隧道2-2-----隧道3-3
隧道1-6-------隧道2-2-----隧道3-3
隧道1-7-------隧道2-2-----隧道3-4
隧道1-8-------隧道2-2-----隧道3-4
针对上述各种隧道形成需求，当前的Seamless MPLS提供的解决方案如下：
UPE-2向UPE-1发布一条边界网关协议(Border Gateway Protocol，BGP)标签路由，UPE-1与UPE-2之间建立一条到达UPE-2的端到端边界网关协议标签交换路径(End-to-End Border gateway protocol Label Switched Path，E2E BGP LSP)，同理，UPE-1也向UPE-2发一条BGP标签路由，UPE-2与UPE-1之间建立一条到达UPE-1的BGP LSP，所有的业务都迭代在建立的BGP LSP上，然后BGP LSP再承载在三条分段的隧道上，实现业务的端到端承载。
但是上述现有技术提供的方案，对于同一条标签路由，比如 UPE-1(1.1.1.1)，只能建立一条BGP LSP。很显然，一条BGP LSP就在一个域内，就只能承载在一条隧道上，因此所有的业务在一个域内就只能选择一条隧道来承载，无法实现不同的业务采用不同的隧道来承载。
发明内容
本发明提供一种业务隧道建立方法及设备，本发明所提供的方法和装置解决现有技术中所有的业务在一个域内就只能选择一条隧道来承载，无法实现不同的业务采用不同的隧道来承载的问题。
第一方面，本发明提供一种业务隧道建立方法，该方法包括：
当第一区域的第一边缘设备跨至少一个中间区域与第二区域的第二边缘设备之间需要开通一虚拟专用网VPN业务时，接收到与所述VPN业务对应的标签路由的目的边缘设备从所述标签路由中获取与所述VPN业务对应的隧道要求标识；
所述目的边缘设备利用获取到的隧道要求标识匹配自身所属区域中已经建立的隧道，如果所述隧道要求标识与所述已建立的隧道中的任一隧道的匹配结果满足预设条件，则选择所述任一隧道承载所述VPN业务。
结合第一方面，在第一种可能的实现方式中，所述目的边缘设备利用获取到的隧道要求标识匹配自身所属区域中已经建立的隧道包括：
所述目的边缘设备利用预设的算法对所述隧道要求标识和自身已建立的隧道的标识进行运算得到一运算结果，根据所述运算结果确定需要承载所述VPN业务的已经建立的隧道。
结合第一方面的第一种可能的实现方式，在第二种可能的实现方式中，所述隧道要求标识为业务亲和属性，则所述根据所述运算结果确定需要承载所述VPN业务的已经建立的隧道包括：将所述计算结果与所述目的边缘设备存储的隧道管理属性匹配，并根据匹配结果确定需要承载所述VPN业务的已经建立的隧道。
结合第一方面的第一种可能的实现方式，在第三种可能的实现方式中， 当所述目的边缘设备为第二边缘设备则该方法还包括：
所述第二边缘设备从所述标签路由中获取中转隧道，将所述中转隧道迭代形成所述第一边缘设备到所述第二边缘设备的完整业务隧道，其中，所述中转隧道是所述标签路由中携带的其他边缘设备选择的隧道。
结合第一方面的第三种可能的实现方式，在第四种可能的实现方式中，该方法还包括：
所述第二边缘设备接收到所述第一边缘设备发送的VPN业务路由时，从所述VPN业务路由中获取所述隧道要求标识；
利用所述隧道要求标识与已建立隧道对应的隧道要求标识进行匹配，如果与所述隧道要求标识与任一隧道对应的隧道要求标识相同，则利用匹配确定的隧道发送所述VPN业务。
第二方面，本发明还提供另外一种业务隧道建立方法，该方法包括：
当第一区域的第一边缘设备跨至少一个中间区域与第二区域的第二边缘设备之间需要开通一虚拟专用网VPN业务时，所述第一边缘设备将与所述VPN业务对应的隧道要求标识添加到所述VPN业务对应的标签路由中；
转发所述标签路由，使得接收到所述标签路由的边缘设备从所述标签路由中获取所述隧道要求标识，并使接收到所述标签路由的边缘设备利用所述隧道要求标识匹配自身所属区域中已经建立的隧道，如果所述隧道要求标识与所述已建立的隧道中的任一隧道的匹配结果满足预设条件，则选择所述任一隧道承载所述VPN业务。
第三方面，本发明提供一种边缘设备，该边缘设备包括：
获取单元，当第一区域的第一边缘设备跨至少一个中间区域与第二区域的第二边缘设备之间需要开通一虚拟专用网VPN业务时，用于接收到与所述VPN业务对应的标签路由，并从所述标签路由中获取与所述VPN业务对应的隧道要求标识；
隧道选择单元，用于利用获取到的隧道要求标识匹配自身所属区域中已经建立的隧道，如果所述隧道要求标识与所述已建立的隧道中的任一隧道的 匹配结果满足预设条件，则选择所述任一隧道承载所述VPN业务。
结合第二方面，在第一种可能的实现方式中，所述隧道选择单元还用于利用预设的算法对所述隧道要求标识和自身已建立的隧道的标识进行运算得到一运算结果，根据所述运算结果确定需要承载所述VPN业务的已经建立的隧道。
结合第二方面的第一种可能的实现方式，在第二种可能的实现方式中，所述隧道要求标识为业务亲和属性，所述隧道选择单元还用于将所述计算结果与自身存储的隧道管理属性匹配，并根据匹配结果确定需要承载所述VPN业务的已经建立的隧道。
结合第二方面的第一种可能的实现方式，在第三种可能的实现方式中，当所述边缘设备为第二边缘设备则该边缘设备还包括：
隧道迭代单元，用于从所述标签路由中获取中转隧道，将所述中转隧道迭代形成所述第一边缘设备到所述第二边缘设备的完整业务隧道，其中，所述中转隧道是所述标签路由中携带的其他边缘设备选择的隧道。
结合第二方面的第三种可能的实现方式，在第四种可能的实现方式中，该边缘设备还包括：
业务匹配单元，用于在接收到所述第一边缘设备发送的VPN业务路由时，从所述VPN业务路由中获取所述隧道要求标识；利用所述隧道要求标识与已建立隧道对应的隧道要求标识进行匹配，如果与所述隧道要求标识与任一隧道对应的隧道要求标识相同，则利用匹配确定的隧道发送所述VPN业务。
第四方面，本发明还提供另外一种边缘设备，所述边缘设备为第一区域的第一边缘设备，其中，当所述第一边缘设备跨至少一个中间区域与第二区域的第二边缘设备之间需要开通一虚拟专用网VPN业务时，所述第一边缘设备包括：
标识添加单元，用于将与所述VPN业务对应的隧道要求标识添加到所述VPN业务对应的标签路由中；
转发单元，用于转发所述标签路由，使得接收到所述标签路由的边缘设 备从所述标签路由中获取所述隧道要求标识，并使接收到所述标签路由的边缘设备利用所述隧道要求标识匹配自身所属区域中已经建立的隧道，如果所述隧道要求标识与所述已建立的隧道中的任一隧道的匹配结果满足预设条件，则选择所述任一隧道承载所述VPN业务。
上述技术方案中的一个或两个，至少具有如下技术效果：
本发明实施例提供的上述方法，发起虚拟专用网(Virtual Private Network，VPN)业务的边缘设备，针对不同业务对隧道的要求，给不同业务分配对应的隧道要求标识，并将所述隧道要求标识携带在业务对应的标签路由中，然后使得接收到所述标签路由的边缘设备能够根据所述隧道要求标识为所述VPN业务选择需要的隧道。所以本发明实施例所提供的方法，使得不同的业务在不同的域可以选用不同或相同的隧道来承载，隧道可以在不同的域之间动态进行映射，保证在业务进入对应的域后，可以承载在正确的隧道上。从而使得不同的业务可以灵活选择隧道，大大提升网络链路带宽利用率。
附图说明
图1为现有技术中全网采用Seamless MPLS解决方案来承载业务的网络结构示意图；
图2为本发明实施例一提供的一种业务隧道建立方法的流程示意图；
图3为本发明实施例二和实施例三所提供方案适用的网络拓扑图；
图4为本发明实施例二提供的一种业务隧道建立方法的流程示意图；
图5为本发明实施例三提供的一种业务隧道建立方法的流程示意图；
图6为本发明实施例四和实施例五所提供方案适用的网络拓扑图；
图7为本发明实施例四提供的一种业务隧道建立方法的流程示意图；
图8为本发明实施例五提供的一种业务隧道建立方法的流程示意图；
图9为本发明实施例六提供的一种业务隧道建立方法的流程示意图；
图10为本发明实施例七提供的一种边缘设备的结构示意图；
图11为本发明实施例八提供的一种边缘设备的结构示意图；
图12为本发明实施例八提供的一种业务隧道建立装置的结构示意图。
具体实施方式
为使本发明实施例的目的、技术方案和优点更加清楚，下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本发明一部分实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本发明保护的范围。
为了解决现有技术中的问题，本发明提供一种业务隧道建立方法，该方法包括：
当第一区域的第一边缘设备跨至少一个中间区域与第二区域的第二边缘设备之间需要开通一虚拟专用网VPN业务时，接收到与所述VPN业务对应的标签路由的目的边缘设备从所述标签路由中获取与所述VPN业务对应的隧道要求标识；
所述目的边缘设备利用获取到的隧道要求标识匹配自身所属区域中已经建立的隧道，如果所述隧道要求标识与所述已建立的隧道中的任一隧道的匹配结果满足预设条件，则选择所述任一隧道承载所述VPN业务。
本发明实施例提供的上述方法，发起VPN业务的边缘设备，针对不同业务对隧道的要求，给不同业务分配对应的隧道要求标识，并将所述隧道要求标识携带在业务对应的标签路由中，然后使得接收到所述标签路由的边缘设备能够根据所述隧道要求标识为所述VPN业务选择需要的隧道。所以本发明实施例所提供的方法，使得不同的业务在不同的域可以选用不同或相同的隧道来承载，同时隧道可以在不同的域之间动态进行映射，保证在业务进入对应的域后，可以承载在正确的隧道上。从而使得不同的业务可以灵活选择隧道，大大提升网络链路带宽利用率。
为了更清楚详细的说明本发明实施例所提供的方法，以下结合说明书附图对本发明实施例所提供的方法做进一步详细的说明，具体包括：
实施例一
如图2所示，本发明实施例提供一种业务隧道建立方法，该方法具体包括步骤：
步骤201，当第一区域的第一边缘设备跨至少一个中间区域与第二区域的第二边缘设备之间需要开通一虚拟专用网VPN业务时，接收到与所述VPN业务对应的标签路由的目的边缘设备从所述标签路由中获取与所述VPN业务对应的隧道要求标识；
在本发明实施例中，当发起VPN业务的边缘设备(可以是UPE)针对不同业务的特点，给不同的VPN业务分配不同的标签路由，使得接收到所述标签路由的边缘设备能够根据所述标签路由去选择符合每个VPN业务的需求的隧道来承载每个VPN业务。
所述区域是一个独立的网络管理子集，具体是指设定数量及特定位置的网络设备的网络覆盖区域组合形成的区域。例如图3所示的网络结构中，第一服务提供商核心网络边缘设备(notework faceing provider edge，NPE，标识NPE-1)、第二服务提供商核心网络边缘设备(NPE-2)以及第一面向用户提供服务边缘设备(UPE-1)的网络覆盖区域组合形成的区域1。区域2由NPE-1、NPE-2、NPE-3和NPE-4组成，第3区域由NPE-3、NPE-4和UPE-2形成。在本发明实施例中所提到的边缘设备是指，同时为两个区域提供服务的设备。其中，每一个区域都有着该区域独立的网络拓扑数据库及网络拓扑图。对于每一个区域，其网络拓扑结构在区域外是不可见的，同样，在每一个区域中的路由器对其域外其余网络结构也不可知。
步骤202，所述目的边缘设备利用获取到的隧道要求标识匹配自身所属区域中已经建立的隧道，如果所述隧道要求标识与所述已建立的隧道中的任一隧道的匹配结果满足预设条件，则选择所述任一隧道承载所述VPN业务。
在本发明实施例中，当第二边缘设备接收到所述标签路由，第二边缘设备就可以通过标签路由经过的边缘设备确定出第一边缘设备到第二边缘设备的完整路径了。所以当所述边缘设备为第二边缘设备，第二边缘设备还需要 根据接收到的标签路由确定第一边缘设备到第二边缘设备的完整业务隧道，所以该方法包括：
所述第二边缘设备从所述标签路由中获取中转隧道，将所述中转隧道迭代形成所述第一边缘设备到所述第二边缘设备的完整业务隧道，其中，所述中转隧道是所述标签路由中携带的其他边缘设备选择的隧道。
进一步，因为第一边缘设备与第二设备建立业务隧道之后，需要利用建立的业务隧道承载对应的VPN业务，所以第二边缘设备还需要将建立的业务隧道与对应的VPN业务建立对应的关系，所以第二边缘设备根据标签路由确定第一边缘设备到第二边缘设备的隧道，还包括：
所述第二边缘设备接收到所述第一边缘设备发送的VPN业务路由时，从所述VPN业务路由中获取所述隧道要求标识；
利用所述隧道要求标识与已建立隧道对应的隧道要求标识进行匹配，如果与所述隧道要求标识与任一隧道对应的隧道要求标识相同，则利用匹配确定的隧道发送所述VPN业务。
在本发明实例中，所述隧道要求标识的具体可以是通过多种方式实现的，以下提供几种可选的方式进行详细的说明，具体为：
首先，因为不同边缘设备可能采用不同的标识来区分不同条件的隧道，所以一般情况下边缘设备获取到标签路由中的隧道要求标识之后，需要根据一定的算法确定所述隧道要求标识对应的自身已建立的那个隧道，所以边缘设备接收到标签路由之后，利用获取到的隧道要求标识匹配自身所属区域中已经建立的隧道包括：
所述目的边缘设备利用预设的算法对所述隧道要求标识和自身已建立的隧道的标识进行运算得到一运算结果，根据所述运算结果确定需要承载所述VPN业务的已经建立的隧道。
其中，所述隧道要求标识与所述VPN业务希望承载的隧道标识对应。
方式一，当所述隧道要求标识为业务亲和属性，所述边缘设备将计算结果与自身已建立隧道的标识进行匹配的具体实现方式可以是：所述隧道要求 标识为业务亲和属性，则所述根据所述运算结果确定需要承载所述VPN业务的已经建立的隧道包括：将所述计算结果与所述目的边缘设备存储的隧道管理属性匹配，并根据匹配结果确定需要承载所述VPN业务的已经建立的隧道。其中，利用RFC3209计算所述业务亲和属性，然后利用计算结果去匹配隧道管理组。
根据图3所示的拓扑网络结构，对本发明实施例所提供的隧道选择方法作进一步的说明，其中各个域中使用的隧道可以是TE LSP，下图中3段TELSP在各自AREA中的首节点分别为UPE-1、NPE-1、NPE-3。
如果BGP标签路由发布方向：UPE-2→NPE-3→NPE-1→UPE-1(也可以是UPE-2→NPE-4→NPE-2→UPE-1)。
VPN路由发布：UPE-2→UPE-1。
针对VPN路由，NPE作为相邻UPE的路由反射器(Route Reflector，RR)，NPE之间又互为RR和Client的关系，所以VPN路由可以从远端UPE经多个RR反射到达本地UPE，即：如下场景中，UPE-2的VPN路由可以到达UPE-1。
实施例二
其中，在UPE-2与UPE-1之间开通VPN1触发建立BGP LSP并选择各段隧道的处理方法包括(如图4所示)：
步骤401，UPE-2为VPN1所在实例配置业务亲和属性X1，UPE-2向NPE-3发布携带业务亲和属性X1的BGP标签路由；
步骤402，NPE-3在接收到UPE-2发布的BGP标签路由，根据该标签路由携带的亲和属性去匹配该设备上的TE tunnel上的隧道管理属性，进一步找到对应的TE LSP：隧道3-1；
步骤403，NPE-3将BGP标签路由中的下一跳修改为NPE-3，不改原有的业务亲和属性，前发至NPE-1；
步骤404，NPE-1在接收到NPE-3发布的BGP标签路由，根据该标签路由携带的亲和属性去匹配该设备上的TE tunnel上的隧道管理属性，进一步找到对应的TE LSP：隧道2-1；
步骤405，NPE-1将BGP标签路由中的下一跳修改为NPE-1，不改原有的业务亲和属性，前发至UPE-1；
步骤406，UPE-1在接收到NPE-1发布的BGP标签路由，根据该标签路由携带的亲和属性去匹配该设备上的TE tunnel上的隧道管理属性，进一步找到对应的TE LSP：隧道1-1；到这一步，建立了UPE-1到UPE-2的BGP LSP(例如：BGP LSP1)，从左到右依次迭代到隧道1-1、隧道2-1、隧道3-1；
步骤407，VPN1所在的实例从UPE-2发布VPN route到UPE-1，该VPN route也携带亲和属性X1，在UPE-1迭代到BGP LSP1。
在该实施例中，为了在所述标签路由中携带业务亲和属性(Service Affinity Property Attribute)的具体实现方式可以通过以下方式实现，
a、新增一个BGP属性，新增的BGP属性用来标示VPN业务的业务亲和属性。
在该实施例中，业务亲和属性是一个可选过渡属性，属性Value中的3个字段的含义与RFC3209保持一致，但长度不做限定。该属性可以随同BGP标签路由和VPN路由一起发送。可用在需要BGP路由携带该属性的各种场景。
其中，业务亲和属性各字段的处理如下：
Include-any＝Affinity&Mask
Exclude-any＝(-Include-any)&Mask，即Include-any按Mask取反
Include-all＝0x0
b，新增一个LDP TLV：Service Affinity Property TLV(业务亲和属性TLV)：
LDP Mapping消息中包括很多不同用途的类型/长度/值(Type/Length/Value，简称：TLV)：
Service Affinity Property TLV，该TLV随同LDP Mapping消息一起发布，携带的内容是业务亲和属性。
本发明实施例方案的LDP扩展设计了所述业务亲和属性TLV，用于L2VPN业务设置的业务亲和属性(Service Affinity Property)，其具体格式如 下：
该TLV的U-bit设置为1，当收到该TLV，但无法识别时，忽略不处理。
该TLV的F-bit设置为1，该比特位仅在U-bit设置为1时使用。设置为1表示接收到该TLV、即使无法识别，也要向前转发该TLV。
上述业务亲和属性的设置及处理，只是本发明方案的一个特例，旨在说明本发明方案的可实施性，并不局限本发明只有这一实现途径。
下面以图1所提供的网络结构为例，对本发明实施例中利用业务亲和属性与管理组属性匹配实现隧道选择的方法具体实现可以是：
首先，在VPN标签路由的属性列表中添加亲和属性，亲和属性可以是设置成如下格式：service affinity property properties[mask mask-value]；
对应的要实现管理组属性与所述亲和属性的匹配，则对应的还需要在接收标签路由的边缘设备管理组属性中添加对应的匹配属性，该匹配属性可以设置为：tunnel administrative group[value]。
根据图3所示的拓扑网络结构，实施例二中，在UPE-2与UPE-1之间开通VPN1，UPE-2为VPN1所在实例配置业务亲和属性X1，如果X1具体配置为：service affinity property 10011 mask 11101；
在接收标签路由的NPE-3管理组属性中，隧道3-1的管理组标识为10010，另外，隧道3-2的管理组为10101。则NPE-3根据X1选择隧道的具体过程可以是：
总体的匹配规则是：administrative group&mask的结果中为1的位对应Affinity&mask结果中的对应位也为1，则认为匹配。
例如：
NPE-3从UPE-2接收到BGP标签路由携带亲和属性，在NPE-3上计算：
首先计算业务亲和属性：因为Affinity＝10011；MASK＝11101；则Affinity&mask＝10001；
其次计算可以匹配的隧道：
针对隧道3-2，administrative group＝10101，(mask为从UPE-2接收到 的：11101)；则对应的administrative group&mask＝10101&11101＝10101,在这个结果中第一、第三和四五位这三个位为1，所以根据规则，要求亲和属性三个位也要为1，但是亲和属性计算的结果为10001，只有两个位为1，所以这个隧道不匹配。
针对3-1，administrative group＝10010，(mask为从UPE-2接收到的：11101)；administrative group&mask＝10010&11101＝10000，所得的结果要求第一个位为1(从左到右数)，亲和属性计算的结果为10001，亲和属性能与管理组属性匹配，所以隧道3-1匹配。
上述是亲和属性的一种实现方式，但并不限定本发明实施例所提供的方法只能通过上述方式实现。
实施例三
在UPE-2与UPE-1之间开通PW1业务触发建立BGP LSP并选择各段隧道的处理流程(如图5所示)：
步骤501，UPE-2为PW1所在实例配置了业务亲和属性X6，UPE-2向NPE-3发布携带业务亲和属性X6的BGP标签路由；
步骤502，NPE-3在接收到UPE-2发布的BGP标签路由，根据该标签路由携带的亲和属性去匹配该设备上的TE tunnel上的隧道管理属性，进一步找到对应的TE LSP：隧道3-3；
步骤503，NPE-3将BGP标签路由中的下一跳修改为NPE-3，不改原有的业务亲和属性，前发至NPE-1；
步骤504，NPE-1在接收到NPE-3发布的BGP标签路由，根据该标签路由携带的亲和属性去匹配该设备上的TE tunnel上的隧道管理属性，进一步找到对应的TE LSP：隧道2-2；
步骤505，NPE-1将BGP标签路由中的下一跳修改为NPE-1，不改原有的业务亲和属性，前发至UPE-1；
步骤506，UPE-1在接收到NPE-1发布的BGP标签路由，根据该标签路由携带的亲和属性去匹配该设备上的TE tunnel上的隧道管理属性，进一步找 到对应的TE LSP：隧道1-6；到这一步，建立了UPE-1到UPE-2的BGP LSP(例如：BGP LSP6)，从左到右依次迭代到隧道1-6、隧道2-2、隧道3-3；
步骤507，PW1所在的实例从UPE-2发布Label Mapping消息到UPE-1，该消息携带业务亲和属性TLV，在UPE-1上根据业务亲和属性去匹配对应的BGP LSP，匹配并迭代到BGP LSP6。
方式二、当所述隧道要求标识为标识隧道的ID标识，则以下结合图6所示场景详细说明本发明实施例实现过程。
在各个域中使用的是TE LSP，下图中3段TE LSP在各自AREA中的首节点分别为UPE-1、NPE-1、NPE-3。
BGP标签路由发布方向：UPE-2→NPE-3→NPE-1→UPE-1(也可以是UPE-2→NPE-4→NPE-2→UPE-1)。
VPN路由发布：UPE-2→UPE-1。
针对VPN路由，NPE作为相邻UPE的RR(路由反射器)，NPE之间又互为RR和Client的关系，所以VPN路由可以从远端UPE经多个RR反射到达本地UPE，即：如下场景中，UPE-2的VPN路由可以到达UPE-1。
实施例四
其中，在UPE-2与UPE-1之间开通VPN触发建立BGP LSP并选择各段隧道的处理流程包括(如图7所示)：
步骤701，UPE-2为VPN1所在实例配置了优选的隧道要求标识列表，列表中有id：1，UPE-2向NPE-3发布携带业务优选标识属性的BGP标签路由；
步骤702，NPE-3在接收到UPE-2发布的BGP标签路由，根据该标签路由携带的业务优选标识属性去匹配该设备上的隧道管理标识，找到对应的TELSP：隧道3-1(隧道3-1配置了管理id：1～2)；
即，NPE-3在接收到BGP标签路由后，检测到标签路由中的业务优选标识属性为id：1，而且NPE-3已建立的隧道中隧道3-1配置了管理ID：1～2，所以id：1与隧道3-1匹配；
步骤703，NPE-3将BGP标签路由的下一跳修改为NPE-3，不改原有的 业务优选标识属性，前发至NPE-1；
步骤704，NPE-1在接收到NPE-3发布的BGP标签路由，根据该标签路由携带的业务优选标识属性去匹配该设备上的隧道管理标识，找到对应的TELSP：隧道2-1(隧道2-1配置了管理ID：1～4)；
步骤705，NPE-1将BGP标签路由中的下一跳修改为NPE-1，不改原有的业务优选标识属性，前发至UPE-1；
步骤706，UPE-1在接收到NPE-1发布的BGP标签路由，根据该标签路由携带的业务优选标识属性去匹配该设备上的隧道管理标识，进一步找到对应的TE LSP：隧道1-1(隧道1-1配置了管理ID：1)；到这一步，建立了UPE-1到UPE-2的BGP LSP(例如：BGP LSP1)，从左到右依次迭代到TE LSP：隧道1-1、隧道2-1、隧道3-1；
步骤707，VPN1所在的实例从UPE-2发布VPN route到UPE-1，该VPN route也携带业务优选标识属性，根据该属性和BGP LSP的业务优选标识属性进行匹配，在UPE-1上匹配并迭代到BGP LSP1。
实施例五
其中，在UPE-2与UPE-1之间开通PW业务触发建立BGP LSP并选择各段隧道的处理流程具体包括(如图8所示)：
步骤801，UPE-2为PW1所在实例配置了优选的隧道要求标识列表，列表中有id：6，UPE-2向NPE-3发布携带业务优选标识属性的BGP标签路由；
步骤802，NPE-3在接收到UPE-2发布的BGP标签路由，根据该标签路由携带的业务优选标识属性去匹配该设备上的隧道管理标识，找到对应的TELSP：隧道3-3(隧道3-3配置了管理ID：5～6)；
步骤803，UPE-2将BGP标签路由的下一跳修改为NPE-3，不改原有的业务优选标识属性，前发至NPE-1；
步骤804，NPE-1在接收到NPE-3发布的BGP标签路由，根据该标签路由携带的业务优选标识属性去匹配该设备上的隧道管理标识，找到对应的TELSP：隧道2-2(隧道2-2配置了管理ID：5～8)；
步骤805，NPE-1将BGP标签路由中的下一跳修改为NPE-1，不改原有的业务优选标识属性，前发至UPE-1；
步骤806，UPE-1在接收到NPE-1发布的BGP标签路由，根据该标签路由携带的业务优选标识属性去匹配该设备上的隧道管理标识，进一步找到对应的TE LSP：隧道1-6(隧道1-6配置了管理ID：6)；到这一步，建立了UPE-1到UPE-2的BGP LSP(例如：BGP LSP6)，从左到右依次迭代到TE LSP：隧道1-6、隧道2-2、隧道3-3；
步骤807，PW1所在的实例从UPE-2发布LDP Mapping消息到UPE-1，该消息同时也携带业务优选标识TLV，根据该TLV中的标识和BGP LSP的业务优选标识属性进行匹配，在UPE-1上匹配并迭代到BGP LSP6。
实施例六
如图9所示，本发明实施例还提供另外一种业务隧道建立方法，该方法包括：
步骤901，当第一区域的第一边缘设备跨至少一个中间区域与第二区域的第二边缘设备之间需要开通一虚拟专用网VPN业务时，所述第一边缘设备将与所述VPN业务对应的隧道要求标识添加到所述VPN业务对应的标签路由中；
步骤902，转发所述标签路由，使得接收到所述标签路由的边缘设备从所述标签路由中获取所述隧道要求标识，并使接收到所述标签路由的边缘设备利用所述隧道要求标识匹配自身所属区域中已经建立的隧道，如果所述隧道要求标识与所述已建立的隧道中的任一隧道的匹配结果满足预设条件，则选择所述任一隧道承载所述VPN业务。
实施例七
如图10所示，针对实施例一提供的方法本发明还提供一种边缘设备1000，该边缘设备包括：
获取单元1001，当第一区域的第一边缘设备跨至少一个中间区域与第二区域的第二边缘设备之间需要开通一虚拟专用网VPN业务时，用于接收到与 所述VPN业务对应的标签路由，并从所述标签路由中获取与所述VPN业务对应的隧道要求标识；
隧道选择单元1002，用于利用获取到的隧道要求标识匹配自身所属区域中已经建立的隧道，如果所述隧道要求标识与所述已建立的隧道中的任一隧道的匹配结果满足预设条件，则选择所述任一隧道承载所述VPN业务。
为了保证边缘设备能通过所述隧道要求标识找到VPN业务需要的隧道，所以本发明所提供的方案中，在利用获取到的隧道要求标识匹配自身所属区域中已经建立的隧道方面：
所述隧道选择单元1002还用于利用预设的算法对所述隧道要求标识和自身已建立的隧道的标识进行运算得到一运算结果，根据所述运算结果确定需要承载所述VPN业务的已经建立的隧道。
另外，所述隧道要求标识可以是多种实现方式，其中主要的可以是为业务亲和属性，所述将计算结果与自身已建立隧道的标识进行匹配方面：所述隧道选择单元1002还用于将所述计算结果与自身存储的隧道管理属性匹配，并根据匹配结果确定需要承载所述VPN业务的已经建立的隧道。
另外，在本发明实施例中，因为两个边缘设备是跨越多个中间区域实现VPN业务的开通，所以所述标签路由要经由多个中间区域的边缘设备才能转发到目的边缘设备，对于中间区域中的边缘设备主要的任务是根据隧道要求标识选择承载VPN业务的隧道，然后转发标签路由。但是对于建立VPN业务的目的边缘设备，则在接收到标签路由之后，则还需要将标签路由转发的路径迭代形成完整的承载隧道；并且还需要将隧道与对应的VPN业务建立对应的关系，使得发送VPN业务的时候能够在对应的隧道上进行发送。所以当接收到所述标签路由的边缘设备为目的边缘设备(在该实施例中为第二边缘设备)，则该实施例提供的边缘设备还包括：
首先，该边缘设备需要将标签路由转发经过的路径进行迭代形成一条完整的承载所述VPN业务的隧道，则该设备包括：
隧道迭代单元，用于从所述标签路由中获取中转隧道，将所述中转隧道 迭代形成所述第一边缘设备到所述第二边缘设备的完整业务隧道，其中，所述中转隧道是所述标签路由中携带的其他边缘设备选择的隧道。
其次，将需要承载的VPN业务与建立的隧道对应上，则该边缘设备就还包括：
业务匹配单元，用于在接收到所述第一边缘设备发送的VPN业务路由时，从所述VPN业务路由中获取所述隧道要求标识；利用所述隧道要求标识与已建立隧道对应的隧道要求标识进行匹配，如果与所述隧道要求标识与任一隧道对应的隧道要求标识相同，则利用匹配确定的隧道发送所述VPN业务。
实施例八
如图11所示，根据实施例六提供的方法本发明实施例还提供另外一种边缘设备1100，所述边缘设备为第一区域的第一边缘设备，其中，当所述第一边缘设备跨至少一个中间区域与第二区域的第二边缘设备之间需要开通一虚拟专用网VPN业务时，所述第一边缘设备1100包括：
标识添加单元1101，将与所述VPN业务对应的隧道要求标识添加到所述VPN业务对应的标签路由中；
转发单元1102，用于转发所述标签路由，使得接收到所述标签路由的边缘设备从所述标签路由中获取所述隧道要求标识，并使接收到所述标签路由的边缘设备利用所述隧道要求标识匹配自身所属区域中已经建立的隧道，如果所述隧道要求标识与所述已建立的隧道中的任一隧道的匹配结果满足预设条件，则选择所述任一隧道承载所述VPN业务。
如图12所示，本发明还提供一种业务隧道建立装置120，用于执行前述各个实施例中的业务隧道建立方法，该业务隧道建立装置包括至少一个处理器1201(例如CPU)，至少一个网络接口1202或者其他通信接口，存储器1203，和至少一个通信总线1204，用于实现这些装置之间的连接通信。处理器1201用于执行存储器1203中存储的可执行模块，例如计算机程序。存储器1203可能包含高速随机存取存储器(RAM：Random Access Memory)，也可能还包括非不稳定的存储器(non-volatile memory)，例如至少一个磁盘存储器。通 过至少一个网络接口1202(可以是有线或者无线)实现该系统网关与至少一个其他网元之间的通信连接，可以使用互联网，广域网，本地网，城域网等。
在一些实施方式中，存储器存储了程序12031，程序可以被处理器执行，这个程序包括：当第一区域的第一边缘设备跨至少一个中间区域与第二区域的第二边缘设备之间需要开通一虚拟专用网VPN业务时，接收到与所述VPN业务对应的标签路由，从所述标签路由中获取与所述VPN业务对应的隧道要求标识；利用获取到的隧道要求标识匹配自身所属区域中已经建立的隧道，如果所述隧道要求标识与所述已建立的隧道中的任一隧道的匹配结果满足预设条件，则选择所述任一隧道承载所述VPN业务。
本申请实施例中的上述一个或多个技术方案，至少具有如下的技术效果：
本发明实施例提供的上述方法，发起VPN业务的边缘设备，针对不同业务对隧道的要求，给不同业务分配对应的隧道要求标识，并将所述隧道要求标识携带在业务对应的标签路由中，然后使得接收到所述标签路由的边缘设备能够根据所述隧道要求标识为所述VPN业务选择需要的隧道。所以本发明实施例所提供的方法，使得不同的业务在不同的域可以选用不同或相同的隧道来承载，同时隧道可以在不同的域之间动态进行映射，保证在业务进入对应的域后，可以承载在正确的隧道上。从而使得不同的业务可以灵活选择隧道，大大提升网络链路带宽利用率。
另外通过本发明提供的方案，用户可以根据不同域的情况规划建立不同的隧道，隧道之间的映射可以动态完成，运维简单。
进一步，还便于客户显式地、端到端地规划业务实例与隧道的对应关系。
本发明所述的方法并不限于具体实施方式中所述的实施例，本领域技术人员根据本发明的技术方案得出其它的实施方式，同样属于本发明的技术创新范围。
显然，本领域的技术人员可以对本发明进行各种改动和变型而不脱离本发明的精神和范围。这样，倘若本发明的这些修改和变型属于本发明权利要求及其等同技术的范围之内，则本发明也意图包含这些改动和变型在内。

Claims (12)

  1. 一种业务隧道建立方法，其特征在于，该方法包括：
    当第一区域的第一边缘设备跨至少一个中间区域与第二区域的第二边缘设备之间需要开通一虚拟专用网VPN业务时，接收到与所述VPN业务对应的标签路由的目的边缘设备从所述标签路由中获取与所述VPN业务对应的隧道要求标识；
    所述目的边缘设备利用获取到的隧道要求标识匹配自身所属区域中已经建立的隧道，如果所述隧道要求标识与所述已建立的隧道中的任一隧道的匹配结果满足预设条件，则选择所述任一隧道承载所述VPN业务。
  2. 如权利要求1所述的方法，其特征在于，所述目的边缘设备利用获取到的隧道要求标识匹配自身所属区域中已经建立的隧道包括：
    所述目的边缘设备利用预设的算法对所述隧道要求标识和自身已建立的隧道的标识进行运算得到一运算结果，根据所述运算结果确定需要承载所述VPN业务的已经建立的隧道。
  3. 如权利要求2所述的方法，其特征在于，所述隧道要求标识为业务亲和属性，则所述根据所述运算结果确定需要承载所述VPN业务的已经建立的隧道包括：将所述计算结果与所述目的边缘设备存储的隧道管理属性匹配，并根据匹配结果确定需要承载所述VPN业务的已经建立的隧道。
  4. 如权利要求2所述的方法，其特征在于，当所述目的边缘设备为第二边缘设备则该方法还包括：
    所述第二边缘设备从所述标签路由中获取中转隧道，将所述中转隧道迭代形成所述第一边缘设备到所述第二边缘设备的完整业务隧道，其中，所述中转隧道是所述标签路由中携带的其他边缘设备选择的隧道。
  5. 如权利要求4所述的方法，其特征在于，该方法还包括：
    所述第二边缘设备接收到所述第一边缘设备发送的VPN业务路由时，从所述VPN业务路由中获取所述隧道要求标识；
    利用所述隧道要求标识与已建立隧道对应的隧道要求标识进行匹配，如果与所述隧道要求标识与任一隧道对应的隧道要求标识相同，则利用匹配确定的隧道发送所述VPN业务。
  6. 一种业务隧道建立方法，其特征在于，该方法包括：
    当第一区域的第一边缘设备跨至少一个中间区域与第二区域的第二边缘设备之间需要开通一虚拟专用网VPN业务时，所述第一边缘设备将与所述VPN业务对应的隧道要求标识添加到所述VPN业务对应的标签路由中；
    转发所述标签路由，使得接收到所述标签路由的边缘设备从所述标签路由中获取所述隧道要求标识，并使接收到所述标签路由的边缘设备利用所述隧道要求标识匹配自身所属区域中已经建立的隧道，如果所述隧道要求标识与所述已建立的隧道中的任一隧道的匹配结果满足预设条件，则选择所述任一隧道承载所述VPN业务。
  7. 一种边缘设备，其特征在于，该边缘设备包括：
    获取单元，当第一区域的第一边缘设备跨至少一个中间区域与第二区域的第二边缘设备之间需要开通一虚拟专用网VPN业务时，用于接收到与所述VPN业务对应的标签路由，并从所述标签路由中获取与所述VPN业务对应的隧道要求标识；
    隧道选择单元，用于利用获取到的隧道要求标识匹配自身所属区域中已经建立的隧道，如果所述隧道要求标识与所述已建立的隧道中的任一隧道的匹配结果满足预设条件，则选择所述任一隧道承载所述VPN业务。
  8. 如权利要求7所述的边缘设备，其特征在于，所述隧道选择单元还用于利用预设的算法对所述隧道要求标识和自身已建立的隧道的标识进行运算得到一运算结果，根据所述运算结果确定需要承载所述VPN业务的已经建立的隧道。
  9. 如权利要求8所述的边缘设备，其特征在于，所述隧道要求标识为业务亲和属性，所述隧道选择单元还用于将所述计算结果与自身存储的隧道管理属性匹配，并根据匹配结果确定需要承载所述VPN业务的已经建立的隧道。
  10. 如权利要求8所述的边缘设备，其特征在于，当所述边缘设备为第二边缘设备则该边缘设备还包括：
    隧道迭代单元，用于从所述标签路由中获取中转隧道，将所述中转隧道迭代形成所述第一边缘设备到所述第二边缘设备的完整业务隧道，其中，所述中转隧道是所述标签路由中携带的其他边缘设备选择的隧道。
  11. 如权利要求10所述的边缘设备，其特征在于，该边缘设备还包括：
    业务匹配单元，用于在接收到所述第一边缘设备发送的VPN业务路由时，从所述VPN业务路由中获取所述隧道要求标识；利用所述隧道要求标识与已建立隧道对应的隧道要求标识进行匹配，如果与所述隧道要求标识与任一隧道对应的隧道要求标识相同，则利用匹配确定的隧道发送所述VPN业务。
  12. 一种边缘设备，其特征在于，所述边缘设备为第一区域的第一边缘设备，其中，当所述第一边缘设备跨至少一个中间区域与第二区域的第二边缘设备之间需要开通一虚拟专用网VPN业务时，所述第一边缘设备包括：
    标识添加单元，用于将与所述VPN业务对应的隧道要求标识添加到所述VPN业务对应的标签路由中；
    转发单元，用于转发所述标签路由，使得接收到所述标签路由的边缘设备从所述标签路由中获取所述隧道要求标识，并使接收到所述标签路由的边缘设备利用所述隧道要求标识匹配自身所属区域中已经建立的隧道，如果所述隧道要求标识与所述已建立的隧道中的任一隧道的匹配结果满足预设条件，则选择所述任一隧道承载所述VPN业务。
PCT/CN2015/074488 2014-04-04 2015-03-18 一种业务隧道建立方法及设备 WO2015149623A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410136102.6 2014-04-04
CN201410136102.6A CN104980362B (zh) 2014-04-04 2014-04-04 一种业务隧道建立方法及设备

Publications (1)

Publication Number Publication Date
WO2015149623A1 true WO2015149623A1 (zh) 2015-10-08

Family

ID=54239379

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/074488 WO2015149623A1 (zh) 2014-04-04 2015-03-18 一种业务隧道建立方法及设备

Country Status (2)

Country Link
CN (1) CN104980362B (zh)
WO (1) WO2015149623A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110611607B (zh) * 2019-10-08 2021-10-19 深信服科技股份有限公司 隧道连接方法、控制设备、存储介质及装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101009627A (zh) * 2006-12-27 2007-08-01 华为技术有限公司 一种业务绑定的方法和设备
CN101163098A (zh) * 2007-11-13 2008-04-16 中兴通讯股份有限公司 一种实现业务数据流与标签交换路径隧道映射的方法
CN101702665A (zh) * 2009-11-13 2010-05-05 中兴通讯股份有限公司 以太网业务接入承载隧道的方法、运营商边缘设备和系统
EP2512071A1 (en) * 2010-02-05 2012-10-17 Huawei Technologies Co., Ltd. Method, apparatus, and system for distributing labels in seamless multi-protocol label switching network
CN103475557A (zh) * 2013-09-05 2013-12-25 华为技术有限公司 隧道建立的方法及路由器

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1254059C (zh) * 2002-12-10 2006-04-26 华为技术有限公司 一种多协议标签交换虚拟专用网的实现方法
US7558219B1 (en) * 2004-08-30 2009-07-07 Juniper Networks, Inc. Multicast trees for virtual private local area network (LAN) service multicast
CN100563182C (zh) * 2004-08-31 2009-11-25 华为技术有限公司 一种在多层标签交换网络中实现虚拟专网业务的方法
CN101848199A (zh) * 2009-03-26 2010-09-29 华为技术有限公司 实现层次化虚链路的方法和系统及传送设备
CN102377630A (zh) * 2011-10-13 2012-03-14 华为技术有限公司 基于流量工程隧道的虚拟专用网络实现方法及系统
CN103209125B (zh) * 2013-04-07 2016-03-02 杭州华三通信技术有限公司 一种标签信息的传输方法和设备

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101009627A (zh) * 2006-12-27 2007-08-01 华为技术有限公司 一种业务绑定的方法和设备
CN101163098A (zh) * 2007-11-13 2008-04-16 中兴通讯股份有限公司 一种实现业务数据流与标签交换路径隧道映射的方法
CN101702665A (zh) * 2009-11-13 2010-05-05 中兴通讯股份有限公司 以太网业务接入承载隧道的方法、运营商边缘设备和系统
EP2512071A1 (en) * 2010-02-05 2012-10-17 Huawei Technologies Co., Ltd. Method, apparatus, and system for distributing labels in seamless multi-protocol label switching network
CN103475557A (zh) * 2013-09-05 2013-12-25 华为技术有限公司 隧道建立的方法及路由器

Also Published As

Publication number Publication date
CN104980362B (zh) 2019-04-12
CN104980362A (zh) 2015-10-14

Similar Documents

Publication Publication Date Title
US11700198B2 (en) Transmission control method, node, network system and storage medium
EP3200402B1 (en) Segment routing information obtainment method and segment routing network establishment method
CN109257278B (zh) 用于非分段路由启用的路由器的分段路由标签交换路径方法
WO2020156105A1 (zh) 数据转发方法及相关装置
US9444677B2 (en) Scalable edge node protection using IPv6 segment routing extension header
EP3002913B1 (en) Tunnel establishment method, label allocation method, device, and network system
US9525619B2 (en) Scalable edge node protection using segment routing
US7751405B1 (en) Automatic configuration of label switched path tunnels using BGP attributes
US11805010B2 (en) Signaling IP path tunnels for traffic engineering
WO2016115823A1 (zh) 标签构造以及标签报文转发方法及装置
CN109218197B (zh) 分段路由中的冲突解决方法及路由器
WO2020134139A1 (zh) 一种业务数据的转发方法、网络设备及网络系统
WO2015192501A1 (zh) 地址信息的发布方法及装置
US11483242B2 (en) Seamless end-to-end segment routing across metropolitan area networks
US20160226753A1 (en) Scheme for performing one-pass tunnel forwarding function on two-layer network structure
US20210367883A1 (en) Bitmask route target in targeted distribution of information using a routing protocol
CN104980347A (zh) 一种建立隧道的方法及装置
US20150109954A1 (en) Topology discovery based on sctp/x2 snooping
US9294986B2 (en) Topology discovery based on explicit signaling
KR20130109154A (ko) 라우팅 정보 업데이트의 우선 순위 지정
WO2012116545A1 (en) Multiprotocol label switching (mpls) virtual private network (vpn) over routed ethernet backbone
WO2019052406A1 (en) METHODS, NODES, AND COMPUTER-READABLE MEDIA FOR TRUNK TUNNEL ESTABLISHMENT
WO2016150093A1 (zh) 报文转发方法、装置及服务提供商网络边缘pe设备
WO2015149623A1 (zh) 一种业务隧道建立方法及设备
WO2016119461A1 (zh) 一种建立bgp lsp隧道的方法及网络设备

Legal Events

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

Ref document number: 15773660

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: 15773660

Country of ref document: EP

Kind code of ref document: A1