IP Library › Granted Patent US 12,470,470
Granted Patent B2
US 12,470,470 · App. 18/164,301 · Granted Nov 11, 2025

Load balancing and OAM in service function chaining using multiprotocol label switching

Inventors: Gregory Mirsky (Pleasanton, CA); Yao Liu (Shenzhen, CN)
Assignee: ZTE Corporation
H04L43/106H04L47/125
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,470,470
App. No.
18/164,301
Granted
Nov 11, 2025
Kind
B2
Abstract

Disclosed are devices, systems and methods for load balancing and operation, administration and maintenance (OAM) in service function chaining using the multiprotocol label switching (MPLS) forwarding plane. In some implementations, a packet processing method includes processing a network packet comprising a plurality of labels based on presence of an indicator label in the plurality of labels such that in case that the indicator label is present in the network packet, the indicator label is used to determine a first destination of a payload of the network packet, and in case that the indicator label is not present in the network packet, the payload is passed to a second destination selected based on a service function indicator in the plurality of labels.

Claims (29)

1 . A packet processing method, comprising:

processing a packet comprising a payload and a plurality of labels based on presence of an indicator label for indicating that the packet is a test packet, in the plurality of labels;

upon determination that the indicator label is present indicating that the packet is a test packet, continuing processing of the packet without passing the packet to a destination; and

upon determination that the indicator label is not present to indicate that the packet is not a test packet, passing the packet to the destination.

2 . The method of claim 1 , wherein the test packet includes an operation, administration, and maintenance (OAM) network test packet generated to monitor a service function path.

3 . The method of claim 1 , wherein the destination includes a service function selected based on a service function indicator in the plurality of labels.

4 . The method of claim 3 , wherein the service function indicator includes at least one of a service function (SF) label or a service function chaining (SFC) context label.

5 . The method of claim 4 , wherein the service function is selected based on a service index label in the service function (SF) label.

6 . The method of claim 4 , wherein the service function is selected based on the service function chaining (SFC) context label.

7 . The method of claim 1 , wherein the plurality of labels is assigned to the payload and includes a service function (SF) label and a service function chaining (SFC) context label, wherein the indicator label, the service function (SF) label and the service function chaining (SFC) context label are stacked on top of each other, and wherein the indicator label is arranged between the service function label and the service function chaining context label.

8 . The method of claim 2 , wherein the indicator label includes a generic associated label (GAL) to indicate a generic associated channel over which the OAM test packet is exchanged.

9 . The method of claim 8 , wherein the destination includes a service function forwarder different from a current service function forwarder.

10 . The method of claim 8 , wherein the destination includes a control plane associated with a current service function forwarder.

11 . The method of claim 1 , wherein the indicator label includes an entropy label indicator (ELI) and an entropy label.

12 . The method of claim 11 , wherein the packet is passed to a service function selected based on at least one of the entropy label indicator (ELI) and the entropy label.

13 . A data communication method, comprising:

receiving a packet including a payload and a plurality of labels that includes a service path identifier label and a service function label;

determining whether the plurality of labels includes at least one of a first label indicating a channel for exchanging a test packet or a second label including a load balancing information;

upon determination that the first label is present indicating that the packet is a test packet, processing the packet without passing the packet to a destination; and

upon determination that the first label is not present to indicate that the packet is not a test packet, passing the packet to the destination.

14 . The method of claim 13 , wherein the data packet includes an operation, administration, and maintenance (OAM) test packet generated to monitor a service function path.

15 . The method of claim 14 , further comprising, upon passing the payload to the service function selected, decrementing a time-to-live value of a service index label in the service function label.

16 . The method of claim 15 , wherein the indicator label includes a generic associated label (GAL) configured to indicate a generic associated channel over which the OAM test packet is exchanged.

17 . The method of claim 13 , wherein the second label includes an entropy label indicator (ELI) and an entropy label.

18 . The method of claim 17 , further comprising, upon determination that the plurality of labels includes the second label:

selecting a service function as the destination based on a value of the entropy label; and

passing the data packet to the selected service function.

19 . The method of claim 18 , wherein the selecting of the service function is based on a balance of load among a plurality of service functions of a same type mapped to a service function forwarder.

20 . The method of claim 13 , further comprising, upon determination that the plurality of labels does not include any of the first and second labels, dropping the data packet.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 3, 2023
From: MIRSKY, GREGORY; LIU, YAO
To: ZTE CORPORATION
Reel/Frame 062588/0175 →
Continuity (2)
Continuation PCTCN2020116709 · Sep 22, 2020
Related Publication 20230188449A1 · Jun 15, 2023
References Cited (19)
US 8804736B1 · Drake et al. · 2014 [cited by applicant]
US 9300579B2 · Frost et al. · 2016 [cited by applicant]
US 10263887B2 · Patil · 2019 [cited by examiner]
US 20120163190A1 · Jocha et al. · 2012 [cited by applicant]
US 20170366461A1 · Wu · 2017 [cited by examiner]
US 20180091420A1 · Drake · 2018 [cited by examiner]
US 20180295053A1 · Leung et al. · 2018 [cited by applicant]
US 20200153716A1 · Nainar · 2020 [cited by examiner]
US 20200358698A1 · Song · 2020 [cited by examiner]
CN 102577260A · 2012 [cited by applicant]
CN 111213345A · 2020 [cited by applicant]
WO 2020181636A1 · 2020 [cited by applicant]
Farrel, A. et al., “An MPLS-Based Forwarding Plane for Service Function Chaining,” MPLS Working Group, Internet-Draft, draft-ietf-mpls-sfc-05, Aug. 16, 2019 (57 pages). [cited by applicant]
Office Action for Chinese Patent Application No. 202080103020.5, mailed Jul. 9, 2024 (18 pages). [cited by applicant]
Farrel, A. et al. “An MPLS-Based Forwarding Plane for Service Function Chaining,” 1-25 Internet Engineering Task Force (IETF), Request for Comments: 8595, Jun. 30, 2019. [cited by applicant]
International Search Report and Written Opinion for International Application No. PCT/CN2020/116709, mailed on Jun. 25, 2021 (9 pages). [cited by applicant]
Extended European Search Report for European Patent Application No. 20954343.8, mailed Sep. 19, 2023 (11 pages). [cited by applicant]
Farrel, A. et al., “An MPLS-Based Forwarding Plane for Service Function Chaining draft-ietf-mpls-sfc-05,” MPLS Working Group, Feb. 12, 2019 (29 pages). [cited by applicant]
CNIPA, Notification to Complete Formalities of Registration for Chinese Application No. 202080103020.5, mailed on Mar. 17, 2025, 4 pages with unofficial English translation. [cited by applicant]