Mapping of a single preamble to multiple physical uplink shared channel resource units for a two-step random access procedure.

Abstract

Aspects are provided for supporting a payload for msgA transmission in a two-step random access (RACH) procedure by providing a one-to-many mapping configuration between preambles and physical uplink shared channel (PUSCH) resource units (PRUs). A UE determines the preambles to be mapped to one or more groups of PRUs to support piggybacking of uplink control information (UCI), frequency hopping on the PUSCH, and multiple slot repetition for msgA transmission. Piggybacking UCI to the payload in msgA can provide flexibility in MCS and waveform selection, as well as resource allocation for demodulation reference signals (DMRS) and PUSCH in the PRU. Furthermore, allowing the payload to hop to different frequencies on the PUSCH during the transmission of msgA can provide improved frequency diversity and interference averaging, and allowing the payload to repeat across multiple slots in the msgA transmission can provide enhanced coverage and / or reliability.

Description

Technical Field

[0001] Cross - reference to Related Applications This application claims the benefit of International Patent Application No. PCT / CN2019 / 089292, filed on May 30, 2019, entitled "MAPPING ONE PREAMBLE TO MULTIPLE PHYSICAL UPLINK SHARED CHANNEL RESOURCE UNITS FOR TWO - STEP RANDOM ACCESS PROCEDURE", which is hereby incorporated by reference in its entirety.

[0002] The present disclosure generally relates to communication systems, and more specifically, to wireless communication between a base station and a user equipment (UE).

Background Art

[0003] Wireless communication systems are widely deployed to provide various telecommunication services such as telephone, video, data, messaging, and broadcast. A typical wireless communication system may utilize multiple - access techniques that can support communication with multiple users by sharing available system resources. Examples of such multiple - access techniques 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.

[0004] These multiple access technologies are being adopted in various telecommunications standards to provide a common protocol that enables different wireless devices to communicate at urban, national, regional, and even global levels. An exemplary telecommunications standard is 5G New Radio (NR). 5G NR is part of the ongoing evolution of mobile broadband published by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)), and other requirements. 5G NR includes services associated with Enhanced Mobile Broadband (eMBB), Massive Machine-Type Communications (mMTC), and Ultra-High Reliability Low Latency Communications (URLLC). Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. Further improvements to 5G NR technology are needed. These improvements may also be applicable to other multiple access technologies and the telecommunications standards that employ them. [Overview of the project] [Means for solving the problem]

[0005] The following provides a simplified overview of one or more embodiments to provide a basic understanding of such embodiments. This overview is not a comprehensive overview of all possible embodiments, nor is it intended to identify the main or important elements of all embodiments, nor to define the scope of any or all embodiments. Its sole purpose is to present some concepts of one or more embodiments in a simplified form as a prelude to more detailed explanations that will be presented later.

[0006] In a contention-based random access (RACH) procedure, typically four messages are exchanged between the UE and the base station. For example, during the initial attach procedure, the UE may send a preamble to the base station (e.g., message 1), receive a random access response (RAR) from the base station (e.g., message 2), send an RRC connection request message or other payload to the base station (e.g., message 3), and receive an RRC connection setup message or other transmission from the base station that will undergo contention resolution (e.g., message 4). This four-step RACH procedure can be simplified to a two-step RACH procedure in which the UE sends the preamble and payload in the first message. For example, in the two-step RACH procedure, message A ("msgA") may correspond to messages 1 and 3 of the four-step RACH procedure, and message B ("msgB") may correspond to messages 2 and 4 of the four-step RACH procedure. Therefore, in a two-step RACH procedure, the UE may send a preamble followed by a payload to the base station in a single msgA transmission, while the base station may send RAR and RRC response messages to the UE in a single msgB transmission.

[0007] However, the payload transmitted in the msgA of a two-step RACH procedure can have a variety of payload sizes and all coverage requirements. For example, user plane data may have a larger payload size than radio resource control messages, and different types of payloads may require different modulation coding schemes (MCS). To support this variety of payloads, the msgA transmission in the two-step RACH procedure must allow for configurable MCS and configurable resource sizes in the time-frequency domain. This disclosure satisfies this need by providing a one-to-many mapping configuration between a preamble and physical uplink shared channel (PUSCH) resource units (PRUs). For example, a preamble selected by a UE may be mapped to one or more groups of PRUs. The mapping may support piggybacking of uplink control information (UCI), frequency hopping on PUSCH, and / or iteration of multiple slots for msgA transmission. By piggybacking UCI into the payload in the msgA, this disclosure can provide flexibility in the selection of MCS and waveforms, as well as resource allocation for DMRS and PUSCH on the PRUs. Furthermore, allowing the payload to hop to different frequencies on the PUSCH during msgA transmission can lead to improved frequency diversity and interference averaging. In addition, enabling the payload to repeat across multiple slots within msgA transmission can enhance coverage and / or increase reliability.

[0008] In some aspects of this disclosure, a method, a computer-readable storage medium, and an apparatus are provided. The apparatus may be a UE. In one aspect, the apparatus receives random access configuration information from a base station. Based on the random access configuration information, the apparatus determines a preamble for a random access message from a group of preambles for random access opportunities (ROs). Based on the preamble and a mapping based on the random access configuration information, the apparatus determines one or more PRU resource sets for the random access message, where the random access configuration information maps the preamble to one or more PRU resource sets. The apparatus then transmits a random access message to the base station, the payload being transmitted using one or more PRU groups of one or more PRU resource sets based on the mapping.

[0009] In another aspect of this disclosure, a method, a computer-readable storage medium, and an apparatus are provided. The apparatus may be a base station. In one aspect, the apparatus transmits random access configuration information to a UE, the random access configuration information is transmitted using at least one of system information or RRC signaling, and the random access configuration information includes mapping of preambles to one or more PRU resource sets. The apparatus also receives a random access message from the UE, which includes a preamble on the RO, the preamble being from a preamble group. The random access message includes a payload received in one or more PRU groups of one or more PRU resource sets based on the mapping.

[0010] To achieve the above-mentioned and related objectives, one or more embodiments shall have features that are fully described below and, in particular, indicated in the claims. The following description and accompanying drawings detail some exemplary features of one or more embodiments. However, these features represent only a few of the various ways in which the principles of various embodiments may be employed, and this description shall include all such embodiments and their equivalents. [Brief explanation of the drawing]

[0011] [Figure 1] This figure shows examples of wireless communication systems and access networks. [Figure 2A] This figure shows an example of the first 5G / NR frame. [Figure 2B] This figure shows an example of a DL channel within a 5G / NR subframe. [Figure 2C] This figure shows an example of a second 5G / NR frame. [Figure 2D] This figure shows an example of a UL channel within a 5G / NR subframe. [Figure 3] This diagram shows examples of base stations and user equipment (UEs) within an access network. [Figure 4] This diagram shows an example communication flow between the UE and the base station. [Figure 5] This figure shows an example of sending msgA in a two-step RACH. [Figure 6] This figure shows an example of one-to-many mapping of preambles to PRUs. [Figure 7] This figure shows another example of a one-to-many mapping of preambles to PRUs. [Figure 8] This figure shows an example of a one-to-many mapping of preambles to PRUs to support UCI piggyback on payloads. [Figure 9] This figure shows an example of a one-to-many mapping of preambles to PRUs to support frequency hopping for payload transmission. [Figure 10] FIG. showing an example of a one-to-many mapping of a preamble to a PRU to support repetition of multiple slots for payload transmission. [Figure 11] FIG. showing an example of a one-to-many mapping of a preamble to a PRU to support the combination of piggybacking of UCI on a payload and frequency hopping and / or multiple slot repetition for payload transmission. [Figure 12] FIG. is a flowchart of a method of wireless communication in a UE. [Figure 13] FIG. is a conceptual data flow diagram showing the data flow between different means / components in an exemplary apparatus. [Figure 14] FIG. shows an example of a hardware implementation form of an apparatus using a processing system. [Figure 15] FIG. is a flowchart of a method of wireless communication in a base station. [Figure 16] FIG. is a conceptual data flow diagram showing the data flow between different means / components in an exemplary apparatus. [Figure 17] FIG. shows an example of a hardware implementation form of an apparatus using a processing system.

MODE FOR CARRYING OUT THE INVENTION

[0012] The detailed description set forth below in connection with the appended drawings is intended as a description of various configurations and is not intended to represent the only configuration in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of the various concepts. It will be apparent to those skilled in the art, however, that these concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form in order to avoid obscuring such concepts.

[0013] Next, some aspects of the telecommunications system are presented with reference to various devices and methods. These devices and methods are described in the following detailed description and are shown in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0014] By way of example, an element, or any part of an element, or any combination of elements can be implemented as a "processing system" that includes 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 (SoC), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gate logic, discrete hardware circuits, and other suitable hardware configured to perform the various functions described throughout this disclosure. One or more of the processors in the processing system can execute software. Software should be broadly construed to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc., regardless of the name given to it, such as software, firmware, middleware, microcode, hardware description language, etc.

[0015] [[ID=~]] Accordingly, in one or more exemplary embodiments, the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored on a computer-readable storage medium or encoded on a computer-readable storage medium as one or more instructions or codes. Computer-readable storage medium includes computer storage medium. A storage medium may be any available medium that can be accessed by a computer. Such computer-readable storage medium may include, but not limited to, 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 the computer-readable storage mediums of the types described above, or any other medium that can be used to store computer executable code in the form of instructions or data structures accessible by a computer.

[0016] Figure 1 shows an example of a wireless communication system and access network 100. The wireless communication system (also called a wireless wide area network (WWAN)) includes a base station 102, an UE 104, an advanced packet core (EPC) 160, and another core network 190 (for example, a 5G core (5GC)). The base station 102 may include macrocells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Macrocells include base stations. Small cells include femtocells, picocells, and microcells.

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

[0018] Base station 102 can communicate wirelessly with UE 104. Each base station 102 can provide communication coverage to its respective geographical coverage area 110. There may be overlapping geographical coverage areas 110. For example, a small cell 102' may have a coverage area 110' that overlaps with the coverage area 110 of one or more macro base stations 102. A network that includes both small cells and macro cells is sometimes called a heterogeneous network. A heterogeneous network may also include Home Evolved Node B (eNB) (HeNB) which can serve a limited group known as a Limited Subscriber Group (CSG). The communication link 120 between base station 102 and UE 104 may include uplink (UL) transmissions from UE 104 to base station 102 (also called a reverse link) and / or downlink (DL) transmissions from base station 102 to UE 104 (also called a forward link). Communication link 120 may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may be through one or more carriers. Base station 102 / UE104 may use a spectrum with bandwidth up to Y MHz per carrier (e.g., 5, 10, 15, 20, 100, 400 MHz, etc.) allocated in carrier aggregation up to a total of Yx MHz (x component carriers) used for transmission in each direction. Carriers may or may not be adjacent to one another. Carrier allocation may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL than to UL). Component carriers may include primary component carriers and one or more secondary component carriers. Primary component carriers may be called primary cells (PCells), and secondary component carriers may be called secondary cells (SCells).

[0019] Several UE104s may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use the DL / UL WWAN spectrum. The D2D communication link 158 may use one or more sidelink channels, such as the Physical Sidelink Broadcast Channel (PSBCH), Physical Sidelink Discovery Channel (PSDCH), Physical Sidelink Sharing Channel (PSSCH), and Physical Sidelink Control Channel (PSCCH). D2D communication may also be conducted through various wireless D2D communication systems, such as FlashLinQ, WiMedia, Bluetooth®, ZigBee®, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.

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

[0021] Small cell 102' can operate in licensed and / or unlicensed frequency spectrums. When operating in the unlicensed frequency spectrum, small cell 102' can utilize NR and use the same 5GHz unlicensed frequency spectrum used by Wi-Fi AP150. Small cell 102' utilizing NR in the unlicensed frequency spectrum can enhance coverage to the access network and / or increase the capacity of the access network.

[0022] Base station 102 may include and / or be referred to as an eNB, gNodeB (gNB), or other type of base station, whether it be a small cell 102' or a large cell (e.g., a macro base station). Some base stations, such as gNB180, may communicate with UE104 and operate in the conventional sub-6 GHz spectrum, millimeter wave (mmW) frequencies, and / or quasi-mmW frequencies. When gNB180 operates in mmW or quasi-mmW frequencies, gNB180 may be referred to as an mmW base station. Extremely high frequency (EHF) is a part of RF in the electromagnetic spectrum. EHF has a range from 30 GHz to 300 GHz and wavelengths between 1 millimeter and 10 millimeters. Radio waves in that band are sometimes called millimeter waves. Quasi-mmW may extend downwards to a frequency of 3 GHz with a wavelength of 100 millimeters. The very high frequency (SHF) band extends between 3 GHz and 30 GHz and is also called centimeter waves. Communications using mmW / quasi-mmW radio frequency bands (e.g., 3 GHz to 300 GHz) have extremely high path loss and short distances. An mmW base station 180 may utilize beamforming 182 together with a UE 104 to compensate for the extremely high path loss and short distances. Both the base station 180 and the UE 104 may include multiple antennas, such as antenna elements, antenna panels, and / or antenna arrays, to facilitate beamforming.

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

[0024] EPC160 may include a Mobility Management Entity (MME) 162, another MME 164, a serving gateway 166, a Multimedia Broadcast Multicast Service (MBMS) gateway 168, a Broadcast Multicast Service Center (BM-SC) 170, and a Packet Data Network (PDN) gateway 172. MME 162 may communicate with a Home Subscriber Server (HSS) 174. MME 162 is the control node that handles signaling between UE 104 and EPC160. Generally, MME 162 manages bearers and connections. All user Internet Protocol (IP) packets are forwarded through the serving gateway 166, which itself connects to the PDN gateway 172. The PDN gateway 172 provides UE IP address allocation and other functions. The PDN gateway 172 and BM-SC 170 connect to the IP service 176. The IP service 176 may include the Internet, intranet, IP multimedia subsystem (IMS), PS streaming service, and / or other IP services. The BM-SC 170 may provide functionality for MBMS user service provisioning and distribution. The BM-SC 170 may act as an entry point for content provider MBMS transmissions, may be used to authorize and initiate MBMS bearer services within a public land mobile network (PLMN), and may be used to schedule MBMS transmissions. The MBMS gateway 168 may be used to distribute MBMS traffic to base stations 102 belonging to a multicast broadcast single frequency network (MBSFN) area broadcasting specific services, and may be responsible for session management (start / stop) and collecting eMBMS-related billing information.

[0025] The core network 190 may include Access and Mobility Management Function (AMF) 192, other AMFs 193, Session Management Function (SMF) 194, and User Plane Function (UPF) 195. AMF 192 may communicate with Unified Data Management (UDM) 196. AMF 192 is a control node that handles signaling between UE 104 and the core network 190. Generally, AMF 192 provides QoS flow and session management. All user Internet Protocol (IP) packets are forwarded through UPF 195. UPF 195 provides UE IP address allocation and other functions. UPF 195 connects to IP services 197. IP services 197 may include the Internet, intranet, IP multimedia subsystem (IMS), PS streaming services, and / or other IP services.

[0026] Base stations may include and / or be referred to as gNB, Node B, eNB, access point, transceiver base station, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), transmit / receive point (TRP), or any other appropriate term. Base station 102 provides access points to EPC 160 or core network 190 to UE 104. Examples of UE 104 include cell phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablets, smart devices, wearable devices, vehicles, electric meters, gas pumps, large or small kitchen appliances, health management devices, implants, sensors / actuators, displays, or any other similar functional devices. Some UE 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, cardiac monitors, etc.). The UE104 may also be referred to as station, mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or any other preferred term.

[0027] Referring again to Figure 1, in some embodiments, UE 104 may also include RACH UE component 198, which receives random access configuration information from base stations 102 / 180, determines a preamble for a random access message from a preamble group for RO based on the random access configuration information, determines one or more PRU resource sets for the random access message based on the preamble and a mapping based on the random access configuration information, maps the preamble to one or more PRU resource sets, and sends a random access message to the base station, which includes the preamble and payload, and the payload is sent using one or more PRU groups of one or more PRU resource sets based on the mapping.

[0028] Referring further to Figure 1, in another embodiment, base stations 102 / 180 may also include a RACH base station component 199, which is configured to transmit random access configuration information to UE 104, the random access configuration information being transmitted using at least one of system information or RRC signaling, and the random access configuration information includes mapping of preambles to one or more PRU resource sets. The RACH base station component 199 is also configured to receive random access messages from the UE, which include preambles on the RO, the preambles being from a preamble group. The random access message includes a payload received in one or more PRU groups of one or more PRU resource sets based on the mapping.

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

[0030] Figure 2A is Figure 200, which shows an example of a first subframe in a 5G / NR frame structure. Figure 2B is Figure 230, which shows an example of a DL channel in a 5G / NR subframe. Figure 2C is Figure 250, which shows an example of a second subframe in a 5G / NR frame structure. Figure 2D is Figure 280, which shows an example of a UL channel in a 5G / NR subframe. The 5G / NR frame structure may be FDD, where for a particular set of subcarriers (carrier system bandwidth), the subframes within the set of subcarriers are dedicated to either DL or UL, or it may be TDD, where for a particular set of subcarriers (carrier system bandwidth), the subframes within the set of subcarriers are dedicated to both DL and UL. In the example given in Figures 2A and 2C, the 5G / NR frame structure is assumed to be TDD, subframe 4 is configured with slot format 28 (usually with DL), where D is DL, U is UL, and X is flexible for use between DL and UL, and subframe 3 is configured with slot format 34 (usually with UL). Subframes 3 and 4 are shown with slot formats 34 and 28, respectively, but any particular subframe may be configured with any of the various available slot formats 0 to 61. Slot formats 0 and 1 are all DL and UL, respectively. The other slot formats 2 to 61 include DL, UL, and a mix of flexible symbols. The UE is configured with a slot format (dynamically via DL control information (DCI) or semi-statically / statically via radio resource control (RRC) signaling) through the received slot format indicator (SFI). Please note that the following explanation also applies to the TDD 5G / NR frame structure.

[0031] Other wireless communication technologies may have different frame structures and / or different channels. A frame (10 ms) may be divided into 10 equally sized subframes (1 ms). Each subframe may contain one or more time slots. Subframes may also contain minislots that may contain 7, 4, or 2 symbols. Each slot may contain 7 or 14 symbols depending on the slot configuration. In slot configuration 0, each slot may contain 14 symbols, and in slot configuration 1, each slot may contain 7 symbols. Symbols on DL may be cyclic prefix (CP) OFDM (CP-OFDM) symbols. Symbols on UL may be CP-OFDM symbols (for high-throughput scenarios) or discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbols (also called single-carrier frequency-division multiple access (SC-FDMA) symbols) (limited to single-stream transmission for power-limited scenarios). The number of slots in a subframe is based on the slot configuration and numerology. In slot configuration 0, different numerologies μ0-5 allow 1, 2, 4, 8, 16, and 32 slots per subframe, respectively. In slot configuration 1, different numerologies 0-2 allow 2, 4, and 8 slots per subframe, respectively. Therefore, for slot configuration 0 and numerology μ, there are 14 symbols / slot and 2 μ There are 2 slots / subframes. The subcarrier interval and symbol length / duration depend on the numerology. The subcarrier interval is 2 μ*It may be equal to 15kHz, and μ is numerology 0 to 5. Therefore, numerology μ=0 has a subcarrier interval of 15kHz, and numerology μ=5 has a subcarrier interval of 480kHz. The symbol length / duration has an inverse relationship with the subcarrier interval. Figures 2A-2D give examples of slot configuration 0, which has 14 symbols per slot, and numerology μ=2, which has 4 slots per subframe. The slot duration is 0.25ms, the subcarrier interval is 60kHz, and the symbol duration is approximately 16.67μs.

[0032] A resource grid can be used to represent a frame structure. Each time slot contains a resource block (RB) (also called a physical RB (PRB)) spanning 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.

[0033] As shown in Figure 2A, some of the REs carry a reference (pilot) signal (RS) for the UE. The RS is used for channel estimation in the UE, and for a certain configuration, it is a demodulated RS (DM-RS) (where 100x is the port number). x Although shown as such, other DM-RS configurations are possible) and may include a channel state information reference signal (CSI-RS). RS may also include beam measurement RS (BRS), beam improvement RS (BRRS), and phase tracking RS (PT-RS).

[0034] Figure 2B shows examples of various DL channels within a frame subframe. A physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs), each CCE containing nine RE groups (REGs), and each REG containing four consecutive REs in the OFDM symbol. A primary synchronization signal (PSS) may be in symbol 2 of a particular subframe of the frame. The PSS is used by UE104 to determine subframe / symbol timing and physical layer identification information. A secondary synchronization signal (SSS) may be in symbol 4 of a particular subframe of the frame. The SSS is used by UE to determine the physical layer cell identification information group number and radio frame timing. Based on the physical layer identification information and physical layer cell identification information group number, UE can determine the physical cell identifier (PCI). Based on the PCI, UE can determine the location of the DM-RS described above. A physical broadcast channel (PBCH) carrying a Master Information Block (MIB) can be logically grouped with PSS and SSS to form a Synchronization Signal (SS) / PBCH block. The MIB provides the number of RBs and the System Frame Number (SFN) within the system bandwidth. The physical downlink shared channel (PDSCH) carries user data, broadcast system information not transmitted through the PBCH, such as System Information Blocks (SIBs), and paging messages.

[0035] As shown in Figure 2C, some of the REs carry DM-RS for channel estimation at the base station (shown as R for one particular configuration, but other DM-RS configurations are possible). The UE may transmit DM-RS for the physical uplink control channel (PUCCH) and for the physical uplink shared channel (PUSCH). PUSCH DM-RS may be transmitted in the first one or two symbols of the PUSCH. PUCCH DM-RS may 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 may transmit a sounding reference signal (SRS). SRS may be transmitted in the last symbol of a subframe. SRS may have a comb structure, and the UE may transmit SRS in one of the combs. SRS may be used by the base station for channel quality estimation to enable frequency-dependent scheduling on the UL.

[0036] Figure 2D shows examples of various UL channels within a frame subframe. In one configuration, the PUCCH may be arranged as shown. The PUCCH carries uplink control information (UCI) such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and HARQ ACK / NACK feedback. The PUCCH may carry data and may be further used to carry buffer status reports (BSR), power headroom reports (PHR), and / or UCI.

[0037] Figure 3 is a block diagram of a base station 310 communicating with UE350 in the access network. In DL, IP packets from EPC160 can be provided to the controller / processor 375. The controller / processor 375 implements Layer 3 and Layer 2 functions. Layer 3 includes the Radio Resource Control (RRC) layer, and Layer 2 includes the Service Data Adaptive Protocol (SDAP) layer, the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer, and the Medium Access Control (MAC) layer. The controller / processor 375 includes 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 correction, 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 forwarding upper layer packet data units (PDUs), error correction via ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), and MAC from TBs. It provides SDU demultiplexing, scheduling information reporting, error correction via HARQ, priority processing, and MAC layer functionality associated with logical channel prioritization.

[0038] The transmit (TX) processor 316 and the 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 on the transport channel, forward error correction (FEC) coding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 handles mapping to signal constellations based on various modulation schemes (e.g., 2-phase shift keying (BPSK), 4-phase shift keying (QPSK), M-phase shift keying (M-PSK), M-phase quadrature amplitude modulation (M-QAM)). Coded and modulated symbols may then be divided into parallel streams. Each stream is then mapped to an OFDM subcarrier to generate a physical channel that carries a time-domain OFDM symbol stream, multiplexed with a reference signal (e.g., a pilot) in the time-domain and / or frequency-domain, and then possibly synthesized together using an inverse fast Fourier transform (IFFT). The OFDM streams are spatially precoded to generate multiple spatial streams. Channel estimates from channel estimator 374 may be used to determine the coding and modulation scheme and for spatial processing. Channel estimates may be derived from a reference signal and / or channel state feedback transmitted by UE350. Each spatial stream may then be provided to different antennas 320 via a separate transmitter 318TX. Each transmitter 318TX may modulate an RF carrier using its respective spatial stream for transmission.

[0039] In UE350, each receiver 354RX receives signals through its respective antenna 352. Each receiver 354RX reconstructs the information modulated on the RF carrier and provides this information to the receiver (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 may perform spatial processing on the information to reconstruct any spatial stream directed to UE350. Multiple spatial streams, if directed to UE350, 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 convert the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal has a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, and the reference signal, are reconstructed and demodulated by determining the most likely signal constellation point transmitted by the base station 310. These soft decisions may be based on channel estimates calculated by the channel estimator 358. The soft decisions are then decoded and deinterleaved to reconstruct the data and control signals originally transmitted by the base station 310 on the physical channel. The data and control signals are then provided to the controller / processor 359, which implements Layer 3 and Layer 2 functions.

[0040] The controller / processor 359 may be associated with memory 360, which stores program code and data. Memory 360 is sometimes referred to as a computer-readable storage medium. In UL, the controller / processor 359 reconstructs IP packets from the EPC160 by performing demultiplexing between transport and logical channels, packet reassembly, decoding, header decompression, and control signal processing. The controller / processor 359 is also responsible for error detection using the ACK and / or NACK protocols to support HARQ operation.

[0041] Similar to the functions described for DL ​​transmission by base station 310, the controller / processor 359 provides RRC layer functions associated with system information (e.g., MIB, SIB) collection, RRC connectivity, and measurement reporting; PDCP layer functions associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functions associated with the transfer of upper layer PDUs, error correction via ARQ, concatenation, segmentation, and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and sorting of RLC data PDUs; and MAC layer functions associated with mapping between logical channels and transport channels, multiplexing MAC SDUs onto TB, demultiplexing MAC SDUs from TB, scheduling information reporting, error correction via HARQ, priority processing, and logical channel prioritization.

[0042] The channel estimate derived by the channel estimator 358 from a reference signal or feedback transmitted by the base station 310 may be used by the TX processor 368 to select an appropriate coding and modulation scheme to facilitate spatial processing. The spatial stream generated by the TX processor 368 may be provided to different antennas 352 via separate transmitters 354TX. Each transmitter 354TX may modulate the RF carrier in its respective spatial stream for transmission.

[0043] UL transmission is processed at base station 310 in a manner similar to that described for receiver functions in UE350. Each receiver 318RX receives the signal through its respective antenna 320. Each receiver 318RX reconstructs the information modulated on the RF carrier and provides this information to RX processor 370.

[0044] The controller / processor 375 may be associated with memory 376 that stores program code and data. Memory 376 is sometimes referred to as a computer-readable storage medium. In UL, the controller / processor 375 reconstructs IP packets from the UE350 by performing demultiplexing between transport and logical channels, packet reassembly, decoding, header decompression, and control signal processing. IP packets from the controller / processor 375 may be served to the EPC160. The controller / processor 375 is also responsible for error detection using the ACK and / or NACK protocols to support HARQ operation.

[0045] At least one of the TX processor 368, RX processor 356, and controller / processor 359 may be configured to perform an embodiment related to the RACH UE component 198 shown in Figure 1.

[0046] At least one of the TX processor 316, RX processor 370, and controller / processor 375 may be configured to perform an embodiment related to the RACH base station component 199 in Figure 1.

[0047] In a four-step contention-based random access (RACH) procedure, four messages may be provided between the UE and the base station. For example, during the initial attach procedure, the UE may send a preamble to the base station (e.g., message 1), receive a random access response (RAR) from the base station (e.g., message 2), send an RRC connection request message or other payload to the base station (e.g., message 3), and receive an RRC connection setup message or other transmission from the base station that will undergo contention resolution (e.g., message 4). This four-step RACH procedure can be simplified into a two-step RACH procedure in which the UE sends the preamble and payload in the first message. For example, message A ("msgA") in the two-step RACH procedure may correspond to messages 1 and 3 in the four-step RACH procedure, and message B ("msgB") may correspond to messages 2 and 4 in the four-step RACH procedure. Therefore, in a two-step RACH procedure, the UE may send a preamble followed by a payload to the base station in msgA transmission, while the base station may send RAR and RRC response messages to the UE in msgB transmission.

[0048] Figure 4 shows an exemplary communication flow 400 between UE 402 and base station 404 as part of a two-step RACH procedure. Before initiating the two-step RACH process, the UE may first receive random access configuration information 406 from the base station. For example, the UE may receive SSB, SIB, and / or reference signal broadcasts from the base station. The UE may process these signals and channels and determine the configuration for the two-step RACH. For example, in 408, the UE may determine one of the following: downlink synchronization, decoding information based on at least one of the SSB, SIB, or reference signal, or other measurement information for random access with base station 404.

[0049] After the UE obtains random access configuration information 406, the UE may generate and transmit msgA409. MsgA409 is an uplink transmission from the UE 402 to the base station 404, comprising at least two parts: a preamble 410 and a payload 412. Once the UE determines the preamble from a group of preamble sequences in a random access opportunity (RO), the UE transmits the preamble 410, followed by the payload 412, to the base station. The payload may include, for example, an RRC message (similar to message 3 in a four-step RACH process), user plane (UP) or control plane (CP) data, media access control (MAC) control elements (CE) (e.g., a buffer status report (BSR) or power headroom report (PHR)), and, in some embodiments, piggybacked uplink control information (UCI). A demodulation reference signal (DMRS) may also be transmitted with the payload. When msgA reaches the base station, the base station first processes the preamble at 414 and then the payload at 416. If the preamble processing is successful, base station 404 may then transmit msgB418 to UE402.

[0050] Figure 5 shows an exemplary msgA transmission in a two-step RACH. First, the payload of the msgA to be transmitted over PUSCH may be combined with cyclic redundancy check (CRC) in 502. Next, in 504, the payload may be encoded by a low-density parity check (LDPC) encoder, which may provide a method for controlling errors in data transmission over unreliable or noisy communication channels. Subsequently, the payload may be bit-scrambled in 506, the process of which may be enhanced with PUSCH scrambling ID extension 508. After bit scrambling 506, linear modulation 510 and optional transform precoding 512 may be applied to the payload. Subsequently, the payload is multiplexed with DMRS 518 via an inverse fast Fourier transform (IFFT) 514 (516). The DMRS is generated based on the preamble sequence ID 520 of the UE's selected preamble 522, which may be enhanced using the DMRS scrambling ID set extension 523. In addition, uplink control information (UCI) 524 may be piggybacked to payload transmission.

[0051] The preamble and payload can then be mapped in 526 to various radio resources to form msgA528. Resources for the payload may be physical uplink shared channel (PUSCH) resource units (PRUs), which may include time-frequency resources configured for transmitting the payload over the PUSCH, as well as antenna ports and sequence scrambling IDs configured for DMRS transmission (i.e., each PRU can be considered a PUSCH opportunity with DMRS resources). Since PUSCH transmission opportunities are configured in the frequency and time domains, and DMRS resources are configured in the time, frequency, and code domains, each PRU can be multiplexed into various PRU groups in the time, frequency, or code domains. Mapping rules or association rules may be applied between the preamble and the PRUs. Mapping rules or association rules may be determined from random access configuration information. The preamble and the multiplexed payload / DMRS (with or without piggybacked UCI) can be mapped to different PRUs or PRU groups. For example, the association rule could be a one-to-many mapping relationship between a preamble and a PRU. Therefore, when sending msgA, the UE may send the payload and DMRS on multiple PRUs or groups of PRUs that map to a single selected sequence of preambles.

[0052] The payload transmitted in msgA (e.g., msgA409, 528) may have varying payload sizes and cell coverage requirements. For example, UP data may have a larger payload size than RRC messages. Different types of payloads may require different modulation coding schemes (MCS). To support these diverse payloads, the msgA transmission in the two-step RACH procedure must allow for configurable MCS and configurable resource sizes in the time-frequency domain. This disclosure satisfies this need by providing a one-to-many mapping configuration between preambles and PRUs, where the preamble selected by the UE may be mapped to one or more groups of PRUs. This may include piggybacking of UCIs, frequency hopping on PUSCHs, and / or iteration of multiple slots for msgA transmissions. Piggybacking UCIs into the payload in msgA provides flexibility in MCS and waveform selection, as well as resource allocation for DMRS and PUSCHs in the PRUs. Furthermore, allowing the payload to hop to different frequencies on the PUSCH during msgA transmission can lead to improved frequency diversity and interference averaging. In addition, enabling the payload to repeat across multiple slots within msgA transmission can enhance coverage and / or increase reliability.

[0053] Figure 6 shows an exemplary time-frequency diagram 600 of a one-to-many mapping configuration of preambles to a PRU according to an aspect of the present disclosure. In the first message of a two-step RACH process, the UE transmits a preamble 602 to the base station on a random access opportunity (RO) 604. The UE determines a preamble from a preamble group 606, which may include multiple preambles 602 having different preamble sequences that can be transmitted on the same RO 604. For example, the preamble group 606 may include 64 preamble sequences, and the UE may determine a preamble 602 from these sequences for transmission on the time and frequency resources associated with the RO 604.

[0054] After the UE sends preamble 602 for msgA, the UE sends the payload for msgA. The payload may be sent to the base station using a PRU. As stated, different payloads may require different MCS or payload size coverage requirements. For example, as explained above, UP data may have a larger payload size than RRC messages and may require a smaller Modulation Coding Scheme (MCS) for different payloads. Therefore, to simplify payload resource allocation for these different sizes or MCSs, PRUs may be grouped into different PRU resource sets.

[0055] For example, Figure 6 shows a preamble group 606 for RO 604 associated with a first PRU resource set 608 and a second PRU resource set 610, where each PRU resource set contains one or more groups of PRUs. A PRU group 612 contains PRUs across different time / frequency resources within a resource set and may also be different from one another in a particular resource set, for example, by MCS. A PRU group 612 may also have different time / frequency resource sizes across multiple resource sets, while having similar time / frequency resource sizes within each resource set. For example, Figure 6 shows that the first PRU resource set 608 has six PRU groups 612 of the same smaller resource size (corresponding to different time / frequency resources and possibly different MCSs), while the second PRU resource set 610 has four PRU groups 612 of the same larger resource size (corresponding to different time / frequency resources and possibly different MCSs). This example is just an illustration. Any number of PRU groups 612 of any resource size may be included in PRU resource sets 608, 610 for different time / frequency resources. Furthermore, any number of PRU resource sets 608, 610 may be associated with or mapped to a particular preamble group 606.

[0056] In one embodiment, a single preamble group 606 for RO604 may be associated with multiple PRU resource sets. More specifically, some preambles within a preamble group may be associated with one PRU resource set, while other preambles within the preamble group may be associated with another PRU resource set. For example, referring to Figure 6, one preamble 602a within preamble group 606 may be mapped to PRU group 612a in a first PRU resource set 608, while another preamble 602b within preamble group 606 may be mapped to PRU group 612d in a second PRU resource set 610. Thus, if the UE decides to send a preamble associated with PRU group 612a in the first PRU resource set 608, the UE may later send a payload using one or more PRUs in that PRU group 612a. Similarly, if the UE decides to send a preamble associated with PRU group 612b of a second PRU resource set 610, the UE may later send a payload using one or more PRUs in that PRU group 612d.

[0057] PRU resource sets are orthogonal in the time domain, frequency domain, or code domain. For example, Figure 6 shows a first PRU resource set 608 and a second PRU resource set 610 that are orthogonal to each other in the time domain 614, but PRU resource sets may also be orthogonal in the frequency domain 616 or code domain. For example, the second PRU resource set 610 may be above or below the first resource set 608 in the time-frequency domain figure 600 of Figure 6. Furthermore, within each PRU resource set, different PRU groups may be orthogonal to each other in the time domain or frequency domain. For example, Figure 6 shows PRU groups 612a and 612c of the first PRU resource set 608 that are orthogonal to each other in the time domain 614, and PRU groups 612b and 612d of the second PRU resource set 610 that are orthogonal to each other in the frequency domain 616.

[0058] A preamble from a preamble group can be mapped to multiple PRUs within the same PRU resource set. Furthermore, a preamble from a preamble group can be mapped to multiple PRUs in different PRU resource sets. For example, referring again to Figure 6, one preamble in preamble group 606 can be mapped to PRU groups 612a and 612c of the first PRU resource set 608, to PRU groups 612b and 612d of the second PRU resource set 610, to PRU group 612c of the first PRU resource set 608 and PRU group 612d of the second PRU resource set 610, or to any combination of PRU group 612 and PRU resource sets 608 and 610. For example, Figure 6 shows preamble 1 602 which is mapped to PRU group 612c in the first resource set and PRU group 612b in the second PRU resource set.

[0059] Thus, a one-to-many mapping configuration is provided between a preamble and multiple PRU groups, however, other preambles in the preamble group configured for the RO may not support one-to-many mapping. Instead, these preambles may only support one-to-one mapping (e.g., one preamble associated with one PRU group) or many-to-one mapping (e.g., multiple preambles associated with the same PRU group). This disclosure enables such mapping. For example, Figure 7 shows a time-frequency diagram 700 in which the UE transmits preamble 702 on RO 704 to the base station. The preamble is determined from a preamble group 706 configured for RO 704, which includes a first set of preambles 708 and a second set of preambles 710, where each preamble in the first set of preambles 708 supports one-to-many mapping configurations, and each preamble in the second set of preambles 710 supports either one-to-one mapping configurations or many-to-one mapping configurations. Therefore, if one preamble group 706 configured for RO contains 64 preambles of different preamble sequences, then a first set of preambles 708 (e.g., three or another number) may be individually associated with multiple PRU groups 712 in the same or different PRU resource sets as described above, while other sets of preambles 710 (e.g., the rest) may be individually associated with one or more PRU groups 712 in the PRU resource sets. For example, in the example shown in Figure 7, preamble 2 702a may be associated with PRU groups 712a and 712b (one-to-many mapping), preamble 3 702b may be associated with PRU group 712c (one-to-one mapping), and preambles 4 702c and 5 702d may be associated with PRU group 712d (many-to-one mapping). Other combinations of preamble-to-PRU mappings are possible.

[0060] The first random access message may include a UCI in addition to the preamble and payload. Referring to Figure 8, in one embodiment, the UCI and payload in msgA may be mapped to different PRU groups based on the one-to-many mapping configuration described above in order to support the piggybacking of the UCI on the payload. For example, Figure 8 shows an exemplary time-frequency diagram 800 in which msgA includes a payload 802 and a UCI 804 containing information for configuring the payload. In one embodiment, the UCI 804 may show the MCS, transport block size (TBS), waveform, and resource allocation information for payload 802. In another embodiment, the UCI 804 may further show frequency-hopping patterns and / or multi-slot repetition information for payload 802, as described below.

[0061] In this example, the UE first determines a preamble from preamble group 806, which is associated with PRU groups 812 (e.g., PRU groups 812a, 812c) in the first PRU resource set 808, as described above with respect to Figure 6. For example, the preamble may be mapped to PRU group 812c in the first PRU resource set 808. This PRU group 812c carries a UCI 804 that provides configuration information for the payload 802 of msgA, including resource allocation information for another PRU group 812 (e.g., PRU groups 812b, 812d) in another PRU resource set 810. For example, the UCI 804 in PRU group 812c of the first PRU resource set 808 may allocate PRU group 812b of the second PRU resource set 810 to carry the payload 802. The UE may then use the allocated PRU group 812b of the second PRU resource set 810 linked from UCI804 to transmit the payload 802 (for example, over PUSCH).

[0062] As a result, the UE can piggyback the UCI 804 into the payload in msgA based on a one-to-many mapping configuration between the UE's determined preamble and multiple PRU groups 812. By using different PRU resource sets 808, 810, the first PRU group 812c carrying the UCI may have a different resource size and / or MCS than the second PRU group 812b carrying the payload. Furthermore, depending on the preamble selected by the UE from preamble group 806 on one RO, different PRU groups 812 and / or resource sets 808, 810 may be used for the UCI 804 and payload 802. Thus, this disclosure may provide flexibility in the selection of MCS and waveform when transmitting the payload in msgA to the base station with the piggybacked UCI, as well as resource allocation for DMRS and PUSCH in the PRU.

[0063] Referring to Figure 9, in one embodiment, the payload in msgA may be mapped to different PRU groups based on the one-to-many mapping configuration described above in Figure 6, in order to support frequency hopping for payload transmission. For example, Figure 9 shows an exemplary time-frequency diagram 900 in which msgA contains a payload 902 to be transmitted according to a hopping pattern on multiple PRU resource sets 908, 910. In this example, msgA does not contain piggybacked UCIs to constitute the payload, but it may contain piggybacked UCIs (see Figure 11). The hopping pattern may be intra-slot (for example, the msgA PUSCH configuration is a Type-B PUSCH mapping, and the msgA payload transmission may hop frequencies after a certain number of symbols in a slot of a physical resource block (PRB), with each hop occupying a pre-configured PRU) or inter-slot (for example, the msgA PUSCH configuration is a Type-A PUSCH mapping, and the msgA payload transmission may hop frequencies after a certain number of slots in one or more PRBs, with each hop occupying a pre-configured PRU). The msgA PUSCH configuration (for example, PUSCH mapping type A or B) may be one or more RRC parameters in the random access configuration information. Furthermore, the msgA PUSCH configuration (type A or type B) for idle or inactive UEs may be included in the time-domain resource allocation (TDRA) table.

[0064] The UE first determines a preamble from preamble group 906, which is associated with a PRU group in the first PRU resource set 908 (e.g., PRU groups 912a, 912c) as described above. For example, a preamble may be mapped to PRU group 912a in the first PRU resource set 908 for carrying payload 904a of msgA at a first frequency. Thus, each PRU in PRU group 912a may carry payload 904a of msgA at the first frequency for a predetermined duration, for example, the duration of PRU group 912a. Furthermore, based on either a dynamic or static frequency offset, PRU group 912a in the first PRU resource set 908 may be mapped to another PRU group in the second PRU resource set 910 (e.g., PRU group 912b or 912d) for carrying payload 904b of msgA at a second frequency. For example, the second frequency may be dynamically determined as a function of the first frequency, an index of the first PRU group 912a, an index of the first resource set 908, channel information within the first PRU group or the first resource set, or other information. The second frequency may also be based on a frequency hopping pattern acquired by the UE (e.g., in random access configuration information received from the base station, or in the UCI as described below). Alternatively, the second frequency may be statically determined to be at a fixed offset from the first frequency (e.g., 200 MHz or another frequency). Thus, each PRU in the PRU group 912d may carry the payload 904b of msgA at the second frequency for another predetermined duration, for example, for the duration of the PRU group 912d.This process may be repeated for subsequent frequencies until the payload 902 is fully transmitted. For example, after the UE hops from the first PRU group 912a in the first PRU resource set 908 to the second PRU group 912d in the second PRU resource set 910 to carry the payload 902 as described above, the UE may hop to the third PRU group in the second PRU resource set 910 (or to another PRU group in another PRU resource set) to transmit the payload 902 based on a dynamically or statically determined frequency offset or frequency hopping pattern.

[0065] Therefore, the preamble for msgA PUSCH in a two-step RACH can be mapped to multiple PRUs for intra-slot frequency hopping (as well as inter-slot frequency hopping). For example, for msgA PUSCH, the frequency offset can be provided by parameters of a higher layer. In the case of intra-slot frequency hopping, the starting RB in each hop may be given by:

[0066]

number

[0067] i=0 and i=1 are the first hop and the second hop, respectively, RB start This is the starting resource block (RB) within the uplink (UL) bandwidth portion (BWP), calculated from the resource block allocation information of resource allocation type 1, and RB offset This is the frequency offset in RB between two frequency hops. The number of symbols in the first hop is

number

number

number

[0068] As a result, the UE can transmit payload 902 in msgA according to a hopping pattern based on a one-to-many mapping configuration between the UE's determined preamble and multiple PRU groups. By using different PRU groups and / or PRU resource sets 908, 910, a first PRU group 912a carrying payload 904a may have a different frequency than a second PRU group 912d carrying payload 904b. Furthermore, depending on the preamble selected by the UE from preamble group 906 on one RO, different PRU groups and / or resource sets 908, 910 may be used for payload 902. Thus, this disclosure enables the transmission of payload 902 to the base station in msgA based on a hopping pattern of different frequencies on PUSCH, thereby resulting in improved frequency diversity and interference averaging.

[0069] Referring to Figure 10, in one embodiment, the payload in msgA may be mapped to different PRU groups based on the one-to-many mapping configuration described above in Figure 6, in order to support multiple slot iterations for payload transmission. For example, Figure 10 shows an exemplary time-frequency diagram 1000 in which msgA contains payload 1002a transmitted in multiple slots 1004a, 1004b on multiple PRU resource sets 1008, 1010. In this example, msgA does not contain piggybacked UCIs for constructing the payload, but it may contain piggybacked UCIs (see Figure 11). Multiple slot iterations can be inter-slot (for example, the msgA PUSCH configuration is a Type-A PUSCH mapping, where each iteration of msgA payload transmission occupies a pre-configured PRU). For example, multiple slot iterations of payloads 1002a, 1002b can span contiguous slots of one or more PRBs in the time domain (as shown, e.g., in PRU group 1012a, but possible for any PRU group) or non-contiguous slots of one or more PRBs in the time domain (as shown, e.g., in PRU group 1012b, but possible for any PRU group). Alternatively, multiple slot iterations can be inter-slots (e.g., the msgA PUSCH configuration is a Type-B PUSCH mapping, where each iteration of the msgA payload transmission occupies a pre-configured PRU in a PUSCH mini-slot). The msgA PUSCH configuration (e.g., PUSCH mapping type A or B) can be one or more RRC parameters in the random access configuration information. Furthermore, msgA PUSCH configurations (type A or type B) for idle or inactive UEs can be included in the time-domain resource allocation (TDRA) table.

[0070] The UE first determines a preamble from preamble group 1006, which is associated with PRU group 1012 (e.g., PRU groups 1012a, 1012c) in the first PRU resource set 1008, as described above. For example, a preamble may be mapped to PRU group 1012a in the first PRU resource set 1008 for carrying the payload 1002a of msgA in the first set of slots 1004a. Thus, each PRU in PRU group 1012a may carry the payload 1002a of msgA in the first set of slots 1004a for a predetermined time length, for example, between a number of consecutive (or non-consecutive) slots in the first set of slots 1004a. Furthermore, based on the dynamic or static determination of this number of slots, PRU group 1012a in the first PRU resource set 1008 may be mapped to another PRU group in the second PRU resource set 1010 (e.g., PRU group 1012b or 1012d) for iterating the payload 1002b of msgA in the second set of slots 1004b. For example, the second set of slots 1004b may be determined dynamically depending on the number of slots in the first set of slots 1004a, the index of the first PRU group 1012a, the index of the first resource set 1008, the channel information in the first PRU group 1012a or the first resource set 1008, or other information. The second set of slots 1004b may also be determined based on slot iteration information obtained by the UE (e.g., in random access configuration information received from the base station, or in the UCI as described below). Alternatively, the second set of slots 1004b may be statically determined to be at a fixed offset (e.g., 1 ms or other time length) from the first set of slots 1004a. Thus, each PRU in the PRU group 1012b may repeat the payload 1002b of msgA in the second set of slots 1004b for a predetermined time length, for example, between a number of non-consecutive (or consecutive) slots in the second set of slots 1004b.This process can be repeated for subsequent sets of consecutive or non-consecutive slots in the additional PRU group 1012 or PRU resource sets 1008, 1010.

[0071] As a result, the UE may transmit and repeat payloads 1002a and 1002b in msgA using multiple slot iterations, based on a one-to-many mapping configuration between the UE's determined preamble and multiple PRU groups 1012. By using different PRU groups 1012 and / or PRU resource sets 1008 and 1010, a second PRU group 1012b repeating payload 1002b may provide better coverage enhancement or reliability than the first PRU group 1012a that initially transmitted payload 1002a. Furthermore, depending on the preamble selected by the UE from preamble group 1006 on one RO, different PRU groups 1012 and / or resource sets 1008 and 1010 may be used for the payload. Therefore, this disclosure enables payloads 1002a and 1002b to be transmitted to and repeated at msgA based on the repetition of multiple slots on PUSCH, thereby resulting in enhanced coverage and transmission reliability.

[0072] Referring to Figure 11, in one embodiment, the UCI and payload in msgA may be mapped to different PRU groups based on the one-to-many mapping configuration described above to support a combination of piggybacking of the UCI on the payload and frequency hopping and / or multi-slot repetition for payload transmission. For example, Figure 11 shows an exemplary time-frequency diagram 1100 in which msgA contains UCI 1104 containing information for configuring payload 1102 (as described above in Figure 8), and msgA contains payload 1102 to be transmitted according to a hopping pattern on multiple PRU resource sets 1108, 1110 (as described above in Figure 9). Payload 1102 may, additionally or alternatively, be transmitted in multiple slots on multiple PRU resource sets (as described above in Figure 10). In one embodiment, UCI 1104 may contain MCS, transport block size (TBS), waveform, payload resource allocation information, and frequency hopping pattern and / or multi-slot repetition information for the payload. The hopping pattern can be intra-slot (for example, the payload transmission may hop in frequency after a certain number of symbols in a slot of a physical resource block (PRB)) or inter-slot (for example, the payload transmission may hop in frequency after a certain number of slots in one or more PRBs). Furthermore, the iteration of multiple slots of payload 1102 may span consecutive or non-consecutive slots in one or more PRBs in the time domain.

[0073] In this example, the UE first determines a preamble from preamble group 1106, which is associated with PRU groups 1112 (e.g., PRU groups 1112a, 1112c) in the first PRU resource set 1108, as described above with respect to Figure 6. For example, the preamble may be mapped to the first PRU group 1112c in the first PRU resource set. This PRU group 1112c carries a UCI 1104 that provides configuration information for the payload 1102 of msgA, including resource allocation information for another PRU group (e.g., PRU groups 1112b, 1112d) in another PRU resource set. For example, the UCI in the first PRU group 1112c of the first PRU resource set 1108 may allocate the second PRU group 1112b of the second PRU resource set 1110 to carry the payload 1102. The UE may then use the second PRU group 1112b of the second PRU resource set 1110 linked from UCI1104 to transmit the payload 1102 (for example, over PUSCH).

[0074] Each PRU in the second PRU group 1112b may carry or repeat the payload 1102a of msgA in a first set of first frequencies or slots for a predetermined duration, for example, the duration of the PRU group 1112b. Furthermore, based on frequency hopping information in the UCI 1104, or based on a number of frequency offsets or slots determined dynamically or statically, the second PRU group 1112b in the second PRU resource set 1110 may be mapped to a third PRU group 1112d in the second PRU resource set 1110 for carrying or repeating the payload 1102b of msgA in a second set of second frequencies or slots. For example, each second set of second frequencies or slots may be based on frequency hopping pattern or slot repeat information determined by the UE and configured in the UCI 1104. Alternatively, the second set of frequencies or slots may be dynamically determined as a function of the first set of frequencies or slots, an index of the second PRU group 1112b, an index of the second resource set 1110, channel information in the second PRU group 1112b or the second resource set 1110, or other information. Alternatively, the second set of frequencies or slots may be statically determined to be at a fixed offset (e.g., 200 MHz or other frequencies or 1 ms or other durations) from the first set of frequencies or slots. Thus, each PRU in the third PRU group 1112d may carry or repeat the payload 1102b of msgA in the second set of frequencies or slots for another predetermined duration, for example, for the duration of the PRU group 1112d. This process may be repeated for subsequent frequencies until the payload 1102 is fully transmitted, and similarly, for subsequent sets of consecutive or non-consecutive slots in additional PRU groups 1112 or PRU resource sets 1108, 1110.

[0075] As a result, in msgA, the UE may include a UCI 1104 with payload 1102, transmit payloads 1102a and 1102b according to a hopping pattern, and transmit and repeat payloads using multiple slot iterations based on a determined preamble of the UE and a one-to-many mapping configuration between multiple PRU groups 1112. By using different PRU resource sets 1108 and 1110, the first PRU group 1112c carrying the UCI 1104 may have a different resource size and / or MCS than the second PRU group 1112b carrying payload 1102a, and the second PRU group 1112b carrying payload 1102a may have a different frequency than the third PRU group 1112d carrying payload 1102b. When the payload 1102 is repeated, a third PRU group 1112d may also provide better coverage enhancement or reliability than the second PRU group 1112b that initially transmitted the payload. Furthermore, depending on the preamble selected by the UE from preamble group 1106 on one RO, different PRU groups 1112 and / or resource sets 1108, 1110 may be used for the UCI 1104 and payload 1102. Thus, this disclosure may provide flexibility in MCS and waveform selection when transmitting payload 1102 in msgA to a base station with a piggybacked UCI, as well as resource allocation for DMRS and PUSCH in the PRU. This disclosure also enables the transmission of payload 1102 in msgA to a base station based on different frequency hopping patterns on PUSCH, thereby resulting in improved frequency diversity and interference averaging. Furthermore, this disclosure enables the payload 1102 to be transmitted to and repeated at msgA based on the repetition of multiple slots on PUSCH, thereby resulting in enhanced coverage and transmission reliability.

[0076] Figure 12 is a flowchart 1200 of a wireless communication method. The method can be performed by a UE (e.g., UE104, 350, 402, device 1302 / 1302', processing system 1414, which may include memory 360, may be the entire UE350, or may be components of the UE350 such as TX processor 368, RX processor 356, and / or controller / processor 359). The method allows the UE to send msgA transmissions in a two-step RACH process using a one-to-many mapping configuration between preambles and PRUs, and the preamble selected by the UE may be mapped to one or more groups of PRUs to support UCI piggyback, PUSCH hopping, and / or multi-slot iteration.

[0077] In step 1202, the UE receives random access configuration information from the base station. For example, step 1202 may be performed by the random access configuration component 1306 in Figure 13. Referring to Figure 4, for example, the UE may receive random access configuration information 406 from the base station before the start of the two-step RACH process. For example, the UE may receive SSB, SIB, and / or reference signal broadcasts from the base station. The UE can process these signals and channels and determine the configuration for the two-step RACH.

[0078] In 1204, the UE determines a preamble for a random access message from a preamble group for the RO. For example, 1204 may be performed by the preamble component 1308 in Figure 13. Referring to Figure 6, for example, the UE may determine a preamble from preamble group 606, which may include multiple preambles 602 having different preamble sequences that can be transmitted on the same RO 604. In one example, preamble group 606 may include 64 preamble sequences, and the UE may determine a preamble 602 from these sequences for transmission on the time and frequency resources associated with the RO 604.

[0079] The UE determines the mapping based on the random access configuration information. For example, 1206 may be performed by the mapping component 1310 in Figure 13. The mapping may consist of one-to-many mapping (e.g., one preamble is associated with multiple PRU groups), one-to-one mapping (e.g., one preamble is associated with one PRU group), or many-to-one mapping (e.g., multiple preambles are associated with the same PRU group). For example, referring to Figure 7, the UE may determine from the random access configuration that the preambles in preamble group 706 support one-to-many, one-to-one, or many-to-one mapping configurations. More specifically, the UE may determine from the random access configuration that some preambles may be associated with multiple PRU groups in the same or different PRU resource sets, while other preambles may be associated with only one PRU group individually or with multiple PRU groups. Therefore, in one example, if one preamble group 706 configured for RO contains 64 preambles of different preamble sequences, the UE may determine that preamble 2 702a is associated with PRU groups 712a and 712b (one-to-many mapping), preamble 3 702b is associated with PRU group 712c (one-to-one mapping), and preamble 4 702c and preamble 5 702d are associated with PRU group 712d (many-to-one mapping).

[0080] Each PRU group may comprise a time-frequency resource associated with PUSCH transmission and an antenna port and sequence scrambling identification information associated with DMRS transmission. For example, referring to Figure 5, the preamble and payload may be mapped in 526 to various radio resources (e.g., PRUs) to form msgA528, and each PRU includes a time-frequency resource configured for transmitting the payload over PUSCH, as well as an antenna port and sequence scrambling ID configured for DMRS transmission. Each PRU may be multiplexed into various PRU groups in the time domain, frequency domain, or code domain, and the preamble and multiplexed payload / DMRS may be mapped to different PRUs or PRU groups based on association rules between the preamble and PRUs determined from random access configuration information.

[0081] In 1206, the UE determines one or more PRU resource sets for random access messages based on the preamble, and the random access configuration information maps the preamble to one or more PRU resource sets. For example, 1208 may be performed by the PRU resource set component 1312 in Figure 13. One or more PRU resource sets may comprise a first PRU resource set and a second PRU resource set. For example, referring to Figure 6, the UE may determine a first PRU resource set 608 and a second PRU resource set 610 in relation to a preamble group 606 for RO 604 from which a preamble 602 is determined, and each PRU resource set contains one or more groups of PRUs (PRU groups 612). Based on the mapping obtained from the random access configuration information (e.g., a one-to-many mapping configuration), the UE may determine which PRU resource sets 608 and / or 610 contain one or more PRU groups 612 that are mapped to the selected preamble 602.

[0082] In one embodiment, one or more PRU resource sets comprise multiple PRU resource sets associated with a preamble group configured for an RO, where the resource sets are orthogonal in at least one of the time domain, frequency domain, or code domain. For example, referring to Figure 6, one preamble group 606 for RO 604 may be associated with multiple PRU resource sets. More specifically, some preambles in a preamble group may be associated with one PRU resource set, while other preambles in the preamble group may be associated with another PRU resource set. PRU resource sets can also be orthogonal in the time domain, frequency domain, or code domain. For example, Figure 6 shows a first PRU resource set 608 and a second PRU resource set 610 that are orthogonal to each other in the time domain 614, but PRU resource sets can also be orthogonal in the frequency domain 616 or the code domain.

[0083] In another embodiment, one or more PRU resource sets comprise multiple PRUs associated with preamble groups configured for RO, and preambles determined by the UE are associated with multiple PRU groups within a single PRU resource set. For example, referring to Figure 6, one preamble group 606 for RO 604 may be associated with multiple PRU resource sets. Preambles determined from preamble groups may be mapped to multiple PRUs within the same PRU resource set. For example, one preamble 602a in preamble group 606 may be mapped to PRU groups 612a and 612c of a first PRU resource set 608, or to PRU groups 612b and 612d of a second PRU resource set 610.

[0084] In a further embodiment, one or more PRU resource sets may comprise multiple PRUs associated with preamble groups configured for RO, where the preamble determined by the UE is associated with at least one PRU group in different PRU resource sets. For example, referring to Figure 6, one preamble group 606 for RO 604 may be associated with multiple PRU resource sets, where the preamble determined from the preamble group is mapped to multiple PRUs in different PRU resource sets. For example, one preamble 602a in preamble group 606 may be mapped to PRU group 612c of the first PRU resource set 608 and PRU group 612d of the second PRU resource set 610, or to PRU group 612 and any combination of PRU group 612 and PRU resource sets 608, 610.

[0085] In other embodiments, a preamble group may comprise a first set of preambles and a second set of preambles, where each preamble in the first set of preambles is associated with a group of PRUs in one or more of a plurality of PRU resource sets, and at least one preamble in the second set of preambles is associated with a single PRU in one of the plurality of PRU resource sets. For example, referring to Figure 7, the preamble may be determined from a preamble group 706 configured for RO 704, which includes a first set of preambles 708 and a second set of preambles 710, where each preamble in the first set of preambles 708 supports a one-to-many mapping configuration, and each preamble in the second set of preambles 710 supports either a one-to-one mapping configuration or a many-to-one mapping configuration. For example, in the example shown in Figure 7, preamble 2 702a may be in the first set of preambles and may be associated with PRU groups 712a and 712b (one-to-many mapping), while preamble 3 702b may be in the second set of preambles and may be associated with PRU group 712c (one-to-one mapping). Similarly, preamble 4 702c and preamble 5 702d may be in the second set of preambles and may be associated with PRU group 712d (many-to-one mapping). Other combinations of mappings from preambles to PRU mappings are possible.

[0086] According to aspects of this disclosure relating to the piggyback of a UCI, a random access message may comprise a UCI transmitted using a first group of PRUs in a first PRU resource set, the UCI allocating a second group of PRUs in a second PRU resource set for the payload of the random access message. The UCI may comprise at least one of the following: MCS, TBS, waveform, resource allocation information for the payload, frequency hopping pattern for the payload, or multi-slot repetition information for the payload. For example, referring to Figure 8, msgA may comprise a piggybacked UCI 804 containing information for constructing a payload 802. The UCI 804 may comprise the MCS, transport block size (TBS), waveform, resource allocation information for the payload 802, and frequency hopping pattern and / or multi-slot repetition information for the payload 802. In one example, the determined preamble may be mapped to PRU group 812c in the first PRU resource set 808, where PRU group 812c carries UCI 804, which provides configuration information for payload 802. UCI 804 may then be allocated PRU group 812b in the second PRU resource set 810 to carry payload 802 of msgA.

[0087] In another aspect of this disclosure relating to push hopping, a random access message is transmitted according to a frequency hopping pattern using a first PRU resource set and a second PRU resource set. The random access message may be transmitted using a first PRU group in the first PRU resource set at a first frequency of the frequency hopping pattern, and using a second PRU group in the second PRU resource set at a second frequency of the frequency hopping pattern. For example, referring to Figure 9, msgA may include a payload 902 that is transmitted according to a hopping pattern on multiple PRU resource sets 908, 910. In one example, a preamble to be determined may be mapped to a PRU group 912a in the first PRU resource set 908 for carrying the payload 904a of msgA at a first frequency. Furthermore, based on either a dynamic or static frequency offset, PRU group 912a in the first PRU resource set 908 may be mapped to another PRU group 912d in the second PRU resource set 910 for carrying the payload 904b of msgA at a second frequency. The frequency hopping pattern may be obtained in random access configuration information, determined by the UE, and / or included in the UCI.

[0088] In a further aspect of the present disclosure relating to multi-slot iteration, a random access message may be transmitted according to a multi-slot iteration pattern spanning a first PRU resource set and a second PRU resource set, where the first transmission of the random access message uses a first PRU group in the first PRU resource set, and the second transmission of the random access message uses a second PRU group in the second PRU resource set. For example, referring to Figure 10, msgA may include a payload 1002a, which is transmitted in multiple slots 1004a, 1004b on multiple PRU resource sets 1008, 1010. In one example, a preamble to be determined may be mapped to a PRU group 1012a in the first PRU resource set 1008 for carrying the payload 1002a of msgA in the first set of slots 1004a. Furthermore, based on the dynamic or static determination of this number of slots, PRU group 1012a in the first PRU resource set 1008 may be mapped to another PRU group 1012b in the second PRU resource set 1010 for iterating the payload 1002b of msgA in the second set 1004b of slots. Slot iteration information may be obtained in random access configuration information, or determined by the UE, and / or included in the UCI.

[0089] In additional aspects of this disclosure relating to piggyback and / or push hopping and / or multi-slot iterations of UCI, the UCI may be transmitted in a first PRU group of a first PRU resource set, the UCI may allocate a second PRU group in a second PRU resource set for the payload, and the payload may be transmitted in a second PRU group of the second PRU resource set. For example, referring to Figure 11, msgA may include a piggybacked UCI 1104 containing information for configuring payload 1102. In one example, the determined preamble may be mapped to PRU group 1112c in a first PRU resource set 1108, where PRU group 1112c carries the UCI 1104 providing configuration information for payload 1102. The UCI 1104 may allocate PRU group 1112b in a second PRU resource set 1110 to carry payload 1102 of msgA.

[0090] Furthermore, according to this embodiment, the payload may be transmitted using frequency hopping or slot repetition across a second and third PRU group in a second PRU resource set. In some embodiments, the payload may be transmitted in the second and third PRU group based on frequency hopping information in the UCI, which includes either intra-slot PRB hopping information or inter-slot PRB hopping information. In other embodiments, the payload may be transmitted in the second and third PRU group based on multi-slot repetition information in the UCI, which spans one of multiple consecutive or non-consecutive slots in the time domain. For example, referring to Figure 11, each PRU in the second PRU group 1112b may carry or repeat the payload 1102a of msgA in a first set of first frequencies or slots. Furthermore, based on frequency hopping information or slot repetition information in UCI1104, a second PRU group 1112b in a second PRU resource set 1110 may be mapped to a third PRU group 1112d in a second PRU resource set 1110 for carrying or repeating payload 1102b of msgA in a second set of second frequencies or slots. The hopping pattern may be intra-slot (e.g., payload transmission may hop frequencies after a number of symbols in a slot of a physical resource block (PRB)) or inter-slot (e.g., payload transmission may hop frequencies after a number of slots of one or more PRBs). Multiple slot repetitions of payloads 1002a, 1002b may span consecutive or non-consecutive slots of one or more PRBs in the time domain.

[0091] Finally, in 1208, the UE sends a random access message to the base station, which includes a preamble and a payload, the payload being sent using one or more PRU groups of one or more PRU resource sets based on mapping. For example, 1210 may be performed by the random access message component 1314 in Figure 13. Referring, for example, to Figures 4 and 5, the UE may also send a preamble 410 to the base station, followed by a payload 412, the payload 412 may include, for example, an RRC message (similar to message 3 in a four-step RACH process), user plane (UP) or control plane (CP) data, MAC CE (e.g., a buffer status report (BSR) or power headroom report (PHR)), and, in some embodiments, piggybacked uplink control information (UCI). When sending msgA, the UE sends the payload and DMRS on multiple PRUs or PRU groups mapped to a single sequence of transmitted preambles. Furthermore, referring to Figures 8, 9, 10, and 11, the UE can piggyback UCI804 into the payload in msgA, transmit payload 902 according to a hopping pattern in msgA, repeat payloads 1002a and 1002b in msgA using multiple slot iterations, or combine these steps based on a determined preamble of the UE and a one-to-many mapping configuration between multiple PRU groups 812, 912a-d, 1012, and 1112.

[0092] Figure 13 is a conceptual data flow diagram 1300 showing the data flow between different means / components in an exemplary device 1302. The device could be a UE (e.g., UE104, 350, 402) or a component of a UE communicating with a base station 1350 (e.g., base stations 102 / 180, 310, 404). The device includes a receiving component 1304 that receives a downlink transmission from base station 1350 containing random access configuration information. The device includes a random access configuration component 1306 that receives random access configuration information from base station 1350 via the receiving component 1304, for example, as described with respect to step 1202 in Figure 12. The device includes a preamble component 1308 that determines a preamble for a random access message from a preamble group for ROs, for example, as described with respect to step 1204 in Figure 12. The device includes a mapping component 1310 that determines a mapping based on the random access configuration information. The device includes a PRU resource set component 1312 that determines one or more PRU resource sets for a random access message based on a preamble, as described, for example, with respect to step 1206 in Figure 12. The random access configuration information maps the preamble to one or more PRU resource sets. The device includes a random access message component 1314 that transmits a random access message, including the preamble and payload, to the base station 1350 via a transmit component 1316, as described, for example, with respect to step 1208 in Figure 12. The payload is transmitted using one or more PRU groups of one or more PRU resource sets, based on the mapping in the PRU resource set component 1312. The device includes a transmit component 1316 that transmits an uplink communication, including the random access message, from the random access message component 1314 to the base station 1350.

[0093] The device may include additional components that execute each of the algorithm blocks in the flowchart of Figure 12 described above. Thus, each block in the flowchart of Figure 12 described above may be executed by a component, and the device may include one or more of those components. A component may be one or more hardware components specifically configured to execute the described process / algorithm, implemented by a processor configured to execute the described process / algorithm, stored in a computer-readable storage medium for processor implementation, or any combination thereof.

[0094] Figure 14 is a diagram of Figure 1400 showing an example of a hardware implementation of a device 1302' utilizing the processing system 1414. The processing system 1414 can be implemented using a bus architecture schematically represented by bus 1424. Bus 1424 may include any number of interconnection buses and bridges, depending on the specific application and overall design constraints of the processing system 1414. Bus 1424 connects various circuits together, including one or more processors and / or hardware components represented by processor 1404, components 1304, 1306, 1308, 1310, 1312, 1314, 1316, and computer-readable storage medium / memory 1406. Bus 1424 may also connect various other circuits, such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further.

[0095] The processing system 1414 may be coupled to a transceiver 1410. The transceiver 1410 is coupled to one or more antennas 1420. The transceiver 1410 provides means for communicating with various other devices via a transmitting medium. The transceiver 1410 receives signals from one or more antennas 1420, extracts information from the received signals, and provides the extracted information to the processing system 1414, in particular to the receiving component 1304. In addition, the transceiver 1410 receives information from the processing system 1414, in particular to the transmitting component 1316, and generates signals to be applied to one or more antennas 1420 based on the received information. The processing system 1414 includes a processor 1404 coupled to a computer-readable storage medium / memory 1406. The processor 1404 is responsible for general processing, including the execution of software stored in the computer-readable storage medium / memory 1406. When the software is executed by processor 1404, it causes the processing system 1414 to perform various functions described above for any particular device. Computer-readable storage medium / memory 1406 may also be used to store data manipulated by processor 1404 when the software is executed. Processing system 1414 further includes at least one of components 1304, 1306, 1308, 1310, 1312, 1314, and 1316. These components may be software components that operate within processor 1404 and reside / stored in computer-readable storage medium / memory 1406, one or more hardware components coupled to processor 1404, or any combination thereof. Processing system 1414 may also be a component of UE350 and may include memory 360, and / or at least one of TX processor 368, RX processor 356, and controller / processor 359. Alternatively, processing system 1414 may be the entire UE (see, for example, 350 in Figure 3).

[0096] In one configuration, the device 1302 / 1302' for wireless communication includes means for receiving random access configuration information from a base station; means for determining a preamble for a random access message from a preamble group for a random access opportunity (RO); means for determining one or more physical uplink shared channel resource unit (PRU) resource sets for a random access message based on the preamble and a mapping based on the random access configuration information, wherein the random access configuration information maps the preamble to one or more PRU resource sets; and means for transmitting a random access message to the base station, comprising the preamble and a payload, wherein the payload is transmitted using one or more PRU groups of one or more PRU resource sets based on the mapping.

[0097] The means described above may be one or more of the components of the device 1302 and / or the processing system 1414 of the device 1302', configured to perform the functions enumerated by the means described above. As described above, the processing system 1414 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Thus, in one configuration, the means described above may be the TX processor 368, the RX processor 356, and the controller / processor 359, configured to perform the functions enumerated by the means described above.

[0098] Figure 15 is a flowchart 1500 of a wireless communication method. The method may be performed by base stations 102 / 180, 310, 404 (for example, base station 310, equipment 1602 / 1602', processing system 1714, which may include memory 376, may be the entire base station 310, or may be components of base station 310 such as TX processor 316, RX processor 370, and / or controller / processor 375). The method allows a base station to receive msgA transmissions in a two-step RACH process based on a one-to-many mapping configuration between preambles and PRUs, and the preamble selected by the UE may be mapped to one or more groups of PRUs to support UCI piggyback, PUSCH hopping, and multi-slot iteration.

[0099] In step 1502, the base station transmits random access configuration information to the UE, which is transmitted using at least one of system information or RRC signaling. For example, step 1502 may be performed by the random access configuration information component 1608 in Figure 16. For example, referring to Figure 4, the base station may transmit random access configuration information 406 to the UE before the start of the two-step RACH process. For example, the base station may broadcast SSB, SIB, and / or reference signals for the UE to process these signals and channels and determine the configuration for the two-step RACH.

[0100] Random access configuration information includes mapping preambles to one or more PRU resource sets (e.g., PRU groups of a PRU resource set). Association rules may include one-to-many mapping (e.g., one preamble is associated with multiple PRU groups), one-to-one mapping (e.g., one preamble is associated with one PRU group), or many-to-one mapping (e.g., multiple preambles are associated with the same PRU group). For example, referring to Figure 7, the random access configuration may indicate that preambles in preamble group 706 support one-to-many, one-to-one, or many-to-one mapping configurations. More specifically, the random access configuration may indicate that some preambles may be associated with multiple PRU groups in the same or different PRU resource sets, while other preambles may be associated with only one PRU group individually or with multiple PRU groups. Therefore, in one example, if one preamble group 706 configured for RO contains 64 preambles of different preamble sequences, the random access configuration information may show that preamble 2 702a is associated with PRU groups 712a and 712b (one-to-many association rule), preamble 3 702b is associated with PRU group 712c (one-to-one association rule), and preamble 4 702c and preamble 5 702d are associated with PRU group 712d (many-to-one association rule).

[0101] Finally, in 1504, the base station receives a random access message from the UE, which includes a preamble on the RO, and the preamble is from a preamble group. For example, 1504 may be performed by the random access component 1606 in Figure 16. Referring to Figure 4, for example, the base station may receive msgA from the UE, which includes a preamble 410 followed by a payload 412. Furthermore, referring to Figure 6, the preamble received by the base station may be determined based on random access configuration information from a preamble group 606, which may include multiple preambles 602 having different preamble sequences that can be received on the same RO 604. In one example, the preamble group 606 may include 64 preamble sequences, and the base station may receive a preamble 602 determined from these sequences on the time and frequency resources associated with the RO 604.

[0102] A preamble is associated with one or more PRU resource sets for random access messages based on a mapping. One or more PRU resource sets may comprise a first PRU resource set and a second PRU resource set. For example, referring to Figure 6, preamble 602 in preamble group 606 for RO604 may be associated with a first PRU resource set 608 and a second PRU resource set 610, each PRU resource set containing one or more groups of PRUs (PRU group 612) for sending the payload in msgA.

[0103] In one embodiment, one or more PRU resource sets may comprise multiple PRU resource sets associated with a preamble, where the resource sets are orthogonal in at least one of the time domain, frequency domain, or code domain. For example, referring to Figure 6, one preamble group 606 for RO604 may be associated with multiple PRU resource sets. More specifically, some preambles within a preamble group may be associated with one PRU resource set, while other preambles within the preamble group may be associated with another PRU resource set. PRU resource sets can be orthogonal in the time domain, frequency domain, or code domain. For example, Figure 6 shows a first PRU resource set 608 and a second PRU resource set 610 that are orthogonal to each other in the time domain 614, but PRU resource sets can also be orthogonal in the frequency domain 616 or the code domain.

[0104] In another embodiment, one or more PRU resource sets may comprise multiple PRUs associated with a preamble, and the preamble may be associated with multiple PRU groups within a single PRU resource set. For example, referring to Figure 6, one preamble group 606 for RO604 may be associated with multiple PRU resource sets, and the preamble determined from the preamble group may be mapped to multiple PRUs within the same PRU resource set. For example, one preamble 602a in preamble group 606 may be mapped to PRU groups 612a and 612c of a first PRU resource set 608, or to PRU groups 612b and 612d of a second PRU resource set 610.

[0105] In a further embodiment, one or more PRU resource sets may comprise multiple PRUs associated with a preamble, and the preamble is associated with at least one group of PRUs in different PRU resource sets. For example, referring to Figure 6, one preamble group 606 for RO604 may be associated with multiple PRU resource sets, and the preamble determined from the preamble group may be mapped to multiple PRUs in different PRU resource sets. For example, one preamble 602a in preamble group 606 may be mapped to PRU group 612c of the first PRU resource set 608 and PRU group 612d of the second PRU resource set 610, or to PRU group 612 and any combination of PRU group 612 and PRU resource sets 608, 610.

[0106] According to aspects of this disclosure relating to UCI piggyback, a random access message may comprise a UCI received using a first PRU group in a first PRU resource set, the UCI allocating a second PRU group in a second PRU resource set for the payload of the random access message. For example, referring to Figure 8, the received msgA may comprise a piggybacked UCI 804 containing information for configuring payload 802. The UCI 804 may comprise the MCS, transport block size (TBS), waveform, resource allocation information for payload 802, and frequency hopping pattern and / or multi-slot repeat information for payload 802. In one example, the preamble may be mapped to PRU group 812c in a first PRU resource set 808, the PRU group 812c carrying the UCI 804 providing configuration information for payload 802. UCI804 may allocate PRU group 812b of the second PRU resource set 810 to carry payload 802 of msgA.

[0107] In another aspect of this disclosure relating to push hopping, a random access message may be received according to a frequency hopping pattern using a first PRU resource set and a second PRU resource set. The random access message may be received using a first PRU group in the first PRU resource set at a first frequency of the frequency hopping pattern, and using a second PRU group in the second PRU resource set at a second frequency of the frequency hopping pattern. The payload may be received using frequency hopping in the first PRU group and the second PRU group. For example, referring to Figure 9, the received msgA may include a payload 902, which is received according to a hopping pattern on multiple PRU resource sets 908, 910. In one example, a preamble may be mapped to a first PRU group 912a in the first PRU resource set 908 for carrying the payload 904a of msgA at a first frequency. Furthermore, based on either a dynamic or static frequency offset, a first PRU group 912a in the first PRU resource set 908 may be mapped to a second PRU group 912d in the second PRU resource set 910 for carrying the payload 904b of msgA at a second frequency.

[0108] In a further aspect of the present disclosure relating to multiple slot iterations, a random access message may be received according to a multiple slot iteration pattern spanning a first PRU resource set and a second PRU resource set, and the random access message is received using a first PRU group in the first PRU resource set in the first slot of the multiple slot iteration pattern, and using a second PRU group in the second PRU resource set in the second slot of the multiple slot iteration pattern. The payload may be received using slot iterations in the first PRU group and the second PRU group. For example, referring to Figure 10, the received msgA may include a payload 1002a, which is received in multiple slots 1004a, 1004b on multiple PRU resource sets 1008, 1010. In one example, a preamble may be mapped to a first PRU group 1012a in the first PRU resource set 1008 for carrying the payload 1002a of msgA in the first set of slots 1004a. Furthermore, based on the dynamic or static determination of this number of slots, PRU group 1012a in the first PRU resource set 1008 may be mapped to a second PRU group 1012b in the second PRU resource set 1010 for iterating the payload 1002b of msgA in a second set 1004b of slots.

[0109] In additional embodiments of this disclosure relating to combinations of UCI piggyback and PUSCH hopping and / or multi-slot iteration, the UCI may be received in a first PRU group of a first PRU resource set, the UCI may allocate a second PRU group in a second PRU resource set for the payload, and the payload may be received in a second PRU group of the second PRU resource set. For example, referring to Figure 11, the received msgA may include a piggybacked UCI 1104 containing information constituting the payload 1102. In one example, the preamble may be mapped to PRU group 1112c in a first PRU resource set 1108, where PRU group 1112c carries the UCI 1104 providing configuration information for the payload 1102. The UCI 1104 may allocate PRU group 1112b in a second PRU resource set 1110 to carry the payload 1102 of msgA.

[0110] In some embodiments, the payload may frequency hop across a second and third PRU group in a second PRU resource set. In other embodiments, the payload may be repeated across a second and third PRU group in a second PRU resource set. For example, referring to Figure 11, each PRU in the second PRU group 1112b may carry or repeat the payload 1102a of msgA in a first set of first frequencies or slots. Furthermore, based on frequency hopping information or slot repeat information in UCI 1104, the second PRU group 1112b in the second PRU resource set 1110 may be mapped to the third PRU group 1112d in the second PRU resource set 1110 for carrying or repeating the payload 1102b of msgA in a second set of second frequencies or slots.

[0111] A random access message may contain a payload received on one or more PRU groups of one or more PRU resource sets based on a mapping. For example, referring to Figures 4 and 5, a base station may receive a payload 412 in msgA following a preamble 410, and the payload 412 may include, for example, an RRC message (similar to message 3 in a four-step RACH process), user plane (UP) or control plane (CP) data, MAC CE (e.g., a buffer status report (BSR) or power headroom report (PHR)), and, in some embodiments, piggybacked uplink control information (UCI). Upon receiving msgA, the base station may receive the payload and DMRS on multiple PRUs or PRU groups mapped to a single sequence of transmitted preambles. Furthermore, referring to Figures 8, 9, 10, and 11, the base station may receive the piggybacked UCI804 on the payload in msgA, receive payload 902 according to the hopping pattern in msgA, receive the repeated payloads 1002a and 1002b in msgA using multiple slot iterations, or receive combinations based on a determined preamble and a one-to-many mapping configuration between multiple PRU groups 812, 912a-d, 1012, and 1112.

[0112] Figure 16 is a conceptual data flow diagram 1600 showing the data flow between different means / components in an exemplary device 1602. The device may be a base station (e.g., base stations 102 / 180, 310, 404) or a component of a base station communicating with a UE 1650 (e.g., UE 104, 350, 402). The device includes a receiving component 1604 that receives uplink communications from the UE containing random access messages to the random access component 1606 of the device 1602. The device includes a random access configuration information component 1608 that transmits random access configuration information to the UE 1650 via the transmitting component 1610 of the device 1602, as described, for example, with respect to step 1502 in Figure 15. The random access configuration information is transmitted from the random access configuration information component 1608 using at least one of system information or RRC signaling, and the random access configuration information includes mapping of preambles to one or more PRU resource sets, as described, for example, further with respect to step 1502 in Figure 15. The device includes a transmitting component 1610 that transmits downlink communication containing random access configuration information to the UE 1650. Subsequently, the random access component 1606 of the device 1602 receives a random access message containing a preamble from the UE via the receiving component 1604, for example, as described with respect to step 1504 in Figure 15. The preamble is from a preamble group and may be associated with one or more PRU resource sets for the random access message based on a mapping, for example, as further described with respect to step 1504 in Figure 15. The random access message contains a payload received by the random access component 1606 in one or more PRU groups of one or more PRU resource sets based on the mapping.

[0113] The device may include additional components that execute each of the blocks of the algorithm in the flowchart of Figure 15 described above. Thus, each block in the flowchart of Figure 15 described above may be executed by a component, and the device may include one or more of those components. A component may be one or more hardware components specifically configured to execute the described process / algorithm, implemented by a processor configured to execute the described process / algorithm, stored in a computer-readable storage medium for processor implementation, or any combination thereof.

[0114] Figure 17 is a diagram of Figure 1700 showing an example of a hardware implementation of a device 1602' utilizing the processing system 1714. The processing system 1714 may be implemented using a bus architecture schematically represented by bus 1724. Bus 1724 may include any number of interconnecting buses and bridges, depending on the specific application and overall design constraints of the processing system 1714. Bus 1724 connects various circuits together, including one or more processors and / or hardware components represented by processor 1704, components 1604, 1606, 1608, 1610, and computer-readable storage medium / memory 1706. Bus 1724 may also connect various other circuits, such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further.

[0115] The processing system 1714 may be coupled to a transceiver 1710. The transceiver 1710 is coupled to one or more antennas 1720. The transceiver 1710 provides means for communicating with various other devices via a transmitting medium. The transceiver 1710 receives signals from one or more antennas 1720, extracts information from the received signals, and provides the extracted information to the processing system 1714, in particular to the receiving component 1604. In addition, the transceiver 1710 receives information from the processing system 1714, in particular from the transmitting component 1610, and generates signals to be applied to one or more antennas 1720 based on the received information. The processing system 1714 includes a processor 1704 coupled to a computer-readable storage medium / memory 1706. The processor 1704 is responsible for general processing, including the execution of software stored in the computer-readable storage medium / memory 1706. When the software is executed by the processor 1704, it causes the processing system 1714 to perform the various functions described above for any particular device. The computer-readable storage medium / memory 1706 may also be used to store data manipulated by the processor 1704 when the software is executed. The processing system 1714 further includes at least one of the components 1604, 1606, 1608, and 1610. These components may be software components that operate within the processor 1704 and reside / stored in the computer-readable storage medium / memory 1706, one or more hardware components coupled to the processor 1704, or any combination thereof. The processing system 1714 may also be a component of the base station 310 and may include memory 376, and / or at least one of the TX processor 316, RX processor 370, and controller / processor 375. Alternatively, the processing system 1714 may be the entire base station (see, for example, 310 in Figure 3).

[0116] In one configuration, the device 1602 / 1602' for wireless communication includes means for transmitting random access configuration information to a user device (UE), the random access configuration information being transmitted using at least one of system information or radio resource control (RRC) signaling, and the random access configuration information including a mapping of preambles to one or more PRU resource sets. The device 1602 / 1602' also includes means for receiving a random access message from the UE on a random access opportunity (RO), the preamble being from a preamble group, and the random access message including a payload received in one or more PRU groups of one or more PRU resource sets based on the mapping.

[0117] The means described above may be one or more of the components of the device 1602 and / or the processing system 1714 of the device 1602', configured to perform the functions enumerated by the means described above. As described above, the processing system 1714 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Thus, in one configuration, the means described above may be the TX processor 316, the RX processor 370, and the controller / processor 375, configured to perform the functions enumerated by the means described above.

[0118] Accordingly, this disclosure supports a variety of payloads for msgA transmission in a two-step RACH procedure by providing a one-to-many mapping configuration between the preamble and PRU to enable a configurable MCS and configurable resource size in the time-frequency domain. The preamble determined by the UE may be mapped to one or more groups of PRUs to support UCI piggybacking, frequency hopping on the PUSCH, and multiple slot repetitions for msgA transmission. By piggybacking the UCI into the payload in msgA, this disclosure can provide flexibility in MCS and waveform selection, as well as resource allocation for DMRS and PUSCH in the PRUs. Furthermore, by allowing the payload to hop to different frequencies on the PUSCH during msgA transmission, improved frequency diversity and interference averaging can be achieved. In addition, by allowing the payload to repeat across multiple slots in msgA transmission, coverage can be enhanced and / or reliability can be increased.

[0119] The following examples are illustrative and may be combined with other embodiments or teachings described herein without limitation.

[0120] Example 1 is a method for wireless communication in a UE, the method comprising: receiving random access configuration information from a base station; determining a preamble for a random access message from a group of preambles for random access opportunities (ROs); determining one or more physical uplink shared channel resource unit (PRU) resource sets for a random access message based on the preamble and a mapping based on the random access configuration information, wherein the random access configuration information maps the preamble to one or more PRU resource sets; and transmitting a random access message to the base station, the payload being transmitted using one or more PRU groups of one or more PRU resource sets based on the mapping.

[0121] In Example 2, the method of Example 1 further includes one or more PRU resource sets comprising a first PRU resource set and a second PRU resource set.

[0122] In Example 3, the method of Example 1 or 2 further includes the random access message comprising uplink control information (UCI) transmitted using a first group of PRUs in a first PRU resource set, and the UCI allocating a second group of PRUs in a second PRU resource set for the payload of the random access message.

[0123] In Example 4, any of the methods in Examples 1 to 3 further includes the UCI including at least one of the following: Modulation Control Scheme (MCS), Transport Block Size (TBS), waveform, Resource Allocation Information for the Payload, Frequency Hopping Pattern for the Payload, or Multiple Slot Repetition Information for the Payload.

[0124] In Example 5, any of the methods in Examples 1 to 4 further includes the transmission of a random access message using a first PRU resource set and a second PRU resource set according to a frequency hopping pattern, wherein the random access message is transmitted using a first group of PRUs in the first PRU resource set at a first frequency of the frequency hopping pattern, and using a second group of PRUs in the second PRU resource set at a second frequency of the frequency hopping pattern.

[0125] In Example 6, any of the methods in Examples 1 to 5 further includes each PRU group of one or more PRU groups comprising a time-frequency resource associated with a physical uplink shared channel (PUSCH) transmission and an antenna port and sequence scrambling identification information associated with a demodulated reference signal (DMRS) transmission.

[0126] In Example 7, any of the methods in Examples 1 to 6 further comprises one or more PRU resource sets comprising multiple PRU resource sets associated with a preamble group configured for the RO, wherein the multiple PRU resource sets are orthogonal in at least one of the time domain, frequency domain, or code domain.

[0127] In Example 8, any of the methods in Examples 1 to 7 further comprises one or more PRU resource sets comprising multiple PRUs associated with a preamble group configured for the RO, where the preamble determined by the UE is associated with multiple PRU groups within a single PRU resource set.

[0128] In Example 9, any of the methods in Examples 1 to 8 further comprises one or more PRU resource sets comprising multiple PRUs associated with a preamble group configured for the RO, wherein the preamble determined by the UE is associated with at least one PRU group from different PRU resource sets.

[0129] In Example 10, any of the methods in Examples 1 to 9 further comprises a preamble group comprising a first set of preambles and a second set of preambles, where each preamble in the first set of preambles is associated with multiple PRU groups in one or more PRU resource sets, and at least one preamble in the second set of preambles is associated with a single PRU group in one of the one or more PRU resource sets.

[0130] In Example 11, any of the methods in Examples 1 to 10 further comprises one or more PRU resource sets comprising a first PRU resource set and a second PRU resource set, wherein a random access message is transmitted according to a multi-slot repeating pattern spanning the first PRU resource set and the second PRU resource set, the first transmission of a random access message using a first PRU group in the first PRU resource set, and the second transmission of a random access message using a second PRU group in the second PRU resource set.

[0131] In Example 12, any method of Examples 1 to 11 further comprises one or more PRU resource sets comprising a first PRU resource set and a second PRU resource set, wherein uplink control information (UCI) is transmitted in a first PRU group of the first PRU resource set, the UCI allocates a second PRU group in the second PRU resource set for the payload, the payload is transmitted in a second PRU group of the second PRU resource set, and the payload is transmitted using frequency hopping or slot iterations spanning a second PRU group and a third PRU group in the second PRU resource set.

[0132] In Example 13, any of the methods in Examples 1 to 12 further transmits the payload in a second PRU group and a third PRU group based on frequency hopping information in the UCI, where the UCI includes either intra-slot physical resource block (PRB) hopping information or inter-slot physical resource (PRB) hopping information.

[0133] In Example 14, any of the methods in Examples 1 to 13 further includes the transmission of the payload in a second PRU group and a third PRU group based on multi-slot iteration information in the UCI, wherein the payload spans one of multiple consecutive or non-consecutive slots in the time domain.

[0134] Example 15 is a device comprising one or more processors and one or more memories that store instructions and communicate electronically with the one or more processors, wherein the instructions are executable by one or more processors to cause a system or device to perform any of the methods in Examples 1 to 14.

[0135] Example 16 is a system or apparatus that includes means for implementing any of the methods in Examples 1 to 14 or for realizing the apparatus.

[0136] Example 17 is a non-temporary computer-readable storage medium for storing instructions, which are executable by one or more processors such that one or more processors perform any of the methods in Examples 1 to 14.

[0137] Figure 18 shows a method of wireless communication at a base station, the method comprising the steps of: transmitting random access configuration information to a user device (UE), wherein the random access configuration information is transmitted using at least one of system information or radio resource control (RRC) signaling, and the random access configuration information includes mapping a preamble to one or more physical uplink shared channel resource unit (PRU) resource sets; and receiving a random access message from the UE on a random access opportunity (RO), wherein the preamble is from a preamble group, and the random access message includes a payload that is received in one or more PRU groups of one or more PRU resource sets based on the mapping.

[0138] In Example 19, the method of Example 18 further includes one or more PRU resource sets comprising a first PRU resource set and a second PRU resource set.

[0139] In Example 20, the method of Example 18 or 19 further includes the random access message comprising uplink control information (UCI) received using a first group of PRUs in a first PRU resource set, and the UCI allocating a second group of PRUs in a second PRU resource set for the payload of the random access message.

[0140] In Example 21, any of the methods in Examples 18 to 20 further comprises the random access message being received according to a frequency hopping pattern using a first PRU resource set and a second PRU resource set, the random access message being received using a first group of PRUs in the first PRU resource set at a first frequency of the frequency hopping pattern, and a second group of PRUs in the second PRU resource set at a second frequency of the frequency hopping pattern.

[0141] In Example 22, any of the methods in Examples 18 to 21 further includes the payload being received using frequency hopping in a first PRU group and a second PRU group.

[0142] In Example 23, any method of Examples 18 to 22 further comprises having multiple PRU resource sets, one or more PRU resource sets associated with a preamble, wherein the multiple PRU resource sets are orthogonal in at least one of the time domain, frequency domain, or code domain.

[0143] In Example 24, any of the methods in Examples 18 to 23 further comprises one or more PRU resource sets having multiple PRU resource sets associated with a preamble, the preamble being associated with multiple PRU groups within a single PRU resource set.

[0144] In Example 25, any of the methods in Examples 18 to 24 further comprises one or more PRU resource sets comprising multiple PRU resource sets associated with a preamble, the preamble being associated with at least one group of PRUs from different PRU resource sets.

[0145] In Example 26, any method of Examples 18 to 25 further comprises one or more PRU resource sets comprising a first PRU resource set and a second PRU resource set, wherein random access messages are received according to a multi-slot repeating pattern spanning the first PRU resource set and the second PRU resource set, and the random access messages are received using a first PRU group in the first PRU resource set in the first slot of the multi-slot repeating pattern and using a second PRU group in the second PRU resource set in the second slot of the multi-slot repeating pattern.

[0146] In Example 27, any of the methods in Examples 18 to 26 further includes the payload being received using slot iterations in a first PRU group and a second PRU group.

[0147] In Example 28, any method of Examples 18 to 27 further comprises one or more PRU resource sets comprising a first PRU resource set and a second PRU resource set, wherein uplink control information (UCI) is received in a first PRU group of the first PRU resource set, the UCI allocates a second PRU group in the second PRU resource set for the payload, the payload is received in a second PRU group of the second PRU resource set, and the payload is frequency-hopped across a second PRU group and a third PRU group in the second PRU resource set.

[0148] In Example 29, any method of Examples 18 to 28 further comprises one or more PRU resource sets comprising a first PRU resource set and a second PRU resource set, wherein uplink control information (UCI) is received in a first PRU group of the first PRU resource set, the UCI allocates a second PRU group in the second PRU resource set for the payload, the payload is received in a second PRU group of the second PRU resource set, and the payload is iterated over a second PRU group and a third PRU group in the second PRU resource set.

[0149] Example 30 is a device comprising one or more processors and one or more memories that store instructions and communicate electronically with the one or more processors, wherein the instructions are executable by one or more processors to cause a system or device to perform any of the methods in Examples 18 to 29.

[0150] Example 31 is a system or apparatus that includes means for implementing any of the methods in Examples 18-29 or for realizing the apparatus.

[0151] Example 32 is a non-temporary computer-readable storage medium for storing instructions, the instructions being executable by one or more processors such that one or more processors perform any of the methods in Examples 18-29.

[0152] It should be understood that the specific order or hierarchy of blocks in the disclosed process / flowchart is illustrative of the method. It should also be understood that the specific order or hierarchy of blocks in the process / flowchart may be rearranged based on design preferences. Furthermore, some blocks may be combined or omitted. The attached method claims present various block elements in an illustrative order and are not limited to the specific order or hierarchy presented.

[0153] The foregoing descriptions are provided to enable any person skilled in the art to practice the various embodiments described herein. Various modifications to these embodiments will be readily apparent to a person skilled in the art, and the general principles defined herein may apply to other embodiments. Accordingly, the claims should not be limited to the embodiments shown herein, but should be given the maximum scope that is not inconsistent with the claim language, and references to singular elements mean "one or more" and not "unique" unless otherwise specified. The term "exemplary" is used herein to mean "to serve as an example, case, or illustration." Any embodiment described herein as "exemplary" should not necessarily be construed as being preferable or advantageous to other embodiments. Unless otherwise specified, the term "several" 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 multiple A's, multiple B's, or multiple C's. 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 A only, B only, C only, A and B, A and C, B and C, or A and B and C, and any such combination may include one or more members of A, B, or C. All structural and functional equivalents of elements of various aspects described throughout this disclosure, whether known to those skilled in the art or to be known thereafter, are expressly incorporated herein by reference and intended to be encompassed by the claims. Furthermore, nothing disclosed herein is made public, whether such disclosure is expressly enumerated in the claims or not.Words such as "module," "mechanism," "element," and "device" are not always substitutes for the word "means." Therefore, no claim element should be interpreted as means plus function unless it is explicitly described using the phrase "means for." [Explanation of symbols]

[0154] 102 Base station 104 UE 110 Geographic Coverage Areas 120 Communication Links 132 First backhaul link 134 Third backhaul link 150 Wi-Fi access points 152 Wi-Fi stations 154 Communication Links 158 Inter-device communication links 160 EPC 162 MME 164 Other MMEs 166 Serving Gateways 168 MBMS GW 170 BM-SC 172 PDN Gateway 174 HSS 176 IP Services 180 gNB 182 Beamforming 184 Second backhaul link 190 Core Network 192 AMF 193 Other AMF 194 SMF 195 UPF 196 UDM 197 IP Services 198 RACH UE Components 199 RACH base station components 310 base station 316 TX processors 318RX Receiver 318TX Transmitter 320 Antenna 350 UE 352 Antenna 354RX Receiver 354TX Transmitter 356 RX processors 358-channel estimator 359 Controllers / Processors 360 memory 368 TX processors 370 RX processor 374 channel estimator 375 Controllers / Processors 376 memory 510 Linear Modulation 512 Conversion Precoding 514 IFFT 516 MUX 518 DMRS 520 Preamble Sequence ID 522 PRACH Preamble 602 Preamble 604 Random access opportunity 606 Preamble Group 608 First PRU resource set 610 Second PRU resource set 612 PRU Group 702 Preamble 704 Random access opportunity 706 Preamble Group 708 Preamble 710 Preamble 712 PRU Group 802 Payload 804 UCI 806 Preamble Group 808 First PRU resource set 810 Second PRU resource set 812 PRU Group 902 Payload 904 Payload 906 Preamble Group 908 First PRU resource set 910 Second PRU resource set 912 PRU Group 1002 Payload 1006 Preamble Group 1008 First PRU resource set 1010 Second PRU resource set 1012 PRU Group 1102 Payload 1104 UCI 1106 Preamble Group 1108 First PRU resource set 1110 Second PRU resource set 1112 PRU Group 1302 Equipment 1304 Receiving Component 1306 Random Access Configuration Component 1308 Preamble Component 1310 Mapping Component 1312 PRU Resource Set Component 1314 Random Access Message Component 1316 Sending Component 1350 base station 1404 Processor 1406 Computer-readable storage medium / memory 1410 Transceiver 1414 Processing System 1420 Antenna 1424 Bus 1602 Equipment 1604 Receiving Component 1606 Random Access Component 1608 Random Access Configuration Information Component 1610 Sending Component 1650 UE 1704 Processor 1706 Computer-readable storage medium / memory 1710 Transceiver 1714 Processing System 1720 Antenna 1724 Bus

Claims

1. A method for wireless communication in user equipment (UE), The steps include receiving random access configuration information from the base station, The steps include determining a preamble for a random access message from a preamble group for random access opportunities (ROs), A step of determining a plurality of physical uplink shared channel resource unit (PRU) resource sets for the random access message based on the preamble and the mapping based on the random access configuration information, wherein the random access configuration information indicates a mapping between the preamble and the plurality of PRU resource sets. A step of transmitting the random access message to the base station, the random access message comprising the preamble for the UE and the payload for the UE, wherein the payload is transmitted using a first PRU group and a second PRU group of the plurality of PRU resource sets based on the mapping, the first PRU group at a first frequency is included in the plurality of PRU groups, and the second PRU group at a second frequency is included in the plurality of PRU groups. The process includes the step of mapping the first PRU group to the second PRU group based on the frequency hopping pattern indicated by the random access configuration information, The plurality of PRU resource sets are associated with the preamble group configured for the RO, The aforementioned multiple PRU resource sets are orthogonal in at least the time domain. method.

2. The plurality of PRU resource sets include a first PRU resource set and a second PRU resource set, The random access message is transmitted using the first PRU resource set and the second PRU resource set according to a frequency hopping pattern, and the random access message is transmitted using the first PRU group in the first PRU resource set at the first frequency of the frequency hopping pattern, and using the second PRU group in the second PRU resource set at the second frequency of the frequency hopping pattern. The method according to claim 1.

3. Each of the plurality of PRU groups includes a time-frequency resource associated with physical uplink shared channel (PUSCH) transmission and an antenna port and sequence scrambling identification information associated with demodulated reference signal (DMRS) transmission. The method according to claim 1.

4. The plurality of PRU resource sets are orthogonal in at least one of the frequency domain or the code domain. The method according to claim 1.

5. The preamble determined by the UE is associated with at least one group of PRUs in different PRU resource sets. The method according to claim 1.

6. The method according to claim 1, wherein the plurality of PRU resource sets include a first PRU resource set and a second PRU resource set, the random access message is transmitted according to a multi-slot repeat pattern spanning the first PRU resource set and the second PRU resource set, the first transmission of the random access message uses a first PRU group in the first PRU resource set, and the second transmission of the random access message uses a second PRU group in the second PRU resource set.

7. A device for wireless communication, A means for receiving random access configuration information from a base station, Means for determining a preamble for a random access message from a group of preambles for a random access opportunity (RO), wherein the means for determining the preamble is further configured to determine a plurality of physical uplink shared channel resource unit (PRU) resource sets for the random access message based on the preamble and a mapping based on random access configuration information, wherein the random access configuration information indicates a mapping between the preamble and the plurality of PRU resource sets. Means for transmitting the random access message to the base station, the random access message including the preamble for the device and the payload for the device, wherein the means for transmitting is further configured to transmit the payload using a first PRU group and a second PRU group of the plurality of PRU resource sets based on the mapping, the first PRU group at a first frequency is included in the plurality of PRU groups, and the second PRU group at a second frequency is included in the plurality of PRU groups, Means for mapping the first PRU group to the second PRU group based on the frequency hopping pattern indicated by the random access configuration information, Equipped with, The plurality of PRU resource sets are associated with the preamble group configured for the RO, The aforementioned multiple PRU resource sets are orthogonal in at least the time domain. Device.

8. The means for carrying out the method described in any one of claims 2 to 6 is further provided. The apparatus according to claim 7.

9. A computer-readable storage medium mounted in a device and storing computer-executable code, wherein when the code is executed by a processor, the processor... Receiving random access configuration information from the base station, Determining a preamble for a random access message from a preamble group for random access opportunities (RO), Determining a set of multiple physical uplink shared channel resource units (PRUs) for the random access message based on the preamble and the mapping based on the random access configuration information, wherein the random access configuration information indicates a mapping between the preamble and the set of multiple PRU resources, Transmitting the random access message to the base station, the random access message including the preamble for the device and the payload for the device, wherein the processor transmits the payload using a first PRU group and a second PRU group of the plurality of PRU resource sets based on the mapping, the first PRU group at a first frequency being included in the plurality of PRU groups, and the second PRU group at a second frequency being included in the plurality of PRU groups. The first PRU group is mapped to the second PRU group based on the frequency hopping pattern indicated by the random access configuration information. Have them do it, The plurality of PRU resource sets are associated with the preamble group configured for the RO, The aforementioned multiple PRU resource sets are orthogonal in at least the time domain. Computer-readable storage medium.

10. A method of wireless communication at a base station, A step of transmitting random access configuration information to a user device (UE), wherein the random access configuration information is transmitted using at least one of system information or radio resource control (RRC) signaling, and the random access configuration information indicates a mapping of a preamble to a set of multiple physical uplink shared channel resource units (PRUs). A step of receiving a random access message from the UE, which includes the preamble for the UE on a random access opportunity (RO), wherein the preamble is from a preamble group. It has, The PRU group at the first frequency is included in the PRU group and mapped to the second PRU group at the second frequency, based on the frequency hopping pattern indicated by the random access configuration information. The random access message includes a payload for the UE that is received in the first PRU group and the second PRU group based on the mapping. The aforementioned multiple PRU resource sets are configured for the RO, The aforementioned multiple PRU resource sets are orthogonal in at least the time domain. method.

11. The plurality of PRU resource sets include a first PRU resource set and a second PRU resource set, The random access message is received using the first PRU resource set and the second PRU resource set according to a frequency hopping pattern, and the random access message is received using the first PRU group in the first PRU resource set at the first frequency of the frequency hopping pattern, and using the second PRU group in the second PRU resource set at the second frequency of the frequency hopping pattern. The method according to claim 10, wherein the payload is received using frequency hopping in the first PRU group and the second PRU group.

12. The plurality of PRU resource sets are orthogonal in at least one of the frequency domain or code domain. The method according to claim 10.

13. The method according to claim 10, wherein the preamble is associated with at least one group of PRUs in different PRU resource sets.

14. A device for wireless communication, Means for transmitting random access configuration information to a user device (UE), wherein the random access configuration information is transmitted using at least one of system information or radio resource control (RRC) signaling, and the random access configuration information indicates a mapping of a preamble to a set of multiple physical uplink shared channel resource units (PRUs). Means for receiving a random access message from a UE on a random access opportunity (RO), the UE comprising the preamble, wherein the preamble is from a preamble group. Equipped with, The PRU group at the first frequency is included in the PRU group and mapped to the second PRU group at the second frequency, based on the frequency hopping pattern indicated by the random access configuration information. The random access message includes a payload for the UE that is received in the first PRU group and the second PRU group based on the mapping. The plurality of PRU resource sets are associated with the preamble group configured for the RO, The aforementioned multiple PRU resource sets are orthogonal in at least the time domain. Device.

15. The means for carrying out the method according to any one of claims 11 to 13 are further provided. The apparatus according to claim 14.

16. A computer-readable storage medium storing computer executable code, wherein when the code is executed by a processor, the processor... Transmitting random access configuration information to a user device (UE), wherein the random access configuration information is transmitted using at least one of system information or radio resource control (RRC) signaling, and the random access configuration information indicates a mapping of a preamble to a set of multiple physical uplink shared channel resource units (PRUs). Receiving a random access message from the UE on a random access opportunity (RO) that includes the preamble for the UE, wherein the preamble is from a preamble group. Have them do it, The PRU group at the first frequency is included in the PRU group and mapped to the second PRU group at the second frequency, based on the frequency hopping pattern indicated by the random access configuration information. The random access message includes a payload for the UE that is received in the first PRU group and the second PRU group based on the mapping. The plurality of PRU resource sets are associated with the preamble group configured for the RO, The aforementioned multiple PRU resource sets are orthogonal in at least the time domain. Computer-readable storage medium.

Images