Predicted event triggers for mobility procedures

Abstract

A user equipment (UE), baseband processor, and network device are described. The UE (or a baseband processor thereof) can receive a configuration message identifying a set of parameter values for a respective set of mobility event types. The set of parameter values may include a time window and a likelihood threshold for a first mobility event type used to predict a mobility event. The UE may then obtain reference signal measurements for a time window, the reference signals from a serving and / or neighboring cell. The UE may determine, using the obtained measurements, that the likelihood threshold is satisfied for the first mobility event type. The UE may then transmit a report indicating the first mobility event type.

Description

PREDICTED EVENT TRIGGERS FOR MOBILITY PROCEDURESCROSS-REFERENCE TO RELATED APPLICATION

[0001] This Patent Cooperation Treaty patent application claims priority to U.S. Provisional Patent Application No. 63 / 749,417, filed January 24, 2025, and titled “Predicted Event Triggers For Mobility Procedures,” the content of which is incorporated herein by reference as if fully disclosed herein in its entirety.TECHNICAL FIELD

[0002] Phis application relates generally to wireless communication systems, including systems, apparatuses, and methods for predicted event triggers for mobility procedures.BACKGROUND

[0003] Wireless mobile communication technology uses various standards and protocols to transmit data between a network device (e.g., a base station, a radio head, etc.) and a wireless communication device. Wireless communication system standards and protocols can include, for example, 3rd Generation Partnership Project (3GPP) long term evolution (LTE) (e.g., 4G), 3GPP new radio (NR) (e.g., 5G), and IEEE 802.11 standard for wireless local area networks (WLAN) (commonly known to industry groups as Wi-Fi®).

[0004] As contemplated by the 3GPP, different wireless communication systems standards and protocols can use various radio access networks (RANs) for communicating between a network device of the RAN (which may also sometimes be referred to generally as a RAN node, a network node, or simply a node) and a wireless communication device known as a user equipment (UE).3GPP RANs can include, for example, global system for mobile communications (GSM), enhanced data rates for GSM evolution (EDGE) RAN (GERAN), Universal Terrestrial Radio Access Network (UTRAN), Evolved Universal Terrestrial Radio Access Network (E-UTRAN), and / or Next-Generation Radio Access Network (NG-RAN).

[0005] Each RAN may use one or more radio access technologies (RATs) to perform communication between the network device and the UE. For example, the GERAN implements GSM and / or EDGE RAT, the UTRAN implements universal mobile telecommunication system (UMTS) RAT or other 3GPP RAT, the E-UTRAN implements LTE RAT (sometimes simply referred to as LTE), and NG-RAN implements NR RAT (sometimes referred to herein as 5G RAT,- 1 - P70385W01 Specification. docx5G NR RAT, or simply NR). In certain deployments, the E-UTRAN may also implement NR RAT. Tn certain deployments, NG-RAN may also implement LTE RAT.

[0006] A network device used by a RAN may correspond to that RAN. One example of an E- UTRAN network device is an E-UTRAN Node B (also commonly denoted as evolved Node B, enhanced Node B, eNodeB, or eNB). One example of an NG-RAN network device is a next generation Node B (also sometimes referred to as a g Node B or gNB).

[0007] A RAN provides its communication services with external entities through its connection to a core network (CN). For example, E-UTRAN may utilize an Evolved Packet Core (EPC), while NG-RAN may utilize a 5G Core Network (5GC).- 2 - P70385W01 Specification. docxBRIEF DESCRIPTION OF THE DRAWINGS

[0008] To easily identify the discussion of any particular element or act, the most significant digit or digits in a reference number refer to the figure number in which that element is first introduced.

[0009] FIG. 1 shows an example wireless communication system, according to one or more aspects described herein.

[0010] FIG. 2 shows an example communication flow, according to one or more aspects described herein.

[0011] FIG. 3 shows an example method of wireless communication at a UE, according to one or more aspects described herein.

[0012] FIG. 4 shows an example method of wireless communication at a network device, according to one or more aspects described herein.

[0013] FIG. 5 illustrates an example architecture of a wireless communication system, according to one or more aspects described herein.

[0014] FIG. 6 illustrates an example system for performing signaling between a wireless device and a network device, according to one or more aspects described herein.- 3 - P70385W01 Specification. docxDETAILED DESCRIPTION

[0015] Various embodiments are described with regard to a processor (e.g., baseband processor), wireless device (e.g., a user equipment (UE)), or a network device. However, reference to a processor, wireless device, or network device is merely provided for illustrative purposes. The example embodiments may be utilized with any electronic component or device that may establish a wireless connection and is configured with the hardware, software, and / or firmware to exchange information and data over the wireless connection. Therefore, the processors, wireless devices, and network devices described herein are used to represent any appropriate electronic components or devices.

[0016] A wireless communication network (e.g., cellular network) may use a report configuration (e.g., measurement report) for mobility management and resource optimization. A network device of the wireless communications network may provide a UE with a configuration for the UE to collect and report network performance metrics to the network. The parameters that the UE may collect and report include reference signal received power (RSRP), reference signal received quality (RSRQ), signal-to-interference-plus-noise ratio (SINR), and neighbor cell performance for handover decisions.

[0017] The measurement reporting that may be configured at the UE by the network device may including periodic reports, event-triggered reports, and / or on-demand reports. For periodic reporting, the UE sends measurement reports at regular intervals, regardless of changes in network conditions. Periodic reporting may be useful for continuous monitoring of the network’s overall performance. For on-demand reporting, the network may request specific measurement reports from the UE when additional insights are needed by the network for decision-making, such as during network troubleshooting or optimization processes. For event-triggered reporting, reports are sent only when certain events (e.g., similar to Al, A2, A3, A5 events) are triggered. Event-triggered reports may help in reacting to specific network conditions, such as signal degradation or improvements, enabling quick decisions like handovers.

[0018] Generally, event triggers are mechanisms that facilitate adaptive and dynamic communication between network elements, including between network devices, and the UEs that are served by the network devices. Generally, event triggers may be used to monitor network conditions, including signal quality, bandwidth, and user mobility. Event triggers may also be used to activate necessary actions, for example handover, resource allocation, or power control. Types of mobility events (which may also be referred to as mobility event triggers) include events for good coverage (an “Al” event), poor coverage (“A2”), neighbor cell better (“A3"), and combined thresholds (“A5”).- 4 - P70385W01 Specification. docx

[0019] The configuration of both events and reporting may be done by a network device using radio resource control (RRC) signaling. The parameters for an event configuration include a time to trigger (TTT), hysteresis, and event threshold. The time to trigger specifies the time duration for which a certain condition is met before an event is triggered. The time to trigger parameter map help avoid unnecessary handover, for examples due to temporary or otherwise short-term fluctuations in signal quality. The hysteresis parameter includes a margin value added to signal strength or quality measurements (e.g., RSRP, RSRQ, and / or SINR) to provide additional stability before triggering an event. Hysteresis may help “ping-pong” effects, where the UE might otherwise switch (in the absence of hysteresis) between cells. The event threshold parameter can be used to predefine (e.g., define or preconfigure) a signal strength or quality threshold (e.g., RSRP, RSRQ, and / or SINR) that is to be satisfied for the mobility event (e.g., the mobility event trigger) to be considered to have occurred. The parameters for a reporting configuration define how and when a UE is to send measurement reports to the network, for example via a network device. Examples of reporting configuration parameters include a reporting frequency, a quantity of measurements, and reporting intervals. The reporting configuration parameters may be important for timely handover and mobility management.

[0020] Current techniques directed to mobility procedures are generally network-centric, meaning that the network (e.g., via a network device) controls when a UE provides measurement reports. The network-centric approach has multiple challenges. For example, measurement variations for a UE can be unique to a particular UE and its environment. While a network may compensate for general measurement trends, individual compensation for a UE may not be possible. Moreover, current approaches may not allow or otherwise provide a mechanism for the network to obtain information from the UE about measurement variations at the UE. Improved techniques that allow a UE to assist or otherwise provide measurement information to the network for improved mobility procedures may be desired.

[0021] As further described herein, a UE may use machine learning (ML) techniques to improve mobility performance for the UE. As used herein, ML techniques may also be referred to as artificial intelligence (Al) techniques or AI / ML techniques. Generally, a UE may use a model to predict event triggers within a defined further time window. Such a prediction model may be referred to herein as a mobility event prediction model. Techniques using event-triggered reporting with mobility events predicted are further discussed herein. A UE may receive a configuration (e.g., be configured by a network) indicating parameter values for a set of mobility event types. One or more of the mobility event types may be used to predict a mobility event using the mobility event prediction model. The parameter values may include a time window and likelihood threshold- 5 - P70385W01 Specification. docxfor the mobility event. The time window may be a defined future time window for the mobility event. The likelihood threshold representing the likelihood of the corresponding mobility event may occur during the defined future time window, as determined by the mobility event prediction model.

[0022] Following configuration, the UE may obtain initial measurements of references from a serving cell of the UE and / or a neighbor cell. Based on the initial measurements and the mobility event prediction model, the UE may obtain a determination that the likelihood threshold for one of the mobility event types is satisfied for a time window. The UE may then transmit a measurement report indicating an occurrence of a mobility event of the first mobility event type.

[0023] The mobility event types used by the techniques described herein may relate to measurement events, including radio link failure (RLF) and / or handover (HO) failure. A network device may configure parameters for one or more mobility event types. In some cases, a measurement event may be predicted. In other cases, RLF may be predicted and an RLF prediction indication transmitted to the network, for example in a measurement report. In some cases, the network may need a predicted measurement in addition to the RLF prediction. In some cases, HO failure may be predicted and an HO failure prediction indication transmitted to the network, for example in a measurement report.

[0024] FIG. 1 shows an example wireless communications system 100, according to one or more aspects described herein. In one or more embodiments, wireless communications system 100 supports one or more aspects of predicted event triggers for mobility procedures, as further described herein.

[0025] Wireless communications system 100 includes a UE 102, network device 104, network device 108, and a machine learning engine 106. One or more UEs including the UE 102 may be served by (e.g., has an established RRC connection with) the network device 104 via communication link 120. Coverage area 110 (e.g., a cell or serving cell with respect to the UE 102) is the service area for the RF spectrum band utilized by network device 104. In one or more embodiments, communication link 120 may include a downlink connection and / or uplink connection. Network device 108 may be a neighbor network device of the network device 104, and have a corresponding coverage area 112 (e.g., a cell or neighbor cell with respect to the UE 102).

[0026] In one or more embodiments, network device 104, network device 108, or both, may utilize beam steering, to receive signals, transmit signals, or both. In one or more embodiments, network device 104 utilizes beam steering for a set of beams 130, or network device 108 utilizes beam steering for a set of beams 132, or both.- 6 - P70385W01 Specification. docx

[0027] The network device 104 and / or the network device 108 may transmit reference signals (e.g., using the set of beams 130 and / or the set of beams 132, respectively) that are receivable by UEs. In the case of UEs (e.g., including UE 102) being served by the network device 104 in the coverage area 110 in a serving cell of the network device 104, the reference signals transmitted by the serving cell as well as neighbor cells may be received and measured by the UE 102 according to a measurement configuration 122 used for link monitoring and mobility purposes, for example radio link monitoring (RLM) and / or handover (HO). Specifically, a UE 102 may monitor for and receive reference signals 128 from a network device 104, including on a serving cell. The measurement configuration 122 may further specify resources identifying measurement occasions for the UE 102 to use to monitor for and measure reference signals 134 received from a neighbor cell, for example the neighbor cell of the network device 108. The UE 102 may receive, from the network, a measurement configuration 122 indicating a set of measurement occasions for the UE 102 to use to measure reference signals transmitted by a serving cell (e.g., from network device 104) or a neighbor cell (e.g., from network device 108).

[0028] In some embodiments, the reference signals include one or more of a channel state information reference signal (CSI-RS) or a synchronization signal block (SSB) (e.g., including a primary synchronization signal (PSS), secondary synchronization signal (SSS), physical broadcast channel (PBCH) carrying control information, and a demodulation reference signal (DMRS) for the PBCH). As an example configuration, the network device 104 and the network device 108 may transmit reference signals (e.g., CSI-RS, SSB, or both) on a set of beams 130 and / or set of beams 132, respectively, during a set of measurement occasions known to the UE 102 via the measurement configuration 122.

[0029] The UE 102 may further include a mobility event prediction model 140, that the UE 102 may use to predict mobility events (e.g., triggers for mobility events). The UE 102 may receive a configuration of model parameters 124 from the network (e.g., via network device 104). The model parameters 124 may include a time window and / or a likelihood threshold, the likelihood threshold associated with a likelihood that a mobility event will occur during that future time window. In some examples, the time window may define a certain time duration (e.g., 50 ms, 100 ms, 200 ms, 500 ms, or 1000 ms). The time windows may be sequential in some examples, or may be a sliding time window in other examples. In some examples, the likelihood threshold of the predicted mobility event may be expressed as a percentage (e.g., 10%, 25%, 50%, 75%, or 90%). One or more of the values of the model parameters 124, including the time window and / or likelihood threshold, may be configured at a time. In some cases, for example in the absence of the receipt of the configuration of the model parameters 124, default values may be used by the UE 102. For- 7 - P70385W01 Specification. docxexample, a likelihood threshold may be set at 90% as the default value in the absence of a different likelihood threshold set by configuration. The mobility event may be considered (e.g., determined, identified, and so on) when the likelihood of the predicted event in the configured prediction time window is at least (e.g., higher than) the configured likelihood threshold. The configuration of model parameters 124 may be an alternative to, or in addition to, threshold, hysteresis, and time-to-trigger.

[0030] In some examples, these mobility events may include a set of events related to RLF and / or HO failure. In some examples, the predicted mobility events may be similar to (but different than) actual mobility events that are defined according to existing techniques (e.g., an A2 and / or A3 event).

[0031] In a first example, the first mobility event type is a signal quality (an RSRP, RSRQ, and / or SINR) of the serving cell (e.g., of the network device 104) meeting or exceeding a threshold quality with a predicted likelihood that satisfies a likelihood threshold. That is, the likelihood (e.g., as a percentage) may represent how likely it is, according to the mobility event prediction model, that the signal quality for a serving cell is better than or becomes better than some threshold signal quality value during a future time window. In some examples, the event description corresponding to the mobility event (e.g., event “Rl”) may be similar to: “Likelihood of serving cell becoming better than threshold-x is higher than threshold-y.”

[0032] In another example, a second mobility event type is a signal quality (an RSRP, RSRQ, and / or SINR) of the serving cell (e.g., of the network device 104) below a threshold quality with a predicted likelihood that satisfies a likelihood threshold. That is, the likelihood (e.g., as a percentage) may represent how likely it is. according to the mobility event prediction model, that the signal quality for a serving cell is below some threshold signal quality value during a future time window. In some examples, the event description corresponding to the mobility event (e.g., event “R2”) may be similar to: “Likelihood of serving cell becoming worse than threshold-x is higher than thrcshold-y.'’ In some examples, the second mobility event type may additionally include an RLF prediction, for example, where the serving cell becomes worse than a threshold value.

[0033] In yet another example, a third mobility event type is a signal quality (an RSRP, RSRQ, and / or SINR) of a neighbor cell (e.g., of the network device 108) that meets or exceeds a threshold quality with a likelihood that satisfies the likelihood threshold. That is, the likelihood (e.g., as a percentage) may represent how likely it is, according to the mobility event prediction model, that the signal quality for the neighbor cell is at least as much as (e.g., meets or exceeds) some threshold signal quality value during a future time window. In some examples, the event description - 8 - P70385W01 Specification. docxcorresponding to the mobility event (e.g., event “R3”) may be similar to: “Likelihood of neighbor cell becoming offset-x better than secondary primary cell (SpCell) is higher than threshold-y.” Tn some examples, the third mobility event type may additionally include an HO failure prediction.

[0034] In another example, a fourth mobility event type is a signal quality (an RSRP, RSRQ, and / or SINR) of a neighbor cell (e.g., of the network device 108) below a threshold quality with a likelihood that satisfies the likelihood threshold. That is, the likelihood (e.g., as a percentage) may represent how likely it is, according to the mobility event prediction model, that the signal quality for the neighbor cell is below some threshold signal quality value during a future time window. Tn some examples, the event description corresponding to the mobility event (e.g., event “R4”) may be similar to: “Likelihood of neighbor cell becoming better than threshold-x is higher than threshold-y.” In some examples, the fourth mobility event type may additionally include an HO failure prediction.

[0035] In another example, a fifth mobility event type is a signal quality (an RSRP, RSRQ, and / or SINR) of an SpCell (e.g., of the network device 104) below a first threshold quality and a signal quality of a neighbor cell meets or exceeds a second threshold quality with a likelihood that satisfies the likelihood threshold. That is, the likelihood (e.g., as a percentage) may represent how likely it is, according to the mobility event prediction model, that the signal quality for the SpCell is below some first threshold signal quality value during a future time window, and the neighbor cell exceeds a second threshold signal quality value. In some examples, the event description corresponding to the mobility event (e.g., event “R5”) may be: “Likelihood of SpCell becoming worse than threshold-xi and neighbor becoming better than threshold- X2 is higher than threshold-y.”

[0036] In another example, a sixth mobility event type is an RLF first signal quality (an RSRP, RSRQ, and / or SINR) of a neighbor cell (e.g., of the network device 108) below a threshold quality with a likelihood that satisfies the likelihood threshold. That is, the likelihood (e.g., as a percentage) may represent how likely it is, according to the mobility event prediction model, that the signal quality for the neighbor cell is below some threshold signal quality value during a future time window. In some examples, the event description corresponding to the mobility event (e.g., event “R4”) may be similar to: “Likelihood of neighbor cell becoming better than threshold-x is higher than threshold-y.” In some examples, the sixth mobility event type may additionally include an HO failure prediction.

[0037] The configuration of model parameters 124 may be transmitted to the UE 102 from the network device 104 via radio resource control (RRC) signaling. For example, an information element for a predicted event trigger configuration (e.g., PredictedEventTriggerConfig') may be - 9 - P70385W01 Specification. docxconfigured by the network and transmitted to the UE 102 by the network device 104. In some examples, the predicted event trigger configuration may be included in a reporting configuration information element (e.g., in ReportConfigNR for NR). In some cases, different radio access technologies (RATs) (e.g., LTE) may use similar configuration signaling, with parallel configuration of event types in a reporting configuration information element (e.g., in ReportConfiglnterRAT), but applicable to that of another RAT.

[0038] In some examples, the configuration of model parameters 124 may be (or be a part of) an information element that includes a quantity of separate sub-configuration values for each mobility event type. The first mobility event type may have a sub-configuration of a first time window value (e.g., prediction time window), a first likelihood threshold value (e.g., prediction likelihood threshold), and an indication of whether the event is reported on leaving the serving cell. The second mobility event type may have a sub-configuration of a second time window value (e.g., prediction time window), a second likelihood threshold value (e.g., prediction likelihood threshold), an indication of whether the event is reported on leaving the serving cell, and an indication of whether a predicted RLF is indicated by the event. The third mobility event type may have a sub-configuration of a third time window value (e.g., prediction time window), a third likelihood threshold value (e.g., prediction likelihood threshold), an indication of whether the event is reported on leaving the serving cell, and an indication of whether a predicted HO is indicated by the event. The fourth mobility event type may have a sub-configuration of a fourth time window value (e.g., prediction time window), a fourth likelihood threshold value (e.g., prediction likelihood threshold), and an indication of whether the event is reported on leaving the serving cell. The fifth mobility event type may have a sub-configuration of a fifth time window value (e.g., prediction time window), a fifth likelihood threshold value (e.g., prediction likelihood threshold), and an indication of whether the event is reported on leaving the serving cell. The sixth mobility event type may have a sub-configuration of a sixth time window value (e.g., prediction time window), a sixth likelihood threshold value (e.g., prediction likelihood threshold), and an indication of whether the event is reported on leaving the serving cell.

[0039] In other examples, the configuration of model parameters 124 may be (or be a part of) an information element for an event trigger configuration (e.g., EventTriggerConfig) in RRC signaling from the network to the UE 102 via the network device 104. For example, each mobility event type may be configured via the event trigger configuration, where the mobility event type is associated with an event identifier (e.g., eventID). Each mobility event type (e.g., the first, second, third, fourth, fifth, and / or sixth) may be associated with a corresponding event identifier. Each event identifier may be associated with a corresponding time window value (e.g., prediction time- 10 - P70385W01 Specification. docxwindow), a likelihood threshold value (e.g., prediction likelihood threshold), and, in some examples, an indication of whether prediction is allowed (e.g., predictionAllowed) for the event associated with the event identifier. In other examples, the indication of whether prediction is allowed may be omitted or otherwise not present, and the inclusion of the time window value and / or the likelihood threshold value may be an implicit indication that prediction is allowed for the corresponding event identifier (e.g., using the mobility event prediction model 140).

[0040] The UE 102 may receive the measurement configuration 122 for the UE 102 to use to measure reference signals to use, among other purposes, to make mobility event predictions according to the mobility event prediction model. In some examples, the measurements may be made using existing measurement frameworks, such as by measuring measurement objects configured for non-prediction purposes. These measurement objects may include reference signals during measurement occasions and on frequency resources specified by a configuration for radio resource management (RRM), radio link monitoring (RLM), beam failure detection and recovery (BFR), and / or handover failure (HOF). One or more of these measurement objects and / or configurations may be used for the mobility event predictions, in addition to the use of the measurement objects and / or configurations for the existing measurement framework.

[0041] In addition, different configurations may use the same or overlapping measurement objects, including the measurement objects for mobility event predictions and measurement objects for non-prediction purposes. For example, the network may configure measurement occasions for legacy events for some frequencies and frequency resources, and measurement occasions for predicted events for different frequencies and frequency resources. In other examples, the network may configure predicted events (e.g., mobility event predictions), and then add on non-prediction (e.g., legacy) events when the prediction level reaches a threshold level. For example, the UE 102 may perform measurements using resources configured for mobility event predictions, without performing measurements using resources configured for non-predictions, to the extent that the resources do not overlap. Once a prediction threshold is satisfied, then additional measurement types (e.g., non-prediction purposes) may be performed.

[0042] Additionally, conditional events may be configured in some examples. For example, a mobility event, as further described herein, may be triggered by satisfaction of the likelihood threshold during a time window for that mobility event. Upon satisfaction of that likelihood threshold, further measurements of reference signals may be made and / or further evaluation of events made (e.g., non-prediction-based events, legacy events).

[0043] Following event detection, an indication of the predicted mobility event may be transmitted to the network device 104 via a report 126, which may be a measurement report. In - 11 - P70385W01 Specification. docxsome examples, the report may be a layer 1 (LI) or layer 3 (L3) report. In some examples, the event report may be a portion of an REM, RRM, BFR, or HOF report.

[0044] The mobility event prediction model 140 at the UE 102 may come from one or more of a number of different sources. For example, a machine learning engine 106 may implement or otherwise perform one or more machine learning tasks, such as training a mobility event prediction model 140 for UE 102 based on a set of measurements taken by UE 102 of reference signals received from network device 104 on one or more beams of the set of beams 130 and / or reference signals received from network device 108 on one or more beams of the set of beams 132. Following training, machine learning engine 106 may then provide the mobility event prediction model 140 to UE 102 via communication link 136, which may be a wired or wireless connection.

[0045] Machine learning engine 106 may be or include one or more computing components, such as a processor and memory. In some examples, the machine learning engine may also be referred to as an artificial intelligence (Al) engine. In one or more embodiments, the machine learning engine 106 is a device external to UE 102, but in communication with UE 102 (e.g., directly, or via a network device such as network device 104, such as a server). In other embodiments, the machine learning engine 106 is a server (e.g., a software-based server) for a machine learning engine that is internal to UE 102 or otherwise collocated with UE 102, for example within a same mobile device, vehicle, and so on.

[0046] The machine learning engine 106 may include and / or generate a machine learning model (e.g., a mobility event prediction model 140) to find patterns or make decisions from a previously unseen dataset. In some examples, a machine learning model may refer to a program (algorithm, code, process). Additionally, or alternatively, a machine learning model may refer to parameters, values, data, or other inputs provided to a machine learning engine 106 (e.g., a program) that define or otherwise control the operation of the machine learning engine. The mobility event prediction model 140 may be trained using a dataset, where the program is optimized to find certain patterns or outputs from the dataset. The output of the training is the mobility event prediction model 140.

[0047] In some examples, the machine learning engine 106 may be a component or other portion of a baseband processor, for example within a UE 102. In other examples, the machine learning engine may be a component or other portion of an application processor of the UE 102. In some examples, the mobility event prediction model 140 may use crowd-sourcing techniques. For example, a quantity of different UEs, including the UE 102, may provide measurements to a machine learning engine 106 at a centralized location. The mobility event prediction model 140 may then be generated by the machine learning engine 106 and provided for use by the UE 102.- 12 - P70385W01 Specification. docx

[0048] FIG. 2 shows an example communication flow 200, according to one or more aspects described herein. In one or more embodiments, communication flow 200 supports one or more aspects of predicted event triggers for mobility procedures, as further described herein. In some examples, the communication flow 200 may be by and between a UE 102, a network device 104, and a network device 108.

[0049] The UE 102 may receive a configuration message 210 from the network device 104, which may serve the UE 102 (e.g., by providing a serving cell to the UE 102). In some examples, the configuration message 210 may include a set of parameter values (e.g., mobility event parameters) for a set of mobility event types. These parameter values may include at least a time window and a likelihood threshold for a mobility event type. The mobility event type may be one of a set of mobility event types, for example any of the first through sixth mobility event types described herein with reference to predicted mobility events. In some examples, the time window and / or likelihood threshold may include one or more additional parameter values. In some examples, in addition to the parameter values for the predicted mobility events, the configuration message 210 may include one or more parameter values for one or more non-predicted events (e.g., non-prediction mobility events).

[0050] In some examples, the configuration message 210 may be received by the UE 102 during establishment of an RRC connection between the UE 102 and the network device 104. Following RRC connection establishment to establish a wireless communication link between the UE 102 and the network device 104 on a serving cell, the UE 102 and the network device 104 may exchange communications 212. The UE 102 may monitor (e.g., listen) for and receive reference signals 214 from network device 104 (e.g., a serving cell, serving base station), or both. The reference signals 214, the reference signals 216, or both, may be CSI-RSs, SSBs, or both.

[0051] The UE 102 may perform reference signal measurements 218. In some examples, a baseband processor of the UE 102 may obtain measurements (e.g., reference signal measurements 218) of reference signals for the time window, the reference signals measured according to a measurement configuration for the reference signals from one or both of a serving cell or a neighbor cell. The UE 102 may then determine, using the mobility event prediction model, that the likelihood threshold for the mobility event type is satisfied for the time window. This determination is based at least in part on the obtained measurements (e.g., reference signal measurements 218).

[0052] In response to determining that the likelihood threshold for the mobility event type is satisfied, the UE 102 may transmit a report 222 indicating the mobility event for the mobility event type. For example, the indicated mobility event may be a predicted mobility event for a first type - 13 - P70385W01 Specification. docxthat indicates that a likelihood of the serving cell (e.g., of network device 104) becoming worse than a first threshold value (e.g., threshold-x) is higher than a second threshold value (e.g., threshold-y).

[0053] FIG. 3 shows an example method 300 of wireless communication by a UE, according to one or more aspects described herein. In some cases, the UE may be the wireless device 602 or UE 102. In some cases, the method 300 may be performed by a baseband processor of the UE. In some embodiments, the baseband processor may include one or more processor cores, and memory that is coupled to the processor core(s). The memory may store instructions that, when executed by the processor core(s), cause the baseband processor to perform the operations of the method 300. As the baseband processor performs the operations of the method 300, the baseband processor may also cause other components of the UE to perform, or discontinue, various operations.

[0054] At 302, the method 300 includes receiving a set of predicted mobility event parameters. In some embodiments, the method 300 includes receiving a configuration message identifying a set of parameter values for a respective set of mobility event types, the set of parameter values including a time window and a likelihood threshold for a first mobility event type of the set of mobility event types, the first mobility event type to be used to predict a mobility event.

[0055] At 304, the method 300 includes obtaining reference signal measurements for serving and neighboring cells. In some embodiments, the method 300 includes obtaining measurements of reference signals for the time window, the reference signals measured according to a measurement configuration for the reference signals from one or both of a serving cell or a neighbor cell.

[0056] At 306, the method 300 includes determining a likelihood that a mobility event will occur. In some embodiments, the method 300 includes determining, based at least in part on the obtained measurements, that the likelihood threshold for the first mobility event type is satisfied for the time window.

[0057] At 308, the method 300 includes transmitting an indication of the predicted mobility event. In some embodiments, the method 300 includes transmitting, responsive to the determination that the likelihood threshold is satisfied, a measurement report indicating the first mobility event type.

[0058] In one or more embodiments, the method further includes receiving, responsive to the transmitted measurement report, a control message indicating to perform a mobility procedure; and performing the mobility procedure responsive to the control message, the mobility procedure including reconnecting with the serving cell or re-establishing an RRC connection with the neighbor cell.- 14 - P70385W01 Specification. docx

[0059] In one or more embodiments, the method further includes determining, for a second mobility event type of the set of mobility event types, whether a second likelihood threshold is satisfied for a second time window, where the set of parameter values further includes the second time window and the second likelihood threshold for the second mobility event type of the set of mobility event types.

[0060] In some embodiments, the set of mobility event types are a first set of mobility event types configured to predict the mobility event using the mobility event prediction model for a first radio frequency spectrum band; and the configuration message further identifies a second set of mobility event types for the first radio frequency spectrum band or a second radio frequency spectrum band, the second set of mobility event types configured to use a deterministic comparison to identify that the mobility event has occurred.

[0061] In some embodiments, the first mobility event type is a signal quality of the serving cell that meets or exceeds a threshold quality with a likelihood that satisfies the likelihood threshold. In some embodiments, the first mobility event type is a signal quality of the serving cell that is below a threshold quality with a likelihood that satisfies the likelihood threshold. In some embodiments, the first mobility event type is a signal quality of the neighbor cell that meets or exceeds a threshold quality with a likelihood that satisfies the likelihood threshold. In some embodiments, the first mobility event type is a signal quality of the neighbor cell that is below a threshold quality with a likelihood that satisfies the likelihood threshold. In some embodiments, the first mobility event type is a first signal quality of a secondary primary cell that is below a first threshold quality, and the neighbor cell that meets or exceeds a threshold quality with a likelihood that satisfies the likelihood threshold. In some embodiments, the first mobility event type is a likelihood of a radio link failure that is greater than or equal to a threshold likelihood.

[0062] In one or more embodiments, the method further includes receiving the configuration indicating a set of measurement occasions for the UE to use to measure the reference signals transmitted by the serving cell or the neighbor cell of the UE; receiving the reference signals using the set of measurement occasions of the configuration; and performing, for the time window, one or more measurements according to the configuration.

[0063] The method 300 may be variously embodied, extended, or adapted, as described in the following paragraphs and elsewhere in this description.

[0064] FIG. 4 shows an example method 400 of wireless communication by a network device, according to one or more aspects described herein. In one or more embodiments, method 400 supports one or more aspects of predicted event triggers for mobility procedures, as further described herein. In some cases, the network device may be the network device 104, network - 15 - P70385W01 Specification. docxdevice 620, or one of the other network devices described herein. The method 400 may be performed using a processor, a transceiver, or other components of the network device.

[0065] At 402, the method 400 includes transmitting a set of predicted mobility event parameters. In some embodiments, the method 400 includes transmitting a configuration message identifying a set of parameter values for a respective set of mobility event types, the set of parameter values including a time window and a likelihood threshold for a first mobility event type of the set of mobility event types, the first mobility event type to be used to predict a mobility event.

[0066] At 404, the method 400 includes transmitting a measurement configuration for a serving cell and / or neighbor cell. In some embodiments, the method 400 includes transmitting a measurement configuration indicating a set of measurement occasions for a UE to use to measure reference signals transmitted by a serving cell or a neighbor cell of the UE.

[0067] At 406, the method 400 includes receiving an indication that a first mobility event type has occurred according to a likelihood threshold. In some embodiments, the method 400 includes receiving, in response to a determination that the likelihood threshold is satisfied, a measurement report indicating that the likelihood threshold is satisfied for the time window and the first mobility event type has occurred.

[0068] In one or more embodiments, the method further includes transmitting, via the transceiver and responsive to the received measurement report, a control message indicating for the UE to perform a mobility procedure. In some embodiments, the set of parameter values further include a second time window and a second likelihood threshold for a second mobility event type of the set of mobility event types.

[0069] In some embodiments, the set of mobility event types are a first set of mobility event types configured to predict the mobility event using the mobility event prediction model for a first radio frequency spectrum band; and the configuration message further identifies a second set of mobility event types for the first radio frequency spectrum band or a second radio frequency spectrum band, the second set of mobility event types configured to use a deterministic comparison to identify that the mobility event has occurred.

[0070] In some embodiments, the first mobility event type is based at least in part on a signal quality of the serving cell or the neighbor cell satisfying or failing to satisfy a threshold quality with a likelihood that satisfies the likelihood threshold.

[0071] The method 400 may be variously embodied, extended, or adapted, as described in the following paragraphs and elsewhere in this description.- 16 - P70385W01 Specification. docx

[0072] Embodiments contemplated herein include one or more non-transitory computer-readable media storing instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of the methods 300 or 400. In the context of method 300, this non-transitory computer-readable media may be, for example, a memory of a UE (such as a memory 606 of a wireless device 602 that is a UE, as described herein). In the context of method 400, this non-transitory computer-readable media may be, for example, a memory of a network device (such as a memory 624 of a network device 620, as described herein).

[0073] Embodiments contemplated herein include an apparatus having logic, modules, or circuitry to perform one or more elements of the methods 300 or 400. In the context of method 300, this apparatus may be, for example, an apparatus of a UE (such as a wireless device 602 that is a UE). In the context of method 400, this apparatus may be, for example, an apparatus of a network device (such as a network device 620, as described herein).

[0074] Embodiments contemplated herein include an apparatus having one or more processors and one or more computer-readable media, using or storing instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of the methods 300 or 400. In the context of method 300, this apparatus may be, for example, an apparatus of a UE (such as a wireless device 602 that is a UE, as described herein). In the context of the method 400, this apparatus may be, for example, an apparatus of a network device (such as a network device 620, as described herein).

[0075] Embodiments contemplated herein include a signal as described in or related to one or more elements of the methods 300, or 400.

[0076] Embodiments contemplated herein include a computer program or computer program product having instructions, wherein execution of the program by a processor causes the processor to carry out one or more elements of the methods 300 or 400. In the context of method 300, the processor may be a processor of a UE (such as a processor(s) 604 of a wireless device 602 that is a UE, as described herein), and the instructions may be, for example, located in the processor and / or on a memory of the UE (such as a memory 606 of a wireless device 602 that is a UE, as described herein). In the context of method 400, the processor may be a processor of a network device (such as a processor(s) 622 of a network device 620, as described herein), and the instructions may be, for example, located in the processor and / or on a memory of the network device (such as a memory 624 of a network device 620, as described herein).

[0077] FIG. 5 illustrates an example architecture of a wireless communication system, according to embodiments described herein. The following description is provided for an example - 17 - P70385W01 Specification. docxwireless communication system 500 that operates in conjunction with the LTE system standards or specifications and / or 5G or NR system standards or specifications, as provided by 3GPP technical specifications.

[0078] As shown, the wireless communication system 500 includes UE 502 and UE 504 (although any number of UEs may be used). In this example, the UE 502 and the UE 504 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks) but may also comprise any mobile or non-mobile computing device configured for wireless communication.

[0079] The UE 502 and UE 504 may be configured to communicatively couple with a RAN 506. In some embodiments, the RAN 506 may be NG-RAN, E-UTRAN, etc. The UE 502 and UE 504 utilize connections (or channels) (shown as connection 508 and connection 510, respectively) with the RAN 506, each of which comprises a physical communications interface. The RAN 506 can include one or more network devices, such as base station 512 and base station 514, that enable the connection 508 and connection 510.

[0080] In this example, the connection 508 and connection 510 are air interfaces to enable such communicative coupling and may be consistent with RAT(s) used by the RAN 506, such as, for example, an LTE and / or NR.

[0081] In some embodiments, the UE 502 and UE 504 may also directly exchange communication data via a sidelink interface 516. The UE 504 is shown to be configured to access an access point (shown as AP 518) via connection 520. By way of example, the connection 520 can comprise a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein the AP 518 may comprise a Wi-Fi® router. In this example, the AP 518 may be connected to another network (for example, the Internet) without going through a CN 524.

[0082] In some embodiments, the UE 502 and UE 504 can be configured to communicate using orthogonal frequency division multiplexing (OFDM) communication signals with each other or with the base station 512 and / or the base station 514 over a multicarrier communication channel in accordance with various communication techniques, such as, but not limited to, an orthogonal frequency division multiple access (OFDMA) communication technique (e.g., for downlink communications) or a single carrier frequency division multiple access (SC-FDMA) communication technique (e.g., for uplink and ProSe or sidelink communications), although the scope of the embodiments is not limited in this respect. The OFDM signals can comprise a plurality of orthogonal subcarriers.- 18 - P70385W01 Specification. docx

[0083] In some embodiments, all or parts of the base station 512 or base station 514 may be implemented as one or more software entities running on server computers as part of a virtual network. In addition, or in other embodiments, the base station 512 or base station 514 may be configured to communicate with one another via interface 522. In embodiments where the wireless communication system 500 is an LTE system (e.g., when the CN 524 is an EPC), the interface 522 may be an X2 interface. The X2 interface may be defined between two or more network devices of a RAN (e.g., two or more eNBs and the like) that connect to an EPC, and / or between two eNBs connecting to the EPC. In embodiments where the wireless communication system 500 is an NR system (e.g., when CN 524 is a 5GC), the interface 522 may be an Xn interface. The Xn interface is defined between two or more network devices of a RAN (e.g., two or more gNBs and the like) that connect to the 5GC, between a base station 512 (e.g., a gNB) connecting to the 5GC and an eNB, and / or between two eNBs connecting to the 5GC (e.g., CN 524).

[0084] The RAN 506 is shown to be communicatively coupled to the CN 524. The CN 524 may comprise one or more network elements 526, which are configured to offer various data and telecommunications services to customers / subscribers (e.g., users of UE 502 and UE 504) who are connected to the CN 524 via the RAN 506. The components of the CN 524 may be implemented in one physical device or separate physical devices including components to read and execute instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium).

[0085] In some embodiments, the CN 524 may be an EPC, and the RAN 506 may be connected with the CN 524 via an SI interface 528. In some embodiments, the SI interface 528 may be split into two parts, an SI user plane (Sl-U) interface, which carries traffic data between the base station 512 or base station 514 and a serving gateway (S-GW), and the Sl-MME interface, which is a signaling interface between the base station 512 or base station 514 and mobility management entities (MMEs).

[0086] In some embodiments, the CN 524 may be a 5GC, and the RAN 506 may be connected with the CN 524 via an NG interface 528. In other embodiments, the NG interface 528 may be split into two parts, an NG user plane (NG-U) interface, which carries traffic data between the base station 512 or base station 514 and a user plane function (UPF), and the SI control plane (NG-C) interface, which is a signaling interface between the base station 512 or base station 514 and access and mobility management functions (AMFs).

[0087] Generally, an application server 530 may be an clement offering applications that use internet protocol (IP) bearer resources with the CN 524 (e.g., packet switched data services). The application server 530 can also be configured to support one or more communication services (e.g.,- 19 - P70385W01 Specification. docxVoIP sessions, group communication sessions, etc.) for the UE 502 and UE 504 via the CN 524. The application server 530 may communicate with the CN 524 through an TP communications interface 532.

[0088] FIG. 6 illustrates an example system 600 for performing signaling 638 between a wireless device 602 and a network device 620, according to embodiments described herein. The system 600 may be a portion of a wireless communication system as herein described. The wireless device 602 may be, for example, a UE of a wireless communication system. The network device 620 may be, for example, a base station (e.g., an eNB or a gNB) or a radio head of a wireless communication system.

[0089] The wireless device 602 may include one or more processor(s) 604. The processor(s) 604 may execute instructions such that various operations of the wireless device 602 are performed, as described herein. The processor(s) 604 may include one or more baseband processors implemented using, for example, a central processing unit (CPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a controller, a field programmable gate array (FPGA) device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein.

[0090] The wireless device 602 may include a memory 606. The memory 606 may be a non-transitory computer-readable storage medium that stores instructions 608 (which may include, for example, the instructions being executed by the processor(s) 604). The instructions 608 may also be referred to as program code or a computer program. The memory 606 may also store data used by, and results computed by, the processor(s) 604.

[0091] The wireless device 602 may include one or more transceiver(s) 610 (also collectively referred to as a transceiver 610) that may include radio frequency (RF) transmitter and / or receiver circuitry that use the antenna(s) 612 of the wireless device 602 to facilitate signaling (e.g., the signaling 638) to and / or from the wireless device 602 with other devices (e.g., the network device 620) according to corresponding RATs.

[0092] The wireless device 602 may include one or more antenna(s) 612 (e.g., one, two, four, eight, or more). For embodiments with multiple antenna(s) 612, the wireless device 602 may leverage the spatial diversity of such multiple antenna(s) 612 to send and / or receive multiple different data streams on the same time and frequency resources. This behavior may be referred to as, for example, multiple input multiple output (MIMO) behavior (referring to the multiple antennas used at each of a transmitting device and a receiving device that enable this aspect). MIMO transmissions by the wireless device 602 may be accomplished according to precoding (or digital beamforming) that is applied at the wireless device 602 that multiplexes the data streams - 20 - P70385W01 Specification. docxacross the antenna(s) 612 according to known or assumed channel characteristics such that each data stream is received with an appropriate signal strength relative to other streams and at a desired location in the spatial domain (e.g., the location of a receiver associated with that data stream). Some embodiments may use single user MIMO (SU-MIMO) methods (where the data streams are all directed to a single receiver) and / or multi-user MIMO (MU-MIMO) methods (where individual data streams may be directed to individual (different) receivers in different locations in the spatial domain).

[0093] In some embodiments having multiple antennas, the wireless device 602 may implement analog beamforming techniques, whereby phases of the signals sent by the antenna(s) 612 are relatively adjusted such that the (joint) transmission of the antenna(s) 612 can be directed (this is sometimes referred to as beam steering).

[0094] The wireless device 602 may include one or more interface(s) 614. The interface(s) 614 may be used to provide input to or output from the wireless device 602. For example, a wireless device 602 that is a UE may include interface(s) 614 such as microphones, speakers, a touchscreen, buttons, and the like in order to allow for input and / or output to the UE by a user of the UE. Other interfaces of such a UE may be made up of transmitters, receivers, and other circuitry (e.g., other than the transceiver(s) 610 / antenna(s) 612 already described) that allow for communication between the UE and other devices and may operate according to known protocols (e.g., Wi-Fi®, Bluetooth®, and the like).

[0095] The wireless device 602 may include mobility prediction manager 616. The mobility prediction manager 616 may be implemented via hardware, software, or combinations thereof. For example, the mobility prediction manager 616 may be implemented as a processor, circuit, and / or instructions 608 stored in the memory 606 and executed by the processor(s) 604. In some examples, the mobility prediction manager 616 may be integrated within the processor(s) 604 and / or the transceiver(s) 610. For example, the mobility prediction manager 616 may be implemented by a combination of software components (e.g., executed by a DSP or a general processor) and hardware components (e.g., logic gates and circuitry) within the processor(s) 604 or the transceiver(s) 610.

[0096] The mobility prediction manager 616 may be used for various aspects of the present disclosure, for example, aspects of FIGs. 1-6, from a wireless device or UE perspective. The mobility prediction manager 616 may be configured, for example, to receive a configuration message identifying a set of parameter values for a respective set of mobility event types, the set of parameter values including a time window and a likelihood threshold for a first mobility event type of the set of mobility event types, the first mobility event type to be used to predict a mobility - 21 - P70385W01 Specification. docxevent; obtain measurements of reference signals for the time window, the reference signals measured according to a measurement configuration for the reference signals from one or both of a serving cell or a neighbor cell; determine, based at least in part on the obtained measurements, that the likelihood threshold for the first mobility event type is satisfied for the time window; and transmit, responsive to the determination that the likelihood threshold is satisfied, a measurement report indicating the first mobility event type.

[0097] The network device 620 may include one or more processor(s) 622. The processor(s) 622 may execute instructions such that various operations of the network device 620 are performed, as described herein. The processor(s) 622 may include one or more baseband processors implemented using, for example, a CPU, a DSP, an ASIC, a controller, an FPGA device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein.

[0098] The network device 620 may include a memory 624. The memory 624 may be a non-transitory computer-readable storage medium that stores instructions 626 (which may include, for example, the instructions being executed by the processor(s) 622). The instructions 626 may also be referred to as program code or a computer program. The memory 624 may also store data used by, and results computed by, the processor(s) 622.

[0099] The network device 620 may include one or more transceiver(s) 628 (also collectively referred to as a transceiver 628) that may include RF transmitter and / or receiver circuitry that use the antenna(s) 630 of the network device 620 to facilitate signaling (e.g., the signaling 638) to and / or from the network device 620 with other devices (e.g., the wireless device 602) according to corresponding RATs.

[0100] The network device 620 may include one or more antenna(s) 630 (e.g., one, two, four, or more). In embodiments having multiple antenna(s) 630, the network device 620 may perform MIMO, digital beamforming, analog beamforming, beam steering, etc., as has been described.

[0101] The network device 620 may include one or more interface(s) 632. The interface(s) 632 may be used to provide input to or output from the network device 620. For example, a network device 620 of a RAN (e.g., a base station, a radio head, etc.) may include interface(s) 632 made up of transmitters, receivers, and other circuitry (e.g., other than the transceiver(s) 628 / antenna(s) 630 already described) that enables the network device 620 to communicate with other equipment in a network, and / or that enables the network device 620 to communicate with external networks, computers, databases, and the like for purposes of operations, administration, and maintenance of the network device 620 or other equipment operably connected thereto.- 22 - P70385W01 Specification. docx

[0102] The network device 620 may include at least one mobility prediction manager 634. The mobility prediction manager 634 may be implemented via hardware, software, or combinations thereof. For example, the mobility prediction manager 634 may be implemented as a processor, circuit, and / or instructions 626 stored in the memory 624 and executed by the processor(s) 622. In some examples, the mobility prediction manager 634 may be integrated within the processor(s) 622 and / or the transceiver(s) 628. For example, the mobility prediction manager 634 may be implemented by a combination of software components (e.g., executed by a DSP or a general processor) and hardware components (e.g., logic gates and circuitry) within the processor(s) 622 or the transceiver(s) 628.

[0103] The mobility prediction manager 634 may be used for various aspects of the present disclosure, for example, aspects of FIGs. 1-6, from a network device perspective. The mobility prediction manager 634 may be configured, for example, to transmit a configuration message identifying a set of parameter values for a respective set of mobility event types, the set of parameter values including a time window and a likelihood threshold for a first mobility event type of the set of mobility event types, the first mobility event type to be used to predict a mobility event; transmit a measurement configuration indicating a set of measurement occasions for a UE to use to measure reference signals transmitted by a serving cell or a neighbor cell of the UE; and receive, in response to a determination that the likelihood threshold is satisfied, a measurement report indicating that the likelihood threshold is satisfied for the time window and the first mobility event type has occurred.

[0104] For one or more embodiments, at least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and / or methods as set forth herein. For example, a baseband processor (or processor) as described herein in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth herein. For another example, circuitry associated with a UE, network device, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth herein.

[0105] Any of the above described embodiments may be combined with any other embodiment (or combination of embodiments), unless explicitly stated otherwise. The foregoing description of one or more implementations provides illustration and description but is not intended to be exhaustive or to limit the scope of embodiments to the precise form described. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.- 23 - P70385W01 Specification. docx

[0106] Embodiments and implementations of the systems and methods described herein may include various operations, which may be embodied in machine-executable instractions to be executed by a computer system. A computer system may include one or more general-purpose or special-purpose computers (or other electronic devices). The computer system may include hardware components that include specific logic for performing the operations or may include a combination of hardware, software, and / or firmware.

[0107] The systems described herein pertain to specific embodiments but are provided as examples. These embodiments can be combined into single systems, partially combined into other systems, split into multiple systems or divided or combined in other ways. In addition, it is contemplated that parameters, attributes, aspects, etc., of one embodiment can be used in another embodiment. The parameters, attributes, aspects, etc., are merely described in one or more embodiments for clarity, and it is recognized that the parameters, attributes, aspects, etc., can be combined with or substituted for parameters, attributes, aspects, etc., of another embodiment unless specifically disclaimed herein.

[0108] Although the foregoing has been described in some detail for purposes of clarity, it will be apparent that changes and modifications may be made without departing from the principles thereof. It should be noted that there are many alternative ways of implementing both the processes and apparatuses described herein. Accordingly, the present embodiments are to be considered illustrative and not restrictive, and the description is not to be limited to the details given herein but may be modified within the scope and equivalents of the appended claims.- 24 - P70385W01 Specification. docx

Claims

1. CLAIMS1. A baseband processor comprising a memory and configured to:receive a configuration message identifying a set of parameter values for a respective set of mobility event types, the set of parameter values including a time window and a likelihood threshold for a first mobility event type of the set of mobility event types, the first mobility event type to be used to predict a mobility event;obtain measurements of reference signals for the time window, the reference signals measured according to a measurement configuration for the reference signals from one or both of a serving cell or a neighbor cell;determine, based at least in part on the obtained measurements, that the likelihood threshold for the first mobility event type is satisfied for the time window; andtransmit, responsive to the determination that the likelihood threshold is satisfied, a report indicating the mobility event of the first mobility event type.

2. The baseband processor of claim 1 , further configured to:receive, responsive to the transmitted report, a control message indicating to perform a mobility procedure; andperform the mobility procedure responsive to the control message, the mobility procedure comprising reconnecting with the serving cell or re-establishing a radio resource control (RRC) connection with the neighbor cell.

3. The baseband processor of claim 1 , further configured to:determine, for a second mobility event type of the set of mobility event types, whether a second likelihood threshold is satisfied for a second time window, wherein the set of parameter values further includes the second time window and the second likelihood threshold for the second mobility event type of the set of mobility event types.

4. The baseband processor of claim 1 , wherein:the set of mobility event types are a first set of mobility event types configured to predict the mobility event using the mobility event prediction model for a first radio frequency spectrum band; andthe configuration message further identifies a second set of mobility event types for the first radio frequency spectrum band or a second radio frequency spectrum band, the second set of mobility event types configured to use a deterministic comparison to identify that the mobility event has occurred.- 25 - P70385W01 Specification. docx5. The baseband processor of claim 1, wherein the first mobility event type is a signal quality of the serving cell that meets or exceeds a threshold quality with a likelihood that satisfies the likelihood threshold.

6. The baseband processor of claim 1, wherein the first mobility event type is a signal quality of the serving cell below a threshold quality with a likelihood that satisfies the likelihood threshold.

7. The baseband processor of claim 1 , wherein the first mobility event type is a signal quality of the neighbor cell meeting or exceeding a threshold quality with a likelihood that satisfies the likelihood threshold.

8. The baseband processor of claim 1, wherein the first mobility event type is a signal quality of the neighbor cell below a threshold quality with a likelihood that satisfies the likelihood threshold.

9. The baseband processor of claim 1, wherein the first mobility event type is a first signal quality of a secondary primary cell below a first threshold quality, and the neighbor cell meets or exceeds a threshold quality with a likelihood that satisfies the likelihood threshold.

10. The baseband processor of claim 1 , wherein the first mobility event type is a likelihood of a radio link failure greater than or equal to a threshold likelihood.

11. A network device, comprising:a transceiver; anda processor configured to cause the network device to:transmit, to a user equipment (UE) via the transceiver, a configuration message identifying a set of parameter values for a respective set of mobility event types, the set of parameter values including a time window and a likelihood threshold for a first mobility event type of the set of mobility event types, the first mobility event type to be used to predict a mobility event;transmit, to the UE via the transceiver, a measurement configuration indicating a set of measurement occasions for the UE to use to measure reference signals transmitted by a serving cell or a neighbor cell of the UE; and- 26 - P70385W01 Specification. docxreceive, from the UE via the transceiver and in response to a determination that the likelihood threshold is satisfied, a report indicating that the likelihood threshold is satisfied for the time window and the first mobility event type has occurred.

12. The network device of claim 11, wherein the processor is further configured to cause the network device to:transmit, via the transceiver and responsive to the received report, a control message indicating for the UE to perform a mobility procedure.

13. The network device of claim 11, wherein:the set of parameter values further include a second time window and a second likelihood threshold for a second mobility event type of the set of mobility event types.

14. The network device of claim 11, wherein:the set of mobility event types are a first set of mobility event types configured to predict the mobility event using the mobility event prediction model for a first radio frequency spectrum band; andthe configuration message further identifies a second set of mobility event types for the first radio frequency spectrum band or a second radio frequency spectrum band, the second set of mobility event types configured to use a deterministic comparison to identify that the mobility event has occurred.

15. The network device of claim 11, wherein:the first mobility event type is based at least in part on a signal quality of the serving cell or the neighbor cell satisfying or failing to satisfy a threshold quality with a likelihood that satisfies the likelihood threshold.

16. A method of wireless communication at a user equipment (UE), comprising:receiving a configuration message identifying a set of parameter values for a respective set of mobility event types, the set of parameter values including a time window and a likelihood threshold for a first mobility event type of the set of mobility event types, the first mobility event type to be used to predict a mobility event;obtaining measurements of reference signals for the time window, the reference signals measured according to a measurement configuration for the reference signals from one or both of a serving cell or a neighbor cell;- 27 - P70385W01 Specification. docxdetermining, based at least in part on the obtained measurements, that the likelihood threshold for the first mobility event type is satisfied for the time window; and transmitting, responsive to the determination that the likelihood threshold is satisfied, a report indicating the first mobility event type.

17. The method of claim 16, further comprising:receiving the measurement configuration indicating a set of measurement occasions for the UE to use to measure the reference signals transmitted by the serving cell or the neighbor cell of the UE;receiving the reference signals using the set of measurement occasions of the measurement configuration; andperforming, for the time window, one or more measurements according to the measurement configuration.

18. The method of claim 16, further comprising:receiving, responsive to the transmitted report, a control message indicating to perform a mobility procedure; andperforming the mobility procedure responsive to the control message, the mobility procedure comprising reconnecting with the serving cell or re-establishing a radio resource control (RRC) connection with the neighbor cell.

19. The method of claim 16, further comprising:determining, for a second mobility event type of the set of mobility event types, whether a second likelihood threshold is satisfied for a second time window, wherein the set of parameter values further includes the second time window and the second likelihood threshold for the second mobility event type of the set of mobility event types.

20. The method of claim 16, wherein:the set of mobility event types is a first set of mobility event types configured to predict the mobility event using the mobility event prediction model for a first radio frequency spectrum band; andthe configuration message further identifies a second set of mobility event types for the first radio frequency spectrum band or a second radio frequency spectrum band, the second set of mobility event types configured to use a deterministic comparison to identify that the mobility event has occurred.- 28 - P70385W01 Specification. docx

Images