NW Assistance For Measurement And Mobility Enhancement

Abstract

A method for wireless communication at a source node and a related device is provided. In the method, the source node receives a user equipment (UE) request for on-demand allocation of mobility measurement resources or mobility reporting resources for the UE, and provides a configuration, allocation, or activation for the mobility measurement resources or the mobility reporting resources in response to the UE request.

Description

[0001] Cross - Reference to Related Applications

[0002] This application claims the benefit and priority of U.S. Provisional Application Serial No. 63 / 385,389, filed on November 29, 2022, entitled "NW ASSISTANCE FOR MEASUREMENT AND MOBILITY ENHANCEMENT", and U.S. Non - Provisional Patent Application Serial No. 18 / 476,201, filed on September 27, 2023, entitled "NW ASSISTANCE FOR MEASUREMENT AND MOBILITY ENHANCEMENT", the entire disclosures of which are hereby incorporated by reference in their entireties. Technical Field

[0003] This disclosure generally relates to communication systems, and more particularly, to network assistance for measurement and mobility enhancement in wireless communication. Background Art

[0004] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasting. A typical wireless communication system 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.

[0005] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at the urban, national, regional, and even global levels. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the continuous evolution of mobile broadband promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)), and other requirements. 5G NR includes services associated with Enhanced Mobile Broadband (eMBB), Massive Machine - Type Communication (mMTC), and Ultra - Reliable Low - Latency Communication (URLLC). Certain aspects of 5G NR may be based on the 4G Long - Term Evolution (LTE) standard. Further improvements to 5G NR technology are needed. Additionally, these improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the Invention

[0006] A simplified review of one or more aspects is presented below to provide a basic understanding of these aspects. This Summary is not an extensive review of all contemplated aspects. It neither identifies key or critical elements of all aspects nor describes 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.

[0007] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus for wireless communication at a source node are provided. The apparatus may include a memory and at least one processor coupled to the memory. At least in part based on information stored in the memory, the at least one processor may be configured to receive a UE request for an on-demand allocation of mobility measurement resources or mobility reporting resources for a UE; and provide a configuration, an allocation, or an activation of the mobility measurement resources or the mobility reporting resources in response to the UE request.

[0008] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus for wireless communication at a user equipment (UE) are provided. The apparatus may include a memory and at least one processor coupled to the memory. At least in part based on information stored in the memory, the at least one processor may be configured to send a UE request for an on-demand allocation of mobility measurement resources or mobility reporting resources for the UE; and receive a configuration, an allocation, or an activation of the mobility measurement resources or the mobility reporting resources in response to the UE request.

[0009] To achieve the foregoing and related purposes, one or more aspects may include the features described in detail below and particularly pointed out in the claims. The following description and the drawings set forth in detail some illustrative features of one or more aspects. However, these features are indicative of only some of the various ways in which the principles of the various aspects may be employed. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0011] Figure 2A is a diagram illustrating an example of a first frame in accordance with various aspects of the present disclosure.

[0012] Figure 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] Figure 2C is a diagram illustrating an example of a second frame in accordance with various aspects of the present disclosure.

[0014] Figure 2DIs a diagram illustrating an example of an uplink (UL) channel within a subframe according to various aspects of the present disclosure.

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

[0016] Figure 4 Is a diagram illustrating an example of a UE mobility configuration.

[0017] Figure 5 Is a diagram illustrating a conditional handover.

[0018] Figure 6 Is a diagram illustrating an example of a BWP switch according to various aspects of the present disclosure.

[0019] Figure 7 Is a diagram illustrating an example of a measurement model.

[0020] Figure 8 Is a call flow diagram illustrating network-assisted on-demand RS transmission / activation according to various aspects of the present disclosure.

[0021] Figure 9 Is a call flow diagram illustrating network-assisted timer adaptation for BWP switching and mobility according to various aspects of the present disclosure.

[0022] Figure 10 Is a call flow diagram illustrating a method of wireless communication according to various aspects of the present disclosure.

[0023] Figure 11 Is a flowchart illustrating a method of wireless communication at a source node according to various aspects of the present disclosure.

[0024] Figure 12 Is a flowchart illustrating a method of wireless communication at a source node according to various aspects of the present disclosure.

[0025] Figure 13 Is a flowchart illustrating a method of wireless communication at a source node according to various aspects of the present disclosure.

[0026] Figure 14 Is a flowchart illustrating a method of wireless communication at a network entity according to various aspects of the present disclosure.

[0027] Figure 15 Is a flowchart illustrating a method of wireless communication at a UE according to various aspects of the present disclosure.

[0028] Figure 16 Is a flowchart illustrating a method of wireless communication at a UE according to various aspects of the present disclosure.

[0029] Figure 17 is a flowchart illustrating a method for wireless communication at a UE in accordance with various aspects of the present disclosure.

[0030] Figure 18 is a diagram illustrating an example of a hardware implementation for example devices and / or network entities.

[0031] Figure 19 is a diagram illustrating an example of a hardware implementation for example network entities. DETAILED DESCRIPTION

[0032] In wireless communication, a user equipment (UE) may switch its connection from one cell (e.g., a source cell) to another cell (e.g., a target cell) based on measurements of reference signals (RSs), which is a process known as a handover (HO) operation. HO failures, which may occur due to various reasons such as the source cell not receiving a measurement report or the HO command not reaching the UE, may have a significant impact on network performance. One way to address this problem is conditional handover (CHO), which improves mobility robustness by pre-preparing multiple candidate target cells. While CHO enhances the robustness and reliability of HO, it also increases signaling overhead, thereby reducing the spectral and energy efficiency of the network. Additionally, bandwidth part (BWP) switching during HO may exacerbate the latency and power issues of HO. The example aspects presented herein provide methods and apparatuses for network (NW)-assisted, on-demand reference signal (RS) transmission / activation and repetition of mobility signaling by the network. NW assistance enables on-demand transmission or activation of non-periodic or periodic downlink (DL) RSs to facilitate HO operations, where the non-periodic or periodic downlink (DL) RSs are configured for layer 1 (L1) or layer 3 (L3) measurements of source and / or target cells.

[0033] The various aspects generally relate to wireless communication. Some aspects more specifically relate to network assistance for measurements and mobility enhancements in wireless communication. In some examples, a source node of a network may receive a UE request for an on-demand allocation of mobility measurement resources or mobility reporting resources; and provide a configuration, allocation, or activation of the mobility measurement resources or mobility reporting resources in response to the UE request. In some examples, a source node of a network may receive a request for a downlink reference signal configured for layer 1 (L1), layer 2 (L2), or layer 3 (L3) measurements at a UE from a source node; and provide a reference signal configuration for the UE in response to the request. In some examples, a network entity may receive mobility measurement information from a UE triggering or indicating a cell handover, a change of a primary cell in dual connectivity, a transmit receive point (TRP) handover, or a beam switch; and provide an indication of repeated mobility signaling indicating the cell handover, the change of the primary cell, the TRP handover, or the beam switch.

[0034] Certain aspects of the subject matter described in this disclosure can be implemented to realize one or more of the following potential advantages. In some examples, by providing a configuration, allocation, or activation of mobility measurement resources or mobility reporting resources in response to an on-demand allocation of UE requests for mobility measurement resources or mobility reporting resources, or by providing a reference signal configuration for a UE in response to a request from a source node for a downlink reference signal configured for L1, L2, or L3 measurements, the techniques described can be used to mitigate a potential increase in latency / overhead / power caused by an undesired BWP switch during a handover (HO) (including network-initiated HO, conditional handover (CHO), conditional primary serving cell (PSCell) change (CPC), etc.). On-demand resources can allow the network to reserve fewer resources for UE mobility and increase resources based on UE requests, thereby reducing network signaling and power overhead. Based on measurement conditions, a UE may request additional RS resources for better measurements and request an additional BWP timer mechanism to improve HO success, thereby avoiding inactivity timer expiration. BWP inactivity timer adaptation signaling helps avoid BWP switches during handovers.

[0035] The detailed description set forth below in connection with the accompanying drawings is a description of various configurations and does not represent the only configurations in which the concepts described herein can be practiced. To provide a thorough understanding of the various concepts, the detailed description includes specific details. However, the concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form in order to avoid obscuring such concepts.

[0036] Certain aspects of a telecommunications system 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 can be implemented using electronic hardware, computer software, or any combination thereof. Whether an element is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.

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

[0038] Thus, in one or more example aspects, embodiments, and / or use cases, the described functionality can be implemented in hardware, software, or any combination thereof. If implemented in software, the functionality can be stored or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media includes computer storage media. Storage media can be any available media that can be accessed by a computer. By way of example, such computer-readable media can 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 these types of computer-readable media, or any other media that can be used to store computer-executable code in the form of instructions or data structures that can be accessed by a computer.

[0039] While aspects, embodiments, and / or use cases are described by way of some examples in this application, additional or different aspects, embodiments, and / or use cases may arise in many different arrangements and scenarios. The aspects, embodiments, and / or use cases described herein may be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, aspects, embodiments, and / or use cases may be embodied via integrated chips and other devices based on non-module components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchase devices, medical devices, artificial intelligence (AI)-enabled devices, etc.). Although some examples may or may not be specifically targeted at use cases or applications, the examples described may have broad applicability. Aspects, embodiments, and / or use cases may range from chip-level or modular components to non-modular, non-chip-level embodiments, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more of the technologies herein. In some practical settings, devices incorporating the aspects and features described may also include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily involve multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The technologies described herein may be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated components, or disaggregated components, end-user devices, etc., of various sizes, shapes, and configurations.

[0040] The deployment of a communication system such as a 5G NR system can be arranged in various ways using various components or constituent parts. In a 5G NR system or network, network nodes, network entities, mobility elements of the network, radio access network (RAN) nodes, core network nodes, network elements, or network equipment (such as a base station (BS)) or one or more units (or one or more components) performing base station functions may be implemented in an aggregated or disaggregated architecture. For example, a BS (such as a Node B (NB), evolved NB (eNB), NR BS, 5G NB, access point (AP), TRP, or cell, etc.) may be implemented as an aggregated base station (also referred to as a stand-alone BS or monolithic BS) or a disaggregated base station.

[0041] 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 split base station may be configured to utilize a protocol stack that is physically or logically distributed between two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed among 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).

[0042] Base station operation or network design may consider the aggregation characteristics of base station functionality. For example, a split base station may be used in an integrated access backhaul (IAB) network, an open radio access network (O-RAN, such as a network configuration advocated by the O-RAN Alliance), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Splitting may include distributing functions across two or more units at various physical locations, as well as virtualizing the function of at least one unit, which may achieve flexibility in network design. The various units of a split base station or a split RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0043] Figure 1 FIG. 100 is a diagram illustrating an example of a wireless communication system and an access network. The illustrated wireless communication system includes a split base station architecture. The split base station architecture may include one or more CUs 110, which may communicate directly with the core network 120 via a backhaul link, or indirectly with the core network 120 through one or more split base station units, such as a near real-time (near RT) RAN intelligent controller (RIC) 125 via an E2 link, or a non-real-time (non RT) RIC 115 associated with a service management and orchestration (SMO) framework 105, or both. The CU 110 may communicate with one or more DUs 130 via a respective midhaul link, such as an F1 interface. The DU 130 may communicate with one or more RUs 140 via a respective fronthaul link. The RU 140 may communicate with a respective UE 104 via one or more radio frequency (RF) access links. In some embodiments, the UE 104 may be served simultaneously by multiple RUs 140.

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

[0045] In some aspects, the CU 110 may host one or more higher 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 using an interface that is configured to communicate signals with other control functions hosted by the CU 110. The CU 110 may be configured to handle user plane functionality (i.e., Central Unit - User Plane (CU-UP)), control plane functionality (i.e., Central Unit - Control Plane (CU-CP)), or a combination thereof. In some embodiments, 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 may communicate bi-directionally with the CU-CP units via an interface (such as an E1 interface). As needed, the CU 110 may be implemented to communicate with the DU 130 for network control and signaling.

[0046] The DU 130 may correspond to a logical unit that includes 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 the Radio Link Control (RLC) layer, Medium Access Control (MAC) layer, and one or more high Physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation, and demodulation, etc.) at least partially according to a function split (such as those defined by 3GPP). In some aspects, the DU 130 may also host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by the DU 130 or with control functions hosted by the CU 110.

[0047] The lower layer functions can be implemented by one or more RUs 140. In some deployments, the RUs 140 controlled by the DU 130 can correspond to logical nodes that host RF processing functions or low PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.) or both, at least partially based on function splitting (such as lower layer function splitting). In such an architecture, the RU 140 can be implemented to handle over-the-air (OTA) communication with one or more UEs 104. In some specific implementations, the real-time and non-real-time aspects of the control plane and user plane communication with the RU 140 can be controlled by the corresponding DU 130. In some scenarios, this configuration enables the implementation of the DU 130 and CU 110 in a cloud-based RAN architecture (such as a vRAN architecture).

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

[0049] The non-RT RIC 115 can 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 updating, or policy-based guidance of applications / features in the near-RT RIC 125. The non-RT RIC 115 can be coupled to or communicate with the near-RT RIC 125 (such as via the A1 interface). The near-RT RIC 125 can be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via the E2 interface) that connects one or more CUs 110, one or more DUs 130, or both, and the O-eNB to the near-RT RIC 125.

[0050] In some specific implementations, to generate an AI / ML model to be deployed in the near-RT RIC 125, the non-RT RIC 115 can receive parameters or external enrichment information from an external server. Such information can be utilized by the near-RT RIC 125 and can be received from non-network data sources or from network functions at the SMO framework 105 or at the non-RT RIC 115. In some examples, the non-RT RIC 115 or the near-RT RIC 125 can be configured to tune RAN behavior or performance. For example, the non-RT RIC 115 can monitor long-term trends and patterns of performance and employ an AI / ML model to perform corrective actions via the SMO framework 105 (such as via reconfiguration of O1) or via creation of RAN management policies (such as A1 policies).

[0051] At least one of CU 110, DU 130, and RU 140 may be referred to as base station 102. Thus, base station 102 may include one or more of CU 110, DU 130, and RU 140 (each component is indicated by a dashed line to indicate that each component may or may not be included in base station 102). Base station 102 provides an access point to core network 120 for UE 104. Base station 102 may include macro cells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Small cells include femto cells, pico cells, and micro cells. A network including both small cells and macro cells may be referred to as a heterogeneous network. The heterogeneous network may also include a home evolved Node B (HeNB), which may provide services to a restricted group referred to as a closed subscriber group (CSG). The communication link between RU 140 and UE 104 may include an uplink (UL) (also referred to as a reverse link) transmission from UE 104 to RU 140 and / or a downlink (DL) (also referred to as a forward link) transmission from RU 140 to UE 104. The communication link may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may be via one or more carriers. For each carrier allocated in carrier aggregation of up to a total of Yx MHz (x component carriers) for transmission in each direction, base station 102 / UE 104 may use a spectrum with a bandwidth of up to Y MHz (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, etc.). These carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric for DL and UL (e.g., more or fewer carriers may be allocated for DL compared to UL). Component carriers may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as the primary cell (PCell) and the secondary component carriers may be referred to as secondary cells (SCells).

[0052] Some UEs 104 may use device-to-device (D2D) communication link 158 to communicate with each other. D2D communication link 158 may use DL / UL wireless wide area network (WWAN) spectrum. D2D communication link 158 may use one or more sidelink channels, such as physical sidelink broadcast channel (PSBCH), physical sidelink discovery channel (PSDCH), physical sidelink shared channel (PSSCH), and physical sidelink control channel (PSCCH). D2D communication may be carried out through various wireless D2D communication systems, such as for example Bluetooth TM (Bluetooth is a trademark of the Bluetooth Special Interest Group (SIG)), Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard TM (Wi-Fi is a trademark of the Wi-Fi Alliance), LTE, or NR.

[0053] The wireless communication system may also include a Wi-Fi AP 150 that communicates with a UE 104 (also referred to as a Wi-Fi station (STA)) via a communication link 154, for example, in an unlicensed spectrum such as the 5 GHz unlicensed spectrum. When communicating in an unlicensed spectrum, the UE 104 / AP 150 may perform a Clear Channel Assessment (CCA) before communication to determine whether the channel is available.

[0054] The electromagnetic spectrum is generally subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as Frequency Range Designation FR1 (410 MHz - 7.125 GHz) and FR2 (24.25 GHz - 52.6 GHz). Although a part of FR1 is greater than 6 GHz, in various documents and articles, FR1 is generally referred to (interchangeably) as the "sub-6 GHz" band. Regarding FR2, a similar naming issue sometimes occurs, which is generally (interchangeably) referred to as the "millimeter wave" band in documents and articles, although it is different from the Extremely High Frequency (EHF) band (30 GHz - 300 GHz) identified by the International Telecommunication Union (ITU) as the "millimeter wave" band.

[0055] The frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as Frequency Range Designation FR3 (7.125 GHz - 24.25 GHz). The bands falling within FR3 may inherit FR1 characteristics and / or FR2 characteristics, and thus can effectively extend the features of FR1 and / or FR2 to the mid-band frequencies. In addition, higher bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as Frequency Range Designation FR2-2 (52.6 GHz - 71 GHz), FR4 (71 GHz - 114.25 GHz), and FR5 (114.25 GHz - 300 GHz). Each of these higher bands falls within the EHF band.

[0056] Considering the above aspects, unless otherwise specifically stated, if terms such as "sub-6 GHz" are used in this document, they may broadly represent frequencies that can be less than 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise specifically stated, if terms such as "millimeter wave" are used in this document, they may broadly represent frequencies that can include mid-band frequencies, can be within FR2, FR4, FR2-2, and / or FR5, or can be within the EHF band.

[0057] Base station 102 and UE 104 may each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming. Base station 102 may transmit beamformed signal 182 to UE 104 in one or more transmission directions. UE 104 may receive the beamformed signal from base station 102 in one or more reception directions. UE 104 may also transmit beamformed signal 184 to base station 102 in one or more transmission directions. Base station 102 may receive the beamformed signal from UE 104 in one or more reception directions. Base station 102 / UE 104 may perform beam training to determine the optimal reception and transmission directions for each of base station 102 / UE 104. The transmission direction and reception direction of base station 102 may be the same or may not be the same. The transmission direction and reception direction of UE 104 may be the same or may not be the same.

[0058] Base station 102 may include and / or be referred to as gNB, Node B, eNB, access point, base station transceiver, 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 term. Base station 102 may be implemented as an integrated access and backhaul (IAB) node, relay node, sidelink node, a convergent (monolithic) base station with a baseband unit (BBU) (including CU and DU) and RU, or may be implemented as a disaggregated base station including one or more of CU, DU, and / or RU. A set of base stations including disaggregated base stations and / or convergent base stations may be referred to as next generation (NG) RAN (NG-RAN).

[0059] 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 processes 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 the generation of Authentication and Key Agreement (AKA) credentials, user identity handling, access authorization, and subscription management. One or more Location Servers 168 are illustrated as including a Gateway Mobile Location Center (GMLC) 165 and a Location Management Function (LMF) 166. However, in general, one or more Location Servers 168 may include one or more location / locationing 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 location information. The LMF 166 receives measurements and assistance information from the NG-RAN and the UE 104 via the AMF 161 to calculate the location of the UE 104. The NG-RAN may utilize one or more positioning methods to determine the location of the UE 104. Positioning the UE 104 may involve signal measurements, position estimation, and optional speed calculation 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 measured signals may be based on a Satellite Positioning System (SPS) 170 (e.g., a Global Navigation Satellite System (GNSS), Global Positioning System (GPS), Non-Terrestrial Network (NTN), or one or more of other satellite positioning / locationing systems), LTE signals, Wireless Local Area Network (WLAN) signals, Bluetooth signals, a Terrestrial Beacon System (TBS), sensor-based information (e.g., an atmospheric pressure sensor, a motion sensor), an NR Enhanced Cell ID (NR E-CID) method, NR signals (e.g., multi-Round Trip Time (multi-RTT), DL Angle of Departure (DL-AoD), DL Time Difference of Arrival (DL-TDOA), UL Time Difference of Arrival (UL-TDOA), and UL Angle of Arrival (UL-AoA) positioning), and / or one or more of other systems / signals / sensors.

[0060] Examples of the UE 104 include cellular telephones, smart phones, Session Initiation Protocol (SIP) telephones, laptop computers, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet computers, smart devices, wearable devices, vehicles, utility meters, gas pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other device with similar functionality. Some of the UEs in the UE 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, heart monitors, etc.). The UE 104 may also be referred to as a station, mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, cellular phone, user agent, mobile client, client, or some other suitable term. In some scenarios, the term UE may also apply to one or more companion devices, such as in a device constellation. One or more of these devices may access the network jointly and / or individually access the network.

[0061] Refer again to Figure 1, in some aspects, UE 104 may include a mobility enhancement component 198. In some aspects, the mobility enhancement component 198 may be configured to send a UE request for on-demand allocation of mobility measurement resources or mobility reporting resources for the UE; and receive, in response to the UE request, a configuration, allocation, or activation for the mobility measurement resources or mobility reporting resources. In some aspects, the mobility enhancement component 198 may be configured to send mobility measurement information to a network node that triggers or indicates a cell handover, a change in the primary cell in dual connectivity, a TRP handover, or a beam switch; and receive an indication of repeated mobility signaling that indicates a cell handover, a change in the primary cell, a TRP handover, or a beam switch. In some aspects, base station 102 may include a mobility enhancement component 199. In some aspects, the mobility enhancement component 199 may be configured to receive a UE request for on-demand allocation of mobility measurement resources or mobility reporting resources for the UE; and provide, in response to the UE request, a configuration, allocation, or activation for the mobility measurement resources or mobility reporting resources. In some aspects, the mobility enhancement component 199 may be configured to receive a request from a source node for a downlink reference signal configured for L1 or L3 measurements at the UE; and provide, in response to the request, a reference signal configuration for the UE to the source node. In some aspects, the mobility enhancement component 199 may be configured to receive mobility measurement information from the UE that triggers or indicates a cell handover, a change in the primary cell in dual connectivity, a TRP handover, or a beam switch; and provide an indication of repeated mobility signaling that indicates a cell handover, a change in the primary cell, a TRP handover, or a beam switch. Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar domains, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0062] Figure 2A FIG. 200 is an illustration example of a first subframe within a 5G NR frame structure. Figure 2B FIG. 230 is an illustration example of DL channels within a 5G NR subframe. Figure 2C FIG. 250 is an illustration example of a second subframe within a 5G NR frame structure. Figure 2D FIG. 280 is an illustration example of UL channels within a 5G NR subframe. The 5G NR frame structure may be frequency division duplexing (FDD) (wherein for a specific set of subcarriers (carrier system bandwidth), the subframes within the set of subcarriers are dedicated to DL or UL), or may be time division duplexing (TDD) (wherein for a specific set of subcarriers (carrier system bandwidth), the subframes within the set of subcarriers are dedicated to both DL and UL). In Figure 2A 、 Figure 2CIn the provided example, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (with most being DL), where D is DL, U is UL, and F is flexibly usable between DL / UL, and subframe 3 is configured with slot format 1 (where all are UL). Although subframes 3 and 4 are shown as having slot formats 1 and 28 respectively, any particular subframe can be configured with any of the various available slot formats 0 - 61. Slot formats 0 and 1 are all - DL and all - UL respectively. The other slot formats 2 - 61 include a mixture of DL, UL, and flexible symbols. The UE is configured with the slot format by the received Slot Format Indicator (SFI) (configured dynamically via Downlink Control Information (DCI) or semi - statically / statically via Radio Resource Control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure as TDD.

[0063] Figures 2A to 2D The frame structure is illustrated, and aspects of the present disclosure can be applicable to other wireless communication technologies that may have different frame structures and / or different channels. One frame (10 ms) can be divided into 10 equal - sized subframes (1 ms). Each subframe can include one or more slots. A subframe can also include mini - slots, which can include 7, 4, or 2 symbols. Each slot can include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended. For normal CP, each slot can include 14 symbols, and for extended CP, each slot can include 12 symbols. The symbols on the DL can be Cyclic Prefix 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 - constrained scenarios; limited to single - stream transmission). The number of slots within a subframe is based on the CP and the parameter set. The parameter set defines the sub - carrier spacing (SCS) (see Table 1). The symbol length / duration can be scaled with 1 / SCS.

[0064]

[0065] Table 1: Parameter Set, SCS, and CP

[0066] For normal CP (14 symbols / slot), the different parameter sets μ0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe respectively. For extended CP, parameter set 2 allows 4 slots per subframe. Thus, for normal CP and parameter set μ, there are 14 symbols / slot and 2 μ slots / subframe. The sub - carrier spacing can be equal to 2 μ*15 kHz, where μ is a parameter set from 0 to 4. Thus, the subcarrier spacing for parameter set μ = 0 is 15 kHz, and the subcarrier spacing for parameter set μ = 4 is 240 kHz. The symbol length / duration is negatively correlated with the subcarrier spacing. Figures 2A to 2D An example of parameter set μ = 2 with normal CP having 14 symbols per time slot and 4 time slots per subframe is provided. The time slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within the frame set, there may be one or more different bandwidth parts (BWPs) that are frequency division multiplexed (see Figure 2B ). Each BWP may have a specific parameter set and CP (normal or extended).

[0067] A resource grid can be used to represent the frame structure. Each time slot includes a resource block (RB) (also referred to as a physical RB (PRB)) that extends over 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.

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

[0069] Figure 2BExamples of various DL channels within a subframe of a frame are illustrated. 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 six Resource Element groups (REGs), and each REG includes 12 consecutive Resource Elements (REs) in the OFDM symbols of an RB. The PDCCH within a BWP can be referred to as a Control Resource Set (CORESET). The UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., common search space, UE-specific search space) during PDCCH monitoring occasions on the CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs can be located at higher and / or lower frequencies on the channel bandwidth. The Primary Synchronization Signal (PSS) can be in symbol 2 of a specific subframe of the frame. The PSS is used by the UE 104 to determine subframe / symbol timing and the physical layer identity. The Secondary Synchronization Signal (SSS) can be in symbol 4 of a specific subframe of the frame. The SSS is used by the UE to determine the physical layer cell identity group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine the Physical Cell Identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS. The Physical Broadcast Channel (PBCH) carrying the Master Information Block (MIB) can be logically grouped with the PSS and SSS to form a Synchronization Signal (SS) / PBCH block (also referred to as an SS block (SSB)). The MIB provides the number of RBs in the system bandwidth and the system frame number. The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information not sent via the PBCH (such as System Information Blocks (SIBs)) and paging messages.

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

[0071] Figure 2DExamples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located at the position indicated in one configuration. The PUCCH carries uplink control information (UCI), such as a scheduling request, a channel quality indicator (CQI), a precoding matrix indicator (PMI), a rank indicator (RI), and a hybrid automatic repeat request (HARQ) acknowledgment (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUSCH carries data and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

[0072] Figure 3 Is a block diagram of a base station 310 in an access network communicating with a UE 350. In the DL, Internet Protocol (IP) packets may be provided to a controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a media access control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with the broadcast of system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with the transfer of upper layer packet data units (PDUs), error correction via ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and re-ordering of RLC data PDUs; and MAC layer functionality associated with the mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel prioritization.

[0073] The transmit (TX) processor 316 and the receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1, which includes the physical (PHY) layer, may include error detection on the transport channel, forward error correction (FEC) encoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 handles the mapping to signal constellations based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase phase shift keying (M-PSK), M-order quadrature amplitude modulation (M-QAM)). The encoded and modulated symbols are then split into parallel streams. Subsequently, each stream may be mapped to OFDM subcarriers, multiplexed with reference signals (e.g., pilots) 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 stream of time-domain OFDM symbols. The OFDM stream is space precoded to generate multiple space streams. Channel estimates from the channel estimator 374 may be used to determine the encoding and modulation schemes, as well as for space processing. The channel estimates may be derived from reference signals transmitted by the UE 350 and / or channel state feedback. Each space stream is then provided to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx may modulate a radio frequency (RF) carrier using the corresponding space stream for transmission.

[0074] At the UE 350, each receiver 354Rx receives signals via its corresponding antenna 352. Each receiver 354Rx recovers the information modulated onto the RF carrier and provides the information to the receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions. The RX processor 356 may perform space processing on the information to recover any space streams destined for the UE 350. If multiple space streams are destined for the UE 350, they may be combined by the RX processor 356 into a single OFDM symbol stream. The RX processor 356 then uses a fast Fourier transform (FFT) to convert the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols and reference signals on each subcarrier are recovered and demodulated by determining the most likely signal constellation points transmitted by the base station 310. These soft decisions may be based on the channel estimates computed by the 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. The data and control signals are then provided to the controller / processor 359, which implements layer 3 and layer 2 functionality.

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

[0076] Similar to the functionality described in connection with DL transmissions performed by the base station 310, the 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 the transfer of upper layer PDUs, error correction via ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and re-ordering of RLC data PDUs; and MAC layer functionality associated with the mapping between the logical channel and the transport channel, 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.

[0077] Channel estimates derived by the channel estimator 358 based on reference signals or feedback transmitted by the base station 310 may be used by the TX processor 368 to select appropriate decoding and modulation schemes and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via a separate transmitter 354Tx. Each transmitter 354Tx modulates an RF carrier with the corresponding spatial stream for transmission.

[0078] UL transmissions are processed at the base station 310 in a manner similar to that described in connection with the receiver functionality at the UE 350. Each receiver 318Rx receives signals via its corresponding antenna 320. Each receiver 318Rx recovers the information modulated onto the RF carrier and provides this information to the RX processor 370.

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

[0080] At least one of TX processor 368, RX processor 356, and controller / processor 359 may be configured to perform aspects related to Figure 1 mobility enhancement component 198.

[0081] At least one of TX processor 316, RX processor 370, and controller / processor 375 may be configured to perform aspects related to Figure 1 mobility enhancement component 199.

[0082] A wireless communication network, such as a 5G NR network, may be designed to include UE mobility. The UE may receive commands, RRC configurations, or RRC reconfigurations for mobility operations from the network. For example, the UE may make measurements related to a source node and a target node and provide such measurements to the source node in a report, which may in turn initiate or trigger cell-level mobility, TRP-level mobility, or beam-level mobility. In some aspects, by way of example, mobility may include a handover (HO) operation from a source node to a target node. In some cases, an HO failure may occur when communication between the UE and the source node is not completed. Complicating the issue, the UE may be configured to perform a BWP switch from operating in an active DL BWP on the source node to the default DL BWP. In some aspects, the BWP switch may be triggered by the expiration of an inactivity timer or based on the expiration of an inactivity timer. The default DL BWP may provide power savings for the UE, and the UE may transition to the default DL BWP after an inactive period to save power. In such a configuration, an HO command from the source node may be sent by the network in the active DL BWP while the UE has switched to the default DL BWP. The network-side operations for HO may include multiple processing steps and may take some time to complete. In such cases, the UE may completely miss the HO command and the opportunity for a network-initiated HO.

[0083] In other words, the latency in the network - side response for mobility operations can be problematic in terms of mobility and power saving. For example, in network - initiated mobility procedures such as handover (HO) and inter - node (e.g., cell, transceiver point (TRP), etc.) beam switching, due to multiple processing steps and signaling exchanges sequentially performed by the source node and the target node, after transmitting a measurement report triggering re - configuration to the source node, the user equipment (UE) may take time to receive re - configuration signaling (e.g., "RRCReconfiguration") via radio resource control (RRC). For example, the source node can process the UE's measurement report for mobility, transmit a request for HO / beam switching to the target node based on the results of the measurement report, receive an acknowledgment (ACK) of the request for HO / beam switching from the target node, and transmit re - configuration signaling to the UE via an RRC (e.g., "RRCReconfiguration") message. Similarly, the target node can receive a request for HO / beam switching from the source node, perform admission control and provide a new RRC configuration as part of the acknowledgment of the request for HO / beam switching, and send an acknowledgment to the source node. Regarding the increased latency / power / signaling overhead that may be caused by bandwidth part (BWP) switching, if the UE is configured with a BWP inactivity timer for power saving on the source node and the BWP inactivity timer expires before the UE receives a command for HO / beam switching (e.g., via downlink control information (DCI) or RRC ("RRCReconfiguration")), the UE may fallback to the default downlink BWP and miss the opportunity for network - initiated mobility. Additionally, since the link quality is unlikely to improve in the default downlink BWP, the UE may be forced to attempt RRC reconstruction or initiate cell selection / reselection after releasing its RRC connection with the source node due to RRC reconstruction failure. Furthermore, physical random access channel (PRACH) resources may not be configured in the uplink BWP associated with the UE's default downlink BWP or active downlink BWP, which can force the UE to switch the BWP again for the random access channel (RACH).

[0084] Some mobility enhancement schemes (e.g., dual active protocol stack (DAPS) and conditional handover (CHO)) can improve robustness and reduce the latency of mobility in some scenarios, but they can have higher implementation complexity for the network / UE (dual connectivity to the source and target nodes), or can consume more network resources (e.g., early data forwarding and RACH resource reservation on multiple target nodes). There may also be additional challenges for mobility in wireless communications such as 5G / 6G. For example, with network - side densification and new spectrum being opened for 5G / 6G, as well as extended support for new devices with higher speeds, frequent cell - level / beam - level mobility may be more frequent for the UE and / or the network.

[0085] Figure 4 FIG. 400 is a diagram illustrating exemplary UE mobility configurations in various aspects. In various aspects, FIG. 400 can be used for cell-level and / or beam-level mobility of UE 402 in an RRC connected state (e.g., “RRC_CONNECTED”) with a source node 404 (e.g., a source base station or a part thereof). As shown, cell-level / beam-level mobility of UE 402 can be performed with respect to a target node 406 (e.g., a target base station or a part thereof). In some aspects, the source node can be a source base station and the target node can be a target base station. In other aspects, the source node can be a source TRP and the target node can be a target TRP. The source and target TRPs can be used for the same base station or can be used for different base stations. In some aspects, the first node can be a first component of a base station and the second node can be a second component of the same or a different base station.

[0086] Network-initiated mobility can be applied to a UE in an RRC connected state and can be classified as cell-level and beam-level operations. Network-initiated cell-level / beam-level mobility can be in response to UE 402 transmitting a measurement report 408 to the source node 404. UE 402 can measure the source node 404 and / or the target node 406, for example, via a measurement reference signal on one or more beams from the source node and / or the target node, and provide the measurement report to the source node 404. If the source node 404 determines that the measurement report indicates that a mobility operation should be performed with the target node 406 (e.g., in response to the measurement at the source node being below a threshold or the measurement at the target node being better than the measurement at the source node), the source node 404 can provide a HO request 410 to the target node 406. The target node 406 can then be configured to perform admission control 412 associated with UE 402. Upon completion of the admission control 412, the target node 406 can provide a HO request confirmation (ACK) 414 to the source node 404, which in turn can provide a HO command 416 to UE 402. UE 402 can be configured to switch to the indicated cell / beam of the target node 406 at 418, and as part of the mobility operation, UE 402 can perform a RACH procedure 420 using the target node 406. When the RACH procedure 420 is completed, UE 402 can then provide an indication of RRC reconfiguration complete for the mobility operation switch at 422.

[0087] However, as mentioned above and as Figure 4As illustrated in the diagram 400, HO failure may occur when the measurement report 408 of the UE does not reach the source cell, for example due to a communication failure. In this example, the network is unaware that the conditions triggering a node change have occurred and does not initiate a handover. In other respects, HO failure may occur when the HO command 416 of the source cell does not reach the UE, for example due to a communication failure, because the UE is unaware of the HO.

[0088] In some aspects, the UE may be configured for conditional handover (CHO), and when the measurements at the UE meet the configured conditions for triggering a CHO, the UE may know to initiate a CHO. Figure 5 is a diagram 500 illustrating an example communication flow for conditional handover. As Figure 5 shown, the example CHO process may include three phases: handover preparation 519, handover execution 520, and handover completion 530. In handover preparation 519, the source node 504 and candidate target nodes (506, 508) may receive mobility control information provided by the AMF at 510, and the UE 502 and the source node 504 may communicate at 511 for measurement control and reporting. For example, at 512, a CHO decision may be made by the source node 504. After the CHO decision is made at 512, the source node 504 may transmit a handover request to the candidate target nodes (506, 508) at 513, and the candidate target nodes (506, 508) may perform admission control at 514 and respond to the source node 504 with a handover request confirmation at 515. The source node 504 may then transmit a list of candidate target nodes (e.g., 506, 508) and CHO trigger conditions to the UE 502 at 516 via RRC configuration (e.g., via an "RRCReconfiguration" message), and the UE 502 may respond at 517 using, for example, an "RRCReconfigurationComplete" message.

[0089] In handover execution 520, the UE 502 may measure the candidate nodes (e.g., 506, 508) and evaluate the CHO trigger conditions at 522. When the CHO trigger conditions are met for one of the candidate nodes (e.g., 506, 508), the UE 502 may detach from the old node (i.e., the source node 506) and connect to the candidate target node that meets the CHO trigger conditions (e.g., the target node 506) at 524.

[0090] In handover completion 530, a target node newly connected to the UE (e.g., target node 506) may transmit a handover success confirmation to the source node 504 at 518a, and the source node 504 may convey the source node state to the newly connected target node (e.g., 506) at 518b. The same principle of CHO can be reused for CPC in dual connectivity (DC). In some aspects, the handover may be cancelled, as shown at 518c.

[0091] The UE may communicate with the network based on a BWP that spans a portion of the total channel bandwidth configured for the cell. The UE may be configured with multiple BWPs, each BWP spanning a contiguous set of frequency resources, e.g., a set of PRBs. A BWP may be activated for the UE from the set of configured BWPs. It may not be desirable for the UE to receive PDSCH, PDCCH, CSI-RS, TRS, etc. outside the active DL BWP. Outside the active UL BWP, the UE may not transmit PUSCH or PUCCH. The UE may receive an indication from the network to switch from a first active BWP to a second active BWP, the first active BWP and the second active BWP being from the set of configured BWPs. In some aspects, the UE may switch from the active DL BWP to the default DL BWP based on an inactive period. The default DL BWP may provide power savings for the UE, and the UE may switch to the default DL BWP in response to the expiration of an inactive timer to save power. Figure 6 FIG. 600 is a diagram illustrating an example BWP handover in accordance with various aspects of the present disclosure. FIG. 600 is illustrated with respect to a time slot in which a smaller / narrower DL BWP or a larger / wider DL BWP may be configured, where the narrower DL BWP may be configured as the default DL BWP for power savings.

[0092] As shown in FIG. 600, control channel (CCH) information may indicate whether the next time slot has a grant. For example, in the case of a configured narrow DL BWP, time slot n includes a CCH without a grant, and thus, there is no data in time slot n+1 (e.g., which may be beneficial for micro-dormancy). However, the CCH in time slot n+1 includes a grant for time slot n+2 in the narrow DL BWP (ID=1) for a small amount of data that may be received by the UE in a single time slot with the narrow DL BWP. Thus, time slot n+2 includes a grant and a small amount of data, and no BWP handover is performed.

[0093] When operating in the active DL BWP of the source cell, the default DL BWP and timer values can be provided to the UE, for example, via the "bwp-inactivityTimer". The UE can be configured to decrement the timer (e.g., at the end of a subframe for FR1, or at the end of a half-subframe for FR2), and if the UE does not receive a DCI indicating a DL assignment / UL grant in the configured DL assignment on the active BWP or a MAC PDU for a unicast / multicast broadcast signal (MBS) (e.g., during the interval of a subframe for FR1 or a half-subframe for FR2).

[0094] At time slot m+1, a large amount of data arrives in the queue, and the corresponding CCH indicates a DL grant for the large data, which will cause the BWP to switch to the wide BWP ID=2 for the next time slot: m+2. At time slot m+2, the large data is received by the UE via the wide BWP (although not drawn to scale, Figure 6 it is exemplified that the large data may not be carried within the narrow BWP and thus not carried in the handover. At a later time slot x, it can be assumed that no new data is received via the wide BWP and the timer has expired, such that the UE is configured to switch from the wider active DL BWP (ID=2) to the narrower default DL BWP (ID=1) for power and signaling efficiency. That is, the UE can be configured to switch to the default DL BWP (e.g., the narrower BWP) of the source cell when the BWP timer expires after a certain period of scheduling inactivity. If the UE receives a DL grant, the UE can switch to a wider active DL BWP to receive DL data according to the DL grant. The UE can remain on the active DL BWP until the inactivity timer expires again, at which time the UE can switch back to the narrower default DL BWP.

[0095] A time gap can be provided at the end of the time slot to accommodate the uplink control block (ULCB) for TDD, which is not exemplified for clarity and conciseness.

[0096] As discussed above, if the UE switches to the default DL BWP based on inactivity and during the time period after the UE transmits a measurement report (such as shown at 415 in Figure 4 ), the UE may miss the HO / beam switching command generated from the measurement report. The UE may miss the opportunity for network-initiated mobility. If the link quality does not improve in the default DL BWP, as part of the RRC reconstruction failure, the UE can attempt RRC reconstruction or initiate cell selection / reselection after releasing the RRC connection with the source node. The PRACH resource may not be configured in the UL BWP associated with the default DL BWP or the active DL BWP, and the UE can switch the BWP to perform RACH.

[0097] The UE can measure one or more beams from the UE to derive beam quality or cell quality. In RRC connected mode, the UE can measure one or more beams of a cell and can average the measurement results (e.g., power values) to derive cell quality. In some aspects, the UE can be configured to consider a subset of the detected beams.

[0098] Figure 7 FIG. 700 is a diagram illustrating an example of a measurement model. As Figure 7 shown, the measurements that can be performed by the UE can include L1 measurements (filtering) and L3 measurements (filtering). The L1 measurements can be, for example, measurements for reference signal received power (RSRP) and can be specific to the UE implementation. The L3 measurements can be based on the L1 measurements and are performed over a longer interval than the L1 measurements. Thus, the L3 measurements can provide a more stable and longer-term beam metric than the L1 measurements and are therefore more suitable for applications that require long-term measurements, such as handover or beam-level mobility. The measurements (filtering) can be performed at the physical layer to derive beam quality and then at the RRC layer to derive cell quality from multiple beams. For example, as Figure 7 shown, in branch A 710 of the measurement flow, L3 measurements (filtering) are performed for cell-level quality (i.e., based on the aggregation of multiple beams), and the measurement results can be useful in cell-level mobility (such as handover). In branch B 720 of the measurement flow, the L3 measurements (filtering) are beam-specific (i.e., performed on individual beams), and the measurement results can be used for beam-level mobility. The cell quality from beam measurements can be derived in the same way for serving and non-serving cells, and the UE can be configured to report the X best beams in a measurement report.

[0099] CHO and CPC can improve the robustness and reliability of HO and secondary cell group (SCG) changes in DC because the target cell configuration for CHO / CPC can include multiple candidates selected by the source node and the CHO / CPC condition evaluation and execution can be performed by the UE. However, it may be necessary to enable early data forwarding and resource assignment (RA) resource reservation on multiple cells before CHO / CPC execution, which can increase system / signaling overhead and reduce the network's spectral / energy efficiency. Additionally, for network-initiated HO and CHO / CPC, the UE takes time to receive an RRC message (e.g., RRCReconfiguration message) after transmitting a measurement report. Thus, BWP switching due to the expiration of the BWP inactivity timer in the source node may exacerbate the latency and power issues of HO.

[0100] The present disclosure provides methods and apparatuses for configuring mobility timers and signaling enhancements for a network to assist UE measurements and mobility. The disclosed methods and apparatuses can mitigate potential increases in latency / overhead / power caused by undesired BWP switching during HO (including network-initiated HO, CHO, CPC, etc.).

[0101] One aspect of the present disclosure relates to network assistance for on-demand reference signal (RS) transmission / activation. Figure 8 FIG. 800 is a call flow diagram illustrating network assistance for on-demand RS transmission / activation in accordance with various aspects of the present disclosure. As Figure 8 shown, in addition to a set of measurement resources configured for UE 802 via dedicated RRC, the network may additionally support on-demand transmission / activation of aperiodic / periodic DL RSs configured for L1 / L2 / L3 measurements at the source node and the target node. Examples of DL RSs applicable for on-demand transmission / activation may include, but are not limited to: non-cell-defined synchronization signal blocks (NCD-SSBs), positioning reference signals (PRSs), channel state information reference signals (CSI-RSs), or tracking reference signals (TRSs). A request from the UE may be conveyed to the source node via a UL RS / sequence (e.g., PRACH, SRS) or a UL control / data channel (PUCCH, PUSCH). The response from the network (from the source node and the target node) may be delivered to the UE by the source node using DCI, RRC, medium access control - control element (MAC-CE), or a combination thereof.

[0102] For example, as Figure 8As shown, the UE 802 may transmit a request for DL RS configured for L1 / L2 / L3 measurements of the source / target node at 810. After receiving the request, the source node 804 may forward the request for DL RS configured for L1 / L2 / L3 measurements of the target node to one or more target nodes (e.g., target node candidate #1 806 and target node candidate #2 808) at 812. After receiving the request from the source node 804, each of the one or more target nodes may perform a scheduling process at 813 to check its ability to grant the UE or transmit the requested RS. The target node will transmit a response to the RS configuration to the source node 804 at 814, and the response may include the target node's decision to grant the UE or transmit the requested RS. When receiving the response from the target node, if the UE's request is granted by the source / target node, the source node 804 may transmit the configuration / reconfiguration of the L1 / L2 / L3 measurements of the source / target node at 816. The source node 806 and one or more target nodes (e.g., target node candidate #1 806 and target node candidate #2 808) may each transmit on-demand transmission / activation of DL RS configured for L1 / L2 / L3 measurements to the UE 802 at, for example, 818, 820, 822. In some aspects, the on-demand transmission / activation of DL RS may be used by multiple UEs belonging to the same UE group and connected to the same source node (e.g., multiple UEs connected to the source node 804). The UE 802 may send a measurement report based on the on-demand RS of the source / target node to the source node 804 at 824. At 826, based on the measurement report, the source node 804 may initiate a HO, or the UE 802 may initiate a CHO / CPC.

[0103] Another aspect of the present disclosure relates to network-assisted timer adaptation for BWP switching and mobility. Figure 9 is a call flow diagram 900 illustrating network-assisted timer adaptation for BWP exchange and mobility according to various aspects of the present disclosure. As Figure 9As shown, the source node 904 may transmit an inquiry about the UE capabilities to the UE 902 at 906. The capabilities of the UE may include capabilities associated with measurements, power saving, and mobility enhancements, and the UE 902 may report the UE capabilities to the source node 904 at 908. The source node 904 may also send the RRC configurations of the measurement report (MR), the BWP inactivity timer, and the mobility timer to the UE 902 at 910. At 912, the UE 902 may transmit a scheduling request to the source node 904 for reporting the status of the UE's measurements and timers. At 914, the source node 904 may transmit a response to the UE's scheduling request to the UE 902. The response may include resources allocated to the UE 902 to report measurements, the status of the ongoing BWP inactivity timer, or the conditions for triggering the UE's mobility timer. At 916, the UE 902 may send a measurement report for the source / target node to the source node 904. At 918, the UE 902 may send a status report for the BWP inactivity timer or the mobility timer to the source node 904. The measurement report for the source / target node and the status report for the BWP inactivity timer or the mobility timer may be multiplexed on a single UL channel or sent separately on multiple UL channels. After receiving the UE's measurement report and status report, the source node 904 may send an indication to the UE 902 to reset the BWP inactivity timer at 920. For example, the source node 904 may provide a new expiration time after restarting the timer, or provide a new configuration for the mobility timer (e.g., start / restart, configuration / reconfiguration of the expiration time). At 922, the source node 904 may further send supplementary information for the UE's measurements and mobility to the UE 902. For example, the source node 904 may provide on-demand RS transmission / activation, updates on the number / status of the target nodes / system load. At 924, the UE 902 may send an acknowledgement (ACK) of the indication / activation / reconfiguration from the source node to the source node 804. At 926, based on the ACK from the UE 902, the source node 904 may send / resend an HO command (PDCCH command, MAC-CE, or RRC) or an RRC reconfiguration message before the expiration of the time window determined by the UE's mobility timer and / or BWP inactivity timer.

[0104] Another aspect of the present disclosure relates to the repetition of mobility signaling by a network. In the repetition of mobility signaling, based on the UE's report of measurement and timer status, the network can respond with an indication sent by, for example, DCI, RRC, MAC-CE, or sequence / RS, which can signal that an HO command or RRC reconfiguration message will be repeated. In some aspects, the repetition can occur in multiple BWPs of the source node. For example, the source node can send an HO command or RRC reconfiguration in both the active BWP and the default BWP of the UE (or UE group, if group HO / CHO / CPC applies) of the source node. In some aspects, the repetition can occur across multiple nodes within a time window, and the time window can start from a reference time associated with the UE's reception of the network indication. For example, the source node and the target node can jointly send an HO command or RRC reconfiguration for the UE (or UE group, if group HO / CHO / CPC applies) in a single-frequency network (SFN) scenario. In some aspects, the mobility signaling can be multicast to a group of UEs connected to the source node.

[0105] Figure 10 FIG. 1000 is a call flow diagram illustrating the repetition of mobility signaling by a network according to various aspects of the present disclosure. As Figure 10 shown, at 1006, the source node 1004 can send, for example via RRC configuration, configurations for measurement reporting and various timers to the UE 1002. The various timers can include, for example, a BWP inactivity timer or a mobility timer. At 1008, the source node 1004 can receive mobility measurement information from the UE 1002. The mobility measurement information can indicate a handover or a beam switch. At 1010, the source node 1006 can provide an indication of the repeated mobility signaling, which triggers or indicates a cell handover, a change of the primary cell in dual connectivity, a TRP switch, or a beam switch. At 1012, the source node can provide the repeated signaling.

[0106] Figure 11 FIG. 1100 is a flow diagram illustrating a method of wireless communication at a source node according to various aspects of the present disclosure. In various aspects, the method can be performed by the source node in the context of the target node. In some aspects, the source node can be a source base station and the target node can be a target base station. In other aspects, the source node can be a source TRP and the target node can be a target TRP. The source TRP and the target TRP can be used for the same base station or can be used for different base stations. In some aspects, the source node can be a first component of a base station and the target node can be a second component of the same base station or a different base station. The base station can be Figure 1 a base station or a component of a base station in an access network, or a core network component (e.g., base stations 102, 310; or Figure 18in the network entity 1802 in the specific hardware implementation). This method improves the flexibility and reliability in processing the UE's requests for mobility measurement sources or mobility reporting resources. Consequently, the efficiency of wireless communication is enhanced.

[0107] As Figure 11 shown, at 1102, the source node may receive a UE request for on-demand allocation of mobility measurement resources or mobility reporting resources for the UE. The source node may receive the UE request from the UE. The UE may be Figure 18 the UE 104, 350, 802, 902, 1002 in the specific hardware implementation or the device 1804. Figure 8 , Figure 9 and Figure 10 illustrate various aspects of the steps in combination with the flowchart 1100. For example, referring to Figure 8 , the source node 804 may receive at 810 a UE request for on-demand allocation of mobility measurement resources or mobility reporting resources for the UE 802 (e.g., a request for DL RS configured for L1 / L2 / L3 measurements). In some aspects, the on-demand allocation of mobility measurement resources or mobility reporting resources may be used by multiple UEs belonging to the same UE group and connected to the same source node (e.g., multiple UEs connected to the source node 804). In some aspects, 1102 may be performed by the mobility enhancement component 199.

[0108] At 1104, the source node may provide a configuration, allocation, or activation for the mobility measurement resources or mobility reporting resources in response to the UE request. For example, referring to Figure 8 , the source node 804 may provide at 816 a configuration, allocation, or activation for the mobility measurement resources or mobility reporting resources in response to the UE request (e.g., configuration / reconfiguration of L1 / L2 / L3 measurements of the source / target node). In some aspects, 1104 may be performed by the mobility enhancement component 199.

[0109] Figure 12 is a flowchart 1200 illustrating a method for wireless communication at a source node according to various aspects of the present disclosure. In various aspects, this method may be performed by the source node in the context of the target node. In some aspects, the source node may be a source base station, and the target node may be a target base station. In other aspects, the source node may be a source TRP, and the target node may be a target TRP. The source TRP and the target TRP may be used for the same base station or may be used for different base stations. In some aspects, the source node may be a first component of a base station, and the target node may be a second component of the same base station or a different base station. The base station may be Figure 1 a base station or a component of a base station in the access network, or a core network component (e.g., base station 102, 310; or Figure 18in the network entity 1802 in the specific hardware implementation). This method improves the flexibility and reliability in processing the UE's requests for mobility measurement sources or mobility reporting resources. Therefore, the efficiency of wireless communication is improved.

[0110] As Figure 12 shown, at 1202, the source node may receive a UE request for on-demand allocation of mobility measurement resources or mobility reporting resources for the UE. The source node may receive the UE request from the UE. The UE may be Figure 18 the UE 104, 350, 802, 902, 1002 in the specific hardware implementation or the device 1804. Figure 8 , Figure 9 and Figure 10 illustrate various aspects of the steps in combination with the flowchart 1200. For example, refer to Figure 8 , the source node 804 may receive at 810 a UE request for on-demand allocation of mobility measurement resources or mobility reporting resources for the UE 802 (e.g., a request for a DL RS configured for L1 / L2 / L3 measurements). In some aspects, the on-demand allocation of mobility measurement resources or mobility reporting resources may be used by multiple UEs belonging to the same UE group and connected to the same source node (e.g., multiple UEs connected to the source node 804). In some aspects, 1202 may be performed by the mobility enhancement component 199.

[0111] At 1208, the source node may provide a configuration, allocation, or activation for the mobility measurement resources or mobility reporting resources in response to the UE request. For example, refer to Figure 8 , the source node 804 may provide a configuration, allocation, or activation for the mobility measurement resources or mobility reporting resources at 816 in response to the UE request (e.g., configuration / reconfiguration of L1 / L2 / L3 measurements of the source / target node). In some aspects, 1208 may be performed by the mobility enhancement component 199.

[0112] In some aspects, the request may be for a downlink reference signal for L1 measurement, L2 measurement, or L3 measurement of the source node and at least one target node. For example, refer to Figure 8 , the request may be for a DL RS for L1 measurement, L2 measurement, or L3 measurement of the source node 804 and at least one target node (806, 808).

[0113] In some aspects, the source node may send a downlink reference signal at 1210 in response to the UE request, and receive a measurement report at 1212 using at least a portion of the resources allocated for mobility reporting in response to the UE request after measuring the downlink reference signal. The measurement report may include measurement information for one or more of the source node or at least one target node. For example, refer toFigure 8 At Figure 8 , the source node 804 may send a DL RS in response to a UE request at 818, and receive a measurement report (measurement report based on on-demand RS of the source / target node) at 824 using at least a portion of the resources allocated for mobility reporting in response to the UE request after measuring the downlink reference signal. In some aspects, 1210 and 1212 may be performed by the mobility enhancement component 199.

[0114] In some aspects, the downlink reference signal may be aperiodic or periodic. The downlink reference signal may include at least one of the following: NCD-SSB, PRS, CSI-RS, or TRS. For example, see Figure 8 At Figure 8 , when the source node 804 sends a DL RS to the UE 802 at 818, the DL RS may be aperiodic or periodic, and may include at least one of the following: NCD-SSB, PRS, CSI-RS, or TRS.

[0115] In some aspects, the UE request may be indicated in at least one of the following: uplink reference signal, uplink sequence, uplink control channel, or uplink data channel. For example, see Figure 8 At Figure 8 , when the UE 802 transmits a request for a DL RS to the source node 804 at 810, the request may be indicated in at least one of the following: uplink reference signal, uplink sequence, uplink control channel, or uplink data channel.

[0116] In some aspects, the configuration, allocation, or activation in response to the UE request may be included in DCI, RRC message, MAC-CE, or a combination thereof. For example, see Figure 8 At Figure 8 , when the source node 804 sends a configuration / reconfiguration of L1 / L2 / L3 measurements at 816, the configuration / reconfiguration may be included in DCI, RRC message, MAC-CE, or a combination thereof.

[0117] In some aspects, the source node may configure one or more configurations for L1 measurements, L2 measurements, or L3 measurements. The source node may activate one of the one or more configurations in response to the UE request. For example, see Figure 8 At Figure 8 , the source node 804 may configure one or more configurations for L1 measurements, L2 measurements, or L3 measurements at 816. The source node 804 may activate one of the one or more configurations at 816 in response to the UE request received by the source node 804 at 810.

[0118] In some aspects, a source node may provide, at 1204, a request for target node resources for L1 measurements, L2 measurements, or L3 measurements to be performed by a UE to at least one target node. At 1206, the source node may also receive a reference signal configuration from at least one target node. The source node may provide a configuration in response to a UE request, and the configuration may include a reference signal configuration from at least one target node. For example, referring to Figure 8 , source node 804 may provide, at 812, a request for target node resources for L1 measurements, L2 measurements, or L3 measurements to be performed by UE 802 to at least one target node (806, 808). Source node 804 may also receive a reference signal configuration from at least one target node (806, 808) at 814. Source node 804 may provide a configuration at 816 in response to a UE request (received at 810), and the configuration may include a reference signal configuration from at least one target node (806, 808). In some aspects, 1204 and 1206 may be performed by a mobility enhancement component 199.

[0119] In some aspects, the UE request may be for mobility reporting resources to report one or more of the following: a mobility measurement report, the status of a BWP inactivity timer, the status of a mobility timer, or a condition for triggering or resetting a mobility timer or a BWP inactivity timer, and the source node may receive at least one of a mobility measurement report, the status of a BWP inactivity timer, the status of a mobility timer, or a condition for triggering or resetting a mobility timer or a BWP inactivity timer. For example, referring to Figure 8 , the UE request (received by source node 804 at 810) may be for mobility reporting resources to report one or more of the following: a mobility measurement report, the status of a BWP inactivity timer, the status of a mobility timer, or a condition for triggering or resetting a mobility timer or a BWP inactivity timer. Source node 804 may receive at least one of a mobility measurement report, the inactive status of a BWP timer, the status of a mobility timer, or a condition for triggering or resetting a mobility timer or a BWP inactivity timer (the measurement report received at 824). Referring to Figure 9 , source node 904 may receive at least one of a mobility measurement report (the measurement report at 916), the status of a BWP inactivity timer (the status report of a BWP inactivity timer or a mobility timer at 918), the status of a mobility timer, or a condition for triggering or resetting a mobility timer or a BWP inactivity timer.

[0120] In some aspects, the source node may provide an indication for the UE to reset a BWP inactivity timer or a mobility timer at 1214. For example, referring to Figure 9, the source node 904 may provide an indication at 920 to reset the UE's BWP inactivity timer or mobility timer. In some aspects, 1214 may be performed by the mobility enhancement component 199.

[0121] In some aspects, the source node may provide additional information for UE mobility measurement or mobility at 1216. The additional information may include at least one of on-demand reference signal transmission or on-demand reference signal activation, or updated information for at least one target node. For example, see Figure 9 , the source node 904 may provide additional information for UE mobility measurement or mobility (supplementary information for UE measurement and mobility) at 922. The additional information may include at least one of on-demand reference signal transmission or on-demand reference signal activation, or updated information for at least one target node. In some aspects, 1216 may be performed by the mobility enhancement component 199.

[0122] Figure 13 is a flowchart 1300 illustrating a method of wireless communication at a target node in accordance with various aspects of the present disclosure. In various aspects, the method may be performed by the target node in the context of the source node. In some aspects, the source node may be a source base station and the target node may be a target base station. In other aspects, the source node may be a source TRP and the target node may be a target TRP. The source TRP and the target TRP may be used for the same base station or may be used for different base stations. In some aspects, the source node may be a first component of a base station and the target node may be a second component of the same or a different base station. The base station may be Figure 1 a base station or a component of a base station in an access network, or a core network component (e.g., base stations 102, 310; or Figure 18 network entity 1802 in a hardware implementation of

[0123] As Figure 13 shown, at 1302, the target node may receive a request from the source node for a downlink reference signal configured for L1 or L3 measurement at the UE. The UE may be Figure 18 UE 104, 350, 802, 902, 1002 or device 1804 in a hardware implementation of Figure 8 , Figure 9 and Figure 10 illustrate various aspects of steps in conjunction with flowchart 1300. For example, see Figure 8, the target node 806 may receive at 812 a request from the source node 804 for DLRS configured for L1 or L3 measurements at the UE 802. In some aspects, 1302 may be performed by the mobility enhancement component 199.

[0124] At 1304, the target node may provide a reference signal configuration for the UE to the source node in response to the request. For example, see Figure 8 , the target node 806 may provide an RS configuration for the UE 802 to the source node 804 at 814 in response to the request (received at 812). In some aspects, 1304 may be performed by the mobility enhancement component 199.

[0125] Figure 14 FIG. 1400 is a flowchart illustrating a method of wireless communication at a network entity in accordance with various aspects of the present disclosure. The method may be performed by a network entity. The network entity may be Figure 1 a base station or a component of a base station in an access network, or a core network component (e.g., base stations 102, 310; source nodes 804, 904, 1004; or Figure 18 the network entity 1802 in a hardware implementation of

[0126] As Figure 14 shown, at 1402, the network entity may receive mobility measurement information from the UE indicating a cell handover, a change in the primary cell in dual connectivity, a TRP handover, or a beam handover. The UE may be Figure 18 the UE 104, 350, 802, 902, 1002 or the device 1804 in a hardware implementation of Figure 8 , Figure 9 and Figure 10 illustrate various aspects of steps in conjunction with flowchart 1400. For example, see Figure 10 , the network entity (source node 904) may receive mobility measurement information from the UE 902 at 908 triggering or indicating a cell handover, a change in the primary cell in dual connectivity, a TRP handover, or a beam handover. In some aspects, 1402 may be performed by the mobility enhancement component 199.

[0127] At 1404, the network entity may provide an indication of duplicate mobility signaling that triggers or indicates a cell handover, a change in the primary cell in dual connectivity, a TRP handover, or a beam handover. For example, see Figure 10, a network entity (source node 904) may provide an indication of duplicate mobility signaling at 910, which triggers or indicates a cell handover, a change in the primary cell in dual connectivity, a TRP handover, or a beam switch. In some aspects, 1404 may be performed by a mobility enhancement component 199.

[0128] In some aspects, the indication of duplicate mobility signaling may be provided based on measurements from the UE or the timer state of the UE. For example, see Figure 10 , when the source node 1004 sends an indication of duplicate mobility signaling to the UE 1002 at 1010, the indication may be provided based on measurements from the UE 1002 or the timer state of the UE 1002.

[0129] In some aspects, the indication of duplicate mobility signaling may be included in at least one of the following: DCI, RRC message, MAC-CE, sequence, or reference signal. For example, see Figure 10 , when the source node 1004 sends an indication of duplicate mobility signaling to the UE 1002 at 1010, the indication of duplicate mobility signaling may be included in at least one of the following: DCI, RRC message, MAC-CE, sequence, or reference signal.

[0130] In some aspects, the duplicate mobility signaling may include commands for cell handover, change in the primary cell in dual connectivity, TRP handover, or beam switch that are repeated in multiple BWPs during a time window. The window may start from a reference time associated with the UE's reception of the mobility signaling. For example, see Figure 10 , when the source node 1004 sends an indication of duplicate mobility signaling to the UE 1002 at 1010, the duplicate mobility signaling may include commands for cell handover, change in the primary cell, TRP handover, or beam switch that are repeated in multiple BWPs during a time window. The window may start from a reference time associated with the UE 1002's reception of the mobility signaling.

[0131] In some aspects, the multiple BWPs may include the active downlink BWP and the default downlink BWP of the source node. For example, the multiple BWPs may include the active downlink BWP and the default downlink BWP of the source node 1004.

[0132] In some aspects, the duplicate mobility signaling may include joint transmission from the source node and the target node in an SFN transmission scheme. For example, see Figure 10 , when the source node 1004 sends an indication of duplicate mobility signaling to the UE 1002 at 1010, the duplicate mobility signaling may include joint transmission from the source node 1004 and the target node in an SFN transmission scheme.

[0133] Figure 15 FIG. 1500 is a flow chart illustrating a method for wireless communication at a UE in accordance with various aspects of the present disclosure. In various aspects, the method may be performed by the UE in the context of a target node and a source node. The UE may be the UE 104, 350, 802, 902, 1002 or the apparatus 1804 in a hardware implementation thereof. In some aspects, the source node may be a source base station and the target node may be a target base station. In other aspects, the source node may be a source TRP and the target node may be a target TRP. The source TRP and the target TRP may be used for the same base station or may be used for different base stations. In some aspects, the source node may be a first component of a base station and the target node may be a second component of the same base station or a different base station. The base station may be a base station or a component of a base station in an access network, or a core network component (e.g., base station 102, 310; or the network entity 1802 in a hardware implementation thereof). The method improves the flexibility and reliability in processing a UE request for a mobility measurement source or a mobility reporting resource. Accordingly, the efficiency of wireless communication is improved. Figure 18 As shown in FIG. 1502, at 1502, the UE may send a UE request for on-demand allocation of a mobility measurement resource or a mobility reporting resource for the UE. The UE may send the UE request to the source node. The source node may be a base station or a component of a base station in an access network, or a core network component (e.g., base station 102, 310; source nodes 804, 904, 1004; or the network entity 1802 in a hardware implementation thereof). Figure 1 FIGS., and illustrate various aspects of steps in conjunction with the flow chart 1500. For example, referring to FIG., the UE 802 may send a UE request for on-demand allocation of a mobility measurement resource or a mobility reporting resource for the UE (e.g., a request for DL RS configured for L1 / L2 / L3 measurements for the source / target node) at 810. In some aspects, 1502 may be performed by the mobility enhancement component 198. Figure 18 At 1504, the UE may receive a configuration, allocation, or activation for the mobility measurement resource or the mobility reporting resource in response to the UE request. For example, referring to FIG.

[0134] As Figure 15 shown, at 1502, the UE may send a UE request for on-demand allocation of a mobility measurement resource or a mobility reporting resource for the UE. The UE may send the UE request to the source node. The source node may be a base station or a component of a base station in an access network, or a core network component (e.g., base station 102, 310; source nodes 804, 904, 1004; or the network entity 1802 in a hardware implementation thereof). Figure 1 The source node may be a base station or a component of a base station in an access network, or a core network component (e.g., base station 102, 310; source nodes 804, 904, 1004; or the network entity 1802 in a hardware implementation thereof). Figure 18 FIGS., and illustrate various aspects of steps in conjunction with the flow chart 1500. For example, referring to FIG., the UE 802 may send a UE request for on-demand allocation of a mobility measurement resource or a mobility reporting resource for the UE (e.g., a request for DL RS configured for L1 / L2 / L3 measurements for the source / target node) at 810. In some aspects, 1502 may be performed by the mobility enhancement component 198. Figure 8 FIGS. Figure 9 and Figure 10 illustrate various aspects of steps in conjunction with the flow chart 1500. For example, referring to FIG. Figure 8 FIG., the UE 802 may send a UE request for on-demand allocation of a mobility measurement resource or a mobility reporting resource for the UE (e.g., a request for DL RS configured for L1 / L2 / L3 measurements for the source / target node) at 810. In some aspects, 1502 may be performed by the mobility enhancement component 198.

[0135] At 1504, the UE may receive a configuration, allocation, or activation for the mobility measurement resource or the mobility reporting resource in response to the UE request. For example, referring to FIG. Figure 8, the UE 802 may receive, at 816, a configuration, allocation, or activation of mobility measurement resources or mobility reporting resources (e.g., configuration / reconfiguration of L1 / L2 / L3 measurements of source / destination nodes) in response to a UE request transmitted by the UE at 810. In some aspects, 1504 may be performed by the mobility enhancement component 198.

[0136] Figure 16 FIG. 1600 is a flowchart illustrating a method of wireless communication at a UE in accordance with various aspects of the present disclosure. In various aspects, the method may be performed by the UE in the context of a target node and a source node. The UE may be Figure 18 the UE 104, 350, 802, 902, 1002 or the apparatus 1804 in a hardware implementation thereof. In some aspects, the source node may be a source base station and the target node may be a target base station. In other aspects, the source node may be a source TRP and the target node may be a target TRP. The source TRP and the target TRP may be used for the same base station or may be used for different base stations. In some aspects, the source node may be a first component of a base station and the target node may be a second component of the same base station or a different base station. The base station may be Figure 1 a base station or a component of a base station in an access network, or a core network component (e.g., base stations 102, 310; or Figure 18 the network entity 1802 in a hardware implementation thereof). The method improves the flexibility and reliability in processing UE requests for mobility measurement sources or mobility reporting resources. Accordingly, the efficiency of wireless communication is improved.

[0137] As Figure 16 illustrated, at 1602, the UE may send a UE request for on-demand allocation of mobility measurement resources or mobility reporting resources for the UE. The UE may send the UE request to the source node. The source node may be Figure 1 a base station or a component of a base station in an access network, or a core network component (e.g., base stations 102, 310; source nodes 804, 904, 1004; or Figure 18 the network entity 1802 in a hardware implementation thereof). Figure 8 , Figure 9 and Figure 10 illustrate various aspects of steps in combination with FIG. 1500. For example, referring to Figure 8 , the UE 802 may send, at 810, a UE request for on-demand allocation of mobility measurement resources or mobility reporting resources for the UE (e.g., a request for DL RS configured for L1 / L2 / L3 measurements of source / destination nodes). In some aspects, 1602 may be performed by the mobility enhancement component 198.

[0138] At 1606, the UE may receive configuration, allocation, or activation of mobility measurement resources or mobility reporting resources in response to a UE request. For example, see Figure 8 , the UE 802 may receive configuration, allocation, or activation of mobility measurement resources or mobility reporting resources (e.g., configuration / reconfiguration of L1 / L2 / L3 measurements of the source / target node) at 816 in response to a UE request (transmitted by the UE at 810). In some aspects, 1606 may be performed by the mobility enhancement component 198.

[0139] In some aspects, the request may be for a downlink reference signal for L1 measurements, L2 measurements, or L3 measurements of the source node and at least one target node. For example, see Figure 8 , the request may be for a DL RS for L1 measurements, L2 measurements, or L3 measurements of the source node 804 and at least one target node (806, 808).

[0140] In some aspects, the UE may be further configured to receive a downlink reference signal at 1608 in response to a UE request, and at 1610, after measuring the downlink reference signal, use at least a portion of the resources allocated for mobility reporting in response to the UE request to transmit a measurement report. The measurement report may include measurement information for one or more of the source node or at least one target node. For example, see Figure 8 , the UE 802 may be further configured to receive a downlink reference signal at 818 in response to a UE request, and at 824, after measuring the downlink reference signal, use at least a portion of the resources allocated for mobility reporting in response to the UE request to transmit a measurement report. The measurement report may include measurement information for one or more of the source node 804 or at least one target node (806, 808). In some aspects, 1608 and 1610 may be performed by the mobility enhancement component 198.

[0141] In some aspects, the downlink reference signal may be aperiodic or periodic and may include at least one of the following: NCD-SSB, PRS, CSI-RS, or TRS. For example, see Figure 8 , when the UE 802 receives a DL RS from the source node 804 at 818, the DL RS may be aperiodic or periodic and may include at least one of the following: NCD-SSB, PRS, CSI-RS, or TRS.

[0142] In some aspects, a UE request may be indicated in at least one of the following: uplink reference signal, uplink sequence, uplink control channel, or uplink data channel, and the configuration, allocation, or activation in response to the UE request may be included in a DCI, RRC message, MAC-CE, or a combination thereof. For example, see Figure 8 , the UE request (transmitted by UE 802 to source node 804 at 810) may be indicated in at least one of the following: uplink reference signal, uplink sequence, uplink control channel, or uplink data channel, and the configuration, allocation, or activation in response to the UE request (received by UE 802 at 816) may be included in a DCI, RRC message, MAC-CE, or a combination thereof.

[0143] In some aspects, the UE may be further configured to receive, at 1604, one or more configurations for L1 measurements, L2 measurements, or L3 measurements. The UE may receive the activation of one of the one or more configurations in response to the UE request. For example, see Figure 8 , UE 802 may be further configured to receive, at 816, one or more configurations for L1 measurements, L2 measurements, or L3 measurements. The UE may receive the activation of one of the one or more configurations in response to the UE request (transmitted by UE 802 at 810). In some aspects, 1604 may be performed by the mobility enhancement component 198.

[0144] In some aspects, the UE request may be for a mobility reporting resource to report one or more of the following: a mobility measurement report, the status of the BWP inactivity timer, the status of the mobility timer, or the conditions for triggering or resetting the mobility timer or the BWP inactivity timer. The UE may be further configured to receive, at 1612, at least one of a mobility measurement report, the status of the BWP inactivity timer, the status of the mobility timer, or the conditions for triggering or resetting the mobility timer or the BWP inactivity timer. For example, see Figure 8 , the UE request (transmitted by UE 802 at 810) may be for a mobility reporting resource to report one or more of the following: a mobility measurement report, the status of the BWP inactivity timer, the status of the mobility timer, or the conditions for triggering or resetting the mobility timer or the BWP inactivity timer. See Figure 9 , UE 902 may be further configured to receive at least one of a mobility measurement report (at 916), the status of the BWP inactivity timer (at 918), the status of the mobility timer, or the conditions for triggering or resetting the mobility timer or the BWP inactivity timer. In some aspects, 1612 may be performed by the mobility enhancement component 198.

[0145] In some aspects, the UE may be further configured to receive, at 1614, an indication to reset the UE's BWP inactivity timer or mobility timer, or to receive, at 1616, additional information for the UE's mobility measurement or mobility. The additional information may include at least one of on-demand reference signal transmission or on-demand reference signal activation, or update information for at least one target node. For example, referring to Figure 9 , the UE 902 may be further configured to receive, at 920, an indication to reset the UE's BWP inactivity timer or mobility timer, or to receive, at 922, additional information for the UE's mobility measurement or mobility. The additional information may include at least one of on-demand reference signal transmission or on-demand reference signal activation, or update information for at least one target node. In some aspects, 1614 and 1616 may be performed by the mobility enhancement component 198.

[0146] Figure 17 FIG. 1700 is a flowchart illustrating a method of wireless communication at a UE in accordance with various aspects of the present disclosure. In various aspects, the method may be performed by the UE in the context of a target node and a source node. The UE may be Figure 18 the UE 104, 350, 802, 902, 1002 or the apparatus 1804 in a hardware implementation of Figure 1 . In some aspects, the source node may be a source base station and the target node may be a target base station. In other aspects, the source node may be a source TRP and the target node may be a target TRP. The source TRP and the target TRP may be used for the same base station or may be used for different base stations. In some aspects, the source node may be a first component of a base station and the target node may be a second component of the same base station or a different base station. The base station may be Figure 18 a base station or a component of a base station in an access network, or a core network component (e.g., the base station 102, 310; or Figure 18 the network entity 1802 in a hardware implementation of

[0147] As shown in Figure 17 , at 1702, the UE may send mobility measurement information indicating a cell handover, a change in the primary cell in dual connectivity, a TRP handover, or a beam handover to a network node. The network node may be Figure 1 a base station or a component of a base station in an access network, or a core network component (e.g., the base station 102, 310; the source node 1004; or Figure 18 the network entity 1802 in a hardware implementation of Figure 8 , Figure 9 and Figure 10Illustrates various aspects of the steps in conjunction with the flow chart 1700. For example, see Figure 10 , the UE 1002 may send mobility measurement information indicating cell handover, change of the primary cell in dual connectivity, TRP handover, or beam handover to a network node (source node 1004) at 1008. In some aspects, 1702 may be performed by the mobility enhancement component 198.

[0148] At 1704, the UE may receive an indication of repeated mobility signaling, which indicates cell handover, change of the primary cell in dual connectivity, TRP handover, or beam handover. For example, see Figure 10 , the UE 1002 may receive an indication of repeated mobility signaling at 1010, which indicates cell handover, change of the primary cell in dual connectivity, TRP handover, or beam handover. In some aspects, 1704 may be performed by the mobility enhancement component 198.

[0149] In some aspects, the indication of repeated mobility signaling may be provided based on measurements from the UE or the timer state of the UE. For example, see Figure 10 , when the UE 1002 receives an indication of repeated mobility signaling from the source node 1004 at 1010, the indication may be provided based on measurements from the UE 1002 or the timer state of the UE 1002.

[0150] In some aspects, the indication of repeated mobility signaling may be included in at least one of the following: DCI, RRC message, MAC-CE, sequence, or reference signal. For example, see Figure 10 , when the UE 1002 receives an indication of repeated mobility signaling from the source node 1004 at 1010, the indication of repeated mobility signaling may be included in at least one of the following: DCI, RRC message, MAC-CE, sequence, or reference signal.

[0151] In some aspects, the repeated mobility signaling may include commands for cell handover, change of the primary cell in dual connectivity, TRP handover, or beam handover to be repeated in multiple BWPs during a time window. The window may start from a reference time associated with the UE's reception of the mobility signaling. The multiple BWPs may include the active downlink BWP and the default downlink BWP of the source node. The time window may start from a reference time associated with the UE's reception of the mobility signaling. For example, see Figure 10, when the UE 1002 receives an indication of repeated mobility signaling from the source node 1004 at 1010, the repeated mobility signaling may include commands for cell handover repeated in multiple BWPs during a time window, a change of the primary cell in dual connectivity, a TRP handover, or a beam handover. The window may start from a reference time associated with the UE 1002's reception of the mobility signaling. The multiple BWPs may include the active downlink BWP and the default downlink BWP of the source node 1004. The time window may start from a reference time associated with the UE 1002's reception of the mobility signaling.

[0152] In some aspects, the repeated mobility signaling may include joint transmission from the source node and the target node in an SFN transmission scheme. For example, see Figure 10 , when the UE 1002 receives an indication of repeated mobility signaling from the source node 1004 at 1010, the repeated mobility signaling may include joint transmission from the source node 1004 and the target node in an SFN transmission scheme.

[0153] Figure 18FIG. 1800 is a diagram illustrating an example of a hardware implementation for apparatus 1804. Apparatus 1804 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, apparatus 1804 may include at least one cellular baseband processor 1824 (also referred to as a modem) coupled to one or more transceivers 1822 (e.g., cellular RF transceivers). The cellular baseband processor 1824 may include at least one on-chip memory 1824'. In some aspects, apparatus 1804 may also include one or more subscriber identity module (SIM) cards 1820 and at least one application processor 1806 coupled to a secure digital (SD) card 1808 and a screen 1810. The application processor 1806 may include on-chip memory 1806'. In some aspects, apparatus 1804 may also include a Bluetooth module 1812, a WLAN module 1814, an SPS module 1816 (e.g., a GNSS module), one or more sensor modules 1818 (e.g., an atmospheric pressure sensor / altimeter; motion sensors such as an inertial measurement unit (IMU), gyroscope, and / or accelerometer; light detection and ranging (LIDAR), radio assisted detection and ranging (RADAR), sound navigation and ranging (SONAR), magnetometer, audio, and / or other technologies for positioning), additional memory modules 1826, a power source 1830, and / or a camera 1832. The Bluetooth module 1812, the WLAN module 1814, and the SPS module 1816 may include on-chip transceivers (TRXs) (or in some cases, only receivers (RXs)). The Bluetooth module 1812, the WLAN module 1814, and the SPS module 1816 may include their own dedicated antennas and / or communicate using antenna 1880. The cellular baseband processor 1824 communicates with UE 104 and / or with an RU associated with network entity 1802 via transceiver 1822 through one or more antennas 1880. The cellular baseband processor 1824 and the application processor 1806 may each separately include computer-readable media / memory 1824', 1806'. The additional memory module 1826 may also be considered computer-readable media / memory. Each computer-readable media / memory 1824', 1806', 1826 may be non-transitory. The cellular baseband processor 1824 and the application processor 1806 are each responsible for general processing, including execution of software stored on the computer-readable media / memory. The software, when executed by the cellular baseband processor 1824 / application processor 1806, causes the cellular baseband processor 1824 / application processor 1806 to perform the various functions described above. The cellular baseband processor 1824 and the application processor 1806 are configured to perform the various functions described above based at least in part on information stored in the memory.That is, the cellular baseband processor 1824 and the application processor 1806 can be configured to perform a first subset of the various functions described above without information stored in the memory, and can be configured to perform a second subset of the various functions described above based on the information stored in the memory. The computer-readable medium / memory can also be used to store data manipulated by the cellular baseband processor 1824 / application processor 1806 when executing software. The cellular baseband processor 1824 / application processor 1806 can be a component of the UE 350 and can include at least one memory 360 and / or at least one of the TX processor 368, the RX processor 356, and the controller / processor 359. In one configuration, the device 1804 can be at least one processor chip (modem and / or application) and include only the cellular baseband processor 1824 and / or the application processor 1806, while in another configuration, the device 1804 can be the entire UE (e.g., see Figure 3 the UE350) and include additional modules of the device 1804.

[0154] As discussed above, in some aspects, the component 198 can be configured to send a UE request for an on-demand allocation of mobility measurement resources or mobility reporting resources for the UE; and receive a configuration, allocation, or activation for the mobility measurement resources or mobility reporting resources in response to the UE request. In some aspects, the component 198 can be configured to send mobility measurement information indicating a cell handover, a change in the primary cell in dual connectivity, a TRP handover, or a beam switch to a network node; and receive an indication of repeated mobility signaling, which indicates a cell handover, a change in the primary cell in dual connectivity, a TRP handover, or a beam switch. The component 198 can be further configured to perform any of the aspects described in the flowcharts associated with Figure 15 and Figure 17 and / or, respectively, by Figure 8 , Figure 9 and Figure 10Any aspect among the various aspects performed by the UEs 802, 902, 1002 in []. The component 198 can be within the cellular baseband processor 1824, the application processor 1806, or both the cellular baseband processor 1824 and the application processor 1806. The component 198 can be one or more hardware components that are specifically configured to perform the stated process / algorithm, implemented by one or more processors configured to perform the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination of the above. When multiple processors are implemented, the multiple processors can perform the stated process / algorithm individually or in combination. As shown, the apparatus 1804 can include various components configured for various functions. In one configuration, the apparatus 1804 (and particularly the cellular baseband processor 1824 and / or the application processor 1806) includes means for sending a UE request for an on-demand allocation of mobility measurement resources or mobility reporting resources to the UE; and means for receiving a configuration, allocation, or activation of mobility measurement resources or mobility reporting resources in response to the UE request. In one configuration, the apparatus 1804 can include means for sending mobility measurement information to a network node that triggers or indicates a cell handover, a change in the primary cell in dual connectivity, a TRP handover, or a beam switch; and means for receiving an indication of repeated mobility signaling that triggers or indicates a cell handover, a change in the primary cell in dual connectivity, a TRP handover, or a beam switch. The apparatus 1804 can also include means for performing any aspect among the various aspects described in the flowchart in conjunction with Figure 15 and Figure 17 and / or any aspect among the various aspects performed by the UEs 802, 902, 1002 in [], respectively, by Figure 8 , Figure 9 and Figure 10 . The means can be the component 198 of the apparatus 1804 configured to perform the functions recited by the means. As described above, the apparatus 1804 can include a TX processor 368, an RX processor 356, and a controller / processor 359. Thus, in one configuration, the means can be the TX processor 368, the RX processor 356, and / or the controller / processor 359 configured to perform the functions recited by the means.

[0155] Figure 19FIG. 1900 is a diagram illustrating an example of a hardware implementation for network entity 1902. Network entity 1902 can be a BS, a component of a BS, or can implement BS functionality. Network entity 1902 can include at least one of CU 1910, DU 1930, or RU 1940. For example, depending on the layer functions handled by component 199, network entity 1902 can include CU 1910; both CU 1910 and DU 1930; each of CU 1910, DU 1930, and RU 1940; DU 1930; both DU 1930 and RU 1940; or RU 1940. CU 1910 can include at least one CU processor 1912. CU processor 1912 can include on-chip memory 1912'. In some aspects, CU 1910 can also include additional memory modules 1914 and communication interface 1918. CU 1910 communicates with DU 1930 via an intermediate link, such as the F1 interface. DU 1930 can include at least one DU processor 1932. DU processor 1932 can include on-chip memory 1932'. In some aspects, DU 1930 can also include additional memory modules 1934 and communication interface 1938. DU 1930 communicates with RU 1940 via a fronthaul link. RU 1940 can include at least one RU processor 1942. RU processor 1942 can include on-chip memory 1942'. In some aspects, RU 1940 can also include additional memory modules 1944, one or more transceivers 1946, antenna 1980, and communication interface 1948. RU 1940 communicates with UE 104. On-chip memories 1912', 1932', 1942' and additional memory modules 1914, 1934, 1944 can each be considered computer-readable media / memories. Each computer-readable media / memory can be non-transitory. Each of processors 1912, 1932, 1942 is responsible for general processing, including executing software stored on the computer-readable media / memory. The software, when executed by the corresponding processor, causes the processor to perform the various functions described above. The computer-readable media / memory can also be used to store data manipulated by the processor when executing the software.

[0156] As discussed above, in some aspects, component 199 may be configured to receive a UE request for an on-demand allocation of mobility measurement resources or mobility reporting resources for the UE; and provide configuration, allocation, or activation of the mobility measurement resources or mobility reporting resources in response to the UE request. In some aspects, component 199 may be configured to receive, from a source node, a request for a downlink reference signal configured for L1 or L3 measurements at the UE; and provide a reference signal configuration for the UE to the source node in response to the request. In some aspects, component 199 may be configured to receive mobility measurement information from the UE that triggers or indicates a cell handover, a change in the primary cell in dual connectivity, a TRP handover, or a beam switch; and provide an indication of repeated mobility signaling that triggers or indicates a cell handover, a change in the primary cell in dual connectivity, a TRP handover, or a beam switch. Component 199 may be further configured to perform any of the aspects described in the flowcharts associated with Figure 11 , Figure 13 and Figure 14 , and / or respectively by Figure 8 , Figure 9 and Figure 10Any aspect of the aspects performed by the source nodes 804, 904, 1004 in []. Component 199 can be within one or more processors of one or more of CU 1910, DU 1930, and RU 1940. Component 199 can be one or more hardware components specifically configured to perform the stated process / algorithm, implemented by one or more processors configured to perform the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination of the above. When multiple processors are implemented, the multiple processors can perform the stated process / algorithm individually or in combination. Network entity 1902 can include various components configured for various functions. In one configuration, network entity 1902 includes components for receiving a UE request for on-demand allocation of mobility measurement resources or mobility reporting resources for the UE; and components for providing configuration, allocation, or activation of mobility measurement resources or mobility reporting resources in response to the UE request. In one configuration, network entity 1902 can include components for receiving from a source node a request for a downlink reference signal configured for L1 or L3 measurements at the UE; and components for providing reference signal configuration for the UE to the source node in response to the request. In one configuration, network entity 1902 can include components for receiving from the UE mobility measurement information triggering or indicating cell handover, change of the primary cell in dual connectivity, TRP handover, or beam switching; and components for providing an indication of repeated mobility signaling that triggers or indicates cell handover, change of the primary cell in dual connectivity, TRP handover, or beam switching. Network entity 1902 can also include components for performing any aspect of the aspects described in the flowcharts associated with Figure 11 , Figure 13 and Figure 14 and / or any aspect of the aspects performed by the source nodes 804, 904, 1004 in Figure 8 , Figure 9 and Figure 10 . The components can be component 199 of network entity 1902 configured to perform the functions documented by the components. As described above, network entity 1902 can include TX processor 316, RX processor 370, and controller / processor 375. Thus, in one configuration, the components can be TX processor 316, RX processor 370, and / or controller / processor 375 configured to perform the functions documented by the components.

[0157] The present disclosure provides a method for wireless communication at a source node. The method may include receiving a UE request for on-demand allocation of mobility measurement resources or mobility reporting resources for a UE; and providing configuration, allocation, or activation of mobility measurement resources or mobility reporting resources in response to the UE request. The method improves the flexibility and reliability in processing UE requests for mobility measurement sources or mobility reporting resources. Therefore, the efficiency of wireless communication is improved.

[0158] It should be understood that the specific order or hierarchy of the blocks in the disclosed process / flowchart is illustrative of example methods. It should be understood that based on design preferences, the specific order or hierarchy of the blocks in the process / flowchart may be rearranged. Further, some blocks may be combined or omitted. The appended method claims present the elements of the various blocks in a sample order, but are not limited to the specific order or hierarchy presented.

[0159] 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 can be applied to other aspects. Thus, the claims are not limited to the aspects described herein, but are to be accorded the full scope consistent with the language of the claims. References to elements in the singular form do not mean "one and only one" unless specifically stated, but rather "one or more." Terms such as "if," "when," and "while" do not denote a direct temporal relationship or reaction. That is, these phrases, such as "when...," do not mean an immediate action in response to the occurrence of an action or during the occurrence of an action, but simply imply that if a condition is met, then the action will occur, without requiring a specific or immediate time limitation for the occurrence of the action. 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 having an advantage over other aspects. Unless specifically stated, 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 "any combination of A, B, C, or any of them," including any combination of A, B, and / or C, may include multiple A's, multiple B's, or multiple C's. Specifically, combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B, and C," "one or more of A, B, and C," and "any combination of A, B, C, or any of them" can be only A, only B, only C, A and B, A and C, B and C, or A and B and C, where any such combination may contain one or more members of A, B, or C. A set should be construed as a collection of elements, where the number of elements is one or more. Thus, for a set of X, X will include one or more elements. When at least one processor is configured to perform a set of functions, the at least one processor is configured to perform the set of functions individually or in any combination. Thus, each processor in the at least one processor may be configured to perform a particular subset of the set of functions, where the subset is the complete set, a proper subset of the set, or the empty subset of the set. A processor may be referred to as a processor circuit. A memory / memory module may be referred to as a memory circuit. If a first device receives data from or sends data to a second device, the data may be received / sent directly between the first device and the second device, or indirectly between the first device and the second device through a collection of devices. A device configured to "output" or "provide" data (such as, a transmission, signal, or message) may, for example, send the data with a transceiver, or may convey the data to a device that sends the data.A device configured to "obtain" data (such as a transmission, signal, or message) can receive the data with a transceiver, for example, or can obtain the data from a device that received the data. Information stored in a memory includes instructions and / or data. All structural and functional equivalents of the elements of the aspects described throughout this disclosure that are known or will later be known to those of ordinary skill in the art are expressly incorporated herein by reference and are covered by the claims. Additionally, nothing disclosed herein is intended to be dedicated to the public, whether or not such disclosure is explicitly recited in the claims. The words "module," "mechanism," "element," "device," etc. do not substitute for the word "component." Accordingly, no claim element shall be construed as a means-plus-function unless the element is expressly recited using the phrase "means for...".

[0160] As used herein, the phrase "based on" should not be construed to refer 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.) should be construed as "at least based on A" unless stated otherwise specifically.

[0161] The following aspects are merely illustrative and can be combined with other aspects or teachings described herein without limitation.

[0162] Aspect 1 is a method for wireless communication at a source node. The method can include receiving a UE request for an on-demand allocation of mobility measurement resources or mobility reporting resources for a UE; and providing a configuration, allocation, or activation for the mobility measurement resources or the mobility reporting resources in response to the UE request.

[0163] Aspect 2 is the method according to Aspect 1, wherein the request is for a downlink reference signal for L1 measurement, L2 measurement, or L3 measurement for the source node and at least one target node.

[0164] Aspect 3 is the method according to any one of Aspects 1 to 2, wherein the method can further include sending the downlink reference signal and the resource allocation for mobility reporting in response to the UE request; and receiving a measurement report using at least a portion of the resources allocated for mobility reporting in response to the UE request after measuring the downlink reference signal. The measurement report can include measurement information for one or more of the source node or the at least one target node. The measurement report of the UE can use at least a portion of the resources allocated for mobility reporting in response to the UE request.

[0165] Aspect 4 is the method according to any one of Aspects 2 to 3, wherein the downlink reference signal can be aperiodic or periodic, and may include at least one of the following: NCD-SSB, PRS, CSI-RS, or TRS.

[0166] Aspect 5 is the method according to any one of Aspects 2 to 4, wherein the UE request can be indicated in at least one of the following: uplink reference signal, uplink sequence, uplink control channel, or uplink data channel.

[0167] Aspect 6 is the method according to any one of Aspects 2 to 5, wherein the configuration, the allocation, or the activation in response to the UE request can be included in DCI, RRC message, MAC-CE, or a mixture thereof.

[0168] Aspect 7 is the method according to any one of Aspects 2 to 6, wherein the method may further include configuring one or more configurations for the L1 measurement, the L2 measurement, or the L3 measurement. The source node can activate one of the one or more configurations in response to the UE request.

[0169] Aspect 8 is the method according to any one of Aspects 2 to 7, wherein the method may further include providing a request for target node resources for the L1 measurement, the L2 measurement, or the L3 measurement to be performed by the UE to the at least one target node; and receiving a reference signal configuration from the at least one target node. The source node can provide the configuration in response to the UE request, and the configuration can include the reference signal configuration from the at least one target node.

[0170] Aspect 9 is the method according to any one of Aspects 1 to 8, wherein the UE request can be for the mobility reporting resources to report one or more of the following: mobility measurement report, inactivity status of the BWP inactivity timer, mobility status of the mobility timer, or conditions triggering the mobility timer or the BWP inactivity timer. The method may further include receiving at least one of the mobility measurement report, the inactivity status of the BWP inactivity timer, the mobility status of the mobility timer, or the conditions triggering or resetting the mobility timer or the BWP inactivity timer.

[0171] Aspect 10 is the method according to Aspect 9, wherein the method may further include providing an indication for the UE to reset the BWP inactivity timer or the mobility timer.

[0172] Aspect 11 is the method according to aspect 9, wherein the method may further include providing additional information for mobility measurement or mobility of the UE. The additional information may include at least one of on-demand reference signal transmission or on-demand reference signal activation, or updated information for the at least one target node.

[0173] Aspect 12 is a method for wireless communication at a target node. The method may include receiving, from a source node, a request for a downlink reference signal configured for L1 or L3 measurement at a UE; and providing, in response to the request, a reference signal configuration for the UE to the source node.

[0174] Aspect 13 is a device for wireless communication, the device including: at least one memory; and at least one processor, the at least one processor being coupled to the at least one memory and being configured to perform, alone or in any combination, the method according to any one of aspects 1 to 12, at least in part based on information stored in the at least one memory.

[0175] Aspect 14 is the device according to aspect 13, further including at least one of a transceiver or an antenna, the at least one of the transceiver or the antenna being coupled to the at least one processor and being configured to receive the UE request or a request from a source node.

[0176] Aspect 15 is a device for wireless communication, the device including components for implementing the method according to any one of aspects 1 to 12.

[0177] Aspect 16 is a computer-readable medium (e.g., a non-transitory computer-readable medium) storing computer-executable code for wireless communication at a node, wherein the code, when executed by at least one processor, causes the node to implement the method according to any one of aspects 1 to 12.

[0178] Aspect 17 is a method for wireless communication at a network entity. The method may include receiving, from a UE, mobility measurement information triggering or indicating cell handover, a change in a primary cell in dual connectivity, a TRP handover, or a beam switch; and providing an indication of repeated mobility signaling that triggers or indicates the cell handover, the change in the primary cell in dual connectivity, the TRP handover, or the beam switch.

[0179] Aspect 18 is the method according to aspect 17, wherein the indication of the repeated mobility signaling may be provided based on a measurement from the UE or a timer state of the UE.

[0180] Aspect 19 is the method according to any one of Aspects 17 to 18, wherein the indication of the repeated mobility signaling may be included in at least one of the following: DCI, RRC message, MAC-CE, sequence, or reference signal.

[0181] Aspect 20 is the method according to any one of Aspects 17 to 19, wherein the repeated mobility signaling may include commands for the cell handover repeated in multiple BWPs during a time window, the change of the primary cell in dual connectivity, the TRP handover, or the beam handover. The window may start from a reference time associated with the UE's reception of the mobility signaling.

[0182] Aspect 21 is the method according to Aspect 20, wherein the multiple BWPs may include the active downlink BWP and the default downlink BWP of the source node.

[0183] Aspect 22 is the method according to any one of Aspects 17 to 21, wherein the repeated mobility signaling may include a joint transmission from the source node and the target node in an SFN transmission scheme.

[0184] Aspect 23 is a device for wireless communication at a network entity, the device including: at least one memory; and at least one processor, the at least one processor being coupled to the at least one memory, and at least partially based on information stored in the at least one memory, the at least one processor is configured alone or in any combination to cause the network entity to perform the method according to any one of Aspects 17 to 22.

[0185] Aspect 24 is the device according to Aspect 23, further including at least one of a transceiver or an antenna, the at least one of the transceiver or the antenna being coupled to the at least one processor and configured to receive the mobility measurement information.

[0186] Aspect 25 is a device for wireless communication, the device including components for implementing the method according to any one of Aspects 17 to 22.

[0187] Aspect 26 is a computer-readable medium (e.g., a non-transitory computer-readable medium) storing computer-executable code for wireless communication at a network entity, wherein the code, when executed by at least one processor, causes the network entity to implement the method according to any one of Aspects 17 to 22.

[0188] Aspect 27 is a method for wireless communication at a UE. The method may include transmitting a UE request for an on-demand allocation of mobility measurement resources or mobility reporting resources for the UE; and receiving, in response to the UE request, a configuration, allocation, or activation for the mobility measurement resources or the mobility reporting resources.

[0189] Aspect 28 is the method according to aspect 27, wherein the request may be for a downlink reference signal for L1 measurement, L2 measurement, or L3 measurement for a source node and at least one target node.

[0190] Aspect 29 is the method according to any one of aspects 27 to 28, wherein the method may further include: receiving the downlink reference signal and the resource allocation for mobility reporting in response to the UE request; and transmitting a measurement report using at least a portion of the resources allocated for mobility reporting in response to the UE request after measuring the downlink reference signal. The measurement report may include measurement information for one or more of the source node or the at least one target node, and the measurement report of the UE may use at least a portion of the resources allocated for mobility reporting in response to the UE request.

[0191] Aspect 30 is the method according to aspect 29, wherein the downlink reference signal may be aperiodic or periodic and may include at least one of the following: NCD-SSB, PRS, CSI-RS, or TRS.

[0192] Aspect 31 is the method according to any one of aspects 28 to 30, wherein the UE request may be indicated in at least one of the following: an uplink reference signal, an uplink sequence, an uplink control channel, or an uplink data channel, and the configuration, the allocation, or the activation in response to the UE request may be included in a DCI, an RRC message, or a MAC-CE or a combination thereof.

[0193] Aspect 32 is the method according to any one of aspects 28 to 31, wherein the method may further include receiving one or more configurations for the L1 measurement, the L2 measurement, or the L3 measurement, and the UE may receive the activation of one of the one or more configurations in response to the UE request.

[0194] Aspect 33 is the method according to any one of aspects 27 to 32, wherein the UE request may be for the mobility reporting resource to report one or more of the following: a mobility measurement report, an inactivity status of a BWP inactivity timer, a mobility status of a mobility timer, or a condition for triggering or resetting the mobility timer or the BWP inactivity timer. And the method may further include receiving at least one of the mobility measurement report, the inactivity status of the BWP inactivity timer, the mobility status of the mobility timer, or the condition for triggering or resetting the mobility timer or the BWP inactivity timer.

[0195] Aspect 34 is the method according to aspect 33, wherein the method may further include: receiving an indication to reset the BWP inactivity timer or the mobility timer for the UE, or receiving additional information for mobility measurement or mobility of the UE. The additional information may include at least one of on-demand reference signal transmission or on-demand reference signal activation, or update information for at least one target node.

[0196] Aspect 35 is a device for wireless communication at a UE, the device including: at least one memory; and at least one processor, the at least one processor being coupled to the at least one memory and being configured, at least in part based on information stored in the at least one memory, to cause the UE to perform the method according to any one of aspects 27 to 34, either alone or in any combination.

[0197] Aspect 36 is the device according to aspect 35, further including at least one of a transceiver or an antenna, the at least one of the transceiver or the antenna being coupled to the at least one processor and being configured to send the UE request.

[0198] Aspect 37 is a device for wireless communication, the device including components for implementing the method according to any one of aspects 27 to 34.

[0199] Aspect 38 is a computer-readable medium (e.g., a non-transitory computer-readable medium) storing computer-executable code for wireless communication at a UE, wherein the code, when executed by at least one processor, causes the UE to implement the method according to any one of aspects 27 to 34.

[0200] Aspect 39 is a method for wireless communication at a UE. The method may include sending mobility measurement information to a network node that triggers or indicates a cell handover, a change of a primary cell in dual connectivity, a TRP handover, or a beam handover; and receiving an indication of repeated mobility signaling that indicates the cell handover, the change of the primary cell, the TRP handover, or the beam handover.

[0201] Aspect 40 is the method according to aspect 39, wherein the indication of the repeated mobility signaling may be provided based on measurements from the UE or the timer status of the UE.

[0202] Aspect 41 is the method according to any one of aspects 39 to 40, wherein the indication of the repeated mobility signaling may be included in at least one of the following: DCI, RRC message, MAC-CE, sequence, or reference signal.

[0203] Aspect 42 is the method according to any one of aspects 39 to 41, wherein the repeated mobility signaling may include a command for the cell handover, the change of the primary cell in dual connectivity, the TRP handover, or the beam handover to be repeated in a plurality of BWPs during a time window. The window may start from a reference time associated with the UE's reception of the mobility signaling, and the plurality of BWPs may include the active downlink BWP and the default downlink BWP of the source node. The time window may start from a reference time associated with the UE's reception of the mobility signaling.

[0204] Aspect 43 is the method according to any one of aspects 39 to 42, wherein the repeated mobility signaling may include a joint transmission from a source node and a target node in an SFN transmission scheme.

[0205] Aspect 44 is a device for wireless communication at a UE, the device including: at least one memory; and at least one processor, the at least one processor being coupled to the at least one memory and being configured, alone or in any combination, to perform the method according to any one of aspects 39 to 43 at least partially based on information stored in the at least one memory.

[0206] Aspect 45 is the device according to aspect 44, further including at least one of a transceiver or an antenna, the at least one of the transceiver or the antenna being coupled to the at least one processor and being configured to send the mobility measurement information.

[0207] Aspect 46 is a device for wireless communication, the device including components for implementing the method according to any one of aspects 39 to 43.

[0208] Aspect 47 is a computer-readable medium (e.g., a non-transitory computer-readable medium) storing computer-executable code for wireless communication at a UE, wherein the code, when executed by at least one processor, causes the UE to implement the method according to any one of Aspects 39 to 43.

Claims

1. An apparatus for wireless communication at a source node, the apparatus comprising: at least one memory; and at least one processor coupled to the at least one memory, and at least partially based on information stored in the at least one memory, the at least one processor is configured, alone or in any combination, to cause the source node to: receive a UE request for an on-demand allocation of mobility measurement resources or mobility reporting resources for a user equipment (UE); and in response to the UE request, provide a configuration, allocation, or activation for the mobility measurement resources or the mobility reporting resources.

2. The apparatus according to claim 1, further comprising a transceiver coupled to the at least one processor, wherein, in order to receive the UE request, the at least one processor is configured, alone or in any combination, to cause the source node to receive the UE request via the transceiver.

3. The apparatus according to claim 1, wherein the UE request is for a downlink reference signal for layer 1 (L1) measurements or layer 3 (L3) measurements for the source node and at least one target node.

4. The apparatus according to claim 3, wherein the at least one processor is further configured, alone or in any combination, to cause the source node to: in response to the UE request, send the downlink reference signal and a resource allocation for mobility reporting; and receive a measurement report after sending the downlink reference signal, the measurement report including measurement information for one or more of the source node or the at least one target node, and wherein the measurement report of the UE uses at least a portion of the resources allocated in the resource allocation for mobility reporting in response to the UE request.

5. The apparatus according to claim 4, wherein the downlink reference signal is aperiodic or periodic and includes at least one of the following: non-cell-defined synchronization signal block (NCD-SSB), positioning reference signal (PRS), channel state information reference signal (CSI-RS), or tracking reference signal (TRS).

6. The apparatus according to claim 3, wherein the UE request indicates in at least one of the following: an uplink reference signal, an uplink sequence, an uplink control channel, or an uplink data channel.

7. The apparatus according to claim 3, wherein the configuration, the allocation, or the activation in response to the UE request is included in downlink control information (DCI), a radio resource control (RRC) message, a media access control-control element (MAC-CE), or a combination thereof.

8. The apparatus according to claim 3, wherein the at least one processor is further configured, alone or in any combination, to cause the source node to: configure one or more configurations for the L1 measurement or the L3 measurement, wherein the source node activates one of the one or more configurations in response to the UE request.

9. The apparatus according to claim 3, wherein the at least one processor is further configured, alone or in any combination, to cause the source node to: Provide a target request to the at least one target node for target node resources for the L1 measurement or the L3 measurement to be performed by the UE; and Receive at least one reference signal configuration from the at least one target node, wherein the source node provides the at least one reference signal configuration in response to the UE request, and the at least one reference signal configuration includes a reference signal configuration from the at least one target node for the L1 measurement or the L3 measurement or a combination thereof.

10. The apparatus according to claim 1, wherein the UE request is for the mobility reporting resource to report one or more of the following: A mobility measurement report, An inactive state of a bandwidth part (BWP) inactivity timer, A mobility state of a mobility timer, or A condition for triggering or resetting the mobility timer or the BWP inactivity timer.

11. The apparatus according to claim 10, wherein the at least one processor is further configured, alone or in any combination, to cause the source node to receive at least one of the mobility measurement report, the inactive state of the BWP inactivity timer, the mobility state of the mobility timer, or the condition for triggering or resetting the mobility timer or the BWP inactivity timer.

12. The apparatus according to claim 11, wherein the at least one processor is further configured, alone or in any combination, to cause the source node to: Provide an indication to the UE to reset the BWP inactivity timer or the mobility timer.

13. The apparatus according to claim 11, wherein the at least one processor is further configured, alone or in any combination, to cause the source node to: Provide additional information for the UE's mobility measurement or mobility, the additional information including at least one of on-demand reference signal transmission or on-demand reference signal activation, or update information for at least one target node.

14. An apparatus for wireless communication at a target node, the apparatus comprising: At least one memory; And At least one processor, the at least one processor coupled to the at least one memory, and at least partially based on information stored in the at least one memory, the at least one processor is configured, alone or in any combination, to cause the target node to: Receive a request from a source node for a downlink reference signal configured for layer 1 (L1) or layer 3 (L3) measurements at a user equipment (UE); And Provide a reference signal configuration for the UE to the source node in response to the request.

15. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: At least one memory; And At least one processor, the at least one processor being coupled to the at least one memory and, at least in part based on information stored in the at least one memory, the at least one processor being configured, alone or in any combination, to cause the UE: Send a UE request for on-demand allocation of mobility measurement resources or mobility reporting resources for the user equipment (UE); and Receive a configuration, allocation, or activation for the mobility measurement resources or the mobility reporting resources in response to the UE request.

16. The apparatus according to claim 15, wherein the UE request is for a downlink reference signal for layer 1 (L1) measurements or layer 3 (L3) measurements for a source node and at least one target node.

17. The apparatus according to claim 15, wherein the at least one processor is further configured, alone or in any combination, to cause the UE: Receive a downlink reference signal in response to the UE request; and After measuring the downlink reference signal, use at least a portion of the resources allocated for mobility reporting in response to the UE request to send a measurement report, the measurement report including measurement information for one or more of the source node or at least one target node.

18. The apparatus according to claim 17, wherein the downlink reference signal is aperiodic or periodic and includes at least one of the following: Non-cell definition synchronization signal block (NCD-SSB), Positioning reference signal (PRS), Channel state information reference signal (CSI-RS), or Tracking reference signal (TRS).

19. The apparatus according to claim 16, wherein the UE request indicates in at least one of the following: Uplink reference signal, Uplink sequence, Uplink control channel, or Uplink data channel.

20. The apparatus according to claim 16, wherein the configuration, the allocation, or the activation in response to the UE request is included in downlink control information (DCI), radio resource control (RRC) message, medium access control - control element (MAC-CE), or a combination thereof.

21. The apparatus according to claim 16, wherein the at least one processor is further configured, alone or in any combination, to cause the UE: Receive one or more configurations for the L1 measurements or the L3 measurements, wherein the UE receives the activation of one of the one or more configurations in response to the UE request.

22. The apparatus according to claim 15, wherein the UE request is for the mobility reporting resources to report one or more of the following: Mobility measurement report, Inactive state of a bandwidth part (BWP) inactivity timer, Mobility state of a mobility timer, or Conditions for triggering or resetting the mobility timer or the BWP inactivity timer.

23. The apparatus according to claim 22, wherein the at least one processor is further configured, alone or in any combination, to receive at least one of the mobility measurement report, the inactive state of the BWP inactivity timer, the mobility state of the mobility timer, or the condition for triggering or resetting the mobility timer or the BWP inactivity timer.

24. The apparatus according to claim 23, wherein the at least one processor is further configured, alone or in any combination, to cause the UE to: Receive an indication to reset the BWP inactivity timer or the mobility timer for the UE.

25. The apparatus according to claim 23, wherein the at least one processor is further configured, alone or in any combination, to cause the UE to: Receive additional information for mobility measurement or mobility of the UE, the additional information including at least one of on-demand reference signal transmission or on-demand reference signal activation, or update information for at least one target node.

26. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: At least one memory; And At least one processor coupled to the at least one memory and at least partially based on information stored in the at least one memory, the at least one processor is configured, alone or in any combination, to cause the UE to: Transmit mobility measurement information triggering or indicating cell handover, change of a primary cell in dual connectivity, TRP handover, or beam handover to a network node; And Receive an indication of repeated mobility signaling that triggers or indicates the cell handover, the change of the primary cell, the TRP handover, or the beam handover.

27. The apparatus according to claim 26, wherein the indication of the repeated mobility signaling is provided based at least on measurements from the UE or the timer state of the UE.

28. The apparatus according to claim 26, wherein the indication of the repeated mobility signaling is included in at least one of the following: Downlink control information (DCI), Medium access control - control element (MAC-CE), Radio resource control (RRC) message, Sequence, or Reference signal.

29. The apparatus according to claim 26, wherein the repeated mobility signaling includes a command for the cell handover, the change of the primary cell, the TRP handover, or the beam handover to be repeated in a plurality of bandwidth parts (BWPs) during a time window, wherein the plurality of BWPs includes an active downlink BWP and a default downlink BWP of a source node, and the time window starts from a reference time associated with the UE's reception of the mobility signaling.

30. The apparatus according to claim 26, wherein the repeated mobility signaling includes a joint transmission from a source node and at least a target node in a single-frequency network (SFN) transmission scheme.

Images