IP Library Granted Patent US 12,213,178
Granted Patent B2
US 12,213,178 · App. 17/142,622 · Granted Jan 28, 2025

Random access channel procedures with multiple carriers

Inventors: Sony Akkarakaran (Poway, CA); Tao Luo (San Diego, CA); Makesh Pravin John Wilson (San Diego, CA); Sumeeth Nagaraja (Los Altos, CA); Xiao Feng Wang (San Diego, CA); Kaushik Chakraborty (San Diego, CA); Wooseok Nam (San Diego, CA); Shengbo Chen (San Diego, CA); Juan Montojo (San Diego, CA)
Assignee: QUALCOMM Incorporated
H04W74/0833H04L5/001H04W74/002H04W74/004H04W74/006H04L5/0035H04W36/00692
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,213,178
App. No.
17/142,622
Granted
Jan 28, 2025
Kind
B2
Abstract

Methods, systems, and devices for wireless communication are described. Wireless communications systems may support uplink random access channel (RACH) transmissions on multiple beams and over multiple component carriers (CCs). A wireless device may transmit a random access preamble to a base station in a first RACH transmission, which may indicate a set of CCs over which the base station may respond with a random access response (RAR) in a second RACH transmission. The second RACH transmission may then include an indication for which CCs the wireless device may use for a subsequent RACH transmission (e.g., a RACH message 3). The wireless device may also indicate a beam index and/or time-frequency resources associated with beams and/or CCs used for such cell acquisition transmissions. In other examples, the base station may indicate resources (e.g., via a handover command or RACH command) for wireless device scheduling request and/or beam-failure recovery request transmission.

Claims (67)

1. A method for wireless communication at a user equipment (UE), comprising:

receiving, from an access network entity, an indication that indicates that at least one component carrier is selected for the UE to use to transmit a beam-failure recovery request to the access network entity; and

transmitting, based at least in part on the indication and using one or more component carriers of the at least one component carrier, the beam-failure recovery request to the access network entity.

2. The method of claim 1 , wherein the indication of the at least one component carrier comprises an instruction to transmit the beam-failure recovery request for a single component carrier of the at least one component carrier.

3. The method of claim 1 , wherein the indication of the at least one component carrier comprises an instruction to transmit the beam-failure recovery request for the at least one component carrier.

4. The method of claim 1 , wherein transmitting the beam-failure recovery request to the access network entity comprises:

identifying loss of beam synchronization for a single component carrier of the at least one component carrier; and

transmitting the beam-failure recovery request for the single component carrier.

5. The method of claim 1 , wherein transmitting the beam-failure recovery request to the access network entity comprises:

identifying loss of beam synchronization for a single component carrier of the at least one component carrier; and

transmitting the beam-failure recovery request for the at least one component carrier.

6. The method of claim 1 , further comprising:

receiving, from the access network entity, a quasi co-location indication, the quasi co-location indication indicating a quasi co-location relationship among the at least one component carrier.

7. The method of claim 1 , further comprising:

monitoring for beam failure of at least one component carrier for each group of component carriers of the at least one component carrier.

8. An apparatus for wireless communication at a user equipment (UE), comprising:

one or more processors;

memory coupled with the one or more processors; and

instructions stored in the memory and executable by the one or more processors to cause the apparatus to:

receive, from an access network entity, an indication that indicates that at least one component carrier is selected for the UE to use to transmit a beam-failure recovery request to the access network entity; and

transmit, based at least in part on the indication and using one or more component carriers of the at least one component carrier, the beam-failure recovery request to the access network entity.

9. The apparatus of claim 8 , wherein the indication of the at least one component carrier comprises an instruction to transmit the beam-failure recovery request for a single component carrier of the at least one component carrier.

10. The apparatus of claim 8 , wherein the indication of the at least one component carrier comprises an instruction to transmit the beam-failure recovery request for the at least one component carrier.

11. The apparatus of claim 8 , wherein the instructions to transmit the beam-failure recovery request to the access network entity are executable by the one or more processors to cause the apparatus to:

identify loss of beam synchronization for a single component carrier of the at least one component carrier; and

transmit the beam-failure recovery request for the single component carrier.

12. The apparatus of claim 8 , wherein the instructions to transmit the beam-failure recovery request to the access network entity are executable by the one or more processors to cause the apparatus to:

identify loss of beam synchronization for a single component carrier of the at least one component carrier; and

transmit the beam-failure recovery request for the at least one component carrier.

13. The apparatus of claim 8 , wherein the instructions are further executable by the one or more processors to cause the apparatus to:

receive, from the access network entity, a quasi co-location indication, the quasi co-location indication indicating a quasi co-location relationship among the at least one component carrier.

14. The apparatus of claim 8 , wherein the instructions are further executable by the one or more processors to cause the apparatus to:

monitor for beam failure of at least one component carrier for each group of component carriers of the at least one component carrier.

15. An apparatus for wireless communication at a user equipment (UE), comprising:

means for receiving, from an access network entity, an indication that indicates that at least one component carrier is selected for the UE to use to transmit a beam-failure recovery request to the access network entity; and

means for transmitting, based at least in part on the indication and using one or more component carriers of the at least one component carrier, the beam-failure recovery request to the access network entity.

16. The apparatus of claim 15 , wherein the indication of the at least one component carrier comprises an instruction to transmit the beam-failure recovery request for a single component carrier of the at least one component carrier.

17. The apparatus of claim 15 , wherein the indication of the at least one component carrier comprises an instruction to transmit the beam-failure recovery request for the at least one component carrier.

18. The apparatus of claim 15 , wherein the means for transmitting the beam-failure recovery request to the access network entity comprise:

means for identifying loss of beam synchronization for a single component carrier of the at least one component carrier; and

means for transmitting the beam-failure recovery request for the single component carrier.

19. The apparatus of claim 15 , wherein the means for transmitting the beam-failure recovery request to the access network entity comprise:

means for identifying loss of beam synchronization for a single component carrier of the at least one component carrier; and

means for transmitting the beam-failure recovery request for the at least one component carrier.

20. The apparatus of claim 15 , further comprising:

means for receiving, from the access network entity, a quasi co-location indication, the quasi co-location indication indicating a quasi co-location relationship among the at least one component carrier.

21. A non-transitory computer-readable medium storing code for wireless communication at a user equipment (UE), the code comprising instructions executable by a processor to:

receive, from an access network entity, an indication that indicates that at least one component carrier is selected for the UE to use to transmit a beam-failure recovery request to the access network entity; and

transmit, based at least in part on the indication and using one or more component carriers of the at least one component carrier, the beam-failure recovery request to the access network entity.

22. The non-transitory computer-readable medium of claim 21 , wherein the indication of the at least one component carrier comprises an instruction to transmit the beam-failure recovery request for a single component carrier of the at least one component carrier.

23. The non-transitory computer-readable medium of claim 21 , wherein the indication of the at least one component carrier comprises an instruction to transmit the beam-failure recovery request for the at least one component carrier.

24. The non-transitory computer-readable medium of claim 21 , wherein the instructions to transmit the beam-failure recovery request to the access network entity are executable by the processor to:

identify loss of beam synchronization for a single component carrier of the at least one component carrier; and

transmit the beam-failure recovery request for the single component carrier.

25. The non-transitory computer-readable medium of claim 21 , wherein the instructions to transmit the beam-failure recovery request to the access network entity are executable by the processor to:

identify loss of beam synchronization for a single component carrier of the at least one component carrier; and

transmit the beam-failure recovery request for the at least one component carrier.

26. The non-transitory computer-readable medium of claim 21 , wherein the instructions are further executable by the processor to:

receive, from the access network entity, a quasi co-location indication, the quasi co-location indication indicating a quasi co-location relationship among the at least one component carrier.

27. The method of claim 1 , further comprising:

initiating a stored timer based at least in part on one or more identified beam failures, wherein transmitting the beam-failure recovery request is based at least in part on the one or more identified beam failures.

28. The apparatus of claim 8 , wherein the instructions are further executable by the one or more processors to cause the apparatus to:

initiate a stored timer based at least in part on one or more identified beam failures, wherein transmitting the beam-failure recovery request is based at least in part on the one or more identified beam failures.

29. The apparatus of claim 15 , further comprising:

means for initiating a stored timer based at least in part on one or more identified beam failures, wherein transmitting the beam-failure recovery request is based at least in part on the one or more identified beam failures.

30. The non-transitory computer-readable medium of claim 21 , wherein the instructions are further executable by the processor to:

initiate a stored timer based at least in part on one or more identified beam failures, wherein transmitting the beam-failure recovery request is based at least in part on the one or more identified beam failures.

Assignments (3)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 14, 2023
From: AKKARAKARAN, SONY; LUO, TAO; JOHN WILSON, MAKESH PRAVIN; NAGARAJA, SUMEETH; WANG, XIAO FENG; CHAKRABORTY, KAUSHIK; NAM, WOOSEOK; CHEN, SHENGBO; MONTOJO, JUAN
To: QUALCOMM INCORPORATED
Reel/Frame 065556/0796 →
CORRECTIVE ASSIGNMENT TO CORRECT THE CORRECT EXECUTION DATE FOR SHENGBO CHEN PREVIOUSLY RECORDED AT REEL: 054912 FRAME: 0651. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Feb 12, 2021
From: AKKARAKARAN, SONY; LUO, TAO; JOHN WILSON, MAKESH PRAVIN; NAGARAJA, SUMEETH; WANG, XIAO FENG; NAM, WOOSEOK; CHEN, SHENGBO; MONTOJO, JUAN
To: QUALCOMM INCORPORATED
Reel/Frame 056391/0428 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 6, 2021
From: AKKARAKARAN, SONY; LUO, TAO; JOHN WILSON, MAKESH PRAVIN; NAGARAJA, SUMEETH; WANG, XIAO FENG; CHAKRABORTY, KAUSHIK; NAM, WOOSEOK; CHEN, SHENGBO; MONTOJO, JUAN
To: QUALCOMM INCORPORATED
Reel/Frame 054912/0651 →
Continuity (3)
Division 16046781 · Jul 26, 2018
Provisional Application 62538624 · Jul 28, 2017
Related Publication 20210127428A1 · Apr 29, 2021
References Cited (58)
US 9130698B2 · Khandekar et al. · 2015 [cited by applicant]
US 20100150092A1 · Aydin · 2010 [cited by examiner]
US 20100260136A1 · Fan et al. · 2010 [cited by applicant]
US 20100303039A1 · Zhang et al. · 2010 [cited by applicant]
US 20100322185A1 · Park et al. · 2010 [cited by applicant]
US 20110275374A1 · Narasimha et al. · 2011 [cited by applicant]
US 20120202501A1 · Morioka et al. · 2012 [cited by applicant]
US 20130010619A1 · Fong et al. · 2013 [cited by applicant]
US 20130010711A1 · Larsson et al. · 2013 [cited by applicant]
US 20130010964A1 · Fong · 2013 [cited by examiner]
US 20130258882A1 · Dinan · 2013 [cited by applicant]
US 20140269632A1 · Blankenship et al. · 2014 [cited by applicant]
US 20150036666A1 · Blankenship et al. · 2015 [cited by applicant]
US 20150071198A1 · Deng · 2015 [cited by applicant]
US 20150215829A1 · Chang et al. · 2015 [cited by applicant]
US 20150341132A1 · Hwang et al. · 2015 [cited by applicant]
US 20160135148A1 · Novlan et al. · 2016 [cited by applicant]
US 20160223639A1 · Davydov · 2016 [cited by examiner]
US 20160330740A1 · Uchino et al. · 2016 [cited by applicant]
US 20160359593A1 · Dai et al. · 2016 [cited by applicant]
US 20170231055A1 · Yadav et al. · 2017 [cited by applicant]
US 20180110066A1 · Luo · 2018 [cited by examiner]
US 20180234960A1 · Nagaraja · 2018 [cited by examiner]
US 20180270895A1 · Park · 2018 [cited by examiner]
US 20180288755A1 · Liu et al. · 2018 [cited by applicant]
US 20190037423A1 · Yu · 2019 [cited by examiner]
US 20190037604A1 · Akkarakaran et al. · 2019 [cited by applicant]
US 20190229777A1 · Guan · 2019 [cited by examiner]
US 20200068416A1 · Kang · 2020 [cited by examiner]
US 20200137801A1 · Chen · 2020 [cited by examiner]
US 20200187128A1 · Yao · 2020 [cited by examiner]
US 20220376769A1 · Xiong · 2022 [cited by examiner]
CN 109039408 · 2018 [cited by examiner]
CN 109121223 · 2019 [cited by examiner]
CN 113115324 · 2021 [cited by examiner]
EP 2418907A1 · 2012 [cited by applicant]
JP 2016171597A · 2016 [cited by applicant]
WO WO2010078365A1 · 2010 [cited by applicant]
WO WO2010115304A1 · 2010 [cited by applicant]
WO WO2010135706 · 2010 [cited by applicant]
WO WO2016160907A1 · 2016 [cited by applicant]
WO WO2018126363A1 · 2018 [cited by examiner]
WO WO2018202010A1 · 2018 [cited by examiner]
WO WO2018202332A1 · 2018 [cited by examiner]
WO WO2018220773A1 · 2018 [cited by examiner]
WO WO2018224013A1 · 2018 [cited by examiner]
WO WO2019128975A1 · 2019 [cited by examiner]
Huawei et al., “Cross-Carrier Beam Management”, 3GPP Draft, R1-1711410, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre, 650, Route Des Lucioles, F-06921 Sophia-Antipolis Cedex, France, vol. RAN WG1,… [cited by applicant]
Intel Corporation: “Cross-carrier QCL for NR”, 3GPP Draft, R1-1704738, RAN WG1, Spokane, USA, Apr. 2, 2017, XP051242876, 2 Pages, Retrieved from the Internet: URL: http://www.3gpp.org/ftp/Meetings_3GPP_SYNC/RAN1/Docs/. … [cited by applicant]
Alcatel-Lucent Shanghai Bell, et al., “SR Transmissions on SCell PUCCH”, 3GPP TSG-RAN WG2 Meeting #89bis, R2-151469, 3rd Generation Partnership Project, Mobile Competence Centre, 650, Route Des Lucioles, F-06921 Sophia-… [cited by applicant]
European Search Report—EP23174707—Search Authority—The Hague—dated Aug. 23, 2023. [cited by applicant]
Huawei, et al., “RAN2 Aspects of DL Beam Management”, 3GPP TSG-RAN WG2 Meeting NR#2, R2-1706718, 3rd Generation Partnership Project, Mobile Competence Centre, 650, Route Des Lucioles, F-06921 Sophia-Antipolis Cedex, Fra… [cited by applicant]
Qualcomm Incorporated: “Beam Recovery Request”, 3GPP TSG-RAN WG2 Meeting NR ad-hoc, R2-1706926, 3rd Generation Partnership Project, Mobile Competence Centre, 650, Route Des Lucioles, F-06921 Sophia-Antipolis Cedex, Fran… [cited by applicant]
Alcatel-Lucent., et al., “DL-UL Linking with Non-Contention RACH and UL Grant Assignment”, 3GPP Draft; R2-102366, Dedicated Preamble_06, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre; 650, Route De… [cited by applicant]
Huawei: “Random Access with Asymmetric Carrier Aggregation”, 3GPP Draft; R2-102151 Random Access with Asymmetric Carrier Aggregation, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre ; 650, Route Des … [cited by applicant]
International Preliminary Report on Patentability—PCT/US2018/044194, The International Bureau of WIPO—Geneva, Switzerland, dated Feb. 6, 2020. [cited by applicant]
International Search Report and Written Opinion—PCT/US2018/044194—ISA/EPO—dated Nov. 30, 2018. [cited by applicant]
Partial International Search Report—PCT/US2018/044194—ISA/EPO—dated Oct. 9, 2018. [cited by applicant]
Cited By (1)
US 12,581,539