Beam indication for candidate cell groups in lower layer triggered mobility operations

Abstract

Various aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may transmit UE capability information, the UE capability information indicates a capability of the UE associated with activation of at least one transmit configuration indicator (TCI) associated with a candidate cell of a set of cells configured for lower layer triggered mobility (LTM) operation prior to reception of a beam indication associated with the candidate cell. The UE may receive configuration information corresponding to the LTM operation. The UE may perform an LTM handover operation based on the configuration information and the at least one TCI. Numerous other aspects are described.

Description

Technical Field

[0001] All aspects of this disclosure relate to wireless communication in general, and more particularly to techniques and apparatus for beam indication of candidate cell groups in lower-level mobility operations. Background Technology

[0002] Wireless communication systems are widely deployed to provide a variety of services, which may include carrying voice, text, messaging, video, data, and / or other services. Services may include unicast, multicast, and / or broadcast services, etc. Typical wireless communication systems may employ multiple access radio access technologies (RATs) capable of supporting communication with multiple users by sharing available system resources (e.g., system bandwidth and / or device transmit power). Examples of such multiple access RATs include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems.

[0003] The aforementioned Multiple Access RATs have been adopted in various telecommunications standards to provide a common protocol enabling different wireless communication devices to communicate at the city, national, regional, or global level. An example telecommunications standard is New Radio (NR). NR (which can also be referred to as 5G) is part of the continuous evolution of mobile broadband announced by the 3rd Generation Partnership Project (3GPP). NR (and other mobile broadband evolutions beyond NR) can be designed to better support the Internet of Things (IoT) and reduced-capacity device deployments, industrial connectivity, millimeter-wave (mmWave) expansion, licensed and unlicensed spectrum access, non-terrestrial network (NTN) deployments, sidelinks and other device-to-device direct communication technologies, massive MIMO, decomposed network architectures and network topology expansion, multi-subscriber implementations and / or high-precision positioning, and more. As the demand for mobile broadband access continues to grow, further improvements to NR can be made, and other radio access technologies, such as 6G, can be introduced to further advance mobile broadband evolution.

[0004] In some cases, User Equipment (UE) may be configured with Lower Layer Triggered Mobility (LTM) to enable efficient handover between multiple cells. Layer 1 (L1) and / or Layer 2 (L2) signaling may be referred to as “lower layer” signaling and may be used to activate and / or deactivate candidate cells in a set of cells configured for L1 / L2 mobility, and / or provide reference signals for measurement by the UE, by which the UE selects a candidate beam as the target beam for lower layer handover operations. LTM may refer to L1 / L2 mobility triggered by the network during cell handover. To facilitate LTM, the target beam may be indicated to the UE by the network. Summary of the Invention

[0005] Some aspects described herein relate to a user equipment (UE) for wireless communication. The UE may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured to transmit UE capability information indicating the UE's capabilities associated with the activation of at least one Transmit Configuration Indicator (TCI) associated with a candidate cell prior to the reception of a beam indication associated with a candidate cell in a set of cells configured for lower-level triggered mobility (LTM) operation. The one or more processors may be configured to receive configuration information corresponding to the LTM operation. The one or more processors may be configured to perform an LTM handover operation based on the configuration information and the at least one TCI.

[0006] Some aspects described herein relate to a network node for wireless communication. The network node may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured to receive UE capability information indicating the UE's capabilities associated with the activation of at least one TCI associated with a candidate cell prior to the transmission of a beam indication associated with a candidate cell in a set of cells configured for LTM operation. The one or more processors may be configured to transmit configuration information corresponding to the LTM operation. The one or more processors may be configured to perform an LTM handover operation based on the configuration information and the at least one TCI.

[0007] Some aspects described herein relate to a method for wireless communication performed by a UE. The method may include transmitting UE capability information indicating the UE's capability associated with activation of at least one TCI associated with a candidate cell prior to reception of a beam indication associated with a candidate cell in a set of cells configured for LTM operation. The method may include receiving configuration information corresponding to the LTM operation. The method may include performing an LTM handover operation based on the configuration information and the at least one TCI.

[0008] Some aspects described herein relate to a method for wireless communication performed by a network node. The method may include receiving UE capability information indicating the UE's capabilities associated with the activation of at least one TCI associated with a candidate cell prior to the transmission of a beam indication associated with a candidate cell in a set of cells configured for LTM operation. The method may include transmitting configuration information corresponding to the LTM operation. The method may include performing an LTM handover operation based on the configuration information and the at least one TCI.

[0009] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a UE. When executed by one or more processors of the UE, the set of instructions enables the UE to transmit UE capability information indicating the UE's capability associated with activation of at least one TCI associated with a candidate cell prior to reception of a beam indication associated with a candidate cell in a set of cells configured for LTM operation. When executed by one or more processors of the UE, the set of instructions enables the UE to receive configuration information corresponding to the LTM operation. When executed by one or more processors of the UE, the set of instructions enables the UE to perform an LTM handover operation based on the configuration information and the at least one TCI.

[0010] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a network node. When executed by one or more processors of the network node, the set of instructions enables the network node to receive UE capability information indicating the UE's capability associated with the activation of at least one TCI associated with a candidate cell prior to the transmission of a beam indication associated with a candidate cell in a set of cells configured for LTM operation. When executed by one or more processors of the network node, the set of instructions enables the network node to transmit configuration information corresponding to the LTM operation. When executed by one or more processors of the network node, the set of instructions enables the network node to perform an LTM handover operation based on the configuration information and the at least one TCI.

[0011] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for transmitting UE capability information indicating the apparatus's capability associated with activation of at least one TCI associated with a candidate cell prior to reception of a beam indication associated with a candidate cell in a set of cells configured for LTM operation. The apparatus may include components for receiving configuration information corresponding to the LTM operation. The apparatus may include components for performing an LTM handover operation based on the configuration information and the at least one TCI.

[0012] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for receiving UE capability information indicating the UE's capabilities associated with the activation of at least one TCI associated with a candidate cell prior to the transmission of a beam indication associated with a candidate cell in a set of cells configured for LTM operation. The apparatus may include components for transmitting configuration information corresponding to the LTM operation. The apparatus may include components for performing an LTM handover operation based on the configuration information and the at least one TCI.

[0013] The entirety of the terms includes, as fully described with reference to the accompanying drawings and description, and as illustrated in the accompanying drawings and description, methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network nodes, network entities, wireless communication devices and / or processing systems.

[0014] The foregoing has broadly summarized some aspects of this disclosure. Additional aspects and associated advantages will be described below. The disclosed aspects can serve as a basis for modifying or designing other aspects for performing the same purpose of this disclosure. Such equivalent aspects do not depart from the scope of the appended claims. The characteristics of the aspects disclosed herein, in both their organization and manner of operation, and their associated advantages, will be better understood by considering the following description in conjunction with the accompanying drawings. Each drawing in the accompanying drawings is for illustrative and descriptive purposes and not intended to define limitations of the claims. Attached Figure Description

[0015] The accompanying drawings illustrate some aspects of this disclosure, but do not limit its scope, as other aspects can be achieved with this description. The same reference numerals in different drawings may identify the same or similar elements.

[0016] Figure 1 This is a diagram illustrating an example of a wireless network according to the present disclosure.

[0017] Figure 2 This is a diagram illustrating an example network node communicating with an example user equipment (UE) in a wireless network according to the present disclosure.

[0018] Figure 3 This is a diagram illustrating an example decomposed base station architecture according to this disclosure.

[0019] Figure 4A An example of a first lower layer triggered mobility (LTM) technique according to this disclosure is illustrated.

[0020] Figure 4B An example of a second LTM technology according to this disclosure is illustrated.

[0021] Figure 5 This is a diagram illustrating an example of an example associated with a layer 1 measurement operation based on layer 3 for LTM according to this disclosure.

[0022] Figure 6 This is a diagram illustrating an example procedure performed by a UE according to this disclosure, for example.

[0023] Figure 7 This is a diagram illustrating an example process performed, for example, by a network node according to this disclosure.

[0024] Figure 8 This is a diagram of an example device for wireless communication according to the present disclosure.

[0025] Figure 9 This is a diagram of an example device for wireless communication according to the present disclosure. Detailed Implementation

[0026] Various aspects of this disclosure are described below with reference to the accompanying drawings. However, this disclosure may be embodied in many different forms and is not to be construed as limited to any particular aspect presented herein. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of this disclosure to those skilled in the art. Those skilled in the art will understand that the scope of this disclosure is intended to cover any aspect of this disclosure disclosed herein, whether implemented independently of or in combination with any other aspect of this disclosure. For example, any amount of aspects set forth herein may be used to implement an apparatus or practice. Furthermore, the scope of this disclosure is intended to cover an apparatus or method practiced using another structure, function, or structure and function that complements or replaces the various aspects of this disclosure set forth herein. Any aspect of this disclosure disclosed herein may be embodied by one or more elements of the claims.

[0027] Several aspects of a telecommunications system will now be presented with reference to various devices and techniques. These devices and techniques will be described in detail below and illustrated in the accompanying drawings by various boxes, modules, components, circuits, steps, processes, or algorithms (collectively, “elements”). These elements may be implemented using hardware, software, or a combination of hardware and software. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole.

[0028] Various aspects generally relate to lower-layer triggered mobility (LTM) operations. Some aspects more specifically relate to beam indication for candidate cell groups during LTM operations. In some examples, the user equipment (UE) may send UE capability information to the network node, indicating the UE's capabilities associated with activation of the Transmit Configuration Indicator (TCI) state prior to the reception of the beam indication. For example, in some aspects, the UE capability information may indicate that the UE supports TCI activation prior to the beam indication. In some other aspects, the UE capability information may indicate that the UE supports TCI activation along with the beam indication. In some aspects, the UE may be provided with TCI activation communication (e.g., a Media Access Control (MAC) Control Element (CE) (MAC CE)) prior to receiving the beam indication. In some other aspects, the UE may be provided with TCI activation and a beam indication associated with the candidate cell's beam (e.g., in a cell handover command). The UE may activate the TCI, activate the beam, and perform LTM handover in association with the activated TCI and beam.

[0029] Specific aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. By sending UE capability information to the network node, some aspects can facilitate coordination between the UE and the network node associated with signaling for TCI and beam activation, thereby improving the efficiency of LTM handover. For example, by instructing the UE to support TCI activation prior to beam indication, some aspects of the UE capability information described herein can facilitate earlier preparation for LTM handover by the UE and candidate cells. As another example, by instructing the UE not to support TCI activation prior to beam indication (or by instructing the UE to support TCI activation along with beam indication), some aspects of the UE capability information described herein can enable the network node to include a TCI activation indication in the cell handover command, thereby reducing overhead prior to LTM handover.

[0030] Figure 1This is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be a 5G (or New Radio (NR)) network or a 6G network, or may include elements of a 5G (or New Radio (NR)) network or a 6G network, etc. The wireless network 100 may include multiple network nodes 110 (also referred to as network entities), shown as network node (NN) 110a, network node 110b, network node 110c, and network node 110d. Network nodes 110 may support communication with multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e).

[0031] Network node 110 may include one or more devices that enable communication between UE 120 and one or more components of wireless network 100. Network node 110 may be, may include, or may be referred to as an NR network node, 6G network node, node B, eNB (e.g., in 4G), gNB (e.g., in 5G), access point (AP), transmit / receive point (TRP), network mobility element, core network node, network element, network equipment, and / or one or more devices of another type included in a radio access network (RAN).

[0032] Network node 110 can be a single physical node, or it can be two or more physical nodes. For example, network node 110 can be a device or system implementing a part of a radio protocol stack, a device or system implementing a complete protocol stack (such as a complete gNB protocol stack), or a collection of devices or systems collectively implementing a complete protocol stack. For example, and as shown, network node 110 can be an aggregated network node, meaning that network node 110 can use a radio protocol stack physically and logically integrated within a single node in wireless network 100. For example, aggregated network node 110 can consist of a single standalone base station or a single TRP that uses a complete radio protocol stack to implement or facilitate communication between UE 120 and the core network of wireless network 100.

[0033] Alternatively, and also as shown in the figure, network node 110 can be a decomposed network node (sometimes referred to as a decomposed base station), meaning that network node 110 can use protocol stacks that are physically distributed and / or logically distributed across two or more nodes in the same or different geographical locations. In some deployments, decomposed network node 110 can be used in integrated access and backhaul (IAB) networks, in open radio access networks (O-RAN) (such as network configurations initiated by the O-RAN Alliance), or in virtualized radio access networks (vRAN) (also referred to as cloud radio access networks (C-RAN)) to facilitate scaling of the communication system by decomposing base station functionality into multiple separately deployable units.

[0034] Network nodes 110 of wireless network 100 may include one or more central units (CUs), one or more distributed units (DUs), and / or one or more radio units (RUs). CUs may host one or more higher-layer control functions, such as Radio Resource Control (RRC) functions, Packet Data Convergence Protocol (PDCP) functions, and / or Service Data Adaptation Protocol (SDAP) functions, etc. DUs may host one or more of the Radio Link Control (RLC) layer, MAC layer, and / or one or more high physical (PHY) layers, at least in part, according to functional splits (such as those defined by the 3rd Generation Partnership Project (3GPP)). In some examples, DUs may host one or more low-PHY layer functions, such as Fast Fourier Transform (FFT), Inverse FFT (iFFT), beamforming, Physical Random Access Channel (PRACH) extraction and filtering, and / or scheduling of resources for one or more UEs 120, etc. RUs may host RF processing functions or low-PHY layer functions, such as FFT, iFFT, beamforming, or PRACH extraction and filtering, etc., according to functional splits (such as lower-layer functional splits). In this type of architecture, each RU can be operated to handle over-the-air (OTA) communications with one or more UE 120s.

[0035] In some aspects, network node 110 may include one or more CUs, one or more DUs, one or more RUs, one or more IAB nodes, one or more near real-time (near RT) RAN Intelligent Controllers (RICs), and / or a combination of one or more non-real-time (non-RT) RICs from wireless network 100. In some examples, CUs, DUs, and / or RUs may be implemented as virtual units, such as Virtual Central Units (VCUs), Virtual Distributed Units (VDUs), or Virtual Radio Units (VRUs), etc. Virtual units may be implemented as virtual network functions, such as within a cloud deployment.

[0036] In some examples, network node 110 may be, may include, or operate as a RU, TRP, or base station communicating with one or more UEs 120 via a radio access link (which may be referred to as a "Uu" link). The radio access link may include a downlink and an uplink. A "downlink" (or "DL") refers to the communication direction from network node 110 to UE 120, and an "uplink" (or "UL") refers to the communication direction from UE 120 to network node 110. Downlink channels may include one or more control channels and one or more data channels. Downlink control channels may be used to transmit downlink control information (e.g., scheduling information, reference signals, and / or configuration information) from network node 110 to UE 120. Downlink data channels may be used to transmit downlink data (e.g., user data associated with UE 120) from network node 110 to UE 120. Downlink control channels may include one or more physical downlink control channels (PDCCH), and downlink data channels may include one or more physical downlink shared channels (PDSCH). The uplink channel may include one or more control channels and one or more data channels. The uplink control channel may be used to transmit uplink control information (e.g., corresponding reference signals and / or feedback to one or more downlinks) from UE 120 to network node 110. The uplink data channel may be used to transmit uplink data (e.g., user data associated with UE 120) from UE 120 to network node 110. The uplink control channel may include one or more physical uplink control channels (PUCCH), and the uplink data channel may include one or more physical uplink shared channels (PUSCH). The downlink and uplink may each include a set of resources on which network node 110 and UE 120 can communicate.

[0037] In some examples, wireless network 100 may be configured for half-duplex and / or full-duplex operation. In half-duplex operation, network node 110 and / or UE 120 may transmit or receive communications only during specific time periods (such as specific time slots, symbols, or other time periods). Half-duplex operation may involve time division duplex (TDD), in which the transmissions of network node 110 and UE 120 do not occur in the same time periods (i.e., these transmissions do not overlap in time). For example, in half-duplex operation, wireless communication devices may perform only one of transmission or reception during a specific time period. In full-duplex operation, wireless communication devices (such as network node 110 and / or UE 120) may transmit and receive communications concurrently (e.g., within the same time period). In some examples, full-duplex operation may involve frequency division duplex (FDD), in which the transmissions of network node 110 are performed on a first frequency, and the transmissions of UE 120 are performed on a second frequency different from the first carrier. In FDD, transmissions from network node 110 and UE 120 can be performed concurrently. In some examples, UE 120 can communicate with two network nodes 110 in a configuration that may be referred to as a multi-TRP (mTRP) configuration. In some examples, full-duplex operation can be enabled for UE 120 but not for network node 110. For example, UE 120 can simultaneously send UL transmissions to a first network node 110 and receive DL transmissions from a second network node 110 in the same time instance. In some other examples, full-duplex operation can be enabled for network node 110 but not for UE 120. For example, network node 110 can simultaneously send DL transmissions to a first UE 120 and receive UL transmissions from a second UE 120 in the same time instance. In some examples, full-duplex operation can be enabled for both network node 110 and UE 120. Full-duplex operation increases the capacity of network and radio access links.

[0038] In some examples, UE 120 and network node 110 can perform MIMO communication. "MIMO" generally refers to the simultaneous transmission and reception of multiple data signals (such as multiple layers or multiple data streams) over a radio channel. MIMO can utilize multipath propagation. MIMO can be implemented using spatial processing known as pre-decoding, or it can be implemented using spatial multiplexing. In some examples, MIMO can support simultaneous transmission to multiple receivers, which is called multi-user MIMO (MU-MIMO). Some radio access technologies (RATs) can employ advanced MIMO techniques such as multi-TRP operation (including redundant transmission or reception on multiple TRPs), reciprocity in the time or frequency domain, single-frequency network (SFN) transmission, or noncoherent joint transmission (NC-JT).

[0039] As described above, in some aspects, wireless network 100 may be an IAB network, may include an IAB network, or may be included in an IAB network. In an IAB network, at least one network node 110 may be an anchor network node communicating with the core network via a wired backhaul link (such as a fiber optic connection). Anchor network node 110 may also be referred to as an IAB donor (or IAB-donor), central entity, and / or CU, etc. An IAB network may include one or more non-anchor network nodes 110, sometimes referred to as relay network nodes or IAB nodes (or IAB-nodes). Non-anchor network nodes 110 may communicate directly or indirectly with anchor network node 110 via one or more backhaul links (e.g., via one or more non-anchor network nodes) to form a backhaul path to the core network for carrying backhaul services. In various deployments, the backhaul link may be a radio link. Anchor network node 110 and / or non-anchor network node 110 may also communicate directly with one or more UEs 120 via access links (which may be radio links for carrying access services).

[0040] As described above, an IAB network includes IAB donors that can be connected to a core network via a wired connection (e.g., wired backhaul). For example, the Ng interface of an IAB donor may terminate at the core network. Additionally or alternatively, an IAB donor may connect to one or more devices in the core network that provide core access and mobility management functions (AMF). As described above, an IAB donor may include a CU that performs Access Node Controller (ANC) functions and / or AMF functions. The CU may configure the IAB donor's DU and / or configure one or more IAB nodes (e.g., Mobile Terminal (MT) functions and / or DU functions of the IAB node) connected to the core network via the IAB donor. A link between an IAB donor and an IAB node, or between two IAB nodes, may also be referred to as a backhaul link. In some examples, a backhaul link between an IAB donor and an IAB node, or between two IAB nodes, may be a wireless backhaul link that provides radio access to the core network to the IAB node via the IAB donor and optionally via one or more other IAB nodes. Therefore, the CU of an IAB donor can control and / or configure the entire IAB network (or a portion thereof) connected to the core network via that IAB donor, for example, by using control messages and / or configuration messages (e.g., RRC configuration messages or F1 Application Protocol (F1AP) messages). Access links facilitate communication between UE 120 and the IAB donor or between UE 120 and IAB nodes. For example, network resources used for wireless communication (such as time resources, frequency resources, and / or spatial resources) can be shared between the access link and the backhaul link. The backhaul link can be a primary backhaul link or a secondary backhaul link (e.g., a backup backhaul link). In some respects, a secondary backhaul link can be used if the primary backhaul link fails, becomes congested, and / or becomes overloaded, etc.

[0041] When a first IAB node controls and / or schedules communications for a second IAB node (e.g., when the first IAB node provides DU functionality for the MT functionality of the second IAB node), the first IAB node may be referred to as the parent IAB node of the second IAB node, and the second IAB node may be referred to as the child IAB node of the first IAB node. The child IAB node of the second IAB node may be referred to as the grandchild IAB node of the first IAB node. Therefore, the DU functionality of the parent IAB node can control and / or schedule communications for the child IAB nodes of that parent IAB node. In some examples, the DU functionality may provide limited control over the communications of the grandchild node, such as through indication of soft resources or restricted beams at the child nodes associated with the grandchild node. In some examples, in an IAB network, the DU may be referred to as a scheduling node or scheduling component, and the MT may be referred to as a scheduled node or scheduled component. The parent IAB node may be an IAB donor or an IAB node, and the child IAB node may be an IAB node or a UE 120. Communication of the MT function of a child IAB node can be controlled and / or scheduled by the parent IAB node of that child IAB node.

[0042] Network node 110 for relay communication may be referred to as a relay station, relay network node, or relay. The relay station can receive data transmissions from an upstream station (e.g., network node 110 or UE 120) and transmit data to a downstream station (e.g., UE 120 or network node 110). In this case, the wireless network 100 may include or be referred to as a "multi-hop network." Figure 1 In the example shown, network node 110d (e.g., a relay network node) can communicate with network node 110a (e.g., a macro network node) and UE 120d to facilitate communication between network node 110a and UE 120d. Additionally or alternatively, UE 120 can be a relay station capable of relaying transmissions to or from other UE 120s, or can operate as such a relay station. UE 120 relaying communication can be referred to as a UE repeater or relay UE, etc.

[0043] In some examples, the relay station may include an electromagnetic radiation reflection relay network node 110, which can be used to relay signals from a first network node 110 to a second network node 110 or UE 120. The electromagnetic radiation reflection relay network node 110 may include, for example, a radio frequency reflection array configured to perform radio frequency reflection services. The electromagnetic radiation reflection relay network node 110 may be, for example, a reconfigurable smart surface (RIS) (which may also be referred to as an intelligent reflecting surface (IRS)).

[0044] UE 120 may be physically distributed throughout the wireless network 100, and each UE 120 may be stationary or mobile. UE 120 may be, may include, an access terminal, another terminal, a mobile station, or a subscriber unit, or may be included in an access terminal, another terminal, a mobile station, or a subscriber unit. UE 120 may be, or may include, a cellular phone (e.g., a smartphone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smartwatch, smart clothing, smart glasses, a smart wristband and / or smart jewelry (such as a smart ring or smart bracelet)), an entertainment device (e.g., a music device, a video device and / or a satellite radio), an extended reality (XR) device, a vehicle component or sensor, a smart meter or sensor, industrial manufacturing equipment, a Global Navigation Satellite System (GNSS) device (such as a Global Positioning System device or another type of positioning device), a UE function of a network node, and / or any other suitable device or function that can communicate via a wireless medium, or may be coupled to them.

[0045] UE 120 may include or be included in a housing that houses components associated with UE 120, such as one or more processor components and / or one or more memory components. One or more processor components may be coupled to one or more of the memory components and / or other components. For example, processor components (e.g., one or more processors) and memory components (e.g., one or more memories) may be operatively coupled, communicatively coupled, electronically coupled, or electrically coupled to each other.

[0046] Some UEs 120 may be considered as Machine Type Communication (MTC) UEs or Evolved or Enhanced Machine Type Communication (eMTC) UEs (or Further Enhanced eMTC (feMTC) or Enhanced feMTC (efeMTC) or further evolutions thereof, all of which may be referred to simply as "MTC"). An MTC UE may be, and may include, a robot, unmanned aerial vehicle (UAV), remote device, sensor, instrument, monitor, and / or location tag, or may be included in or coupled to a robot, UAV, remote device, sensor, instrument, monitor, and / or location tag. Some UEs 120 may be considered as IoT devices and / or may be implemented as NB-IoT (Narrowband IoT) devices. IoT UEs or NB-IoT devices can be, and may include, industrial machines, appliances, refrigerators, doorbell cameras, home automation devices and / or lighting fixtures, etc., or may be included in or coupled to industrial machines, appliances, refrigerators, doorbell cameras, home automation devices and / or lighting fixtures, etc. Some UEs 120 can be considered customer premises equipment, which may include telecommunications equipment installed at a customer location (such as a home or office) to enable access to a service provider's network (such as being included in or communicating with the wireless network 100).

[0047] Some UEs 120 can be categorized according to different classes associated with varying levels of complexity and / or capabilities. UEs 120 in the first class can facilitate large-scale IoT within the wireless network 100 and can offer lower complexity and / or cost compared to UEs 120 in the second class. UEs 120 in the second class can include mission-critical IoT devices capable of ultra-reliable low-latency communication (URLLC), enhanced mobile broadband (eMBB), and / or precise location within the wireless network 100, legacy UEs, baseline UEs, high-end UEs, advanced UEs, full-capability UEs, and / or advanced UEs, etc. UEs 120 in the third class may have mid-range complexity and / or capabilities (e.g., capabilities between a UE 120 in the first class and a UE 120 in the second class). UEs 120 in the third class may be referred to as reduced-capability UEs (“RedCap UEs”), mid-range UEs, NR-Light UEs, and / or NR-Lite UEs, etc. RedCap UEs can bridge the gap in capabilities and complexity between NB-IoT devices and / or eMTC UEs and mission-critical IoT devices and / or advanced UEs. RedCap UEs can include, for example, wearable devices, IoT devices, industrial sensors, and / or cameras associated with limited bandwidth, power capacity, and / or transmission range. RedCap UEs can support deployments in healthcare environments, building automation, power distribution, process automation, transportation and logistics, and / or smart cities, among others.

[0048] In some examples, UE 120 in Category 3 (RedCap UE) can support lower latency communication than UE 120 in Category 1 (NB-IoT UE or eMTC UE), and UE 120 in Category 2 (mission-critical IoT UE or advanced UE) can support lower latency communication than UE 120 in Category 3. Additionally or alternatively, in some examples, UE 120 in Category 3 (RedCap UE) can support higher wireless communication throughput than UE 120 in Category 1 (NB-IoT UE or eMTC UE), and UE 120 in Category 2 (mission-critical IoT UE or advanced UE) can support higher wireless communication throughput than UE 120 in Category 3. Additionally or alternatively, in some examples, the UE 120 in the first category (NB-IoT UE or eMTC UE) may support a longer battery life than the UE 120 in the third category (RedCap UE), and the UE 120 in the third category may support a longer battery life than the UE 120 in the second category (mission-critical IoT UE or advanced UE).

[0049] In some examples, a Category 3 UE 120 (RedCap UE) may have the capability to meet a first device or performance requirement (such as parameters specified by Section 4.2.21 of 3GPP Technical Specification 38.306 Version 17) but not a second device or performance requirement (such as parameters specified for NR UE 120 other than Category 3 UE 120, which may be defined by parameters specified by Section 4 of 3GPP Technical Specification 38.306 Version 17), while a Category 2 UE 120 (mission-critical IoT UE or advanced UE) may have the capability to meet the second device or performance requirement (and in some examples, also meet the first device or performance requirement). For example, a Category 3 UE 120 may support a lower maximum modulation and decoding scheme (MCS) (e.g., modulation schemes such as Quadrature Phase Shift Keying (QPSK)) than a Category 2 UE 120 supports. As another example, a Category 3 UE may support a lower maximum transmit power than a Category 2 UE. As another example, a Category 3 UE 120 may have less advanced beamforming capabilities than a Category 2 UE 120 (e.g., a RedCap UE may not be able to form as many beams as an advanced UE). As another example, a Category 3 UE 120 may require a longer processing time than a Category 2 UE 120. As another example, a Category 3 UE 120 may include less hardware or less complex hardware (such as fewer antennas, fewer transmit antennas, and / or fewer receive antennas) than a Category 2 UE 120. As another example, a Category 3 UE 120 may not be able to communicate over the same wide maximum bandwidth portion (BWP) as a Category 2 UE 120.

[0050] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) can communicate directly with each other using sidelink communication (e.g., without communicating through a network node 110 acting as an intermediary). As an example, UE 120a can send data, control information, or other signaling directly to UE 120e as sidelink communication. This contrasts with, for example, UE 120a first sending data to network node 110 in UL communication, and then that network node sending data to UE 120e in DL communication. In various examples, UE 120 can communicate using peer-to-peer (P2P) communication protocols, device-to-device (D2D) communication protocols, vehicle-to-everything (V2X) communication protocols (which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, and / or vehicle-to-pedestrian (V2P) protocols), and / or mesh network communication protocols. In some deployments and configurations, network node 110 may schedule and / or allocate resources for sidelink communication between UEs 120 in wireless network 100. In some other deployments and configurations, UE 120 (instead of network node 110) may perform or cooperate with or negotiate with one or more other UEs to perform scheduling operations, resource selection operations, and / or other operations for sidelink communication.

[0051] Downlink and uplink resources may include time-domain resources (frames, subframes, time slots, and / or symbols), frequency-domain resources (bands, frequency carriers, subcarriers, resource blocks, and / or resource elements), and / or spatial-domain resources (specific transmission directions and / or beam parameters). Frequency-domain resources in some bands may be subdivided into Blocks of Presence (BWPs). A BWP may be a contiguous block of frequency-domain resources allocated to one or more UEs 120 (e.g., a contiguous block of resource blocks). A UE 120 may be configured with both an uplink BWP and a downlink BWP (where the uplink BWP and downlink BWP may be the same BWP or different BWPs). BWPs may be dynamically configured (e.g., configured by sending downlink control information (DCI) to one or more UEs 120 via network node 110) and / or reconfigured, meaning that BWPs can be adjusted in real-time (or near real-time) based on changing network conditions in the radio network 100 and / or based on specific requirements of one or more UEs 120. This allows for more efficient use of available frequency domain resources in the wireless network 100, as fewer frequency domain resources can be allocated to the BWP for UE 120 (which reduces the number of frequency domain resources that UE 120 needs to monitor), thus distributing more frequency domain resources across multiple UE 120s. Therefore, the BWP can also assist in the implementation for such UE 120s by facilitating the configuration of smaller bandwidths for communications performed by lower-capacity UE 120s.

[0052] As indicated above, a BWP can be configured as a subset or part of the total or full component carrier bandwidth, and typically forms or covers a set of consecutive common resource blocks (CRBs) within the full component carrier bandwidth. In other words, within the carrier bandwidth, a BWP begins at a CRB and can span a set of consecutive CRBs. Each BWP can be associated with its own set of parameters (indicating subcarrier spacing (SCS) and cyclic prefix (CP)). UE 120 can be configured with up to four downlink BWPs and up to four uplink BWPs for each serving cell. To achieve reasonable UE battery consumption, under typical operation, only one downlink BWP and one uplink BWP are typically active at a given time on the active serving cell. The active BWP defines the operating bandwidth of UE 120 within the operating bandwidth of the serving cell, while all other BWPs configured on UE 120 are deactivated. On deactivated BWPs, UE 120 does not send or receive any communication.

[0053] Some network nodes 110 (e.g., base stations, RUs, or TRPs) can provide communication coverage for specific geographic areas. In 3GPP, the term "cell" can refer to the coverage area of ​​network node 110 or to network node 110 itself, depending on the context in which the term is used. Network node 110 can support one or more (e.g., three) cells. In some examples, network node 110 can provide communication coverage for macro cells, pico cells, femto cells, or another type of cell. A macro cell can cover a relatively large geographic area (e.g., a radius of several kilometers) and can allow unrestricted access by UE 120 with a service subscription. A pico cell can cover a relatively small geographic area and can allow unrestricted access by UE 120 with a service subscription. A femto cell can cover a relatively small geographic area (e.g., a residential area) and can allow restricted access by UE 120 associated with that femto cell (e.g., UE 120 in a Closed Subscriber Group (CSG)). A network node 110 used for a macro cell may be referred to as a macro network node. Network node 110 used for a pico cell may be referred to as a pico network node. Network node 110 used for a femtocell may be referred to as a femto network node or a home network node. In some examples, the cell may not necessarily be stationary. For example, the geographical area of ​​the cell may be mobile based on the location of the associated mobile network node 110 (e.g., a train, satellite base station, unmanned aerial vehicle, or non-terrestrial network (NTN) network node).

[0054] Wireless network 100 can be a heterogeneous network, comprising different types of network nodes 110, such as macro network nodes, piconet nodes, femtonet nodes, relay network nodes, aggregation network nodes, and / or decomposition network nodes, etc. Figure 1In the example shown, network node 110a can be a macro network node for macro cell 130a, network node 110b can be a pico network node for pico cell 130b, and network node 110c can be a femto network node for femto cell 130c. Various types of network nodes 110 can typically transmit at different power levels, serve different coverage areas, and / or have different interference effects on the wireless network 100 compared to other types of network nodes 110. For example, macro network nodes can have high transmit power levels (e.g., 5 watts to 40 watts), while pico network nodes, femto network nodes, and relay network nodes can have lower transmit power levels (e.g., 0.1 watts to 2 watts).

[0055] As indicated above, network node 110 can be a terrestrial network node 110 (e.g., an entity of a terrestrial base station or a distributed base station) or an NTN network node 110. For example, wireless network 100 may include one or more NTN deployments, which may include non-terrestrial network nodes, NTN network nodes 110, and / or relay stations. In some examples, a relay station in an NTN deployment may be referred to as a "non-terrestrial relay station." NTN can facilitate access to wireless network 100 for remote areas (such as waterborne or remote areas where no terrestrial network is deployed) that might otherwise be outside the coverage area of ​​terrestrial network node 110. NTN can provide connectivity for a variety of applications, including satellite communications, IoT, MTC, and / or other applications. NTN network node 110 may include satellites, manned spacecraft systems, or unmanned aerial vehicle system (UAS) platforms, etc. Satellites may include low Earth orbit (LEO) satellites, medium Earth orbit (MEO) satellites, geostationary orbit (GEO) satellites, and / or highly elliptical orbit (HEO) satellites, etc. Manned aircraft systems may include airplanes, helicopters, and / or airships, etc. UAS platforms may include high altitude platform stations (HAPS), balloons, airships, and / or airplanes, etc.

[0056] NTN network node 110 can communicate directly and / or indirectly with other entities in wireless network 100 using NTN communications. Other entities may include UE 120, other NTN network nodes 110 in one or more NTN deployments, other types of network nodes 110 (e.g., stationary, terrestrial, and / or terrestrial-based network nodes), relay stations, and / or one or more components and / or devices included in and / or coupled to the core network of wireless network 100. For example, NTN network node 110 may communicate with UE 120 via a serving link (e.g., where the serving link includes an access link). Additionally or alternatively, NTN network node 110 may communicate with a gateway (e.g., a terrestrial node providing connectivity to a data network or core network for NTN network node 110) via a feeder link (e.g., where the feeder link is associated with an N2 or N3 interface). Additionally or alternatively, NTN network node 110 may communicate directly with each other via an inter-satellite link (ISL). NTN deployments can be transparent (e.g., where NTN network node 110 operates in a manner similar to a repeater or trunk and / or where access links do not terminate at NTN network node 110) or regenerative (e.g., where NTN network node 110 regenerates signals and / or where access links terminate at NTN network node 110).

[0057] In some examples, UE 120 may implement power-saving features, such as for UE 120 in RRC connected mode, RRC idle mode, or RRC inactive mode. Power-saving features may include, for example, relaxed radio resource monitoring (such as for devices operating in low mobility or good radio conditions), discontinuous reception (DRX), reduced PDCCH monitoring during active time, and / or power-efficient paging reception.

[0058] UE 120 may operate in association with a DRX configuration (e.g., indicated to UE 120 by network node 110). DRX operation allows UE 120 to enter sleep mode at various times while within the coverage area of ​​network node 110, thereby reducing power consumption to conserve battery resources, etc. The DRX configuration typically configures UE 120 to operate in association with a DRX cycle. UE 120 may repeat the DRX cycle periodically according to the DRX configuration. A DRX cycle may include a DRX-enabled duration during which UE 120 is in wake-up mode or active, and one or more durations during which UE 120 may operate in an inactive state, which may provide an opportunity for UE 120 to enter a DRX sleep mode in which UE 120 may suppress monitoring of communications from network node 110. Additionally or alternatively, UE 120 may disable one or more antennas, RF chains, and / or other hardware components or devices while operating in DRX sleep mode.

[0059] The time during which UE 120 is configured to be active during the DRX enable duration can be referred to as the active time, and the time during which UE 120 is configured to be inactive, such as during the DRX sleep duration, can be referred to as the inactive time. During the DRX enable duration, UE 120 may monitor downlink communication from one or more network nodes 110. If UE 120 does not detect and / or successfully decode any downlink communication during the DRX enable duration, UE 120 may enter DRX sleep mode for the inactive duration at the end of the DRX enable duration. Conversely, if UE 120 detects and / or successfully decodes downlink communication during the DRX enable duration, UE 120 may remain active for the duration of the DRX inactive timer (this may extend the active time). UE 120 may start the DRX inactive timer at the time downlink communication is received. UE 120 may remain active until the DRX inactive timer expires, at which point UE 120 may transition to sleep mode for the inactive duration. Additionally or alternatively, UE 120 may use a DRX cycle known as an extended DRX (eDRX) cycle, such as for use cases that tolerate latency. An eDRX cycle may include a relatively long period of inactivity relative to a baseline DRX cycle (e.g., an eDRX cycle may have a lower ratio of active time to inactive time).

[0060] Network nodes 110 and UEs 120 of wireless network 100 can communicate using the electromagnetic spectrum, which can be subdivided into various categories, frequency bands, carriers, and / or channels according to frequency or wavelength. For example, devices of wireless network 100 can communicate using one or more operating frequency bands. In some aspects, multiple wireless networks 100 can be deployed in a given geographical area. Each wireless network 100 can support a specific RAT (which may also be referred to as an air interface) and can operate on one or more carrier frequencies in one or more frequency ranges. Examples of RATs include 4G RAT, 5G / NR RAT, and / or 6G RAT, etc. In some examples, when multiple RATs are deployed in a given geographical area, each RAT in that geographical area can operate on a different frequency to avoid interference with each other.

[0061] Various operating frequency bands have been defined as frequency ranges designated FR1 (410 MHz to 7.125 GHz), FR2 (24.25 GHz to 52.6 GHz), FR3 (7.125 GHz to 24.25 GHz), FR4a or FR4-1 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Although a portion of FR1 is greater than 6 GHz, in some documents and articles, FR1 is often (interchangeably) referred to as the “sub-6 GHz” band. Similarly, in some documents and articles, FR2 is often (interchangeably) referred to as the “millimeter wave” band, but this is different from the Extremely High Frequency (EHF) band (30 GHz to 300 GHz) designated as “millimeter wave” by the International Telecommunication Union (ITU). The frequencies between FR1 and FR2 are generally referred to as the mid-band frequencies, including FR3. Frequency bands falling within FR3 can inherit FR1 or FR2 characteristics, thereby effectively extending the characteristics of FR1 or FR2 to mid-band frequencies. Therefore, "below 6 GHz" (if used herein) can broadly refer to frequencies less than 6 GHz, within FR1, and / or included in mid-band frequencies. Similarly, the term "millimeter wave" (if used herein) can broadly refer to frequencies included in mid-band frequencies, within FR2, FR4, FR4-a, FR4-1, or FR5, and / or within the EHF band. Higher frequency bands can extend 5G NR operation, 6G operation, and / or other RATs above 52.6 GHz. For example, each of FR4a, FR4-1, FR4, and FR5 falls within the EHF band. In some examples, Wireless Network 100 can implement Dynamic Spectrum Sharing (DSS), where multiple RATs (e.g., 4G / LTE and 5G / NR) are implemented within a single frequency band using dynamic bandwidth allocation (e.g., based on user demand). It is conceivable that the frequencies included in these operating frequency bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1 and / or FR5) can be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0062] In some aspects, the UE (e.g., UE 120) may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may: transmit UE capability information indicating the UE's capability associated with activation of at least one TCI associated with a candidate cell prior to reception of a beam indication associated with a candidate cell in a set of cells configured for LTM operation; receive configuration information corresponding to LTM operation; and perform LTM handover operations based on the configuration information and at least one TCI. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0063] In some aspects, a network node (e.g., network node 110) may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may: receive UE capability information indicating the UE's capabilities associated with the activation of at least one TCI associated with a candidate cell prior to the transmission of a beam indication associated with a candidate cell in a set of cells configured for LTM operation; transmit configuration information corresponding to the LTM operation; and perform an LTM handover operation based on the configuration information and at least one TCI. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0064] Figure 2 This is a diagram illustrating an example network node 210 communicating with an example UE 220 in a wireless network according to the present disclosure. Figure 2 Network node 210 can be a reference Figure 1 The example described is network node 110. Similarly, UE 220 can be a reference. Figure 1 An example of the described UE 120.

[0065] like Figure 2 As shown, network node 210 may include a data source 212, a transmit processor 214, a transmit (TX) multiple-input multiple-output (MIMO) processor 216, a set of modems 232 (shown as 232a to 232t, where t≥1), a set of antennas 234 (shown as 234a to 234v, where v≥1), a MIMO detector 236, a receive processor 238, a data sink 239, a controller / processor 240, a memory 242, a communication unit 244, a scheduler 246, and / or a communication manager 150, etc. In some configurations, one or a combination of antennas 234, modems 232, MIMO detectors 236, receive processors 238, transmit processors 214, and / or TX MIMO processors 216 may be included in the transceiver of network node 210. The transceiver may be under the control of and used by a processor (such as controller / processor 240), and in some respects, may perform aspects of the methods, procedures, and / or operations described herein in conjunction with processor-readable code stored in memory 242. In some respects, network node 210 may include one or more interfaces, communication components, and / or other components that facilitate communication with UE 220 or another network node.

[0066] The terms “processor,” “controller,” or “controller / processor” can refer to one or more controllers and / or one or more processors. For example, references to “a / the processor,” “a / the controller / processor,” etc. (in the singular) should be understood as referring to a combination of… Figure 2 The processor described refers to any one or more processors, such as a single processor or a combination of multiple different processors. The reference to "one or more processors" should be understood as a combination of references. Figure 2 Any one or more processors described herein. For example, one or more processors of network node 210 may include transmit processor 214, TX MIMO processor 216, MIMO detector 236, receive processor 238, and / or controller / processor 240. Similarly, one or more processors of UE 220 may include MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, and / or controller / processor 280. As used herein, “processor,” “controller,” or “controller / processor” may refer to a general-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic unit, discrete hardware component, or any combination thereof. A general-purpose processor may be a microprocessor, or any commercially available processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors working in conjunction with a DSP core, a system-on-a-chip (SoC), or any other such configuration).

[0067] In some respects, a single processor can perform all operations described as being performed by that one or more processors. In other respects, the one or more processors can jointly perform a set of functions. For example, a first group(s) of the one or more processors can perform a first function described as being performed by that one or more processors, and a second group(s) of the one or more processors can perform a second function described as being performed by that one or more processors. The first group and the second group of processors can be the same group of processors or can be different groups of processors. The reference to "one or more processors" should be understood as referring to a combination Figure 2 Any one or more processors described. The reference to "one or more memories" should be understood to mean any one or more memories of the corresponding device, such as those in conjunction with... Figure 2 The memory described. For example, a function described as being performed by one or more memories can be performed by the same subset of the one or more memories or by different subsets of the one or more memories.

[0068] For downlink communication from network node 210 to UE 220, transmitting processor 214 may receive data (“downlink data”) intended for use by UE 220 (or a set of UEs including UE 220) from data source 212 (such as a data pipeline or data queue). In some examples, transmitting processor 214 may select one or more MCSs for UE 220 based on one or more Channel Quality Indicators (CQIs) received from UE 220. Network node 210 may process the data (e.g., including encoding the data) based on the MCS selected for UE 220 for transmission to UE 220 on the downlink, thereby generating data symbols. Transmitting processor 214 may process system information (e.g., semi-static resource partitioning information (SRPI)) and / or control information (e.g., CQI requests, grants, and / or upper-layer signaling) and provide overhead symbols and / or control symbols. The transmitting processor 214 can generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS), demodulation reference signals (DMRS), or channel state information (CSI) reference signals (CSI-RS)) and / or synchronization signals (e.g., primary synchronization signal (PSS) or secondary synchronization signal (SSS)).

[0069] The TX MIMO processor 216 can perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and can provide a set of output symbol streams (e.g., T output symbol streams) to a set of modems 232. For example, each output symbol stream can be provided to a corresponding modulator component (shown as MOD) of modem 232. Each modem 232 can use the corresponding modulator component to process (e.g., modulate) the corresponding output symbol stream (e.g., for Orthogonal Frequency Division Multiplexing (OFDM)) to obtain an output sample stream. Each modem 232 can further use the corresponding modulator component to process (e.g., convert to analog, amplify, filter, and / or up-convert) the output sample stream to obtain a time-domain downlink signal. Modems 232a to 232t can transmit a set of downlink signals (e.g., T downlink signals) together via a set of corresponding antennas 234.

[0070] Downlink signaling may include DCI communication, MAC-CE communication, RRC communication, downlink reference signaling, or another type of downlink communication. Downlink signaling may be transmitted on the PDCCH, PDSCH, and / or another downlink channel. Downlink signaling may carry one or more transport blocks (TBs) of data. A TB may be a data unit transmitted via the air interface in wireless network 100. A data stream (e.g., from data source 212) may be encoded into multiple TBs for transmission via the air interface. The number of TBs used to carry data associated with a particular data stream may be associated with a TB size shared by multiple TBs. The TB size may be based on the radio channel conditions of the air interface, the MCS used to encode the data, downlink resources allocated for transmitting data, and / or other parameters, or otherwise associated with them. Generally, a larger TB size allows for a larger amount of data to be transmitted in a single transmission, reducing signaling overhead. However, a larger TB size may be more prone to transmission and / or reception errors than a smaller TB size, but such errors can be mitigated through more robust error correction techniques.

[0071] For uplink communication from UE 220 to network node 210, the uplink signal from UE 220 may be received by antenna 234, processed by modem 232 (e.g., demodulator component of modem 232, shown as DEMOD), detected where applicable by MIMO detector 236 (e.g., receive (Rx) MIMO processor), and / or further processed by receive processor 238 to obtain decoded data and / or control information. Receive processor 238 may provide the decoded data to data sink 239 (which may be a data pipeline, data queue, and / or another type of data sink) and provide the decoded control information to processors such as controller / processor 240.

[0072] Network node 210 may use scheduler 246 to schedule one or more UEs 220 for downlink or uplink communication. In some aspects, scheduler 246 may use DCI to dynamically schedule DL transmissions to and / or UL transmissions from UE 220. In some examples, scheduler 246 may allocate repetitive time-domain and / or frequency-domain resources that UE 220 may use for transmission and / or reception of communication using RRC configuration (e.g., semi-static configuration), for example, to perform semi-persistent scheduling (SPS) or to configure configuration grant (CG) for UE 220.

[0073] One or more of the following may be included in the RF chain of network node 210: transmit processor 214, TX MIMO processor 216, modem 232, antenna 234, MIMO detector 236, receive processor 238, and / or controller / processor 240. The RF chain may include filters, mixers, oscillators, amplifiers, analog-to-digital converters (ADCs), and / or other devices for converting analog signals (such as those used for transmission or reception via an air interface) to digital signals (such as those used for processing by one or more processors of network node 210). In some aspects, the RF chain may be a transceiver of network node 210, or may be included in such a transceiver.

[0074] In some examples, network node 210 may use communication unit 244 to communicate with the core network and / or other network nodes. Communication unit 244 may support wired and / or wireless communication protocols and / or connections, such as Ethernet, fiber optic, Common Public Radio Interface (CPRI), and / or wired or wireless backhaul, etc. Network node 210 may use communication unit 244 to send and / or receive data associated with UE 220, or to execute network control signaling, etc. Communication unit 244 may include transceivers and / or interfaces, such as network interfaces.

[0075] UE 220 may include a set of antennas 252 (shown as antennas 252a to 252r, where r ≥ 1), a set of modems 254 (shown as modems 254a to 254u, where u ≥ 1), a MIMO detector 256, a receive processor 258, a data sink 260, a data source 262, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, a memory 282, and / or a communication manager 140, etc. One or more components of UE 220 may be included in housing 284. In some aspects, one or a combination of antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, or TX MIMO processor 266 may be included in a transceiver included in UE 220. The transceiver may be under the control of and used by a processor (such as controller / processor 280), and in some respects, may perform aspects of the methods, procedures, or operations described herein in conjunction with processor-readable code stored in memory 282. In some respects, UE 220 may include another interface, another communication component, and / or another component that facilitates communication with network node 210 and / or another UE 220.

[0076] For downlink communication from network node 210 to UE 220, the set of antennas 252 can receive downlink communication or signals from network node 210 and can provide a set of received downlink signals (e.g., R received signals) to a set of modems 254. For example, each received signal can be provided to a corresponding demodulator component (shown as DEMOD) of modem 254. Each modem 254 can use the corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain an input sample. Each modem 254 can use the corresponding demodulator component to further demodulate or process the input sample (e.g., for OFDM) to obtain a received symbol. MIMO detector 256 can obtain the received symbols from the set of modems 254, can perform MIMO detection on the received symbols where applicable, and can provide the detected symbols. The receiver processor 258 can process (e.g., decode) the detected symbols, provide the decoded data for the UE 220 to the data sink 260 (such as a data pipeline, data queue and / or an application running on the UE 220), and provide the decoded control information and system information to the controller / processor 280.

[0077] For uplink communication from UE 220 to network node 210, transmitting processor 264 may receive and process data (“uplink data”) from data source 262 (such as data pipelines, data queues, and / or applications running on UE 220) and control information from controller / processor 280. The control information may include one or more parameters, feedback, one or more signal measurements, and / or other types of control information. In some aspects, receiving processor 258 and / or controller / processor 280 may determine one or more parameters related to the transmission of uplink communication for received signals (such as those received from network node 210 or another UE). One or more parameters may include a Reference Signal Received Power (RSRP) parameter, a Received Signal Strength Indicator (RSSI) parameter, a Reference Signal Received Quality (RSRQ) parameter, a CQI parameter, or a Transmit Power Control (TPC) parameter, etc. The control information may include indications of RSRP, RSSI, RSRQ, CQI, TPC, and / or another parameter. Control information can facilitate parameter selection and / or scheduling for UE 220 by network node 210.

[0078] Transmit processor 264 can generate reference symbols for one or more reference signals, such as uplink DMRS, uplink sounding reference signal (SRS), and / or another type of reference signal. Symbols from transmit processor 264 can be pre-decoded by TX MIMO processor 266 (where applicable) and further processed by an assembly of modems 254 (e.g., for DFT-s-OFDM or CP-OFDM). TX MIMO processor 266 can perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols (where applicable) and can provide an assembly of output symbol streams (e.g., R output symbol streams) to the assembly of modems 254. For example, each output symbol stream can be provided to a corresponding modulator component (shown as MOD) of modem 254. Each modem 254 can use the corresponding modulator component to process (e.g., modulate) the corresponding output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modem 254 may further use a corresponding modulator component to process (e.g., convert to analog, amplify, filter, and / or upconvert) the output sample stream to obtain an uplink signal.

[0079] Modems 254a to 254r can transmit a set of uplink signals (e.g., R uplink signals) via a set of corresponding antennas 252. Uplink signals may include uplink control information (UCI) communication, MAC-CE communication, RRC communication, or another type of uplink communication. Uplink signals can be transmitted on PUSCH, PUCCH, and / or another type of uplink channel. Uplink signals can carry one or more TBs of data. Sidelink data and control transmission (i.e., transmission directly between two or more UEs 220) typically uses techniques similar to those described for uplink data and control transmission and may use sidelink-specific channels such as the Physical Sidelink Shared Channel (PSSCH), Physical Sidelink Control Channel (PSCCH), and / or Physical Sidelink Feedback Channel (PSFCH).

[0080] One or more antennas in the set of antennas 252 or the set of antennas 234 may include one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, etc., or may be included in one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, or antenna arrays may include one or more antenna elements (within a single housing or multiple housings), a set of coplanar antenna elements, a set of non-coplanar antenna elements, or with one or more transmitting or receiving components (such as...) Figure 2An antenna module is a combination of one or more antenna elements coupled to one or more components. As used herein, "antenna" can mean one or more antennas, one or more antenna panels, one or more antenna groups, one or more collections of antenna elements, or one or more antenna arrays. "Antenna panel" can mean a group of antennas (such as antenna elements) arranged in an array or panel that can facilitate beamforming by manipulating the parameters of that group of antennas. "Antenna module" can mean a circuit that includes one or more antennas, and may also include one or more other components (such as filters, amplifiers, or processors) associated with integrating the antenna module into a wireless communication device.

[0081] In some examples, each antenna element of antenna 234 or antenna 252 may include one or more sub-elements for radiating or receiving radio frequency signals. For example, a single antenna element may include a first sub-element cross-polarized with a second sub-element, which can be used to independently transmit cross-polarized signals. Antenna elements may include patch antennas, dipole antennas, and / or other types of antennas arranged in a linear pattern, a two-dimensional pattern, or another pattern. The spacing between antenna elements can allow signals with a desired wavelength transmitted individually by the antenna elements to interact or interfere (e.g., to form a desired beam) in various directions. For example, given a desired wavelength or frequency range, the spacing may provide a quarter wavelength, half a wavelength, or another fraction of the wavelength between adjacent antenna elements to allow desired constructive and destructive interference modes of signals transmitted by individual antenna elements within that desired range.

[0082] The amplitude and / or phase of signals transmitted via antenna elements and / or sub-elements can be modulated and (e.g., by manipulating phase shifts, phase offsets, and / or amplitudes) shifted relative to each other to generate one or more beams; this is known as beamforming. The term "beam" can refer to the directional transmission of a wireless signal toward a receiving device or otherwise in a desired direction. "Beam" can also generally refer to the direction associated with such directional signal transmission, the set of directional resources associated with the signal transmission (e.g., angle of arrival, horizontal direction, and / or vertical direction), and / or a set of parameters indicating one or more aspects of the directional signal, the direction associated with the signal, and / or the set of directional resources associated with the signal. In some implementations, antenna elements can be individually selected or deselected for the directional transmission of a signal (or multiple signals) by controlling the amplitude of one or more corresponding amplifiers and / or the phase of the signal to form one or more beams. The shape of the beam (such as amplitude, width, and / or the presence of sidelobes) and / or the direction of the beam (such as the angle of the beam relative to the surface of the antenna array) can be dynamically controlled by modifying the phase shifts, phase offsets, and / or amplitudes of multiple signals relative to each other.

[0083] Different UEs 220 or network nodes 110 may include different numbers of antenna elements. For example, UE 220 may include a single antenna element, two antenna elements, four antenna elements, eight antenna elements, or different numbers of antenna elements. As another example, network node 210 may include eight antenna elements, 24 antenna elements, 64 antenna elements, 128 antenna elements, or different numbers of antenna elements. Generally speaking, a larger number of antenna elements provides increased control over the parameters used for beamforming compared to a smaller number of antenna elements, while a smaller number of antenna elements may be less complex to implement and can use less power. Multiple antenna elements can support multi-layer transmission, in which the same time and frequency resources are used to utilize spatial multiplexing to transmit a first layer of communication (which may include a first data stream) and a second layer of communication (which may include a second data stream).

[0084] Network node 210 may provide UE 220 with a configuration of TCI states, which may be indicated by or correspond to beams used by UE 220 for receiving one or more communications via physical channels. For example, network node 210 may (e.g., using DCI) indicate an active TCI state to UE 220, which UE 220 may use to generate beams for receiving one or more communications via physical channels. Beam indications may be, or may include, TCI state information elements, beam identifiers (IDs), spatial relationship information, TCI state IDs, closed-loop indexes, panel IDs, TRP IDs, and / or SRS set IDs, etc. TCI state information elements (sometimes referred to herein as TCI states) may indicate specific information associated with a beam. For example, TCI status information elements can indicate a TCI status identifier (e.g., tci-StateID), quasi-co-location (QCL) type (e.g., qcl-Type1, qcl-Type2, qcl-TypeA, qcl-TypeB, qcl-TypeC, or qcl-TypeD, etc.), cell identifier (e.g., ServCellIndex), bandwidth portion identifier (bwp-Id), or reference signal identifier (such as CSI-RS identifier (e.g., NZP-CSI-RS-ResourceId or SSB-Index, etc.)). Spatial relationship information can similarly indicate information associated with the uplink beam. Beam indication can be a joint or separate DL / UL beam indication within a unified TCI framework. Within a unified TCI framework, the network can support common TCI status ID updates and activations, which can provide common QCL and / or common UL transmit spatial filters across a set of configured component carriers. This type of beam indication is applicable to in-band carrier aggregation and to both joint and separate DL / UL beam indications. The Common TCI Status ID can refer to a reference signal determined based on the TCI status indicated by the Common TCI Status ID, which is used to provide QCL Type D indication and to determine the UL transmit space filter across the configured CC set.

[0085] In some examples, the network may use at least a UE-specific (unicast) DCI to indicate a combined or individual DL / UL beam indication selectable from the active TCI state, thereby supporting Layer 1 (L1) based beam indication. In some examples, DCI formats 1_1 and / or 1_2 may be used for beam indication. Network node 210 may include a support mechanism for UE 220 to acknowledge successful decoding of the beam indication. For example, acknowledgment / negation of a PDSCH scheduled by a DCI carrying the beam indication may also be used as acknowledgment for the DCI.

[0086] Further efficiency improvements in throughput, signal strength, and / or other signal properties can be achieved through beam refinement. For example, network node 210 may be able to communicate with UE 220 using beams of various beamwidths. For instance, network node 210 may be configured to utilize a wider beam to communicate with UE 220 when UE 220 is in motion, as wider coverage increases the likelihood that UE 220 will remain within the coverage area of ​​network node 210 while moving. Conversely, when UE 220 is stationary, network node 210 uses a narrower beam to communicate with UE 220, as network node 210 can reliably focus coverage on UE 220, and the likelihood of UE 220 moving out of the coverage area of ​​network node 210 is low or minimal. In some examples, to select a specific beam for communicating with UE 220, network node 210 may transmit reference signals, such as synchronization signal blocks (SSBs) or CSI-RS, in a beam-sweeping manner on each of multiple beams. In some examples, the SSB can be transmitted on a wider beam, while the CSI-RS can be transmitted on a narrower beam. The UE 220 can measure the RSRP or signal-to-interference-plus-noise ratio (SINR) on each of the beams and send a beam measurement report (e.g., an L1 measurement report) to the network node 210 indicating the RSRP or SINR associated with each of one or more of the measured beams. The network node 210 can then select a specific beam for communicating with the UE 220 based on the L1 measurement report. In some other examples, when channel reciprocity exists between the uplink and downlink, the network node 210 can derive a specific beam for communicating with the UE 220 (e.g., on both the uplink and downlink) based on uplink measurements of one or more uplink reference signals (such as SRS) transmitted by the UE 220.

[0087] One enhancement for multi-beam operation at higher carrier frequencies is to facilitate efficient (e.g., low latency and low overhead) downlink and / or uplink beam management operations to support higher Layer 1 and / or Layer 2 (L1 / L2) centered inter-cell mobility. L1 and / or L2 signaling, referred to as “lower-layer” signaling, can be used to activate and / or deactivate candidate cells in a set of cells configured for L1 / L2 mobility, and / or provide reference signals for measurement by UE 220, which can then select candidate beams as target beams for lower-layer handover operations. Therefore, one objective of L1 / L2 centered inter-cell mobility is to enable UEs to perform cell handover via dynamic control signaling at lower layers (e.g., DCI for L1 signaling or MAC CE for L2 signaling) instead of semi-static Layer 3 (L3) RRC signaling, in order to reduce latency, lower overhead, and / or otherwise improve the efficiency of cell handover.

[0088] In some examples, for UE 220, one antenna panel can be used for UL transmission and another for DL ​​reception. In some examples, full-duplex communication can be conditional on beam separation of the UL and DL beams at the respective antenna panels. Utilizing full-duplex communication can reduce latency, making it possible to receive DL signals in UL-only time slots, thus achieving latency savings. Furthermore, full-duplex communication can enhance spectral efficiency per cell or per UE 220 and enable more efficient resource utilization. Beam separation of the UL and DL beams helps limit or reduce self-interference that may occur during full-duplex communication. Separating the UL and DL beams on their respective antenna panels can provide reliable full-duplex communication by minimizing or reducing self-interference.

[0089] Full-duplex UE 220 can perform a self-interference measurement (SIM) procedure to identify self-interference from transmissions of full-duplex UE 220. Full-duplex network node 210 can also perform a SIM procedure to identify self-interference from transmissions of full-duplex network node 210. UE 220 can provide a measurement report to network node 210 to indicate the results of the UE SIM. Network node 210 can select multiple beam pairs (referred to herein as "beam pairs") for use during full-duplex communication for UE 220 ("UE beam pair") and network node 210 ("network node beam pair"). Beam pairs typically include receive (Rx) beams and transmit (Tx) beams, such as DL beams and UL beams for UE 220, and similarly, UL beams and DL beams for network node 210.

[0090] Figure 3This is an illustration of an example disaggregated base station architecture 300 according to the present disclosure. One or more components of the example disaggregated base station architecture 300 may be one or more network nodes (such as one or more network nodes 110 or one or more network nodes 210), may include, or may be included in one or more network nodes. The disaggregated base station architecture 300 may include a CU 302, which may communicate directly with the core network 304 via a backhaul link, or indirectly with the core network 304 via one or more disaggregated control units (such as a near-RT RIC 306 via an E2 link, or a non-RT RIC 308 associated with a Service Management and Orchestration (SMO) framework 310, or both). The CU 302 may communicate with one or more DUs 312 via a corresponding midhaul link (such as via an F1 interface). Each DU in the DU 312 may communicate with one or more RUs 314 via a corresponding fronthaul link. Each RU in the RU 314 may communicate with one or more UEs 316 via a corresponding RF access link. In some deployments, UE 316 can be served by multiple RU 314 simultaneously.

[0091] Each component of the decomposed base station architecture 300 (including CU 302, DU 312, RU 314) as well as the near-RT RIC 306, non-RT RIC 308 and SMO framework 310 may include one or more interfaces or may be coupled to one or more interfaces for receiving or transmitting signals, data or information (collectively referred to as signals) via wired or wireless transmission media.

[0092] In some aspects, the CU 302 can host one or more higher-level control functions. Such control functions may include RRC functions, PDCP functions, or SDAP functions, etc. Each control function can be implemented using an interface for signaling to other control functions hosted by the CU 302. The CU 302 can handle user plane functions (e.g., Central Unit-User Plane (CU-UP) functions) and / or control plane functions (e.g., Central Unit-Control Plane (CU-CP) functions). In some implementations, the CU 302 can be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 302 can be deployed to communicate with one or more DU 312s for network control and signaling as needed.

[0093] Each DU 312 may correspond to a logic unit including one or more base station functions for controlling the operation of one or more RU 314s. In some aspects, the DU 312 may at least partially host one or more of the RLC layer, MAC layer, and one or more high PHY layers according to functional splits such as those defined by 3GPP. In some implementations, the one or more high PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, and modulation and demodulation, etc. In some implementations, the DU 312 may further host one or more low PHY layers, such as those implemented by one or more modules for FFT, iFFT, digital beamforming, or PRACH extraction and filtering, etc. Each layer (which may also be referred to as a module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by the DU 312 or with control functions hosted by the CU 302.

[0094] Each RU 314 can implement low-level functionality. In some deployments, an RU 314 controlled by a DU 312 can correspond to a logical node that hosts RF processing functions or low-PHY layer functions, such as performing FFT, performing iFFT, digital beamforming, or PRACH extraction and filtering, based on function splitting (e.g., function splitting defined by 3GPP) (such as low-level function splitting). In this architecture, each RU 314 can be operated to handle OTA communication with one or more UEs 316. In some specific implementations, the real-time and non-real-time aspects of control plane and user plane communication with the RU 314 can be controlled by the corresponding DU 312. In some deployments, this configuration allows each DU 312 and CU 302 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0095] The SMO framework 310 supports RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 310 supports the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operation and maintenance interfaces such as the O1 interface. For virtualized network elements, the SMO framework 310 can interact with cloud computing platforms such as the Open Cloud (O-Cloud) platform 318 to perform network element lifecycle management (such as instantiating virtualized network elements) via cloud computing platform interfaces such as the O2 interface. Such virtualized network elements may include, but are not limited to, CU 302, DU 312, RU 314, non-RT RIC 308, and near-RT RIC 306. In some implementations, the SMO framework 310 can communicate with hardware aspects of the 4G RAN, 5G NR RAN, and / or 6G RAN (such as the Open eNB (O-eNB) 320) via the O1 interface. Additionally, in some implementations, the SMO framework 310 can communicate directly with each of one or more RUs 314 via a corresponding O1 interface. The SMO framework 310 may also include a non-RTRIC 308 that supports the functionality of the SMO framework 310.

[0096] The non-RT RIC 308 may include or implement logic functions that enable non-real-time control and optimization of RAN elements and resources, including artificial intelligence / machine learning (AI / ML) workflows for model training and updates, or policy-based guidance for applications / features in the near-RT RIC 306. The non-RT RIC 308 may be coupled to or communicate with the near-RT RIC 306, such as via an A1 interface. The near-RT RIC 306 may include or implement logic functions that enable near real-time control and optimization of RAN elements and resources via an interface, such as via an E2 interface, through data collection and action, connecting one or more CUs 302, one or more DUs 312, or both, and an O-eNB 320 to the near-RT RIC 306.

[0097] In some implementations, to generate AI / ML models to be deployed in the near-RT RIC 306, the non-RT RIC 308 may receive parameters or external enrichment information from an external server. This information can be utilized by the near-RT RIC 306 and can be received from non-network data sources or network functions at the SMO framework 310 or the non-RT RIC 308. In some examples, the non-RT RIC 308 or the near-RT RIC 306 may modulate RAN behavior or performance. For example, the non-RT RIC 308 may monitor long-term trends and patterns in performance and employ AI / ML models to perform corrective actions via the SMO framework 310 (such as reconfiguration via the O1 interface) or via the creation of RAN management policies (such as A1 interface policies).

[0098] The controller / processor 240 of network node 110 and network node 210, and the controller / processor 280 of UE 120 and UE 220. Figure 3 CU 302, Figure 3 DU 312, Figure 3 RU 340 or Figure 1 , Figure 2 or Figure 3 Any other component may implement one or more techniques associated with beam indication for candidate cell groups in LTM operations or perform one or more operations associated with beam indication for candidate cell groups in LTM operations, as described in more detail elsewhere herein. For example, the controller / processor 240 of network node 210, the controller / processor 280 of UE 220, or... Figure 2 Any other component may be operable to perform or direct, for example Figure 6 Process 600 Figure 7 The operation of process 700 or other processes as described herein. Memory 242 and memory 282 may store data and program code for network nodes 110 / 210 and UE 120 / 220, respectively. In some examples, memory 242 or memory 282 may include a non-transitory computer-readable medium storing a set of instructions (e.g., code or program code) for wireless communication. Memory 242 may include one or more memories, such as a single memory or multiple different memories (of the same or different types). Memory 282 may include one or more memories, such as a single memory or multiple different memories (of the same or different types). For example, the set of instructions is stored by network node 210, UE 220, Figure 3 CU 302, Figure 3 DU 312 or Figure 3 One or more processors of the RU 340 may execute (e.g., directly, or after compilation, transformation, or interpretation) when they are executed. Figure 6 Process 600 Figure 7 The process 700 or other processes as described herein. In some examples, the instructions to be executed may include run instructions, translation instructions, compilation instructions, or interpretation instructions, etc. As used herein, “processor,” “controller,” or “controller / processor” may refer to a general-purpose processor, DSP, ASIC, FPGA, or other PLD, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof. While a general-purpose processor may be a microprocessor, in alternatives, a processor may be any commercially available processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors working in conjunction with a DSP core, a system-on-a-chip (SoC), or any other such configuration).

[0099] In some aspects, a UE (e.g., UE 220) includes: components for transmitting UE capability information indicating the UE's capability associated with activation of at least one TCI associated with a candidate cell prior to reception of a beam indication associated with a candidate cell in a set of cells configured for LTM operation; components for receiving configuration information corresponding to LTM operation; and / or components for performing LTM handover operations based on the configuration information and at least one TCI. Components for the UE to perform the operations described herein may include, for example, one or more of the following: a communication manager 140, an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, or a memory 282.

[0100] In some aspects, a network node (e.g., network node 210) includes: components for receiving UE capability information indicating the UE's capability associated with activation of at least one TCI associated with a candidate cell prior to the transmission of a beam indication associated with a candidate cell in a set of cells configured for LTM operation; components for transmitting configuration information corresponding to the LTM operation; and / or components for performing an LTM handover operation based on the configuration information and at least one TCI. Components for the network node to perform the operations described herein may include, for example, one or more of the following: a communication manager 150, a transmit processor 214, a TX MIMO processor 230, a modem 232, an antenna 234, a MIMO detector 236, a receive processor 238, a controller / processor 240, a memory 242, or a scheduler 246.

[0101] Figure 4AExample 400 illustrates a first LTM technology according to this disclosure. The first LTM technology may be referred to as inter-cell mobility scheme 1, beam-based inter-cell mobility, dynamic point selection-based inter-cell mobility, and / or non-serving cell-based inter-cell mobility, etc. As further described in detail herein, the first LTM technology enables network nodes to use L1 signaling (e.g., DCI) or L2 signaling (e.g., MAC CE) to instruct UE 405 to communicate on the access link using beams from the serving cell or a non-serving cell. For example, in a radio network that does not support LTM (e.g., cell handover is triggered only by L3 handover), beam selection for control information and for data is typically limited to beams within the Physical Cell Identifier (PCI) associated with the serving cell. In contrast, in a radio network that supports the first LTM technology (e.g., as...), beam selection is more specific. Figure 4A As shown, the beam selection for control and data can be extended to include any beam within the serving cell 410 or one or more non-serving neighboring cells 415 for LTM configuration.

[0102] For example, in Figure 4A In the first LTM technology shown, UE 405 may be configured with a single serving cell 410, and UE 405 may be further configured with a set of neighboring cells including one or more non-serving neighboring cells 415 configured for LTM. Typically, the serving cell 410 and non-serving neighboring cells 415 configured for LTM may be associated with a common CU and a common DU, or the serving cell 410 and non-serving neighboring cells 415 configured for LTM may be associated with a common CU and different DUs. In some aspects, as indicated by reference numeral 420, the base station may use L1 / L2 signaling (e.g., DCI or MAC-CE) to trigger LTM for the UE, the L1 / L2 signaling indicating the selected TCI state for QCL with a reference signal (e.g., SSB) associated with the PCI. For example, in Figure 4A In this context, the UE can use PCI associated with the serving cell 410 (e.g., in...). Figure 4A The SSB (Signal SSB) of PCI 1) communicates with serving cell 410 using the QCL TCI state, and lower-layer (e.g., L1 / L2) signaling can instruct UE 405 to switch to using the PCI associated with non-serving neighbor cell 415 (e.g., in...). Figure 4A The SSB (shown as PCI2) communicates in the TCI state of QCL to trigger inter-cell mobility. Therefore, in the first LTM technique, the network node (e.g., the common CU controlling the serving cell 410 and the non-serving neighboring cell 415) can use L1 / L2 signaling to select a beam from the serving cell 410 or the non-serving neighboring cell 415 to serve UE 405.

[0103] In this manner, compared to limiting L1 / L2 beam selection to beams within serving cell 410, the first LTM technology is more robust against obstruction and provides more opportunities for higher-rank spatial multiplexing across different cells. However, the first LTM technology cannot support changing the primary cell (PCell) or secondary cell (PSCell) of UE 405. Instead, in the first LTM technology, triggering PCell or PSCell changes is performed using RRC signaling via legacy L3 handover. In this respect, the first LTM technology is associated with the following limitation: when UE 405 is within the coverage area of ​​serving cell 410, L1 / L2 signaling can only be used to indicate beams from serving cell 410 or configured neighboring cells 415, because L1 / L2 signaling cannot be used to change PCell or PSCell.

[0104] therefore, Figure 4B Example 450 illustrates a second LTM technique according to this disclosure. The second LTM technique may be referred to as inter-cell mobility scheme 2 and / or serving cell-based inter-cell mobility, etc. As described in further detail herein, the second LTM technique enables network nodes to use L1 / L2 signaling (e.g., DCI or MAC-CE) to indicate control information associated with an active set of cells and / or a deactivated set of cells and / or to indicate changes to PCells or PSCells within the active set of cells.

[0105] For example, such as Figure 4B As shown, the second LTM technology can use a mechanism similar to carrier aggregation to implement LTM, except that different cells configured for LTM can operate on the same carrier frequency. For example... Figure 4BAs shown, a network node can configure a cell set 460 for LTM (e.g., using RRC signaling), which includes at least cell 1 (“1”), cell 2 (“2”), cell 3 (“3”), and cell 4 (“4”). As further shown, an active cell set 465 can include one or more cells from the configured cell set 460 that are activated and ready for data and / or control transfer. For example, the active cell set 465 can include cell 1 and cell 2. Cell 1 can be a PCell, and cell 2 can be a PSCell. Therefore, in the second LTM technique, a deactivated cell set can include one or more cells (cell 3 and cell 4) that are included in the LTM-configured cell set 460 but not in the active cell set 465. However, using L1 / L2 signaling, cells included in the deactivated cell set can be easily activated and thus added to the active cell set 465. Therefore, as indicated by reference numeral 470, L1 / L2 signaling can be used for mobility management of the active cell set 465. For example, in some aspects, L1 / L2 signaling can be used to activate cells within the configured cell set 460 (e.g., add cells to the active cell set 465), deactivate cells in the active cell set 465, and / or select beams included in cells within the active cell set 465. In this way, the second LTM technology can use L1 / L2 signaling (e.g., using beam management technology) to achieve seamless mobility between cells included in the active cell set 465.

[0106] Furthermore, as indicated by reference numeral 475, the second LTM technology enables the use of L1 / L2 signaling to set or change the PCell or PSCell from cells included in the active cell set 465. Additionally or alternatively, when a cell to become a new PCell or PSCell is in a deactivated cell set (e.g., included in the LTM-configured cell set 460 but not in the active cell set 465), L1 / L2 signaling can be used to move the cell from the deactivated cell set to the active cell set 465 before further L1 / L2 signaling is used to set the cell as the new PCell or PSCell. However, in the second LTM technology, when a new PCell or PSCell is not included in the LTM-configured cell set 460, L3 handover (using RRC signaling) is used to change the PCell or PSCell. In such cases, the RRC signaling associated with the L3 handover can be used to update cells included in the LTM-configured cell set 460.

[0107] In some aspects, multiple TRP 480s and TRP 485s can transmit communications (e.g., the same or different communications) in the same Transmission Time Interval (TTI) (e.g., time slots, micro-slots, subframes, or symbols) or in different TTIs using different QCL relationships (e.g., different spatial parameters, different TCI states, different pre-decoding parameters, or different beamforming parameters). In some aspects, the TCI state can be used to indicate one or more QCL relationships. TRP 480s can be configured to serve traffic to UE 405 individually (e.g., using dynamic selection) or jointly (e.g., using joint transmission with one or more other TRP 485s). In some aspects, TRP 480s and / or TRP 485s can be a combination of the above. Figure 1 and Figure 2 The described one or more network nodes 110 may include, or may be included in, the one or more network nodes. In some examples, different TRP 480s and TRP 485s may be included in different base stations and / or other network nodes. In some cases, multiple TRP 480s and TRP 485s may be included in a single base station and / or other network node. In some cases, TRP 480s and / or TRP 485s may be referred to as network nodes, cells, panels, antenna arrays, and / or arrays.

[0108] Cells in the LTM-configured cell set 460 may belong to Timing Advance Groups (TAGs), which may include a primary TAG (pTAG) and / or a secondary TAG (sTAG). A “TAG” may refer to a group of cells having the same (or similar within a threshold) uplink TA value. For example, the first uplink carrier and the second uplink carrier may have different propagation delays between UE 405 and TRP 480 associated with the same cell 1, and between UE 405 and TRP 485. For example, TRP 480 and TRP 485 may not co-located, resulting in different propagation delays for uplink transmissions to reach the corresponding TRPs on different uplink carriers. Therefore, the first uplink carrier and the second uplink carrier may have different timing advance values ​​for uplink transmissions and may belong to different TAGs.

[0109] UE 405 can use a timing advance value for the uplink carrier to transmit uplink communication on that uplink carrier at a timing that synchronizes the TTI with TRP 480 or 485, thereby reducing inter-TTI interference.

[0110] In some cases, the TCI state activation (sometimes referred to as "TCI activation") of a candidate cell can be received before the beam indication of the candidate cell is received. In other cases, the TCI state activation of a candidate cell can be received together with the beam indication of the candidate cell. However, some wireless communication standards may not provide signaling for TCI state activation and beam indication.

[0111] Various aspects are involved in LTM operations as a whole. Some aspects are more specifically related to beam indication for candidate cell groups in LTM operations. In some examples, the UE may send UE capability information to the network node, indicating the UE's capabilities associated with activation of the TCI state prior to the reception of the beam indication. For example, in some aspects, the UE capability information may indicate that the UE supports TCI activation prior to the beam indication. In some other aspects, the UE capability information may indicate that the UE supports TCI activation along with the beam indication. In some aspects, the UE may be provided with TCI activation communication (e.g., MAC CE) prior to receiving the beam indication. In some other aspects, the UE may be provided with TCI activation and a beam indication associated with the beam of the candidate cell (e.g., in a cell handover command). The UE may activate the TCI, activate the beam, and perform LTM handover in association with the activated TCI and beam.

[0112] Figure 5 This is a diagram illustrating an example 500 associated with a layer 1 measurement operation based on layer 3 for LTM according to this disclosure. Figure 5 As shown, UE 502 and network node 504 can communicate with each other. In some aspects, UE 502 can be, can be similar to, can include, or can be included in the following: Figure 4A and Figure 4B The UE405 described, and / or Figures 1 to 3 The UE 120 is depicted. In some aspects, network node 504 may be, may be similar to, may include, or may be included in the following: Figure 4B The TRP 480 and / or TRP485 described Figure 1 and Figure 2 The network node 110 described, and / or Figure 3 The depicted decomposed base station architecture 300 includes one or more components. In some aspects, network node 504 may include one or more TRPs and may provide multiple cells. Network node 504 may be associated with a source cell (e.g., UE 502 with its currently active cell in a connected state). The source cell may also be a PCell and / or a special cell (SpCell). Network node 504 may be associated with an SCell.

[0113] As indicated by reference numeral 506 in the accompanying drawings, UE 502 can transmit and network node 504 can receive UE capability information. In some aspects, the UE capability information may indicate the capability of UE 502 associated with the activation of at least one TCI associated with a candidate cell prior to reception of a beam indication associated with a candidate cell in a set of cells configured for LTM operation. In some aspects, the capability of UE 502 may be associated with at least one of component carriers (CC), frequency bands, or combinations of frequency bands.

[0114] As shown by reference numeral 508 in the attached figure, network node 504 can send configuration information, and UE 502 can receive the configuration information. In some aspects, RRC communication can be used to send the configuration information. The configuration information may correspond to LTM operations associated with a set of cells configured for LTM operations. In some aspects, the configuration information may include additional configuration information, which includes mTRP configuration. In some aspects, the mTRP configuration may include a single DCI-based mTRP configuration or a multi-DCI-based mTRP configuration.

[0115] As shown by reference numeral 510 in the accompanying drawings, network node 504 may send TCI activation communication, and UE 502 may receive TCI activation communication. The TCI activation communication may indicate the activation of at least one TCI. In some aspects, the TCI activation communication may include a MAC CE. In some aspects, the TCI activation communication may include a DCI (e.g., TCI activates DCI). The TCI activation communication may include a cell ID associated with a candidate cell. In some aspects, the TCI activation communication may include at least one of a downlink BWP ID or an uplink BWP ID associated with a candidate cell. The TCI activation communication may indicate at least one TCI to be activated.

[0116] In some aspects, for example, the TCI activation MAC CE may include a cell ID and a downlink and / or uplink BWP ID for the corresponding candidate cell. For a candidate cell configured with an mTRP, UE 502 may be activated using at least one TCI code point with up to two joint TCIs, or for a single DCI-based (sDCI) mTRP, the UE may be activated using at least one TCI code point with up to two downlink (DL) TCIs and two uplink (UL) TCIs. The mapping order between TCIs and TRPs may be implicitly determined based on rules such as, for example, based on the TCI ID order and / or TRP ID order. For example, UE 502 may be activated using at least two TCI code points, each TCI code point being mapped to a joint TCI or a pair of DL TCIs and UL TCIs for a multi-DCI-based (mDCI) mTRP. In some aspects, the mapping order between TCI code points and TRP IDs and / or control resource set (CORESET) pool indices may be indicated by the TCI code points. In some respects, the mapping order can be implicitly determined based on rules.

[0117] For example, in some aspects, UE 502 may receive additional configuration information including mTRP configuration, and based on the mTRP configuration, TCI activation communication may activate a TCI code point having at least one TCI, wherein the at least one TCI includes at least one joint TCI. The at least one joint TCI may include one joint TCI or two joint TCIs. In some aspects, UE 502 may receive additional configuration information including single DCI mTRP configuration, and based on the single DCI mTRP configuration, TCI activation communication may activate at least one of a downlink TCI or an uplink TCI. The at least one of a downlink TCI or an uplink TCI may include less than or equal to two downlink TCIs and less than or equal to two uplink TCIs. In some aspects, the mapping between at least one TCI and at least one TRP associated with the single DCI mTRP configuration may be based on mapping rules.

[0118] In some aspects, UE 502 may receive additional configuration information including mTRP configuration, and based on the mTRP configuration, TCI activation communication may activate a first TCI code point and a second TCI code point. The first TCI code point may be mapped to a first joint TCI among at least one TCI, and the second TCI code point may be mapped to a second joint TCI among at least one TCI. In some aspects, the first TCI code point may be mapped to a first uplink TCI and a first downlink TCI among at least one TCI, and the second TCI code point may be mapped to a second uplink TCI and a second downlink TCI among at least one TCI. In some aspects, the mapping order associated with the mapping set related to the first TCI code point and the second TCI code point may be indicated by at least one of the first TCI code point, the second TCI code point, or a third TCI code point. The mapping set may include at least one of the following: a mapping between a first TCI code point and at least one of a first TRP ID or a first CORESET ID, or a mapping between a second TCI code point and at least one of a second TRP ID or a second CORESET ID. In some aspects, the mapping order associated with the mapping set related to the first TCI code point and the second TCI code point may be based on mapping rules.

[0119] In some aspects, TCI activation of DCI may include a cell ID and a DL and / or UL BWPID for the corresponding candidate cell. For example, UE 502 may receive a TCI ID in the DCI (e.g., indicated using reserved bits). In some aspects, UE 502 may receive an SSB indication in the DCI, and UE 502 may apply the first TCI ID together with the indicated SSB as a root QCL source. In some aspects, the TCI to be activated may be for a candidate cell that is a future target cell. For example, the future target cell may be a candidate cell indicated in the next cell handover command or in the next cell handover command in a subsequent time window. UE 502 may anticipate receiving a cell handover command for a candidate cell within a certain period after the TCI is activated or after the TCI activation command for the candidate cell. The start time of the time window may be associated with at least one of the activation time of at least one TCI or the time associated with the reception of TCI activation communication.

[0120] In some aspects, to activate the TCI for a candidate cell using beam indication, UE 502 may receive a cell handover command with a joint TCI or a pair of DL and / or UL TCIs, and UE 502 may activate the indicated TCI after beam indication and then apply the indicated beam. For a candidate cell configured with an mTRP, UE 502 may be activated using TCI code points with up to two joint TCIs, or for a single DCI-based mTRP, the UE may be activated using TCI code points with up to two DLTCIs and two UL TCIs. The mapping order between TCIs and TRPs may be implicitly determined based on rules. In some aspects, UE 502 may be activated using two TCI code points, each code point mapped to a joint TCI or a pair of DL TCIs and UL TCIs for an mDCI-based mTRP. In some aspects, the mapping order between TCI code points and TRP IDs and / or CORESET pool indices may be indicated by the TCI code points. In some respects, the mapping order can be implicitly determined based on rules.

[0121] As shown by reference numeral 512 in the accompanying drawings, for example, network node 504 may send a cell handover command, and UE 502 may receive the cell handover command. The cell handover command may activate at least one TCI. For example, the cell handover command may indicate at least one TCI. In some aspects, the at least one TCI includes a joint TCI. In some other aspects, the at least one TCI may include a downlink TCI and an uplink TCI. In some aspects, UE 502 may receive additional configuration information including mTRP configuration, and based on the mTRP configuration, the cell handover command may indicate the activation of a TCI code point having at least one TCI, where the at least one TCI includes at least one joint TCI. For example, the at least one joint TCI may include one joint TCI or two joint TCIs. In some aspects, UE 502 may receive additional configuration information including a single DCI mTRP configuration, and based on the single DCI mTRP configuration, the cell handover command may indicate at least one of a downlink TCI or an uplink TCI. At least one of the downlink TCI or uplink TCI may include two or more downlink TCIs and two or more uplink TCIs.

[0122] In some aspects, UE 502 may receive additional configuration information including mTRP configuration, and based on the mTRP configuration, the cell handover command may indicate a first TCI code point and a second TCI code point. In some aspects, the first TCI code point may be mapped to a first joint TCI among at least one TCI, and the second TCI code point may be mapped to a second joint TCI among at least one TCI. In some aspects, the first TCI code point may be mapped to a first uplink TCI and a first downlink TCI among at least one TCI, and the second TCI code point may be mapped to a second uplink TCI and a second downlink TCI among at least one TCI. In some aspects, the mapping order associated with the mapping set related to the first TCI code point and the second TCI code point may be indicated by at least one of the first TCI code point, the second TCI code point, or a third TCI code point. The mapping set may include at least one of the following: a mapping between a first TCI code point and at least one of a first TRP ID or a first CORESET ID, or a mapping between a second TCI code point and at least one of a second TRP ID or a second CORESET ID. In some aspects, the mapping order associated with the mapping set related to the first TCI code point and the second TCI code point may be based on mapping rules.

[0123] As shown by reference numeral 514, network node 504 can send beam indication communication, and UE 502 can receive beam indication communication. The beam indication communication can indicate the beam of a candidate cell to be used for LTM handover operations. As shown by reference numeral 516, UE 502 can activate at least one TCI, and as shown by reference numeral 518, UE 502 and network node 504 can perform LTM handover operations. In some aspects, for example, network node 504 refers to more than one network node. For example, in some aspects, network node 504 may include a first TRP associated with the serving cell and a second TRP associated with a candidate cell (e.g., the cell to which UE 502 is handing over). In some aspects, UE 502 can perform LTM handover operations with additional network nodes (not shown).

[0124] In LTM operations, for TCI activation prior to or accompanying a cell handover command for one or more target CCs, if the target CC belongs to multiple CC lists (where all CCs in one list are configured to share a common beam indication), each CC list may have TCI activation for at least one CC in that list. For example, based on the target CC belonging to multiple CC lists and the common beam indication applying to at least one CC list among the multiple CC lists, at least one TCI may include multiple TCIs corresponding to the multiple CC lists, each of the multiple TCIs corresponding to at least one CC in the corresponding CC list among the multiple CC lists. If the target CC is not in any CC list, individual TCI activation may be provided to the CC. For example, in some aspects, based on the omission of the target CC from the CC list, TCI activation communication may indicate activation of the TCI associated with the target CC, or the cell handover command may indicate the beam associated with the target CC.

[0125] Figure 6 This is a diagram illustrating an example procedure 600 performed by a UE according to this disclosure. Example procedure 600 is an example in which a UE (e.g., UE 502) performs operations associated with beam indication for a candidate cell group in LTM operations.

[0126] like Figure 6 As shown, in some aspects, process 600 may include transmitting UE capability information indicating the UE's capability associated with the activation of at least one TCI associated with a candidate cell prior to reception of a beam indication associated with a candidate cell in a set of cells configured for LTM operation (box 610). For example, the UE (e.g., using...) Figure 8 The depicted transmitting component 804 and / or communication manager 806 can transmit UE capability information indicating the UE's capability associated with the activation of at least one TCI associated with a candidate cell prior to the reception of a beam indication associated with a candidate cell in a set of cells configured for LTM operation, as described above.

[0127] like Figure 6 As further shown, in some aspects, process 600 may include receiving configuration information corresponding to LTM operation (block 620). For example, the UE (e.g., using...) Figure 8 The described receiving component 802 and / or communication manager 806 can receive configuration information corresponding to LTM operation, as described above.

[0128] like Figure 6 As further shown, in some aspects, process 600 may include performing LTM handover operations based on configuration information and at least one TCI (block 630). For example, the UE (e.g., using...) Figure 8 The described communication manager 806 can perform LTM handover operations based on configuration information and at least one TCI, as described above.

[0129] Process 600 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0130] In a first aspect, the UE's capability is associated with at least one of component carriers, frequency bands, or combinations of frequency bands. In a second aspect, alone or in combination with the first aspect, process 600 includes receiving TCI activation communication indicating activation of at least one TCI prior to receiving beam indication. In a third aspect, alone or in combination with the second aspect, the TCI activation communication includes a TCI activation MAC CE. In a fourth aspect, alone or in combination with one or more of the second to third aspects, the TCI activation communication includes a cell ID associated with a candidate cell.

[0131] In the fifth aspect, either alone or in combination with one or more of the second to fourth aspects, the TCI activation communication includes at least one of a downlink BWP ID or an uplink BWP ID associated with a candidate cell. In the sixth aspect, either alone or in combination with one or more of the second to fifth aspects, process 600 includes receiving additional configuration information including a multiple transmit receive point (mTRP) configuration, and based on the mTRP configuration, the TCI activation communication activates a TCI code point having at least one TCI, wherein the at least one TCI includes at least one joint TCI. In the seventh aspect, either alone or in combination with the sixth aspect, the at least one joint TCI includes one joint TCI or two joint TCIs.

[0132] In the eighth aspect, either alone or in combination with one or more of the second to seventh aspects, process 600 includes receiving additional configuration information including a single DCI multiple transmit receive point (mTRP) configuration, and based on the single DCI mTRP configuration, TCI activation communication activates at least one of the downlink TCI or uplink TCI. In the ninth aspect, either alone or in combination with the eighth aspect, at least one of the downlink TCI or uplink TCI includes less than or equal to two downlink TCIs and less than or equal to two uplink TCIs. In the tenth aspect, either alone or in combination with one or more of the eighth to ninth aspects, the mapping between at least one TCI and at least one TRP associated with the single DCI mTRP configuration is based on a mapping rule.

[0133] In the eleventh aspect, either alone or in combination with one or more of the second to tenth aspects, process 600 includes receiving additional configuration information including a multiple transmit receive point (mTRP) configuration, and based on the mTRP configuration, TCI activation communication activates a first TCI code point and a second TCI code point. In the twelfth aspect, either alone or in combination with the eleventh aspect, the first TCI code point is mapped to a first joint TCI among at least one TCI, and the second TCI code point is mapped to a second joint TCI among at least one TCI. In the thirteenth aspect, either alone or in combination with the eleventh aspect, the first TCI code point is mapped to a first uplink TCI and a first downlink TCI among at least one TCI, and the second TCI code point is mapped to a second uplink TCI and a second downlink TCI among at least one TCI. In the fourteenth aspect, either alone or in combination with one or more of aspects eleven to thirteen, the mapping order associated with the mapping set of the first TCI code point and the second TCI code point is indicated by at least one of the first TCI code point, the second TCI code point, or the third TCI code point, the mapping set including at least one of the following: a mapping between the first TCI code point and at least one of the first TRP ID or the first CORESET ID, or a mapping between the second TCI code point and at least one of the second TRP ID or the second CORESET ID. In the fifteenth aspect, either alone or in combination with one or more of aspects eleven to thirteen, the mapping order associated with the mapping set of the first TCI code point and the second TCI code point is based on a mapping rule, the mapping set including at least one of the following: a mapping between the first TCI code point and at least one of the first TRP ID or the first CORESET ID, or a mapping between the second TCI code point and at least one of the second TRP ID or the second CORESET ID.

[0134] In the sixteenth aspect, alone or in combination with the second aspect, the TCI activation communication includes TCI activation DCI. In the seventeenth aspect, alone or in combination with the sixteenth aspect, the DCI indicates at least one TCI. In the eighteenth aspect, alone or in combination with one or more of the sixteenth to seventeenth aspects, the DCI includes an SSB indication indicating an SSB, and the method further includes applying a first TCI associated with an SSB among the at least one TCI as a root QCL source. In the nineteenth aspect, alone or in combination with one or more of the second to eighteenth aspects, the activation of at least one TCI includes a future target cell based on candidate cells. In the twentieth aspect, alone or in combination with the nineteenth aspect, candidate cells include a future target cell based on at least one of a candidate cell being associated with a next cell handover command or a cell handover command to be received within a time window. In the twenty-first aspect, alone or in combination with the twentieth aspect, the start time of the time window is associated with at least one of the activation time associated with at least one TCI or the time associated with the reception of the TCI activation communication.

[0135] In a twenty-second aspect, either alone or in combination with the first aspect, process 600 includes: receiving a cell handover command for activating at least one TCI, the cell handover command indicating at least one TCI; receiving beam indication communication indicating a beam associated with a candidate cell; and activating at least one TCI based on the received beam indication communication, wherein performing LTM handover operations includes applying a beam based on the activation of at least one TCI. In a twenty-third aspect, either alone or in combination with the twenty-second aspect, at least one TCI includes a joint TCI. In a twenty-fourth aspect, either alone or in combination with the twenty-second aspect, at least one TCI includes a downlink TCI and an uplink TCI. In a twenty-fifth aspect, either alone or in combination with the twenty-second aspect, process 600 includes receiving additional configuration information including a multiple transmit receive point (mTRP) configuration, and based on the mTRP configuration, the cell handover command indicates activation of a TCI code point having at least one TCI, the at least one TCI including at least one joint TCI. In a twenty-sixth aspect, either alone or in combination with the twenty-fifth aspect, at least one joint TCI includes one joint TCI or two joint TCIs. In the twenty-seventh aspect, either alone or in combination with the twenty-second aspect, process 600 includes receiving additional configuration information including a single DCI multiple transmit receive point (mTRP) configuration, and based on the single DCI mTRP configuration, a cell handover command indicates at least one of a downlink TCI or an uplink TCI. In the twenty-eighth aspect, either alone or in combination with the twenty-seventh aspect, at least one of the downlink TCI or uplink TCI includes less than or equal to two downlink TCIs and less than or equal to two uplink TCIs.

[0136] In the twenty-ninth aspect, either alone or in combination with the twenty-second aspect, process 600 includes receiving additional configuration information including a multiple transmit receive point (mTRP) configuration, and based on the mTRP configuration, a cell handover command indicates a first TCI code point and a second TCI code point. In the thirtieth aspect, either alone or in combination with the twenty-ninth aspect, the first TCI code point is mapped to a first joint TCI among at least one TCI, and the second TCI code point is mapped to a second joint TCI among at least one TCI. In the thirty-first aspect, either alone or in combination with the twenty-ninth aspect, the first TCI code point is mapped to a first uplink TCI and a first downlink TCI among at least one TCI, and the second TCI code point is mapped to a second uplink TCI and a second downlink TCI among at least one TCI.

[0137] In aspect thirty-two, either alone or in combination with one or more of aspects twenty-nine to thirty-one, the mapping order associated with the mapping set of the first TCI code point and the second TCI code point may be indicated by at least one of the first TCI code point, the second TCI code point, or the third TCI code point, the mapping set including at least one of the following: a mapping between the first TCI code point and at least one of the first TRP ID or the first CORESET ID, or a mapping between the second TCI code point and at least one of the second TRP ID or the second CORESET ID. In aspect thirty-three, either alone or in combination with one or more of aspects twenty-nine to thirty-one, the mapping order associated with the mapping set of the first TCI code point and the second TCI code point may be based on mapping rules, the mapping set including at least one of the following: a mapping between the first TCI code point and at least one of the first TRP ID or the first CORESET ID, or a mapping between the second TCI code point and at least one of the second TRP ID or the second CORESET ID.

[0138] In the thirty-fourth aspect, individually or in combination with one or more of the first to thirty-third aspects, based on the fact that the target CC belongs to multiple CC lists and a common beam indication applies to at least one of the multiple CC lists, at least one TCI includes multiple TCIs corresponding to the multiple CC lists, each of the multiple TCIs corresponding to at least one CC in a corresponding CC list among the multiple CC lists. In the thirty-fifth aspect, individually or in combination with one or more of the first to thirty-fourth aspects, based on the fact that the target CC is omitted from the CC list, activation communication further indicates the activation of the TCI associated with the target CC, or a cell handover command further indicates the beam associated with the target CC.

[0139] although Figure 6 An example box of process 600 is shown, but in some respects, process 600 may include... Figure 6 The boxes depicted may be fewer, different, or arranged differently compared to additional boxes. Alternatively, two or more boxes in the process 600 may be executed in parallel.

[0140] Figure 7 This is a diagram illustrating an example process 700 performed by a network node, for example, according to this disclosure. Example process 700 is an example in which a network node (e.g., network node 504) performs operations associated with beam indication for a candidate cell group in LTM operations.

[0141] like Figure 7 As shown, in some aspects, process 700 may include receiving UE capability information indicating the UE's capabilities associated with the activation of at least one TCI associated with a candidate cell prior to the transmission of a beam indication associated with a candidate cell in a set of cells configured for LTM operation (box 710). For example, a network node (e.g., using...) Figure 9 The depicted receiving component 902 and / or communication manager 906 can receive UE capability information indicating the UE's capability associated with the activation of at least one TCI associated with a candidate cell prior to the transmission of a beam indication associated with a candidate cell in a set of cells configured for LTM operation, as described above.

[0142] like Figure 7 As further shown, in some aspects, process 700 may include sending configuration information corresponding to the LTM operation (box 720). For example, network nodes (e.g., using...) Figure 9 The transmitting component 904 and / or the communication manager 906 described herein can transmit configuration information corresponding to LTM operation, as described above.

[0143] like Figure 7 As further shown, in some aspects, process 700 may include performing LTM handover operations based on configuration information and at least one TCI (box 730). For example, network nodes (e.g., using...) Figure 9 The described communication manager 906 can perform LTM handover operations based on configuration information and at least one TCI, as described above.

[0144] Process 700 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other process descriptions elsewhere herein.

[0145] In a first aspect, the UE's capability is associated with at least one of component carriers, frequency bands, or combinations of frequency bands. In a second aspect, alone or in combination with the first aspect, process 700 includes transmitting TCI activation communication indicating activation of at least one TCI prior to the transmission of beam indication. In a third aspect, alone or in combination with the second aspect, the TCI activation communication includes a TCI activation MAC CE. In a fourth aspect, alone or in combination with one or more of the second to third aspects, the TCI activation communication includes a cell ID associated with a candidate cell.

[0146] In the fifth aspect, either alone or in combination with one or more of the second to fourth aspects, the TCI activation communication includes at least one of a downlink BWP ID or an uplink BWP ID associated with a candidate cell. In the sixth aspect, either alone or in combination with one or more of the second to fifth aspects, process 700 includes transmitting additional configuration information including a multiple transmit receive point (mTRP) configuration, and based on the mTRP configuration, the TCI activation communication activates a TCI code point having at least one TCI, where the at least one TCI includes at least one joint TCI. In the seventh aspect, either alone or in combination with the sixth aspect, the at least one joint TCI includes one joint TCI or two joint TCIs.

[0147] In the eighth aspect, either alone or in combination with one or more of the second to seventh aspects, process 700 includes sending additional configuration information including a single DCI multiple transmit receive point (mTRP) configuration, and based on the single DCI mTRP configuration, TCI activation communication activates at least one of the downlink TCI or uplink TCI. In the ninth aspect, either alone or in combination with the eighth aspect, at least one of the downlink TCI or uplink TCI includes less than or equal to two downlink TCIs and less than or equal to two uplink TCIs. In the tenth aspect, either alone or in combination with one or more of the eighth to ninth aspects, the mapping between at least one TCI and at least one TRP associated with the single DCI mTRP configuration is based on a mapping rule.

[0148] In the eleventh aspect, either alone or in combination with one or more of the second to tenth aspects, process 700 includes transmitting additional configuration information including a multiple transmit receive point (mTRP) configuration, and based on the mTRP configuration, TCI activation communication activates a first TCI code point and a second TCI code point. In the twelfth aspect, either alone or in combination with the eleventh aspect, the first TCI code point is mapped to a first joint TCI among at least one TCI, and the second TCI code point is mapped to a second joint TCI among at least one TCI. In the thirteenth aspect, either alone or in combination with the eleventh aspect, the first TCI code point is mapped to a first uplink TCI and a first downlink TCI among at least one TCI, and the second TCI code point is mapped to a second uplink TCI and a second downlink TCI among at least one TCI. In the fourteenth aspect, either alone or in combination with one or more of aspects eleven to thirteen, the mapping order associated with the mapping set of the first TCI code point and the second TCI code point may be indicated by at least one of the first TCI code point, the second TCI code point, or the third TCI code point, the mapping set including at least one of the following: a mapping between the first TCI code point and at least one of the first TRP ID or the first CORESET ID, or a mapping between the second TCI code point and at least one of the second TRP ID or the second CORESET ID. In the fifteenth aspect, either alone or in combination with one or more of aspects eleven to fourteen, the mapping order associated with the mapping set of the first TCI code point and the second TCI code point may be based on a mapping rule, the mapping set including at least one of the following: a mapping between the first TCI code point and at least one of the first TRP ID or the first CORESET ID, or a mapping between the second TCI code point and at least one of the second TRP ID or the second CORESET ID.

[0149] In the sixteenth aspect, alone or in combination with one or more of the second to fifteenth aspects, TCI activation communication includes TCI activation DCI. In the seventeenth aspect, alone or in combination with the sixteenth aspect, the DCI indicates at least one TCI. In the eighteenth aspect, alone or in combination with one or more of the sixteenth to seventeenth aspects, the DCI includes an SSB indication indicating an SSB, wherein a first TCI of at least one TCI is associated with an SSB as a root QCL source.

[0150] In the nineteenth aspect, either alone or in combination with one or more of the second to eighteenth aspects, the activation of at least one TCI is based on candidate cells including future target cells. In the twentieth aspect, either alone or in combination with the nineteenth aspect, candidate cells are included to include future target cells based on at least one of a candidate cell being associated with a next cell handover command or a cell handover command to be received within a time window. In the twenty-first aspect, either alone or in combination with the twentieth aspect, the start time of the time window is associated with at least one of the activation time associated with at least one TCI or the time associated with the reception of TCI activation communication.

[0151] In a twenty-second aspect, process 700 includes: transmitting a cell handover command for activating at least one TCI, the cell handover command indicating at least one TCI; and transmitting beam indication communication indicating a beam associated with a candidate cell, wherein the at least one TCI is activated based on the beam indication communication, wherein performing LTM handover operations includes applying a beam based on activating at least one TCI. In a twenty-third aspect, individually or in combination with the twenty-second aspect, the at least one TCI includes a joint TCI. In a twenty-fourth aspect, individually or in combination with the twenty-second aspect, the at least one TCI includes a downlink TCI and an uplink TCI.

[0152] In aspect twenty-fif, either alone or in combination with one or more of aspects twenty-two to twenty-four, process 700 includes transmitting additional configuration information including a multiple transmit receive point (mTRP) configuration, and based on the mTRP configuration, a cell handover command indicates activation of a TCI code point having at least one TCI, wherein the at least one TCI includes at least one joint TCI. In aspect twenty-six, either alone or in combination with aspect twenty-fif, at least one joint TCI includes one joint TCI or two joint TCIs. In aspect twenty-seven, either alone or in combination with one or more of aspects twenty-two to twenty-six, process 700 includes transmitting additional configuration information including a single DCI multiple transmit receive point (mTRP) configuration, and based on the single DCI mTRP configuration, a cell handover command indicates at least one of a downlink TCI or an uplink TCI. In aspect twenty-eight, either alone or in combination with aspect twenty-seven, at least one of a downlink TCI or an uplink TCI includes less than or equal to two downlink TCIs and less than or equal to two uplink TCIs.

[0153] In the twenty-ninth aspect, either alone or in combination with one or more of the twenty-second to twenty-eighth aspects, process 700 includes transmitting additional configuration information including a multiple transmit receive point (mTRP) configuration, and based on the mTRP configuration, a cell handover command indicates a first TCI code point and a second TCI code point. In the thirtieth aspect, either alone or in combination with the twenty-ninth aspect, the first TCI code point is mapped to a first joint TCI among at least one TCI, and the second TCI code point is mapped to a second joint TCI among at least one TCI. In the thirty-first aspect, either alone or in combination with the twenty-ninth aspect, the first TCI code point is mapped to a first uplink TCI and a first downlink TCI among at least one TCI, and the second TCI code point is mapped to a second uplink TCI and a second downlink TCI among at least one TCI.

[0154] In aspect thirty-two, either alone or in combination with one or more of aspects twenty-nine to thirty-one, the mapping order associated with the mapping set relating to the first TCI code point and the second TCI code point is indicated by at least one of the first TCI code point, the second TCI code point, or the third TCI code point, the mapping set including at least one of the following: a mapping between the first TCI code point and at least one of the first TRP ID or the first CORESET ID, or a mapping between the second TCI code point and at least one of the second TRP ID or the second CORESET ID. In aspect thirty-three, either alone or in combination with one or more of aspects twenty-nine to thirty-one, the mapping order associated with the mapping set relating to the first TCI code point and the second TCI code point may be based on mapping rules, the mapping set including at least one of the following: a mapping between the first TCI code point and at least one of the first TRP ID or the first CORESET ID, or a mapping between the second TCI code point and at least one of the second TRP ID or the second CORESET ID.

[0155] In the thirty-fourth aspect, individually or in combination with one or more of the first to thirty-third aspects, based on the fact that the target CC belongs to multiple CC lists and a common beam indication applies to at least one of the multiple CC lists, at least one TCI includes multiple TCIs corresponding to the multiple CC lists, each of the multiple TCIs corresponding to at least one CC in a corresponding CC list among the multiple CC lists. In the thirty-fifth aspect, individually or in combination with one or more of the first to thirty-fourth aspects, based on the fact that the target CC is omitted from the CC list, activation communication further indicates the activation of the TCI associated with the target CC, or a cell handover command further indicates the beam associated with the target CC.

[0156] although Figure 7 An example box of process 700 is shown, but in some respects, process 700 may include... Figure 7 The boxes depicted may be fewer, different, or arranged differently compared to additional boxes. Alternatively, two or more boxes in the process 700 may be executed in parallel.

[0157] Figure 8 This is a diagram illustrating an example device 800 for wireless communication according to the present disclosure. Device 800 may be a UE, or a UE may include device 800. In some aspects, device 800 includes a receiving component 802, a transmitting component 804, and / or a communication manager 806 that can communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, the communication manager 806 is combined with... Figure 1 The described communication manager 140. As shown, device 800 can communicate with another device 808 (such as a UE or a network node (such as a CU, DU, RU or base station)) using receiving component 802 and transmitting component 804.

[0158] In some respects, device 800 can be configured to perform the functions described herein. Figure 5 One or more operations described herein. Additionally or alternatively, the apparatus 800 may be configured to perform one or more processes described herein, such as Figure 6 The process is 600. In some respects, Figure 8 The illustrated device 800 and / or one or more components may include a combination Figure 2 One or more components of the UE described. Additionally or alternatively, Figure 8 One or more components shown can be combined Figure 2 Implementation within one or more of the described components. Additionally or alternatively, one or more of the components in a set of components may be implemented at least partially as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.

[0159] Receiver 802 may receive communications from device 808, such as reference signals, control information, data communications, or combinations thereof. Receiver 802 may provide the received communications to one or more other components of device 800. In some aspects, receiver 802 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) and may provide the processed signals to one or more other components of device 800. In some aspects, receiver 802 may include combinations of... Figure 2 The described UE includes one or more antennas, modems, demodulators, MIMO detectors, receiver processors, controllers / processors, memory, or combinations thereof.

[0160] Transmitting component 804 can transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 808. In some aspects, one or more other components of device 800 can generate communications and provide the generated communications to transmitting component 804 for transmission to device 808. In some aspects, transmitting component 804 can perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and can transmit the processed signals to device 808. In some aspects, transmitting component 804 may include combinations of... Figure 2 The described UE includes one or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memory, or combinations thereof. In some aspects, the transmit component 804 may be co-located with the receive component 802 in a transceiver.

[0161] The communication manager 806 may support the operation of the receiving component 802 and / or the transmitting component 804. For example, the communication manager 806 may receive information associated with configuring the reception of communications by the receiving component 802 and / or the transmission of communications by the transmitting component 804. Additionally or alternatively, the communication manager 806 may generate control information and / or provide control information to the receiving component 802 and / or the transmitting component 804 to control the reception and / or transmission of communications.

[0162] Transmitting component 804 can transmit UE capability information indicating the UE's capability associated with the activation of at least one TCI associated with a candidate cell prior to the reception of a beam indication associated with a candidate cell in the cell set configured for LTM operation. Receiving component 802 can receive configuration information corresponding to LTM operation. Communication manager 806 can perform LTM handover operation based on the configuration information and at least one TCI. Receiving component 802 can receive TCI activation communication indicating the activation of at least one TCI prior to the reception of the beam indication.

[0163] The receiving component 802 can receive additional configuration information including a multiple transmit receive point (mTRP) configuration, and based on the mTRP configuration, TCI activation communication activates a TCI code point having at least one TCI, wherein the at least one TCI includes at least one joint TCI. The receiving component 802 can also receive additional configuration information including a single DCI multiple transmit receive point (mTRP) configuration, and based on the single DCI mTRP configuration, TCI activation communication activates at least one of a downlink TCI or an uplink TCI.

[0164] The receiving component 802 can receive additional configuration information including a Multiple Transmit Receive Point (mTRP) configuration, and based on the mTRP configuration, TCI activation communication activates a first TCI code point and a second TCI code point. The receiving component 802 can receive a cell handover command for activating at least one TCI, the cell handover command indicating at least one TCI. The receiving component 802 can receive beam indication communication indicating a beam associated with a candidate cell.

[0165] The communication manager 806 can activate at least one TCI based on received beam indication communication, wherein performing LTM handover operations includes applying a beam based on the activation of at least one TCI. The receiving component 802 can receive additional configuration information including a multiple transmit receive point (mTRP) configuration, and based on the mTRP configuration, a cell handover command indicates the activation of a TCI code point having at least one TCI, wherein the at least one TCI includes at least one joint TCI.

[0166] The receiving component 802 can receive additional configuration information including a single DCI multiple transmit receive point (mTRP) configuration, and based on the single DCI mTRP configuration, the cell handover command indicates at least one of the downlink TCI or the uplink TCI. The receiving component 802 can also receive additional configuration information including a multiple transmit receive point (mTRP) configuration, and based on the mTRP configuration, the cell handover command indicates a first TCI code point and a second TCI code point.

[0167] Figure 8 The number and arrangement of components shown are provided as an example. In reality, they can exist in... Figure 8 The components shown are compared to additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 8 The two or more components shown can be implemented within a single component, or Figure 8 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 8 The collection of (one or more) components shown is executable and described as being composed of Figure 8 Another set of components shown performs one or more functions.

[0168] Figure 9 This is a diagram illustrating an example device 900 for wireless communication according to the present disclosure. Device 900 may be a network node, or a network node may include device 900. In some aspects, device 900 includes a receiving component 902, a transmitting component 904, and / or a communication manager 906 that can communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, the communication manager 906 is combined with... Figure 1The described communication manager 150. As shown, device 900 can communicate with another device 908 (such as a UE or a network node (such as a CU, DU, RU or base station)) using receiving component 902 and transmitting component 904.

[0169] In some respects, device 900 can be configured to perform the functions described herein. Figure 5 One or more operations described herein. Additionally or alternatively, device 900 may be configured to perform one or more processes described herein, such as Figure 7 The process is 700. In some respects, Figure 9 The illustrated device 900 and / or one or more components may include a combination Figure 2 One or more components of the described network node. Additionally or alternatively, Figure 9 One or more components shown can be combined Figure 2 Implementation within one or more of the described components. Additionally or alternatively, one or more of the components in a set of components may be implemented at least partially as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.

[0170] Receiver 902 may receive communications from device 908, such as reference signals, control information, data communications, or combinations thereof. Receiver 902 may provide the received communications to one or more other components of device 900. In some aspects, receiver 902 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.), and may provide the processed signals to one or more other components of device 900. In some aspects, receiver 902 may include combinations of... Figure 2 The described network node includes one or more antennas, modems, demodulators, MIMO detectors, receiver processors, controllers / processors, memory, or combinations thereof. In some aspects, receiver component 902 and / or transmitter component 904 may include or be included in a network interface. The network interface may be configured to acquire and / or output signals for device 900 via one or more communication links, such as backhaul links, midhaul links, and / or fronthaul links.

[0171] Transmitting component 904 can transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 908. In some aspects, one or more other components of device 900 can generate communications and provide the generated communications to transmitting component 904 for transmission to device 908. In some aspects, transmitting component 904 can perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and can transmit the processed signals to device 908. In some aspects, transmitting component 904 may include combinations of... Figure 2 The described network node includes one or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memory, or combinations thereof. In some aspects, the transmit component 904 may be co-located with the receive component 902 in a transceiver.

[0172] The communication manager 906 may support the operation of the receiving component 902 and / or the transmitting component 904. For example, the communication manager 906 may receive information associated with configuring the reception of communications by the receiving component 902 and / or the transmission of communications by the transmitting component 904. Additionally or alternatively, the communication manager 906 may generate control information and / or provide control information to the receiving component 902 and / or the transmitting component 904 to control the reception and / or transmission of communications.

[0173] The receiving component 902 can receive UE capability information indicating the UE's capabilities associated with the activation of at least one TCI associated with a candidate cell prior to the transmission of a beam indication associated with a candidate cell in the cell set configured for LTM operation. The transmitting component 904 can transmit configuration information corresponding to the LTM operation. The communication manager 906 can perform an LTM handover operation based on the configuration information and at least one TCI. The transmitting component 904 can transmit TCI activation communication indicating the activation of at least one TCI prior to the transmission of the beam indication.

[0174] Transmitting component 904 can transmit additional configuration information including a multiple transmit / receive point (mTRP) configuration, and based on the mTRP configuration, TCI activation communication activates a TCI code point having at least one TCI, wherein the at least one TCI includes at least one joint TCI. Transmitting component 904 can also transmit additional configuration information including a single DCI multiple transmit / receive point (mTRP) configuration, and based on the single DCI mTRP configuration, TCI activation communication activates at least one of a downlink TCI or an uplink TCI.

[0175] Transmitting component 904 can transmit additional configuration information including a Multiple Transmit / Receive Point (mTRP) configuration, and based on the mTRP configuration, TCI activation communication activates a first TCI code point and a second TCI code point. Transmitting component 904 can transmit a cell handover command for activating at least one TCI, the cell handover command indicating at least one TCI. Transmitting component 904 can transmit beam indication communication indicating a beam associated with a candidate cell, wherein at least one TCI is activated based on the beam indication communication, and performing LTM handover operations includes applying a beam based on activating at least one TCI.

[0176] Transmitting component 904 can transmit additional configuration information including a multiple transmit-receive point (mTRP) configuration, and based on the mTRP configuration, a cell handover command indicates the activation of a TCI code point having at least one TCI, wherein the at least one TCI includes at least one joint TCI. Transmitting component 904 can transmit additional configuration information including a single DCI multiple transmit-receive point (mTRP) configuration, and based on the single DCI mTRP configuration, a cell handover command indicates at least one of a downlink TCI or an uplink TCI. Transmitting component 904 can transmit additional configuration information including a multiple transmit-receive point (mTRP) configuration, and based on the mTRP configuration, a cell handover command indicates a first TCI code point and a second TCI code point.

[0177] Figure 9 The number and arrangement of components shown are provided as an example. In reality, they can exist in... Figure 9 The components shown are compared to additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 9 The two or more components shown can be implemented within a single component, or Figure 9 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 9 The collection of (one or more) components shown is executable and described as being composed of Figure 9 Another set of components shown performs one or more functions.

[0178] The following provides an overview of some aspects of this disclosure:

[0179] Aspect 1: A method for wireless communication performed by a user equipment (UE), the method comprising: transmitting UE capability information indicating the UE's capability associated with activation of at least one transmission configuration indicator (TCI) associated with a candidate cell prior to reception of a beam indication associated with a candidate cell in a set of cells configured for lower-layer triggered mobility (LTM) operation; receiving configuration information corresponding to the LTM operation; and performing an LTM handover operation based on the configuration information and the at least one TCI.

[0180] Aspect 2: According to the method of aspect 1, wherein the capability of the UE is associated with at least one of component carrier, frequency band, or combination of frequency bands.

[0181] Aspect 3: The method according to any one of claims 1 or 2, the method further comprising receiving TCI activation communication indicating activation of the at least one TCI prior to the reception of the beam indication.

[0182] Aspect 4: According to the method of aspect 3, wherein the TCI activation communication includes a TCI activation media access control (MAC) control element (MAC CE).

[0183] Aspect 5: The method according to any one of Aspects 3 or 4, wherein the TCI activation communication includes a cell identifier (ID) associated with the candidate cell.

[0184] Aspect 6: The method according to any one of Aspects 3 to 5, wherein the TCI activation communication includes at least one of a downlink bandwidth portion (BWP) ID or an uplink BWP ID associated with the candidate cell.

[0185] Aspect 7: The method according to any one of Aspects 3 to 6, the method further comprising receiving additional configuration information including a multiple transmit receive point (mTRP) configuration, and wherein, based on the mTRP configuration, the TCI activation communication activates a TCI code point having the at least one TCI, the at least one TCI including at least one joint TCI.

[0186] Aspect 8: According to the method of aspect 7, the at least one joint TCI comprises one joint TCI or two joint TCIs.

[0187] Aspect 9: The method according to any one of Aspects 3 to 6, the method further comprising receiving additional configuration information including a single downlink control information (DCI) multiple transmit receive point (mTRP) configuration, and wherein, based on the single DCI mTRP configuration, the TCI activation communication activates at least one of a downlink TCI or an uplink TCI.

[0188] Aspect 10: According to the method of aspect 9, the at least one of the downlink TCI or the uplink TCI includes less than or equal to two downlink TCIs and less than or equal to two uplink TCIs.

[0189] Aspect 11: The method according to any one of claims 9 or 10, wherein the mapping between the at least one TCI and the at least one transmit / receive point (TRP) associated with the single DCI mTRP configuration is based on a mapping rule.

[0190] Aspect 12: The method according to any one of Aspects 3 to 6, the method further comprising receiving additional configuration information including a multiple transmit receive point (mTRP) configuration, and wherein, based on the mTRP configuration, the TCI activation communication activates a first TCI code point and a second TCI code point.

[0191] Aspect 13: According to the method of aspect 12, wherein the first TCI code point is mapped to a first joint TCI of the at least one TCI, and the second TCI code point is mapped to a second joint TCI of the at least one TCI.

[0192] Aspect 14: The method according to any one of Aspects 12 to 13, wherein the first TCI code point is mapped to a first uplink TCI and a first downlink TCI of the at least one TCI, and wherein the second TCI code point is mapped to a second uplink TCI and a second downlink TCI of the at least one TCI.

[0193] Aspect 15: The method according to any one of Aspects 12 to 14, wherein the mapping order associated with the mapping set associated with the first TCI code point and the second TCI code point is indicated by at least one of the first TCI code point, the second TCI code point, or the third TCI code point, the mapping set including at least one of the following: a mapping between the first TCI code point and at least one of the first TRP identifier (ID) or the first control resource set (CORESET) ID, or a mapping between the second TCI code point and at least one of the second TRP ID or the second CORESET ID.

[0194] Aspect 16: The method according to any one of Aspects 12 to 14, wherein the mapping order associated with the mapping set associated with the first TCI code point and the second TCI code point is based on a mapping rule, the mapping set including at least one of the following: a mapping between the first TCI code point and at least one of a first TRP identifier (ID) or a first control resource set (CORESET) ID, or a mapping between the second TCI code point and at least one of a second TRP ID or a second CORESET ID.

[0195] Aspect 17: The method according to aspect 3, wherein the TCI activation communication includes TCI activation downlink control information (DCI).

[0196] Aspect 18: The method according to aspect 17, wherein the DCI indicates the at least one TCI.

[0197] Aspect 19: The method according to any one of Aspects 17 or 18, wherein the DCI includes an SSB indication indicating a Synchronization Signal Block (SSB), and the method further includes applying a first TCI associated with the SSB among the at least one TCI as a root quasi-common address (QCL) source.

[0198] Aspect 20: The method according to any one of Aspects 3 to 19, wherein the activation of the at least one TCI is based on the candidate cell including a future target cell.

[0199] Aspect 21: According to the method of aspect 20, the candidate cells are included as future target cells based on the association of the candidate cells with at least one of a next cell handover command or a cell handover command to be received within a time window.

[0200] Aspect 22: According to the method of aspect 21, the start time of the time window is associated with at least one of the activation time of the at least one TCI or the time of receiving the TCI activation communication.

[0201] Aspect 23: The method according to any one of Aspects 3 to 22, wherein the target component carrier (CC) belongs to a plurality of CC lists and a common beam indication applies to at least one CC list among the plurality of CC lists, the at least one TCI comprising a plurality of TCIs corresponding to the plurality of CC lists, each of the plurality of TCIs corresponding to at least one CC in a corresponding CC list among the plurality of CC lists.

[0202] Aspect 24: The method according to any one of Aspects 3 to 23, wherein based on the omission of the target component carrier (CC) from the CC list, the activation of communication further indicates the activation of the TCI associated with the target CC.

[0203] Aspect 25: The method according to any one of Aspect 1 or 2, the method further comprising: receiving a cell handover command for activating the at least one TCI, the cell handover command indicating the at least one TCI; receiving a beam indication communication indicating a beam associated with the candidate cell; and activating the at least one TCI based on receiving the beam indication communication, wherein performing the LTM handover operation includes applying the beam based on activating the at least one TCI.

[0204] Aspect 26: According to the method of aspect 25, the at least one TCI includes a combined TCI.

[0205] Aspect 27: According to the method of aspect 25, the at least one TCI includes a downlink TCI and an uplink TCI.

[0206] Aspect 28: According to the method of aspect 25, the method further includes receiving additional configuration information including a multiple transmit receive point (mTRP) configuration, and wherein, based on the mTRP configuration, the cell handover command indicates the activation of a TCI code point having the at least one TCI, the at least one TCI including at least one joint TCI.

[0207] Aspect 29: According to the method of aspect 28, the at least one joint TCI comprises one joint TCI or two joint TCIs.

[0208] Aspect 30: According to the method of aspect 25, the method further includes receiving additional configuration information including a single downlink control information (DCI) multiple transmit receive point (mTRP) configuration, and wherein, based on the single DCI mTRP configuration, the cell handover command indicates at least one of a downlink TCI or an uplink TCI.

[0209] Aspect 31: According to the method of aspect 30, the at least one of the downlink TCI or the uplink TCI includes less than or equal to two downlink TCIs and less than or equal to two uplink TCIs.

[0210] Aspect 32: According to the method of aspect 25, the method further includes receiving additional configuration information including a multiple transmit receive point (mTRP) configuration, and wherein the cell handover command indicates a first TCI code point and a second TCI code point based on the mTRP configuration.

[0211] Aspect 33: According to the method of aspect 32, wherein the first TCI code point is mapped to a first joint TCI of the at least one TCI, and the second TCI code point is mapped to a second joint TCI of the at least one TCI.

[0212] Aspect 34: According to the method of aspect 32, wherein the first TCI code point is mapped to a first uplink TCI and a first downlink TCI of the at least one TCI, and wherein the second TCI code point is mapped to a second uplink TCI and a second downlink TCI of the at least one TCI.

[0213] Aspect 35: The method according to any one of Aspects 32 to 34, wherein the mapping order associated with the mapping set associated with the first TCI code point and the second TCI code point is indicated by at least one of the first TCI code point, the second TCI code point, or the third TCI code point, the mapping set including at least one of the following: a mapping between the first TCI code point and at least one of the first TRP identifier (ID) or the first control resource set (CORESET) ID, or a mapping between the second TCI code point and at least one of the second TRP ID or the second CORESET ID.

[0214] Aspect 36: The method according to any one of Aspects 32 to 34, wherein the mapping order associated with the mapping set associated with the first TCI code point and the second TCI code point is based on a mapping rule, the mapping set including at least one of the following: a mapping between the first TCI code point and at least one of a first TRP identifier (ID) or a first control resource set (CORESET) ID, or a mapping between the second TCI code point and at least one of a second TRP ID or a second CORESET ID.

[0215] Aspect 37: The method according to any one of Aspects 25 to 36, wherein the target component carrier (CC) belongs to a plurality of CC lists and a common beam indication applies to at least one CC list among the plurality of CC lists, the at least one TCI comprising a plurality of TCIs corresponding to the plurality of CC lists, each of the plurality of TCIs corresponding to at least one CC in a corresponding CC list among the plurality of CC lists.

[0216] Aspect 38: The method according to any one of Aspects 25 to 37, wherein the target component carrier (CC) is omitted from the CC list, and the cell handover command further indicates the beam associated with the target CC.

[0217] Aspect 39: A method for wireless communication performed by a network node, the method comprising: receiving user equipment (UE) capability information, the UE capability information indicating the UE's capability associated with the activation of at least one transmission configuration indicator (TCI) associated with the candidate cell prior to the transmission of a beam indication associated with a candidate cell in a set of cells configured for lower-layer triggered mobility (LTM) operation; transmitting configuration information corresponding to the LTM operation; and performing an LTM handover operation based on the configuration information and the at least one TCI.

[0218] Aspect 40: The method according to aspect 39, wherein the capability of the UE is associated with at least one of component carrier, frequency band, or combination of frequency bands.

[0219] Aspect 41: The method according to any one of claims 39 or 40, the method further comprising transmitting a TCI activation communication indicating activation of the at least one TCI prior to the transmission of the beam indication.

[0220] Aspect 42: The method according to aspect 41, wherein the TCI activation communication includes a TCI activation media access control (MAC) control element (MAC CE).

[0221] Aspect 43: The method according to any one of Aspects 41 or 42, wherein the TCI activation communication includes a cell identifier (ID) associated with the candidate cell.

[0222] Aspect 44: The method according to any one of Aspects 41 to 43, wherein the TCI activation communication includes at least one of a downlink bandwidth portion (BWP) ID or an uplink BWP ID associated with the candidate cell.

[0223] Aspect 45: The method according to any one of aspects 41 to 44, the method further comprising transmitting additional configuration information including a multiple transmit receive point (mTRP) configuration, and wherein, based on the mTRP configuration, the TCI activation communication activates a TCI code point having the at least one TCI, the at least one TCI including at least one joint TCI.

[0224] Aspect 46: According to the method of aspect 45, the at least one joint TCI comprises one joint TCI or two joint TCIs.

[0225] Aspect 47: The method according to any one of aspects 41 to 44, the method further comprising transmitting additional configuration information including a single downlink control information (DCI) multiple transmit receive point (mTRP) configuration, and wherein, based on the single DCI mTRP configuration, the TCI activation communication activates at least one of a downlink TCI or an uplink TCI.

[0226] Aspect 48: According to the method of aspect 47, the at least one of the downlink TCI or the uplink TCI includes less than or equal to two downlink TCIs and less than or equal to two uplink TCIs.

[0227] Aspect 49: The method according to any one of Aspects 47 or 48, wherein the mapping between the at least one TCI and the at least one transmit / receive point (TRP) associated with the single DCI mTRP configuration is based on a mapping rule.

[0228] Aspect 50: The method according to any one of aspects 41 to 44, the method further comprising transmitting additional configuration information including a multiple transmit receive point (mTRP) configuration, and wherein, based on the mTRP configuration, the TCI activation communication activates a first TCI code point and a second TCI code point.

[0229] Aspect 51: According to the method of aspect 50, wherein the first TCI code point is mapped to a first joint TCI of the at least one TCI, and the second TCI code point is mapped to a second joint TCI of the at least one TCI.

[0230] Aspect 52: According to the method of aspect 50, wherein the first TCI code point is mapped to a first uplink TCI and a first downlink TCI of the at least one TCI, and wherein the second TCI code point is mapped to a second uplink TCI and a second downlink TCI of the at least one TCI.

[0231] Aspect 53: The method according to any one of Aspects 50 to 52, wherein the mapping order associated with the mapping set associated with the first TCI code point and the second TCI code point is indicated by at least one of the first TCI code point, the second TCI code point, or the third TCI code point, the mapping set including at least one of the following: a mapping between the first TCI code point and at least one of the first TRP identifier (ID) or the first control resource set (CORESET) ID, or a mapping between the second TCI code point and at least one of the second TRP ID or the second CORESET ID.

[0232] Aspect 54: The method according to any one of Aspects 50 to 52, wherein the mapping order associated with the mapping set associated with the first TCI code point and the second TCI code point is based on a mapping rule, the mapping set including at least one of the following: a mapping between the first TCI code point and at least one of a first TRP identifier (ID) or a first control resource set (CORESET) ID, or a mapping between the second TCI code point and at least one of a second TRP ID or a second CORESET ID.

[0233] Aspect 55: The method according to any one of Aspects 41 to 44, wherein the TCI activation communication includes TCI activation downlink control information (DCI).

[0234] Aspect 56: The method according to aspect 55, wherein the DCI indicates the at least one TCI.

[0235] Aspect 57: The method according to any one of Aspects 55 or 56, wherein the DCI includes an SSB indication indicating a Synchronization Signal Block (SSB), wherein a first TCI of the at least one TCI is associated with the SSB as a root quasi-co-address (QCL) source.

[0236] Aspect 58: The method according to any one of Aspects 41 to 57, wherein the activation of the at least one TCI is based on the candidate cell including a future target cell.

[0237] Aspect 59: According to the method of aspect 58, the candidate cells are included as future target cells based on the association of the candidate cells with at least one of a next cell handover command or a cell handover command to be received within a time window.

[0238] Aspect 60: According to the method of aspect 59, the start time of the time window is associated with at least one of the activation time of the at least one TCI or the time of receiving the TCI activation communication.

[0239] Aspect 61: The method according to any one of Aspects 41 to 60, wherein the target component carrier (CC) belongs to a plurality of CC lists and a common beam indication applies to at least one CC list among the plurality of CC lists, the at least one TCI comprising a plurality of TCIs corresponding to the plurality of CC lists, each of the plurality of TCIs corresponding to at least one CC in a corresponding CC list among the plurality of CC lists.

[0240] Aspect 62: The method according to any one of aspects 41 to 61, wherein based on the omission of the target component carrier (CC) from the CC list, the activation of communication further indicates the activation of the TCI associated with the target CC.

[0241] Aspect 63: The method according to aspect 39, the method further comprising: sending a cell handover command for activating the at least one TCI, the cell handover command indicating the at least one TCI; and sending beam indication communication indicating a beam associated with the candidate cell, wherein the at least one TCI is activated based on the beam indication communication, wherein performing the LTM handover operation includes applying the beam based on activating the at least one TCI.

[0242] Aspect 64: According to the method of aspect 63, the at least one TCI includes a combined TCI.

[0243] Aspect 65: According to the method of aspect 63, the at least one TCI includes a downlink TCI and an uplink TCI.

[0244] Aspect 66: The method according to any one of aspects 63 to 65, the method further comprising transmitting additional configuration information including a multiple transmit receive point (mTRP) configuration, and wherein, based on the mTRP configuration, the cell handover command indicates activation of a TCI code point having the at least one TCI, the at least one TCI including at least one joint TCI.

[0245] Aspect 67: According to the method of aspect 66, the at least one joint TCI comprises one joint TCI or two joint TCIs.

[0246] Aspect 68: The method according to any one of aspects 63 to 65, the method further comprising transmitting additional configuration information including a single downlink control information (DCI) multiple transmit receive point (mTRP) configuration, and wherein, based on the single DCI mTRP configuration, the cell handover command indicates at least one of a downlink TCI or an uplink TCI.

[0247] Aspect 69: According to the method of aspect 68, the at least one of the downlink TCI or the uplink TCI includes less than or equal to two downlink TCIs and less than or equal to two uplink TCIs.

[0248] Aspect 70: The method according to any one of aspects 63 to 65, the method further comprising transmitting additional configuration information including a multiple transmit receive point (mTRP) configuration, and wherein the cell handover command indicates a first TCI code point and a second TCI code point based on the mTRP configuration.

[0249] Aspect 71: According to the method of aspect 70, wherein the first TCI code point is mapped to a first joint TCI of the at least one TCI, and the second TCI code point is mapped to a second joint TCI of the at least one TCI.

[0250] Aspect 72: The method according to any one of aspects 70 to 71, wherein the first TCI code point is mapped to a first uplink TCI and a first downlink TCI of the at least one TCI, and wherein the second TCI code point is mapped to a second uplink TCI and a second downlink TCI of the at least one TCI.

[0251] Aspect 73: The method according to any one of Aspects 70 to 72, wherein the mapping order associated with the mapping set associated with the first TCI code point and the second TCI code point is indicated by at least one of the first TCI code point, the second TCI code point, or the third TCI code point, the mapping set including at least one of the following: a mapping between the first TCI code point and at least one of the first TRP identifier (ID) or the first control resource set (CORESET) ID, or a mapping between the second TCI code point and at least one of the second TRP ID or the second CORESET ID.

[0252] Aspect 74: The method according to any one of Aspects 70 to 72, wherein the mapping order associated with the mapping set associated with the first TCI code point and the second TCI code point is based on a mapping rule, the mapping set including at least one of the following: a mapping between the first TCI code point and at least one of a first TRP identifier (ID) or a first control resource set (CORESET) ID, or a mapping between the second TCI code point and at least one of a second TRP ID or a second CORESET ID.

[0253] Aspect 75: The method according to any one of Aspects 63 to 74, wherein the target component carrier (CC) belongs to a plurality of CC lists and a common beam indication applies to at least one CC list among the plurality of CC lists, the at least one TCI comprising a plurality of TCIs corresponding to the plurality of CC lists, each of the plurality of TCIs corresponding to at least one CC in a corresponding CC list among the plurality of CC lists.

[0254] Aspect 76: The method according to any one of Aspects 63 to 75, wherein the target component carrier (CC) is omitted from the CC list, and the cell handover command further indicates the beam associated with the target CC.

[0255] Aspect 77: An apparatus for wireless communication at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method according to one or more of aspects 1 to 38.

[0256] Aspect 78: An apparatus for wireless communication, the apparatus comprising a memory and one or more processors coupled to the memory, the one or more processors being configured to perform the method according to one or more of aspects 1 to 38.

[0257] Aspect 79: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 1 to 38.

[0258] Aspect 80: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by a processor to perform the methods described in one or more of aspects 1 to 38.

[0259] Aspect 81: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method according to one or more of aspects 1 to 38.

[0260] Aspect 82: An apparatus for wireless communication at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods according to aspects 39 to 76.

[0261] Aspect 83: An apparatus for wireless communication, the apparatus comprising a memory and one or more processors coupled to the memory, the one or more processors being configured to perform the method according to one or more of aspects 39 to 76.

[0262] Aspect 84: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 39 to 76.

[0263] Aspect 85: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by a processor to perform the methods described in one or more of aspects 39 to 76.

[0264] Aspect 86: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method according to one or more of aspects 39 to 76.

[0265] While the foregoing disclosure provides examples and descriptions, it is not intended to be exhaustive or to limit aspects to the precise form disclosed. Modifications and variations can be made based on the foregoing disclosure, or from various aspects of practice.

[0266] As used herein, the term "component" is intended to be broadly interpreted as hardware or a combination of hardware and at least one of software or firmware. "Software" should be broadly interpreted as instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable programs, threads of execution, procedures, or functions, whether referred to as software, firmware, middleware, microcode, hardware description languages, or other terms. As used herein, a "processor" is implemented in hardware or a combination of hardware and software. It will be apparent that the systems or methods described herein may be implemented in various forms of hardware or combinations of hardware and software. The actual dedicated control hardware or software code used to implement these systems or methods is not limited in any way. Therefore, the operation and behavior of these systems or methods are described herein without reference to specific software code, as those skilled in the art will understand that the software and hardware can be designed to implement these systems or methods, at least in part, based on the description herein. Unless otherwise stated, a component configured to perform a function means that the component has the capability to perform that function, but it is not necessary for the component to actually perform that function.

[0267] As used in this article, depending on the context, "meeting the threshold" can mean a value greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, etc.

[0268] As used in this article, the phrase “at least one of the items” refers to any combination of these items, including a single member. As an example, “at least one of a, b, or c” is intended to cover: a, b, c, ab, ac, bc, and abc, as well as any combination with multiple identical elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbb, cc, and ccc, or any other ordering of a, b, and c).

[0269] No element, action, or instruction used herein should be construed as essential or necessary unless explicitly stated otherwise. Furthermore, as used herein, the articles “a” and “an” are intended to include one or more items and are interchangeable with “one or more.” Similarly, as used herein, the article “described” is intended to include one or more items mentioned in connection with the article “described” and is interchangeable with “one or more.” Furthermore, as used herein, the terms “set” and “group” are intended to include one or more items and are interchangeable with “one or more.” If only one item is desired, the phrase “only one” or similar terminology will be used. Moreover, as used herein, the terms “having” and similar terms are intended as open-ended terms that do not limit the elements they modify (e.g., “having” A may also have B). Additionally, the phrase “based on” is intended to mean “based on or otherwise related to” unless otherwise explicitly stated. Furthermore, as used herein, the term “or” is intended to be inclusive when used consecutively and is interchangeable with “and / or” unless otherwise explicitly stated (e.g., if used in conjunction with “either of the two” or “only one of them”). It should be understood that “one or more” is equivalent to “at least one”.

[0270] Although specific combinations of features are set forth in the claims or disclosed in the description, these combinations are not intended to limit the disclosure of various aspects. Many of these features may be combined in ways not specifically stated in the claims or disclosed in the description. The disclosure of various aspects includes each dependent claim in combination with each other claim in the claim set.

Claims

1. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: One or more memory units; as well as One or more processors, said one or more processors being coupled to said one or more memories and configured to cause the UE to: Transmit UE capability information, which indicates the UE's capability associated with the activation of at least one Transmit Configuration Indicator (TCI) associated with a candidate cell prior to the reception of a beam indication associated with a candidate cell in a set of cells configured for lower-layer triggered mobility (LTM) operation. Receive configuration information corresponding to the LTM operation; as well as The LTM handover operation is performed based on the configuration information and the at least one TCI.

2. The UE of claim 1, wherein the capability of the UE is associated with at least one of component carrier, frequency band, or combination of frequency bands.

3. The UE of claim 1, wherein the one or more processors are further configured to cause the UE to receive TCI activation communication indicating activation of the at least one TCI prior to the reception of the beam indication, wherein the TCI activation communication includes a TCI Activation Medium Access Control (MAC) Control Element (MAC CE).

4. The UE of claim 3, wherein the TCI activation communication includes at least one of a cell identifier (ID) associated with the candidate cell, a downlink bandwidth portion (BWP) ID associated with the candidate cell, or an uplink BWP ID.

5. The UE of claim 3, wherein the one or more processors are further configured to cause the UE to receive additional configuration information including a multiple transmit receive point (mTRP) configuration, and wherein, based on the mTRP configuration, the TCI activation communication activates a TCI code point having the at least one TCI, the at least one TCI including at least one joint TCI.

6. The UE of claim 3, wherein the one or more processors are further configured to cause the UE to receive additional configuration information including a single downlink control information (DCI) multiple transmit receive point (mTRP) configuration, and wherein, based on the single DCI mTRP configuration, the TCI activation communication activates at least one of the downlink TCI or the uplink TCI.

7. The UE of claim 6, wherein the mapping between the at least one TCI and the at least one transmit / receive point (TRP) associated with the single DCI mTRP configuration is based on a mapping rule.

8. The UE of claim 3, wherein the one or more processors are further configured to cause the UE to receive additional configuration information including a multiple transmit receive point (mTRP) configuration, and wherein, based on the mTRP configuration, the TCI activation communication activates a first TCI code point and a second TCI code point.

9. The UE according to claim 3, wherein the TCI activation communication includes TCI activation downlink control information (DCI).

10. The UE of claim 9, wherein the DCI indicates the at least one TCI.

11. The UE of claim 9, wherein the DCI includes an SSB indication indicating a Synchronization Signal Block (SSB), and wherein the one or more processors are further configured to cause the UE to apply a first TCI associated with the SSB in the at least one TCI as a root quasi-co-address (QCL) source.

12. The UE of claim 3, wherein the activation of the at least one TCI is based on the candidate cell including a future target cell.

13. The UE of claim 12, wherein the candidate cells include future target cells based on at least one of the candidate cells being associated with a next cell handover command or a cell handover command to be received within a time window, wherein the start time of the time window is associated with at least one of the activation time associated with the at least one TCI or the time associated with the reception of the TCI activation communication.

14. The UE of claim 3, wherein the target component carrier (CC) belongs to a plurality of CC lists and a common beam indication applies to at least one CC list among the plurality of CC lists, the at least one TCI comprising a plurality of TCIs corresponding to the plurality of CC lists, each of the plurality of TCIs corresponding to at least one CC in a corresponding CC list among the plurality of CC lists.

15. The UE of claim 3, wherein the TCI activation communication further indicates the activation of the TCI associated with the target CC, based on the fact that the target component carrier (CC) is omitted from the CC list.

16. The UE of claim 1, wherein the one or more processors are further configured to cause the UE to: Receive a cell handover command for activating the at least one TCI, the cell handover command indicating the at least one TCI; Receive beam indication communication indicating the beam associated with the candidate cell; and Activating the at least one TCI based on receiving the beam indication communication, wherein performing the LTM handover operation includes applying the beam based on activating the at least one TCI.

17. The UE of claim 16, wherein the one or more processors are further configured to cause the UE to receive additional configuration information including a multiple transmit receive point (mTRP) configuration, and wherein, based on the mTRP configuration, the cell handover command indicates activation of a TCI code point having the at least one TCI, the at least one TCI including at least one joint TCI.

18. The UE of claim 16, wherein the one or more processors are further configured to cause the UE to receive additional configuration information including a single downlink control information (DCI) multiple transmit receive point (mTRP) configuration, and wherein, based on the single DCI mTRP configuration, the cell handover command indicates at least one of a downlink TCI or an uplink TCI.

19. The UE of claim 16, wherein the one or more processors are further configured to cause the UE to receive additional configuration information including a multiple transmit receive point (mTRP) configuration, and wherein the cell handover command indicates a first TCI code point and a second TCI code point based on the mTRP configuration.

20. The UE of claim 19, wherein the first TCI code point is mapped to a first joint TCI of the at least one TCI, and the second TCI code point is mapped to a second joint TCI of the at least one TCI.

21. The UE of claim 19, wherein the first TCI code point is mapped to a first uplink TCI and a first downlink TCI of the at least one TCI, and wherein the second TCI code point is mapped to a second uplink TCI and a second downlink TCI of the at least one TCI.

22. The UE of claim 16, wherein the target component carrier (CC) belongs to a plurality of CC lists and a common beam indication applies to at least one of the plurality of CC lists, the at least one TCI comprising a plurality of TCIs corresponding to the plurality of CC lists, each of the plurality of TCIs corresponding to at least one CC in a corresponding CC list of the plurality of CC lists.

23. The UE of claim 16, wherein the target component carrier (CC) is omitted from the CC list, and the cell handover command further indicates the beam associated with the target CC.

24. A network node for wireless communication, the network node comprising: One or more memory units; as well as One or more processors, said one or more processors coupled to said one or more memories and configured to cause the network node to: Receive User Equipment (UE) capability information, which indicates the UE's capability associated with the activation of at least one Transmission Configuration Indicator (TCI) associated with a candidate cell prior to the transmission of a beam indication associated with a candidate cell in a set of cells configured for lower-level triggered mobility (LTM) operation. Send configuration information corresponding to the LTM operation; as well as The LTM handover operation is performed based on the configuration information and the at least one TCI.

25. The network node of claim 24, wherein the one or more processors are further configured to cause the network node to transmit TCI activation communication indicating activation of the at least one TCI prior to the transmission of the beam indication.

26. The network node of claim 24, wherein the one or more processors are further configured to cause the network node to: Send a cell handover command to activate the at least one TCI, the cell handover command indicating the at least one TCI; and Transmit beam indication communication indicating a beam associated with the candidate cell, wherein at least one TCI is activated based on the beam indication communication, wherein performing the LTM handover operation includes applying the beam based on activating the at least one TCI.

27. A method for wireless communication performed by a user equipment (UE), the method comprising: Transmit UE capability information, which indicates the UE's capability associated with the activation of at least one Transmit Configuration Indicator (TCI) associated with a candidate cell prior to the reception of a beam indication associated with a candidate cell in a set of cells configured for lower-layer triggered mobility (LTM) operation. Receive configuration information corresponding to the LTM operation; as well as The LTM handover operation is performed based on the configuration information and the at least one TCI.

28. The method of claim 27, wherein the capability of the UE is associated with at least one of component carrier, frequency band, or combination of frequency bands.

29. A method for wireless communication performed by a network node, the method comprising: Receive User Equipment (UE) capability information, which indicates the UE's capability associated with the activation of at least one Transmission Configuration Indicator (TCI) associated with a candidate cell prior to the transmission of a beam indication associated with a candidate cell in a set of cells configured for lower-level triggered mobility (LTM) operation. Send configuration information corresponding to the LTM operation; as well as The LTM handover operation is performed based on the configuration information and the at least one TCI.

30. The method of claim 29, wherein the capability of the UE is associated with at least one of component carrier, frequency band, or combination of frequency bands.

Images