WO2019029350A1

WO2019029350A1 - Data processing method and related device

Info

Publication number: WO2019029350A1
Application number: PCT/CN2018/096687
Authority: WO
Inventors: 娄崇; 徐小英; 郭英昊
Original assignee: 华为技术有限公司
Priority date: 2017-08-11
Filing date: 2018-07-23
Publication date: 2019-02-14
Also published as: CN109392012B; CN109392012A

Abstract

Disclosed in embodiments of the present application are a data processing method and a related device. The method is applied at a transmitting end, and comprises: receiving at least two packet data convergence protocol (PDCP) data packets at one PDCP entity in a radio bearer; and first transmitting a PDCP data packet with a higher priority in the at least two PDCP data packets and then transmitting a PDCP data packet with a lower priority in the at least two PDCP data packets to one radio link control (RLC) entity corresponding to the PDCP entity. The method described in the embodiments of the present application facilitates timely transmitting a data packet with a higher priority in the same radio bearer to a receiving end.

Description

Data processing method and related equipment

Technical field

The present application relates to the field of communications technologies, and in particular, to a data processing method and related devices.

Background technique

Mobile communication technology has profoundly changed people's lives, but the pursuit of higher performance mobile communication technology has never stopped. Typically, in the fifth generation (5G) communication system, there is a radio interface protocol stack as shown in FIG. As shown in FIG. 1, the radio interface protocol stack includes a packet data convergence protocol (PDCP) layer, a radio link control protocol (RLC) layer, and media intervention at both the transmitting end and the receiving end. A media access control (MAC) layer and a physical layer (PHY) layer. Figure 1 shows an example where the terminal device is the transmitting end and the access network device is the receiving end. The data packet is transmitted from the PDCP layer of the terminal device to the RLC layer in turn, and then transmitted to the MAC layer by the RLC layer, then transmitted to the PHY layer by the MAC layer, and finally sent to the access network device in the air interface. The access network device is the transmitting end, and the terminal device is the receiving end.

Generally, the PDCP entity of the transmitting end goes through the processing flow shown in FIG. 2 for the received data packet. among them:

201. After receiving the PDCP service data unit (SDU), set a discard timer exclusive to the PDCP SDU. The PDCP receives the data sent by the upper layer and is called a PDCP SDU.

202. Give a serial number (SN) to the PDCP header corresponding to the PDCP SDU.

203. Perform IP header compression on the PDCP SDU if the PDCP SDU is user plane data.

204. Perform integrity protection on the PDCP SDU.

205. Encrypt the PDCP SDU.

206. Add a PDCP Header to the PDCP SDU to generate a PDCP protocol data unit (PDU).

207. Send the PDCP PDU to the RLC layer.

Usually, data of different priorities is transmitted between the sender and the receiver. For example, critical data (CD) and non-critical data (NCD) are transmitted between the sender and the receiver. The priority of important data is higher than that of non-critical data. Take the example of transmitting a video frame between the sender and the receiver. A fully encoded video frame is called an I frame and can also be represented as a key frame. A video frame generated by referring to the previous I frame and containing only the difference partial coding is called a P frame. Another frame that refers to the frame encoding before and after is called a B frame, and the B frame is a bidirectional difference frame, that is, the B frame records the difference between the current frame and the previous frame. The I frame and some control frames have a great influence on the video playback quality of the receiving end. Therefore, I frames and some control frames are important data. The P frame and the B frame have less influence on the video playback quality of the receiving end. Therefore, the P frame and the B frame are non-critical data.

The PDCP layer on the sending end sets a long discard timer for packets with high priority, so as to ensure that packets with high priority can stay in the PDCP layer for a long time without being discarded in the case of congestion. High packets can be sent successfully. However, a packet with a high priority has a high requirement for delay, and a packet with a high priority needs to be sent to the receiving end in time. By setting a long discard timer, you can only ensure that packets with high priority are successfully sent to the receiver. It is not guaranteed that packets with high priority can be sent to the receiver in time. For example, as shown in FIG. 3, the priority of the data packet corresponding to the sequence numbers SN1 to SN3 is lower than the data packet corresponding to the SN4. The data packet corresponding to SN4 can be sent to the RLC layer at the end. Therefore, the data packet with high priority cannot be sent to the receiving end in time.

Summary of the invention

The embodiment of the present application provides a data processing method and related device, which is convenient for transmitting a data packet with a high priority in the same radio bearer to a receiving end in time.

In a first aspect, the embodiment of the present application provides a data processing method, which is applied to a sending end, where the method includes: acquiring, by a same packet data convergence protocol, a PDCP entity in a radio bearer, at least two PDCP data packets; to a PDCP entity The corresponding radio link layer control protocol RLC entity first sends a PDCP data packet with a higher priority among the at least two PDCP data packets, and then transmits a PDCP data packet with a lower priority among the at least two PDCP data packets.

It can be seen that by implementing the method described in the first aspect, it is advantageous to timely transmit a data packet with a high priority among the same radio bearers to the receiving end.

Optionally, the sequence number SN of the PDCP packet with a high priority is before the SN of the PDCP packet with a lower priority. In this way, according to the order of the SN, the PDCP data packet with the highest priority is sent to the RLC entity, and the PDCP data packet with the lower priority is sent to the RLC entity. After the PDCP entity allocates an SN for the PDCP data packet, the next SN is set to be 1 for the SN, so that the SN of the PDCP data packet that is allocated first is allocated before the PDCP data packet is allocated. Here, the SN of the PDCP packet with the highest priority is allocated to the SN of the PDCP packet with the lower priority, that is, the SN is allocated for the PDCP packet with the higher priority, and then the SN is allocated for the PDCP packet with the lower priority.

In the prior art, the SN allocated by the PDCP data packet acquired first is after the SN of the PDCP data packet acquired later. In this embodiment, even if the PDCP packet with the higher priority is acquired after the PDCP packet with the lower priority, the SN of the PDCP packet with the higher priority is before the SN of the PDCP packet with the lower priority. Therefore, compared with the prior art, this embodiment only changes the processing mode of the PDCP data packet, that is, how to allocate the PDCP data packet SN has changed, but how to transmit the PDCP data packet to the RLC entity is compared with the current The technology has not changed, and the PDCP data packets are sent to the RLC entity in the order of the SN. It can be seen that by implementing this embodiment, it is possible to achieve the effect of transmitting a high priority packet to the receiving end in time without making major changes to the existing flow.

Optionally, the at least two PDCP data packets include the first PDCP data packet and the second PDCP data packet, and the priority of the first PDCP data packet is higher than the priority of the second PDCP data packet, and the sending end may also be The first PDCP packet is allocated a first SN, and the second SN is re-allocated to the second PON, the first SN is before the second SN; correspondingly, the same RLC entity corresponding to the PDCP entity sends at least two The PDCP data packet with a high priority in the PDCP data packet, and the PDCP data packet with a lower priority in the at least two PDCP data packets may be sent in the following manner: at least two in the order of the first SN and the second SN. The PDCP data packets are sent to the same RLC entity.

By implementing this embodiment, the SN can be reassigned to the PDCP data packet with the low priority assigned to the SN to ensure that the SN of the PDCP data packet with the higher priority is before the SN of the PDCP data packet with the lower priority.

Optionally, after the PDCP entity obtains the second PDCP data packet, the PDCP entity allocates a first SN for the second PDCP data packet, and re-allocates the second SN for the first PDCP data packet. The PDCP entity does not have to wait for the preset time to arrive and then allocates the first SN for the second PDCP data packet, or the PDCP entity does not have to wait until the number of acquired PDCP data packets reaches a preset number, and then allocates the first SN for the second PDCP data packet. And reallocating the second SN for the first PDCP data packet.

Optionally, the obtained at least two PDCP data packets are at least two packet data convergence protocol service data units (PDCP SDUs), and the transmitting end may further determine a PDCP SDU with a higher priority among the at least two PDCP SDUs and a lower priority. Correspondingly, the same RLC entity corresponding to the PDCP entity first transmits a PDCP data packet with a high priority among the at least two PDCP data packets, and then transmits a PDCP data packet with a lower priority of the at least two PDCP data packets. The embodiment may be: first transmitting, to the same RLC entity, a packet data convergence protocol protocol data unit PDCP PDU generated by the high priority PDCP SDU, and then transmitting a PDCP PDU generated by a low priority PDCP SDU.

It can be seen that, by implementing the implementation manner, the sending end does not need to change the processing flow of the existing PDCP data packet, that is, the SN allocated by the PDCP data packet received first is before the SN allocated by the PDCP data packet received later. This embodiment does not transmit PDCP PDUs sequentially in the order of SN. Instead, the PDCP PDU corresponding to the PDCP packet with the highest priority is sent to the RLC entity first. It can be seen that by implementing this embodiment, it is possible to achieve the effect of transmitting a high priority packet to the receiving end in time without making major changes to the existing flow.

Optionally, the at least two PDCP data packets are PDCP data packets acquired within a preset time in a buffer of the sending end, or the at least two PDCP data packets are obtained in a preset amount within a buffer of the sending end. . By implementing this embodiment, it is advantageous to save CPU resources.

Optionally, the PDCP PDU corresponding to the PDCP data packet with the highest priority is directly sent to the RLC entity, as long as the PDCP PDU corresponding to the PDCP data packet with the highest priority is generated.

Optionally, the sending end is a terminal device, and the same radio link layer control protocol RLC entity corresponding to the PDCP entity first sends the PDCP data packet with the highest priority in the at least two PDCP data packets, and then sends the at least two PDCP data packets. Before the low-priority PDCP data packet, the sending end may further receive the indication information sent by the access network device, where the indication information is used to indicate that the same RLC entity corresponding to the PDCP entity is allowed to send at least two PDCP data packets first. The PDCP data packet of the highest level is sent, and the PDCP data packet with low priority among the at least two PDCP data packets is sent.

By implementing this embodiment, the PDCP data packets with higher priority can be preferentially transmitted when necessary.

Optionally, the indication message is a radio resource control (RRC) configuration message. Or the indication message is a PDCP indication message, for example, the indication information is carried in the PDCP packet header, or a new PDCP Control PDU is designed to indicate the message. Or the indication message is a MAC indication message, for example, the indication information is carried in the MAC packet header, or a new MAC control element is designed to indicate the message.

In a second aspect, the embodiment of the present application further provides a data processing method, which is applied to a receiving end, where the method includes: receiving indication information from a first device, where the indication information is used to indicate whether to allow the transmitting end to pass the same wireless The packet data convergence protocol PDCP data packet transmitted in an out-of-order manner is reordered; if the indication information is used to indicate that the PDCP data packet sent by the transmitting end through the same radio bearer is reordered, the PDCP data packet is received in the same PDCP entity. The PDCP packet sent by the sender through the same radio bearer in an out-of-order manner; the same PDCP entity reorders the PDCP packets sent out of order.

It can be seen that by implementing the method described in the second aspect, the PDCP data packet can be reordered when receiving the out-of-order PDCP data packet, instead of reordering the PDCP data packet at any time.

Optionally, the receiving end is a terminal device, and the first device and the sending end are access network devices. Or the receiving end is an access network device, and the first device is a core network device CN, and the sending end is a terminal device.

Optionally, the indication message is an RRC configuration message. Or the indication message is a PDCP indication message, for example, the indication information is carried in the PDCP packet header, or a new PDCP Control PDU is designed to indicate the message. Or the indication message is a MAC indication message, for example, the indication information is carried in the MAC packet header, or a new MAC control element is designed to indicate the message.

In a third aspect, a sender is provided, which can perform the method in the first aspect or the possible implementation of the first aspect. This function can be implemented in hardware or in hardware by executing the corresponding software. The hardware or software includes one or more units corresponding to the functions described above. The unit can be software and/or hardware. Based on the same inventive concept, the principle and the beneficial effects of the problem at the transmitting end can be referred to the foregoing first aspect or the possible implementation manners and beneficial effects of the first aspect, and the repeated description is not repeated.

In a fourth aspect, a receiving end is provided, which can perform the method in the second aspect or the possible implementation manner of the second aspect. This function can be implemented in hardware or in hardware by executing the corresponding software. The hardware or software includes one or more units corresponding to the functions described above. The unit can be software and/or hardware. Based on the same inventive concept, the principle and the beneficial effects of the problem at the receiving end can be referred to the foregoing second aspect or the possible implementation manner and beneficial effects of the second aspect, and the repeated description is not repeated.

In a fifth aspect, a transmitting end is provided, the transmitting end comprising: a processor, a memory, a communication interface, and one or more programs; the processor, the communication interface, and the memory are connected; wherein one or more programs are stored in the memory The processor calls the program stored in the memory to implement the solution in the above first aspect or the possible implementation manner of the first aspect, and the implementation manner and the beneficial effects of the problem at the transmitting end can be referred to the first aspect or the foregoing The possible implementations and beneficial effects on the one hand are not repeated here.

In a sixth aspect, a receiving end is provided, the receiving end comprising: a processor, a memory, a communication interface, and one or more programs; the processor, the communication interface, and the memory are connected; wherein one or more programs are stored in the memory The processor calls the program stored in the memory to implement the solution in the foregoing second aspect or the possible implementation manner of the second aspect, and the implementation manner and the beneficial effects of the receiving end solving the problem can be referred to the second aspect or the foregoing The possible implementations and beneficial effects of the two aspects are not repeated here.

A seventh aspect, a computer program product, when executed on a computer, causes the computer to perform the method of any of the first aspect, the second aspect, or any optional implementation of the first aspect or Any optional implementation of the two aspects.

In an eighth aspect, there is provided a chip product at a transmitting end, which performs the method of any of the above first aspect or any possible implementation of the first aspect.

In a ninth aspect, a chip product at a receiving end is provided to perform the method of any of the above second aspect or any of the possible implementations of the second aspect.

DRAWINGS

1 is a schematic diagram of a conventional wireless interface protocol stack;

2 is a schematic flowchart of data processing of a received data packet by a PDCP entity at a transmitting end;

3 is a schematic diagram of a PDCP entity of a transmitting end transmitting a PDCP data packet to an RLC;

4 is a schematic diagram of a communication system according to an embodiment of the present application;

FIG. 5 is a schematic flowchart diagram of a data processing method according to an embodiment of the present disclosure;

6 is a schematic diagram of a PDCP entity at a sending end sending a PDCP data packet to an RLC according to an embodiment of the present disclosure;

FIG. 7 is a schematic diagram of still another PDCP entity of a sending end sending a PDCP data packet to an RLC according to an embodiment of the present disclosure;

FIG. 8 is a schematic diagram of still another PDCP entity of a sending end sending a PDCP data packet to an RLC according to an embodiment of the present disclosure;

FIG. 9 is a schematic flowchart diagram of another data processing method according to an embodiment of the present disclosure;

FIG. 10 is a schematic flowchart diagram of another data processing method according to an embodiment of the present disclosure;

FIG. 11 is a schematic flowchart diagram of another data processing method according to an embodiment of the present application;

FIG. 12 is a schematic diagram of a reordering window according to an embodiment of the present application;

FIG. 13 is a schematic structural diagram of a transmitting end according to an embodiment of the present disclosure;

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

FIG. 15 is a schematic structural diagram of another transmitting end according to an embodiment of the present disclosure;

FIG. 16 is a schematic structural diagram of another receiving end according to an embodiment of the present application.

Detailed ways

The specific embodiments of the present application are further described in detail below with reference to the accompanying drawings.

The embodiment of the present application provides a data processing method and related device, which is convenient for sending a data packet with a high priority to a receiving end in time.

In order to better understand the embodiments of the present application, a communication system to which the embodiments of the present application are applicable will be described below.

4 is a schematic diagram of a communication system provided by an embodiment of the present application. As shown in FIG. 4, the communication system includes a core network device, an access network device, and at least one terminal device. FIG. 4 exemplifies two terminal devices. The terminal device is connected to the access network device in a wireless manner, and the access network device is connected to the core network device through a wireless or wired manner. The core network device and the access network device may be independent physical devices, or may integrate the functions of the core network device with the logical functions of the access network device on the same physical device, or may be integrated on one physical device. The functions of some core network devices and the functions of some access network devices. The terminal device can be fixed or mobile. FIG. 4 is only a schematic diagram, and the communication system may further include other network devices, such as a wireless relay device and a wireless backhaul device, which are not shown in FIG. 4. The embodiment of the present application does not limit the number of core network devices, access network devices, and terminal devices included in the communication system.

The access network device is an access device that the terminal device accesses to the mobile communication system by using a wireless device, and may be a network side NodeB, an evolved network side eNodeB, a network side in a 5G mobile communication system, and a future mobile communication system. The specific technology and the specific device configuration adopted by the access network device are not limited in the embodiment of the present application.

The terminal device may also be referred to as a terminal terminal, a user equipment (UE), a mobile station (MS), a mobile terminal (MT), and the like. The terminal device can be a mobile phone, a tablet, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, industrial control (industrial control) Wireless terminal, wireless terminal in self driving, wireless terminal in remote medical surgery, wireless terminal in smart grid, wireless in transport safety A terminal, a wireless terminal in a smart city, a wireless terminal in a smart home, and the like.

Access network equipment and terminal equipment can be deployed on land, indoors or outdoors, hand-held or on-board; they can also be deployed on the water; they can also be deployed on airborne aircraft, balloons and satellites. The application scenarios of the radio access network device and the terminal device are not limited.

The embodiments of the present application can be applied to downlink signal transmission, and can also be applied to uplink signal transmission, and can also be applied to device to device (D2D) signal transmission. For downlink signal transmission, the sending device is an access network device, and the corresponding receiving device is a terminal device. For uplink signal transmission, the sending device is a terminal device, and the corresponding receiving device is an access network device. For D2D signal transmission, the transmitting device is a terminal device, and the corresponding receiving device is also a terminal device. The embodiment of the present application does not limit the transmission direction of the signal.

The access network device and the terminal device and between the terminal device and the terminal device can communicate through a licensed spectrum, or can communicate through an unlicensed spectrum, or can simultaneously pass the licensed spectrum and the license-free. The spectrum communicates. Communication between the radio access network device and the terminal device and between the terminal device and the terminal device may be performed through a spectrum of 6 gigahertz (GHz) or less, or may be communicated through a spectrum of 6 GHz or higher, or may be used below 6 GHz. The spectrum communicates with the spectrum above 6 GHz. The embodiment of the present application does not limit the spectrum resources used between the radio access network device and the terminal device.

The data processing method and related devices provided by the present application are further described below.

Referring to FIG. 5, FIG. 5 is a data processing method provided by an embodiment of the present application. As shown in FIG. 5, the data processing method includes the following

sections

501 and 502, wherein:

501. The sender obtains at least two PDCP data packets by the same PDCP entity in one radio bearer.

502. The sending end sends, to the same RLC entity corresponding to the PDCP entity, a PDCP data packet with a high priority among the at least two PDCP data packets, and then sends a PDCP data packet with a lower priority among the at least two PDCP data packets.

The sending end may be a terminal device or an access network device. When the transmitting end is a terminal device, the receiving end is an access network device, and when the transmitting end is an access network device, the receiving end is a terminal device.

The at least two PDCP data packets may be obtained from an upper layer (such as an application layer). The PDCP entity obtains the format of the PDCP data packet sent by the upper layer (such as the application layer) into the PDCP SDU format. The PDCP entity sends the PDCP packet to the RLC entity in the PDCP PDU format.

The PDCP data packet with a high priority among the at least two PDCP data packets refers to a PDCP data packet with a high priority, that is, a PDCP data packet that needs to be transmitted to the receiving end in time. For example, a PDCP packet with a high priority may be an I frame or some control frame in a video frame. A PDCP packet with a lower priority may be a P frame or a B frame in a video frame.

Optionally, the priority of the at least two PDCP data packets may be identified by the PDCP entity or notified by the application layer to notify the PDCP entity.

The PDCP layer of the transmitting end may include multiple PDCP entities, and the RLC layer of the transmitting end may include multiple RLC entities. At least two PDCP data packets are received by the same PDCP entity, and the at least two PDCP data packets are sent to the same RLC entity.

For example, the PDCP layer of the transmitting end includes the PDCP entity 1 and the PDCP entity 2, and the RLC layer of the transmitting end includes the RLC entity 1 and the RLC entity 2. The PDCP entity 1 and the RLC entity 1 belong to one radio bearer. The PDCP entity 2 and the RLC entity 2 belong to another radio bearer.

The PDCP entity 1 receives the PDCP packet 1 and the PDCP packet 2. The priority of PDCP packet 1 is higher than the priority of PDCP packet 2. The PDCP entity 1 first transmits the PDCP data packet 1 to the RLC entity 1, and then transmits the PDCP data packet 2 to the RLC entity 1. Similarly, the PDCP entity 2 receives the PDCP packet 3 and the PDCP packet 4. The priority of PDCP packet 3 is higher than the priority of PDCP packet 4. The PDCP entity 2 first transmits the PDCP data packet 3 to the RLC entity 2, and then transmits the PDCP data packet 4 to the RLC entity 2.

It can be seen that, by implementing the method described in FIG. 5, in a radio bearer, a data packet with a high priority can be transmitted to the receiving end, and then a data packet with a low priority is transmitted to the receiving end. It can be seen that by implementing the method described in FIG. 5, it is advantageous to timely transmit a data packet with a high priority among the same radio bearers to the receiving end.

Optionally, the at least two PDCP data packets are PDCP data packets acquired within a preset time in a buffer of the sending end. That is to say, the PDCP entity sends a PDCP data packet with a high priority to the same RLC entity in a preset time period, and then transmits a PDCP data packet with a low priority.

For example, the PDCP entity acquires PDCP data packet 1, PDCP data packet 2, and PDCP data packet 3 from the upper layer within the first 2 ms. The PDCP entity first transmits the PDCP data packet 2 with the highest priority and the PDCP data packet 3 to the RLC entity, and then transmits the PDCP data packet 1 with the lower priority to the same RLC entity. The PDCP entity acquires PDCP packet 4, PDCP packet 5, and PDCP packet 6 from the upper layer within the second 2 ms. The PDCP entity first transmits the PDCP packet 5 with high priority and the PDCP packet 6 to the RLC entity, and then transmits the PDCP packet 4 with the lower priority to the same RLC entity.

Optionally, the at least two PDCP data packets are obtained in a preset number of buffers in the sending end.

For example, the preset number is 3. After the PDCP entity obtains the PDCP data packet 1, the PDCP data packet 2, and the PDCP data packet 3 from the upper layer, the PDCP entity first sends the PDCP data packet 2 and the PDCP data packet 3 with high priority. To the RLC entity, the PDCP packet 1 with a lower priority is sent to the same RLC entity. After the PDCP entity obtains the PDCP data packet 4, the PDCP data packet 5, and the PDCP data packet 6, the PDCP entity first transmits the PDCP data packet 5 and the PDCP data packet 6 to the RLC entity with high priority, and then transmits the PDCP data packet with low priority. 4 to the same RLC entity.

Optionally, the SN of the PDCP packet with a high priority is allocated before the SN of the PDCP packet with a lower priority. In this way, according to the order of the SNs, according to the order that the SNs are small to large, the PDCP data packets with high priority can be sent to the RLC entity, and the PDCP data packets with low priority are sent to the RLC entity. After the PDCP entity allocates an SN for the PDCP data packet, the next SN is set to be 1 for the SN, so that the SN of the PDCP data packet that is allocated first is allocated before the PDCP data packet is allocated. Here, the SN of the PDCP packet with the highest priority is allocated to the SN of the PDCP packet with the lower priority, that is, the SN is allocated for the PDCP packet with the higher priority, and then the SN is allocated for the PDCP packet with the lower priority.

For example, an example is to transmit a PDCP packet to an RLC entity in order of SN being small to large. As shown in FIG. 6, the priority of PDCP packet 3 is higher than the priorities of PDCP packet 1 and PDCP packet 2. Even if the PDCP entity first acquires the PDCP data packet 1 and the PDCP data packet 2 from the upper layer, and finally acquires the PDCP data packet 3, the SN finally allocated to the PDCP data packet 3 is smaller than the SN of the PDCP data packet 1 and the PDCP data packet 2. According to the order of SN from small to large, the PDCP data packet 3 with high priority can be sent to the RLC entity, and then the PDCP data packet 1 and the PDCP data packet 2 with low priority are sent to the RLC entity.

In the prior art, the SN that is first acquired by the PDCP data packet is before the SN of the PDCP data packet that is acquired later. In this embodiment, even if the PDCP packet with the higher priority is acquired after the PDCP packet with the lower priority, the SN of the PDCP packet with the higher priority is before the SN of the PDCP packet with the lower priority. Therefore, compared with the prior art, this embodiment only changes the processing mode of the PDCP data packet, that is, how to allocate the PDCP data packet SN has changed, but how to transmit the PDCP data packet to the RLC entity is compared with the current The technology has not changed, and the PDCP data packets are sent to the RLC entity in the order of the SN. It can be seen that by implementing the implementation manner, it is possible to achieve the effect of transmitting a high priority data packet to the receiving end in the same radio bearer in a timely manner without making major changes to the existing flow.

Optionally, the at least two PDCP data packets include the first PDCP data packet and the second PDCP data packet, and the first PDCP data packet has a higher priority than the second PDCP data packet, and the sending end receives the first After the PDCP data packet, the first PDCP data packet may be assigned a first sequence number SN, and the second PDCP data packet may be reassigned a second SN, the first SN being before the second SN. Correspondingly, the transmitting end sends the PDCP data packet with the highest priority in the at least two PDCP data packets to the same RLC entity corresponding to the PDCP entity, and then sends the PDCP data packet with the lower priority of the at least two PDCP data packets. The method may be: sending at least two PDCP data packets to the RLC layer in the order of the first SN and the second SN.

That is, in this embodiment, the PDCP entity first receives the second PDCP data packet and then receives the first PDCP data packet. The PDCP first allocates an SN for the second PDCP packet. After receiving the first PDCP data packet, the PDCP entity allocates a first SN for the first PDCP data packet, and reallocates a second SN after the first SN for the second PDCP data packet.

For example, an example is to transmit a PDCP packet to an RLC entity in order of SN being small to large. The PDCP entity acquires PDCP packet 1 and PDCP packet 2 from the upper layer. The PDCP entity assigns an SN of 1 to PDCP packet 1, and the PDCP entity assigns an SN of 2 to PDCP packet 2. After acquiring the PDCP data packet 3 from the upper layer, since the priority of the PDCP data packet 3 is higher than the priority of the PDCP data packet 1 and the PDCP data packet 2, the PDCP entity allocates the SN to the PDCP data packet 3 as 1 for the PDCP data packet. 1 Reassign SN to 2, and redistribute SN to PDCP packet 2. Thus PDCP packet 3 can be sent to the RLC entity before PDCP packet 1 and PDCP packet 2. The first PDCP data packet may be PDCP data packet 1 or PDCP data packet 2. The second PDCP packet is a PDCP packet 3.

Optionally, after the PDCP entity obtains the second PDCP data packet, the PDCP entity allocates a first SN for the second PDCP data packet, and re-allocates the second SN for the first PDCP data packet. For example, as shown in FIG. 7, the PDCP entity does not have to wait until the preset time arrives to allocate the first SN for the second PDCP data packet, or the PDCP entity does not have to wait until the number of acquired PDCP data packets reaches a preset number, and then the second The PDCP packet allocates a first SN and reassigns a second SN for the first PDCP packet.

As shown in FIG. 7, the PDCP data packet is transmitted to the RLC entity in an order that the SN is small to large. The PDCP entity acquires PDCP packet 1 and PDCP packet 2 from the upper layer. The PDCP entity assigns an SN of 1 to PDCP packet 1, and the PDCP entity assigns an SN of 2 to PDCP packet 2. After acquiring the PDCP data packet 3 from the upper layer, since the priority of the PDCP data packet 3 is higher than the priority of the PDCP data packet 1 and the PDCP data packet 2, the PDCP entity allocates the SN to the PDCP data packet 3 as 1 for the PDCP data packet. 1 Reassign SN to 2, and redistribute SN to PDCP packet 2. After acquiring the PDCP data packet 4 from the upper layer, since the priority of the PDCP data packet 4 is higher than the priority of the PDCP data packet 1 and the PDCP data packet 2, the PDCP entity allocates the SN to the PDCP data packet 4 to 2, for the PDCP data packet. 1 Reassign SN to 3, and reassign SN to PDCP packet 2. Thus, PDCP packet 3 and PDCP packet 4 can be sent to the RLC entity before PDCP packet 1 and PDCP packet 2. The first PDCP data packet may be PDCP data packet 1 or PDCP data packet 2. The second PDCP data packet may be PDCP data packet 3 or PDCP data packet 4.

The at least two PDCP data packets are PDCP data packets acquired within a preset time in the buffer of the transmitting end, and the PDCP data packets are sent to the RLC entity in an order that the SN is small to large. For another example, the PDCP entity sequentially acquires PDCP data packet 1, PDCP data packet 2, and PDCP data packet 3 from the upper layer within a preset time (eg, 2 ms). The priority of PDCP packet 3 is higher than PDCP data 1 and PDCP data 2. The PDCP entity assigns an SN of 1 to PDCP packet 1, and the PDCP entity assigns an SN of 2 to PDCP packet 2. Since the priority of PDCP data packet 3 is higher than the priority of PDCP data packet 1 and PDCP data packet 2, when 2 ms arrives, if PDCP data packet 3 has not been allocated SN, the PDCP entity allocates SN for PDCP data packet 3 for the first time. 1. Reassign SN to 2 for PDCP packet 1, and reassign SN to 3 for PDCP packet 2. Thus PDCP packet 3 can be sent to the RLC entity before PDCP packet 1 and PDCP packet 2. The first PDCP data packet may be PDCP data packet 1 or PDCP data packet 2. The second PDCP packet is a PDCP packet 3.

The at least two PDCP data packets are PDCP data packets acquired in a preset number of buffers in the sending end, and the PDCP data packets are sent to the RLC entity in an order that the SN is small to large. For another example, the preset number is 3, and the PDCP entity sequentially acquires PDCP data packet 1, PDCP data packet 2, and PDCP data packet 3 from the upper layer. The priority of PDCP packet 3 is higher than PDCP data 1 and PDCP data 2. The PDCP entity assigns an SN of 1 to PDCP packet 1, and the PDCP entity assigns an SN of 2 to PDCP packet 2. Since the priority of the PDCP data packet 3 is higher than the priority of the PDCP data packet 1 and the PDCP data packet 2, after receiving the PDCP data packet 3, the PDCP entity first allocates the SN to 1 for the PDCP data packet 3, and the PDCP data packet 1 The reassignment SN is 2, and the PDCP packet 2 is reassigned SN to 3. Thus PDCP packet 3 can be sent to the RLC entity before PDCP packet 1 and PDCP packet 2. The first PDCP data packet may be PDCP data packet 1 or PDCP data packet 2. The second PDCP packet is a PDCP packet 3.

Of course, if at least two PDCP data packets are PDCP data packets acquired within a preset time in the buffer of the transmitting end, when the preset time arrives, if the SN of the third PDCP data packet exists in the fourth PDCP data packet After the SN, the priority of the third PDCP data packet is higher than the priority of the fourth PDCP data packet, and then the SN is re-allocated to the third PDCP data packet and the fourth PDCP data packet, so that the SN of the third PDCP data packet is in the fourth Before the SN of the PDCP packet. Optionally, if the fifth PDCP data packet of the unassigned SN is still present in the at least two PDCP data packets, the priority of the fifth PDCP data packet is higher than the priority of the fourth PDCP data packet, and is also the fifth The PDCP packet is assigned an SN such that the SN of the fifth PDCP packet precedes the SN of the fourth PDCP packet.

For example, the PDCP data packet is sent to the RLC entity in an order that the SN is small to large. The PDCP entity sequentially acquires PDCP data packet 1, PDCP data packet 2, and PDCP data packet 3 within a preset time (eg, 2 ms). PDCP packet 2 and PDCP packet 3 have higher priority than PDCP packet 1. The PDCP entity assigns an SN of 1 to PDCP packet 1, and the PDCP entity assigns an SN of 2 to PDCP packet 2. Since the priority of PDCP packet 2 is higher than the priority of PDCP packet 1, the PDCP entity reassigns SN to 1 for PDCP packet 2 when 2 ms arrives, and PDCP data for PDCP packet 3 has not been assigned SN. Packet 3 allocates SN to 2, and PDCP packet 1 reassigns SN to 3. Thus PDCP Packet 2 and PDCP Packet 3 can be sent to the RLC entity before PDCP Packet 1. The third PDCP data packet may be the PDCP data packet 2, the fourth PDCP data packet may be the PDCP data packet 1, and the fifth PDCP data packet may be the PDCP data packet 3.

Of course, if the at least two PDCP data packets are obtained in a buffer of the sending end within a preset number, if the number of the at least two PDCP data packets reaches a preset number, if the SN of the third PDCP data packet exists After the SN of the fourth PDCP data packet, the priority of the third PDCP data packet is higher than the priority of the fourth PDCP data packet, then the SN is re-allocated to the third PDCP data packet and the fourth PDCP data packet, so that the third PDCP is obtained. The SN of the data packet precedes the SN of the fourth PDCP data packet. Optionally, if there is still a fifth PDCP data packet that is not assigned an SN, and the priority of the fifth PDCP data packet is higher than the priority of the fourth PDCP data packet, the fifth PDCP data packet is also allocated an SN, so that The SN of the fifth PDCP packet precedes the SN of the fourth PDCP packet.

For example, the PDCP data packet is sent to the RLC entity in an order that the SN is small to large. The preset number is 3, and the PDCP entity sequentially acquires PDCP data packet 1, PDCP data packet 2, and PDCP data packet 3 from the upper layer. PDCP packet 2 and PDCP packet 3 have higher priority than PDCP packet 1. The PDCP entity assigns an SN of 1 to PDCP packet 1, and the PDCP entity assigns an SN of 2 to PDCP packet 2. Since the priority of the PDCP packet 2 is higher than the priority of the PDCP packet 1, when the PDCP packet 3 is acquired from the upper layer, the PDCP entity reassigns the SN to 1 for the PDCP packet 2, since the PDCP packet 3 has not been allocated. For SN, SN is assigned to PDCP packet 3, and SN is 3 for PDCP packet 1. Thus PDCP Packet 2 and PDCP Packet 3 can be sent to the RLC entity before PDCP Packet 1. The third PDCP data packet may be the PDCP data packet 2, the fourth PDCP data packet may be the PDCP data packet 1, and the fifth PDCP data packet may be the PDCP data packet 3.

Optionally, the obtained at least two PDCP data packets are at least two packet data convergence protocol service data units (PDCP SDUs), and after the transmitting end acquires at least two PDCP data packets, the transmitting end may further determine the at least two PDCP SDUs. A PDCP SDU with a high priority and a PDCP SDU with a low priority. Correspondingly, the transmitting end sends the PDCP data packet with the highest priority among the at least two PDCP data packets to the same RLC entity corresponding to the PDCP entity, and then sends the PDCP data packet with the lower priority of the at least two PDCP data packets. The embodiment may be: first transmitting, to the same RLC entity, a packet data convergence protocol protocol data unit PDCP PDU generated by the high priority PDCP SDU, and then transmitting a PDCP PDU generated by a low priority PDCP SDU.

For example, as shown in FIG. 8, the at least two PDCP data packets acquired by the PDCP entity of the transmitting end from the upper layer are, in order, PDCP data packet 1, PDCP data packet 2, and PDCP data packet 3. The PDCP entity at the transmitting end determines that the PDCP SDU with the highest priority is the PDCP SDU3 corresponding to the PDCP data packet 3, and the PDCP SDU with the lower priority is the PDCP SDU2 corresponding to the PDCP data packet 2 and the PDCP SDU1 corresponding to the PDCP data packet 1. The transmitting end generates the PDCP PDU1 corresponding to the PDCP SDU1, the PDCP PDU2 corresponding to the PDCP SDU2, and the PDCP PDU3 corresponding to the PDCP SDU3 according to the existing procedure. The SN of the PDCP PDU1 is 1, the SN of the PDCP PDU2 is 2, and the SN of the PDCP PDU3 is 3. After the PDCP PDU3 is generated by the sender, the PDCP PDU3 with the highest priority is sent to the RLC entity, and the PDCP PDU1 and PDCP PDU2 with the lower priority are sent to the same RLC entity. That is, the PDCP PDU3 with the SN of 3 is transmitted first, then the PDCP PDU1 with the SN of 1 is transmitted, and the PDCP PDU 2 with the SN of 2 is transmitted.

It can be seen that, by implementing the implementation manner, the sending end does not need to change the processing flow of the existing PDCP data packet, that is, the SN allocated by the PDCP data packet acquired first is before the SN allocated by the PDCP data packet acquired later. This embodiment does not transmit PDCP PDUs sequentially in the order of SN. Instead, the PDCP PDU corresponding to the PDCP packet with the highest priority is sent to the RLC entity first. It can be seen that by implementing this embodiment, it is possible to achieve the effect of transmitting a high priority packet to the receiving end in time without making major changes to the existing flow.

For example, the PDCP entity at the transmitting end sequentially acquires PDCP data packet 1, PDCP data packet 2, and PDCP data packet 3. The PDCP entity at the transmitting end determines that the PDCP SDU with the highest priority is the PDCP SDU3 corresponding to the PDCP data packet 3, and the PDCP SDU with the lower priority is the PDCP SDU2 corresponding to the PDCP data packet 2 and the PDCP SDU1 corresponding to the PDCP data packet 1. The transmitting end generates the PDCP PDU1 corresponding to the PDCP SDU1, the PDCP PDU2 corresponding to the PDCP SDU2, and the PDCP PDU3 corresponding to the PDCP SDU3 according to the existing procedure. The SN of the PDCP PDU1 is 1, the SN of the PDCP PDU2 is 2, and the SN of the PDCP PDU3 is 3. The PDCP entity at the transmitting end first sends the PDCP PDU3 to the RLC entity. The PDCP entity at the transmitting end acquires the PDCP data packet 4, and determines that the PDCP SDU4 corresponding to the PDCP data packet 4 is a PDCP SDU with a high priority. After the PDCP entity at the transmitting end generates the PDCP PDU4 corresponding to the PDCP SDU4, the PDCP PDU4 is first sent to the RLC entity. Finally, the PDCP entity at the transmitting end sends the PDCP PDU1 and the PDCP PDU2 to the same RLC entity.

For example, the PDCP data packet acquired within a preset time in the buffer of the transmitting end is taken as an example. For another example, the PDCP entity at the transmitting end sequentially acquires PDCP data packet 1, PDCP data packet 2, and PDCP data packet 3 from the upper layer within a preset time (eg, 2 ms). The PDCP SDU3 corresponding to the PDCP data packet 3 and the PDCP SDU2 corresponding to the PDCP data packet 2 have higher priority than the PDCP SDU1 corresponding to the PDCP data packet 1. The transmitting end generates the PDCP PDU1 corresponding to the PDCP SDU1, the PDCP PDU2 corresponding to the PDCP SDU2, and the PDCP PDU3 corresponding to the PDCP SDU3 according to the existing procedure. The SN of the PDCP PDU1 is 1, the SN of the PDCP PDU2 is 2, and the SN of the PDCP PDU3 is 3. Upon arrival of 2 ms, the PDCP entity of the transmitting end first sends PDCP PDU2 and PDCP PDU3 to the RLC entity, and then sends the PDCP PDU1 to the same RLC entity.

The example in which the at least two PDCP data packets are obtained in a buffer of the transmitting end within a preset number is taken as an example. For example, the preset number is 3, and the PDCP entity at the transmitting end sequentially acquires PDCP data packet 1, PDCP data packet 2, and PDCP data packet 3 from the upper layer. The priority of the PDCP SDU2 corresponding to the PDCP SDU3 and the PDCP data packet 2 of the PDCP data packet 3 is higher than the priority of the PDCP SDU1 corresponding to the PDCP data packet 1. The transmitting end generates the PDCP PDU1 corresponding to the PDCP SDU1, the PDCP PDU2 corresponding to the PDCP SDU2, and the PDCP PDU3 corresponding to the PDCP SDU3 according to the existing procedure. The SN of the PDCP PDU1 is 1, the SN of the PDCP PDU2 is 2, and the SN of the PDCP PDU3 is 3. The PDCP entity at the transmitting end first sends the PDCP PDU2 and the PDCP PDU3 to the RLC entity, and then sends the PDCP PDU1 to the same RLC entity.

Optionally, the sending end is a terminal device, and the same RLC entity corresponding to the PDCP entity first sends the PDCP data packet with the highest priority in the at least two PDCP data packets, and then sends the PDCP with the lower priority of the at least two PDCP data packets. Before the data packet, the PDCP entity of the sending end may further receive the indication information sent by the access network device, where the indication information is used to indicate whether to allow the same RLC entity corresponding to the PDCP entity to first send the at least two PDCP data packets with high priority. The PDCP data packet is followed by the PDCP data packet with a lower priority among the at least two PDCP data packets. If the indication information received by the PDCP entity of the transmitting end is used to indicate that the same RLC entity corresponding to the PDCP entity is allowed to first send the PDCP data packet with the highest priority in the at least two PDCP data packets, and then send the at least two PDCP data packets. The PDCP packet with a low priority is sent by the sending end to the same RLC entity corresponding to the PDCP entity, and then the PDCP data packet with the highest priority of the at least two PDCP data packets is sent, and then the low priority of the at least two PDCP data packets is sent. PDCP packet.

Referring to FIG. 9, FIG. 9 is another data processing method provided by an embodiment of the present application. As shown in FIG. 9, the data processing method includes the following sections 901 to 903, wherein:

901. The receiving end receives the indication information from the first device.

902. The receiving end receives, in the same PDCP entity, a PDCP data packet that is sent out by the sending end through the same radio bearer.

903. The receiving end reorders the PDCP data packets sent out of order by the same PDCP entity.

The indication information is used to indicate whether to allow reordering of PDCP data packets sent by the sending end by the same radio bearer in an out-of-order manner. If the indication information is used to indicate that the PDCP data packets sent by the transmitting end through the same radio bearer are reordered, the receiving end receives the PDCP data packet that is sent out by the same radio bearer in the same PDCP entity. Reordering PDCP packets sent out of order in the same PDCP entity.

Optionally, as shown in FIG. 10, the receiving end is a terminal device, and the first device and the sending end may be access network devices. The indication information sent by the access network device to the terminal device may be sent by the core network (CN) to the access network device, or the indication information sent by the access network device to the terminal device may be generated by the access network device itself. And sent to the access network device. FIG. 10 is an example of sending, by the access network device, the indication information sent by the access network device to the access network device.

For example, the PDCP entity of the access network device receives the indication information sent by the core network device to indicate whether to allow the PDCP data packets sent by the sending end to be out of order by the same radio bearer. The access network device sends the indication information to the terminal device. If the core network device indicates that the PDCP data packets that are randomly sent by the access network device through the same radio bearer are reordered, the PDCP entity of the access network device sequentially receives the PDCP data packet 1, the PDCP data packet 2, and the PDCP data. After the packet 3, the PDCP PDU1 corresponding to the PDCP data packet 1, the PDCP PDU2 corresponding to the PDCP data packet 2, and the PDCP PDU3 corresponding to the PDCP data packet 3 are generated according to the existing procedure. The SN of the PDCP PDU1 is 1, the SN of the PDCP PDU2 is 2, and the SN of the PDCP PDU3 is 3. The priority of PDCP packet 3 is higher than the priority of PDCP packet 1 and PDCP packet 2. After the PDCP PDU3 is generated by the access network device, the PDCP PDU corresponding to the PDCP packet with the highest priority is detected as the PDCP PDU3. The PDCP entity of the access network device first sends the PDCP PDU3 to the RLC entity, and then sends the PDCP PDU1 and the PDCP PDU2 to the same RLC entity, and the RLC entity sends the sequence to the terminal device. That is, the PDCP PDU3 with the SN of 3 is sent first, then the PDCP PDU1 with the SN of 1 is sent, and the PDCP PDU2 with the SN of 2 is sent.

The PDCP entity 1 of the terminal device in a radio bearer receives indication information from the access network device. If the indication information indicates that the terminal device is allowed to reorder the PDCP data packets received out of order by the same radio bearer, the PDCP entity 1 of the terminal device sequentially receives the PDCP PDU3, the PDCP PDU1, and the PDCP PDU2 in a reordering window. Thereafter, PDCP PDU3, PDCP PDU1, and PDCP PDU2 are reordered in order of small to large SN. Since the SN of the PDCP PDU1 is 1, the SN of the PDCP PDU2 is 2, and the SN of the PDCP PDU3 is 3. Therefore, the PDCP entity 1 of the terminal device ranks the PDCP PDU1 in the first place and the PDCP PDU2 in the second place, which will be the PDCP. PDU3 is ranked third.

Optionally, as shown in FIG. 11, the receiving end is an access network device, the first device is a core network device CN, and the sending end is a terminal device.

For example, the PDCP entity of the terminal device sequentially receives PDCP data packet 1, PDCP data packet 2, and PDCP data packet 3. The priority of PDCP packet 3 is higher than the priority of PDCP packet 1 and PDCP packet 2. The terminal device generates PDCP PDU1 corresponding to PDCP data packet 1, PDCP PDU2 corresponding to PDCP data packet 2, and PDCP PDU3 corresponding to PDCP data packet 3 according to an existing procedure. The SN of the PDCP PDU1 is 1, the SN of the PDCP PDU2 is 2, and the SN of the PDCP PDU3 is 3. After the PDCP PDU3 is generated by the terminal device, the PDCP PDU corresponding to the PDCP data packet with the highest priority is detected as the PDCP PDU3. The PDCP entity of the terminal device first sends the PDCP PDU3 to the RLC entity, and then sends the PDCP PDU1 and the PDCP PDU2 to the same RLC entity, and is sent by the RLC entity to the access network device. That is, the PDCP PDU3 with the SN of 3 is transmitted first, then the PDCP PDU1 with the SN of 1 is transmitted, and the PDCP PDU 2 with the SN of 2 is transmitted.

The access network device receives indication information from the core network device. If the indication information indicates that the access network device is allowed to reorder the PDCP data packets that are received out of order by the same radio bearer, the PDCP entity 1 of the access network device receives the PDCP PDU3 and the PDCP in sequence in a reordering window. After PDU1 and PDCP PDU2, PDCP PDU3, PDCP PDU1, and PDCP PDU2 are reordered in order of SN being small to large. Since the SN of the PDCP PDU1 is 1, the SN of the PDCP PDU2 is 2, and the SN of the PDCP PDU3 is 3. Therefore, the PDCP entity 1 of the access network device ranks the PDCP PDU1 in the first place and the PDCP PDU2 in the second place. The PDCP PDU3 is placed in the third place.

It can be seen that by implementing the embodiment, the PDCP data packet can be reordered when receiving the out-of-order PDCP data packet, instead of reordering the PDCP data packet at any time.

Optionally, if the indication information indicates that the receiving end (such as the terminal device or the access network device) does not reorder the PDCP data packets received by the same radio bearer in an out-of-order manner, the receiving end receives the PDCP sent by the sending end. After the PDU is completed, after the operations such as decompression, decryption, and integrity protection authentication of the PDCP PDU are completed, the SN of the PDCP PDU does not need to be reordered. Instead, the PDCP SDU is directly passed to the upper layer, for example, the upper layer can be an application layer.

The lower edge variable RX_DELIV of the receiving end window of the receiving end can be updated according to the reordering timer. For example, one PDCP PDU corresponds to a COUNT value, which is a value consisting of the SN of the PDCP PDU and the superframe number HFN. When the reordering timer expires, the lower edge variable RX_DELIV should be updated to the COUNT value of the PDCP SDU that triggered the reordering timer, ie, the RX_REORD should be updated to the COUNT value of the PDCP SDU that is continuously delivered to the last position of the upper layer.

For example, as shown in FIG. 12, the initial RX_DELIV is RX_DELIV before packet 0. If packet 0 or packet 3 is not received, the reordering timer is triggered to start timing when the packet 6 is received. At this time, since RX_DELIV+1 is not received, that is, packet 0 is not received, the initial RX_DELIV is updated to the COUNT value corresponding to packet 6, and the COUNT value corresponding to packet 6 is RX_DELIV_2.

Another possible way is that when the receiving end receives the PDCP SDU with the COUNT value of RX_DELIV+1, the initial RX_DELIV can be updated to the COUNT value of the PDCP SDU that is continuously delivered to the last position of the upper layer starting from RX_DELIV+1.

For example, if RX_DELIV+1 is received, that is, the packet 0 is not received as shown in FIG. 12, the initial RX_DELIV is updated to the COUNT value corresponding to the packet 2, and the COUNT value corresponding to the packet 2 is RX_DELIV_1.

The embodiment of the present invention may divide the function module into the device according to the foregoing method example. For example, each function module may be divided according to each function, or two or more functions may be integrated into one module. The above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of the module in the embodiment of the present invention is schematic, and is only a logical function division, and the actual implementation may have another division manner.

Referring to FIG. 13, FIG. 13 is a transmitting end provided by an implementation of the present invention. The sending end includes: an obtaining module 1301 and a sending module 1302. among them:

The obtaining module 1301 is configured to acquire at least two PDCP data packets by the same packet data convergence protocol PDCP entity in one radio bearer, and the sending module 1302 is further configured to use the same radio link layer control protocol RLC entity corresponding to the PDCP entity. The PDCP data packet with the highest priority among the at least two PDCP data packets is sent first, and then the PDCP data packets with the lower priority among the at least two PDCP data packets are sent.

Optionally, the sequence number SN of the PDCP packet with a high priority is before the SN of the PDCP packet with a lower priority.

Optionally, the at least two PDCP data packets include the first PDCP data packet and the second PDCP data packet, and the first PDCP data packet has a higher priority than the second PDCP data packet. The processing module 1302 is configured to allocate a first SN to the first PDCP data packet, and the processing module 1302 is further configured to re-allocate the second SN to the second PDCP data packet, where the first SN is smaller than the second SN, and the communication module 1301 is configured to the PDCP entity. The corresponding radio link layer control protocol RLC entity first sends a PDCP data packet with a high priority among the at least two PDCP data packets, and then sends a PDCP data packet with a low priority among the at least two PDCP data packets. The at least two PDCP data packets are sent to the same RLC entity in the order of the first SN and the second SN.

Optionally, the obtained at least two PDCP data packets are at least two packet data convergence protocol service data units (PDCPs), and the sending end may further include a processing module, configured to determine a PDCP with a high priority among the at least two PDCP SDUs. The SDU and the PDCP SDU with a low priority; the sending module 1302 first sends the PDCP data packet with the highest priority in the at least two PDCP data packets to the same radio link layer control protocol RLC entity corresponding to the PDCP entity, and then sends at least two PDCP packets. The manner of the PDCP data packet with a lower priority in the data packet is specifically: the sending module 1302 is configured to first send the packet data convergence protocol protocol data unit PDCP PDU generated by the PDCP SDU with high priority to the same RLC entity, and then send the priority by using the PDCP PDU. PDCP PDU generated by a low PDCP SDU.

Optionally, the at least two PDCP data packets are PDCP data packets acquired within a preset time in a buffer of the sending end, or the at least two PDCP data packets are obtained in a preset amount within a buffer of the sending end. .

Optionally, the sending end is a terminal device, and the communications module 1301 is further configured to: first send a PDCP data packet with a high priority among the at least two PDCP data packets to the same radio link layer control protocol RLC entity corresponding to the PDCP entity, and then Before transmitting the PDCP data packet with the lower priority of the at least two PDCP data packets, the indication information sent by the access network device is used to indicate that the same RLC entity corresponding to the PDCP entity is allowed to send at least two PDCP data packets first. A medium-priority PDCP packet is sent, and then a PDCP packet with a lower priority among at least two PDCP packets is sent.

Optionally, the indication message is a radio resource control RRC configuration message, or the indication message is a PDCP indication message, or the indication message is a medium access control protocol MAC indication message.

Referring to FIG. 14, FIG. 14 is a receiving end provided by an implementation of the present invention. The receiving end includes a communication module 1401 and a processing module 1402. among them:

The communication module 1401 is configured to receive indication information from the first device, where the indication information is used to indicate that the packet data convergence protocol PDCP data packet that is sent out by the transmitting end by the same radio bearer is reordered; the communication module 1401 further The PDCP data packet is sent by the same PDCP entity in the out-of-order manner by the same radio bearer. The processing module 1402 is configured to reorder the PDCP data packets sent out of order by the same PDCP entity.

Optionally, the receiving end is a terminal device, and the first device and the sending end are access network devices. Or, the receiving end is an access network device, and the first device is a core network device CN, and the sending end is a terminal device.

Referring to FIG. 15, FIG. 15 is a schematic structural diagram of a transmitting end according to an embodiment of the present application. As shown in FIG. 15, the transmitting end 1500 includes a processor 1501, a memory 1502, and a communication interface 1503. The processor 1501, the memory 1502 and the communication interface 1503 are connected.

The processor 1501 may be a central processing unit (CPU), a general-purpose processor, a coprocessor, a digital signal processor (DSP), or an application-specific integrated circuit (ASIC). , field programmable gate array (FPGA) or other programmable logic device, transistor logic device, hardware component, or any combination thereof. The processor 1501 can also be a combination of computing functions, such as one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like.

The communication interface 1503 is used to implement communication with other network elements (such as the receiving end).

The processor 1501 invokes the program code stored in the memory 1502, and may perform the steps performed by the transmitting end described in FIG. 5 in the foregoing method embodiment, or other steps performed by the transmitting end in the method embodiment.

Referring to FIG. 16, FIG. 16 is a schematic structural diagram of a receiving end according to an embodiment of the present application. As shown in FIG. 16, the receiving end 1600 includes a processor 1601, a memory 1602, and a communication interface 1603. The processor 1601, the memory 1602, and the communication interface 1603 are connected.

The processor 1601 may be a central processing unit (CPU), a general-purpose processor, a coprocessor, a digital signal processor (DSP), or an application-specific integrated circuit (ASIC). , field programmable gate array (FPGA) or other programmable logic device, transistor logic device, hardware component, or any combination thereof. The processor 1601 can also be a combination of computing functions, such as one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like.

The communication interface 1603 is configured to implement communication with other network elements (such as a transmitting end).

The processor 1601 calls the program code stored in the memory 1602, and can perform the steps performed by the receiving end described in FIG. 9 in the foregoing method embodiment, or other steps performed by the receiving end in the method embodiment.

It can be understood that when the embodiment of the present application is applied to a transmitting end chip, the transmitting end chip implements the function of the transmitting end in the foregoing method embodiment. The transmitting end chip sends the first information to other modules in the transmitting end, such as the radio frequency module or the antenna, and receives the second information from other modules in the transmitting end. The first information is sent to the receiving end by other modules of the transmitting end, and the second information is sent by the receiving end to the transmitting end. When the embodiment of the present application is applied to a receiving end chip, the receiving end chip implements the function of the receiving end in the foregoing method embodiment. The receiving end chip receives the first information from other modules in the receiving end, such as a radio frequency module or an antenna, and sends the second information to other modules in the receiving end. The first information is sent by the sending end to the receiving end, and the second information is sent to the sending end. The first information and the second information herein do not specifically refer to a certain type of information, and are only used to characterize the communication mode between the chip and other modules.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, it may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present application are generated in whole or in part. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device. The computer instructions can be stored in or transmitted by a computer readable storage medium. The computer instructions can be from a website site, computer, server or data center to another website site by wire (eg, coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.) Transfer from a computer, server, or data center. The computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media. The usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, a Solid State Disk (SSD)) or the like.

Based on the same inventive concept, the principle of solving the problem of each device provided in the embodiment of the present application is similar to the method embodiment of the present application. Therefore, the implementation of each device may refer to the implementation of the method, and is not described here.

In the above embodiments, the descriptions of the various embodiments are different, and the details that are not detailed in a certain embodiment can be referred to the related descriptions of other embodiments.

Finally, it should be noted that the above embodiments are only for explaining the technical solutions of the present application, and are not limited thereto; although the present application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that 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 application. range.

Claims

A data processing method is applied to a transmitting end, and the method includes:

The same packet data convergence protocol PDCP entity in one radio bearer acquires at least two PDCP data packets;

Sending, by the same radio link layer control protocol RLC entity corresponding to the PDCP entity, a PDCP data packet with a high priority among the at least two PDCP data packets, and then transmitting the at least two PDCP data packets with a low priority PDCP packet.
The method according to claim 1, wherein the sequence number SN of the PDCP data packet with a high priority is before the SN of the PDCP data packet with a low priority.
The method according to claim 1 or 2, wherein the at least two PDCP data packets include a first PDCP data packet and a second PDCP data packet, and the first PDCP data packet has a higher priority than the second PDCP data packet. The priority of the PDCP packet, the method further includes:

Allocating a first SN to the first PDCP data packet;

Reassigning a second SN to the second PDCP data packet, the first SN being before the second SN;

Sending, to the same RLC entity corresponding to the PDCP entity, a PDCP data packet with a high priority among the at least two PDCP data packets, and then transmitting a PDCP data packet with a low priority among the at least two PDCP data packets. ,include:

And transmitting the at least two PDCP data packets to the same RLC entity in the order of the second SN after the first SN.
The method according to claim 1, wherein the acquired at least two PDCP data packets are at least two packet data convergence protocol service data units PDCP SDU, the method further comprising: determining the at least two a PDCP SDU with a higher priority and a PDCP SDU with a lower priority in the PDCP SDU;

Transmitting, by the same radio link layer control protocol RLC entity corresponding to the PDCP entity, a PDCP data packet with a high priority among the at least two PDCP data packets, and then transmitting the at least two PDCP data packets with a priority Low-level PDCP packets, including:

Transmitting, by the same RLC entity, a packet data convergence protocol protocol data unit PDCP PDU generated by the PDCP SDU with a higher priority, and then transmitting a PDCP PDU generated by a PDCP SDU having a lower priority.
The method according to any one of claims 1 to 4, wherein the at least two PDCP data packets are PDCP data packets acquired within a preset time in a buffer of the transmitting end, or the at least two The PDCP data packets are obtained within a preset amount of the buffer of the transmitting end.
The method according to any one of claims 1 to 5, wherein the transmitting end is a terminal device, and the at least two are sent to the same radio link layer control protocol RLC entity corresponding to the PDCP entity. Before the PDCP data packet with a high priority in the PDCP data packet is sent, and the PDCP data packet with a low priority among the at least two PDCP data packets is sent, the method further includes:

And receiving the indication information sent by the access network device, where the indication information is used to indicate that the same RLC entity corresponding to the PDCP entity is allowed to first send the PDCP data packet with the highest priority among the at least two PDCP data packets, and then send the a PDCP packet with a lower priority among the at least two PDCP data packets.
The method according to claim 6, wherein the indication message is a radio resource control RRC configuration message, or the indication message is a PDCP indication message, or the indication message is a medium access control protocol MAC indication message.
A data processing method is applied to a receiving end, and the method includes:

Receiving indication information from the first device, where the indication information is used to indicate whether to allow reordering of the packet data convergence protocol PDCP data packet that is sent out by the transmitting end by the same radio bearer;

If the indication information is used to indicate that the PDCP data packets that are sent by the transmitting end in the out-of-order manner by the same radio bearer are reordered, the transmitting end of the same PDCP entity is sent out in the same order by the same radio bearer. PDCP data packet;

And reordering the out-of-order PDCP data packets by the same PDCP entity.
The method of claim 8 wherein:

The receiving end is a terminal device, and the first device and the sending end are access network devices; or

The receiving end is an access network device, and the first device is a core network device CN, and the sending end is a terminal device.
The method according to claim 8 or 9, wherein the indication message is a radio resource control RRC configuration message, or the indication message is a PDCP indication message, or the indication message is a medium access control protocol MAC indication Message.
A transmitting end, wherein the sending end comprises:

An acquiring module, configured to acquire at least two PDCP data packets by a PDCP entity of the same packet data convergence protocol in a radio bearer;

The sending module is further configured to send, to the same radio link layer control protocol RLC entity corresponding to the PDCP entity, a PDCP data packet with a high priority among the at least two PDCP data packets, and then send the at least two PDCP packets. A PDCP packet with a lower priority in the packet.
The transmitting end according to claim 11, wherein the sequence number SN of the PDCP data packet with a high priority is before the SN of the PDCP data packet with a low priority.
The transmitting end according to claim 11 or 12, wherein the at least two PDCP data packets include a first PDCP data packet and a second PDCP data packet, and the first PDCP data packet has a higher priority than the first PDCP data packet. The priority of the second PDCP packet, where the sender further includes:

a processing module, configured to allocate a first SN to the first PDCP data packet;

The processing module is further configured to reallocate a second SN to the second PDCP data packet, where the first SN is before the second SN;

The sending module is configured to first send, to the same RLC entity corresponding to the PDCP entity, a PDCP data packet with a high priority among the at least two PDCP data packets, and then send the at least two PDCP data packets with a priority. Low-level PDCP packets, including:

And transmitting the at least two PDCP data packets to the same RLC entity in the order of the second SN after the first SN.
The sender according to claim 11, wherein the at least two PDCP data packets are the at least two packet data convergence protocol service data units (PDCPs), and the sender further comprises:

a processing module, configured to determine a PDCP SDU with a high priority among the at least two PDCP SDUs and a PDCP SDU with a low priority;

The sending module is configured to first send, to the same radio link layer control protocol RLC entity corresponding to the PDCP entity, a PDCP data packet with a high priority among the at least two PDCP data packets, and then send the at least two PDCP packets. The PDCP packets with low priority in the data packet include:

The sending module is configured to send, to the same RLC entity, a packet data convergence protocol protocol data unit PDCP PDU generated by the PDCP SDU with a higher priority, and then send a PDCP PDU generated by a PDCP SDU with a lower priority.
The transmitting end according to any one of claims 11 to 14, wherein the at least two PDCP data packets are PDCP data packets acquired within a preset time in a buffer of the transmitting end, or the at least Two PDCP data packets are acquired within a preset amount of the buffer of the transmitting end.
The transmitting end according to any one of claims 11 to 14, wherein the transmitting end is a terminal device,

The communication module is further configured to send, to the same radio link layer control protocol RLC entity corresponding to the PDCP entity, a PDCP data packet with a high priority among the at least two PDCP data packets, and then send the at least two And receiving, by the access network device, the indication information that is sent by the access network device, where the indication information is used to indicate that the at least two the same RLC entity corresponding to the PDCP entity is allowed to send the at least two A PDCP packet with a high priority in the PDCP packet, and then a PDCP packet with a lower priority among the at least two PDCP packets.
The transmitting end according to claim 16, wherein the indication message is a radio resource control RRC configuration message, or the indication message is a PDCP indication message, or the indication message is a medium access control protocol MAC indication message. .
A receiving end, wherein the receiving end comprises:

a communication module, configured to receive indication information from the first device, where the indication information is used to indicate whether to allow reordering of the packet data convergence protocol PDCP data packet sent by the sending end by the same radio bearer;

The communication module is further configured to: if the indication information is used to indicate that the PDCP data packet that is sent out by the sending end by the same radio bearer is reordered, the same PDCP entity receives the sending end through the same Transmitting, by the radio bearer, a PDCP data packet that is sent out of order;

And a processing module, configured to reorder the out-of-order PDCP data packets by the same PDCP entity.
The receiving end according to claim 18, wherein the receiving end is a terminal device, and the first device and the sending end are access network devices; or

The receiving end is an access network device, and the first device is a core network device CN, and the sending end is a terminal device.
The receiving end according to claim 18 or 19, wherein the indication message is a radio resource control RRC configuration message, or the indication message is a PDCP indication message, or the indication message is a medium access control protocol MAC Indicate the message.
A computer program product comprising instructions, comprising program code, causing a computer to perform the method of any of claims 1-10 when the program code is run on a computer.