IP Library Granted Patent US 12,255,829
Granted Patent B2
US 12,255,829 · App. 18/516,268 · Granted Mar 18, 2025

Data unit processing

Inventors: SungDuck Chun (Fairfax, VA); Kyungmin Park (Vienna, VA); Esmael Hejazi Dinan (McLean, VA); Peyman Talebi Fard (Vienna, VA); Weihua Qiao (Herndon, VA)
Assignee: Ofinno, LLC
H04L47/32H04L47/33H04W28/06H04W28/10H04W76/18H04W28/04
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,255,829
App. No.
18/516,268
Granted
Mar 18, 2025
Kind
B2
Abstract

A PDCP layer of a first transmitting device determines a transmission failure of at least one PDCP SDU, wherein a plurality of PDCP SDUs, comprising a data unit of a data flow, comprise the at least one PDCP SDU. The PDCP layer of the first transmitting device discards, based on the determining, the plurality of PDCP SDUs.

Claims (38)

1. A method comprising:

receiving, by a packet data convergence protocol (PDCP) layer of a first transmitting device from a radio resource control (RRC) layer of the first transmitting device, a configuration information configuring the PDCP layer of the first transmitting device to send a PDCP report indicating service data unit (SDU) discard by the PDCP layer;

determining, by the PDCP layer of the first transmitting device, a transmission failure of at least one PDCP service data unit (SDU), wherein a plurality of PDCP SDUs, comprising a data unit (DU) of a data flow, comprise the at least one PDCP SDU;

discarding, by the PDCP layer of the first transmitting device and based on the determining, the plurality of PDCP SDUs; and

sending, by the PDCP layer of the first transmitting device and based on the configuration information configuring the PDCP layer to send the PDCP report, a first PDCP report indicating, to at least a PDCP layer of a second device, that the plurality of PDCP SDUs, comprising the DU, are discarded.

2. The method of claim 1 , further comprising transmitting, by the first transmitting device to the second device, the plurality of packets associated with the data unit of the data flow.

3. The method of claim 1 , further comprising identifying, by the PDCP layer of the first transmitting device, the plurality of PDCP SDUs.

4. The method of claim 1 , wherein the PDCP layer of the first transmitting device determines the transmission failure based on expiration of a time duration associated with the at least PDCP SDU.

5. The method of claim 4 , wherein the PDCP layer of the first transmitting device:

starts the time duration associated with the at least one PDCP SDU when the PDCP SDU is received; and

stops the time duration associated with the at least one PDCP SDU when the first transmitting device receives an indication that the at least one PDCP SDU is received by the second device.

6. The method of claim 1 , wherein the PDCP report is sent via a PDCP control protocol data unit (PDU).

7. The method of claim 6 , wherein the PDCP control PDU comprises information of one or more sequence numbers of the plurality of PDCP SDUs comprising the DU.

8. A first transmitting device comprising one or more processors and memory storing instructions that, when executed by the one or more processors, cause the first transmitting device to:

receive, by a packet data convergence protocol (PDCP) layer of the first transmitting device from a radio resource control (RRC) layer of the first transmitting device, a configuration information configuring the PDCP layer of the first transmitting device to send of a PDCP report indicating service data unit (SDU) discard by the PDCP layer;

determine, by the PDCP layer of the first transmitting device, a transmission failure of at least one PDCP service data unit (SDU), wherein a plurality of PDCP SDUs, comprising a data unit (DU) of a data flow, comprise the at least one PDCP SDU;

discard, by the PDCP layer of the first transmitting device and based on the determining, the plurality of PDCP SDUs; and

send, by the PDCP layer of the first transmitting device and based on the configuration information configuring the PDCP layer to send the PDCP report, a first PDCP report indicating, to at least a PDCP layer of a second device, that the plurality of PDCP SDUs, comprising the DU are discarded.

9. The first transmitting device of claim 8 , wherein the instructions further cause the first transmitting device to transmit, to the second device, the plurality of packets associated with the data unit of the data flow.

10. The first transmitting device of claim 8 , wherein the instructions further cause the PDCP layer of the first transmitting device to identify the plurality of PDCP SDUs.

11. The first transmitting device of claim 8 , wherein the PDCP report is sent via a PDCP control protocol data unit (PDU) comprising information of one or more sequence numbers of the plurality of PDCP SDUs comprising the DU.

12. The first transmitting device of claim 8 , wherein the PDCP layer of the first transmitting device determines the transmission failure based on expiration of a time duration associated with the at least PDCP SDU.

13. The first transmitting device of claim 12 , wherein the PDCP layer of the first transmitting device:

starts the time duration associated with the at least one PDCP SDU when the PDCP SDU is received; and

stops the time duration associated with the at least one PDCP SDU when the first transmitting device receives an indication that the at least one PDCP SDU is received by the second device.

14. The first transmitting device of claim 8 , wherein the instructions further cause the first transmitting device to send an indication that the plurality of PDCU SDUs is discarded via a packet data convergence protocol (PDCP) status report.

15. A non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause a first transmitting device to:

receive, by a packet data convergence protocol (PDCP) layer of the first transmitting device from a radio resource control (RRC) layer of the first transmitting device, a configuration information configuring the PDCP layer of the first transmitting device to send a PDCP report indicating service data unit (SDU) discard by the PDCP layer;

determine, by the PDCP layer of the first transmitting device, a transmission failure of at least one PDCP service data unit (SDU), wherein a plurality of PDCP SDUs, comprising a data unit (DU) of a data flow, comprise the at least one PDCP SDU;

discard, by the PDCP layer of the first transmitting device and based on the determining, the plurality of PDCP SDUs; and

send, by the PDCP layer of the first transmitting device and based on the configuration information configuring the PDCP layer to send the PDCP report, a first PDCP report indicating, to at least a PDCP layer of a second device, that the plurality of PDCP SDUs, comprising the DU are discarded.

16. The computer-readable medium of claim 15 , wherein the instructions further cause the first transmitting device to transmit, to the second device, the plurality of packets associated with the data unit of the data flow.

17. The computer-readable medium of claim 15 , wherein the instructions further cause the PDCP layer of the first transmitting device to identify the plurality of PDCP SDUs.

18. The computer-readable medium of claim 15 , wherein the PDCP report is sent via a PDCP control protocol data unit (PDU) comprising information of one or more sequence numbers of the plurality of PDCP SDUs comprising the DU.

19. The computer-readable medium of claim 15 , wherein the PDCP layer of the first transmitting device determines the transmission failure based on expiration of a time duration associated with the at least PDCP SDU.

20. The computer-readable medium of claim 19 , wherein the PDCP layer of the first transmitting device:

starts the time duration associated with the at least one PDCP SDU when the PDCP SDU is received; and

stops the time duration associated with the at least one PDCP SDU when the first transmitting device receives an indication that the at least one PDCP SDU is received by the second device.

Assignments (3)
CHANGE OF NAME Recorded Feb 26, 2024
From: OFINNO TECHNOLOGIES, LLC
To: OFINNO, LLC
Reel/Frame 066559/0352 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 27, 2023
From: CHUN, SUNGDUCK; PARK, KYUNGMIN; DINAN, ESMAEL HEJAZI; TALEBI FARD, PEYMAN
To: OFINNO, LLC
Reel/Frame 065962/0354 →
EMPLOYMENT AGREEMENT Recorded Dec 27, 2023
From: QIAO, WEIHUA
To: OFINNO TECHNOLOGIES, LLC
Reel/Frame 066130/0370 →
Continuity (3)
Continuation PCTUS2023011252 · Jan 20, 2023
Provisional Application 63301541 · Jan 21, 2022
Related Publication 20240089795A1 · Mar 14, 2024
References Cited (60)
US 8259732B2 · Torsner · 2012 [cited by applicant]
US 8855047B2 · Sammour et al. · 2014 [cited by applicant]
US 11533136B2 · Dudda · 2022 [cited by applicant]
US 20110211591A1 · Traub et al. · 2011 [cited by applicant]
US 20140281707A1 · Su et al. · 2014 [cited by applicant]
US 20150215218A1 · Kanamarlapudi et al. · 2015 [cited by applicant]
US 20160286426A1 · Chun et al. · 2016 [cited by applicant]
US 20190053326A1 · Lee et al. · 2019 [cited by applicant]
US 20190394675A1 · Baek et al. · 2019 [cited by applicant]
US 20210084121A1 · Park · 2021 [cited by examiner]
US 20230179533A1 · Basu Mallick · 2023 [cited by examiner]
US 20240007410A1 · Tano · 2024 [cited by examiner]
EP 1161809A1 · 2001 [cited by applicant]
WO 0056002A1 · 2000 [cited by applicant]
WO 2019158059A1 · 2019 [cited by applicant]
WO 2022075912A1 · 2022 [cited by applicant]
WO WO2023130453A1 · 2023 [cited by examiner]
3GPP TS 23.501 V17.2.0 (Sep. 2021); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System architecture for the 5G System (5GS); Stage 2; (Release … [cited by applicant]
3GPP TS 23.502 V17.2.1 (Sep. 2021); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System (5GS); Stage 2; (Release 17). [cited by applicant]
3GPP TR 26.928 V16.1.0 (Dec. 2020); Technical Report; 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Extended Reality (XR) in 5G; (Release 16). [cited by applicant]
3GPP TS 29.060 V16.0.0 (Mar. 2020); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (G… [cited by applicant]
3GPP TS 29.122 V17.3.0 (Sep. 2021); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; T8 reference point for Northbound APIs; (Release 17). [cited by applicant]
3GPP TS 29.212 V17.1.0 (Sep. 2021); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Policy and Charging Control (PCC); Reference points (Release 17). [cited by applicant]
3GPP TS 29.281 V16.2.0 (Mar. 2021); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; General Packet Radio System (GPRS) Tunnelling Protocol User Plan… [cited by applicant]
3GPP TS 29.522 V17.3.0 (Sep. 2021); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Network Exposure Function Northbound APIs; Stage 3; (… [cited by applicant]
3GPP TS 36.322 V16.0.0 (Jul. 2020); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Link Contro… [cited by applicant]
3GPP TS 37.324 V16.3.0 (Jun. 2021); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; E-UTRA and NR; Service Data Adaptation Protocol (SDAP) specification; … [cited by applicant]
3GPP TS 38.300 V16.7.0 (Sep. 2021); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; NR and NG-RAN Overall Description; Stage 2; (Release 16). [cited by applicant]
3GPP TS 38.322 V16.2.0 (Dec. 2020); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Radio Link Control (RLC) protocol specification; (Release 16). [cited by applicant]
3GPP TS 38.323 V16.4.0 (Jun. 2021); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Packet Data Convergence Protocol (PDCP) specification; (Release 16… [cited by applicant]
3GPP TS 38.331 V16.5.0 (Jun. 2021); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Radio Resource Control (RRC) protocol specification; (Release 16). [cited by applicant]
3GPP TS 38.413 V16.7.0 (Oct. 2021); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; NG Application Protocol (NGAP); (Release 16). [cited by applicant]
3GPP TS 38.415 V16.5.0 (Jul. 2021); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; PDU Session User Plane Protocol; (Release 16). [cited by applicant]
R2-163775; 3GPP TSG-RAN WG2 Meeting #93b; Dubrovnik, Croatia, Apr. 11-15, 2016; (Update of R2-162241); Agenda Item: 9.4.3 (Protocol Architecture); Source: Fujitsu; Title: Radio Bearer Handling and Challenges for 5G; Doc… [cited by applicant]
R2-166571; 3GPP TSG-RAN WG2 Meeting #95bis; Kaohsiung, Taiwan, Oct. 10-14, 2016; Title: Throughput prediction and network assisted DASH; Source: Qualcomm Incorporated; Agenda item: 8.16; Document for: Discussion and App… [cited by applicant]
R2-166574; 3GPP TSG-RAN WG2 Meeting #95bis; Kaohsiung, Taiwan, Oct. 10-14, 2016; Title: Radio-aware TCP optimization; Source: Qualcomm Incorporated, CMCC, Huawei; Agenda item: 8.16; Document for: Discussion and Approval. [cited by applicant]
R2-166576; 3GPP TSG-RAN WG2 Meeting #95bis; Kaohsiung, Taiwan, Oct. 10-14, 2016; Title: Text proposal for radio-aware TCP optimization; Source: Qualcomm Incorporated, CMCC, Huawei; Agenda item: 8.16; Document for: pCR. [cited by applicant]
R2-166583; 3GPP TSG RAN WG2 Meeting #95bis; Kaohsiung, Oct. 10-14, 2016; Agenda item: 8.16; Source: Intel Corporation; Title: Impact analysis of critical data discard on UL Video transmission; Document for: Discussion a… [cited by applicant]
R2-166585; 3GPP TSG-RAN WG2 Meeting #95bis; Kaohsiung, Taiwan, Oct. 10-14, 2016; Title: Text proposal for service information acquisition and UE assisted local cache; Source: Qualcomm Incorporated, CMCC; Agenda item: 8.… [cited by applicant]
R2-166597; 3GPP TSG-RAN2 Meeting #95bis; Kaohsiung, Oct. 10-14, 2016; Title: Discussion on the solution on video optimization; Source: Huawei, HiSilicon, Qualcomm Incorporated, CMCC; Agenda item: 8.16 SI: Study on Conte… [cited by applicant]
R2-166642; 3GPP TSG-RAN WG2 Meeting #95bis; Kaohsiung, Taiwan, Oct. 10-14, 2016; Agenda item: 8.16; Source: Nokia, Alcatel-Lucent Shanghai Bell; Title: Considerations on CASD issues; WID/SID: FS_LTE_context—Release 14; … [cited by applicant]
R2-1700191; 3GPP TSG-RAN WG2 NR Tdoc; Spokane, USA, Jan. 17-19, 2017; Agenda Item: 3.2.1.5; Souce: MediaTek Inc.; Title: User Plane Enhancements for TCP Performance; Document for: Discussion and decision. [cited by applicant]
R2-1703311; 3GPP TSG-RAN WG2 #97bis; Apr. 3-7, 2017; Revision of R2-1700377; Spokane, USA; Source: NTT Docomo, Inc., Fujitsu; Title: Potential hurdle in maximising DL TCP throughput; Document for: Discussion and decisio… [cited by applicant]
R2-1703524; 3GPP TSG-RAN WG2 #97bis; Spokane, USA, Apr. 3-7, 2017; Revision of R2-1701686; Agenda Item: 10.2.2.4; Source: MediaTek Inc.; Title: Impact of blockage on TCP performance in high frequency scenarios; Document… [cited by applicant]
R2-1704060; 3GPP TSG-RAN2 #98; Hangzhou, China, May 15-19, 2017; Agenda Item: 9.5.2; Source: OPPO; Title: Discussion on open issues of eVideo; Document for: Discussion and Decision. [cited by applicant]
R2-1704757; 3GPP TSG RAN WG2 Meeting #98; Hangzhou, China, May 15-19, 2017; Agenda item: 9.5.2; Source: Intel Corporation; Title: Enhancements to critical data discard on video; Document for: Discussion and decision. [cited by applicant]
R2-1707777; 3GPP TSG-RAN2 #99; Berlin, Germany, Aug. 21-25, 2017; Agenda Item: 9.5.3; Source: OPPO; Title: Discussion on open issues of eVideo; Document for: Discussion and Decision. [cited by applicant]
R3-162790; 3GPP TSG RAN WG3 Meeting #94; Reno, USA, Nov. 14-18, 2016; Agenda item: 28.3; Source: Intel Corporation; Title: Impact analysis of critical data discard on UL Video transmission and TP to address solutions fo… [cited by applicant]
RP-213587; 3GPP TSG RAN Meeting #94e; Electronic Meeting, Dec. 6-17, 2021; (revision of RP-213558); Source: Nokia (Email discussion moderator); Title: New SID “Study on XR Enhancements for NR”; Document for: Approval; A… [cited by applicant]
S2-2105434; 3GPP TSG-TSA2 Meeting # 146E; E-meeting, Aug. 16-27, 2021; Change Request; 23.501; CR Draft; rev ---; Current version: 1x.x.x. [cited by applicant]
S2-2109360; SA WG2 Meeting #S2-148E; Nov. 15-22, 2021, Electronic meeting(revision of S2-2108416r07); Source: China Mobile, Huawei, Hisilicon, Tencent, Xiaomi; Title: New SID on Study on architecture enhancement for XR … [cited by applicant]
S4-210612; 3GPP TSG SA WG4 #113e; E-meeting, Apr. 6-14, 2021; revision of S4-210468; Agenda item: 11.8 1; Source: Qualcomm Incorporated; Title: [FS_XRTraffic] SA4 and RAN1 Collaboration Proposal; Document for Discussion… [cited by applicant]
S4-210640; F3GPP TSG SA WG4113-e; Apr. 6-14, 2021; revision of S4-210634; Pseudo Change Request; 26.804; CR <CR#>; rev -; Current version: 0.1.1. [cited by applicant]
RP-180346; 3GPP RAN#79, Chennai, Mar. 19-22, 2018; Source: Mediatek; Title: Study on NR Enhancements for TCP Motivation. [cited by applicant]
S1-202120; Title: Motivation for R18 5G multi-media enhancements SID; Source: Huawei; May 8, 2020. [cited by applicant]
S1-203149; 3GPP TSG-SA WG1 Meeting #91-e; e-meeting, Aug. 24-Sep. 2, 2020; Title: Motivation for network efficiency for wideband media services; Source: Huawei. [cited by applicant]
SP-210620; 3GPP SA Rel. 18 Workshop Sep. 9-10, 2021; Title: System Architecture (SA2) Rel 18 priorities; Source: Qualcomm. [cited by applicant]
3GPP TS 29.244 V17.3.0 (Dec. 2021); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Interface between the Control Plane and the User Plane Nodes; St… [cited by applicant]
3GPP TS 38.323 V16.2.0 (Sep. 2020); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Packet Data Convergence Protocol (PDCP) specification; (Release 16… [cited by applicant]
International Search Report and Written Opinion of the International Searching authority mailed Apr. 25, 2023, in International Application No. PCT/US2023/011252. [cited by applicant]