RACH configuration across frequency subcomponents
By providing individual RACH configurations for each frequency subcomponent in 5G NR systems, the flexibility and performance of RACH procedures are enhanced, addressing the limitations of existing systems.
Patent Information
- Application Number
- PCT/CN2025/092752
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-05-03
- Publication Date
- 2026-11-12
AI Technical Summary
Existing wireless communication systems, particularly 5G NR, lack flexibility in Random Access Channel (RACH) configurations across different frequency subcomponents, leading to suboptimal performance.
Implementing individual RACH configurations for each frequency subcomponent, allowing for different RACH parameters such as RO, power-related settings, and preamble formats, to enhance RACH performance by optimizing configurations based on specific frequency subcomponents.
This approach improves RACH performance by enabling more suitable configurations for respective frequency subcomponents, enhancing the efficiency and effectiveness of RACH procedures.
Smart Images

Figure CN2025092752_12112026_PF_FP_ABST
Abstract
Description
RACH CONFIGURATION ACROSS FREQUENCY SUBCOMPONENTSTECHNICAL FIELD
[0001] The present disclosure relates generally to communication systems, and more particularly, to wireless communication systems with random access channel (RACH) . 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. There exists a need for further improvements in 5G NR technology. 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 at a user equipment (UE) are provided. 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, individually or in any combination, is configured to (e.g., cause the UE to) transmit, to a network node, a capability indication indicating a support for a respective RACH configuration for each frequency subcomponent (SC) of multiple frequency SCs. Based at least in part on information stored in the at least one memory, the at least one processor, individually or in any combination, is configured to receive, from the network node, a set of multiple RACH configurations associated with a set of multiple frequency SCs.
[0006] In another aspect of the disclosure, a method, a computer-readable medium, and an apparatus at a network entity are provided. 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, individually or in any combination, is configured to receive, from a user equipment (UE) , a capability indication indicating a support for a respective RACH configuration for each frequency subcomponent (SC) of multiple frequency SCs. Based at least in part on information stored in the at least one memory, the at least one processor, individually or in any combination, is configured to transmit a set of multiple RACH configurations associated with a set of multiple frequency SCs.
[0007] To the accomplishment of the foregoing and related ends, the one or more aspects 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 communications 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, in accordance with various aspects of the present disclosure.
[0014] FIG. 4A and FIG. 4B illustrate example aspects of random access, in accordance with various aspects of the present disclosure.
[0015] FIG. 5 is a diagram illustrating example communications between a network node and a UE, in accordance with various aspects of the present disclosure.
[0016] FIG. 6 is a flowchart of a method of wireless communication, in accordance with various aspects of the present disclosure.
[0017] FIG. 7 is a flowchart of a method of wireless communication, in accordance with various aspects of the present disclosure.
[0018] FIG. 8 is a diagram illustrating an example of a hardware implementation for an example apparatus and / or network entity, in accordance with various aspects of the present disclosure.
[0019] FIG. 9 is a diagram illustrating an example of a hardware implementation for an example network entity, in accordance with various aspects of the present disclosure.DETAILED DESCRIPTION
[0020] 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.
[0021] In some wireless communication systems, there may be one random access channel (RACH) configuration for a user equipment (UE) . In some wireless communication systems, for normal uplink (NUL) and supplementary uplink (SUL) , there may be two separate / independent RACH configurations provided, each associated with the same downlink (DL) component and the synchronization signal blocks (SSBs) . As an example, the UE may select the RACH configuration for the NUL or the SUL based on a configured measurement (e.g., reference signal received power (RSRP) ) threshold. Aspects provided herein may further provide flexibility in RACH configurations to improve RACH performance by supporting individual RACH configuration (s) for different frequency subcomponents (SCs) . For example, for different frequency SCs, there may be different RACH configuration such as different RO, power-related parameters, preamble format, or other RACH parameters. Such flexibility may improve RACH performance because the individual RACH configurations may be more suitable for their respective frequency SC. Aspects provided herein may also enable using different frequency SCs in subsequent RACH messages / responses or RACH retransmissions, which may also improve performance of the RACH procedure. A downlink RACH message (such as a message 2, message 4, or message B) may be associated with a set of DL frequency SCs and an uplink RACH message (such a message 1, message 3, or message A) may be associated with a set of uplink (UL) frequency SCs. As an example, there may be many-to-one, one-to-one, one-to-many, or many-to-many mapping between the set of DL frequency SCs and the set of UL frequency SCs.
[0022] 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.
[0023] 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. One or more processors in the processing system may execute software to cause a device that includes the one or more processors to perform the various functionality described throughout this disclosure.
[0024] 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 (e.g., transitory or non-transitory medium that may be accessed by computer) .
[0025] 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.
[0026] Deployment of communication systems, such as 5G NR systems, may be arranged in multiple manners with various components or constituent parts. In a 5G NR system, or 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.
[0027] 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) .
[0028] 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.
[0029] 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.
[0030] 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.
[0031] 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.
[0032] 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.
[0033] 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.
[0034] 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.
[0035] 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.
[0036] 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) .
[0037] 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) .
[0038] 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.
[0039] 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.
[0040] 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.
[0041] The frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR studies have identified an operating band for these mid-band frequencies as frequency range designation FR3 (7.125 GHz –24.25 GHz) . 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 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.
[0042] 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.
[0043] 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.
[0044] 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) .
[0045] 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.
[0046] 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.
[0047] Referring again to FIG. 1, in some aspects, the UE 104 may include a RACH component 198. In some aspects, the RACH component 198 may be configured to transmit, to a network node, a capability indication indicating a support for a respective RACH configuration for each frequency subcomponent (SC) of multiple frequency SCs. In some aspects, the RACH component 198 may be further configured to receive, from the network node, a set of multiple RACH configurations associated with a set of multiple frequency SCs.
[0048] In certain aspects, the base station 102 may include a RACH component 199. In some aspects, the RACH component 199 may be configured to receive, from a user equipment (UE) , a capability indication indicating a support for a respective RACH configuration for each frequency subcomponent (SC) of multiple frequency SCs. In some aspects, the RACH component 199 may be further configured to transmit a set of multiple RACH configurations associated with a set of multiple frequency SCs.
[0049] Although the following description may be focused on 5G NR, the concepts described herein may be applicable to other similar areas, such as 6G, LTE, LTE-A, CDMA, GSM, and other wireless technologies.
[0050] As described herein, a node (which may be referred to as a node, a network node, a network entity, or a wireless node) may include, be, or be included in (e.g., be a component of) a base station (e.g., any base station described herein) , a UE (e.g., any UE described herein) , a network controller, an apparatus, a device, a computing system, an integrated access and backhauling (IAB) node, a distributed unit (DU) , a central unit (CU) , a remote / radio unit (RU) (which may also be referred to as a remote radio unit (RRU) ) , and / or another processing entity configured to perform any of the techniques described herein. For example, a network node may be a UE. As another example, a network node may be a base station or network entity. As another example, a first network node may be configured to communicate with a second network node or a third network node. In one aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a UE. In another aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a base station. In yet other aspects of this example, the first, second, and third network nodes may be different relative to these examples. Similarly, reference to a UE, base station, apparatus, device, computing system, or the like may include disclosure of the UE, base station, apparatus, device, computing system, or the like being a network node. For example, disclosure that a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node. Consistent with this disclosure, once a specific example is broadened in accordance with this disclosure (e.g., a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node) , the broader example of the narrower example may be interpreted in the reverse, but in a broad open-ended way. In the example above where a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node, the first network node may refer to a first UE, a first base station, a first apparatus, a first device, a first computing system, a first set of one or more one or more components, a first processing entity, or the like configured to receive the information; and the second network node may refer to a second UE, a second base station, a second apparatus, a second device, a second computing system, a second set of one or more components, a second processing entity, or the like.
[0051] As described herein, communication of information (e.g., any information, signal, or the like) may be described in various aspects using different terminology. Disclosure of one communication term includes disclosure of other communication terms. For example, a first network node may be described as being configured to transmit information to a second network node. In this example and consistent with this disclosure, disclosure that the first network node is configured to transmit information to the second network node includes disclosure that the first network node is configured to provide, send, output, communicate, or transmit information to the second network node. Similarly, in this example and consistent with this disclosure, disclosure that the first network node is configured to transmit information to the second network node includes disclosure that the second network node is configured to receive, obtain, or decode the information that is provided, sent, output, communicated, or transmitted by the first network node.
[0052] FIG. 2A is a diagram 200 illustrating an example of a first subframe within a 5G NR frame structure. FIG. 2B is a diagram 230 illustrating an example of DL channels within a 5G NR subframe. FIG. 2C is a diagram 250 illustrating an example of a second subframe within a 5G NR frame structure. FIG. 2D is a diagram 280 illustrating an example of UL channels within a 5G NR subframe. The 5G NR 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.
[0053] 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
[0054] 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) .
[0055] 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.
[0056] 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) .
[0057] 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.
[0058] 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.
[0059] 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.
[0060] 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.
[0061] 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.
[0062] 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.
[0063] 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.
[0064] 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.
[0065] 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.
[0066] 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.
[0067] 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.
[0068] 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 RACH component 198 of FIG. 1.
[0069] 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 RACH component 199 of FIG. 1.
[0070] A UE may use a random access procedure in order to communicate with a network node. For example, the UE may use the random access procedure for various reasons, e.g., including to request an RRC connection, to re-establish an RRC connection, resume an RRC connection, etc. Random access procedures may include two different random access procedures, e.g., The UE may use contention based random access (CBRA) may be performed when a UE is not synchronized with a network node, and contention free random access (CFRA) may be applied, e.g., when the UE was previously synchronized to a network node. Both the procedures include transmission of a random access preamble from the UE to the network node. In CBRA, a UE may randomly select a random access preamble sequence, e.g., from a set of preamble sequences. As the UE randomly selects the preamble sequence, the network node may receive another preamble from a different UE at the same time. Thus, CBRA provides for the network node to resolve such contention among multiple UEs. In CFRA, the network may allocate a preamble sequence to the UE rather than the UE randomly selecting a preamble sequence. This may help to avoid potential collisions with a preamble from another UE using the same sequence. Thus, CFRA is referred to as “contention free” random access. The preamble may be based on a particular preamble format, such as long format for large cell coverage, short format for dense urban areas, or the like.
[0071] FIG. 4A illustrates example aspects of a random access procedure 400 between a UE 402 and a network node such as a network node 404. The aspects illustrated for the network node 404 may be performed by one or more components of the network node. The UE 402 may initiate the random access message exchange by sending, to the network node 404, a first random access message 430 (e.g., message 1 or Msg 1) including a preamble in a random access occasion (RO) . Prior to sending the first random access message 430, the UE 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 429 from the network node 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 network node 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.
[0072] The network node responds to the first random access message 430 by sending a second random access message 431 (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, cell radio network temporary identifier (C-RNTI) or another identifier, and / or a back-off indicator. Upon receiving the second random access message 431, the UE 402 may transmit a third random access message 433 (e.g., Msg 3) to the network node 404, e.g., using PUSCH, that may include an RRC request, such as 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 network node 404 may then complete the random access procedure by sending a fourth random access message 435 (e.g., Msg 4) to the UE 402, e.g., using PDCCH for scheduling and PDSCH for the message. The fourth random access message 435 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 sent a same preamble at 430, both UEs may receive the RAR leading both UEs to send a third random access message 433. The network node 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 435, 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 435 may complete the random access procedure. Thus, the UE 402 may then transmit uplink communication and / or receive downlink communication with the network node 404 based on the second random access message 431 and / or the fourth random access message 435.
[0073] In order to reduce latency or control signaling overhead, a single round trip cycle between the UE 402 and the network node 404 may be achieved in a 2-step RACH process, as shown in the communication flow 440 in FIG. 4B. Aspects of Msg 1 and Msg 3 may be combined in a single message, e.g., which may be referred to as Msg A 450 (message A or Msg A) . The Msg A may include a random access preamble, and may also include a PUSCH transmission, e.g., such as data. The Msg A preambles may be separate from the four step preambles, yet may be transmitted in the same 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 450, the UE 402 may wait for a response from the network node 404. Additionally, aspects of the Msg 2 and Msg 4 may be combined into a single message, which may be referred to as Msg B 452 (message B or Msg B) .
[0074] A RACH procedure (e.g., which may also be referred to as a random access procedure) may be used for acquiring a connection to a cell, as well as part of various connection mode procedures. A RACH procedure can be 4-step or 2-step, e.g., as illustrated in FIG. 4A and FIG. 4B. A RACH procedure may be based on a contention based procedure or a contention free procedure, e.g., depending on the timing advance (TA) information available. A RACH procedure may facilitate obtaining the accurate TA and / or cell random network temporary identifier (C-RNTI) for a UE to exchange connected mode communication with the network. An SSB may provide the details of the time offset at which RACH procedure can be initiated with message 1 transmission in UL, for example. Based on the message 1, which may include a Zadoff Chu sequence, and autocorrelation output, the network may estimate an adjustment to TA and inform the UE of the adjustment to the TA as part of message 2. The UE may adjust the TA as part of preparing to transmit a message. The UE may then transmit the RRC Connection Request (e.g., message 3) to the network along with a randomly generated number as temporary C-RNTI (TC-RNTI) . The network may reply by sending the contention resolution message (message 4) along with TC-RNTI received in message 3. When the received message 4 TC-RNTI matches with message 3 TC-RNTI sent from the UE, the RACH procedure may be assumed to be successful and TC-RNTI may be noted as C-RNTI for further connection mode procedures. Otherwise, the UE may determine that the RACH procedure has failed. A RACH procedure may also be used for various activities, such as beam failure recovery (BFR) , scheduling request (SR) failure, TA calculation, during out of service (OOS) recovery, handover, or the like. In some aspects, a 4-step RACH may be based on CBRA and a 2-step RACH may be based on a CFRA procedure. When target cell SSB information is available from source cell, a UE may use the 2-step RACH procedure for faster acquisition as part of a CFRA procedure. In some wireless communication systems, various RACH parameters such as initial preamble power, quantity of retransmissions allowed, power ramp up step between retransmission, scaling factor, contention resolution timer, RACH response window, and other parameters, may be indicated by the network, e.g., as part of a configuration, and followed by the UE for RACH procedure.
[0075] A RACH configuration may define how a network may provide random access resources for UEs to initiate communication with network node. An example RACH configuration may include a preamble format (e.g., structure and duration of the RACH signal based on subcarrier spacing and cell size) , a quantity of preamble sequences (e.g., preamble sequences available for the RACH message) , the RACH occasions (e.g., time or frequency where the RACH message may be transmitted) , root sequence index and preamble group configuration, beam association (s) with RACH occasions, a power ramping step, maximum number of preamble transmissions, or RA response window.
[0076] In some wireless communication systems, there may be one RACH configuration for a UE. In some wireless communication systems, for normal uplink (NUL) and supplementary uplink (SUL) , there may be two separate / independent RACH configurations provided, each associated with the same DL component and the SSBs. As an example, the UE may select the RACH configuration for the NUL or the SUL based on a configured measurement (e.g., reference signal received power (RSRP) ) threshold. Aspects provided herein may further provide flexibility in RACH configurations to improve RACH performance by supporting individual RACH configuration (s) for different frequency subcomponents (SCs) . For example, for different frequency SCs, there may be different RACH configuration such as different RO, power-related parameters, preamble format, or other RACH parameters. Such flexibility may improve RACH performance because the individual RACH configurations may be more suitable for their respective frequency SC. Aspects provided herein may also enable using different frequency SCs in subsequent RACH messages / responses or RACH retransmissions, which may also improve performance of the RACH procedure. A downlink RACH message (such as a message 2, message 4, or message B) may be associated with a set of DL frequency SCs and an uplink RACH message (such a message 1, message 3, or message A) may be associated with a set of UL frequency SCs. A UE may transmit a first RACH message in a first frequency SC based on a first RACH configuration associated with the first frequency SC, receive a RACH response in a same or a different frequency SC, transmit a subsequent RACH message (e.g., a message 3 or a retransmission of the first RACH message) in a frequency SC same as or different from the first frequency SC (e.g., and based on RACH configuration associated with the frequency SC same as or different from the first frequency SC, or based on the first RACH configuration regardless of the frequency SC used)
[0077] As an example, there may be many-to-one, one-to-one, one-to-many, or many-to-many mapping between the set of DL frequency SCs and the set of UL frequency SCs. There may be a first set of SCs configured with DL-RS resources such as SSBs that may be indicated by a DL frequency SC configuration for DL-RSs. In a UL frequency SC configuration for RACH resources, there may be a second set of SCs may be configured with RACH resources. The two sets may or may not be the same. In some aspects, there may be overlap in frequency between the two sets. In some aspects, there may be no overlap between the two sets.
[0078] FIG. 5 is a diagram 500 illustrating example communications between a network node 504 and a UE 502, in accordance with various aspects of the present disclosure. As illustrated in FIG. 5, the network node 504 may receive, from a UE 502, a capability indication 510 indicating a support for a respective RACH configuration for each frequency SC of multiple frequency SCs. The network node 504 may transmit (e.g., in SIB, RRC configurations, or the like) a set of multiple RACH configurations 520 associated with a set of multiple frequency SCs.
[0079] In some aspects, there may be a configuration (e.g., in mapping 530 from the network node 504 to the UE 502) of many-to-one or many-to-many mapping between DL frequency SCs in the first set and UL frequency SCs in the second set. For example, SSBs in X (a positive integer) DL frequency SCs may be associated with PRACH resources in one UL frequency SC. As another example, SSBs in X DL frequency SCs are associated with PRACH resources in Y (a positive integer) UL frequency SCs. In some aspects, the mapping may be configured via SIB or RRC configurations.
[0080] In some aspects, there may be an indication (e.g. in indication 550 from the network node 504 to the UE 502) of inter-SC quasi-colocation (QCL) relation between DL-RS across SCs. For example, a DL-RS in SC A (one of the SCs) may be quasi-co-located (QCL’ ed) to a DL-RS in SC B as indicated in the indication of inter-SCL QCL relation. Such information on inter-SCL QCL relation may be used for RO selection related to a RACH message (e.g., RACH message 560 or RACH message 580) . For example, X (a positive integer) DL frequency SCs associated with the same UL frequency SC of RACH resources may have QCL’ ed DL-RSs to share a same RO for RACH. The UE may determine a message1 PRACH transmission (e.g., which may be the RACH message 560) based on a DL-RS A in SC A, and receive message-2 (e.g., the RACH response 570) in a SC B using a DL-RS B QCL’ ed to DL-RS A. In some aspects, SC selection for a RACH message may be based on a configured criteria for SC selection associated with the set of UL frequency SCs to initiate RACH. For example, the criteria for SC selection may be based on measurements on multiple SCs from the DL-RSs associated with the set of DL frequency SCs, indicated priorities, or the SC that has a more immediate available RO, depending on a “cause” value associated with the RACH procedure that indicates a purpose or trigger of the RACH procedure, an indication in paging, or the like. In some aspects, 520, 530, and 550 may be provided in a same signaling or separate signaling (e.g., SIB or RRC configuration) .
[0081] In some aspects, the RACH configuration may also include a PRACH retransmission configuration which may define the parameters for PRACH retransmission. In some aspects, the UL frequency SC used for PRACH retransmission may be indicated in a RACH response (e.g., the RACH response 570 as an extension of back-off indicator) , in the RACH configuration, or based on criteria related to channel qualities or priorities. In some aspects, there may be “hopping” (e.g., switch) of SCs. For example, the UE may transmit a first RACH message (e.g., 560) in SC A, and hop to retransmit a second RACH message (e.g., 580) in SC B if the first RACH message fails. As another example, the UE may transmit two associated / consecutive / repeated PRACHs in message-1 (e.g., 560) , such as transmit a first PRACH in SC A and hop to second PRACH in SC B for the same first RACH message. In some aspects, the first transmission of PRACH may be in one UL frequency SC, and second retransmission may be in two UL frequency SCs using hopping. In some aspects, a pattern for such a switch may be referred to as a “hopping pattern” and such a hopping pattern may be: (1) configured by SIB, (2) configured without signaling, (3) based on UE implementation and subject to configuration form the network (e.g., based on path loss or measurement (e.g., RSRP) criteria) .
[0082] In some aspects, there may be hopping rules that defines: (1) hopping may not be allowed and the UE may perform retransmission in the same SC as the first transmission, (2) hopping may be allowed under all conditions, (3) hopping is allowed within an indicated / configured set of UL frequency SCs (e.g., all those UL frequency SCs originally associated with the UE’s selected DL frequency SC, or the set of associated UL frequency SCs over which hopping is allowed may be configured or indicated by the network, (4) for each UL frequency SC, a set of one or multiple other UL frequency SCs may be indicated to be allowed to hop to, or (5) one or multiple hopping pattern can be configured, where each happing pattern is an ordered list of UL frequency SCs.
[0083] In some aspects, there may be transmission power ramping configuration based on the PRACH retransmission and hopping. For example, the UE may increase transmission power for a PRACH transmission if the PRACH is a retransmission for a PRACH previously transmitted in the same SC. The UE may not increase transmission power for a PRACH transmission if the PRACH transmission is a retransmission on a new SC. As another example, the UE may increase transmission power for a PRACH transmission if the PRACH transmission is a retransmission on a new SC (e.g., based on a same power ramp-up step, or a power ramp-up step separately configured when hopping is present) . As another example, the UE may increase transmission power within an indicated / configured set of UL frequency SCs (e.g., where the SC for the previous RACH transmission belongs to) , but not when switching outside the indicated / configured set.
[0084] In some aspects, for the RAR configuration, there may be many-to-one or one-to-one mapping between UL frequency SCs to DL frequency SCs. For example, the UE may transmit PRACH in any of X UL frequency SCs, and receive RAR in one DL frequency SC (X being larger than two or larger than one) . As another example, the UE transmits PRACH in one UL frequency SC, and receive RAR in one associated DL frequency SC.
[0085] In some aspects, there may be one-to-many mapping that may be RO / beam / preamble ID-specific. For example, the UE may transmit PRACH in one UL frequency SC, and depending on PRACH’s RO / beam / preamble ID to receive RARs in one of Y DL frequency SCs (Y being larger than one) . In some aspects, the mapping between RO / beam / preamble and DL frequency SCs can be configured in SIB, RRC, or configured without signaling. In some aspects, there may be RAR enhancement for X UL frequency SCs associated with one DL frequency SC. For example, there may be RA-RNTI enhancement which may include an extended formula for more and configurable set of values for a UL SC represented by an ul_carrier_id where RA-RNTI = 1 + s_id + 14 × t_id + 14 × 80 × f_id + 14 × 80 × 8 × ul_carrier_id. In some aspects, there may be a common RA-RNTI used for X UL frequency SCs, but RAR content may differentiate different UL subcomponents.
[0086] FIG. 6 is a flowchart 600 of a method of wireless communication. The method may be performed by a UE (e.g., the UE 104, the UE 502; the apparatus 804) . The method may provide flexibility in RACH configurations to improve RACH performance by supporting individual RACH configuration (s) for different frequency subcomponents (SCs) . For example, for different frequency SCs, there may be different RACH configuration such as different RO, power-related parameters, preamble format, or other RACH parameters. Such flexibility may improve RACH performance because the individual RACH configurations may be more suitable for their respective frequency SC. The method may also enable using different frequency SCs in subsequent RACH messages / responses or RACH retransmissions, which may also improve performance of the RACH procedure.
[0087] At 602, the UE may transmit, to a network node, a capability indication indicating a support for a respective RACH configuration for each frequency subcomponent (SC) of multiple frequency SCs. For example, the UE 502 may transmit, to a network node 504, a capability indication (e.g., 510) indicating a support for a respective RACH configuration for each frequency subcomponent (SC) of multiple frequency SCs. In some aspects, 602 may be performed by RACH component 198.
[0088] At 604, the UE may receive, from the network node, a set of multiple RACH configurations associated with a set of multiple frequency SCs. For example, the UE 502 may receive, from the network node 504, a set of multiple RACH configurations (e.g., 520) associated with a set of multiple frequency SCs. In some aspects, 604 may be performed by RACH component 198.
[0089] In some aspects, the multiple frequency SCs is a set of uplink frequency SCs associated with a set of downlink frequency SCs, where the set of downlink frequency SCs is associated with a set of downlink reference signals, where the set of uplink frequency SCs is associated with an uplink RACH message and the set of downlink frequency SCs is associated with a downlink RACH message.
[0090] In some aspects, the UE may receive, from the network node in system information block (SIB) or a radio resource control (RRC) configuration, a mapping (e.g., 530) between the set of downlink frequency SCs and the set of uplink frequency SCs, where the mapping is a many-to-one mapping or a many-to-many mapping.
[0091] In some aspects, the UE may receive, from the network node, inter-SC quasi-colocation (QCL) information (e.g., 550) of the set of downlink reference signals associated with the set of downlink frequency SCs.
[0092] In some aspects, the UE may transmit a RACH message (e.g., 560) in a RACH occasion (RO) , where more than two uplink frequency SCs of the set of uplink frequency SCs is associated with the RO based on more than two downlink frequency SCs mapped to the more than two uplink frequency SCs being associated with quasi-co-located (QCL’ ed) downlink reference signals of the set of downlink reference signals according to the inter-SC QCL information.
[0093] In some aspects, the RACH message (e.g., 560) is included in a first frequency SC of the more than two uplink frequency SCs that corresponds to a corresponding first frequency SC of the more than two downlink frequency SCs. In some aspects, the UE may receive a second RACH message in a second frequency SC of the more than two downlink frequency SCs.
[0094] In some aspects, the UE may receive, from the network node, an SC selection criteria for transmission of a RACH message.
[0095] In some aspects, the UE may transmit a first RACH message (e.g., 560) based on a first frequency SC of the multiple frequency SCs and a first RACH configuration associated with the first frequency SC. In some aspects, the UE may transmit a second RACH message (e.g., 580) based on a second frequency SC of the multiple frequency SCs and a second RACH configuration associated with the second frequency SC. In some aspects, a hopping pattern associated with a change from the first frequency SC to the second frequency SC is included in a system information block (SIB) or configured without signaling, or where a RACH response associated with the first RACH message indicates the second frequency SC or the second frequency SC is based on a channel quality or priority criteria. In some aspects, the second RACH message is a retransmission of the first RACH message, and where the second RACH message is associated with a same transmission power as the first RACH message.
[0096] FIG. 7 is a flowchart 700 of a method of wireless communication. The method may be performed by a network node (e.g., the base station 102, the network node 504, the network entity 802, the network entity 902) . The method may provide flexibility in RACH configurations to improve RACH performance by supporting individual RACH configuration (s) for different frequency subcomponents (SCs) . For example, for different frequency SCs, there may be different RACH configuration such as different RO, power-related parameters, preamble format, or other RACH parameters. Such flexibility may improve RACH performance because the individual RACH configurations may be more suitable for their respective frequency SC. The method may also enable using different frequency SCs in subsequent RACH messages / responses or RACH retransmissions, which may also improve performance of the RACH procedure.
[0097] At 702, the network node may receive, from a user equipment (UE) , a capability indication indicating a support for a respective RACH configuration for each frequency subcomponent (SC) of multiple frequency SCs. For example, the network node 504 may receive, from a user equipment (UE) (e.g., 502) , a capability indication (e.g., 510) indicating a support for a respective RACH configuration for each frequency subcomponent (SC) of multiple frequency SCs. In some aspects, 702 may be performed by RACH component 199.
[0098] At 704, the network node may transmit a set of multiple RACH configurations associated with a set of multiple frequency SCs. For example, the network node 504 may transmit a set of multiple RACH configurations associated with a set of multiple frequency SCs. In some aspects, 704 may be performed by RACH component 199.
[0099] In some aspects, the multiple frequency SCs is a set of uplink frequency SCs associated with a set of downlink frequency SCs, where the set of downlink frequency SCs is associated with a set of downlink reference signals, where the set of uplink frequency SCs is associated with an uplink RACH message and the set of downlink frequency SCs is associated with a downlink RACH message.
[0100] In some aspects, the network node may transmit, in system information block (SIB) or a radio resource control (RRC) configuration, a mapping (e.g., 530) between the set of downlink frequency SCs and the set of uplink frequency SCs, where the mapping is a many-to-one mapping or a many-to-many mapping.
[0101] In some aspects, the network node may transmit inter-SC quasi-colocation (QCL) information (e.g., 550) of the set of downlink reference signals associated with the set of downlink frequency SCs.
[0102] In some aspects, the network node may receive a RACH message (e.g., 560) in a RACH occasion (RO) , where more than two uplink frequency SCs of the set of uplink frequency SCs is associated with the RO based on more than two downlink frequency SCs mapped to the more than two uplink frequency SCs being associated with quasi-co-located (QCL’ ed) downlink reference signals of the set of downlink reference signals according to the inter-SC QCL information.
[0103] In some aspects, the RACH message is included in a first frequency SC of the more than two uplink frequency SCs that corresponds to a corresponding first frequency SC of the more than two downlink frequency SCs. In some aspects, the network node may transmit a second RACH message in a second frequency SC of the more than two downlink frequency SCs.
[0104] In some aspects, the network node may transmit an SC selection criteria for transmission of a RACH message.
[0105] In some aspects, the network node may receive a first RACH message (e.g., 560) based on a first frequency SC of the multiple frequency SCs and a first RACH configuration associated with the first frequency SC. In some aspects, the network node may receive a second RACH message (e.g., 580) based on a second frequency SC of the multiple frequency SCs and a second RACH configuration associated with the second frequency SC. In some aspects, a hopping pattern associated with a change from the first frequency SC to the second frequency SC is included in a system information block (SIB) or configured without signaling, or where a RACH response associated with the first RACH message indicates the second frequency SC or the second frequency SC is based on a channel quality or priority criteria. In some aspects, the second RACH message is a retransmission of the first RACH message, and where the second RACH message is associated with a same transmission power as the first RACH message.
[0106] FIG. 8 is a diagram 800 illustrating an example of a hardware implementation for an apparatus 804. The apparatus 804 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus804 may include at least one cellular baseband processor 824 (also referred to as a modem) coupled to one or more transceivers 822 (e.g., cellular RF transceiver) . The cellular baseband processor (s) 824 may include at least one on-chip memory 824'. In some aspects, the apparatus 804 may further include one or more subscriber identity modules (SIM) cards 820 and at least one application processor 806 coupled to a secure digital (SD) card 808 and a screen 810. The application processor (s) 806 may include on-chip memory 806'. In some aspects, the apparatus 804 may further include a Bluetooth module 812, a WLAN module 814, an SPS module 816 (e.g., GNSS module) , one or more sensor modules 818 (e.g., barometric pressure sensor / altimeter; motion sensor such as inertial measurement unit (IMU) , gyroscope, and / or accelerometer (s) ; light detection and ranging (LIDAR) , radio assisted detection and ranging (RADAR) , sound navigation and ranging (SONAR) , magnetometer, audio and / or other technologies used for positioning) , additional memory modules 826, a power supply 830, and / or a camera 832. The Bluetooth module 812, the WLAN module 814, and the SPS module 816 may include an on-chip transceiver (TRX) (or in some cases, just a receiver (RX) ) . The Bluetooth module 812, the WLAN module 814, and the SPS module 816 may include their own dedicated antennas and / or utilize the antennas 880 for communication. The cellular baseband processor (s) 824 communicates through the transceiver (s) 822 via one or more antennas 880 with the UE 104 and / or with an RU associated with a network entity 802. The cellular baseband processor (s) 824 and the application processor (s) 806 may each include a computer-readable medium / memory 824', 806', respectively. The additional memory modules 826 may also be considered a computer-readable medium / memory. Each computer-readable medium / memory 824', 806', 826 may be non-transitory. The cellular baseband processor (s) 824 and the application processor (s) 806 are each responsible for general processing, including the execution of software stored on the computer-readable medium / memory. The software, when executed by the cellular baseband processor (s) 824 / application processor (s) 806, causes the cellular baseband processor (s) 824 / application processor (s) 806 to perform the various functions described supra. The computer-readable medium / memory may also be used for storing data that is manipulated by the cellular baseband processor (s) 824 / application processor (s) 806 when executing software. The cellular baseband processor (s) 824 / application processor (s) 806 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 804 may be at least one processor chip (modem and / or application) and include just the cellular baseband processor (s) 824 and / or the application processor (s) 806, and in another configuration, the apparatus 804 may be the entire UE (e.g., see UE 350 of FIG. 3) and include the additional modules of the apparatus 804.
[0107] As discussed supra, the RACH component 198 may be configured to transmit, to a network node, a capability indication indicating a support for a respective RACH configuration for each frequency subcomponent (SC) of multiple frequency SCs. In some aspects, the RACH component 198 may be further configured to receive, from the network node, a set of multiple RACH configurations associated with a set of multiple frequency SCs. The RACH component 198 may be within the cellular baseband processor (s) 824, the application processor (s) 806, or both the cellular baseband processor (s) 824 and the application processor (s) 806. 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 804 may include a variety of components configured for various functions. In one configuration, the apparatus 804, and in particular the cellular baseband processor (s) 824 and / or the application processor (s) 806, may include means for transmitting, to a network node, a capability indication indicating a support for a respective RACH configuration for each frequency subcomponent (SC) of multiple frequency SCs. In some aspects, the apparatus 804 may include means for receiving, from the network node, a set of multiple RACH configurations associated with a set of multiple frequency SCs. In some aspects, the apparatus 804 may include means for receiving, from the network node in system information block (SIB) or a radio resource control (RRC) configuration, a mapping between the set of downlink frequency SCs and the set of uplink frequency SCs, where the mapping is a many-to-one mapping or a many-to-many mapping. In some aspects, the apparatus 804 may include means for receiving, from the network node, inter-SC quasi-colocation (QCL) information of the set of downlink reference signals associated with the set of downlink frequency SCs. In some aspects, the apparatus 804 may include means for transmitting a RACH message in a RACH occasion (RO) , where more than two uplink frequency SCs of the set of uplink frequency SCs is associated with the RO based on more than two downlink frequency SCs mapped to the more than two uplink frequency SCs being associated with quasi-co-located (QCL’ ed) downlink reference signals of the set of downlink reference signals according to the inter-SC QCL information. In some aspects, the apparatus 804 may include means for receiving a second RACH message in a second frequency SC of the more than two downlink frequency SCs. In some aspects, the apparatus 804 may include means for receiving, from the network node, an SC selection criteria for transmission of a RACH message. In some aspects, the apparatus 804 may include means for transmitting a first RACH message based on a first frequency SC of the multiple frequency SCs and a first RACH configuration associated with the first frequency SC. In some aspects, the apparatus 804 may include means for transmitting a second RACH message based on a second frequency SC of the multiple frequency SCs and a second RACH configuration associated with the second frequency SC. The means may be the component 198 of the apparatus 804 configured to perform the functions recited by the means. As described supra, the apparatus 804 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. The apparatus 804 may be configured to perform operations described in connection with FIG. 6.
[0108] FIG. 9 is a diagram 900 illustrating an example of a hardware implementation for a network entity 902. The network entity 902 may be a BS, a component of a BS, or may implement BS functionality. The network entity 902 may include at least one of a CU 910, a DU 930, or an RU 940. For example, depending on the layer functionality handled by the component 199, the network entity 902 may include the CU 910; both the CU 910 and the DU 930; each of the CU 910, the DU 930, and the RU 940; the DU 930; both the DU 930 and the RU 940; or the RU 940. The CU 910 may include at least one CU processor 912. The CU processor (s) 912 may include on-chip memory 912'. In some aspects, the CU 910 may further include additional memory modules 914 and a communications interface 918. The CU 910 communicates with the DU 930 through a midhaul link, such as an F1 interface. The DU 930 may include at least one DU processor 932. The DU processor (s) 932 may include on-chip memory 932'. In some aspects, the DU 930 may further include additional memory modules 934 and a communications interface 938. The DU 930 communicates with the RU 940 through a fronthaul link. The RU 940 may include at least one RU processor 942. The RU processor (s) 942 may include on-chip memory 942'. In some aspects, the RU 940 may further include additional memory modules 944, one or more transceivers 946, antennas 980, and a communications interface 948. The RU 940 communicates with the UE 104. The on-chip memory 912', 932', 942'a nd the additional memory modules 914, 934, 944 may each be considered a computer-readable medium / memory. Each computer-readable medium / memory may be non-transitory. Each of the processors 912, 932, 942 is responsible for general processing, including the execution of software stored on the computer-readable medium / memory. The software, when executed by the corresponding processor (s) causes the processor (s) to perform the various functions described supra. The computer-readable medium / memory may also be used for storing data that is manipulated by the processor (s) when executing software.
[0109] As discussed supra, the RACH component 199 may be configured to receive, from a user equipment (UE) , a capability indication indicating a support for a respective RACH configuration for each frequency subcomponent (SC) of multiple frequency SCs. In some aspects, the RACH component 199 may be further configured to transmit a set of multiple RACH configurations associated with a set of multiple frequency SCs. The RACH component 199 may be within one or more processors of one or more of the CU 910, DU 930, and the RU 940. 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 902 may include a variety of components configured for various functions. In one configuration, the network entity 902 may include means for receiving, from a user equipment (UE) , a capability indication indicating a support for a respective RACH configuration for each frequency subcomponent (SC) of multiple frequency SCs. In some aspects, the network entity 902 may include means for transmitting a set of multiple RACH configurations associated with a set of multiple frequency SCs. In some aspects, the network entity 902 may include means for transmitting, in system information block (SIB) or a radio resource control (RRC) configuration, a mapping between the set of downlink frequency SCs and the set of uplink frequency SCs, where the mapping is a many-to-one mapping or a many-to-many mapping. In some aspects, the network entity 902 may include means for transmitting inter-SC quasi-colocation (QCL) information of the set of downlink reference signals associated with the set of downlink frequency SCs. In some aspects, the network entity 902 may include means for receiving a RACH message in a RACH occasion (RO) , where more than two uplink frequency SCs of the set of uplink frequency SCs is associated with the RO based on more than two downlink frequency SCs mapped to the more than two uplink frequency SCs being associated with quasi-co-located (QCL’ ed) downlink reference signals of the set of downlink reference signals according to the inter-SC QCL information. In some aspects, the network entity 902 may include means for transmitting a second RACH message in a second frequency SC of the more than two downlink frequency SCs. In some aspects, the network entity 902 may include means for transmitting an SC selection criteria for transmission of a RACH message. In some aspects, the network entity 902 may include means for receiving a first RACH message based on a first frequency SC of the multiple frequency SCs and a first RACH configuration associated with the first frequency SC. In some aspects, the network entity 902 may include means for receiving a second RACH message based on a second frequency SC of the multiple frequency SCs and a second RACH configuration associated with the second frequency SC. The means may be the component 199 of the network entity 902 configured to perform the functions recited by the means. As described supra, the network entity 902 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. The network entity 902 may be configured to perform operations described in connection with FIG. 7.
[0110] 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.
[0111] 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 processors 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. ”
[0112] 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.
[0113] The following aspects are illustrative only and may be combined with other aspects or teachings described herein, without limitation.
[0114] Aspect 1 is an apparatus for wireless communication at a user equipment (UE) , including: 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 is configured to: transmit, to a network node, a capability indication indicating a support for a respective RACH configuration for each frequency subcomponent (SC) of multiple frequency SCs; and receive, from the network node, a set of multiple RACH configurations associated with a set of multiple frequency SCs.
[0115] Aspect 2 is the apparatus of aspect 1, where the multiple frequency SCs is a set of uplink frequency SCs associated with a set of downlink frequency SCs, where the set of downlink frequency SCs is associated with a set of downlink reference signals, where the set of uplink frequency SCs is associated with an uplink RACH message and the set of downlink frequency SCs is associated with a downlink RACH message.
[0116] Aspect 3 is the apparatus of aspect 2, where the at least one processor is further configured to: receive, from the network node in system information block (SIB) or a radio resource control (RRC) configuration, a mapping between the set of downlink frequency SCs and the set of uplink frequency SCs, where the mapping is a many-to-one mapping or a many-to-many mapping.
[0117] Aspect 4 is the apparatus of aspect 3, where the at least one processor is further configured to: receive, from the network node, inter-SC quasi-colocation (QCL) information of the set of downlink reference signals associated with the set of downlink frequency SCs.
[0118] Aspect 5 is the apparatus of aspect 4, where the at least one processor is further configured to: transmit a RACH message in a RACH occasion (RO) , where more than two uplink frequency SCs of the set of uplink frequency SCs is associated with the RO based on more than two downlink frequency SCs mapped to the more than two uplink frequency SCs being associated with quasi-co-located (QCL’ ed) downlink reference signals of the set of downlink reference signals according to the inter-SC QCL information.
[0119] Aspect 6 is the apparatus of aspect 5, where the RACH message is included in a first frequency SC of the more than two uplink frequency SCs that corresponds to a corresponding first frequency SC of the more than two downlink frequency SCs, and where the at least one processor is further configured to: receive a second RACH message in a second frequency SC of the more than two downlink frequency SCs.
[0120] Aspect 7 is the apparatus of any of aspects 1-6, where the at least one processor is further configured to: receive, from the network node, an SC selection criteria for transmission of a RACH message.
[0121] Aspect 8 is the apparatus of any of aspects 1-7, where the at least one processor is further configured to: transmit a first RACH message based on a first frequency SC of the multiple frequency SCs and a first RACH configuration associated with the first frequency SC; and transmit a second RACH message based on a second frequency SC of the multiple frequency SCs and a second RACH configuration associated with the second frequency SC.
[0122] Aspect 9 is the apparatus of aspect 8, where a hopping pattern associated with a change from the first frequency SC to the second frequency SC is included in a system information block (SIB) or configured without signaling, or where a RACH response associated with the first RACH message indicates the second frequency SC or the second frequency SC is based on a channel quality or priority criteria.
[0123] Aspect 10 is the apparatus of any of aspects 8-9, where the second RACH message is a retransmission of the first RACH message, and where the second RACH message is associated with a same transmission power as the first RACH message.
[0124] Aspect 11 is an apparatus for wireless communication at a network node, including: 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 is configured to: receive, from a user equipment (UE) , a capability indication indicating a support for a respective RACH configuration for each frequency subcomponent (SC) of multiple frequency SCs; and transmit a set of multiple RACH configurations associated with a set of multiple frequency SCs.
[0125] Aspect 12 is the apparatus of aspect 11, where the multiple frequency SCs is a set of uplink frequency SCs associated with a set of downlink frequency SCs, where the set of downlink frequency SCs is associated with a set of downlink reference signals, where the set of uplink frequency SCs is associated with an uplink RACH message and the set of downlink frequency SCs is associated with a downlink RACH message.
[0126] Aspect 13 is the apparatus of aspect 12, where the at least one processor is further configured to: transmit, in system information block (SIB) or a radio resource control (RRC) configuration, a mapping between the set of downlink frequency SCs and the set of uplink frequency SCs, where the mapping is a many-to-one mapping or a many-to-many mapping.
[0127] Aspect 14 is the apparatus of aspect 13, where the at least one processor is further configured to: transmit inter-SC quasi-colocation (QCL) information of the set of downlink reference signals associated with the set of downlink frequency SCs.
[0128] Aspect 15 is the apparatus of aspect 14, where the at least one processor is further configured to: receive a RACH message in a RACH occasion (RO) , where more than two uplink frequency SCs of the set of uplink frequency SCs is associated with the RO based on more than two downlink frequency SCs mapped to the more than two uplink frequency SCs being associated with quasi-co-located (QCL’ ed) downlink reference signals of the set of downlink reference signals according to the inter-SC QCL information.
[0129] Aspect 16 is the apparatus of aspect 15, where the RACH message is included in a first frequency SC of the more than two uplink frequency SCs that corresponds to a corresponding first frequency SC of the more than two downlink frequency SCs, and where the at least one processor is further configured to: transmit a second RACH message in a second frequency SC of the more than two downlink frequency SCs.
[0130] Aspect 17 is the apparatus of any of aspects 11-16, where the at least one processor is further configured to: transmit an SC selection criteria for transmission of a RACH message.
[0131] Aspect 18 is the apparatus of any of aspects 11-17, where the at least one processor is further configured to: receive a first RACH message based on a first frequency SC of the multiple frequency SCs and a first RACH configuration associated with the first frequency SC; and receive a second RACH message based on a second frequency SC of the multiple frequency SCs and a second RACH configuration associated with the second frequency SC.
[0132] Aspect 19 is the apparatus of aspect 18, where a hopping pattern associated with a change from the first frequency SC to the second frequency SC is included in a system information block (SIB) or configured without signaling, or where a RACH response associated with the first RACH message indicates the second frequency SC or the second frequency SC is based on a channel quality or priority criteria.
[0133] Aspect 20 is the apparatus of any of aspects 18-19, where the second RACH message is a retransmission of the first RACH message, and where the second RACH message is associated with a same transmission power as the first RACH message.
[0134] Aspect 21 is a method of wireless communication for implementing any of aspects 1 to 10.
[0135] Aspect 22 is a computer-readable medium (e.g., a non-transitory computer-readable medium) storing computer executable code, the code when executed by at least one processor causes the at least one processor to implement any of aspects 1 to 10.
[0136] Aspect 23 is an apparatus comprising means for implementing any of aspects 1 to 10.
[0137] Aspect 24 is a method of wireless communication for implementing any of aspects 11 to 20.
[0138] Aspect 25 is a computer-readable medium (e.g., a non-transitory computer-readable medium) storing computer executable code, the code when executed by at least one processor causes the at least one processor to implement any of aspects 11 to 20.
[0139] Aspect 26 is an apparatus comprising means for implementing any of aspects 11 to 20.
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, 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 network node, a capability indication indicating a support for a respective RACH configuration for each frequency subcomponent (SC) of multiple frequency SCs; andreceive, from the network node, a set of multiple RACH configurationsassociated with a set of multiple frequency SCs.2.The apparatus of claim 1, wherein the multiple frequency SCs is a set of uplink frequency SCs associated with a set of downlink frequency SCs, wherein the set of downlink frequency SCs is associated with a set of downlink reference signals, wherein the set of uplink frequency SCs is associated with an uplink RACH message and the set of downlink frequency SCs is associated with a downlink RACH message.3.The apparatus of claim 2, wherein the at least one processor is further configured to:receive, from the network node in system information block (SIB) or a radio resource control (RRC) configuration, a mapping between the set of downlink frequency SCs and the set of uplink frequency SCs, wherein the mapping is a many-to-one mapping or a many-to-many mapping.4.The apparatus of claim 3, wherein the at least one processor is further configured to:receive, from the network node, inter-SC quasi-colocation (QCL) information of the set of downlink reference signals associated with the set of downlink frequency SCs.5.The apparatus of claim 4, wherein the at least one processor is further configured to:transmit a RACH message in a RACH occasion (RO) , wherein more than two uplink frequency SCs of the set of uplink frequency SCs is associated with the RO based on more than two downlink frequency SCs mapped to the more than two uplink frequency SCs being associated with quasi-co-located (QCL’ed) downlink reference signals of the set of downlink reference signals according to the inter-SC QCL information.6.The apparatus of claim 5, wherein the RACH message is included in a first frequency SC of the more than two uplink frequency SCs that corresponds to a corresponding first frequency SC of the more than two downlink frequency SCs, and wherein the at least one processor is further configured to:receive a second RACH message in a second frequency SC of the more than two downlink frequency SCs.7.The apparatus of claim 1, wherein the at least one processor is further configured to:receive, from the network node, an SC selection criteria for transmission of a RACH message.8.The apparatus of claim 1, wherein the at least one processor is further configured to:transmit a first RACH message based on a first frequency SC of the multiple frequency SCs and a first RACH configuration associated with the first frequency SC; andtransmit a second RACH message based on a second frequency SC of the multiple frequency SCs and a second RACH configuration associated with the second frequency SC.9.The apparatus of claim 8, wherein a hopping pattern associated with a change from the first frequency SC to the second frequency SC is included in a system information block (SIB) or configured without signaling, or wherein a RACH response associated with the first RACH message indicates the second frequency SC or the second frequency SC is based on a channel quality or priority criteria.10.The apparatus of claim 8, wherein the second RACH message is a retransmission of the first RACH message, and wherein the second RACH message is associated with a same transmission power as the first RACH message.11.An apparatus for wireless communication at a network node, comprising:at least one memory; andat 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 is configured to:receive, from a user equipment (UE) , a capability indication indicating a support for a respective RACH configuration for each frequency subcomponent (SC) of multiple frequency SCs; andtransmit a set of multiple RACH configurations associated with a set of multiple frequency SCs.12.The apparatus of claim 11, wherein the multiple frequency SCs is a set of uplink frequency SCs associated with a set of downlink frequency SCs, wherein the set of downlink frequency SCs is associated with a set of downlink reference signals, wherein the set of uplink frequency SCs is associated with an uplink RACH message and the set of downlink frequency SCs is associated with a downlink RACH message.13.The apparatus of claim 12, wherein the at least one processor is further configured to:transmit, in system information block (SIB) or a radio resource control (RRC) configuration, a mapping between the set of downlink frequency SCs and the set of uplink frequency SCs, wherein the mapping is a many-to-one mapping or a many-to-many mapping.14.The apparatus of claim 13, wherein the at least one processor is further configured to:transmit inter-SC quasi-colocation (QCL) information of the set of downlink reference signals associated with the set of downlink frequency SCs.15.The apparatus of claim 14, wherein the at least one processor is further configured to:receive a RACH message in a RACH occasion (RO) , wherein more than two uplink frequency SCs of the set of uplink frequency SCs is associated with the RO based on more than two downlink frequency SCs mapped to the more than two uplink frequency SCs being associated with quasi-co-located (QCL’ed) downlink reference signals of the set of downlink reference signals according to the inter-SC QCL information.16.The apparatus of claim 15, wherein the RACH message is included in a first frequency SC of the more than two uplink frequency SCs that corresponds to a corresponding first frequency SC of the more than two downlink frequency SCs, and wherein the at least one processor is further configured to:transmit a second RACH message in a second frequency SC of the more than two downlink frequency SCs.17.The apparatus of claim 11, wherein the at least one processor is further configured to:transmit an SC selection criteria for transmission of a RACH message.18.The apparatus of claim 11, wherein the at least one processor is further configured to:receive a first RACH message based on a first frequency SC of the multiple frequency SCs and a first RACH configuration associated with the first frequency SC; andreceive a second RACH message based on a second frequency SC of the multiple frequency SCs and a second RACH configuration associated with the second frequency SC.19.The apparatus of claim 18, wherein a hopping pattern associated with a change from the first frequency SC to the second frequency SC is included in a system information block (SIB) or configured without signaling, or wherein a RACH response associated with the first RACH message indicates the second frequency SC or the second frequency SC is based on a channel quality or priority criteria.20.The apparatus of claim 18, wherein the second RACH message is a retransmission of the first RACH message, and wherein the second RACH message is associated with a same transmission power as the first RACH message.
