IP Library Granted Patent US 10,855,586
Granted Patent B2
US 10,855,586 · App. 16/120,014 · Granted Dec 1, 2020

Packet processing method and system, and device

Inventor: Changjiang Yan (Beijing, CN)
Assignee: Huawei Technologies Co., Ltd.
H04L45/74H04L45/306H04L45/38H04L45/50H04L45/64H04L45/66H04L47/19H04L61/2007H04L61/6022
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 10,855,586
App. No.
16/120,014
Granted
Dec 1, 2020
Kind
B2
Abstract

The application disclose a packet processing method that includes: receiving, by a service distribution node, service routing information sent by a controller, where the service routing information includes a flow identifier, a service identifier, and a next-hop address, the flow identifier is used to identify a packet flow, the service identifier is used to identify a sequence of a service node instance that processes the packet flow, and the next-hop address is used to identify the service node instance that processes the packet flow; receiving a first packet; acquiring a first flow identifier according to the first packet, and searching the service routing information according to the first flow identifier to acquire a matched service identifier and a matched next-hop address; and sending a second packet to a first service node instance that has the matched next-hop address, which implements service processing on a packet flow.

Claims (27)

1. A method, comprising:

obtaining, by a controller, a first flow identifier, a first service identifier, and a first next-hop address, wherein the first flow identifier uniquely identifies a packet flow, the first service identifier is uniquely allocated to the packet flow, the first service identifier identifies a sequence of a plurality of service node instances that process the packet flow, and the first next-hop address identifies the address of a first service node instance of the plurality of service node instances that processes the packet flow; and

sending, by the controller, the first flow identifier, the first service identifier and the first next-hop address to a service distribution node.

2. The method according to claim 1 , further comprising:

obtaining, by the controller, a second next-hop address, wherein the second next-hop address identifies the address of the first service node instance that processes the packet flow; and

sending, by the controller, the first service identifier and the second next-hop address to a second service node instance.

3. The method according to claim 1 , wherein the first flow identifier comprises 5-tuple information of the packet flow.

4. The method according to claim 1 , wherein the address of the first service node instance is an IP address of the first service node instance.

5. A controller, comprising:

a processor; and

a transmitter;

wherein the processor is configured to:

obtain a first flow identifier, a first service identifier, and a first next-hop address, wherein the first flow identifier uniquely identifies a packet flow, the first service identifier is uniquely allocated to the packet flow, the first service identifier identifies a sequence of a plurality of service node instances that process the packet flow, and the first next-hop address identifies an address of a first service node instance of the plurality of service node instances that processes the packet flow; and

wherein the transmitter is configured to send the first flow identifier, the first service identifier, and the first next-hop address to a service distribution node.

6. The controller according to claim 5 , wherein the processor is further configured to:

obtain a second next-hop address, wherein the second next-hop address identifies the address of the first service node instance that processes the packet flow; and

wherein the transmitter is further configured to send the first service identifier and the second next-hop address to a second service node instance of the plurality of service node instances.

7. The controller according to claim 5 , wherein the first flow identifier comprises 5-tuple information of the packet flow.

8. The controller according to claim 5 , wherein the address of the first service node instance is an IP address of the first service node instance.

9. A non-transitory computer readable storage medium storing instructions that, when executed by a processor, cause a computer to:

obtain a first flow identifier, a first service identifier, and a first next-hop address, wherein the first flow identifier uniquely identifies a packet flow, the first service identifier is uniquely allocated to the packet flow, the first service identifier identifies a sequence of a plurality of service node instances that process the packet flow, and the first next-hop address identifies an address of a first service node instance of the plurality of service node instances that processes the packet flow; and

send, using a transmitter, the first flow identifier, the first service identifier, and the first next-hop address to a service distribution node.

10. The non-transitory computer readable storage medium according to claim 9 , wherein the instructions, when executed by the processor, further cause the computer to:

obtain a second next-hop address, wherein the second next-hop address identifies the address of the first service node instance that processes the packet flow; and

send, using the transmitter, the first service identifier and the second next-hop address to a second service node instance of the plurality of service node instances.

11. The non-transitory computer readable storage medium according to claim 9 , wherein the first flow identifier comprises 5-tuple information of the packet flow.

12. The non-transitory computer readable storage medium according to claim 9 , wherein the address of the first service node instance is an IP address of the first service node instance.

Continuity (3)
Division 14854872 · Sep 15, 2015
Continuation PCTCN2013072724 · Mar 15, 2013
Related Publication 20190020584A1 · Jan 17, 2019