IP Library › Granted Patent US 12,538,170
Granted Patent B2
US 12,538,170 · App. 18/247,123 · Granted Jan 27, 2026

PDU rate reduction in mobile communications

Inventor: Jarkko Eskelinen (Oulu, FI)
Assignee: MEDIATEK SINGAPORE PTE. LTD.
H04W28/06H04L1/1854H04L1/1887H04W28/0268H04W80/02
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,538,170
App. No.
18/247,123
Granted
Jan 27, 2026
Kind
B2
Abstract

Various solutions for protocol data unit (PDU) rate reduction in mobile communications are described. A processor of an apparatus implementable in a user equipment (UE) generates a Packet Data Convergence Protocol (PDCP) data PDU containing a plurality of service data units (SDUs). The apparatus then transfers the PDCP data PDU to a receiver of the apparatus.

Claims (32)

1 . A method, comprising:

generating a Packet Data Convergence Protocol (PDCP) data protocol data unit (PDU) containing a plurality of service data units (SDUs); and

transferring the PDCP data PDU to a receiver;

wherein the generating of the PDCP data PDU comprises concatenating the plurality of SDUs in generating the PDCP data PDU;

wherein the concatenating of the plurality of SDUs comprises selectively concatenating one or more flows of SDUs in generating the PDCP data PDU such that a first flow of SDUs associated with a first quality-of-service (QOS) identifier (ID) is concatenated and a second flow of SDUs associated with a second QoS ID is not concatenated,

wherein the generating of the PDCP data PDU comprises generating the PDCP data PDU using a PDCP data PDU format which has a multi-PDU (mPDU) container field containing a plurality of plain mPDUs from one or more data flows.

2 . The method of claim 1 , wherein the plurality of SDUs comprise a plurality of consecutive upper-layer SDUs related to a same Service Data Adaptation Protocol (SDAP) data flow.

3 . The method of claim 1 , wherein the first flow is associated with a non-time-critical traffic and the second flow is associated with a real-time traffic or a time-critical traffic.

4 . The method of claim 1 , wherein a number of the plurality of SDUs that are concatenated is based on available SDUs in a PDCP buffer at a time of the concatenating.

5 . The method of claim 1 , wherein a number of the plurality of SDUs that are concatenated is based on either or both of:

an amount of data being concatenated based on a counter, and

an amount of time elapsed from a previous concatenation based on a timer.

6 . The method of claim 1 , wherein a predetermined bit in a header of the PDCP data PDU is set to indicate the PDCP data PDU format as having the mPDU container field that contains the plurality of plain mPDUs.

7 . The method of claim 1 , wherein the PDCP data PDU format is agreed with the network by signaling using a PDCP control PDU.

8 . The method of claim 1 , wherein the transferring of the PDCP data PDU comprises dynamically indicating the PDCP data PDU format using a header in a data field of the PDCP data PDU.

9 . The method of claim 1 , wherein the plain mPDUs contain the plurality of SDUs associated with a PDU session.

10 . The method of claim 1 , wherein the generating of the PDCP data PDU comprises generating the PDCP data PDU using a PDCP data PDU format which has a plain mPDU field configured to contain the plurality of SDUs from an Internet Protocol (IP) flow or a Service Data Adaptation Protocol (SDAP) data flow.

11 . The method of claim 10 , wherein a predetermined bit in a header of the PDCP data PDU is set to indicate the PDCP data PDU format as having the plain mPDU field that contains the plurality of SDUs.

12 . The method of claim 10 , wherein the PDCP data PDU format is agreed with the network by signaling using a PDCP control PDU.

13 . The method of claim 10 , wherein the transferring of the PDCP data PDU comprises dynamically indicating the PDCP data PDU format using a header in a data field of the PDCP data PDU.

14 . The method of claim 10 , wherein a header in the plain mPDU field is set to indicate the PDCP data PDU format as having the plain mPDU field that contains the plurality of SDUs.

15 . The method of claim 10 , wherein the plain mPDU field contains a Service Data Adaptation Protocol (SDAP) SDU associated with a PDU session.

16 . An apparatus implementable in a user equipment (UE), comprising:

a transceiver configured to wirelessly communicate with a network; and

a processor coupled to the transceiver and configured to perform operations comprising:

generating a Packet Data Convergence Protocol (PDCP) data protocol data unit (PDU) containing a plurality of service data units (SDUs); and

transferring the PDCP data PDU to a receiver,

wherein, in generating the PDCP data PDU, the processor is configured to perform either:

concatenating the plurality of SDUs in generating the PDCP data PDU; or

generating the PDCP data PDU using a PDCP data PDU format which has a multi-PDU (mPDU) container field or a plain mPDU field configured to contain the plurality of SDUs;

wherein, in concatenating the plurality of SDUs, the processor selectively concatenates one or more flows of SDUs in generating the PDCP data PDU such that a first flow of SDUs associated with a first quality-of-service (QOS) identifier (ID) is concatenated and a second flow of SDUs associated with a second QoS ID is not concatenated,

wherein the generating of the PDCP data PDU comprises generating the PDCP data PDU using a PDCP data PDU format which has a multi-PDU (mPDU) container field containing a plurality of plain mPDUs from one or more data flows.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 29, 2023
From: ESKELINEN, JARKKO
To: MEDIATEK SINGAPORE PTE. LTD.
Reel/Frame 063143/0567 →
Continuity (2)
Provisional Application 63087937 · Oct 6, 2020
Related Publication 20230413108A1 · Dec 21, 2023
References Cited (43)
US 9264940B2 · Liu et al. · 2016 [cited by applicant]
US 10652147B2 · Makineni et al. · 2020 [cited by applicant]
US 10869224B2 · Zhao et al. · 2020 [cited by applicant]
US 11606717B2 · Joseph · 2023 [cited by applicant]
US 20100189059A1 · Yang · 2010 [cited by applicant]
US 20160381598A1 · Chan · 2016 [cited by examiner]
US 20170223578A1 · Hong · 2017 [cited by examiner]
US 20170311362A1 · Hong · 2017 [cited by examiner]
US 20180077605A1 · Maheshwari · 2018 [cited by examiner]
US 20180124642A1 · Phuyal · 2018 [cited by examiner]
US 20180213461A1 · Grayson · 2018 [cited by examiner]
US 20180368021A1 · Jung · 2018 [cited by applicant]
US 20190149638A1 · Desai et al. · 2019 [cited by applicant]
US 20190174449A1 · Shan · 2019 [cited by examiner]
US 20190280826A1 · Yi · 2019 [cited by applicant]
US 20190306884A1 · Palat · 2019 [cited by examiner]
US 20190313271A1 · Yiu · 2019 [cited by examiner]
US 20200044792A1 · Vaidya · 2020 [cited by applicant]
US 20200077470A1 · Xiong et al. · 2020 [cited by applicant]
US 20200275311A1 · Zhao · 2020 [cited by applicant]
US 20210006376A1 · Cirik · 2021 [cited by applicant]
US 20210227579A1 · Lee · 2021 [cited by applicant]
US 20210250808A1 · Mitra · 2021 [cited by applicant]
US 20210282050A1 · Adjakple · 2021 [cited by applicant]
US 20220225163A1 · Sharma · 2022 [cited by applicant]
US 20220225428A1 · Xiong · 2022 [cited by examiner]
US 20220286929A1 · Park · 2022 [cited by applicant]
US 20220338227A1 · Cirik · 2022 [cited by applicant]
US 20230070783A1 · Hui · 2023 [cited by applicant]
US 20230362883A1 · Park · 2023 [cited by applicant]
CN 1964362A · 2007 [cited by applicant]
CN 102300256A · 2011 [cited by applicant]
CN 102427446A · 2012 [cited by applicant]
CN 104812006A · 2015 [cited by applicant]
CN 106255153A · 2016 [cited by applicant]
CN 108696900A · 2018 [cited by applicant]
CN 110622451A · 2019 [cited by applicant]
CN 110945909A · 2020 [cited by applicant]
WO 2019193154A1 · 2019 [cited by applicant]
International Search Report and Written Opinion dated Dec. 30, 2021, issued in application No. PCT/CN2021/122212. [cited by applicant]
Qualcomm Incorporated; “Further details of RLC protocol without concatenation;” 3GPP TSG-RAN WG2 Meeting #96 R2-168603; Nov. 2016; pp. 1-3. [cited by applicant]
International Search Report and Written Opinion dated Jan. 6, 2022, issued in application No. PCT/CN2021/122562. [cited by applicant]
Notice of Allowance dated Nov. 13, 2025, issued in application No. U.S. Appl. No. 18/247,319. [cited by applicant]