Techniques for interruption latency requirements for predictive mobility

Abstract

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a user equipment (UE) can receive, from a network node, a handover command triggering a handover to a target cell associated with an unknown state. The UE can identify a handover interruption time associated with the target cell in accordance with one or more latency requirements associated with the target cell having a known state or a semi-known state based on one or more predictive mobility conditions being satisfied within a threshold time prior to receiving the handover command. The UE can transmit an uplink message to the target cell within the handover interruption time. Numerous other aspects are described.

Description

Technical Field

[0001] All aspects of this disclosure relate to wireless communication in general, and more particularly to techniques, apparatus and methods for addressing interruption delay requirements for predictive mobility. 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] These 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 made, 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 a method for wireless communication performed by a user equipment (UE). The method may include receiving from a network node a handover command that triggers a handover to a target cell associated with an unknown state. The method may include identifying a handover interruption time associated with the target cell based on one or more delay requirements associated with the target cell having a known or semi-known state, based on the satisfaction of one or more predictive mobility conditions within a threshold time prior to receiving the handover command. The method may include sending an uplink message to the target cell during the handover interruption time.

[0005] Some aspects described herein relate to a UE for wireless communication. The UE may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured to receive from a network node a handover command that triggers a handover to a target cell associated with an unknown state. The one or more processors may be configured to identify a handover interruption time associated with the target cell, based on one or more predictive mobility conditions satisfied within a threshold time prior to receiving the handover command, according to one or more delay requirements associated with the target cell having a known or semi-known state. The one or more processors may be configured to send an uplink message to the target cell during the handover interruption time.

[0006] 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 from a network node a handover command triggering a handover to a target cell associated with an unknown state. When executed by one or more processors of the UE, the set of instructions enables the UE to identify a handover interruption time associated with the target cell, based on one or more predictive mobility conditions satisfied within a threshold time prior to receiving the handover command, according to one or more delay requirements associated with the target cell having a known or semi-known state. When executed by one or more processors of the UE, the set of instructions enables the UE to send an uplink message to the target cell during the handover interruption time.

[0007] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for receiving from a network node a handover command triggered to a target cell associated with an unknown state. The apparatus may include components for identifying a handover interruption time associated with the target cell based on one or more delay requirements associated with the target cell having a known or semi-known state, based on the satisfaction of one or more predictive mobility conditions within a threshold time prior to receiving the handover command. The apparatus may include components for transmitting uplink messages to the target cell during the handover interruption time.

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

[0009] 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

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

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

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

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

[0014] Figure 4 This is a diagram illustrating an example of the handover process of first opening and then closing according to this disclosure.

[0015] Figures 5A to 5B This is a diagram illustrating an example of mobility (LTM) triggered by layer 1 (L1) and / or layer 2 (L2) according to this disclosure.

[0016] Figure 6 This is an illustration of an example of beam management based on artificial intelligence and / or machine learning (AI / ML) according to this disclosure.

[0017] Figures 7A to 7B This is a diagram illustrating an example of latency requirements associated with predictive mobility according to this disclosure.

[0018] Figure 8This is a flowchart illustrating an example procedure performed by a UE according to this disclosure.

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

[0020] 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 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 method of 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 of practice using those other structures and / or functionalities. Any aspect of this disclosure disclosed herein may be embodied by one or more elements of the claims.

[0021] 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 boxes, modules, components, circuits, steps, processes, or algorithms (collectively, “elements”). These elements may be implemented using hardware, software, or a combination of hardware and software. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole.

[0022] In some wireless networks, artificial intelligence or machine learning (AI / ML) models may be deployed at or on one or more wireless nodes (e.g., user equipment (UE) and / or network nodes) to generate one or more UE-side predictions that may be indicated in a prediction report transmitted to the network node and / or one or more network-side predictions that may be indicated in a prediction result indication transmitted to the UE. For example, intelligent principles or algorithms implemented by AI / ML technologies have been utilized and / or studied for various possible use cases, including beam management, energy saving, load balancing, coverage optimization, and / or mobility management. For instance, in some cases, AI / ML technologies have been used for downlink beam prediction, where measurements associated with a first set of beams are used to predict measurements for a second set of beams to achieve spatial and / or temporal downlink beam prediction. In some cases, AI / ML technologies can be used to predict beam measurements at the network and / or UE.

[0023] Furthermore, in some cases, beam measurements predicted using AI / ML techniques can be used to achieve AI / ML-assisted mobility, which may be referred to herein as predictive mobility, etc. For example, in a spatial prediction use case, the UE can obtain measurements for a first set of cross-cell (or inter-cell) synchronization signal blocks (SSBs), which are then used to predict measurements for a second set of cross-cell (or inter-cell) SSBs. The predicted measurements for the second set of cross-cell (or inter-cell) SSBs can be used to make mobility decisions, thereby reducing UE power consumption and / or measurement latency in the presence of a large number of cross-cell beams. In another example, in a timing prediction use case, the UE may obtain measurements for a first set of cross-cell (or inter-cell) SSBs, which are then used to predict a second set of measurements for cross-cell (or inter-cell) Channel State Information (CSI) Reference Signal (CSI-RS) beams or other narrow beams for future timing. The predicted second set of measurements for cross-cell (or inter-cell) CSI-RS beams or other narrow beams can be used to make mobility decisions and thereby reduce Layer 1 (L1) and / or Layer 2 (L2) triggered mobility (LTM) delays and / or avoid service interruptions (e.g., for inter-distributed cell (DU) handover and / or non-ideal backhaul).

[0024] However, when beam prediction is considered for a specific SSB of a target cell, even if a network node can trigger a handover or cell handover command based on the beam prediction result (e.g., via a Layer 3 (L3) mobility framework and / or an LTM framework), the UE may not have yet measured the SSB. In such cases, the target cell is typically associated with an "unknown" state (e.g., indicating that the target cell has not been measured) based on the old definition of known and unknown target cells, where the UE has not yet measured the SSB associated with the predicted measurement that triggered the handover to the target cell. The unknown state of the target cell typically results in a much longer outage delay compared to a target cell associated with a known state. For example, when the UE receives a handover command indicating a handover to the target cell, various standards and / or rules may specify that the UE must be prepared to begin sending Physical Random Access Channel (PRACH), Physical Uplink Control / Shared Channel (PUxCH), or Probe Reference Signal (SRS) to the target cell before the handover outage period expires. For example, a longer outage delay for a target cell associated with an unknown (e.g., unmeasured) state is typically defined as allowing multiple rounds of SSB measurements, enabling the UE to identify the appropriate SSB and / or preferred receive (Rx) beam for the target cell. However, when the handover decision is based on one or more predictions performed by the UE and / or network nodes, the outage delay associated with handover to a target cell associated with an unknown state can potentially be significantly reduced (e.g., because the SSB associated with the handover decision is identified based on measurements that have already been predicted).

[0025] Various aspects generally relate to techniques for allowing a target cell associated with a handover command to be associated with a known or semi-known state when the target cell is identified based on one or more beam predictions (e.g., predicted measurements for a beam associated with the target cell). For example, when the target cell is identified based on one or more predicted measurements for a beam associated with the target cell, the target cell may be associated with a known or semi-known state depending on the number of additional SSBs or other beam measurements required for the target cell. For example, in some aspects, the target cell associated with the handover command may be associated with a known or semi-known state if one or more predictive mobility conditions are met within a threshold time prior to the UE receiving the handover command from the network node. For example, in some aspects, one or more predictive mobility conditions may be met if the UE has transmitted a valid prediction report associated with the target cell or one or more SSBs associated with the target cell within a threshold time prior to the UE receiving the handover command from the network node, and / or if the UE has received a valid prediction result indication or one or more SSBs associated with the target cell within a threshold time prior to receiving the handover command from the network node, thereby indicating that the target cell may be associated with a known or semi-known state. Additionally or alternatively, the predictive mobility condition may be satisfied if the UE has not transmitted a valid measurement report about the target cell or one or more SSBs associated with the target cell within a threshold time prior to receiving the handover command from the network node, and / or if one or more SSBs measured from the target cell remain detectable during the handover delay (or handover interruption time).

[0026] Generally, when a (unmeasured) target cell is associated with a known or semi-known state based on satisfying predictive mobility conditions, one or more timeline constraints or delay requirements may have correspondingly defined values. For example, a target cell associated with a known state may be associated with a time relative to the time used to search for the target cell when the handover command is received, which has a value of 0 milliseconds (ms). Additionally or alternatively, a target cell associated with a semi-known state may be associated with a time relative to the time used to search for the target cell when the handover command is received, which has a value greater than 0 ms and less than the search time associated with a target cell associated with an unknown state. Furthermore, for a target cell associated with a semi-known state, the time required for fine-tuning time tracking and acquiring complete timing information associated with the target cell may be equal to the time required for fine-tuning time tracking and acquiring complete timing information for target cells associated with known and / or unknown states.

[0027] Specific aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. In some examples, by associating the target cell associated with the handover command with a known or semi-known state when identifying the target cell based on one or more beam predictions, handover interruption delay can be significantly reduced compared to the older definition where a target cell not previously measured by the UE is associated with a much longer handover interruption delay. For example, when identifying the target cell associated with the handover command based on one or more predicted beam measurements, the UE does not need to perform multiple rounds of SSB measurements for the target cell to identify the appropriate target SSB and / or preferred Rx beam for the target cell, because the appropriate target SSB and / or preferred Rx beam may have already been identified based on the predicted beam measurements. Furthermore, when identifying the target cell based on one or more predicted beam measurements obtained by the UE, a single Rx beam or a relatively small number of candidate Rx beams can be predicted based on the predicted beam measurements, thereby supporting shorter handover interruption times for target cells that meet one or more predictive mobility conditions. Additionally or alternatively, when identifying a target cell based on one or more predicted beam measurements obtained by a network node, the network node may signal a Type D quasi-co-located (QCL) source to the UE to assist in narrowing the range of candidate Rx beams. In this way, when identifying a target cell based on one or more predictive mobility conditions, associating the target cell with a known or semi-known state can significantly reduce handover delay and thereby improve UE and / or network performance.

[0028] 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).

[0029] With increasing demand for broadband access and the evolution of technologies supported by wireless communication networks, further technological improvements can be adopted in or implemented for 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. These 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, redcap UE functionality, industrial connectivity, multi-subscriber implementations, high-precision positioning, radio frequency (RF) sensing and / or AI / ML, and more. Such 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, etc. 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.

[0030] 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).

[0031] 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, 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 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 / NR RATs, 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.

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

[0033] 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).

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

[0035] 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 geographic 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 compliant with the O-RAN Alliance), 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.

[0036] Network nodes 110 of the 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 Radio Resource Control (RRC) functions, Packet Data Convergence Protocol (PDCP) functions, and / or Service Data Adaptation Protocol (SDAP) functions, etc. DUs may host one or more of the Radio Link Control (RLC) layer, 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, 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.

[0037] In some aspects, a single 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.

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

[0039] 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).

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

[0041] 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). A UE 120 may be configured with both an uplink BWP and a downlink BWP (where the uplink BWP and downlink BWP may be the same BWP or different BWPs). BWPs may be dynamically configured 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.

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

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

[0044] 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 device, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smartwatch, smart clothing, smart glasses, a smart wristband and / or smart jewelry (such as a smart ring or smart bracelet)), an entertainment device (e.g., a music device, a video device and / or a satellite radio), an extended reality (XR) device, a vehicle component or sensor, a smart meter or sensor, industrial manufacturing equipment, a Global Navigation Satellite System (GNSS) device (such as a Global Positioning System device or another type of positioning device), a UE function of a network node, and / or any other suitable device or function that can communicate via a wireless medium, or may be coupled to them.

[0045] UE 120 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.

[0046] 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 multiple 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.

[0047] 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 collectively referred to 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).

[0048] 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 lower cost compared to UEs 120 in the second category. UEs 120 in the second category may include mission-critical IoT devices, legacy UEs, baseline UEs, high-level UEs, advanced UEs, full-capability UEs, and / or premium UEs capable of ultra-reliable low-latency communication (URLLC), enhanced mobile broadband (eMBB), and / or precise positioning, etc., within the wireless communication network 100. UEs 120 in the third category may have intermediate-level complexity and / or capabilities (e.g., capabilities between UEs 120 in the first category and UEs 120 in the second category). 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.

[0049] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) can communicate directly with each other using sidelink communication (e.g., without communicating through a network node 110 acting as an intermediary). As an example, UE 120a can send data, control information, or other signaling directly to UE 120e as sidelink communication. This contrasts with, for example, UE 120a first sending data to network node 110 in UL communication, and then that network node sending data to UE 120e in DL communication. In various examples, UE 120 can 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.

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

[0051] 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).

[0052] In some aspects, UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may: receive from network node 110 a handover command that triggers handover to a target cell associated with an unknown state; identify a handover interruption time associated with the target cell based on one or more delay requirements associated with the target cell having a known or semi-known state, based on one or more predictive mobility conditions being met within a threshold time prior to receiving the handover command; and send an uplink message to the target cell during the handover interruption time. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

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

[0054] Figure 2 This is a diagram illustrating Example 200, which demonstrates communication between network node 110 and example UE 120 in a wireless network.

[0055] like Figure 2 As 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, and / or a scheduler 246, 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, performs aspects of the methods, processes, 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.

[0056] 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 2The 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.

[0057] 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 first set of processors and the second set of processors can be the same set of processors or can be 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 combined... 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.

[0058] 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 signal (CRS), demodulation reference signal (DMRS), or CSI-RS) and / or synchronization signals (e.g., primary synchronization signal (PSS) or secondary synchronization signal (SSS)).

[0059] The TX MIMO processor 216 can perform space processing (e.g., pre-decoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols where applicable, and can output a set of symbol streams (e.g., T A set of output symbol streams is provided to modem 232. For example, each output symbol stream may be provided to a corresponding modulator component (shown as MOD) of modem 232. Each modem 232 may 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 may further use the corresponding modulator component to process (e.g., convert to analog, amplify, filter, and / or upconvert) the output sample stream to obtain a time-domain downlink signal. Modems 232a to 232t may transmit the set of downlink signals (e.g., via a set of corresponding antennas 234) together. T (One downlink signal).

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

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

[0062] 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 to transmit and / or receive communication using RRC configuration (e.g., semi-static configuration), for example, to perform semi-persistent scheduling (SPS) or to configure configuration grant (CG) for UE 120.

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

[0064] 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 perform network control signaling, etc. Communication unit 244 may include transceivers and / or interfaces, such as network interfaces.

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

[0066] 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 receive the set of downlink signals (e.g., R Each received signal is provided to a set of modems 254. For example, each received signal may be provided to a corresponding demodulator component (shown as DEMOD) of modem 254. Each modem 254 may use the corresponding demodulator component to condition (e.g., filter, amplify, down-convert, and / or digitize) the received signal to obtain an input sample. Each modem 254 may use the corresponding demodulator component to further demodulate or process the input sample (e.g., for OFDM) to obtain a received symbol. MIMO detector 256 may obtain the received symbols from the set of modems 254, may perform MIMO detection on the received symbols where applicable, and may provide the detected symbols. Receiver processor 258 may process (e.g., decode) the detected symbols, may provide the decoded data for UE 120 to data sink 260 (which may include data pipelines, data queues, and / or applications executed on UE 120), and may provide the decoded control information and system information to controller / processor 280.

[0067] 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 Channel Quality Indicator (CQI) parameter, or a Transmit Power Control (TPC) parameter, etc. The control information may include indications of RSRP, RSSI, RSRQ, CQI, TPC, and / or another parameter. Control information can facilitate parameter selection and / or scheduling for UE 120 by network node 110.

[0068] Transmit processor 264 can generate reference symbols for one or more reference signals, such as uplink DMRS, uplink SRS, and / or another type of reference signal. Symbols from transmit processor 264 may 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 (where applicable) perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, and can provide an output symbol stream set (e.g., ...) to the assembly of modems 254. U Each output symbol stream may be provided to a corresponding modulator component (shown as MOD) of modem 254. Each modem 254 may 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 the corresponding modulator component to process (e.g., convert to analog, amplify, filter, and / or upconvert) the output sample stream to obtain an uplink signal.

[0069] Modems 254a to 254u can transmit uplink signal sets (e.g., via a set of corresponding antennas 252) R One uplink signal or U Uplink signals may include UCI communication, MAC-CE communication, RRC communication, or another type of uplink communication. Uplink signals may be transmitted on PUSCH, PUCCH, and / or another type of uplink channel. Uplink signals may carry one or more TBs of data. Sidelink data and control transmission (i.e., transmission directly between two or more UEs 120) may typically use 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).

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

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

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

[0073] 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).

[0074] In some respects, the controller / processor 280 may be a component of a processing system. A processing system can typically be a system or a series of machines or components that receive input and process it to produce output (which may be passed to other systems or components, such as UE 120). For example, the processing system of UE 120 may be a system that includes various other components or sub-components of UE 120.

[0075] The processing system of UE 120 can interface with one or more other components of UE 120, and can process information (such as input or signals) received from one or more other components, or can output information to one or more other components. For example, the chip or modem of UE 120 may include: a processing system, a first interface for receiving or acquiring information, and a second interface for outputting, transmitting, or providing information. In some examples, the first interface may be an interface between the processing system of the chip or modem and a receiver, allowing UE 120 to receive information or signal input and to pass information to the processing system. In some examples, the second interface may be an interface between the processing system of the chip or modem and a transmitter, allowing UE 120 to transmit information output from the chip or modem. Those skilled in the art will readily recognize that the second interface may also acquire or receive information or signal input, and the first interface may also output, transmit, or provide information.

[0076] In some respects, the controller / processor 240 may be a component of a processing system. A processing system can typically be a system or a series of machines or components that receive input and process it to produce output (which may be passed to other systems or components, such as network node 110). For example, the processing system of network node 110 may be a system that includes various other components or sub-components of network node 110.

[0077] The processing system of network node 110 can interface with one or more other components of network node 110, and can process information (such as input or signals) received from one or more other components, or can output information to one or more other components. For example, the chip or modem of network node 110 may include: a processing system, a first interface for receiving or acquiring information, and a second interface for outputting, transmitting, or providing information. In some examples, the first interface may be an interface between the processing system of the chip or modem and a receiver, allowing network node 110 to receive information or signal input and to pass information to the processing system. In some examples, the second interface may be an interface between the processing system of the chip or modem and a transmitter, allowing network node 110 to transmit information output from the chip or modem. Those skilled in the art will readily recognize that the second interface may also acquire or receive information or signal input, and the first interface may also output, transmit, or provide information.

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

[0079] Figure 3 This is an illustration of an example decomposed base station architecture 300 according to the present disclosure. One or more components of the example decomposed base station architecture 300 may be, may include, or may be included in one or more network nodes (such as one or more network nodes 110). The decomposed 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 decomposed 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 330s via a corresponding midhaul link (such as via an F1 interface). Each DU 330 may communicate with one or more RU 340s via a corresponding fronthaul link. Each RU 340 may communicate with one or more UE 120s via a corresponding RF access link. In some deployments, a UE 120 may be served simultaneously by multiple RU 340s.

[0080] 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 be coupled to one or more interfaces for receiving or transmitting signals, such as data or information, via wired or wireless transmission media.

[0081] In some respects, the CU 310 can be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 310 can be 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.

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

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

[0084] 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).

[0085] 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 or perform one or more operations associated with interruption latency requirements for predictive mobility, 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 or perform one or more operations associated with interruption latency requirements for predictive mobility, as described in more detail elsewhere herein. Figure 2 Any other component (or combination of components), CU 310, DU 330, or RU 340 may (alone or in combination with one or more other processors) perform or direct, for example Figure 8 The operation of process 800 or other processes as described herein. 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 instruction sets (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 instruction set 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 8The process 800 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.

[0086] In some aspects, UE 120 includes: components for receiving from network node 110 a handover command triggered to a target cell associated with an unknown state; components for identifying a handover interruption time associated with the target cell based on one or more delay requirements associated with the target cell having a known or semi-known state, based on satisfying one or more predictive mobility conditions within a threshold time prior to receiving the handover command; and / or components for transmitting an uplink message to the target cell during the handover interruption time. Components for UE 120 to perform the operations described herein may include, for example, one or more of the following: communication manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller / processor 280, or memory 282.

[0087] Figure 4 This is a diagram illustrating Example 400 of the MBB (Mobile-Blocked-Blocked) handover process according to this disclosure.

[0088] like Figure 4 As shown, the MBB handover process may involve UE 405, source network node 410, target network node 415, User Plane Function (UPF) device 420, and Access and Mobility Management Function (AMF) device 425. In some examples, actions described as being performed by network nodes may be performed by multiple network nodes. For example, configuration actions and / or core network communication actions may be performed by a first network node (e.g., CU or DU), and radio communication actions may be performed by a second network node (e.g., DU or RU). UE 405 may correspond to UE 120 as described elsewhere herein. Source network node 410 and / or target network node 415 may correspond to network node 110 as described elsewhere herein. UE 405 and source network node 410 may be connected via a serving cell or source cell (e.g., may have an RRC connection), and UE 405 may undergo a handover via the target cell to target network node 415. UPF device 420 and / or AMF device 425 may be located within the core network. Source network node 410 and target network node 415 can communicate with the core network for mobility support and user plane functions.

[0089] like Figure 4As shown, the MBB handover process may include a handover preparation phase 430, a handover execution phase 435, and a handover completion phase 440. During the handover preparation phase 430, the UE 405 may report measurements that prepare the source network node 410 and / or the target network node 415 for handover and trigger the execution of the handover. During the handover execution phase 435, the UE 405 may perform the handover by executing a random access procedure with the target network node 415 and establishing an RRC connection with the target network node 415. During the handover completion phase 440, the source network node 410 may forward one or more stored communications associated with the UE 405 to the target network node 415, and the UE 405 may be released from the connection with the source network node 410.

[0090] As indicated by reference numeral 445, during the handover preparation phase 430, UE 405 may perform one or more measurements and may send a measurement report to source network node 410 based at least in part on these measurements (e.g., serving cell measurements and / or neighboring cell measurements). The measurement report may indicate, for example (e.g., for the serving cell and / or one or more neighboring cells), RSRP parameters, RSRQ parameters, RSSI parameters, and / or signal-to-interference-plus-noise ratio (SINR) parameters. Source network node 410 may use the measurement report to determine whether to trigger handover to target network node 415. For example, if one or more measurements meet certain conditions, source network node 410 may trigger handover of UE 405 to target network node 415.

[0091] As indicated by reference numeral 450, during the handover preparation phase 430, the source network node 410 and the target network node 415 may communicate with each other to prepare for the handover of UE 405. As part of the handover preparation, the source network node 410 may send a handover request to the target network node 415 to instruct the target network node 415 to prepare for the handover. The source network node 410 may communicate to the target network node 415 the RRC context information associated with UE 405 and / or the configuration information associated with UE 405. The target network node 415 may prepare for the handover by reserving resources for UE 405. After reserving resources, the target network node 415 may send an acknowledgment (ACK) to the source network node 410 in response to the handover request.

[0092] As indicated by reference numeral 455, during the handover preparation phase 430, the source network node 410 may send an RRC reconfiguration message to the UE 405. The RRC reconfiguration message may include a handover command instructing the UE 405 to perform a handover procedure from the source network node 410 to the target network node 415. The handover command may include information associated with the target network node 415, such as the assignment of a random access channel (RACH) preamble for accessing the target network node 415. Reception of the RRC reconfiguration message including the handover command by the UE 405 may trigger the start of the handover execution phase 435.

[0093] As indicated by reference numeral 460, during the handover execution phase 435, UE 405 may perform the handover by performing a random access procedure with target network node 415 (e.g., including synchronization with target network node 415) while continuing to communicate with source network node 410. For example, when UE 405 performs the random access procedure with target network node 415, UE 405 may send uplink data, uplink control information, and / or uplink reference signals (e.g., SRS) to source network node 410, and / or may receive downlink data, DCI, and / or downlink reference signals from source network node 410.

[0094] As indicated by reference numeral 465, during the handover execution phase 435, after successfully establishing a connection with the target network node 415 (e.g., via a random access procedure), the UE 405 may send an RRC reconfiguration complete message to the target network node 415. Reception of the RRC reconfiguration message by the target network node 415 may trigger the start of the handover completion phase 440.

[0095] As indicated by reference numeral 470, during the handover completion phase 440, the source network node 410 and the target network node 415 may communicate with each other to prepare for releasing the connection between the source network node 410 and the UE 405. In some aspects, such as after receiving an RRC reconfiguration message from the UE 405, the target network node 415 may determine that the connection between the source network node 410 and the UE 405 is to be released. In this case, the target network node 415 may send a handover connection setup complete message to the source network node 410. The handover connection setup complete message may cause the source network node 410 to stop sending data to the UE 405 and / or stop receiving data from the UE 405. Additionally or alternatively, the handover connection setup complete message may cause the source network node 410 to forward communications associated with the UE 405 to the target network node 415 and / or notify the target network node 415 of the status of one or more communications with the UE 405. For example, source network node 410 may forward buffered downlink communications (e.g., downlink data) and / or uplink communications (e.g., uplink data) received from UE 405 to target network node 415. Additionally or alternatively, source network node 410 may notify target network node 415 of the PDCP status associated with UE 405 and / or the sequence number to be used for downlink communication with UE 405.

[0096] As indicated by reference numeral 475, during the handover completion phase 440, the target network node 415 may send an RRC reconfiguration message to the UE 405 to instruct the UE 405 to release its connection with the source network node 410. Upon receiving the instruction to release the connection with the source network node 410, the UE 405 may cease communication with the source network node 410. For example, the UE 405 may avoid sending uplink communication to the source network node 410 and / or may avoid monitoring downlink communication from the source network node 410.

[0097] As indicated by reference numeral 480, during the handover completion phase 440, the UE may send an RRC reconfiguration completion message to the target network node 415 to indicate that the connection between the source network node 410 and the UE 405 is being released or has been released.

[0098] As shown by reference numeral 485, during the handover completion phase 440, the target network node 415, UPF device 420, and / or AMF device 425 can communicate to switch the user plane path of UE 405 from the source network node 410 to the target network node 415. Before the user plane path handover, downlink communication for UE 405 can be routed to the source network node 410 via the core network. After the user plane path handover, downlink communication for UE 405 can be routed to the target network node 415 via the core network. Upon completion of the user plane path handover, AMF device 425 can send an end marker message to the source network node 410 to signal the completion of the user plane path handover. As shown by reference numeral 490, the target network node 415 and the source network node 410 can communicate to release the source network node 410.

[0099] As part of the MBB handover process, UE 405 may maintain simultaneous connections with both the source network node 410 and the target network node 415 during time period 495. Time period 495 may begin at the start of handover execution phase 435 (e.g., when UE 405 receives a handover command from source network node 410) while UE 405 performs a random access procedure with target network node 415. Time period 495 may end when the connection between UE 405 and source network node 410 is released (e.g., when UE 405 receives an instruction to release source network node 410 from target network node 415). By maintaining simultaneous connections with both source network node 410 and target network node 415, the handover process can be performed with zero or minimal communication interruptions, thereby reducing latency.

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

[0101] Figures 5A to 5B These are illustrations of examples 500, 550 of mobility triggered according to layer 1 (L1) and / or layer 2 (L2) of this disclosure.

[0102] In wireless networks, UEs and network nodes can communicate on access links using directional links (e.g., using high-dimensional phased arrays) to benefit from beamforming gain and / or maintain acceptable communication quality. However, directional links typically require fine alignment of transmit and receive beams, which can be achieved through a set of operations known as beam management and / or beam selection. Furthermore, wireless networks may support multi-beam operation at relatively high carrier frequencies (e.g., within FR2 or FR4), which can be associated with more severe propagation conditions compared to relatively lower carrier frequencies. For example, signals propagating in millimeter-wave bands may suffer increased path loss and severe channel intermittency compared to sub-6 GHz bands (e.g., FR1), and / or may be obstructed by objects common in the UE's surrounding environment (e.g., buildings, trees, and / or the user's body, etc.). Therefore, beam management is particularly important for multi-beam operation at relatively high carrier frequencies.

[0103] One possible enhancement to multi-beam operation at higher carrier frequencies is to facilitate efficient (e.g., low latency and low overhead) downlink and / or uplink beam management to support higher L1 / L2-centric inter-cell mobility, which may be referred to herein as L1 / L2-triggered mobility (LTM). Therefore, one objective of LTM is to enable the UE to perform cell handover via dynamic control signaling at lower layers (e.g., DCI for L1 signaling or MAC-CE for L2 signaling) instead of semi-static Layer 3 (L3) RRC signaling, thereby reducing latency, reducing overhead, and / or otherwise increasing the efficiency of cell handover.

[0104] For example, Figure 5A Example 500 illustrates an LTM technology, which may be referred to as beam-based inter-cell mobility, dynamic point selection-based inter-cell mobility, and / or non-serving cell-based inter-cell mobility, etc. As described in further detail herein, a first LTM technology enables network nodes to use L1 signaling (e.g., DCI) or L2 signaling (e.g., MAC-CE) to instruct the UE to use beams from the serving cell or a non-serving cell for communication on the access link. For example, in a radio network that does not support LTM (e.g., cell handover is triggered only by L3 handover), beam selection for control information and for data is typically limited to beams within the Physical Cell Identifier (PCI) associated with the serving cell. In contrast, in a radio network that supports the first LTM technology (e.g., as...), beam selection is significantly different. Figure 5A As shown, the beam selection for control and data can be extended to include any beam within the serving cell 510 or one or more non-serving neighboring cells 515 for LTM configuration.

[0105] For example, in Figure 5AIn the first LTM technology shown, the UE can be configured with a single serving cell 510 and can be further configured with a set of neighboring cells including one or more non-serving cells 515 configured for LTM. Typically, the serving cell 510 and non-serving cells 515 configured for LTM can be associated with a common CU and a common DU, or the serving cell 510 and non-serving cells 515 configured for LTM can be associated with a common CU and different DUs. In some aspects, as indicated by reference numeral 520, a network node can use L1 / L2 signaling (e.g., DCI or MAC-CE) to trigger the UE's LTM, the L1 / L2 signaling indicating that the selected Transmit Configuration Indication (TCI) state and the reference signal (e.g., Synchronization Signal Block (SSB)) associated with the PCI are in QCL. For example, in Figure 5A In this context, the UE can use PCI associated with the serving cell 510 (e.g., in...). Figure 5A The SSB (shown as PCI1) is in the TCI state of QCL to communicate with serving cell 510, and L1 / L2 signaling can instruct the UE to switch to using the PCI associated with the non-serving neighboring cell 515 (e.g., in...). Figure 5A The SSB (shown as PCI 2) communicates in the TCI state of QCL to trigger inter-cell mobility. Therefore, in the first LTM technique, network nodes (e.g., controlling the common CU of serving cell 510 and non-serving neighboring cell 515) can use L1 / L2 signaling to select a beam from serving cell 510 or non-serving neighboring cell 515 to serve the UE.

[0106] In this manner, compared to limiting L1 / L2 beam selection to beams within serving cell 510, the first LTM technology is more robust against obstruction and provides more opportunities for higher-rank spatial multiplexing across different cells. However, the first LTM technology cannot support changing the UE's specific cell (SpCell), where the SpCell can be a primary cell (PCell) or a primary-secondary cell (PSCell). Instead, in the first LTM technology, triggering SpCell changes is performed via legacy L3 handover using RRC signaling. In this respect, the first LTM technology is associated with the limitation that when the UE is within the coverage area of ​​serving cell 510, L1 / L2 signaling can only be used to indicate beams from serving cell 510 or configured neighboring cells 515 (e.g., because L1 / L2 signaling cannot be used to change PCell or PSCell). Therefore, Figure 5BExample 550 illustrates a second LTM technique, which may be referred to as inter-cell mobility based on serving cell, etc. As described in further detail herein, the second LTM technique enables network nodes to use L1 / L2 signaling (e.g., DCI or MAC-CE) to indicate control information associated with an active set of cells and / or a deactivated set of cells and / or to indicate changes to SpCells within the active set of cells.

[0107] For example, such as Figure 5B As shown, the second LTM technology can use a mechanism similar to carrier aggregation to implement LTM, except that different cells configured for LTM can operate on the same carrier frequency. For example... Figure 5B As shown, a network node can configure cell set 560 for LTM (e.g., using RRC signaling). As further shown, the active cell set 565 may include one or more cells in the configured cell set 560 that are activated and ready for data and / or control transfer. Therefore, in the second LTM technique, the deactivated cell set may include one or more cells included in the LTM-configured cell set 560 but not in the active cell set 565. However, using L1 / L2 signaling, cells included in the deactivated cell set can be easily activated and thus added to the active cell set 565. Therefore, as indicated by reference numeral 570, L1 / L2 signaling can be used for mobility management of the active cell set 565. For example, in some aspects, L1 / L2 signaling can be used to activate cells within the configured cell set 560 (e.g., add cells to the active cell set 565), deactivate cells in the active cell set 565, and / or select beams within cells included in the active cell set 565. In this way, the second LTM technology can use L1 / L2 signaling (e.g., using beam management technology) to achieve seamless mobility between cells included in the active cell set 565.

[0108] Furthermore, as indicated by reference numeral 575, the second LTM technology enables the use of L1 / L2 signaling to set or change the SpCell (e.g., PCell or PSCell) of cells included in the active cell set 565. Additionally or alternatively, when a cell to become a new SpCell is in a deactivated cell set (e.g., included in the LTM-configured cell set 560 but not in the active cell set 565), L1 / L2 signaling can be used to move the cell from the deactivated cell set to the active cell set 565 before additional L1 / L2 signaling is used to set the cell as the new SpCell. However, in the second LTM technology, L3 handover (e.g., using RRC signaling) is used to change the SpCell when a new SpCell is not included in the LTM-configured cell set 560. In such cases, the RRC signaling associated with the L3 handover can be used to update the cells included in the LTM-configured cell set 560. Therefore, LTM can provide more efficient cell handover to support multi-beam operation, thereby achieving lower latency and reduced overhead by changing the beam that the UE uses to communicate on the access link using L1 signaling (e.g., DCI) and / or L2 signaling (e.g., MAC-CE) instead of L3 signaling (e.g., RRC).

[0109] As indicated above, Figures 5A to 5B This is provided as an example. Other examples may be provided in conjunction with [the relevant information]. Figures 5A to 5B The descriptions are different.

[0110] Figure 6 This is a diagram illustrating example 600 of AI / ML-based beam management according to this disclosure. Figure 6 As shown, AI / ML model 610 can be deployed at or on a wireless node, which may correspond to UE 120 and / or network node 110 as described elsewhere herein. For example, a model inference host can be deployed at or on UE 120 to generate one or more UE-side predictions that may be indicated in a prediction report transmitted to the network node, or a model inference host can be deployed at or on network node 110 to generate one or more network-side predictions that may be indicated in a prediction result indication transmitted to the UE. In some aspects, as described herein, AI / ML model 610 enables a wireless node to determine one or more inferences or predictions based on data input to AI / ML model 610.

[0111] For example, as indicated by reference numeral 615, the input to AI / ML model 610 may include measurements associated with a first set of beams. For example, network node 110 may transmit one or more signals using a corresponding beam from the first set of beams. UE 120 may perform measurements of the first set of beams (e.g., L1-RSRP measurement, L1-SINR measurement, L3-RSRP measurement, L3-SINR measurement, or other suitable measurements) to obtain a first set of measurements. For example, each beam from the first set of beams may be associated with one or more measurements performed by UE 120. UE 120 may input the first set of measurements (e.g., L1 / RSRP / L1-SINR measurements and / or L3-RSRP / L3-SINR measurements) together with information associated with the first set of beams and / or a second set of beams (such as beam orientation (e.g., spatial orientation), beamwidth, beam shape, and / or other characteristics of the corresponding beams from the first set of beams and / or the second set of beams) into AI / ML model 610.

[0112] As indicated by reference numeral 620, the AI / ML model 610 can output one or more predictions. These predictions may include predicted measurements associated with a second set of beams (e.g., predicted L1-RSRP / L1-SINR measurements and / or L3-RSRP / L3-SINR measurements). This reduces the number of beam measurements performed by the UE 120, thereby converting the power of the UE 120 and / or network resources of all beams included in the first and second sets of beams that would otherwise be used for measurement. This type of prediction may be referred to as codebook-based spatial domain selection or prediction.

[0113] As another example, the output of AI / ML model 610 may include the pointing, departure angle (AoD), and / or arrival angle (AoA) of beams included in a second set of beams. This type of prediction may be referred to as non-codebook-based spatial domain selection or prediction. As another example, multiple measurement reports or values ​​collected at different time points may be input into AI / ML model 610. This allows AI / ML model 610 to output codebook-based and / or non-codebook-based predictions for beam measurements, AoD, and / or AoA, etc., at future times. As described herein, the output of AI / ML model 610 can facilitate initial access procedures, secondary cell group (SCG) setup procedures, beam refinement procedures (e.g., P2 beam management procedures or P3 beam management procedures), link quality or interference adaptation procedures, beam failure and / or beam blocking prediction, and / or radio link failure prediction, etc.

[0114] In some examples, the first set of beams may be referred to as set B beams, and the second set of beams may be referred to as set A beams. In some examples, the first set of beams (e.g., set B beams) may be a subset of the second set of beams (e.g., set A beams). In some other examples, the first set of beams and the second set of beams may be different beams and / or may be mutually exclusive sets. For example, the first set of beams (e.g., set B beams) may include wide beams (e.g., SSB, unrefined beams, or other beams with beamwidths that satisfy a first threshold), and the second set of beams (e.g., set A beams) may include narrow beams (e.g., CSI-RS beams, refined beams, or other beamwidths that satisfy a second threshold). In one example, AI / ML model 610 can be used to perform spatial domain downlink beam prediction for beams included in set A beams based on measurements of beams included in set B beams. As another example, AI / ML model 610 can be used to perform temporal downlink beam prediction for beams included in set A based on historical measurements of beams included in set B. When AI / ML model 610 is used to perform temporal downlink beam prediction, set A beams may be the same as set B beams (e.g., for purely temporal beam prediction), or set A beams may be different from set B beams (e.g., with or without overlap to achieve spatial and temporal beam prediction). Generally, as described herein, AI / ML model 610 can be used for spatial and / or temporal beam prediction at network node 110 or UE 120 and can support single-cell scenarios.

[0115] Furthermore, in some cases, beam measurements predicted using AI / ML techniques can be used to achieve AI / ML-assisted mobility, which may be referred to herein as predictive mobility, etc. For example, in the LTM spatial prediction use case, the UE can obtain measurements (e.g., L1-RSRP measurements and / or L1-SINR measurements) for a first set of cross-cell (or inter-cell) SSBs, which can then be used to predict L1-RSRP measurements, L1-SINR measurements, and / or other suitable measurements for a second set of cross-cell (or inter-cell) SSBs. In such cases, the predicted measurements for the second set of cross-cell (or inter-cell) SSBs can be used to make mobility decisions, thereby reducing UE power consumption and / or measurement latency in the presence of a large number of cross-cell beams. In another example, in the LTM timing prediction use case, the UE can obtain measurements for a first set of cross-cell (or inter-cell) SSBs (e.g., L1-RSRP measurements, L1-SINR measurements, and / or other suitable measurements), which can then be used to predict a second set of measurements for cross-cell (or inter-cell) CSI-RS beams or other narrow beams for future timing. In such cases, the predicted second set of measurements for cross-cell (or inter-cell) CSI-RS beams or other narrow beams can be used to make mobility decisions (e.g., considering one or more triggering conditions for conditional LTM based on UE-side timing beam prediction results) and reduce LTM latency and / or avoid service interruptions (e.g., for inter-DU handover and / or non-ideal backhaul).

[0116] However, when beam prediction is considered for a specific SSB of a target cell, even if a network node can trigger a handover or cell handover command based on the beam prediction result (e.g., via the L3 mobility framework and / or LTM framework), the UE may not have yet measured the SSB. In such cases, the target cell is typically associated with an "unknown" state (e.g., indicating a target cell that has not yet been measured) based on the old definition of known and unknown target cells, where the UE has not yet measured the SSB associated with the predicted measurement that triggered the handover to the target cell. The unknown state of the target cell typically results in a much longer outage delay compared to a target cell associated with a known state. For example, when the UE receives an RRC message indicating a handover to the target cell in the L3-based mobility framework (e.g., as referenced above) Figure 4 As described, various wireless communication standards and / or rules typically specify that the UE needs to be ready after the end of the last transmission time interval (TTI) containing the RRC-based handover command. handover Within ms, a new uplink PRACH is sent to the target cell, where D handoverIt has a value equal to the applicable RRC process delay plus the handover interruption time (e.g., as defined in one or more clauses of 3GPP Technical Specification 38.331).

[0117] Therefore, in an L3-based mobility framework, the handover interruption time is typically defined as the time between the end of the last TTI (Time Interruption) containing an RRC-based handover command on the PDSCH associated with the source cell and the time when the UE begins sending a new PRACH to the target cell. For example, when the UE receives an L3 (e.g., RRC) message containing an intra-frequency or inter-frequency handover command, the handover interruption time is subject to latency requirements, and thus the handover interruption time cannot exceed T... interrupt ,in .

[0118] In the above expression defining the maximum handover interruption time, T search This is the time required to search for the target cell when the UE receives a handover command. If the target cell is associated with a "known" state (e.g., a cell that the UE has already measured), then T... search It has a value of 0ms. Alternatively, if the target cell is associated with a cell in an "unknown" (e.g., unmeasured) frequency range, and the target cell is associated with a measurement Es / Iot equal to or greater than -2 dB, then T search = N T rs ms. Alternatively, if the target cell is associated with a cell at an unknown frequency, and the target cell Es / Iot is equal to or greater than -2dB, then T search = N 3 T rs ms. In either case, regardless of whether discontinuous reception (DRX) is being used by the UE, T search Both can be based on the search time for non-DRX target cells. Furthermore, in determining T... search When the value is , Es / Iot is the ratio of Es (the received energy per resource element (RE) at the UE's antenna connector) to Iot (the received power spectral density of total noise and interference for a specific RE, measured at the UE's antenna connector). N Corresponding to the number of cycles required to synchronize the Rx beam (e.g., where N It has a value of 8 when the target cell is in FR2-1, or a value of 12 when the target cell is in FR2-2), and T rsThis refers to the SMTC periodicity of the target cell when the UE has been provided with an SSB Measurement Timing Timing (SMTC) configuration for the target cell in the handover command, or when the UE has not been provided with an SMTC configuration for the target cell in the handover command, and the target cell has the same SSB frequency and subcarrier spacing. measObjectNR The SMTC is configured in the parameters. If configured by the master node (MN) and slave node (SN). measObjectNR If the parameters have different SMTCs, then T rs This refers to the periodicity of an SMTC within an SMTC, which depends on the specific implementation for the UE. If the UE is not provided with an SMTC configuration or measurement target on the target frequency, then, assuming an SSB transmission period of 5ms, T... rs The value is 5ms, or if the SSB transmission period is not 5ms, there is no corresponding delay requirement.

[0119] Furthermore, in the above expression defining the maximum handover interruption time, T IU The interrupt uncertainty is the timing of acquiring the first available PRACH opportunity in the new target cell, where T IU It can have a value up to the sum of the SSB-PRACH timing correlation period and 10ms, where the SSB-PRACH timing correlation period is defined in one or more wireless communication standards. Furthermore, T processing This is the time used for UE processing, which can be as high as 20ms, T Δ It is the time used for fine-grained time tracking and acquiring complete timing information of the target cell (e.g., where T is used for both known and unknown target cells). Δ =T rs ), and T margin This is the time used for SSB post-processing, which can have values ​​up to 2ms. Typically, for L3-based mobility in FR2, the target cell associated with the handover command is associated with a known state if the UE has transmitted a valid measurement report for the target cell during the last 5 seconds before receiving the handover command, the SSB measured from the target cell remains detectable according to one or more cell identifier conditions during the last 5 seconds before receiving the handover command, and / or the SSB measured from the target cell remains detectable during the handover delay according to one or more cell identifier conditions. Otherwise, if none of these conditions are met, the target cell is associated with an unknown state.

[0120] Furthermore, although there are no specific rules or standards regarding handover delays and / or handover interruption times for LTM versus L3-based mobility, it is generally expected that LTM will reuse existing definitions for L3-based mobility. However, while L3-based mobility measurements transmitted by the UE typically include L3-RSRP measurements and / or L3-SINR measurements reported via RRC signaling, LTM measurements transmitted by the UE may include L3-RSRP measurements and / or L3-SINR measurements reported by the UE via CSI reporting regarding one or more SSBs associated with the target cell. Additionally, in LTM, sending a PRACH to the target cell may be unnecessary because timing advance (TA) acquisition of the target cell can be performed via PDCCH ordered PRACH before the UE receives the LTM cell handover (or handover) command. In such cases, the TA is already valid at the UE, and the UE can directly send PUxCH and / or SRS to the target cell without first sending a PRACH. Therefore, although the interruption time for L3-based mobility is generally defined as the time between the end of the last TTI containing the RRC (handover) command and the time when the UE begins to send a new PRACH to the target cell, the interruption time for LTM can be defined as the time between the end of the last TTI containing the L1 / L2 handover command and the time when the UE begins to send PUxCH and / or SRS to the target cell.

[0121] However, when beam prediction is considered for handover related to a specific SSB of a target cell, even if the network node can trigger a handover or cell handover command based on the beam prediction results (e.g., via the L3 mobility framework and / or LTM framework), the UE may not have yet measured that SSB. For example, if beam prediction is performed by the UE, the UE may report the associated prediction results to the network node (e.g., predicted L1-RSRP / L1-SINR measurements for the SSB or an SSB that is one of the best beams among multiple candidate SSBs). In this case, the network node is also aware that these results are based on one or more UE predictions obtained without the UE actually measuring the SSB. Alternatively, if beam prediction is performed at the network node, the beam prediction may be based on measurements reported by the UE regarding one or more SSBs not associated with the target cell associated with the handover command, which can be widely understood between the network node and the UE when signaling the cell handover or handover command to the UE.

[0122] In such cases, where the UE has not yet measured the SSB associated with the predicted measurement that triggers the handover to the target cell, the target cell is typically associated with an "unknown" state (e.g., indicating a target cell that has not yet been measured) based on the old definition of known and unknown target cells. The unknown state of the target cell typically results in a much longer outage delay compared to a target cell associated with a known state. For example, as described above, when the UE receives a handover command indicating a handover to the target cell, various standards and / or rules may specify that the UE must be prepared to begin sending PRACH, PUxCH, or SRS to the target cell before the handover outage period expires, where the handover outage period may be relatively long (causing a longer handover delay) for a target cell associated with an unknown state, and relatively short (causing a shorter handover delay) for a target cell associated with a known state. For example, a longer outage delay for a target cell associated with an unknown (e.g., unmeasured) state is typically defined as allowing multiple rounds of SSB measurement so that the UE can identify the appropriate SSB and / or preferred Rx beam for the target cell. However, when the handover decision is based on one or more predictions performed by the UE and / or network nodes, the downtime associated with handover to a target cell with an unknown state can potentially be significantly reduced (e.g., because the SSB associated with the handover decision is identified based on already predicted measurements). For example, when the handover command to the target cell is based on UE beam prediction, a single Rx beam or several candidate Rx beams may also be predicted when predicting L1-RSRP measurements and / or L1-SINR measurements. For example, Rx beam prediction may be performed by the UE using one or more AI / ML models, and / or the candidate Rx beams may be the Rx beam used to receive the strongest SSB in the measured cell, plus one or more adjacent Rx beams, sub-Rx beams, and / or parent Rx beams associated with the Rx beam used to receive the strongest SSB. Additionally or alternatively, when the handover command to the target cell is based on beam prediction performed by the network node, the network node may signal a type D QCL source to assist in narrowing the range of candidate Rx beams. For example, a type D QCL source can be the strongest SSB measured and reported by the UE within the most recently reported L1-RSRP feedback, and then the UE can optionally identify one or more candidate Rx beams as one or more Rx beams and / or one or more adjacent Rx beams, sub-Rx beams and / or parent Rx beams that receive such a strongest SSB.

[0123] Therefore, as described in further detail herein, various aspects generally relate to techniques for allowing a target cell associated with a handover command to be associated with a known or semi-known state when the target cell is identified based on one or more beam predictions (e.g., predicted measurements for a beam associated with the target cell). For example, when the target cell is identified based on one or more predicted measurements for a beam associated with the target cell, the target cell may be associated with a known or semi-known state depending on the number of additional SSBs or other beam measurements required for the target cell. For example, in some aspects, the target cell associated with the handover command may be associated with a known or semi-known state if one or more predictive mobility conditions are met within a threshold time prior to the UE receiving the handover command from the network node. For example, in some aspects, one or more predictive mobility conditions may be met if the UE has transmitted a valid prediction report associated with the target cell or one or more SSBs associated with the target cell within a threshold time prior to the UE receiving the handover command from the network node, and / or if the UE has received a valid prediction result indication or one or more SSBs associated with the target cell within a threshold time prior to receiving the handover command from the network node, thereby indicating that the target cell may be associated with a known or semi-known state. Additionally or alternatively, the predictive mobility condition may be satisfied if the UE has not transmitted a valid measurement report about the target cell or one or more SSBs associated with the target cell within a threshold time prior to receiving the handover command from the network node, and / or if one or more SSBs measured from the target cell remain detectable during the handover delay (or handover interruption time).

[0124] Generally, when a (unmeasured) target cell is associated with a known or semi-known state based on satisfying predictive mobility conditions, one or more timeline constraints or delay requirements may have correspondingly defined values. For example, a target cell associated with a known state may be associated with a time relative to the time used to search for the target cell when the handover command is received, which has a value of 0 ms. Additionally or alternatively, a target cell associated with a semi-known state may be associated with a time relative to the time used to search for the target cell when the handover command is received, which has a value greater than 0 ms and less than the search time associated with a target cell in an unknown state. Furthermore, for a target cell associated with a semi-known state, the time required for fine-tuning time tracking and acquiring complete timing information associated with the target cell may be equal to the time required for fine-tuning time tracking and acquiring complete timing information for target cells associated with known and / or unknown states.

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

[0126] Figures 7A to 7B This is a diagram illustrating Example 700 associated with latency requirements for predictive mobility according to this disclosure. As shown in FIG. 7, Example 700 includes UE 705, source network node 710, and target network node 715. In some examples, actions described as being performed by network nodes (e.g., source network node 710 and / or target network node 715) may be performed by multiple network nodes. For example, configuration actions may be performed by a first network node (e.g., CU or DU), and radio communication actions may be performed by a second network node (e.g., DU or RU).

[0127] UE 705 may correspond to UE 120 as described elsewhere herein. Source network node 710 and / or target network node 715 may correspond to network node 110 as described elsewhere herein. UE 705 and source network node 710 may be connected via a serving cell or a source cell, and UE 705 may undergo a handover via a target cell to target network node 715. Source network node 710 and target network node 715 may communicate with a core network (not shown) for mobility support, user plane functions, and / or other suitable functions.

[0128] In some aspects, such as Figure 7A And as indicated by reference numeral 720, UE 705 may receive a handover command from source network node 710. For example, in some aspects, when UE 705 is configured for L3-based mobility, the handover command may include an L3 (e.g., RRC) message (e.g., as referenced above). Figure 4 (For further details), or when the UE 705 is configured for LTM, the handover command may include an L1 (e.g., DCI) message or an L2 (e.g., MAC-CE) message (e.g., as described above). Figures 5A to 5B (To be described in further detail). In some respects, the handover command may instruct UE 705 to perform a handover from source network node 710 associated with the source cell to target network node 715 associated with the target cell.

[0129] like Figure 7AFurthermore, as shown by reference numeral 725, the UE can determine the state associated with the target cell based on whether one or more predictive mobility conditions are met. For example, as described herein, the target cell associated with the handover command can be identified based on one or more beam predictions (e.g., predicted beam measurements) obtained by the UE 705 and / or one or more beam predictions obtained by a network node (e.g., the source network node 710 or a network node that directs or otherwise controls the operation associated with the source network node 710). Thus, using the default legacy definition of known and / or unknown states for the target cell associated with the handover, the target cell can be associated with an unknown default state because the handover decision is based on one or more beam predictions, rather than one or more direct measurements of the target cell. However, since an unknown state can result in significantly longer handover interruption delays compared to a known or semi-known state, the target cell can be associated with a known or semi-known state to reduce handover interruption delays if one or more predictive mobility conditions are met.

[0130] For example, if UE 705 has transmitted a valid prediction report associated with the target cell or one or more SSBs associated with the target cell to source network node 710 within a threshold time before receiving the handover command, the target cell may be associated with a known or semi-known state. For example, as by Figure 7A As indicated by reference numeral 730 in the accompanying drawings, UE 705 may send a prediction report to the source network 710 before receiving a handover command. Therefore, within a threshold timeframe before UE 705 receives the handover command (e.g., at the last possible moment before receiving the handover command), X During the seconds, X It has values ​​defined in one or more wireless communication standards, and where X If a prediction report is sent to source network node 710 for L3-based mobility (which may have the same or different values ​​for LTM) and the prediction report is associated with a predicted measurement for the target cell (rather than an actual measurement for the target cell), one or more predictive mobility conditions are met, and the target cell may be associated with a known or semi-known state. Alternatively, if UE 705 has not yet transmitted a prediction report for the target cell to source network node 710 or has transmitted a prediction report for the target cell before a threshold time prior to receiving the handover command, the predictive mobility conditions associated with the transmission of a valid prediction report are not met, and the target cell is associated with an unknown state, unless one or more other predictive mobility conditions are met.

[0131] Additionally or alternatively, if UE 705 has received a valid prediction result indication associated with the target cell or one or more SSBs associated with the target cell from source network node 710 within a threshold time before UE 705 receives the handover command, the target cell may be associated with a known or semi-known state. For example, as by Figure 7A As indicated by reference numeral 735 in the accompanying drawings, UE 705 can receive a prediction result indication from source network 710 before receiving a handover command. Therefore, within a threshold timeframe before UE 705 receives the handover command (e.g., the last...),... X If, within a specified time period, the UE 705 receives a prediction result indication from the source network node 710 and the prediction result indication is associated with a predicted measurement for the target cell (rather than an actual measurement obtained by the UE 705 for the target cell), one or more predictive mobility conditions are met, and the target cell may be associated with a known or semi-known state. Alternatively, if the UE 705 has not yet received a prediction result indication for the target cell from the source network node 710 or receives a prediction result indication for the target cell before a threshold time prior to receiving the handover command, the predictive mobility conditions associated with the reception of a valid prediction result indication are not met, and the target cell is associated with an unknown state, unless one or more other predictive mobility conditions are met.

[0132] Alternatively or additionally, if UE 705 has not sent a valid measurement report about the target cell or one or more SSBs associated with the target cell to the source network node 710 within a threshold time prior to UE 705 receiving the handover command, the target cell may be associated with a known or semi-known state. Alternatively or additionally, if one or more SSBs measured by UE 705 from the target cell remain detectable during the handover delay (e.g., for fine-grained time tracking and / or obtaining complete timing information associated with the target cell), the target cell may be associated with a known or semi-known state. Alternatively, if UE 705 has sent a valid measurement report about the target cell or one or more SSBs associated with the target cell, or if the SSBs measured by UE 705 are undetectable during the handover delay, the corresponding predictive mobility condition is not met and the target cell is associated with an unknown state, unless one or more other predictive mobility conditions are met.

[0133] like Figure 7A Furthermore, as shown by reference numeral 740, UE 705 can determine the handover interruption time for handover to the target cell based on the state associated with the target cell. For example, as described herein, the handover interruption time can be defined according to one or more delay requirements such that the handover interruption time cannot exceed T. interrupt ,in As described in this article, T search T is the time required to search for the target cell when the UE 705 receives the handover command. IU The interrupt uncertainty T refers to the interruption uncertainty when acquiring the first available PRACH opportunity in the target cell. processing It is the UE processing time. It is the time used for fine-grained time tracking and acquiring complete timing information of the target cell, and T margin This refers to the SSB post-processing time. Generally, the handover interruption time is defined as the time between the end of the last TTI containing the handover command and the time when the UE 705 begins sending PRACH (e.g., for L3-based mobility) or PUxCH or SRS (e.g., for LTM) to the target cell. Therefore, the TTI configuration for the target cell can depend on whether the target cell is associated with a known state, a semi-known state, or an unknown state. search and / or The value (e.g., to reduce handover delay when one or more predictive mobility conditions are met, so that a target cell associated with an unknown state can be associated with a known or semi-known state instead).

[0134] For example, when the target cell is associated with a known state, the time T required to search for the target cell when the handover command is received by UE 705. search This can be defined as 0 ms (e.g., because the target SSB in the target cell has already been identified based on one or more beam predictions performed by UE 705 or source network node 710, and one or more candidate Rx beams can be directly predicted at UE 705 using separate AI / ML techniques), making it unnecessary to measure any SSB from the target cell. Alternatively, in the case where the target cell is associated with a semi-known state, the time T required to search for the target cell upon receiving the handover command by UE 705 is... search It can be defined as exceeding 0 ms and being less than T for a target cell associated with an unknown state. search The value (e.g., because the target SSB in the target cell has already been identified based on one or more beam predictions by UE 705 or source network node 710, and the range of one or more candidate Rx beams can be narrowed at UE 705 by AI / ML technology and / or QCL source indication from source network node 710). Furthermore, when the target cell is associated with a semi-known state, the time required for fine-grained time tracking and obtaining complete timing information of the target cell. This can be equivalent to the time for fine-grained time tracking and acquiring complete timing information of the target cell associated with a known or unknown state. Therefore, depending on whether the target cell is associated with a known state, a semi-known state, or an unknown state, UE 705 can determine the appropriate handover interruption time that defines when UE 705 must be ready to send uplink signals (e.g., PRACH, PUxCH, or SRS) to the target cell.

[0135] For example, such as Figure 7A As shown by reference numeral 745, UE 705 can perform one or more handover activities, which may include actions based on T after receiving a handover command. search The value is used to search for the target cell, and based on T Δ The value is used to perform fine-grained time tracking and obtain complete timing information for the target cell. For example... Figure 7A And as further shown by reference numeral 750 in the accompanying drawings, the UE 750 can then be based at least in part on T search The value of T Δ During the handover interruption period, the uplink message (or signal) is sent to the target cell.

[0136] For example, refer to Figure 7B Figure 755 depicts the state of the target cell associated with an unknown state, where T for the unknown target cell search The value is N 3 T rs Where N=8 if the target cell is in FR2-1, or N=12 if the target cell is in FR2-2 (e.g., based on UE 705, it must be...). N (Measure 3 SSBs on each receive beam). However, as indicated by reference numeral 760, one or more beam predictions performed by UE 705 and / or source network node 710 can be used to identify the target SSB among the various SSBs transmitted by the target cell. This eliminates the need to measure multiple SSBs, allowing the target cell to be associated with a semi-known state based on one or more beam predictions. Furthermore, as described herein, the range of candidate receive beam sets can be narrowed (e.g., via a specific implementation of UE 705 or by QCL source indication provided by source network node 710) relative to the case where the target cell is associated with an unknown state, which reduces the number of receive beams that need to be scanned during handover. Therefore, as indicated by reference numeral 765, when the target cell is associated with a semi-known state, the T for the semi-known target cell... search The value is M 2 T rs ,in M2 = M =4 (For example, based on UE 705, it must be 4) M 2 One SSB is measured on each receive beam (in the illustrated example, this SSB includes four receive beams). Additionally or alternatively, as indicated by reference numeral 770, one or more beam predictions performed by UE 705 and / or source network node 710 can be used to identify the target SSB among various SSBs transmitted by the target cell. This eliminates the need to measure multiple SSBs, and candidate receive beams can be directly predicted (e.g., via a separate AI / ML technique supported by UE 705), allowing the target cell to be associated with a known state based on one or more beam predictions. Therefore, as indicated by reference numeral 775, when the target cell is associated with a known state, the T for the known target cell... search The value is 0ms because UE 705 does not need to perform any SSB measurements or select a preferred candidate receive beam.

[0137] In some respects, where the handover command is based on one or more beam predictions obtained by UE 705, whether the target cell associated with the handover command meets the criteria for being associated with a known or semi-known state may depend on one or more capabilities of UE 705. For example, in some respects, UE 705 may send capability information to source network node 710 that indicates one or more capabilities related to whether the target cell identified based on one or more beam predictions can be associated with a known or semi-known state. For example, if UE 705 is a high-end UE or otherwise has the capability to support Rx beam prediction, the target cell may be associated with a known state. Additionally or alternatively, if UE 705 is in an intermediate tier or only supports a limited number of candidate Rx beams, the target cell may be associated with a semi-known state but may not meet the criteria for being associated with a known state. Additionally or alternatively, T search The duration can depend on the capability signaling reported by UE 705 to source network node 710. For example, in FR2, for a target cell within the frequency range, T search Can be equal to M 1 T rs And for target cells between frequencies, T search Can be equal to M 2 T rs This includes capability reports based on UE 705. M 1 << N and M 2<<3 N (For example, where) N (This is defined elsewhere in this document).

[0138] Furthermore, in some aspects, a target cell associated with handover may be associated with an unknown state based on RRC and / or dynamic (e.g., L1 / L2) signaling transmitted from UE 705 to source network node 710 (e.g., but UE 705 transmits a valid prediction report and / or UE 705 receives a valid prediction result indication). For example, when UE 705 is in a lower tier or category, UE 705 may have an option to report an indication that the target cell will be associated with an unknown state, even if one or more predictive mobility conditions for associating the target cell with a known or semi-known state are met. Additionally, in such cases, any applicable timeline constraints or delay requirements for identifying or otherwise determining the handover interruption time of the target cell may be based on the target cell having an unknown state. Additionally or alternatively, UE 705 may indicate that a target cell that meets the conditions for associating with a known or semi-known state due to the satisfaction of one or more predictive mobility conditions will be associated with an unknown state, regardless of the tier or category associated with UE 705. For example, UE 705 may send a request to source network node 710 to associate a target cell associated with predictive mobility decisions with an unknown state due to a lack of AI / ML computing resources, overheating issues, and / or other reasons (e.g., via one or more RRC messages, MAC-CE messages, or UCI messages). UE 705 may subsequently (e.g., via one or more RRC messages, MAC-CE messages, or UCI messages) send additional signaling to revoke the request, such that the target cell identified based on one or more beam predictions can be associated with a known or semi-known state once any computing resource constraints, overheating issues, and / or other reasons have been resolved. For example, subsequent signaling may instruct that a target cell identified based on one or more beam predictions can be associated with a known or semi-known state after its state was previously restricted to only semi-known / unknown or unknown. In such cases, UE 705 may wait for one or more messages from source network node 710 confirming the state change before applying updated assumptions based on updated preferences.

[0139] In addition, in some aspects, UE 705 may jointly or separately report capability information and / or preference updates for L3 mobility and LTM and / or for intra-frequency target cells and inter-frequency target cells. Additionally or alternatively, UE 705 may jointly or separately report capability information and / or preference updates for one or more additional conditions related to the beam prediction obtained by UE 705 (e.g., the number of measurement cells and / or reference signals used to derive the beam prediction, the number of target cells and / or SSBs associated with the beam prediction, and / or the duration between the prediction report transmitted by UE 705 and the handover command). Additionally or alternatively, UE 705 may jointly or separately report capability information and / or preference updates for one or more additional conditions related to the beam prediction obtained by source network node 710 (e.g., the availability or type of network-side auxiliary information (such as beam shape or direction information, cell layout information, etc.), whether a QCL source is provided as a reference, and / or the duration between the prediction result indication transmitted by source network node 710 and the subsequent handover command).

[0140] In some respects, as described herein, predictive mobility can be enabled for L3-based mobility (e.g., L3- or RRC-based signaling) and / or for LTM (e.g., L1 / L2-based signaling). Therefore, when a handover command is associated with L3-based mobility (e.g., carried in an RRC message), the prediction report sent by UE 705 may include one or more predicted L3-RSRP measurements and / or L3-SINR measurements for one or more SSBs associated with the target cell. Additionally or alternatively, the prediction report sent by UE 705 may include predicted previous... K Each SSB (e.g., in terms of L3-RSRP measurement and / or L3-SINR measurement). In some aspects, the prediction results indicated in the prediction report can be derived by the UE 705 without the UE 705 actually measuring the SSB associated with the predicted measurement, and the source network node 710 receiving the prediction report can know that the prediction report does not include actual SSB measurement based on the appropriate signaling framework between the UE 705 and the source network node 710 (e.g., an RRC message can be defined for the prediction report, which may be different from the RRC message used to carry the measurement report). Additionally or alternatively, when the handover command is associated with LTM (e.g., the handover command is carried in an L1 or L2 message), the prediction report sent by the UE 705 may include one or more predicted L1-RSRP measurements and / or L1-SINR measurements regarding one or more SSBs associated with the target cell. Additionally or alternatively, the prediction report sent by the UE 705 may include predicted previous SSB measurements associated with the target cell. KEach SSB (e.g., in terms of L1-RSRP measurement and / or L1-SINR measurement). In some aspects, the prediction results indicated in the prediction report can be derived by the UE 705 without the UE 705 actually measuring the SSB associated with the predicted measurement, and the source network node 710 receiving the prediction report can know that the prediction report does not include actual SSB measurement based on the appropriate signaling framework between the UE 705 and the source network node 710 (e.g., a CSI report setting can be defined for the prediction report, which may be different from the CSI report setting used to carry the measurement report).

[0141] Additionally or alternatively, where the handover command is based on one or more beam predictions obtained by the source network node 710 and the handover command is associated with L3-based mobility (e.g., carried in an RRC message), the prediction result indication sent by the source network node 710 to the UE 705 may include one or more predicted L3-RSRP measurements and / or L3-SINR measurements regarding one or more SSBs associated with the target cell. Additionally or alternatively, the prediction result indication may include the predictions made by the source network node 710 for the target cell. K Each SSB (e.g., in terms of L3-RSRP measurement and / or L3-SINR measurement). In some aspects, a predicted result indication can be derived without the UE 705 actually measuring the SSB associated with the predicted result indication, and the UE 705 receiving the predicted result indication can know, based on an appropriate signaling framework between the UE 705 and the source network node 710, that the prediction report does not include actual SSB measurement (e.g., an RRC message can be defined for the prediction report, which may be different from the RRC message used to carry a typical L3 handover message). Additionally or alternatively, the predicted result indication may be indicated via a MAC-CE or DCI message that it is not associated with an actual measurement, or the UE 705 may know that the SSB addressed in the handover command from the source network node 710 has not previously been configured for measurement and / or reporting to the source network node 710.

[0142] Additionally or alternatively, where the handover command is associated with LTM (e.g., the handover command is carried in an L1 or L2 message), the prediction result indication transmitted to UE 705 may include one or more predicted L1-RSRP measurements and / or L1-SINR measurements regarding one or more SSBs associated with the target cell. Additionally or alternatively, the prediction result indication transmitted to UE 705 may include predicted previous values ​​associated with the target cell. KEach SSB (e.g., in terms of L1-RSRP measurement and / or L1-SINR measurement). In some aspects, a prediction result indication can be derived without the UE 705 actually measuring the SSB associated with the predicted measurement, and the UE 705 receiving the prediction result indication can know, based on an appropriate signaling framework, that the prediction result indication is not based on an actual SSB measurement. For example, in some aspects, a TCI state configuration, activation, and / or indication message can be defined for the predicted SSB that is a QCL source, which may differ from a typical TCI state configuration, activation, and / or indication message. In another example, an indication that the prediction result indication is not based on an actual measurement can be carried in the LTM handover command, or the UE 705 can know that the SSB addressed in the handover command from the source network node 710 has not previously been configured for measurement and / or reporting to the source network node 710.

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

[0144] Figure 8 This is a diagram illustrating an example process 800 performed, for example, at a UE or a device of a UE, according to this disclosure. Example process 800 is an example in which a device or UE (e.g., UE 120) performs operations associated with techniques for interruption delay requirements for predictive mobility.

[0145] like Figure 8 As shown, in some aspects, process 800 may include receiving from a network node a handover command (block 810) that triggers a handover to a target cell associated with an unknown state. For example, the UE (e.g., using...) Figure 9 The described receiving component 902 and / or communication manager 906 can receive from the network node a handover command that triggers the handover to a target cell associated with an unknown state, as described above.

[0146] like Figure 8 Further, in some aspects, process 800 may include identifying a handover interruption time associated with a target cell (box 820) based on one or more predictive mobility conditions satisfied within a threshold time prior to receiving a handover command, according to one or more delay requirements associated with a target cell having a known or semi-known state. For example, the UE (e.g., using...) Figure 9 The described communication manager 906 can identify the handover interruption time associated with the target cell based on one or more predictive mobility conditions satisfied within a threshold time prior to receiving the handover command, according to one or more delay requirements associated with the target cell having a known or semi-known state, as described above.

[0147] like Figure 8 As further shown, in some aspects, process 800 may include sending an uplink message to the target cell during the handover interruption period (box 830). For example, the UE (e.g., using...) Figure 9 The transmitting component 904 and / or the communication manager 906 depicted may transmit uplink messages to the target cell during the handover interruption period, as described above.

[0148] Process 800 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.

[0149] In the first aspect, one or more predictive mobility conditions are satisfied based on the UE transmitting a valid prediction report associated with the target cell or one or more SSBs associated with the target cell.

[0150] In the second aspect, either alone or in combination with the first aspect, based on a handover command including L3 messages, an effective prediction report indicates one or more predicted L3 measurements for one or more SSBs associated with the target cell, or a predicted set of SSBs associated with the target cell that have the best L3 measurements.

[0151] In the third aspect, either alone or in combination with one or more of the first and second aspects, based on a handover command including L1 messages or L2 messages, an effective prediction report indicates one or more predicted L1 measurements for one or more SSBs associated with the target cell, or a predicted set of SSBs associated with the target cell that have the best L1 measurements.

[0152] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, one or more predictive mobility conditions are satisfied based on the UE receiving a valid prediction result indication associated with the target cell or one or more SSBs associated with the target cell.

[0153] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, based on a handover command including L3 messages, a valid prediction result indication indicates one or more predicted L3 measurements for one or more SSBs associated with the target cell, or a predicted set of SSBs associated with the target cell that have the best L3 measurements.

[0154] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, based on a handover command including L1 messages or L2 messages, a valid prediction result indication indicates one or more predicted L1 measurements for one or more SSBs associated with the target cell, or a predicted set of SSBs associated with the target cell that have the best L1 measurement.

[0155] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, one or more predictive mobility conditions are satisfied based on the UE not having transmitted a valid measurement report associated with the target cell or one or more synchronization signal blocks associated with the target cell.

[0156] In the eighth aspect, either alone or in combination with one or more of the first to seventh aspects, one or more predictive mobility conditions are satisfied based on the fact that one or more synchronization signal blocks associated with the target cell are detectable during the handover interruption time.

[0157] In the ninth aspect, either alone or in combination with one or more of the first to eighth aspects, one or more delay requirements include a time for searching the target cell upon receiving the handover command, and the time for searching the target cell has a value of 0 ms based on the target cell being associated with a known state.

[0158] In the tenth aspect, either alone or in combination with one or more of the first to ninth aspects, one or more delay requirements include a time for searching the target cell upon receiving the handover command, and the time for searching the target cell has a value greater than 0 ms and less than the time for searching the cell associated with the unknown state, based on the target cell being associated with a semi-known state.

[0159] In the eleventh aspect, alone or in combination with one or more of the first to tenth aspects, one or more delay requirements include time for fine-grained time tracking and acquiring complete timing information associated with the target cell, and based on the target cell being associated with a semi-known state, the time for fine-grained time tracking and acquiring complete timing information associated with the target cell has a value associated with the target cell having a known or unknown state.

[0160] In the twelfth aspect, either alone or in combination with one or more of the first to eleventh aspects, a handover command is associated with one or more candidate receive beams that are directly predicted using machine learning techniques and associated with the target cell, and one or more delay requirements are associated with the target cell having a known state.

[0161] In the thirteenth aspect, either alone or in combination with one or more of the first to twelfth aspects, a handover command is associated with a set of candidate receive beams associated with a target cell, and one or more delay requirements are associated with a target cell having a semi-known state, the set of candidate receive beams including fewer members than the set of candidate receive beams associated with a target cell having an unknown state.

[0162] In the fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, process 800 includes sending capability information to network nodes related to whether the target cell is associated with a known state or a semi-known state.

[0163] In the fifteenth aspect, alone or in combination with one or more of the first to fourteenth aspects, the handover interruption time includes one or more durations having corresponding values ​​based on capability information.

[0164] In the sixteenth aspect, alone or in combination with one or more of the first to fifteenth aspects, process 800 includes sending capability information or dynamic signaling to a network node to indicate one or more supported state types for a target cell, wherein one or more delay requirements are associated with values ​​for a target cell having a semi-known or unknown state according to one or more supported state types.

[0165] In the seventeenth aspect, either alone or in combination with one or more of the first to sixteenth aspects, one or more supported state types are indicated for one or more of the following: L3 mobility and LTM, or intra-frequency target cell and inter-frequency target cell.

[0166] In the eighteenth aspect, either alone or in combination with one or more of the first to seventeenth aspects, one or more supported state types are indicated for one or more additional conditions related to the prediction of a trigger handover command executed by the UE.

[0167] In the nineteenth aspect, either alone or in combination with one or more of the first to eighteenth aspects, one or more supported state types are indicated for one or more additional conditions related to the prediction of a handover command executed by a network node.

[0168] although Figure 8 An example box of process 800 is shown, but in some respects, process 800 may include... Figure 8 The boxes depicted in the diagram may be fewer, different, or arranged differently than additional boxes. Alternatively, two or more boxes in the process 800 may be executed in parallel.

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

[0170] In some respects, device 900 can be configured to perform the functions described herein. Figures 7A to 7B One or more operations described herein. Additionally or alternatively, device 900 may be configured to perform one or more processes described herein, such as Figure 8 The process is 800. In some respects, Figure 9 The illustrated device 900 and / or one or more components may include a combination Figure 2 One or more components of the described UE. Additionally or alternatively, Figure 9 One or more components shown can be combined Figure 2 Implementation within one or more of the described components. Additionally or alternatively, one or more 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.

[0171] Receiver 902 may receive communications from device 908, such as reference signals, control information, data communications, or combinations thereof. Receiver 902 may provide the received communications to one or more other components of device 900. In some aspects, receiver 902 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.), and may provide the processed signals to one or more other components of device 900. In some aspects, receiver 902 may include combinations of... Figure 2 The described 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.

[0172] Transmitting component 904 can transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 908. In some aspects, one or more other components of device 900 can generate communications and provide the generated communications to transmitting component 904 for transmission to device 908. In some aspects, transmitting component 904 can perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and transmit the processed signals to device 908. In some aspects, transmitting component 904 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 904 may co-located with the receive component 902 in one or more transceivers.

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

[0174] The receiving component 902 can receive from the network node a handover command that triggers the handover to a target cell associated with an unknown state. The communication manager 906 can identify the handover interruption time associated with the target cell based on one or more predictive mobility conditions satisfied within a threshold time prior to receiving the handover command, according to one or more delay requirements associated with the target cell having a known or semi-known state. The transmitting component 904 can transmit uplink messages to the target cell during the handover interruption time.

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

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

[0177] Aspect 1: A method for wireless communication performed by a UE, the method comprising: receiving from a network node a handover command triggering a handover to a target cell associated with an unknown state; identifying a handover interruption time associated with the target cell based on one or more predictive mobility conditions satisfied within a threshold time prior to receiving the handover command, according to one or more delay requirements associated with the target cell having a known or semi-known state; and sending an uplink message to the target cell during the handover interruption time.

[0178] Aspect 2: According to the method of aspect 1, wherein the one or more predictive mobility conditions are satisfied based on the UE transmitting a valid prediction report associated with the target cell or one or more SSBs associated with the target cell.

[0179] Aspect 3: According to the method of aspect 2, wherein, based on the handover command including L3 messages, the effective prediction report indicates one or more predicted L3 measurements for one or more SSBs associated with the target cell, or a predicted set of SSBs associated with the target cell that have the best L3 measurements.

[0180] Aspect 4: According to the method of aspect 2, wherein based on the handover command including L1 messages or L2 messages, the effective prediction report indicates one or more predicted L1 measurements for one or more SSBs associated with the target cell or a predicted set of SSBs with the best L1 measurements associated with the target cell.

[0181] Aspect 5: The method according to any one of Aspects 1 to 4, wherein the one or more predictive mobility conditions are satisfied based on the UE receiving a valid prediction result indication associated with the target cell or one or more SSBs associated with the target cell.

[0182] Aspect 6: According to the method of aspect 5, wherein based on the handover command including L3 messages, the effective prediction result indicates one or more predicted L3 measurements for one or more SSBs associated with the target cell, or a predicted set of SSBs associated with the target cell that have the best L3 measurements.

[0183] Aspect 7: According to the method of aspect 5, wherein based on the handover command including L1 messages or L2 messages, the effective prediction result indicates one or more predicted L1 measurements for one or more SSBs associated with the target cell or a predicted set of SSBs with the best L1 measurement associated with the target cell.

[0184] Aspect 8: The method according to any one of Aspects 1 to 7, wherein the one or more predictive mobility conditions are satisfied based on the UE not having transmitted a valid measurement report associated with the target cell or one or more SSBs associated with the target cell.

[0185] Aspect 9: The method according to any one of Aspects 1 to 8, wherein the one or more predictive mobility conditions are satisfied based on the fact that one or more SSBs associated with the target cell are detectable during the handover interruption time.

[0186] Aspect 10: The method according to any one of Aspects 1 to 9, wherein the one or more delay requirements include a time for searching the target cell when the handover command is received, and wherein the time for searching the target cell has a value of 0 ms based on the target cell being associated with the known state.

[0187] Aspect 11: The method according to any one of Aspects 1 to 10, wherein the one or more delay requirements include a time for searching the target cell when the handover command is received, and wherein the time for searching the target cell has a value greater than 0 ms and less than the time for searching a cell associated with an unknown state, based on the target cell being associated with the semi-known state.

[0188] Aspect 12: The method according to any one of Aspects 1 to 11, wherein the one or more delay requirements include time for fine time tracking and acquiring complete timing information associated with the target cell, and wherein the time for fine time tracking and acquiring the complete timing information associated with the target cell has a value associated with the target cell having a known or unknown state, based on the target cell being associated with the semi-known state.

[0189] Aspect 13: The method according to any one of Aspects 1 to 12, wherein the handover command is associated with one or more candidate receive beams directly predicted using machine learning techniques in connection with the target cell, and the one or more delay requirements are associated with the target cell having the known state.

[0190] Aspect 14: The method according to any one of Aspects 1 to 13, wherein the handover command is associated with a set of candidate receive beams associated with the target cell, the one or more delay requirements are associated with the target cell having the semi-known state, and the set of candidate receive beams includes fewer members than the set of candidate receive beams associated with the target cell associated with the unknown state.

[0191] Aspect 15: The method according to any one of Aspects 1 to 14, the method further comprising: sending capability information to the network node relating to whether the target cell is associated with the known state or the semi-known state.

[0192] Aspect 16: According to the method of aspect 15, the handover interruption time includes one or more durations having corresponding values ​​based on the capability information.

[0193] Aspect 17: The method according to any one of Aspects 1 to 16, the method further comprising: sending capability information or dynamic signaling to the network node to indicate one or more supported state types for the target cell, wherein the one or more latency requirements are associated with a value for the target cell having the semi-known state or the unknown state according to the one or more supported state types.

[0194] Aspect 18: According to the method of aspect 17, the one or more supported state types are indicated for one or more of the following: L3 mobility and LTM, or intra-frequency target cell and inter-frequency target cell.

[0195] Aspect 19: According to the method of aspect 17, wherein the one or more supported state types are indicated for one or more additional conditions related to a prediction of triggering the handover command executed by the UE.

[0196] Aspect 20: According to the method of aspect 17, wherein the one or more supported state types are indicated for one or more additional conditions related to a prediction that triggers the handover command executed by the network node.

[0197] Aspect 21: 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 20.

[0198] Aspect 22: 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 20.

[0199] Aspect 23: 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 20.

[0200] Aspect 24: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by one or more processors to perform the method according to one or more of aspects 1 to 20.

[0201] Aspect 25: 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 20.

[0202] Aspect 26: 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 20.

[0203] Aspect 27: 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 20.

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

[0205] As used herein, the term "component" is intended to be interpreted broadly as hardware, firmware, or a combination of hardware and software. As used herein, a processor is implemented as hardware, firmware, or a combination of hardware and software. As used herein, the phrase "based on" is intended to be interpreted broadly as "at least partially based on". As used herein, depending on the context, "meeting a threshold" can refer to a value greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc. As used herein, the phrase referring to "at least one of" a list of items means any combination of those items, including a single member. As an example, "at least one of a, b, or c" is intended to cover: a, b, c, a+b, a+c, b+c, and a+b+c.

[0206] Furthermore, as used herein, the articles “a” and “an” are intended to include one or more items and are interchangeable with “one or more”. Furthermore, as used herein, the article “described” is intended to include one or more items mentioned in connection with the article “described” and is interchangeable with “one or more”. Furthermore, as used herein, the terms “set” and “group” are intended to include one or more items (e.g., related items, unrelated items, or a combination of related and unrelated items) and are interchangeable with “one or more”. If only one item is desired, the phrase “only one” or similar terms will be used. Moreover, as used herein, the terms “having” and similar terms are intended to be open-ended terms that do not limit the elements they modify (e.g., an element “having” A may also have B). Furthermore, as used herein, the term “or” when used in a sequence is intended to be inclusive and is interchangeable with “and / or” unless otherwise explicitly stated (e.g., in conjunction with “either of” or “only one of”).

[0207] The various exemplary logic components, logic blocks, modules, circuits, and algorithmic processes described in conjunction with the aspects disclosed herein can be implemented as electronic hardware, computer software, or a combination of both. The interchangeability of hardware and software has been generally described in terms of functionality and is illustrated in the various exemplary components, blocks, modules, circuits, and processes described herein. Whether such functionality is implemented in hardware or software depends on the specific application and the design constraints imposed on the overall system.

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

[0209] In one or more aspects, the described functionality may be implemented in hardware, digital electronic circuits, computer software, firmware, including the structures disclosed in this specification and their structural equivalents or any combination thereof. Aspects of the subject matter described in this specification may also be implemented as one or more computer programs (such as one or more modules of computer program instructions) encoded on a computer storage medium for execution by or control of the operation of a data processing apparatus.

[0210] If implemented in software, the functionality can be stored as one or more instructions or code on or transmitted through a computer-readable medium. The process of the methods or algorithms disclosed herein can be implemented in a processor-executable software module that can reside on a computer-readable medium. Computer-readable media includes both computer storage media and communication media, with communication media including any medium capable of transferring a computer program from one place to another. Storage media can be any available medium accessible to a computer. By way of example, and not limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disc storage devices, disk storage devices or other magnetic storage devices, or any other medium that can be used to store desired program code in the form of instructions or data structures and is accessible to a computer. Furthermore, any connection may be properly referred to as a computer-readable medium. As used herein, disks and optical discs include compact optical discs (CDs), laser discs, optical discs, digital versatile optical discs (DVDs), floppy disks, and Blu-ray discs, where disks typically reproduce data magnetically, while optical discs reproduce data optically using lasers. Combinations of media described herein should also be included within the scope of computer-readable media. Additionally, the operation of a method or algorithm may reside as a set of code and instructions or any combination of code and instructions on a machine-readable medium and a computer-readable medium that may be incorporated into a computer program product.

[0211] Various modifications to the aspects described in this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects without departing from the spirit or scope of this disclosure. Therefore, the claims are not intended to be limited to the aspects shown herein, but are to be granted the widest scope consistent with this disclosure, the principles disclosed herein, and the novel features.

[0212] Additionally, those skilled in the art will readily recognize that the terms “upper” and “lower” are sometimes used to facilitate the description of the drawings and to indicate relative positioning on a correctly oriented page corresponding to the orientation of the drawings, and may not reflect the correct orientation of any device as implemented.

[0213] Some features described in the context of an independent aspect in this specification may also be implemented in combination in a single aspect. Conversely, various features described in the context of a single aspect may also be implemented individually or in any suitable sub-combination in multiple aspects. Furthermore, although features may be described as functioning in certain combinations and even originally claimed in this way, one or more features from the claimed combination may be removed from that combination in some cases, and the claimed combination may be for sub-combinations or variations thereof.

[0214] Similarly, although operations are depicted in a specific order in the figures, this should not be construed as requiring such operations to be performed in the specific order shown or in sequential order, or to perform all illustrated operations to achieve the desired result. Furthermore, the figures may schematically depict one or more example processes in the form of flowcharts. However, other operations not depicted may be incorporated into the schematically illustrated example processes. For example, one or more additional operations may be performed before, after, simultaneously with, or between any of the illustrated operations. In some contexts, multitasking and parallel processing are advantageous. Moreover, the separation of various system components in the described aspects should not be construed as requiring such separation in all aspects, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products. Additionally, other aspects also fall within the scope of the appended claims. In some cases, the actions recited in the claims may be performed in a different order and still achieve the desired result.

Claims

1. A method for wireless communication performed by a user equipment (UE), the method comprising: Receive a handover command from the network node that triggers the handover to the target cell associated with an unknown state; Based on satisfying one or more predictive mobility conditions within a threshold time prior to receiving the handover command, the handover interruption time associated with the target cell is identified according to one or more delay requirements associated with the target cell having a known or semi-known state. as well as During the handover interruption period, an uplink message is sent to the target cell.

2. The method of claim 1, wherein the one or more predictive mobility conditions are satisfied based on the UE transmitting a valid prediction report associated with the target cell or one or more synchronization signal blocks (SSBs) associated with the target cell.

3. The method of claim 2, wherein, based on the handover command including a Layer 3 (L3) message, the effective prediction report indicates one or more predicted L3 measurements for one or more SSBs associated with the target cell, or a predicted set of SSBs associated with the target cell that have the best L3 measurements.

4. The method of claim 2, wherein, based on the handover command including a Layer 1 (L1) message or a Layer 2 (L2) message, the effective prediction report indicates one or more predicted L1 measurements for one or more SSBs associated with the target cell or a predicted set of SSBs associated with the target cell that have the best L1 measurement.

5. The method of claim 1, wherein the one or more predictive mobility conditions are satisfied based on the UE receiving a valid prediction result indication associated with the target cell or one or more synchronization signal blocks (SSBs) associated with the target cell.

6. The method of claim 5, wherein the effective prediction result, based on the handover command including a Layer 3 (L3) message, indicates one or more predicted L3 measurements for one or more SSBs associated with the target cell, or a predicted set of SSBs associated with the target cell that have the best L3 measurements.

7. The method of claim 5, wherein the effective prediction result indicates, based on the handover command including a Layer 1 (L1) message or a Layer 2 (L2) message, one or more predicted L1 measurements for one or more SSBs associated with the target cell or a predicted set of SSBs associated with the target cell that have the best L1 measurement.

8. The method of claim 1, wherein the one or more predictive mobility conditions are satisfied based on the UE not having transmitted a valid measurement report associated with the target cell or one or more synchronization signal blocks associated with the target cell.

9. The method of claim 1, wherein the one or more predictive mobility conditions are satisfied based on the fact that one or more synchronization signal blocks associated with the target cell are detectable during the handover interruption time.

10. The method of claim 1, wherein the one or more latency requirements include a time for searching the target cell upon receiving the handover command, and wherein the time for searching the target cell has a value of zero milliseconds based on the target cell being associated with the known state.

11. The method of claim 1, wherein the one or more latency requirements include a time for searching the target cell upon receiving the handover command, and wherein the time for searching the target cell, based on the association of the target cell with the semi-known state, has a value greater than zero milliseconds and less than the time for searching cells associated with the unknown state.

12. The method of claim 1, wherein the one or more latency requirements include time for fine-tuning time tracking and acquiring complete timing information associated with the target cell, and wherein the time for fine-tuning time tracking and acquiring the complete timing information associated with the target cell has a value associated with a target cell having a known or unknown state, based on the target cell being associated with the semi-known state.

13. The method of claim 1, wherein the handover command is associated with one or more candidate receive beams directly predicted using machine learning techniques in connection with the target cell, and the one or more delay requirements are associated with the target cell having the known state.

14. The method of claim 1, wherein the handover command is associated with a set of candidate receive beams associated with the target cell, the one or more delay requirements are associated with the target cell having the semi-known state, and the set of candidate receive beams includes fewer members than the set of candidate receive beams associated with the target cell associated with the unknown state.

15. The method according to claim 1, further comprising: Send capability information to the network node related to whether the target cell is associated with the known state or the semi-known state.

16. The method of claim 15, wherein the handover interruption time comprises one or more durations having corresponding values ​​based on the capability information.

17. The method according to claim 1, further comprising: The network node sends capability information or dynamic signaling to indicate one or more supported state types for the target cell, wherein the one or more latency requirements are associated with a value for the target cell having the semi-known state or the unknown state according to the one or more supported state types.

18. The method of claim 17, wherein the one or more supported state types are indicated for one or more of the following: Layer 3 mobility and Layer 1 / Layer 2 triggered mobility, or intra-frequency target cell and inter-frequency target cell.

19. The method of claim 17, wherein the one or more supported state types are indicated for one or more additional conditions related to a prediction of triggering the handover command executed by the UE.

20. The method of claim 17, wherein the one or more supported state types are indicated for one or more additional conditions related to a prediction executed by the network node that triggers the handover command.

21. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: One or more memory units; and One or more processors, said one or more processors being coupled to said one or more memories and configured to cause the UE to: Receive a handover command from the network node that triggers the handover to the target cell associated with an unknown state; Based on satisfying one or more predictive mobility conditions within a threshold time prior to receiving the handover command, the handover interruption time associated with the target cell is identified according to one or more delay requirements associated with the target cell having a known or semi-known state. as well as During the handover interruption period, an uplink message is sent to the target cell.

22. The UE of claim 21, wherein the one or more predictive mobility conditions are satisfied based on one or more of the following: The UE transmits a valid prediction report associated with the target cell or one or more synchronization signal blocks (SSBs) associated with the target cell. Upon receiving a valid prediction result indication associated with the target cell or one or more SSBs associated with the target cell, The UE has not yet transmitted a valid measurement report associated with the target cell or one or more synchronization signal blocks associated with the target cell, or One or more SSBs associated with the target cell are detectable during the handover interruption time.

23. The UE of claim 21, wherein the one or more delay requirements include time for searching the target cell when the handover command is received, and wherein the time for searching the target cell has a value based on whether the target cell is associated with the known state or the semi-known state.

24. The UE of claim 21, wherein the one or more latency requirements include time for fine-tuning time tracking and acquiring complete timing information associated with the target cell, and wherein the time for fine-tuning time tracking and acquiring the complete timing information associated with the target cell has a value associated with a target cell having a known or unknown state, based on the target cell being associated with the semi-known state.

25. The UE of claim 21, wherein the handover command is associated with one or more candidate receive beams directly predicted using machine learning techniques in connection with the target cell, and the one or more delay requirements are associated with the target cell having the known state.

26. The UE of claim 21, wherein the handover command is associated with a set of candidate receive beams associated with the target cell, the one or more delay requirements are associated with the target cell having the semi-known state, and the set of candidate receive beams includes fewer members than the set of candidate receive beams associated with the target cell associated with the unknown state.

27. The UE of claim 21, wherein the one or more processors are further configured to cause the UE to: Send capability information to the network node related to whether the target cell is associated with the known state or the semi-known state.

28. The UE of claim 21, wherein the one or more processors are further configured to cause the UE to: The network node sends capability information or dynamic signaling to indicate one or more supported state types for the target cell, wherein the one or more latency requirements are associated with a value for the target cell having the semi-known state or the unknown state according to the one or more supported state types.

29. A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising: One or more instructions, which, when executed by one or more processors of a user equipment (UE), cause the UE to: Receive a handover command from the network node that triggers the handover to the target cell associated with an unknown state; Based on satisfying one or more predictive mobility conditions within a threshold time prior to receiving the handover command, the handover interruption time associated with the target cell is identified according to one or more delay requirements associated with the target cell having a known or semi-known state. as well as During the handover interruption period, an uplink message is sent to the target cell.

30. An apparatus for wireless communication, the apparatus comprising: A component used to receive a handover command from a network node that triggers a handover to a target cell associated with an unknown state; A component for identifying the handover interruption time associated with the target cell based on one or more delay requirements associated with the target cell having a known or semi-known state, based on satisfying one or more predictive mobility conditions within a threshold time prior to receiving the handover command; and A component used to send uplink messages to the target cell during the handover interruption period.

Images