IP Library › Granted Patent US 12,262,422
Granted Patent B2
US 12,262,422 · App. 17/635,453 · Granted Mar 25, 2025

HARQ procedure for RACH response message in two-step RACH

Inventors: Jing Lei (San Diego, CA); Yi Huang (San Diego, CA); Wanshi Chen (San Diego, CA); Linhai He (San Diego, CA); Ruiming Zheng (Beijing, CN); Peter Gaal (San Diego, CA); Joseph Binamira Soriaga (San Diego, CA)
Assignee: QUALCOMM Incorporated
H04W74/0841H04L1/1812H04L5/0053H04W72/1263H04W72/23H04W74/0866
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,262,422
App. No.
17/635,453
Granted
Mar 25, 2025
Kind
B2
Abstract

Certain aspects of the present disclosure provide techniques for a hybrid automatic repeat request (HARQ) procedure for the random access channel (RACH) response message in a two-step RACH procedure. A method that may be performed by a user equipment (UE) includes sending a RACH message to a base station (BS) during a two-step RACH procedure. The RACH message includes a RACH preamble and a RACH payload. The UE monitors a RACH response message from the BS during a random access response (RAR) window. The UE transmits a retransmission of the RACH message, an acknowledgement (ACK) to the RACH response message, a negative acknowledgment (NACK) to the RACH response message, or does not transmit, to the BS based on whether a RACH response message carrying a success RAR or a fallback RAR, or no RACH response message, is received from the BS during the window.

Claims (59)

1. A method for wireless communications by a user equipment (UE), the method comprising:

sending a random access channel (RACH) message during a two-step RACH procedure, the RACH message including a RACH preamble and a RACH payload;

monitoring for a RACH response message during a random access response (RAR) window;

receiving a physical downlink control channel (PDCCH) of the RACH response message, wherein the PDCCH of the RACH response message includes a field indicating whether hybrid automatic repeat request (HARQ) feedback is requested for a physical downlink shared channel (PDSCH) of the RACH response message; and one of:

if the UE successfully decodes the PDSCH of the RACH response message during the RAR window:

transmitting an acknowledgement (ACK) to the RACH response message if the PDSCH of the RACH response message is carrying a success RAR during the RAR window and the field in the PDCCH of the RACH response message indicates that HARQ feedback is requested for the PDSCH of the RACH response message; or

transmitting a retransmission of the RACH payload of the RACH message on a physical uplink shared channel (PUSCH) if the PDSCH of the RACH response message is carrying a fallback RAR; and

if the UE does not successfully decode the PDSCH of the RACH response message during the RAR window:

transmitting a negative acknowledgment (NACK) to the RACH response message if the field in the PDCCH of the RACH response message indicates that HARQ feedback is requested for the PDSCH of the RACH response message; or

performing a discontinuous transmission (DTX) if the field in the PDCCH of the RACH response message indicates that HARQ feedback is not requested for the PDSCH of the RACH response message.

2. The method of claim 1 , wherein the ACK is transmitted on a physical uplink control channel (PUCCH) resource.

3. The method of claim 2 , wherein the PUCCH resource is provided in the RACH response message.

4. The method of claim 2 , wherein the PUCCH resource is preconfigured via system information (SI), radio resource control (RRC) signaling, or downlink control information (DCI).

5. The method of claim 2 , further comprising selecting the PUCCH resource based on a multiple access signature of the UE.

6. The method of claim 1 , wherein the PUSCH is on a resource granted in the RACH response message carrying the fallback RAR.

7. The method of claim 1 , wherein performing DTX is further if the UE does not have a valid resource for providing HARQ feedback.

8. The method of claim 1 , wherein transmitting the NACK is further if the UE has a valid resource for providing HARQ feedback.

9. The method of claim 1 , wherein the ACK is multiplexed with a scheduling request (SR) in uplink control information (UCI) when the UE has new uplink data to transmit and does not have a valid uplink grant for the new uplink data.

10. The method of claim 1 , further comprising receiving a retransmitted RACH response message in response to transmitting the NACK or the DTX, wherein the retransmitted RACH response message includes a radio network temporary identifier (RNTI).

11. The method of claim 1 , wherein the ACK is multiplexed on a PUSCH when the UE does not have a valid configured physical uplink control channel (PUCCH) resource and has a valid uplink grant for new data transmission on the PUSCH.

12. The method of claim 1 , wherein:

the RACH response message includes at least a timing advance command (TAC); and

the method further comprises adjusting a timing offset for uplink transmissions based on the TAC.

13. The method of claim 12 , wherein a granularity of the TAC is based on a numerology configured for a data channel or a control channel in an active uplink bandwidth part (BWP).

14. The method of claim 1 , wherein the RACH response message further includes a contention resolution identifier (ID) and a UE ID when the UE is in a radio resource control (RRC) idle or inactive state and is in a contention based random access (CBRA) mode.

15. The method of claim 1 , wherein the RACH response message with fallback RAR further includes a RACH preamble identifier (RAPID).

16. The method of claim 1 , wherein the RACH response message with fallback RAR further includes a temporary cell radio network temporary identifier (TC-RNTI) when the UE is in a contention based random access (CBRA) mode.

17. The method of claim 1 , wherein the field indicating whether HARQ feedback is requested for the PDSCH of the RACH response message is provided via 1 or 2 bits in the PDCCH of the RACH response message in a physical uplink control channel (PUCCH) resource configuration further including a PUCCH resource set indicator field.

18. The method of claim 17 , wherein:

the field is 1-bit and indicates to provide NACK feedback regardless whether the UE has a valid timing advance (TA) or not to provide NACK feedback regardless whether the UE has a valid TA; or

the field is 2-bits and indicates to provide NACK feedback regardless whether the UE has a valid, to provide NACK feedback only if the UE has a valid TA, not to provide HARQ feedback regardless whether the UE has a valid TA, or not to provide NACK feedback regardless whether the UE has a valid TA.

19. The method of claim 1 , wherein:

the UE is in a contention free random access (CFRA) mode or a contention based random access (CBRA) mode; and

the UE in a radio resource control (RRC) idle, inactive, or connected state.

20. The method of claim 1 , wherein:

the RACH preamble comprises a physical random access channel (PRACH) carrying a RACH sequence;

the RACH payload comprises a demodulation reference signal (DMRS) and a physical uplink shared channel (PUSCH) carrying:

a medium access control (MAC) control element or small data when the UE is in a contention free random access (CFRA) mode; and

a contention resolution identifier (ID) when the UE is in a contention based random access (CBRA) mode.

21. An apparatus for wireless communication, the apparatus comprising:

at least one processor; and

a memory coupled to the at least one processor, the memory comprising code executable by the at least one processor to, individually or collectively, cause the apparatus to:

send a random access channel (RACH) message during a two-step RACH procedure, the RACH message including a RACH preamble and a RACH payload;

monitor a RACH response message during a random access response (RAR) window;

receive a physical downlink control channel (PDCCH) of the RACH response message, wherein the PDCCH of the RACH response message includes a field indicating whether hybrid automatic repeat request (HARQ) feedback is requested for a physical downlink shared channel (PDSCH) of the RACH response message;

if the apparatus successfully decodes the PDSCH of the RACH response message during the RAR window:

transmit an acknowledgement (ACK) to the RACH response message if the RACH response message is carrying a success RAR and the field in the PDCCH of the RACH response message indicates that HARQ feedback is requested for the PDSCH of the RACH response message; and

transmit a retransmission of the RACH payload of the RACH message on a physical uplink shared channel (PUSCH) if the RACH response message is carrying the fallback RAR during the RAR window; and

if the apparatus successfully decodes the PDSCH of the RACH response message during the RAR window:

transmit a negative acknowledgment (NACK) to the RACH response message if the field in the PDCCH of the RACH response message indicates that HARQ feedback is requested for the PDSCH of the RACH response message; and

perform a discontinuous transmission (DTX) if the field in the PDCCH of the RACH response message indicates that HARQ feedback is not requested for the PDSCH of the RACH response message.

22. A non-transitory computer readable medium storing computer executable code thereon for wireless communication by a user equipment (UE), the computer executable code comprising:

code for sending a random access channel (RACH) message during a two-step RACH procedure, the RACH message including a RACH preamble and a RACH payload;

code for monitoring a RACH response message during a random access response (RAR) window;

code for receiving a physical downlink control channel (PDCCH) of the RACH response message, wherein the PDCCH of the RACH response message includes a field indicating whether hybrid automatic repeat request (HARQ) feedback is requested for a physical downlink shared channel (PDSCH) of the RACH response message;

code for transmitting an acknowledgement (ACK) to the RACH response message if the UE successfully decodes the PDSCH of the RACH response message carrying a success RAR during the RAR window and the field in the PDCCH of the RACH response message indicates that HARQ feedback is requested for the PDSCH of the RACH response message;

code for transmitting a negative acknowledgment (NACK) to the RACH response message if the UE does not successfully decodes the PDSCH of the RACH response message during the RAR window and the field in the PDCCH of the RACH response message indicates that HARQ feedback is requested for the PDSCH of the RACH response message;

code for performing a discontinuous transmission (DTX) if the UE does not successfully decode the PDSCH of the RACH response message during the RAR window and the field in the PDCCH of the RACH response message indicates that HARQ feedback is not requested for the PDSCH of the RACH response message; and

code for transmitting a retransmission of the RACH payload of the RACH message on a physical uplink shared channel (PUSCH) if the UE successfully decodes the PDSCH of the RACH response message carrying a fallback RAR during the RAR window.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 25, 2022
From: LEI, JING; HUANG, YI; CHEN, WANSHI; HE, LINHAI; ZHENG, RUIMING; GAAL, PETER; SORIAGA, JOSEPH BINAMIRA
To: QUALCOMM INCORPORATED
Reel/Frame 060015/0223 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 15, 2022
From: LEI, JING; HUANG, YI; CHEN, WANSHI; HE, LINHAI; ZHENG, RUIMING; GAAL, PETER; SORIAGA, JOSEPH BINAMIRA
To: QUALCOMM INCORPORATED
Reel/Frame 059013/0406 →
Priority Claims (1)
WO PCT/CN2019/101168 · Aug 16, 2019 · international
Continuity (1)
Related Publication 20220272769A1 · Aug 25, 2022
References Cited (42)
US 20110216722A1 · Yang · 2011 [cited by examiner]
US 20170289995A1 · Lin · 2017 [cited by examiner]
US 20180027537A1 · Yang · 2018 [cited by applicant]
US 20180124822A1 · Wang et al. · 2018 [cited by applicant]
US 20180139787A1 · Islam et al. · 2018 [cited by applicant]
US 20180295541A1 · Hall et al. · 2018 [cited by applicant]
US 20190159249A1 · Ahn · 2019 [cited by examiner]
US 20200107371A1 · Kunt · 2020 [cited by examiner]
US 20210329704A1 · Yang · 2021 [cited by examiner]
US 20210385854A1 · Wu · 2021 [cited by examiner]
US 20220046717A1 · Zhang · 2022 [cited by examiner]
US 20220053568A1 · Xing · 2022 [cited by examiner]
US 20220086824A1 · Kundu · 2022 [cited by examiner]
US 20220183071A1 · Liu · 2022 [cited by applicant]
US 20220225428A1 · Xiong · 2022 [cited by examiner]
US 20220264653A1 · Xiong · 2022 [cited by examiner]
US 20220279559A1 · Wong · 2022 [cited by examiner]
US 20220287107A1 · Kim · 2022 [cited by examiner]
US 20220377801A1 · Lei et al. · 2022 [cited by applicant]
US 20230413277A1 · Park · 2023 [cited by examiner]
US 20240284494A1 · Kim · 2024 [cited by examiner]
CN 110115096A · 2019 [cited by applicant]
WO 2009088858A1 · 2009 [cited by applicant]
WO 2016175981A1 · 2016 [cited by applicant]
WO WO2017217400A1 · 2017 [cited by examiner]
WO 2018089265 · 2018 [cited by applicant]
WO 2019036150A1 · 2019 [cited by applicant]
Taiwan Search Report—TW109127712—TIPO—Nov. 18, 2023. [cited by applicant]
Ericsson: “Configuration of 2-step RA”, 3GPP TSG-RAN WG2 RAN2#107, R2-1909936, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre, 650, Route Des Lucioles, F-06921, Sophia-Antipolis Cedex, France, vol. … [cited by applicant]
Ericsson: “Fallback for 2-step RA”, 3GPP TSG-RAN WG2 #107, R2-1909934, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre, 650, Route Des Lucioles, F-06921, Sophia-Antipolis Cedex, France, vol. RAN WG2,… [cited by applicant]
Huawei: “Feature Lead Summary of HARQ Enhancements for NR-U”, 3GPP TSG RAN WG1 Meeting #97, R1-1907652, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre, 650, Route Des Lucioles, F-06921, Sophia-Antip… [cited by applicant]
Mediatek Inc: “RNTI and HARQ Aspects of 2-Step RACH”, 3GPP TSG-RAN WG2 Meeting #106, R2-1907073, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre, 650, Route Des Lucioles, F-06921, Sophia-Antipolis Ce… [cited by applicant]
Supplementary European Search Report—EP20854283—Search Authority—The Hague—Jul. 28, 2023. [cited by applicant]
Nokia, et al., “Feature Lead's Summary on Channel Access Procedures”, 3GPP TSG RAN WG1 Meeting #96bis, R1-1904187, Xian, China, Apr. 8-12, 2019, 20 Pages. [cited by applicant]
Nokia., et al., “2-Step RACH Procedure Feature Lead Summary”, R1-1905670, FF3GPP TSG RAN WG1 #96bis, Xi'an, China, Apr. 8-Apr. 12, 2019, pp. 1-92. [cited by applicant]
Qualcomm Incorporated: “Channel Structure for Two-Step RACH”, 3GPP Draft, R1-1907691, 3GPP TSG-RAN WG1 Meeting #97, Channel Structure for Two-Step RACH, 3rd Generation Partnership Project (3GPP), Mobile Competence Centr… [cited by applicant]
International Search Report and Written Opinion—PCT/CN2019/101168—ISAEPO—May 19, 2020. [cited by applicant]
International Search Report and Written Opinion—PCT/CN2020/108803—ISAEPO—May 19, 2020. [cited by applicant]
Nokia et al., “Feature Lead Summary#2 on 2 Step RACH Procedures”, 3GPP TSG RAN WG1 #97, R1-1907838, Reno, USA, May 13-17, 2019, pp. 1-56 (p. 4 Offline Proposal 3.1.1, p. 5, pp. 11-12 Offline Proposal 3.6.1). [cited by applicant]
Nokia et al., “Feature Lead Summary#3 on 2 Step RACH Procedures”, 2-STEP RACH Procedure Feature Lead Summary RAN1#97, 3GPP TSG RAN WG1 #97, R1-1907900, Reno, USA, May 13, 2019-May 17, 2019, May 17, 2019 (May 17, 2019), … [cited by applicant]
Nokia, et al., “On 2-Step RACH Procedure”, 3GPP Draft, 3GPP TSG RAN WG1 #97, R1-1906747, On 2-Step RACH Procedure, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre, 650, Route Des Lucioles, F-06921 So… [cited by applicant]
Qualcomm Incorporated: “Procedures for Two-Step RACH”, 3GPP TSG-RAN WG1 Meeting #97, R1-1907256, 3GPP Draft, R1-1907256 Procedures for Two-Step Rach, 3rd Generation Partnership Project(3GPP), Mobile Competence Centre, 6… [cited by applicant]