IP Library › Granted Patent US 12,726,434
Granted Patent B2
US 12,726,434 · App. 19/004,157 · Granted Sep 1, 2026

Packet forwarding methods and apparatuses

Inventor: Tingqiao Wu (Beijing, CN)
Assignee: New H3C Technologies Co., Ltd.
H04L45/34H04L45/74H04L69/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,726,434
App. No.
19/004,157
Granted
Sep 1, 2026
Kind
B2
Abstract

This application provides a packet forwarding method and apparatus. In the embodiment, a headend releases respectively to other nodes on the current path SRv6 TE Policy source path routing and a source path control probe packet, to trigger other nodes on the current path to generate a source path control table. The source path control table contains routing forwarding information that nodes on the path of the existing SRv6 TE Policy conventionally does not care about, in order to use this source path control table to mitigate risks caused by nodes on the path of the existing SRv6 TE Policy not caring about the above routing forwarding information and improve the security of the SRv6 network.

Claims (46)

1 . A packet forwarding method, the method applied to a network node, and the method comprising:

sending, by the network node serving as a headend of an SRv6 Traffic Engineering Policy TE Policy to other nodes on a current path included in the SRv6 TE Policy, an SRv6 TE Policy source path routing; the SRv6 TE Policy source path routing carrying first routing information for forwarding packets on the current path, so that any node other than the headend on the current path, upon receiving the SRv6 TE Policy source path routing, records the first routing information carried by the SRv6 TE Policy source path routing;

sending, by the network node serving as the headend to other nodes on the current path, a source path control probe packet for probing the current path; the source path control probe packet carrying second routing information for forwarding packets on the current path, so that any node other than the headend on the current path, when recognizing that the second routing information carried by the source path control probe packet matches with the recorded first routing information, generates a source path control table that matches with the first routing information; any node other than the headend on the current path being configured to perform forwarding control on a received service packet based on the generated source path control table.

2 . The method of claim 1 , wherein the first routing information comprises: a routing identifier RouterID of the headend, a source IPv6 address used by the headend for SRv6 encapsulation, and a segment list Segment List; the Segment List containing segment identifiers SIDs of respective nodes other than the headend on the current path;

the second routing information comprises: a routing identifier RouterID of the headend, a source IPv6 address used by the headend for SRv6 encapsulation, and a segment list Segment List of the current path, the Segment List containing segment identifiers SIDs of respective nodes other than the headend on the current path.

3 . The method of claim 1 , wherein the source path control probe packet encapsulates an IPv6 primary header, an SRv6 packet header SRH, and a RouterID header;

wherein the IPv6 primary header comprises at least a source address field carrying the source IPv6 address used by the headend for SRv6 encapsulation;

the SRH comprises at least: a Routing Type field, a Next Header field, and a Segment List field; the Routing Type field carries a first value used to indicate a source path control probe packet; the Next Header field carries a second value used to indicate that a next packet header of the SRH carries the routing identifier RouterID of the headend; the Segment List field carries the Segment List of the current path including the segment identifiers SIDs of respective nodes other than the headend on the current path;

the RouterID header carries the routing identifier RouterID of the headend;

the second routing information comprises: the routing identifier RouterID of the headend carried in the RouterID header, the Segment List carried in the Segment List field, and the source IPv6 address carried in the source address field.

4 . The method of claim 1 , further comprising:

the network node serving as the headend taking a backup path of the current path in the SRv6 TE Policy as the current path when the current path is abnormal, and returning to the step of sending an SRv6 TE Policy source path routing to other nodes on the current path included in the SRv6 TE Policy.

5 . The method of claim 1 , wherein the SRv6 TE Policy source path routing further comprises: an identifier ID of the SRv6 TE Policy;

the SRv6 TE Policy ID is used so that, when any node other than the headend on the current path, upon currently receiving the SRv6 TE Policy source path routing, finds that the SRv6 TE Policy ID has not been recorded, the node associates and records the first routing information carried by the currently received SRv6 TE Policy source path routing with the SRv6 TE Policy ID; if the SRv6 TE Policy ID has already been recorded, the node deletes routing information associated with the SRv6 TE Policy ID and a source path control table matching with the routing information, and associates and records the SRv6 TE Policy ID with the first routing information carried by the currently received SRv6 TE Policy source path routing.

6 . A packet forwarding method, applied to a network node, and the method comprising:

if the network node serves as any node other than a headend of an SRv6 Traffic Engineering Policy TE Policy, then:

receiving an SRv6 TE Policy source path routing sent by a headend of the SRv6 TE Policy for a current path included in the SRv6 TE Policy; the SRv6 TE Policy source path routing carrying first routing information for forwarding packets on the current path;

recognizing whether the network node is on the current path, and if so, recording the first routing information carried by the SRv6 TE Policy source path routing;

receiving a source path control probe packet sent by the headend; the source path control probe packet carrying second routing information for forwarding packets on the current path; if recognizing that the second routing information carried by the source path control probe packet matches with the recorded first routing information, generating a source path control table that matches with the first routing information;

performing forwarding control on a service packet received by the network node based on the source path control table.

7 . The method of claim 6 , wherein the first routing information comprises at least: a Segment List; the Segment List containing segment identifiers SIDs of respective nodes other than the headend on the current path;

recognizing whether the network node is on the current path comprises: recognizing whether a segment identifier SID of the network node is in the Segment List; if so, determining that the network node is on the current path; otherwise, determining that the network node is not on the current path.

8 . The method of claim 6 , wherein the first routing information comprises: a routing identifier RouterID of the headend, a source IPv6 address used by the headend for SRv6 encapsulation, and a segment list Segment List; the Segment List containing segment identifier SIDs of respective nodes other than the headend on the current path;

the second routing information comprises: the routing identifier RouterID of the headend, the source IPv6 address used by the headend for SRv6 encapsulation, and the segment list Segment List of the current path, which comprises the segment identifiers SIDs of respective nodes other than the headend on the current path;

recognizing whether the second routing information carried by the source path control probe packet matches with the recorded first routing information comprises: if the RouterID carried by the source path control probe packet and the RouterID in the recorded first routing information meet a first preset matching requirement, the source IPv6 address carried by the source path control probe packet and the source IPv6 address in the recorded first routing information meet a second preset matching requirement, and the Segment List carried by the source path control probe packet and the Segment List in the recorded first routing information meet a third preset matching requirement, then determining that the second routing information carried by the source path control probe packet matches with the recorded first routing information.

9 . The method of claim 6 , wherein receiving a source path control probe packet sent by the headend for probing the current path comprises:

receiving a packet sent by the headend;

if a packet type carried by the packet is a first value which indicates a source path control probe packet, determining that the source path control probe packet sent by the headend has been received.

10 . The method of claim 9 , wherein the source path control probe packet encapsulates an IPv6 primary header, an SRv6 packet header SRH, and a RouterID header;

wherein the IPv6 primary header comprises at least a source address field, which carries the source IPv6 address used by the headend for SRv6 encapsulation;

the SRH comprises at least: a Routing Type field, a Next Header field, and a Segment List field; the Routing Type field carries a first value, which is used to indicate a source path control probe packet; the Next Header field carries a second value, which is used to indicate that a next packet header of the SRH carries the routing identifier RouterID of the headend; the Segment List field carries the Segment List of the current path, which comprises the segment identifiers SIDs of respective nodes other than the headend on the current path;

the RouterID header carries the routing identifier RouterID of the headend;

the second routing information comprises at least: the routing identifier RouterID of the headend carried in the RouterID header, the Segment List carried in the Segment List field, and the source IPv6 address carried in the source address field.

11 . The method of claim 10 , wherein the IPv6 primary header further comprises a destination address field; the SRH further comprises an SL field carrying SL which indicates a number of remaining segment identifiers SIDs in the Segment List, the remaining segment identifiers SIDs refer to segment identifiers SIDs corresponding to nodes that the source path control probe packet has not yet passed through;

the source path control table matched with the first routing information comprises at least: an interface where the source path control probe packet is received, the source IPv6 address carried in the source address field, the destination address carried in the destination address field, the Segment List carried by the source path control probe packet, and the SL;

performing forwarding control on a service packet received by the network node based on the source path control table comprises: checking whether an interface where the service packet is received, the source IPv6 address and the destination address encapsulated in the service packet, and the Segment List and the SL encapsulated in the service packet respectively match with the ingress interface, the source IPv6 address, the destination address, the Segment List, and the SL in the source path control table, if so, proceeding to forward the service packet; and if not, discarding the service packet.

12 . The method of claim 11 , wherein the method further comprises:

when the network node is not a last node on the current path, modifying the source path control probe packet and proceeding to forward the packet by: modifying the destination address field in the source path control probe packet to a node identifier of a next node following the network node on the current path, and updating the number in the SL field to obtain an updated number less than the number before updating by 1.

13 . The method of claim 6 , wherein the SRv6 TE Policy source path routing further comprises: an identifier ID of the SRv6 TE Policy;

the network node recording the first routing information carried by the SRv6 TE Policy source path routing comprises: recognizing whether there is routing information associated with the SRv6 TE Policy ID currently recorded; if not, associating and recording the currently received first routing information carried by the SRv6 TE Policy source path routing with the SRv6 TE Policy ID; if so, deleting the routing information associated with the SRv6 TE Policy ID and a source path control table that matches with the routing information, and associating and recording the SRv6 TE Policy ID with the first routing information carried by the current received SRv6 TE Policy source path routing.

14 . A network node which serves as a headend of an SRv6 Traffic Engineering Policy TE Policy, the network node comprising:

a transmitter, a receiver, a memory and a processor connected with the transmitter, the receiver and the memory,

wherein the processor is configured to the method of claim 1 .

15 . A network node which serves as any node other than a headend of an SRv6 Traffic Engineering Policy TE Policy, the network node comprising:

a transmitter, a receiver, a memory and a processor connected with the transmitter, the receiver and the memory,

wherein the processor is configured to perform the method of claim 6 .

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 27, 2024
From: WU, TINGQIAO
To: NEW H3C TECHNOLOGIES CO., LTD.
Reel/Frame 069693/0571 →
Priority Claims (1)
CN 202411768870.3 · Dec 3, 2024 · national
Continuity (1)
Related Publication 20260156070A1 · Jun 4, 2026
References Cited (17)
US 12537761B2 · Zhang · 2026 [cited by examiner]
US 20180359176A1 · Nainar · 2018 [cited by examiner]
US 20220182326A1 · Gamage · 2022 [cited by examiner]
US 20240106740A1 · Chang et al. · 2024 [cited by applicant]
US 20250175416A1 · Valceanu · 2025 [cited by examiner]
US 20250254120A1 · Hu · 2025 [cited by examiner]
CN 113206790A · 2021 [cited by applicant]
CN 113497800A · 2021 [cited by applicant]
CN 117997625A · 2024 [cited by applicant]
WO 2022199486A1 · 2022 [cited by applicant]
WO 2023179174A1 · 2023 [cited by applicant]
WO 2023179656A1 · 2023 [cited by applicant]
Mianzu, “SRv6—Message Forwarding Process”, CSDN blog, https://blog.csdn.net/qq_33681684/article/details/127182706, Oct. 22, 2022. [cited by applicant]
Cisco, “Configure Design and Migration Best Practices for Segment Routing over IPv6”, https://www.cisco.com/c/en/us/support/docs/ip/ipv6-routing/220485-configure-design-and-migration-best-prac.html, Jun. 1, 2023. [cited by applicant]
Extended European Search Report for EP 24223566.1 by European Patent Office dated May 22, 2025. [cited by applicant]
Li, Xueting et al., “Segment Routing Policy-Based Source Address Validation (SAV) Mechanism draft-li-savnet-srsav-00”, Internet Draft submitted to Internet Engineering Task Force, XP15169708A, Sep. 2024. [cited by applicant]
Yang, Feng et al., “SID as source address in SRv6 draft-yang-spring-sid-as-source-address-03”, Internet Draft submitted to Internet Engineering Task Force, XP015164445, Jan. 2024. [cited by applicant]