Two-step random access physical uplink shared channel allocation on multiple resource block sets

Abstract

The UE receives the configuration for the Physical Random Access Channel (PRACH) of message A (Msg A) on the resource block (RB) set used for two-step random access channel (RACH) operation, and receives one or more parameters for the Physical Uplink Shared Channel (PUSCH) configuration of Msg A. The UE transmits Msg A in the configured Msg A PRACH timing and Msg A PUSCH resources based on the RB set for Msg A PRACH and the one or more parameters for Msg A PUSCH configuration.

Description

[0001] Cross-reference to related applications

[0002] This application claims the rights and priorities of the following applications: U.S. Provisional Application Serial No. 63 / 071,330, filed August 27, 2020, entitled “Two-Step Random Access Physical Uplink Shared Channel Allocation Over Multiple Resource Block Sets”; and U.S. Patent Application No. 17 / 402,274, filed August 13, 2021, entitled “TWO-STEP RANDOM ACCESS PHYSICAL UPLINK SHARED CHANNELALLOCATION OVER MULTIPLE RESOURCE BLOCK SETS”, the entire contents of which are expressly incorporated herein by reference. Technical Field

[0003] In summary, this disclosure relates to communication systems, and more specifically, to wireless communications including random access. Background Technology

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunications services such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. 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, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems.

[0005] These multiple access technologies have been adopted in various telecommunications standards to provide a common protocol enabling different wireless devices to communicate at the city, country, region, and even global levels. An example telecommunications standard is 5G New Radio (NR). 5G NR is part of the continuous evolution of mobile broadband released by the 3rd Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., in conjunction with the Internet of Things (IoT),) and others. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable low-latency communications (URLLC). Some aspects of 5G NR can be based on the 4G Long Term Evolution (LTE) standard. There is a need for further improvements to 5G NR technology. These improvements can also be applied to other multiple access technologies and telecommunications standards that adopt them. Summary of the Invention

[0006] The following provides a brief overview of one or more aspects to offer a basic understanding of such aspects. This overview is not a comprehensive summary of all anticipated aspects, nor is it intended to identify key or important elements of all aspects, nor to depict the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that follows.

[0007] In one aspect of this disclosure, a method, computer-readable medium, and apparatus are provided. A UE receives configuration for the Physical Random Access Channel (PRACH) for message A (Msg A) on a set of resource blocks (RBs) for two-step random access channel (RACH) operation, and receives one or more parameters for the Physical Uplink Shared Channel (PUSCH) configuration for Msg A. The UE transmits Msg A at the configured Msg A PRACH timing based on the RB set for Msg A PRACH and the one or more parameters for Msg A PUSCH configuration.

[0008] In another aspect of this disclosure, a method, computer-readable medium, and apparatus are provided. A base station transmits a configuration for Msg A PRACH on a set of RBs for two-step RACH operation and indicates one or more parameters for the Msg A PUSCH configuration. The base station receives Msg A in the configured Msg A PRACH timing and identified Msg A PUSCH resources based on the set of RBs configured for Msg A PRACH and the one or more parameters for the Msg A PUSCH configuration.

[0009] To achieve the foregoing and related objectives, one or more aspects include the features fully described below and particularly pointed out in the claims. The following description and drawings set forth certain illustrative features of one or more aspects in detail. However, these features indicate only some of the various ways in which the principles of each aspect may be employed, and the description is intended to include all such aspects and their equivalents. Attached Figure Description

[0010] Figure 1 This is a diagram illustrating an example of a wireless communication system and access network.

[0011] Figure 2A This is a diagram illustrating an example of the first frame of various aspects according to this disclosure.

[0012] Figure 2B This is a diagram illustrating an example of a DL channel within a subframe according to various aspects of this disclosure.

[0013] Figure 2C This is a diagram illustrating an example of the second frame according to various aspects of this disclosure.

[0014] Figure 2D This is a diagram illustrating an example of a UL channel within a subframe according to various aspects of this disclosure.

[0015] Figure 3 This is a diagram illustrating an example of a base station and user equipment (UE) in an access network.

[0016] Figure 4A An example of a 4-step random access process is shown.

[0017] Figure 4B An example of a two-step random access process is shown.

[0018] Figure 5 An example of a PUSCH timing that overlaps with the boundary between two RB sets is shown.

[0019] Figure 6A and 6B The frequency offset for PUSCH timing (PO) in multiple RB sets is shown.

[0020] Figure 7 It is a flowchart of a wireless communication method, including transmitting Msg A PUSCH using resources based at least in part on a set of RBs configured for Msg A PRACH.

[0021] Figure 8 This is a diagram illustrating an example of the hardware implementation used for the example device.

[0022] Figure 9It is a flowchart of a wireless communication method, including receiving Msg A PUSCH using resources based at least in part on a set of RBs configured for Msg A PRACH.

[0023] Figure 10 This is a diagram illustrating an example of the hardware implementation used for the example device.

[0024] Figure 11 An example communication flowchart between the UE and the base station is shown, including sending Msg A PUSCH based on the RB set configured for the corresponding Msg A PRACH. Detailed Implementation

[0025] Random access can be performed in a shared spectrum. In some aspects, the RB set size can correspond to a Listen-After-Speak (LBT) unit. For initial access, the uplink (UL) bandwidth portion (BWP) can correspond to a single RB set. Therefore, PRACH resources for initial access can be mapped based on a single RB set based on the initial uplink BWP. For connected-mode UEs, the PRACH configuration can include multiple RB sets corresponding to an active UL BWP that is wider than the initial UL BWP. The use of multiple RBs can help extend random access from connected-mode UEs over a wider frequency range and can help avoid collisions between UEs. Multiple random access opportunities (ROs) in different RB sets in the frequency domain can help distribute PRACH load and provide LBT diversity. For example, if a UE does not pass an LBT in RB set 0 but passes an LBT in RB set 1, the UE can send PRACH in RB set 1.

[0026] However, Msg A PUSCH resources covering the boundaries of multiple RB sets may cause the UE to attempt to transmit Msg A PUSCH via LBT in two RB sets. The UE could wait for LBT to be passed for both RB set 1 and RB set 2 before transmitting Msg A PUSCH in resource 502. The aspects presented herein enable the identification of Msg A PUSCH resources within each RB set, ensuring that the Msg A PUSCH resources do not overlap with the boundaries between two different RB sets. The aspects presented herein enable the UE to identify Msg A PUSCH resources for transmission using a minimum number of successful LBTs, based on the RBs associated with a specific RO. For example, the UE could receive configuration for Msg A PRACH on the RB set used for two-step RACH operations and receive one or more parameters for the Msg A PUSCH configuration. The UE transmits Msg A in the configured Msg A PRACH timing and Msg A PUSCH resources based on the RB set used for Msg A PRACH and one or more parameters used for Msg A PUSCH configuration.

[0027] The specific embodiments described below with reference to the accompanying drawings are intended as descriptions of various configurations and not as representing the only configuration in which the concepts described herein can be practiced. Specific details are included in the specific embodiments for the purpose of providing a comprehensive understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0028] Several aspects of a telecommunications system will now be described with reference to various apparatuses and methods. These apparatuses and methods will be described in detail below, and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively, “elements”). These elements can be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented in hardware or software depends on the specific application and the design constraints imposed on the system as a whole.

[0029] For example, an element, or any part of an element, or any combination of elements, can be implemented as a "processing system" including one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, system-on-a-chip (SoCs), baseband processors, field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functions described herein. One or more processors in a processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other names, software should be broadly interpreted as meaning instructions, instruction sets, code, code segments, program code, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc.

[0030] Accordingly, in one or more example embodiments, the described functionality may be implemented in hardware, software, or any combination thereof. If implemented in software, the functionality may be stored or encoded as one or more instructions or code on a computer-readable medium. A computer-readable medium includes a computer storage medium. The storage medium may be any available medium accessible by a computer. By way of example, and not limitation, such a computer-readable medium may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of computer-readable media of the types described above, or any other medium capable of storing computer-executable code accessible by a computer in the form of instructions or data structures.

[0031] While aspects and implementations are described herein by way of example, those skilled in the art will understand that additional implementations and use cases may arise in many different arrangements and scenarios. The innovations described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and package arrangements. For example, implementations and / or uses may arise via integrated chip implementations and other devices based on non-modular components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, AI-enabled devices, etc.). While some examples may or may not be specific to a particular use case or application, a wide variety of applicability to the described innovations can exist. Implementations can range from chip-level or modular components to non-modular, non-chip-level implementations, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more aspects of the described innovations. In some practical settings, devices incorporating the described aspects and features may also include additional components and features for the implementation and enforcement of the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily involve multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / converters, etc.). The innovations described herein are intended to be implemented in a variety of devices, chip-level components, systems, distributed arrangements, aggregated or decomposed components, end-user devices, etc., with different sizes, shapes, and constructions.

[0032] Figure 1 This is a diagram illustrating an example of a wireless communication system and access network 100. The wireless communication system (also referred to as a wireless wide area network (WWAN)) includes a base station 102, a UE 104, an evolved packet core (EPC) 160, and another core network 190 (e.g., a 5G core (5GC)). Base station 102 may include macro cells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Macro cells include base stations. Small cells include femtocells, picocells, and microcells.

[0033] Base station 102 configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can interface with EPC 160 via a first backhaul link 132 (e.g., S1 interface). Base station 102 configured for 5G NR (collectively referred to as Next Generation RAN (NG-RAN)) can interface with core network 190 via a second backhaul link 184. Among other functions, base station 102 can also perform one or more of the following functions: transmission of user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), user and device tracking, RAN information management (RIM), paging, location, and delivery of warning messages. Base stations 102 can communicate directly or indirectly with each other on a third backhaul link 134 (e.g., an X2 interface) (e.g., via EPC 160 or core network 190). The first backhaul link 132, the second backhaul link 184, and the third backhaul link 134 can be wired or wireless.

[0034] Base station 102 can wirelessly communicate with UE 104. Each base station 102 in the base station 102 can provide communication coverage for a corresponding geographic coverage area 110. Overlapping geographic coverage areas 110 may exist. For example, a small cell 102' may have a coverage area 110' that overlaps with the coverage areas 110 of one or more macro base stations 102. A network that includes both small cells and macro cells can be referred to as a heterogeneous network. The heterogeneous network may also include a Home Evolved Node B (eNB) (HeNB), which can provide services to restricted groups referred to as Closed Subscriber Groups (CSGs). The communication link 120 between base station 102 and UE 104 may include uplink (UL) (also referred to as reverse link) transmission from UE 104 to base station 102 and / or downlink (DL) (also referred to as forward link) transmission from base station 102 to UE 104. The communication link 120 may use multiple-input multiple-output (MIMO) antenna technology, which includes spatial multiplexing, beamforming, and / or transmit diversity. The communication link may be via one or more carriers. Base station 102 / UE 104 may use spectrum allocated in carrier aggregation for a total of up to Y x MHz (x component carriers) for transmission in each direction, with a bandwidth of up to Y MHz per carrier (e.g., 5, 10, 15, 20, 100, 400 MHz, etc.). Carriers may be adjacent to each other or may not be adjacent to each other. Carrier allocation may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL ​​compared to UL). Component carriers may include primary component carriers and one or more secondary component carriers. The primary component carrier may be referred to as the primary cell (PCell), and the secondary component carrier may be referred to as the secondary cell (SCell).

[0035] Some UEs 104 can communicate with each other using device-to-device (D2D) communication link 158. D2D communication link 158 can use DL / UL WWAN spectrum. D2D communication link 158 can use one or more sideline channels, such as the Physical Sideline Broadcast Channel (PSBCH), Physical Sideline Discovery Channel (PSDCH), Physical Sideline Shared Channel (PSSCH), and Physical Sideline Control Channel (PSCCH). D2D communication can be achieved through a wide variety of wireless D2D communication systems, such as, for example, FlashLinQ, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.

[0036] The wireless communication system may also include a Wi-Fi access point (AP) 150 that communicates with a Wi-Fi station (STA) 152 via a communication link 154 in, for example, a 5 GHz unlicensed spectrum. When communicating in the unlicensed spectrum, the STA 152 / AP 150 may perform a free channel assessment (CCA) before communication to determine whether the channel is available.

[0037] Small cell 102' can operate in licensed and / or unlicensed spectrum. When operating in unlicensed spectrum, small cell 102' can employ NR and use the same unlicensed spectrum (e.g., 5 GHz, etc.) as used by Wi-Fi AP 150. Small cell 102' employing NR in unlicensed spectrum can improve coverage of the access network and / or increase the capacity of the access network.

[0038] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc., based on frequency / wavelength. In 5G NR, the two initial operating bands have been designated as frequency range names FR1 (410MHz-7.125GHz) and FR2 (24.25GHz-52.6GHz). Although a portion of FR1 is greater than 6GHz, in various documents and articles, FR1 is often (interchangeably) referred to as the "below 6GHz" band. Similar naming issues sometimes arise regarding FR2; although it differs from the extremely high frequency (EHF) band (30GHz-300GHz), it is often (interchangeably) referred to in documents and articles as the "millimeter wave" band, which is designated as such by the International Telecommunication Union (ITU).

[0039] The frequencies between FR1 and FR2 are generally referred to as intermediate frequency (IF) bands. Recent 5G NR studies have designated the operating bands of these IF bands as the frequency range name FR3 (7.125 GHz – 24.25 GHz). Bands falling within FR3 can inherit FR1 and / or FR2 characteristics, and thus can effectively extend the characteristics of FR1 and / or FR2 to IF band frequencies. Additionally, higher frequency bands are currently being explored to extend 5G NR operation above 52.6 GHz. For example, three higher operating frequency bands have been designated as the frequency range names FR4a or FR4-1 (52.6 GHz – 71 GHz), FR4 (52.6 GHz – 114.25 GHz), and FR5 (114.25 GHz – 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0040] In light of the foregoing, unless otherwise specifically stated, it should be understood that when the term "below 6 GHz" is used herein, it can broadly refer to frequencies that are less than 6 GHz, within FR1, or may include intermediate frequency band frequencies. Furthermore, unless otherwise specifically stated, it should be understood that when the term "millimeter wave" is used herein, it can broadly refer to frequencies that may include intermediate frequency band frequencies, within FR2, FR4, FR4-a or FR4-1 and / or FR5, or within the EHF band.

[0041] Base station 102 (whether a small cell 102' or a large cell (e.g., a macro base station)) may include and / or be referred to as an eNB, gNodeB (gNB), or another type of base station. Some base stations (such as gNB 180) may operate in conventional sub-6 GHz spectrum, millimeter wave frequencies, and / or near-millimeter wave frequencies to communicate with UE 104. When gNB 180 operates in millimeter wave or near-millimeter wave frequencies, gNB 180 may be referred to as a millimeter wave base station. Millimeter wave base station 180 may utilize beamforming 182 with UE 104 to compensate for extremely high path loss and short range. Base station 180 and UE 104 may each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming.

[0042] Base station 180 may transmit beamforming signals to UE 104 in one or more transmit directions 182'. UE 104 may receive beamforming signals from base station 180 in one or more receive directions 182'. UE 104 may also transmit beamforming signals to base station 180 in one or more transmit directions. Base station 180 may receive beamforming signals from UE 104 in one or more receive directions. Base station 180 / UE 104 may perform beam training to determine the optimal receive and transmit directions for each of base station 180 / UE 104. The transmit and receive directions for base station 180 may be the same or different. The transmit and receive directions for UE 104 may be the same or different.

[0043] EPC 160 may include Mobility Management Entity (MME) 162, other MMEs 164, Serving Gateway 166, Multimedia Broadcast Multicast Service (MBMS) Gateway 168, Broadcast Multicast Service Center (BM-SC) 170, and Packet Data Network (PDN) Gateway 172. MME 162 can communicate with Home Subscriber Server (HSS) 174. MME 162 is the control node that handles signaling between UE 104 and EPC 160. Generally, MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are transmitted through Serving Gateway 166, which is itself connected to PDN Gateway 172. PDN Gateway 172 provides IP address allocation and other functions to the UE. PDN Gateway 172 and BM-SC 170 are connected to IP Service 176. IP Service 176 may include the Internet, intranet, IP Multimedia Subsystem (IMS), PS streaming service, and / or other IP services. The BM-SC 170 provides functions for setting up and delivering MBMS user services. The BM-SC 170 can serve as an entry point for MBMS transmissions to content providers, authorizing and initiating MBMS bearer services within a Public Land Mobile Network (PLMN), and scheduling MBMS transmissions. The MBMS gateway 168 can distribute MBMS services to base stations 102 belonging to areas of Multicast-Broadcast Single Frequency Networks (MBSFNs) that broadcast specific services, and can be responsible for session management (start / stop) and collecting billing information related to eMBMS.

[0044] The core network 190 may include Access and Mobility Management Functions (AMF) 192, other AMFs 193, Session Management Functions (SMF) 194, and User Plane Functions (UPF) 195. AMF 192 can communicate with the Unified Data Management Unit (UDM) 196. AMF 192 is the control node that processes signaling between UE 104 and the core network 190. Typically, AMF 192 provides QoS streaming and session management. All user Internet Protocol (IP) packets are transmitted through UPF 195. UPF 195 provides UE IP address allocation and other functions. UPF 195 connects to IP service 197. IP service 197 may include the Internet, intranet, IP Multimedia Subsystem (IMS), packet-switched (PS) streaming service, and / or other IP services.

[0045] Base stations may include and / or be referred to as gNB, Node B, eNB, access point, base transceiver station, wireless base station, wireless transceiver, transceiver function, Basic Services Set (BSS), Extended Services Set (ESS), Transmitter Receiver Point (TRP), or some other suitable term. Base station 102 provides UE 104 with access to EPC 160 or core network 190. Examples of UE 104 include cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radio units, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablets, smart devices, wearable devices, vehicles, electricity meters, air pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other similarly functional devices. Some UEs in UE 104 may be referred to as IoT devices (e.g., parking meters, air pumps, ovens, vehicles, heart monitors, etc.). UE 104 may also be referred to as a station, mobile station, user station, mobile unit, user unit, radio unit, remote unit, mobile device, radio device, wireless communication device, remote device, mobile user station, access terminal, mobile terminal, radio terminal, remote terminal, handheld device, user agent, mobile client, client, or any other suitable term.

[0046] Refer again Figure 1 In some aspects, UE 104 may include a PRACH component 198 configured to: receive configuration for Msg A PRACH on a set of RBs for two-step RACH operation; receive one or more parameters for Msg A PUSCH configuration; and identify Msg A PUSCH resources based on the set of RBs for Msg A PRACH configuration and one or more parameters for Msg A PUSCH configuration. UE 104 may be configured to: transmit Msg A in one of the configured Msg A PRACH timings and identified Msg A PUSCH resources based on the set of RBs for Msg A PRACH and one or more parameters for Msg A PUSCH configuration.

[0047] Base station 102 or 180 may include a PRACH component 199 configured to: transmit configuration for Msg A PRACH on a set of RBs for two-step RACH operation; and indicate one or more parameters for Msg A PUSCH configuration. The base station may be configured to: receive Msg A in the configured Msg A PRACH timing and identified Msg A PUSCH resources based on the set of RBs configured for Msg A PRACH and the one or more parameters for Msg A PUSCH configuration.

[0048] Although the following description may focus on 5G NR, the concepts described herein can be applied to other similar fields, such as LTE, LTE-A, CDMA, GSM and other wireless technologies.

[0049] Figure 2A This is a schematic diagram 200 showing an example of the first subframe within a 5G NR frame structure. Figure 2B This is a schematic diagram 230 showing an example of a DL channel within a 5G NR subframe. Figure 2C This is a schematic diagram 250 showing an example of a second subframe within a 5G NR frame structure. Figure 2D This is a schematic diagram 280 illustrating an example of a UL channel within a 5G NR subframe. The 5G NR frame structure can be Frequency Division Duplex (FDD) (where, for a specific set of subcarriers (carrier system bandwidth), subframes within that set are dedicated to either DL or UL), or Time Division Duplex (TDD) (where, for a specific set of subcarriers (carrier system bandwidth), subframes within that set are dedicated to both DL and UL). In the process of... Figure 2A , 2C In the provided example, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (mostly DL), where D is DL, U is UL, and F is flexible between DL / UL, and subframe 3 is configured with slot format 1 (all UL). Although subframes 3 and 4 are shown as having slot formats 1 and 28, respectively, any particular subframe can be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are all DL and all UL, respectively. Other slot formats 2-61 include a mixture of DL, UL, and flexible symbols. The UE is configured with a slot format via the received Slot Format Indicator (SFI) (dynamically configured via DL Control Information (DCI) or semi-statically / statically configured via Radio Resource Control (RRC) signaling). This description also applies to 5G NR frame structures as TDD.

[0050] Figures 2A-2DThe frame structure is illustrated, and aspects of this disclosure are applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10 ms) can be divided into 10 equal-sized subframes (1 ms). Each subframe may include one or more time slots. Subframes may also include micro-time slots, which may include 7, 4, or 2 symbols. Each time slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended. For normal CP, each time slot may include 14 symbols, and for extended CP, each time slot may include 12 symbols. Symbols on the DL may be CP Orthogonal Frequency Division Multiplexing (OFDM) (CP-OFDM) symbols. Symbols on the UL may be CP-OFDM symbols (for high-throughput scenarios) or Discrete Fourier Transform (DFT) Spread Spectrum OFDM (DFT-s-OFDM) symbols (also known as Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols) (for power-constrained scenarios; limited to single-stream transmission). The number of time slots within a subframe may be based on the time slot configuration and the CP. The digital scheme defines the subcarrier spacing (SCS) and, in effect, the symbol length / duration (which can be equal to 1 / SCS).

[0051] μ <![CDATA[SCSΔf=2 μ ·15[kHz]]]> Cyclic prefix 0 15 ordinary 1 30 ordinary 2 60 Normal, Extended 3 120 ordinary 4 240 ordinary

[0052] For a standard CP (e.g., 14 symbols per slot), different digital schemes μ0 through 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For an extended CP, digital scheme 2 allows 4 slots per subframe. Correspondingly, for the standard slot configuration and digital scheme μ0, there are 14 symbols / slot and 2... μ One time slot / subframe. Subcarrier spacing and symbol length / duration depend on the digital scheme. Subcarrier spacing can be equal to 2. μ *15kHz, where μ is the digital scheme from 0 to 4. Therefore, digital scheme μ = 0 has a subcarrier spacing of 15kHz, and digital scheme μ = 4 has a subcarrier spacing of 240kHz. The symbol length / duration is inversely related to the subcarrier spacing. Figures 2A-2D Examples are provided for a standard CP (with 14 symbols per time slot) and a digital scheme μ=2 (with 4 time slots per subframe). The time slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within a frame set, one or more distinct bandwidth portions (BWPs) of frequency division multiplexing can exist (see [link to relevant documentation]). Figure 2B Each BWP can have a specific digital scheme and CP (normal or extended).

[0053] A resource grid can be used to represent the frame structure. Each time slot includes a resource block (RB) (also known as a physical RB (PRB)), which consists of 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0054] As in Figure 2A As shown, some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include a demodulation RS (DM-RS) for channel estimation at the UE (indicated as R for a particular configuration, but other DM-RS configurations are possible) and a channel state information reference signal (CSI-RS). The RS may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and a phase tracking RS (PT-RS).

[0055] Figure 2B Examples of various DL channels within a subframe of a frame are shown. The Physical Downlink Control Channel (PDCCH) carries DCI within one or more Control Channel Elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE comprising six RE Groups (REGs), each REG comprising 12 consecutive REs in an OFDM symbol within an RB. The PDCCH within a BWP can be referred to as a Control Resource Set (CORESET). The UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., a common search space, a UE-specific search space) during PDCCH monitoring on a CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs can span the channel bandwidth at larger and / or lower frequencies. The Primary Synchronization Signal (PSS) can be within symbol 2 of a specific subframe of the frame. The PSS is used by UE 104 to determine subframe / symbol timing and physical layer identification. The Secondary Synchronization Signal (SSS) can be within symbol 4 of a specific subframe of the frame. The SSS is used by the UE to determine the Physical Layer Cell Identifier Group Number and radio frame timing. Based on the Physical Layer Identifier and Physical Layer Cell Identifier Group Number, the UE can determine the Physical Cell Identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS. The Physical Broadcast Channel (PBCH), carrying the Master Information Block (MIB), can logically be grouped with the PSS and SSS to form a Synchronization Signal (SS) / PBCH block (also known as an SS block (SSB)). The MIB provides the number of RBs and the System Frame Number (SFN) in the system bandwidth. The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information not transmitted via the PBCH (such as System Information Block (SIB)), and paging messages.

[0056] As in Figure 2CAs shown, some of the REs carry DM-RS for channel estimation at the base station (indicated as R for a specific configuration, but other DM-RS configurations are possible). The UE can transmit DM-RS for the Physical Uplink Control Channel (PUCCH) and DM-RS for the PUSCH. The PUSCH DM-RS can be transmitted in the first one or two symbols before the PUSCH. The PUCCH DM-RS can be transmitted in different configurations depending on whether a short or long PUCCH is transmitted and depending on the specific PUCCH format used. The UE can transmit a Sounding Reference Signal (SRS). The SRS can be transmitted in the last symbol of a subframe. The SRS can have a comb structure, and the UE can transmit the SRS on one of the combs. The SRS can be used by the base station for channel quality estimation to enable frequency-dependent scheduling on the UL.

[0057] Figure 2D Examples of various UL channels within a subframe of a frame are shown. The PUCCH can be positioned as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) ACK / NACK bits. The PUSCH carries data and may also be used to carry buffer status reports (BSR), power headroom reports (PHR), and / or UCI.

[0058] Figure 3This is a block diagram illustrating communication between base station 310 and UE 350 in the access network. In the DL, IP packets from EPC 160 can be provided to controller / processor 375. Controller / processor 375 implements Layer 3 and Layer 2 functions. Layer 3 includes the Radio Resource Control (RRC) layer, and Layer 2 includes the Serving Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and Media Access Control (MAC) layer. The controller / processor 375 provides: RRC layer functions associated with: broadcasting system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-Radio Access Technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functions associated with: header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functions associated with: transmission of upper-layer packet data units (PDUs), error correction via ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with: mapping between logical channels and transport channels, multiplexing of MAC SDUs to transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel prioritization.

[0059] Transmit (TX) processor 316 and receive (RX) processor 370 implement Layer 1 functions associated with various signal processing functions. Layer 1, including the physical (PHY) layer, may include error detection of the transport channel, forward error correction (FEC) encoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. TX processor 316 processes the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase phase shift keying (M-PSK), and M-order quadrature amplitude modulation (M-QAM)). The encoded and modulated symbols can then be divided into parallel streams. Each stream can then be mapped to OFDM subcarriers, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domains, and then combined using inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time-domain OFDM symbol stream. The OFDM stream is spatially precoded to generate multiple spatial streams. Channel estimation from channel estimator 374 can be used to determine coding and modulation schemes and for spatial processing. The channel estimation can be derived from reference signals transmitted by UE 350 and / or channel condition feedback. Each spatial stream can then be provided to a different antenna 320 via a separate transmitter 318TX. Each transmitter 318TX can use the corresponding spatial stream to modulate a radio frequency (RF) carrier for transmission.

[0060] At UE 350, each receiver 354RX receives signals via its corresponding antenna 352. Each receiver 354RX recovers the information modulated onto the RF carrier and provides the information to the receive (RX) processor 356. The TX processor 368 and RX processor 356 implement Layer 1 functions associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial stream destined for UE 350. If multiple spatial streams are destined for UE 350, they can be combined by the RX processor 356 into a single OFDM symbol stream. The RX processor 356 then uses a Fast Fourier Transform (FFT) to transform the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal consists of a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, along with a reference signal, are recovered and demodulated by determining the most probable signal constellation point transmitted by base station 310. These soft decisions can be based on a channel estimate calculated by channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally transmitted by base station 310 on the physical channel. The data and control signals are then provided to controller / processor 359, which implements Layer 3 and Layer 2 functions.

[0061] The controller / processor 359 may be associated with a memory 360 that stores program code and data. The memory 360 may be referred to as a computer-readable medium. In the UL, the controller / processor 359 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between the transport and logical channels to recover IP packets from the EPC 160. The controller / processor 359 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operation.

[0062] Similar to the functions described in conjunction with DL transmissions performed by base station 310, controller / processor 359 provides: RRC layer functions associated with: system information (e.g., MIB, SIB) acquisition, RRC connection and measurement reporting; PDCP layer functions associated with: header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functions associated with: transmission of upper-layer PDUs, error correction via ARQ, concatenation, segmentation and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with: mapping between logical channels and transport channels, multiplexing of MAC SDUs to TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority processing, and logical channel prioritization.

[0063] The channel estimate derived by the channel estimator 358 from the reference signal or feedback transmitted by the base station 310 can be used by the TX processor 368 to select appropriate coding and modulation schemes, as well as to facilitate spatial processing. The spatial stream generated by the TX processor 368 can be provided to different antennas 352 via a separate transmitter 354TX. Each transmitter 354TX can use the corresponding spatial stream to modulate the RF carrier for transmission.

[0064] UL transmission at base station 310 is handled in a manner similar to that described for the receiver functions integrated at UE 350. Each receiver 318RX receives signals via its corresponding antenna 320. Each receiver 318RX recovers the information modulated onto the RF carrier and provides the information to the RX processor 370.

[0065] The controller / processor 375 may be associated with a memory 376 that stores program code and data. The memory 376 may be referred to as a computer-readable medium. In the UL, the controller / processor 375 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between the transport channel and the logical channel to recover IP packets from the UE 350. IP packets from the controller / processor 375 may be provided to the EPC 160. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operation.

[0066] At least one of the TX processor 368, RX processor 356, and controller / processor 359 can be configured to perform and Figure 1 The PRACH component 198 relates to various aspects.

[0067] At least one of the TX processor 316, RX processor 370, and controller / processor 375 can be configured to perform operations related to... Figure 1 The PRACH component 199 relates to various aspects.

[0068] The UE can use random access procedures to communicate with the base station. For example, the UE can use random access procedures to request an RRC connection, re-establish an RRC connection, restore an RRC connection, and so on. Figure 4A An example aspect of a random access procedure 400 between UE 402 and base station 404 is illustrated. UE 402 can initiate a random access message exchange by sending a first random access message 403 (e.g., Msg 1) including a preamble to base station 404. Before sending the first random access message 403, the UE can obtain random access parameters, such as preamble format parameters, time and frequency resources, root sequence for determining the random access preamble, and / or cyclic shift parameters, for example, from system information 401 from base station 404. The preamble can be sent along with an identifier such as a random access RNTI (RA-RNTI). UE 402 can randomly select a random access preamble sequence, for example, from a set of preamble sequences. If UE 402 randomly selects a preamble sequence, base station 404 can simultaneously receive another preamble from a different UE. In some examples, a preamble sequence can be assigned to UE 402.

[0069] The base station responds to the first random access message 403 by sending a second random access message 405 (e.g., Msg 2) using PDSCH and including a random access response (RAR). The RAR may include, for example, an identifier of a random access preamble sent by the UE, a timing advance (TA), an uplink grant for the UE to transmit data, a cell radio network temporary identifier (C-RNTI), or another identifier and / or a fallback indicator. Upon receiving the RAR (e.g., 405), the UE 402 may, for example, use PUSCH to send a third random access message 407 (e.g., Msg 3) to the base station 404, which may include an RRC connection request, an RRC connection re-establishment request, or an RRC connection recovery request, depending on the trigger used to initiate the random access procedure. The base station 404 can then complete the random access procedure by sending a fourth random access message 409 (e.g., Msg 4) to the UE 402, for example, using PDCCH for scheduling and PDSCH for messaging. The fourth random access message 409 may include a random access response message, which includes timing advance information, contention resolution information, and / or RRC connection establishment information. UE 402 may, for example, use C-RNTI to monitor the PDCCH. If the PDCCH is successfully decoded, UE 402 may also decode the PDSCH. UE 402 may send HARQ feedback for any data carried in the fourth random access message. If two UEs send the same preamble at 703, both UEs may receive a RAR that causes both UEs to send the third random access message 407. Base station 404 can resolve such a conflict by being able to decode only the third random access message from one of the UEs and respond to that UE with the fourth random access message. The other UE that does not receive the fourth random access message 409 can determine that random access was unsuccessful and can retry random access. Therefore, the fourth message may be referred to as a contention resolution message. The fourth random access message 409 can complete the random access procedure. Therefore, UE 402 can then send uplink communication and / or receive downlink communication with base station 404 based on RAR and fourth random access message 409.

[0070] To reduce latency or control signaling overhead, a single round-trip cycle between the UE and the base station can be implemented in the 2-step RACH procedure 450, for example... Figure 4BAs shown in the diagram. Aspects of Msg 1 and Msg 3 can be combined into a single message, for example, it can be referred to as Msg A. Msg A can include a random access preamble and can also include a PUSCH transmission, such as data. The Msg A preamble can be separate from the four-step preamble, but can be sent in the same RO as the preamble of the four-step RACH procedure, or can be sent in a separate RO. The RO includes the time and frequency resources in which the UE can send PRACH. PUSCH transmission can be sent in a PO that can span multiple symbols and PRBs. The PO includes the time and frequency resources in which the UE can send PUSCH. After UE 402 sends Msg A 411, UE 402 can wait for a response from base station 404. In addition, aspects of Msg 2 and Msg 4 can be combined into a single message, which can be referred to as Msg B. For reasons similar to the four-step RACH procedure, a two-step RACH can be triggered. If the UE does not receive a response, it can retransmit Msg A or fall back to the four-step RACH procedure starting with Msg 1. If the base station detects Msg A but fails to successfully decode Msg APUSCH, it can respond by allocating uplink resources for PUSCH retransmission. The UE can fall back to the four-step RACH with Msg 3 based on the response from the base station and can retransmit the PUSCH from Msg A. If the base station successfully decodes Msg A and the corresponding PUSCH, it can reply with an indication of successful reception (e.g., as a random access response 413 upon completion of a two-step RACH procedure). Msg B may include a random access response and a contention resolution message. The contention resolution message may be sent after the base station successfully decodes the PUSCH transmission.

[0071] For a two-step RACH procedure, a set of PUSCH resources can be configured for each PRACH slot. When using a non-interleaved waveform, the base station can send a Msg A PUSCH configuration to the UE, which provides, for example, an offset from the lowest RB of the first PUSCH to PRB 0 in a parameter such as a frequency start parameter for Msg A PUSCH (e.g., “frequencyStartMsgA-PUSCH”). If the UE uses an interleaved waveform for Msg A PUSCH, the base station can provide a first interleaving index. For example, the base station can provide the frequency start parameter and / or the first interleaving index in RRC signaling. The POs used for the non-interleaved waveform can be defined by a start offset (e.g., from a reference PRB such as PRB 0), the number of RBs for each PO, a guard band parameter indicating whether a guard band exists between POs (which can be configured to 0 or 1 RB), and the number of frequency domain POs. For example, the number of frequency domain POs can be configured to 1, 2, 4, or 8. The PO used for interleaving waveforms can be defined by the starting interleave (e.g., “interleaveIndexFirstPO-MsgA-PUSCH”) and the number of interleaves (e.g., “nrofinterlacesPerMsgA-PO”).

[0072] This approach can also be applied to unlicensed communication in shared spectrum, such as NR-U (NR-Unlicensed) in unlicensed spectrum. In NR-U, as an example, the RB set can be approximately 20 MHz and can be a Listen-After-Speak (LBT) unit. For initial access, the uplink (UL) bandwidth portion (BWP) can be 20 MHz, for example, corresponding to a single RB set. Therefore, PRACH resources for initial access are mapped based on a single RB set. For PRACH used for initial access, the PRACH can be constrained by the initial uplink BWP.

[0073] For connected-mode UEs, PRACH configuration can include multiple RB sets, for example, when the active UL BWP is greater than 20MHz. The use of multiple RBs can help extend random access from connected-mode UEs over a wider frequency range and can help avoid conflicts between UEs. From the perspective of efficient resource utilization, the PRACH resources used for connected-mode UEs (including multiple RB sets) can be a superset of the PRACH resources used for idle UEs. For example, for initial access, the UE can use PRACH in RB set 0, and in connected mode, the UE can use PRACH in RB sets 0 / 1 / 2 / 3 (e.g., a superset including RB set 0 and additional RB sets).

[0074] Multiple Returns (ROs) in the frequency domain within different RB sets can help distribute PRACH load and provide LBT diversity. For example, if a UE fails to pass the LBT in RB set 0 but passes the LBT in RB set 1, the UE can send PRACH in RB set 1.

[0075] However, Msg A PUSCH resources covering the boundaries of multiple RB sets may cause the UE to attempt to send Msg A PUSCH via LBT in two RB sets. Figure 5 In the example resource diagram 500, the Msg A PUSCH resource 502 overlaps with the boundary between RB set 1 and RB set 2. Therefore, the UE can wait for LBT to pass for both RB set 1 and RB set 2 in order to send Msg A PUSCH in resource 502.

[0076] The aspects presented herein enable the identification of Msg A PUSCH resources within each RB set, ensuring that the Msg A PUSCH resources do not overlap with the boundaries between two different RB sets. Therefore, these aspects allow the UE to identify Msg A PUSCH resources that do not involve an additional number of successful LBTs in order to transmit Msg A PUSCH.

[0077] Similar to the Msg 2PRACH configuration, when using a non-interleaved waveform, the 2-step MsgA PUSCH configuration for RACH can provide an offset from the lowest RB of the first PUSCH to PRB 0 via an offset parameter such as the “frequencyStartMsgA-PUSCH” parameter. Alternatively, when using an interleaved waveform, the 2-step MsgA PUSCH configuration for RACH can provide the first interleaving index. The Msg A PUSCH configuration can not address multiple RB sets and can be applied to a single RB set configuration only.

[0078] When using a non-interleaved PUSCH waveform, the frequency start of the PUSCH can be interpreted as the frequency start in each RB set. Figure 6A An example of applying the frequency offset from the first option to multiple RB sets is shown. In the second option, a design incorporating two indicators or offsets can be used. For example, the UE can identify the offset between the PUSCH start point indicated by the frequency start parameter and the lower end of the RB set in which the first PUSCH falls. If the first RB set cannot maintain all frequency-domain PUSCH timings configured for the UE, the UE can apply the same offset to the next RB set. Figure 6B An example of a second option, including a first offset and a second offset, is shown. Within each RB set, an integer number of POs can be filled. Filling can stop if the number of POs exceeds the range of the RB set.

[0079] If an interleaved PUSCH waveform is used, in the first option, another RRC parameter can indicate the starting RB set index. For example, Msg A PUSCH can begin from the RB set indicated by the starting RB set index. For example, for RB set index 1, the Msg A PUSCH timing can be defined starting from RB set 1, and if RB set 1 cannot hold all frequency domain PO, it can continue in RB set 2, etc. In the second option, the starting interleaving index can indicate the starting interleaving index on all RB sets (e.g., multiple RB sets). For 15 / 30kHz waveforms, there can be M = 10 / 5 interleavings respectively. The starting interleaving can be in the range of 1-10 (e.g., 0-9). To indicate the starting interleaving on multiple RB sets, the interleaving index can be changed to the range of 0-39 or 49. The starting interleaving X can indicate the starting interleaving mod(X / M) starting from the RB set numbered with the floor value of X / M. For example, if X = 11 and M = 10, it indicates starting from RB set 1 and interleaving 1. To limit MsgA PUSCH in an RB set, if PO exceeds the number of interleavings available in the RB set, further limits can be applied to fill PO, and the placement can be moved to the next RB set.

[0080] Examples may include added RRC signaling to provide the UE with one or more additional Msg A PUSCH parameters. The aspects described herein enable the UE to utilize more efficient RRC signaling (e.g., no additional RRC parameters are required for RACH configurations of multiple RB sets compared to a single RB set RACH configuration) to identify Msg A PUSCH resources whose boundaries do not overlap with those of the RB sets.

[0081] Figure 11 An example communication flowchart 1100 between UE 1102 and base station 1104 is shown, including sending Msg A PUSCH based on the RB set configured for the corresponding Msg APRACH. As shown at 1101, UE 1102 can receive configurations of multiple RB sets (e.g., one RB set associated with each RO) for PRACH transmission. For example, multiple RB sets may exist for communication systems, carriers, or bandwidths. One or more RB sets can be configured for a specific RACH timing.

[0082] At 1103, the UE can receive configuration for one or more parameters for Msg A PUSCH. At 1105, the UE can perform LBT, and if successful, can continue sending message A 1106. Msg A may include a PRACH preamble based on the PRACH configuration received at 1101 (e.g., 1107). Msg A may include Msg A PUSCH 1108 based on the RB set configured for the corresponding PRACH at 1101 and the parameters configured for Msg A PUSCH at 1103. (See also...) Figure 4B As described, the UE can receive Msg B 1109 from base station 1104 in response to Msg A 1106.

[0083] When the interleaved waveform is used for Msg A PUSCH, UE 1102 can identify the Msg A PUSCH resource using the set of RB sets configured for Msg A PRACH at 1101. UE 1102 can receive the set of RB sets in the RO configuration and can determine the RB set for Msg A PUSCH based on the RB set used for the corresponding PRACH without additional RRC parameters. UE 1102 can interpret the RRC parameters defining the timing of Msg APUSCH within each RB set configured for Msg A PRACH. Therefore, the UE can apply the PUSCH parameters configured for Msg A PUSCH 1108 (e.g., at 1103) to the RB set configured for the corresponding Msg A PRACH 1107 (e.g., at 1101). As described above, Msg APUSCH configuration 1103 can include the starting interleaving and the number of interleavings for each Msg A PO. These parameters indicate the starting interleaving in each RB set and the number of interleavings used for each Msg A PUSCH resource. For multiple RB sets, UE1102 can reinterpret the number of Frequency Division Multiplexing (FDM) POs as the number of interleaving-based POs used for the RB sets. UE1102 can repeat this process for each RB set for which ROs are defined.

[0084] When a non-interleaved waveform is used for Msg A PUSCH, UE 1102 can similarly use the RB set configured for Msg A PRACH 1107 for the RB set to be used. UE 1102 can reinterpret the RRC parameters used for PUSCH timing (e.g., configured at 1103) within the RB set of multiple RB sets configured at 1101. For example, the UE can interpret the parameters for the RRC configuration of Msg A PUSCH 1108 within the RB set corresponding to PRACH 1107. UE 1102 can interpret the start offset parameter from the lower bound of the RB set instead of from PRB 0. UE 1102 can interpret the number of RBs per PO in the same way for a single RB set PRACH configuration and multiple RB set configurations. For example, Figure 6A The diagram illustrates an example of UE 1102 applying a starting offset to each RB set as an offset from the lowest RB in the corresponding RB set. UE 1102 can interpret the configuration parameters regarding the number of RBs (e.g., 0 or 1 RBs) in the guard band between POs in the same way for both single RB set PRACH configurations and multiple RB set configurations. UE 1102 can interpret the configured number of frequency domain POs (e.g., 1 / 2 / 4 / 8) as the number of POs in each RB set rather than the total number of POs. For example, if the PRACH configuration includes 2 RB sets, and the UE receives a configuration of 4 frequency domain POs for Msg A PUSCH, the UE can have 8 total POs, for example, 4 per RB set.

[0085] Figure 7 This is a flowchart 700 of a wireless communication method. This method can be performed by a UE (e.g., UE 104, 350, 402). This method can provide the UE with a more efficient way to determine Msg A PUSCH resources with reduced signaling overhead and by avoiding LBTs in multiple RBs.

[0086] At 702, the UE receives configuration for Msg A PRACH on the RB set used for two-step RACH operation. This reception can be performed, for example, by the Msg A PRACH component 840 via the receiving component 830 and / or the RF transceiver 822. Multiple RB sets may exist, configured for the communication system, carrier, or bandwidth. One or more RB sets can be configured for a specific RACH timing.

[0087] At 704, the UE receives one or more parameters for configuring the Msg A PUSCH. This reception may be performed, for example, by the Msg APUSCH component 842 via the receiving component 830 and / or the RF transceiver 822. In some aspects, the one or more parameters may include the start interleaving for the Msg A PUSCH, the number of interleavings for the Msg A PUSCH, and / or the number of FDM POs for the Msg APUSCH with interleaved waveforms. In some aspects, the one or more parameters may include at least one of the following: the start offset for the Msg A PUSCH, the number of resource blocks, the guard band between POs, or the number of FDM POs for the Msg A PUSCH with non-interleaved waveforms.

[0088] At 708, the UE transmits Msg A in the configured Msg A PRACH timing and Msg A PUSCH resource, the Msg A PUSCH resource being based on the RB set configured for Msg A PRACH and one or more parameters configured for Msg A PUSCH. This transmission can be performed, for example, by the transmission component 834 of device 802. In some aspects, as shown at 706, the UE can identify the Msg A PUSCH resource based on the RB set configured for Msg A PRACH and one or more parameters configured for Msg A PUSCH. This identification can be performed, for example, by the resource identification component 844 of device 802.

[0089] Msg A PUSCH may include interleaved waveforms. One or more parameters configured for Msg A PUSCH may include at least one of the following: the initial interleaving for Msg A PUSCH, the number of interleavings for Msg A PUSCH, or the number of FDM POs for Msg A PUSCH. The UE may apply the initial interleaving as the initial interleaving in the RB set configured for Msg A PUSCH. The UE may apply the number of interleavings for Msg A PUSCH as the number of interleavings in the RB set configured for Msg A PUSCH. The UE may apply the number of FDM POs for Msg A PUSCH as the number of FDM POs, as the interleaving-based number of POs in the RB set configured for Msg A PUSCH.

[0090] Msg A PUSCH may include a non-interleaved waveform. One or more parameters may include at least one of the following: the start offset for Msg A PUSCH, the number of resource blocks, the guard band between POs, or the number of FDM POs for Msg A PUSCH. The UE may apply the start offset as the frequency of the lowest resource block in the RB set configured for Msg A PUSCH. The UE may apply the number of FDM POs for Msg A PUSCH as the number of POs in the RB set configured for Msg A PUSCH.

[0091] Figure 8 Figure 800 illustrates an example of a hardware implementation for device 802. Device 802 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, device 802 may include a cellular baseband processor 804 (also referred to as a modem) coupled to a cellular RF transceiver 822. In some aspects, device 802 may also include one or more Subscriber Identity Module (SIM) cards 820, an application processor 806 coupled to a Secure Digital Card (SD) card 808 and a screen 810, a Bluetooth module 812, a Wireless Local Area Network (WLAN) module 814, a Global Positioning System (GPS) module 816, and a power supply 818. Cellular baseband processor 804 communicates with UE 104 and / or base station 102 / 180 via cellular RF transceiver 822. Cellular baseband processor 804 may include computer-readable medium / memory. The computer-readable medium / memory may be non-transitory. Cellular baseband processor 804 is responsible for general processing, including executing software stored on the computer-readable medium / memory. When the software is executed by the cellular baseband processor 804, it causes the cellular baseband processor 804 to perform the various functions described herein. The computer-readable medium / memory can also be used to store data manipulated by the cellular baseband processor 804 during software execution. The cellular baseband processor 804 also includes a receiving component 830, a communication manager 832, and a transmitting component 834. The communication manager 832 includes one or more components shown. The components within the communication manager 832 can be stored in a computer-readable medium / memory and / or configured as hardware within the cellular baseband processor 804. The cellular baseband processor 804 can be a component of the UE 350 and can include a memory 360 and / or at least one of a TX processor 368, an RX processor 356, and a controller / processor 359. In one configuration, the device 802 can be a modem chip and only includes the baseband processor 804, and in another configuration, the device 802 can be the entire UE (e.g., see...). Figure 3 (350) and includes an additional module of device 802.

[0092] Communication manager 832 includes Msg A PRACH component 840, which is configured to receive configuration for Msg A PRACH on a set of RBs for two-step RACH operation, for example, as combined with Figure 7 As described in 702. The communication manager 832 also includes a Msg A PUSCH component 842, which receives one or more parameters for Msg A PUSCH configuration, such as, in combination with Figure 7 As described in section 704. The communication manager 832 may also include a resource identification component 844, which receives input from component 840 in the form of a set of RBs configured for a two-step PRACH operation, and receives one or more parameters for Msg A PUSCH configuration from component 842, and is configured to identify one or more resources for Msg A PUSCH transmission based on the set of RBs configured for Msg A PRACH and one or more parameters configured for Msg A PUSCH, for example, as in combination with... Figure 7 As described in section 706. The sending component 834 is configured to send Msg A PRACH at a configured Msg A PUSCH timing and within a Msg A PUSCH resource, the Msg A PUSCH resource being based on a set of RBs configured for Msg A PRACH and one or more parameters configured for Msg A PUSCH, for example, as combined with... Figure 7 708 is described in the text.

[0093] The device may include execution Figure 7 The flowchart shows the algorithm as an additional component in each box. Therefore, it can be executed by the component. Figure 7 Each box in the flowchart, and the apparatus may include one or more of those components. A component may be one or more hardware components specifically configured to perform the process / algorithm, implemented by a processor configured to perform the process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0094] As shown in the figure, device 802 may include various components configured for various functions. In one configuration, device 802 (specifically, cellular baseband processor 804) includes: a unit for receiving configuration for Msg A PRACH on a set of RBs for two-step RACH operation. Device 802 includes: a unit for receiving one or more parameters for Msg A PUSCH configuration. Device 802 includes: a unit for transmitting Msg A PUSCH in a configured Msg A PRACH timing and Msg A PUSCH resources, the Msg A PUSCH resources being based on the set of RBs configured for Msg A PRACH and one or more parameters for Msg A PUSCH configuration. Device 802 may also include: a unit for identifying one or more resources for Msg A PUSCH transmission based on the set of RBs configured for Msg A PRACH and one or more parameters for Msg A PUSCH configuration. The aforementioned units may be one or more components of device 802 configured to perform the functions described above. As described herein, apparatus 802 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Therefore, in one configuration, the aforementioned units may be the TX processor 368, RX processor 356, and controller / processor 359 configured to perform the functions described herein.

[0095] Figure 9 This is a flowchart 900 of a wireless communication method. This method can be performed by a base station (e.g., base stations 102, 180, 310, 404). This method can provide the base station with a more efficient way to configure Msg A PUSCH resources with reduced signaling overhead by helping the UE receive the configuration to avoid performing LBT in multiple RBs in order to send Msg A PUSCH.

[0096] At 902, the base station transmits the configuration for message A (Msg A) PRACH on the RB set used for two-step RACH operation. This transmission can be performed, for example, by the Msg A PRACH configuration component 1040 via the transmission component 1034 and / or the RF transceiver 1022. Multiple RB sets may exist, configured for the communication system, carrier, or bandwidth. One or more RB sets can be configured for a specific RACH timing.

[0097] At 904, the base station indicates one or more parameters for Msg A PUSCH configuration. This indication can be performed, for example, by Msg A PUSCH configuration component 1042 via transmission component 1034 and / or RF transceiver 1022. In some aspects, the one or more parameters may include the start interleaving for Msg A PUSCH, the number of interleavings for Msg A PUSCH, and / or the number of FDM POs for Msg A PUSCH with interleaved waveforms. In some aspects, the one or more parameters may include at least one of the following: the start offset for Msg A PUSCH, the number of resource blocks, the guard band between POs, or the number of FDM POs for Msg A PUSCH with non-interleaved waveforms.

[0098] At 906, the base station receives Msg A in the configured Msg A PRACH timing and identified Msg A PUSCH resources based on the RB set configured for Msg A PRACH and one or more parameters configured for Msg A PUSCH. This reception can be performed, for example, by Msg A component 1044 via receiving component 1030 and / or RF transceiver 1022 of device 1002. Msg A PUSCH may include interleaved waveforms. The one or more parameters configured for Msg A PUSCH may include at least one of the following: a starting interleaf for Msg A PUSCH, the number of interleaves for Msg A PUSCH, or the number of FDM POs for Msg A PUSCH. The starting interleaf can be applied as the starting interleaf in the RB set configured for Msg A PRACH. The number of interleaves for Msg A PUSCH can be applied as the number of interleaves in the RB set configured for Msg A PRACH. The number of FDM POs used for Msg APRACH can be applied as the number of FDM POs, as the number of interleaved POs in the RB set configured in Msg APRACH.

[0099] Msg A PUSCH may include a non-interleaved waveform. One or more parameters may include at least one of the following: the start offset for Msg A PUSCH, the number of resource blocks, the guard band between POs, or the number of FDM POs for Msg A PUSCH. The start offset may be applied as the frequency of the lowest resource block in the RB set configured for Msg A PUSCH. The number of FDM POs for Msg A PUSCH may be applied as the number of POs in the RB set configured for Msg A PUSCH.

[0100] Figure 10 This is a diagram 1000 illustrating an example of a hardware implementation of device 1002. Device 1002 may be a base station, a component of a base station, or may implement base station functions. In some aspects, device 1002 may include a baseband unit 1004. Baseband unit 1004 may communicate with UE 104 via RF transceiver 1022. RF transceiver 1022 may be a cellular RF transceiver. Baseband unit 1004 may include computer-readable medium / memory. Baseband unit 1004 is responsible for general processing, including executing software stored on the computer-readable medium / memory. When executed by baseband unit 1004, the software causes baseband unit 1004 to perform the various functions described herein. The computer-readable medium / memory may also be used to store data manipulated by baseband unit 1004 during software execution. Baseband unit 1004 also includes a receiving component 1030, a communication manager 1032, and a transmitting component 1034. Communication manager 1032 includes one or more of the components shown. The components within the communication manager 1032 may be stored in a computer-readable medium / memory and / or configured as hardware within the baseband unit 1004. The baseband unit 1004 may be a component of the base station 310 and may include at least one of the memory 376 and / or the TX processor 316, the RX processor 370, and the controller / processor 375.

[0101] Communication manager 1032 includes Msg A PRACH configuration component 1040, which is configured to send configuration for Msg A PRACH on a set of RBs for two-step RACH operation, for example, as combined with Figure 9 As described in 902. The communication manager 1032 also includes a Msg A PUSCH configuration component 1042, which is configured to indicate one or more parameters for Msg A PUSCH configuration, for example, as in conjunction with... Figure 9 As described in 904. The communication manager 1032 also includes a Msg A component 1044, configured to receive Msg A in the configured Msg A PRACH timing and identified Msg A PUSCH resources based on the RB set configured for Msg A PRACH and one or more parameters configured for Msg A PUSCH, for example, as in combination with... Figure 9 As described in 906.

[0102] The device may include execution Figure 9 The flowchart shows the algorithm as an additional component in each box. Therefore, it can be executed by the component. Figure 9Each box in the flowchart, and the apparatus may include one or more of those components. A component may be one or more hardware components specifically configured to perform the process / algorithm, implemented by a processor configured to perform the process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0103] As shown in the figure, device 1002 may include various components configured for various functions. In one configuration, device 1002 (specifically, baseband unit 1004) includes: a unit for transmitting a configuration for Msg A PRACH on a set of RBs for two-step RACH operation. Device 1002 includes: a unit for indicating one or more parameters for Msg A PUSCH configuration. Device 1002 includes: a unit for receiving Msg A in a configured Msg A PRACH timing and identified Msg A PUSCH resources based on the set of RBs configured for Msg A PRACH and one or more parameters for Msg A PUSCH configuration. The aforementioned units may be one or more components of device 1002 configured to perform the functions described therein. As described herein, device 1002 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Therefore, in one configuration, the aforementioned units may be TX processor 316, RX processor 370, and controller / processor 375 configured to perform the functions described therein.

[0104] It should be understood that the specific order or hierarchy of the boxes in the disclosed process / flowchart is illustrative of the example method. It should be understood that the specific order or hierarchy of the boxes in the process / flowchart may be rearranged based on design preferences. Furthermore, some boxes may be combined or omitted. The appended method claims give the elements of each box in the order shown, but this does not imply limitation to the specific order or hierarchy given.

[0105] The foregoing description is provided to enable any person skilled in the art to implement the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but are given the full scope consistent with the textual claims, wherein reference to the singular form of an element, unless expressly stated otherwise, is not intended to mean “one and only one,” but rather “one or more.” Terms such as “if,” “when,” and “while,” should be interpreted as “under the condition of,” rather than implying a direct temporal relationship or reaction. That is, these phrases (e.g., “when”) do not imply an immediate action in response to the occurrence of an action or during the occurrence of such action, but merely that the action will occur if the condition is met, without requiring a specific or immediate temporal constraint on the occurrence of the action. The term “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred over or superior to other aspects. Unless expressly stated otherwise, the term “some” refers to one or more. Combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, and may include multiples of A, multiples of B, or multiples of C. Specifically, combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, wherein any such combination may contain one or more members of A, B, or C. All structural and functional equivalents of the elements throughout the various aspects described in this disclosure are expressly incorporated herein by reference and intended to be included by the claims, and such structural and functional equivalents are known to or will be known later to those skilled in the art. Furthermore, nothing disclosed herein is intended to be offered to the public, whether or not such disclosure is explicitly stated in the claims. Terms such as “module,” “mechanism,” “element,” “device,” etc., are not necessarily substitutes for the term “unit.” Therefore, no claim element should be interpreted as a unit plus a function unless the element is explicitly stated using the phrase “unit for…”.

[0106] The following aspects are illustrative only and may be combined with, but not limited to, other aspects or teachings described herein.

[0107] Aspect 1 is a method for wireless communication at a UE, comprising: receiving configuration for Msg A PRACH on a set of RBs for two-step RACH operation; receiving one or more parameters for Msg A PUSCH configuration; and transmitting the Msg A PUSCH in a configured Msg A PRACH timing and Msg A PUSCH resources, the Msg A PUSCH resources being based on the set of RBs configured for the Msg A PRACH and the one or more parameters of the configuration for the Msg A PUSCH.

[0108] In aspect 2, the method according to aspect 1 further includes: the Msg A PUSCH includes an interleaved waveform, and the one or more parameters configured for the Msg A PUSCH include at least one of the following: a starting interleaf for the Msg A PUSCH, a number of interleafs for the Msg A PUSCH, or a number of FDM POs for the Msg A PUSCH.

[0109] In aspect 3, the method according to aspect 1 or aspect 2 further includes: the one or more parameters configured for the Msg A PUSCH include the starting interleaving for the Msg A PUSCH, and the Msg A PUSCH resources are based on the starting interleaving in the set of RBs configured for the Msg A PUSCH.

[0110] In aspect 4, the method according to any one of aspects 1-3 further includes: the one or more parameters for the Msg A PUSCH configuration include the number of interleavings for the Msg A PUSCH, and the Msg APUSCH resource is based on the number of interleavings in the RB set configured for the Msg A PUSCH by the application.

[0111] In aspect 5, the method according to any one of aspects 1-4 further includes: the one or more parameters for the Msg APUSCH configuration include the number of FDM POs for the Msg APUSCH, and the Msg APUSCH resources are based on applying the number of FDM POs as the number of interlaced POs in the RB configured for the Msg APUSCH.

[0112] In aspect 6, the method according to aspect 1 further includes: the Msg A PUSCH comprising a non-interleaved waveform, and the one or more parameters comprising at least one of the following: a start offset for the Msg A PUSCH, a number of resource blocks, a guard band between POs, or a number of FDM POs for the Msg A PUSCH.

[0113] In aspect 7, the method according to aspect 6 further includes: the one or more parameters for the Msg A PUSCH configuration include the starting offset for the Msg A PUSCH, and the Msg A PUSCH resource is based on the frequency of the lowest resource block in the RB set configured for the Msg A PUSCH.

[0114] In aspect 8, the method according to aspect 6 or aspect 7 further includes: the one or more parameters for the Msg A PUSCH configuration include the number of FDM POs for the Msg A PUSCH, and the Msg A PUSCH resources are based on the number of POs in the RB set configured by the application for the Msg A PUSCH.

[0115] Aspect 9 is an apparatus for wireless communication at a UE, comprising a unit for performing the method according to any one of aspects 1-8.

[0116] In aspect 10, the apparatus according to aspect 9 further includes: at least one antenna and a transceiver coupled to said at least one antenna.

[0117] Aspect 11 is an apparatus for wireless communication at a UE, comprising: a memory and at least one processor coupled to the memory, the memory and the at least one processor being configured to perform a method according to any one of aspects 1-8.

[0118] In aspect 12, the apparatus according to aspect 10 further includes: at least one antenna and a transceiver coupled to the at least one antenna and the at least one processor.

[0119] Aspect 13 is a computer-readable medium storing computer-executable code for wireless communication at a UE, wherein the code, when executed by a processor, causes the processor to implement the method according to any one of aspects 1-8.

[0120] Aspect 14 is a method of wireless communication at a base station, comprising: transmitting configuration for Msg A PRACH on a set of RBs for two-step RACH operation; indicating one or more parameters for Msg A PUSCH configuration; and receiving Msg A in a configured Msg A PRACH timing and identified Msg A PUSCH resources based on the set of RBs configured for said Msg A PRACH and said one or more parameters for said Msg A PUSCH configuration.

[0121] In aspect 15, the method according to aspect 14 further includes: the Msg APUSCH includes an interleaved waveform, and the one or more parameters configured for the Msg APUSCH include at least one of the following: a starting interleaf for the Msg APUSCH, a number of interleafs for the Msg APUSCH, or a number of FDM POs for the Msg APUSCH.

[0122] In aspect 16, the method according to aspect 15 further includes: the one or more parameters configured for the Msg A PUSCH including the starting interleaving for the Msg A PUSCH, to apply the starting interleaving as the set of RBs configured for the Msg APRACH.

[0123] In aspect 17, the method according to aspect 15 or 16 further includes: the one or more parameters for the Msg A PUSCH configuration including the number of interlacings for the Msg A PUSCH, to be applied as the number of interlacings in the RB set configured for the Msg APRACH.

[0124] In aspect 18, the method according to any one of aspects 15-17 further includes: the one or more parameters for the Msg A PUSCH configuration including the number of FDM POs for the Msg A PUSCH, to be applied as the number of FDM POs as the number of interlaced POs in the RB set configured for the Msg A PRACH.

[0125] In aspect 19, the method according to aspect 14 further includes: Msg A PUSCH comprising a non-interleaved waveform, and the one or more parameters comprising at least one of the following: a start offset for the Msg A PUSCH, a number of resource blocks, a guard band between POs, or a number of FDM POs for the Msg A PUSCH.

[0126] In aspect 20, the method according to aspect 19 further includes: the one or more parameters for the Msg A PUSCH configuration including the start offset for the Msg A PUSCH, applied as the frequency of the Msg A PUSCH starting from the lowest resource block in the RB set configured for the Msg A PUSCH.

[0127] In aspect 21, the method according to aspect 19 or aspect 20 further includes: the one or more parameters for the Msg A PUSCH configuration including the number of FDM POs for the Msg A PUSCH, to be applied as the number of POs in the RB set configured for the Msg A PUSCH.

[0128] Aspect 22 is an apparatus for wireless communication at a base station, including a unit for performing the method according to any one of aspects 14-21.

[0129] In aspect 23, the apparatus according to aspect 22 further includes: at least one antenna and a transceiver coupled to said at least one antenna.

[0130] Aspect 24 is an apparatus for wireless communication at a base station, comprising: a memory and at least one processor coupled to the memory, the memory and the at least one processor being configured to perform a method according to any one of aspects 14-21.

[0131] In aspect 25, the apparatus according to aspect 24 further includes: at least one antenna and a transceiver coupled to the at least one antenna and the at least one processor.

[0132] Aspect 26 is a computer-readable medium storing computer-executable code for wireless communication at a base station, wherein the code, when executed by a processor, causes the processor to implement the method according to any one of aspects 14-21.

Claims

1. An apparatus for wireless communication at a user equipment (UE), comprising: Memory; as well as At least one processor coupled to the memory, the memory and the at least one processor being configured as follows: Receive configuration for Physical Random Access Channel (PRACH) for message A (Msg A) on a set of resource blocks (RBs) for two-step random access channel (RACH) operation, wherein the set of RBs is one of a plurality of RB sets configured for PRACH. Receive one or more parameters for configuring the Msg A Physical Uplink Shared Channel (PUSCH); The Msg A PUSCH resource is identified based on both the RB set configured for the Msg A PRACH and one or more parameters configured for the Msg A PUSCH; and The Msg A, comprising Msg A PUSCH and the Msg A PRACH, is transmitted in the configured Msg A PRACH timing and the identified Msg A PUSCH resource, wherein the identified Msg A PUSCH resource is configured to not overlap with the boundary between two different RB sets among the plurality of RB sets, and the RB set is one of the two different sets.

2. The apparatus according to claim 1, wherein, The Msg A PUSCH includes an interleaved waveform, and the one or more parameters used for configuring the Msg A PUSCH include at least one of the following: The starting interleaving for MsgA PUSCH will be applied as the starting interleaving in the set of RBs configured for Msg A PRACH. The number of interlacings in the RB set configured for the Msg A PRACH will be applied as the number of interlacings for the Msg A PUSCH, or The same number of FDM POs for the Msg A PUSCH will be applied as the frequency division multiplexing (FDM) PUSCH timings (POs) in the RB set configured for the Msg A PRACH.

3. The apparatus according to claim 2, wherein, The one or more parameters used for the Msg A PUSCH configuration include the starting interleaving for the Msg A PUSCH, and the Msg A PUSCH resources are based on the starting interleaving in the RB set configured for the Msg A PUSCH.

4. The apparatus according to claim 2, wherein, The one or more parameters used for the Msg A PUSCH configuration include the number of interleavings for the Msg A PUSCH, and the Msg A PUSCH resources are based on the number of interleavings in the RB set configured for the Msg A PUSCH.

5. The apparatus according to claim 2, wherein, The one or more parameters used for the Msg A PUSCH configuration include the number of FDM POs for the Msg A PUSCH, and the Msg A PUSCH resources are based on the number of FDM POs applied as the number of interlaced POs in the RB configured for the Msg A PUSCH.

6. The apparatus according to claim 1, wherein, The Msg A PUSCH includes a non-interleaved waveform, and the one or more parameters include at least one of the following: The starting offset for Msg APUSCH will be applied from the lowest resource block in the RB set configured for Msg A PRACH, or The number of POs in the RB set configured for the Msg A PRACH will be used as the number of frequency division multiplexing (FDM) POs for the Msg APUSCH.

7. The apparatus according to claim 6, wherein, The one or more parameters used for the Msg A PUSCH configuration include the starting offset for the Msg A PUSCH, and the Msg A PUSCH resource is based on the frequency of the lowest resource block in the RB set configured for the Msg A PUSCH.

8. The apparatus according to claim 6, wherein, The one or more parameters used for the Msg A PUSCH configuration include the number of FDM POs for the Msg A PUSCH, and the Msg A PUSCH resources are based on the number of POs in the RB set configured for the Msg A PUSCH by the application.

9. The apparatus according to claim 1, further comprising: antenna; as well as A transceiver coupled to the antenna and the at least one processor.

10. A method for wireless communication at a user equipment (UE), comprising: Receive configuration for Physical Random Access Channel (PRACH) for message A (Msg A) on a set of resource blocks (RBs) for two-step random access channel (RACH) operation, wherein the set of RBs is one of a plurality of RB sets configured for PRACH. Receive one or more parameters for configuring the Msg A Physical Uplink Shared Channel (PUSCH); The Msg A PUSCH resource is identified based on both the RB set configured for the Msg A PRACH and one or more parameters configured for the Msg A PUSCH; and The Msg A, comprising Msg A PUSCH and the Msg A PRACH, is transmitted in the configured Msg A PRACH timing and the identified Msg A PUSCH resource, wherein the identified Msg A PUSCH resource is configured to not overlap with the boundary between two different RB sets among the plurality of RB sets, and the RB set is one of the two different sets.

11. The method according to claim 10, wherein, The Msg A PUSCH includes an interleaved waveform, and the one or more parameters configured for the Msg A PUSCH include a start interleaving for the Msg A PUSCH, which the UE applies as the start interleaving in the set of RBs configured for the Msg A PUSCH.

12. The method according to claim 10, wherein, The Msg A PUSCH includes an interleaved waveform, and the one or more parameters configured for the Msg A PUSCH include the number of interleaved elements for the Msg A PUSCH, which the UE applies as the number of interleaved elements in the RB set configured for the Msg A PUSCH.

13. The method according to claim 10, wherein, The Msg A PUSCH includes an interleaved waveform, and the one or more parameters configured for the Msg A PUSCH include the number of Frequency Division Multiplexing (FDM) PUSCH Opportunities (POs) for the Msg A PUSCH, which the UE applies as the number of FDM POs as the number of interleaved POs in the RB configured for the Msg APRACH.

14. The method according to claim 10, wherein, The Msg A PUSCH includes a non-interleaved waveform, and the one or more parameters configured for the Msg A PUSCH include a start offset for the Msg A PUSCH, which the UE applies as the frequency start of the Msg A PUSCH from the lowest resource block in the RB set configured for the Msg A PUSCH.

15. The method according to claim 10, wherein, The Msg A PUSCH includes a non-interleaved waveform, and the one or more parameters configured for the Msg A PUSCH include the number of Frequency Division Multiplexing (FDM) PUSCH Opportunities (POs) for the Msg A PUSCH, which the UE applies as the number of POs in the RB set configured for the Msg A PUSCH.

16. An apparatus for wireless communication at a base station, comprising: Memory; as well as At least one processor coupled to the memory, the memory and the at least one processor being configured as follows: The configuration for the Physical Random Access Channel (PRACH) of message A (Msg A) is sent on a set of resource blocks (RBs) for two-step random access channel (RACH) operation, wherein the set of RBs is one of a plurality of RB sets configured for PRACH. Indicates one or more parameters used for the configuration of the Physical Uplink Shared Channel (PUSCH) for Msg A; and The Msg A is received in the configured Msg A PRACH timing and the identified Msg A PUSCH resources, which include Msg A PUSCH and the Msg A PRACH. The identified Msg A PUSCH resources are identified based on both the RB set configured for the Msg A PRACH and one or more parameters configured for the Msg A PUSCH. The identified Msg A PUSCH resource is configured to not overlap with the boundary between two different RB sets among the plurality of RB sets, and the RB set is one of the two different sets.

17. The apparatus according to claim 16, wherein, Msg A PUSCH includes an interleaved waveform, and the one or more parameters used for configuring the Msg A PUSCH include at least one of the following: The starting interleaving for MsgA PUSCH will be applied as the starting interleaving in the set of RBs configured for Msg A PRACH. The number of interlacings in the RB set configured for the Msg A PRACH will be applied as the number of interlacings for the Msg A PUSCH, or The same number of FDM POs for the Msg A PUSCH will be applied as the frequency division multiplexing (FDM) PUSCH timings (POs) in the RB set configured for the Msg A PRACH.

18. The apparatus according to claim 17, wherein, The one or more parameters used for the Msg A PUSCH configuration include the starting interleaving for the Msg A PUSCH, to be applied as the starting interleaving in the set of RBs configured for the Msg A PRACH.

19. The apparatus according to claim 17, wherein, The one or more parameters used for the Msg A PUSCH configuration include the number of interlacings for the Msg A PUSCH, applied as the number of interlacings in the RB set configured for the Msg A PRACH.

20. The apparatus according to claim 17, wherein, The one or more parameters used for the Msg A PUSCH configuration include the number of FDM POs for the Msg A PUSCH, which is applied as the number of interlaced POs in the RB set configured for the Msg A PRACH.

21. The apparatus according to claim 16, wherein, Msg A PUSCH includes a non-interleaved waveform, and the one or more parameters include at least one of the following: The starting offset for Msg APUSCH will be applied from the lowest resource block in the RB set configured for Msg A PRACH, or The number of POs in the RB set configured for the Msg A PRACH will be used as the number of frequency division multiplexing (FDM) POs for the Msg APUSCH.

22. The apparatus according to claim 21, wherein, The one or more parameters used for the Msg A PUSCH configuration include the starting offset for the Msg A PUSCH, applied as the frequency of the lowest resource block in the RB set configured for the Msg A PUSCH.

23. The apparatus according to claim 21, wherein, The one or more parameters used for the Msg A PUSCH configuration include the number of FDM POs for the Msg A PUSCH, applied as the number of POs in the RB set configured for the Msg A PRACH.

24. The apparatus of claim 16, further comprising: antenna; as well as A transceiver coupled to the antenna and the at least one processor.

25. A method for wireless communication at a base station, comprising: The configuration for the Physical Random Access Channel (PRACH) of message A (Msg A) is sent on a set of resource blocks (RBs) for two-step random access channel (RACH) operation, wherein the set of RBs is one of a plurality of RB sets configured for PRACH. Indicates one or more parameters used for the configuration of the Physical Uplink Shared Channel (PUSCH) for Msg A; and The Msg A is received in the configured Msg A PRACH timing and the identified Msg A PUSCH resources, which include Msg A PUSCH and the Msg A PRACH. The identified Msg A PUSCH resources are identified based on both the RB set configured for the Msg A PRACH and one or more parameters configured for the Msg A PUSCH. The identified Msg A PUSCH resource is configured to not overlap with the boundary between two different RB sets among the plurality of RB sets, and the RB set is one of the two different sets.

26. The method of claim 25, wherein, The Msg A PUSCH includes an interleaved waveform, and the one or more parameters configured for the Msg A PUSCH include a starting interleaved body for the Msg A PUSCH, applied as the starting interleaved body in the set of RBs configured for the Msg A PUSCH.

27. The method according to claim 25, wherein, The Msg A PUSCH includes an interleaved waveform, and the one or more parameters configured for the Msg A PUSCH include the number of interleaved bodies for the Msg A PUSCH, applied as the number of interleaved bodies in the RB set configured for the Msg A PUSCH.

28. The method according to claim 25, wherein, The Msg A PUSCH includes an interleaved waveform, and the one or more parameters configured for the Msg A PUSCH include the number of frequency division multiplexing (FDM) PUSCH opportunities (POs) for the Msg A PUSCH, applied as the number of FDM POs as the number of interleaved POs in the set of RBs configured for the Msg A PUSCH.

29. The method according to claim 25, wherein, The Msg A PUSCH includes a non-interleaved waveform, and the one or more parameters configured for the Msg A PUSCH include a start offset for the Msg A PUSCH, applied as the frequency of the Msg A PUSCH starting from the lowest resource block in the RB set configured for the Msg A PUSCH.

30. The method according to claim 25, wherein, The Msg A PUSCH includes a non-interleaved waveform, and the one or more parameters configured for the Msg A PUSCH include the number of frequency division multiplexing (FDM) PUSCH timings (POs) for the Msg A PUSCH, applied as the number of POs in the set of RBs configured for the Msg A PUSCH.

Images