Location based prach resource and beam identification for UL-only trp
By associating SSBs with PRACH resources in system information, the method addresses the challenge of determining UL-Tx beams for uplink-only TRPs, improving PRACH coverage and reducing latency in wireless communication systems.
Patent Information
- Application Number
- PCT/CN2025/092748
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-05-03
- Publication Date
- 2026-11-12
AI Technical Summary
In wireless communication systems, determining appropriate uplink transmit (UL-Tx) beams for transmitting messages to uplink-only transmission reception points (TRPs) is challenging due to the absence of downlink reference signals, which complicates the PRACH procedure and leads to increased latency and reduced coverage.
The method involves providing system information that includes location identifiers and associations between synchronization signal blocks (SSBs) and PRACH resources, allowing UEs to determine UL-Tx beams based on downlink reception parameters, thereby improving PRACH coverage and reducing latency.
This approach enhances PRACH coverage and reduces latency by enabling accurate beam selection and minimizing the need for beam sweeping through location-based RACH resource allocation and probabilistic weighting.
Smart Images

Figure CN2025092748_12112026_PF_FP_ABST
Abstract
Description
LOCATION BASED PRACH RESOURCE AND BEAM IDENTIFICATION FOR UL-ONLY TRPTECHNICAL FIELD
[0001] The present disclosure relates generally to communication systems and, more particularly, to physical random access channel (PRACH) in wireless communication. INTRODUCTION
[0002] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple-access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.
[0003] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate on a municipal, national, regional, and even global level. An example telecommunication standard is 5G New Radio (NR) . 5G NR is part of a continuous mobile broadband evolution promulgated by Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with Internet of Things (IoT) ) , and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB) , massive machine type communications (mMTC) , and ultra-reliable low latency communications (URLLC) . Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard, and some aspects of future wireless communication technologies may be based on aspects of 5G NR. Some aspects of later wireless communication, such as 6G or others, may be based on aspects of 5G NR and / or 4G LTE. There exists a need for further improvements in 5G NR technology and additional wireless communication technology, including future wireless communication technologies, such as 6G, among other examples. These improvements may also be applicable to other multi-access technologies and the telecommunication standards that employ these technologies. BRIEF SUMMARY
[0004] The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects. This summary neither identifies key or critical elements of all aspects nor delineates the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.
[0005] In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided for wireless communication at a user equipment (UE) . The apparatus may include at least one memory and at least one processor coupled to the at least one memory. Based at least in part on information stored in the at least one memory, the at least one processor may be configured to receive system information, where the system information includes one or more location identifiers and a first number of groups of random access channel (RACH) occasions (ROs) or preambles associated with a second number of uplink nodes of a network entity, where the uplink nodes are dedicated for uplink transmission; transmit, to one uplink node of the second number of uplink nodes, a first message associated with a random access procedure using uplink transmission parameters, where the uplink transmission parameters are based on the system information; and perform the random access procedure with the network entity based on the first message.
[0006] In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided for wireless communication at a network entity. The apparatus may include at least one memory and at least one processor coupled to the at least one memory. Based at least in part on information stored in the at least one memory, the at least one processor may be configured to transmit, to a user equipment (UE) , system information, where the system information includes one or more location identifiers and a first number of groups of ROs or preambles associated with a second number of uplink nodes of the network entity, where the uplink nodes are dedicated for uplink transmission; receive, via one uplink node of the second number of uplink nodes, a first message associated with a random access procedure using uplink transmission parameters, where the uplink transmission parameters are based on the system information; and perform the random access procedure with the UE based on the first message.
[0007] To the accomplishment of the foregoing and related ends, the one or more aspects may include the features hereinafter fully described and particularly pointed out in the claims. The following description and the drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed.BRIEF DESCRIPTION OF THE DRAWINGS
[0008] FIG. 1 is a diagram illustrating an example of a wireless communication system and an access network.
[0009] FIG. 2A is a diagram illustrating an example of a first frame, in accordance with various aspects of the present disclosure.
[0010] FIG. 2B is a diagram illustrating an example of downlink (DL) channels within a subframe, in accordance with various aspects of the present disclosure.
[0011] FIG. 2C is a diagram illustrating an example of a second frame, in accordance with various aspects of the present disclosure.
[0012] FIG. 2D is a diagram illustrating an example of uplink (UL) channels within a subframe, in accordance with various aspects of the present disclosure.
[0013] FIG. 3 is a diagram illustrating an example of a base station and user equipment (UE) in an access network.
[0014] FIG. 4A illustrates example aspects of a random access procedure.
[0015] FIG. 4B illustrates example aspects of a random access procedure.
[0016] FIG. 5A is a diagram illustrating an example of an uplink transmit beam identification based on channel reciprocity with a downlink-and-uplink transmission reception point (TRP) .
[0017] FIG. 5B is a diagram illustrating an example of transmitting message (Msg) 1 (Msg 1) or Msg A toward an uplink-only TRP.
[0018] FIG. 6 is a diagram illustrating an example of a physical random access channel (PRACH) resource and uplink-transmit (UL-Tx) beam identification method in accordance with various aspects of the present disclosure.
[0019] FIG. 7 is a diagram illustrating another example of a PRACH resource and UL-Tx beam identification method in accordance with various aspects of the present disclosure.
[0020] FIG. 8 is a diagram illustrating another example of a PRACH resource and UL-Tx beam identification method in accordance with various aspects of the present disclosure.
[0021] FIG. 9 is a call flow diagram illustrating a method of wireless communication in accordance with various aspects of the present disclosure.
[0022] FIG. 10 is a flowchart illustrating methods of wireless communication at a UE in accordance with various aspects of the present disclosure.
[0023] FIG. 11 is a flowchart illustrating methods of wireless communication at a UE in accordance with various aspects of the present disclosure.
[0024] FIG. 12 is a flowchart illustrating methods of wireless communication at a network entity in accordance with various aspects of the present disclosure.
[0025] FIG. 13 is a diagram illustrating an example of a hardware implementation for an example apparatus and / or UE.
[0026] FIG. 14 is a diagram illustrating an example of a hardware implementation for an example network entity.DETAILED DESCRIPTION
[0027] In wireless communication, uplink (UL) -only transmission reception points (TRPs) may be used to improve physical random access channel (PRACH) coverage and reduce latency. When different UEs access the same cell through the UL-only TRP closest to their location, the likelihood of PRACH collision can be reduced, thereby improving PRACH latency. Additionally, the use of UL-only TRPs improves the efficiency of UE uplink transmit (UL-Tx) power. However, when UL-only TRPs are used for the PRACH procedure, determining the UL-Tx beams for transmitting message (Msg) 1 (Msg 1) or Msg A of the PRACH to the UL-only TRPs becomes challenging. For example, in scenarios involving downlink and uplink symmetric TRPs for PRACH, a UE may identify its UL-Tx beams for Msg 1 or Msg A transmission through reciprocity, such as based on the receive (Rx) beam identified for the synchronization signal block (SSB) associated with the selected RACH resource, such as the preamble or random access occasion (RO) . On the other hand, when transmitting Msg 1 or Msg A toward a UL-only TRP, there are no corresponding downlink reference signals (DL-RSs) to assist the UE in beam determination, and the network may not provide the UE the instructions regarding the UL-Tx beam (s) to be used. Hence, it becomes difficult for the UE to determine the appropriate UL-Tx beam. Example aspects presented herein provide methods and apparatus for location-based RACH resource allocation for UL-only TRPs, for example, by including in the remaining minimum system information (RMSI) an association (e.g., a probabilistic associated) of the SSB to the UL-only TRPs.
[0028] Various aspects relate generally to wireless communication. Some aspects more specifically relate to PRACH resource and beam identification for UL-only TRP in wireless communication. In some examples, a UE receives system information. The system information may include one or more location identifiers and a first number of groups of ROs or preambles associated with a second number of uplink nodes of a network entity. The uplink nodes may be dedicated for uplink transmission. The UE transmits, to one uplink node of the second number of uplink nodes, a first message associated with a random access procedure using uplink transmission parameters. The uplink transmission parameters may be based on the system information. The UE then performs the random access procedure with the network entity based on the first message. In some examples, the system information may further include a third number of synchronization signal blocks (SSBs) , and the first number of groups of ROs or preambles are respectively mapped to the third number of SSBs. In this case, the UE may determine the uplink transmission parameters based on downlink reception parameters for the reception of one SSB of the third number of SSBs. The one SSB may map to the corresponding RO or preamble. In some examples, the system information may further include a fourth number of uplink pointing directions, and the first number of groups of ROs or preambles may be respectively mapped to the fourth number of uplink pointing directions. In this case, the UE may determine the uplink transmission parameters based on one uplink pointing direction of the fourth number of uplink pointing directions. The one uplink pointing direction is associated with the corresponding RO or preamble. In some examples, the system information may further include prior probability information for the third number of SSBs. In some examples, the system information may further include one or more of: location information for the second number of uplink nodes, or prior probability information for the fourth number of uplink pointing directions.
[0029] Particular aspects of the subject matter described in this disclosure can be implemented to realize one or more of the following potential advantages. In some examples, by associating UE locations with SSBs and ROs or preambles, or by incorporating location-based beam identification with system broadcast information (e.g., RMSI) , the described techniques allow UE to determine appropriate PRACH resources and UL-Tx beam directions for Msg 1 or Msg A transmission for UL-only TRPs, thereby improving PRACH coverage and reducing latency. In some examples, by using prior probability signaling for SSBs or ROs / preambles, the described techniques allow the network to guide UEs with probabilistic weighting toward the most effective access configurations, thereby improving beam selection accuracy and reducing the need for beam sweeping.
[0030] The detailed description set forth below in connection with the drawings describes various configurations and does not represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of various concepts. However, 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.
[0031] Several aspects of telecommunication systems are presented with reference to various apparatus and methods. These apparatus and methods are described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as “elements” ) . These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.
[0032] By way of example, an element, or any portion of an element, or any combination of elements may be implemented as a “processing system” that includes one or more processors. When multiple processors are implemented, the multiple processors may perform the functions individually or in combination. 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, systems on a chip (SoC) , baseband processors, field programmable gate arrays (FPGAs) , programmable logic devices (PLDs) , state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure. One or more processors in the processing system may execute software. Software, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise, shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, or any combination thereof.
[0033] Accordingly, in one or more example aspects, implementations, and / or use cases, the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored on or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media includes computer storage media. Storage media may be any available media that can be accessed by a computer. By way of example, such computer-readable media can include a random-access memory (RAM) , a read-only memory (ROM) , an electrically erasable programmable ROM (EEPROM) , optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of the types of computer-readable media, or any other medium that can be used to store computer executable code in the form of instructions or data structures that can be accessed by a computer.
[0034] While aspects, implementations, and / or use cases are described in this application by illustration to some examples, additional or different aspects, implementations and / or use cases may come about in many different arrangements and scenarios. Aspects, implementations, and / or use cases described herein may be implemented across many differing platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, aspects, implementations, and / or use cases may come about via integrated chip implementations and other non-module-component based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, artificial intelligence (AI) -enabled devices, etc. ) . While some examples may or may not be specifically directed to use cases or applications, a wide assortment of applicability of described examples may occur. Aspects, implementations, and / or use cases may range a spectrum from chip-level or modular components to non-modular, non-chip-level implementations and further to aggregate, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more techniques herein. In some practical settings, devices incorporating described aspects and features may also include additional components and features for implementation and practice of claimed and described aspect. For example, transmission and reception of wireless signals necessarily includes a number of components for analog and digital purposes (e.g., hardware components including antenna, RF-chains, power amplifiers, modulators, buffer, processor (s) , interleaver, adders / summers, etc. ) . Techniques described herein may be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc. of varying sizes, shapes, and constitution.
[0035] Deployment of communication systems, such as 5G NR systems, 6G systems, or other communication systems, may be arranged in multiple manners with various components or constituent parts. As an example, in a wireless communication network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element, or a network equipment, such as a base station (BS) , or one or more units (or one or more components) performing base station functionality, may be implemented in an aggregated or disaggregated architecture. For example, a BS (such as a Node B (NB) , evolved NB (eNB) , NR BS, 5G NB, access point (AP) , a transmission reception point (TRP) , or a cell, etc. ) may be implemented as an aggregated base station (also known as a standalone BS or a monolithic BS) or a disaggregated base station.
[0036] An aggregated base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A disaggregated base station may be configured to utilize a protocol stack that is physically or logically distributed among two or more units (such as one or more central or centralized units (CUs) , one or more distributed units (DUs) , or one or more radio units (RUs) ) . In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed throughout one or multiple other RAN nodes. The DUs may be implemented to communicate with one or more RUs. Each of the CU, DU and RU can be implemented as virtual units, i.e., a virtual central unit (VCU) , a virtual distributed unit (VDU) , or a virtual radio unit (VRU) .
[0037] Base station operation or network design may consider aggregation characteristics of base station functionality. For example, disaggregated base stations may be utilized in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (such as the network configuration sponsored by the O-RAN Alliance) ) , or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN) ) . Disaggregation may include distributing functionality across two or more units at various physical locations, as well as distributing functionality for at least one unit virtually, which can enable flexibility in network design. The various units of the disaggregated base station, or disaggregated RAN architecture, can be configured for wired or wireless communication with at least one other unit.
[0038] FIG. 1 is a diagram 100 illustrating an example of a wireless communications system and an access network. The illustrated wireless communications system includes a disaggregated base station architecture. The disaggregated base station architecture may include one or more CUs 110 that can communicate directly with a core network 120 via a backhaul link, or indirectly with the core network 120 through one or more disaggregated base station units (such as a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC) 125 via an E2 link, or a Non-Real Time (Non-RT) RIC 115 associated with a Service Management and Orchestration (SMO) Framework 105, or both) . A CU 110 may communicate with one or more DUs 130 via respective midhaul links, such as an F1 interface. The DUs 130 may communicate with one or more RUs 140 via respective fronthaul links. The RUs 140 may communicate with respective UEs 104 via one or more radio frequency (RF) access links. In some implementations, the UE 104 may be simultaneously served by multiple RUs 140.
[0039] Each of the units, i.e., the CUs 110, the DUs 130, the RUs 140, as well as the Near-RT RICs 125, the Non-RT RICs 115, and the SMO Framework 105, may include one or more interfaces or be coupled to one or more interfaces configured to receive or to transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units, or an associated processor or controller providing instructions to the communication interfaces of the units, can be configured to communicate with one or more of the other units via the transmission medium. For example, the units can include a wired interface configured to receive or to transmit signals over a wired transmission medium to one or more of the other units. Additionally, the units can include a wireless interface, which may include a receiver, a transmitter, or a transceiver (such as an RF transceiver) , configured to receive or to transmit signals, or both, over a wireless transmission medium to one or more of the other units.
[0040] In some aspects, the CU 110 may host one or more higher layer control functions. Such control functions can include radio resource control (RRC) , packet data convergence protocol (PDCP) , service data adaptation protocol (SDAP) , or the like. Each control function can be implemented with an interface configured to communicate signals with other control functions hosted by the CU 110. The CU 110 may be configured to handle user plane functionality (i.e., Central Unit –User Plane (CU-UP) ) , control plane functionality (i.e., Central Unit –Control Plane (CU-CP) ) , or a combination thereof. In some implementations, the CU 110 can be logically split into one or more CU-UP units and one or more CU-CP units. The CU-UP unit can communicate bidirectionally with the CU-CP unit via an interface, such as an E1 interface when implemented in an O-RAN configuration. The CU 110 can be implemented to communicate with the DU 130, as necessary, for network control and signaling.
[0041] The DU 130 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs 140. In some aspects, the DU 130 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation, demodulation, or the like) depending, at least in part, on a functional split, such as those defined by 3GPP. In some aspects, the DU 130 may further host one or more low PHY layers. Each layer (or module) can be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 130, or with the control functions hosted by the CU 110.
[0042] Lower-layer functionality can be implemented by one or more RUs 140. In some deployments, an RU 140, controlled by a DU 130, may correspond to a logical node that hosts RF processing functions, or low-PHY layer functions (such as performing fast Fourier transform (FFT) , inverse FFT (iFFT) , digital beamforming, physical random access channel (PRACH) extraction and filtering, or the like) , or both, based at least in part on the functional split, such as a lower layer functional split. In such an architecture, the RU (s) 140 can be implemented to handle over the air (OTA) communication with one or more UEs 104. In some implementations, real-time and non-real-time aspects of control and user plane communication with the RU (s) 140 can be controlled by the corresponding DU 130. In some scenarios, this configuration can enable the DU (s) 130 and the CU 110 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.
[0043] The SMO Framework 105 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO Framework 105 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements that may be managed via an operations and maintenance interface (such as an O1 interface) . For virtualized network elements, the SMO Framework 105 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 190) to perform network element life cycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an O2 interface) . Such virtualized network elements can include, but are not limited to, CUs 110, DUs 130, RUs 140 and Near-RT RICs 125. In some implementations, the SMO Framework 105 can communicate with a hardware aspect of a 4G RAN, such as an open eNB (O-eNB) 111, via an O1 interface. Additionally, in some implementations, the SMO Framework 105 can communicate directly with one or more RUs 140 via an O1 interface. The SMO Framework 105 also may include a Non-RT RIC 115 configured to support functionality of the SMO Framework 105.
[0044] The Non-RT RIC 115 may be configured to include a logical function that enables non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) / machine learning (ML) (AI / ML) workflows including model training and updates, or policy-based guidance of applications / features in the Near-RT RIC 125. The Non-RT RIC 115 may be coupled to or communicate with (such as via an A1 interface) the Near-RT RIC 125. The Near-RT RIC 125 may be configured to include a logical function that enables near-real-time control and optimization of RAN elements and resources via data collection and actions over an interface (such as via an E2 interface) connecting one or more CUs 110, one or more DUs 130, or both, as well as an O-eNB, with the Near-RT RIC 125.
[0045] In some implementations, to generate AI / ML models to be deployed in the Near-RT RIC 125, the Non-RT RIC 115 may receive parameters or external enrichment information from external servers. Such information may be utilized by the Near-RT RIC 125 and may be received at the SMO Framework 105 or the Non-RT RIC 115 from non-network data sources or from network functions. In some examples, the Non-RT RIC 115 or the Near-RT RIC 125 may be configured to tune RAN behavior or performance. For example, the Non-RT RIC 115 may monitor long-term trends and patterns for performance and employ AI / ML models to perform corrective actions through the SMO Framework 105 (such as reconfiguration via O1) or via creation of RAN management policies (such as A1 policies) .
[0046] At least one of the CU 110, the DU 130, and the RU 140 may be referred to as a base station 102. Accordingly, a base station 102 may include one or more of the CU 110, the DU 130, and the RU 140 (each component indicated with dotted lines to signify that each component may or may not be included in the base station 102) . The base station 102 provides an access point to the core network 120 for a UE 104. The base station 102 may include macrocells (high power cellular base station) and / or small cells (low power cellular base station) . The small cells include femtocells, picocells, and microcells. A network that includes both small cell and macrocells may be known as a heterogeneous network. A heterogeneous network may also include Home Evolved Node Bs (eNBs) (HeNBs) , which may provide service to a restricted group known as a closed subscriber group (CSG) . The communication links between the RUs 140 and the UEs 104 may include uplink (UL) (also referred to as reverse link) transmissions from a UE 104 to an RU 140 and / or downlink (DL) (also referred to as forward link) transmissions from an RU 140 to a UE 104. The communication links may use multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication links may be through one or more carriers. The base station 102 / UEs 104 may use spectrum up to Y MHz (e.g., 5, 10, 15, 20, 100, 400, etc. MHz) bandwidth per carrier allocated in a carrier aggregation of up to a total of Yx MHz (x component carriers) used for transmission in each direction. The carriers may or may not be adjacent to each other. Allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL than for UL) . The component carriers may include a primary component carrier and one or more secondary component carriers. A primary component carrier may be referred to as a primary cell (PCell) and a secondary component carrier may be referred to as a secondary cell (SCell) .
[0047] Certain UEs 104 may communicate with each other using device-to-device (D2D) communication link 158. The D2D communication link 158 may use the DL / UL wireless wide area network (WWAN) spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH) , a physical sidelink discovery channel (PSDCH) , a physical sidelink shared channel (PSSCH) , and a physical sidelink control channel (PSCCH) . D2D communication may be through a variety of wireless D2D communications systems, such as for example, BluetoothTM (Bluetooth is a trademark of the Bluetooth Special Interest Group (SIG) ) , Wi-FiTM (Wi-Fi is a trademark of the Wi-Fi Alliance) based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.
[0048] The wireless communications system may further include a Wi-Fi AP 150 in communication with UEs 104 (also referred to as Wi-Fi stations (STAs) ) via communication link 154, e.g., in a 5 GHz unlicensed frequency spectrum or the like. When communicating in an unlicensed frequency spectrum, the UEs 104 / AP 150 may perform a clear channel assessment (CCA) prior to communicating in order to determine whether the channel is available.
[0049] The electromagnetic spectrum is often subdivided, based on frequency / wavelength, into various classes, bands, channels, etc. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz –7.125 GHz) and FR2 (24.25 GHz –52.6 GHz) . Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as a “sub-6 GHz” band in various documents and articles. A similar nomenclature issue sometimes occurs with regard to FR2, which is often referred to (interchangeably) as a “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz –300 GHz) which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band.
[0050] The frequencies between FR1 and FR2 are often referred to as mid-band frequencies. An operating band for these mid-band frequencies may have the frequency range designation FR3 (7.125 GHz –24.25 GHz) , for example. Frequency bands falling within FR3 may inherit FR1 characteristics and / or FR2 characteristics, and thus may effectively extend features of FR1 and / or FR2 into mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operation, or other wireless communication operation, beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR2-2 (52.6 GHz –71 GHz) , FR4 (71 GHz –114.25 GHz) , and FR5 (114.25 GHz –300 GHz) . Each of these higher frequency bands falls within the EHF band.
[0051] With the above aspects in mind, unless specifically stated otherwise, the term “sub-6 GHz” or the like if used herein may broadly represent frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. Further, unless specifically stated otherwise, the term “millimeter wave” or the like if used herein may broadly represent frequencies that may include mid-band frequencies, may be within FR2, FR4, FR2-2, and / or FR5, or may be within the EHF band.
[0052] The base station 102 and the UE 104 may each include a plurality of antennas, such as antenna elements, antenna panels, and / or antenna arrays to facilitate beamforming. The base station 102 may transmit a beamformed signal 182 to the UE 104 in one or more transmit directions. The UE 104 may receive the beamformed signal from the base station 102 in one or more receive directions. The UE 104 may also transmit a beamformed signal 184 to the base station 102 in one or more transmit directions. The base station 102 may receive the beamformed signal from the UE 104 in one or more receive directions. The base station 102 / UE 104 may perform beam training to determine the best receive and transmit directions for each of the base station 102 / UE 104. The transmit and receive directions for the base station 102 may or may not be the same. The transmit and receive directions for the UE 104 may or may not be the same.
[0053] The base station 102 may include and / or be referred to as a gNB, Node B, eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS) , an extended service set (ESS) , a TRP, network node, network entity, network equipment, or some other suitable terminology. The base station 102 can be implemented as an integrated access and backhaul (IAB) node, a relay node, a sidelink node, an aggregated (monolithic) base station with a baseband unit (BBU) (including a CU and a DU) and an RU, or as a disaggregated base station including one or more of a CU, a DU, and / or an RU. The set of base stations, which may include disaggregated base stations and / or aggregated base stations, may be referred to as next generation (NG) RAN (NG-RAN) .
[0054] The core network 120 may include an Access and Mobility Management Function (AMF) 161, a Session Management Function (SMF) 162, a User Plane Function (UPF) 163, a Unified Data Management (UDM) 164, one or more location servers 168, and other functional entities. The AMF 161 is the control node that processes the signaling between the UEs 104 and the core network 120. The AMF 161 supports registration management, connection management, mobility management, and other functions. The SMF 162 supports session management and other functions. The UPF 163 supports packet routing, packet forwarding, and other functions. The UDM 164 supports the generation of authentication and key agreement (AKA) credentials, user identification handling, access authorization, and subscription management. The one or more location servers 168 are illustrated as including a Gateway Mobile Location Center (GMLC) 165 and a Location Management Function (LMF) 166. However, generally, the one or more location servers 168 may include one or more location / positioning servers, which may include one or more of the GMLC 165, the LMF 166, a position determination entity (PDE) , a serving mobile location center (SMLC) , a mobile positioning center (MPC) , or the like. The GMLC 165 and the LMF 166 support UE location services. The GMLC 165 provides an interface for clients / applications (e.g., emergency services) for accessing UE positioning information. The LMF 166 receives measurements and assistance information from the NG-RAN and the UE 104 via the AMF 161 to compute the position of the UE 104. The NG-RAN may utilize one or more positioning methods in order to determine the position of the UE 104. Positioning the UE 104 may involve signal measurements, a position estimate, and an optional velocity computation based on the measurements. The signal measurements may be made by the UE 104 and / or the base station 102 serving the UE 104. The signals measured may be based on one or more of a satellite positioning system (SPS) 170 (e.g., one or more of a Global Navigation Satellite System (GNSS) , global position system (GPS) , non-terrestrial network (NTN) , or other satellite position / location system) , LTE signals, wireless local area network (WLAN) signals, Bluetooth signals, a terrestrial beacon system (TBS) , sensor-based information (e.g., barometric pressure sensor, motion sensor) , NR enhanced cell ID (NR E-CID) methods, NR signals (e.g., multi-round trip time (Multi-RTT) , DL angle-of-departure (DL-AoD) , DL time difference of arrival (DL-TDOA) , UL time difference of arrival (UL-TDOA) , and UL angle-of-arrival (UL-AoA) positioning) , and / or other systems / signals / sensors.
[0055] Examples of UEs 104 include a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA) , a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player) , a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor / actuator, a display, or any other similar functioning device. Some of the UEs 104 may be referred to as IoT devices (e.g., parking meter, gas pump, toaster, vehicles, heart monitor, etc. ) . The UE 104 may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology. In some scenarios, the term UE may also apply to one or more companion devices such as in a device constellation arrangement. One or more of these devices may collectively access the network and / or individually access the network.
[0056] Referring again to FIG. 1, in certain aspects, the UE 104 may include the PRACH component 198. The PRACH component 198 may be configured to receive system information, where the system information includes one or more location identifiers and a first number of groups of ROs or preambles associated with a second number of uplink nodes of a network entity, where the uplink nodes are dedicated for uplink transmission; transmit, to one uplink node of the second number of uplink nodes, a first message associated with a random access procedure using uplink transmission parameters, where the uplink transmission parameters are based on the system information; and perform the random access procedure with the network entity based on the first message. In certain aspects, the base station 102 may include the PRACH component 199. The PRACH component 199 may be configured to transmit, to a UE, system information, where the system information includes one or more location identifiers and a first number of groups of ROs or preambles associated with a second number of uplink nodes of the network entity, where the uplink nodes are dedicated for uplink transmission; receive, via one uplink node of the second number of uplink nodes, a first message associated with a random access procedure using uplink transmission parameters, where the uplink transmission parameters are based on the system information; and perform the random access procedure with the UE based on the first message. Although the following description may give examples based on 5G NR to illustrate concepts relating to wireless communication, the concepts described herein may be applicable to other similar areas, such as LTE, LTE-A, CDMA, GSM, 6G and other wireless technologies.
[0057] FIG. 2A is a diagram 200 illustrating an example of a first subframe within a frame structure. FIG. 2B is a diagram 230 illustrating an example of DL channels within a subframe. FIG. 2C is a diagram 250 illustrating an example of a second subframe within a frame structure. FIG. 2D is a diagram 280 illustrating an example of UL channels within a subframe. The examples in FIGs. 2A-2D show example aspects of a frame structure based on 5G NR to illustrate the concept of a frame structure and wireless communication based on a frame structure. Various aspects described in connection with FIGs. 2A-2D may also be used in connection with other wireless communication technologies, such as 6G among other examples. The frame structure may be frequency division duplexed (FDD) in which for a particular set of subcarriers (carrier system bandwidth) , subframes within the set of subcarriers are dedicated for either DL or UL, or may be time division duplexed (TDD) in which for a particular set of subcarriers (carrier system bandwidth) , subframes within the set of subcarriers are dedicated for both DL and UL. In the examples provided by FIGs. 2A, 2C, the 5G NR frame structure is assumed to be TDD, with subframe 4 being configured with slot format 28 (with mostly DL) , where D is DL, U is UL, and F is flexible for use between DL / UL, and subframe 3 being configured with slot format 1 (with all UL) . While subframes 3, 4 are shown with slot formats 1, 28, respectively, any particular subframe may be configured with any of the various available slot formats 0-61. Slot formats 0, 1 are all DL, UL, respectively. Other slot formats 2-61 include a mix of DL, UL, and flexible symbols. UEs are configured with the slot format (dynamically through DL control information (DCI) , or semi-statically / statically through radio resource control (RRC) signaling) through a received slot format indicator (SFI) . Note that the description infra applies also to a 5G NR frame structure that is TDD.
[0058] FIGs. 2A-2D illustrate a frame structure, and the aspects of the present disclosure may be applicable to other wireless communication technologies, which may have a different frame structure and / or different channels. A frame (10 ms) may be divided into 10 equally sized subframes (1 ms) . Each subframe may include one or more time slots. Subframes may also include mini-slots, which may include 7, 4, or 2 symbols. Each slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended. For normal CP, each slot may include 14 symbols, and for extended CP, each slot may include 12 symbols. The symbols on DL may be CP orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbols. The symbols on UL may be CP-OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbols (for power limited scenarios; limited to a single stream transmission) . The number of slots within a subframe is based on the CP and the numerology. The numerology defines the subcarrier spacing (SCS) (see Table 1) . The symbol length / duration may scale with 1 / SCS. Table 1: Numerology, SCS, and CP
[0059] For normal CP (14 symbols / slot) , different numerologies μ 0 to 4 allow for 1, 2, 4, 8, and 16 slots, respectively, per subframe. For extended CP, the numerology 2 allows for 4 slots per subframe. Accordingly, for normal CP and numerology μ, there are 14 symbols / slot and 2μ slots / subframe. The subcarrier spacing may be equal to 2μ*15 kHz, where μ is the numerology 0 to 4. As such, the numerology μ=0 has a subcarrier spacing of 15 kHz and the numerology μ=4 has a subcarrier spacing of 240 kHz. The symbol length / duration is inversely related to the subcarrier spacing. FIGs. 2A-2D provide an example of normal CP with 14 symbols per slot and numerology μ=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within a set of frames, there may be one or more different bandwidth parts (BWPs) (see FIG. 2B) that are frequency division multiplexed. Each BWP may have a particular numerology and CP (normal or extended) .
[0060] A resource grid may be used to represent the frame structure. Each time slot includes a resource block (RB) (also referred to as physical RBs (PRBs) ) that extends 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.
[0061] As illustrated in FIG. 2A, some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include demodulation RS (DM-RS) (indicated as R for one particular configuration, but other DM-RS configurations are possible) and channel state information reference signals (CSI-RS) for channel estimation at the UE. The RS may also include beam measurement RS (BRS) , beam refinement RS (BRRS) , and phase tracking RS (PT-RS) .
[0062] FIG. 2B illustrates an example of various DL channels within a subframe of a frame. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs) , each CCE including six RE groups (REGs) , each REG including 12 consecutive REs in an OFDM symbol of an RB. A PDCCH within one BWP may be referred to as a control resource set (CORESET) . A UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., common search space, UE-specific search space) during PDCCH monitoring occasions on the CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at greater and / or lower frequencies across the channel bandwidth. A primary synchronization signal (PSS) may be within symbol 2 of particular subframes of a frame. The PSS is used by a UE 104 to determine subframe / symbol timing and a physical layer identity. A secondary synchronization signal (SSS) may be within symbol 4 of particular subframes of a frame. The SSS is used by a UE to determine a physical layer cell identity group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine a physical cell identifier (PCI) . Based on the PCI, the UE can determine the locations of the DM-RS. The physical broadcast channel (PBCH) , which carries a master information block (MIB) , may be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (also referred to as SS block (SSB) ) . The MIB provides a number of RBs in the system bandwidth and a system frame number (SFN) . 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.
[0063] As illustrated in FIG. 2C, some of the REs carry DM-RS (indicated as R for one particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may transmit DM-RS for the physical uplink control channel (PUCCH) and DM-RS for the physical uplink shared channel (PUSCH) . The PUSCH DM-RS may be transmitted in the first one or two symbols of the PUSCH. The PUCCH DM-RS may be transmitted in different configurations depending on whether short or long PUCCHs are transmitted and depending on the particular PUCCH format used. The UE may transmit sounding reference signals (SRS) . The SRS may be transmitted in the last symbol of a subframe. The SRS may have a comb structure, and a UE may transmit SRS on one of the combs. The SRS may be used by a base station for channel quality estimation to enable frequency-dependent scheduling on the UL.
[0064] FIG. 2D illustrates an example of various UL channels within a subframe of a frame. The PUCCH may be located as indicated in one configuration. The PUCCH carries uplink control information (UCI) , such as scheduling requests, a channel quality indicator (CQI) , a precoding matrix indicator (PMI) , a rank indicator (RI) , and hybrid automatic repeat request (HARQ) acknowledgment (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACK and / or negative ACK (NACK) ) . The PUSCH carries data, and may additionally be used to carry a buffer status report (BSR) , a power headroom report (PHR) , and / or UCI.
[0065] FIG. 3 is a block diagram of a base station 310 in communication with a UE 350 in an access network. In the DL, Internet protocol (IP) packets may be provided to a controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIBs) , RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release) , inter radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (ciphering, deciphering, integrity protection, integrity verification) , and handover support functions; RLC layer functionality associated with the transfer of upper layer packet data units (PDUs) , error correction through ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs) , re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs) , demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.
[0066] The transmit (TX) processor 316 and the receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1, which includes a physical (PHY) layer, may include error detection on the transport channels, forward error correction (FEC) coding / decoding of the transport channels, interleaving, rate matching, mapping onto physical channels, modulation / demodulation of physical channels, and MIMO antenna processing. The TX processor 316 handles mapping to signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK) , quadrature phase-shift keying (QPSK) , M-phase-shift keying (M-PSK) , M-quadrature amplitude modulation (M-QAM) ) . The coded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and / or frequency domain, and then combined together using an Inverse Fast Fourier Transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially precoded to produce multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation scheme, as well as for spatial processing. The channel estimate may be derived from a reference signal and / or channel condition feedback transmitted by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx may modulate a radio frequency (RF) carrier with a respective spatial stream for transmission.
[0067] At the UE 350, each receiver 354Rx receives a signal through its respective antenna 352. Each receiver 354Rx recovers information modulated onto an RF carrier and provides the information to the receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions. The RX processor 356 may perform spatial processing on the information to recover any spatial streams destined for the UE 350. If multiple spatial streams are destined for the UE 350, they may be combined by the RX processor 356 into a single OFDM symbol stream. The RX processor 356 then converts the OFDM symbol stream from the time-domain to the frequency domain using a Fast Fourier Transform (FFT) . The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, and the reference signal, are recovered and demodulated by determining the most likely signal constellation points transmitted by the base station 310. These soft decisions may be based on channel estimates computed by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals that were 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 functionality.
[0068] The controller / processor 359 can be associated with at least one memory 360 that stores program codes and data. The at least one memory 360 may be referred to as a computer-readable medium. In the UL, the controller / processor 359 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, and control signal processing to recover IP packets. The controller / processor 359 is also responsible for error detection using an ACK and / or NACK protocol to support HARQ operations.
[0069] Similar to the functionality described in connection with the DL transmission by the base station 310, the controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIBs) acquisition, RRC connections, and measurement reporting; PDCP layer functionality associated with header compression / decompression, and security (ciphering, deciphering, integrity protection, integrity verification) ; RLC layer functionality associated with the transfer of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.
[0070] Channel estimates derived by a 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 the appropriate coding and modulation schemes, and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antenna 352 via separate transmitters 354Tx. Each transmitter 354Tx may modulate an RF carrier with a respective spatial stream for transmission.
[0071] The UL transmission is processed at the base station 310 in a manner similar to that described in connection with the receiver function at the UE 350. Each receiver 318Rx receives a signal through its respective antenna 320. Each receiver 318Rx recovers information modulated onto an RF carrier and provides the information to a RX processor 370.
[0072] The controller / processor 375 can be associated with at least one memory 376 that stores program codes and data. The at least one memory 376 may be referred to as a computer-readable medium. In the UL, the controller / processor 375 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover IP packets. The controller / processor 375 is also responsible for error detection using an ACK and / or NACK protocol to support HARQ operations.
[0073] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to perform aspects in connection with the PRACH component 198 of FIG. 1.
[0074] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to perform aspects in connection with the PRACH component 199 of FIG. 1.
[0075] A UE may use a random access procedure in order to communicate with a base station. FIG. 4A illustrates example aspects of a random access procedure 400 between a UE 402 and a base station 404. For example, the UE 402 may be a New Radio (NR) UE. For example, the UE 402 may use the random access procedure to request an RRC connection, to re-establish an RRC connection, to resume an RRC connection, etc. The UE 402 may initiate the random access message exchange by sending, to the base station 404, a first random access message 403 (e.g., Msg 1) including a preamble. In some examples, prior to sending the first random access message 403, the UE 402 may obtain random access parameters, e.g., including preamble format parameters, time and frequency resources, parameters for determining root sequences and / or cyclic shifts for a random access preamble, etc., e.g., in system information 401 from the base station 404. The preamble may be transmitted with an identifier, such as a Random Access RNTI (RA-RNTI) . The UE 402 may randomly select a random access preamble sequence, e.g., from a set of preamble sequences. If the UE 402 randomly selects the preamble sequence, the base station 404 may receive another preamble from a different UE at the same time. In some examples, a preamble sequence may be assigned to the UE 402.
[0076] The base station 404 responds to the first random access message 403 by sending a second random access message 405 (e.g., Msg 2) using PDSCH and including a random access response (RAR) . The RAR may include, e.g., an identifier of the random access preamble sent by the UE, a time advance (TA) , an uplink grant for the UE to transmit data, a cell radio network temporary identifier (C-RNTI) or other identifier, and / or a back-off indicator. Upon receiving the RAR at 405, the UE 402 may transmit a third random access message 407 (e.g., Msg 3) to the base station 404, e.g., using PUSCH, that may include an RRC connection request, an RRC connection re-establishment request, or an RRC connection resume request, depending on the trigger for the initiating the random access procedure. The base station 404 may then complete the random access procedure by sending a fourth random access message 409 (e.g., Msg 4) to the UE 402, e.g., using PDCCH for scheduling and PDSCH for the message. The fourth random access message 409 may include a random access response message that includes timing advancement information, contention resolution information, and / or RRC connection setup information. The UE 402 may monitor for PDCCH, e.g., with the C-RNTI. If the PDCCH is successfully decoded, the UE 402 may also decode PDSCH. The UE 402 may send HARQ feedback for any data carried in the fourth random access message. If two UEs send the same preamble at 403, both UEs may receive the RAR, leading both UEs to send a third random access message 407. The base station 404 may resolve such a collision by being able to decode the third random access message from one of the UEs and responding with a fourth random access message to that UE. The other UE, which did not receive the fourth random access message 409, may determine that random access did not succeed and may re-attempt random access. Thus, the fourth message may be referred to as a contention resolution message. The fourth random access message 409 may complete the random access procedure. Thus, the UE 402 may then transmit uplink communication and / or receive downlink communication with the base station 404 based on the RAR.
[0077] In order to reduce latency or control signaling overhead, a single round trip cycle between the UE and the base station 404 may be achieved in a 2-step RACH process 430, such as shown in FIG. 4B. Aspects of Msg 1 (e.g., at 403) and Msg 3 (e.g., at 407) may be combined in a single message, e.g., which may be referred to as Msg A (e.g., at 411) . The Msg A may include a random access preamble, and may also include a PUSCH transmission, e.g., such as data. The MsgA preambles may be separate from the four step preambles, yet may be transmitted in the same random access occasions (ROs) as the preambles of the four step RACH procedure or may be transmitted in separate ROs. The PUSCH transmissions may be transmitted in PUSCH occasions (POs) that may span multiple symbols and PRBs. After the UE 402 transmits the Msg A (e.g., at 411) , the UE 402 may wait for a response from the base station 404. Additionally, aspects of the Msg 2 (e.g., at 405) and Msg 4 (e.g., at 409) may be combined into a single message, which may be referred to as Msg B (e.g., at 413) . Two step RACH may be triggered for reasons similar to a four-step RACH procedure. If the UE does not receive a response, the UE may retransmit the MsgA or may fall back to a four-step RACH procedure starting with a Msg 1. If the base station detects the Msg A, but fails to successfully decode the Msg A PUSCH, the base station may respond with an allocation of resources for an uplink retransmission of the PUSCH. The UE may fall back to the four step RACH with a transmission of Msg 3 based on the response from the base station and may retransmit the PUSCH from Msg A.If the base station successfully decodes the Msg A and corresponding PUSCH, the base station may reply with an indication of the successful receipt, e.g., as a random access response 413 that completes the two-step RACH procedure. The Msg B may include the random access response and a contention-resolution message. The contention resolution message may be sent after the base station successfully decodes the PUSCH transmission. The physical layer implementation of the RACH procedure may be referred to as the physical random access channel (PRACH) procedure.
[0078] In wireless communication, a UL-only TRP refers to a network node or TRP that is configured to receive uplink signals from UE but does not transmit downlink signals. In some aspects, UL-only TRPs may also be referred to as UL TRPs. Initial access (e.g., PRACH procedures) through UL-only TRPs may improve PRACH coverage and latency. For example, when different UEs access the same cell through the UL-only TRP closest to their location, the likelihood of PRACH collision (e.g., a situation in which two or more UEs select and transmit the same preamble on the same PRACH resource) can be reduced, thus improving PRACH latency. Additionally, the use of UL-only TRPs improves the efficiency of UE uplink transmit (UL-Tx) power. However, when UL-only TRPs are used for the PRACH procedure, determining the UL-Tx beams for transmitting Msg 1 or Msg A of the PRACH to the UL-only TRPs becomes challenging. For example, in scenarios involving downlink and uplink symmetric TRPs for PRACH, a UE may identify its UL-Tx beams for Msg 1 or Msg A transmission through reciprocity, such as based on the receive (Rx) beam identified for the SSB associated with the selected RACH resource, such as the preamble or RO. FIG. 5A is a diagram 500 illustrating an example of identifying a UL-Tx beam based on reciprocity with a DL-and-UL TRP. As shown in FIG. 5A, UE 502 may identify its UL-Tx beam 510 for Msg 1 or Msg A transmission to TRP 504 through channel reciprocity, such as based on the Rx beams 520 identified for the SSB associated with the selected RACH resource (e.g., preamble or RO) .
[0079] On the other hand, when transmitting Msg 1 or Msg A toward a UL-only TRP, there are no corresponding downlink reference signals to assist the UE in beam determination, and the network may not provide the UE the instructions regarding the UL-Tx beam (s) to be used. Hence, it becomes difficult for the UE to determine the appropriate UL-Tx beam. FIG. 5B is a diagram 550 illustrating an example of transmitting Msg 1 or Msg A toward a UL-only TRP. As shown in FIG. 5B, when UE 552 performs a PRACH procedure with UL-only TRP 562 (e.g., transmitting Msg 1 or Msg A toward UL-only TRP 562 at 570) , it is difficult for UE 552 to determine the UL-Tx beam for Msg 1 or Msg A transmission, as there are no corresponding downlink reference signals from UL-only TRP 562 to assist the UE 552 in beam determination, and the network (e.g., DL+UL TRP 554) may not provide the UE 552 the instructions regarding the UL-Tx beam (s) to be used. Example aspects presented herein provide methods and apparatus for location-based RACH resource allocation for UL-only TRPs. These methods address the challenge that UL-only TRPs lack channel reciprocity, and therefore the RO cannot be determined based on the received SSB beam. In some example aspects, methods are provided to include in the RMSI information a (probabilistic) association of the SSB to the UL-only TRPs. Some example aspects provide methods to build the association and to incorporate UE location information.
[0080] In some aspects, a method for PRACH resource and uplink-transmit (UL-Tx) beam identification based on location and synchronization signal blocks (SSB) is provided. In some examples, at a given location, the uplink receive (UL-Rx) beam (s) that would be better used by UL-only TRPs for receiving, and thus the UE’s corresponding UL-Tx beam for transmitting, may be probabilistically identified to be associated with certain SSBs transmitted by a DL-and-UL TRP (e.g., DL+UL TRP) . FIG. 6 is a diagram 600 illustrating an example of a PRACH resource and UL-Tx beam identification method based on location and SSB in accordance with various aspects of the present disclosure. As shown in FIG. 6, there is a single DL+UL TRP 610 and four UL-only TRPs (TRP #1 612, TRP #2 614, TRP #3 616, TRP #4 618) are available for PRACH procedures for a UE. Each of these four UL-only TRPs (TRP #1 612, TRP #2 614, TRP #3 616, TRP #4 618) may be associated with four UL-Rx beams. For example, TRP #1 612 may be associated with UL-Rx beam #1.1 622, beam #1.2 624, beam #1.3 626, and beam #1.4 628. TRP #2 614 may be associated with UL-Rx beam #2.1 632, beam #2.2 634, beam #2.3 636, and beam #2.4 638. TRP #3 616 may be associated with UL-Rx beam #3.1 642, beam #3.2 644, beam #3.3 646, and beam #3.4 648, and TRP #4 618 may be associated with UL-Rx beam #4.1 652, beam #4.2 654, beam #4.3 656, and beam #4.4 658.
[0081] The example in FIG. 6 shows four ROs (e.g., RO #1 682, RO #2 684, RO #3 686, RO #4 688) , each of these four ROs may be shared by four UL-Rx beams selected from all UL-only TRPs, and these four ROs may cover all UL-only TRP and their respective UL-Rx beams. For example, RO #1 682 is shared by four UL-Rx beams, including beam #1.1 622 from TRP #1 612, beam #2.1 632 from TRP #2 614, beam #3.1 642 from TRP #3 616, and beam #4.1 652 from TRP #4 618.
[0082] At a given UE location (e.g., UE location 662, 664, 666, or 668) , prior probabilities (also referred to as a-prior probabilities in some aspects) of using certain combinations of one of the four UL-Rx beams and one of the four UL-only TRPs may be identified as the most favorable (or the best) among all candidate UL-Rx beams across all UL-only TRPs. For example, at UE location 662, SSB #1 672 may be recommended to determine UL-Tx parameters for transmitting Msg 1 or Msg A. When using SSB #1 672 at UE location 662, the prior probabilities associated with selecting RO #1 682, RO #2 684, RO #3 686, RO #4 688 may be, for example, 5%, 45%, 40%, and 10%, respectively. For example, at UE location 664, SSB #2 674 may be recommended to determine UL-Tx parameters for transmitting Msg 1 or Msg A. When using SSB #2 674 at UE location 664, the prior probabilities associated with selecting RO #1 682, RO #2 684, RO #3 686, RO #4 688 may be, for example, 15%, 40%, 30%, and 15%, respectively. For example, at UE location 666, SSB #3 676 may be recommended to determine UL-Tx parameters for transmitting Msg 1 or Msg A. When using SSB #3 676 at UE location 666, the prior probabilities associated with selecting RO #1 682, RO #2 684, RO #3 686, RO #4 688 may be, for example, 15%, 30%, 40%, and 15%, respectively. For example, at UE location 668, SSB #4 678 may be recommended to determine UL-Tx parameters for transmitting Msg 1 or Msg A. When using SSB #4 678 at UE location 668, the prior probabilities associated with selecting RO #1 682, RO #2 684, RO #3 686, RO #4 688 may be, for example, 10%, 40%, 45%, and 5%, respectively.
[0083] Based on this information, the best combinations of UL-Rx beams and UL-only TRPs identified may include UL-Rx beam #1.1 622 at UL-only TRP #1 612, UL-Rx beam #1.2 624 at UL-only TRP #1 612, and UL-Rx beam #2.2 634 at UL-only TRP #2 614, with the associated probabilities of, for example, 75%, 12%, 5%, respectively.
[0084] Based on the identified combinations of the UL-Rx beams and UL-only TRPs, the UE may transmit toward the corresponding UL-only TRPs via UL-Tx beams associated with the above-identified UL-Rx beams. For example, the UE may transmit toward the UL-only TRP #1 612 via a UL-Tx beam associated with the UL-Rx beam #1.1 622, transmit toward the UL-only TRP #1 612 via a UL-Tx beam associated with the UL-Rx beam #1.2 624, and transmit toward the UL-only TRP #2 614 via a UL-Tx beam associated with the UL-Rx beam #2.2 634. In some examples, this determination may be based on certain downlink receive (DL-Rx) beams identified from the SSBs (e.g., SSB #1 672, SSB #2 674, SSB #3 676, SSB #4 678) transmitted by the DL+UL TRP (e.g., DL+UL TRP 610) .
[0085] For PRACH procedures, the network may signal an association that includes at least a certain location (e.g., UE location 662, 664, 666, 668) , the corresponding SSBs that the UE should use to identify its uplink transmission configuration indicator (TCI) states for transmitting Msg 1 or Msg A, and the RACH occasions or preambles associated with the identified UL TCI states or, equivalently, the corresponding SSBs.
[0086] In some aspects, the network may signal (e.g., via remaining minimum system information (RMSI) signaling) the UE relevant information for the UE to identify proper PRACH resource and UL-Tx beam. For example, the information may include the associations among several components, including a certain location identifier related to the UE’s location (e.g., UE location 662, 664, 666, 668) , a number of SSBs (e.g., SSB #1 672, SSB #2 674, SSB #3 676, SSB #4 678) , and a number of groups of ROs or preambles (e.g., RO #1 682, RO #2 684, RO #3 686, RO #4 688) that are associated with the UL-only TRPs (e.g., UL-only TRP #1 612, TRP #2 614, TRP #3 616, TRP #4 618) and are respectively mapped to the number of SSBs (e.g., SSB #1 672, SSB #2 674, SSB #3 676, SSB #4 678) . Based on the mapping between the number of groups of ROs or preambles and the SSBs (e.g., SSB #1 672, SSB #2 674, SSB #3 676, SSB #4 678) , when the UE transmits Msg 1 or Msg A through one of the ROs or preambles, the UE may determine the UL-Tx parameters based on the DL-Rx parameters identified for receiving the SSB that corresponds to the group of ROs or preambles. In some examples, the RMSI may also signal prior probability information regarding the respective groups of ROs or preambles and / or the SSBs. When the UE performs PRACH by transmitting Msg 1 or Msg A toward the UL-only TRPs, the UE may identify the RO or preamble and the corresponding UL-Tx parameters for transmitting Msg 1 or Msg A based on this information.
[0087] In some aspects, the associations among UE locations, SSBs, and ROs or preambles may be constructed in various ways. In one configuration, the association among UE locations, SSBs, and ROs or preambles may be constructed based on network implementation. In this method, the process begins by considering a certain fixed location across various UEs that are already in RRC CONNECTED mode with the cell. For a given UE, sounding reference signals (SRS) are scheduled, with their uplink transmission configuration indicator (UL-TCI) states associated with respective SSBs. The corresponding UL-Rx beams associated with the UL-only TRPs may be used to receive such SRS.
[0088] In some examples, among all candidate pairs including an SSB being considered as a certain SRS’s UL-TCI state and a certain UL-Rx beam with respect to an UL-only TRP, the best pairs that have the best signal quality, such as the best uplink reference signal received power (UL-RSRP) or uplink signal to interference plus noise ratio (UL-SINR) values are identified. In some examples, the observed probabilities associated with these best pairs may also be identified.
[0089] In some examples, the procedure of using the corresponding UL-Rx beams associated with the UL-only TRPs to receive SRS may be repeated for various UEs associated with the same fixed location, and the overall statistics may be calculated to identify the best pairs of SSB and UL-Rx beam combinations. In some examples, synthesized probabilities associated with these best pairs may be determined.
[0090] After the best pairs of SSB and UL-Rx beam combinations for a given location have been determined, the same process may be repeated across various locations. Based on the resulting data, the respective UL-Rx beams are mapped to certain ROs or preambles, and the network may signal the associations among UE locations, SSBs, and ROs or preambles through RMSI.
[0091] In another configuration, the association among UE locations, SSBs, and ROs or preambles may be constructed based on a UE-assisted method. In this method, the process begins by considering a certain UE associated with a fixed location. The UE is scheduled with SRS without mandated UL-TCI states. For each of these SRS, the UE reports one of the SSBs used to derive the UL-Tx parameters. The network then gathers this information across various locations and UEs to build the associations among UE locations, SSBs, and ROs or preambles, and subsequently signals such associations through RMSI.
[0092] In some aspects, a method for PRACH resource and uplink-transmit (UL-Tx) beam identification based on location and uplink pointing directions is provided. In some examples, at a certain location, the UL-Rx beam (s) that would be better used by UL-only TRPs for receiving, and thus the UE’s corresponding UL-Tx beam for transmitting, may be determined based on geographical and directional relationships. These relationships may involve the UE’s location, the UL-only TRP’s location, and the UL-Rx beams with respect to the UL-only TRPs. Compared to the method that is based on location and SSB, the method based on location and uplink pointing direction needs less over-the-air (OTA) data collection effort, as such information may be calculated without OTA data collection, making this method especially efficient and effective in environments that are line-of-sight (LoS) dominant.
[0093] FIG. 7 is a diagram 700 illustrating an example of a PRACH resource and UL-Tx beam identification method based on location and uplink pointing directions in accordance with various aspects of the present disclosure. As shown in FIG. 7, four UL-only TRPs (TRP #1 712, TRP #2 714, TRP #3 716, TRP #4 718) are available for PRACH procedures for a UE. Each of these four UL-only TRPs (TRP #1 712, TRP #2 714, TRP #3 716, TRP #4 718) may be associated with four UL-Rx beams. For example, TRP #1 712 may be associated with UL-Rx beam #1.1 722, beam #1.2 724, beam #1.3 726, and beam #1.4 728. TRP #2 714 may be associated with UL-Rx beam #2.1 732, beam #2.2 734, beam #2.3 736, and beam #2.4 738. TRP #3 716 may be associated with UL-Rx beam #3.1 742, beam #3.2 744, beam #3.3 746, and beam #3.4 748, and TRP #4 718 may be associated with UL-Rx beam #4.1 752, beam #4.2 754, beam #4.3 756, and beam #4.4 758.
[0094] The example in FIG. 7 shows four ROs (e.g., RO #1 782, RO #2 784, RO #3 786, RO #4 788) , each of these four ROs may be shared by four UL-Rx beams selected from all UL-only TRPs, and these four ROs may cover all UL-only TRPs and their respective UL-Rx beams. For example, RO #1 782 is shared by four UL-Rx beams, including beam #1.1 722 from TRP #1 712, beam #2.1 732 from TRP #2 714, beam #3.1 742 from TRP #3 716, and beam #4.1 752 from TRP #4 718.
[0095] For each location of various UE locations (e.g., UE location 762, 764, 766, 768) , the relative uplink transmit (UL-Tx) pointing directions, referenced to the center of the corresponding location, are signaled for the respective ROs with respect to Msg 1 or Msg A transmission. In some examples, prior probabilities corresponding to these UL-Tx pointing directions are also signaled.
[0096] In some aspects, the network may signal (e.g., via remaining minimum system information (RMSI) signaling) the UE relevant information for the UE to identify proper PRACH resource and UL-Tx beam. For example, the information may include the associations among several components, including a certain location identifier related to the UE’s location (e.g., UE location 762, 764, 766, 768) , a number of uplink transmit pointing directions (e.g., directions 770, 772 for UE location 662, directions 774, 776 for UE location 664, directions 778, 780 for UE location 666, and directions 790, 792 for UE location 668) , and a number of groups of ROs or preambles (e.g., RO #1 782, RO #2 784, RO #3 786, RO #4 788) that are associated with the UL-only TRPs (e.g., UL-only TRP #1 712, TRP #2 714, TRP #3 716, TRP #4 718) and are respectively mapped to the number of uplink transmit pointing directions (also referred to as uplink pointing directions in some aspects) . Based on the mapping between the number of groups of ROs or preambles and the uplink pointing directions, when the UE transmits Msg 1 or Msg A through one of the ROs or preambles, the UE may determine the UL-Tx parameters based on the associated uplink transmit pointing directions. In some examples, the RMSI may also include the location information of the UL-only TRPs associated with the respective groups of ROs or preambles. In some examples, the RMSI may include prior probability information on the respective groups of ROs or preambles or, equivalently, on the respective uplink transmit pointing directions. When the UE performs PRACH by transmitting Msg 1 or Msg A toward the UL-only TRPs, the UE may identify the RO or preamble and the corresponding UL-Tx parameters for transmitting Msg 1 or Msg A based on this information.
[0097] In some aspects, to facilitate the location-based methods to identify PRACH resource and UL-Tx parameter for UL-only TRPs, for various location identifiers, the RMSI may signal the association between a certain location identifier and a number of groups of ROs or preambles associated with the UL-only TRPs. These UL-only TRPs may be configured to receive uplink signals but cannot transmit downlink signals. When the UE performs PRACH by transmitting Msg 1 or Msg A toward the UL-only TRPs, the UE may identify the appropriate RO or preamble and the corresponding UL-Tx parameters for transmitting Msg 1 or Msg A based at least on this signaled information (e.g., the signaled association between the location identifier and the number of groups of ROs or preambles associated with the UL-only TRPs) .
[0098] In some aspects, the location-based PRACH resource and UL-Tx parameter identification methods may be based on the mapping between the number of groups of ROs or preambles and the SSBs (e.g., SSB #1 672, SSB #2 674, SSB #3 676, SSB #4 678) . In this case, the associations signaled by RMSI may include a certain location identifier (e.g., an identifier that identifies the UE location 662, 664, 666, or 668) , a set of SSBs, and a number of groups of ROs or preambles (e.g., RO #1 682, RO #2 684, RO #3 686, RO #4 688) that are associated with the UL-only TRPs (e.g., UL-only TRP #1 612, TRP #2 614, TRP #3 616, TRP #4 618) . These groups of ROs or preambles may be respectively mapped to the number of SSBs, such that when the UE transmits Msg 1 or Msg A through one of the ROs or preambles, the UE may determine the UL-Tx parameters based on the downlink receive parameters identified for receiving the SSB mapped to the associated group of ROs or preambles. In some examples, the RMSI may also signal prior probability information on the respective groups of ROs or preambles and / or the SSBs.
[0099] In some aspects, to facilitate the network in building the associations among UE locations, SSBs, and ROs or preambles, the UE may be scheduled with SRS without mandated UL-TCI states. The UE is expected to be requested to further report one SSB index for each SRS, where the reported SSB may be used to derive the UL-Tx parameters for the SRS.
[0100] In some aspects, the RMSI may signal prior probability information on the respective groups of ROs or preambles and / or the SSBs. In some examples, the prior probabilities may be signaled for the SSBs, but not for the respective groups of ROs or preambles. In this case, for a given location identifier, the prior probabilities may be provided for the respective SSBs. It may be up to the UE implementation to determine how to use the ROs or preambles associated with these SSBs. For example, the UE may attempt various Msg 1 or Msg A transmissions using the ROs or preambles corresponding to the respective SSBs, following a distribution based on the network-indicated prior probabilities for the SSBs.
[0101] In some examples, in addition to the prior probabilities for the SSBs, the RMSI may further signal the prior probabilities for the respective groups of ROs or preambles. In this case, multiple groups of ROs or preambles may be signaled as associated with the same SSB. For example, different groups of ROs or preambles may be associated with different network UL-Rx beams. For a given location identifier, the prior probabilities may be signaled for the respective groups of ROs or preambles that are all associated with the same SSB. In some examples, a single SSB may be signaled for a certain location identifier (e.g., when the network is certain that this SSB is appropriate for UL-Tx parameter determination at that specific location) . In such cases, various prior probabilities may still be signaled for the different ROs or preambles associated with that location, for example, when different UL-Rx beams from the UL-only TRP associated with those ROs or preambles further include different prior probabilities in a given location. It may be up to UE implementation to determine how to use the ROs or preambles associated with the SSBs. For example, the distribution based on the network-indicated prior probabilities for the SSBs may be refined to also consider the likelihoods of different groups of ROs or preambles, even if they are associated with the same SSB. In other words, even if the same UL-Tx beam is used for transmitting Msg 1 or Msg A, the UE may attempt transmissions using different ROs or preambles so that the network can receive them through different UL-Rx beams.
[0102] In some aspects, the location-based PRACH resource and UL-Tx parameter identification methods may be based on the mapping between the number of groups of ROs or preambles and the uplink transmit pointing directions (e.g., uplink pointing directions 770, 772, 774, 776, 778, 780, 790, 792) . In this case, the associations signaled by RMSI may include a certain location identifier (e.g., an identifier that identifies the UE location 762, 764, 766, or 768) , a number of UL-Tx pointing directions (e.g., uplink pointing directions 770, 772, 774, 776, 778, 780, 790, 792) , and a number of groups of ROs or preambles associated with the UL-only TRPs (e.g., UL-only TRP #1 712, TRP #2 714, TRP #3 716, TRP #4 718) . These groups of ROs or preambles may be respectively mapped to the UL-Tx pointing directions, such that when the UE transmits Msg 1 or Msg A through one of the ROs or preambles, the UE may determine the UL-Tx parameters based on the associated UL-Tx pointing direction. In some examples, the RMSI may also signal the location information of the UL-TRP associated with the respective groups of ROs or preambles. In some examples, the RMSI may also signal the prior probability information on the respective groups of ROs or preambles or, equivalently, on the respective UL-Tx pointing directions.
[0103] In some aspects, the uplink pointing directions (e.g., uplink pointing directions 770, 772, 774, 776, 778, 780, 790, 792) may be signaled based on a local coordinate system, where the reference point for each pointing direction may be the central location of the corresponding location identifier. In some examples, the uplink pointing directions themselves can be further defined using two components: a main direction and a certain angular range with respect to the main direction.
[0104] In some aspects, when signaling the location information of the UL-only TRP (e.g., UL-only TRP #1 712, TRP #2 714, TRP #3 716, TRP #4 718) , the location information of the UL-only TRP may be signaled via a global coordinate system. For example, the location information of the UL-only TRP may include global positioning system (GPS) coordinates of the UL-only TRP. In some examples, the location information of the UL-only TRP may be signaled using a local coordinate system, with a differential coordinate that refers to the central location of the corresponding location identifier.
[0105] In some aspects, using RMSI to signal the information for the identification of PRACH resource and UL-Tx parameters (e.g., the associated between the UE location, the SSBs (or the uplink pointing directions) , and the groups of ROs or preambles) may incur large signaling overhead (e.g., when the granularity of location information is high) , resulting in inefficiencies for payload-restricted RMSI.
[0106] To address this issue, in some aspects, the associations (e.g., the associated between the UE location, the SSBs (or the uplink pointing directions) may be identified and managed through another remote network entity or a cloud-based platform (e.g., a cloud server) . For example, the remote network entity or the cloud-based platform could be a new network entity associated with wireless communication (e.g., 6G communication) or a third-party entity. For example, the remote network entity or the cloud-based platform may be associated with various global cell identifiers (IDs) for wireless communication. In some examples, the UE may download or restore such an association table and use the information after identifying the global cell ID during the initial access phase.
[0107] In some examples, a hybrid approach using both RMSI and cloud-based solutions may be used to signal the information for the identification of PRACH resource and UL-Tx parameters (e.g., the associated between the UE location, the SSBs (or the uplink pointing directions) . In some examples, for the same global cell ID, the information signaled through RMSI and the cloud (e.g., a cloud server) may have different granularities on one or more of the components (e.g., the UE location, the SSBs (or the uplink pointing directions) , or the groups of ROs or preambles) among the associations. In some examples, the information signaled by RMSI may not include the prior probability information. In some examples, the information signaled by RMSI may be based on a coarser location identifier system compared to the information signaled by the cloud server. In some examples, the information signaled by RMSI may be limited to the information related to direction-based methods, while the information signaled by the cloud server may include information for the direction-based methods and SSB-based methods. This hybrid approach allows UE of different capabilities to retrieve or restore information based on their capabilities. For example, more capable UEs that are able to restore and utilize information downloaded from a cloud server can benefit from more efficient initial access due to access to richer prior probability information. On the other hand, lower-tier UEs that do not retrieve such cloud-based information can still operate effectively using the more limited but still useful data signaled through RMSI.
[0108] In some aspects, timing advance (TA) values may be provided for the groups of ROs or preambles to facilitate the UE to identify PRACH resource and UL-Tx beam. In some examples, each group of ROs or preambles may be further signaled with a TA value. For example, this TA value may refer to the timing estimated from the SSB that is associated with the corresponding group of ROs or preambles. In some examples, each group of ROs or preambles (or equivalently, each UL-Tx pointing direction) may be signaled with a TA value. In this case, the TA may be based on the timing estimated from certain SSBs transmitted by the DL+UL TRP.
[0109] In some aspects, the methods to identify PRACH resource and UL-Tx beam are applicable to UEs in the RRC CONNECTED state. In some aspects, to reduce the uplink transmit beam sweeping efforts for UEs in the RRC CONNECTED state and to refine their UL-Tx beams on UL-only TRPs, the information that is signaled through RMSI or the cloud server (e.g., the association among UE locations, SSBs (or uplink pointing directions) , and ROs or preambles) may alternatively be signaled directly from the network via RRC signaling, medium access control (MAC) –control elements (MAC-CE) , or downlink control information (DCI) .
[0110] FIG. 8 is a diagram 800 illustrating another example of a PRACH resource and UL-Tx beam identification method in accordance with various aspects of the present disclosure. As shown in FIG. 8, four UL-only TRPs (TRP #1 812, TRP #2 814, TRP #3 816, TRP #4 818) are available for PRACH procedures for a UE 802. FIG. 8 also shows a DL TRP (or DL+UL TRP) 804.
[0111] As shown in FIG. 8, various location zones (e.g., zone #1 832, zone #2 834, zone #3 836) may be either predefined or signaled through RMSI or the cloud server for the considered cell. For example, these zones (e.g., zone #1 832, zone #2 834, zone #3 836) may be defined based on a global coordinate system, including parameters such as the center of the zone, the radius or coverage area of the zone, and the identifier of the zone. In some examples, the zones (e.g., zone #1 832, zone #2 834, zone #3 836) may be determined based on the RSRPs of the SSBs measured by the UE (e.g., UE 802) .
[0112] In some aspects, to reduce the PRACH beam sweep for initial access by RRC IDLE UEs via UL-only UL-TRPs (e.g., UL-only TRP #1 812, TRP #2 814, TRP #3 816, TRP #4 818) , the cloud server or the network may provide a priority list of recommended ROs or preambles for each zone. These ROs or preambles correspond to different UL-Rx beams at the UL-TRPs. For example, in FIG. 8, RO #1 822 of TRP #4 818 is a recommended RO for zone #1 832, RO #2 824 of TRP #4 818 is a recommended RO for zone #2 834, and RO #3 826 of TRP #4 818 is a recommended RO for zone #3 836.
[0113] In some examples, for each RO or preamble, the cloud server or the network may provide a priority list of recommended uplink pointing directions for the UE’s UL transmit beam.
[0114] In some examples, to reduce the PRACH beam sweep range for UEs in RRC CONNECTED state to refine their UL-Tx beams on UL-TRPs, the cloud server or the network may provide a priority list of recommended UL-Tx beam directions for each zone (e.g., zone #1 832, zone #2 834, zone #3 836) . In some examples, these directions may include a main direction and an associated angular range with respect to the main direction.
[0115] In some examples, the specific RO and UE UL-Tx beam direction to be used may be determined based on the UE’s location zone, which may be derived either from the UE’s position information or from the RSRPs of SSBs. For example, the RMSI may inform the UE to select RO #1 822 and to use a transmit beam with an absolute direction defined by the angles of, for example, {θ, α} if the strongest SSB is the SSB corresponding to RO #1 822 and its RSRP falls within a predefined range (e.g., a range of -80 to -90 dBm) .
[0116] FIG. 9 is a call flow diagram 900 illustrating a method of wireless communication in accordance with various aspects of this present disclosure. Various aspects are described in connection with a UE 902 and a base station 904. The aspects may be performed by the UE 902 or the base station 904 in aggregation and / or by one or more components of a base station 904 (e.g., a CU 110, a DU 130, and / or an RU 140) . In some examples, base station 904 may be associated with one or more UL-only TRP (e.g., UL-only TRP 906) .
[0117] As shown in FIG. 9, at 920, the UE 902 may receive system information from base station 904. For example, the system information may include one or more location identifiers and a first number of groups of ROs or preambles associated with a second number of uplink nodes of a network entity. In some examples, the system information may further include prior probability information (e.g., prior probabilities) for the third number of SSBs.
[0118] At 922, the UE 902 may transmit a first set of first messages associated with the random access procedure using a second set of ROs or preambles with corresponding SSBs based on a distribution. For example, the distribution may be based on at least the set of first prior probabilities for the third number of SSBs.
[0119] At 924, the UE 902 may receive resources for a set of SRS from base station 904.
[0120] At 926, the UE 902 may report an index for one SSB in the third number of SSB for each SRS in the set of SRS. The one SSB may be associated with the uplink transmission parameters for each SRS in the set of SRS.
[0121] At 928, the UE 902 may determine the uplink transmission parameters based on downlink reception parameters for the reception of one SSB of the third number of SSBs. In some examples, the one SSB may map to the corresponding RO or preamble. In some examples, the uplink transmission parameters may include an uplink transmission beam. For example, the uplink transmission beam may be one beam (e.g., beam 916) among uplink transmission beams 912, 914, 916, or 918. In some examples, the uplink transmission beam (e.g., beam 916) may be used to transmit the first message (e.g., Msg 1 or Msg A) for a PRACH procedure with base station 904 (e.g., at 934) .
[0122] At 930, the UE 902 may determine the uplink transmission parameters based on one uplink pointing direction of the fourth number of uplink pointing directions. The one uplink pointing direction may be associated with the corresponding RO or preamble. For example, the uplink transmission beam may be one beam (e.g., beam 916) among uplink transmission beams 912, 914, 916, or 918. In some examples, the uplink transmission beam (e.g., beam 916) may be used to transmit the first message (e.g., Msg 1 or Msg A) for a PRACH procedure with base station 904 (e.g., at 934) .
[0123] At 932, the UE 902 may transmit, to one uplink node (e.g., UL-only TRP 906) of the second number of uplink nodes, a first message associated with a random access procedure using uplink transmission parameters. The uplink transmission parameters are based on the system information (e.g., at 920) . In some examples, the uplink transmission parameters may include an uplink transmission beam (e.g., beam 916) for transmitting the first message. For example, the first message may be Msg 1 at 403 or Msg A at 411.
[0124] At 934, the UE 902 and base station 904 may perform the random access procedure with the network entity based on the first message (e.g., at 932) .
[0125] FIG. 10 is a flowchart 1000 illustrating methods of wireless communication at a UE in accordance with various aspects of the present disclosure. The method may be performed by a UE in collaboration with a network entity. The network entity may be a base station, or a component of a base station, in the access network of FIG. 1 or a core network component (e.g., base station 102, 310, 904; or the network entity 1302 in the hardware implementation of FIG. 13) . In some examples, the network entity may be associated with one or more UL-only TRPs, such as UL-only TRP #1 612, TRP #2 614, TRP #3 616, TRP #4 618. The UE may be the UE 104, 350, 802, 902, or the apparatus 1304 in the hardware implementation of FIG. 13. By associating UE locations with SSBs and ROs or preambles, or by incorporating location-based beam identification with system broadcast information (e.g., RMSI) , the methods allow UE to determine appropriate PRACH resources and UL-Tx beam directions for Msg 1 or Msg A transmission for UL-only TRPs, thereby improving PRACH coverage and reducing latency. Additionally, by using prior probability signaling for SSBs or ROs / preambles, the methods enable the network to guide UEs with probabilistic weighting toward the most effective access configurations, thereby improving beam selection accuracy and reducing the need for beam sweeping.
[0126] As shown in FIG. 10, at 1002, the UE may receive system information. The system information may include one or more location identifiers and a first number of groups of random access channel (RACH) occasions (ROs) or preambles associated with a second number of uplink nodes of a network entity. The uplink nodes may be dedicated for uplink transmission. FIG. 6, FIG. 7, FIG. 8, and FIG. 9 illustrate various aspects of the steps in connection with flowchart 1000. For example, referring to FIG. 6 and FIG. 9, the UE 902 may, at 920, receive system information. The system information may include one or more location identifiers (e.g., identifiers identifying UE location 662, 664, 666, or 668) and a first number of groups of ROs or preambles (e.g., RO #1 682, RO #2 684, RO #3 686, RO #4 688) associated with a second number of uplink nodes (e.g., UL-only TRP #1 612, TRP #2 614, TRP #3 616, TRP #4 618) of a network entity. The uplink nodes (e.g., UL-only TRP #1 612, TRP #2 614, TRP #3 616, TRP #4 618) may be dedicated for uplink transmission. In some aspects, 1002 may be performed by the PRACH component 198.
[0127] At 1004, the UE may transmit, to one uplink node of the second number of uplink nodes, a first message associated with a random access procedure using uplink transmission parameters. The uplink transmission parameters may be based on the system information. For example, referring to FIG. 9, the UE 902 may, at 932, transmit, to one uplink node (e.g., UL-only TRP 906) of the second number of uplink nodes, a first message associated with a random access procedure using uplink transmission parameters. The uplink transmission parameters may be based on the system information. In some aspects, 1004 may be performed by the PRACH component 198.
[0128] At 1006, the UE may perform the random access procedure with the network entity based on the first message. For example, referring to FIG. 9, the UE 902 may, at 934, perform the random access procedure with the network entity (e.g., base station 904) based on the first message. In some aspects, 1006 may be performed by the PRACH component 198.
[0129] FIG. 11 is a flowchart 1100 illustrating methods of wireless communication at a UE in accordance with various aspects of the present disclosure. The method may be performed by a UE in collaboration with a network entity. The network entity may be a base station, or a component of a base station, in the access network of FIG. 1 or a core network component (e.g., base station 102, 310, 904; or the network entity 1302 in the hardware implementation of FIG. 13) . In some examples, the network entity may be associated with one or more UL-only TRPs, such as UL-only TRP #1 612, TRP #2 614, TRP #3 616, TRP #4 618. The UE may be the UE 104, 350, 802, 902, or the apparatus 1304 in the hardware implementation of FIG. 13. By associating UE locations with SSBs and ROs or preambles, or by incorporating location-based beam identification with system broadcast information (e.g., RMSI) , the methods allow UE to determine appropriate PRACH resources and UL-Tx beam directions for Msg 1 or Msg A transmission for UL-only TRPs, thereby improving PRACH coverage and reducing latency. Additionally, by using prior probability signaling for SSBs or ROs / preambles, the methods enable the network to guide UEs with probabilistic weighting toward the most effective access configurations, thereby improving beam selection accuracy and reducing the need for beam sweeping.
[0130] As shown in FIG. 11, at 1102, the UE may receive system information. The system information may include one or more location identifiers and a first number of groups of ROs or preambles associated with a second number of uplink nodes of a network entity. The uplink nodes may be dedicated for uplink transmission. FIG. 6, FIG. 7, FIG. 8, and FIG. 9 illustrate various aspects of the steps in connection with flowchart 1100. For example, referring to FIG. 6 and FIG. 9, the UE 902 may, at 920, receive system information. The system information may include one or more location identifiers (e.g., identifiers identifying UE location 662, 664, 666, or 668) and a first number of groups of ROs or preambles (e.g., RO #1 682, RO #2 684, RO #3 686, RO #4 688) associated with a second number of uplink nodes (e.g., UL-only TRP #1 612, TRP #2 614, TRP #3 616, TRP #4 618) of a network entity. The uplink nodes (e.g., UL-only TRP #1 612, TRP #2 614, TRP #3 616, TRP #4 618) may be dedicated for uplink transmission. In some aspects, 1102 may be performed by the PRACH component 198.
[0131] At 1114, the UE may transmit, to one uplink node of the second number of uplink nodes, a first message associated with a random access procedure using uplink transmission parameters. The uplink transmission parameters may be based on the system information. For example, referring to FIG. 9, the UE 902 may, at 932, transmit, to one uplink node (e.g., UL-only TRP 906) of the second number of uplink nodes, a first message associated with a random access procedure using uplink transmission parameters. The uplink transmission parameters may be based on the system information. In some aspects, 1114 may be performed by the PRACH component 198.
[0132] At 1116, the UE may perform the random access procedure with the network entity based on the first message. For example, referring to FIG. 9, the UE 902 may, at 934, perform the random access procedure with the network entity (e.g., base station 904) based on the first message. In some aspects, 1116 may be performed by the PRACH component 198.
[0133] In some aspects, the uplink transmission parameters may include an uplink transmission beam for the transmission of the first message. The UE may transmit the first message (e.g., at 1114) via the uplink transmission beam through a corresponding RO or preamble of the first number of groups of ROs or preambles. For example, referring to FIG. 9, the uplink transmission parameters may include an uplink transmission beam (e.g., beam 916) for the transmission of the first message (e.g., at 932) . The UE 902 may transmit the first message (e.g., at 932) via the uplink transmission beam (e.g., beam 916) through a corresponding RO or preamble of the first number of groups of ROs or preambles. In some aspects, 1014 may be performed by the PRACH component 198.
[0134] In some aspects, the system information may further include a third number of SSBs. The first number of groups of ROs or preambles may be respectively mapped to the third number of SSBs. At 1110, the UE may determine the uplink transmission parameters based on downlink reception parameters for the reception of one SSB of the third number of SSBs. The one SSB may map to the corresponding RO or preamble. For example, referring to FIG. 6, the system information may further include a third number of SSBs (e.g., SSB #1 672, SSB #2 674, SSB #3 676, SSB #4 678) . The first number of groups of ROs or preambles may be respectively mapped to the third number of SSBs. At 928, the UE may determine the uplink transmission parameters based on downlink reception parameters for the reception of one SSB of the third number of SSBs (e.g., SSB #1 672, SSB #2 674, SSB #3 676, SSB #4 678) . The one SSB may map to the corresponding RO (e.g., RO #1 682, RO #2 684, RO #3 686, RO #4 688) or preamble. In some aspects, 1110 may be performed by the PRACH component 198.
[0135] In some aspects, the system information may further include prior probability information for the third number of SSBs. For example, referring to FIG. 9, the system information (e.g., at 920) may further include prior probability information for the third number of SSBs (e.g., SSB #1 672, SSB #2 674, SSB #3 676, SSB #4 678) .
[0136] In some aspects, the prior probability information may include a set of first prior probabilities for the third number of SSBs. At 1104, the UE may transmit a first set of first messages associated with the random access procedure using a second set of ROs or preambles with corresponding SSBs based on a distribution. The distribution is based on at least the set of first prior probabilities for the third number of SSBs. For example, referring to FIG. 6, the prior probability information may include a set of first prior probabilities for the third number of SSBs (e.g., SSB #1 672, SSB #2 674, SSB #3 676, SSB #4 678) . Referring to FIG. 9, at 922, the UE 902 may transmit a first set of first messages associated with the random access procedure using a second set of ROs or preambles with corresponding SSBs based on a distribution. The distribution is based on at least the set of first prior probabilities for the third number of SSBs (e.g., SSB #1 672, SSB #2 674, SSB #3 676, SSB #4 678) . In some aspects, 1104 may be performed by the PRACH component 198.
[0137] In some aspects, the prior probability information may further include a set of second prior probabilities for the first number of groups of ROs or preambles. For example, referring to FIG. 6, the prior probability information may further include a set of second prior probabilities for the first number of groups of ROs (e.g., RO #1 682, RO #2 684, RO #3 686, RO #4 688) or preambles.
[0138] In some aspects, the distribution may be further based on the set of second prior probabilities for the first number of groups of ROs or preambles. For example, referring to FIG. 6, the distribution may be further based on the set of second prior probabilities for the first number of groups of ROs (e.g., RO #1 682, RO #2 684, RO #3 686, RO #4 688) or preambles.
[0139] In some aspects, at 1106, the UE may receive resources for a set of sounding reference signals (SRS) . At 1108, the UE may report an index for one SSB in the third number of SSB for each SRS in the set of SRS. The one SSB may be associated with the uplink transmission parameters for each SRS in the set of SRS. For example, referring to FIG. 9, at 924, the UE 902 may receive resources for a set of SRS. At 926, the UE 902 may report an index for one SSB in the third number of SSB for each SRS in the set of SRS. The one SSB may be associated with the uplink transmission parameters for each SRS in the set of SRS. In some aspects, 1106 and 1108 may be performed by the PRACH component 198.
[0140] In some aspects, the system information may further include a timing advance (TA) value for each group of ROs or preambles in the first number of groups of ROs or preambles. The TA value for a group of ROs or preambles may be based on the SSB associated with each group of ROs or preambles. For example, referring to FIG. 9, the system information (e.g., at 920) may further include a TA value for each group of ROs or preambles in the first number of groups of ROs or preambles. The TA value for a group of ROs or preambles may be based on the SSB (e.g., SSB #1 672, SSB #2 674, SSB #3 676, SSB #4 678) associated with each group of ROs (e.g., RO #1 682, RO #2 684, RO #3 686, RO #4 688) or preambles.
[0141] In some aspects, the system information may further include a fourth number of uplink pointing directions. The first number of groups of ROs or preambles may be respectively mapped to the fourth number of uplink pointing directions. At 1112, the UE may determine the uplink transmission parameters based on one uplink pointing direction of the fourth number of uplink pointing directions. The one uplink pointing direction may be associated with the corresponding RO or preamble. For example, referring to FIG. 7 and FIG. 9, the system information (e.g., at 920) may further include a fourth number of uplink pointing directions (e.g., uplink pointing direction 770, 772, 774, 776, 778, 780, 790, 792) . The first number of groups of ROs (e.g., RO #1 782, RO #2 784, RO #3 786, RO #4 788) or preambles may be respectively mapped to the fourth number of uplink pointing directions (e.g., uplink pointing direction 770, 772, 774, 776, 778, 780, 790, 792) . At 930, the UE 902 may determine the uplink transmission parameters based on one uplink pointing direction of the fourth number of uplink pointing directions. The one uplink pointing direction may be associated with the corresponding RO or preamble. In some aspects, 1112 may be performed by the PRACH component 198.
[0142] In some aspects, the system information may further include one or more of: location information for the second number of uplink nodes, or prior probability information for the fourth number of uplink pointing directions. For example, referring to FIG. 9, the system information (e.g., at 920) may further include one or more of: location information for the second number of uplink nodes (e.g., UL-only TRP #1 712, TRP #2 714, TRP #3 716, TRP #4 718) , or prior probability information for the fourth number of uplink pointing directions.
[0143] In some aspects, the location information for the second number of uplink nodes may be based on a global coordinate system. For example, referring to FIG. 7, the location information for the second number of uplink nodes (e.g., UL-only TRP #1 712, TRP #2 714, TRP #3 716, TRP #4 718) may be based on a global coordinate system.
[0144] In some aspects, the location information for the second number of uplink nodes may be based on a center location of a corresponding location identifier and a set of differential coordinates respectively corresponding to the second number of uplink nodes. For example, referring to FIG. 7, the location information for the second number of uplink nodes (e.g., UL-only TRP #1 712, TRP #2 714, TRP #3 716, TRP #4 718) may be based on a center location of a corresponding location identifier and a set of differential coordinates respectively corresponding to the second number of uplink nodes (e.g., UL-only TRP #1 712, TRP #2 714, TRP #3 716, TRP #4 718) .
[0145] In some aspects, the fourth number of uplink pointing directions may be based on a local coordination system. The reference point of one uplink pointing direction of the fourth number of uplink pointing directions may be the center location of a corresponding location identifier. For example, referring to FIG. 7, the fourth number of uplink pointing directions (e.g., uplink pointing direction 770, 772, 774, 776, 778, 780, 790, 792) may be based on a local coordination system. The reference point of one uplink pointing direction of the fourth number of uplink pointing directions may be the center location of a corresponding location identifier.
[0146] In some aspects, the fourth number of uplink pointing directions may be based on a main direction and a set of angular ranges. For example, referring to FIG. 7, the fourth number of uplink pointing directions (e.g., uplink pointing direction 770, 772, 774, 776, 778, 780, 790, 792) may be based on a main direction and a set of angular ranges.
[0147] In some aspects, the system information may further include a TA value for each group of ROs or preambles in the first number of groups of ROs or preambles. The TA value for a group of ROs or preambles may be based on one or more SSBs from an uplink-downlink node of the network entity. For example, referring to FIG. 9, the system information (e.g., at 920) may further include a TA value for each group of ROs or preambles in the first number of groups of ROs or preambles. The TA value for a group of ROs or preambles may be based on one or more SSBs from an uplink-downlink node of the network entity.
[0148] In some aspects, to receive the system information (e.g., at 1102) , the UE may receive the system information from one or more of: remaining minimum system information (RMSI) from the network entity, a cloud server, or a second entity different from the network entity. For example, referring to FIG. 9, the UE 902 may, at 920, receive the system information from one or more of: RMSI from the network entity (e.g., base station 904) , a cloud server, or a second entity different from the network entity.
[0149] In some aspects, the system information may include a fourth number of uplink pointing directions mapped to the first number of groups of ROs or preambles and prior probability information for the fourth number of uplink pointing directions. To receive the system information (e.g., at 1102) , the UE may receive, from the RMSI, the fourth number of uplink pointing directions; and receive, from the cloud server, the prior probability information for the fourth number of uplink pointing directions. For example, referring to FIG. 9, the system information (e.g., at 920) may include a fourth number of uplink pointing directions mapped to the first number of groups of ROs or preambles and prior probability information for the fourth number of uplink pointing directions. To receive the system information (e.g., at 920) , the UE 902 may receive, from the RMSI, the fourth number of uplink pointing directions; and receive, from the cloud server, the prior probability information for the fourth number of uplink pointing directions.
[0150] FIG. 12 is a flowchart 1200 illustrating methods of wireless communication at a network entity in accordance with various aspects of the present disclosure. The method may be performed by a network entity in collaboration with a UE. The network entity may be a base station, or a component of a base station, in the access network of FIG. 1 or a core network component (e.g., base station 102, 310, 904; or the network entity 1302 in the hardware implementation of FIG. 13) . In some examples, the network entity may be associated with one or more UL-only TRPs, such as UL-only TRP #1 612, TRP #2 614, TRP #3 616, TRP #4 618. The UE may be the UE 104, 350, 802, 902, or the apparatus 1304 in the hardware implementation of FIG. 13. By associating UE locations with SSBs and ROs or preambles, or by incorporating location-based beam identification with system broadcast information (e.g., RMSI) , the methods allow UE to determine appropriate PRACH resources and UL-Tx beam directions for Msg 1 or Msg A transmission for UL-only TRPs, thereby improving PRACH coverage and reducing latency. Additionally, by using prior probability signaling for SSBs or ROs / preambles, the methods enable the network to guide UEs with probabilistic weighting toward the most effective access configurations, thereby improving beam selection accuracy and reducing the need for beam sweeping.
[0151] As shown in FIG. 12, at 1202, the network entity may transmit system information to a UE. The system information may include one or more location identifiers and a first number of groups of ROs or preambles associated with a second number of uplink nodes of the network entity. The uplink nodes may be dedicated for uplink transmission. FIG. 6, FIG. 7, FIG. 8, and FIG. 9 illustrate various aspects of the steps in connection with flowchart 1200. For example, referring to FIG. 9, the network entity (e.g., base station 904) may, at 920, transmit system information to UE 902. The system information may include one or more location identifiers and a first number of groups of ROs or preambles associated with a second number of uplink nodes of the network entity. The uplink nodes may be dedicated for uplink transmission. In some aspects, 1202 may be performed by the PRACH component 199.
[0152] At 1204, the network entity may receive, via one uplink node of the second number of uplink nodes, a first message associated with a random access procedure using uplink transmission parameters. The uplink transmission parameters are based on the system information. For example, referring to FIG. 9, the network entity (e.g., base station 904) may, at 932, receive, via one uplink node (e.g., UL-only TRP 906) of the second number of uplink nodes, a first message associated with a random access procedure using uplink transmission parameters. The uplink transmission parameters are based on the system information. In some aspects, 1204 may be performed by the PRACH component 199.
[0153] At 1206, the network entity may perform the random access procedure with the UE based on the first message. For example, referring to FIG. 9, the network entity (e.g., base station 904) may, at 934, perform the random access procedure with the UE 902 based on the first message. In some aspects, 1206 may be performed by the PRACH component 199.
[0154] FIG. 13 is a diagram 1300 illustrating an example of a hardware implementation for an apparatus 1304. The apparatus 1304 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus 1304 may include at least one cellular baseband processor (or processing circuitry) 1324 (also referred to as a modem) coupled to one or more transceivers 1322 (e.g., cellular RF transceiver) . The cellular baseband processor (s) (or processing circuitry) 1324 may include at least one on-chip memory (or memory circuitry) 1324'. In some aspects, the apparatus 1304 may further include one or more subscriber identity modules (SIM) cards 1320 and at least one application processor (or processing circuitry) 1306 coupled to a secure digital (SD) card 1308 and a screen 1310. The application processor (s) (or processing circuitry) 1306 may include on-chip memory (or memory circuitry) 1306'. In some aspects, the apparatus 1304 may further include a Bluetooth module 1312, a WLAN module 1314, an SPS module 1316 (e.g., GNSS module) , one or more sensor modules 1318 (e.g., barometric pressure sensor / altimeter; motion sensor such as inertial measurement unit (IMU) , gyroscope, and / or accelerometer (s) ; magnetometer, audio and / or other technologies used for positioning) , additional memory modules 1326, a power supply 1330, and / or a camera 1332. The Bluetooth module 1312, the WLAN module 1314, and the SPS module 1316 may include an on-chip transceiver (TRX) (or in some cases, just a receiver (RX) ) . The Bluetooth module 1312, the WLAN module 1314, and the SPS module 1316 may include their own dedicated antennas and / or utilize the antennas 1380 for communication. The cellular baseband processor (s) (or processing circuitry) 1324 communicates through the transceiver (s) 1322 via one or more antennas 1380 with the UE 104 and / or with an RU associated with a network entity 1302. The cellular baseband processor (s) (or processing circuitry) 1324 and the application processor (s) (or processing circuitry) 1306 may each include a computer-readable medium / memory (or memory circuitry) 1324', 1306', respectively. The additional memory modules 1326 may also be considered a computer-readable medium / memory (or memory circuitry) . Each computer-readable medium / memory (or memory circuitry) 1324', 1306', 1326 may be non-transitory. The cellular baseband processor (s) (or processing circuitry) 1324 and the application processor (s) (or processing circuitry) 1306 are each responsible for general processing, including the execution of software stored on the computer-readable medium / memory (or memory circuitry) . The software, when executed by the cellular baseband processor (s) (or processing circuitry) 1324 / application processor (s) (or processing circuitry) 1306, causes the cellular baseband processor (s) (or processing circuitry) 1324 / application processor (s) (or processing circuitry) 1306 to perform the various functions described supra. The cellular baseband processor (s) (or processing circuitry) 1324 and the application processor (s) (or processing circuitry) 1306 are configured to perform the various functions described supra based at least in part of the information stored in the memory (or memory circuitry) . That is, the cellular baseband processor (s) (or processing circuitry) 1324 and the application processor (s) (or processing circuitry) 1306 may be configured to perform a first subset of the various functions described supra without information stored in the memory and may be configured to perform a second subset of the various functions described supra based on the information stored in the memory. The computer-readable medium / memory (or memory circuitry) may also be used for storing data that is manipulated by the cellular baseband processor (s) (or processing circuitry) 1324 / application processor (s) (or processing circuitry) 1306 when executing software. The cellular baseband processor (s) (or processing circuitry) 1324 / application processor (s) (or processing circuitry) 1306 may be a component of the UE 350 and may include the at least one memory 360 and / or at least one of the TX processor 368, the RX processor 356, and the controller / processor 359. In one configuration, the apparatus 1304 may be at least one processor chip (modem and / or application) and include just the cellular baseband processor (s) (or processing circuitry) 1324 and / or the application processor (s) (or processing circuitry) 1306, and in another configuration, the apparatus 1304 may be the entire UE (e.g., see UE 350 of FIG. 3) and include the additional modules of the apparatus 1304.
[0155] As discussed supra, the component 198 may be configured to receive system information, where the system information includes one or more location identifiers and a first number of groups of ROs or preambles associated with a second number of uplink nodes of a network entity, where the uplink nodes are dedicated for uplink transmission; transmit, to one uplink node of the second number of uplink nodes, a first message associated with a random access procedure using uplink transmission parameters, where the uplink transmission parameters are based on the system information; and perform the random access procedure with the network entity based on the first message. The component 198 may be further configured to perform any of the aspects described in connection with the flowcharts in FIG. 10 and FIG. 11, and / or performed by the UE 902 in FIG. 9. The component 198 may be within the cellular baseband processor (s) (or processing circuitry) 1324, the application processor (s) (or processing circuitry) 1306, or both the cellular baseband processor (s) (or processing circuitry) 1324 and the application processor (s) (or processing circuitry) 1306. The component 198 may be one or more hardware components specifically configured to carry out the stated processes / algorithm, implemented by one or more processors configured to perform the stated processes / algorithm, stored within a computer-readable medium for implementation by one or more processors, or some combination thereof. When multiple processors are implemented, the multiple processors may perform the stated processes / algorithm individually or in combination. As shown, the apparatus 1304 may include a variety of components configured for various functions. In one configuration, the apparatus 1304, and in particular the cellular baseband processor (s) (or processing circuitry) 1324 and / or the application processor (s) (or processing circuitry) 1306, includes means for receiving system information, where the system information includes one or more location identifiers and a first number of groups of ROs or preambles associated with a second number of uplink nodes of a network entity, where the uplink nodes are dedicated for uplink transmission; means for transmitting, to one uplink node of the second number of uplink nodes, a first message associated with a random access procedure using uplink transmission parameters, where the uplink transmission parameters are based on the system information; and means for performing the random access procedure with the network entity based on the first message. The apparatus 1304 may further include means for performing any of the aspects described in connection with the flowcharts in FIG. 10 and FIG. 11, and / or aspects performed by the UE 902 in FIG. 9. The means may be the component 198 of the apparatus 1304 configured to perform the functions recited by the means. As described supra, the apparatus 1304 may include the TX processor 368, the RX processor 356, and the controller / processor 359. As such, in one configuration, the means may be the TX processor 368, the RX processor 356, and / or the controller / processor 359 configured to perform the functions recited by the means.
[0156] FIG. 14 is a diagram 1400 illustrating an example of a hardware implementation for a network entity 1402. The network entity 1402 may be a BS, a component of a BS, or may implement BS functionality. The network entity 1402 may include at least one of a CU 1410, a DU 1430, or an RU 1440. For example, depending on the layer functionality handled by the component 199, the network entity 1402 may include the CU 1410; both the CU 1410 and the DU 1430; each of the CU 1410, the DU 1430, and the RU 1440; the DU 1430; both the DU 1430 and the RU 1440; or the RU 1440. The CU 1410 may include at least one CU processor (or processing circuitry) 1412. The CU processor (s) (or processing circuitry) 1412 may include on-chip memory (or memory circuitry) 1412'. In some aspects, the CU 1410 may further include additional memory modules 1414 and a communications interface 1418. The CU 1410 communicates with the DU 1430 through a midhaul link, such as an F1 interface. The DU 1430 may include at least one DU processor (or processing circuitry) 1432. The DU processor (s) (or processing circuitry) 1432 may include on-chip memory (or memory circuitry) 1432'. In some aspects, the DU 1430 may further include additional memory modules 1434 and a communications interface 1438. The DU 1430 communicates with the RU 1440 through a fronthaul link. The RU 1440 may include at least one RU processor (or processing circuitry) 1442. The RU processor (s) (or processing circuitry) 1442 may include on-chip memory (or memory circuitry) 1442'. In some aspects, the RU 1440 may further include additional memory modules 1444, one or more transceivers 1446, antennas 1480, and a communications interface 1448. The RU 1440 communicates with the UE 104. The on-chip memory (or memory circuitry) 1412', 1432', 1442'a nd the additional memory modules 1414, 1434, 1444 may each be considered a computer-readable medium / memory (or memory circuitry) . Each computer-readable medium / memory (or memory circuitry) may be non-transitory. Each of the processors (or processing circuitry) 1412, 1432, 1442 is responsible for general processing, including the execution of software stored on the computer-readable medium / memory (or memory circuitry) . The software, when executed by the corresponding processor (s) (or processing circuitry) causes the processor (s) (or processing circuitry) to perform the various functions described supra. The computer-readable medium / memory (or memory circuitry) may also be used for storing data that is manipulated by the processor (s) (or processing circuitry) when executing software.
[0157] As discussed supra, the component 199 may be configured to transmit, to a UE, system information, where the system information includes one or more location identifiers and a first number of groups of ROs or preambles associated with a second number of uplink nodes of the network entity, where the uplink nodes are dedicated for uplink transmission; receive, via one uplink node of the second number of uplink nodes, a first message associated with a random access procedure using uplink transmission parameters, where the uplink transmission parameters are based on the system information; and perform the random access procedure with the UE based on the first message. The component 199 may be further configured to perform any of the aspects described in connection with the flowchart in FIG. 12, and / or performed by the base station 904 in FIG. 9. The component 199 may be within one or more processors (or processing circuitry) of one or more of the CU 1410, DU 1430, and the RU 1440. The component 199 may be one or more hardware components specifically configured to carry out the stated processes / algorithm, implemented by one or more processors configured to perform the stated processes / algorithm, stored within a computer-readable medium for implementation by one or more processors, or some combination thereof. When multiple processors are implemented, the multiple processors may perform the stated processes / algorithm individually or in combination. The network entity 1402 may include a variety of components configured for various functions. In one configuration, the network entity 1402 includes means for transmitting, to a UE, system information, where the system information includes one or more location identifiers and a first number of groups of ROs or preambles associated with a second number of uplink nodes of the network entity, where the uplink nodes are dedicated for uplink transmission; means for receiving, via one uplink node of the second number of uplink nodes, a first message associated with a random access procedure using uplink transmission parameters, where the uplink transmission parameters are based on the system information; and means for performing the random access procedure with the UE based on the first message. The network entity 1402 may further include means for performing any of the aspects described in connection with the flowchart in FIG. 12, and / or aspects performed by the base station 904 in FIG. 9. The means may be the component 199 of the network entity 1402 configured to perform the functions recited by the means. As described supra, the network entity 1402 may include the TX processor 316, the RX processor 370, and the controller / processor 375. As such, in one configuration, the means may be the TX processor 316, the RX processor 370, and / or the controller / processor 375 configured to perform the functions recited by the means.
[0158] This disclosure provides a method for wireless communication at a UE. The method may include receiving system information, where the system information includes one or more location identifiers and a first number of groups of ROs or preambles associated with a second number of uplink nodes of a network entity, where the uplink nodes are dedicated for uplink transmission; transmitting, to one uplink node of the second number of uplink nodes, a first message associated with a random access procedure using uplink transmission parameters, where the uplink transmission parameters are based on the system information; and performing the random access procedure with the network entity based on the first message. By associating UE locations with SSBs and ROs or preambles, or by incorporating location-based beam identification with system broadcast information (e.g., RMSI) , the methods allow UE to determine appropriate PRACH resources and UL-Tx beam directions for Msg 1 or Msg A transmission for UL-only TRPs, thereby improving PRACH coverage and reducing latency. Additionally, by using prior probability signaling for SSBs or ROs / preambles, the methods enable the network to guide UEs with probabilistic weighting toward the most effective access configurations, thereby improving beam selection accuracy and reducing the need for beam sweeping.
[0159] It is understood that the specific order or hierarchy of blocks in the processes / flowcharts disclosed is an illustration of example approaches. Based upon design preferences, it is understood that the specific order or hierarchy of blocks in the processes / flowcharts may be rearranged. Further, some blocks may be combined or omitted. The accompanying method claims present elements of the various blocks in a sample order, and are not limited to the specific order or hierarchy presented.
[0160] The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not limited to the aspects described herein, but are to be accorded the full scope consistent with the language claims. Reference to an element in the singular does not mean “one and only one” unless specifically so stated, but rather “one or more. ” Terms such as “if, ” “when, ” and “while” do not imply an immediate temporal relationship or reaction. That is, these phrases, e.g., “when, ” do not imply an immediate action in response to or during the occurrence of an action, but simply imply that if a condition is met then an action will occur, but without requiring a specific or immediate time constraint for the action to occur. The word “exemplary” is used herein to mean “serving as an example, instance, or illustration. ” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects. Unless specifically stated otherwise, the term “some” refers to one or more. Combinations such as “at least one of A, B, or C, ” “one or more of A, B, or C, ” “at least one of A, B, and C, ” “one or more of A, B, and C, ” and “A, B, C, or any combination thereof” include any combination of A, B, and / or C, and may include multiples of A, multiples of B, or multiples of C. Specifically, combinations such as “at least one of A, B, or C, ” “one or more of A, B, or C, ” “at least one of A, B, and C, ” “one or more of A, B, and C, ” and “A, B, C, or any combination thereof” may be A only, B only, C only, A and B, A and C, B and C, or A and B and C, where any such combinations may contain one or more member or members of A, B, or C. Sets should be interpreted as a set of elements where the elements number one or more. Accordingly, for a set of X, X would include one or more elements. When at least one processor (i.e., a set of one or more processor P) is configured to perform a set of functions F, each processor of P may be configured to perform a subset S of F, where Accordingly, each processor of the at least one processor may be configured to perform a particular subset of the set of functions, where the subset is the full set, a proper subset of the set, or an empty subset of the set. A processor may be referred to as processor circuitry. A memory / memory module may be referred to as memory circuitry. If a first apparatus receives data from or transmits data to a second apparatus, the data may be received / transmitted directly between the first and second apparatuses, or indirectly between the first and second apparatuses through a set of apparatuses. A device configured to “output” data or “provide” data, such as a transmission, signal, or message, may transmit the data, for example with a transceiver, or may send the data to a device that transmits the data. A device configured to “obtain” data, such as a transmission, signal, or message, may receive, for example with a transceiver, or may obtain the data from a device that receives the data. Information stored in a memory includes instructions and / or data. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are encompassed by the claims. Moreover, nothing disclosed herein is dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. The words “module, ” “mechanism, ” “element, ” “device, ” and the like may not be a substitute for the word “means. ” As such, no claim element is to be construed as a means plus function unless the element is expressly recited using the phrase “means for. ”
[0161] As used herein, the phrase “based on” shall not be construed as a reference to a closed set of information, one or more conditions, one or more factors, or the like. In other words, the phrase “based on A” (where “A” may be information, a condition, a factor, or the like) shall be construed as “based at least on A” unless specifically recited differently.
[0162] The following aspects are illustrative only and may be combined with other aspects or teachings described herein, without limitation.
[0163] Aspect 1 is a method of wireless communication at a user equipment (UE) . The method includes receiving system information, wherein the system information includes one or more location identifiers and a first number of groups of random access channel (RACH) occasions (ROs) or preambles associated with a second number of uplink nodes of a network entity, wherein the uplink nodes are dedicated for uplink transmission; transmitting, to one uplink node of the second number of uplink nodes, a first message associated with a random access procedure using uplink transmission parameters, wherein the uplink transmission parameters are based on the system information; and performing the random access procedure with the network entity based on the first message.
[0164] Aspect 2 is the method of aspect 1, wherein the uplink transmission parameters include an uplink transmission beam for transmission of the first message, and wherein transmitting the first message comprises transmitting the first message via the uplink transmission beam through a corresponding RO or preamble of the first number of groups of ROs or preambles.
[0165] Aspect 3 is the method of aspect 2, wherein the system information further includes a third number of synchronization signal blocks (SSBs) , wherein the first number of groups of ROs or preambles are respectively mapped to the third number of SSBs, and wherein the method further comprises determining the uplink transmission parameters based on downlink reception parameters for a reception of one SSB of the third number of SSBs, wherein the one SSB maps to the corresponding RO or preamble.
[0166] Aspect 4 is the method of any of aspects 1 to 3, wherein the system information further includes prior probability information for the third number of SSBs.
[0167] Aspect 5 is the method of aspect 4, wherein the prior probability information includes a set of first prior probabilities for the third number of SSBs, and wherein the method further comprises transmitting a first set of first messages associated with the random access procedure using a second set of ROs or preambles with corresponding SSBs based on a distribution, wherein the distribution is based on at least the set of first prior probabilities for the third number of SSBs.
[0168] Aspect 6 is the method of aspect 5, wherein the prior probability information further includes a set of second prior probabilities for the first number of groups of ROs or preambles.
[0169] Aspect 7 is the method of aspect 6, wherein the distribution is further based on the set of second prior probabilities for the first number of groups of ROs or preambles.
[0170] Aspect 8 is the method of any of aspects 1 to 3, where the method further includes receiving resources for a set of sounding reference signals (SRS) ; and reporting an index for one SSB in the third number of SSB for each SRS in the set of SRS, wherein the one SSB is associated with the uplink transmission parameters for each SRS in the set of SRS.
[0171] Aspect 9 is the method of any of aspects 1 to 3, wherein the system information further comprises a timing advance (TA) value for each group of ROs or preambles in the first number of groups of ROs or preambles, wherein the TA value for a group of ROs or preambles is based on the SSB associated with each group of ROs or preambles.
[0172] Aspect 10 is the method of any of aspects 1 to 2, wherein the system information further includes a fourth number of uplink pointing directions, wherein the first number of groups of ROs or preambles is respectively mapped to the fourth number of uplink pointing directions, and wherein the method further comprises determining the uplink transmission parameters based on one uplink pointing direction of the fourth number of uplink pointing directions, wherein the one uplink pointing direction is associated with the corresponding RO or preamble.
[0173] Aspect 11 is the method of aspect 10, wherein the system information further includes one or more of: location information for the second number of uplink nodes, or prior probability information for the fourth number of uplink pointing directions.
[0174] Aspect 12 is the method of aspect 11, wherein the location information for the second number of uplink nodes is based on a global coordinate system.
[0175] Aspect 13 is the method of aspect 11, wherein the location information for the second number of uplink nodes is based on a center location of a corresponding location identifier and a set of differential coordinates respectively corresponding to the second number of uplink nodes.
[0176] Aspect 14 is the method of aspect 10, wherein the fourth number of uplink pointing directions is based on a local coordination system, and wherein a reference point of one uplink pointing direction of the fourth number of uplink pointing directions is a center location of a corresponding location identifier.
[0177] Aspect 15 is the method of aspect 10, wherein the fourth number of uplink pointing directions is based on a main direction and a set of angular ranges.
[0178] Aspect 16 is the method of aspect 10, wherein the system information further comprises a timing advance (TA) value for each group of ROs or preambles in the first number of groups of ROs or preambles, wherein the TA value for a group of ROs or preambles is based on one or more SSBs from an uplink-downlink node of the network entity.
[0179] Aspect 17 is the method of any of aspects 1 to 2, wherein receiving the system information comprises receiving the system information from one or more of: remaining minimum system information (RMSI) from the network entity, a cloud server, or a second entity different from the network entity.
[0180] Aspect 18 is the method of aspect 17, wherein the system information includes a fourth number of uplink pointing directions mapped to the first number of groups of ROs or preambles and prior probability information for the fourth number of uplink pointing directions, wherein receiving the system information comprises receiving, from the RMSI, the fourth number of uplink pointing directions; and receiving, from the cloud server, the prior probability information for the fourth number of uplink pointing directions.
[0181] Aspect 19 is an apparatus for wireless communication at a UE, comprising: at least one memory; and at least one processor coupled to the at least one memory, the at least one processor is configured to perform the method of any of aspects 1 to 18.
[0182] Aspect 20 is the apparatus for wireless communication at a UE, comprising means for performing each step in the method of any of aspects 1-18.
[0183] Aspect 21 is an apparatus of any of aspects 19-20, further comprising a transceiver configured to receive or to transmit in association with the method of any of aspects 1-18.
[0184] Aspect 22 is a computer-readable medium (e.g., a non-transitory computer-readable medium) storing computer executable code at a UE, the code when executed by at least one processor causes the at least one processor to perform the method of any of aspects 1-18.
[0185] Aspect 23 is a method of wireless communication at a network entity. The method includes transmitting, to a user equipment (UE) , system information, wherein the system information includes one or more location identifiers and a first number of groups of random access channel (RACH) occasions (ROs) or preambles associated with a second number of uplink nodes of the network entity, wherein the uplink nodes are dedicated for uplink transmission; receiving, via one uplink node of the second number of uplink nodes, a first message associated with a random access procedure using uplink transmission parameters, wherein the uplink transmission parameters are based on the system information; and performing the random access procedure with the UE based on the first message.
[0186] Aspect 24 is the method of aspect 23, wherein the uplink transmission parameters include an uplink transmission beam for transmission of the first message, and wherein receiving the first message comprises: receiving the first message via the uplink transmission beam through a corresponding RO or preamble of the first number of groups of ROs or preambles.
[0187] Aspect 25 is an apparatus for wireless communication at a network entity, comprising: at least one memory; and at least one processor coupled to the at least one memory and, where the at least one processor is configured to perform the method of any of aspects 23-24.
[0188] Aspect 26 is the apparatus for wireless communication at a network entity, comprising means for performing each step in the method of any of aspects 23-24.
[0189] Aspect 27 is an apparatus of any of aspects 25-26, further comprising a transceiver configured to receive or to transmit in association with the method of any of aspects 23-24.
[0190] Aspect 28 is a computer-readable medium (e.g., a non-transitory computer-readable medium) storing computer executable code at a network entity, the code when executed by at least one processor causes the at least one processor to perform the method of any of aspects 23-24.
Claims
1.An apparatus for wireless communication at a user equipment (UE) , comprising:at least one memory; andat least one processor coupled to the at least one memory and, based at least in part on information stored in the at least one memory, the at least one processor is configured to:receive system information, wherein the system information includes one or more location identifiers and a first number of groups of random access channel (RACH) occasions (ROs) or preambles associated with a second number of uplink nodes of a network entity, wherein the uplink nodes are dedicated for uplink transmission;transmit, to one uplink node of the second number of uplink nodes, a first message associated with a random access procedure using uplink transmission parameters, wherein the uplink transmission parameters are based on the system information; andperform the random access procedure with the network entity based on the first message.2.The apparatus of claim 1, further comprising a transceiver coupled to the at least one processor, wherein to receive the system information, the at least one processor is configured to receive the system information via the transceiver, wherein the uplink transmission parameters include an uplink transmission beam for transmission of the first message, and wherein to transmit the first message, the at least one processor is configured to:transmit the first message via the uplink transmission beam through a corresponding RO or preamble of the first number of groups of ROs or preambles.3.The apparatus of claim 2, wherein the system information further includes a third number of synchronization signal blocks (SSBs) , wherein the first number of groups of ROs or preambles are respectively mapped to the third number of SSBs, and wherein the at least one processor is further configured to:determine the uplink transmission parameters based on downlink reception parameters for a reception of one SSB of the third number of SSBs, wherein the one SSB maps to the corresponding RO or preamble.4.The apparatus of claim 3, wherein the system information further includes prior probability information for the third number of SSBs.5.The apparatus of claim 4, wherein the prior probability information includes a set of first prior probabilities for the third number of SSBs, and wherein the at least one processor is further configured to:transmit a first set of first messages associated with the random access procedure using a second set of ROs or preambles with corresponding SSBs based on a distribution, wherein the distribution is based on at least the set of first prior probabilities for the third number of SSBs.6.The apparatus of claim 5, wherein the prior probability information further includes a set of second prior probabilities for the first number of groups of ROs or preambles.7.The apparatus of claim 6, wherein the distribution is further based on the set of second prior probabilities for the first number of groups of ROs or preambles.8.The apparatus of claim 3, wherein the at least one processor is further configured to:receive resources for a set of sounding reference signals (SRS) ; andreport an index for one SSB in the third number of SSB for each SRS in the set of SRS, wherein the one SSB is associated with the uplink transmission parameters for each SRS in the set of SRS.9.The apparatus of claim 3, wherein the system information further comprises a timing advance (TA) value for each group of ROs or preambles in the first number of groups of ROs or preambles, wherein the TA value for a group of ROs or preambles is based on the SSB associated with each group of ROs or preambles.10.The apparatus of claim 2, wherein the system information further includes a fourth number of uplink pointing directions, wherein the first number of groups of ROs or preambles is respectively mapped to the fourth number of uplink pointing directions, and wherein the at least one processor is further configured to:determine the uplink transmission parameters based on one uplink pointing direction of the fourth number of uplink pointing directions, wherein the one uplink pointing direction is associated with the corresponding RO or preamble.11.The apparatus of claim 10, wherein the system information further includes one or more of:location information for the second number of uplink nodes, orprior probability information for the fourth number of uplink pointing directions.12.The apparatus of claim 11, wherein the location information for the second number of uplink nodes is based on a global coordinate system.13.The apparatus of claim 11, wherein the location information for the second number of uplink nodes is based on a center location of a corresponding location identifier and a set of differential coordinates respectively corresponding to the second number of uplink nodes.14.The apparatus of claim 10, wherein the fourth number of uplink pointing directions is based on a local coordination system, and wherein a reference point of one uplink pointing direction of the fourth number of uplink pointing directions is a center location of a corresponding location identifier.15.The apparatus of claim 10, wherein the fourth number of uplink pointing directions is based on a main direction and a set of angular ranges.16.The apparatus of claim 10, wherein the system information further comprises a timing advance (TA) value for each group of ROs or preambles in the first number of groups of ROs or preambles, wherein the TA value for a group of ROs or preambles is based on one or more SSBs from an uplink-downlink node of the network entity.17.The apparatus of claim 2, wherein to receive the system information, the at least one processor is configured to receive the system information from one or more of:remaining minimum system information (RMSI) from the network entity, a cloud server, ora second entity different from the network entity.18.The apparatus of claim 17, wherein the system information includes a fourth number of uplink pointing directions mapped to the first number of groups of ROs or preambles and prior probability information for the fourth number of uplink pointing directions, wherein to receive the system information, the at least one processor is configured to:receive, from the RMSI, the fourth number of uplink pointing directions; andreceive, from the cloud server, the prior probability information for the fourth number of uplink pointing directions.19.An apparatus for wireless communication at a network entity, comprising:at least one memory; andat least one processor coupled to the at least one memory and, based at least in part on information stored in the at least one memory, the at least one processor is configured to:transmit, to a user equipment (UE) , system information, wherein the system information includes one or more location identifiers and a first number of groups of random access channel (RACH) occasions (ROs) or preambles associated with a second number of uplink nodes of the network entity, wherein the uplink nodes are dedicated for uplink transmission;receive, via one uplink node of the second number of uplink nodes, a first message associated with a random access procedure using uplink transmission parameters, wherein the uplink transmission parameters are based on the system information; andperform the random access procedure with the UE based on the first message.20.A computer-readable medium storing computer executable code at a user equipment (UE) , the code when executed by at least one processor causes the at least one processor to:receive system information, wherein the system information includes one or more location identifiers and a first number of groups of random access channel (RACH) occasions (ROs) or preambles associated with a second number of uplink nodes of a network entity, wherein the uplink nodes are dedicated for uplink transmission;transmit, to one uplink node of the second number of uplink nodes, a first message associated with a random access procedure using uplink transmission parameters, wherein the uplink transmission parameters are based on the system information; andperform the random access procedure with the network entity based on the first message.
