CN115996426A

CN115996426A - Method and user equipment for performing uplink data compression

Info

Publication number: CN115996426A
Application number: CN202211156611.6A
Authority: CN
Inventors: 张园园; 徐家俊
Original assignee: MediaTek Singapore Pte Ltd
Current assignee: MediaTek Singapore Pte Ltd
Priority date: 2021-10-19
Filing date: 2022-09-22
Publication date: 2023-04-21
Also published as: WO2023065114A1

Abstract

The invention provides a method for performing uplink data compression and user equipment, wherein the method of one embodiment comprises the following steps: receiving, by a PDCP entity of the user equipment, an uncompressed data packet for UL transmission over configured radio bearers in a new radio wireless network; generating a UDC compressed data packet for the configured radio bearer; and routing the UDC compressed data packets to one or more radio link control, RLC, entities of the user equipment. By utilizing the present invention, uplink data compression can be better performed.

Description

Method and user equipment for performing uplink data compression

Technical Field

The present invention relates to wireless communications, and more particularly to performing uplink data compression (data compression) in a New Radio (NR) wireless network.

Background

In recent years, the use of mobile data has grown exponentially. As mobile services have grown dramatically over the past few years, attempts have been made to find new communication technologies to further improve the end user experience and system performance of mobile networks. Traffic growth is driven mainly by explosive growth of the number of connected devices, which require more and more high quality content, which requires very high throughput rates.

Uplink data compression (uplink data compression, UDC) is a method of increasing uplink capacity by compressing Uplink (UL) data. For UDC, many compression algorithms can be applied. For example, two different UDC compression algorithms are described in RFC1951 DEFLATE and RFC1950 ZLIB. UDC uses dictionary-based compression methods. To date, UDC has been introduced in long term evolution (long term evolution, LTE), but has limited use. For example, the UDC configuration is not applicable to split Radio Bearers (RBs). Whereas NR networks currently do not support UDC. To further improve the UE experience in NR, a method is needed to integrate UDC into NR wide range of applications, such as supporting MRDC and split bearers. Considering that the flow in the NR protocol stack is different from LTE, the method of supporting UDC in NR will be different from LTE.

UDCs in NR networks need to be improved and enhanced.

Disclosure of Invention

An embodiment of the present invention provides a method of performing uplink data compression, including: receiving, by a PDCP entity of the user equipment, an uncompressed data packet for UL transmission over configured radio bearers in a new radio wireless network; generating a UDC compressed data packet for the configured radio bearer; and routing the UDC compressed data packets to one or more radio link control, RLC, entities of the user equipment.

Another embodiment of the present invention provides a method of performing uplink data compression, comprising: receiving, by a PDCP entity of the gNB, a data packet from a sending user equipment in a new radio network over a configured radio bearer from an uplink transmission, wherein the data packet is a UDC compressed data packet; reordering the received UDC compressed data packets; decompressing the UDC compressed data packet; and transmitting the decompressed data packets to an upper layer of the gNB.

Another embodiment of the present invention provides a user equipment, including: a transceiver for transceiving radio frequency signals in a new radio wireless network; a receiving module of the PDCP entity for receiving uncompressed data packets for UL transmission over configured radio bearers in the new radio wireless network; a UDC module of the PDCP entity for generating UDC compressed data packets for the configured radio bearers; and a routing module of the PDCP entity for routing the UDC compressed data packets to one or more radio link control RLC entities of the user equipment.

Another embodiment of the present invention provides a storage medium storing a program which, when executed, causes a user equipment to perform the steps of the method of performing uplink data compression of the present invention.

By utilizing the present invention, uplink data compression can be better performed.

Drawings

The drawings illustrate embodiments of the invention, wherein like numerals indicate like components.

Fig. 1 is a system diagram of an exemplary NR wireless communication network for enabling a UDC application according to an embodiment of the present invention.

Fig. 2 is a simplified block diagram of a transmitter and receiver for performing UDC in an NR wireless network according to an embodiment of the present invention.

Fig. 3 is an exemplary flow diagram of a UE performing UDC for normal or split bearers according to an embodiment of the present invention.

Fig. 4 is an exemplary flowchart of a BS performing UL data decompression for normal or split bearers according to an embodiment of the present invention.

Fig. 5 is an exemplary flow diagram of a UE performing UDC for DAPS bearer in accordance with an embodiment of the invention.

Fig. 6 is an exemplary flow chart of a BS performing UL data decompression for DAPS bearers in accordance with an embodiment of the invention.

Fig. 7 is an exemplary flow chart of performing UDC from a transmitter perspective according to an embodiment of the present invention.

Fig. 8 is an exemplary flow chart of performing UDC from the perspective of a receiver according to an embodiment of the present invention.

Detailed Description

Reference will now be made in detail to some embodiments of the present invention, examples of which are illustrated in the accompanying drawings.

Fig. 1 is a system diagram of an exemplary NR wireless communication network for enabling an (enable) UDC application according to an embodiment of the present invention. NR wireless network 100 includes one or more fixed infrastructure elements forming a network distributed over a geographic area. These base units may also be referred to as access points, access terminals, base stations, node bs, evolved node bs (eNode-bs), next generation node bs (gnbs), or other terminology used in the art. The network may be a homogeneous network or a heterogeneous network, and may be deployed using the same or different frequencies. The gNB 101 and the gNB 102 are base stations in the NR network, and service areas thereof may or may not overlap with each other. In an example, the User Equipment (UE) 105 or mobile station 105 is only in the service area of the gNB 101 and is connected to the gNB 101. UE 105 is connected only with the gNB 101. Similarly, UE 106 is only in the service area of the gNB 102 and is connected with the gNB 102. UE 106 is connected only with gNB 102. gNB 101 is connected to gNB 102 through Xn interface 109. UE 103 is in an overlapping service area of gNB 101 and gNB 102. In an embodiment, UE 103 is configured with dual protocol stacks that can be connected to both gNB 101 and gNB 102. In an example, one or more UEs in NR network 100 are configured with UDCs to increase UL capacity by compressing UL data. In one embodiment, the UDC uses a dictionary-based compression method. The UE transmits the UDC compressed data packets over one or more configured radio bearers. The configured radio bearers may be serving radio bearers (service radio bearer, SRB), data radio bearers (data radio bearer, DRB) or split bearers (split bearers). The gNB receives the UDC compressed data packet over one or more configured radio bearers.

In an embodiment, UEs in NR wireless network 100 support multiple radio access technology (radio access technology, RAT) dual connectivity (mutiple RAT dual connectivity, MRDC). In one example, the MRDC configuration 150 is configured with a primary cell group (primary cell group) and a secondary cell group (secondary cell group). The primary cell group and the secondary cell group may be configured with NR or LTE. The (primary, secondary) configurations of the exemplary MRDC 150 are (NR, NR), (NR, LTE) and (LTE, NR) supporting MRDC in the NR network. In one embodiment, to facilitate UDC processing between the transmitter and the receiver, the following design is considered: 1) Process flows for processing TX and RX compressed and uncompressed packets; 2) UDC is enabled for split bearers.

In one example, UDC is performed in an NR wireless network. On the transmitter side (e.g., UE 103), the UDC compressor places the processed uncompressed data into its compressed memory 139 and generates UDC compressed data packets 130. At the receiver side (e.g., BS/gNB 101), the UDC decompressor receives UDC compressed data packets 110 from the transmitter and stores the received UDC compressed data in its compressed memory 119. In an exemplary scenario, the UE 103 transmits uplink data, which is to be received by the BS/gNB 101. On the TX side, the application layer prepares data packets to be sent to BS/gNB 102 via a lower layer. In the packet data convergence protocol (packet data convergence protocol, PDCP) layer 131, data packets are compressed by UDCs, and the compressed UDC packets 130 are transmitted through the radio link control (radio link control, RLC) layer 132. The transmission mode may be RLC AM or RLC UM. The RLC layer packet is further transmitted through a medium access control (media access control, MAC) layer 133 and a Physical (PHY) layer 134. On the RX side, the BS 101 receives data packets through the PHY layer 114, the MAC layer 113, the RLC layer 112, and the PDCP layer 111. BS/gNB 101 decompresses compressed UDC data packet 110 and passes it to a higher application layer. In an embodiment, separate bearers are configured for the UE 103, UL data may be transmitted over two RLC bearers in the UL. Different protocol layers apply different error handling schemes to ensure proper data packet delivery. For example, at the PHY layer (e.g., PHY 114 and PHY 134), cyclic redundancy check (cyclic redundancy check, CRC) error detection and channel coding/decoding may be employed. At the MAC layer (e.g., MAC 113 and MAC 133), hybrid automatic repeat request (hybrid automatic repeat request, HARQ) forward error checking and ARQ error control may be employed. At the RLC layers (e.g., RLC 112 and RLC 132), ARQ may be employed, which provides error correction through retransmissions in the AM. At PDCP layers (e.g., PDCP 111 and PDCP 131), if UDC is configured, UDC layer error handling may be applied through a UDC checksum (checksum) to maintain compressed memory synchronization between TX and RX.

Fig. 2 is a simplified block diagram of a transmitter and receiver for performing UDC in an NR wireless network according to an embodiment of the present invention. A transmitter 201, such as a UE, has a Radio Frequency (RF) transceiver module 213 coupled to an antenna 219, which may receive RF signals from the antenna 219, convert them to baseband signals and transmit them to a processor 212. The RF transceiver 213 also converts the baseband signal received from the processor 212 into an RF signal and transmits to the antenna 219. The processor 212 processes the received baseband signals and invokes different functional modules to perform functional features in the UE/transmitter 201. Memory 211 stores program instructions and data 215 to control the operation of transmitter/UE 201. The program instructions and data 215, when executed by the processor 212, may enable the transmitter/UE 201 to perform embodiments of the present invention. Suitable processors may include, by way of example, a special purpose processor, a digital signal processor (digital signal processor, DSP), a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, a controller, a microcontroller, application specific integrated circuits (application specific integrated circuit, ASIC), field programmable gate array (field programmable gate array, FPGA) circuits, and other types of integrated circuits and/or state machines.

The transmitter/UE 201 also includes a plurality of functional modules and circuitry to perform different tasks according to embodiments of the invention. The functional modules and circuits may be implemented and configured in hardware, firmware, software, and any combination thereof. A processor associated with the software may be used to implement and configure the features of the transmitter/UE 201. In an embodiment, the functional modules and circuits 220 include an application or service data adaptation protocol (service data adaptation protocol, SDAP) module 221, a PDCP layer entity 222 for PDCP layer functions including ciphering/deciphering, header compression/decompression, routing and reordering, an RLC layer entity 251, a MAC layer entity 252 with HARQ, and a PHY layer entity 253 supporting CRC and channel coding/decoding. In an embodiment, the PDCP entity 222 includes a receiving module 226 for receiving uncompressed data packets for UL transmission over configured radio bearers in an NR wireless network; a UDC module 227 for generating compressed data packets for configured radio bearers; a routing module 228 for routing the UDC compressed data packets to one or more RLC entities of the UE.

In one example, the application/SDAP module 221 prepares data packets that are received by the PDCP 222 and compressed by the UDC entity 227. The compressed PDCP/UDC packets are then routed through a routing module 228 and transported through RLC bearers and then through the MAC layer and PHY layer. The memory 211 comprises a buffer 216 for storing uncompressed source packet flows, and a buffer 217 for storing UDC compressed packet flows. Further, the memory 221 includes a UDC compressed memory/buffer 218, which functions as a first-in first-out (first in first out, FIFO) buffer. The input data to the UDC compression memory/buffer 218 is an uncompressed packet stream for UDC checksum calculation. In one example, each UDC compressed packet is accompanied by a checksum. The receiver also maintains a UDC compressed memory/buffer for deriving the checksum. When configuring the UDC, the compressed memory is initially synchronized between the UE 201 and the receiver. In an embodiment, the UDC is configured for split bearers and the PDCP entity 222 is associated with two RLC bearers/

entities

251 and 231, two

MAC entities

232 and 252, and two

PHY entities

233 and 253.

Receiver 202, such as a gNB, has an RF transceiver module 263 coupled to antenna 269, which may receive RF signals from antenna 269, convert them to baseband signals, and send them to processor 262. The RF transceiver 263 also converts the baseband signal received from the processor 262 into an RF signal and transmits it to the antenna 269. Processor 262 processes the received baseband signals and invokes different functional modules to perform functional features in the gNB/receiver 202. Memory 261 stores program instructions and data 265 to control the operation of gNB/receiver 202. Program instructions and data 265, when executed by processor 262, enable the gNB/receiver 202 to execute an embodiment of the present invention. For example, suitable processors may include a special purpose processor, a DSP, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, a controller, a microcontroller, an ASIC, an FPGA circuit, and other types of integrated circuits and/or state machines.

The gNB/receiver 202 also includes a plurality of functional modules and circuitry to perform different tasks according to an embodiment of the present invention. The functional modules and circuits may be implemented and configured in hardware, firmware, software, and any combination thereof. A processor associated with the software may be used to implement and configure the features of the gNB/receiver 202. In an embodiment, the functional modules and circuits 270 include an application or SDAP module 271, a PDCP layer entity 272 for PDCP layer functions including ciphering/deciphering, header compression/decompression, routing and reordering, an RLC layer entity 291, a MAC layer entity 292 with HARQ, and a PHY layer entity 293 supporting CRC and channel coding/decoding. In one embodiment, the PDCP entity 272 includes a receiving module 278 for receiving data packets from UL transmissions over a configured radio bearer in an NR wireless network, where the data packets are UDC compressed data packets; a reordering module 277 for reordering received UDC compressed data packets; a UDC module 276 for decompressing UDC compressed data packets; and the transmission module is used for transmitting the decompressed data packet to an upper layer (upper layer) of the gNB.

In one example, PHY 293 receives the UDC compressed data packets and passes them to MAC 292 and RLC 291.PDCP 272 is received by a receiving module 278 and reordering is performed at a reordering module 277. The reordered data packets are then decompressed by the UDC module 276. The decompressed data packets are transmitted to the application/SDAP 271. The memory 261 includes a buffer 266 for storing a UDC compression source packet stream, and a buffer 267 for storing a UDC decompression packet stream. Furthermore, the memory 261 includes a UDC compressed memory/buffer 268, which serves as a FIFO buffer. The input data to the memory/buffer 268 is a decompressed packet stream for use in the UDC checksum calculation. In one example, each UDC compressed packet is accompanied by a checksum. The receiver also maintains a UDC compressed memory/buffer for deriving the checksum. When configuring the UDC, the compressed memory is initially synchronized between the gNB 202 and the sender. In an embodiment, the UDC is configured for split bearers and the PDCP entity 272 is associated with two RLC bearers/

entities

291 and 281, two

MAC entities

292 and 282, and two

PHY entities

293 and 283.

Fig. 3 is an exemplary flow diagram of a UE performing UDC for normal or split bearers according to an embodiment of the present invention. The normal transmitting PDCP entity 310 of the transmitter/UE 301 receives data from an upper layer of the transmitter/UE. In step 311, sequence numbering (sequence numbering, SN) is performed. The transmitting PDCP entity associates a COUNT value (COUNT) corresponding to tx_next with a PDCP service data unit (service data unit, SDU). In step 312, UL data compression is performed on PDCP SDUs using UDCs. If the received data packet is not associated with a PDCP SDU, the data packet is sent to an add PDCP header process at step 330, otherwise, ciphering and security functions are performed before the addition of the PDCP header process at step 320. At step 314, integrity protection is performed. In step 315, encryption is performed. In step 316, TX NEXT is increased by 1 by adding a PDCP header with the PDCP sequence number of the PDCP data PDU. In step 317, the UDC compressed data is submitted to the lower layer. When configuring the split bearer, the transmitter/UE routes the PDCP data PDU to the appropriate RLC entity. In an example, the UE receives a UDC enable indicator from an NR wireless network (e.g., a gNB) to enable UDC for configured split bearers. In one embodiment, the UDC is performed prior to routing.

Fig. 4 is an exemplary flowchart of a BS performing UL data decompression for normal or split bearers according to an embodiment of the present invention. The normal receiving PDCP entity 410 of the receiver/gNB 401 receives data from the lower layers of the receiver/gNB. Subsequently, the receiving PDCP entity performs reordering of the stored PDCP SDUs. In step 416, the normal receiving PDCP entity 410 receives PDCP data PDUs from the lower layer, determines COUNT values of the received PDCP data PDUs, and removes PDCP headers. If the received data packet is not associated with a pdc sdu, the data packet is sent to the header decompression unit UDC 411 in step 430, otherwise decryption and security functions are performed before header decompression in step 420. In step 415, the normal receiving PDCP entity 410 performs decryption using a decryption key associated with the source cell. In step 414, the normal receiving PDCP entity 410 performs integrity verification using the source security key. In step 413, the receiver/gNB performs reordering of the stored PDCP SDUs. In step 411, UL data decompression is performed when the PDCP SDU is delivered to an upper layer. The data is transferred sequentially to the application layer of the receiver/gNB 401 by repeated detection. In an embodiment, the reordering is performed before the UDC.

Fig. 5 is an exemplary flow diagram of a UE performing UDC for dual active protocol stack (dual active protocol stack, DAPS) bearers in accordance with an embodiment of the invention. For the DAPS bearer, the PDCP entity is configured with two sets of UDC protocols. When an upper layer requests uplink data handover (to a target cell), a transmitting PDCP entity performs UDC of PDCP SDUs using UDC configuration of the target cell and delivers the generated PDCP data PDUs to the target cell. The DAPS transmitting PDCP entity 500 of the transmitter/UE 501 receives data from an upper layer of the transmitter/UE. In step 510, a sequence number SN is performed. In

steps

521 and 522, UDC is performed on the first data packet and the second data packet, respectively. In one embodiment, the first data packet is a source data packet and the second data packet is a destination data packet. If the received data packet is not associated with a PDCP SDU, the first and second data packets are sent to an add PDCP header process at

steps

582 and 592, respectively, otherwise ciphering and security functions are performed before adding the PDCP header at

steps

581 and 591. At step 531, integrity protection is performed on the first/source data packet. At step 532, integrity protection is performed on the second/target data packet. In step 551, encryption is performed on the first/source data packet. At step 552, encryption is performed on the second/target data packet. In step 560, a PDCP header is added. At step 570, routing is performed.

Fig. 6 is an exemplary flow chart of a BS performing UL data decompression for DAPS bearers in accordance with an embodiment of the invention. For the DAPS bearer, the PDCP entity is configured with two sets of UDC protocols. The receiving PDCP entity performs PDCP reordering prior to UDC decompression. When the upper layer requests uplink data handover, the receiving PDCP entity performs UDC decompression on the PDCP SDU using the UDC configuration of the target cell and delivers the generated PDCP SDU to the upper layer.

The DAPS receiving PDCP entity 600 of the receiver/gNB 601 receives data packets from a lower layer of the UE. The data packets are from a first cell and a second cell. In an embodiment, the first cell is a source cell and the second cell is a target cell. In step 610, the receiving PDCP entity of the receiver/gNB removes the PDCP header. If the received data packet is not associated with a PDCP SDU, then at steps 682 and 692, first and second data packets are sent to the

UDCs

651 and 652, respectively. Otherwise, in steps 681 and 691, decryption and security functions are performed before a/source UDC of the first/source data packet or a second/target UDC of the second/target data packet. At step 621, decryption is performed on the first/source data packet using a source decryption key associated with the first/source cell. At step 622, decryption is performed on the second/target data packet using a second/target decryption key associated with the second/target cell. In step 631, an integrity verification is performed on the first/source data packet using the first/source security key. At step 632, integrity verification is performed on the second/target data packet using the second/target security key. At step 640, reordering is performed and duplicate packets are discarded. In step 651, UDC decompression is performed on the first/source packet. At step 652, UDC decompression is performed on the second/target packet. The data is transferred sequentially to the application layer of the receiver/gNB 601 by repetition detection.

Fig. 7 is an exemplary flow chart of performing UDC from a transmitter perspective according to an embodiment of the present invention. In step 701, the ue receives an uncompressed data packet through a PDCP entity for UL transmission over configured radio bearers in an NR wireless network. In step 702, the ue generates a UDC compressed data packet for a configured radio bearer. The UE then routes the UDC compressed data packet to one or more RLC entities of the UE in step 703.

Fig. 8 is an exemplary flow chart of performing UDC from the perspective of a receiver according to an embodiment of the present invention. In step 801, the gNB receives a data packet from a transmitting UE over a configured radio bearer in an NR wireless network over a PDCP entity from a UL transmission, wherein the data packet is a UDC compressed data packet. In step 802, the gNB reorders the received UDC compressed data packets. In step 803, the gNB decompresses the UDC compressed data packet. In step 804, the gNB transmits the decompressed data packets to an upper layer of the gNB.

In one embodiment, a storage medium (e.g., a computer-readable storage medium) stores a program that, when executed, causes a UE to perform embodiments of the present invention.

Although the invention has been described in connection with specific embodiments for purposes of illustration, the invention is not limited thereto. Accordingly, various modifications, adaptations, and combinations of the various features of the described embodiments can be practiced without departing from the scope of the invention as set forth in the claims.

Claims

1. A method of performing uplink data compression, comprising:

receiving, by a packet data convergence protocol PDCP entity of the user equipment, an uncompressed data packet for uplink UL transmission over the configured radio bearer in the new radio wireless network;

generating an uplink data compression, UDC, compressed data packet for the configured radio bearer; and

the UDC compressed data packets are routed to one or more radio link control, RLC, entities of the user equipment.

2. The method of performing uplink data compression according to claim 1, wherein the configured radio bearer is a serving radio bearer, a data radio bearer, or a separate bearer.

3. The method of performing uplink data compression according to claim 1, wherein the user equipment is configured with a multi-radio access technology dual connection, wherein a primary cell group and a secondary cell group are configured, and the PDCP entity of the user equipment performs UDC data compression for the multi-radio access technology dual connection prior to routing.

4. The method of performing uplink data compression of claim 1, in which the configured radio bearer is a dual active protocol stack, DAPS, bearer.

5. The method of performing uplink data compression of claim 4, wherein two sets of UDC protocols are created, and wherein each set of UDC protocols is associated with a respective RLC entity configured for the DAPS.

6. The method of performing uplink data compression according to claim 5, further comprising:

receiving a request from an upper layer of the user equipment to switch uplink data to a target cell; and

the UDC is performed using a UDC configuration corresponding to the target cell.

7. The method of performing uplink data compression according to claim 1, wherein the configured radio bearers are separate bearers, the method of performing uplink data compression further comprising:

a UDC enable indicator is received from the new radio wireless network to enable UDC for the configured split bearer.

8. A method of performing uplink data compression, comprising:

receiving, by a packet data convergence protocol PDCP entity of the gNB, a data packet from a sending user equipment in a new radio wireless network over a configured radio bearer from an uplink transmission, wherein the data packet is an uplink data compression, UDC, compressed data packet;

reordering the received UDC compressed data packets;

decompressing the UDC compressed data packet; and

the decompressed data packets are communicated to an upper layer of the gNB.

9. The method of performing uplink data compression according to claim 8, wherein the configured radio bearer is a serving radio bearer, a data radio bearer, or a separate bearer.

10. The method of performing uplink data compression according to claim 8, further comprising:

configuring a primary cell group and a secondary cell group for the sending user equipment; and

the PDCP entity of the gNB performs reordering prior to UDC data decompression.

11. The method of performing uplink data compression of claim 8, in which the configured radio bearer is a dual active protocol stack, DAPS, bearer.

12. The method of performing uplink data compression of claim 11, wherein two sets of UDC protocols are created, and wherein each set of UDC protocols is associated with a respective RLC entity configured for the DAPS.

13. The method of performing uplink data compression according to claim 8, wherein the configured radio bearers are separate bearers, the method of performing uplink data compression further comprising:

a UDC enable indicator is sent to the sending user equipment to enable UDC for the configured split bearer.

14. A user equipment, comprising:

a transceiver for transceiving radio frequency signals in a new radio wireless network;

a receiving module of a packet data convergence protocol PDCP entity for receiving uncompressed data packets for uplink UL transmission over configured radio bearers in the new radio wireless network;

an uplink data compression, UDC, module of the PDCP entity for generating UDC compressed data packets for the configured radio bearers; and

a routing module of the PDCP entity for routing the UDC compressed data packets to one or more radio link control RLC entities of the user equipment.

15. The user equipment of claim 14, wherein the configured radio bearer is a serving radio bearer, a data radio bearer, or a split bearer.

16. The user equipment of claim 14, wherein the user equipment is configured with a multi-radio access technology dual connection, wherein a primary cell group and a secondary cell group are configured, and wherein the PDCP entity of the user equipment performs UDC data compression for the multi-radio access technology dual connection prior to routing.

17. The user equipment of claim 14, wherein the configured radio bearer is a dual active protocol stack, DAPS, bearer.

18. The user device of claim 17, wherein two sets of UDC protocols are created, and wherein each set of UDC protocols is associated with a respective RLC entity configured for the DAPS.

19. The user equipment according to claim 18, wherein the user equipment receives a request from an upper layer of the user equipment to handover uplink data to a target cell; and performing UDC using the UDC configuration corresponding to the target cell.

20. The user equipment of claim 14, wherein the configured radio bearer is a split bearer, the user equipment further receiving a UDC enable indicator from the new radio wireless network to enable UDC for the configured split bearer.

21. A storage medium storing a program which, when executed, causes a user equipment to perform the steps of the method of performing uplink data compression of any of claims 1-7.