IP Library › Granted Patent US 12,501,481
Granted Patent B2
US 12,501,481 · App. 17/945,285 · Granted Dec 16, 2025

Random access procedures using repetition

Inventors: Nazanin Rastegardoost (McLean, VA); Esmael Hejazi Dinan (McLean, VA); Hyoungsuk Jeon (Centreville, VA); Yunjung Yi (Vienna, VA)
Assignee: Comcast Cable Communications, LLC
H04W74/006H04B17/318H04L5/0051H04L5/10H04W72/23H04W74/0833H04W74/0836H04W74/0838
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,501,481
App. No.
17/945,285
Granted
Dec 16, 2025
Kind
B2
Abstract

Wireless communications may be used for repetition of one or more transmissions. At least some wireless devices may use and/or require different quantities of repetitions of one or more transmissions based on one or more factors such as received signal strength and/or other channel condition(s). The quantity of repetitions may be less than or equal to a maximum quantity of repetitions that may be indicated by a base station.

Claims (82)

1 . A method comprising:

receiving, by a wireless device, an indication of an allowable quantity of repetitions for a physical uplink shared channel (PUSCH) transmission comprising at least one transport block, wherein the PUSCH transmission is associated with a random access preamble of a random access procedure; and

sending repetitions of the PUSCH transmission, wherein a quantity of the repetitions is determined based on a received signal strength of a downlink reference signal and is less than or equal to the allowable quantity of repetitions.

2 . The method of claim 1 , further comprising:

receiving, in response to the PUSCH transmission, a random access response that indicates at least one of:

a success of the random access procedure;

a failure of the random access procedure;

a fallback from a two-step random access procedure to a four-step random access procedure; or

an uplink grant.

3 . The method of claim 1 , wherein the allowable quantity of repetitions is a maximum quantity of allowed repetitions.

4 . The method of claim 1 , further comprising:

determining a physical random access channel (PRACH) occasion associated with the downlink reference signal; and

transmitting, via the PRACH occasion, the random access preamble.

5 . The method of claim 1 , further comprising:

receiving configuration parameters of a plurality of PUSCH resources for the random access preamble, wherein the sending the quantity of repetitions of the PUSCH transmission comprises sending the quantity of repetitions of the PUSCH transmission via at least one PUSCH resource of the plurality of PUSCH resources.

6 . The method of claim 5 , wherein each of the at least one PUSCH resource comprises:

at least one frequency resource;

at least one time resource; and

at least one demodulation reference signal (DM-RS) resource.

7 . The method of claim 5 , further comprising:

based on not receiving at least one random access response within a time period, transmitting the PUSCH transmission via at least one second PUSCH resource of the plurality of PUSCH resources.

8 . A method comprising:

sending, by a base station, an indication of an allowable quantity of repetitions for a physical uplink shared channel (PUSCH) transmission comprising at least one transport block, wherein the PUSCH transmission is associated with a random access preamble of a random access procedure; and

receiving, by the base station, repetitions of the PUSCH transmission, wherein a quantity of the repetitions is determined based on a received signal strength of a downlink reference signal and is less than or equal to the allowable quantity of repetitions.

9 . The method of claim 8 , further comprising:

sending, in response to the PUSCH transmission, a random access response that indicates at least one of:

a success of the random access procedure;

a failure of the random access procedure;

a fallback from a two-step random access procedure to a four-step random access procedure; or

an uplink grant.

10 . The method of claim 8 , wherein the allowable quantity of repetitions is a maximum quantity of allowed repetitions.

11 . The method of claim 9 , further comprising:

receiving, via a physical random access channel (PRACH) occasion associated with the downlink reference signal, the random access preamble.

12 . The method of claim 8 , further comprising:

sending configuration parameters of a plurality of PUSCH resources for the random access preamble, wherein the receiving the quantity of repetitions of the PUSCH transmission comprises receiving the quantity of repetitions of the PUSCH transmission via at least one PUSCH resource of the plurality of PUSCH resources.

13 . The method of claim 12 , wherein each of the at least one PUSCH resource comprises:

at least one frequency resource;

at least one time resource; and

at least one demodulation reference signal (DM-RS) resource.

14 . The method of claim 12 , further comprising:

based on not sending at least one random access response within a time period, receiving the PUSCH transmission via at least one second PUSCH resource of the plurality of PUSCH resources.

15 . A wireless device comprising:

one or more processors; and

memory storing instructions that, when executed by the one or more processors, cause the wireless device to:

receive an indication of an allowable quantity of repetitions for a physical uplink shared channel (PUSCH) transmission comprising at least one transport block, wherein the PUSCH transmission is associated with a random access preamble of a random access procedure; and

send repetitions of the PUSCH transmission, wherein a quantity of the repetitions is determined based on a received signal strength of a downlink reference signal and is less than or equal to the allowable quantity of repetitions.

16 . The wireless device of claim 15 , wherein the instructions, when executed by the one or more processors, cause the wireless device to receive, in response to the PUSCH transmission, a random access response that indicates at least one of:

a success of the random access procedure;

a failure of the random access procedure;

a fallback from a two-step random access procedure to a four-step random access procedure; or

an uplink grant.

17 . The wireless device of claim 15 , wherein the allowable quantity of repetitions is a maximum quantity of allowed repetitions.

18 . The wireless device of claim 15 , wherein the instructions, when executed by the one or more processors, cause the wireless device to:

determine a physical random access channel (PRACH) occasion associated with the downlink reference signal; and

transmit, via the PRACH occasion, the random access preamble.

19 . The wireless device of claim 15 , wherein the instructions, when executed by the one or more processors, cause the wireless device to receive configuration parameters of a plurality of PUSCH resources for the random access preamble, the sending the quantity of repetitions of the PUSCH transmission comprises sending the quantity of repetitions of the PUSCH transmission via at least one PUSCH resource of the plurality of PUSCH resources.

20 . The wireless device of claim 19 , wherein each of the at least one PUSCH resource comprises:

at least one frequency resource;

at least one time resource; and

at least one demodulation reference signal (DM-RS) resource.

21 . The wireless device of claim 19 , wherein the instructions, when executed by the one or more processors, cause the wireless device to:

based on not receiving at least one random access response within a time period, transmit the PUSCH transmission via at least one second PUSCH resource of the plurality of PUSCH resources.

22 . A base station comprising:

one or more processors; and

memory storing instructions that, when executed by the one or more processors, cause the base station to:

send an indication of an allowable quantity of repetitions for a physical uplink shared channel (PUSCH) transmission comprising at least one transport block, wherein the PUSCH transmission is associated with a random access preamble of a random access procedure; and

receive repetitions of the PUSCH transmission, wherein a quantity of the repetitions is determined based on a received signal strength of a downlink reference signal and is less than or equal to the allowable quantity of repetitions.

23 . The base station of claim 22 , wherein the instructions, when executed by the one or more processors, cause the base station to:

send, in response to the PUSCH transmission, a random access response that indicates at least one of:

a success of the random access procedure;

a failure of the random access procedure;

a fallback from a two-step random access procedure to a four-step random access procedure; or

an uplink grant.

24 . The base station of claim 22 , wherein the allowable quantity of repetitions is a maximum quantity of allowed repetitions.

25 . The base station of claim 22 , wherein the instructions, when executed by the one or more processors, cause the base station to receive, via a physical random access channel (PRACH) occasion associated with the downlink reference signal, the random access preamble.

26 . The base station of claim 22 , wherein the instructions, when executed by the one or more processors, cause the base station to send configuration parameters of a plurality of PUSCH resources for the random access preamble, wherein the receiving the quantity of repetitions of the PUSCH transmission comprises receiving the quantity of repetitions of the PUSCH transmission via at least one PUSCH resource of the plurality of PUSCH resources.

27 . The base station of claim 26 , wherein each of the at least one PUSCH resource comprises:

at least one frequency resource;

at least one time resource; and

at least one demodulation reference signal (DM-RS) resource.

28 . The base station of claim 26 , wherein the instructions, when executed by the one or more processors, cause the base station to:

based on not sending at least one random access response within a time period, receiving the PUSCH transmission via at least one second PUSCH resource of the plurality of PUSCH resources.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 1, 2024
From: RASTEGARDOOST, NAZANIN; DINAN, ESMAEL HEJAZI; JEON, HYOUNGSUK; YI, YUNJUNG
To: COMCAST CABLE COMMUNICATIONS, LLC
Reel/Frame 067888/0284 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 1, 2024
From: RASTEGARDOOST, NAZANIN; DINAN, ESMAEL HEJAZI; JEON, HYOUNGSUK; YI, YUNJUNG
To: COMCAST CABLE COMMUNICATIONS, LLC
Reel/Frame 067888/0335 →
Continuity (3)
Continuation 16993546 · Aug 14, 2020
Provisional Application 62888069 · Aug 16, 2019
Related Publication 20230069881A1 · Mar 9, 2023
References Cited (43)
US 20100074130A1 · Bertrand et al. · 2010 [cited by applicant]
US 20160270038A1 · Papasakellariou · 2016 [cited by applicant]
US 20180324716A1 · Jeon et al. · 2018 [cited by applicant]
US 20190132882A1 · Li et al. · 2019 [cited by applicant]
US 20200092777A1 · Agiwal et al. · 2020 [cited by applicant]
GB 2544317A · 2017 [cited by applicant]
KR 20200054086A · 2020 [cited by applicant]
WO WO2016025899A1 · 2016 [cited by examiner]
WO 2018031620A1 · 2018 [cited by applicant]
WO 2020032745A1 · 2020 [cited by applicant]
WO 2020033660A1 · 2020 [cited by applicant]
WO WO2020060371A1 · 2020 [cited by examiner]
WO WO2020076953A1 · 2020 [cited by examiner]
WO 2020167794A1 · 2020 [cited by applicant]
Interdigital Inc: “Discussion on Procedures for Two-Step RACH”, 3GPP Draft; R1-1904850 Discussion on Procedures for Twostep Rach, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre ; 650, Route Des Luci… [cited by applicant]
Dec. 9, 2020—European Search Report—EP 20191064.3. [cited by applicant]
3GPP TS 36.321 V15.4.0 (Dec. 2018), Technical Specification, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Con… [cited by applicant]
3GPP TS 36.331 V15.4.0 (Dec. 2018), Technical Specification, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Co… [cited by applicant]
3GPP TSG RAN WG1 Meeting #96bis, Xi'an, China, Apr. 8-12, 2019, Title: RAN1 Chairman's Notes. [cited by applicant]
R1-1905793 3GPP TSG RAN WG1 Meeting #96bis, Xi'an, China, Apr. 8-12, 2019, Source: ZTE, Title: Updated summary of 7.2.1.1 Channel Structure for Two-step RACH. [cited by applicant]
3GPP TS 38.212 V15.6.0 (Jun. 2019), 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Multiplexing and channel coding (Release 15). [cited by applicant]
3GPP TS 38.213 V15.6.0 (Jun. 2019), Technical Specification, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical layer procedures for control (Release 15). [cited by applicant]
3GPP TS 38.214 V15.6.0 (Jun. 2019), Technical Specification, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical layer procedures for data (Release 15). [cited by applicant]
3GPP TS 38.321 V15.6.0 (Jun. 2019), Technical Specification, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Medium Access Control (MAC) protocol specification (Release 15). [cited by applicant]
3GPP TS 38.331 V15.6.0 (Jun. 2019), Technical Specification, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Radio Resource Control (RRC) protocol specification (Release 15). [cited by applicant]
3GPP TSG RAN WG1 Meeting #97, Reno, USA, May 13-17, 2019, Title: RAN1 Chairman's Notes. [cited by applicant]
R1-1905989 3GPP TSG RAN WG1 Meeting #97, Reno, USA, May 13-17, 2019, Source: ZTE, Sanechips, Title: Further discussions on the channel structure of msgA. [cited by applicant]
R1-1905990 3GPP TSG RAN WG1 Meeting #97, Reno, USA, May 13-17, 2019, Source: ZTE, Sanechips, Title: Further discussions on 2-step RACH procedures. [cited by applicant]
R1-1906050 3GPP TSG RAN WG1 Meeting #97, Reno, USA, May 13-17, 2019, Source: Huawei, HiSilicon, Title: Discussion on channel structure of 2-step RACH. [cited by applicant]
R1-1906124 3GPP TSG RAN WG1 Meeting #97, Reno, USA, May 13-17, 2019, Source: vivo, Title: Discussion on channel structure of 2-step RACH. [cited by applicant]
R1-1906192 3GPP TSG RAN WG1 #97, Reno, USA, May 13-17, 2019, Source: NITT DOCOMO, Inc., Title: Discussion on Channel Structure of Two-Step RACH. [cited by applicant]
R1-1906366 3GPP TSG RAN WG1 Meeting #97, Reno, USA, May 13-17, 2019, Source: Spreadtrum communications Title: Considerations on the channel structure of 2-step RACH. [cited by applicant]
R1-1906747 3GPP TSG RAN WG1 #97, Reno, USA, May 13-17, 2019, Source: Nokia, Nokia Shanghai Bell, Title: On 2-step RACH Procedure. [cited by applicant]
R1-1906779 3GPP TSG RAN WG1 #97, Reno, USA, May 13-17, 2019, Source: Intel Corporation, Title: Discussion on channel structure for 2-step RACH. [cited by applicant]
R1-1906858 3GPP TSG RAN WG1 Meeting #97, Reno, USA, May 13-17, 2019, Source: InterDigital Inc. Title: On preamble and PUSCH mapping. [cited by applicant]
R1-1907196 3GPP TSG RAN WG1 Meeting #97, Reno, USA, May 13-17, 2019, Source: CAICT, Title: Considerations on Channel Structure for Two-step RACH. [cited by applicant]
R1-1907255 3GPP TSG RAN WG1 Meeting #97, Reno, USA, May 13-17, 2019, Source: Qualcomm Incorporated, Title: Channel Structure for Two-step RACH. [cited by applicant]
R1-1907256 3GPP TSG RAN WG1 Meeting #97, Reno, USA, May 13-17, 2019, Source: Qualcomm Incorporated, Title: Procedures for Two-step RACH. [cited by applicant]
R1-1907830 3GPP TSG RAN WG1 #97, Reno, USA, May 13-17, 2019, Source: ZTE, Title: Feature Lead Summary #2 of 7.2.1.1 Two-step RACH Channel Structure. [cited by applicant]
3GPP TSG RAN WG2 Meeting #105bis, Xi'an, China, Apr. 8-12, 2019, Source: RAN2 Chairman (Intel), Title: Chair notes. [cited by applicant]
3GPP TSG RAN WG2 Meeting #106, Reno, USA, May 13-17, 2019, Source: RAN2 Chairman (Intel), Title: Chair notes. [cited by applicant]
RP-190xxx 3GPP TSG RAN Meeting #84, Newport Beach, USA, Jun. 3-6, 2019, Source: ZTW Corporation, Title: Status Report to TSG. [cited by applicant]
Jan. 16, 2023—EP Office Action—EP App No. 20191064.3. [cited by applicant]