[go: up one dir, main page]

WO2017211164A1 - Procédé, appareil et système de détermination de tunnel de chemin à commutation d'étiquettes entre systèmes autonomes - Google Patents

Procédé, appareil et système de détermination de tunnel de chemin à commutation d'étiquettes entre systèmes autonomes Download PDF

Info

Publication number
WO2017211164A1
WO2017211164A1 PCT/CN2017/084377 CN2017084377W WO2017211164A1 WO 2017211164 A1 WO2017211164 A1 WO 2017211164A1 CN 2017084377 W CN2017084377 W CN 2017084377W WO 2017211164 A1 WO2017211164 A1 WO 2017211164A1
Authority
WO
WIPO (PCT)
Prior art keywords
tunnel
node
controller
label
configuration message
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/CN2017/084377
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
Publication of WO2017211164A1 publication Critical patent/WO2017211164A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

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
    • 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]
    • 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
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control

Definitions

  • Embodiments of the present invention relate to the field of communications, and, more particularly, to a method, apparatus, and system for determining a cross-domain label switched path tunnel.
  • a cross-domain end-to-end label switched path (Label Switched Path) is required for the cross-domain end-to-end (E2E) service deployment.
  • LSP label Switched Path
  • the controller needs to calculate the inter-domain LSP tunnel on a node-by-node basis.
  • the corresponding tunnel configuration needs to be sent to each node in the tunnel to establish the cross-domain LSP tunnel.
  • the controller In the existing scheme of establishing a cross-domain LSP tunnel, the controller has a large computational burden and a large signaling overhead.
  • the present invention provides a method, device, and system for determining a cross-domain LSP tunnel, which can establish an inter-area LSP tunnel based on effectively reducing the computational burden and signaling overhead of the controller.
  • a method for determining a cross-domain label switched path tunnel comprising:
  • the controller acquires a tunnel establishment request, where the tunnel establishment request is used to request to establish a label switched path LSP tunnel between the first node and the tail node, where the first node and the tail node belong to different domains; a tunnel establishment request, the first cross-domain LSP tunnel is calculated based on the network topology, where the node that the first cross-domain LSP tunnel passes includes the first node, the first intermediate node, and the tail node, where the first node, The first intermediate node and the first node and the second node of the tail node have an established tunnel, and the network topology includes the established tunnel; the controller respectively goes to the first And the first intermediate node and the tail node send a corresponding tunnel configuration message, where the first node, the first intermediate node, and the tail node establish the first cross-domain LSP tunnel.
  • the tunnel configuration message sent by the controller to the first node carries next hop tunnel information, where the next hop tunnel information is used to indicate the established tunnel to indicate The first node using the tunnel has been established
  • the first intermediate node may include one or more nodes, in other words, one or more intermediate nodes may be included between the head node and the tail node of the first cross-domain LSP tunnel.
  • the head node and the tail node belong to different domains, and specifically, for example, the head node and the tail node belong to different AS domains, or the head node and the The tail nodes belong to different IGP domains in the same AS domain.
  • the first node may indicate a first node of the first cross-domain LSP tunnel, or indicate a first intermediate node of the first cross-domain LSP tunnel, or indicate the first node and the The first intermediate node is described.
  • the controller calculates a cross-domain LSP tunnel based on a network topology, where the network topology includes Once the tunnel has been established, the controller can calculate the cross-domain LSP tunnel based on the established tunnel in the network. Specifically, the controller learns, according to the network topology, that the cross-domain LSP tunnel to be calculated passes through the first node and the second node, and the established node has a tunnel between the first node and the second node, and the controller directly uses the established The tunnel determines the tunnel between the first node and the second node, rather than calculating the tunnel between the first node and the second node node by node.
  • the router After the controller completes the calculation of the inter-domain LSP tunnel, the router sends a corresponding tunnel configuration message to the forwarding node that crosses the LSP tunnel to complete the establishment of the inter-domain LSP tunnel, where the tunnel configuration is sent to the first node.
  • the message carries the next hop tunnel information, where the next hop tunnel information is used to indicate the established tunnel, to indicate that the first node establishes a communication connection with the second node by using the established tunnel, instead of requiring the same as in the prior art.
  • the forwarding connection between the first node and the second node can be implemented by each forwarding node between the first node and the second node, so that the signaling overhead of the controller can be reduced.
  • the controller calculates the cross-domain LSP tunnel by using the established tunnel in the network, which can effectively reduce the computing load of the controller.
  • the controller does not need to send the tunnel configuration to each node passing through the inter-domain LSP tunnel, which can reduce the signaling overhead of the controller to some extent.
  • the technical solution of the present invention can complete the establishment of a cross-domain LSP tunnel on the basis of effectively reducing the computational burden and signaling overhead of the controller.
  • the network topology that is learned by the controller includes the first node, the first intermediate node, and the tail node, and includes the first node and the second node. There is information about the established tunnel between the two.
  • the controller can learn that the cross-domain LSP tunnel passes through the first node and the second node, and the established node has an already established tunnel between the first node and the second node.
  • the controller may acquire the network topology by using any existing feasible method.
  • the established tunnel refers to a tunnel already established in the network.
  • the established tunnel includes but is not limited to any one of the following tunnels: LDP LSP, BGP LSP, TE, Tunnels used in communication networks such as GRE.
  • LDP is the Label Distribution Protocol
  • the TE is the traffic engineering
  • the BGP is the Border Gateway Protocol
  • the GRE is the Generic Routing Encapsulation.
  • the first node indicates the first node and the first intermediate node that the cross-domain LSP tunnel passes.
  • the controller knows according to the network topology that the cross-domain LSP tunnel is calculated by splicing the already established tunnel in the network, which can further reduce the calculation load of the controller.
  • the controller is configured to the first node, the first intermediate node, and the And sending, by the tail node, a corresponding tunnel configuration message, where the controller sends a first tunnel configuration message to the first node, where the first tunnel configuration message carries the following information: an ingress tunnel type, an outbound label, The IP address of the next hop node; the controller sends a second tunnel configuration message to the first intermediate node, where the second tunnel configuration message carries the following information: transit tunnel type (Transit), inbound label, outgoing label, The IP address of the next hop node, the ingress label of the first intermediate node is the same as the egress label of the previous hop node of the first intermediate node; the controller sends a third tunnel configuration message to the tail node, The third tunnel configuration message carries the following information: an egress tunnel type (Egress), an ingress label, and an ingress label of the tail node is the
  • the tunnel configuration message sent by the controller to the first node includes information indicating a tunnel name of the established tunnel and/or a tunnel type of the established tunnel.
  • the controller utilizes a network
  • the NETCONF protocol or the border gateway protocol BGP is configured to deliver the corresponding tunnel configuration message to the first node, the first intermediate node, and the tail node, respectively.
  • the controller The tunnel configuration message sent by the first node, the first intermediate node, and the tail node further carries the tunnel name of the first inter-area LSP tunnel
  • the method further includes: the controller according to the a tunnel establishment request, the second cross-domain LSP tunnel is calculated based on the network topology, where the node that the second cross-domain LSP tunnel passes includes the first node, the second intermediate node, and the tail node; a tunnel configuration message, where the first node, the second intermediate node, and the tail node send a tunnel name carrying the second cross-domain LSP tunnel, to indicate the first node, the second intermediate node, and the The tail node establishes the second cross-domain LSP tunnel.
  • the second inter-domain LSP tunnel is not the same LSP tunnel as the first LSP tunnel.
  • the first intermediate node represents each intermediate node of the first cross-domain LSP tunnel (other than the first node and the tail node)
  • the second intermediate node represents each intermediate node of the second cross-domain LSP tunnel (except A node other than the first node and the tail node, and the first intermediate node and the second intermediate node must have mutually different nodes.
  • the controller determines two different cross-domain LSP tunnels between the first node and the tail node by setting a tunnel name, which can implement end-to-end multi-path transmission.
  • the controller may further calculate multiple cross-domain LSP tunnels based on the first node and the tail node, and respectively configure different tunnel names, and send corresponding tunnel configuration messages to related nodes, so that the same is based on the same
  • the first node and the tail node establish multiple cross-domain LSP tunnels.
  • a method for determining a cross-domain label switched path tunnel comprising:
  • the first network device receives, by the controller, a tunnel configuration message, which is used to indicate the establishment of the cross-domain label switched path LSP tunnel, where the tunnel configuration message carries next hop tunnel information, where the next hop tunnel information is used to indicate the An established tunnel between a network device and a second network device, the cross-domain LSP tunnel including the established tunnel; the first network device according to the tunnel configuration message, through the established The tunnel establishes a communication connection with the second network device.
  • the cross-domain LSP tunnel is established through the tunnel already established in the network, which can effectively reduce the burden of the controller computing, and can also reduce the overhead of transmitting signaling between the controller and the network device.
  • the first network device is a first node of the cross-domain LSP tunnel
  • the tunnel configuration message received by the first network device is further Carrying the following information: an ingress tunnel type, an outgoing label, an IP address of a next hop node, the next hop node is the second network device; or the first network device is an intermediate node of the cross-domain LSP tunnel
  • the tunnel configuration message received by the first network device further carries the following information: a transit tunnel type, an inbound label, an outbound label, an IP address of a next hop node, and the next hop node is the second network device.
  • the ingress label of the first network device and the last hop node of the first network device The outgoing labels are the same.
  • the second network device when the first network device is the first node of the cross-domain LSP tunnel, the second network device is an intermediate node of the cross-domain LSP tunnel.
  • the first network device is an intermediate node of the cross-domain LSP tunnel
  • the second network device is a next hop intermediate node of the first network device in the cross-domain LSP tunnel, or the The second network device is a tail node of the cross-domain LSP tunnel.
  • the tunnel configuration message includes the following information: an egress tunnel type, an ingress label, and an ingress label of the second network device is the same as an egress label of the first network device.
  • the first network device determines, according to the next hop tunnel information, the established tunnel according to the tunnel configuration message sent by the controller, and is the established tunnel. Assign a tunnel ID and generate a forwarding entry.
  • the forwarding entry includes the tunnel destination IP address, the outbound label, the IP address of the next hop node, and the next hop tunnel ID.
  • the forwarding entry includes the tunnel destination IP address, the ingress label, the outbound label, the IP address of the next hop node, and the next hop tunnel ID.
  • the forwarding entry includes a tunnel destination IP address and an ingress label.
  • a method for determining a cross-domain LSP tunnel comprising:
  • the controller acquires a tunnel establishment request, where the tunnel establishment request is used to request to establish a label switching path LSP tunnel between the first end node and the second end node, where the first end node belongs to the first autonomous system, and the second The end node belongs to the second autonomous system, the first domain controller manages the first autonomous system, and the second domain controller manages the second autonomous system;
  • the controller determines, according to the tunnel establishment request, that a first cross-domain LSP tunnel is calculated by using a network topology of the first autonomous system and a network topology of the second autonomous system, where the first cross-domain LSP tunnel is The first node is the first end node, and the tail node is the second end node;
  • the controller sends a first indication message to the first domain controller, where the first indication message is used to indicate that a first between the first end node and the first border node of the first autonomous system is established.
  • An intra-domain LSP tunnel the first indication message further indicating that the first end node is a head node, the first border node is an intermediate node, and a next hop node of the first border node is the second autonomous system.
  • the second border node the first indication message is further used to indicate an outgoing label of the first border node;
  • the controller sends a second indication message to the second domain controller, where the second indication message is used to indicate establishing a second intra-domain LSP tunnel between the second end node and the second border node,
  • the second indication message further indicates that the second end node is a tail node, the second border node is an intermediate node, and the second indication message is further used to indicate an inbound label of the second border node,
  • the ingress label of the second boundary node is the same as the egress label of the first border node.
  • the controller in the controller layered scenario, the controller establishes an inter-domain LSP tunnel by controlling the domain controller, and can also reduce the controller computing burden and signaling overhead.
  • the first domain controller or the second domain controller may establish an LSP tunnel according to the method of the controller in the first aspect.
  • the controller may use the BGP protocol to send a tunnel configuration message to the node, and the tunnel configuration message based on the BGP protocol may be referred to as BGP signaling.
  • BGP signaling in the present invention is relative to traditional BGP
  • An address family is added to the Multi-Protocol Network Layer Reachability Information (MP-NLRI) attribute, and the address family is, for example, a tunnel routing address family, and the address family includes the following fields.
  • the information used for storing the fields is as follows:
  • the tunnel name field is used to store the tunnel name of the LSP tunnel to be established.
  • the length of the tunnel name field is, for example, 2 bytes. It should be understood that the tunnel is named a string, and specifically, the specific format of the tunnel name can be customized.
  • the tunnel length field is used to store the length of the tunnel name stored in the tunnel name field.
  • the length of the tunnel length field is, for example, 1 byte.
  • the destination address field is used to store the destination address of the LSP tunnel to be established.
  • the destination address is in the address family + destination address.
  • the address family includes IPv4 and IPv6.
  • the destination address field has a length of, for example, 3 bytes.
  • the address length field is used to store the total length of the tunnel destination address stored in the destination address field. For example, when the tunnel destination address is an IPv4 address, the address length is 4 bytes. When the tunnel destination address is an IPv6 address, the address length is generally 16 bytes, the length of the address length field is, for example, 1 byte.
  • the address mask field is used to store a mask of the tunnel destination address stored in the destination address field, and the length of the address mask field is, for example, 1 byte.
  • the tunnel type field is used to store the tunnel type of the receiving node of the current tunnel configuration message.
  • the tunnel type includes an ingress, a transit, or an egress.
  • the length of the tunnel type field is, for example, 1 byte.
  • the tunnel label field when the tunnel type in the tunnel type field is Ingress, the tunnel label stored in the tunnel label field is the outbound label.
  • the tunnel label in the tunnel type field is Transit or Egress, the tunnel label stored in the tunnel label field.
  • the length of the tunnel label field is, for example, 3 bytes.
  • the tunnel label field is valid only when the tunnel type in the tunnel type field is Transit. If the tunnel type is other, the tunnel label field is invalid. For example, the tunnel label field can be set to a null value.
  • the length of the tunnel label field is, for example, 3 bytes.
  • the tunnel next hop field is used to store the IP address of the next hop node of the receiving node of the current tunnel configuration message, for example, IPv4 or IPv6, and the length of the next hop field of the tunnel is, for example, 4 bytes.
  • the next hop tunnel type field is used to store the tunnel type of the tunnel existing between the receiving node and the next hop node of the current tunnel configuration message.
  • the next hop tunnel type may be an LDP LSP, a BGP LSP, a TE, or a GRE
  • the length of the next hop tunnel type field is, for example, 1 byte.
  • the tunnel identifier field is used to store the tunnel name corresponding to the tunnel type stored in the next hop tunnel type field, and the length of the tunnel identifier field is, for example, 3 bytes.
  • the tunnel identifier length field is used to store the length of the tunnel name stored in the tunnel identifier field, and the length of the tunnel identifier length field is, for example, 1 byte.
  • the tunnel routing field of the tunnel configuration message further includes the following field: a reverse tunnel association field, where information for indicating a reverse association tunnel is stored, and only in a hierarchical controller scenario, the reverse tunnel The associated field is valid, and is used by the upper-level controller to guide the lower-level controller to associate the tunnel.
  • the reverse tunnel association field specifically includes a reverse tunnel name field, and the length of the reverse tunnel name field is, for example, 2 bytes.
  • the length of the reverse tunnel length field is, for example, 1 byte
  • the reverse tunnel address length field and the length of the reverse tunnel address length field is, for example, 1 byte, and a reverse tunnel address mask field.
  • the length of the reverse tunnel address mask field is, for example, 1 byte
  • the reverse tunnel destination address field has a length of, for example, 3 bytes.
  • the meaning of setting the reverse tunnel association field is that the tunnel is usually unidirectional, that is, a tunnel has a unique destination address, but the service is generally bidirectional.
  • the service in each direction needs to be bound to the tunnel in the direction.
  • the traffic in the direction uses different tunnels. If the tunnels in the two directions are not related, the following situation may occur: the tunnel in direction A is invalid, and the tunnel in direction B (in the opposite direction to direction A) is still valid (Up). Layer controller scenarios are undesirable.
  • the two-way association tunnel is deployed, that is, the tunnels in the two directions A and B are associated, so that if one direction (for example, direction A) is used, If the tunnel is invalid, the tunnel in the other direction (for example, direction B) is also set to invalid.
  • next hop tunnel type field is illustrated by a specific example below.
  • the tunnel type stored in the next hop tunnel type field is an LDP LSP.
  • the LDP LSP carried in the next hop tunnel type field in the tunnel configuration message is used.
  • the LDP LSP tunnel with the next hop node is used to establish communication with the next hop node (for example, the LDP LSP tunnel is used to forward the service flow to the next hop node).
  • the LSP tunnel to be established is established by using the established LDP LSP tunnel. This process is also called tunnel iteration (current LSP tunnel iterative LDP LSP tunnel to be established).
  • the controller may also use the network configuration (NETCONF) protocol to deliver a tunnel configuration message to the node.
  • the format of the tunnel configuration message based on the NETCONF protocol may be a standard format of the NETCONF protocol, such as an xsd table.
  • the NETCONF-based tunnel configuration message also includes various fields included in the BGP-based tunnel configuration message, and is not described here for brevity.
  • a fourth aspect provides a controller for performing the method of the first aspect or the possible implementation of any of the aspects of the first aspect.
  • controller may comprise means for performing the method of the first aspect or any of the possible implementations of the first aspect.
  • a fifth aspect provides a network device for performing the method in a possible implementation of the second aspect or the second aspect.
  • the network device may comprise means for performing the method of any of the possible implementations of the second aspect or the second aspect.
  • a sixth aspect provides a controller including a memory and a processor for storing instructions for executing instructions stored in the memory, and performing execution of the instructions stored in the memory such that the processing The method of the first aspect or the possible implementation of any of the aspects of the first aspect is performed.
  • a seventh aspect provides a network device including a memory and a processor for storing instructions for executing instructions stored by the memory, and performing execution of the instructions stored in the memory such that the processing The method of the second aspect or a possible implementation of any of the aspects of the second aspect is performed.
  • a controller control system comprising a controller as provided in the fourth aspect and the network device as provided in the fifth aspect.
  • the controller calculates the cross-domain LSP tunnel by using the established tunnel in the network, which can effectively reduce the computing load of the controller.
  • the controller does not need to send the tunnel configuration to each node passing through the inter-domain LSP tunnel, which can reduce the signaling overhead of the controller to some extent.
  • the technical solution of the present invention can complete the establishment of a cross-domain LSP tunnel on the basis of effectively reducing the computational burden and signaling overhead of the controller.
  • FIG. 1 is a schematic diagram of a scenario of an embodiment of the present invention.
  • FIG. 2 is a schematic flowchart of a method for determining an LSP tunnel according to an embodiment of the present invention.
  • FIG. 3 is a schematic diagram of a method for determining an LSP tunnel according to an embodiment of the present invention.
  • FIG. 4 is a schematic diagram showing a format of a tunnel configuration message according to an embodiment of the present invention.
  • FIG. 5 is another schematic diagram of a method for determining an LSP tunnel according to an embodiment of the present invention.
  • FIG. 6 shows a schematic block diagram of a controller provided in accordance with an embodiment of the present invention.
  • FIG. 7 shows a schematic block diagram of a forwarding device according to an embodiment of the present invention.
  • FIG. 8 shows another schematic block diagram of a controller provided in accordance with an embodiment of the present invention.
  • FIG. 9 shows another schematic block diagram of a forwarding device according to an embodiment of the present invention.
  • FIG. 10 shows a schematic block diagram of a controller control system provided in accordance with an embodiment of the present invention.
  • the application scenario of the embodiment of the present invention is to establish an inter-area LSP tunnel, where the cross-domain refers to that two end nodes of the LSP tunnel to be established belong to two different domains, for example, belong to two different AS domains, or belong to Two different IGP domains within the same AS domain.
  • the already calculated tunnel in the network cannot be utilized, for example, a calculated traffic engineering (TE) tunnel in an AS domain, and the cross-domain LSP tunnel is completely calculated by the controller.
  • the controller is required to deliver the tunnel configuration to all the nodes passing through the inter-domain LSP tunnel, resulting in a large controller pressure and a large signaling overhead.
  • the embodiments of the present invention provide a method, a device, and a system for determining an inter-area LSP tunnel, which can establish an inter-area LSP tunnel on the basis of effectively reducing the computational load and signaling overhead of the controller.
  • SDN Software Defined Network
  • SNC SDN network controller
  • DC domain controller
  • ABR Autonomous System Boundary Router
  • the embodiment of the present invention can be applied to the scenario of the hierarchical controller (SNC and DC layer) shown in FIG. 1; and can also be applied to the scenario of a layer controller, for example, there is no DC in FIG. 1 and only the SNC is used.
  • the SNC uniformly controls and manages various network devices on the data plane.
  • the SNC can also be referred to as a super controller.
  • Multiprotocol Label Switching is a classification and forwarding technology. Groups with the same forwarding processing method are classified into one type, called FEC (Forwarding Equivalence Class). Packets of the same FEC will get exactly the same processing in the MPLS network.
  • the FEC is divided in a flexible manner, which can be based on the source address, destination address, source port, destination port, or protocol type. For example, in the traditional IP forwarding using the longest matching algorithm, all messages to the same destination address are an FEC.
  • a tag is a short identifier with a fixed length and only local significance. It is used to uniquely identify the FEC to which a packet belongs. A tag can only represent one FEC.
  • Label Switching Router is an MPLS network.
  • LSRs support MPLS technology.
  • the network devices CSG, ASG, and ASBR shown in Figure 1 can be used as LSRs.
  • a path that an FEC passes through in an MPLS network is called a Label Switched Path (LSP), such as LSP ⁇ CSG1 ⁇ ASG1 ⁇ ASBR1 ⁇ ASBR3 ⁇ CSG2> shown in FIG.
  • LSP Label Switched Path
  • adjacent LSRs are respectively referred to as an upstream LSR and a downstream LSR.
  • ASG1 is a downstream LSR of CSG1
  • CSG1 is an upstream LSR of ASG1.
  • the ingress node of the LSP is called the ingress node
  • the middle node also called the forwarding node
  • the egress node is called the egress node.
  • CSG1 is the ingress node, ASG1.
  • ASBR1 and ASBR3 are Transit nodes
  • CSG2 is an Egress node.
  • MPLS supports LSP tunneling technology.
  • the upstream LSR and the downstream LSR of an LSP although the path between them may not be on the path provided by the routing protocol, MPLS allows a new LSP to be established between them, so that the upstream LSR and the downstream LSR are respectively The start and end points of the LSP.
  • the LSP between the upstream LSR and the downstream LSR is an LSP tunnel, which avoids the traditional network layer encapsulation tunnel.
  • LSP ⁇ CSG1 ⁇ ASG1 ⁇ ASBR1 ⁇ ASBR3 ⁇ CSG2> shown in FIG. 1 can be regarded as a cross-domain LSP tunnel between CSG1 and CSG2.
  • FIG. 2 is a schematic flowchart of a method 100 for determining a cross-domain LSP tunnel according to an embodiment of the present invention. As shown in FIG. 2, the method 100 includes:
  • the controller acquires a tunnel establishment request, where the tunnel establishment request is used to request to establish a label switching path LSP tunnel between the first node and the tail node, where the first node and the tail node belong to different domains.
  • the controller in the embodiment of the present invention is, for example, the SNC shown in FIG.
  • the controller calculates, according to the tunnel establishment request, a first cross-domain LSP tunnel based on a network topology, where the node that the first cross-domain LSP tunnel passes includes the first node, the first intermediate node, and the tail node, where the first The node, the first intermediate node, and the first node and the second node in the tail node have an established tunnel, and the network topology includes the established tunnel.
  • the first intermediate node indicates one or more forwarding nodes located in the first cross-domain LSP tunnel between the head node and the tail node.
  • the controller sends a corresponding tunnel configuration message to the first node, the first intermediate node, and the tail node, respectively, to indicate that the first node, the first intermediate node, and the tail node establish the first cross-domain An LSP tunnel, where the tunnel configuration message sent by the controller to the first node carries next hop tunnel information, where the next hop tunnel information is used to indicate an established tunnel between the first node and the second node, Instructing the first node to make a communication connection with the second node by using the established tunnel.
  • the next hop tunnel information specifically includes a tunnel type of a next hop tunnel (corresponding to an already established tunnel).
  • the tunnel configuration message sent by the controller to the head node carries the following information: an ingress tunnel type, an outbound label, and an IP address of a next hop node;
  • the tunnel configuration message sent to the first intermediate node carries the following information: The tunnel type (Transit), the inbound label, the outgoing label, and the IP address of the next hop node.
  • the ingress label of the first intermediate node is the same as the egress label of the previous hop node of the first intermediate node; sent to the tail node.
  • the tunnel configuration message carries the following information: the egress tunnel type (Egress) and the inbound label.
  • the ingress label of the tail node is the same as the egress label of the last hop node of the tail node.
  • the first node according to the received tunnel configuration message, the tunnel configuration message carries next hop tunnel information, where the next hop tunnel information is used to indicate an established tunnel between the first node and the second node.
  • the first node establishes a communication connection with the second node through the established tunnel.
  • the second node is an intermediate node of the first cross-domain LSP tunnel.
  • the first node is an intermediate node of the first cross-domain LSP tunnel
  • the second node is a next hop intermediate node of the first node in the first cross-domain LSP tunnel, or the second node is the first node The tail node of a cross-domain LSP tunnel.
  • the tunnel configuration message sent by the first node receiving controller further carries the following information: ingress, outbound label, next The IP address of the hop node, which is the second node.
  • the first node determines the established tunnel according to the next hop tunnel information in the received tunnel configuration message, and allocates a tunnel ID for the established tunnel, and generates a forwarding entry.
  • the forwarding entry includes the tunnel destination IP address, the outgoing label, the IP address of the next hop node, and the next hop tunnel ID (that is, the ID assigned to the established tunnel).
  • the tunnel configuration message sent by the first node receiving controller further carries the following information: transit tunnel type (Transit), inbound label, and outgoing label
  • the IP address of the next hop node, the next hop node is the second node, and the ingress label of the first node is the same as the egress label of the previous hop node of the first node.
  • the first node determines the established tunnel according to the next hop tunnel information in the tunnel configuration message, allocates a tunnel ID to the established tunnel, and generates a forwarding entry.
  • the forwarding entry includes the tunnel destination IP address, the ingress label, the outbound label, the IP address of the next hop node, and the next hop tunnel ID (that is, the ID assigned to the established tunnel).
  • the tunnel configuration message sent by the second node receiving controller includes the following Information: The egress egress and the ingress label.
  • the ingress label of the second node is the same as the egress label of the first node.
  • the second node generates a forwarding entry according to the received tunnel configuration message, where the forwarding entry includes a tunnel destination IP address and an ingress label.
  • the controller acquires the network topology (including related topology information of CSG1, ASG1, CSG3, and CSG2) as shown in FIG. 3 in advance.
  • the LDP LSP tunnel may include multiple forwarding nodes (not shown in Figure 3).
  • a TE tunnel has been established between ASG1 and CSG2.
  • the TE tunnel may include Multiple forwarding nodes (not shown in Figure 3).
  • the LDP LSP tunnel between CSG1 and CSG2, and the TE tunnel between ASG1 and CSG2 correspond to the established tunnel in the embodiment of the present invention.
  • the controller obtains a tunnel establishment request for requesting establishment of an LSP tunnel between CSG1 and CSG2.
  • the CSG1 is the first node and the CSG2 is the tail node, and an LSP tunnel is calculated: ⁇ CSG1 ⁇ ASG1 ⁇ CSG2> (corresponding to the first cross-domain LSP tunnel in the embodiment of the present invention) ).
  • CSG1 is an ingress node
  • ASG1 is a transit node
  • CSG2 is an egress node.
  • the controller assigns a label to the CSG1, the ASG1, and the CSG2.
  • the label Label1 is assigned to the ingress node CSG1, the label Label1 and the outgoing label Label2 are assigned to the transit node ASG1, and the label Label2 is assigned to the Egress node CSG2.
  • the controller then sends a related tunnel configuration message to CSG1, ASG1, and CSG2 to create an LSP tunnel ⁇ CSG1 ⁇ ASG1 ⁇ CSG2>.
  • the tunnel configuration message sent by the controller to the CSG1 includes: an ingress tunnel type (Ingress), an outgoing label Label1, an IP address of a next hop node (ie, ASG1), and a next hop tunnel type LDP LSP tunnel, used for The CSG1 is configured to establish a communication connection with the ASG1 by using the LDP LSP tunnel.
  • the tunnel configuration message sent to the ASG1 includes: a transit tunnel type (Transit), an inbound label Label1, an outgoing label Label2, and an IP address of a next hop node (ie, CSG2).
  • a next-hop tunnel type TE tunnel which is used to instruct ASG1 to establish a communication connection with CSG2 by using a TE tunnel.
  • the ASG1 uses the TE tunnel to forward the service flow to the CSG2.
  • the tunnel configuration message sent to the CSG2 includes the egress tunnel type (Egress) and the label Label2.
  • the establishment of the LSP tunnel ⁇ CSG1 ⁇ ASG1 ⁇ CSG2> is completed.
  • Subsequent traffic entering the network will be transmitted according to ⁇ CSG1 ⁇ ASG1 ⁇ CSG2>.
  • CSG1 uses the LDP LSP tunnel to send the service flow carrying Label1 to ASG1, ASG1 receives the service flow carrying Label1, replaces Label1 in the service flow with Label2, and uses the TE tunnel to CSG2 sends the service flow carrying Label2, and CSG2 receives the service flow carrying Label2.
  • the node determines the established tunnel according to the next hop tunnel information, and allocates a tunnel ID for the established tunnel, and Generate a forwarding entry.
  • the CSG1 generates a forwarding entry according to the tunnel configuration message sent by the controller, where the forwarding entry includes the tunnel destination IP address (that is, the IP address of the CSG2), and the IP of the outgoing label Label1 and the next hop node (that is, ASG1). Address, ID of the next hop tunnel (that is, the LDP LSP tunnel).
  • the ASG1 generates a forwarding entry according to the tunnel configuration message sent by the controller.
  • the forwarding entry includes the tunnel destination IP address (that is, the IP address of CSG2), the inbound label Label1, the outgoing label Label2, and the next hop node (that is, CSG1). IP address, next hop tunnel (ie TE tunnel) ID.
  • the forwarding entry is generated by the CSG2 according to the tunnel configuration message sent by the controller.
  • the forwarding entry includes the tunnel destination IP address (that is, the IP address of CSG2) and the label Label2.
  • the controller allocates a tunnel name Tunnel1 for the LSP tunnel ⁇ CSG1 ⁇ ASG1 ⁇ CSG2> (that is, the tunnel configured for the first inter-area LSP tunnel is named Tunnel1).
  • tunnel name Tunnel1 may be carried in the relevant tunnel configuration message sent by the controller to the CSG1, the ASG1, and the CSG2.
  • the controller calculates the cross-domain LSP tunnel based on the network topology, where the network topology includes the already established tunnel, and the controller may calculate the cross-domain LSP tunnel based on the already established tunnel in the network. Specifically, the controller learns, according to the network topology, that the cross-domain LSP tunnel to be calculated passes through the first node and the second node, and the already established tunnel is established between the first node and the second node, and the controller directly The tunnel between the first node and the second node is determined by using the already established tunnel, instead of calculating the tunnel between the first node and the second node node by node.
  • the router sends a corresponding tunnel configuration message to the forwarding node that crosses the LSP tunnel to complete the establishment of the inter-domain LSP tunnel, where the tunnel configuration is sent to the first node.
  • the message carries the next hop tunnel information, where the next hop tunnel information is used to indicate the established tunnel, to indicate that the first node establishes a communication connection with the second node by using the established tunnel, instead of requiring the same as in the prior art.
  • the forwarding connection between the first node and the second node can be implemented by each forwarding node between the first node and the second node, so that the signaling overhead of the controller can be reduced.
  • the controller calculates the cross-domain LSP tunnel by using the established tunnel in the network, which can effectively reduce the computing load of the controller.
  • the controller does not need to send the tunnel configuration to each node passing through the inter-domain LSP tunnel, which can reduce the signaling overhead of the controller to some extent.
  • the embodiment of the present invention can complete the establishment of the cross-domain LSP tunnel on the basis of effectively reducing the computational burden and signaling overhead of the controller.
  • FIG. 3 is by way of example and not limitation.
  • a tunnel established between ASG1 and CSG2 may be the following tunnel types in addition to the TE tunnel: LDP LSP, BGP LSP, TE, GRE, etc. Used tunnel. This embodiment of the present invention does not limit this.
  • the controller sends a corresponding tunnel configuration message to the first node, the first intermediate node, and the tail node, including: the controller network configuration NETCONF protocol or border gateway protocol BGP delivers a corresponding tunnel configuration message to the first node, the first intermediate node, and the tail node.
  • the tunnel configuration message is BGP signaling.
  • the controller may use the BGP protocol to send a tunnel configuration message to the node, and the tunnel configuration message based on the BGP protocol may be referred to as BGP signaling.
  • the BGP signaling in the present invention adds an address family to the multi-protocol network layer reachability information (MP-NLRI) attribute, which can be called, for example, a tunnel routing address family, and the address family includes
  • MP-NLRI multi-protocol network layer reachability information
  • the tunnel name field is used to store the tunnel name of the LSP tunnel to be established.
  • the length of the tunnel name field is, for example, 2 bytes. It should be understood that the tunnel is named a string, and specifically, the specific format of the tunnel name can be customized.
  • the tunnel length field is used to store the length of the tunnel name stored in the tunnel name field.
  • the length of the tunnel length field is, for example, 1 byte.
  • the destination address field is used to store the destination address of the LSP tunnel to be established.
  • the destination address is in the address family + destination address.
  • the address family includes IPv4 and IPv6.
  • the destination address field has a length of, for example, 3 bytes.
  • the address length field is used to store the total length of the tunnel destination address stored in the destination address field. For example, when the tunnel destination address is an IPv4 address, the address length is 4 bytes. When the tunnel destination address is an IPv6 address, the address length is generally 16 bytes, the length of the address length field is, for example, 1 byte.
  • the address mask field is used to store a mask of the tunnel destination address stored in the destination address field, and the length of the address mask field is, for example, 1 byte.
  • the tunnel type field is used to store the tunnel type of the receiving node of the current tunnel configuration message.
  • the tunnel type includes an ingress, a transit, or an egress.
  • the length of the tunnel type field is, for example, 1 byte.
  • the tunnel label field when the tunnel type in the tunnel type field is Ingress, the tunnel label stored in the tunnel label field is the outbound label.
  • the tunnel label in the tunnel type field is Transit or Egress, the tunnel label stored in the tunnel label field.
  • the length of the tunnel label field is, for example, 3 bytes.
  • the tunnel label field is valid only when the tunnel type in the tunnel type field is Transit. If the tunnel type is other, the tunnel label field is invalid. For example, the tunnel label field can be set to a null value.
  • the length of the tunnel label field is, for example, 3 bytes.
  • the tunnel next hop field is used to store the IP address of the next hop node of the receiving node of the current tunnel configuration message, for example, IPv4 or IPv6, and the length of the next hop field of the tunnel is, for example, 4 bytes.
  • the next hop tunnel type field is used to store the tunnel type of the tunnel existing between the receiving node and the next hop node of the current tunnel configuration message.
  • the next hop tunnel type may be an LDP LSP, a BGP LSP, a TE, or a GRE
  • the length of the next hop tunnel type field is, for example, 1 byte.
  • the tunnel identifier field is used to store the tunnel name corresponding to the tunnel type stored in the next hop tunnel type field, and the length of the tunnel identifier field is, for example, 3 bytes.
  • the tunnel identifier length field is used to store the length of the tunnel name stored in the tunnel identifier field, and the length of the tunnel identifier length field is, for example, 1 byte.
  • the tunnel routing field of the tunnel configuration message further includes the following field: a reverse tunnel association field, where information for indicating a reverse association tunnel is stored, only in a hierarchical controller scenario.
  • the reverse tunnel association field is valid, and is used by the upper-level controller to guide the lower-level controller to associate the tunnel.
  • the reverse tunnel association field specifically includes a reverse tunnel name field, and the length of the reverse tunnel name field is, for example, 2 bytes, the reverse tunnel length field, the length of the reverse tunnel length field is, for example, 1 byte, the reverse tunnel address length field, and the length of the reverse tunnel address length field is, for example, 1 byte, and the reverse tunnel address
  • the mask field, the length of the reverse tunnel address mask field is, for example, 1 byte, and the reverse tunnel destination address field has a length of, for example, 3 bytes.
  • the controller may further send a tunnel configuration message to the node by using a network configuration (NETCONF) protocol, and the format of the tunnel configuration message based on the NETCONF protocol may be a NETCONF protocol.
  • Standard format such as the xsd table.
  • the NETCONF-based tunnel configuration message also includes various fields as shown in FIG. 4, which are not described herein for brevity.
  • the LSP tunnel calculated by the controller is: ⁇ CSG1 ⁇ ASG1 ⁇ CSG2>, and the controller allocates the tunnel name Tunnel1 for the LSP tunnel ⁇ CSG1 ⁇ ASG1 ⁇ CSG2>.
  • the format of the tunnel configuration message delivered by the controller to the CSG1 that is the ingress node is as shown in Figure 4, where the tunnel name field stores the string "Tunnel1"; the tunnel length field stores the length of the string "Tunnel1”; the destination address
  • the destination IP address of the LSP tunnel is stored in the field, that is, the IP address of the CSG2; the total length of the IP address of the CSG2 stored in the destination address field is stored in the address length field; and the address mask field stores the IP address of the CSG2 stored in the destination address field.
  • the mask is stored in the tunnel type field; the label label field stores the label Label1; the tunnel label field is the invalid field; the next hop field of the tunnel stores the IP address of the ASG1; and the next hop tunnel type field stores the tunnel of the LDP LSP tunnel.
  • Type information The tunnel identifier field stores the tunnel name of the LDP LSP tunnel stored in the next hop tunnel type field; the tunnel identifier length field stores the length of the tunnel name stored in the tunnel identifier field; the reverse tunnel association field is an invalid field.
  • the format of the tunnel configuration message sent by the controller to the ASG1 that is the Transit node is also shown in Figure 4.
  • the tunnel name field stores the string "Tunnel1";
  • the tunnel length field stores the length of the string "Tunnel1”;
  • the address field stores the destination IP address of the LSP tunnel, that is, the IP address of CSG2;
  • the address length field stores the total length of the IP address of the CSG2 stored in the destination address field;
  • the address mask field stores the IP of the CSG2 stored in the destination address field.
  • tunnel type field stores Transit
  • tunnel label field stores label Label1
  • tunnel switch label field stores label Label2
  • tunnel next hop field stores CSG2 IP address
  • next hop tunnel type field stores TE tunnel
  • tunnel The identifier field stores the tunnel name of the TE tunnel
  • the tunnel identifier length field stores the length of the tunnel name of the TE tunnel stored in the tunnel identifier field
  • the reverse tunnel association field is an invalid field.
  • the format of the tunnel configuration message sent by the controller to the CSG2 that is the egress node is also shown in Figure 4.
  • the tunnel name field stores the string "Tunnel1";
  • the tunnel length field stores the length of the string "Tunnel1”;
  • the address field stores the destination IP address of the LSP tunnel, that is, the IP address of CSG2;
  • the address length field stores the total length of the IP address of the CSG2 stored in the destination address field;
  • the address mask field stores the IP of the CSG2 stored in the destination address field.
  • the mask of the address; the tunnel type field stores the Egress; the tunnel label field stores the label Label2; the tunnel switch label field, the tunnel next hop field, the next hop tunnel type field, the tunnel identifier field, and the tunnel identifier length field are associated with the reverse tunnel. Fields with invalid fields are invalid fields.
  • the controller may send a tunnel configuration message from the tail node of the calculated LSP tunnel.
  • the controller sends the CSG1 to the CSG1.
  • the corresponding tunnel configuration message can be sent one by one from the tail node CSG2.
  • the tunnel configuration message sent by the controller to the first node, the first intermediate node, and the tail node further carries the tunnel name of the first cross-domain LSP tunnel, where
  • the method 100 also includes:
  • the controller calculates a second cross-domain LSP tunnel based on the network topology according to the tunnel establishment request, where the node that the second cross-domain LSP tunnel passes includes the first node, the second intermediate node, and the tail node, and the second intermediate node Not exactly the same as the first intermediate node.
  • the second intermediate node indicates one or more forwarding nodes located in the third LSP tunnel between the first node and the tail node. It should be understood that the second intermediate node is not identical to the first intermediate node in the first cross-domain LSP tunnel in S120.
  • the controller sends a tunnel configuration message carrying the tunnel name of the second cross-domain LSP tunnel to the first node, the second intermediate node, and the tail node, and is used to indicate the first node, the second intermediate node, and the tail node. Establish the second cross-domain LSP tunnel.
  • the controller calculates an LSP tunnel between CSG1 and CSG2 according to the network topology shown in FIG. 3.
  • the calculated LSP tunnel is: ⁇ CSG1—ASG2—CSG2> (corresponding to the third LSP tunnel in the embodiment of the present invention), the tunnel direction is ⁇ CSG1 ⁇ ASG2 ⁇ CSG2> as an example.
  • CSG1 is an ingress node
  • ASG2 is a transit node
  • CSG2 is an egress node.
  • a label is assigned to CSG1, ASG2, and CSG2.
  • CSG1 is an ingress node
  • label Label3 is assigned to it.
  • ASG2 is a transit node, which is assigned a label Label3 and an outgoing label Label4.
  • CSG2 is an Egress node and is assigned a label Label4.
  • the controller configures the tunnel name Tunnel2 for the ⁇ CSG1 ⁇ ASG1 ⁇ CSG2> (that is, the tunnel name of the third LSP tunnel is Tunnel2). Then, the controller sends a related tunnel configuration message to CSG1, ASG2, and CSG2 to create an LSP tunnel ⁇ CSG1 ⁇ ASG2 ⁇ CSG2>, and the specific process and the first cross-domain LSP tunnel (ie, ⁇ CSG1 ⁇ ASG1 ⁇ CSG2>) The related process is similar. For the sake of introduction, it will not be repeated here.
  • the tunnel configuration message sent by the controller to CSG1 and ASG2 in the LSP tunnel ⁇ CSG1 ⁇ ASG2 ⁇ CSG2> also carries the next hop tunnel information, so as to efficiently establish the tunnel by iterating the established tunnel.
  • the controller calculates two different LSP tunnels between the head node (CSG1) and the tail node (CSG2), and configures different tunnel names for the two LSP tunnels respectively. Distinguish between the two LSP tunnels.
  • the forwarding device receives the channel configuration information sent by the controller, and can distinguish different LSP tunnels according to the tunnel name carried therein.
  • the controller calculates two different tunnels between the first node and the tail node, and implements the establishment of two tunnels by sending messages to the forwarding nodes of the different tunnels, and in the message.
  • the tunnel name of the corresponding tunnel is carried to distinguish different tunnels between the same head node and the tail node. Therefore, the present invention can flexibly implement two different tunnels between the same head node and the tail node.
  • the embodiment of the present invention further provides a method for determining a cross-domain LSP tunnel, where the method includes:
  • the controller acquires a tunnel establishment request, and the tunnel establishment request is used to request to establish a label switching path LSP tunnel between the first end node and the second end node, where the first end node belongs to the first autonomous system, and the second end node belongs to a second autonomous system, the first domain controller manages the first autonomous system, and the second domain controller manages the second autonomous system;
  • the controller determines, according to the tunnel establishment request, that the first cross-domain LSP tunnel is to be calculated by using the network topology of the first autonomous system and the network topology of the second autonomous system, where the first node of the first cross-domain LSP tunnel is the first node One end node and a tail node are the second end node;
  • the controller sends a first indication message to the first domain controller, where the first indication message is used to indicate that the first intra-domain LSP tunnel between the first end node and the first border node of the first autonomous system is established.
  • the first indication message further indicates that the first end node is a head node, the first border node is an intermediate node, and the next hop node of the first border node is a second border node of the second autonomous system, the first indication
  • the message is further used to indicate an outgoing label of the first border node;
  • the controller sends a second indication message to the second domain controller, where the second indication message is used to indicate establishing a second intra-domain LSP tunnel between the second end node and the second border node, the second indication message And indicating that the second end node is a tail node, and the second border node is an intermediate node, where the second indication message is further used to indicate an inbound label of the second border node, and the inbound label of the second border node is the first label
  • the outbound labels of the boundary nodes are the same.
  • CSG1, CSG3, ASG1, and ASBR1 are routers in AS1, and CSG2, ASBR2, and ASBR3 are routers in AS2.
  • the domain controller DC1 is responsible for managing the routers in AS1, namely CSG1, CSG3, ASG1 and ASBR1.
  • DC2 is responsible for managing the routers in AS1, namely CSG2, ASBR2 and ASBR3.
  • the controller is responsible for controlling DC1 and DC2, and also knows that DC1 manages AS1 and DC2 to manage AS2.
  • the scenario shown in FIG. 5 is a layered scenario of the controller, and the layering of the controller refers to hierarchical abstraction of the complete network topology, and the network topology of the higher layer ignores the internal information of the lower layer network topology.
  • the network topology of the lower layer receives the decomposition of the network topology of the higher layer and then performs the secondary calculation decomposition according to the internal topology.
  • DC1 can obtain the network topology of AS1
  • DC2 can obtain the network topology of AS2.
  • the controller only obtains the network topology of the upper layer. That is, the controller can only obtain the border routers of AS1 and AS2, that is, ASBR1, ASBR2, and ASBR3, and can also manage and control these border routers.
  • the controller does not see the network topology inside AS1 and AS2. In other words, the controller cannot directly manage the internal routers of AS1 and AS2. Of course, the controller can know the end node of the LSP tunnel to be established. In the scenario shown in Figure 5, the network topology that the controller can see is CSG1—ASBR1—ASBR2/3—CSG2.
  • the tunnel establishment request received by the controller is used to request to establish an LSP tunnel between CSG1 and CSG2, and the LSP tunnel calculated by the controller is ⁇ CSG1 ⁇ ASBR1 ⁇ ASBR3 ⁇ CSG2>.
  • the controller assigns a tunnel named Tunnel1 to the tunnel ⁇ CSG1 ⁇ ASBR1 ⁇ ASBR3 ⁇ CSG2>.
  • the controller finds that CSG1 and CSG2 are not managed by the controller.
  • the controller allocates the switching label only for ASBR1 and ASBR3, the label L1 to ASBR1, and the label L1 to ASBR3.
  • the controller can also notify the corresponding PCEP to calculate the tunnel between ASBR1 and ASBR3.
  • the PCEP can also be notified to establish an inter-domain tunnel between ASBR1 and ASBR2.
  • the AS1 and AS2 internal nodes are not assigned to the controller. Therefore, the controller sends the remaining tunnel requests CSG1-ASBR1 and ASBR3-CSG2 to DC1 and DC2 respectively.
  • the controller sends a first tunnel establishment request to the DC1.
  • the first tunnel establishment request carries the following information: the LSP tunnel from the CSG1 to the ASBR1 is established, and the tail node of the LSP tunnel is CSG2, the ASBR1 is Transit, and the next hop node of the ASBR1 is ASBR3, and the outgoing label of ASBR1 is Label1.
  • the controller sends a second tunnel establishment request to the DC1.
  • the second tunnel establishment request carries the following information: the LSP tunnel from the ASBR3 to the CSG2 is established, and the tail node of the LSP tunnel is CSG2, the ASBR3 is Transit, and the next hop node of the ASBR3 is The inbound label of CSG2 and ASBR3 is Label1.
  • DC1 calculates an LSP tunnel from CSG1 to ASBR1 according to the first tunnel establishment request. Assume that the LSP tunnel calculated by DC1 is ⁇ CSG1 ⁇ ASG1 ⁇ ASBR1>, then CSG1 is the Ingress, and the label L3 is assigned to it, and the next hop node is ASG1; ASG1 is Transit, which is assigned the label L3 and the outgoing label L4. The next hop node is ASBR1; ASBR1 is Transit, which is assigned the label L4 and the outgoing label L1, and the next hop node is ASBR3.
  • the DC1 delivers the corresponding tunnel configuration information to the CSG1, the ASG1, and the ASBR1 according to the tunnel configuration of the CSG1 to the ASBR1.
  • the tunnel configuration message sent by the DC1 to the CSG1 includes: an ingress type, an IP address of the outgoing label Label3 and the next hop node ASG1, and a next hop tunnel information, and may also include a tunnel name Tunnel1;
  • the tunnel configuration message sent to the ASBR1 is the transit tunnel type (Transit), the inbound label Label3, the outbound label Label4 and the IP address of the next hop node ASBR1, and the next hop tunnel information.
  • the configuration message includes: the transit tunnel type (Transit), the inbound label Label4, the outgoing label Label1 and the next hop node ASBR3, the next hop tunnel information, and the tunnel name Tunnel1.
  • next hop tunnel information is used to indicate that the tunnel has been established between the ASBR1 and the ASBR3, and is used to instruct the ASBR1 to forward the service flow to the ASBR3 by using the established tunnel.
  • the DC2 calculates an LSP tunnel from ASBR3 to CSG2 according to the second tunnel establishment request. Assume that the LSP tunnel calculated by DC2 is ⁇ ASBR3 ⁇ CSG2>, and ASBR3 is Transit, which is assigned the label L1 and the outgoing label L5, and the next hop node is CSG2; CSG2 is the Egress, and the label L5 is assigned to it.
  • the DC2 sends the corresponding tunnel configuration information to the ASBR3 and the CSG2 according to the ASBR3 to CSG2 tunnel configuration.
  • the tunnel configuration message sent by DC2 to ASBR2 includes: transit tunnel type (Transit), inbound label Label1, outgoing label Label5 and next hop node CSG2 IP address, next hop tunnel information, and tunnel name Tunnel1; to CSG2
  • the delivered tunnel configuration message includes the egress tunnel type (Egress), the inbound label Label5, and the tunnel name Tunnel1.
  • the controller establishes an LSP tunnel of CSG1 to CSG2 through DC1 and DC2, that is, ⁇ CSG1 ⁇ ASG1 ⁇ ASBR1 ⁇ ASBR3 ⁇ CSG2>.
  • the controller does not need to acquire the network topology of the first autonomous system and the second autonomous system, that is, the first node and the tail node can be completed by controlling the domain controller without acquiring all network topologies.
  • the tunnel is established, and therefore, the present invention can reduce the computational and communication burden of the controller.
  • the DC1 can use the BGP protocol to deliver the corresponding tunnel configuration message to the CSG1, the ASG1, and the ASBR1, respectively, and the DC2 can use the BGP protocol to deliver the corresponding tunnel configuration to the ASBR3 and the CSG2 respectively.
  • the format of the tunnel configuration message is shown in Figure 4. For brevity, it will not be described here.
  • the LSP tunnel is directional.
  • the method for establishing an end-to-end LSP tunnel described above with reference to FIG. 3 and FIG. 5 is described by taking a tunnel direction as an example.
  • the description is made by taking the tunnel direction as ⁇ CSG1 ⁇ ASG1 ⁇ CSG2> as an example, but the embodiment of the present invention is not limited thereto.
  • the controller is for two tunnel end nodes (for example, CSG1 and CSG2 in FIG. 3) ), a bidirectional LSP tunnel can be established.
  • the controller calculates the reverse LSP tunnel ⁇ CSG2 ⁇ ASG1 ⁇ CSG1>, and the destination address of the reverse LSP tunnel is the IP address of the CSG1, and the CSG2 is the Ingress, and the label is allocated.
  • ASG1 is Transit, which is assigned a label a and an outgoing label b
  • CSG1 is an Egress, and is assigned a label b.
  • the controller delivers the corresponding tunnel configuration message to CSG2, ASG1, and CSG1 according to the above configuration.
  • the TE tunnel is configured between the CSG2 and the ASG1.
  • the tunnel configuration message sent by the controller to the CSG2 also carries information indicating that the next hop tunnel type is a TE tunnel, and is used to indicate that the CSG2 passes the TE tunnel and the ASG1. Establish a communication connection.
  • a bidirectional tunnel can also be established.
  • the reverse LSP path between CSG1 and CSG2 calculated by the controller is ⁇ CSG2 ⁇ ASBR3 ⁇ ASBR1 ⁇ CSG1> (reverse is relative).
  • the controller finds that CSG1 and CSG2 are not managed by the controller.
  • the controller only assigns the label to ASBR1 and ASBR3.
  • the controller assigns label Label2 to ASBR1 and label Label2 to ASBR3.
  • the AS1 and AS2 internal nodes are not assigned to the controller. Therefore, the controller sends the remaining tunnel requests CSG2-ASBR3 and ASBR1-CSG1 to DC2 and DC1 respectively.
  • the controller sends a third tunnel establishment request to the DC1.
  • the third tunnel establishment request carries the following information: the LSP tunnel of the ASBR1 to the CSG1 is established, and the tail node of the LSP tunnel is CSG1, the ASBR1 is Transit, and the ingress label of the ASBR1 is Label2.
  • the controller sends a fourth tunnel establishment request to the DC1.
  • the fourth tunnel establishment request carries the following information: the LSP tunnel from the CSG2 to the ASBR3 is established, and the tail node of the LSP tunnel is CSG1, the ASBR3 is transit, and the label of the ASBR3 is Label2.
  • the next hop of ASBR3 is ASBR1.
  • DC1 calculates the LSP tunnel from ASBR1 to CSG1 according to the third tunnel establishment request. It is assumed that the LSP tunnel calculated by DC1 is ⁇ ASBR1 ⁇ ASG1 ⁇ CSG1>, and the corresponding tunnel configuration information is sent to CSG1, ASG1, and ASBR1 to establish an LSP tunnel. For ⁇ ASBR1 ⁇ ASG1 ⁇ CSG1>, the specific process is similar to the above-mentioned forward tunnel ( ⁇ CSG1 ⁇ ASG1 ⁇ ASBR1>) establishment process, and will not be described here. Assume that the inter-domain tunnel is established between ASBR1 and ASBR3. The tunnel configuration message sent by DC1 to ASBR1 also includes the next hop tunnel information.
  • the next hop tunnel information is used to indicate the tunnel established between ASBR1 and ASBR3. That is, the inter-domain tunnel is used to indicate that ASBR1 uses the inter-domain tunnel to forward traffic to ASBR3.
  • DC2 calculates an LSP tunnel from CSG2 to ASBR3 according to the fourth tunnel establishment request. Assume that the LSP tunnel calculated by the DC2 is ⁇ CSG2 ⁇ ASBR3>, and the corresponding tunnel configuration information is sent to the ASBR3 and the CSG2 to establish an LSP tunnel ⁇ CSG2 ⁇ ASBR3>. So far, the controller establishes an LSP tunnel of CSG2 to CSG1 through DC1 and DC2, that is, ⁇ CSG2 ⁇ ASBR3 ⁇ ASBR1 ⁇ ASG1 ⁇ CSG1>.
  • the association of the bidirectional LSP tunnel may be established.
  • the tunnel configuration message sent by the controller to the forwarding node carries the reverse tunnel association information, including the tunnel name and tunnel address information, for example.
  • the reverse tunnel association information may be directly sent by the controller to the relevant forwarding node, for example, the tunnel configuration message sent by the controller to the relevant forwarding node is included.
  • the reverse tunnel association field stores reverse correlation tunnel related information
  • the reverse tunnel association field specifically includes a reverse tunnel name field, a reverse tunnel length field, a reverse tunnel address length field, and a reverse
  • the tunnel address mask field and the reverse tunnel destination address field are shown in Figure 4.
  • the upper layer controller such as the controller shown in FIG. 5 first tells the domain controller (such as DC1 and DC2 as shown in FIG. 5) that the inverse association is associated with the tunnel. The information is then sent by the domain controller to the associated forwarding node.
  • the controller calculates the LSP tunnel according to the network topology, the first node and the tail node, and the specific calculation method may utilize the existing method for calculating the end-to-end LSP tunnel, which is not compared in the embodiment of the present invention. limited. It should be noted that, in the embodiment of the present invention, the controller can determine the end-to-end LSP tunnel to be established by using the established LSP tunnel, for example, the TE tunnel shown in FIG. 3, in other words, the embodiment of the present invention. The calculated LSP tunnel can iterate over the established LSP tunnel.
  • FIG. 6 is a schematic block diagram of a controller 200 according to an embodiment of the present invention.
  • the controller 200 includes:
  • the obtaining module 210 is configured to acquire a tunnel establishment request, where the tunnel establishment request is used to request to establish a label switched path LSP tunnel between the first node and the tail node, where the first node and the tail node belong to different domains;
  • the calculating module 220 is configured to calculate, according to the tunnel establishment request acquired by the acquiring module, a first cross-domain LSP tunnel based on a network topology, where the node that the first cross-domain LSP tunnel passes includes the first node, the first intermediate node, and the tail a node, wherein the first node, the first intermediate node, and the first node and the second node in the tail node have an established tunnel, and the network topology includes the established tunnel;
  • the sending module 230 is configured to send a corresponding tunnel configuration to the first node, the first intermediate node, and the tail node. And indicating that the first node, the first intermediate node, and the tail node establish the first cross-domain LSP tunnel calculated by the computing module, where the tunnel configuration message sent by the controller to the first node carries the next
  • the tunnel information is used to indicate the established tunnel to indicate that the first node uses the established tunnel to communicate with the second node.
  • the controller calculates the cross-domain LSP tunnel based on the network topology, where the network topology includes the already established tunnel, and the controller may calculate the cross-domain LSP tunnel based on the already established tunnel in the network. Specifically, the controller learns, according to the network topology, that the cross-domain LSP tunnel to be calculated passes through the first node and the second node, and the already established tunnel is established between the first node and the second node, and the controller directly The tunnel between the first node and the second node is determined by using the already established tunnel, instead of calculating the tunnel between the first node and the second node node by node.
  • the router sends a corresponding tunnel configuration message to the forwarding node that crosses the LSP tunnel to complete the establishment of the inter-domain LSP tunnel, where the tunnel configuration is sent to the first node.
  • the message carries the next hop tunnel information, where the next hop tunnel information is used to indicate the established tunnel, to indicate that the first node establishes a communication connection with the second node by using the established tunnel, instead of requiring the same as in the prior art.
  • the forwarding connection between the first node and the second node can be implemented by each forwarding node between the first node and the second node, so that the signaling overhead of the controller can be reduced.
  • the controller calculates the cross-domain LSP tunnel by using the established tunnel in the network, which can effectively reduce the computing load of the controller.
  • the controller does not need to send the tunnel configuration to each node passing through the inter-domain LSP tunnel, which can reduce the signaling overhead of the controller to some extent.
  • the embodiment of the present invention can complete the establishment of the cross-domain LSP tunnel on the basis of effectively reducing the computational burden and signaling overhead of the controller.
  • the first node indicates the first node and the first intermediate node.
  • the sending module 230 is configured to send the corresponding tunnel configuration message to the first node, the first intermediate node, and the tail node by using the NETCONF protocol or the BGP protocol.
  • the sending module 230 is specifically configured to send a first tunnel configuration message to the first node, where the first tunnel configuration message carries the following information: an ingress tunnel type, an outbound label, and a next hop node. IP address;
  • the sending module 230 is specifically configured to send a second tunnel configuration message to the first intermediate node, where the second tunnel configuration message carries the following information: a transit tunnel type, an inbound label, an outgoing label, and an IP address of a next hop node.
  • An ingress label of an intermediate node is the same as an egress label of a previous hop node of the first intermediate node;
  • the sending module 230 is specifically configured to send a third tunnel configuration message to the tail node, where the third tunnel configuration message carries the following information: an egress tunnel type, an ingress label, an ingress label of the tail node, and a previous hop node of the tail node.
  • the outgoing labels are the same.
  • the tunnel configuration message sent by the sending module 230 to the first node, the first intermediate node, and the tail node further carries the tunnel name of the first cross-domain LSP tunnel;
  • the calculating module 220 is further configured to: calculate, according to the tunnel establishment request, a second cross-domain LSP tunnel based on the network topology, where the node that the second cross-domain LSP tunnel passes includes the first node, the second intermediate node, and the tail node, The second intermediate node is not identical to the first intermediate node;
  • the sending module 230 is further configured to send the second cross to the first node, the second intermediate node, and the tail node.
  • the tunnel configuration message of the tunnel name of the domain LSP tunnel is used to indicate that the first node, the second intermediate node, and the tail node establish the second cross-domain LSP tunnel calculated by the computing module.
  • a controller according to an embodiment of the present invention may correspond to a controller in a method of determining a cross-domain LSP tunnel of an embodiment of the present invention, and the above-described and other operations and/or functions of respective modules in the controller are respectively implemented
  • the corresponding processes of the respective methods in FIG. 2, FIG. 3 and FIG. 5 are not described herein again for the sake of brevity.
  • FIG. 7 is a schematic block diagram of a network device 300 according to an embodiment of the present invention.
  • the network device 300 includes:
  • the receiving module 310 is configured to receive, by the controller, a tunnel configuration message, which is used to indicate the establishment of the cross-domain label switched path LSP tunnel, where the tunnel configuration message carries next hop tunnel information, where the next hop tunnel information is used to indicate the network device.
  • a tunnel configuration message which is used to indicate the establishment of the cross-domain label switched path LSP tunnel
  • the tunnel configuration message carries next hop tunnel information, where the next hop tunnel information is used to indicate the network device.
  • the establishing module 320 is configured to establish a communication connection with the second network device by using the established tunnel according to the tunnel configuration message received by the receiving module.
  • the cross-domain LSP tunnel is established through the tunnel already established in the network, which can effectively reduce the burden of the controller computing, and can also reduce the overhead of signaling between the controller and the network device.
  • the network device 300 is the first node of the inter-area LSP tunnel, and the tunnel configuration message received by the receiving module 310 further carries the following information: the ingress tunnel type, the outbound label, and the next hop.
  • the IP address of the node, the next hop node is the second network device; or
  • the network device 300 is an intermediate node of the inter-area LSP tunnel, and the tunnel configuration message received by the receiving module 310 further carries the following information: a transit tunnel type, an inbound label, an outgoing label, and an IP address of a next hop node.
  • the hop node is the second network device, and the ingress label of the network device 300 is the same as the egress label of the previous hop node of the network device 300.
  • the network device 300 determines the established tunnel according to the next hop tunnel information according to the tunnel configuration message sent by the controller, and allocates a tunnel ID for the established tunnel, and generates a transfer. Publish the item.
  • the forwarding entry includes the tunnel destination IP address, the outgoing label, the IP address of the next hop node, and the next hop tunnel ID.
  • the forwarding entry includes the tunnel destination IP address, the ingress label, the outbound label, the IP address of the next hop node, and the next hop tunnel ID.
  • the forwarding entry includes the tunnel destination IP address and the ingress label.
  • the network device 300 may correspond to the first node and/or the intermediate node in the method for determining the cross-domain LSP tunnel of the embodiment of the present invention, and the foregoing and other operations of the respective modules in the network device 300
  • the detailed description of the respective processes in FIG. 2, FIG. 3 and FIG. 5 will not be repeated here.
  • FIG. 8 shows another schematic block diagram of a controller 400 provided by an embodiment of the present invention.
  • the controller 400 includes a processor 410, a memory 420, a bus system 430, a receiver 440, and a transmitter 450.
  • the processor 410, the memory 420, the receiver 440, and the transmitter 450 are connected by a bus system 430 for storing instructions for executing instructions stored in the memory 420 to control the receiver 440 to receive.
  • Signal and control transmitter 450 to send a signal.
  • the processor 410 is configured to: acquire a tunnel establishment request, where the tunnel establishment request is used to request to establish a label switched path LSP tunnel between the first node and the tail node, where the first node and the tail node belong to different domains; according to the tunnel Establishing a request, and calculating a first cross-domain LSP tunnel based on the network topology, where the node that the first cross-domain LSP tunnel passes includes the first node, the first intermediate node, and the tail node, where the first node, the first intermediate node, and The tail An established tunnel is established between the first node and the second node in the node, and the established topology is included in the network topology.
  • the transmitter 450 is configured to send a corresponding tunnel configuration message to the first node, the first intermediate node, and the tail node, to indicate that the first node, the first intermediate node, and the tail node establish the first cross a domain LSP tunnel, where the tunnel configuration message sent by the controller to the first node carries next hop tunnel information, where the next hop tunnel information is used to indicate the established tunnel, to indicate that the first node utilizes the already The established tunnel is in communication with the second node.
  • the controller calculates the cross-domain LSP tunnel by using the established tunnel in the network, which can effectively reduce the computing load of the controller.
  • the controller does not need to send the tunnel configuration to each node passing through the inter-domain LSP tunnel, which can reduce the signaling overhead of the controller to some extent.
  • the embodiment of the present invention can complete the establishment of the cross-domain LSP tunnel on the basis of effectively reducing the calculation load and signaling overhead of the controller.
  • the first node indicates the first node and the first intermediate node.
  • the transmitter 450 is configured to send the corresponding tunnel configuration message to the first node, the first intermediate node, and the tail node by using the NETCONF protocol or the BGP protocol.
  • the transmitter 450 is configured to send a first tunnel configuration message to the first node, where the first tunnel configuration message carries the following information: an ingress tunnel type, an outbound label, and a next hop node. IP address;
  • the transmitter 450 is configured to send, to the first intermediate node, a second tunnel configuration message, where the second tunnel configuration message carries the following information: a transit tunnel type, an inbound label, an outgoing label, and an IP address of a next hop node, where the first The ingress label of the intermediate node is the same as the egress label of the previous hop node of the first intermediate node;
  • the transmitter 450 is configured to send, to the tail node, a third tunnel configuration message, where the third tunnel configuration message carries the following information: an egress tunnel type, an ingress label, an ingress label of the tail node, and a previous hop node of the tail node.
  • the labels are the same.
  • the tunnel configuration message sent by the transmitter 450 to the first node, the first intermediate node, and the tail node further carries the tunnel name of the first cross-domain LSP tunnel;
  • the processor 410 is configured to calculate, according to the tunnel establishment request, a second cross-domain LSP tunnel based on the network topology, where the node that the second cross-domain LSP tunnel passes includes the first node, the second intermediate node, and the tail node, where The second intermediate node is not identical to the first intermediate node;
  • the transmitter 450 is configured to send, to the head node, the second intermediate node, and the tail node, a tunnel configuration message that carries the tunnel name of the second cross-domain LSP tunnel, and is used to indicate the first node and the second intermediate node. Establishing the second cross-domain LSP tunnel with the tail node.
  • controller 400 may correspond to a controller in a method of determining a cross-domain LSP tunnel of an embodiment of the present invention, and may correspond to the controller 200 according to an embodiment of the present invention, and the controller 400
  • the above and other operations and/or functions of the respective modules in order to implement the respective processes of the respective methods in FIG. 2, FIG. 3 and FIG. 5 are omitted for brevity.
  • FIG. 9 shows another schematic block diagram of a network device 500 according to an embodiment of the present invention.
  • the network device 500 includes a processor 510, a memory 520, a bus system 530, a receiver 540, and a transmitter 550.
  • the processor 510, the memory 520, the receiver 540 and the transmitter 550 are connected by a bus system 530 for storing instructions for executing instructions stored in the memory 520 to control the receiver 540 to receive.
  • Signal and control transmitter 550 to send a signal.
  • the receiver 540 is configured to receive, by the controller, a tunnel configuration message, which is used to indicate to establish an inter-AS label switched path LSP tunnel, where the tunnel configuration message carries next hop tunnel information, where the next hop tunnel information is used.
  • the cross-domain LSP tunnel includes the established tunnel; the processor 510 is configured to establish a communication connection with the second network device by using the established tunnel according to the tunnel configuration message.
  • the controller calculates the cross-domain LSP tunnel by using the established tunnel in the network, which can effectively reduce the computing load of the controller.
  • the controller does not need to send the tunnel configuration to each node passing through the inter-domain LSP tunnel, which can reduce the signaling overhead of the controller to some extent.
  • the embodiment of the present invention can complete the establishment of the cross-domain LSP tunnel on the basis of effectively reducing the computational burden and signaling overhead of the controller.
  • the network device 500 is the first node of the inter-AS LSP tunnel, and the tunnel configuration message received by the network device 500 further carries the following information: the ingress tunnel type, the outgoing label, and the next hop.
  • the IP address of the node, the next hop node is the second network device; or
  • the network device 500 is an intermediate node of the inter-AS LSP tunnel.
  • the tunnel configuration message received by the network device 500 further carries the following information: a transit tunnel type, an inbound label, an outgoing label, and an IP address of a next hop node.
  • the hop node is the second network device, and the ingress label of the network device 500 is the same as the egress label of the previous hop node of the network device 500.
  • the network device 500 may correspond to a first node or an intermediate node in a method for determining a cross-domain LSP tunnel according to an embodiment of the present invention, and may correspond to the network device 300 according to an embodiment of the present invention, and
  • the above and other operations and/or functions of the respective modules in the network device 500 are respectively implemented in order to implement the respective processes of the respective methods in FIG. 2, FIG. 3 and FIG. 5, and are not described herein again for brevity.
  • FIG. 10 is a schematic block diagram of a controller control system 600 according to an embodiment of the present invention.
  • the controller control system 600 includes a controller 610 and a network device 620.
  • the controller 610 is a controller 200 provided by an embodiment of the present invention.
  • the controller 400, the network device 620 is the network device 300 or the network device 500 provided by the embodiment of the present invention.
  • the controller calculates the cross-domain LSP tunnel based on the network topology, where the network topology includes the already established tunnel, and the controller may calculate the cross-domain LSP tunnel based on the already established tunnel in the network. Specifically, the controller learns, according to the network topology, that the cross-domain LSP tunnel to be calculated passes through the first node and the second node, and the established node has a tunnel between the first node and the second node, and the controller directly uses the established The tunnel determines the tunnel between the first node and the second node, rather than calculating the tunnel between the first node and the second node node by node.
  • the router sends a corresponding tunnel configuration message to the forwarding node that crosses the LSP tunnel to complete the establishment of the inter-domain LSP tunnel, where the tunnel configuration is sent to the first node.
  • the message carries the next hop tunnel information, where the next hop tunnel information is used to indicate the established tunnel, to indicate that the first node establishes a communication connection with the second node by using the established tunnel, instead of requiring the same as in the prior art.
  • the forwarding connection between the first node and the second node can be implemented by each forwarding node between the first node and the second node, so that the signaling overhead of the controller can be reduced.
  • the controller calculates the cross-domain LSP tunnel by using the established tunnel in the network, which can effectively reduce the computing load of the controller.
  • the controller does not need to send the tunnel configuration to each node passing through the inter-domain LSP tunnel, which can reduce the signaling overhead of the controller to some extent.
  • the embodiment of the present invention can complete the establishment of the cross-domain LSP tunnel on the basis of effectively reducing the computational burden and signaling overhead of the controller.
  • the size of the sequence numbers of the above processes does not mean the order of execution, and the order of execution of each process should be determined by its function and internal logic, and should not be directed to the embodiments of the present invention.
  • the implementation process constitutes any limitation.
  • the disclosed systems, devices, and methods may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the functions may be stored in a computer readable storage medium if implemented in the form of a software functional unit and sold or used as a standalone product.
  • the technical solution of the present invention which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including
  • the instructions are used to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present invention.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like. .

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 concerne un procédé, un appareil et un système de détermination de tunnel de chemin à commutation d'étiquettes (LSP) entre systèmes autonomes (AS). Le procédé consiste : à acquérir une requête d'établissement de tunnel demandant d'établir un tunnel LSP entre un nœud d'entrée et un nœud de sortie, le nœud d'entrée et le nœud de sortie appartenant à différents systèmes autonomes (AS) ; à calculer, sur la base d'une topologie de réseau, un premier tunnel LSP inter-AS passant par des nœuds comprenant le nœud d'entrée, des nœuds intermédiaires et le nœud de sortie, un premier nœud et un deuxième nœud inclus dans lesdits nœuds ayant un tunnel établi entre eux, et la topologie de réseau comprenant le tunnel établi ; et à envoyer à chaque nœud des messages de configuration de tunnel correspondants utilisés pour donner l'instruction d'établir le premier tunnel LSP inter-AS, le message de configuration de tunnel envoyé par un contrôleur au premier nœud contenant des informations de tunnel de bond suivant utilisées pour indiquer le tunnel établi. La présente invention permet l'établissement d'un tunnel LSP inter-AS tout en réduisant efficacement la charge de calcul de routage et le coût de signalisation d'un contrôleur.
PCT/CN2017/084377 2016-06-08 2017-05-15 Procédé, appareil et système de détermination de tunnel de chemin à commutation d'étiquettes entre systèmes autonomes Ceased WO2017211164A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610402567.0A CN107483338A (zh) 2016-06-08 2016-06-08 一种确定跨域标签交换路径隧道的方法、设备和系统
CN201610402567.0 2016-06-08

Publications (1)

Publication Number Publication Date
WO2017211164A1 true WO2017211164A1 (fr) 2017-12-14

Family

ID=60577586

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/084377 Ceased WO2017211164A1 (fr) 2016-06-08 2017-05-15 Procédé, appareil et système de détermination de tunnel de chemin à commutation d'étiquettes entre systèmes autonomes

Country Status (2)

Country Link
CN (1) CN107483338A (fr)
WO (1) WO2017211164A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110943923A (zh) * 2018-09-21 2020-03-31 中兴通讯股份有限公司 一种lsp建立方法、装置、设备和计算机存储介质

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111131038B (zh) * 2018-10-31 2022-04-19 中国电信股份有限公司 跨域报文转发方法、系统以及存储系统
CN109639600B (zh) * 2019-01-25 2022-07-01 新华三技术有限公司 一种隧道限速的方法及装置
CN111600737B (zh) * 2019-02-21 2021-12-24 华为技术有限公司 一种拓扑信息收集方法及网络设备
CN110838965B (zh) * 2019-09-25 2022-02-11 北京华为数字技术有限公司 一种隧道建立方法以及接收节点
CN112039774B (zh) * 2020-07-27 2022-01-07 深圳市风云实业有限公司 一种隧道与sr相结合的网络流量调优方法
CN115037681A (zh) * 2021-03-04 2022-09-09 国家电网有限公司信息通信分公司 一种以ip地址为显式路径的标签转发方法和系统
CN118368318A (zh) * 2023-01-18 2024-07-19 华为技术有限公司 连接建立方法、控制器、节点、通信系统和存储介质
CN120455203A (zh) * 2024-02-08 2025-08-08 华为技术有限公司 一种网络互联的方法及装置、通信系统

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102065006A (zh) * 2010-12-01 2011-05-18 电子科技大学 一种跨域标签交换路径域间失效的恢复方法
CN102611607A (zh) * 2011-01-21 2012-07-25 中兴通讯股份有限公司 域间链路信息的处理方法及路径计算单元
US8422514B1 (en) * 2010-02-09 2013-04-16 Juniper Networks, Inc. Dynamic configuration of cross-domain pseudowires
US9246838B1 (en) * 2011-05-27 2016-01-26 Juniper Networks, Inc. Label switched path setup using fast reroute bypass tunnel

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101478474B (zh) * 2008-12-19 2011-06-15 华为技术有限公司 跨域建立mpls te lsp的方法、装置和系统
CN101945035A (zh) * 2009-07-10 2011-01-12 中兴通讯股份有限公司 基于路径计算元的跨域路径恢复方法和装置
CN105591862A (zh) * 2014-10-20 2016-05-18 中兴通讯股份有限公司 一种隧道算路重优化的方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8422514B1 (en) * 2010-02-09 2013-04-16 Juniper Networks, Inc. Dynamic configuration of cross-domain pseudowires
CN102065006A (zh) * 2010-12-01 2011-05-18 电子科技大学 一种跨域标签交换路径域间失效的恢复方法
CN102611607A (zh) * 2011-01-21 2012-07-25 中兴通讯股份有限公司 域间链路信息的处理方法及路径计算单元
US9246838B1 (en) * 2011-05-27 2016-01-26 Juniper Networks, Inc. Label switched path setup using fast reroute bypass tunnel

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
FANG, JUN: "Solution of Networks Based on L3 MPLS VPN", COMPUTER AND INFORMATION TECHNOLOGY, vol. 16, no. 03, 30 June 2008 (2008-06-30), pages 36 - 39 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110943923A (zh) * 2018-09-21 2020-03-31 中兴通讯股份有限公司 一种lsp建立方法、装置、设备和计算机存储介质
CN110943923B (zh) * 2018-09-21 2023-09-12 中兴通讯股份有限公司 一种lsp建立方法、装置、设备和计算机存储介质

Also Published As

Publication number Publication date
CN107483338A (zh) 2017-12-15

Similar Documents

Publication Publication Date Title
US11431526B2 (en) Deterministic forwarding across L2 and L3 networks
CN111865796B (zh) 用于网络业务的路径计算单元中央控制器（pcecc）
US20160006614A1 (en) Source Routing Using Path Computation Elements
US10484203B2 (en) Method for implementing communication between NVO3 network and MPLS network, and apparatus
WO2017211164A1 (fr) Procédé, appareil et système de détermination de tunnel de chemin à commutation d'étiquettes entre systèmes autonomes
US9998368B2 (en) Zone routing system
CN106656781B (zh) 一种报文传输的方法、装置和系统
CN110870261B (zh) Pecp分段路由路径分段标签绑定扩展
EP3148131B1 (fr) Procédé et appareil de libération d'informations d'adresse
EP3200402A1 (fr) Procédé d'obtention d'informations sr, et procédé d'établissement de réseau sr
WO2021196717A1 (fr) Procédé et appareil de transmission de trafic de multidiffusion, nœud de communication et support de stockage
US9210075B2 (en) Method and apparatus for managing end-to-end consistency of bi-directional MPLS-TP tunnels via in-band communication channel (G-ACH) protocol
US10374831B2 (en) Stitching multi-domain LSPs in hierarchical SDN architecture
EP2135393B1 (fr) Construction d'un arbre recouvrant sur ethernet
US20180324081A1 (en) X Channel to Zone in Zone Routing
CN105594167A (zh) 转发报文的方法、控制器、转发设备和网络系统
US20080198751A1 (en) Method for implementing cross-domain constraint routing
US11303549B2 (en) Segmented traceroute for segment routing traffic engineering
Martini et al. Dynamic Placement of Multi-Segment Pseudowires
CN103650453B (zh) 在路径计算单元通信协议中通信的方法以及网络装置
CN102904808B (zh) 跨资源预留协议流量工程标签交换路径的建立方法及系统
CN117749687A (zh) 位索引路由表建立方法、网络设备及存储介质
Liu et al. Internet Engineering Task Force H. Chen Internet-Draft Huawei Technologies Intended status: Standards Track N. So Expires: August 14, 2014 Tata Communications
Martini et al. RFC 7267: Dynamic Placement of Multi-Segment Pseudowires

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

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

Country of ref document: EP

Kind code of ref document: A1