# US 2010/0165883 A1 · Ring topology discovery mechanism

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

- Number: US 2010/0165883 A1
- Document ID: US20100165883A1
- Status: Published application
- Kind: A1
- Application number: 12/347,362
- Filed: 2008-12-31
- Published: 2010-07-01
- Earliest claimed: 2008-12-31
- Assignees: Nortel Networks Limited
- Inventors: Marc HOLNESS; Bashar ABDULLAH; Marc Andre ROCHON
- Web page: https://patentgrep.com/patent/US20100165883A1

## CPC

- H04L 12/437: Ring fault isolation or reconfiguration {(for SDH/SONET ring networks H04J3/085)}
- H04L 45/28: using route fault recovery
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A method automatically discovers a topology of a communication network ring. The ring includes a plurality of nodes. Each node includes a first port and a second port. A ring topology request or a response to the ring topology request is received from at least one node on the ring. The ring topology request or the response to the ring topology request includes an identification of the at least one node and an indication of a hop count needed to reach the at least one node. The ring topology request or the response to the ring topology request is forwarded to at least one neighboring node on the ring through the first port. The topology is determined based on the identification of the at least one node, the hop count, and an identification of the first port.

## Claims

### Claim 1

A method for automatically discovering a topology of a communication network ring, the ring including a plurality of nodes, each node including a first port and a second port, the method comprising:
receiving at least one of a ring topology request and a response to the ring topology request from at least one node on the ring, the at least one of the ring topology request and the response to the ring topology request including an identification of the at least one node and an indication of a hop count needed to reach the at least one node;
forwarding the at least one of the ring topology request and the response to the ring topology request to at least one neighboring node on the ring through the first port; and
determining the topology based on the identification of the at least one node, the hop count, and an identification of the first port.

### Claim 2 (depends on 1)

The method of claim 1, wherein the ring topology request is a Ring Automated Protection Switching message, the Ring Automated Protection Switching message including a type-length-value element, the method further comprising:
receiving a ring topology request at the first port and the second port;
modifying each ring topology request by adding an identification of a receiving node to the type-length-value element and incrementing the node count; and
forwarding each modified ring topology request to the neighboring node through the other of the first port and the second port than the port on which the ring topology request was received.

### Claim 3 (depends on 1)

The method of claim 1, wherein the ring is an Ethernet ring.

### Claim 4 (depends on 1)

The method of claim 1, wherein the at least one ring topology request is a Ring Automated Protection Switching message, the method further comprises:
creating the at least one ring topology request by adding a type-length-value element to the Ring Automated Protection Switching message, the type-length-value element including a node signature for an originating node and the hop count; and
initializing the hop count.

### Claim 5 (depends on 4)

The method of claim 4, wherein the ring topology request is forwarded through the first port and the second port, and further wherein receiving at least one response to the ring topology request comprises:
receiving a response at first port and the second port, each response having been forwarded through the ring from the other of the first port and the second port from which the response was received, each response including a total node count of all the nodes in the ring and an identification of each node in the ring arranged in an order of processing.

### Claim 6 (depends on 1)

The method of claim 1, further comprising creating the ring topology request in response to detecting a failure of a link connected to the other of the first port and the second port from which the response was received the transmitting port.

### Claim 7 (depends on 1)

The method of claim 1, wherein the ring topology request is a LinkTrace message, the LinkTrace message including a time-to-live value, the method further comprising:
inserting a ring identifier into the LinkTrace message, the ring identifier being used to keep the ring topology request local to the ring;
receiving a plurality of LinkTrace responses, each LinkTrace response originated by one of the nodes of the plurality of nodes of the ring, each LinkTrace response including an identification of the originating node; and
wherein the indication of a node count needed for the ring topology request to reach the at least one responding node is a time-to-live value.

### Claim 8 (depends on 7)

The method of claim 7, wherein the node count needed for the ring topology request to reach the at least one responding node is equal to one half of a difference between the time-to-live value of the LinkTrace message and the time-to-live value of the LinkTrace response.

### Claim 9 (depends on 1)

The method of claim 1, wherein the ring topology request is a continuity check message, the continuity check message including a listing of identifications of nodes having previously received continuity check message, the method further comprising:
receiving the ring topology request at one of the first port and the second port;
modifying the ring topology request by appending an identification of a receiving node to listing of identifications of nodes having previously received continuity check message and incrementing the node count; and
forwarding the modified ring topology request to the neighboring node through the other of the first port and the second port than the port on which the ring topology request was received.

### Claim 10 (depends on 1)

The method of claim 1, wherein the ring topology request is a continuity check message, the method further comprising:
receiving a modified ring topology request through the other of the first port and the second port than the port on which the ring topology request was transmitted, the modified ring topology request including a listing of identifications of nodes having previously received continuity check message in an order of processing and a total node count of all the node on the ring.

### Claim 11 (depends on 1)

The method of claim 1, further comprising:
populating static entries in a forwarding database table according to the topology;
receiving notice of a failed link, the notice including a source address of a node adjacent to the failed link;
using the topology and the source address of the node adjacent to the failed link to reconfigure the forwarding database table; and
forwarding data using the reconfigured forwarding database table without flooding the ring.

### Claim 12

A node for automatically discovering a topology of a communication network ring, the ring including a plurality of nodes, the node comprising:
a first port and a second port, each port operable to receive and transmit data:
at least one of the first port and the second port receiving at least one of a ring topology request and a response to the ring topology request from at least one other node on the ring, the at least one of the ring topology request and the response to the ring topology request including an identification of the at least one other node and an indication of a hop count needed to reach the at least one other node;
the other of the first port and the second port than the port on which the at least one of a ring topology request and a response to the ring topology request was received forwarding the at least one of a ring topology request and a response to the ring topology request to at least one neighboring node on the ring; and
a processor electrically connected to each port, the processor determining the topology based on the identification of the at least one node, the hop count, and an identification of the forwarding port.

### Claim 13 (depends on 12)

The node of claim 12, wherein the ring topology request is a Ring Automated Protection Switching message, the Ring Automated Protection Switching message including a type-length-value element,
each port further receives a ring topology request; and
the processor further:
modifies each ring topology request by adding an identification of a receiving node to the type-length-value element and incrementing the node count; and
forwards the modified ring topology request to the neighboring node through the other of the first port and the second port than the port on which the ring topology request was received.

### Claim 14 (depends on 12)

The node of claim 12, wherein the at least one ring topology request is a Ring Automated Protection Switching message, the processor further creates the at least one ring topology request by:
adding a type-length-value element to the Ring Automated Protection Switching message, the type-length-value element including a node signature for the node and the hop count; and
initializing the hop count.

### Claim 15 (depends on 14)

The node of claim 14, wherein the ring topology request is forwarded through both ports, receiving at least one response to the ring topology request comprises:
receiving a response at each of the first port and the second port, each response having been forwarded through the ring from the opposite port, each response including a total node count of all the nodes in the ring and an identification of each node in the ring arranged in an order of processing.

### Claim 16 (depends on 12)

The node of claim 12, wherein the ring topology request is a LinkTrace message, the LinkTrace message including a time-to-live value, the processor further inserts a ring identifier into the LinkTrace message, the ring identifier insuring that the ring topology request remains local to the ring; and
at least one of the first port and the second port further receives a plurality of LinkTrace responses, each LinkTrace response originated by one of the nodes of the plurality of nodes of the ring, each LinkTrace response including an identification of the originating node; and
wherein the indication of a hop count needed for the ring topology request to reach the at least one responding node is a time-to-live value.

### Claim 17 (depends on 16)

The node of claim 16, wherein the hop count needed for the ring topology request to reach the at least one responding node is equal to one half of a difference between the time-to-live value of the LinkTrace message and the time-to-live value of the LinkTrace response.

### Claim 18 (depends on 12)

The node of claim 12, wherein the ring topology request is a continuity check message, at least one port further receives a modified ring topology request through the other of the first port and the second port than the port on which the ring topology request was transmitted, the modified ring topology request including a listing of identifications of nodes having previously received continuity check message in an order of processing and a total node count of all the nodes on the ring.

### Claim 19 (depends on 12)

The node of claim 12, wherein the processor further:
populates static entries in a forwarding database table according to the topology; and
responsive to receiving notice of a failed link, the notice including a source address of a node adjacent to the failed link, the processor further:
uses the topology and the source address of the node adjacent to the failed link to reconfigure the forwarding database table; and
forwards data using the reconfigured forwarding database table without flooding the ring.

### Claim 20

A system for automatically discovering a topology of a communication network ring, the system comprising:
a plurality of nodes interconnected in a ring configuration, each node including:
a first port and a second port, each port operable to receive and transmit data:
at least one of the first port and the second port receiving at least one of a ring topology request and a response to the ring topology request from at least one other node on the ring, the at least one of the ring topology request and the response to the ring topology request including an identification of the at least one other node and an indication of a hop count needed to reach the at least one other node;
the other of the first port and the second port than the port on which the ring topology request was received forwarding the at least one of a ring topology request and a response to the ring topology request to at least one neighboring node on the ring; and
a processor electrically connected to each port, the processor determining the topology based on the identification of the at least one node, the hop count, and an identification of the forwarding port.
