Predicted radio link quality reports for lower layer triggered mobility

Abstract

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a user equipment (UE) can receive a configuration of one or more lower layer triggered mobility (LTM) candidate cells. The UE can transmit a report indicating one or more predicted radio link qualities associated with one or more LTM candidate cells and one or more future time windows based at least in part on one or more predicted radio link channel characteristics. Numerous other aspects are described.

Description

Technical Field

[0001] All aspects of this disclosure relate to wireless communications in general, and more particularly to techniques, apparatus, and methods for radio link quality reporting for predictions of lower layer triggered mobility (LTM). Background Technology

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

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

[0004] Some aspects described herein relate to an apparatus for wireless communication at a user equipment (UE). The apparatus may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or in any combination to enable the apparatus to receive configurations of one or more lower-layer triggered mobility (LTM) candidate cells. The one or more processors may be able to operate individually or in any combination to enable the apparatus to transmit reports indicating one or more predicted radio link qualities associated with the one or more LTM candidate cells and one or more future time windows, at least in part, based on one or more predicted radio link channel characteristics.

[0005] Some aspects described herein relate to an apparatus for wireless communication at a network node. The apparatus may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or in any combination to cause the apparatus to transmit configurations of one or more LTM candidate cells. The one or more processors may be able to operate individually or in any combination to cause the apparatus to receive reports indicating one or more predicted radio link qualities associated with the one or more LTM candidate cells and one or more future time windows, at least in part, based on one or more predicted radio link channel characteristics.

[0006] Some aspects described herein relate to a method for wireless communication performed by a UE. The method may include receiving a configuration of one or more LTM candidate cells. The method may include transmitting a report indicating one or more predicted radio link qualities associated with the one or more LTM candidate cells and one or more future time windows, based at least in part on one or more predicted radio link channel characteristics.

[0007] Some aspects described herein relate to a method for wireless communication performed by a network node. The method may include transmitting a configuration of one or more LTM candidate cells. The method may include receiving reports indicating one or more predicted radio link qualities associated with the one or more LTM candidate cells and one or more future time windows, based at least in part on one or more predicted radio link channel characteristics.

[0008] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a UE. When executed by one or more processors of the UE, the set of instructions enables the UE to receive configurations for one or more LTM candidate cells. When executed by one or more processors of the UE, the set of instructions enables the UE to transmit reports indicating one or more predicted radio link qualities associated with the one or more LTM candidate cells and one or more future time windows, based at least in part on one or more predicted radio link channel characteristics.

[0009] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a network node. When executed by one or more processors of the network node, the set of instructions enables the network node to transmit configurations of one or more LTM candidate cells. When executed by one or more processors of the network node, the set of instructions enables the network node to receive reports indicating one or more predicted radio link qualities associated with the one or more LTM candidate cells and one or more future time windows, based at least in part on one or more predicted radio link channel characteristics.

[0010] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for receiving configurations of one or more LTM candidate cells. The apparatus may also include components for transmitting, at least in part, a report indicating one or more predicted radio link qualities associated with the one or more LTM candidate cells and one or more future time windows, based on one or more predicted radio link channel characteristics.

[0011] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for transmitting configurations of one or more LTM candidate cells. The apparatus may also include components for receiving, at least in part, reports indicating one or more predicted radio link qualities associated with the one or more LTM candidate cells and one or more future time windows, based on one or more predicted radio link channel characteristics.

[0012] Various aspects of this disclosure may be implemented or be implemented as described in whole by or embodied in the methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network nodes, network entities, wireless communication devices and / or processing systems as fully described in the specification and drawings and illustrated in the specification and drawings.

[0013] The preceding paragraphs of this section have broadly summarized some aspects of this disclosure. These and additional aspects and their associated advantages will be described below. The disclosed aspects can serve as the basis for modifying or designing other aspects for performing the same or similar purposes of this disclosure. Such equivalent aspects do not depart from the scope of the appended claims. The characteristics of the aspects disclosed herein, their organization and operation, and their associated advantages will be better understood from the following description taken in conjunction with the accompanying drawings. Attached Figure Description

[0014] The accompanying drawings illustrate some aspects of this disclosure but do not limit its scope, as other aspects can be achieved by this description. Each drawing in the drawings is provided for illustrative and descriptive purposes and not as a definition of limitation of the claims. Identical or similar reference numerals in different drawings may identify identical or similar elements.

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

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

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

[0018] Figure 4 This is a diagram illustrating an example of a lower-level triggered mobility (LTM) process according to this disclosure.

[0019] Figure 5 This is a diagram illustrating an example of a radio link quality report associated with a prediction for LTM according to this disclosure.

[0020] Figure 6 This is a diagram illustrating an example of predictive radio link monitoring (RLM) in LTM according to this disclosure.

[0021] Figure 7 This is a diagram illustrating an example of a purely UE-based predictive RLM for LTM according to this disclosure.

[0022] Figure 8 This is an illustration of an example associated with an artificial intelligence or machine learning (AI / ML) framework for a purely UE-based predictive RLM for LTM, according to this disclosure.

[0023] Figure 9 This is a diagram illustrating an example of network-assisted predictive RLM for LTM according to this disclosure.

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

[0025] Figure 11 This 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.

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

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

[0028] Various aspects of this disclosure are described below with reference to the accompanying drawings. However, aspects of this disclosure may be embodied in many different forms and should not be construed as limited to any specific aspect illustrated or described with reference to the drawings or otherwise presented in this disclosure. Rather, these aspects are provided so that this disclosure will be comprehensive and complete, and will fully convey the scope of protection of this disclosure to those skilled in the art. Those skilled in the art will understand that the scope of this disclosure is intended to cover any aspect of this disclosure disclosed herein, whether implemented independently of or in combination with any other aspect of this disclosure. For example, various combinations or numbers of aspects set forth herein may be used to implement an apparatus or a practice. Furthermore, the scope of this disclosure is intended to cover apparatuses having structures and / or functionalities other than those available for practicing the various aspects of this disclosure set forth herein, or methods practiced using these other structures and / or functionalities. Any aspect of this disclosure disclosed herein may be embodied by one or more elements of the claims.

[0029] Various methods, operations, apparatuses, and techniques will now be presented with reference to them. These methods, operations, apparatuses, 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 may be implemented using hardware, software, or a combination of hardware and software. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole.

[0030] Multiple access radio access technology (RAT) has been adopted in various telecommunications standards to provide a common protocol that enables wireless communication devices to communicate at the city, enterprise, national, regional, or global level. For example, 5G New Radio (NR) is part of the continuous mobile broadband evolution announced by the 3rd Generation Partnership Project (3GPP). 5G NR supports a variety of technologies and use cases, including enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), massive machine-type communication (mMTC), millimeter wave (mmWave) technology, beamforming, network slicing, edge computing, Internet of Things (IoT) connectivity and management, and network function virtualization (NFV).

[0031] As the demand for broadband access increases and as the technologies supported by wireless communication networks evolve, further technological improvements can be adopted or implemented in 5G NR or future RATs (such as 6G) to further advance the evolution of wireless communication for a variety of existing and new use cases and applications. Such technological improvements can be associated with new frequency band extensions, licensed and unlicensed spectrum access, overlapping spectrum use, small cell deployments, non-terrestrial network (NTN) deployments, decomposed network architectures and network topology extensions, device aggregation, advanced duplex communication, sidelinks and other device-to-device direct communication, IoT (including passive or environmental IoT) networks, reduced-capacity (RedCap) user equipment (UE) functionality, industrial connectivity, multi-subscriber implementations, high-precision positioning, radio frequency (RF) sensing and / or artificial intelligence or machine learning (AI / ML), and more. These technological improvements can support use cases such as wireless backhaul, wireless data centers, extended reality (XR) and metaverse applications, meta-services for supporting vehicle connectivity, holographic and mixed reality communications, autonomous and collaborative robots, vehicle platooning and collaborative manipulation, sensor networks, posture monitoring, brain-computer interfaces, digital twin applications, asset management, and general coverage applications using off-ground and / or aerial platforms, among others. The methods, operations, apparatuses, and techniques described herein can implement one or more of the foregoing technologies and / or support one or more of the foregoing use cases.

[0032] In some examples, network nodes may instruct the UE to change serving cells, such as when the UE leaves the coverage area of ​​its current serving cell and moves toward the coverage area of ​​a neighboring cell. In some cases, network nodes may instruct the UE to change cells using a Layer 3 (L3) handover procedure. However, these handover procedures can be associated with high latency and high overhead due to the multiple Radio Resource Control (RRC) reconfiguration messages and / or other L3 signaling and operations used to perform them. Accordingly, in some examples, the UE may be configured to perform lower-layer (e.g., Layer 1 (L1) and / or Layer 2 (L2)) handover procedures, sometimes referred to as lower-layer triggered mobility (LTM) procedures. An LTM procedure may include four phases: an LTM preparation phase, an early synchronization phase, an LTM execution phase, and / or an LTM completion phase. Compared to L3 handover procedures, cell handover to a target cell using LTM can be performed with less overhead and / or latency.

[0033] However, due to the lack of robustness in Radio Link Detection (RLM) and Beam Failure Detection (BFD) in LTM, potential Radio Link Failures (RLFs) in the target cell cannot be adequately identified (e.g., due to impending obstruction). Therefore, the robustness of LTM can be reduced due to reactive RLM (and / or BFD) based solely on historical measurements. For example, a UE might experience an RLF in the target cell shortly after an LTM cell handover (e.g., within tens or hundreds of milliseconds). The UE can respond to the RLF by performing Radio Link Recovery or fallback to initial access, which can further degrade the robustness of LTM.

[0034] Various aspects generally relate to predictive RLM and / or BFD in LTM. Some aspects more specifically relate to the timing prediction of RLF and / or beam faults for one or more LTM candidate cells. In some aspects, network nodes may transmit and UEs may receive configurations for one or more LTM candidate cells. Based at least in part on one or more predicted radio link channel characteristics, UEs may transmit and network nodes may receive reports indicating one or more predicted radio link qualities associated with one or more LTM candidate cells and one or more future time windows. One or more predicted radio link channel characteristics may be predicted future L1 reference received power (L1-RSRP), L1 signal-to-interference-plus-noise ratio (L1-SINR), L3 reference received power (L3-RSRP), L3 signal-to-interference-plus-noise ratio (L3-SINR), etc. In some examples, UEs may estimate and report one or more predicted (e.g., future) radio link qualities for one or more LTM candidate cells with respect to one or more future time windows. For example, predicted radio link qualities may be asynchronous or synchronous instances of RLM metrics (e.g., defined according to the assumption BLER). Additionally or alternatively, the predicted radio link quality may be a beam failure instance (e.g., defined according to the BFD procedure). The predicted radio link quality (e.g., asynchronous instance, synchronous instance, beam failure instance, etc.) may be determined at least in part based on the predicted radio link channel characteristics (e.g., L1-RSRP, L1-SINR, L3-RSRP, L3-SINR, etc.) and UE-side receiver assumptions and / or conditions.

[0035] In some aspects, the UE can generate one or more predicted radio link channel characteristics. For example, the UE can use AI / ML to predict one or more predicted radio link channel characteristics. In some aspects, the network node can transmit, and the UE can receive, indications of one or more predicted radio link channel characteristics. For example, the network node can use AI / ML to predict one or more predicted radio link channel characteristics and can signal these radio link channel characteristics to the UE.

[0036] 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, the described techniques can be used to improve the robustness of LTM by transmitting or receiving reports indicating one or more predicted radio link qualities associated with one or more LTM candidate cells and one or more future time windows, based at least in part on one or more predicted radio link channel characteristics. For example, network nodes and / or UEs can use the predicted radio link quality to prevent UEs from experiencing RLF and / or beam failure shortly after handover to the target cell. Thus, the UE may be involved in fewer radio link recovery, fallback to initial access, etc.

[0037] Generating one or more predicted radio link channel characteristics can improve efficiency because the UE can identify the UE-received beam, orientation, L1-RSRP of unreported beams, etc. The network node sending and the UE receiving indications of one or more predicted radio link channel characteristics can reduce complexity and save resources (e.g., power, computing resources, etc.) at the UE.

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

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

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

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

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

[0043] Alternatively, and also as shown in the figure, network node 110 can be a decomposed network node (sometimes referred to as a decomposed base station), meaning that network node 110 can realize a radio protocol stack that is physically distributed and / or logically distributed among two or more nodes in the same or different geographical locations. For example, a decomposed network node may have a decomposed architecture. In some deployments, decomposed network node 110 may be used in integrated access and backhaul (IAB) networks, in open radio access networks (O-RAN) (such as network configurations conforming to O-RAN Alliance standards), or in virtualized radio access networks (vRAN) (also referred to as cloud radio access networks (C-RAN)) to facilitate scaling by decomposing base station functionality into multiple units that can be deployed independently.

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

[0045] In some aspects, network node 110 may include a combination of one or more CUs, one or more DUs, and / or one or more RUs. Additionally or alternatively, network node 110 may include one or more near real-time (near RT) RAN Intelligent Controllers (RICs) and / or one or more non-real-time (non-RT) RICs. In some examples, CUs, DUs, and / or RUs may be implemented as virtual units, such as Virtual Central Units (VCUs), Virtual Distributed Units (VDUs), or Virtual Radio Units (VRUs), etc. Virtual units may be implemented as virtual network functions, such as those associated with cloud deployments.

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

[0047] The wireless communication network 100 can be a heterogeneous network, comprising different types of network nodes 110, such as macro network nodes, piconet nodes, femtonet nodes, relay network nodes, aggregation network nodes, and / or decomposition network nodes, etc. Figure 1 In the example shown, network node 110a can be a macro network node for macro cell 130a, network node 110b can be a pico network node for pico cell 130b, and network node 110c can be a femto network node for femto cell 130c. Compared to other types of network nodes 110, the various types of network nodes 110 typically transmit at different power levels, serve different coverage areas, and / or have different effects on interference in the wireless communication 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).

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

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

[0050] As described above, in some aspects, the wireless communication network 100 may be an IAB network, may include an IAB network, or may be included in an IAB network. In an IAB network, at least one network node 110 is an anchor network node communicating with a core network. The anchor network node 110 may also be referred to as an IAB donor (or "IAB donor"). The anchor network node 110 may be connected to the core network via a wired backhaul link. For example, the Ng interface of the anchor network node 110 may terminate at the core network. Additionally or alternatively, the anchor network node 110 may be connected to one or more devices in the core network that provide core access and mobility management functions (AMF). An IAB network typically also includes multiple non-anchor network nodes 110, which may also be referred to as relay network nodes or simply IAB nodes (or "IAB-nodes"). Each non-anchor network node 110 can directly communicate with the anchor network node 110 via a wireless backhaul link to access the core network, or can indirectly communicate with the anchor network node 110 via one or more other non-anchor network nodes 110 and an associated wireless backhaul link forming a backhaul path to the core network. Some anchor network nodes 110 or other non-anchor network nodes 110 can also directly communicate with one or more UEs 120 via a wireless access link carrying access services. For example, network resources used for wireless communication (such as time resources, frequency resources, and / or spatial resources) can be shared between the access link and the backhaul link.

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

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

[0053] UE 120 and / or network node 110 may include one or more chips, system-on-a-chip (SoC), chipsets, packages, or devices that individually or collectively constitute or include a processing system. The processing system includes processor (or “processing”) circuitry in the form of one or more processors, microprocessors, processing units (such as central processing units (CPUs), graphics processing units (GPUs), neural processing units (NPUs), and / or digital signal processors (DSPs)), processing blocks, application-specific integrated circuits (ASICs), programmable logic devices (PLDs) (such as field-programmable gate arrays (FPGAs)), or other discrete gate or transistor logic components or circuits (all of which are generally referred to herein individually as “processors” or collectively as “processors” or “processor circuitry”). One or more of these processors may be individually or collectively configured to perform the various functions or operations described herein. A group of processors that can be configured or configured to perform a set of functions may include a first processor that can be configured or configured to perform a first function in the set, and a second processor that can be configured or configured to perform a second function in the set, or may include the entire group of processors that are configured or configured to perform the set of functions.

[0054] The processing system may also include memory circuitry in the form of one or more memory devices, memory blocks, memory elements, or other discrete gate or transistor logic components or circuits, each of which may include tangible storage media such as random access memory (RAM) or read-only memory (ROM) or combinations thereof (all of which are generally referred to herein individually as "memory" or collectively as "memory" or "memory circuitry"). One or more of these memories may be coupled to one or more processors in the processor (e.g., operatively coupled, communicatively coupled, electronically coupled, or electrically coupled) and may store processor-executable code (such as software) individually or collectively, which, when executed by one or more processors in the processor, may configure one or more processors in the processor to perform the various functions or operations described herein. Additionally or alternatively, in some examples, one or more processors in the processor may be pre-configured to perform the various functions or operations described herein without being configured by software. The processing system may also include or be coupled to one or more modems (such as Wi-Fi (e.g., IEEE compliant) modems or cellular (e.g., 3GPP 4G LTE, 5G, or 6G compliant) modems). In some embodiments, one or more processors of the processing system include or implement one or more modems among the modems. The processing system may also include, or be coupled to, multiple radio components (collectively, “radio components”), multiple RF chains, or multiple transceivers, each of which may in turn be coupled to one or more antennas among a plurality of antennas. In some embodiments, one or more processors of the processing system include or implement one or more of the radio components, RF chains, or transceivers. UE 120 may be included or may be contained in a housing that houses components associated with UE 120, including the processing system.

[0055] Some UEs 120 may be considered Machine Type Communication (MTC) UEs, Evolved or Enhanced Machine Type Communication (eMTC) UEs, Further Enhanced eMTC (feMTC) UEs, or Enhanced feMTC (efeMTC) UEs, or further evolutions thereof, all of which may be referred to simply as "MTC UEs". MTC UEs may be, may include, or may be included in or coupled with the following: robots, unmanned aerial vehicles, remote devices, sensors, instruments, monitors, and / or location tags. Some UEs 120 may be considered IoT devices and / or may be implemented as NB-IoT (Narrowband IoT) devices. IoT UEs or NB-IoT devices may be, may include, or may be included in or coupled with the following: industrial machines, appliances, refrigerators, doorbell camera devices, home automation devices, and / or lighting fixtures, etc. Some UEs 120 may be considered customer premises equipment, which may include telecommunications equipment installed at a customer location (such as a home or office) to enable access to a service provider’s network (such as being included in or communicating with the wireless communication network 100).

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

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

[0058] In various examples, in addition to half-duplex operation, some network nodes and UEs in the wireless communication network 100, including network node 110 and UE 120, can also be configured for full-duplex operation. Network node 110 or UE 120 operating in half-duplex mode can perform only one of transmission or reception during a specific time resource period (such as a specific time slot, symbol, or other time period). Half-duplex operation may involve time division duplex (TDD), where the DL transmission of network node 110 and the UL transmission of UE 120 do not occur in the same time resource (i.e., the transmissions do not overlap in time). In contrast, network node 110 or UE 120 operating in full-duplex mode can transmit and receive communications concurrently (e.g., within the same time resource). By operating in full-duplex mode, network node 110 and / or UE 120 can generally increase the capacity of the network and radio access links. In some examples, full-duplex operation may involve frequency division duplex (FDD), in which network node 110 performs DL transmission in a first frequency band or on a first component carrier, and UE 120 performs transmission in a second frequency band or on a second component carrier, the second frequency band or the second component carrier being different from the first frequency band or the first component carrier, respectively. In some examples, full-duplex operation may be enabled for UE 120 but not for network node 110. For example, UE 120 may simultaneously transmit UL to the first network node 110 and receive DL transmissions from the second network node 110 in the same time resources. In some other examples, full-duplex operation may be enabled for network node 110 but not for UE 120. For example, network node 110 may simultaneously transmit DL to the first UE 120 and receive UL transmissions from the second UE 120 in the same time resources. In some other examples, full-duplex operation may be enabled for both network node 110 and UE 120.

[0059] In some examples, UE 120 and network node 110 can perform MIMO communication. "MIMO" generally refers to the simultaneous transmission or reception of multiple signals (such as multiple layers or multiple data streams) using the same time and frequency resources. MIMO techniques typically utilize multipath propagation. MIMO can be implemented using various spatial processing or spatial multiplexing operations. In some examples, MIMO can support simultaneous transmission to multiple receivers, which is called multi-user MIMO (MU-MIMO). Some RATs can employ advanced MIMO techniques such as mTRP operations (including redundant transmission or reception on multiple TRPs), reciprocity in the time or frequency domain, single-frequency network (SFN) transmission, or noncoherent joint transmission (NC-JT).

[0060] In some respects, UE 120 may include a communications manager 140. As described in more detail elsewhere herein, communications manager 140 may: receive configurations of one or more LTM candidate cells; and transmit reports indicating one or more predicted radio link qualities associated with one or more LTM candidate cells and one or more future time windows, based at least in part on one or more predicted radio link channel characteristics. Additionally or alternatively, communications manager 140 may perform one or more other operations described herein.

[0061] In some respects, network node 110 may include communication manager 150. As described in more detail elsewhere herein, communication manager 150 may: transmit configurations of one or more LTM candidate cells; and receive reports indicating one or more predicted radio link qualities associated with one or more LTM candidate cells and one or more future time windows, based at least in part on one or more predicted radio link channel characteristics. Additionally or alternatively, communication manager 150 may perform one or more other operations described herein.

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

[0063] Figure 2 This is an illustration of an example network node 110 communicating with an example UE 120 in a wireless network according to the present disclosure.

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

[0065] The terms “processor,” “controller,” or “controller / processor” can refer to one or more controllers and / or one or more processors. For example, references to “a / the processor,” “a / the controller / processor,” etc. (in the singular) should be understood as referring to a combination of… Figure 2 The processor described refers to any one or more processors, such as a single processor or a combination of multiple different processors. The reference to "one or more processors" should be understood as a combination of references. Figure 2 Any one or more processors described herein. For example, one or more processors of network node 110 may include transmit processor 214, TX MIMO processor 216, MIMO detector 236, receive processor 238, and / or controller / processor 240. Similarly, one or more processors of UE 120 may include MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, and / or controller / processor 280.

[0066] In some aspects, a single processor can perform all operations described as being performed by one or more processors. In some aspects, a first set of one or more processors can perform a first operation described as being performed by that one or more processors, and a second set of one or more processors can perform a second operation described as being performed by that one or more processors. The processors in the first set and the processors in the second set can be from the same set of processors or can be from different sets of processors. 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 combination. Figure 2 The memory described. For example, an operation 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0084] Figure 3 This is an illustration of an example disaggregated base station architecture 300 according to the present disclosure. One or more components of the example disaggregated base station architecture 300 may be one or more network nodes (such as one or more network nodes 110), may include, or may be included in, the one or more network nodes. 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 may communicate indirectly with the core network 320 via one or more disaggregated control units (such as non-RT RIC 350 and / or near-RT RIC 370 associated with a Service Management and Orchestration (SMO) framework 360 (e.g., via an E2 link)). The CU 310 may communicate with one or more DU 330 via a corresponding midhaul link (such as via an F1 interface). Each DU 330 may communicate with one or more RU 340 via a corresponding fronthaul link. Each RU 340 may communicate with one or more UE 120 via a corresponding RF access link. In some deployments, UE 120 can be served by multiple RU 340s simultaneously.

[0085] Each component of the disassembled base station architecture 300 (including CU 310, DU 330, RU 340, near-RT RIC 370, non-RT RIC 350, and SMO frame 360) may include one or more interfaces or may be coupled to one or more interfaces for receiving or transmitting signals, such as data or information, via wired or wireless transmission media.

[0086] In some respects, the CU 310 can be logically divided into one or more CU user plane (CU-UP) units and one or more CU control plane (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 deployed to communicate with one or more DU 330s for network control and signaling, as needed. Each DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RU 340s. For example, the DU 330 may host various layers, such as the RLC layer, MAC layer, or one or more PHY layers (such as one or more high PHY layers or one or more low PHY layers). Each layer (which may also be referred to as a module) can be implemented using an interface for signaling to other layers (and modules) hosted by the DU 330, or for signaling to control functions hosted by the CU 310. Each RU 340 may implement lower-layer functionality. In some respects, the real-time and non-real-time aspects of communication with the control plane and user plane of the RU 340 can be controlled by the corresponding DU 330.

[0087] The SMO framework 360 supports RAN deployment and provisioning for both non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 360 supports the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operation and maintenance interfaces such as the O1 interface. For virtualized network elements, the SMO framework 360 can 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. Virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 350, and / or near-RT RIC 370. In some aspects, the SMO framework 360 can communicate with hardware aspects of the 4G RAN, 5G NR RAN, and / or 6G RAN (such as the Open eNB (O-eNB) 380) via the O1 interface. Additionally or alternatively, the SMO framework 360 can communicate directly with each of one or more RUs 340 via the corresponding O1 interface. In some deployments, this configuration enables each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0088] The non-RT RIC 350 may include or implement logic functions that enable non-real-time control and optimization of RAN elements and resources, including AI / ML workflows for model training and updates, and / or policy-based guidance of applications and / or features in the near-RT RIC 370. The non-RT RIC 350 may be coupled to or communicate with the near-RT RIC 370, such as via an A1 interface. The near-RT RIC 370 may include or implement logic 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, and / or O-eNBs to the near-RT RIC 370.

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

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

[0091] Figure 1 , Figure 2 or Figure 3 Network node 110, its controller / processor 240, UE 120, UE 120's controller / processor 280, CU 310, DU 330, RU 340, or any other component may implement one or more technologies associated with predicted radio link quality reports for LTM or perform one or more operations associated with predicted radio link quality reports for LTM, as described in more detail elsewhere herein. For example, network node 110's controller / processor 240, UE 120's controller / processor 280, CU 310, DU 330, RU 340, or any other component may implement one or more technologies associated with predicted radio link quality reports for LTM or perform one or more operations associated with predicted radio link quality reports for LTM, as described in more detail elsewhere herein. Figure 2 Any other component, CU 310, DU 330, or RU 340 may execute or instruct, for example Figure 10 Process 1000 Figure 11The operation of process 1100 or other processes as described herein (alone or in combination with one or more other processors). Memory 242 may store data and program code for network node 110, CU 310, DU 330, or RU 340. Memory 282 may store data and program code for UE 120. In some examples, memory 242 or memory 282 may include a non-transitory computer-readable medium storing a set of instructions (e.g., code or program code) for wireless communication. Memory 242 may include one or more memories, such as a single memory or multiple different memories (of the same or different types). Memory 282 may include one or more memories, such as a single memory or multiple different memories (of the same or different types). For example, the set of instructions may be made to be executed by one or more processors of network node 110, UE 120, CU 310, DU 330, or RU 340 (e.g., directly, or after compilation, transformation, or interpretation). Figure 10 Process 1000 Figure 11 The process 1100 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.

[0092] In some aspects, UE 120 includes: components for receiving configurations of one or more LTM candidate cells; and / or components for transmitting reports indicating one or more predicted radio link qualities associated with one or more LTM candidate cells and one or more future time windows, at least in part based on one or more predicted radio link channel characteristics. Components enabling UE 120 to perform the operations described herein may include, for example, one or more of the following: a communications 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.

[0093] In some aspects, network node 110 includes: components for transmitting configurations of one or more LTM candidate cells; and / or components for receiving, at least in part, reports indicating one or more predicted radio link qualities associated with one or more LTM candidate cells and one or more future time windows, based on one or more predicted radio link channel characteristics. Components enabling network node 110 to perform the operations described herein may include, for example, one or more of the following: a communications manager 150, a transmit processor 214, a TX MIMO processor 216, a modem 232, an antenna 234, a MIMO detector 236, a receive processor 238, a controller / processor 240, a memory 242, or a scheduler 246.

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

[0095] One or more AI / ML models can be used to facilitate wireless communication tasks. The lifecycle management of AI / ML models can involve model training, model deployment, model inference, model monitoring, and model updates. Model training can involve AI / ML model training (e.g., offline training), validation and / or testing, etc. AI / ML model training can also involve data preparation based on training data delivered by data collection functions (e.g., data preprocessing, data cleaning, data formatting and / or transformation, etc.). Model deployment can include deploying the AI / ML model (e.g., at the UE or network node).

[0096] Model inference may involve feeding inferred data as input to an AI / ML model and obtaining the AI / ML model's inference output (e.g., prediction, classification, estimation, and / or decision-making, etc.). In some cases, model inference may involve providing model performance feedback to the model training function. Model inference may also involve performing data preparation based on the inferred data (e.g., data preprocessing, data cleaning, data formatting, and / or transformation, etc.).

[0097] Model monitoring can involve monitoring the performance of an AI / ML model (e.g., how frequently and / or how well the predictions generated by the AI / ML model are correct). For example, poor performance of an AI / ML model (e.g., if the accuracy of the AI / ML model's predictions drops below a threshold) may trigger a fallback to a non-AI / ML model. Model updates can involve retraining the AI / ML model or switching to a different AI / ML model. In some examples, model monitoring can trigger model updates.

[0098] AI / ML-based predictive beam management can involve beam management using AI / ML. One problem with traditional beam management processes is identifying beam quality / faults via measurements, which can require significant power / overhead to achieve good performance. Furthermore, beam accuracy can be limited by power / overhead constraints, and latency / throughput can be affected by beam recovery efforts. AI / ML-based predictive beam management can provide predictive beam management in the spatial domain (SD), time domain (TD), and / or frequency domain (FD), and may lead to reduced latency and overhead and / or improved beam selection accuracy.

[0099] For AI / ML-based beam management, both a first case and a second case of beam management can be supported for characterization and baseline performance evaluation. In the first case, SD downlink beam prediction for beam set A can be at least partially based on measurements from beam set B. In the second case, temporal downlink beam prediction for beam set A can be at least partially based on historical measurements from beam set B. Therefore, set A can correspond to the output of the ML model, and set B can correspond to the input of the model. Beams in set A and set B can be in the same frequency range.

[0100] For the first scenario, a first alternative and a second alternative can be defined. In the first alternative, beams in set B may be a subset of beams in set A. The number of beams in set A and the number of beams in set B can be defined. Beams in set B can be determined from beams in set A, at least in part, based on a fixed or random pattern. In the second alternative, beams in set A may differ from beams in set B (e.g., beams in set B may not be a subset of beams in set A). For example, beams in set A may be associated with narrow beams, and beams in set B may be associated with wide beams. The number of beams in set A and the number of beams in set B can be defined. Quasi-colocation (QCL) relationships can be defined between beams in set A and beams in set B. For both the first and second alternatives, set A may be associated with downlink beam prediction, and set B may be associated with downlink beam measurement. Codebook constructions for set A and set B can be defined.

[0101] In some cases, downlink spatial and temporal beam prediction can be at least partially based on AI / ML techniques. In the first case, spatial downlink beam prediction for set A beams can be at least partially based on measurements of set B beams. In some examples, set B beams can be wide beams similar to synchronization signal blocks, and set A beams can be narrow beams similar to CSI-RS. In some examples, set B beams can be narrow beams, and set A beams can be other narrow beams. In the second case, temporal downlink beam prediction for set A beams can be based on historical measurements of set B beams. In some examples, set A beams and set B beams can be the same (e.g., using pure temporal beam prediction). In some examples, set A beams and set B beams can be different (e.g., using both spatial and temporal beam prediction). In single-cell scenarios, prediction may occur at both the gNB side and the UE side.

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

[0103] 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 use an L3 handover procedure to change cells. 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 disconnect 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.

[0104] Because of the multiple RRC reconfiguration messages and / or other L3 signaling and operations used to perform the handover procedure, the L3 handover process can be associated with high latency and high overhead. Accordingly, in some examples, the UE 120 may be configured to perform lower-layer (e.g., L1 and / or L2) handover procedures, sometimes referred to as LTM procedures, such as... Figure 4The example 400 LTM process is 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.

[0105] 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 a Measurement Report), 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 the 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.

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

[0107] 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 early timing 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, as described in more detail below with reference numeral 455.

[0108] 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 lower-layer (e.g., L1) measurement reports to network node 110. As indicated by reference numeral 440, based at least in part on the lower-layer measurement reports, network node 110 may decide to perform an LTM cell handover to the target cell. Accordingly, as indicated by reference numeral 445, network node 110 may send, and UE 120 may receive, a 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 the receipt of 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 a target cell, such as when the timing associated with the target cell is not available in advance (e.g., in an example where UE 120 does not perform an early synchronization as described above in conjunction with reference numeral 430).

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

[0110] In some cases, L1 and / or L2 can be enhanced (e.g., mobility and / or LTM can be AI / ML assisted). For example, AI / ML-based beam prediction can be implemented for LTM. In some examples, spatial prediction can reduce the power consumption and measurement latency of the UE 120 for a large number of cross-cell beams (e.g., by measuring the L1-RSRP of a first set of cross-cell synchronization signal blocks (SSBs) and predicting the L1-RSRP of a second set of cross-cell SSBs). In some examples, temporal prediction can reduce LTM latency and avoid throughput interruptions (e.g., for inter-DU scenarios, non-ideal backhaul scenarios, etc.). For example, the L1-RSRP of SSBs can be measured, and the L1-RSRP of narrow beams similar to CSI-RS can be predicted relative to future timing for the LTM target cell. Additionally or alternatively, the triggering conditions in conditional LTM can take into account the UE-side temporal beam prediction results.

[0111] Reactive RLM and BFD lack robustness in LTM. For example, traditionally, RLM uses historical measurements, such as the assumed BLER of PDCCH evaluated over tens of milliseconds (e.g., assumed PDCCH BLER). In some cases, UE 120 can identify instances of desynchronization or synchronization. For example, if the radio link quality (e.g., assumed PDCCH BLER) does not meet (e.g., below) the threshold Q of all resources in the resource set of the RLM. out Then the physical layer in UE 120 can provide asynchrony indications to higher layers in frames that evaluate radio link quality. If the radio link quality (e.g., assuming PDCCH BLER) meets (e.g., is higher than) a threshold Q for any resource in the RLM's resource set. in Then the physical layer in UE 120 can provide synchronization indications to higher layers in frames that assess radio link quality. Q out and Q in The value can be a serving cell-specific predefined value (e.g., in the standard) and configured by network node 110. UE 120 may not perform RLM outside of the active downlink BWP.

[0112] Mobility decisions (e.g., as indicated via MAC-CE) are typically made using the L1-RSRP reported by the UE regarding the SSBs in the candidate cell, enabling faster and more efficient cell handovers. However, the L1-RSRP measured solely by the UE 120 is insufficient to adequately identify potential RLFs (e.g., due to impending obstruction) in the target cell. Therefore, the robustness of LTM may be reduced due to reactive RLMs based solely on historical measurements. For example, although LTM cell handovers can be performed with short delays, the UE 120 may experience an RLF in the target cell shortly after the LTM cell handover (e.g., within tens or hundreds of milliseconds). The UE 120 may respond to the RLF by performing radio link recovery or fallback to initial access, which could reduce robustness.

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

[0114] Figure 5 This is a diagram illustrating example 500 associated with a radio link quality report for LTM prediction according to this disclosure. Figure 5 As shown, network node 110 and UE 120 can communicate with each other.

[0115] As shown by reference numeral 510 in the accompanying drawings, network node 110 may send and UE 120 may receive configurations for one or more LTM candidate cells. For example, network node 110 may send and UE 120 may receive an RRC reconfiguration message indicating such configuration. One or more LTM candidate cells may become the serving cell of UE 120 and / or may be cells that UE 120 may later trigger to perform an LTM procedure on.

[0116] As indicated by reference numeral 520 in the accompanying drawings, UE 120 may transmit, and network node 110 may receive, a report indicating one or more predicted radio link qualities associated with one or more LTM candidate cells and one or more future time windows, based at least in part on one or more predicted radio link channel characteristics. The one or more predicted radio link channel characteristics may be predicted future L1-RSRP, L1-SINR, L3-RSRP, L3-SINR, etc. The one or more predicted radio link qualities may be associated with one or more LTM candidate cells because the one or more predicted radio link qualities may be one or more radio link qualities that UE 120 is predicted to experience in one or more LTM candidate cells. The one or more predicted radio link qualities may be associated with one or more future time windows because UE 120 is predicted to experience one or more predicted radio link qualities in one or more future time windows. Therefore, in some examples, UE 120 may (e.g., via MAC-CE, UCI, etc.) estimate and report one or more predicted future radio link qualities for one or more LTM candidate cells in one or more future time windows. One or more predicted future radio link quality may be based, at least in part, on one or more predicted radio link channel characteristics relative to one or more predictive RLM reference signals (RLM-RS) associated with one or more LTM candidate cells.

[0117] In some aspects, UE 120 may generate one or more predicted radio link channel characteristics. These aspects may involve purely UE-based predictive RLM for LTM. For example, UE 120 may use AI / ML to predict one or more predicted radio link channel characteristics. UE 120 may estimate and report future RLF based at least in part on one or more predicted radio link channel characteristics and / or UE 120's reception assumptions. Reception assumptions enable UE 120 to derive the hypothetical PDCCH BLER.

[0118] In some aspects (e.g., relating to purely UE-based predictive RLM for LTM), network node 110 may send, and UE 120 may receive, an instruction for activating artificial intelligence (AI) functionality associated with sending the report. Such aspects may be referred to as an AI / ML framework for purely UE-based predictive RLM for LTM. The AI ​​functionality may be an AI / ML functionality that enables UE 120 to perform predictive RLM and / or predictive BFD. For example, network node 110 may activate applicable AI / ML functionality for UE 120, which may enable UE 120 to report predictive future (e.g., predicted) RLM and / or BFD results. The AI / ML functionality may be referred to as “predictive RLM for LTM AI / ML functionality” and / or “predictive BFD for LTM AI / ML functionality”.

[0119] When AI / ML functionality is activated, UE 120 may receive an additional indication of a model identifier corresponding to the model to be used for prediction (e.g., an AI / ML model). In some examples, the model may be preloaded at UE 120. In some examples, UE 120 may download the model. Furthermore, network node 110 may send, and UE 120 may receive, an indication to update the model identifier. For example, if network node 110 updates the configuration / indication on the predictive RLM-RS, network node 110 may also update the associated model identifier.

[0120] In some aspects, network node 110 may transmit, and UE 120 may receive, indications of one or more predicted radio link channel characteristics. Such aspects may involve network-assisted predictive RLM for LTM. For example, network node 110 may use AI / ML to predict one or more predicted radio link channel characteristics, and these radio link channel characteristics may be signaled from network node 110 to UE 120. Upon receiving the predicted radio link channel characteristics signaled by the network, UE 120 may estimate and report future RLF at least in part based on one or more predicted radio link channel characteristics and / or UE 120's reception assumptions. Reception assumptions may enable UE 120 to derive the assumed PDCCH BLER.

[0121] In some respects, one or more predicted radio link channel characteristics are based at least in part on one or more predictive RLM-RS. The one or more predictive RLM-RS may be based at least in part on actual SSB and / or CSI-RS associated with one or more LTM candidate cells, virtual RS associated with one or more LTM candidate cells but not actually transmitted, etc. If a virtual RS is configured or indicated, UE 120 may perform UE-side spatial beamforming prediction of one or more predicted radio link channel characteristics on the virtual RS based at least in part on measurements from actual SSB and / or CSI-RS relative to the LTM candidate cells.

[0122] In some respects, one or more future time windows are associated with one or more start times or one or more end times. In some examples, network node 110 may signal the start and end times (e.g., start and end points) on the future time window. In some examples, the start and end times may be (e.g., in the standard) predefined, where the start point is defined in association with the network command that triggers UE 120 to report the feedback. Examples of network commands may include an LTM cell handover MAC-CE command, a DCI triggering one or more aperiodic CSI reports carrying the report, a MAC-CE activating a semi-persistent CSI report carrying the report, etc.

[0123] In some examples, network node 110 may indicate which LTM candidate cells to address. For example, network node 110 may signal a subset of LTM candidate cells in the RRC configuration to be addressed. In some examples, which LTM candidate cells to address may be predefined (e.g., in a standard). For example, the standard may predefine that all LTM candidate cells should be addressed, or only LTM candidate cells configured with predictive RLM-RS should be addressed.

[0124] Therefore, network node 110 can send, and UE 120 can receive, configurations or indications relative to the RLM-RS and future time window associated with the prediction. Network node 110 can use RRC, MAC-CE, DCI, etc., to send the configurations or indications. In the case of RRC, if the CSI report is used for UE feedback, network node 110 can use the RRC configuration relative to the LTM candidate cell, the RRC configuration set in the CSI report, or the CSI-AssociatedReportConfigInfo information element (IE), or other RRC configuration IEs. In the case of MAC-CE, if the semi-persistent CSI report is used for UE feedback, network node 110 can use the LTM cell handover MAC-CE command, MAC-CE to activate the semi-persistent CSI report, or other dedicated MAC-CE. In some examples, the MAC-CE can be selected from multiple RRC configuration options. In the case of DCI, if the non-periodic CSI report is used for UE feedback or other dedicated DCI fields, network node 110 can use the DCI that triggers the non-periodic CSI report. In some examples, DCI can be selected from multiple RRC configurations and / or MAC-CE indications, or selected downwards. In the case of an AI / ML framework for purely UE-based predictive RLM for LTM, AI / ML functionality can be RRC-based, MAC-CE-based, DCI-based, etc. For example, AI / ML functionality can be activated using RRC with other RRC configurations described herein, MAC-CE with other MAC-CE indications described herein, DCI with other DCI indications described herein, etc.

[0125] In the case of network-assisted predictive RLM for LTM, UE 120 may receive, at least in part, predicted radio link channel characteristics relative to the network-configured or network-indicated predictive RLM-RS based on a downlink MAC-CE or RRC. In the case of a downlink MAC-CE, a network prediction amount regarding one or more future time windows on the predictive RLM-RS in the applicable LTM candidate cells may be signaled in a single MAC-CE. For example, a single MAC-CE may be a dedicated MAC-CE (which may also be used as a trigger command for a report), an LTM cell handover MAC-CE command, a MAC-CE activating a semi-persistent CSI report carrying a report, etc. MAC-CEs may be well-suited for performing real-time operations involved in predictive RLM and / or BFD. Additionally or alternatively, the network prediction amount may be configured by RRC.

[0126] The report may contain any suitable reporting volume. In some respects (e.g., for predictive RLM), it predicts one or more desynchronization events that will occur within one or more future time windows for one or more LTM candidate cells. Therefore, in some examples, the reporting volume may only include the predicted desynchronization events for certain LTM candidate cells and future windows. For example, UE 120 may (e.g., via MAC-CE) send a report containing only such desynchronization events and the predicted future window (e.g., window identifier). MAC-CE may be triggered in response to UE 120 identifying at least one desynchronization event for a certain LTM candidate cell and a certain future time window.

[0127] In some respects (e.g., for predictive RLM), at least one of an asynchronous event or a synchronous event can be predicted to occur within one or more future time windows for one or more LTM candidate cells. Therefore, in some examples, the reporting volume may include events in which at least one of an asynchronous event or a synchronous event is predicted for certain LTM candidate cells and future windows. For example, UE 120 may (e.g., via MAC-CE) send a report containing such an asynchronous event and / or a synchronous event, along with the predicted future window (e.g., a window identifier). MAC-CE may be triggered in response to UE 120 identifying at least one asynchronous event or synchronous event for a given LTM candidate cell and a given future time window.

[0128] In some respects (e.g., for predictive RLM), events that are neither asynchronous nor synchronous can be predicted to occur within one or more future time windows for one or more LTM candidate cells. For example, in addition to at least one of asynchronous or synchronous events, the reporting volume may also include events for applicable future windows, where neither synchronous nor asynchronous events are predicted relative to certain LTM candidate cells. For example, UE 120 may send a report (e.g., as a CSI report or via MAC-CE) containing (e.g., addressing) all applicable LTM candidate cells and future time windows. Thus, for a given LTM candidate cell and future time window, UE 120 may report one or more predicted radio link quality events as one or more of the following: asynchronous events, synchronous events, or events that are neither asynchronous nor synchronous.

[0129] In some respects (e.g., for predictive RLM), one or more predicted radio link quality parameters may include one or more predicted hypothetical block error rates. Therefore, in some examples, the reported quantity may include one or more estimated PDCCH hypothesis BLER values ​​predicted for LTM candidate cells and future time windows. For example, UE 120 may transmit a report containing (e.g., addressed) all applicable LTM candidate cells and future time windows (e.g., as a CSI report or via MAC-CE). Thus, for a given LTM candidate cell and future time window, UE 120 may report PDCCH hypothesis BLER values ​​relative to all corresponding RLM-RS.

[0130] UE 120 can determine whether an event is asynchronous, synchronous, or neither. The criteria for predicting whether a future event is asynchronous, synchronous, or neither based on a given LTM candidate cell and a future time window can be at least partially based on an extension of the method used to determine whether an event is asynchronous or synchronous relative to the active downlink BWP.

[0131] In some aspects, one or more predicted radio link quality parameters include one or more predicted PDCCH assumption BLERs. For example, UE 120 may evaluate events based at least in part on predicted PDCCH assumption BLERs (e.g., rather than on measured assumption BLERs). In some aspects, one or more predicted PDCCH assumption block error rates may be correlated with one or more per-LTM candidate cell thresholds (e.g., Q... out and Q in Related to ) For example, Q out和 Q in The value can be (e.g., in the standard) predefined and configured by network node 110 for different LTM candidate cells. In some respects, the report can be associated with one or more frequencies outside of the active downlink BWP. For example, UE 120 can perform predictive RLM and / or predictive BFD outside of the active downlink BWP.

[0132] In some examples, the report may be provided periodically or triggered aperiodically (e.g., and transmitted via UCI). In some examples, the report may be an event-triggered UE report (e.g., and transmitted via MAC-CE). For example, UE 120 may send the report in response to one or more triggering conditions. In the case that the report is event-triggered, one or more parameters may control the triggering conditions. One or more parameters may be (e.g., in the standard) predefined, or signaled by network node 110 via RRC, MAC-CE, DCI, etc.

[0133] In some examples, the parameter can be an on / off parameter. In some aspects, UE 120 may send the report in response to a predicted asynchronous event for one of one or more LTM candidate cells and one of one or more future time windows. For example, the report may be triggered only if at least one asynchronous instance is predicted for a given LTM candidate cell and a given future window. In some aspects, UE 120 may send the report in response to a predicted asynchronous event for a primary cell (Pcell) associated with UE 120, a primary / secondary cell (PsCell) associated with UE 120, an active serving cell associated with UE 120, or multiple active serving cells associated with UE 120. For example, the report may be triggered only if at least one asynchronous instance is predicted for a given Pcell, PsCell, any active serving cell, or all active serving cells. In some aspects, UE 120 may send the report in response to a predicted synchronization event for one of one or more LTM candidate cells or for an LTM candidate cell that is not an active serving cell among one or more LTM candidate cells. For example, the report can only be triggered if at least one synchronization instance is predicted for a particular LTM candidate cell or for an LTM candidate cell that is not an active serving cell.

[0134] In some examples, the parameter may be a quantitative parameter. In some aspects, UE 120 may send the report in response to the number of predicted asynchronous events for the primary cell (Pcell) associated with the UE, the PsCell associated with the UE, the active serving cell associated with the UE, or multiple active serving cells associated with the UE, meeting a first threshold. For example, the report may be triggered only if the number of predicted asynchronous instances for a particular Pcell, PsCell, any active serving cell, or all active serving cells meets (e.g., exceeds) a predefined (e.g., in a standard) or network-controlled threshold. In some aspects, UE 120 may send the report in response to the number of predicted asynchronous events for at least one LTM candidate cell that is not an active serving cell among one or more LTM candidate cells, meeting a second threshold. For example, the report may be triggered only if the number of predicted synchronization instances for an LTM candidate cell that is not an active serving cell meets (e.g., exceeds) a predefined (e.g., in a standard) or network-controlled threshold.

[0135] In some respects, the report may be associated with BFD (e.g., predictive BFD). In some examples, the number of reports for predictive BFD may include the number of instances where, for a given LTM candidate cell and a given RLM-RS or BFD-RS within a given future time window, the PDCCH assumes that the BLER meets (e.g., exceeds) a threshold of network configuration. For a given LTM candidate cell and a given future time window, a predictive beam fault may be declared at least in part based on the number of instances where the PDCCH assumes the BLER meets the threshold of network configuration that meets (e.g., exceeds) the threshold of the number of instances of network configuration for all BFD-RS configured for the LTM candidate cell during the future time window.

[0136] Predictive BFD may involve a purely UE-based predictive BFD for LTM, which may be similar to a purely UE-based predictive RLM for LTM. For example, BFD prediction may use the future (e.g., predicted) L1-RSRP on the BFD-RS predicted by UE 120. Additionally or alternatively, predictive BFD may involve a network-assisted predictive BFD for LTM, which may be similar to a network-assisted predictive RLM for LTM. For example, network-assisted predictive BFD for LTM may use the future (e.g., predicted) L1-RSRP on the BFD-RS signaled by network node 110.

[0137] In some respects, this report may be associated with conditional LTM. For example, UE 120 may determine whether to trigger a conditional LTM cell handover request based at least in part on the predicted radio link quality regarding LTM candidate cells and future time windows. The conditions for triggering a conditional LTM cell handover request may be predefined (e.g., in the standard) or configured or indicated by network node 110. The conditions may be any triggering conditions suitable for triggering conditional LTM, such as any suitable triggering conditions described herein (e.g., having network-controllable parameters). In the case of conditional LTM, UE 120 may or may not send a report (e.g., may or may not report radio link quality to network node 110).

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

[0139] Figure 6 This is a diagram illustrating example 600 associated with predictive RLM in LTM according to this disclosure.

[0140] In some examples, UE 120 may use a predictive RLM-RS 620 to identify the predicted radio link quality relative to a future time window 630 for LTM candidate cell 610. The predictive RLM-RS 620 may be based at least in part on SSB, CSI-RS, virtual RS, etc., and may assist UE 120 in predicting the predicted radio link quality via predicted radio link channel characteristics (e.g., predicted future L1-RSRP, L3-RSRP, etc.). The predicted radio link channel characteristics may be predicted by UE 120 or network node 110. UE 120 may report to network node 110 instances of asynchrony, synchronization, or neither synchronization nor non-synchronization between each LTM candidate cell 610 and the future time window 630.

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

[0142] Figure 7 This is an illustration of example 700 associated with a purely UE-based predictive RLM for LTM according to this disclosure.

[0143] As shown by reference numeral 710, UE 120 can operate an AI / ML model residing at UE 120. As shown by reference numeral 720, the AI / ML model can output predicted radio link channel characteristics (e.g., predicted future L1-RSRP, L3-RSRP, etc.) for future time windows. UE 120 can use the predicted radio link channel characteristics to generate predicted radio link quality for three different cells (e.g., LTM candidate cells) relative to future time windows. As shown by reference numeral 730, UE 120 can report the predicted radio link channel characteristics to network node 110.

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

[0145] Figure 8 This is an illustration of an example 800 associated with an AI / ML framework for a purely UE-based predictive RLM for LTM according to this disclosure.

[0146] As indicated by reference numeral 810 in the attached figure, network node 110 can activate AI / ML functionality. Over time, network node 110 can update predictive RLM-related configurations or indications (e.g., predictive RLM configurations 820-840) and corresponding model identifiers, at least in part based on updated predictive RLM configurations 820-840. Predictive RLM configuration 820 may correspond to model A, where predictive RLM-RS is predicted at least in part based on wide beams. Predictive RLM configuration 830 may correspond to model B, where predictive RLM-RS is predicted at least in part based on narrow beams. Predictive RLM configuration 840 may correspond to model C, where predictive RLM-RS is predicted at least in part based on both narrow and wide beams. Predictive RLM-RS may be at least in part based on SSB, CSI-RS, virtual RS, etc.

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

[0148] Figure 9 This is an illustration of example 900 associated with network-assisted predictive RLM for LTM according to this disclosure.

[0149] As shown by reference numeral 910, network node 110 can use an AI / ML model residing at network node 110 to generate predicted radio link channel characteristics (e.g., predicted future L1-RSRP, L3-RSRP, etc.) for future time-prospective scenarios. As shown by reference numeral 920, network node 110 can signal the predicted radio link channel characteristics to UE 120 via MAC-CE or RRC. As shown by reference numeral 930, UE 120 can use the predicted radio link channel characteristics to generate predicted radio link quality for three different cells (e.g., LTM candidate cells) relative to a future time window. As shown by reference numeral 940, UE 120 can report the predicted radio link channel characteristics to network node 110.

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

[0151] One or more predicted radio link qualities associated with one or more LTM candidate cells and one or more future time windows can improve the robustness of LTM. For example, network node 110 and / or UE 120 can use predicted radio link qualities to prevent UE 120 from experiencing RLF and / or beam failure shortly after handover to the target cell. Therefore, UE 120 may be involved in fewer radio link recovery, fallback to initial access, etc.

[0152] UE 120 can improve efficiency by generating one or more predicted radio link channel characteristics because UE 120 can identify the UE received beam, orientation, L1-RSRP of unreported beams, etc. The network node sends and UE 120 receives indications of one or more predicted radio link channel characteristics, which can reduce complexity and save resources (e.g., power, computing resources, etc.) at UE 120.

[0153] Predicting one or more asynchronous events occurring within one or more future time windows for one or more LTM candidate cells helps ensure that the report indicates which LTM candidate cells to avoid (e.g., LTM candidate cells with asynchronous events). Predicting at least one of asynchronous or synchronous events occurring within one or more future time windows for one or more LTM candidate cells helps ensure that the report can recommend LTM candidate cells (e.g., LTM candidate cells with synchronous events).

[0154] 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 a radio link quality report for a predicted LTM.

[0155] like Figure 10 As shown, in some aspects, process 1000 may include the configuration of receiving one or more LTM candidate cells (block 1010). For example, the UE (e.g., using...) Figure 12 The receiving component 1202 and / or communication manager 1206 described herein can receive configurations for one or more LTM candidate cells as described above.

[0156] like Figure 10 Further shown, in some aspects, process 1000 may include transmitting a report (box 1020) indicating one or more predicted radio link qualities associated with one or more LTM candidate cells and one or more future time windows, based at least in part on one or more predicted radio link channel characteristics. For example, the UE (e.g., using...) Figure 12The transmitting component 1204 and / or the communication manager 1206 described herein may transmit, at least in part, a report indicating one or more predicted radio link qualities associated with one or more LTM candidate cells and one or more future time windows, as described above, based on one or more predicted radio link channel characteristics.

[0157] 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 in this document.

[0158] In a first aspect, process 1000 includes generating one or more predicted radio link channel characteristics.

[0159] In a second aspect, either alone or in combination with the first aspect, process 1000 includes receiving an instruction for activating AI functionality associated with sending the report.

[0160] In a third aspect, either alone or in combination with one or more of the first and second aspects, process 1000 includes receiving an indication of one or more predicted radio link channel characteristics.

[0161] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, one or more predicted radio link channel characteristics are based at least in part on one or more predictive RLM-RS.

[0162] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, one or more future time windows are associated with one or more start times or one or more end times.

[0163] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, one or more asynchronous events are predicted to occur in one or more future time windows for one or more LTM candidate cells.

[0164] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, it is predicted that at least one of an asynchronous event or a synchronous event will occur in one or more future time windows for one or more LTM candidate cells.

[0165] In the eighth aspect, either alone or in combination with one or more of the first to seventh aspects, an event is predicted to occur in one or more future time windows for one or more LTM candidate cells, and the event is neither an asynchronous event nor a synchronous event.

[0166] In the ninth aspect, alone or in combination with one or more of the first to eighth aspects, one or more predicted radio link quality includes one or more predicted PDCCH hypothetical block error rates.

[0167] In the tenth aspect, alone or in combination with one or more of the first to ninth aspects, one or more predicted radio link quality includes one or more predicted PDCCH hypothetical block error rates, which are associated with one or more per-LTM candidate cell thresholds, or the report is associated with one or more frequencies outside of the active downlink BWP.

[0168] In the eleventh aspect, sending the report, either alone or in combination with one or more of the first to tenth aspects, includes sending the report in response to one or more of the following: a desynchronization event predicted for one of one or more LTM candidate cells and one of one or more future time windows; a desynchronization event predicted for a Pcell associated with the UE, a PsCell associated with the UE, an active serving cell associated with the UE, or multiple active serving cells associated with the UE; or a synchronization event predicted for one of one or more LTM candidate cells or for one of one or more LTM candidate cells that is not an active serving cell.

[0169] In the twelfth aspect, sending the report, either alone or in combination with one or more of the first to eleventh aspects, includes sending the report in response to one or more of the following: the number of out-of-synchronization events predicted for a Pcell associated with the UE, a PsCell associated with the UE, an active serving cell associated with the UE, or multiple active serving cells associated with the UE meets a first threshold; or the number of out-of-synchronization events predicted for at least one LTM candidate cell that is not an active serving cell among one or more LTM candidate cells meets a second threshold.

[0170] In the thirteenth aspect, the report is associated with beam fault detection, either alone or in combination with one or more of the first to twelfth aspects.

[0171] In aspect fourteen, alone or in combination with one or more of aspects one through thirteen, this report is associated with conditional LTM.

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

[0173] Figure 11 This is a diagram illustrating an example process 1100 performed, for example, at a network node or a device of a network node according to this disclosure. Example process 1100 is an example in which a device or network node (e.g., network node 110) performs operations associated with a radio link quality report for a prediction of LTM.

[0174] like Figure 11 As shown, in some aspects, process 1100 may include sending configurations for one or more LTM candidate cells (box 1110). For example, network nodes (e.g., using...) Figure 13 The transmitting component 1304 and / or the communication manager 1306 described herein can transmit the configuration of one or more LTM candidate cells as described above.

[0175] like Figure 11 Further shown, in some aspects, process 1100 may include receiving reports (box 1120) indicating one or more predicted radio link qualities associated with one or more LTM candidate cells and one or more future time windows, based at least in part on one or more predicted radio link channel characteristics. For example, network nodes (e.g., using...) Figure 13 The receiving component 1302 and / or communication manager 1306 described herein may receive, at least in part, reports indicating one or more predicted radio link qualities associated with one or more LTM candidate cells and one or more future time windows, as described above, based on one or more predicted radio link channel characteristics.

[0176] 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 in this document.

[0177] In the first aspect, one or more predicted radio link channel characteristics are generated at the UE.

[0178] In a second aspect, either alone or in combination with the first aspect, process 1100 includes transmitting an indication of one or more predicted radio link channel characteristics.

[0179] In the third aspect, the report is associated with beam fault detection, either alone or in combination with one or more of the first and second aspects.

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

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

[0182] In some respects, device 1200 can be configured to perform the functions described herein. Figures 5 to 9 One or more operations described herein. Additionally or alternatively, the apparatus 1200 may be configured to perform one or more processes described herein, such as Figure 10 The process is 1000. In some respects, Figure 12 The illustrated device 1200 and / or one or more components may include a combination Figure 2 One or more components of the described UE. Additionally or alternatively, Figure 12 One or more components shown can be combined Figure 2 Implementation within one or more of the described components. Additionally or alternatively, one or more components in the set of components 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.

[0183] The receiving component 1202 can receive communications from the device 1208, such as reference signals, control information, data communications, or combinations thereof. The receiving component 1202 can provide the received communications to one or more other components of the device 1200. In some aspects, the receiving component 1202 can perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding) on ​​the received communications, and can provide the processed signals to the one or more other components of the device 1200. In some aspects, the receiving component 1202 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.

[0184] Transmitting component 1204 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1208. In some aspects, one or more other components of device 1200 may generate communications and provide the generated communications to transmitting component 1204 for transmission to device 1208. In some aspects, transmitting component 1204 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 1208. In some aspects, transmitting component 1204 may include combinations of... Figure 2 The 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 1204 may co-located with the receive component 1202 in one or more transceivers.

[0185] The communication manager 1206 may support the operation of the receiving component 1202 and / or the transmitting component 1204. For example, the communication manager 1206 may receive information associated with configuring the receiving component 1202 to receive communication and / or the transmitting component 1204 to transmit communication. Additionally or alternatively, the communication manager 1206 may generate control information and / or provide control information to the receiving component 1202 and / or the transmitting component 1204 to control the receiving and / or transmitting of communication.

[0186] The receiving component 1202 can receive the configuration of one or more LTM candidate cells. The transmitting component 1204 can transmit a report indicating one or more predicted radio link qualities associated with one or more LTM candidate cells and one or more future time windows, based at least in part on one or more predicted radio link channel characteristics.

[0187] The communication manager 1206 can generate one or more predicted radio link channel characteristics.

[0188] The receiving component 1202 can receive an instruction for activating the artificial intelligence functionality associated with sending the report.

[0189] The receiving component 1202 can receive indications of one or more predicted radio link channel characteristics.

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

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

[0192] In some respects, device 1300 can be configured to perform the functions described herein. Figures 5 to 9 One or more operations described herein. Additionally or alternatively, the apparatus 1300 may be configured to perform one or more processes described herein, such as Figure 11 The process 1100. In some respects, Figure 13 The illustrated device 1300 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 13 One or more components shown can be combined Figure 2Implementation within one or more of the described components. Additionally or alternatively, one or more components in the set of components 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.

[0193] Receiver 1302 may receive communications from device 1308, such as reference signals, control information, data communications, or combinations thereof. Receiver 1302 may provide the received communications to one or more other components of device 1300. In some aspects, receiver 1302 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding) on ​​the received communications, and may provide the processed signals to the one or more other components of device 1300. In some aspects, receiver 1302 may include combinations of... Figure 2 The 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 1302 and / or transmitter component 1304 may include or be included in a network interface. The network interface may be configured to acquire and / or output signals for device 1300 via one or more communication links, such as backhaul links, midhaul links, and / or fronthaul links.

[0194] Transmitting component 1304 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1308. In some aspects, one or more other components of device 1300 may generate communications and provide the generated communications to transmitting component 1304 for transmission to device 1308. In some aspects, transmitting component 1304 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 1308. In some aspects, transmitting component 1304 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 1304 may co-located with the receive component 1302 in one or more transceivers.

[0195] The communication manager 1306 may support the operation of the receiving component 1302 and / or the transmitting component 1304. For example, the communication manager 1306 may receive information associated with configuring the receiving component 1302 to receive communication and / or the transmitting component 1304 to transmit communication. Additionally or alternatively, the communication manager 1306 may generate control information and / or provide control information to the receiving component 1302 and / or the transmitting component 1304 to control the receiving and / or transmitting of communication.

[0196] Transmitting component 1304 may transmit the configuration of one or more LTM candidate cells. Receiving component 1302 may receive reports indicating one or more predicted radio link qualities associated with one or more LTM candidate cells and one or more future time windows, based at least in part on one or more predicted radio link channel characteristics.

[0197] The transmitting component 1304 can transmit indications of one or more predicted radio link channel characteristics.

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

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

[0200] Aspect 1: A method for wireless communication performed by a UE, the method comprising: receiving configuration of one or more LTM candidate cells; and transmitting a report indicating one or more predicted radio link quality associated with the one or more LTM candidate cells and one or more future time windows, based at least in part on one or more predicted radio link channel characteristics.

[0201] Aspect 2: According to the method of aspect 1, the method further includes: generating the one or more predicted radio link channel characteristics.

[0202] Aspect 3: According to the method of aspect 2, the method further includes: receiving an instruction for activating artificial intelligence functionality associated with sending the report.

[0203] Aspect 4: The method according to any one of aspects 1 to 3, the method further comprising: receiving an indication of the one or more predicted radio link channel characteristics.

[0204] Aspect 5: The method according to any one of Aspects 1 to 4, wherein the one or more predicted radio link channel characteristics are at least partially based on one or more predictive RLM-RS.

[0205] Aspect 6: The method according to any one of Aspects 1 to 5, wherein the one or more future time windows are associated with one or more start times or one or more end times.

[0206] Aspect 7: The method according to any one of Aspects 1 to 6, wherein one or more asynchronous events are predicted to occur in the one or more future time windows for the one or more LTM candidate cells.

[0207] Aspect 8: The method according to any one of Aspects 1 to 7, wherein at least one of an asynchronous event or a synchronous event is predicted to occur in the one or more future time windows for the one or more LTM candidate cells.

[0208] Aspect 9: The method according to aspect 8, wherein an event is predicted to occur in the one or more future time windows for the one or more LTM candidate cells, and wherein the event is neither an asynchronous event nor a synchronous event.

[0209] Aspect 10: The method according to any one of Aspects 1 to 9, wherein the one or more predicted radio link quality includes one or more predicted hypothetical block error rates.

[0210] Aspect 11: The method according to any one of Aspects 1 to 10, wherein the one or more predicted radio link quality includes one or more predicted PDCCH hypothetical block error rates, wherein the one or more predicted PDCCH hypothetical block error rates are associated with one or more per LTM candidate cell thresholds, or wherein the report is associated with one or more frequencies outside the active downlink bandwidth portion.

[0211] Aspect 12: The method according to any one of Aspects 1 to 11, wherein sending the report comprises sending the report in response to one or more of the following: a desynchronization event predicted for one LTM candidate cell and one future time window of the one or more future time windows; a desynchronization event predicted for a Pcell associated with the UE, a PsCell associated with the UE, an active serving cell associated with the UE, or multiple active serving cells associated with the UE; or a synchronization event predicted for one LTM candidate cell or an LTM candidate cell that is not an active serving cell among the one or more LTM candidate cells.

[0212] Aspect 13: The method according to any one of Aspects 1 to 12, wherein sending the report comprises sending the report in response to one or more of the following: the number of out-of-synchronization events predicted for a Pcell associated with the UE, a PsCell associated with the UE, an active serving cell associated with the UE, or a plurality of active serving cells associated with the UE meets a first threshold; or the number of out-of-synchronization events predicted for at least one LTM candidate cell that is not an active serving cell among the one or more LTM candidate cells meets a second threshold.

[0213] Aspect 14: The method according to any one of Aspects 1 to 13, wherein the report is associated with beam fault detection.

[0214] Aspect 15: The method according to any one of Aspects 1 to 14, wherein the report is associated with conditional LTM.

[0215] Aspect 16: A method of wireless communication performed by a network node, the method comprising: receiving configuration of one or more LTM candidate cells; and receiving, at least in part, a report indicating one or more predicted radio link quality associated with the one or more LTM candidate cells and one or more future time windows, based on one or more predicted radio link channel characteristics.

[0216] Aspect 17: According to the method of aspect 16, the one or more predicted radio link channel characteristics are generated at the UE.

[0217] Aspect 18: The method according to any one of aspects 16 to 17, the method further comprising: transmitting an indication of the one or more predicted radio link channel characteristics.

[0218] Aspect 19: The method according to any one of Aspects 16 to 18, wherein the report is associated with beam fault detection.

[0219] Aspect 20: 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 19.

[0220] Aspect 21: 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 19.

[0221] Aspect 22: 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 19.

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

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

[0224] Aspect 25: 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 19.

[0225] Aspect 26: 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 19.

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

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

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

[0229] As used in this article, the phrase “at least one of” in a list of items refers to any combination of these items, including a single member. As an example, “at least one of the following: 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 with multiple of the same element (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).

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

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

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: One or more memory units; and One or more processors coupled to one or more memories, the one or more processors being capable of operating individually or in any combination to enable the device to: Receive the configuration of one or more lower-layer triggered mobility (LTM) candidate cells; as well as Reports indicating one or more predicted radio link qualities associated with the one or more LTM candidate cells and one or more future time windows are transmitted, based at least in part on one or more predicted radio link channel characteristics.

2. The apparatus of claim 1, wherein the one or more processors are further capable of operating individually or in any combination to cause the apparatus to: Generate the one or more predicted radio link channel characteristics.

3. The apparatus of claim 2, wherein the one or more processors are further capable of operating individually or in any combination to cause the apparatus to: Receive an instruction to activate the artificial intelligence functionality associated with sending the report.

4. The apparatus of claim 1, wherein the one or more processors are further capable of operating individually or in any combination to cause the apparatus to: Receive an indication of the one or more predicted radio link channel characteristics.

5. The apparatus of claim 1, wherein the one or more predicted radio link channel characteristics are based at least in part on one or more predictive radio link monitoring reference signals (RLM-RS).

6. The apparatus of claim 1, wherein the one or more future time windows are associated with one or more start times or one or more end times.

7. The apparatus of claim 1, wherein one or more asynchronous events are predicted to occur within one or more future time windows for the one or more LTM candidate cells.

8. The apparatus of claim 1, wherein at least one of an asynchronous event or a synchronous event is predicted to occur in the one or more future time windows for the one or more LTM candidate cells.

9. The apparatus of claim 8, wherein an event is predicted to occur in the one or more future time windows for the one or more LTM candidate cells, and wherein the event is neither an asynchronous event nor a synchronous event.

10. The apparatus of claim 1, wherein the one or more predicted radio link quality includes one or more predicted hypothetical block error rates.

11. The apparatus of claim 1, wherein the one or more predicted radio link quality includes one or more predicted physical downlink control channel (PDCCH) assumed block error rates. The one or more predicted PDCCH assumption block error rates are associated with one or more per-LTM candidate cell thresholds, or The report mentioned therein is associated with one or more frequencies outside the active downlink bandwidth portion.

12. The apparatus of claim 1, wherein the one or more processors operable to cause the apparatus to send the report are operable to cause the apparatus to send the report in response to one or more of the following: For the asynchronous events predicted by one LTM candidate cell and one future time window in the one or more future time windows, this refers to... For asynchronous events predicted by the primary cell (Pcell) associated with the UE, the primary and secondary cells (PsCell) associated with the UE, the active serving cell associated with the UE, or multiple active serving cells associated with the UE, or Synchronization events predicted for one of the one or more LTM candidate cells or for one of the one or more LTM candidate cells that is not an active serving cell.

13. The apparatus of claim 1, wherein the one or more processors operable to cause the apparatus to send the report are operable to cause the apparatus to send the report in response to one or more of the following: If the number of asynchronous events predicted for the primary cell (Pcell) associated with the UE, the primary and secondary cells (PsCell) associated with the UE, the active serving cell associated with the UE, or multiple active serving cells associated with the UE meets a first threshold, or The number of asynchronous events predicted for at least one LTM candidate cell that is not an active serving cell among the one or more LTM candidate cells meets the second threshold.

14. The apparatus of claim 1, wherein the report is associated with beam fault detection.

15. The apparatus of claim 1, wherein the report is associated with conditional LTM.

16. An apparatus for wireless communication at a network node, the apparatus comprising: One or more memory units; and One or more processors coupled to one or more memories, the one or more processors being capable of operating individually or in any combination to enable the device to: Send the configuration of one or more lower-layer triggered mobility (LTM) candidate cells; as well as Reports indicating one or more predicted radio link qualities associated with the one or more LTM candidate cells and one or more future time windows are received, based at least in part on one or more predicted radio link channel characteristics.

17. The apparatus of claim 16, wherein the one or more predicted radio link channel characteristics are generated at the user equipment (UE).

18. The apparatus of claim 16, wherein the one or more processors are further capable of operating individually or in any combination to cause the apparatus to: Send an indication of the one or more predicted radio link channel characteristics.

19. The apparatus of claim 16, wherein the report is associated with beam fault detection.

20. A method for wireless communication performed by a user equipment (UE), the method comprising: Receive the configuration of one or more lower-layer triggered mobility (LTM) candidate cells; as well as Reports indicating one or more predicted radio link qualities associated with the one or more LTM candidate cells and one or more future time windows are transmitted, based at least in part on one or more predicted radio link channel characteristics.

Images