WO2020224631A1

WO2020224631A1 - Method and apparatus for processing data packets

Info

Publication number: WO2020224631A1
Application number: PCT/CN2020/089099
Authority: WO
Inventors: 严乐; 曾清海; 张宏平; 耿婷婷
Original assignee: 华为技术有限公司
Priority date: 2019-05-08
Filing date: 2020-05-08
Publication date: 2020-11-12
Also published as: CN111918335A; CN111918335B

Abstract

The present application provides a method for processing data packets. Before performing header compression on received data packets, a receiving end obtains a PDCP sequence number of a data packet needing to be first header-decompressed in the data packets sent by a sending end, then errors due to performing header decompression on the data packets by the receiving end in the case that the data packets are out of order can be avoided, and thus the error rate of header decompression can be reduced.

Description

Method and device for processing data packet

This application claims the priority of the Chinese patent application filed with the State Intellectual Property Office on May 8, 2019, the application number is 201910381560.9, and the application name is "Method and Device for Processing Data Packets", the entire content of which is incorporated into this application by reference in.

Technical field

This application relates to the field of wireless communication technologies, and in particular to a method and device for processing data packets.

Background technique

In a traditional mobile communication system, as the terminal device moves, the network switches the terminal device from the source cell to the target cell for data transmission through a handover process. After the handover process is completed, the terminal device switches to the target base station for communication. In the handover process, after the source base station sends a handover message to the terminal device, the data transmission between the terminal device and the source base station is interrupted. After the terminal device successfully switches to the target base station, the terminal device can perform data transmission with the target base station. Resume data transfer.

In order to improve user experience and system performance, the third generation partnership project (3GPP) puts forward the requirement of 0ms handover interruption delay during handover, and provides a handover enhancement solution for this purpose, such as eMBB (enhanced make before break, MBB) solution. In the eMBB solution, after the terminal device receives the handover message from the source base station, on the one hand, the terminal device continues to maintain the user plane protocol stack corresponding to the source base station to maintain data transmission with the source base station. On the other hand, the terminal equipment establishes a protocol stack corresponding to the target base station for data transmission with the target base station. In addition, after the source base station sends the handover message to the terminal device, it can forward data with the target base station. Specifically, the source base station forwards the PDCP service data unit (service data unit, SDU) assigned with the packet data convergence protocol sequence number (packet data convergence protocol sequence number, PDCP SN) to the target base station. The target base station performs header compression and encryption on these PDCP SDUs. Once the terminal device successfully accesses the target base station, the target base station can send the PDCP SDU received from the source base station and processed by the target base station to the terminal device. As a result, a switching interruption delay of 0 ms can be achieved.

In the foregoing process, the target base station's header compression processing of the PDCP SDU is also called robust header compression (ROHC). ROHC is currently recognized as an ideal header compression method used on wireless links. After the transmitting end performs PDCP layer processing such as ROHC on the PDCP SDU, the PDCP protocol data unit (protocol data unit, PDU) is obtained, and the receiving end performs header decompression processing on the received PDCP PDU, which is called ROHC header decompression. ROHC header decompression requires PDCP PDU to be in order.

However, in many cases, the transmitter performs ROHC and other PDCP layer processing on the PDCP SDU and sends it to the receiver. The PDCP PDUs received by the receiver may be out of order, resulting in a high ROHC header decompression error rate.

Summary of the invention

The present application provides a method and device for processing data packets, which can reduce the error rate of ROHC header decompression.

In the first aspect, this application provides a method for processing data packets. The terminal device obtains the PDCP sequence number of the first packet that needs to be decompressed by the header among the data packets received from the first network device; the terminal Starting from the PDCP sequence number of the first data packet that needs to be decompressed by the header, the device performs header decompression processing on the data packet received from the first network device.

In the technical solution of this application, before decompressing the header of the received data packet, the receiving end can avoid the receiving end by obtaining the PDCP sequence number of the first data packet sent by the transmitting end that needs to be decompressed by the header. When the data packet is out of order, the header decompression process is performed on the data packet, which results in a header decompression error, thereby reducing the header decompression error rate.

With reference to the first aspect, in some implementations of the first aspect, the terminal device obtains the PDCP sequence number of the first data packet that needs to be decompressed by the header among the data packets received from the first network device, including: terminal device Receive first indication information from the second network device, where the first indication information is used to indicate the PDCP sequence number of the first data packet that needs to be decompressed by the header.

In one implementation, the first network device may be the target base station of the terminal device in the cell handover process, and the second network device may be the source base station.

During the handover process, the terminal device can obtain the PDCP sequence number of the data packet that needs to be decompressed by the first header from the source base station. In other words, the source base station can notify the terminal device that it needs the PDCP sequence number of the first packet whose header is decompressed, so that the terminal device can reorder the data packets received from the target base station from the PDCP sequence number, and follow the reorder Decompressing the header of the data packet in the order after sorting can reduce the error rate of header decompression.

With reference to the first aspect, in some implementations of the first aspect, the terminal device receives the first indication information from the second network device, including: the terminal device receives the radio resource control RRC reconfiguration message from the second network device, and the RRC reconfiguration The message carries one or more of the first indication information, where each first indication information is used to indicate the corresponding bearer PDCP sequence number of the first data packet that needs to be decompressed by the header; or, the terminal device A PDCP control protocol data unit PDU is received from the second network device, the PDCP control PDU carries the first indication information, wherein the first indication information is used to indicate the requirement of the bearer corresponding to the PDCP control PDU. The PDCP sequence number of a packet decompressed by the header.

With reference to the first aspect, in some implementations of the first aspect, the terminal device obtains the PDCP sequence number of the first data packet that needs to be decompressed by the header among the data packets received from the first network device, including: terminal device According to the first data packet received from the first network device, the PDCP sequence number of the first data packet that needs to be decompressed by the header is obtained, where the RLC sequence number of the first data packet is the preset RLC sequence number .

In this way, by presetting an RLC sequence number, when the terminal device parses the received data packet and determines that its RLC sequence number is the preset RLC sequence number, the PDCP obtained by parsing the data packet The sequence number is the PDCP sequence number of the first packet that needs to be decompressed by the header. In this way, interaction between network equipment and terminal equipment can be avoided, and signaling overhead can be saved.

With reference to the first aspect, in some implementation manners of the first aspect, the preset RLC sequence number is 0.

With reference to the first aspect, in some implementations of the first aspect, the terminal device headers the data packet received from the first network device according to the PDCP sequence number of the first header decompressed data packet. The decompression process includes: according to the PDCP sequence number of the first data packet that needs to be decompressed by the header, the terminal device determines the data packet received from the first network device from the first data packet that needs to be decompressed by the header. Start with the data packet corresponding to the PDCP sequence number of the data packet, reorder the data packets received from the first network device, and perform header decoding on the data packets received from the first network device in the order after the reordering compression.

In a second aspect, the present application provides a method for processing data packets. A second network device generates first indication information. The first indication information is used to indicate that the terminal device needs the first indication information among the data packets received from the first network device. The PDCP sequence number of each packet decompressed by the header; the second network device sends the first indication information to the terminal device.

Here, the second network device may correspond to the source base station of the terminal device in the cell handover process.

With reference to the second aspect, in some implementation manners of the second aspect, the second network device sending the first indication information to the terminal device includes: the second network device sends an RRC reconfiguration message to the terminal device, the RRC reconfiguration message Carries one or more of the first indication information, each of the first indication information is used to indicate the packet data convergence protocol PDCP sequence number of the corresponding bearer that requires the first packet to be decompressed by the header; or, 2. The network device sends a packet data convergence protocol PDCP control protocol data unit PDU to the terminal device, the PDCP control PDU carries the first indication information, and the first indication information is used to indicate the bearer corresponding to the PDCP control PDU The PDCP sequence number of the first packet that needs to be decompressed by the header.

In the third aspect, this application provides a method for processing data packets. The first network device obtains the PDCP sequence number of the first data packet that needs to be decompressed by the header among the data packets received from the terminal device; Starting with the PDCP sequence number of the first data packet that needs to be decompressed by the header, header decompression processing is performed on the data packet received from the terminal device.

Here, the first network device may correspond to the target base station of the terminal device in the cell handover process.

With reference to the third aspect, in some implementations of the third aspect, the first network device obtains the PDCP sequence number of the first data packet that needs to be decompressed by the header among the data packets received from the terminal device, including: The network device receives second indication information from the terminal device, where the second indication information is used to indicate the PDCP sequence number of the first data packet that needs to be decompressed by the header among the data packets sent by the terminal device.

With reference to the third aspect, in some implementations of the third aspect, the first network device receiving the second indication information from the terminal device includes: the first network device receives an RRC reconfiguration complete message from the terminal device, the RRC reconfiguration The completion message carries one or more of the second indication information, where each second indication information is used to indicate the PDCP sequence number of the corresponding bearer that requires the first header decompressed data packet; or A network device receives a PDCP status report from a terminal device, and the PDCP status report carries the second indication information, where the second indication information is used to indicate the needs of the bearer corresponding to the PDCP status report. The PDCP sequence number of the data packet decompressed by the header; or, the first network device receives the packet data convergence protocol PDCP control protocol data unit PDU from the terminal device, and the PDCP control PDU carries the second indication information, wherein, The second indication information is used to indicate the PDCP sequence number of the first data packet that needs to be decompressed by the header of the bearer corresponding to the PDCP control PDU.

With reference to the third aspect, in some implementations of the third aspect, the first network device obtains the first data packet that needs to be decompressed by the header among the data packets received from the terminal device, including: The second data packet received by the terminal device obtains the PDCP sequence number of the first data packet that needs to be decompressed by the header, where the radio link control RLC sequence number of the second data packet is the preset RLC sequence number .

With reference to the third aspect, in some implementation manners of the third aspect, the preset RLC sequence number is 0.

With reference to the third aspect, in some implementations of the third aspect, the method further includes: the first network device sends a first message to the second network device, where the first message is used to indicate the need to be the first to be The PDCP sequence number of the data packet whose header is decompressed; the first network device starts with the data packet corresponding to the PDCP sequence number of the first data packet that needs to be decompressed by the header, and headers the data packet received from the terminal device The decompression process includes: when the first network device receives one or more data packets from the terminal device, the first network device sends the one or more data packets to the second network device; The device receives the one or more data packets after the reordering, and performs header decompression processing on the one or more data packets in the order after the reordering, wherein the one or more data packets are It is reordered starting from the PDCP sequence number of the first packet that needs to be decompressed by the header.

With reference to the third aspect, in some implementations of the third aspect, the method further includes: the first network device sends a first message to the second network device, where the first message is used to indicate the need to be the first to be The PDCP sequence number of the header decompressed data packet; when the first network device receives one or more data packets from the terminal device, the first network device sends the PDCP sequence of the one or more data packets to the second network device Number; the first network device receives a second message from the second network device, the second message is used to indicate whether to allow header decompression of the data packet corresponding to the one or more PDCP sequence numbers, where the The second message is generated according to the first message and the one or more PDCP sequence numbers; and, the first network device receives the PDCP sequence number of the first packet that needs to be decompressed by the header, and responds to the slave Decompressing the header of the data packet received by the terminal device includes: the first network device starts from the data packet corresponding to the PDCP sequence number of the first data packet that needs to be decompressed by the header, and performs processing on the second message. Header decompression is performed on the indicated data packet that is allowed to be decompressed by the header, and header decompression is not performed on the data packet that is not allowed to be decompressed by the header indicated by the second message.

With reference to the third aspect, in some implementation manners of the third aspect, the first network device headers the data packet received from the terminal device according to the PDCP sequence number of the first header decompressed data packet. Decompression processing includes: when the first network device receives the data packet that needs to be decompressed by the first header, the first network device sends the data that needs to be decompressed by the first header to the second network device Packet, and after sending the data packet that needs to be decompressed by the first header, it sends other data packets received from the terminal device to the second network device; the first network device receives all the reordered data packets from the second network device The first data packet that needs to be decompressed by the header and the other data packets; the first network device performs processing on the data packet that needs to be decompressed by the first header and the other data packets in the order after reordering Header decompression processing.

With reference to the third aspect, in some implementation manners of the third aspect, the first network device headers the data packet received from the terminal device according to the PDCP sequence number of the first header decompressed data packet. Decompression processing includes: when the first network device receives the data packet that needs to be decompressed by the first header, the first network device sends the data that needs to be decompressed by the first header to the second network device The PDCP sequence number of the packet, and the PDCP sequence number of one or more data packets received from the terminal device is sent to the second network device after the first data packet that needs to be decompressed by the header; the first network device Receive a second message from the second network device, where the second message is used to indicate whether the first network device is allowed to decompress the header of the data packet corresponding to the one or more PDCP sequence numbers; the first network device is based on In the second message, header decompression processing is performed on the data packet that needs to be decompressed by the first header and the one or more data packets.

In a fourth aspect, this application provides a method for processing data packets, including: a second network device obtains the PDCP sequence number of the first data packet that needs to be decompressed by the header among the data packets sent by the terminal device; The PDCP sequence number of the first data packet that needs to be decompressed by the header assists the first network device to perform header decompression processing on the data packet received from the terminal device.

With reference to the fourth aspect, in some implementations of the fourth aspect, the second network device obtains the PDCP sequence number of the first data packet that needs to be decompressed by the header among the data packets sent by the terminal device, including: the second network device A first message is received from the first network device, where the first message is used to indicate the PDCP sequence number of the first data packet that needs to be decompressed by the header; the second network device is the first to be decompressed according to the need. The PDCP sequence number of the compressed data packet to assist the first network device in performing header decompression processing on the data packet received from the terminal device includes: the second network device receives one or more data packets from the first network device; second According to the first message, the network device starts from the data packet corresponding to the PDCP sequence number of the first data packet that needs to be decompressed by the header for the one or more data packets received from the first network device. The data packets received from the first network device are reordered, and the reordered data packets are sent to the first network device for header decompression processing.

With reference to the fourth aspect, in some implementation manners of the fourth aspect, the second network device assists the first network device to receive data from the terminal device according to the PDCP sequence number of the data packet that needs to be decompressed by the first header. The header decompression processing of the data packet includes: the second network device receives a first message from the first network device, the first message is used to indicate the PDCP sequence number of the first data packet that needs to be decompressed by the header The second network device receives one or more PDCP sequence numbers from the first network device; the second network device determines whether to allow the first network device to correspond to the one or more PDCP sequence numbers according to the first message The data packet is header decompressed; the second device sends a second message to the first network device, the second message is used to indicate whether the first network device is allowed to check the corresponding one or more PDCP sequence numbers The packet is header decompressed.

With reference to the fourth aspect, in some implementations of the fourth aspect, the second network device obtains the PDCP sequence number of the first data packet that needs to be decompressed by the header among the data packets sent by the terminal device, including: the second network device Receive the data packet corresponding to the first PDCP sequence number from the first network device, and receive other data packets from the first network device after receiving the data packet corresponding to the first PDCP sequence number; the second network device receives the data packet from the first network device A PDCP sequence number starts to reorder the data packets corresponding to the first PDCP sequence number and the other data packets, and reorder the data packets corresponding to the first PDCP sequence number and the other data packets Send it to the first network device for header decompression processing.

Here, the data packet corresponding to the first PDCP sequence number is the first data packet received by the second network device from the first network device, and the data packet corresponding to the first PDCP sequence number is the first header that needs to be Uncompressed data package.

With reference to the fourth aspect, in some implementations of the fourth aspect, the second network device obtains the PDCP sequence number of the first data packet that needs to be decompressed by the header among the data packets sent by the terminal device, including: the second network device Receive a second PDCP sequence number from the first network device, and the second PDCP sequence number is preset to be the PDCP sequence of the first data packet that needs to be decompressed by the header among the data packets received by the first network device from the terminal device The second network device assists the first network device to perform header decompression processing on the data packet received from the terminal device according to the PDCP sequence number of the first header decompressed data packet, including: the second network The device receives one or more data packets from the first network device; the second network device reorders the one or more data packets starting from the data packet corresponding to the second PDCP sequence number, and after the reordering The data packet corresponding to the second PDCP sequence number and the one or more data packets are sent to the first network device for header decompression processing.

Here, the second PDCP sequence number is the first PDCP sequence number received by the second network device from the first network device, and the data packet corresponding to the second PDCP sequence number is the data packet that needs to be decompressed by the first header data pack.

It should be noted that the number "second" of the second PDCP serial number is only to distinguish it from the number "first" of the first PDCP serial number above, and should not constitute a limitation on the technical solution.

In a fifth aspect, the present application provides a method for processing data packets. A terminal device generates second indication information. The second indication information is used to indicate that the first data packet sent by the terminal device needs to be decoded by the first network device header. The PDCP sequence number of the compressed data packet; the terminal device sends the second indication information to the first network device.

With reference to the fifth aspect, in some implementations of the fifth aspect, the terminal device sending the second indication information to the first network device includes: the terminal device sends an RRC reconfiguration complete message to the first network device, and the RRC The reconfiguration complete message carries one or more of the second indication information, where each second indication information is used to indicate the PDCP sequence number of the corresponding bearer that requires the first header decompressed data packet; or , The terminal device sends a PDCP status report to the first network device, the PDCP status report carries the second indication information, where the second indication information is used to indicate that the corresponding bearer needs to be resolved by the first header The PDCP sequence number of the compressed data packet; or, the terminal device sends a PDCP control PDU to the first network device, and the PDCP control PDU carries the second indication information, where the second indication information is used to indicate the The PDCP control PDU bears the PDCP sequence number of the first data packet that needs to be decompressed by the header.

In a sixth aspect, the present application provides a communication device that has the function of implementing the method in the first aspect or any of its possible implementations, or the communication device has the function of implementing the fifth aspect or any of its possible implementations. The function of the method in the realization mode. The function can be realized by hardware, or by hardware executing corresponding software. The hardware or software includes one or more units corresponding to the above functions.

In a seventh aspect, this application provides a communication device that has the function of implementing the method in the second aspect or any of its possible implementations, or the communication device has the ability to implement the fourth aspect or any of its possible implementations The function in the way of the method. The function can be realized by hardware, or by hardware executing corresponding software. The hardware or software includes one or more units corresponding to the above functions.

In an eighth aspect, the present application provides a communication device that has a function of implementing the method in the third aspect or any possible implementation manner thereof. The function can be realized by hardware, or by hardware executing corresponding software. The hardware or software includes one or more units corresponding to the above functions.

In a ninth aspect, this application provides a terminal device including a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to make the terminal device execute the method in the first aspect or any of its possible implementations, or make the terminal device execute the fifth aspect or any of its possible methods The method in the implementation.

In a tenth aspect, this application provides a network device including a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory, so that the network device executes the method in the second aspect or any possible implementation manner thereof, or executes the fourth aspect or any possible implementation manner thereof Method in.

Here, the network device of the tenth aspect may be the first network device in this application.

In an eleventh aspect, this application provides a network device including a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory, so that the network device executes the method in the third aspect or any possible implementation manner thereof.

Here, the network device of the eleventh aspect may be the second network device in this application.

In a twelfth aspect, this application provides a computer-readable storage medium having computer instructions stored in the computer-readable storage medium. When the computer instructions run on a computer, the computer executes the first aspect or any possible implementation thereof. Or make a computer execute the method in the fifth aspect or any possible implementation manner thereof.

In a thirteenth aspect, this application provides a computer-readable storage medium having computer instructions stored in the computer-readable storage medium. When the computer instructions run on a computer, the computer executes the second aspect or any possible implementation thereof The function of the method in the manner, or the method of performing the fourth aspect or any possible implementation manner thereof.

In a fourteenth aspect, this application provides a computer-readable storage medium having computer instructions stored in the computer-readable storage medium. When the computer instructions run on a computer, the computer executes the third aspect or any possible implementation thereof The method in the way.

In a fifteenth aspect, this application provides a chip including a processor. The processor is configured to read and execute the computer program stored in the memory to execute the method in the first aspect or any possible implementation manner thereof, or execute the method in the fifth aspect or any possible implementation manner thereof.

Optionally, the chip further includes a memory, and the memory and the processor are connected to the memory through a circuit or a wire.

Further optionally, the chip further includes a communication interface.

In a sixteenth aspect, this application provides a chip including a processor. The processor is used to read and execute a computer program stored in the memory to execute the method in the second aspect or any possible implementation manner thereof, or execute the method in the fourth aspect or any possible implementation manner thereof.

Further optionally, the chip further includes a communication interface.

In a seventeenth aspect, this application provides a chip including a processor. The processor is used to read and execute the computer program stored in the memory to execute the method in the third aspect or any possible implementation manner thereof.

Further optionally, the chip further includes a communication interface.

In an eighteenth aspect, this application provides a computer program product. The computer program product includes computer program code. When the computer program code runs on a computer, the computer executes the first aspect or any of its possible implementations. , Or execute the method in the fifth aspect or any of its possible implementation manners.

In a nineteenth aspect, this application provides a computer program product. The computer program product includes computer program code. When the computer program code runs on a computer, the computer executes the second aspect or any of its possible implementations. , Or execute the method in the fourth aspect or any of its possible implementation manners.

In a twentieth aspect, this application provides a computer program product. The computer program product includes computer program code. When the computer program code runs on a computer, the computer executes the third aspect or any of its possible implementations. Methods.

Description of the drawings

Fig. 1 is an architecture diagram of a communication system applicable to an embodiment of the present application.

Figure 2 is a schematic diagram of the handover process in the eMBB solution.

Figure 3 is a schematic diagram of the functional modules of the PDCP layer.

Figure 4 is a schematic diagram of a user plane protocol stack of a network device.

Figure 5 is a schematic diagram of a user plane protocol stack of the UE.

Fig. 6 is a schematic diagram of another user plane protocol stack of the UE.

FIG. 7 is a schematic diagram of the first network device and the second network device each having a reordering function module.

Fig. 8 is a schematic diagram of the first network device and the second network device sharing a reordering function module.

FIG. 9 is a schematic diagram of a communication device 500 provided by this application.

FIG. 10 is a schematic diagram of a communication device 600 provided by this application.

FIG. 11 is a schematic diagram of a communication device 700 provided by this application.

FIG. 12 is a schematic structural diagram of a terminal device provided by this application.

FIG. 13 is a schematic structural diagram of a network device provided by this application.

FIG. 14 is a schematic structural diagram of a network device provided by this application.

Detailed ways

The technical solution in this application will be described below in conjunction with the drawings.

The technical solutions of the embodiments of this application can be applied to various communication systems, for example, long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, and LTE time division duplex (time division duplex) systems. , TDD), universal mobile telecommunication system (UMTS), worldwide interoperability for microwave access (WiMAX) communication system, the future 5th generation (5G) system or new wireless ( new radio, NR) etc.

The terminal equipment in the embodiments of this application may refer to user equipment, access terminals, user units, user stations, mobile stations, mobile stations, remote stations, remote terminals, mobile equipment, user terminals, terminals, wireless communication equipment, user agents, or User device. The terminal device can also be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), with wireless communication Functional handheld devices, computing devices, or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminal devices in the future 5G network or future evolution of the public land mobile network (PLMN) Terminal equipment, etc., this application is not limited to this.

The network device in the embodiment of the present application may be any device with a wireless transceiver function. The network equipment includes but is not limited to: evolved Node B (eNB), radio network controller (RNC), node B (Node B, NB), base station controller (base station controller, BSC), base transceiver station (base transceiver station, BTS), home base station (home evolved NodeB, or home Node B, HNB), baseband unit (BBU), wireless fidelity (wireless fidelity, WIFI) system Access point (access point, AP), wireless relay node, wireless backhaul node, transmission point (transmission point, TP), or transmission and reception point (transmission and reception point, TRP), etc., can also be the fifth generation (the fifth generation (5G) system, for example, gNB or transmission point (TRP or TP) in the new radio (NR), one or a group (including multiple antenna panels) antenna panels of the base station in the 5G system, or It may also be a network node that constitutes a gNB or a transmission point, such as a baseband unit (building baseband unit, BBU) or a distributed unit (DU), etc.

In some deployments, the gNB may include a centralized unit (CU) and a distributed unit (DU). The gNB may also include an active antenna unit (AAU). CU implements part of the functions of gNB, and DU implements part of the functions of gNB. For example, the CU is responsible for processing non-real-time protocols and services, and implements radio resource control (radio resource control, RRC), packet data convergence protocol (packet data convergence protocol, PDCP) layer functions. The DU is responsible for processing physical layer protocols and real-time services, and realizes the functions of the radio link control (RLC) layer, media access control (MAC) layer, and physical (PHY) layer. AAU realizes some physical layer processing functions, radio frequency processing and related functions of active antennas. Since the information of the RRC layer will eventually become the information of the PHY layer, or be transformed from the information of the PHY layer, under this architecture, high-level signaling, such as RRC layer signaling, can also be considered to be sent by DU , Or, sent by DU and AAU.

It is understandable that the network device may be a device including one or more of CU, DU, and AAU. In addition, the CU can be divided into network equipment in an access network (radio access network, RAN), and the CU can also be divided into network equipment in a core network (core network, CN), which is not limited in this application.

Referring to FIG. 1, FIG. 1 is an architecture diagram of a communication system applicable to an embodiment of the present application. As shown in FIG. 1, the wireless communication system may include a network device 101 and a network device 102, and one or more terminal devices 103. When the network device 101 or the network device 102 sends a signal, the network device is the transmitting end, and the terminal device 103 is the receiving end. Conversely, when the terminal device 103 sends a signal, the terminal device is the transmitting end, and the network device 101 and/or the network device 102 is the receiving end.

The technical solution of the present application is applicable to scenarios where terminal devices perform handover.

In a traditional handover process, after the source base station sends a handover message to the UE, data transmission between the UE and the source base station will be interrupted until the UE successfully switches to the target base station, and the UE can perform data transmission with the target base station. Specifically, after the UE successfully accesses the target base station, the UE sends an RRC reconfiguration complete message to the target base station. At this time, the air interface can resume data transmission. Therefore, there is an interruption delay during the handover.

In order to improve user experience, 3GPP puts forward the requirement of 0ms mobile interruption delay during handover. In order to realize the 0ms handover interruption delay, the eMBB scheme is proposed for this.

Refer to Figure 2, which is a schematic diagram of the handover process in the eMBB solution. In the handover process proposed by the eMBB solution, after the source base station sends a handover message to the UE, it can perform data forwarding with the target base station. That is, the source base station forwards the PDCP service data unit (service data unit, SDU) assigned to the packet data convergence protocol sequence number (packet data convergence protocol sequence number, PDCP SN) to the target base station, that is, the source base station sends the PDCP to the target base station. SDU(s) and the PDCP SN corresponding to each PDCP SDU. Among them, each PDCP SDU assigned to the PDCP SN is associated with a PDCP SN. These PDCP SDUs forwarded to the target base station are processed by the target base station for header compression, encryption, and PDCP header addition. The description of other steps in FIG. 2 can refer to the prior art.

In addition, the eMBB handover process shown in FIG. 2 is merely an example. Optionally, the handover process may also include other steps besides the steps shown in FIG. 2, or, the steps shown in FIG. 2 may execute part but not all of the steps.

In order to facilitate the understanding of the technical solution of the present application, the existing PDCP layer will be introduced below in conjunction with FIG. 3.

Refer to Figure 3, which is a schematic diagram of the functional modules of the PDCP layer. Figure 3 shows the PDCP entity at the transmitting end and the PDCP entity at the receiving end. The PDCP entity at the sending end can perform PDCP SN allocation, header compression, integrity protection, encryption, PDCP header addition (add PDCP header), routing/copying, etc. The PDCP entity at the receiving end can perform PDCP header removal, decryption, and integrity verification , Reordering, copy discarding, header decompression and other processing. It should be understood that in downlink data transmission, the PDCP entity at the transmitting end is the PDCP entity of the network device, and the PDCP entity at the receiving end is the PDCP entity of the terminal device. In uplink data transmission, the PDCP entity at the transmitting end is the PDCP entity of the terminal device, and the PDCP entity at the receiving end is the PDCP entity of the network device.

For the downlink (DL), the network device serves as the sender of the data packet, and its user plane protocol stack architecture can be seen in Figure 4.

Since the PDCP layer is a bearer granularity, each bearer has a corresponding PDCP layer. Referring to Figure 4, taking a bearer as an example, Figure 4 is a schematic diagram of a user plane protocol stack of a network device. The PDCP layer of the network device (for example, the source base station shown in Figure 4) generates the sequence numbering of the data packet, which is the above PDCP SN, or in other words, performs the PDCP SN allocation and performs the data packet Operations such as header compression, integrity protection, ciphering, and PDCP header addition (add PDCP header) are then submitted to the RLC layer. After being processed by RLC, MAC layer, and PHY layer in turn, it is sent to the terminal device.

It should be noted that Fig. 4 is only an example. The PDCP layer of the source base station or the target base station shown in Figure 4 may also include integrity protection (when used as a sender), integrity verification (when used as a receiver), and PDCP header addition ( add PDCP header, routing/duplication, reordering, duplicate discarding and other functional modules. These functional modules can be referred to as shown in FIG. 3, but not shown in FIG. 4. Among them, the routing/replication module in FIG. 4 is different from that in FIG. 3, which will be described in the following embodiments.

In the data transmission process, in order to improve the reliability of data transmission, in an optional implementation manner, the network device may perform duplication processing or duplication operation on the data packet. In this article, the duplication of downlink data packets is called DL duplication. For the downlink, the replication process refers to a certain PDCP SN (the PDCP SN is allocated by the source base station), and the source base station can generate 2 PDCP SDUs. In other words, the source base station generates two PDCP SDUs corresponding to the same PDCP SN. Among them, a PDCP SDU is passed to the source base station's own compression, encryption and other functional modules. After the source base station's header compression (such as ROHC) context is used for header compression and the source base station's key for encryption, the source base station sends it to UE. Another PDCP SDU (and the PDCP SN corresponding to the PDCP SDU) is forwarded by the source base station to the target base station, and uses the target base station's header compression (such as ROHC) context for header compression and the target base station's key for encryption, etc., to generate PDCP PDU. Once the UE successfully accesses the target base station, for example, the target base station receives the RRC reconfiguration complete message sent by the UE, the target base station can send the PDCP PDU received from the source base station and processed by the target base station to the UE.

From the perspective of the UE, after receiving the handover message from the source base station, the UE maintains data transmission with the source base station on the one hand, that is, maintains the user plane protocol stack corresponding to the source base station, and does not perform layer 2 on the user plane protocol stack of the source base station. Reset (reset) or re-establishment (re-establishment). It should be understood that layer 2 includes a MAC layer, an RLC layer, and a PDCP layer. On the other hand, the UE establishes a protocol stack of the target base station for initiating RACH and data transmission to the target. In an optional implementation manner, the UE may perform duplication processing or duplication operation on the data packet. In this article, the duplication of uplink data packets is called UL duplication. For the uplink, the replication process refers to a certain PDCP SN (the PDCP SN is allocated by the UE), and the UE can generate 2 PDCP SDUs. In other words, the UE generates two PDCP SDUs corresponding to the same PDCP SN. Among them, a PDCP SDU is transferred to the corresponding source base station's header compression, encryption and other functional modules. After the header compression (such as ROHC) context of the source base station is used for header compression and the source base station key is used for encryption, the UE sends it to Source base station. Another PDCP SDU is passed to the corresponding target base station's header compression, encryption and other functional modules, and the target base station's header compression (such as ROHC) context is used for header compression and the target base station's key for encryption, etc., to generate PDCP PDU, and the UE will Send to the target base station.

After the UE receives the handover message and before the UE releases the connection with the source base station, the UE maintains two sets of security contexts corresponding to the source base station and the target base station (or maintains two security keys, such as the key of the source base station and the target base station. Key), or the UE maintains two sets of header compression (such as ROHC) contexts corresponding to the source base station and the target base station respectively. The UE uses the corresponding security context (or key) for decryption according to whether the received data packet is from the source base station or the target base station, and uses the corresponding header decompression context to perform header decompression and other processing.

After the UE successfully switches to the target base station and the UE releases the connection with the source base station, the UE can perform uplink data transmission with the source base station and the target base station respectively. Optionally, the transmission may be a UL duplication data packet or not a UL duplication data packet. The UE will use the ROHC context of the source base station for header compression, use the key of the source base station for encryption and other processing, and then send the PDCP PDU to the RLC layer, MAC layer and PHY layer of the source base station. The UE will use the ROHC context of the target base station for header compression, use the key of the target base station for encryption and other processing, and then send the PDCP PDU to the RLC layer, MAC layer and PHY layer of the target base station.

Take the uplink (UL) data transmission as an example, the UE as the sender, taking a bearer as an example, its user plane protocol stack architecture can be similar to the protocol stack architecture of the network side downlink data transmission, see figure 5 shown.

Refer to Figure 5, which is a schematic diagram of a user plane protocol stack of the UE. Corresponding to a certain bearer, in Figure 5, the UE has two PDCP layers. One PDCP layer corresponds to the source base station, and the other PDCP layer corresponds to the target base station. For example, in the protocol stack architecture shown in Figure 5, if the UE performs a duplication operation on UL data packets, for the same PDCP SN, the two PDCP layers have their own corresponding PDCP SDUs. Among them, the PDCP layer corresponding to the source base station uses the header compression context of the source base station for header compression, uses the key of the source base station for encryption and other processing to generate PDCP PDU, and the PDCP layer corresponding to the target base station uses the header compression context of the target base station for header compression. After compression, use the key of the target base station for encryption and other processing to generate PDCP PDU. The protocol stacks on the left (for example, PHY1, MAC1, RLC1) in FIG. 5 can correspond to the target base station, and the protocol stacks on the right (for example, PHY2, MAC2, RLC2) can correspond to the source base station.

The header addition in Figure 5 refers to the PDCP header addition.

In addition, it should be understood that when the UE is used as the transmitting end, corresponding to a certain bearer, the two PDCP entities (or PDCP layers) of the UE shown in FIG. 5 may be transmitting PDCP entities (or PDCP layers). Wherein, the sending PDCP entity may also include functional modules such as integrity protection, PDCP header addition (add PDCP header), routing/duplication, etc. In Figure 5, routing/duplication The functional module of) is located in the PDCP entity corresponding to the source base station. When the UE serves as the receiving end, corresponding to a certain bearer, the two PDCP entities (or PDCP layers) of the UE shown in FIG. 5 can be the receiving PDCP entity (or PDCP layer), and the receiving PDCP entity can also include integrity verification (integrity verification). Verification), PDCP header removal (remove PDCP header), reordering (reordering), copy discarding and other functional modules. These functional modules can be referred to as shown in FIG. 3, but not shown in FIG. 5.

Optionally, corresponding to a certain bearer, there is a PDCP layer on the UE side (for example, the PDCP layer is called common PDCP). The PDCP layer corresponds to both the source base station and the target base station. In this case, the user plane protocol stack of the UE can be referred to Shown in Figure 6.

As shown in Figure 6, Figure 6 is a schematic diagram of another user plane protocol stack of the UE. The common PDCP shown in FIG. 6 maintains two sets of security contexts (and the common PDCP maintains two sets of header compression contexts). Optionally, the UE performs UL duplication. Specifically, under the protocol stack architecture shown in Figure 6, if the UE performs duplication operations on UL data packets, for the same PDCP SN, the common PDCP layer uses the header compression context corresponding to the source base station for header compression and uses the source base station's key After encryption and other processing, a PDCP PDU is generated. At the same time, the common PDCP layer uses the header compression context corresponding to the target base station to perform header compression and uses the key of the target base station for encryption and other processing to generate another PDCP PDU, namely For a certain PDCP SN, the UE generates 2 PDCP PDUs corresponding to the same PDCP SN. The UE uses the ROHC context of the source base station for header compression, and uses the key of the source base station for encryption and other processing and sends the data packet to the source base station. In addition, the UE sends to the target base station the data packet after header compression using the ROHC context of the target base station and encryption using the key of the target base station.

In addition, when the UE serves as the transmitting end, corresponding to a certain bearer, the PDCP entity (or PDCP layer) shown in FIG. 6 may be the transmitting PDCP entity (or PDCP layer). Wherein, the sending PDCP entity may also include functional modules such as integrity protection, PDCP header addition (add PDCP header), routing/duplication, and so on. When the UE serves as the receiving end, corresponding to a certain bearer, the PDCP entity (or PDCP layer) shown in Figure 6 can be the receiving PDCP entity (or PDCP layer), and the receiving PDCP entity can also include integrity verification, PDCP Functional modules such as remove PDCP header, reordering, and copy discarding. These functional modules can be referred to as shown in FIG. 3, but not shown in FIG. 6.

The user plane protocol stack architecture of the network equipment and UE given in Figure 4 to Figure 6 above is only an example. The technical solution of the present application does not limit the use of other protocol stack architectures or variations thereof, as long as the network side or the UE side is guaranteed The data can be transmitted through two legs to achieve a 0ms switching interruption delay, which is applicable in the technical solutions of this application.

From the perspective of the network side, the source base station decrypts the PDCP PDU received from the UE using the key of the source base station, and uses the header decompression context of the source base station to decompress the header. The target base station decrypts the PDCP PDU received from the UE using the key of the target base station, and uses the header decompression context of the target base station to perform header decompression.

However, the RLC layer at the receiving end does not guarantee that the data packets will be delivered to the PDCP layer in order. Therefore, if the data packets are out of order before header decompression, the error rate of header decompression will be very high.

For this reason, this application proposes a method for processing data packets, which aims to reduce the error rate of header decompression.

The technical solution of the present application is applicable to both uplink data transmission and downlink data transmission, which will be described separately below.

First, it should be noted that the first network device and the second network device in this application are merely examples of network side devices. For example, the first network device may be the target base station of the terminal device in the handover process, and the second network device may be the source base station in the handover process.

Downlink data transmission

510. The terminal device obtains the packet data convergence protocol sequence number (PDCP sequence, PDCP SN) of the first data packet that needs to be decompressed by the header among the data packets received from the first network device.

The terminal device can obtain the PDCP sequence number of the first data packet that needs to be decompressed by the header in multiple ways. Several methods are listed below for illustration.

Way 1

The terminal device receives the first indication information from the second network device. The first indication information is used to indicate the PDCP sequence number of the first data packet decompressed by the header among the data packets received by the terminal device from the first network device.

From the perspective of the second network device, the second network device generates the first indication information and sends the first indication information to the terminal device.

In an implementation manner, the second network device sends a radio resource control (radio resource control, RRC) reconfiguration message to the terminal device, and the RRC reconfiguration message carries one or more first indication information. Each first indication information is used to indicate the PDCP sequence number of the first data packet that needs to be decompressed by the header among the data packets transmitted on the bearer corresponding to the first indication information. For example, each first indication information is the PDCP sequence number of the first data packet that needs to be decompressed by the header among the data packets transmitted on the bearer corresponding to the first indication information.

It should be noted that the PDCP sequence number is based on the granularity of the radio bearer (data radio bearer, DRB), where the RB can include data radio bearer (DRB) and signaling radio bearer (signalling radio bearer, SRB) . Therefore, the first indication information carried in the RRC reconfiguration message is also based on radio bearer granularity. Different bearers have their own corresponding PDCP sequence numbers that need to be decompressed by the header.

Optionally, the PDCP sequence numbers of the data packets that need to be decompressed by the first header of different bearers may be the same or different.

Therefore, if the RRC reconfiguration message carries multiple first indication information, each first indication information corresponds to a different bearer. Therefore, the PDCP sequence number indicated by each first indication information is the PDCP sequence number of the first data packet that needs to be decompressed by the header of the bearer corresponding to the first indication information.

Optionally, when the RRC reconfiguration message carries multiple first indication information, each first indication information is associated with an RB identity, indicating that the PDCP sequence number indicated by the first indication information is the RB identity. The PDCP sequence number of the first packet decompressed by the header is required on the corresponding RB. That is, optionally, the RRC reconfiguration message includes the first indication information and the RB ID associated with the first indication information.

Optionally, the RRC reconfiguration message here may be an RRC reconfiguration message including a synchronization reconfiguration (ReconfigurationWithSync) cell, or may be an RRC connection reconfiguration message including a mobility control information (Mobility ControlInfo) cell, which is not limited here. . In addition, the RRC reconfiguration message may also adopt other names. The RRC reconfiguration message is used to instruct the UE to perform handover.

In another implementation manner, the second network device sends a PDCP control protocol data unit (protocol data unit, PDU) to the terminal device, and the PDCP control PDU carries the first indication information.

Different from the RRC reconfiguration message, the PDCP control PDU itself has a bearing granularity. Therefore, the PDCP control PDU carries the first indication information of the bearer corresponding to the PDCP control PDU. Specifically, the first indication information may be the PDCP sequence number, and the PDCP sequence number is the PDCP sequence number of the first data packet that needs to be decompressed by the header on the corresponding bearer.

Way 2

When the terminal device receives the data packet of the preset RLC sequence number from the first network device, the terminal device parses the data packet to obtain the PDCP sequence number corresponding to the data packet. The PDCP sequence number corresponding to the data packet is the PDCP sequence number of the first data packet that needs to be decompressed by the header from the first network device.

In other words, in mode 2, the terminal device determines the received PDCP sequence number of the data packet with the preset RLC sequence number as the PDCP sequence from the first network device that needs the first data packet decompressed by the header number. In other words, the terminal device determines the data packet with the preset RLC sequence number received from the first network device as the first data packet from the first network device that needs to be decompressed by the header.

Optionally, the preset RLC sequence number may be specified by a protocol, or agreed upon by the terminal device and the network, and is not limited here.

In one implementation, the preset RLC sequence number is 0.

That is, after receiving the data packet with the RLC sequence number of 0 from the first network device, the terminal device performs the PDCP layer corresponding processing on the data packet received from the first network device starting from the data packet with the RLC sequence number 0 .

Specifically, the RLC layer of the terminal device must wait for the RLC PDU (or RLC SDU) with the RLC SN of 0 to be received before it starts to submit data to its PDCP layer (for example, the RLC layer submits the RLC to the PDCP layer with SN of 0). RLC SDU), that is, the first packet that the terminal device submits to its PDCP layer must be a data packet with an RLC SN of 0. Even if the RLC layer of the terminal device has received the RLC SN non-zero data packet before it receives the RLC SN non-zero data packet, the RLC layer first buffers these RLC SN non-zero data packets, and does not submit to the PDCP layer, the RLC layer After receiving a packet with an RLC SN of 0 and submitting the packet with an RLC SN of 0 to the PDCP layer, the RLC layer delivers the buffered data packets with a non-zero RLC SN to the PDCP layer.

After the PDCP layer of the terminal device parses out the PDCP SN corresponding to the data packet whose RLC SN is 0, it reorders the data packets from the first network device according to the PDCP SN (that is, uses the PDCP SN as the start of the reordering Value), and then the PDCP layer of the terminal device decompresses the header of the reordered data packets in order.

In this embodiment, the first data packet submitted by the RLC layer of the terminal device to its own PDCP layer must be a data packet with an RLC SN of 0, and the RLC SN of the data packet subsequently submitted to the PDCP layer by the RLC layer can be out of order or according to This is not limited (for example, the second data packet submitted by the RLC layer of the terminal device to its own PDCP layer can be a data packet with RLC SN 1, or a data packet with RLC SN 3, or It is a data packet whose RLC SN is 2, which is not limited). The PDCP layer of the terminal device can reorder the received data packets (for example, the received RLC SDU (or PDCP PDU)).

Optionally, when the RLC layer of the UE receives a data packet with an RLC SN of 0 from the first network device, the RLC layer sends indication information to the PDCP layer for instructing the PDCP layer to start reordering or header decompression operations.

Specifically, RLC transmission modes include UM mode and AM mode. Correspondingly, RLC data PDU includes UMD (Unacknowledged Mode Data) PDU and AMD (Acknowledged Mode Data) PDU.

In the AM mode, because the AMD PDU header carries the RLC SN, in the AM mode, the first network device (that is, the sender) performs regular processing on the data packet, and the terminal device (that is, the receiver) performs the processing according to the above method.

In UM mode, only when the RLC SDU is segmented, the UMD PDU header carries RLC SN (An UMD PDU header contains the SN field only when the corresponding RLC SDU is segmented). In UM mode, the first network device (i.e. the sender) needs to perform special processing on data packets with RLC SN 0, that is, the RLC layer at the sender must use data packets with RLC SN 0 for data packets with RLC SN 0 The packet is processed in the format of. For example, the RLC layer of the sender performs segmentation processing on the RLC SDU with RLC SN of 0, and the format of the generated UMD PDU is UMD PDU with X bit SN (for example, X=6 or 12), For the specific format, please refer to the description in section 6.2.2.3 of TS38.322-f50 (for example, for the specific UMD PDU format, please refer to Figure 6.2.2.3-2, Figure 6.2.2.3-3, Figure 6.2.2.3-4, Figure 6.2. 2.3-5);

Optionally, in UM mode, the sender can perform special processing for data packets whose RLC SN is not 0 according to the above-mentioned method; or, no special processing is required, that is, the format of the generated UMD PDU is UMD PDU containing a complete RLC SDU For the specific format of UMD PDU, please refer to the description in section 6.2.2.3 of TS38.322-f50 (for example, refer to Figure 6.2.2.3-1 for the specific format of UMD PDU).

In the UM mode, the processing method of the receiving end (that is, the terminal device) is similar to the processing method of the receiving end (that is, the terminal device) in the AM mode, and the processing can be performed according to the above method 2.

520. The terminal device performs header decompression processing on the data packet received from the first network device according to the PDCP sequence number of the first header decompressed data packet.

Through any of the methods listed in step 510, the terminal device learns the PDCP sequence number of the first data packet that needs to be decompressed by the header among the data packets received from the first network device. At this time, the terminal device can reorder the data packets received from the first network device starting from the PDCP sequence number of the first data packet that needs to be decompressed by the header, and reorder the data packets in the order after the reordering. The data packet received from the first network device undergoes header decompression processing.

Optionally, corresponding to a certain bearer, the terminal device may decompress the header of the data packet received from the first network device at the PDCP layer corresponding to the first network device, or it may be common PDCP (common PDCP). ) Layer (the common PDCP corresponds to both the first network device and the second network device), for example, the user plane protocol stack of the terminal device may be as shown in Figure 4 or Figure 5 above. The user plane protocol stack of the terminal device is not limited here.

Optionally, in each embodiment of downlink data transmission, if the second network device performs a copy processing operation on the data packet, the first data packet that needs to be decompressed by the header is the second network device sent to the first data packet. The first data packet to be copied in the PDCP SDUs of a network device (or, it is the PDCP SN corresponding to the data packet that is copied in the PDCP SDUs sent by the second network device to the first network device) Minimum value), or, it is the minimum value of PDCP SN corresponding to the PDCP SDUs sent by the second network device to the first network device.

In other words, the terminal device needs to obtain the PDCP sequence number of the first DL duplication data packet from the first network device (or the minimum value of the PDCP SN corresponding to the DL duplication data packet from the first network device).

Uplink data transmission

610. The first network device obtains the PDCP sequence number of the first data packet that needs to be decompressed by the header among the data packets received from the terminal device.

Similar to downlink data transmission, the first network device can obtain the PDCP sequence number of the first data packet that needs to be decompressed by the header among the data packets received from the terminal device. Here are a few examples.

Way 1

The first network device receives second indication information from the terminal device, where the second indication information is used to indicate the PDCP sequence number of the first data packet that needs header decompression processing among the data packets sent by the terminal device.

In an implementation manner, the terminal device sends an RRC reconfiguration complete message to the first network device, and the RRC reconfiguration complete message carries one or more second indication information. Wherein, each second indication information is used to indicate the PDCP sequence number of the first data packet that needs to be decompressed by the header of the bearer corresponding to the second indication information.

Here, the second indication information is also based on radio bearer granularity. Therefore, the RRC reconfiguration complete message may carry one or more second indication information. The different second indication information is used to indicate the PDCP sequence number of the first data packet that needs to be decompressed by the header on different bearers.

Optionally, when the RRC reconfiguration complete message carries multiple second indication information, each second indication information is associated with one RB, indicating that the PDCP sequence number indicated by the second indication information corresponds to the RB identity The PDCP sequence number of the first packet on the RB that needs to be decompressed by the header. That is, optionally, the RRC reconfiguration complete message includes the second indication information and the RB ID associated with the second indication information.

Optionally, the PDCP sequence numbers of the first data packet that needs to be decompressed by the header on different bearers may be the same or different from each other, or the PDCP sequence number of the first data packet that needs to be decompressed by the header on part of the bearers Similarly, this application does not limit this.

In another implementation manner, the terminal device sends a PDCP status report to the first network device, and the PDCP status report carries the second indication information. Among them, the PDCP status report is sent with the granularity of the bearer. Therefore, the second indication information carried in each PDCP status report is used to indicate the first data packet on the bearer corresponding to the PDCP status report that needs to be decompressed by the header. The PDCP serial number. Alternatively, the terminal device sends an RLC status report to the first network device, and the RLC status report carries the second indication information.

In another implementation manner, the terminal device sends a PDCP control PDU to the first network device, and the PDCP control PDU carries the second indication information. Among them, the PDCP control PDU is sent with the granularity of the bearer. Therefore, the second indication information carried in each PDCP control PDU is used to indicate the first data packet on the bearer corresponding to the PDCP control PDU that needs to be decompressed by the header. The PDCP serial number.

Way 2

When the first network device receives a data packet with a preset RLC sequence number from the terminal device, the first network device parses the data packet to obtain the PDCP sequence number corresponding to the data packet. The PDCP sequence number corresponding to the data packet is the PDCP sequence number of the first data packet that needs to be decompressed by the header among the data packets received from the terminal device.

That is, the first network device determines the PDCP sequence number of the data packet with the preset RLC sequence number received from the terminal device as the first data packet from the terminal device that needs to be decompressed by the first network device. The PDCP serial number. In other words, the first network device determines the data packet of the preset RLC sequence number received from the terminal device as the first data packet that needs to be decompressed by the header.

In addition, the preset RLC sequence number in uplink data transmission and the preset RLC sequence number in downlink data transmission described above may be set to be the same or different, which is not limited in this application.

Optionally, the preset RLC sequence number in the uplink data transmission is 0.

Through any of the foregoing methods, the first network device obtains the PDCP sequence number of the first data packet that needs to be decompressed by the header among the data packets received from the terminal device. At this time, the first network device may perform header decompression processing on the data packet received from the terminal device starting from the first data packet that needs to be decompressed by the header.

620. The first network device performs header decompression processing on the data packet received from the terminal device starting from the PDCP sequence number of the first data packet that needs to be decompressed by the header.

After the first network device obtains the PDCP sequence number of the first data packet that needs to be decompressed by the header, according to whether the first network device has a reordering function module, the first network device checks the header of the data packet received from the terminal device. The decompression process can be implemented in a variety of specific implementations, which are described separately below.

Situation 1

The first network device has a function of reordering data packets, in other words, the first network device has a function module for reordering data packets.

For simplicity of description, the functional module that reorders data packets is referred to as a reordering functional module below.

In a possible implementation manner, the first network device and the second network device each have a reordering function module (the reordering function module is used to reorder the data packets before header decompression). The data packets received by the first network device and the second network device are reordered by their respective reordering function modules.

Refer to FIG. 7, which is a schematic diagram of the first network device and the second network device each having a reordering function module. As shown in Figure 7, the source base station and the target base station each have functional modules for reordering and header decompression. Among them, the reordering function module of the source base station is shown in Figure 7 for reordering (1), and the reordering function of the target base station is shown in Figure 7 for reordering (2). The above line of data transmission is taken as an example. The source base station and the target base station respectively complete PDCP header removal (remove PDCP header), decryption (deciphering), integrity verification (integrity verification), and complete reordering in the reception buffer (reception buffer) After processing such as duplicate discarding and header decompression, the data packets on the two legs will be reordered on a common reordering function module, and repeated packet detection/drop processing will be performed. Finally, the reordering function module delivers the data packet to the upper layer. Among them, this common reordering function module is shown in Figure 7 for reordering (3).

It should be noted that the source base station and the target base station shown in FIG. 7 each also have a copy discard function, or called a copy packet discard function. Optionally, the copy discard function and the reordering function can be designed on the same functional module. For example, the reordering (1)/copy discarding shown in FIG. 7 indicates that the functional module has both a reordering function and a copy discarding function. Or, the source base station and the target base station do not have a copy discard function, for example, the source base station's receive buffer does not have reordering (1), and the target base station's receive buffer does not have reordering (2).

Here, the duplication discard function refers to the function of detecting duplicate data packets (that is, the above-mentioned duplication data packets) for the same PDCP SN, and discarding one of them if two data packets with the same PDCP SN are detected.

In a possible implementation, before the target base station receives the SN status transfer message sent by the source base station, the common reordering/duplicate packet discarding function module (as shown in Figure 7 for reordering (3)/copy Discard) can be located at the source base station. After the target base station receives the SN status transfer message sent by the source base station, the common reordering/duplicate packet discarding function module may be located in the target base station.

In another possible implementation manner, the first network device and the second network device share a reordering function module. Wherein, the common reordering function module may be set on the first network device. Alternatively, the common reordering function module may be provided on the second network device.

In case 1, no matter which specific implementation manner is described above, after the first network device receives the data packet from the terminal device, it can use the reordering function module set on the first network device to determine the first Beginning with the PDCP sequence numbers of the data packets processed by header decompression, the data packets with the PDCP sequence numbers received from the terminal device are reordered sequentially. After the reordering is completed, the first network device decompresses the headers of these data packets in the order after the reordering.

Specifically, corresponding to Figure 7, after the first network device receives a data packet with an RLC sequence number of 0 from a terminal device, it starts with a data packet with an RLC sequence number of 0 and performs PDCP layer processing on the data packet received from the terminal device. Deal with it accordingly.

Specifically, RLC transmission modes include Unacknowledged Mode (UM) and Acknowledged Mode (AM). Correspondingly, RLC data PDU includes UMD (Unacknowledged Mode Data) PDU and AMD (Acknowledged Mode Data) PDU.

Under AM, because the AMD PDU header carries RLC SN, under AM, the terminal device (that is, the sending end) performs regular processing on the data packet, and the first network device (that is, the receiving end) performs the processing according to the above method.

Under UM, only when the RLC SDU is segmented, the UMD PDU header contains RLC SN (An UMD PDU header contains the SN field only when the corresponding RLC SDU is segmented). Under UM, the terminal device (i.e. the sender) needs to perform special processing on the data packets with RLC SN 0 sent to the first network device. That is, the RLC layer at the sender must carry RLC for data packets with RLC SN 0. The format of the SN data packet processes the data packet. For example, the RLC layer of the sender performs segmentation processing on the RLC SDU whose RLC SN is 0, and the format of the generated UMD PDU is the UMD PDU including X bit SN (e.g., X = 6 or 12). Optionally, the specific format of UMD PDU can refer to the description in section 6.2.2.3 of TS38.322-f50 (for example, Figure 6.2.2.3-2, Figure 6.2.2.3-3, Figure 6.2.2.3-4, Figure 6.2 .2.3-5).

Optionally, under UM, the sender can perform special processing for data packets whose RLC SN is not 0 according to the above method; or, there is no need to perform special processing, that is, the format of the generated UMD PDU is a UMD PDU containing a complete RLC SDU . Optionally, the specific format of UMD PDU can refer to the description in section 6.2.2.3 of TS38.322-f50 (for example, Figure 6.2.2.3-1).

Under UM, the processing method of the receiving end (ie, the first network device) is similar to the processing method of the receiving end (ie, the first network device) under AM, and the processing can be performed in the manner 2 above.

It can be seen that in case 1, the first network device can independently reorder the data packets received from the terminal device (that is, reorder (2) in Figure 7), and reorder the data according to the order after reordering. The packet is header decompressed.

Situation 2

The first network device does not have a reordering function module.

In a possible implementation manner, the first network device and the second network device share a reordering function module, but the reordering function module is provided on the second network device.

It is understandable that in case 2, since the first network device does not have a reordering function module, as shown in FIG. 8, the first network device (ie, the target base station) does not have reordering and copying before performing the header decompression function. Discard function. For example, compared with FIG. 7, the target base station shown in FIG. 8 does not have the functional module of reordering (2). Therefore, the first network device cannot reorder the data packets received from the terminal device. Therefore, the first network device needs the second network device to assist in decompressing the header of the data packet. Or, in another way, in case 2, the second network device does not have a reordering function module, and the second network device (that is, the source base station) does not have the reordering and copy discarding functions before performing the header decompression function. For example, compared with FIG. 7, the source base station does not have the reordering (1) functional module, and the target base station has the reordering (2) functional module. Therefore, the second network device cannot reorder the data packets received from the terminal device. Therefore, the second network device needs the first network device to assist in decompressing the header of the data packet.

Refer to FIG. 8, which is a schematic diagram of the first network device and the second network device sharing a reordering function module. As an example, as shown in FIG. 8, the reordering (3) on the source base station is set on the source base station as a common reordering function module of the source base station and the target base station. The target base station does not have a functional module for reordering after header decompression. Or, in another way, a common reordering function module after decompressing the headers of the source base station and the target base station is set on the target base station.

Continuing with the upstream data transmission as an example, for the source base station, after receiving the UL PDCP PDU from the UE, the source base station removes the PDCP header, and then the source base station uses the key of the source base station to decrypt and complete the integrity verification. After that, the source base station respectively reorders the data packets sent by the UE to the source base station and the data packets sent by the UE to the target base station. The reordering (1) function module in FIG. 8 performs the reordering operation.

It should be noted that in the uplink data transmission, if the terminal device performs a duplication operation on the data packet, the reordering (1) function module of the source base station will receive the duplication data packet. Therefore, the difference from the existing PDCP layer shown in Figure 3 is that the receiving PDCP entity (the PDCP entity shown on the right in Figure 3) in Figure 3 has a copy and discard function, while the source shown in Figure 8 The base station needs to disable the duplication discarding function.

Reordering of the source base station (1) The function module reorders the data packets received from the UE, and then submits it to the header decompression function module of the source base station for header decompression. After header decompression is completed, the header decompression module then submits the header decompressed data packet to the reordering (3)/copy and discarding function module to perform reordering/duplicate packet discard processing. After the reordering, copy detection, and copy discarding are completed, the data packet is delivered to the upper layer.

For the target base station, after the target base station receives the UL PDCP PDU from the UE, it removes the PDCP header, then uses the key of the target base station for decryption and then performs integrity verification. Since the header must be decompressed to ensure that the data packets are in order, and the target base station does not have a reordering function module. Therefore, the target base station's decompression processing of the header of the data packet includes the following method 1 and method 2.

Method 1: As shown in path 1 in Figure 8, the target base station sends the data packets received from the terminal device to the source base station, and the source base station's reordering function module (reordering (1) shown in Figure 8) Reorder these packets. After completing the reordering, the source base station needs to record which base station each data packet reordered by the reordering (1) comes from, and then transfer the data packet to the corresponding base station for header decompression processing.

Method 2: As shown in path 2 in Figure 8, the target base station only sends the PDCP sequence number of the data packet to the source base station, and the source base station checks whether the PDCP sequence number is in sequence. If the PDCP sequence numbers are in sequence, the source base station instructs the target base station to decompress the header of the data packet corresponding to the PDCP sequence number. Then, the target base station submits the data packet corresponding to the PDCP sequence number to its own header decompression module for header decompression according to the instruction of the source base station. After the target base station completes header decompression, it then submits the header decompressed data packet to the public reordering/duplication discarding function module for reordering and duplication packet (ie, duplication data packet) discarding processing. The common reordering/duplication discarding function module completes reordering, duplication data packet detection, and discarding the data packets of the two legs, and then delivers the data packets to the upper layer.

Here, the common reordering/copy discarding function module is the reordering (3)/copying discarding function module shown in FIG. 8.

It should be understood that, in FIG. 8, the common reordering/duplication discarding function module is located in the source base station as an example. Optionally, in another implementation manner, the common reordering/duplication discarding functional module may also be located in the target base station. In this case, the network side decompressing the header of the data packet is similar to that shown in Figure 8. Those skilled in the art can also easily process the data packet according to the reordering/duplication discarding function module at the source base station. The process of processing data packets when the reordering/duplication discarding function module is known to be located at the target base station is appropriately omitted here to avoid repetition.

It should be noted that, in FIG. 8, the reordering function module is set in the source base station as an example for illustration (that is, the reordering (1) function module is located in the source base station). For example, the target base station did not receive the SN status transfer message sent by the source base station. Alternatively, the reordering function module can also be set in the target base station. For example, the target base station receives the SN status transfer message sent by the source base station.

Optionally, the second network device may assist the first network device in completing the decompression processing of the header of the data packet in a variety of ways. Several methods are listed below as examples.

Way A

After the first network device obtains the PDCP data packet that requires the first data packet decompressed by the header, it sends a first message to the second network device. The first message is used to indicate the data received by the first network device from the terminal device. The packet needs the PDCP sequence number of the first packet decompressed by the header.

After the first network device informs the second network device of the PDCP sequence number of the first data packet whose header is decompressed by the first network device through the first message, the first network device will receive one or more Data packets are sent to the second network device.

From the perspective of the second network device, when the second network device receives one or more data packets from the first network device, the second network device needs the first one to be decompressed from the header indicated by the first message. Starting with the PDCP sequence number of the data packet, reorder one or more data packets received from the first network device, and return the one or more data packets after the reordering to the first network device for header decoding Compression processing.

It can be seen that the second network device assists the first network device in reordering the data packets from the terminal device received by the first network device. After that, the first network device receives the reordered data packets returned by the second network device, and sequentially performs header decompression processing on the data packets in the order after the reordering.

Way B

According to the first message, the second network device can learn the PDCP sequence number of the first data packet that needs to be decompressed by the header among the data packets received by the first network device from the terminal device. This is the same as Method A above.

When the first network device receives one or more data packets from the terminal device, the first network device sends the PDCP sequence number corresponding to the received one or more data packets to the second network device.

After the second network device receives one or more PDCP sequence numbers sent by the first network device, it determines the one or more PDCP sequence numbers received from the first network device according to the PDCP sequence number of the first packet decompressed by the header. Or whether the data packets corresponding to the multiple PDCP sequence numbers can be decompressed by the header and return a second message to the first network device.

Here, the second message is used to indicate whether the first network device can decompress the header of each data packet corresponding to the one or more PDCP sequence numbers.

Optionally, the first network device may send the PDCP sequence number of the data packet to the second network device for judgment every time it receives a data packet from the terminal device. In this case, when the second network device receives the first PDCP sequence number from the first network device, if the first PDCP sequence number is the same as the first packet that needs to be decompressed by the header, then The second message returned by the second network device to the first network device indicates that the data packet header corresponding to the PDCP sequence number is allowed to be decompressed.

After that, if the PDCP sequence number received by the second network device from the first network device is sequentially increasing from the PDCP sequence number of the first packet that needs to be decompressed by the header, the second network device returns The second message indicates that the first network device is allowed to decompress the header of the data packets corresponding to the PDCP sequence numbers. On the contrary, if the PDCP sequence number received by the second network device from the first network device does not increase sequentially from the PDCP sequence number of the first packet that needs to be decompressed by the header, it means that the first network device is from the terminal device. The PDCP sequence number of the received data packet or the PDCP sequence number indicated by the second network device to the first network device is out of sequence. Therefore, the second message returned by the second network device for the out-of-sequence PDCP sequence number indicates not Allow the first network device to decompress the header.

Assuming that the second network device learns, according to the first message, the PDCP SN=3 of the first data packet that needs to be decompressed by the first network device, an example is given below.

The first PDCP SN=3 received by the second network device from the first network device, and the second network device returns an ACK to the first network device, indicating that the header can be decompressed for the data packet corresponding to PDCP SN=3.

After that, if the second PDCP SN=4 received by the second network device from the first network device, the second network device returns an ACK to the first network device, indicating that header decompression of the packet corresponding to PDCP SN=4 is allowed .

On the contrary, if the second network device receives the second PDCP SN=6 from the first network device, the second network device returns a NACK to the first network device, indicating that it is not allowed to decompress the packet with PDCP SN=6. .

It should be understood that the PDCP SN=6 here is only used as an example for description, that is, if the PDCP SN received by the second network device from the first network device is not from the PDCP SN that requires the first packet to be decompressed by the header. Increasing sequentially, it means that the data packets received by the first network device from the terminal device are out of order, and header decompression needs to be performed after reordering, otherwise header decompression errors will occur.

Optionally, the first network device may also send the PDCP sequence numbers of the multiple data packets to the second network device according to the receiving order after receiving multiple data packets. The second network device determines whether the data packets corresponding to the multiple PDCP sequence numbers received from the first network device can be decompressed by the header according to the PDCP sequence number of the first data packet that needs to be decompressed by the header.

Continue to assume that the second network device learns the PDCPSN=3 of the first data packet that needs to be decompressed by the header according to the first message, and an example is described below.

The second network device receives multiple PDCP sequence numbers from the first network device, and the multiple PDCP sequence numbers are PDCPSN=3, PDCPSN=5, PDCPSN=4, PDCPSN=6. The second network device judges according to the PDCP SN=3 of the first data packet that needs to be decompressed by the header. PDCP SN=3, 5, 4, and 6 are not incrementally increased, that is, the first network device The PDCP sequence numbers of the data packets received by the terminal device are out of order. Therefore, the second network device returns a NACK to the first network device, which means that the first network device is not allowed to decompress the header of each data packet corresponding to the PDCP SN=3, 5, 4, and 6.

In an implementation manner, the second network device may return the reordered PDCP sequence numbers to the first network device while returning NACK, so as to instruct the first network device to follow the indicated reordered PDCP sequence numbers. , Decompress the header of the data packets corresponding to these PDCP sequence numbers.

For example, the second network device returns 3, 4, 5, and 6 to the first network device. The first network device respectively decompresses the header of the data packet with PDCP SN=3, 5, 4, and 6 according to the sequence of the PDCP SN returned by the second network device.

In another implementation manner, the second network device may use multiple bits to respectively indicate whether the data packets corresponding to the multiple PDCP sequence numbers received from the first network device can be decompressed by the header.

For example, the second network device returns 1000 to the first network device, indicating that the data packet corresponding to the first PDCP sequence number sent by the first network device to the second network device allows the first network device to decompress the header, and the next three The data packets corresponding to the respective PDCP sequence numbers do not allow the first network device to perform header decompression.

It can be seen that in method A, after receiving the data packet from the terminal device, the first network device sends the received data packet to the second network device for reordering. In method B, after receiving the data packet from the terminal device, the first network device sends the PDCP sequence number of the received data packet to the second network device, and the second network device transmits the first network device according to the requirements indicated in the first message. The PDCP sequence number of a data packet decompressed by the header determines whether the first network device is allowed to decompress the data packet corresponding to the PDCP sequence number, and then the first network device is instructed through a second message.

It should be understood that, in the method A and the method B, the process of the source base station assisting the target base station to decompress the header of the data packet received from the terminal device can be referred to the description of path 1 and path 2 in FIG. 8 respectively.

In the foregoing manner A and manner B, after the first network device obtains the PDCP sequence number of the data packet that needs to be decompressed by the first network device for the first header, it indicates the need to the second network device through the first message The PDCP sequence number of the packet decompressed by the first header. Then, when the first network device receives the data packet from the terminal device, the first network device sends the received data packet or the PDCP sequence number of the received data packet to the order of the data packets received from the terminal device The second network device.

The following introduces other ways in which the second network device assists the first network device in decompressing the header of the data packet received from the terminal device, such as the following way C and way D.

Way C

The first network device obtains a PDCP data packet that requires the first header decompressed data packet, and the PDCP sequence number of the PDCP data packet is the first PDCP sequence number.

The first network device receives the data packet from the terminal device. When the first network device receives the data packet corresponding to the first PDCP serial number from the terminal device, the first network device first transfers the data corresponding to the first PDCP serial number The packet is sent to the second network device, and then other data packets received from the terminal device are sent to the second network device.

In other words, in method C, the first data packet sent by the first network device to the second network device is by default the data packet that needs to be decompressed by the first header. It is equivalent to that, the first network device implicitly informs the second network device of the data packet received by the first network device from the terminal device that the PDCP sequence number of the first packet decompressed by the header is required, and It is no longer necessary to notify through other additional messages (for example, the first message).

In method C, from the perspective of the second network device, the PDCP sequence number of the first packet received by the second network device from the first network device (hereinafter referred to as the first PDCP sequence number) is the The first data packet that needs to be decompressed by the header among the data packets received by the first network device from the terminal device.

In other words, the second network device uses the PDCP sequence number of the first data packet received from the first network device as a reference for reordering the data packets received from the first network device. Starting from the first PDCP sequence, the second network device reorders the data packets received from the first network device.

Way D

The first network device obtains the PDCP data packet that needs the first data packet decompressed by the header.

When the first network device receives the data packet that needs to be decompressed by the first header from the terminal device, the first network device first sends the PDCP sequence number of the data packet that needs to be decompressed by the first header to The second network device then sends the PDCP sequence numbers of other data packets received from the terminal device to the second network device.

Similar to method C, in method D, the first PDCP sequence number sent by the first network device to the second network device is the PDCP sequence number of the data packet that needs to be decompressed by the first header by default. In other words, the first network device implicitly informs the second network device of the PDCP sequence number of the first packet decompressed by the header among the data packets received by the first network device from the terminal device. It is also no longer necessary to notify through other additional messages (for example, the first message).

It can be seen that, compared with the above method A or the method B, the method C and the method D can save the signaling interaction between the first network device and the second network device, and save the signaling overhead.

Similarly, in each embodiment of uplink data transmission, if a terminal device performs a copy processing operation on a data packet sent to a network device, the first network device needs to decompress the first data packet received from the terminal device. The data packet may also be the first data packet that is subjected to copy processing among the data packets sent by the terminal device to the first network device (or, that is, the data packet that is sent to the network device by the terminal device corresponds to the data packet that is subjected to copy processing. The minimum value of PDCP SN), or the minimum value of PDCP SN corresponding to the PDCP SDUs sent by the terminal device to the first network device.

Alternatively, in the method embodiments of the present application, the first data packet that needs to be decompressed by the header can also be replaced with the first data packet that needs to be decompressed by the header. That is, the PDCP sequence number of the first data packet that needs to be decompressed by the header can also be replaced with the PDCP sequence number of the first data packet that needs to be decompressed by the header.

Optionally, if the sending end performs a duplication operation on the data packet, the receiving end needs to obtain the PDCP sequence number of the first data packet that is subjected to the duplication process among the sent data packets.

In the above embodiment, the description is made by taking the sending end of the data packet performing the copy processing operation on the data packet as an example. In another possible implementation manner, in uplink data transmission or downlink data transmission, the sender may not perform a copy processing operation on the data packet.

In the uplink data transmission, if the data packet is not copied, that is, the UE only sends UL data to the source base station before sending the RRC reconfiguration message to the target base station. After sending the RRC reconfiguration complete message, the UE only sends UL data to the target base station. Since some of the data packets sent by the UE to the source base station may not be successfully received, the UE needs to retransmit these data packets to the target base station, which may also cause the target base station to receive the data packets from the UE out of order, and the target base station When the header decompresses the data packet, the PDCP sequence number may also appear out of order, which causes the header decompression error of the target base station.

For example, the UE sends data packets with PDCP SN 2, 3, 4 to the source base station, but the source base station only successfully receives data packets with PDCP SN 2, 4. Among them, the data packet with PDCP SN of 3 failed to be sent. At this time, the UE may have sent a data packet with a PDCP SN of 5 to the target base station, and then the UE finds that the data packet with a PDCP SN of 3 failed to be sent. If at this time, the UE uses the header compression (such as ROHC) context of the target base station to perform header compression on the data packet whose PDCP SN is 3, and retransmit to the target base station. Because the target base station first receives the data packet with PDCP SN of 5, and then receives the data packet with PDCP SN of 3. If the target base station first decompresses the header of the data packet whose PDCP SN is 5 according to the order of the received data packets, the header decompression error occurs.

For this reason, this application also proposes a solution for the situation where the copy processing operation is not performed on the data packet, which is applicable to both uplink and downlink data transmission. The following is an example of the above data transmission.

In an implementation manner, after the UE sends a data packet to the source base station, it needs to receive feedback from the source base station corresponding to all the data packets sent to the source base station, and then send the data packet to the target base station.

For example, in the above example, the UE sends data packets with PDCP SN 2, 3, 4 to the source base station, and after receiving feedback for all data packets from the source base station, it is determined that the data packet with PDCP SN 3 fails to be sent. At this time, the UE uses the ROHC context of the target base station to compress the data packet whose PDCP SN is 3. Therefore, the first data packet sent by the UE to the target base station is a data packet whose PDCP SN is 3. After the UE sends a data packet with a PDCP SN of 3 to the target base station, it then sends a data packet with a PDCP SN of 5 to the target base station. In this way, the data packet whose PDCP SN is 3 will be the first data packet received by the target base station and decompressed by the header, which can avoid header decompression errors.

Optionally, in another implementation manner, the UE may indicate to the target base station the PDCP sequence number of the first data packet that requires header decompression.

For example, in the example above, the PDCP SN indicated by the UE to the target base station is 3.

In another possible implementation manner, after the UE sends to the target base station the first data packet that needs to be decompressed by the header, it sends indication information to the target base station, for example, the indication information is an end marker. Wherein, the indication information (such as the end identifier) is used to instruct the target base station to start decompressing the received PDCP PDU header.

It should be noted that, for the data packet whose PDCP SN is 4 in the above example, the UE can use the ROHC context of the target base station to perform header compression, and then the UE sends it to the target base station. That is, even if the source base station successfully receives a data packet with a PDCP SN of 4, the UE may send a data packet with a PDCP SN of 4 to the target base station. The target base station decrypts and decompresses the header of the data packet whose PDCP SN is 4.

Or, in an implementation manner, the source base station decrypts the successfully received data packet (PDCP PDU) with a PDCP SN of 4 using the key of the source base station and decompresses the header of the ROHC context of the source base station, and then the PDCP SN The PDCP SDU of the data packet of 4 is forwarded to the target base station.

The method for processing data packets provided by this application is described in detail above.

It is understandable that, in the above method for processing data packets, the steps implemented by the terminal device can also be implemented by components (such as chips or circuits) that can be used in the terminal device, and the steps implemented by the network device can also be implemented by For the implementation of components (such as chips or circuits) of the network device, the embodiment of the present application does not limit this.

In the technical solution of the present application, the receiving end indicates to the receiving end the PDCP sequence number of the first packet decompressed by the header, or presets the PDCP sequence number of the first packet decompressed by the header. , Can avoid the header decompression processing on the data packet by the receiving end when the data packet is out of order, resulting in header decompression error, thereby reducing the header decompression error rate.

It is understandable that the foregoing method for processing data packets is not only applicable to eMBB scenarios, but also applicable to similar scenarios where disorder may occur during header decompression. For example, in a traditional handover, the UE sends an uplink data packet with a PDCP SN of 10-20 to the source base station, the source base station successfully receives a data packet with a PDCP SN of 10-15, and the source base station sends an SN STATUS TRANSFER message to the target base station. The indicated PDCP SN of the first missing uplink data packet is 16, but the source base station does not send a status report to the UE or the UE does not receive the status report sent by the source base station, the UE sends an uplink with a PDCP SN of 10-20 to the target base station Data packet, the first data packet received by the target base station is a data packet with PDCP SN of 16, and the target base station considers that the data packet with PDCP SN of 16 is the first data packet that requires header decompression, and the target base station performs header decompression The first compressed packet is a data packet with a PDCP SN of 16. At this time, the header decompression fails. At this time, the above method of processing the data packet can also be used to solve the problem of header decompression failure.

The following describes the device for processing data packets provided by this application.

Refer to FIG. 9, which is a schematic diagram of a communication device 500 provided by this application. The communication device 500 includes a communication unit 510 and a processing unit 520.

The communication unit 510 is configured to obtain the packet data convergence protocol PDCP sequence number of the first data packet that needs to be decompressed by the header among the data packets received from the first network device;

The processing unit 520 is configured to perform header decompression processing on the data packet received from the first network device according to the PDCP sequence number of the first header decompressed data packet.

Optionally, the communication unit 510 may also be replaced by a receiving unit and/or a sending unit.

For example, the communication unit 510 may be replaced by a receiving unit when performing the receiving step. The communication unit 510 may be replaced by a sending unit when performing the steps of sending. Alternatively, the communication unit 510 may also be an interface circuit.

Optionally, the communication device 500 may further include a storage unit for storing code or data, and the processing unit 520 may call the code or data in the storage unit to enable the communication device to implement corresponding functions or steps.

In an implementation manner, the communication device 500 may completely correspond to the terminal device in the method embodiment, or in other words, the communication device 500 is a terminal device.

Optionally, the communication unit 510 shown in FIG. 9 may be a transceiver. The transceiver has the function of sending and/or receiving. The transceiver can also be replaced by a receiver and/or transmitter. It can be understood that the communication unit 510 may also be a transceiver circuit or an interface circuit.

In downlink data transmission, the steps and/or processing performed by each unit of the communication device 500 are as follows.

For example, the communication unit 510 receives first indication information from the second network device, where the first indication information is used to indicate the PDCP sequence number of the first data packet that needs to be decompressed by the header.

For another example, the communication unit 510 receives a radio resource control RRC reconfiguration message from the second network device, where the RRC reconfiguration message carries one or more of the first indication information, where each first indication information is used It indicates the PDCP sequence number of the first packet that needs to be decompressed by the header of the corresponding bearer. or,

The communication unit 510 receives the PDCP control protocol data unit PDU from the second network device, the PDCP control PDU carries the first indication information, where the first indication information is used to indicate the bearer corresponding to the PDCP control PDU The PDCP sequence number of the first packet that needs to be decompressed by the header.

Optionally, the processing unit 520 may be a processor. The processor is configured to execute steps or processing corresponding to the terminal device implementation in each method embodiment.

For example, the processing unit 520 parses the data packet received by the communication unit 510 from the first network device, and when it is determined that the communication unit 510 receives a data packet with a preset radio link control RLC sequence number, the processing unit 520 performs analysis on the pre- It is assumed that the data packet of the RLC sequence number is analyzed to obtain the PDCP sequence number of the first data packet that needs to be decompressed by the header.

For another example, the processing unit 520 starts from the data packet corresponding to the PDCP sequence number of the first data packet that needs to be decompressed by the header for the data packet received from the first network device, and for the data packet received from the first network device The data packets are reordered, and the header of the data packets received from the first network device is decompressed according to the order after the reordering.

In another implementation manner, the communication device 500 may be a chip or an integrated circuit.

Optionally, the communication unit 510 shown in FIG. 9 may be a communication interface. Optionally, the communication interface may be an input/output interface or a transceiver circuit. The processing unit 520 may be a processing device. The functions of the processing device can be partially or fully realized by software.

In an implementation manner, the functions of the processing device may be partially or fully implemented by software. In this implementation, the processing device may include a memory and a processor, where the memory is used to store a computer program, and the processor reads and executes the computer program stored in the memory to execute the internal implementation of the terminal device in each embodiment. deal with. For example, the processing performed by the processing unit 520 described above is executed.

Optionally, the processing device may only include a processor, and the memory for storing the computer program is located outside the processing device. The processor is connected to the memory through a circuit/wire to read and execute the computer program stored in the memory.

In another implementation manner, the functions of the processing device may be partially or fully implemented by hardware. In this implementation, the processing device includes an input interface circuit, a logic circuit, and an output interface circuit. The input interface circuit is used to obtain the data packet that needs to be decompressed by the first header and the data packet received by the communication device from the first network device; the logic circuit is used to obtain the data packet that needs to be decompressed by the first header. The PDCP sequence number of the data packet is used to perform header decompression processing on the data packet received from the first network device; the output interface circuit is used to output the data packet after the header is decompressed.

Alternatively, the input interface circuit is used to obtain the first indication information; the logic circuit is used to parse the first indication information to obtain the PDCP serial number of the data packet that needs to be decompressed by the first header; and the output interface circuit is used to output The PDCP sequence number of the first data packet that needs to be decompressed by the header.

Optionally, the input interface circuit can be used to obtain the RRC reconfiguration message, and the logic circuit parses the RRC reconfiguration message to obtain the PDCP sequence number of the first packet that needs to be decompressed by the header; output interface circuit Used to output the PDCP sequence number of the first packet that needs to be decompressed by the header.

Optionally, the input interface circuit can be used to obtain the PDCP control PDU, and the logic circuit can obtain the PDCP serial number of the first packet decompressed by the header according to the PDCP control PDU; the output interface circuit is used to output the data packet. The PDCP sequence number of the first packet that needs to be decompressed by the header.

Optionally, the input interface circuit may be used to obtain the data packet received by the communication device from the first network device, and the logic circuit parses the data packet to obtain the RLC sequence number of the data packet, so that when it is determined that the pre-order is received When setting the data packet of the RLC sequence number, analyze the data packet to obtain the PDCP sequence number of the data packet, and determine the PDCP sequence number as the PDCP sequence number of the first data packet that needs to be decompressed by the header; The output interface circuit is used to output the PDCP sequence number of the first packet that needs to be decompressed by the header.

The processing unit 520 is configured to generate second indication information, where the second indication information is used to indicate the PDCP sequence number of the first data packet that needs to be decompressed by the first network device header among the data packets sent by the terminal device;

The communication unit 510 is configured to send second instruction information to the first network device.

Optionally, the communication unit 510 is specifically configured to send an RRC reconfiguration complete message to the first network device, where the RRC reconfiguration complete message carries one or more of the second indication information, where each second indication information It is used to indicate the PDCP sequence number of the first packet that needs to be decompressed by the header of the corresponding bearer. or,

The communication unit 510 is specifically configured to send a PDCP status report to the first network device, where the PDCP status report carries the second indication information, where the second indication information is used to indicate that the corresponding bearer needs to be first The PDCP sequence number of the decompressed packet. or,

The communication unit 510 is specifically configured to send a PDCP control PDU to the first network device, where the PDCP control PDU carries the second indication information, where the second indication information is used to indicate the bearer corresponding to the PDCP control PDU The PDCP sequence number of the first packet that needs to be decompressed by the header.

Refer to FIG. 10, which is a schematic diagram of a communication device 600 provided by this application. The communication device 600 includes a processing unit 610 and a transceiving unit 620.

Optionally, the communication device 600 may correspond to the second network device in each method embodiment of downlink data transmission, or may also be a chip or an integrated circuit installed on the second network device. At this time, the functions of each unit included in the communication device 600 are as follows.

The processing unit 610 is configured to generate first indication information, where the first indication information is used to indicate that the terminal device needs the packet data convergence protocol PDCP sequence of the first header decompressed data packet among the data packets received from the first network device number;

The communication unit 620 is configured to send the first indication information to a terminal device.

Optionally, the communication device 600 may further include a storage unit for storing code or data, and the processing unit 610 may call the code or data in the storage unit to enable the communication device 600 to implement corresponding functions or steps.

Optionally, the communication unit 620 may also be replaced by a receiving unit and/or a sending unit.

For example, the communication unit 620 may be replaced by a receiving unit when performing the receiving step. The communication unit 620 may be replaced by a sending unit when performing the steps of sending. Alternatively, the communication unit 620 may also be an interface circuit.

In an implementation manner, the communication device 600 may completely correspond to the second network device (for example, the source base station) in the method embodiment, or in other words, the communication device 600 is the second network device.

In this implementation, the transceiving unit 620 shown in FIG. 10 may be a transceiver. The transceiver has the function of sending and/or receiving. The transceiver can also be replaced by a receiver and/or transmitter. The processing unit 610 may be a processor. The transceiver and the processor are used to perform steps or processing performed by the second network device in each method embodiment of downlink data transmission.

For example, the communication unit 620 sends an RRC reconfiguration message to the terminal device, the RRC reconfiguration message carries one or more of the first indication information, and each first indication information is used to indicate that the corresponding bearer needs the first indication. The PDCP sequence number of each packet decompressed by the header.

For another example, the communication unit 620 sends a PDCP control PDU to the terminal device, where the PDCP control PDU carries the first indication information, and the first indication information is used to indicate that the bearer corresponding to the PDCP control PDU needs the first indication. The PDCP sequence number of a packet decompressed by the header.

In another implementation manner, the communication device 600 may be a chip or an integrated circuit.

In this implementation manner, the communication unit 620 shown in FIG. 10 may be a communication interface. Optionally, the communication interface may be an input/output interface or a transceiver circuit. The processing unit 610 may be a processing device. The functions of the processing device can be partially or fully realized by software.

In an implementation manner, the functions of the processing device may be partially or fully implemented by software. In this implementation, the processing device may include a memory and a processor, where the memory is used to store a computer program, and the processor reads and executes the computer program stored in the memory to execute the second network device in the various embodiments. Realized processing. For example, the processing performed by the processing unit 610 described above is executed.

In another implementation manner, the functions of the processing device may be partially or fully implemented by hardware. In this implementation, the processing device includes an input interface circuit, a logic circuit, and an output interface circuit.

Optionally, the logic circuit is configured to generate first indication information, where the first indication information is used to indicate that the PDCP sequence number of the first data packet decompressed by the header among the data packets received by the terminal device from the first network device; The output interface circuit is used to output the first indication information.

Optionally, the communication apparatus 600 may correspond to the second network device in each method embodiment of uplink data transmission, or may also be a chip or an integrated circuit installed on the second network device. At this time, the functions of each unit included in the communication device 600 are as follows.

The processing unit 610 is configured to obtain the PDCP sequence number of the first data packet that needs to be decompressed by the header among the data packets sent by the terminal device, and according to the PDCP sequence number of the first data packet that needs to be decompressed by the header, Assisting the first network device to perform header decompression processing on the data packet received from the terminal device.

In a possible implementation, when the communication device 600 can correspond to the second network device in each method embodiment of uplink data transmission, the communication unit 620 is configured to receive a first message from the first network device, and the first message is used for Indicates the PDCP sequence number of the first packet that needs to be decompressed by the header. And, the communication unit 620 is configured to receive one or more data packets from the first network device. At this time, the processing unit 610 is configured to reorder the one or more data packets received from the first network device starting from the PDCP sequence number of the first data packet that needs to be decompressed by the header, And sending the one or more data packets after the reordering to the first network device for header decompression processing.

In another possible implementation, the aforementioned communication unit 620 is configured to receive a first message from the first network device, and the first message is used to indicate the PDCP sequence number of the first data packet that needs to be decompressed by the header. And, the communication unit 620 is configured to receive the PDCP sequence number of one or more data packets from the first network device. At this time, the processing unit 610 is configured to determine, according to the first message, whether to allow the first network device to decompress the header of each data packet corresponding to the one or more PDCP sequence numbers. Further, the communication unit 620 is further configured to send a second message to the first network device, where the second message is used to indicate whether the first network device is allowed to access the data corresponding to the one or more PDCP sequence numbers. The packet is header decompressed.

In yet another possible implementation manner, the communication unit 620 receives the data packet corresponding to the first PDCP sequence number from the first network device, and after receiving the data packet corresponding to the first PDCP sequence number, The first network device receives other data packets. The processing unit 610 is configured to reorder the data packets corresponding to the first PDCP sequence number and the other data packets starting from the first PDCP sequence number, and reorder the data corresponding to the first PDCP sequence number after the reordering The packet and the other data packets are sent to the first network device for header decompression processing.

In another possible implementation manner, the communication unit 620 receives a second PDCP sequence number from the first network device, and the second PDCP sequence number is preset to be that the first network device receives from the terminal device The received packet needs the PDCP sequence number of the first packet decompressed by the header. The processing unit 610 reorders the one or more data packets starting from the second PDCP sequence number. And, the communication unit 620 is further configured to send the data packet corresponding to the reordered second PDCP sequence number and the one or more data packets to the first network device for header decompression processing.

Referring to FIG. 11, FIG. 11 is a schematic diagram of a communication device 700 provided by this application. The communication device 700 includes a communication unit 710 and a processing unit 720.

The communication unit 710 is configured to obtain the PDCP sequence number of the first data packet that needs to be decompressed by the header among the data packets received from the terminal device;

The processing unit 720 is configured to perform header decompression processing on the data packet received from the terminal device starting from the PDCP sequence number of the first data packet that needs to be decompressed by the header.

Optionally, the communication unit 710 may also be replaced by a receiving unit and/or a sending unit.

For example, the communication unit 710 may be replaced by a receiving unit when performing the receiving step. The communication unit 710 may be replaced by a sending unit when performing the steps of sending.

Optionally, the communication device 700 may further include a storage unit for storing code or data, and the processing unit 720 may call the code or data in the storage unit to enable the communication device 700 to implement corresponding functions or steps.

In an implementation manner, the communication apparatus 700 may completely correspond to the first network device (for example, the target base station) in the method embodiment. In other words, the communication apparatus 700 is the first network device.

In this implementation, the communication unit 710 shown in FIG. 11 may be a transceiver. The transceiver has the function of sending and/or receiving. The transceiver can also be replaced by a receiver and/or transmitter. The processing unit 720 may be a processor. The transceiver and the processor are used to execute steps or processes executed by the first network device in each method embodiment.

For example, the communication unit 710 receives second indication information from the terminal device, where the second indication information is used to indicate the PDCP sequence number of the first data packet that needs to be decompressed by the header among the data packets sent by the terminal device.

For another example, the communication unit 710 receives an RRC reconfiguration complete message from the terminal device, where the RRC reconfiguration complete message carries one or more of the second indication information, where each second indication information is used to indicate the corresponding The PDCP sequence number of the first packet that needs to be decompressed by the header.

For another example, the communication unit 710 receives a PDCP status report from a terminal device, and the PDCP status report carries the second indication information, where the second indication information is used to indicate the needs of the bearer corresponding to the PDCP status report The PDCP sequence number of the first packet decompressed by the header.

For another example, the communication unit 710 receives a PDCP control PDU from the terminal device, and the PDCP control PDU carries the second indication information. The second indication information is used to indicate the PDCP sequence number of the first data packet that needs to be decompressed by the header of the bearer corresponding to the PDCP control PDU.

For another example, the processing unit 720 is configured to determine the RLC sequence number of the data packet received by the communication unit 710 from the terminal device. When the processing unit 720 determines that the communication unit 710 has obtained the data packet with the preset RLC sequence number, the processing unit 720 parses the data packet with the preset RLC sequence number to obtain the first data packet that needs to be decompressed by the header. The PDCP sequence number of the packet.

For another example, the communication unit 710 sends a first message to the second network device, where the first message is used to indicate the PDCP sequence number of the first data packet that needs to be decompressed by the header. And, when the communication unit 710 receives one or more data packets from the terminal device, it sends the one or more data packets to the second network device. And, the processing unit 720 is further configured to receive the one or more data packets after reordering from the second network device, and perform header decompression processing on the one or more data packets in the order after the reordering , Wherein the one or more data packets are reordered starting from the PDCP sequence number of the first data packet that needs to be decompressed by the header.

For another example, the communication unit 710 sends a first message to the second network device, where the first message is used to indicate the PDCP sequence number of the first data packet that needs to be decompressed by the header. And, when the communication unit 710 receives one or more data packets from the terminal device, it sends the PDCP sequence numbers of the one or more data packets to the second network device. And, the processing unit 720 receives a second message from the second network device, where the second message is used to indicate whether header decompression is allowed for the data packet corresponding to the one or more PDCP sequence numbers, where the first The second message is generated according to the first message and the one or more PDCP sequence numbers. And, the processing unit 720 starts from the PDCP sequence number of the first data packet that needs to be decompressed by the header, decompresses the header of the data packet that is allowed to be decompressed by the header indicated by the second message, and decompresses all the data packets. The data packet indicated by the second message that it is not allowed to be decompressed by the header does not undergo header decompression.

For another example, when the communication unit 710 receives the data packet that needs to be decompressed by the first header, the communication unit 710 sends the data packet that needs to be decompressed by the first header to the second network device, and sends it After the data packet that needs to be decompressed by the first header, the other data packet received from the terminal device is sent to the second network device. And, the communication unit 710 receives the first data packet that needs to be decompressed by the header and the other data packets after reordering from the second network device. And, the processing unit 720 is configured to perform header decompression processing on the data packet that needs to be decompressed by the first header and the other data packets in the order after the reordering.

For another example, when the communication unit 710 receives the data packet that needs to be decompressed by the first header, the communication unit 710 sends the PDCP sequence number of the data packet that needs to be decompressed by the first header to the second network device. , And after sending the PDCP sequence number of the data packet that needs to be decompressed by the first header, the PDCP sequence number of the other data packet received from the terminal device is sent to the second network device. And, the communication unit 710 receives from the second network device the PDCP sequence numbers of the first data packet that needs to be decompressed by the header and the other data packets after the reordering. And, the processing unit 720 is configured to perform header decompression processing on the data packet that needs to be decompressed by the first header and the other data packets in the order after the reordering.

In another implementation manner, the communication device 700 may be a chip or an integrated circuit.

In this implementation manner, the communication unit 710 shown in FIG. 11 may be a communication interface. Optionally, the communication interface may be an input/output interface or a transceiver circuit. The processing unit 720 may be a processing device. The functions of the processing device can be partially or fully realized by software.

In an implementation manner, the functions of the processing device may be partially or fully implemented by software. In this implementation manner, the processing device may include a memory and a processor, where the memory is used to store a computer program, and the processor reads and executes the computer program stored in the memory to execute the internal Realized processing. For example, the processing performed by the processing unit 720 described above is executed.

In another implementation manner, the functions of the processing device may be partially or fully implemented by hardware. In this implementation, the processing device includes an input interface circuit, a logic circuit, and an output interface circuit. The input interface circuit is used to obtain the PDCP sequence number of the first data packet that needs to be decompressed by the header among the data packets received from the terminal device; the logic circuit is used to obtain the PDCP sequence number of the first data packet that needs to be decompressed by the header. Beginning with the PDCP sequence number, the header decompression process is performed on the data packet received from the terminal device.

Refer to FIG. 12, which is a schematic structural diagram of a terminal device provided by this application. As shown in FIG. 12, the terminal device 800 includes a processor 801 and a transceiver 802.

Optionally, the terminal device 800 further includes a memory 803. Among them, the processor 801, the transceiver 802, and the memory 803 can communicate with each other through an internal connection path to transfer control signals and/or data signals.

Among them, the memory 803 is used to store computer programs. The processor 801 is configured to execute a computer program stored in the memory 803, so as to implement various functions of the communication device 500 in the foregoing device embodiment.

Specifically, the processor 801 may be used to perform operations and/or processing performed by the processing unit 520 described in the apparatus embodiment (for example, FIG. 9), and the transceiver 802 may be used to perform operations and/or processing performed by the communication unit 510. .

Optionally, the memory 803 may also be integrated in the processor 801 or independent of the processor 801.

Optionally, the terminal device 800 may further include an antenna 804 for transmitting the signal output by the transceiver 802. Alternatively, the transceiver 802 receives signals through an antenna.

Optionally, the terminal device 800 may further include a power supply 805 for providing power to various devices or circuits in the terminal device.

In addition, in order to make the functions of the terminal device more complete, the terminal device 800 may further include one or more of an input unit 806, an output unit 807, an audio circuit 808, a camera 809, and a sensor 810. The audio circuit may also include a speaker 8082, a microphone 8084, etc., which will not be repeated.

Optionally, when the communication apparatus 500 is a terminal device, the communication unit 510 shown in FIG. 9 may be the transceiver 804 shown in FIG. 12, and the processing unit 520 may be the processor 801.

Optionally, when the communication device 500 is a chip or an integrated circuit, the communication unit 510 shown in FIG. 9 may be a communication interface, and the processing unit 520 is a processor.

Refer to FIG. 13, which is a schematic structural diagram of a network device provided by this application. The network device 1000 may correspond to the first network device (for example, the source base station) in each method embodiment.

As shown in FIG. 13, the network device 1000 includes an antenna 1101, a radio frequency device 1102, and a baseband device 1103. The antenna 1101 is connected to the radio frequency device 1102. In the uplink direction, the radio frequency device 1102 receives signals from the terminal equipment through the antenna 1101, and sends the received signals to the baseband device 1103 for processing. In the downlink direction, the baseband device 1103 generates a signal that needs to be sent to the terminal device, and sends the generated signal to the radio frequency device 1102. The radio frequency device 1102 transmits the signal through the antenna 1101.

The baseband device 1103 may include one or more processing units 11031. The processing unit 11031 may specifically be a processor.

In addition, the baseband device 1103 may further include one or more storage units 11032 and one or more communication interfaces 11033. The storage unit 11032 is used to store computer programs and/or data. The communication interface 11033 is used to exchange information with the radio frequency device 1102. The storage unit 11032 may specifically be a memory, and the communication interface 11033 may be an input/output interface or a transceiver circuit.

Optionally, the storage unit 11032 may be a storage unit on the same chip as the processing unit 11031, that is, an on-chip storage unit, or a storage unit on a different chip from the processing unit, that is, an off-chip storage unit. This application does not limit this.

In an implementation, when the communication device 600 shown in FIG. 10 is completely corresponding to the second network device in the method embodiment, the communication device 600 may be implemented by the network device 1000 shown in FIG. 13, or in other words, the first A network device can be as shown in Figure 13. For example, the processing unit 610 of the communication device 600 shown in FIG. 10 may be the baseband device 1103 shown in FIG. 13. The communication unit 620 may be the radio frequency device 1102 shown in FIG. 13.

Refer to FIG. 14, which is a schematic structural diagram of a network device provided by this application. The network device 2000 may correspond to the first network device (for example, the target base station) in each method embodiment.

As shown in FIG. 14, the network equipment 2000 includes an antenna 2101, a radio frequency device 2102, and a baseband device 2103. The antenna 2101 is connected to the radio frequency device 2102. In the uplink direction, the radio frequency device 2102 receives signals from the access network equipment through the antenna 2101, and sends the received signals to the baseband device 2103 for processing. In the downlink direction, the baseband device 2103 generates a signal that needs to be sent to the terminal device or the access network device, and sends the generated signal to the radio frequency device 2102. The radio frequency device 2102 transmits the signal through the antenna 2101.

The baseband device 2103 may include one or more processing units 21031. The processing unit 21031 may specifically be a processor.

In addition, the baseband device 2103 may further include one or more storage units 21032 and one or more communication interfaces 21033. The storage unit 21032 is used to store computer programs and/or data. The communication interface 21033 is used to exchange information with the radio frequency device 2102. The storage unit 21032 may specifically be a memory, and the communication interface 21033 may be an input/output interface or a transceiver circuit.

Optionally, the storage unit 21032 may be a storage unit on the same chip as the processing unit 21031, that is, an on-chip storage unit, or a storage unit on a different chip from the processing unit, that is, an off-chip storage unit. This application does not limit this.

In an implementation, when the communication apparatus 700 shown in FIG. 11 completely corresponds to the first network device in the method embodiment, the communication apparatus 700 may be the network device 2000 shown in FIG. 14. For example, the communication unit 710 of the communication device 700 shown in FIG. 11 may be the radio frequency device 2102 shown in FIG. 14. The processing unit 720 may be the baseband device 2103 shown in FIG. 14.

In addition, this application also provides a communication system, including one or more terminal devices, one or more first network devices, and one or more second network devices provided in this application.

For example, the communication system includes one or more terminal devices provided in this application, and one or more first network devices. Further, the communication system may also include one or more second network devices.

For another example, the communication system includes one or more first network devices and one or more second network devices provided in this application. Further, the communication system may also include one or more terminal devices.

The present application also provides a computer-readable storage medium with a computer program stored on the computer-readable storage medium, and when the computer program is executed by a computer, the computer executes the operations performed by the terminal device in any method embodiment and /Or processing.

The present application also provides a computer-readable storage medium with a computer program stored on the computer-readable storage medium, and when the computer program is executed by a computer, the computer executes any of the method embodiments executed by the second network device Operation and/or processing.

The present application also provides a computer-readable storage medium having a computer program stored on the computer-readable storage medium, and when the computer program is executed by a computer, the computer executes any of the method embodiments executed by the first network device Operation and/or processing.

This application also provides a computer program product. The computer program product includes computer program code. When the computer program code runs on a computer, the computer executes the operations performed by the terminal device in any method embodiment and/or deal with.

This application also provides a computer program product. The computer program product includes computer program code. When the computer program code runs on a computer, the computer can execute the operations performed by the second network device in any method embodiment. /Or processing.

This application also provides a computer program product. The computer program product includes computer program code. When the computer program code is run on a computer, the computer can execute the operations performed by the first network device in any method embodiment. /Or processing.

The application also provides a chip including a processor. The memory used to store the computer program is provided independently of the chip, and the processor is used to execute the computer program stored in the memory to execute the operation and/or processing performed by the terminal device in any method embodiment.

Further, the chip may also include a communication interface. The communication interface may be an input/output interface, an input/output circuit, etc. Further, the chip may also include the memory.

The application also provides a chip including a processor. The memory for storing the computer program is provided independently of the chip, and the processor is used to execute the computer program stored in the memory to execute the operation and/or processing performed by the second network device in any method embodiment.

The application also provides a chip including a processor. The memory for storing the computer program is provided independently of the chip, and the processor is used to execute the computer program stored in the memory to perform the operation and/or processing performed by the first network device in any method embodiment.

The processor in the embodiment of the present application may be an integrated circuit chip, which has the ability to process signals. In the implementation process, the steps of the foregoing method embodiments can be completed by hardware integrated logic circuits in the processor or instructions in the form of software. The processor can be a general-purpose processor, digital signal processor (digital signal processor, DSP), application specific integrated circuit (ASIC), field programmable gate array (field programmable gate array, FPGA) or other programmable logic Devices, discrete gates or transistor logic devices, discrete hardware components. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like. The steps of the method disclosed in the embodiments of the present application may be directly embodied as being executed and completed by a hardware encoding processor, or executed by a combination of hardware and software modules in the encoding processor. The software module can be located in a mature storage medium in the field such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, registers. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

The memory in the embodiments of the present application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. Among them, the non-volatile memory can be read-only memory (ROM), programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), and electrically available Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory. The volatile memory may be random access memory (RAM), which is used as an external cache. By way of exemplary but not restrictive description, many forms of RAM are available, such as static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), and synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection dynamic random access memory (synchlink DRAM, SLDRAM) ) And direct memory bus random access memory (direct rambus RAM, DRRAM). It should be noted that the memories of the systems and methods described herein are intended to include, but are not limited to, these and any other suitable types of memories.

A person of ordinary skill in the art can be aware that the units and algorithm steps of the examples described in the embodiments disclosed herein can be implemented by electronic hardware or a combination of computer software and electronic hardware, depending on the specific technical solution. Application and design constraints. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered beyond the scope of this application.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the embodiments of the present application.

In addition, the functional units in each embodiment of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.

If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium. Based on this understanding, the technical solution of this application essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the method described in each embodiment of the present application.

The above are only specific implementations of this application, but the protection scope of this application is not limited to this. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed in this application. Should be covered within the scope of protection of this application. Therefore, the protection scope of this application should be subject to the protection scope of the claims.

Claims

A method for processing data packets, characterized in that it comprises:

The terminal device obtains the packet data convergence protocol PDCP sequence number of the first data packet that needs to be decompressed by the header among the data packets received from the first network device;

The terminal device performs header decompression processing on the data packet received from the first network device according to the PDCP sequence number of the first data packet that needs to be decompressed by the header.
The method according to claim 1, wherein the terminal device acquiring the PDCP sequence number of the first data packet that needs to be decompressed by the header among the data packets received from the first network device comprises:

The terminal device receives first indication information from the second network device, where the first indication information is used to indicate the PDCP sequence number of the first header decompressed data packet.
The method according to claim 2, wherein the terminal device receiving the first indication information from the second network device comprises:

The terminal device receives a radio resource control RRC reconfiguration message from the second network device, where the RRC reconfiguration message carries one or more of the first indication information, where each first indication information is used to indicate The corresponding PDCP sequence number of the first packet that needs to be decompressed by the header; or,

The terminal device receives the PDCP control protocol data unit PDU from the second network device, and the PDCP control PDU carries the first indication information, where the first indication information is used to indicate that the PDCP control PDU is The corresponding PDCP sequence number of the first packet that needs to be decompressed by the header.
The method according to claim 1, wherein the terminal device acquiring the PDCP sequence number of the first data packet that needs to be decompressed by the header among the data packets received from the first network device comprises:

The terminal device obtains the PDCP sequence number of the first data packet that needs to be decompressed by the header according to the first data packet received from the first network device, wherein the RLC sequence of the first data packet The number is the preset radio link control RLC sequence number.
The method according to claim 4, wherein the preset RLC sequence number is 0.
The method according to any one of claims 1 to 5, wherein the terminal device performs a response to the first network device according to the PDCP sequence number of the first packet decompressed by the header. The received data packet undergoes header decompression processing, including:

According to the PDCP sequence number of the first data packet that needs to be decompressed by the header, the terminal device starts from the data packet corresponding to the PDCP sequence number of the first data packet that needs to be decompressed by the header. Reorder the data packets received by the first network device, and perform header decompression on the data packets received from the first network device in the order after the reordering.
A method for processing data packets, characterized in that it comprises:

The second network device generates first indication information, where the first indication information is used to indicate that the terminal device needs the first packet data convergence protocol PDCP sequence of the header decompressed data packet among the data packets received from the first network device number;

The second network device sends the first indication information to the terminal device.
The method according to claim 6, wherein the sending of the first indication information by the second network device to the terminal device comprises:

The second network device sends an RRC reconfiguration message to the terminal device, where the RRC reconfiguration message carries one or more of the first indication information, and each first indication information is used to indicate the requirement of the corresponding bearer. The PDCP sequence number of a packet that is decompressed by the header; or,

The second network device sends a packet data convergence protocol PDCP control protocol data unit PDU to the terminal device, the PDCP control PDU carries the first indication information, and the first indication information is used to indicate the location of the PDCP control PDU. The corresponding PDCP sequence number of the first packet that needs to be decompressed by the header.
A method for processing data packets, characterized in that it comprises:

The first network device acquires the PDCP sequence number of the first data packet that needs header decompression by the first network device among the data packets received from the terminal device;

The first network device starts from the data packet corresponding to the PDCP sequence number of the first data packet that needs to be decompressed by the header, and performs header decompression processing on the data packet received from the terminal device.
The method according to claim 9, wherein the acquiring, by the first network device, the PDCP sequence number of the first data packet that needs to be decompressed by the header among the data packets received from the terminal device comprises:

The first network device receives second indication information from the terminal device, where the second indication information is used to indicate the PDCP sequence number of the first data packet that needs to be decompressed by the header among the data packets sent by the terminal device .
The method according to claim 10, wherein the first network device receiving the second indication information from the terminal device comprises:

The first network device receives an RRC reconfiguration complete message from the terminal device, where the RRC reconfiguration complete message carries one or more of the second indication information, where each second indication information is used to indicate The corresponding PDCP sequence number of the first packet that needs to be decompressed by the header; or,

The first network device receives a PDCP status report from the terminal device, and the PDCP status report carries the second indication information, where the second indication information is used to indicate the bearer corresponding to the PDCP status report The PDCP sequence number of the first packet that needs to be decompressed by the header; or,

The first network device receives a packet data convergence protocol PDCP control protocol data unit PDU from the terminal device, and the PDCP control PDU carries the second indication information, where the second indication information is used to indicate the The PDCP control PDU bears the PDCP sequence number of the first data packet that needs to be decompressed by the header.
The method according to claim 9, wherein the acquiring, by the first network device, of the data packets received from the terminal device that needs to be the first data packet decompressed by the header, comprises:

The first network device obtains the PDCP sequence number of the first data packet that needs to be decompressed by the header according to the second data packet received from the terminal device, wherein the wireless link of the second data packet The route control RLC sequence number is the preset RLC sequence number.
The method according to claim 12, wherein the preset RLC sequence number is 0.
The method according to any one of claims 10-12, wherein the method further comprises:

Sending, by the first network device, a first message to the second network device, where the first message is used to indicate the PDCP sequence number of the first data packet that needs to be decompressed by the header;

And, starting from the data packet corresponding to the PDCP sequence number of the first data packet that needs to be decompressed by the header, the first network device performs header decompression processing on the data packet received from the terminal device, including :

When the first network device receives one or more data packets from the terminal device, the first network device sends the one or more data packets to the second network device;

The first network device receives the one or more data packets after reordering from the second network device, and performs header decompression processing on the one or more data packets in the order after the reordering , Wherein the one or more data packets are reordered starting from the PDCP sequence number of the first data packet that needs to be decompressed by the header.
The method according to any one of claims 10-12, wherein the method further comprises:

Sending, by the first network device, a first message to the second network device, where the first message is used to indicate the PDCP sequence number of the first data packet that needs to be decompressed by the header;

When the first network device receives one or more data packets from the terminal device, the first network device sends the PDCP sequence numbers of the one or more data packets to the second network device;

Receiving, by the first network device, a second message from the second network device, the second message being used to indicate whether header decompression is allowed for the data packet corresponding to the one or more PDCP sequence numbers;

And, starting from the data packet corresponding to the PDCP sequence number of the first data packet that needs to be decompressed by the header, the first network device performs header decompression processing on the data packet received from the terminal device, including :

The first network device starts from the data packet corresponding to the PDCP sequence number of the first data packet that needs to be decompressed by the header, and performs header decompression on the data packet indicated by the second message that is allowed to be decompressed by the header. Compression, and header decompression is not performed on the data packet indicated by the second message that the header is not allowed to be decompressed.
The method according to any one of claims 9-13, wherein the first network device starts from the data packet corresponding to the PDCP sequence number of the first data packet that needs to be decompressed by the header, and Decompressing the header of the data packet received from the terminal device includes:

When the first network device receives the data packet that needs to be decompressed by the first header, the first network device sends the data that needs to be decompressed by the first header to the second network device Packet, and send other data packets received from the terminal device to the second network device after sending the data packet that needs to be decompressed by the first header;

Receiving, by the first network device, the first data packet that needs to be decompressed by the header and the other data packets after reordering from the second network device;

The first network device performs header decompression processing on the data packet that needs to be decompressed by the first header and the other data packets in the order after the reordering.
The method according to any one of claims 9-13, wherein the first network device starts from the data packet corresponding to the PDCP sequence number of the first data packet that needs to be decompressed by the header, and Decompressing the header of the data packet received from the terminal device includes:

When the first network device receives the data packet that needs to be decompressed by the first header, the first network device sends the data that needs to be decompressed by the first header to the second network device The PDCP sequence number of the packet, and sending the PDCP sequence number of one or more data packets received from the terminal device to the second network device after sending the first data packet that needs to be decompressed by the header;

The first network device receives a second message from the second network device, where the second message is used to indicate whether to allow the first network device to access the data packets corresponding to the one or more PDCP sequence numbers. Perform header decompression;

According to the second message, the first network device performs header decompression processing on the data packet that needs to be decompressed by the first header and the one or more data packets.
A method for processing data packets, characterized in that it comprises:

The second network device obtains the PDCP sequence number of the first data packet that needs to be decompressed by the header among the data packets sent by the terminal device;

The second network device assists the first network device in performing header decompression processing on the data packet received from the terminal device according to the PDCP sequence number of the first header decompressed data packet.
The method according to claim 18, wherein the second network device acquiring the PDCP sequence number of the first data packet that needs to be decompressed by the header among the data packets sent by the terminal device comprises:

Receiving, by the second network device, a first message from the first network device, where the first message is used to indicate the PDCP sequence number of the first header decompressed data packet;

The second network device assists the first network device to perform header decompression processing on the data packet received from the terminal device according to the PDCP sequence number of the first header decompressed data packet, including :

The second network device receives one or more data packets from the first network device;

The one or more data packets received from the first network device by the second network device according to the first message start from the PDCP sequence number of the first data packet that needs to be decompressed by the header Reordering is performed, and the one or more data packets after the reordering are sent to the first network device for header decompression processing.
The method according to claim 18, wherein the second network device assists the first network device in pairing the slave terminal according to the PDCP sequence number of the data packet that needs to be decompressed by the first header. The data packet received by the device undergoes header decompression processing, including:

The second network device receives a first message from the first network device, where the first message is used to indicate the PDCP sequence number of the first data packet that needs to be decompressed by the header;

The second network device receives one or more PDCP sequence numbers from the first network device;

The second network device determines, according to the first message, whether to allow the first network device to decompress the header of each data packet corresponding to the one or more PDCP sequence numbers;

The second device sends a second message to the first network device, where the second message is used to indicate whether the first network device is allowed to perform data packets corresponding to the one or more PDCP sequence numbers. Unzip the header.
The method according to claim 18, wherein the second network device acquiring the PDCP sequence number of the first data packet that needs to be decompressed by the header among the data packets sent by the terminal device includes:

The second network device receives the data packet corresponding to the first PDCP serial number from the first network device, and receives other data from the first network device after receiving the data packet corresponding to the first PDCP serial number package;

The second network device reorders the data packet corresponding to the first PDCP sequence number and the other data packets starting from the data packet corresponding to the first PDCP sequence number, and reorders the first data packet after the reordering. A data packet corresponding to a PDCP sequence number and the other data packets are sent to the first network device for header decompression processing.
The method according to claim 18, wherein the second network device acquiring the PDCP sequence number of the first data packet that needs to be decompressed by the header among the data packets sent by the terminal device includes:

The second network device receives a second PDCP sequence number from the first network device, and the second PDCP sequence number is preset to be that the first network device needs the first data packet received from the terminal device. The PDCP sequence number of a packet decompressed by the header;

And, the second network device assists the first network device to perform header decompression processing on the data packet received from the terminal device according to the PDCP sequence number of the first header decompressed data packet ,include:

The second network device receives one or more data packets from the first network device;

The second network device reorders the one or more data packets starting from the data packet corresponding to the second PDCP sequence number, and reorders the data packet corresponding to the second PDCP sequence number after the reordering and The one or more data packets are sent to the first network device for header decompression processing.
A method for processing data packets, characterized in that it comprises:

The terminal device generates second indication information, where the second indication information is used to indicate the PDCP sequence number of the first data packet that needs to be decompressed by the first network device header among the data packets sent by the terminal device;

The terminal device sends the second indication information to the first network device.
The method according to claim 23, wherein the sending of the second indication information by the terminal device to the first network device comprises:

The terminal device sends an RRC reconfiguration complete message to the first network device, where the RRC reconfiguration complete message carries one or more of the second indication information, where each second indication information is used to indicate all The corresponding PDCP sequence number of the first packet that needs to be decompressed by the header; or,

The terminal device sends a PDCP status report to the first network device, and the PDCP status report carries the second indication information, where the second indication information is used to indicate that the corresponding bearer needs to be first The PDCP sequence number of the decompressed data packet; or,

The terminal device sends a PDCP control PDU to the first network device, and the PDCP control PDU carries the second indication information, where the second indication information is used to indicate the bearer corresponding to the PDCP control PDU The PDCP sequence number of the first packet that needs to be decompressed by the header.
A communication device, characterized by comprising a unit for implementing the method according to any one of claims 1-6, 23, and 24.
A communication device, characterized by comprising a unit for implementing the method according to any one of claims 7, 8, 18-22.
A communication device, characterized by comprising a unit for implementing the method according to any one of claims 9-17.
A computer-readable storage medium, characterized by comprising a computer program, when the computer program is executed by a processor, the method according to any one of claims 1-24 is executed.