Systems and methods related to non-terrestrial networks

Abstract

Systems and methods for self-organizing network (SON) and / or minimization of drive tests (MDT) enhancements for non-terrestrial networks (NTN) are provided. A wireless communication device can transmit an uplink (UL) message to a wireless communication node. The UL message can include information related to a non-terrestrial network (NTN).

Description

Technical Field

[0001] This disclosure generally relates to wireless communications, including but not limited to systems and methods for enhancing self-organizing networks (SON) and / or minimization of drive test (MDT) for non-terrestrial networks (NTNs). Background Technology

[0002] The Third Generation Partnership Project (3GPP), the standards organization, is currently working on developing a new radio interface called 5G New Radio (5G NR) and a next-generation packet core network (NG-CN or NGC). 5G NR will have three main components: the 5G Access Network (5G-AN), the 5G Core Network (5GC), and user equipment (UE). To facilitate the implementation of different data services and needs, the elements of the 5GC (also known as network functions) have been simplified: some are software-based, while others are hardware-based, allowing for adaptation as needed. Satellite communication is a typical scenario for non-terrestrial networks in 3GPP standardization. Summary of the Invention

[0003] The exemplary embodiments disclosed herein are intended to address problems related to one or more of the problems presented in the prior art and provide additional features that will become apparent when taken into account in conjunction with the following drawings and by reference to the following detailed description. Exemplary systems, methods, apparatuses, and computer program products are disclosed herein according to various embodiments. However, it should be understood that these embodiments are presented by way of example only and are not restrictive, and that various modifications can be made to the disclosed embodiments while remaining within the scope of this disclosure, as will be apparent to those skilled in the art who have read this disclosure.

[0004] At least one aspect relates to a system, method, apparatus, or computer-readable medium that can transmit uplink (UL) messages (e.g., UE information response messages) to wireless communication nodes (e.g., gNBs or base stations (BSs)). The UL messages may include information related to non-terrestrial networks (NTNs). In some embodiments, the wireless communication device (e.g., the user equipment (UE)) can receive configuration information (e.g., Logged Measurement Configuration) from the wireless communication node (e.g., gNB or base station (BS)) for optimizing network performance.

[0005] In some embodiments, the information may include an indication that the cell associated with at least one of the wireless communication devices or wireless communication nodes is part of an NTN. In some embodiments, the information may include at least one of the following: frequency information of the cell, or an indication of whether the cell is part of an NTN. In some embodiments, the cell may include at least one of the following: the serving cell that performed the recorded measurement in a recorded measurement report; at least one neighboring cell that performed the recorded measurement in the recorded measurement report; the cell that obtained the last measurement result in a connection failure report; in which a connection establishment failure or connection recovery failure occurred; at least one neighboring cell that obtained the last measurement result in a connection failure report, in which a connection establishment failure or connection recovery failure occurred; the primary cell (PCell) that detected a radio link failure (RLF) in a radio link failure report, or the target PCell for handover in case of failure; at least one candidate target cell for conditional handover in case of connection failure in a radio link failure report; the candidate target cell selected by the wireless communication device for conditional handover (CHO) in a radio link failure report; in evolved universal terrestrial radio access (ETH), In a UTRA radio link failure report, the PCell that detected the radio link failure, or the source PCell of the handover failure; in a radio link failure report, at least one neighboring E-UTRA cell that obtained the last measurement result when the radio link failure or handover failure occurred; in a radio link failure report, at least one neighboring new radio (NR) cell that obtained the last measurement result when the radio link failure or handover failure occurred; in a radio link failure report, the source PCell of the last handover; in a radio link failure report, the PCell in which the wireless communication device failed to perform the fast master cell group (MCG) recovery procedure or successfully performed the fast MCG recovery procedure; in a radio link failure report, the cell in which the wireless communication device returned to the connected state after a connection failure and after failing to perform a reconstruction; in a radio link failure report, the cell in which a reconstruction attempt was made after a connection failure; in a successful handover report, the target PCell of the handover that generated the successful handover report; in a successful handover report, the target E-UTRA cell in which the successful handover triggered the handover report. PCell; In a successful handover report, the last measurement result is at least one neighboring NR cell obtained during the successful handover execution; The source PCell of the handover that triggered the successful handover report; The target PCell of the handover that triggered the successful handover report; The last measurement is at least one neighboring cell obtained during a successful change or addition of the primary SCG cell (PSCell) in a secondary cell group (SCG); In a successful PSCell report, the PCell to which the wireless communication device is connected during the successful PSCell change or addition; In a successful PSCell report, the source PSCell of the successful PSCell change; In a successful PSCell report, the target PSCell of the successful PSCell change; or the most recently visited cell in mobility history information.

[0006] In some embodiments, the information may include at least one NTN-related measurement parameter. At least one NTN-related measurement parameter may include at least one of the following: an indication of the type of NTN-related measurement performed in the RRC_IDLE state and / or RRC_INACTIVE state, wherein the NTN-related measurement is a location-based measurement or a time-based measurement; an indication of a distance threshold for initiating location-based measurements in the RRC_IDLE state and / or RRC_INACTIVE state; an indication of the reference location of the serving cell at a time reference for initiating location-based measurements in the RRC_IDLE state and / or RRC_INACTIVE state; or a list of TN coverage area information for assisting NTN user equipment (UE) in the RRC_IDLE and / or RRC_INACTIVE state to skip terrestrial network (TN) measurements.

[0007] In some embodiments, the information may include at least one NTN-related parameter. The at least one NTN-related parameter may include at least one of the following: time information about when a cell, provided by the NTN system, ceases to serve the area currently covered by the cell; an indication of whether a recently performed handover was an intra-NTN handover; an indication of whether a connection failure was caused by a failure in an intra-NTN handover or a failure in an intra-NTN radio link; or a list of neighboring NTN cells.

[0008] In some embodiments, the information may include time-based Conditional Handover (CHO) information or location-based CHO information. In some embodiments, the time-based information may include at least one of the following: an indication of absolute time when a radio link failure (RLF) or handover failure is caused by a time-based CHO; an indication of absolute time when a successful handover is detected by a time-based CHO; an indication of a time threshold for the time-based CHO; an indication of the duration for defining the leave condition for the time-based CHO; an indication of the last handover performed before the last detected connection failure that was a time-based CHO; an indication that the last handover performed before the last detected connection failure was a time-based CHO performed via a random access channel (RACH); an indication of whether the connection failure was caused by a time-based CHO; or an indication of whether the connection failure was caused by a time-based CHO performed via a RACH. In some embodiments, location-based CHO information may include at least one of the following: an indication of the location of the wireless communication device when a wireless link failure (RLF) or handover failure is caused by a location-based CHO; an indication of the approximate location of the wireless communication device when a wireless link failure (RLF) or handover failure is caused by a location-based CHO; an indication of the location of the wireless communication device when a successful handover is detected by a location-based CHO; an indication of the approximate location of the wireless communication device when a successful handover is detected by a location-based CHO; an indication of one or more reference locations for the location-based CHO; an indication of one or more distance thresholds for the location-based CHO; an indication of the distance between the wireless communication device and the one or more reference locations when the RLF, the handover failure, or the successful handover is detected by a location-based CHO; an indication of the last handover performed before the last detected connection failure; or an indication of whether the connection failure was caused by a location-based CHO.

[0009] In some embodiments, the configuration information may include a measurement configuration for recording for at least one NTN cell. The measurement configuration for recording may include at least one of the following: a list of tracking area codes for a tracking area identifier in a region configuration for recording measurements; a region configuration for the NTN system, wherein the region configuration includes a reference location and a distance threshold; or at least one coordinate point for marking the region configuration for recording measurements. This application provides a region configuration for an NTN system. A reference location and a distance threshold may exist. When the distance between the UE and the reference location is less than the distance threshold, the UE may perform the recorded measurement. This application provides one or more coordinate points to mark the region configuration for recording measurements. In a particular embodiment, this application provides a region configuration for an NTN system. A reference location and a distance threshold may exist. When the distance between the UE and the reference location is less than the distance threshold, the UE may skip the recorded measurement.

[0010] In some embodiments, the information may include no random access channel (RACH) handover information. No RACH handover information may include at least one of the following: an indication that the last handover performed was a no RACH handover; an indication of whether the connection failure was caused by a no RACH handover failure; or at least one no RACH handover related parameter.

[0011] In some embodiments, at least one RACH-free handover-related parameter may include at least one of the following: an indication of the reference signal received power (RSRP) for selecting synchronization signal blocks (SSBs) for pre-allocated uplink grants; an initial value of the grant retransmission timer configured for the initial uplink transmission of the RACH-free handover; a set of demodulation reference signal (DMRS) ports for the RACH-free handover SSB-to-physical uplink shared channel (PUSCH) mapping; the number of DMRS sequences for the RACH-free handover SSB-to-PUSCH mapping; a threshold for the RSRP configured for the RACH-free handover SSB selection for the pre-allocated uplink grant; the number of SSBs for each pre-allocated uplink grant PUSCH for the RACH-free handover; or a subset of SSBs for SSB-to-CG PUSCH mapping within the configured grant (CG) configuration for the RACH-free handover.

[0012] In some embodiments, the information may include information about the satellite handover process. In some embodiments, the information about the satellite handover process may include at least one of the following: an indicator of whether the random access procedure was initiated for a satellite handover with a resynchronization process; an indication of whether a radio link failure (RLF) was caused by consecutive satellite handovers with a resynchronization process; or at least one parameter regarding the satellite handover with a resynchronization process. At least one parameter regarding the satellite handover with a resynchronization process may include at least one of the following: an indication of the time from the last satellite handover with resynchronization until the loss of UL synchronization due to the satellite handover with the resynchronization process; an indication of the absolute time at which the UL synchronization was lost due to the satellite handover with the resynchronization process; an indication of the effective duration of NTN-related auxiliary information; the number of the most recent consecutive satellite handover failures with a resynchronization process; an indication of the absolute time at which the satellite handover with the resynchronization process was obtained; an indication of the time from the first loss of UL synchronization due to the satellite handover with the resynchronization process until the UL synchronization was obtained; or the source satellite. Indication of Physical Cell Identifier (PCI); indication of the target satellite's PCI; indication of the type of satellite handover as soft satellite handover; indication of the type of satellite handover as hard satellite handover; indication of whether the satellite handover was performed via a resynchronization process; indication of whether the satellite handover was performed via a resynchronization process without a random access procedure; indication of the time offset between the synchronization signal block (SSB) from the source satellite and the SSB from the target satellite at the uplink time synchronization reference point; indication of time information regarding when the target satellite will begin serving the area currently covered by the serving satellite; or indication of time information regarding when the cell, provided by the NTN system, will cease serving the area currently covered by the cell.

[0013] In some embodiments, the information may include satellite information of the first cell. The satellite information may include at least one of the following: an indication of the absolute time when the satellite will begin serving the first cell; ephemeris information of the satellite indicating when it will begin serving the first cell; or an indication of the epoch time of the satellite used for NTN auxiliary information of the first cell. In some embodiments, the first cell may include at least one of the following: the serving cell that performed the recorded measurement in the recorded measurement report; at least one neighboring cell that performed the recorded measurement in the recorded measurement report; the cell that obtained the last measurement result in the connection failure report; in which a connection establishment failure or connection recovery failure occurred; at least one neighboring cell that obtained the last measurement result in the connection failure report, in which a connection establishment failure or connection recovery failure occurred; the primary cell (PCell) that detected the radio link failure (RLF) in the radio link failure report, or the target PCell for handover failure; the candidate target cell for conditional handover in the radio link failure report when a connection fails; the candidate target cell selected by the wireless communication device for conditional handover (CHO) in the radio link failure report; in the evolved Universal Terrestrial Radio Access (ETH)... In a UTRA radio link failure report, the PCell that detected the radio link failure, or the source PCell of the handover failure; in a radio link failure report, at least one neighboring E-UTRA cell that obtained the last measurement result when the radio link failure or handover failure occurred; in a radio link failure report, at least one neighboring New Radio (NR) cell that obtained the last measurement result when the radio link failure or handover failure occurred; in a radio link failure report, the source PCell of the last handover; in a radio link failure report, the PCell in which the wireless communication device failed to perform a Fast Primary Cell Group (MCG) recovery procedure or successfully performed a Fast MCG recovery procedure; in a radio link failure report, the cell in which the wireless communication device returned to the connected state after a connection failure and after failing to perform a reconstruction; in a radio link failure report, the cell in which a reconstruction attempt was made after a connection failure; in a successful handover report, the target PCell of the handover that generated the successful handover report; in a successful handover report, the target E-UTRA cell in which the successful handover triggered the handover report. PCell; In a successful handover report, the last measurement result is at least one neighboring NR cell obtained when the successful handover is performed; The source PCell of the handover that triggered the successful handover report; The target PCell of the handover that triggered the successful handover report; The last measurement is at least one neighboring cell obtained when a successful change or addition of the primary cell (PSCell) in a secondary cell group (SCG) is performed; In a successful PSCell report, the PCell to which the wireless communication device is connected at the time of the successful PSCell change or addition; In a successful PSCell report, the source PSCell of the successful PSCell change; In a successful PSCell report, the target PSCell of the successful PSCell change; or the most recently visited cell in the mobility history information.

[0014] In some embodiments, the information may include at least one of the following: a radio link failure report when a radio link failure is detected; a successful handover report when a successful handover is detected; a report stored during the satellite handover process; a report of recorded measurement results; a connection failure report; or a report of mobility history information. In some embodiments, the information may include the duration of stay in the NTN cell.

[0015] In some embodiments, the wireless communication device may receive a request for a UL message from a wireless communication node. The wireless communication device may then send a UL message to the wireless communication node upon request.

[0016] In some embodiments, a wireless communication node (e.g., a gNB or base station (BS)) may receive uplink (UL) messages from a wireless communication device (e.g., a user equipment (UE)). The UL message may include information related to a non-terrestrial network (NTN). In some embodiments, the wireless communication node (e.g., a gNB or base station (BS)) may send configuration information to the wireless communication device (e.g., a user equipment (UE)) for optimizing network performance. Attached Figure Description

[0017] Various exemplary embodiments of this solution are described in detail below with reference to the following figures or drawings. These figures are provided for illustrative purposes only and depict only exemplary embodiments of this solution to aid the reader's understanding of it. Therefore, these figures should not be considered as limitations on the breadth, scope, or applicability of this solution. It should be noted that these figures are not necessarily drawn to scale for clarity and ease of explanation.

[0018] Figure 1 An example cellular communication network that can implement the techniques disclosed herein is shown according to embodiments of the present disclosure; Figure 2 Block diagrams of example base stations and user equipment according to some embodiments of the present disclosure are shown; Figure 3 A flowchart is shown of an example method for enhancements related to non-terrestrial networks (NTNs) according to embodiments of this disclosure. Detailed Implementation

[0019] Mobile communication technology and environment Figure 1 An example wireless communication network and / or system 100 according to an embodiment of this disclosure is illustrated, in which the technologies disclosed herein can be implemented. In the following discussion, the wireless communication network 100 can be any wireless network, such as a cellular network or a narrowband Internet of Things (NB-IoT) network, and is referred to herein as network 100. Such an example network 100 includes base stations 102 (hereinafter referred to as "BS 102", also called wireless communication nodes) and user equipment 104 (hereinafter referred to as "UE 104", also called wireless communication devices) that can communicate with each other via communication links 110 (e.g., wireless communication channels), and a cluster of cells 126, 130, 132, 134, 136, 138, and 140 covering a geographic area 101. Figure 1In this context, BS 102 and UE 104 are included within the corresponding geographical boundaries of cell 126. Each of the other cells 130, 132, 134, 136, 138, and 140 may include at least one base station operating on its allocated bandwidth to provide sufficient radio coverage to the intended users of that cell.

[0020] For example, BS 102 can operate on the allocated channel transmission bandwidth to provide sufficient coverage to UE 104. BS 102 and UE 104 can communicate via downlink radio frame 118 and uplink radio frame 124, respectively. Each radio frame 118 / 124 can also be divided into subframes 120 / 127, which can include data symbols 122 / 128. In this disclosure, BS 102 and UE 104 are generally described herein as non-limiting examples of "communication nodes" capable of practicing the methods disclosed herein. According to various embodiments of this solution, such communication nodes may be capable of wireless and / or wired communication.

[0021] Figure 2 A block diagram of an example wireless communication system 200 for transmitting and receiving wireless communication signals (e.g., OFDM (orthogonal frequency division multiplexing) / OFDMA (orthogonal frequency division multiple access) signals) according to some embodiments of this solution is shown. System 200 may include components and elements configured to support known or conventional operating features that do not need to be described in detail herein. In one exemplary embodiment, system 200 may be configured to... Figure 1 The wireless communication environment 100 is a wireless communication environment in which communication (e.g., transmission and reception) data symbols are as described above.

[0022] System 200 generally includes base station 202 (hereinafter referred to as "BS 202") and user equipment 204 (hereinafter referred to as "UE 204"). BS 202 includes BS (base station) transceiver module 210 (hereinafter also referred to as transceiver module 210, transceiver 210 or base station transceiver 210), BS antenna 212 (hereinafter also referred to as antenna 212, downlink antenna 212 or RF antenna arrangement 212), BS processor module 214 (hereinafter also referred to as processor module 214), BS memory module 216 (hereinafter also referred to as memory module 216) and network communication module 218, each module being coupled and interconnected to each other as needed via data communication bus 220. UE 204 includes a UE (User Equipment) transceiver module 230 (hereinafter also referred to as UE transceiver 230, transceiver module 230, or transceiver 230), a UE antenna 232 (hereinafter also referred to as antenna 232, uplink antenna 232, or RF antenna arrangement 232), a UE memory module 234 (hereinafter also referred to as memory module 234), and a UE processor module 236 (hereinafter also referred to as processor module 236). Each module is coupled to and interconnected with each other as needed via a data communication bus 240. BS 202 communicates with UE 204 via a communication channel 250 (hereinafter also referred to as: wireless transmission link 250, wireless data communication link 250), which may be any wireless channel or other medium suitable for the data transmission described herein.

[0023] As those skilled in the art will understand, system 200 may also include, in addition to Figure 2 Any number of modules other than those shown herein. Those skilled in the art will understand that the various illustrative blocks, modules, circuits, and processing logic described in conjunction with the embodiments disclosed herein can be implemented in hardware, computer-readable software, firmware, or any practical combination thereof. To clearly illustrate this interchangeability and compatibility of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps are described generally according to their functionality. Whether this functionality is implemented as hardware, firmware, or software may depend on the specific application and design constraints imposed on the system as a whole. Those skilled in the art described herein can implement such functionality in a suitable manner for each specific application; however, such implementation decisions should not be construed as limiting the scope of this disclosure.

[0024] According to some embodiments, UE transceiver 230 may be referred to herein as an "uplink" transceiver 230 including a radio frequency (RF) transmitter and an RF receiver, each RF transmitter and RF receiver including circuitry coupled to antenna 232. A duplex switch (not shown) may alternatively couple the uplink transmitter or receiver to the uplink antenna in a time-division duplex manner. Similarly, according to some embodiments, BS transceiver 210 may be referred herein as a "downlink" transceiver 210 including an RF transmitter and an RF receiver, each RF transmitter and RF receiver including circuitry coupled to antenna 212. A downlink duplex switch may alternatively couple the downlink transmitter or receiver to downlink antenna 212 in a time-division duplex manner. The operation of the two transceiver modules 210 and 230 may be time-coordinated such that while the downlink transmitter is coupled to downlink antenna 212, the uplink receiver circuitry is coupled to uplink antenna 232 to receive transmissions via wireless transmission link 250. Conversely, the operation of the two transceivers 210 and 230 can be coordinated in time such that the downlink receiver is coupled to the downlink antenna 212 to receive transmissions on the wireless transmission link 250 while the uplink receiver is coupled to the uplink antenna 232. In some embodiments, there is tight time synchronization with a minimum guard time between changes in the duplex direction.

[0025] UE transceiver 230 and base transceiver 210 are configured to communicate via wireless data communication link 250 and cooperate with RF antenna arrangements 212 / 232 appropriately configured to support specific wireless communication protocols and modulation schemes. In some illustrative embodiments, UE transceiver 210 and base transceiver 210 are configured to support industry standards such as Long Term Evolution (LTE) and emerging 5G standards. However, it should be understood that this disclosure is not necessarily limited to application to specific standards and associated protocols. Rather, UE transceiver 230 and base transceiver 210 may be configured to support alternative or additional wireless data communication protocols (including future standards or variations thereof).

[0026] According to various embodiments, BS 202 may be, for example, an evolved Node B (eNB), a serving eNB, a target eNB, a femto station, or a pico station. In some embodiments, UE 204 may be embodied in various types of user equipment, such as mobile phones, smartphones, personal digital assistants (PDAs), tablets, laptops, wearable computing devices, etc. Processor modules 214 and 236 may be implemented or realized using the following devices designed to perform the functions described herein: general-purpose processors, content-addressable memory, digital signal processors, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), any suitable programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination thereof. In this way, the processor may be implemented as a microprocessor, a controller, a microcontroller, a state machine, etc. The processor may also be implemented as a combination of multiple computing devices, such as a combination of a digital signal processor and a microprocessor, a combination of multiple microprocessors, a combination of one or more microprocessors coupled with a digital signal processor core, or any other such configuration.

[0027] Furthermore, the steps of the methods or algorithms described in conjunction with the embodiments disclosed herein can be directly implemented in hardware, firmware, software modules executed by processor modules 214 and 236 respectively, or any practical combination thereof. Storage modules 216 and 234 can be implemented as random access memory (RAM), flash memory, read-only memory (ROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), registers, hard disks, removable disks, optical disc read-only memory (CD-ROM), or any other form of storage medium known in the art. In this respect, storage modules 216 and 234 can be coupled to processor modules 210 and 230 respectively, such that processor modules 210 and 230 can read information from and write information to storage modules 216 and 234 respectively. Storage modules 216 and 234 can also be integrated into their respective processor modules 210 and 230. In some embodiments, memory modules 216 and 234 may each include cache memory for storing temporary variables or other intermediate information during the execution of instructions to be executed by processor modules 210 and 230, respectively. Memory modules 216 and 234 may also each include non-volatile memory for storing instructions to be executed by processor modules 210 and 230, respectively.

[0028] Network communication module 218 broadly represents the hardware, software, firmware, processing logic, and / or other components of base station 202 that enable bidirectional communication between base station transceiver 210 and other network components and communication nodes configured to communicate with base station 202. For example, network communication module 218 may be configured to support Internet or WiMAX (World Interoperability for Microwave Access) services. In a typical but non-limiting deployment, network communication module 218 provides an 802.3 Ethernet interface, allowing base station transceiver 210 to communicate with traditional Ethernet-based computer networks. In this way, network communication module 218 may include a physical interface for connecting to a computer network (e.g., a Mobile Switching Center (MSC)). The terms “configured for,” “configured to,” and their various variations used in this document in relation to a specified operation or function refer to devices, components, circuits, structures, machines, signals, etc., that are physically constructed, programmed, formatted, and / or arranged to perform the specified operation or function.

[0029] The Open Systems Interconnection (OSI) model (referred to herein as the "OSI model") is a conceptual and logical layout that defines network communications used by systems (e.g., wireless communication devices, wireless communication nodes) for interconnecting and communicating with other systems. The model is divided into seven sub-components or layers, each representing a conceptual set of services provided to its upper and lower layers. The OSI model also defines logical networks and effectively describes computer packet transmission using different layer protocols. The OSI model may also be referred to as the seven-layer OSI model or the seven-layer model. In some embodiments, the first layer may be the physical layer. In some embodiments, the second layer may be the Medium Access Control (MAC) layer. In some embodiments, the third layer may be the Radio Link Control (RLC) layer. In some embodiments, the fourth layer may be the Packet Data Convergence Protocol (PDCP) layer. In some embodiments, the fifth layer may be the Radio Resource Control (RRC) layer. In some embodiments, the sixth layer may be the Non-Access Stratum (NAS) layer or the Internet Protocol (IP) layer, and the seventh layer may be any other layer.

[0030] Various exemplary embodiments of the present solution are described below with reference to the accompanying drawings to enable those skilled in the art to formulate and use the present solution. As will be apparent to those skilled in the art, various changes or modifications can be made to the examples described herein without departing from the scope of the present solution after reading this disclosure. Therefore, the present solution is not limited to the exemplary embodiments and applications described and illustrated herein. Furthermore, the specific order or hierarchy of the steps in the methods disclosed herein is merely illustrative. Based on design preferences, the specific order or hierarchy of the steps of the disclosed methods or processes can be rearranged while remaining within the scope of the present solution. Therefore, those skilled in the art will understand that the methods and techniques disclosed herein present various steps or actions in an exemplary order, and unless otherwise expressly stated, the present solution is not limited to the specific order or hierarchy presented.

[0031] Systems and methods for enhancing non-terrestrial networks (NTN) Self-Organizing Networks (SON) can encompass solutions for network self-configuration and self-optimization. It can be an automated technology designed to simplify and accelerate the planning, configuration, management, optimization, and repair of mobile radio access networks. The goal of SON technology is to achieve network self-configuration, self-optimization, and / or self-repair. Self-configuration may refer to the automatic deployment of newly added network elements and the determination of appropriate parameter configurations for these elements. In the initial network deployment phase, self-configuration technology can enable plug-and-play deployment of base stations. As network operational data accumulates, self-optimization and self-repair can be achieved to a certain extent with the help of artificial intelligence algorithms. Self-optimization may involve automatically optimizing various aspects of the network during operation, such as coverage, capacity, and user perception, without human intervention. Examples may include load balancing, handover optimization, automatic neighbor cell relationships, coverage and capacity optimization, inter-cell interference coordination, and energy saving. Self-repair may refer to the automation of fault management and fault correction processes to maintain normal network operation.

[0032] Self-Organizing Network (SON) and Minimum Drive Test (MDT) capabilities supported by 5G NR can include mobility robustness optimization (MRO), mobility load balancing (MLB), random access channel (RACH) optimization, MDT, and / or L2 measurement. Mobility robustness optimization (MRO) can detect and correct mobility-related issues, including connection failures caused by intra- or inter-system mobility, unnecessary inter-system handovers, and / or inter-system ping-pong handovers. MRO can also provide methods to distinguish these issues from New Radio (NR) coverage-related problems and other mobility-independent issues. Mobility load balancing (MLB) can refer to the even distribution of load between cells and cell areas, diverting some traffic from congested cells or cell areas, and / or removing some traffic from cells, cell areas, operators, or different systems to achieve network energy savings.

[0033] Minimized road testing (MDT) primarily involves obtaining relevant parameters for network optimization by collecting measurement reports from mobile terminals or from base stations. Its aim is to reduce the operational costs of network optimization and maintenance for operators. Compared to traditional road testing, MDT offers advantages such as energy savings, reduced testing costs, and shorter optimization cycles, thereby improving user satisfaction. Furthermore, MDT can collect measurement information from entire areas (e.g., narrow roads, forests, private locations) that traditional driving tests cannot capture.

[0034] Considering the tangible commercial benefits, as well as stability and technological maturity, enhancements to SON / MDT are being considered for certain new features, such as MRO enhancements for lower-layer triggered mobility (LTM), conditional handover (CHO) with candidate secondary cell groups (SCGs) and subsequent primary cell addition and change (CPAC) for conditional SCGs, SON / MDT enhancements for intra-NTN mobility, and / or network slicing.

[0035] From a global network coverage perspective, over 80% of land area and 95% of ocean area are not covered by terrestrial cellular networks. 5G networks can provide not only high-speed internet but also ubiquitous mobile network access. However, in remote areas such as mountains, deserts, and oceans, building and maintaining 5G terrestrial networks can be extremely expensive, making 5G coverage in these areas impossible. Fortunately, advancements in aerospace technology have enabled satellite-based broadband communication systems to provide wireless coverage to vast, even global, areas at a lower cost. Therefore, 5G networks can be deeply integrated with satellite communication systems to form converged communication networks, providing seamless global coverage and meeting diverse service needs worldwide.

[0036] Non-terrestrial networks (NTNs) can be terminal-satellite direct communication technologies based on New Radio (NR) interface technology, and can also serve as an important supplement to terrestrial cellular communication technologies. Through the convergence of satellite communication networks and terrestrial 5G networks, NTNs can provide ubiquitous coverage, unrestricted by terrain and topography, and connect the sky, earth, ocean, and other spaces to form an integrated ubiquitous access network, enabling on-demand access in all scenarios. It can be seen that non-terrestrial networks (NTNs) have been researched, but SON and MDT functions have not yet considered potential NTN deployments. Supporting MROs for NTNs could be beneficial, especially in addressing mobility issues related to NTNs, such as time-based and / or location-based CHOs. This application provides possible solutions for supporting SON / MDTs for NTNs.

[0037] How to indicate that a cell is an NTN cell User equipment (UE) can send uplink (UL) messages to gNB or base stations. UL messages may include information related to non-terrestrial networks (NTN).

[0038] In some embodiments, the information may include at least one of the following: a wireless link failure report when a wireless link failure is detected; a successful handover report when a successful handover is detected; a report of recorded measurement results; a connection failure report; a successful PSCell change or addition report; a report of mobility history information; or a new report stored during the satellite handover process.

[0039] In a particular embodiment, the UE can receive a request for a UL message from a gNB or BS. The UE can then send a UL message to the gNB or BS upon request.

[0040] In some embodiments, the information may include an indication that a cell associated with at least one of the wireless communication devices or wireless communication nodes is part of an NTN. The information may include at least one of the following: frequency information of the cell, or an indication of whether the cell is part of an NTN.

[0041] In some embodiments, a cell may include at least one of the following: a serving cell that performed the recorded measurement in a recorded measurement report; at least one neighboring cell that performed the recorded measurement in the recorded measurement report; a cell that obtained the last measurement result in a connection failure report; in which a connection establishment failure or connection recovery failure occurred; at least one neighboring cell that obtained the last measurement result in a connection failure report, in which a connection establishment failure or connection recovery failure occurred; a primary cell (PCell) that detected a radio link failure (RLF) in a radio link failure report, or a target PCell for handover in failure; at least one candidate target cell for conditional handover in a radio link failure report; a candidate target cell selected by the wireless communication device for conditional handover (CHO) in a radio link failure report; in Evolved Universal Terrestrial Radio Access (ETH). In a UTRA radio link failure report, the PCell that detected the radio link failure, or the source PCell of the handover failure; in a radio link failure report, at least one neighboring E-UTRA cell that obtained the last measurement result when the radio link failure or handover failure occurred; in a radio link failure report, at least one neighboring New Radio (NR) cell that obtained the last measurement result when the radio link failure or handover failure occurred; in a radio link failure report, the source PCell of the last handover; in a radio link failure report, the PCell in which the wireless communication device failed to perform a Fast Primary Cell Group (MCG) recovery procedure or successfully performed a Fast MCG recovery procedure; in a radio link failure report, the cell in which the wireless communication device returned to the connected state after a connection failure and after failing to perform a reconstruction; in a radio link failure report, the cell in which a reconstruction attempt was made after a connection failure; in a successful handover report, the target PCell of the handover that generated the successful handover report; in a successful handover report, the target E-UTRA cell in which the successful handover triggered the handover report. PCell; In a successful handover report, the last measurement result is at least one neighboring NR cell obtained when the successful handover is performed; The source PCell of the handover that triggered the successful handover report; The target PCell of the handover that triggered the successful handover report; The last measurement is at least one neighboring cell obtained when a successful change or addition of the primary cell (PSCell) in a secondary cell group (SCG) is performed; In a successful PSCell report, the PCell to which the wireless communication device is connected at the time of the successful PSCell change or addition; In a successful PSCell report, the source PSCell of the successful PSCell change; In a successful PSCell report, the target PSCell of the successful PSCell change; or the most recently visited cell in the mobility history information.

[0042] In current reports (e.g., Radio Link Failure (RLF) reports, Successful Handover (SHR) reports, Connection Failure (connEstFailReport), Log Meas Report, and SuccessPSCell reports), only the cell identity (ID) can be used to indicate the cell's identification characteristics. To indicate that a cell in the report is an NTN cell, frequency information (e.g., carrierFreq(carrierFreq)IE) can also be added to the report to indicate the cell's identification characteristics.

[0043] RLF reports may include / record information about multiple cells, including the source cell of the last handover (previousPCellId IE), the cell where an RLF was detected (failedPCellId IE), the cell where a reconnection occurred (reconnectCellId IE), the cell where a connection was re-established (reestablishmentCellId IE), the cell associated with a CHO (choCellId IE), and / or the PScell ​​where the UE performed a Primary Cell Group (MCG) recovery procedure (pSCellId IE). To indicate whether these cells are NTN cells, relevant frequency information (e.g., carrierFreq IE) can be provided in the message along with the cell ID.

[0044] SHR reports may include / record information about multiple cells, including the source PCell (sourcePCellId IE) and / or the target PCell (targetPCellId IE) for a successful handover. To indicate whether these cells are NTN cells, relevant frequency information (e.g., carrierFreq IE) can be provided in the message along with the cell ID.

[0045] The ConnEstFail report may include / record the last measurement obtained in the cell to indicate that the cell is an NTN cell, and may provide frequency information (e.g., carrierFreq IE). In some embodiments, to indicate that the cell is an NTN cell, the frequency information (e.g., carrierFreq IE) may be provided along with the cell identifier in the LogMeas report and the SuccessPSCell report.

[0046] In some embodiments, an indication (e.g., 1 bit of information) regarding whether the cell is an NTN cell can be added to the report. In the current report (e.g., RLF report, SHR report, ConnEstFail report, LogMeas report, SuccessPSCell report), only the cell ID can be used to indicate the cell's identifying characteristics. To indicate that a cell in the report is an NTN cell, an indication regarding whether the cell is an NTN cell can be added to the report.

[0047] RLF reports can include / record information about multiple cells, including the source cell of the last handover (previousPCellId IE), the cell where the RLF was detected (failedPCellId IE), the cell where reconnection occurred (reconnectCellId IE), the cell where reconstruction occurred (reestablishmentCellId IE), the cell associated with CHO (choCellId IE), and / or the pScell ​​(pSCellId IE) where the UE performed the MCG recovery procedure. To indicate whether these cells are NTN cells, relevant indications regarding whether a cell is an NTN cell can be provided in the message along with the cell ID.

[0048] SHR reports can include / record information about multiple cells, including the source PCell (sourcePCellId IE) and / or the target PCell (targetPCellId IE) for a successful handover. To indicate whether these cells are NTN cells, relevant indications regarding whether a cell is an NTN cell can be provided in the message along with the cell ID.

[0049] The ConnEstFail report may include / record the last measurement obtained in the cell to indicate that the cell is an NTN cell and provide an indication of whether the cell is an NTN cell. To indicate that the cell is an NTN cell, an indication of whether the cell is an NTN cell can be provided along with the cell identifier in the LogMeas report and the SuccessPSCell report.

[0050] NTN Configuration for Self-Optimization User equipment (UE) can send uplink (UL) messages to gNB or base stations. UL messages may include information related to the non-terrestrial network (NTN). To aid network self-optimization, this information may include at least one NTN-related measurement parameter.

[0051] In some embodiments, the information may include at least one of the following: a wireless link failure report when a wireless link failure is detected; a successful handover report when a successful handover is detected; a report of recorded measurement results; a connection failure report; a successful PSCell change or addition report; a report of mobility history information; or a new report stored during the satellite handover process.

[0052] In a particular embodiment, the UE can receive a request for a UL message from a gNB or BS. The UE can then send a UL message to the gNB or BS based on the request.

[0053] In some embodiments, at least one NTN-related measurement parameter may include at least one of the following: an indication of the type of NTN-related measurement performed in the RRC_IDLE state and / or RRC_INACTIVE state, wherein the NTN-related measurement is a location-based measurement or a time-based measurement; an indication of a distance threshold for initiating location-based measurements in the RRC_IDLE state and / or RRC_INACTIVE state; an indication of the reference location of the serving cell at a time reference for initiating location-based measurements in the RRC_IDLE state and / or RRC_INACTIVE state; a list of TN coverage area information for NTN user equipment (UE) in the auxiliary RRC_IDLE and / or RRC_INACTIVE state to skip terrestrial network (TN) measurements; or time information regarding when a cell, provided by the NTN system, ceases to serve the area currently covered by the cell.

[0054] In some embodiments, the information may include at least one NTN-related parameter. The at least one NTN-related parameter may include at least one of the following: time information about when a cell, provided by the NTN system, ceases to serve the area currently covered by the cell; an indication of whether a recently performed handover was an intra-NTN handover; an indication of whether a connection failure was caused by a failure in an intra-NTN handover or a failure in an intra-NTN radio link; or a list of neighboring NTN cells.

[0055] In some embodiments, the RLF report may include a type / indicator / parameter indicating whether the last handover performed before the most recently detected connection failure was an intra-NTN handover. For example, a value may be added to the lastHO-Type IE. If this field is set (e.g., ntnho), the last handover performed may have occurred between multiple NTN cells. In some embodiments, the RLF report may include types / indicators / parameters indicating whether the connection failure was due to an intra-NTN radio link failure or an intra-NTN handover failure. In some embodiments, values / indicators may be added to the connectionFailureType IE. If this field is set (e.g., ntnrlf, ntnhof), the connection failure may have been due to an intra-NTN radio link failure or an intra-NTN handover failure.

[0056] In some embodiments, since measurement results in the RRC_IDLE state and / or RRC_INACTIVE state can be included in the recorded measurement report, in order to assist gNB in ​​network optimization, information about measurement results in the RRC_IDLE state and / or RRC_INACTIVE state for NTN cells can be included in the recorded measurement report of the UL message.

[0057] In some embodiments, this indicates the type of NTN-related measurement performed in the RRC_IDLE state and / or RRC_INACTIVE state. NTN-related measurements can be location-based or time-based.

[0058] In some embodiments, an indication of a distance threshold for location-based measurement initiation in the RRC_IDLE state and / or RRC_INACTIVE state can be carried in a UL message from the UE to the network.

[0059] In some embodiments, the UL message may carry an indication of the reference location of the serving cell of the NTN Earth Mobile System from the UE to the network at a time reference, the reference location being used to initiate location-based measurements in the RRC_IDLE state and / or RRC_INACTIVE state.

[0060] In some embodiments, an indication from the UE to the network may be carried in the UL message, which is a reference location of the serving cell at a time reference provided via the NTN quasi-geostationary system, the reference location being used to initiate location-based measurements in the RRC_IDLE state and / or RRC_INACTIVE state.

[0061] In some embodiments, the UL message may carry a list of terrestrial network (TN) coverage area information from the UE to the network to assist NTN user equipment (UE) in RRC_IDLE and / or RRC_INACTIVE states in skipping TN measurements. For example, a reference location and a distance radius from the reference location may be used to define the TN coverage area.

[0062] In some embodiments, time information about when a cell, provided by the NTN system, ceases to serve the area currently covered by the cell can be carried from the UE to the network in a UL message.

[0063] In some embodiments, at least one parameter for the UE to access the NR via NTN access can be carried from the UE to the network in the UL message. This at least one parameter may include at least one of the following: ephemeris data, common TA parameters, k_offset, or the effective duration for UL synchronization information and epochs. In some embodiments, a list of NTN neighboring cells, including ntn-Config, carrier frequency, and / or PhysCellId (physical cell ID), can be carried from the UE to the network in the UL message.

[0064] Satellite Information User equipment (UE) can send uplink (UL) messages to gNB or base stations. UL messages can include information related to non-terrestrial networks (NTN). This information may include satellite information.

[0065] In some embodiments, the information may include at least one of the following: a wireless link failure report when a wireless link failure is detected; a successful handover report when a successful handover is detected; a report of recorded measurement results; a connection failure report; a successful PSCell change or addition report; a report of mobility history information; or a new report stored during the satellite handover process.

[0066] In a particular embodiment, the UE can receive a request for a UL message from a gNB or BS. The UE can then send a UL message to the gNB or BS based on the request.

[0067] In some embodiments, satellite information may include at least one of the following: an indication of the absolute time when the satellite will begin serving the cell; the ephemeris information of the satellite when it will begin serving the cell; and the epoch time of the satellite for the cell's NTN auxiliary information.

[0068] In some embodiments, a cell may include at least one of the following: a serving cell that performed the recorded measurement in a recorded measurement report; at least one neighboring cell that performed the recorded measurement in the recorded measurement report; a cell that obtained the last measurement result in a connection failure report; in which a connection establishment failure or connection recovery failure occurred; at least one neighboring cell that obtained the last measurement result in a connection failure report, in which a connection establishment failure or connection recovery failure occurred; a primary cell (PCell) that detected a radio link failure (RLF) in a radio link failure report, or a target PCell for handover in failure; at least one candidate target cell for conditional handover in a radio link failure report; a candidate target cell selected by the wireless communication device for conditional handover (CHO) in a radio link failure report; in Evolved Universal Terrestrial Radio Access (ETH). In a UTRA radio link failure report, the PCell that detected the radio link failure, or the source PCell of the handover failure; in a radio link failure report, at least one neighboring E-UTRA cell that obtained the last measurement result when the radio link failure or handover failure occurred; in a radio link failure report, at least one neighboring New Radio (NR) cell that obtained the last measurement result when the radio link failure or handover failure occurred; in a radio link failure report, the source PCell of the last handover; in a radio link failure report, the PCell in which the wireless communication device failed to perform a Fast Primary Cell Group (MCG) recovery procedure or successfully performed a Fast MCG recovery procedure; in a radio link failure report, the cell in which the wireless communication device returned to the connected state after a connection failure and after failing to perform a reconstruction; in a radio link failure report, the cell in which a reconstruction attempt was made after a connection failure; in a successful handover report, the target PCell of the handover that generated the successful handover report; in a successful handover report, the target E-UTRA cell in which the successful handover triggered the handover report. PCell; In a successful handover report, the last measurement result is at least one neighboring NR cell obtained when the successful handover is performed; The source PCell of the handover that triggered the successful handover report; The target PCell of the handover that triggered the successful handover report; The last measurement is at least one neighboring cell obtained when a successful change or addition of the primary cell (PSCell) in a secondary cell group (SCG) is performed; In a successful PSCell report, the PCell to which the wireless communication device is connected at the time of the successful PSCell change or addition; In a successful PSCell report, the source PSCell of the successful PSCell change; In a successful PSCell report, the target PSCell of the successful PSCell change; or the most recently visited cell in the mobility history information.

[0069] In some embodiments, the ephemeris can be represented as a position and velocity state vector in an earth-centered earth-fixed (ECEF) coordinate system, or as orbital parameters in an earth-centered inertial (ECI) coordinate system.

[0070] In some embodiments, the epoch time of the satellite may be provided by a previous SIB1 message. The epoch time may include the start time of the DL subframe, indicated by the system frame number (SFN), and the subframe number is signaled in the message along with auxiliary information.

[0071] Information for time / location-based CHO User equipment (UE) can send uplink (UL) messages to gNB or base stations. UL messages can include information related to non-terrestrial networks (NTN). Since NTN supports time-based and location-based Conditional Handover (CHO) messages, this information can include either time-based or location-based CHO information to aid in network optimization.

[0072] In some embodiments, the information may include at least one of the following: a wireless link failure report when a wireless link failure is detected; a successful handover report when a successful handover is detected; a report of recorded measurement results; a report of connection failure; a report of mobility history information; or a new report stored during the satellite handover process.

[0073] In a particular embodiment, the UE can receive a request for a UL message from a gNB or BS. The UE can then send a UL message to the gNB or BS based on the request.

[0074] In some embodiments, time-based information may include at least one of the following: an indication of absolute time when a radio link failure (RLF) or handover failure is caused by a time-based CHO; When a successful handover is detected by a time-based CHO, the following are indications: the absolute time; the time threshold for the time-based CHO; the duration of the leave condition for defining the time-based CHO; the last handover performed before the last detected connection failure was a time-based CHO; the last handover performed before the last detected connection failure was a time-based CHO performed via a random access channel (RACH); whether the connection failure was caused by a time-based CHO; or whether the connection failure was caused by a time-based CHO performed via a RACH.

[0075] In some embodiments, location-based CHO information may include at least one of the following: an indication of the location of the wireless communication device when a wireless link failure (RLF) or handover failure is caused by a location-based CHO; an indication of the location of the wireless communication device when a successful handover is detected by a location-based CHO; an indication of the approximate location of the wireless communication device when a wireless link failure (RLF) or handover failure is caused by a location-based CHO; an indication of the approximate location of the wireless communication device when a successful handover is detected by a location-based CHO; an indication of one or more reference locations for the location-based CHO; an indication of one or more distance thresholds for the location-based CHO; an indication of the distance between the wireless communication device and the one or more reference locations when the RLF, the handover failure, or the successful handover is detected by a location-based CHO; an indication of the last handover performed before the last detected connection failure; or an indication of whether the connection failure was caused by a location-based CHO.

[0076] In some embodiments, location information may include at least one of the following: location estimation using one of a plurality of geographic shapes, velocity estimation using one of a plurality of velocity shapes, and location estimation valid UTC time.

[0077] In some embodiments, the coarse location information may include latitude and longitude information. The coarse location information can meet a granularity accuracy requirement of approximately 2 kilometers.

[0078] In some embodiments, the reference location for a location-based CHO can be carried from the UE to the network in a UL message. The reference location can be used for condEventD1 and condEventD2. There can be two reference locations: one can be associated with the serving cell (e.g., referenceLocation1), and the other can be associated with a candidate target cell (e.g., referenceLocation2).

[0079] In some embodiments, the distance threshold for location-based CHO can be carried from the UE to the network in the UL message. There can be two distance thresholds. One (e.g., distanceThreshFromReference1 (distance threshold from reference 1)) can be used to compare the distance between the UE and a reference location (e.g., referenceLocation1). The other (e.g., distanceThreshFromReference2 (distance threshold from reference 2)) can be used to compare the distance between the UE and a reference location (e.g., referenceLocation2).

[0080] In some embodiments, when a location-based CHO detects a radio link failure and / or a handover failure and / or a successful handover, the distance between the UE and a reference location (e.g., referencelocation1) can be carried from the UE to the network in a UL message. In some embodiments, when a location-based CHO detects a radio link failure and / or a handover failure and / or a successful handover, the distance between the UE and a reference location (e.g., referencelocation2) can be carried from the UE to the network in a UL message.

[0081] RACH-free handover for NTN User equipment (UE) can send uplink (UL) messages to gNB or base stations. UL messages may include information related to non-terrestrial networks (NTN). Since NTN systems support RACH-less handover, this information may include RACH-less handover information to aid network optimization.

[0082] In some embodiments, the information may include at least one of the following: a wireless link failure report when a wireless link failure is detected; a successful handover report when a successful handover is detected; a recorded measurement result report; a connection failure report; or a new report stored during the satellite handover process.

[0083] In a particular embodiment, the UE can receive a request for a UL message from a gNB or BS. The UE can then send a UL message to the gNB or BS based on the request.

[0084] No-RACH handover information may include at least one of the following: an indication that the last handover performed was a no-RACH handover; an indication of whether the connection failure was caused by a no-RACH handover failure; or at least one no-RACH handover related parameter. In some embodiments, at least one RACH-free handover-related parameter may include at least one of the following: an indication of the Reference Signal Received Power (RSRP) for the selection of Synchronization Signal Blocks (SSBs) for pre-allocated uplink grants; an initial value of the grant retransmission timer configured for the initial uplink transmission of the RACH-free handover; a set of Demodulation Reference Signal (DMRS) ports for the SSB-to-Physical Uplink Shared Channel (PUSCH) mapping of the RACH-free handover; the number of DMRS sequences for the SSB-to-PUSCH mapping of the RACH-free handover; a threshold for the RSRP configured for the SSB selection of the pre-allocated uplink grants for the RACH-free handover; the number of SSBs for each pre-allocated uplink grant PUSCH for the RACH-free handover; or a subset of SSBs for the SSB-to-configured CG PUSCH mapping within the configuration grant (CG) configuration for the RACH-free handover.

[0085] In some embodiments, the type / indicator / parameter of the last switch performed before the last detected connection failure can be added to the RLF report. Since NTN systems support RACH-less HOs, the type / indicator / parameter of the last switch performed for RACH-less HOs can be added to the RLF report. For example, a value / indicator / parameter can be added to the lastHO-Type IE. If this field is set with a value (e.g., rachlessho), the last switch performed can be a RACH-less switch.

[0086] In some embodiments, a type / indicator / parameter can be added to the RLF report to indicate whether the connection failure was caused by a no-RACH handover failure. For example, a value can be added to the connectionFailureType IE. If this field is set with a value (e.g., rachlessho), the connection failure may be due to a no-RACH handover failure.

[0087] In some embodiments, parameters for RACH-free handover can be recorded in the RLF report. In some embodiments, the Reference Signal Received Power (RSRP) for SSB selection of pre-allocated uplink grants can be carried from the UE to the network in the UL message. In some embodiments, the initial value of the grant retransmission timer configured for the initial uplink transmission without RACH handover can be carried from the UE to the network in the UL message.

[0088] In some embodiments, the set of demodulation reference signal (DMRS) ports for SSB-to-Physical Uplink Shared Channel (PUSCH) mapping for RACH-free handover can be carried from the UE to the network in the UL message. In some embodiments, the number of DMRS sequences for SSB-to-PUSCH mapping for RACH-free handover can be carried from the UE to the network in the UL message. In some embodiments, the RSRP threshold for SSB selection for pre-allocated uplink grants in a RACH-free handover configuration can be carried from the UE to the network in the UL message. In some embodiments, the number of SSBs per pre-allocated uplink grant PUSCH for RACH-free handover can be carried from the UE to the network in the UL message. In some embodiments, a subset of SSBs for SSB-to-CG PUSCH mapping within a CG configuration for RACH-free handover can be carried from the UE to the network in the UL message.

[0089] Satellite handover with resynchronization User equipment (UE) can send uplink (UL) messages to the gNB or base station. UL messages can include information related to the non-terrestrial network (NTN). Satellite handover procedures can be performed in NTN systems, but information related to network optimization is not included in the messages from the UE to the network. To help the gNB optimize the satellite handover process, information about the satellite handover procedure can be included in the UL message.

[0090] In some embodiments, the information may include at least one of the following: a radio link failure report when a radio link failure is detected; a successful handover report when a successful handover is detected; a report of mobility history information; or a new report stored during the satellite handover process.

[0091] In a particular embodiment, the UE can receive a request for a UL message from a gNB or BS. The UE can then send a UL message to the gNB or BS based on the request.

[0092] In some embodiments, information about the satellite handover process may include at least one of the following: an indicator that the random access procedure is initiated for a satellite handover with a resynchronization procedure; an indication that the cause of a radio link failure (RLF) is due to a continuous satellite handover with a resynchronization procedure; or at least one parameter about a satellite handover with a resynchronization procedure.

[0093] In some embodiments, at least one parameter relating to a satellite handover with a resynchronization process may include at least one of the following: an indication of the time from the last satellite handover with resynchronization performed until the loss of UL synchronization caused by the satellite handover with the resynchronization process; an indication of the absolute time at which the UL synchronization was lost due to the satellite handover with the resynchronization process; an indication of the effective duration of NTN-related auxiliary information; the number of the most recent consecutive satellite handover failures with the resynchronization process; an indication of the absolute time at which the satellite handover with the resynchronization process was obtained; and the time from the first loss of UL synchronization caused by the satellite handover with the resynchronization process until the acquisition of the resynchronization process. Indication of the time up to UL synchronization; or indication of the Physical Cell Identifier (PCI) of the source satellite; indication of the PCI of the target satellite; indication of the type of satellite handover as soft satellite handover; indication of the type of satellite handover as hard satellite handover; indication of whether the satellite handover was performed via a resynchronization process; time offset between the SSBs of the source and target satellites at the uplink time synchronization reference point; time information regarding when the target satellite begins to serve the area currently covered by the serving satellite; time information regarding when the cell provided by the NTN system ceases to serve the area currently covered by the cell; or indication of whether the satellite handover was performed via a resynchronization process without a random access procedure.

[0094] In some embodiments, this information may include the cause of the Radio Link Failure (RLF) to indicate whether the RLF was caused by a satellite handover with a resynchronization process. In some embodiments, the cause of the RLF, indicating whether the radio link failure was caused by a satellite handover with a resynchronization process, can be added to the RLF report. For example, the RLF cause can be added to rlf-CauseIE. If this field is set with a value (e.g., satelliteswitchresync (satellite handover with resynchronization)), the radio link failure is likely caused by a satellite handover with a resynchronization process.

[0095] In some embodiments, this information may introduce a new indicator that triggers a RA report. For example, in the case of a satellite handover with a resynchronization-related RA process occurring in the cell, a new indicator (e.g., satelliteswitch) may be used.

[0096] Duration of stay in NTN cell User equipment (UE) can send uplink (UL) messages to the gNB or base station. UL messages can include information related to non-terrestrial networks (NTNs). Since NTN cells are much larger than TN cells, the duration of stay in an NTN cell can be much longer than in a TN cell. To help the gNB optimize its configuration for NTN cells, the duration of stay in NTN cells can be included in the UL message.

[0097] In some embodiments, the information may include at least one of the following: a wireless link failure report when a wireless link failure is detected; a successful handover report when a successful handover is detected; a report of recorded measurement results; a report of connection failure; a report of mobility history information; or a new report stored during the satellite handover process.

[0098] In a particular embodiment, the UE can receive a request for a UL message from a gNB or BS. The UE can then send a UL message to the gNB or BS based on the request.

[0099] In some embodiments, this information includes the duration of stay in the NTN cell.

[0100] Regional configuration for recorded MDTs User equipment (UE) can receive configuration information from gNB or base station for optimizing network performance. Since NTN cells are much larger than TN cells, area configuration for recorded measurements can be enhanced for energy conservation. In a particular embodiment, the UE can send an uplink (UL) message to the gNB or base station either after receiving the configuration information or before. The UL message may include information related to the non-terrestrial network (NTN).

[0101] In some embodiments, the configuration information may include a measurement configuration for recording for at least one NTN cell. The measurement configuration for recording may include at least one of the following: a list of tracking area codes for a tracking area identifier in a region configuration for recording measurements; a region configuration for the NTN system, wherein the region configuration includes a reference location and a distance threshold; or at least one coordinate point for marking the region configuration for recording measurements. This application provides a region configuration for an NTN system. A reference location and a distance threshold may exist. When the distance between the UE and the reference location is less than the distance threshold, the UE may perform the recorded measurement. This application provides one or more coordinate points to mark the region configuration for recording measurements. In a particular embodiment, this application provides a region configuration for an NTN system. A reference location and a distance threshold may exist. When the distance between the UE and the reference location is less than the distance threshold, the UE may skip the recorded measurement.

[0102] In some embodiments, unlike terrestrial networks, this network may broadcast multiple Tracking Area Codes (TACs) per Public Land Mobile Network (PLMN) cell in an NRN TN cell. In conventional techniques, the Tracking Area Identifier may include the PLMN identifier and Tracking Area Code in the area configuration of the recorded MDT, which may not be suitable for non-terrestrial network (NTN) systems.

[0103] In some embodiments, a list of tracking area codes for tracking area identifiers in the area configuration used for recording the MDT may be included. The tracking area identifier may include a list of PLMN identifiers and tracking area codes. In some embodiments, a list of tracking area codes for the measured cells may be included / recorded in the recorded MDT report.

[0104] It should be understood that one or more features from the above / below examples of embodiments are not limited to specific examples of embodiments, but can be combined in any way (e.g., in any priority and / or order, simultaneously or otherwise).

[0105] Figure 3 A flowchart of method 300 for enhancing mobility within non-terrestrial networks (NTNs) using self-organizing networks (SON) and / or minimized road test (MDT) is shown. Method 300 can be used in conjunction with the methods described herein. Figures 1 to 2 This can be implemented by any of the components and devices described in detail. Generally, in some embodiments, method 300 can be performed by the UE. Depending on the embodiment, additional, fewer, or different operations may be performed in method 300. At least one aspect of these operations relates to a system, method, apparatus, or computer-readable medium.

[0106] Wireless communication devices (e.g., user equipment (UE)) can send uplink (UL) messages (e.g., UE information response messages) to wireless communication nodes (e.g., gNB or base station (BS)). UL messages may include information related to non-terrestrial networks (NTNs). In some embodiments, the wireless communication device (e.g., user equipment (UE)) can receive configuration information (e.g., LoggedMeasurementConfiguration) from the wireless communication node (e.g., gNB or base station (BS)) to optimize network performance.

[0107] In some embodiments, the information may include an indication that the cell associated with at least one of the wireless communication devices or wireless communication nodes is part of an NTN. In some embodiments, the information may include at least one of the following: frequency information of the cell, or an indication of whether the cell is part of an NTN. In some embodiments, the cell may include at least one of the following: the serving cell that performed the recorded measurement in a recorded measurement report; at least one neighboring cell that performed the recorded measurement in the recorded measurement report; the cell that obtained the last measurement result in a connection failure report; in which a connection establishment failure or connection recovery failure occurred; at least one neighboring cell that obtained the last measurement result in a connection failure report, in which a connection establishment failure or connection recovery failure occurred; the primary cell (PCell) that detected a radio link failure (RLF) in a radio link failure report, or the target PCell for handover failure; at least one candidate target cell for conditional handover in a radio link failure report; the candidate target cell selected by the wireless communication device for conditional handover (CHO) in a radio link failure report; in Evolved Universal Terrestrial Radio Access (ETH). In a UTRA radio link failure report, the PCell that detected the radio link failure, or the source PCell of the handover failure; in a radio link failure report, at least one neighboring E-UTRA cell that obtained the last measurement result when the radio link failure or handover failure occurred; in a radio link failure report, at least one neighboring New Radio (NR) cell that obtained the last measurement result when the radio link failure or handover failure occurred; in a radio link failure report, the source PCell of the last handover; in a radio link failure report, the PCell in which the wireless communication device failed to perform a Fast Primary Cell Group (MCG) recovery procedure or successfully performed a Fast MCG recovery procedure; in a radio link failure report, the cell in which the wireless communication device returned to the connected state after a connection failure and after failing to perform a reconstruction; in a radio link failure report, the cell in which a reconstruction attempt was made after a connection failure; in a successful handover report, the target PCell of the handover that generated the successful handover report; in a successful handover report, the target E-UTRA cell in which the successful handover triggered the handover report. PCell; In a successful handover report, the last measurement result is at least one neighboring NR cell obtained when the successful handover is performed; The source PCell of the handover that triggered the successful handover report; The target PCell of the handover that triggered the successful handover report; The last measurement is at least one neighboring cell obtained when a successful change or addition of the primary cell (PSCell) in a secondary cell group (SCG) is performed; In a successful PSCell report, the PCell to which the wireless communication device is connected at the time of the successful PSCell change or addition; In a successful PSCell report, the source PSCell of the successful PSCell change; In a successful PSCell report, the target PSCell of the successful PSCell change; or the most recently visited cell in the mobility history information.

[0108] In some embodiments, the information may include at least one NTN-related measurement parameter. At least one NTN-related measurement parameter may include at least one of the following: an indication of the type of NTN-related measurement performed in the RRC_IDLE state and / or RRC_INACTIVE state, wherein the NTN-related measurement is a location-based measurement or a time-based measurement; an indication of a distance threshold for initiating location-based measurements in the RRC_IDLE state and / or RRC_INACTIVE state; an indication of the reference location of the serving cell at a time reference for initiating location-based measurements in the RRC_IDLE state and / or RRC_INACTIVE state; a list of TN coverage area information for assisting NTN user equipment (UE) in the RRC_IDLE and / or RRC_INACTIVE state to skip terrestrial network (TN) measurements; or time information regarding when a cell, provided by the NTN system, ceases to serve the area currently covered by that cell.

[0109] In some embodiments, the information may include at least one NTN-related parameter. The at least one NTN-related parameter may include at least one of the following: time information about when a cell, provided by the NTN system, ceases to serve the area currently covered by the cell; an indication of whether a recently performed handover was an intra-NTN handover; an indication of whether a connection failure was caused by an intra-NTN handover failure or an intra-NTN radio link failure; or a list of neighboring NTN cells.

[0110] In some embodiments, the information may include time-based Conditional Handover (CHO) information or location-based CHO information. In some embodiments, the time-based information may include at least one of the following: an indication of absolute time when a radio link failure (RLF) or handover failure is caused by a time-based CHO; an indication of absolute time when a successful handover is detected by a time-based CHO; an indication of a time threshold for the time-based CHO; an indication of the duration for defining the leave condition for the time-based CHO; an indication of the last handover performed before the last detected connection failure that was a time-based CHO; an indication that the last handover performed before the last detected connection failure was a time-based CHO performed via a random access channel (RACH); an indication of whether the connection failure was caused by a time-based CHO; or an indication of whether the connection failure was caused by a time-based CHO performed via a RACH. In some embodiments, location-based CHO information may include at least one of the following: an indication of the location of the wireless communication device when a wireless link failure (RLF) or handover failure is caused by a location-based CHO; an indication of the location of the wireless communication device when a successful handover is detected by a location-based CHO; an indication of the approximate location of the wireless communication device when a wireless link failure (RLF) or handover failure is caused by a location-based CHO; an indication of the approximate location of the wireless communication device when a successful handover is detected by a location-based CHO; an indication of one or more reference locations for the location-based CHO; an indication of one or more distance thresholds for the location-based CHO; an indication of the distance between the wireless communication device and the one or more reference locations when the RLF, the handover failure, or the successful handover is detected by a location-based CHO; an indication of the last handover performed before the last detected connection failure; or an indication of whether the connection failure was caused by a location-based CHO.

[0111] In some embodiments, the configuration information may include a measurement configuration for recording for at least one NTN cell. The measurement configuration for recording may include at least one of the following: a list of tracking area codes for a tracking area identifier in a region configuration for recording measurements; a region configuration for the NTN system, wherein the region configuration includes a reference location and a distance threshold; or at least one coordinate point for marking the region configuration for recording measurements. This application provides a region configuration for an NTN system. A reference location and a distance threshold may exist. When the distance between the UE and the reference location is less than the distance threshold, the UE may perform the recorded measurement. This application provides one or more coordinate points to mark the region configuration for recording measurements. In a particular embodiment, this application provides a region configuration for an NTN system. A reference location and a distance threshold may exist. When the distance between the UE and the reference location is less than the distance threshold, the UE may skip the recorded measurement.

[0112] In some embodiments, the information may include no random access channel (RACH) handover information. No RACH handover information may include at least one of the following: an indication that the last handover performed was a no RACH handover; an indication of whether the connection failure was caused by a no RACH handover failure; or at least one no RACH handover related parameter.

[0113] In some embodiments, at least one RACH-free handover-related parameter may include at least one of the following: an indication of the Reference Signal Received Power (RSRP) for the selection of Synchronization Signal Blocks (SSBs) for pre-allocated uplink grants; an initial value of the grant retransmission timer configured for the initial uplink transmission of the RACH-free handover; a set of Demodulation Reference Signal (DMRS) ports for the SSB-to-Physical Uplink Shared Channel (PUSCH) mapping of the RACH-free handover; the number of DMRS sequences for the SSB-to-PUSCH mapping of the RACH-free handover; a threshold for the RSRP configured for the SSB selection of the pre-allocated uplink grants for the RACH-free handover; the number of SSBs for each pre-allocated uplink grant PUSCH for the RACH-free handover; or a subset of SSBs for the SSB-to-configured CGPUSCH mapping within the Configuration Grant (CG) configuration for the RACH-free handover.

[0114] In some embodiments, the information may include information about the satellite handover process. In some embodiments, the information about the satellite handover process may include at least one of the following: an indicator of whether the random access procedure was initiated for a satellite handover with a resynchronization process; an indication of whether a radio link failure (RLF) was caused by consecutive satellite handovers with a resynchronization process; or at least one parameter regarding the satellite handover with a resynchronization process. At least one parameter regarding the satellite handover with a resynchronization process may include at least one of the following: an indication of the time from the last satellite handover with resynchronization until the loss of UL synchronization due to the satellite handover with the resynchronization process; an indication of the absolute time at which the UL synchronization was lost due to the satellite handover with the resynchronization process; an indication of the effective duration of NTN-related auxiliary information; the number of the most recent consecutive satellite handover failures with a resynchronization process; an indication of the absolute time at which the satellite handover with the resynchronization process was obtained; an indication of the time from the first loss of UL synchronization due to the satellite handover with the resynchronization process until the UL synchronization was obtained; or the source satellite. Indication of Physical Cell Identifier (PCI); indication of the target satellite's PCI; indication of the type of satellite handover as soft satellite handover; indication of the type of satellite handover as hard satellite handover; indication of whether the satellite handover was performed via a resynchronization process; indication of whether the satellite handover was performed via a resynchronization process without a random access procedure; indication of the time offset between the synchronization signal block (SSB) from the source satellite and the SSB from the target satellite at the uplink time synchronization reference point; indication of time information regarding when the target satellite will begin serving the area currently covered by the serving satellite; or indication of time information regarding when the cell, provided by the NTN system, will cease serving the area currently covered by the cell.

[0115] In some embodiments, the information may include satellite information of the first cell. The satellite information may include at least one of the following: an indication of the absolute time when the satellite will begin serving the first cell; ephemeris information of the satellite indicating when it will begin serving the first cell; or an indication of the epoch time of the satellite used for NTN auxiliary information of the first cell. In some embodiments, the first cell may include at least one of the following: the serving cell that performed the recorded measurement in the recorded measurement report; at least one neighboring cell that performed the recorded measurement in the recorded measurement report; the cell that obtained the last measurement result in the connection failure report; in which a connection establishment failure or connection recovery failure occurred; at least one neighboring cell that obtained the last measurement result in the connection failure report, in which a connection establishment failure or connection recovery failure occurred; the primary cell (PCell) that detected the radio link failure (RLF) in the radio link failure report, or the target PCell for handover failure; the candidate target cell for conditional handover in the radio link failure report when a connection fails; the candidate target cell selected by the wireless communication device for conditional handover (CHO) in the radio link failure report; in the evolved Universal Terrestrial Radio Access (ETH)... In a UTRA radio link failure report, the PCell that detected the radio link failure, or the source PCell of the handover failure; in a radio link failure report, at least one neighboring E-UTRA cell that obtained the last measurement result when the radio link failure or handover failure occurred; in a radio link failure report, at least one neighboring New Radio (NR) cell that obtained the last measurement result when the radio link failure or handover failure occurred; in a radio link failure report, the source PCell of the last handover; in a radio link failure report, the PCell in which the wireless communication device failed to perform a Fast Primary Cell Group (MCG) recovery procedure or successfully performed a Fast MCG recovery procedure; in a radio link failure report, the cell in which the wireless communication device returned to the connected state after a connection failure and after failing to perform a reconstruction; in a radio link failure report, the cell in which a reconstruction attempt was made after a connection failure; in a successful handover report, the target PCell of the handover that generated the successful handover report; in a successful handover report, the target E-UTRA cell in which the successful handover triggered the handover report. PCell; in a successful handover report, the last measurement result is at least one neighboring NR cell obtained when the successful handover is performed; the source PCell of the handover that triggered the successful handover report; the target PCell of the handover that triggered the successful handover report; the last measurement is at least one neighboring cell obtained when a successful change or addition of the primary cell (PSCell) in a secondary cell group (SCG) is performed; in a successful PSCell report, the PCell to which the wireless communication device is connected at the time of the successful PSCell change or addition; in a successful PSCell report, the source PSCell of the successful PSCell change; in a successful PSCell report, the target PSCell of the successful PSCell change; or one or more recently visited cells in the mobility history information.

[0116] In some embodiments, the information may include at least one of the following: a radio link failure report when a radio link failure is detected; a successful handover report when a successful handover is detected; a report stored during the satellite handover process; a report of recorded measurement results; a connection failure report; or a report of mobility history information. In some embodiments, the information may include the duration of stay in the NTN cell.

[0117] In some embodiments, the wireless communication device may receive a request for a UL message from a wireless communication node. The wireless communication device may then send a UL message to the wireless communication node upon request.

[0118] In some embodiments, a wireless communication node (e.g., a gNB or base station (BS)) may receive uplink (UL) messages from a wireless communication device (e.g., a user equipment (UE)). The UL message may include information related to a non-terrestrial network (NTN). In some embodiments, the wireless communication node (e.g., a gNB or base station (BS)) may send configuration information to the wireless communication device (e.g., a user equipment (UE)) for optimizing network performance.

[0119] It should also be understood that any references to elements in this document using names such as "first," "second," etc., generally do not restrict the number or order of these elements. Rather, these names may be used in this document as a convenient means of distinguishing two or more elements, or multiple instances of a single element. Therefore, a reference to the first element and the second element does not imply that only two elements can be used, or that the first element must somehow precede the second element.

[0120] Furthermore, those skilled in the art will understand that various techniques and skills can be used to represent information and signals. For example, data, instructions, commands, information, signals, bits, and symbols that may be mentioned in the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof.

[0121] Those skilled in the art will further understand that any of the various illustrative logic blocks, modules, processors, means, circuits, methods, and functions described in connection with the aspects disclosed herein can be implemented by electronic hardware (e.g., digital implementation, analog implementation, or a combination of both), firmware, various forms of program or design code in conjunction with instructions (which may be referred to herein as "software" or "software module" for convenience), or any combination of these technologies. To clearly illustrate the interchangeability of hardware, firmware, and software, the various exemplary components, blocks, modules, circuits, and steps described above are generally described in terms of their functionality. Whether such functionality is implemented as hardware, firmware, or software, or a combination of these technologies, depends on the specific application and the design constraints imposed on the system as a whole. Those skilled in the art can implement the described functionality in various ways for each specific application, but such implementation will not depart from the scope of this disclosure.

[0122] Furthermore, those skilled in the art will understand that the various exemplary logic blocks, modules, devices, components, and circuits described herein can be implemented within or executed by an integrated circuit (IC), which may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, or any combination thereof. Logic blocks, modules, and circuits may also include antennas and / or transceivers for communicating with various components within a network or device. A general-purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a combination of multiple microprocessors, a combination of one or more microprocessors combined with a DSP core, or any other suitable configuration that performs the functions described herein.

[0123] If these functions are implemented in software, they can be stored as one or more instructions or code on a computer-readable medium. Therefore, the steps of the methods or algorithms disclosed herein can be implemented as software stored on a computer-readable medium. Computer-readable media include both computer storage media and communication media, with the latter including any medium capable of transferring a computer program or code from one location to another. Storage media can be any available medium accessible to a computer. By way of example and not limitation, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store the required program code in the form of instructions or data structures and that is accessible to a computer.

[0124] In this document, the term "module" as used herein refers to software, firmware, hardware, and any combination of such elements for performing the relevant functions described herein. Furthermore, for purposes of discussion, individual modules are described as discrete modules; however, as will be apparent to those skilled in the art, two or more modules can be combined to form a single module that performs the relevant functions according to embodiments of the present solution.

[0125] Furthermore, memory or other storage devices, as well as communication components, may be used in embodiments of this solution. It should be understood that, for clarity, the above description refers to embodiments of this solution described with reference to different functional units and processors. However, it will be apparent that any suitable functional distribution among different functional units, processing logic elements, or domains can be used without impairing this solution. For example, functions shown to be performed by separate processing logic elements or controllers may be performed by the same processing logic element or controller. Therefore, references to specific functional units are merely references to suitable means for providing the described functions and do not indicate a strict logical or physical structure or organization.

[0126] Various modifications to the embodiments described in this disclosure will be apparent to those skilled in the art, and the general principles defined herein can be applied to other embodiments without departing from the scope of this disclosure. Therefore, this disclosure is not intended to be limited to the embodiments shown herein, but is to be given the broadest scope consistent with the novel features and principles disclosed herein as described in the claims.

Claims

1. A method comprising: The uplink (UL) message is sent from the wireless communication device to the wireless communication node. The UL message includes information related to non-terrestrial networks (NTN).

2. The method according to claim 1, comprising: The wireless communication device receives configuration information from the wireless communication node for optimizing network performance.

3. The method according to claim 1, wherein, The information includes an indication that the cell associated with at least one of the wireless communication devices or the wireless communication nodes is part of the NTN.

4. The method according to claim 3, wherein, The information includes at least one of the following: frequency information of the cell, or an indication of whether the cell is part of the NTN.

5. The method according to claim 3, wherein, The community includes at least one of the following: The service cell for the recorded measurements in the measurement report; The recorded measurement report includes at least one neighboring cell that performed the recorded measurement; The cell in the connection failure report that obtained the last measurement result; wherein a connection establishment failure or connection recovery failure occurred in the cell; In the connection failure report, at least one neighboring cell from which the last measurement result was obtained, wherein a connection establishment failure or a connection recovery failure occurred in the at least one neighboring cell; In the Radio Link Failure Report, the primary cell (PCell) that detected Radio Link Failure (RLF), or the target PCell that failed the handover; In a radio link failure report, at least one candidate target cell is used for conditional handover when a connection fails; In the wireless link failure report, the wireless communication device is the candidate target cell selected for conditional handover (CHO); In Evolution Universal Terrestrial Radio Access (ETH) In the UTRA wireless link failure report, the PCell that detected the wireless link failure (RLF) or the source PCell that failed the handover. In a radio link failure report, at least one neighboring E-UTRA cell that obtained the last measurement result when a radio link failure or handover failure occurred; In a radio link failure report, at least one neighboring new radio (NR) cell from which the last measurement result was obtained when a radio link failure or handover failure occurred; In the wireless link failure report, the last switched source PCell; In the wireless link failure report, the wireless communication device failed to execute the Fast Primary Cell Group (MCG) recovery procedure or successfully execute the PCell of the Fast MCG recovery procedure; In a wireless link failure report, the wireless communication device returns to the connected state of the cell after a connection failure and after a failure to perform a reconstruction. In a wireless link failure report, the cell that attempted to rebuild after a connection failure; The successful handover report generates the target PCell of the handover. A successful handover triggered a successful handover report for the target E-UTRA PCell. In a successful handover report, the final measurement result is at least one neighboring NR cell obtained at the time of the successful handover execution; A successful switch triggers the source PCell of the successful switch report; A successful switch triggers the target PCell of the successful switch report; The final measurement is obtained when the primary cell (PSCell) of a successful secondary cell group (SCG) change or addition is executed, at least one neighboring cell is obtained. In a successful PSCell report, the PCell to which the wireless communication device is connected is mentioned when a successful PSCell change or addition occurs. In a successful PSCell report, the source PSCell of the PSCell change that occurred is listed. In the successful PSCell report, the target PSCell of the PSCell change that occurred during the successful PSCell change; or The most recently visited cell in mobility history information.

6. The method according to claim 1, wherein, The information includes at least one NTN-related measurement parameter.

7. The method according to claim 6, wherein, The at least one NTN-related measurement parameter includes at least one of the following: An indication of the type of NTN-related measurement performed in the RRC_IDLE state and / or the RRC_INACTIVE state, wherein the NTN-related measurement is a location-based measurement or a time-based measurement; An indication of the distance threshold used for location-based measurement initiation in the RRC_IDLE and / or RRC_INACTIVE states; In the RRC_IDLE and / or RRC_INACTIVE states, it is used to indicate the reference location of the serving cell at the time reference for location-based measurement initiation. A list of TN coverage area information used to assist NTN user equipment (UE) in RRC_IDLE and / or RRC_INACTIVE states in skipping terrestrial network (TN) measurements; or Information about when a cell, provided by the NTN system, ceases service to the area currently covered by the cell.

8. The method according to claim 1, wherein, The information includes at least one NTN-related parameter.

9. The method according to claim 8, wherein, The at least one NTN-related parameter includes at least one of the following: Is the last handover performed an indication of a handover within the NTN? Indication of whether the connection failure was caused by a handover failure within the NTN or a failure in the radio link within the NTN; Information regarding when a cell ceases service to the area currently covered by the cell, provided by the NTN system; or List of neighboring NTN neighborhoods.

10. The method according to claim 1, wherein, The information includes time-based conditional switching (CHO) information or location-based CHO information.

11. The method according to claim 10, wherein, The time-based information includes at least one of the following: An absolute time indication when a radio link failure (RLF) or handover failure is caused by a time-based CHO; The absolute time indication when a successful switch is detected by a time-based CHO; Indicator of time threshold for time-based CHO; Indicator used to define the duration of departure conditions for time-based CHOs; The last switch performed before the last detected connection failure is indicated by a time-based CHO. The last handover performed before the last detected connection failure is indicated by a time-based CHO via the No Random Access Channel (RACH). Is the connection failure due to an indication caused by a time-based CHO? Indicator whether the connection failure was caused by a time-based CHO executed without RACH.

12. The method according to claim 10, wherein, The location-based CHO information includes at least one of the following: The location indication of the wireless communication device when a wireless link failure (RLF) or handover failure is caused by a location-based CHO; When a wireless link failure (RLF) or handover failure is caused by a location-based CHO, the approximate location of the wireless communication device is indicated. The location of the wireless communication device is indicated when a successful handover is detected by a location-based CHO. When a successful handover is detected by a location-based CHO, it indicates the approximate location of the wireless communication device; Indication for one or more reference locations for location-based CHO; Indication for one or more distance thresholds for location-based CHOs; An indication of the distance between the wireless communication device and the one or more reference locations when the RLF, the handover failure, or the successful handover is detected by a location-based CHO; The last handover performed before the last detected connection failure is based on the location-based CHO indication; or Indicator of whether the connection failure was caused by a location-based CHO.

13. The method according to claim 2, wherein, The configuration information includes the measurement configuration recorded for at least one NTN cell.

14. The method according to claim 13, wherein, The recorded measurement configuration includes at least one of the following: A list of tracking area codes for tracking area identification in the area configuration used for recording measurements; For the NTN system, a region configuration is provided, wherein the region configuration includes a reference location and a distance threshold; or At least one coordinate point is used to mark the area configuration for recording measurements.

15. The method according to claim 1, wherein, The information includes information on handover without a random access channel (RACH).

16. The method according to claim 15, wherein, The no-RACH handover information includes at least one of the following: The final handover instruction is a no-RACH handover; Is the connection failure due to an indication of no RACH handover failure? At least one parameter is not related to RACH switching.

17. The method according to claim 16, wherein, The at least one RACH-free handover related parameter includes at least one of the following: An indication of the Reference Signal Received Power (RSRP) for the selection of the Synchronization Signal Block (SSB) used for pre-allocated uplink grants; The initial value of the authorized retransmission timer configured for the initial uplink transmission without RACH handover; The set of demodulation reference signal (DMRS) ports used for the SSB-to-Physical Uplink Shared Channel (PUSCH) mapping without RACH handover; The number of DMRS sequences used for the SSB-to-PUSCH mapping without RACH switching; For the SSB with the pre-allocated uplink grant that does not undergo RACH handover, select the configured RSRP threshold; The number of SSBs for each pre-allocated uplink licensed PUSCH used for the RACH-free handover; or A subset of SSBs used for SSB-to-configuration CG PUSCH mapping within the configuration authorization (CG) configuration for the no-RACH handover.

18. The method according to claim 1, wherein, The information includes details about the satellite handover process.

19. The method according to claim 18, wherein, Information regarding the satellite handover process includes at least one of the following: Is the random access procedure an indicator for a satellite handover involving a resynchronization process? Used to indicate whether a radio link failure (RLF) is caused by a continuous satellite handover with a resynchronization process; or At least one parameter relating to satellite handover with resynchronization process.

20. The method according to claim 19, wherein, At least one parameter relating to satellite handover with the resynchronization process includes at least one of the following: An indication of the time from the last satellite handover with resynchronization execution until the loss of UL synchronization due to the satellite handover with said resynchronization process. Indication of absolute time when the UL synchronization is lost due to satellite handover with the resynchronization process; Indication of the effective duration of NTN-related auxiliary information; The number of most recent consecutive satellite handover failures with resynchronization procedures; Obtain an indication of the absolute time during satellite handover with the resynchronization process described above; An indication of the time elapsed from the loss of the first UL synchronization due to satellite handover with the resynchronization process until the UL synchronization is regained; or Indication of the Physical Cell Identifier (PCI) of the source satellite; PCI indication of the target satellite; The type of satellite handover is indicated as soft satellite handover; The type of satellite handover is indicated as hard satellite handover; Instructions on whether the satellite handover was performed via a resynchronization process; Indication on whether the satellite handover is performed via a resynchronization process without a random access procedure; At the uplink time synchronization reference point, it indicates the time offset between the synchronization signal block (SSB) from the source satellite and the SSB from the target satellite; Instructions regarding the timing of when the target satellite will begin serving the area currently covered by the serving satellite; or Instructions regarding the time information provided by the NTN system that a cell will cease service to the area currently covered by the cell.

21. The method according to claim 1, wherein the information includes satellite information of the first cell.

22. The method according to claim 21, wherein, The satellite information includes at least one of the following: An indication of the absolute time when the satellite will begin serving the first cell; The ephemeris information of the satellite when it is about to begin serving the first cell; or The epoch time indication of the satellite for the NTN auxiliary information of the first cell.

23. The method according to claim 21, wherein, The first cell includes at least one of the following: The service cell for the recorded measurements in the measurement report; The recorded measurement report includes at least one neighboring cell that performed the recorded measurement; The cell in the connection failure report that obtained the last measurement result; in the cell, a connection establishment failure or connection recovery failure occurred; In the connection failure report, at least one neighboring cell that obtained the last measurement result, in which connection establishment failure or connection recovery failure occurred; In the Radio Link Failure Report, the primary cell (PCell) that detected Radio Link Failure (RLF), or the target PCell that failed the handover; In the wireless link failure report, candidate target cells are used for conditional handover when the connection fails; In the wireless link failure report, the wireless communication device is the candidate target cell selected for conditional handover (CHO); In Evolution Universal Terrestrial Radio Access (ETH) In the UTRA wireless link failure report, the PCell that detected the wireless link failure (RLF) or the source PCell that failed the handover. In the radio link failure report, at least one neighboring E-UTRA cell that obtained the last measurement result when a radio link failure or handover failure occurred; In the radio link failure report, at least one neighboring new air interface (NR) cell that obtained the last measurement result when the radio link failure or handover failure occurred; In the wireless link failure report, the last switched source PCell; In the wireless link failure report, the wireless communication device failed to execute the Fast Primary Cell Group (MCG) recovery procedure or successfully execute the PCell of the Fast MCG recovery procedure; In the wireless link failure report, after the connection fails and after the reconstruction is not performed, the wireless communication device returns to the connected state of the cell. In the wireless link failure report, the cell that attempted to rebuild after the connection failure; The successful handover report generates the target PCell of the handover. The successful handover triggered the target E-UTRA PCell of the successful handover report; In the successful handover report, the last measurement result is at least one neighboring NR cell obtained at the time of the successful handover execution; The successful handover triggers the source PCell of the successful handover report; The successful handover triggers the target PCell of the successful handover report; The final measurement is obtained when the primary cell (PSCell) of a successful secondary cell group (SCG) change or addition is executed, at least one neighboring cell is obtained. In a successful PSCell report, the PCell to which the wireless communication device was connected at the time the successful PSCell was changed or added; In the successful PSCell report, the source PSCell of the PSCell change that occurred is listed. The target PSCell of the successful PSCell change that occurred in the successful PSCell report; or The most recently visited cell in mobility history information.

24. The method according to claim 1, wherein, The information is included in at least one of the following: Wireless link failure report when a wireless link failure is detected; A successful handover report is generated when a successful handover is detected. New reports stored during the satellite handover process; A report of the recorded measurement results; A connection failure report; or Reporting of mobility history information.

25. The method according to claim 1, wherein, The information includes the duration of stay in the NTN cell.

26. The method of claim 1, comprising: The wireless communication device receives a request for the UL message from the wireless communication node; as well as The wireless communication device sends the UL message to the wireless communication node according to the request.

27. A method comprising: The wireless communication node receives uplink (UL) messages from the wireless communication device. The UL message includes information related to non-terrestrial networks (NTN).

28. A non-transitory computer-readable medium storing instructions that, when executed by at least one processor, cause the at least one processor to perform the method according to any one of claims 1 to 27.

29. An apparatus comprising: At least one processor is configured to perform the method according to any one of claims 1 to 27.

Images