IP Library › Granted Patent US 12,328,255
Granted Patent B2
US 12,328,255 · App. 18/529,878 · Granted Jun 10, 2025

Segment routing network signaling and packet processing

Inventors: Clarence Filsfils (Brussells, BE); Zafar Ali (Hicksville, NY); Syed Kamran Raza (Kanata, CA); Ahmed Refaat Bashandy (Milpitas, CA); Nagendra Kumar Nainar (Morrisville, NC); Carlos M. Pignataro (Cary, NC); Jaganbabu Rajamanickam (Stittsville, CA); Rakesh Gandhi (Stittsville, CA); Bhupendra Yadav (Kanata, CA); Faisal Iqbal (Ottawa, CA)
Assignee: Cisco Technology, Inc.
H04L45/34H04L41/0246H04L43/106H04L45/02H04L45/20H04L45/304H04L45/741H04L2101/659
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 12,328,255
App. No.
18/529,878
Granted
Jun 10, 2025
Kind
B2
Abstract

In one embodiment, a service chain data packet is instrumented as it is communicated among network nodes in a network providing service-level and/or networking operations visibility. The service chain data packet includes a particular header identifying a service group defining one or more service functions, and is a data packet and not a probe packet. A network node adds networking and/or service-layer operations data to the particular service chain data packet, such as, but not limited to, in the particular header. Such networking operations data includes a performance metric or attribute related to the transport of the particular service chain packet in the network. Such service-layer operations data includes a performance metric or attribute related to the service-level processing of the particular service chain data packet in the network.

Claims (45)

1. A method, comprising:

receiving a segment routing packet by a router in a network;

responsive to a router data plane ascertaining during fast path processing by a fast path processing unit based on an Operations, Administration, and Maintenance (OAM) segment identifier (SID) of the segment routing packet that the segment routing packet is to be OAM processed, communicating the segment routing packet for remote processing, with fast path processing being hardware-based packet processing by the fast path processing unit; and

transmitting the segment routing packet for remote processing,

wherein the segment routing packet is an Internet Protocol version 6 (IPv6) packet including an IPv6 header, the IPv6 header including an IPv6 Destination Address,

wherein the IPv6 Destination Address includes the OAM SID, and

wherein responsive to the OAM SID identifying timestamp behavior, the fast path processing unit communicating a timestamp of a current time along with the segment routing packet.

2. The method of claim 1 , wherein the OAM SID includes an identification of an END.OTP endpoint with timestamp and punt function.

3. The method of claim 2 , wherein a segment list of the segment routing packet includes the OAM SID.

4. The method of claim 1 , wherein the OAM SID includes an identification of END.OTPF endpoint with punt and forward function.

5. The method of claim 4 , wherein a segment list of the segment routing packet includes the OAM SID.

6. The method of claim 1 , wherein a segment list of the received segment routing packet includes the OAM SID.

7. The method of claim 1 , wherein the OAM SID includes an OAM argument value, comprising one or more bits, qualifying the OAM processing designated by a segment routing function value in the OAM.

8. The method of claim 1 , wherein transmitting the segment routing packet includes sending a timestamp and identifying information of the segment routing packet via the network.

9. The method of claim 8 , further comprising:

another segment router in the network OAM processing of the segment routing packet, including sending another timestamp and packet identifying information related to the segment routing packet; and

receiving and processing the timestamp and the identifying information and the another timestamp and the packet identifying information and to determine a result including delay, loss, segment routing path verification, or jitter.

10. An apparatus, comprising:

one or more hardware interfaces sending and receiving packets with a network; and

a fast path packet processing unit performing hardware-based packet processing,

wherein the apparatus performs packet processing operations including segment routing-capable (SR-capable) packet processing operations, with the packet processing operations including:

receiving a segment routing packet;

responsive to a router data plane ascertaining during fast path processing by a fast path processing unit based on an Operations, Administration, and Maintenance (OAM) segment identifier (SID) of the segment routing packet that the segment routing packet is to be OAM processed, communicating the segment routing packet for remote processing, with fast path processing being hardware-based packet processing by the fast path processing unit; and

transmitting the segment routing packet for remote processing,

wherein the segment routing packet is an Internet Protocol version 6 (IPv6) packet including an IPv6 header, with the IPv6 header including an IPv6 Destination Address,

wherein the IPv6 Destination Address includes the OAM SID; and

wherein responsive to the OAM SID identifying timestamp behavior, the fast path processing unit communicating a timestamp of a current time along with the segment routing packet.

11. The apparatus of claim 10 , wherein the OAM SID includes an identification of an END.OTP endpoint with timestamp and punt function.

12. The apparatus of claim 11 , wherein a segment list of the segment routing packet includes the OAM SID.

13. The apparatus of claim 10 , wherein the OAM SID includes an identification of END.OTPF endpoint with punt and forward function.

14. The apparatus of claim 13 , wherein a segment list of the segment routing packet includes the OAM SID.

15. The apparatus of claim 10 , wherein a segment list of the received segment routing packet includes the OAM SID.

16. The apparatus of claim 10 , wherein the OAM SID includes an OAM argument value, comprising one or more bits, qualifying the OAM processing designated by a segment routing function value in the OAM SID.

17. The apparatus of claim 10 , wherein the OAM processing includes sending a timestamp and identifying information of the segment routing packet via the network.

18. The apparatus of claim 17 , further comprising:

another segment router in the network OAM processing of the segment routing packet, including sending another timestamp and packet identifying information related to the segment routing packet;

receiving and processing the timestamp and the identifying information and the another timestamp and the packet identifying information and to determine a result including delay, loss, segment routing path verification, or jitter.

19. At least one non-transitory computer-readable medium storing instructions, which when executed by at least one processor of a network device, causes the at least one processor to:

receive a segment routing packet;

responsive to a router data plane ascertaining during fast path processing by a fast path processing unit based on an Operations, Administration, and Maintenance (OAM) segment identifier (SID) of the segment routing packet that the segment routing packet is to be OAM processed, communicating the segment routing packet for remote processing, with fast path processing being hardware-based packet processing by the fast path processing unit; and

transmitting the segment routing packet for remote processing,

wherein the segment routing packet is an Internet Protocol version 6 (IPv6) packet including an IPv6 header, with the IPv6 header including an IPv6 Destination Address,

wherein the IPv6 Destination Address includes the OAM SID, and

wherein responsive to the OAM SID identifying timestamp behavior, the fast path processing unit communicating a timestamp of a current time along with the segment routing packet.

20. The non-transitory computer-readable medium of claim 19 , wherein the OAM SID includes an identification of an END.OTP endpoint with timestamp and punt function.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 5, 2023
From: FILSFILS, CLARENCE; ALI, ZAFAR; RAZA, SYED KAMRAN; BASHANDY, AHMED REFAAT; NAINAR, NAGENDRA KUMAR; PIGNATARO, CARLOS M.; RAJAMANICKAM, JAGANBABU; GANDHI, RAKESH; YADAV, BHUPENDRA; IQBAL, FAISAL
To: CISCO TECHNOLOGY, INC.
Reel/Frame 065772/0439 →
Continuity (5)
Continuation 17811570 · Jul 8, 2022
Continuation 16675083 · Nov 5, 2019
Continuation 15841276 · Dec 13, 2017
Provisional Application 62567823 · Oct 4, 2017
Related Publication 20240113962A1 · Apr 4, 2024
References Cited (64)
US 6658480B2 · Boucher et al. · 2003 [cited by applicant]
US 7197008B1 · Shabtay et al. · 2007 [cited by applicant]
US 7961636B1 · Barach et al. · 2011 [cited by applicant]
US 9444675B2 · Guichard et al. · 2016 [cited by applicant]
US 9525627B2 · Padgett et al. · 2016 [cited by applicant]
US 9537769B2 · Bryant et al. · 2017 [cited by applicant]
US 9762488B2 · Previdi et al. · 2017 [cited by applicant]
US 9806962B2 · Guichard et al. · 2017 [cited by applicant]
US 9912577B2 · Filsfils et al. · 2018 [cited by applicant]
US 10063463B2 · Saad et al. · 2018 [cited by applicant]
US 10063475B2 · Previdi et al. · 2018 [cited by applicant]
US 10153951B2 · Guichard et al. · 2018 [cited by applicant]
US 10158568B2 · Gage · 2018 [cited by applicant]
US 10277471B2 · Ubaldi et al. · 2019 [cited by applicant]
US 10382334B2 · Previdi et al. · 2019 [cited by applicant]
US 20010037397A1 · Boucher et al. · 2001 [cited by applicant]
US 20030023710A1 · Corlett et al. · 2003 [cited by applicant]
US 20030112748A1 · Puppa et al. · 2003 [cited by applicant]
US 20030221015A1 · Basso et al. · 2003 [cited by applicant]
US 20040054813A1 · Boucher et al. · 2004 [cited by applicant]
US 20040139237A1 · Rangan et al. · 2004 [cited by applicant]
US 20050099949A1 · Mohan et al. · 2005 [cited by applicant]
US 20060155532A1 · Nam et al. · 2006 [cited by applicant]
US 20060215582A1 · Castagnoli et al. · 2006 [cited by applicant]
US 20070036080A1 · Addeo · 2007 [cited by examiner]
US 20070115986A1 · Shankara · 2007 [cited by applicant]
US 20070206503A1 · Gong et al. · 2007 [cited by applicant]
US 20070280247A1 · Mera et al. · 2007 [cited by applicant]
US 20080101241A1 · Mohan et al. · 2008 [cited by applicant]
US 20080313364A1 · Flynn et al. · 2008 [cited by applicant]
US 20110093946A1 · Chen · 2011 [cited by applicant]
US 20110222412A1 · Kompella · 2011 [cited by applicant]
US 20150256456A1 · Previdi et al. · 2015 [cited by applicant]
US 20150263892A1 · John et al. · 2015 [cited by applicant]
US 20150381444A1 · Nainar · 2015 [cited by examiner]
US 20160021162A1 · Surcouf et al. · 2016 [cited by applicant]
US 20160099853A1 · Nedeltchev et al. · 2016 [cited by applicant]
US 20160254991A1 · Eckert et al. · 2016 [cited by applicant]
US 20160337264A1 · Murashko · 2016 [cited by examiner]
US 20160352620A1 · Schmutzer et al. · 2016 [cited by applicant]
US 20170250907A1 · Pignataro et al. · 2017 [cited by applicant]
US 20170250908A1 · Nainar et al. · 2017 [cited by applicant]
US 20170310569A1 · Clemm et al. · 2017 [cited by applicant]
US 20170324622A1 · Ubaldi et al. · 2017 [cited by applicant]
US 20170366456A1 · Dara et al. · 2017 [cited by applicant]
EP 2690821A1 · 2014 [cited by applicant]
GB 2420244A · 2006 [cited by applicant]
Bates T., et al., “Multiprotocol Extensions for BGP-4,” Network Working Group, Request for Comments: 4760, Jan. 2007, pp. 1-12. [cited by applicant]
Bates T., et al., “Multiprotocol Extensions for BGP-4,” RFC 2283, Feb. 1998, The Internet Society, Reston, VA, USA, 9 pages. [cited by applicant]
Cisco Systems, Inc., “Cisco 10000 Series Router Control Plane Policing—Platform Enhancement,” San Jose, CA, Apr. 2008, 24 Pages. [cited by applicant]
Deering S., et al., “Internet Protocol, Version 6 (IPv6) Specification,” RFC 8200, Jul. 2017, The Internet Society, Reston, VA, USA, 42 pages. [cited by applicant]
Deering S., et al., “Internet Protocol, Version 6 (IPv6) Specification,” rfc2460.txt, Internet Protocol, Version 6 (IPV6) Specification, Internet Engineering Task Force, IETF, Standard, Internet Society (ISOC) 4, Rue De… [cited by applicant]
Edgeworth B., et al., “IP Routing on Cisco IOS, IOS XE, and IOS XR: How a Router Works,” An Essential Guide to Understanding and Implementing IP Routing Protocols, Chapter 3, Cisco Press, Indianapolis, Jan. 2, 2015, 16 … [cited by applicant]
Extended European Search Report for European Application No. 22160328.5, mailed Jun. 1, 2022, 9 Pages. [cited by applicant]
Filsfils C., et al., “Segment Routing Architecture draft-ietf-spring-segment-routing-11,” Network Working Group, The Internet Society, Internet-Draft, Reston, VA, USA, Feb. 16, 2017, pp. 1-28. [cited by applicant]
Filsfils C., et al., “Segment Routing Architecture draft-ietf-spring-segment-routing-12,” Network Working Group, The Internet Society, Reston, VA, USA, Jun. 20, 2017, pp. 1-28. [cited by applicant]
Filsfils C., et al., “SRv6 Network Programming draft-filsfils-spring-srv6-network-programming-01,” Cisco Systems, Inc., Spring, The Internet Society, Reston, VA, USA, Jun. 28, 2017, pp. 1-42. [cited by applicant]
Filsfls C., et al., “SRv6 Network Programming; draft-filsfils-spring-srv6-network-programming-00,” The Internet Society, Mar. 9, 2017, Reston, VA, USA, 41 Pages. [cited by applicant]
International Preliminary Report on Patentability for International Application No. PCT/US2018/054463, mailed Apr. 16, 2020, 10 Pages. [cited by applicant]
International Search Report and Written Opinion for International Application No. PCT/US2018/054463, mailed Dec. 12, 2018, 12 Pages. [cited by applicant]
International Standard, “Information Technology—Telecommunications and Information Exchange Between Systems—Intermediate System to Intermediate System Intra-domain Routeing Information Exchange Protocol for Use in Conju… [cited by applicant]
Previdi S., et al., “IPv6 Segment Routing Header (SRH) draft-ietf-6man-segment-routing-header-06.txt,” Internet Engineering Task Force (IETF), Standard Working Draft, Internet Society (ISOC) 4, Rue Des Falaises CH—1205 … [cited by applicant]
Rekhter Y., et al., “A Border Gateway Protocol 4 (BGP-4),” Network Working Group, RFC 4271, Reston, VA, USA, Jan. 2006, pp. 1-104, https://www.rfc-editor.org/rfc/rfc4271. [cited by applicant]
Rosen E., et al., “Multiprotocol Label Switching Architecture,” Network Working Group, Request for Comments: 3031, Jan. 2001, pp. 1-61. [cited by applicant]