Correlating label switched paths of a pseudowire

This invention relates generally to the field of communication networks and more specifically to correlating label switched paths of a pseudowire.

A pseudowire (PW) is an emulation of a native service over a Packet Switched Network (PSN). The pseudowire emulates the operation of a transparent wire that carries the native service, and may be used to carry packets from a network that uses the native service, across a Packet Switched Network, to another network that uses the native service.

In accordance with the present invention, disadvantages and problems associated with previous techniques for using pseudowires may be reduced or eliminated.

According to one embodiment of the present invention, correlating label switched paths of a pseudowire includes receiving a first message at a second label switching router. The first message is sent from a first label switching router and includes a pseudowire identifier and a first label switched path identifier. The pseudowire identifier identifies a pseudowire, and the first label switched path identifier identifies a first label switched path that implements the pseudowire. A second message is sent from the second label switching router to the first label switching router. The second message comprises the pseudowire identifier and a second label switched path identifier. The second label switched path identifier identifies a second label switched path that implements the pseudowire.

Certain embodiments of the invention may provide one or more technical advantages. A technical advantage of one embodiment may be that a message includes a pseudowire-to-label switched path (PW-to-LSP) mapping that maps a pseudowire to paths that implement the pseudowire. The message is sent to nodes of the pseudowire to the inform the nodes of the paths that implement the pseudowire. If one node detects a fault on one path, the node may use the other path to send a failure notification to the other node.

Certain embodiments of the invention may include none, some, or all of the above technical advantages. One or more other technical advantages may be readily apparent to one skilled in the art from the figures, descriptions, and claims included herein.

For a more complete understanding of the present invention and its features and advantages, reference is now made to the following description, taken in conjunction with the accompanying drawings, in which:

FIG. 1 illustrates an example of a system for correlating label switched paths of a pseudowire;

FIG. 2 illustrates an example of a pseudowire implemented by paths of the system of FIG. 1 ; and

FIG. 3 illustrates an example of a method for correlating label switched paths of a pseudowire.

Embodiments of the present invention and its advantages are best understood by referring to FIGS. 1 through 3 of the drawings, like numerals being used for like and corresponding parts of the various drawings.

FIG. 1 illustrates a system 10 for correlating label switched paths of a pseudowire. In the embodiment, a pseudowire 14 that includes nodes 24 is implemented by paths 20 , such as label switched paths. A message 30 includes a pseudowire-to-label switched path (PW-to-LSP) mapping that maps pseudowire 14 to paths 20 . Message 30 is sent to nodes 24 to inform nodes 24 of paths 20 that implement pseudowire 14 . A node 24 may use a path 20 to send a notification, such as a failure notification, to another node 24 .

In one embodiment, system 10 communicates information through signals such as optical signals (for example, Synchronous Transport Signals (STSs)). As an example, an optical signal may have a data rate of 10, 20, 40, or over 40 gigabits per second. Information may include voice, data, audio, video, multimedia, control, signaling, and/or other information.

In the illustrated embodiment, system 10 includes Layer 1 or Layer 2 (Layer 1/2) networks 16 (networks 16 a and 16 b ) and a packet switched network (PSN) 18 . Layer 1/2 network 16 uses a native service that implements Layer 1/2 protocols, such as Asynchronous Transfer Mode (ATM), Frame Relay, Ethernet, Time-Division Multiplexing (TDM), synchronous optical networking/synchronous digital hierarchy (SONET/SDH), and/or other suitable Layer 1/2 protocols. Layer 1/2 networks 16 a and 16 b include clients 22 a and 22 c . A client 22 communicates using Layer 1/2 protocols.

Packet switched network (PSN) 18 implements Layer 3 or higher protocols such as MultiProtocol Label Switching (MPLS), Internet Protocol (IP), or Layer 2 Tunneling Protocol (L2TP). Packet switched network 18 includes nodes 24 a , 24 b , and 24 c . Node 24 represents any suitable network element such as a Multi-Protocol Label Switching (MPLS) MPLS router, or label switching router.

A path 20 , or circuit or tunnel, comprises a sequence of nodes 24 that communicate packets. Path 20 may be a label switched path (LSP). Packets travel from an ingress node 24 a , through zero, one, or more intermediate nodes 24 b , to an egress node 24 c . In the illustrated example, path 20 a goes from ingress node 24 a through intermediate node 24 b to egress node 24 c . Path 20 b goes from ingress node 24 c through intermediate node 24 b to egress node 24 a . A path identifier identifies path 20 . In the illustrated example, path identifier LSP 1 identifies path 20 a , and path identifier LSP 2 identifies path 20 b . A node 24 may manage the pseudowire parameters, such as the pseudowire identifiers and labels, as well as the source, destination, and path identifiers.

To route a packet along path 20 a , ingress node 24 a attaches a label to a packet and sends the packet to a next hop node according to a forwarding entry for path 20 a . Intermediate node 24 b uses the label from node 24 a to look up another forwarding entry. Intermediate node 24 b replaces the label from node 24 a with a new label and sends the packet to a next hop node according to the forwarding entry. Egress node 24 c uses the label from node 24 b to look up a forwarding entry. The forwarding entry indicates that node 24 c is the egress node.

Pseudowire 14 is implemented by paths 20 a and 20 b . Pseudowire 14 emulates Layer 1/2 services over packet switched network 18 , and allows for Layer 1/2 packets to be communicated over packet switched network 18 . Pseudowire acts like a Layer 1/2 wire and may be used to forward Layer 1/2 packets from one Layer 1/2 network 16 a to another Layer 1/2 network 16 b over packet switched network 18 .

A particular pseudowire 14 may be used to communicate packets to particular clients. For example, pseudowire 14 a communicates between clients 22 a , and pseudowire 14 b communicates between clients 22 b.

A pseudowire identifier identifies a particular pseudowire 14 . For example, pseudowire identifier PW 1 identifies pseudowire 14 a , and pseudowire identifier PW 2 identifies pseudowire 14 b . Pseudowire labels are allocated to a particular pseudowire 14 during setup of the pseudowire 14 . In one embodiment, one label PWL 1 may be given to a pseudowire PW 1 in one direction, and another label PWL 2 may be given to the same pseudowire PW 1 in the other direction.

Message 30 communicates information about pseudowire 14 to nodes 24 of path 20 . In the illustrated embodiment, message 30 includes a pseudowire-to-label switched path (PW-to-LSP) mapping 34 . PW-to-LSP mapping 34 indicates paths 20 that implement pseudowire 14 . PW-to-LSP mapping 34 includes a pseudowire identifier 36 , a pseudowire label 38 , and a label switched path identifier 42 .

In the illustrated embodiment, node 24 a sends message 30 a to node 24 c , and node 24 c sends message 30 b to node 24 a . PW-to-LSP mapping 34 a informs node 24 c of path 20 a that implements pseudowire 14 a , and PW-to-LSP mapping 34 b informs node 24 a of path 20 b that implements pseudowire 14 a.

Specifically, pseudowire identifier 36 a includes pseudowire identifier PW 1 identifying pseudowire 14 a , pseudowire label 38 a includes label PWL 1 identifying pseudowire 14 a in one direction, and label switched path identifier 42 a includes path identifier LSP 1 identifying path 20 a . Pseudowire identifier 36 b includes pseudowire identifier PW 1 identifying pseudowire 14 a , pseudowire label 38 b includes label PWL 2 identifying pseudowire 14 a in the other direction, and label switched path identifier 42 b includes path identifier LSP 2 identifying path 20 b.

Message 30 represents any suitable message, for example, a Label Distribution Protocol (LDP) a label mapping message used to set up a pseudowire 14 or an LDP notification message used to update pseudowire 14 . PW-to-LSP mapping 34 may be communicated in any suitable portion of message 30 , for example, a type-length-value (TLV) element.

PW-to-LSP mapping 34 allows ingress and egress nodes 24 a and 24 c to know paths 20 used to form pseudowires 14 . Accordingly, in the event that a path 20 a of a pseudowire 14 fails, egress node 24 c can notify ingress node 24 a using the other path 20 b . Using the other path 20 b may be more efficient since path 20 b does not require IP forwarding.

A component of system 10 may include an interface, logic, memory, and/or other suitable element. An interface receives input, sends output, processes the input and/or output, and/or performs other suitable operation. An interface may comprise hardware and/or software.

Logic performs the operations of the component, for example, executes instructions to generate output from input. Logic may include hardware, software, and/or other logic, and may be embodied as a computer-readable storage medium. Certain logic, such as a processor, may manage the operation of a component. Examples of a processor include one or more computers, one or more microprocessors, one or more applications, and/or other logic.

A memory stores information. A memory may comprise computer memory (for example, Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (for example, a hard disk), removable storage media (for example, a Compact Disk (CD) or a Digital Video Disk (DVD)), database and/or network storage (for example, a server), and/or other computer-readable medium.

Modifications, additions, or omissions may be made to system 10 without departing from the scope of the invention. The components of network system 10 may be integrated or separated according to particular needs. Moreover, the operations of network system 10 may be performed by more, fewer, or other devices. Additionally, operations of network system 10 may be performed using any suitable logic. As used in this document, “each” refers to each member of a set or each member of a subset of a set.

FIG. 2 illustrates an example of pseudowire 14 implemented by paths 20 a and 20 b of system 10 of FIG. 1 . Pseudowire 14 communicates data traffic 54 and bidirectional forwarding detection (BFD) control packets 58 . Bidirectional forwarding detection detects a data plane failure in the forward path of a label switched path 20 . To detect a data plane failure of path 20 a , ingress node 24 a sends one or more failure detection packets to egress node 24 c over path 20 a . The failure detection packets may be BFD control packets that are sent at a configurable rate.

If egress node 24 c does not receive the packets in an expected manner, path 20 a is declared to be faulty. An unexpected manner indicating failure may occur if, for example, the packets do not have the expected contents, a particular number of packets fails to arrive, and/or the packets are late. Egress node 24 c sends a failure notification on path 20 b indicating that there is a failure of path 20 a.

FIG. 3 illustrates one embodiment of a method for correlating label switched paths of a pseudowire. According to one embodiment, the method may be performed by system 10 .

Steps 110 through 126 describes setup of path 20 a according to, for example, Resource Reservation Protocol (RSVP). Node 24 a initiates setup of path 20 a from node 24 a to node 24 c at step 110 . Node 24 a determines that path 20 a includes node 24 a , node 20 b , and node 24 c . A BFD instance is allocated. Node 24 a sends a reservation request to node 24 b at step 114 . Node 24 b processes the reservation request, and forwards the reservation request to node 24 c at step 118 .

Node 24 c selects label L 2 for the link from node 24 c to node 24 b , and sends the label L 2 to node 24 b in a reservation response at step 122 . Node 24 b selects a label L 1 for the link from node 24 b to node 24 a , and sends the label L 1 to node 24 a in a reservation response at step 126 .

Steps 130 through 146 describe setup of path 20 b from node 24 c to node 24 a . Node 24 c initiates setup of path 20 b from node 24 c to node 24 a at step 130 . Node 24 c determines that path 20 b includes node 24 c , node 20 b , and node 24 a . A BFD instance is allocated. Node 24 c sends a reservation request to node 24 b at step 134 . Node 24 b processes the reservation request, and forwards the reservation request to node 24 a at step 138 .

Node 24 a selects label L 3 for the link from node 24 a to node 24 b , and sends the label L 3 to node 24 b in a reservation response at step 142 . Node 24 b selects a label L 4 for the link from node 24 b to node 24 c , and sends the label L 4 to node 24 c in a reservation response at step 146 .

Steps 150 and 154 describe setup of pseudowire PW 1 according to, for example, LDP. The setup involves notification of nodes 24 a and 24 c of paths LSP 1 and LSP 2 that implement pseudowire PW 1 . The notification may also be performed during an update process. Node 24 a sends PW-to-LSP mapping 34 a to node 24 c at step 150 . Node 24 a selects path LSP 1 for pseudowire PW 1 . In the illustrated embodiment, PW-to-LSP mapping 34 a includes pseudowire identifier PW 1 , pseudowire label PWL 1 , and LSP identifier LSP 1 .

Node 24 c sends PW-to-LSP mapping 34 b to node 24 a at step 154 . Node 24 c selects path LSP 2 for pseudowire PW 1 . PW-to-LSP mapping 34 b includes pseudowire identifier PW 1 , pseudowire label PWL 2 , and LSP identifier LSP 2 .

Steps 160 through 172 describe communication of data between nodes 24 a and 24 c . Node 24 a sends data packets designated for clients C 1 to node 24 b at step 160 . The data packets include pseudowire label PWL 1 and label L 1 . Node 24 b sends data packets to node 24 c at step 164 . The data packets include pseudowire label PWL 1 and label L 2 . Node 24 c removes the labels and forwards the packets to client C 1 . Node 24 c sends data packets to node 24 b at step 168 , and node 24 b sends the data packets to node 24 a at step 172 .

Steps 174 through 188 describe performance of bidirectional forwarding detection. The BFD instance is configured at step 174 with transmit and receive labels that allow the BFD detection packets and failure notifications to travel over paths 20 a and 20 b.

Node 24 a sends one or more BFD detection packets to node 24 c along path 20 a at steps 180 and 182 . Node 24 c detects a failure at step 184 . Node 24 c sends a BFD failure notification along path 20 b at steps 186 and 188 . The failure notification indicates that a failure of path 20 a has been detected.

Certain embodiments of the invention may provide one or more technical advantages. A technical advantage of one embodiment may be that a message includes a pseudowire-to-label switched path (PW-to-LSP) mapping that maps a pseudowire to paths that implement the pseudowire. The message is sent to nodes of the pseudowire to the inform the node of the paths that implement the pseudowire. A node may use a path to send a notification, such as a failure notification, to another node.

While this disclosure has been described in terms of certain embodiments and generally associated methods, alterations and permutations of the embodiments and methods will be apparent to those skilled in the art. Accordingly, the above description of example embodiments does not constrain this disclosure. Other changes, substitutions, and alterations are also possible without departing from the spirit and scope of this disclosure, as defined by the following claims.