# US 2012/0250583 A1 · Multi-Protocol Label Switching Multi-Topology Support

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2012/0250583 A1
- Document ID: US20120250583A1
- Status: Published application
- Kind: A1
- Application number: 13/523,564
- Filed: 2012-06-14
- Published: 2012-10-04
- Earliest claimed: 2008-04-07
- Assignees: Futurewei Technologies, Inc.
- Inventors: Huaimo Chen; Qianglin Quintin Zhao; Raveendra Torvi; Hua Autumn Liu
- Web page: https://patentgrep.com/patent/US20120250583A1

## CPC

- H04L 45/12: Shortest path evaluation
- H04L 45/02: Topology update or discovery
- H04L 45/50: using label swapping, e.g. multi-protocol label switch [MPLS]
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A network component comprising at least one processor configured to implement a method comprising receiving a packet, determining whether the packet comprises a topology label, and adding the topology label to the packet if the packet does not comprise the topology label. Included is a method comprising routing a plurality of packets corresponding to a plurality of forwarding equivalence classes (FECs) over a plurality of network topologies using a topology label and plurality of forwarding labels for each network topology. Also included is a network comprising a plurality of nodes in communication with each other and having a plurality of network topologies, wherein at least some of the nodes are configured to route data packets for a plurality of FECs along a path in each network topology using a topology label corresponding to each network topology and an inner label corresponding to each FEC.

## Claims

### Claim 1

A network component comprising:
at least one processor configured to:
receive a packet;
determine through classification of the packet a network topology and a forwarding equivalence class (FEC) corresponding to the packet;
attach to the packet both a topology label and an inner next hop label, wherein the topology label correlates to the network topology and the inner next hop label correlates to the FEC; and
forward the packet to a node.

### Claim 2 (depends on 1)

The network component of claim 1, wherein the topology label is located on top of the inner next hop label to enable the topology label to be detected prior to the inner next hop label upon reception of the packet at the node.

### Claim 3 (depends on 1)

The network component of claim 1, wherein the processor is further configured to:
initiate a session between a plurality of nodes;
negotiate multi-topology (MT) capability between the nodes, and
exchange topology information or label mapping information between at least some of the nodes.

### Claim 4 (depends on 3)

The network component of claim 3, wherein the session is initiated using an initialization session establishment message comprising a first MT capability type length value (TLV), an initialization message header, an initialization message length field, an initialization message Identification (ID) field, and a common session parameters TLV, wherein the MT capability is negotiated using the MT capability TLV.

### Claim 5 (depends on 3)

The network component of claim 3, wherein the MT capability is negotiated using a capability message comprising a capability header, a capability message length, a capability message ID field, and a second MT capability TLV.

### Claim 6 (depends on 5)

The network component of claim 5, wherein the second MT capability TLV is substantially similar to a first MT capability TLV, wherein the first MT capability TLV is contained within an initialization session establishment message, and wherein both the first MT capability TLV and the second MT capability TLV comprise an unknown (U) bit, a forward unknown (F) bit, a TLV code point, a TLV length, a state (S) bit, and a capability data portion.

### Claim 7 (depends on 3)

The network component of claim 3, wherein exchanging topology or label mapping information comprises requesting topology or label mapping information by transmitting a label request message comprising a label request header, a label request message ID, and a FEC TLV.

### Claim 8 (depends on 7)

The network component of claim 7, wherein exchanging topology information further comprises receiving a label mapping message comprising a topology information or a label mapping information, wherein the label mapping message further comprises a label mapping header, a label mapping message length, a label mapping message ID, the FEC TLV, a label TLV, and a first label request message ID TLV.

### Claim 9 (depends on 7)

The network component of claim 7, wherein exchanging topology or label mapping information further comprises aborting the request for topology or label mapping information by transmitting a label abort message comprising a label abort request header, a label abort message length, a label abort message ID, the FEC TLV, and a label request message ID TLV, wherein the label request message ID TLV comprises the label request message ID.

### Claim 10 (depends on 8)

The network component of claim 8, wherein exchanging topology or label mapping information further comprises:
determining whether the first label request message ID TLV comprises the label request message ID;
processing the label mapping message if the first label request message ID TLV comprises the label request message ID, wherein processing the label mapping message includes storing the topology information or the label mapping information in a memory; and
ignoring the label mapping message if the first request message ID TLV does not comprise the label request message ID.

### Claim 11 (depends on 10)

The network component of claim 10, wherein exchanging topology or label mapping information further comprises:
receiving a label withdraw message comprising a label withdraw header, a label withdraw message length, a label withdraw message ID, the FEC TLV, and a second label mapping message ID TLV;
determining whether the second label mapping message ID TLV comprises the label mapping message ID;
processing the label withdraw message if the second label mapping message ID TLV comprises the label mapping message ID; and
ignoring the label withdraw message if the second label mapping message ID TLV does not comprise the label mapping message ID,
wherein the second label mapping message ID TLV comprises the label mapping message ID, and
wherein processing the label withdraw message includes removing the topology information or the label mapping information from the memory.

### Claim 12

A network comprising:
a plurality of nodes in communication with each other and having a plurality of network topologies,
wherein at least some of the nodes are configured to route data packets for a plurality of Forwarding Equivalence Classes (FECs) along a path in each network topology using a topology label corresponding to each network topology and an inner label corresponding to each FEC, and
wherein the nodes comprise:
an ingress node configured to add the topology label and the inner label to the packet;
a transit node configured to replace the inner label and keep the topology label in the packet; and
an egress node configured to remove the inner label or both the inner label and the topology label from the packet.

### Claim 13 (depends on 12)

The network of claim 12, wherein the network topologies are supported in a Multiprotocol Label Switching (MPLS) network or a generalized MPLS (GMPLS) network.

### Claim 14

A method comprising:
receiving a packet;
determining through classification of the packet a network topology and a forwarding equivalence class (FEC) corresponding to the packet;
attaching to the packet both a topology label and an inner next hop label, wherein the topology label correlates to the network topology and the inner next hop label correlates to the FEC; and
forwarding the packet to a node.

### Claim 15 (depends on 14)

The method of claim 14, wherein the topology label is located on top of the inner next hop label to enable the topology label to be detected prior to the inner next hop label upon reception of the packet at the node.

### Claim 16 (depends on 14)

The method of claim 14 further comprising:
initiating a session between a plurality of nodes;
negotiating multi-topology (MT) capability between the nodes, and
exchanging topology information or label mapping information between at least some of the nodes.

### Claim 17 (depends on 16)

The method of claim 16, wherein the session is initiated using an initialization session establishment message comprising a first MT capability type length value (TLV), an initialization message header, an initialization message length field, an initialization message Identification (ID) field, and a common session parameters TLV, wherein the MT capability is negotiated using the MT capability TLV.

### Claim 18 (depends on 16)

The method of claim 16, wherein the MT capability is negotiated using a capability message comprising a capability header, a capability message length, a capability message ID field, and a second MT capability TLV.

### Claim 19 (depends on 18)

The method of claim 18, wherein the second MT capability TLV is substantially similar to a first MT capability TLV, wherein the first MT capability TLV is contained within an initialization session establishment message, and wherein both the first MT capability TLV and the second MT capability TLV comprise an unknown (U) bit, a forward unknown (F) bit, a TLV code point, a TLV length, a state (S) bit, and a capability data portion.

### Claim 20 (depends on 16)

The method of claim 16, wherein exchanging topology or label mapping information comprises requesting topology or label mapping information by transmitting a label request message comprising a label request header, a label request message ID, and a FEC TLV.
