User equipment capability for mobility of layer 1 / layer 2 triggers and unified transmission configuration indication

Abstract

Various aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may send a capability indication associated with Layer 1 / Layer 2 triggered Mobility (LTM) capabilities according to a Medium Access Control (MAC) Control Element (MAC-CE) cell handover operation. The UE may receive the configuration according to the capability indication. Numerous other aspects are described.

Description

Technical Field

[0001] All aspects of this disclosure relate to wireless communication in general, and to techniques and apparatus for layer 1 triggered mobility communication. Background Technology

[0002] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems employ multiple access technologies that enable communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems, and Long Term Evolution (LTE). LTE / LTE-Advanced is a collection of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard issued by the 3rd Generation Partnership Project (3GPP).

[0003] A wireless network may include one or more network nodes that support communication for wireless communication devices, such as user equipment (UE) or multiple UEs. A UE may communicate with network nodes via downlink and uplink communication. A "downlink" (or "DL") refers to the communication link from the network node to the UE, and an "uplink" (or "UL") refers to the communication link from the UE to the network node. Some wireless networks may support device-to-device communication, such as via local links (e.g., sidelinks (SL), wireless local area network (WLAN) links, and / or wireless personal area network (WPAN) links, etc.).

[0004] The aforementioned multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables different UEs to communicate at the city, country, region, and / or global levels. New Radio (NR) (which may be referred to as 5G) is a set of enhancements to the LTE mobile standard issued by 3GPP. NR is designed to better support mobile broadband internet access by: improving spectrum efficiency; reducing costs; improving service; utilizing new spectrum; and better integrating with other open standards by using Orthogonal Frequency Division Multiplexing (OFDM) with Cyclic Prefix (CP) on the downlink (CP-OFDM), and CP-OFDM and / or Single Carrier Frequency Division Multiplexing (SC-FDM) (also known as Discrete Fourier Transform Extended OFDM (DFT-s-OFDM)) on the uplink; and supporting beamforming, Multiple-Input Multiple-Output (MIMO) antenna technologies and carrier aggregation. Further improvements to LTE, NR, and other radio access technologies remain useful as the demand for mobile broadband access continues to increase. Attached Figure Description

[0005] To gain a full understanding of the foregoing features of this disclosure, a more specific description of the invention, briefly outlined above, can be obtained by referring to various aspects, some of which are illustrated in the accompanying drawings. However, it should be noted that the drawings illustrate only certain typical aspects of this disclosure and are therefore not to be considered as limiting its scope, as other equally valid aspects are permissible in this description. The same reference numerals in different drawings may identify the same or similar elements.

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

[0007] Figure 2 This is a diagram illustrating an example of communication between a network node and a user equipment (UE) in a wireless network according to the present disclosure.

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

[0009] Figure 4 This is a diagram illustrating an example of a Layer 1 / Layer 2 triggered mobility (LTM) process according to this disclosure.

[0010] Figure 5 An example logical architecture of a distributed radio access network according to this disclosure is illustrated.

[0011] Figure 6 This is a diagram illustrating an example of multi-transmitter and receiver communication according to this disclosure.

[0012] Figure 7 This is a diagram illustrating an example of using a beam for communication between a network node and a UE according to this disclosure.

[0013] Figure 8 This is a diagram illustrating an example of configuring a UE for an LTM procedure, based on this disclosure.

[0014] Figure 9 This is a diagram illustrating an example of simultaneous transmission multiple points (STxMP) operation associated with the Unified Transmission Configuration Indicator (TCI) framework, based on this disclosure.

[0015] Figure 10 This is a diagram illustrating an example process performed, for example, at the UE or a device of the UE, according to this disclosure.

[0016] Figure 11 This is a diagram illustrating another example process performed, for example, at the UE or at a device of the UE, according to this disclosure.

[0017] Figure 12This is a diagram illustrating an example process performed, for example, at a network node or a device of a network node, according to the present disclosure.

[0018] Figure 13 This is a diagram illustrating another example process performed according to this disclosure, for example at a network node or a device of a network node.

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

[0020] Figure 15 This is a diagram of an example device for wireless communication according to the present disclosure. Summary of the Invention

[0021] In some aspects, a method of wireless communication performed by a user equipment (UE) includes: transmitting a capability indication associated with a Layer 1 / Layer 2 triggered mobility (LTM) capability based on a Medium Access Control (MAC) Control Element (MAC-CE) cell handover operation; and receiving a configuration based on the capability indication.

[0022] In some aspects, a method of wireless communication performed by a UE includes: transmitting a TCI capability associated with a Unified Transmission Configuration Indication (TCI) framework for simultaneous transmission of multipoint (STxMP) communication; and receiving a TCI configuration based on the TCI capability, wherein the TCI configuration is used to apply one or more of two or more TCI states.

[0023] In some aspects, a method of wireless communication performed by a network node includes: receiving from a UE a capability indication associated with an LTM capability related to a MAC-CE cell handover operation; and transmitting configuration based on the capability indication.

[0024] In some aspects, a method of wireless communication performed by a network node includes: receiving TCI capabilities associated with a unified TCI framework for STxMP communication; and transmitting TCI configuration based on the TCI capabilities, wherein the TCI configuration is used to apply one or more of two or more TCI states.

[0025] In some aspects, a UE for wireless communication includes: one or more memories; and one or more processors coupled to the one or more memories, the one or more processors being configured to cause the UE to: transmit a capability indication associated with LTM capability in accordance with a MAC-CE cell handover operation; and receive configuration in accordance with the capability indication.

[0026] In some aspects, a UE for wireless communication includes: one or more memories; and one or more processors coupled to the one or more memories, the one or more processors being configured to cause the UE to: transmit TCI capabilities associated with a unified TCI framework for STxMP communication; and receive TCI configuration based on the TCI capabilities, wherein the TCI configuration is used to apply one or more of two or more TCI states.

[0027] In some aspects, a network node for wireless communication includes: one or more memories; and one or more processors coupled to the one or more memories, the one or more processors being configured to cause the network node to: receive from a UE a capability indication associated with LTM capabilities related to MAC-CE cell handover operations; and transmit configuration based on the capability indication.

[0028] In some aspects, a network node for wireless communication includes: one or more memories; and one or more processors coupled to the one or more memories, the one or more processors being configured to cause the network node to: receive TCI capabilities associated with a unified TCI framework for STxMP communication; and transmit TCI configuration based on the TCI capabilities, wherein the TCI configuration is used to apply one or more of two or more TCI states.

[0029] In some aspects, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a UE, cause the UE to: transmit a capability indication associated with LTM capability in accordance with a MAC-CE cell handover operation; and receive configuration in accordance with the capability indication.

[0030] In some aspects, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a UE, cause the UE to: transmit TCI capabilities associated with a unified TCI framework for STxMP communication; and receive TCI configurations based on the TCI capabilities, wherein the TCI configurations are used to apply one or more of two or more TCI states.

[0031] In some aspects, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a network node, cause the network node to: receive a capability indication from a UE associated with LTM capabilities related to MAC-CE cell handover operations; and transmit configuration according to the capability indication.

[0032] In some aspects, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a network node, cause the network node to: receive TCI capabilities associated with a unified TCI framework for STxMP communication; and transmit TCI configuration according to the TCI capabilities, wherein the TCI configuration is used to apply one or more of two or more TCI states.

[0033] In some aspects, an apparatus for wireless communication includes: components for transmitting a capability indication associated with LTM capability in accordance with a MAC-CE cell handover operation; and components for receiving configuration in accordance with the capability indication.

[0034] In some aspects, an apparatus for wireless communication includes: components for transmitting TCI capabilities associated with a unified TCI framework for STxMP communication; and components for receiving TCI configurations based on the TCI capabilities, wherein the TCI configurations are for applying one or more of two or more TCI states.

[0035] In some aspects, an apparatus for wireless communication includes: a component for receiving from a UE a capability indication associated with an LTM capability related to a MAC-CE cell handover operation; and a component for transmitting a configuration based on the capability indication.

[0036] In some aspects, an apparatus for wireless communication includes: components for receiving TCI capabilities associated with a unified TCI framework for STxMP communication; and components for transmitting TCI configurations according to the TCI capabilities, wherein the TCI configurations are used to apply one or more of two or more TCI states.

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

[0038] The features and technical advantages of the examples according to this disclosure have been summarized rather extensively above in order to better understand the detailed description below. Additional features and advantages will be described below. The disclosed concepts and specific examples can be readily used as the basis for modifying or designing other structures for achieving the same purpose as this disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, in both their organization and manner of operation, and the associated advantages, will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the drawings provided is for illustrative and descriptive purposes and not as a definition of limitation of the claims.

[0039] While aspects are described herein by way of example, those skilled in the art will understand that such aspects can be implemented in many different arrangements and scenarios. The techniques described herein can be implemented using different platform types, devices, systems, shapes, sizes, and / or package arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-modular components (e.g., end-user equipment, vehicles, communication equipment, computing devices, industrial equipment, retail / shopping devices, medical devices, and / or artificial intelligence devices). Aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, and / or system-level components. Devices incorporating the described aspects and features may include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals may include one or more components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders, and / or summers). The aspects described herein are intended to be practiced in a wide variety of devices, components, systems, distributed arrangements, and / or end-user equipment of various sizes, shapes, and configurations. Detailed Implementation

[0040] User equipment (UE) mobility can impact network performance. For example, when a UE moves relative to a network node (such as a cell tower), the signal strength between the UE and the network node may be affected. If the signal strength decreases, network performance may be negatively affected. Using Layer 1 / Layer 2 (L1 / L2) triggered mobility (LTM), the UE and / or network node can identify potential network performance issues anticipated due to the UE's movement relative to the network node. If a potential network performance issue could lead to a poor user experience, the UE can be transferred to a new network node via a handover process.

[0041] The decision to transition a UE to a different network node is typically handled by the serving network node (e.g., the network node communicating with the UE). In some cases, the UE may be in a better position to determine whether to initiate an LTM transition. UEs are not usually configured to initiate or process LTM transitions, which may delay transitions that would otherwise improve network performance.

[0042] Multiple Transmit and Receive Points (mTRP) typically refers to the coordinated deployment and operation of multiple network nodes to simultaneously serve a single UE or multiple UEs. Transmit Configuration Indication (TCI) helps facilitate signaling for specific configurations related to channel state information. A unified TCI framework allows TCI to be applied across different system components and interfaces. In the context of mTRP, a unified TCI framework can provide consistency across network nodes. However, a UE can be configured with multiple TCI states, and no single TCI should be applied to the configuration or indication of every mTRP channel.

[0043] Various aspects are involved in the LTM process as a whole. Some aspects concern the UE capabilities used in the LTM process more specifically. In some examples, the UE sends a capability indication associated with the LTM capability based on a MAC-CE cell handover operation and receives configuration based on the capability indication. In some examples, the network node receives the capability indication associated with the LTM capability based on a MAC-CE cell handover operation and sends configuration based on the capability indication.

[0044] Specific aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. In some examples, by sending an LTM capability indication, the UE can be configured to process certain aspects of the LTM procedure according to the UE's capabilities. For example, the UE can be configured to apply an appropriate timing advance (TA) value and perform certain measurements based on, for example, whether the LTM candidate cell is the UE's serving cell. In some examples, by sending configuration according to the capability indication, the network node can configure the UE to perform LTM more efficiently.

[0045] Various aspects can be considered holistically in relation to Simultaneous Transmit Multipoint (STxMP) communication. Some aspects are more specifically related to STxMP communication within a unified TCI framework. In some examples, the UE transmits TCI capabilities associated with the unified TCI framework used for STxMP communication and receives TCI configuration based on these TCI capabilities. The TCI configuration can be used to apply one or more of two or more TCI states. In some examples, the network node receives TCI capabilities associated with the unified TCI framework used for STxMP communication and transmits TCI configuration based on these TCI capabilities.

[0046] Specific aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. In some examples, by sending TCI capabilities, the UE can be configured to apply one or more TCI states to mTRP communications. In some examples, by sending configurations based on TCI capabilities, a network node can configure the UE to participate more efficiently in STxMP communications under a unified TCI framework.

[0047] Various aspects of this disclosure are described more fully below with reference to the accompanying drawings. However, this disclosure may be embodied in many different forms and should not be construed as limited to any particular structure or function presented throughout this disclosure. Rather, these aspects are provided to make this disclosure thorough and complete, and to fully convey the scope of this disclosure to those skilled in the art. Those skilled in the art will appreciate that the scope of this disclosure is intended to cover any aspect of this disclosure disclosed herein, whether implemented independently or in combination with any other aspect of this disclosure. For example, any number of aspects set forth herein may be used to implement an apparatus or method of practice. Furthermore, the scope of this disclosure is intended to cover such apparatus or methods practiced using structures, functions, or structures and functions other than or different from the aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure herein may be embodied by one or more elements of the claims.

[0048] Various devices and techniques will now be used to illustrate several aspects of a telecommunications system. These devices and techniques will be described in detail below and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, or algorithms (collectively, “elements”). These elements can be implemented using hardware, software, or a combination thereof. 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.

[0049] Although terms generally associated with 5G or New Radio (NR) Radio Access Technology (RAT) may be used herein to describe aspects, aspects of this disclosure may be applied to other RATs, such as 3G RAT, 4G RAT and / or 5G and later (e.g., 6G) RATs.

[0050] 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 (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements of a 5G (e.g., NR) network and / or elements of a 4G (e.g., LTE) network, etc. The wireless network 100 may include one or more network nodes 110 (shown as network nodes 110a, 110b, 110c, and 110d), one or more UEs 120 (shown as UEs 120a, 120b, 120c, 120d, and 120e), and / or other entities. Network node 110 is a network node that communicates with UE 120. As shown, network node 110 may include one or more network nodes. For example, network node 110 can be an aggregated network node, meaning that an aggregated network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single radio access network (RAN) node (e.g., within a single device or unit). As another example, network node 110 can be a decomposed network node (sometimes referred to as a decomposed base station), meaning that network node 110 is configured to utilize a protocol stack that is physically or logically distributed among two or more nodes (such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)).

[0051] In some examples, network node 110 is or includes network nodes (such as RUs) that communicate with UE 120 via a radio access link. In some examples, network node 110 is or includes network nodes (such as DUs) that communicate with other network nodes 110 via a fronthaul or midhaul link. In some examples, network node 110 is or includes network nodes (such as CUs) that communicate with other network nodes 110 via a midhaul link or with the core network via a backhaul link. In some examples, network node 110 (such as aggregated network node 110 or decomposed network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. Network node 110 may include, for example, NR base stations, LTE base stations, Node Bs, eNBs (e.g., in 4G), gNBs (e.g., in 5G), access points, Transmit / Receive Points (TRPs), DUs, RUs, CUs, network mobility elements, core network nodes, network elements, network equipment, RAN nodes, or combinations thereof. In some examples, network nodes 110 can interconnect with each other or with one or more other network nodes 110 in the wireless network 100 using any suitable transport network through various types of fronthaul interfaces, midhaul interfaces, and / or backhaul interfaces (such as direct physical connections, air interfaces, or virtual networks).

[0052] In some examples, network node 110 may provide communication coverage for a specific geographic area. In the 3rd Generation Partnership Project (3GPP), depending on the context of terminology use, the term "cell" may refer to the coverage area of ​​network node 110 and / or the network node subsystem serving that coverage area. Network node 110 may provide communication coverage for macrocells, picocells, femtocells, and / or another type of cell. A macrocell may cover a relatively large geographic area (e.g., with a radius of several kilometers) and may allow unrestricted access by UE 120 with a service subscription. A picocell may cover a relatively small geographic area and may allow unrestricted access by UE 120 with a service subscription. A femtocell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UE 120 associated with the femtocell (e.g., UE 120 in a Closed Subscriber Group (CSG)). Network node 110 used for macrocells may be referred to as a macro network node. Network node 110 used for picocells may be referred to as a pico network node. The network node 110 used for femtocells can be referred to as a femtocell network node or a home network node. Figure 1 In the example shown, network node 110a can be a macro network node for macro cell 102a, network node 110b can be a pico network node for pico cell 102b, and network node 110c can be a femto network node for femto cell 102c. Network nodes can support one or more (e.g., three) cells. In some examples, the cells may not necessarily be stationary, and the geographical area of ​​the cells may move depending on the location of the mobile network node 110 (e.g., a mobile network node).

[0053] In some aspects, the term "base station" or "network node" may refer to an aggregated base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, "base station" or "network node" may refer to a CU, DU, RU, a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network node" may refer to a device configured to perform one or more functions (such as those described herein in conjunction with network node 110). In some aspects, the term "base station" or "network node" may refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, each of multiple different devices (which may be located in the same geographical location or different geographical locations) may be configured to perform at least a portion of a function, or to repeatedly perform at least a portion of that function, and the term "base station" or "network node" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network node" may refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, two or more base station functions can be instantiated on a single device. In some aspects, the term "base station" or "network node" may refer to one base station function rather than another. In this way, a single device may include more than one base station.

[0054] Wireless network 100 may include one or more relay stations. A relay station is a network node that can receive data transmissions from upstream nodes (e.g., network node 110 or UE 120) and transmit data to downstream nodes (e.g., UE 120 or network node 110). A relay station may be a UE 120 that can relay transmissions to other UE 120s. 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. The network node 110 for relay communication may be referred to as a relay station, relay base station, relay network node, relay node, repeater, etc.

[0055] Wireless network 100 can be a heterogeneous network, comprising different types of network nodes 110, such as macro network nodes, pico network nodes, femto network nodes, relay network nodes, etc. These different types of network nodes 110 may have different transmit power levels, different coverage areas, and / or different effects on interference in wireless network 100. For example, macro network nodes may have high transmit power levels (e.g., 5 watts to 40 watts), while pico network nodes, femto network nodes, and relay network nodes may have lower transmit power levels (e.g., 0.1 watts to 2 watts).

[0056] Network controller 130 may be coupled to or communicate with network node set 110, and may provide coordination and control for these network nodes 110. Network controller 130 may communicate with network nodes 110 via a backhaul or midhaul link. Network nodes 110 may also communicate directly with each other, or indirectly via a wireless or wired backhaul link. In some aspects, network controller 130 may be a CU or core network device, or may include a CU or core network device.

[0057] UE 120 may be distributed throughout the wireless network 100, and each UE 120 may be stationary or mobile. UE 120 may include, for example, access terminals, terminals, mobile stations, and / or subscriber units. UE 120 may be 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, smart jewelry (e.g., a smart ring or smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, industrial manufacturing equipment, a GPS device, a UE function of a network node, and / or any other suitable device configured to communicate via wireless or wired media.

[0058] Some UEs 120 may be considered Machine-Type Communication (MTC) or Evolved or Enhanced Machine-Type Communication (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, robots, unmanned aerial vehicles, remote devices, sensors, instruments, monitors, and / or location tags that can communicate with network nodes, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered Internet of Things (IoT) devices and / or may be implemented as NB-IoT (Narrowband IoT) devices. Some UEs 120 may be considered customer premises equipment. UEs 120 may be contained within a housing that houses components of the UE 120, such as processor components and / or memory components. In some examples, the processor components and memory components may be coupled together. For example, the processor components (e.g., one or more processors) and memory components (e.g., memory) may be operatively coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0059] Generally, any number of wireless networks 100 can be deployed in a given geographical area. Each wireless network 100 can support a specific RAT and can operate on one or more frequencies. A RAT may be referred to as a radio technology, air interface, etc. A frequency may be referred to as a carrier, frequency channel, etc. Each frequency in a given geographical area can support a single RAT to avoid interference between wireless networks using different RATs. In some cases, NR or 5G RAT networks can be deployed.

[0060] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more sidelink channels (e.g., without using network node 110 as an intermediary device to communicate with each other). For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols) and / or mesh networks. In such examples, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by network node 110.

[0061] Devices in Wireless Network 100 can communicate using the electromagnetic spectrum, which can be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, devices in Wireless Network 100 can communicate using one or more operating frequency bands. In 5G NR, two initial operating frequency bands have been designated as frequency ranges FR1 (410MHz to 7.125GHz) and FR2 (24.25GHz to 52.6GHz). It should be understood that although a portion of FR1 is greater than 6GHz, FR1 is often (interchangeably) referred to as the “sub-6GHz” band in various documents and articles. Similar naming issues sometimes occur with FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, although this is different from the Extremely High Frequency (EHF) band (30GHz to 300GHz) designated as a “millimeter wave” band by the International Telecommunication Union (ITU).

[0062] The frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR studies have identified the operating bands used for these mid-band frequencies as the frequency range designation FR3 (7.125 GHz to 24.25 GHz). Bands falling within FR3 can inherit FR1 and / or FR2 characteristics, thus effectively extending the features of FR1 and / or FR2 to mid-band frequencies. Furthermore, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as the frequency range designations 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). Each of these higher frequency bands falls within the EHF band.

[0063] Considering the examples above, unless otherwise specifically stated, it should be understood that if the term "below 6 GHz" is used herein, it can broadly refer to frequencies below 6 GHz, within FR1, or including intermediate frequency bands. Furthermore, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" is used herein, it can broadly refer to frequencies that can include intermediate frequency bands, within FR2, FR4, FR4-a, or FR4-1 and / or FR5, or within the EHF band. Modifications to frequencies included in these operating frequency bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) are contemplated, and the techniques described herein are applicable to those modified frequency ranges.

[0064] In some aspects, UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may send a capability indication associated with LTM capabilities in accordance with MAC-CE cell handover operations, and receive configuration based on the capability indication. In some aspects, as described in more detail elsewhere herein, the communication manager 140 may send TCI capabilities associated with a unified TCI framework for STxMP communications, and receive TCI configuration based on the TCI capabilities, wherein the TCI configuration is used to apply one or more of two or more TCI states. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0065] In some aspects, network node 110 may include communication manager 150. As described in more detail elsewhere herein, communication manager 150 may receive capability indications associated with LTM capabilities related to MAC-CE cell handover operations from the UE, and transmit configurations based on the capability indications. In some aspects, as described in more detail elsewhere herein, communication manager 150 may receive TCI capabilities associated with a unified TCI framework for STxMP communications, and transmit TCI configurations based on the TCI capabilities, wherein the TCI configurations are used to apply one or more of two or more TCI states. Additionally or alternatively, communication manager 150 may perform one or more other operations described herein.

[0066] As indicated above, Figure 1 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 1 The examples described are different.

[0067] Figure 2 This is a diagram illustrating example 200 of communication between network node 110 and UE 120 in a wireless network 100 according to this disclosure. Network node 110 may be equipped with antenna sets 234a to 234t, such as... T One antenna ( T ≥1). UE 120 may be equipped with antenna sets 252a to 252r, such as R One antenna ( R ≥1). Network node 110 of Example 200 includes one or more radio frequency components, such as antenna 234 and modem 232. In some examples, network node 110 may include an interface, communication components, or another component that facilitates communication with UE 120 or another network node. Some network node 110 may not include radio frequency components that facilitate direct communication with UE 120, such as one or more CUs or one or more DUs.

[0068] At network node 110, transmitting processor 220 may receive data from data source 212 intended for use by UE 120 (or a set of UEs 120). Transmitting processor 220 may select one or more modulation and decoding schemes (MCS) for UE 120 based at least in part on one or more channel quality indicators (CQIs) received from UE 120. Network node 110 may process (e.g., encode and modulate) the data for UE 120 based at least in part on the MCS selected for UE 120 and may provide data symbols for UE 120. Transmitting processor 220 may process system information (e.g., semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper-layer signaling) and provide overhead symbols and control symbols. Transmitting processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signal (PSS) or secondary synchronization signal (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 can perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols where applicable, and can transmit a set of output symbol streams (e.g., T Each output symbol stream is provided to a corresponding set of modems 232 (e.g., ...). T Each modem 232a to 232t can be used to process a corresponding output symbol stream (e.g., for OFDM) to obtain an output sample stream. For example, each output symbol stream can be provided to a modulator component (MOD) of modem 232. Each modem 232 can use a corresponding modulator component to process the corresponding output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modem 232 can also use a corresponding modulator component to process the output sample stream (e.g., convert to analog, amplify, filter, and / or up-convert) to obtain a downlink signal. Modems 232a to 232t can be connected via a corresponding set of antennas 234 (e.g., T Each antenna (shown as antennas 234a to 234t) is used to transmit a set of downlink signals (e.g., ...). T (One downlink signal).

[0069] At UE 120, a set of antennas 252 (shown as antennas 252a to 252r) can receive downlink signals from network node 110 and / or other network nodes 110 and can transmit a set of received signals (e.g., R The received signals are provided to a group of modems 254 (e.g., REach modem 254 (shown as modems 254a to 254r) may receive a signal. For example, each received signal may be provided to a demodulator component (shown as DEMOD) of modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, down-convert, and / or digitize) the received signal to obtain an input sample. Each modem 254 may use a demodulator component to further process the input sample (e.g., for OFDM) to obtain a received symbol. MIMO detector 256 may obtain the received symbols from modem 254, perform MIMO detection on the received symbols where applicable, and provide the detected symbols. Receiver processor 258 may process (e.g., demodulate and decode) the detected symbols, provide the decoded data for UE 120 to data sink 260, and provide the decoded control information and system information to controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor can determine parameters such as the Reference Signal Received Power (RSRP), Received Signal Strength Indicator (RSSI), Reference Signal Received Quality (RSRQ), and / or CQI. In some examples, one or more components of the UE 120 may be included in the housing 284.

[0070] Network controller 130 may include communication unit 294, controller / processor 290, and memory 292. Network controller 130 may include one or more devices, for example, in a core network. Network controller 130 may communicate with network node 110 via communication unit 294.

[0071] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include one or more antenna panels, one or more antenna groups, one or more sets of antenna elements and / or one or more antenna arrays, etc., or may be included within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements and / or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements and / 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 and / or coupled to one or more transmitting and / or receiving components (such as...). Figure 2 One or more antenna elements (one or more components in a )

[0072] On the uplink, at UE 120, the transmit processor 264 can receive and process data from data source 262 and control information from controller / processor 280 (e.g., for reporting including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 can generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 can be pre-decoded by the TX MIMO processor 266 where applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to network node 110. In some examples, the modem 254 of UE 120 may include a modulator and demodulator. In some examples, UE 120 includes a transceiver. The transceiver may include any combination of antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, and / or TX MIMO processor 266. The transceiver may be used by a processor (e.g., controller / processor 280) and memory 282 to execute this document (e.g., reference). Figures 4 to 15 ( ) any aspect of the methods described in the method.

[0073] At network node 110, uplink signals from UE 120 and / or other UEs may be received by antenna 234, processed by modem 232 (e.g., demodulator component of modem 232 (shown as DEMOD)), detected by MIMO detector 236, and further processed by receiver processor 238 to obtain decoded data and control information transmitted by UE 120. Receiver processor 238 may provide the decoded data to data sink 239 and the decoded control information to controller / processor 240. Network node 110 may include communication unit 244 and may communicate with network controller 130 via communication unit 244. Network node 110 may include scheduler 246 to schedule one or more UEs 120 for downlink and / or uplink communication. In some examples, modem 232 of network node 110 may include modulator and demodulator. In some examples, network node 110 includes transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to execute this document (e.g., reference). Figures 4 to 15 ( ) any aspect of the methods described in the method.

[0074] The controller / processor 240 of network node 110, the controller / processor 280 of UE 120 and / or Figure 2Any other component may execute one or more technologies associated with LTM and / or STxMP under the unified TCI framework, as described in more detail elsewhere herein. For example, the controller / processor 240 of network node 110, the controller / processor 280 of UE 120, and / or Figure 2 Any other component that can execute or direct, for example Figure 10 Process 1000 Figure 11 Process 1100 Figure 12 Process 1200 Figure 13 The operation of process 1300 and / or other processes as described herein. Memory 242 and memory 282 may store data and program code for network node 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, when executed by one or more processors of network node 110 and / or UE 120 (e.g., direct execution, or execution after compilation, transformation, and / or interpretation), these one or more instructions may cause the one or more processors, UE 120, and / or network node 110 to perform or direct, for example... Figure 10 Process 1000 Figure 11 Process 1100 Figure 12 Process 1200 Figure 13 The operation of process 1300 and / or other processes as described herein. In some examples, the execution instructions may include run instructions, transform instructions, compile instructions and / or interpret instructions, etc.

[0075] In some aspects, UE 120 includes: components for transmitting a capability indication associated with LTM capability in accordance with MAC-CE cell handover operations; and / or components for receiving configuration in accordance with the capability indication. Components for enabling UE 120 to perform the operations described herein may include, for example, one or more of the following: communication manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller / processor 280, or memory 282.

[0076] In some aspects, the UE includes: components for transmitting TCI capabilities associated with a unified TCI framework for STxMP communication; and / or components for receiving TCI configurations based on the TCI capabilities, wherein the TCI configurations are used to apply one or more of two or more TCI states. Components for enabling the UE 120 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.

[0077] In some aspects, network node 110 includes: components for receiving from UE 120 a capability indication associated with LTM capabilities related to MAC-CE cell handover operations; and / or components for transmitting configuration based on the capability indication. Components for enabling network node 110 to perform the operations described herein may include, for example, one or more of the following: communication manager 150, transmit processor 220, TXMIMO processor 230, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller / processor 240, memory 242, or scheduler 246.

[0078] In some aspects, network node 110 includes: components for receiving TCI capabilities associated with a unified TCI framework for STxMP communication; and / or components for transmitting TCI configurations according to the TCI capabilities, wherein the TCI configurations are used to apply one or more of two or more TCI states. Components for enabling network node 110 to perform the operations described herein may include, for example, one or more of the following: communication manager 150, transmit processor 220, TX MIMO processor 230, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller / processor 240, memory 242, or scheduler 246.

[0079] In some respects, individual processors can be described as performing all functions executed by the one or more processors. In other respects, the one or more processors can jointly perform a set of functions. For example, the processors of a first set (one or more) of the one or more processors can be described as performing a first function executed by the one or more processors, and the processors of a second set (one or more) of the one or more processors can be described as performing a second function executed by the one or more processors. The processors of the first set and the processors of the second set can be the same set of processors or can be different sets of processors. The reference to "one or more processors" should be understood as referring to a combination of processors. Figure 2Any one or more processors described. The reference to "one or more memories" should be understood to refer to 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.

[0080] Although Figure 2 The boxes in the diagram are illustrated as different components, but the functions described above with respect to these boxes may be implemented in a single hardware, software, or combined component, or in various combinations of components. For example, the functions described with respect to transmit processor 264, receive processor 258, and / or TX MIMO processor 266 may be performed by or under the control of controller / processor 280.

[0081] As indicated above, Figure 2 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 2 The examples described are different.

[0082] The deployment of communication systems such as 5G NR systems can be arranged in a variety of ways using various components or parts. In a 5G NR system or network, network nodes, network entities, network mobility elements, RAN nodes, core network nodes, network elements, base stations, or network equipment can be implemented in either a converged or decomposed architecture. For example, a base station (such as a Node B (NB), evolved NB (eNB), NR base station, 5G NB, access point (AP), TRP, or cell, etc.) or one or more units (or components) performing base station functionality can be implemented as a converged base station (also known as a standalone base station or monolithic base station) or a decomposed base station. A "network entity" or "network node" can refer to a decomposed base station or one or more units of a decomposed base station (such as one or more CUs, one or more DUs, one or more RUs, or combinations thereof).

[0083] Aggregated base stations (e.g., aggregated network nodes) can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or cell). Decomposed base stations (e.g., decomposed network nodes) can be configured to utilize a protocol stack that is physically or logically distributed across two or more cells (such as one or more CUs, one or more DUs, or one or more RUs). In some examples, the CU may be implemented within a network node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other network nodes. DUs may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may also be implemented as a virtual cell, such as a Virtual Central Unit (VCU), a Virtual Distributed Unit (VDU), or a Virtual Radio Unit (VRU), etc.

[0084] Base station type operation or network design can take into account the aggregation characteristics of base station functionality. For example, decomposed base stations can be utilized in IAB networks, Open Radio Access Networks (O-RAN (such as network configurations initiated by the O-RAN Alliance)), or Virtualized Radio Access Networks (vRAN, also known as Cloud Radio Access Networks (C-RAN)) to facilitate the scaling of communication systems by separating base station functionality into one or more units that can be deployed independently. Decomposed base stations can include functionality implemented across two or more units at various physical locations, as well as functionality virtually implemented for at least one unit, which enables flexibility in network design. Each unit of a decomposed base station can be configured for wired or wireless communication with at least one other unit of the decomposed base station.

[0085] Figure 3 This is an illustration of an example disaggregated base station architecture 300 according to this disclosure. The disaggregated base station architecture 300 may include a CU 310, which may communicate directly with the core network 320 via a backhaul link, or indirectly with the core network 320 via one or more disaggregated control units (such as near-RT RIC 325 via an E2 link, or a non-RT RIC 315 associated with a Service Management and Orchestration (SMO) framework 305, or both). The CU 310 may communicate with one or more DUs 330 via a corresponding midhaul link (such as via an F1 interface). Each DU 330 may communicate with one or more RUs 340 via a corresponding fronthaul link. Each RU 340 may communicate with one or more UEs 120 via a corresponding radio frequency (RF) access link. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.

[0086] Each of these units (including CU 310, DU 330, RU 340) and the near-RT RIC 325, non-RT RIC 315, and SMO frame 305 may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via wired or wireless transmission media. Each of these units, or an associated processor or controller providing instructions to one or more communication interfaces of the respective unit, may be configured to communicate with one or more units in other units via transmission media. In some examples, each unit may include a wired interface and a wireless interface configured to receive signals via a wired transmission media or transmit signals to one or more units in other units, and the wireless interface may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive signals via a wireless transmission media or transmit signals to one or more units in other units, or both.

[0087] In some aspects, the CU 310 can host one or more higher-level control functions. Such control functions may include Radio Resource Control (RRC) functions, Packet Data Convergence Protocol (PDCP) functions, or Service Data Adaptation Protocol (SDAP) functions, etc. Each control function can be implemented using an interface configured to signal to other control functions hosted by the CU 310. The CU 310 can be configured to handle user plane functions (e.g., Central Unit-User Plane (CU-UP) functions), control plane functions (e.g., Central Unit-Control Plane (CU-CP) functions), or combinations thereof. In some implementations, the CU 310 can be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 310 can be implemented to communicate with the DU 330 for network control and signaling purposes, as needed.

[0088] Each DU 330 may correspond to a logical unit comprising one or more base station functions for controlling the operation of one or more RU 340s. In some aspects, the DU 330 may host one or more of the Radio Link Control (RLC) layer, Medium Access Control (MAC) layer, and one or more high physical (PHY) layers, at least in part, according to functional splits (such as those defined by 3GPP). In some aspects, 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 aspects, the DU 330 may also host one or more low PHY layers, such as those implemented by one or more modules for Fast Fourier Transform (FFT), Inverse FFT (iFFT), Digital Beamforming, or Physical Random Access Channel (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 330 or with control functions hosted by the CU 310.

[0089] Each RU 340 can implement lower-layer functionality. In some deployments, the RU 340 controlled by the DU 330 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 lower-layer function splitting). In this architecture, each RU 340 can be operated to handle over-the-air (OTA) communications with one or more UE 120s. In some specific implementations, the real-time and non-real-time aspects of control plane and user plane communications with the RU 340 can be controlled by the corresponding DU 330. In some scenarios, this configuration allows each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0090] The SMO framework 305 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 305 can be configured to support 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 305 can be configured to interact with cloud computing platforms such as the Open Cloud (O-Cloud) platform 390 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 310, DU 330, RU 340, non-RT RIC 315, and near-RTTRIC 325. In some specific implementations, the SMO framework 305 may communicate with the hardware aspects of the 4G RAN, such as the Open eNB (O-eNB) 311, via the O1 interface. Additionally, in some implementations, the SMO framework 305 can communicate directly with each of one or more RUs 340 via a corresponding O1 interface. The SMO framework 305 may also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305.

[0091] The non-RT RIC 315 can be configured to include logical 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 325. The non-RT RIC 315 can be coupled to or communicate with the near-RT RIC 325, such as via an A1 interface. The near-RT RIC 325 can be configured to include logical functions that enable near real-time control and optimization of RAN elements and resources via an interface, such as an E2 interface, through data collection and actions, connecting one or more CU 310s, one or more DU 330s, or both, and O-eNBs to the near-RT RIC 325.

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

[0093] As indicated above, Figure 3 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 3 The examples described are different.

[0094] Figure 4 This is a diagram illustrating Example 400 of the LTM process according to this disclosure.

[0095] In some examples, network node 110 may instruct UE 120 to change serving cells, such as when UE 120 leaves the coverage area of ​​its current serving cell (sometimes referred to as the source cell) and moves toward the coverage area of ​​a neighboring cell (sometimes referred to as the target cell). In some cases, network node 110 may instruct UE 120 to change cells using a Layer 3 (L3) handover procedure. The L3 handover procedure may include: network node 110 sending an RRC reconfiguration message to UE 120 instructing UE 120 to perform a handover procedure to the target cell. This RRC reconfiguration message may be sent in response to UE 120 providing an L3 measurement report to network node 110, which indicates signal strength measurements associated with various cells (e.g., measurements associated with the source cell and one or more neighboring cells). In response to receiving the RRC reconfiguration message, UE 120 may communicate with the source cell and the target cell to detach from the source cell and connect to the target cell (e.g., UE 120 may establish an RRC connection with the target cell). Once the handover is complete, the target cell can communicate with the User Plane Function (UPF) of the core network to instruct the UPF to switch the user plane path of UE 120 from the source cell to the target cell. The target cell can also communicate with the source cell to indicate that the handover is complete and the source cell can be released.

[0096] Because of the multiple RRC reconfiguration messages and / or other L3 signaling and operations used to perform the handover process, the L3 handover process can be associated with high latency and high overhead. Therefore, in some examples, the UE 120 may be configured to perform lower-layer (e.g., L1 and / or L2) handover processes, sometimes referred to as LTM processes, such as... Figure 4 The example 400 LTM process is shown. (As shown) Figure 4 As shown, the LTM process can include four phases: LTM preparation phase, early synchronization phase (in... Figure 4 The LTM phase is shown as “early synchronization”, the LTM execution phase, and / or the LTM completion phase.

[0097] During the LTM preparation phase, and as indicated by reference numeral 405, UE 120 may be in an RRC connected state (sometimes referred to as RRC_Connected) with the source cell. As indicated by reference numeral 410, UE 120 may send, and network node 110 may receive, a measurement report (sometimes referred to as MeasurementReport), which may be an L3 measurement report. This measurement report may indicate signal strength measurements (e.g., RSRP, RSSI, RSRQ, and / or CQI) or similar measurements associated with the source cell and / or one or more neighboring cells. In some examples, based at least in part on this measurement report or other information, network node 110 may decide to use LTM, and therefore, as indicated by reference numeral 415, network node 110 may initiate LTM candidate preparation. For example, network node 110 may initiate LTM candidate preparation by sending an LTM candidate configuration via RRC as indicated by reference numeral 420 (discussed below) and receiving an RRC reconfiguration message as indicated by reference numeral 425 (discussed below).

[0098] As shown by reference numeral 420 in the accompanying drawings, network node 110 may send, and UE 120 may receive, an RRC reconfiguration message (sometimes referred to as an RRCReconfiguration message), which may include LTM candidate configurations. More specifically, the RRC reconfiguration message may indicate the configuration of one or more LTM candidate target cells, which may be candidate cells to become the serving cell of the UE and / or cells to which the UE 120 may later trigger to perform an LTM procedure. As shown by reference numeral 425 in the accompanying drawings, UE 120 may store the configuration of the one or more LTM candidate cell configurations and, in response, may send an RRC reconfiguration complete message (sometimes referred to as an RRCReconfigurationComplete message) to network node 110.

[0099] During the early synchronization phase, and as indicated by reference numeral 430, UE 120 may optionally perform downlink / uplink synchronization with a candidate cell associated with one or more LTM candidate cell configurations. For example, UE 120 may perform downlink synchronization and TA acquisition with one or more candidate target cells before receiving an LTM handover command (described in more detail below with reference numeral 445). In some respects, performing early synchronization with one or more candidate cells can reduce the latency associated with performing the Random Access Channel (RACH) procedure later in the LTM process, which is described in more detail below with reference numeral 455.

[0100] During the LTM execution phase, and as indicated by reference numeral 435, UE 120 may perform L1 measurements on the configured LTM candidate target cells, and thus may send a lower-layer (e.g., L1) measurement report to network node 110. As indicated by reference numeral 440, based at least in part on this lower-layer measurement report, network node 110 may decide to perform an LTM cell handover to the target cell. Therefore, as indicated by reference numeral 445, network node 110 may send, and UE 120 may receive, a MAC control element (MAC-CE) or similar message that triggers an LTM cell handover (this MAC-CE or similar message is sometimes referred to herein as a cell handover command). The cell handover command may include an indication of a candidate configuration index associated with the target cell. As indicated by reference numeral 450, based at least in part on receiving the cell handover command, UE 120 may switch to the configuration of the LTM candidate target cell (e.g., UE 120 may leave the source cell and apply the target cell configuration). Furthermore, as indicated by reference numeral 455, UE 120 may perform a RACH procedure toward the target cell, such as when the TA associated with the target cell is unavailable (e.g., in an example where UE 120 has not performed the early synchronization described above in conjunction with reference numeral 430). Figure 4 As shown in Example 400, the target cell and the serving cell can be part of the same network node. Alternatively, the target cell and the serving cell can be part of different network nodes, in which case the UE 120 can perform the RACH procedure with the network node associated with the target cell.

[0101] During the LTM completion phase and as indicated by reference numeral 460 in the attached figure, UE 120 may indicate successful completion of the LTM cell handover to the target cell. In this way, the cell handover to the target cell can be performed with less overhead than the L3 handover procedure, and / or the cell handover to the target cell is associated with lower latency compared to the L3 handover procedure.

[0102] In some respects, as described below compared to Figure 8 In more detail, UE 120 can be configured to send a capability report indicating the capabilities associated with the LTM procedure, and to receive configurations based on the capabilities of UE 120. In some respects, as part of the LTM procedure, UE 120 can receive a cell handover command with a TA indication based on whether UE 120 is able to measure TA.

[0103] As indicated above, Figure 4 This is provided as an example. Other examples are available relative to... Figure 4 The descriptions are different.

[0104] Figure 5 An example logical architecture of a distributed RAN 500 according to this disclosure is illustrated.

[0105] 5G access node 505 may include access node controller 510. Access node controller 510 may be a CU of distributed RAN 500. In some aspects, backhaul interfaces to 5G core network 515 may be terminated at access node controller 510. 5G core network 515 may include 5G control plane components 520 and 5G user plane components 525 (e.g., 5G gateways), and backhaul interfaces for one or both of the 5G control plane and 5G user plane may be terminated at access node controller 510. Additionally or alternatively, backhaul interfaces to one or more neighboring access nodes 530 (e.g., another 5G access node 505 and / or LTE access node) may be terminated at access node controller 510.

[0106] Access node controller 510 may include one or more TRPs 535 and / or be able to communicate with one or more TRPs (e.g., via an F1 control (F1-C) interface and / or an F1 user (F1-U) interface). TRP 535 may include DUs and / or RUs of the distributed RAN 500. In some aspects, TRP 535 may correspond to the above combination. Figure 1 The network node 110 is described. For example, different TRPs 535 may be included in different network nodes 110. Alternatively, multiple TRPs 535 may be included in a single network node 110. In some aspects, network node 110 may include a CU (e.g., access node controller 510) and / or one or more DUs (e.g., one or more TRPs 535). In some cases, TRP 535 may be referred to as a cell, panel, antenna array, or array.

[0107] The TRP 535 can connect to a single access node controller 510 or multiple access node controllers 510. In some respects, the architecture of the distributed RAN 500 can have dynamically configured split logical functions, referred to elsewhere in this document as function splitting. For example, the PDCP layer, RLC layer, and / or MAC layer can be configured to terminate at the access node controller 510 or the TRP 535.

[0108] In some aspects, multiple TRP 535s may transmit communications in the same Transmission Time Interval (TTI) (e.g., time slots, micro-slots, subframes, or symbols) or in different TTIs (e.g., the same communication or different communications) using different quasi-co-location (QCL) relationships (e.g., different spatial parameters, different TCI states, different pre-decoding parameters, and / or different beamforming parameters). In some aspects, the TCI state may be used to indicate one or more QCL relationships. TRP 535s may be configured to provide services to UE120 individually (e.g., using dynamic selection) or jointly (e.g., using joint transmission with one or more other TRP 535s).

[0109] In some respects, each TRP 535 may be associated with a network node (such as network node 110) (e.g., be a part of it). In some respects, one or more TRP 535s may be associated with a serving cell and / or a target cell. Furthermore, as discussed above, refer to... Figure 4 In Example 400, each serving cell and target cell can be associated with a network node (such as network node 110), and the serving cell and target cell can be part of the same network node or part of different network nodes. Therefore, each TRP 535 can be part of the same or different network nodes. For example, refer to... Figure 5 One of the TRPs 535 shown is associated with the neighboring access node 530, while the other TRPs 535 are associated with the access node 505.

[0110] As indicated above, Figure 5 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 5 The examples described are different.

[0111] Figure 6 This is a diagram illustrating example 600 of mTRP communication (sometimes referred to as multi-panel communication) according to this disclosure. Figure 6 As shown, multiple TRP 605s can communicate with the same UE 120. The TRP 605 can correspond to the above-described combination... Figure 5 The TRP 535 described.

[0112] Multiple TRPs 605 (shown as TRP A and TRP B) can communicate with the same UE 120 in a coordinated manner (e.g., using coordinated multicast) to improve reliability and / or increase throughput. Such communication can be coordinated via an interface between TRPs 605 (e.g., a backhaul interface and / or access node controller 510). When TRPs 605 are co-located at the same network node 110 (e.g., when TRPs 605 are different antenna arrays or panels of the same network node 110), the interface can have lower latency and / or higher capacity, and when TRPs 605 are located at different network nodes 110, the interface can have higher latency and / or lower capacity (compared to co-location). Different TRPs 605 can communicate with the UE 120 using different QCL relationships (e.g., different TCI states), different DMRS ports, and / or different layers (e.g., multi-layer communication).

[0113] In the first multi-TRP transmission mode (e.g., mode 1), a single physical downlink control channel (PDCCH) can be used to schedule downlink data communication on a single physical downlink shared channel (PDSCH). In this case, multiple TRPs 605 (e.g., TRP A and TRP B) can transmit communication to UE 120 on the same PDSCH. For example, a single codeword with different spatial layers for different TRPs 605 can be used to transmit communication (e.g., one codeword is mapped to a first set of layers transmitted by the first TRP 605 and to a second set of layers transmitted by the second TRP 605). As another example, multiple codewords can be used to transmit communication, where different codewords are transmitted by different TRPs 605 (e.g., using different sets of layers). In either case, different TRPs 605 can use different QCL relationships (e.g., different TCI states) for different DMRS ports corresponding to different layers. For example, the first TRP 605 may use a first QCL relationship or a first TCI state for a first group of DMRS ports corresponding to a first group layer, and the second TRP 605 may use a second (different) QCL relationship or a second (different) TCI state for a second (different) group of DMRS ports corresponding to a second (different) group layer. In some aspects, the TCI state in the downlink control information (DCI) (e.g., transmitted on the PDCCH, such as DCI format 1_0 or DCI format 1_1) may indicate a first QCL relationship (e.g., by indicating a first TCI state) and a second QCL relationship (e.g., by indicating a second TCI state). The first TCI state and the second TCI state may be indicated using the TCI field in the DCI. Generally, in this multi-TRP transmission mode (e.g., mode 1), the TCI field may indicate a single TCI state (for single TRP transmission) or multiple TCI states (for multi-TRP transmission as discussed herein).

[0114] In the second multi-TRP transmission mode (e.g., mode 2), multiple PDCCHs can be used to schedule downlink data communication for multiple corresponding PDSCHs (e.g., one PDCCH for each PDSCH). In this case, the first PDCCH can be scheduled to transmit a first codeword by the first TRP 605, and the second PDCCH can be scheduled to transmit a second codeword by the second TRP 605. Furthermore, the first DCI (e.g., transmitted by the first TRP 605) can be scheduled to communicate with the first PDSCH associated with a first set of DMRS ports having a first QCL relationship (e.g., indicated by the first TCI state) for the first TRP 605, and the second DCI (e.g., transmitted by the second TRP 605) can be scheduled to communicate with the second PDSCH associated with a second set of DMRS ports having a second QCL relationship (e.g., indicated by the second TCI state) for the second TRP 605. In this case, (for example, a DCI with DCI format 1_0 or DCI format 1_1) can indicate the corresponding TCI state for TRP 605 corresponding to that DCI. The TCI field of the DCI indicates the corresponding TCI state (for example, the TCI field of the first DCI indicates the first TCI state and the TCI field of the second DCI indicates the second TCI state).

[0115] In some respects, TRP A and TRP B may be part of the same cell (such as the same serving cell or the same target cell). Alternatively, in some respects, TRP A and TRP B may be associated with different cells (e.g., one cell is associated with the serving cell, and the other with the target cell). In some respects, TRP A and TRP B may be associated with the same network node. Alternatively, in some respects, TRP A and TRP B may be associated with different network nodes.

[0116] As indicated above, Figure 6 This is provided as an example. Other examples are available relative to... Figure 6 The descriptions are different.

[0117] Figure 7 This is an illustration of example 700 of using beaming for communication between a network node and a UE according to this disclosure. Figure 7 As shown, network node 110 and UE 120 can communicate with each other.

[0118] Network node 110 can transmit to UE 120 located within its coverage area. Network node 110 and UE 120 can be configured for beamforming communication, wherein network node 110 can use a directional network node (NN) transmit beam (e.g., network node 110 transmits a beam) in the direction of UE 120, and UE 120 can use a directional UE receive beam to receive the transmission. Each NN transmit beam may have an associated beam ID, beam direction, or beam symbol, etc. Network node 110 can transmit downlink communication via one or more NN transmit beams 705.

[0119] UE 120 may attempt to receive downlink transmissions via one or more UE receive beams 710, which may be configured at the UE 120's receive circuitry using different beamforming parameters. UE 120 may identify specific NN transmit beams 705 (shown as NN transmit beam 705-A) and specific UE receive beams 710 (shown as UE receive beam 710-A) that provide relatively good performance (e.g., optimal channel quality with different combinations of measurements of NN transmit beam 705 and UE receive beam 710). In some examples, UE 120 may send an indication of which NN transmit beam 705 UE 120 identifies as the preferred NN transmit beam, which network node 110 may select to transmit to UE 120. Therefore, UE 120 can obtain and maintain a beam-to-link (BPL) with network node 110 for downlink communication (e.g., a combination of NN transmit beam 705-A and UE receive beam 710-A), which can be further refined and maintained according to one or more established beam refinement procedures.

[0120] Downlink beams (such as NN transmit beam 705 or UE receive beam 710) may be associated with a TCI state. The TCI state may indicate the directivity or characteristics of the downlink beam, such as one or more QCL characteristics of the downlink beam. QCL attributes may include, for example, Doppler shift, Doppler spread, average delay, delay spread, or spatial reception parameters. In some examples, each NN transmit beam 705 may be associated with a Synchronization Signal Block (SSB), and UE 120 may indicate a preferred NN transmit beam 705 by transmitting an uplink transmit in the resource of the SSB associated with the preferred NN transmit beam 705. A particular SSB may have an associated TCI state (e.g., for antenna port or for beamforming). In some examples, network node 110 may indicate the downlink NN transmit beam 705 at least in part based on antenna port QCL attributes that can be indicated by the TCI state. For different QCL types (e.g., QCL types for different combinations of Doppler shift, Doppler spread, average delay, delay spread, or spatial reception parameters), the TCI state can be associated with a set of downlink reference signals (e.g., SSB, and aperiodic, periodic, or semi-persistent channel state information reference signals (CSI-RS)). In the case where the QCL type indicates spatial reception parameters, the QCL type can correspond to the analog receive beamforming parameters of the UE receive beam 710 at UE 120. Therefore, UE 120 can select the corresponding UE receive beam 710 from the BPL set, at least in part, based on the network node 110 instructing the NN transmit beam 705 via the TCI indication.

[0121] Network node 110 may maintain a set of active TCI states for downlink shared channel transmission and a set of active TCI states for downlink control channel transmission. The set of active TCI states for downlink shared channel transmission may correspond to the beams used by network node 110 for downlink transmission on the PDSCH. The set of active TCI states for downlink control channel communication may correspond to the beams that network node 110 can use for downlink transmission on the PDCCH or in the control resource set (CORESET). UE 120 may also maintain this set of active TCI states for receiving downlink shared channel transmission and CORESET transmission. When TCI states are activated for UE 120, UE 120 may have one or more antenna configurations at least partially based on the TCI states, and UE 120 may not need to reconfigure antennas or antenna weighting configurations. In some examples, the set of active TCI states for UE 120 (e.g., active PDSCH TCI states and active CORESET TCI states) may be configured by configuration messages (such as RRC messages).

[0122] Similarly, for uplink communication, UE 120 can use a directional UE transmit beam to transmit in the direction of network node 110, and network node 110 can use a directional NN receive beam to receive the transmission. Each UE transmit beam may have an associated beam ID, beam direction, or beam symbol, etc. UE 120 can transmit uplink communication via one or more UE transmit beams 715.

[0123] Network node 110 can receive uplink transmissions via one or more NN receive beams 720 (e.g., BS receive beams). Network node 110 can identify specific UE transmit beams 715 (shown as UE transmit beam 715-A) and specific NN receive beams 720 (shown as NN receive beam 720-A) that provide relatively good performance (e.g., optimal channel quality for different combinations of UE transmit beams 715 and NN receive beams 720). In some examples, network node 110 can send an indication of which UE transmit beam 715 network node 110 identifies as the preferred UE transmit beam, which network node 110 can select for transmission from UE 120. Therefore, UE 120 and network node 110 can obtain and maintain a BPL (e.g., a combination of UE transmit beam 715-A and NN receive beam 720-A) for uplink communication, which can be further refined and maintained according to one or more established beam refinement procedures. Uplink beams (such as UE transmit beam 715 or NN receive beam 720) can be associated with spatial relationships. Spatial relationships can indicate the directionality or characteristics of the uplink beam (similar to one or more QCL attributes), as described above.

[0124] The following text is relative to Figure 9 In more detail, UE 120 can be configured with multiple TCI states for STxMP communication. In some respects, UE 120 can receive configurations for STxMP communication under a unified TCI framework.

[0125] As indicated above, Figure 7 This is provided as an example. Other examples are available relative to... Figure 7 The descriptions are different.

[0126] Figure 8 This is a diagram of example 800 associated with configuring a UE for the LTM procedure, according to this disclosure. Figure 8 As shown, network nodes (e.g., network nodes 110, CU, DU, and / or RU) can communicate with a UE (e.g., UE 120). In some aspects, the network nodes and UEs can be part of a wireless network (e.g., wireless network 100). The UE and network nodes can... Figure 8The operation shown has been performed after a wireless connection has been established. In some respects, Figure 8 The communication shown in Example 800 can be Figure 4 This occurs during the LTM preparation section of Example 400. In some respects, see below. Figure 8 Some of the communications discussed in Example 800 are related to those mentioned above. Figure 4 Example 400 discusses some communication overlaps.

[0127] As shown by reference numeral 805 in the attached figure, the network node can send and the UE can receive configuration information. In some aspects, the UE can receive configuration information via one or more of the following: system information (e.g., Master Information Block (MIB) and / or System Information Block (SIB), RRC signaling, one or more MAC-CE communications and / or DCI.

[0128] In some aspects, the configuration information may indicate one or more candidate configuration and / or communication parameters. In some aspects, these one or more candidate configuration and / or communication parameters may be selected, activated, and / or deactivated by subsequent indications. For example, a subsequent indication may select a candidate configuration and / or communication parameter from the one or more candidate configuration and / or communication parameters. In some aspects, subsequent indications (e.g., the indications described herein) may include dynamic indications, such as waiting for one or more MAC-CE messages and / or one or more DCI messages.

[0129] In some aspects, configuration information can instruct the UE to send capability indications associated with LTM capabilities in accordance with MAC-CE-based cell handover operations. In other aspects, configuration information can instruct the UE to receive configurations based on capability indications. LTM capabilities may include granular "types." Granularity can be indicated by UE, by frequency band, by combination of frequency bands, by feature set, by feature set per carrier component (FSCP), and / or combinations thereof. LTM capabilities can also be associated with Frequency Division Duplex (FDD) operations, Time Division Duplex (TDD) operations, FR1 and / or FR2 differentiation, and / or combinations thereof.

[0130] In some respects, LTM capabilities can indicate support for MAC-CE-based cell handover operations based on whether one of the LTM candidate cells is the UE's current serving cell. For example, LTM capabilities can indicate support for RACH-based TA acquisition of an LTM candidate cell used as the serving cell. In some respects, the UE can support a certain number of (i.e., ...) cell handover operations based on a contention-free random access (CFRA) procedure according to the PDCCH command before receiving a MAC-CE-based cell handover command. NThe TA (Transmission Acquisition) of candidate cells can be obtained. In some aspects, PDCCH commands can be received from the current non-candidate serving cell or from an LTM candidate cell operating as the UE's serving cell. In some aspects, the UE can support power ramping for PRACH retransmission based on the PDCCH command indication. In some aspects, the UE can support handling the overlap between uplink transmissions on the serving cell and PRACH communications on an LTM candidate cell acting as the current serving cell.

[0131] In some aspects, LTM capability may indicate support for one or more of the following: synchronous inter-frequency L1 RSRP measurement, synchronous intra-frequency L1 RSRP measurement, asynchronous inter-frequency L1 RSRP measurement, or asynchronous intra-frequency L1 RSRP measurement. In some aspects, each L1 RSRP measurement may be based on the SSB associated with one of the LTM candidate cells, including whether the LTM candidate cell is currently operating as the UE's serving cell.

[0132] In some aspects, LTM capability can instruct the UE to support a maximum number of LTM candidate cells for performing L1-RSRP measurements to generate periodic reports, activated semi-persistent reports, or triggered aperiodic reports. In some aspects, the maximum number of LTM candidate cells excludes LTM candidate cells that are serving cells of the UE. Alternatively, the UE can support including all LTM candidate cells (whether or not they are serving cells) in the maximum number of LTM candidate cells. In some aspects, the maximum number of LTM candidate cells includes LTM candidate cells configured via RRC signaling.

[0133] In some respects, LTM capability can indicate UE support for LTM in the absence of RACH communication. For example, the UE can support intra-frequency and / or intra-frequency handover without RACH for LTM. In some respects, the UE can indicate support for a maximum number of LTM candidate cells that support intra-frequency and / or inter-frequency handover without RACH (which may exclude LTM candidate cells that are not currently operating as serving cells).

[0134] The UE can configure itself, at least in part, based on configuration information. In some respects, the UE can be configured to perform one or more of the operations described herein, at least in part, based on configuration information.

[0135] As shown by reference numeral 810 in the attached figure, the UE can send and the network node can receive a capability report. The capability report can indicate whether the UE supports a feature and / or one or more parameters associated with that feature. For example, capability information can indicate capabilities and / or parameters for MAC-CE-based cell handover operations in the context of LTM. One or more operations described herein can be based on the capability information in the capability report. For example, the UE can perform communication based on the capability information, or can receive configuration information based on the capability information. In some aspects, the capability report can indicate the UE's support for sending capability indications associated with LTM capabilities based on MAC-CE cell handover operations.

[0136] In some aspects, the configuration information and / or capability report described in conjunction with reference to reference numeral 805 may include information transmitted via multiple communications. Additionally or alternatively, the network node may transmit the configuration information or communications including at least a portion of the configuration information before and / or after the UE transmits the capability report. For example, the network node may transmit a first portion of the configuration information before the capability report, the UE may transmit at least a portion of the capability report, and the network node may transmit a second portion of the configuration information after receiving the capability report.

[0137] As shown by reference numeral 815 in the attached figure, the UE can receive and the network node can send an indication associated with a configuration for operating according to a MAC-CE-based cell handover operation for LTM. In some aspects, the indication can be included in the message transmission associated with the LTM procedure. For example, the indication can be an RRC reconfiguration message, such as the one referenced above. Figure 4 The RRC reconfiguration message discussed is referenced to figure 420. The RRC reconfiguration message may indicate the configuration of one or more LTM candidate target cells, which may be candidate cells to become the serving cell of the UE and / or cells to which the UE120 may later be triggered to perform an LTM procedure. Alternatively, in some aspects, the indication may be included in the cell handover command, such as those mentioned above relative to… Figure 4 The cell handover command discussed in Figure 445.

[0138] As shown by reference numeral 820, the UE can configure itself, at least in part, to perform an LTM procedure in accordance with a MAC-CE-based cell handover operation, based on receiving an instruction described in conjunction with reference numeral 815.

[0139] As shown by reference numeral 825 in the attached figure, the UE can communicate with network nodes, at least in part, based on 815, to facilitate the LTM process. For example, the UE can be configured to receive a MAC-CE-based cell handover command that includes a TA indication for the LTM candidate cell. In some aspects, the TA indication can indicate the presence or absence of the TA field in the cell handover command.

[0140] In some aspects, such as when a UE is configured to perform TA measurements via RRC, for example, the TA indication may include a first and a second bit. The first bit may indicate the presence or absence of the TA field, and the second bit may indicate a UE action. Examples of UE actions may include performing a TA measurement, applying the actual (i.e., measured) TA to an LTM candidate cell, applying zero TA to an LTM candidate cell, applying a previous TA to an LTM candidate cell, or sending RACH or PRACH communication to an LTM candidate cell. UE actions may further or alternatively include deriving the target cell TA based on the TA measurement. The TA measurement may be derived from the TA associated with the current source cell and the reference signal time difference (RSTD) between the source cell and one or more LTM candidate cells.

[0141] In some aspects, the TA indication may include a single bit indicating the presence or absence of the TA field in the cell handover command. In some aspects, if a single bit indicates the presence of TA, the UE may be configured to apply a TA value, i.e., the actual TA, zero TA, or the previous TA. If a single bit indicates the absence of TA, the UE may be configured to determine TA based on a triggered PRACH procedure or by measuring TA if, for example, a PRACH procedure is not triggered.

[0142] In some respects, such as when the UE is not configured to perform TA measurements, a single bit can indicate the actual TA value or the previous TA value. If a single bit is not present (e.g., indicating that the TA field is not present in a cell handover command), the UE can be configured to measure TA according to a triggered PRACH procedure.

[0143] In some respects, in addition to the TA (Translation Acquisition) indication, the cell handover command may also include a beam indication. The TA and beam indications can be represented by two bits in the cell handover command. The first bit indicates whether the TA field exists, and the second bit indicates whether the beam field exists.

[0144] As indicated above, Figure 8 This is provided as an example. Other examples are available relative to... Figure 8 The examples described are different.

[0145] Figure 9 This is a diagram of Example 900 associated with STxMP operations under the Unified TCI framework, based on this disclosure. Figure 9 As shown, network nodes (e.g., network nodes 110, CU, DU, and / or RU) can communicate with a UE (e.g., UE 120). In some aspects, the network nodes and UEs can be part of a wireless network (e.g., wireless network 100). The UE and network nodes can... Figure 9The operation shown has been performed with a wireless connection already established.

[0146] As shown by reference numeral 905 in the attached figure, a network node can send configuration information, and a UE can receive this configuration information. In some aspects, the UE can receive the configuration information via one or more of the following: system information (e.g., MIB and / or SIB), RRC signaling, one or more MAC-CEs and / or DCIs.

[0147] In some aspects, the configuration information may indicate one or more candidate configuration and / or communication parameters. In some aspects, these one or more candidate configuration and / or communication parameters may be selected, activated, and / or deactivated by subsequent indications. For example, a subsequent indication may select a candidate configuration and / or communication parameter from the one or more candidate configuration and / or communication parameters. In some aspects, subsequent indications (e.g., the indications described herein) may include dynamic indications, such as one or more MAC CEs and / or one or more DCI messages, etc.

[0148] In some respects, configuration information can instruct the UE to perform STxMP operations under the unified TCI framework. The UE can configure itself, at least in part, based on the configuration information. In some respects, the UE can be configured to perform one or more operations described herein, at least in part, based on the configuration information.

[0149] As shown by reference numeral 910 in the attached figure, the UE can send and the network node can receive a capability report. The capability report can indicate whether the UE supports a feature and / or one or more parameters associated with that feature. For example, capability information can indicate capabilities and / or parameters for STxMP communication under the unified TCI framework. One or more operations described herein can be based on the capability information in the capability report. For example, the UE can perform communication based on the capability information, or can receive configuration information based on the capability information. In some aspects, the capability report can indicate the UE's support for sending TCI capabilities associated with the unified TCI framework for STxMP communication. The capability report can also include the UE's support for receiving TCI configuration based on TCI capabilities. TCI configuration can configure the UE to apply one or more of two or more TCI states when, for example, the UE has received indications for multiple (e.g., two or more) TCI states.

[0150] In some aspects, the configuration information and / or capability report described in conjunction with reference to reference numeral 905 may include information transmitted via multiple communications. Additionally or alternatively, the network node may transmit the configuration information or communications including at least a portion of the configuration information before and / or after the UE transmits the capability report. For example, the network node may transmit a first portion of the configuration information before the capability report, the UE may transmit at least a portion of the capability report, and the network node may transmit a second portion of the configuration information after receiving the capability report.

[0151] As shown by reference numeral 915 in the attached figure, the UE can receive and the network node can send instructions for configuring STxMP communication under the unified TCI framework. For example, multiple TCI states in the unified TCI framework can be defined via RRC message reception. In some aspects, the activation and / or deactivation of one or more TCI states can be indicated for different channels via RRC message reception or DCI.

[0152] As shown by reference numeral 920, the UE can configure itself, at least in part, to receive TCI configuration according to TCI capabilities based on received instructions described in conjunction with reference numeral 915, as discussed above. In some aspects, TCI configuration can refer to the configuration of a unified TCI framework for mTRP operation based on an auxiliary DCI (sDCI) associated with mTRP in a single-frequency network (SFN) or coordinated joint transmission (CJT). TCI configuration can be applied to PDCCH and / or PDSCH reception in type 0 / 0A / 2 CSS of a CORESET (e.g., CORESET0). In some aspects, the UE can apply one TCI state (e.g., the first indicated TCI state) from among multiple TCI states indicated for PDSCH / PDCCH that is not associated with type 0 / 0A / 2 CSS to PDCCH and / or PDSCH reception in type 0 / 0A / 2 CSS of a CORESET (e.g., CORESET0). In some aspects, TCI configuration can configure the UE to apply multiple TCIs based on the configuration received by the SFN PDCCH. In some aspects, the UE can apply the QCL of the associated SSB, such as the QCL determined from previous contention-based random access (CBRA) PRACH communications. In some aspects, the UE can apply the TCI state indicated by a TCI activation signal received via MAC-CE (in the case of PDCCH reception) or by the TCI used for scheduling DCI (in the case of PDSCH reception) to PDSCH reception in type 0 / 0A / 2 CSS of CORESET (e.g., CORESET0). In some aspects, TCI configuration can configure the UE to apply the TCI state according to UE capabilities.

[0153] In some respects, TCI configuration can configure the UE to transmit Power Headroom (PHR) reports. This is useful when the UE is configured for multiple PHR modes (e.g., twoPHRMode In cases involving two sets of sounding reference signals (SRS) resources for codebook and / or non-codebook multi-panel schemes used for spatial division multiplexing (SDM) or SFN operation, TCI configuration may include configuration for PHR reporting. In some aspects, PHR reporting may indicate one or more of the PHR and maximum output power associated with one or more of two or more TCI states. TCI configuration may configure the UE to determine the PHR based on a reference Physical Uplink Shared Channel (PUSCH) transmission. If the actual PUSCH transmission is applied only to the first indicated joint / uplink TCI state, the UE may be configured to provide a first PHR report (e.g., PHR and configured maximum output power) associated with the first indicated joint / uplink TCI state used for the actual PUSCH transmission. In some aspects, the UE may be configured to apply a second PHR report associated with a second indicated joint / UL TCI state to the reference PUSCH transmission report (e.g., virtual PHR and configured maximum output power). In some respects, if the actual PUSCH transmission applies only to the second indicated joint / UL TCI state, the UE can be configured to provide a first PHR report associated with the second indicated joint / UL TCI state used for the actual PUSCH transmission and a second PHR report associated with the first indicated joint / UL TCI state used for the reference PUSCH transmission (e.g., virtual PHR and configured maximum output power). If the UE determines that multiple Type 1 PHRs are transmitted based on a reference PUSCH, the UE can be configured to provide a first PHR report associated with the first indicated joint / UL TCI state used for the reference PUSCH transmission (e.g., virtual PHR and configured maximum output power) and a second PHR report associated with the second indicated joint / UL TCI state used for another reference PUSCH transmission (e.g., virtual PHR and configured maximum output power). For example, for PHR reporting, the UE can report both per-panel power headroom and the configured maximum output power per panel based on the reference PUSCH transmission used for SDM or SFN timing in multi-TRP operations. In some respects, for PHR reports during SDM or SFN timing of multi-TRP operations, the UE can report two MPE fields of the applied power backoff for both panels to meet the MPE requirements, regardless of whether the PUSCH transmission is actual or virtual.

[0154] In some respects, the UE can trigger PHR reports via per-panel trigger events. For multi-TRP operations based on a unified TCI, if the UE is configured with two SRS resource sets for CB / NCB, the UE can support per-TRP path loss change monitoring for event-triggered PHRs, wherein the path loss reference used to determine the path loss change of a serving cell at different times is derived from a joint or UL TCI state used as a first indicated TCI state or a second indicated TCI state, and the path loss reference can be changed based on a TCI state update for the first indicated TCI state or the second indicated TCI state.

[0155] In some aspects, such as when the configured maximum output power is not reported via a virtual PHR report and the UE determines a Type 1 PHR based on a reference PUSCH transmission, the TCI configuration can configure the UE to transmit a PHR report based on the actual PUSCH transmission. In this case, the PHR report may include only the PHR and omit the configured maximum output power. In some aspects, if the actual PUSCH transmission applies only to a first indicated joint / uplink TCI state, the UE can provide a first PHR report associated with the first indicated joint / uplink TCI state used for the actual PUSCH transmission and a second PHR report associated with a second indicated joint / uplink TCI state used for the reference PUSCH transmission. If the actual PUSCH transmission applies only to a second indicated joint / uplink TCI state, the UE can be configured to provide a first PHR report associated with the second indicated joint / uplink TCI state used for the actual PUSCH transmission and a second PHR report associated with the first indicated joint / uplink TCI state used for the reference PUSCH transmission. Alternatively, if the UE determines that both Type 1 PHRs are transmitted based on a reference PUSCH, the UE can be configured to provide a first PHR report associated with a first indicated joint / uplink TCI state used for transmission on the reference PUSCH and a second PHR report associated with a second indicated joint / uplink TCI state used for transmission on the other reference PUSCH. In some aspects, the network node may not be aware of the maximum power enhancement (MPE) of the virtual PHR report. In some aspects, the virtual PHR report can be generated and / or transmitted based on the UE's capabilities.

[0156] In some aspects, TCI configuration can configure the UE to switch from a single TRP (sTRP) to an mTRP based on MAC-CE signaling. In some aspects, TCI configuration can configure the UE to send PHR reports for each TRP or for each cell. In some aspects, if multiple PHR modes are configured and two SRS resource sets for SDM / SFN codebook / non-codebook and multi-panel schemes are configured for the Bandwidth Part (BWP) or Component Carrier (CC), TCI configuration can configure the UE to send PHR reports for each TRP. In some aspects, when BWP / CC is configured and mTRP operation is enabled, the UE can be configured to generate and send PHR reports per TRP. In some aspects, if the UE is enabled for sTRP operation for BWP / CC via, for example, MAC-CE signaling, the UE can be configured to generate and send PHR reports per cell.

[0157] As shown by reference numeral 925 in the attached figure, according to the TCI configuration, the UE can communicate with network nodes at least partially based on 915. In doing so, the UE and network nodes can facilitate STxMP communication under the unified TCI framework.

[0158] As indicated above, Figure 9 This is provided as an example. Other examples are available relative to... Figure 9 The descriptions are different.

[0159] Figure 10 This is a diagram illustrating an example process 1000 performed, for example, at a UE or a device of a UE, according to this disclosure. Example process 1000 is an example in which a device or UE (e.g., UE 120) performs operations associated with UE capabilities for LTM.

[0160] like Figure 10 As shown, in some aspects, process 1000 may include sending a capability indication associated with LTM capability based on MAC-CE cell handover operations (box 1010). For example, the UE (e.g., using...) Figure 14 The transmitting component 1404 and / or the communication manager 1406 depicted herein may transmit capability indications associated with LTM capabilities, as described above, in accordance with MAC-CE cell handover operations.

[0161] like Figure 10 As further shown, in some aspects, process 1000 may include receiving configuration based on a capability indication (block 1020). For example, the UE (e.g., using...) Figure 14 The receiving component 1402 and / or communication manager 1406 depicted herein may receive configurations according to capability indications, as described above.

[0162] Process 1000 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.

[0163] In a first aspect, process 1000 includes receiving a cell handover command including a TA indication for an LTM candidate cell, wherein the TA indication indicates the presence or absence of a TA field in the cell handover command.

[0164] In the second aspect, either alone or in combination with the first aspect, the TA indication includes a first bit and a second bit, wherein the first bit indicates the presence or absence of the TA field, and the second bit indicates the UE action.

[0165] In the third aspect, either alone or in combination with one or more of the first and second aspects, the UE action includes one of the following: performing a TA measurement, applying zero TA to an LTM candidate cell, or sending RACH communication to an LTM candidate cell.

[0166] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, the TA indication includes a single bit indicating the presence or absence of the TA field.

[0167] In the fifth aspect, the TA value is associated with the RACH process, either alone or in combination with one or more of the first to fourth aspects.

[0168] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the cell handover command includes a first bit associated with the TA field and a second bit associated with the beam field.

[0169] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the first bit indicates the presence or absence of the TA field, and the second bit indicates the presence or absence of the beam field.

[0170] In the eighth aspect, either alone or in combination with one or more of the first to seventh aspects, the LTM capability indicates support for MAC-CE-based cell handover operations based on whether one of the LTM candidate cells is the UE's current serving cell.

[0171] In the ninth aspect, alone or in combination with one or more of the first to eighth aspects, the LTM capability includes a TA acquisition indication associated with a certain number of LTM candidate cells used in the CFRA procedure.

[0172] In the tenth aspect, either alone or in combination with one or more of the first to ninth aspects, the LTM capability indication supports one or more of the following: synchronous inter-frequency L1 RSRP measurement, synchronous intra-frequency L1 RSRP measurement, asynchronous inter-frequency L1 RSRP measurement, or asynchronous intra-frequency L1 RSRP measurement, and wherein each of the L1 RSRP measurements is based on an SSB associated with one of the LTM candidate cells.

[0173] In the eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the LTM capability indicates the maximum number of LTM candidate cells to be measured against one or more of periodic reports, active semi-persistent reports, or triggered non-periodic reports.

[0174] In the twelfth aspect, either alone or in combination with one or more of the first to eleventh aspects, the maximum number of LTM candidate cells are excluded as LTM candidate cells serving the UE.

[0175] In the thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, the maximum number of LTM candidate cells includes LTM candidate cells configured via RRC signaling.

[0176] In the fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, LTM capability indicates support for LTM in the absence of RACH communication.

[0177] although Figure 10 An example box for process 1000 is shown, but in some respects, it differs from... Figure 10 Compared to the boxes depicted, process 1000 may include additional boxes, fewer boxes, different boxes, or boxes arranged in a different manner. Additionally or alternatively, two or more boxes in process 1000 may be executed in parallel.

[0178] Figure 11 This is a diagram illustrating an example process 1100 performed, for example, at a UE or a device of a UE, according to this disclosure. Example process 1100 is an example in which a device or UE (e.g., UE 120) performs operations associated with UE capabilities for STxMP communication under the Unified TCI framework.

[0179] like Figure 11 As shown, in some aspects, process 1100 may include transmitting TCI capabilities associated with the unified TCI framework used for STxMP communication (box 1110). For example, the UE (e.g., using...) Figure 14The transmitting component 1404 and / or communication manager 1406 depicted can transmit TCI capabilities associated with the unified TCI framework for STxMP communication, as described above.

[0180] like Figure 11 As further shown, in some aspects, process 1100 may include receiving a TCI configuration based on TCI capabilities, wherein the TCI configuration is used to apply one or more TCI states of two or more TCI states (box 1120). For example, the UE (e.g., using...) Figure 14 The receiving component 1402 and / or communication manager 1406 depicted herein may receive a TCI configuration based on the TCI capability, wherein the TCI configuration is used to apply one or more of two or more TCI states, as described above.

[0181] Process 1100 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.

[0182] In a first aspect, process 1100 includes receiving one or more indications for two or more TCI states.

[0183] In the second aspect, either alone or in combination with the first aspect, each of two or more TCI states is applied to one or more of the PDSCH or PDCCH communications.

[0184] In a third aspect, either alone or in combination with one or more of the first and second aspects, process 1100 includes sending a PHR report according to the TCI configuration.

[0185] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, the PHR report indicates one or more of the PHR or maximum output power associated with one or more of the two or more TCI states.

[0186] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, one or more of the PHR or maximum output power are associated with the reference PUSCH transmission.

[0187] In the sixth aspect, the PHR report is associated with one or more of the BWP or CC, either alone or in combination with one or more of the first through fifth aspects.

[0188] although Figure 11 An example box for process 1100 is shown, but in some respects, it differs from... Figure 11Compared to the boxes depicted, process 1100 may include additional boxes, fewer boxes, different boxes, or boxes arranged in a different manner. Additionally or alternatively, two or more boxes in process 1100 may be executed in parallel.

[0189] Figure 12 This is a diagram illustrating an example process 1200 performed, for example, at a network node or a device of a network node, according to this disclosure. Example process 1200 is an example in which a device or network node (e.g., network node 110) performs operations associated with UE capabilities for LTM.

[0190] like Figure 12 As shown, in some aspects, process 1200 may include receiving from the UE a capability indication associated with LTM capabilities related to MAC-CE cell handover operations (box 1210). For example, a network node (e.g., using...) Figure 15 The receiving component 1502 and / or the communication manager 1506 depicted in the text can receive capability indications associated with LTM capabilities related to MAC-CE cell handover operations from the UE, as described above.

[0191] like Figure 12 As further shown, in some aspects, process 1200 may include sending configuration based on capability indications (box 1220). For example, network nodes (e.g., using...) Figure 15 The sending component 1504 and / or communication manager 1506 depicted herein may send configurations according to capability indications, as described above.

[0192] Process 1200 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.

[0193] In a first aspect, process 1200 includes sending a cell handover command including a TA indication for an LTM candidate cell, wherein the TA indication indicates the presence or absence of a TA field in the cell handover command.

[0194] In the second aspect, either alone or in combination with the first aspect, the TA indication includes a first bit and a second bit, wherein the first bit indicates the presence or absence of the TA field, and the second bit indicates the UE action.

[0195] In the third aspect, either alone or in combination with one or more of the first and second aspects, the UE action includes one of the following: performing a TA measurement, applying zero TA to an LTM candidate cell, or sending RACH communication to an LTM candidate cell.

[0196] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, the TA indication includes a single bit indicating the presence or absence of the TA field.

[0197] In the fifth aspect, the TA value is associated with the RACH process, either alone or in combination with one or more of the first to fourth aspects.

[0198] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the cell handover command includes a first bit associated with the TA field and a second bit associated with the beam field.

[0199] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the first bit indicates the presence or absence of the TA field, and the second bit indicates the presence or absence of the beam field.

[0200] In the eighth aspect, either alone or in combination with one or more of the first to seventh aspects, the LTM capability indicates support for MAC-CE-based cell handover operations based on whether one of the LTM candidate cells is the UE's current serving cell.

[0201] In the ninth aspect, alone or in combination with one or more of the first to eighth aspects, the LTM capability includes a TA acquisition indication associated with a certain number of LTM candidate cells used in the CFRA procedure.

[0202] In the tenth aspect, either alone or in combination with one or more of the first to ninth aspects, the LTM capability indication supports one or more of the following: inter-frequency L1 RSRP measurement, synchronous intra-frequency L1 RSRP measurement, asynchronous inter-frequency L1 RSRP measurement, or asynchronous intra-frequency L1 RSRP measurement, wherein one or more of the L1 RSRP measurements are based on an SSB associated with one of the LTM candidate cells.

[0203] In the eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the LTM capability indicates the maximum number of LTM candidate cells to be measured against one or more of periodic reports, active semi-persistent reports, or triggered non-periodic reports.

[0204] In the twelfth aspect, either alone or in combination with one or more of the first to eleventh aspects, the maximum number of LTM candidate cells are excluded as LTM candidate cells serving the UE.

[0205] In the thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, the maximum number of LTM candidate cells includes LTM candidate cells configured via RRC signaling.

[0206] In the fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, LTM capability indicates support for LTM in the absence of RACH communication.

[0207] although Figure 12 An example box for process 1200 is shown, but in some respects, it differs from... Figure 12 Compared to the boxes depicted, process 1200 may include additional boxes, fewer boxes, different boxes, or boxes arranged in a different manner. Additionally or alternatively, two or more boxes in process 1200 may be executed in parallel.

[0208] Figure 13 This is a diagram illustrating an example process 1300 performed, for example, at a network node or a device of a network node, according to this disclosure. Example process 1300 is an example in which a device or network node (e.g., network node 110) performs operations associated with STxMP communication under the Unified TCI framework.

[0209] like Figure 13 As shown, in some aspects, process 1300 may include receiving TCI capabilities associated with a unified TCI framework for STxMP communication (box 1310). For example, network nodes (e.g., using...) Figure 15 The receiving component 1502 and / or communication manager 1506 depicted can receive TCI capabilities associated with the unified TCI framework for STxMP communication, as described above.

[0210] like Figure 13 As further shown, in some aspects, process 1300 may include sending a TCI configuration based on TCI capabilities, wherein the TCI configuration is used to apply one or more TCI states of two or more TCI states (box 1320). For example, a network node (e.g., using...) Figure 15 The transmitting component 1504 and / or the communication manager 1506 depicted herein may transmit a TCI configuration based on the TCI capability, wherein the TCI configuration is used to apply one or more of two or more TCI states, as described above.

[0211] Process 1300 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.

[0212] In the first aspect, process 1300 includes sending one or more indications for two or more TCI states.

[0213] In the second aspect, either alone or in combination with the first aspect, each of two or more TCI states is applied to one or more of the PDSCH or PDCCH communications.

[0214] In a third aspect, either alone or in combination with one or more of the first and second aspects, process 1300 includes receiving a PHR report according to the TCI configuration.

[0215] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, the PHR report indicates one or more of the PHR or maximum output power associated with one or more of the two or more TCI states.

[0216] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, one or more of the PHR or maximum output power are associated with the reference PUSCH transmission.

[0217] In the sixth aspect, the PHR report is associated with one or more of the BWP or CC, either alone or in combination with one or more of the first through fifth aspects.

[0218] although Figure 13 An example box for process 1300 is shown, but in some respects, it differs from... Figure 13 Compared to the boxes depicted, process 1300 may include additional boxes, fewer boxes, different boxes, or boxes arranged in a different manner. Additionally or alternatively, two or more boxes in process 1300 may be executed in parallel.

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

[0220] In some respects, device 1400 can be configured to perform the functions described herein. Figures 4 to 9One or more operations described herein. Additionally or alternatively, the apparatus 1400 may be configured to perform one or more processes described herein, such as Figure 10 Process 1000 Figure 11 Processes 1100 or combinations thereof. In some aspects, apparatus 1400 and / or Figure 14 One or more components shown may include combinations Figure 2 One or more components of the described UE. Additionally or alternatively, Figure 14 One or more components shown can be combined Figure 2 Implemented within one or more of the described components. Additionally or alternatively, one or more of the components in the group may be implemented at least partially as software stored in one or more memories. For example, a component (or a portion thereof) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the function or operation of the component.

[0221] Receiver 1402 may receive communications from device 1408, such as reference signals, control information, data communications, or combinations thereof. Receiver 1402 may provide the received communications to one or more other components of device 1400. In some aspects, receiver 1402 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 1400. In some aspects, receiver 1402 may include combinations of... Figure 2 The described UE includes one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receiver processors, one or more controllers / processors, one or more memories, or combinations thereof.

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

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

[0224] The transmitting component 1404 can transmit a capability indication associated with LTM capability based on MAC-CE cell handover operations. The receiving component 1402 can receive configuration based on the capability indication.

[0225] The receiving component 1402 can receive a cell handover command that includes a TA indication for an LTM candidate cell, wherein the TA indication indicates the presence or absence of the TA field in the cell handover command.

[0226] The transmitting component 1404 can transmit TCI capabilities associated with the unified TCI framework used for STxMP communication. The receiving component 1402 can receive TCI configurations based on the TCI capabilities, wherein the TCI configurations are used to apply one or more of two or more TCI states.

[0227] The receiving component 1402 can receive one or more indications for two or more TCI states. The transmitting component 1404 can send PHR reports according to the TCI configuration.

[0228] Figure 14 The number and arrangement of components shown are provided as an example. In reality, with... Figure 14 Compared to the components shown, there may be additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 14 The two or more components shown can be implemented within a single component, or Figure 14 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 14 The component collection (one or more components) shown can be executed as described by Figure 14 The other set of components shown performs one or more functions.

[0229] Figure 15 This is a diagram of an example device 1500 for wireless communication according to the present disclosure. Device 1500 may be a network node, or a network node may include device 1500. In some aspects, device 1500 includes a receiving component 1502, a transmitting component 1504, and / or a communication manager 1506 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 1506 is combined with... Figure 1 The described communication manager 150. As shown, device 1500 can communicate with another device 1508 (such as a UE or a network node (such as a CU, DU, RU or base station)) using receiving component 1502 and transmitting component 1504.

[0230] In some respects, device 1500 can be configured to perform the functions described herein. Figures 4 to 9 One or more operations described herein. Additionally or alternatively, the apparatus 1500 may be configured to perform one or more processes described herein, such as Figure 12 Process 1200 Figure 13 The process 1300 or a combination thereof. In some respects, Figure 15 The illustrated device 1500 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 15 One or more components shown can be combined Figure 2 Implemented within one or more of the described components. Additionally or alternatively, one or more of the components in the group may be implemented at least partially as software stored in one or more memories. For example, a component (or a portion thereof) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the function or operation of the component.

[0231] Receiver 1502 may receive communications from device 1508, such as reference signals, control information, data communications, or combinations thereof. Receiver 1502 may provide the received communications to one or more other components of device 1500. In some aspects, receiver 1502 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 1500. In some aspects, receiver 1502 may include combinations of... Figure 2The described network node may include one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receiver processors, one or more controllers / processors, one or more memories, or combinations thereof. In some aspects, receiver component 1502 and / or transmitter component 1504 may include or be included in a network interface. The network interface may be configured to acquire and / or output signals for device 1500 via one or more communication links, such as backhaul links, midhaul links, and / or fronthaul links.

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

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

[0234] The receiving component 1502 can receive a capability indication associated with the LTM capability related to the MAC-CE cell handover operation from the UE. The transmitting component 1504 can transmit configuration based on the capability indication.

[0235] The transmitting component 1504 can transmit a cell handover command that includes a TA indication for the LTM candidate cell, wherein the TA indication indicates the presence or absence of the TA field in the cell handover command.

[0236] The receiving component 1502 can receive TCI capabilities associated with the unified TCI framework used for STxMP communication. The transmitting component 1504 can transmit TCI configurations based on the TCI capabilities, wherein the TCI configurations are used to apply one or more of two or more TCI states.

[0237] The transmitting component 1504 can transmit one or more indications for two or more TCI states. The receiving component 1502 can receive PHR reports according to the TCI configuration.

[0238] Figure 15 The number and arrangement of components shown are provided as an example. In reality, with... Figure 15 Compared to the components shown, there may be additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 15 The two or more components shown can be implemented within a single component, or Figure 15 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 15 The component collection (one or more components) shown can be executed as described by Figure 15 The other set of components shown performs one or more functions.

[0239] The following provides an overview of some aspects of this disclosure: Aspect 1: A method for wireless communication performed by a UE, the method comprising: transmitting a capability indication associated with LTM capability according to a MAC-CE cell handover operation; and receiving configuration according to the capability indication.

[0240] Aspect 2: According to the method of aspect 1, the method further includes: receiving a cell handover command including a TA indication for an LTM candidate cell, wherein the TA indication indicates the presence or absence of a TA field in the cell handover command.

[0241] Aspect 3: According to the method of aspect 2, the TA indication includes a first bit and a second bit, wherein the first bit indicates the presence or absence of the TA field, and the second bit indicates UE action.

[0242] Aspect 4: According to the method of aspect 3, the UE action includes one of the following: performing a TA measurement, applying zero TA to the LTM candidate cell, or sending RACH communication to the LTM candidate cell.

[0243] Aspect 5: According to the method of aspect 2, wherein the TA indication includes a single bit indicating the presence or absence of the TA field.

[0244] Aspect 6: The method described in aspect 2, wherein the TA value is associated with the RACH process.

[0245] Aspect 7: According to the method of aspect 2, the cell handover command includes a first bit associated with the TA field and a second bit associated with the beam field.

[0246] Aspect 8: According to the method of aspect 7, wherein the first bit indicates the presence or absence of the TA field, and wherein the second bit indicates the presence or absence of the beam field.

[0247] Aspect 9: The method according to any one of Aspects 1 to 8, wherein the LTM capability indicates support for MAC-CE based cell handover operations based on whether one of the LTM candidate cells is the current serving cell of the UE.

[0248] Aspect 10: According to the method of aspect 9, the LTM capability includes a TA acquisition indication associated with a number of LTM candidate cells for the CFRA procedure.

[0249] Aspect 11: The method according to any one of Aspects 1 to 10, wherein the LTM capability indication supports one or more of the following: synchronous inter-frequency L1 RSRP measurement, synchronous intra-frequency L1 RSRP measurement, asynchronous inter-frequency L1 RSRP measurement, or asynchronous intra-frequency L1 RSRP measurement, and wherein each of the L1 RSRP measurements is based on an SSB associated with one of the LTM candidate cells.

[0250] Aspect 12: The method according to any one of Aspects 1 to 11, wherein the LTM capability indicates the maximum number of LTM candidate cells to be measured against one or more of periodic reports, active semi-persistent reports, or triggered non-periodic reports.

[0251] Aspect 13: According to the method of aspect 12, wherein the maximum number of LTM candidate cells excludes LTM candidate cells that serve as the UE's serving cell.

[0252] Aspect 14: According to the method of aspect 12, the maximum number of LTM candidate cells includes LTM candidate cells configured via RRC signaling.

[0253] Aspect 15: The method according to any one of Aspects 1 to 14, wherein the LTM capability indicates support for LTM in the absence of RACH communication.

[0254] Aspect 16: A method for wireless communication performed by a UE, the method comprising: transmitting a TCI capability associated with a unified TCI framework for STxMP communication; and receiving a TCI configuration based on the TCI capability, wherein the TCI configuration is for applying one or more of two or more TCI states.

[0255] Aspect 17: The method according to aspect 16 further includes receiving one or more indications for the two or more TCI states.

[0256] Aspect 18: The method according to any one of Aspects 16 to 17, wherein each of the two or more TCI states is applied to one or more of the PDSCH or PDCCH communications.

[0257] Aspect 19: The method according to any one of Aspects 16 to 18, the method further comprising: sending a PHR report according to the TCI configuration.

[0258] Aspect 20: The method according to aspect 19, wherein the PHR report indicates one or more of the PHR or maximum output power associated with one or more of the two or more TCI states.

[0259] Aspect 21: According to the method of aspect 20, one or more of the PHR or the maximum output power are associated with the reference PUSCH transmission.

[0260] Aspect 22: The method according to aspect 19, wherein the PHR report is associated with one or more of BWP or CC.

[0261] Aspect 23: A method for wireless communication performed by a network node, the method comprising: receiving from a UE a capability indication associated with an LTM capability related to a MAC-CE cell handover operation; and transmitting a configuration based on the capability indication.

[0262] Aspect 24: According to the method of aspect 23, the method further includes sending a cell handover command including a TA indication for an LTM candidate cell, wherein the TA indication indicates the presence or absence of a TA field in the cell handover command.

[0263] Aspect 25: According to the method of aspect 24, wherein the TA indication includes a first bit and a second bit, wherein the first bit indicates the presence or absence of the TA field, and the second bit indicates UE action.

[0264] Aspect 26: According to the method of aspect 25, the UE action includes one of the following: performing a TA measurement, applying zero TA to the LTM candidate cell, or sending RACH communication to the LTM candidate cell.

[0265] Aspect 27: The method according to aspect 24, wherein the TA indication includes a single bit indicating the presence or absence of the TA field.

[0266] Aspect 28: The method described in aspect 24, wherein the TA value is associated with the RACH process.

[0267] Aspect 29: According to the method of aspect 24, the cell handover command includes a first bit associated with the TA field and a second bit associated with the beam field.

[0268] Aspect 30: The method according to aspect 29, wherein the first bit indicates the presence or absence of the TA field, and wherein the second bit indicates the presence or absence of the beam field.

[0269] Aspect 31: The method according to any one of Aspects 23 to 30, wherein the LTM capability indicates support for MAC-CE based cell handover operation based on whether one of the LTM candidate cells is the current serving cell of the UE.

[0270] Aspect 32: According to the method of aspect 31, the LTM capability includes a TA acquisition indication associated with a number of LTM candidate cells for the CFRA procedure.

[0271] Aspect 33: The method according to any one of Aspects 23 to 32, wherein the LTM capability indication supports one or more of the following: synchronous inter-frequency L1 RSRP measurement, synchronous intra-frequency L1 RSRP measurement, asynchronous inter-frequency L1 RSRP measurement, or asynchronous intra-frequency L1 RSRP measurement, wherein the one or more of the L1 RSRP measurements are based on an SSB associated with one of the LTM candidate cells.

[0272] Aspect 34: The method according to any one of Aspects 23 to 33, wherein the LTM capability indicates the maximum number of LTM candidate cells to be measured against one or more of periodic reports, active semi-persistent reports, or triggered non-periodic reports.

[0273] Aspect 35: According to the method of aspect 34, wherein the maximum number of LTM candidate cells excludes LTM candidate cells that serve as the UE's serving cell.

[0274] Aspect 36: According to the method of aspect 34, the maximum number of LTM candidate cells includes LTM candidate cells configured via RRC signaling.

[0275] Aspect 37: The method according to any one of Aspects 23 to 36, wherein the LTM capability indicates support for LTM in the absence of RACH communication.

[0276] Aspect 38: A method for wireless communication performed by a network node, the method comprising: receiving a TCI capability associated with a unified TCI framework for STxMP communication; and transmitting a TCI configuration based on the TCI capability, wherein the TCI configuration is for applying one or more of two or more TCI states.

[0277] Aspect 39: The method according to aspect 38 further includes sending one or more indications for the two or more TCI states.

[0278] Aspect 40: The method according to any one of Aspects 38 to 39, wherein each of the two or more TCI states is applied to one or more of the PDSCH or PDCCH communications.

[0279] Aspect 41: The method according to any one of Aspects 38 to 40, the method further comprising: receiving a PHR report according to the TCI configuration.

[0280] Aspect 42: The method according to aspect 41, wherein the PHR report indicates one or more of the PHR or maximum output power associated with one or more of the two or more TCI states.

[0281] Aspect 43: According to the method of aspect 42, one or more of the PHR or the maximum output power are associated with the reference PUSCH transmission.

[0282] Aspect 44: The method according to aspect 41, wherein the PHR report is associated with one or more of BWP or CC.

[0283] Aspect 45: An apparatus for wireless communication at a device, the apparatus comprising: one or more processors; one or more memories coupled to the one or more processors; and instructions stored in the one or more memories and executable by the one or more processors to cause the apparatus to perform the method according to one or more of aspects 1 to 44.

[0284] Aspect 46: An apparatus for wireless communication at a device, the apparatus comprising one or more memories and one or more processors coupled to the one or more memories, the one or more processors being configured to cause the device to perform the method according to one or more of aspects 1 to 44.

[0285] Aspect 47: 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 44.

[0286] Aspect 48: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by one or more processors to perform the methods described in one or more of aspects 1 to 44.

[0287] Aspect 49: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions including, when executed by one or more processors of a device, causing the device to perform one or more of the methods described in one or more of aspects 1 to 44.

[0288] Aspect 50: A device for wireless communication, the device including a processing system comprising one or more processors and one or more memories coupled to the one or more processors, the processing system being configured to cause the device to perform the method according to one or more of aspects 1 to 44.

[0289] Aspect 51: An apparatus for wireless communication at a device, the apparatus comprising one or more memories and one or more processors coupled to the one or more memories, the one or more processors being individually or collectively configured to cause the device to perform the method according to one or more of aspects 1 to 44.

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

[0291] As used herein, the term "component" is intended to be interpreted broadly as hardware and / or a combination of hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other names, "software" should be interpreted broadly as meaning instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, and / or functions, etc. As used herein, a "processor" is implemented in hardware and / or a combination of hardware and software. It will be apparent to those skilled in the art that the systems and / or methods described herein can be implemented in various forms of hardware and / or combinations of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods is not limiting in any way. Therefore, no specific software code is referenced in this document to describe the operation and behavior of the systems and / or methods, as those skilled in the art will understand that the software and hardware can be designed, at least in part, based on the descriptions herein, to implement the systems and / or methods.

[0292] Hardware and data processing means for implementing the various exemplary logic units, logic blocks, modules, and circuits described herein can be implemented or executed using general-purpose single-chip or multi-chip processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic units, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor can be a microprocessor, or any conventional processor, controller, microcontroller, or state machine. A processor can also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration. In some aspects, specific processes and methods can be performed by circuitry dedicated to a given function.

[0293] 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.

[0294] Although specific combinations of features are set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features may be combined in ways not specifically set forth in the claims and / or not disclosed in the specification. The disclosure of various aspects includes each dependent claim in combination with each other claim in the set of claims. As used herein, the phrase referring to “at least one of” the list of items means 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, a+b, a+c, b+c, and a+b+c, as well as any combination having multiple identical elements (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c, and c+c+c, or any other ordering of a, b, and c).

[0295] 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 used interchangeably with “one or more.” Furthermore, as used herein, the article “the” is intended to include one or more items mentioned in connection with the article “the” and is used interchangeably with “one or more.” Furthermore, as used herein, the terms “group” and “cluster” are intended to include one or more items and are used interchangeably with “one or more.” If only one item is desired, the phrase “only one” or similar terminology will be used. Furthermore, as used herein, the terms “have,” “possess,” “have,” etc., are intended to be open-ended terms that do not limit the elements they modify (e.g., an element “having” A may also have B). Furthermore, the phrase “based on” is intended to mean “at least partially based on” unless otherwise explicitly stated. Furthermore, as used herein, the term “or” is intended to be inclusive when used in a series and is interchangeable with “and / or” unless otherwise explicitly stated (e.g., in the case of its use in conjunction with “any” or “only one”).

Claims

1. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: One or more memory units; and One or more processors, said one or more processors coupled to said one or more memories, said one or more processors being configured to cause the UE to: Based on the Media Access Control (MAC) Control Element (MAC-CE) cell handover operation, transmit capability indications associated with Layer 1 / Layer 2 triggered mobility (LTM) capabilities; and Receive configuration according to the capability indication.

2. The UE of claim 1, wherein the one or more processors are further configured to cause the UE to: Receive a cell handover command including a timing advance (TA) indication for an LTM candidate cell, wherein the TA indication indicates the presence or absence of a TA field in the cell handover command.

3. The UE according to claim 2, wherein the TA indication includes a first bit and a second bit, and The first bit indicates the presence or absence of the TA field, and the second bit indicates the UE action.

4. The UE according to claim 3, wherein the UE action includes one of the following: Perform TA measurement, Apply zero TA to the LTM candidate cells, or Send Random Access Channel (RACH) communication to the LTM candidate cell.

5. The UE of claim 2, wherein the TA indication includes a single bit indicating the presence or absence of the TA field.

6. The UE of claim 2, wherein the TA value is associated with the Random Access Channel (RACH) procedure.

7. The UE of claim 2, wherein the cell handover command includes a first bit associated with the TA field and a second bit associated with the beam field.

8. The UE of claim 7, wherein the first bit indicates the presence or absence of the TA field, and The second bit indicates the presence or absence of the beam field.

9. The UE of claim 1, wherein the LTM capability indicates support for the MAC-CE cell handover operation based on whether one or more LTM candidate cells are the current serving cell of the UE.

10. The UE of claim 9, wherein the LTM capability includes a TA acquisition indication associated with a number of LTM candidate cells for a contention-free random access (CFRA) procedure.

11. The UE of claim 1, wherein the LTM capability indication supports one or more of the following: synchronous inter-frequency layer 1 (L1) reference signal received power (RSRP) measurement, synchronous intra-frequency L1 RSRP measurement, asynchronous inter-frequency L1 RSRP measurement, or asynchronous intra-frequency L1 RSRP measurement, and Each L1 RSRP measurement in the L1 RSRP measurement is based on a synchronization signal block (SSB) associated with one of the LTM candidate cells.

12. The UE of claim 1, wherein the LTM capability indicates the maximum number of LTM candidate cells to be measured against one or more of periodic reports, active semi-persistent reports, or triggered aperiodic reports.

13. The UE of claim 12, wherein the maximum number of LTM candidate cells is excluded as an LTM candidate cell serving the UE.

14. The UE of claim 12, wherein the maximum number of LTM candidate cells includes LTM candidate cells configured via Radio Resource Control (RRC) signaling.

15. The UE of claim 1, wherein the LTM capability indicates support for LTM in the absence of random access channel (RACH) communication.

16. A UE for wireless communication, the UE comprising: One or more memory units; and One or more processors, said one or more processors coupled to said one or more memories, said one or more processors being configured to cause the UE to: Sending TCI capabilities associated with the Unified Transmission Configuration Indicator (TCI) framework for simultaneous transmission of multiple points (STxMP) communication; and Receive TCI configuration according to the TCI capability, wherein the TCI configuration is used to apply one or more TCI states of two or more TCI states.

17. The UE of claim 16, wherein the one or more processors are further configured to cause the UE to receive one or more indications for the two or more TCI states.

18. The UE of claim 16, wherein each of two or more TCI states applies to one or more of physical downlink shared channel (PDSCH) communications or physical downlink control channel (PDCCH) communications.

19. The UE of claim 16, wherein the one or more processors are further configured to cause the UE to: Send a Power Headroom (PHR) report according to the TCI configuration.

20. The UE of claim 19, wherein the PHR report indicates one or more of the PHR or maximum output power associated with one or more of the two or more TCI states.

21. The UE of claim 20, wherein one or more of the PHR or the maximum output power are associated with a reference physical uplink shared channel (PUSCH) transmission.

22. The UE of claim 19, wherein the PHR report is associated with one or more of a bandwidth portion (BWP) or a component carrier (CC).

23. A network node for wireless communication, the network node comprising: One or more memory units; and One or more processors, said one or more processors coupled to said one or more memories, said one or more processors being configured to cause the network node to: Receive capability indications from the User Equipment (UE) associated with Layer 1 / Layer 2 triggered mobility (LTM) capabilities related to cell handover operations involving Media Access Control (MAC) Control Elements (MAC-CE); and Send the configuration according to the capability indication.

24. The network node of claim 23, wherein the one or more processors are further configured to cause the network node to send a cell handover command including a timing advance (TA) indication for an LTM candidate cell, wherein the TA indication indicates the presence or absence of a TA field in the cell handover command.

25. The network node of claim 23, wherein the LTM capability indicates support for the MAC-CE cell handover operation based on whether one or more LTM candidate cells are the current serving cell of the UE.

26. The network node of claim 23, wherein the LTM capability indicates support for LTM in the absence of random access channel (RACH) communication.

27. A network node for wireless communication, the network node comprising: One or more memory units; and One or more processors, said one or more processors coupled to said one or more memories, said one or more processors being configured to cause the network node to: Receive TCI capabilities associated with the Unified Transmission Configuration Indicator (TCI) framework for simultaneous transmission of multiple points (STxMP) communication; and The TCI configuration is sent according to the TCI capability, wherein the TCI configuration is used to apply one or more of two or more TCI states.

28. The network node of claim 27, wherein the one or more processors are further configured to cause the network node to send one or more indications for the two or more TCI states.

29. The network node of claim 27, wherein each of two or more TCI states applies to one or more of Physical Downlink Shared Channel (PDSCH) communication or Physical Downlink Control Channel (PDCCH) communication.

30. The network node of claim 27, wherein the one or more processors are further configured to cause the network node to receive a power headroom (PHR) report according to the TCI configuration.

Images