CN111918335A

CN111918335A - Method and device for processing data packet

Info

Publication number: CN111918335A
Application number: CN201910381560.9A
Authority: CN
Inventors: 严乐; 曾清海; 张宏平; 耿婷婷
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2019-05-08
Filing date: 2019-05-08
Publication date: 2020-11-10
Anticipated expiration: 2039-05-08
Also published as: CN111918335B; WO2020224631A1

Abstract

Before the receiving end performs header decompression on the received data packet, the PDCP serial number of the data packet which needs to be first header decompressed in the data packet sent by the sending end is obtained, so that the receiving end can be prevented from performing header decompression processing on the data packet under the condition that the data packet is out of order to cause errors, and the error rate of header decompression can be reduced.

Description

Method and device for processing data packet

Technical Field

The present application relates to the field of wireless communication technologies, and in particular, to a method and an apparatus for processing a data packet.

Background

In a conventional mobile communication system, along with the movement of a terminal device, a network switches the terminal device from a source cell to a target cell for data transmission through a switching process, and after the switching process is completed, the terminal device is switched to a target base station for communication. In the handover process, after the source base station sends the handover message to the terminal device, data transmission between the terminal device and the source base station is interrupted until the terminal device is successfully handed over to the target base station, the terminal device can perform data transmission with the target base station, and at this time, data transmission can not be resumed.

In order to improve user experience and system performance, the third generation partnership project (3 GPP) proposes a requirement for implementing 0ms handover interruption delay in the handover process, and provides a handover enhancement scheme, such as an eMBB (enhanced matrix before break, MBB) scheme. In the eMBB scheme, after the terminal device receives the handover message from the source base station, on 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 device 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, the source base station may forward data with the target base station. Specifically, the source base station forwards a PDCP Service Data Unit (SDU) to which a packet data convergence protocol sequence number (PDCP SN) is allocated to the target base station. The target base station performs header compression, ciphering and the like on the PDCP SDUs. Once the terminal device successfully accesses the target base station, the target base station may send PDCP SDUs received from the source base station and processed by the target base station to the terminal device. Thereby a handover interruption delay of 0ms can be achieved.

In the above process, the header compression processing of the PDCP SDU by the target base station is also referred to as robust header compression (ROHC). ROHC is currently recognized as an ideal way of header compression for wireless links. After the sending end performs the processing of PDCP layers such as ROHC on the PDCP SDU, a PDCP Protocol Data Unit (PDU) is obtained, and the receiving end performs header decompression on the received PDCP PDU, which is called ROHC header decompression. ROHC header decompression requires that PDCP PDUs be in-order.

However, in many cases, after the transmitting end performs the processing of the PDCP layer such as ROHC on the PDCP SDU and transmits the processed PDCP SDU to the receiving end, the PDCP PDUs received by the receiving end may be out of order, resulting in a high error rate of ROHC header decompression.

Disclosure of Invention

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

In a first aspect, the present application provides a method for processing a data packet, in which a terminal device obtains a packet data convergence protocol PDCP sequence number of a data packet that needs to be first header-decompressed in a data packet received from a first network device; and the terminal equipment performs header decompression processing on the data packet received from the first network equipment from the PDCP sequence number of the data packet needing first header decompression.

In the technical scheme of the application, before decompressing the received data packet header, the receiving end can avoid the error of header decompression caused by header decompression processing of the data packet performed by the receiving end under the condition of data packet disorder by obtaining the PDCP sequence number of the data packet which needs to be first header decompressed in the data packet sent by the sending end, thereby reducing the error rate of header decompression.

With reference to the first aspect, in some implementations of the first aspect, the obtaining, by the terminal device, a PDCP sequence number of a packet that needs to be header-decompressed first in a packet received from the first network device includes: the terminal device receives first indication information from the second network device, wherein the first indication information is used for indicating the PDCP sequence number of the data packet needing first header decompression.

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

The terminal device may obtain the PDCP sequence number of the data packet to be decompressed by the first header from the source base station during the handover. Or, the source base station may notify the terminal device of the PDCP sequence number of the first packet that needs to be header-decompressed, so that the terminal device may reorder the packet received from the target base station from the PDCP sequence number, and perform header decompression on the packet according to the order after reordering, thereby reducing the error rate of header decompression.

With reference to the first aspect, in some implementations of the first aspect, the receiving, by the terminal device, the first indication information from the second network device includes: the terminal device receives a Radio Resource Control (RRC) reconfiguration message from the second network device, wherein the RRC reconfiguration message carries one or more pieces of first indication information, and each piece of first indication information is used for indicating a PDCP sequence number of a corresponding bearer data packet which needs to be subjected to header decompression; or, the terminal device receives a PDCP control protocol data unit PDU from the second network device, where the PDCP control PDU carries the first indication information, and the first indication information is used to indicate a PDCP sequence number of a data packet that needs to be first header-decompressed and is carried by a bearer corresponding to the PDCP control PDU.

With reference to the first aspect, in some implementations of the first aspect, the obtaining, by the terminal device, a PDCP sequence number of a packet that needs to be header-decompressed first in a packet received from the first network device includes: the terminal device obtains the PDCP sequence number of the first packet to be header-decompressed according to the first packet received from the first network device, where the RLC sequence number of the first packet is a preset RLC sequence number.

In this way, by presetting an RLC sequence number, when the terminal device analyzes the received data packet and determines that the RLC sequence number is the preset RLC sequence number, the PDCP sequence number obtained by analyzing the data packet is the PDCP sequence number of the data packet requiring the first header decompression. Therefore, interaction between the network equipment and the terminal equipment can be avoided, and signaling overhead can be saved.

With reference to the first aspect, in certain implementations 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 performing, by the terminal device, header decompression processing on the data packet received from the first network device according to the PDCP sequence number of the data packet requiring first header decompression includes: and the terminal equipment reorders the data packets received from the first network equipment from the data packets corresponding to the PDCP sequence number of the data packets needing first header decompression according to the PDCP sequence number of the data packets needing first header decompression, and performs header decompression on the data packets received from the first network equipment according to the order after reordering.

In a second aspect, the present application provides a method for processing a data packet, where a second network device generates first indication information, where the first indication information is used to indicate a packet data convergence protocol PDCP sequence number of a data packet that needs to be first header-decompressed in a data packet received by a terminal device from a first network device; and the second network equipment sends the first indication information to the terminal equipment.

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

With reference to the second aspect, in some implementations of the second aspect, the sending, by the second network device, the first indication information to the terminal device includes: the second network equipment sends an RRC reconfiguration message to the terminal equipment, wherein the RRC reconfiguration message carries one or more pieces of first indication information, and each piece of first indication information is used for indicating a Packet Data Convergence Protocol (PDCP) sequence number of a corresponding carried data packet which needs to be decompressed by a first header; or, the second network device sends a packet data convergence protocol PDCP control protocol data unit PDU to the terminal device, where the PDCP control PDU carries the first indication information, and the first indication information is used to indicate a PDCP sequence number of a data packet that needs to be first header-decompressed and is carried by a bearer corresponding to the PDCP control PDU.

In a third aspect, the present application provides a method for processing a data packet, where a first network device obtains a PDCP sequence number of a data packet that needs to be first header-decompressed in a data packet received from a terminal device; 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 data packet requiring the first header decompression.

Here, the first network device may correspond to a target base station of the terminal device during a cell handover procedure.

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

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

With reference to the third aspect, in some implementations of the third aspect, the obtaining, by the first network device, a first packet that needs to be subjected to header decompression in a packet received from the terminal device includes: and the first network equipment acquires the PDCP serial number of the data packet needing first header decompression according to a second data packet received from the terminal equipment, wherein the RLC serial number of the radio link control of the second data packet is a preset RLC serial number.

With reference to the third aspect, in certain implementations of the third aspect, the preset RLC sequence number is 0.

With reference to the third aspect, in certain implementations of the third aspect, the method further includes: the first network equipment sends a first message to second network equipment, wherein the first message is used for indicating the PDCP sequence number of the data packet needing first header decompression; the first network device performs header decompression processing on the data packet received from the terminal device, starting from the data packet corresponding to the PDCP sequence number of the data packet requiring first header decompression, and includes: when the first network equipment receives one or more data packets from the terminal equipment, the first network equipment sends the one or more data packets to the second network equipment; 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 according to the order after reordering, wherein the one or more data packets are reordered from the PDCP sequence number of the data packet requiring first header decompression.

With reference to the third aspect, in certain implementations of the third aspect, the method further includes: the first network equipment sends a first message to second network equipment, wherein the first message is used for indicating the PDCP sequence number of the data packet needing first header decompression; when the first network equipment receives one or more data packets from the terminal equipment, the first network equipment sends PDCP sequence numbers of the one or more data packets to the second network equipment; the first network equipment receives a second message from a second network equipment, wherein the second message is used for indicating whether header decompression is allowed to be carried out on data packets corresponding to the one or more PDCP sequence numbers, and the second message is generated according to the first message and the one or more PDCP sequence numbers; and the first network device performs header decompression processing on the data packet received from the terminal device from the PDCP sequence number of the data packet requiring the first header decompression, including: and the first network equipment performs header decompression on the data packet which is indicated by the second message and allowed to be subjected to header decompression, and does not perform header decompression on the data packet which is indicated by the second message and not allowed to be subjected to header decompression, starting from the data packet corresponding to the PDCP sequence number of the data packet needing first header decompression.

With reference to the third aspect, in some implementations of the third aspect, the performing, by the first network device, header decompression processing on the data packet received from the terminal device according to the PDCP sequence number of the data packet requiring first header decompression includes: when the first network equipment receives the data packet needing to be decompressed by the first header, the first network equipment sends the data packet needing to be decompressed by the first header to the second network equipment, and sends other data packets received from the terminal equipment to the second network equipment after sending the data packet needing to be decompressed by the first header; the first network equipment receives the data packet needing the first header decompression and the other data packets after reordering from the second network equipment; and the first network equipment carries out header decompression processing on the data packet needing to be decompressed by the first header and the other data packets according to the sequence after reordering.

With reference to the third aspect, in some implementations of the third aspect, the performing, by the first network device, header decompression processing on the data packet received from the terminal device according to the PDCP sequence number of the data packet requiring first header decompression includes: when the first network equipment receives the data packet needing to be decompressed by the first header, the first network equipment sends the PDCP sequence number of the data packet needing to be decompressed by the first header to the second network equipment, and sends the PDCP sequence number of one or more data packets received from the terminal equipment to the second network equipment after sending the data packet needing to be decompressed by the first header; the first network equipment receives a second message from the second network equipment, wherein the second message is used for indicating whether the first network equipment is allowed to carry out header decompression on a data packet corresponding to each of the one or more PDCP sequence numbers; and the first network equipment carries out header decompression processing on the data packet needing to be decompressed by the first header and the one or more data packets according to the second message.

In a fourth aspect, the present application provides a method for processing a data packet, including: the second network equipment acquires a PDCP sequence number of a data packet which needs first header decompression in the data packet sent by the terminal equipment; and the second network equipment assists the first network equipment to carry out header decompression processing on the data packet received from the terminal equipment according to the PDCP serial number of the data packet which needs to be subjected to header decompression firstly.

With reference to the fourth aspect, in some implementations of the fourth aspect, the acquiring, by the second network device, the PDCP sequence number of the packet that needs to be header-decompressed first in the data packet sent by the terminal device includes: the second network equipment receives a first message from the first network equipment, wherein the first message is used for indicating the PDCP sequence number of the data packet needing first header decompression; 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 data packet requiring the first header decompression, including: the second network device receiving one or more data packets from the first network device; and the second network equipment reorders the data packets received from the first network equipment from the data packets corresponding to the PDCP sequence numbers of the data packets needing to be first header-decompressed according to the first message, and sends the reordered data packets to the first network equipment for header decompression.

With reference to the fourth aspect, in some implementations of the fourth aspect, the assisting, by the second network device, 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 data packet that needs to be decompressed by the first header includes: the second network equipment receives a first message from the first network equipment, wherein the first message is used for indicating the PDCP sequence number of the data packet needing first header decompression; receiving, by the second network device, one or more PDCP sequence numbers from the first network device; the second network equipment judges whether to allow the first network equipment to carry out header decompression on the data packet corresponding to each of the one or more PDCP sequence numbers or not according to the first message; and the second device sends a second message to the first network device, wherein the second message is used for indicating whether the first network device is allowed to perform header decompression on the data packet corresponding to each of the one or more PDCP sequence numbers.

With reference to the fourth aspect, in some implementations of the fourth aspect, the acquiring, by the second network device, the PDCP sequence number of the packet that needs to be header-decompressed first in the data packet sent by the terminal device includes: the second network equipment receives the data packet corresponding to the first PDCP sequence number from the first network equipment, and receives other data packets from the first network equipment after receiving the data packet corresponding to the first PDCP sequence number; and the second network equipment reorders the data packet corresponding to the first PDCP sequence number and the other data packets from the first PDCP sequence number, and sends the reordered data packet corresponding to the first PDCP sequence number and the other data packets to the first network equipment for header decompression.

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 data packet to be decompressed by the first header.

With reference to the fourth aspect, in some implementations of the fourth aspect, the acquiring, by the second network device, the PDCP sequence number of the packet that needs to be header-decompressed first in the data packet sent by the terminal device includes: the second network equipment receives a second PDCP sequence number from the first network equipment, wherein the second PDCP sequence number is preset as the PDCP sequence number of a data packet which needs first header decompression in the data packets received by the first network equipment from the terminal equipment; 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 data packet requiring the first header decompression, including: the second network device receiving one or more data packets from the first network device; and the second network equipment reorders the one or more data packets from the data packet corresponding to the second PDCP sequence number, and sends the reordered data packet corresponding to the second PDCP sequence number and the one or more data packets to the first network equipment for header decompression.

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 packet corresponding to the second PDCP sequence number is the packet that needs to be decompressed by the first header.

It should be noted that the number "second" of the second PDCP sequence number is only for distinguishing from the number "first" of the first PDCP sequence number, and the technical solution should not be limited.

In a fifth aspect, the present application provides a method for processing a data packet, where a terminal device generates second indication information, where the second indication information is used to indicate a PDCP sequence number of a first data packet that needs to be decompressed by a first network device header in a data packet sent by the terminal device; and the terminal equipment sends the second indication information to the first network equipment.

With reference to the fifth aspect, in some implementations of the fifth aspect, the sending, by the terminal device, the second indication information to the first network device includes: the terminal device sends an RRC reconfiguration complete message to the first network device, where the RRC reconfiguration complete message carries one or more second indication information, where each second indication information is used to indicate a PDCP sequence number of a first header-decompressed data packet of the corresponding bearer; or, the terminal device sends 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 a PDCP sequence number of a data packet that needs to be decompressed by the first header of the corresponding bearer; or, the terminal device sends 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 a PDCP sequence number of a first header-decompressed data packet of a bearer corresponding to the PDCP control PDU.

In a sixth aspect, the present application provides a communication device having the functionality of implementing the method of the first aspect or any possible implementation manner thereof, or the functionality of implementing the method of the fifth aspect or any possible implementation manner thereof. The functions can be realized by hardware, and the functions can also be realized by executing corresponding software by hardware. The hardware or software includes one or more units corresponding to the above functions.

In a seventh aspect, the present application provides a communication device having the functionality of the method of the second aspect or any possible implementation thereof, or the functionality of the method of the fourth aspect or any possible implementation thereof. The functions can be realized by hardware, and the functions can also be realized by executing corresponding software by hardware. 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 having the functionality to implement the method of the third aspect or any possible implementation thereof. The functions can be realized by hardware, and the functions can also be realized by executing corresponding software by hardware. The hardware or software includes one or more units corresponding to the above functions.

In a ninth aspect, the present application provides a terminal device comprising a processor and a memory. The memory is adapted to store a computer program, and the processor is adapted to call and run the computer program stored in the memory, to cause the terminal device to perform the method of the first aspect or any possible implementation thereof, or to cause the terminal device to perform the method of the fifth aspect or any possible implementation thereof.

In a tenth aspect, the present application provides a network device comprising a processor and a memory. The memory is adapted to store a computer program, and the processor is adapted to call and run the computer program stored in the memory, so that the network device performs the method of the second aspect or any possible implementation thereof, or performs the method of the fourth aspect or any possible implementation thereof.

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

In an eleventh aspect, the present application provides a network device comprising a processor and a memory. The memory is used for storing a computer program and the processor is used for calling and executing the computer program stored in the memory, so that the network device executes the method of the third aspect or any possible implementation manner thereof.

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

In a twelfth aspect, the present application provides a computer-readable storage medium having stored thereon computer instructions which, when run on a computer, cause the computer to perform the method of the first aspect or any possible implementation thereof, or cause the computer to perform the method of the fifth aspect or any possible implementation thereof.

In a thirteenth aspect, the present application provides a computer-readable storage medium having stored thereon computer instructions which, when run on a computer, cause the computer to perform the functions of the method of the second aspect or any possible implementation thereof, or to perform the method of the fourth aspect or any possible implementation thereof.

In a fourteenth aspect, the present application provides a computer-readable storage medium having stored thereon computer instructions which, when run on a computer, cause the computer to perform the method of the third aspect or any possible implementation thereof.

In a fifteenth aspect, the present application provides a chip comprising a processor. The processor is adapted to read and execute the computer program stored in the memory to perform the method of the first aspect or any possible implementation thereof, or to perform the method of the fifth aspect or any possible implementation thereof.

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

Further optionally, the chip further comprises a communication interface.

In a sixteenth aspect, the present application provides a chip comprising a processor. The processor is adapted to read and execute the computer program stored in the memory to perform the method of the second aspect or any possible implementation thereof or to perform the method of the fourth aspect or any possible implementation thereof.

Further optionally, the chip further comprises a communication interface.

In a seventeenth aspect, the present application provides a chip comprising a processor. The processor is adapted to read and execute the computer program stored in the memory to perform the method of the third aspect or any possible implementation thereof.

Further optionally, the chip further comprises a communication interface.

In an eighteenth aspect, the present application provides a computer program product comprising computer program code to, when run on a computer, cause the computer to perform the method of the first aspect or any possible implementation thereof, or the method of the fifth aspect or any possible implementation thereof.

In a nineteenth aspect, the present application provides a computer program product comprising computer program code which, when run on a computer, causes the computer to perform the method of the second aspect or any possible implementation thereof, or the method of the fourth aspect or any possible implementation thereof.

In a twentieth aspect, the present application provides a computer program product comprising computer program code which, when run on a computer, causes the computer to perform the method of the third aspect or any possible implementation thereof.

Drawings

Fig. 1 is an architecture diagram of a communication system suitable for use with embodiments of the present application.

Fig. 2 is a schematic diagram of a handover procedure in an eMBB scheme.

Fig. 3 is a diagram illustrating functional blocks of a PDCP layer.

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

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

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

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

Fig. 8 is a diagram illustrating a reordering function module commonly used by a first network device and a second network device.

Fig. 9 is a schematic diagram of a communication device 500 provided in the present application.

Fig. 10 is a schematic diagram of a communication device 600 provided in the present application.

Fig. 11 is a schematic diagram of a communication device 700 provided in the present application.

Fig. 12 is a schematic structural diagram of a terminal device provided in the present application.

Fig. 13 is a schematic structural diagram of a network device provided in the present application.

Fig. 14 is a schematic structural diagram of a network device provided in the present application.

Detailed Description

The technical solution in the present application will be described below with reference to the accompanying drawings.

The technical solution of the embodiment of the present application may be applied to various communication systems, for example, a Long Term Evolution (LTE) system, an LTE Frequency Division Duplex (FDD) system, an LTE Time Division Duplex (TDD), a Universal Mobile Telecommunications System (UMTS), a Worldwide Interoperability for Microwave Access (WiMAX) communication system, a future fifth generation (5G) system, a New Radio (NR), or the like.

Terminal equipment in the embodiments of the present application may refer to user equipment, access terminals, subscriber units, subscriber stations, mobile stations, remote terminals, mobile devices, user terminals, wireless communication devices, user agents, or user devices. The terminal device may 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), a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a future 5G network or a terminal device in a future evolved Public Land Mobile Network (PLMN), etc., which is not limited in this application.

The network device in the embodiment of the present application may be any device having a wireless transceiving function. The network devices include, but are not limited to: evolved Node B (eNB), Radio Network Controller (RNC), Node B (Node B, NB), Base Station Controller (BSC), Base Transceiver Station (BTS), home base station (home evolved NodeB, or home Node B, HNB), baseband unit (base band unit, BBU), Access Point (AP) in wireless fidelity (WIFI) system, wireless relay Node, wireless backhaul Node, Transmission Point (TP), or transmission and reception point (TP), etc., and may also be a fifth generation (TRP) system, for example, a gbb or TP in a new radio, NR), or a group of antennas may also constitute a network panel or a multiple-panel TRP system, or a network panel may constitute a network panel or a group of antennas including a network Node (NB), such as a baseband unit (BBU) or a Distributed Unit (DU).

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). The CU implements part of the function of the gNB and the DU implements part of the function of the gNB. For example, a CU is responsible for handling non-real-time protocols and services, and implementing functions of a Radio Resource Control (RRC) layer and a Packet Data Convergence Protocol (PDCP) layer. The DU is responsible for processing a physical layer protocol and a real-time service, and implements functions of a Radio Link Control (RLC) layer, a Medium Access Control (MAC) layer, and a Physical (PHY) layer. The AAU implements part of the physical layer processing functions, radio frequency processing and active antenna related functions. Since the information of the RRC layer eventually becomes or is converted from the information of the PHY layer, the higher layer signaling, such as the RRC layer signaling, may also be considered to be transmitted by the DU or transmitted by the DU and the AAU under this architecture.

It is to be understood that the network device may be a device comprising one or more of a CU, a DU, an AAU. In addition, the CU may be divided into network devices in an access network (RAN), or may be divided into network devices in a Core Network (CN), which is not limited in this application.

Referring to fig. 1, fig. 1 is an architecture diagram of a communication system suitable for use with embodiments 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 a transmitting end, and the terminal device 103 is a receiving end. Conversely, when the terminal device 103 sends a signal, the terminal device is a transmitting end, and the network device 101 and/or the network device 102 is a receiving end.

The technical scheme of the application is suitable for the scene of switching the terminal equipment.

In a conventional handover process, after a source base station sends a handover message to a UE, data transmission between the UE and the source base station is interrupted until the UE is successfully handed over to a 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, and at this time, the air interface can resume data transmission. Therefore, there is an interruption delay in the handover process.

In order to improve the user experience, the 3GPP proposes a requirement for realizing 0ms mobile interruption delay in the handover process. To realize 0ms handover interruption delay, an eMBB scheme is proposed for the interruption delay.

Referring to fig. 2, fig. 2 is a schematic diagram of a handover procedure in an eMBB scheme. In the handover procedure proposed by the eMBB scheme, after sending a handover message to the UE, the source base station may perform data forwarding (data forwarding) with the target base station. That is, the source base station forwards the PDCP service data unit (service data unit, SDU) to which the packet data convergence protocol sequence number (PDCP SN) is allocated to the target base station, that is, the PDCP SDU(s) and the PDCP SN corresponding to each PDCP SDU are sent from the source base station to the target base station. Wherein each of the PDCP SDUs assigned the PDCP SNs is associated with one PDCP SN. These PDCP SDUs forwarded to the target base station are processed by the target base station for header compression, ciphering, adding PDCP headers, etc. The description of the other steps in fig. 2 can be found in the prior art.

In addition, the handover procedure of the eMBB shown in fig. 2 is merely an example. Alternatively, the handover procedure may include other steps than those shown in fig. 2, or the steps shown in fig. 2 may be performed partially, but not completely.

In order to facilitate understanding of the technical solution of the present application, the conventional PDCP layer is described below with reference to fig. 3.

Referring to fig. 3, fig. 3 is a schematic diagram of functional modules of a PDCP layer. The PDCP entity of the transmitting end and the PDCP entity of the receiving end are shown in fig. 3. The PDCP entity of the transmitting end may perform PDCP SN allocation, header compression, integrity protection, ciphering, PDCP header addition (add PDCP header), routing/copying, etc., and the PDCP entity of the receiving end may perform PDCP header removal, deciphering, integrity verification, reordering, copy discard, header decompression, etc. It should be understood that, in the downlink data transmission, the PDCP entity of the transmitting side is the PDCP entity of the network device, and the PDCP entity of the receiving side is the PDCP entity of the terminal device. In uplink data transmission, the PDCP entity of the transmitting side is the PDCP entity of the terminal device, and the PDCP entity of the receiving side is the PDCP entity of the network device.

For Downlink (DL), the network device serves as a sender of a data packet, and the user plane protocol stack architecture thereof can be seen in fig. 4.

Since the PDCP layers are bearer granularities, each bearer has a PDCP layer corresponding thereto. Referring to fig. 4, taking a certain bearer as an example, fig. 4 is a schematic diagram of a user plane protocol stack of a network device. The PDCP layer of the network device (e.g., the source base station shown in fig. 4) generates a sequence number (sequence number) of a packet, i.e., the above PDCP SN, or performs PDCP SN allocation, and performs header compression (header compression), integrity protection (integrity) and PDCP header addition (add PDCP header) on the packet, and then delivers the packet to the RLC layer. And then the data is sent to the terminal equipment after being processed by an RLC layer, an MAC layer and a PHY layer in sequence.

Fig. 4 is only an example of the formula. The PDCP layer of the source or target base station shown in fig. 4 may further include an integrity protection (integrity protection) (when serving as a sending end), an integrity verification (integrity verification) (when serving as a receiving end), a PDCP header addition (add PDCP header), a routing/copying (copying), a reordering (reordering), and a copying discard (copying). These functional modules may be referred to as shown in fig. 3, but not shown in fig. 4. The routing/replication module in fig. 4 is different from that in fig. 3, and will be explained in the following embodiments.

In order to improve the reliability of data transmission during data transmission, in an alternative implementation, the network device may perform a duplication (duplication) process or operation on the data packet. The process of copying the downstream packet is referred to herein as DL duplication. For downlink, the duplication process refers to that for a certain PDCP SN (which is assigned by the source base station), 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. Wherein, a PDCP SDU is transferred to the functional modules of the source base station itself, such as compression and ciphering, and the source base station sends it to the UE after performing header compression using the header compression (e.g., ROHC) context of the source base station, ciphering using the key of the source base station, and so on. The other PDCP SDU (and the PDCP SN corresponding to the PDCP SDU) is forwarded to the target base station by the source base station, and the PDCP PDU is generated by performing header compression by using a header compression (such as ROHC) context of the target base station, encrypting a key of the target base station and the like. 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 may 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 keeps data transmission with the source base station, that is, keeps the user plane protocol stack of the corresponding source base station, and does not perform layer 2 reset (reset) or re-establishment (re-establishment) on the user plane protocol stack of the source base station. It is understood that the 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, which is used to initiate RACH to the target and perform data transmission. In an alternative implementation, the UE may perform a duplication (duplication) process or operation on the data packet. The process of copying the uplink packet is referred to herein as UL duplication. For uplink, the duplication process means that the UE can generate 2 PDCP SDUs for a certain PDCP SN (the PDCP SN is assigned by the UE). In other words, the UE generates two PDCP SDUs corresponding to the same PDCP SN. Wherein, one PDCP SDU is transferred to the header compression, ciphering, and other functional modules corresponding to the source base station, and after performing header compression using a header compression (e.g., ROHC) context of the source base station, ciphering a key of the source base station, and other processing, the UE sends it to the source base station. And the other PDCP SDU is transferred to a header compression, encryption and other functional modules corresponding to the target base station, header compression, encryption and other processing are carried out by using a header compression (such as ROHC) context of the target base station, a key of the target base station is used for encryption and other processing, a PDCP PDU is generated, and the UE sends the PDCP PDU 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 (or maintains two security keys, such as a key of the source base station and a key of the target base station) respectively corresponding to the source base station and the target base station, or the UE maintains two sets of header compression (such as ROHC) contexts respectively corresponding to the source base station and the target base station. The UE decrypts the data packet by using the corresponding security context (or key) according to whether the received data packet is from the source base station or the target base station, and performs header decompression and other processing by using the corresponding header decompression context.

During the period from the time when the UE is successfully switched to the target base station to the time when the UE releases the connection with the source base station, the UE can respectively perform uplink data transmission with the source base station and the target base station. Optionally, the transmission may be a UL duplicate packet or not. The UE performs header compression using the ROHC context of the source base station, and transmits PDCP PDUs to the RLC layer, the MAC layer and the PHY layer of the source base station after performing encryption and other processing using the key of the source base station. And the UE performs header compression on the ROHC context of the target base station, encrypts the ROHC context by using a key of the target base station and transmits the PDCP PDU to an RLC layer, an MAC layer and a PHY layer of the target base station after the encryption and other processing.

Taking Uplink (UL) data transmission as an example, a UE is used as a sending end, and taking a certain bearer as an example, a user plane protocol stack architecture of the UE may be similar to a protocol stack architecture of a network side during downlink data transmission, as shown in fig. 5.

Referring to fig. 5, fig. 5 is a schematic diagram of a user plane protocol stack of the UE. For a certain bearer, in fig. 5, the UE has two PDCP layers, one of which corresponds to the source base station and the other of which corresponds to the target base station. For example, under the protocol stack architecture shown in fig. 5, if the UE performs duplicate operation on the UL data packet, for the same PDCP SN, two PDCP layers respectively have their corresponding PDCP SDUs. The PDCP layer corresponding to the source base station performs header compression by using a header compression context of the source base station, generates a PDCP PDU after performing encryption and other processing by using a secret key of the source base station, performs header compression by using a header compression context of the target base station, and generates a PDCP PDU after performing encryption and other processing by using a secret key of the target base station. The protocol stacks on the left side in fig. 5 (e.g., PHY1, MAC1, RLC1) may correspond to the target base station, and the protocol stacks on the right side (e.g., PHY2, MAC2, RLC2) may correspond to the source base station.

The header addition in fig. 5 refers to PDCP header addition.

Further, it should be understood that, when the UE is a transmitting end, two PDCP entities (or PDCP layers) of the UE shown in fig. 5 may be the transmitting PDCP entity (or PDCP layer) corresponding to a certain bearer. The sending PDCP entity may further include an integrity protection (integrity protection), an add PDCP header, a routing/copying function, and the like, and in fig. 5, the routing/copying function is located in the PDCP entity corresponding to the source base station. When the UE serves as a receiving end, corresponding to a certain bearer, the two PDCP entities (or PDCP layers) of the UE shown in fig. 5 may be receiving PDCP entities (or PDCP layers), and the receiving PDCP entities may further include functional modules such as integrity verification (integrity verification), PDCP header removal (remove PDCP header), reordering (reordering), copy discard, and the like. These functional modules may be referred to as shown in fig. 3, but not shown in fig. 5.

Optionally, corresponding to a certain bearer, the UE side has a PDCP layer (for example, the PDCP layer is referred to as common PDCP), and the PDCP layer corresponds to both the source base station and the target base station, at this time, a user plane protocol stack of the UE may be as shown in fig. 6.

As shown in fig. 6, fig. 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 duplicate. Specifically, under the protocol stack architecture shown in fig. 6, if the UE performs duplicate operation on the UL data packet, for the same PDCP SN, the common PDCP layer performs header compression using the header compression context corresponding to the source base station and performs processing such as encryption using the key of the source base station, and then generates one PDCP PDU, and at the same time, the common PDCP layer performs header compression using the header compression context corresponding to the target base station and performs processing such as encryption using the key of the target base station, and then generates another PDCP PDU, that is, for a certain PDCP SN, the UE generates 2 PDCP PDUs corresponding to the same PDCP SN. The UE performs header compression using the ROHC context of the source base station, and transmits a packet to the source base station after performing encryption and other processing using the key of the source base station. In addition, the UE transmits a packet to the target base station after header compression using the ROHC context of the target base station and encryption or the like using a key of the target base station.

In addition, when the UE is a transmitting end, the PDCP entity (or PDCP layer) shown in fig. 6 may be a transmitting PDCP entity (or PDCP layer) corresponding to a certain bearer. The sending PDCP entity may further include an integrity protection (integrity protection), an add PDCP header, a routing/copy (duplication), and other functional modules. When the UE serves as a receiving end, corresponding to a certain bearer, the PDCP entity (or PDCP layer) shown in fig. 6 may be a receiving PDCP entity (or PDCP layer), and the receiving PDCP entity may further include functional modules such as integrity verification (integrity verification), PDCP header removal (remove PDCP header), reordering (reordering), and copy discard. These functional modules may be referred to as shown in fig. 3, but not shown in fig. 6.

The user plane protocol stack architectures of the network device and the UE shown in fig. 4 to fig. 6 are only an example, and the technical solution of the present application is not limited to adopt other protocol stack architectures or their variants, and is applicable to the technical solution of the present application as long as it is ensured that data on the network side or the UE side can be transmitted through two legs to implement 0ms handover interruption delay.

From the network side perspective, the source base station decrypts PDCP PDUs received from the UE using the key of the source base station and performs header decompression using the header decompression context of the source base station. The target base station decrypts the PDCP PDU received from the UE using the key of the target base station, and performs header decompression using a header decompression context of the target base station.

However, the RLC layer of the receiving end does not guarantee that the data packets are 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.

To this end, the present 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, and is described below separately.

It should be noted that, the first network device and the second network device in this application are only examples of network side devices. For example, the first network device may be a target base station of the terminal device during handover, and the second network device is a source base station during handover.

Downlink data transmission

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

The terminal device may obtain the PDCP sequence number of the packet that needs to be first header-decompressed in various ways, which are listed as follows for illustration.

Mode 1

The terminal device receives the first indication information from the second network device. The first indication information is used for indicating the PDCP sequence number of the first header-decompressed data packet in the data packet 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 transmits the first indication information to the terminal device.

In one implementation, the second network device sends a Radio Resource Control (RRC) reconfiguration message to the terminal device, where the RRC reconfiguration message carries one or more pieces of first indication information. Each first indication message is used for indicating the PDCP sequence number of the first header-decompressed data packet in the data packets transmitted on the bearer corresponding to the first indication message. For example, each piece of first indication information is a PDCP sequence number of a packet that needs to be first header-decompressed in a packet transmitted on a bearer corresponding to the first indication information.

It should be noted that the PDCP sequence number is a Data Radio Bearer (DRB) with granularity, where an RB may include a Data Radio Bearer (DRB) and a Signaling Radio Bearer (SRB). Therefore, the first indication information carried in the RRC reconfiguration message is also at the granularity of radio bearers. Different bearers have their own corresponding PDCP sequence numbers of packets that require first header decompression.

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

Therefore, if the RRC reconfiguration message carries multiple pieces of first indication information, each piece of 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 packet requiring the first header decompression of the bearer corresponding to the first indication information.

Optionally, when the RRC reconfiguration message carries multiple pieces of first indication information, each piece of first indication information is associated with an RB identifier, which indicates that the PDCP sequence number indicated by the first indication information is a PDCP sequence number of a packet that needs to be first header-decompressed on an RB corresponding to the RB identifier. 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 may be an RRC reconfiguration message containing a synchronization reconfiguration (reconfiguration within sync) information element, or may be an RRC connection reconfiguration message containing a mobile control information (Mobility control info) information element, which is not limited herein. Also, the RRC reconfiguration message may take 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 (PDU) to the terminal device, where the PDCP control PDU carries the first indication information.

Unlike RRC reconfiguration messages, PDCP control PDUs are bearer granular by themselves. 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 a PDCP sequence number, which is a PDCP sequence number of a packet on a corresponding bearer that needs first header decompression.

Mode 2

When the terminal equipment receives a data packet with a preset RLC serial number from the first network equipment, the terminal equipment analyzes the data packet to obtain a PDCP serial number corresponding to the data packet. The PDCP sequence number corresponding to the packet is the PDCP sequence number of the packet that needs the first header decompression from the first network device.

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

Alternatively, the preset RLC sequence number may be specified by a protocol or agreed by the terminal device and the network, which is not limited herein.

In one implementation, the predetermined 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 corresponding processing of the PDCP layer on the data packet received from the first network device, starting from the data packet with the RLC sequence number of 0.

Specifically, the RLC layer of the terminal device must wait for receiving the RLC PDU (or RLC SDU) with RLC SN of 0 before starting to deliver data to its PDCP layer (e.g., the RLC layer delivers the RLC SDU with RLC SN of 0 to the PDCP layer), that is, the first packet that the terminal device delivers to its PDCP layer must be a data packet with RLC SN of 0. Even if the RLC layer of the terminal device receives a data packet with RLC SN of 0 before it receives the data packet with RLC SN of 0, the RLC layer buffers the data packet with RLC SN of 0 and does not deliver it to the PDCP layer, and the RLC layer receives a data packet with RLC SN of 0 and delivers it to the PDCP layer, and then delivers the buffered data packet with RLC SN of 0 to the PDCP layer.

After the PDCP layer of the terminal device resolves the PDCP SN corresponding to the data packet with the RLC SN of 0, the data packet from the first network device is reordered according to the PDCP SN (that is, the PDCP SN is used as an initial value of reordering), and then the PDCP layer of the terminal device performs header decompression on the reordered data packet in sequence.

In this embodiment, the first packet that the RLC layer of the terminal device delivers to the PDCP layer of the terminal device must be a packet with RLC SN of 0, and the RLC SNs of the packets that the RLC layer subsequently delivers to the PDCP layer may be out of order or in order, which is not limited to this (for example, the second packet that the RLC layer of the terminal device delivers to the PDCP layer of the terminal device may be a packet with RLC SN of 1, or may be a packet with RLC SN of 3, or may be a packet with RLC SN of 2, which is not limited to this). The PDCP layer of the terminal device may reorder received data packets, such as received RLC SDUs (or PDCP PDUs).

Optionally, when the RLC layer of the UE receives a data packet with RLC SN of 0 from the first network device, the RLC layer sends indication information to the PDCP layer, where the indication information is used to indicate the PDCP layer to start reordering or header decompression.

Specifically, the RLC transmission mode includes an UM mode and an AM mode. Accordingly, the RLC Data PDU includes umd (unscented Mode Data) PDU and AMD (Acknowledged Mode Data) PDU.

In AM mode, because the AMD PDU header carries RLC SN, the first network device (i.e. the sending end) processes the data packet conventionally, and the terminal device (i.e. the receiving end) processes according to the above method.

In UM mode, only when RLC SDU is segmented, UMD PDU header carries RLC SN (An UMD PDU header contains the SN field only in the preceding decoded RLC SDU is segmented). In the UM mode, the first network device (i.e., the sending end) needs to perform special processing on a data packet with an RLC SN of 0, that is, the RLC layer of the sending end must process the data packet with the RLC SN in a format of a data packet carrying the RLC SN, for example, the RLC layer of the sending end performs segmentation processing on an RLC SDU with the 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), and the specific format may refer to the description in section 6.2.2.3 in TS38.322-f50 (for example, the specific format of the UMD PDU may refer to fig. 6.2.2.3-2, 6.2.3-3, 6.2.2.3-4, and 6.2.2.3-5);

optionally, in the UM mode, the sending end may perform special processing on the data packet whose RLC SN is not 0 according to the above method; alternatively, no special processing may be performed, that is, the format of the generated UMD PDU is UMD PDU containing a complete RLC SDU, and the specific format of the UMD PDU may refer to the description in section 6.2.2.3 of TS38.322-f50 (for example, the specific format of the UMD PDU may refer to fig. 6.2.2.3-1).

In the UM mode, the processing method of the receiving end (i.e., the terminal device) is similar to the processing method of the receiving end (i.e., the terminal device) in the AM mode, and the processing may be performed in the above-described manner 2.

520. And the terminal equipment performs header decompression processing on the data packet received from the first network equipment according to the PDCP sequence number of the data packet which needs to be subjected to the first header decompression.

In any one of the manners listed in step 510, the terminal device knows the PDCP sequence number of the first header-decompressed data packet in the data packets received from the first network device. At this time, the terminal device may reorder the data packets received from the first network device from the PDCP sequence number of the data packet requiring the first header decompression, and perform header decompression on the data packets received from the first network device according to the order after reordering.

Optionally, for a certain bearer, the header decompression processing of the data packet received from the first network device by the terminal device may be performed in a PDCP layer corresponding to the first network device, or may be performed in a common PDCP (common PDCP) layer (the common PDCP layer corresponds to both the first network device and the second network device), for example, a user plane protocol stack of the terminal device may be as in fig. 4 or fig. 5 above. The user plane protocol stack of the terminal device is not limited herein.

Optionally, in each embodiment of the downlink data transmission, if the second network device performs a duplication processing operation on the data packet, the data packet that needs to be first decompressed is a data packet that is first subjected to the duplication processing and is sent by the second network device to the PDCP SDUs of the first network device (or is a minimum value of PDCP SNs corresponding to the data packets subjected to the duplication processing and sent by the second network device to the PDCP SDUs of the first network device), or is a minimum value of PDCP SNs corresponding to the PDCP SDUs sent by the second network device to the PDCP SDUs of the first network device.

In other words, the terminal device needs to obtain the PDCP sequence numbers of the first DL duplicate packets from the first network device (or the minimum values of the PDCP SNs corresponding to the DL duplicate packets from the first network device).

Uplink data transmission

610. The first network equipment acquires the PDCP sequence number of the data packet which needs the first header decompression in the data packet received from the terminal equipment.

Similar to downlink data transmission, the first network device may obtain the PDCP sequence number of the first header-decompressed data packet in the data packets received from the terminal device in various ways. Several are listed below as examples.

Mode 1

The first network device receives second indication information from the terminal device, where the second indication information is used to indicate a PDCP sequence number of a first header-decompressed data packet in data packets sent by the terminal device.

In one implementation manner, the terminal device sends an RRC reconfiguration complete message to the first network device, where the RRC reconfiguration complete message carries one or more pieces of second indication information. Wherein, each second indication information is used for indicating the PDCP sequence number of the data packet requiring the first header decompression, which is carried corresponding to the second indication information.

Here, the second indication information is also granular in radio bearers. Therefore, the RRC reconfiguration complete message may carry one or more second indication information. The second different indication information is used to indicate PDCP sequence numbers of packets requiring first header decompression on different bearers.

Optionally, when the RRC reconfiguration complete message carries multiple pieces of second indication information, each piece of second indication information is associated with one RB, and it indicates that the PDCP sequence number indicated by the second indication information is the PDCP sequence number of the packet that needs to be first header-decompressed on the RB corresponding to the identifier of the RB. 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 packets requiring first header decompression on different bearers may be the same or different from each other, or the PDCP sequence numbers of the packets requiring first header decompression on partial bearers are the same, which is not limited in this application.

In another implementation manner, the terminal device sends a PDCP status report to the first network device, where the PDCP status report carries the second indication information. The PDCP status report is sent with bearer as granularity, and therefore, the second indication information carried in each PDCP status report is used to indicate the PDCP sequence number of the data packet that needs to be first header-decompressed on the bearer corresponding to the PDCP status report. Or, the terminal device sends an RLC status report to the first network device, where the RLC status report carries the second indication information.

In another implementation, the terminal device sends a PDCP control PDU to the first network device, where the PDCP control PDU carries the second indication information. The PDCP control PDUs are sent with bearer granularity, and therefore, the second indication information carried in each PDCP control PDU is used to indicate the PDCP sequence number of the data packet that needs to be first header decompressed on the bearer corresponding to the PDCP control PDU.

Mode 2

When the first network equipment receives a data packet with a preset RLC serial number from the terminal equipment, the first network equipment analyzes the data packet to obtain a PDCP serial number corresponding to the data packet. The PDCP sequence number corresponding to the data packet is the PDCP sequence number of the data packet that needs the first header decompression in the data packet received from the terminal device.

That is, the first network device determines the PDCP sequence number of the packet with the preset RLC sequence number received from the terminal device as the PDCP sequence number of the packet from the terminal device that needs the first header decompression operation performed by the first network device. Or, the first network device determines the data packet of the preset RLC sequence number received from the terminal device as the data packet requiring the first header decompression.

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, and the present application is not limited thereto.

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

Through any one of the above manners, the first network device obtains the PDCP sequence number of the packet that needs to be first header-decompressed from 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 data packet requiring the first header decompression.

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 data packet requiring the first header decompression.

After the first network device obtains the PDCP sequence number of the data packet that needs to be first header-decompressed, the first network device may perform header decompression on the data packet received from the terminal device in multiple specific ways according to whether the first network device has a reordering function module, which will be described below.

Case 1

The first network device has a function of reordering the data packets, or the first network device has a function module of reordering the data packets.

For simplicity of description, the functional module for reordering packets will be referred to as a reordering functional module hereinafter.

In one possible implementation, the first network device and the second network device each have a reordering function (the reordering function 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 the reordering function module.

Referring to fig. 7, fig. 7 is a schematic diagram of a first network device and a second network device each having a reordering function. As shown in fig. 7, the source base station and the target base station each have a functional module for reordering and header decompression. Wherein, the reordering function module of the source base station reorders as shown in fig. 7 (1), and the reordering function of the target base station reorders as shown in fig. 7 (2). In the above data transmission as an example, the source base station and the target base station respectively complete PDCP header removal (remove PDCP header), decryption (decryption), integrity verification (integrity verification), and after completing reordering (reordering)/copy discard (duplicate discard), header decompression (header discard) and other processes in the receive buffer (replay buffer), reorder, duplicate packet detection/discard processes may be performed on data packets on two legs on a common reordering function module. Finally, the reordering function module delivers the data packet to the upper layer. Wherein this common reordering functionality is reordered as shown in fig. 7 (3).

It should be noted that the source base station and the target base station shown in fig. 7 each further have a duplicate dropping function, or referred to as duplicate packet dropping function. Alternatively, the copy discard function may be designed on one functional block with the reordering function. For example, reordering (1)/copy discard as shown in FIG. 7 indicates that the functional block has both reordering and copy discard functions. Alternatively, the source base station and the target base station do not have the copy discard function, for example, the source base station does not have reordering in the receiving buffer (1), and the target base station does not have reordering in the receiving buffer (2).

Here, the duplicate discard function refers to a function of detecting duplicate packets (i.e., duplicate packets described above) for the same PDCP SN, and discarding one of the duplicate packets if two packets having the same PDCP SN are detected.

In one possible implementation, the common reordering/duplicate packet discarding function (reordering (3)/duplicate discarding as shown in fig. 7) may be located at the source base station before the target base station receives the SN status transfer message sent by 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 at the target base station.

In another possible implementation, the first network device and the second network device share one reordering function. Wherein the common reordering function may be provided on the first network device. Alternatively, the common reordering functionality may be provided on the second network device.

In case 1, no matter which specific implementation manner is adopted, after the first network device receives the data packet from the terminal device, the reordering function module arranged on the first network device may reorder, starting from the PDCP sequence number of the first data packet to be header-decompressed, the data packets whose PDCP sequence numbers are sequentially incremented backward, the data packets received from the terminal device. After the reordering is completed, the first network device performs header decompression on the data packets according to the order after the reordering.

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

Specifically, the RLC transmission modes include an Unacknowledged Mode (UM) and an Acknowledged Mode (AM). Accordingly, the RLC Data PDU includes umd (unscented Mode Data) PDU and AMD (Acknowledged Mode Data) PDU.

In AM, since the AMD PDU header carries the RLC SN, the terminal device (i.e. the sending end) performs conventional processing on the data packet, and the first network device (i.e. the receiving end) performs processing according to the above method.

In UM, only when RLC SDU is segmented, the UMD PDU header carries RLC SN (An UMD PDU header contains the SN field only in the corrected RLC SDU is segmented). Under UM, a terminal device (i.e., a transmitting end) needs to perform special processing on a data packet with an RLC SN of 0 sent to a first network device, that is, an RLC layer of the transmitting end must process the data packet with the RLC SN carrying format for the data packet with the RLC SN of 0, for example, the RLC layer of the transmitting end performs segmentation processing on an RLC SDU with the RLC SN of 0, and a format of a generated UMD PDU is an UMD PDU including X bit SN (for example, X ═ 6 or 12). Alternatively, the specific format of the UMD PDU can be described, for example, in TS38.322-f50, section 6.2.2.3 (e.g., FIG. 6.2.2.3-2, FIG. 6.2.2.3-3, FIG. 6.2.2.3-4, FIG. 6.2.2.3-5).

Optionally, in UM, the sending end sends a data packet with RLC SN not 0, and may perform special processing according to the above method; alternatively, no special processing may be performed, i.e., the format of the generated UMD PDU is a UMD PDU containing a complete RLC SDU. Alternatively, the specific format of UMD PDUs may be as described in TS38.322-f50, section 6.2.2.3 (e.g., FIG. 6.2.2.3-1).

In UM, the processing method of the receiving end (i.e., the first network device) is similar to the processing method of the receiving end (i.e., the first network device) in AM, and may be processed in the above-described manner 2.

It can be seen that in case 1, the first network device can independently complete reordering of the data packets received from the terminal device (i.e., reordering (2) in fig. 7), and perform header decompression on the data packets according to the order after reordering.

Case 2

The first network device does not have a reordering function.

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

It can be understood 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 (i.e. the target base station) does not have a reordering, copy discarding function before performing the header decompression function. For example, the target base station shown in fig. 8 does not have the functional module of reordering (2) compared to that in fig. 7. Therefore, the first network device cannot reorder the data packets received from the terminal device. Therefore, header decompression of a data packet by a first network device requires a second network device to assist in completion. Or, in another way, in case 2, the second network device does not have a reordering function module, and the second network device (i.e. the source base station) does not have a reordering, copying and discarding function before performing the header decompression function. For example, compared to fig. 7, the source base station does not have a functional module for reordering (1), and the target base station has a functional module for reordering (2). Therefore, the second network device cannot reorder the data packets received from the terminal device. Therefore, header decompression of the data packet by the second network device requires the first network device to assist in completion.

Referring to fig. 8, fig. 8 is a schematic diagram illustrating a reordering function module commonly used by a first network device and a second network device. As an example, as shown in fig. 8, reordering (3) on the source base station is set on the source base station as a reordering function module common to the source base station and the target base station. And the target base station does not have a functional module for reordering after header decompression. Or, in another mode, the common reordering function module after header decompression of the source base station and the target base station is set on the target base station.

Continuing with the uplink 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 decrypts using the key of the source base station, thereby completing integrity verification. Then, the source base station 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, respectively, and the reordering operation is performed as the reordering (1) function module in fig. 8.

It should be noted that, in the uplink data transmission, if the terminal device performs duplicate operation on the data packet, the reordering (1) function module of the source base station will receive the duplicate data packet. So, unlike the existing PDCP layer shown in fig. 3, the receiving PDCP entity (the PDCP entity shown on the right side in fig. 3) in fig. 3 has a duplicate discard function, whereas the source base station shown in fig. 8 needs to disable a duplicate discard (duplicate discard) function.

The reordering (1) function module of the source base station reorders the data packets received from the UE, and then delivers the data packets to the header decompression (header decompression) function module of the source base station for header decompression. After the header decompression is completed, the data packet after the header decompression is delivered to the reordering (3)/copy discard function module by the header decompression module to execute the reordering/repeat packet discard processing. After reordering, duplicate detection, duplicate discard, the packet is delivered to the upper layer.

For the target base station, after receiving the UL PDCP PDU from the UE, the target base station removes the PDCP header, decrypts the received UL PDCP PDU using the key of the target base station, and performs integrity verification. Since the header decompression must ensure that the data packets are in order, the target base station has no reordering function. Therefore, the header decompression processing of the data packet by the target base station includes the following method 1 and method 2.

The method comprises the following steps: as shown in path 1 in fig. 8, the target base station transmits data packets received from the terminal device to the source base station, and these data packets are reordered by the reordering function module (reordering (1) shown in fig. 8) of the source base station. After the reordering is completed, 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.

The method 2 comprises the following steps: as shown in path 2 in fig. 8, the target base station transmits only the PDCP sequence number of the packet to the source base station, which checks whether the PDCP sequence number is in order. If the PDCP sequence numbers are in-sequence, the source base station indicates that the target base station can carry out header decompression on the data packet corresponding to the PDCP sequence numbers. Then, the target base station delivers the data packet corresponding to the PDCP sequence number to its own header decompression module for header decompression according to the indication of the source base station. After the target base station completes header decompression, the data packet after header decompression is delivered to the common reordering/copying discarding function module for reordering and discarding the copied packet (i.e. duplicate data packet). And after the common reordering/copying discarding function module completes reordering, duplicate data packet detection and discarding on the data packets of the two legs, the common reordering/copying discarding function module delivers the data packets to an upper layer.

Here, the common reordering/copy discard function is as the reordering (3)/copy discard function shown in fig. 8.

It should be understood that fig. 8 illustrates the common reordering/copy discard function at the source base station. Optionally, in another implementation, the common reordering/duplication discarding function module may also be located in the target base station. In this case, the decompression of the header of the data packet by the network side is similar to that shown in fig. 8, and a person skilled in the art can also easily know the processing procedure of the data packet when the reordering/copying discarding function module is located in the target base station according to the processing procedure of the data packet when the reordering/copying discarding function module is located in the source base station, which is appropriately omitted here to avoid repeated descriptions.

It should be noted that fig. 8 illustrates the reordering function module being disposed in the source base station as an example (i.e., the reordering function module (1) is located in the source base station). For example, the target base station does not receive the SN status transfer message sent by the source base station. Alternatively, the reordering function module may be disposed in the target base station. For example, the target base station receives an SN status transfer message transmitted by the source base station.

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

Mode A

After acquiring the PDCP data packet of the data packet requiring the first header decompression, the first network device sends a first message to the second network device, where the first message is used to indicate the PDCP sequence number of the data packet requiring the first header decompression in the data packets received by the first network device from the terminal device.

After the first network device notifies the second network device of the PDCP sequence number of the first packet to be header-decompressed by the first network device through the first message, the first network device sends one or more received packets from the terminal device 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 reorders the one or more data packets received from the first network device starting from the PDCP sequence number of the data packet requiring first header decompression indicated by the first message, and returns the reordered one or more data packets to the first network device for header decompression processing.

It can be seen that the second network device assists the first network device in reordering the data packets received by the first network device from the terminal device. And then, the first network equipment receives the reordered data packets returned by the second network equipment, and sequentially carries out header decompression processing on the data packets according to the reordered sequence.

Mode B

The second network device can learn, according to the first message, the PDCP sequence number of the first header-decompressed data packet in the data packets received by the first network device from the terminal device. This is the same as the above-described mode a.

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

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

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

Alternatively, the first network device may send the PDCP sequence number of each data packet received from the terminal device to the second network device for determination. 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 data packet that needs to be header-decompressed, the second message returned by the second network device to the first network device indicates that decompression of the data packet header corresponding to the PDCP sequence number is allowed.

Then, if the PDCP sequence number received by the second network device from the first network device is sequentially incremented from the PDCP sequence number of the first header-decompressed data packet, the second message returned by the second network device indicates that the first network device is allowed to perform header decompression on 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 is not sequentially incremented from the PDCP sequence number of the packet requiring the first header decompression, it indicates that the PDCP sequence number of the packet received by the first network device from the terminal device or the PDCP sequence number indicated by the second network device to the first network device is out of order, and therefore, the second message returned by the second network device for the out-of-order PDCP sequence number indicates that the first network device is not allowed to perform header decompression on the packet.

It is assumed that the second network device knows from the first message that the PDCP SN of the first packet that needs to be header-decompressed by the first network device is 3, which is illustrated below.

The second network device receives the first PDCP SN of 3 from the first network device, and returns an ACK to the first network device, indicating that header decompression can be performed on the data packet corresponding to the PDCP SN of 3.

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

Conversely, if the second PDCP SN received by the second network device from the first network device is 6, the second network device returns a NACK to the first network device indicating that header decompression of the packet with PDCP SN 6 is not allowed.

It should be understood that the PDCP SN of 6 is only used as an example, that if the PDCP SN received by the second network device from the first network device is not sequentially incremented from the PDCP SN of the first header decompression required data packet, it means that the data packet received by the first network device from the terminal device is out of order, and the header decompression is performed after the reordering is required, otherwise, the header decompression is erroneous.

Optionally, the first network device may also send the PDCP sequence numbers of a plurality of data packets to the second network device in the receiving order after receiving the plurality of data packets. And the second network equipment judges whether the data packet corresponding to each of the plurality of PDCP sequence numbers received from the first network equipment can be subjected to header decompression or not according to the PDCP sequence number of the data packet needing to be subjected to header decompression firstly.

It is assumed that the second network device knows from the first message that the PDCP SN of the first packet that needs to be header-decompressed is 3, which is illustrated below.

The second network device receives a plurality of PDCP sequence numbers from the first network device, which are in turn PDCP SN-3, 5,4, 6. The second network device determines according to the PDCP SN of the first header-decompressed data packet being 3, where the PDCP SNs 3,5,4, and 6 are not sequentially incremented, that is, the PDCP sequence numbers of the data packets received by the first network device from the terminal device are out of order. Therefore, the second network device returns a NACK to the first network device, indicating that the first network device is not allowed to perform header decompression on the data packets corresponding to the PDCP SN 3,5,4, and 6 respectively.

In one implementation, the second network device may return the reordered PDCP sequence numbers to the first network device while returning the NACK, so as to instruct the first network device to perform header decompression on the data packets corresponding to the PDCP sequence numbers according to the indicated order of the reordered PDCP sequence numbers.

For example, the second network device returns 3,4,5,6 to the first network device. And the first network equipment respectively performs header decompression on the data packets with the PDCP SNs being 3,5,4 and 6 according to the sequence of the returned PDCP SNs of the second network equipment.

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

For example, the second network device returns 1000 to the first network device, which indicates that the first network device is allowed to perform header decompression on the data packet corresponding to the first PDCP sequence number sent to the second network device by the first network device, and the data packets corresponding to the following 3 PDCP sequence numbers do not allow header decompression by the first network device.

As can be seen, in the 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 the 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 determines, according to the PDCP sequence number of the data packet that needs to be first header-decompressed, indicated in the first message, whether to allow the first network device to perform header decompression on the data packet corresponding to the PDCP sequence number, and further indicates the first network device through the second message.

It should be understood that, in the mode a and the mode B, the source base station assists the target base station in performing header decompression on the data packet received from the terminal device, and refer to the description of the path 1 and the path 2 in fig. 8, respectively.

In the above mode a and mode B, after the first network device obtains the PDCP sequence number of the data packet whose header needs to be decompressed by the first network device, the first message indicates the PDCP sequence number of the data packet whose header needs to be decompressed to the second network device. Then, when the first network device receives the data packet from the terminal device, the first network device transmits the received data packet or the PDCP sequence number of the received data packet to the second network device in the order of the data packets received from the terminal device.

Other ways in which the second network device assists the first network device in header decompression of a data packet received from the terminal device are described below, such as way C and way D below.

Mode C

The first network equipment acquires a PDCP data packet of a data packet needing first header decompression, wherein the PDCP sequence number of the PDCP data packet is the first PDCP sequence number.

The first network equipment receives a data packet from the terminal equipment, and when the first network equipment receives the data packet corresponding to the first PDCP serial number from the terminal equipment, the first network equipment firstly sends the data packet corresponding to the first PDCP serial number to the second network equipment, and then sends other data packets received from the terminal equipment to the second network equipment.

In other words, in the method C, the first packet sent by the first network device to the second network device is the packet to be decompressed by the first header by default. Equivalently, the first network device implicitly informs the second network device of the PDCP sequence number of the first header-decompressed data packet in the data packet received by the first network device from the terminal device, and does not need to inform the first network device of the PDCP sequence number by other additional messages (e.g., the first message).

In the method C, from the perspective of the second network device, a PDCP sequence number (hereinafter, referred to as a first PDCP sequence number) of a first packet received by the second network device from the first network device is a first packet that needs to be header-decompressed in a packet 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 packet received from the first network device as a reference for reordering the packets received from the first network device. The second network device reorders the data packets received from the first network device starting with the first PDCP sequence.

Mode D

The first network equipment acquires a PDCP data packet of a data packet needing first header decompression.

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

Similar to the method C, in the 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 packet 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 header-decompressed data packet in the data packet received by the first network device from the terminal device, and does not need to inform the first network device of the PDCP sequence number by other additional messages (e.g., the first message).

Therefore, compared with the mode a or the mode B, the mode C and the mode D can save signaling interaction between the first network device and the second network device, and save signaling overhead.

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

Alternatively, in the embodiments of the methods of the present application, the packet that needs to be first header-decompressed may also be replaced with the first packet that needs to be header-decompressed. That is, the PDCP sequence number of the first packet requiring header decompression may also be replaced with the PDCP sequence number of the first packet requiring header decompression.

Alternatively, if the transmitting end performs a duplication (duplication) operation on the data packets, the receiving end needs to acquire the PDCP sequence number of the first data packet to be duplicated in the transmitted data packets.

In the above embodiments, the description has been given taking as an example that the transmission end of the packet performs the copy processing operation on the packet. In another possible implementation manner, in uplink data transmission or downlink data transmission, the sending end may not perform the copy processing operation on the data packet.

In uplink data transmission, if the data packet is not subjected to the duplication processing operation, that is, the UE only sends UL data to the source base station before sending the RRC reconfiguration message to the target base station. And after the UE sends the RRC reconfiguration complete message, the UE only sends UL data to the target base station. Because some data packets sent by the UE to the source base station may not be successfully received, the UE needs to retransmit the data packets to the target base station, which may also cause the data packets received by the target base station from the UE to be out of order, and thus the PDCP sequence number may also be out of order when the target base station decompresses the data packets, resulting in an error in the header decompression of the target base station.

For example, the UE transmits a packet with PDCP SNs 2,3,4 to the source base station, but the source base station only successfully receives the packet with PDCP SN 2, 4. Wherein, the data packet with PDCP SN 3 fails to be sent. At this time, the UE may have already transmitted a packet with PDCP SN of 5 to the target base station, and then the UE finds that the transmission of the packet with PDCP SN of 3 has failed. If the UE uses the header compression (such as ROHC) context of the target base station to perform header compression on the data packet with PDCP SN 3, and retransmits the data packet to the target base station. The target base station receives the data packet with the PDCP SN of 5 firstly and then receives the data packet with the PDCP SN of 3. If the target base station firstly performs header decompression on the data packet with the PDCP SN of 5 according to the sequence of the received data packets, the header decompression has errors.

Therefore, the present application also proposes a solution for the case where the copy processing operation is not performed on the data packet, and is applicable to both uplink and downlink data transmission. The following is explained with the above data transmission as an example.

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

For example, in the above example, the UE transmits data packets having PDCP SNs 2,3,4 to the source base station, and determines that the transmission of the data packet having the PDCP SN 3 fails after receiving feedback for all the data packets from the source base station. At this time, the UE compresses the packet having the PDCP SN of 3 using the ROHC context of the target base station. Thus, the first data packet sent by the UE to the target base station is a PDCP SN of 3 data packet. And after the UE sends the data packet with the PDCP SN of 3 to the target base station, the UE sends the data packet with the PDCP SN of 5 to the target base station. Thus, the data packet with PDCP SN of 3 will be the first received and header decompressed data packet of the target base station, and the header decompression error can be avoided.

Optionally, in another implementation, the UE may indicate, to the target base station, a PDCP sequence number of a packet that needs header decompression for the first time.

For example, in this example above, the UE indicates a PDCP SN of 3 to the target base station.

In another possible implementation manner, after sending the data packet requiring the first header decompression to the target base station, the UE sends indication information to the target base station, where the indication information is an end marker (end marker), for example. Wherein the indication information (e.g., the end flag) is used to instruct the target base station to start header decompression of the received PDCP PDUs.

It should be noted that, for the packet with PDCP SN of 4 in the above example, the UE may perform header compression on the packet using the ROHC context of the target base station, and then transmit the packet to the target base station. That is, even if the source base station successfully receives the PDCP SN 4 packet, the UE may send the PDCP SN 4 packet to the target base station. And the target base station decrypts the data packet with the PDCP SN of 4, decompresses the header and the like.

Or, in an implementation manner, after the source base station decrypts a successfully received data packet (PDCP PDU) with PDCP SN of 4 using a key of the source base station and performs header decompression on an ROHC context of the source base station, the source base station forwards a PDCP SDU of the data packet with PDCP SN of 4 to the target base station.

The method for processing the data packet provided by the present application is described in detail above.

It is to be understood that, in the above method for processing a data packet, the steps implemented by the terminal device may also be implemented by a component (e.g., a chip or a circuit) that can be used for the terminal device, and the steps implemented by the network device may also be implemented by a component (e.g., a chip or a circuit) that can be used for the network device, which is not limited in this embodiment of the present application.

In the technical scheme of the application, the receiving end can avoid the receiving end from performing header decompression processing on the data packet under the condition of disordered data packets to cause header decompression errors by indicating the PDCP sequence number of the data packet needing first header decompression to the receiving end or presetting the PDCP sequence number of the data packet needing first header decompression, so that the error rate of header decompression can be reduced.

It is to be understood that the above method of handling packets is applicable not only to the eMBB scenario, but also to similar scenarios where out-of-order may occur during header decompression. For example, in the conventional handover, the UE sends an uplink packet with a PDCP SN of 10-20 to the source base station, the source base station successfully receives the packet with the PDCP SN of 10-15, the PDCP SN of the first lost uplink packet indicated in the SN STATUS TRANSFER message sent by the source base station to the target base station 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 data packet with PDCP SN of 10-20 to the target base station, the first received data packet of the target base station is a data packet with PDCP SN of 16, the target base station considers that the data packet with PDCP SN of 16 is the first data packet that needs header decompression, the first packet subjected to header decompression by the target base station is a packet with PDCP SN of 16, at this time, the header decompression fails, and the above method for processing the data packet can be used to solve the problem of the failure of the header decompression.

The following describes an apparatus for processing packets provided in the present application.

Referring to fig. 9, fig. 9 is a schematic diagram of a communication device 500 provided in the present application. The communication device 500 comprises a communication unit 510 and a processing unit 520.

A communication unit 510, configured to obtain a packet data convergence protocol PDCP sequence number of a packet that needs to be first header-decompressed in a packet received from a first network device;

a processing unit 520, configured to perform header decompression processing on the data packet received from the first network device according to the PDCP sequence number of the data packet that needs to be first header decompressed.

Alternatively, the communication unit 510 may be replaced by a receiving unit and/or a transmitting unit.

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

Optionally, the communication device 500 may further include a storage unit for storing codes or data, and the processing unit 520 may call the codes or data in the storage unit, so that the communication device implements corresponding functions or steps.

In one implementation, the communication apparatus 500 may completely correspond to the terminal device in the method embodiment, or the communication apparatus 500 is the terminal device.

Alternatively, the communication unit 510 shown in fig. 9 may be a transceiver. The transceiver has a function of transmitting and/or receiving. The transceiver may also be replaced by a receiver and/or a transmitter. It will be appreciated that the communication unit 510 may also be a transceiver circuit or an interface circuit.

In the downlink data transmission, steps and/or processes performed by the units of the communication apparatus 500 are as follows.

For example, the communication unit 510 receives, from the second network device, first indication information indicating a PDCP sequence number of the packet requiring first header decompression.

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 pieces of the first indication information, where each piece of the first indication information is used to indicate a PDCP sequence number of a first header-decompressed data packet of the corresponding bearer. Alternatively, the first and second electrodes may be,

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

Alternatively, the processing unit 520 may be a processor. The processor is used for executing the steps or processes implemented corresponding to the terminal device in the method embodiments.

For example, the processing unit 520 parses the packet received by the communication unit 510 from the first network device, and when it is determined that the communication unit 510 receives the packet with the preset RLC sequence number, the processing unit 520 parses the packet with the preset RLC sequence number to obtain the PDCP sequence number of the packet requiring the first header decompression.

For another example, the processing unit 520 reorders the data packets received from the first network device, starting from the data packet corresponding to the PDCP sequence number of the data packet requiring the first header decompression, and performs header decompression on the data packets received from the first network device according to the order after reordering.

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

Alternatively, the communication unit 510 shown in fig. 9 may be a communication interface. Alternatively, the communication interface may be an input-output interface or a transceiver circuit. The processing unit 520 may be a processing device. The functionality of the processing means may be partly or wholly implemented by software.

In one implementation, the functionality of the processing means may be implemented partly or wholly in software. In this implementation, the processing device may include a memory and a processor, where the memory is used for storing the computer program, and the processor reads and executes the computer program stored in the memory to perform the processing internally implemented by the terminal device in the embodiments. For example, the processing performed by the processing unit 520 described above is performed.

Alternatively, the processing means may comprise only the processor, the memory for storing the computer program being located outside the processing means. The processor is connected to the memory through the circuit/wire to read and execute the computer program stored in the memory.

In another implementation, the functionality of the processing means may be implemented partly or wholly in 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 for acquiring the data packet to be decompressed by the first header and the data packet received by the communication device from the first network equipment; the logic circuit is used for performing header decompression processing on the data packet received from the first network equipment from the PDCP sequence number of the data packet needing first header decompression; the output interface circuit is used for outputting the data packet after header decompression.

Or the input interface circuit is used for acquiring first indication information; the logic circuit is used for analyzing the first indication information to obtain the PDCP sequence number of the data packet which needs to be decompressed by the first header; the output interface circuit is used for outputting the PDCP sequence number of the data packet needing the first header decompression.

Optionally, the input interface circuit may be configured to acquire an RRC reconfiguration message, and the logic circuit analyzes the RRC reconfiguration message to acquire a PDCP sequence number of the packet that needs to be decompressed by the first header; the output interface circuit is used for outputting the PDCP sequence number of the data packet needing the first header decompression.

Optionally, the input interface circuit may be configured to obtain a PDCP control PDU, and the logic circuit obtains a PDCP sequence number of the data packet that needs to be first header-decompressed according to the PDCP control PDU; the output interface circuit is used for outputting the PDCP sequence number of the data packet needing the first header decompression.

Optionally, the input interface circuit may be configured to obtain a data packet received by the communication apparatus from the first network device, and analyze the data packet by the logic circuit to obtain an RLC sequence number of the data packet, so that when it is determined that the data packet with a preset RLC sequence number is received, the data packet is analyzed to obtain a PDCP sequence number of the data packet, and the PDCP sequence number is determined as the PDCP sequence number of the data packet requiring first header decompression; the output interface circuit is used for outputting the PDCP sequence number of the data packet needing the first header decompression.

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

a communication unit 510, configured to send the second indication 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 pieces of the second indication information, where each piece of the second indication information is used to indicate a PDCP sequence number of a first header-decompressed data packet of the corresponding bearer. Alternatively, the first and second electrodes may be,

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 a PDCP sequence number of a data packet of the corresponding bearer, which needs to be decompressed by the first header. Alternatively, the first and second electrodes may be,

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 a PDCP sequence number of a first header-decompressed data packet of a bearer corresponding to the PDCP control PDU.

Referring to fig. 10, fig. 10 is a schematic diagram of a communication device 600 provided in the present application. The communication device 600 includes a processing unit 610 and a transceiving unit 620.

Optionally, the communication apparatus 600 may correspond to the second network device in each method embodiment for downlink data transmission, or may also be a chip or an integrated circuit mounted on the second network device. In this case, the functions of the respective units included in communication apparatus 600 are as follows.

A processing unit 610, configured to generate first indication information, where the first indication information is used to indicate a packet data convergence protocol PDCP sequence number of a first header-decompressed data packet in a data packet received by a terminal device from a first network device;

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

Optionally, the communication device 600 may further include a storage unit for storing codes or data, and the processing unit 610 may call the codes or data in the storage unit, so that the communication device 600 implements corresponding functions or steps.

Alternatively, the communication unit 620 may be replaced by a receiving unit and/or a transmitting unit.

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

In one implementation, the communication apparatus 600 may completely correspond to a second network device (e.g., a source base station) in the method embodiment, or the communication apparatus 600 is the second network device.

In such an implementation, the transceiving unit 620 shown in fig. 10 may be a transceiver. The transceiver has a function of transmitting and/or receiving. The transceiver may also be replaced by a receiver and/or a transmitter. The processing unit 610 may be a processor. The transceiver and the processor are used to perform the steps or processes performed by the second network device in the method embodiments of downstream data transmission.

For example, the communication unit 620 sends an RRC reconfiguration message to the terminal device, where the RRC reconfiguration message carries one or more pieces of the first indication information, and each piece of the first indication information is used to indicate a packet data convergence protocol PDCP sequence number of a corresponding bearer that needs a first header-decompressed data packet.

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 a PDCP sequence number of a first header-decompressed data packet of a bearer corresponding to the PDCP control PDU.

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

In this implementation, the communication unit 620 shown in fig. 10 may be a communication interface. Alternatively, the communication interface may be an input-output interface or a transceiver circuit. The processing unit 610 may be a processing device. The functionality of the processing means may be partly or wholly implemented by software.

In one implementation, the functionality of the processing means may be implemented partly or wholly in software. In this implementation, the processing means may include a memory for storing the computer program and a processor for reading and executing the computer program stored in the memory to perform the processing internally implemented by the second network device in the embodiments. For example, the processing performed by the processing unit 610 described above is performed.

In another implementation, the functionality of the processing means may be implemented partly or wholly in 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, from among data packets received by the terminal device from the first network device, a PDCP sequence number of a first header-decompressed data packet; the output interface circuit is used for outputting the first indication information.

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

The processing unit 610 is configured to obtain a PDCP sequence number of a packet that needs to be first header-decompressed in a data packet sent by a terminal device, and assist a 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 packet that needs to be first header-decompressed.

In a possible implementation, when the communication apparatus 600 may correspond to a second network device in the method embodiments of uplink data transmission, the communication unit 620 is configured to receive a first message from the first network device, where the first message is used to indicate a PDCP sequence number of the packet that needs to be first header-decompressed. 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 from the PDCP sequence number of the data packet requiring the first header decompression, and send the one or more data packets after reordering to the first network device for header decompression.

In another possible implementation, the communication unit 620 is configured to receive a first message from the first network device, where the first message is used to indicate a PDCP sequence number of the packet requiring first header decompression. And a communication unit 620 is configured to receive PDCP sequence numbers 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 perform header decompression on a data packet corresponding to each of 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 to allow the first network device to perform header decompression on a data packet corresponding to each of the one or more PDCP sequence numbers.

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

In another possible implementation manner, the communication unit 620 receives a second PDCP sequence number from the first network device, where the second PDCP sequence number is preset as a PDCP sequence number of a first header-decompressed data packet required in a data packet received by the first network device from the terminal device. 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.

Referring to fig. 11, fig. 11 is a schematic diagram of a communication device 700 provided in the present application. The communication device 700 comprises a communication unit 710 and a processing unit 720.

A communication unit 710, configured to obtain a PDCP sequence number of a packet that needs to be first header-decompressed in a packet received from a terminal device;

a processing unit 720, configured to perform header decompression processing on the data packet received from the terminal device, starting from the PDCP sequence number of the data packet requiring first header decompression.

Alternatively, the communication unit 710 may be replaced by a receiving unit and/or a transmitting unit.

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

Optionally, the communication apparatus 700 may further include a storage unit for storing codes or data, and the processing unit 720 may call the codes or data in the storage unit, so that the communication apparatus 700 implements corresponding functions or steps.

In one implementation, the communication apparatus 700 may correspond exactly to the first network device (e.g., the target base station) in the method embodiment. Alternatively, the communication apparatus 700 is a first network device.

In such an implementation, the communication unit 710 shown in fig. 11 may be a transceiver. The transceiver has a function of transmitting and/or receiving. The transceiver may also be replaced by a receiver and/or a transmitter. The processing unit 720 may be a processor. The transceiver and the processor are used to perform the steps or processes performed by the first network device in the method embodiments.

For example, the communication unit 710 receives second indication information from the terminal device, where the second indication information is used to indicate a PDCP sequence number of a first header-decompressed data packet in 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 second indication information, where each second indication information is used to indicate a PDCP sequence number of a first header-decompressed data packet of the corresponding bearer.

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

For another example, the communication unit 710 receives a PDCP control PDU from the terminal device, where the PDCP control PDU carries the second indication information. Wherein the second indication information is used to indicate a PDCP sequence number of a first header-decompressed data packet of a 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 obtains the data packet with the preset RLC sequence number, the processing unit 720 analyzes the data packet with the preset RLC sequence number to obtain the PDCP sequence number of the data packet requiring the first header decompression.

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 header decompression required packet. And, when the communication unit 710 receives one or more data packets from the terminal device, transmits 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 on the one or more data packets according to the order after reordering, where the one or more data packets are reordered from the PDCP sequence number of the data packet requiring first header decompression.

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 header decompression required packet. And when the communication unit 710 receives one or more data packets from the terminal device, transmitting 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 a second network device, where the second message is used to indicate whether header decompression is allowed for a data packet corresponding to the one or more PDCP sequence numbers, and the second message is generated according to the first message and the one or more PDCP sequence numbers. And the processing unit 720 performs header decompression on the data packet indicated by the second message and allowed to be header-decompressed, starting from the PDCP sequence number of the data packet requiring the first header decompression, and does not perform header decompression on the data packet indicated by the second message and not allowed to be header-decompressed.

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

For another example, when the communication unit 710 receives the packet that needs to be decompressed by the first header, the communication unit 710 transmits the PDCP sequence number of the packet that needs to be decompressed by the first header to the second network device, and transmits the PDCP sequence numbers of other packets received from the terminal device to the second network device after transmitting the PDCP sequence number of the packet that needs to be decompressed by the first header. And the communication unit 710 receives the PDCP sequence numbers of the data packet requiring the first header decompression 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 to be decompressed by the first header and the other data packets according to the order after reordering.

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

In this implementation, the communication unit 710 shown in fig. 11 may be a communication interface. Alternatively, the communication interface may be an input-output interface or a transceiver circuit. The processing unit 720 may be a processing device. The functionality of the processing means may be partly or wholly implemented by software.

In one implementation, the functionality of the processing means may be implemented partly or wholly in software. In this implementation, the processing apparatus may include a memory and a processor, where the memory is used for storing the computer program, and the processor reads and executes the computer program stored in the memory to perform the processing internally implemented by the first network device in the embodiments. For example, the processing performed by processing unit 720 described above is performed.

In another implementation, the functionality of the processing means may be implemented partly or wholly in 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 for acquiring a PDCP sequence number of a data packet which needs first header decompression in the data packet received from the terminal equipment; the logic circuit is used for performing header decompression processing on the data packet received from the terminal equipment from the PDCP sequence number of the data packet needing first header decompression.

Referring to fig. 12, fig. 12 is a schematic structural diagram of a terminal device provided in the present application. As shown in fig. 12, the terminal device 800 includes a processor 801 and a transceiver 802.

Optionally, terminal device 800 further comprises a memory 803. The processor 801, the transceiver 802 and the memory 803 may communicate with each other via internal connection paths to transmit control signals and/or data signals.

The memory 803 is used for storing computer programs, among other things. The processor 801 is configured to execute the computer program stored in the memory 803, thereby implementing each function of the communication apparatus 500 in the above-described apparatus embodiment.

In particular, processor 801 may be used to perform the operations and/or processes described in the apparatus embodiments (e.g., fig. 9) as being performed by processing unit 520, while transceiver 802 is used to perform the operations and/or processes described as being performed by communication unit 510.

Alternatively, the memory 803 may be integrated into the processor 801 or separate from the processor 801.

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

Optionally, terminal apparatus 800 can also include a power supply 805 for providing power to various devices or circuits in the terminal apparatus.

In addition to this, in order to further improve the functions of the terminal apparatus, the terminal apparatus 800 may further include one or more of an input unit 806, an output unit 807, an audio circuit 808, a camera 809, a sensor 810, and the like. The audio circuit may further include a speaker 8082, a microphone 8084, etc., which are not described in detail.

Alternatively, 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.

Alternatively, 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.

Referring to fig. 13, fig. 13 is a schematic structural diagram of a network device provided in the present application. Network device 1000 may correspond to a first network device (e.g., a source base station) in various method embodiments.

As shown in fig. 13, the network device 1000 includes an antenna 1101, a radio frequency device 1102, and a baseband device 1103. An antenna 1101 is connected to the radio frequency device 1102. In the uplink direction, the rf device 1102 receives a signal from the terminal device through the antenna 1101, and sends the received signal to the baseband device 1103 for processing. In the downlink direction, the baseband apparatus 1103 generates a signal to be transmitted to the terminal device, and transmits the generated signal to the rf apparatus 1102. The rf device 1102 transmits the signal through an antenna 1101.

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

In addition, the baseband device 1103 may also 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 be specifically a memory, and the communication interface 11033 may be an input/output interface or a transceiver circuit.

Alternatively, 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 may be a storage unit on a different chip from the processing unit, that is, an off-chip storage unit. This is not a limitation of the present application.

In one implementation, when the communication apparatus 600 shown in fig. 10 and the second network device in the method embodiment completely correspond, the communication apparatus 600 may be implemented by the network device 1000 shown in fig. 13, or in other words, the first network device may be as shown in fig. 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.

Referring to fig. 14, fig. 14 is a schematic structural diagram of a network device provided in the present application. Network device 2000 may correspond to a first network device (e.g., a target base station) in various method embodiments.

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

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

The baseband apparatus 2103 may further comprise one or more memory 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 interact with the radio frequency device 2102. The storage unit 21032 may be specifically a memory, and the communication interface 21033 may be an input/output interface or a transceiver circuit.

Alternatively, 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 may be a storage unit on a different chip from the processing unit, that is, an off-chip storage unit. This is not a limitation of the present application.

In one implementation, when the communication apparatus 700 shown in fig. 11 and the first network device in the method embodiment fully correspond, 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, the application also provides a communication system, which comprises one or more terminal devices, one or more first network devices and one or more second network devices.

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

Also for example, the communication system includes one or more first network devices and one or more second network devices provided herein. Further, the communication system may also include one or more terminal devices.

The present application also provides a computer-readable storage medium having a computer program stored thereon, where the computer program, when executed by a computer, causes the computer to perform the operations and/or processes performed by the terminal device in any one of the method embodiments.

The present application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a computer, causes the computer to perform the operations and/or processes performed by the second network device in any of the method embodiments.

The present application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a computer, causes the computer to perform the operations and/or processes performed by the first network device in any of the method embodiments.

The present application also provides a computer program product comprising computer program code to, when run on a computer, cause the computer to perform the operations and/or processes performed by the terminal device in any of the method embodiments.

The present application further provides a computer program product comprising computer program code to, when run on a computer, cause the computer to perform the operations and/or processes performed by the second network device in any of the method embodiments.

The present application further provides a computer program product comprising computer program code to, when run on a computer, cause the computer to perform the operations and/or processes performed by the first network device in any of the method embodiments.

The present application further provides a chip comprising a processor. A memory for storing the computer program is provided separately from the chip, and a processor is configured to execute the computer program stored in the memory to perform the operations and/or processes performed by the terminal device in any one of the method embodiments.

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

The present application further provides a chip comprising a processor. A memory for storing the computer program is provided separately from the chip, and the processor is configured to execute the computer program stored in the memory to perform the operations and/or processes performed by the second network device in any of the method embodiments.

The present application further provides a chip comprising a processor. A memory for storing the computer program is provided separately from the chip, and the processor is configured to execute the computer program stored in the memory to perform the operations and/or processes performed by the first network device in any of the method embodiments.

The processor in the embodiments of the present application may be an integrated circuit chip having the capability of processing signals. In implementation, the steps of the above method embodiments may be performed by integrated logic circuits of hardware in a processor or instructions in the form of software. The processor may be a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic, or discrete hardware components. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in the embodiments of the present application may be directly implemented by a hardware encoding processor, or implemented by a combination of hardware and software modules in the encoding processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in a memory, and a processor reads information in the memory and completes the steps of the method in combination with hardware of the processor.

The memory in the embodiments of the present application may be either volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The non-volatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an electrically Erasable EPROM (EEPROM), or a flash memory. Volatile memory can be Random Access Memory (RAM), which acts as external cache memory. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), double data rate SDRAM, enhanced SDRAM, SLDRAM, Synchronous Link DRAM (SLDRAM), and Direct Rambus RAM (DRRAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware, depending on the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the elements can be selected according to actual needs to achieve the purpose of the embodiments of the present application.

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

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application.

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method for processing data packets, comprising:

the terminal equipment acquires a Packet Data Convergence Protocol (PDCP) sequence number of a data packet which needs to be subjected to first header decompression in the data packet received from the first network equipment;

and the terminal equipment performs header decompression processing on the data packet received from the first network equipment according to the PDCP sequence number of the data packet needing to be subjected to header decompression firstly.

2. The method of claim 1, wherein the obtaining, by the terminal device, the PDCP sequence number of the first header-decompressed data packet from the data packets received from the first network device comprises:

the terminal device receives first indication information from a second network device, wherein the first indication information is used for indicating the PDCP sequence number of the data packet needing first header decompression.

3. The method of claim 2, wherein the terminal device receives the first indication information from the second network device, and wherein the receiving comprises:

the terminal device receives a Radio Resource Control (RRC) reconfiguration message from the second network device, wherein the RRC reconfiguration message carries one or more pieces of first indication information, and each piece of first indication information is used for indicating a PDCP sequence number of a corresponding bearer data packet which needs to be subjected to header decompression; alternatively, the first and second electrodes may be,

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

4. The method of claim 1, wherein the obtaining, by the terminal device, the PDCP sequence number of the first header-decompressed data packet from the data packets received from the first network device comprises:

the terminal device obtains the PDCP sequence number of the first packet to be header-decompressed according to a first packet received from the first network device, where the RLC sequence number of the first packet is a preset RLC sequence number.

5. The method of claim 4, wherein the predetermined RLC sequence number is 0.

6. The method according to any of claims 1-5, wherein the performing, by the terminal device, header decompression processing on the data packet received from the first network device according to the PDCP sequence number of the first header-required data packet comprises:

and the terminal equipment reorders the data packets received from the first network equipment according to the PDCP sequence number of the data packet needing first header decompression, starting from the data packet corresponding to the PDCP sequence number of the data packet needing first header decompression, and performs header decompression on the data packets received from the first network equipment according to the order after reordering.

7. A method for processing data packets, comprising:

the second network equipment generates first indication information, wherein the first indication information is used for indicating a Packet Data Convergence Protocol (PDCP) sequence number of a data packet which needs to be subjected to header decompression in the data packet received by the terminal equipment from the first network equipment;

and the second network equipment sends the first indication information to the terminal equipment.

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

the second network equipment sends an RRC reconfiguration message to the terminal equipment, wherein the RRC reconfiguration message carries one or more pieces of first indication information, and each piece of first indication information is used for indicating a Packet Data Convergence Protocol (PDCP) sequence number of a corresponding carried data packet which needs to be decompressed by a first header; alternatively, the first and second electrodes may be,

and the second network equipment sends a Packet Data Convergence Protocol (PDCP) control Protocol Data Unit (PDU) to the terminal equipment, wherein the PDCP control PDU carries the first indication information, and the first indication information is used for indicating a PDCP sequence number of a data packet which needs to be subjected to first header decompression and is carried by a bearer corresponding to the PDCP control PDU.

9. A method for processing data packets, comprising:

the first network equipment acquires a PDCP sequence number of a data packet which needs to be subjected to header decompression by the first network equipment in the data packet received from the terminal equipment;

and the first network equipment performs header decompression processing on the data packet received from the terminal equipment from the data packet corresponding to the PDCP sequence number of the data packet needing first header decompression.

10. The method of claim 9, wherein the obtaining, by the first network device, the PDCP sequence number of the first header-decompressed data packet from the data packets received from the terminal device comprises:

and the first network equipment receives second indication information from the terminal equipment, wherein the second indication information is used for indicating the PDCP sequence number of a data packet which needs to be subjected to header decompression in the data packets sent by the terminal equipment.

11. The method of claim 10, wherein the first network device receives second indication information from a terminal device, comprising:

the first network device receives an RRC reconfiguration complete message from the terminal device, where the RRC reconfiguration complete message carries one or more second indication information, where each second indication information is used to indicate a PDCP sequence number of a first header-decompressed data packet of a corresponding bearer; alternatively, the first and second electrodes may be,

the first network device receives a PDCP status report from the terminal device, where the PDCP status report carries the second indication information, where the second indication information is used to indicate a PDCP sequence number of a first header-decompressed data packet of a bearer corresponding to the PDCP status report; alternatively, the first and second electrodes may be,

and the first network equipment receives a Packet Data Convergence Protocol (PDCP) control Protocol Data Unit (PDU) from the terminal equipment, wherein the PDCP control PDU carries the second indication information, and the second indication information is used for indicating a PDCP sequence number of a data packet which needs to be subjected to first header decompression and is carried by a bearer corresponding to the PDCP control PDU.

12. The method of claim 9, wherein the obtaining, by the first network device, the first header-decompressed data packet from the data packets received from the terminal device comprises:

the first network equipment acquires the PDCP serial number of the data packet needing first header decompression according to a second data packet received from the terminal equipment, wherein the Radio Link Control (RLC) serial number of the second data packet is a preset RLC serial number.

13. The method of claim 12, wherein the predetermined RLC sequence number is 0.

14. The method according to any one of claims 10-12, further comprising:

the first network equipment sends a first message to second network equipment, wherein the first message is used for indicating the PDCP sequence number of the data packet needing first header decompression;

and the first network device performs header decompression processing on the data packet received from the terminal device, starting from the data packet corresponding to the PDCP sequence number of the data packet requiring first header decompression, including:

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

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 according to the order after reordering, wherein the one or more data packets are reordered from the PDCP sequence number of the data packet requiring first header decompression.

15. The method according to any one of claims 10-12, further comprising:

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

the first network device receives a second message from the second network device, wherein the second message is used for indicating whether header decompression is allowed to be carried out on data packets corresponding to the one or more PDCP sequence numbers;

and the first network equipment performs header decompression on the data packet which is indicated by the second message and allowed to be subjected to header decompression, and does not perform header decompression on the data packet which is indicated by the second message and not allowed to be subjected to header decompression, starting from the data packet corresponding to the PDCP sequence number of the data packet needing first header decompression.

16. The method according to any of claims 9-13, wherein the first network device performs header decompression processing on the data packet received from the terminal device starting from the data packet corresponding to the PDCP sequence number of the first header-decompressed data packet, and comprising:

when the first network equipment receives the data packet needing to be decompressed by the first header, the first network equipment sends the data packet needing to be decompressed by the first header to the second network equipment, and sends other data packets received from the terminal equipment to the second network equipment after sending the data packet needing to be decompressed by the first header;

the first network device receives the data packet requiring first header decompression and the other data packets after reordering from the second network device;

and the first network equipment carries out header decompression processing on the data packet needing to be decompressed by the first header and the other data packets according to the sequence after reordering.

17. The method according to any of claims 9-13, wherein the first network device performs header decompression processing on the data packet received from the terminal device starting from the data packet corresponding to the PDCP sequence number of the first header-decompressed data packet, and comprising:

when the first network equipment receives the data packet needing to be decompressed by the first header, the first network equipment sends the PDCP sequence number of the data packet needing to be decompressed by the first header to the second network equipment, and sends the PDCP sequence number of one or more data packets received from the terminal equipment to the second network equipment after sending the data packet needing to be decompressed by the first header;

the first network device receiving a second message from the second network device, the second message being used to indicate whether the first network device is allowed to perform header decompression on a data packet corresponding to each of the one or more PDCP sequence numbers;

and the first network equipment carries out header decompression processing on the data packet needing to be decompressed by the first header and the one or more data packets according to the second message.

18. A method for processing data packets, comprising:

the second network equipment acquires a PDCP sequence number of a data packet which needs first header decompression in the data packet sent by the terminal equipment;

and the second network equipment assists the first network equipment to carry out header decompression processing on the data packet received from the terminal equipment according to the PDCP sequence number of the data packet needing to be subjected to header decompression firstly.

19. The method of claim 18, wherein the obtaining, by the second network device, the PDCP sequence number of the first header-decompressed data packet in the data packets sent by the terminal device comprises:

the second network equipment receives a first message from the first network equipment, wherein the first message is used for indicating the PDCP sequence number of the data packet needing first header decompression;

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 data packet requiring first header decompression, including:

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

the second network equipment reorders the one or more data packets received from the first network equipment according to the first message from the PDCP sequence number of the data packet needing first header decompression, and sends the one or more data packets after the reordering to the first network equipment for header decompression.

20. The method of claim 18, wherein the second network device assists the first network device in performing header decompression on the data packet received from the terminal device according to the PDCP sequence number of the data packet that needs to be first header decompressed, comprising:

receiving, by the second network device, one or more PDCP sequence numbers from the first network device;

the second network equipment judges whether to allow the first network equipment to carry out header decompression on the data packet corresponding to each of the one or more PDCP sequence numbers or not according to the first message;

and the second device sends a second message to the first network device, where the second message is used to indicate whether to allow the first network device to perform header decompression on a data packet corresponding to each of the one or more PDCP sequence numbers.

21. The method of claim 18, wherein the obtaining, by the second network device, the PDCP sequence number of the first header-decompressed data packet in the data packets sent by the terminal device comprises:

the second network equipment receives a data packet corresponding to the first PDCP sequence number from the first network equipment, and receives other data packets from the first network equipment after receiving the data packet corresponding to the first PDCP sequence number;

and the second network equipment reorders the data packet corresponding to the first PDCP sequence number and the other data packets from the data packet corresponding to the first PDCP sequence number, and sends the reordered data packet corresponding to the first PDCP sequence number and the other data packets to the first network equipment for header decompression.

22. The method of claim 18, wherein the obtaining, by the second network device, the PDCP sequence number of the first header-decompressed data packet in the data packets sent by the terminal device comprises:

the second network device receives a second PDCP sequence number from the first network device, where the second PDCP sequence number is preset as a PDCP sequence number of a first header-decompressed data packet required in the data packets received by the first network device from the terminal device;

and 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 data packet requiring the first header decompression, including:

and the second network equipment reorders the one or more data packets from the data packet corresponding to the second PDCP sequence number, and sends the reordered data packet corresponding to the second PDCP sequence number and the one or more data packets to the first network equipment for header decompression.

23. A method for processing data packets, comprising:

the terminal equipment generates second indication information, wherein the second indication information is used for indicating a PDCP sequence number of a data packet which needs to be decompressed by the first network equipment head in the data packet sent by the terminal equipment;

and the terminal equipment sends the second indication information to the first network equipment.

24. The method of claim 23, wherein the sending, by the terminal device, the second indication information 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 second indication information, where each second indication information is used to indicate a PDCP sequence number of a first header-decompressed data packet of the corresponding bearer; alternatively, the first and second electrodes may be,

the terminal device sends 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 a PDCP sequence number of a data packet that needs to be decompressed by a first header of a corresponding bearer; alternatively, the first and second electrodes may be,

and the terminal equipment sends a PDCP control PDU to the first network equipment, wherein the PDCP control PDU carries the second indication information, and the second indication information is used for indicating a PDCP sequence number of a data packet which needs first header decompression and is carried by the PDCP control PDU.

25. A communication device comprising means for implementing the method of any of claims 1-6, 23, 24.

26. A communication apparatus, characterized in that it comprises means for implementing the method according to any of claims 7, 8, 18-22.

27. A communication apparatus, characterized in that it comprises means for implementing the method according to any of claims 9-17.

28. A computer-readable medium, comprising a computer program which, when executed by a processor, causes the method of any of claims 1-24 to be performed.