WO2014205660A1

WO2014205660A1 - Method, apparatus and routing device for forwarding data packet

Info

Publication number: WO2014205660A1
Application number: PCT/CN2013/077967
Authority: WO
Inventors: 傅瑜; 蒋胜
Original assignee: 华为技术有限公司
Priority date: 2013-06-26
Filing date: 2013-06-26
Publication date: 2014-12-31
Also published as: CN103748842B; CN103748842A

Abstract

The embodiments of the present invention provide a method, apparatus and routing device for forwarding a data packet so as to improve the forwarding efficiency of the data packet. The method comprises: receiving a data packet; adding a semantic packet header to an outer layer of an original packet header of the data packet, wherein the semantic packet header contains an identification bit which is used for identifying the data packet being a data packet carrying a semantic mark; if the data packet is a first data packet of a data stream, then adding a record regarding a next hop routing of the first data packet into a data record table; and according to the next hop routing of the first data packet, sending the first data packet. The method for forwarding a data packet provided in the embodiments of the present invention exempts an original packet header of a data packet from parsing, thereby shortening time for forwarding the data packet and improving the efficiency of forwarding the data packet.

Description

Method, device and routing device for forwarding data packets

Technical field

The present invention relates to the field of data communications, and in particular, to a method, an apparatus, and a routing device for forwarding a data packet.

Background technique

In the field of data communication, a data packet is generally composed of a header and a data, wherein the data belongs to a payload, which is a part of the communication system that the receiver really needs, and the packet header enables the data to be smoothly transmitted from the sender to the sender. Information attached to the recipient, including a five-tuple. The so-called quintuple usually refers to a set consisting of five sources: source address, source port, destination address, destination port, and protocol type. Taking an IP packet as an example, <192.168.1.1 10000 TCP 121.14.88.76 80> constitutes a quintuple, 192.168.1.1 is the source IP address, 10000 is the source port, TCP is the protocol type, and 121.14.88.76 is the destination IP address. 80 is the destination port. The meaning of the quintuple is that a terminal with an IP address of 192.168.1.1 passes the port 10000, uses the TCP protocol, and the terminal with the IP address is 121.14.88.76 and the port is 80; the quintuple is data. The bag header can uniquely identify important information for a session.

It is precisely because the quintuple can uniquely determine a session. Therefore, when an existing router forwards a data packet, it usually parses the packet header after receiving a data packet, and solves the five-member packet of the data packet. group. Based on the information in the quintuple and determining the next hop route by looking up the routing table, the data packet is forwarded to the next routing device and finally transmitted to the receiver of the data packet. For the router, if it is necessary to determine whether the currently received packet and the previous packet are the same stream, it is necessary to record the quintuple information of each packet.

The process of forwarding a data packet from the above prior art shows that the intermediate router determines the routing path according to the IP address carried in the data packet, so that although all source addresses and destination addresses of the same data stream are the same, they are received. All routers of these packets need to parse the headers of these packets to determine the next hop route, and then forward the packet, and the forwarding efficiency of the packet is relatively low.

Summary of the invention Embodiments of the present invention provide a method, an apparatus, and a routing device for forwarding a data packet, so as to improve forwarding efficiency of data packets.

An embodiment of the present invention provides a method for forwarding a data packet, where the method includes:

Receiving a data packet;

Adding a semantic header to an outer layer of the original header of the data packet, where the semantic header includes an identifier for identifying the data packet as a data packet carrying a semantic mark;

If the data packet is the first data packet of the data stream, adding a record of the next hop route of the first data packet to the data record table;

And sending the first data packet according to a next hop route of the first data packet.

Another embodiment of the present invention provides a method for transmitting a data packet, the method comprising: receiving a data packet, where the data packet includes a semantic packet header, where the semantic packet header is configured to identify the data packet as carrying a semantic tag The identification bit of the data packet;

Parsing the semantic header of the data packet;

Another embodiment of the present invention provides a method for transmitting a data packet, where the method includes: receiving a data packet;

Transmitting the data packet according to the semantic header.

Another embodiment of the present invention provides an apparatus for forwarding a data packet, where the apparatus includes: a first receiving module, configured to receive a data packet;

a first semantic packet header generating module, configured to add a semantic header to an outer layer of the original packet header of the data packet, where the semantic packet header includes an identifier bit for identifying the data packet as a data packet carrying a semantic tag;

a first record adding module, configured to add, in the data record table, a record about a next hop route of the first data packet if the data packet is a first data packet of the data flow; The first sending module is configured to send the first data packet according to a next hop route of the first data packet. Another embodiment of the present invention provides an apparatus for forwarding a data packet, where the apparatus includes:

a second receiving module, configured to receive a data packet, where the data packet includes a semantic packet header, where the semantic packet header includes an identifier bit for identifying the data packet as a data packet carrying a semantic tag;

a packet header parsing module, configured to parse a semantic header of the data packet;

a second record adding module, configured to add, in the data record table, a record about a next hop route of the first data packet if the data packet is a first data packet of the data flow;

And a second sending module, configured to send the first data packet according to a next hop route of the first data packet. Another embodiment of the present invention provides an apparatus for forwarding a data packet, where the apparatus includes:

a third receiving module, configured to receive a data packet;

a second semantic packet header generating module, configured to add a semantic header to an outer layer of the original packet header of the data packet, where the semantic packet header includes an identifier bit for identifying the data packet as a data packet carrying a semantic tag;

And a third forwarding module, configured to forward the data packet according to the semantic header.

As can be seen from the foregoing embodiments of the present invention, since only the semantic header of the current data packet needs to be parsed, according to the identifier bit of the data packet carrying the semantic token for identifying the data packet, it can be determined that the original data packet is not needed. The packet header is parsed again, but the current data packet is directly forwarded. Therefore, the method for forwarding a data packet provided by the embodiment of the present invention is exempt from the data, as compared with the prior art, which is required to parse the original packet header of the data packet (for example, the IP packet header of the IP data packet) and then forward the data packet through the query routing table. The analysis of the original packet header shortens the time for forwarding the data packet and improves the efficiency of forwarding the data packet.

DRAWINGS

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the description of the prior art or the embodiments will be briefly described below. Obviously, the drawings in the following description are only the present invention. For some embodiments, other figures may also be obtained as those skilled in the art from these figures.

1 is a schematic flowchart of a method for forwarding a data packet according to an embodiment of the present invention;

2 is a schematic structural diagram of an IP data packet including a semantic header according to an embodiment of the present invention; FIG. 3 is a schematic diagram of a data record table according to an embodiment of the present invention; FIG.

FIG. 3 is a schematic diagram of a data record table according to another embodiment of the present invention; FIG.

Figure 3-c is a schematic diagram of a data record table according to another embodiment of the present invention;

4 is a schematic flowchart of a method for forwarding a data packet according to another embodiment of the present invention;

FIG. 5 is a schematic diagram of a data record table according to another embodiment of the present invention; FIG.

6 is a schematic flowchart of a method for forwarding a data packet according to another embodiment of the present invention;

7 is a schematic structural diagram of an apparatus for forwarding a data packet according to an embodiment of the present invention;

FIG. 8 is a schematic structural diagram of an apparatus for forwarding a data packet according to another embodiment of the present invention; FIG.

FIG. 9 is a schematic structural diagram of an apparatus for forwarding a data packet according to another embodiment of the present invention;

FIG. 10 is a schematic structural diagram of an apparatus for forwarding a data packet according to another embodiment of the present invention;

11 is a schematic structural diagram of an apparatus for forwarding a data packet according to another embodiment of the present invention; FIG. 11 is a schematic structural diagram of an apparatus for forwarding a data packet according to another embodiment of the present invention; FIG. 12 is another embodiment of the present invention; The device structure diagram of the forwarding data packet provided by the example.

detailed description

BRIEF DESCRIPTION OF THE DRAWINGS The technical solutions in the embodiments of the present invention will be described in detail below with reference to the accompanying drawings. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention are within the scope of the present invention.

FIG. 1 is a schematic flowchart of a method for forwarding a data packet according to an embodiment of the present invention. The executor may be a routing device at the edge of the network, that is, a routing device that serves as an ingress node in the network operated by the operator. The method illustrated in FIG. 1 mainly includes step S101, step S102 and step S103, and the detailed description: 3⁄4 port:

5101, Receive the data packet.

5102. Add a semantic header to an outer layer of the original header of the data packet, where the semantic header includes an identifier bit for identifying the data packet as a data packet carrying a semantic mark.

In the embodiment of the present invention, the semantic header is an information body added to the outer layer of the original packet header, and may be generated by the routing device located at the edge of the network after receiving the data packet entering the network. Taking an IP packet as an example, Figure 2 shows a schematic diagram of the structure of an IP packet containing a semantic header. The semantic header of the example shown in FIG. 2 may include, in addition to the identifier bit, a stream identifier (flow ID) field and a semantic tag of the data stream to which the data packet belongs, wherein the identifier bit is used to identify the data. A package is a data packet carrying a semantic mark. A semantic mark is used to represent semantic information of a certain special meaning, and its syntax can be similar to XML syntax. For example, taking XML-like syntax in semantic markup as an example, its semantic information includes: <security level = "3"/security> is used to identify the security requirement level of the packet; application id ="5" /application is used to identify The business information of the packet; <user grade ="1" /1^1 is used to identify the user's level; <flow type = "2"/flow> is used to identify the traffic type; <Qos grade = "4" /Qos > Used to identify the quality of service, and so on. In the embodiment of the present invention, the semantic information may also be an implementation other than the XML syntax. As another embodiment of the semantic information of the present invention, the semantic information may also be expressed using a program, for example, using an executable program.

It should be noted that the semantic header illustrated in FIG. 2 is a case where the stream identifier is independent of the semantic token. In fact, the semantic token in the semantic header may also include the stream identifier. In either form, the semantic markup may only contain the security requirement level, the user level and the traffic type, or only one semantic information in the security requirement level, the user level, the traffic type, and the flow identifier, or may be the semantic information described above. random combination.

S103. Forward the data packet according to the semantic header.

It should be noted that the foregoing semantic information is merely an exemplary description of the semantic markup, and the corresponding semantic information may be provided according to the requirements of the operator, and may be differentiated and forwarded during forwarding, thereby satisfying the operator's demand for differentiated services. For example, the data can be forwarded to the secure router according to the security requirement level, or the user-level data packet can be preferentially forwarded according to the user level. After receiving the packet-to-semantic header parsing, the intermediate routing device of the network, if it finds that there is an identifier, does not need to continue parsing the original packet header after the semantic packet header to forward the data packet.

According to the method for forwarding a data packet provided by the foregoing embodiment of the present invention, since only the semantic header of the received data packet needs to be parsed, according to the identifier bit of the data packet carrying the semantic identifier for identifying the data packet, It can be judged that the original packet header of the data packet need not be parsed again, but the data packet is directly forwarded. Therefore, compared with the prior art, it is required to parse the original packet header of the data packet (for example, the IP packet header of the IP data packet), and then forward the data packet by querying the routing table. The method of forwarding the data packet eliminates the parsing of the original packet header of the data packet, thereby shortening the time for forwarding the data packet and improving the efficiency of forwarding the data packet.

Referring to FIG. 4, it is a schematic flowchart of a method for forwarding a data packet according to an embodiment of the present invention. The executor may be a routing device at the edge of the network, that is, a routing device that serves as an ingress node in the network operated by the operator. The method illustrated in FIG. 4 mainly includes step S401, step S402 and step S403, and the detailed description: 3⁄4 port:

5401, receiving a data packet.

5402. Add a semantic header to an outer layer of the original packet header of the data packet, where the semantic packet header includes an identifier bit for identifying the data packet as a data packet carrying a semantic mark.

In this embodiment, the semantic header contains the stream identifier of the data stream to which the data packet belongs, and its structure is the same as that of the semantic header in the foregoing embodiment, as shown in FIG. Semantic values in the semantic header can be defined in advance by the operator according to the differentiated requirements of the existing network, and are issued by a unified controller (Controller), or negotiated in advance in the carrier domain. The semantic parsing table is directly delivered. After the router in the domain receives the data packet carrying the semantic packet header, the relevant processing rules according to the meaning of the semantic value can be dynamically configured by the operator or the network administrator.

5403. If the data packet is the first data packet of the data flow, add a record about the next hop route of the first data packet in the data record table.

In this embodiment, the data record table records the next hop route of each data packet belonging to the same data stream according to the flow identifier carried by the carried semantic header. Since the data packet is the first data packet of the data flow, if there is no corresponding record of the first data packet in the data record table, the record of the next hop route of the first data packet may be added in the data record table, and the structure and structure thereof are The data recording table of any of the drawings of the foregoing embodiment from Fig. 3-a to Fig. 3-c is similar. It should be noted that, since the data packet is the first data packet of the data flow, the data record table does not have a record of the next hop route of the data packet, and therefore, the original packet header of the first data packet, such as an IP packet header, may be used. Parse and obtain the next hop route by querying the routing table. For example, the data packet marked by the flow is the first data packet of the data flow whose flow identifier is. In the example data record table of FIG. 3-a, the next hop record of the data packet included in the data flow with no flow identifier is, Figure 3-a shows an example of a data record table with corresponding records added. The data record table after the record is added is shown in Figure 5.

S404: Send the first data packet according to a next hop route of the first data packet. As described above, since the received data packet is the first data packet of the data flow, the data record table does not have a record of the next hop route of the data packet, and therefore, the first data can be the same as the prior art. The original packet header of the packet, for example, the IP header, is parsed, and the next hop route is obtained by querying the routing table, and is sent out, for example, to the intermediate routing device.

If the data packet received in step S401 is a subsequent data packet of the data stream, a semantic packet header is added to the outer layer of the original packet header of the subsequent data packet, and the data record table is queried to obtain the next hop route of the first data packet. And then transmitting the subsequent data packet according to the record of the next hop route of the first data packet.

Similar to the foregoing embodiment, in the embodiment shown in FIG. 4, the semantic header may include a flow identifier (flow ID) field and a semantic tag of the data stream to which the data packet belongs, in addition to the identifier bit. Etc., wherein the identifier bit is used to identify that the data packet is a data packet carrying a semantic mark, and the semantic mark is used to represent semantic information of a certain special meaning, and the syntax may be similar to the XML syntax. For example, taking XML-like syntax in semantic markup as an example, its semantic information includes: <security level = "3" /security> is used to identify the security requirement level of the packet; application id ="5" /application is used to identify The service information of the packet; <user grade ="1" /user> is used to identify the user's level; <flow type = "2" /flow> is used to identify the traffic type; <Qos grade = "4" /Qos> Used to identify the quality of service, and so on. In this embodiment, the semantic information may also be an implementation other than the XML syntax. As another embodiment of the semantic information of the present invention, the semantic information can also be expressed using a program, for example, using an executable program.

It should be noted that, in this embodiment, the flow identifier may be independent of the semantic mark. In fact, the semantic mark in the semantic header may also include the flow identifier. In either form, the semantic markup may only contain a security requirement level, a user level and a traffic type, or only one semantic information in a security requirement level, a user level, a traffic type, and a flow identifier, or may be the above semantic information. random combination.

According to the method for forwarding a data packet provided by the foregoing embodiment of the present invention, since the flow identifier of the data stream to which the data packet belongs is obtained only after the parsing semantic packet header is obtained, the data can be forwarded by querying the next hop route of the data packet from the data record table. package. Therefore, the method for forwarding a data packet provided by the embodiment of the present invention saves forwarding data, as compared with the prior art, which requires parsing the original packet header of the data packet (for example, the IP packet header of the IP data packet) and forwarding the data packet by querying the routing table. The time of the package improves the efficiency of forwarding packets. FIG. 6 is a schematic flowchart of a method for forwarding a data packet according to an embodiment of the present invention. The executor may be a routing device at the edge of the network, that is, a routing device that serves as an ingress node in the network operated by the operator. The method illustrated in FIG. 6 mainly includes step S601, step S602, step S603, and step S604, which are described in detail as follows:

S601, receiving a data packet.

In this embodiment, the data packet includes a semantic header, and the semantic header includes an identification bit for identifying the data packet as a data packet carrying a semantic token.

5602, parsing the semantic header of the data packet.

S603. If the data packet is the first data packet of the data flow, add a record about the next hop route of the first data packet in the data record table.

In this embodiment, the data record table records the next hop route of each data packet belonging to the same data stream according to the flow identifier carried by the carried semantic header. Since when the data packet is the first data packet of the data stream, and there is no corresponding record of the first data packet in the data record table, a record of the next hop route of the first data packet can be added to the data record table. It should be noted that, since the data packet is the first data packet of the data flow, the data record table does not have a record of the next hop route of the data packet, and therefore, the original packet header of the first data packet, such as an IP packet header, may be used. Parse and obtain the next hop route by querying the routing table. For example, the data packet marked by the flow is the first data packet of the data flow whose flow identifier is, and the next hop record of the data packet included in the data flow whose flow identifier is not in the sample data record table in FIG. 3-a is Figure 3-a shows an example of a data record table with corresponding records added. The data record table after the record is added is shown in Figure 5.

S604: Send the first data packet according to a next hop route of the first data packet.

As described above, since the data packet is the first data packet of the data stream, there is no record of the next hop route of the data packet in the data record table, and therefore, the original data packet can be the same as the prior art. The packet header, for example, the IP header, is parsed, and the next hop route is obtained by querying the routing table, and sent out, for example, to the intermediate routing device.

If the data packet received in step S601 is a subsequent data packet of the data stream, querying the record of the next hop route of the first data packet in the data record table, and then according to the next hop route of the first data packet Record, send the subsequent data packet. As described above, in this embodiment, the data record table records the next hop route of each data packet belonging to one data stream according to the flow identifier carried by the semantic packet header. Since the received data packet is a subsequent data packet of the data stream, a record of the next hop route of the data packet can be queried in the data record table, that is, if the data packet is a follow-up to the data stream The data packet is used to query the record of the next hop route of the first data packet in the data record table, and send the subsequent data packet according to the record of the next hop route of the first data packet.

Similar to the foregoing embodiment, in the embodiment shown in FIG. 6, the semantic header includes, in addition to the identifier bit, a stream identifier (flow ID) field and a semantic tag of the data stream to which the data packet belongs. And so on, wherein the identifier bit is used to identify that the data packet is a data packet carrying a semantic mark, and the semantic mark is used to represent semantic information of a certain special meaning, and the syntax thereof can be similar to the XML syntax. For example, taking XML-like syntax in semantic markup as an example, its semantic information includes: <security level = "3" /security> is used to identify the security requirement level of the packet; application id ="5" /application is used to identify The business information of the packet; <user grade =" 1 " /1^61 is used to identify the user's level; <flow type = "2" /flow> is used to identify the traffic type; <Qos grade = "4" /Qos > Used to identify the quality of service, and so on. If the semantic tag includes the security requirement level, in the embodiment of the present invention, the data packet may be forwarded to a corresponding security router in the domain according to the security requirement level.

In this embodiment, the semantic information may also be an implementation other than the XML syntax. As another embodiment of the semantic information of the present invention, the semantic information may also be expressed using a program, for example, using an executable program.

According to the method for forwarding a data packet provided by the foregoing embodiment of the present invention, since the flow identifier of the data stream to which the data packet belongs is obtained only after the parsing semantic packet header is obtained, the data can be forwarded by querying the next hop route of the data packet from the data record table. package. Therefore, compared with the prior art, it is required to parse the original packet header of the data packet (for example, the IP packet header of the IP data packet), and then forward the data packet by querying the routing table. The method of forwarding data packets saves time for forwarding data packets and improves the efficiency of forwarding data packets. To save resources, you can also set the aging time for records in the data record table. In this way, the aging time set in the data record table can be timed. If the aging time is not full, the subsequent data packet of the same data stream is not received, and the next hop route of the first data packet in the data record table is deleted. recording. For example, for the data record table illustrated in FIG. 3-a, if the aging time T is set for the record of the data flow with the flow identifier of /5, the aging time T is counted, and after the aging time is full, if not received, identified as stream / ₅ subsequent data packet, the data records in the table of the stream identifier / next-hop ₅ data streams first data packet this record is deleted, the deleted data recording table after recording as in FIG. 3 -c is shown.

Referring to FIG. 7, FIG. 7 is a schematic structural diagram of an apparatus for forwarding a data packet according to an embodiment of the present invention. For the convenience of description, only the parts related to the embodiment of the present invention are shown. The device for forwarding a data packet as illustrated in FIG. 7 may be a routing device at the edge of the network, that is, a routing device as an ingress node in the network operated by the operator, including a first receiving module 701, a first semantic packet header generating module 702, and a A record adding module 703 and a first sending module 704, wherein:

The first receiving module 701 is configured to receive a data packet.

a first semantic header generating module 702, configured to add a semantic header to an outer layer of the original header of the data packet, where the semantic header includes an identifier for identifying the data packet as a data packet carrying a semantic mark;

a first record adding module 703, configured to add, in the data record table, a record about a next hop route of the first data packet if the data packet is a first data packet of the data stream;

The first sending module 704 is configured to send the first data packet according to the next hop route of the first data.

In the apparatus for forwarding a packet as exemplified in Fig. 7, the semantic header includes a stream identifier of a data stream to which the packet belongs, and its structure is the same as that of the semantic header in the foregoing embodiment, as shown in Fig. 2. Semantic values in the semantic header can be defined in advance by the operator according to the differentiated requirements of the existing network, and are sent by a unified controller (Controller), or negotiated in advance in the carrier domain. The semantic parsing table is directly delivered. After the router in the domain receives the data packet carrying the semantic packet header, the relevant processing rules according to the meaning of the semantic value can be dynamically configured by the operator or the network administrator. The data record table records the same data stream according to the flow identifier carried by the carrying semantic header. The next hop route for each packet. Since the data packet is the first data packet of the data stream, the first record adding module 703 may add a next hop route for the first data packet in the data record table, if the data record table does not have a corresponding record of the first data packet. The record is similar in structure to the data record table of any of the drawings of the foregoing embodiment from Fig. 3-a to Fig. 3-c. It should be noted that, since the data packet is the first data packet of the data flow, the data record table does not have a record of the next hop route of the data packet, and therefore, the original packet header of the first data packet, such as an IP packet header, may be used. Parse and obtain the next hop route by querying the routing table. For example, the data packet marked by the flow is the first data packet of the data flow whose flow identifier is. In the example data record table of FIG. 3-a, the next hop record of the data packet included in the data flow with no flow identifier is, Figure 3-a shows an example of a data record table with corresponding records added. The data record table after the record is added is shown in Figure 5.

As described above, since the data packet received by the first receiving module 701 is the first data packet of the data stream, there is no record of the next hop route of the data packet in the data record table, and therefore, it can be the same as the prior art. The original packet header of the first data packet, for example, the IP packet header, is parsed, and the next hop route is obtained by querying the routing table, and the first sending module 704 sends the next packet to the intermediate routing device.

It should be noted that, in the foregoing implementation of the apparatus for forwarding a data packet, the division of each functional module is merely an example. In actual applications, the foregoing may be considered according to requirements, such as configuration requirements of corresponding hardware or convenience of implementation of software. The function assignment is performed by different functional modules, that is, the internal structure of the device for forwarding the data packet is divided into different functional modules to complete all or part of the functions described above. Moreover, in practical applications, the corresponding functional modules in this embodiment may be implemented by corresponding hardware, or may be executed by corresponding hardware, for example, the foregoing first semantic header generating module may be executed. The foregoing hardware for adding a semantic header to the outer layer of the original packet of the data packet, for example, the first semantic header generator, may also be a general processor or other hardware device capable of executing a corresponding computer program to perform the foregoing functions; The first record adding module may be hardware having a function of performing the foregoing, if the data packet is the first data packet, and adding a recording function for the next hop route of the first data packet in the data recording table, for example, The first record adder may also be a general processor or other hardware device capable of executing a corresponding computer program to perform the aforementioned functions (the various embodiments provided in this specification may apply the above described principles).

The apparatus for forwarding a data packet as illustrated in FIG. 7 further includes a first query module 801 and a first forwarding module 802. The apparatus for forwarding a data packet according to another embodiment of the present invention, as shown in FIG. 8, wherein: the first query module 801 is configured to query the data record table to obtain a next hop route of the first data packet. recording;

The first forwarding module 802 is configured to send the subsequent data packet according to the record of the next hop route of the first data packet;

The first semantic header generating module 702 is further configured to add a semantic header to an outer layer of the original header of the subsequent data packet if the data packet is a subsequent data packet of the data flow.

In the apparatus for forwarding a data packet illustrated in FIG. 7, the semantic header further includes a semantic mark, the semantic mark including one or any combination of a security requirement level, a user level, a traffic type, and a flow identifier, and the flow identifier is used for Identifying a data flow to which the data packet belongs; or, the semantic header further includes a semantic mark and a flow identifier independent of the semantic mark, the semantic mark including one or any combination of a security requirement level, a user level, and a traffic type The flow identifier is used to identify a data flow to which the data packet belongs. Similar to the foregoing embodiment, the semantic header may include a flow identifier (flow ID) field and a semantic tag of the data stream to which the data packet belongs, in addition to the identifier bit, wherein the identifier bit is used to identify the identifier. A data packet is a data packet carrying a semantic mark. A semantic mark is used to represent semantic information of a certain special meaning, and its syntax can be similar to XML syntax. For example, taking XML-like syntax in semantic markup as an example, its semantic information includes: <security level = "3" /security> is used to identify the security requirement level of the packet; application id ="5" /application is used to identify The business information of the packet; <user grade ="1" /1^1 is used to identify the user's level; <flow type = "2" /flow> is used to identify the traffic type; <Qos grade = "4" /Qos > Used to identify the quality of service, and so on. In this embodiment, the semantic information may also be an implementation other than the XML syntax. As another embodiment of the semantic information of the present invention, the semantic information may also be expressed using a program, for example, using an executable program. It should be noted that, in this embodiment, the flow identifier may be independent of the semantic mark. In fact, the semantic mark in the semantic header may also include the flow identifier.

FIG. 9 is a schematic structural diagram of an apparatus for forwarding a data packet according to another embodiment of the present invention. For the convenience of description, only parts related to the embodiment of the present invention are shown. The device for forwarding a data packet as illustrated in FIG. 9 may be an intermediate routing device of the network, that is, other routing devices in the network operated by the operator, except for the ingress node routing device, including the second receiving module module 901 and the packet header parsing module. Block 902, second record adding module 903 and second sending module 904, wherein:

a second receiving module 901, configured to receive a data packet, where the data packet includes a semantic packet header, where the semantic packet header includes an identifier bit for identifying the data packet as a data packet carrying a semantic tag;

a header parsing module 902, configured to parse a semantic header of the data packet;

a second record adding module 903, configured to add, in the data record table, a record about a next hop route of the first data packet if the data packet is a first data packet of the data stream;

The second sending module 904 is configured to send the first data packet according to a next hop route of the first data packet.

The apparatus for forwarding a data packet as illustrated in FIG. 9 further includes a second query module 1001, such as the apparatus for forwarding a data packet provided by another embodiment of the present invention as shown in FIG. The second query module 1001 is configured to query the record of the next hop route of the first data packet in the data record table if the data packet is a subsequent data packet of the data stream. The second sending module 904 is further configured to send the subsequent data packet according to the record of the next hop route of the first data packet.

In the apparatus for forwarding a data packet as illustrated in FIG. 9, the semantic header further includes a semantic mark, the semantic mark including one or any combination of a security requirement level, a user level, a traffic type, and a flow identifier, where the flow identifier is used. And identifying the data flow to which the data packet belongs; or the semantic header further includes a semantic mark and a flow identifier independent of the semantic mark, the semantic mark including one or any of a security requirement level, a user level, and a traffic type In combination, the flow identifier is used to identify a data flow to which the data packet belongs. Similar to the foregoing embodiment, the semantic header may include a flow identifier (stream ID) field and a semantic tag of the data stream to which the data packet belongs, in addition to the identifier bit, wherein the identifier bit is used to identify the identifier. A data packet is a data packet carrying a semantic mark. A semantic mark is used to represent semantic information of a certain special meaning, and its syntax can be similar to XML syntax. For example, taking XML-like syntax in semantic markup as an example, its semantic information includes: <security level = "3"/security> is used to identify the security requirement level of the packet; application id ="5" /application is used to identify The business information of the packet; <user grade ="1" /1^1 is used to identify the user's level; <flow type = "2"/flow> is used to identify the traffic type; <Qos grade = "4" /Qos > Used to identify the quality of service, and so on. In this embodiment, the semantic information may also be an implementation other than the XML syntax. As another embodiment of the semantic information of the present invention, the semantic information may also use a program table. To, for example, use an executable program to express. It should be noted that, in this embodiment, the flow identifier may be independent of the semantic mark. In fact, the semantic mark in the semantic header may also include the flow identifier.

In the above embodiment, if the semantic tag includes the security requirement level, the second sending module 904 is further configured to forward the data packet to a corresponding security router in the domain according to the security requirement level.

The apparatus for forwarding data packets illustrated in FIG. 9 or FIG. 10 further includes a timing module 1101 and a record deletion module 1102, and the forwarding data packet provided by another embodiment of the present invention is shown in FIG. 11-a or FIG. 11-b. Device, where:

The timing module 1101 is configured to time the aging time set by the data record table, and the record deletion module 1102 is configured to delete the subsequent data packet that belongs to the same data stream when the aging time is full. A record of the next hop route of the first data packet in the data record table. For example, for the data record table illustrated in FIG. 3-a, if the aging time T is set for the record of the data stream whose stream identifier is /5, the timing module 1101 counts the aging time T, after the aging time is full, if If the subsequent data packet whose stream identifier is / ₅ is not received, the record deletion module 1102 deletes the record of the next hop route of the first data packet of the data stream whose stream identifier is /5 in the data record table, and deletes the record after deleting the record. The data record table is shown in Figure 3-c. In this way, resources can be saved.

Referring to FIG. 12, it is a schematic structural diagram of an apparatus for forwarding a data packet according to another embodiment of the present invention. For the convenience of description, only parts related to the embodiment of the present invention are shown. The device for forwarding a data packet as illustrated in FIG. 12 may be a routing device at the edge of the network, that is, a routing device as an ingress node in the network operated by the operator, including a third receiving module 1201, a second semantic header generating module 1202, and a The three forwarding module 1203, wherein:

a third receiving module 1201, configured to receive a data packet;

The second semantic packet header generating module 1202 is configured to add a semantic header to an outer layer of the original packet header of the data packet, where the semantic packet header includes an identifier bit for identifying the data packet as a data packet carrying a semantic tag;

The third forwarding module 1203 is configured to forward the data packet according to the semantic header.

In the apparatus for forwarding a data packet illustrated in FIG. 12, the semantic header further includes a semantic mark, the semantic mark including one or any combination of a security requirement level, a user level, a traffic type, and a flow identifier. The flow identifier is used to identify a data flow to which the data packet belongs; or the semantic header further includes a semantic mark and a flow identifier independent of the semantic mark, where the semantic mark includes a security requirement level, a user level, and a traffic type. In one or any combination, the flow identifier is used to identify a data flow to which the data packet belongs.

In another aspect, still another embodiment of the present invention provides a computer readable storage medium, which may be a computer readable storage medium included in the memory in the above embodiment; There is a computer readable storage medium that is not assembled into the terminal. The computer readable storage medium stores one or more programs, and the one or more programs are used by one or more processors to perform a method of forwarding a data packet, the method comprising:

Receiving a data packet;

In the second possible implementation manner that the first possible implementation is provided as a cornerstone, the method further includes:

If the data packet is a subsequent data packet of the data stream, adding a semantic header to an outer layer of the original packet header of the subsequent data packet;

Querying the data record table to obtain a record of a next hop route of the first data packet;

Sending the subsequent data packet according to the record of the next hop route of the first data packet.

Assuming that the foregoing is a first possible implementation manner, in a third possible implementation manner that the first possible implementation is provided as a cornerstone, the semantic header further includes a semantic mark, and the semantic mark includes security One or any combination of a requirement level, a user level, a traffic type, and a flow identifier, where the flow identifier is used to identify a data flow to which the data packet belongs.

Assuming that the above is a first possible implementation, in a fourth possible implementation provided by the first possible implementation as a cornerstone, the semantic header also includes semantic markup and is independent of The stream identifier of the semantic tag, the semantic tag includes one or any combination of a security requirement level, a user level, and a traffic type, and the flow identifier is used to identify a data flow to which the data packet belongs.

Receiving a data packet, the data packet includes a semantic packet header, and the semantic packet header includes an identifier bit for identifying the data packet as a data packet carrying a semantic mark;

Parsing the semantic header of the data packet;

If the data packet is a subsequent data packet of the data stream, querying a record of a next hop route of the first data packet in the data record table;

Assuming that the above is a first possible implementation, in a fourth possible implementation provided by the first possible implementation as a cornerstone, the semantic header further includes a semantic mark and is independent of the semantic mark The stream identifier includes one or any combination of a security requirement level, a user level, and a traffic type, and the flow identifier is used to identify a data flow to which the data packet belongs.

Assuming the above is the third and fourth possible implementation, then in the third or fourth possible implementation In a fifth possible implementation manner, the method further includes: forwarding, according to the security requirement level, the data packet to a corresponding security router in the domain.

殳The above are the first, second, third, fourth and fifth possible embodiments, and the first, second, third, fourth or fifth possible embodiments are provided as the basis In the six possible implementation manners, the method further includes:

Counting the aging time set by the data record table;

If the subsequent data packet of the same data stream is not received when the aging time is full, the record of the next hop route of the first data packet in the data record table is deleted.

Receiving a data packet;

Transmitting the data packet according to the semantic header.

In the second possible implementation manner that the first possible implementation is provided as a cornerstone, the semantic header further includes a semantic mark, and the semantic mark includes security. One or any combination of a requirement level, a user level, a traffic type, and a flow identifier, where the flow identifier is used to identify a data flow to which the data packet belongs.

The foregoing is a first possible implementation manner, and in a third possible implementation manner that the first possible implementation is provided as a cornerstone, the semantic header further includes a semantic mark and is independent of the semantic mark. The stream identifier includes one or any combination of a security requirement level, a user level, and a traffic type, and the flow identifier is used to identify a data flow to which the data packet belongs.

An embodiment of the present invention further provides an intermediate routing device of a network, including: an input device, an output device, a memory, and a processor, where the memory is used to store a data record table, where the data record table is carried according to The stream identifier carried by the semantic packet header records the next hop route of each data packet belonging to a data stream. The processor performs the following steps: receiving a data packet, where the data packet includes a semantic packet header, and the semantic packet header includes The identifier is used to identify the identifier of the data packet carrying the semantic mark; parse the semantic header of the data packet; if the data packet is the first data packet of the data flow, add a relevant information in the data record table Recording a next hop route of the first data packet; sending the first data packet according to a next hop route of the first data packet.

Another embodiment of the present invention further provides an edge routing device for a network, including: an input device, an output device, a memory, and a processor, where the memory is configured to store a data record table, where the data record table carries a flow identifier carried by the semantic packet header Recording a next hop route of each data packet belonging to the same data stream; wherein the processor performs the following steps: receiving a data packet; adding a semantic header to an outer layer of the original packet header of the data packet, where the semantic packet header includes An identifier for identifying the data packet as a data packet carrying a semantic mark; if the data packet is a first data packet of the data flow, adding a next hop route for the first data packet in the data record table Recording; transmitting the first data packet according to a next hop route of the first data packet.

The embodiment of the present invention further provides a network edge routing device, including: an input device, an output device, a memory, and a processor, where the memory is used to store a data record table, and the data record table records the same genus according to the flow identifier carried by the semantic packet header. a next hop route for each packet of a data stream; wherein the processor performs the following steps:

Receiving a data packet;

Transmitting the data packet according to the semantic header.

It should be noted that the information interaction, the execution process, and the like between the modules/units of the foregoing device are the same as the embodiment of the method of the present invention. Reference is made to the description in the method embodiment of the present invention, and details are not described herein again.

A person of ordinary skill in the art may understand that all or part of the steps of the foregoing embodiments may be completed by a program to instruct related hardware, and the program may be stored in a computer readable storage medium, and the storage medium may include Not limited to: Read Only Memory (ROM, Read Only) Memory ), Random Access Memory (RAM), disk or optical disk. The foregoing description of the method, device, and routing device for forwarding a data packet provided by the embodiment of the present invention is only for helping to understand the method and core idea of the present invention. Meanwhile, for those skilled in the art, The present invention is not limited by the scope of the present invention.

Claims

Rights request

1. A method of forwarding data packets, characterized in that the method includes:

receive data packet;

Add a semantic header to the outer layer of the original header of the data packet, and the semantic header includes an identification bit used to identify the data packet as a data packet carrying a semantic mark;

If the data packet is the first data packet of the data flow, then add a record about the next hop or route of the first data packet in the data record table;

The first data packet is sent according to the next hop route of the first data packet.

2. The method according to claim 1, characterized in that, the method further includes:

If the data packet is a subsequent data packet of the data flow, a semantic header is added to the outer layer of the original header of the subsequent data packet;

Query the data record table to obtain the record of the next hop route of the first data packet;

The subsequent data packet is sent according to the record of the next hop route of the first data packet.

3. The method of claim 1, wherein the semantic header further includes a semantic mark, and the semantic mark includes one or any combination of security requirement level, user level, traffic type and flow identifier, so The flow identifier is used to identify the data flow to which the data packet belongs.

4. The method of claim 1, wherein the semantic packet header further includes a semantic tag and a flow identifier independent of the semantic tag, and the semantic tag includes security requirement level, user level and traffic type. One item or any combination, the flow identifier is used to identify the data flow to which the data packet belongs.

5. A method of forwarding data packets, characterized in that the method includes:

Receive a data packet, the data packet includes a semantic packet header, and the semantic packet header includes an identification bit used to identify the data packet as a data packet carrying a semantic tag;

Parse the semantic header of the data packet;

If the data packet is the first data packet of the data flow, add a record about the next hop route of the first data packet in the data record table;

6. The method according to claim 5, further comprising:

If the data packet is a subsequent data packet of the data flow, query the data record table for the The record of the next hop route of the first data packet;

7. The method of claim 5, wherein the semantic header further includes a semantic mark, and the semantic mark includes one or any combination of security requirement level, user level, traffic type and flow identifier, so The flow identifier is used to identify the data flow to which the data packet belongs.

8. The method of claim 5, wherein the semantic header further includes a semantic tag and a flow identifier independent of the semantic tag, and the semantic tag includes security requirement level, user level and traffic type. One item or any combination, the flow identifier is used to identify the data flow to which the data packet belongs.

9. The method according to claim 7 or 8, characterized in that, if the semantic mark includes the security requirement level, the method further includes:

According to the security requirement level, the data packet is forwarded to the corresponding security router in the domain.

10. The method according to any one of claims 5 to 9, characterized in that the method further includes: timing the aging time set in the data recording table;

If no subsequent data packet belonging to the same data flow is received when the aging time expires, the record of the next-hop route of the first data packet in the data record table is deleted.

11. A method of forwarding data packets, characterized in that the method includes:

receive data packet;

The data packet is forwarded according to the semantic header.

12. The method of claim 11, wherein the semantic header further includes a semantic mark, and the semantic mark includes one or any combination of security requirement level, user level, traffic type and flow identifier, so The flow identifier is used to identify the data flow to which the data packet belongs.

13. The method of claim 11, wherein the semantic packet header further includes a semantic tag and a flow identifier independent of the semantic tag, and the semantic tag includes security requirement level, user level and traffic type. One item or any combination, the flow identifier is used to identify the data flow to which the data packet belongs.

14. A device for forwarding data packets, characterized in that the device includes: The first receiving module is used to receive data packets;

A first semantic header generation module, configured to add a semantic header to the outer layer of the original header of the data packet, where the semantic header includes an identification bit used to identify the data packet as a data packet carrying a semantic mark;

The first record adding module is used to add a record about the next hop route of the first data packet in the data record table if the data packet is the first data packet of the data flow;

The first sending module is configured to send the first data packet according to the next hop route of the first data.

15. The device according to claim 14, characterized in that, the device further includes:

The first query module is used to query the data record table to obtain the record of the next hop route of the first data packet;

The first forwarding module is configured to send the subsequent data packet according to the record of the next hop route of the first data packet;

The first semantic header generation module is also configured to add a semantic header to the outer layer of the original header of the subsequent data packet if the data packet is a subsequent data packet of the data flow.

16. The device according to claim 14, wherein the semantic header further includes a semantic tag, and the semantic tag includes one or any combination of security requirement level, user level, traffic type and flow identifier, so The flow identifier is used to identify the data flow to which the data packet belongs.

17. The device according to claim 14, wherein the semantic packet header further includes a semantic tag and a flow identifier independent of the semantic tag, and the semantic tag includes security requirement level, user level and traffic type. One item or any combination, the flow identifier is used to identify the data flow to which the data packet belongs.

18. A device for forwarding data packets, characterized in that the device includes:

The second receiving module is configured to receive a data packet, the data packet includes a semantic packet header, and the semantic packet header includes an identification bit used to identify the data packet as a data packet carrying a semantic tag;

A header parsing module, used to parse the semantic header of the data packet;

The second record adding module is used to add a record about the next hop route of the first data packet in the data record table if the data packet is the first data packet of the data flow;

The second sending module is configured to send the first data packet according to the next hop route of the first data packet.

19. The device according to claim 18, characterized in that the device further includes: a second query module, configured to query the data record table for information about the data packet if the data packet is a subsequent data packet of the data stream. The record of the next hop route of the first data packet;

The second sending module is also configured to send the subsequent data packet according to the record of the next hop route of the first data packet.

20. The device according to claim 19, wherein the semantic header further includes a semantic tag, and the semantic tag includes one or any combination of security requirement level, user level, traffic type and flow identifier, so The flow identifier is used to identify the data flow to which the data packet belongs.

21. The device according to claim 19, wherein the semantic packet header further includes a semantic tag and a flow identifier independent of the semantic tag, and the semantic tag includes security requirement level, user level and traffic type. One item or any combination, the flow identifier is used to identify the data flow to which the data packet belongs.

22. The device according to claim 20 or 21, wherein if the semantic mark includes the security requirement level, the second sending module is further configured to send the data packet according to the security requirement level. Forwarded to the corresponding secure router in the domain.

23. The device according to any one of claims 18 to 22, characterized in that the device further includes:

A timing module, used to time the aging time set in the data recording table;

A record deletion module, configured to delete the record of the next hop route of the first data packet in the data record table if no subsequent data packet belonging to the same data flow is received when the aging time expires.

24. A device for forwarding data packets, characterized in that the device includes:

The third receiving module is used to receive data packets;

The second semantic header generation module is used to add a semantic header to the outer layer of the original header of the data packet. The semantic header includes an identification bit used to identify the data packet as a data packet carrying a semantic tag; third forwarding Module, configured to forward the data packet according to the semantic packet header.

25. The device of claim 24, wherein the semantic header further includes a semantic tag, and the semantic tag includes one of a security requirement level, a user level, a traffic type, and a flow identifier. or any combination, the flow identifier is used to identify the data flow to which the data packet belongs.

26. The device according to claim 24, wherein the semantic packet header further includes a semantic tag and a flow identifier independent of the semantic tag, and the semantic tag includes security requirement level, user level and traffic type. One item or any combination, the flow identifier is used to identify the data flow to which the data packet belongs.