IP Library Granted Patent US 9,729,433
Granted Patent B2
US 9,729,433 · App. 14/443,047 · Granted Aug 8, 2017

Enhanced route tracing

Inventor: Joseph Polland (Eden Prairie, MN)
Assignee: CommScope Technologies LLC
H04L45/36H04L43/10H04L45/745
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 9,729,433
App. No.
14/443,047
Filed
May 14, 2015
Granted
Aug 8, 2017
Kind
B2
Art Unit
2475
USPC
370/392
Abstract

A network comprises a destination node; a source node configured to output an enhanced route trace packet; and one or more intermediate nodes configured to forward the enhanced route trace packet toward the destination node based on a routing table until the enhanced route trace packet reaches the destination node. Each of the one or more intermediate nodes is further configured to insert identifying information into the enhanced route trace packet. The destination node is configured to send a response packet to the source node containing all the identifying information entered by the one or more intermediate nodes. The destination node is also configured to insert identifying information into the response packet.

Claims (43)

1. A network comprising:

a destination node;

a source node configured to output an enhanced route trace packet;

one or more intermediate nodes configured to forward the enhanced route trace packet toward the destination node based on a routing table until the enhanced route trace packet reaches the destination node;

wherein each of the one or more intermediate nodes is further configured to insert identifying information into the enhanced route trace packet;

wherein the destination node is configured to send a response packet to the source node containing all the identifying information entered by the one or more intermediate nodes, the destination node also configured to insert identifying information into the response packet, wherein the destination node sends the response packet when source routing is not requested or a node address for the destination node is a last node address in a list specified by the source node;

wherein the enhanced route trace packet satisfies one of Internet Protocol version 4 (IPv4) or Internet Protocol version 6 (IPv6).

2. The network of claim 1 , wherein the identifying information includes at least one of a node address, ingress port identification, ingress cable information, egress port identification, and egress cable information.

3. The network of claim 1 , wherein the source node is configured to multicast the enhanced route trace packet to a plurality of destination nodes.

4. The network of claim 1 , wherein each of the intermediate nodes is configured to adjust the length of a data field in the enhanced route trace packet for insertion of the respective identifying information.

5. The network of claim 1 , wherein the enhanced route trace packet includes a pointer field which indicates a next insertion point in a data field of the enhanced route trace packet;

wherein each of the intermediate nodes is configured to update the pointer field such that each intermediate node inserts the respective identifying information in topological order.

6. The network of claim 1 , wherein the response packet sent by the destination node is an enhanced Internet Control Message Protocol (ICMP) response message containing path information from the source node to the destination node based on the respective identifying information inserted by the one or more intermediate nodes and the destination node.

7. The network of claim 1 , wherein each of the intermediate nodes is configured to insert the respective identifying information into the enhanced route trace packet via one or more Type Length Value (TLV) elements.

8. A network node comprising:

a plurality of ports each configured to receive and transmit data;

a memory configured to store a routing table; and

a processing unit configured to process an enhanced route trace packet received over one of the plurality of ports; wherein processing the enhanced route trace packet includes inserting identifying information into the enhanced route trace packet and determining over which of the plurality of ports to forward the enhanced route trace packet based on a destination node indicated in the enhanced route trace packet and the routing table, wherein the network node sends a response packet when the network node is the destination node and source routing is not requested or a node address for the network node is a last node address in a list specified by a source node;

wherein the enhanced route trace packet satisfies one of Internet Protocol version 4 (IPv4) or Internet Protocol version 6 (IPv6).

9. The network node of claim 8 , wherein the identifying information includes at least one of a node address, ingress port identification, ingress cable information, egress port identification, and egress cable information.

10. The network node of claim 8 , wherein the processing unit is configured to replicate the enhanced route trace packet based on a plurality of destination node addresses in the enhanced route trace packet.

11. The network node of claim 8 , wherein the processing unit is configured to adjust the length of a data field in the enhanced route trace packet for insertion of the identifying information.

12. The network node of claim 8 , wherein the enhanced route trace packet includes a pointer field which indicates a next insertion point in a data field of the enhanced route trace packet;

wherein the processing unit is configured to update the pointer field after inserting the identifying information.

13. The network node of claim 8 , wherein the processing unit is configured to insert the identifying information into the enhanced route trace packet via one or more Type Length Value (TLV) elements.

14. A method of route tracing, the method comprising:

receiving a route trace packet at a node, the route trace packet having an enhanced route trace header, the enhanced route trace header includes respective fields for at least one of ingress port identification (ID), egress port ID, ingress cable information, and egress cable information;

inserting a node address of the node into the enhanced route trace header;

determining if the node address matches a destination address in the route trace packet;

if the node address matches the destination address and source routing is not requested or the node address is a last node address in a list specified by a source node, the method further comprises:

extracting information from the enhanced route trace header;

inserting the extracted information into an enhanced response packet; and

sending the enhanced response packet to a source node of the route trace packet; and

if the node address does not match the destination address:

selecting an egress port over which to forward the route trace packet based on the destination address; and

forwarding the route trace packet via the selected egress port;

wherein the enhanced route trace packet satisfies one of Internet Protocol version 4 (IPv4) or Internet Protocol version 6 (IPv6).

15. The method of claim 14 , wherein inserting the node address into the enhanced route trace header includes inserting at least one of ingress port identification (ID) and ingress cable information corresponding to the port over which the route trace packet was received.

16. The method of claim 14 , further comprising:

inserting at least one of egress port ID and egress cable information corresponding to the selected egress port into the enhanced route trace header prior to forwarding the route trace packet.

17. The method of claim 14 , wherein the egress cable information and the ingress cable information includes one or more of cable ID, cable type, cable color, polarity, length, media, category, rating, and optical mode.

18. The method of claim 14 , wherein inserting the node address comprises inserting the node address and other identifying information in event chronological order.

19. The method of claim 14 , wherein inserting the node address comprises inserting the node address via a Time Length Value (TLV) element.

Assignments (14)
RELEASE OF SECURITY INTEREST AT REEL/FRAME 049905/0504 Recorded Dec 19, 2024
From: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT
To: ARRIS ENTERPRISES LLC (F/K/A ARRIS ENTERPRISES, INC.); ARRIS TECHNOLOGY, INC.; ARRIS SOLUTIONS, INC.; COMMSCOPE, INC. OF NORTH CAROLINA; COMMSCOPE TECHNOLOGIES LLC; RUCKUS WIRELESS, LLC (F/K/A RUCKUS WIRELESS, INC.)
Reel/Frame 071477/0255 →
SECURITY INTEREST Recorded Dec 17, 2024
From: ARRIS ENTERPRISES LLC; COMMSCOPE TECHNOLOGIES LLC; COMMSCOPE INC., OF NORTH CAROLINA; OUTDOOR WIRELESS NETWORKS LLC; RUCKUS IP HOLDINGS LLC
To: APOLLO ADMINISTRATIVE AGENCY LLC
Reel/Frame 069889/0114 →
SECURITY INTEREST Recorded Nov 19, 2021
From: ARRIS SOLUTIONS, INC.; ARRIS ENTERPRISES LLC; COMMSCOPE TECHNOLOGIES LLC; COMMSCOPE, INC. OF NORTH CAROLINA; RUCKUS WIRELESS, INC.
To: WILMINGTON TRUST
Reel/Frame 060752/0001 →
TERM LOAN SECURITY AGREEMENT Recorded Jul 3, 2019
From: COMMSCOPE, INC. OF NORTH CAROLINA; COMMSCOPE TECHNOLOGIES LLC; ARRIS ENTERPRISES LLC; ARRIS TECHNOLOGY, INC.; RUCKUS WIRELESS, INC.; ARRIS SOLUTIONS, INC.
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 049905/0504 →
ABL SECURITY AGREEMENT Recorded Jul 3, 2019
From: COMMSCOPE, INC. OF NORTH CAROLINA; COMMSCOPE TECHNOLOGIES LLC; ARRIS ENTERPRISES LLC; ARRIS TECHNOLOGY, INC.; RUCKUS WIRELESS, INC.; ARRIS SOLUTIONS, INC.
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 049892/0396 →
PATENT SECURITY AGREEMENT Recorded Jul 3, 2019
From: COMMSCOPE TECHNOLOGIES LLC
To: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS COLLATERAL AGENT
Reel/Frame 049892/0051 →
RELEASE OF SECURITY INTEREST Recorded Apr 9, 2019
From: JPMORGAN CHASE BANK, N.A.
To: REDWOOD SYSTEMS, INC.; ALLEN TELECOM LLC; ANDREW LLC; COMMSCOPE, INC. OF NORTH CAROLINA; COMMSCOPE TECHNOLOGIES LLC
Reel/Frame 048840/0001 →
RELEASE OF SECURITY INTEREST Recorded Apr 9, 2019
From: JPMORGAN CHASE BANK, N.A.
To: REDWOOD SYSTEMS, INC.; ALLEN TELECOM LLC; ANDREW LLC; COMMSCOPE, INC. OF NORTH CAROLINA; COMMSCOPE TECHNOLOGIES LLC
Reel/Frame 049260/0001 →
PATENT SECURITY AGREEMENT (TERM) Recorded Jan 13, 2016
From: COMMSCOPE TECHNOLOGIES LLC
To: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT
Reel/Frame 037513/0709 →
PATENT SECURITY AGREEMENT (ABL) Recorded Jan 13, 2016
From: COMMSCOPE TECHNOLOGIES LLC
To: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT
Reel/Frame 037514/0196 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 29, 2015
From: COMMSCOPE EMEA LIMITED
To: COMMSCOPE TECHNOLOGIES LLC
Reel/Frame 037012/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 26, 2015
From: TYCO ELECTRONICS SERVICES GMBH
To: COMMSCOPE EMEA LIMITED
Reel/Frame 036956/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 21, 2015
From: ADC TELECOMMUNICATIONS, INC.; TE CONNECTIVITY SOLUTIONS GMBH
To: TYCO ELECTRONICS SERVICES GMBH
Reel/Frame 036908/0443 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 19, 2015
From: POLLAND, JOSEPH
To: ADC TELECOMMUNICATIONS, INC.
Reel/Frame 035674/0442 →
Continuity (2)
Provisional Application 61818205 · May 1, 2013
Related Publication 20160142291A1 · May 19, 2016