IP Library › Granted Patent US 12,342,380
Granted Patent B2
US 12,342,380 · App. 17/135,019 · Granted Jun 24, 2025

Determination of contention resolution timer

Inventors: Samuli Turtinen (Ii, FI); Chunli Wu (Beijing, CN)
Assignee: Nokia Technologies Oy
H04W74/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,342,380
App. No.
17/135,019
Granted
Jun 24, 2025
Kind
B2
Abstract

Example embodiments of the present disclosure relate to a solution for determining a contention resolution timer. In an aspect, a first device receives, from a second device, an indication to perform Msg3 transmission. The first device transmits, to the second device, information of the first device for contention resolution. In case a configuration of a 4-step random access channel is unavailable in an active bandwidth part for the first device, the first device determines a duration for monitoring a contention resolution message based on one of: a first configuration of a 2-step random access channel in the active bandwidth part, or a second configuration of a 4-step random access channel in a bandwidth part different from the active bandwidth part. Example embodiments of the present disclosure can improve the performance of a random access procedure.

Claims (64)

1. A first device comprising:

at least one processor; and

at least one memory storing instructions that, when executed with the at least one processor, cause the first device at least to:

transmit, to a second device, at least one message according to a first configuration of a 2-step random access channel in an active bandwidth part;

receive, from the second device in response to the at least one message, an indication to perform Msg3 transmission;

transmit, to the second device via Msg3, information of the first device for contention resolution;

based on a determination that a configuration of a 4-step random access channel is not configured in the active bandwidth part for the first device, determine a duration for monitoring for a contention resolution message based on one of:

the first configuration of the 2-step random access channel in the active bandwidth part, or

a second configuration of a 4-step random access channel in a bandwidth part that is different from the active bandwidth part; and

based on a determination that the first configuration indicates a contention resolution timer, determine the duration as a time length of the contention resolution timer,

wherein the first configuration indicates the contention resolution timer when the configuration of the 4-step random access channel is not configured in the active bandwidth part for the first device, and does not indicate the contention resolution timer when the configuration of the 4-step random access channel is configured in the active bandwidth part for the first device.

2. The first device of claim 1 , wherein the at least one memory stores instructions that, when executed with the at least one processor, cause the first device to:

based on a determination that the first configuration does not indicate the contention resolution timer, determine the duration as a time length of a contention resolution timer indicated in the second configuration.

3. The first device of claim 1 , wherein the active bandwidth part comprises one of the following:

an initial bandwidth part for the first device,

a default bandwidth part for the first device,

a first active bandwidth part for the first device, or

a predetermined bandwidth part indicated by the second device.

4. The first device of claim 1 , wherein the at least one memory stores instructions that, when executed with the at least one processor, cause the first device to:

based on a determination that the first configuration does not indicate the contention resolution timer, determine the duration as a time length for monitoring a MSGB from the second device, wherein the MSGB comprises a message transmitted by the second device in response to a MSGA transmitted over the 2-step random access channel, wherein the at least one message comprises, at least, the MSGA.

5. The first device of claim 4 , wherein the time length for monitoring the MSGB is a time length of an MSGB response window.

6. The first device of claim 1 , wherein the at least one memory stores instructions that, when executed with the at least one processor, cause the first device to:

receive the first configuration or the second configuration from the second device.

7. The first device of claim 1 , wherein the first device comprises a terminal device, and the second device comprises a network device.

8. The first device of claim 1 , wherein the contention resolution message comprises a contention resolution message in response to the information of the first device transmitted via Msg3, wherein the at least one memory stores instructions that, when executed with the at least one processor, cause the first device to:

monitor for the contention resolution message, in the active bandwidth part and according to the first configuration, for the determined duration.

9. A second device comprising:

at least one processor; and

at least one memory storing instructions that, when executed with the at least one processor, cause the second device to:

receive, from a first device, at least one message according to a first configuration of a 2-step random access channel in an active bandwidth part;

transmit, to the first device in response to the at least one message, an indication to perform Msg3 transmission;

based on a determination that a configuration of a 4-step random access channel is not configured in the active bandwidth part for the first device, determine a duration for transmitting a contention resolution message to the first device based on one of:

the first configuration of the 2-step random access channel in the active bandwidth part, or

a second configuration of a 4-step random access channel in a bandwidth part that is different from the active bandwidth part;

based on a determination that the first configuration indicates the contention resolution timer, determine the duration as a time length of the contention resolution timer; and

based on a determination that information of the first device for contention resolution is received from the first device via Msg3, transmit the contention resolution message to the first device within the duration,

wherein the first configuration indicates the contention resolution timer when the configuration of the 4-step random access channel is not configured in the active bandwidth part for the first device, and does not indicate the contention resolution timer when the configuration of the 4-step random access channel is configured in the active bandwidth part for the first device.

10. The second device of claim 9 , wherein the at least one memory stores instructions that, when executed with the at least one processor, cause the second device to:

based on a determination the first configuration does not indicate the contention resolution timer, determine the duration as a time length of a contention resolution timer indicated in the second configuration.

11. The second device of claim 9 , wherein the active bandwidth part comprises one of the following:

an initial bandwidth part for the first device,

a default bandwidth part for the first device,

a first active bandwidth part for the first device, or

a predetermined bandwidth part indicated by the second device.

12. The second device of claim 9 , wherein the at least one memory stores instructions that, when executed with the at least one processor, cause the second device to:

based on a determination that the first configuration does not indicate the contention resolution timer, determine the duration as a time length for the first device to monitor a MSGB from the second device, wherein the MSGB comprises a message transmitted by the second device in response to a MSGA transmitted over the 2-step random access channel, wherein the at least one message comprises, at least, the MSGA.

13. The second device of claim 12 , wherein the time length for monitoring the MSGB is a time length of an MSGB response window.

14. The second device of claim 9 , wherein the at least one memory stores instructions that, when executed with the at least one processor, cause the second device to:

determine the first configuration or the second configuration; and

transmit the first configuration or the second configuration to the first device.

15. The second device of claim 14 , wherein the at least one memory stores instructions that, when executed with the at least one processor, cause the second device to:

based on a determination that the configuration of the 4-step random access channel is not configured in the active bandwidth part, cause the first configuration to indicate the contention resolution timer for the active bandwidth part.

16. The second device of claim 14 , wherein the at least one memory stores instructions that, when executed with the at least one processor, cause the second device to:

cause the first configuration to indicate the contention resolution timer for the active bandwidth part.

17. The second device of claim 9 , wherein the first device comprises a terminal device, and the second device comprises a network device.

18. A method comprising:

transmitting, with a first device to a second device, at least one message according to a first configuration of a 2-step random access channel in an active bandwidth part;

receiving, from the second device in response to the at least one message, an indication to perform Msg3 transmission;

transmitting, to the second device via Msg3, information of the first device for contention resolution; and

based on a determination that a configuration of a 4-step random access channel is not configured in the active bandwidth part for the first device, determining a duration for monitoring for a contention resolution message based on one of:

the first configuration of the 2-step random access channel in the active bandwidth part, or

a second configuration of a 4-step random access channel in a bandwidth part that is different from the active bandwidth part; and

based on a determination that the first configuration indicates a contention resolution timer, determining the duration as a time length of the contention resolution timer,

wherein the first configuration indicates the contention resolution timer when the configuration of the 4-step random access channel is not configured in the active bandwidth part for the first device, and does not indicate the contention resolution timer when the configuration of the 4-step random access channel is configured in the active bandwidth part for the first device.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 4, 2021
From: TURTINEN, SAMULI; WU, CHUNLI
To: NOKIA TECHNOLOGIES OY
Reel/Frame 057684/0402 →
Priority Claims (1)
WO PCT/CN2020/076188 · Feb 21, 2020 · international
Continuity (1)
Related Publication 20210266971A1 · Aug 26, 2021
References Cited (34)
US 20140376425A1 · Han et al. · 2014 [cited by applicant]
US 20180199381A1 · Rong et al. · 2018 [cited by applicant]
US 20190387541A1 · Agiwal et al. · 2019 [cited by applicant]
US 20200053779A1 · Jeon · 2020 [cited by examiner]
US 20200107369A1 · Jeon · 2020 [cited by examiner]
US 20200221506A1 · Jeon · 2020 [cited by examiner]
US 20220287080A1 · Liu · 2022 [cited by examiner]
US 20220287107A1 · Kim · 2022 [cited by examiner]
CN 110312312A · 2019 [cited by applicant]
CN 110536403A · 2019 [cited by applicant]
CN 110771248A · 2020 [cited by applicant]
WO 2016116065A1 · 2016 [cited by applicant]
WO 2018062925A1 · 2018 [cited by applicant]
WO WO2018085726A1 · 2018 [cited by applicant]
WO WO2019245779A1 · 2019 [cited by examiner]
WO 2020034319A1 · 2020 [cited by applicant]
WO WO2020167083A1 · 2020 [cited by examiner]
Motorola Mobility NPL “Physical channel design for 2-step RACH”, 3GPP R1-1800727, Jan. 22-26, 2018 (Year: 2018). [cited by examiner]
Apple “Open issues on 2-step RACH”, 3GPP R2-2000586, Feb. 24, 2020 (Year: 2020). [cited by examiner]
CATT “Consideration on 2-step RA”, 3GPP R2-1700205, Jan. 17-19, 2017 (Year: 2017). [cited by examiner]
Samsung “Handling PDCCH Order Initiated CFRA”, 3GPP R2-2000220, Feb. 24-28, 2020 (Year: 2020). [cited by examiner]
Apple “Open issues on 2-step RACH”, 3GPP R2-2000586, Feb. 24-Mar. 6, 2020, available for retrieval from the internet on Feb. 13, 2020 (Year: 2020). [cited by examiner]
Motorola Mobility “Physical channel design for 2-step RACH”, 3GPP R1-1800727, Jan. 22-26, 2018 (Year: 2018). [cited by examiner]
“Revised work item proposal: 2-step RACH for NR”, 3GPP TSG RAN Meeting #83, RP-190711, Agenda: 9.4.7, ZTE Corporation, Mar. 18-21, 2019, 4 pages. [cited by applicant]
“Remaining stage-2 open issues for 2-step RACH”, 3GPP TSG-RAN WG2 Meeting #107bis, R2-190xxxx, Agenda: 11.13.5, OPPO, Oct. 14-18, 2019, pp. 1-4. [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Medium Access Control (MAC) protocol specification (Release 15)”, 3GPP TS 38.321, V15.8.0, Dec. 2019, pp. 1-78. [cited by applicant]
International Search Report and Written Opinion received for corresponding Patent Cooperation Treaty Application No. PCT/CN2020/076188, dated Nov. 17, 2020, 9 pages. [cited by applicant]
“2 step and 4 step RACH”, 3GPP TSG-RAN WG1 #87, R1-1612033, Agenda: 7.1.2.4, Qualcomm Incorporated, Nov. 14-18, 2016, 3 pages. [cited by applicant]
“Physical channel design for 2-step RACH”, 3GPP TSG RAN WG1 Meeting AH 1801, R1-1800727, Agenda: 7.1.4.1, Motorola Mobility, Jan. 22-26, 2018, pp. 1-4. [cited by applicant]
Office action received for corresponding Finnish Patent Application No. 20206296, dated Jun. 11, 2021, 6 pages. [cited by applicant]
“Consideration on 2-step RA”, 3GPP TSG RAN WG2 Meeting Ad Hoc, R2-1700205, Agenda Item: 3.2.1.4, CATT, Jan. 17-19, 2017, 6 pages. [cited by applicant]
“Configuration of 2-step RA”, Ericsson, 3GPP TSG-RAN WG2 RAN2#107bis, R2-1912680, Oct. 2019, 8 pages. [cited by applicant]
“Open Issues on 2-step RACH”, Apple, 3GPP TSG-RAN WG2 Meeting #109 electronic, R2-2000586, Mar. 2020, 3 pages. [cited by applicant]
“Handling PDCCH Order Initiated CFRA”, Samsung, 3GPP TSG-RAN WG2 Meeting #109, R2-2000220, Feb. 2020, 5 pages. [cited by applicant]