WO2018072097A1 - Data transmission method and device - Google Patents

Abstract

Embodiments of the present invention relate to a data transmission method and device. The method comprises: a sending device determines a mapping relationship between a TCP data packet identifier and an RLC PDU identifier; receive an RLC status report sent by a receiving device, the RLC status report comprising the RLC PDU identifier and being used for indicating the receiving condition, at the receiving device, of the RLC PDU indicated by the RLC PDU identifier comprised in the RLC status report; the sending device generates a TCP status report according to the RLC status report and the mapping relationship between the TCP data packet identifier and the RLC PDU identifier, the TCP status report being used for indicating the receiving condition of the TCP data packet at the receiving device. The present invention achieves the function of a TCP acknowledgement packet by means of the transmission of an RLC acknowledgement packet at an air interface. The resources occupied by the RLC acknowledgement packet during air interface transmission are far less than those occupied by the TCP acknowledgement packet, and therefore, the transmission rate of data flow of a TCP protocol can be improved.

Description

Data transmission method and device Technical field

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

Background technique

The Transmission Control Protocol (TCP) is a connection-oriented, reliable, byte stream-based transport layer communication protocol defined by the Internet Engineering Task Force (IETF) RFC 793. In the simplified computer network OSI model, it performs the functions specified by the fourth layer of the transport layer. The User Datagram Protocol (UDP) is another important transport protocol in the same layer. In the Internet protocol suite, the TCP layer is an intermediate layer located above the Internet Protocol (IP) layer and below the application layer. Reliable, pipe-like connections are often required between application layers of different hosts, but the IP layer does not provide such a flow mechanism, but provides unreliable packet switching.

At present, the data traffic on the Internet and the data traffic of the TCP protocol account for more than 90%. Among them, the data traffic of the TCP protocol on the mobile network also accounts for the vast majority. For example, streaming media, web browsing, Email, Filehosting, and SNS services are basically based on the TCP protocol, peer-to-peer (Peer to Peer, P2P). And Instant Messaging (IM) can be based on TCP or UDP protocols.

In the data stream transmission process of the TCP protocol, the application layer sends a data stream represented by an 8-bit byte for inter-network transmission to the TCP layer, and then the TCP layer partitions the data stream into a segment of a suitable length to generate a result packet. The length of the segment is typically limited by the Maximum Transmission Unit (MTU) of the data link layer of the network to which the computer is connected. The TCP layer transmits the result packet to the IP layer, and the IP layer transmits the packet to the TCP layer of the receiving device through the network. For the mobile network, the process needs to be implemented by wireless transmission. The receiving device returns a confirmation of the required packet that has been successfully received. (Acknowledgement, ACK), for mobile networks, the process needs to be implemented by wireless transmission; if the transmitting device does not receive an acknowledgment within a reasonable Round-Trip Time (RTT), then the corresponding packet is It is assumed that it has been lost and will be retransmitted. In this process, the ratio of the uplink and downlink data packets (TCP acknowledgement packet to TCP packet) of the TCP protocol according to the current network data will reach 1:1.3.

In the existing mobile network, the wireless resources are scarce. However, the ratio of the number of uplink and downlink data packets of the TCP protocol is 1:1.3, so the requirements for the uplink and downlink bandwidth are very high, and the data rate of the TCP protocol is low, and the user has a low transmission rate. Poor experience.

Summary of the invention

The embodiment of the invention provides a data transmission method and device. The function of the TCP confirmation packet is realized by the RLC confirming the transmission of the packet in the air interface. Since the Radio Link Control (RLC) confirms that the resources occupied by the packet in the air interface transmission are much smaller than the TCP acknowledgement packet, the transmission rate of the data stream of the TCP protocol can be improved.

In one aspect, the invention provides a method of data transmission. The method includes: the eNB establishes, by the eNB, a connection based on a transmission control protocol TCP and a radio link layer control RLC protocol; the eNB sends data processed according to the TCP and the RLC protocol to the UE, where the data to be sent according to the TCP processing is obtained by one or more The TCP data packet is processed according to the RLC protocol to obtain one or more RLC Protocol Data Units (PDUs); the eNB determines a mapping relationship between the identifier of the TCP data packet and the identifier of the RLC PDU. The eNB receives an RLC status report sent by the UE, where the RLC status report includes an identifier of the RLC PDU, where the RLC status report is used to indicate that the RLC PDU indicated by the RLC PDU identifier included by the UE is received by the UE. The eNB generates a TCP status report according to the RLC status report and the mapping relationship between the TCP packet identifier and the RLC PDU identifier, where the TCP status report is used to indicate the reception status of the TCP data packet in the UE. Through the embodiment of the present invention, the transmission of the RLC status report in the air interface can be realized, and the transmission of the TCP data packet is confirmed, which saves the wireless resource and improves the user experience.

In one possible implementation, the identification of the TCP packet includes quintuple information for the TCP packet; the identification of the RLC PDU includes the sequence number of the RLC PDU.

In another optional implementation, the mapping relationship between the identifier of the TCP packet corresponding to the foregoing determination data and the identifier of the RLC PDU specifically includes: determining a mapping relationship between the quintuple information of the TCP packet and the PDCP sequence number of the packet data convergence protocol The mapping between the packet data convergence protocol (PDCP) sequence number and the sequence number of the RLC PDU is determined. The mapping between the TCP layer and the PDCP layer and the mapping between the PDCP layer and the RLC layer can be implemented by using the embodiment of the present invention. Finally, the mapping between the TCP layer and the RLC layer is implemented.

In still another optional implementation, before the eNB receives the RLC status report sent by the UE, the method further includes: when the RLC PDU sent by the eNB to the UE reaches a threshold, when the eNB sends the next RLC PDU, A polling polling is configured on the next RLC PDU, and the polling is used to instruct the UE to return an RLC status report. The eNB can trigger the sending of the RLC status report by using the embodiment of the present invention, and can ensure that the RLC status report is faster than the TCP status report, and the user experience is higher.

In still another optional implementation, the method further includes: after sending the RLC PDU configured with the polling to the UE, after the set scheduling time, the eNB sends uplink grant information to the UE, where the uplink The link grant information is used to instruct the UE to send an RLC status report to the eNB. The intelligent scheduling can be implemented by the embodiment of the invention, so that the sending of the status report is more timely and accurate.

In still another optional implementation, the eNB generates a TCP status report according to the RLC status report and the mapping relationship between the TCP packet identifier and the PDU identifier of the RLC layer, including: when the eNB and the UE support the selective acknowledge SACK function, according to The RLC status report generates a TCP status report that supports SACK. The construction of the status report of the TCP status report supporting SACK can be realized by the present invention.

In a second aspect, the present invention provides a data transmission method. The method includes: the UE establishes a connection with the eNB according to a transmission control protocol TCP and a radio link layer control RLC protocol, where the connection is used to transmit data processed according to the TCP and the RLC protocol, where the data is processed according to the TCP. a TCP packet, which processes the TCP packet according to the RLC protocol to obtain an RLC protocol data unit PDU; after receiving the RLC protocol data unit PDU sent by the eNB, the UE sends an RLC status report to the eNB, where the RLC status report includes Determining an identifier of the RLC PDU, where the RLC status report is used to indicate a receiving situation of the RLC PDU in the UE, so that the eNB determines, according to the receiving situation of the RLC PDU in the UE, that the RLC PDU corresponds to The TCP packet is received by the UE.

In an optional implementation, before the sending the RLC status report to the eNB, the method further includes: the UE processing the RLC PDU according to a TCP and an RLC protocol, obtaining the TCP data packet, and determining, Determining a mapping relationship between an identifier of the RLC PDU and an identifier of the TCP data packet; the UE generates a TCP status report, the TCP status report includes an identifier of the TCP data packet, and the TCP status report is used to indicate the TCP a status of the data packet received by the UE; the UE generates an RLC status report according to the TCP status report and a mapping relationship between the identifier of the RLC PDU and the identifier of the TCP data packet, where the RLC status report includes An identifier of the RLC PDU, where the RLC status report is used to indicate a reception status of the RLC PDU at the UE.

In another optional implementation, after receiving the RLC protocol data unit PDU sent by the eNB, the UE sends an RLC status report to the eNB, where the RLC status report includes an identifier of the RLC PDU corresponding to the data, The RLC status report is used to indicate the receiving situation of the RLC PDU in the UE, including: after receiving the threshold of the RLC PDU sent by the eNB, the UE sends an RLC status report to the eNB, where The RLC status report includes an identifier of a corresponding RLC PDU in the threshold, and the RLC status report is used to indicate a reception status of the corresponding RLC PDU in the threshold at the UE.

In still another optional implementation, the identifier of the TCP data packet includes quintuple information of the TCP data packet; the identifier of the RLC PDU includes a sequence number of the RLC PDU, and the TCP corresponding to the data is determined. The mapping relationship between the identifier of the data packet and the identifier of the RLC PDU includes: determining a mapping relationship between the quintuple information of the TCP data packet and the PDCP sequence number of the packet data convergence protocol; Determining a mapping relationship between the PDCP sequence number and a sequence number of the RLC PDU.

In another optional implementation, before the sending the RLC status report to the eNB, the method further includes: receiving, by the UE, an RLC PDU sent by the eNB, where the RLC PDU is configured with a polling poll; The eNB sends an RLC status report, where the RLC status report includes an identifier of the RLC PDU, where the RLC status report is used to indicate a reception status of the RLC PDU in the UE, so that the eNB is according to the RLC Determining, by the PDU in the receiving situation of the UE, that the TCP data packet corresponding to the RLC PDU is received by the UE, the UE sends an RLC status report to the eNB according to the polling, where the RLC status report includes The received configuration is configured with the polled RLC PDU to the identifier of the plurality of RLC PDUs received between the last received RLC PDUs configured with polling, and the RLC status report is used to indicate that the multiple RLC PDUs are in the The receiving situation of the UE is such that the eNB determines, according to the receiving situation of the multiple RLC PDUs in the UE, the reception status of the TCP data packet corresponding to the multiple RLC PDUs in the UE.

In another optional implementation, before the sending the RLC status report to the eNB, the method further includes: after the UE receives the RLC PDU configured with polling, after the set scheduling time, the UE receives the The uplink grant information sent by the eNB is used to indicate that the RLC status report is sent to the eNB.

In a third aspect, an embodiment of the present invention provides a sending device, which can implement the steps performed by the sending device in the foregoing first aspect and optionally in the method. The device can be implemented in hardware or implemented in hardware. The hardware or software includes one or more modules corresponding to the functions described above.

In a fourth aspect, an embodiment of the present invention provides a receiving device, which is capable of implementing the steps performed by the receiving device in the foregoing second aspect and optionally in the method. The device can be implemented in hardware or implemented in hardware. The hardware or software includes one or more modules corresponding to the functions described above.

In a fifth aspect, an embodiment of the present invention provides a sending device, where the device includes a transceiver, a processor, and a memory. The transceiver is for interacting with the receiving device, and may include a receiver and a transmitter; the memory is used to store programs and data. The processor implements the steps performed by the transmitting device in the first aspect described above, and optionally in the implementation, by executing a program stored in the memory.

In a sixth aspect, an embodiment of the present invention provides a receiving device. The receiving device includes a transceiver, a processor, and a memory. Each module can be connected via a bus. The transceiver is used to communicate with the transmitting device. The memory is used to store program code as well as data. The processor performs the operational steps of the receiving device in the second aspect and optionally in accordance with the program instructions stored in the memory.

In a seventh aspect, an embodiment of the present invention provides a computer storage medium for storing computer software instructions for use in the above-described transmitting device, including a program for performing the above first aspect and optionally implementing the program.

In an eighth aspect, an embodiment of the present invention provides a computer storage medium for storing computer software instructions for use in the above-mentioned receiving device, including a program designed to perform the second aspect described above and optionally implemented.

In a ninth aspect, an embodiment of the present invention provides a data transmission system. The data transmission system includes a transmitting device and a receiving device, wherein the transmitting device is the transmitting device in the fifth aspect; and the receiving device is the receiving device in the sixth aspect.

DRAWINGS

FIG. 1 is a schematic diagram of an application scenario;

2 is a signaling interaction diagram of a data transmission method according to an embodiment of the present invention;

FIG. 3 is an example of an embodiment of the present invention;

4 is another example provided by an embodiment of the present invention;

Figure 5 is an example of an RLC status report format;

FIG. 6 is still another example provided by an embodiment of the present invention;

Figure 7 is an example of an RLC PDU structure;

FIG. 8 is still another example provided by an embodiment of the present invention;

Figure 9 is a RLC status report delay analysis;

FIG. 10 is a schematic structural diagram of a sending device according to an embodiment of the present disclosure;

FIG. 11 is a schematic structural diagram of a receiving device according to an embodiment of the present disclosure;

FIG. 12 is a schematic structural diagram of another sending device according to an embodiment of the present disclosure;

FIG. 13 is a schematic structural diagram of another receiving device according to an embodiment of the present invention.

detailed description

As shown in FIG. 1, the embodiments of the present invention are mainly applicable to a wireless communication system, for example, LTE, LTE-A, and the like. Among them, LTE is a long-term evolution of the UMTS (Universal Mobile Telecommunications System) technical standard established by the 3GPP (The 3rd Generation Partnership Project). The TCP packet generated by the TCP server is sent by the evolved Node B (eNB) to the user equipment (User Equipment, UE) by wireless transmission. After receiving the TCP data packet sent by the eNB, the user equipment returns the confirmation information, or The UE sends a TCP packet to the eNB, and after receiving the TCP packet, the eNB returns a confirmation message.

The transmitting device according to the embodiment of the present invention is a device that sends a TCP packet, and is also a device that receives an RLC status report. The receiving device is a device that receives TCP packets and is also a device that sends RLC status reports. The eNB may send a TCP packet to the user equipment, and the user equipment may also send a TCP packet to the eNB. Therefore, the sending device may be an eNB or a user equipment, and the receiving device may be a user equipment or an eNB.

The TCP status report is used to indicate the reception status of the TCP packet at the receiving device, and may also be referred to as a TCP ACK or a TCP acknowledgement packet.

The RLC status report user indicates the reception status of the RLC PDU at the receiving device, and may also be referred to as an RLC ACK or an RLC acknowledgement packet.

The inventor of the present application found through analysis that most of the current network is medium to low load, so the downlink belt Width is not a factor, the uplink transmission becomes a bottleneck, the uplink coverage is limited, and the uplink bandwidth cannot meet the requirement of the uplink TCP acknowledgement packet rate corresponding to the downlink video data transmission rate. As a result, the downlink rate of the TCP is not as good as the User Datagram Protocol (User Datagram Protocol, UDP) Downstream rate. The invention realizes the function of the TCP confirmation packet by confirming the transmission of the packet in the air interface by the RLC. Since the RLC acknowledges that the packet occupies less resources than the TCP acknowledgment packet in the air interface transmission, the transmission rate of the data stream of the TCP protocol can be improved.

Specifically, the eNB sends a TCP packet to the user equipment as an example. The TCP packet is sent by the user equipment to the TCP server during the wireless transmission between the eNB and the user equipment, or the eNB is from the core. The TCP packet sent to the user equipment received by the Packet Switched (Packet Switched Domain) is compressed in the Packet Data Convergence Protocol (PDCP) layer (in order to improve efficiency), and then submitted. The RLC layer is divided and concatenated, and then placed in an RLC Protocol Data Unit (PDU), and then a MAC header field is added to the Media Access Control (MAC) layer to become a MAC PDU. The physical layer, the last physical layer needs to add a Cyclic Redundancy Check (CRC) header, coding, interleaving, and then convert the data into electromagnetic waves for transmission, and the eNB or user equipment recovers the TCP through the inverse operation of the above process. Packet. If it is a TCP packet of the user equipment to the TCP server, it needs to be sent by the eNB to the core network. Similarly, the TCP service. The TCP packet sent to the user equipment is transmitted to the eNB via the core network, and then sent by the eNB to the user equipment.

In the present invention, when the eNB sends a TCP packet to the user equipment or the user equipment sends a data packet to the eNB, the correspondence between the TCP layer and the RLC layer is established, and only the RLC status report is transmitted in the wireless air interface, according to the TCP layer and the RLC. The correspondence between the layers constructs a TCP status report. Due to the characteristics of the RLC acknowledgment mechanism and the size of the data packet reported by the RLC status, the size of the data packet of the RLC status report is much smaller than that of the TCP status report. Therefore, in the data transmission process between the eNB and the user equipment, the air interface resources are greatly saved, and the sensing rate is improved. And business experience. In the embodiment of the present invention, the eNB actively constructs a polling to trigger the UE to send an RLC status report, and also supports a TCP shape under the SACK function. The configuration of the state report, the eNB can reconstruct more types of TCP status reports, and can improve the downlink rate, uplink coverage, and resource saving. In addition, the uplink pre-scheduling and the downlink sensing rate of the TCP service can be improved by using the uplink pre-scheduling.

It should be noted that, in the embodiment of the present invention, the receiving device has the capability of intercepting the TCP status report and actively triggering the RLC status report.

The intercepting of the TCP status report by the receiving device may include at least the following methods:

When the receiving device identifies the TCP status report delivered by the TCP layer according to the received PDCP SDU, the PDCP PDU, or the RLC SDU, the receiving device intercepts the TCP status report and does not generate the RLC PDU to the lower layer.

The receiving device triggers the RLC status report to be sent at least in the following manner:

In the first mode, when the RLC layer correctly receives the RLC service data unit (SDU) sent by the peer end to the PDCP layer, it triggers sending an RLC status report to the sending device, where the RLC status report is generated according to the RLC SDU.

In the second mode, when the RLC layer receives the TCP status report sent by the local TCP layer, it triggers sending an RLC status report to the sending device.

It should be noted that, by intercepting the TCP status report by the receiving device, the receiving device can implement the function of the TCP status report by using only the transmission of the RLC status report. The transmitting device needs to be able to determine the correspondence between the RLC status report of the receiving device and the TCP packet to generate a TCP status report according to the received RLC status report.

In the embodiment of the present invention, whether the receiving device intercepts the TCP status report or the sending device generates a TCP status report according to the RLC status report, the mapping relationship between the RLC PDU identifier and the identifier of the TCP data packet needs to be implemented.

The determining the mapping relationship between the RLC PDU identifier and the identifier of the TCP packet is as follows:

When the RLC layer of the receiving device correctly receives the RLC SDU sent by the sending device and sends the RLC SDU to the PDCP layer, the correspondence between each RLC PDU identifier and the identifier of the TCP packet is recorded, and the corresponding relationship is generated. Map list.

The sending device can receive the TCP packet sent by the TCP layer at the RLC layer, and when the RLC SDU is generated according to the TCP packet, record the correspondence between each RLC PDU identifier and the identifier of the TCP packet, and generate a mapping list.

Specifically, the correspondence between the RLC PDU identifier and the identifier of the TCP packet may be a correspondence between the RLC PDU sequence number and the quintuple of the TCP packet.

The mapping between the TCP layer and the RLC layer can be implemented by using a TCP layer and a PDCP layer and a PDCP layer and an RLC layer mapping method. The specific description is as follows:

The PDCP layer maintains the mapping relationship between the quintuple of the TCP packet and the PDCP sequence number.

The RLC layer maintains a mapping relationship between the PDCP sequence number and the RLC PDU sequence number.

The two-layer mapping finally realizes the mapping relationship between the quintuple of the TCP packet and the RLC PDU sequence number.

In another embodiment of the present invention, the sending device may trigger the receiving device to send an RLC status report, which ensures timely reporting of the RLC status report. The sending device needs to maintain a mapping relationship between the identifier of the RLC PDU and the identifier of the TCP packet.

Specifically, the sending device may determine, according to the mapping relationship between the RLC PDU identifier and the TCP packet identifier, that when a certain number of TCP data packets are sent, when the RLC PDUs corresponding to the certain number of data packets are sent, in the RLC PDUs. The polling is configured on the last RLC PDU. After receiving the RLC PDU configured with polling, the receiving device sends an RLC status report to the sending device. In this process, intelligent pre-scheduling can also be performed.

It should be appreciated that the RLC includes three types of RLC entities: a transparent mode TM RLC entity, a non-acknowledged mode UM RLC entity, and an acknowledge mode AM RLC entity. The AM RLC entity of the receiving device reports a status report RLC status report to the AM RLC entity of the transmitting device, the RLC status reporting confirmation information about the received AMD (AMData, acknowledgment mode data) PDU for the transmitting device The AM RLC entity performs corresponding processing according to the confirmation information, thereby ensuring the orderly transmission and the normal operation of the system. The acknowledgement information returned by the AM RLC entity of the receiving device to the AM RLC entity of the transmitting device may be a confirmation message regarding an AMD PDU. It can also be the confirmation information of multiple AMD PDUs.

The embodiments of the present invention are further described below in conjunction with the flow of data transmission. As shown in FIG. 2, the method may include the following steps:

Step 210: The transmitting device establishes a wireless connection with the receiving device, and the wireless connection is established based on a transmission control protocol TCP and a radio link layer control RLC protocol and the like.

When the transmitting device and the receiving device transmit data, a wireless connection needs to be established, and the data transmitted through the wireless connection can be correctly received.

In the wireless communication of the embodiment of the present invention, the data is transmitted according to the TCP and the RLC protocol, and the data packet of the TCP layer needs to be transmitted through the RLC layer, and when the connection is established, the sending device and the receiving device are required to be established. The TCP-based connection and the RCL connection, in other words, the transmitting device and the user equipment need to establish a connection between the TCP layer of the transmitting device and the TCP layer of the receiving device and the RLC layer of the transmitting device and the RLC layer of the receiving device.

In addition, the data packet of the TCP layer may be from a TCP server, a core network device, or a user equipment, etc., for example, the user equipment uses streaming media provided by a TCP server, web browsing, Email (email), Filehosting (file access). When a service such as a social network service (SNS) is used, the user equipment obtains service data from the TCP server, and the service data is generally transmitted to the user equipment in the form of a TCP packet according to TCP processing, or the user equipment is also User data is uploaded to the TCP server, and the user data is generally transmitted to the TCP server in the form of TCP packets according to TCP processing.

Step 220: The sending device sends a TCP data packet to the receiving device by using a wireless connection. Specifically, the sending device processes the TCP data packet according to the RLC protocol to obtain one or more RLC PDUs, and the sending device sends the RLC PDU to the receiving device. The RLC PDU is a data unit that is transmitted by the RLC layer between the sending device and the receiving device. The transmitting device may configure a polling polling on the next RLC PDU when the number of the RLC PDUs sent by the sending device to the receiving device reaches a threshold, and the polling is used to indicate that the UE returns the RLC status report. . The threshold of the number of RLC PDUs may be set according to actual needs, for example, according to the RLC status report and the RLC PDU. The ratio can be set to 2.

Wherein each TCP data packet has a TCP data packet identifier, and the TCP data packet identifier can identify the TCP data packet to enable the transmitting device and the receiving device to identify the TCP data packet, such as quintuple information of the TCP data packet. Each RLC PDU has an RLC PDU identification that can identify the RLC PDU to enable the transmitting device and the receiving device to identify the RLC PDU, such as the sequence number of the RLC PDU. Each TCP packet corresponds to one or more RLC PDUs.

The transmitting device can determine the mapping relationship between the identifier of the TCP packet and the identifier of the RLC PDU.

For example, as shown in FIG. 3, in the process shown in FIG. 3, the TCP layer of the transmitting device receives the IP data packet sent by the TCP server, and after parsing the TCP data packet, the TCP data packet is transmitted to the PDCP layer. The PDCP layer compresses and configures the PDCP sequence number. At this time, the PDCP layer of the transmitting device records the mapping relationship between the quintuple of the TCP packet and the PDCP sequence number.

The PDCP layer transmits the compressed TCP data packet to the RLC layer of the transmitting device, and the RLC layer generates an RLC PDU according to the compressed TCP data packet, the RLC PDU includes the RLC PDU sequence number, and the RLC layer of the transmitting device records the PDCP sequence number and the RLC. Mapping relationship between PDU serial numbers.

After the RLC layer transmits the RLC PDU to the MAC for further processing by the MAC layer, electromagnetic waves generated by the physical layer are transmitted to the receiving device.

Step 230: The receiving device receives the TCP data packet sent by the sending device.

The receiving device receives the RLC SDU sent by the sending device, processes the RLC PDU according to the RLC protocol, and processes the RLC PDU according to the TCP to obtain a TCP packet.

In addition, the receiving device may also determine a mapping relationship between the identifier of the TCP packet and the identifier of the RLC PDU.

As shown in FIG. 4, in an example, the RLC layer of the receiving device receives the data transmitted by the MAC layer, parses the TCP data packet, transmits the TCP data packet to the PDCP layer, and determines the PDCP sequence number and the RLC PDU sequence. The mapping relationship of the identifier of the number, the PDCP layer decompresses the TCP packet sent by the RLC, sends the decompressed TCP packet to the TCP layer, and determines the mapping relationship between the TCP packet quintuple and the PDCP sequence number. TCP layer parsing is obtained in the TCP packet data.

In another example, the receiving device processes the received data according to the RLC protocol and TCP to obtain data in the TCP packet. This process does not require determining the mapping relationship between the TCP packet identifier and the RLC PDU identifier. In the process of receiving the TCP packet, the sending device sends an indication of the RLC status report feedback to the receiving device, for example, carrying the polled RLC PDU.

Step 240: The receiving device sends an RLC status report to the sending device.

The receiving device may generate a TCP status report, but does not send, and after the preset condition is reached, sends an RLC status report, so that the existing process can be changed at a minimum cost to implement the present invention. For example, the generated TCP status report is intercepted at the PDCP layer or the RLC layer.

The receiving device may also not generate a TCP status report, and directly send the RLC status report after the preset condition is reached.

For the generation and transmission of the RLC status report, after the RLC layer of the receiving device determines that the TCP data packet is correctly received, according to the mapping relationship between the RLC PDU sequence number and the TCP packet quintuple, it is determined which RLC PDUs corresponding to the downlink TCP packet are Correctly received, the ACK_SN field in the RLC status report fills in the next RLC PDU sequence number to be received, and sends the RLC status report to the sending device. As shown in FIG. 5, the RLC status report format is as follows. The CPT: Control PDU category indication is used to indicate the category of the RLC PDU. ACK_SN: A sequence number used to indicate the next PDU that did not receive the ACK information and did not indicate a loss in the status report. E1: A combined field for indicating whether a group of NACK_SN and E1/E2 is followed. E2: A combined field used to indicate whether or not it is accompanied by a set of SOstart and SOend. SOstart and SOend jointly indicate an AMD PDU that has been detected as lost in the AM RLC receiving portion, where SOstart indicates the starting position of the lost portion in the AMD PDU, and SOend indicates the ending position of the lost portion in the AMD PDU, both in bytes. For the unit. NACK_SN: Used to indicate the sequence number of the most recently detected lost AMD PDU. All PDUs with the ACK_SN as the line are correctly received except for the RCL PDUs or segments that have failed to be listed in this status report.

As shown in FIG. 6, in one example, the TCP layer of the receiving device correctly receives the TCP data. After the packet, a TCP status report is sent to the PDCP layer. The PDCP layer can intercept the TCP status report, or it can be transmitted to the RLC layer by the PDCP layer, and intercepted by the RLC layer.

In another example, after receiving the indication of the RLC status report feedback sent by the sending device (the RLC PDU carrying the polling), the receiving device sends an RLC status report to the sending device according to the indication of the RLC status report feedback. It should be noted that the embodiment of the present invention may not generate a TCP status report on the receiving device.

In yet another example, the receiving device can report to the transmitting device RLC status when the preset condition is reached.

In still another example, when the RLC layer of the receiving device determines that the number of correctly received TCP packets reaches a threshold, the RLC status report is sent to the transmitting device to notify that all RLC PDUs of the TCP packets corresponding to the threshold are correctly received. . For example, in general, the TCP packet and the TCP status report are 2:1, and the receiving device can report the status to the transmitting device RLC when the two TCP packets are correctly received.

The RLC layer of the receiving device can determine that the TCP packet has been correctly received at least by:

In the first mode, the RLC layer of the receiving device correctly receives the RLC SDU sent by the sending device.

In the second mode, the RLC layer of the receiving device receives the TCP status report of the TCP layer transmission of the receiving device.

Step 250: The sending device receives the RLC status report sent by the receiving device.

When the sending device receives the status report sent by the receiving device, the downlink scheduler and the uplink scheduler may coordinate to implement intelligent pre-scheduling. Specifically, after the transmitting device sends the RLC PDU configured with the polling to the receiving device, the sending device sends uplink grant information to the receiving device after the set scheduling time, where the uplink grant information is used to indicate that the receiving device sends the uplink grant information. The device sends an RLC status report. The set scheduling time may be determined according to actual conditions, for example, according to channel quality, delay, and other information.

Step 260: The sending device according to the RLC status report and the TCP packet identifier and the RLC PDU The mapping relationship of the identifier determines the reception status of the TCP packet at the receiving end according to the RLC status report. For example, a TCP status report is generated according to the RLC status report and the mapping relationship between the TCP packet identifier and the RLC PDU identifier, and the TCP status report is used to indicate the reception status of the TCP data packet at the receiving device.

The RLC layer of the sending device receives the RLC status report sent by the receiving device, that is, the acknowledgment information that the RLC layer of the receiving device correctly receives the downlink RLC PDU, and the sending device determines that the mapping relationship is correct according to the mapping relationship between the RLC PDU identifier and the identifier of the TCP packet. The received TCP packet identifier generates a TCP status report.

Specifically, the RLC layer determines the correctly received PDCP sequence number according to the RLC status report and the mapping relationship between the PDCP sequence number and the RLC PDU sequence number maintained by the RLC, and sends the PDCP sequence number to the upper layer PDCP layer, and the PDCP layer maintains the TCP according to the maintenance. The mapping relationship between the packet quintuple and the PDCP sequence number generates a TCP status report and sends it to the TCP layer.

For example, the eNB side PDCP layer refers to the TCP packet header information in the relationship list to construct a UL TCP status report packet to be delivered to the upper layer TCP Proxy (proxy). The TCP proxy on the eNB side sends the TCP status report uploaded by the PDCP layer to the TCP layer of the server.

In addition, when the sending device generates the TCP status report according to the RLC status report sent by the receiving device, the acknowledgment sequence number needs to be constructed, and the sending sequence number needs to be updated in real time according to the information in the TCP header with the uplink service data sent by the UE.

In one example, when generating a TCP status report, it is specifically configured in the format of a general TCP status report (there is no SACK field in the TCP option), or is constructed in a TCP status report format that supports the SACK function (with the SACK field in the TCP option). The device and the receiving device determine the SACK function support. The SACK function can be determined by the sending device and the receiving device when the connection is established according to the TCP. When both the sending device and the receiving device support the SACK function, the sending device generates a TCP status report in a format that supports the SACK function. Otherwise, the TCP status report is generated according to the general format. .

Through the embodiment of the present invention, the transmission of the RLC status report in the air interface can be realized, and the TCP is implemented. The transmission of the data packet is confirmed, which saves wireless resources and improves the user experience. The embodiment of the present invention can use the active acknowledgment mechanism of the RLC layer to ensure that the RLC status report is faster than the TCP status report. The present invention does not affect the RLC layer's own retransmission mechanism based on the active use of the RLC acknowledgment mechanism. . The receiving device can also actively intercept the TCP status report and utilize the uplink pre-scheduling, which greatly reduces the requirement for the uplink rate at the same downlink rate, saves the consumption of air interface resources, and improves the uplink coverage and user experience.

In one embodiment, the RLC may rebuild due to data transfer. Since the RLC layer maintains the mapping relationship between the PDCP SN and the RLC PDU SN, when the RLC re-establishment occurs, it means that the entity needs to re-maintain new parameters. Since these PDCP SNs are not retransmitted, the PDCP SN corresponding to the PDUs that are not confirmed by the RLC layer and the SDUs that are not sent out are required to be fed back to the PDCP layer before the reconstruction.

During the RLC re-establishment process, the AM RLC layer needs to perform the following operations:

The receiving device needs to initialize related state variables and timers;

Discard all RLC control PDUs;

If possible, reassemble the reordered RLC PDUs into RLC SDUs and provide the RLC SDUs in order to the upper layer (PDCP layer). Discard any remaining PDUs that cannot be reassembled into RCL SDUs;

The sending device needs to discard all RLC SDUs and RLC PDUs.

In another embodiment, at the transmitting device, the PDCP layer may feed back to the TCP layer the TCP status report generated according to the RLC status report when the preset condition is reached.

Specifically, when the PDCP layer of the sending device determines that the TCP layer transmits the TCP packet from the serial number greater than the expected received sequence number (indicating that packet loss or delay occurs), the TCP status report is immediately sent, the TCP The status report indicates that the last sequence number is received in order, so that the TCP layer determines that packet loss or delay occurs according to the TCP status report, and the TCP layer retransmits the TCP packet that has lost or retransmitted.

When the received data is the data that you expect to receive:

If the maximum number of delayed TCP status reports is reached (by default, the ratio of TCP packets to TCP status reports is 2, the default is 2). The TCP status report is sent immediately, and FIN|ACK needs to be sent during the connection release process.

If the maximum delayed TCP status report number is not reached, it is determined whether the timer for delaying the TCP status report is started, and if not, the timer is started.

If the Delay timeout (for example, the timer can be set to 0.2s), the TCP status report is sent immediately.

When the PDCP layer finds that the sequence number of the downlink TCP packet is smaller than the expected sequence number, and considers this to be a duplicate packet, the duplicate packet is directly discarded. Wherein, the repeated packet here means that the sending device retransmits a TCP packet, and the TCP packet has been correctly received by the receiving device before.

It should also be noted that when the PDCP layer finds that the sequence number of the downlink TCP packet is larger than the expected sequence number (indicating that packet loss or delay occurs), the SACK in the SYN packet sent by the two parties according to the TCP connection is SACK in the TCP option. Whether the function supports the determination. When generating the TCP status report, it is constructed according to the format of the general TCP status report (there is no SACK field in the TCP option), or is constructed according to the TCP status report format that supports the SACK function (the SACK field is included in the TCP option). When both the sending device and the receiving device support the SACK function, the sending device generates a TCP status report in the format that supports the SACK function. Otherwise, the TCP status report is generated in the normal format.

The following is an example of the filling of the ACK sequence number and the SACK option when the TCP status report is constructed in different situations.

The ratio of TCP packets and TCP status reports is assumed to be 1:1 in Table 1-4.

Table 1 shows the TCP packets from the TCP server to the eNB in order, without packet loss.

Table 2 shows the TCP packets from the TCP server to the eNB in order, without packet loss.

Table 3: Packet loss from the TCP server to the eNB TCP packet

Table 4: Out of order of TCP packet data from TCP server to eNB

It is noted that, in the sending device, when the RLC status report of the receiving device is received, and the RLC status report feeds back an RLC PDU error, the RLC retransmission is not performed at this time, and the RLC only when the MAC indication reaches the maximum number of HARQ retransmissions. The RLC retransmission is triggered again.

The embodiment of the present invention generates a TCP status report by using the RLC status report, and the RLC status report may not be used for the RLC retransmission mechanism to avoid unnecessary resource consumption due to RLC retransmission.

As shown in FIG. 7, FIG. 7 is a schematic structural diagram of an RLC PDU, wherein the meanings of the fields in the figure are as follows. SN: Serial number indicating the serial number of the corresponding PDU. FI: Indicates whether a PDU is divided at the beginning or end of the data field. E: Extended bit. R1: Reserved field. LI: length indication field, Indicates the length of the byte in the data field. D/C: A data/control indication indicating whether the PDU is a data PDU or a control PDU. RF: A segmentation indication to indicate whether it is a PDU or a PDU segment. P: A polling indication bit indicating whether the sender of the AMRLC entity needs to send a status report to the peer entity.

The sending device instructs the receiving device to feed back the RLC status, which may be specifically as follows: The sending device sets the P field to 1, and the P field indicates that the receiving device sends the RLC status report.

According to the general TCP packet and the TCP status report is a 2:1 relationship, polling can be configured on the last RLC PDU sent every two TCP packets, the polling instructs the receiving device to send an RLC status report.

Specifically, the parameter t-StatusProhibit (timer) of the receiving device RLC layer controls the actual transmission time of the RLC status report. The t-StatusProhibit is set smaller and the receiving device sends the RLC status report with a minimum time granularity. For example, set the timer to 0ms.

The parameter t-Reordering of the receiving device RLC layer detects the out-of-order packet received by the RLC PDU at the receiving device, but if the timer expires, the corresponding RLC PDU is lost, and the VR (MS) is updated. Therefore, the timely update of the VR (MS) ensures that the RLC status report indicates whether or not the correct timeliness is received. Therefore, setting the timer to 0ms indicates that the timer always times out. Once the receiving device receives a downlink subframe, the RLC layer can immediately determine whether it is correctly received.

When an RLC status report is triggered to be sent, if t-StatusProhibit is not running, a status protocol data unit (STATUS PDU) is constructed and passed to the MAC at the first transmission opportunity indicated by the MAC.

When the polling TTI n is configured, the uplink intelligent pre-scheduling is triggered, and the UL grant is sent at the time of TTI n+2 to let the receiving device send the RLC status report in time.

Delay analysis of whether the RLC PDU is correctly received by the RLC status report:

As shown in FIG. 8, if the downlink is initially transmitted at time n-2 and polling is configured in the RLC PDU, the data packet is solved at time n.

For the UL grant (up line grant) at time n, the RLC status report is grouped into the MAC PDU at time n+1.

The n+k time is sent to the transmitting device through the air interface.

At the time of n+k+2, the RLC status report is released, and the transmitting device can recognize whether the transmission of n-2 is correct through the RLC.

As can be seen from Figure 8, by means of the RLC status report, the scheduling can get the packet reception correct information at time k+4 (the first uplink subframe with K>=4). That is to say, when k=4, it takes at least 8ms from the downlink subframe scheduling to the RLC to successfully solve the RLC status report.

If the uplink does not perform pre-scheduling, the delay of the UL grant will be caused, and the maximum delay will be 9ms. As shown in Figure 9, the analysis is as follows:

If the downlink initial transmission is at time n-2, then the data packet is solved at time n.

The uplink sends the RLC status report in cycles of 5ms (the receiving device buffer is empty and not triggered by the UL grant), there is no UL grant at time n, and the RLC status report is triggered at time n+5.

The N+5+4 time sending device sends the UL grant.

It can be seen that the time when the UL grant is obtained when the uplink is not pre-scheduled is 9 ms later than the time when the uplink intelligent pre-scheduling obtains the UL grant.

Whether the uplink scheduler triggers intelligent pre-scheduling at time n+2 at time n, the judgment process is as follows:

If UeBufferSize==0//UeBufferSize is the size of the receiving device BufferSize maintained by the sending device

{trigger intelligent pre-scheduling, issuing UL grant at time n+2;

MCS in the UL grant = MCS level -2 order of historical SINR conversion to further reduce its bit error rate;

The PRB Num is determined by the RLC status report size (typically 4Byte RLC Status Report + 600 bit BSR + 3 Byte MAC header) and Modulation and Coding Scheme (MCS).

}else//UeBufferSize! =0

{Do not trigger intelligent pre-scheduling, but can do compensation scheduling. Adjust the number of PRBs in the UL grant for small UeBufferSize cases.

If UeBufferSize<10Byte//Adjust the number of PRBs in the UL grant

{

The PRB Num is determined by the amount of data to be transmitted and the history MCS.

The amount of data to be transmitted = UeBufferSize + RLC status report size (usually 4Byte)

}

}

FIG. 10 is a schematic structural diagram of a sending device according to an embodiment of the present invention. As shown in FIG. 10, the sending device specifically includes:

The RLC processing unit 1001 is configured to process the transmission control protocol TCP data packet according to the radio link layer control RLC protocol to obtain at least one RLC protocol data unit PDU;

a mapping relationship determining unit 1002, configured to determine a mapping relationship between an identifier of the TCP data packet and an identifier of the at least one RLC PDU;

The sending unit 1003 is configured to send the at least one RLC PDU to the receiving device, when the number of RLC PDUs sent by the sending device to the receiving device reaches a threshold, when the sending device sends the next RLC PDU, Configuring polling polling on the next RLC PDU, where the polling is used to instruct the receiving device to return an RLC status report;

The receiving unit 1004 is configured to receive, by the receiving device, at least one RLC status report, where one of the at least one RLC status report includes an identifier of one or more of the at least one RLC PDU, the at least one RLC status One of the reports is used to indicate reception of one or more of the at least one RLC PDU at the receiving device;

The receiving status determining unit 1005 is configured to determine, according to the at least one RLC status report and the mapping relationship between the TCP data packet identifier and the at least one RLC PDU identifier, the reception status of the TCP data packet at the receiving device.

Optionally, the identifier of the TCP packet includes the quintuple information of the TCP packet; the identifier of the RLC PDU includes the sequence number of the RLC PDU, and the mapping relationship determining unit 1002 is further configured to:

Determining the quintuple information of the TCP data packet and the packet data convergence protocol PDCP serial number Mapping relations;

Determining a mapping relationship between the PDCP sequence number and a sequence number of the at least one RLC PDU.

Optionally, after sending the RLC PDU configured with the polling to the receiving device, the sending unit 1003 is further configured to send, to the receiving device, uplink grant information, where the uplink is sent. The authorization information is used to instruct the receiving device to send an RLC status report to the sending device.

Optionally, the receiving state determining unit 1005 is further configured to: when the sending device and the receiving device support the selective acknowledge SACK function, generate a TCP status report that supports SACK according to the at least one RLC status report.

FIG. 11 is a schematic structural diagram of a receiving device according to an embodiment of the present invention. As shown in FIG. 11, the receiving device specifically includes:

The receiving unit 1101 is configured to receive an RLC protocol data unit PDU sent by the sending device, where the polling poll is configured on the RLC PDU;

The sending unit 1102 is configured to send, to the sending device, an RLC status report according to the indication of the polling, where the RLC status report includes an identifier of at least one RLC PDU, where the RLC status report is used to indicate that the at least one RLC PDU is The receiving device receives the situation, so that the sending device determines, according to the receiving situation of the at least one RLC PDU in the receiving device, the receiving situation of the TCP data packet corresponding to the RLC PDU at the receiving device.

Optionally, it also includes:

The RLC processing unit 1103 is configured to process the at least one RLC PDU according to the RLC protocol, obtain a TCP data packet, and determine a mapping relationship between the identifier of the at least one RLC PDU and the identifier of the TCP data packet;

a TCP status report generating unit 1104, configured to generate a TCP status report, where the TCP status report includes an identifier of the TCP data packet, where the TCP status report is used to indicate a reception status of the TCP data packet at the receiving device;

An RLC status report generating unit 1105, configured to report according to the TCP status, and the Generating an RLC status report by using a mapping relationship between an identifier of the one RLC PDU and an identifier of the at least one TCP data packet, where the RLC status report includes an identifier of the RLC PDU, where the RLC status report is used to indicate the RLC PDU The reception situation at the receiving device.

Optionally, the identifier of the at least one RLC PDU includes:

The received configuration has the identity of the polled RLC PDU to the last received RLC PDU received between the RLC PDUs configured with polling.

Optionally, the receiving unit 1101 is further configured to:

After receiving the RLC PDU configured with the polling, the receiving device receives the uplink grant information sent by the sending device, where the uplink grant information is used to indicate the location The sending device sends an RLC status report.

FIG. 12 is a schematic structural diagram of another sending device according to an embodiment of the present invention. As shown in FIG. 12, the sending device specifically includes: a receiver 1201, a transmitter 1202, a processor 1203, and a memory 1204. Individual modules can be connected via bus 1205.

The receiver 1201 and the transmitter 1202 are configured to support sending and receiving information between the sending device and the receiving device in the foregoing embodiment. For example, the receiver 1201 and the transmitter 1202 may be radio frequency circuits, and may support between the sending device and the receiving device. Wireless communication. During communication between the transmitting device and the receiving device, the data and signaling messages are processed by the processor 1203 and transmitted by the transmitter 1202 to the receiving device. The signal from the receiving device is received via the receiver 1201 and processed by the processor 1203 to obtain data and signaling information transmitted or forwarded by the receiving device. The processor 1203 also performs the processes involved in the transmitting device of Figures 2-4 and 6 and/or other processes for the techniques described herein. The memory 1204 is used to store program codes and data of the terminal.

FIG. 13 is a schematic structural diagram of another receiving device according to an embodiment of the present invention. As shown in FIG. 12, the device specifically includes: a receiver 1301, a transmitter 1302, a processor 1303, and a memory 1304. Individual modules can be connected via bus 1305.

The receiver 1301 and the transmitter 1302 are configured to support sending and receiving information between the receiving device and the sending device in the foregoing embodiment. For example, the receiver 1301 and the transmitter 1302 may be radio frequency circuits. Supports communication between the transmitting device and the receiving device. During communication between the transmitting device and the receiving device, the data and signaling messages are processed by the processor 1303 and transmitted by the transmitter 1302 to the transmitting device. The signal from the transmitting device is received via the receiver 1301, and processed by the processor 1303 to obtain data and signaling information transmitted or forwarded by the transmitting device. The processor 1303 also performs the processes involved in the receiving device of Figures 2-4 and 6 and/or other processes for the techniques described herein. The memory 1304 is used to store program codes and data of the profile download server.

It should be understood that, in the foregoing embodiment of the present invention, the processor may be a central processing unit (CPU), and may be other general-purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, etc. The general purpose processor may be a microprocessor or the processor or any conventional processor or the like.

The memory can include read only memory and random access memory, store program code, and provide instructions and data to the processor.

The communication bus may include a power bus, a control bus, and a status signal bus in addition to the data bus. However, for the sake of clarity, the various buses are labeled as communication buses in the figures.

A person skilled in the art should further appreciate that the elements and algorithm steps of the various examples described in connection with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both, in order to clearly illustrate hardware and software. Interchangeability, the composition and steps of the various examples have been generally described in terms of function in the above description. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods for implementing the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present invention.

It will be understood by those skilled in the art that all or part of the steps of implementing the above embodiments may be performed by a program, and the program may be stored in a computer readable storage medium, which is non-transitory ( English: non-transitory) media, such as random access memory, read-only memory, flash memory, hard disk, solid state disk, tape (English: magnetic Tape), floppy disk (English: floppy disk), optical disc (English: optical disc) and any combination thereof.

The above is only a preferred embodiment of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily think of changes or within the technical scope disclosed by the present invention. Alternatives are intended to be covered by the scope of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims (16)

1. A data transmission method, comprising:

   The transmitting device processes the transmission control protocol TCP data packet according to the radio link layer control RLC protocol to obtain at least one RLC protocol data unit PDU;

   Determining, by the sending device, a mapping relationship between an identifier of the TCP data packet and an identifier of the at least one RLC PDU;

   The sending device sends the at least one RLC PDU to the receiving device, when the number of RLC PDUs sent by the sending device to the receiving device reaches a threshold, when the sending device sends the next RLC PDU, under the Polling polling is configured on an RLC PDU, where the polling is used to instruct the receiving device to return an RLC status report;

   Receiving, by the sending device, at least one RLC status report sent by the receiving device, where one of the at least one RLC status report includes an identifier of one or more of the at least one RLC PDU, where the at least one RLC status report is One for indicating reception of one or more of the at least one RLC PDU at the receiving device;

   The transmitting device determines, according to the at least one RLC status report and the mapping relationship between the TCP data packet identifier and the at least one RLC PDU identifier, the reception status of the TCP data packet at the receiving device.
2. The method according to claim 1, wherein the identifier of the TCP packet includes quintuple information of the TCP packet; the identifier of the RLC PDU includes a sequence number of the RLC PDU, and the transmitting device determines the TCP data The mapping relationship between the identifier of the packet and the identifier of the at least one RLC PDU includes:

   The sending device determines a mapping relationship between the quintuple information of the TCP data packet and a packet data convergence protocol PDCP sequence number;

   The transmitting device determines a mapping relationship between the PDCP sequence number and a sequence number of the at least one RLC PDU.
3. The method according to claim 1 or 2, further comprising: After the receiving device sends the RLC PDU configured with the polling, the sending device sends uplink grant information to the receiving device, where the uplink grant information is used to indicate that the receiving device is located The sending device sends an RLC status report.
4. The method according to any one of claims 1 to 3, wherein the transmitting device determines the according to the at least one RLC status report and a mapping relationship between the TCP packet identifier and at least one RLC PDU identifier. The reception of the TCP packet at the receiving device includes:

   When the transmitting device and the receiving device support the selective acknowledge SACK function, generate a TCP status report supporting SACK according to the at least one RLC status report.
5. A data transmission method, comprising:

   Receiving, by the receiving device, an RLC protocol data unit PDU sent by the sending device, where the polling poll is configured on the RLC PDU;

   Sending, by the receiving device, an RLC status report to the sending device according to the indication of the polling, where the RLC status report includes an identifier of at least one RLC PDU, where the RLC status report is used to indicate that the at least one RLC PDU is in the The receiving device receives the situation, so that the sending device determines, according to the receiving situation of the at least one RLC PDU in the receiving device, the receiving situation of the TCP data packet corresponding to the RLC PDU at the receiving device.
6. The method according to claim 5, further comprising: before the sending the RLC status report to the sending device,

   The receiving device processes the at least one RLC PDU according to the RLC protocol, obtains a TCP data packet, and determines a mapping relationship between the identifier of the at least one RLC PDU and the identifier of the TCP data packet;

   The receiving device generates a TCP status report, where the TCP status report includes an identifier of the TCP data packet, and the TCP status report is used to indicate a reception status of the TCP data packet at the receiving device;

   The receiving device generates an RLC status report according to the TCP status report and a mapping relationship between the identifier of the at least one RLC PDU and the identifier of the at least one TCP data packet. The RLC status report includes an identifier of the RLC PDU, and the RLC status report is used to indicate a reception status of the RLC PDU at the receiving device.
7. The method according to claim 5 or 6, wherein the identifier of the at least one RLC PDU comprises:

   The received configuration has the identity of the polled RLC PDU to the last received RLC PDU received between the RLC PDUs configured with polling.
8. The method according to any one of claims 5-7, further comprising: before the sending the RLC status report to the sending device,

   After receiving the RLC PDU configured with the polling, the receiving device receives the uplink grant information sent by the sending device, where the uplink grant information is used to indicate the location The sending device sends an RLC status report.
9. A transmitting device, comprising:

   An RLC processing unit, configured to process the transmission control protocol TCP data packet according to a radio link layer control RLC protocol to obtain at least one RLC protocol data unit PDU;

   a mapping relationship determining unit, configured to determine a mapping relationship between an identifier of the TCP data packet and an identifier of the at least one RLC PDU;

   a sending unit, configured to send the at least one RLC PDU to the receiving device, when the number of RLC PDUs sent by the sending device to the receiving device reaches a threshold, when the transmitting device sends the next RLC PDU, in the Polling polling is configured on the next RLC PDU, where the polling is used to instruct the receiving device to return an RLC status report;

   a receiving unit, configured to receive at least one RLC status report sent by the receiving device, where one of the at least one RLC status report includes an identifier of one or more of the at least one RLC PDU, the at least one RLC status report One of the instructions for indicating reception of one or more of the at least one RLC PDU at the receiving device;

   a receiving status determining unit, configured to determine, according to the at least one RLC status report and a mapping relationship between the TCP data packet identifier and the at least one RLC PDU identifier, that the TCP data packet is in the The receiving situation of the receiving device.
10. The transmitting device according to claim 9, wherein the identifier of the TCP packet includes quintuple information of the TCP packet; the identifier of the RLC PDU includes a sequence number of the RLC PDU, and the mapping relationship determining unit further uses to:

    Determining a mapping relationship between the quintuple information of the TCP data packet and the packet data convergence protocol PDCP serial number;

    Determining a mapping relationship between the PDCP sequence number and a sequence number of the at least one RLC PDU.
11. The transmitting device according to claim 9 or 10, wherein after transmitting the RLC PDU configured with polling to the receiving device, the sending unit is further configured to receive the received scheduling time The device sends uplink grant information, where the uplink grant information is used to instruct the receiving device to send an RLC status report to the sending device.
12. The transmitting device according to any one of claims 9 to 11, wherein the receiving state determining unit is further configured to: when the transmitting device and the receiving device support a selective acknowledge SACK function, according to the At least one RLC status report generates a TCP status report that supports SACK.
13. A receiving device, comprising: a receiving unit, configured to receive an RLC protocol data unit PDU sent by a sending device, where a polling poll is configured on the RLC PDU;

    a sending unit, configured to send, to the sending device, an RLC status report according to the indication of the polling, where the RLC status report includes an identifier of at least one RLC PDU, where the RLC status report is used to indicate that the at least one RLC PDU is in the The receiving situation of the receiving device is performed, so that the sending device determines, according to the receiving situation of the at least one RLC PDU in the receiving device, the receiving situation of the TCP data packet corresponding to the RLC PDU at the receiving device.
14. The receiving device according to claim 13, further comprising:

    An RLC processing unit, configured to process at least one RLC PDU according to an RLC protocol, obtain a TCP data packet, and determine a mapping relationship between an identifier of the at least one RLC PDU and an identifier of the TCP data packet;

    a TCP status report generating unit, configured to generate a TCP status report, where the TCP status report includes an identifier of the TCP data packet, where the TCP status report is used to indicate a reception status of the TCP data packet at the receiving device;

    An RLC status report generating unit, configured to generate an RLC status report according to the TCP status report and a mapping relationship between an identifier of the at least one RLC PDU and an identifier of the at least one TCP data packet, where the RLC status report includes An identifier of the RLC PDU, where the RLC status report is used to indicate a reception status of the RLC PDU at the receiving device.
15. The receiving device according to claim 13 or 14, wherein the identifier of the at least one RLC PDU comprises:

    The received configuration has the identity of the polled RLC PDU to the last received RLC PDU received between the RLC PDUs configured with polling.
16. The receiving device according to any one of claims 13-15, wherein the receiving unit is further configured to:

    After receiving the RLC PDU configured with the polling, the receiving device receives the uplink grant information sent by the sending device, where the uplink grant information is used to indicate the location The sending device sends an RLC status report.

Images