WO2018166325A1 - Method and device for forwarding data packet - Google Patents

Abstract

The embodiments of the present application relate to the technical field of communications, especially to a method and device for forwarding a data packet, for reducing entries in a forwarding table on an SFF, thereby improving the forwarding efficiency of the SFF. In the embodiments of the present application, a first SPI, an SI and a second SPI are encapsulated in an NSH of a data packet, wherein the first SPI indicates a first service link path currently forwarding the data packet, the second SPI indicates a second service link path specified by a service link controller for a service link where the data packet is located, and the first service path is partially overlapped with the second service path. In the embodiments of the present invention, by means of indicating an overlapped part of a first service link path and a second service link path with a first SPI, path information in a forwarding table can be multiplexed, thus reducing the number of entries in a forwarding table, and thereby reducing the amount of memory occupied by the forwarding table.

Description

Data packet forwarding method and device

This application claims the priority of the Chinese Patent Application filed on March 14, 2017, the Chinese Patent Office, Application No. 201710150395.7, entitled "A Data Packet Forwarding Method and Apparatus", the entire contents of which are incorporated by reference. In this application.

Technical field

The embodiments of the present invention relate to the field of communications, and in particular, to a data packet forwarding method and device.

Background technique

As the types of services of carriers increase, in order to support a better service experience, a service routing network needs to be deployed in the network, and a Service Function Chaining (SFC) technology is proposed. This technology provides the foundation for flexible business processing by linking multiple business functions. The service classifier (SC) classifies the service flow by the service classifier (SC), and then forwards the data packet of the service chain along the predefined service chain path through the service function forwarder (SFF). The end of the service chain forwards the packet to the service chain server (Post Service, PS).

The Network Service Header (NSH) is an extended message header format designed specifically for the service chain by the Internet Engineering Task Force (IETF) SFC Working Group. The data packet transmitted on the service chain is encapsulated with an NSH. The NSH includes a Service Path ID (SPI) and a Service Index (SI) of the data packet. A forwarding table is stored in the SFF, and the forwarding table indicates the next hop device corresponding to the SPI and the SI in the data packet. The SFF may determine, according to the SPI and the SI in the data packet, the next hop device corresponding to the data packet from the forwarding table, and after the SI in the data packet is decremented by one, the data packet is sent to the next. One hop device.

In order to implement the forwarding of data packets in the service chain, the SPI flow table corresponding to the path of each service chain in the prior art needs to be stored in all SFFs corresponding to the path. When a large number of service chains exist in the network, There are many entries in the forwarding table on the SFF. Searching for a large number of entries reduces the forwarding efficiency of the SFF.

Summary of the invention

The embodiment of the present invention provides a data packet forwarding method and device, which are used to reduce the forwarding table entries on the SFF and improve the forwarding efficiency of the SFF.

In a first aspect, the embodiment of the present application provides a data packet forwarding method, where the method includes: receiving a data packet of a service chain, where the network service header NSH of the data packet includes a first service chain path identifier SPI and a a service index SI; the data message further includes a second SPI; the first SPI is used to indicate the first service chain path, and the second SPI is used to indicate the second service chain path, the first service chain path and the second service chain path are at least Partially coincident. In this application, the first SPI is the SPI of the service chain path in which the data packet is currently located, and the second SPI is the SPI of the service chain corresponding to the service flow to which the data packet added by the SC is the data packet. Determining a next hop address and an NSH encapsulation information in the forwarding entry corresponding to the first SPI and the first SI according to the forwarding table; the NSH encapsulation information includes a jump information and a type tag; and the type flag indicates when the packet is forwarded according to the forwarding entry Type of operation. The next hop address may be an address of the SF, the SFF, or the PS. The forwarding table is calculated by the service chain controller according to the deployment of the service chain and sent to each forwarding device. The NSH is re-encapsulated according to the NSH encapsulation information, and the data packet re-packaged by the NSH is sent to the next hop address. In the embodiment of the present application, each time the forwarding device forwards the data packet, the SI in the data packet is decremented by one. Optionally, receiving the data packet sent by the service function SF; decrementing the first SI in the data packet by one.

In the embodiment of the present application, the first SPI, the SI, and the second SPI are encapsulated in the NSH of the data packet, where the first SPI indicates the first service chain path for forwarding the data packet, and the second SPI indicates the service chain control. The second service chain path specified by the service chain in which the data packet is located, where the first service path and the second service path partially overlap. In the embodiment of the present invention, the part of the first service chain path and the second service chain path are instructed by the first SPI, so that the path information in the forwarding table can be reused, thereby reducing the number of entries in the forwarding table, and further reducing the forwarding table. Memory usage.

The type tag in the embodiment of the present application may include the indicated operation type as a merged type tag and the indicated operation type as a separate type tag. If the operation type indicated by the type tag is merged, and the jump information includes the target SPI and the target SI, re-encapsulating the NSH according to the NSH encapsulation information, including: updating the first SPI in the NSH by using the target SPI; updating by using the target SI The first SI in the NSH; wherein the combined operation type is further used to indicate that the next hop address of the data packet on the second service chain path is the same as the next hop address on the first service chain path. In this manner, when the next hop address of the data packet on the second service chain path is the same as the next hop address on the first service chain path, the second service chain path can reuse the first service chain in the forwarding table. The entry of the path.

If the operation type indicated by the type tag is separated, and the jump information includes the target SPI and the target SI, and the first SPI and the second SPI are different, the NSH is re-packaged according to the NSH encapsulation information, including: obtaining the NSH encapsulation information. The target SPI and the target SI, when the target SPI and the second SPI are the same, use the target SPI to update the first SPI in the NSH; use the target SI to update the first SI in the NSH; wherein the separated operation type is also used to indicate The next hop address of the data packet on the second service chain path is different from the next hop address of the data packet on the first service chain. In this manner, when the next hop address of the data packet on the second service chain path and the next hop address on the first service chain path are not available, the second service chain path and the first service chain path may be respectively used in the forwarding table. Their respective entries.

Optionally, the first SPI is located in the SPI field of the NSH of the data packet, where the first SI is located in the SI field of the NSH of the data packet, and the second SPI is located in the context header of the NSH of the data packet. Since forwarding is performed according to the first SPI and the first SI, it is often necessary to access the first SPI and the first SI, and placing the first SPI and the first SI into the header may reduce the access delay.

In a second aspect, the embodiment of the present application provides a data packet forwarding device, where the data packet forwarding device includes a memory, a communication interface, and a processor, where: the memory is used to store an instruction; the processor is configured to execute the memory storage instruction, and control The communication interface receives or transmits a data message, and when the processor executes the instruction stored in the memory, the data message forwarding device is configured to perform the method of any of the first aspect or the first aspect.

In a third aspect, the embodiment of the present application provides a data packet forwarding device, which is used to implement the method in any of the foregoing first aspect or the first aspect, where the data forwarding device includes a corresponding function module, which is used to implement The steps in the above method.

In a fourth aspect, an embodiment of the present application provides a computer readable storage medium, where the computer readable storage medium stores instructions that, when run on a computer, cause the computer to perform any of the first aspect or the first aspect. The method in the implementation.

In a fifth aspect, an embodiment of the present application provides a computer program product comprising instructions, when executed on a computer, causing the computer to perform the method in the first aspect or any possible implementation manner of the first aspect.

In the embodiment of the present application, the first SPI, the SI, and the second SPI are encapsulated in the NSH of the data packet, where the first SPI indicates the first service chain path for forwarding the data packet, and the second SPI indicates the service chain control. The second service chain path specified by the service chain in which the data packet is located, where the first service path and the second service path partially overlap. In the embodiment of the present invention, the part of the first service chain path and the second service chain path are instructed by the first SPI, so that the path information in the forwarding table can be reused, thereby reducing the number of entries in the forwarding table, and further reducing the forwarding table. Memory usage.

DRAWINGS

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings used in the description of the embodiments will be briefly described below.

1 is a schematic diagram of a service chain system architecture applicable to an embodiment of the present application;

FIG. 1 is a schematic flowchart of a method for processing a data packet by an NSH Proxy according to an embodiment of the present disclosure;

FIG. 2 is a schematic flowchart of a data packet forwarding method according to an embodiment of the present disclosure;

2a is a schematic structural diagram of an NSH according to an embodiment of the present application;

FIG. 2b is a schematic structural diagram of another NSH according to an embodiment of the present disclosure;

FIG. 3 is a schematic diagram of a forwarding table on an SFF according to an embodiment of the present application;

FIG. 4 is a schematic structural diagram of a service chain according to an embodiment of the present application;

Figure 5 is a two-tailed business chain path provided based on the structure shown in Figure 4;

5a-5c are schematic structural diagrams of a forwarding table stored on the SFF 212, the SFF 213, and the SFF 214, respectively, based on the service chain path shown in FIG. 5 in the prior art;

FIG. 5 is a schematic structural diagram of a forwarding table stored on the SFF 212, the SFF 213, and the SFF 214 according to the service chain shown in FIG. 5 according to the embodiment of the present application;

6 is a service chain path in which two headers and a tail are coincident based on the structure shown in FIG. 4;

FIG. 6 is a schematic structural diagram of a forwarding table stored on the SFF 212, the SFF 213, and the SFF 214 according to the service chain path shown in FIG. 6 according to the embodiment of the present application;

Figure 7 is a two-headed business chain path provided based on the structure shown in Figure 4;

FIG. 7 is a schematic structural diagram of a forwarding table stored on the SFF 212, the SFF 213, and the SFF 214 according to the service chain path shown in FIG. 7 according to the embodiment of the present application;

8 is a schematic structural diagram of a data packet forwarding device;

FIG. 9 is a schematic structural diagram of another forwarding device for data packets.

Specific embodiment

The present invention will be further described in detail below with reference to the accompanying drawings and embodiments. It is understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

In a specific implementation, implementing end-to-end services requires various service functions, such as firewalls, network address translation services (NATs), and other specific application functions. The service chain is an ordered collection of service functions (SF) and a service flow scheduling technique. FIG. 1 is a schematic diagram showing a service chain system architecture applicable to an embodiment of the present application. As shown in FIG. 1, the service chain architecture in the embodiment of the present application is mainly composed of the following key components.

Service Chain Collaboration Layer (SFC Orchestrator) 101: Mainly complete the basic resource configuration required to provide service chain services, including SC, SFF, and Service Node (SN) configuration, SF and SFF network connection coordination, and SF service. Functions such as policy configuration are a unified entry for the characteristics of the service chain.

Service Chain Controller (SFC Controller) 102: A network control function that implements the characteristics of the service chain, including functions such as overlay network management and service chain path calculation and forwarding table delivery required by the service chain, and provides interfaces and clouds in the north. The management platform or the service chain collaboration layer 101 is docked, and the south interface can be connected to the SC, the SFF, and the PS through an open source streaming (Openflow) or network configuration (Netconf) interface.

SC103: Receives a data packet from a non-SFC network and classifies the packet, matches the corresponding service chain, encapsulates the data packet, and forwards the encapsulated data packet to the service chain. The first jump SFF104. The SC can be divided into two (outbound) and inbound (inbound) SCs. The SCs in both directions can be the same device. The SC and SFF can be deployed on the same device.

The SFF 104 and the SFF 105 are responsible for forwarding the data packets introduced by the SC into the service chain along a predefined service chain path, and the SFF 105 forwards the message to the PS at the end of the service chain; and integrates the network service host proxy function. That is, the NSH-unaware type SF proxy performs NSH decapsulation and encapsulation on the packet and updates the information in the NSH.

Service Function (SF) instances SF107, SF108, SF109, and SF110: are exclusive to the tenant, that is, different tenants do not use the same SF instance. The SF instance is usually a virtual resource, such as a vsys instance. The data message is received from the SFF and the received data message is processed by applying the service policy, and the processed data message is returned to the SFF.

SN111 and SN112: SF containers, which may be network service devices supporting physical network function (PNF) or virtual network function (VNF). The SN can support single SF instance or multiple SF instance mode work. Supports virtual local area network (VLAN) or virtual extensible local area network (VXLAN) access to SFF.

PS106 (Post Service): The tail server of the service chain, that is, the destination device that the data packet needs to reach after passing through the service chain. The PS and SFF can be deployed on the same device.

Based on the service chain architecture shown in Figure 1, the forwarding process of data packets on the service chain is introduced:

First, the SC 103 receives the data packet from the non-SFC network, and the data packet may be a VXLAN packet, a Generic Routing Encapsulation (GRE) packet, or an Ethernet Ethernet Port (ETH) packet. For example, the data packet is a VXLAN packet. After receiving the data packet encapsulated by the VXLAN, the SC decapsulates the VXLAN, determines the traffic classifier corresponding to the data packet, determines the service chain matching the traffic classifier, and then performs the network service header for the data packet encapsulated by the VXLAN ( English: network service header (NSH) encapsulation, that is, encapsulating NSH for the data packet encapsulated by VXLAN, and then performing VXLAN encapsulation on the data packet encapsulating the NSH (that is, adding a VXLAN packet header), and then according to the forwarding table, The data packet after the VXLAN encapsulation and the NSH encapsulation is forwarded to the first hop SFF of the service chain, that is, the SFF 104.

Second, after receiving the data packet after the VXLAN encapsulation and the NSH encapsulation, the SFF 104 de-packs the VXLAN, decapsulates the NSH, and finds the SPI and the SI according to the SPI and SI lookup forwarding tables in the NSH. The next hop address, the data packet is re-encapsulated in the NSH and VXLAN, and then the data packet encapsulated in the NSH and VXLAN is forwarded to the next hop address; the next hop address is the address of the SF107.

The SFF 104 forwards the data packet of the NSH and the VXLAN to the SF107. The SF107 decapsulates the VXLAN, decapsulates the NSH, processes the data packet, and re-processes the processed data packet. In the VXLAN package, the NSH encapsulation and VXLAN encapsulation data packets are returned to the SFF 104.

Fourth, the SFF 104 receives the re-performed NSH encapsulation and VXLAN encapsulation data message returned by the SF 107, de-packs the VXLAN, de-packets the NSH, and decrements the SI, and determines the next table according to the SPI and the reduced SI lookup table. The hop address, which is the address of the SF108.

After the service chain forwarding process as shown above, the data message is forwarded to the PS. Specifically, the SFF 105 may determine that the next hop needs to jump to the PS according to the content in the forwarding table, and the SFF 105 may search the routing table according to the destination IP address in the original data packet and forward the packet to the PS.

Specifically, according to the support of the SF for the NSH encapsulation, we refer to different SFs as SF (NSH-aware SF) supporting NSH encapsulation and SF (NSH-unaware SF) not supporting NSH encapsulation. In the foregoing second and third steps, the SF 107 is an SF supporting the NSH encapsulation. If the SF 107 is an SF that does not support the NSH encapsulation, an NSH proxy needs to be added between the SFF 104 and the SF 107. character of.

Figure 1a is a schematic diagram showing the flow of processing data packets by the NSH proxy 1205 in the embodiment of the present application. As shown in Figure 1a, the SF1203 output of the NSH is not supported for data packets sent from the SF 1203 that does not support the NSH to the SFF 1207. The data packet is a data packet that is not encapsulated in the NSH package 1204, and is then encapsulated in the NSH by the NSH proxy 1205. The data packet transmitted by the NSH proxy 1205 to the SFF 1207 is a data packet for the NSH package 1206, and then transmitted to the network by the SFF 1207. 1208. For the data packet sent from the SFF 1207 to the SF 1203 that does not support the NSH, the SFF 1207 transmits the data packet of the NSH package 1206 to the NSH proxy 1205, and the NSH proxy 1205 removes the NSH encapsulation of the data packet, and the obtained NSF package is obtained. The data packet of the NSH package 1204 is sent to the SF 1203 that does not support the NSH.

As shown in FIG. 1a, for data packets transmitted from the SF 1201 supporting the NSH to the SFF 1207, the SF 1201 supporting the NSH performs NSH encapsulation 1202 on the data message, and then directly transmits it to the SFF 1207, and transmits it to the network 1208 by the SFF 1207; The SFF 1207 directly transmits the data packet of the NSH package 1202 to the SF 1201 supporting the NSH.

The NSH proxy 1205 in the service chain network is a logical role and can be concurrently served by SFF. We refer to the table items required for SFF to restore NSH encapsulation as the SFC mapping table. For the NSH-Based service chain, the SFC Controller sends an NSH flow table (including a forwarding table and a mapping table) to the SFF and the SC, so that the SFF and the SC forward the data packet of the service chain according to the NSH flow table to complete the processing of the service chain.

FIG. 2 is a schematic flowchart showing a data packet forwarding method according to an embodiment of the present disclosure. As shown in FIG. 2, the method is performed by a forwarding device, and the forwarding device may be the SFF in FIG. 1. The method includes :

Step 201: The forwarding device receives the data packet, where the network service header NSH of the data packet includes a first SPI, a first SI, and a second SPI, where the first SPI is used to indicate the first service chain. a path, where the second SPI is used to indicate a second service chain path, where the first service chain path and the second service chain path at least partially overlap.

The forwarding device may receive the data packet from the service classifier SC, or may receive the data packet from another forwarding device.

In the present application, the first SPI is the SPI of the service chain path in which the data packet is currently located, and the second SPI is the service flow to which the data packet to which the service classifier SC adds the data packet belongs. SPI of the business chain. That is, when the SC receives the data packet, the service chain corresponding to the data packet is determined, the SPI corresponding to the service chain is obtained, and then the SPI and the initial SI (for example, 255) are added to the data. The message is encapsulated in the NSH. The service chain corresponding to the data packet is determined, and the identifier of the service flow to which the data packet belongs is obtained according to the preset flow rule, and the flow mapping on the SC is searched according to the identifier of the obtained service flow. The table obtains the identifier of the service chain path corresponding to the identifier of the service flow. Each entry of the flow mapping table includes an identifier of the service flow and an identifier of the service chain path.

In the embodiment of the present application, each time the forwarding device forwards the data packet, the SI in the data packet is decremented by one.

Step 202: The forwarding device determines, according to the forwarding table, a next hop address and an NSH encapsulation information in the forwarding entry corresponding to the first SPI and the first SI; the NSH encapsulation information includes a jump information and a type tag; and the type tag indicates the forwarding entry according to the forwarding entry. The type of operation when forwarding a message.

The next hop address may be an address of the SF, the SFF, or the PS. The forwarding table is calculated by the service chain controller according to the deployment situation of the service chain and sent to each forwarding device.

Step 203: The forwarding device re-encapsulates the NSH as a data packet according to the NSH encapsulation information.

Step 204: The forwarding device sends the data packet re-packaging the NSH to the next hop address.

In the solution, in the solution, if the next hop address is an SF that does not support the NSH encapsulation, the forwarding device sends the data packet of the re-encapsulated NSH to the next hop address. Specifically, the forwarding device includes the NSH. The function of the proxy, the forwarding device will re-encapsulate the NSH in the data packet of the NSH, and then send the data packet to the next hop address. If the next hop address is an SF that supports NSH encapsulation, the forwarding device directly sends the data packet encapsulating the NSH to the next hop address.

In the embodiment of the present application, the first SPI, the SI, and the second SPI are encapsulated in the NSH of the data packet, where the first SPI indicates the first service chain path for forwarding the data packet, and the second SPI indicates the service chain control. The second service chain path specified by the service chain in which the data packet is located, where the first service path and the second service path partially overlap. In the embodiment of the present invention, the part of the first service chain path and the second service chain path are instructed by the first SPI, so that the path information in the forwarding table can be reused, thereby reducing the number of entries in the forwarding table, and further reducing the forwarding table. Memory usage.

The data packet after the NSH encapsulation provided by the embodiment of the present application can be carried in multiple types of packets. For example, the NSH is carried in various overlay packages such as VXLAN, GRE, and ETH.

NSH currently has two package formats. 2a and 2b are schematic diagrams showing the structure of two NSHs provided by the embodiments of the present application. As shown in FIG. 2a, the NSH includes protocol version information and length information 2100, and a format indication bit 2101. For example, the format indication bit 2101 of the NSH in FIG. 2a is 0x1, and the NSH in FIG. 2a includes the next protocol 2102. The field, along with the SPI2103 field and the service index SI2104 field, also includes a plurality of fixed length context headers, and context header-2108 is shown in Figure 2a. In NSH, the first SPI and the first SI can be placed in SPI2103 and SI2104 in Figure 2a, while the second SPI can be placed in a fixed length context header. The NSR has the next protocol 2102 field, which is used to carry the data packet protocol, and the NSH can carry the Layer 2 user packet and the Layer 3 user packet through the next protocol (next protocol) field. .

As shown in FIG. 2b, in another encapsulation format of the NSH, the NSH includes protocol version information and length information 2200, and a format indication bit 2201. For example, the format indication bit 2201 of the NSH in FIG. 2b is 0x2, in FIG. 2a. The NSH includes a variable length context header 2205 in addition to the next protocol 2202 field, and the SPI2203 field and the service index SI2204 field. In NSH, the first SPI and the first SI can be placed in SPI 2203 and SI 2204 in Figure 2b, while the second SPI can be placed in a variable length context header 2205.

The service flow corresponding to the data packet is determined according to the traffic classification rule on the SC, and the service chain corresponding to the service flow is determined, and the data packet is NSH encapsulated according to the service chain corresponding to the service flow. The SFF receives the forwarding table sent by the SFC, and forwards the received data packet according to the forwarding table. Specifically, the SFF identifies the first SPI and the first SI in the NSH header in the data packet when receiving the data packet, and searches the forwarding table according to the first SPI and the first SI, and forwards the data packet encapsulated by the NSH to the data packet. The next hop (SF or SFF) specified in the forwarding table. Figure 3 exemplarily shows a forwarding table on an SFF.

As shown in FIG. 3, each entry of the forwarding table includes SPI, SI, next hop address, transport protocol, and type flag. When the transport protocol points to the next hop device to send a data packet, the packet should be encapsulated in the encapsulation format corresponding to the transport protocol. The use of the transport protocol in the forwarding table in this application is the same as in the prior art. Therefore, in the following description, the forwarding protocol related content does not appear in the forwarding table of the present application. Flag is used to define the type of next hop. The type of the next hop indicated by the flag may include two types: null information (NA) and normal route forwarding (GoTo). When the type indicated by the flag is NA, it indicates that the data packet is forwarded normally along the service link. When the type indicated by the flag is GoTo, the SFF is the last hop of the service chain, and the next hop is directly redirected to the PS.

Based on the forwarding table shown in FIG. 3, the flag in the solution provided by the embodiment of the present application may also indicate two other types, namely, combining (combination) and separating (English: separate).

The operation type indicated by the type tag is merge, and the jump information includes the target SPI and the target SI, and the NSH is re-encapsulated for the data message according to the NSH encapsulation information, including: updating the first SPI in the NSH using the target SPI; and updating the NSH using the target SI The first SI; wherein the merged operation type is further used to indicate that the next hop address of the data packet on the second service chain path is the same as the next hop address on the first service chain path.

The operation type indicated by the type tag is separated, and the jump information includes the target SPI and the target SI, and the first SPI and the second SPI are different, and the NSH is re-packaged according to the NSH encapsulation information, including: obtaining the NSH encapsulation information. The target SPI and the target SI, when the target SPI and the second SPI are the same, use the target SPI to update the first SPI in the NSH; use the target SI to update the first SI in the NSH; wherein the separated operation type is also used to indicate: The next hop address of the data packet on the second service link path is different from the next hop address of the data packet on the first service chain.

Optionally, if the NSH encapsulation information includes null information or common route forwarding information, the data packet is directly forwarded to the next hop address.

The following is a few specific examples for illustrating the technical solutions provided by the embodiments of the present application.

Based on the above, FIG. 4 exemplarily shows a schematic diagram of a service chain provided by an embodiment of the present application. In FIG. 4, the service function classifier SC211, the service function forwarder SFF212, the SFF213, the SFF214, and the service chain tail server PS215 may form a plurality of service chains. Assume that the service function SF216 connected to the SFF 212, the service connected to the SFF 213, and the SF 220 and the SF 221 connected to the SFF 214 and the SF 221 support the NSH encapsulation. As shown in FIG. 5, based on the service chain shown in FIG. 4, it is assumed that there are two service chain paths whose tails coincide.

As can be seen from Figure 5, the two service chain paths of SPI0 and SPI1 differ only in the starting path part, and the two paths are the same from SFF213 to the end (the same part is shown in bold).

In order to embody the beneficial effects of the embodiments of the present application, in the embodiment of the present application, FIG. 5a, FIG. 5b, and FIG. 5c respectively exemplarily show that when there are two service chain paths of SPI0 and SPI1, the prior art SFF212, SFF213, and SFF214 Schematic diagram of the stored forwarding table. In order to be compatible with the prior art, the NSH package information includes the type flag flag shown in FIG.

It can be seen from Fig. 5a to Fig. 5c that although the two service chain paths of SPI0 and SPI1 are only different in the starting path part, the paths from SFF213 to the end are the same, that is, the paths of SPI0 and SPI1 in Fig. 5b and Fig. 5c. The same is true, but the paths of SPI0 and SPI1 are still stored in FIG. 5b and FIG. 5c, respectively, causing more problems in forwarding table entries.

Applying the solution provided by the present application, in order to be compatible with the prior art solution, the NSH encapsulation information in the prior art includes a flag. In the embodiment of the present application, a Context is added to the NSH encapsulation information, and a Context is used to store the jump information. For storage type tags. The forwarding table generated by using the solution provided by the embodiment of the present application is as shown in FIG. 5d, FIG. 5e and FIG. 5f. Optionally, a second SI may also be set, and the second SI is also placed in the context header. The example in which the second SI is included in FIGS. 5d to 5f in the following example is exemplified.

Since SFF212 is both the first SFF of SPI0 and the first SFF of SPI1, the forwarding table calculated by SFC for SFF212 includes both the forwarding entry corresponding to SPI0 and the forwarding entry corresponding to SPI1. As shown in FIG. 5d, the first SPI is 0, and the next hop corresponding to the data packet with the first SI being 255 is the IP address {1.1.1.1} of the SF216, the first SPI is 0, and the first SI is 254. The next hop corresponding to the data packet is the IP address of SFF213 {10.1.2.1}; the first SPI is 1, and the next hop corresponding to the data packet with the first SI being 255 is the IP address of SF2173 {1.1.2.1 }; Since the two paths in FIG. 5 start to coincide at SFF 213, the first SPI is 1, and the data packet with the first SI of 254 can be forwarded along the path of SPI0 after reaching the SFF 213, and its corresponding transfer The type tag of the published item indicates that the subsequent operation type is merge, and the jump information is {target SPI: 0, target SI: 254}.

In the forwarding table of the SFF 213 of FIG. 5e, only the forwarding entry corresponding to SPI0 is included in the forwarding table of the SFF 213 of the SPI1. Specifically, the first SPI is 0, and the next hop corresponding to the data packet of the first SI is 254 is the IP address {1.1.3.1} of the SF218. When the data packet is forwarded to the next hop, The first SI is decremented by one and the second SI is decremented by one. The information in the data message is updated as follows: the first SPI is 0, the first SI is 253, the second SPI is 0, and the second SI is 253. The first SPI is 0, and the next hop corresponding to the data packet of the first SI is 253 is the IP address {1.1.4.1} of the SF219. When the data packet is forwarded to the next hop, the first SI is used. Subtract one, the second SI is reduced by one. The information in the data message is updated as follows: the first SPI is 0, the first SI is 252, the second SPI is 0, and the second SI is 252. The first SPI is 0, and the next hop corresponding to the data packet with the first SI being 252 is the IP address {10.1.3.1} of the SFF214.

Since SPI0 and SPI1 are still merged on SFF214, in the forwarding table of SFF214 of Figure 5f, only the forwarding entry corresponding to SPI0 is available. In FIG. 5f, the first SPI is 0, and the next hop corresponding to the data packet with the first SI being 252 is the IP address {1.1.5.1} of the SF220. When the data packet is forwarded to the next hop, The first SI is decremented by one, and the second SI is decremented by one. The information in the data packet is updated as follows: the first SPI is 0, the first SI is 251, the second SPI is 0, and the second SI is 251. The first SPI is 0, and the next hop corresponding to the data packet of the first SI is 251 is VRFn (SFC), and the data packet is directly sent to the PS that sends the data packet to the SPI0. In the example, VRFn (SFC) in Figures 5 to 7 represents the last hop.

That is, in the embodiment of the present application, since the first SPI and the first SI are updated to SPI:0, SI:254 in the NSH encapsulation information of the SPI1 in the SFF 212, subsequent need in FIG. 5e and FIG. 5f The path of the SPI1 is separately stored, and the data packet of the SPI1 is directly taken to the path of the SPI0. It can be seen that, by using the solution provided by the embodiment of the present application, the coincidence path is indicated by the first SPI, and the path information in the forwarding table can be reused. Therefore, the number of entries in the forwarding table is reduced, thereby reducing the memory usage of the forwarding table.

Example two

It is assumed that the SF nodes support the NSH encapsulation. As shown in FIG. 6, there are two service chain paths in which the header and the tail overlap, but the middle portions do not coincide.

As can be seen from the RSP in Figure 6, the two service chain paths of SPI2 and SPI3 differ only in the middle path part (the same part is shown in bold). In the prior art, even if the two paths are overlapped, each forwarding path is stored in the forwarding table stored in the SFF. As shown in FIG. 5a-5c, the forwarding table entries are more.

Based on the service chain path shown in FIG. 6, the forwarding tables generated by the SFC for the SFF 212, SFF 213, and SFF 214 are shown in FIGS. 6a, 6b, and 6c, respectively.

The path of SPI2 is completely described in FIG. 6a to FIG. 6c, and details are not described herein again. The SPI3 will be described in detail below with reference to FIG. 6a to FIG. 6c:

In the service path shown in FIG. 6, after receiving the data packet whose first SPI is 2 and the first SPI is 254, the SFF 212 finds that the operation type indicated by the type tag in the corresponding forwarding table is separated, and the jump information is If it is not empty, it is determined that the data packet needs to be forwarded to another service chain path, and then the first SPI in the data packet is modified according to the jump information {target SPI:3, target SI: 254}, and the modification is performed. The first SI in the data packet is 254, and the modified data packet is forwarded according to the modified first SPI and the first SI.

According to the forwarding table of the SFF 213 of FIG. 6b, the first SPI in the data packet of the SPI3 is 3, and the next hop corresponding to the first SI is 254 is the IP address {1.1.4.1} of the SF219, and the data packet is in the data packet. When forwarding to the next hop, the first SI is decremented by one. The information in the data packet is updated as follows: the first SPI is 3, the first SI is 253, and the second SPI is 3. Moreover, the first SPI is 3, the first SI is 253, and the next hop corresponding to the second SPI is 3 is the IP address {10.1.3.1} of the SFF214. The operation type indicated by the type tag in the corresponding NSH package information is merge, and the target SPI information is SPI2, and the target SI information is SI253. The first SPI in the NSH is updated using the target SPI information; the first SI in the NSH is updated using the target SI information. In the updated SPI3 data message: the first SPI is 2, the first SI is 253, and the second SPI is 3.

According to the forwarding table of the SFF 214 of FIG. 6c, the first SPI in the data packet of the SPI3 is 2, and the next hop corresponding to the first SI is 253 is the IP address {1.1.5.1} of the SF220, and the data packet is in the data packet. When forwarding to the next hop, the first SI is decremented by one. The information in the data message of SPI3 is updated as follows: the first SPI is 2, the first SI is 252, and the second SPI is 3. Since the first SPI is 2, and the next hop corresponding to the data message of the first SI is 252 is VRFn (SFC), the data message is directly sent to the PS of SPI3.

That is, in the embodiment of the present application, when the SC performs the NSH encapsulation on the data packet of the SPI3, the first SPI is encapsulated as SPI2, and the first SI is encapsulated as SI255. Therefore, the SPI3 need not be stored in the forwarding table of FIG. 6a. When the SI is 255, the corresponding forwarding entry is used. When the SFF 212 forwards the SPI3 data packet, the SPI2 forwarding entry can be multiplexed. Further, since the operation type is a separate type flag in FIG. 6a, the SPI3 is used. The first SI in the data packet NSH of SI254 is restored to SPI3, and the SI is modified to SI254. Therefore, according to the forwarding table of SFF213 in FIG. 6b, the data packets of SPI2 and SPI3 can go their respective paths, further, due to FIG. 6b. According to the type of the operation, the first SPI is modified to SPI2, and the first SI is modified to SI253. Therefore, in FIG. 6c, it is not necessary to store the path information of SPI3, and only the path information of SPI2 can be multiplexed. Forward SPI3 data packets. It can be seen that the coincidence path is indicated by the first SPI, which can implement multiplexing of path information in the forwarding table, thereby reducing the number of entries in the forwarding table, thereby reducing the memory usage of the forwarding table.

Example three

Assuming that the SF nodes support NSH encapsulation, as shown in FIG. 7, there may be two header-coherent service chain paths in the structure shown in FIG.

As can be seen from the RSP in Figure 7, the two service chain paths of SPI4 and SPI5 differ only in the tail path portion (the same part is shown in bold). In the prior art, even if the two paths are overlapped, each forwarding path is stored in the forwarding table stored in the SFF. As shown in the example, the forwarding table entries are more.

Based on the service chain path shown in FIG. 7, the forwarding tables generated by the SFC for the SFF 212, SFF 213, and SFF 214 are shown in FIGS. 7a, 7b, and 7c, respectively.

The path of SPI4 is completely described in FIG. 7a to FIG. 7c, and details are not described herein again. SPI5 will be described in detail below with reference to FIG. 7a to FIG. 7c:

According to the forwarding table of SFF212 in FIG. 7a, since the first half of SPI5 and SPI4 are the same, after the SC performs NSH encapsulation on the data packet of SPI5, the first SPI in the data packet of SPI5 is 4, and the first SI is 255. The second SPI is 5. The next hop corresponding to the data packet is the IP address {1.1.1.1} of the SF216. When the data packet is forwarded to the next hop, the first SI is decremented by one. The information of the data packet is updated as follows: the first SPI is 4, the first SI is 254, and the second SPI is 5. Moreover, the first SPI is 4, and the next hop corresponding to the data packet of the first SI is 254 is the IP address {10.1.2.1} of the SFF213.

According to the forwarding table of the SFF 213 of FIG. 7b, the first SPI in the data packet of the SPI5 is 4, and the next hop corresponding to the first SI is 254 is the IP address {1.1.3.1} of the SF218, and the data packet is in the data packet. When forwarding to the next hop, the first SI is decremented by one. The information in the data packet is updated as follows: the first SPI is 4, the first SI is 253, and the second SPI is 5. The first SPI is 4, and the next hop corresponding to the data packet whose first SI is 253 is the IP address {1.1.4.1} of the SF219. When the data packet is forwarded to the next hop, the first SI is decremented by one. The information in the data message is updated as follows: the first SPI is 4, the first SI is 252, and the second SPI is 5. The first SPI is 4, and the next hop corresponding to the data packet with the first SI of 252 is the IP address {10.1.3.1} of the SFF214. The operation type indicated by the type tag in the corresponding NSH package information is separated. Since the first SPI and the second SPI of the data message are different, and the second SPI is the same as the target SPI, the target SPI is used to update the first in the NSH. The SPI updates the first SI in the NSH using the target SI. In the updated data message of SPI5, the first SPI is 5, the first SI is 252, the second SPI is 5, and the first SI is 252. The first SPI is 5, and the next hop corresponding to the data packet with the first SI being 252 is the IP address {1.1.5.1} of the SF220. When the data packet is forwarded to the next hop, the first SI is used. minus one. The information in the data packet is updated as follows: the first SPI is 5, the first SI is 251, and the second SPI is 5. Since the first SPI in the data packet of SPI5 is 5, and the next hop corresponding to the first SI is 251 is VRFn (SFC), the data packet is directly sent to the PS of SPI5.

That is, in the embodiment of the present application, when the SC performs NSH encapsulation on the data packet of the SPI5, the first SPI is encapsulated into SPI4, and the first SI is encapsulated as SI255. Therefore, in the forwarding table of FIG. 7a and FIG. 7b. It is not necessary to store the information of SI255 to SI253 of SPI5, and the information of SPI4 can be multiplexed. Further, since the type of operation indicated in FIG. 7b is a separate type flag, the first SI outside the data message of SI252 of SPI5 is used. Restore to SPI5 and restore SI to SI252, so SPI4 and SPI5 can follow their respective paths in the forwarding table of SFF214 in Figure 7c. It can be seen that, by using the solution provided by the embodiment of the present application, the coincidence path is indicated by the first SPI, and the path information in the forwarding table can be reused, thereby reducing the number of entries in the forwarding table, thereby reducing the memory usage of the forwarding table.

Optionally, in the embodiment of the present application, the RSP path may be generated by the SFC controller according to a service function path (SFP) of the client. The at least two RSPs with the longest coincidence path are queried from the existing multiple RSP paths, and the forwarding flow table is delivered to the corresponding SFF according to the at least two RSPs. Specifically, it is divided into the following cases:

In the first case, at least two service chain paths coincident with the tail: in the forwarding flow table on the previous SFF of the coincidence path: each of the at least two service chain paths that overlap in the tail except the target service link The operation type indicated by the type flag in the NSH encapsulation information corresponding to the SPI and SI of the link is set to merge, and the target SPI and the target SI are added; the target SPI and the target SI are the SPI and SI of the service link to be switched to.

In the second case, at least two service chain paths in which the head end and the tail overlap: the forwarding flow table on the last SFF of the head end coincidence path: the target service chain in at least two service chain paths where the head end and the tail overlap The operation type indicated by the type flag in the NSH package information corresponding to the SPI and SI of the path is set to be separated;

In the forwarding flow table on the previous SFF of the trailing coincidence path: the NSH encapsulation information corresponding to the SPI and SI of each service link except the target service link in the at least two service chain paths where the head end and the tail overlap The type of operation indicated by the medium type flag is set to merge and the target SPI and target SI are added; the target SPI and the target SI are the SPI and SI of the service link to be switched to.

In the third case, at least two service chain paths coincident at the head end, and a forwarding flow table on the last SFF of the head end coincidence path: at least two service chain paths in the at least two service chain paths where the head end and the tail end coincide The operation type indicated by the type flag in the NSH package information corresponding to the SPI and the SI is set to be separated.

In the embodiment of the present application, the existing service chain forwarding table is reused in a scenario where a large number of service chain paths are overlapped, and the number of forwarding entries of all SFF nodes in the service chain path is reduced, and the SFF can be quickly matched. Publish and forward, improve the forwarding performance of service chain equipment, and reduce equipment costs. In addition, in the embodiment of the present application, the extended NSH can also carry other service information therein, and all the SFF nodes can share the information carrying the service to expand the service.

Based on the same concept, the present application provides a data message forwarding device 800 for performing the above method flow. FIG. 8 is a schematic structural diagram of a data packet forwarding device provided by the present application. The forwarding device 800 includes a receiving unit 801, a processing unit 802, and a transmitting unit 803.

The receiving unit 801 in the embodiment of the present application is configured to receive a data packet of a service chain. The NSR of the data packet includes a first SPI and a first SI, and the data packet further includes a second SPI. The first SPI is used to indicate a first service chain path, and the second SPI is used to indicate a second service chain path. The first service chain path and the second service chain path at least partially coincide. In this application, the first SPI is the SPI of the service chain path in which the data packet is currently located, and the second SPI is the SPI of the service chain corresponding to the service flow to which the data packet added by the SC is the data packet.

The processing unit 802 is configured to determine, according to the forwarding table, a next hop address and an NSH encapsulation information in the forwarding entry corresponding to the first SPI and the first SI, and re-encapsulate the NSH according to the NSH encapsulation information; the NSH encapsulation information includes the hopping The information and type tag; the type tag indicates the type of operation when forwarding the message according to the forwarding entry. The next hop address may be an address of the SF, the SFF, or the PS. The forwarding table is calculated by the service chain controller according to the deployment of the service chain and sent to each forwarding device.

The sending unit 803 is configured to send the data packet of the re-packaged NSH to the next hop address. In the embodiment of the present application, each time the forwarding device forwards the data packet, the SI in the data packet is decremented by one. Optionally, the receiving unit 801 is specifically configured to: receive the data packet sent by the service function SF, and the processing unit 802 is further configured to: if the data packet sent by the service function SF is received by the receiving unit 801, the data packet is sent The first SI in the first one is reduced by one.

In the embodiment of the present application, the first SPI, the SI, and the second SPI are encapsulated in the NSH of the data packet, where the first SPI indicates the first service chain path for forwarding the data packet, and the second SPI indicates the service chain control. The second service chain path specified by the service chain in which the data packet is located, where the first service path and the second service path partially overlap. In the embodiment of the present invention, the part of the first service chain path and the second service chain path are instructed by the first SPI, so that the path information in the forwarding table can be reused, thereby reducing the number of entries in the forwarding table, and further reducing the forwarding table. Memory usage.

The type tag in the embodiment of the present application may include the indicated operation type as a merged type tag and the indicated operation type as a separate type tag. If the operation type indicated by the type tag is merge, and the jump information includes the target SPI and the target SI, the processing unit 802 is configured to: update the first SPI in the NSH using the target SPI; and update the first SI in the NSH using the target SI; The merged operation type is further used to indicate that the next hop address of the data packet on the second service chain path is the same as the next hop address on the first service chain path.

If the operation type indicated by the type tag is detached, and the jump information includes the target SPI and the target SI, and the first SPI and the second SPI are different, the processing unit 802 is configured to: acquire the target SPI and the target SI in the NSH package information. Updating the first SPI in the NSH using the target SPI when the target SPI and the second SPI are the same; updating the first SI in the NSH using the target SI; wherein the separated operation type is further used to indicate that the data message is in the second The next hop address on the service chain path is different from the next hop address of the data packet on the first service chain.

For specific examples of the above two types of labels, refer to the description of the above embodiments, and details are not described herein again.

Optionally, the first SPI is located in the SPI field of the NSH of the data packet, where the first SI is located in the SI field of the NSH of the data packet, and the second SPI is located in the context header of the NSH of the data packet. Since forwarding is performed according to the first SPI and the first SI, it is often necessary to access the first SPI and the first SI, and placing the first SPI and the first SI into the header may reduce the access delay.

It should be understood that the division of each unit above is only a division of a logical function, and the actual implementation may be integrated into one physical entity in whole or in part, or may be physically separated. In the embodiment of the present application, the receiving unit 801 and the sending unit 803 may be implemented by a communication interface, and the processing unit 802 may be implemented by a processor.

Based on the same concept, the present application provides a data message forwarding device 900 for performing the above method flow. FIG. 9 is a schematic structural diagram of a data packet forwarding device provided by the present application. The forwarding device 900 includes a processor 901, a memory 903, and a communication interface 902; wherein the processor 901, the memory 903, and the communication interface 902 are connected to each other through a bus 904.

The bus 904 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. The bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 9, but it does not mean that there is only one bus or one type of bus.

The memory 903 may include a volatile memory such as a random-access memory (RAM); the memory may also include a non-volatile memory such as a flash memory (flash) Memory), hard disk drive (HDD) or solid-state drive (SSD); the memory 410 may also include a combination of the above types of memory.

The communication interface 902 can be a wired communication access port, a wireless communication interface, or a combination thereof, wherein the wired communication interface can be, for example, an Ethernet interface. The Ethernet interface can be an optical interface, an electrical interface, or a combination thereof. The wireless communication interface can be a WLAN interface.

The processor 901 can be a central processing unit (CPU), a network processor (NP) or a combination of a CPU and an NP.

The processor 901 may further include a hardware chip. The hardware chip may be an application specific integrated circuit (ASIC), a programmable logic device (PLD) or a combination thereof. The PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a general array logic (GAL) or any combination.

Optionally, the memory 903 can also be used to store program instructions, and the processor 901 calls the program instructions stored in the memory 903, and can perform one or more steps in the embodiment shown in FIG. 2, or an optional implementation thereof. The forwarding device 900 is implemented to implement the functions of the forwarding device in the above method.

The processor 901 is configured to determine, according to the forwarding table, the next hop address and the NSH encapsulation information in the forwarding entry corresponding to the first SPI and the first SI, and re-encapsulate the NSH according to the NSH encapsulation information. The NSH encapsulation information includes a jump information and a type tag; the type flag indicates an operation type when the packet is forwarded according to the forwarding entry. The next hop address may be an address of the SF, the SFF, or the PS. The forwarding table is calculated by the service chain controller according to the deployment of the service chain and sent to each forwarding device. The communication interface 902 is configured to send the data packet of the re-packaged NSH to the next hop address. In the embodiment of the present application, each time the forwarding device forwards the data packet, the SI in the data packet is decremented by one. Optionally, the processor 901 is further configured to: if the data message sent by the service function SF is received through the communication interface 902, the first SI in the data packet is decremented by one.

In the embodiment of the present application, the communication interface 902 is configured to receive a data packet of the service chain. The NSH of the data packet includes a first SPI and a first SI, and the data packet further includes a second SPI. The first service chain path is indicated, and the second SPI is used to indicate the second service chain path, where the first service chain path and the second service chain path at least partially overlap. In this application, the first SPI is the SPI of the service chain path in which the data packet is currently located, and the second SPI is the SPI of the service chain corresponding to the service flow to which the data packet added by the SC is the data packet. Optionally, the communication interface 902 is configured to: receive a data packet sent by the service function SF.

In the embodiment of the present application, the first SPI, the SI, and the second SPI are encapsulated in the NSH of the data packet, where the first SPI indicates the first service chain path for forwarding the data packet, and the second SPI indicates the service chain control. The second service chain path specified by the service chain in which the data packet is located, where the first service path and the second service path partially overlap. In the embodiment of the present invention, the part of the first service chain path and the second service chain path are instructed by the first SPI, so that the path information in the forwarding table can be reused, thereby reducing the number of entries in the forwarding table, and further reducing the forwarding table. Memory usage.

The type tag in the embodiment of the present application may include the indicated operation type as a merged type tag and the indicated operation type as a separate type tag. If the operation type indicated by the type tag is merged, and the jump information includes the target SPI and the target SI, the processor 901 is configured to: update the first SPI in the NSH by using the target SPI; and update the first SI in the NSH by using the target SI; The merged operation type is further used to indicate that the next hop address of the data packet on the second service chain path is the same as the next hop address on the first service chain path.

If the operation type indicated by the type tag is detached, and the jump information includes the target SPI and the target SI, and the first SPI and the second SPI are different, the processor 901 is configured to: acquire the target SPI and the target SI in the NSH package information. Updating the first SPI in the NSH using the target SPI when the target SPI and the second SPI are the same; updating the first SI in the NSH using the target SI; wherein the separated operation type is further used to indicate that the data message is in the second The next hop address on the service chain path is different from the next hop address of the data packet on the first service chain.

For specific examples of the above two types of labels, refer to the description of the above embodiments, and details are not described herein again.

Optionally, the first SPI is located in the SPI field of the NSH of the data packet, where the first SI is located in the SI field of the NSH of the data packet, and the second SPI is located in the context header of the NSH of the data packet. Since forwarding is performed according to the first SPI and the first SI, it is often necessary to access the first SPI and the first SI, and placing the first SPI and the first SI into the header may reduce the access delay.

Those skilled in the art will appreciate that embodiments of the invention may be provided as a method, system, or computer program product. Thus, embodiments of the invention may be in the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware. Moreover, embodiments of the invention may take the form of a computer program product embodied on one or more computer usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.

The computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device. The apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.

These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device. The instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

It is apparent that those skilled in the art can make various modifications and variations to the embodiments of the present invention without departing from the spirit and scope of the application. Thus, it is intended that the present invention cover the modifications and variations of the embodiments of the invention.

Claims (11)

A data packet forwarding method, comprising: Receiving a data packet of the service chain, where the network service header NSH of the data packet includes a first service chain path identifier SPI and a first service index SI; the data packet further includes a second SPI; An SPI is used to indicate a first service chain path, and the second SPI is used to indicate a second service chain path, where the first service chain path and the second service chain path at least partially overlap; Determining, according to the forwarding table, a next hop address and an NSH encapsulation information in the forwarding entry corresponding to the first SPI and the first SI; the NSH encapsulation information includes a jump information and a type tag; The type of operation when the forwarding entry forwards the packet. Re-packaging the NSH for the data packet according to the NSH encapsulation information; Transmitting the data packet of the re-encapsulated NSH to the next hop address. The method of claim 1, wherein the operation type indicated by the type tag is a merge, and the jump information includes a target SPI and a target SI, and the data packet is the data packet according to the NSH package information. Repackage NSH, including: Updating the first SPI in the NSH by using the target SPI; Updating the first SI in the NSH by using the target SI; The merged operation type is also used to indicate: The next hop address of the data packet on the second service chain path is the same as the next hop address on the first service chain path. The method of claim 1, wherein the type of operation indicated by the type tag is separate, and the jump information comprises a target SPI and a target SI, and the first SPI and the second SPI are different The re-packaging the NSH for the data packet according to the NSH encapsulation information includes: Obtaining the target SPI and the target SI in the NSH package information, when the target SPI and the second SPI are the same, using the target SPI to update the first SPI in the NSH; Updating the first SI in the NSH by using the target SI; wherein the separated operation type is further used to indicate: The next hop address of the data packet on the second service chain path is different from the next hop address of the data packet on the first service chain. The method according to any one of claims 1 to 3, wherein the receiving the data packet of the service chain comprises: And receiving the data packet sent by the service function SF, and decrementing the first SI in the data packet by one. The method according to any one of claims 1 to 4, wherein the first SPI is located in an SPI field of an NSH of the data packet, and the first SI is located in an NSH of the data packet. In the SI field, the second SPI is located in a context header of the NSH of the data packet. A data packet forwarding device, comprising: a receiving unit, configured to receive a data packet of the service chain, where the network service header NSH of the data packet includes a first service chain path identifier SPI and a first service index SI, and the data packet further includes a second SPI; the first SPI is used to indicate a first service chain path, and the second SPI is used to indicate a second service chain path, where the first service chain path and the second service chain path at least partially overlap; a processing unit, configured to determine, according to the forwarding table, a next hop address and an NSH encapsulation information in the forwarding entry corresponding to the first SPI and the first SI; and re-encapsulating the NSH according to the NSH encapsulation information; The NSH encapsulation information includes a jump information and a type tag; the type tag indicates an operation type when the packet is forwarded according to the forwarding entry; And a sending unit, configured to send the data packet of the re-encapsulated NSH to the next hop address. The forwarding device according to claim 6, wherein the operation type indicated by the type tag is a merge, and the jump information includes a target SPI and a target SI, and the processing unit is configured to: Updating the first SPI in the NSH by using the target SPI; Updating the first SI in the NSH by using the target SI; The merged operation type is also used to indicate: The next hop address of the data packet on the second service chain path is the same as the next hop address on the first service chain path. The forwarding device according to claim 6, wherein the type of operation indicated by the type flag is separate, and the jump information includes a target SPI and a target SI, and the first SPI and the second SPI Different, the processing unit is used to: Obtaining the target SPI and the target SI in the NSH package information, when the target SPI and the second SPI are the same, using the target SPI to update the first SPI in the NSH; Updating the first SI in the NSH by using the target SI; wherein the separated operation type is further used to indicate: The next hop address of the data packet on the second service chain path is different from the next hop address of the data packet on the first service chain. The forwarding device according to any one of claims 6 to 8, wherein the receiving unit is configured to: Receiving the data packet sent by the service function SF; The processing unit is further configured to: And receiving, by the receiving unit, the data packet sent by the service function SF, and decrementing the first SI in the data packet by one. The forwarding device according to any one of claims 6 to 9, wherein the first SPI is located in an SPI field of an NSH of the data packet, and the first SI is located in the data packet. In the SI field of the NSH, the second SPI is located in a context header of the NSH of the data packet. A forwarding device for data packets, characterized in that the forwarding device comprises a processor, a communication interface and a memory; The memory is configured to store an instruction, the processor is configured to execute the memory stored instruction, and control the communication interface to receive or transmit a data message, when the processor executes the memory stored instruction, A forwarding device is operative to perform the method of any of claims 1-5.

Images