WO2015172675A1

WO2015172675A1 - Packet processing method and device

Info

Publication number: WO2015172675A1
Application number: PCT/CN2015/078508
Authority: WO
Inventors: 徐卫平; 牛乐宏
Original assignee: 华为技术有限公司
Priority date: 2014-05-15
Filing date: 2015-05-08
Publication date: 2015-11-19
Also published as: CN105099919B; CN105099919A

Abstract

Disclosed are a packet processing method and device, which solve the problem that an SF node is unable to process a packet comprising a service header. The method comprises: receiving, by a packet processing device, a first packet from a service forwarding entity (SFE), wherein the first packet comprises a second packet and a service header encapsulated in the second packet, and the service header in the first packet comprises a path identifier (ID) of a service chain; acquiring, by the packet processing device, the second packet and the path ID; processing, by the packet processing device, the second packet according to the path ID to acquire a third packet, wherein processing the second packet comprises: adding a first parameter into the second packet, the first parameter being a parameter determined according to the path ID; and sending, by the packet processing device, the third packet to a service function (SF) node.

Description

Message processing method and device

This application claims the priority of the Chinese Patent Application, filed on May 15, 2014, which is hereby incorporated by reference. .

Technical field

The present invention relates to communication technologies, and in particular, to a message processing method and apparatus.

Background technique

In addition to providing basic switching, routing and other forwarding functions, the usual network equipment can also provide value-added services (English name is Value-Added Service, abbreviated as VAS), for example, network address translation (English name is Network Address Translation, English) Abbreviated as NAT), firewall and other services.

In the network providing value-added services, the service chain (English name is service chain) includes a service classifier (English name is service classifier) and N service forwarding entities (English full name is service forwarding entity, English abbreviation is SFE). The SFEs included in the service chain are connected in sequence. One or more service functions (English full service function, English abbreviated as SF) nodes can be connected to the SFE. The SF node is configured to perform service processing on the received packet. For example, the SF node has functions such as a NAT function and a firewall.

The service classifier on the service chain adds a service header to the received packet according to the service type corresponding to the received packet. The service header includes the path identifier of the service chain corresponding to the service type (English name is Identifier, English abbreviation is ID). The service classifier sends a packet including the service header to the SFE connected to the service classifier. The SFE sends a packet including the service header to the SF node connected to the SFE. The SF node cannot identify the packet including the service header, and thus cannot perform service processing on the packet including the service header.

Summary of the invention

In view of this, the embodiment of the present invention provides a packet processing method and device, which solves the problem that an SF node cannot process a packet including a service header.

The technical solutions provided by the embodiments of the present invention are as follows.

In a first aspect, a packet processing method is provided, including:

The packet processing apparatus receives the first packet from the SFE, where the first packet includes a second packet and a service header encapsulated in the second packet, where the service header is in the first packet Including the path ID of the service chain;

The message processing apparatus acquires the second packet and the path ID;

The packet processing apparatus processes the second packet according to the path ID to obtain a third packet, where the processing of the second packet includes: adding a first parameter to the In the second packet, the first parameter is a parameter determined according to the path ID;

The message processing apparatus sends the third message to the SF node.

In the first possible implementation manner of the foregoing first aspect, the method further includes:

The message processing apparatus receives a fourth packet from the SF node, where the fourth packet includes the first parameter;

The packet processing device acquires the path ID according to the first parameter included in the fourth packet;

The message processing apparatus acquires the fifth packet by processing the fourth packet according to the path ID obtained by the packet processing apparatus after receiving the fourth packet, where the The processing of the fourth packet includes: determining the service header according to the path ID, and encapsulating the fourth packet by using the service header;

The message processing apparatus sends the fifth message to the SFE.

In conjunction with the first possible implementation of the foregoing first aspect, a second possible implementation of the first aspect is also provided, including:

The packet processing device determines, according to the identifier of the interface that receives the first packet, that the third packet is forwarded according to the forwarding entry, where the forwarding entry includes the interface that receives the first packet. The identifier and the identifier of the first interface;

The packet processing apparatus sends the third packet to the SF node by using the first interface.

In conjunction with the second possible implementation of the foregoing first aspect, a third possible implementation manner of the first aspect is further provided, where the forwarding entry further includes the path ID;

The packet processing apparatus determines, according to the identifier of the interface that receives the first packet, that the third packet is forwarded according to the forwarding entry, and includes:

The packet processing apparatus determines, according to the path ID and the identifier of the interface that receives the first packet, that the third packet is forwarded according to the forwarding entry.

In conjunction with the second possible implementation of the foregoing first aspect, the fourth possible implementation of the first aspect is further provided, the forwarding entry further includes a second parameter, where the second parameter is used to identify the An SF node or a SF node of the SF node on the service chain;

When the service header in the first packet includes the second parameter, the packet processing apparatus determines, according to the identifier of the interface that receives the first packet, that the third packet is forwarded according to the forwarding entry. include:

The packet processing apparatus determines to forward the third packet according to the forwarding entry according to the second parameter carried in the first packet and the identifier of the interface that receives the first packet. .

In conjunction with the fourth possible implementation of the foregoing first aspect, a fifth possible implementation of the first aspect is also provided, including:

The message processing apparatus adds the second parameter to the traffic header.

In conjunction with the foregoing first aspect or any one of the foregoing possible implementation manners, the sixth possible implementation manner of the first aspect is further provided, where the service header in the first packet further includes a third parameter, where The third parameter is used to identify that the first packet is an operation, management, and maintenance (English full name operation, administration and maintenance, English abbreviation is OAM) message;

Before the packet processing apparatus sends the third packet to the SF node, the method further includes:

When the packet processing apparatus determines that the first packet includes the third parameter, and the forwarding policy is to send an OAM packet from the SFE to the SF node, send the Third message.

In combination with any of the above first aspect or any one of the possible implementations of the first aspect, In a seventh possible implementation manner, the first parameter is the path ID, or the first parameter is data obtained by processing the path ID according to an algorithm.

In a second aspect, a message processing apparatus is provided, including:

a first receiving unit, configured to receive a first packet from the SFE, where the first packet is a packet obtained after the service header is encapsulated in the second packet, where the service header is in the first packet Including the path ID of the service chain;

Decapsulating unit, configured to acquire the second packet and the path ID;

a first acquiring unit, configured to process the second packet according to the path ID, to obtain a third packet, where the processing performed by the first acquiring unit on the second packet includes: The first obtaining unit adds a first parameter to the second packet, where the first parameter is a parameter determined according to the path ID;

The first forwarding unit is configured to send the third packet to the SF node.

In the first possible implementation manner of the foregoing second aspect, the method further includes:

a second receiving unit, configured to receive a fourth packet from the SF node, where the fourth packet includes the first parameter;

a second acquiring unit, configured to acquire the path ID according to the first parameter included in the fourth packet;

An encapsulating unit, configured to process the fourth packet according to the path ID obtained by the packet processing device after receiving the fourth packet, to obtain a fifth packet, where the encapsulation The processing of the fourth packet by the unit includes: the encapsulating unit determines the service header according to the path ID, and encapsulates the fourth packet by using the service header;

The second forwarding unit is configured to send the fifth packet to the SFE.

In conjunction with the foregoing second aspect or the first possible implementation of the second aspect, a second possible implementation manner of the second aspect is further provided, where the first forwarding unit is specifically configured to receive according to the first receiving unit And determining, by the identifier of the interface of the first packet, that the forwarding entry forwards the third packet, where the forwarding entry includes an identifier of the interface that receives the first packet and an identifier of the first interface;

The first forwarding unit is specifically configured to send, by using the first interface, the SF node Third message.

In conjunction with the second possible implementation of the foregoing second aspect, a third possible implementation of the second aspect is further provided, where the forwarding entry further includes the path ID;

The first forwarding unit is configured to determine, according to the path ID and the identifier of the interface that the first receiving unit receives the first packet, to forward the third packet according to the forwarding entry.

In conjunction with the second possible implementation of the foregoing second aspect, the fourth possible implementation of the second aspect is further provided, the forwarding entry further includes a second parameter, where the second parameter is used to identify the An SF node or a SF node of the SF node on the service chain;

When the service header of the first packet includes the second parameter, the first forwarding unit is configured to receive, according to the second parameter carried in the first packet, the first receiving unit The identifier of the interface of the first packet is determined, and the third packet is forwarded according to the forwarding entry.

In conjunction with the fourth possible implementation of the foregoing second aspect, a fifth possible implementation manner of the second aspect is further provided, where the encapsulating unit is specifically configured to add the second parameter to the service header.

A sixth possible implementation manner of the second aspect, where the service header in the first packet further includes a third parameter, in combination with the foregoing second aspect or any one of the foregoing possible implementation manners. The third parameter is used to identify that the first packet is an OAM packet.

The message processing device further includes:

a control unit, configured to determine that the first packet includes the third parameter, and the forwarding policy is to control the first forwarding unit to send the OAM packet from the SFE to the SF node The SF node sends the third packet.

A seventh possible implementation manner of the second aspect, the first parameter is the path ID, or the first parameter, in combination with the foregoing second aspect or any one of the foregoing possible implementation manners Data obtained by processing the path ID according to an algorithm.

Through the foregoing solution, the packet processing apparatus provided by the embodiment of the present invention strips the service header of the first packet and obtains the second packet. The message processing apparatus may obtain a path ID from a service header of the first packet. The packet processing device adds a first parameter corresponding to the path ID to the second packet, Obtain the third message. The message processing apparatus sends the third message to the SF node. In this way, the third packet received by the SF node does not include the service header, and the problem that the SF node cannot process the packet including the service header is solved.

DRAWINGS

In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings used in the description of the embodiments will be briefly described below. It is obvious that the drawings in the following description are only some embodiments of the present invention. Other figures may also be obtained from those of ordinary skill in the art in view of these figures.

FIG. 1 is a schematic diagram of a network scenario.

FIG. 2 is a schematic diagram of a network scenario according to an embodiment of the present invention.

FIG. 3 is a schematic diagram of a message processing apparatus according to an embodiment of the present invention.

FIG. 4 is a schematic diagram of a message processing apparatus according to an embodiment of the present invention.

FIG. 5 is a flowchart of a packet processing method according to an embodiment of the present invention.

detailed description

The technical solutions in the embodiments of the present invention will be clearly described in conjunction with the drawings in the embodiments of the present invention. Some embodiments, rather than all of the embodiments, are invented. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present invention are within the scope of the present invention.

FIG. 1 is a schematic diagram of a network scenario. The network shown in FIG. 1 includes a service classifier 101, an SFE 102, and an SF node 103. The SF node may have at least one of service functions such as a NAT and a firewall. A service chain in the network shown in FIG. 1 includes a service classifier 101, an SFE 102, and an SF node 103. On the service chain, the service classifier 101 encapsulates the service header on the received packet 1001 and obtains the packet 1011. The service header of the message 1011 includes a path ID and a preset ID of the service chain. The preset ID is used to identify the SF node 103 on the service chain. The last hop of the SF node. SFE 102 receives message 1011 from service classifier 101. The SFE 102 determines the forwarding entry according to the path ID and the preset ID included in the service header of the packet 1011. The forwarding entry includes a path ID, a preset ID, and an egress port. The egress port is connected to the SF node 103. The SFE 102 transmits the message 1011 to the SF node 103 through the egress port. The SF node 103 cannot perform the service processing on the packet 1001 included in the packet 1011 because the SF node 103 cannot identify the service header of the packet 1011.

Aiming at the above problems, a solution to the problem that the SF node cannot process the packet including the service header is proposed. The method is to add a message processing device between the SF node and the SFE. The message processing apparatus processes the service header included in the received message 1011 so that the message 1002 received by the SF node 103 does not include the service header. The method may include the message processing device stripping the service header of the message 1011 from the SFE 102 to obtain the message 1001. The message processing device acquires the first parameter corresponding to the path ID according to the path ID included in the service header of the message 1011. The message processing device adds the first parameter to the message 1001 to obtain the message 1002. The message processing device transmits the message 1002 to the SF node. Since the message 1002 does not include a service header, the SF node 103 can perform service processing on the message 1002. This solution can be implemented by the following embodiments.

FIG. 2 is a schematic diagram of a network scenario according to an embodiment of the present invention. The network shown in FIG. 2 includes a service classifier 101, an SFE 102, an SF node 103, and a message processing device 104. The service chain in the network shown in FIG. 2 includes a service classifier 101, an SFE 102, a message processing device 104, and an SF node 103. On the service chain, the service classifier 101 communicates with the SFE 102; the SFE 102 communicates with the message processing device 104; and the message processing device 104 communicates with the SF node 103. If the SF node 103 is the first SF node on the service chain, the SF node 103 does not exist on the previous hop SF node on the service chain. If the SF node 103 is not the first SF node on the service chain, the service chain may also include an SF node 105 in communication with the message processing device 104. The SF node 105 is the last hop SF node of the SF node 103 on the service chain. The SFE 102 can transmit the message 1010 to the SF node 105 via the message processing device 104, and receive the message 1011 sent by the SF node 105 through the message processing device 104. The SFE 102 then transmits the message 1011 to the SF node 103 via the message processing device 104 such that the message 1010 is processed on the service chain in the order of the SF nodes. The service described in the embodiment of the present invention Chain can also be a business function chain (English full service function chain).

FIG. 3 is a schematic diagram of a message processing apparatus according to an embodiment of the present invention. The message processing apparatus shown in FIG. 3 can be the message processing apparatus 104 in the network shown in FIG. 2. The message processing apparatus shown in FIG. 3 can be deployed between the SFE 102 and the SF node 103 on the service chain. Alternatively, the message processing apparatus shown in FIG. 3 can be deployed on the same device as the SFE 102. Alternatively, the message processing apparatus shown in FIG. 3 can be deployed on the same device as the SF node 103.

The message processing apparatus shown in FIG. 3 may include a processor 1040, a memory 1041, and a communication interface 1042. The processor 1040, the memory 1041, and the communication interface 1042 are connected by a communication bus 1043. The memory 1041 is used to store programs, and may also store mapping relationships. The mapping relationship is a mapping relationship between the path ID and the first parameter.

The processor 1040 performs the following operations in accordance with executable instructions included in the program read from the memory 1041.

The processor 1040 receives the message 1011 from the SFE 102 via the communication interface 1042. The packet 1011 is a packet obtained after the service header is encapsulated in the packet 1001. The service header of the message 1011 includes the path ID of the service chain.

The processor 1040 strips the service header from the message 1011 and obtains the message 1001 and the path ID.

The processor 1040 obtains the message 1002 according to the path ID and the message 1001. The message 1002 is a message 1002 obtained by adding the first parameter corresponding to the path ID stored in the memory 1041 to the message 1001.

The processor 1040 transmits the message 1002 to the SF node 103 via the communication interface 1042.

Optionally, the first forwarding entry may also be saved in the memory 1041. The first forwarding entry stored in the memory 104 includes an ID of an interface that receives the message 1011 and an ID of the first interface. The first interface is connected to the SFE node 103. The processor 1040 can determine, according to the ID of the interface that receives the message 1011, that the message 1002 is sent according to the first forwarding entry. The processor 1040 can send the message 1002 to the SF node 103 through the communication interface 1042 according to the ID of the first interface. The interface that receives the message 1011 is connected to the SFE 102.

Optionally, the message 1003 includes a first parameter. The processor 1040 receives through the communication interface 1042 Message 1003 from SF node 103. The processor 1040 acquires a path ID corresponding to the first parameter from the memory 1041 according to the first parameter included in the message 1003. The processor 1040 obtains the message 1013 according to the path ID and the message 1003 received through the communication interface 1042. The packet 1013 is a packet obtained after the service header is encapsulated in the packet 1003. The service header of the message 1013 includes the path ID. The processor 1040 transmits a message 1013 to the SFE 102 via the communication interface 1042.

Optionally, a second forwarding entry may also be saved in the memory 1041. The second forwarding entry stored in the memory 104 includes an ID of an interface that receives the message 1003 and an ID of the second interface. The second interface is connected to the SFE 102. The processor 1040 can determine, according to the ID of the interface that receives the message 1003, that the message 1003 is sent according to the second forwarding entry. The processor 1040 can transmit the message 1003 to the SFE 102 via the communication interface 1042 according to the ID of the second interface. The interface that receives the message 1003 is connected to the SF node 103.

Further, the processor 1040 cooperates with the communication interface 1042 according to the executable instructions and the mapping relationship in the memory 1041, so that the message processing apparatus shown in FIG. 3 executes the message processing apparatus in the embodiment shown in FIG. All the operations performed. It is also considered that the message processing apparatus shown in Fig. 3 is the message processing apparatus in the embodiment shown in Fig. 5.

FIG. 4 is a schematic diagram of a message processing apparatus according to an embodiment of the present invention. The message processing apparatus shown in FIG. 4 includes a first receiving unit 1044, a decapsulation unit 1045, a first obtaining unit 1046, and a first forwarding unit 1047. Optionally, the packet processing apparatus provided in the embodiment corresponding to FIG. 4 further includes: a second receiving unit 1048, a second obtaining unit 1049, a packaging unit 1050, and a second forwarding unit 1051. Optionally, the packet processing apparatus provided in the embodiment corresponding to FIG. 4 further includes a storage unit 1052. The storage unit 1052 can be used to save the mapping relationship held by the memory 1041 in FIG. Optionally, the packet processing apparatus provided in the embodiment corresponding to FIG. 4 further includes a control unit 1053.

The message processing apparatus shown in FIG. 3 and the message processing apparatus shown in FIG. 4 may be the same apparatus, for example, the message processing apparatus 104 in the network shown in FIG. 2. It can be considered that Fig. 3 shows the contents included in a message processing apparatus from a physical point of view, and Fig. 4 shows the contents included in a message processing apparatus from a logical point of view. Optionally, the first receiving unit 1044, the first forwarding unit 1047, the second receiving unit 1048, and the second forwarding unit 1051 in FIG. 4 may be implemented by the communication interface 1042 in FIG. 3, and the communication interface 1042 may include at least one Physical interface; decapsulation list in Figure 4 The element 1045, the first obtaining unit 1046, and the encapsulating unit 1050 may be implemented by the processor 1040 of FIG. 3 according to executable instructions stored by the memory 1041 or according to executable instructions and mapping relationships stored by the memory 1041, and the processor 1040 may include at least A physical processor.

FIG. 5 is a flowchart of a packet processing method according to an embodiment of the present invention. The packet processing method provided by the embodiment of the present invention is described in detail below with reference to FIG. 2 to FIG.

501. The SFE 102 sends a message 1011 to the message processing device 104.

In the network scenario shown in FIG. 2, the SFE 102 can receive the message 1010 sent by the service classifier 101. Message 1010 may be generated by service classifier 101. For example, service classifier 101 receives message 1001. The service classifier 101 determines the path ID of the service chain corresponding to the service type according to the service type corresponding to the message 1001. The service classifier 101 encapsulates the service header in the packet 1001 and obtains the packet 1010. The traffic header of message 1010 includes the path ID of the service chain.

Optionally, when there is a last hop SFE of the SFE 102 on the service chain between the service classifier 101 and the SFE 102, the message 1010 received by the SFE 102 is from the SFE 102 on the service chain. One hop SFE.

Optionally, the service header of the packet 1010 may further include at least one of a protocol type and metadata (English name is metadata). The metadata may include the ID of the user who sent the message 1001 to the service classifier 101.

The SFE 102 can determine the forwarding entry according to the path ID in the service header of the packet 1010. The forwarding entry includes a path ID and an ID of the interface. The SFE 102 can send the message 1011 to the message processing device 104 according to the ID of the interface. The interface may be an interface that the SFE 102 connects to the message processing device 104. Alternatively, the interface may be an interface where the SFE 102 connects to the SF node 103. Since the message processing device 104 is interposed between the SFE 102 and the SF node, the SFE 102 can send the message 1011 to the message processing device 104 without updating or upgrading the forwarding entry in the SFE 102. .

The message 1010 received by the SFE 102 may be the same as the message 1011 sent by the SFE 102 to the message processing apparatus 104, or may be different from the message 1011 sent by the SFE 102 to the message processing apparatus 104.

502. The message processing device 104 obtains the path ID of the message 1001 and the service chain.

For example, the first receiving unit 1044 receives the message 1011 from the SFE 102. The decapsulation unit 1045 strips the service header of the message 1011, obtains the message 1001, and obtains the path ID of the service chain from the service header.

The packet sent by the SFE 102 to the SF node 103 may be a packet including the service header, and the decapsulation unit 1045 may directly obtain the packet 1001 and the service included in the service header from the packet 1011 received by the first receiving unit 1044. The path ID of the chain.

If the protocol type is further included in the service header of the packet 1011, the decapsulation unit 1045 may also write the protocol type included in the service header to the storage unit 1052. The protocol type stored in the storage unit 1052 has a correspondence relationship with the path ID. If the header of the message 1011 further includes metadata, the decapsulation unit 1045 may also write the metadata included in the service header to the storage unit 1052. The metadata stored in the storage unit 1052 has a correspondence relationship with the path ID. The service header of the message 1011 may include any or all of the protocol type and the metadata.

503. The message processing device 104 processes the message 1001 by using the first parameter determined according to the path ID, and obtains the message 1002. The processing includes adding the first parameter to the message 1001.

The first parameter may be the path ID itself, or the first parameter may be data obtained by processing the path ID according to an algorithm. The algorithm can be a hash algorithm or a compression algorithm. The compression algorithm is used to map data larger than N bits into N-bit data. N is the data bit contained in at least one byte.

The first obtaining unit 1046 may acquire the message 1002 by adding the first parameter determined according to the path ID to the message 1001. Adding the first parameter determined according to the path ID to the message 1001 means adding the first parameter to the inside of the message 1001, instead of adding an outer message header to the message 1001, and The first parameter is added to the newly added outer header. Optionally, the first obtaining unit 1046 may obtain the first parameter corresponding to the path ID from the mapping relationship between the path ID and the first parameter saved by the storage unit 1052.

Optionally, the first obtaining unit 1046 may add the first parameter to a preset field in the message 1001. The preset field is a word that the SF node 103 does not modify when performing service processing on the message 1002. At least one field in the segment. The number of preset fields may be determined according to the number of bytes occupied by the first parameter. If the first parameter is a path ID and the path ID is 8 bits, the first obtaining unit 1046 may select a field from the message 1001 to save the path ID. If the first parameter is a path ID and the path ID is greater than 8 bits, the first obtaining unit 1046 may select a plurality of fields from the message 1001 to save the path ID. If the first parameter is data obtained by processing the path ID according to the algorithm, the first obtaining unit 1046 may select one or more fields in the message 1001 to save the first according to the method of saving the path ID in the message 1001. parameter. The selected one or more fields in the message 1001 are fields that the SF node 103 does not modify during the service processing of the message 1002.

For example, the preset field may be a virtual local area network (English name is Virtual Local Area Network, abbreviated as VLAN) field. If the packet 1001 is an IPv4 packet, the default field may also be a service type of the IPv4 packet (English name is service, the English abbreviation is TOS) field and the survival time (English is called time to live, the English abbreviation is One or more fields in the TTL) field. If the packet 1001 is an IPv6 packet, the default field may be a stream type of the IPv6 packet (the English name is a traffic class) field, a hop limit (English name is a hop limit) field, and a stream tag (the English name is Flow). Label One or more fields in the field. When the SF node 103 processes the packet 1002, the Time-To-Live field is modified. The first obtaining unit 1046 pre-stores the configuration information of the SF node 103. The configuration information of the SF node 103 can modify the Time-To-Live field when the SF node 103 performs service processing. The first obtaining unit 1046 adds the first parameter to the Type-of-Service field according to the configuration information of the SF node 103, so that the SF node 103 retains the first parameter corresponding to the path ID in the process of processing the message 1002.

Taking the path ID as 24-bit data as an example, the first obtaining unit 1046 can map the 24-bit path ID to the 8-bit first parameter and store it in a field of the message 1001. Optionally, if the first parameter corresponding to the path ID is not included in the mapping relationship saved by the storage unit 1052, the first obtaining unit 1046 may select an unused value as the first parameter from the value range of the 8-bit data. The first obtaining unit 1046 may store the first parameter corresponding to the path ID to the storage unit 1052.

It should be noted that the first obtaining unit 1046 may also add the first parameter to the non-preset field in the message 1001 instead of adding the first parameter to the preset field, where The preset field refers to a field that the SF node 103 will modify when performing service processing on the message 1002. When the first parameter is added to the non-preset field in the message 1001, the SF node 103 may first read the first parameter in the process of performing service processing on the message 1002, and then The field is modified, and the first parameter is added back to the modified non-preset field or another non-preset field of the message 1001. As long as the message processing device 104 learns the rules of the first parameter added in the non-preset field, it can be ensured that the first parameter added by the SF node 103 in the non-preset field can still be recognized by the SFE 102.

If the individual fields in the message 1002 are modified or deleted, or one or more fields are added to the message 1002, but the main functions and attributes of the message 1002 are not changed, then the modified message 1002 is implemented in the present embodiment. The example is still considered to be the message 1002 obtained after processing the message 1001 by the first parameter.

504. The message processing device 104 sends the message 1002 to the SF node 103.

For example, the message 1002 to the SF node 103 can be transmitted by the first forwarding unit 1047.

The first forwarding unit 1047 can forward the message 1002 according to the first forwarding entry. The first forwarding entry may include an ID of the interface that receives the message 1011 and an ID of the first interface, where the interface of the received message 1011 is connected to the SFE 102, and the first interface is connected to the SF node 103. The first forwarding unit 1047 determines that the packet 1002 is sent according to the first forwarding entry according to the ID of the interface that receives the packet 1011.

Optionally, the first forwarding entry may include a path ID in addition to the ID of the interface that receives the message 1011 and the ID of the first interface. In this case, the first forwarding unit 1047 determines to send the message 1002 according to the first forwarding entry according to the ID of the interface that receives the message 1011 and the ID of the interface that receives the message 1011.

Optionally, the first forwarding entry may include a first parameter in addition to the ID of the interface that receives the message 1011 and the ID of the first interface. In this case, the first forwarding unit 1047 determines to send the message 1002 according to the first forwarding entry according to the first parameter and the ID of the interface of the received message 1011.

After determining that the message 1002 is sent according to the first forwarding entry, the first forwarding unit 1047 sends the message 1002 to the SF node 103 according to the first interface.

The method of 502 to 504 is a method in which the message processing device 104 processes the message 1011 transmitted to the SF node 103. The message processing device 104 performs the above processing on the message 1011, and then strips the service header and acquires the message 1002. The SF node 103 can identify and process the message 1002 that is not encapsulated with the service header.

The following 505 to 507 are methods in which the message processing apparatus 104 processes the message 1003 transmitted by the SF node 103 to the SFE 102. The message 1003 is a message obtained after the SF node 103 performs service processing on the message 1002. The field in which the message 1003 holds the path ID is the same as the field in which the message 1002 holds the path ID. The following 505 to 507 are optional steps.

505. The SF node 103 sends a message 1003 to the message processing device 104.

The SF node 103 can transmit the message 1003 to the message processing device 104 by receiving the interface of the message 1002. Alternatively, the forwarding entry is stored on the SF node 103. The forwarding entry includes a first parameter and an ID of an interface to which the message processing device 104 is connected. The SF node 103 acquires the ID of the interface of the connection message processing device 104 included in the forwarding entry according to the first parameter in the message 1002. The SF node 103 transmits the message 1003 to the message processing device 104 based on the ID of the interface to which the message processing device 104 is connected.

506. The message processing device 104 obtains the message 1013 by processing the message 1003 according to the path ID. The processing includes encapsulating the packet 1003 by using the service header corresponding to the path ID.

For example, the second receiving unit 1048 receives the message 1003 from the SF node 103. The message 1003 includes a first parameter. The second obtaining unit 1049 acquires a path ID corresponding to the first parameter according to the first parameter included in the received message 1003. The encapsulating unit 1050 encapsulates the service header on the packet 1003 to obtain the packet 1013. The service header of the message 1013 includes a path ID. Optionally, the second obtaining unit 1049 may obtain the path ID corresponding to the first parameter from the storage unit 1052.

The service header of the packet 1013 obtained by the second obtaining unit 1049 is the same as the traffic header of the packet 1011. For example, if the service header of the packet 1011 in 502 carries the protocol type, the second obtaining unit 1049 may obtain the protocol type corresponding to the path ID from the storage unit 1052 according to the path ID, and add the protocol type to the packet 1013. Business head. If the service header of the packet 1011 in 502 carries the protocol type and the metadata, the second obtaining unit 1049 may obtain the information from the storage unit 1052 according to the path ID. The protocol type and metadata corresponding to the path ID, and the protocol type and metadata are added to the service header of the message 1013.

If the individual fields in the message 1003 are modified or deleted, or one or more fields are added to the message 1003, but the main functions and attributes of the message 1003 are not changed, then the modified message 1003 is implemented in the present embodiment. The example is still considered to be the message 1003.

507. The message processing device 104 transmits the message 1013 to the SFE 102.

The second forwarding unit 1051 transmits a message 1013 to the SFE 102.

For example, the second forwarding unit 1051 can forward the message 1013 according to the second forwarding entry. The second forwarding entry includes an ID of an interface that receives the message 1003 and an ID of the second interface. The second forwarding unit 1051 may determine to send the message 1013 to the SFE 102 according to the second forwarding entry according to the ID of the interface that receives the message 1003. The second forwarding unit 1051 may send the message 1013 to the SFE 102 according to the second interface. The second interface is connected to the SFE 102. Optionally, the second entry may be saved in the storage unit 1052.

Optionally, the interface receiving the message 1003 is connected to the SF node 103. The second forwarding unit 1049 can determine that the message 1003 is from the SF node 103 according to the ID of the interface that receives the message 1003. The second forwarding unit 1049 can send the message 1013 to the SFE 102 by receiving the interface of the message 1011 to reduce the lookup of the forwarding entry.

Since the message 1013 is from the SF node 103 and the SF node 103 is attached to the SFE 102, the message processing device 104 can forward any message determined to be from the SF node 103 to the SFE 102.

In order to accurately forward the message, the service classifier 101 may add a second parameter to the service header of the message 1011 in the process of generating the message 1011. The second parameter is used to identify the SF node 103 on the service chain or the last hop SF node of the SF node 103 on the service chain. The second parameter mentioned in the embodiment of the present invention may be information such as a character, a character string, a name, or an index (English name is index).

Between 502 and 503, the first obtaining unit 1046 also stores the second parameter included in the service header of the message 1011 in the storage unit 1052. The second parameter in the storage unit 1052 corresponds to the path ID.

The first forwarding entry further includes a second parameter. The first forwarding unit 1047 of the 504 determines to send the message 1002 according to the first forwarding entry according to the second parameter and the ID of the interface of the received message 1011.

Between 505 and 506, the second obtaining unit 1049 further acquires the second parameter corresponding to the path ID from the storage unit 1052 according to the acquired path ID. Encapsulation unit 1050 also adds a second parameter to the traffic header of message 1013.

In the above embodiment, if the message processing device 104 is connected to one or more SF nodes similar to the SF node 103, the message processing device 104 can determine the SF node 103 that receives the message 1002 according to the second parameter, which is helpful to improve. The accuracy of forwarding.

When the message processing device 104 is connected to the SF node on another service chain, the SF node on the other service chain is the SF node 105 on the last hop node on the other service chain, and the second parameter When the SF node 105 is used to identify the forwarding entry, the packet processing device 104 can determine the forwarding entry according to the path ID.

Between 502 and 503, the first obtaining unit 1046 saves the path ID and the second parameter included in the service header of the message 1011 in the storage unit 1052.

For example, if the first forwarding entry further includes a path ID and a second parameter. The first forwarding unit 1047 in the 504 may determine to send the message 1002 according to the first forwarding entry according to the second parameter, the path ID, and the ID of the interface that receives the message 1011. The first forwarding entry further includes a first parameter and a second parameter. The first forwarding unit 1047 in the 504 may determine to send the message 1002 according to the first forwarding entry according to the second parameter, the first parameter, and the ID of the interface of the received message 1011.

Optionally, the service header of the message 1011 mentioned in the foregoing embodiment of the present invention may further include a third parameter. The third parameter is used to identify that the packet 1011 is an OAM packet. The 504 further includes: when the message processing device 104 determines that the message 1011 includes the third parameter, and the forwarding policy is to send the OAM message from the SFE 102 to the SF node 103, the message 1002 is sent to the SF node 103. Specifically, the control unit 1053 included in the message processing apparatus 104 determines the industry that the decapsulation unit 1045 strips from the message 1011. The service header includes a third parameter, and when the forwarding policy is to send the OAM message from the SFE 102 to the SF node 103, the first forwarding unit 1047 is controlled to send the message 1002 to the SF node 103.

The interface mentioned in the above embodiments of the present invention may be an interface of a physical interface, a logical interface or a tunnel. If the interface mentioned in the above embodiment of the present invention is an interface of a tunnel, the message processing apparatus 104 needs to establish a tunnel with the SFE 102 and the SF node 103, respectively. The ID of the interface mentioned in the foregoing embodiment of the present invention belongs to the identifier of the interface, and the identifier of the interface in the embodiment of the present invention may also be identifier information represented by other forms.

The above general purpose processor may be a microprocessor or the processor or any conventional processor. The steps of the method disclosed in the embodiment of the present invention may be directly implemented as a hardware processor, or may be performed by a combination of hardware and software modules in the processor. When implemented in software, the code implementing the above functions may be stored in a computer readable medium. Computer readable media includes computer storage media. A storage medium may be any available media that can be accessed by a computer. For example, but not limited to: the computer readable medium may be a random access memory (English full name is random access memory, abbreviated as RAM), read-only memory (English full name is read-only memory, English abbreviation for ROM), Electrical erasable programmable read-only memory (English full name electrically erasable programmable read-only memory, abbreviated as EEPROM), read-only optical disc (English full name compact disc read-only memory, English abbreviation for CD-ROM) or other disc A storage, magnetic storage medium or other magnetic storage device, or any other medium that can be used to carry or store program code in the form of an instruction or data structure and that can be accessed by a computer. The computer readable medium may be a compact disc (English full name compact disc, abbreviated as CD), a laser disc, a digital video disc (English full name digital video disc, abbreviated as DVD), a floppy disk or a Blu-ray disc.

Finally, it should be noted that the above embodiments are only used to exemplify the technical solutions of the present invention, and are not limited thereto; although the beneficial effects brought by the present invention and the present invention are described in detail with reference to the foregoing embodiments, the field It should be understood by those skilled in the art that the technical solutions described in the foregoing embodiments may be modified or equivalently replaced with some of the technical features; and such modifications or substitutions do not deviate from the essence of the corresponding technical solutions. The scope of the claims.

Claims

A packet processing method, characterized in that the method comprises:

The packet processing apparatus receives the first packet from the service forwarding entity SFE, where the first packet includes a second packet and a service header encapsulated in the second packet, where the first packet is included The service header includes a path identifier ID of the service chain;

The message processing apparatus acquires the second packet and the path ID;

The packet processing apparatus processes the second packet according to the path ID to obtain a third packet, where the processing of the second packet includes: adding a first parameter to the In the second packet, the first parameter is a parameter determined according to the path ID;

The message processing apparatus sends the third message to a service function SF node.
The method of claim 1 wherein the method further comprises:

The message processing apparatus receives a fourth packet from the SF node, where the fourth packet includes the first parameter;

The packet processing device acquires the path ID according to the first parameter included in the fourth packet;

The message processing apparatus acquires the fifth packet by processing the fourth packet according to the path ID obtained by the packet processing apparatus after receiving the fourth packet, where the The processing of the fourth packet includes: determining the service header according to the path ID, and encapsulating the fourth packet by using the service header;

The message processing apparatus sends the fifth message to the SFE.
The method of claim 2, wherein the sending, by the message processing device, the third message to the service function SF node comprises:

The packet processing device determines, according to the identifier of the interface that receives the first packet, that the third packet is forwarded according to the forwarding entry, where the forwarding entry includes the interface that receives the first packet. The identifier and the identifier of the first interface;

The packet processing apparatus sends the third packet to the SF node by using the first interface.
The method of claim 3, wherein the forwarding entry further comprises the path ID;

The packet processing apparatus determines, according to the identifier of the interface that receives the first packet, that the third packet is forwarded according to the forwarding entry, and includes:

The packet processing apparatus determines, according to the path ID and the identifier of the interface that receives the first packet, that the third packet is forwarded according to the forwarding entry.
The method of claim 3, wherein the forwarding entry further comprises a second parameter, the second parameter is used to identify a previous one of the SF node or the SF node on the service chain. Jump SF node;

When the service header in the first packet includes the second parameter, the packet processing apparatus determines, according to the identifier of the interface that receives the first packet, that the third packet is forwarded according to the forwarding entry. include:

The packet processing apparatus determines to forward the third packet according to the forwarding entry according to the second parameter carried in the first packet and the identifier of the interface that receives the first packet. .
The method according to claim 5, wherein the encapsulating the fourth packet by using the service header comprises:

The message processing apparatus adds the second parameter to the traffic header.
The method according to any one of claims 1 to 6, wherein the service header in the first packet further includes a third parameter, and the third parameter is used to identify that the first packet is an operation, Manage and maintain OAM packets;

Before the packet processing apparatus sends the third packet to the service function SF node, the method further includes:

When the packet processing apparatus determines that the first packet includes the third parameter, and the forwarding policy is to send an OAM packet from the SFE to the SF node, send the Third message.
The method according to any one of claims 1 to 7, wherein the first parameter is the path ID, or the first parameter is a number obtained by processing the path ID according to an algorithm. according to.
A message processing apparatus, characterized in that the message processing apparatus comprises:

a first receiving unit, configured to receive a first packet from the service forwarding entity SFE, where the first packet is a packet obtained after the service header is encapsulated in the second packet, where the first packet is The service header includes a path identifier ID of the service chain;

Decapsulating unit, configured to acquire the second packet and the path ID;

a first acquiring unit, configured to process the second packet according to the path ID, to obtain a third packet, where the processing performed by the first acquiring unit on the second packet includes: The first obtaining unit adds a first parameter to the second packet, where the first parameter is a parameter determined according to the path ID;

The first forwarding unit is configured to send the third packet to the service function SF node.
The device of claim 9 wherein said device further comprises:

a second receiving unit, configured to receive a fourth packet from the SF node, where the fourth packet includes the first parameter;

a second acquiring unit, configured to acquire the path ID according to the first parameter included in the fourth packet;

An encapsulating unit, configured to process the fourth packet according to the path ID obtained by the packet processing device after receiving the fourth packet, to obtain a fifth packet, where the encapsulation The processing of the fourth packet by the unit includes: the encapsulating unit determines the service header according to the path ID, and encapsulates the fourth packet by using the service header;

The second forwarding unit is configured to send the fifth packet to the SFE.
The device of claim 10 wherein:

The first forwarding unit is configured to: according to the identifier of the interface that the first receiving unit receives the first packet, determine that the forwarding entry forwards the third packet, where the forwarding entry includes the receiving station The identifier of the interface of the first packet and the identifier of the first interface;

The first forwarding unit is specifically configured to send the third packet to the SF node by using the first interface.
The apparatus according to claim 11, wherein the forwarding entry further includes the path ID;

The first forwarding unit is configured to determine, according to the path ID and the identifier of the interface that the first receiving unit receives the first packet, to forward the third packet according to the forwarding entry.
The apparatus according to claim 11, wherein the forwarding entry further comprises a second parameter, the second parameter is used to identify a previous one of the SF node or the SF node on the service chain. Jump SF node;

When the service header of the first packet includes the second parameter, the first forwarding unit is configured to receive, according to the second parameter carried in the first packet, the first receiving unit The identifier of the interface of the first packet is determined, and the third packet is forwarded according to the forwarding entry.
The device of claim 13 wherein:

The encapsulating unit is specifically configured to add the second parameter to the service header.
The device according to any one of claims 9 to 14, wherein the service header in the first packet further includes a third parameter, and the third parameter is used to identify the first packet as operation, management, and Maintain OAM packets;

The message processing device further includes:

a control unit, configured to determine that the first packet includes the third parameter, and the forwarding policy is to control the first forwarding unit to send the OAM packet from the SFE to the SF node The SF node sends the third packet.
The apparatus according to any one of claims 9 to 15, wherein the first parameter is the path ID, or the first parameter is data obtained by processing the path ID according to an algorithm.