Sensing-based mobility procedure

Abstract

This disclosure provides systems, devices, apparatus, and methods, including computer programs encoded on storage media, for sensing-based mobility. A serving network entity (104S), upon detecting a sensing-triggering event (210) by the serving network entity (104S), obtains (216) sensing data from a sensor associated with at least one of: the serving network entity (104S), a neighbor network entity (104N), or a UE (102). The serving network entity (104S) transmits (230), to the UE (102) based on the sensing data, a command to perform a mobility procedure with the neighbor network entity (104N).

Description

SENSING-BASED MOBILITY PROCEDURECROSS REFERENCE TO RELATED APPLICATIONS

[0001] This application claims priority' to U.S. Provisional Patent Application No.63 / 762.506, filed on February 24, 2025. the content of which is incorporated herein by reference.TECHNICAL FIELD

[0002] The present disclosure relates generally to wireless communication, and more particularly, to a sensing-based mobility procedure.BACKGROUND

[0003] The Third Generation Partnership Project (3GPP) specifies a radio interface referred to as fifth generation (5G) new radio (NR) (5G NR). An architecture for a 5G NR wireless communication system includes a 5G core (5GC) network, a 5G radio access network (5G-RAN), a user equipment (5G UE), etc. The 5G NR architecture seeks to provide increased data rates, decreased latency, and / or increased capacity compared to prior generation cellular communication systems.

[0004] Wireless communication systems, in general, provide various telecommunication services (e.g., telephony, video, data, messaging, etc.) based on multiple-access technologies, such as orthogonal frequency division multiple access (OFDMA) technologies, that support communication with multiple UEs. Improvements in mobile broadband continue the progression of such wireless communication technologies. For example, some UEs and network entities (NEs) are associated with one or more sensors capable of detecting environmental information. The UEs and the NEs can support a broad range of mobile applications using data collected by the sensors.BRIEF SUMMARY

[0005] The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects. This summary neither identifies key or critical elements of all aspects nor delineates the scope of any or all aspects. Its sole purpose G114380 10120WOis to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.

[0006] In cellular communications, an NE, such as a base station or a unit of a base station, may communicate with a UE when the UE is within a coverage area of the NE. When the communication quality drops due to. e.g., an environmental change or the UE’s movement out of the coverage area, the NE may initiate a mobility procedure such that the UE switches to another NE, e.g., a neighbor NE, for continued cellular service. In general, it is desirable to reduce interruption to the UE's communication caused by the mobility procedure.

[0007] Traditionally, an NE determines to initiate the mobility procedure based on signal quality measurements reported by the UE. For example, the NE sends a downlink reference signal (DLRS) to the UE, and the UE measures the reference signal received power (RSRP) and signal-to-interference-plus-noise ratio (SINR) of the DLRS and reports the measurement results to the NE. Using the measurement results, the NE determines whether to initiate the mobility procedure and, if so, the target NE. As the radio environment becomes more complex, mobility procedures based on DLRS measurements may temporarily interrupt high-speed and high-quality communication services.

[0008] Aspects of the present disclosure address the above-noted and other deficiencies by utilizing sensing to improve the accuracy and efficiency in mobility procedures. For example, an NE uses sensors to detect or predict environmental changes that affect the communication quality with the UE, and further uses sensing data obtained from the sensors along with the measurement results to make a mobility decision. With one or more features described herein, implementations of this disclosure allows the NE to be more informed about the communication environment and to make mobility decisions more efficiently or effectively, thereby improving communication quality and user experience.

[0009] According to some aspects, a serving NE, upon detecting a triggering event, obtains sensing data from a sensor associated with at least one of: the serving NE, a neighbor NE, or a UE. The serving NE optionally obtains sensing data from a UE. The serving NE transmits, to the UE and based on the sensing data, a command to perform the mobility procedure with the neighbor NE. In response, the UE establishes a connection with the neighbor NE and optionally transmits updated sensing data to the neighbor NE.G114380 10120WOBRIEF DESCRIPTION OF THE DRAWINGS

[0010] FIG. 1 illustrates a diagram of a wireless communications system that includes a plurality of UEs and NEs in communication over one or more cells, according to some implementations.

[0011] FIG. 2 is a signaling diagram illustrating a sensing-based mobility procedure, according to some implementations.

[0012] FIG. 3 is a flowchart illustrating a sensing-based mobility procedure at a serving NE, according to some implementations.

[0013] FIG. 4 is a flowchart illustrating a sensing-based mobility' procedure at a UE, according to some implementations.

[0014] FIG. 5 is a flowchart illustrating a sensing-based mobility procedure at a neighbor NE, according to some implementations.

[0015] FIG. 6 is a flowchart of a method of wireless communication at a NE entity, according to some implementations.

[0016] FIG. 7 is a flowchart of a method of wireless communication at a UE, according to some implementations.

[0017] FIG. 8 is a flowchart of a method of wireless communication at a neighbor NE.according to some implementations.

[0018] FIG. 9 is a diagram illustrating a hardware implementation for an example UE apparatus, according to some implementations.

[0019] FIG. 10 is a diagram illustrating a hardware implementation for one or more example NEs, according to some implementations.DETAILED DESCRIPTION

[0020] As discussed above, mobility procedures retying on cellular signal (e.g., DLRS) measurement results face challenges in today’s high-speed and high-quality communication systems. In view of these challenges, implementations of this disclosure provide sensing-based mobility, which enables an NE to detect or predict environmental changes based on sensing data and make mobility decisions accordingly. As described in detail below, implementations of this disclosure allow the NE to be more informed about the communication environment and to make mobility decisions more efficiently or effectively, thereby improving communication quality' and user experience.G114380 10120WO

[0021] FIG. 1 illustrates a diagram 100 of a wireless communications system associated with a plurality of cells 190. The wireless communications system includes UEs 102 and base stations / NEs 104. Some base stations may include an aggregated base station architecture and other base stations may include a disaggregated base station architecture. The aggregated base station architecture utilizes a radio protocol stack that is physically or logically integrated within a single RAN node. A disaggregated base station architecture utilizes a protocol stack that is physically or logically distributed among two or more units (e.g., radio unit (RU) 106, distributed unit (DU) 108, central unit (CU) 110). For example, a CU 110 is implemented within a RAN node, and one or more DUs 108 may be co-located with the CU 110, or alternatively, may be geographically or virtually distributed throughout one or multiple other RAN nodes. The DUs 108 may be implemented to communicate with one or more RUs 106. Any of the RU 106, the DU 108 and the CU 110 can be implemented as virtual units, such as a virtual radio unit (VRU), a virtual distributed unit (VDU), or a virtual central unit (VCU). The base station / NE 104 (e.g., an aggregated base station or disaggregated units of the base station, such as the RU 106 or the DU 108), may be referred to as a transmission reception point (TRP).

[0022] Operations of the base station 104 and / or network designs may be based on aggregation characteristics of base station functionality. For example, disaggregated base station architectures are utilized in an integrated access backhaul (TAB) network, an open-radio access network (O-RAN) network, or a virtualized radio access network (vRAN), which may also be referred to a cloud radio access network (C- RAN). Disaggregation may include distributing functionality across the two or more units at various physical locations, as well as distributing functionality' for at least one unit virtually, which can enable flexibility in network designs. The various units of the disaggregated base station architecture, or the disaggregated RAN architecture, can be configured for wired or wireless communication with at least one other unit. For example, the base stations 104d, 104e and / or the RUs 106a, 106b, 106c, 106d may communicate with the UEs 102a, 102b, 102c, 102d, and / or 102s via one or more radio frequency (RF) access links based on a Uu interface. In examples, multiple RUs 106 and / or base stations 104 may simultaneously serve the UEs 102, such as by intracell and / or inter-cell access links between the UEs 102 and the RUs 106 / base stations 104.G114380 10120WO

[0023] The RU 106, the DU 108, and the CU 110 may include (or may be coupled to) one or more interfaces configured to transmit or receive information / signals via a wired or wireless transmission medium. For example, a wired interface can be configured to transmit or receive the information / signals over a wired transmission medium, such as via the fronthaul link 160 between the RU 106d and the baseband unit (BBU) 112 of the base station 104d associated with the cell 190d. The BBU 112 includes a DU 108 and a CU 110, which may also have a wired interface (e.g., midhaul link) configured between the DU 108 and the CU 110 to transmit or receive the information / signals between the DU 108 and the CU 110. In further examples, a wireless interface, which may include a receiver, a transmitter, or a transceiver, such as an RF transceiver, configured to transmit and / or receive the information / signals via the wireless transmission medium, such as for information communicated between the RU 106a of the cell 190a and the base station 104e of the cell 190e via cross-cell communication beams 136-138 of the RU 106a and the base station 104e.

[0024] The RUs 106 may be configured to implement lower layer functionality. For example, the RU 106 is controlled by the DU 108 and may correspond to a logical node that hosts RF processing functions, or lower layer PHY functionality', such as execution of fast Fourier transform (FFT). inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc. The functionality of the RU 106 may be based on the functional split, such as a functional split of lower layers.

[0025] The RUs 106 may transmit or receive over-the-air (OTA) communication with one or more UEs 102. For example, the RU 106b of the cell 190b communicates with the UE 102b of the cell 190b via a first set of communication beams 132 of the RU 106b and a second set of communication beams 134b of the UE 102b, which may correspond to inter-cell communication beams or, in some examples, cross-cell communication beams. For instance, the UE 102b of the cell 190b may communicate with the RU 106a of the cell 190a via a third set of communication beams 134a of the UE 102b and a fourth set of communication beams 136 of the RU 106a. DUs 108 can control both real-time and non-real-time features of control plane and user plane communications of the RUs 106.

[0026] Any combination of the RU 106, the DU 108, and the CU 110, or reference thereto individually, may correspond to a base station 104. Thus, the base station 104 may include at least one of the RU 106, the DU 108, or the CU 110. The base stations 104 G114380 10120WOprovide the UEs 102 with access to a core network. The base stations 104 may relay communications between the UEs 102 and the core network (not shown). The base stations 104 may be associated with macrocells for higher-power cellular base stations and / or small cells for lower-power cellular base stations. For example, the cell 190e may correspond to a macrocell, whereas the cells 190a-190d may correspond to small cells. Small cells include femtocells, picocells, microcells, etc. A network that includes at least one macrocell and at least one small cell may be referred to as a “heterogeneous network.”

[0027] Transmissions from a UE 102 to a base station 104 / RU 106 are referred to as uplink (UL) transmissions, whereas transmissions from the base station 104 / RU 106 to the UE 102 are referred to as downlink (DL) transmissions. Uplink transmissions may also be referred to as reverse link transmissions and downlink transmissions may also be referred to as forward link transmissions. For example, the RU 106d utilizes antennas of the base station 104d of cell 190d to transmit a downlink / forward link communication to the UE 102d or receive an uplink / reverse link communication from the UE 102d based on the Uu interface associated with the access link between the UE 102d and the base station 104d / RU 106d.

[0028] Communication links between the UEs 102 and the base stations 104 / RUs 106 may be based on multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication links may be associated with one or more carriers. The UEs 102 and the base stations 104 / RUs 106 may utilize a spectrum bandwidth of Y MHz (e.g., 5, 10, 15, 20, 100, 400, 800, 1600, 2000, etc. MHz) per earner allocated in a carrier aggregation of up to a total of Yx MHz, where x component carriers (CCs) are used for communication in each of the uplink and downlink directions. The carriers may or may not be adjacent to each other along a frequency spectrum. In examples, uplink and downlink carriers may be allocated in an asymmetric manner, with more or fewer carriers allocated to either the uplink or the downlink. A primary component carrier and one or more secondary component carriers may be included in the component carriers. The primary component carrier may be associated w ith a primary cell (PCell) and a secondary component carrier may be associated with a secondary cell (SCell).

[0029] Some UEs 102, such as the UEs 102a and 102s, may perform device-to-device (D2D) communications over sidelink. For example, a sidelink communi cation / D2D link utilizes a spectrum for a wireless w ide area network (WWAN) associated with G114380 10120WOuplink and downlink communications. Such sidelink / D2D communication may be performed through various wireless communications systems, such as wireless fidelity (Wi-Fi) systems, Bluetooth systems, Long Term Evolution (LTE) systems, New Radio (NR) systems, etc.

[0030] The UEs 102 and the base stations 104 / RUs 106 may each include a plurality of antennas. The plurality of antennas may correspond to antenna elements, antenna panels, and / or antenna arrays that may facilitate beamforming operations. For example, the RU 106b transmits a downlink beamformed signal based on a first set of communication beams 132 to the UE 102b in one or more transmit directions of the RU 106b. The UE 102b may receive the downlink beamformed signal based on a second set of communication beams 134b from the RU 106b in one or more receive directions of the UE 102b. In a further example, the UE 102b may also transmit an uplink beamformed signal (e.g., sounding reference signal (SRS)) to the RU 106b based on the second set of communication beams 134b in one or more transmit directions of the UE 102b. The RU 106b may receive the uplink beamformed signal from the UE 102b in one or more receive directions of the RU 106b. The UE 102b may perform beam training to determine the best receive and transmit directions for the beamformed signals. The transmit and receive directions for the UEs 102 and the base stations 104 / RUs 106 may or may not be the same.

[0031] In further examples, beamformed signals may be communicated between a first base station / RU 106a and a second base station 104e. For instance, the base station 104e of the cell 190e may transmit a beamformed signal to the RU 106a based on the communication beams 138 in one or more transmit directions of the base station 104e. The RU 106a may receive the beamformed signal from the base station 104e of the cell 190e based on the RU communication beams 136 in one or more receive directions of the RU 106a. In further examples, the base station 104e transmits a downlink beamformed signal to the UE 102e based on the communication beams 138 in one or more transmit directions of the base station 104e. The UE 102e receives the dow nlink beamformed signal from the base station 104e based on UE communication beams 130 in one or more receive directions of the UE 102e. The UE 102e may also transmit an uplink beamformed signal to the base station 104e based on the UE communication beams 130 in one or more transmit directions of the UE 102e, such that the base station 104e may receive the uplink beamformed signal from the UE 102e in one or more receive directions of the base station 104e.G114380 10120WO

[0032] The base station 104 may include and / or be referred to as a NE. That is, “network entity7” may refer to the base station 104 or at least one unit of the base station 104, such as the RU 106, the DU 108, and / or the CU 110. The base station 104 may also include and / or be referred to as a next generation evolved Node B (ng-eNB), a next generation NB (gNB). an evolved NB (eNB), an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a TRP, a network node, network equipment, or other related terminology. The base station 104 or an entity at the base station 104 can be implemented as an IAB node, a relay node, a sidelink node, an aggregated (monolithic) base station, or a disaggregated base station including one or more RUs 106, DUs 108, and / or CUs 110. A set of aggregated or disaggregated base stations may be referred to as a next generation-radio access network (NG-RAN). In some examples, the UE 102a operates in dual connectivity (DC) with the base station 104e and the base station / RU 106a. In such cases, the base station 104e can be a master node and the base station / RU 160a can be a secondary node.

[0033] Still referring to FIG. 1, any of the UEs 102 may include a UE sensing controller 140 configured to transmit, to a serving NE, a sensing report comprising sensing data. The UE sensing controller 140 is configured to receive, from the serving NE based on the sensing data, a command to perform a mobility procedure with the neighbor NE. The UE sensing controller 140 is further configured to perform the mobility procedure with the neighbor NE.

[0034] The base stations 104 or a NE of the base stations 104 may include a NE sensing controller 150. When implemented in a serving NE. the NE sensing controller 150 is configured to obtain, upon detecting a triggering event, sensing data from a sensor associated with at least one of the serving NE, a UE, or a neighbor NE. The NE sensing controller 150 is further configured to transmit, to a UE and based on the sensing data, a command to perform a mobility procedure with the neighbor NE. When implemented in a neighbor NE, the NE sensing controller 150 is configured to transmit, to a serving NE, a sensing report including sensing data. The NE sensing controller 150 is configured to receive, from the serving NE based on the sensing data, a request to perform a mobility procedure with a UE. The NE sensing controller 150 is configured to transmit, to the serving NE, an acknowledgement to perform the mobility procedure. The NE sensing controller 150 is further configured to perform the mobility procedure with the UE.G114380 10120WO

[0035] Accordingly, FIG. 1 describes a wireless communication system that may be implemented in connection with aspects of one or more other figures described herein. Further, although the following description may be focused on 5G NR, the concepts described herein may be applicable to other similar areas, such as 5 G- Advanced and future versions, LTE, LTE-advanced (LTE-A), and other wireless technologies, such as 6G.

[0036] FIG. 2 is a signaling diagram illustrating a sensing-based mobility procedure 200, according to some implementations. The procedure 200 involves a serving NE 104S in communication with the UE 102. Based on the procedure 200, the serving NE 104S hands over the UE 102 to a neighbor NE 104N. The NEs 104S and 104N may each correspond to a base station or a unit of a base station, such as the RU 106, the DU 108, the CU 110, etc.

[0037] Among the apparatuses of the serving NE 104S, the neighbor NE 104N, and the UE 102, at least one apparatus is associated with or equipped with a sensing module, which includes one or more sensors, such as a visible light camera, an infrared light camera, a hygrometer, a thermometer, an audio device (e.g., microphone), a radio detection and ranging (RADAR) device (e.g., mono-static RADAR or bi-static RADAR), or a light detection and ranging (LIDAR) device. For example, the serving NE 104S includes a RADAR device under the control of a NE sensing controller 150 to detect physical objects in the vicinity of the serving NE 104S. Similarly, the UE 102 includes a camera under the control of a UE sensing controller 140 to capture the images in the vicinity of the UE 102. In some implementations, the serving NE 104S and the neighbor NE 104N each include an element of a bi-static RADAR device that operates under the control of the sensing controllers 150 of both NEs. The data generated by the sensing module may be referred to as sending data.

[0038] As illustrated, the serving NE 104S detects 210 an event that triggers sensing. The event may be based on internal operations of the serving NE 104S. As an example, the serving NE 104S detects the triggering of sensing after an expiry of a timer, which indicates the passage of a certain amount of time. As another example, the serving NE 104S detects the triggering of sensing after switching from a first connectivity or power state to another connectivity or power state.

[0039] Alternatively or additionally, the event may be based on the serving NE’s 104S interactions with other apparatuses or the external environment. As an example, the event is based on the serving NE’s 104S reception of a sensing report from the G114380 10120WOneighbor NE 104N or the UE 102, or based on the serving NE 104S obtaining a sensing result from these sensing reports or from a local sensing measurement (e.g., using the serving NE’s 104S own sensor). As another example, the event is based on the serving NE’s 104S determination that the sensing result indicates an object in a region of interest, or indicates that a difference between the sensing result and a previous sensing result satisfies (e.g., exceeds) a threshold.

[0040] As another example, the serving NE 104S detects the triggering of sensing upon receiving a downlink cellular signal measurement result (e.g.. a DLRS measurement result) from the UE 102. with the downlink cellular signal measurement result indicating a downlink cellular communication quality or a change of downlink cellular communication quality that satisfies a threshold. As another example, the serving NE 104S measures an uplink sounding reference signals (SRS) from the UE 102 and detects the triggering of sensing when the SRS quality measurement result indicates an uplink cellular communication quality or a change of uplink cellular communication quality that satisfies a threshold. As yet another example, the serving NE 104S detects the triggering of sensing upon receiving a request from the neighbor NE 104N, where the request may include sensing data obtained by the neighbor NE 104N. Other factors that may trigger sensing include, e.g., an ambient temperature or humidity, an interference level in the surroundings, a software or hardware update in the serving NE 104S, a computing or storage capacity of the serving NE 104S, and a network latency or congestion level as w ell as a change in the parameters described.

[0041] After the detection of the event that triggers sensing, the serving NE 104S performs 216 one or more operations to obtain sensing data. The serving NE 104S may obtain 216A the sensing data locally, e g., by performing 214S a local sensing measurement, which could be an SRS measurement, RADAR measurement, LIDAR measurement, camera measurement, and / or other combination of sensor measurements. The serving NE 104S may obtain 216B the sensing data from the neighbor NE 104N, e.g., by sending 212 a sensing request to the neighbor NE 104N and receiving 215 a sensing report from the neighbor NE 104N, with the sensing report including sensing data collected by the neighbor NE 104N in a sensing measurement 214N of the neighbor NE 104N. The serving NE 104S may also obtain 216C sensing data from the UE 102, e.g., by sending 218 a UE sensing configuration and receiving 220A UE sensing data from a sensing measurement 214A of the UEG114380 10120WO102. The operations at 216A, 216B, and 216C are collectively referred to as operations 216.

[0042] In some implementations, the serving NE 104S indicates a region of interest when sending 212 the sensing request to the neighbor NE 104N, and the neighbor NE 104N configures the sensor to collect sensing data from the region of interest. The serving NE 104S may determine the region of interest based on, e g., a predicted movement or trajectory of the UE 102, which the serving NE 104S obtains from historical measurements. For example, when the serving NE 104S determines that the signal strength received from the UE 102 in a particular direction exceeds a threshold, the serving NE 104S designates a region corresponding to the particular direction as the region of interest and requests the neighbor NE 104N to perform sensing accordingly.

[0043] In some implementations, the neighbor NE 104N performs 214N the sensing measurement and sends 215 the sensing report autonomously, e.g., without receiving 212 the sensing request. As an example, the neighbor NE 104N periodically performs local sensing to monitor the surroundings of the neighbor NE 104. Upon detecting certain sensing activities, e.g., a vehicle entering the surroundings of the neighbor NE 104N and blocking the radio propagation from the neighbor NE 104N, the neighbor NE 104N transmits 215 a sensing report to the serving NE 104S. Regardless of whether the neighbor NE 104N sends the sensing report autonomously or at the request of the serving NE 104S, the neighbor NE 104N may include in the sensing report information about, e.g., the surroundings of the neighbor NE 104N or the sensing activities detected by the neighbor NE 104N.

[0044] Similarly, the UE 102 may perform 214A sensing measurement autonomously or upon receiving 218 the UE sensing configuration from the serving NE 104S. The UE sensing configuration may be an air interface resource configuration including configurations for the UE 102 to obtain 214A or transmit 220 A the sensing data to the serving NE 104S. Along with UE sensing data, the UE 102 may include, in a sensing report, information about the surroundings of the UE 102 or sensing activities detected by the UE 102. In some implementations, the UE 102 sends 220A the UE sensing data along with downlink cellular measurement results (e.g., RSRP, RS SI, or reference signal received quality (RSRQ)), an indication of a UE mobility event, or UE context information (e.g., the UE 102 moving based on a scheduled event).

[0045] In some implementations, the serving NE 104S performs only a subset of operations 216 as triggered 210. In other w ords, the serving NE 104S may obtain 216 G114380 10120WOsensing data without one ortwo of: performing the local measurement 2I4S. receiving 215 the sensing report from the neighbor NE 104N, or receiving 220A UE sensing data from the UE 102. In an example, the serving NE 104S obtains 216A a first portion of sensing data from the local measurement 214S of the serving NE 104S and obtains 216B a second portion of sensing data from the neighbor NE 104N, but does not request 218 or receive 220 A UE sensing data as a result of the triggering event. In some examples, the serving UE NE 104S received sensing data from the UE earlier (not shown). As another example, the serving NE 104S obtains 216B the second portion of sensing data from the neighbor NE 104N and obtains 216C a third portion of sensing data from the UE 102, but does not perform 214S the local measurement. As another example, the serving NE 104S obtains 216A the first portion of sensing data from the local measurement 214S of the serving NE 104S and obtains 216C a third portion of sensing data from the UE 102, but does not request 212 or receive 215 sensing data from the neighbor NE 104N in response to the triggering event.

[0046] Further, the illustration of the operations 216 does not necessarily mean that these operations are performed in a chronological order, and does not necessarily mean that these operations are performed after the triggering event 210. As an example, the serving NE 104S obtains 216A sensing data from a local measurement 214S after obtaining 216B sensing data from the neighbor NE 104N. As another example, the serving NE 104S obtains 216C sensing data from the UE 102 contemporaneously with obtaining 216B sensing data from the neighbor NE 104N. As yet another example, the UE 102 autonomously performs 214A sensing measurement and transmits 220 A UE sensing data to the serving NE 104S before the triggering event 210, and the serving NE 104S treats the reception 220A of the UE sensing data as the triggering event 210. More generally, each of the three apparatuses (the UE 102, the serving NE 104S. and the neighbor NE 104N) may perform sensing measurement at same or different times with respect to the other apparatuses.

[0047] The serving NE 104S makes 224 a handover decision based on the sensing data obtained from the operations 216. In some implementations, this handover decision augments existing handover and mobility decision making such as lower-layer triggered mobility (LTM), dual connectivity mobility, and other variants. The handover decision includes, e.g., whether to hand the UE 102 over to the neighbor NE 104N, when to perform the handover, and whether the handover is an unconditionalG114380 10120WOhandover or a conditional handover. In some implementations, the serving NE 104S makes 224 the handover decision jointly with the neighbor NE 104N.

[0048] In some implementations, the serving NE 104S makes 224 the handover decision using a machine learning (ML) model, such as a neural network, which may be hosted on the serving NE 104S or on a core network entity. For example, the ML model predicts, based on the sensing data, which of the serving NE 104S and the neighbor NE 104N is likely to provide better communication quality with the UE 102 at a given time. The ML model may be trained to simulate the physical electromagnetic wave propagation (e.g., via ray-tracing within a digital twin model) and may receive the sensing data along with the UE’s 102 movement as inputs. By deploying the ML mode, the serving NE 104S obtains a timing for handing over the UE 102 to the neighbor NE 104N. Alternatively or additionally, the serving NE 104S determines to perform a conditional handover and obtains a configuration for the conditional handover using the ML model. The configuration for the conditional handover includes, e.g., a desired lower layer measurement (e.g., RSRP, or SINR) for the UE 102 to trigger the conditional handover.

[0049] Based on the handover decision, the serving NE 104S optionally transmits 226 a handover request to the neighbor NE 104N and receives 228 a handover request acknowledgement from the neighbor NE 104N. The handover request acknowledgement may include an updated sensing configuration for the UE 102 to perform updated sensing and report updated sensing results to the neighbor NE 104N.

[0050] The serving NE 104S transmits 230 a handover command to the UE 102. The serving NE 104S may transmit 230 the handover command within a radio resource control (RRC) reconfiguration message. When the handover is an unconditional handover, the command instructs the UE 102 to perform the handover immediately. When the handover is a conditional handover, the command configures the UE 102 to perform the handover upon satisfying a condition, e.g.. upon detecting a handover triggering event at the UE. The serving NE 104S may forward the updated sensing configuration to the UE 102 in the handover command.

[0051] In response to the handover command, the UE 102 establishes 232 a connection with the neighbor NE 104N. As such, the neighbor NE 104N begins to provide the wireless services to the UE 102 in lieu of the serving NE 104S.

[0052] In some implementations, the UE 102 optionally performs 214B an updated sensing measurement to collect sensing data during the handover or after completing G114380 10120WOthe handover. The UE 102 transmits 220B the updated UE sensing data to the neighbor NE 104N. The UE 102 may perform 214B the updated sensing measurement according to a configuration received from the serving NE 104S in the handover command.

[0053] Although the above description of the procedure 200 is in the context of a handover procedure including conditional handover, the procedure 200 may additionally or alternatively involve other types of mobility' procedure, such as a primary cell (PCell) change, a primary secondary cell (PSCell) change, a secondary node (SN) addition or change, a conditional PCell change, a conditional PSCell addition or change, or lower-layer triggered mobility (LTM). The serving NE 104S may determine the type and the timing of the mobility procedure based on the sensing data obtained 216 from local measurement or received from the neighbor NE 104N or the UE 102.

[0054] FIG. 2 illustrates a sensing-based mobility procedure 200 among a UE 102, a serving NE 104S, and neighbor NE 104N, whereas FIGs. 3-8 shows methods of implementing one or more aspects of FIG. 2.

[0055] FIG. 3 is a flowchart illustrating a sensing-based mobility procedure 300 at a serving NE, according to some implementations. The procedure 300 may be an implementation by the serving NE 104S of one or more aspects of the procedure 200 of FIG. 2.

[0056] According to the procedure 300, the serving NE 104S detects 310A an event that triggers sensing. Based on the detection, the serving NE 104S obtains sensing data from one or more apparatuses.

[0057] In some implementations, the serving NE 104S obtains 316A local sensing data by performing a local sensing measurement. Alternatively or additionally, the serving NE 104S transmits 312 a sensing request to a neighbor NE 104N and receives 315 sensing data in a sensing report from the neighbor NE 104N. Alternatively or additionally, the serving NE 104S transmits 318 a sensing configuration to a UE 102 and receives 320A UE sensing data in a sensing report from the UE. Similar to the procedure 200, the operations at 310-318 may have different chronological orders in different implementations.

[0058] The serving NE 104S decides 324 to perform a mobility procedure, such as a handover procedure. Based on the decision, the serving NE 104S transmits 326 a handover request to the neighbor NE 104N and receives an acknowledgement from G114380 10120WOthe neighbor NE 104N. The serving NE 104S then transmits 330 a command to the UE 102 to perform the mobility procedure.

[0059] FIG. 4 is a flowchart illustrating a sensing-based mobility procedure 400 at a UE, according to some implementations. The procedure 400 may be an implementation by the UE 102 of one or more aspects of the procedure 200 of FIG. 2.

[0060] According to the procedure 400, the UE 102 receives 418 a sensing configuration from a serving NE 104S. Based on the sensing configuration, the UE 102 performs 414A a measurement to obtain UE sensing data and transmits 420A the UE sensing data to the serving NE 104S.

[0061] The UE 102 then receives 430 a command to perform a mobility procedure from the serving NE 104S. According to the command, the UE 102 performs the procedure by establishing 432 a connection with a neighbor NE 104N.

[0062] The UE 102 optionally performs 414B an updated sensing measurement to obtain updated UE sensing data. The UE 102 then transmits 420B the updated UE sensing data to the neighbor NE 104N.

[0063] FIG. 5 is a flowchart illustrating a sensing-based mobility procedure 500 at a neighbor NE according to some implementations. The procedure 500 may be an implementation by the neighbor NE 104N of one or more aspects of the procedure 200 of FIG. 2.

[0064] According to the procedure 500, the neighbor NE 104N receives 512 a sensing request from a serving NE 104S. In response to the sensing request, the neighbor NE 104N performs 514N a sensing measurement to obtain sensing data and transmits 515 the sensing data in a sensing report to the serving NE 104S.

[0065] The neighbor NE 104N then receives 526 a request, such as a handover request, from the serving NE 104S to perform a mobility procedure with a UE 102. In response, the neighbor NE 104N transmits 528 an acknowledgement to the request and performs 532 the mobility procedure to establish a connection with the UE 102. In some implementations, the neighbor NE 104N optionally receives 520B updated sensing data from the UE 102.

[0066] FIG. 6 is a flowchart of a method 600 of wireless communication at a serving NE 104S. according to some implementations. With reference to FIGs. 1-5, the method 600 may be performed by the serving NE 104S.

[0067] According to one or more implementations, the serving NE 104S, upon detecting a triggering event, obtains 616 sensing data from a sensor associated with the serving G114380 10120WONE 104S or a second sensor associated with a neighbor NE 104N. In some implementations, the serving NE 104S also obtains sensing data from a UE 102.

[0068] Based on the sensing data, the serving NE 104S transmits 630 a command to the UE 102. The command instructs or configures the UE 102 to perform a mobility procedure with the neighbor NE 104N.

[0069] FIG. 7 is a flowchart of a method 700 of wireless communication at a UE, according to some implementations. With reference to FIGs. 1-5, the method 600 may be performed by the UE 102.

[0070] According to one or more implementations, the UE 102 transmits 720A, to a serving NE 104S, a sensing report including sensing data. As discussed above, the transmission of the sensing report may be autonomous or at the request of the serving NE 104S.

[0071] The UE 102 then receives 730, from the serving NE 104S, a command to perform a mobility procedure with the neighbor NE 104N. In response, the UE 102 performs 732 the mobility procedure to establish a connection with the neighbor NE 104N.

[0072] FIG. 8 is a flowchart of a method 800 of wireless communication at a neighbor NE, such as the neighbor NE 104N, according to some implementations.

[0073] According to one or more implementations, the neighbor NE 104N transmits 815.to a serving NE 104S, a sensing report including sensing data. As discussed above, the transmission of the sensing report may be autonomous or at the request of the serving NE 104S.

[0074] The neighbor NE 104N then receives 826 a request, such as a handover request, from the serving NE 104S, to perform a mobility procedure with a UE 102. In response, the neighbor NE 104N transmits 828 an acknowledgement to the request and performs 832 the mobility procedure to establish a connection with the UE 102.

[0075] A UE apparatus 902, as described in FIG. 9, may perform the method 700 in FIG.7. The one or more NEs 104, as described in FIG. 10. may perform the methods 600 and 800 in FIGs. 6 and 8, respectively.

[0076] FIG. 9 is a diagram 900 illustrating an example of a hardware implementation for a UE apparatus 902. The UE apparatus 902 may be the UE 102 or a component of the UE 102, or may implement UE functionality. The UE apparatus 902 may include an application processor 906, which may have on-chip memory 906’. In examples, the application processor 906 may be coupled to a secure digital (SD) card 908 and / or a display 910. The application processor 906 may also be coupled to a sensor(s) G114380 10120WOmodule 912, a power supply 914, an additional module of memory 916, a camera 918, and / or other related components. For example, the sensor(s) module 912 may control a barometric pressure sensor / altimeter, a motion sensor such as an inertial management unit (IMU), a gyroscope, accelerometer(s). a LIDAR device, a RADAR device, a sound navigation and ranging (SONAR) device, a magnetometer, an audio device, and / or other technologies used for positioning.

[0077] The UE apparatus 902 may further include a wireless baseband processor 926, which may be referred to as a modem. The wireless baseband processor 926 may have on-chip memory’ 926'. Along with, and similar to, the application processor 906. the wireless baseband processor 926 may also be coupled to the sensor(s) module 912, the power supply 914, the additional module of memory 916, the camera 918, and / or other related components. The wireless baseband processor 926 may be additionally- coupled to one or more subscriber identity module (SIM) card(s) 920 and / or one or more transceivers 930 (e.g., wireless RF transceivers).

[0078] Within the one or more transceivers 930, the UE apparatus 902 may include a Bluetooth module 932, a WLAN module 934, an SPS module 936 (e.g., GNSS module), and / or a cellular module 938. The Bluetooth module 932, the WLAN module 934, the SPS module 936. and the cellular module 938 may each include an on-chip transceiver (TRX), or in some cases, just a transmitter (TX) or just a receiver (RX). The Bluetooth module 932, the WLAN module 934, the SPS module 936, and the cellular module 938 may each include dedicated antennas and / or utilize antennas 940 for communication with one or more other nodes. For example, the UE apparatus 902 can communicate through the transceiver(s) 930 via the antennas 940 with another UE (e g., sidelink communication) and / or with a NE 104 (e.g., upl ink / downl ink communication), where the NE 104 may correspond to a base station or a unit of the base station, such as the RU 106. the DU 108, or the CU 110.

[0079] The wireless baseband processor 926 and the application processor 906 may each include a computer-readable medium / memory 926', 906', respectively. The additional module of memory 916 may also be considered a computer-readable medium / memory. Each computer-readable medium / memory 926', 906', 916 may be non-transitory . The wireless baseband processor 926 and the application processor 906 may each be responsible for general processing, including execution of software stored on the computer-readable medium / memory 926', 906', 916. The software, when executed by the wireless baseband processor 926 / application processor 906, G114380 10120WOcauses the wireless baseband processor 926 / application processor 906 to perform the various functions described herein. The computer-readable medium / memory may also be used for storing data that is manipulated by the wireless baseband processor 926 / application processor 906 when executing the software. The wireless baseband processor 926 I application processor 906 may be a component of the UE 102. The UE apparatus 902 may be a processor chip (e.g., modem and / or application) and include just the wireless baseband processor 926 and / or the application processor 906. In other examples, the UE apparatus 902 may be the entire UE 102 and include the additional modules of the apparatus 902.

[0080] As discussed in FIG. 1 and implemented with respect to FIG. 7, the UE sensing controller 140 is configured to transmit, to a serving NE, a sensing report comprising sensing data. The UE sensing controller 140 is configured to receive, from the serving NE based on the sensing data, a command to perform a mobility procedure with the neighbor NE. The UE sensing controller 140 is further configured to perform the mobility procedure with the neighbor NE.

[0081] The UE sensing controller 140 may be within the application processor 906 (e.g., at 140a), the wireless baseband processor 926 (e.g., at 140b), or both the application processor 906 and the wireless baseband processor 926. The UE sensing controller 140a- 140b may be one or more hardware components specifically configured to carry out the stated processes / algorithm, implemented by one or more processors configured to perform the stated processes / algorithm, stored within a computer- readable medium for implementation by the one or more processors, or a combination thereof.

[0082] FIG. 10 is a diagram 1000 illustrating an example of a hardware implementation for one or more NEs 104. The one or more NEs 104 may be a base station, a component of a base station, or may implement base station functionality. The one or more NEs 104 may include, or may correspond to, at least one of the RU 106. the DU, 108, or the CU 110. The CU 110 may include a CU processor 1046, which may have on-chip memory 1046'. In some aspects, the CU 110 may further include an additional module of memory 1056 and / or a communications interface 1048, both of which may be coupled to the CU processor 1046. The CU 110 can communicate with the DU 108 through a midhaul link 162, such as an Fl interface between the communications interface 1048 of the CU 110 and a communications interface 1028 of the DU 108.G114380 10120WO

[0083] The DU 108 may include a DU processor 1026, which may have on-chip memory 1026'. In some aspects, the DU 108 may further include an additional module of memory' 1036 and / or the communications interface 1028, both of which may be coupled to the DU processor 1026. The DU 108 can communicate with the RU 106 through a fronthaul link 160 between the communications interface 1028 of the DU 108 and a communications interface 1008 of the RU 106.

[0084] The RU 106 may include an RU processor 1006, which may have on-chip memory 1006'. In some aspects, the RU 106 may further include an additional module of memory 1016, the communications interface 1008, and one or more transceivers 1030, all of which may be coupled to the RU processor 1006. The RU 106 may further include antennas 1040, which may be coupled to the one or more transceivers 1030, such that the RU 106 can communicate through the one or more transceivers 1030 via the antennas 1040 with the UE 102.

[0085] The on-chip memory 1006', 1026'. 1046' and the additional modules of memory 1016, 1036, 1056 may each be considered a computer-readable medium / memory. Each computer-readable medium / memory- may be non-transitory. Each of the processors 1006, 1026, 1046 is responsible for general processing, including execution of software stored on the computer-readable medium / memory. The software, when executed by the corresponding processor(s) 1006, 1026, 1046 causes the processor(s) 1006, 1026, 1046 to perform the various functions described herein. The computer-readable medium / memory' may also be used for storing data that is manipulated by the processor(s) 1006. 1026, 1046 when executing the software. In examples, the NE sensing controller 150 may sit at any of the one or more NEs 104, such as at the CU 110; both the CU 110 and the DU 108; each of the CU 110, the DU 108, and the RU 106; the DU 108; both the DU 108 and the RU 106; or the RU 106.

[0086] As discussed in FIG. 1 and implemented with respect to FIG. 6, the NE sensing controller 150. when implemented in a serving NE. is configured to obtain, upon detecting a triggering event, sensing data from a sensor associated with at least one of the serving NE, a UE, or a neighbor NE. The NE sensing controller 150 is further configured to transmit, to a UE and based on the sensing data, a command to perform a mobility procedure with the neighbor NE.

[0087] As discussed in FIG. 1 and implemented with respect to FIG. 8 the NE sensing controller 150, when implemented in a neighbor NE, is configured to transmit, to a serving NE, a sensing report including sensing data. The NE sensing controller 150 G114380 10120WOis configured to receive, from the serving NE based on the sensing data, a request to perform a mobility procedure with a UE. The NE sensing controller 150 is configured to transmit, to the serving NE, an acknowledgement to perform the mobility procedure. The NE sensing controller 150 is further configured to perform the mobility procedure with the UE.

[0088] The NE sensing controller 150 may be within one or more processors of the one or more NEs 104, such as the RU processor 1006 (e.g., at 150a), the DU processor 1026 (e.g., at 150b), and / or the CU processor 1046 (e.g., at 150c). The NE sensing controller 150a- 150c may be one or more hardware components specifically configured to carry out the stated processes / algorithm, implemented by one or more processors 1006, 1026, 1046 configured to perform the stated processes / algorithm, stored within a computer-readable medium for implementation by the one or more processors 1006, 1026, 1046, or a combination thereof.

[0089] The specific order or hierarchy of blocks in the processes and flowcharts disclosed herein is an illustration of example approaches. Hence, the specific order or hierarchy of blocks in the processes and flowcharts may be rearranged. Some blocks may also be combined or deleted. Dashed lines may indicate optional elements of the diagrams. The accompanying method claims present elements of the various blocks in an example order, and are not limited to the specific order or hierarchy presented in the claims, processes, and flowcharts.

[0090] The detailed description set forth herein describes various configurations in connection with the drawings and does not represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough explanation of various concepts. However, these concepts may be practiced without these specific details. In some instances, well known structures and components are shown in block diagram form in order to avoid obscuring such concepts.

[0091] Aspects of wireless communication systems, such as telecommunication systems, are presented with reference to various apparatuses and methods. These apparatuses and methods are described in the following detailed description and are illustrated in the accompanying drawings by various blocks, components, circuits, processes, call flows, systems, algorithms, etc. (collectively referred to as '‘elements”). These elements may be implemented using electronic hardware, computer software, or combinations thereof. Whether such elements are implemented as hardware or G114380 10120WOsoftware depends upon the particular application and design constraints imposed on the overall system.

[0092] An element, or any portion of an element, or any combination of elements may be implemented as a “processing system” that includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems-on-chip (SoC), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other similar hardware configured to perform the various functionality described throughout this disclosure. One or more processors in the processing system may execute software, which may be referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, or any combination thereof.

[0093] If the functionality described herein is implemented in software, the functions may be stored on, or encoded as, one or more instructions or code on a computer-readable medium, such as a non-transitory computer-readable storage medium. Computer- readable media includes computer storage media and can include a random-access memory (RAM), a read-only memory (ROM), an electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of these types of computer-readable media, or any other medium that can be used to store computer executable code in the form of instructions or data structures that can be accessed by a computer. Storage media may be any available media that can be accessed by a computer. The functionality described herein may also be implemented as a computer program product.

[0094] Aspects, implementations, and / or use cases described herein may be implemented across many differing platform ty pes, devices, systems, shapes, sizes, and packaging arrangements. For example, the aspects, implementations, and / or use cases may come about via integrated chip implementations and other non-module-component based devices, such as end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, artificial G114380 10120WOintelligence (Al)-enabled devices, machine learning (ML)-enabled devices, etc. The aspects, implementations, and / or use cases may range from chip-level or modular components to non-modular or non-chip-level implementations, and further to aggregate, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more techniques described herein.

[0095] Devices incorporating the aspects and features described herein may also include additional components and features for the implementation and practice of the claimed and described aspects and features. For example, transmission and reception of wireless signals necessarily includes a number of components for analog and digital purposes, such as hardware components, antennas, RF-chains, power amplifiers, modulators, buffers, processor(s), interleavers, adders / summers, etc. Techniques described herein may be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc., of varying configurations.

[0096] The description herein is provided to enable a person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not limited to the aspects described herein, but are to be interpreted in view of the full scope of the present disclosure consistent with the language of the claims.

[0097] Reference to an element in the singular does not mean “one and only one'’ unless specifically stated, but rather “one or more.” Terms such as “if,” “when,” and “while” do not imply an immediate temporal relationship or reaction. That is, these phrases, e.g., “when,” do not imply an immediate action in response to or during the occurrence of an action, but simply imply that if a condition is met then an action will occur, but without requiring a specific or immediate time constraint for the action to occur. The terms “may”, “might”, and “can”, as used in this disclosure, often carry certain connotations. For example, “may” refers to a permissible feature that may or may not occur, “might” refers to a feature that probably occurs, and “can” refers to a capability (e.g., capable of). The phrase “For example” often carries a similar connotation to “may” and. therefore, “may” is sometimes excluded from sentences that include “for example” or other similar phrases.

[0098] Unless specifically stated otherwise, the term “some” refers to one or more.Combinations such as “at least one of A, B, or C” or “one or more of A, B, or G114380 10120WOC” include any combination of A, B, and / or C, such as A and B, A and C, B and C, or A and B and C, and may include multiples of A, multiples of B, and / or multiples of C, or may include A only, B only, or C only. Sets should be interpreted as a set of elements where the elements number one or more. Terms or articles such as “a”, “an”, and / or “the” may refer to one of an item, feature, element, etc., that the term or article precedes, or may refer to more than one of said item, feature, element, etc. that the term or article precedes. For example, the recitation “a widget” does not preclude reference to multiples of said widget, as “multiple widgets” necessarily includes “a widget”. Hence, the recitation “a widget” may be interpreted as “at least one widget” or, similarly, interpreted as “one or more widgets”.

[0099] Unless otherwise specifically indicated, ordinal terms such as “first” and “second” do not necessarily imply an order in time, sequence, numerical value, etc., but are used to distinguish between different instances of a term or phrase that follows each ordinal term.

[0100] Reference numbers, as used in the specification and figures, are sometimes cross- referenced among drawings to denote same or similar features. A feature that is exactly the same in multiple drawings may be labeled with the same reference number in the multiple drawings. A feature that is similar among the multiple drawings, but not exactly the same, may be labeled with reference numbers that have different leading numbers but have one or more of the same trailing numbers (e.g., 206, 306, 406, etc., may refer to similar features in the drawings). Hence, like numbers may refer to like actions.

[0101] Structural and functional equivalents to elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are encompassed by the claims. The words “module,” “mechanism,” “element,” “device,” and the like may not be a substitute for the word “means.” As such, no claim element is to be construed as a means plus function unless the element is expressly recited using the phrase “means for.” As used herein, the phrase “based on” shall not be construed as a reference to a closed set of information, one or more conditions, one or more factors, or the like. In other words, the phrase “based on A”, where “A” may be information, a condition, a factor, or the like, shall be construed as “based at least on A” unless specifically recited differently.G114380 10120WO

[0102] The following examples are illustrative only and may be combined with other examples or teachings described herein, without limitation.

[0103] Example 1 is a method of wireless communication at a serving network entity, including: detecting (210), by the serving network entity (104S), a sensing-triggering event; obtaining, from a sensor associated with at least one of: the serving network entity, a neighbor network entity, or a user equipment, UE, sensing data upon the detecting (210); and transmitting, to the UE based on the sensing data, a command to perform a mobility procedure with the neighbor network entity7.

[0104] Example 2 may be combined with the method of Example 1 , wherein the obtaining the sensing data includes: transmitting, to the neighbor network entity, a request for the sensing data; and receiving, from the neighbor network entity, a sensing report including the sensing data.

[0105] Example 3 may be combined with the method of Example 2, wherein the request indicates a region of interest.

[0106] Example 4 may be combined with the method of any of Examples 1-3, wherein the sensing-triggering event includes at least one of: receiving a first sensing report from the neighbor network entity; receiving a second sensing report from the UE; obtaining a sensor measurement result that satisfies a first condition; obtaining an uplink cellular measurement result that satisfies a second condition; receiving a downlink cellular measurement result that satisfies a third condition; or detecting that a time period has passed.

[0107] Example 5 may be combined with the method of Example 4, wherein the first condition includes at least one of: detecting an object in a region of interest; or a difference betw een the sensor measurement result and a previous sensor measurement result satisfying a first threshold.

[0108] Example 6 may be combined with the method of Example 4 or 5, wherein the second condition includes: the serving network entity detecting that a quality of a sounding reference signal, SRS, satisfies a second threshold.

[0109] Example 7 may be combined with the method of any of Examples 4-6, wherein the third condition includes: the UE reporting that a quality of a downlink reference signal, DLRS, satisfies a third threshold.

[0110] Example 8 may be combined with the method of any of Examples 1-7, wherein the obtaining the sensing data includes: transmitting, to the UE, a request for the sensing data; and receiving, from the UE, a sensing report including the sensing data. G114380 10120WO

[0111] Example 9 may be combined with the method of any of Examples 1-8, wherein a type of the mobility procedure includes at least one of: a handover, a primary cell, PCell, change, a primary secondary' cell, PSCell, change, a secondary' node, SN, addition or change, a conditional handover, a conditional PCell change, a conditional PSCell addition or change, or lower-layer triggered mobility. LTM, and wherein the method further includes: determining, based on the sensing data, a timing of the mobility procedure, or the type of the mobility' procedure.

[0112] Example 10 may be combined with the method of Example 9, wherein the determining the at least one of: the timing of the mobility procedure, or the type of the mobility procedure includes: determining, based on the sensing data, radio wave propagation information; and determining, based on the radio wave propagation information and using a machine learning model, the at least one of: the timing of the handover procedure, or the type of the handover procedure.

[0113] Example 11 may be combined with the method of any of Examples 1-10, wherein the sensing data is obtained from one or more sensors of the serving network entity.

[0114] Example 12 is a method of wireless communication at a user equipment, UE„ including: transmitting, to a serving network entity, a sensing report including sensing data obtained from one or more sensors of the UE; receiving, from the serving network entity, a command to perform a mobility procedure with a neighbor network entity; and performing the mobility procedure with the neighbor network entity.

[0115] Example 13 may be combined with the method of Example 12, further including:transmitting, to the serving network entity, a downlink cellular signal measurement result.

[0116] Example 14 may be combined with the method of Example 12 or 13, further including: receiving, from the serving network entity, an air interface resource configuration for at least one of obtaining or transmitting the sensing data.

[0117] Example 15 may be combined with the method of any of Examples 12-14, wherein a type of the mobility procedure includes at least one of: a handover, a primary cell, PCell, change, a primary secondary cell, PSCell, change, a secondary' node, SN, addition or change, a conditional handover, a conditional PCell change, a conditional PSCell addition or change, or lower-layer triggered mobility, LTM, and wherein the command includes at least one of: a timing of the mobility procedure, or the type of the mobility procedure.G114380 10120WO

[0118] Example 16 may be combined with the method of Example 15, further including: obtaining updated sensing data based on the command; and transmitting, to the neighbor network entity, updated sensing data after completing the mobility procedure.

[0119] Example 17 may be combined with the method of any of the preceding any of Examples, wherein the mobility procedure is a conditional handover procedure, and wherein the command includes a configuration of the conditional handover procedure.

[0120] Example 18 may be combined with the method of Example 17, wherein the configuration of the conditional handover procedure includes a lower layer measurement threshold value for triggering the conditional handover procedure.

[0121] Example 19 may be combined with the method of any of the preceding any of Examples, wherein the command includes a sensing configuration that configures at least one of obtaining or transmitting updated sensing data for the neighbor network entity.

[0122] Example 20 is a method of wireless communication at a neighbor network entity, including: transmitting, to a serving network entity, a sensing report including sensing data obtained from one or more sensors of the neighbor network entity; receiving, from the serving network entity, a request to perform a mobility procedure with a user equipment, UE,; transmitting, to the serving network entity, an acknowledgement to perform the mobility procedure; and performing the mobility procedure with the UE according to the request.

[0123] Example 21 may be combined with the method of Example 20, further including:receiving, from the UE, updated sensing data.

[0124] Example 22 may be combined with the method of Example 20 or 21, wherein a type of the mobility procedure includes at least one of: a handover, a secondary7node, SN, addition or change, or a conditional handover.

[0125] Example 23 may be combined with the method of any of Examples 20-22, wherein the acknowledgement includes a configuration that configures the UE to obtain updated sensing data.

[0126] Example 24 may be combined with the method of any of the preceding any of Examples, wherein the sensing data includes at least one of: visible light camera data, infrared camera data, radio detection and ranging, RADAR, data, light detection and ranging, LiDAR, data, hygrometer data, thermometer data, or audio data.G114380 10120WO

[0127] Example 25 is an apparatus for wireless communication including a memory, a transceiver, and a processor coupled to the memory and the transceiver, the apparatus being configured to implement a method as in any of Examples 1 -24.

[0128] Example 26 is a non-transitory computer-readable medium storing computer executable code, the code when executed by a processor causes the processor to implement a method as in any of Examples 1-24

[0129] Example 27 is a computer program product for implementing a method as in any of Examples 1-24.G114380 10120WO

Claims

CLAIMSWHAT IS CLAIMED IS:

1. A method of wireless communication at a serving network enti ty ( 104S), comprising:detecting (210), by the serving network entity ( 104S), a sensing-triggering event; obtaining (216), from a sensor associated with at least one of: the serving network entity (104S), aneighbor network entity (104N), or a user equipment, UE, (102), sensing data upon the detecting (210); andtransmitting (230). to the UE (102) based on the sensing data, a command to perform a mobility procedure with the neighbor network entity (104N).

2. The method of claim 1, wherein the obtaining (216) the sensing data comprises: transmitting (212). to the neighbor network entity (104N). a request for the sensing data; andreceiving (215), from the neighbor network entity (104N), a sensing report comprising the sensing data.

3. The method of claim 2, wherein the request indicates a region of interest.

4. The method of any of claims 1-3, wherein the sensing-triggering event comprises at least one of:receiving a first sensing report from the neighbor network entity (104N); receiving a second sensing report from the UE;obtaining a sensor measurement result that satisfies a first condition; obtaining an uplink cellular measurement result that satisfies a second condition; receiving a downlink cellular measurement result that satisfies a third condition;ordetecting that a time period has passed.

5. The method of claim 4, wherein the first condition comprises at least one of:detecting an object in a region of interest; ora difference between the sensor measurement result and a previous sensor measurement result satisfying a first threshold.

6. The method of claim 4 or 5, wherein the second condition comprises:G114380 10120WOthe serving network entity (104S) detecting that a quality of a sounding reference signal, SRS, satisfies a second threshold.

7. The method of any of claims 4-6, wherein the third condition comprises:the UE (102) reporting that a quality of a downlink reference signal, DLRS, satisfies a third threshold.

8. The method of any of claims 1-7, wherein the obtaining (216) the sensing data comprises:transmitting (218), to the UE, a request for the sensing data; andreceiving (220A), from the UE, a sensing report comprising the sensing data.

9. The method of any of claims 1 -8, wherein a type of the mobility procedure comprises at least one of: a handover, a primary cell, PCell, change, a primary secondary cell, PSCell, change, a secondary node, SN, addition or change, a conditional handover, a conditional PCell change, a conditional PSCell addition or change, or lower-layer triggered mobility, LTM. and wherein the method further comprises:determining, based on the sensing data, a timing of the mobility procedure, or the type of the mobility procedure.

10. The method of claim 9, wherein the determining the at least one of: the timing of the mobility procedure, or the type of the mobility procedure comprises:determining, based on the sensing data, radio wave propagation information; and determining, based on the radio wave propagation information and using a machine learning model, the at least one of: the timing of the handover procedure, or the type of the mobility procedure.

11. A method of wireless communication at a user equipment, UE, (102), comprising:transmitting (220A). to a serving network entity (104S). a sensing report comprising sensing data obtained from one or more sensors of the UE; receiving (230), from the serving network entity (104S), a command to perform a mobility procedure with a neighbor network entity (104N); and performing (232) the mobility procedure with the neighbor network entity (104N).G114380 10120WO12. The method of claim 11. further comprising: receiving (218), from the serving network entity (104S), an air interface resource configuration for at least one of obtaining (214A) or transmitting (220 A) the sensing data.

13. The method of any of claims 11-12,wherein a type of the mobility procedure comprises at least one of: a handover, a primary cell, PCell, change, a primary secondary cell, PSCell, change, a secondary node, SN, addition or change, a conditional handover, a conditional PCell change, a conditional PSCell addition or change, or lower-layer triggered mobility, LTM, andwherein the command comprises at least one of: a timing of the mobility7procedure, or the type of the mobility procedure.

14. The method of claim 13, further comprising:obtaining (214B) updated sensing data based on the command; and transmitting (220B), to the neighbor network entity' (104N), updated sensing data after completing the mobility procedure.

15. The method of claim 14, wherein the command comprises a configuration of a conditional handover procedure, and the configuration of the conditional handover procedure comprises a lower layer measurement threshold value for triggering the conditional handover procedure.

16. A method of wireless communication at a neighbor network entity (104N), comprising:transmitting (215), to a serving network entity (104S), a sensing report comprising sensing data obtained from one or more sensors of the neighbor network entity;receiving (226), from the serving network entity' (104S), a request to perform a mobility procedure with a user equipment, UE, (102);transmitting (228), to the serving network entity (104S), an acknowledgement to perform the mobility procedure; andperforming (232) the mobility' procedure with the UE (102) according to the request.G114380 10120WO17. An apparatus for wireless communication compnsing a memory, a transceiver, and a processor coupled to the memory and the transceiver, the apparatus being configured to implement a method as in any of claims 1-16.G114380 10120WO

Images