# US 11,909,633 B2 · Packet processing method, device, and system > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 11,909,633 B2 - Document ID: US11909633B2 - Status: Granted - Kind: B2 - Application number: 17/536,507 - Filed: 2021-11-29 - Published: 2022-03-17 - Granted: 2024-02-20 - Earliest claimed: 2015-09-22 - Assignees: Huawei Technologies Co., Ltd. - Applicants: Huawei Technologies Co., Ltd. - Inventors: Shunwan Zhuang; Zhenbin Li; Shuanglong Chen; Guoyi Chen; Jia Che; Nan Wu - Web page: https://patentgrep.com/patent/US11909633B2 ## CPC - H04L 12/4641: {Virtual LANs, VLANs, e.g. virtual private networks [VPN] (LAN interconnection over a bridge based backbone H04L12/462; encapsulation techniques H04L12/4633; routing of packets H04L45/00; packet switches H04L49/00; virtual private networks for security H04L63/0272)} - H04L 45/507: {Label distribution} - H04L 47/825: {Involving tunnels, e.g. MPLS} - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract The present disclosure discloses a packet processing method, device, and system. The system includes: a controller, configured to: allocate a service label to a service processing manner of an FEC, establish a mapping relationship between the service label and the service processing manner, send the service label to a source node, and send the mapping relationship to a destination node; the source node, configured to: receive the service label sent by the controller, receive a first packet, insert the service label to the first packet to obtain a second packet, and send the second packet to the destination node; the destination node, configured to: receive the mapping relationship sent by the controller, receive the second packet sent by the source node, and pop the service label from the second packet according to the mapping relationship, to obtain the first packet. ## Claims ### Claim 1 A method for processing packets, comprising: allocating, by a controller, a service label corresponding to a service processing manner of a forwarding equivalence class (FEC) and a path, wherein the controller also establishes a mapping relationship between the service label and the service processing manner; sending, by the controller, the service label to a source node of the path to enable the source node to insert the service label to a first packet to obtain a second packet to be forwarded along the path to a destination node, wherein the service label is used to instruct a network node on the path to perform service processing on the second packet according to the service processing manner; and sending, by the controller, the mapping relationship to the destination node to enable the destination node to pop the service label from the second packet to obtain the first packet. ### Claim 2 (depends on 1) The method according to claim 1, further comprising: binding, by the controller, the service label to routing information corresponding to the path; and sending, by the controller, the routing information bound with the service label to the source node. ### Claim 3 (depends on 1) The method according to claim 1, further comprising: sending, by the controller, the service label to the destination node of the path to enable the destination node to perform service processing according to the service label. ### Claim 4 (depends on 1) The method according to claim 1, wherein the service label comprises a source label, segment identifier (SID), an entropy label, a quality of service (QoS) label, a steering label, a virtual private network (VPN) prefix label, a VPN label, or a color label. ### Claim 5 (depends on 1) The method according to claim 1, wherein the service label is a bottom label in a label stack of the second packet. ### Claim 6 (depends on 1) The method according to claim 1, wherein the path is a segment routing (SR) path. ### Claim 7 (depends on 1) The method according to claim 1, wherein the service processing manner comprises: performing load sharing processing on a packet; performing source identification processing on a packet; or performing packet coloring processing. ### Claim 8 (depends on 1) The method according to claim 1, wherein the path comprises the network node and the destination node. ### Claim 9 A method for processing packet, comprising: receiving, by a source node of a path, a service label corresponding to a service processing manner of a forwarding equivalence class (FEC) and the path; receiving, by a destination node of the path, a mapping relationship between the service label and the service processing manner; receiving, by the source node, a first packet; inserting the service label to the first packet to generate a second packet; and sending, by the source node, the second packet to the destination node corresponding to the path, wherein the service label is used to instruct a network node on the path to perform service processing on the second packet according to the service processing manner; and receiving the second packet at the destination node, wherein the destination node is enabled, based on the mapping relationship, to pop the service label from the second packet to obtain the first packet. ### Claim 10 (depends on 9) The method according to claim 9, wherein the receiving a service label comprises: receiving, by the source node, routing information corresponding to the path from a controller; and obtaining, by the source node, the service label from the routing information. ### Claim 11 (depends on 9) The method according to claim 9, wherein the service label is a bottom label in a label stack of the second packet. ### Claim 12 (depends on 9) The method according to claim 9, wherein the service label comprises a source label, segment identifier (SID), an entropy label, a quality of service (QoS) label, a steering label, a virtual private network (VPN) prefix label, a VPN label, or a color label. ### Claim 13 A controller, comprising: at least one processor; one or more memories coupled to the at least one processor and storing instructions, which when by the at least one processor, cause the controller to: allocate a service label corresponding to a service processing manner of a forwarding equivalence class (FEC) and a path; establish a mapping relationship between the service label and the service processing manner; send the service label to a source node of the path to enable the source node to insert the service label to a first packet to obtain a second packet to be forwarded along the path to a destination node, wherein the service label is used to instruct a network node on the path to perform service processing on the second packet according to the service processing manner; and send the mapping relationship to the destination node, wherein the destination node is enabled to pop the service label from the second packet to obtain the first packet based on the mapping relationship. ### Claim 14 (depends on 13) The controller according to claim 13, wherein the instructions, when executed by the at least one processor, further cause the controller to: bind the service label to routing information corresponding to the path; and send the routing information bound with the service label to the source node. ### Claim 15 (depends on 13) The controller according to claim 13, wherein the instructions, when executed by the at least one processor, further cause the controller to: send the service label to a destination node of the path to enable the destination node to perform service processing according to the service label. ### Claim 16 (depends on 13) The controller according to claim 13, wherein the service label comprises a source label, segment identifier (SID), an entropy label, a quality of service (QoS) label, a steering label, a virtual private network (VPN) prefix label, a VPN label, or a color label. ### Claim 17 A source node device, comprising: at least one processor; one or more memories coupled to the at least one processor and storing instructions, which when executed by the at least one processor, cause the at least one processor to: receive a service label corresponding to a service processing manner of a forwarding equivalence class (FEC) and a path, wherein the source node device is a source node of the path; receive a first packet; insert the service label to the first packet to generate a second packet; and send the second packet to a destination node corresponding to the path, wherein the service label is used to instruct a network node on the path to perform service processing on the second packet according to the service processing manner, and wherein the destination node is enabled to pop the service label from the second packet to obtain the first packet based on a mapping relationship between the service label and the service processing manner. ### Claim 18 (depends on 17) The source node device according to claim 17, wherein the instructions, when executed by the at least one processor, cause the at least one processor to: receiving routing information corresponding to the path from a controller; and obtaining the service label from the routing information. ### Claim 19 (depends on 17) The source node device according to claim 17, wherein the service label comprises a bottom label in a label stack of the second packet. ### Claim 20 (depends on 17) The source node device according to claim 17, wherein the service label comprises a source label, segment identifier (SID), an entropy label, a quality of service (QoS) label, a steering label, a virtual private network (VPN) prefix label, a VPN label or a color label.