CN113726635A

CN113726635A - Message processing method and device and electronic equipment

Info

Publication number: CN113726635A
Application number: CN202111006852.8A
Authority: CN
Inventors: 郑上闽
Original assignee: New H3C Big Data Technologies Co Ltd
Current assignee: New H3C Big Data Technologies Co Ltd
Priority date: 2021-08-30
Filing date: 2021-08-30
Publication date: 2021-11-30
Anticipated expiration: 2041-08-30
Also published as: CN113726635B

Abstract

The application discloses a message processing method and device and electronic equipment. In the application, the network device can assemble and encapsulate the data messages passing through the same tunnel, and a plurality of data messages are assembled together to be used as an assembled message to be transmitted by the tunnel, so that the scheme that each data message is separately transmitted after being encapsulated by the tunnel in the prior art is replaced, the total quantity of the forwarded data messages in the tunnel is reduced, and the network bandwidth utilization rate is also improved. By applying the scheme, the problem of low network bandwidth utilization efficiency of the small data message during tunnel transmission can be effectively solved.

Description

Message processing method and device and electronic equipment

Technical Field

The present application relates to a network tunneling technology, and in particular, to a method and an apparatus for processing a packet, and an electronic device.

Background

In current applications, common tunneling protocols include: generic routing encapsulates GRE, virtual extended LAN VxLAN, Internet security protocol IPSec, segment routing SRv6 based on IPv6, etc. Taking VxLAN as an example, for a data message transmitted by using a VxLAN tunnel, a tunnel header with a length of 50 bytes needs to be encapsulated before an original data message. Similarly, for tunnels under other tunneling protocols, when a data packet is transmitted through a tunnel, a tunnel header of a corresponding byte is encapsulated on the data packet.

In some cases, for small data messages transmitted in a network, such as data messages applied to voice, game control, etc., the payload length is relatively small, such as about 35 bytes. When these small data packets are tunneled, they encapsulate a certain byte of tunnel header as described above. The encapsulated tunnel header can greatly increase the length of the whole message and occupy more network bandwidth. For example, for a small data message with a payload length of 35 bytes, after encapsulating the VxLAN tunnel header, the message length is increased to 85 bytes, and the encapsulated VxLAN tunnel header occupies a larger amount of network bandwidth than the original small data message transmission. The same is true for the case where other tunneling protocols are used to encapsulate the tunnel header in the small data message.

Disclosure of Invention

The application provides a message processing method, a message processing device and electronic equipment, which are used for improving the utilization efficiency of network bandwidth during small data message transmission.

According to a first aspect of the embodiments of the present application, there is provided a packet processing method, where the method is applied to a network device, and the method includes:

when determining that the currently received data message is forwarded through a tunnel between the device and an opposite terminal device, storing the currently received data message into an output interface queue corresponding to the tunnel;

when a message aggregation and encapsulation event is detected, selecting N data messages meeting preset conditions from the output interface queue, wherein N is more than or equal to 2; the sum of the total message length of the N data messages and the length of the aggregation encapsulation header is less than or equal to the maximum transmission unit MTU required by the tunnel, where the length of the aggregation encapsulation header is the length of the aggregation encapsulation header required when the network device performs aggregation encapsulation on the N data messages, and the length of the aggregation encapsulation header at least includes: the length of a tunnel header encapsulated during transmission through the tunnel and the length of a separation mark used for separating the N data messages when the network equipment performs convergence encapsulation on the N data messages;

the N data messages are converged and encapsulated to obtain converged messages, and the converged messages are forwarded through the tunnel; the aggregation message carries an aggregation encapsulation head, and the aggregation encapsulation head at least comprises: the tunnel head and a separation mark used for separating the N data messages.

According to a second aspect of the embodiments of the present application, there is provided a packet processing method, which is applied to a network device, and includes:

receiving a convergence message sent by opposite-end equipment through a tunnel; the aggregation packet is obtained by the peer device through aggregation and encapsulation of N data packets, and the aggregation packet carries an aggregation encapsulation header, where the aggregation encapsulation header at least includes: the length of a tunnel header encapsulated during transmission through the tunnel and the length of a separation mark used for separating the N data messages when the opposite terminal equipment performs convergence encapsulation on the N data messages;

and de-encapsulating the aggregation message, obtaining the N data messages according to the separation marks obtained after de-encapsulation, and forwarding the N data messages respectively.

According to a third aspect of the embodiments of the present application, there is provided a packet processing apparatus, where the apparatus is applied to a network device, and the apparatus includes:

a message storage unit, configured to store a currently received data message into an egress interface queue corresponding to a tunnel when it is determined that the currently received data message is forwarded through the tunnel between the device and an opposite device;

the message selection unit is used for selecting N data messages meeting preset conditions from the output interface queue when a message aggregation packaging event is detected, wherein N is more than or equal to 2; the sum of the total message length of the N data messages and the length of the aggregation encapsulation header is less than or equal to the maximum transmission unit MTU required by the tunnel, the length of the aggregation encapsulation header is the length of the aggregation encapsulation header required when the N data messages are aggregated and encapsulated, and the length of the aggregation encapsulation header at least includes: the length of a tunnel header encapsulated during transmission through the tunnel and the length of a separation mark for separating the N data messages during the convergence encapsulation of the N data messages;

a message aggregation unit, configured to aggregate and encapsulate the N data messages to obtain an aggregated message, and forward the aggregated message through the tunnel; the aggregation message carries an aggregation encapsulation head, and the aggregation encapsulation head at least comprises: the tunnel head and a separation mark used for separating the N data messages.

According to a fourth aspect of the embodiments of the present application, there is provided a packet processing apparatus, where the apparatus is applied to a network device, and the apparatus includes:

a message receiving unit, configured to receive, through a tunnel, a convergence message sent by an opposite-end device; the aggregation packet is obtained by the peer device through aggregation and encapsulation of N data packets, and the aggregation packet carries an aggregation encapsulation header, where the aggregation encapsulation header at least includes: the length of a tunnel header encapsulated during tunnel transmission and the length of a separation mark used for separating the N messages when the opposite terminal device performs convergence encapsulation on the N messages are determined;

and the message forwarding unit is used for decapsulating the converged message, obtaining the N data messages according to the decapsulated separation identifiers, and forwarding the N data messages respectively.

According to a fifth aspect of embodiments of the present application, there is provided an electronic device, including a memory, a processor, and a program stored on the memory and executable on the processor, wherein the processor implements the following method when executing the program: any one of the above message processing methods.

It can be seen from the above technical solutions that, in this embodiment, the network device aggregates and encapsulates the data packets passing through the same tunnel, and multiple data packets are aggregated together to serve as one aggregated packet to be transmitted by the tunnel, so that a scheme in the prior art that each data packet is separately sent after being individually tunnel-encapsulated is replaced, the total number of forwarded data packets in the tunnel is reduced, and the network bandwidth utilization rate is also improved.

Drawings

FIG. 1 is a diagram illustrating a network tunneling architecture;

FIG. 2 is a diagram of a packet encapsulation format;

FIG. 3 is a flow chart of a first method provided by an embodiment of the present application;

FIG. 4 is a flowchart illustrating specific steps provided in an embodiment of the present application;

FIG. 5 is a flowchart illustrating another specific process provided in an embodiment of the present application;

FIG. 6 is a diagram of another packet encapsulation format;

FIG. 7 is a flow chart of a second method provided by an embodiment of the present application;

FIG. 8 is a block diagram of a first apparatus provided by an embodiment of the present application;

fig. 9 is a block diagram of a second apparatus according to an embodiment of the present application.

Detailed Description

In order to make the technical solutions in the embodiments of the present application better understood and make the above objects, features and advantages of the embodiments of the present application more comprehensible, the technical solutions in the embodiments of the present application are described in further detail below with reference to the accompanying drawings.

Fig. 1 illustrates one of the cases in which a data message is transmitted through a tunnel.

In fig. 1, a network device 101 is connected to a private network 104, a network device 102 is connected to a private network 105, and a tunnel 103 is established between the network device 101 and the network device 102, so that data packet communication between devices in the private network 104 and the private network 105 can be realized. Some of the major current tunneling protocols include: GRE, VxLAN, IPSec, SRv6, etc., and the present embodiment is not limited to the specific tunneling protocol used.

For example, for a VxLAN tunnel, a VxLAN tunnel header needs to be added before an original data message to serve as tunnel encapsulation, for an SRv6 tunnel, encapsulated message information needs to be added before an original data message load to serve as tunnel encapsulation, and the specific content or position of the tunnel encapsulation in the original data message is not limited in this embodiment.

Under the network architecture shown in fig. 1, fig. 2 illustrates, by way of example, one of the tunnel encapsulations, where the tunnel encapsulation used corresponds to the VxLAN tunnel in fig. 1, which is a VxLAN encapsulation.

In the embodiment, the HostA1 and the HostB1 in the private network 104 respectively send data messages to the HostA2 and the HostB2 in the private network 105 through the Vxlan tunnel 103 using the network device 101 and the network device 102 as tunnel endpoints.

In the two data packets shown in fig. 2, the white part is the original packet content, the first data packet is a data packet sent by the HostA1 to the HostA2, and the source IP address is IPA1 and the destination IP address is IPA 2; the second data message is a data message sent by the HostB1 to the HostB2, and the source IP address of the second data message is IPB1 and the destination IP address of the second data message is IPB 2. While the shaded portion in the figure is the added tunnel encapsulation, EP1, i.e. tunnel endpoint 1, and EP1 address is the address of network device 101; EP2, namely, tunnel endpoint 2, and EP2 address is an address of the network device 102, and for convenience of description, the first data packet is referred to as a packet a and the second data packet is referred to as a packet B in fig. 2.

In the network, there are a large number of application scenarios for small data message transmission, such as voice and game control messages. The existing statistics show that the length of the effective load of most network game data messages is about 35 bytes, and for the small data messages, the tunnel encapsulation increased during the tunnel encapsulation can greatly increase the length of the whole data message. For example, after VxLAN tunnel encapsulation is performed on a small data packet with 35 bytes of payload, the length of the data packet is increased to 85 bytes and increased to 143%, the payload only accounts for 41%, and similar situations exist after other tunnel protocol encapsulation, which causes a problem of network bandwidth waste. Moreover, when the network device processes the data packets, the number of data packets processed per second is basically fixed, and the processing performance for a large number of small data packets cannot reach the line speed.

Therefore, in the existing tunnel technology, under the condition of a large number of small data messages, the utilization efficiency of network bandwidth is low, and the processing and forwarding efficiency of equipment is low.

As can be seen from fig. 2, for data packets that need to be transmitted in the same direction through the same tunnel, even if the source IP address and the destination IP address are different, the tunnel encapsulation contents added thereto may be the same, so that a large number of tunnel encapsulation bytes with the same contents are transmitted in the same tunnel, resulting in unnecessary waste of network bandwidth.

In view of the above, the present application provides a message processing method as shown in fig. 3, and the following describes in detail the implementation process shown in fig. 3 with reference to specific embodiments.

Referring to fig. 3, fig. 3 is a flowchart of a first method provided in an embodiment of the present application. The flow is applied to a network device. As shown in fig. 3, the process may include the following steps:

step 301: and when determining that the currently received data message is forwarded through the tunnel between the device and the opposite-end device, storing the currently received data message into an output interface queue corresponding to the tunnel.

In this embodiment, the network device receives data packets of different source IPs and destination IPs, and the related IP address information is carried in the data packets. The network device searches a forwarding table according to the IP address information for the currently received data message, and when determining that the currently received data message needs to be sent to the network device serving as the endpoint on the other side of the tunnel through a certain tunnel with the device as one of the endpoints, the network device divides the currently received data message into an output interface queue corresponding to the corresponding tunnel to wait for subsequent operation.

Taking the data packet shown in fig. 2 as an example, after receiving the packet a, the network device 101 searches a forwarding table through the information of the source IPA1 and the destination IPA2 carried in the packet a, and when determining that the packet a needs to be sent to the network device 102 through the tunnel 103, divides the packet a into an egress interface queue corresponding to the tunnel 103, and waits for subsequent operations; after receiving the packet B, the network device 101 also divides the packet B into an egress interface queue corresponding to the tunnel 103 and waits in the same queue as the packet a based on the same flow.

And for other data messages which do not need to be sent through the tunnel 103, if the data messages are to be sent to the opposite terminal device through other tunnels which take the network device as a tunnel endpoint, the data messages are divided into other outgoing interface queues corresponding to the corresponding tunnels. If the device is only used as a tunnel intermediate device, or a data packet sent through a tunnel is not needed, the processing may be performed according to a corresponding rule of the network device, which is not limited in this embodiment.

Preferably, in this embodiment, the same tunnel may correspond to multiple egress interface queues, and different queues are provided with corresponding priorities. And the network equipment divides the data message into an output interface queue which corresponds to the corresponding tunnel and is matched with the priority according to the IP address information and the priority information in the received data message. In this embodiment, the priority information may be a packet Traffic Class (Traffic Class), a priority for indicating a Traffic flow to which the data packet belongs, or a Type of Service (ToS), and the like, which is not limited in this embodiment.

Step 302: and when a message aggregation and encapsulation event is detected, selecting N data messages meeting preset conditions from the output interface queue, wherein N is more than or equal to 2.

In this embodiment, when the network device detects a packet aggregation and encapsulation event, it selects N corresponding data packets according to a preset selection condition, and waits for subsequent aggregation and encapsulation, where N is greater than or equal to 2 in this embodiment. Preferably, for different aggregate encapsulation events, different message selection conditions may also be set for the corresponding events. As for a specific detection mode of the aggregation and encapsulation event and a selection range of N data messages corresponding to different events, detailed description will be given below in conjunction with the pictures and the specific embodiments, which are not repeated herein.

The selected N data messages are subsequently aggregated and encapsulated, where aggregation and encapsulation refer to adding a separation identifier before each data message to serve as separation, aggregating the N data messages to serve as one message, and adding a tunnel encapsulation to the aggregated message to replace an original encapsulation mode that tunnel encapsulations need to be added to the N data messages respectively, where N is greater than or equal to 2 in this embodiment.

And when N subsequent data messages for aggregation and encapsulation are selected, the total length of the message after the selected N data messages are aggregated is required to be less than or equal to the maximum transmission unit MTU required by the tunnel. The total length of the aggregated messages includes the total length of the N data messages and the length of the aggregation encapsulation head. In this embodiment, the converging encapsulation head length at least includes: the length of the tunnel header encapsulated during transmission through the tunnel and the length of the separation mark for separating the N data messages during the convergent encapsulation of the N data messages.

The length and content of the separation identifier may be preset, and may only include the necessary identifier bytes for the receiving device of the subsequent aggregation packet to split and obtain N data packets, and preferably, may also include data packet length information, aggregation time information, aggregation packet number and sequence number information, and the like.

In this embodiment, the selection manner of the message aggregation and encapsulation event and the N data messages under different aggregation and encapsulation events is not limited. Some embodiments regarding the packet aggregation encapsulation event and the selection of N data packets are exemplarily given below, and it should be noted that these embodiments are for more clearly illustrating the scheme of the embodiment, and are not intended to limit the present application.

For convenience of subsequent description, first, an abbreviation of a condition related to a message aggregation encapsulation event is defined:

recording the total message length of the data message in the egress interface queue and the sum of the lengths of the convergence encapsulation heads required for convergence encapsulation of the existing data message in the egress interface queue, which is greater than the MTU, as a condition 1, wherein the lengths of the convergence encapsulation heads at least comprise: the length of the tunnel head and the length of the separation mark;

recording that "the length of a single data message is greater than a set length threshold" as a condition 2, where the length threshold is obtained by presetting, and may be set by referring to information such as a data message aggregation rate, a data message forwarding rate, an average length of forwarded data messages, and the like of the device, and this embodiment does not limit this;

let "the timer time of the timer expires" be condition 3.

Still further, it is also possible to:

let "set length threshold value less than or equal to 0" be condition 4, where the length threshold value is the length threshold value in condition 2;

note that "the timing time of the set timer is less than or equal to 0" is the condition 5, where the timing time is the timing time in the condition 3.

Preferably, to further improve the effect of this embodiment, different processing modes may be adopted according to whether the egress is congested when the data packet is forwarded. For example, if there is no congestion during forwarding of the data packet, a timer may be started, and wait for a certain time, for example, 50us, and the timing time of the timer may be set according to an actual situation, for example, according to parameters such as the priority of a service flow to which the data packet belongs, the average transmission delay of the data packet, and the average time consumption for aggregation and encapsulation of the data packet; if congestion occurs during data message forwarding and the messages are accumulated in the exit cache, the timer is not set any more, and the data messages meeting the length condition are selected as N data messages. For example, whether the data packet currently received and stored in the egress interface queue corresponding to the tunnel is the first packet in the egress interface queue may be determined to be required to start the timer.

When the data message currently received and stored in the corresponding output interface queue is the first message of the queue, the timer is started, under the condition, the equipment continuously transfers the data message meeting the conditions in the received data message into the queue, and detects whether a convergence packaging event occurs in the queue according to the existing and newly transferred data messages in the queue:

recording that the conditions of satisfying the condition 3 and not satisfying the conditions 1, 4 and 5 are one of the conditions of the type 1 convergent package event, when the type 1 convergent package event is determined to be detected, selecting all data messages in the output interface queue as N data messages, and further closing a timer;

recording that 'the condition 1 is met, the conditions 3, 4 and 5 are not met' as one of the conditions of the type 2 convergence encapsulation event, when the type 2 convergence encapsulation event is detected, selecting all data messages except the designated message in the output interface queue as N data messages, and further closing a timer, wherein the designated message refers to the data message finally stored in the output interface queue, and after the message is added into the output interface queue, the sum of the total length of the messages in the queue and the length of the convergence encapsulation head exceeds the MTU length.

It should be noted that "type 1 aggregate package event" and "type 2 aggregate package event" are not limited to specific events corresponding to specific conditions, but are generic terms of a type of aggregate package event that is the same for subsequent processing operations, such as:

"satisfy condition 2, do not satisfy condition 1, 3, 4, 5", "satisfy condition 3, do not satisfy condition 1, 2, 4, 5", "satisfy condition 2, 3, do not satisfy condition 1, 4, 5", etc., also belong to some possible situations of class 1 aggregate package event, after detecting the above-mentioned situation, can all data messages in the queue of the outgoing interface, choose N data messages, further, can also close the timer;

"condition 1 is satisfied, condition 4, 5 is not satisfied", "condition 1 is satisfied, condition 2, 4, 5 is not satisfied", "condition 1, 3 is satisfied, condition 4, 5 is not satisfied", "condition 1, 2 is satisfied, condition 4, 5 is not satisfied", "condition 1, 3 is satisfied, condition 2, 4, 5 is not satisfied", "condition 1, 2 is satisfied, condition 3, 4, 5 is not satisfied", "condition 1, 2, 3 is satisfied, condition 4, 5 is not satisfied", etc., also belong to some possible situations of class 2 aggregation encapsulation event, after detecting the above situations, all data messages except the designated message in the output interface queue can be selected as N data messages, further, the timer can also be closed;

it should be noted that the above listed cases are only an exemplary description of possible cases in this embodiment, and in practical applications, the content of the judgment condition, the judgment sequence, some judgment conditions may be removed, or whether all the conditions are completely detected may be adjusted according to specific cases, which is not limited in this embodiment. For example, in one embodiment, the determination sequence for the above conditions 1 to 5 is: if it is known that the conditions 4, 5, 1, 2, and 3 are satisfied, and the conditions 2, 4, and 5 are not satisfied, in this embodiment, it may be determined that the type 2 aggregate package event is detected directly after determining that the conditions 4 and 5 are not satisfied and the condition 1 is satisfied, or it may be determined that the type 2 aggregate package event is detected after continuing to determine the conditions 2 and 3, which is not limited in this embodiment.

As a preferred scheme, under the congestion-free condition, if it is detected that "condition 4 is satisfied", "condition 5 is satisfied", and "condition 4, 5" is satisfied in a certain egress interface queue, the data packets in the queue are no longer aggregated and encapsulated, and naturally, no corresponding N data packets are selected from the queue, and all the data packets in the queue need to be directly transmitted through tunnel encapsulation. It should be noted that, in this embodiment, the preset length threshold and the timer timing time may be set for different queues respectively, so that after the length threshold or the timer timing time set for a part of queues according to actual requirements is less than or equal to 0, the technical solution of this embodiment is not affected and corresponding effects are obtained when other queues continue to adopt the technical solution of this embodiment.

In this embodiment, if the data packet currently received and stored in the corresponding egress interface queue is a non-first packet of the queue, it is not necessary to start a timer for the device, and whether the corresponding condition of the packet aggregation and encapsulation event is satisfied can be determined according to the existing data packet in the queue and the currently received data packet. In this case, the respective determination conditions are appropriately adjusted:

recording a condition 1' that the sum of the message length of the currently received data message, the message total length of the data message in the outgoing interface queue and the length of a convergence encapsulation head required when the currently received data message and the existing data message in the outgoing interface queue are converged and encapsulated is greater than an MTU;

recording a condition 2' that the message length of the currently received data message is greater than a set length threshold value;

condition 3 does not change, it should be noted that, when the currently received data packet is a non-first packet of the queue, it is only not necessary to start a timer for the currently received data packet, and the currently started timer and related conditions are not affected, and the timer may be started or may not be started, which is not limited in this embodiment.

In this case, the device may detect whether a convergence encapsulation event occurs in the queue according to the existing data packet and the currently received data packet in the queue:

recording that the condition 2 is met, and the conditions 1 ', 4 and 5 are not met as one of the conditions of the 1 ' type convergence encapsulation event, when the 1 ' type convergence encapsulation event is detected, selecting all data messages in the output interface queue as N data messages, and further, if the timer is started, closing the timer;

recording that 'the condition 1 is met', the conditions 3, 4 and 5 are not met as one of the conditions of the 2 'type aggregation and encapsulation event, when the 2' type aggregation and encapsulation event is detected, selecting all data messages except the currently received data message in the output interface queue as N data messages, and further, if the timer is started, closing the timer;

for other possible condition combinations, the condition combinations may also be used as aggregation and encapsulation events, and the corresponding relationship is the same as that in the case of "when the data message currently received by the device and stored in the corresponding egress interface queue is the first message of the queue", the condition 1 or 2 is replaced by the condition 1 ' or 2 ', and the aggregation and encapsulation events of the 1 st or 2 nd type are replaced by the aggregation and encapsulation events of the 1 st or 2 ' type, which is not described herein again.

Further, in this embodiment, if a congestion condition occurs during forwarding of the data packet and the data packet is accumulated in the egress cache, the timer may not be set, and the data packet meeting the length condition may be selected as N data packets. That is, in case of congestion, whether condition 3 or condition 5 is satisfied is no longer taken as a basis for detecting the aggregate encapsulation event. Meanwhile, after the convergence encapsulation event is detected, the timer does not need to be closed, because the timer is not started.

In this case, the basis and the corresponding processing manner for the device to detect whether the aggregate encapsulation event occurs in the queue may refer to the foregoing, for example:

for the conditions of "meeting the condition 2, not meeting the conditions 1 and 5", "meeting the condition 2 ', not meeting the conditions 1 ' and 5", and the like, the subsequent processing mode of detecting the type of the convergent package event can also be used as the convergent package event, and the subsequent processing mode of detecting the type of the convergent package event corresponds to the detection of the type 1 or 1 ' convergent package event;

for the cases such as "the condition 1 is satisfied, the condition 2, 5 is not satisfied", "the conditions 1, 2 are satisfied, the condition 5 is not satisfied", "the condition 1 ' is satisfied", the conditions 2 ', 5 are not satisfied "," the conditions 1 ', 2 ', 5 are not satisfied ", and the like, the cases may also be regarded as the aggregate package event, and the subsequent processing mode for detecting the type of the aggregate package event corresponds to the detection of the type 2 or 2 ' aggregate package event.

Corresponding to the foregoing preferred solution, it should be noted that, in the case of congestion and without starting a timer, since the determination condition related to the timer is not involved, even if "condition 5 is satisfied" is detected, the aggregation encapsulation and N data message selection of the message in the queue are not affected. And only when the condition 4 is met, all the data messages in the queue are directly sent through tunnel encapsulation.

For ease of understanding, the process of detecting the packet aggregation encapsulation event and selecting N data packets in step 302 is further described in detail below with reference to more specific embodiments.

Referring to fig. 4, fig. 4 is a schematic flow chart of step 302 provided in the embodiment of the present application.

In the situation corresponding to fig. 4, the device has started the timer, and in this situation, the device continues to transfer the data packet that meets the condition in the received data packet to the queue, and detects whether a convergence encapsulation event occurs in the queue according to the existing and newly transferred data packets in the queue.

Assuming that a new data message is transferred into the queue, at this time, the sum of the message total length of the data message in the output interface queue and the length of a convergence encapsulation head required when converging and encapsulating the existing data message in the output interface queue is less than or equal to MTU; the length of a single message is greater than a set length threshold; expiration of a timing time of the timer; setting a length threshold value to be greater than 0; the timer is set to have a timing time greater than 0 ″, that is, the foregoing conditions 2, 3 are satisfied, and the conditions 1, 4, 5 are not satisfied. Under the assumption condition, the determination and execution are performed according to the step sequence of 400-.

It should be noted that the determination process shown in fig. 4 is only one possible case of this embodiment, and in practical applications, the content of the determination conditions, the determination sequence, some determination conditions may be removed, or whether all the conditions are completely detected may be selected according to specific situations, which is not limited in this embodiment. For example, in fig. 4, the order of the judgment between the conditions 4 and 5 and the order of the judgment between the conditions 2 and 3 may be adjusted, or the 5 conditions may be completely and sequentially judged, and then the subsequent processing mode may be selected according to the judgment result.

Assuming another situation, a new message is transferred into the queue, and at this time, the sum of the total message length of the data message in the outgoing interface queue and the length of a convergence encapsulation head required when the existing data message in the outgoing interface queue is subjected to convergence encapsulation is greater than MTU; setting a length threshold value to be greater than 0; if the timer is set to have a timing time greater than 0 ", that is, the condition 1 is satisfied, and the conditions 4 and 5 are not satisfied, the conditions 2 and 3 may be determined continuously, or may not be determined. In this case, the determination and execution can be performed according to the steps sequence of 400-. The specific message has already been described in detail and is not described again.

For ease of understanding, the process of detecting the packet aggregation encapsulation event and selecting N data packets in step 302 is described in further detail below with reference to another more specific embodiment.

Referring to fig. 5, fig. 5 is another schematic flow chart of step 302 provided in the embodiment of the present application.

In the case corresponding to fig. 5, the queue is in a congestion state, it is not necessary to start a timer, and the data packet currently received and stored in the corresponding egress interface queue by the device is a non-first packet of the queue, and at this time, it may be determined whether the corresponding condition of the packet aggregation and encapsulation event is satisfied according to the existing packet in the queue and the currently received data packet.

At this time, the judgment condition in the process is adjusted accordingly, the condition 1 is adjusted to the condition 1 ', the condition 2 is adjusted to the condition 2', and the conditions 3 and 5 are not referred to, and the specific adjustment content is described in detail above and will not be described again.

Assuming that the currently received data message is transferred to the queue, at this time, "the message length of the currently received data message, the total message length of the message in the outgoing interface queue, and the sum of the lengths of the aggregation encapsulation heads required for aggregation encapsulation of the currently received data message and the existing data message in the outgoing interface queue are less than or equal to MTU"; the message length of the currently received data message is greater than a set length threshold; the length threshold is set to be greater than 0 ″, i.e., the aforementioned condition 2 'is satisfied, and the conditions 1', 4 are not satisfied. Under the assumption condition, the determination and execution are performed according to the step sequence of 500-.

Assuming another situation, the currently received data message is transferred to the queue, and at this time, "the sum of the message length of the currently received data message, the total message length of the data message in the outgoing interface queue, and the length of a convergence encapsulation header required when the currently received data message and the existing data message in the outgoing interface queue are subjected to convergence encapsulation" is greater than the MTU; the message length of the currently received data message is less than or equal to a set length threshold; the length threshold is set to be greater than 0 ″, i.e., the aforementioned condition 1 'is satisfied, and the conditions 2', 4 are not satisfied. Under the assumption condition, the determination and execution are performed according to the step sequence of 500-.

It should be noted that, when the data message currently received and stored in the corresponding egress interface queue is the first message of the queue, it may be said that the queue is in a congestion-free state, and a timer may be started; however, when the data packet currently received and stored in the corresponding egress interface queue is a non-first packet of the queue, it cannot be proved that the queue is necessarily in a congestion state, and at this time, the timer may or may not be started. The examples given in fig. 4 and 5 are only two exemplary of the many possible scenarios of the present embodiment, and many other scenarios are possible.

For example, the queue is not congested and the data packet currently received and stored in the corresponding egress interface queue by the device is a non-first packet of the queue. At this time, different from the flow shown in fig. 5, the condition 3 and the condition 5 need to be considered, and only the aggregation and encapsulation events of the conditions 1, 2 and the types 1 and 2 in fig. 4 need to be adjusted to the aggregation and encapsulation events of the conditions 1 ', 2', and the types 1 'and 2', respectively, so the processing can be directly referred to the case of fig. 4 and is not separately described.

So far, several possible operation flows of step 302 are exemplarily described with reference to the flowchart illustrations of the specific embodiments of fig. 4 and fig. 5.

Step 303: and aggregating and packaging the N data messages to obtain an aggregated message, and forwarding the aggregated message through a tunnel.

By detecting the aggregate encapsulation event, N data packets satisfying the preset conditions have been selected. For the selected N data messages, the aggregation and encapsulation is to add a separation mark in front of each data message for separation, aggregate the N data messages as one message, and add a tunnel encapsulation to the aggregated message to replace the original encapsulation mode of respectively adding tunnel encapsulations to the N data messages, so that the aggregated message can be transmitted through the tunnel. Because N data messages in the same queue are sorted into the corresponding queue corresponding to the target tunnel by the equipment according to the IP address information table lookup, the converged messages obtained by convergence and encapsulation can be transmitted to the opposite end equipment of the tunnel through the tunnel without any doubt.

Under the network architecture shown in fig. 1, fig. 6 illustrates, by way of example, one of the cases of convergence encapsulation. Fig. 6 shows a converged message, which is divided into two lines for easy and clear display, and the dotted line represents the actual connection position of the upper and lower lines of the message content.

The messages in fig. 6 are the message a and the message B in fig. 2, and are aggregated messages obtained by VxLAN tunnel encapsulation after aggregation by adding a separation identifier, and for convenience of description, the messages are subsequently referred to as aggregated messages AB.

Assuming that in step 302, a corresponding aggregation encapsulation event is detected, and the message a and the message B are selected as the N data messages, where N is 2; in step 303, the message a and the message B are subjected to aggregation and encapsulation to obtain an aggregation message AB, and the aggregation message AB is sent from the network device 101 to the network device 102 through the VxLAN tunnel 103.

The specific operation of converging and encapsulating the message A and the message B to obtain a converged message AB is as follows:

adding a separation mark 1 in front of the message A, adding a separation mark 2 in front of the message B, converging the message A and the message B added with the separation marks to form a message, performing tunnel encapsulation, and additionally installing corresponding information such as a VxLAN (virtual private LAN) header and the like to obtain a converged message AB.

The separation identifier 1 and the separation identifier 2 may be the same content or different contents, and are determined according to the content actually contained in the separation identifier, for example, when the separation identifier only contains the necessary identifier bytes for the receiving device of the subsequent aggregated packet to split and obtain N packets, the contents of the separation identifier 1 and the separation identifier 2 may be the same; when the separation identifier includes content such as data packet length information, aggregation time information, aggregation sequence number information, and the like, the content of the separation identifier 1 is different from that of the separation identifier 2, which is not limited in this embodiment.

In this embodiment, for the case of aggregating and encapsulating more than 2 data packets, for example, the scheme of aggregating and encapsulating the packet a, the packet B, and the packet C to obtain the aggregated packet ABC may be performed with reference to the operation of obtaining the aggregated packet AB. The embodiment does not limit the number of the actual messages participating in the convergence encapsulation, the number of the data messages participating in the convergence encapsulation is greater than or equal to 2, and the total length after convergence does not exceed the MTU value of the tunnel.

So far, the description of the flow shown in fig. 3 is completed.

Further, when the network device processes the packet, the number of data packets processed per second is substantially fixed, and the processing performance of a large number of small data packets cannot reach the linear speed, so the scheme provided by this embodiment further plays a role in reducing the number of times that the network device checks the table and processes the packet header by reducing the total number of data packets forwarded in the tunnel, thereby achieving the effect of improving the forwarding efficiency.

The following describes in detail an implementation process of receiving the aggregation packet and performing corresponding subsequent operations by the tunnel peer device shown in fig. 7, with reference to a specific embodiment.

Referring to fig. 7, fig. 7 is a flowchart of a second method provided in the embodiment of the present application, where the flowchart is applied to a network device. The network device may be a tunnel peer network device connected to the network device corresponding to the first method flowchart through a tunnel. As shown in fig. 7, the process may include the following steps:

step 701, receiving a convergence message sent by an opposite terminal device through a tunnel.

The aggregation packet is obtained by aggregating and encapsulating the N data packets by the peer device, and carries an aggregation encapsulation header, where the aggregation encapsulation header at least includes: the separation identifier is used for separating the N data messages when the N data messages are subjected to aggregation encapsulation by the opposite terminal equipment. The peer device refers to the network device corresponding to the first method flowchart provided in fig. 3, and the tunnel and the aggregation packet have been described in detail in steps 301 to 303, and are not described again.

In this embodiment, the network device may receive data packets of different source IPs and destination IPs, and also receive a tunnel packet sent by the device at the opposite end of the tunnel through the tunnel. After receiving the tunnel message, the device can determine whether the message is a convergence message containing N data messages or not through the separation identifier in the message.

Still taking the aggregation message AB shown in fig. 6 as an example, in step 303, the message a and the message B are aggregated and encapsulated to obtain the aggregation message AB, and the aggregation message AB is sent from the network device 101 to the network device 102 through the VxLAN tunnel 103. The network device 102 may receive a large number of messages including the aggregation message AB, where the network device 102 may determine that the message is the aggregation message through the separation identifier in the aggregation message AB.

And 702, decapsulating the aggregation message, obtaining N data messages according to the separation identifiers obtained after decapsulation, and forwarding the N data messages respectively.

Decapsulating the aggregated message, that is, removing a tunnel encapsulation part in the aggregated message, wherein the specific content depends on an adopted tunnel protocol, for example, a VxLAN tunnel message header before the message is removed for a tunnel adopting VxLAN protocol communication; for the tunnel adopting the SRv6 protocol for communication, the embodiment does not limit the added encapsulated message information before removing the message load.

Still taking the aggregation message AB shown in fig. 6 as an example, the MAC header, EP1 address, EP2 address, and VxLAN header parts before the partition identifier 1 in the message are removed, and a decapsulated message including the partition identifier 1, the message a, the partition identifier 2, and the message B is obtained.

After the decapsulation operation is performed, the N data messages determined in steps 302 to 303 are obtained according to the separation identifiers in the data messages, and the N data messages are respectively forwarded.

For example, for a packet after tunnel decapsulation including the separation identifier 1, the packet a, the separation identifier 2, and the packet B, according to the separation identifier 1 and the separation identifier 2, two data packets, i.e., the packet a and the packet B, are obtained by parsing.

Further, in this embodiment, each time a data packet is obtained by parsing, data packet forwarding is performed once, and the data packet forwarding is repeated N times; the N data messages may also be forwarded one by one after all N data messages are obtained through disassembly, and the order and specific implementation manner of message disassembly and forwarding are not limited in this embodiment.

For example, for obtaining the message a and the message B from the aggregation message AB, the message a may be obtained by parsing, the message a is forwarded to the HostA2 by the network device 102 through table lookup according to the destination IP address IPA2 of the message a, and then the message B is obtained by parsing, and the message B is forwarded to the HostA2 by the network device 102 through table lookup according to the destination IP address IPB2 of the message B; or directly disassembling to obtain the message A and the message B, and then sequentially looking up the table for forwarding the message A and the message B.

This completes the description of the flow shown in fig. 7.

It can be seen from the above technical solutions that, in this embodiment, the network device may receive the aggregation message sent from the tunnel peer device through the tunnel, disassemble the aggregation message, and obtain multiple data messages before aggregation and encapsulation from one aggregation message. By gathering a plurality of data messages together to be used as a gathered message to be transmitted by the tunnel, the scheme that each message is separately transmitted after being independently subjected to tunnel encapsulation in the prior art is replaced, the total quantity of the data messages forwarded in the tunnel is reduced, and the network bandwidth utilization rate is also improved.

The methods provided herein are described above. The following describes the apparatus provided in the present application:

referring to fig. 8, fig. 8 is a block diagram of a first apparatus provided in the embodiment of the present application. The device is applied to network equipment. As shown in fig. 8, the apparatus may include the following units:

801, a message storing unit, configured to store the currently received data message into an egress interface queue corresponding to a tunnel when it is determined that the currently received data message is forwarded through the tunnel between the device and the opposite-end device.

And 802, a message selecting unit, configured to select N data messages meeting a preset condition from the egress interface queue when a message aggregation encapsulation event is detected, where N is greater than or equal to 2.

And 803, the message aggregation unit is configured to aggregate and encapsulate the N data messages to obtain an aggregated message, and forward the aggregated message through the tunnel.

Optionally, the message storage unit further starts a timer when the currently received data message is the first message in the egress interface queue, where the timing time of the timer is determined by the network device according to the priority of the service flow to which the data message belongs;

based on this, the message selection unit can detect the message aggregation encapsulation event by the following modes:

when the expiration of the timing time of the timer is detected, determining that a message aggregation encapsulation event is detected;

selecting N data messages meeting preset conditions from an output interface queue, specifically comprising:

selecting all data messages in an output interface queue as N data messages;

alternatively, the first and second electrodes may be,

the message selection unit detects a message aggregation and encapsulation event in the following way:

when the sum of the total message length of the data messages in the outgoing interface queue and the length of a convergence encapsulation head required when the existing data messages in the outgoing interface queue are converged and encapsulated is larger than an MTU (maximum transmission unit) is detected, determining that a message convergence encapsulation event is detected;

selecting all data messages except the designated message in the output interface queue as N data messages; the designated message is the last data message stored in the egress interface queue.

Optionally, the message selecting unit further closes the timer when detecting the message aggregation encapsulation event.

Optionally, when the currently received data packet is a non-first packet in the egress interface queue, the packet selecting unit may detect the packet aggregation and encapsulation event in the following manner:

if the sum of the message length of the currently received data message, the message total length of the existing data message in the outgoing interface queue and the length of a convergence encapsulation head required when the currently received data message and the existing data message in the outgoing interface queue are subjected to convergence encapsulation is larger than MTU, determining that a message convergence encapsulation event is detected;

and selecting all data messages except the currently received data message in the output interface queue as N data messages.

if the message length of the currently received data message is greater than the set length threshold, determining that a message convergence encapsulation event is detected when the sum of the message length of the currently received data message, the total message length of the existing data message in the outgoing interface queue and the convergence encapsulation head length required when the currently received data message and the existing data message in the outgoing interface queue are converged and encapsulated is less than or equal to MTU;

and selecting all data messages in the output interface queue as N data messages.

Referring to fig. 9, fig. 9 is a block diagram of a second apparatus provided in the embodiment of the present application. The device is applied to the tunnel opposite-end network equipment which is connected with the network equipment corresponding to the first device block diagram through the tunnel. As shown in fig. 9, the apparatus may include the following units:

901, a message receiving unit, configured to receive, through a tunnel, an aggregation message sent by an opposite end device.

And a message forwarding unit 902, configured to perform tunnel decapsulation on the aggregation message, obtain N data messages according to the separation identifiers obtained after decapsulation, and forward the N data messages respectively.

The implementation process of the functions and actions of each unit in the above device is specifically described in the implementation process of the corresponding step in the above method, and is not described herein again.

Thus, the description of the device structure provided in the present application is completed.

Correspondingly, the embodiment also provides an electronic device for message processing, which comprises a memory, a processor and a program stored in the memory and capable of running on the processor.

When the processor executes the program, the following method is realized: such as any one of the message processing methods in the first method flow or the second method flow of this embodiment.

The above description is only exemplary of the present application and should not be taken as limiting the present application, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the scope of protection of the present application.

Claims

1. A message processing method is applied to network equipment and comprises the following steps:

2. The method of claim 1, wherein when the currently received data packet is the first packet in the egress interface queue, the method further comprises:

starting a timer, wherein the timing time of the timer is determined by network equipment according to the priority of the service flow to which the data message belongs;

detecting a message aggregation encapsulation event by the following method:

selecting N data messages meeting preset conditions from the output interface queue, specifically comprising:

selecting all data messages in the output interface queue as the N data messages;

alternatively, the first and second electrodes may be,

detecting a message aggregation encapsulation event by the following method:

when the sum of the total message length of the data messages in the outgoing interface queue and the length of a convergence encapsulation head required when the existing data messages in the outgoing interface queue are converged and encapsulated is larger than the MTU is detected, determining that a message convergence encapsulation event is detected;

selecting all data messages in the output interface queue except the designated message as the N data messages; the designated message is the last data message stored in the egress interface queue.

3. The method of claim 2, wherein upon detecting a message aggregation encapsulation event, the method further comprises: the timer is turned off.

4. The method according to claim 1, wherein when the currently received data packet is a non-first packet in the egress interface queue, a packet aggregation encapsulation event is detected by:

if the sum of the message length of the currently received data message, the message total length of the existing data message in the outgoing interface queue and the required aggregation encapsulation head length when the currently received data message and the existing data message in the outgoing interface queue are subjected to aggregation encapsulation is greater than the MTU, determining that a message aggregation encapsulation event is detected;

and selecting all data messages in the output interface queue except the currently received data message as the N data messages.

5. The method according to claim 1, wherein when the currently received data packet is a non-first packet in the egress interface queue, a packet aggregation encapsulation event is detected by:

if the message length of the currently received data message is greater than a set length threshold, determining that a message convergence packaging event is detected when the sum of the message length of the currently received data message, the total message length of the existing data message in the outgoing interface queue and the convergence packaging head length required when the currently received data message and the existing data message in the outgoing interface queue are subjected to convergence packaging is less than or equal to the MTU;

and selecting all data messages in the output interface queue as the N data messages.

6. A message processing method is applied to network equipment and comprises the following steps:

7. A message processing device, which is applied to a network device, includes:

8. The apparatus of claim 7, wherein when the currently received data packet is the first packet in the egress interface queue, the packet storing unit further comprises:

and starting a timer, wherein the timing time of the timer is determined by the network equipment according to the priority of the service flow to which the data message belongs.

9. A message processing device, which is applied to a network device, includes:

10. An electronic device comprising a memory, a processor, and a program stored on the memory and executable on the processor, wherein the processor implements the following method when executing the program: the message processing method according to any of claims 1 to 6.