Record information related to the conditional switching execution of multiple events on the wireless network.

Abstract

According to an example embodiment, a method may include a user equipment in a wireless network recording information related to the execution of a multi-event conditional handover, wherein the execution of the multi-event conditional handover is based on a joint evaluation of multiple events by the user equipment; and the user equipment sending a report including at least a portion of the information.

Description

Technical Field

[0001] This manual relates to wireless communication. Background Technology

[0002] A communication system can be a facility that enables communication between two or more nodes or devices, such as fixed or mobile communication devices. Signals can be carried by wired or wireless carriers.

[0003] An example of a cellular communication system is the architecture standardized by the 3rd Generation Partnership Project (3GPP). Recent developments in this area are often referred to as the Long Term Evolution (LTE) of Universal Mobile Telecommunications System (UMTS) radio access technology. E-UTRA (Evolved UMTS Terrestrial Radio Access) is the air interface for the 3GPP LTE upgrade path for mobile networks. In LTE, base stations or access points (APs), known as Enhanced Node APs (eNBs), provide radio access within a coverage area or cell. In LTE, mobile devices or mobile stations are referred to as User Equipment (UEs). LTE has incorporated numerous improvements and developments. Various aspects of LTE are constantly being improved.

[0004] The development of 5G New Radio (NR) is part of the ongoing evolution of mobile broadband to meet the requirements of 5G, similar to the early evolution of 3G and 4G wireless networks. Beyond mobile broadband, 5G also targets emerging use cases. The goal of 5G is to significantly improve wireless performance, which can include higher levels of data rates, latency, reliability, and security. 5G NR can also scale to efficiently connect massive amounts of Internet of Things (IoT) and can propose new mission-critical services. For example, ultra-reliable and low-latency communication (URLLC) devices may require high reliability and very low latency. Summary of the Invention

[0005] According to an example embodiment, a method may include a user equipment in a wireless network recording information related to the execution of a multi-event conditional handover, wherein the execution of the multi-event conditional handover is based on a joint evaluation of multiple events by the user equipment; and the user equipment sending a report including at least a portion of the information.

[0006] According to another example embodiment, a method may include a network node sending a handover command to a user equipment (UE) having joint event configuration information, the joint event configuration information including configurations of multiple events to be jointly evaluated by the UE for conditional handover execution; the network node receiving a report including information recorded by the UE related to a failure of the UE's multi-event conditional handover execution, wherein the multi-event conditional handover execution is based on multiple events; and the network node modifying one or more parameters associated with the configurations for one or more events used in the multi-event conditional handover execution based on the report.

[0007] Other example embodiments are provided or described for each of the example methods, including: components for implementing any one of the example methods; a non-transient computer-readable storage medium including instructions stored thereon, which, when executed by at least one processor, are configured to cause a computing system to implement any one of the example methods; and an apparatus including at least one processor and at least one memory, including computer program code, the at least one memory and the computer program code being configured, together with at least one processor, to cause the apparatus to at least implement any one of the example methods.

[0008] Details of one or more embodiments are set forth in the accompanying drawings and the following description. Other features will be apparent from the specification, drawings, and claims. Attached Figure Description

[0009] Figure 1 This is a block diagram of a wireless network according to an example embodiment.

[0010] Figure 2 This is a flowchart illustrating the operation of a user equipment (UE) according to an example embodiment.

[0011] Figure 3 This is a flowchart illustrating the operation of a network node (e.g., a BS or gNB) according to an example embodiment.

[0012] Figure 4 This is a schematic diagram illustrating a conditional switching of multiple events (CHO) according to an example embodiment.

[0013] Figure 5 This is a schematic diagram illustrating the execution of a dual-event conditional switch (CHO) according to an example embodiment.

[0014] Figure 6 This is a block diagram of a wireless station or wireless node (e.g., AP, BS, gNB, RAN node, relay node, UE, or user equipment or other node) according to an example embodiment. Detailed Implementation

[0015] Figure 1 This is a block diagram of a wireless network 130 according to an example embodiment. Figure 1In the wireless network 130, user equipment 131, 132, 133, and 135 (also referred to as mobile stations (MS) or user equipment (UE)) can connect to (and communicate with) a base station (BS) 134, which can also be referred to as an access point (AP), an enhanced node B (eNB), a BS, a next-generation node B (gNB), a next-generation enhanced node B (ng-eNB), or a network node. The terms user equipment and user equipment (UE) are used interchangeably. A BS may also include or be referred to as a RAN (Radio Access Network) node, and may include a portion of a BS or a portion of a RAN node, such as (e.g., in the case of a split BS, such as a centralized unit (CU) and / or a distributed unit (DU)). The functionality of a BS (e.g., an access point (AP), a base station (BS), or an (e) node B (eNB), a BS, or a RAN node) may also be implemented in at least part by any node, server, or host operatively coupled to a transceiver, such as a remote radio headend. BS (or AP) 134 provides wireless coverage within cell 136, including to user equipment (or UE) 131, 132, 133, and 135. Although only four user equipment (or UE) are shown connected to or attached to BS 134, any number of user equipment can be provided. BS 134 is also connected to core network 150 via S1 interface or NG interface 151. This is just a simplified example of a wireless network; other examples may also be used.

[0016] A base station (e.g., such as BS 134) is an example of a radio access network (RAN) node within a wireless network. A BS (or RAN node) may be or may include (or may alternatively be referred to as) such as an access point (AP), gNB, eNB, or a portion thereof (such as a centralized unit (CU) and / or distributed unit (DU) in the case of splitting a BS or gNB) or other network nodes.

[0017] According to illustrative examples, a BS node (e.g., BS, eNB, gNB, CU / DU, ...) or radio access network (RAN) can be part of a mobile telecommunications system. The RAN (radio access network) may include one or more BS or RAN nodes implementing radio access technologies, for example, to allow one or more UEs to access the network or core network. Thus, for example, the RAN (RAN node, such as BS or GNB) may reside between one or more user equipment or UEs and the core network. According to example embodiments, each RAN node (e.g., BS, eNB, gNB, CU / DU, ...) or BS may provide one or more wireless communication services to one or more UEs or user equipments, for example, to allow UEs to wirelessly access the network via the RAN node. Each RAN node or BS may implement or provide wireless communication services, such as allowing a UE or user equipment to establish a wireless connection to the RAN node, and to send data to one or more UEs and / or receive data from one or more UEs. For example, after establishing a connection to a UE, the RAN node (e.g., BS, eNB, gNB, CU / DU, ...) may forward data received from the network or core network to the UE, and / or forward data received from the UE to the network or core network. RAN nodes (e.g., BS, eNB, gNB, CU / DU, ...) can implement a wide variety of other radio functions or services, such as broadcasting control information (e.g., system information) to UEs, paging UEs when data needs to be delivered to them, assisting UEs in handover between cells, scheduling resources for uplink data transmission from UE(one or more) and downlink data transmission to UE(one or more), sending control information to configure one or more UEs, etc. These are just a few examples of one or more functions that a RAN node or BS can implement. A base station can also be a DU (Distributed Unit) portion of an IAB (Integrated Access and Backhaul) node (also known as a relay node). A DU facilitates the connection of (multiple) access links of an IAB node.

[0018] User equipment (user terminal, user equipment (UE), mobile terminal, handheld wireless device, etc.) can refer to portable computing devices including wireless mobile communication devices that operate with or without a Subscriber Identity Module (SIM), including but not limited to the following types of devices: mobile station (MS), mobile phone, cellular phone, smartphone, personal digital assistant (PDA), cell phone, device using a wireless modem (alarm or measuring device, etc.), laptop and / or touchscreen computer, tablet computer, tablet phone, game console, laptop computer, vehicle, sensor and multimedia device, as an example, or any other wireless device. It should be understood that user equipment can also be (or may include) a virtually exclusive uplink-only device, an example of which is a camera or camcorder that loads image or video clips onto the network. User equipment can also be the MT (Mobile Terminal) portion of an IAB (Integrated Access and Backhaul) node (also known as a relay node). The MT facilitates backhaul connections for the IAB node.

[0019] In LTE (as an illustrative example), the core network 150 may be referred to as the Evolved Packet Core (EPC), which may include a Mobility Management Entity (MME) that handles or assists user equipment in mobility / handover between BSs; one or more gateways that forward data and control signals between the BS and a packet data network or the Internet; and other control functions or blocks. Other types of wireless networks, such as 5G (which may be referred to as New Radio (NR)), may also include a core network.

[0020] Furthermore, through illustrative examples, the various exemplary embodiments or technologies described herein can be applied to various types of user equipment or data service types, or to user equipment on which multiple applications can run for different data service types. New radio (5G) developments can support many different applications or many different data service types, such as, for example: Machine-Type Communications (MTC), Enhanced Machine-Type Communications (eMTC), Internet of Things (IoT) and / or Narrowband IoT user equipment, Enhanced Mobile Broadband (eMBB), and Ultra-Reliable and Low-Latency Communications (URLLC). Many of these new 5G (NR) related applications may require higher performance than previous wireless networks.

[0021] The Internet of Things (IoT) can refer to a growing group of objects that possess internet or network connectivity, enabling them to send and receive information from other network devices. For example, many sensor-type applications or devices can monitor physical conditions or states and, for instance, send reports to servers or other network devices when events occur. Machine-type communication (MTC, or machine-to-machine communication), for example, can be characterized by fully automated data generation, exchange, processing, and driving between intelligent machines, with or without human intervention. Enhanced Mobile Broadband (eMBB) can support data rates significantly higher than those currently available in LTE.

[0022] Ultra-Reliable and Low-Latency Communication (URLLC) is a new type of data service or use case that can support new radio (5G) systems. This enables emerging new applications and services, such as industrial automation, autonomous driving, vehicle safety, e-health services, and more. As an example, 3GPP aims to provide [equipment / services] corresponding to 10 [unclear - possibly 5G]. -5 The block error rate (BLER) and U-plane (user / data plane) latency of up to 1 ms affect the reliability of connectivity. Therefore, for example, URLLC user equipment / UEs may require significantly lower block error rates and lower latency than other types of user equipment / UEs (with or without high reliability requirements). Thus, for example, a URLLC UE (or URLLC application on a UE) may require much shorter latency compared to an eMBB UE (or an eMBB application running on a UE).

[0023] Various example embodiments can be applied to a wide variety of wireless technologies or wireless networks, such as LTE, LTE-A, 5G (New Radio (NR)), cmWave and / or mmWave band networks, IoT, MTC, eMTC, eMBB, URLLC, etc., or any other wireless network or wireless technology. These example networks, technologies, or data service types are provided as illustrative examples only.

[0024] User equipment (UE) handover refers to the process of transferring a UE's connected call or data session from one cell (or base station) to another without interrupting the session. In some wireless technologies, such as 5G / New Radio (NR), operating at higher frequencies can present additional mobility challenges because the increased diffraction loss at these frequencies can lead to rapid signal attenuation due to obstacles. Therefore, reliable and efficient handover is desirable to ensure UE mobility.

[0025] According to the example implementation, Conditional Handover (CHO) can be used to improve mobility robustness. In the example CHO, CHO handover preparation and CHO handover execution can be separated. For example, during the example CHO process, the serving cell can prepare for the handover of the UE to the target cell in advance, and then perform the handover of the UE from the source cell to the target cell later when the radio link between the UE and the target cell is sufficient or when the CHO execution conditions are met. Therefore, CHO can allow the serving BS / gNB (associated with or providing the source cell currently serving the UE) to prepare multiple possible target cells, and then perform a handover to one of the target cells for the UE later. The advantage of CHO is that when the radio link between the UE and the source cell is still good, the source cell (or source / serving BS / network node) can send a handover (HO) command to the UE in advance, and then the UE can perform the CHO execution later if the CHO execution conditions are met. As mentioned, after the target cell has been prepared for a possible handover by the source cell, the source cell (serving BS / network node) can send a handover (HO) command to the UE, providing the target cell configuration (e.g., including an indication of the UE's random access / RACH resources in the target cell) and the event configuration to be used for CHO execution (including one or more parameters of the event). If the CHO execution conditions are met, the UE can execute the CHO. CHO execution conditions are typically based on one or more events. For example, using a single event, if the event's entry conditions are met within at least one triggering time period, the UE can execute (trigger) a CHO for the target cell.

[0026] The UE can receive configurations of conditional handover (CHO) execution conditions for the target cell from the source cell or source / serving network node (gNB / BS). These configurations can include one or more parameters that can be defined by the UE to determine the CHO execution conditions. For example, the CHO execution condition configuration can include an event configuration that includes one or more parameters for events that define entry or exit conditions for the event. In a single event CHO, the CHO execution condition is satisfied or met if the event's entry condition is satisfied within a minimum time period known as the trigger time (TTT). For example, the UE can periodically execute signal measurements of signals received from the source cell and one or more neighboring (or potential target) cells. The UE's measurements can include measured reference signal received power (RSRP), reference signal received quality (RSRQ), or other signal measurements. For example, for event A3, the CHO execution condition can indicate that the target cell measurement should be better than (e.g., greater than) the source cell measurement by an indicated threshold or offset(s). For example, CHO execution conditions can be configured (or indicated to the UE) by the source node (source BS / gNB) in a reconfiguration message that can be sent by the source BS (source node) to the UE (e.g., in a Radio Resource Control (RRC) reconfiguration message or a handover command).

[0027] As an illustrative example, the example of event A3 can be configured as an example event for CHO execution conditions. For instance, if the entry condition of event A3 (indicated by Equation 1) satisfies a certain trigger time (TTT), then CHO execution on the UE can be triggered, where TTT can refer to the minimum time period during which the entry condition of the event must be met or fulfilled to trigger or cause CHO execution on the UE from the source cell to the target cell:

[0028] Mn + Ofn + Ocn - Hys > Mp + Ofp + Ocp + Off (Equation 1)

[0029] Where Mn is the measurement of the neighboring target cell to be handed over, Mp is the measurement of the serving cell, and Ocn is the cell-specific offset (CIO). Parameters Ofn, Ofp, Ocp, Off, and Hys are other offsets that can be configured by the network (and can be indicated in the configuration of the conditional handover execution conditions). The CIO (shown as Ocn in Equation 1) can be an offset that can be specifically applied to neighboring cell measurements (and can be specific to the target / neighboring cell) to make such neighboring cell measurements more attractive for UE handover (e.g., via positive CIO) or less attractive for UE handover (e.g., via negative CIO).

[0030] The exit condition for event A3 can be defined by Equation 2:

[0031] Mn + Ofn + Ocn + Hys > Mp + Ofp + Ocp + Off (Equation 2)

[0032] Because the entry condition for event A3 uses a single threshold, event A3 is an example of a single-threshold event or a non-double-threshold event. Therefore, for event A3, the entry condition requires the target (or neighboring) cell measurement to become at least better than the source cell measurement.

[0033] Another example event, event A5, is an example of a dual-threshold event because event A5 can use two thresholds to determine whether the event meets the entry (or exit) conditions. For event A5 (equation not shown), the entry condition requires the source cell measurement to be worse than (e.g., less than) a first threshold, and the target cell to be better than (e.g., stronger than or greater than) a second threshold. Events A3 and A5 are example events, and other events can be used for CHO execution.

[0034] Furthermore, to improve the reliability and / or performance of UE CHO execution, CHO execution can be based on multiple events (e.g., dual-event CHO execution). These multiple events can be based on measurements of different signal parameters, such as Reference Signal Received Power (RSRP) or Reference Signal Received Quality (RSRQ). Therefore, conditional switching of multiple events can use different events (e.g., A3 event + A5 event), or can be based on the same or different events to measure different signal parameters, such as: RSRP-based A3 event + RSRQ-based A3 event; or RSRP-based A3 event + RSRQ-based A5 event; or RSRQ-based A3 event + RSRP-based R5 event, etc.

[0035] The UE may receive a multi-event CHO configuration from a source cell or serving network node, for example, via a handover command. This configuration may include one or more of the following: target cell configuration (e.g., indicating the UE's random access / RACH resources), CHO execution conditions, and event configurations for the multiple events (e.g., where the event configuration may include or identify one or more events (e.g., A3 or A5 events), signal parameters to be measured (e.g., RSRP or RSRQ), one or more offsets, hysteresis of the event's entry conditions, and / or the event's TTT value). Therefore, each event may include its own event configuration, which may specify one or more parameters for the event, such as the event type (e.g., A3 or A5 event), signal parameters to be measured (e.g., RSRP or RSRQ), offset of the entry conditions, TTT value, etc.

[0036] Multi-event CHO execution conditions, which may be known in advance by the UE or transmitted to the UE as part of a multi-event CHO configuration signal, can indicate the state or condition of each event in the multi-event CHO, or the relationship between the events, which requires that state or condition to occur in order to satisfy the CHO execution conditions of the multi-event CHO execution (and thus trigger CHO execution). For example, for a dual-event CHO execution based on two events (a first event and a second event), the UE can jointly evaluate (whereby the UE evaluates aspects of both events, e.g., in some cases even simultaneously) both the first and second events to determine whether the following multi-event CHO execution condition has been met: if the first event, which has an expired trigger timeout (TTT) timer, does not satisfy the departure condition of the first event when the trigger timeout (TTT) timer of the second event expires, then the UE performs the multi-event CHO execution. This is an example of a multi-event CHO execution condition; other conditions may also be used.

[0037] In some cases, CHO may fail, for example, leading to a Radio Link Failure (RLF) or Handover (HO) failure for the UE. An HO failure can occur when the UE fails to successfully implement random access to the target cell. In Radio Resource Control (RRC) connection modes (e.g., RRC_CONNECTED mode), the UE typically monitors the serving cell radio link, a process known as Radio Link Monitoring (RLM), and performs RLM measurements. RLM measurements help assess the serving cell radio link quality to determine if the downlink (DL) radio link quality is good enough (e.g., sufficient) to maintain the radio link and / or to indicate to higher layers when the radio link quality falls below a defined threshold (e.g., when it is expected that the radio link will no longer be able to provide sufficiently good quality for data transmission). RLM may include a procedure through which the UE or user equipment can monitor the radio link between the UE and the serving gNB or serving cell to detect or declare a radio link failure in certain circumstances.

[0038] In the case of a single-event CHO, the UE can collect and / or store information prior to an RLF or HO failure, which can then be reported to the network. However, this collected information is specific to a single-event CHO and has a very limited scope. More detailed information related to multi-event CHO execution is needed; for example, this would allow the UE to determine which event might have been the cause of an RLF or HO failure and how parameters can be adjusted to improve CHO execution performance.

[0039] Figure 2This is a flowchart illustrating the operation of a user equipment (UE) according to an example embodiment. Operation 210 includes the UE in the wireless network recording information related to the execution of a multi-event conditional handover, wherein the multi-event conditional handover execution is based on a joint evaluation of multiple events by the UE. Recording may include creating or saving a log or record. Recording may include, for example, creating a log or record that records (or stores) information related to events or event-related conditions of the conditional handover execution for the UE or UE. For example, recording information related to the execution of a multi-event conditional handover may include, for example, recording or storing a variety of event-related conditions. Event-related conditions may include, for example, one or more states of the state of an event's trigger timer, including states of not started, started, started but stopped, or expired; events that satisfy the entry conditions of an event; events that satisfy the departure conditions of an event; the occurrence of a handover failure of the UE; or whether the execution conditions of the multi-event conditional handover execution are met. For example, the record may include the occurrence of event-related conditions, the time when event-related conditions occur, the number of times event-related conditions occur, or the relationship (e.g., sequence or order) between the occurrence of event-related conditions of different events (e.g., which event has a specific event-related condition that occurs first), or other information related to events performed by a multi-event CHO.

[0040] Multi-event conditional handover execution can be based on a joint evaluation of multiple events by the user equipment. For example, this may include the UE / user equipment evaluating information related to two events (e.g., one or more condition-related events) at different points in time (e.g., this may include evaluating the condition-related events of two events simultaneously or concurrently) to determine whether the multi-event CHO execution conditions have been met. If the multi-event CHO execution conditions have been met, the UE may (or typically will) execute the CHO on the target cell.

[0041] In addition, regarding Figure 2Operation 220 includes sending a report containing at least a portion of information by the user equipment or UE. Therefore, the report may include at least a portion of information recorded by the UE. This report (e.g., it may include recorded information) may be sent by the UE to the network node or network, for example, after detecting an RLF or HO failure (after the UE re-establishes the connection) or in response to a request from a network node (BS, gNB). For example, by recording and then sending a more detailed log of information related to the multi-event CHO execution, this may allow the network, the source network node (e.g., the source BS / gNB), or other network node or network to modify one or more parameters associated with the configuration of the CHO execution conditions and / or modify one or more parameters of one or more events of the multi-event CHO execution, for example, to improve the reliability and performance of the CHO execution. In one example, multi-event conditional handover execution may include a two-event (two-event) conditional handover execution based on a joint evaluation of two events.

[0042] about Figure 2 The transmission may include: after a handover failure or radio link failure occurs in the user equipment, or after the user equipment re-establishes a connection to the cell, the user equipment sends a report including at least a portion of the information.

[0043] about Figure 2 The method of transmission may include sending a report comprising at least a portion of information by a user equipment in response to a radio link failure or a handover failure; or sending a report comprising at least a portion of information by a user equipment in response to a request from a network node.

[0044] about Figure 2 The method allows for conditional switching execution across multiple events, which can be based on multiple events. The records may include at least the occurrence of event-related conditions, the number of times the event-related conditions occur, or the occurrence time or timing of the event-related conditions for one or more of the multiple events.

[0045] about Figure 2 The method may include at least one of the following: the state of the event trigger timer, including not started, started, started and stopped or expired; an event that meets the event entry condition; an event that meets the event exit condition; the occurrence of a user equipment switching failure; or whether the execution conditions for conditional switching of multiple events are met.

[0046] about Figure 2The method may record at least one of the following: recording information indicating whether an event-related condition has occurred for one or more of a plurality of events; recording information indicating the number of times an event-related condition has occurred for one or more of a plurality of events; recording the temporal relationship or time difference between the event-related conditions of at least two of the plurality of events; recording information indicating the time at which an event-related condition has occurred for one or more of the plurality of events; recording information indicating which event's event-related condition occurred first; or recording the number of user equipment switching failures caused by multiple events not meeting the execution conditions for conditional switching of multiple events.

[0047] In addition, the record may include information indicating whether event-related conditions have occurred for one or more of a plurality of events, for example, including one or more of the following: information indicating which event (if any) has met the event's entry conditions and started a trigger timer; information indicating which event (if any) has met the event's entry conditions, started a trigger timer, and the event's trigger timer has expired; information indicating whether execution conditions for conditional switching of execution of multiple events are met based on a joint evaluation of multiple events by the user equipment; information indicating whether a first event with an expired trigger timer meets the first event's exit conditions when the trigger timer of a second event expires; or information indicating which event (if any) meets the event's entry conditions, starts its trigger timer, and the event's trigger timer is stopped before it expires.

[0048] about Figure 2 The method may include recording information indicating the number of times event-related conditions have occurred for one or more of a plurality of events. This information may include, for example, recording the number of times each event (if any) starts its trigger timer and the number of times the event's trigger timer is stopped before it expires.

[0049] about Figure 2 The method of recording information may include at least one of the following: the order of the first event-related conditions of the first event and the second event-related conditions of the second event; the time between the occurrence of the first event-related conditions of the first event and the occurrence of the second event-related conditions of the second event; or the time of occurrence of the first event-related conditions of the first event and the second event-related conditions of the second event.

[0050] about Figure 2The method of recording information indicating the relationship may include at least one of the following: recording whether the first event or the second event first satisfies the entry condition; recording the value of the trigger timer for the first event and the second event when one of the trigger timer stops or expires; or recording the time or time period when the trigger timers for the first event and the second event run in parallel.

[0051] about Figure 2 The method may include recording information indicating the time of occurrence of event-related conditions for one or more of a plurality of events, for example, including at least one of the following: recording information indicating the time when an event's trigger timer starts; recording information indicating the time when an event's trigger timer expires; recording information indicating the time when an event's trigger timer stops; or recording information indicating the time when a trigger timer for a first event runs in parallel with a trigger timer for a second event.

[0052] about Figure 2 The method may include recording information indicating which event-related conditions occur first, for example, it may include at least one of the following: recording information indicating which event (if any) satisfies the event's entry conditions and first starts the trigger timer; recording information indicating which event (if any)'s trigger timer expires first; or recording information indicating which event (if any) satisfies the event's entry conditions, starts the trigger timer, and then first stops the trigger timer.

[0053] about Figure 2 The method allows for the recording of information that may include multiple faults (e.g., HO faults and / or RLFs), which may be counted or tracked by various counters. Thus, for example, the recording may include recording a fault counter that counts the number of conditional switching faults of the user equipment caused by multiple events failing to meet the execution conditions for multi-event conditional switching. This may include recording one or more of the following when both the first and second events are non-dual-threshold measurement events: the number of conditional switching faults when the trigger timer for the first event has not expired; or the number of conditional switching faults when the trigger timer for the second event has not expired.

[0054] The fault counter may include recording one or more of the following information when both the first event and the second event are dual-threshold measurement events: the number of conditional handover faults when the trigger timer of the first event has not expired due to the source cell measurement value being not less than the first threshold; the number of conditional handover faults when the trigger timer of the second event has not expired due to the target cell measurement value being not greater than the second threshold; the number of conditional handover faults when the trigger timer of the second event has not expired due to the source cell measurement value being not less than the first threshold; or the number of conditional handover faults when the trigger timer of the first event has not expired due to the target cell measurement value being not greater than the second threshold.

[0055] Alternatively, the fault counter may include recording the number of times a conditional fault switchover occurs when a trigger timer for a first event expires and then a trigger timer for a second event expires, but when the trigger timer for the second event expires, the departure condition of the first event is met.

[0056] about Figure 2The record may include one or more of the following, for example: recording the configuration of the first event and / or the configuration of the second event; recording information indicating which event (if any) has met the event's entry conditions and started the trigger timer; recording information indicating which event (if any) has met the event's entry conditions, started the trigger timer, and the event's trigger timer has expired; recording information indicating whether the execution conditions for conditional switching of multiple events are met; recording information indicating whether the first event with an expired trigger timer meets the first event's exit conditions when the trigger timer of the second event expires; recording information indicating which event (if any) starts its trigger timer and the event's trigger timer is stopped before it expires; recording information indicating the number of times each event (if any) starts its trigger timer and the number of times the event's trigger timer is stopped before it expires; recording whether the first event or the second event first meets the entry conditions; recording when one of the trigger timers stops... The values ​​of the trigger timers for the first and second events when they expire; the time or time period when the trigger timers for the first and second events run in parallel; information indicating the time when the trigger timer for an event starts; information indicating the time when the trigger timer for an event expires; information indicating the time when the trigger timer for an event stops; information indicating the time when the trigger timers for the first and second events run in parallel; information indicating which event (if any) meets the event's entry conditions and starts its trigger timer first; information indicating which event (if any)'s trigger timer expires first; information indicating which event (if any) meets the event's entry conditions, starts its trigger timer, and then stops its trigger timer first; or a fault counter that counts the number of conditional switching failures of the user equipment caused by multiple events not meeting the execution conditions for conditional switching of multiple events.

[0057] about Figure 2 The method may further include receiving a handover command from a network node by a user equipment as part of a conditional handover, the handover command including configurations for each of a plurality of events, including at least configurations for a first event and a second event, and a joint evaluation configuration configured by the user equipment for a joint evaluation of the plurality of events to determine whether to perform a conditional handover.

[0058] about Figure 2The method may further include the joint evaluation of multiple events by the user equipment to determine whether to perform a conditional handover of the user equipment from the source network node to the target network node.

[0059] Figure 3 This is a flowchart illustrating the operation of a network node (e.g., a BS, gNB, or other network node) according to an example embodiment. Operation 310 includes the network node sending a handover command to a user equipment (UE) with joint event configuration information, which includes configurations of multiple events to be jointly evaluated by the UE for conditional handover execution. Operation 320 includes the network node receiving a report including information recorded by the UE related to a failure of the UE's multi-event conditional handover execution, wherein the multi-event conditional handover execution is based on multiple events. Furthermore, operation 330 includes the network node modifying one or more parameters associated with the configurations for one or more events used in the multi-event conditional handover execution based on the report.

[0060] about Figure 3 The method involves a joint event configuration information system, which includes a joint evaluation configuration. This system configures the joint evaluation of multiple events by the user equipment to determine whether to implement conditional handover execution. The joint event configuration information may include information describing the CHO execution conditions, the configuration of each of the multiple events, and so on.

[0061] about Figure 3 The method, wherein the information recorded by the user equipment may include at least one of the following: the occurrence of event-related conditions for one or more events among a plurality of events, the number of times the event-related conditions occur, or the occurrence time or timing of the event-related conditions. As mentioned, event-related conditions may include, for example, at least one of the following: the state of an event trigger timer, including a state of not started, started, started but stopped, or expired; an event that meets the event entry condition; an event that meets the event exit condition; the occurrence of a user equipment switching failure; or whether the execution conditions for conditional switching execution of multiple events are met.

[0062] about Figure 3 The method may include information recorded by the user equipment that may include at least one of the following: information indicating whether event-related conditions have occurred for one or more of a plurality of events; information indicating the number of times event-related conditions have occurred for one or more of a plurality of events; the time relationship or time difference of event-related conditions for at least two of a plurality of events; information indicating the time at which event-related conditions have occurred for one or more of a plurality of events; information indicating which event's event-related conditions occurred first; or the number of user equipment switching failures caused by multiple events not meeting the execution conditions for conditional switching of multiple events.

[0063] Figure 4 This is a schematic diagram illustrating a multi-event conditional switching (CHO) according to an example embodiment. Figure 4 The diagram illustrates UE 132, the serving node 210 (e.g., serving BS) associated with the source cell, and the target node 214 associated with the target cell. Furthermore, core network entities are shown, including, for example, the Serving Gateway / User Plane Function (S-GW / UPF), and the Mobility Management Entity / Access and Mobility Management Function (MME / AMF) functions. Operations 1 to 16 are... Figure 4 The diagram illustrates this. For example, operations 1 through 6 may be associated with CHO preparation, while operations 7 through 16 may be associated with CHO execution. At point 1, a measurement report(s) is sent to serving node 210, indicating, for example, the RSRP (or other signal measurements) of the source cell and one or more target cells, to allow serving node 210 to determine one or more possible target cells for a possible handover of the UE.

[0064] exist Figure 4 At point 2, serving node 210 can make a CHO decision, for example, performing a conditional handover of the UE to one or more (possible) target cells. At point 3, the CHO request is sent to target node 214 associated with the target cell. Although not shown, the CHO request can be sent to other target nodes. At point 4, target node 214 performs admission control to decide whether to accept the handover requested by UE 132. At point 5, target node 214 sends a CHO request confirmation to the target cell, accepting or confirming the CHO requested by UE 132, and providing the target cell configuration for the target cell.

[0065] exist Figure 4At point 6, the UE receives a reconfiguration message with a handover (HO) command (e.g., RRC reconfiguration). The RRC message may also include, for example, a multi-event CHO configuration, which may include one or more of the following: target cell configuration (e.g., including target resources for random access preamble / RACH), indications of multi-event CHO execution conditions (e.g., indicating what specific or even related conditions should exist or have occurred for multiple events to trigger CHO execution on the target cell), and event configurations for multiple events. For example, event configurations may include one or more parameters of the event's entry conditions (e.g., threshold, hyst, CIO, Off, or offset, or other parameters of the event's entry conditions, TTT values). For example, indications of multi-event CHO execution conditions may include fields or parameters that can indicate a specific multi-event CHO execution condition among multiple possible CHO execution conditions. For example, for a dual-event CHO execution based on two events (a first event and a second event), an example could be: if the first event has an expired trigger timeout (TTT) timer, and the departure condition of the first event is not met when the trigger timeout (TTT) timer of the second event expires, then the UE performs a multi-event CHO execution. This is an example of multi-event CHO execution conditions; other conditions may also be used. In some cases, multi-event CHO execution conditions may be pre-configured or known in advance by the UE.

[0066] exist Figure 4 The system records information related to the execution of multi-event CHOs at seven locations and allows for joint evaluation of multiple events (e.g., evaluation of multiple events, or simultaneous evaluation of various event-related conditions of multiple events at different time points) to determine whether the conditions for CHO execution have been met.

[0067] exist Figure 4 At point 8, the UE determines that the multi-event CHO execution conditions are met (e.g., based on the joint evaluation of multiple events, which triggers the CHO execution on the target cell / target node, and the UE 132 disconnects from the source node and stops transmitting to and receiving from the source node).

[0068] If a failure occurs during a CHO execution (e.g., an RLF or HO failure), the UE may (e.g., after reconnecting to the cell) send a report to the network node that may include all or part of the recorded information related to the multi-event CHO execution. Alternatively, a report including all or part of the recorded information related to the multi-event CHO execution may be sent to the network node upon request. The report including recorded information related to (e.g., a failed) multi-event CHO execution may be forwarded to, for example, the source node to allow the network and / or source node to perform Mobility Robustness Optimization (MRO), whereby the source node or network may determine which event is (or may already be) the cause of the failure, and then determine one or more parameters or functions related to the multi-event CHO execution that should be adjusted (e.g., adjusting the TTT or offset of the event that may have caused the failure) to improve the reliability and / or operation of the multi-event CHO execution.

[0069] Assuming there are no faults (e.g., assuming there are no RLF or HO faults), Figure 4 The remaining operations 9 through 16 are part of the CHO execution.

[0070] exist Figure 4 At point 9, the serving node 210 / source cell stops transmitting data to and receiving data from UE 132, and begins forwarding the UE's DL data to the target node 214. The DL data forwarded from the source node 210 to the target node 214 may include DL (downlink) data transmitted from the source node 210 to UE 132 but not acknowledged by the UE, as well as any newly received DL data (from the core network) that has been received by the source node 210 but has not yet been transmitted to UE 132.

[0071] exist Figure 4 At points 10 and 11, data forwarding is performed, including a sequence number state transition at point 10 and data forwarding at point 11. In the example embodiment, the source cell initiates data forwarding immediately after ceasing reception and transmission with the UE. Furthermore, the source cell sends an "SN State Transfer" message to the target cell for handover, which defines the next lost PDCPCOUNT value for the DL and UL, i.e., the next lost packet that the target cell should transmit in the DL or receive in the UL.

[0072] Subsequently, the UE can synchronize with the target node / target cell (e.g., receive PSS and SSS from the target node / target cell), and then perform random access with the target node / target cell to establish a connection, including sending a RACH (Random Access) preamble at point 12 and receiving a random access (RACH) response at point 13. Once the UE has established a connection with the target node / target cell, at point 14, the UE sends an RRC reconfiguration complete message / indication to the target node / target cell, and at point 15, the target node replies to the serving node / source cell with a handover success indication, and at point 16, path switching for UE services is performed between the core network and the source and target nodes.

[0073] Figure 5 This is a schematic diagram illustrating the execution of a two-event conditional switch (CHO) according to an example embodiment. Figure 5 As shown, two events are provided for multi-event (or dual-event) CHO execution, including events A3 and A5. At time T1, the UE receives a CHO (or handover) command, including, for example, a multi-event CHO configuration, such as CHO execution conditions and / or event configurations for each event. Therefore, for this example, at T1, the UE receives event configurations for events A3 and A5. At time T2, the UE determines that event A3 meets its entry condition for the first time (thus starting the TTT timer for event A3). At time T3, event A5 meets its entry condition for the first time, thus starting the TTT timer for event A5. At time T4, event A3 is triggered (the TTT timer for A3 expires). At time T5, event A5 is triggered (the TTT timer for event A5 expires). At time T5 indicated by 510 (along with various other possible times), the UE can jointly evaluate both events A3 and A5 to determine if the multi-event CHO execution conditions are met. Therefore, at T5, if the exit condition for event A3 is not true at T5, CHO execution is performed. Some example information elements (IEs) may be logged as part of a record of information related to the execution of a multi-event CHO. Figure 5 The times and events shown may be useful for explaining some examples of events that may be recorded in IE.

[0074] Assume that both Event 1 (Event A3) and Event 2 (Event A5) are configured to the UE as events for CHO execution conditions, and they will be evaluated simultaneously at one or more time points, for example, to determine whether the CHO execution conditions have been met (based on multiple events), thereby triggering CHO execution. Figure 5The possible timelines for these two events and their evaluations are given. Note that the described timelines can have many combinations (or multiple different scenarios and / or different occurrences of various event-related conditions), because it will be unknown which event will be triggered first, the time between the events being triggered, whether a joint evaluation of the two events at one or more points (e.g., simultaneously) will trigger CHO execution, etc. As an illustrative example, Figure 5 The timeline of the two events shown is only one possible timeline. Figure 5 The timeline shown depicts the best-case scenario for a successful CHO, or even a successful CHO execution. However, in general, RLF may exist at any point, such as any point between T1 and T5.

[0075] If a problem occurs between T1 and T5 (e.g., a fault, such as an RLF or HO fault), the UE can typically continue recording information related to the (attempted) multi-event CHO execution (e.g., recording the event-related conditions for each of the multiple events), and the UE can, for example, send a report to the network or serving node after reconnection (e.g., including all or part of the recorded information). If an RLF exists, the UE will become temporarily disconnected, and then the UE will connect or reconnect to the cell (by implementing random access).

[0076] although Figure 5 Not shown, but CHO preparation has been performed for the UE, and two events, A3 and A5 (as an example), have been configured. First, an event (A3 event fulfills its entry condition) is triggered, and a Time-to-Time (TTT) is initiated. While the first event (A3) is running, the second event (A5) fulfills its entry condition. The TTT for the first event (A3) expires, while the TTT for the second event (A5) continues. In this example, the joint evaluation point (or example) for both events is at T5—for example, after both events have expired (based on the successful CHO execution example). At time T5, the time when the second event has expired in this example, if the A3 exit condition is not true, the CHO is executed.

[0077] Currently, when performing CHOs using multiple (e.g., dual) events, UE records at RLFs and MRO (Mobility Robustness Optimization) KPIs (Key Performance Indicators) do not help the network / MRO identify the root cause of RLFs (or other failures). Therefore, especially in the case of multi-event CHO execution, the network is currently unable to make correct or accurate decisions regarding adjustments to mobility parameters that would improve performance.

[0078] As mentioned above, for each event, there may be multiple configurable (or variable) mobility-related parameters, such as offset, hysteresis, TTT, etc. If the mobility-related parameters for a measurement event are misconfigured, this may cause the UE to fail to perform CHO correctly, potentially leading to RLF. Therefore, properly configured or even optimized mobility parameters for multi-event CHO execution are desirable for efficient and correct CHO execution. Mobility robustness optimization (MRO), aimed at reducing the number of connectivity failures (radio link failures and handover failures) in the network, can address this issue by adjusting mobility parameters based on information or reports. Adjustments to (multiple) event parameters can be based on information recorded by the UE (e.g., recorded information related to multi-event CHO execution), and the UE can report this information to the network (or network node) in, for example, RLF reports, recorded measurement reports, or other reports. Information from RLF reports can also be added to recorded measurement reports evaluated by MDT features.

[0079] The UE can record various information, such as information related to multi-event CHO execution, which can be reported by the UE and later used by the network (e.g., the source network node) to adjust one or more parameters to improve the performance and / or reliability of CHO execution. Below is a list of some example information elements (IEs) that the UE can record / collect for one or more events (or related to) multi-event CHO execution. For example, in the case of a fault such as an RLF or HO failure, the UE can report this information or multiple pieces of information for the multi-event to the network or network node(s) to help the network or network node perform root cause analysis to determine the root cause of the fault (e.g., an RLF or HO failure) and / or to help improve future CHO execution. For example, root cause analysis performed by the network (such as a network node) based on the recorded information / IE can be performed to determine, for example, which of the multiple events is the cause of the fault, and what possible parameter adjustments should or can be performed to improve the performance and / or reliability of CHO execution. The following describes some example IEs that can be logged (and may be reported by the UE to the network / network node), as well as some example root cause analyses and possible parameter tunings that can be implemented to potentially improve the performance and / or reliability of CHO execution (e.g., parameter tuning designed to reduce RLF and / or HO failures).

[0080] IE (Information Element) 1: Identifies the configuration of Event 1 (A3) and Event 2 (A5 in this example) (the publishing cell may not maintain the configuration for a long time, and signaling values ​​from the network can be scaled on the UE side). The event configuration may indicate one or more of the following: such as the event type (e.g., A3 or A5), the signal parameters to be measured, and the associated hysteresis, offset, and TTT (which can be scaled by the UE based on UE speed) or other event-related parameters.

[0081] IE 2: Which event (if any) has met the entry conditions for the TTT duration, i.e., TTT started and TTT expired—Event 1, Event 2, both, or none. Provide information about these two events; for dual-event configuration of CHO.

[0082] IE 3: The timestamp (or time) when the event's TTT expires, for example, Figure 5 T4 / T5 in the middle.

[0083] IE 4: Indication of whether the first event (whose TTT has expired) does not meet the exit condition when the TTT of the second event expires – evaluation result at T5.

[0084] IE 5: Event 1 and / or Event 2 meet the entry conditions and start TTT.

[0085] IE 6: Timestamp (or time) when the event's TTT has been initiated — Figure 5 T2 and T3 in the example.

[0086] IE 7: The time difference between the first event of TTT (Time To Trial) starting when the entry condition is met and the second event of TTT starting when the entry condition is met. Figure 5 (T3-T2) in the middle.

[0087] IE 8: Time taken for two events (TTT) to run in parallel — Figure 5 (T4-T3)

[0088] IE 9: Which event satisfies the entry condition and starts TTT first—Event 1 or Event 2, or both simultaneously. Figure 5 In the example, at T2, the first event (A3) satisfies the entry condition and initiates TTT first.

[0089] IE 10: Event 1 / Event 2 TTT started, but was stopped before it expired.

[0090] IE 11: TTT value of event 1 / event 2 when stopped before expiration.

[0091] IE 12: Number of times the TTT for Event 1 / Event 2 starts and stops before it expires.

[0092] Some examples of how this information can be further used for Mobility Robustness Optimization (MRO) purposes (e.g., it can be based on combinations of information elements) are described below. CHO optimization is to increase the number of times CHO is triggered while maintaining stability, e.g., improving the reliability and performance of CHO. Note that Figure 5 A timeline showing a successful CHO execution is presented, where at T5, the UE triggers a CHO execution (based on a joint evaluation of two events at T5). However, although not shown in Figure 5 , many problems or failures may occur at any time, e.g., a failure such as an RLF HO failure may occur at any time in this timeline. Therefore, if a failure occurs at any time before T5, various other event-related conditions ( Figure 5 not shown) may occur and various IEs are used to record them. Therefore, Figure 5 Various other event-related conditions not shown in Figure 5 may occur and / or can be recorded by the UE, e.g., the TTT timer stops before expiration due to a failure or other conditions, the second event is not triggered or its TTT timer is started, the events do not overlap at all, etc. Therefore, many changes not shown in

[0093] IE 8: T4 - T3 equals zero (the TTTs of the two events do not overlap), and the value of IE 4 above = FALSE (when the TTT of the second event expires, the first event that satisfies the entry condition and whose TTT has expired satisfies the exit condition). Therefore, the overall evaluation of the two events takes too long, which means that the TTT of the second event can (or should) be relaxed or the offset of its entry condition be controlled so that the second event satisfies the entry condition earlier (and starts the TTT), and when the TTT of the second event expires, the first event has a better chance of not satisfying the exit condition.

[0094] IE 10 is true (the TTT stops before expiration) and the value of IE 11 << TTT, which may mean that the configuration of the event is too conservative. This is not shown in Figure 5 0]]but can occur.

[0095] The value of IE 2: In another example ( Figure 5 not shown), only the TTT of event 1 has expired. This means that the CHO has no chance to be executed. The configuration of event 2 should be modified.

[0096] The value of IE 2: In another illustrative example ( Figure 5(Not shown in the image), no events have TTTs expiring (TTTs for any of the events have not expired). This indicates that both event configurations should be modified.

[0097] The IE 6 value (the timestamp when the event's TTT has started) occurs long after time T1 has provided the CHO execution to the UE. This indicates that the configuration of both events can be relaxed.

[0098] In addition, faults can be counted or stored in the recorded information related to the execution of multi-event CHOs. Therefore, it is recommended to count faults (too late switching) caused by failure to meet the above-mentioned dual-event CHO execution conditions into a new sub-counter used for dual-event CHO execution.

[0099] Depending on whether a non-double-threshold measurement event (e.g., event A3), a double-threshold measurement event (e.g., event A5), or one of each event is used as one of the two events executed by a double-event CHO, there are three possible scenarios described here:

[0100] 1) When event 1 and / or event 2 are not double-threshold measurement events, the following sub-counters can be used, such as A3:

[0101] Event 1 was never triggered (the TTT for Event 1 had not expired):

[0102] The fault counter for CHO.OutFail.TooLateEvent1NotTriggered increments.

[0103] Event 2 was never triggered (the TTT for Event 2 had not expired):

[0104] The fault counter for CHO.OutFail.TooLateEvent2NotTriggered increments.

[0105] 2) If events 1 and / or 2 are double-threshold measurement events (e.g., A5), then we may have the following incrementing sub-counters when a specific type of fault occurs:

[0106] Event 1 was never triggered:

[0107] Since the source measurement value is not lower than threshold 1 (Th1), event 1 is never triggered.

[0108] The CHO.OutFail.TooLateEvent1OwnNotCrossed fault counter increments.

[0109] Since the target measurement value never exceeded threshold 2 (Th2), event 1 was never triggered.

[0110] CHO.OutFail.TooLateEvent1NeighbourNotCrossed fault counter increments

[0111] Event 2 was never triggered:

[0112] Since the source measurement value is not lower than Th1, event 2 is never triggered.

[0113] The fault counter CHO.OutFail.TooLateEvent2OwnNotCrossed increments.

[0114] Event 2 was never triggered because the target measurement value was not higher than Th2.

[0115] The fault counter for CHO.OutFail.TooLateEvent2NeighbourNotCrossed increments.

[0116] 3) For events A3 and A5: Events 1 and 2 are triggered, but when the TTT of the second event expires, the exit condition of the first triggering event is met. The CHO.OutFail.TooLateEvent12CombinatonNotTriggered fault counter increments.

[0117] Some examples will be described:

[0118] Example 1. A method comprising: a user equipment in a wireless network recording information relating to multi-event conditional handover execution, wherein the multi-event conditional handover execution is based on a joint evaluation of multiple events by the user equipment; and the user equipment sending a report including at least a portion of the information.

[0119] Example 2. According to the method described in Example 1, wherein multi-event conditional switching execution includes dual-event conditional switching execution based on the joint evaluation of two events.

[0120] Example 3. The method according to any one of Examples 1-2, wherein the transmission includes: after the user equipment has experienced a handover failure or radio link failure, and after the user equipment has re-established a connection to the cell, the user equipment sends a report including at least a portion of the information.

[0121] Example 4. The method according to Example 3, wherein the transmission includes at least one of the following: a report including at least a portion of information being transmitted by the user equipment in response to a radio link failure or handover failure; or a report including at least a portion of information being transmitted by the user equipment in response to a request from a network node.

[0122] Example 5. The method according to any one of Examples 1 to 4, wherein the conditional switching execution of multiple events is based on multiple events; wherein the record includes at least the record of the occurrence of event-related conditions for one or more of the multiple events, the number of times the event-related conditions occur, or the occurrence time or timing of the event-related conditions.

[0123] Example 6. According to the method described in Example 5, the event-related conditions include at least one of the following: the state of the trigger timer for the event, including the state of not started, started, started and stopped or expired; the event that satisfies the entry condition for the event; the event that satisfies the exit condition for the event; the occurrence of a handover failure of the user equipment; or whether the execution conditions for conditional handover execution of multiple events are met.

[0124] Example 7. The method according to any one of Examples 1 to 6, wherein multi-event conditional handover execution is based on multiple events; wherein the record includes at least one of the following: information indicating whether an event-related condition has occurred for one or more of the multiple events; information indicating the number of times an event-related condition has occurred for one or more of the multiple events; the time relationship or time difference between the event-related conditions of at least two of the multiple events; information indicating the time of the occurrence of the event-related condition for one or more of the multiple events; information indicating which event the event-related condition occurred first; or the number of handover failures of the user equipment caused by multiple events not meeting the execution conditions for multi-event conditional handover execution.

[0125] Example 8. The method according to any one of the examples, wherein multi-event conditional switching execution is based on multiple events; wherein the record includes information indicating whether an event-related condition has occurred for one or more of the multiple events.

[0126] Example 9. The method according to Example 8, wherein the information recording the event-related conditions indicating whether one or more of the multiple events has occurred includes at least one of the following: recording information indicating which event (if any) has met the entry conditions for the event and started a trigger timer; recording information indicating which event (if any) has met the entry conditions for the event, started a trigger timer, and the trigger timer of the event has expired; recording information indicating whether the execution conditions for conditional switching execution for the multiple events are met based on the joint evaluation of the multiple events by the user equipment; recording information indicating whether the first event with an expired trigger timer meets the exit conditions for the first event when the trigger timer for the second event expires; or recording information indicating which event (if any) meets the entry conditions for the event, starts its trigger timer, and the trigger timer for the event is stopped before it expires.

[0127] Example 10. The method according to any one of Examples 1 to 9, wherein multi-event conditional switching execution is based on multiple events; wherein the record includes information indicating the number of times that conditions related to one or more of the multiple events have occurred.

[0128] Example 11. The method according to Example 10, wherein the record includes information indicating the number of times related conditions for one or more of a plurality of events have occurred, including at least: information indicating the number of times each event (if any) starts its trigger timer and the number of times the trigger timer for the event is stopped before it expires.

[0129] Example 12. The method according to any one of Examples 1 to 7, wherein the conditional switching of multiple events is based on a plurality of events including at least a first event and a second event; wherein the record includes at least a record of information indicating the relationship between the first event-related conditions for the first event and the second event-related conditions for the second event.

[0130] Example 13. The method according to Example 12, wherein the information indicating the relationship includes at least one of the following: the order of a first event-related condition for a first event and a second event-related condition for a second event; the time between the occurrence of the first event-related condition for the first event and the occurrence of the second event-related condition for the second event; or the time of occurrence of the first event-related condition for the first event and the time of occurrence of the second event-related condition for the second event.

[0131] Example 14. The method according to any one of Examples 12 to 13, wherein the information recording the indication relationship includes at least one of the following: recording whether the first event or the second event first satisfies the entry condition; recording the value of the trigger timer of the first event and the second event when one of the trigger timers stops or expires; or recording the time or time period when the trigger timers of the first event and the second event run in parallel.

[0132] Example 15. The method according to any one of Examples 1 to 7, wherein multi-event conditional switching is performed based on multiple events; wherein the record includes information indicating the time of occurrence of event-related conditions for one or more of the multiple events.

[0133] Example 16. The method according to Example 15, wherein recording information including recording time of conditions related to one or more of a plurality of events that have occurred includes at least one of the following: recording information indicating time when a trigger timer for an event starts; recording information indicating time when a trigger timer for an event expires; recording information indicating time when a trigger timer for an event stops; or recording information indicating time when a trigger timer for a first event and a trigger timer for a second event are running in parallel.

[0134] Example 17. The method according to any one of Examples 1 to 7, wherein multi-event conditional switching execution is based on multiple events; wherein the record includes: information indicating which event-related conditions occur first.

[0135] Example 18. The method according to Example 17, wherein the information recording the event-related conditions for which event occurs first includes at least one of the following: recording information indicating which event (if any) satisfies the entry conditions for the event and starts the trigger timer first; recording information indicating which event (if any) has its trigger timer expire first; recording information indicating which event (if any) satisfies the entry conditions for the event, starts the trigger timer, and then stops the trigger timer first.

[0136] Example 19. The method according to any one of Examples 1 to 18, wherein the multi-event conditional handover execution is based on a plurality of events, including at least a first event and a second event; wherein the record includes a record fault counter that counts the number of faults in the conditional handover of the user equipment caused by the multiple events not meeting the execution conditions for the multi-event conditional handover execution.

[0137] Example 20. The method according to Example 19, wherein recording the fault counter includes recording one or more of the following information when both the first event and the second event are non-double threshold measurement events: the number of times a conditional fault switching occurs when the trigger timer for the first event has not expired; or the number of times a conditional fault switching occurs when the trigger timer for the second event has not expired.

[0138] Example 21. According to the method of Example 19, the fault counter includes recording one or more of the following information when both the first event and the second event are dual-threshold measurement events: the number of conditional handover faults when the trigger timer for the first event has not expired due to the source cell measurement value being not less than the first threshold; the number of conditional handover faults when the trigger timer for the second event has not expired due to the target cell measurement value being not greater than the second threshold; the number of conditional handover faults when the trigger timer for the second event has not expired due to the source cell measurement value being not less than the first threshold; or the number of conditional handover faults when the trigger timer for the first event has not expired due to the target cell measurement value being not greater than the second threshold.

[0139] Example 22. According to the method of Example 19, wherein recording the fault counter includes recording the number of times a conditional switching fault occurs when a trigger timer for a first event expires and then a trigger timer for a second event expires, but the departure condition of the first event is met when the trigger timer for the second event expires.

[0140] Example 23. The method according to any one of Examples 1 to 22, wherein multi-event conditional switching execution is based on multiple events, including at least a first event and a second event; wherein the recording includes at least one of the following: recording the configuration of the first event and / or the configuration of the second event; recording information indicating which event (if any) has satisfied the entry condition for said event and started a trigger timer; recording information indicating which event (if any) has satisfied the entry condition for the event, started a trigger timer, and the trigger timer for the event has expired; recording information indicating whether the execution conditions for multi-event conditional switching execution are satisfied; recording information indicating whether the first event with an expired trigger timer satisfies the exit condition of the first event when the trigger timer for the second event expires; recording information indicating which event (if any) starts its trigger timer and the event's trigger timer is stopped before it expires; recording information indicating the number of times each event (if any) starts its trigger timer and the number of times the event's trigger timer is stopped before it expires; recording whether the first event or the second event first satisfies the entry condition; Entry conditions; record the values ​​of the trigger timers for the first and second events when one of the trigger timers stops or expires; record the time or time period when the trigger timers for the first and second events run in parallel; record information indicating the time when the trigger timer for the event starts; record information indicating the time when the trigger timer for the event expires; record information indicating the time when the trigger timer for the event stops; record information indicating the time when the trigger timer for the first event and the trigger timer for the second event run in parallel; record information indicating which event (if any) meets the entry conditions for the event and starts the trigger timer first; record information indicating which event (if any) has its trigger timer expire first; record information indicating which event (if any) meets the entry conditions for the event, starts the trigger timer, and then stops the trigger timer first; or record a fault counter that counts the number of conditional switching failures of the user equipment caused by multiple events not meeting the execution conditions for conditional switching execution for multiple events.

[0141] Example 24. The method according to any one of Examples 1 to 23 further includes: receiving a handover command from a network node by a user equipment as part of a conditional handover, the handover command including a configuration for each of multiple events, including at least a configuration for a first event and a configuration for a second event, and a joint evaluation configuration configured by the user equipment to jointly evaluate the multiple events to determine whether to perform a conditional handover.

[0142] Example 25. The method according to any one of Examples 1 to 24 further includes: jointly evaluating multiple events by the user equipment to determine whether to perform a conditional handover of the user equipment from the source network node to the target network node.

[0143] Example 26. An apparatus comprising tools for carrying out the method of any one of Examples 1 to 25.

[0144] Example 27. A non-transient computer-readable storage medium including instructions stored thereon, which, when executed by at least one processor, are configured to cause a computing system to perform any one of Examples 1 to 25.

[0145] Example 28. An apparatus comprising: at least one processor; and at least one memory including computer program code; wherein the at least one memory and the computer program code are configured, together with the at least one processor, to cause the apparatus to perform at least the method described in any one of Examples 1 to 25.

[0146] Example 29. An apparatus comprising: at least one processor; and at least one memory including computer program code; wherein the at least one memory and the computer program code are configured, together with the at least one processor, to enable the apparatus to at least: record information related to multi-event conditional handover execution by a user equipment in a wireless network, wherein the multi-event conditional handover execution is based on a joint evaluation of multiple events by the user equipment; and transmit a report by the user equipment including at least a portion of the information.

[0147] Example 30. A method comprising: sending a handover command with joint event configuration information to a user equipment (UE), the joint event configuration information including configurations of multiple events to be jointly evaluated by the UE for conditional handover execution; receiving a report by the network node including information recorded by the UE related to a failure of the UE's multi-event conditional handover execution, wherein the multi-event conditional handover execution is based on multiple events; and modifying one or more parameters associated with the configurations for one or more events of the multi-event conditional handover execution based on the report.

[0148] Example 31. The method according to Example 30, wherein the joint event configuration information includes a joint evaluation configuration configured by the user equipment for joint evaluation of multiple events to determine whether to implement conditional handover execution.

[0149] Example 32. The method according to any one of Examples 30 to 31, wherein multi-event conditional switching execution includes dual-event conditional switching execution based on two events.

[0150] Example 33. The method according to any one of Examples 30 to 32, wherein the conditional switching execution of multiple events is based on multiple events; wherein the information recorded by the user equipment includes at least one of the following: the occurrence of an event-related condition of one or more of the multiple events, the number of times the event-related condition occurs, or the occurrence time or timing of the event-related condition.

[0151] Example 34. The method according to Example 33, wherein the event-related conditions include at least one of the following: the state of the trigger timer for the event, including not started, started, started and stopped or expired; an event that satisfies the entry conditions for the event; an event that satisfies the exit conditions for the event; the occurrence of a handover failure of the user equipment; or whether the execution conditions for conditional handover execution of multiple events are met.

[0152] Example 35. The method according to any one of Examples 30 to 34, wherein the multi-event conditional handover execution is based on multiple events; wherein the information recorded by the user equipment includes at least one of the following: information indicating whether an event-related condition has occurred for one or more of the multiple events; information indicating the number of times an event-related condition has occurred for one or more of the multiple events; the time relationship or time difference of the event-related conditions for at least two of the multiple events; information indicating the time when an event-related condition has occurred for one or more of the multiple events; information indicating which event the event-related condition occurred first; or the number of handover failures of the user equipment caused by multiple events not meeting the execution conditions for the multi-event conditional handover execution.

[0153] Example 36. The method according to any one of Examples 30 to 35, wherein multi-event conditional switching execution is based on multiple events, including at least a first event and a second event; wherein the information recorded by the user equipment includes at least one of the following: configuration of the first event and / or configuration of the second event; information indicating which event (if any) has satisfied the entry conditions for the event and started a trigger timer; information indicating which event (if any) has satisfied the entry conditions for the event, started a trigger timer, and the trigger timer for the event has expired; information indicating whether the execution conditions for multi-event conditional switching execution are satisfied; information indicating whether the first event with an expired trigger timer satisfies the exit conditions of the first event when the trigger timer for the second event expires; information indicating which event (if any) starts its trigger timer and the trigger timer for the event is stopped before it expires; information indicating the number of times each event (if any) starts its trigger timer and the number of times the trigger timer for the event is stopped before it expires; the first event or Whether the second event first meets the entry condition; the value of the trigger timer for the first and second events when one of the trigger timer stops or expires; the time or time period when the trigger timers for the first and second events run in parallel; information indicating the time when the trigger timer for the event starts; information indicating the time when the trigger timer for the event expires; information indicating the time when the trigger timer for the event stops; information indicating the time when the trigger timer for the first event and the trigger timer for the second event run in parallel; information indicating which event (if any) meets the entry condition for the event and starts the trigger timer first; information indicating which event (if any)'s trigger timer expires first; information indicating which event (if any) meets the entry condition for the event, starts the trigger timer, and then stops the trigger timer first; or a fault counter that counts the number of conditional switching failures of the user equipment caused by multiple events not meeting the execution conditions for conditional switching execution for multiple events.

[0154] Example 37. An apparatus comprising tools for carrying out the method described in any one of Examples 30 to 36.

[0155] Example 38. A non-transient computer-readable storage medium including instructions stored thereon, which, when executed by at least one processor, are configured to cause a computing system to perform any one of Examples 30-36.

[0156] Example 39. An apparatus comprising: at least one processor; and at least one memory including computer program code; wherein the at least one memory and the computer program code are configured, together with the at least one processor, to cause the apparatus to perform at least the method described in any one of Examples 30 to 36.

[0157] Figure 6 This is a block diagram of a wireless station or node (e.g., AP, BS, gNB, eNB, relay node or other network node, or user equipment / UE or other node) 1100 according to an example embodiment. The wireless station 1100 may include, for example, one or more (e.g., such as...) Figure 6 The two RF (radio frequency) or wireless transceivers 1102A and 1102B shown include a transmitter for transmitting signals and a receiver for receiving signals in each wireless transceiver. The wireless station also includes a processor or control unit / entity (controller) 1104 for executing instructions or software and controlling the transmission and reception of signals, and a memory 1106 for storing data and / or instructions.

[0158] Processor 1104 may also make decisions or determinations, generate frames, packets, or messages for transmission, decode received frames or messages for further processing, and perform other tasks or functions described herein. For example, processor 1104, which may be a baseband processor, may generate messages, packets, frames, or other signals for transmission via wireless transceiver 1102 (1102A or 1102B). Processor 1104 may control the transmission of signals or messages over the wireless network and may control the reception of signals or messages, etc., through the wireless network (e.g., after being down-converted by wireless transceiver 1102). Processor 1104 may be programmable and capable of executing software or other instructions stored in memory or other computer media to perform the various tasks and functions described above, such as one or more of the tasks or methods described above. Processor 1104 may be (or may include) such as hardware, programmable logic, a programmable processor executing software or firmware, and / or any combination of these. Using other terms, for example, processor 1104 and transceiver 1102 together may be considered a wireless transmitter / receiver system.

[0159] In addition, refer to Figure 6 The controller (or processor) 1108 can execute software and instructions, and can provide overall control for station 1100, and can provide... Figure 6 Other systems, not shown, provide control, such as controlling input / output devices (e.g., a display, a keypad), and / or may execute software for one or more applications provided on the wireless station 1100, such as an email program, an audio / video application, a word processor, an IP voice application, or other applications or software.

[0160] In addition, a storage medium may be provided that includes storage instructions, which, when executed by a controller or processor, cause the processor 1104 or other controller or processor to perform one or more of the functions or tasks described above.

[0161] According to another example embodiment, the RF or (multiple) wireless transceivers 1102A / 1102B can receive signals or data and / or transmit or send signals or data. The processor 1104 (and possibly the transceivers 1102A / 1102B) can control the RF or wireless transceivers 1102A or 1102B to receive, transmit, broadcast, or transmit signals or data.

[0162] However, the example embodiments are not limited to the system given as an example, and those skilled in the art can apply the solution to other communication systems. Another example of a suitable communication system is a 5G system. It is assumed that the network architecture of 5G will be very similar to that of advanced LTE. 5G may use multiple-input multiple-output (MIMO) antennas, far more base stations or nodes than LTE (the so-called small cell concept), including macro sites cooperating with smaller base stations, and perhaps also employ various radio technologies for better coverage and higher data rates.

[0163] It should be understood that future networks are most likely to utilize Network Functions Virtualization (NFV), a network architecture concept that proposes virtualizing network node functions as "building blocks" or entities that are operatively connected or linked together to provide services. Virtualized network functions (VNFs) can include one or more virtual machines running computer program code using standard or general-purpose servers instead of custom hardware. Cloud computing or data storage may also be utilized. In radio communications, this can mean that node operations can be implemented at least partially in servers, hosts, or nodes operatively coupled to a remote radio head. Node operations can also be distributed across multiple servers, nodes, or hosts. It should also be understood that the workforce distribution between core network operations and base station operations may differ from LTE, or may not even exist.

[0164] Example embodiments of the various technologies described herein can be implemented in digital electronic circuit systems or in computer hardware, firmware, or software. Example embodiments can be implemented as computer program products, i.e., computer programs tangibly implemented in an information carrier (e.g., in a machine-readable storage device or in a propagating signal) for execution by or control of a data processing apparatus (e.g., a programmable processor, a computer, or multiple computers). Embodiments can also be provided on a computer-readable medium or a computer-readable storage medium, which may be a non-transient medium. Embodiments of the various technologies may also include embodiments provided via transient signals or media, and / or program and / or software embodiments downloadable via the Internet or (multiple) other networks (wired and / or wireless networks). Furthermore, embodiments can be provided via machine-type communication (MTC) or via the Internet of Things (IoT).

[0165] A computer program can be in the form of source code, object code, or some intermediate form, and it can be stored on some carrier, distribution medium, or computer-readable medium, which can be any entity or device capable of carrying the program. Examples of such carriers include recording media, computer memory, read-only memory, photoelectric and / or electrical carrier signals, telecommunication signals, and software distribution packages. Depending on the required processing power, a computer program can be executed in a single electronic digital computer, or it can be distributed across multiple computers.

[0166] Furthermore, example embodiments of the various technologies described herein can utilize cyber-physical systems (CPS) (systems of collaborative computing elements that control physical entities). CPS enables the implementation and development of numerous interconnected ICT devices (sensors, actuators, processors, microcontrollers, etc.) embedded in physical objects at different locations. Mobile cyber-physical systems are a subclass of cyber-physical systems in which the physical systems discussed possess inherent mobility. Examples of mobile physical systems include mobile robots and electronic devices transported by humans or animals. The proliferation of smartphones has increased interest in the field of mobile cyber-physical systems. Therefore, various embodiments of the technologies described herein can be provided via one or more of these technologies.

[0167] Computer programs, such as one or more of the above-described computer programs, can be written in any programming language, including compiled or interpreted languages, and can be deployed in any form, including as standalone programs or modules, components, subroutines, or other units or parts thereof suitable for a computing environment. Computer programs can be deployed to execute on one or more computers at one location, or distributed across multiple locations and interconnected through a communication network.

[0168] The method steps can be implemented by one or more programmable processors executing a computer program or a portion thereof to perform the function by manipulating input data and generating output. The method steps can also be implemented by a dedicated logic circuit system, and the apparatus can be implemented as a dedicated logic circuit system, such as an FPGA (Field-Programmable Gate Array) or an ASIC (Application-Specific Integrated Circuit).

[0169] Processors suitable for executing computer programs include, for example, both general-purpose and special-purpose microprocessors, and any one or more processors of any type of digital computer, chip, or chipset. Generally, a processor receives instructions and data from read-only memory or random access memory, or both. Computer components may include at least one processor for executing instructions and one or more storage devices for storing instructions and data. Generally, a computer may also include or be operatively coupled to one or more mass storage devices for storing data, such as magnetic disks, magneto-optical disks, or optical disks, to receive data from or transfer data to, or both. Information carriers suitable for embodying computer program instructions and data include all forms of non-volatile memory, including, for example, semiconductor storage devices such as EPROMs, EEPROMs, and flash memory devices; magnetic disks, such as internal hard disks or removable disks; magneto-optical disks; and CD-ROMs and DVD-ROMs. Processors and memory may be complemented by or incorporated into a dedicated logic circuit system.

[0170] To provide interaction with the user, embodiments can be implemented on a computer having a display device for displaying information to the user, such as a cathode ray tube (CRT) or liquid crystal display (LCD) monitor; and a user interface through which the user can provide input to the computer, such as a keyboard and pointing devices, such as a mouse or trackball. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback, such as visual feedback, auditory feedback, or tactile feedback; and input from the user can be received in any form, including sound, speech, or tactile input.

[0171] The example embodiments can be implemented in a computing system that includes backend components, such as a data server, or middleware components, such as an application server, or frontend components, such as a client computer with a graphical user interface or web browser through which a user can interact with the embodiments or any combination of such backend, middleware, or frontend components. The components can be interconnected via digital data communication of any form or medium, such as a communication network. Examples of communication networks include local area networks (LANs) and wide area networks (WANs), such as the Internet.

[0172] Although certain features of the described embodiments have been illustrated herein, many modifications, substitutions, alterations, and equivalents will now occur to those skilled in the art. Therefore, it should be understood that the appended claims are intended to cover all such modifications and alterations consistent with the true spirit of the various embodiments.

Claims

1. A method of communication, comprising: Information related to the execution of a multi-event conditional handover is recorded by a user equipment in a wireless network, wherein the execution of the multi-event conditional handover is based on a joint evaluation of multiple events by the user equipment; as well as The user equipment sends a report including at least a portion of the information, wherein the record includes at least: the occurrence of event-related conditions for one or more of a plurality of events, the number of times the event-related conditions occur, or the time or timing of the occurrence of the event-related conditions.

2. The method according to claim 1, wherein the conditional switching execution of multiple events includes: Dual-event conditional switching execution based on joint evaluation of two events.

3. The method according to claim 1, wherein the sending comprises: After the user equipment has experienced a handover failure or radio link failure, and after the user equipment has re-established a connection to the cell, the user equipment sends a report including at least a portion of the information.

4. The method of claim 3, wherein the transmission comprises at least one of the following: A report including at least a portion of the information is sent by the user equipment in response to a radio link failure or handover failure; or The user equipment sends a report including at least a portion of the information in response to a request from a network node.

5. The method of claim 1, wherein the event-related conditions include at least one of the following: The status of the event trigger timer, including not started, started, started but stopped, or expired; An event that satisfies the entry conditions for the event described above; An event that satisfies the exit condition for the event described above; In response to the occurrence of handover failure of the aforementioned user equipment; or The condition for conditionally switching execution of the multiple events is determined by whether the execution conditions are met.

6. The method of claim 1, wherein the conditional switching execution of multiple events is based on multiple events; The record mentioned above includes at least one of the following: Record information indicating whether one or more of the multiple events have occurred; Record information indicating the number of times conditions related to one or more of the stated events have occurred; Record the temporal relationship or time difference between the event-related conditions of at least two of the multiple events; Record information indicating the time of time related to one or more of the events that have occurred; Record information indicating which event and related conditions occurred first; or Record the number of times the user equipment switching failures are caused by the multiple events not meeting the execution conditions for conditional switching execution for the multiple events.

7. The method of claim 1, wherein the conditional switching execution of multiple events is based on multiple events; The records mentioned therein include: The record indicates information related to whether one or more of the plurality of events have occurred.

8. The method of claim 7, wherein the information indicating whether one or more of the plurality of events has occurred includes at least one of the following: Record information indicating which event (if any) has met the entry conditions for the event and started the trigger timer; Record information indicating which event (if any) has met the entry conditions for the event, started the trigger timer, and the trigger timer for the event has expired; Based on the joint evaluation of multiple events by the user equipment, information is recorded indicating whether the execution conditions for conditional switching of execution for the multiple events are met; The record indicates whether the first event, which has an expired trigger timer, meets the exit condition for the first event when the trigger timer for the second event expires; or The record indicates which event (if any) satisfies the event's entry conditions, starts its trigger timer, and stops the trigger timer for the event before it expires.

9. The method of claim 1, wherein the conditional switching execution of multiple events is based on multiple events; The records mentioned therein include: Record information indicating the number of times conditions related to one or more of the multiple events have occurred.

10. The method of claim 9, wherein the record, which records information indicating the number of times an event-related condition has occurred for one or more of the plurality of events, comprises at least: Record information on the number of times each event (if any) is instructed to start its trigger timer, and the number of times the trigger timer for said event is stopped before it expires.

11. The method of claim 1, wherein the conditional switching execution of the multiple events is based on a plurality of events including at least a first event and a second event; The records mentioned therein include at least: A record indicating the relationship between a first event-related condition for the first event and a second event-related condition for the second event.

12. The method of claim 11, wherein the information indicating the relationship comprises at least one of the following: The order of the first event-related conditions for the first event and the second event-related conditions for the second event; The time between the occurrence of the first event-related condition for the first event and the occurrence of the second event-related condition for the second event; or The occurrence time of the first event-related condition for the first event and the occurrence time of the second event-related condition for the second event.

13. The method of claim 11, wherein the record indicating the relationship information comprises at least one of the following: Record whether the first or second event satisfies the entry condition first; Record the values ​​of the trigger timers for the first event and the second event when one of the trigger timers stops or expires; or Record the time or time period when the trigger timers for the first event and the second event run in parallel.

14. The method of claim 1, wherein the conditional switching execution of multiple events is based on multiple events; The records mentioned therein include: Record information indicating the time when the relevant conditions for one or more of the plurality of events have occurred.

15. The method of claim 14, wherein the record, which records information indicating the time of occurrence of conditions related to one or more of the plurality of events, comprises at least one of the following: Records information indicating the time when a timer for the event's trigger time is started; Record information indicating the time when the timer for triggering an event expires; Records information indicating the time when the timer for the event's trigger time stops; or Record information indicating the time when the trigger timer for the first event and the trigger timer for the second event run in parallel.

16. The method of claim 1, wherein the conditional switching execution of multiple events is based on multiple events; wherein the record includes: Record information indicating which event-related conditions occurred first.

17. The method of claim 16, wherein the information indicating which event-related condition first occurred includes at least one of the following: Record information indicating which event (if any) satisfies the entry conditions for said event and initiates the trigger timer first; Record information indicating which event (if any) trigger timer expires first; Record information indicating which event (if any) satisfies the event's entry condition, starts the trigger timer, and then stops the trigger timer first.

18. The method of claim 1, wherein the conditional switching execution of the multiple events is based on multiple events, including at least a first event and a second event; The record includes a fault counter that counts the number of faults in the conditional switching of the user equipment caused by the failure of the plurality of events to meet the execution conditions for conditional switching of the plurality of events.

19. The method of claim 18, wherein the fault-recording counter comprises: If both the first event and the second event are non-double threshold measurement events, record one or more of the following information: The number of times a conditional fault switching occurs when the trigger timer for the first event has not expired; or The number of times a conditional failover occurs when the trigger timer for the second event has not expired.

20. The method of claim 18, wherein the fault-recording counter comprises: If both the first event and the second event are dual-threshold measurement events, record one or more of the following information: The number of conditional handover failures when the trigger timer for the first event has not expired because the source cell measurement value is not less than the first threshold; The number of conditional handover failures when the trigger timer for the second event has not expired because the target cell measurement value is not greater than the second threshold; The number of conditional handover failures when the trigger timer for the second event has not expired because the source cell measurement value is not less than the first threshold; or The number of conditional handover failures when the trigger timer for the first event has not expired because the target cell measurement value is not greater than the second threshold.

21. The method of claim 18, wherein the fault-recording counter includes recording the following information: The number of times a conditional switching fault occurs, based on the expiration of the trigger timer for the first event and then the expiration of the trigger timer for the second event, but the departure condition for the first event is satisfied when the trigger timer for the second event expires.

22. The method of claim 1, wherein the conditional switching execution of the multiple events is based on multiple events, including at least a first event and a second event; The record mentioned above includes at least one of the following: Record the configuration of the first event and / or the configuration of the second event; Record information indicating which event (if any) has met the entry conditions for said event and started the trigger timer; Record information indicating which event (if any) has met the entry conditions for the event, started the trigger timer, and expired the trigger timer for the event; Record information on whether the execution conditions for conditional switching of execution for the multiple events are met; The record indicates whether the first event, which has an expired trigger timer, meets the exit condition of the first event when the trigger timer for the second event expires. Record information indicating which event (if any) starts its trigger timer, and that the trigger timer for said event is stopped before it expires; Record information on the number of times each event (if any) is instructed to start its trigger timer, and the number of times the trigger timer for that event is stopped before it expires; Record whether the first or second event satisfies the entry condition first; Record the values ​​of the trigger timers for the first event and the second event when one of the trigger timers stops or expires; Record the time or time period when the trigger timers for the first event and the second event run in parallel; Records information indicating the time when a timer for the event's trigger time is started; Record information indicating the time when the timer for triggering an event expires; Records information indicating the time when the timer for the event's trigger time stops; Record information indicating the time when the trigger timer for the first event and the trigger timer for the second event run in parallel; Record information indicating which event (if any) satisfies the entry conditions for said event and initiates the trigger timer first; Record information indicating which event (if any) trigger timer expires first; Record information indicating which event (if any) satisfies the entry conditions for said event, starts the trigger timer, and then first stops said trigger timer; or A fault counter is recorded, which counts the number of faults in the conditional switching of the user equipment caused by the failure of the multiple events to meet the execution conditions for conditional switching of the multiple events.

23. The method of claim 1, further comprising: The user equipment receives a handover command from a network node as part of a conditional handover. The handover command includes a configuration for each of multiple events, including at least a configuration for a first event and a configuration for a second event, as well as a joint evaluation configuration. The joint evaluation configuration is configured by the user equipment to jointly evaluate the multiple events to determine whether to perform a conditional handover.

24. The method according to any one of claims 1 to 23, further comprising: The user equipment jointly evaluates the multiple events to determine whether to perform a conditional handover from the source network node to the target network node.

25. An apparatus for communication, comprising components for carrying out the method of any one of claims 1 to 24.

26. A non-transient computer-readable storage medium comprising instructions stored thereon, the instructions being configured, when executed by at least one processor, to cause a computing system to perform the method according to any one of claims 1 to 24.

27. A communication apparatus, comprising: At least one processor; as well as At least one memory, including computer program code; The at least one memory and the computer program code are configured, together with the at least one processor, to cause the apparatus to perform at least the method of any one of claims 1 to 24.

Images