Granted Patent B2

US 12,506,584 · App. 17/068,585 · Granted Dec 23, 2025

Inventors: Yisheng Xue (San Diego, CA); Jing Sun (San Diego, CA); Xiaoxia Zhang (San Diego, CA); Jing Lei (San Diego, CA)

Assignee: Qualcomm Incorporated

H04L5/14H04W74/0833H04W74/0836

Abstract

Claims (101)

1 . A method of wireless communication, comprising:

receiving, at a user equipment (UE) from a base station (BS), a first configuration of a first random-access channel (RACH) occasion or a first physical uplink shared channel (PUSCH) occasion for a first RACH procedure and a second configuration of a second RACH occasion for a second RACH procedure;

determining whether the first PUSCH occasion is valid depending at least in part on whether the first PUSCH occasion collides with the first RACH occasion or the second RACH occasion, wherein the determining comprises:

determining that the first PUSCH occasion is invalid when the first PUSCH occasion overlaps with the first RACH occasion or the second RACH occasion in time and frequency for more than a threshold ratio portion of the first RACH occasion or the second RACH occasion;

excluding the first PUSCH occasion from a resource pool for a 2-step RACH procedure in response to determining that the first PUSCH occasion is invalid; and

transmitting, to the BS, a first RACH message using available PUSCH occasions and available RACH occasions, wherein the available PUSCH occasions are selected from the resource pool that does not contain the excluded first PUSCH occasions.

2 . The method of claim 1 , wherein the determining whether the first PUSCH occasion or the first RACH occasion is valid comprises:

validating the first PUSCH occasion with a synchronization signal block (SSB) and a downlink pattern defined in a time division duplexing (TDD) mode.

3 . The method of claim 1 , wherein the determining whether the first PUSCH occasion or the first RACH occasion is valid further comprises:

determining that the first PUSCH occasion is valid in response to determining that an overlapping area between the first PUSCH occasion and the first RACH occasion or the second RACH occasion is smaller than the threshold ratio portion of the first RACH occasion or the second RACH occasion.

4 . The method of claim 1 , further comprising:

determining that the first PUSCH occasion is invalid; and

excluding the first PUSCH occasion when associating a synchronization signal block (SSB) with PUSCH occasions and RACH occasions for the first RACH procedure.

5 . The method of claim 1 , further comprising:

determining that the first PUSCH occasion or the first RACH occasion is valid;

associating a first SSB with the first PUSCH occasion;

associating a second SSB with the first RACH occasion;

associating the first PUSCH occasion and the first RACH occasion according to an association rule defined by a network, in response to determining that the first SSB and the second SSB are a same SSB;

excluding the first PUSCH occasion or the first RACH occasion from a RACH resource pool in response to determining that the first SSB and the second SSB are different.

6 . The method of claim 1 , further comprising:

associating a first SSB with the first PUSCH occasion;

associating a second SSB with the first RACH occasion;

associating the first PUSCH occasion and the first RACH occasion according to an association rule defined by a network, in response to determining that the first SSB and the second SSB are a same SSB;

determining that the first PUSCH occasion or the first RACH occasion is invalid; and

re-associating the first SSB or the second SSB with a valid PUSCH occasion and a valid RACH occasion selected from a RACH resource pool.

7 . The method of claim 1 , further comprising:

receiving, from the BS, an update including a change in RACH configuration parameters; and

re-validating the first RACH occasion or the first PUSCH occasion according to the change in RACH configuration parameters.

8 . The method of claim 1 , wherein the determining whether the first PUSCH occasion or the first RACH occasion is valid comprises:

determining that the first PUSCH occasion collides with the first RACH occasion or the second RACH occasion;

determining that the first PUSCH occasion is associated with a first SSB, and the first RACH occasion or the second RACH occasion that collides with the first PUSCH is associated with a second SSB; and

determining that the first PUSCH occasion is valid in response to determining that the first SSB is different from the second SSB.

9 . The method of claim 1 , wherein the first RACH procedure is a 2-step RACH procedure, and the second RACH procedure is a 4-step RACH procedure.

10 . A user equipment (UE) of wireless communication, comprising:

a transceiver configured to:

receive, from a base station (BS), a first configuration of a first random-access channel (RACH) occasion or a first physical uplink shared channel (PUSCH) occasion for a first RACH procedure and a second configuration of a second RACH occasion for a second RACH procedure;

a processor configured to:

determine whether the first PUSCH occasion is valid depending at least in part on whether the first PUSCH occasion collides with the first RACH occasion or the second RACH occasion, wherein the determining comprises:

determining that the first PUSCH occasion is invalid when the first PUSCH occasion overlaps with the first RACH occasion or the second RACH occasion in time and frequency for more than a threshold ratio portion of the first RACH occasion or the second RACH occasion;

exclude the first PUSCH occasion from a resource pool in response to determining that the first PUSCH occasion is invalid; and

wherein the transceiver is configured to transmit to the BS, a first RACH message using available PUSCH occasions and available RACH occasions selected from the resource pool that does not contain the excluded first PUSCH occasions.

11 . The UE of claim 10 , wherein the processor is configured to determine whether the first PUSCH occasion or the first RACH occasion is valid by:

validating the first PUSCH occasion with a synchronization signal block (SSB) and a downlink pattern defined in a time division duplexing (TDD) mode.

12 . The UE of claim 10 , wherein the processor is configured to determine whether the first PUSCH occasion or the first RACH occasion is valid by:

determining that the first PUSCH occasion is valid in response to determining that an overlapping area between the first PUSCH occasion and the first RACH occasion or the second RACH occasion is smaller than the threshold ratio portion of the first RACH occasion or the second RACH occasion.

13 . The UE of claim 10 , wherein the processor is further configured to:

determining that the first PUSCH occasion is invalid; and

excluding the first PUSCH occasion when associating a synchronization signal block (SSB) with PUSCH occasions and RACH occasions for the first RACH procedure.

14 . The UE of claim 10 , wherein the processor is further configured to:

determine that the first PUSCH occasion or the first RACH occasion is valid;

associate a first SSB with the first PUSCH occasion;

associate a second SSB with the first RACH occasion;

associate the first PUSCH occasion and the first RACH occasion according to an association rule defined by a network, in response to determining that the first SSB and the second SSB are a same SSB; and

exclude the first PUSCH occasion or the first RACH occasion from a RACH resource pool in response to determining that the first SSB and the second SSB are different.

15 . The UE of claim 10 , wherein the processor is further configured to:

associate a first SSB with the first PUSCH occasion;

associate a second SSB with the first RACH occasion;

associate the first PUSCH occasion and the first RACH occasion according to an association rule defined by a network, in response to determining that the first SSB and the second SSB are a same SSB;

determine that the first PUSCH occasion or the first RACH occasion is invalid; and

re-associate the first SSB or the second SSB with a valid PUSCH occasion and a valid RACH occasion selected from a RACH resource pool.

16 . The UE of claim 10 , wherein the processor is further configured to:

receive, from the BS, an update including a change in RACH configuration parameters; and

re-validate the first RACH occasion or the first PUSCH occasion according to the change in RACH configuration parameters.

17 . The UE of claim 10 , wherein the processor is further configured to determine whether the first PUSCH occasion or the first RACH occasion is valid by:

determining that the first PUSCH occasion collides with the first RACH occasion or the second RACH occasion;

determining that the first PUSCH occasion is associated with a first SSB, and the first RACH occasion or the second RACH occasion that collides with the first PUSCH is associated with a second SSB; and

determining that the first PUSCH occasion is valid in response to determining that the first SSB is different from the second SSB.

18 . The UE of claim 10 , wherein the first RACH procedure is a 2-step RACH procedure, and the second RACH procedure is a 4-step RACH procedure.

19 . A processor-readable non-transitory storage medium storing processor-executable instructions for a user equipment (UR) of wireless communication, the instructions being executable by a processor to perform operations comprising:

receiving, at a user equipment (UE) from a base station (BS), a first configuration of a first random-access channel (RACH) occasion or a first physical uplink shared channel (PUSCH) occasion for a first RACH procedure and a second configuration of a second RACH occasion for a second RACH procedure;

determining whether the first PUSCH occasion is valid depending at least in part on whether the first PUSCH occasion collides with the first RACH occasion or the second RACH occasion, wherein the determining comprises:

determining that the first PUSCH occasion is invalid when the first PUSCH occasion overlaps with the first RACH occasion or the second RACH occasion in time and frequency for more than a threshold ratio portion of the first RACH occasion or the second RACH occasion;

excluding the first PUSCH occasion from a resource pool for a 2-step procedure in response to determining that the first PUSCH occasion is invalid; and

transmitting, to the BS, a first RACH message using available PUSCH occasions and available RACH occasions selected from the resource pool that does not contain the excluded first PUSCH occasions.

20 . The medium of claim 19 , wherein the operation of determining whether the first PUSCH occasion or the first RACH occasion is valid comprises:

validating the first PUSCH occasion with a synchronization signal block (SSB) and a downlink pattern defined in a time division duplexing (TDD) mode.

21 . The medium of claim 19 , wherein the operation of determining whether the first PUSCH occasion or the first RACH occasion is valid further comprises:

determining that the first PUSCH occasion is valid in response to determining that an overlapping area between the first PUSCH occasion and the first RACH occasion or the second RACH occasion is smaller than the threshold ratio portion of the first RACH occasion or the second RACH occasion.

22 . The medium of claim 19 , wherein the operation further comprises:

determining that the first PUSCH occasion is invalid; and

excluding the first PUSCH occasion when associating a synchronization signal block (SSB) with PUSCH occasions and RACH occasions for the first RACH procedure.

23 . The medium of claim 19 , wherein the operations further comprise:

determining that the first PUSCH occasion or the first RACH occasion is valid;

associating a first SSB with the first PUSCH occasion;

associating a second SSB with the first RACH occasion;

associating the first PUSCH occasion and the first RACH occasion according to an association rule defined by a network, in response to determining that the first SSB and the second SSB are a same SSB;

excluding the first PUSCH occasion or the first RACH occasion from a RACH resource pool in response to determining that the first SSB and the second SSB are different.

24 . The medium of claim 19 , wherein the operations further comprise:

associating a first SSB with the first PUSCH occasion;

associating a second SSB with the first RACH occasion;

associating the first PUSCH occasion and the first RACH occasion according to an association rule defined by a network, in response to determining that the first SSB and the second SSB are a same SSB;

determining that the first PUSCH occasion or the first RACH occasion is invalid; and

re-associating the first SSB or the second SSB with a valid PUSCH occasion and a valid RACH occasion selected from a RACH resource pool.

25 . The medium of claim 19 , wherein the operations further comprise:

receiving, from the BS, an update including a change in RACH configuration parameters; and

re-validating the first RACH occasion or the first PUSCH occasion according to the change in RACH configuration parameters.

26 . The medium of claim 19 , wherein the operation of determining whether the first PUSCH occasion or the first RACH occasion is valid comprises:

determining that the first PUSCH occasion collides with the first RACH occasion or the second RACH occasion;

determining that the first PUSCH occasion is associated with a first SSB, and the first RACH occasion or the second RACH occasion that collides with the first PUSCH is associated with a second SSB; and

determining that the first PUSCH occasion is valid in response to determining that the first SSB is different from the second SSB.

27 . The medium of claim 19 , wherein the first RACH procedure is a 2-step RACH procedure, and the second RACH procedure is a 4-step RACH procedure.

Assignments (2)

Continuity (2)

References Cited (18)

Cited By (1)

US 12,588,065