Patent Description:
Examples of such multiple-access systems include fourth generation (<NUM>) systems such as Long-Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, or LTE-A Pro systems, and fifth generation (<NUM>) systems which may be referred to as New Radio (NR) systems.

In some wireless communications systems, a UE may use a two-step random-access procedure to establish a connection with a base station and/or identify suitable parameters and configurations for communicating with the base station. The two-step RACH procedure may include a transmission of a first RACH message from a UE to a base station and a transmission of a second RACH message from the base station to the UE (e.g., confirming reception of the first RACH message). In some cases, as part of a two-step RACH procedure, it may be appropriate for a UE to transmit data or control information to a base station. The data or control information may include a radio resource control (RRC) setup request, an RRC reestablishment request, an RRC resume request, an RRC system information request, or a cell radio network temporary identifier (C-RNTI). Conventional techniques for transmitting data or control information to a base station as part of a two-step RACH procedure may be deficient.

3GPP DRAFT R1-<NUM> relates to channel structure for two-step RACH considerations. 3GPP DRAFT R1-<NUM> relates to <NUM>-step random access procedure. 3GPP DRAFT R1-<NUM> relates to procedures for two-step RACH.

The described techniques relate to improved methods, systems, devices, and apparatuses that support random-access channel (RACH) occasion configuration. Generally, the described techniques provide for efficiently transmitting data and control information in a first RACH message to a base station as part of a two-step RACH procedure. In particular, rather than or in addition to transmitting data and control information in a physical uplink shared channel (PUSCH) in the first RACH message, a user equipment (UE) may transmit the data and control information along with a RACH preamble in a RACH occasion in the first RACH message (e.g., when the number of bytes of data and control information to be transmitted is low). Using these techniques, in some instances, the UE may transmit the data and control information in a first RACH message without transmitting the PUSCH, and the overhead associated with transmitting the PUSCH may be eliminated (e.g., cyclic redundancy check (CRC) overhead, channel coding overhead, higher layer header overhead).

According to the present invention, a method for wireless communication is provided as set out in claims <NUM> and <NUM> and an apparatus for wireless communication as set out in claim <NUM>.

In some wireless communications systems, a user equipment (UE) may use a two-step random-access channel (RACH) procedure to establish or re-establish a connection with a base station and/or identify suitable parameters and configurations for communicating with the base station. The two-step RACH procedure may include a transmission of a first RACH message from a UE to a base station and a transmission of a second RACH message from the base station to the UE. In some cases, as part of a two-step RACH procedure, it may be appropriate for a UE to transmit data or control information in a first RACH message to a base station. The data or control information may include a radio resource control (RRC) setup request, an RRC reestablishment request, an RRC resume request, an RRC system information request, or a cell radio network temporary identifier (C-RNTI).

Accordingly, in conventional systems, the UE may be configured to transmit the data or control information to the base station in a data channel in the first RACH message. However, the overhead associated with transmitting the data channel may be high (e.g., the overhead may include cyclic redundancy check (CRC) overhead, channel coding overhead, higher layer header overhead, or the like). Further, the two-step RACH procedure may be a contention-based RACH procedure, and the first RACH message may conflict with RACH messages from other UEs. Thus, if the amount of resources used to transmit the PUSCH in the first RACH message is large, there may be a greater chance that the first RACH message will conflict with RACH messages from other UEs, resulting in RACH failure.

As described herein, a UE may support efficient techniques for transmitting data and control information in a first RACH message to a base station as part of a two-step RACH procedure. In particular, rather than or in addition to transmitting data or control information in a physical uplink shared channel (PUSCH) in the first RACH message, a UE transmits the data or control information along with a RACH preamble in a RACH occasion in the first RACH message.

Using these techniques, in some instances (e.g., when the number of bytes of data and control information to be transmitted is low or below a threshold), the UE may transmit the data or control information in a RACH occasion in a first RACH message without transmitting the PUSCH in the first RACH message, and the overhead associated with transmitting the PUSCH may be eliminated (e.g., cyclic redundancy check (CRC) overhead, channel coding overhead, higher layer header overhead). Further, in other instances (e.g., when the number of bytes of data and control information to be transmitted is high or above a threshold), the UE may transmit the data or control information in a RACH occasion in a first RACH message and in a PUSCH in the first RACH message. In such instances, since the amount of data or control information transmitted in the PUSCH in the first RACH message may be minimized (e.g., because some of the data or control information is transmitted in the RACH occasion), the chances that the first RACH message will conflict with RACH messages from other UEs may be lowered, resulting in a lower possibility of RACH failure.

Aspects of the disclosure introduced above are described below in the context of a wireless communications system. Examples of processes and signaling exchanges that support RACH occasion configuration are then described. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts that relate to RACH occasion configuration.

<FIG> illustrates an example of a wireless communications system <NUM> that supports RACH occasion configuration in accordance with aspects of the present disclosure. The wireless communications system <NUM> includes base stations <NUM>, UEs <NUM>, and a core network <NUM>. In some examples, the wireless communications system <NUM> may be a Long-Term Evolution (LTE) network, an LTE-Advanced (LTE-A) network, an LTE-A Pro network, or a New Radio (NR) network. In some cases, wireless communications system <NUM> may support enhanced broadband communications, ultra-reliable (e.g., mission critical) communications, low latency communications, or communications with low-cost and low-complexity devices.

Communication links <NUM> shown in wireless communications system <NUM> may include uplink transmissions from a UE <NUM> to a base station <NUM> or downlink transmissions from a base station <NUM> to a UE <NUM>.

The term "cell" may refer to a logical communication entity used for communication with a base station <NUM> (e.g., over a carrier), and may be associated with an identifier for distinguishing neighboring cells (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID)) operating via the same or a different carrier.

The term "carrier" may refer to a set of radio frequency spectrum resources having a defined physical layer structure for supporting communications over a communication link <NUM>. A carrier may be associated with a pre-defined frequency channel (e.g., an evolved universal mobile telecommunication system terrestrial radio access (E-UTRA) absolute radio frequency channel number (EARFCN)), and may be positioned according to a channel raster for discovery by UEs <NUM>. Carriers may be downlink or uplink (e.g., in a frequency division duplexing (FDD) mode) or be configured to carry downlink and uplink communications (e.g., in a time division duplexing (TDD) mode). In some examples, signal waveforms transmitted over a carrier may be made up of multiple sub-carriers (e.g., using multi-carrier modulation (MCM) techniques such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)).

For example, wireless communications system <NUM> may use a transmission scheme between a transmitting device (e.g., a base station <NUM>) and a receiving device (e.g., a UE <NUM>), where the transmitting device is equipped with multiple antennas and the receiving device is equipped with one or more antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry bits associated with the same data stream (e.g., the same codeword) or different data streams.

In one example, a base station <NUM> may use multiple antennas or antenna arrays to conduct beamforming operations for directional communications with a UE <NUM>. For instance, some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted by a base station <NUM> multiple times in different directions, which may include a signal being transmitted according to different beamforming weight sets associated with different directions of transmission. Transmissions in different beam directions may be used to identify (e.g., by the base station <NUM> or a receiving device, such as a UE <NUM>) a beam direction for subsequent transmission and/or reception by the base station <NUM>.

Some signals, such as data signals associated with a particular receiving device, may be transmitted by a base station <NUM> in a single beam direction (e.g., a direction associated with the receiving device, such as a UE <NUM>). In some examples, the beam direction associated with transmissions along a single beam direction may be determined based at least in in part on a signal that was transmitted in different beam directions. For example, a UE <NUM> may receive one or more of the signals transmitted by the base station <NUM> in different directions, and the UE <NUM> may report to the base station <NUM> an indication of the signal it received with a highest signal quality, or an otherwise acceptable signal quality. Although these techniques are described with reference to signals transmitted in one or more directions by a base station <NUM>, a UE <NUM> may employ similar techniques for transmitting signals multiple times in different directions (e.g., for identifying a beam direction for subsequent transmission or reception by the UE <NUM>) or transmitting a signal in a single direction (e.g., for transmitting data to a receiving device).

In wireless communications system <NUM>, a UE <NUM> may use a RACH procedure to establish or re-establish a connection with a base station <NUM> and/or identify suitable parameters and configurations for communicating with the base station <NUM>. Wireless communications system <NUM> may support four-step RACH procedures and two-step RACH procedures. A four-step RACH procedure may include four message exchanges between a UE <NUM> and a base station <NUM>, and a two-step RACH procedure may include two message exchanges between a UE <NUM> and a base station <NUM>. In both procedures, it may be appropriate for a UE <NUM> to transmit data or control information to a base station <NUM>. In a four-step RACH procedure, the UE <NUM> may transmit the data or control information in a third RACH message (e.g., MSG3) to the base station <NUM>. In a two-step RACH procedure the UE <NUM> may transmit the data or control information in a first RACH message (e.g., MSG1 or MSGA) to the base station <NUM>.

The data or control information may include a MAC sub-header (e.g., <NUM> byte) in addition an RRC setup request (e.g., <NUM> bytes), an RRC reestablishment request (e.g., <NUM> bytes), an RRC resume request (e.g., <NUM> bytes), an RRC system information request (e.g., <NUM> bytes), or a cell radio network temporary identifier (C-RNTI) (e.g., <NUM> bytes). The content of the data or control information transmitted in a RACH procedure may be based on the intention of the RACH procedure. For instance, a UE <NUM> may transmit an RRC setup request to gain initial access to a base station <NUM> from an RRC_IDLE mode, an RRC re-establishment request to re-establish an RRC connection, an RRC resume request to transition from an RRC_INACTIVE mode, an RRC system information request to request system information, or a C-RNTI for a beam failure recovery (BFR) procedure, a handover procedure, a buffer status reporting (BSR) procedure, a beam correspondence indication, or other uplink control information. Thus, the payload including the data or control information may be one of <NUM>, <NUM>, <NUM>, or <NUM> bytes (e.g., with RRC message transmissions) or one of <NUM>, <NUM>, or <NUM> bytes (e.g., without RRC message transmissions when the UE <NUM> is in an RRC_CONNECTED mode).

<FIG> illustrates an example of a first RACH message <NUM> that supports RACH occasion configuration in accordance with aspects of the present disclosure. In some examples, first RACH message <NUM> may be an example of a first RACH message (e.g., Message A (MSGA)) used in wireless communications system <NUM>. For example, a first RACH message <NUM> may be an example of a first RACH message sent between a UE <NUM> and a base station <NUM> as part of a two-step RACH procedure. As described herein, a UE <NUM> in wireless communications system <NUM> may support efficient techniques for transmitting data and control information in a first RACH message <NUM> to a base station as part of a two-step RACH procedure.

As described above, in a four-step RACH procedure, a UE <NUM> may transmit a RACH preamble in a first RACH message of the four-step RACH procedure and may transmit data or control information in a third RACH message of the four-step RACH procedure. In a two-step RACH procedure, however, a UE <NUM> may transmit both a RACH preamble and data or control information in the first RACH message. Accordingly, in conventional systems, the UE <NUM> may be configured to transmit the data or control information to the base station in a PUSCH in the first RACH message.

In the example of <FIG>, a UE <NUM> may transmit a RACH preamble <NUM> to a base station <NUM> in a RACH occasion <NUM> of the first RACH message <NUM> (e.g., Message A (MGSA)). After a transmission gap <NUM>, the UE <NUM> may then transmit a PUSCH <NUM> (e.g., on resource blocks different from the RACH occasion <NUM>), including data or control information, to the base station <NUM>.

In some cases, however, the overhead associated with transmitting the PUSCH <NUM> may be high (e.g., the overhead may include cyclic redundancy check (CRC) overhead, channel coding overhead, higher layer header overhead, or the like). Further, the two-step RACH procedure may be a contention-based RACH procedure, and the first RACH message <NUM> may conflict with RACH messages from other UEs. Thus, if the amount of resources used to transmit the PUSCH <NUM> in the first RACH message <NUM> is large (e.g., larger than a threshold), there may be a greater chance that the first RACH message <NUM> will conflict with RACH messages from other UEs, which may result in RACH failure.

To improve reliability of RACH procedures (e.g., in cases where the amount of resources used to transmit a PUSCH <NUM> is above a threshold), a UE <NUM> may transmit, to a base station, data or control information in a first RACH message as part of a two-step RACH procedure. In particular, rather than or in addition to transmitting data or control information in a PUSCH in the first RACH message, a UE <NUM> may transmit the data or control information along with a RACH preamble (e.g., RACH preamble <NUM>) in a RACH occasion (e.g., RACH occasion <NUM>) in the first RACH message (e.g., first RACH message <NUM>).

<FIG> illustrates an example of a wireless communications system <NUM> that supports RACH occasion configuration in accordance with aspects of the present disclosure. Wireless communications system <NUM> includes base station <NUM>-a, which may be an example of a base station <NUM> described with reference to <FIG>. Wireless communications system <NUM> also includes UE <NUM>-a, which may be an example of a UE <NUM> described with reference to <FIG>. Base station <NUM>-a may provide communication coverage for a respective coverage area <NUM>-a, which may be an example of a coverage area <NUM> described with reference to <FIG>. Wireless communications system <NUM> may implement aspects of wireless communications system <NUM>. For example, UE <NUM>-a in wireless communications system <NUM> may support efficient techniques for transmitting data and control information in a first RACH message <NUM> to a base station <NUM>-a as part of a two-step RACH procedure.

In the example of <FIG>, UE <NUM>-a may determine to perform a two-step RACH procedure to establish or re-establish a connection with a base station <NUM>-a. Additionally or alternatively, UE <NUM>-a may identify suitable parameters and configurations for communicating with the base station <NUM>-a. Accordingly, UE <NUM>-a may transmit a first RACH message <NUM> (e.g., MSG1 or MSGA) to base station <NUM>-a as part of the two-step RACH procedure. The first RACH message <NUM> may include a RACH occasion <NUM>, which may further contain a RACH preamble <NUM> and data or control information <NUM>. The first RACH message <NUM> may also include a transmission gap <NUM> and a PUSCH <NUM>, which may further contain additional data or control information <NUM>. Upon reception of the first RACH message <NUM>, base station <NUM>-a may transmit a second RACH message <NUM> (e.g., MSG2 or MSGB) to UE <NUM>-a (e.g., confirming receipt of the first RACH message <NUM>).

UE <NUM>-a identifies a RACH preamble <NUM> and data or control information <NUM> to transmit to base station <NUM>-a. UE <NUM>-a transmits the RACH preamble <NUM> to base station <NUM>-a in a RACH occasion <NUM> in the first RACH message <NUM>. UE <NUM>-a also transmits the identified data or control information <NUM> in the RACH occasion <NUM> along with the RACH preamble <NUM>. In some cases, after a transmission gap <NUM>, UE <NUM>-a may also transmit additional data or control information <NUM> in a PUSCH <NUM> in the first RACH message <NUM>.

In some aspects, if UE <NUM>-a determines that the number of bytes of data or control information to be transmitted in the first RACH message <NUM> is low or below a threshold (e.g., <NUM>-<NUM> bytes for BFR procedures, BSR transmissions), UE <NUM>-a may transmit all of the data or control information in the RACH occasion <NUM> in the first RACH message <NUM> (e.g., only data or control information <NUM>). In such aspects, UE <NUM>-a may transmit an indication in the RACH occasion <NUM> that no additional data or control information <NUM> is to be transmitted in a PUSCH <NUM> in the first RACH message <NUM>. In other aspects, if UE <NUM>-a determines that the number of bytes of data or control information to be transmitted in the first RACH message <NUM> is high or above a threshold, UE <NUM>-a may transmit data or control information <NUM> in the RACH occasion <NUM> and additional data or control information <NUM> in the PUSCH <NUM>. In such aspects, UE <NUM>-a may transmit an indication in the RACH occasion <NUM> that additional data or control information <NUM> is transmitted in a PUSCH <NUM> in the first RACH message <NUM>.

In some cases, in the first RACH message <NUM>, UE <NUM>-a may transmit an explicit indication of resources of the PUSCH <NUM> used to transmit the additional data or control information <NUM> such that base station <NUM>-a may be able to monitor the resources of the PUSCH <NUM> to receive the additional data or control information <NUM>. In other cases, the resources of the PUSCH <NUM> used to transmit the additional data or control information <NUM> may be implicitly indicated, and base station <NUM>-a may identify which resources of the PUSCH <NUM> to monitor for the additional data or control information <NUM> based on the resources of the RACH occasion <NUM> (e.g., the PUSCH resources may be a certain number of symbols after the RACH occasion).

Thus, first RACH message <NUM> may include, but is not limited to, a RACH preamble <NUM>, data or control information <NUM> (e.g., including a C-RNTI and other information depending on the RACH intention), additional data or control information <NUM>, an indication of the presence of a PUSCH <NUM>, an indication of PUSCH resources, a cyclic prefix, a guard time, and an optional cyclic redundancy check (CRC). As described above, UE <NUM>-a may transmit the RACH preamble <NUM>, the data or control information <NUM>, the optional indication of the presence of the PUSCH <NUM>, and the optional indication of PUSCH resources in a RACH occasion in the first RACH message <NUM>. Then, after the transmission gap <NUM>, UE <NUM>-a may optionally transmit the additional data or control information <NUM> in a PUSCH <NUM> in the first RACH message <NUM>. Once base station <NUM>-a receives the first RACH message <NUM>, base station <NUM>-a may transmit a second RACH message <NUM> to UE <NUM>-a (e.g., confirming receipt of the first RACH message <NUM>).

<FIG> illustrates an example of a process flow <NUM> that supports RACH occasion configuration in accordance with aspects of the present disclosure. Process flow <NUM> illustrates aspects of techniques performed by a base station <NUM>-b, which may be an example of a base station <NUM> described with reference to <FIG>. Process flow <NUM> also illustrates aspects of techniques performed by a UE <NUM>-b, which may be an example of a UE <NUM> described with reference to <FIG>. Process flow <NUM> may implement aspects of wireless communications systems <NUM> and <NUM>. For example, UE <NUM>-b in process flow <NUM> may support efficient techniques for transmitting data and control information in a first RACH message to a base station <NUM>-b as part of a two-step RACH procedure. In particular, rather than or in addition to transmitting data or control information in a PUSCH in the first RACH message, UE <NUM>-b may transmit the data or control information along with a RACH preamble in a RACH occasion in the first RACH message.

At <NUM>, base station <NUM>-b may identify configurations for a set of RACH occasions to be used in a two-step RACH procedure, where at least one of the configurations indicates a first set of resources in the RACH occasion allocated for a RACH preamble transmission and a second set of resources allocated for a data or control information transmission. Base station <NUM>-b may transmit a control message (e.g., a system information block (SIB)) indicating the RACH occasion configurations. In some cases, the resources allocated for RACH occasions to be used for RACH preamble transmissions and data or control information transmissions (e.g., in two-step RACH procedures) may be orthogonal to resources allocated for RACH occasions to be used for only RACH preamble transmissions (e.g., in four-step RACH procedures). The RACH preambles (e.g., made up of gold sequences) may be the same for both types of RACH occasions. For example, a RACH preamble available to be transmitted in a RACH occasion to be used for both RACH preamble transmissions and data or control information may be the same as a RACH preamble available to be transmitted in a RACH occasion to be used for only RACH preamble transmissions (e.g., without data or control information).

Each RACH occasion configuration transmitted by base station <NUM>-b at <NUM> may indicate the time and frequency resources to be used for the RACH preamble transmission (e.g., the first set of resources), a resource or payload size for the data or control information transmission (e.g., where the resource or payload size may be indicated by a RACH occasion type), a correspondence of the RACH occasion to an SSB, a modulation and coding scheme (MCS) to be used for the transmissions in the RACH occasion, etc..

At <NUM>, UE <NUM>-b may select the RACH occasion based on the content or quantity of the data or control information to be transmitted to base station <NUM>-b as part of the RACH procedure. For example, UE <NUM>-b may select the RACH occasion based on the intention of the RACH procedure (e.g., re-establishing an RRC connection, transmitting a BSR, or the like). UE <NUM>-b may identify a RACH preamble for transmission to base station <NUM>-b in the RACH occasion as part of a two-step RACH procedure.

At <NUM>, UE <NUM>-b may identify data or control information for transmission to base station <NUM>-b as part of the two-step RACH procedure.

At <NUM>, UE <NUM>-b may transmit both the RACH preamble and the data or control information within the RACH occasion in a first RACH message. In some cases, as described above with reference to <FIG>, UE <NUM>-b may also transmit additional data or control information in the first RACH message (e.g., in a PUSCH that is outside of the RACH occasion).

In some cases, the resource size for the data or control information transmission in a RACH occasion may be based on the content or quantity of data or control information to be transmitted in the RACH occasion (e.g., based on the RACH intention). Accordingly, when UE <NUM>-b selects a RACH occasion in which to transmit data or control information in a two-step RACH procedure based on an intention of the two-step RACH procedure, the UE <NUM>-b may have sufficient resources to transmit the data and control information in the RACH occasion. In other cases, the resource size for the data or control information transmission in a RACH occasion may be fixed. In such cases, when UE <NUM>-b selects a RACH occasion in which to transmit data or control information in a two-step RACH procedure based on an intention of the two-step RACH procedure, the UE <NUM>-b may transmit the data and control information in the RACH occasion on the fixed resources. Further, if additional resources are available after the data and control information is mapped to the fixed resources, UE <NUM>-b may repeat portions of the data and control information in the RACH occasion on the additional resources. As an example, if the resource size of a RACH occasion is sufficient for a one-byte payload, and UE <NUM>-b determines to transmit a C-RNTI in a two-step RACH procedure (e.g., for a BFR procedure), UE <NUM>-b may transmit the C-RNTI once in the RACH occasion. In another example, if the resource size of a RACH occasion is sufficient for a three-byte payload, and UE <NUM>-b determines to transmit a C-RNTI in a two-step RACH procedure (e.g., for a BFR procedure), UE <NUM>-b may repeat the C-RNTI three times in the RACH occasion.

In some cases, the channel coding used to encode the first RACH message may be based on the number of bits in the first RACH message. For instance, if the number of bits in the first RACH message is below or equal to a threshold (e.g., <NUM> bits), UE <NUM>-b may use an NR resource management coding scheme to encode the first RACH message. Alternatively, if the number of bits in the first RACH message is above a threshold (e.g., <NUM> bits), UE <NUM>-b may use a polar coding scheme to encode the first RACH message.

At <NUM>, after base station <NUM>-b receives the first RACH message, base station <NUM>-b may transmit a second RACH message to UE <NUM>-b confirming receipt of the first RACH message. The second RACH message may include timing advance information, power control parameters, an uplink grant, a downlink grant, a cell radio network temporary identifier (C-RNTI), information for contention resolution, etc. Thus, UE <NUM>-b may use the information in the second RACH message for subsequent communications with base station <NUM>-b.

It is to be understood that a RACH occasion (e.g., or RACH resource) may be selected from a number of RACH occasions (e.g., or RACH resources) configured by the base station <NUM>-a in a control message (e.g., system information block (SIB)), and the RACH occasion (e.g., RACH occasion <NUM>) may be different from a PUSCH (e.g., PUSCH <NUM>). In a four-step RACH procedure, a RACH occasion may correspond to the resources (e.g., time, frequency, and/or spatial resources) on which a RACH preamble is transmitted using a configured RACH preamble format (e.g., with a single transmit beam). In a two-step RACH procedure, a RACH occasion may also correspond to the resources (e.g., time frequency, and/or spatial resources) on which a RACH preamble is transmitted using a configured RACH preamble format (e.g., with a single transmit beam). However, as described herein, a UE may also transmit data or control information in a RACH occasion in a first RACH message of a two-step RACH procedure.

<FIG> shows a block diagram <NUM> of a device <NUM> that supports RACH occasion configuration in accordance with aspects of the present disclosure. The device <NUM> may be an example of aspects of a UE <NUM> as described herein. The device <NUM> may include a receiver <NUM>, a communications manager <NUM>, and a transmitter <NUM>. The device <NUM> may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).

The receiver <NUM> may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to RACH occasion configuration). Information may be passed on to other components of the device <NUM>. The receiver <NUM> may be an example of aspects of the transceiver <NUM> described with reference to <FIG>. The receiver <NUM> may utilize a single antenna or a set of antennas.

The communications manager <NUM> may identify a random-access preamble for transmission to a base station in a random-access channel occasion as part of a two-step random-access procedure, identify data or control information for transmission to the base station as part of the two-step random-access procedure, and transmit both the random-access preamble and the data or control information within the random-access channel occasion. The communications manager <NUM> may be an example of aspects of the communications manager <NUM> described herein.

In some examples, the communications manager <NUM> may be implemented as an integrated circuit or chipset for a mobile device modem, and the receiver <NUM> and transmitter <NUM> may be implemented as analog components (for example, amplifiers, filters, antennas, etc.) coupled with the mobile device modem to enable wireless transmission and reception.

The communications manager <NUM> as described herein may be implemented to realize one or more potential advantages. Various implementations may reduce overhead associated with RACH procedures. At least some implementations may enable the communications manager <NUM> to transmit data and control information in a first RACH message and, as such, refrain from transmitting data and control information in a PUSCH transmission. At least some implementations may enable the communications manager <NUM> to reduce the amount of data or control information transmitted in a PUSCH in a first RACH message.

Based on implementing the overhead reduction techniques as described herein, one or more processors of the device <NUM> (for example, processor(s) controlling or incorporated with one or more of receiver <NUM>, communications manager <NUM>, and transmitter <NUM>) may improve communication reliability or efficiency. For example, a UE may send data and control information to a base station along with a RACH preamble in a first RACH message. Accordingly, the UE may refrain from transmitting a PUSCH in the first RACH message or may transmit a reduced amount of data and control information in a PUSCH in the first RACH message. As such, the amount of overhead associated with transmitting a PUSCH may be reduced and the likelihood of RACH failure may decrease.

<FIG> shows a block diagram <NUM> of a device <NUM> that supports RACH occasion configuration in accordance with aspects of the present disclosure. The device <NUM> may be an example of aspects of a device <NUM> or a UE <NUM> as described herein. The device <NUM> may include a receiver <NUM>, a communications manager <NUM>, and a transmitter <NUM>. The device <NUM> may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).

The receiver <NUM> may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to RACH occasion configuration, etc.). Information may be passed on to other components of the device <NUM>. The receiver <NUM> may be an example of aspects of the transceiver <NUM> described with reference to <FIG>. The receiver <NUM> may utilize a single antenna or a set of antennas.

The communications manager <NUM> may be an example of aspects of the communications manager <NUM> as described herein. The communications manager <NUM> may include a RACH preamble manager <NUM>, a RACH data or control information manager <NUM>, and a RACH transmission manager <NUM>. The communications manager <NUM> may be an example of aspects of the communications manager <NUM> described herein.

The RACH preamble manager <NUM> may identify a random-access preamble for transmission to a base station in a random-access channel occasion as part of a two-step random-access procedure. The RACH data or control information manager <NUM> may identify data or control information for transmission to the base station as part of the two-step random-access procedure. The RACH transmission manager <NUM> may transmit both the random-access preamble and the data or control information within the random-access channel occasion.

<FIG> shows a block diagram <NUM> of a communications manager <NUM> that supports RACH occasion configuration in accordance with aspects of the present disclosure. The communications manager <NUM> may be an example of aspects of a communications manager <NUM>, a communications manager <NUM>, or a communications manager <NUM> described herein. The communications manager <NUM> may include a RACH preamble manager <NUM>, a RACH data or control information manager <NUM>, a RACH transmission manager <NUM>, a RACH occasion manager <NUM>, a RACH PUSCH manager <NUM>, and a RACH reception manager <NUM>. Each of these modules may communicate, directly or indirectly, with one another (e.g., via one or more buses).

The RACH preamble manager <NUM> may identify a random-access preamble for transmission to a base station in a random-access channel occasion as part of a two-step random-access procedure. The RACH data or control information manager <NUM> may identify data or control information for transmission to the base station as part of the two-step random-access procedure. In some cases, the data or control information is transmitted on a first set of resources adjacent to a second set of resources on which the random-access preamble is transmitted in the random-access channel occasion.

The RACH transmission manager <NUM> may transmit both the random-access preamble and the data or control information within the random-access channel occasion. In some examples, the RACH transmission manager <NUM> may transmit the data or control information in the random-access channel occasion with the random-access preamble based on a number of bytes of the data or control information being below a threshold. In some cases, the threshold may be configurable (e.g., signaled to a UE from a base station) and may be based at least in part on the random-access channel occasion (e.g., different RACH occasions may have different thresholds). In some examples, the RACH transmission manager <NUM> may transmit the random-access preamble and the data or control information in the random-access channel occasion in a first random-access message of the two-step random-access procedure. The RACH occasion manager <NUM> may receive a control message indicating a set of random-access channel occasion configurations.

In some examples, the RACH occasion manager <NUM> may select the random-access channel occasion from the set of random-access channel occasion configurations based on a content or quantity of the data or control information to be transmitted as part of the two-step random-access procedure. In some cases, each random-access channel occasion configuration indicates time and frequency resources for a random-access preamble transmission in a corresponding random-access channel occasion, a correspondence of the corresponding random-access channel occasion to a synchronization signal block, and a resource size for a data or control information transmission in the corresponding random-access channel occasion. In some cases, the resource size for the data or control information transmission in each random-access channel occasion is based on data or control information to be transmitted in the random-access channel occasion. In some cases, the resource size for the data or control information transmission in each random-access channel occasion is fixed.

The RACH PUSCH manager <NUM> may transmit additional data or control information in a data channel in the first random-access message but outside of the random-access channel occasion. In some examples, the RACH PUSCH manager <NUM> may transmit an indication in the random-access channel occasion of whether additional data or control information is transmitted in a data channel in the first random-access message. In some examples, the RACH PUSCH manager <NUM> may transmit an indication in the random-access channel occasion of resources to be used for transmitting additional data or control information in a data channel in the first random-access message. The RACH reception manager <NUM> may receive a second random-access message from the base station as part of the two-step random-access procedure, the second random-access message being received based on transmission of the first random-access message. In some cases, the second random-access message includes a timing advance indication, power control parameters, an uplink grant, a downlink grant, a cell radio network temporary identifier, information for contention resolution, or a combination thereof.

<FIG> shows a diagram of a system <NUM> including a device <NUM> that supports RACH occasion configuration in accordance with aspects of the present disclosure. The device <NUM> may be an example of or include the components of device <NUM>, device <NUM>, or a UE <NUM> as described herein. The device <NUM> may include components for bi-directional voice and data communications including components for transmitting and receiving communications, including a communications manager <NUM>, an I/O controller <NUM>, a transceiver <NUM>, an antenna <NUM>, memory <NUM>, and a processor <NUM>. These components may be in electronic communication via one or more buses (e.g., bus <NUM>).

The communications manager <NUM> may identify a random-access preamble for transmission to a base station in a random-access channel occasion as part of a two-step random-access procedure, identify data or control information for transmission to the base station as part of the two-step random-access procedure, and transmit both the random-access preamble and the data or control information within the random-access channel occasion.

The processor <NUM> may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor <NUM> may be configured to operate a memory array using a memory controller. In other cases, a memory controller may be integrated into the processor <NUM>. The processor <NUM> may be configured to execute computer-readable instructions stored in a memory (e.g., the memory <NUM>) to cause the device <NUM> to perform various functions (e.g., functions or tasks supporting RACH occasion configuration).

<FIG> shows a block diagram <NUM> of a device <NUM> that supports RACH occasion configuration in accordance with aspects of the present disclosure. The device <NUM> may be an example of aspects of a base station <NUM> as described herein. The device <NUM> may include a receiver <NUM>, a communications manager <NUM>, and a transmitter <NUM>. The device <NUM> may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).

The communications manager <NUM> may identify a configuration for a random-access channel occasion to be allocated to one or more UE, where the configuration indicates a first set of resources in the random-access channel occasion allocated for a random-access preamble transmission and a second set of resources in the random-access channel occasion allocated for a data or control information transmission, transmit a control message indicating the configuration of the random-access channel occasion, and receive, from a UE, a random-access preamble on the first set of resources in the random-access channel occasion and data or control information on the second set of resources in the random-access channel occasion as part of a two-step random-access procedure. The communications manager <NUM> may be an example of aspects of the communications manager <NUM> described herein.

<FIG> shows a block diagram <NUM> of a device <NUM> that supports RACH occasion configuration in accordance with aspects of the present disclosure. The device <NUM> may be an example of aspects of a device <NUM> or a base station <NUM> as described herein. The device <NUM> may include a receiver <NUM>, a communications manager <NUM>, and a transmitter <NUM>. The device <NUM> may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).

The communications manager <NUM> may be an example of aspects of the communications manager <NUM> as described herein. The communications manager <NUM> may include a RACH occasion manager <NUM> and a RACH reception manager <NUM>. The communications manager <NUM> may be an example of aspects of the communications manager <NUM> described herein.

The RACH occasion manager <NUM> may identify a configuration for a random-access channel occasion to be allocated to one or more UE, where the configuration indicates a first set of resources in the random-access channel occasion allocated for a random-access preamble transmission and a second set of resources in the random-access channel occasion allocated for a data or control information transmission and transmit a control message indicating the configuration of the random-access channel occasion. The RACH reception manager <NUM> may receive, from a UE, a random-access preamble on the first set of resources in the random-access channel occasion and data or control information on the second set of resources in the random-access channel occasion as part of a two-step random-access procedure.

<FIG> shows a block diagram <NUM> of a communications manager <NUM> that supports RACH occasion configuration in accordance with aspects of the present disclosure. The communications manager <NUM> may be an example of aspects of a communications manager <NUM>, a communications manager <NUM>, or a communications manager <NUM> described herein. The communications manager <NUM> may include a RACH occasion manager <NUM>, a RACH reception manager <NUM>, a RACH PUSCH manager <NUM>, and a RACH transmission manager <NUM>. Each of these modules may communicate, directly or indirectly, with one another (e.g., via one or more buses).

The RACH occasion manager <NUM> may identify a configuration for a random-access channel occasion to be allocated to one or more UEs, where the configuration indicates a first set of resources in the random-access channel occasion allocated for a random-access preamble transmission and a second set of resources in the random-access channel occasion allocated for a data or control information transmission. In some examples, the RACH occasion manager <NUM> may transmit a control message indicating the configuration of the random-access channel occasion. In some cases, the configuration of the random-access channel occasion further indicates a correspondence of the random-access channel occasion to a synchronization signal block.

In some cases, a size of the second set of resources allocated for the data or control information transmission is based on the data or control information to be transmitted in the random-access channel occasion. In some aspects, a size of the second set of resources allocated for the data or control information transmission is fixed. In some cases, the first set of resources allocated for the random-access preamble transmission is adjacent to the second set of resources allocated for the data or control information transmission.

The RACH reception manager <NUM> may receive, from a UE, a random-access preamble on the first set of resources in the random-access channel occasion and data or control information on the second set of resources in the random-access channel occasion as part of a two-step random-access procedure. In some examples, the RACH reception manager <NUM> may receive the data or control information in the random-access channel occasion with the random-access preamble based on a number of bytes of the data or control information being below a threshold. In some cases, the threshold may be configurable and may be based at least in part on the random-access channel occasion. In some examples, the RACH reception manager <NUM> may receive the random-access preamble and the data or control information in the random-access channel occasion in a first random-access message of the two-step random-access procedure.

The RACH PUSCH manager <NUM> may receive additional data or control information in a data channel in the first random-access message but outside of the random-access channel occasion. In some examples, the RACH PUSCH manager <NUM> may receive an indication in the random-access channel occasion of whether additional data or control information is transmitted in a data channel in the first random-access message. In some examples, the RACH PUSCH manager <NUM> may receive an indication in the random-access channel occasion of resources to monitor for additional data or control information in a data channel in the first random-access message. The RACH transmission manager <NUM> may transmit a second random-access message to the UE as part of the two-step random-access procedure, the second random-access message being transmitted based on reception of the first random-access message. In some cases, the second random-access message includes a timing advance indication, power control parameters, an uplink grant, a downlink grant, a cell radio network temporary identifier, information for contention resolution, or a combination thereof.

<FIG> shows a diagram of a system <NUM> including a device <NUM> that supports RACH occasion configuration in accordance with aspects of the present disclosure. The device <NUM> may be an example of or include the components of device <NUM>, device <NUM>, or a base station <NUM> as described herein. The device <NUM> may include components for bi-directional voice and data communications including components for transmitting and receiving communications, including a communications manager <NUM>, a network communications manager <NUM>, a transceiver <NUM>, an antenna <NUM>, memory <NUM>, a processor <NUM>, and an inter-station communications manager <NUM>. These components may be in electronic communication via one or more buses (e.g., bus <NUM>).

The communications manager <NUM> may identify a configuration for a random-access channel occasion to be allocated to one or more UEs, where the configuration indicates a first set of resources in the random-access channel occasion allocated for a random-access preamble transmission and a second set of resources in the random-access channel occasion allocated for a data or control information transmission. The communications manager <NUM> may transmit a control message indicating the configuration of the random-access channel occasion, and may receive, from a UE, a random-access preamble on the first set of resources in the random-access channel occasion and data or control information on the second set of resources in the random-access channel occasion as part of a two-step random-access procedure.

The processor <NUM> may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor <NUM> may be configured to operate a memory array using a memory controller. In some cases, a memory controller may be integrated into processor <NUM>. The processor <NUM> may be configured to execute computer-readable instructions stored in a memory (e.g., the memory <NUM>) to cause the device <NUM> to perform various functions (e.g., functions or tasks supporting RACH occasion configuration).

The inter-station communications manager <NUM> may manage communications with other base station <NUM> and may include a controller or scheduler for controlling communications with UEs <NUM> in cooperation with other base stations <NUM>.

<FIG> shows a flowchart illustrating a method <NUM> that supports RACH occasion configuration in accordance with aspects of the present disclosure. The operations of method <NUM> may be implemented by a UE <NUM> or its components as described herein. For example, the operations of method <NUM> may be performed by a communications manager as described with reference to <FIG>. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the functions described below. Additionally, or alternatively, a UE may perform aspects of the functions described below using special-purpose hardware.

At <NUM>, the UE may identify a random-access preamble for transmission to a base station in a random-access channel occasion as part of a two-step random-access procedure. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a RACH preamble manager as described with reference to <FIG>.

At <NUM>, the UE may identify data or control information for transmission to the base station as part of the two-step random-access procedure. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a RACH data or control information manager as described with reference to <FIG>.

At <NUM>, the UE may transmit both the random-access preamble and the data or control information within the random-access channel occasion. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a RACH transmission manager as described with reference to <FIG>.

<FIG> shows a flowchart illustrating a method <NUM> that supports RACH occasion configuration in accordance with aspects of the present disclosure. The operations of method <NUM> may be implemented by a base station <NUM> or its components as described herein. For example, the operations of method <NUM> may be performed by a communications manager as described with reference to <FIG>. In some examples, a base station may execute a set of instructions to control the functional elements of the base station to perform the functions described below. Additionally, or alternatively, a base station may perform aspects of the functions described below using special-purpose hardware.

At <NUM>, the base station may identify a configuration for a random-access channel occasion to be allocated to one or more UE, where the configuration indicates a first set of resources in the random-access channel occasion allocated for a random-access preamble transmission and a second set of resources in the random-access channel occasion allocated for a data or control information transmission. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a RACH occasion manager as described with reference to <FIG>.

At <NUM>, the base station may transmit a control message indicating the configuration of the random-access channel occasion. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a RACH occasion manager as described with reference to <FIG>.

At <NUM>, the base station may receive, from a UE, a random-access preamble on the first set of resources in the random-access channel occasion and data or control information on the second set of resources in the random-access channel occasion as part of a two-step random-access procedure. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a RACH reception manager as described with reference to <FIG>.

A non-transitory storage medium may be any available medium that can be accessed by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code means in the form of instructions or data structures and that can be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.

Claim 1:
A method for wireless communication at a user equipment, UE (<NUM>), comprising:
identifying (<NUM>) a random-access preamble (<NUM>) for transmission to a base station (<NUM>) in a random-access channel occasion (<NUM>) as part of a two-step random-access procedure;
identifying (<NUM>) data or control information (<NUM>) for transmission to the base station (<NUM>) as part of the two-step random-access procedure; and characterized by
transmitting (<NUM>) both the random-access preamble (<NUM>) and the data or control information (<NUM>) within the random-access channel occasion (<NUM>).