EP4666487A1

EP4666487A1 - L1 inter-frequency measurement configuration in ltm

Info

Publication number: EP4666487A1
Application number: EP23708144.3A
Authority: EP
Inventors: Fang Yuan; Yan Zhou; Jelena Damnjanovic
Original assignee: Qualcomm Inc
Current assignee: Qualcomm Inc
Priority date: 2023-02-15
Filing date: 2023-02-15
Publication date: 2025-12-24
Also published as: CN120604487A; WO2024168564A1

Abstract

A method for wireless communication at a user equipment (UE) and related apparatus are provided. In the method, the UE obtains a first configuration of a channel measurement resource set. The channel measurement resource set includes one or more reference signals (RSs) for lower-layer triggered mobility (LTM) and is associated with a layer 1 (L1) channel state information (CSI) report. The channel measurement resource set further includes one or more reference identifiers (IDs) for the one or more RSs. The UE further performs at least one measurement for LTM based on the one or more RSs. The method enhances the flexibility of inter-frequency LTM measurements and improves the efficiency of wireless communication.

Description

L1 INTER-FREQUENCY MEASUREMENT CONFIGURATION IN LTM

TECHNICAL FIELD

The present disclosure relates generally to communication systems, and more particularly, to layer 1 (L1) inter-frequency measurement configuration in lower-layer triggered mobility (LTM) for wireless communication.
INTRODUCTION
Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple-access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.
These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate on a municipal, national, regional, and even global level. An example telecommunication standard is 5G New Radio (NR) . 5G NR is part of a continuous mobile broadband evolution promulgated by Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with Internet of Things (IoT) ) , and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB) , massive machine type communications (mMTC) , and ultra-reliable low latency communications (URLLC) . Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. There exists a need for further improvements in 5G NR technology. These improvements may also be applicable to other multi-access technologies and the telecommunication standards that employ these technologies.
BRIEF SUMMARY
The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects. This summary neither identifies key or critical elements of all aspects nor delineates the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.
In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided for wireless communication at a user equipment (UE) . The apparatus may include memory and at least one processor coupled to the memory. Based at least in part on information stored in the memory, the at least one processor may be configured to obtain a first configuration of a channel measurement resource set including one or more reference signals (RSs) for LTM, where the channel measurement resource set is associated with an L1 channel state information (CSI) report and includes one or more reference identifiers (IDs) for the one or more RSs; and perform at least one measurement for LTM based on the one or more RSs.
In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided for wireless communication at a network entity. The apparatus may include memory and at least one processor coupled to the memory. Based at least in part on information stored in the memory, the at least one processor may be configured to configure, for a UE, a first configuration of a channel measurement resource set including one or more RSs for LTM, where the channel measurement resource set is associated with an L1 CSI report and includes one or more reference IDs for the one or more RSs; and receive, from the UE, at least one measurement for LTM based on the one or more RSs.
To the accomplishment of the foregoing and related ends, the one or more aspects may include the features hereinafter fully described and particularly pointed out in the claims. The following description and the drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram illustrating an example of a wireless communication system and an access network.
FIG. 2A is a diagram illustrating an example of a first frame, in accordance with various aspects of the present disclosure.
FIG. 2B is a diagram illustrating an example of downlink (DL) channels within a subframe, in accordance with various aspects of the present disclosure.
FIG. 2C is a diagram illustrating an example of a second frame, in accordance with various aspects of the present disclosure.
FIG. 2D is a diagram illustrating an example of uplink (UL) channels within a subframe, in accordance with various aspects of the present disclosure.
FIG. 3 is a diagram illustrating an example of a base station and user equipment (UE) in an access network.
FIG. 4A is a diagram illustrating an example beam management.
FIG. 4B is a diagram illustrating an example inter-cell beam management.
FIG. 5 is a diagram illustrating an example cell configuration.
FIG. 6 is a diagram illustrating a system model of an example cell configuration.
FIG. 7 is a diagram illustrating an example LTM measurement configuration in accordance with various aspects of the present disclosure.
FIG. 8 is a diagram illustrating an example configuration of inter-frequency RS set for LTM in accordance with various aspects of the present disclosure.
FIG. 9 is a diagram illustrating an example LTM measurement object configuration in accordance with various aspects of the present disclosure.
FIG. 10 is a diagram illustrating an example configuration of inter-frequency RS set for LTM in accordance with various aspects of the present disclosure.
FIG. 11 is a diagram illustrating an example LTM measurement configuration in accordance with various aspects of the present disclosure.
FIG. 12 is a diagram illustrating an example configuration of inter-frequency RS set for LTM in accordance with various aspects of the present disclosure.
FIG. 13 is a diagram illustrating an example LTM measurement configuration in accordance with various aspects of the present disclosure.
FIG. 14 is a call flow diagram illustrating a method of wireless communication in accordance with various aspects of the present disclosure.
FIG. 15 is a flowchart illustrating methods of wireless communication at a UE in accordance with various aspects of the present disclosure.
FIG. 16 is a flowchart illustrating methods of wireless communication at a UE in accordance with various aspects of the present disclosure.
FIG. 17 is a flowchart illustrating methods of wireless communication at a network entity in accordance with various aspects of the present disclosure.
FIG. 18 is a flowchart illustrating methods of wireless communication at a network entity in accordance with various aspects of the present disclosure.
FIG. 19 is a diagram illustrating an example of a hardware implementation for an example apparatus and/or network entity.
FIG. 20 is a diagram illustrating an example of a hardware implementation for an example network entity.

DETAILED DESCRIPTION

Various aspects relate generally to communication systems. Some aspects more specifically relate to L1 inter-frequency measurement configuration in LTM for wireless communication. In some examples, a UE may obtain a first configuration of a channel measurement resource set including one or more RSs for LTM, where the channel measurement resource set is associated with an L1 CSI report and includes one or more reference IDs for the one or more RSs; and perform at least one measurement for LTM based on the one or more RSs.
Particular aspects of the subject matter described in this disclosure can be implemented to realize one or more of the following potential advantages. In some examples, by configuring a first configuration of a channel measurement resource set including one or more RSs for LTM, where the channel measurement resource set is associated with an L1 CSI report and includes one or more reference IDs for the one or more RSs, the described techniques can be used to support inter-frequency RS configurations for LTM measurements. It enhances the flexibility of inter-frequency LTM measurements and improves the efficiency of wireless communication. In some aspects, radio resource control (RRC) configuration structures may be reused to support the inter-frequency RS configuration, which may not be a part of the RRC configuration for a candidate cell. In this case, the UE may not need to validate the RRC configuration for a candidate cell before the cell switching. Thus the pre-validation of the candidate cell’s RRC configurations is not necessary.
The detailed description set forth below in connection with the drawings describes various configurations and does not represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of various concepts. However, these concepts may be practiced without these specific details. In some instances, well known structures and components are shown in block diagram form in order to avoid obscuring such concepts.
Several aspects of telecommunication systems are presented with reference to various apparatus and methods. These apparatus and methods are described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as “elements” ) . These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.
By way of example, an element, or any portion of an element, or any combination of elements may be implemented as a “processing system” that includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs) , central processing units (CPUs) , application processors, digital signal processors (DSPs) , reduced instruction set computing (RISC) processors, systems on a chip (SoC) , baseband processors, field programmable gate arrays (FPGAs) , programmable logic devices (PLDs) , state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure. One or more processors in the processing system may execute software. Software, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise, shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, or any combination thereof.
Accordingly, in one or more example aspects, implementations, and/or use cases, the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored on or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media includes computer storage media. Storage media may be any available media that can be accessed by a computer. By way of example, such computer-readable media can include a random-access memory (RAM) , a read-only memory (ROM) , an electrically erasable programmable ROM (EEPROM) , optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of the types of computer-readable media, or any other medium that can be used to store computer executable code in the form of instructions or data structures that can be accessed by a computer.
While aspects, implementations, and/or use cases are described in this application by illustration to some examples, additional or different aspects, implementations and/or use cases may come about in many different arrangements and scenarios. Aspects, implementations, and/or use cases described herein may be implemented across many differing platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, aspects, implementations, and/or use cases may come about via integrated chip implementations and other non-module-component based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail/purchasing devices, medical devices, artificial intelligence (AI) -enabled devices, etc. ) . While some examples may or may not be specifically directed to use cases or applications, a wide assortment of applicability of described examples may occur. Aspects, implementations, and/or use cases may range a spectrum from chip-level or modular components to non-modular, non-chip-level implementations and further to aggregate, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more techniques herein. In some practical settings, devices incorporating described aspects and features may also include additional components and features for implementation and practice of claimed and described aspect. For example, transmission and reception of wireless signals necessarily includes a number of components for analog and digital purposes (e.g., hardware components including antenna, RF-chains, power amplifiers, modulators, buffer, processor (s) , interleaver, adders/summers, etc. ) . Techniques described herein may be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc. of varying sizes, shapes, and constitution.
Deployment of communication systems, such as 5G NR systems, may be arranged in multiple manners with various components or constituent parts. In a 5G NR system, or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element, or a network equipment, such as a base station (BS) , or one or more units (or one or more components) performing base station functionality, may be implemented in an aggregated or disaggregated architecture. For example, a BS (such as a Node B (NB) , evolved NB (eNB) , NR BS, 5G NB, access point (AP) , a transmission reception point (TRP) , or a cell, etc. ) may be implemented as an aggregated base station (also known as a standalone BS or a monolithic BS) or a disaggregated base station.
An aggregated base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A disaggregated base station may be configured to utilize a protocol stack that is physically or logically distributed among two or more units (such as one or more central or centralized units (CUs) , one or more distributed units (DUs) , or one or more radio units (RUs) ) . In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed throughout one or multiple other RAN nodes. The DUs may be implemented to communicate with one or more RUs. Each of the CU, DU and RU can be implemented as virtual units, i.e., a virtual central unit (VCU) , a virtual distributed unit (VDU) , or a virtual radio unit (VRU) .
Base station operation or network design may consider aggregation characteristics of base station functionality. For example, disaggregated base stations may be utilized in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (such as the network configuration sponsored by the O-RAN Alliance) ) , or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN) ) . Disaggregation may include distributing functionality across two or more units at various physical locations, as well as distributing functionality for at least one unit virtually, which can enable flexibility in network design. The various units of the disaggregated base station, or disaggregated RAN architecture, can be configured for wired or wireless communication with at least one other unit.
FIG. 1 is a diagram 100 illustrating an example of a wireless communications system and an access network. The illustrated wireless communications system includes a disaggregated base station architecture. The disaggregated base station architecture may include one or more CUs 110 that can communicate directly with a core network 120 via a backhaul link, or indirectly with the core network 120 through one or more disaggregated base station units (such as a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC) 125 via an E2 link, or a Non-Real Time (Non-RT) RIC 115 associated with a Service Management and Orchestration (SMO) Framework 105, or both) . A CU 110 may communicate with one or more DUs 130 via respective midhaul links, such as an F1 interface. The DUs 130 may communicate with one or more RUs 140 via respective fronthaul links. The RUs 140 may communicate with respective UEs 104 via one or more radio frequency (RF) access links. In some implementations, the UE 104 may be simultaneously served by multiple RUs 140.
Each of the units, i.e., the CUs 110, the DUs 130, the RUs 140, as well as the Near-RT RICs 125, the Non-RT RICs 115, and the SMO Framework 105, may include one or more interfaces or be coupled to one or more interfaces configured to receive or to transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units, or an associated processor or controller providing instructions to the communication interfaces of the units, can be configured to communicate with one or more of the other units via the transmission medium. For example, the units can include a wired interface configured to receive or to transmit signals over a wired transmission medium to one or more of the other units. Additionally, the units can include a wireless interface, which may include a receiver, a transmitter, or a transceiver (such as an RF transceiver) , configured to receive or to transmit signals, or both, over a wireless transmission medium to one or more of the other units.
In some aspects, the CU 110 may host one or more higher layer control functions. Such control functions can include radio resource control (RRC) , packet data convergence protocol (PDCP) , service data adaptation protocol (SDAP) , or the like. Each control function can be implemented with an interface configured to communicate signals with other control functions hosted by the CU 110. The CU 110 may be configured to handle user plane functionality (i.e., Central Unit –User Plane (CU-UP) ) , control plane functionality (i.e., Central Unit –Control Plane (CU-CP) ) , or a combination thereof. In some implementations, the CU 110 can be logically split into one or more CU-UP units and one or more CU-CP units. The CU-UP unit can communicate bidirectionally with the CU-CP unit via an interface, such as an E1 interface when implemented in an O-RAN configuration. The CU 110 can be implemented to communicate with the DU 130, as necessary, for network control and signaling.
The DU 130 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs 140. In some aspects, the DU 130 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation, demodulation, or the like) depending, at least in part, on a functional split, such as those defined by 3GPP. In some aspects, the DU 130 may further host one or more low PHY layers. Each layer (or module) can be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 130, or with the control functions hosted by the CU 110.
Lower-layer functionality can be implemented by one or more RUs 140. In some deployments, an RU 140, controlled by a DU 130, may correspond to a logical node that hosts RF processing functions, or low-PHY layer functions (such as performing fast Fourier transform (FFT) , inverse FFT (iFFT) , digital beamforming, physical random access channel (PRACH) extraction and filtering, or the like) , or both, based at least in part on the functional split, such as a lower layer functional split. In such an architecture, the RU (s) 140 can be implemented to handle over the air (OTA) communication with one or more UEs 104. In some implementations, real-time and non-real-time aspects of control and user plane communication with the RU (s) 140 can be controlled by the corresponding DU 130. In some scenarios, this configuration can enable the DU (s) 130 and the CU 110 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.
The SMO Framework 105 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO Framework 105 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements that may be managed via an operations and maintenance interface (such as an O1 interface) . For virtualized network elements, the SMO Framework 105 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 190) to perform network element life cycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an O2 interface) . Such virtualized network elements can include, but are not limited to, CUs 110, DUs 130, RUs 140 and Near-RT RICs 125. In some implementations, the SMO Framework 105 can communicate with a hardware aspect of a 4G RAN, such as an open eNB (O- eNB) 111, via an O1 interface. Additionally, in some implementations, the SMO Framework 105 can communicate directly with one or more RUs 140 via an O1 interface. The SMO Framework 105 also may include a Non-RT RIC 115 configured to support functionality of the SMO Framework 105.
The Non-RT RIC 115 may be configured to include a logical function that enables non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) /machine learning (ML) (AI/ML) workflows including model training and updates, or policy-based guidance of applications/features in the Near-RT RIC 125. The Non-RT RIC 115 may be coupled to or communicate with (such as via an A1 interface) the Near-RT RIC 125. The Near-RT RIC 125 may be configured to include a logical function that enables near-real-time control and optimization of RAN elements and resources via data collection and actions over an interface (such as via an E2 interface) connecting one or more CUs 110, one or more DUs 130, or both, as well as an O-eNB, with the Near-RT RIC 125.
In some implementations, to generate AI/ML models to be deployed in the Near-RT RIC 125, the Non-RT RIC 115 may receive parameters or external enrichment information from external servers. Such information may be utilized by the Near-RT RIC 125 and may be received at the SMO Framework 105 or the Non-RT RIC 115 from non-network data sources or from network functions. In some examples, the Non-RT RIC 115 or the Near-RT RIC 125 may be configured to tune RAN behavior or performance. For example, the Non-RT RIC 115 may monitor long-term trends and patterns for performance and employ AI/ML models to perform corrective actions through the SMO Framework 105 (such as reconfiguration via O1) or via creation of RAN management policies (such as A1 policies) .
At least one of the CU 110, the DU 130, and the RU 140 may be referred to as a base station 102. Accordingly, a base station 102 may include one or more of the CU 110, the DU 130, and the RU 140 (each component indicated with dotted lines to signify that each component may or may not be included in the base station 102) . The base station 102 provides an access point to the core network 120 for a UE 104. The base station 102 may include macrocells (high power cellular base station) and/or small cells (low power cellular base station) . The small cells include femtocells, picocells, and microcells. A network that includes both small cell and macrocells may be known as a heterogeneous network. A heterogeneous network may also include Home Evolved Node Bs (eNBs) (HeNBs) , which may provide service to a restricted group known as a closed subscriber group (CSG) . The communication links between the RUs 140 and the UEs 104 may include uplink (UL) (also referred to as reverse link) transmissions from a UE 104 to an RU 140 and/or downlink (DL) (also referred to as forward link) transmissions from an RU 140 to a UE 104. The communication links may use multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and/or transmit diversity. The communication links may be through one or more carriers. The base station 102 /UEs 104 may use spectrum up to Y MHz (e.g., 5, 10, 15, 20, 100, 400, etc. MHz) bandwidth per carrier allocated in a carrier aggregation of up to a total of Yx MHz (x component carriers) used for transmission in each direction. The carriers may or may not be adjacent to each other. Allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL than for UL) . The component carriers may include a primary component carrier and one or more secondary component carriers. A primary component carrier may be referred to as a primary cell (PCell) and a secondary component carrier may be referred to as a secondary cell (SCell) .
Certain UEs 104 may communicate with each other using device-to-device (D2D) communication link 158. The D2D communication link 158 may use the DL/UL wireless wide area network (WWAN) spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH) , a physical sidelink discovery channel (PSDCH) , a physical sidelink shared channel (PSSCH) , and a physical sidelink control channel (PSCCH) . D2D communication may be through a variety of wireless D2D communications systems, such as for example, Bluetooth, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.
The wireless communications system may further include a Wi-Fi AP 150 in communication with UEs 104 (also referred to as Wi-Fi stations (STAs) ) via communication link 154, e.g., in a 5 GHz unlicensed frequency spectrum or the like. When communicating in an unlicensed frequency spectrum, the UEs 104 /AP 150 may perform a clear channel assessment (CCA) prior to communicating in order to determine whether the channel is available.
The electromagnetic spectrum is often subdivided, based on frequency/wavelength, into various classes, bands, channels, etc. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz –7.125 GHz) and FR2 (24.25 GHz –52.6 GHz) . Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as a “sub-6 GHz” band in various documents and articles. A similar nomenclature issue sometimes occurs with regard to FR2, which is often referred to (interchangeably) as a “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz –300 GHz) which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band.
The frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR studies have identified an operating band for these mid-band frequencies as frequency range designation FR3 (7.125 GHz –24.25 GHz) . Frequency bands falling within FR3 may inherit FR1 characteristics and/or FR2 characteristics, and thus may effectively extend features of FR1 and/or FR2 into mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR2-2 (52.6 GHz –71 GHz) , FR4 (71 GHz –114.25 GHz) , and FR5 (114.25 GHz –300 GHz) . Each of these higher frequency bands falls within the EHF band.
With the above aspects in mind, unless specifically stated otherwise, the term “sub-6 GHz” or the like if used herein may broadly represent frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. Further, unless specifically stated otherwise, the term “millimeter wave” or the like if used herein may broadly represent frequencies that may include mid-band frequencies, may be within FR2, FR4, FR2-2, and/or FR5, or may be within the EHF band.
The base station 102 and the UE 104 may each include a plurality of antennas, such as antenna elements, antenna panels, and/or antenna arrays to facilitate beamforming. The base station 102 may transmit a beamformed signal 182 to the UE 104 in one or more transmit directions. The UE 104 may receive the beamformed signal from the base station 102 in one or more receive directions. The UE 104 may also transmit a beamformed signal 184 to the base station 102 in one or more transmit directions. The base station 102 may receive the beamformed signal from the UE 104 in one or more receive directions. The base station 102 /UE 104 may perform beam training to determine the best receive and transmit directions for each of the base station 102 /UE 104. The transmit and receive directions for the base station 102 may or may not be the same. The transmit and receive directions for the UE 104 may or may not be the same.
The base station 102 may include and/or be referred to as a gNB, Node B, eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS) , an extended service set (ESS) , a TRP, network node, network entity, network equipment, or some other suitable terminology. The base station 102 can be implemented as an integrated access and backhaul (IAB) node, a relay node, a sidelink node, an aggregated (monolithic) base station with a baseband unit (BBU) (including a CU and a DU) and an RU, or as a disaggregated base station including one or more of a CU, a DU, and/or an RU. The set of base stations, which may include disaggregated base stations and/or aggregated base stations, may be referred to as next generation (NG) RAN (NG-RAN) .
The core network 120 may include an Access and Mobility Management Function (AMF) 161, a Session Management Function (SMF) 162, a User Plane Function (UPF) 163, a Unified Data Management (UDM) 164, one or more location servers 168, and other functional entities. The AMF 161 is the control node that processes the signaling between the UEs 104 and the core network 120. The AMF 161 supports registration management, connection management, mobility management, and other functions. The SMF 162 supports session management and other functions. The UPF 163 supports packet routing, packet forwarding, and other functions. The UDM 164 supports the generation of authentication and key agreement (AKA) credentials, user identification handling, access authorization, and subscription management. The one or more location servers 168 are illustrated as including a Gateway Mobile Location Center (GMLC) 165 and a Location Management Function (LMF) 166. However, generally, the one or more location servers 168 may include one or more location/positioning servers, which may include one or more of the GMLC 165, the LMF 166, a position determination entity (PDE) , a serving mobile location center (SMLC) , a mobile positioning center (MPC) , or the like. The GMLC 165 and the LMF 166 support UE location services. The GMLC 165 provides an interface for clients/applications (e.g., emergency services) for accessing UE positioning information. The LMF 166 receives measurements and assistance information from the NG-RAN and the UE 104 via the AMF 161 to compute the position of the UE 104. The NG-RAN may utilize one or more positioning methods in order to determine the position of the UE 104. Positioning the UE 104 may involve signal measurements, a position estimate, and an optional velocity computation based on the measurements. The signal measurements may be made by the UE 104 and/or the base station 102 serving the UE 104. The signals measured may be based on one or more of a satellite positioning system (SPS) 170 (e.g., one or more of a Global Navigation Satellite System (GNSS) , global position system (GPS) , non-terrestrial network (NTN) , or other satellite position/location system) , LTE signals, wireless local area network (WLAN) signals, Bluetooth signals, a terrestrial beacon system (TBS) , sensor-based information (e.g., barometric pressure sensor, motion sensor) , NR enhanced cell ID (NR E-CID) methods, NR signals (e.g., multi-round trip time (Multi-RTT) , DL angle-of-departure (DL-AoD) , DL time difference of arrival (DL-TDOA) , UL time difference of arrival (UL-TDOA) , and UL angle-of-arrival (UL-AoA) positioning) , and/or other systems/signals/sensors.
Examples of UEs 104 include a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA) , a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player) , a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor/actuator, a display, or any other similar functioning device. Some of the UEs 104 may be referred to as IoT devices (e.g., parking meter, gas pump, toaster, vehicles, heart monitor, etc. ) . The UE 104 may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology. In some scenarios, the term UE may also apply to one or more companion devices such as in a device constellation arrangement. One or more of these devices may collectively access the network and/or individually access the network.
Referring again to FIG. 1, in certain aspects, the UE 104 may include an inter-frequency measurement configuration component 198. The inter-frequency measurement configuration component 198 may be configured to obtain a first configuration of a channel measurement resource set including one or more RSs for LTM, where the channel measurement resource set is associated with an L1 CSI report and includes one or more reference IDs for the one or more RSs; and perform at least one measurement for LTM based on the one or more RSs. In certain aspects, the base station 102 may include an inter-frequency measurement configuration component 199. The inter-frequency measurement configuration component 199 may be configured to configure, for a UE, a first configuration of a channel measurement resource set including one or more RSs for LTM, where the channel measurement resource set is associated with an L1 CSI report and includes one or more reference IDs for the one or more RSs; and receive, from the UE, at least one measurement for LTM based on the one or more RSs. Although the following description may be focused on 5G NR, the concepts described herein may be applicable to other similar areas, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.
FIG. 2A is a diagram 200 illustrating an example of a first subframe within a 5G NR frame structure. FIG. 2B is a diagram 230 illustrating an example of DL channels within a 5G NR subframe. FIG. 2C is a diagram 250 illustrating an example of a second subframe within a 5G NR frame structure. FIG. 2D is a diagram 280 illustrating an example of UL channels within a 5G NR subframe. The 5G NR frame structure may be frequency division duplexed (FDD) in which for a particular set of subcarriers (carrier system bandwidth) , subframes within the set of subcarriers are dedicated for either DL or UL, or may be time division duplexed (TDD) in which for a particular set of subcarriers (carrier system bandwidth) , subframes within the set of subcarriers are dedicated for both DL and UL. In the examples provided by FIGs. 2A, 2C, the 5G NR frame structure is assumed to be TDD, with subframe 4 being configured with slot format 28 (with mostly DL) , where D is DL, U is UL, and F is flexible for use between DL/UL, and subframe 3 being configured with slot format 1 (with all UL) . While subframes 3, 4 are shown with slot formats 1, 28, respectively, any particular subframe may be configured with any of the various available slot formats 0-61. Slot formats 0, 1 are all DL, UL, respectively. Other slot formats 2-61 include a mix of DL, UL, and flexible symbols. UEs are configured with the slot format (dynamically through DL control information (DCI) , or semi-statically/statically through radio resource control (RRC) signaling) through a received slot format indicator (SFI) . Note that the description infra applies also to a 5G NR frame structure that is TDD.
FIGs. 2A-2D illustrate a frame structure, and the aspects of the present disclosure may be applicable to other wireless communication technologies, which may have a different frame structure and/or different channels. A frame (10 ms) may be divided into 10 equally sized subframes (1 ms) . Each subframe may include one or more time slots. Subframes may also include mini-slots, which may include 7, 4, or 2 symbols. Each slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended. For normal CP, each slot may include 14 symbols, and for extended CP, each slot may include 12 symbols. The symbols on DL may be CP orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbols. The symbols on UL may be CP-OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbols (for power limited scenarios; limited to a single stream transmission) . The number of slots within a subframe is based on the CP and the numerology. The numerology defines the subcarrier spacing (SCS) (see Table 1) . The symbol length/duration may scale with 1/SCS.
Table 1: Numerology, SCS, and CP
For normal CP (14 symbols/slot) , different numerologies μ 0 to 4 allow for 1, 2, 4, 8, and 16 slots, respectively, per subframe. For extended CP, the numerology 2 allows for 4 slots per subframe. Accordingly, for normal CP and numerology μ, there are 14 symbols/slot and 2^μ slots/subframe. The subcarrier spacing may be equal to 2^μ* 15 kHz, where μ is the numerology 0 to 4. As such, the numerology μ=0 has a subcarrier spacing of 15 kHz and the numerology μ=4 has a subcarrier spacing of 240 kHz. The symbol length/duration is inversely related to the subcarrier spacing. FIGs. 2A-2D provide an example of normal CP with 14 symbols per slot and numerology μ=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within a set of frames, there may be one or more different bandwidth parts (BWPs) (see FIG. 2B) that are frequency division multiplexed. Each BWP may have a particular numerology and CP (normal or extended) .
A resource grid may be used to represent the frame structure. Each time slot includes a resource block (RB) (also referred to as physical RBs (PRBs) ) that extends 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs) . The number of bits carried by each RE depends on the modulation scheme.
As illustrated in FIG. 2A, some of the REs carry reference (pilot) signals (RS) for the UE.The RS may include demodulation RS (DM-RS) (indicated as R for one particular configuration, but other DM-RS configurations are possible) and channel state information reference signals (CSI-RS) for channel estimation at the UE. The RS may also include beam measurement RS (BRS) , beam refinement RS (BRRS) , and phase tracking RS (PT-RS) .
FIG. 2B illustrates an example of various DL channels within a subframe of a frame. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs) , each CCE including six RE groups (REGs) , each REG including 12 consecutive REs in an OFDM symbol of an RB. A PDCCH within one BWP may be referred to as a control resource set (CORESET) . A UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., common search space, UE-specific search space) during PDCCH monitoring occasions on the CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at greater and/or lower frequencies across the channel bandwidth. A primary synchronization signal (PSS) may be within symbol 2 of particular subframes of a frame. The PSS is used by a UE 104 to determine subframe/symbol timing and a physical layer identity. A secondary synchronization signal (SSS) may be within symbol 4 of particular subframes of a frame. The SSS is used by a UE to determine a physical layer cell identity group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine a physical cell identifier (PCI) . Based on the PCI, the UE can determine the locations of the DM-RS. The physical broadcast channel (PBCH) , which carries a master information block (MIB) , may be logically grouped with the PSS and SSS to form a synchronization signal (SS) /PBCH block (also referred to as SS block (SSB) ) . The MIB provides a number of RBs in the system bandwidth and a system frame number (SFN) . The physical downlink shared channel (PDSCH) carries user data, broadcast system information not transmitted through the PBCH such as system information blocks (SIBs) , and paging messages.
As illustrated in FIG. 2C, some of the REs carry DM-RS (indicated as R for one particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may transmit DM-RS for the physical uplink control channel (PUCCH) and DM-RS for the physical uplink shared channel (PUSCH) . The PUSCH DM-RS may be transmitted in the first one or two symbols of the PUSCH. The PUCCH DM-RS may be transmitted in different configurations depending on whether short or long PUCCHs are transmitted and depending on the particular PUCCH format used. The UE may transmit sounding reference signals (SRS) . The SRS may be transmitted in the last symbol of a subframe. The SRS may have a comb structure, and a UE may transmit SRS on one of the combs. The SRS may be used by a base station for channel quality estimation to enable frequency-dependent scheduling on the UL.
FIG. 2D illustrates an example of various UL channels within a subframe of a frame. The PUCCH may be located as indicated in one configuration. The PUCCH carries uplink control information (UCI) , such as scheduling requests, a channel quality indicator (CQI) , a precoding matrix indicator (PMI) , a rank indicator (RI) , and hybrid automatic repeat request (HARQ) acknowledgment (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACK and/or negative ACK (NACK) ) . The PUSCH carries data, and may additionally be used to carry a buffer status report (BSR) , a power headroom report (PHR) , and/or UCI.
FIG. 3 is a block diagram of a base station 310 in communication with a UE 350 in an access network. In the DL, Internet protocol (IP) packets may be provided to a controller/processor 375. The controller/processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller/processor 375 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIBs) , RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release) , inter radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (ciphering, deciphering, integrity protection, integrity verification) , and handover support functions; RLC layer functionality associated with the transfer of upper layer packet data units (PDUs) , error correction through ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs) , re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs) , demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.
The transmit (TX) processor 316 and the receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1, which includes a physical (PHY) layer, may include error detection on the transport channels, forward error correction (FEC) coding/decoding of the transport channels, interleaving, rate matching, mapping onto physical channels, modulation/demodulation of physical channels, and MIMO antenna processing. The TX processor 316 handles mapping to signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK) , quadrature phase-shift keying (QPSK) , M-phase-shift keying (M-PSK) , M-quadrature amplitude modulation (M-QAM) ) . The coded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and/or frequency domain, and then combined together using an Inverse Fast Fourier Transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially precoded to produce multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation scheme, as well as for spatial processing. The channel estimate may be derived from a reference signal and/or channel condition feedback transmitted by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx may modulate a radio frequency (RF) carrier with a respective spatial stream for transmission.
At the UE 350, each receiver 354Rx receives a signal through its respective antenna 352. Each receiver 354Rx recovers information modulated onto an RF carrier and provides the information to the receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions. The RX processor 356 may perform spatial processing on the information to recover any spatial streams destined for the UE 350. If multiple spatial streams are destined for the UE 350, they may be combined by the RX processor 356 into a single OFDM symbol stream. The RX processor 356 then converts the OFDM symbol stream from the time-domain to the frequency domain using a Fast Fourier Transform (FFT) . The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, and the reference signal, are recovered and demodulated by determining the most likely signal constellation points transmitted by the base station 310. These soft decisions may be based on channel estimates computed by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals that were originally transmitted by the base station 310 on the physical channel. The data and control signals are then provided to the controller/processor 359, which implements layer 3 and layer 2 functionality.
The controller/processor 359 can be associated with a memory 360 that stores program codes and data. The memory 360 may be referred to as a computer-readable medium. In the UL, the controller/processor 359 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, and control signal processing to recover IP packets. The controller/processor 359 is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations.
Similar to the functionality described in connection with the DL transmission by the base station 310, the controller/processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIBs) acquisition, RRC connections, and measurement reporting; PDCP layer functionality associated with header compression /decompression, and security (ciphering, deciphering, integrity protection, integrity verification) ; RLC layer functionality associated with the transfer of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.
Channel estimates derived by a channel estimator 358 from a reference signal or feedback transmitted by the base station 310 may be used by the TX processor 368 to select the appropriate coding and modulation schemes, and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antenna 352 via separate transmitters 354Tx. Each transmitter 354Tx may modulate an RF carrier with a respective spatial stream for transmission.
The UL transmission is processed at the base station 310 in a manner similar to that described in connection with the receiver function at the UE 350. Each receiver 318Rx receives a signal through its respective antenna 320. Each receiver 318Rx recovers information modulated onto an RF carrier and provides the information to a RX processor 370.
The controller/processor 375 can be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer-readable medium. In the UL, the controller/processor 375 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover IP packets. The controller/processor 375 is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations.
At least one of the TX processor 368, the RX processor 356, and the controller/processor 359 may be configured to perform aspects in connection with the inter-frequency measurement configuration component 198 of FIG. 1.
At least one of the TX processor 316, the RX processor 370, and the controller/processor 375 may be configured to perform aspects in connection with the inter-frequency measurement configuration component 199 of FIG. 1.
A network may be in communication with a UE based on one or more beams (spatial filters) . For example, a base station of the network may transmit a beamformed signal to a UE in one or more directions that correspond with one or more beams. The base station and the UE may perform beam training to determine the best receive and transmit beam directions for the base station and the UE.
In response to different conditions, beams may be switched. For example, a TCI state change may be transmitted by a base station so that the UE may switch to a new beam for the TCI state. The TCI state change may cause the UE to find the best UE receive beam corresponding to the TCI state from the base station, and switch to such beam. Switching beams may allow for enhanced or improved connection between the UE and the base station by ensuring that the transmitter and receiver use the same configured set of beams for communication. A TCI state may include quasi-co-location (QCL) information that the UE can use to derive timing/frequency error and/or transmission/reception spatial filtering for transmitting/receiving a signal.
Different procedures for managing and controlling beams may be collectively referred to as “beam management. ” The process of selecting a beam to switch to for data channels or control channels may be referred to as “beam selection. ” In some wireless communication systems, beam selection for data channels or control channels may be limited to beams within the same physical cell identifier (ID) (PCI) . A PCI may be associated with a TRP. FIG. 4A is a diagram 400 illustrating an example of beam management. As illustrated in FIG. 4A, for a UE 402, beam selection 406 may be limited to beams within the PCI 404A and beams associated with the PCI 404B and the PCI 404C may not be used. As an example, each of the PCI 404A, the PCI 404B, and the PCI 404C may be associated with a different TRP.
By way of example, a UE may encounter two types of mobility –cell-level mobility and beam-level mobility (which may be beam-based mobility) . For cell-level mobility, a UE may experience an inter-base station handover. In some wireless communication systems, for beam-level mobility, as previously explained, switching of beams may occur within the same base station.
In some wireless communication systems, inter-cell beam management may be based on beam-based mobility where the indicated beam may be from a TRP with different PCI with regard to the serving cell. Benefits of inter-cell beam management based on beam-based mobility may include more robustness against blocking, more opportunities for higher rank for subscriber data management (SDM) across different cells, and in general more efficient communication between a UE and the network. FIG. 4B is a diagram 450 illustrating an example of inter-cell beam management. As illustrated in FIG. 4B, for a UE 452, beam selection 456 may be based on beams within the PCI 454A and beams associated with the PCI 454B and the PCI 454C. As an example, each of the PCI 454A, the PCI 454B, and the PCI 454C may be associated with a different TRP.
As an example, inter-cell beam management based on beam-based mobility may be facilitated by L1 and/or L2 (L1/L2) signaling, such as UE-dedicated channels/RSs, which may be associated with a switch to a TRP with different PCI according to downlink control information (DCI) or medium access control (MAC) control element (MAC-CE) based unified TCI update. As used herein, such mobility may be referred to as L1/L2 mobility (lower-layer triggered mobility (LTM) ) .
In some aspects, the network may configure a set of cells for L1/L2 mobility or LTM. The set of cells for L1/L2 mobility may be referred to as L1/L2 mobility configured cell set or an LTM configured cell set. A subset of the L1/L2 mobility configured cell set may be activated (e.g., with L1 or L2 control signaling) and may be referred to as an L1/L2 mobility activated cell set (which may also be referred to as an L1/L2 activated mobility cell set or LTM activated cell set) . The subset of the L1/L2 mobility configured cell set that is not activated or that is indicated to be deactivated may be referred to as an L1/L2 mobility deactivated cell set or a deactivated L1/L2 mobility cell set or an LTM deactivated cell set. The L1/L2 mobility activated cell set may be a group of cells in the L1/L2 mobility configured cell set that are activated and may be readily used for data and control transfer. The L1/L2 mobility deactivated cell set (which may be an L1/L2 mobility candidate cell set) may be a group of cells in the configured set that is configured for the UE yet deactivated (e.g., not used for data/control transfer until activated) and may be activated by L1/L2 signaling. Once activated, a deactivated cell may be used for data and control transfer. The configuration and maintenance of multiple candidate cells may allow for a quicker application of configurations for the candidate cells, and the activated set of cells may provide for dynamic switching among the candidate serving cells (e.g., including a special cell (SpCell) and SCell) based on L1 or L2 signaling.
The procedures of L1/L2 based inter-cell mobility or LTM are applicable to many scenarios. These scenarios may include standalone CA and NR-DC cases with serving cell changing within one CG, intra-DU cases and intra-CU inter-DU cases (applicable for standalone and CA, with no new RAN interface expected) , intra-frequency and inter-frequency cases, FR1 and FR2 cases. In these scenarios, the source and target cells may be synchronized or non-synchronized.
For mobility management of the activated cell set, L1/L2 signaling may be used to activate/deactivate cells in the L1/L2 mobility configured cell set and to select beams within the activated cells (of the activated cell set) . As the UE moves, cells from the L1/L2 mobility configured cell set may be deactivated and activated by L1/L2 signaling based on signal quality (e.g., based on measurements) , loading, or the like. Example measurements may include cell coverage measurements represented by Radio Signal Received Power (RSRP) , and quality represented by Radio Signal Received Quality (RSRQ) , or other measurements that the UE performs on signals from the base station. In some aspects, the measurements may be L1 measurements, such as one or more of an RSRP, an RSRQ, a received signal strength indicator (RSSI) , or a signal-to-interference plus noise ratio (SINR) measurement of various signals, such as an SSB, a PSS, an SSS, a broadcast channel (BCH) , a DM-RS, CSI-RS, or the like. As used herein, an “L1 measurement” may refer to a measurement used for Layer 1 (rather than any other layers, such as layer 3) , an “L1 inter-frequency measurement” may refer to an L1 measurement having a different frequency and/or subcarrier spacing with that of the active serving cell, and an “L1 inter-frequency measurement configuration” may refer to a configuration for performing an L1 inter-frequency measurement.
In some aspects, all cells in the L1/L2 mobility configured cell set may belong to the same DU and the cells may be on the same or different carrier frequencies. Cells in the L1/L2 mobility configured cell set may cover a mobility area.
FIG. 5 is a diagram 500 illustrating an example of cell configuration. As illustrated in FIG. 5, a CU 502 (which may correspond to a component of a base station such as a gNB) may be associated with a first DU 504 (and other DUs) . An L1/L2 mobility configured cell set 506 may be associated with the first DU 504 and may include an L1/L2 mobility activated cell set 508 and an L1/L2 mobility deactivated cell set 510. The L1/L2 mobility configured cell set 506 may also include one or more cells not in the current L1/L2 mobility activated cell set 508 or the current L1/L2 mobility deactivated cell set 510. For example, at a given time, the L1/L2 mobility activated cell set 508 may include a first subset of the L1/L2 mobility configured cell set, and the L1/L2 mobility deactivated cell set 510 may include a second, non-overlapping subset of the L1/L2 mobility configured cell set. There may remain one or more cells that are in the L1/L2 mobility configured cell set that are not in the first set subset (e.g., activated) or the second subset (e.g., deactivated) . A UE 512 may use the cells in the L1/L2 mobility activated cell set 508 for data channel and control channel communications.
A UE may be provided with a subset of L1/L2 mobility deactivated cells (candidate cell set) that the UE may autonomously choose to add to the L1/L2 mobility activated cell set. For example, the UE may add cells in the subset of L1/L2 mobility deactivated cells to the L1/L2 mobility activated cell set based on measurements (e.g., measured channel quality) , loading, or the like. In some aspects, each of the RUs could have multi-component carrier (CC) (N CCs) support (where each CC is a cell) . In some aspects, activation or deactivation may be performed for groups of carriers (cells) . For PCell management, L1/L2 signaling may be used to set the PCell out of the configured options within the activated cell set. In some aspects, L3 mobility may be used for PCell change (L3 handover) when a new PCell is not from the activated cell set for L1/L2 mobility. As an example, RRC signaling may be used to update the set of cells for L1/L2 mobility at L3 handover. In some aspects, L1/L2 mobility configured cells may be associated with a PCell configuration without being the PCell. The PCell configuration may be activated and one of the L1/L2 mobility activated cells (e.g., in an L1/L2 mobility activated cell set) may be activated based on L1/L2 signaling to become a PCell. In some aspects, L1/L2 mobility deactivated cells (e.g., in an L1/L2 mobility deactivated cell set) may support L1 measurements to facilitate sufficient beam management, timing synchronization, power control, or the like. For L1/L2 mobility deactivated cells, measurement reporting may be done on an activated cell.
A network node (e.g., a base station) may change a SpCell for a UE using a layer 3 (L3) handover (e.g., using radio resource control (RRC) signaling) . However, L3 handovers may be time-consuming and/or inefficient. A network node that utilizes the improved L1/L2 signaling scheme is able to change one or more cells for a UE in a more rapid manner in comparison to L3 (RRC) based approaches. In an example, a UE receives an L1 or L2 mobility cell configuration for a set of cells for L1 or L2 inter-cell mobility. The set of cells may include multiple cells, and each cell in the set of cells is able to be activated or deactivated for data and/or control transfer using L1 or L2 signaling. The UE receives L1 or L2 signaling indicating multiple activated cells, and activates one or more cells in the multiple activated cells in a priority order for the data and/or control transfer using L1 or L2 signaling. Via the aforementioned L1 or L2 signaling, one or more cells, including SpCell and SCell, are able to be activated and/or deactivated in a manner that avoids RRC-based signaling. As a result, the cells may be activated and/or deactivated in a more rapid manner in comparison to RRC-based signaling. Additionally, the cells may be activated in a priority order to further facilitate more efficient and robust mobility management.
A base station may configure a UE, e.g., in RRC signaling, with a set of cells for L1/L2 mobility. The set of cells may be referred to as an L1/L2 mobility configured set. A subset of the cells in the configured set may be activated and can be used for data and control transfer between the UE and the network. The subset of activated cells may be referred to as the L1/L2 mobility activated cell set. A subset of the L1/L2 mobility configured set may be deactivated and may be referred to as the L1/L2 mobility deactivated set. The L1/L2 deactivated set of cells can be activated for the UE by L1/L2 signaling from the network.
In conditional handover, a set of candidate cells (including cell ID, system information, etc. ) and conditions for handover may be configured in advance via RRC. When the configured condition is met for one of the configured candidate cells, the UE may initiate the handover procedure by transmitting PRACH toward the candidate cell. The handover completion may be notified to the previous serving cell by the new serving cell. DL/UL channel between the UE and the new cell might not be immediately usable for high speed/volume traffic due to the lack of, for example, channel state information between the UE and the new cell.
For enhanced mobility, the UE may be configured with a set of candidate cells (including cell ID, system information, etc. ) in advance, and the UE may be expected to keep performing L1 and L3 measurements for the configured candidate cells. A handover toward a specific cell among the preconfigured candidate cells will be initiated via L1 and/or L2 messages. The handover allows the DL/UL channel over the new link to be immediately usable for high speed/volume traffic as soon as the handover procedure is completed. As a part of the fast handover procedure, communication is improved with a seamless UL power control mechanism. Otherwise, DL/UL transmission/reception may be delayed except for PRACH and random-access response (RAR) for UL power control initialization, even when timing advance (TA) for the new cell is obtained by other means.
FIG. 6 is a diagram 600 illustrating a system model of an example cell configuration. As shown in FIG. 6, a UE 602 may be configured with a set of cells (Cell1, …, Cell8) for L1/L2 mobility. The set of cells may be configured through radio resource control (RRC) signaling. The set of cells may be on the same frequencies, and the existing mechanism of carrier aggregation (CA) may be utilized to enable L1/L2 mobility. Cells in the configured set may be further characterized into two groups: activated cells and deactivated cells. The activated cells are serving cells that are currently active and can be used for data and control transfer. The deactivated cells are serving cells that are currently deactivated (and hence have no active data or control communication with the UE 602) but can be quickly activated through L1/L2 signaling to the UE from the network.
The UE 602 may be a mobile device and may be moving while communicating with the cells in the configured cell set. L1/L2 signaling may be used to activate/deactivate cells in the set and to select beams within the activated cells. For example, as the UE 602 moves, the serving cell may change based on, for example, the UE’s location and measurement reports using L1/L2 singling. A group of cells may be activated at one time. L1/L2 signaling may be used to set the PCell out of the configured PCell options within the activated cell set. L3 mobility may be used for PCell change (L3 handover) to a new PCell is not from the configured cell set for L1/L2 mobility, and RRC signaling may update the set of cells for L1/L2 mobility at L3 handover.
Example aspects presented herein provide methods and apparatus for measurement configurations for LTM measurements (e.g., inter-frequency LTM measurements) . In some aspects, the measurement configurations may be based on L1 CSI request signaling (e.g., CSI-meas-config and CSI-report-config configured in serving cell configuration in an active cell) for a candidate cell. In some aspects, the measurement configurations for an inter-frequency channel measurement resource setting may be based on SSB configuration structures. For example, the inter-frequency channel measurement resource setting may include one or more inter-frequency SSBs configured in an SSB measurement timing configuration window (SMTC) .
In some aspects, for LTM measurements, such as L1 measurements, a channel measurement resource set (e.g., a set of resources configured for receiving measurement signals in an RRC information element “resourcesForChannelMeasurement” ) associated with an L1 CSI report configured in active cells may include one or more inter-frequency RSs. An L1 CSI report is configured for the UE to measure and report channel information for the physical layer (Layer 1) . The inter-frequency RSs may include a set of IDs for the RSs (e.g., the RS IDs) . In some examples, the one or more inter-frequency RSs may include one or more SSBs (e.g., inter-frequency SSBs) , and the set of RS IDs may be configured for the one or more SSBs. The one or more SSBs may be configured with an SSB configuration. In some examples, the SSB configuration may include a set of SSB indexes with a single PCI ID or a set of multiple PCI IDs. In some examples, the PCI ID may be a full PCI ID (e.g., a 10-bit PCI ID) or a short PCI ID (e.g., a 2-bit local PCI index) mapping to a full PCI ID. In this disclosure, an “inter-frequency RS” may refer to an RS associated with an inter-frequency measurement. An “L1 inter-frequency RS” may refer to an RS associated with an L1 measurement but having a different frequency and/or subcarrier spacing with any of the active serving cell.
In some examples, the SSB configuration may further include the periodicity and the offset of the SSBs, which may indicate the time locations of the SSBs. The SSB configuration may further include a subset identifier identifying a subset of SSBs within the one or more SSBs, and the transmit power of the SSBs.
In some examples, the one or more SSBs may be configured with frequency information (e.g., the frequency of the SSB) and SCS information (e.g., the SCS of the SSB) associated with each SSB configuration (parameter settings of an SSB) . An RS ID reported in an L1 CSI report, which refers to an RS configured in the channel measurement setting, may be mapped to an SSB index, a PCI ID (e.g., a short PCI ID) , the frequency information, and the SCS information. In a single report, the UE may report SSBs associated with the same or different PCI IDs, SSBs associated with the same or different frequency information, and SSBs associated with the same or different SCS information.
In some aspects, a new SSB configuration may be defined. The new SSB configuration may include various information, such as a set of SSBs, a PCI, frequency information and SCS information. FIG. 7 is a diagram 700 illustrating an example LTM measurement configuration in accordance with various aspects of the present disclosure. As shown in FIG. 7, the example LTM measurement configuration may be an SSB configuration (e.g., the SSB-MTC-LTMPCI configuration 702) . The SSB configuration may include the frequency of the SSB (e.g., ssbFrequency 712) , the SCS of the SSB (e.g., ssbSubcarrierSpacing 714) , the PCI associated with the SSB (e.g., PCI 716) , and one or more SSBs (e.g., SSB 718) . In some examples, the SSB configuration may further include additional information related to the SSB, such as the periodicity and the offset of the SSBs, the transmit power of the SSBs, a time duration, and a subset identifier identifying a subset of the SSB within the set of SSBs. The SSB configuration (e.g., the SSB-MTC-LTMPIC configuration 702) may be configured under the L3 measurement configuration (e.g., at place B 706) or the serving cell configuration (e.g., at place A 704) . In the example of FIG. 7, the UE may be configured with an L1 CSI measurement configuration (e.g., csi-MeasConfig 708) , which may include an L1 CSI report configuration (csi-ReportConfig 710) . The L1 CSI report configuration may be configured with a channel measurement resource set 720. The channel measurement resource set 720 may include one or more RSs (or the IDs of the RSs) , which may include intra-frequency RSs 730 and inter-frequency RSs 740. The inter-frequency RSs 740 in the channel measurement resource set 720 may refer to the RSs in the SSB configuration (e.g., the SSB-MTC-LTMPCI configuration 702) .
FIG. 8 is a diagram 800 illustrating an example configuration of inter-frequency RS set for LTM in accordance with various aspects of the present disclosure. The example configuration of inter-frequency RS set in the channel measurement resource set 720 may be associated with the example LTM measurement configuration of FIG. 7. As shown in FIG. 8, the set of RSs 802 may represent the structure of the inter-frequency RSs 740, and the SSB configuration 804 may represent the SSB-MTC-LTMPCI configuration 702. Each RS in the set of RSs 802 (e.g., RS 0, RS 1, …, RS N-1) may have an associated SSB (e.g., SSB x) and an associated PCI (e.g., PCI mi) . Each RS in the set of RSs 802 may be configured in the SSB configuration 804.
In some examples, the SSB configuration may be based on L3 SSB-MTC configuration and L3 measurement object configuration with a single PCI. FIG. 9 is a diagram 900 illustrating an example LTM measurement object configuration. As shown in FIG. 9, the example LTM measurement object configuration (the measObject configuration 902) may include the frequency information (e.g., ssbFrequency 912) of the SSB, the SCS information (e.g., ssbSubcarrierSpacing 914) of the SSB, and SSB configuration (e.g., SSB-MTC 915) that may include one PCI ID (PCI 916) and one or more SSBs (e.g., SSB 918) . The example LTM measurement object configuration (the measObject configuration 902) may further include a measurement gap (e.g., Gap ID 917) associated with the measurements. The example LTM measurement object configuration (the measObject configuration 902) may be configured at place A 904 or place B 906.
In wireless communication, a measurement gap is a time duration reserved for a UE to perform measurements on DL signals (e.g., measurements on the signal quality of the DL signals) . The signal to be measured within a measurement gap may come from, for example, a candidate cell (e.g., a non-serving cell) of the UE, and the candidate cell may be operating on a frequency band that is the same as or different from that of the serving cell of the UE.
FIG. 10 is a diagram 1000 illustrating an example configuration of inter-frequency RS set for LTM in accordance with various aspects of the present disclosure. The example configuration of inter-frequency RS set may be associated with the example LTM measurement configuration of FIG. 9. As shown in FIG. 10, the set of RSs 1002 may represent the structure of the inter-frequency RSs 940, and the measurement object configuration 1004 may represent the measObject configuration 902. Each RS in the set of RSs 1002 (e.g., RS 0, RS 1, …, RS N-1) may have an associated SSB (e.g., SSB x) and an associated measurement object (e.g., mo mi) . Each RS in the set of RSs 1002 may be configured in the measurement object configuration 1004.
In some examples, the SSB configuration may be based on L3 SSB-MTC configuration and L3 measurement object configuration with multiple PCIs. FIG. 11 is a diagram 1100 illustrating an example LTM measurement object configuration. As shown in FIG. 1100, the example LTM measurement object configuration (the measObject configuration 1102) may include the frequency information (e.g., ssbFrequency 1112) of the SSB, the SCS information (e.g., ssbSubcarrierSpacing 1114) of the SSB, and SSB configuration (e.g., SSB-MTC 1115) that may include multiple PCI IDs (e.g., PCI list 1116) and one or more SSBs (e.g., SSB 1118) . The example LTM measurement object configuration (the measObject configuration 1102) may further include a measurement gap (e.g., Gap ID 1117) associated with the measurements. The example LTM measurement object configuration (the measObject configuration 1102) may be configured at place A 1104 or place B 1106.
FIG. 12 is a diagram 1200 illustrating an example configuration of inter-frequency RS set for LTM in accordance with various aspects of the present disclosure. The example configuration of inter-frequency RS set may be associated with the example LTM measurement configuration of FIG. 11. As shown in FIG. 12, the set of RSs 1202 may represent the structure of the inter-frequency RSs 1140, and the measurement object configuration 1204 may represent the measObject configuration 1102. Each RS in the set of RSs 1202 (e.g., RS 0, RS 1, …, RS N-1) may have an associated SSB (e.g., SSB x) , an associated measurement object (e.g., mo mi) , and an associated PCI ID (e.g., PCI ki) . Each RS in the set of RSs 1202 may be configured in the measurement object configuration 1204.
In some aspects, CSI-RS can be configured as the inter-frequency RS in an enhanced channel measurement resource set associated with an L1 CSI report configured in active cells for LTM. For example, CSI-RS for mobility can be referred to by L1 inter-frequency measurement in LTM. FIG. 13 is a diagram 1300 illustrating an example LTM measurement configuration in accordance with various aspects of the present disclosure. As shown in FIG. 13, a UE may be configured with a channel measurement resource set 1320. The channel measurement resource set 1320 may include one or more RSs (or the IDs of the RSs) , which may include intra-frequency RSs 1330 for active cells and inter-or intra-frequency RSs 1340 for candidate cells. The channel measurement resource set 1320 may further include one or more measurement gaps (referenced by Gap ID 1350) . The inter-or intra-frequency RSs 1340 in the channel measurement resource set 1320 may refer to one or more RS configurations, such as the measurement object configuration (MeasObjectLTM 1360) . For example, frequency information of the CSI-RS may be configurable at refFreqCSI-RS 1370, SCS information of the CSI-RS may be configurable at Subcarrier Spacing 1380, and CSI-RS resources may be configurable at 1390.
FIG. 14 is a call flow diagram 1400 illustrating a method of wireless communication in accordance with various aspects of this present disclosure. Although aspects are described for a base station 1404, the aspects may be performed by a base station in aggregation and/or by one or more components of a base station 1404 (e.g., such as a CU 110, a DU 130, and/or an RU 140) .
As shown in FIG. 14, a UE 1402 may obtain, at 1406, a first configuration of a channel measurement resource set including one or more RSs for LTM from base station 1404. The channel measurement resource set may be associated with an L1 CSI report and include one or more reference IDs for the one or more RSs. For example, referring to FIGs. 7, 9, and 11, a UE may obtain a first configuration of a channel measurement resource set (720, 920, or 1120) including one or more RSs (740, 940, or 1140) for LTM from a base station. The one or more RSs (740, 940, or 1140) in the channel measurement resource set (720, 920, or 1120) may be configurable through the configurations (702, 902, or 1102) .
At 1408, the UE 1402 may perform at least one measurement for LTM based on the one or more RSs. For example, referring to FIG. 7, the UE may perform at least one measurement for LTM based on the one or more RSs (e.g., SSB 718) .
At 1410, the UE 1402 may transmit at least one measurement for LTM based on the one or more RSs to base station 1404.
FIG. 15 is a flowchart 1500 illustrating methods of wireless communication at a UE in accordance with various aspects of the present disclosure. The method may be performed by a UE. The UE may be the UE 104, 350, 1402, or the apparatus 1904 in the hardware implementation of FIG. 19. By signaling to a UE with a configuration of a channel measurement resource set including one or more RSs for LTM, the method supports inter-frequency RS configurations for LTM measurements. It enhances the flexibility of inter-frequency LTM measurements and improves the efficiency of wireless communication.
As shown in FIG. 15, at 1502, the UE may obtain a first configuration of a channel measurement resource set including one or more RSs for LTM. The channel measurement resource set may be associated with an L1 CSI report and include one or more reference IDs for the one or more RSs. The network entity may be a base station, or a component of a base station, in the access network of FIG. 1 or a core network component (e.g., base station 102, 310, 1404; or the network entity 1902 in the hardware implementation of FIG. 19) . FIGs. 7, 8, 9, 10, 11, 12, 13, and 14 illustrate various aspects of the steps in connection with flowchart 1500. For example, referring to FIG. 14, the UE 1402 may obtain a first configuration of a channel measurement resource set including one or more RSs for LTM. Referring to FIGs. 7, 9, and 11, the channel measurement resource set (720, 920, or 1120) may include one or more RSs (740, 940, or 1140) for LTM. The one or more RSs (740, 940, or 1140) in the channel measurement resource set (720, 920, or 1120) may be configurable through the configurations (702, 902, or 1102) . In some aspects, 1502 may be performed by the inter-frequency measurement configuration component 198.
At 1504, the UE may perform at least one measurement for LTM based on the one or more RSs. For example, referring to FIG. 14, the UE 1402 may perform, at 1408, at least one measurement for LTM based on the one or more RSs. The one or more RSs may be SSBs (e.g., SSB 718) . In some aspects, 1504 may be performed by the inter-frequency measurement configuration component 198.
FIG. 16 is a flowchart 1600 illustrating methods of wireless communication at a UE in accordance with various aspects of the present disclosure. The method may be performed by a UE. The UE may be the UE 104, 350, 1402, or the apparatus 1904 in the hardware implementation of FIG. 19. By signaling to a UE with a configuration of a channel measurement resource set including one or more RSs for LTM, the method supports inter-frequency RS configurations for LTM measurements. It enhances the flexibility of inter-frequency LTM measurements and improves the efficiency of wireless communication.
As shown in FIG. 16, at 1602, the UE may obtain a first configuration of a channel measurement resource set including one or more RSs for LTM. The channel measurement resource set may be associated with an L1 CSI report and include one or more reference IDs for the one or more RSs. The network entity may be a base station, or a component of a base station, in the access network of FIG. 1 or a core network component (e.g., base station 102, 310, 1404; or the network entity 1902 in the hardware implementation of FIG. 19) . FIGs. 7, 8, 9, 10, 11, 12, 13, and 14 illustrate various aspects of the steps in connection with flowchart 1600. For example, referring to FIG. 14, the UE 1402 may obtain a first configuration of a channel measurement resource set including one or more RSs for LTM. Referring to FIGs. 7, 9, and 11, the channel measurement resource set (720, 920, or 1120) may include one or more RSs (740, 940, or 1140) for LTM. The one or more RSs (740, 940, or 1140) in the channel measurement resource set (720, 920, or 1120) may be configurable through the configurations (702, 902, or 1102) . In some aspects, 1602 may be performed by the inter-frequency measurement configuration component 198.
At 1604, the UE may perform at least one measurement for LTM based on the one or more RSs. For example, referring to FIG. 14, the UE 1402 may perform, at 1408, at least one measurement for LTM based on the one or more RSs. The one or more RSs may be SSBs (e.g., SSB 718) . In some aspects, 1604 may be performed by the inter-frequency measurement configuration component 198.
In some aspects, at 1606, the first configuration of the channel measurement resource set may be associated with a first network entity, and the one or more RSs may include one or more SSBs associated with a set of second network entities. For example, referring to FIG. 11, the one or more RSs may include one or more SSBs (e.g., SSBs 1118) . The one or more SSBs (e.g., SSBs 1118) may be associated with a set of second network entities (referred to by PCI list 1116) . In some aspects, 1606 may be performed by the inter-frequency measurement configuration component 198.
In some aspects, at 1608, the first network entity may operate at a first frequency band, and at least one second network entity of the set of second network entities may operate at a second frequency band different from the first frequency band. For example, referring to FIGs. 7, 9, and 11, the RSs (740, 940, and 1140) are inter-frequency RSs, indicating the first network entity and at least one second network entity of the set of second network entities operate at different frequency bands. In some aspects, 1608 may be performed by the inter-frequency measurement configuration component 198.
In some aspects, at 1610, the first configuration may include an SSB configuration associated with the one or more SSBs. The SSB configuration may include: one or more PCI IDs. The one or more PCI IDs may be associated with the set of second network entities. For example, referring to FIGs. 7, 9, and 11, the first configuration may include an SSB configuration (702, 902, and 1102) associated with the one or more SSBs (718, 918, and 1118) . The SSB configuration may include: one or more PCI IDs (716, 916, and 1116) . The one or more PCI IDs may be associated with the set of second network entities. In some aspects, 1610 may be performed by the inter-frequency measurement configuration component 198.
In some aspects, each of the one or more PCI IDs may be a PCI index associated with a PCI number identifying one second network entity of the set of second network entities. For example, each of the one or more PCI IDs may be a PCI index (e.g., a 2-bit short PCI ID) associated with a PCI number (e.g., a 10-bit full PCI ID) identifying one second network entity of the set of second network entities.
In some aspects, the SSB configuration may further include one or more of: the periodicity of the one or more SSBs; the offset of the one or more SSBs; a subset identifier identifying a subset of SSBs within the one or more SSBs; and the transmit power of the one or more SSBs. For example, referring to FIGs. 7, 9, and 11, the SSB configuration (702, 902, and 1102) may further include one or more of the periodicity of the one or more SSBs; the offset of the one or more SSBs; a subset identifier identifying a subset of SSBs within the one or more SSBs; and the transmit power of the one or more SSBs.
In some aspects, the first configuration may further include frequency information and SCS information associated with the one or more SSBs. For example, referring to FIGs. 7, 9, and 11, the first configuration may further include frequency information (712, 912, and 1112) and SCS information (714, 914, and 1114) associated with the one or more SSBs.
In some aspects, each of the one or more reference IDs may be associated with: one SSB of the one or more SSBs, one PCI ID of the one or more PCI IDs, the frequency information of the one or more SSBs, and the SCS information of the one or more SSBs. For example, referring to FIG. 8, each of the one or more reference IDs (e.g., RS 1) may be associated with: one SSB (e.g., SSB y) of the one or more SSBs, one PCI ID (e.g., PCI ni) of the one or more PCI IDs, the frequency information (e.g., Freq n) of the one or more SSBs, and the SCS information (e.g., SCS n) of the one or more SSBs.
In some aspects, the one or more PCI IDs is one PCI ID, and the SSB configuration may be included in one of: a first RRC configuration for the first network entity or a second RRC configuration for an L3 measurement. For example, referring to FIG. 7, the one or more PCI IDs is one PCI ID (716) , and the SSB configuration may (702) be included in one of: a first RRC configuration for the first network entity (at 704) or a second RRC configuration (at 706) for an L3 measurement.
In some aspects, the one or more PCI IDs is one PCI ID, and the SSB configuration may further include a measurement gap ID associated with a measurement gap for the one or more SSBs. The SSB configuration may be included in one of: a first RRC configuration for the first network entity or a second RRC configuration for an L3 measurement. For example, referring to FIG. 9, the one or more PCI IDs is one PCI ID (916) , and the SSB configuration (902) may further include a measurement gap ID (917) associated with a measurement gap for the one or more SSBs. The SSB configuration may be included in one of: a first RRC configuration (at 904) for the first network entity or a second RRC configuration (at 906) for an L3 measurement.
In some aspects, the one or more PCI IDs are multiple PCI IDs, and the SSB configuration may further include a measurement gap ID associated with a measurement gap for the one or more SSBs. The SSB configuration may be included in one of: a first RRC configuration for the first network entity or a second RRC configuration for an L3 measurement. For example, referring to FIG. 11, the one or more PCI IDs are multiple PCI IDs (PCI list 1116) , and the SSB configuration (1102) may further include a measurement gap ID (1117) associated with a measurement gap for the one or more SSBs. The SSB configuration may be included in one of: a first RRC configuration (at 1104) for the first network entity or a second RRC configuration (at 1116) for an L3 measurement.
In some aspects, at 1612, the one or more RSs may include one or more CSI-RSs associated with a set of second network entities. The first configuration of the channel measurement resource set may be associated with a first network entity. The first network entity may operate at a first frequency band, and at least one second network entity of the set of second network entities may operate at a second frequency band different from the first frequency band. For example, referring to FIG. 13, the one or more RSs may include one or more CSI-RSs (at 1340) associated with a set of second network entities. The first configuration of the channel measurement resource set may be associated with a first network entity. The first network entity may operate at a first frequency band, and at least one second network entity of the set of second network entities may operate at a second frequency band different from the first frequency band. In some aspects, 1612 may be performed by the inter-frequency measurement configuration component 198.
In some aspects, at 1614, the first configuration may include one or more of: a reference frequency for the one or more CSI-RSs, an SCS associated with the one or more CSI-RSs, one or more PCI IDs, where the one or more PCI IDs are associated with the set of second network entities, and the measurement gap associated with the one or more CSI-RSs. For example, referring to FIG. 13, the first configuration (e.g., MeasObjectLTM 1360) may include one or more of: a reference frequency (e.g., refFreqCSI-RS 1370) for the one or more CSI-RSs, an SCS (e.g., Subcarrier Spacing 1380) associated with the one or more CSI-RSs, one or more PCI IDs (1392) , where the one or more PCI IDs are associated with the set of second network entities, and the measurement gap associated with the one or more CSI-RSs. In some aspects, 1614 may be performed by the inter-frequency measurement configuration component 198.
In some aspects, to obtain the first configuration of the channel measurement resource set, the UE may be configured to receive, from a first network entity, the first configuration of the channel measurement resource set. For example, referring to FIG. 14, the UE 1402 may be configured to receive, at 1406, from a first network entity (base station 1404) , the first configuration of the channel measurement resource set.
FIG. 17 is a flowchart 1700 illustrating methods of wireless communication at a network entity in accordance with various aspects of the present disclosure. The method may be performed by a network entity. The network entity may be a base station, or a component of a base station, in the access network of FIG. 1 or a core network component (e.g., base station 102, 310, 1404; or the network entity 1902 in the hardware implementation of FIG. 19) . By signaling to a UE with a configuration of a channel measurement resource set including one or more RSs for LTM, the method supports inter-frequency RS configurations for LTM measurements. It enhances the flexibility of inter-frequency LTM measurements and improves the efficiency of wireless communication.
As shown in FIG. 17, at 1702, the network entity may configure, for a UE, a first configuration of a channel measurement resource set including one or more RSs for LTM, where the channel measurement resource set is associated with an L1 CSI report and includes one or more reference IDs for the one or more RSs. The UE may be the UE 104, 350, 1402, or the apparatus 1904 in the hardware implementation of FIG. 19. FIGs. 7, 8, 9, 10, 11, 12, 13, and 14 illustrate various aspects of the steps in connection with flowchart 1700. For example, referring to FIG. 14, the network entity (base station 1404) may configure, at 1406, for a UE 1402, a first configuration of a channel measurement resource set including one or more RSs for LTM. Referring to FIGs. 7, 9, and 11, the channel measurement resource set (720, 920, or 1120) may be associated with an L1 CSI report and include one or more reference IDs (740, 940, or 1140) for the one or more RSs. In some aspects, 1702 may be performed by the inter-frequency measurement configuration component 199.
At 1704, the network entity may receive, from the UE, at least one measurement for LTM based on the one or more RSs. For example, referring to FIG. 14, the network entity (base station 1404) may receive, at 1410, from the UE 1402, at least one measurement for LTM based on the one or more RSs. In some aspects, 1704 may be performed by the inter-frequency measurement configuration component 199.
FIG. 18 is a flowchart 1800 illustrating methods of wireless communication at a network entity in accordance with various aspects of the present disclosure. The method may be performed by a network entity. The network entity may be a base station, or a component of a base station, in the access network of FIG. 1 or a core network component (e.g., base station 102, 310, 1404; or the network entity 1902 in the hardware implementation of FIG. 19) . By signaling to a UE with a configuration of a channel measurement resource set including one or more RSs for LTM, the method supports inter-frequency RS configurations for LTM measurements. It enhances the flexibility of inter-frequency LTM measurements and improves the efficiency of wireless communication.
As shown in FIG. 18, at 1802, the network entity may configure, for a UE, a first configuration of a channel measurement resource set including one or more RSs for LTM, where the channel measurement resource set is associated with an L1 CSI report and includes one or more reference IDs for the one or more RSs. The UE may be the UE 104, 350, 1402, or the apparatus 1904 in the hardware implementation of FIG. 19. FIGs. 7, 8, 9, 10, 11, 12, 13, and 14 illustrate various aspects of the steps in connection with flowchart 1800. For example, referring to FIG. 14, the network entity (base station 1404) may configure, at 1406, for a UE 1402, a first configuration of a channel measurement resource set including one or more RSs for LTM. Referring to FIGs. 7, 9, and 11, the channel measurement resource set (720, 920, or 1120) may be associated with an L1 CSI report and include one or more reference IDs (740, 940, or 1140) for the one or more RSs. In some aspects, 1802 may be performed by the inter-frequency measurement configuration component 199.
At 1804, the network entity may receive, from the UE, at least one measurement for LTM based on the one or more RSs. For example, referring to FIG. 14, the network entity (base station 1404) may receive, at 1410, from the UE 1402, at least one measurement for LTM based on the one or more RSs. In some aspects, 1804 may be performed by the inter-frequency measurement configuration component 199.
In some aspects, at 1806, the one or more RSs may include one or more SSBs associated with a set of second network entities. For example, referring to FIG. 11, the one or more RSs may include one or more SSBs (e.g., SSBs 1118) . The one or more SSBs (e.g., SSBs 1118) may be associated with a set of second network entities (referred to by PCI list 1116) . In some aspects, 1806 may be performed by the inter-frequency measurement configuration component 199.
In some aspects, at 1808, the first network entity may operate at a first frequency band, and at least one second network entity of the set of second network entities may operate at a second frequency band different from the first frequency band. For example, referring to FIGs. 7, 9, and 11, the RSs (740, 940, and 1140) are inter-frequency RSs, indicating the first network entity and at least one second network entity of the set of second network entities operate at different frequency bands. In some aspects, 1808 may be performed by the inter-frequency measurement configuration component 199.
In some aspects, at 1810, the first configuration may include an SSB configuration associated with the one or more SSBs, and the SSB configuration may include: one or more PCI IDs, where the one or more PCI IDs are associated with the set of second network entities. For example, referring to FIGs. 7, 9, and 11, the first configuration may include an SSB configuration (702, 902, and 1102) associated with the one or more SSBs (718, 918, and 1118) . The SSB configuration may include: one or more PCI IDs (716, 916, and 1116) . The one or more PCI IDs may be associated with the set of second network entities. In some aspects, 1810 may be performed by the inter-frequency measurement configuration component 199.
In some aspects, each of the one or more PCI IDs may be a PCI index associated with a PCI number identifying one second network entity of the set of second network entities. For example, each of the one or more PCI IDs may be a PCI index (e.g., a 2-bit short PCI ID) associated with a PCI number (e.g., a 10-bit full PCI ID) identifying one second network entity of the set of second network entities.
In some aspects, the SSB configuration may further include one or more of: the periodicity of the one or more SSBs; the offset of the one or more SSBs; a subset identifier identifying a subset of SSBs within the one or more SSBs; and the transmit power of the one or more SSBs. For example, referring to FIGs. 7, 9, and 11, the SSB configuration (702, 902, and 1102) may further include one or more of the periodicity of the one or more SSBs; the offset of the one or more SSBs; a subset identifier identifying a subset of SSBs within the one or more SSBs; and the transmit power of the one or more SSBs.
In some aspects, the first configuration may further include frequency information and SCS information associated with the one or more SSBs. For example, referring to FIGs. 7, 9, and 11, the first configuration may further include frequency information (712, 912, and 1112) and SCS information (714, 914, and 1114) associated with the one or more SSBs.
In some aspects, each of the one or more reference IDs may be associated with: one SSB of the one or more SSBs, one PCI ID of the one or more PCI IDs, the frequency information of the one or more SSBs, and the SCS information of the one or more SSBs. For example, referring to FIG. 8, each of the one or more reference IDs (e.g., RS 1) may be associated with: one SSB (e.g., SSB y) of the one or more SSBs, one PCI ID (e.g., PCI ni) of the one or more PCI IDs, the frequency information (e.g., Freq n) of the one or more SSBs, and the SCS information (e.g., SCS n) of the one or more SSBs.
In some aspects, the one or more PCI IDs is one PCI ID, and the SSB configuration may be include in one of: a first RRC configuration for the first network entity or a second RRC configuration for an L3 measurement. For example, referring to FIG. 7, the one or more PCI IDs is one PCI ID (716) , and the SSB configuration may (702) be included in one of: a first RRC configuration for the first network entity (at 704) or a second RRC configuration (at 706) for an L3 measurement.
In some aspects, the one or more PCI IDs is one PCI ID, and the SSB configuration may further include a measurement gap ID associated with a measurement gap for the one or more SSBs. The SSB configuration may be included in one of: a first RRC configuration for the first network entity or a second RRC configuration for an L3 measurement. For example, referring to FIG. 9, the one or more PCI IDs is one PCI ID (916) , and the SSB configuration (902) may further include a measurement gap ID (917) associated with a measurement gap for the one or more SSBs. The SSB configuration may be included in one of: a first RRC configuration (at 904) for the first network entity or a second RRC configuration (at 906) for an L3 measurement.
In some aspects, the one or more PCI IDs are multiple PCI IDs, and the SSB configuration may further include a measurement gap ID associated with a measurement gap for the one or more SSBs. The SSB configuration may be included in one of: a first RRC configuration for the first network entity or a second RRC configuration for an L3 measurement. For example, referring to FIG. 11, the one or more PCI IDs are multiple PCI IDs (PCI list 1116) , and the SSB configuration (1102) may further include a measurement gap ID (1117) associated with a measurement gap for the one or more SSBs. The SSB configuration may be included in one of: a first RRC configuration (at 1104) for the first network entity or a second RRC configuration (at 1116) for an L3 measurement.
In some aspects, at 1812, the one or more RSs may include one or more CSI-RSs associated with a set of second network entities. The first network entity may operate at a first frequency band, and at least one second network entity of the set of second network entities may operate at a second frequency band different from the first frequency band. For example, referring to FIG. 13, the one or more RSs may include one or more CSI-RSs (at 1340) associated with a set of second network entities. The first configuration of the channel measurement resource set may be associated with a first network entity. The first network entity may operate at a first frequency band, and at least one second network entity of the set of second network entities may operate at a second frequency band different from the first frequency band. In some aspects, 1812 may be performed by the inter-frequency measurement configuration component 199.
In some aspects, at 1814, the first configuration may include one or more of: a reference frequency for the one or more CSI-RSs, an SCS associated with the one or more CSI-RSs, one or more PCI IDs, where the one or more PCI IDs are associated with the set of second network entities, and the measurement gap associated with the one or more CSI-RSs. For example, referring to FIG. 13, the first configuration (e.g., MeasObjectLTM 1360) may include one or more of: a reference frequency (e.g., refFreqCSI-RS 1370) for the one or more CSI-RSs, an SCS (e.g., Subcarrier Spacing 1380) associated with the one or more CSI-RSs, one or more PCI IDs (1392) , where the one or more PCI IDs are associated with the set of second network entities, and the measurement gap associated with the one or more CSI-RSs. In some aspects, 1814 may be performed by the inter-frequency measurement configuration component 199.
FIG. 19 is a diagram 1900 illustrating an example of a hardware implementation for an apparatus 1904. The apparatus 1904 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus 1904 may include a cellular baseband processor 1924 (also referred to as a modem) coupled to one or more transceivers 1922 (e.g., cellular RF transceiver) . The cellular baseband processor 1924 may include on-chip memory 1924'. In some aspects, the apparatus 1904 may further include one or more subscriber identity modules (SIM) cards 1920 and an application processor 1906 coupled to a secure digital (SD) card 1908 and a screen 1910. The application processor 1906 may include on-chip memory 1906'. In some aspects, the apparatus 1904 may further include a Bluetooth module 1912, a WLAN module 1914, an SPS module 1916 (e.g., GNSS module) , one or more sensor modules 1918 (e.g., barometric pressure sensor /altimeter; motion sensor such as inertial measurement unit (IMU) , gyroscope, and/or accelerometer (s) ; light detection and ranging (LIDAR) , radio assisted detection and ranging (RADAR) , sound navigation and ranging (SONAR) , magnetometer, audio and/or other technologies used for positioning) , additional memory modules 1926, a power supply 1930, and/or a camera 1932. The Bluetooth module 1912, the WLAN module 1914, and the SPS module 1916 may include an on-chip transceiver (TRX) (or in some cases, just a receiver (RX) ) . The Bluetooth module 1912, the WLAN module 1914, and the SPS module 1916 may include their own dedicated antennas and/or utilize the antennas 1980 for communication. The cellular baseband processor 1924 communicates through the transceiver (s) 1922 via one or more antennas 1980 with the UE 104 and/or with an RU associated with a network entity 1902. The cellular baseband processor 1924 and the application processor 1906 may each include a computer-readable medium /memory 1924', 1906', respectively. The additional memory modules 1926 may also be considered a computer-readable medium /memory. Each computer-readable medium /memory 1924', 1906', 1926 may be non-transitory. The cellular baseband processor 1924 and the application processor 1906 are each responsible for general processing, including the execution of software stored on the computer-readable medium /memory. The software, when executed by the cellular baseband processor 1924 /application processor 1906, causes the cellular baseband processor 1924 /application processor 1906 to perform the various functions described supra. The computer-readable medium /memory may also be used for storing data that is manipulated by the cellular baseband processor 1924 /application processor 1906 when executing software. The cellular baseband processor 1924 /application processor 1906 may be a component of the UE 350 and may include the memory 360 and/or at least one of the TX processor 368, the RX processor 356, and the controller/processor 359. In one configuration, the apparatus 1904 may be a processor chip (modem and/or application) and include just the cellular baseband processor 1924 and/or the application processor 1906, and in another configuration, the apparatus 1904 may be the entire UE (e.g., see UE 350 of FIG. 3) and include the additional modules of the apparatus 1904.
As discussed supra, the component 198 may be configured to obtain a first configuration of a channel measurement resource set including one or more RSs for LTM, where the channel measurement resource set is associated with an L1 CSI report and includes one or more reference IDs for the one or more RSs; and perform at least one measurement for LTM based on the one or more RSs. The component 198 may be further configured to perform any of the aspects described in connection with the flowcharts in FIG. 15 and FIG. 16, and/or performed by the UE 1402 in FIG. 14. The component 198 may be within the cellular baseband processor 1924, the application processor 1906, or both the cellular baseband processor 1924 and the application processor 1906. The component 198 may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by one or more processors configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by one or more processors, or some combination thereof. As shown, the apparatus 1904 may include a variety of components configured for various functions. In one configuration, the apparatus 1904, and in particular the cellular baseband processor 1924 and/or the application processor 1906, includes means for obtaining a first configuration of a channel measurement resource set including one or more RSs for LTM, where the channel measurement resource set is associated with an L1 CSI report and includes one or more reference IDs for the one or more RSs, and means for performing at least one measurement for LTM based on the one or more RSs. The apparatus 1904 may further include means for performing any of the aspects described in connection with the flowcharts in FIG. 15 and FIG. 16, and/or aspects performed by the UE 1402 in FIG. 14. The means may be the component 198 of the apparatus 1904 configured to perform the functions recited by the means. As described supra, the apparatus 1904 may include the TX processor 368, the RX processor 356, and the controller/proces sor 359. As such, in one configuration, the means may be the TX processor 368, the RX processor 356, and/or the controller/processor 359 configured to perform the functions recited by the means.
FIG. 20 is a diagram 2000 illustrating an example of a hardware implementation for a network entity 2002. The network entity 2002 may be a BS, a component of a BS, or may implement BS functionality. The network entity 2002 may include at least one of a CU 2010, a DU 2030, or an RU 2040. For example, depending on the layer functionality handled by the component 199, the network entity 2002 may include the CU 2010; both the CU 2010 and the DU 2030; each of the CU 2010, the DU 2030, and the RU 2040; the DU 2030; both the DU 2030 and the RU 2040; or the RU 2040. The CU 2010 may include a CU processor 2012. The CU processor 2012 may include on-chip memory 2012'. In some aspects, the CU 2010 may further include additional memory modules 2014 and a communications interface 2018. The CU 2010 communicates with the DU 2030 through a midhaul link, such as an F1 interface. The DU 2030 may include a DU processor 2032. The DU processor 2032 may include on-chip memory 2032'. In some aspects, the DU 2030 may further include additional memory modules 2034 and a communications interface 2038. The DU 2030 communicates with the RU 2040 through a fronthaul link. The RU 2040 may include an RU processor 2042. The RU processor 2042 may include on-chip memory 2042'. In some aspects, the RU 2040 may further include additional memory modules 2044, one or more transceivers 2046, antennas 2080, and a communications interface 2048. The RU 2040 communicates with the UE 104. The on-chip memory 2012', 2032', 2042'a nd the additional memory modules 2014, 2034, 2044 may each be considered a computer-readable medium /memory. Each computer-readable medium /memory may be non-transitory. Each of the processors 2012, 2032, 2042 is responsible for general processing, including the execution of software stored on the computer-readable medium /memory. The software, when executed by the corresponding processor (s) causes the processor (s) to perform the various functions described supra. The computer-readable medium /memory may also be used for storing data that is manipulated by the processor (s) when executing software.
As discussed supra, the component 199 may be configured to configure, for a UE, a first configuration of a channel measurement resource set including one or more RSs for LTM, where the channel measurement resource set is associated with an L1 CSI report and includes one or more reference IDs for the one or more RSs; and receive, from the UE, at least one measurement for LTM based on the one or more RSs. The component 199 may be further configured to perform any of the aspects described in connection with the flowcharts in FIG. 17 and FIG. 18, and/or performed by the base station 1404 in FIG. 14. The component 199 may be within one or more processors of one or more of the CU 2010, DU 2030, and the RU 2040. The component 199 may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by one or more processors configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by one or more processors, or some combination thereof. The network entity 2002 may include a variety of components configured for various functions. In one configuration, the network entity 2002 includes means for configuring, for a UE, a first configuration of a channel measurement resource set including one or more RSs for LTM, where the channel measurement resource set is associated with an L1 CSI report and includes one or more reference IDs for the one or more RSs, and means for receiving, from the UE, at least one measurement for LTM based on the one or more RSs. The network entity 2002 may further include means for performing any of the aspects described in connection with the flowcharts in FIG. 17 and FIG. 18, and/or aspects performed by the base station 1404 in FIG. 14. The means may be the component 199 of the network entity 2002 configured to perform the functions recited by the means. As described supra, the network entity 2002 may include the TX processor 316, the RX processor 370, and the controller/processor 375. As such, in one configuration, the means may be the TX processor 316, the RX processor 370, and/or the controller/processor 375 configured to perform the functions recited by the means.
This disclosure provides a method for wireless communication at a UE. The method may include obtaining a first configuration of a channel measurement resource set including one or more RSs for LTM, where the channel measurement resource set is associated with an L1 CSI report and includes one or more reference IDs for the one or more RSs; and performing at least one measurement for LTM based on the one or more RSs. By signaling to a UE with a configuration of a channel measurement resource set including one or more RSs for LTM, the method supports inter-frequency RS configurations for LTM measurements. It enhances the flexibility of inter-frequency LTM measurements and improves the efficiency of wireless communication.
It is understood that the specific order or hierarchy of blocks in the processes /flowcharts disclosed is an illustration of example approaches. Based upon design preferences, it is understood that the specific order or hierarchy of blocks in the processes /flowcharts may be rearranged. Further, some blocks may be combined or omitted. The accompanying method claims present elements of the various blocks in a sample order, and are not limited to the specific order or hierarchy presented.
The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not limited to the aspects described herein, but are to be accorded the full scope consistent with the language claims. Reference to an element in the singular does not mean “one and only one” unless specifically so stated, but rather “one or more. ” Terms such as “if, ” “when, ” and “while” do not imply an immediate temporal relationship or reaction. That is, these phrases, e.g., “when, ” do not imply an immediate action in response to or during the occurrence of an action, but simply imply that if a condition is met then an action will occur, but without requiring a specific or immediate time constraint for the action to occur. The word “exemplary” is used herein to mean “serving as an example, instance, or illustration. ” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects. Unless specifically stated otherwise, the term “some” refers to one or more. Combinations such as “at least one of A, B, or C, ” “one or more of A, B, or C, ” “at least one of A, B, and C, ” “one or more of A, B, and C, ” and “A, B, C, or any combination thereof” include any combination of A, B, and/or C, and may include multiples of A, multiples of B, or multiples of C. Specifically, combinations such as “at least one of A, B, or C, ” “one or more of A, B, or C, ” “at least one of A, B, and C, ” “one or more of A, B, and C, ” and “A, B, C, or any combination thereof” may be A only, B only, C only, A and B, A and C, B and C, or A and B and C, where any such combinations may contain one or more member or members of A, B, or C. Sets should be interpreted as a set of elements where the elements number one or more. Accordingly, for a set of X, X would include one or more elements. If a first apparatus receives data from or transmits data to a second apparatus, the data may be received/transmitted directly between the first and second apparatuses, or indirectly between the first and second apparatuses through a set of apparatuses. A device configured to “output” data, such as a transmission, signal, or message, may transmit the data, for example with a transceiver, or may send the data to a device that transmits the data. A device configured to “obtain” data, such as a transmission, signal, or message, may receive, for example with a transceiver, or may obtain the data from a device that receives the data. Information stored in a memory includes instructions and/or data. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are encompassed by the claims. Moreover, nothing disclosed herein is dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. The words “module, ” “mechanism, ” “element, ” “device, ” and the like may not be a substitute for the word “means. ” As such, no claim element is to be construed as a means plus function unless the element is expressly recited using the phrase “means for. ”
As used herein, the phrase “based on” shall not be construed as a reference to a closed set of information, one or more conditions, one or more factors, or the like. In other words, the phrase “based on A” (where “A” may be information, a condition, a factor, or the like) shall be construed as “based at least on A” unless specifically recited differently.
The following aspects are illustrative only and may be combined with other aspects or teachings described herein, without limitation.
Aspect 1 is a method of wireless communication at a UE. The method may include obtaining a first configuration of a channel measurement resource set including one or more RSs for LTM, where the channel measurement resource set is associated with an L1 CSI report and includes one or more reference IDs for the one or more RSs; and performing at least one measurement for LTM based on the one or more RSs.
Aspect 2 is the method of aspect 1, where the first configuration of the channel measurement resource set may be associated with a first network entity, and the one or more RSs may include one or more SSBs associated with a set of second network entities.
Aspect 3 is the method of aspect 2, where the first network entity may operate at a first frequency band, and at least one second network entity of the set of second network entities may operate at a second frequency band different from the first frequency band.
Aspect 4 is the method of aspect 3, where the first configuration may include an SSB configuration associated with the one or more SSBs, and the SSB configuration may include one or more PCI IDs, where the one or more PCI IDs may be associated with the set of second network entities.
Aspect 5 is the method of aspect 4, where each of the one or more PCI IDs may be a PCI index associated with a PCI number identifying one second network entity of the set of second network entities.
Aspect 6 is the method of aspect 4, where the SSB configuration may further include one or more of: the periodicity of the one or more SSBs; the offset of the one or more SSBs; a subset identifier identifying a subset of SSBs within the one or more SSBs; and the transmit power of the one or more SSBs.
Aspect 7 is the method of aspect 4, where the first configuration may further include frequency information and SCS information associated with the one or more SSBs.
Aspect 8 is the method of aspect 7, where each of the one or more reference IDs may be associated with: one SSB of the one or more SSBs, one PCI ID of the one or more PCI IDs, the frequency information of the one or more SSBs, and the SCS information of the one or more SSBs.
Aspect 9 is the method of aspect 4, where the one or more PCI IDs is one PCI ID, and the SSB configuration may be included (i.e., comprised) in one of: a first RRC configuration for the first network entity or a second RRC configuration for an L3 measurement.
Aspect 10 is the method of aspect 4, where the one or more PCI IDs is one PCI ID, and the SSB configuration may further include a measurement gap ID associated with a measurement gap for the one or more SSBs, and the SSB configuration may be included in one of: a first RRC configuration for the first network entity or a second RRC configuration for an L3 measurement.
Aspect 11 is the method of aspect 4, where the one or more PCI IDs are multiple PCI IDs, and the SSB configuration may further include a measurement gap ID associated with a measurement gap for the one or more SSBs, and the SSB configuration may be included in one of: a first RRC configuration for the first network entity or a second RRC configuration for an L3 measurement.
Aspect 12 is the method of aspect 1, where the one or more RSs may include one or more CSI-RSs associated with a set of second network entities. The first configuration of the channel measurement resource set may be associated with a first network entity. The first network entity may operate at a first frequency band, and at least one second network entity of the set of second network entities may operate at a second frequency band different from the first frequency band.
Aspect 13 is the method of aspect 12, where the first configuration may include one or more of: the reference frequency for the one or more CSI-RSs, the SCS associated with the one or more CSI-RSs, one or more PCI IDs, where the one or more PCI IDs are associated with the set of second network entities, and the measurement gap associated with the one or more CSI-RSs.
Aspect 14 is the method of any of aspects 1 to 13, where obtaining the first configuration of the channel measurement resource set may include: receiving, from a first network entity, the first configuration of the channel measurement resource set.
Aspect 15 is an apparatus for wireless communication at a UE, including: a memory; and at least one processor coupled to the memory and, based at least in part on information stored in the memory, the at least one processor is configured to perform the method of any of aspects 1-14.
Aspect 16 is the apparatus of aspect 15, further including at least one of a transceiver or an antenna coupled to the at least one processor and configured to obtain the first configuration.
Aspect 17 is an apparatus for wireless communication including means for implementing the method of any of aspects 1-14.
Aspect 18 is a computer-readable medium (e.g., a non-transitory computer-readable medium) storing computer executable code, where the code when executed by a processor causes the processor to implement the method of any of aspects 1-14.
Aspect 19 is a method of wireless communication at a network entity. The method may include configuring, for a UE, a first configuration of a channel measurement resource set including one or more RSs for LTM, where the channel measurement resource set is associated with an L1 CSI report and includes one or more reference IDs for the one or more RSs; and receiving, from the UE, at least one measurement for LTM based on the one or more RSs.
Aspect 20 is the method of aspect 19, where the one or more RSs may include one or more SSBs associated with a set of second network entities.
Aspect 21 is the method of aspect 20, where the first network entity may operate at a first frequency band, and at least one second network entity of the set of second network entities may operate at a second frequency band different from the first frequency band.
Aspect 22 is the method of aspect 21, where the first configuration may include an SSB configuration associated with the one or more SSBs. The SSB configuration may include: one or more PCI IDs, where the one or more PCI IDs are associated with the set of second network entities.
Aspect 23 is the method of aspect 22, where each of the one or more PCI IDs may be a PCI index associated with a PCI number identifying one second network entity of the set of second network entities.
Aspect 24 is the method of aspect 22, where the SSB configuration may further include one or more of: the periodicity of the one or more SSBs; the offset of the one or more SSBs; a subset identifier identifying a subset of SSBs within the one or more SSBs; and the transmit power of the one or more SSBs.
Aspect 25 is the method of aspect 22, where the first configuration may further include frequency information and SCS information associated with the one or more SSBs.
Aspect 26 is the method of aspect 25, where each of the one or more reference IDs may be associated with: one SSB of the one or more SSBs, one PCI ID of the one or more PCI IDs, the frequency information of the one or more SSBs, and the SCS information of the one or more SSBs.
Aspect 27 is the method of aspect 22, where the one or more PCI IDs is one PCI ID, and the SSB configuration may be included in one of: a first RRC configuration for the first network entity or a second RRC configuration for an L3 measurement.
Aspect 28 is the method of aspect 22, where the one or more PCI IDs is one PCI ID, and the SSB configuration may further include a measurement gap ID associated with a measurement gap for the one or more SSBs, and the SSB configuration may be included in one of: a first RRC configuration for the first network entity or a second RRC configuration for an L3 measurement.
Aspect 29 is the method of aspect 22, where the one or more PCI IDs are multiple PCI IDs, and the SSB configuration may further include a measurement gap ID associated with a measurement gap for the one or more SSBs, and the SSB configuration may be included in one of: a first RRC configuration for the first network entity or a second RRC configuration for an L3 measurement.
Aspect 30 is the method of aspect 19, where the one or more RSs may include one or more CSI-RSs associated with a set of second network entities. The first network entity may operate at a first frequency band, and at least one second network entity of the set of second network entities may operate at a second frequency band different from the first frequency band.
Aspect 31 is the method of aspect 30, where the first configuration may include one or more of: the reference frequency for the one or more CSI-RSs, the SCS associated with the one or more CSI-RSs, one or more PCI IDs, where the one or more PCI IDs are associated with the set of second network entities, and the measurement gap associated with the one or more CSI-RSs.
Aspect 32 is an apparatus for wireless communication at a network entity, including: a memory; and at least one processor coupled to the memory and, based at least in part on information stored in the memory, the at least one processor is configured to perform the method of any of aspects 19-31.
Aspect 33 is the apparatus of aspect 32, further including at least one of a transceiver or an antenna coupled to the at least one processor and configured to receive the at least one measurement for LTM.
Aspect 34 is an apparatus for wireless communication including means for implementing the method of any of aspects 19-31.
Aspect 35 is a computer-readable medium (e.g., a non-transitory computer-readable medium) storing computer executable code, where the code when executed by a processor causes the processor to implement the method of any of aspects 19-31.

Claims

An apparatus for wireless communication at a user equipment (UE) , comprising:

memory; and

at least one processor coupled to the memory and, based at least in part on information stored in the memory, the at least one processor is configured to:

obtain a first configuration of a channel measurement resource set comprising one or more reference signals (RSs) for lower-layer triggered mobility (LTM) , wherein the channel measurement resource set is associated with a layer 1 (L1) channel state information (CSI) report and comprises one or more reference identifiers (IDs) for the one or more RSs; and

perform at least one measurement for LTM based on the one or more RSs.
The apparatus of claim 1, further comprising a transceiver coupled to the at least one processor, wherein, to obtain the first configuration, the at least one processor is configured to obtain the first configuration via the transceiver, wherein the first configuration of the channel measurement resource set is associated with a first network entity, and wherein the one or more RSs include one or more synchronization signal blocks (SSBs) associated with a set of second network entities.
The apparatus of claim 2, wherein the first network entity operates at a first frequency band, and at least one second network entity of the set of second network entities operates at a second frequency band different from the first frequency band.
The apparatus of claim 3, wherein the first configuration comprises an SSB configuration associated with the one or more SSBs, wherein the SSB configuration comprises:

one or more physical cell identifier (PCI) IDs, wherein the one or more PCI IDs are associated with the set of second network entities.
The apparatus of claim 4, wherein each of the one or more PCI IDs is:

a PCI index associated with a PCI number identifying one second network entity of the set of second network entities.
The apparatus of claim 4, wherein the SSB configuration further comprises one or more of:

a periodicity of the one or more SSBs;

an offset of the one or more SSBs;

a subset identifier identifying a subset of SSBs within the one or more SSBs; and

a transmit power of the one or more SSBs.
The apparatus of claim 4, wherein the first configuration further comprises frequency information and subcarrier spacing (SCS) information associated with the one or more SSBs.
The apparatus of claim 7, wherein each of the one or more reference IDs is associated with:

one SSB of the one or more SSBs,

one PCI ID of the one or more PCI IDs,

the frequency information of the one or more SSBs, and

the SCS information of the one or more SSBs.
The apparatus of claim 4, wherein the one or more PCI IDs is one PCI ID, and the SSB configuration is comprised in one of:

a first radio resource control (RRC) configuration for the first network entity, or

a second RRC configuration for an L3 measurement.
The apparatus of claim 4, wherein the one or more PCI IDs is one PCI ID, and the SSB configuration further includes a measurement gap ID associated with a measurement gap for the one or more SSBs, and the SSB configuration is comprised in one of:

a first radio resource control (RRC) configuration for the first network entity, or

a second RRC configuration for an L3 measurement.
The apparatus of claim 4, wherein the one or more PCI IDs are multiple PCI IDs, and the SSB configuration further includes a measurement gap ID associated with a measurement gap for the one or more SSBs, and the SSB configuration is comprised in one of:

a first radio resource control (RRC) configuration for the first network entity, or

a second RRC configuration for an L3 measurement.
The apparatus of claim 1, wherein the one or more RSs include one or more channel state information reference signals (CSI-RSs) associated with a set of second network entities, wherein the first configuration of the channel measurement resource set is associated with a first network entity, and wherein the first network entity operates at a first frequency band, and at least one second network entity of the set of second network entities operates at a second frequency band different from the first frequency band.
The apparatus of claim 12, wherein the first configuration comprises one or more of:

a reference frequency for the one or more CSI-RSs,

a subcarrier spacing (SCS) associated with the one or more CSI-RSs,

one or more physical cell identifier (PCI) IDs, wherein the one or more PCI IDs are associated with the set of second network entities, and

a measurement gap associated with the one or more CSI-RSs.
The apparatus of claim 1, wherein, to obtain the first configuration of the channel measurement resource set, the at least one processor is configured to:

receive, from a first network entity, the first configuration of the channel measurement resource set.
An apparatus for wireless communication at a first network entity, comprising:

memory; and

at least one processor coupled to the memory and, based at least in part on information stored in the memory, the at least one processor is configured to:

configure, for a user equipment (UE) , a first configuration of a channel measurement resource set comprising one or more reference signals (RSs) for lower-layer triggered mobility (LTM) , wherein the channel measurement resource set is associated with a layer 1 (L1) channel state information (CSI) report and comprises one or more reference identifiers (IDs) for the one or more RSs; and

receive, from the UE, at least one measurement for LTM based on the one or more RSs.
The apparatus of claim 15, wherein the one or more RSs include one or more synchronization signal blocks (SSBs) associated with a set of second network entities.
The apparatus of claim 16, wherein the first network entity operates at a first frequency band, and at least one second network entity of the set of second network entities operates at a second frequency band different from the first frequency band.
The apparatus of claim 17, wherein the first configuration comprises an SSB configuration associated with the one or more SSBs, wherein the SSB configuration comprises:

one or more physical cell identifier (PCI) IDs, wherein the one or more PCI IDs are associated with the set of second network entities.
The apparatus of claim 18, wherein each of the one or more PCI IDs is:

a PCI index associated with a PCI number identifying one second network entity of the set of second network entities.
The apparatus of claim 18, wherein the SSB configuration further comprises one or more of:

a periodicity of the one or more SSBs;

an offset of the one or more SSBs;

a subset identifier identifying a subset of SSBs within the one or more SSBs; and

a transmit power of the one or more SSBs.
The apparatus of claim 18, wherein the first configuration further comprises frequency information and subcarrier spacing (SCS) information associated with the one or more SSBs.
The apparatus of claim 21, wherein each of the one or more reference IDs is associated with:

one SSB of the one or more SSBs,

one PCI ID of the one or more PCI IDs,

the frequency information of the one or more SSBs, and

the SCS information of the one or more SSBs.
The apparatus of claim 18, wherein the one or more PCI IDs is one PCI ID, and the SSB configuration is comprised in one of:

a first radio resource control (RRC) configuration for the first network entity, or

a second RRC configuration for an L3 measurement.
The apparatus of claim 18, wherein the one or more PCI IDs is one PCI ID, and the SSB configuration further includes a measurement gap ID associated with a measurement gap for the one or more SSBs, and the SSB configuration is comprised in one of:

a first radio resource control (RRC) configuration for the first network entity, or

a second RRC configuration for an L3 measurement.
The apparatus of claim 18, wherein the one or more PCI IDs are multiple PCI IDs, and the SSB configuration further includes a measurement gap ID associated with a measurement gap for the one or more SSBs, and the SSB configuration is comprised in one of:

a first radio resource control (RRC) configuration for the first network entity, or

a second RRC configuration for an L3 measurement.
The apparatus of claim 15, wherein the one or more RSs include one or more channel state information reference signals (CSI-RSs) associated with a set of second network entities, wherein the first network entity operates at a first frequency band, and at least one second network entity of the set of second network entities operates at a second frequency band different from the first frequency band.
The apparatus of claim 26, wherein the first configuration comprises one or more of:

a reference frequency for the one or more CSI-RSs,

a subcarrier spacing (SCS) associated with the one or more CSI-RSs,

one or more physical cell identifier (PCI) IDs, wherein the one or more PCI IDs are associated with the set of second network entities, and

a measurement gap associated with the one or more CSI-RSs.
A method of wireless communication at a user equipment (UE) , comprising:

obtaining a first configuration of a channel measurement resource set comprising one or more reference signals (RSs) for lower-layer triggered mobility (LTM) , wherein the channel measurement resource set is associated with a layer 1 (L1) channel state information (CSI) report and comprises one or more reference identifiers (IDs) for the one or more RSs; and

performing at least one measurement for LTM based on the one or more RSs.
The method of claim 28, wherein the first configuration of the channel measurement resource set is associated with a first network entity, and wherein the one or more RSs include one or more synchronization signal blocks (SSBs) associated with a set of second network entities.
A method of wireless communication at a network entity, comprising:

configuring, for a user equipment (UE) , a first configuration of a channel measurement resource set comprising one or more reference signals (RSs) for lower-layer triggered mobility (LTM) , wherein the channel measurement resource set is associated a layer 1 (L1) channel state information (CSI) report and comprises one or more reference identifiers (IDs) for the one or more RSs; and

receiving, from the UE, at least one measurement for LTM based on the one or more RSs.