# US 12,764,066 B2 · Message sending > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,764,066 B2 - Document ID: US12764066B2 - Status: Granted - Kind: B2 - Application number: 18/714,687 - Filed: 2022-06-28 - Published: 2025-01-23 - Granted: 2026-10-13 - Earliest claimed: 2022-06-28 - Assignees: New H3C Technologies Co., Ltd. - Applicants: New H3C Technologies Co., Ltd. - Inventors: Hao Li - Web page: https://patentgrep.com/patent/US12764066B2 ## CPC - H04L 45/74: Address processing for routing - H04L 69/22: Parsing or analysis of headers - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract The present disclosure provides message sending and relates to the technical field of communications. The solutions of the present disclosure include: receiving a first service message, which comprises a destination address, a first in-situ flow detection option, a segment routing header (SRH) and an original service message, and the SRH comprises an SID list indicating a forwarding path; if the destination address is a locally configured proxy SID, sending a second service message on the forwarding path, and sending the original service message to a service function node; wherein, the second service message comprises a second in-situ flow detection option, which comprises replication flag information for indicating that the second service message is a replication message of the first service message. The in-situ flow detection can be performed on the forwarding path without affecting service chain services. ## Claims ### Claim 1 A method for message sending, which is applied to a network device, comprising: receiving a first service message, which comprises a destination address, a first in-situ flow detection option, a segment routing header (SRH) and an original service message, wherein the SRH comprises a Segment ID (SID) list indicating a forwarding path, the first in-situ flow detection option is used to determine whether the first service message is sent on the forwarding path, or is replicated to obtain a second service message; if the destination address is a locally configured proxy SID, sending the second service message on the forwarding path and sending the original service message to a Service Function (SF) node; wherein, the second service message comprises a second in-situ flow detection option, which comprises replication flag information for indicating that the second service message is a replication message of the first service message. ### Claim 2 (depends on 1) The method of claim 1, wherein before sending the second service message on the forwarding path, the method further comprises: determining whether the first in-situ flow detection option comprises the replication flag information; if the first in-situ flow detection option comprises the replication flag information, sending the first service message on the forwarding path; if the first in-situ flow detection option does not comprise the replication flag information, replicating the first service message and adding the replication flag information into the in-situ flow detection option of the replicated first service message, to obtain the second service message. ### Claim 3 (depends on 2) The method of claim 2, wherein before sending the first service message on the forwarding path, the method further comprises: determining whether the destination address is a last SID in the SID list; if the destination address is the last SID in the SID list, discarding the first service message; if the destination address is not the last SID in the SID list, sending the first service message on the forwarding path. ### Claim 4 (depends on 1) The method of claim 1, wherein before sending the second service message on the forwarding path, the method further comprises: obtaining a link state of a link between the network device and the service function node; if the link state is inaccessible, discarding the first service message; if the link state is accessible, replicating the first service message and adding the replication flag information into the in-situ flow detection option of the replicated first service message, to obtain the second service message. ### Claim 5 (depends on 4) The method of claim 4, wherein the obtaining the link state of the link between the network device and the service function node, specifically comprises: obtaining the link state of the link between the network device and the service function node from a data plane; wherein, if the service function node fails and/or the link between the network device and the service function node fails, the link state is inaccessible; if the service function node does not fail and the link between the network device and the service function node does not fail, the link state is accessible. ### Claim 6 (depends on 1) The method of claim 1, wherein the in-situ flow detection option of the second service message comprises a reserved field carrying the replication flag information. ### Claim 7 (depends on 1) A non-transitory, machine-readable storage medium having stored thereon machine executable instructions that, when invoked and executed by a processor, cause the processor to implement the method of claim 1. ### Claim 8 (depends on 1) A non-transitory computer program product, which causes a processor to implement the method of claim 1. ### Claim 9 A network device, comprising: a processor; a transceiver; a machine-readable storage medium storing machine executable instructions that can be executed by the processor and cause the processor to implement the following steps: receiving, by the transceiver, a first service message, which comprises a destination address, a first in-situ flow detection option, a segment routing header (SRH) and an original service message, wherein the SRH comprises an SID list indicating a forwarding path, the first in-situ flow detection option is used to determine whether the first service message is sent on the forwarding path, or is replicated to obtain a second service message; if the destination address is a locally configured proxy SID, sending, by the transceiver, the second service message on the forwarding path and the original service message to a service function node; wherein, the second service message comprises a second in-situ flow detection option, which comprises replication flag information for indicating that the second service message is a replication message of the first service message. ### Claim 10 (depends on 9) The network device of claim 9, wherein the machine executable instructions further cause the processor to execute the following steps: determining whether the first in-situ flow detection option comprises the replication flag information; if the first in-situ flow detection option comprises the replication flag information, sending, by the transceiver, the first service message on the forwarding path; if the first in-situ flow detection option does not comprise the replication flag information, replicating the first service message and adding the replication flag information into the in-situ flow detection option of the replicated first service message, to obtain the second service message. ### Claim 11 (depends on 10) The network device of claim 10, wherein the machine executable instructions further cause the processor to execute the following steps: determining whether the destination address is a last SID in the SID list; if the destination address is the last SID in the SID list, discarding the first service message; if the destination address is not the last SID in the SID list, sending, by the transceiver, the first service message on the forwarding path. ### Claim 12 (depends on 9) The network device of claim 9, wherein the machine executable instructions further cause the processor to execute the following steps: obtaining a link state of a link between the network device and the service function node; if the link state is inaccessible, discarding the first service message; if the link state is accessible, replicating the first service message and adding the replication flag information into the in-situ flow detection option of the replicated first service message, to obtain the second service message. ### Claim 13 (depends on 12) The network device of claim 12, wherein the machine executable instructions further cause the processor to execute the following steps: obtaining the link state of the link between the network device and the service function node from a data plane; wherein, if the service function node fails and/or the link between the network device and the service function node fails, the link state is inaccessible; if the service function node does not fail and the link between the network device and the service function node does not fail, the link state is accessible. ### Claim 14 (depends on 9) The network device of claim 9, wherein the in-situ flow detection option of the second service message comprises a reserved field carrying the replication flag information.