# US 2024/0187919 A1 · Communication devices and methods for concatenating service data units

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2024/0187919 A1
- Document ID: US20240187919A1
- Status: Published application
- Kind: A1
- Application number: 17/796,633
- Filed: 2021-09-03
- Published: 2024-06-06
- Earliest claimed: 2021-09-03
- Assignees: Apple Inc.
- Applicants: Apple Inc.
- Inventors: Ralf Rossbach; Fangli Xu; Alexander Sirotkin; Bobby Jose; Dawei Zhang; Francois E. Deparis; Haijing Hu; Mohamed Mounir Mohamed Abdelrahman; Murali Narasimha; Murtaza A. Shikari; Naveen Kumar R. Palle Venkata; Pavan Nuggehalli; Ralf Itjeshorst; Sarma V. Vangala; Sethuraman Gurumoorthy; Vijay Venkataraman; Yuqin Chen; Zhibin Wu
- Web page: https://patentgrep.com/patent/US20240187919A1

## CPC

- H04W 28/04: Error control
- H04L 1/0064: {Concatenated codes}
- H04W 28/0268: {using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR] (negotiating SLA or negotiating QoS H04W28/24)}
- H04W 76/20: Manipulation of established connections
- H04W 80/02: Data link layer protocols
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

The present application relates to devices and components including apparatus, systems, and methods for concatenating in the packet data convergence protocol sublayer or the service data adaptation sublayer in wireless networks.

## Claims

### Claim at position 1

-25. (canceled)

### Claim 26

A method comprising:
identifying a plurality of packet data convergence protocol (PDCP) service data units (SDUs);
generating a PDCP packet data unit (PDU) to include the plurality of PDCP SDUs and a header with a concatenation field having a concatenation value to indicate that the PDCP PDU is concatenated; and
providing the PDCP PDU to a radio link control (RLC) sublayer for transmission.

### Claim 27 (depends on 26)

The method of claim 26, wherein the header further comprises:
a packet-number field with a packet-number value to indicate a number of PDCP SDUs in the PDCP PDU; and
a length field with a length value to indicate a length of each of the number PDCP SDUs.

### Claim 28 (depends on 26)

The method of claim 26, wherein the plurality of PDCP SDUs comprises a first set of one or more PDCP SDUs and a second set of one or more PDCP SDUs and the header further comprises:
a first packet-number field having a first packet number value to indicate a number of PDCP SDUs in the first set;
a first length field having a first length value to indicate a length of each PDCP SDU of the first set of one or more PDCP SDUs; and
a second length field having a second length value to indicate a length of each PDCP SDU of the second set of one or more PDCP SDUs.

### Claim 29 (depends on 26)

The method of claim 26, further comprising:
identifying a parameter that is preconfigured or signaled by a radio resource control (RRC) message that indicates a maximum number of PDCP SDUs that can be concatenated in one PDCP PDU; a maximum size of one PDCP PDU; a maximum size of a PDCP SDU that can be concatenated into one PDCP PDU; or an uplink or downlink direction in which concatenation of PDCP SDUs is permitted.

### Claim 30 (depends on 26)

The method of claim 26, further comprising:
transmitting or receiving an indication of a PDCP concatenation capability of a user equipment.

### Claim 31 (depends on 26)

The method of claim 26, further comprising:
identifying a plurality of service data adaptation (SDAP) PDUs, each SDAP PDU having a respective SDAP header and payload;
determining that the SDAP headers of the plurality of SDAP PDUs have a common quality of service flow identifier; and
generating, based on said determining, the plurality of PDCP SDUs to include one SDAP header and the payloads of the plurality of SDAP PDUs.

### Claim 32 (depends on 26)

The method of claim 26, further comprising:
identifying a plurality of service data adaptation (SDAP) PDUs, each SDAP PDU having a common header and a respective payload; and
generating, based on said identifying, the plurality of PDCP SDUs to include the common header and the payloads of the plurality of SDAP PDUs.

### Claim 33 (depends on 26)

The method of claim 26, wherein the concatenation value provides an identifier and the method further comprises:
accessing, based on the identifier, a lookup table or a number of predefined patterns to determine one or more concatenation parameters; and
generating the PDCP PDU based on the one or more concatenation parameters.

### Claim 34 (depends on 26)

The method of claim 26, further comprising:
receiving, in downlink control information or a media access control control element, an indication that PDCP concatenation is activated; and
generating the PDCP PDU based on the indication.

### Claim 35 (depends on 26)

The method of claim 26, wherein the PDCP PDU is a first PDCP PDU, the plurality of PDCP SDUs is a first plurality of PDCP SDUs, and the method further comprises:
identifying a second plurality of PDCP SDUs in a sequence, the second plurality of PDCP SDUs to include the first plurality of PDCP SDUs;
determining a first PDCP SDU includes a reflective quality of service (QoS) indication (RQI) or reflective QoS flow to data radio bearer mapping indication (RDI) bit that indicates an update to a quality of service parameter;
setting a second PDCP SDU that immediately precedes the first PDCP SDU in the sequence as a last PDCP SDU to be included in the first plurality of PDCP SDUs to be concatenated into the first PDCP PDU based on said determining; and
generating a second PDCP PDU to include the first PDCP SDU and at least one additional PDCP SDU of the second plurality of PDCP SDUs.

### Claim 36 (depends on 26)

The method of claim 26, wherein the PDCP PDU is to be transmitted over: a Uu interface between a user equipment and a base station; an F1 interface between a gNB distributed unit (DU) and a gNB central unit (CU); an E1 interface between a CU control plane and a CU data plane; an X2 interface between base stations, or an Xn interface between gNB CUs.

### Claim 37 (depends on 26)

The method of claim 26, wherein the method is performed by a source base station, the PDCP PDU is to be transmitted to a user equipment (UE), and the method further comprises:
determining the UE is being handed over to a target base station;
determining whether the target base station supports concatenation; and
forwarding the plurality of PDCP SDUs in the PDCP PDU or in a corresponding plurality of PDCP PDUs based on said determining whether the target base station supports concatenation.

### Claim 38 (depends on 26)

The method of claim 26, further comprising:
determining concatenation of the plurality of PDCP SDUs would not result in lower-layer segmentation; and
generating the PDCP PDU to include the plurality of PDCP SDUs based on said determining.

### Claim 39 (depends on 26)

The method of claim 26, further comprising:
generating a concatenated PDCP SDU to include the plurality of PDCP SDUs; and
performing ciphering and integrity protection on the concatenated PDCP SDU.

### Claim 40

One or more non-transitory, computer-readable media having instructions that, when executed by one or more processors, cause a device to:
identify a plurality of service data adaptation (SDAP) service data units (SDUs);
generate an SDAP PDU to include the plurality of SDAP SDUs and a header with a field having a value to indicate that the SDAP PDU is concatenated; and
provide the SDAP PDU to a packet data convergence protocol (PDCP) sublayer for transmission.

### Claim 41 (depends on 40)

The one or more non-transitory, computer-readable media of claim 40, wherein the instructions, when executed, further cause the device to:
determine the plurality of SDAP SDUs have a common quality of service flow identifier (QFI); and
generate the SDAP PDU to include the plurality of SDAP SDUs based on said determination that the plurality of SDAP SDUs have a common QFI.

### Claim 42 (depends on 40)

The one or more non-transitory, computer-readable media of claim 40, wherein the header further comprises:
a packet-number field having a packet number value to indicate a number of SDAP SDUs in the SDAP PDU; and
a length field with a length value to indicate a length of each of the number SDAP SDUs.

### Claim 43 (depends on 40)

The one or more non-transitory, computer-readable media of claim 40, wherein the instructions, when executed, further cause the device to:
generate the SDAP PDU for a first data radio bearer (DRB) based on a determination that the first DRB is configured with SDAP headers; and
generate a concatenated PDCP PDU for a second DRB based on a determination that the second DRB is configured without SDAP headers.

### Claim 44

An apparatus comprising:
a reception buffer; and
processing circuitry coupled with the reception buffer, the processing circuitry to:
receive a packet data convergence protocol (PDCP) packet data unit (PDU) from a radio link control (RLC) sublayer;
determine, based on a header of the PDCP PDU, that the PDCP PDU includes a virtual PDCP service data unit (SDU) with a plurality of PDCP SDUs; and
store, in the reception buffer, a plurality of the virtual PDCP SDUs, including the virtual PDCP SDU, in order based on a plurality of sequence numbers respectively associated with the plurality of virtual PDCP SDUs.

### Claim 45 (depends on 44)

The apparatus of claim 44, wherein the processing circuitry is further to:
perform deciphering and integrity verification on the virtual PDCP SDU.
