Beam indication and PRACH configuration for candidate cells in L1 and L2 mobility

Abstract

An apparatus and method are described for beam indication and RACH configuration for a candidate cell in L1 / L2 mobility of a UE. The apparatus is configured to receive, from a serving cell, a switch command indicating a switch associated with L1 / L2 mobility of the apparatus from the serving cell to a candidate cell among a set of candidate cells associated with the L1 / L2 mobility. The switch command is associated with at least one of a TCI for the beam or at least one RACH parameter for a BWP of the set of candidate cells. The apparatus is also configured to communicate with the candidate cell based on at least one of the TCI for the beam or the at least one RACH parameter for the BWP.

Description

[Technical Field]

[0001]

[0001] The present disclosure relates generally to communication systems, and more particularly to wireless communication systems and user equipment mobility.

[0002] 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 telecommunications standards to provide common protocols that enable different wireless devices to communicate at city, national, regional, or even global levels. An exemplary telecommunications standard is 5G New Radio (NR). 5G NR is part of the ongoing mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., for the Internet of Things (IoT)), and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine type communications (mMTC), and ultra-reliable low latency communications (URLLC). Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. Further improvements are needed in 5G NR technology, and these improvements may also be applicable to other multiple access technologies and the telecommunications standards that employ these technologies. Summary of the Invention

[0004]

[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. It is not intended to identify key or critical elements of all aspects, nor is it intended to delineate 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]

[0005] In one aspect of the present disclosure, a method and an apparatus are provided. The apparatus is configured to receive, from a serving cell, a switch command indicating a switch associated with layer 1 or layer 2 (L1 / L2) mobility of the UE from the serving cell to a candidate cell among a set of candidate cells associated with the L1 / L2 mobility of the UE, the switch command being associated with at least one of (1) a transmission configuration indication (TCI) for a beam or (2) at least one random access channel (RACH) parameter for a bandwidth part (BWP) of the set of candidate cells. The apparatus is also configured to communicate with the candidate cell based on at least one of the TCI for the beam or the at least one RACH parameter for the BWP.

[0006] In this aspect, the method includes receiving, from a serving cell, a switch command indicating a switch associated with L1 / L2 mobility of the UE from the serving cell to a candidate cell among a set of candidate cells associated with the L1 / L2 mobility of the UE, the switch command being associated with at least one of (1) a TCI for the beam or (2) at least one RACH parameter for a BWP of the set of candidate cells. The method also includes communicating with the candidate cell based on the at least one of the TCI for the beam or the at least one RACH parameter for the BWP.

[0007]

[0007] In one aspect of the present disclosure, a method and an apparatus are provided. The apparatus is configured to configure a switch command indicating a switch associated with L1 / L2 mobility of the UE to a candidate cell among a set of candidate cells associated with L1 / L2 mobility of the UE, the switch command being associated with at least one of (1) a TCI for a beam or (2) at least one RACH parameter for a BWP of the set of candidate cells. The apparatus is also configured to transmit, for the UE, the switch command indicating a switch associated with L1 / L2 mobility of the UE to the candidate cell.

[0008] In this aspect, the method includes configuring a switch command to a candidate cell among a set of candidate cells associated with the L1 / L2 mobility of the UE, the switch command indicating a switch associated with the L1 / L2 mobility of the UE, the switch command being associated with at least one of (1) a TCI for the beam or (2) at least one RACH parameter for a BWP of the set of candidate cells. The method also includes transmitting, for the UE, the switch command to the candidate cell indicating the switch associated with the L1 / L2 mobility of the UE.

[0009] To the accomplishment of the foregoing and related ends, the one or more aspects may include the features hereinafter fully described and particularly pointed out in the claims. The following description and the drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of the various aspects may be employed. [Brief explanation of the drawings]

[0010] [Figure 1]

[0010] FIG. 1 illustrates an example of a wireless communication system and access network. [Figure 2]

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

[0012] FIG. 2B is a diagram illustrating an example of a downlink (DL) channel within a subframe, in accordance with various aspects of the present disclosure.

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

[0014] FIG. 2D is a diagram illustrating an example of an uplink (UL) channel within a subframe, in accordance with various aspects of the present disclosure. [Figure 3]

[0015] FIG. 1 illustrates an example of a base station and user equipment (UE) in an access network. [Figure 4]

[0016] FIG. 1 illustrates an example configuration for UE mobility, in accordance with various aspects of the present disclosure. [Figure 5]

[0017] FIG. 1 is a call flow diagram for wireless communication in accordance with various aspects of the present disclosure. [Figure 6]

[0018] FIG. 1 illustrates an example of beam pre-configuration for UE mobility, in accordance with various aspects of the present disclosure. [Figure 7]

[0019] FIG. 1 illustrates an example of random access channel (RACH) pre-configuration for UE mobility, in accordance with various aspects of the present disclosure. [Figure 8]

[0020] FIG. 1 illustrates an example configuration for beams and RACH in UE mobility, in accordance with various aspects of the present disclosure. [Figure 9]

[0021] 1 is a flowchart of a method of wireless communication in accordance with various aspects of the present disclosure. [Figure 10]

[0022] 1 is a flowchart of a method of wireless communication in accordance with various aspects of the present disclosure. [Figure 11]

[0023] 1 is a flowchart of a method of wireless communication in accordance with various aspects of the present disclosure. [Figure 12]

[0024] 1 is a flowchart of a method of wireless communication in accordance with various aspects of the present disclosure. [Figure 13]

[0025] FIG. 1 illustrates an example of a hardware implementation for an exemplary device and / or network entity. [Figure 14]

[0026] FIG. 2 illustrates an example of a hardware implementation for an exemplary network entity. [Figure 15]

[0027] FIG. 2 illustrates an example of a hardware implementation for an exemplary network entity. DETAILED DESCRIPTION OF THE INVENTION

[0011]

[0028] Wireless communication networks, such as LTE networks and / or 5G NR networks, can be designed for UE mobility. Such UE mobility may be Layer 3 mobility, which relies on relatively slow messaging and configuration of the UE for post-mobility communications. As an example, a UE may initially be served by a serving cell, which may include a 5G NR cell or "SCell," a combination of 5G NR and legacy protocols and / or hardware (e.g., an "SpCell" implementation), while candidate cells (e.g., legacy cells, 5G NR cells, etc.) are available to the UE for L3 mobility. The UE may receive an L3 mobility communication from the serving cell for movement via L3 mobility to one of the candidate cells as a new serving cell, and the UE then moves to the new serving cell and initiates its setup (e.g., configuration for beams, transmission configuration indication (TCI), random access channel (RACH), etc.) for communications with it.

[0012]

[0029] However, as mentioned above, L3 mobility may be relatively slow and may not allow pre-configuration for various communications associated with candidate cells for mobility. Aspects described herein provide beam indication and RACH configuration for candidate cells in L1 / L2 mobility of a UE, including pre-configuration for beam and RACH implementation with candidate cells, which may be faster and more efficient than L3 mobility. For example, a UE may receive a switch command from a serving cell indicating a switch associated with the UE's L1 / L2 mobility from the serving cell to a candidate cell among a set of candidate cells. The switch command may be associated with RACH parameter(s) for the TCI for the beam and / or BWP of the set of candidate cells. Thus, the UE may be pre-configured to communicate with the candidate cell via L1 / L2 mobility based on the RACH parameter(s) for the TCI and / or BWP for the beam, thereby reducing mobility latency.

[0013]

[0030] Various aspects relate generally to inter-cell mobility of a UE. Some aspects, more particularly, relate to L1 / L2 inter-cell mobility of a UE using pre-configuration for beams and RACH of a candidate cell. In some embodiments, the beam may be pre-configured by the serving cell via radio resource control (RRC) signaling, medium access control (MAC) control elements (MAC-CEs), and downlink control information (DCIs), and / or via the switch command itself, while the RACH may be pre-configured via RACH parameter(s) for BWP of the candidate cell via RRC signaling, including beam failure recovery configuration.

[0014]

[0031] Certain aspects of the subject matter described in this disclosure may be implemented to achieve one or more of the following potential advantages: In some embodiments, by pre-configuring beams and RACHs for candidate cells in L1 / L2 mobility, the described techniques can be used to reduce mobility latency through fast application of configurations for candidate cells, dynamic switching mechanisms between candidate cells, L1 extensions for inter-cell beam management including L1 measurements and reporting, and beam pointing, inter- and intra-frequency scenarios, etc.

[0015]

[0032] The Detailed Description, set forth below in connection with the accompanying drawings, illustrates various configurations and does not represent the only configurations in which the concepts described herein may be practiced. The Detailed Description includes specific details intended to provide a thorough understanding of the 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 to avoid obscuring such concepts.

[0016]

[0033] Several aspects of telecommunications 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 on the particular application and design constraints imposed on the overall system.

[0017]

[0034] By way of example, an element, or any portion of an element, or any combination of elements, may be implemented as a "processing system" including one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on a chip (SoC), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gate logic, discrete hardware circuits, and other suitable hardware configured to perform various functions described throughout this disclosure. One or more processors in a processing system may execute software. Software 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, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0018]

[0035] Thus, 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 or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media includes computer storage media. A storage medium may be any available medium that can be accessed by a computer. By way of example, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of 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.

[0019]

[0036] Although aspects, implementations, and / or use cases are described herein by way of example for some embodiments, additional or different aspects, implementations, and / or use cases may occur in many different configurations and scenarios. The aspects, implementations, and / or use cases described herein may be implemented across many different platform types, devices, systems, shapes, sizes, and packaging configurations. For example, the aspects, implementations, and / or use cases may occur via integrated chip implementations and other non-modular component-based devices (e.g., end-user devices, vehicles, communications devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, artificial intelligence (AI)-enabled devices, etc.). While some embodiments may or may not be specifically targeted to a use case or application, a wide variety of combined applicability of the described embodiments may arise. Aspects, implementations, and / or use cases may range from chip-level or modular components to non-modular, non-chip-level implementations, and even to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more techniques herein. In some practical settings, devices incorporating the described aspects and features may also include additional components and features for implementing and practicing the claimed and described aspects. For example, transmitting and receiving wireless signals necessarily involves several components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processor(s), interleavers, summers / analog summers, etc.). The techniques described herein can be practiced in a wide variety of devices, chip-level components, systems, distributed configurations, aggregated or non-aggregated components, end-user devices, etc., of various sizes, shapes, and configurations.

[0020]

[0037] The deployment of a communication system, such as a 5G NR system, can be configured in multiple ways using various components or parts. In a 5G NR system or network, network equipment such as a network node, network entity, network mobility element, Radio Access Network (RAN) node, core network node, network element, or base station (BS), or one or more units (or one or more components) performing base station functionality, can 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), transmission reception point (TRP), or cell) can be implemented as an aggregated base station (also known as a standalone BS or monolithic BS) or a disaggregated base station.

[0021]

[0038] A centralized 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 (e.g., one or more 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 geographically or virtually distributed across one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0022]

[0039] Base station operation or network design may take into account the aggregation characteristics of base station functions. 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 supported 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 functions across two or more units in different physical locations, as well as virtually distributing the functions of at least one unit, which may enable flexibility in network design. Various units of a disaggregated base station, or a disaggregated RAN architecture, may be configured for wired or wireless communication with at least one other unit.

[0023]

[0040] FIG. 1 is a diagram 100 illustrating an example of a wireless communication system and access network. The illustrated wireless communication system includes a disaggregated base station architecture. The disaggregated base station architecture may include one or more CUs 110 that may 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 (e.g., 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). The CUs 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 served by multiple RUs 140 simultaneously.

[0024]

[0041] Each of the units, i.e., CU 110, DU 130, RU 140, and quasi-RT RIC 125, non-RT RIC 115, and SMO framework 105, may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) over a wired or wireless transmission medium. Each of the units, or an associated processor or controller that provides instructions to the unit's communication interface, may be configured to communicate with one or more of the other units over a transmission medium. For example, a unit may include a wired interface configured to receive or transmit signals to one or more of the other units over a wired transmission medium. In addition, a unit may include a wireless interface, which may include a receiver, a transmitter, or a transceiver (such as an RF transceiver), configured to receive and / or transmit signals to one or more of the other units over a wireless transmission medium.

[0025]

[0042] In some aspects, the CU 110 may host one or more upper layer control functions. Such control functions may include Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Service Data Adaptation Protocol (SDAP), etc. Each control function may 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 functions (i.e., Central Unit-User Plane (CU-UP)), control plane functions (i.e., Central Unit-Control Plane (CU-CP)), or a combination thereof. In some implementations, the CU 110 may be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface, such as an E1 interface. The CU 110 may be implemented to communicate with the DU 130, as needed, for network control and signaling.

[0026]

[0043] The DU 130 may correspond to a logical unit including one or more base station functions for controlling 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 upper physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation, demodulation, etc.), at least in part according to a functional division such as that defined by 3GPP. In some aspects, the DU 130 may further host one or more lower PHY layers. Each layer (or module) may be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 130 or with control functions hosted by the CU 110.

[0027]

[0044] The lower layer functions may be implemented by one or more RUs 140. In some deployments, the RUs 140 controlled by the DU 130 may correspond to logical nodes hosting RF processing functions, lower PHY layer functions (such as performing fast Fourier transforms (FFTs), inverse FFTs (iFFTs), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on a functional division, such as a lower layer functional division. In such an architecture, the RU(s) 140 may be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some implementations, real-time and non-real-time aspects of control and user plane communications with the RU(s) 140 may be controlled by the corresponding DU 130. In some scenarios, this configuration may enable the DU(s) 130 and the CU 110 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0028]

[0045] 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 deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (e.g., an O1 interface). For virtualized network elements, the SMO framework 105 may be configured to interact with a cloud computing platform (e.g., an open cloud (O-cloud) 190) via a cloud computing platform interface (e.g., an O2 interface) to perform network element lifecycle management (e.g., to instantiate virtualized network elements). Such virtualized network elements may include, but are not limited to, the CU 110, the DU 130, the RU 140, and the quasi-RT RIC 125. In some implementations, the SMO framework 105 may communicate with hardware aspects of a 4G RAN, such as the open eNB (O-eNB) 111, via the O1 interface. Additionally, in some implementations, the SMO framework 105 may communicate directly with one or more RUs 140 via the O1 interface. The SMO framework 105 may also include a non-RT RIC 115 configured to support the functionality of the SMO framework 105.

[0029]

[0046] The non-RT RIC 115 may be configured to include logic functions that enable 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 quasi-RT RIC 125. The non-RT RIC 115 may be coupled to the quasi-RT RIC 125 or may communicate with the quasi-RT RIC 125 (e.g., via an A1 interface). The quasi-RT RIC 125 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources through data collection and action via an interface connecting one or more CUs 110, one or more DUs 130, or both, and the O-eNB to the quasi-RT RIC 125 (e.g., via an E2 interface).

[0030]

[0047] In some implementations, the non-RT RIC 115 may receive parameters or external enrichment information from an external server to generate the AI / ML models deployed to the quasi-RT RIC 125. Such information may be utilized by the quasi-RT RIC 125 or may be received at the SMO framework 105 or non-RT RIC 115 from non-network data sources or from network functions. In some examples, the non-RT RIC 115 or quasi-RT RIC 125 may be configured to adjust RAN behavior or performance. For example, the non-RT RIC 115 may employ AI / ML models to monitor long-term trends and patterns in performance and implement corrective actions through the SMO framework 105 (e.g., reconfiguration via O1) or through the creation of RAN management policies (e.g., A1 policies).

[0031]

[0048] At least one of the CU 110, the DU 130, and the RU 140 may be referred to as a base station 102. Thus, the base station 102 may include one or more of the CU 110, the DU 130, and the RU 140 (each component is shown with a dotted line to indicate that the 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 the UE 104. The base station 102 may include macrocells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Small cells include femtocells, picocells, and microcells. A network including both small cells 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 restricted groups known as closed subscriber groups (CSGs). The communication link between the RU 140 and the UE 104 may include uplink (UL) (also referred to as reverse link) transmissions from the UE 104 to the RU 140 and / or downlink (DL) (also referred to as forward link) transmissions from the RU 140 to the UE 104. The communication link may use multiple-input multiple-output (MIMO) antenna techniques, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may be over one or more carriers. The base station 102 / UE 104 may use spectrum with a bandwidth of up to Y MHz (e.g., 5, 10, 15, 20, 100, 400 MHz, etc.) per carrier, allocated in a carrier aggregation of up to Yx MHz (x component carriers) in total, used for transmission in each direction. The carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric for DL ​​and UL (eg, more or fewer carriers may be allocated for DL ​​than for UL).The component carriers may include a primary component carrier, which may be referred to as a primary cell (PCell), and one or more secondary component carriers, which may be referred to as a secondary cell (SCell).

[0032]

[0049] Particular UEs 104 may communicate with each other using device-to-device (D2D) communication links 158. The D2D communication links 158 may use DL / UL wireless wide area network (WWAN) spectrum. The D2D communication links 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 via various wireless D2D communication systems, such as Bluetooth, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

[0033]

[0050] The wireless communication system may further include a Wi-Fi AP 150 that communicates with UEs 104 (also referred to as Wi-Fi stations (STAs)) via communication links 154, such as in the 5 GHz unlicensed frequency spectrum. When communicating in the unlicensed frequency spectrum, the UEs 104 / AP 150 may perform clear channel assessment (CCA) before communicating to determine if a channel is available.

[0034]

[0051] The electromagnetic spectrum is often divided into various classes, bands, channels, etc. based on frequency / wavelength. For 5G NR, two initial operating bands have been identified by the frequency range designations FR1 (410 MHz to 7.125 GHz) and FR2 (24.25 GHz to 52.6 GHz). Although portions of FR1 are above 6 GHz, FR1 is often referred to (interchangeably) as the “sub-6 GHz” band in various documents and papers. Similar nomenclature issues may arise with respect to FR2, which is often referred to (interchangeably) as the “millimeter wave” band in documents and papers, even though it is different from the extremely high frequency (EHF) band (30 GHz to 300 GHz), which is identified by the International Telecommunications Union (ITU) as the “millimeter wave” band.

[0035]

[0052] Frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR studies have identified operating bands for these mid-band frequencies as the frequency range designated FR3 (7.125 GHz to 24.25 GHz). Frequency bands included within FR3 may inherit FR1 and / or FR2 characteristics, thus effectively extending the characteristics of FR1 and / or FR2 to the mid-band frequencies. 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 the frequency ranges designated FR2-2 (52.6 GHz to 71 GHz), FR4 (71 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher frequency bands is included within the EHF band.

[0036]

[0053] With the above aspects in mind, unless otherwise specified, as used herein, terms such as "sub-6 GHz" may broadly refer to frequencies that may be below 6 GHz, may be within FR1, or may include mid-band frequencies. Further, unless otherwise specified, as used herein, terms such as "millimeter wave" may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR2-2, and / or FR5, or may be within the EHF band.

[0037]

[0054] The base station 102 and the UE 104 may each include multiple 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.

[0038]

[0055] The base station 102 may include and / or be referred to as a gNB, Node B, eNB, access point, base transceiver station, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), TRP, network node, network entity, network equipment, or some other suitable terminology. The base station 102 may be implemented as an aggregated (monolithic) base station having an integrated access and backhaul (IAB) node, a relay node, a sidelink node, a baseband unit (BBU) (including a CU and a DU) and a RU, or as a disaggregated base station including one or more of a CU, a DU, and / or a RU. A set of base stations, which may include disaggregated base stations and / or aggregated base stations, may be referred to as a next generation (NG) RAN (NG-RAN).

[0039]

[0056] 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 a control node that handles signaling between the UE 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 authentication and key agreement (AKA) credential generation, user identity handling, access authorization, and subscription management. The one or more location servers 168 are shown as including a Gateway Mobile Location Center (GMLC) 165 and a Location Management Function (LMF) 166. However, in general, 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, LMF 166, a position determination entity (PDE), a serving mobile location center (SMLC), a mobile positioning center (MPC), etc. The GMLC 165 and LMF 166 support UE location services. The GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE positioning information.The LMF 166 receives measurements and assistance information from the NG-RAN and the UE 104 via the AMF 161 to calculate the position of the UE 104. The NG-RAN may utilize one or more positioning methods to determine the position of the UE 104. Positioning the UE 104 may include signal measurements, position estimation, and optional velocity calculations based on these measurements. The signal measurements may be performed by the UE 104 and / or the base station 102 serving the UE 104. The signals measured may include a satellite positioning system (SPS) 170 (e.g., one or more of a Global Navigation Satellite System (GNSS), a global position system (GPS), a non-terrestrial network (NTN), or other satellite position / location system), an LTE signal, a wireless local area network (WLAN) signal, a Bluetooth signal, a terrestrial beacon system (TBS), sensor-based information (e.g., barometric pressure sensor, motion sensor), an NR enhanced cell ID (NR E-CID) method, an NR signal (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), or a LTE signal (e.g., a LTE signal, a wireless local area network (WLAN) signal, a Bluetooth signal, a terrestrial beacon system (TBS)), sensor-based information (e.g., barometric pressure sensor, motion sensor), an NR enhanced cell ID (NR E-CID) method, an NR signal (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), or a LTE signal (e.g., a LTE signal ... The signal may be based on one or more of UL Time Domain Observation (TDOA), UL Angle-of-Arrival (UL-AoA) positioning, and / or other systems / signals / sensors.

[0040]

[0057] Examples of UEs 104 include a cellular phone, a smartphone, 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., an 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 cooking appliance, a healthcare device, an implant, a sensor / actuator, a display, or any other similarly functional device. Some of the UEs 104 may be referred to as IoT devices (e.g., a parking meter, a gas pump, a toaster, a vehicle, a heart monitor, etc.). The UEs 104 may also be referred to as stations, mobile stations, subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless terminals, remote terminals, handsets, user agents, mobile clients, clients, 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 configuration, where one or more of these devices may collectively access the network and / or may individually access the network.

[0041]

[0058] Referring again to FIG. 1 , in some aspects, UE 104 may have a mobility component 198 (“component 198”) that may be configured to receive a switch command from a serving cell indicating a switch associated with the UE's L1 / L2 mobility from the serving cell to a candidate cell among a set of candidate cells associated with the UE's L1 / L2 mobility, the switch command being associated with at least one of (1) a TCI for the beam or (2) at least one RACH parameter for a BWP of the set of candidate cells. Component 198 is also configured to communicate with the candidate cell based on at least one of the TCI for the beam or the at least one RACH parameter for the BWP. In an aspect, component 198 may be configured to receive at least one of a TCI configuration for the candidate cell or a RACH configuration for the candidate cell prior to receiving the switch command, the TCI for the beam being based on the TCI configuration and the at least one RACH parameter being based on the RACH configuration. In an aspect, component 198 can be configured to receive a TCI for the beam from the serving cell via RRC signaling and prior to receiving the switch command, the TCI for the beam including at least one of a first legacy TCI state for periodic CSI-RS, first legacy spatial relationship information for periodic SRS or PUCCH, or a list of legacy TCI states for PDSCH. In an aspect, component 198 can be configured to receive activation of the TCI for the beam via MAC-CE including at least one of a second legacy TCI state for CORESET or semi-persistent CSI-RS, second legacy spatial relationship information for at least one of semi-persistent SRS, aperiodic SRS, or PUCCH, a subset of legacy TCI states for PDSCH, or at least one SRS or path loss RS for at least one physical uplink shared channel (PUSCH). In an aspect, component 198 can be configured to receive DCI indicating a third legacy TCI state of the subset of legacy TCI states for the PDSCH.In an aspect, component 198 can be configured to receive a TCI for the beam from the serving cell via RRC signaling and prior to receiving the switching command, the TCI for the beam including a first aggregated TCI state for periodic CSI-RS or periodic SRS configured to not follow the aggregated TCI indication, or at least one of a list of downlink TCI states, a list of joint TCI states, or a list of uplink TCI states. In an aspect, component 198 can be configured to receive an activation of the TCI for the beam via MAC-CE including a second aggregated TCI state for at least one of CORESET, semi-persistent CSI-RS, semi-persistent SRS, or aperiodic SRS configured to not follow the aggregated TCI indication. In an aspect, component 198 can be configured to receive DCI indicating at least one of a joint TCI state for at least one of a PDSCH, a PDCCH, a PUSCH, a PUCCH, a CSI-RS, or an SRS configured to follow the joint TCI indication, a downlink TCI state for at least one of a PDSCH, a PDCCH, or a CSI-RS configured to follow the joint TCI indication, or an uplink TCI state for a PUSCH, a PUCCH, or an SRS configured to follow the joint TCI indication. In an aspect, component 198 can be configured to receive at least one RACH parameter for BWP of the set of candidate cells from the serving cell via the at least one transceiver and RRC signaling, the at least one RACH parameter including at least one of (1) a PRACH parameter or (2) at least one BFR parameter.In some aspects, base station 102 can have a mobility component 199 (“component 199”) that can be configured to configure a switch command indicating a switch associated with L1 / L2 mobility of the UE to a candidate cell among a set of candidate cells associated with the UE's L1 / L2 mobility, the switch command being associated with at least one of (1) a TCI for the beam or (2) at least one RACH parameter for a BWP of the set of candidate cells. Component 199 is also configured to transmit, for the UE, the switch command indicating a switch associated with L1 / L2 mobility of the UE to the candidate cell. In an aspect, component 199 can be configured to transmit, for the UE, at least one of a TCI configuration for the candidate cell or a RACH configuration for the candidate cell prior to transmitting the switch command, the TCI for the beam being based on the TCI configuration and the at least one RACH parameter being based on the RACH configuration. In an aspect, component 199 can be configured to transmit, for the UE via RRC signaling and before transmitting the switching command, a TCI for the beam, where the TCI for the beam includes at least one of a first legacy TCI state for periodic CSI-RS, first legacy spatial relationship information for periodic SRS or PUCCH, or a list of legacy TCI states for PDSCH. In an aspect, component 199 can be configured to transmit, for the UE, an activation of the TCI for the beam via MAC-CE including at least one of a second legacy TCI state for CORESET or semi-persistent CSI-RS, second legacy spatial relationship information for at least one of semi-persistent SRS, aperiodic SRS, or PUCCH, a subset of legacy TCI states for PDSCH, or path loss RS for at least one SRS or at least one PUSCH. In an aspect, component 199 can be configured to transmit, for the UE, a DCI indicating a third legacy TCI state of the subset of legacy TCI states for the PDSCH.In an aspect, component 199 can be configured to transmit, for the UE via RRC signaling and before receiving the switching command, a TCI for the beam, where the TCI for the beam includes a first consolidated TCI state for periodic CSI-RS or periodic SRS configured to not follow the consolidated TCI indication, or at least one of a list of downlink TCI states, a list of joint TCI states, or a list of uplink TCI states. In an aspect, component 199 can be configured to transmit, for the UE via MAC-CE, an activation of the TCI for the beam including a second consolidated TCI state for at least one of CORESET, semi-persistent CSI-RS, semi-persistent SRS, or aperiodic SRS configured to not follow the consolidated TCI indication. In an aspect, component 199 can be configured to transmit, for the UE, a DCI indicating at least one of a joint TCI state for at least one of a PDSCH, a PDCCH, a PUSCH, a PUCCH, a CSI-RS, or an SRS configured to follow the joint TCI indication, a downlink TCI state for at least one of a PDSCH, a PDCCH, or a CSI-RS configured to follow the joint TCI indication, or an uplink TCI state for a PUSCH, a PUCCH, or an SRS configured to follow the joint TCI indication. In an aspect, component 199 can be configured to transmit, for the UE via the at least one transceiver and RRC signaling, at least one RACH parameter for beamforming of a set of candidate cells, the at least one RACH parameter including at least one of (1) a PRACH parameter or (2) at least one BFR parameter. That is, aspects provide L1 / L2 mobility for the UE through pre-configuration for beam TCI and RACH of candidate cells, dynamic mobility application, and reduced mobility latency.

[0042]

[0059] Figure 2A is a diagram 200 illustrating an example of a first subframe in a 5G NR frame structure. Figure 2B is a diagram 230 illustrating an example of a DL channel in a 5G NR subframe. Figure 2C is a diagram 250 illustrating an example of a second subframe in a 5G NR frame structure. Figure 2D is a diagram 280 illustrating an example of a UL channel in a 5G NR subframe. The 5G NR frame structure may be frequency division duplexed (FDD) where, for a particular set of subcarriers (carrier system bandwidth), subframes within the set of subcarriers are dedicated to either DL or UL, or time division duplexed (TDD) where, for a particular set of subcarriers (carrier system bandwidth), subframes within the set of subcarriers are dedicated to both DL and UL. In the examples provided by FIGS. 2A and 2C, the 5G NR frame structure is assumed to be TDD, with subframe 4 configured (mostly DL) using slot format 28, where D is DL, U is UL, and F is flexible for DL / UL use, and subframe 3 configured (all UL) using slot format 1. While subframes 3 and 4 are shown with slot formats 1 and 28, respectively, any particular subframe can be configured to have any of the various available slot formats 0 through 61. Slot formats 0 and 1 are all DL and all UL, respectively. The other slot formats 2 through 61 contain a mix of DL symbols, UL symbols, and flexible symbols. The UE is configured to have the slot format through a received slot format indicator (SFI) (either dynamically through DL control information (DCI) or semi-statically / statically through radio resource control (RRC) signaling). Note that the following description also applies to TDD 5G NR frame structures.

[0043]

[0060] 2A-2D illustrate one frame structure, and embodiments of the present disclosure may be applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10 ms) may be divided into 10 equally sized subframes (1 ms). Each subframe may include one or more time slots. A subframe may also include a minislot, 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. With a normal CP, each slot may include 14 symbols, and with an extended CP, each slot may include 12 symbols. Symbols on the DL may be CP orthogonal frequency division multiplexing (CP-OFDM) symbols. The symbols on the UL can be CP-OFDM symbols (for high-throughput scenarios) or Discrete Fourier Transform (DFT) Spread OFDM (DFT-s-OFDM) symbols (for power-limited scenarios, when limited to single-stream transmission). The number of slots in a subframe is based on CP and numerology. The numerology defines the subcarrier spacing (SCS) (see Table 1). The symbol length / duration can be scaled by 1 / SCS.

[0044] [Table 1]

[0045]

[0061] For normal CP (14 symbols / slot), different number logics μ0-μ4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For extended CP, number logic 2 allows 4 slots per subframe. Therefore, for normal CP and number logic μ, 14 symbols / slot and 2 μ There are slots / subframes. The subcarrier spacing is 2μ * μ may be equal to 15 kHz, where μ is a numerology from 0 to 4. Therefore, 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 proportional to the subcarrier spacing. Figures 2A-2D provide an example of a normal CP with 14 symbols per slot and a 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 Figure 2B), which are frequency division multiplexed. Each BWP may have a specific numerology and CP (normal or extended).

[0046]

[0062] A resource grid may be used to represent the frame structure. Each time slot contains resource blocks (RBs) (also called physical RBs (PRBs)), spanning 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0047]

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

[0048]

[0064] Figure 2B shows 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), where each CCE includes 6 RE groups (REGs), and each REG includes 12 consecutive REs within an OFDM symbol of an RB. The PDCCHs within one BWP may be referred to as a control resource set (CORESET). During a PDCCH monitoring occasion on the CORESET, a UE is configured to monitor PDCCH candidates within a PDCCH search space (e.g., a common search space, a UE-specific search space), where the PDCCH candidates have different DCI formats and aggregation levels. Additional BWPs may be deployed at higher and / or lower frequencies across the channel bandwidth. A primary synchronization signal (PSS) may be present in symbol 2 of a particular subframe of a frame. The PSS is used by the UE 104 to determine the subframe / symbol timing and the physical layer identity. A secondary synchronization signal (SSS) may be present in symbol 4 of a particular subframe of a frame. The SSS is used by the UE to determine the group number of the physical layer cell identity and the timing of the radio frame. Based on the physical layer identity and the group number of the physical layer cell identity, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS.The physical broadcast channel (PBCH), which carries the master information block (MIB), may be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (also called an SS block (SSB)). The MIB provides the number of RBs in the system bandwidth and the system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information not transmitted over the PBCH, such as system information blocks (SIBs), and paging messages.

[0049]

[0065] As shown in FIG. 2C , some of the REs carry DM-RS (denoted as R for one particular configuration, although 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 a short or long PUCCH is transmitted and on the specific 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 the UE may transmit the SRS in one of the combs. The SRS may be used by the base station for channel quality estimation to enable frequency-dependent scheduling on the UL.

[0050]

[0066] 2D shows an example of various UL channels within a subframe of a frame. The PUCCH, in one configuration, may be arranged as shown. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQIs), precoding matrix indicators (PMIs), rank indicators (RIs), and hybrid automatic repeat request (HARQ) acknowledgment (ACK) (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUSCH carries data and, in addition, may be used to carry buffer status reports (BSRs), power headroom reports (PHRs), and / or UCIs.

[0051]

[0067] 3 is a block diagram of a base station 310 communicating 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 functions. Layer 3 includes the RRC layer, and Layer 2 includes the Service Data Adaptation Protocol (SDAP) layer, the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer, and the Medium Access Control (MAC) layer. The controller / processor 375 is responsible for RRC layer functions associated with broadcasting system information (e.g., MIBs, 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 functions associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functions associated with forwarding higher layer packet data units (PDUs), error correction via ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and mapping of logical channels to transport channels, multiplexing MAC SDUs onto transport blocks (TBs), and MAC SDUs from TBs. It provides MAC layer functions associated with demultiplexing of SDUs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0052]

[0068] The transmit (TX) processor 316 and receive (RX) processor 370 implement Layer 1 functionality associated with various signal processing functions. Layer 1, including the physical (PHY) layer, may include error detection on transport channels, forward error correction (FEC) encoding / decoding of transport channels, interleaving, rate matching, mapping onto physical channels, modulation / demodulation of physical channels, and MIMO antenna processing. The TX processor 316 processes 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), and M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be split into parallel streams. Each stream can then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domain, and then combined together using an Inverse Fast Fourier Transform (IFFT) to generate a physical channel carrying a time-domain OFDM symbol stream. This OFDM stream is spatially precoded to generate multiple spatial streams. Channel estimates from a channel estimator 374 can be used to determine coding and modulation schemes and for spatial processing. The channel estimates can be derived from a reference signal and / or channel condition feedback transmitted by the UE 350. Each spatial stream can then be provided to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx can modulate a radio frequency (RF) carrier with the respective spatial stream for transmission.

[0053]

[0069] 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 a 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 can 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, the RX processor 356 can combine them 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, as well as the reference signal, are recovered and demodulated by determining the most likely signal constellation point transmitted by the base station 310. These soft decisions may be based on channel estimates calculated by a channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally transmitted by the base station 310 on the physical channel, which are then provided to a controller / processor 359, which implements Layer 3 and Layer 2 functions.

[0054]

[0070] The controller / processor 359 can be associated with a memory 360 that stores program codes and data. The memory 360 may be referred to as a computer-readable medium. In the UL, the controller / processor 359 is responsible for demultiplexing between transport and logical channels, packet reassembly, decoding, 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.

[0055]

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

[0056]

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

[0057]

[0073] UL transmissions are processed at the base station 310 in a manner similar to that described for the receiver functions at the UE 350. Each receiver 318Rx receives a signal through its corresponding antenna 320. Each receiver 318Rx recovers the information modulated onto the RF carrier and provides the information to the RX processor 370.

[0058]

[0074] The controller / processor 375 can be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer-readable medium. In the UL, the controller / processor 375 is responsible for demultiplexing between transport and logical channels, packet reassembly, decoding, header decompression, and 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.

[0059]

[0075] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to perform aspects associated with the mobility component 198 of Figure 1. At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to perform aspects associated with the mobility component 199 of Figure 1.

[0060]

[0076] Wireless communication networks, such as LTE networks and / or 5G NR networks, can be designed for UE mobility. Such UE mobility may be Layer 3 mobility, which relies on relatively slow messaging and configuration of the UE for post-mobility communications. As an example, a UE may initially be served by a serving cell, which may include a 5G NR cell or "SCell," a combination of 5G NR and legacy protocols and / or hardware (e.g., an "SpCell" implementation), while candidate cells (e.g., legacy cells, 5G NR cells, etc.) are available to the UE for L3 mobility. The UE may receive an L3 mobility communication from the serving cell for movement via L3 mobility to one of the candidate cells as a new serving cell, and the UE then moves to the new serving cell and initiates its setup (e.g., configuration for beams, transmission configuration indication (TCI), random access channel (RACH), etc.) for communications with it.

[0061]

[0077] However, as mentioned above, L3 mobility can be relatively slow and may not allow for pre-configuration of various communications associated with candidate cells for mobility. Aspects described herein provide beam indication and RACH configuration for candidate cells in L1 / L2 mobility of a UE, including pre-configuration of beams and RACHs for candidate cells, which may be faster and more efficient than L3 mobility. That is, aspects provide pre-configuration and maintenance of multiple candidate cells to enable fast application of configurations for candidate cells and target / new serving cells. For example, a UE may receive a switch command from a serving cell indicating a switch associated with the UE's L1 / L2 mobility from the serving cell to a candidate cell among a set of candidate cells. The switch command may be associated with a TCI for the beam and / or RACH parameter(s) for the BWP of the set of candidate cells.

[0062]

[0078] Thus, a UE can be pre-configured to communicate with a candidate cell via L1 / L2 mobility based on the TCI for the beam and / or RACH parameter(s) for the BWP, thereby reducing mobility latency. The described techniques can reduce mobility latency through fast application of configuration for the candidate cell, dynamic switching mechanisms between candidate cells via L1 / L2 signaling (e.g., via mobility commands), L1 extensions for inter-cell beam management including L1 measurements and reporting, and beam indication, inter-frequency and intra-frequency scenarios, timing advance management, CU-DU interface signaling to further support L1 / L2 mobility, FR2-specific extensions, standalone, CA, and NR-DC scenario support for serving cell change within one configured grant (CG), intra-DU and intra-CU / inter-DU applicability, etc. Aspects may be applicable to intra-frequency and / or inter-frequency scenarios, and FR1 and / or FR2 implementations, including source and candidate / target cells that are synchronous or asynchronous.

[0063]

[0079] 4 is a diagram 400 illustrating an example configuration for UE mobility, according to various aspects. In diagram 400, UE 402 may initially be served by SpCell 404, while three candidate cells (e.g., a pre-configured set of candidate SpCells)—SpCell 406, SpCell 408, and SpCell 410—are available to UE 402 for L3 mobility. After measurements are performed by UE 402 on the illustrated SpCells, UE 402 may receive an L3 mobility communication (e.g., a mobility command) from SpCell 404 for movement via L3 mobility to SpCell 406 as its new serving cell. UE 402 then moves to SpCell 406 and initiates its setup (e.g., configuration for beams, RACH, etc.) for communication with SpCell 406.

[0064]

[0080] FIG. 5 is a call flow diagram 500 for wireless communications, according to various aspects. The call flow diagram 500 illustrates beam direction and RACH pre-configuration for a candidate cell in L1 / L2 mobility in a wireless device (e.g., a UE 502) for application in a serving cell, such as a network node (e.g., a base station 504, such as a gNB or other type of base station, as shown), and in a candidate cell, such as a target network node (e.g., a base station 505, such as a gNB or other type of base station, as shown), according to various aspects. The aspects described with respect to the base station 504 can be performed by the base station in an aggregated manner and / or by one or more components of the base station in a non-aggregated manner. Additionally or alternatively, aspects can be performed autonomously by the UE 502 in addition to and / or instead of operation of the base station 504. The base station 504, in aspects, can be configured to provide at least one cell.

[0065]

[0081] In the illustrated aspect, the UE 502 can be configured to receive configuration(s) 506 provided from the base station 504. The configuration(s) 506 can include a TCI configuration for a candidate cell (e.g., the base station 505) and / or a RACH configuration for the candidate cell (e.g., the base station 505), where the TCI for the beam as described herein can be based on the TCI configuration, and where at least one RACH parameter as described herein can be based on the RACH configuration. In an aspect, the configuration(s) 506 can include a single signaling or multiple signaling, and the configuration(s) 506 can be provided by the base station 504 via RRC signaling. As described in further detail below, the configuration(s) 506 can be based on previous L1 measurements of a set of candidate cells (e.g., including the base station 505) performed by the UE 502.

[0066]

[0082] The base station 504 can be configured to provide the parameter(s) 508, and the UE 502 can be configured to receive the parameter(s) 508. The parameter(s) 508 can include TCI for the beam(s) of the candidate cell and / or RACH parameter(s) for the BWP of the candidate cell (e.g., a set of candidate cells including the base station 505). In an aspect, the TCI for the beam(s) can include legacy and / or combined (e.g., joint) TCI status and related information of the candidate cell. In an aspect, the parameter(s) 508 can be received by the UE 502 in one or more signalings and can be provided via RRC signaling, MAC-CE, and / or DCI. Further details regarding the parameter(s) 508 are described below with respect to FIGS. 7 and 8.

[0067]

[0083] The base station 504 can be configured to configure 509 a switch command 510 for L1 / L2 mobility (e.g., handoff or transfer) of the UE 502 from a serving cell (e.g., base station 504) to a candidate cell (e.g., base station 505) among a set of candidate cells available for L1 / L2 mobility of the UE 502. In an aspect, the switch command 510 can be associated with a TCI for the beam(s) and / or at least one RACH parameter for BWP of the set of candidate cells (e.g., including the base station 505). In some aspects, the switch command 510 can dynamically include the TCI for the beam(s) in addition to or instead of the TCI for the beam(s) of the parameter(s) 508 being provided via RRC / MAC-CE / DCI. In such an aspect, the switching command 510 may further include a MAC-CE that activates a TCI for the beam(s) for the base station 505 and / or a DCI that indicates the TCI for the beam(s).

[0068]

[0084] The switch command 510 may be provided from the base station 504 and received by the UE 502. The switch command 510 may indicate a switch (e.g., handoff or transfer) associated with L1 / L2 mobility of the UE 502 from a serving cell (e.g., base station 504) to a candidate cell (e.g., base station 505) of a set of candidate cells available for L1 / L2 mobility of the UE 502.

[0069]

[0085] After receiving the switch command 510, the UE 502 can be configured to receive and / or transmit communication 512 with the target candidate cell (e.g., the base station 505 acting as the new serving cell) based on at least one RACH parameter for the TCI and / or BWP for the beam(s). In an aspect, because the UE is pre-configured with the RACH parameter(s) for the TCI for the beam(s) and / or BWP of the base station 505, the UE 502 can be configured to immediately receive and / or transmit communication 512 with the base station 505 after completion of the handoff initiated by the switch command 510. That is, after the handoff to the base station 505, the UE can skip performing configuration for the TCI / RACH because of the pre-configuration(s) for the TCI / RACH, thus achieving reduced mobility latency.

[0070]

[0086] 6 is a diagram 600 illustrating an example for beam and RACH pre-configuration for UE mobility, according to various aspects. In diagram 600, UE 602 may initially be served by SpCell 604, but by way of example and not limitation, three candidate cells (e.g., pre-configured candidate SpCell set) are available to UE 602 for L1 / L2 mobility: SpCell 606, SpCell 608, and SpCell 610. After measurements 612, which may be L1 measurements, are performed by UE 602 on SpCell 606, SpCell 608, and SpCell 610 as shown, UE 602 may be provided with pre-configuration information 614 (e.g., TCI for the candidate cell's beam(s) and / or RACH parameter(s) for the candidate cell's BWP). In an aspect, the pre-configuration information 614 can be provided via RRC / MAC-CE / DCI and / or mobility command 616 .

[0071]

[0087] The UE 602 may receive a mobility command 616 (e.g., after and / or including the pre-configuration information 614), which may move the UE 602 via L1 / L2 mobility from a serving cell, e.g., SpCell 604, to a candidate cell, e.g., SpCell 606, that will become the new serving cell upon handoff. Thus, the UE 602 is enabled to receive and / or transmit communication 618 with the SpCell 606 upon completion of the handoff based on the pre-configuration for beams, RACH, etc., as described herein. That is, because the pre-configuration for the TCI and RACH as described herein has been performed, additional configuration and / or setup for receiving and / or transmitting communication 618 may be skipped, thus reducing mobility latency for the UE handoff.

[0072]

[0088] 7 is a diagram 700 illustrating an example for beam pre-configuration for UE mobility, according to various aspects. Diagram 700 may be a further aspect of call flow diagram 500 of FIG. 5 and illustrates configurations 720 for legacy TCI, 730 for unified TCI, and 740 for command-based TCI for L1 / L2 mobility of a UE 702 in a serving cell (e.g., base station 704), each with pre-configuration for beam setup in a candidate / new cell (e.g., base station 705) before moving from the serving cell to the candidate / new cell (e.g., from base station 704 to base station 705).

[0073]

[0089] For example, configuration for legacy TCI 720 shows UE 702 receiving RRC signaling 706, MAC-CE 708, DCI 710, and mobility command 712 from base station 704 for L1 / L2 movement to base station 705. In configuration for legacy TCI 720, RRC signaling 706 provided by base station 704 and received by UE 702 may include at least one of a first legacy TCI state for periodic CSI-RS, legacy spatial relationship information for periodic SRS or PUCCH, and / or a list of legacy TCI states for PDSCH. In the configuration 720 for legacy TCI, the MAC-CE 708 provided by the base station 704 and received by the UE 702 may include at least one of a second legacy TCI state for CORESET or semi-persistent CSI-RS, legacy spatial relationship information for at least one of semi-persistent SRS, aperiodic SRS, or PUCCH, a subset of legacy TCI states for PDSCH, and / or a path loss RS for at least one SRS or at least one PUSCH. In the configuration 720 for legacy TCI, the DCI 710 provided by the base station 704 and received by the UE 702 may indicate a third legacy TCI state of the subset of legacy TCI states for PDSCH. The UE 702 may receive a legacy TCI state indication for each channel or reference signal.

[0074]

[0090] Based on receiving the mobility command 708, the UE 702 can move via L1 / L2 mobility from the base station 704 to the base station 705 with which it has already configured a beam(s) for communication with the base station 705, as described above.

[0075]

[0091] The configuration for joint TCI 730 also shows the UE 702 receiving RRC signaling 706, MAC-CE 708, DCI 710, and mobility command 712 from the base station 704 for L1 / L2 movement to the base station 705, but in the configuration 730, the information / configuration(s) provided to the UE 702 for joint TCI differs from that provided in the configuration 720. In the configuration for joint TCI 730, the RRC signaling 706 provided by the base station 704 and received by the UE 702 may include a first joint TCI state for periodic CSI-RS or periodic SRS configured not to follow the joint TCI indication and / or at least one of a list of joint TCI states, a list of downlink TCI states, and a list of uplink TCI states. In the configuration 730 for the joint TCI, the MAC-CE 708 provided by the base station 704 and received by the UE 702 may include at least one of a second joint TCI state for at least one of CORESET, semi-persistent CSI-RS, semi-persistent SRS, and / or aperiodic SRS configured to not follow the joint TCI indication. In the configuration 730 for the joint TCI, the DCI 710 provided by the base station 704 and received by the UE 702 may indicate a joint TCI state for at least one of the PDSCH, PDCCH, PUSCH, PUCCH, CSI-RS, or SRS configured to follow the joint TCI indication, a downlink TCI state for at least one of the PDSCH, PDCCH, or CSI-RS configured to follow the joint TCI indication, and / or an uplink TCI state for the PUSCH, PUCCH, or SRS configured to follow the joint TCI indication. The UE 702 may receive a joint TCI status indication for multiple channels or reference signals.

[0076]

[0092] Based on receiving the mobility command 708, the UE 702 can move via L1 / L2 mobility from the base station 704 to the base station 705 with which it has already configured a beam(s) for communication with the base station 705, as described above.

[0077]

[0093] The configuration 740 for command-based TCI also indicates that the UE 702 receives a mobility command 712 from the base station 704 for an L1 / L2 movement to the base station 705. That is, aspects include the ability of the UE 702 to be pre-configured for L1 / L2 mobility prior to moving from the base station 704 to the base station 705 via the mobility command 712 without the RRC signaling 706, the MAC-CE 708, and / or the DCI 710 described above for the configurations 720 and 730. The mobility command 712 in the configuration 740 may include at least one of a first legacy TCI state for periodic CSI-RS, legacy spatial relationship information for periodic SRS or PUCCH, a second legacy TCI state for CORESET or semi-persistent CSI-RS, legacy spatial relationship information for at least one of semi-persistent SRS, aperiodic SRS, or PUCCH, a path loss RS for at least one of SRS or PUSCH, and / or a third legacy TCI state for PDSCH. The mobility command 712 may include a MAC-CE that may activate a TCI for the beam, and the mobility command 712 may include a DCI that may indicate the TCI for the beam.

[0078]

[0094] Based on receiving the mobility command 708, the UE 702 can move via L1 / L2 mobility from the base station 704 to the base station 705 with which it has already configured a beam(s) for communication with the base station 705, as described above.

[0079]

[0095] 8 is a diagram 800 illustrating an example for RACH pre-configuration for UE mobility, according to various aspects. Diagram 800 may be a further aspect of call flow diagram 500 of FIG. 5 and illustrates configuration 820 for L1 / L2 mobility of UE 802 in a serving cell (e.g., base station 804) with pre-configuration for RACH setup for BWP of a set of candidate cells, including in the candidate / new cell (e.g., base station 805), before moving from the serving cell to the candidate / new cell (e.g., from base station 804 (serving) to base station 805 (candidate / new / target)).

[0080]

[0096] For example, configuration for RACH pre-configuration for UE mobility 820 shows a UE 802 receiving RRC signaling 806 and a mobility command 808 from a base station 804 for L1 / L2 movement to a base station 805. In the configuration for RACH pre-configuration 820, the RRC signaling 806 provided by the base station 804 and received by the UE 802 may include at least one RACH parameter for the BWP of at least one candidate cell, e.g., base station 805, including PRACH parameter(s) and / or at least one beam failure recovery (BFR) parameter for transmission in the BWP of the candidate cell.

[0081]

[0097] In aspects, the RACH parameter(s) may include at least one of a general PRACH parameter (e.g., "rach-ConfigGeneric"), a total number of PRACH preambles, a number of SSBs per RACH occasion, an SSB threshold for selecting a PRACH (e.g., associated with SSB selection and corresponding PRACH resource selection for path loss estimation and transmission or retransmission operations), an initial value of a PRACH contention resolution timer, a root sequence for the PRACH, a subcarrier spacing for the PRACH, a first configuration of an unrestricted set, a second configuration of at least one type of restricted set, and / or a transform precoder indication for Message 3 (Msg3) transmission. In some aspects, the SSB-based PRACH may be utilized for an uplink BWP when the linked downlink BWP (e.g., having the same BWP identifier as the uplink BWP) is the initial downlink BWP or a downlink BWP that includes an SSB associated with the initial downlink BWP in the candidate cell. In an aspect, the PRACH parameter(s) may include at least one of the number of PRACH transmission occasions in a time instance based on FDM, the offset of the lowest PRACH transmission occasion in the frequency domain relative to the initial PRB, the maximum number of random access preamble transmissions performed before a failure is declared, the power ramping step on the PRACH, and / or the Message 2 random access response window length in number of slots.In an aspect, the BFR parameter(s) may include at least one of a PRACH configuration for BFR (e.g., “rach-ConfigBFR”, “rach-ConfigGeneric”), a root sequence for PRACH-based BFR, a candidate beam threshold (e.g., “rsrp-ThresholdSSB”), a candidate beam list (e.g., “candidateBeamRSList”), a number of SSBs per RACH occasion for PRACH-based BFR, a mask for PRACH-based BFR transmission (e.g., “ra-ssb-OccasionMaskIndex”), a BFR search space identifier for PRACH-based BFR, a BFR timer for PRACH-based BFR (e.g., “beamFailureRecoveryTimer”), etc. In an aspect, the PRACH-based BFR may be configurable in the candidate special cell.

[0082]

[0098] Based on receiving the mobility command 808, the UE 802 can move via L1 / L2 mobility from the base station 804 to the base station 805 that has already configured a RACH for communication with the base station 805, as described above.

[0083]

[0099] 9 is a flowchart 900 of a method of wireless communication, according to various aspects. The method may be performed by a UE (e.g., UE 104 / 402 / 502 / 602 / 702 / 802, device 1304). In some aspects, the method may include aspects described in connection with the communication flow of FIG. 5 and / or aspects described in FIGS. 6, 7, and 8. The method provides improved UE mobility, enabling the UE to utilize L1 / L2 mobility through pre-configuration of TCI for beams and pre-configuration of RACH for BWP of candidate cells, as well as dynamic pre-configuration via mobility commands that improve mobility latency.

[0084]

[0100] At 902, the UE receives a switch command from a serving cell indicating a switch associated with L1 / L2 mobility of the UE from the serving cell to a candidate cell among a set of candidate cells associated with the UE's L1 / L2 mobility, the switch command being associated with at least one of (1) a TCI for a beam or (2) at least one RACH parameter for a BWP of the set of candidate cells. As an example, the receiving can be performed by one or more of the components 198, the transceiver 1322, and / or the antennas 1380 of FIG. 13. FIG. 5 shows an example in which a UE 502 receives a switch command 510 for L1 / L2 mobility from a serving cell (e.g., base station 504).

[0085]

[0101] The switch command 510 may indicate a switch (e.g., handoff or transfer) associated with L1 / L2 mobility of the UE 502 from a serving cell (e.g., base station 504) to a candidate cell (e.g., base station 505) among a set of candidate cells available for L1 / L2 mobility of the UE 502. In an aspect, the switch command 510 may be associated with a TCI for the beam(s) and / or at least one RACH parameter for BWP of the set of candidate cells (e.g., including the base station 505). In some aspects, the switch command 510 may dynamically include the TCI for the beam(s) in addition to or instead of the TCI for the beam(s) of the parameter(s) 508 being provided via RRC / MAC-CE / DCI. In such an aspect, the switching command 510 may further include a MAC-CE that activates a TCI for the beam(s) for the base station 505 and / or a DCI that indicates the TCI for the beam(s).

[0086]

[0102] At 904, the UE communicates with the candidate cell based on at least one of the TCI for the beam or the at least one RACH parameter for the BWP. As an example, the communication can be performed by one or more of the components 198, the transceiver 1322, and / or the antennas 1380 of FIG. 13. FIG. 5 shows an example in which the UE 502 communicates with a target cell (e.g., base station 505) based on the preconfigured TCI for the beam and / or the RACH parameter(s) for the BWP of the target cell after a switch command 510 for L1 / L2 mobility from a serving cell (e.g., base station 504) initiates and completes a handoff / transfer therefrom.

[0087]

[0103] In other words, after receiving the switch command 510, the UE 502 can be configured to receive and / or transmit communication 512 with the target candidate cell (e.g., the base station 505 acting as the new serving cell) based on at least one RACH parameter(s) for the TCI and / or BWP for the beam(s). In an aspect, because the UE is pre-configured with the RACH parameter(s) for the TCI for the beam(s) and / or BWP of the base station 505, the UE 502 can be configured to immediately receive and / or transmit communication 512 with the base station 505 after completion of the handoff initiated by the switch command 510. That is, after the handoff to the base station 505, the UE can skip performing configuration for the TCI / RACH because of the pre-configuration(s) for the TCI / RACH, and thus, reduced mobility latency can be achieved.

[0088]

[0104] FIG. 10 is a flowchart 1000 of a method of wireless communication, according to various aspects. The method may be performed by a UE (e.g., UE 104 / 402 / 502 / 602 / 702 / 802, device 1304). In some aspects, the method may include aspects described in connection with the communication flow of FIG. 5 and / or aspects described in FIGS. 6, 7, and 8. The method provides improved UE mobility, enabling the UE to utilize L1 / L2 mobility through pre-configuration of TCI for beams and pre-configuration of RACH for BWP of candidate cells, as well as dynamic pre-configuration via mobility commands that improve mobility latency.

[0089]

[0105] At 1002, before receiving the switching command, the UE receives at least one of a TCI configuration for a candidate cell or a RACH configuration for the candidate cell, where the TCI for the beam is based on the TCI configuration and the at least one RACH parameter is based on the RACH configuration. As an example, the receiving can be performed by one or more of component 198, transceiver 1322, and / or antenna 1380. FIG. 5 shows an example in which a UE 502 receives configuration(s) 506 from a serving cell (e.g., base station 505), where the configuration 506 can include a TCI configuration and / or a RACH configuration for a candidate cell (e.g., base station 504).

[0090]

[0106] The configuration(s) 506 may include a TCI configuration for a candidate cell (e.g., base station 505) and / or a RACH configuration for the candidate cell (e.g., base station 505), where the TCI for the beam as described herein can be based on the TCI configuration, and the at least one RACH parameter as described herein can be based on the RACH configuration. In an aspect, the configuration(s) 506 may include a single signaling or multiple signaling, and the configuration(s) 506 may be provided by the base station 504 via RRC signaling. As described in further detail below, the configuration(s) 506 may be based on previous L1 measurements of a set of candidate cells (e.g., including the base station 505) performed by the UE 502.

[0091]

[0107] At 1004, the UE receives at least one RACH parameter for BWP of a set of candidate cells from a serving cell via RRC signaling, the at least one RACH parameter including at least one of (1) a PRACH parameter or (2) at least one BFR parameter. As an example, the receiving can be performed by one or more of component 198, transceiver 1322, and / or antenna 1380. FIG. 5 shows an example in which a base station 504 provides parameter(s) 508 to be received by a UE 502.

[0092]

[0108] The base station 504 can be configured to provide the parameter(s) 508, and the UE 502 can be configured to receive the parameter(s) 508. The parameter(s) 508 can include RACH parameter(s) for BWP of a candidate cell (e.g., a set of candidate cells that includes the base station 505). In an aspect, the RACH parameter(s) in the parameter(s) 508 can be provided via RRC signaling (e.g., 806 in FIG. 8). Further details regarding the parameter(s) 508 are described with respect to FIG. 8.

[0093]

[0109] At 1006, it is determined whether TCI is received by the UE via RRC (e.g., followed by MAC-CE and DCI). As an example, this determination may be performed by component 198. If TCI is received by the UE via RRC, flowchart 1000 proceeds to 1008. Otherwise, flowchart 1000 proceeds to 1010, where TCI may be dynamically included in the mobility command.

[0094]

[0110] At 1008, the UE receives (1) the TCI for the beam (e.g., legacy and / or integrated) from the serving cell via RRC signaling, (2) the activation of the TCI via MAC-CE, and (3) a DCI indicating the TCI state(s) prior to the switch command. As an example, the reception can be performed by one or more of the component 198, the transceiver 1322, and / or the antenna 1380. FIG. 5 illustrates an example in which a base station 504 provides parameter(s) 508 to be received by the UE 502.

[0095]

[0111] The base station 504 can be configured to provide, and the UE 502 can be configured to receive, parameter(s) 508. The parameter(s) 508 can include TCI for beam(s) of a candidate cell (e.g., a set of candidate cells including the base station 505). In an aspect, the TCI for the beam(s) can include legacy and / or combined (e.g., joint) TCI status and related information of the candidate cell(s). In an aspect, the parameter(s) 508 can be received by the UE 502 in one or more signalings and can be provided via RRC signaling (e.g., 706 in FIG. 7), MAC-CE signaling (e.g., 708 in FIG. 7), and / or DCI (e.g., 710 in FIG. 7). Further details regarding the parameter(s) 508 are described with respect to FIG. 7.

[0096]

[0112] From 1008, the flowchart 1000 can proceed to 1012.

[0097]

[0113] At 1010, the UE receives, from a serving cell, a switch command indicating a switch associated with the UE's L1 / L2 mobility from the serving cell to a candidate cell among a set of candidate cells associated with the UE's L1 / L2 mobility, the switch command being associated with at least one of (1) a TCI for the beam or (2) at least one RACH parameter for BWP of the set of candidate cells, the switch command including (1) a TCI (e.g., legacy and / or unified) for the beam from the serving cell via RRC signaling, (2) activation of the TCI via MAC-CE, and (3) a DCI indicating the TCI state(s). As an example, the receiving can be performed by one or more of the component 198, the transceiver 1322, and / or the antenna 1380. FIG. 5 illustrates an example in which a UE 502 receives a switch command 510 for L1 / L2 mobility from a serving cell (e.g., base station 504).

[0098]

[0114] The switch command 510 may indicate a switch (e.g., handoff or transfer) associated with L1 / L2 mobility of the UE 502 from a serving cell (e.g., base station 504) to a candidate cell (e.g., base station 505) of a set of candidate cells available for L1 / L2 mobility of the UE 502. In an aspect, the switch command 510 may be associated with a TCI for the beam(s) and / or at least one RACH parameter for BWP of the set of candidate cells (e.g., including the base station 505). In some aspects, the switch command 510 may dynamically include the TCI for the beam(s) in addition to or instead of the TCI for the beam(s) of the parameter(s) 508 being provided via RRC / MAC-CE / DCI (e.g., as described with respect to 1008 above). In such an aspect, the switching command 510 may further include a MAC-CE that activates a TCI for the beam(s) for the base station 505 and / or a DCI that indicates the TCI for the beam(s).

[0099]

[0115] From 1010, the flowchart 1000 can proceed to 1014.

[0100]

[0116] At 1012, the UE receives a switch command from the serving cell indicating a switch associated with L1 / L2 mobility of the UE from the serving cell to a candidate cell among a set of candidate cells associated with L1 / L2 mobility of the UE, the switch command being associated with at least one of (1) a TCI for the beam or (2) at least one RACH parameter for BWP of the set of candidate cells. As an example, the receiving can be performed by one or more of component 198, transceiver 1322, and / or antenna 1380. FIG. 5 shows an example in which a UE 502 receives a switch command 510 for L1 / L2 mobility from a serving cell (e.g., base station 504).

[0101]

[0117] The switch command 510 may indicate a switch (e.g., handoff or transfer) associated with L1 / L2 mobility of the UE 502 from a serving cell (e.g., base station 504) to a candidate cell (e.g., base station 505) among a set of candidate cells available for L1 / L2 mobility of the UE 502. In an aspect, the switch command 510 may be associated with at least one RACH parameter for a TCI for a beam(s) and / or a BWP of the set of candidate cells (e.g., including base station 505).

[0102]

[0118] At 1014, the UE communicates with the candidate cell based on at least one of the TCI for the beam or the at least one RACH parameter for the BWP. By way of example, the communication can be performed by one or more of the component 198, the transceiver 1322, and / or the antenna 1380. Figure 5 shows an example in which the UE 502 communicates with the target cell (e.g., base station 505) based on the preconfigured TCI for the beam and / or the RACH parameter(s) for the BWP of the target cell after a switch command 510 for L1 / L2 mobility from a serving cell (e.g., base station 504) initiates and completes a handoff / transfer therefrom.

[0103]

[0119] In other words, after receiving the switch command 510, the UE 502 can be configured to receive and / or transmit communication 512 with the target candidate cell (e.g., the base station 505 acting as the new serving cell) based on at least one RACH parameter(s) for the TCI and / or BWP for the beam(s). In an aspect, because the UE is pre-configured with the RACH parameter(s) for the TCI for the beam(s) and / or BWP of the base station 505, the UE 502 can be configured to immediately receive and / or transmit communication 512 with the base station 505 after completion of the handoff initiated by the switch command 510. That is, after the handoff to the base station 505, the UE can skip performing configuration for the TCI / RACH because of the pre-configuration(s) for the TCI / RACH, and thus, reduced mobility latency can be achieved.

[0104]

[0120] FIG. 11 is a flowchart 1100 of a method of wireless communication, according to various aspects. The method may be performed by a base station and / or a serving cell (e.g., a base station 102, 504, 704, 804, an SpCell 404, 604, a network entity 1302, 1402, 1560). In some aspects, the method may include aspects described in connection with the communication flow of FIG. 5 and / or aspects described in FIGS. 6, 7, and 8. The method provides improved UE mobility by enabling a UE to utilize L1 / L2 mobility through pre-configuration of TCI for beams and pre-configuration of RACH for BWP of candidate cells, as well as dynamic pre-configuration via mobility commands that improve mobility latency.

[0105]

[0121] At 1102, the base station configures a switch command indicating a switch associated with the UE's L1 / L2 mobility to a candidate cell among a set of candidate cells associated with the UE's L1 / L2 mobility, the switch command being associated with at least one of (1) a TCI for the beam or (2) at least one RACH parameter for the BWP of the set of candidate cells. As an example, providing the configuration can be performed by, for example, component 199, transceiver 1446, and / or antenna 1480 of Figure 14, or network interface 1580 of Figure 15. Figure 5 shows an example of base station 504 configuring (at 509) switch command 510.

[0106]

[0122] The switch command 510 can be configured by the base station 504 for L1 / L2 mobility (e.g., handoff or transfer) of the UE 502 from a serving cell (e.g., base station 504) to a candidate cell (e.g., base station 505) among a set of candidate cells available for the UE 502's L1 / L2 mobility. In an aspect, the switch command 510 can be configured to be associated with the TCI for the beam(s) and / or at least one RACH parameter for the BWP of the set of candidate cells (e.g., including the base station 505). In some aspects, in addition to or instead of the TCI for the beam(s) of the parameter(s) 508 being provided via RRC / MAC-CE / DCI, the switch command 510 can be configured to include the TCI for the beam(s) for the UE 502's dynamic mobility. In such an aspect, the switching command 510 can be configured to further include a MAC-CE that activates the TCI for the beam(s) for the base station 505 and / or a DCI that indicates the TCI for the beam(s).

[0107]

[0123] At 1104, the base station transmits a switch command to the candidate cell for the UE indicating a switch associated with the UE's L1 / L2 mobility. As an example, providing the configuration can be performed by, for example, component 199, transceiver 1446, and / or antenna 1480 of Figure 14, or network interface 1580 of Figure 15. Figure 5 illustrates an example in which a base station 504 provides a switch command 510 to a UE 502.

[0108]

[0124] The switch command 510 may be provided from the base station 504 and received by the UE 502 and may indicate a switch (e.g., handoff or transfer) associated with the L1 / L2 mobility of the UE 502 from a serving cell (e.g., the base station 504) to a candidate cell (e.g., the base station 505) among a set of candidate cells available for the UE 502's L1 / L2 mobility.

[0109]

[0125] FIG. 12 is a flowchart 1200 of a method of wireless communication, according to various aspects. The method may be performed by a base station and / or a serving cell (e.g., a base station 102, 504, 704, 804, an SpCell 404, 604, a network entity 1302, 1402, 1560). In some aspects, the method may include aspects described in connection with the communication flow of FIG. 5 and / or aspects described in FIGS. 6, 7, and 8. The method provides improved UE mobility by enabling a UE to utilize L1 / L2 mobility through pre-configuration of TCI for beams and pre-configuration of RACH for BWP of candidate cells, as well as dynamic pre-configuration via mobility commands that improve mobility latency.

[0110]

[0126] In 1202, the base station transmits, for the UE, before the switching command, at least one of a TCI configuration for the candidate cell or a RACH configuration for the candidate cell, where the TCI for the beam is based on the TCI configuration and the at least one RACH parameter is based on the RACH configuration. As an example, transmitting or providing the configuration(s) can be performed by, for example, component 199, transceiver 1446, and / or antenna 1480 of Figure 14, or any of network interface 1580 of Figure 15. Figure 5 shows an example in which a base station 504 provides configuration(s) 506 to a UE 502.

[0111]

[0127] The configuration(s) 506 may include a TCI configuration for a candidate cell (e.g., base station 505) and / or a RACH configuration for the candidate cell (e.g., base station 505), where the TCI for the beam as described herein can be based on the TCI configuration, and the at least one RACH parameter as described herein can be based on the RACH configuration. In an aspect, the configuration(s) 506 may include a single signaling or multiple signaling, and the configuration(s) 506 may be provided by the base station 504 via RRC signaling. As described in further detail below, the configuration(s) 506 may be based on previous L1 measurements of a set of candidate cells (e.g., including the base station 505) performed by the UE 502.

[0112]

[0128] At 1204, the base station transmits at least one RACH parameter for BWP of the set of candidate cells to the UE via RRC signaling, where the at least one RACH parameter includes at least one of (1) a PRACH parameter or (2) at least one BFR parameter. By way of example, the transmitting or providing may be performed by, for example, component 199, transceiver 1446, and / or antenna 1480 of FIG. 14, or network interface 1580 of FIG. 15. FIG. 5 illustrates an example in which a base station 504 provides parameter(s) 508 to a UE 502.

[0113]

[0129] The base station 504 can be configured to provide, and the UE 502 can be configured to receive, the parameter(s) 508. The parameter(s) 508 can include RACH parameter(s) for BWP of a candidate cell (e.g., a set of candidate cells that includes the base station 505). In an aspect, the RACH parameter(s) of the parameter(s) 508 can be provided via RRC signaling (e.g., 806 in FIG. 8). Further details regarding the parameter(s) 508 are described with respect to FIG. 8.

[0114]

[0130] At 1206, it is determined whether the TCI is provided to the UE by the serving cell via RRC (e.g., followed by MAC-CE and DCI). As an example, the determination may be performed by one or more of components 199. If the TCI is provided by the serving cell and received by the UE via RRC, flowchart 1200 proceeds to 1208. Otherwise, flowchart 1200 proceeds to 1210, where the TCI may be dynamically included in the mobility command.

[0115]

[0131] At 1208, the base station transmits, prior to the switch command, (1) the TCI for the beam (e.g., legacy and / or unified) from the serving cell via RRC signaling, (2) the activation of the TCI via MAC-CE, and (3) a DCI indicating the TCI state(s). As an example, the transmitting or providing can be performed by, for example, any of the components 199, transceiver 1446, and / or antenna 1480 of FIG. 14, the network interface 1580 of FIG. 15. FIG. 5 illustrates an example in which a base station 504 provides parameter(s) 508 to be received by a UE 502.

[0116]

[0132] The base station 504 can be configured to provide, and the UE 502 can be configured to receive, parameter(s) 508. The parameter(s) 508 can include TCI for beam(s) of a candidate cell (e.g., a set of candidate cells including the base station 505). In an aspect, the TCI for the beam(s) can include legacy and / or combined (e.g., joint) TCI status and related information of the candidate cell(s). In an aspect, the parameter(s) 508 can be received by the UE 502 in one or more signalings and can be provided via RRC signaling (e.g., 706 in FIG. 7), MAC-CE signaling (e.g., 708 in FIG. 7), and / or DCI (e.g., 710 in FIG. 7). Further details regarding the parameter(s) 508 are described with respect to FIG. 7.

[0117]

[0133] From 1208, the flowchart 1000 can proceed to 1212.

[0118]

[0134] At 1210, the base station configures a switch command indicating a switch associated with the UE's L1 / L2 mobility to a candidate cell among a set of candidate cells associated with the UE's L1 / L2 mobility, the switch command being associated with at least one of (1) a TCI for the beam or (2) at least one RACH parameter for BWP of the set of candidate cells, the switch command including (1) a TCI (e.g., legacy and / or unified) for the beam from the serving cell via RRC signaling, (2) activation of the TCI via MAC-CE, and (3) a DCI indicating the TCI state(s). As an example, the transmitting or providing can be performed by, for example, any of the component 199, transceiver 1446, and / or antenna 1480 of FIG. 14, or the network interface 1580 of FIG. 15. FIG. 5 illustrates an example in which a UE 502 receives a switch command 510 for L1 / L2 mobility from a serving cell (e.g., base station 504).

[0119]

[0135] The switch command 510 may indicate a switch (e.g., handoff or transfer) associated with L1 / L2 mobility of the UE 502 from a serving cell (e.g., base station 504) to a candidate cell (e.g., base station 505) of a set of candidate cells available for L1 / L2 mobility of the UE 502. In an aspect, the switch command 510 may be associated with a TCI for the beam(s) and / or at least one RACH parameter for BWP of the set of candidate cells (e.g., including the base station 505). In some aspects, the switch command 510 may dynamically include the TCI for the beam(s) in addition to or instead of the TCI for the beam(s) of the parameter(s) 508 being provided via RRC / MAC-CE / DCI (e.g., as described with respect to 1008 above). In such an aspect, the switching command 510 may further include a MAC-CE that activates a TCI for the beam(s) for the base station 505 and / or a DCI that indicates the TCI for the beam(s).

[0120]

[0136] From 1210, the flowchart 1200 can proceed to 1214.

[0121]

[0137] At 1212, the base station configures a switch command indicating a switch associated with the UE's L1 / L2 mobility to a candidate cell among a set of candidate cells associated with the UE's L1 / L2 mobility, the switch command being associated with at least one of (1) a TCI for the beam or (2) at least one RACH parameter for the BWP of the set of candidate cells. As an example, providing the configuration can be performed by, for example, component 199, transceiver 1446, and / or antenna 1480 of Figure 14, or network interface 1580 of Figure 15. Figure 5 shows an example of base station 504 configuring (at 509) switch command 510.

[0122]

[0138] The switch command 510 can be configured by the base station 504 for L1 / L2 mobility (e.g., handoff or transfer) of the UE 502 from a serving cell (e.g., base station 504) to a candidate cell (e.g., base station 505) among a set of candidate cells available for L1 / L2 mobility of the UE 502. In an aspect, the switch command 510 can be configured to be associated with at least one RACH parameter for a TCI for a beam(s) and / or a BWP of the set of candidate cells (e.g., including the base station 505).

[0123]

[0139] At 1214, the base station transmits a switch command to the candidate cell for the UE indicating a switch associated with the UE's L1 / L2 mobility. As an example, providing the configuration can be performed by, for example, component 199, transceiver 1446, and / or antenna 1480 of Figure 14, or network interface 1580 of Figure 15. Figure 5 illustrates an example in which a base station 504 provides a switch command 510 to a UE 502.

[0124]

[0140] The switch command 510 may be provided from the base station 504 and received by the UE 502 and may indicate a switch (e.g., handoff or transfer) associated with the L1 / L2 mobility of the UE 502 from a serving cell (e.g., the base station 504) to a candidate cell (e.g., the base station 505) among a set of candidate cells available for the UE 502's L1 / L2 mobility.

[0125]

[0141] 13 is a diagram 1300 illustrating an example of a hardware implementation for an apparatus 1304. The apparatus 1304 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus 1304 may include a cellular baseband processor 1324 (also referred to as a modem) coupled to one or more transceivers 1322 (e.g., cellular RF transceivers). The cellular baseband processor 1324 may include on-chip memory 1324′. In some aspects, the apparatus 1304 may further include one or more subscriber identity modules (SIM) cards 1320 and an application processor 1306 coupled to a secure digital (SD) card 1308 and a screen 1310. The application processor 1306 may include on-chip memory 1306′. In some aspects, the device 1304 may further include a Bluetooth module 1312, a WLAN module 1314, an SPS module 1316 (e.g., a GNSS module), one or more sensor modules 1318 (e.g., a barometric pressure sensor / altimeter, an inertial measurement unit (IMU), a motion sensor such as a gyroscope and / or accelerometer(s), light detection and ranging (LIDAR), radio assisted detection and ranging (RADAR), sound navigation and ranging (SONAR), a magnetometer, audio, and / or other technologies used for positioning), an additional memory module 1326, a power source 1330, and / or a camera 1332. The Bluetooth module 1312, the WLAN module 1314, and the SPS module 1316 may include an on-chip transceiver (TRX) (or in some cases, simply a receiver (RX)).The Bluetooth module 1312, the WLAN module 1314, and the SPS module 1316 may include their own dedicated antennas and / or utilize an antenna 1380 for communications. The cellular baseband processor 1324 communicates with the UE 104 and / or RUs associated with the network entity 1302 via transceiver(s) 1322 via one or more antennas 1380. The cellular baseband processor 1324 and the application processor 1306 may each include computer-readable media / memory 1324′, 1306′, respectively. The additional memory module 1326 may also be considered a computer-readable medium / memory. Each computer-readable medium / memory 1324′, 1306′, 1326 may be non-transitory. The cellular baseband processor 1324 and the application processor 1306 are each responsible for general processing, including executing software stored in the computer-readable medium / memory. The software, when executed by the cellular baseband processor 1324 / application processor 1306, causes the cellular baseband processor 1324 / application processor 1306 to perform the various functions described above. The computer-readable medium / memory may also be used to store data manipulated by the cellular baseband processor 1324 / application processor 1306 when executing the software. The cellular baseband processor 1324 / application processor 1306 may be a component of the UE 350 and may include the 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 device 1304 may be a processor chip (modem and / or application) and may include only the cellular baseband processor 1324 and / or the application processor 1306; in another configuration, the device 1304 may be an entire UE (e.g., see UE 350 in FIG. 3) and may include additional modules of the device 1304.

[0126]

[0142] As described above, component 198 can be configured to receive a switch command from a serving cell indicating a switch associated with the UE's L1 / L2 mobility from the serving cell to a candidate cell among a set of candidate cells associated with the UE's L1 / L2 mobility, the switch command being associated with at least one of (1) a TCI for the beam or (2) at least one RACH parameter for a BWP of the set of candidate cells. Component 198 is also configured to communicate with the candidate cell based on at least one of the TCI for the beam or the at least one RACH parameter for the BWP. In an aspect, component 198 can be configured to receive at least one of a TCI configuration for the candidate cell or a RACH configuration for the candidate cell prior to receiving the switch command, where the TCI for the beam is based on the TCI configuration and the at least one RACH parameter is based on the RACH configuration. In an aspect, component 198 can be configured to receive a TCI for the beam from the serving cell via RRC signaling and prior to receiving the switch command, the TCI for the beam including at least one of a first legacy TCI state for periodic CSI-RS, first legacy spatial relationship information for periodic SRS or PUCCH, or a list of legacy TCI states for PDSCH. In an aspect, component 198 can be configured to receive activation of the TCI for the beam via MAC-CE including at least one of a second legacy TCI state for CORESET or semi-persistent CSI-RS, second legacy spatial relationship information for at least one of semi-persistent SRS, aperiodic SRS, or PUCCH, a subset of legacy TCI states for PDSCH, or at least one SRS or path loss RS for at least one physical uplink shared channel (PUSCH). In an aspect, component 198 can be configured to receive DCI indicating a third legacy TCI state of the subset of legacy TCI states for the PDSCH.In an aspect, component 198 can be configured to receive a TCI for the beam from the serving cell via RRC signaling and prior to receiving the switching command, the TCI for the beam including a first aggregated TCI state for periodic CSI-RS or periodic SRS configured to not follow the aggregated TCI indication, or at least one of a list of downlink TCI states, a list of joint TCI states, or a list of uplink TCI states. In an aspect, component 198 can be configured to receive an activation of the TCI for the beam via MAC-CE including a second aggregated TCI state for at least one of CORESET, semi-persistent CSI-RS, semi-persistent SRS, or aperiodic SRS configured to not follow the aggregated TCI indication. In an aspect, component 198 can be configured to receive DCI indicating at least one of a joint TCI state for at least one of a PDSCH, a PDCCH, a PUSCH, a PUCCH, a CSI-RS, or an SRS configured to follow the joint TCI indication, a downlink TCI state for at least one of a PDSCH, a PDCCH, or a CSI-RS configured to follow the joint TCI indication, or an uplink TCI state for a PUSCH, a PUCCH, or an SRS configured to follow the joint TCI indication. In an aspect, component 198 can be configured to receive at least one RACH parameter for BWP of the set of candidate cells from the serving cell via the at least one transceiver and RRC signaling, the at least one RACH parameter including at least one of (1) a PRACH parameter or (2) at least one BFR parameter. Component 198 may be further configured to perform any of the aspects described in connection with the flowcharts in any of Figures 9 to 12 and / or any of the aspects performed by the UE in any of Figures 4, 5, 6, 7, and 8.Component 198 may be located within cellular baseband processor 1324, application processor 1306, or both cellular baseband processor 1324 and application processor 1306. Component 198 may be one or more hardware components specifically configured to perform the described processes / algorithms, may be implemented by one or more processors configured to perform the described processes / algorithms, may be stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. As shown, device 1304 may include various components configured for various functions. In one configuration, the apparatus 1304, particularly the cellular baseband processor 1324 and / or the application processor 1306, may include means for receiving, from a serving cell, a switch command indicating a switch associated with the UE's L1 / L2 mobility from the serving cell to a candidate cell among a set of candidate cells associated with the UE's L1 / L2 mobility, the switch command being associated with at least one of (1) a TCI for the beam or (2) at least one RACH parameter for a BWP of the set of candidate cells. In this configuration, the apparatus 1304, particularly the cellular baseband processor 1324 and / or the application processor 1306, may include means for communicating with the candidate cell based on at least one of the TCI for the beam or the at least one RACH parameter for the BWP. In one configuration, the device 1304, particularly the cellular baseband processor 1324 and / or the application processor 1306, may include means for receiving at least one of a TCI configuration for a candidate cell or a RACH configuration for a candidate cell before receiving a switch command, wherein the TCI for the beam is based on the TCI configuration and the at least one RACH parameter is based on the RACH configuration.In one configuration, the apparatus 1304, particularly the cellular baseband processor 1324 and / or the application processor 1306, may include means for receiving a TCI for the beam from the serving cell via RRC signaling and before receiving the switching command, the TCI for the beam including at least one of a first legacy TCI state for periodic CSI-RS, first legacy spatial relationship information for periodic SRS or PUCCH, or a list of legacy TCI states for PDSCH. In one configuration, the apparatus 1304, particularly the cellular baseband processor 1324 and / or the application processor 1306, may include means for receiving activation of a TCI for a beam via a MAC-CE including at least one of a second legacy TCI state for a CORESET or semi-persistent CSI-RS, second legacy spatial relationship information for at least one of a semi-persistent SRS, an aperiodic SRS, or a PUCCH, a subset of legacy TCI states for a PDSCH, or at least one path loss RS for at least one SRS or at least one physical uplink shared channel (PUSCH). In one configuration, the apparatus 1304, particularly the cellular baseband processor 1324 and / or the application processor 1306, may include means for receiving a DCI indicating a third legacy TCI state of the subset of legacy TCI states for a PDSCH. In one configuration, the device 1304, particularly the cellular baseband processor 1324 and / or the application processor 1306, may include means for receiving a TCI for the beam from the serving cell via RRC signaling and before receiving the switching command, wherein the TCI for the beam includes at least one of a first integrated TCI state for the periodic CSI-RS or periodic SRS configured to not follow the integrated TCI instruction, or at least one of a list of downlink TCI states, a list of joint TCI states, or a list of uplink TCI states.In one configuration, the apparatus 1304, particularly the cellular baseband processor 1324 and / or the application processor 1306, may include means for receiving activation of the TCI for the beam via the MAC-CE including a second joint TCI state for at least one of CORESET, semi-persistent CSI-RS, semi-persistent SRS, or aperiodic SRS configured to not follow the joint TCI indication. In an aspect, the component 198 may be configured to receive a DCI indicating at least one of a joint TCI state for at least one of the PDSCH, PDCCH, PUSCH, PUCCH, CSI-RS, or SRS configured to follow the joint TCI indication, a downlink TCI state for at least one of the PDSCH, PDCCH, or CSI-RS configured to follow the joint TCI indication, or an uplink TCI state for the PUSCH, PUCCH, or SRS configured to follow the joint TCI indication. In one configuration, the apparatus 1304, particularly the cellular baseband processor 1324 and / or the application processor 1306, may include means for receiving at least one RACH parameter for a BWP of a set of candidate cells from a serving cell via at least one transceiver and RRC signaling, where the at least one RACH parameter includes at least one of (1) a PRACH parameter or (2) at least one BFR parameter. The means may be a component 198 of the apparatus 1304 configured to perform the recited functions. As described above, the apparatus 1304 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Thus, 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 recited functions.

[0127]

[0143] FIG. 14 is a diagram 1400 illustrating an example of a hardware implementation for a network entity 1402. The network entity 1402 may be a BS, a component of a BS, or may implement BS functionality. The network entity 1402 may include at least one of a CU 1410, a DU 1430, or an RU 1440. For example, depending on the layer functions processed by the component 199, the network entity 1402 may include a CU 1410, both the CU 1410 and the DU 1430, each of the CU 1410, the DU 1430, and the RU 1440, both the DU 1430, the DU 1430, and the RU 1440, or an RU 1440. The CU 1410 may include a CU processor 1412. The CU processor 1412 may include an on-chip memory 1412′. In some aspects, the CU 1410 may further include an additional memory module 1414 and a communication interface 1418. The CU 1410 communicates with the DU 1430 through a midhaul link, such as an F1 interface. The DU 1430 may include a DU processor 1432. The DU processor 1432 may include an on-chip memory 1432′. In some aspects, the DU 1430 may further include an additional memory module 1434 and a communication interface 1438. The DU 1430 communicates with the RU 1440 through a fronthaul link. The RU 1440 may include an RU processor 1442. The RU processor 1442 may include an on-chip memory 1442′. In some aspects, the RU 1440 may further include an additional memory module 1444, one or more transceivers 1446, an antenna 1480, and a communication interface 1448. The RU 1440 communicates with the UE 104. The on-chip memories 1412', 1432', 1442' and the additional memory modules 1414, 1434, 1444 can each be considered a computer-readable medium / memory. Each computer-readable medium / memory can be non-transitory. Each of the processors 1412, 1432, 1442 is responsible for general processing, including executing software stored on the computer-readable medium / memory.The software, when executed by a corresponding processor(s), causes the processor(s) to perform the various functions described above. The computer-readable medium / memory may also be used to store data that is manipulated by the processor(s) when executing the software.

[0128]

[0144] As described above, component 199 can be configured to configure a switch command indicating a switch associated with L1 / L2 mobility of the UE to a candidate cell among a set of candidate cells associated with the UE's L1 / L2 mobility, the switch command being associated with at least one of (1) a TCI for the beam or (2) at least one RACH parameter for a BWP of the set of candidate cells. Component 199 is also configured to transmit, for the UE, the switch command indicating a switch associated with L1 / L2 mobility of the UE to the candidate cell. In an aspect, component 199 can be configured to transmit, for the UE, at least one of a TCI configuration for the candidate cell or a RACH configuration for the candidate cell before transmitting the switch command, the TCI for the beam being based on the TCI configuration and the at least one RACH parameter being based on the RACH configuration. In an aspect, component 199 can be configured to transmit, for the UE via RRC signaling and before transmitting the switching command, a TCI for the beam, where the TCI for the beam includes at least one of a first legacy TCI state for periodic CSI-RS, first legacy spatial relationship information for periodic SRS or PUCCH, or a list of legacy TCI states for PDSCH. In an aspect, component 199 can be configured to transmit, for the UE, an activation of the TCI for the beam via MAC-CE including at least one of a second legacy TCI state for CORESET or semi-persistent CSI-RS, second legacy spatial relationship information for at least one of semi-persistent SRS, aperiodic SRS, or PUCCH, a subset of legacy TCI states for PDSCH, or path loss RS for at least one SRS or at least one PUSCH. In an aspect, component 199 can be configured to transmit, for the UE, a DCI indicating a third legacy TCI state of the subset of legacy TCI states for the PDSCH.In an aspect, component 199 can be configured to transmit, for the UE via RRC signaling and before receiving the switching command, a TCI for the beam, where the TCI for the beam includes a first consolidated TCI state for periodic CSI-RS or periodic SRS configured to not follow the consolidated TCI indication, or at least one of a list of downlink TCI states, a list of joint TCI states, or a list of uplink TCI states. In an aspect, component 199 can be configured to transmit, for the UE via MAC-CE, an activation of the TCI for the beam including a second consolidated TCI state for at least one of CORESET, semi-persistent CSI-RS, semi-persistent SRS, or aperiodic SRS configured to not follow the consolidated TCI indication. In an aspect, component 199 can be configured to transmit, for the UE, a DCI indicating at least one of a joint TCI state for at least one of the PDSCH, PDCCH, PUSCH, PUCCH, CSI-RS, or SRS configured to follow the joint TCI indication, a downlink TCI state for at least one of the PDSCH, PDCCH, or CSI-RS configured to follow the joint TCI indication, or an uplink TCI state for the PUSCH, PUCCH, or SRS configured to follow the joint TCI indication. In an aspect, component 199 can be configured to transmit, for the UE via the at least one transceiver and RRC signaling, at least one RACH parameter for BWP of the set of candidate cells, the at least one RACH parameter including at least one of (1) a PRACH parameter or (2) at least one BFR parameter. Component 199 may be further configured to perform any of the aspects described in connection with the flowcharts in any of Figures 9-12 and / or any of the aspects performed by the serving cell in any of Figures 4, 5, 6, 7, and 8. Component 199 may reside in one or more processors of one or more of CU 1410, DU 1430, and RU 1440.The component 199 may be one or more hardware components specifically configured to perform the described processes / algorithms, may be implemented by one or more processors configured to perform the described processes / algorithms, may be stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. The network entity 1402 may include various components configured for various functions. In one configuration, the network entity 1402 may include means for configuring a switch command indicating a switch associated with the UE's L1 / L2 mobility to a candidate cell among a set of candidate cells associated with the UE's L1 / L2 mobility, the switch command being associated with at least one of (1) a TCI for the beam or (2) at least one RACH parameter for the BWP of the set of candidate cells. In this configuration, the network entity 1402 may include means for transmitting, for the UE, a switch command to the candidate cell indicating a switch associated with the UE's L1 / L2 mobility. In one configuration, the network entity 1402 may include means for transmitting, for the UE, at least one of a TCI configuration for the candidate cell or a RACH configuration for the candidate cell before transmitting the switch command, where the TCI for the beam is based on the TCI configuration and the at least one RACH parameter is based on the RACH configuration. In this configuration, the network entity 1402 may include means for transmitting, for the UE via RRC signaling and before transmitting the switch command, a TCI for the beam including at least one of a first legacy TCI state for periodic CSI-RS, first legacy spatial relationship information for periodic SRS or PUCCH, or a list of legacy TCI states for PDSCH.In this configuration, the network entity 1402 may include means for transmitting, for the UE, a DCI indicating a third legacy TCI state of the subset of legacy TCI states for the PDSCH. In this configuration, the network entity 1402 may include means for transmitting, for the UE via RRC signaling and before receiving the switching command, a TCI for the beam, where the TCI for the beam includes a first aggregated TCI state for the periodic CSI-RS or the periodic SRS configured to not follow the aggregated TCI indication, or at least one of a list of downlink TCI states, a list of joint TCI states, or a list of uplink TCI states. In this configuration, the network entity 1402 may include means for transmitting, for the UE, an activation of the TCI for the beam via the MAC-CE including a second aggregated TCI state for at least one of CORESET, semi-persistent CSI-RS, semi-persistent SRS, or aperiodic SRS configured to not follow the aggregated TCI indication.In this configuration, the network entity 1402 may include means for transmitting, for the UE, DCI indicating at least one of a joint TCI state for at least one of the PDSCH, PDCCH, PUSCH, PUCCH, CSI-RS, or SRS configured to follow the joint TCI indication, a downlink TCI state for at least one of the PDSCH, PDCCH, or CSI-RS configured to follow the joint TCI indication, or an uplink TCI state for the PUSCH, PUCCH, or SRS configured to follow the joint TCI indication. In this configuration, the network entity 1402 may include means for transmitting, for the UE via the at least one transceiver and RRC signaling, at least one RACH parameter for BWP of the set of candidate cells, the at least one RACH parameter including at least one of (1) a PRACH parameter or (2) at least one BFR parameter. The means may be component 199 of the network entity 1402 configured to perform the enumerated functions by the means. As described above, the network entity 1402 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Thus, 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 recited functions by that means.

[0129]

[0145] FIG. 15 is a diagram 1500 illustrating an example of a hardware implementation for a network entity 1560. In one embodiment, the network entity 1560 may reside within the core network 120. The network entity 1560 may include a network processor 1512. The network processor 1512 may include an on-chip memory 1512′. In some aspects, the network entity 1560 may further include an additional memory module 1514. The network entity 1560 communicates with the CU 1502 via a network interface 1580, either directly (e.g., via a backhaul link) or indirectly (e.g., through a RIC). The on-chip memory 1512′ and the additional memory module 1514 may each be considered a computer-readable medium / memory. Each computer-readable medium / memory may be non-transitory. The processor 1512 is responsible for general processing, including the execution of software stored on the computer-readable medium / memory. The software, when executed by a corresponding processor(s), causes the processor(s) to perform various functions described above. The computer-readable medium / memory may also be used for storing data that is manipulated by the processor(s) when executing software.

[0130]

[0146] As described above, component 199 can be configured to configure a switch command indicating a switch associated with L1 / L2 mobility of the UE to a candidate cell among a set of candidate cells associated with the UE's L1 / L2 mobility, the switch command being associated with at least one of (1) a TCI for the beam or (2) at least one RACH parameter for a BWP of the set of candidate cells. Component 199 is also configured to transmit, for the UE, the switch command indicating a switch associated with L1 / L2 mobility of the UE to the candidate cell. In an aspect, component 199 can be configured to transmit, for the UE, at least one of a TCI configuration for the candidate cell or a RACH configuration for the candidate cell before transmitting the switch command, the TCI for the beam being based on the TCI configuration and the at least one RACH parameter being based on the RACH configuration. In an aspect, component 199 can be configured to transmit, for the UE via RRC signaling and before transmitting the switching command, a TCI for the beam, where the TCI for the beam includes at least one of a first legacy TCI state for periodic CSI-RS, first legacy spatial relationship information for periodic SRS or PUCCH, or a list of legacy TCI states for PDSCH. In an aspect, component 199 can be configured to transmit, for the UE, an activation of the TCI for the beam via MAC-CE including at least one of a second legacy TCI state for CORESET or semi-persistent CSI-RS, second legacy spatial relationship information for at least one of semi-persistent SRS, aperiodic SRS, or PUCCH, a subset of legacy TCI states for PDSCH, or path loss RS for at least one SRS or at least one PUSCH. In an aspect, component 199 can be configured to transmit, for the UE, a DCI indicating a third legacy TCI state of the subset of legacy TCI states for the PDSCH.In an aspect, component 199 can be configured to transmit, for the UE via RRC signaling and before receiving the switching command, a TCI for the beam, where the TCI for the beam includes a first consolidated TCI state for periodic CSI-RS or periodic SRS configured to not follow the consolidated TCI indication, or at least one of a list of downlink TCI states, a list of joint TCI states, or a list of uplink TCI states. In an aspect, component 199 can be configured to transmit, for the UE via MAC-CE, an activation of the TCI for the beam including a second consolidated TCI state for at least one of CORESET, semi-persistent CSI-RS, semi-persistent SRS, or aperiodic SRS configured to not follow the consolidated TCI indication. In an aspect, component 199 can be configured to transmit, for the UE, a DCI indicating at least one of a joint TCI state for at least one of the PDSCH, PDCCH, PUSCH, PUCCH, CSI-RS, or SRS configured to follow the joint TCI indication, a downlink TCI state for at least one of the PDSCH, PDCCH, or CSI-RS configured to follow the joint TCI indication, or an uplink TCI state for the PUSCH, PUCCH, or SRS configured to follow the joint TCI indication. In an aspect, component 199 can be configured to transmit, for the UE via the at least one transceiver and RRC signaling, at least one RACH parameter for BWP of the set of candidate cells, the at least one RACH parameter including at least one of (1) a PRACH parameter or (2) at least one BFR parameter. Component 199 may be further configured to perform any of the aspects described in connection with the flowcharts in any of Figures 9-12 and / or any of the aspects performed by the serving cell in any of Figures 4, 5, 6, 7, and 8. Component 199 may reside within processor 1512.Component 199 may be one or more hardware components specifically configured to perform the described processes / algorithms, may be implemented by one or more processors configured to perform the described processes / algorithms, may be stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. Network entity 1560 may include various components configured for various functions. In one configuration, network entity 1560 may include means for configuring a switch command indicating a switch associated with the UE's L1 / L2 mobility to a candidate cell among a set of candidate cells associated with the UE's L1 / L2 mobility, the switch command being associated with at least one of (1) a TCI for the beam or (2) at least one RACH parameter for the BWP of the set of candidate cells. In this configuration, network entity 1560 may include means for transmitting, for the UE, a switch command to the candidate cell indicating a switch associated with the UE's L1 / L2 mobility. In one configuration, the network entity 1560 may include means for transmitting, for the UE, at least one of a TCI configuration for the candidate cell or a RACH configuration for the candidate cell before sending the switch command, where the TCI for the beam is based on the TCI configuration and the at least one RACH parameter is based on the RACH configuration. In one configuration, the network entity 1560 may include means for transmitting, for the UE via RRC signaling and before sending the switch command, a TCI for the beam including at least one of a first legacy TCI state for periodic CSI-RS, first legacy spatial relationship information for periodic SRS or PUCCH, or a list of legacy TCI states for PDSCH.In one configuration, the network entity 1560 may include means for transmitting, for the UE, a DCI indicating a third legacy TCI state of the subset of legacy TCI states for the PDSCH. In one configuration, the network entity 1560 may include means for transmitting, for the UE via RRC signaling and before receiving the switching command, a TCI for the beam, where the TCI for the beam includes a first aggregated TCI state for periodic CSI-RS or periodic SRS configured to not follow the aggregated TCI indication, or at least one of a list of downlink TCI states, a list of joint TCI states, or a list of uplink TCI states. In one configuration, the network entity 1560 may include means for transmitting, for the UE, an activation of the TCI for the beam via the MAC-CE including a second aggregated TCI state for at least one of CORESET, semi-persistent CSI-RS, semi-persistent SRS, or aperiodic SRS configured to not follow the aggregated TCI indication. In one configuration, the network entity 1560 may include means for transmitting, for the UE, DCI indicating at least one of a joint TCI state for at least one of the PDSCH, PDCCH, PUSCH, PUCCH, CSI-RS, or SRS configured to follow the joint TCI indication, a downlink TCI state for at least one of the PDSCH, PDCCH, or CSI-RS configured to follow the joint TCI indication, or an uplink TCI state for the PUSCH, PUCCH, or SRS configured to follow the joint TCI indication.In one configuration, the network entity 1560 may include means for transmitting, via the at least one transceiver and RRC signaling, for the UE, at least one RACH parameter for BWP of the set of candidate cells, the at least one RACH parameter including at least one of (1) a PRACH parameter or (2) at least one BFR parameter. The means may be a component 199 of the network entity 1560 configured to perform the recited functions therewith.

[0131]

[0147] Wireless communication networks, such as LTE networks and / or 5G NR networks, can be designed for UE mobility. Such UE mobility may be Layer 3 mobility, which relies on relatively slow messaging and configuration of the UE for post-mobility communications. As an example, a UE may initially be served by a serving cell, which may include a 5G NR cell or "SCell," a combination of 5G NR and legacy protocols and / or hardware (e.g., an "SpCell" implementation), while candidate cells (e.g., legacy cells, 5G NR cells, etc.) are available to the UE for L3 mobility. The UE may receive an L3 mobility communication from the serving cell for movement via L3 mobility to one of the candidate cells as a new serving cell, and the UE then moves to the new serving cell and initiates its setup (e.g., configuration for beams, transmission configuration indication (TCI), random access channel (RACH), etc.) for communications with it.

[0132]

[0148] However, as mentioned above, L3 mobility may be relatively slow and may not allow pre-configuration for various communications associated with candidate cells for mobility. Aspects described herein provide L1 / L2 mobility for a UE, including beam and RACH pre-configuration for candidate cells, which may be faster and more efficient than L3 mobility. For example, a UE may receive a switch command from a serving cell indicating a switch associated with the UE's L1 / L2 mobility from the serving cell to a candidate cell among a set of candidate cells. The switch command may be associated with RACH parameter(s) for the TCI for the beam and / or BWP of the set of candidate cells. Thus, the UE may be pre-configured to communicate with the candidate cell via L1 / L2 mobility based on the RACH parameter(s) for the TCI and / or BWP for the beam, which may reduce mobility latency.

[0133]

[0149] Various aspects relate generally to inter-cell mobility of a UE. Some aspects, more particularly, relate to L1 / L2 inter-cell mobility of a UE using pre-configuration for beams and RACH of a candidate cell. In some embodiments, the beam may be pre-configured by the serving cell via RRC signaling, MAC-CE, and DCI, and / or via the switch command itself, while the RACH may be pre-configured via RACH parameter(s) for BWP of the candidate cell via RRC signaling, including beam failure recovery configuration.

[0134]

[0150] Certain aspects of the subject matter described in this disclosure may be implemented to achieve one or more of the following potential advantages: In some embodiments, by pre-configuring beams and RACHs for candidate cells in L1 / L2 mobility, the described techniques can be used to reduce mobility latency through fast application of configurations for candidate cells, dynamic switching mechanisms between candidate cells, L1 extensions for inter-cell beam management including L1 measurements and reporting, and beam pointing, inter- and intra-frequency scenarios, etc.

[0135]

[0151] It should be understood that the specific order or hierarchy of the blocks in the disclosed processes / flowcharts is an example of an example approach. Based on design preferences, it should be understood that the specific order or hierarchy of the blocks in those processes / flowcharts can be rearranged. Furthermore, some blocks can be combined or omitted. The accompanying method claims present elements of the various blocks in an example order and are not limited to the specific order or hierarchy presented.

[0136]

[0152] The foregoing 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 general principles defined herein may be applied to other aspects. Therefore, the claims are not limited to the aspects described herein but are to be accorded the full scope consistent with the language of the claims. Reference to an element in the singular does not mean "one and only one," unless so expressly 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, such as "when," do not imply immediate action in response to or during the occurrence of an action; they simply mean that if a condition is met, an action will occur, but that the action does not require any specific or immediate time constraints for its occurrence. 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 expressly stated otherwise, the term "some" refers to one or more. Combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B, and C," "one or more of A, B, and C," and "A, B, C, or any combination thereof" are inclusive of any combination of A, B, and / or C, and may include multiple As, multiple Bs, or multiple Cs.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" can be A only, B only, C only, A and B, A and C, B and C, or A and B and C, and any such combination may include one or more elements of A, B, or C. A set should be interpreted as a set of elements, the number of elements being one or more. Thus, with respect to a set of X, X will include one or more elements. When a first device receives data from or transmits data to a second device, the data can be received / transmitted directly between the first and second devices or indirectly between the first and second devices via a set of devices. A device configured to "output" data, such as a transmission, signal, or message, may transmit the data or send the data to a device that transmits the data, for example, using a transceiver. A device configured to "receive" data, such as a transmission, signal, or message, may receive the data or obtain the data from a device that receives the data, for example, using a transceiver. Information stored in memory includes instructions and / or data. All structural and functional equivalents to the elements of various aspects described throughout this disclosure that are known or later become known to those skilled in the art are expressly incorporated herein by reference and are encompassed by the claims. Furthermore, nothing disclosed herein is intended to be made public, regardless of whether such disclosure is expressly recited in the claims. Terms such as "module," "mechanism," "element," and "device" may not be substitutes for the word "means." Thus, no element of a claim should be construed as a means-plus-function unless the element is expressly recited using the phrase "means for."

[0137]

[0153] As used herein, the phrase "based on" should not be construed as a reference to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase "based on A" (where "A" can be information, a condition, a factor, etc.) shall be construed as "based on at least A," unless expressly stated otherwise.

[0138]

[0154] The following aspects are exemplary only and may be combined with other aspects or teachings described herein without limitation.

[0139]

[0155] Aspect 1 is a method of wireless communication in a UE, the method including: receiving a switch command from a serving cell indicating a switch associated with the UE's Layer 1 or Layer 2 (L1 / L2) mobility from the serving cell to a candidate cell of a set of candidate cells associated with the UE's L1 / L2 mobility, the switch command being associated with at least one of (1) a transmission configuration indication (TCI) for a beam or (2) at least one random access channel (RACH) parameter for a bandwidth portion (BWP) of the set of candidate cells; and communicating with the candidate cell based on at least one of the TCI for the beam or the at least one RACH parameter for the BWP.

[0140]

[0156] Aspect 2 is the method of aspect 1, further including receiving at least one of a TCI configuration for the candidate cell or a RACH configuration for the candidate cell before receiving the switching command, wherein the TCI for the beam is based on the TCI configuration and the at least one RACH parameter is based on the RACH configuration.

[0141]

[0157] Aspect 3 is the method of aspect 1 or 2, further comprising: receiving, via radio resource control (RRC) signaling and before receiving the switching command, from the serving cell, a TCI for the beam, the TCI including at least one of a first legacy TCI state for a periodic channel signal information (CSI) reference signal (CSI-RS), a periodic sounding reference signal (SRS) or a physical uplink control channel (PUCCH), or a list of legacy TCI states for a physical downlink shared channel (PDSCH).

[0142]

[0158] Aspect 4 is the method of aspect 3, further including receiving activation of the TCI for the beam via a medium access control (MAC) control element (MAC-CE) including at least one of a control resource set (CORESET) or a second legacy TCI state for a semi-persistent CSI-RS, second legacy spatial relationship information for at least one of a semi-persistent SRS, an aperiodic SRS, or a PUCCH, a subset of legacy TCI states for a PDSCH, or a path loss RS for at least one SRS or at least one physical uplink shared channel (PUSCH).

[0143]

[0159] Example 5 is the method of example 4, further comprising receiving downlink control information (DCI) indicating a third legacy TCI state of the subset of legacy TCI states for the PDSCH.

[0144]

[0160] Aspect 6 is the method of aspect 1 or 2, further comprising receiving, via radio resource control (RRC) signaling and before receiving the switching command, a TCI for the beam from the serving cell, the TCI including a first aggregated TCI state for a periodic channel signal information (CSI) reference signal (CSI-RS) or a periodic sounding reference signal (SRS) configured to not follow the aggregated TCI indication, or at least one of a list of downlink TCI states, a list of joint TCI states, or a list of uplink TCI states.

[0145]

[0161] Aspect 7 is the method of aspect 6, further including receiving activation of the TCI for the beam via a medium access control (MAC) control element (MAC-CE) including a second integrated TCI state for at least one of a control resource set (CORESET), a semi-persistent CSI-RS, a semi-persistent SRS, or an aperiodic SRS, configured to not follow the integrated TCI instruction.

[0146]

[0162] Aspect 8 is the method of aspect 7, further including receiving downlink control information (DCI) indicating at least one of a joint TCI state for at least one of a physical downlink shared channel (PDSCH), a physical downlink control channel (PDCCH), a physical uplink shared channel (PUSCH), a physical uplink control channel (PUCCH), a CSI-RS, or an SRS configured to follow the joint TCI indication, a downlink TCI state for at least one of a PDSCH, a PDCCH, or a CSI-RS configured to follow the joint TCI indication, or an uplink TCI state for a PUSCH, a PUCCH, or an SRS configured to follow the joint TCI indication.

[0147]

[0163] Example 9 is the method of example 1 or 2, wherein the switching command includes a TCI for the beam.

[0148]

[0164] Aspect 10 is the method of aspect 9, wherein the TCI for the beam includes at least one of a first legacy TCI state for a periodic channel signal information (CSI) reference signal (CSI-RS), first legacy spatial relationship information for a periodic sounding reference signal (SRS) or a physical uplink control channel (PUCCH), a second legacy TCI state for a control resource set (CORESET) or semi-persistent CSI-RS, second legacy spatial relationship information for at least one of semi-persistent SRS, aperiodic SRS, or PUCCH, a path loss RS for at least one of SRS or a physical uplink shared channel (PUSCH), or a third legacy TCI state for a physical downlink shared channel (PDSCH).

[0149]

[0165] Example 11 is a method according to example 10, wherein the switching command includes at least one of a medium access control (MAC) control element (MAC-CE) that activates a TCI for the beam, or downlink control information (DCI) that indicates a TCI for the beam.

[0150]

[0166] Aspect 12 is a method according to any one of aspects 9 to 11, wherein the TCI for the beam includes at least one of an integrated TCI associated with one or more channels and RSs, or a first integrated TCI associated with a first set of one or more channels and RSs configured to follow the integrated TCI instruction, and a second integrated TCI associated with a second set of one or more channels and RSs not configured to follow the integrated TCI instruction.

[0151]

[0167] Aspect 13 is the method of aspect 1 or 2, further comprising receiving at least one RACH parameter for BWP of the set of candidate cells from the serving cell via at least one transceiver of the UE and radio resource control (RRC) signaling, the at least one RACH parameter including at least one of (1) a physical RACH (PRACH) parameter or (2) at least one beam failure recovery (BFR) parameter.

[0152]

[0168] Example 14 is the method of example 13, wherein the PRACH parameters include at least one of a number of PRACH transmission occasions at a time instance based on frequency domain multiplexing (FDM), an offset of the lowest PRACH transmission occasion in the frequency domain relative to an initial physical resource block (PRB), a maximum number of random access preamble transmissions performed before a failure is declared, a power ramping step on the PRACH, or a Message 2 random access response window length in number of slots, and the at least one RACH parameter for the BWP further includes at least one of a total number of PRACH preambles, a number of synchronization signal blocks (SSBs) per RACH occasion, an SSB threshold for selecting the PRACH associated with SSB selection and corresponding PRACH resource selection for path loss estimation and transmission or retransmission operations, an initial value of the PRACH contention resolution timer, a root sequence for the PRACH, a subcarrier spacing for the PRACH, a first configuration of an unrestricted set, a second configuration of at least one type of restricted set, or a transform precoder indication for the Message 3 transmission.

[0153]

[0169] Aspect 15 is the method of aspect 13 or 14, wherein the at least one BFR parameter includes at least one of a BFR PRACH parameter, a root sequence for PRACH-based BFR, a candidate beam threshold, a candidate beam list, a number of synchronization signal blocks (SSBs) per RACH occasion for PRACH-based BFR, a mask for PRACH-based BFR transmission, a BFR search space identifier for PRACH-based BFR, or a BFR timer for PRACH-based BFR.

[0154]

[0170] Aspect 16 is a method of wireless communication in a serving cell, the method including: configuring a switch command indicating a switch associated with Layer 1 or Layer 2 (L1 / L2) mobility of a user equipment (UE) to a candidate cell among a set of candidate cells associated with the UE's L1 / L2 mobility, the switch command being associated with at least one of (1) a transmission configuration indication (TCI) for a beam or (2) at least one random access channel (RACH) parameter for a bandwidth portion (BWP) of the set of candidate cells; and transmitting, for the UE, the switch command indicating a switch associated with the UE's L1 / L2 mobility to the candidate cell.

[0155]

[0171] Aspect 17 is the method of aspect 16, further comprising, for the UE, transmitting at least one of a TCI configuration for the candidate cell or a RACH configuration for the candidate cell before transmitting the switching command, wherein the TCI for the beam is based on the TCI configuration and the at least one RACH parameter is based on the RACH configuration.

[0156]

[0172] Example 18 is the method of example 16 or example 17, further including: transmitting, via radio resource control (RRC) signaling and before transmitting the switching command, for the UE, a TCI for the beam, the TCI including at least one of a first legacy TCI state for a periodic channel signal information (CSI) reference signal (CSI-RS), a periodic sounding reference signal (SRS) or a physical uplink control channel (PUCCH), or a list of legacy TCI states for a physical downlink shared channel (PDSCH).

[0157]

[0173] Example 19 is the method of example 18, further including transmitting, for the UE, via a medium access control (MAC) control element (MAC-CE) including at least one of a control resource set (CORESET) or a second legacy TCI state for a semi-persistent CSI-RS, second legacy spatial relationship information for at least one of a semi-persistent SRS, an aperiodic SRS, or a PUCCH, a subset of legacy TCI states for a PDSCH, or a path loss RS for at least one SRS or at least one physical uplink shared channel (PUSCH), an activation of a TCI for the beam.

[0158]

[0174] Example 20 is the method of example 19, further comprising transmitting, for the UE, downlink control information (DCI) indicating a third legacy TCI state of the subset of legacy TCI states for the PDSCH.

[0159]

[0175] Example 21 is the method of example 16 or 17, further including: transmitting, for the UE via radio resource control (RRC) signaling and before receiving the switching command, a TCI for the beam, the TCI including at least one of a first aggregated TCI state for a periodic channel signal information (CSI) reference signal (CSI-RS) or a periodic sounding reference signal (SRS) configured to not follow the aggregated TCI indication, or at least one of a list of downlink TCI states, a list of joint TCI states, or a list of uplink TCI states.

[0160]

[0176] Example 22 is the method of example 21, further including transmitting, for the UE, an activation of the TCI for the beam via a medium access control (MAC) control element (MAC-CE) including a second integrated TCI state for at least one of a control resource set (CORESET), a semi-persistent CSI-RS, a semi-persistent SRS, or an aperiodic SRS configured to not follow the integrated TCI indication.

[0161]

[0177] Example 23 is the method of example 22, further including transmitting, for the UE, downlink control information (DCI) indicating at least one of a joint TCI state for at least one of a physical downlink shared channel (PDSCH), a physical downlink control channel (PDCCH), a physical uplink shared channel (PUSCH), a physical uplink control channel (PUCCH), a CSI-RS, or an SRS configured to follow the joint TCI indication, a downlink TCI state for at least one of a PDSCH, a PDCCH, or a CSI-RS configured to follow the joint TCI indication, or an uplink TCI state for a PUSCH, a PUCCH, or an SRS configured to follow the joint TCI indication.

[0162]

[0178] Example 24 is the method of example 16 or 17, wherein the switching command includes a TCI for the beam, and the TCI for the beam includes at least one of a first legacy TCI state for a periodic channel signal information (CSI) reference signal (CSI-RS), first legacy spatial relationship information for a periodic sounding reference signal (SRS) or a physical uplink control channel (PUCCH), a second legacy TCI state for a control resource set (CORESET) or semi-persistent CSI-RS, second legacy spatial relationship information for at least one of semi-persistent SRS, aperiodic SRS, or PUCCH, a path loss RS for at least one of SRS or a physical uplink shared channel (PUSCH), or a third legacy TCI state for a physical downlink shared channel (PDSCH).

[0163]

[0179] Example 25 is a method according to example 24, wherein the switching command includes a TCI for the beam, and the switching command includes at least one of a medium access control (MAC) control element (MAC-CE) that activates the TCI for the beam, or downlink control information (DCI) that indicates the TCI for the beam.

[0164]

[0180] Aspect 26 is a method according to aspect 24, wherein the TCI for the beam includes at least one of an integrated TCI associated with one or more channels and RSs, or a first integrated TCI associated with a first set of one or more channels and RSs configured to follow the integrated TCI instruction, and a second integrated TCI associated with a second set of one or more channels and RSs not configured to follow the integrated TCI instruction.

[0165]

[0181] Aspect 27 is the method of aspect 16 or 17, further comprising transmitting, via at least one transceiver of the serving cell and radio resource control (RRC) signaling, for the UE, at least one RACH parameter for BWP of the set of candidate cells, the at least one RACH parameter including at least one of (1) a physical RACH (PRACH) parameter or (2) at least one beam failure recovery (BFR) parameter.

[0166]

[0182] Aspect 28 is an aspect of the present invention in which the PRACH parameters include at least one of a number of PRACH transmission occasions in a time instance based on frequency domain multiplexing (FDM), an offset of the lowest PRACH transmission occasion in the frequency domain relative to an initial physical resource block (PRB), a maximum number of random access preamble transmissions performed before a failure is declared, a power ramping step in the PRACH, or a message 2 random access response window length in number of slots; and the at least one RACH parameter for the BWP further includes at least one of a total number of PRACH preambles, a first number of synchronization signal blocks (SSBs) per RACH occasion, an SSB threshold for selecting a PRACH associated with SSB selection and corresponding PRACH resource selection for path loss estimation and transmission or retransmission operations, an initial value of a PRACH contention resolution timer, a first root sequence for the PRACH, a subcarrier spacing for the PRACH, a first configuration of an unrestricted set, a second configuration of at least one type of restricted set, or a transform precoder indication for a message 3 transmission; and the at least one BFR parameter is an aspect of the present invention in which the at least one BFR parameter is a BFR 28. The method of aspect 27, comprising at least one of a PRACH parameter, a second root sequence for the PRACH-based BFR, a candidate beam threshold, a candidate beam list, a second number of SSBs per RACH occasion for the PRACH-based BFR, a mask for the PRACH-based BFR transmission, a BFR search space identifier for the PRACH-based BFR, or a BFR timer for the PRACH-based BFR.

[0167]

[0183] Aspect 29 is an apparatus for wireless communication including means for implementing any of aspects 1 to 15.

[0168]

[0184] Embodiment 30 is a computer-readable medium (e.g., a non-transitory computer-readable medium) storing computer-executable code that, when executed by at least one processor, causes the at least one processor to perform any of embodiments 1 through 15.

[0169]

[0185]

[0013] Aspect 31 is an apparatus for wireless communication in a network node, the apparatus including: a memory; and at least one processor coupled to the memory, wherein the at least one processor is configured to perform any of aspects 1 through 15 based at least in part on information stored in the memory.

[0170]

[0186] Aspect 32 is the apparatus of aspect 31, further comprising at least one of a transceiver or an antenna coupled to the at least one processor.

[0171]

[0187] Aspect 33 is an apparatus for wireless communication including means for implementing any of aspects 16 to 28.

[0172]

[0188] Aspect 34 is a computer-readable medium (e.g., a non-transitory computer-readable medium) storing computer-executable code that, when executed by at least one processor, causes the at least one processor to perform any of aspects 16 through 28.

[0173]

[0189]

[0023] Aspect 35 is an apparatus for wireless communication in a network node. The apparatus includes a memory and at least one processor coupled to the memory, wherein the at least one processor is configured to perform any of aspects 16-28 based at least in part on information stored in the memory.

[0174]

[0190] Aspect 36 is the apparatus of aspect 35, further comprising at least one of a transceiver or an antenna coupled to the at least one processor.

Claims

1. 1. An apparatus for wireless communication in a user equipment (UE), comprising: Memory and at least one processor coupled to the memory; and wherein, based at least in part on information stored in the memory, the at least one processor: receiving, from a serving cell, a switch command indicating a switch associated with Layer 1 or Layer 2 (L1 / L2) mobility of the UE from the serving cell to a candidate cell among a set of candidate cells associated with the L1 / L2 mobility of the UE, the switch command being associated with at least one of (1) a transmission configuration indication (TCI) for a beam, or (2) at least one random access channel (RACH) parameter for a bandwidth portion (BWP) of the set of candidate cells; communicating with the candidate cell based on the at least one of the TCI for the beam or the at least one RACH parameter for the BWP; It is configured as follows: Device.

2. the at least one processor: and further configured to receive at least one of a TCI configuration for the candidate cell or a RACH configuration for the candidate cell before receiving the switching command, wherein the TCI for the beam is based on the TCI configuration and the at least one RACH parameter is based on the RACH configuration.

10. The apparatus of claim 1.

3. the at least one processor: and further configured to receive the TCI for the beam from the serving cell via radio resource control (RRC) signaling before receiving the switching command, wherein the TCI for the beam comprises: a first legacy TCI state for periodic channel signal information (CSI) reference signals (CSI-RS); first legacy spatial relationship information for a periodic sounding reference signal (SRS) or a physical uplink control channel (PUCCH); or A list of legacy TCI states for the Physical Downlink Shared Channel (PDSCH); at least one of:

10. The apparatus of claim 1.

4. the at least one processor: and further configured to receive activation of the TCI for the beam via a Medium Access Control (MAC) Control Element (MAC-CE), the MAC-CE comprising: a second legacy TCI state for the control resource set (CORESET) or semi-persistent CSI-RS; second legacy spatial relationship information for at least one of a semi-persistent SRS, a non-periodic SRS, or the PUCCH; a subset of the legacy TCI states for the PDSCH; or a path loss RS for at least one SRS or at least one physical uplink shared channel (PUSCH); at least one of:

4. The apparatus of claim 3.

5. the at least one processor: and further configured to receive downlink control information (DCI) indicating a third legacy TCI state of the subset of legacy TCI states for the PDSCH.

5. The apparatus of claim 4.

6. the at least one processor: and further configured to receive the TCI for the beam from the serving cell via radio resource control (RRC) signaling before receiving the switching command, wherein the TCI for the beam comprises: a first aggregated TCI state for a periodic channel signal information (CSI) reference signal (CSI-RS) or a periodic sounding reference signal (SRS) configured to not follow the aggregated TCI indication; or at least one of a list of downlink TCI states, a list of joint TCI states, or a list of uplink TCI states; at least one of:

10. The apparatus of claim 1.

7. the at least one processor: and further configured to receive activation of the TCI for the beam via a medium access control (MAC) control element (MAC-CE) including a second integrated TCI state for at least one of a control resource set (CORESET), a semi-persistent CSI-RS, a semi-persistent SRS, or an aperiodic SRS, the control element configured to not follow the integrated TCI indication.

7. The apparatus of claim 6.

8. the at least one processor: Downlink control information (DCI), a joint TCI state for at least one of a physical downlink shared channel (PDSCH), a physical downlink control channel (PDCCH), a physical uplink shared channel (PUSCH), a physical uplink control channel (PUCCH), a CSI-RS, or an SRS configured to follow the joint TCI indication; a downlink TCI state for at least one of the PDSCH, the PDCCH, or the CSI-RS configured to follow the consolidated TCI indication; or an uplink TCI state for the PUSCH, the PUCCH, or the SRS configured to follow the consolidated TCI indication; and further configured to receive a DCI indicating at least one of:

8. The apparatus of claim 7.

9. The apparatus of claim 1 , wherein the switching command includes the TCI for the beam.

10. The TCI for the beam is: a first legacy TCI state for periodic channel signal information (CSI) reference signals (CSI-RS); first legacy spatial relationship information for a periodic sounding reference signal (SRS) or a physical uplink control channel (PUCCH); a second legacy TCI state for the control resource set (CORESET) or semi-persistent CSI-RS; second legacy spatial relationship information for at least one of a semi-persistent SRS, a non-periodic SRS, or the PUCCH; a path loss RS for at least one of an SRS or a physical uplink shared channel (PUSCH); or a third legacy TCI state for the Physical Downlink Shared Channel (PDSCH); at least one of:

10. The apparatus of claim 9.

11. The switching command is a Medium Access Control (MAC) Control Element (MAC-CE) that activates the TCI for the beam; or Downlink Control Information (DCI) indicating the TCI for the beam; at least one of:

11. The apparatus of claim 10.

12. The TCI for the beam is: an aggregate TCI associated with one or more channels and RSs; or a first aggregated TCI associated with the one or more channels and a first set of RSs, the first aggregated TCI being configured to comply with an aggregated TCI indication, and a second aggregated TCI associated with the one or more channels and a second set of RSs, the second aggregated TCI not being configured to comply with the aggregated TCI indication; at least one of:

10. The apparatus of claim 9.

13. and at least one transceiver coupled to the at least one processor, the at least one processor comprising: and further configured to receive, from the serving cell via the at least one transceiver and via radio resource control (RRC) signaling, the at least one RACH parameter for the BWP of the set of candidate cells, the at least one RACH parameter including at least one of (1) a physical RACH (PRACH) parameter or (2) at least one beam failure recovery (BFR) parameter.

10. The apparatus of claim 1.

14. The PRACH parameters are: the number of PRACH transmission occasions in a time instance based on frequency domain multiplexing (FDM); the offset of the lowest PRACH transmission occasion in the frequency domain relative to the initial physical resource block (PRB); The maximum number of random access preamble transmissions performed before a failure is declared, a power ramping step on the PRACH, or Message 2 Random Access Response Window Length in number of slots, and The at least one RACH parameter for the BWP is: the total number of PRACH preambles, the number of synchronization signal blocks (SSBs) per RACH occasion, an SSB threshold for selecting the PRACH associated with an SSB selection and corresponding PRACH resource selection for path loss estimation and transmission or retransmission operations; The initial value of the PRACH contention resolution timer, a root sequence for the PRACH; a subcarrier spacing for the PRACH; a first configuration of the unlimited set; a second configuration of the restricted set of at least one type; or Transform precoder indication for message 3 transmission, further comprising at least one of 14. The apparatus of claim 13.

15. The at least one BFR parameter is: BFR PRACH parameters, Root sequence for PRACH-based BFR; candidate beam threshold, Candidate beam list, the number of synchronization signal blocks (SSBs) per RACH occasion for the PRACH-based BFR; a mask for PRACH-based BFR transmissions; a BFR search space identifier for the PRACH-based BFR; or a BFR timer for the PRACH-based BFR; at least one of:

14. The apparatus of claim 13.

16. 1. An apparatus for wireless communication in a serving cell, comprising: Memory and at least one processor coupled to the memory; and wherein, based at least in part on information stored in the memory, the at least one processor: configuring a switch command indicating a switch associated with Layer 1 or Layer 2 (L1 / L2) mobility of a user equipment (UE) to a candidate cell among a set of candidate cells associated with the L1 / L2 mobility of the UE, the switch command being associated with at least one of (1) a transmission configuration indication (TCI) for a beam or (2) at least one random access channel (RACH) parameter for a bandwidth portion (BWP) of the set of candidate cells; sending, for the UE, the switch command to the candidate cell indicating the switch associated with the L1 / L2 mobility of the UE; It is configured as follows: Device.

17. the at least one processor: The method is further configured for the UE to transmit at least one of a TCI configuration for the candidate cell or a RACH configuration for the candidate cell before transmitting the switching command, wherein the TCI for the beam is based on the TCI configuration and the at least one RACH parameter is based on the RACH configuration.

17. The apparatus of claim 16.

18. the at least one processor: and transmitting, for the UE via radio resource control (RRC) signaling and before transmitting the switching command, the TCI for the beam, wherein the TCI for the beam comprises: a first legacy TCI state for periodic channel signal information (CSI) reference signals (CSI-RS); first legacy spatial relationship information for a periodic sounding reference signal (SRS) or a physical uplink control channel (PUCCH); or A list of legacy TCI states for the Physical Downlink Shared Channel (PDSCH); at least one of:

17. The apparatus of claim 16.

19. the at least one processor: and transmitting, for the UE, activation of the TCI for the beam via a Medium Access Control (MAC) Control Element (MAC-CE), wherein the MAC-CE: a second legacy TCI state for the control resource set (CORESET) or semi-persistent CSI-RS; second legacy spatial relationship information for at least one of a semi-persistent SRS, a non-periodic SRS, or the PUCCH; a subset of the legacy TCI states for the PDSCH; or a path loss RS for at least one SRS or at least one physical uplink shared channel (PUSCH); at least one of:

20. The apparatus of claim 18.

20. the at least one processor: and transmitting, for the UE, downlink control information (DCI) indicating a third legacy TCI state of the subset of legacy TCI states for the PDSCH.

20. The apparatus of claim 19.

21. the at least one processor: and transmitting, for the UE, via radio resource control (RRC) signaling and before receiving the switching command, the TCI for the beam, wherein the TCI for the beam comprises: a first aggregated TCI state for a periodic channel signal information (CSI) reference signal (CSI-RS) or a periodic sounding reference signal (SRS) configured to not follow the aggregated TCI indication; or at least one of a list of downlink TCI states, a list of joint TCI states, or a list of uplink TCI states; at least one of:

17. The apparatus of claim 16.

22. the at least one processor: and transmitting, for the UE, activation of the TCI for the beam via a medium access control (MAC) control element (MAC-CE) including a second integrated TCI state for at least one of a control resource set (CORESET), a semi-persistent CSI-RS, a semi-persistent SRS, or an aperiodic SRS, the second integrated TCI state being configured to not follow the integrated TCI indication.

22. The apparatus of claim 21.

23. the at least one processor: and further configured to transmit, for the UE, downlink control information (DCI), the DCI comprising: a joint TCI state for at least one of a physical downlink shared channel (PDSCH), a physical downlink control channel (PDCCH), a physical uplink shared channel (PUSCH), a physical uplink control channel (PUCCH), a CSI-RS, or an SRS configured to follow the joint TCI indication; a downlink TCI state for at least one of the PDSCH, the PDCCH, or the CSI-RS configured to follow the consolidated TCI indication; or an uplink TCI state for the PUSCH, the PUCCH, or the SRS configured to follow the consolidated TCI indication; Indicating at least one of 23. The apparatus of claim 22.

24. the switching command includes the TCI for the beam; The TCI for the beam is: a first legacy TCI state for periodic channel signal information (CSI) reference signals (CSI-RS); first legacy spatial relationship information for a periodic sounding reference signal (SRS) or a physical uplink control channel (PUCCH); a second legacy TCI state for the control resource set (CORESET) or semi-persistent CSI-RS; second legacy spatial relationship information for at least one of a semi-persistent SRS, a non-periodic SRS, or the PUCCH; a path loss RS for at least one of an SRS or a physical uplink shared channel (PUSCH); or a third legacy TCI state for the Physical Downlink Shared Channel (PDSCH); at least one of:

17. The apparatus of claim 16.

25. The switching command includes the TCI for the beam, and the switching command includes: a Medium Access Control (MAC) Control Element (MAC-CE) that activates the TCI for the beam; or Downlink Control Information (DCI) indicating the TCI for the beam; at least one of:

17. The apparatus of claim 16.

26. The TCI for the beam is: an aggregate TCI associated with one or more channels and RSs; or a first aggregated TCI associated with the one or more channels and a first set of RSs, the first aggregated TCI being configured to comply with an aggregated TCI indication, and a second aggregated TCI associated with the one or more channels and a second set of RSs, the second aggregated TCI not being configured to comply with the aggregated TCI indication; at least one of:

25. The apparatus of claim 24.

27. and at least one transceiver coupled to the at least one processor, the at least one processor comprising: and transmitting, via the at least one transceiver and via radio resource control (RRC) signaling, for the UE, the at least one RACH parameter for the BWP of the set of candidate cells, the at least one RACH parameter including at least one of (1) a physical RACH (PRACH) parameter or (2) at least one beam failure recovery (BFR) parameter.

17. The apparatus of claim 16.

28. The PRACH parameters are: the number of PRACH transmission occasions in a time instance based on frequency domain multiplexing (FDM); the offset of the lowest PRACH transmission occasion in the frequency domain relative to the initial physical resource block (PRB); The maximum number of random access preamble transmissions performed before a failure is declared, a power ramping step on the PRACH, or Message 2 Random Access Response Window Length in number of slots, and The at least one RACH parameter for the BWP is: the total number of PRACH preambles, a first number of synchronization signal blocks (SSBs) per RACH occasion; an SSB threshold for selecting the PRACH associated with an SSB selection and corresponding PRACH resource selection for path loss estimation and transmission or retransmission operations; The initial value of the PRACH contention resolution timer, a first root sequence for the PRACH; a subcarrier spacing for the PRACH; a first configuration of the unlimited set; a second configuration of the restricted set of at least one type; or Transform precoder indication for message 3 transmission, and further comprising at least one of The at least one BFR parameter is: BFR PRACH parameters, a second root sequence for PRACH-based BFR; candidate beam threshold, Candidate beam list, a second number of SSBs per RACH occasion for the PRACH-based BFR; a mask for PRACH-based BFR transmissions; a BFR search space identifier for the PRACH-based BFR; or a BFR timer for the PRACH-based BFR; at least one of:

28. The apparatus of claim 27.

29. 1. A method of wireless communication in a user equipment (UE), comprising: receiving, from a serving cell, a switch command indicating a switch associated with Layer 1 or Layer 2 (L1 / L2) mobility of the UE from the serving cell to a candidate cell among a set of candidate cells associated with the L1 / L2 mobility of the UE, the switch command being associated with at least one of (1) a transmission configuration indication (TCI) for a beam, or (2) at least one random access channel (RACH) parameter for a bandwidth portion (BWP) of the set of candidate cells; communicating with the candidate cell based on the at least one of the TCI for the beam or the at least one RACH parameter for the BWP; A method comprising:

30. 1. A method of wireless communication in a serving cell, comprising: configuring a switch command indicating a switch associated with a Layer 1 or Layer 2 (L1 / L2) mobility of a user equipment (UE) to a candidate cell among a set of candidate cells associated with the L1 / L2 mobility of the UE, the switch command being associated with at least one of (1) a transmission configuration indication (TCI) for a beam or (2) at least one random access channel (RACH) parameter for a bandwidth portion (BWP) of the set of candidate cells; sending, for the UE, the switch command to the candidate cell indicating the switch associated with the L1 / L2 mobility of the UE; A method comprising:

Images