IP Library › Granted Patent US 12,250,734
Granted Patent B2
US 12,250,734 · App. 17/764,181 · Granted Mar 11, 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,250,734
App. No.
17/764,181
Granted
Mar 11, 2025
Kind
B2
Abstract

A command can be received ( 910 ) from a network entity. The command can initiate a random access procedure and can include information of a type of random access procedure. The type of random access procedure can be selected from a 2-step random access procedure and a 4-step random access procedure. A MsgA transmission can be transmitted ( 920 ) in response to receiving the command when the type of random access procedure is the 2-step random access procedure.

Claims (59)

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

receiving a command initiating a random access procedure, the command comprising a common uplink control channel resource set and information of a type of the random access procedure, wherein the type of the random access procedure comprises a 2-step random access procedure or a 4-step random access procedure;

transmitting a MsgA transmission in response to receiving the command based at least in part on the type of the random access procedure being the 2-step random access procedure;

receiving, in response to the MsgA transmission, a MsgB transmission;

selecting a common uplink control channel resource of the common uplink control channel resource set based at least in part on reception of the MsgB transmission; and

transmitting, using the common uplink control channel resource, feedback information associated with the MsgB transmission.

2. The method of claim 1 , wherein the command indicates a handover in a higher layer message comprising a plurality of radio resource control (RRC) parameters that reconfigure an RRC configuration, wherein the handover comprises reconfiguration of the plurality of RRC parameters, and wherein the MsgA transmission is transmitted in response to receiving the command of the handover in the higher layer message.

3. The method of claim 1 , wherein the command comprises downlink control information (DCI) comprising an indication of initiation of a physical downlink control channel (PDCCH) order based random access procedure.

4. The method of claim 1 , further comprising:

receiving, based at least in part on the type of the random access procedure being the 2-step random access procedure, information of at least one dedicated physical random access channel (PRACH) preamble and at least one set of PRACH occasions for the 2-step random access procedure, wherein transmitting the MsgA transmission comprises:

transmitting the at least one dedicated PRACH preamble on a PRACH occasion of the at least one set of PRACH occasions, wherein the at least one set of PRACH occasions is associated with the at least one dedicated PRACH preamble.

5. The method of claim 4 , further comprising:

receiving, based at least in part on the type of the random access procedure being the 2-step random access procedure, information of at least one dedicated MsgA physical uplink shared channel (PUSCH) resource associated with the at least one dedicated PRACH preamble and associated with the at least one set of PRACH occasions for the 2-step random access procedure, wherein transmitting the MsgA transmission comprises:

transmitting a MsgA PUSCH on the at least one dedicated MsgA PUSCH resource.

6. The method of claim 1 , further comprising:

receiving, based at least in part on the type of the random access procedure being the 2-step random access procedure, an indication requesting a channel state information (CSI) report, wherein the MsgA transmission comprises a MsgA physical uplink shared channel comprising the CSI report.

7. The method of claim 6 , wherein receiving the command comprises:

receiving downlink control information (DCI) comprising a field with the indication requesting the CSI report jointly encoded with the information of the type of the random access procedure.

8. The method of claim 1 , further comprising:

receiving, based at least in part on the type of the random access procedure being the 2-step random access procedure, a configuration of a first physical downlink control channel (PDCCH) search space set and a second PDCCH search space set for reception of a PDCCH in response to transmitting the MsgA transmission; and

monitoring for a plurality of PDCCH candidates in at least one of the first PDCCH search space set or the second PDCCH search space set in the 2-step random access procedure.

9. The method of claim 8 , wherein the first PDCCH search space set is a common search space set for a downlink control information (DCI) format with a cyclic redundancy check (CRC) scrambled by a first identity, and wherein the second PDCCH search space set is a UE-specific search space set for a DCI format with a CRC scrambled by a second identity.

10. The method of claim 9 , further comprising:

determining the first identity is a MsgB-radio network temporary identifier (RNTI) based at least in part on a physical random access channel (PRACH) occasion used for a PRACH preamble transmission of the MsgA transmission, wherein the MsgB-RNTI is used to receive the PDCCH scheduling a MsgB physical downlink shared channel (PDSCH) corresponding to the MsgA transmission;

decoding the MsgB PDSCH; and

determining whether the MsgB PDSCH comprises a fallback random access response intended for the UE.

11. The method of claim 9 , wherein the second identity is a UE-specific identity, and wherein the MsgA transmission comprises a MsgA physical uplink shared channel (PUSCH) comprising the UE-specific identity.

12. The method of claim 11 , wherein the MsgA transmission further comprises a contention-based physical random access channel (PRACH) preamble transmission, and wherein monitoring the plurality of PDCCH candidates comprises monitoring the plurality of PDCCH candidates in the first PDCCH search space set or the second PDCCH search space set.

13. The method of claim 8 , wherein monitoring for the plurality of PDCCH candidates comprises monitoring for the plurality of PDCCH candidates during a time window, and wherein a starting time of the time window is based at least in part on an ending time of the MsgA transmission and the configuration of the first PDCCH search space set or the second PDCCH search space set.

14. 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:

receive a command initiating a random access procedure, the command comprising a common uplink control channel resource set and information of a type of the random access procedure, wherein the type of the random access procedure comprises a 2-step random access procedure or a 4-step random access procedure;

transmit a MsgA transmission in response to receiving the command based at least in part on the type of the random access procedure being the 2-step random access procedure;

receive, in response to the MsgA transmission, a MsgB transmission;

select a common uplink control channel resource of the common uplink control channel resource set based at least in part on reception of the MsgB transmission; and

transmit, using the common uplink control channel resource, feedback information associated with the MsgB transmission.

15. The UE of claim 14 , wherein the command indicates a handover in a higher layer message comprising a plurality of radio resource control (RRC) parameters that reconfigure an RRC configuration, wherein the handover comprises reconfiguration of the plurality of RRC parameters, and wherein the MsgA transmission is transmitted in response to receiving the command of the handover in the higher layer message.

16. The UE of claim 14 , wherein the command comprises downlink control information (DCI) comprising an indication of initiation of a physical downlink control channel (PDCCH) order based random access procedure.

17. The UE of claim 14 , wherein the at least one processor is configured to cause the UE to:

receive, based at least in part on the type of the random access procedure being the 2-step random access procedure, information of at least one dedicated physical random access channel (PRACH) preamble and at least one set of PRACH occasions for the 2-step random access procedure; and

transmit the at least one dedicated PRACH preamble on a PRACH occasion of the at least one set of PRACH occasions, wherein the at least one set of PRACH occasions is associated with the at least one dedicated PRACH preamble.

18. The UE of claim 14 , wherein the at least one processor is further configured to cause the UE to:

receive, based at least in part on the type of the random access procedure being the 2-step random access procedure, a configuration of a first physical downlink control channel (PDCCH) search space set and a second PDCCH search space set for reception of a PDCCH in response to transmitting the MsgA transmission; and

monitor for a plurality of PDCCH candidates in at least one of the first PDCCH search space set or the second PDCCH search space set in the 2-step random access procedure.

19. A processor for wireless communication, comprising:

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

receive a command initiating a random access procedure, the command comprising a common uplink control channel resource set and information of a type of the random access procedure, wherein the type of the random access procedure comprises a 2-step random access procedure or a 4-step random access procedure;

transmit a MsgA transmission in response to receiving the command based at least in part on the type of the random access procedure being the 2-step random access procedure;

receive, in response to the MsgA transmission, a MsgB transmission;

select a common uplink control channel resource of the common uplink control channel resource set based at least in part on reception of the MsgB transmission; and

transmit, using the common uplink control channel resource, feedback information associated with the MsgB transmission.

20. A network entity (NE) 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 NE to:

transmit a command initiating a random access procedure, the command comprising a common uplink control channel resource set and information of a type of the random access procedure, wherein the type of the random access procedure comprises a 2-step random access procedure or a 4-step random access procedure;

receive a MsgA transmission in response to transmitting the command based at least in part on the type of the random access procedure being the 2-step random access procedure;

transmit, in response to the MsgA transmission, a MsgB transmission; and

receive, using a common uplink control channel resource selected from the common uplink control channel resource set based at least in part on the transmission of the MsgB transmission, feedback information associated with the MsgB transmission.

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 EDLER VON ELBWART, ALEXANDER JOHANN MARIA; LOVE, ROBERT T.
To: LENOVO (SINGAPORE) PTE. LTD.
Reel/Frame 059511/0726 →
Continuity (2)
Provisional Application 62911197 · Oct 4, 2019
Related Publication 20220386387A1 · Dec 1, 2022
References Cited (75)
US 20180279186A1 · Park · 2018 [cited by examiner]
US 20180368169A1 · Jung · 2018 [cited by examiner]
US 20190053313A1 · Zhou et al. · 2019 [cited by applicant]
US 20190313437A1 · Jung · 2019 [cited by examiner]
US 20200008244A1 · Suzuki et al. · 2020 [cited by applicant]
US 20200252974A1 · Akkarakaran et al. · 2020 [cited by applicant]
US 20200260341A1 · Jang et al. · 2020 [cited by applicant]
US 20220225428A1 · Xiong · 2022 [cited by examiner]
US 20220264659A1 · Enbuske · 2022 [cited by examiner]
US 20220295574A1 · Lin · 2022 [cited by examiner]
US 20220369376A1 · Lin · 2022 [cited by examiner]
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]
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,183 , “Non-Final Office Action”, U.S. Appl. No. 17/764,183, Aug. 6, 2024, 27 pages. [cited by applicant]
3GPP , “LS on overall procedure for 2-step RACH”, 3GPP TSG RAN WG2 #106; R2-1908481; Reno, Nevada, May 13, 2019, 2 pages. [cited by applicant]
PCT/IB2020/059310 , “International Search Report”, PCT Application No. PCT/IB2020/059310, Jan. 22, 2021, 4 pages. [cited by applicant]
U.S. Appl. No. 17/764,182 , “Notice of Allowance”, U.S. Appl. No. 17/764,182, Jul. 10, 2024, 8 pages. [cited by applicant]
202080067309 , “Foreign Office Action”, CN Application No. 202080067309, May 31, 2024, 12 pages. [cited by applicant]
20792731.0 , “Foreign Office Action”, EP Application No. 20792731.0, Jul. 8, 2024, 10 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]
3GPP , “Technical Specification Group Radio Access Network; NR; Physical layer procedures for control”, 3GPP TS 38.213 V15.7.0, 3rd Generation Partnership Project; (Release 15), Sep. 2019, 108 pages. [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, 2019, 1 page. [cited by applicant]
Ericsson , “2-step RA 38.331 Draft CR”, 3GPP TSG-RAN WG2 #107bis Tdoc R2-1912683, 12 pages. [cited by applicant]
Huawei , et al., “Discussion on mobility in connected mode for NR-U”, 3GPP TSG-RAN WG2 #104 R2-1816611, Dec. 12, 2018, 3 pages. [cited by applicant]
Intel Corporation , “Further consideration of MsgB contents and procedure when CCCH SDU is included in MsgA”, 3GPP TSG RAN WG2 #107 R2-1910378, Aug. 20, 2019, 4 pages. [cited by applicant]
Interdigital , “2-Step RACH Procedure”, 3GPP TSG-RAN WG2 Meeting #103bis R2-1814008, Oct. 8, 2018, 5 pages. [cited by applicant]
LG Electronics , “Further Clarification on Parameters for Random Access Procedure”, 3GPP TSG-RAN WG2 #109bis-e R2-2003666, Apr. 20, 2020, 6 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]
NEC , “Details on fallback mechanisms”, 3GPP TSG-RAN WG2 #107 R2-1909147, Aug. 26, 2019, 4 pages. [cited by applicant]
PCT/IB2020/059309 , “International Search Report”, PCT Application PCT/IB2020/059309, Jan. 25, 2021, 6 pages. [cited by applicant]
PCT/IB2020/059312 , “International Search Report”, PCT Application PCT/IB2020/059312, Jan. 21, 2021, 4 pages. [cited by applicant]
Qualcomm Incorporated , “Further details on RACH for NR-U”, 3GPP TSG-RAN2#104 R2-1818503, Nov. 12, 2018, 2 pages. [cited by applicant]
Qualcomm Incorporated , “Procedures for Two-Step RACH”, 3GPP TSG-RAN WG1 Meeting #98 R1-1909240, Aug. 26, 2019, 15 pages. [cited by applicant]
Sony , “Discussion on Procedure for 2-step RACH”, 3GPP TSG RAN WG1 #98 R1-1908763, Aug. 26, 2019, 6 pages. [cited by applicant]
Spreadtrum Communications , “Discussion on 2-step RACH procedure”, 3GPP TSG RAN WG1 Meeting #98Bis, Oct. 14, 2019, 8 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]
ZTE , “On the remaining issues of 2-step RACH procedures”, 3GPP TSG RAN WG1 Meeting #98 R1-1908182, Aug. 26, 2019, 20 pages. [cited by applicant]
ZTE Corporation , et al., “Support of CFRA with 2-step RACH”, 3GPP TSG-RAN2 Meeting #107-bis R2-1913368, Oct. 14, 2019, 6 pages. [cited by applicant]
PCT International Search Report for PCT/IB2020/059310, Hyejung Jung, mailing date—Jan. 22, 2021. [cited by applicant]
PCT International Search Report for PCT/IB2020/059312, Hyejung Jung, mailing date—Jan. 21, 2021. [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]
U.S. Appl. No. 17/764,182 , “Notice of Allowance”, U.S. Appl. No. 17/764,182, Oct. 29, 2024, 5 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, Oct. 4, 2019, 35 pages. [cited by applicant]
Cited By (2)
US 12,289,776 US 12,684,589