Physical random access channel occasions for transmitting physical uplink shared channel repetition requests
Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a user equipment (UE) may transmit a physical random access channel (PRACH) message corresponding to a PRACH occasion, wherein the PRACH occasion comprises a dedicated PRACH occasion or one of a plurality of PRACH occasions comprising at least one shared PRACH occasion associated with a two-step random access channel (RACH) procedure and a four-step RACH procedure, wherein the PRACH message includes a request for physical uplink shared channel (PUSCH) repetition corresponding to a radio resource control (RRC) connection request message of the four-step RACH procedure. The UE may transmit at least one PUSCH repetition associated with the RRC connection request message based at least in part on the request. Numerous other aspects are described.
1 . A user equipment (UE) for wireless communication, comprising:
one or more memories; and
one or more processors, coupled to the one or more memories, configured to:
receive an indication of a physical uplink shared channel (PUSCH) request configuration that indicates one or more subsets of a plurality of physical random access channel (PRACH) occasions from which a PRACH message is to be transmitted, the indication being received in system information that comprises a system information block;
transmit the PRACH message corresponding to the one or more subsets of the PRACH occasions, wherein the one or more subsets of the PRACH occasions comprises a dedicated PRACH occasion comprising at least one shared PRACH occasion associated with a two-step random access channel (RACH) procedure and a four-step RACH procedure, wherein the PRACH message includes a request for PUSCH repetition corresponding to a radio resource control (RRC) connection request message of the four-step RACH procedure; and
transmit at least one PUSCH repetition associated with the RRC connection request message based at least in part on the request.
2 . The UE of claim 1 , wherein the one or more processors are further configured to receive a second indication that the dedicated PRACH occasion is to be used for transmitting requests for PUSCH repetition corresponding to requests for RRC connection request messages.
3 . The UE of claim 2 , wherein the one or more processors, to receive the second indication, are configured to receive system information that includes the indication.
4 . The UE of claim 1 , wherein the one or more subsets include at least one of:
a first subset of the plurality of PRACH occasions, wherein all of the PRACH occasions in the first subset are associated with only the four-step RACH procedure,
a second subset of the plurality of PRACH occasions, wherein all of the PRACH occasions in the second subset are associated with only the two-step RACH procedure, or
a third subset of the plurality of PRACH occasions, wherein the third subset comprises the at least one shared PRACH occasion.
5 . The UE of claim 1 , wherein the PRACH message comprises a PRACH preamble associated with a set of preambles configured only in the plurality of PRACH occasions, and wherein the plurality of PRACH occasions are associated with the four-step RACH procedure, and wherein the plurality of PRACH occasions are configured with one or more PRACH preambles that are not used for requesting repetition of the RRC connection request message.
6 . The UE of claim 5 , wherein the one or more processors are further configured to transmit an additional PRACH message corresponding to an additional PRACH occasion, wherein the additional PRACH occasion is selected from a subset of the plurality of PRACH occasions, and wherein all of the PRACH occasions in the subset are associated with only the four-step RACH procedure.
7 . The UE of claim 5 , wherein the one or more processors are further configured to transmit an additional PRACH message corresponding to an additional PRACH occasion, wherein the additional PRACH occasion is selected from a subset of the plurality of PRACH occasions, and wherein the subset comprises the at least one shared PRACH occasion.
8 . The UE of claim 1 , wherein the plurality of PRACH occasions are associated with the two-step RACH procedure.
9 . The UE of claim 8 , wherein the one or more processors are further configured to transmit an additional PRACH message corresponding to an additional PRACH occasion, wherein the additional PRACH occasion is selected from a subset of the plurality of PRACH occasions, and wherein all of the PRACH occasions in the subset are associated with only the two-step RACH procedure.
10 . The UE of claim 8 , wherein the one or more processors are further configured to transmit an additional PRACH message corresponding to an additional PRACH occasion, wherein the additional PRACH occasion is selected from a subset of the plurality of PRACH occasions, and wherein the subset comprises the at least one shared PRACH occasion.
11 . The UE of claim 1 , wherein the one or more processors are further configured to transmit an additional PRACH message corresponding to an additional PRACH occasion of the plurality of PRACH occasions, wherein the additional PRACH message includes a reduced capability (RedCap) UE identification that indicates that the UE is a RedCap UE.
12 . The UE of claim 11 , wherein the PRACH message comprises a first PRACH preamble associated with a first set of PRACH preambles, wherein the additional PRACH message comprises a second PRACH preamble associated with a second set of PRACH preambles, and wherein the second set of PRACH preambles does not overlap the first set of PRACH preambles.
13 . A network entity for wireless communication, comprising:
one or more memories; and
one or more processors, coupled to the one or more memories, configured to:
transmit an indication of a physical uplink shared channel (PUSCH) request configuration that indicates one or more subsets of a plurality of physical random access channel (PRACH) occasions from which a PRACH message is to be transmitted, the indication being received in system information that comprises a system information block;
receive the PRACH message corresponding to the one or more subsets of the PRACH occasions, wherein the one or more subsets of the PRACH occasions comprises a dedicated PRACH occasion comprising at least one shared PRACH occasion associated with a two-step random access channel (RACH) procedure and a four-step RACH procedure, wherein the PRACH message includes a request for PUSCH repetition corresponding to a radio resource control (RRC) connection request message of the four-step RACH procedure; and
receive at least one PUSCH repetition associated with the RRC connection request message based at least in part on the request.
14 . The network entity of claim 13 , wherein the PRACH message comprises a PRACH preamble associated with a set of preambles configured only in the plurality of PRACH occasions, and wherein the plurality of PRACH occasions are associated with the four-step RACH procedure, and wherein the plurality of PRACH occasions are configured with one or more PRACH preambles that are not used for requesting repetition of the RRC connection request message.
15 . The network entity of claim 14 , wherein the one or more processors are further configured to receive an additional PRACH message corresponding to an additional PRACH occasion, wherein additional PRACH occasion is selected from a subset of the plurality of PRACH occasions, and wherein all of the PRACH occasions in the subset are associated with only the four-step RACH procedure.
16 . The network entity of claim 14 , wherein the one or more processors are further configured to receive an additional PRACH message corresponding to an additional PRACH occasion, wherein the additional PRACH occasion is selected from a subset of the plurality of PRACH occasions, and wherein the subset comprises the at least one shared PRACH occasion.
17 . The network entity of claim 13 , wherein the plurality of PRACH occasions are associated with the two-step RACH procedure.
18 . The network entity of claim 17 , wherein the one or more processors are further configured to receive an additional PRACH message corresponding to an additional PRACH occasion, wherein the additional PRACH occasion is selected from a subset of the plurality of PRACH occasions, and wherein all of the PRACH occasions in the subset are associated with only the two-step RACH procedure.
19 . The network entity of claim 17 , wherein the one or more processors are further configured to receive an additional PRACH message corresponding to an additional PRACH occasion, wherein the additional PRACH occasion is selected from a subset of the plurality of PRACH occasions, and wherein the subset comprises the at least one shared PRACH occasion.
20 . The network entity of claim 13 , wherein the one or more processors are further configured to transmit:
an indication that the PRACH occasion is to be used for transmitting requests for PUSCH repetition corresponding to requests for RRC connection request messages, wherein the PRACH occasion comprises the dedicated PRACH occasion.
21 . The network entity of claim 20 , wherein the one or more subsets include at least one of:
a first subset of the plurality of PRACH occasions, wherein all of the PRACH occasions in the first subset are associated with only the four-step RACH procedure,
a second subset of the plurality of PRACH occasions, wherein all of the PRACH occasions in the second subset are associated with only the two-step RACH procedure, or
a third subset of the plurality of PRACH occasions, wherein the third subset comprises the at least one shared PRACH occasion.
22 . The network entity of claim 13 , wherein the one or more processors are further configured to receive an additional PRACH message corresponding to an additional PRACH occasion of the plurality of PRACH occasions, wherein the additional PRACH message includes a reduced capability (RedCap) user equipment (UE) identification that indicates that a UE is a RedCap UE.
23 . The network entity of claim 22 , wherein the PRACH message comprises a first PRACH preamble associated with a first set of PRACH preambles, wherein the additional PRACH message comprises a second PRACH preamble associated with a second set of PRACH preambles, and wherein the second set of PRACH preambles does not overlap the first set of PRACH preambles.
24 . A method of wireless communication performed by a user equipment (UE), comprising:
receiving an indication of a physical uplink shared channel (PUSCH) request configuration that indicates one or more subsets of a plurality of physical random access channel (PRACH) occasions from which a PRACH message is to be transmitted, the indication being received in system information that comprises a system information block;
transmitting the PRACH message corresponding to the one or more subsets of the PRACH occasions, wherein the one or more subsets of the PRACH occasions comprises a dedicated PRACH occasion comprising at least one shared PRACH occasion associated with a two-step random access channel (RACH) procedure and a four-step RACH procedure, wherein the PRACH message includes a request for PUSCH repetition corresponding to a radio resource control (RRC) connection request message of the four-step RACH procedure; and
transmitting at least one PUSCH repetition associated with the RRC connection request message based at least in part on the request.
25 . A method of wireless communication performed by a network entity, comprising:
transmitting an indication of a physical uplink shared channel (PUSCH) request configuration that indicates one or more subsets of a plurality of physical random access channel (PRACH) occasions from which a PRACH message is to be transmitted, the indication being received in system information that comprises a system information block;
receiving the PRACH message corresponding to the one or more subsets of the PRACH occasions, wherein the one or more subsets of the PRACH occasions comprises a dedicated PRACH occasion comprising at least one shared PRACH occasion associated with a two-step random access channel (RACH) procedure and a four-step RACH procedure, wherein the PRACH message includes a request for PUSCH repetition corresponding to a radio resource control (RRC) connection request message of the four-step RACH procedure; and
receiving at least one PUSCH repetition associated with the RRC connection request message based at least in part on the request.
26 . The method of claim 24 , wherein the one or more subsets include at least one of:
a first subset of the plurality of PRACH occasions, wherein all of the PRACH occasions in the first subset are associated with only the four-step RACH procedure,
a second subset of the plurality of PRACH occasions, wherein all of the PRACH occasions in the second subset are associated with only the two-step RACH procedure, or
a third subset of the plurality of PRACH occasions, wherein the third subset comprises the at least one shared PRACH occasion.
27 . The method of claim 24 , wherein the PRACH message comprises a PRACH preamble associated with a set of preambles configured only in the plurality of PRACH occasions, and wherein the plurality of PRACH occasions are associated with the four-step RACH procedure, and wherein the plurality of PRACH occasions are configured with one or more PRACH preambles that are not used for requesting repetition of the RRC connection request message.
28 . The method of claim 27 , wherein the one or more processors are further configured to transmit an additional PRACH message corresponding to an additional PRACH occasion, wherein the additional PRACH occasion is selected from a subset of the plurality of PRACH occasions, and wherein all of the PRACH occasions in the subset are associated with only the four-step RACH procedure.
29 . The method of claim 27 , wherein the one or more processors are further configured to transmit an additional PRACH message corresponding to an additional PRACH occasion, wherein the additional PRACH occasion is selected from a subset of the plurality of PRACH occasions, and wherein the subset comprises the at least one shared PRACH occasion.
30 . The method of claim 25 , wherein the one or more subsets include at least one of:
a first subset of the plurality of PRACH occasions, wherein all of the PRACH occasions in the first subset are associated with only the four-step RACH procedure,
a second subset of the plurality of PRACH occasions, wherein all of the PRACH occasions in the second subset are associated with only the two-step RACH procedure, or
a third subset of the plurality of PRACH occasions, wherein the third subset comprises the at least one shared PRACH occasion.