Methods and apparatuses for mobile robustness optimization (MRO) mechanisms for non-terrestrial networks (NTN)

Abstract

Various aspects of the present disclosure relate to methods and apparatuses for mobile robustness optimization (MRO) mechanisms for non-terrestrial networks (NTNs). According to embodiments of the present 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 cause the UE to obtain a configuration for the UE to store or report information related to a mobility procedure in a non-terrestrial network (NTN) and store or report the information related to the mobility in the (NTN).

Description

Technical Field

[0001] This disclosure relates to wireless communications, and more specifically, to methods and apparatus for mobility robustness optimization (MRO) mechanisms for non-terrestrial networks (NTNs). 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 to enable the UE to: obtain a first configuration for the UE to store or report first information related to mobility procedures in a non-terrestrial network (NTN); and store or report 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 receive the first configuration from a network equipment (NE).

[0006] 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 distance between the UE and the reference location of the source cell at the time of handover initiation; at least one second threshold related to the distance between the UE and the mobile reference location of the source cell at the time of handover initiation; at least one third threshold related to the distance between the UE and the reference location of the source cell at the time of successful handover; at least one fourth threshold related to the distance between the UE and the mobile reference location of the source cell at the time of successful handover; at least one fifth threshold related to the distance between the UE and the reference location of the target cell or candidate target cell at the time of handover initiation; at least one sixth threshold, It is related to the distance between the UE and the mobile reference position of the target cell or the candidate target cell when the handover is initiated; at least one seventh threshold, which is related to the distance between the UE and the reference position of the target cell or the candidate target cell when the handover is successful; at least one eighth threshold, which is related to the distance between the UE and the mobile reference position of the target cell or the candidate target cell when the handover is successful; at least one ninth threshold, which is related to the duration between when the location-based conditional handover (CHO) execution conditions configured for the cell are met and when the measurement-based CHO execution conditions configured for the cell are met; at least one timer T310 related threshold; at least one timer T312 related threshold; or at least one timer T304 related threshold.

[0007] 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 one or more thresholds; or successful completion of the handover.

[0008] 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 distance between the UE and the reference location of the source cell is shorter than the at least one first threshold when the handover is initiated; the distance between the UE and the moving reference location of the source cell is shorter than the at least one second threshold when the handover is initiated; the distance between the UE and the reference location of the source cell is shorter than the at least one third threshold when the handover is successful; the distance between the UE and the moving reference location of the source cell is shorter than the at least one fourth threshold when the handover is successful; the distance between the UE and the reference location of the target cell or the candidate target cell is greater than the at least one fifth threshold when the handover is initiated; the distance between the UE and the moving reference location of the target cell or the candidate target cell is greater than the at least one sixth threshold when the handover is successful; and the distance between the UE and the reference location of the target cell or the candidate target cell is greater than the at least one sixth threshold when the handover is successful. The distance between the UE and the reference location of the target cell or the candidate target cell is greater than at least one seventh threshold; the distance between the UE and the moving reference location of the target cell or the candidate target cell is greater than at least one eighth threshold when the handover is successful; the duration between when the location-based CHO execution condition configured for the cell is satisfied and when the measurement-based CHO execution condition configured for the cell is satisfied is greater than at least one ninth threshold; the ratio between the elapsed runtime value of timer T310 and the configured value of timer T310 when the handover is initiated is greater than 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 handover is initiated is greater than 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 at least one timer T304 related threshold.

[0009] In some implementations of the UE described herein, the first information includes at least one of the following: a set of cell types of at least one cell; the distance between the UE and the reference location of the source cell at the time of handover initiation; the distance between the UE and the moving reference location of the source cell at the time of handover initiation; the distance between the UE and the reference location of the source cell at the time of successful handover; the distance between the UE and the moving reference location of the source cell at the time of successful handover; the distance between the UE and the reference location of the target cell or candidate target cell at the time of handover initiation; the distance between the UE and the moving reference location of the target cell or candidate target cell at the time of handover initiation; the handover successful... The distance between the UE and the reference position of the target cell or the candidate target cell when the handover is successful; the distance between the UE and the moving reference position of the target cell or the candidate target cell when the handover is successful; the reason value used for the first information; at least one location-based conditional handover (CHO) execution condition; the type of the first CHO execution condition satisfied; the type of the second CHO execution condition satisfied; the distance between the UE and the reference position of the source cell when the location-based CHO execution condition is satisfied; the distance between the UE and the moving reference position of the source cell when the location-based CHO execution condition is satisfied; the distance between the UE and the reference position of the source cell when the location-based CHO execution condition is satisfied; the distance between the UE and the reference position of the source cell when the location-based CHO execution condition is satisfied. The distance between the UE and the reference position of the target cell or the candidate target cell; the distance between the UE and the moving reference position of the target cell or the candidate target cell when the location-based CHO execution condition is met; the distance between the UE and the reference position of the source cell when the measurement-based CHO execution condition is met; the distance between the UE and the moving reference position of the source cell when the measurement-based CHO execution condition is met; the distance between the UE and the reference position of the target cell or the candidate target cell when the measurement-based CHO execution condition is met; the distance between the UE and the reference position of the target cell or the candidate target cell when the measurement-based CHO execution condition is met. The distance between the moving reference positions of the candidate target cells; one or more measurement results of the source cell, the target cell, or the candidate target cell when the location-based CHO execution conditions are met; one or more measurement results of the source cell, the target cell, or the candidate target cell when the measurement-based CHO execution conditions are met; information indicating whether satellite switching with a resynchronization procedure is configured; the time elapsed between the time the location-based CHO execution conditions are met and the time elapsed between the time the measurement-based CHO execution conditions are met and the time elapsed between the time the measurement-based CHO execution conditions are met and the time elapsed between the time the measurement-based CHO execution conditions are met and the time elapsed between the time the measurement-based CHO execution conditions are met and the time elapsed between the time the measurement-based CHO execution conditions are met and the time elapsed between the time the measurement-based CHO execution conditions are met and the time elapsed between the time the measurement-based CHO execution conditions are met and the time elapsed between the time the measurement-based CHO execution conditions are met and the time elapsed between the time elapsed ...The duration between when the location-based CHO execution conditions configured for the cell are met and when the measurement-based CHO execution conditions configured for the cell are met; the elapsed time between when the measurement-based CHO execution conditions are met and when the handover is successful; the elapsed time between when the location-based CHO execution conditions are met and when the handover is successful; the triggering order of the location-based CHO execution conditions and the measurement-based CHO execution conditions; the radio link interruption since the handover was initiated or when the handover was successful; or information indicating that the radio link interruption was due to radio link quality issues or due to feeder link switching.

[0010] In some implementations of the UE described herein, the mobility procedure or the handover is performed in a normal handover procedure, a handover procedure without a random access channel (RACH), a dual active protocol stack (DAPS) handover procedure, a conditional handover (CHO) procedure, another different mobility mechanism, or a combination thereof.

[0011] 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 or reporting of the first information.

[0012] 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 a user equipment (UE) to store or report first information related to mobility procedures in a non-terrestrial network (NTN); and stores or reports the first information.

[0013] 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 mobility procedures in a non-terrestrial network (NTN); and storing or reporting the first information.

[0014] Some embodiments of this disclosure provide a network apparatus (NE). 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 related to mobility procedures in a non-terrestrial network (NTN).

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

[0016] 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 distance between the UE and the reference location of the source cell at the time of handover initiation; at least one second threshold related to the distance between the UE and the mobile reference location of the source cell at the time of handover initiation; at least one third threshold related to the distance between the UE and the reference location of the source cell at the time of successful handover; at least one fourth threshold related to the distance between the UE and the mobile reference location of the source cell at the time of successful handover; at least one fifth threshold related to the distance between the UE and the reference location of the target cell or candidate target cell at the time of handover initiation; at least one sixth threshold, It is related to the distance between the UE and the mobile reference position of the target cell or the candidate target cell when the handover is initiated; at least one seventh threshold, which is related to the distance between the UE and the reference position of the target cell or the candidate target cell when the handover is successful; at least one eighth threshold, which is related to the distance between the UE and the mobile reference position of the target cell or the candidate target cell when the handover is successful; at least one ninth threshold, which is related to the duration between when the location-based conditional handover (CHO) execution conditions configured for the cell are met and when the measurement-based CHO execution conditions configured for the cell are met; at least one timer T310 related threshold; at least one timer T312 related threshold; or at least one timer T304 related threshold.

[0017] In some implementations of the NE described herein, the first information includes at least one of the following: a set of cell types of at least one cell; the distance between the user equipment (UE) and the reference location of the source cell at the time of handover initiation; the distance between the UE and the mobile reference location of the source cell at the time of handover initiation; the distance between the UE and the reference location of the source cell at the time of successful handover; the distance between the UE and the mobile reference location of the source cell at the time of successful handover; the distance between the UE and the reference location of the target cell or candidate target cell at the time of handover initiation; the distance between the UE and the mobile reference location of the target cell or candidate target cell at the time of handover initiation; The distance between the UE and the reference position of the target cell or the candidate target cell when the handover is successful; the distance between the UE and the moving reference position of the target cell or the candidate target cell when the handover is successful; the reason value used for the first information; at least one location-based conditional handover (CHO) execution condition; the type of the first CHO execution condition satisfied; the type of the second CHO execution condition satisfied; the distance between the UE and the reference position of the source cell when the location-based CHO execution condition is satisfied; the distance between the UE and the moving reference position of the source cell when the location-based CHO execution condition is satisfied; when the location-based CHO execution condition is satisfied... The distance between the UE and the reference position of the target cell or the candidate target cell; the distance between the UE and the moving reference position of the target cell or the candidate target cell when the location-based CHO execution condition is met; the distance between the UE and the reference position of the source cell when the measurement-based CHO execution condition is met; the distance between the UE and the moving reference position of the source cell when the measurement-based CHO execution condition is met; the distance between the UE and the reference position of the target cell or the candidate target cell when the measurement-based CHO execution condition is met; the distance between the UE and the reference position of the target cell or the candidate target cell when the measurement-based CHO execution condition is met. The distance between the moving reference positions of the candidate target cells; one or more measurement results of the source cell, the target cell, or the candidate target cell when the location-based CHO execution conditions are met; one or more measurement results of the source cell, the target cell, or the candidate target cell when the measurement-based CHO execution conditions are met; information indicating whether satellite switching with a resynchronization procedure is configured; the time elapsed between the time the location-based CHO execution conditions are met and the time elapsed between the time the measurement-based CHO execution conditions are met and the time elapsed between the time the measurement-based CHO execution conditions are met and the time elapsed between the time the measurement-based CHO execution conditions are met and the time elapsed between the time the measurement-based CHO execution conditions are met and the time elapsed between the time the measurement-based CHO execution conditions are met and the time elapsed between the time the measurement-based CHO execution conditions are met and the time elapsed between the time the measurement-based CHO execution conditions are met and the time elapsed between the time the measurement-based CHO execution conditions are met and the time elapsed between the time the measurement-based CHO execution conditions are met and the time elapsed between the time elapsed ...The duration between when the location-based CHO execution conditions configured for the cell are met and when the measurement-based CHO execution conditions configured for the cell are met; the elapsed time between when the measurement-based CHO execution conditions are met and when the handover is successful; the elapsed time between when the location-based CHO execution conditions are met and when the handover is successful; the triggering order of the location-based CHO execution conditions and the measurement-based CHO execution conditions; the radio link interruption since the handover was initiated or when the handover was successful; or information indicating that the radio link interruption was due to radio link quality issues or due to feeder link switching.

[0018] In some implementations of the NE described herein, the mobility procedure or the handover is performed in a normal handover procedure, a handover procedure without a random access channel (RACH), a dual active protocol stack (DAPS) handover procedure, a conditional handover (CHO) procedure, another different mobility mechanism, or a combination thereof.

[0019] In some embodiments of the NE described herein, the processor of the NE is configured to receive optional UE capability information from the user equipment (UE) for storage or reporting to support the first information.

[0020] Some embodiments of this disclosure provide a processor for wireless communication, comprising: at least one controller coupled to at least one memory and configured to receive first information relating to mobility procedures in a non-terrestrial network (NTN).

[0021] Some embodiments of this disclosure provide a method performed by a network equipment (NE). The method includes receiving first information related to mobility procedures in a non-terrestrial network (NTN).

[0022] 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 in a mobility procedure in a non-terrestrial network (NTN), stores information related to the connection failure.

[0023] In some implementations of the UE described herein, the information related to the connection failure includes at least one of the following: a set of cell types of at least one cell; the distance between the UE and the reference location of the source cell at the time of handover initiation; the distance between the UE and the moving reference location of the source cell at the time of handover initiation; the distance between the UE and the reference location of the source cell at the time of connection failure; the distance between the UE and the moving reference location of the source cell at the time of connection failure; the distance between the UE and the reference location of the target cell or candidate target cell at the time of handover initiation; the distance between the UE and the moving reference location of the target cell or candidate target cell at the time of handover initiation; and the distance between the UE and the reference location of the target cell or candidate target cell at the time of connection failure. The distance between the UE and the moving reference position of the target cell or the candidate target cell when the connection failure occurs; at least one location-based conditional handover (CHO) execution condition; the type of the first satisfied CHO execution condition; or the type of the second satisfied CHO execution condition; information indicating whether satellite switching with a resynchronization procedure is configured; information indicating whether a measurement-based CHO execution condition configured for the cell is satisfied when the connection failure occurs; information indicating whether a location-based CHO execution condition configured for the cell is satisfied when the connection failure occurs; the triggering order of the location-based CHO execution condition and the measurement-based CHO execution condition; radio link interruption since the handover was initiated; or information indicating that the radio link interruption is due to radio link quality or due to feeder link handover.

[0024] In some implementations of the UE described herein, if the first satisfied CHO execution condition is the location-based CHO execution condition and if only the location-based CHO execution condition is satisfied before the connection failure occurs, then the information associated with the connection failure further includes at least one of the following: an identifier (ID) associated with a first cell whose location-based CHO execution condition is satisfied but whose measurement-based CHO execution condition is not satisfied; the distance between the UE and a reference location of the source cell when the location-based CHO execution condition is satisfied; the distance between the UE and a moving reference location of the source cell when the location-based CHO execution condition is satisfied; and the location-based CHO execution condition is satisfied. The distance between the UE and the reference position of the first cell or other candidate target cell when the location-based CHO execution condition is met; the distance between the UE and the moving reference position of the first cell or other candidate target cell when the location-based CHO execution condition is met; one or more measurement results of the source cell when the location-based CHO execution condition is met; one or more measurement results of the first cell or other candidate target cell when the location-based CHO execution condition is met; the time elapsed between when the location-based CHO execution condition is met and when the latest conditional reconfiguration is received; or the time elapsed between when the location-based CHO execution condition is met and when the connection failure occurs.

[0025] In some implementations of the UE described herein, if the first satisfied CHO execution condition is the measurement-based CHO execution condition and if only the measurement-based CHO execution condition is satisfied before the connection failure occurs, then the information associated with the connection failure further includes at least one of the following: an identifier (ID) associated with a second cell whose measurement-based CHO execution condition is satisfied but whose location-based CHO execution condition is not satisfied; the distance between the UE and the reference location of the source cell when the measurement-based CHO execution condition is satisfied; the distance between the UE and the moving reference location of the source cell when the measurement-based CHO execution condition is satisfied; and the information associated with the measurement-based CHO execution condition. The distance between the UE and the reference position of the second cell or other candidate target cell when the measurement-based CHO execution condition is met; the distance between the UE and the moving reference position of the second cell or other candidate target cell when the measurement-based CHO execution condition is met; one or more measurement results of the source cell when the measurement-based CHO execution condition is met; one or more measurement results of the second cell or other candidate target cell when the measurement-based CHO execution condition is met; the time elapsed between when the measurement-based CHO execution condition is met and when the latest conditional reconfiguration is received; or the time elapsed between when the measurement-based CHO execution condition is met and when the connection failure occurs.

[0026] In some implementations of the UE described herein, if both a location-based CHO execution condition and a measurement-based CHO execution condition are satisfied before the connection failure occurs, then: wherein the first satisfied CHO execution condition is one of the location-based CHO execution condition and the measurement-based CHO execution condition, wherein the second satisfied CHO execution condition is the other of the location-based CHO execution condition and the measurement-based CHO execution condition, and wherein the information associated with the connection failure further includes at least one of the following: its location-based CHO execution condition is satisfied and its measurement-based CHO execution condition is satisfied. The identifier (ID) of the third cell for which the CHO execution condition is met; the distance between the UE and the reference position of the source cell when the first CHO execution condition is met; the distance between the UE and the moving reference position of the source cell when the first CHO execution condition is met; the distance between the UE and the reference position of the third cell or other candidate target cells when the first CHO execution condition is met; the distance between the UE and the moving reference position of the third cell or other candidate target cells when the second CHO execution condition is met; the distance between the UE and the source cell when the first ... The distance between the reference positions of the source cell; the distance between the UE and the moving reference position of the source cell when the second CHO execution condition is met; the distance between the UE and the reference position of the third cell or other candidate target cells when the second CHO execution condition is met; the distance between the UE and the moving reference position of the third cell or other candidate target cells when the second CHO execution condition is met; one or more measurement results of the source cell when the first CHO execution condition is met; the distance between the third cell or other candidate target cells when the second CHO execution condition is met. One or more measurement results of the target cell; the time elapsed between when the first CHO execution condition is met and when the latest conditional reconfiguration is received; the time elapsed between when the second CHO execution condition is met and when the latest conditional reconfiguration is received; the time elapsed between when the first CHO execution condition is met and when the second CHO execution condition is met; the time elapsed between when the first CHO execution condition is met and when the connection failure occurs; or the time elapsed between when the second CHO execution condition is met and when the connection failure occurs.

[0027] In some implementations of the UE described herein, the mobility procedure is a normal handover procedure, a handover procedure without a random access channel (RACH), a dual active protocol stack (DAPS) handover procedure, a conditional handover (CHO) procedure, another different mobility mechanism, or a combination thereof.

[0028] In some implementations of the UE described herein, the processor of the UE is configured to report the information related to the connection failure, wherein the information related to the connection failure is reported via a radio link failure (RLF) report.

[0029] 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 occurring in a mobility procedure in a non-terrestrial network (NTN), stores information related to the connection failure.

[0030] Some embodiments of this disclosure provide a method performed by a user equipment (UE) for wireless communication. The method includes storing information related to a connection failure in a mobility procedure within a non-terrestrial network (NTN) in response to such a failure.

[0031] Some embodiments of this disclosure provide a network apparatus (NE). The NE includes: at least one memory; and at least one processor coupled to the at least one memory and configured to receive information related to connection failures in mobility procedures in a non-terrestrial network (NTN).

[0032] In some implementations of the NE described herein, the information associated with the connection failure includes at least one of the following: a set of cell types of at least one cell; the distance between the UE and the reference location of the source cell at the time of handover initiation; the distance between the UE and the moving reference location of the source cell at the time of handover initiation; the distance between the UE and the reference location of the source cell at the time of connection failure; the distance between the UE and the moving reference location of the source cell at the time of connection failure; the distance between the UE and the reference location of the target cell or candidate target cell at the time of handover initiation; the distance between the UE and the moving reference location of the target cell or candidate target cell at the time of handover initiation; and the distance between the UE and the reference location of the target cell or candidate target cell at the time of connection failure. The distance between the UE and the moving reference position of the target cell or the candidate target cell when the connection failure occurs; at least one location-based conditional handover (CHO) execution condition; the type of the first satisfied CHO execution condition; or the type of the second satisfied CHO execution condition; information indicating whether satellite switching with a resynchronization procedure is configured; information indicating whether a measurement-based CHO execution condition configured for the cell is satisfied when the connection failure occurs; information indicating whether a location-based CHO execution condition configured for the cell is satisfied when the connection failure occurs; the triggering order of the location-based CHO execution condition and the measurement-based CHO execution condition; radio link interruption since the handover was initiated; or information indicating that the radio link interruption is due to radio link quality or due to feeder link handover.

[0033] In some implementations of the NE described herein, if the first satisfied CHO execution condition is the location-based CHO execution condition and if only the location-based CHO execution condition is satisfied before the connection failure occurs, then the information associated with the connection failure further includes at least one of the following: an identifier (ID) associated with a first cell whose location-based CHO execution condition is satisfied but whose measurement-based CHO execution condition is not satisfied; the distance between the UE and the reference location of the source cell when the location-based CHO execution condition is satisfied; the distance between the UE and the moving reference location of the source cell when the location-based CHO execution condition is satisfied; and the location-based CHO execution condition is satisfied. The distance between the UE and the reference position of the first cell or other candidate target cell when the location-based CHO execution condition is met; the distance between the UE and the moving reference position of the first cell or other candidate target cell when the location-based CHO execution condition is met; one or more measurement results of the source cell when the location-based CHO execution condition is met; one or more measurement results of the first cell or other candidate target cell when the location-based CHO execution condition is met; the time elapsed between when the location-based CHO execution condition is met and when the latest conditional reconfiguration is received; or the time elapsed between when the location-based CHO execution condition is met and when the connection failure occurs.

[0034] In some implementations of the NE described herein, if the first satisfied CHO execution condition is the measurement-based CHO execution condition and if only the measurement-based CHO execution condition is satisfied before the connection failure occurs, then the information associated with the connection failure further includes at least one of the following: an identifier (ID) associated with a second cell whose measurement-based CHO execution condition is satisfied but whose location-based CHO execution condition is not satisfied; the distance between the UE and the reference location of the source cell when the measurement-based CHO execution condition is satisfied; the distance between the UE and the moving reference location of the source cell when the measurement-based CHO execution condition is satisfied; and the information associated with the measurement-based CHO execution condition. The distance between the UE and the reference position of the second cell or other candidate target cell when the measurement-based CHO execution condition is met; the distance between the UE and the moving reference position of the second cell or other candidate target cell when the measurement-based CHO execution condition is met; one or more measurement results of the source cell when the measurement-based CHO execution condition is met; one or more measurement results of the second cell or other candidate target cell when the measurement-based CHO execution condition is met; the time elapsed between when the measurement-based CHO execution condition is met and when the latest conditional reconfiguration is received; or the time elapsed between when the measurement-based CHO execution condition is met and when the connection failure occurs.

[0035] In some implementations of the NE described herein, if both a location-based CHO execution condition and a measurement-based CHO execution condition are satisfied before the connection failure occurs, then: wherein the first satisfied CHO execution condition is one of the location-based CHO execution condition and the measurement-based CHO execution condition, wherein the second satisfied CHO execution condition is the other of the location-based CHO execution condition and the measurement-based CHO execution condition, and wherein the information associated with the connection failure further includes at least one of the following: its location-based CHO execution condition is satisfied and its measurement-based CHO execution condition is satisfied. The identifier (ID) of the third cell for which the CHO execution condition is met; the distance between the UE and the reference position of the source cell when the first CHO execution condition is met; the distance between the UE and the moving reference position of the source cell when the first CHO execution condition is met; the distance between the UE and the reference position of the third cell or other candidate target cells when the first CHO execution condition is met; the distance between the UE and the moving reference position of the third cell or other candidate target cells when the second CHO execution condition is met; the distance between the UE and the source cell when the first ... The distance between the reference positions of the source cell; the distance between the UE and the moving reference position of the source cell when the second CHO execution condition is met; the distance between the UE and the reference position of the third cell or other candidate target cells when the second CHO execution condition is met; the distance between the UE and the moving reference position of the third cell or other candidate target cells when the second CHO execution condition is met; one or more measurement results of the source cell when the first CHO execution condition is met; the distance between the third cell or other candidate target cells when the second CHO execution condition is met. One or more measurement results of the target cell; the time elapsed between when the first CHO execution condition is met and when the latest conditional reconfiguration is received; the time elapsed between when the second CHO execution condition is met and when the latest conditional reconfiguration is received; the time elapsed between when the first CHO execution condition is met and when the second CHO execution condition is met; the time elapsed between when the first CHO execution condition is met and when the connection failure occurs; or the time elapsed between when the second CHO execution condition is met and when the connection failure occurs.

[0036] In some implementations of the NE described herein, the mobility procedure is a normal handover procedure, a handover procedure without a random access channel (RACH), a dual active protocol stack (DAPS) handover procedure, a conditional handover (CHO) procedure, another different mobility mechanism, or a combination thereof.

[0037] Some embodiments of this disclosure provide a processor for wireless communication, comprising: at least one controller coupled to at least one memory and configured to receive information related to connection failures in mobility procedures in a non-terrestrial network (NTN).

[0038] Some embodiments of this disclosure provide a method performed by a network equipment (NE). The method includes receiving information related to connection failures in mobility procedures within a non-terrestrial network (NTN).

[0039] 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 non-terrestrial network (NTN) related information; and transmit the NTN related information via random access (RA) reports.

[0040] In some implementations of the UE described herein, the NTN-related information includes at least one of the following: a set of cell types for at least one cell of the UE; epoch time; ephemeris information; scheduling offset for timing relationships modified for the NTN; scheduling offset provided by the network equipment (NE) when downlink and uplink frame timings are not aligned at the NE; polarization information for downlink transmissions on the serving link; polarization information for the uplink serving link; validity period configured by the NE for auxiliary information; common timing advance (TA) value; drift rate of the common TA value; change in the drift rate of the common TA value; information indicating whether the UE is configured to report the TA value; or information indicating whether event-triggered reporting of the TA value is supported.

[0041] 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 non-terrestrial network (NTN) related information; and transmits the NTN related information via random access (RA) reporting.

[0042] Some embodiments of this disclosure provide a method performed by a user equipment (UE) for wireless communication. The method includes: storing non-terrestrial network (NTN) related information; and transmitting the NTN related information via random access (RA) reporting.

[0043] Some embodiments of this disclosure provide a network apparatus (NE). 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 random access (RA) reports containing non-terrestrial network (NTN) related information.

[0044] In some implementations of the NE described herein, the NTN-related information includes at least one of the following: a set of cell types for at least one cell of the user equipment (UE); epoch time; ephemeris information; scheduling offset for timing relationships modified for the NTN; scheduling offset provided by the network equipment (NE) when downlink and uplink frame timings are misaligned at the NE; polarization information for downlink transmissions on the serving link; polarization information for the uplink serving link; validity period configured by the NE for auxiliary information; common timing advance (TA) value; drift rate of the common TA value; change in the drift rate of the common TA value; information indicating whether the UE is configured to report the TA value; or information indicating whether event-triggered reporting of the TA value is supported.

[0045] Some embodiments of this disclosure provide a processor for wireless communication, comprising: at least one controller coupled to at least one memory and configured to receive random access (RA) reports containing information related to non-terrestrial networks (NTNs).

[0046] Some embodiments of this disclosure provide a method performed by a network equipment (NE). The method includes: receiving a random access (RA) report containing information related to a non-terrestrial network (NTN).

[0047] 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: stores non-terrestrial network (NTN) related information of at least one cell of the UE; and transmits the NTN related information via mobility history information (MHI) or in the MHI.

[0048] In some implementations of the UE described herein, the NTN-related information includes at least one of the following: a set of cell identifiers (IDs) of the at least one cell; a set of cell types of the at least one cell; the duration for which the UE remains in at least one NTN cell; or the duration for which the UE remains in at least one terrestrial network (TN) cell.

[0049] 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 non-terrestrial network (NTN) related information of at least one cell of a UE; and transmits the NTN related information via mobility history information (MHI) or in the MHI.

[0050] Some embodiments of this disclosure provide a method performed by a user equipment (UE) for wireless communication. The method includes: storing non-terrestrial network (NTN) related information of at least one cell of the UE; and transmitting the NTN related information via mobility history information (MHI) or in the MHI.

[0051] Some embodiments of this disclosure provide a network equipment (NE). The NE includes: at least one memory; and at least one processor coupled to the at least one memory and configured to store user equipment (UE) historical information, wherein the UE historical information includes NTN-related information of at least one cell of the UE.

[0052] In some implementations of the NE described herein, the NTN-related information includes at least one of the following: a set of cell identifiers (IDs) of the at least one cell; a set of cell types of the at least one cell; the duration for which the UE remains in at least one NTN cell; or the duration for which the UE remains in at least one terrestrial network (TN) cell.

[0053] Some embodiments of this disclosure provide a processor for wireless communication, comprising: at least one controller coupled to at least one memory and configured to store user equipment (UE) historical information, wherein the UE historical information includes NTN-related information of at least one cell of the UE.

[0054] Some embodiments of this disclosure provide a method performed by a network equipment (NE). The method includes storing user equipment (UE) historical information, wherein the UE historical information includes NTN-related information for at least one cell of the UE. Attached Figure Description

[0055] Figure 1A Examples of non-terrestrial networks (NTNs) according to aspects of this disclosure are described.

[0056] Figure 1B An example illustrating the timing relationship between a co-located base station (BS) and an NTN gateway according to aspects of this disclosure.

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

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

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

[0060] Figure 4 Examples of network equipment (NE) 400 according to aspects of this disclosure are described.

[0061] Figures 5 to 7 A flowchart illustrating methods related to the MRO mechanism of NTN according to some aspects of this disclosure. Detailed Implementation

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

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

[0064] Figure 1A This section describes an example of NTN providing non-terrestrial NR access to a UE using an NTN payload and an NTN gateway. It depicts the service link between the NTN payload and the UE, and the feeder link between the NTN gateway and the NTN payload.

[0065] The NTN payload transparently forwards radio protocols received from the UE (via the serving link) to the NTN gateway (via the feeder link) and vice versa. The following connectivity is supported by the NTN payload:

[0066] - An NTN gateway can serve multiple NTN payloads;

[0067] - NTN payloads can be served by multiple NTN gateways.

[0068] The NTN payload can change the carrier frequency before retransmitting on the serving link and vice versa (correspondingly on the feeder link).

[0069] It supports three types of service links:

[0070] - Earth-fixed type: defined by a beam that continuously covers the same geographical area (e.g., the case of GSO satellites);

[0071] - Quasi-Earth-fixed type: defined by beams that cover a geographic area for a limited period of time and a different geographic area for another period of time (e.g., the case of NGSO satellites that generate steerable beams);

[0072] - Earth-mobile type: The beam pattern is defined by the area of ​​coverage that slides across the Earth's surface (e.g., the case of NGSO satellites that produce fixed or non-steerable beams).

[0073] For NGSO satellites, a BS (e.g., a gNB) can provide either a quasi-fixed or a mobile service link, while a BS operating with GSO satellites can provide a fixed service link. UEs supporting NTN can have Global Navigation Satellite System (GNSS) capabilities. In NTN, distance can refer to Euclidean distance.

[0074] Regarding timing and synchronization, the downlink (DL) and uplink (UL) synchronize at the uplink time reference point (RP) via N. TA,offset The given offset is used for frame alignment (see Clause 4.2 of 3GPP standard document TS 38.213).

[0075] To accommodate the propagation delay in NTN, several timing relationships are determined by common timing advance (common TA) and two offsets K. offset and k mac Enhancement:

[0076] - The common TA is the configured timing offset of the RTT between the RP and NTN payloads.

[0077] - K offset It is a configuration scheduling offset that needs to be greater than or equal to the sum of the service link RTT and the common TA.

[0078] - k mac It is the configuration offset that is approximately equal to the RTT between RP and gNB.

[0079] Scheduling offset K offset This is to allow the UE sufficient processing time between downlink reception and uplink transmission, see TS 38.213.

[0080] Offset k macApplications used to delay downlink configurations indicated by MAC CE commands on the PDSCH, see TS38.213, and for estimating UE-gNB RTT, see TS 38.321. This can be provided by the network when downlink and uplink frame timings are misaligned at the BS. mac It is also used in random access procedures to determine the start time of the RAR window / MsgB window after Msg1 / MsgA transmission (see TS 38.213).

[0081] Service Link RTT, Feeder Link RTT, RP, Common TA, k mac and T TA exist Figure 1B The explanation is as follows.

[0082] The network can be configured with HARQ operations as follows:

[0083] - For the downlink, HARQ feedback can be enabled or disabled per HARQ procedure (as specified in Clauses 5.3.2.2 and 5.7 of TS 38.321). Disabling HARQ feedback allows a HARQ procedure to be scheduled before one HARQ RTT has elapsed since the last scheduling.

[0084] - For the uplink, each HARQ procedure can be configured with a HARQ mode (i.e., HARQ mode A or HARQ mode B) (as specified in Clauses 5.4.3.1 and 5.7 of TS38.321). HARQ mode B allows a HARQ procedure to be scheduled before one HARQRTT has elapsed since the last scheduling.

[0085] For HARQ procedures configured with HARQ feedback enabled / disabled, the network implementation ensures the correct configuration of HARQ feedback for HARQ procedures used by the SPS (e.g., all enabled or all disabled). For HARQ procedures configured with HARQ modes, the network implementation ensures the correct configuration of HARQ modes for HARQ procedures used by the CG (e.g., full HARQ mode A or full HARQ mode B).

[0086] Regarding timing advance and frequency pre-compensation, for the serving cell, the network broadcasts valid ephemeris information and common TA parameters. The UE should have a valid GNSS location, ephemeris, and common TA before connecting to the NTN cell. To achieve synchronization, before and during connection to the NTN cell, the UE should calculate the RTT between the UE and the RP based on the GNSS location, ephemeris, and common TA parameters (see Clause 4.2 in TS 38.213), and automatically use T... TA The pre-compensated RTT between the UE and RP is described in Clause 4.3 of TS 38.211.

[0087] The UE should calculate the frequency Doppler shift of the serving link and automatically pre-compensate for it during uplink transmission by taking into account the UE's location and ephemeris. If the UE does not have a valid GNSS location and / or valid ephemeris and common TA, it should not transmit until it regains both. In connected mode, the UE should be able to continuously update timing advance and frequency pre-compensation. The UE can be configured to report timing advance during random access procedures or in connected mode. In connected mode, event-triggered reporting of timing advance is supported. While pre-compensation for transient Doppler shifts experienced on the serving link will be performed by the UE, management of Doppler shifts experienced on the feeder link and transponder frequency errors will be left to the network implementation scheme.

[0088] Generally, during movement between the NTN and the terrestrial network (TN), the UE does not need to be connected to both the NTN and the TN simultaneously. NTN-TN handover can refer to mobility in two directions: from NTN to TN (handover in) and from TN to NTN (handover out). The UE can support mobility between BSs operating with NTN payloads on different tracks (e.g., GSO, NGSO at different altitudes). Handover without RACH is supported in the NTN, as specified in TS 38.32.

[0089] Regarding Conditional Handover (CHO) in NTN, NTN supports the UE in executing the following additional triggering conditions for CHO to a candidate cell, as defined in TS 38.331:

[0090] - Event A4 based on RRM measurement;

[0091] - Time-based triggering conditions; and / or

[0092] - Location-based triggering conditions.

[0093] CondEvent D1 can be configured in the CHO procedure. CondEvent D1 is a location-based trigger condition or event, defined as follows: the distance between the UE and the reference location referenceLocation1 becomes greater than the configured threshold distanceThreshFromReference1, and the distance between the UE and the reference location referenceLocation2 becomes less than the configured threshold distanceThreshFromReference2. For details, please refer to TS 38.331.

[0094] CondEvent D2 can be configured in the CHO procedure. CondEvent D2 is a location-based trigger condition or event, defined as follows: the distance between the UE and the mobile reference location determined based on referenceLocation1 becomes greater than the configured threshold distanceThreshFromReference1, and the distance between the UE and the mobile reference location determined based on referenceLocation2 becomes less than the configured threshold distanceThreshFromReference2. For details, please refer to TS 38.331.

[0095] Time-based or location-based trigger conditions / events are always configured together with measurement-based trigger conditions (or radio link quality-based trigger conditions or events, such as CondEvent A3, CondEvent A4, or CondEvent A5), as defined in TS 38.331.

[0096] How the UE evaluates time-based or location-based triggering conditions and events based on RRM measurements depends on the UE's implementation scheme.

[0097] Location can be defined by the distance between the UE and a reference location. Time can be defined by the time interval between T1 and T2, where T1 is an absolute time value and T2 is the duration from T1. Time-based CHOs can be performed without RACH.

[0098] Regarding satellite switching with resynchronization, both hard and soft satellite switching in quasi-geocentric scenarios with the same SSB frequency and BS support satellite switching with resynchronization procedures. Satellite switching with resynchronization avoids L3 mobility of the UE in the cell by maintaining the same PCI over the geographical area covered by the quasi-geocentric beam. CHO can be configured simultaneously with satellite switching with resynchronization procedures. For soft satellite switching, the UE can begin synchronizing with the target satellite before the source satellite ceases to serve the cell. When the UE switches to the target satellite, the UE does not need to connect to the source satellite.

[0099] 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:

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

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

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

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

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

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

[0106] 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:

[0107] - Failure indicator on the Xn interface.

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

[0109] 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 the Xn interface or the uplink RAN ​​configuration transmission procedure on the NG. This may include an RLF report.

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

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

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

[0113] 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 the Xn interface or by relying on the uplink RAN ​​configuration delivery procedure and downlink RAN ​​configuration delivery procedure on the NG.

[0114] If the NG-RAN node from which the SHR is extracted from the UE is neither the source node nor the target 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 the Xn interface or by relying on the uplink RAN ​​configuration delivery procedure and the downlink RAN ​​configuration delivery procedure on the NG.

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

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

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

[0118] Generally, NTN is a new feature introduced in 3GPP Rel-17 and Rel-18. To optimize NTN-related configurations and improve mobility robustness, a MRO (Mobility Recovery Overhaul) mechanism for NTN will be supported. Currently, the details of the NTN MRO mechanism need to be addressed, including the following issues: In mobility procedures within NTN, near-failure successful handovers may occur, and the issue is how to enable the Network Equipment (NE) to optimize mobility-related configurations and / or mobility-related thresholds (e.g., reference signal received power (RSRP), reference signal received quality (RSRQ), or signal-to-interference-plus-noise ratio (SINR) thresholds used to trigger normal handover (i.e., normal legacy handover), or handover procedures without RACH, or DAPS handover, or location-related thresholds used to trigger CHO (e.g., distanceThreshFromReference1 or distanceThreshFromReference2)). The issues of how to trigger the storage or reporting of successful mobility reports in NTN (e.g., what are the NTN-specific triggering conditions for SHR) and what successful mobility-related information in NTN is stored or reported by the UE are yet to be resolved. In mobility procedures within the NTN, connection failures may occur. To enable the NE to understand MRO optimization failures, the question of what failure-related information in the NTN stored or reported by the UE is unresolved. For mobility in the UE's RRC_IDLE, RRC_INACTIVE, or RRC_CONNECTED states, the UE can execute a cell-to-cell RA procedure, and the RA report can be stored or reported by the UE. However, the question of what NTN-specific information is stored or reported by the UE in the RA report is unresolved. Furthermore, the question of what NTN-specific historical information is remains unresolved.

[0119] 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 success report in an NTN. In some embodiments, the UE records or stores or generates an NTN-specific trigger condition for the NTN success report and configures it to the UE. For example, the NTN-specific trigger condition may be a distance threshold relating to the distance between the UE and the "reference location or mobile reference location of the source cell (i.e., serving cell)" or the distance between the UE and the "reference location or mobile reference location of the target cell or candidate target cell" when a mobility RRC reconfiguration message is received, or when mobility is performed, or when mobility is successfully performed, or a time threshold relating to the duration between "when a location-based CHO execution condition or event is satisfied" and "when a measurement-based CHO execution condition or event is satisfied". Details of the NTN-specific trigger condition can be found in Embodiments 1-1 described below.

[0120] In some embodiments of this disclosure, when NTN-specific triggering conditions for the UE to record, store, or generate a successful NTN report are met, the UE records, stores, or generates an NTN success report to include NTN-specific information, such as the distance between the UE and the "reference location or mobile reference location of the source cell" or the distance between the UE and the "reference location or mobile reference location of the target cell or candidate target cell" when a mobility-specific mobility reconfiguration message is received, or when mobility execution is successful, or when a location-based CHO execution condition or event is met, or when a measurement-based CHO execution condition or event is met. Details of the NTN-specific mobility information (e.g., included in the success report) can be found in Embodiments 2-1 described below.

[0121] Several other embodiments of this disclosure provide a method for enhancing failure reporting in an NTN. In some embodiments, NTN-specific failure information may be stored or reported by the UE, for example, in an RLF report. For example, NTN-specific failure information may include the distance between the UE and the "reference location or mobile reference location of the source cell" or the distance between the UE and the "reference location or mobile reference location of the target cell or candidate target cell" when a mobility RRC reconfiguration message is received, when mobility is performed, when a connection failure occurs, when a location-based CHO execution condition or event is met, or when a measurement-based CHO execution condition or event is met. Details of NTN-specific failure information (e.g., included in an RLF report) can be found in Embodiments 2-2 described below.

[0122] In embodiments of this disclosure, mobility may be performed in a normal handover procedure (i.e., normal or Rel-15 conventional handover), a RACH-free handover procedure, a DAPS handover procedure (e.g., Rel-16 DAPS handover), a CHO procedure (e.g., Rel-16 CHO), another different mobility mechanism (e.g., L1 / L2 triggered mobility (LTM) cell handover or any new mobility technology or solution introduced by subsequent standards) or a combination thereof.

[0123] Some embodiments of this disclosure provide a method for enhancing RA reporting in an NTN. For example, NTN-specific information may be stored or reported by the UE in the RA report. Details of the NTN-specific information included in the RA report can be found in Embodiment 3 described below.

[0124] Some embodiments of this disclosure provide a method for enhancing UE History Information (UHI) or Mobility History Information (MHI) in an NTN. For example, a UE may store or report NTN-related information of at least one cell, for example, in or via the MHI. The network may store or record NTN-related information of at least one cell, for example, in or via the UHI. In some embodiments of this disclosure, the MHI or UHI may include cell type (e.g., the cell is an NTN cell or the cell is a TN cell), duration of UE stay in the NTN cell, or percentage of time, etc. Details of the MHI or UHI can be found in Embodiments 4-1 and 4-2 described below.

[0125] In some embodiments of this disclosure, for SON enhancements of NTN, new optional features are introduced in the SON report. These new optional features are optional, require no signaling, and cover SHR, RLF, or RA reports. For NTN's SHR, it is an optional feature without signaling. For NTN's RLF report, it is an optional feature without signaling. For NTN's RA report, it is an optional feature without signaling.

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

[0127] Figure 1 This 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).

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

[0129] NE 102 can provide a geographic coverage area, whereby 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0144] 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, such as memory 204 or another type of memory. Computer-readable media includes both non-transitory computer storage media and communication media, encompassing any media that facilitates the transfer of a computer program from one place to another. Non-transitory storage media may be any available media accessible by a general-purpose or special-purpose computer.

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

[0146] For example, processor 202 can support [the following] at UE 200 based on [the following] Figure 5 The publicly disclosed example demonstrates wireless communication. UE 200 can be configured to support: components for obtaining configurations for UE 200 to store or report mobility-related information in the NTN; and components for storing or reporting information related to mobility procedures in the NTN. For example, mobility-related information in the NTN is reported by UE 200 in SHR or other named reports or newly introduced reports.

[0147] 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 the mobility procedure of NTN. For example, the information related to connection failure is reported by UE 200 in an RLF report.

[0148] For example, processor 202 can support [the following] at UE 200 based on [the following] Figure 6 The publicly disclosed example performs wireless communication. UE 200 can be configured to support: components for storing NTN-related information; and components for transmitting NTN-related information, for example, via random access (RA) reports.

[0149] For example, processor 202 can support [the following] at UE 200 based on [the following] Figure 7 The disclosed example performs wireless communication. UE 200 can be configured to support: components for storing NTN-related information of at least one cell of the UE; and components for transmitting NTN-related information via Mobility History Information (MHI) or in MHI.

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

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

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

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

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

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

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

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

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

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

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

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

[0162] In some implementations, processor 300 may be configured to support the execution of [specific actions / functions]. Figure 5 The described components describe the operation of the UE. The processor 300 may be configured or operable to support: components for obtaining configurations for the processor 300 to store or report information related to mobility procedures in the NTN; and components for storing or reporting mobility-related information in the NTN. For example, mobility-related information in the NTN may be reported by the processor 300 in an SHR or other named report or newly introduced report.

[0163] In some implementations, processor 300 may be configured to support components for performing operations of the NE. Processor 300 may be configured or operable to support components for receiving, for example, information related to mobility procedures in the NTN via SHR or other named reports or newly introduced reports.

[0164] 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 a connection failure in response to a connection failure occurring in the mobility procedure within the NTN. For example, information related to the connection failure may be reported by processor 300 in an RLF report.

[0165] In some implementations, processor 300 may be configured to support components for performing operations of the NE. Processor 300 may be configured or operable to support components for receiving information related to connection failures in the mobility procedures of the NTN. For example, information related to connection failures is received via an RLF report.

[0166] In some implementations, processor 300 may be configured to support the execution of [specific actions / functions]. Figure 6 The described components are for the operation of the UE. The processor 300 may be configured or operable to support: components for storing NTN-related information; and components for transmitting NTN-related information via random access (RA) reports.

[0167] In some implementations, processor 300 may be configured to support components for performing operations of the NE. Processor 300 may be configured or operable to support components for receiving RA reports containing NTN-related information.

[0168] In some implementations, processor 300 may be configured to support the execution of [specific actions / functions]. Figure 7 The processor 300 is configured or operable to support: components for storing NTN-related information of at least one cell of the UE; and components for transmitting NTN-related information via Mobility History Information (MHI) or in MHI.

[0169] In some implementations, processor 300 may be configured to support components for performing operations of the NE. Processor 300 may be configured or operable to support components for storing UE historical information, wherein the UE historical information contains NTN-related information of at least one cell of the UE.

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

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

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

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

[0174] 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, such as memory 404 or another type of memory. Computer-readable media includes both non-transitory computer storage media and communication media, encompassing 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.

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

[0176] In some implementations, the NE 400 may be a network node and may be configured or operable to support components for receiving information related to mobility procedures in the NTN, for example, in SHR or other named or newly introduced reports.

[0177] In some implementations, the NE 400 may be a network node and may be configured or operable to support components for, for example, receiving information related to connection failures in mobility procedures within the NTN in an RLF report.

[0178] In some implementations, the NE 400 may be a network node and may be configured or operable to support components for receiving RA reports containing NTN-related information.

[0179] In some implementations, the NE 400 may be a network node and may be configured or operable to support components for storing UE historical information, wherein the UE historical information includes NTN-related information of at least one cell of the UE.

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

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

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

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

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

[0185] Figure 5 A flowchart illustrating methods related to NTN according to some aspects of this disclosure is provided. The operation of the methods can be implemented by the UE described herein. In some embodiments, aspects of operations 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.

[0186] In operation 502, the method may include the UE obtaining a configuration (simply denoted as configuration #1) for the UE to store or report information (represented as information #1) related to a mobility procedure in the NTN. For example, information #1 is related to a successful or near-failed successful mobility procedure in the NTN. In some embodiments of the method, the UE may obtain configuration #1 through pre-configuration, such as by default. In some other embodiments, the UE may receive configuration #1 from a network equipment (NE).

[0187] For example, mobility procedures can be performed in a normal handover procedure (i.e., normal or Rel-15 traditional handover), a handover procedure without RACH, a DAPS handover procedure (e.g., Rel-16 DAPS handover), a CHO procedure (e.g., Rel-16 CHO), another different mobility mechanism (e.g., L1 / L2 triggered mobility (LTM) cell handover or any new mobility technology or solution introduced by subsequent standards) or a combination thereof.

[0188] In some implementations of the method, configuration #1 includes at least one of the following thresholds (denoted as threshold #A):

[0189] (1) At least one threshold (denoted as threshold #1) related to the distance between the UE and the reference location (e.g., referenceLocation1) of the source cell (or serving cell) when handover execution or mobility is initiated or triggered (or when a synchronized reconfiguration for mobility or cell change is initiated or triggered, or when an RRC reconfiguration message for mobility or handover is received). For example, mobility or handover execution may be performed in a normal handover procedure, a handover procedure without RACH, a DAPS handover procedure, a CHO procedure, another different mobility mechanism (e.g., LTM cell handover or any new mobility technology or solution introduced by subsequent standards), or a combination thereof.

[0190] (2) At least one threshold (denoted as threshold #2) related to the distance between the UE and the mobile reference location of the source cell (e.g., determined based on referenceLocation1) when mobility or handover execution is initiated or triggered (or when a synchronized reconfiguration for mobility or cell change is initiated or triggered or when an RRC reconfiguration message for mobility or handover is received).

[0191] (3) At least one threshold (denoted as threshold #3) related to the distance between the UE and the reference location (e.g., referenceLocation1) of the source cell when mobility or handover is successfully performed (or when the UE successfully accesses the target cell).

[0192] (4) At least one threshold (denoted as threshold #4) related to the distance between the UE and the source cell’s mobile reference location (e.g., determined based on referenceLocation1) when mobility or handover is successfully performed (or when the UE successfully accesses the target cell).

[0193] (5) At least one threshold (denoted as threshold #5) related to the distance between the UE and the reference location (e.g., referenceLocation2) of the target cell or candidate target cell when mobility or handover execution is initiated or triggered (or when a synchronous reconfiguration for mobility or cell change is initiated or triggered or when an RRC reconfiguration message for mobility or handover is received).

[0194] (6) At least one threshold (denoted as threshold #6) related to the distance between the UE and the mobile reference location (e.g., determined based on referenceLocation2) of the target cell or candidate target cell when mobility or handover execution is initiated or triggered (or when a synchronized reconfiguration for mobility or cell change is initiated or triggered or when an RRC reconfiguration message for mobility or handover is received).

[0195] (7) At least one threshold (denoted as threshold #7) related to the distance between the UE and the reference location (e.g., referenceLocation2) of the target cell or candidate target cell when mobility or handover is successfully performed (or when the UE successfully accesses the target cell).

[0196] (8) At least one threshold (denoted as threshold #8) related to the distance between the UE and the mobile reference location (e.g., determined based on referenceLocation2) of the target cell or candidate target cell when mobility or handover is successfully performed (or when the UE successfully accesses the target cell).

[0197] (9) At least one threshold (denoted as threshold #9) relating to the duration between when a location-based CHO execution condition (e.g., CondEvent D1 or CondEvent D2) configured for a cell (e.g., target cell or candidate target cell) is met and when a measurement-based CHO execution condition (e.g., CondEvent A3, CondEvent A4, or CondEvent A5) configured for a cell (e.g., target cell or candidate target cell) is met. A location-based CHO execution condition may also be referred to as a "location-based CHO trigger condition," a "location-based CHO trigger event," or a "location-based CHO execution event," etc. A measurement-based CHO execution condition may also be referred to as a "measurement-based CHO trigger condition," a "radio link quality-based CHO execution condition," or a "radio link quality-based CHO trigger condition," etc. Measurement-based CHO execution conditions may be referred to as "measurement-based CHO triggering events", "measurement-based CHO execution events", "measurement-based CHO triggering conditions", "radio link quality-based CHO execution conditions", "radio link quality-based CHO triggering conditions", "radio link quality-based CHO triggering events", or "radio link quality-based CHO execution events", etc.

[0198] (10) At least one timer T310 related threshold, such as that commonly used for SHR.

[0199] (11) At least one timer T312 related threshold, such as that commonly used for SHR.

[0200] (12) At least one timer T304 related threshold, such as that commonly used for SHR.

[0201] In operation 504, the method may include storing or reporting information #1 by the UE. In some implementations, information #1 may be stored by the UE based on at least one of the following:

[0202] (1) Mobility or handover execution completed successfully; or

[0203] (2) At least one trigger condition (denoted as trigger condition #B) associated with threshold #A is satisfied. In some embodiments, this satisfaction of trigger condition #B includes at least one of the following:

[0204] 1) When mobility or handover execution is initiated or triggered (or when a synchronous reconfiguration for mobility or cell change is initiated or triggered, or when an RRC reconfiguration message for mobility or handover is received), the distance between the UE and the reference location (e.g., referenceLocation1) of the source cell (or serving cell) is less than threshold #1;

[0205] 2) When mobility or handover execution is initiated or triggered (or when a synchronized reconfiguration for mobility or cell change is initiated or triggered, or when an RRC reconfiguration message for mobility or handover is received), the distance between the UE and the mobile reference location of the source cell (e.g., determined based on referenceLocation1) is less than threshold #2.

[0206] 3) When mobility or handover is successfully performed (or when the UE successfully accesses the target cell), the distance between the UE and the reference location (e.g., referenceLocation1) of the source cell is shorter than threshold #3;

[0207] 4) When mobility or handover is successfully performed (or when the UE successfully accesses the target cell), the distance between the UE and the mobile reference location of the source cell (e.g., determined based on referenceLocation1) is shorter than threshold #4;

[0208] 5) When mobility or handover execution is initiated or triggered (or when a synchronous reconfiguration for mobility or cell change is initiated or triggered, or when an RRC reconfiguration message for mobility or handover is received), the distance between the UE and the reference location (e.g., referenceLocation2) of the target cell or candidate target cell is greater than threshold #5;

[0209] 6) When mobility or handover execution is initiated or triggered (or when a synchronized reconfiguration for mobility or cell change is initiated or triggered, or when an RRC reconfiguration message for mobility or handover is received), the distance between the UE and the mobility reference location (e.g., determined based on referenceLocation2) of the target cell or candidate target cell is greater than threshold #6.

[0210] 7) When mobility or handover is successfully performed (or when the UE successfully accesses the target cell), the distance between the UE and the reference location (e.g., referenceLocation2) of the target cell or candidate target cell is greater than the threshold #7;

[0211] 8) When mobility or handover is successfully performed (or when the UE successfully accesses the target cell), the distance between the UE and the mobile reference location of the target cell or candidate target cell (e.g., determined based on referenceLocation2) is greater than threshold #8;

[0212] 9) The duration between when a location-based CHO execution condition (e.g., CondEvent D1 or CondEvent D2) configured for a cell (e.g., target cell or candidate target cell) is met and when a measurement-based CHO execution condition (i.e., radio link quality-based CHO execution condition) configured for a cell (e.g., target cell or candidate target cell) (e.g., CondEvent A3, CondEvent A4 or CondEvent A5) is met is greater than threshold #9;

[0213] 10) When mobility or handover execution is initiated (or when an RRC reconfiguration message for mobility or handover 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.

[0214] 11) When mobility or handover execution is initiated (or when an RRC reconfiguration message for mobility or handover 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

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

[0216] exist Figure 5 In a specific embodiment (simply referred to as Embodiment 1-1), for near-failure success cases, NTN-specific triggering conditions are designed for a success report (i.e., information #1). For example, the success report could be an SHR or other named report or a newly introduced report. In Embodiment 1-1, for mobility in the NTN (e.g., normal handover, RACH-free handover procedure, DAPS handover, or CHO or other mobility mechanisms), triggering conditions are configured for the UE to record, store, or generate an NTN success report (e.g., SHR or other named report or newly introduced report) or to record, store, or generate information related to successful mobility in the NTN or information related to successful mobility in the NTN. For example, the configuration for recording, storing, or generating an NTN success report or information related to successful mobility in the NTN or information related to successful mobility in the NTN (i.e., configuration #1) includes one or more triggering conditions, such as triggering condition #B associated with threshold #A as described above.

[0217] In Example 1-1, the aforementioned NTN-specific triggering conditions for successful reporting (e.g., thresholds) can be configured by default in the UE or by the network (e.g., source RAN node or target RAN node). The distance-related threshold can be an absolute value or a percentage value. For example, if mobility is a CHO procedure in the NTN, then the aforementioned distance-related threshold can be an absolute value or a percentage value. The percentage value can indicate the ratio of the threshold to a location-based triggering threshold configured for the CHO execution condition (e.g., the location-based triggering threshold could be distanceThreshFromReference1 or distanceThreshFromReference2), for example, the percentage value could be 20%, 40%, 60%, 80%, or other values. For another example, if mobility is a normal / R15 legacy handover or DAPS handover, then the aforementioned distance-related threshold can be an absolute value.

[0218] Return to reference Figure 5 In operation 504, in some embodiments of the method, information #1 contains at least one of the following (represented as content #A):

[0219] (1) At least one set of cell types of a cell, such as one or more cell types of a target cell, a source cell (or serving cell) and / or a candidate target cell, for example, the cell type of the cell may be an NTN cell or a terrestrial network (TN) cell.

[0220] (2) The distance between the UE and the reference location (e.g., referenceLocation1) of the source cell (or serving cell) when mobility or handover execution is initiated or triggered (or when a synchronized reconfiguration for mobility or cell change is initiated or triggered, or when an RRC reconfiguration message for mobility or handover is received);

[0221] (3) The distance between the UE and the mobile reference location of the source cell (e.g., determined based on referenceLocation1) when mobility or handover execution is initiated or triggered (or when a synchronized reconfiguration for mobility or cell change is initiated or triggered, or when an RRC reconfiguration message for mobility or handover is received);

[0222] (4) The distance between the UE and the reference location (e.g., referenceLocation1) of the source cell when mobility or handover is successful (or when the UE successfully accesses the target cell);

[0223] (5) The distance between the UE and the source cell's mobile reference location (e.g., determined based on referenceLocation1) when mobility or handover is successful (or when the UE successfully accesses the target cell);

[0224] (6) The distance between the UE and the reference location (e.g., referenceLocation2) of the target cell or candidate target cell when mobility or handover execution is initiated or triggered (or when a synchronized reconfiguration for mobility or cell change is initiated or triggered, or when an RRC reconfiguration message for mobility or handover is received);

[0225] (7) The distance between the UE and the mobility reference location (e.g., determined based on referenceLocation2) of the target cell or candidate target cell when mobility or handover execution is initiated or triggered (or when a synchronized reconfiguration for mobility or cell change is initiated or triggered or when an RRC reconfiguration message for mobility or handover is received);

[0226] (8) The distance between the UE and the reference location (e.g., referenceLocation2) of the target cell or candidate target cell when mobility or handover is successful (or when the UE successfully accesses the target cell);

[0227] (9) The distance between the UE and the mobile reference location of the target cell or candidate target cell (e.g., determined based on referenceLocation2) when mobility or handover is successful (or when the UE successfully accesses the target cell);

[0228] (10) Cause value; such as cause value for storing or reporting a success report (e.g., SHR), such as indicating which trigger condition is met or which trigger conditions for generating or recording a success report (e.g., SHR) are met, for example: cause value, flag or indication used to indicate that the distance between the UE and the reference location (e.g., referenceLocation1) of the source cell (or serving cell) is less than a threshold when mobility or handover is successful (or when the UE successfully accesses the target cell); or cause value, flag or indication used to indicate that the distance between the UE and the reference location (e.g., referenceLocation2) of the target cell or candidate target cell is greater than a threshold when mobility or handover is successful (or when the UE successfully accesses the target cell);

[0229] (11) At least one location-based CHO execution (or triggering) condition (or event), such as network configuration or location-based CHO execution (or triggering) condition (or event) received by the UE (e.g., CondEvent D1 or CondEvent D2);

[0230] (12) At least one measurement-based CHO execution (or triggering) condition (or event), such as network configuration or measurement-based CHO execution (or triggering) condition (or event) received by the UE (e.g., CondEvent A3 or CondEvent A4 or CondEvent A5);

[0231] (13) The type of CHO execution (or triggering) condition (or event) that is first satisfied, such as location-based CHO execution (or triggering) condition (or event) (e.g., CondEvent D1 or CondEvent D2) or radio link quality or measurement-based CHO execution (or triggering) condition (or event) (e.g., CondEvent A3, CondEvent A4 or CondEvent A5);

[0232] (14) The type of CHO execution (or triggering) condition (or event) that is satisfied, such as location-based CHO execution (or triggering) condition (or event) (e.g., CondEvent D1 or CondEvent D2) or radio link quality or measurement-based CHO execution (or triggering) condition (or event) (e.g., CondEvent A3, CondEvent A4 or CondEvent A5);

[0233] (15) The distance between the UE and the reference location (e.g., referenceLocation1) of the source cell when the location-based CHO execution (or triggering) condition (or event) is met;

[0234] (16) The distance between the UE and the mobile reference location of the source cell (e.g., determined based on referenceLocation1) when the location-based CHO execution (or triggering) condition (or event) is met;

[0235] (17) The distance between the UE and the reference location (e.g., referenceLocation2) of the target cell or candidate target cell when the location-based CHO execution (or triggering) condition (or event) is met;

[0236] (18) The distance between the UE and the moving reference location (e.g., determined based on referenceLocation2) of the target cell or candidate target cell when the location-based CHO execution (or triggering) condition (or event) is met;

[0237] (19) The distance between the UE and the reference location (e.g., referenceLocation1) of the source cell when the measurement-based CHO execution (or triggering) condition (or event) is met;

[0238] (20) The distance between the UE and the mobile reference location of the source cell (e.g., determined based on referenceLocation1) when the measurement-based CHO execution (or triggering) condition (or event) is met;

[0239] (21) The distance between the UE and the reference location (e.g., referenceLocation2) of the target cell or candidate target cell when the measurement-based CHO execution (or triggering) condition (or event) is met;

[0240] (22) The distance between the UE and the moving reference location of the target cell or candidate target cell (e.g., determined based on referenceLocation2) when the measurement-based CHO execution (or triggering) condition (or event) is met;

[0241] (23) When the location-based CHO execution (or triggering) conditions (or events) are met, one or more measurement results of the source cell, target cell, or candidate target cell are obtained;

[0242] (24) When the measurement-based CHO execution (or triggering) conditions (or events) are met, one or more measurement results of the source cell, target cell, or candidate target cell are met;

[0243] (25) Information indicating whether a satellite exchange with a resynchronization procedure is configured, such as an indication of a satellite exchange with a resynchronization procedure or an indication of a satellite exchange without a resynchronization procedure.

[0244] (26) The time elapsed between when the location-based CHO execution (or triggering) condition (or event) is met and when the latest RRC reconfiguration message or conditional reconfiguration is received;

[0245] (27) The time elapsed between the fulfillment of a CHO execution (or triggering) condition (or event) based on radio link quality or measurement and the receipt of the latest RRC reconfiguration message or conditional reconfiguration;

[0246] (28) The duration between when a location-based CHO execution (or triggering) condition (or event) configured for a cell (e.g., target cell or candidate cell) is met and when a measurement-based CHO execution (or triggering) condition (or event) configured for a cell (e.g., target cell or candidate cell) is met;

[0247] (29) The time elapsed between when the measurement-based CHO execution (or triggering) condition (or event) is met and when mobility or handover is successfully executed (or when the UE successfully accesses the target cell);

[0248] (30) The time elapsed between when the location-based CHO execution (or triggering) condition (or event) is met and when the mobility or handover is successfully executed (or when the UE successfully accesses the target cell);

[0249] (31) The order in which location-based CHO execution (or triggering) conditions (or events) and measurement-based CHO execution (or triggering) conditions (or events) are triggered; or an indication regarding whether location-based CHO execution (or triggering) conditions (or events) are triggered when location-based CHO execution (or triggering) conditions (or events) are triggered;

[0250] (32) Radio link interruption since the mobility or handover execution was initiated or triggered (or when a synchronized reconfiguration for mobility or cell change was initiated or triggered, or when an RRC reconfiguration message for mobility or handover was received) or when the mobility or handover execution was successful (or when the UE successfully accessed the target cell); or

[0251] (33) Indicates that the radio link interruption is due to radio link quality issues or feeder link switching.

[0252] exist Figure 5 In some implementations, information #1 may be referred to as or included in NTN success reports (e.g., SHR or other named reports or newly introduced reports) or in NTN information related to successful mobility or information related to successful mobility in NTN. Figure 5 In some other implementations, at least one of the above contents in information #1 (e.g., content #A) (other than the reason value of the success report (e.g., SHR) in content #A) may be stored or reported by the UE in the RA report or connection establishment failure (CEF) report.

[0253] exist Figure 5In a specific embodiment (referred to as Embodiment 2-1), the NTN success report (e.g., SHR or another named report or new introduction report) or information related to successful mobility in the NTN or related to successful mobility in the NTN can be stored or reported by the UE. Specifically, when at least one of the trigger conditions #B associated with threshold #A described above is met and / or mobility or handover to the target cell is successfully performed, the UE records or stores the NTN success report or information related to successful mobility in the NTN or related to successful mobility in the NTN. For example, if at least one of the trigger conditions #B associated with threshold #A is met and / or mobility or handover to the target cell is successfully performed, the UE records or stores the NTN's SHR or other named report or new introduction report. Then, the UE transmits the NTN success report or information related to successful mobility in the NTN or related to successful mobility in the NTN to the network.

[0254] In Example 2-1, the NTN success report (e.g., SHR or other named reports or newly introduced reports) or information related to successful mobility in the NTN or information related to successful mobility in the NTN may include at least one of the contents #A described above.

[0255] In Example 2-1, based on the received success report, the network (e.g., NE) can optimize mobility-related configurations (e.g., normal handover-related configuration, CHO-related configuration, no-RACH handover-related configuration, or any of configuration #1) and / or mobility-related thresholds (e.g., thresholds for triggering normal or no-RACH handover, CHO-related execution, or triggering thresholds). For example, the network can optimize RSRP, RSRQ, or SINR thresholds for triggering normal, no-RACH, or DAPS handover. Alternatively, the network can optimize location-related thresholds (e.g., distanceThreshFromReference1 or distanceThreshFromReference2) for triggering CHO execution.

[0256] Return to reference Figure 5 In some implementations, the UE may transmit optional UE capability information for supporting the storage or reporting of information #1, such as optional UE capability information with or without signaling.

[0257] In UE capabilities Figure 5In certain embodiments (referred to as Embodiments 1-2), because configuration is required for the UE to store or generate or report success reports of the NTN or information related to successful mobility in the NTN, or information related to successful mobility in the NTN (e.g., triggering condition #B mentioned in Embodiment 1-1), the network (e.g., the NE) needs to know the UE's capabilities in order to configure the correct settings to trigger success reports in the NTN. In Embodiments 1-2, the UE's ability to store or report success reports of the NTN or information related to successful mobility in the NTN, or information related to successful mobility in the NTN, can be an optional UE capability. Even if the UE supports access to the NTN, storing or reporting success reports of the NTN or information related to successful mobility in the NTN, or information related to successful mobility in the NTN, is optional, and this capability is explicitly signaled to the network; that is, explicit capability signaling or optional UE capability with signaling is required.

[0258] In Examples 1-2, depending on the specific example, the following two options may exist: option #a and option #b.

[0259] (1) Option #a: Optional capability signaling. In option #a, storing or reporting NTN success reports or information related to successful mobility in the NTN, or information related to successful mobility in the NTN, is optional, and this capability is explicitly signaled to the network by the UE. New UE capability bits (optionally with signaling) may be introduced to support, for example, storing and delivering NTN success reports or information related to successful mobility in the NTN, or information related to successful mobility in the NTN, based on requests from the network. For example, new UE capability bits may be introduced for NTN SHR or other named reports or newly introduced reports.

[0260] - For example, it may include optional UE capability indications for storing or reporting information related to successful mobility in the NTN or information related to successful mobility in the NTN, or for example, it may include optional UE capability indications of the NTN's SHR in the UE capability information message.

[0261] - In another instance, the existing optional UE capability indication is used again in the successful handover (HO) report (i.e., success-HO-Report-r17) in the UE capability information message for mobility in the NTN.

[0262] (2) Option #b: Optional no capability signaling. In option #b, storing or reporting information related to successful mobility in the NTN or information related to successful mobility in the NTN is optional, and the UE does not signal the explicit capability bit. In option #b, an optional feature without signaling is introduced for successful reporting of the NTN (e.g., SHR).

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

[0264] According to some aspects of this disclosure, methods related to NTN can be implemented by the NE described herein. In some embodiments, aspects of the operation of the NE can be described by reference to [reference needed]. 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 procedures may be rearranged or otherwise eliminated or modified without departing from the spirit and scope of this disclosure, and other implementations are possible.

[0265] Specifically, the method may include receiving information related to mobility in the NTN by the NE (e.g., Figure 5 The information described in the embodiments (#1) includes, for example, information related to successful mobility in the NTN. This information may include... Figure 5 The elements described in the embodiments are the same as the elements of information #1 (e.g., content #A).

[0266] For example, the NE may receive information #1 from the UE, a third-party node, or the target node of the mobility (e.g., the target node to which the target cell belongs). Mobility may be performed, for instance, in a normal handover procedure (i.e., normal or Rel-15 legacy handover), a handover procedure without RACH, a DAPS handover procedure (e.g., Rel-16 DAPS handover), a CHO procedure (e.g., Rel-16 CHO), another different mobility mechanism (e.g., LTM cell handover or any new mobility technology or solution introduced by subsequent standards), or a combination thereof.

[0267] 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 embodiments is #1). The configuration may include... Figure 5 The elements of configuration #1 described in the embodiments (e.g., threshold #A) are the same as the elements.

[0268] In some implementations of the method, the NE may receive optional UE capability information from the UE for storing or reporting supporting information #1, such as optional UE capability information with or without signaling. Details can be found in the description above. Figure 5 Examples of implementations.

[0269] According to other aspects of this disclosure, the methods related to NTN can be implemented by the UE described herein. In some implementations, aspects of the UE's operation can be described by reference to... Figure 2The UE 200 described herein is implemented. It should be noted that the methods implemented by the UE 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.

[0270] Specifically, in response to a connection failure occurring during a handover procedure in the NTN, the method may include having the UE store information related to the connection failure. For example, a connection failure may be an RLF in the source / serving cell before receiving an RRC reconfiguration message for mobility or handover, or before performing a mobility or handover operation; or a connection failure may be a failure during mobility or handover operation; or a connection failure may be an RLF occurring shortly after a successful mobility or handover operation. For example, the handover procedure may be a normal handover procedure (i.e., normal or Rel-15 legacy handover), a handover procedure without RACH, a DAPS handover procedure (e.g., Rel-16 DAPS handover), a CHO procedure (e.g., Rel-16 CHO), another different mobility mechanism (e.g., LTM cell handover or any new mobility technology or solution introduced by subsequent standards), or a combination thereof.

[0271] In some embodiments of the method, the UE may report information related to connection failure, for example via an RLF report or other report.

[0272] In some implementations of the method, the information related to connection failure includes at least one of the following (denoted as Content #B):

[0273] (1) At least one set of cell types of a cell, such as one or more cell types of a target cell, a source cell (or serving cell) and / or a candidate target cell, for example, the cell type of the cell may be an NTN cell or a terrestrial network (TN) cell.

[0274] (2) The distance between the UE and the reference location (e.g., referenceLocation1) of the source cell when mobility or handover execution is initiated or triggered (or when a synchronized reconfiguration for mobility or cell change is initiated or triggered, or when an RRC reconfiguration message for mobility or handover is received);

[0275] (3) The distance between the UE and the mobile reference location of the source cell (e.g., determined based on referenceLocation1) when mobility or handover execution is initiated or triggered (or when a synchronized reconfiguration for mobility or cell change is initiated or triggered, or when an RRC reconfiguration message for mobility or handover is received);

[0276] (4) When a connection failure occurs (e.g., before receiving an RRC reconfiguration message for mobility or handover or when an RLF occurs in the source / serving cell before performing a mobility or handover operation, or when a mobility or handover operation fails (or when the UE fails to access the target cell), or when an RLF occurs shortly after a successful mobility or handover operation or access to the target cell) the distance between the UE and the reference location (e.g., referenceLocation1) of the source cell;

[0277] (5) When a connection failure occurs (e.g., before receiving an RRC reconfiguration message for mobility or handover or when an RLF occurs in the source / serving cell before performing a mobility or handover operation, or when a mobility or handover operation fails (or when the UE fails to access the target cell), or when an RLF occurs shortly after a successful mobility or handover operation or access to the target cell) the distance between the UE and the mobile reference location of the source cell (e.g., determined based on referenceLocation1);

[0278] (6) The distance between the UE and the reference location (e.g., referenceLocation2) of the target cell or candidate target cell when mobility or handover execution is initiated or triggered (or when a synchronized reconfiguration for mobility or cell change is initiated or triggered, or when an RRC reconfiguration message for mobility or handover is received);

[0279] (7) The distance between the UE and the mobility reference location (e.g., determined based on referenceLocation2) of the target cell or candidate target cell when mobility or handover execution is initiated or triggered (or when a synchronized reconfiguration for mobility or cell change is initiated or triggered or when an RRC reconfiguration message for mobility or handover is received);

[0280] (8) When a connection failure occurs (e.g., before receiving an RRC reconfiguration message for mobility or handover or when an RLF occurs in the source / serving cell before performing a mobility or handover operation, or when a mobility or handover operation fails (or when the UE fails to access the target cell), or when an RLF occurs shortly after a successful mobility or handover operation or access to the target cell) the distance between the UE and the reference location (e.g., referenceLocation2) of the target cell or candidate target cell;

[0281] (9) When a connection failure occurs (e.g., before receiving an RRC reconfiguration message for mobility or handover or when an RLF occurs in the source / serving cell before performing a mobility or handover operation, or when a mobility or handover operation fails (or when the UE fails to access the target cell), or when an RLF occurs shortly after a successful mobility or handover operation or access to the target cell) the distance between the UE and the mobility reference location (e.g., determined based on referenceLocation2) of the target cell or candidate target cell;

[0282] (10) At least one location-based conditional switching (CHO) execution (or triggering) condition (or event), such as a location-based CHO execution (or triggering) condition (or event) received by the NW configuration / UE (e.g., CondEvent D1 or CondEvent D2);

[0283] (11) At least one measurement-based CHO execution (or triggering) condition (or event), such as network configuration or measurement-based CHO execution (or triggering) condition (or event) received by the UE (e.g., CondEvent A3 or CondEvent A4 or CondEvent A5);

[0284] (12) The type of CHO execution (or triggering) condition (or event) (if any) that is first satisfied, such as a location-based CHO execution (or triggering) condition (or event) (e.g., CondEvent D1 or CondEvent D2) or a radio link quality / measurement-based CHO execution (or triggering) condition (or event) (e.g., CondEvent A3, CondEvent A4, or CondEvent A5); or

[0285] (13) The type of CHO execution (or triggering) condition (or event) (if any) that is satisfied, such as location-based CHO execution (or triggering) condition (or event) (e.g., CondEvent D1 or CondEvent D2) or radio link quality / measurement-based CHO execution (or triggering) condition (or event) (e.g., CondEvent A3, CondEvent A4 or CondEvent A5);

[0286] (14) Information indicating whether a satellite exchange with a resynchronization procedure is configured, such as an indication of a satellite exchange with a resynchronization procedure or an indication of a satellite exchange without a resynchronization procedure.

[0287] (15) Information indicating whether the measurement-based CHO execution (or triggering) conditions (or events) configured for the cell are met when a connection failure occurs (e.g., when an RRC reconfiguration message for mobility or handover is received or occurs in the source / serving cell before a mobility or handover execution is performed, or when a mobility or handover execution fails (or when the UE fails to access the target cell), or when an RRC reconfiguration occurs shortly after a successful mobility or handover execution / access to the target cell) or when the UE performs an RRC reconstruction (the reconstructed cell may be the source cell or another cell);

[0288] (16) Information indicating whether the location-based CHO execution (or triggering) conditions (or events) configured for the cell are met when a connection failure occurs (e.g., when an RRC reconfiguration message for mobility or handover is received or occurs in the source / serving cell before a mobility or handover execution is performed, or when a mobility or handover execution fails (or when the UE fails to access the target cell), or when an RRC reconfiguration occurs shortly after a successful mobility or handover execution / access to the target cell) or when the UE performs an RRC rebuild (the rebuilding cell may be the source cell or another cell);

[0289] (17) The order in which location-based CHO execution (or triggering) conditions (or events) and measurement-based CHO execution (or triggering) conditions (or events) are triggered; or an indication of whether location-based CHO execution (or triggering) conditions (or events) are triggered when location-based CHO execution (or triggering) conditions (or events) are triggered;

[0290] (18) Radio link interruption since the start of mobility or handover execution; or

[0291] (19) Indicates that the radio link interruption is due to radio link quality issues or feeder link switching.

[0292] In some implementations of the method, if the CHO execution (or triggering) condition (or event) that is first satisfied is a location-based CHO execution (or triggering) condition (or event), or if only a location-based CHO execution (or triggering) condition (or event) (e.g., CondEvent D1 or CondEvent D2) is satisfied before the connection failure occurs, then the information related to the connection failure further includes at least one of the following (denoted as Content #C):

[0293] (1) The ID associated with a cell (represented as cell #1) whose location-based CHO execution (or triggering) condition (or event) is met but whose measurement-based CHO execution (or triggering) condition (or event) is not met;

[0294] (2) The distance between the UE and the reference location of the source cell when the location-based CHO execution (or triggering) condition (or event) is met;

[0295] (3) The distance between the UE and the mobile reference location of the source cell when the location-based CHO execution (or triggering) condition (or event) is met;

[0296] (4) The distance between the UE and the reference location of cell #1 or other candidate target cells when the location-based CHO execution (or triggering) condition (or event) is met;

[0297] (5) The distance between the UE and the mobile reference location of cell #1 or other candidate target cells when the location-based CHO execution (or triggering) condition (or event) is met;

[0298] (6) One or more measurement results of the source cell when the location-based CHO execution (or triggering) conditions (or events) are met;

[0299] (7) One or more measurement results of cell #1 or other candidate target cells when the location-based CHO execution (or triggering) conditions (or events) are met;

[0300] (8) The time elapsed between the fulfillment of the location-based CHO execution (or triggering) condition (or event) and the receipt of the latest condition reconfiguration; or

[0301] (9) The time elapsed between when the location-based CHO execution (or triggering) condition (or event) is met and when the connection failure occurs.

[0302] In some implementations of the method, if the CHO execution (or triggering) condition (or event) initially met is a measurement-based CHO execution (or triggering) condition (or event), or if only a radio link quality-based or measurement-based CHO execution (or triggering) condition (or event) (e.g., CondEvent A3, A4, or A5) is met before the connection failure occurs, then the information related to the connection failure further includes at least one of the following (denoted as Content #D):

[0303] (1) The ID associated with the cell (represented as cell #2) whose measurement-based CHO execution (or triggering) condition (or event) is met but whose location-based CHO execution (or triggering) condition (or event) is not met;

[0304] (2) The distance between the UE and the reference location of the source cell when the measurement-based CHO execution (or triggering) condition (or event) is met;

[0305] (3) The distance between the UE and the mobile reference position of the source cell when the measurement-based CHO execution (or triggering) condition (or event) is met;

[0306] (4) The distance between the UE and the reference location of cell #2 or other candidate target cells when the measurement-based CHO execution (or triggering) condition (or event) is met;

[0307] (5) The distance between the UE and the mobile reference position of cell #2 or other candidate target cells when the measurement-based CHO execution (or triggering) condition (or event) is met;

[0308] (6) When the measurement-based CHO execution (or triggering) conditions (or events) are met, one or more measurement results of the source cell are met;

[0309] (7) One or more measurement results of the second cell or other candidate target cells when the measurement-based CHO execution (or triggering) conditions (events) are met;

[0310] (8) The time elapsed between the fulfillment of the measurement-based CHO execution (or triggering) condition (or event) and the receipt of the latest condition reconfiguration or condition reconfiguration; or

[0311] (9) The time elapsed between when the measurement-based CHO execution (or triggering) condition (or event) is met and when the connection failure occurs.

[0312] In some implementations of the method, if both a location-based CHO execution (or triggering) condition (or event) and a measurement-based CHO execution (or triggering) condition (or event) are met before a connection failure occurs (e.g., the first met CHO execution (or triggering) condition (or event) is one of a location-based CHO execution (or triggering) condition (or event) and a measurement-based CHO execution (or triggering) condition (or event), and the second met CHO execution condition is the other of a location-based CHO execution (or triggering) condition (or event) and a measurement-based CHO execution (or triggering) condition (or event), then the information related to the connection failure further includes at least one of the following (denoted as Content #E):

[0313] (1) The ID associated with the cell (represented as cell #3) whose location-based CHO execution (or triggering) condition (or event) is met and whose measurement-based CHO execution (or triggering) condition (or event) is met;

[0314] (2) The distance between the UE and the reference position of the source cell when the first CHO execution (or triggering) condition (or event) is met;

[0315] (3) The distance between the UE and the mobile reference position of the source cell when the first CHO execution (or triggering) condition (or event) is met;

[0316] (4) The distance between the UE and the reference location of cell #3 or other candidate target cells when the first CHO execution (or triggering) condition (or event) is met;

[0317] (5) The distance between the UE and cell #3 or other candidate target cells when the first CHO execution (or triggering) condition (or event) is met;

[0318] (6) The distance between the UE and the reference location of the source cell when the secondary CHO execution (or triggering) condition (or event) is met;

[0319] (7) The distance between the UE and the mobile reference position of the source cell when the secondary CHO execution (or triggering) condition (or event) is met;

[0320] (8) The distance between the UE and the reference location of cell #3 or other candidate target cells when the secondary CHO execution (or triggering) condition (or event) is met;

[0321] (9) The distance between the UE and the mobile reference position of cell #3 or other candidate target cells when the CHO execution (or triggering) condition (or event) is met;

[0322] (10) When the first CHO execution (or triggering) condition (or event) is met, one or more measurement results of the source cell are obtained;

[0323] (11) When the CHO execution (or triggering) condition (or event) is met, one or more measurement results of cell #3 or other candidate target cells are met;

[0324] (12) The time elapsed between the first CHO execution (or triggering) condition (or event) being met and the latest RRC reconfiguration message or conditional reconfiguration being received;

[0325] (13) The time elapsed between the fulfillment of the second-fulfilled CHO execution (or triggering) condition (or event) and the receipt of the latest RRC reconfiguration message or condition reconfiguration;

[0326] (14) The time elapsed between when the first CHO execution (or triggering) condition (or event) is met and when the second CHO execution (or triggering) condition (or event) is met;

[0327] (15) The time elapsed between when the first CHO execution (or triggering) condition (or event) is met and when the connection failure occurs; or

[0328] (16) The time elapsed between when the CHO execution (or triggering) condition (or event) is met and when the connection failure occurs.

[0329] In some other implementations of the method implemented by the UE, at least one of the above-mentioned contents (i.e., content #B, content #C, content #D and / or content #E) in the information related to connection failure may be stored or reported by the UE in the RA report or connection establishment failure (CEF) report instead of the RLF report.

[0330] According to some aspects of this disclosure, methods related to NTN can be implemented by the NE described herein. In some embodiments, aspects of the operation of the NE can be described by reference to [reference needed]. 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 procedures may be rearranged or otherwise eliminated or modified without departing from the spirit and scope of this disclosure, and other implementations are possible.

[0331] Specifically, the method may include the NE receiving information related to connection failures in mobility or handover procedures within the NTN. For example, the NE may receive information #1 from the UE (e.g., via RLF reporting), a third-party node, or the source node of mobility (e.g., the source node to which the source cell belongs) or the target node of mobility (e.g., the target node to which the target cell belongs). The mobility or handover procedure may be a normal handover procedure, a handover procedure without RACH, a DAPS handover procedure, a CHO procedure, another different mobility mechanism (e.g., LTM cell handover or any new mobility technology or solution introduced by subsequent standards), or a combination thereof. The information received by the NE may contain the same content as the information related to failed connections stored or reported by the UE (e.g., via RLF reporting) (i.e., content #B, content #C, content #D, and / or content #E), as described in the method described above performed by the UE.

[0332] In a specific embodiment of this disclosure (referred to as Embodiment 2-2), for mobility in the NTN, similar to conventional methods, connection failures may occur. For example, an RLF may occur in the source / serving cell before receiving an RRC reconfiguration message for mobility or handover, or before performing a mobility or handover operation, or a mobility or handover operation failure may occur (or the UE fails to access the target cell), or an RLF may occur shortly after a successful mobility or handover operation or access to the target cell. For MRO purposes, the UE may store or record failure-related information for mobility in the NTN in a failure report (e.g., an RLF report or other named or newly introduced report). The failure report or failure-related information may contain at least one of the content #B, content #C, content #D, and / or content #E described above.

[0333] In Example 2-2, based on the received failure report, the network (e.g., NE) can optimize mobility-related configurations and / or mobility-related thresholds (e.g., RSRP, RSRQ, or SINR thresholds for triggering normal / R15 legacy handover or DAPS handover, or location-related thresholds for triggering CHO execution (e.g., distanceThreshFromReference1 or distanceThreshFromReference2)).

[0334] Some aspects of this disclosure refer to enhancements to the Xn interface. In some embodiments, the “SN state transition” message may contain location-related information (e.g., referenceLocation1 defined in TS 38.331 and contained in the ReportConfigNR IE, and / or referenceLocation2 defined in TS 38.331 and contained in the ReportConfigNR IE, and / or distanceThreshFromReference1 defined in TS 38.331 and contained in the ReportConfigNR IE, and / or distanceThreshFromReference2 defined in TS 38.331). If this location-related information is included in the “SN state transition” message, the target NG-RAN node should store this information in the UE context (if supported) and use it for MRO, as specified in TS38.300, for example.

[0335] In some other embodiments, the "Handover Report" message may contain location-related information (e.g., referenceLocation1 defined in TS 38.331 and contained in the ReportConfigNR IE, and / or referenceLocation2 defined in TS 38.331 and contained in the ReportConfigNR IE, and / or distanceThreshFromReference1 defined in TS 38.331 and contained in the ReportConfigNR IE, and / or distanceThreshFromReference2 defined in TS 38.331). If this location-related information is included in the "Handover Report" message, the source node should use it for MRO (if supported), as specified in, for example, TS 38.300.

[0336] Figure 6 This document provides another flowchart illustrating an NTN-related method based on some aspects of this disclosure. The operation of the method can be implemented by the UE described herein. In some implementations, aspects of operations 602 and 604 can be referenced from... Figure 2 The UE200 described herein is executed. Each of operations 602 and 604 may be executed according to the instances described herein.

[0337] In operation 602, the method may include the UE storing NTN-related information. This information may also be referred to as NTN-specific information. In operation 602, the method may include the UE transmitting NTN-related information, for example, via a RA report.

[0338] For example, NTN-related information may include at least one of the following (represented as content #F):

[0339] (1) A set of cell types of at least one cell of the UE, such as one or more cell types of the target cell, the source cell (or serving cell) and / or the candidate target cell, for example, the cell type of the cell may be an NTN cell or a terrestrial network (TN) cell.

[0340] (2) Ephemeris time, for example, it may contain sfn value and subFrameNR value (as defined in TS38.331);

[0341] (3) Ephemeris information, for example, satellite ephemeris provided in the format of position and velocity state vectors or orbital parameters (as defined in TS38.331);

[0342] (4) Scheduling offsets for timing relationships modified for NTN (as defined in TS38.331), such as cellSpecificKoffset;

[0343] (5) Scheduling offsets provided by the network equipment (NE) when downlink and uplink frame timings are misaligned at the NE (as defined in TS38.331), such as kmac;

[0344] (6) Polarization information for downlink transmission on the serving link (as defined in TS38.331), such as ntn-PolarizationDL, which may include right-hand circular polarization (RHCP, LHCP) and linear polarization;

[0345] (7) Polarization information used for uplink service links, such as ntn-PolarizationUL (as defined in TS38.331);

[0346] (8) The validity period configured by the NE for the auxiliary information (i.e., the ephemeris of the service and / or adjacent satellites and the common TA parameters), which indicates the maximum duration during which the UE can apply the auxiliary information and has not acquired new auxiliary information (from epochTime) (as defined in TS38.331), such as ntn-UlSyncValidityDuration;

[0347] (9) Common timing advance (TA) value, such as ta-Common, such as the common timing advance value of network control, and may include any timing offsets that the network deems necessary (as defined in TS38.331);

[0348] (10) Drift rate of common TA values ​​(as defined in TS38.331), such as ta-CommonDrift;

[0349] (11) Changes in the drift rate of common TA values ​​(as defined in TS38.331), such as ta-CommonDriftVariant;

[0350] (12) Indicates whether the UE is configured to report timing advance during random access due to RRC connection establishment or RRC connection restoration or RRC connection reconstruction, such as an indication that the UE is configured to report timing advance during random access due to RRC connection establishment or RRC connection restoration or RRC connection reconstruction, or an indication that the UE is not configured to report timing advance during random access due to RRC connection establishment or RRC connection restoration or RRC connection reconstruction; or

[0351] (13) Information indicating whether advance-timed event triggering reports are supported, such as instructions on whether advance-timed event triggering reports are supported or instructions on whether advance-timed event triggering reports are not supported.

[0352] According to some aspects of this disclosure, methods related to NTN can be implemented by the NE described herein. Specifically, the method may include the NE receiving a RA report containing NTN-related information. The NTN-related information may include at least one of the contents #F described above. In some embodiments, aspects of the NE's operation may be described by reference to... 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 procedures may be rearranged or otherwise eliminated or modified without departing from the spirit and scope of this disclosure, and other implementations are possible.

[0353] exist Figure 6 In a specific embodiment (referred to as Embodiment 3), the network can broadcast valid ephemeris information and common TA parameters for the serving cell. The UE should have a valid GNSS location, ephemeris, and common TA before connecting to the NTN cell. For synchronization, before and during connection to the NTN cell, the UE should calculate the RTT between the UE and the reference point (RP) based on the GNSS location, ephemeris, and common TA parameters, and automatically use the T... TA Pre-compensation for RTT between UE and RP.

[0354] In Example 3, the UE can calculate the frequency Doppler shift of the serving link and automatically pre-compensate for it in uplink transmissions by taking into account the UE's location and ephemeris. If the UE does not have a valid GNSS location and / or valid ephemeris and common TA, it should not transmit until it regains both. In connected mode, the UE should be able to continuously update timing advance and frequency pre-compensation. The UE can be configured to report timing advance during random access procedures or in connected mode.

[0355] Example 3 provides a solution for enhancing RA reporting in NTN. The UE can store or report at least one of the aforementioned NTN-related information (i.e., content #F) in the RA report. The granularity of storing or reporting information can be per RA attempt, per RA procedure, only for the last RA attempt, only for the first RA attempt, or for a portion of the RA attempts in the RA procedure.

[0356] In some other embodiments of this disclosure, at least one of the above-mentioned NTN-related information (e.g., content #F) may be stored or reported by the UE in a CEF report or a success report (e.g., a success report may be an SHR or other named report or a newly introduced report) or a failure report (e.g., an RLF report or other named report or a newly introduced report) rather than a RA report.

[0357] Figure 7 This document provides another flowchart illustrating an NTN-related method based on some aspects of this disclosure. The operation of the method can be implemented by the UE described herein. In some embodiments, aspects of operations 702 and 704 can be referenced from... Figure 2 The UE200 described herein is executed. Each of operations 702 and 704 may be executed according to the instances described herein.

[0358] In operation 702, the method may include the UE storing NTN-related information for at least one cell of the UE. In operation 704, the method may include the UE transmitting the NTN-related information, for example, the UE transmitting the NTN-related information via Mobility History Information (MHI) or within the MHI. For example, the NTN-related information includes at least one of the following:

[0359] (1) A set of cell IDs for at least one cell of the UE;

[0360] (2) At least one set of cell types for a cell, for example, the cell type of a cell may be NTN cell or TN cell;

[0361] (3) The duration or percentage of time the UE remains in at least one NTN cell; or

[0362] (4) The duration or percentage of time the UE stays in at least one TN cell.

[0363] Figure 7 A specific embodiment (referred to as Embodiment 4-1) provides an enhanced solution regarding UE history information at the UE side. In Embodiment 4-1, the UE may, for example, store or report NTN-related information of at least one cell in / via the MHI. For example, the NTN-related information of a cell includes at least one of the following: cell ID, cell type (e.g., the cell is an NTN cell or the cell is a TN cell), the duration or percentage of time the UE spends in the NTN cell, and the duration or percentage of time the UE spends in the TN cell.

[0364] According to some aspects of this disclosure, methods related to NTN can be implemented by the NE described herein. In some embodiments, aspects of the operation of the NE can be described by reference to [reference needed]. 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 procedures may be rearranged or otherwise eliminated or modified without departing from the spirit and scope of this disclosure, and other implementations are possible.

[0365] Specifically, the method may include storing NTN-related information by the NE. For example, UE historical information (UHI) may contain NTN-related information for at least one cell of the UE. For instance, the NTN-related information may include at least one of the following:

[0366] (1) At least one set of cell IDs;

[0367] (2) At least one set of cell types for a cell, for example, the cell type of a cell may be NTN cell or TN cell;

[0368] (3) The duration or percentage of time the UE remains in at least one NTN cell; or

[0369] (4) The duration or percentage of time the UE stays in at least one TN cell.

[0370] A specific embodiment of the method described above, implemented by the NE (referred to as Embodiment 4-2), provides an enhanced solution regarding UE historical information at the network side. In Embodiment 4-2, the NE (i.e., the network) may, for example, store or record NTN-related information of at least one cell in / via the UHI. For example, the NTN-related information of the cell includes at least one of the following: cell ID, cell type (e.g., the cell is an NTN cell or the cell is a TN cell), the duration or percentage of time the UE spends in the NTN cell, and the duration or percentage of time the UE spends in the TN cell.

[0371] 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 the UE's mobility procedures in a non-terrestrial network (NTN); and Store or report 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 Receive the first configuration from the network equipment NE.

3. The UE of claim 1, 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 distance between the UE and the reference location of the source cell at the time of handover initiation; At least one second threshold, which is related to the distance between the UE and the mobile reference position of the source cell at the time of handover initiation; At least one third threshold, which is related to the distance between the UE and the reference location of the source cell when the handover is successful; At least one fourth threshold, which is related to the distance between the UE and the mobile reference position of the source cell when the handover is successful; At least one fifth threshold, which is related to the distance between the UE and the reference location of the target cell or candidate target cell at the time of handover initiation; At least one sixth threshold, which is related to the distance between the UE and the mobile reference position of the target cell or the candidate target cell at the time of handover initiation; At least one seventh threshold, which is related to the distance between the UE and the reference location of the target cell or the candidate target cell when the handover is successful; At least one eighth threshold, which is related to the distance between the UE and the moving reference position of the target cell or the candidate target cell when the handover is successful; At least one ninth threshold, which is related to the duration between when the location-based conditional handover CHO execution condition configured for the cell is met and when the measurement-based CHO execution condition configured for the cell is met; At least one timer T310 related threshold; At least one timer T312 related threshold; or At least one timer T304 related threshold.

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

5. The UE of claim 4, wherein the satisfaction of the at least one triggering condition associated with the one or more thresholds includes at least one of the following: When the handover is initiated, the distance between the UE and the reference location of the source cell is shorter than at least one first threshold. When the handover is initiated, the distance between the UE and the mobile reference position of the source cell is shorter than at least one second threshold. When the handover is successful, the distance between the UE and the reference location of the source cell is shorter than at least one third threshold. When the handover is successful, the distance between the UE and the mobile reference position of the source cell is shorter than at least one fourth threshold. When the handover is initiated, the distance between the UE and the reference position of the target cell or the candidate target cell is greater than at least one fifth threshold. When the handover is initiated, the distance between the UE and the mobile reference position of the target cell or the candidate target cell is greater than the at least one sixth threshold. When the handover is successful, the distance between the UE and the reference position of the target cell or the candidate target cell is greater than at least one seventh threshold. When the handover is successful, the distance between the UE and the mobile reference position of the target cell or the candidate target cell is greater than the at least one eighth threshold. The duration between when the location-based CHO execution condition configured for the cell is met and when the measurement-based CHO execution condition configured for the cell is met is greater than the at least one ninth threshold; When the switching starts, 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 switching starts, 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.

6. The UE of claim 1, wherein the first information comprises at least one of the following: At least one set of community types; The distance between the UE and the reference location of the source cell at the time of handover initiation; The distance between the UE and the mobile reference position of the source cell when the handover is initiated; The distance between the UE and the reference position of the source cell when the handover is successful; The distance between the UE and the mobile reference position of the source cell when the handover is successful; The distance between the UE and the reference position of the target cell or candidate target cell when the handover is initiated; The distance between the UE and the movement reference position of the target cell or the candidate target cell when the handover is initiated; The distance between the UE and the reference position of the target cell or the candidate target cell when the handover is successful; The distance between the UE and the moving reference position of the target cell or the candidate target cell when the handover is successful; The reason value used for the first information; At least one location-based conditional switching CHO execution condition; The first type of CHO execution condition to be satisfied; Secondly, the type of CHO execution condition that needs to be met; The distance between the UE and the reference location of the source cell when the location-based CHO execution conditions are met; The distance between the UE and the mobile reference position of the source cell when the location-based CHO execution condition is met; The distance between the UE and the reference location of the target cell or the candidate target cell when the location-based CHO execution conditions are met; The distance between the UE and the moving reference position of the target cell or the candidate target cell when the location-based CHO execution conditions are met; The distance between the UE and the reference position of the source cell when the measurement-based CHO execution conditions are met; The distance between the UE and the moving reference position of the source cell when the measurement-based CHO execution conditions are met; The distance between the UE and the reference position of the target cell or the candidate target cell when the measurement-based CHO execution conditions are met; The distance between the UE and the moving reference position of the target cell or the candidate target cell when the measurement-based CHO execution conditions are met; When the location-based CHO execution conditions are met, one or more measurement results of the source cell, the target cell, or the candidate target cell are obtained. When the measurement-based CHO execution conditions are met, one or more measurement results of the source cell, the target cell, or the candidate target cell are obtained. Indicates whether satellite exchange with a resynchronization procedure is configured; The time elapsed between when the location-based CHO execution conditions are met and when the latest Radio Resource Control (RRC) reconfiguration message is received; The time elapsed between when the measurement-based CHO execution conditions are met and when the latest Radio Resource Control (RRC) reconfiguration message is received; The duration between when the location-based CHO execution conditions configured for the cell are met and when the measurement-based CHO execution conditions configured for the cell are met; The time elapsed between when the measurement-based CHO execution conditions are met and when the switch is successful; The time elapsed between when the location-based CHO execution conditions are met and when the switch is successful; The order in which the location-based CHO execution conditions and the measurement-based CHO execution conditions are triggered; The radio link has been interrupted since the handover was initiated or when the handover was successful; or The information indicates that the radio link interruption is due to radio link quality issues or feeder link switching.

7. The UE according to any one of claims 1 to 6, wherein the mobility procedure or the handover is performed in a normal handover procedure, a handover procedure without a random access channel (RACH), a dual active protocol stack (DAPS) handover procedure, a conditional handover (CHO) procedure, another different mobility mechanism, or a combination thereof.

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

9. 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 enable the NE to receive first information related to mobility procedures in a non-terrestrial network (NTN).

10. The NE of claim 9, wherein the processor of the NE is configured to transmit a first configuration to the user equipment (UE) for the UE to store or report the first information.

11. The NE of claim 10, 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 distance between the UE and the reference location of the source cell at the time of handover initiation; At least one second threshold, which is related to the distance between the UE and the mobile reference position of the source cell at the time of handover initiation; At least one third threshold, which is related to the distance between the UE and the reference location of the source cell when the handover is successful; At least one fourth threshold, which is related to the distance between the UE and the mobile reference position of the source cell when the handover is successful; At least one fifth threshold, which is related to the distance between the UE and the reference location of the target cell or candidate target cell at the time of handover initiation; At least one sixth threshold, which is related to the distance between the UE and the mobile reference position of the target cell or the candidate target cell at the time of handover initiation; At least one seventh threshold, which is related to the distance between the UE and the reference location of the target cell or the candidate target cell when the handover is successful; At least one eighth threshold, which is related to the distance between the UE and the moving reference position of the target cell or the candidate target cell when the handover is successful; At least one ninth threshold, which is related to the duration between when the location-based conditional handover CHO execution condition configured for the cell is met and when the measurement-based CHO execution condition configured for the cell is met; At least one timer T310 related threshold; At least one timer T312 related threshold; or At least one timer T304 related threshold.

12. The NE of claim 9, wherein the first information comprises at least one of the following: At least one set of community types; The distance between the user equipment (UE) and the reference location of the source cell at the start of handover; The distance between the UE and the mobile reference position of the source cell when the handover is initiated; The distance between the UE and the reference position of the source cell when the handover is successful; The distance between the UE and the mobile reference position of the source cell when the handover is successful; The distance between the UE and the reference position of the target cell or candidate target cell when the handover is initiated; The distance between the UE and the movement reference position of the target cell or the candidate target cell when the handover is initiated; The distance between the UE and the reference position of the target cell or the candidate target cell when the handover is successful; The distance between the UE and the moving reference position of the target cell or the candidate target cell when the handover is successful; The reason value used for the first information; At least one location-based conditional switching CHO execution condition; The first type of CHO execution condition to be satisfied; Secondly, the type of CHO execution condition that needs to be met; The distance between the UE and the reference location of the source cell when the location-based CHO execution conditions are met; The distance between the UE and the mobile reference position of the source cell when the location-based CHO execution condition is met; The distance between the UE and the reference location of the target cell or the candidate target cell when the location-based CHO execution conditions are met; The distance between the UE and the moving reference position of the target cell or the candidate target cell when the location-based CHO execution conditions are met; The distance between the UE and the reference position of the source cell when the measurement-based CHO execution conditions are met; The distance between the UE and the moving reference position of the source cell when the measurement-based CHO execution conditions are met; The distance between the UE and the reference position of the target cell or the candidate target cell when the measurement-based CHO execution conditions are met; The distance between the UE and the moving reference position of the target cell or the candidate target cell when the measurement-based CHO execution conditions are met; When the location-based CHO execution conditions are met, one or more measurement results of the source cell, the target cell, or the candidate target cell are obtained. When the measurement-based CHO execution conditions are met, one or more measurement results of the source cell, the target cell, or the candidate target cell are obtained. Indicates whether satellite exchange with a resynchronization procedure is configured; The time elapsed between when the location-based CHO execution conditions are met and when the latest Radio Resource Control (RRC) reconfiguration message is received; The time elapsed between when the measurement-based CHO execution conditions are met and when the latest Radio Resource Control (RRC) reconfiguration message is received; The duration between when the location-based CHO execution conditions configured for the cell are met and when the measurement-based CHO execution conditions configured for the cell are met; The time elapsed between when the measurement-based CHO execution conditions are met and when the switch is successful; The time elapsed between when the location-based CHO execution conditions are met and when the switch is successful; The order in which the location-based CHO execution conditions and the measurement-based CHO execution conditions are triggered; The radio link has been interrupted since the handover was initiated or when the handover was successful; or The information indicates that the radio link interruption is due to radio link quality issues or feeder link switching.

13. The NE of claim 9, wherein the processor of the NE is configured to receive optional UE capability information from a user equipment (UE) for supporting the storage or reporting of the first information.

14. 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 occurring in a mobility procedure within a non-terrestrial network (NTN), information related to the connection failure is stored.

15. The UE of claim 14, wherein the information related to the connection failure includes at least one of the following: At least one set of community types; The distance between the UE and the reference location of the source cell at the time of handover initiation; The distance between the UE and the mobile reference position of the source cell when the handover is initiated; The distance between the UE and the reference position of the source cell when the connection failure occurs; The distance between the UE and the mobile reference position of the source cell when the connection failure occurs; The distance between the UE and the reference position of the target cell or candidate target cell when the handover is initiated; The distance between the UE and the movement reference position of the target cell or the candidate target cell when the handover is initiated; The distance between the UE and the reference position of the target cell or the candidate target cell when the connection failure occurs; The distance between the UE and the moving reference position of the target cell or the candidate target cell when the connection failure occurs; At least one location-based conditional switching CHO execution condition; The first type of CHO execution condition to be satisfied; or Secondly, the type of CHO execution condition that needs to be met; Indicates whether satellite exchange with a resynchronization procedure is configured; Information indicating whether the measurement-based CHO execution conditions configured for the cell are met when the connection failure occurs; Information indicating whether the location-based CHO execution conditions configured for the cell are met when the connection failure occurs; The order in which the location-based CHO execution conditions and the measurement-based CHO execution conditions are triggered; The radio link has been interrupted since the handover was initiated; or The information indicates that the radio link interruption is due to radio link quality issues or feeder link switching.

16. The UE of claim 15, wherein if the first satisfied CHO execution condition is the location-based CHO execution condition and if only the location-based CHO execution condition is satisfied before the connection failure occurs, then the information related to the connection failure further includes at least one of the following: The identifier ID associated with the first cell whose location-based CHO execution conditions are met but whose measurement-based CHO execution conditions are not met; The distance between the UE and the reference location of the source cell when the location-based CHO execution conditions are met; The distance between the UE and the mobile reference position of the source cell when the location-based CHO execution condition is met; The distance between the UE and the reference location of the first cell or other candidate target cells when the location-based CHO execution conditions are met; The distance between the UE and the first cell or other candidate target cells when the location-based CHO execution conditions are met; One or more measurement results of the source cell when the location-based CHO execution conditions are met; When the location-based CHO execution conditions are met, one or more measurement results of the first cell or other candidate target cells; The time elapsed between when the location-based CHO execution conditions are met and when the latest conditional reconfiguration is received; or The time elapsed between when the location-based CHO execution conditions are met and when the connection failure occurs.

17. The UE of claim 15, wherein if the first satisfied CHO execution condition is the measurement-based CHO execution condition and if only the measurement-based CHO execution condition is satisfied before the connection failure occurs, then the information related to the connection failure further includes at least one of the following: The identifier ID associated with the second cell whose measurement-based CHO execution conditions are met but whose location-based CHO execution conditions are not met; The distance between the UE and the reference position of the source cell when the measurement-based CHO execution conditions are met; The distance between the UE and the mobile reference position of the source cell when the measurement-based CHO execution conditions are met; The distance between the UE and the reference location of the second cell or other candidate target cells when the measurement-based CHO execution conditions are met; The distance between the UE and the second cell or other candidate target cells when the measurement-based CHO execution conditions are met; When the measurement-based CHO execution conditions are met, one or more measurement results of the source cell are obtained. When the measurement-based CHO execution conditions are met, one or more measurement results of the second cell or other candidate target cells; The time elapsed between when the measurement-based CHO execution conditions are met and when the latest conditional reconfiguration is received; or The time elapsed between when the measurement-based CHO execution conditions are met and when the connection failure occurs.

18. The UE of claim 15, wherein if both the location-based CHO execution condition and the measurement-based CHO execution condition are satisfied before the connection failure occurs, then: The first CHO execution condition to be met is one of the location-based CHO execution condition and the measurement-based CHO execution condition. The second CHO execution condition to be satisfied is either the location-based CHO execution condition or the measurement-based CHO execution condition, and The information related to the connection failure further includes at least one of the following: The identifier ID associated with the third cell whose location-based CHO execution conditions are met and whose measurement-based CHO execution conditions are met; The distance between the UE and the reference position of the source cell when the first CHO execution condition is met; The distance between the UE and the mobile reference position of the source cell when the first CHO execution condition is met; The distance between the UE and the reference position of the third cell or other candidate target cells when the first CHO execution condition is met; The distance between the UE and the third cell or other candidate target cell when the first CHO execution condition is met; The distance between the UE and the reference position of the source cell when the second CHO execution condition is met; The distance between the UE and the mobile reference position of the source cell when the second CHO execution condition is met; The distance between the UE and the reference position of the third cell or other candidate target cells when the second CHO execution condition is met; The distance between the UE and the moving reference position of the third cell or other candidate target cell when the second CHO execution condition is met; When the first CHO execution condition is met, one or more measurement results of the source cell are obtained; When the second CHO execution condition is met, one or more measurement results of the third cell or other candidate target cells are obtained. The time elapsed between when the first CHO execution condition is met and when the latest condition reconfiguration is received; The time elapsed between when the second CHO execution condition is met and when the latest condition reconfiguration is received; The time elapsed between when the first CHO execution condition is met and when the second CHO execution condition is met; The time elapsed between when the first CHO execution condition is met and when the connection failure occurs; or The time elapsed between when the second CHO execution condition is met and when the connection failure occurs.

19. 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: Stores information related to non-terrestrial networks (NTNs); and The NTN-related information is transmitted via random access RA reports.

20. The UE of claim 19, wherein the NTN-related information comprises at least one of the following: At least one cell of the UE, a set of cell types; epochal time; ephemeris information; Scheduling offsets used for timing relationships modified for NTN; Scheduling offset provided by the network equipment NE when downlink and uplink frame timings are not aligned at the NE; Polarization information used for downlink transmission on the service link; Polarization information used for uplink service links; The validity period of the auxiliary information configured by the NE; Publicly scheduled advance TA value; The drift rate of the common TA value; The drift rate change of the common TA value; Information indicating whether the UE is configured to report TA values; or Information indicating whether event-triggered reporting of the TA value is supported.

Images