IP Library Granted Patent US 12,457,171
Granted Patent B1
US 12,457,171 · App. 18/630,214 · Granted Oct 28, 2025

Micro SID packet processing

Inventors: Nancy Y. Shaw (Cupertino, CA); Sharada Yeluri (Cupertino, CA); Venkatraman Chandrasekaran (Cupertino, CA); Sri Karthik Goud Gadela (Cupertino, CA); Swamy Sadashivaiah Renu Kananda (Sunnyvale, CA)
Assignee: Juniper Networks, Inc.
H04L45/745H04L45/02H04L45/12H04L69/22
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,457,171
App. No.
18/630,214
Granted
Oct 28, 2025
Kind
B1
Abstract

An example first network device includes a control unit configured to execute at least one application and a forwarding unit. The forwarding unit includes an interface configured to receive packets, at least one packet processor operably coupled to a memory, and a forwarding path, wherein at least a portion of the forwarding path is stored in the memory and is executable by the at least one packet processor. The forwarding unit is configured to receive an advertisement originated by a second network device in a network, wherein the advertisement specifies a second micro segment identifier (SID), and store, in a destination lookup table, a route entry comprising a first micro SID associated with the first network device and the second micro SID.

Claims (34)

1. A method comprising:

storing, by a network device and in a destination lookup table, a route entry comprising both a first micro segment identifier (SID) associated with the network device and a second micro SID; and

determining, based on the route entry, that at least a portion of a header of a received packet matches both the first micro SID and the second micro SID through a single lookup in the destination lookup table.

2. The method of claim 1 , further comprising:

performing, by the network device, based on the determining, one or more actions indicated in a matching route entry on the received packet.

3. The method of claim 2 , wherein the network device is a first network device, and wherein the one or more actions comprise a shift of a position of the second micro SID in the header and a forward of the received packet along a shortest path to a second network device.

4. The method of claim 1 , wherein the network device is a first network device, and wherein the method further comprises:

based on the at least the portion of the header of the received packet matching both the first micro SID and the second micro SID in the route entry, removing, by the first network device, the first micro SID from the header and shifting a position of the second micro SID in the header to obtain an updated header that includes a shifted second micro SID; and

based on the second micro SID in the header, forwarding, by the first network device and into a network towards a second network device, a packet comprising the updated header.

5. The method of claim 4 , wherein the forwarding the packet comprising the updated header into the network comprises forwarding the packet comprising the updated header without performing a lookup in the destination lookup table of information in the updated header.

6. The method of claim 4 , wherein the shifting moves the second micro SID to a previous location of the first micro SID in the header.

7. The method of claim 4 , wherein the forwarding the packet comprising the updated header into the network comprises forwarding the packet comprising the updated header to an egress forwarding unit for the egress forwarding unit to forward into the network.

8. The method of claim 1 , wherein a forwarding path of a forwarding unit of the network device comprises at least one of an Interior Gateway Protocol (IGP) flex parser, a destination lookup unit, and an ingress results parser, wherein the forwarding unit comprises the destination lookup table.

9. The method of claim 1 , wherein the first micro SID and the second micro SID each has a length of 16 bits.

10. The method of claim 1 , further comprising receiving, by the network device, the received packet.

11. A network device comprising:

memory configured to store a destination lookup table; and

processing circuitry coupled to the memory, the processing circuitry configured to:

store, in the destination lookup table, a route entry comprising both a first micro segment identifier (SID) associated with the network device and a second micro SID; and

determine, based on the route entry, that at least a portion of a header of a received packet matches both the first micro SID and the second micro SID through a single lookup in the destination lookup table.

12. The network device of claim 11 , wherein the processing circuitry is further configured to perform, based on the determining, one or more actions indicated in a matching router entry on the received packet.

13. The network device of claim 12 , wherein the network device is a first network device, and wherein the one or more actions comprise a shift of a position of the second micro SID in the header and a forward of the received packet along a shortest path to a second network device.

14. The network device of claim 11 , wherein the network device is a first network device, and wherein the processing circuitry is further configured to:

remove, based on the at least the portion of the header of the received packet matching both the first micro SID and the second micro SID in the route entry, the first micro SID from the header and shifting a position of the second micro SID in the header to obtain an updated header that includes a shifted second micro SID; and

forward, based on the second micro SID in the header and into a network towards a second network device, a packet comprising the updated header.

15. The network device of claim 14 , wherein as part of forwarding the packet comprising the updated header into the network, the processing circuitry is configured to forward the packet comprising the updated header without performing a lookup in the destination lookup table of information in the updated header.

16. The network device of claim 14 , wherein the shifting moves the second micro SID to a previous location of the first micro SID in the header.

17. The network device of claim 14 , wherein as part of forwarding the packet comprising the updated header into the network, the processing circuitry is configured to forward the packet comprising the updated header to an egress forwarding unit for the egress forwarding unit to forward into the network.

18. The network device of claim 11 , further comprising:

a forwarding unit, wherein a forwarding path of the forwarding unit comprises at least one of an Interior Gateway Protocol (IGP) flex parser, a destination lookup unit, and an ingress results parser, wherein the forwarding unit comprises the destination lookup table.

19. The network device of claim 11 , wherein the first micro SID and the second micro SID each has a length of 16 bits.

20. Non-transitory computer-readable media storing instructions, which when executed, cause processing circuitry of a network device to perform steps comprising:

storing, in a destination lookup table, a route entry comprising both a first micro segment identifier (SID) associated with the network device and a second micro SID; and

determining, based on the route entry, that at least a portion of a header of a received packet matches both the first micro SID and the second micro SID through a single lookup in the destination lookup table.

Assignments (2)
NUNC PRO TUNC ASSIGNMENT Recorded May 6, 2026
From: JUNIPER NETWORKS, INC.
To: HEWLETT PACKARD ENTERPRISE DEVELOPMENT LP
Reel/Frame 075513/0034 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 27, 2025
From: SHAW, NANCY Y.; YELURI, SHARADA; CHANDRASEKARAN, VENKATRAMAN; GOUD GADELA, SRI KARTHIK; KANANDA, SWAMY SADASHIVAIAH RENU
To: JUNIPER NETWORKS, INC.
Reel/Frame 071776/0107 →
Continuity (2)
Continuation 17934431 · Sep 22, 2022
Continuation 17247955 · Dec 31, 2020
References Cited (25)
US 10841220B1 · Filsfils et al. · 2020 [cited by applicant]
US 11323371B1 · Goud Gadela et al. · 2022 [cited by applicant]
US 11477119B1 · Shaw · 2022 [cited by examiner]
US 11582140B2 · Nainar et al. · 2023 [cited by applicant]
US 11991081B1 · Shaw · 2024 [cited by examiner]
US 20070094394A1 · Singh · 2007 [cited by examiner]
US 20120226700A1 · Chang · 2012 [cited by applicant]
US 20170331794A1 · Lokman · 2017 [cited by examiner]
US 20180091518A1 · Zhuang · 2018 [cited by examiner]
US 20210092053A1 · Filsfils · 2021 [cited by examiner]
US 20210320884A1 · Filsfils et al. · 2021 [cited by applicant]
US 20210352009A1 · Van de Velde et al. · 2021 [cited by applicant]
US 20220053072A1 · Filsfils · 2022 [cited by examiner]
Filsfils et al., “Network Programming extension: SRv6 uSID instruction,” draft-filsfils-spring-net-pgm-extension-srv6-usid-08, Internet-Draft, Network Working Group, Nov. 2, 2020, 22 pp. [cited by applicant]
Filsfils et al., “Segment Routing Architecture draft-filsfils-rtgwg-segment-routing-00,” Internet-Draft, Network Working Group, Jun. 28, 2013, 28 pp. [cited by applicant]
Filsfils et al., “Segment Routing Architecture,” draft-filsfils-spring-segment-routing-04, Internet-Draft, Network Working Group, Jul. 3, 2014, 18 pp. [cited by applicant]
Filsfils et al., “Segment Routing Use Cases,” Network Working Group, draft-filsfils-rtgwg-segment-routing-use-cases-01, Internet-Draft, Jul. 14, 2013, 46 pp. [cited by applicant]
Filsfils et al., “Segment Routing with MPLS data plane,” draft-filsfils-spring-segment-routing-mpls-03, Internet-Draft, Network Working Group, Jul. 31, 2014, 14 pp. [cited by applicant]
Notice of Allowance from U.S. Appl. No. 17/934,431 dated Jan. 4, 2024, 9 pp. [cited by applicant]
Office Action from U.S. Appl. No. 17/934,431 dated Oct. 5, 2023, 7 pp. [cited by applicant]
Previdi et al., “Source Packet Routing in Networking (SPRING) Problem Statement and Requirements,” RFC 7855, Internet Engineering Task Force (IETF), May 2016, 19 pp. [cited by applicant]
Prosecution History from U.S. Appl. No. 17/247,955, dated Mar. 24, 2022 through Jun. 24, 2022, 30 pp. [cited by applicant]
Prosecution History from U.S. Appl. No. 17/934,431, dated Oct. 5, 2023 through Jan. 4, 2024, 27 pp. [cited by applicant]
Response to Office Action dated Oct. 5, 2023 from U.S. Appl. No. 17/934,431, filed Dec. 5, 2023, 8 pp. [cited by applicant]
Tulumello et al., Micro SIDs: a solution for Efficient Representation of Segment IDs in SRv6 , arXiv:2007.12286, Jul. 23, 2020 (v1), last revised Oct. 16, 2020 (this version, v3), 12 pp. [cited by applicant]