IP Library › Granted Patent US 12,302,370
Granted Patent B2
US 12,302,370 · App. 18/314,073 · Granted May 13, 2025

Preconfigured uplink resource techniques in wireless communications

Inventors: Umesh Phuyal (San Diego, CA); Mungal Singh Dhanda (Slough, GB); Ayan Sengupta (San Diego, CA); Alberto Rico Alvarino (San Diego, CA); Le Liu (San Jose, CA)
Assignee: QUALCOMM Incorporated
H04W72/53H04W72/21H04W72/23H04W76/27H04W76/36
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,370
App. No.
18/314,073
Granted
May 13, 2025
Kind
B2
Abstract

Methods, systems, and devices for wireless communications are described. that support preconfigured uplink resources (PUR) in wireless communications. A base station may communicate that support for PUR is available, and may allocate PUR resources to a user equipment (UE) based on requests from the UE. The UE may receive an indication that the base station supports PUR, such as via a system information block (SIB), determine to request PUR, and transmit a PUR request message to the base station. A PUR response from the base station may indicate configuration, or reconfiguration of PUR allocation for the UE that may be used for uplink transmissions, or release of the PUR allocation.

Claims (40)

1. A user equipment (UE), comprising:

one or more memories storing processor-executable code; and

one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the UE to:

transmit a preconfigured uplink resource (PUR) request message to an access network entity based at least in part on determining that the access network entity supports preconfigured uplink resources, wherein the PUR request message includes a number of instances of PUR grants requested by the UE;

receive a message from the access network entity indicating a PUR configuration or reconfiguration or release of PURs;

determine, based at least in part on the message from the access network entity, a set of control channel resources to monitor for an uplink grant; and

monitor the set of control channel resources for the uplink grant.

2. The UE of claim 1 , wherein the number of instances of PUR grants provides an explicit number of PUR grants or an indication of an infinite number of PUR grants.

3. The UE of claim 1 , wherein the number of instances of PUR grants requested by the UE indicate a one-shot PUR configuration is requested or a multi-shot PUR configuration is requested.

4. The UE of claim 1 , wherein the PUR configuration is provided as a delta configuration that indicates differences over a prior PUR configuration of the UE.

5. The UE of claim 1 , wherein the PUR configuration is provided as a delta configuration that indicates differences over a default PUR configuration or that indicates differences over a configuration being used at the UE.

6. The UE of claim 1 , wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:

transmit, after receiving the PUR configuration, a PUR reconfiguration failure indication to the access network entity; and

release the PUR configuration.

7. The UE of claim 1 , wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:

determine that the PUR configuration is de-configured based at least in part on receiving a broadcast system information transmission from the access network entity that indicates PUR is unsupported; and

release the PUR configuration.

8. The UE of claim 1 , wherein the PUR request message is transmitted to the access network entity in an uplink message of an early data transmission (EDT) procedure.

9. The UE of claim 8 , wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:

format the PUR request message to be transmitted in the uplink message of the EDT procedure, wherein the PUR request message indicates a requested configuration, reconfiguration, or release of the PUR configuration.

10. The UE of claim 8 , wherein the PUR request message is transmitted in a message three (MSG3) transmission of the EDT procedure.

11. The UE of claim 1 , wherein the message from the access network entity indicating configuration or reconfiguration or release of PURs of the UE is received in an early data transmission (EDT) downlink message 4 that provides a radio resource control (RRC) connection release message or an RRC early data complete message.

12. The UE of claim 1 , wherein the message from the access network entity explicitly or implicitly provides one or more of an indication that the UE is to use a prior PUR configuration, a confirmation of the prior PUR configuration, an indication to de-configure and release the prior PUR configuration, a new resource for a new PUR configuration, or any combinations thereof.

13. A user equipment (UE), comprising:

one or more memories storing processor-executable code; and

one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the UE to:

transmit a preconfigured uplink resource (PUR) request message to an access network entity based at least in part on determining that the access network entity supports preconfigured uplink resources, wherein the PUR request message includes a number of instances of PUR grants requested by the UE;

receive a message from the access network entity indicating a PUR configuration or PUR reconfiguration or PUR release;

determine that the PUR configuration is de-configured based at least in part on a broadcast system information transmission that indicates PUR is unsupported; and

release the PUR configuration.

14. The UE of claim 13 , wherein the number of instances of PUR grants provides an explicit number of PUR grants or an indication of an infinite number of PUR grants.

15. The UE of claim 13 , wherein the number of instances of PUR grants requested by the UE indicate a one-shot PUR configuration is requested or a multi-shot PUR configuration is requested.

16. The UE of claim 13 , wherein the PUR configuration is provided as a delta configuration that indicates differences over a prior PUR configuration of the UE.

17. The UE of claim 13 , wherein the PUR configuration is provided as a delta configuration that indicates differences over a default PUR configuration or that indicates differences over a configuration being used at the UE.

18. The UE of claim 13 , wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:

transmit, after receiving the PUR configuration, a PUR reconfiguration failure indication to the access network entity; and

release the PUR configuration.

19. The UE of claim 13 , wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:

receive the broadcast system information transmission from the access network entity that indicates the PUR is unsupported, wherein the release of the PUR configuration is based at least in part on the received broadcast system information transmission.

20. The UE of claim 13 , wherein the PUR request message is transmitted to the access network entity in an uplink message of an early data transmission (EDT) procedure.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 24, 2023
From: PHUYAL, UMESH; DHANDA, MUNGAL SINGH; SENGUPTA, AYAN; RICO ALVARINO, ALBERTO; LIU, LE
To: QUALCOMM INCORPORATED
Reel/Frame 064695/0925 →
Continuity (3)
Continuation 16926164 · Jul 10, 2020
Provisional Application 62873836 · Jul 12, 2019
Related Publication 20230362965A1 · Nov 9, 2023
References Cited (22)
US 11690086B2 · Phuyal · 2023 [cited by examiner]
US 20180020431A1 · Cho et al. · 2018 [cited by applicant]
US 20210014864A1 · Phuyal et al. · 2021 [cited by applicant]
CN 105744614A · 2016 [cited by applicant]
WO WO2020065620A1 · 2020 [cited by applicant]
WO WO2020155059A1 · 2020 [cited by examiner]
Ericsson: “PUR Configuration”, 3GPP Draft, 3GPP TSG-RAN WG2 #106, R2-1906939—PUR Configuration, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre, 650, Route Des Lucioles, F-06921, Sophia-Antipolis Ced… [cited by applicant]
International Search Report and Written Opinion—PCT/US2020/041732—ISA/EPO—Sep. 16, 2020. [cited by applicant]
Qualcomm Incorporated: “(Re)configuration and Release of PUR,” 3GPP Draft, 3GPP TSG-RAN WG2 Meeting #106, R2-1906445, PUR (Re)Config, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre, 650, Route Des L… [cited by applicant]
Sierra Wireless: “D-PUR Configuration Details,” 3GPP Draft, R2-1907244, 3GPP TSG-RAN WG2 Meeting#106, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre, 650, Route Des Lucioles, F-06921, Sophia-Antipol… [cited by applicant]
Sierra Wireless: “Pre-Configured UL Resources Design Considerations”, 3GPP Draft, 3GPP TSG RAN WG2 Meeting #104, R2-1817940, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre; 650, Route Des Lucioles; … [cited by applicant]
ZTE Corporation: “Main Issues for Transmission Over Preconfigured Dedicated Resource in Idle”, 3GPP Draft, 3GPP TSG-RAN2 meeting#104, R2-1816993, Main Issues for Transmission Over Preconfigured Dedicated Resource in IDL… [cited by applicant]
Taiwan Search Report—TW109123619—TIPO—Nov. 6, 2023. [cited by applicant]
Sierra Wireless: “Pre-Configured UL Resource Design Considerations”, 3GPP TSG-RAN WG2 Meeting#105bis, R2-1903063, Xi'an, China, Apr. 8-12, 2019, pp. 1-8. [cited by applicant]
Ericsson: “PUR Configuration”, 3GPP TSG-RAN WG2 #106, Tdoc R2-1906939 (Revision of R2-1903832), Reno, Nevada, US, May 13-17, 2019, pp. 1-12. [cited by applicant]
Qualcomm Incorporated: “(Re)Configuration and Release of PUR”, 3GPP TSG-RAN WG2 Meeting #106, R2-1906445, Reno, Nevada USA, May 13-17, 2019, May 3, 2019, pp. 1-9. [cited by applicant]
Sierra Wireless: “D-PUR Configuration Details”, 3GPP TSG-RAN WG2 Meeting#106, R2-1907244, Reno, Nevada, USA, May 13-17, 2019, May 2, 2019, pp. 1-7. [cited by applicant]
Sierra Wireless: “Email Discussion [104#43][eMTC & NB-IoT R16] D-PUR Report”, 3GPP TSG-RAN WG2 Meeting#105, R2-1900120, Athens, Greece, Feb. 25-Mar. 1, 2019, Feb. 14, 2019, pp. 1-47. [cited by applicant]
Sierra Wireless: “Pre-Configured UL Resources Design Considerations”, 3GPP TSG RAN WG2 Meeting #104, R2-1817940, Spokane, USA, Nov. 12-16, 2018, Nov. 2, 2018, pp. 1-11. [cited by applicant]
Qualcomm Incorporated: “Retransmission and Fallback for Data Transmission on PUR”, 3GPP TSG-RAN WG2 Meeting #106, R2-1906446, Reno, Nevada, USA, May 13-17, 2019, 4 Pages. [cited by applicant]
Sierra Wireless: “Email Discussion [104#43][eMTC & NB-IoT R16] D-PUR Report”, 3GPP TSG-RAN WG2 Meeting#105, R2-1900120, Athens, Greece, Feb. 25, 2019-Mar. 1, 2019, Feb. 14, 2019, pp. 1-45, Section 2, Tables 2, 3, 7 and … [cited by applicant]
Sierra Wireless: “Pre-configured UL Resource Design Considerations”, 3GPP TSG-RAN WG2 Meeting#105bis, R2-1903063, Xi'an, China, Apr. 8, 2018-Apr. 12, 2019, Mar. 29, 2019, pp. 1-8, Sections 1-2 and 5. [cited by applicant]