Granted Patent B1

US 12,659,270 · App. 18/221,727 · Granted Jun 16, 2026

Inventors: Kapil Arora (Bangalore, IN); Samson P Ninan (Bangalore, IN); Shraddha Hegde (Bangalore, IN)

Assignee: Hewlett Packard Enterprise Development LP

H04L45/50H04L45/02H04L45/04H04L45/22

Abstract

Claims (70)

1 . A non-transitory computer-readable storage medium storing processor-executable instructions which, when executed by at least one processor, cause the at least one processor to perform a method for use in ping request or traceroute operations in a multi-autonomous system (AS) segment routed (SR) path including a headend router in a first AS and an egress router in an AS other than the first AS, the first AS having a first AS border router (ASBR) and a second AS having a second ASBR peering with the first ASBR, the method including:

a) receiving, by a router in the second AS, a ping or traceroute request from the headend router in the first AS, the ping or traceroute request including a reverse path label pair, and the reverse path label pair including

1) A node segment identifier (SID) corresponding to the second ASBR of the second AS, and

2) An egress peer engineering (EPE) SID corresponding to a segment between the second ASBR and the first ASBR;

b) generating, by the router and responsive to receiving the ping or traceroute request, a ping or traceroute reply including the reverse path label pair; and

c) forwarding the ping or traceroute reply to the second ASBR using the node SID of the reverse path label pair.

2 . The non-transitory computer-readable storage medium of claim 1 , wherein the method further includes:

d) forwarding the ping or traceroute reply from the second ASBR to the first ASBR using the EPE SID of the reverse path label pair.

3 . The non-transitory computer-readable storage medium of claim 1 , wherein IP addresses are unique across the first and second ASes, and

wherein the node SID corresponding to the second ASBR of the second AS is a first label, and the EPE SID corresponding to a segment between the second ASBR and the first ASBR is a second label.

4 . The non-transitory computer-readable storage medium of claim 1 , wherein the egress router is in the second AS.

5 . The non-transitory computer-readable storage medium of claim 1 , wherein the SR path does not include the second ASBR.

6 . The non-transitory computer-readable storage medium of claim 1 , wherein the SR path does not include the first ASBR.

7 . A non-transitory computer-readable storage medium storing processor-executable instructions which, when executed by at least one processor, cause the at least one processor to perform a method for use in ping request or traceroute operations in a multi-autonomous system (AS) segment routed (SR) path including a headend router in a first AS and an egress router in an AS other than the first AS, the first AS having a first AS border router (ASBR) and a second AS having a second ASBR peering with the first ASBR, the method including:

a) receiving, by the second ASBR, an initial ping or traceroute request from the first ASBR, wherein the initial ping or traceroute request does not include a reverse label pair;

b) responsive to receiving the initial ping or traceroute request from the first ASBR, generating an initial ping or traceroute reply including a reverse path label pair, the reverse path label pair including

1) A node segment identifier (SID) corresponding to the second ASBR of the second AS, and

2) An egress peer engineering (EPE) SID corresponding to a segment between the second ASBR and the first ASBR; and

c) sending, by the second ASBR, the initial ping or traceroute reply towards the headend router via the first ASBR.

8 . The non-transitory computer-readable storage medium of claim 7 , wherein the method further includes:

d) receiving, by the headend router, the initial ping or traceroute reply;

e) generating, by the headend router and responsive to receiving the initial ping or traceroute reply, a further ping or traceroute request including the reverse path label pair; and

f) forwarding the further ping or traceroute request to the second ASBR using the node SID of the reverse path label pair.

9 . A non-transitory computer-readable storage medium storing processor-executable instructions which, when executed by at least one processor, cause the at least one processor to perform a method for use in a headend router of a multi-autonomous system (AS) segment routed (SR) path, the headend router belonging to a first AS, and the multi-AS SR path including an egress router in an AS other than the first AS, the first AS having a first AS border router (ASBR) and a second AS having a second ASBR peering with the first ASBR, the method including:

a) receiving a reverse path label pair including

1) A node segment identifier (SID) corresponding to the second ASBR of the second AS, and

2) An egress peer engineering (EPE) SID corresponding to a segment between the second ASBR and the first ASBR;

b) storing the reverse path label pair received;

c) generating a ping or traceroute request including the reverse path label pair for use in a ping or traceroute reply; and

d) sending, from the headend router, the ping or traceroute request.

10 . The non-transitory computer-readable storage medium of claim 9 wherein the SR path does not include at least one of (A) the second ASBR and/or (B) the first ASBR.

11 . A router on a multi-autonomous system (AS) segment routed (SR) path including a headend router in a first AS and an egress router in an AS other than the first AS, the first AS having a first AS border router (ASBR) and a second AS having a second ASBR peering with the first ASBR, the router comprising:

a) at least one processor; and

b) computer-readable storage medium storing processor-executable instructions which, when executed by the at least one processor, cause the at least one processor to perform a method for use in ping request or traceroute operations in the multi-autonomous system (AS) segment routed (SR) path, the method including

1) Receiving, by the router, a ping or traceroute request from the headend router in the first AS, the ping or traceroute request including a reverse path label pair, and the reverse path label pair including

a node segment identifier (SID) corresponding to the second ASBR of the second AS, and

an egress peer engineering (EPE) SID corresponding to a segment between the second ASBR and the first ASBR;

2) Generating, by the router and responsive to receiving the ping or traceroute request, a ping or traceroute reply including the reverse path label pair; and

3) forwarding, by the router, the ping or traceroute reply towards the second ASBR using the node SID of the reverse path label pair,

wherein the router is in the second AS.

12 . The router of claim 11 , wherein the ping or traceroute reply is forwarded from the second ASBR to the first ASBR using the EPE SID of the reverse path label pair.

13 . The router of claim 11 , wherein IP addresses are unique across the first and second ASes, and

wherein the node SID corresponding to the second ASBR of the second AS is a first label, and the EPE SID corresponding to a segment between the second ASBR and the first ASBR is a second label.

14 . The router of claim 11 , wherein the egress router is in the second AS.

15 . The router of claim 11 , wherein the SR path does not include the second ASBR.

16 . The router of claim 11 , wherein the SR path does not include the first ASBR.

17 . A communications network system comprising a second autonomous system border router (ASBR) for use with a multi-autonomous system (AS) segment routed (SR) path including a headend router in a first AS and an egress router in an AS other than the first AS, the first AS having a first AS border router (ASBR), wherein the second ASBR is in a second AS and peers with the first ASBR, the second ASBR including:

a) at least one processor; and

b) computer-readable storage medium storing processor-executable instructions which, when executed by the at least one processor, cause the at least one processor to perform a method for use in ping request or traceroute operations in the multi-autonomous system (AS) segment routed (SR) path, the method including:

1) Receiving, by the second ASBR, an initial ping or traceroute request from the first ASBR, wherein the initial ping or traceroute request does not include a reverse label pair;

2) Responsive to receiving the initial ping or traceroute request from the first ASBR, generating, by the second ASBR, an initial ping or traceroute reply including a reverse path label pair, the reverse path label pair including

a node segment identifier (SID) corresponding to the second ASBR of the second AS, and

an egress peer engineering (EPE) SID corresponding to a segment between the second ASBR and the first ASBR; and

3) sending, by the second ASBR, the initial ping or traceroute reply towards the headend router via the first ASBR.

18 . The communications system of claim 17 , further comprising the headend router, the head end router including:

a) at least one processor; and

b) a computer-readable storage medium storing processor-executable instructions which, when executed by the at least one processor of the headend router, cause the at least one processor of the headend router to perform a method including:

1) Receiving, by the headend router, the initial ping or traceroute reply;

2) Generating, by the headend router and responsive to receiving the initial ping or traceroute reply, a further ping or traceroute request including the reverse path label pair; and

3) Forwarding, by the first router, the further ping or traceroute request towards the second ASBR using the node SID of the reverse path label pair.

19 . A headend router on a multi-autonomous system (AS) segment routed (SR) path including a headend router in a first AS and an egress router in an AS other than the first AS, the first AS having a first AS border router (ASBR) and a second AS having a second ASBR peering with the first ASBR, the headend router comprising:

a) at least one processor; and

b) computer-readable storage medium storing processor-executable instructions which, when executed by the at least one processor, cause the at least one processor to perform a method for use in ping request or traceroute operations in the multi-autonomous system (AS) segment routed (SR) path, the method including:

1) Receiving, by the headend router, a reverse path label pair including

a node segment identifier (SID) corresponding to the second ASBR of the second AS, and

an egress peer engineering (EPE) SID corresponding to a segment between the second ASBR and the first ASBR;

2) Storing, by the headend router, the reverse path label pair received;

3) Generating, by the headend router, a ping or traceroute request including the reverse path label pair for use in a ping or traceroute reply; and

4) Sending, from the headend router, the ping or traceroute request.

20 . The headend router of claim 19 wherein the SR path does not include at least one of (A) the second ASBR and/or (B) the first ASBR.

Assignments (1)

Continuity (2)

References Cited (9)