IP Library › Granted Patent US 12,302,438
Granted Patent B2
US 12,302,438 · App. 18/919,942 · Granted May 13, 2025

Timer for small data transmission

Inventors: Taehun Kim (Fairfax, VA); Hyoungsuk Jeon (Centreville, VA); Esmael Hejazi Dinan (McLean, VA); Kyungmin Park (Vienna, VA)
Assignee: Ofinno, LLC
H04W76/20H04W76/19H04W76/30
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,302,438
App. No.
18/919,942
Granted
May 13, 2025
Kind
B2
Abstract

A wireless device receives, from a first base station, a RRC release message comprising a suspend configuration, wherein the suspend configuration comprises a configuration of a small data transmission (SDT) procedure indicating a radio bearer configured for the SDT procedure. The device suspends, based on the suspend configuration, one or more radio bearers comprising the radio bearer configured for the SDT procedure. Based on initiating the SDT procedure, the wireless device resumes the radio bearer configured for the SDT procedure; and transmits, to a second base station, a radio resource control (RRC) resume request message. The wireless device communicates with the second base station and during the SDT procedure, data associated with the SDT procedure, and transmits to the second base station and during the SDT procedure, a user equipment (UE) assistance information message comprising a non-SDT indication, wherein the non-SDT indication indicates availability of data mapped to a radio bearer which is not configured for the SDT procedure, and a resume cause associated with the data. The wireless device receives, from the second base station and after transmitting the UE assistance information message, an RRC response message.

Claims (83)

1. A method comprising:

receiving, by a wireless device from a first base station, a radio resource control (RRC) release message comprising a suspend configuration, wherein:

the suspend configuration comprises a configuration of a small data transmission (SDT) procedure; and

the configuration indicates a radio bearer configured for the SDT procedure;

suspending, based on the suspend configuration, one or more radio bearers comprising the radio bearer configured for the SDT procedure;

based on initiating the SDT procedure:

resuming the radio bearer configured for the SDT procedure; and

transmitting, to a second base station, a radio resource control (RRC) resume request message;

communicating, with the second base station and during the SDT procedure, data associated with the SDT procedure;

transmitting, by the wireless device to the second base station and during the SDT procedure, a user equipment (UE) assistance information message comprising:

a non-SDT indication, wherein the non-SDT indication indicates availability of data mapped to a radio bearer which is not configured for the SDT procedure; and

a resume cause associated with the data; and

receiving, from the second base station and after transmitting the UE assistance information message, an RRC response message.

2. The method of claim 1 , wherein the RRC response message comprises at least one of:

an RRC resume message;

an RRC release message; or

an RRC setup message.

3. The method of claim 1 , wherein the suspend configuration comprises at least one of:

a resume identity;

a radio access network (RAN) paging cycle;

a RAN based notification area (RNA) configuration; or

network hop chaining count (NCC) value.

4. The method of claim 3 , wherein the RNA configuration comprises at least one of:

RNA notification area information; or

periodic RNA update timer value.

5. The method of claim 1 , wherein the first base station receives, from the second base station, a partial context of the wireless device.

6. The method of claim 5 , wherein the partial context is a context associated with a lower layer of the wireless device, a radio link control layer of the wireless device, a medium access control layer of the wireless device, and/or a physical layer of the wireless device.

7. The method of claim 1 , wherein the second base station comprises a last serving base station or an anchor base station.

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

receive, from a first base station, a radio resource control (RRC) release message comprising a suspend configuration, wherein:

the suspend configuration comprises a configuration of a small data transmission (SDT) procedure; and

the configuration indicates a radio bearer configured for the SDT procedure;

suspend, based on the suspend configuration, one or more radio bearers comprising the radio bearer configured for the SDT procedure;

based on initiating the SDT procedure:

resume the radio bearer configured for the SDT procedure; and

transmit, to a second base station, a radio resource control (RRC) resume request message;

communicate, with the second base station and during the SDT procedure, data associated with the SDT procedure;

transmit, by the wireless device to the second base station and during the SDT procedure, a user equipment (UE) assistance information message comprising:

a non-SDT indication, wherein the non-SDT indication indicates availability of data mapped to a radio bearer which is not configured for the SDT procedure; and

a resume cause associated with the data; and

receive, from the second base station and after transmitting the UE assistance information message, an RRC response message.

9. The wireless device of claim 8 , wherein the RRC response message comprises at least one of:

an RRC resume message;

an RRC release message; or

an RRC setup message.

10. The wireless device of claim 8 , wherein the suspend configuration comprises at least one of:

a resume identity;

a radio access network (RAN) paging cycle;

a RAN based notification area (RNA) configuration; or

network hop chaining count (NCC) value.

11. The wireless device of claim 10 , wherein the RNA configuration comprises at least one of:

RNA notification area information; or

periodic RNA update timer value.

12. The wireless device of claim 8 , wherein the first base station receives, from the second base station, a partial context of the wireless device.

13. The wireless device of claim 12 , wherein the partial context is a context associated with a lower layer of the wireless device, a radio link control layer of the wireless device, a medium access control layer of the wireless device, and/or a physical layer of the wireless device.

14. The wireless device of claim 8 , wherein the second base station comprises a last serving base station or an anchor base station.

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

receive, from a first base station, a radio resource control (RRC) release message comprising a suspend configuration, wherein:

the suspend configuration comprises a configuration of a small data transmission (SDT) procedure; and

the configuration indicates a radio bearer configured for the SDT procedure;

suspend, based on the suspend configuration, one or more radio bearers comprising the radio bearer configured for the SDT procedure;

based on initiating the SDT procedure:

resume the radio bearer configured for the SDT procedure; and

transmit, to a second base station, a radio resource control (RRC) resume request message;

communicate, with the second base station and during the SDT procedure, data associated with the SDT procedure;

transmit, by the wireless device to the second base station and during the SDT procedure, a user equipment (UE) assistance information message comprising:

a non-SDT indication, wherein the non-SDT indication indicates availability of data mapped to a radio bearer which is not configured for the SDT procedure; and

a resume cause associated with the data; and

receive, from the second base station and after transmitting the UE assistance information message, an RRC response message.

16. The non-transitory computer-readable medium of claim 15 , wherein the RRC response message comprises at least one of:

an RRC resume message;

an RRC release message; or

an RRC setup message.

17. The non-transitory computer-readable medium of claim 15 , wherein the suspend configuration comprises at least one of:

a resume identity;

a radio access network (RAN) paging cycle;

a RAN based notification area (RNA) configuration; or

network hop chaining count (NCC) value.

18. The non-transitory computer-readable medium of claim 17 , wherein the RNA configuration comprises at least one of:

RNA notification area information; or

periodic RNA update timer value.

19. The non-transitory computer-readable medium of claim 15 , wherein the first base station receives, from the second base station, a partial context of the wireless device.

20. The non-transitory computer-readable medium of claim 19 , wherein the partial context is a context associated with a lower layer of the wireless device, a radio link control layer of the wireless device, a medium access control layer of the wireless device, and/or a physical layer of the wireless device.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 18, 2024
From: KIM, TAEHUN; JEON, HYOUNGSUK; DINAN, ESMAEL HEJAZI; PARK, KYUNGMIN
To: OFINNO, LLC
Reel/Frame 069308/0256 →
Continuity (3)
Continuation PCTUS2023019660 · Apr 24, 2023
Provisional Application 63334011 · Apr 22, 2022
Related Publication 20250048474A1 · Feb 6, 2025
References Cited (63)
US 20210410180A1 · Tsai et al. · 2021 [cited by applicant]
US 20230180338A1 · Fujishiro · 2023 [cited by examiner]
US 20230380003A1 · Agiwal · 2023 [cited by examiner]
US 20240090045A1 · Agiwal · 2024 [cited by examiner]
US 20240306147A1 · Wang · 2024 [cited by examiner]
WO 2021257856A1 · 2021 [cited by applicant]
R4-2207128; 3GPP TSG-RAN WG4 Meeting #102-e; Electronic, Feb. 21-Mar. 3, 2022; Change Request; 38.133; CR 2269; rev-; Current version: 17.4.0. [cited by applicant]
R1-2202979; 3GPP TSG-WG1 Meeting #108; e-meeting, Feb. 21-Mar. 3, 2022; Change Request; 38.211; CR 0094; rev-; Current version: 17.0.0. [cited by applicant]
R1-2202987; 3GPP TSG RAN WG1 #108-e; e-Meeting, Feb. 21-Mar. 3, 2022; Change Request; 38.213; CR 0303; rev-; Current version: 17.0.0. [cited by applicant]
R1-2202996; 3GPP TSG-RAN WG1 Meeting #108-e; Electronic Meeting, Feb. 21-Mar. 3, 2022; Change Request; 38.214; CR 0267; rev-; Current version: 17.0.0. [cited by applicant]
R2-2204234; 3GPP TSG-RAN WG2 Meeting #117 Electronic; Elbonia, Feb. 21-Mar. 3, 2022; Change Request; 38.300; CR 0357; rev 7; Current version: 16.8.0. [cited by applicant]
R2-2204216; 3GPP TSG-RAN2 Meeting #117e; Electronic, Feb. 21-Mar. 3, 2022; Change Request; 38.321; CR 1198; rev 1; Current version: 16.7.0. [cited by applicant]
R2-2203769; 3GPP TSG-RAN WG2 Meeting #117e; Electronic, Feb. 21-Mar. 3, 2022; Change Request; 38.321; CR 1214; rev 1; Current version: 16.7.0. [cited by applicant]
R2-2203768; 3GPP TSG-RAN WG2 Meeting #117-e; Electronic, Feb. 21-Mar. 3, 2022; Change Request; 38.331; CR 2937; rev 1; Current version: 16.7.0. [cited by applicant]
R2-2204241; 3GPP TSG-RAN WG2 Meeting #117-e; Electronic, Feb. 21-Mar. 3, 2022; Change Request; 38.331; CR 2951; rev 1; Current version: 16.7.0. [cited by applicant]
3GPP TS 38.401 V17.0.0 (Apr. 2022); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; Architecture description; (Release 17). [cited by applicant]
R3-222956; 3GPP TSG-RAN WG3 Meeting #115-e; Electronic Meeting, Feb. 21-Mar. 3, 2022; Change Request; 38.401; CR 0192; rev 3; Current version: 16.8.0. [cited by applicant]
R3-222961; 3GPP TSG-RAN WG3 Meeting #115-e; E-meeting, Feb. 21-Mar. 3, 2022; Change Request; 38.401; CR 0196; rev 1; Current version: 16.8.0. [cited by applicant]
R3-222957; 3GPP TSG-RAN WG3 Meeting #115-e; Feb. 21-Mar. 3, 2022; Change Request; 38.420; CR 0024; rev 2; Current version: 16.0.0. [cited by applicant]
3GPP TS 38.423 V17.0.0 (Apr. 2022); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; Xn application protocol (XnAP); (Release 17). [cited by applicant]
R3-222958; 3GPP TSG-RAN WG3 Meeting #115-e; Online, Feb. 21-Mar. 3, 2022; Change Request; 38.423; CR 0720; rev 3; Current version: 16.8.0. [cited by applicant]
3GPP TS 38.463 V17.0.0 (Apr. 2022); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; E1 Application Protocol (E1AP); (Release 17). [cited by applicant]
R3-222986; 3GPP TSG-RAN WG3 #115; Feb. 21-Mar. 3, 2022; Online; Change Request; 38.463; CR 0681; rev 2; Current version: 16.8.0. [cited by applicant]
R3-222962; 3GPP TSG-RAN WG3 #115e; Online, Feb. 21-Mar. 3, 2022; Change Request; 38.470; CR 0081; rev 2; Current version: 16.5.0. [cited by applicant]
3GPP TS 38.473 V17.0.0 (Apr. 2022); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; F1 application protocol (F1AP); (Release 17). [cited by applicant]
R3-222963; 3GPP TSG-RAN WG3 Meeting #115-e; Feb. 21-Mar. 3, 2022; Online; Change Request; 38.473; CR 0833; rev 3; Current version: 16.8.0. [cited by applicant]
R3-222960; 3GPP TSG-RAN WG3#115-e; E-meeting, Feb. 21-Mar. 3, 2022; Change Request; 38.473; CR 0834; rev 3; Current version: 16.8.0. [cited by applicant]
R3-221472; 3GPP TSG-RAN WG3 #114bis-e; Online, Jan. 17-26, 2022; Title: LS on handling of DL non-SDT during SDT procedure; Reply to:; Release: Release 17; Work Item: NR_SmallData_INACTIVE; Source: RAN3; To: RAN2. [cited by applicant]
R3-221667; 3GPP TSG-RAN3 Meeting #115-e; Electronic meeting, Feb. 21-Mar. 3, 2022; 3GPP TSG RAN WG2 Meeting #116bis-e; Electronic meeting, Jan. 17-25, 2022; Title: LS on RAN3 impacts for non-SDT handling; Release: Rel-1… [cited by applicant]
R3-221775; 3GPP TSG-RAN WG3 #115-e; E-meeting, Feb. 22-Mar. 3, 2022; Agenda Item: 24.2; Source: NEC; Title: RACH based SDT discussion; Document for: decision. [cited by applicant]
R3-221776; 3GPP TSG-RAN WG3 #115-e; E-meeting, Feb. 22-Mar. 3, 2022; Agenda Item: 24.2; Source: NEC; Title: (TP for XNAP BL CR on RA-SDT) RACH based SDT; Document for: decision. [cited by applicant]
R3-221796; 3GPP TSG-RAN WG3 #115-e; Feb. 21-Mar. 3, 2022; Online; Source: ZTE Corporation; Title: Discussion on non-SDT handling during ongoing SDT procedure; Document for: Discussion; Agenda Item: 24.4. [cited by applicant]
R3-221816; 3GPP TSG-RAN WG3#115-e; E-Meeting, Feb. 21-Mar. 3, 2022; Agenda item: 24.2; Source: Nokia, Nokia Shanghai Bell; Title: (TP for TS 38.423) Conclusions on RACH-based SDT; Document for: Approval. [cited by applicant]
R3-221817; 3GPP TSG-RAN WG3#115-e; E-Meeting, Feb. 21-Mar. 3, 2022; Agenda item: 24.2; Source: Nokia, Nokia Shanghai Bell; Title: (TP for TS 38.473) Conclusions on RACH-based SDT; Document for: Approval. [cited by applicant]
R3-221853; 3GPP TSG-RAN WG3 Meeting #115-e; Online, Feb. 21-Mar. 3, 2022; Agenda Item: 24.2; Source: Ericsson, ZTE, Lenovo, Motorola Mobility; Title: (TP for RA-SDT BL CR to TS 38.423) Procedures for context fetch; Docu… [cited by applicant]
R3-221854; 3GPP TSG-RAN WG3 Meeting #115-e; Online, Feb. 21-Mar. 3, 2022; Agenda Item: 24.4; Source: Ericsson; Title: Handling of non-SDT arrival during SDT procedure; Document for: Approval. [cited by applicant]
R3-221855; 3GPP TSG-RAN WG3 Meeting #115-e; Online, Feb. 21-Mar. 3, 2022; Title: [DRAFT] Reply LS on RAN3 impacts for non-SDT handling; Response to: R3-221667 / R2-2201977; Release: Rel-17; Work Item: NR_SmallData_INACT… [cited by applicant]
R3-221896; 3GPP TSG-RAN WG3 Meeting #115-e; Online, Feb. 21-Mar. 3, 2022; Title: (TP for SDT BL CRs) On RA-based SDT; Source: CATT; Agenda item: 24.2; Document for: Discussion and Decision. [cited by applicant]
R3-221898; 3GPP TSG-RAN WG3 Meeting #115-e; Online, Feb. 21-Mar. 3, 2022; Title: (TP for SDT BL CR 38.463) On Continue ROHC and non-SDT; Source: CATT; Agenda item: 24.4; Document for: Discussion and Decision. [cited by applicant]
R3-221899; 3GPP TSG-RAN WG3 Meeting #115-e; Online, Feb. 21-Mar. 3, 2022; Title: [DRAFT] Reply LS on RAN3 impacts for non-SDT handling; Reply to: R3-221667/R2-2201977 LS on RAN3 impacts for non-SDT handling; Release: Re… [cited by applicant]
R3-221937; 3GPP TSG-RAN WG3 #115-e; Feb. 21-Mar. 3, 2022; Online; Title: (TP for RA-SDT BLCR to TS 38.300) Left issues for RA-SDT without anchor relocation case; Source: ZTE, Ericsson; Agenda item: 24.2; Document for: D… [cited by applicant]
R3-221938; 3GPP TSG-RAN WG3 #115-e; Feb. 21-Mar. 3, 2022; Online; Title: (TP for RA-SDT BLCR to TS 38.300) Left issues for RA-SDT with anchor relocation case; Source: ZTE; Agenda item: 24.2; Document for: Discussion and… [cited by applicant]
R3-221995; 3GPP TSG-RAN WG3 Meeting #115e; E-meeting, Feb. 21-Mar. 3, 2022; Agenda item: 24.2; Source: Lenovo, Motorola Mobility; Title: Remaining Issues on RA-SDT; Document for: Discussion. [cited by applicant]
R3-221997; 3GPP TSG-RAN WG3 Meeting #115e; E-meeting, Feb. 21-Mar. 3, 2022; Agenda item: 24.4; Source: Lenovo, Motorola Mobility; Title: Discussion on RAN3 impacts for UL non-SDT handling; Document for: Discussion. [cited by applicant]
R3-221998; 3GPP TSG-RAN WG3 Meeting #115e; E-meeting, Feb. 21-Mar. 3, 2022; Agenda item: 24.4; Source: Lenovo, Motorola Mobility; Title: (TP to RA-SDT TS 38.463 BL CR) Non SDT Data Arrival; Document for: Discussion. [cited by applicant]
R3-222032; 3GPP TSG-RAN WG3 Meeting # 115-e; Online, Feb. 21-Mar. 3, 2022; Agenda item: 24.4. Others ; Source: Google; Title: (TP to RA-SDT BLCR for TS38.463) Changes to Bearer Context Setup procedure; Document for: Dis… [cited by applicant]
R3-222041; 3GPP TSG-RAN WG3 Meeting #115-e; Feb. 21-Mar. 3, 2022; Agenda item: 24.4; Source: Qualcomm Incorporated; Title: Discussion on RAN2 Ls on non-SDT Handling; Document for: Discussion and Approval. [cited by applicant]
R3-222042; 3GPP TSG RAN WG2 Meeting #115-e; Feb. 21-Mar. 3, 2022; Title: [DRAFT] Reply LS on RAN3 impacts for non-SDT handling; Response to: LS on RAN3 impacts for non-SDT handling (R3-221667/R2-2201977); Release: Rel-1… [cited by applicant]
R3-222124; 3GPP TSG-RAN WG3 Meeting #115-e; E-Meeting, Feb. 21-Mar. 3, 2022; Agenda Item: 24.2; Source: Samsung; Title: (TP to RA-SDT BL CR on TS38.473) Discussion on the remaining issues of RA-SDT; Document for: Discus… [cited by applicant]
R3-222170; 3GPP TSG-RAN WG3 Meeting #115-e; Electronic meeting, Feb. 21-Mar. 3, 2022; Title: (TPs to RA-SDT BL CRs of TS 38.300, 38.420, 38.470) RACH based SDT without anchor relocation; Source: Huawei; Agenda item: 24.… [cited by applicant]
R3-222171; 3GPP TSG-RAN WG3 Meeting #115-e; Electronic meeting, Feb. 21-Mar. 3, 2022; Title: (TP to RA-SDT BL CR of TS 38.423) RACH based SDT without anchor relocation; Source: Huawei; Agenda item: 24.2; Document Type: … [cited by applicant]
R3-222173; 3GPP TSG-RAN WG3 Meeting #115-e; Electronic meeting, Feb. 21-Mar. 3, 2022; Title: Considerations on CCCH solution for UL non-SDT arrival; Source: Huawei, InterDigital; Agenda item: 24.4; Document Type: Discus… [cited by applicant]
R3-222238; 3GPP TSG-RAN WG3 #115-e; Electronic meeting, Feb. 21-Mar. 3, 2022; Agenda item: 24.2; Source: LG Electronics Inc.; Title: (TP for RA-SDT BL CR to TS 38.423) Support of RA-SDT; Document for: Agreement. [cited by applicant]
R3-222241; 3GPP TSG-RAN WG3 #115-e; Electronic meeting, Feb. 21-Mar. 3, 2022; Agenda item: 24.4; Source: LG Electronics Inc.; Title: Discussion on CCCH solution for non-SDT data; Document for: Agreement. [cited by applicant]
R3-222319; 3GPP TSG-RAN WG3 Meeting #115-e; Feb. 21-Mar. 3, 2022; Online; Agenda item: 24.4 (Others); Source: Samsung; Title: (TP to RA-SDT BL CR TS38.463) Discussion on remaining issues on SDT; Document for: Discussion… [cited by applicant]
R3-222351; 3GPP TSG-RAN WG3 Meeting #115-e; Electronic Meeting, Feb. 21-Mar. 3, 2022; Agenda item: 24.2 ; Source: Intel Corporation; Title: (TP for RA-SDT BL CR for TS 38.423/463) Toward the completion of RA-SDT; Docume… [cited by applicant]
R3-222352; 3GPP TSG-RAN WG3 Meeting #115-e; Electronic Meeting, Feb. 21-Mar. 3, 2022; Agenda item: 24.2 ; Source: Intel Corporation; Title: (TP for RA-SDT BL CR for TS 38.423) Why relocation preference is necessary for … [cited by applicant]
R3-222353; 3GPP TSG-RAN WG3 Meeting #115-e; Electronic Meeting, Feb. 21-Mar. 3, 2022; Agenda item: 24.2; Source: Intel Corporation; Title: (TP for RA-SDT BL CR for TS 38.300/401); Document for: Other. [cited by applicant]
R3-222355; 3GPP TSG-RAN WG3 Meeting #115-e; Electronic Meeting, Feb. 21-Mar. 3, 2022; Agenda item: 24.4; Source: Intel Corporation; Title: Discussion on RAN3 impacts for non-SDT handling from RAN2; Document for: Discuss… [cited by applicant]
R3-222356; 3GPP TSG-RAN WG3 Meeting #115-e; Electronic Meeting, Feb. 21-Mar. 3, 2022; Title: [Draft] Reply LS on RAN3 impacts for non-SDT handling; Response to: R3-221667/R2-2201977 LS on RAN3 impacts for non-SDT handli… [cited by applicant]
International Search Report and Written Opinion of the International Searching Authority, mailed Jul. 21, 2023, in International Application No. PCT/US2023/019660. [cited by applicant]
R2-2010008; 3GPP TSG-RAN WG2 Meeting #112e; Online, Nov. 2-13, 2020; Agenda item: 8.6.3; Source: Qualcomm Incorporated; Title: Control plane aspects on NR small data transmission; WID/SID: NR SmallData INACTIVE-Core—Rel… [cited by applicant]
R3-222856; 3GPP TSG-RAN WG3 Meeting #115-e; Online, Feb. 21-Mar. 3, 2022; Agenda Item: 24.2; Source: Ericsson (moderator); Title: Summary of Offline Discussion on RACH based SDT; Document for: Approval. [cited by applicant]