WO2013152586A1

WO2013152586A1 - Data packet retransmission method, data packet receiving method and device

Info

Publication number: WO2013152586A1
Application number: PCT/CN2012/083544
Authority: WO
Inventors: 杨荣玉; 王海彬
Original assignee: 华为技术有限公司
Priority date: 2012-04-10
Filing date: 2012-10-26
Publication date: 2013-10-17
Also published as: CN103368703A; CN103368703B

Abstract

The present invention provides a data packet retransmission method, a data packet receiving method, and a data packet receiving device. The retransmission method comprises: receiving a retransmission request comprising a packet reception total sequence number corresponding to a data packet of which retransmission is requested; according to mapping between the packet reception total sequence number corresponding to the data packet of which retransmission is requested and a packet transmission sequence number of each message type and mapping between a locally stored packet transmission total sequence number and a packet transmission sequence number of each message type, acquiring a message type of the data packet of which retransmission is requested and a packet transmission sequence number in the message type; and according to the acquired message type of the data packet of which retransmission is requested and the packet transmission sequence number in the message type, retransmitting to a receiving end the data packet of which retransmission is requested and subsequently sent data packets that have the same message type as the data packet of which retransmission is requested. The technical solution of the present invention can retransmit data packets of the same type only, thereby reducing the data traffic for retransmission and lowering resource waste caused by a retransmission mechanism.

Description

TECHNICAL FIELD The present invention relates to a link retransmission technique, and in particular, to a data packet retransmission method, a data packet reception method, and an apparatus. Background technique

Quick Path Interconnect (QPI) is the central processing unit (Central)

Processing Unit, CPU) and CPU, CPU and input and output hub (Input Output Hub,

An important high-speed channel for data exchange between the IOH and even the CPU and remote memory.

Existing QPI implementations include QPI's Upper Layer, Link Layer, and Physical Layer. QPI has two packet paths, one for the data transmission path and one for the data reception path. For the transmission path: the local protocol layer sends the data packet to the link layer; the link layer sends these packets to the physical layer and also stores it in the retransmission buffer; the local physical layer sends these packets to the remote end. Physical layer. For the receiving path: The local physical layer receives the data packets sent by the remote physical layer, and the local physical layer sends the packets to the link layer, and the link layer decodes the data packets and determines whether there is any error, and the data is correct. The packet is sent to the protocol layer, and the decoding information is sent to the retransmission control module and the system control module respectively. The local link layer will generate an acknowledgment (ack) after receiving a number of fixed number of error-free packets and inform the other party (ie, the remote end), and the other party clears the data pointed by the tail pointer (tail) in the retransmission buffer. . If there is an error, the local link layer will encapsulate the serial number of the error packet (pkt_num) in the retry request (retry_request) and send it to the other party. At the same time, the local will discard the subsequently received packet until it receives Resend the response (retry_response).

During the above retransmission process, the sender will retransmit the first error packet and other packets that have been sent after the first error packet, but in fact some packets do not need to be retransmitted. Therefore, the existing QPI The retransmission mechanism will result in waste of resources. Summary of the invention

The invention provides a data packet retransmission method, a data packet receiving method and a device, which are used for reducing Waste of resources caused by data retransmission.

An aspect of the present invention provides a data packet retransmission method, including:

Receiving a retransmission request, where the retransmission request is sent by the sending end, where the retransmission request includes a total sequence number of the packet corresponding to the data packet requesting retransmission;

Obtaining, according to a mapping relationship between a total number of received packets corresponding to the data packet retransmitted by the request and a total sequence number of the locally stored packet and a packet sequence number of each message type, acquiring the data packet to which the request retransmission belongs The message type and the sequence number of the packet to be retransmitted in the message type to which the request belongs, and the total sequence number of the packet to be sent is a sequence number obtained by counting the data packets of all message types sent;

And sending, according to the message type to which the data packet retransmitted by the request belongs, and the packet sequence number of the data packet requested by the retransmission in the message type to which the request belongs, to the receiving end, the data packet requesting retransmission and The data packet sent after the data packet requested to be retransmitted and the request retransmitted belongs to a data packet of the same message type.

An aspect of the present invention provides a data packet sending apparatus, including:

a first receiving module, configured to receive a retransmission request, where the retransmission request is sent by a sending end, where the retransmission request includes a total sequence number of the packet corresponding to the data packet requesting retransmission;

a first processing module, configured to acquire the request according to a mapping relationship between a total sequence number of the packet corresponding to the retransmitted data packet and a total sequence number of the locally stored packet and a packet sequence number of each message type. The message type to which the retransmitted data packet belongs and the sequence number of the packet to be retransmitted in the message type to which the request is retransmitted, and the total sequence number of the sent packet is obtained by counting the data packets of all the message types sent. serial number;

a first sending module, configured to send the request to the receiving end according to a message type to which the data packet retransmitted according to the request belongs and a sending sequence number of the data packet requested to be retransmitted in a message type to which the request belongs The retransmitted data packet and the data packet transmitted after the requesting retransmitted data packet and the data packet retransmitted by the request belong to the same message type.

Another aspect of the present invention provides a data packet receiving method, including:

Receiving a first data packet sent by the sending end, and modifying a total sequence number of the received packet to obtain a total sequence number of the received packet corresponding to the first data packet; the total sequence number of the receiving packet is a data packet of all message types received Counting the obtained serial number; the first data packet includes a message type to which the first data packet belongs and a delivery sequence number of the first data packet in a message type to which the first data packet belongs; Obtaining, according to the message type to which the first data packet belongs, a last received sequence number of the message type to which the first data packet belongs, where the first data packet belongs to The last received sequence number of the message type is the packet sequence number of the last received message packet of the same message type as the first packet in the message type to which the first packet belongs.

Determining whether a last received sequence number of the message type to which the first data packet belongs and a delivery sequence number in the message type to which the first data packet belongs are consecutive;

When the result of the judgment is that the last received sequence number of the message type to which the first data packet belongs and the delivery sequence number of the first data packet in the message type to which the first data packet belongs are consecutive, the first data packet belongs to The last received sequence number of the message type is updated to the delivery sequence number of the first data packet in the message type to which the first data packet belongs.

Another aspect of the present invention provides a data packet receiving apparatus, including:

a second receiving module, configured to receive a first data packet sent by the sending end, where the first data packet includes a message type to which the first data packet belongs and an outgoing packet of the first data packet in a message type to which the first data packet belongs serial number;

a second processing module, configured to: after the second receiving module receives the first data packet, modify a total sequence number of the received packet to obtain a total sequence number of the packet corresponding to the first data packet, where When the error occurs in the first data packet, the last received packet sequence number of the message type to which the first data packet belongs is obtained according to the message type to which the first data packet belongs, and the message to which the first data packet belongs is determined. Whether the last received sequence number of the type and the initial sequence number of the first data packet in the message type to which the first data packet belongs are consecutive, and when the judgment result is continuous, the last packet of the message type to which the first data packet belongs is The serial number is updated to the sequence number of the packet in which the first data packet belongs in the message type to which the first data packet belongs; the total sequence number of the received packet is a sequence number obtained by counting the data packets of all received message types; The last received sequence number of the message type to which the data packet belongs is the last received data packet belonging to the same message type as the first data packet before the first data packet. SEQ ID NO contract itself belongs message types.

A data packet retransmission method and a data packet transmitting apparatus provided by an aspect of the present invention, after receiving a retransmission request sent by a receiving end, according to a packet retransmission request packet corresponding to a packet sequence number and a locally stored total packet transmission sequence The mapping relationship between the number and the packet sequence number of each message type, obtain the message type to which the data packet requesting retransmission belongs, and the data packet requesting retransmission belongs to The sequence number of the packet sent in the message type, and then the data packet requesting retransmission and the data packet sent after the data packet requested to be retransmitted belong to the same message type as the data packet retransmitted by the request, and the obtained request is heavy. The transmitted data packet and the subsequent data packet belonging to the same message type as the data packet requesting retransmission are resent to the receiving end, so that only the same type of data packet is retransmitted, and other types of data packets do not need to be retransmitted. When there is no retransmission, the amount of data retransmitted is reduced compared with the prior art scheme in which the data packet requested to be retransmitted and all the data packets sent after the data packet requested to be retransmitted are resent to the receiving end. Reduce the waste of resources caused by the retransmission mechanism.

A data packet receiving method and apparatus provided by another aspect of the present invention parses a data packet after receiving a data packet, and if the data packet can be successfully solved, according to the message type of the data packet in the data packet and the data packet to which the data packet belongs The sequence number of the outgoing packet in the message type determines whether to discard the data packet, and if the data packet is not discarded, the last received sequence number of the message type to which the data packet belongs is updated, so as to continue to receive subsequent data packets, and implement the data packet. Reception. The data packet receiving method and device provided by the present invention cooperate with the data packet retransmission method and device provided by the present invention, and the transmitting end performs data packet retransmission according to the message type, reduces the amount of retransmitted data, and reduces resources caused by retransmission. Consumption provides conditions. DRAWINGS

The drawings used in the embodiments or the description of the prior art are briefly described. It is obvious that the drawings in the following description are some embodiments of the present invention, and are not creative to those skilled in the art. Other drawings can also be obtained from these drawings on the premise of labor.

FIG. 1 is a flowchart of a method for retransmitting a data packet according to an embodiment of the present invention;

2 is a flowchart of a data packet retransmission method according to another embodiment of the present invention; FIG. 3 is a flowchart of a data packet receiving method according to an embodiment of the present invention;

4 is a schematic diagram of a data packet retransmission process according to an embodiment of the present invention;

FIG. 5 is a schematic structural diagram of a data packet sending apparatus according to an embodiment of the present invention; FIG. 6B is a schematic structural diagram of a data packet sending apparatus according to another embodiment of the present invention; FIG. 6B is a QPI according to another embodiment of the present invention; Schematic diagram of the link layer of the protocol; FIG. 7 is a schematic structural diagram of a data packet receiving apparatus according to an embodiment of the present invention; FIG. 8 is a schematic structural diagram of a data packet receiving apparatus according to another embodiment of the present invention. The technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. The embodiments are a part of the embodiments of the invention, and not all of the embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

FIG. 1 is a flowchart of a method for retransmitting a data packet according to an embodiment of the present invention. As shown in FIG. 1, the data packet retransmission method in this embodiment includes:

Step 101: Receive a retransmission request, where the retransmission request is sent by a sending end, where the retransmission request includes a total sequence number of the packet corresponding to the data packet requesting retransmission.

The execution body of this embodiment is a transmitting end. The sender may be any device in the device or device with a retransmission mechanism. For example, the sender may be a server, a routing device, or the like, or may be a QPI in a Central Processing Unit (CPU) or a QPI in the interconnect chip. Wait. Similarly, the receiving end may also be any device in the device or device with a retransmission mechanism, for example, the receiving end may also be a server, a routing device, etc., or may be a QPI in the CPU or a QPI in the interconnect chip.

The total sequence number of the received packet is a sequence number obtained by the receiving end to count the data packets of all received message types. The total sequence number of the packet corresponding to the data packet requesting retransmission is the total sequence number of the packet received by the receiving end after receiving the data packet retransmitted by the receiving end. For example, suppose the receiving end receives the total sequence number of the packet before receiving the retransmitted data packet, and after receiving the data packet that is retransmitted, the total sequence number of the received packet will increase by 1 to 11, and the request is heavy. The total sequence number of the received packet corresponding to the transmitted data packet is 11.

During the data transmission process, the sender sends a packet to the receiver, and counts the packets of all message types sent, so that a total sequence number of the packet is obtained. The total sequence number of the packet sent corresponding to each data packet records the transmission sequence number of each transmitted data packet. For example, the total sequence number of the first packet sent by the first transmitted data packet is 1, and the total sequence number of the second packet sent packet is 2, and the packet sent by the Nth transmitted packet corresponds to The total serial number is N and the like. Here, the data packet to be transmitted refers to the data packet transmitted for the first time does not include the retransmitted data packet, and the total sequence number of the packet corresponding to the retransmitted data packet is the first time of the data packet. The total serial number of the corresponding receipt when sending.

For the receiving end, it will receive the data packet sent by the sender, and will parse the received data packet according to the protocol. If the data packet can be successfully parsed, the packet is considered to have no error. If the data packet is not successfully parsed. , then the packet is considered to be in error. If the packet is in error, the receiver sends a retransmission request to the sender. For the receiving end, the packets of all received message types are also counted, so that a total number of received packets is obtained. The total sequence number of the received packet corresponding to each data packet records the receiving sequence number of each received data packet. For example, the total received sequence number corresponding to the first received data packet is 1, and the total received serial number corresponding to the second received data packet is 2, and the received packet corresponding to the Nth received data packet is received. The total serial number is N and the like. Herein, the received data packet mentioned here means that the data packet received for the first time does not include the retransmitted data packet, and the total sequence number of the received packet corresponding to the retransmitted data packet is that the data packet is first. The total received serial number of the corresponding receipt when it is received.

For the same data packet, the total sequence number of the packet corresponding to the data packet counted by the sender is the same as the total sequence number of the packet corresponding to the data packet counted by the receiver. Based on this, when the receiving end sends a retransmission request to the transmitting end, the receiving end may add the total receiving sequence number corresponding to the data packet requesting retransmission to the retransmission request, and based on the sending end, it may be known which data is requested to be retransmitted. package.

Step 102: Acquire, according to a mapping relationship between a total sequence number of the packet corresponding to the retransmitted data packet and a total sequence number of the locally stored packet and a total sequence number of the packet sent by each message type, obtain a data packet to which the request retransmission belongs. The message type and the sequence number of the packet that is requested to be retransmitted in the message type to which it belongs.

The total packet sequence number is a sequence number obtained by the sender to count the data packets of all message types sent. The total sequence number of the outgoing packet corresponding to each data packet is the total sequence number of the outgoing packet counted after the data packet is sent.

Among them, for each packet, there is a message type to which it belongs. For different protocols, there are different message types, and the message type allows modification and definition based on the actual application. For example, for Transmission Control Protocol / Internet Connection Protocol (Transmission Control)

According to the Protocol/Internet Protocol (TCP/IP) protocol, two types of messages can be defined according to the type of the protocol, which is Internet Protocol version 4 (IPv4). Type and Internet Protocol version 6 (IPv6) type. The type of the IPv4 data packet belongs to the IPv4 type, and the type of the IPv6 data packet belongs to the IPv6 type. For example, the QPI protocol mainly includes six types of message types: a listening message (SNOOP, SNP), a source message (HOME, HOM), a request and response message, and a data response message (Data Response, DRS). , Non Data Response (NDR), Non-Coherence Bypass (NCB), and Non-Coherence Standard (NCS).

In this embodiment, in addition to counting the data packets of all message types to obtain the total sequence number of the packet, the sender also separately counts the data packets of different message types to obtain the packet sequence number of each message type. Moreover, the sender also maps the total packet sequence number and the packet sequence number of each message type, and stores the mapping relationship between them locally. The mapping relationship between the total sequence number of the sent packet and the sequence number of the packet sent by each message type mainly includes: a total sequence number of the packet to be sent corresponding to each transmitted data packet, a message type to which each transmitted data packet belongs, and each The correspondence between the transmitted packet and the sequence number of the packet in the associated message type.

Based on this, after receiving the retransmission request sent by the receiving end, the transmitting end parses the retransmission request, and obtains the total sequence number of the packet corresponding to the data packet requesting retransmission from the retransmission request. After the sender receives the total sequence number of the packet corresponding to the data packet requesting retransmission from the retransmission request sent by the receiving end, the total sequence number of the packet corresponding to the data packet retransmitted according to the request and the total number of locally stored packets may be The mapping relationship between the sequence number and the packet sequence number of each message type obtains the message type to which the data packet requesting retransmission belongs and the packet sequence number in the message type to which the retransmission data packet belongs.

Optionally, the sending end may store the mapping relationship between the total packet sequence number and the packet sequence number of each message type in a mapping relationship table, but is not limited thereto. For ease of understanding, Table 1 gives a mapping table showing the three message types as an example.

Table 1

Num ) num ) num )

1 0 1 0 pktl

2 1 1 0 pktO

3 1 2 0 pktl

4 1 3 0 pktl

5 1 3 1 pkt2 Based on the mapping relationship table, when the sending end obtains the total number of the received packet corresponding to the data packet requesting retransmission from the retransmission request sent by the receiving end, the data packet corresponding to the retransmission request may be received. The total sequence number of the packet matches the total sequence number of the packet in the mapping relationship table, and the total sequence number of the packet with the same total sequence number of the packet corresponding to the packet to be retransmitted is referred to as the total number of the packet in the matching, and will be matched. The message type corresponding to the total sequence number of the outgoing packet and the sequence number of the packet in the message type respectively serve as the message type to which the data packet requesting retransmission belongs and the packet sequence number in the message type to which the data packet requested to be retransmitted belongs.

Table 1 is taken as an example for description. Suppose the total sequence number of the packet corresponding to the data packet requesting retransmission is 2, and the total sequence number of the packet in the matching in Table 1 is 2, and the message type corresponding to the total sequence number 2 of the packet is 2 For pktO, the corresponding packet type of the message type is 1, and the message type of the data packet requesting retransmission belongs to pktO, and the sequence number of the packet requesting retransmission in the message type pktO is 1, that is, requesting retransmission The packet is the first packet sent in the message type pktO.

Step 103: Send a data packet requesting retransmission and a data requesting retransmission to the receiving end according to the message type to which the data packet requested to be retransmitted belongs and the data packet sequence number of the data packet requested to be retransmitted in the message type to which the request belongs. Packets sent after the packet that are requested to be retransmitted belong to the same message type.

Specifically, when the sender acquires the message type to which the data packet requesting retransmission belongs and the packet sequence number of the data packet requesting retransmission in the message type to which the request belongs, the request may be obtained from the retransmission buffer according to the information. The retransmitted data packet and the data packet sent after the data packet requested to be retransmitted belong to the same message type as the data packet retransmitted by the request, and then the retransmitted data packet of the obtained request and the data requested in the retransmission A packet that is sent after the packet and belongs to the same message type as the packet requesting retransmission is resent to the receiving end.

Optionally, the sending end of the embodiment may be configured to cache data packets of different message types by setting multiple retransmission buffers. And, the sender will record each retransmission buffer and message. The correspondence between types. Based on this, after obtaining the message type to which the data packet requesting retransmission belongs, the transmitting end may determine, according to the message type to which the data packet requested to be retransmitted, the retransmission buffer corresponding to the data packet requesting retransmission, that is, determining The retransmission buffer in which the packet for which the request is retransmitted is cached. Then, the sending end obtains the data packet requesting retransmission from the retransmission buffer corresponding to the data packet that is requested to be retransmitted according to the packet sequence number in the message type to which the transmitting packet is retransmitted according to the obtained request, and The data packet sent after the data packet requested to be retransmitted belongs to the same message type as the data packet requesting retransmission, that is, the data packet sequence requesting the retransmission in the message type to which the request belongs is the starting position, in the request The retransmission buffer in which the retransmitted data packet is located acquires the data packet requesting retransmission and the data packet stored later. Such a message type corresponds to a retransmission buffer, and the correspondence relationship is simple, which is convenient for the sender to manage, and the data packet is highly efficient from the retransmission buffer.

Optionally, the transmitting end of the embodiment may further use a retransmission buffer, and separately manage storage locations of data packets of different message types in the retransmission buffer through different linked lists. Based on this, after obtaining the message type to which the data packet requesting retransmission belongs, the sender may first determine the linked list corresponding to the data packet requesting retransmission; and then send the packet sequence according to the message type to which the request is retransmitted according to the message type to which the request belongs. The number is searched in the determined linked list, and the data packet requesting retransmission and the data packet sent after requesting the retransmitted data packet belonging to the same message type as the data packet requesting retransmission are respectively in the retransmission buffer. a storage location, and then respectively obtaining a data packet requesting retransmission according to the obtained storage location into the retransmission buffer and a data packet corresponding to the data packet requested to be retransmitted and sent after the data packet requested to be retransmitted belongs to the same message type . The manner in which all message types correspond to the same retransmission buffer and the storage locations of data packets of different message types in the retransmission buffer are managed by different linked lists, the number of retransmission buffers required is small. , help to save resources on the sender.

Wherein, when the transmitting end retransmits the data packet that has been sent before resending (that is, retransmitting the data packet), the total number of the retransmitted data packet is stopped using the total sequence number of the outgoing packet, that is, the total sequence number of the sent packet does not follow the data packet. The retransmission is incremented.

Herein, in order to identify that the subsequently transmitted data packet is a retransmitted data packet, before sending the retransmitted data packet to the receiving end, the transmitting end sends a retransmission response to the receiving end to notify the receiving end of the data packet sent later. A packet for retransmission. For the receiving end, after receiving the retransmission response sent by the sending end, it receives the retransmitted data packet sent by the sending end. Specifically, the sender The retransmission response is sent to the receiving end first, and then the data packet requesting retransmission is sent to the receiving end and the data packet sent after the data packet requesting retransmission belongs to the same message type as the data packet requesting retransmission.

The sending end sends a retransmission response to the receiving end, and after receiving the retransmission request, sending the data packet requesting retransmission to the receiving end and the data sent after requesting the retransmitted data packet and requesting retransmission. A packet can be used before it belongs to the same message type.

Optionally, after receiving the retransmission request, the sending end may obtain the message type to which the data packet requesting retransmission belongs and the data packet requesting retransmission before sending the sequence number of the packet in the message type to which it belongs, and send the packet to the receiving end. Retransmit the response.

Optionally, the sender may obtain the message type to which the data packet to which the request is retransmitted belongs and the type of the message to which the retransmitted data packet belongs in the message type to which the request belongs, according to the message type to which the retransmitted data packet belongs. Before determining the retransmission buffer corresponding to the data packet requesting retransmission, the retransmission response is sent to the receiving end.

Optionally, the sender may obtain the data packet requesting retransmission from the retransmission buffer corresponding to the data packet requested to be retransmitted, and the data packet sent after requesting the retransmitted data packet is the same as the data packet requesting retransmission. After the data packet of the message type, and after transmitting the data packet requesting retransmission and the data packet sent after the data packet requesting retransmission belongs to the same message type, the retransmission response is sent to the receiving end. .

In this embodiment, after receiving the retransmission request sent by the receiving end, the sending end receives the total sequence number of the packet corresponding to the data packet retransmitted by the receiving end, and the total sequence number of the locally stored packet and the type of each message type. Corresponding relationship between the sequence numbers of the packets, finding the message type to which the data packet requesting retransmission belongs and the packet sequence number in the message type to which the data packet requesting retransmission belongs, and then obtaining the request weight from the retransmission buffer according to the information The transmitted data packet and the data packet sent after the data packet requested to be retransmitted belong to the same message type, and then the obtained data packets are resent to the receiving end. The data packet retransmission method of this embodiment implements only retransmission of the same type of data packet in the process of data packet retransmission, and other types of data packets sent after requesting the retransmitted data packet do not need to be retransmitted. Without retransmission, the amount of retransmitted data is reduced, and the amount of data retransmitted is reduced compared with the solution in the prior art that the data packet requested to be retransmitted and all data packets sent after the data packet requested to be retransmitted are resent to the receiving end. Waste of resources caused by the retransmission mechanism. FIG. 2 is a flowchart of a method for retransmitting a data packet according to another embodiment of the present invention. This embodiment is implemented based on the embodiment shown in FIG. 1. As shown in FIG. 2, the method of this embodiment includes before step 103:

Step 103a: Determine whether the message type to which the data packet requesting retransmission belongs is the same as the message type to which the data packet requested by the previous retransmission request is retransmitted; if the result of the determination is no, that is, the step is not the same, step 103 is performed; Go to step 104.

Step 104: Discard the retransmission request.

In the present embodiment, a special case is considered mainly, that is, the case where the receiving end continuously receives two or more packets having errors belonging to the same message type. For the receiving end, if the packet has an error, the packet type to which the packet belongs cannot be known from the packet, and it is impossible to distinguish whether the packet belongs to the same message type as other packets. Since it is impossible to distinguish which message type the packet in which the error belongs, the receiving end sends a retransmission request to the transmitting end as long as it receives the packet in which the error occurred. Thus, for the above special case, the sender continuously receives two retransmission requests, and the data packet retransmitted by the sender to the receiver according to the latter retransmission request is retransmitted to the receiver according to the previous retransmission request. A subset of the data packet, that is, some data packets are repeatedly sent; and for the receiving end, if the data packet is received after receiving the data packet, the data packet is discarded, which shows that A special situation can also result in wasted resources.

To this end, the transmitting end of the embodiment receives the retransmission request and according to the total sequence number of the packet corresponding to the data packet in which the retransmission is requested, and the total sequence number of the packet stored locally and the packet sequence number of each message type. After obtaining the message type to which the data packet requested to be retransmitted belongs, the mapping type of the data packet to which the request is retransmitted may be compared with the message type to which the data packet retransmitted by the previous retransmission request request belongs, and two Are they the same? When the judgment result is different, the special case mentioned above may be excluded, and step 103 may be performed, that is, the message type to which the data packet retransmitted according to the request belongs and the data packet requested to be retransmitted are in the message type to which the message belongs. Sending a sequence number, resending the data packet requesting retransmission to the receiving end and the data packet sent after the data packet requesting retransmission belongs to the same message type as the data packet requesting retransmission. When the judgment result is the same, it indicates that the retransmission request belongs to the same message type as the data packet retransmitted by the previous retransmission request, and belongs to the special case mentioned above, because the sender has already described the message according to the previous retransmission request. The last retransmission request requesting the retransmitted data packet and after the data packet The transmitted data packet that belongs to the same message type as the data packet is resent to the receiving end. Therefore, in order to reduce resource waste, the transmitting end may discard the retransmission request without performing retransmission processing.

In this embodiment, the sender compares the message type to which the data packet retransmitted by the current request belongs with the message type to which the data packet retransmitted by the previous retransmission request request belongs, and determines whether the two previous retransmission requests are heavy. A packet with the same error of the same message type can be discarded. If the result of the determination is yes, the current retransmission request can be discarded without retransmission processing, which is beneficial to reduce resource waste caused by data retransmission.

In the above embodiments, the transmitting end sends the first data packet to the receiving end before receiving the retransmission request sent by the receiving end. The first data packet is a data packet sent by the sending end to the receiving end for the first time. The purpose of using the first data packet here is to distinguish it from the retransmitted data packet or the data packet requesting retransmission. In the foregoing embodiments, the sending, by the sending end, the first data packet to the receiving end may be: the sending end sends the first data packet to the receiving end, buffers the first data packet, and according to the message that the first data packet belongs to. The type updates the mapping relationship between the total sequence number of the outgoing packet and the outgoing sequence number of each message type. The first data packet sent by the sending end includes the message type to which the data packet belongs and the sending sequence number of the first data packet in the message type to which the first data packet belongs. Optionally, the message type to which the first data packet belongs may be implemented by an identifier or a flag bit in the first data packet.

The mapping relationship between the total number of the updated packet and the sequence number of the packet of each message type is mainly added to the total number of the packet to be sent in the mapping relationship, and the sequence number of the packet in the message type to which the first packet belongs. And a correspondence between the message types to which the first data packet belongs. On the basis of Table 1, after a new packet with the message type pktO is sent, the new mapping table will be as shown in Table 2.

Table 2

3 1 2 0 pktl

4 1 3 0 pktl

5 1 3 1 pkt2

6 2 3 1 pktO As can be seen from the above, the total sequence number for the outgoing packet is continuously counted, and the serial number of the packet for each message type is also continuously counted.

If the sending end uses multiple retransmission buffers to respectively buffer data packets of different message types, after the transmitting end sends the first data packet, the process of buffering the first data packet may be: according to the first data packet The message type caches the first data packet into a retransmission buffer corresponding to the first data packet.

If the sender uses a retransmission buffer to simultaneously buffer data packets of all message types and manage the storage locations of data packets of different message types through different linked lists, after the sender sends the first data packet, the first data packet is sent. The process of performing caching may be: buffering the first data packet into the retransmission buffer, and recording the storage location of the first data packet in the retransmission buffer to the message according to the message type to which the first data packet belongs. The type corresponds to the linked list.

Optionally, the sender can use a counter to count the packet sequence number and the total packet sequence number of each message type. When the counter has reached the maximum value, it can be re-counted from 0, that is, it can be cycled.

In the foregoing implementation manner, the transmitting end distinguishes the data packet according to the type of the message when the data packet is sent, and records the mapping relationship between the total sequence number of the sent packet and the packet sequence number of each message type, so as to receive the heavy After the request is transmitted, only the data packet requesting retransmission and the data packet sent after the requesting retransmission of the data packet requesting retransmission belong to the same message type are not retransmitted to the data packet of other message types. The foundation is beneficial to reduce the amount of data retransmitted, reduce the waste of resources caused by the retransmission mechanism, and improve the bandwidth utilization of the system.

FIG. 3 is a flowchart of a data packet receiving method according to an embodiment of the present invention. As shown in FIG. 3, the data packet receiving method in this embodiment includes:

Step 301: Receive a first data packet sent by the sending end, and modify a total sequence number of the received packet to obtain a total sequence number of the received packet corresponding to the first data packet.

In this embodiment, the first data packet is also a data packet that is sent by the sending end for the first time, and is used to distinguish the data packet requesting retransmission or the data packet to be retransmitted, and is not limited to a specific data packet. and also That is to say, the first data packet here is not necessarily the same data packet as the first data packet in the previous embodiment.

The execution body of this embodiment is a receiving end. The receiving end can be any device with a retransmission mechanism or a module in the device. For example, the receiving end can be a server, a routing device, etc., and can also be a QPI in the CPU or a QPI in the interconnect chip. Correspondingly, the sending end may also be any device in the device or device with a retransmission mechanism, for example, the sending end may be a server, a routing device, etc., or may be a QPI in the CPU or a QPI in the interconnect chip.

The total sequence number of the received packet is a sequence number obtained by counting the data packets of all received message types; the total sequence number of the received packet corresponding to the first data packet is the total sequence of the received packets after receiving the first data packet. number. For example, if the total sequence number of the received packet is 5 before the first data packet is received, the total sequence number of the received packet becomes 6 after receiving the first data packet, and the total sequence number of the received packet corresponding to the first data packet is 6. The total sequence number of the received packet changes with the receipt of the data packet, and the total sequence number of the received packet corresponding to a certain data packet is fixed.

The received first data packet includes a message type to which the data packet belongs and a transmission sequence number of the first data packet in a message type to which the first data packet belongs. In this embodiment, in addition to counting the data packets of all message types, the transmitting end also counts the data packets of each message type according to the message type to which the data packet belongs. The message sequence number of the message type is the sequence number obtained by the sender to count the packets belonging to the message type. The packet sequence number in the message type to which the packet belongs is the packet sequence number of the message type to which the packet belongs after the packet is sent. For example, suppose that before the data packet is sent, the packet sequence number of the message type to which the data packet belongs is 2, and after the data packet is sent, the packet sequence number of the message type to which the data packet belongs is 3, and the data packet belongs to itself. The delivery sequence number in the message type is 3. That is, the packet sequence number of the first packet in the message type to which it belongs is the packet sequence number of the message type to which the first packet counted after the first packet is transmitted.

In this embodiment, the receiving end receives the first data packet sent by the sending end, and uses the total receiving sequence number to count the received first data packet. That is, each time a first data packet is received, the receiving end modifies the total sequence number of the received packet, and more specifically increases the total sequence number of the received packet by one. In this embodiment, the receiving end may acquire the total number of the received packet corresponding to the received first data packet while modifying the total sequence number of the received packet. Herein, the data packet that the receiving end uses to count the total sequence number of the received packet refers to the first received data packet and does not include the retransmitted data packet, and the total sequence number of the received packet corresponding to the retransmitted data packet is The total sequence number of the corresponding packet received when the packet is received for the first time.

Step 302: When it is determined that the received first data packet does not have an error, obtain a last received sequence number of the message type to which the first data packet belongs according to the message type to which the first data packet belongs.

In this embodiment, after receiving the first data packet, the receiving end parses the first data packet. If the first packet can be successfully parsed, the first packet has no error; if the first packet cannot be successfully parsed, the first packet has an error.

When it is determined that the first data packet does not have an error, the receiving end may obtain, from the first data packet, the message type to which the first data packet belongs and the delivery sequence number of the first data packet in the message type to which the first data packet belongs. Then, the receiving end obtains the last receiving sequence number of the message type to which the first data packet belongs according to the last received packet sequence number of each message type recorded locally according to the message type to which the first data packet belongs. The last received sequence number of the message type to which the data packet belongs is the packet sequence number of the last received message packet of the same message type as the first data packet in the message type to which the first data packet belongs.

In this embodiment, the receiving end may separately buffer the received data packets according to the message type, or may uniformly cache the data packets of all message types. However, in this embodiment, for each message type, the receiving end records the sequence number of the last received data packet in the message type to which it belongs, so as to determine whether the data packet of each message type is pressed. Order reception.

Step 303: Determine whether the last received sequence number of the message type to which the first data packet belongs and the delivery sequence number of the first data packet in the message type to which the first data packet belongs are consecutive; when the determination result is yes, that is, continuous, step 304 is performed. When the judgment result is no, that is, discontinuous, step 305 is performed.

Specifically, the receiving end compares the received first data packet with the last received packet sequence number of the message type to which the first data packet belongs, and can determine whether the two are consecutive.

Step 304: Update the last received sequence number of the message type to which the first data packet belongs to the delivery sequence number of the first data packet in the message type to which the first data packet belongs.

When the result of the judgment is that the last received sequence number of the message type to which the first data packet belongs and the initial sequence number of the first data packet in the message type to which the first data packet belongs, the first data packet is described. If there is no error in the packet of the message type of the genus, the first packet will be the last received packet, so the receiving end updates the last packet sequence number of the message type to which the first packet belongs to the first packet. The sequence number of the packet in the message type to which it belongs, in order to continue to receive packets of the same message type.

Step 305: Record the sequence number of the first packet in the message type to which the packet belongs, as the retransmission sequence number threshold, and discard the first packet.

When the result of the judgment is that the last received sequence number of the message type to which the first data packet belongs and the initial sequence number of the first data packet in the message type to which the first data packet belongs are discontinuous, it indicates that the first data packet belongs to the first data packet before The packet of the same message type has an error, and the receiving end has sent a retransmission request to the transmitting end. The first data packet belongs to the same message type that is sent after the data packet requested by the receiving end to be retransmitted and sent by the requesting retransmission. Therefore, the transmitting end retransmits the first data packet, so the receiving end discards the first data packet after determining the discontinuous result. At the same time, the receiving end records the sequence number of the first packet in the message type to which it belongs, as the retransmission sequence number threshold. The retransmission sequence number threshold is used for distinguishing, among the data packets sent by the receiving end, which packets are retransmitted.

In this embodiment, the receiving end parses the data packet after receiving the data packet, and if the data packet can be successfully solved, according to the message type of the data packet in the data packet and the packet sending sequence in the message type to which the data packet belongs. The number is determined whether to discard the data packet, and if the data packet is not discarded, the last received sequence number of the message type to which the data packet belongs is updated, so as to continue to receive subsequent data packets, and if the data packet is discarded, the corresponding data packet is recorded. The packet sequence number of the packet in the associated message type, so as to distinguish the retransmitted data packet from the data packet sent by the sender, and realize the reception of the data packet. The data packet receiving method provided in this embodiment is matched with the method for sending a data packet by the sending end provided by the foregoing embodiment, and the transmitting end performs data packet retransmission according to the message type, reduces the amount of retransmitted data, and reduces resources caused by retransmission. Consumption provides conditions.

Further, if it is determined that the last received sequence number of the message type to which the received first data packet belongs and the initial sequence number of the first data packet in the message type to which the first data packet belongs are not consecutive, the same message type before the first data packet is indicated. The data packet has an error, so before the receiving end receives the first data packet, the receiving end sends a retransmission request to the transmitting end by receiving the data packet in which the error occurred, and the retransmission request includes the data requesting retransmission. The total serial number of the packet corresponding to the packet. For ease of differentiation, the retransmission request described herein is referred to as a first retransmission request. Wherein, the first retransmission request The data packet requested for retransmission is a data packet received before the first data packet that belongs to the same message type as the first data packet and an error occurs.

Based on the foregoing, the receiving end receives the first retransmission response sent by the sending end after receiving the first data packet, and sends the first sending end according to the retransmission sequence number threshold recorded before the first retransmission request is sent. Retransmit the packet sent after the response is retransmitted. For retransmitted data packets, the receiving end does not count the total number of received packets, that is, when the retransmitted data packet is received, the receiving end does not update the total receiving sequence number. The first retransmission response is a retransmission response corresponding to the first retransmission request. The retransmission data packet described herein includes a data packet for which the first retransmission request is requested to be retransmitted, and the first data packet and the first data packet transmitted between the data packet requesting retransmission and the first data packet are the same message. Type of packet.

The receiving end receives, according to the retransmission sequence number threshold before sending the first retransmission request, the retransmission data packet sent by the transmitting end after sending the first retransmission response, where the receiving end receives the transmitting end and sends the first retransmission. The data packet sent after the response; the data packet sent by the sender after sending the first retransmission response will also include the message type to which it belongs and the packet sequence number in the message type to which it belongs. Then, the receiving end compares the sending sequence number of the data packet sent by the transmitting end after sending the first retransmission response in the message type to which the transmitting end belongs, and the retransmission sequence number threshold before sending the first retransmission request. If the sending sequence of the data packet sent by the sending end after sending the first retransmission response is less than or equal to the retransmission sequence number threshold before sending the first retransmission request, the data packet is retransmitted. The data packet, so the receiving end uses the data packet as a retransmission data packet. At this time, the receiving end does not update the total receiving sequence number after receiving the retransmission packet.

Herein, when the receiving end receives the data packet sent by the transmitting end after transmitting the first retransmission response, it first parses the received data packet, and distinguishes whether the data packet has an error according to the analysis result. Subsequent operations are performed when the result of the judgment is that no error has occurred in the packet.

If the sending sequence of the data packet sent by the sending end after sending the first retransmission response is greater than the retransmission sequence number threshold before the first retransmission request is sent, the data packet is not retransmitted. The data packet, but the newly transmitted data packet, needs to update the total sequence number of the received packet after receiving the data packet, and more specifically, the total sequence number of the received packet is increased by one. At the same time, the receiving end acquires the number sent by the receiving sender after sending the first retransmission response. According to the total number of the package corresponding to the package. That is, the receiving end can start receiving the data packet according to the process of step 301 to step 304.

The above process describes the processing procedure when the receiving end receives the data packet of the message type before receiving the retransmission response after the packet of the certain message type is in error, by discarding and recording the data packet received after the packet is received. The sequence number of the packet to be sent in the message type, and further distinguish which packets are retransmitted from the data packet sent by the sender after sending the retransmission response, ensuring that the total sequence number of the packet can be correctly counted and sent. The total sequence number of the outgoing packet is consistent, which lays the foundation for the retransmission of the data packet.

Further, when it is determined that the received first data packet has an error, the receiving end sends a second retransmission request to the transmitting end, where the second retransmission request includes a total received sequence number corresponding to the first data packet. Based on this, the receiving end receives the second retransmission response sent by the transmitting end, and receives the first data packet retransmitted by the transmitting end, and does not update the total sequence number of the receiving packet, that is, the total sequence number of the receiving packet is not added. 1. In this process, it is assumed that the receiving end does not receive a packet of the same message type as the packet in which the error occurred before receiving the second retransmission response. If the receiving end receives a packet of the same message type as the packet in which the error occurred before receiving the second retransmission response, the situation will be the same as the above procedure.

Further, when the receiving end finds that the first data packet has an error and sends a second retransmission request to the transmitting end, the receiving terminal may record the total receiving sequence number corresponding to the first data packet that is requested to be retransmitted. The first data packet retransmitted by the transmitting end received by the receiving end may also generate an error. At this time, the receiving end needs to resend the second retransmission request to the transmitting end, but in the process, along with the data of other message types. After receiving the packet, the total sequence number of the received packet may change, so the total sequence number of the first packet corresponding to the first data packet cannot be obtained according to the current total sequence number of the received packet, so the packet corresponding to the first data packet recorded before is received. The total sequence number can regenerate the second retransmission request and send it to the sender. If the first data packet retransmitted by the sender received by the receiving end does not have an error, the total sequence number of the received packet corresponding to the first data packet may be discarded.

In this embodiment, when receiving the retransmission request, the receiving end records the total sequence number of the packet corresponding to the data packet requested to be retransmitted, so as to continue to send the retransmission request to the transmitting end when the retransmitted data packet is still in error. It is beneficial to improve the success rate of receiving data packets.

The principle of the above embodiments of the present invention will be further described below in conjunction with the process of data transmission between the transmitting end and the receiving end. As shown in Figure 4, the sender is Link-A and the receiver is Link-B. Suppose the message type is 3, which are pktO, pktl, and pkt2. In FIG. 4, the data packet is represented by pak, and the number following the pak identifies the total sequence number of the packet or the total sequence number of the packet corresponding to the packet.

When Link-A sends a packet of a certain message type to Link-B, it records the sequence number of the packet of the message type, which is recorded as each_pkt_num, and also sends the total sequence number, which is recorded as total_pkt-num, and A mapping relationship table is created, and the mapping relationship table is stored

Total—pkt— num, each_pkt_num, and the correspondence between message types. When Link-A sends a packet of a certain message type to Link-B, it inserts each_pkt_num corresponding to the packet of this message type into the packet. Therefore, for a packet of the same message type, its corresponding eack_pkt_num is continuously accumulated by one. As shown in Figure 4, at the beginning, Link_A sends data packets pak0, pakl, pak2, pak3, etc. to Link-B.

When Link-B receives the data packet, it counts the number of all received data packets, that is, the total sequence number of the received packet, which is recorded as pkt_num, and extracts each_pkt_num contained in each data packet. When the data packet is correct, the extracted each_pkt_num and the last received sequence number of the message type are recorded as last_each_pkt_num (that is, each of the last received packet of the message type) Pkt — num ) Compare to determine if the packet of the message type is contiguous. If it is not continuous, it indicates that there is an error in the previous packet, then the packet is not received, but pkt_num continues to accumulate at this time. When there is an error in the currently received data packet, because Link-B cannot know the message type to which the data packet belongs, it will directly send a retry_request to Link_A and the total sequence number of the packet corresponding to the error packet (ie The value of pkt_num after receiving the packet) informs Link_A. Link-A can find the message type to which the error packet belongs and the corresponding each_pkt_num according to the total sequence number of the received packet corresponding to the error packet, and then start retransmission.

In conjunction with Figure 4, Link-B detects pakl (shown by dotted line in Figure 4). After an error occurs, a retransmission request is generated, which is retry-req (which contains the pkt-num corresponding to akl) to Link-A. Tells Link—A that there is a packet error and needs to be resent.

After that, Link-B will continue to receive packets sent by Link-A, such as pak2, pak3, etc., and will continue to count pkt_num. At this point, after determining that the received data packet is correct, Link_B will also match each_pkt_num in the data packet with the same message type.

Last_each_pkt_num compares to determine whether the packet of the message type is continuous: if it is continuous, it indicates that the packet of this message type has not been missed and continues to receive; if it is not continuous, If the packet of the message type is wrong before, the received packet is discarded, and each_pkt_num in the discarded packet is assigned to the retransmission sequence number threshold, which is recorded as

Max—each_pkt— num. As shown in Figure 4, pak3 and pakl have the same message type, so the pak3 received after the akl error needs to be discarded, and each_pkt_num in pak3 is assigned to max_each_pkt_num. Since ak2 and akl belong to different message types, and there is no error with the previous packet of ak2 belonging to the same message type, pak2 receives normally without discarding.

As shown in Figure 4, when Link-B successfully receives the data packet sent by LinK-A, it will send ack to Link-A.

When Link-A sends pakN, it receives retry_req, stops the normal packet transmission, and sends a retry res to Link-B. Link-A searches in the mapping table according to pkt_num in retry req, and obtains the retry buffer corresponding to the pktl message and the retransmission buffer corresponding to the starting position of pktl that needs to be retransmitted. Pakl. Then, all the packets that need to be retransmitted are read out from the retransmission buffer and sent to Link-B. As shown in Figure 4, assume that all packets that need to be retransmitted include pakl, pak3 - pakM (shown in phantom in Figure 4).

After Link-A sends pakM, it continues to send normal data packets, such as pak(N+l). After Link-B detects retry_res, it stops counting pkt_num for pktl type packets, that is, it does not increment pkt_num after receiving the packet of message type pktl. Link-B receives the link_A retransmitted message type pktl packet, extracts each_pkt_num, and compares the extracted each_pkt_num with max_each_pkt_num, when each_ When pkt_num is greater than max_each_pkt_num, the pkt_num is restarted for the packet of the message type pktl, that is, each_pkt_num is greater than max in the packet detecting the message type pktl. For each_pkt_num, you need to force kt num 1 and then need to add 1 to pkt_num when receiving a new packet with message type pktl.

Link-B normally receives subsequent data packets and sends ack to Link-A when it successfully receives subsequent data packets.

Here, if a packet of a certain message type fails, Link_B does not receive the packet of the message type before receiving retry_res, then max_each_pkt_num is invalid, indicating the data of the message type during the period. The packet is only wrong once or the packet of the message type is always in error, and the normal max_each_pkt_num cannot be obtained, in order to guarantee kt num Correct, Link - 不会 will not count the first received packet after receiving retry- res, ie will not add pkt_num to 1, because the packet is retransmitted and the packet has been counted It is.

Further, when Link-B detects a packet error, it also saves pkt_num at this time, that is, pkt_num corresponding to the error packet. After receiving the retry_res, if the first received packet has no error, the saved pkt_num is discarded; if the first received packet after retry-res has an error, it needs to be redirected to the Link- A sends retry_req, at which point pkt_num in retry req is the previously saved pkt_num, not the current pkt_num. In this way, after Link-A receives retry req, it can find the correct retransmission packet type and the starting position of the retransmission packet in the mapping table according to pkt_num in retry req.

It can be seen from the above that the data packet retransmission method and the data packet receiving method provided by the embodiment of the present invention cooperate with each other, and in a scenario requiring retransmission, only a certain type of data packet can be retransmitted without After that, all other types of data packets are retransmitted, which reduces the amount of data retransmitted, saves resource waste caused by the retransmission mechanism, and improves the bandwidth utilization of the system.

FIG. 5 is a schematic structural diagram of a data packet sending apparatus according to an embodiment of the present invention. As shown in FIG. 5, the data packet transmitting apparatus 5 of this embodiment includes: a first receiving module 51, a first processing module 52, and a first transmitting module 53.

The first receiving module 51 is configured to receive a retransmission request, where the retransmission request is sent by the receiving end, where the retransmission request includes a total sequence number of the packet corresponding to the data packet requesting retransmission. The total sequence number of the received packet is a sequence number obtained by the receiving end to count the data packets of all received message types. The total sequence number of the packet corresponding to the data packet requesting retransmission is the total sequence number of the packet received after the receiving end receives the data packet requesting retransmission.

The first processing module 52 is connected to the first receiving module 51, and is configured to receive a total sequence number of the packet corresponding to the data packet retransmitted according to the request in the retransmission request received by the first receiving module 51, and a total sequence of the locally stored packet. The mapping relationship between the number and the packet sequence number of each message type obtains the message type to which the data packet requesting retransmission belongs and the packet sequence number of the data packet requesting retransmission in the message type to which it belongs. The total sequence number of the packet is a sequence number obtained by counting packets of all message types sent.

The first sending module 53 is connected to the first processing module 52, and the message type to which the data packet retransmitted according to the request acquired by the first processing module 52 belongs and the data packet requested to be retransmitted are themselves The packet sequence number in the associated message type, the data packet requesting retransmission is sent to the receiving end, and the data packet sent after the requesting retransmitted data packet belongs to the same message type as the data packet requesting retransmission.

The function modules of the data packet transmitting apparatus in this embodiment can be used to perform the process of the data packet retransmission method shown in FIG. 1. The specific working principle is not described here. For details, refer to the description of the method embodiment.

The packet sending device of this embodiment may be any device or device in the device having a retransmission mechanism. For example, the sender may be a server, a routing device, or the like, or may be a QPI in the CPU or a QPI in the interconnect chip.

After receiving the retransmission request sent by the receiving end, the data packet transmitting apparatus of the embodiment receives the total sequence number of the packet corresponding to the data packet retransmitted by the receiving end, and the total sequence number of the packet and the message type of each of the locally stored packets. Correspondence between the serial numbers of the outgoing packets, find the message type to which the data packet requesting retransmission belongs, and the sequence number of the outgoing packet in the message type to which the data packet requesting retransmission belongs, and then obtain the request from the retransmission buffer according to the information. The retransmitted data packet and the data packet sent after the data packet requested to be retransmitted belong to the same message type, and then the obtained data packets are resent to the receiving end. The data packet transmitting apparatus of this embodiment realizes that only the same type of data packet is retransmitted in the process of data packet retransmission, and other types of data packets sent after requesting the retransmitted data packet are not used when retransmission is not required. Retransmission, which reduces the amount of data retransmitted, and reduces the amount of data that is retransmitted compared with the solution in the prior art that retransmits the data packet that is requested to be retransmitted and all data packets that are sent after the data packet is retransmitted to the receiving end. Waste of resources caused by the transmission mechanism.

FIG. 6 is a schematic structural diagram of a data packet sending apparatus according to an embodiment of the present invention. This embodiment is implemented based on the embodiment shown in FIG. As shown in FIG. 6A, the data packet transmitting apparatus 6 of this embodiment also includes a first receiving module 51, a first processing module 52, and a first transmitting module 53, and each module also has the functions described in the embodiment shown in FIG. .

In this embodiment, the first processing module 52 is further configured to send, at the first sending module 53, the data packet requesting retransmission to the receiving end, and the data packet sent after requesting the retransmitted data packet to be requested to be retransmitted. Before the data packet of the message type, it is judged whether the message type of the data packet requesting the retransmission belongs to the same message type as the data packet to which the previous retransmission request request retransmission belongs, and when the judgment result is different, the first sending module is triggered. 53 performing the message type to which the data packet retransmitted according to the request belongs and the data packet requested to be retransmitted in the message type to which it belongs The serial number, the operation of transmitting the data packet requesting retransmission to the receiving end and the data packet of the same message type sent after the data packet requesting retransmission is sent after the data packet requesting retransmission is sent.

Further, the first processing module 52 of the embodiment is further configured to discard the retransmission request received by the first receiving module 51 when the determination result is the same.

Further, the first sending module 53 of this embodiment is further configured to send the first data packet to the receiving end. The first data packet is a data packet sent to the receiving end for the first time, and the first data packet includes a message type to which the first data packet belongs and a delivery sequence number of the first data packet in the message type to which the first data packet belongs.

Correspondingly, the first processing module 52 is further configured to buffer the first data packet, and update a mapping relationship between the total packet sequence number and the packet sequence number of each message type according to the message type to which the first data packet belongs.

Further, the packet transmitting apparatus of this embodiment includes a plurality of retransmission buffers 54. Different retransmission buffers 54 are used to buffer packets of different message types. The first processing module 52 is specifically configured to buffer the first data packet into the retransmission buffer 54 corresponding to the first data packet according to the message type to which the first data packet belongs.

Further, the first transmitting module 53 of this embodiment includes: a retransmission control unit 531, a transmission control unit 532, and a transmitting unit 533.

The retransmission control unit 531 is connected to the first processing module 52, and is configured to determine, according to the message type to which the data packet retransmitted by the first processing module 52 belongs, a retransmission buffer corresponding to the data packet requesting retransmission. 54.

The sending control unit 532 is connected to the first processing module 52 and the retransmission buffer 54 for requesting the retransmission of the data packet according to the request acquired by the first processing module 52 in the message type of the message type to which the first processing module 52 belongs. The retransmission buffer 54 corresponding to the retransmitted data packet acquires the data packet requesting retransmission and the data packet transmitted after the data packet requested to be retransmitted belongs to the same message type as the data packet requested to be retransmitted.

The sending unit 533 is connected to the sending control unit 532, and configured to send a retransmission response to the receiving end, and then send the data packet requested by the sending control unit 532 and retransmitted to the receiving end, and send the data packet after requesting the retransmitted data packet. A packet belonging to the same message type as the packet requested to be retransmitted.

Optionally, the sending unit 533 is specifically configured to acquire, at the first processing module 52, the request for retransmission. The message type to which the data packet belongs and the data packet requesting retransmission send a retransmission response to the receiving end before the packet sequence number in the message type to which it belongs. or

The sending unit 533 is specifically configured to send a retransmission response to the receiving end before the retransmission control unit 531 determines the retransmission buffer corresponding to the data packet requesting retransmission according to the message type of the data packet requested to be retransmitted. Or

The sending unit 533 is specifically configured to: in the retransmission buffer corresponding to the data packet requesting retransmission, the sending control unit 532 acquires the data packet requesting retransmission and the data sent after requesting the retransmitted data packet and requesting retransmission After the packet belongs to the same message type packet, the retransmission response is sent to the receiving end.

Further, the first sending module 53 of this embodiment further includes: a special packet generating unit 534. The special packet generation unit 534 is configured to generate a retransmission response. Optionally, the special packet generating unit 534 is connected to the first processing module 52 and the sending unit 533 for generating a retransmission response under the control of the first processing module 52, and providing the retransmission response to the sending unit 533.

Optionally, when the data packet sending apparatus of the embodiment receives the data packet and finds that the data packet is in error, the special packet generating unit 534 is further configured to generate a retransmission request. In addition, the special packet generating unit 534 of this embodiment is also used to generate an ack message or the like.

Further, the first processing module 52 of this embodiment may include: a receiving decoding unit 521 and a system control unit 522.

The receiving and decoding unit 521 is connected to the first receiving module 51, and configured to parse the retransmission request received by the first receiving module 51, and obtain the total sequence number of the packet corresponding to the data packet requesting retransmission.

The system control unit 522 is connected to the receiving and decoding unit 521, and is configured to match the total sequence number of the packet corresponding to the data packet requesting retransmission with the total sequence number of the packet in the locally stored mapping relationship table, and send the matching packet in the matching. The message type corresponding to the total sequence number and the packet sequence number of the message type respectively serve as the message type to which the data packet requesting retransmission belongs and the packet sequence number in the message type to which the data packet requested to be retransmitted belongs. The mapping relationship table stores a mapping relationship between the total sequence number of the packet and the packet sequence number of each message type.

Specifically, the system control unit 522 is also connected to the retransmission control unit 531, the transmission control unit 532, and the special packet generation unit 534.

Combining the above structure of the first processing module 52 and the first sending module 53, the first sending module Specifically, the sending unit 533 can send the first data packet to the receiving end. Correspondingly, the first processing module 52 may specifically cache the first data packet by its system control unit 522, and update between the total packet sequence number and the packet sequence number of each message type according to the message type to which the first data packet belongs. Mapping relations. More specifically, the first processing module 52 may specifically cache the first data packet by the system control unit 522 according to the message type to which the first data packet belongs to the retransmission buffer 54 corresponding to the first data packet.

Further, in combination with the foregoing structure of the first processing module 52, the first processing module 52 may specifically determine, by its system control unit 522, the message type to which the data packet requesting retransmission belongs and the message to which the data packet to which the previous retransmission request requests retransmission belongs. Whether the types are the same; when the judgment result is different, triggering the first sending module 53 to execute the message type to which the data packet retransmitted according to the request belongs and the packet sequence number of the data packet requesting retransmission in the message type to which the request belongs, The receiving end sends the data packet requesting retransmission and the data packet sent after the data packet requesting retransmission belongs to the same message type as the data packet requesting retransmission; when the judgment result is the same, the first receiving module 51 is used. The received retransmission request is discarded.

The foregoing functional modules or units may be used to perform the process of the data packet retransmission method shown in FIG. 1 or FIG. 2, and the specific working principle is not described here. For details, refer to the description of the method embodiments.

FIG. 6B is a schematic structural diagram of a link layer of a QPI protocol according to an embodiment of the present invention. As shown in FIG. 6B, the QPI protocol in this embodiment includes: a protocol layer of QPI, a link layer of QPI, and The physical layer of QPI. The link layer of QPI is responsible for receiving and retransmitting data packets. The link layer of QPI mainly includes: receiving module rx, receiving decoding module rx_decode, system control module sys-Ctrl, multiple retransmission control modules retry- ctrl, sending control module tx- Ctrl, special packet generating module gen sp , multiple retransmission buffers retry_buf and sending module tx.

With reference to the structure of the data packet transmitting apparatus shown in FIG. 6A, the receiving module rx of this embodiment is equivalent to the first receiving module 51 in the embodiment shown in FIG. 6A; the receiving decoding module rx_decode of this embodiment is equivalent to FIG. 6A. The receiving and decoding unit 521 in the illustrated embodiment; the system control module sys_Ctrl of the embodiment is equivalent to the system control unit 522 in the embodiment shown in FIG. 6A; the retransmission control module retry_Ctrl of the embodiment is equivalent to The retransmission control unit 531 in the embodiment shown in FIG. 6A; the transmission control module tx_Ctrl of the embodiment is equivalent to the transmission control unit 532 in the embodiment shown in FIG. 6A; the special packet generation module gen-sp of this embodiment Corresponding to the special packet generating unit 534 in the embodiment shown in FIG. 6A; the retransmission buffer retry_buf of this embodiment is equivalent to the retransmission buffer 54 in the embodiment shown in FIG. 6A; the sending of this embodiment The module tx corresponds to the transmitting unit 533 in the embodiment shown in Fig. 6A.

In this embodiment, the receiving module rx is an interface between the link layer and the physical layer, and is configured to receive data packets from the physical layer. The receiving decoding module rx_decode is used for decoding the data packet received by the receiving module rx, extracting the link layer contained in the data packet and sending the information to the system control module sys_Ctrl, and receiving Whether the packet is incorrect and which packet error is sent to the retransmission control module retry_ctrl. The system control module sys-Ctrl is mainly used to send control information to the retransmission control module retry- ctrl, the send control module tx-Ctrl, and the special packet generation module gen-sp. The retransmission control module retry-Ctrl is used to control the read/write pointer of the retry buffer retry_buf. The send control module tx_Ctrl is used to select the data to be sent from the retransmission buffer retry_buf, the protocol layer, and the special packet generation module gen-sp. The special packet generation module gen-sp is used to generate special packets used by the link layer, such as acknowledgment (ack), retry-request, retry-response, and so on. Retransmission buffer retry_buf, used to receive the sequence number of the error packet in the retry_requset when retransmission is required

( pkt_num ), find the starting position of the packet that needs to be retransmitted in the retransmission buffer. The sending module tx is used to send data packets.

The link layer of the QPI protocol of the embodiment has the function of transmitting and receiving data packets at the same time. The functions of the modules in the link layer of the QPI protocol of the present embodiment are described above as a whole. According to the packet retransmission, the functions of each module in the link layer when the data packet is retransmitted are described in detail.

If the data packet from the physical layer is a retransmission request sent by the receiving end, the receiving module rx receives the retransmission request from the physical layer. The receiving decoding module rx_decode is used to decode the retransmission request received by the receiving module rx, extract the total sequence number of the packet corresponding to the data packet requesting retransmission, and provide it to the system control module sys- Ctrl. The system control module sys_Ctrl matches the total sequence number of the packet corresponding to the retransmitted data packet with the total sequence number of the packet in the locally stored mapping relationship table, and matches the message type corresponding to the total sequence number of the received packet in the match. The message sequence number of the message type is used as the message type to which the data packet requesting retransmission belongs and the packet sequence number of the data packet requesting retransmission in the message type to which the request is retransmitted, and the message type to which the retransmitted data packet belongs is controlled. The information is provided to the corresponding retransmission control module retry_Ctrl, and the packet sequence number of the data packet requesting retransmission in the message type to which it belongs is provided as control information to the transmission control module tx_ctrl. The retransmission control module retry-Ctrl selects the corresponding retransmission buffer retry_buf according to the message type to which the retransmitted packet belongs. The sending control module tx_Ctrl obtains the data packet requesting retransmission from the retransmission buffer retry_buf selected by the retry control module retry_Ctrl according to the packet sequence number in the message type to which the request is retransmitted. A packet sent after a packet that is requested to be retransmitted. The sending module tx sends the data packet obtained by the sending control module tx_Ctrl to the receiving end.

Further, the special packet generation module gen-sp generates a retransmission response before the sending module tx sends the data packet acquired by the control module tx_Ctrl to the receiving end; the sending module tx sends the retransmission response to the receiving end, and then receives the retransmission response. The data packet sent by the control module tx_Ctrl is sent.

In this embodiment, the link layer of the QPI protocol sets a plurality of retransmission buffers, so that each retransmission buffer corresponds to one message type, and stores the total sequence number of the packet and the packet sequence number of each message type. Correspondence between the two types, so that after receiving the retransmission request from the receiving end, only the same type of data packet can be retransmitted, and other types of data packets sent after requesting the retransmitted data packet do not need to be retransmitted. Without retransmission, compared with the prior art scheme of retransmitting the data packet requesting retransmission and all data packets sent after the data packet requested to be retransmitted to the receiving end, the amount of retransmitted data is reduced, and the number of data is reduced. Waste of resources caused by the retransmission mechanism.

FIG. 7 is a schematic structural diagram of a data packet receiving apparatus according to an embodiment of the present invention. As shown in FIG. 7, the data packet receiving apparatus 7 of this embodiment includes: a second receiving module 71 and a second processing module 72. The second receiving module 71 is configured to receive the first data packet sent by the sending end. The first data packet includes a message type to which the first data packet belongs and a delivery sequence number of the first data packet in a message type to which the first data packet belongs.

The second processing module 72 is connected to the second receiving module 71, and configured to: after receiving the first data packet, the second receiving module 71, modify the total sequence number of the received packet to obtain the total number of the received packet corresponding to the first data packet, And determining that the first packet received by the second receiving module 71 does not generate an error, acquiring the last packet sequence number of the message type to which the first data packet belongs according to the message type to which the first data packet belongs, and determining the first Whether the last received sequence number of the message type to which the data packet belongs and whether the first data packet is consecutive in the message type of the message type to which it belongs, and when the judgment result is continuous, the last message type to which the first data packet belongs is received. The packet sequence number is updated to the packet sequence number of the first packet in the message type to which it belongs. The total sequence number of the received packet is a sequence number obtained by counting the data packets of all received message types; the last received sequence number of the message type to which the first data packet belongs is the last received before the first data packet. The first packet belongs to the packet sequence number of the packet of the same message type in the message type to which it belongs.

The function modules of the data packet receiving apparatus of this embodiment can be used to execute the flowchart of the data packet receiving method shown in FIG. 3. The specific working principle is not described here. For details, refer to the description of the method embodiment.

The data packet receiving apparatus in this embodiment may be any device in the device or device having a retransmission mechanism, for example, the receiving end may also be a server, a routing device, or the like, or may be a QPI in the CPU or a QPI in the interconnect chip.

The data packet receiving apparatus of the embodiment cooperates with the data packet sending apparatus provided by the embodiment of the present invention, and parses the data packet after receiving the data packet. If the data packet can be successfully solved, according to the data packet, the data packet belongs to The message type and the packet sequence number in the message type to which the packet belongs determine whether to discard the packet, and if the packet is not discarded, update the last packet sequence number of the message type to which the packet belongs, so as to continue Receiving a subsequent data packet, if the data packet is discarded, the packet sequence number of the data packet in the associated message type is recorded correspondingly, so as to distinguish the retransmitted data packet from the data packet sent by the sender, and implement the data packet. The receiving, for the data packet transmitting device, retransmits the data packet according to the message type, reduces the amount of retransmitted data, and reduces the resource consumption caused by the retransmission.

FIG. 8 is a schematic structural diagram of a data packet receiving apparatus according to another embodiment of the present invention. This embodiment is implemented based on the embodiment shown in FIG. As shown in FIG. 8, the data packet receiving apparatus of this embodiment 8 also includes: a second receiving module 71 and a second processing module 72, and each module also has the functions described in the embodiment shown in FIG.

Further, the second processing module 72 of the embodiment is further configured to: when the result of the determination is that the last received sequence number of the message type to which the first data packet belongs and the initial sequence number of the first data packet in the message type to which the first data packet belongs are discontinuous When the first data packet is recorded as the retransmission sequence number threshold in the message sequence number of the message type to which the first data packet belongs, the first data packet is discarded.

Further, the apparatus of this embodiment further includes: a second sending module 73.

The second sending module 73 is configured to send a first retransmission request to the sending end before the second receiving module 71 receives the first data packet. The first retransmission request includes a total sequence number of the packet corresponding to the data packet requesting retransmission; the data packet requested to be retransmitted is the same message type received before the first data packet and the error occurs. data pack.

Based on this, the second receiving module 71 is further configured to receive the first retransmission response sent by the sending end. Correspondingly, the second processing module 72 is further configured to receive, according to the retransmission sequence number threshold before sending the first retransmission request, the retransmission data packet sent by the transmitting end after sending the first retransmission response. The retransmitted data packet includes a data packet requesting retransmission, a first data packet, and a data packet that is sent between the data packet requesting retransmission and the first data packet and belongs to the same message type as the data packet.

For the second receiving module 71, the data packet sent by the transmitting end after transmitting the first retransmission response is also received. The second processing module 72 is specifically configured to: send, by the sending end, the data packet sent by the sending end after sending the first retransmission response, the sequence number of the sending packet in the message type to which the transmitting end belongs, and the retransmission sequence number threshold before sending the first retransmission request. Comparing, when the sending packet sent by the transmitting end after transmitting the first retransmission response has a packet sequence number in the message type to which it belongs is less than or equal to the retransmission sequence number threshold before the first retransmission request is sent, the transmitting end is The data packet sent after the first retransmission response is sent as a retransmission data packet.

Further, the second processing module 72 is further configured to: after the sending of the first retransmission response, the data packet sent by the transmitting end in the message type to which the first packet is sent is greater than the retransmission sequence number of the packet before the first retransmission request is sent. The time limit is updated, and the total sequence number of the received packet is obtained, and the total sequence number of the packet corresponding to the data packet sent by the sender after sending the first retransmission response is obtained.

Further, the second sending module 73 is further configured to send a second retransmission request to the sending end when it is determined that the first data packet received by the second receiving module 71 is incorrect. The second retransmission request includes a total sequence number of the packet corresponding to the first data packet. Correspondingly, the second receiving module 71 is further configured to: after receiving the second retransmission response sent by the sending end, receive the first data packet retransmitted by the sending end.

Further, the second processing module 72 is further configured to record a total sequence number of the packet corresponding to the first data packet. The second sending module 73 is further configured to: when determining that the re-received first data packet has an error, regenerate according to the total received sequence number corresponding to the first data packet recorded by the second processing module 72, and send the second to the sending end. Retransmit the request. Optionally, the second processing module 72 and the second sending module 73 are connected.

Each of the foregoing functional modules can be used to perform the process of the data packet receiving method provided in the foregoing embodiment, and the specific working principle is not described herein.

For example, when the link layer of the QPI protocol shown in FIG. 6B receives a data packet as a receiving end, it can be used as the data packet receiving apparatus of this embodiment. The functions of the respective modules shown in Fig. 6B and the packet receiving apparatus of this embodiment will be described below. Specifically, the receiving module rx in the embodiment shown in FIG. 6B is equivalent to the second receiving module 71 in the embodiment; the receiving decoding module rx_decode and the system control module sys-Ctrl in the embodiment shown in FIG. 6B can be As the second processing module 72 in this embodiment, the transmission control module tx- ctrl, the special packet generation module gen-sp, and the transmission module tx in the embodiment shown in FIG. 6B are equivalent to the second transmission module 73 in this embodiment. . For the process of receiving the data packet, the link layer of the QPI protocol shown in FIG. 6B can be referred to the embodiment shown in FIG. 3 or the description of the embodiment, and details are not described herein again.

The data packet receiving apparatus of the embodiment cooperates with the data packet sending apparatus provided by the embodiment of the present invention, and parses the data packet after receiving the data packet. If the data packet can be successfully solved, the data packet is determined according to the data packet. The message type of the message type and the packet sequence number in the message type to which the data packet belongs determine whether to discard the data packet, and if the data packet is not discarded, update the last packet sequence number of the message type to which the data packet belongs, so as to facilitate Continue to receive subsequent data packets. If the data packet is discarded, the packet sequence number of the data packet in the associated message type is recorded correspondingly, so as to distinguish the retransmitted data packet from the data packet sent by the sender, and implement the data packet. Receiving, and when an error occurs in the data packet, by transmitting a retransmission request to the data packet transmitting apparatus as the transmitting end, the data packet transmitting apparatus performs retransmission of the data packet according to the message type, thereby reducing the amount of retransmitted data and reducing retransmission. The resource consumption provides conditions.

It will be understood by those skilled in the art that all or part of the steps of implementing the above method embodiments may be performed by hardware related to the program instructions. The aforementioned program can be stored in a calculation The machine can be read from the storage medium. When the program is executed, the steps including the foregoing method embodiments are performed; and the foregoing storage medium includes: a medium that can store program codes, such as a ROM, a RAM, a magnetic disk, or an optical disk.

It should be noted that the above embodiments are merely illustrative of the technical solutions of the present invention, and are not intended to be limiting; although the present invention has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art The technical solutions described in the foregoing embodiments may be modified, or some or all of the technical features may be equivalently replaced; and the modifications or substitutions do not deviate from the technical solutions of the embodiments of the present invention. range.

Claims

Claim

A data packet retransmission method, characterized in that:

Receiving a retransmission request, where the retransmission request is sent by the receiving end, where the retransmission request includes a total sequence number of the packet corresponding to the data packet requesting retransmission;

The data packet retransmission method according to claim 1, wherein the message type to which the data packet retransmitted according to the request belongs and the data packet to which the request is retransmitted are in a message type to which the message belongs. Sending a sequence number, sending the data packet requesting retransmission to the receiving end, and including before the data packet requesting retransmission, the data packet that belongs to the same message type as the data packet requested to be retransmitted :

Determining whether the message type to which the request retransmitted data packet belongs is the same as the message type to which the previous retransmission request request retransmitted data packet belongs;

If not, the request retransmission is sent to the receiving end according to the message type to which the retransmitted data packet belongs and the data packet sequence number of the request retransmitted data packet in the message type to which the request belongs. The data packet and the data packet sent after the data packet requested to be retransmitted belong to the same message type as the data packet retransmitted by the request.

The data packet retransmission method according to claim 1 or 2, wherein the message type to which the data packet retransmitted according to the request belongs and the message that the request retransmitted data packet belong to a packet sequence number in the type, sending, to the receiving end, the data packet requesting retransmission and the data packet sent after the data packet requested to be retransmitted and belonging to the same message type as the data packet retransmitted by the request include: Determining, according to a message type to which the data packet retransmitted by the request belongs, a retransmission buffer corresponding to the data packet requested to be retransmitted;

Obtaining, according to the packet sequence number of the message type to which the request is retransmitted, the data packet requesting retransmission from the retransmission buffer corresponding to the data packet that is requested to be retransmitted, and the And the data packet that is sent after the data packet that is requested to be retransmitted and that is retransmitted by the request belongs to a data packet of the same message type;

Sending a retransmission response to the receiving end, and then transmitting, to the receiving end, the data packet requesting retransmission and the data packet sent after the requesting retransmitted data packet and the data packet retransmitted by the request belong to the same message Type of packet.

The method for retransmitting a data packet according to claim 1 or 2, wherein the total sequence number of the packet corresponding to the data packet retransmitted according to the request and the total sequence number of the locally stored packet are each The mapping relationship between the message sequence numbers of the message types, the message type to which the data packet requested to be retransmitted belongs, and the packet sequence number of the data packet requested to be retransmitted in the message type to which the request belongs include:

Parsing the retransmission request, and obtaining a total sequence number of the packet corresponding to the data packet that is requested to be retransmitted;

And matching the total sequence number of the packet corresponding to the data packet that is requested to be retransmitted with the total sequence number of the packet in the locally stored mapping relationship table; the mapping relationship table stores the total sequence number of the packet and each of the packets The mapping relationship between the message sequence numbers of the message types;

The message type corresponding to the total sequence number of the delivery packet and the delivery sequence number of the message type are respectively used as the message type to which the data packet requested to be retransmitted and the message to which the request retransmitted packet belongs. The serial number of the packet in the type.

The data packet retransmission method according to claim 1 or 2, further comprising:

Sending a first data packet to the receiving end, buffering the first data packet, and updating the total packet serial number and the sending sequence number of each message type according to the message type to which the first data packet belongs The first data packet is a data packet sent to the receiving end for the first time, and the first data packet includes a message type to which the first data packet belongs and the first data packet belongs to the first data packet. The serial number of the packet in the message type.

6. The data packet retransmission method according to claim 5, wherein The first data packet is cached, including:

And storing, according to the message type to which the first data packet belongs, the first data packet into a retransmission buffer corresponding to the first data packet.

7. A data packet receiving method, comprising:

Receiving a first data packet sent by the sending end, and modifying a total sequence number of the received packet to obtain a total sequence number of the received packet corresponding to the first data packet; the total sequence number of the receiving packet is a data packet of all message types received Counting the obtained serial number; the first data packet includes a message type to which the first data packet belongs and a delivery sequence number of the first data packet in a message type to which the first data packet belongs; when the first data is determined Obtaining, according to the message type to which the first data packet belongs, the last received sequence number of the message type to which the first data packet belongs, and the last received sequence of the message type to which the first data packet belongs. The number of the packet sent in the message type to which the data packet of the same message type that was last received before the first data packet belongs in the message type to which the first data packet belongs;

8. The data packet receiving method according to claim 7, further comprising: when the determination result is a last received sequence number of the message type to which the first data packet belongs and the first data packet is in itself If the sequence number of the packet in the associated message type is not continuous, the packet sequence number of the first packet in the message type to which the packet belongs is recorded as a retransmission sequence number threshold, and the first packet is discarded.

The data packet receiving method according to claim 8, wherein the receiving the first data packet sent by the transmitting end comprises:

Sending a first retransmission request to the sending end, where the first retransmission request includes a total sequence number of the packet corresponding to the data packet requesting retransmission; and the data packet requested to be retransmitted is in the first data packet a previously received data packet that belongs to the same message type as the first data packet and that has an error; the method further includes: Receiving a first retransmission response sent by the sending end, and receiving retransmission data sent by the sending end after sending the first retransmission response according to a retransmission sequence number threshold before sending the first retransmission request The retransmission data packet includes the data packet requesting retransmission, the first data packet, and the data packet sent between the data packet requesting retransmission and the first data packet Packets belonging to the same message type.

The data packet receiving method according to claim 9, wherein the receiving, according to the retransmission sequence number threshold, the retransmission data packet sent by the transmitting end after sending the first retransmission response includes :

Receiving a data packet sent by the sending end after sending the first retransmission response; sending a packet sequence number of the data packet sent by the sending end after sending the first retransmission response in a message type to which the transmitting end belongs Comparing with a retransmission sequence number threshold before sending the first retransmission request;

If the sending sequence of the data packet sent by the sending end after sending the first retransmission response is less than or equal to the retransmission sequence number threshold before sending the first retransmission request, The data packet sent by the transmitting end after sending the first retransmission response is used as the retransmission data packet.

11. A data packet transmitting apparatus, comprising:

The data packet transmitting apparatus according to claim 11, wherein the first processing module is further configured to determine a message type to which the data packet requested to be retransmitted belongs and a previous one The message type of the data packet to which the retransmission request is retransmitted is the same. If the result of the determination is not the same, the first sending module is triggered to execute the message type to which the data packet retransmitted according to the request belongs and the request is heavy. Sending a sequence number of the transmitted data packet in the message type to which the packet belongs, sending the data packet requesting retransmission to the receiving end, and retransmitting the request and transmitting the data packet after the requesting retransmission The operation of a packet belonging to a packet of the same message type.

The data packet transmitting apparatus according to claim 11 or 12, further comprising:

Multiple retransmission buffers for buffering transmitted data packets;

The first sending module includes:

a retransmission control unit, configured to determine, according to a message type to which the data packet retransmitted by the request belongs, a retransmission buffer corresponding to the data packet requested to be retransmitted;

a sending control unit, configured to obtain, according to the packet sequence number of the message type to which the request is retransmitted, the retransmission request from the retransmission buffer corresponding to the data packet that is requested to be retransmitted a data packet and a data packet sent after the data packet requested to be retransmitted and belonging to the same message type as the data packet retransmitted by the request;

a sending unit, configured to send a retransmission response to the receiving end, and then send the data packet requesting retransmission to the receiving end, and the retransmission with the request sent after the requesting retransmitted data packet Packets belong to packets of the same message type.

The data packet transmitting apparatus according to claim 11 or 12, wherein the first processing module comprises:

a receiving decoding unit, configured to parse the retransmission request, and obtain a total sequence number of the packet corresponding to the data packet requested to be retransmitted;

a system control unit, configured to match a total sequence number of the packet corresponding to the data packet that is retransmitted to the total sequence number of the packet in the locally stored mapping relationship table, and to match the total sequence number of the packet in the matching The corresponding message type and the message sequence number of the message type respectively serve as the message type to which the data packet requested to be retransmitted belongs and the packet sequence number in which the data packet requested to be retransmitted belongs in the message type to which the request belongs; The relationship table stores a mapping relationship between the total sequence number of the packet and the packet sequence number of each message type.

The data packet transmitting apparatus according to claim 11 or 12, wherein the first sending module is further configured to send the first data packet to the receiving end, where the first data packet is a data packet sent to the receiving end for the first time, the first data packet includes a message type to which the first data packet belongs and a packet sequence number of the first data packet in a message type to which the first data packet belongs; A processing module is further configured to buffer the first data packet, and update a mapping relationship between the total packet sequence number and the packet sequence number of each message type according to the message type to which the first data packet belongs.

16. A data packet receiving apparatus, comprising:

The data packet receiving apparatus according to claim 16, wherein the second processing module is further configured to: in the determination result, a last received sequence number of the message type to which the first data packet belongs, and the When the first data packet is discontinuous in the message sequence number of the message type to which the first data packet belongs, the first data packet is recorded as the retransmission sequence number threshold in the message sequence number of the message type to which the first data packet belongs, and the first data packet is recorded as the retransmission sequence number threshold. A packet is dropped.

The data packet receiving apparatus according to claim 17, further comprising: a second sending module, configured to send, to the sending end, before the second receiving module receives the first data packet a first retransmission request, where the first retransmission request includes a total sequence number of the packet corresponding to the data packet requesting retransmission; and the data packet requested to be retransmitted is received before the first data packet and The first packet belongs to the same message type and the packet in which the error occurred; The second receiving module is further configured to receive a first retransmission response sent by the sending end, where the second processing module is further configured to receive, according to a retransmission sequence number threshold before sending the first retransmission request Transmitting a retransmission data packet sent by the transmitting end after sending the first retransmission response; the retransmission data packet includes the data packet requesting retransmission, the first data packet, and retransmission in the request A data packet transmitted between the data packet and the first data packet that belongs to the same message type as the data packet.

The data packet receiving apparatus according to claim 18, wherein the second receiving module is further configured to receive a data packet that is sent by the sending end after sending the first retransmission response;

The second processing module is specifically configured to send, by the sending end, a data packet sent by the sending end after the sending the first retransmission response, a packet sequence number in a message type to which the transmitting end belongs, and before sending the first retransmission request. The retransmission sequence number threshold is compared, and the data packet sent by the sending end after sending the first retransmission response in the message type to which the UE belongs is less than or equal to the first retransmission request before sending the first retransmission request. When the sequence number threshold is retransmitted, the data packet sent by the transmitting end after transmitting the first retransmission response is used as the retransmission data packet.