Preamble and physical uplink shared channel resource ordering and scrambling identifier generation for a two-step random access channel procedure

The deterministic ordering and scrambling identifier generation for preamble and PUSCH resources in two-step RACH procedures address inefficiencies and collisions, enhancing scheduling efficiency and reducing interference in wireless communication systems.

JP7595653B2Active Publication Date: 2024-12-06QUALCOMM INC
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
JP2022520786
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Priority Date
2020-08-04
Filing Date
2020-08-05
Publication Date
2024-12-06
Estimated Expiration
2040-08-05

AI Technical Summary

Technical Problem

Existing two-step random access channel (RACH) procedures in wireless communication systems face inefficiencies in configuring physical uplink shared channel (PUSCH) resources, leading to scheduling inefficiencies, signaling overhead, and high collision probabilities, especially in non-orthogonal multiple access and contention-based random access scenarios.

Method used

Implementing a deterministic or semi-permanent ordering procedure for preamble and PUSCH resources, along with scrambling identifier generation techniques, to enhance the two-step RACH procedure, reducing interference and collision probabilities.

Benefits of technology

The proposed solution improves scheduling efficiency, reduces interference, and lowers collision probabilities in wireless systems using non-orthogonal multiple access and contention-based random access techniques.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007595653000010
    Figure 0007595653000010
  • Figure 0007595653000011
    Figure 0007595653000011
  • Figure 0007595653000012
    Figure 0007595653000012
Patent Text Reader

Abstract

Various aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may receive a random access channel (RACH) occasion (RO) configuration from a base station, the RO configuration including information regarding ordered preamble resources. The UE may generate a preamble resource index according to various parameters selected based on the RO configuration information regarding the ordered preamble resources. The UE may generate an uplink RACH message including a preamble based at least in part on the preamble resource index and a payload associated with a physical uplink shared channel (PUSCH) resource unit (PRU) mapped to the preamble resource index. After decoding the uplink RACH message, the base station may send a response message including scrambled downlink control information (e.g., based on a scrambling identifier or payload information associated with the uplink RACH message). Numerous other aspects are provided.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims priority to U.S. Provisional Application No. 62 / 913,118, filed October 9, 2019, entitled "PREAMBLE AND PHYSICAL UPLINK SHARED CHANNEL RESOURCE ORDERING AND SCRAMBLING IDENTIFIER GENERATION FOR TWO-STEP RACH PROCEDURE," and U.S. Nonprovisional Application No. 16 / 947,493, filed August 4, 2020, entitled "PREAMBLE AND PHYSICAL UPLINK SHARED CHANNEL RESOURCE ORDERING AND SCRAMBLING IDENTIFIER GENERATION FOR TWO-STEP RANDOM ACCESS CHANNEL PROCEDURE," which are expressly incorporated herein by reference.

[0002] Aspects of the present disclosure relate generally to wireless communication and techniques and apparatus for ordering and scrambling identifier generation of preamble and physical uplink shared channel (PUSCH) resources for a two-step random access channel (RACH) procedure. [Background technology]

[0003]

[0003] Wireless communication systems have been widely deployed to provide various telecommunication services, such as telephone, video, data, messaging, and broadcast. A typical wireless communication system may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems, and Long Term Evolution (LTE). LTE / LTE-Advanced is a set of extensions to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the 3rd Generation Partnership Project (3GPP).

[0004] A wireless network may include several base stations (BSs) that can support communication for several user equipment (UEs). The user equipment (UEs) may communicate with the base stations (BSs) via a downlink and an uplink. The downlink (or forward link) refers to the communication link from the BS to the UE, and the uplink (or reverse link) refers to the communication link from the UE to the BS. As described in more detail herein, a BS may be referred to as a Node B, a gNB, an access point (AP), a radio head, a transmit receive point (TRP), a new radio (NR) BS, a 5G Node B, etc.

[0005]

[0005] The above multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that allows different user equipment to communicate on a city, national, regional, or even global scale. New Radio (NR), sometimes referred to as 5G, is a set of extensions to the LTE mobile standard promulgated by the Third Generation Partnership Project (3GPP). NR is designed to better support mobile broadband Internet access by improving spectral efficiency, lowering costs, improving services, utilizing new spectrum, and better integrating with other open standards using Orthogonal Frequency Division Multiplexing (OFDM) with Cyclic Prefix (CP) (CP-OFDM) on the downlink (DL) and CP-OFDM and / or SC-FDM (also known as Discrete Fourier Transform Spread OFDM (DFT-s-OFDM) on the uplink (UL), as well as supporting beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation. As the demand for mobile broadband access continues to grow, further improvements in LTE, NR, and other radio access technologies will remain useful. Summary of the Invention

[0006]

[0006] In some aspects, a method of wireless communication performed by a user equipment (UE) may include receiving a random access channel (RACH) occasion (RO) configuration from a base station including information regarding ordered preamble resources, generating a preamble resource index according to a plurality of parameters selected based at least in part on the information in the RO configuration regarding the ordered preamble resources, and generating an uplink RACH message including a preamble based at least in part on the preamble resource index and a payload associated with a physical uplink shared channel (PUSCH) resource unit (PRU) mapped to the preamble resource index.

[0007] In some aspects, a UE for wireless communication may include a memory and one or more processors operably coupled to the memory. The memory and the one or more processors may be configured to receive an RO configuration from a base station including information regarding ordered preamble resources, generate a preamble resource index according to a plurality of parameters selected based at least in part on the information in the RO configuration regarding the ordered preamble resources, and generate an uplink RACH message including a preamble based at least in part on the preamble resource index and a payload associated with a PRU mapped to the preamble resource index.

[0008] In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. The one or more instructions, when executed by one or more processors of a UE, may cause the one or more processors to receive from a base station an RO configuration including information regarding ordered preamble resources, generate a preamble resource index according to a plurality of parameters selected based at least in part on the information in the RO configuration regarding the ordered preamble resources, and generate an uplink RACH message including a preamble based at least in part on the preamble resource index and a payload associated with a PRU mapped to the preamble resource index.

[0009]

[0009] In some aspects, an apparatus for wireless communications may include means for receiving an RO configuration from a base station including information regarding ordered preamble resources, means for generating a preamble resource index according to a plurality of parameters selected based at least in part on the information in the RO configuration regarding the ordered preamble resources, and means for generating an uplink RACH message including a preamble based at least in part on the preamble resource index and a payload associated with a PRU mapped to the preamble resource index.

[0010]

[0010] Aspects generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication devices, and / or processing systems substantially as described in this specification with reference to and as illustrated by the drawings and specification.

[0011]

[0011] The above outlines rather broadly the features and technical advantages of the examples according to the present disclosure so that the following detailed description may be better understood. Additional features and advantages are described below. The concepts and examples disclosed may be readily utilized as a basis for modifying or designing other structures for carrying out the same purposes of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both their organization and the method of operation, together with associated advantages, will be better understood from the following description when considered in conjunction with the accompanying figures. Each of the figures is provided for illustration and description, and is not intended as a definition of the limits of the claims.

[0012]

[0012] In order that the above-mentioned features of the present disclosure may be understood in detail, a more specific description briefly summarized above may be obtained by referring to the embodiments, some of which are shown in the attached drawings. However, it should be noted that the attached drawings show only some typical embodiments of the present disclosure, and therefore should not be considered as limiting the scope of the present disclosure, since the description may lead to other equally effective embodiments. The same reference numbers in different drawings may identify the same or similar elements. [Brief description of the drawings]

[0013] [Figure 1]

[0013] FIG. 1 illustrates an example of a wireless network in accordance with various aspects of the present disclosure. [Diagram 2]

[0014] FIG. 2 illustrates an example of a base station in communication with a UE in a wireless network, in accordance with various aspects of the present disclosure. [Diagram 3]

[0015] FIG. 2 illustrates an example two-step random access channel (RACH) procedure, in accordance with various aspects of the present disclosure. [Figure 4]

[0016] 1 illustrates an example random access message including a preamble and a payload, in accordance with various aspects of the present disclosure. [Diagram 5]

[0017] 1 is a block diagram illustrating an example mapping between a preamble and a physical uplink shared channel (PUSCH) resource unit (PRU), in accordance with various aspects of the present disclosure. [Figure 6]

[0018] 1 is a block diagram illustrating an example RACH occasion (RO) shared between a two-step RACH procedure and a four-step RACH procedure, in accordance with various aspects of the present disclosure. [Figure 7A]

[0019] 1 illustrates an example implementation of ordering of preamble and PUSCH resources and generation of one or more scrambling identifiers for a two-step RACH procedure, in accordance with various aspects of the present disclosure. [Figure 7B] 1 illustrates an example implementation of ordering of preamble and PUSCH resources and generation of one or more scrambling identifiers for a two-step RACH procedure, in accordance with various aspects of the present disclosure. [Figure 7C] 1 illustrates an example implementation of ordering of preamble and PUSCH resources and generation of one or more scrambling identifiers for a two-step RACH procedure, in accordance with various aspects of the present disclosure. [Figure 8]

[0020] 4 illustrates an example process performed, for example, by a UE, in accordance with various aspects of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0014]

[0021] Various aspects of the present disclosure will be described more fully below with reference to the accompanying drawings. However, the present disclosure may be embodied in many different forms and should not be construed as limited to any particular structure or function presented throughout the present disclosure. Instead, these aspects are provided so that the disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. Based on the teachings herein, those skilled in the art should appreciate that the scope of the present disclosure encompasses any aspect of the present disclosure disclosed herein, whether implemented independently or in combination with any other aspect of the present disclosure. For example, an apparatus may be implemented and a method may be practiced using any number of the aspects described herein. In addition, the scope of the present disclosure encompasses an apparatus or method practiced using other structures, functions, or structures and functions in addition to or other than the various aspects of the present disclosure described herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of a claim.

[0015]

[0022] Several aspects of a telecommunications system are now presented with reference to various apparatus and techniques that are described in the detailed description that follows and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using hardware, software, or a combination thereof. Whether such elements are implemented as hardware or software depends on the particular application and design constraints imposed on the overall system.

[0016]

[0023] Although aspects may be described herein using terminology commonly associated with 5G or NR radio access technologies (RATs), it should be noted that aspects of the disclosure may apply to other RATs, such as 3G RATs, 4G RATs, and / or RATs subsequent to 5G (e.g., 6G).

[0017]

[0024] FIG. 1 illustrates an example of a wireless network 100 according to various aspects of the disclosure. The wireless network 100 may be or include an element of a 5G (NR) network, an LTE network, or the like. The wireless network 100 may include several base stations 110 (shown as BS 110a, BS 110b, BS 110c, and BS 110d) and other network entities. A base station (BS) is an entity that communicates with user equipment (UE) and may also be referred to as an NR BS, Node B, gNB, 5G Node B (NB), access point, transmit / receive point (TRP), and the like. Each BS may provide communication coverage for a particular geographic area. In 3GPP, the term "cell" can refer to a coverage area of ​​a BS and / or a BS subsystem serving this coverage area, depending on the context in which the term is used.

[0018]

[0025] A BS may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a few kilometers in radius) and may allow unrestricted access by UEs with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs having an association with a femto cell (e.g., a UE in a Closed Subscriber Group (CSG)). A BS for a macro cell may be referred to as a macro BS. A BS for a pico cell may be referred to as a pico BS. A BS for a femto cell may be referred to as a femto BS or a home BS. In the example shown in FIG. 1, BS 110a may be a macro BS for macro cell 102a, BS 110b may be a pico BS for pico cell 102b, and BS 110c may be a femto BS for femto cell 102c. A BS may support one or multiple (e.g., three) cells. The terms “eNB,” “base station,” “NR BS,” “gNB,” “TRP,” “AP,” “Node B,” “5G NB,” and “cell” may be used interchangeably herein.

[0019]

[0026] In some aspects, the cells may not necessarily be fixed and the geographic area of ​​the cells may move according to the location of the mobile BS. In some aspects, the BSs may be interconnected to each other and / or to one or more other BSs or network nodes (not shown) in wireless network 100 through various types of backhaul interfaces, such as direct physical connections, virtual networks, etc., using any suitable transport network.

[0020]

[0027] The wireless network 100 may also include relay stations. A relay station is an entity that can receive a transmission of data from an upstream station (e.g., a BS or a UE) and send the transmission of the data to a downstream station (e.g., a UE or a BS). A relay station may also be a UE that can relay a transmission for another UE. In the example shown in FIG. 1, a relay BS 110d may communicate with a macro BS 110a and a UE 120d to facilitate communication between the BS 110a and the UE 120d. A relay BS may also be referred to as a relay station, a relay base station, a relay, etc.

[0021]

[0028] The wireless network 100 may be a heterogeneous network including different types of BSs, e.g., macro BSs, pico BSs, femto BSs, relay BSs, etc. These different types of BSs may have different transmit power levels, different coverage areas, and different impacts on interference in the wireless network 100. For example, a macro BS may have a high transmit power level (e.g., 5-40 watts), while a pico BS, femto BS, and relay BS may have a lower transmit power level (e.g., 0.1-2 watts).

[0022]

[0029] A network controller 130 may couple to a set of BSs and provide coordination and control for these BSs. The network controller 130 may communicate with the BSs via a backhaul. The BSs may also communicate with each other directly or indirectly, for example, via a wireless or wireline backhaul.

[0023]

[0030] The UEs 120 (e.g., 120a, 120b, 120c) may be dispersed throughout the wireless network 100, and each UE may be fixed or mobile. A UE may also be referred to as an access terminal, terminal, mobile station, subscriber unit, station, etc. A UE may be a cellular phone (e.g., a smartphone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device or equipment, a biometric sensor / device, a wearable device (smart watch, smart clothing, smart glasses, smart wristband, smart jewelry (e.g., smart ring, smart bracelet)), an entertainment device (e.g., a music or video device, or a satellite radio), a vehicle component or sensor, a smart meter / sensor, industrial manufacturing equipment, a global positioning system device, or any other suitable device configured to communicate over a wireless or wired medium.

[0024]

[0031] Some UEs may be considered as Machine Type Communication (MTC) UEs or evolved or enhanced Machine Type Communication (eMTC) UEs. MTC UEs and eMTC UEs include, for example, a robot, a drone, a remote device, a sensor, a meter, a monitor, a location tag, etc., that may communicate with a base station, another device (e.g., a remote device), or some other entity. A wireless node may provide, for example, connectivity for or to a network (e.g., a wide area network such as the Internet or a cellular network) via a wired or wireless communication link. Some UEs may be considered as Internet of Things (IoT) devices and / or implemented as NB-IoT (Narrowband Internet of Things) devices. Some UEs may be considered as Customer Premises Equipment (CPE). The UE 120 may be included in a housing that stores components of the UE 120, such as a processor component, a memory component, etc. In some aspects, the processor component and the memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., memory) may be operatively coupled, communicatively coupled, electronically coupled, electrically coupled, etc.

[0025]

[0032] Generally, any number of wireless networks may be deployed in a given geographic area. Each wireless network may support a particular RAT and may operate on one or more frequencies. The RAT may also be referred to as a radio technology, an air interface, etc. The frequencies may also be referred to as a carrier, a frequency channel, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

[0026]

[0033] In some aspects, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly (e.g., without using a base station 110 as an intermediary to communicate with each other) using one or more sidelink channels. For example, the UEs 120 may communicate using peer-to-peer (P2P) communications, device-to-device (D2D) communications, vehicle-to-everything (V2X) protocols (which may include, e.g., vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, etc.), mesh networks, etc. In this case, the UEs 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by the base station 110.

[0027]

[0034] The devices of the wireless network 100 may communicate using an electromagnetic spectrum, which may be subdivided into various classes, bands, channels, etc., based on frequency or wavelength. For example, the devices of the wireless network 100 may communicate using an operating band having a first frequency range (FR1), which may range from 410 MHz to 7.125 GHz, and / or may communicate using an operating band having a second frequency range (FR2), which may range from 24.25 GHz to 52.6 GHz. Frequencies between FR1 and FR2 may be referred to as mid-band frequencies. FR1 is often referred to as the "sub-6 GHz" band, although a portion of FR1 is greater than 6 GHz. Similarly, FR2 is often referred to as "millimeter wave" even though it is different from the extra-high frequency (EHF) band (30 GHz to 300 GHz) identified as the "millimeter wave" band by the International Telecommunications Union (ITU). Thus, unless otherwise specified, it should be understood that terms such as "sub-6 GHz," as used herein, may broadly refer to frequencies below 6 GHz, frequencies within FR1, and / or mid-band frequencies (e.g., greater than 7.125 GHz). Similarly, unless otherwise specified, it should be understood that terms such as "millimeter wave," as used herein, may broadly refer to frequencies within the EHF band, frequencies within FR2, and / or mid-band frequencies (e.g., less than 24.25 GHz). It is contemplated that the frequencies included within FR1 and FR2 may be modified, and that the techniques described herein are applicable to those modified frequency bands.

[0028]

[0035] As noted above, Figure 1 is provided as an example. Other examples may differ from those described with respect to Figure 1.

[0029]

[0036] 2 is a diagram illustrating an example base station 200 in communication with a UE 120 in a wireless network 100 in accordance with various aspects of the present disclosure. The base station 110 may be equipped with T antennas 234a through 234t, and the UE 120 may be equipped with R antennas 252a through 252r, where in general, T≧1 and R≧1.

[0030]

[0037] At the base station 110, a transmit processor 220 may receive data from a data source 212 for one or more UEs, select one or more modulation and coding schemes (MCSs) for each UE based at least in part on a channel quality indicator (CQI) received from the UE, process (e.g., encode and modulate) the data for each UE based at least in part on the MCS selected for that UE, and provide data symbols for all UEs. The transmit processor 220 may also process system information (e.g., for semi-static resource partitioning information (SRPI), etc.) and control information (e.g., CQI requests, grants, higher layer signaling, etc.) and provide overhead symbols and control symbols. The transmit processor 220 may also generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS), demodulation reference signals (DMRS), etc.) and synchronization signals (e.g., primary synchronization signals (PSS) and secondary synchronization signals (SSS)). A transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on ​​the data symbols, control symbols, overhead symbols, and / or reference symbols, if applicable, and may provide T output symbol streams to T modulators (MODs) 232a through 232t. Each modulator 232 may process a respective output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator 232 may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. The T downlink signals from modulators 232a through 232t may be transmitted via T antennas 234a through 234t, respectively.

[0031]

[0038] At the UE 120, antennas 252a-252r may receive downlink signals from the base station 110 and / or other base stations and may provide received signals to demodulators (DEMODs) 254a-254r, respectively. Each demodulator 254 may condition (e.g., filter, amplify, downconvert, and digitize) the received signal to obtain input samples. Each demodulator 254 may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. A MIMO detector 256 may obtain received symbols from all R demodulators 254a-254r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. A receive processor 258 may process (e.g., demodulate and decode) the detected symbols, provide decoded data for the UE 120 to a data sink 260, and provide decoded control and system information to a controller / processor 280. The term “controller / processor” may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a reference signal received power (RSRP), a received signal strength indicator (RSSI), a reference signal received quality (RSRQ), a channel quality indicator (CQI), etc. In some aspects, one or more components of the UE 120 may be included in a housing 284.

[0032]

[0039] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include one or more devices in a core network, for example. The network controller 130 may communicate with the base station 110 via the communication unit 294.

[0033]

[0040] On the uplink, at the UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information from a controller / processor 280 (e.g., for reporting including RSRP, RSSI, RSRQ, CQI, etc.). The transmit processor 264 may also generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be precoded by a TX MIMO processor 266, if applicable, further processed by modulators 254a-254r (e.g., for DFT-s-OFDM, CP-OFDM, etc.), and transmitted to the base station 110. In some aspects, the UE 120 includes a transceiver. The transceiver may include any combination of antennas 252, modulators and / or demodulators 254, MIMO detectors 256, receive processors 258, transmit processors 264, and / or TX MIMO processors 266. The transceiver may be used by a processor (e.g., controller / processor 280) and memory 282 to implement aspects of any of the methods described herein, for example, as described with reference to Figures 3-8.

[0034]

[0041] At the base station 110, uplink signals from the UE 120 and other UEs may be received by the antennas 234, processed by the demodulator 232, detected by the MIMO detector 236, if applicable, and further processed by the receive processor 238 to obtain decoded data and control information sent by the UE 120. The receive processor 238 may provide the decoded data to a data sink 239 and the decoded control information to the controller / processor 240. The base station 110 may include a communication unit 244 and may communicate to the network controller 130 via the communication unit 244. The base station 110 may include a scheduler 246 to schedule the UE 120 for downlink and / or uplink communication. In some aspects, the base station 110 includes a transceiver. The transceiver may include any combination of the antennas 234, the modulators and / or demodulators 232, the MIMO detector 236, the receive processor 238, the transmit processor 220, and / or the TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to implement aspects of any of the methods described herein, for example, as described with reference to Figures 3-8.

[0035]

[0042] The controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or any other components of FIG. 2 may perform one or more techniques related to ordering and scrambling identifier generation of preamble and physical uplink shared channel (PUSCH) resources for a two-step random access channel (RACH) procedure, as described in more detail elsewhere herein. For example, the controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or any other components of FIG. 2 may perform or direct the operation of, for example, process 800 of FIG. 8 and / or other processes described herein. The memories 242 and 282 may store data and program codes for the base station 110 and the UE 120, respectively. In some aspects, the memory 242 and / or the memory 282 may include a non-transitory computer-readable medium having stored thereon one or more instructions (e.g., code, program code, etc.) for wireless communication. For example, the one or more instructions, when executed by one or more processors of the base station 110 and / or the UE 120 (e.g., directly or after compilation, translation, interpretation, etc.), may cause the one or more processors, the UE 120, and / or the base station 110 to perform or direct operations of, for example, process 800 of FIG. 8 and / or other processes described herein. In some aspects executing the instructions may include executing the instructions, converting the instructions, compiling the instructions, interpreting the instructions, etc.

[0036]

[0043] In some aspects, the UE 120 may include means for receiving a RACH occasion (RO) configuration from the base station 110 including information regarding ordered preamble resources, means for generating a preamble resource index according to a plurality of parameters selected based at least in part on the information in the RO configuration regarding ordered preamble resources, means for generating an uplink RACH message including a preamble based at least in part on the preamble resource index and a payload associated with a PUSCH resource unit (PRU) mapped to the preamble resource index, etc. In some aspects, such means may include one or more components of the UE 120 described with respect to FIG. 2, such as the controller / processor 280, the transmit processor 264, the TX MIMO processor 266, the MOD 254, the antennas 252, the DEMOD 254, the MIMO detector 256, the receive processor 258, etc.

[0037]

[0044] 2 are shown as separate components, the functionality described above with respect to those blocks may be implemented in a single hardware, software, or combination component, or various combinations of components. For example, functionality described with respect to transmit processor 264, receive processor 258, and / or TX MIMO processor 266 may be performed by or under the control of controller / processor 280.

[0038]

[0045] As noted above, Figure 2 is provided as an example. Other examples may differ from those described with respect to Figure 2.

[0039]

[0046] A UE may access a wireless network by negotiating a connection with a base station included in the wireless network. During connection establishment, the UE and the base station may synchronize the connection in the downlink direction (e.g., from the base station to the UE) and in the uplink direction (e.g., from the UE to the base station). To synchronize the connection in the downlink direction, the UE may read a synchronization signal block (SSB) that includes various synchronization signals transmitted from the base station. The synchronization signals may include a primary synchronization signal (PSS), a secondary synchronization signal (SSS), etc. The UE may use the PSS to determine symbol timing in the downlink direction and may use the SSS to determine a physical cell identifier and frame timing associated with the base station.

[0040]

[0047] To synchronize the connection in the uplink direction, the UE and the base station may perform a RACH procedure. For example, in some cases, the UE and the base station may perform a four-step RACH procedure in which the UE and the base station may exchange four primary RACH communications. The UE may send a msg1 communication to the base station, which may include a RACH preamble communication. The base station may respond to the msg1 communication with a msg2 communication, which may include a random access response (RAR) communication. The UE may respond to the msg2 communication with a msg3 communication, which may include a radio resource control (RRC) connection request communication. The base station may respond to the msg3 communication with a msg4 communication, which may include a medium access control layer control element (MAC-CE) contention resolution identifier communication.

[0041]

[0048] In some cases, the four-step RACH procedure may not meet the low latency requirements of 5G / NR wireless systems. Therefore, the UE and the base station may use a two-step RACH procedure to reduce latency in synchronizing the connection in the uplink direction. In the two-step RACH procedure, the UE may combine the msg1 and msg3 communications into a communication referred to as the msgA communication. The msg1 portion of the msgA communication may be referred to as the preamble portion of the msgA communication, and the msg3 portion of the msgA communication may be referred to as the payload portion of the msgA communication. The UE may transmit the msg1 and msg3 portions consecutively (e.g., according to a time division multiplexing (TDM) configuration) and prior to receiving the msg2 and msg4 communications. The base station may receive the msgA communication and may transmit the msgB communication, which may include the msg2 and msg4 communications.

[0042]

[0049] In some cases, as described above, the msgA communication may include a msgA preamble and a msgA payload. In some cases, the msgA payload may be transmitted using a physical uplink shared channel (PUSCH) resource unit (PRU) mapped to the preamble. For example, the preamble-to-PRU mapping may be one-to-one, many-to-one, or one-to-many. Thus, in some cases, there may be scheduling inefficiencies (e.g., signaling overhead) associated with configuring the PUSCH resources used to transmit the msgA payload. Furthermore, in some cases, there may be an unacceptably high probability of collisions in a wireless system in which a two-step RACH procedure is used with respect to non-orthogonal multiple access (NOMA) and / or contention-based random access (CBRA) techniques.

[0043]

[0050] Accordingly, certain aspects described herein provide techniques and apparatus for ordering preamble and PUSCH resources and generating one or more scrambling identifiers for a two-step RACH procedure. For example, a deterministic or semi-permanent ordering procedure may be used for preamble and / or PUSCH resources to simplify PUSCH resource configuration via system information (SI), RRC signaling, etc., which may reduce signaling overhead, reduce decoding complexity at the base station, etc. Furthermore, certain aspects described herein provide techniques and apparatus for generating scrambling identifiers and demodulation reference signals (DMRSs) for PUSCH transmissions (e.g., msgA payloads), such as to mitigate inter-cell and / or intra-cell interference, reduce collision probability in wireless systems using NOMA and / or CBRA techniques.

[0044]

[0051] 3 is a diagram illustrating an example two-step RACH procedure 300, in accordance with various aspects of the present disclosure. As shown in FIG. 3, the base station 110 and the UE 120 may communicate with each other to perform the two-step RACH procedure.

[0045]

[0052] As indicated by reference numeral 305, the base station 110 may transmit, and the UE 120 may receive, one or more synchronization signal blocks (SSBs) and random access configuration information. In some aspects, the random access configuration information may be transmitted and / or indicated within system information (e.g., one or more system information blocks (SIBs)) and / or SSBs, such as for contention-based random access. Additionally or alternatively, the random access configuration information may include one or more reference signals and / or information transmitted and / or indicated within one or more radio resource control (RRC) signaling messages and / or physical downlink control channel (PDCCH) order messages that trigger a RACH procedure, such as for contention-free random access. Furthermore, as described in more detail elsewhere herein, the random access configuration information may include information regarding one or more RACH occasion (RO) configurations, such as information regarding one or more ordered preamble resources.

[0046]

[0053] As further indicated by reference numeral 310, UE 120 may perform downlink (DL) synchronization (e.g., using one or more SSBs), decode system information (SI) and / or RRC configuration information included in one or more SIBs, perform one or more measurements of one or more reference signals, etc. Based at least in part on the downlink synchronization, decoding the SI and / or RRC configuration information, and / or performing measurements of the reference signals, UE 120 may determine one or more parameters for transmitting a random access message (RAM) in a two-step RACH procedure. For example, UE 120 may determine one or more physical random access channel (PRACH) transmission parameters to be used to transmit the RAM, may determine one or more parameters for generating a preamble for the RAM, may identify one or more uplink leases over which the RAM is to be transmitted, etc.

[0047]

[0054] The UE 120 may transmit, and the base station 110 may receive, a RAM preamble, as indicated by reference numeral 315. The UE 120 may transmit, and the base station 110 may receive, a RAM payload, as indicated by reference numeral 320. As indicated, the UE 120 may transmit a RAM preamble and a RAM payload to the base station 110 as part of an initial (or first) step of a two-step RACH procedure. In some aspects, the RAM may be referred to as a message A, msgA, a first message, an initial message, etc. in a two-step RACH procedure. Further, in some aspects, the RAM preamble may be referred to as a message A preamble, msgA preamble, a preamble, a physical random access channel (PRACH) preamble, etc., and the RAM payload may be referred to as a message A payload, msgA payload, payload, etc. In some aspects, the RAM may include some or all of the contents of message 1 (msg1) and message 3 (msg3) of a four-step RACH procedure. For example, the RAM preamble may include some or all of the contents of message 1 (e.g., a PRACH preamble), and the RAM payload may include some or all of the contents of message 3. For example, in some aspects, the RAM payload may include an identifier associated with UE 120, uplink control information, medium access control (MAC) layer control elements (e.g., power headroom reports, buffer status reports, beam failure reports, channel condition reports, etc.), user plane data, control plane data, etc. Additionally, in some aspects, the msgA preamble and the msgA payload may be time division multiplexed (TDMed) with each other, such that the msgA preamble and the msgA payload may be transmitted in separate symbols based at least in part on a time division multiplexing (TDM) configuration.

[0048]

[0055] As indicated by reference numeral 325, the base station 110 may receive the RAM preamble transmitted by the UE 120. If the base station 110 successfully receives and decodes the RAM preamble, the base station 110 may then receive and decode the RAM payload.

[0049]

[0056] As indicated by reference numeral 330, the base station 110 may transmit a random access response (RAR) (which may be referred to as an RAR message). As indicated, the base station 110 may transmit the RAR message as part of a second step of a two-step RACH procedure. In some aspects, the RAR message may be referred to as message B, msgB, or a second message in a two-step RACH procedure. The RAR message may include some or all of the contents of message 2 (msg2) and message 4 (msg4) of a four-step RACH procedure. For example, the RAR message may include a detected PRACH preamble identifier, a detected UE identifier, a timing advance value, contention resolution information, etc.

[0050]

[0057] As part of the second step of the two-step RACH procedure, the base station 110 may transmit a physical downlink control channel (PDCCH) for the RAR (e.g., to include some or all of the content of msg2 of the four-step RACH procedure) as indicated by reference numeral 335. The PDCCH communication may schedule a physical downlink shared channel (PDSCH) that includes the RAR (e.g., to include some or all of the content of msg4 of the four-step RACH procedure). For example, the PDCCH communication may indicate a resource allocation for the PDSCH communication (e.g., in downlink control information (DCI)).

[0051]

[0058] As indicated by reference numeral 340, as part of the second step of the two-step RACH procedure, the base station 110 may transmit a PDSCH communication for the RAR as scheduled by the PDCCH communication. The RAR may be included within a medium access control (MAC) protocol data unit (PDU) of the PDSCH communication. As indicated by reference numeral 345, the UE may transmit hybrid automatic repeat request (HARQ) feedback to the base station 110 via a physical uplink control channel (PUCCH) based on whether the UE 120 successfully received and decoded the RAR message. For example, the HARQ feedback may include a positive acknowledgement (ACK) if the RAR message is successfully received and decoded by the UE 120, or a negative acknowledgement (NACK) if the UE 120 is unable to successfully receive and / or decode the RAR message.

[0052]

[0059] As noted above, Figure 3 is provided as an example. Other examples may differ from those described with respect to Figure 3.

[0053]

[0060] 4 is a diagram illustrating an example random access message 400 including a preamble and a payload in accordance with various aspects of the present disclosure. As shown, the random access message 400 of the two-step RACH procedure may include a preamble and a payload as described above. The preamble may include a PRACH preamble signal and a (T G The payload may include a first guard period (denoted as GT#1, having a duration of T G As further shown in FIG. 4, the preamble transmission and the payload transmission may include a second guard time (denoted as GT#2, having a duration of T g The signals may be separated in time by a transmission guard time (denoted as T×G, having a length T×G).

[0054]

[0061] As further indicated by reference numeral 405 in FIG. 4, the UE may select one RO and one PRACH sequence to be used to transmit the msgA preamble. For example, as described in more detail elsewhere herein, the UE may select the RO and PRACH sequence based at least in part on one or more shared ROs configured by the base station for the two-step RACH procedure and the four-step RACH procedure, one or more dedicated ROs configured by the base station for the two-step RACH procedure, etc. Furthermore, in some aspects, the base station may configure an ordered set of preamble resources for the shared and / or dedicated ROs, and the UE may select the PRACH sequence based at least in part on the ordered set of preamble resources. As further indicated by reference numeral 410 in FIG. 4, the UE may select a set of DMRS resources and PUSCH occasions to be used to transmit the msgA payload. For example, as described in further detail herein, the UE may select a set of DMRS resources and / or PUSCH occasions based at least in part on a preamble-to-PUSCH resource unit (PRU) mapping. Additionally, in some aspects, the UE may select multiple PRUs to support frequency hopping, repetition of the PUSCH portion of the msgA payload, etc.

[0055]

[0062] As noted above, Figure 4 is provided as an example. Other examples may differ from those described with respect to Figure 4.

[0056]

[0063] FIG. 5 is a block diagram illustrating an example mapping 500 between a preamble and a PRU according to various aspects of the disclosure. In some aspects, the example mapping 500 illustrated in FIG. 5 may be used in a two-step RACH procedure in which an initial uplink message (msgA) includes a preamble and a payload, and the payload may be transmitted using a PRU that is mapped to the preamble. For example, as described above, the preamble and the payload are transmitted separately according to a TDM configuration. Thus, the example mapping 500 illustrated in FIG. 5 may be used to define a relationship between a preamble and a payload associated with msgA (e.g., a UE may select a preamble for transmission within msgA and may further select a PRU for use to transmit the payload based on the selected preamble).

[0057]

[0064] For example, as indicated by reference numeral 505 in FIG. 5, the preamble and PRU may have a one-to-one mapping when the PRU to be used is deterministic. In some aspects, the one-to-one mapping may be used for a general RACH use case (e.g., to synchronize a connection between a UE and a base station in the downlink direction during connection establishment). In another example, as indicated by reference numeral 510, the preamble and PRU may have a one-to-many mapping when the UE may select a PRU from a plurality of PRUs that are mapped to an individual preamble. In some aspects, the one-to-many mapping may be applied in RACH use cases such as PUSCH hopping, transmitting control information (e.g., HARQ feedback, scheduling request, channel state information, etc.), PUSCH payload repetition, etc. In another example, as indicated by reference numeral 515, the preamble and PRU may have a many-to-one mapping where the UE may deterministically select a particular PRU that is mapped to multiple preambles based on the UE selecting one of the multiple preambles that are mapped to the particular PRU. In some aspects, the many-to-one mapping may be applied in RACH use cases such as implementing asynchronous PUSCH transmissions that use a preamble to indicate a modulation coding scheme (MCS).

[0058]

[0065] As noted above, Figure 5 is provided as an example. Other examples may differ from those described with respect to Figure 5.

[0059]

[0066] FIG. 6 is a block diagram illustrating an example 600 of a RACH occasion (RO) shared between a two-step RACH procedure and a four-step RACH procedure in accordance with various aspects of the present disclosure. For example, in some aspects, a wireless network may support both a two-step RACH procedure and a four-step RACH procedure, and one or more ROs may be shared between the two-step RACH procedure and the four-step RACH procedure (e.g., for scheduling efficiency). In general, as described above, one common operation shared between the two-step RACH procedure and the four-step RACH procedure includes preamble transmission. Thus, in both the two-step RACH procedure and the four-step RACH procedure, a UE may select a preamble sequence from a particular RO, which may be defined according to a time resource and a frequency resource. For example, a particular RO may generally include up to 64 preamble sequences (e.g., 32 preamble sequences for a 2-step RACH procedure and 32 preamble sequences for a 4-step RACH procedure), which may be allocated between a 2-step RACH procedure and a 4-step RACH procedure in the case of a shared RO.

[0060]

[0067] As a result, in some cases, a first UE performing a two-step RACH procedure may select msgA from a RO shared between the two-step RACH procedure and the four-step RACH procedure, and a second UE performing a four-step RACH procedure may select a msg1 preamble from the same RO. However, as described above, the msgA preamble is generally followed by a msgA payload transmission, whereas the msg1 preamble includes only a preamble transmission. Thus, when the base station sends a response message (e.g., msgB) to a first UE performing a two-step RACH procedure and a second message (e.g., msg2) to a second UE performing a four-step RACH procedure, one or more techniques may be used to distinguish the first UE from the second UE.

[0061]

[0068] For example, as shown in FIG. 6, the msg2 communication in the four-step RACH procedure may include downlink control information (DCI) transmitted over the PDCCH, PDSCH, etc., and the msg2 DCI may be associated with a cyclic redundancy code (CRC) masked by a random access radio network temporary identifier (RA-RNTI), which may be determined as follows:

[0062]

number

[0063] where s_id is the index of the first OFDM symbol of the designated PRACH (e.g., 0≦s_id<14), t_id is the index of the first slot of the designated PRACH in the system frame (e.g., 0≦t_id<80), f_id is the index of the designated PRACH in the frequency domain (e.g., 0≦f_id<8), and ul_carrier_id is the uplink carrier used for PRACH preamble transmission (e.g., zero (0) for normal uplink (NUL) carrier and one (1) for supplemental uplink (SUL) carrier). As a result, the range of RA-RNTI may be from 1 to 17920 ([1,17920]).

[0064]

[0069] In some aspects, as indicated by reference numeral 605, an RNTI (msgB-RNTI) used to mask DCI associated with the msgB communication may be derived from the RA-RNTI associated with the msg2 communication to avoid ambiguity between the RA-RNTI and the msgB-RNTI. For example, for a UE in an RRC idle or inactive state, the msgB PDCCH may be addressed to the msgB-RNTI, which may be a UE-specific identifier that targets the UE individually or a group identifier that targets a group of UEs sharing a particular RO. In general, the msgB-RNTI may be defined by the RA-RNTI plus a non-zero offset, as follows:

[0065]

number

[0066] where rf_id is the radio frame index associated with the msgB PDCCH transmission. In this way, the RA-RNTI does not overlap with the msgB-RNTI, thereby avoiding ambiguity in PDCCH decoding when a particular RO is shared between 2-step and 4-step RACH procedures.

[0067]

[0070] As noted above, Figure 6 is provided as an example. Other examples may differ from those described with respect to Figure 6.

[0068]

[0071] 7A-7C are diagrams illustrating an example implementation 700 of ordering preamble and PUSCH resources and generating one or more scrambling identifiers for a two-step RACH procedure, in accordance with various aspects of the present disclosure. As shown in FIGs. 7A-7C, the UE and the base station may perform various operations related to ordering preamble and PUSCH resources and generating one or more scrambling identifiers for a two-step RACH procedure.

[0069]

[0072] In FIG. 7A, as indicated by reference numeral 710, a base station may transmit, and a UE may receive, (e.g., via RRC signaling, system information signaling, or other suitable higher layer signaling) an RO configuration including information regarding ordered preamble resources for a two-step RACH procedure. In some aspects, the RO configuration may relate to one or more ROs shared between two-step and four-step RACH procedures and / or one or more ROs dedicated to the two-step RACH procedure. Furthermore, in some aspects, the RO configuration may order preamble resources jointly for shared and dedicated ROs (e.g., the same ordering procedure may be applied to shared and dedicated ROs) or the RO configuration may order preamble resources separately for shared and dedicated ROs (e.g., different ordering procedures may be applied to shared and dedicated ROs).

[0070]

[0073] In some aspects, when the RO configuration concerns one or more ROs shared between two-step RACH procedures and four-step RACH procedures, the preamble sequence may be partitioned or otherwise allocated to the two-step RACH procedures to ensure that UEs performing the two-step RACH procedure and UEs performing the four-step RACH procedure use different preamble sequences. Furthermore, in some aspects, the index of the ordered preamble resource may be repeated within different SSB-RO association periods. For example, in NR, SSBs are generally transmitted using beamforming techniques, whereby beamformed SSBs may have periodicity. Furthermore, there may be an association between SSBs and ROs, which may also be periodic. Thus, since there is generally a finite amount of preamble resource indexes, the preamble resource indexes may be recycled or otherwise repeated within different SSB-RO association periods.

[0071]

[0074] As further indicated in FIG. 7A by reference numeral 720, the UE may generate the msgA preamble resource based at least in part on RO configuration information regarding ordered preamble resources. For example, in some aspects, the RO configuration information may indicate that the msgA preamble resources are consecutively ordered in different domains by various parameters, which may include one or more parameters in the code domain, one or more parameters in the frequency domain, one or more parameters in the time domain, etc. For example, in some aspects, a first parameter (X) may be used to order the msgA preamble resources in the code domain according to an increasing order of preamble sequence index in a particular RO, where 0≦X≦max_preamble_sequence−1, where max_preamble_sequence is a quantity of configured preamble sequences (e.g., 64). Furthermore, a second parameter (Y) may be used to order the msgA preamble resources in the frequency domain according to an increasing order of frequency resource index for frequency division multiplexed ROs, where 0≦Y≦max_number_FDM_RO-1, where max_number_FDM_RO is configured by higher layers (e.g., RRC signaling) and defines the maximum number of ROs that can be frequency division multiplexed (e.g., up to 8). Furthermore, a third parameter (Z) may be used to order the msgA preamble resources in the time domain according to an increasing order of time resource index for time division multiplexed ROs within a PRACH slot, where 0≦Z≦max_number_TDM_RO-1, where max_number_TDM_RO is configured by higher layers and defines the maximum number of ROs that can be frequency division multiplexed.In some aspects, a fourth parameter (W) may also be used to order the msgA preamble resources in the time domain according to increasing order of PRACH slot index, where 0≦W≦max_number_RACH_slot−1, where max_number_RACH_slot is configured by higher layers and defines the maximum number of RACH slots, each of which may contain a quantity of time division multiplexed ROs up to max_number_TDM_RO.

[0072]

[0075] Thus, the ordering procedure may generally indicate that the msgA preamble resources are consecutively ordered by a first parameter (X) in the code domain, followed by a second parameter (Y) in the frequency domain, followed by a third parameter (Z) in the time domain, and followed by a fourth parameter (W) in the time domain. In some aspects, to generate the preamble resource index, the UE may select values ​​for X, Y, Z, and W subject to the constraints described above. In some aspects, the UE may generate the preamble resource index using a function that applies different weights to each of the X, Y, Z, and W parameters. For example, in some aspects, the UE may generate the preamble resource index using the following function:

[0073]

number

[0074]

[0076] Thus, the above function may provide a linear weighted combination based at least in part on the values ​​the UE selects for X, Y, Z, and W, and the preamble resource index may be different for different UEs as long as the values ​​selected for X, Y, Z, and W differ in at least one dimension.

[0075]

[0077] As further indicated in FIG. 7A by reference numeral 730, the UE may configure one or more PUSCH resources for the msgA payload based at least in part on the preamble-to-PRU mapping and PRU ordering. For example, as described above, the msgA payload may be transmitted after the msgA preamble, and the msgA payload may be mapped to a PRU. Thus, as described herein, the UE may follow one or more ordering procedures for PUSCH resource indexes to configure the PUSCH resources for the msgA payload based at least in part on multiple PRU configurations that may be supported for the preconfigured time and frequency resources for the msgA payload. For example, different UEs may transmit the msgA payload using different numbers of resource blocks (RBs) (e.g., three RBs, six RBs, etc.), and the preamble-to-PRU mapping and PRU ordering may be based at least in part on the different PRU configurations supported for the msgA payload.

[0076]

[0078] In some aspects, if the msgA PUSCH resource is configured for multiple PRUs having the same type, when the preamble-to-PRU mapping is one-to-one or many-to-one (e.g., given a particular preamble, the PRUs mapped to the preamble are deterministic), the msgA PRU may be indexed according to the resource index of the msgA preamble selected by the UE. Additionally or alternatively, when the preamble-to-PRU mapping is one-to-many (e.g., multiple PRUs are mapped to the same preamble), the index of the msgA PRU may be based on the resource index of the msgA preamble selected by the UE, which may be based on the PRU group associated with the same preamble.

[0077]

[0079] In some aspects, when the msgA PUSCH resource is configured for multiple PRUs having different types, the ordering of the PRUs may depend on whether the different PRU types overlap within one or more time and / or frequency resources. For example, when two or more PRU types overlap within one or more time and / or frequency resources, the overlapping PRUs may be ordered according to ascending modulation coding scheme (MCS) (e.g., PRUs associated with lower coding rates are ordered before PRUs associated with higher coding rates), ascending TBS (e.g., PRUs associated with smaller TBSs are ordered before PRUs associated with larger TBSs), etc. Alternatively, when the different PRU types do not overlap within the time and / or frequency resources, the non-overlapping PRUs may be ordered according to ascending frequency occasion (e.g., RBs or RB groups (RBGs)), time occasion (e.g., symbols or slots), etc.

[0078]

[0080] In FIG. 7B, as indicated by reference numeral 740, the UE may generate a scrambling identifier for the msgA payload based at least in part on a linear weighted combination of the parameters. In some aspects, in a first technique, the linear weighted combination of the parameters may be the RA-RNTI (R ID ), preamble sequence index (P ID ), and higher layer configuration data scrambling identifier (n ID ) (e.g., a cell identifier that may be indicated in a higher layer parameter such as msgA-dataScramblingIdentity), where the segments do not overlap in the bit extension of the scrambling identifier. For example, in the first technique, the scrambling identifier may be determined as follows:

[0079]

number

[0080] In the formula, C1, C2, and C3 are R ID Parameter, P ID parameters, and n ID is a non-negative integer that may have different values ​​to give different weights to the parameters,

[0081]

number

[0082] is the scrambling identifier, and c init is a value used to initialize a pseudo-noise (PN) sequence generator, which may be equal to a scrambling identifier. For example, in some aspects, C1 may have a value of sixteen (16), C2 may have a value of ten (10), and C3 may have a value of zero (0), as follows:

[0083]

number

[0084] In another example, C1 may have a value of sixteen (16), C2 may have a value of zero (0), and C3 may have a value of six (6), as follows:

[0085]

number

[0086] Alternatively, in the second technique, the linear weighted combination of parameters is a preamble sequence index (P ID ) and higher layer configuration data scrambling identifier (n ID ), plus the truncated RA-RNTI (R * ID), in which case the scrambling identifier may be determined as follows:

[0087]

number

[0088] In the formula, R * ID can be written to contain only one or more sets of the most significant bits. ID Truncate.

[0089]

[0083] Thus, in Figure 7B, reference numeral 750 denotes an exemplary scrambling identifier function based at least in part on the first and second techniques described above. For example, as shown, each of the parameters input to the function may shift one or more most significant bits (MSBs) by different amounts based on a corresponding non-negative integer, C1-C3, and after the MSBs are shifted, the corresponding values ​​may be input to a multiplexer. As further shown in Figure 7B, the multiplexer may generate a scrambling identifier, which is the sum of three weighted terms in the formula given above.

[0090]

number

[0091] The scrambling identifier may then be used to initialize a PN sequence generator, which generates the output used to scramble one or more bits in the msgA payload.

[0092] 7C, as indicated by reference numeral 760, the UE may generate a scrambling identifier for the DMRS associated with msgA based at least in part on the scrambling identifier generated for the msgA payload. Specifically, to reduce the DMRS collision probability for contention-based random access, the pool size for the DMRS resources may be increased by utilizing the scrambling identifier generated for the msgA payload for the PUSCH waveform, which may use cyclic prefix OFDM (CP-OFDM), discrete Fourier transform spread OFDM (DFT-s-OFDM), etc. In some aspects, the scrambling identifier used for the DMRS sequence may be a function of the RA-RNTI, a preamble sequence index, a cell identifier, and one or more time-dependent parameters related to the PUSCH waveform used to transmit the msgA payload. For example, if transform precoding is not enabled for the PUSCH waveform (e.g., the PUSCH waveform uses CP-OFDM), the PN sequence generator for the DMRS sequence may be initialized using a seed that is based at least in part on a scrambling identifier generated for the msgA payload, a slot or symbol index, an OFDM symbol index, etc. Additionally or alternatively, if transform precoding is enabled for the PUSCH waveform (e.g., the PUSCH waveform uses DFT-s-OFDM), multiple groups of DMRS-based sequences may be configured for one cell and the group index may be generated according to a time-dependent hopping pattern, a cell identifier, the RA-RNTI, a preamble sequence index, a scrambling identifier generated for the msgA payload, etc.

[0093] As further indicated by reference numeral 770 in FIG. 7C, the UE may then generate msgA based at least in part on the msgA preamble resource index, the PUSCH resource configured for the msgA payload, a scrambling identifier for the msgA payload, a scrambling identifier for the DMRS, etc. For example, as shown in FIG. 7C, the UE may select a PRACH preamble, which may be input into a radio resource mapping block. Furthermore, in some aspects, the payload and CRC for the msgA transmission may be input into a bit scrambling block, which may scramble one or more bits of the payload and / or CRC according to a scrambling identifier (e.g., after applying channel coding and rate matching to the payload and CRC). The scrambled bits of the payload and / or CRC may be input to a multiplexer (e.g., after applying linear modulation, transform precoding, inverse fast Fourier transform (IFFT), etc. to the scrambled bits) along with a DMRS generated based at least in part on the uplink control information to be transmitted on the msgA PUSCH and the preamble-to-PRU mapping. Additionally, as described above, the bits of the DMRS may be scrambled using a scrambling identifier based at least in part on the scrambling identifier used to scramble the payload and / or CRC bits. Thus, the output from the multiplexer may be provided to a radio resource mapping block that generates msgA based at least in part on the PRACH preamble and the output from the multiplexer.

[0094]

[0086] In FIG. 7C, as further indicated by reference numeral 780, the UE may transmit msgA to a shared or dedicated RO configured by the base station. For example, as described above, the UE may transmit a msgA preamble in a first symbol and then transmit a msgA payload in a second symbol. In some aspects, as described herein, the payload may carry a unique identifier associated with the UE, a MAC-CE (e.g., a power headroom report, a buffer status report, a beam failure report, a channel condition report, etc.), user plane data, control plane data, etc. In FIG. 7C, as further indicated by reference numeral 790, the base station may transmit, and the UE may receive, msgB from the base station in response to the msgA transmission. For example, in some aspects, msgB may be a downlink message including a PDCCH with a CRC masked by the RNTI and a PDSCH carrying at least a portion of an identifier associated with the UE. For example, the RNTI that masks the CRC of the PDCCH may be a UE-specific identifier that targets the UE individually or a group identifier that targets a group of UEs sharing a particular RO. In the former case, the RNTI may be based at least in part on a scrambling identifier generated for the msgA payload (or PUSCH), a scrambling identifier generated for a DMRS associated with the msgA communication, a preamble resource index, an identifier associated with the UE, etc. In the latter case, when the RNTI that masks the CRC of the PDCCH is a group identifier that targets a group of UEs sharing a particular RO, the RNTI may be based at least in part on a resource index associated with the particular RO shared by the group of UEs, a common time and frequency resource index associated with one or more PRUs shared by the group of UEs, a common DMRS resource index shared by the group of UEs, a frequency resource index associated with msgB, etc.

[0095]

[0087] As noted above, Figures 7A-7C are provided as an example. Other examples may differ from those described with respect to Figures 7A-7C.

[0096] 8 illustrates an example process 800, performed, for example, by a UE, in accordance with various aspects of the present disclosure. The example process 800 is an example in which a UE (such as, for example, UE 120) performs operations related to ordering preamble and PUSCH resources and generating one or more scrambling identifiers for a two-step RACH procedure.

[0097] 8, in some aspects, the process 800 may include receiving an RO configuration from a base station including information regarding the ordered preamble resources (block 810). For example, the UE may receive the RO configuration from the base station including information regarding the ordered preamble resources (e.g., using the antennas 252, the DEMOD 254, the MIMO detector 256, the receive processor 258, the controller / processor 280, the memory 282, etc.), as described above.

[0098] 8, in some aspects, the process 800 may include generating a preamble resource index according to a plurality of parameters selected based at least in part on information in the RO configuration regarding ordered preamble resources (block 820). For example, the UE may generate a preamble resource index (e.g., using the controller / processor 280, the memory 282, etc.) according to a plurality of parameters selected based at least in part on information in the RO configuration regarding ordered preamble resources, as described above.

[0099] 8, in some aspects, the process 800 may include generating an uplink RACH message including a preamble based at least in part on the preamble resource index and a payload associated with the PRU mapped to the preamble resource index (block 830). For example, the UE may generate (e.g., using the controller / processor 280, memory 282, etc.) an uplink RACH message including a preamble based at least in part on the preamble resource index and a payload associated with the PRU mapped to the preamble resource index, as described above.

[0100]

[0092] Process 800 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in connection with one or more other processes described elsewhere in this specification.

[0101]

[0093] In a first aspect, the information in the RO configuration relates to one or more ROs dedicated to a two-step RACH procedure or one or more ROs shared between a two-step RACH procedure and a four-step RACH procedure.

[0102]

[0094] In a second aspect, alone or in combination with the first aspect, the information regarding the ordered preamble resources includes one or more indices that are repeated within different SSB-RO association periods.

[0103]

[0095] In a third aspect, alone or in combination with one or more of the first and second aspects, the information regarding the ordered preamble resources indicates that the preamble resources are consecutively ordered based at least in part on a preamble sequence index within a RO, a frequency resource index for a set of ROs associated with an FDM configuration, a time resource index for a set of ROs associated with a TDM configuration within a PRACH slot, and a set of PRACH slot indices.

[0104]

[0096] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the multiple parameters used to generate the preamble resource index include a first parameter selected from a preamble sequence index in the RO, a second parameter selected from a frequency resource index for a set of ROs associated with an FDM configuration, a third parameter selected from a time resource index for a set of ROs associated with a TDM configuration, and a fourth parameter selected from a set of PRACH slot indices.

[0105]

[0097] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the preamble resource index is generated based at least in part on a function that assigns a different weight to each parameter of a plurality of parameters.

[0106]

[0098] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the PRU configuration associated with the payload is one of a plurality of PRU configurations associated with time resources and frequency resources configured for the uplink RACH message.

[0107]

[0099] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the multiple PRU configurations are indexed at least in part based on an index associated with the ordered preamble resource.

[0108]

[0100] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, generating an uplink RACH message includes ordering a plurality of PRU configurations according to one or more criteria, and selecting a PRU configuration associated with a payload from the plurality of PRU configurations based at least in part on the ordering.

[0109]

[0101] In a ninth aspect, either alone or in combination with one or more of the first to eighth aspects, the one or more criteria used to order the multiple PRU configurations include one or more of an ascending modulation coding scheme or an ascending transport block size based at least in part on the multiple PRU configurations that overlap within one or more of the time or frequency resources.

[0110]

[0102] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, one or more criteria used to order the multiple PRU configurations include one or more of ascending frequency occasions or ascending time occasions based at least in part on the multiple PRU configurations not overlapping within time or frequency resources.

[0111]

[0103] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, generating an uplink RACH message includes generating a scrambling identifier for the payload according to a set of parameters based at least in part on an index associated with the preamble, and scrambling the payload using the scrambling identifier.

[0112]

[0104] In a twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, the set of parameters used to generate the scrambling identifier is further based at least in part on the RA-RNTI and a data scrambling identifier configured by the base station.

[0113]

[0105] In a thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, the scrambling identifier is generated based at least in part on a function that assigns a different weight to each parameter of the set of parameters.

[0114]

[0106] In a fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, generating the uplink RACH message further includes generating a DMRS sequence associated with the uplink RACH message, wherein the DMRS sequence is scrambled at least in part based on a scrambling identifier for the payload and one or more time-dependent parameters associated with a PUSCH waveform used to transmit the payload.

[0115]

[0107] In a fifteenth aspect, alone or in combination with one or more of the first to fourteenth aspects, the uplink RACH message is associated with a two-step RACH procedure.

[0116]

[0108] In a sixteenth aspect, alone or in combination with one or more of the first to fifteenth aspects, the process 800 further includes transmitting a preamble associated with the uplink RACH message and a payload associated with the uplink RACH message to a base station, wherein the preamble and the payload are transmitted within separate symbols based at least in part on a time division multiplexing configuration, and wherein the payload carries at least one of a unique identifier associated with the UE, a MAC-CE, or user plane or control plane data.

[0117]

[0109] In a 17th aspect, alone or in combination with one or more of the 1st to 16th aspects, the process 800 further includes receiving a downlink response message to the uplink RACH message from the base station, where the downlink response message includes a PDCCH and a PDSCH, where the PDCCH includes a CRC masked by the RNTI, and where the PDSCH carries at least a portion of an identifier associated with the UE.

[0118]

[0110] In an 18th aspect, alone or in combination with one or more of the 1st to 17th aspects, the RNTI that masks the CRC of the PDCCH is a UE-specific identifier that individually targets the UE, and the RNTI is based at least in part on one or more of a data scrambling identifier for the PUSCH, a DMRS scrambling identifier associated with the uplink RACH message, a preamble resource index, or an identifier associated with the UE that is carried within the payload of the uplink RACH message.

[0119]

[0111] In a 19th aspect, alone or in combination with one or more of the 1st to 18th aspects, the RNTI that masks the CRC of the PDCCH is a group identifier targeting a group of UEs sharing a particular RO, and the RNTI is based at least in part on one or more of a resource index associated with the particular RO shared by the group of UEs, a common time and frequency resource index associated with one or more PRUs shared by the group of UEs, a common DMRS resource index shared by the group of UEs, or a time and frequency resource index associated with a downlink response message.

[0120]

[0112] Although Figure 8 illustrates example blocks of process 800, in some aspects process 800 may include additional blocks, fewer blocks, different blocks, or blocks configured differently than those illustrated in Figure 8. Additionally or alternatively, two or more of the blocks of process 800 may be performed in parallel.

[0121]

[0113] The above disclosure provides illustrations and descriptions, and is not intended to be exhaustive or to limit the embodiments to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or acquired from practice of the embodiments.

[0122]

[0114] As used herein, the term "component" is intended to be broadly interpreted as hardware, firmware, and / or a combination of hardware and software. As used herein, a processor is implemented in hardware, firmware, and / or a combination of hardware and software.

[0123]

[0115] As used herein, satisfying a threshold may refer to a value being greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, etc., depending on the context.

[0124]

[0116] It should be apparent that the systems and / or methods described herein may be implemented in different forms of hardware, firmware, and / or a combination of hardware and software. The actual special control hardware or software code used to implement these systems and / or methods is not a limiting aspect. Thus, the operation and behavior of the systems and / or methods are described herein without reference to specific software code, and it is understood that software and hardware may be designed to implement the systems and / or methods based at least in part on the description herein.

[0125]

[0117] Although certain combinations of features are recited in the claims and / or disclosed herein, these combinations do not limit the disclosure of the various aspects. In fact, many of these features may be combined in ways not specifically recited in the claims and / or disclosed herein. Although each dependent claim described below may depend directly on only one claim, the disclosure of the various aspects includes each dependent claim in combination with any other claims in the claims. A phrase referring to "at least one of" a list of items refers to any combination of those items, including single members. As an example, "at least one of a, b, or c" is intended to include a, b, c, ab, ac, bc, and abc, as well as any combination with multiple identical elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc, or any other ordering of a, b, and c).

[0126]

[0118] No element, act, or instruction used herein should be construed as critical or essential unless expressly described as such. Also, the articles "a" and "an" as used herein include one or more items and may be used interchangeably with "one or more." Furthermore, the article "the" as used herein is intended to include one or more items referenced in relation to the article "the" and may be used interchangeably with "one or more." Furthermore, the terms "set" and "group" as used herein include one or more items (e.g., related items, unrelated items, combinations of related and unrelated items, etc.) and may be used interchangeably with "one or more." When only one item is intended, the phrase "only one" or similar language is used. Also, terms such as "has," "have," and "having" as used herein are intended to be open-ended terms. Furthermore, the phrase "based on" is intended to mean "based at least in part on" unless otherwise specified. Also, as used herein, the term "or" is intended to be inclusive when used in a sequence and can be used interchangeably with "and / or" (e.g., when used in combination with "either" or "only one of"), unless otherwise stated. The invention as described in the claims of the original application is set forth below. [C1] 1. A method of wireless communication implemented by a user equipment (UE), comprising: receiving a random access channel (RACH) occasion (RO) configuration from a base station, the RO configuration including information regarding ordered preamble resources; generating a preamble resource index according to a plurality of parameters selected based at least in part on the information in the RO configuration regarding the ordered preamble resources; and generating an uplink RACH message including a preamble based at least in part on the preamble resource index and a payload associated with a physical uplink shared channel (PUSCH) resource unit (PRU) mapped to the preamble resource index. [C2] The method of C1, wherein the information in the RO configuration relates to one or more ROs dedicated to a two-step RACH procedure or one or more ROs shared between the two-step RACH procedure and a four-step RACH procedure. [C3] The method of claim 1, wherein the information regarding the ordered preamble resources includes one or more indexes that are repeated within different synchronization signal block (SSB)-RO association periods. [C4] 5. The method of claim 1, wherein the information about the ordered preamble resources indicates that the preamble resources are consecutively ordered based at least in part on a preamble sequence index within an RO, a frequency resource index for a set of ROs associated with a frequency division multiplexing (FDM) configuration, a time resource index for a set of ROs associated with a time division multiplexing (TDM) configuration within a physical RACH (PRACH) slot, and a set of PRACH slot indices. [C5] The method of claim 4, wherein the plurality of parameters used to generate the preamble resource index includes a first parameter selected from the preamble sequence index in the RO, a second parameter selected from the frequency resource index for the set of ROs associated with the FDM configuration, a third parameter selected from the time resource index for the set of ROs associated with the TDM configuration, and a fourth parameter selected from the set of PRACH slot indexes. [C6] The method of C1, wherein the preamble resource index is generated based at least in part on a function that assigns a different weight to each parameter of the plurality of parameters. [C7] The method of claim 1, wherein the PRU configuration associated with the payload is one of a plurality of PRU configurations associated with time and frequency resources configured for the uplink RACH message. [C8] The method of C7, wherein the plurality of PRU configurations are indexed based at least in part on an index associated with the ordered preamble resource. [C9] generating the uplink RACH message, ordering the plurality of PRU configurations according to one or more criteria; and selecting the PRU configuration associated with the payload from the plurality of PRU configurations based at least in part on the ordering. [C10] The method of claim 9, wherein the one or more criteria used to order the multiple PRU configurations include one or more of an ascending modulation coding scheme or an ascending transport block size based at least in part on the multiple PRU configurations overlapping within one or more of the time resources or the frequency resources. [C11] The method of C9, wherein the one or more criteria used to order the multiple PRU configurations include one or more of ascending frequency occasions or ascending time occasions based at least in part on the multiple PRU configurations not overlapping within the time or frequency resources. [C12] generating the uplink RACH message, generating a scrambling identifier for the payload according to a set of parameters based at least in part on an index associated with the preamble; scrambling the payload using the scrambling identifier. [C13] The method of claim 12, wherein the set of parameters used to generate the scrambling identifier is further based at least in part on a random access radio network temporary identifier and a data scrambling identifier configured by the base station. [C14] The method of C12, wherein the scrambling identifier is generated based at least in part on a function that applies a different weighting to each parameter of the set of parameters. [C15] The method of claim 12, wherein generating the uplink RACH message further includes generating a demodulation reference signal (DMRS) sequence associated with the uplink RACH message, wherein the DMRS sequence is scrambled based at least in part on the scrambling identifier for the payload and one or more time-dependent parameters associated with a PUSCH waveform used to transmit the payload. [C16] The method according to C1, wherein the uplink RACH message is associated with a two-step RACH procedure. [C17] transmitting the preamble associated with the uplink RACH message and the payload associated with the uplink RACH message to the base station, where the preamble and the payload are transmitted within separate symbols based at least in part on a time division multiplexing configuration, where the payload carries at least one of a unique identifier associated with the UE, a medium access control layer control element, or user plane or control plane data. The method of C1, further comprising: [C18] receiving a downlink response message from the base station to the uplink RACH message, where the downlink response message includes a Physical Downlink Control Channel (PDCCH) and a Physical Downlink Shared Channel (PDSCH), where the PDCCH includes a Cyclic Redundancy Code (CRC) masked by a Radio Network Temporary Identifier (RNTI), and where the PDSCH carries at least a portion of the identifier associated with the UE; The method of C17, further comprising: [C19] The method of claim 18, wherein the RNTI that masks the CRC of the PDCCH is a UE-specific identifier that individually targets the UE, and the RNTI is based at least in part on one or more of a data scrambling identifier for a physical uplink shared channel, a demodulation reference signal scrambling identifier associated with the uplink RACH message, the preamble resource index, or the identifier associated with the UE that is carried within the payload of the uplink RACH message. [C20] The method of claim 18, wherein the RNTI that masks the CRC of the PDCCH is a group identifier that targets a group of UEs that share a particular RO, and the RNTI is based at least in part on one or more of a resource index associated with the particular RO shared by the group of UEs, a common time and frequency resource index associated with one or more PRUs shared by the group of UEs, a common demodulation reference signal resource index shared by the group of UEs, or a time and frequency resource index associated with the downlink response message. [C21] A user equipment (UE) for wireless communications, comprising: Memory, and one or more processors operably coupled to the memory, wherein the memory and the one or more processors: Receive a random access channel (RACH) occasion (RO) configuration from a base station, the RO configuration including information regarding ordered preamble resources; generating a preamble resource index according to a plurality of parameters selected based at least in part on the information in the RO configuration regarding the ordered preamble resources; and a user equipment (UE) configured to generate an uplink RACH message including a preamble based at least in part on the preamble resource index and a payload associated with a physical uplink shared channel (PUSCH) resource unit (PRU) mapped to the preamble resource index. [C22] The UE of C21, wherein the information in the RO configuration relates to one or more ROs dedicated to a two-step RACH procedure or one or more ROs shared between the two-step RACH procedure and a four-step RACH procedure. [C23] The UE of C21, wherein the information regarding the ordered preamble resource includes one or more indexes that are repeated within different synchronization signal block (SSB)-RO association periods. [C24] UE as described in C21, wherein the information regarding the ordered preamble resources indicates that the preamble resources are consecutively ordered based at least in part on a preamble sequence index within an RO, a frequency resource index for a set of ROs associated with a frequency division multiplexing (FDM) configuration, a time resource index for a set of ROs associated with a time division multiplexing (TDM) configuration within a physical RACH (PRACH) slot, and a set of PRACH slot indices. [C25] The UE of C24, wherein the plurality of parameters used to generate the preamble resource index include a first parameter selected from the preamble sequence index in the RO, a second parameter selected from the frequency resource index for the set of ROs associated with the FDM configuration, a third parameter selected from the time resource index for the set of ROs associated with the TDM configuration, and a fourth parameter selected from the set of PRACH slot indexes. [C26] The UE of C21, wherein the preamble resource index is generated based at least in part on a function that assigns a different weight to each parameter of the plurality of parameters. [C27] The UE of C21, wherein the PRU configuration associated with the payload is one of a plurality of PRU configurations associated with time and frequency resources configured for the uplink RACH message. [C28] The UE of C27, wherein the multiple PRU configurations are indexed based at least in part on an index associated with the ordered preamble resources. [C29] When the one or more processors generate the uplink RACH message, ordering the plurality of PRU configurations according to one or more criteria; The UE of C27, configured to select the PRU configuration associated with the payload from the plurality of PRU configurations based at least in part on the ordering. [C30] The UE of C29, wherein the one or more criteria used to order the multiple PRU configurations include one or more of an ascending modulation coding scheme or an ascending transport block size based at least in part on the multiple PRU configurations that overlap within one or more of the time resources or the frequency resources. [C31] The UE of C29, wherein the one or more criteria used to order the multiple PRU configurations include one or more of ascending frequency occasions or ascending time occasions based at least in part on the multiple PRU configurations not overlapping within the time or frequency resources. [C32] When the one or more processors generate the uplink RACH message, generating a scrambling identifier for the payload according to a set of parameters based at least in part on an index associated with the preamble; The UE of C21, configured to scramble the payload using the scrambling identifier. [C33] The UE of C32, wherein the set of parameters used to generate the scrambling identifier is further based at least in part on a random access radio network temporary identifier and a data scrambling identifier configured by the base station. [C34] The UE of C32, wherein the scrambling identifier is generated based at least in part on a function that applies a different weight to each parameter of the set of parameters. [C35] UE according to C32, wherein generating the uplink RACH message further includes generating a demodulation reference signal (DMRS) sequence associated with the uplink RACH message, wherein the DMRS sequence is scrambled based at least in part on the scrambling identifier for the payload and one or more time-dependent parameters associated with a PUSCH waveform used to transmit the payload. [C36] The UE of C21, wherein the uplink RACH message is associated with a two-step RACH procedure. [C37] the one or more processors: The UE of C21, further configured to: transmit the preamble associated with the uplink RACH message and the payload associated with the uplink RACH message to the base station, wherein the preamble and the payload are transmitted within separate symbols based at least in part on a time division multiplexing configuration, and wherein the payload carries at least one of a unique identifier associated with the UE, a medium access control layer control element, or user plane or control plane data. [C38] the one or more processors: The UE of C37, further configured to: receive a downlink response message from the base station to the uplink RACH message, wherein the downlink response message includes a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH), the PDCCH including a cyclic redundancy code (CRC) masked by a radio network temporary identifier (RNTI), and the PDSCH carrying at least a portion of the identifier associated with the UE. [C39] The UE of C38, wherein the RNTI that masks the CRC of the PDCCH is a UE-specific identifier that individually targets the UE, and the RNTI is based at least in part on one or more of a data scrambling identifier for a physical uplink shared channel, a demodulation reference signal scrambling identifier associated with the uplink RACH message, the preamble resource index, or the identifier associated with the UE that is carried within the payload of the uplink RACH message. [C40] The UE described in C38, wherein the RNTI masking the CRC of the PDCCH is a group identifier targeting a group of UEs sharing a particular RO, and the RNTI is based at least in part on one or more of a resource index associated with the particular RO shared by the group of UEs, a common time and frequency resource index associated with one or more PRUs shared by the group of UEs, a common demodulation reference signal resource index shared by the group of UEs, or a time and frequency resource index associated with the downlink response message. [C41] 1. A non-transitory computer-readable medium having stored thereon one or more instructions for wireless communication, the one or more instructions comprising: When executed by one or more processors of a user equipment, the one or more processors are caused to: receiving a random access channel (RACH) occasion (RO) configuration from a base station, the RO configuration including information regarding ordered preamble resources; generating a preamble resource index according to a plurality of parameters selected based at least in part on the information in the RO configuration regarding the ordered preamble resources; A non-transitory computer-readable medium comprising one or more instructions for generating an uplink RACH message including a preamble based at least in part on the preamble resource index and a payload associated with a physical uplink shared channel resource unit mapped to the preamble resource index. [C42] 1. An apparatus for wireless communication, comprising: means for receiving a Random Access Channel (RACH) Occasion (RO) configuration from a base station, the RO configuration including information regarding ordered preamble resources; means for generating a preamble resource index according to a plurality of parameters selected based at least in part on the information in the RO configuration regarding the ordered preamble resources; and means for generating an uplink RACH message including a preamble based at least in part on the preamble resource index and a payload associated with a physical uplink shared channel resource unit mapped to the preamble resource index.

Claims

1. 1. A method of wireless communication implemented by a user equipment (UE), comprising: receiving a random access channel (RACH) occasion (RO) configuration from a base station, the RO configuration including information regarding ordered preamble resources, wherein the information regarding the ordered preamble resources includes one or more indexes that are repeated within different synchronization signal block (SSB)-RO association periods; generating a preamble resource index according to a number of parameters selected based on the information about the ordered preamble resources including the one or more indexes; generating an uplink RACH message including a preamble and a payload based on the preamble resource index and a payload associated with a physical uplink shared channel (PUSCH) resource unit (PRU) mapped to the preamble resource index.

2. 2. The method of claim 1, wherein the information in the RO configuration relates to one or more ROs dedicated to a two-step RACH procedure or one or more ROs shared between the two-step RACH procedure and a four-step RACH procedure.

3. The method of claim 1, wherein the information about the ordered preamble resources indicates that the preamble resources are consecutively ordered based on a preamble sequence index within an RO, a frequency resource index for a set of ROs associated with a frequency division multiplexing (FDM) configuration, a time resource index for a set of ROs associated with a time division multiplexing (TDM) configuration within a physical RACH (PRACH) slot, and a set of PRACH slot indices.

4. The method of claim 1 , wherein the PRU configuration associated with the payload is one of a plurality of PRU configurations associated with time and frequency resources configured for the uplink RACH message.

5. The method of claim 4 , wherein the multiple PRU configurations are indexed based on an index associated with the ordered preamble resources.

6. The method of claim 1, further comprising: ordering the plurality of PRU configurations according to one or more criteria; and selecting the PRU configuration associated with the payload from the plurality of PRU configurations based on the ordering.

7. generating the uplink RACH message, generating a scrambling identifier for the payload according to a set of parameters based on an index associated with the preamble; and scrambling the payload using the scrambling identifier.

8. 8. The method of claim 7, wherein the set of parameters used to generate the scrambling identifier is further based on a random access radio network temporary identifier and a data scrambling identifier configured by the base station, or the scrambling identifier is generated based on a function that weights each parameter of the set of parameters differently.

9. The method of claim 7, wherein generating the uplink RACH message further comprises generating a demodulation reference signal (DMRS) sequence associated with the uplink RACH message, wherein the DMRS sequence is scrambled based on the scrambling identifier for the payload and one or more time-dependent parameters associated with a PUSCH waveform used to transmit the payload.

10. The method of claim 1 , wherein the uplink RACH message is associated with a two-step RACH procedure.

11. transmitting the preamble associated with the uplink RACH message and the payload associated with the uplink RACH message to the base station, where the preamble and the payload are transmitted within separate symbols based on a time division multiplexing configuration, where the payload carries at least one of a unique identifier associated with the UE, a medium access control layer control element, or user plane or control plane data. The method of claim 1 further comprising:

12. receiving a downlink response message from the base station to the uplink RACH message, where the downlink response message includes a Physical Downlink Control Channel (PDCCH) and a Physical Downlink Shared Channel (PDSCH), where the PDCCH includes a Cyclic Redundancy Code (CRC) masked by a Radio Network Temporary Identifier (RNTI), and where the PDSCH carries at least a portion of the identifier associated with the UE. The method of claim 11 further comprising:

13. The RNTI that masks the CRC of the PDCCH is a UE-specific identifier that individually targets the UE, and the RNTI is based on one or more of a data scrambling identifier for a physical uplink shared channel, a demodulation reference signal scrambling identifier associated with the uplink RACH message, the preamble resource index, or the identifier associated with the UE that is carried in the payload of the uplink RACH message; or 13. The method of claim 12, wherein the RNTI masking the CRC of the PDCCH is a group identifier targeting a group of UEs sharing a particular RO, and the RNTI is based on one or more of a resource index associated with the particular RO shared by the group of UEs, a common time and frequency resource index associated with one or more PRUs shared by the group of UEs, a common demodulation reference signal resource index shared by the group of UEs, or a time and frequency resource index associated with the downlink response message.

14. A user equipment (UE) for wireless communications, comprising: means for receiving a Random Access Channel (RACH) Occasion (RO) configuration from a base station, the RACH Occasion (RO) configuration including information regarding ordered preamble resources, wherein the information regarding the ordered preamble resources includes one or more indices that are repeated within different Synchronization Signal Block (SSB)-RO association periods; means for generating a preamble resource index according to a number of parameters selected based on the information about the ordered preamble resources including the one or more indexes; and means for generating an uplink RACH message including a preamble and a payload based on the preamble resource index and a payload associated with a physical uplink shared channel (PUSCH) resource unit (PRU) mapped to the preamble resource index.

15. 15. The UE of claim 14, wherein the information in the RO configuration relates to one or more ROs dedicated to a two-step RACH procedure or one or more ROs shared between the two-step RACH procedure and a four-step RACH procedure.

16. The UE of claim 14, wherein the information about the ordered preamble resources indicates that the preamble resources are consecutively ordered based on a preamble sequence index within an RO, a frequency resource index for a set of ROs associated with a frequency division multiplexing (FDM) configuration, a time resource index for a set of ROs associated with a time division multiplexing (TDM) configuration within a physical RACH (PRACH) slot, and a set of PRACH slot indices.

17. The UE of claim 14, wherein the preamble resource index is generated based on a function that assigns a different weight to each of the plurality of parameters.

18. The UE of claim 14, wherein the PRU configuration associated with the payload is one of a plurality of PRU configurations associated with time and frequency resources configured for the uplink RACH message.

19. means for generating a scrambling identifier for the payload according to a set of parameters that is based on an index associated with the preamble; and means for scrambling the payload using the scrambling identifier.

20. 20. The UE of claim 19, wherein the set of parameters used to generate the scrambling identifier is further based on a random access radio network temporary identifier and a data scrambling identifier configured by the base station, or the scrambling identifier is generated based on a function that weights each parameter of the set of parameters differently.

21. The UE of claim 19, wherein generating the uplink RACH message further comprises generating a demodulation reference signal (DMRS) sequence associated with the uplink RACH message, wherein the DMRS sequence is scrambled based on the scrambling identifier for the payload and one or more time-dependent parameters associated with a PUSCH waveform used to transmit the payload.

22. A computer program comprising code for performing the method according to any one of claims 1 to 13 when the computer program is executed on a computer.

Citation Information

Patent Citations

  • Method and apparatus for random access channel (RACH) structure

    JP2022536451A

  • Method and apparatus for performing communication in wireless communication system

    US20210243812A1

  • User device

    WO2020166044A1

  • Method and apparatuses for random access channel (RACH) structure

    WO2020220373A1