Traffic classifier, service routing trigger, and packet processing method and system

Patent metadata

Field	Value
Publication number	US-10735309-B2
Application number	US-201514924499-A
Country	US
Kind code	B2
Filing date	Oct 27, 2015
Priority date	Apr 28, 2013
Publication date	Aug 4, 2020
Grant date	Aug 4, 2020

Abstract

A packet processing method includes: a traffic classifier receives a first packet; the traffic classifier determines, in policy information in the traffic classifier and according to a first filtering rule that matches the first packet, a first service identifier that matches the first filtering rule, and an address, which matches the first filtering rule, of a first service routing trigger. The traffic classifier sends a second packet to the first service routing trigger. Where the policy information includes: a filtering rule, an address of a service routing trigger, and a service identifier corresponding to the filtering rule. Where the filtering rule is used to identify a packet, and the service identifier is used to represent a sequence of a service node that processes the packet. Where the second packet is formed by adding the first service identifier to the first packet.

First claim

What is claimed is:

1. A packet processing system, comprising:
a traffic classifier; and
a first service routing trigger;
wherein the traffic classifier is configured to receive first policy information from a controller;
wherein the first policy information comprises a filtering rule, an address that corresponds to the filtering rule and that is of a service routing trigger, and a service identifier corresponding to the filtering rule, wherein the filtering rule is used to identify a packet, and wherein the service identifier is a Multiprotocol Label Switching (MPLS) label and represents a sequence of service nodes that will process the packet;
wherein the first service routing trigger is configured to receive second policy information from the controller, wherein the second policy information comprises the service identifier and a service node sequence corresponding to the service identifier;
wherein the traffic classifier is further configured to:
receive a first packet that excludes the service identifier, wherein the service identifier does not include a source address (SA);
determine, in the first policy information and according to a first filtering rule that matches the first packet, that the service identifier matches the first filtering rule, and determine an address that matches the first filtering rule and is of the first service routing trigger;
add the service identifier to the first packet to form a second packet, wherein an existing field used to indicate, in a header of the packet, a portion of a source media access control (MAC) address is reused to have a value indicating the existence of the service identifier; and
send the second packet to the first service routing trigger; and

wherein the first service routing trigger is further configured to:
determine, in the second policy information and according to the service identifier carried in the second packet, a first service node sequence that matches the service identifier;
send the second packet to a first service node in the first service node sequence;
receive the second packet processed by the first service node; and
trigger, according to an order of service nodes in the first service node sequence, a second service node in the first service node sequence after the first service node to process the second packet.

2. The system according to claim 1 , wherein the first policy information further comprises a tenant identifier; and
wherein the service identifier corresponds to the filtering rule and the tenant identifier.

3. The system according to claim 2 , wherein the traffic classifier is further configured to:
determine, in the first policy information and according to a first tenant identifier corresponding to the first filtering rule and the first packet, the service identifier that matches the first filtering rule and the first tenant identifier, and determine an address that matches the first filtering rule and the first tenant identifier and is of the first service routing trigger.

4. The system according to claim 1 , wherein the second policy information further comprises an address of a next-hop node of the service node sequence corresponding to the service identifier.

5. A packet processing system, comprising:
a traffic classifier;
a first service routing trigger; and
a second service routing trigger;
wherein the traffic classifier is configured to receive first policy information from a controller, wherein the first policy information comprises a filtering rule, an address that corresponds to the filtering rule and that is of a service routing trigger, and a service identifier corresponding to the filtering rule, wherein the filtering rule is used to identify a packet, and wherein the service identifier is a Multiprotocol Label Switching (MPLS) label and represents a sequence of service nodes that processes the packet;
wherein the first service routing trigger is configured to receive second policy information from the controller, wherein the second policy information comprises the service identifier, and a first part that is triggered by the first service routing trigger and is of a service node sequence corresponding to the service identifier;
wherein the second service routing trigger is configured to receive third policy information from the controller, wherein the third policy information comprises the service identifier, and a second part that is triggered by the second service routing trigger and is of the service node sequence corresponding to the service identifier;
wherein the traffic classifier is further configured to:
receive a first packet that excludes the service identifier, wherein the service identifier does not include a source address (SA);
determine, in the first policy information and according to a first filtering rule that matches the first packet, that the service identifier matches the first filtering rule;
determine an address that matches the first filtering rule and is of the first service routing trigger;
determine an address that matches the first filtering rule and is of the second service routing trigger;
add the service identifier to the first packet to form a second packet, wherein an existing field used to indicate, in a header of the packet, a portion of a source media access control (MAC) address is reused to have a value indicating the existence of the service identifier;
send the second packet to the first service routing trigger,
determine, in the second policy information and according to the service identifier carried in the second packet, a first service node sequence that matches the service identifier;
send the second packet to a first service node in the first service node sequence;
receive the second packet processed by the first service node; and
trigger, according to an order of service nodes in the first service node sequence, a second service node in the first service node sequence after the first service node to process the second packet.

6. The system according to claim 5 , wherein the first policy information further comprises a tenant identifier; and
wherein the service identifier corresponds to the filtering rule and the tenant identifier.

7. The system according to claim 6 , wherein the traffic classifier is further configured to:
determine, in the first policy information and according to a first tenant identifier corresponding to the first filtering rule and the first packet, the service identifier that matches the first filtering rule and the first tenant identifier; and
determine the address that matches the first filtering rule and is of the first service routing trigger.

8. The system according to claim 5 , wherein the second policy information further comprises an address of a next-hop node of the service node sequence corresponding to the service identifier.

9. A packet processing method, comprising:
receiving, by a traffic classifier, a first packet that excludes a service identifier;
determining, by the traffic classifier, in policy information stored in the traffic classifier and according to a first filtering rule that matches the first packet, that the service identifier matches the first filtering rule, and determining an address that matches the first filtering rule and is of a first service routing trigger, wherein the service identifier does not include a source address (SA), wherein the policy information comprises: a filtering rule, the address of the first service routing trigger, and the service identifier corresponding to the filtering rule, wherein the filtering rule is used to identify a packet, and wherein the service identifier is a Multiprotocol Label Switching (MPLS) label and represents a sequence of service nodes that p

Assignees

• Huawei Tech Co Ltd

Inventors

• Wu Dongjun
• Yan Changjiang
• Huang Shibi

Classifications

• H04L41/5054 Primary

  Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components · CPC title

• H04L45/306

  Route determination based on the nature of the carried application · CPC title

• H04L43/028

  by filtering · CPC title

• H04L45/22 Primary

  Alternate routing · CPC title