IP Library Granted Patent US 12,289,776
Granted Patent B2
US 12,289,776 · App. 17/764,183 · Granted Apr 29, 2025

Method and apparatus for a two-step random access procedure

Inventors: Hyejung Jung (Northbrook, IL); Joachim Löhr (Wiesbaden, DE); Vijay Nangia (Woodridge, IL); Prateek Basu Mallick (Dreieich, DE); Ravi Kuchibhotla (Chicago, IL); Alexander Johann Maria Golitschek Edler von Elbwart (Darmstadt, DE); Robert T. Love (Barrington, IL)
Assignee: Lenovo (Singapore) Pte. Ltd.
H04W74/0841H04L1/0061H04L1/1812H04W24/08H04W52/242H04W52/325H04W52/367H04W74/002H04W74/006H04W74/0833
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,289,776
App. No.
17/764,183
Granted
Apr 29, 2025
Kind
B2
Abstract

At least one common PUCCH resource set configuration can be received ( 1310 ) for a 2-step random access procedure. At least one common PUCCH resource set can be determined ( 1320 ) based on the at least one common PUCCH resource set configuration. A PRACH and a corresponding MsgA PUSCH can be transmitted ( 1330 ). A MsgB PDSCH can be received ( 1340 ) in response to the transmitted PRACH and MsgA PUSCH. The received MsgB PDSCH can be decoded ( 1350 ). A successRAR intended to the UE can be identified ( 1360 ) from the decoded MsgB PDSCH. A common PUCCH resource set of the at least one common PUCCH resource set and a PUCCH resource of the common PUCCH resource set can be determined ( 1370 ) based on the successRAR. At least HARQ-ACK feedback information for the MsgB PDSCH can be transmitted ( 1380 ) on the PUCCH resource.

Claims (64)

1. A method performed by a user equipment (UE), the method comprising:

receiving at least one common physical uplink control channel (PUCCH) resource set configuration for a 2-step random access procedure;

determining at least one common PUCCH resource set based on the at least one common PUCCH resource set configuration;

transmitting a physical random access channel (PRACH) and a corresponding MsgA physical uplink shared channel (PUSCH):

receiving a MsgB physical downlink shared channel (PDSCH) in response to the transmitted PRACH and MsgA PUSCH;

decoding the received MsgB PDSCH;

identifying a success random access response intended to the UE from the decoded MsgB PDSCH;

determining a common PUCCH resource set of the at least one common PUCCH resource set and a PUCCH resource of the common PUCCH resource set based on the success random access response; and

transmitting at least hybrid automatic repeat request (HARQ) acknowledgement feedback information for the MsgB PDSCH on the PUCCH resource.

2. The method according to claim 1 , wherein each of the at least one common PUCCH resource set configuration defines each of the at least one common PUCCH resource sets.

3. The method according to claim 1 , further comprising detecting a downlink control information (DCI) format addressed to a MsgB-radio network temporary identifier (RNTI),

wherein the DCI format addressed to the MsgB-RNTI is the DCI format included in a physical downlink control channel (PDCCH) with a cyclic redundancy check scrambled by the MsgB-RNTI, and

wherein the MsgB PDSCH is received based on the detected DCI format.

4. The method according to claim 1 , wherein a particular common PUCCH resource set configuration of the at least one common PUCCH resource set configuration is used for a 4-step random access procedure.

5. The method according to claim 1 , wherein transmitting at least the HARQ acknowledgement feedback information comprises transmitting at least the HARQ acknowledgement feedback information based on the success random access response intended to the UE being identified from the decoded MsgB PDSCH and based on the HARQ acknowledgement information comprising an acknowledgement.

6. The method according to claim 1 ,

wherein the success random access response includes an indication of whether to multiplex a channel state information report with the HARQ acknowledgement information on the PUCCH resource, and

wherein the common PUCCH resource set is determined based on the indication.

7. The method according to claim 6 ,

wherein the indication further includes information of a channel state information report type, and

wherein the common PUCCH resource set is determined based on the information of the channel state information report type.

8. The method according to claim 1 , wherein each of the at least one common PUCCH resource set configuration includes information of a PUCCH format.

9. The method according to claim 1 , further comprising sending a higher-layer UE identifier on the MsgA PUSCH.

10. The method according to claim 9 , wherein identifying the success random access response intended to the UE comprises identifying a success random access response with a contention resolution identifier, where the contention resolution identifier is based on the higher-layer UE identifier.

11. The method according to claim 1 , further comprising:

receiving an indication that indicates whether at least one re-transmission of a transport block of the MsgB PDSCH by a network entity is allowed in order to enable the UE to receive and combine data of the transport block from each transmission of the transport block by the network entity; and

receiving downlink control information (DCI) scheduling the transport block based on the indication.

12. The method according to claim 11 , wherein receiving the DCI comprises:

receiving the DCI including at least one field related to combining of the data of the transport block, in response to receiving the indication that at least one re-transmission of the transport block of the MsgB PDSCH by the network entity is allowed; and

receiving the DCI without at least one field related to combining of the data of the transport block, in response to receiving the indication that at least one re-transmission of the transport block of the MsgB PDSCH by the network entity is not allowed.

13. A user equipment (UE) for wireless communication, comprising:

at least one memory; and

at least one processor coupled with the at least one memory and configured to cause the UE to:

a receive at least one common physical uplink control channel (PUCCH) resource set configuration for a 2-step random access procedure;

determine at least one common PUCCH resource set based on the at least one common PUCCH resource set configuration;

transmit a physical random access channel (PRACH) and a corresponding MsgA physical uplink shared channel (PUSCH);

receive a MsgB physical downlink shared channel (PDSCH) in response to the transmitted PRACH and MsgA PUSCH;

decode the received MsgB PDSCH;

identify a success random access response intended to the UE from the decoded MsgB PDSCH;

determine a common PUCCH resource set of the at least one common PUCCH resource set and a PUCCH resource of the common PUCCH resource set based on the success random access response; and

transmit at least hybrid automatic repeat request HARQ) acknowledgement feedback information for the MsgB PDSCH on the PUCCH resource.

14. The UE according to claim 13 , wherein each of the at least one common PUCCH resource set configuration defines each of the at least one common PUCCH resource sets.

15. The apparatus UE according to claim 13 ,

wherein the processor is further configured to cause the UE to detect a downlink control information (DCI) format addressed to a MsgB-radio network temporary identifier (RNTI),

wherein the DCI format addressed to the MsgB-RNTI is the DCI format included in a physical downlink control channel (PDCCH) with a cyclic redundancy check scrambled by the MsgB-RNTI, and

wherein the MsgB PDSCH is received based on the detected DCI format.

16. The UE according to claim 13 , wherein a particular common PUCCH resource set configuration of the at least one common PUCCH resource set configuration is used for a 4 -step random access procedure.

17. The UE according to claim 13 , wherein the processor is further configured to cause the UE to transmit at least the HARQ acknowledgement feedback information based on the success random access response intended to the UE being identified from the decoded MsgB PDSCH and based on the HARQ acknowledgement information comprising an acknowledgement.

18. The UE according to claim 13 ,

wherein the success random access response includes an indication of whether to multiplex a channel state information report with the HARQ acknowledgement information on the PUCCH resource, and

wherein the common PUCCH resource set is determined based on the indication.

19. The UE according to claim 18 ,

wherein the indication further includes information of a channel state information report type, and

wherein the common PUCCH resource set is determined based on the information of the channel state information report type.

20. A processor for wireless communication, comprising:

at least one controller coupled with at least one memory and configured to cause the processor to:

receive at least one common physical uplink control channel (PUCCH) resource set configuration for a 2 -step random access procedure;

determine at least one common PUCCH resource set based on the at least one common PUCCH resource set configuration;

transmit a physical random access channel (PRACH) and a corresponding MsgA physical uplink shared channel (PUSCH);

receive a MsgB physical downlink shared channel (PDSCH) in response to the transmitted PRACH and MsgA PUSCH;

decode the received MsgB PDSCH;

identify a success random access response intended to the processor from the decoded MsgB physical downlink shared channel PDSCH;

determine a common PUCCH resource set of the at least one common PUCCH resource set and a PUCCH resource of the common PUCCH resource set based on the success random access response; and

transmit at least hybrid automatic repeat request (HARQ) acknowledgement feedback information for the MsgB PDSCH on the PUCCH resource.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 26, 2022
From: JUNG, HYEJUNG; LÖHR, JOACHIM; NANGIA, VIJAY; BASU MALLICK, PRATEEK; KUCHIBHOTLA, RAVI; GOLITSCHEK EDLERVONELBWART, ALEXANDER JOHANN MARIA; LOVE, ROBERT T.
To: LENOVO (SINGAPORE) PTE. LTD.
Reel/Frame 059511/0769 →
Continuity (2)
Provisional Application 62911197 · Oct 4, 2019
Related Publication 20220386388A1 · Dec 1, 2022
References Cited (62)
US 12245295B2 · Jung et al. · 2025 [cited by applicant]
US 12250734B2 · Jung et al. · 2025 [cited by applicant]
US 20180279186A1 · Park et al. · 2018 [cited by applicant]
US 20180368169A1 · Jung et al. · 2018 [cited by applicant]
US 20190053313A1 · Zhou et al. · 2019 [cited by applicant]
US 20190313437A1 · Jung et al. · 2019 [cited by applicant]
US 20200008244A1 · Suzuki · 2020 [cited by examiner]
US 20200252974A1 · Akkarakaran et al. · 2020 [cited by applicant]
US 20200260341A1 · Jang · 2020 [cited by examiner]
US 20220225428A1 · Xiong et al. · 2022 [cited by applicant]
US 20220264659A1 · Enbuske et al. · 2022 [cited by applicant]
US 20220295574A1 · Lin et al. · 2022 [cited by applicant]
US 20220369376A1 · Lin et al. · 2022 [cited by applicant]
US 20220377812A1 · Jung et al. · 2022 [cited by applicant]
US 20220386387A1 · Jung et al. · 2022 [cited by applicant]
US 20220386388A1 · Jung et al. · 2022 [cited by applicant]
US 20230007700A1 · Saha et al. · 2023 [cited by applicant]
CN 114731697A · 2020 [cited by applicant]
CN 114731594A · 2022 [cited by applicant]
EP 3570624A1 · 2019 [cited by applicant]
KR 20220079548A · 2022 [cited by applicant]
WO 2018085726A1 · 2018 [cited by applicant]
WO 2018131538A1 · 2018 [cited by applicant]
WO 2018151230A1 · 2018 [cited by applicant]
WO 2019028881A1 · 2019 [cited by applicant]
WO 2021064706A1 · 2021 [cited by applicant]
WO 2021064707A1 · 2021 [cited by applicant]
WO 2021064709A1 · 2021 [cited by applicant]
PCT International Search Report for PCT/IB2020/059309, Hyejung Jung, mailing date—Jan. 25, 2021. [cited by applicant]
PCT International Search Report for PCT/IB2020/059310, Hyejung Jung, mailing date—Jan. 22, 2021. [cited by applicant]
Mattis, Notice of References Cited, PTO-892, U.S. Appl. No. 15/764,181, U.S. Patent and Trademark Office, Jul. 1, 2024. [cited by applicant]
Gavin Alarcon, European Office Action, EP Patent Application No. 20792731.0-1215, European Patent Office, Jul. 8, 2024. [cited by applicant]
3GPP TS 38.321 V15.7.0 (Sep. 2019), 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Medium Access Control (MAC) Protocol Specification (Release 15). [cited by applicant]
ZTE et al., “On the remaining issues of 2-step RACH procedures”, R1-1908182, for 3GPP TSG-RAN WG1 Meeting #98, Prague, CZ, Aug. 26-30, 2019. [cited by applicant]
Sony, “Discussion on Procedure for 2-step RACH”, R1-1908763, for 3GPP TSG-RAN WG1 Meeting #98, Prague, CZ, Aug. 26-30, 2019. [cited by applicant]
Qualcomm Incorporated, “Procedures for 2-step Rach”, R1-1909240, for 3GPP TSG-RAN WG1 Meeting #98, Prague, CZ, Aug. 26-30, 2019. [cited by applicant]
Spreadtrum Communications, “Discussion on 2-step RACH procedure”, R1-1910016, for 3GPP TSG-RAN WG1 Meeting #98Bis, Chongqing, China, Oct. 14-20, 2019. [cited by applicant]
InterDigital, “2-step RACH Procedure”, R2-1814008, for 3GPP TSG-RAN WG2 Meeting #103bis, Chengdu, China, Oct. 8-12, 2018. [cited by applicant]
Huawei et al., “Discussion on mobility in connected mode for NR-U”, R2-1816611, for 3GPP TSG-RAN WG2 Meeting #104, Spokane, USA, Dec. 12-16, 2018. [cited by applicant]
Qualcomm Incorporated, “Further details on RACH for NR-U”, R2-1818503, for 3GPP TSG-RAN2 Meeting #104, Spokane, WA, USA, Nov. 12-16, 2018. [cited by applicant]
NEC, “Details on fallback mechanisms”, R2-1909147, for 3GPP TSG-RAN WG2 #107, Prague, Czech Republic, Aug. 26-30, 2019. [cited by applicant]
Intel Corporation, “Further consideration of MsgB contents and procedure when CCCH SDU is included in MsgA”, R2-1910378, for 3GPP TSG RAN WG2 #107, Prague, Czech Republic, Aug. 20-23, 2019. [cited by applicant]
Ericsson, “2-step RA 38.331 Draft CR”, Tdoc R2-1912683, for 3GPP TSG-RAN WG2 Meeting #107bis, Chongqing, P. R. China, Oct. 14-18, 2019. [cited by applicant]
ZTE Corporation et al., “Support of CFRA with 2-step RACH”, R2-1913368, for 3GPP TSG-RAN2 WG2 Meeting #107-bis, Chongqing, China, Oct. 14-18, 2019. [cited by applicant]
LG Electronics Inc., “Further clarifications on parameters for Random Access procedure”, R2-2003666, for 3GPP TSG-RAN WG2 Meeting #109bis-e, Apr. 20-30, 2020. [cited by applicant]
CATT, “LS to RAN1 on RAN2 agreements related to 2-step RACH”, 3GPP TSG-RAN WG2 #107; R2-1911776, Prague, Czech Republic, Aug. 26-30, 2019. [cited by applicant]
3GPP, “LS on overall procedure for 2-step RACH”, 3GPP TSG-RAN WG2 #106; R2-1908481, Reno, Nevada, USA, May 13-17, 2019. [cited by applicant]
Nokia, “On 2-step RACH Procedure”, 3GPP TSG-RAN WG2 #98; R1-1908342, Prague, Czech Republic, Aug. 26-30, 2019. [cited by applicant]
U.S. Appl. No. 17/764,182 , “Notice of Allowance”, U.S. Appl. No. 17/764,182, filed Jul. 10, 2024, 8 pages. [cited by applicant]
U.S. Appl. No. 17/764,182 , “Notice of Allowance”, U.S. Appl. No. 17/764,182, filed Oct. 29, 2024, 5 pages. [cited by applicant]
202080067309 , “Foreign Office Action”, CN Application No. 202080067309, May 31, 2024, 12 pages. [cited by applicant]
20792732.8 , “Foreign Office Action”, EP Application No. 20792732.8, Jul. 11, 2024, 12 pages. [cited by applicant]
3GPP , “Medium Access Control (MAC) protocol specification”, 3GPP TS 38.321 v15.7.0 Release 15, Sep. 2019, 77 pages. [cited by applicant]
Motorola Mobility , et al., “2-step RACH procedure”, 3GPP TSG RAN WG1 #98bis, R1-1911035, Chongqing, China, Oct. 2019, 6 pages. [cited by applicant]
PCT/IB2020/059312 , “International Search Report”, PCT Application PCT/IB2020/059312, Jan. 21, 2021, 4 pages. [cited by applicant]
Spreadtrum Communications , “Discussion on 2-step RACH procedure”, 3GPP TSG RAN WG1 Meeting #98Bis, R1-1910016, Chongqing, China, Oct. 2019, 8 pages. [cited by applicant]
202080067309.6 , “Foreign Office Action”, CN Application No. 202080067309.6, Oct. 11, 2024, 20 pages. [cited by applicant]
202080067314.7 , “Foreign Office Action”, CN Application No. 202080067314.7, Oct. 11, 2024, 15 pages. [cited by applicant]
Jung, Hyejung , et al., “Pursuant to MPEP § 2001.06(b) the applicant brings the following application to the Examiner's attention:”, U.S. Appl. No. 62/911,197, filed Oct. 4, 2019, 35 pages. [cited by applicant]
“Corrected Notice of Allowance”, U.S. Appl. No. 17/764, 181, Dec. 20, 2024, 5 pages. [cited by applicant]
“Notice of Allowance”, U.S. Appl. No. 17/764, 181, Dec. 18, 2024, 9 pages. [cited by applicant]
“Supplemental Notice of Allowability”, U.S. Appl. No. 17/764, 181, Jan. 27, 2025, 2 pages. [cited by applicant]
Cited By (1)
US 12,684,589