Method and apparatus for mobile robustness optimization (MRO) mechanism of network energy saving (NES)

Abstract

Various aspects of this disclosure relate to methods and apparatus for a mobile robustness optimization (MRO) mechanism for Network Energy Saving (NES). According to embodiments of this disclosure, a User Equipment (UE) includes: at least one memory; and at least one processor coupled to the at least one memory and configured to enable the UE to: obtain a configuration for storing or reporting information related to successful handover in the application of a Network Energy Saving (NES) solution; and store the information.

Description

Technical Field

[0001] This disclosure relates to wireless communications, and more specifically, to methods and apparatus for network power saving (NES) mobile robustness optimization (MRO) mechanisms. Background Technology

[0002] A wireless communication system may include one or more network communication devices, such as base stations, which can support wireless communication with one or more user communication devices (which may also be referred to as user equipment (UE) or other suitable terms). The wireless communication system can support wireless communication with one or more user communication devices by utilizing the resources of the wireless communication system (e.g., time-domain resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency-domain resources (e.g., subcarriers, carriers, etc.)). Furthermore, the wireless communication system can support wireless communication across various radio access technologies, including third-generation (3G) radio access technology, fourth-generation (4G) radio access technology, fifth-generation (5G) radio access technology, and other suitable radio access technologies beyond 5G (e.g., sixth-generation (6G)). Summary of the Invention

[0003] The article “a” preceding an element is not a limitation, but should be understood to refer to “at least one” of these elements or “one or more” of these elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. As used herein (included in the claims), the word “or” used in a list of items (e.g., a list of items beginning with phrases such as “at least one of…”, “one or more of…”, or “one or both of…”) indicates an inclusive list, such that (e.g.) a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, as used herein, the phrase “based on” should not be construed as referring to a closed set of conditions. For example, without departing from the scope of this disclosure, an exemplary step described as “based on condition A” may be based on both condition A and condition B. In other words, as used herein, the phrase “based on” should be interpreted in the same manner as the phrase “at least partially based on.” Additionally, as used herein (included in the claims), “group” may include one or more elements.

[0004] Some embodiments of this disclosure provide a user equipment (UE) for wireless communication. The UE includes: at least one memory; and at least one processor coupled to the at least one memory and configured such that the UE: obtains a first configuration for the UE to store or report first information related to a successful handover in the case of an application network power saving (NES) solution; and stores the first information.

[0005] In some implementations of the UE described herein, in order to obtain the first configuration, the processor of the UE is configured to: obtain the first configuration through pre-configuration; or obtain the first configuration from a network node.

[0006] In some implementations of the UE described herein, the first configuration includes second information indicating at least one of the following: a handover execution condition is not met when a lower-layer message is received, wherein the lower-layer message contains an NES mode indication; the handover execution condition is not met during a period of time following the receipt of the lower-layer message; or an NES-specific handover execution event configured for the cell is met, but a normal handover execution event configured for the cell is not met.

[0007] In some implementations of the UE described herein, the first configuration includes one or more thresholds, and the one or more thresholds include at least one of the following: at least one first threshold related to the elapsed time between receiving the lower-layer message and receiving the configuration regarding handover in the case of applying the NES solution; at least one second threshold related to the elapsed time between receiving the lower-layer message and initiating handover execution; at least one third threshold related to the elapsed time between when a first handover execution event configured for the cell is satisfied and when a second handover execution event configured for the cell is satisfied; at least one timer T310 related threshold; at least one timer T312 related threshold; or at least one timer T304 related threshold.

[0008] In some implementations of the UE described herein, the first information is stored based on at least one of the following: satisfaction of at least one trigger condition associated with the second information; satisfaction of at least one trigger condition associated with the one or more thresholds; or successful completion of the switching execution.

[0009] In some implementations of the UE described herein, the satisfaction of the at least one triggering condition associated with the second information includes at least one of the following: the handover execution condition is not satisfied when the lower-layer message is received; the handover execution condition is not satisfied during the time period after the lower-layer message is received; or the NES-specific handover execution event configured for the cell is satisfied, but the normal handover execution event configured for the cell is not satisfied.

[0010] In some implementations of the UE described herein, the satisfaction of the at least one triggering condition associated with the one or more thresholds includes at least one of the following: the duration between receiving the lower-layer message and receiving the configuration regarding the handover is greater than the at least one first threshold; the duration between receiving the lower-layer message and initiating the handover execution is greater than the at least one second threshold; the duration between satisfying the first handover execution event configured for the target cell and satisfying the second handover execution event configured for the target cell is greater than the at least one third threshold; the ratio between the elapsed runtime value of timer T310 and the configured value of timer T310 when the lower-layer message is received is greater than the at least one timer T310 related threshold; the ratio between the elapsed runtime value of timer T312 and the configured value of timer T312 when the lower-layer message is received is greater than the at least one timer T312 related threshold; or the ratio between the elapsed runtime value of timer T304 and the configured value of timer T304 is greater than the at least one timer T304 related threshold.

[0011] In some implementations of the UE described herein, the first information includes at least one of the following: information indicating that no handover execution condition was met when the lower-layer message was received or during a period after the lower-layer message was received, wherein the lower-layer message includes an NES mode indication; information indicating that at least one handover execution condition was met when the lower-layer message was received or during the period after the lower-layer message was received; third information indicating whether an NES-specific handover execution event was met before the lower-layer message was received or whether the handover execution condition was met before the lower-layer message was received; and fourth information indicating whether a normal handover execution event was met before the lower-layer message was received; when the lower-layer message was received, the source small The measurement results of the area; the measurement results of the target cell when the lower-layer message is received; the measurement results of one or more candidate cells when the lower-layer message is received; the measurement results of one or more neighboring cells when the lower-layer message is received; the reason value for storing or reporting the first information; the time elapsed between receiving the lower-layer message and receiving the handover configuration; the time elapsed between receiving the lower-layer message and initiating handover execution; the handover execution event configured for the target cell that is first satisfied; the handover execution event configured for the target cell that is second satisfied; or the time elapsed between satisfying the first handover execution event configured for the target cell and satisfying the second handover execution event configured for the target cell.

[0012] In some implementations of the UE described herein, the first information further includes at least one of the following: the NES-specific handover execution event being satisfied before the lower-layer message is received; the handover execution condition being satisfied before the lower-layer message is received; information about a first cell, wherein the NES-specific handover execution event or the handover execution condition is satisfied before the lower-layer message is received; a first-satisfied handover execution event of the first cell; a second-satisfied handover execution event of the first cell; or the time elapsed between when a first handover execution event of the first cell is satisfied and when a second handover execution event of the first cell is satisfied.

[0013] In some implementations of the UE described herein, the cause value indicates at least one of the following: the duration between receiving the lower-layer message and initiating the handover execution is greater than a threshold; the duration between receiving the lower-layer message and receiving the configuration regarding the handover is greater than a threshold; no handover execution condition is met when the lower-layer message is received or during a period after the lower-layer message is received; no handover execution condition is met during a period after the lower-layer message is received; an NES-specific handover execution event configured for the cell is met, but a normal handover execution event configured for the cell is not met; the duration between when the first handover execution event of the cell is met and when the second handover execution event of the cell is met is greater than a threshold; the ratio between the elapsed runtime value of timer T310 and the configured value of timer T310 when the lower-layer message is received is greater than a threshold; the ratio between the elapsed runtime value of timer T312 and the configured value of timer T312 when the lower-layer message is received is greater than a threshold; or the ratio between the elapsed runtime value of timer T304 and the configured value of timer T304 is greater than a threshold.

[0014] In some implementations of the UE described herein, the processor is configured to cause the UE to transmit optional UE capability information for supporting the storage and reporting of the first information.

[0015] In some implementations of the UE described herein, the first information is stored as a Successful Handover Report (SHR) or reported via the SHR.

[0016] In some implementations of the UE described herein, the processor is configured to cause the UE to report the first information after storing the first information.

[0017] Some embodiments of this disclosure provide a processor for wireless communication, comprising: at least one controller coupled to at least one memory and configured such that the processor: obtains a first configuration for the UE to store or report first information related to a successful handover in the case of an application network power saving (NES) solution; and stores the first information.

[0018] Some embodiments of this disclosure provide a method performed by a user equipment (UE) for wireless communication. The method includes: obtaining a first configuration for the UE to store or report first information related to a successful handover in the event of an application network energy saving (NES) solution; and storing the first information.

[0019] Some embodiments of this disclosure provide a network equipment (NE) for wireless communication. The NE includes: at least one memory; and at least one processor coupled to the at least one memory and configured to enable the NE to receive first information from a user equipment (UE) related to a successful handover in the case of an application network energy saving (NES) solution.

[0020] In some embodiments of the NE described herein, the processor of the NE is configured to transmit a first configuration to the UE for the UE to store or report the first information.

[0021] In some implementations of the NE described herein, the first configuration includes second information indicating at least one of the following: a handover execution condition is not met when a lower-layer message is received, wherein the lower-layer message contains an NES mode indication; the handover execution condition is not met during a period of time following the receipt of the lower-layer message; or an NES-specific handover execution event configured for the cell is met, but a normal handover execution event configured for the cell is not met.

[0022] In some implementations of the NE described herein, the first configuration includes one or more thresholds, and the one or more thresholds include at least one of the following: at least one first threshold related to the elapsed time between receiving the lower-layer message and receiving the configuration regarding handover in the case of applying the NES solution; at least one second threshold related to the elapsed time between receiving the lower-layer message and initiating handover execution; at least one third threshold related to the elapsed time between when a first handover execution event configured for the cell is satisfied and when a second handover execution event configured for the cell is satisfied; at least one threshold related to timer T310; at least one threshold related to timer T312; or at least one threshold related to timer T304.

[0023] In some implementations of the NE described herein, the first information includes at least one of the following: information indicating that no handover execution condition was met when the lower-layer message was received or during a period after the lower-layer message was received, wherein the lower-layer message includes an NES mode indication; information indicating that at least one handover execution condition was met when the lower-layer message was received or during the period after the lower-layer message was received; third information indicating whether an NES-specific handover execution event was met before the lower-layer message was received or whether the handover execution condition was met before the lower-layer message was received; and fourth information indicating whether a normal handover execution event was met before the lower-layer message was received; when the lower-layer message was received, the source small The measurement results of the area; the measurement results of the target cell when the lower-layer message is received; the measurement results of one or more candidate cells when the lower-layer message is received; the measurement results of one or more neighboring cells when the lower-layer message is received; the reason value for storing or reporting the first information; the time elapsed between receiving the lower-layer message and receiving the handover configuration; the time elapsed between receiving the lower-layer message and initiating handover execution; the handover execution event configured for the target cell that is first satisfied; the handover execution event configured for the target cell that is second satisfied; or the time elapsed between satisfying the first handover execution event configured for the target cell and satisfying the second handover execution event configured for the target cell.

[0024] In some implementations of the NE described herein, the first information further includes at least one of the following: the NES-specific handover execution event being satisfied before the lower-layer message is received; the handover execution condition being satisfied before the lower-layer message is received; information about a first cell, wherein the NES-specific handover execution event or the handover execution condition is satisfied before the lower-layer message is received; a first-satisfied handover execution event of the first cell; a second-satisfied handover execution event of the first cell; or the time elapsed between when a first handover execution event of the first cell is satisfied and when a second handover execution event of the first cell is satisfied.

[0025] In some implementations of the NE described herein, the cause value indicates at least one of the following: the duration between receiving the lower-layer message and initiating the handover execution is greater than a threshold; the duration between receiving the lower-layer message and receiving the configuration regarding the handover is greater than a threshold; no handover execution condition is met when the lower-layer message is received or during a period after receiving the lower-layer message; no handover execution condition is met during a period after receiving the lower-layer message; an NES-specific handover execution event configured for the cell is met, but a normal handover execution event configured for the cell is not met; the duration between when the first handover execution event of the cell is met and when the second handover execution event of the cell is met is greater than a threshold; the ratio between the elapsed runtime value of timer T310 and the configured value of timer T310 when the lower-layer message is received is greater than a threshold; the ratio between the elapsed runtime value of timer T312 and the configured value of timer T312 when the lower-layer message is received is greater than a threshold; or the ratio between the elapsed runtime value of timer T304 and the configured value of timer T304 is greater than a threshold.

[0026] In some embodiments of the NE described herein, the processor of the NE is configured to receive optional UE capability information from the UE for supporting the storage and reporting of the first information.

[0027] In some implementations of the NE described herein, the first information is received via a Successful Switching Report (SHR).

[0028] Some embodiments of this disclosure provide a processor for wireless communication, comprising: at least one controller coupled to at least one memory and configured such that the processor: receives from user equipment (UE) first information relating to a successful handover in the case of an application network energy saving (NES) solution.

[0029] Some embodiments of this disclosure provide a method performed by a network equipment (NE) for wireless communication. The method includes receiving first information from a user equipment (UE) related to a successful handover in the context of an applied network energy saving (NES) solution.

[0030] Some embodiments of this disclosure provide a user equipment (UE) for wireless communication. The UE includes: at least one memory; and at least one processor coupled to the at least one memory and configured such that the UE: in response to a connection failure, stores information related to the connection failure in a handover procedure under an application network power saving (NES) solution.

[0031] In some implementations of the UE described herein, the information related to the connection failure includes at least one of the following: information indicating that the handover execution condition was not met when the lower-layer message was received or during a period after the lower-layer message was received, wherein the lower-layer message includes an NES mode indication; information indicating that at least one handover execution condition was met when the lower-layer message was received or during the period after the lower-layer message was received; information indicating whether an NES-specific handover execution event was met before the lower-layer message was received or whether the handover execution condition was met before the lower-layer message was received; information indicating whether a normal handover execution event was met before the lower-layer message was received. The measurement results of the source cell when the lower-layer message is received; the measurement results of the target cell when the lower-layer message is received; the measurement results of one or more candidate cells when the lower-layer message is received; the measurement results of one or more neighboring cells when the lower-layer message is received; the time elapsed between receiving the lower-layer message and receiving the handover configuration; the time elapsed between receiving the lower-layer message and initiating handover execution; the handover execution event configured for the target cell that is first satisfied; the handover execution event configured for the target cell that is second satisfied; or the time elapsed between satisfying the first handover execution event configured for the target cell and satisfying the second handover execution event configured for the target cell.

[0032] In some implementations of the UE described herein, the information related to the connection failure further includes at least one of the following: the NES-specific handover execution event being satisfied before the lower-layer message is received; the handover execution condition being satisfied before the lower-layer message is received; cell information, wherein the NES-specific handover execution event or the handover execution condition is satisfied before the lower-layer message is received; a first-satisfied handover execution event of the cell; a second-satisfied handover execution event of the cell; or the time elapsed between when the first handover execution event of the cell is satisfied and when the second handover execution event of the cell is satisfied.

[0033] In some implementations of the UE described herein, the information related to the connection failure is stored as a Radio Link Failure (RLF) report or reported via the RLF report.

[0034] In some implementations of the UE described herein, the processor is configured to cause the UE to report the information related to the connection failure after storing the information related to the connection failure.

[0035] Some embodiments of this disclosure provide a processor for wireless communication, comprising: at least one controller coupled to at least one memory and configured such that the processor: in response to a connection failure, stores information related to the connection failure in a handover procedure for an application network energy saving (NES) solution.

[0036] Some embodiments of this disclosure provide a method performed by a user equipment (UE) for wireless communication. The method includes: in response to a connection failure, storing information related to the connection failure in a handover procedure under an application network power saving (NES) solution.

[0037] Some embodiments of this disclosure provide a user equipment (UE) for wireless communication. The UE includes: at least one memory; and at least one processor coupled to the at least one memory and configured to enable the UE to: store or report mobility history information regarding activation or deactivation in the case of an applied Network Energy Saving (NES) solution.

[0038] In some implementations of the UE described herein, the mobility history information includes at least one of the following: first information associated with cell discontinuous transmission (DTX) activation of at least one cell; second information associated with cell DTX deactivation of at least one cell; third information associated with cell discontinuous reception (DRX) activation of at least one cell; or fourth information associated with cell DRX deactivation of at least one cell.

[0039] In some embodiments of the UE described herein, the first information includes at least one of the following: the cell identifier of the at least one cell; the time when the cell DTX of the at least one cell was activated; the duration for which the cell DTX of the at least one cell was activated; or a percentage of the duration for which the cell DTX of the at least one cell was activated.

[0040] In some embodiments of the UE described herein, the second information includes at least one of the following: the cell identifier of the at least one cell; the time when the cell DTX of the at least one cell was deactivated; the duration of the cell DTX of the at least one cell being deactivated; or the percentage of the duration of the cell DTX of the at least one cell being deactivated.

[0041] In some implementations of the UE described herein, the third information includes at least one of the following: the cell identifier of the at least one cell; the time when the cell DRX of the at least one cell was activated; the duration for which the cell DRX of the at least one cell was activated; or a percentage of the duration for which the cell DRX of the at least one cell was activated.

[0042] In some implementations of the UE described herein, the fourth information includes at least one of the following: the cell identifier of the at least one cell; the time when the cell DRX of the at least one cell was deactivated; the duration of the cell DRX deactivated in the at least one cell; or a percentage of the duration of the cell DRX deactivated in the at least one cell.

[0043] Some embodiments of this disclosure provide a processor for wireless communication, comprising: at least one controller coupled to at least one memory and configured such that the processor: stores or reports mobility history information regarding activation or deactivation in the context of an applied Network Energy Saving (NES) solution.

[0044] Some embodiments of this disclosure provide a method performed by a user equipment (UE) for wireless communication. The method includes storing or reporting mobility history information regarding activation or deactivation in the context of an applied Network Energy Saving (NES) solution.

[0045] Some embodiments of this disclosure provide a network equipment (NE) for wireless communication. The NE includes: at least one memory; and at least one processor coupled to the at least one memory and configured such that the NE stores user equipment (UE) history information regarding the activation or deactivation of an applied network energy saving (NES) solution.

[0046] In some implementations of the NE described herein, the UE historical information includes at least one of the following: first information associated with cell discontinuous transmission (DTX) activation of at least one cell; second information associated with cell DTX deactivation of at least one cell; third information associated with cell discontinuous reception (DRX) activation of at least one cell; or fourth information associated with cell DRX deactivation of at least one cell.

[0047] In some embodiments of the NE described herein, the first information includes at least one of the following: the cell identifier of the at least one cell; the time when the cell DTX of the at least one cell was activated; the duration for which the cell DTX of the at least one cell was activated; or a percentage of the duration for which the cell DTX of the at least one cell was activated.

[0048] In some embodiments of the NE described herein, the second information includes at least one of the following: the cell identifier of the at least one cell; the time when the cell DTX of the at least one cell was deactivated; the duration of the cell DTX of the at least one cell being deactivated; or a percentage of the duration of the cell DTX of the at least one cell being deactivated.

[0049] In some implementations of the NE described herein, the third information includes at least one of the following: the cell identifier of the at least one cell; the time when the cell DRX of the at least one cell was activated; the duration for which the cell DRX of the at least one cell was activated; or a percentage of the duration for which the cell DRX of the at least one cell was activated.

[0050] In some embodiments of the NE described herein, the fourth information includes at least one of the following: the cell identifier of the at least one cell; the time when the cell DRX of the at least one cell was deactivated; the duration of the cell DRX deactivated in the at least one cell; or a percentage of the duration of the cell DRX deactivated in the at least one cell.

[0051] Some embodiments of this disclosure provide a processor for wireless communication, comprising: at least one controller coupled to at least one memory and configured such that the processor: stores user equipment (UE) history information regarding activation or deactivation in the context of an applied Network Energy Saving (NES) solution.

[0052] Some embodiments of this disclosure provide a method performed by a network equipment (NE) for wireless communication. The method includes storing user equipment (UE) history information regarding the activation or deactivation of an applied network energy saving (NES) solution. Attached Figure Description

[0053] Figure 1 Examples of wireless communication systems according to aspects of this disclosure are described.

[0054] Figure 2 An example of a user equipment (UE) 200 according to aspects of this disclosure is described.

[0055] Figure 3 An example of processor 300 according to aspects of this disclosure is described.

[0056] Figure 4 An example of a network equipment (NE) 400 according to aspects of this disclosure is described.

[0057] Figure 5 A flowchart illustrating a method related to a Network Energy Saving (NES) solution according to aspects of this disclosure. Detailed Implementation

[0058] The detailed description of the accompanying drawings is intended to illustrate preferred embodiments of the present disclosure and is not intended to represent the only form in which the present disclosure is practiced. It should be understood that the same or equivalent functionality may be accomplished through different embodiments that are intended to be covered within the spirit and scope of the present disclosure.

[0059] Reference will now be made to some embodiments of this disclosure, examples of which are illustrated in the accompanying drawings. To facilitate understanding, embodiments are provided under specific network architectures and new service scenarios (e.g., 3GPP 5G (NR), 3GPP Long Term Evolution (LTE) Release 8, etc.). In careful consideration, all embodiments of this disclosure are applicable to similar technical problems as network architectures and new service scenarios evolve; furthermore, the terminology cited in this disclosure may be changed without affecting the principles of this disclosure.

[0060] Generally, to reduce downlink transmit or uplink receive activity time at base stations (BS) (e.g., gNBs), UEs can be configured with periodic cell discontinuous transmit (DTX) or discontinuous receive (DRX) modes (i.e., active and inactive periods). Applying cell DTX or cell DRX mechanisms is a NES solution. Cell DTX or DRX mode configurations are common for UEs with this feature configured in a cell. Cell DTX and cell DRX modes can be configured and activated individually. For different serving cells, each Media Access Control (MAC) entity can configure up to two cell DTX or DRX modes. When cell DTX is configured and activated in a relevant cell, the UE may, under selected conditions, not monitor the Physical Downlink Control Channel (PDCCH) or not monitor semi-persistent scheduling (SPS) timings during the cell DTX inactive period. When cell DRX is configured and activated in a relevant cell, the UE does not transmit on Configuration Grant (CG) resources or transmit scheduling requests (SRs) during the cell DRX inactive period. This feature applies only to UEs in the RRC_CONNECTED state and does not affect random access (RA) procedures, synchronization signal block (SSB) transmission, paging, or system information broadcasting. Cell DRX or DRX can be activated or deactivated by RRC signaling or Layer 1 (L1) group common signaling. The characteristics of cell DTX or DRX are as follows:

[0061] - Activity Duration: The duration during which the UE waits to receive the PDCCH or SPS and transmits the SR or CG. During this duration, for network energy saving purposes, the transmission or reception of BS reports such as PDCCH, SPS, SR, CG, periodic and semi-persistent CSI are not affected.

[0062] - Loop: Specifies the periodic repetition of the activity duration followed by the inactive duration.

[0063] The activity duration and cycle parameters are shared between the cell DTX and the cell DRX when both are configured.

[0064] Once the BS identifies an emergency call or public safety-related service (such as Multimedia Priority Service (MPS) or Mission Critical Service (MCS)), the network should ensure that there is no impact on this service (e.g., it can release or deactivate the cell DTX or DRX configuration). The network should also ensure that there is at least partial overlap between the duration of the UE's connected mode DRX activation and the duration of cell DTX or DRX activity; that is, the UE's connected mode DRX periodicity is a multiple of the cell DTX or DRX periodicity, and vice versa.

[0065] As described in TS 38.331, a UE configured to operate on the serving cell according to one or both of the cell DTX operation of cellDTXConfig and cell DRX operation of cellDRXConfig of the serving cell may additionally provide a search space set by dci-Format2-9 to monitor the PDCCH to detect DCI format2_9 according to the common search space and to detect the position of DCI format2_9 by the position-inDCI-NES of the cell DTX / DRX indicator field of the serving cell.

[0066] If the UE is configured with both cell DTX and cell DRX operations of the serving cell, then the cell DTX / DRX indicator field contains two bits, where the first bit indicates the cell DTX operation and the second bit indicates the cell DRX operation.

[0067] If the UE is configured with only one of the cell DTX operation and cell DRX operation of the serving cell, then the cell DTX / DRX indicator field contains one bit indicating the corresponding cell DTX operation and cell DRX operation of the serving cell.

[0068] A '0' value in the cell DTX / DRX indicator field indicates deactivation of the cell DTX or cell DRX.

[0069] The '1' value of the bit in the cell DTX / DRX indicator field indicates the activation of cell DTX or cell DRX.

[0070] If the serving cell is configured with a SUL carrier, then the cell DTX / DRX indicator field for cell DRX activation or deactivation applies to both UL carriers and SUL carriers.

[0071] The UE does not expect to monitor the PDCCH on more than one serving cell to detect DCI format 2_9.

[0072] Conditional handover (CHO) is defined as a handover performed by the UE when one or more handover execution conditions are met. The UE begins evaluating the execution conditions after receiving the CHO configuration and stops evaluating the execution conditions after the handover is performed. The following principles apply to CHO:

[0073] - The CHO configuration contains the configuration of CHO candidate cells generated by the candidate BS (e.g., candidate gNB) and the execution conditions generated by the source BS (e.g., source gNB).

[0074] - Execution conditions can consist of one or two trigger conditions, or the execution conditions of a CHO candidate cell or target cell can consist of one or two execution events (e.g., CHO events A3 / A5, as defined in 3GPP standard document TS38.331). Only a single reference signal (RS) type is supported, and a maximum of two different trigger quantities (e.g., RSRP and RSRQ, RSRP and SINR, etc.) can be configured simultaneously for the evaluation of CHO execution conditions of a single candidate cell.

[0075] - Before any CHO execution conditions are met, after receiving an HO command (without CHO configuration), the UE executes the HO procedure as described in Clause 9.2.3.2 of TS38.300, regardless of any previously received CHO configuration.

[0076] - When a CHO is executed, that is, from the time when the UE begins to synchronize with the target cell, the UE does not monitor the source cell.

[0077] Regarding NES specific CHO (Or, in the case of a CHO using an NES solution or a CHO for NES in the case of a source cell using an NES solution (e.g., a cell can activate or deactivate cell DTX / DRX, or a cell can deactivate or enable cell DTX / DRX), when the source cell is using a network power saving solution (e.g., a cell can activate or deactivate cell DTX or DRX, or a cell can deactivate or enable cell DTX / DRX), the following additional triggering conditions are supported, after which the UE can use at least one NES-specific CHO execution event to execute a CHO to a candidate cell: The UE can be notified via DCI to enable a CHO execution condition configured with an NES event indication. The DCI is DCI format 2_9. If nesEvent is configured, then the NES mode indication field in DCI format 2_9 contains 1 bit indicating the NES-specific CHO execution condition (e.g., NES mode indication). For example: a '0' value in the NES mode indication field indicates that the NES-specific CHO execution condition is disabled; a '1' value in the NES mode indication field indicates that the NES-specific CHO execution condition is enabled.

[0078] The NES CHO procedure (or CHO in the case of applying the NES solution or CHO in the case where the source cell can use the NES solution (e.g., the cell can activate or deactivate cell DTX / DRX, or the cell can deactivate or enable DTX / DRX) or CHO for NES) is based on the source cell entering "NES mode or cell off mode". For NES CHO, when the source cell starts a certain "NES mode", the UE has performed CHO condition evaluation as a baseline. After receiving the CHO configuration, the UE starts CHO evaluation, and CHO events A3 / A4 / A5 or condEventA3 / A4 / A5 can be configured as handover / CHO trigger conditions or handover / CHO execution events in the NES scenario.

[0079] If a condReconfigId (or a CHO candidate cell or a CHO target cell) is configured with one traditional or normal CHO execution event and one NES-specific CHO execution event, then the UE triggers a handover / CHO execution if either of the two events is satisfied / fulfilled after receiving Layer 1 (L1) signaling (i.e., DCI format 2_9 containing one bit indicating whether NES-specific CHO execution conditions are enabled or disabled (e.g., NES mode indication)). If a condReconfigId (or a CHO candidate cell or a CHO target cell) is configured with two traditional or normal CHO execution events, then the UE triggers a handover / CHO execution if both events are satisfied after receiving L1 signaling. If a condReconfigId (or a CHO candidate cell or a CHO target cell) is configured with two NES-specific CHO execution events, then the UE triggers a handover / CHO execution if either of the two events is satisfied after receiving L1 signaling.

[0080] If, before receiving L1 signaling, both traditional or normal CHO execution events are met for a CHO candidate cell configured with two such events, then the UE performs a handover / CHO execution. If, before receiving L1 signaling, the NES-specific CHO execution event is met for a CHO candidate cell configured with both traditional or normal CHO execution events and NES-specific CHO execution events (regardless of whether traditional or normal CHO execution events are met), then the UE will not perform a handover / CHO execution to the CHO candidate cell. If, before receiving L1 signaling, at least one of the two NES-specific CHO execution events is met for a CHO candidate cell configured with two such events, then the UE will not perform a handover / CHO execution to the CHO candidate cell.

[0081] The basic procedure for an NES-specific CHO (or a CHO in the case of applying an NES solution or a CHO in the case where the source cell can use an NES solution (e.g., the cell can activate or deactivate cell DTX / DRX, or the cell can deactivate or enable cell DTX / DRX) or a CHO for NES) is as follows: The source node sends a CHO configuration to the UE (e.g., containing the CondEvent A3 / A4 / A5 execution conditions and RRC reconfiguration for each CHO (candidate) target cell), and the UE initiates a CHO execution condition evaluation after receiving the CHO configuration. If the source cell decides to enter NES mode or the cell is in a closed state, the source node can send an L1 signaling to the UE to trigger the CHO (e.g., the L1 signaling can be in DCI format 2_9, which contains one bit for enabling or disabling at least one NES-specific CHO execution condition; for example, a '0' value in the NES mode indication field indicates that the NES-specific CHO execution condition is disabled; and a '1' value in the NES mode indication field indicates that the NES-specific CHO execution condition is enabled). When the UE receives an L1 signaling or indication that the source cell has entered at least one NES mode or cell off state to enable or disable at least one NES-specific CHO execution condition and meets a measurement-based event (e.g., CondEvent A3 / A4 / A5 execution condition), it will perform a handover / CHO execution toward the target cell.

[0082] Regarding RLF reporting, one of the functions of MRO is to detect connection failures caused by premature or late handovers or handovers to the wrong cell. These issues are defined as follows:

[0083] - Intra-system delayed handover: RLF occurs after the UE has remained in the cell for an extended period of time; the UE attempts to rebuild the radio link connection in a different cell.

[0084] - Premature handover within the system: RLF occurs shortly after a successful handover from the source cell to the target cell or the handover fails during the handover procedure; the UE attempts to rebuild the radio link connection in the source cell.

[0085] - Intra-system handover to the wrong cell: RLF occurs shortly after a successful handover from the source cell to the target cell or during the handover procedure if the handover fails; the UE attempts to rebuild the radio link connection in a cell other than the source cell and the target cell.

[0086] In the above definition, "successful handover" refers to the UE state, that is, the successful completion of the RA procedure.

[0087] In the case of CHO, the overly late handover, overly early handover, and handover to the wrong cell in the above definition mean that the CHO is executed too late, the CHO is executed too early, and the CHO is executed to the wrong cell.

[0088] Regarding the detection mechanism, failure indication can be initiated after the UE attempts to re-establish the radio link connection at NG-RAN Node B following a failure at NG-RAN Node A. If multiple NG-RAN Nodes control cells using the PCI signaled by the UE during the re-establishment procedure, then NG-RAN Node B can initiate a failure indication procedure to multiple NG-RAN Nodes. Upon receiving this, the NG-RAN Node selects a UE context that matches the received failed cell ID and C-RNTI, and if available, confirms this identification by calculating the shortMAC-I and comparing it with the received IE.

[0089] When an NG-RAN node retrieves an RLF report from a UE by triggering the following, a failure indication can also be sent to the node that last served the UE:

[0090] - Failure indicator on Xn.

[0091] - Uplink RAN ​​configuration transfer procedure and downlink RAN ​​configuration transfer procedure on NG.

[0092] In the event of premature handover or handover to the wrong cell, the NG-RAN node receiving the failure indication may notify the NG-RAN node control of the cell where mobility configuration caused the failure via the handover reporting procedure on Xn or the uplink RAN ​​configuration transmission procedure on NG. This may include an RLF report.

[0093] Following an RLF or handover failure, the UE will perform a rebuild within the cell. The UE will store some information related to the RLF failure and / or handover failure information. The UE stores the latest RLF report (containing the RLF report) until the RLF report is retrieved by the network or within 48 hours after the connection failure is detected. To analyze the connection failure, the UE makes the RLF report available to the network. The availability of the RLF report can be indicated by RRCSetupComplete, RRCResumeComplete, or RRCRe-establishmentComplete. For example, if the UE has failure-related information available for use in the VarRLF-Report, it can include rlf-InfoAvailable in the RRCSetupComplete, RRCResumeComplete, or RRCRe-establishmentComplete message. The network can retrieve the information from the RLF report via the UE information request / response mechanism; that is, the gNB can send a UE information request to the UE. The UE will then send a UE information response containing the RLF report to the network. The network can optimize mobility issues based on the response from the UE.

[0094] Regarding Successful Handover Reports (SHR), one of the functions of MRO is to detect suboptimal successful handover events. The aim is to identify potential conditions during successful normal handovers, successful DAPS handovers, or successful conditional handovers.

[0095] To analyze successful handover, the UE can collect SHR based on network configuration (if stored) and make the SHR available to the network, as specified in TS 38.331.

[0096] For an SHR collected during intra-NR handover, if the target NR node extracts the SHR from the UE and the trigger of the SHR is a timer T310 or T312, it can forward the information to the source NR node, i.e., the node that handles the cell reported as the source cell in this SHR, by using the "Access and Mobility Indication" message on Xn or by relying on the uplink RAN ​​configuration delivery procedure and downlink RAN ​​configuration delivery procedure on NG.

[0097] If the NG-RAN node from which the SHR is extracted from the UE is neither the source node nor the destination node for the handover, then it forwards the information to the node configured with the SHR trigger that causes the SHR to be generated by using the "Access and Mobility Indication" message on Xn or by relying on the uplink RAN ​​configuration delivery procedure and the downlink RAN ​​configuration delivery procedure on the NG.

[0098] After retrieving the SHR, the receiving node can analyze whether its mobility configuration needs to be adjusted.

[0099] In some cases, the UE may report UE history information (e.g., MHI) when connecting to a cell of an NG-RAN node. This information consists of PCell mobility history information and optional PSCell mobility history information, as specified in TS 38.331. When information needs to be discarded because the list is full, it is discarded in the order of its position in the list, starting with the oldest cell record. If the list is full and UE history information from the UE is available, then UE history information from the UE should also be discarded.

[0100] In some cases, the NG-RAN node collects and stores UE historical information as long as the UE remains in one of its cells. In the MR-DC case, as long as the UE remains in the MR-DC, the MN stores and associates UE historical information from both the MN and SN, forwarding the UE historical information and optional UE historical information from the UE to its connected SN. The resulting information is then used by the SN for dual connectivity operations. The SN is responsible for collecting SCG UE historical information and providing the collected information to the MN.

[0101] Generally, Network Energy Saving (NES) is a new feature introduced in 3GPP Rel-18. To optimize NES-related configurations and improve mobility robustness, Rel-19 SON / MDT themes or later will support MRO mechanisms for NES. Currently, the details of MRO for NES are not specifically discussed in wireless communication systems and other areas. For example, the following issues need to be addressed: In NES-specific CHO procedures (or CHOs in the case of applying NES solutions or CHOs where the source cell can use NES solutions (e.g., the cell can activate or deactivate cell DTX / DRX, or the cell can deactivate or enable cell DTX / DRX) or CHOs for NES), near-failure successful handovers can occur. How to trigger the storage or reporting of successful reports for NES-specific CHOs (e.g., what are the specific triggering conditions for NES CHOs for SHRs)? In NES-specific CHO procedures, near-failure successful handovers or failures can occur, and what NES CHO-specific information is stored or reported by the UE? And what are the enhancements to UE History Information (UHI) or Mobility History Information (MHI) due to NES mechanisms or solutions?

[0102] The embodiments of this disclosure are intended to address the aforementioned problems. For example, some embodiments of this disclosure provide a method for triggering a successful NES report. For example, in some embodiments of this disclosure, NES-specific triggering conditions are configured to the UE to record, store, or generate a successful NESCHO report, which may include at least one of the following triggering conditions:

[0103] (1) A threshold related to the duration between receiving Layer 1 (L1) signaling and when CHO execution is initiated or triggered (e.g., when at least one of a normal CHO execution event configured for a candidate cell and an NES-specific CHO execution event is satisfied, or when at least one of two normal CHO execution events configured for a candidate cell or two NES-specific CHO execution events configured for a candidate cell is satisfied);

[0104] (2) Indicates the condition that the CHO execution condition is not met when the L1 signaling is received;

[0105] (3) Indicates the conditions that are not met during a predefined period after receiving the L1 signaling;

[0106] (4) Indicates that when configuring NES-specific CHO execution events and normal CHO events for a cell (e.g., target cell), the conditions for the cell's NES-specific CHO execution events are met but the conditions for the cell's normal CHO execution events are not met;

[0107] (5) A threshold related to the duration between when a normal CHO execution event configured for a cell (e.g., the target cell) is satisfied and when a NES-specific CHO execution event configured for a cell is satisfied;

[0108] (6) A threshold related to the duration between the receipt of L1 signaling and the receipt of CHO configuration;

[0109] (7) A threshold for the percentage ratio between the elapsed running time of timer T310 and the configured value of timer T310 when L1 signaling is received;

[0110] (8) A threshold value representing the percentage ratio between the elapsed runtime of timer T312 and the configured value of timer T312 when L1 signaling is received; or

[0111] (9) Threshold for the percentage ratio between the elapsed running time of timer T304 and the configured value of timer T304.

[0112] Some embodiments of this disclosure provide a method for enhancing NES success or failure reporting. For example, in some embodiments of this disclosure, NES-specific information may be stored or reported by the UE, including at least one of the following: an indication indicating whether a candidate cell meets CHO execution conditions when L1 signaling is received or during a predefined finite period after receiving L1 signaling; an indication indicating whether CHO execution conditions or NES-specific CHO execution events are met before receiving L1 signaling; a measurement result when L1 signaling is received; the time elapsed between receiving L1 signaling and when CHO execution is initiated or triggered; the first event met (e.g., a conventional or normal CHO execution event or an NES-specific CHO execution event); the second event met (e.g., a conventional or normal CHO execution event or an NES-specific CHO execution event); the duration between when a conventional or normal CHO execution event configured for a cell (e.g., a target cell or a CHO candidate cell) is met and when an NES-specific CHO execution event configured for a cell (e.g., a target cell or a CHO candidate cell) is met.

[0113] Some embodiments of this disclosure provide a method for enhancing the UHI or MHI of a NES. For example, in some embodiments of this disclosure, the UE may store or report information on cell DTX activation or deactivation and / or cell DRX activation or deactivation in the MHI. In some embodiments of this disclosure, the UHI stored or collected by the network may contain information on cell DTX activation or deactivation and / or cell DRX activation or deactivation.

[0114] Further details of embodiments of this disclosure will be described below in conjunction with the accompanying drawings.

[0115] Figure 1This describes an example of a wireless communication system 100 according to aspects of this disclosure. The wireless communication system 100 may include one or more NEs 102, one or more UEs 104, and a core network (CN) 106. The wireless communication system 100 may support various radio access technologies. In some embodiments, the wireless communication system 100 may be a 4G network, such as an LTE network or an LTE-A network. In some other embodiments, the wireless communication system 100 may be an NR network, such as a 5G network, a 5G-A network, or a 5G Ultra Wideband (5G-UWB) network. In other embodiments, the wireless communication system 100 may be a combination of 4G and 5G networks or other suitable radio access technologies, including IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20. The wireless communication system 100 may support radio access technologies beyond 5G, such as 6G. In addition, the wireless communication system 100 can support technologies such as Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), or Code Division Multiple Access (CDMA).

[0116] One or more NEs 102 may be distributed throughout a geographic area to form a wireless communication system 100. One or more of the NEs 102 described herein may be, include, or be referred to as a network node, base station, network element, network function, network entity, wireless access network (RAN), NodeB, eNodeB (eNB), next-generation NodeB (gNB), or other suitable terms. NEs 102 and UEs 104 may communicate via a communication link, which may be wireless or wired. For example, NEs 102 and UEs 104 may perform wireless communication (e.g., receiving signaling, transmitting signaling) via a Uu interface.

[0117] NE 102 can provide a geographic coverage area, wherein NE 102 can support services for one or more UE 104s within the geographic coverage area. For example, NE 102 and UE 104 can support wireless communication of signals associated with services (e.g., voice, video, packet data, messaging, broadcasting, etc.) using one or more radio access technologies. In some embodiments, NE 102 can be mobile, such as a satellite associated with a non-terrestrial network (NTN). In some embodiments, different geographic coverage areas associated with the same or different radio access technologies can overlap, but different geographic coverage areas can be associated with different NE 102s.

[0118] One or more UEs 104 may be distributed throughout the geographic area of ​​the wireless communication system 100. UE 104 may include or be referred to as a remote unit, mobile device, wireless device, remote device, subscriber device, transmitter device, receiver device, or some other suitable term. In some embodiments, UE 104 may be referred to as a unit, station, terminal, or client, and other instances thereof. Alternatively or additionally, UE 104 may be referred to as an Internet of Things (IoT) device, Internet of Everything (IoE) device, or Machine-Type Communication (MTC) device, and other instances thereof.

[0119] UE 104 can support direct wireless communication with other UE 104 via a communication link. For example, UE 104 can support direct wireless communication with another UE 104 via a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular-V2X deployments, the communication link 114 may be referred to as a sidelink. For example, UE 104 can support direct wireless communication with another UE 104 via a PC5 interface.

[0120] NE 102 may support communication with CN 106 or another NE 102, or both. For example, NE 102 may interface with other NE 102 or CN 106 via one or more backhaul links (e.g., S1, N2, or network interfaces). In some implementations, NE 102 may communicate directly with each other. In other implementations, NE 102 may communicate with each other or indirectly (e.g., via CN 106). In some implementations, one or more NE 102 may include sub-components, such as access network entities, which may be instances of Access Node Controllers (ANCs). The ANC may communicate with one or more UE 104s via one or more other access network transmitting entities, which may be referred to as radio headends, smart radio headends, or transmit-receive points (TRPs).

[0121] CN 106 can support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. CN 106 can be an evolved packet core (EPC) or a 5G core (5GC), which may include control plane entities that manage access and mobility (e.g., Mobility Management Entity (MME), Access and Mobility Management Function (AMF)) and user plane entities that route packets to or interconnect to external networks (e.g., Serving Gateway (S-GW), Packet Data Network (PDN) Gateway (P-GW), or User Plane Function (UPF)). In some implementations, the control plane entities may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signaling bearers, etc.) of one or more UEs 104 served by one or more NEs 102 associated with CN 106.

[0122] CN 106 can communicate with the packet data network (e.g., via S1, N2, or another network interface) through one or more backhaul links. The packet data network may contain an application server. In some implementations, one or more UEs 104 can communicate with the application server. UE 104 can establish a session (e.g., a Protocol Data Unit (PDU) session) with CN 106 via NE 102. CN 106 can use the established session (e.g., an established PDU session) to route services (e.g., control information, data, etc.) between UE 104 and the application server. A PDU session can be an instance of a logical connection between UE 104 and CN 106 (e.g., one or more network functions of CN 106).

[0123] In the wireless communication system 100, NE 102 and UE 104 can use the resources of the wireless communication system 100 (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communication). In some embodiments, NE 102 and UE 104 may support different resource structures. For example, NE 102 and UE 104 may support different frame structures. In some embodiments, such as in 4G, NE 102 and UE 104 may support a single frame structure. In some other embodiments, such as in 5G and other suitable radio access technologies, NE 102 and UE 104 may support various frame structures (i.e., multiple frame structures). NE 102 and UE 104 may support various frame structures based on one or more sets of parameters.

[0124] The wireless communication system 100 may support one or more parameter sets, and the parameter sets may include subcarrier spacing and cyclic prefixes. A first parameter set (e.g., μ=0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a regular cyclic prefix. In some embodiments, the first parameter set (e.g., μ=0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one time slot per subframe. A second parameter set (e.g., μ=1) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a regular cyclic prefix. A third parameter set (e.g., μ=2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a regular cyclic prefix or an extended cyclic prefix. A fourth parameter set (e.g., μ=3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a regular cyclic prefix. A fifth parameter set (e.g., μ=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a regular cyclic prefix.

[0125] Time intervals for resources (such as communication resources) can be organized according to frames (also known as radio frames). Each frame may have a duration, such as 10 milliseconds (ms). In some implementations, each frame may contain multiple subframes. For example, each frame may contain 10 subframes, and each subframe may have a duration, such as 1 ms. In some implementations, each frame may have the same duration. In some implementations, each subframe of a frame may have the same duration.

[0126] Alternatively, the time intervals of resources (e.g., communication resources) can be organized according to time slots. For example, a subframe may contain a certain number (e.g., a certain quantity) of time slots. The number of time slots in each subframe may also depend on one or more parameter sets supported in the wireless communication system 100. For example, the first, second, third, fourth, and fifth parameter sets (i.e., μ=0, μ=1, μ=2, μ=3, μ=4) associated with corresponding subcarrier intervals of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz can respectively utilize one time slot per subframe, two time slots per subframe, four time slots per subframe, eight time slots per subframe, and 16 time slots per subframe. Each time slot may contain a certain number (e.g., a certain quantity) of symbols (e.g., OFDM symbols). In some embodiments, the number (e.g., quantity) of time slots in a subframe may depend on the parameter set. For a conventional cyclic prefix, a time slot may contain 14 symbols. For an extended cyclic prefix (e.g., applicable to a 60 kHz subcarrier spacing), a time slot may contain 12 symbols. The relationship between the number of symbols per time slot, the number of time slots per subframe, and the number of time slots per frame for the regular and extended cyclic prefixes may depend on the parameter set. It should be understood that a reference to the first parameter set (e.g., μ=0) associated with the first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and time slots.

[0127] In the wireless communication system 100, the electromagnetic (EM) spectrum can be divided into various categories, bands, channels, etc., based on frequency or wavelength. For example, the wireless communication system 100 may support one or more operating frequency bands, such as frequency ranges represented as FR1 (410 MHz to 7.125 GHz), FR2 (24.25 GHz to 52.6 GHz), FR3 (7.125 GHz to 24.25 GHz), FR4 (52.6 GHz to 114.25 GHz), FR4a or FR4-1 (52.6 GHz to 71 GHz), and FR5 (114.25 GHz to 300 GHz). In some embodiments, NE 102 and UE 104 may perform wireless communication on one or more of the operating frequency bands. In some embodiments, FR1 may be used by NE 102 and UE 104, as well as other equipment or devices, for cellular communication services (e.g., control information, data). In some implementations, FR2 can be used by NE 102 and UE 104, as well as other equipment or devices, for short-range, high data rate capabilities.

[0128] FR1 can be associated with one or more parameter sets (e.g., at least three parameter sets). For example, FR1 can be associated with: a first parameter set (e.g., μ=0) containing a 15 kHz subcarrier spacing; a second parameter set (e.g., μ=1) containing a 30 kHz subcarrier spacing; and a third parameter set (e.g., μ=2) containing a 60 kHz subcarrier spacing. FR2 can be associated with one or more parameter sets (e.g., at least two parameter sets). For example, FR2 can be associated with: a third parameter set (e.g., μ=2) containing a 60 kHz subcarrier spacing; and a fourth parameter set (e.g., μ=3) containing a 120 kHz subcarrier spacing.

[0129] Figure 2 An example of a UE 200 according to aspects of this disclosure is described. UE 200 may include a processor 202, a memory 204, a controller 206, and a transceiver 208. The processor 202, memory 204, controller 206, or transceiver 208, or various combinations thereof, or various components thereof, may be examples of components for performing the aspects of this disclosure described herein. These components may be coupled via one or more interfaces (e.g., operatively, communicatively, functionally, electronically, or electrically).

[0130] Processor 202, memory 204, controller 206, or transceiver 208, or various combinations or components thereof, may be implemented in hardware (e.g., a circuit system). The hardware may include processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), or other programmable logic devices, or any combination thereof, configured to or otherwise support components for performing the functions described in this disclosure.

[0131] Processor 202 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, ASICs, FPGAs, or any combination thereof). In some embodiments, processor 202 may be configured to operate memory 204. In some other embodiments, memory 204 may be integrated into processor 202. Processor 202 may be configured to execute computer-readable instructions stored in memory 204 to cause UE 200 to perform various functions of this disclosure.

[0132] Memory 204 may comprise volatile or non-volatile memory. Memory 204 may store computer-readable, computer-executable code containing instructions that, when executed by processor 202, cause UE 200 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium, this memory 204, or another type of memory. Computer-readable media includes both non-transitory computer storage media and communication media, which includes any media that facilitates the transfer of computer programs from one place to another. Non-transitory storage media may be any available media accessible by a general-purpose or special-purpose computer.

[0133] In some implementations, processor 202 and memory 204 coupled to processor 202 may be configured to cause UE 200 to perform one or more of the functions described herein (e.g., instructions stored in memory 204 are executed by processor 202).

[0134] For example, processor 202 may support, at UE 200, according to the provisions of this document... Figure 5 The publicly disclosed example performs wireless communication. UE 200 can be configured to support: a component for obtaining first configuration related to successful handover in the case of UE storage or reporting in the application network power saving (NES) solution; and a component for storing the first information.

[0135] For example, processor 202 may support wireless communication at UE 200, which may be configured to support: a component for storing information related to connection failure in a handover procedure in the case of an NES solution application, in response to a connection failure.

[0136] For example, processor 202 may support wireless communication at UE 200, which may be configured to support: a component for storing mobility history information regarding activation or deactivation in the case of applying an NES solution.

[0137] Controller 206 manages the input and output signals of UE 200. Controller 206 can also manage peripheral devices not integrated into UE 200. In some embodiments, controller 206 may utilize an operating system, such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some embodiments, controller 206 may be implemented as part of processor 202.

[0138] In some embodiments, UE 200 may include at least one transceiver 208. In other embodiments, UE 200 may have more than one transceiver 208. Transceiver 208 may represent a wireless transceiver. Transceiver 208 may include one or more receiver chains 210, one or more transmitter chains 212, or a combination thereof. The aforementioned components for receiving in processor 202 or for transmitting in processor 202 may be implemented via at least one transceiver 208.

[0139] Receiver chain 210 may be configured to receive signals (e.g., control information, data, packets) via wireless media. For example, receiver chain 210 may include one or more antennas for receiving signals via air or wireless media. Receiver chain 210 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. Receiver chain 210 may include at least one demodulator configured to demodulate the received signal and obtain transmitted data by reversing the modulation technique applied during signal transmission. Receiver chain 210 may include at least one decoder for decoding the demodulated signal to receive transmitted data.

[0140] Transmitter chain 212 can be configured to generate and transmit signals (e.g., control information, data, packets). Transmitter chain 212 may include at least one modulator for modulating data onto a carrier signal to prepare the signal for transmission over a wireless medium. At least one modulator may be configured to support one or more techniques, such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes like phase shift keying (PSK) or quadrature amplitude modulation (QAM). Transmitter chain 212 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over a wireless medium. Transmitter chain 212 may also include one or more antennas for transmitting the amplified signal into the air or a wireless medium.

[0141] Figure 3An example of a processor 300 according to aspects of this disclosure is described. Processor 300 may be an example of a processor configured to perform various operations according to the examples described herein. Processor 300 may include a controller 302 configured to perform various operations according to the examples described herein. Processor 300 may optionally include at least one memory 304, which may be, for example, an L1 / L2 / L3 cache. Additionally or alternatively, processor 300 may optionally include one or more arithmetic logic units (ALUs) 306. One or more of these components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0142] Processor 300 may be a processor chipset and includes a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receive, acquire, retrieve, transmit, output, forward, store, determine, identify, access, write, read) according to the examples described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to the processor chipset (e.g., processor 300) or included in the processor chipset) or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase-change memory (PCM), and others).

[0143] Controller 302 can be configured to manage and coordinate various operations of processor 300 (e.g., signaling, receiving, acquiring, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, and reading) to enable processor 300 to support various operations according to the examples described herein. For example, controller 302 can operate as a control unit of processor 300, generating control signals that manage the operation of various components of processor 300. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating operation timing.

[0144] Controller 302 may be configured to fetch (e.g., fetch, retrieve, receive) instructions from memory 304 and determine subsequent instructions to be executed to enable processor 300 to support various operations according to the examples described herein. Controller 302 may be configured to track the memory addresses of instructions associated with memory 304. Controller 302 may be configured to decode instructions to determine the operation to be performed and the operands involved. For example, controller 302 may be configured to interpret instructions and determine control signals output to other components of processor 300 to enable processor 300 to support various operations according to the examples described herein. Alternatively or additionally, controller 302 may be configured to manage data flow within processor 300. Controller 302 may be configured to control data transfers between registers, arithmetic logic unit (ALU), and other functional units of processor 300.

[0145] Memory 304 may include one or more caches (e.g., memory local to or included in processor 300) or other memories, such as RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some embodiments, memory 304 may reside within or on the processor chipset (e.g., locally to processor 300). In some other embodiments, memory 304 may reside outside the processor chipset (e.g., remotely from processor 300).

[0146] Memory 304 may store computer-readable, computer-executable code containing instructions that, when executed by processor 300, cause processor 300 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. Controller 302 and / or processor 300 may be configured to execute computer-readable instructions stored in memory 304 to cause processor 300 to perform various functions. For example, processor 300 and / or controller 302 may be coupled to or coupled to memory 304, and processor 300, controller 302, and memory 304 may be configured to perform the various functions described herein. In some instances, processor 300 may include multiple processors and memory 304 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be individually or jointly configured to perform the various functions described herein.

[0147] One or more ALUs 306 may be configured to support various operations according to the examples described herein. In some embodiments, one or more ALUs 306 may reside within or on a processor chipset (e.g., processor 300). In some other embodiments, one or more ALUs 306 may reside outside the processor chipset (e.g., processor 300). One or more ALUs 306 may perform one or more calculations on data, such as addition, subtraction, multiplication, and division. For example, one or more ALUs 306 may receive input operands and opcodes, which determine the operation to be performed. One or more ALUs 306 are configured with various logic and arithmetic circuits (including adders, subtractors, shifters, and logic gates) to process and manipulate data according to the operation. Alternatively, one or more ALU 306s may support logical operations (such as AND, OR, XOR, NOR, and NAND) to enable one or more ALU 306s to handle conditional operations, comparisons, and bitwise operations.

[0148] Processor 300 can support wireless communication according to the examples disclosed herein.

[0149] In some implementations, processor 300 may be configured to support the execution of [specific actions / functions]. Figure 5 The processor 300 is configured or operable to support: components for obtaining configurations related to successful handover in the case of applying an NES solution for the UE to store or report; and components for storing the information.

[0150] In some implementations, processor 300 may be configured to support components for performing NE operations. Processor 300 may be configured or operable to support components for receiving information from the UE related to a successful handover in the case of applying an NES solution.

[0151] In some implementations, processor 300 may be configured to support components for performing operations on the UE. Processor 300 may be configured or operable to support: components for storing information related to connection failure in a handover procedure when an NES solution is applied, in response to a connection failure.

[0152] In some implementations, processor 300 may be configured to support components for performing operations on the UE. Processor 300 may be configured or operable to support components for storing mobility history information regarding activation or deactivation in the case of applying an NES solution.

[0153] In some implementations, processor 300 may be configured to support components for performing NE operations. Processor 300 may be configured or operable to support components for storing UE history information regarding activation or deactivation in the context of applying an NES solution.

[0154] Those skilled in the art will understand that components in the exemplary processor 300 can be changed. For example, some components in the exemplary processor 300 may be omitted or modified, or new components may be added to the exemplary processor 300 without departing from the spirit and scope of this disclosure. For instance, in some embodiments, the processor 300 may not include an ALU 306.

[0155] Figure 4 An example of NE 400 according to aspects of this disclosure is described. NE 400 may include a processor 402, a memory 404, a controller 406, and a transceiver 408. The processor 402, memory 404, controller 406, or transceiver 408, or various combinations thereof, or various components thereof, may be examples of components for performing the aspects of this disclosure described herein. These components may be coupled via one or more interfaces (e.g., operatively, communicatively, functionally, electronically, electrically).

[0156] Processor 402, memory 404, controller 406, or transceiver 408, or various combinations or components thereof, may be implemented in hardware (e.g., a circuit system). The hardware may include processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), or other programmable logic devices, or any combination thereof, configured to or otherwise support components for performing the functions described in this disclosure.

[0157] Processor 402 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, ASICs, FPGAs, or any combination thereof). In some embodiments, processor 402 may be configured to operate memory 404. In some other embodiments, memory 404 may be integrated into processor 402. Processor 402 may be configured to execute computer-readable instructions stored in memory 404 to cause NE 400 to perform various functions of this disclosure.

[0158] Memory 404 may include volatile or non-volatile memory. Memory 404 may store computer-readable, computer-executable code containing instructions that, when executed by processor 402, cause NE 400 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium, this memory 404, or another type of memory. Computer-readable media includes both non-transitory computer storage media and communication media, which includes any media that facilitates the transfer of computer programs from one place to another. Non-transitory storage media may be any available media accessible by a general-purpose or special-purpose computer.

[0159] In some implementations, processor 402 and memory 404 coupled to processor 402 may be configured to cause NE 400 to perform one or more of the functions described herein (e.g., processor 402 executes instructions stored in memory 404). For example, processor 402 may support wireless communication at NE 400 according to the examples disclosed herein.

[0160] In some implementations, the NE 400 may be a network node and may be configured or operable to support: a component for receiving information from the UE related to a successful handover in the case of applying the NES solution.

[0161] In some implementations, the NE 400 may be a network node and may be configured or operable to support: a component for storing historical information about UE activation or deactivation in the case of applying the NES solution.

[0162] Controller 406 manages the input and output signals of NE 400. Controller 406 can also manage peripheral devices not integrated into NE 400. In some embodiments, controller 406 may utilize an operating system such as iOS®, Android®, Windows®, or other operating systems. In some embodiments, controller 406 may be implemented as part of processor 402.

[0163] In some embodiments, NE 400 may include at least one transceiver 408. In other embodiments, NE 400 may have more than one transceiver 408. Transceiver 408 may represent a wireless transceiver. Transceiver 408 may include one or more receiver chains 410, one or more transmitter chains 412, or a combination thereof. The aforementioned receiving or transmitting components in processor 402 may be implemented via at least one transceiver 408.

[0164] Receiver chain 410 may be configured to receive signals (e.g., control information, data, packets) via wireless media. For example, receiver chain 410 may include one or more antennas for receiving signals via air or wireless media. Receiver chain 410 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. Receiver chain 410 may include at least one demodulator configured to demodulate the received signal and obtain transmitted data by reversing the modulation technique applied during signal transmission. Receiver chain 410 may include at least one decoder for decoding the demodulated signal to receive transmitted data.

[0165] Transmitter chain 412 can be configured to generate and transmit signals (e.g., control information, data, packets). Transmitter chain 412 may include at least one modulator for modulating data onto a carrier signal to prepare the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques, such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes like phase shift keying (PSK) or quadrature amplitude modulation (QAM). Transmitter chain 412 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over a wireless medium. Transmitter chain 412 may also include one or more antennas for transmitting the amplified signal into the air or a wireless medium.

[0166] Those skilled in the art will understand that components in the exemplary NE 400 can be changed. For example, some components in the exemplary NE 400 may be omitted or modified, or new components may be added to the exemplary NE 400 without departing from the spirit and scope of this disclosure. For instance, in some embodiments, the NE 400 may not include the controller 406.

[0167] Figure 5 This document provides flowcharts illustrating methods related to Network Energy Saving (NES) solutions based on some aspects of this disclosure. The operation of these methods can be implemented by the UE described herein. In some implementations, aspects 502 and 504 can be referenced from... Figure 2 The UE 200 described herein is executed. Each of operations 502 and 504 may be executed according to the instances described herein.

[0168] In operation 502, the method may include obtaining a configuration (simply denoted as configuration #1) for the UE to store or report information related to a successful handover in the case of applying the NES solution (represented as information #1). (For example, information #1 is related to a successful NES-specific CHO (or a successful CHO in the case of applying the NES solution or a successful CHO for NES in the case where the source cell can use the NES solution (e.g., the cell can activate or disable cell DTX / DRX, or the cell can deactivate or enable cell DTX / DRX)). For example, if the NES solution is applied, then the UE's source cell uses the NES solution. In the NES solution, the cell can activate or disable cell DTX / DRX, or the cell can deactivate or enable cell DTX / DRX. In operation 504, the method may include having the UE store information #1. For example, information #1 is stored as a Successful Handover Report (SHR) or other named report or newly introduced report, or reported via it. In some implementations, the UE may report information #1, for example, to a network node after storing information #1.

[0169] In some implementations of the method, the UE may obtain configuration #1 through pre-configuration, such as obtaining configuration #1 by default. In some other implementations, the UE may receive configuration #1 from a network node.

[0170] For example, configuration #1 contains information indicating at least one of the following (represented as information #2):

[0171] (1) When a lower-layer message (e.g., Layer 1 (L1) signaling) is received, the handover execution condition (e.g., at least one CHO execution condition) is not met, wherein the lower-layer message contains an NES mode indication; for example, the NES mode indication may indicate that the handover execution condition is enabled or disabled. In one embodiment, the L1 signaling is DCI format 2_9, which indicates that an NES-specific CHO execution condition is enabled or disabled or is used to enable or disable a CHO execution condition. In another embodiment, the L1 signaling from the lower layer contains an indication to notify the UE that the source cell is entering NES mode (e.g., the cell DTX / DRX is deactivated or the source cell is turned off), or the L1 signaling is used to enable or disable at least one NES-specific CHO execution condition from the lower layer, or the L1 signaling indicates that an NES-specific CHO execution condition is enabled or disabled, or the L1 signaling indicates the applicability of an NES-specific CHO execution condition;

[0172] (2) The switching execution conditions are not met during the time period following the receipt of the lower-level message (e.g., a predefined time period); or

[0173] (3) The NES-specific handover execution event configured for the cell (e.g., NES-specific CHO execution event) is satisfied, but the normal handover execution event configured for the cell (e.g., normal CHO execution event) is not satisfied.

[0174] In some implementations of the method, configuration #1 includes one or more thresholds, which include at least one of the following:

[0175] (1) At least one threshold (represented as at least one threshold #1) is related to the elapsed time between receiving a lower layer message (e.g., L1 signaling, e.g., DCI format 2_9, L1 signaling containing a bit indicating that at least one CHO execution condition is enabled or disabled (e.g., NES mode indication)) and receiving a configuration regarding the switching of the application of the NES solution (e.g., CHO configuration).

[0176] (2) At least one threshold (represented as at least one threshold #2) relating to the elapsed time between receiving a lower-layer message (e.g., L1 signaling, e.g., DCI format 2_9, L1 signaling containing a bit indicating that at least one CHO execution condition is enabled or disabled (e.g., NES mode indication)) and initiating switch execution.

[0177] (3) At least one threshold (represented as at least one threshold #3) relating to the elapsed time between when a first handover execution event (e.g., an NES-specific CHO execution event) configured for a cell (e.g., a CHO candidate cell or target cell) is satisfied and when a second handover execution event (e.g., a normal CHO execution event) configured for a cell is satisfied;

[0178] (4) At least one timer T310 related threshold;

[0179] (5) At least one timer T312 related threshold; or

[0180] (6) At least one timer T304 related threshold.

[0181] In some implementations of the method, information #1 is stored in operation 504 based on at least one of the following:

[0182] (1) At least one triggering condition associated with message #2 is met. For example, it is met if at least one of the following is included:

[0183] a) The conditions for switching execution are not met when a message from the lower layer is received;

[0184] b) The switchover execution conditions are not met during the time period following the receipt of the lower-level message; or

[0185] c) The NES-specific handover execution event configured for the cell (e.g., CHO candidate cell or target cell) is satisfied, but the normal handover execution event configured for the cell is not satisfied.

[0186] (2) At least one triggering condition associated with one or more thresholds is met. For example, it is satisfied if at least one of the following is met:

[0187] a) The duration between receiving a lower-level message and receiving a configuration regarding the handover (e.g., a CHO configuration) is greater than at least one threshold #1;

[0188] b) The duration between receiving the lower-level message and initiating the switchover execution is greater than at least one threshold #2;

[0189] c) The duration between the first handover execution event (e.g., NES-specific CHO execution event or normal CHO execution event) configured for the target cell (or CHO candidate cell) and the second handover execution event (e.g., normal CHO execution event or NES-specific CHO execution event) configured for the target cell (or CHO candidate cell) is greater than at least one threshold #3;

[0190] d) When a lower-level message is received, the ratio between the elapsed runtime value of timer T310 and the configured value of timer T310 is greater than at least one timer T310 related threshold;

[0191] e) When a lower-level message is received, the ratio between the elapsed runtime value of timer T312 and the configured value of timer T312 is greater than at least one timer T312-related threshold; or

[0192] f) The ratio between the elapsed runtime value of timer T304 and the configured value of timer T304 is greater than at least one timer T304 related threshold.

[0193] (3) Switching execution or CHO execution completed successfully.

[0194] In some implementations of the method, information #1 includes at least one of the following:

[0195] (1) Information indicating that no handover execution conditions are met when a lower-level message (e.g., L1 signaling) is received or during a period (e.g., a predefined period) after the lower-level message is received. For example, the lower-level message contains an NES mode indication. The NES mode indication can indicate whether the handover execution conditions are enabled or disabled.

[0196] a) In the implementation scheme, L1 signaling is DCI format 2_9, which indicates whether a specific CHO execution condition of the NES is enabled or disabled, or is used to enable or disable CHO execution conditions.

[0197] b) In another embodiment, the L1 signaling from the lower layer includes an indication to notify the UE that the source cell is entering NES mode (e.g., the cell DTX / DRX is deactivated or the source cell is turned off), or the L1 signaling is used to enable or disable at least one NES-specific CHO enforcement condition from the lower layer, or the L1 signaling from the lower layer indicates that the NES-specific CHO enforcement condition is enabled or disabled, or the L1 signaling from the lower layer indicates the applicability of the NES-specific CHO enforcement condition.

[0198] (2) Information indicating that at least one switching execution condition is met when a lower-level message is received or during a period of time after the lower-level message is received.

[0199] (3) Information indicating whether an NES-specific switch execution event (e.g., an NES-specific CHO execution event) or a switch execution condition is met before receiving a lower-level message (represented as message #3).

[0200] (4) Information indicating whether the normal handover execution event is satisfied before receiving a message from the lower layer;

[0201] (5) Measurement results of the source cell when a lower-layer message is received.

[0202] (6) Measurement results of the target cell when a lower-layer message is received, for example, the target cell is the cell to which the UE performs a handover or CHO.

[0203] (7) Measurement results of one or more candidate cells when a lower-layer message is received.

[0204] (8) Measurement results of one or more neighboring cells when a lower-layer message is received.

[0205] (9) The reason value used to store or report information #1.

[0206] (10) The time elapsed between receiving a lower-level message and receiving a configuration regarding the switch (e.g., CHO configuration).

[0207] (11) The time elapsed between receiving a lower-level message and initiating a switchover execution (e.g., CHO execution).

[0208] (12) First satisfy the handover execution event configured for the target cell, for example, the target cell is the cell to which the UE performs a handover or CHO execution.

[0209] (13) Secondly, the handover execution event configured for the target cell is satisfied, if two or more handover execution events configured for the target cell are satisfied.

[0210] (14) The time elapsed between when the first handover execution event configured for the target cell is satisfied and when the second handover execution event configured for the target cell is satisfied.

[0211] In some implementations of the method, message #3 indicates that no NES-specific handover execution event or handover execution condition was met before the lower-level message was received.

[0212] In some implementations of the method, if information #3 indicates that a specific NES handover execution event or a handover execution condition is met before the lower-level message is received, information #1 further includes at least one of the following:

[0213] (1) Satisfy the NES-specific handover execution event before receiving the lower-layer message;

[0214] (2) The switching execution conditions are met before receiving the lower-level message (e.g., including: NES event and normal event; or normal event and another normal event; or NES event and another NES event);

[0215] (3) Cell information (e.g., cell #1) wherein the NES-specific handover execution event is satisfied or the handover execution condition is satisfied before the lower layer message is received; for example, the cell information is a cell identifier (ID) (e.g., PCI+carrier frequency information (e.g., ARFCN) and / or CGI-info (e.g., PLMN identifier, cell identifier and TrackingAreaCode));

[0216] (4) The handover execution event configured for cell #1 must be satisfied first;

[0217] (5) Secondly, the handover execution event configured for cell #1 is satisfied if two or more handover execution events configured for cell #1 are satisfied;

[0218] (6) Measurement results of cell #1 when the first handover execution event configured for cell #1 is satisfied;

[0219] (7) The measurement results of cell #1 when the second handover execution event configured for cell #1 is satisfied; or

[0220] (8) The time elapsed between when the first handover execution event of cell #1 is satisfied and when the second handover execution event of cell #1 is satisfied.

[0221] In some implementations of the method, the cause value for storing or reporting information #1 indicates at least one of the following:

[0222] (1) The duration between receiving a lower-layer message (such as the L1 signaling mentioned above) and initiating the handover execution is greater than a threshold;

[0223] (2) The duration between receiving the lower-level message and receiving the configuration regarding the handover is greater than a threshold;

[0224] (3) The switching execution conditions are not met when a lower-level message is received;

[0225] (4) The switching execution conditions were not met during the period following the receipt of the lower-level message (e.g., a predefined period);

[0226] (5) It meets the NES-specific handover execution event configured for the cell (e.g., NES-specific CHO execution event), but does not meet the normal handover execution event configured for the cell (e.g., normal CHO execution event);

[0227] (6) The duration between the time when the first handover execution event of the cell is satisfied and the time when the second handover execution event of the cell is satisfied is greater than the threshold;

[0228] (7) When a lower-level message is received, the ratio between the elapsed runtime value of timer T310 and the configured value of timer T310 is greater than a threshold.

[0229] (8) When a lower-level message is received, the ratio between the elapsed runtime value of timer T312 and the configured value of timer T312 is greater than a threshold; or

[0230] (9) The ratio between the elapsed running time value of timer T304 and the configured value of timer T304 is greater than the threshold.

[0231] In some implementations of the method, the UE may transmit optional UE capability information, such as optional UE capability information with or without signaling, to the network node for supporting the storage and reporting of information #1.

[0232] It should be noted that Figure 5 The methods described herein describe possible implementations, and the operations and procedures may be rearranged or otherwise eliminated or modified without departing from the spirit and scope of this disclosure, and other implementations are possible.

[0233] Based on some aspects of this disclosure, methods related to NES solutions can be implemented by the NE described herein. In some implementations, aspects of the operation of the NE can be found in references. Figure 4The NE 400 described herein is implemented. It should be noted that the methods implemented by the NE described herein are possible implementations, and the operations and steps may be rearranged or otherwise eliminated or modified without departing from the spirit and scope of this disclosure, and other implementations are possible. Specific examples are described below in Embodiment 2-1.

[0234] Specifically, the method may include information received by the NE from the UE related to a successful handover in the case of applying the NES solution (e.g. Figure 5 Information #1 described in the embodiments. For example, if an NES solution is applied, then the UE's source cell uses the NES solution. In the NES solution, the cell can activate or deactivate cell DTX / DRX, or the cell can deactivate or activate cell DTX / DRX. Information may include... Figure 5 The elements described in the embodiments are the same as those in information #1. In some embodiments, the information is received via SHR or other named reports or newly introduced reports.

[0235] In some implementations of the method, the NE may transmit configuration to the UE for storing or reporting information #1 (e.g., Figure 5 The configuration described in the embodiment is #1). The configuration may include... Figure 5 The elements described in the embodiments are the same as those in configuration #1. For example, the configuration contains information indicating at least one of the following (e.g., Figure 5 Information described in the embodiments #2):

[0236] (1) When a lower-layer message is received (e.g., L1 signaling, the details of which may refer to or be similar to L1 signaling), Figure 5 When the switching execution condition is not met (as described in the embodiments), the lower-level message contains an NES mode indication, which may indicate whether the switching execution condition is enabled or disabled.

[0237] (2) The switching execution conditions are not met during the time period following the receipt of the lower-level message (e.g., a predefined time period); or

[0238] (3) The NES-specific handover execution event configured for the cell (e.g., NES-specific CHO execution event) is satisfied, but the normal handover execution event configured for the cell (e.g., normal CHO execution event) is not satisfied.

[0239] In some implementations of the method, the NE may receive optional UE capability information from the UE for supporting the storage and reporting of information, such as optional UE capability information with or without signaling.

[0240] Based on some aspects of this disclosure, the methods related to the NES solution can be implemented by the UE described herein. In some implementations, aspects of the UE's operation can be described by reference to... Figure 2 The UE 200 described herein is implemented. It should be noted that the methods implemented by the UE herein describe possible implementations, and that operations and steps may be rearranged or otherwise eliminated or modified without departing from the spirit and scope of this disclosure, and other implementations are possible. Specific examples are described below in Embodiments 2-2.

[0241] Specifically, in response to a connection failure, the method may include having the UE store information related to the connection failure from the handover procedure in the case of an NES solution being applied. For example, if an NES solution is applied, then the UE's source cell uses the NES solution. In the NES solution, the cell can activate or deactivate cell DTX / DRX, or the cell can deactivate or activate cell DTX / DRX.

[0242] In some implementations of the method, the information related to connection failure includes at least one of the following:

[0243] (1) Indicates when a lower-layer message (e.g., L1 signaling, details of which may refer to or be similar to) is received. Figure 5 Information that the switching execution condition is not met during the period following the receipt of a lower-level message (as described in the embodiments), wherein the lower-level message contains an NES mode indication that may indicate that the switching execution condition is enabled or disabled;

[0244] (2) Information indicating that at least one switching execution condition is met when a lower-level message is received or during a period of time (e.g., a predefined period) after the lower-level message is received;

[0245] (3) Information indicating whether a NES-specific handover execution event (e.g., an NES-specific CHO execution event) or handover execution conditions are met before receiving a lower-level message;

[0246] (4) Information indicating whether the normal handover execution event is satisfied before receiving a message from the lower layer;

[0247] (5) Measurement results of the source cell when a lower-layer message is received;

[0248] (6) Measurement results of the target cell when a lower-layer message is received;

[0249] (7) Measurement results of one or more candidate cells when a lower-layer message is received;

[0250] (8) Measurement results of one or more neighboring cells when a lower-layer message is received;

[0251] (9) The time elapsed between receiving a lower-level message and receiving a switching configuration (e.g., a CHO configuration);

[0252] (10) The time elapsed between receiving a lower-level message and initiating a switchover execution (e.g., CHO execution);

[0253] (11) First, satisfy the handover execution event configured for the target cell, for example, the target cell is the cell to which the UE performs a handover or CHO execution;

[0254] (12) Secondly, the handover execution events configured for the target cell are satisfied if two or more handover execution events configured for the target cell are satisfied; or

[0255] (13) The time elapsed between when the first handover execution event configured for the target cell is satisfied and when the second handover execution event configured for the target cell is satisfied.

[0256] In some implementations of the method, the information related to connection failure includes information indicating that no NES-specific handover execution event or handover execution condition was met before the lower-layer message was received.

[0257] In some implementations of the method, where the information related to connection failure includes information indicating that "a specific NES handover execution event is satisfied before receiving a lower-layer message or a handover execution condition is satisfied before receiving a lower-layer message," the information related to connection failure further includes at least one of the following:

[0258] (1) Satisfy the NES-specific handover execution event before receiving the lower-layer message;

[0259] (2) The switching execution conditions are met before receiving the lower-level message (e.g., including: NES event and normal event; or normal event and another normal event; or NES event and another NES event);

[0260] (3) Cell information (e.g., cell #A), wherein the NES-specific handover execution event is satisfied before the lower-layer message is received or the handover execution condition is satisfied before the lower-layer message is received; for example, the cell information is the cell identifier (ID) (e.g., PCI+carrier frequency information (e.g., ARFCN) and / or CGI-info (e.g., PLMN identifier, cell identifier and TrackingAreaCode));

[0261] (4) First, satisfy the handover execution event configured for the cell (e.g., cell #A);

[0262] (5) Secondly, the handover execution event configured for the cell (e.g., cell #A) is satisfied if two or more handover execution events configured for the cell (e.g., cell #A) are satisfied;

[0263] (6) Measurement results of cell #A when the first handover execution event configured for cell #A is met;

[0264] (7) The measurement results of cell #A when the second handover execution event configured for cell #A is satisfied; or

[0265] (8) The time elapsed between when the first handover execution event of cell (e.g., cell #A) is satisfied and when the second handover execution event of cell (e.g., cell #A) is satisfied.

[0266] In some implementations of the method, information related to connection failure is stored as a Radio Link Failure (RLF) report or other named reports or newly introduced reports, or reported via such reports.

[0267] In some implementations of the method, the UE may, after storing information related to the connection failure, report the information related to the connection failure to a network node, for example.

[0268] Based on some aspects of this disclosure, the methods related to the NES solution can be implemented by the UE described herein. In some implementations, aspects of the UE's operation can be described by reference to... Figure 2 The UE 200 described herein is implemented. It should be noted that the methods implemented by the UE herein describe possible implementations, and that operations and steps may be rearranged or otherwise eliminated or modified without departing from the spirit and scope of this disclosure, and other implementations are possible. Specific examples are described below in Embodiment 3-1.

[0269] Specifically, the method may include the UE storing Mobility History Information (MHI) regarding activation or deactivation in the context of applying the NES solution. In some implementations of the method, the UE may report the MHI to the NE. For example, the Mobility History Information may include at least one of the following:

[0270] (1) Information associated with cell DTX activation of at least one cell; in some embodiments, for a cell within at least one cell, the information associated with cell DTX activation of the cell includes at least one of the following:

[0271] a) Cell identifier (ID) (e.g., PCI+carrier frequency information (e.g., ARFCN) and / or CGI-info (e.g., PLMN identifier, cell identifier, and TrackingAreaCode));

[0272] b) The time when the cell DTX was activated;

[0273] c) The duration for which the cell DTX is activated; or

[0274] d) Percentage of the duration during which the cell DTX is activated.

[0275] (2) Information associated with cell DTX deactivation of at least one cell; in some embodiments, for one cell within at least one cell, the information associated with cell DTX deactivation of the cell includes at least one of the following:

[0276] a) Cell identifier (ID) (e.g., PCI+carrier frequency information (e.g., ARFCN) and / or CGI-info (e.g., PLMN identifier, cell identifier, and TrackingAreaCode));

[0277] b) The time when the community DTX was deactivated;

[0278] c) The duration for which the cell DTX was deactivated; or

[0279] d) Percentage of the duration during which the cell DTX was deactivated.

[0280] (3) Information associated with cell DRX activation of at least one cell; in some implementations, for a cell within at least one cell, the information associated with cell DRX activation of the cell includes at least one of the following:

[0281] a) Cell identifier (ID) (e.g., PCI+carrier frequency information (e.g., ARFCN) and / or CGI-info (e.g., PLMN identifier, cell identifier, and TrackingAreaCode));

[0282] b) The time when the cell's DRX was activated;

[0283] c) The duration for which the cell DRX is activated; or

[0284] d) Percentage of the duration during which the cell's DRX was activated.

[0285] (4) Information associated with cell DRX deactivation of at least one cell; in some implementations, for a cell within at least one cell, the information associated with cell DRX deactivation of the cell includes at least one of the following:

[0286] a) Cell identifier (ID) (e.g., PCI+carrier frequency information (e.g., ARFCN) and / or CGI-info (e.g., PLMN identifier, cell identifier, and TrackingAreaCode));

[0287] b) The time when the community's DRX was deactivated;

[0288] c) The duration for which the cell's DRX was deactivated; or

[0289] d) Percentage of the duration during which the cell's DRX was deactivated.

[0290] Based on some aspects of this disclosure, methods related to NES solutions can be implemented by the NE described herein. In some implementations, aspects of the operation of the NE can be found in references. Figure 4 The NE 400 described herein is implemented. It should be noted that the methods implemented by the NE described herein are possible implementations, and the operations and steps may be rearranged or otherwise eliminated or modified without departing from the spirit and scope of this disclosure, and other implementations are possible. Specific examples are described below in Examples 3-2.

[0291] Specifically, the method may include UE history information (UHI) stored by the NE regarding activation or deactivation in the context of applying the NES solution. In some implementations, the UHI includes at least one of the following:

[0292] (1) Information associated with cell DTX activation of at least one cell; in some embodiments, for a cell within at least one cell, the information associated with cell DTX activation of the cell includes at least one of the following:

[0293] a) Cell identifier (ID) (e.g., PCI+carrier frequency information (e.g., ARFCN) and / or CGI-info (e.g., PLMN identifier, cell identifier, and TrackingAreaCode));

[0294] b) The time when the cell DTX was activated;

[0295] c) The duration for which the cell DTX is activated; or

[0296] d) Percentage of the duration during which the cell DTX is activated.

[0297] (2) Information associated with cell DTX deactivation of at least one cell; in some embodiments, for one cell within at least one cell, the information associated with cell DTX deactivation of the cell includes at least one of the following:

[0298] a) Cell identifier (ID) (e.g., PCI+carrier frequency information (e.g., ARFCN) and / or CGI-info (e.g., PLMN identifier, cell identifier, and TrackingAreaCode));

[0299] b) The time when the community DTX was deactivated;

[0300] c) The duration for which the cell DTX was deactivated; or

[0301] d) Percentage of the duration during which the cell DTX was deactivated.

[0302] (3) Information associated with cell DRX activation of at least one cell; in some implementations, for a cell within at least one cell, the information associated with cell DRX activation of the cell includes at least one of the following:

[0303] a) Cell identifier (ID) (e.g., PCI+carrier frequency information (e.g., ARFCN) and / or CGI-info (e.g., PLMN identifier, cell identifier, and TrackingAreaCode));

[0304] b) The time when the cell's DRX was activated;

[0305] c) The duration for which the cell DRX is activated; or

[0306] d) Percentage of the duration during which the cell's DRX was activated.

[0307] (4) Information associated with cell DRX deactivation of at least one cell; in some implementations, for a cell within at least one cell, the information associated with cell DRX deactivation of the cell includes at least one of the following:

[0308] a) Cell identifier (ID) (e.g., PCI+carrier frequency information (e.g., ARFCN) and / or CGI-info (e.g., PLMN identifier, cell identifier, and TrackingAreaCode));

[0309] b) The time when the community's DRX was deactivated;

[0310] c) The duration for which the cell's DRX was deactivated; or

[0311] d) Percentage of the duration during which the cell's DRX was deactivated.

[0312] The following describes specific embodiments of the flowcharts shown and described above (i.e., Embodiment 1, Embodiment 2 and Embodiment 3).

[0313] Example 1 (A near-failure to achieve a successful CHO for NES)

[0314] In Embodiment 1, a near-failure successful NES CHO (or a near-failure successful NES-specific CHO, or a near-failure successful CHO in the context of applying an NES solution, or a near-failure successful CHO in the context where the source cell can use an NES solution (e.g., the cell can activate or deactivate cell DTX / DRX, or the cell can deactivate or activate cell DTX / DRX), or a near-failure successful CHO for NES) can exist in two cases, namely, Case 1 and Case 2 as follows. For Case 1 and Case 2, the embodiments of this disclosure consider MRO mechanisms for NES, for example, as described in Embodiments 1-1, 1-2, 2-1, and 2-2 as follows.

[0315] Scenario 1: When the UE receives a lower-layer message (e.g., L1 signaling, the details of which may refer to or be similar to...) Figure 5 When the candidate cell does not meet the CHO execution conditions (as described in the embodiments) (e.g., when the UE is notified to enable the CHO condition configured with NES event indication via DCI) or during a predefined limited period after receiving L1 signaling.

[0316] In scenario 1, the lower-layer message may contain an NES mode indication indicating that a handover execution condition is enabled or disabled. For example, L1 signaling is DCI format 2_9, which indicates that at least one NES-specific CHO execution condition is enabled or disabled, or is used to enable or disable a CHO execution condition, or L1 signaling from the lower layer notifies the UE that the source cell is entering NES mode (e.g., cell DTX or DRX is deactivated or the source cell is turned off).

[0317] In some embodiments, Case 1 may contain the following instances. In one instance, a candidate cell is configured with one traditional or normal CHO execution event and one NES-specific CHO execution event, but neither event is satisfied upon receiving L1 signaling or after a predefined finite time following the receipt of L1 signaling. In another instance, a candidate cell is configured with two traditional or normal CHO execution events, but neither event is satisfied upon receiving L1 signaling or after a predefined finite time following the receipt of L1 signaling. In an additional instance, a candidate cell is configured with two NES-specific CHO execution events, but neither event is satisfied upon receiving L1 signaling or after a predefined finite time following the receipt of L1 signaling. In yet another instance, a candidate cell is configured with three or more NES-specific CHO execution events, but none of these three or more events are satisfied upon receiving L1 signaling or after a predefined finite time following the receipt of L1 signaling.

[0318] In Case 1, after receiving L1 signaling, the UE can continue to measure and evaluate the CHO execution conditions to select a target cell until CHO execution is initiated or triggered, or until an RLF occurs. Case 1 has two potential sub-cases, namely, Case 1-1 and Case 1-2 as follows.

[0319] Case 1-1: Before receiving L1 signaling, the NES-specific CHO execution event is satisfied (e.g., for a candidate cell configured with both traditional or normal CHO execution events and NES-specific CHO execution events, the NES-specific CHO execution event is satisfied (regardless of whether the traditional or normal CHO execution event is satisfied); or for a candidate cell configured with two NES-specific CHO execution events, at least one of the two NES-specific CHO execution events is satisfied); however, when L1 signaling is received or during a predefined limited period after receiving L1 signaling, the candidate cell does not meet the CHO execution conditions. In Case 1-1, after receiving L1 signaling, the UE can continue to measure and evaluate the CHO execution conditions to select the target cell. In Case 1-1, there are three potential sub-cases, namely, Case 1-1-1, Case 1-1-2, and Case 1-1-3 as follows.

[0320] - Case 1-1-1: When a target cell is selected, the UE performs a CHO operation toward the target cell, but the CHO operation is a near-failure CHO operation.

[0321] - Case 1-1-2: When a target cell is selected, the UE performs a CHO (Continuous Homing) towards the target cell, but the CHO execution fails or an RLF (Restricted Line Response) occurs shortly after a successful CHO execution.

[0322] - Case 1-1-3: The target cell is not selected until an RLF occurs.

[0323] Case 1-2: Before receiving L1 signaling, the CHO execution conditions are not met (e.g., the NES-specific CHO execution event or the traditional or normal CHO execution event is not met); and when L1 signaling is received, or during a predefined finite period after receiving L1 signaling, the candidate cell does not meet the CHO execution conditions. In Case 1-2, after receiving L1 signaling, the UE can continue to measure and evaluate the CHO execution conditions to select the target cell. In Case 1-2, there are three potential sub-cases, namely, Case 1-2-1, Case 1-2-2, and Case 1-2-3 as follows.

[0324] - Case 1-2-1: Select the target cell, the UE performs CHO execution, but the CHO execution is a near-failure CHO execution.

[0325] - Case 1-2-2: The target cell is selected, and the UE performs a CHO execution, but the CHO execution fails or an RLF occurs shortly after a successful CHO execution.

[0326] - Situation 1-2-3: The target cell is not selected until an RLF occurs.

[0327] Scenario 2: When the UE receives a lower-layer message (e.g., L1 signaling, the details of which may refer to or be similar to...) Figure 5 When (as described in the embodiments) (e.g., when the UE is notified via DCI to enable the CHO condition configured with NES event indication) or during a predefined finite period after receiving L1 signaling, at least one candidate cell satisfies the CHO execution condition.

[0328] In scenario 2, the lower-layer message may contain an NES mode indication, which indicates whether the handover execution condition is enabled or disabled. For example, L1 signaling is DCI format 2_9, which indicates whether a specific NES CHO execution condition is enabled or disabled, or is used to enable or disable CHO execution conditions, or L1 signaling from the lower layer notifies the UE that the source cell is entering NES mode (e.g., the cell DTX or DRX is deactivated or the source cell is turned off).

[0329] In case 2, there are two potential sub-cases, namely, case 2-1 and case 2-2 as follows.

[0330] Case 2-1: Before receiving L1 signaling, at least one NES-specific CHO execution event is satisfied (e.g., for a candidate cell configured with both traditional or normal CHO execution events and NES-specific CHO execution events, the NES-specific CHO execution event is satisfied (regardless of whether the traditional or normal CHO execution event is satisfied); or for a candidate cell configured with two NES-specific CHO execution events, at least one of the two NES-specific CHO execution events is satisfied); and when L1 signaling is received, or during a predefined finite period after receiving L1 signaling, the CHO execution condition is satisfied. Under Case 2-1, there are two potential sub-cases, namely, Case 2-1-1 and Case 2-1-2 as follows.

[0331] - Case 2-1-1: The UE executes a CHO execution, but the CHO execution is a near-failure CHO execution.

[0332] - Case 2-1-2: The UE performs a CHO execution, but the CHO execution fails or an RLF occurs shortly after a successful CHO execution.

[0333] Case 2-2: The CHO execution conditions are not met before receiving the L1 signaling (e.g., the NES-specific CHO execution event or the traditional or normal CHO execution event is not met); and the CHO execution conditions are met when the L1 signaling is received or during a predefined finite period after receiving the L1 signaling. Under Case 2-2, there are two potential sub-cases, namely, Case 2-2-1 and Case 2-2-2 as follows.

[0334] - Case 2-2-1: The UE executes a CHO execution, but the CHO execution is a near-failure CHO execution.

[0335] - Case 2-2-2: The UE performs a CHO execution, but the CHO execution fails or an RLF occurs shortly after a successful CHO execution.

[0336] Example 1-1 (NES CHO specific triggering conditions)

[0337] In Example 1-1, for near-failure success cases (e.g., Case 1-1-1, Case 1-2-1, Case 2-1-1, or Case 2-2-1), the NESCHO-specific triggering conditions for the success report (e.g., the success report may be an SHR or other named report or a newly introduced report) can be as follows.

[0338] In Example 1-1, for NES-specific CHOs (or CHOs in the case of applying the NES solution, or CHOs in the case where the source cell can use the NES solution (e.g., the cell can activate or deactivate cell DTX / DRX, or the cell can deactivate or activate cell DTX / DRX), or CHOs for NES), the UE records or stores or generates a success report for the NES CHO (e.g., the success report can be an SHR or other named report or a newly introduced report) or records or stores or generates information related to successful NES-specific CHOs or information related to successful CHOs for NES (e.g., ... Figure 5 The triggering conditions of information #1 described in the embodiments (e.g.) Figure 5 The configuration #1 described in the embodiments is configured to the UE. The triggering condition may be named a configuration for recording or storing or generating information related to a successful NES-specific CHO or a successful NES CHO (e.g., configuration #1).

[0339] For example, "the configuration for recording, storing, or generating information related to a successful NES-specific CHO or information related to a successful NES CHO" may include at least one of the following triggering conditions:

[0340] (1) Received lower-layer messages (e.g., L1 signaling, details of which may refer to or be similar to) Figure 5(as described in the embodiments) at least one threshold (e.g., at least one threshold #1 mentioned above) related to the duration between receiving the CHO configuration.

[0341] a) Lower-level messages may contain NES mode indications, which indicate whether the CHO or switching execution condition is enabled or disabled.

[0342] b) For an instance, the L1 signaling is DCI format 2_9, which indicates whether a specific CHO execution condition of the NES is enabled or disabled, or is used to enable or disable CHO execution conditions.

[0343] c) In another instance, L1 signaling comes from the lower layer to notify the UE that the source cell is entering NES mode (e.g., the cell DTX / DRX is deactivated or the source cell is turned off), or L1 signaling is used to enable or disable at least one NES-specific CHO enforcement condition, or L1 signaling contains an indication indicating that at least one NES-specific CHO enforcement condition is enabled or disabled, or L1 signaling contains an indication indicating the applicability of the NES-specific CHO enforcement condition.

[0344] (2) At least one threshold (e.g., at least one threshold #2 above) related to the duration between receiving L1 signaling and when CHO execution is initiated or triggered (e.g., when at least one of a normal CHO execution event configured for the candidate cell and an NES-specific CHO execution event is met, or when at least one of two normal CHO execution events configured for the candidate cell or two NES-specific CHO execution events configured for the candidate cell is met).

[0345] (3) Indicates that the CHO execution conditions are not met when L1 signaling is received.

[0346] (4) An indication that the CHO execution conditions are not met during a predefined period after the L1 signaling is received.

[0347] (5) Instructions that when configuring an NES-specific CHO execution event and a normal CHO event for a cell (e.g., target cell), the NES-specific CHO execution event of the cell (e.g., target cell) is satisfied but the normal CHO execution event of the cell (e.g., target cell) is not satisfied.

[0348] (6) At least one threshold (e.g., at least one threshold #3 above) related to the duration between when a normal CHO execution event configured for a cell (e.g., the target cell) is satisfied and when a NES-specific CHO execution event configured for a cell (e.g., the target cell) is satisfied.

[0349] (7) At least one T310 related threshold, such as when L1 signaling is received (or when DCI format 2_9 indicating that at least one NES-specific CHO execution condition is enabled or disabled, or when an indication is received from the lower layer that the source cell is entering NES mode (e.g., cell DTX or DRX is deactivated or the source cell is turned off), or when an indication is received from the lower layer to enable or disable at least one NES-specific CHO execution condition, or when an indication is received from the lower layer to enable or disable at least one NES-specific CHO execution condition, or when an indication is received from the lower layer to indicate the applicability of the NES-specific CHO execution condition, or when the UE is notified via DCI to enable a CHO execution condition configured with an NES event indication) is a threshold of the percentage ratio between the elapsed running time of timer T310 and the configured value of timer T310.

[0350] a) At least one T310-related trigger threshold may be per cell (e.g., for each CHO candidate cell, the network determines or generates a T310-related trigger threshold, and the T310-related trigger threshold for successful reporting of NES CHO is configured for the UE of each cell).

[0351] b) Or at least one T310-related trigger threshold may be per UE (e.g., only one T310-related trigger threshold is configured for the UE, i.e., for each CHO candidate cell, the T310-related trigger threshold for successful reporting of NES CHO is the same).

[0352] (8) At least one T312 related threshold, such as when L1 signaling is received (or when DCI format 2_9 indicating that NES-specific CHO execution conditions are enabled or disabled is received, or when an indication is received from the lower layer that the source cell is entering NES mode (e.g., cell DTX or DRX is deactivated or the source cell is turned off), or when an indication is received from the lower layer for enabling or disabling at least one NES-specific CHO execution condition, or when an indication is received from the lower layer indicating that NES-specific CHO execution conditions are enabled or disabled, or when an indication is received from the lower layer indicating the applicability of NES-specific CHO execution conditions, or when the UE is notified via DCI to enable a CHO execution condition configured with NES event indication) is enabled, a threshold of the percentage ratio between the elapsed runtime of timer T312 and the configured value of timer T312.

[0353] a) At least one T312-related trigger threshold may be per cell (e.g., for each CHO candidate cell, the network determines or generates a T312-related trigger threshold, and the T312-related trigger threshold for successful reporting of NES CHO is configured for the UE of each cell).

[0354] b) Or at least one T312-related trigger threshold may be per UE (e.g., only one T312-related trigger threshold is configured for the UE, i.e., for each CHO candidate cell, the T312-related trigger threshold for successful reporting of NES CHO is the same).

[0355] (9) At least one T304-related threshold, such as a threshold for the percentage ratio between the elapsed runtime of timer T304 and the configured value of timer T304.

[0356] a) At least one T304-related trigger threshold may be per cell (e.g., for each CHO candidate cell, the network determines or generates a T304-related trigger threshold, and at least one T304-related trigger threshold for successful reporting of NES CHO is configured for the UE of each cell).

[0357] b) Or at least one T304-related trigger threshold may be per UE (e.g., only one T304-related trigger threshold is configured for the UE, i.e., for each CHO candidate cell, the T304-related trigger threshold for successful reporting of NES CHO is the same).

[0358] The specific triggering conditions (e.g., configuration #1) for the above NES CHO that result in a successful report (e.g., a threshold or condition) can be configured by default in the UE (e.g., through pre-configuration) or by the network (e.g., a source node or a target node).

[0359] Examples 1-2 (UE Capabilities)

[0360] Because the UE needs to store or generate or report (near failure) successful NES-specific CHO information or information related to successful CHOs for NES (e.g., triggering conditions mentioned in Example 1-1) (e.g., configuration #1), the network needs to know the UE's capabilities in order to configure appropriate settings to trigger successful reporting for NES CHOs.

[0361] In embodiments 1-2, an optional UE capability is introduced for storing or reporting information related to a (near-failure) successful NES-specific CHO or information related to a successful NES CHO. Even if the UE supports the NES CHO procedure, storing or reporting information related to a successful NES-specific CHO or information related to a successful NES CHO may be optional. In one example, this capability is explicitly signaled to the network; that is, explicit capability signaling is required. In another example, the optional UE capability with signaling is signaled to the network. For example, different embodiments may exist, such as options #A and #B as follows.

[0362] Option #A: Optional capability signaling. Even if the UE supports a CHO (or NES CHO or NES-specific CHO) mechanism for NES or has cell DTX or DRX (NES cell DTX or DRX) capabilities, storing or reporting information related to near-failure successful CHOs (or NES CHOs or NES-specific CHOs) for NES is optional. This capability can be explicitly signaled to the network by the UE, for example, by introducing a new UE capability bit (optionally with signaling) to support the storage and delivery of information related to successful NES-specific CHOs or successful CHOs for NES.

[0363] In some implementations of option #A, a new UE capability bit may be introduced for a successful report of a CHO (or NESCHO or NES-specific CHO) for NES, based on a request from the network (e.g., a successful report may be an SHR or other named report or a newly introduced report).

[0364] For one instance, the UE may transmit an optional UE capability indication for storing or reporting information related to a near-failure successful CHO (or NESCHO or NES-specific CHO) for NES, or, for example, transmit an optional UE capability indication of an SHR for a CHO (or NES CHO or NES-specific CHO) for NES in a UE capability information message. For another instance, the UE may reuse an existing optional UE capability indication from a successful handover (HO) report (i.e., success-HO-Report-r17) for a CHO (or NES CHO or NES-specific CHO) for NES in a UE capability information message.

[0365] Option #B: Optional no capability signaling. Storing or reporting information related to near-failure successful CHOs (or NES CHOs or NES-specific CHOs) for NES is optional, and the UE does not signal explicit capability bits. Option #B introduces an optional feature for signaling SHRs without NES CHOs (or NES CHOs or NES-specific CHOs). Additionally, for RLF reports for NES CHOs (or NES CHOs or NES-specific CHOs), this is an optional feature without signaling. For Random Access (RA) reports for NES CHOs (or NES CHOs or NES-specific CHOs), this is an optional feature without signaling. In Option #B, for Self-Optimization (SON) enhancements for NES CHOs (or NES CHOs or NES-specific CHOs), a new optional feature is introduced in the SON report. This feature optionally has no signaling and covers RA reports or SHR or RLF reports.

[0366] Example 2 (Information stored or reported by the UE)

[0367] Example 2-1 (Information in the success report)

[0368] As illustrated in Example 1, near-failure success scenarios can occur (e.g., scenario 1-1-1, scenario 1-2-1, scenario 2-1-1, or scenario 2-2-1). Example 2-1 provides a solution regarding successful reports for NES CHOs stored or reported by the UE (e.g., successful reports may be SHR or other named reports or newly introduced reports) or information related to successful NES-specific CHOs or information related to successful CHOs for NES.

[0369] In Example 2-1, when at least one configuration trigger condition (e.g., configuration #1) mentioned in Example 1-1 is met and / or the CHO towards the target cell is successfully executed, the UE records or stores a success report for the NES CHO or information related to a successful NES-specific CHO or information related to a successful CHO for the NES.

[0370] For example, if at least one of the following triggering conditions is met and / or the handover to the target cell is successful, then the UE records or stores a success report for the NES CHO (e.g., the success report may be an SHR or other named report or a newly introduced report) or information related to a successful NES-specific CHO or information related to a successful CHO for NES:

[0371] (1) Received lower-layer messages (e.g., L1 signaling, details of which may refer to or be similar to L1 signaling). Figure 5 The duration between the receipt of the CHO configuration (as described in the embodiments) and the receipt of the CHO configuration is greater than the threshold mentioned in Embodiment 1-1 (e.g., at least one threshold #1).

[0372] a) Lower-level messages may contain NES mode indications, which indicate whether the CHO or switching execution condition is enabled or disabled.

[0373] b) For an instance, the L1 signaling is DCI format 2_9, which indicates whether a specific CHO execution condition of the NES is enabled or disabled, or is used to enable or disable CHO execution conditions.

[0374] c) For another instance, the L1 signaling includes an indication to the UE that the source cell is entering NES mode (e.g., the cell DTX or DRX is deactivated or the source cell is turned off), or an indication to enable or disable at least one NES-specific CHO enforcement condition from the lower layer, or an indication from the lower layer that at least one NES-specific CHO enforcement condition is enabled or disabled, or an indication from the lower layer that the applicability of the NES-specific CHO enforcement condition is indicated.

[0375] (2) The duration between receiving L1 signaling and the start or triggering of CHO execution (e.g., when at least one of the normal CHO execution event configured for the candidate cell and the NES-specific CHO execution event is met, or when two normal CHO execution events configured for the candidate cell or at least one of two or more NES-specific CHO execution events configured for the candidate cell is met) is greater than the threshold mentioned in Example 1-1 (e.g., at least one threshold #2).

[0376] (3) When L1 signaling is received, the CHO execution conditions are not met.

[0377] (4) The CHO execution conditions are not met during the predefined period after receiving the L1 signaling.

[0378] (5) Configure an NES-specific CHO execution event and a normal CHO event for the target cell, satisfying the NES-specific CHO execution event of the target cell, but not the normal CHO execution event of the target cell.

[0379] (6) The duration between the time when a normal CHO execution event configured for a cell (e.g., the target cell) is satisfied and the time when a NES-specific CHO execution event configured for a cell (e.g., the target cell) is satisfied is greater than the threshold mentioned in Example 1-1 (e.g., at least one threshold #3).

[0380] (7) When L1 signaling is received (or when DCI format 2_9 indicating that NES-specific CHO execution conditions are enabled or disabled is received, or when an instruction is received from the lower layer notifying that the source cell is entering NES mode (e.g., cell DTX or DRX is deactivated or the source cell is turned off), or when an instruction is received from the lower layer to enable or disable at least one NES-specific CHO execution condition, or when an instruction is received from the lower layer indicating that at least one NES-specific CHO execution condition is enabled or disabled, or when an instruction is received from the lower layer indicating the applicability of NES-specific CHO execution conditions, or when the UE is notified via DCI to enable CHO execution conditions configured with NES event indication), the percentage ratio between the elapsed running time of timer T310 and the configured value of timer T310 is greater than a threshold (i.e., at least one T310-related threshold mentioned in Example 1-1).

[0381] (8) When L1 signaling is received (or when DCI format 2_9 indicating that NES-specific CHO execution conditions are enabled or disabled is received, or when an indication is received from the lower layer that the source cell is entering NES mode (e.g., cell DTX or DRX is deactivated or the source cell is turned off), or when an indication is received from the lower layer to enable or disable at least one NES-specific CHO execution condition, or when an indication is received from the lower layer indicating that NES-specific CHO execution conditions are enabled or disabled, or when an indication is received from the lower layer indicating the applicability of NES-specific CHO execution conditions, or when the UE is notified via DCI to enable CHO execution conditions configured with NES event indications), the percentage ratio between the elapsed running time of timer T312 and the configured value of timer T312 is greater than a threshold (i.e., at least one T312-related threshold mentioned in Example 1-1).

[0382] (9) The ratio between the elapsed time value of timer T304 and the configuration value of timer T304 (e.g., contained in the last RRC reconfiguration message for NES CHO) is greater than a threshold (i.e., at least one T304-related threshold mentioned in Example 1-1).

[0383] In Example 2-1, a success report for an NES CHO (e.g., an SHR or other named report or a newly introduced report) or information related to a successful NES-specific CHO or information related to a successful CHO for NES may include at least one of the following:

[0384] (1) (For example, for case 1-1-1 or case 1-2-1) indicates that no candidate cell meets the CHO execution conditions when L1 signaling is received or during a predefined finite period after L1 signaling is received.

[0385] 1) Lower-level messages may contain NES mode indications, which may indicate whether the switching execution conditions are enabled or disabled.

[0386] 2) For example, L1 signaling is DCI format 2_9, which indicates whether a specific CHO execution condition for NES is enabled or disabled, or is used to enable or disable CHO execution conditions. Alternatively, L1 signaling may contain an indication from the lower layer to the UE that the source cell is entering NES mode (e.g., the cell DTX or DRX is deactivated or the source cell is turned off).

[0387] (2) (e.g., for case 2-1-1 or case 2-2-1) indicates that at least one CHO execution condition is met when L1 signaling is received or during a predefined finite period after L1 signaling is received.

[0388] (3) An indication of whether the CHO execution conditions or NES-specific CHO execution events are met before receiving the L1 signaling, for example:

[0389] 1) For example, for case 1-1-1 or case 2-1-1, the UE may store or report an indication that a CHO execution condition or an NES-specific CHO execution event was met before receiving L1 signaling. Furthermore, for such met CHO execution conditions or NES-specific CHO execution events, the UE may store or report at least one of the following:

[0390] i. Information about the cell whose CHO execution conditions or NES-specific CHO execution events are met (e.g., cell information may include cell ID, which may include PCI+ carrier frequency information (e.g., ARFCN) and / or CGI-info (e.g., PLMN identifier, cell identifier, and TrackingAreaCode));

[0391] ii. The first-satisfied event of the cell (e.g., the first-satisfied event may be a conventional or normal CHO execution event or an NES-specific CHO execution event);

[0392] iii. A secondary satisfied event of the cell (e.g., a secondary satisfied event could be a conventional or normal CHO execution event or an NES-specific CHO execution event) (if present); and

[0393] iv. The duration between when the cell's conventional or normal CHO execution event is satisfied and when the cell's NES-specific CHO execution event is satisfied, if both events are satisfied.

[0394] 2) For another instance, for case 1-2-1 or case 2-2-1, the UE may store or report an indication that the CHO execution conditions (e.g., NES-specific CHO execution events or traditional or normal CHO execution events) were not met before receiving L1 signaling.

[0395] (4) (For example, for case 1-1-1 or case 1-2-1 or case 2-1-1 or case 2-2-1) Measurement results after or at the time of receiving L1 signaling (e.g., source cell, candidate cell or neighboring cell).

[0396] (5) (For example, for case 1-1-1, case 1-2-1, case 2-1-1, or case 2-2-1) New SHR cause value. For example, an SHR may include:

[0397] 1) Indicates a reason value where the duration between receiving L1 signaling and the initiation or triggering of CHO execution is greater than a threshold value, or

[0398] 2) Indicates the reason value for why the CHO execution conditions are not met when L1 signaling is received, or

[0399] 3) Indicates the reason value for why the CHO execution conditions are not met during a predefined period after receiving the L1 signaling, or

[0400] 4) Indicates the reason value that satisfies the NRS-specific CHO execution event for the target cell but does not satisfy the normal CHO execution event for the target cell, or

[0401] 5) Indicate the reason why the duration between the time when a normal CHO execution event configured for a cell (e.g., the target cell) is satisfied and the time when a NES-specific CHO execution event configured for a cell (e.g., the target cell) is satisfied is greater than a threshold, etc.

[0402] (6) (For example, for case 1-1-1 or case 1-2-1 or case 2-1-1 or case 2-2-1) the time elapsed between receiving L1 signaling and CHO execution being started or triggered (or satisfying at least one of the normal CHO execution event configured for the candidate cell and the NES-specific CHO execution event, or satisfying two normal CHO execution events configured for the candidate cell or satisfying at least one of two NES-specific CHO execution events configured for the candidate cell).

[0403] (7) (For example, for case 1-1-1 or case 1-2-1 or case 2-1-1 or case 2-2-1) the time elapsed between receiving the L1 signaling and receiving the CHO configuration of the NES.

[0404] (8) (For example, for case 1-1-1 or case 1-2-1 or case 2-1-1 or case 2-2-1) the event configured for the target cell (e.g., traditional or normal CHO execution event or NES specific CHO execution event) is satisfied first.

[0405] (9) (For example, for case 1-1-1 or case 1-2-1 or case 2-1-1 or case 2-2-1) The next event that is configured for the target cell (e.g., a traditional or normal CHO execution event or an NES-specific CHO execution event) is satisfied (if it exists).

[0406] (10) (For example, for case 1-1-1 or case 1-2-1 or case 2-1-1 or case 2-2-1) the duration between when the conventional or normal CHO execution event configured for the target cell is satisfied and when the NES-specific CHO execution event configured for the target cell is satisfied, if both events are satisfied.

[0407] For case 1-1-1, based on the successful report for NES CHO (such as SHR or other named reports or newly introduced reports) or information related to a successful NES-specific CHO or information related to a successful CHO for NES, the target node or the target node's CU or the source node or the source node's CU shall perform a near-failure cause analysis.

[0408] In an embodiment, the source node or its CU may decide to optimize or relax CHO execution conditions (e.g., including conventional or normal CHO execution events and / or NES-specific CHO execution events). Alternatively, the source node or its CU may be instructed to optimize or relax CHO execution conditions (e.g., including conventional or normal CHO execution events and / or NES-specific CHO execution events). Then, the source node or its CU will optimize or relax the CHO execution conditions (e.g., including conventional or normal CHO execution events and / or NES-specific CHO execution events).

[0409] In another embodiment, the source node may determine that the L1 signaling is delayed, or the source node may be indicated that the L1 signaling is delayed. Then, the source node may shift to an earlier timing to transmit the L1 signaling (e.g., to activate cell DTX or DRX or cell hibernation in advance).

[0410] In an additional embodiment, the source node's CU can determine or be indicated that the L1 signaling is delayed. Then, the source node's CU can indicate the delayed L1 signaling to the source node's DU; and then, the source node's DU can shift to an earlier timing to transmit the L1 signaling (e.g., to activate cell DTX or DRX or cell dormancy in advance).

[0411] For case 1-2-1, based on the successful report for NES CHO (such as SHR or other named reports or newly introduced reports) or information related to a successful NES-specific CHO or information related to a successful CHO for NES, the target node or the target node's CU or the source node or the source node's CU shall perform a near-failure cause analysis.

[0412] In an embodiment, the source node or its CU may decide to optimize or relax CHO execution conditions (e.g., including conventional or normal CHO execution events and / or NES-specific CHO execution events), or the source node or its CU may be instructed to optimize or relax CHO execution conditions (e.g., including conventional or normal CHO execution events and / or NES-specific CHO execution events). Then, the source node or its CU will optimize or relax the CHO execution conditions (e.g., including conventional or normal CHO execution events and / or NES-specific CHO execution events).

[0413] In another embodiment, the source node may determine that the L1 signaling arrived early, or the source node may be indicated that the L1 signaling arrived early. Then, the source node may delay the timing of transmitting the L1 signaling (e.g., postpone activation of cell DTX or DRX or cell shutdown).

[0414] In an additional embodiment, the source node's CU may determine or be indicated that the L1 signaling arrived early. The source node's CU may then indicate the early arrival of the L1 signaling to the source node's DU. The source node's DU may then delay the timing of transmitting the L1 signaling (e.g., postpone cell activation DTX or DRX or cell shutdown).

[0415] For case 2-1-1, based on the successful report for NES CHO (e.g., SHR or other named reports or newly introduced reports) or information related to a successful NES-specific CHO or information related to a successful CHO for NES, the target node or the target node's CU or the source node or the source node's CU shall perform a near-failure cause analysis.

[0416] In an embodiment, the source node or its CU may decide to optimize or tighten at least one CHO execution condition (e.g., including conventional or normal CHO execution events and / or NES-specific CHO execution events), or the source node or its CU may be instructed to optimize or tighten at least one CHO execution condition (e.g., including conventional or normal CHO execution events and / or NES-specific CHO execution events). Then, the source node or its CU will optimize or tighten the CHO execution condition (e.g., including conventional or normal CHO execution events and / or NES-specific CHO execution events).

[0417] In another embodiment, the source node may determine that the L1 signaling is delayed, or the source node may be indicated that the L1 signaling is delayed. Then, the source node may shift to an earlier timing to transmit the L1 signaling (e.g., to activate cell DTX or DRX or cell hibernation in advance).

[0418] In an additional embodiment, the source node's CU can determine or be indicated that the L1 signaling is delayed. Then, the source node's CU can indicate the delayed L1 signaling to the source node's DU. Next, the source node's DU can shift to an earlier timing to transmit the L1 signaling (e.g., to prematurely activate cell DTX or DRX or cell hibernation).

[0419] Example 2-2 (Information from the RLF report)

[0420] As illustrated in Example 1, failure scenarios may occur (e.g., scenario 1-1-2, scenario 1-1-3, scenario 1-2-2, scenario 1-2-3, scenario 2-1-2, or scenario 2-2-2). Example 2-2 provides a solution regarding failure reports for NES CHOs stored or reported by the UE (e.g., failure reports may be RLF reports or other named reports or newly introduced reports) or information related to failed NES-specific CHOs or information related to failed CHOs for NES.

[0421] In Example 2-2, the failure report for the NES CHO (e.g., the failure report may be an RLF report or other named reports or newly introduced reports) or information related to the failed NES-specific CHO or information related to the failed CHO for NES may include at least one of the following:

[0422] (1) (For example, for cases 1-1-2, 1-1-3, 1-2-2, or 1-2-3) an indication that the candidate cell does not meet the CHO execution conditions when a lower-layer message (e.g., L1 signaling) is received or during a predefined finite period after receiving the L1 signaling. For example, the L1 signaling is DCI format 2_9, which indicates that a specific NES CHO execution condition is enabled or disabled or used to enable or disable the CHO execution condition, or the L1 signaling contains an indication from the lower layer to the UE that the source cell is entering NES mode (e.g., the cell DTX or DRX is deactivated or the source cell is turned off).

[0423] (2) (e.g., for case 2-1-2 or case 2-2-2) indicates that the CHO execution conditions are met when L1 signaling is received or during a predefined finite period after L1 signaling is received.

[0424] (3) An indication of whether the CHO execution conditions or NES-specific CHO execution events are met before receiving the L1 signaling, for example:

[0425] a) For example, for cases 1-1-2, 1-1-3, or 2-1-2, the UE may store or report an indication that a CHO execution condition or an NES-specific CHO execution event was met before receiving L1 signaling. Furthermore, for such met CHO execution conditions or NES-specific CHO execution events, the UE may store or report at least one of the following:

[0426] i. Information about the cell whose CHO execution conditions or NES-specific CHO execution events are met (e.g., cell information may include cell ID, which may include PCI+ carrier frequency information (e.g., ARFCN) and / or CGI-info (e.g., PLMN identifier, cell identifier, and TrackingAreaCode)).

[0427] ii. The cell's first-met events (e.g., the first-met events could be traditional or normal CHO execution events or NES-specific CHO execution events),

[0428] iii. Secondary satisfied events of the cell (e.g., secondary satisfied events could be traditional or normal CHO execution events or NES-specific CHO execution events) (if any), and

[0429] iv. The duration between when the cell's conventional or normal CHO execution event is satisfied and when the cell's NES-specific CHO execution event is satisfied, if both events are satisfied.

[0430] b) For another instance, for case 1-2-2 or case 1-2-3 or case 2-2-2, the UE may store or report an indication that the CHO execution conditions (e.g., NES-specific CHO execution events or traditional or normal CHO execution events) were not met before the L1 signaling was received.

[0431] (4) (For example, for cases 1-1-2, 1-1-3, 1-2-2, 1-2-3, 2-1-2 or 2-2-2) the measurement results (e.g., source cell, candidate cell or neighboring cell) after or at the time of receiving L1 signaling.

[0432] (5) (For example, for cases 1-1-2, 1-1-3, 1-2-2, 1-2-3, 2-1-2 or 2-2-2) the time elapsed between receiving L1 signaling and CHO execution being initiated or triggered (or satisfying at least one of the normal CHO execution event configured for the candidate cell and the NES-specific CHO execution event, or satisfying two normal CHO execution events configured for the candidate cell or satisfying at least one of two NES-specific CHO execution events configured for the candidate cell).

[0433] (6) (For example, for cases 1-1-2, 1-1-3, 1-2-2, 1-2-3, 2-1-2 or 2-2-2) the time elapsed between receiving the L1 signaling and receiving the CHO configuration of the NES;

[0434] (7) (For example, for cases 1-1-2, 1-1-3, 1-2-2, 1-2-3, 2-1-2 or 2-2-2) the event configured for the target cell (e.g., a traditional or normal CHO execution event or an NES-specific CHO execution event) is satisfied first.

[0435] (8) (For example, for cases 1-1-2, 1-1-3, 1-2-2, 1-2-3, 2-1-2 or 2-2-2) the next event that is configured for the target cell (e.g., a traditional or normal CHO execution event or an NES-specific CHO execution event) is satisfied (if it exists).

[0436] (9) (For example, for cases 1-1-2, 1-1-3, 1-2-2, 1-2-3, 2-1-2 or 2-2-2) the duration between when the conventional or normal CHO execution event configured for the target cell is satisfied and when the NES-specific CHO execution event configured for the target cell is satisfied, if both events are satisfied.

[0437] Example 3 (UHI or MHI for NES)

[0438] Example 3 provides an enhanced solution for UE History Information (UHI) or Mobility History Information (MHI) when the NES mechanism is applied. UHI or MHI (which contains information on cell DTX activation or deactivation and / or cell DRX activation or deactivation and / or cell open and / or cell closed) will help the network understand the actual state of the cells and further optimize the network configuration.

[0439] Example 3-1 (Enhanced UE Historical Information on the UE Side)

[0440] Example 3-1 provides an enhancement to UE history information at the UE side. In Example 3-1, the UE may, for example, store or report cell DTX activation or deactivation information and / or cell DRX activation or deactivation information of at least one cell in or via the MHI. For example, for any cell within at least one cell, the cell may use an NES solution (e.g., the cell may activate or deactivate cell DTX / DRX, or the cell may deactivate or activate cell DTX / DRX).

[0441] For example, for a cell using an NES solution, the cell's DTX activation information includes:

[0442] (1) Cell identifier (ID) (e.g., PCI+carrier frequency information (e.g., ARFCN) and / or CGI-info (e.g., PLMN identifier, cell identifier and TrackingAreaCode));

[0443] (2) Cell DTX activation time (e.g., cell DTX activity duration or the duration during which cell DTX is activated); and / or

[0444] (3) Percentage of cell DTX activation time (e.g., the percentage of cell DTX activity duration or the percentage of cell DTX activation duration).

[0445] For example, for a cell using an NES solution, the cell DTX deactivation information includes:

[0446] (1) Cell identifier (ID) (e.g., PCI+carrier frequency information (e.g., ARFCN) and / or CGI-info (e.g., PLMN identifier, cell identifier and TrackingAreaCode));

[0447] (2) Cell DTX deactivation time (e.g., cell DTX deactivation duration or the duration during which the cell's DTX is deactivated); and / or

[0448] (3) Percentage of cell DTX deactivation time (e.g., the percentage of cell DTX deactivation duration or the percentage of cell DTX deactivation duration).

[0449] For example, for a cell using the NES solution, the cell's DRX activation information includes:

[0450] (1) Cell identifier (ID) (e.g., PCI+carrier frequency information (e.g., ARFCN) and / or CGI-info (e.g., PLMN identifier, cell identifier and TrackingAreaCode));

[0451] (2) Cell DRX activation time (e.g., cell DRX activity duration or the duration for which cell DRX is activated); and / or

[0452] (3) Percentage of cell DRX activation time (e.g., the percentage of cell DRX activity duration or the percentage of cell DRX activation duration).

[0453] For example, for a cell using the NES solution, the cell DRX deactivation information includes:

[0454] (1) Cell identifier (ID) (e.g., PCI+carrier frequency information (e.g., ARFCN) and / or CGI-info (e.g., PLMN identifier, cell identifier and TrackingAreaCode));

[0455] (2) Cell DRX deactivation time (e.g., cell DRX deactivation duration or the duration during which the cell's DRX is deactivated); and / or

[0456] (3) Percentage of cell DRX deactivation time (e.g., the percentage of cell DRX deactivation duration or the percentage of cell DRX deactivation duration).

[0457] Example 3-2 (Enhanced UE Historical Information at the Network Side)

[0458] Example 3-2 provides an enhancement to UE historical information at the network side. The network can store or record information on cell DTX activation or deactivation and / or cell DRX activation or deactivation for at least one cell. For example, for any cell within at least one cell, the cell can use an NES solution (e.g., the cell can activate or deactivate cell DTX / DRX, or the cell can deactivate or activate cell DTX / DRX). UE historical information may include information on cell DTX activation or deactivation and / or cell DRX activation or deactivation.

[0459] For example, for a cell using an NES solution, the cell's DTX activation information includes:

[0460] (1) Cell identifier (ID) (e.g., PCI+carrier frequency information (e.g., ARFCN) and / or CGI-info (e.g., PLMN identifier, cell identifier and TrackingAreaCode));

[0461] (2) Cell DTX activation time (e.g., cell DTX activity duration or the duration during which cell DTX is activated); and / or

[0462] (3) Percentage of cell DTX activation time (e.g., the percentage of cell DTX activity duration or the percentage of cell DTX activation duration).

[0463] For example, for a cell using an NES solution, the cell DTX deactivation information includes:

[0464] (1) Cell identifier (ID) (e.g., PCI+carrier frequency information (e.g., ARFCN) and / or CGI-info (e.g., PLMN identifier, cell identifier and TrackingAreaCode));

[0465] (2) Cell DTX deactivation time (e.g., cell DTX deactivation duration or the duration during which the cell's DTX is deactivated); and / or

[0466] (3) Percentage of cell DTX deactivation time (e.g., the percentage of cell DTX deactivation duration or the percentage of cell DTX deactivation duration).

[0467] For example, for a cell using the NES solution, the cell's DRX activation information includes:

[0468] (1) Cell identifier (ID) (e.g., PCI+carrier frequency information (e.g., ARFCN) and / or CGI-info (e.g., PLMN identifier, cell identifier and TrackingAreaCode));

[0469] (2) Cell DRX activation time (e.g., cell DRX activity duration or the duration for which cell DRX is activated); and / or

[0470] (3) Percentage of cell DRX activation time (e.g., the percentage of cell DRX activity duration or the percentage of cell DRX activation duration).

[0471] For example, for a cell using the NES solution, the cell DRX deactivation information includes:

[0472] (1) Cell identifier (ID) (e.g., PCI+carrier frequency information (e.g., ARFCN) and / or CGI-info (e.g., PLMN identifier, cell identifier and TrackingAreaCode));

[0473] (2) Cell DRX deactivation time (e.g., cell DRX deactivation duration or the duration during which the cell's DRX is deactivated); and / or

[0474] (3) Percentage of cell DRX deactivation time (e.g., the percentage of cell DRX deactivation duration or the percentage of cell DRX deactivation duration).

[0475] Based on Example 3-1, after the network node receives UE historical information (e.g., MHI) from the UE, for example after receiving at least one of "cell DTX activation information, cell DTX deactivation information, cell DRX activation information, and cell DRX deactivation information" from the UE, in the case of CU-DU split architecture, at least one of "cell DTX activation information, cell DTX deactivation information, cell DRX activation information, and cell DRX deactivation information" can be transmitted between the CU of the network node and at least one DU of the network node.

[0476] In Example 3-2, under the CU-DU split architecture, in one instance, if a DU stores or records or collects at least one of "cell DTX activation information, cell DTX deactivation information, cell DRX activation information, and cell DRX deactivation information", then the DU can transmit at least one of the "cell DTX activation information, cell DTX deactivation information, cell DRX activation information, and cell DRX deactivation information" to the DU that manages or controls it or the corresponding CU associated with the DU; in another instance, if a CU stores or records or collects at least one of "cell DTX activation information, cell DTX deactivation information, cell DRX activation information, and cell DRX deactivation information", then the CU can transmit at least one of the "cell DTX activation information, cell DTX deactivation information, cell DRX activation information, and cell DRX deactivation information" to at least one corresponding DU that is managed or controlled by the CU or associated with the CU.

[0477] The description herein is provided to enable those skilled in the art to make or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be given the broadest scope consistent with the principles and novel features disclosed herein.

Claims

1. A user equipment (UE) for wireless communication, comprising: At least one memory; and At least one processor coupled to the at least one memory and configured to cause the UE to: A first configuration for obtaining first information related to a successful handover in the case of the UE storing or reporting information related to the application network energy-saving NES solution; and Store the first information.

2. The UE according to claim 1, wherein in order to obtain the first configuration, the processor of the UE is configured to: The first configuration is obtained through pre-configuration; or Obtain the first configuration from the network node.

3. The UE of claim 1, wherein the first configuration includes second information indicating at least one of the following: When a lower-level message is received, the switching execution condition is not met, wherein the lower-level message contains an NES mode indication; The switching execution condition is not met during the period following the receipt of the lower-level message; or The NES-specific handover execution event configured for the cell is satisfied, but the normal handover execution event configured for the cell is not satisfied.

4. The UE according to claim 1 or claim 3, wherein the first configuration comprises one or more thresholds, and the one or more thresholds comprise at least one of the following: At least one first threshold, which is related to the elapsed time between receiving the lower-layer message and receiving the configuration regarding the handover when the NES solution is applied; At least one second threshold, which is related to the time elapsed between receiving the lower-level message and initiating the switching execution; At least one third threshold, which is related to the elapsed time between when a first handover execution event configured for the cell is satisfied and when a second handover execution event configured for the cell is satisfied; At least one timer T310 related threshold; At least one timer T312 related threshold; or At least one timer T304 related threshold.

5. The UE according to claim 3 or claim 4, wherein the first information is stored based on at least one of the following: At least one triggering condition associated with the second information is met; At least one triggering condition associated with the one or more thresholds is met; or The switchover was completed successfully.

6. The UE of claim 5, wherein the satisfaction of the at least one triggering condition associated with the second information includes at least one of the following: The switching execution condition is not met when the lower-level message is received. The switching execution condition is not met during the time period following the receipt of the lower-level message; or The NES-specific handover execution event configured for the cell is satisfied, but the normal handover execution event configured for the cell is not satisfied.

7. The UE of claim 5, wherein the satisfaction of the at least one triggering condition associated with the one or more thresholds includes at least one of the following: The duration between receiving the lower-layer message and receiving the configuration regarding the handover is greater than at least one first threshold; The duration between receiving the lower-level message and initiating the switching execution is greater than at least one second threshold; The duration between the time when the first handover execution event configured for the target cell is satisfied and the time when the second handover execution event configured for the target cell is satisfied is greater than the at least one third threshold. When the lower-level message is received, the ratio between the elapsed runtime value of timer T310 and the configuration value of timer T310 is greater than the threshold related to at least one timer T310; When the lower-level message is received, the ratio between the elapsed runtime value of timer T312 and the configuration value of timer T312 is greater than the threshold related to at least one timer T312; or The ratio between the elapsed runtime value of timer T304 and the configuration value of timer T304 is greater than the threshold associated with at least one timer T304.

8. The UE of claim 1, wherein the first information comprises at least one of the following: The information indicates that no switching execution conditions are met when a lower-level message is received or during a period after the lower-level message is received, wherein the lower-level message contains an NES mode indication; Information indicating that at least one switching execution condition is met when the lower-level message is received or during the time period following the receipt of the lower-level message; Third information indicating whether a specific NES handover execution event or handover execution condition is met before the lower-level message is received; The fourth piece of information indicates whether the normal switchover execution event is satisfied before the lower-level message is received; The measurement results of the source cell when the lower-layer message is received; The measurement results of the target cell when the lower-layer message is received; When the lower-layer message is received, the measurement results of one or more candidate cells are received; When the lower-layer message is received, it represents the measurement results of one or more neighboring cells; The reason value used to store or report the first information; The time elapsed between receiving the lower-level message and receiving the configuration regarding the handover; The time elapsed between receiving the lower-level message and initiating the switchover execution; The handover execution event configured for the target cell must be satisfied first; Secondly, the handover execution event configured for the target cell must be satisfied; or The time elapsed between when the first handover execution event configured for the target cell is satisfied and when the second handover execution event configured for the target cell is satisfied.

9. The UE of claim 8, wherein the first information further comprises at least one of the following: The NES-specific handover execution event is satisfied before the lower-layer message is received; The switching execution condition is met before the lower-level message is received; Information about the first cell, wherein the NES-specific handover execution event or the handover execution condition is satisfied before the lower-layer message is received; The handover execution event that is satisfied first in the first cell; The second handover execution event satisfied by the first cell; or The time elapsed between when the first handover execution event of the first cell is satisfied and when the second handover execution event of the first cell is satisfied.

10. The UE of claim 8, wherein the cause value indicates at least one of the following: The duration between receiving the lower-level message and initiating the switching execution is greater than a threshold. The duration between receiving the lower-layer message and receiving the configuration regarding the handover is greater than a threshold; The switching execution condition is not met when the lower-level message is received or during the period following the receipt of the lower-level message; No switching execution conditions were met during the period following the receipt of the lower-level message; The handover execution event configured for the cell meets the NES-specific handover execution event requirements, but does not meet the normal handover execution event requirements configured for the cell. The duration between when the first handover execution event of the cell is satisfied and when the second handover execution event of the cell is satisfied is greater than a threshold. When the lower-level message is received, the ratio between the elapsed runtime value of timer T310 and the configured value of timer T310 is greater than a threshold. When the lower-level message is received, the ratio between the elapsed runtime value of timer T312 and the configured value of timer T312 is greater than a threshold; or The ratio between the elapsed runtime value of timer T304 and the configured value of timer T304 is greater than a threshold.

11. The UE of claim 1, wherein the processor is configured to cause the UE to transmit optional UE capability information for supporting the storage and reporting of the first information.

12. A user equipment (UE) for wireless communication, comprising: At least one memory; and At least one processor coupled to the at least one memory and configured to cause the UE to: In response to a connection failure, information related to the connection failure is stored in the handover procedure for the application network energy-saving NES solution.

13. The UE of claim 12, wherein the information related to the connection failure includes at least one of the following: Information indicating that the switching execution conditions are not met when a lower-level message is received or during a period after the lower-level message is received, wherein the lower-level message contains an NES mode indication; Information indicating that at least one switching execution condition is met when the lower-level message is received or during the time period following the receipt of the lower-level message; Information indicating whether a specific NES handover execution event or handover execution condition is met before the lower-level message is received; Information indicating whether a normal handover execution event was satisfied before the lower-level message was received; The measurement results of the source cell when the lower-layer message is received; The measurement results of the target cell when the lower-layer message is received; When the lower-layer message is received, the measurement results of one or more candidate cells are received; When the lower-layer message is received, it represents the measurement results of one or more neighboring cells; The time elapsed between receiving the lower-level message and receiving the switching configuration; The time elapsed between receiving the lower-level message and initiating the switchover execution; The handover execution event configured for the target cell must be satisfied first; Secondly, the handover execution event configured for the target cell must be satisfied; or The time elapsed between when the first handover execution event configured for the target cell is satisfied and when the second handover execution event configured for the target cell is satisfied.

14. The UE of claim 13, wherein the information related to the connection failure further comprises at least one of the following: The NES-specific handover execution event is satisfied before the lower-layer message is received; The switching execution condition is met before the lower-level message is received; The information of the cell, wherein the NES-specific handover execution event or the handover execution condition is satisfied before the lower-layer message is received; The handover execution event that must be satisfied in the cell; The cell's next satisfying handover execution event; or The time elapsed between when the first handover execution event of the cell is satisfied and when the second handover execution event of the cell is satisfied.

15. A user equipment (UE) for wireless communication, comprising: At least one memory; and At least one processor coupled to the at least one memory and configured to enable the UE to store or report mobility history information regarding activation or deactivation in the case of an application network energy-saving NES solution.

16. The UE of claim 15, wherein the mobility history information comprises at least one of the following: The first piece of information is associated with cell discontinuous transmission DTX activation of at least one cell. The second piece of information is associated with the deactivation of the cell DTX of at least one cell. The third piece of information is associated with DRX activation for cell discontinuous reception in at least one cell; or The fourth piece of information is associated with the deactivation of cell DRX in at least one cell.

17. The UE of claim 16, wherein the first information comprises at least one of the following: The cell identifier of the at least one cell; The time when the cell DTX of at least one cell is activated; The duration for which the cell DTX of at least one cell is activated; or The percentage of time during which the cell DTX of at least one cell is activated. The second information includes at least one of the following: The cell identifier of the at least one cell; The time during which the cell DTX of at least one cell is deactivated; The duration for which the cell DTX of at least one cell is deactivated; or The percentage of time during which the cell DTX of at least one cell is deactivated. The third information includes at least one of the following: The cell identifier of the at least one cell; The time when the cell DRX of at least one cell is activated; The duration for which the cell DRX of at least one cell is activated; or The percentage of time during which the cell DRX of the at least one cell is activated, and The fourth information includes at least one of the following: The cell identifier of the at least one cell; The time when the cell DRX of at least one cell is deactivated; The duration for which the cell DRX of at least one cell is deactivated; or The percentage of time during which the cell DRX of at least one cell is deactivated.

18. A network device NE for wireless communication, comprising: At least one memory; and At least one processor coupled to the at least one memory and configured to store user equipment (UE) history information regarding activation or deactivation in the context of an application network energy-saving NES solution.

19. The NE of claim 18, wherein the UE historical information comprises at least one of the following: The first piece of information is associated with cell discontinuous transmission DTX activation of at least one cell. The second piece of information is associated with the deactivation of the cell DTX of at least one cell. The third piece of information is associated with DRX activation for cell discontinuous reception in at least one cell; or The fourth piece of information is associated with the deactivation of cell DRX in at least one cell.

20. The NE of claim 19, wherein the first information comprises at least one of the following: The cell identifier of the at least one cell; The time when the cell DTX of at least one cell is activated; The duration for which the cell DTX of at least one cell is activated; or The percentage of time during which the cell DTX of at least one cell is activated. The second information includes at least one of the following: The cell identifier of the at least one cell; The time during which the cell DTX of at least one cell is deactivated; The duration for which the cell DTX of at least one cell is deactivated; or The percentage of time during which the cell DTX of at least one cell is deactivated. The third information includes at least one of the following: The cell identifier of the at least one cell; The time when the cell DRX of at least one cell is activated; The duration for which the cell DRX of at least one cell is activated; or The percentage of time during which the cell DRX of the at least one cell is activated, and The fourth information includes at least one of the following: The cell identifier of the at least one cell; The time when the cell DRX of at least one cell is deactivated; The duration for which the cell DRX of at least one cell is deactivated; or The percentage of time during which the cell DRX of at least one cell is deactivated.

Images