Wireless communication method and wireless terminal and wireless network node thereof

Abstract

A wireless communication method for use in a wireless terminal is disclosed. The method includes performing global navigation satellite system (GNSS) positioning if an event occurs.

Description

Technical Field

[0001] This document relates generally to wireless communications, and in particular to non-terrestrial communications. Background Art

[0002] In terrestrial deployment, users and services are very concentrated, making the network mainly located in cities, factories, rural areas, etc. In sparsely populated areas, network deployment is expensive, difficult, or even non-existent. With the advancement of science and technology, there is a huge demand for data collection and communication in remote areas. For example, it may be necessary to collect meteorological data in mountain peaks or deserts.

[0003] In non-terrestrial deployment, satellites can provide large-scale coverage in remote areas. Non-terrestrial network deployment can be considered to extend the coverage of terrestrial networks and further expand the services of cellular network operators. Typical scenarios where non-terrestrial networks provide access to user equipment include Figure 1 shown.

[0004] exist Figure 1 In the NTN, a (NTN) gateway is an earth station or gateway located on the surface of the earth and providing sufficient radio frequency (RF) power and RF sensitivity to access a satellite (or a high altitude platform (HAPS), an unmanned aircraft system (UAS) platform, etc.). The gateway is a transport network layer (TNL) node. The wireless link between the satellite and the gateway is called a feeder link. The wireless link between the satellite and the user equipment (UE) is called a service link. The satellite (or UAS platform) generates a beam over a given service area limited by its field of view. The footprint of the beam is usually elliptical.

[0005] Satellites can be placed into low earth orbit (LEO) or geostationary orbit (GEO). GEO is a circular orbit that is located 35,786km above the Earth's equator and follows the direction of the Earth's rotation. A GEO satellite in this orbit has an orbital period equal to the Earth's rotation period, and therefore appears stationary at a fixed position in the sky to a ground observer. The typical beam coverage of a GEO is 200-3500km.

[0006] LEO refers to an orbit around the Earth at an altitude between 300km and 1500km. In such an orbit, a LEO satellite circles the Earth at a speed of 7.56km per second. The typical beam coverage area of ​​GEO is 100-1000km.

[0007] In addition, Internet of Things (IoT) connections also require a large coverage area. Non-terrestrial network deployment can be suitable for the needs of IoT connections. Therefore, NB-IoT (narrowband IoT) or enhanced machine type communication (eMTC) through NTN has become a trend in technology development. Summary of the invention

[0008] The present disclosure relates to a wireless communication method for use in a wireless terminal. The method comprises: if an event occurs, performing a Global Navigation Satellite System (GNSS) positioning.

[0009] Various embodiments may preferably achieve the following features:

[0010] Preferably, performing GNSS positioning if the event occurs comprises:

[0011] If the event occurs, a GNSS fix is ​​performed in the gap while in connected mode.

[0012] Preferably, the event includes at least one of the following:

[0013] The current GNSS positioning of the wireless terminal is invalid or will become invalid.

[0014] at least one evaluation period is greater than or equal to the time during which the wireless terminal performs GNSS positioning, wherein the wireless terminal evaluates the radio link quality during the evaluation period,

[0015] At least one discontinuous reception DRX cycle is greater than or equal to the time for the wireless terminal to perform GNSS positioning,

[0016] The DRX inactivity time or DRX cycle is greater than or equal to the time for the wireless terminal to perform GNSS positioning.

[0017] DRX period is equal to sf2048,

[0018] DRX onDurationTimer is less than or equal to psf40,

[0019] The time for the wireless terminal to perform GNSS positioning is less than the threshold.

[0020] The startup type of GNSS positioning is hot start or warm start.

[0021] The data buffer is not empty,

[0022] There is subsequent data transmission,

[0023] The quality of service (QoS) meets delay-sensitive requirements, or

[0024] The interval between arriving data is less than the threshold.

[0025] Preferably, sf2048 is a candidate value configured for DRX configuration (eg, for a DRX cycle).

[0026] Preferably, sf2048 ranges from 0 to 2047 (eg, INTEGER(0..2047)).

[0027] Preferably, psf40 is a candidate value configured for DRX configuration (eg, for DRX onDurationTimer or drx-InactivityTimer).

[0028] Preferably, the gap includes at least one of the following: a period not scheduled for data transmission or a DRX inactive time.

[0029] Preferably, the time period is a physical downlink control channel slot, a downlink slot, or a slot configured for acquiring a GNSS position fix.

[0030] Preferably, the gap is greater than or equal to the time for the wireless terminal to perform GNSS positioning.

[0031] Preferably, the timing of the gap is no later than when the current GNSS position of the wireless terminal becomes invalid.

[0032] Preferably, performing GNSS positioning if the event occurs comprises:

[0033] If the event occurs, GNSS positioning is performed after the radio link failure RLF is triggered.

[0034] Preferably, the event includes at least one of the following:

[0035] The current GNSS positioning of the wireless terminal is invalid or will become invalid.

[0036] At least one evaluation period is less than the time for the wireless terminal to perform GNSS positioning, wherein the wireless terminal evaluates the link quality during the evaluation period,

[0037] At least one DRX cycle is less than or equal to the time for the wireless terminal to perform GNSS positioning,

[0038] The DRX inactivity time or DRX cycle is shorter than the time for the wireless terminal to perform GNSS positioning.

[0039] The time for the wireless terminal to perform GNSS positioning is greater than the threshold.

[0040] The startup type of GNSS positioning is warm start or cold start.

[0041] The data buffer is not empty,

[0042] There is subsequent data transmission,

[0043] The quality of service (QoS) meets delay-sensitive requirements, or

[0044] The interval between arriving data is less than the threshold.

[0045] Preferably, performing GNSS positioning if the event occurs comprises:

[0046] If the event occurs, a GNSS fix is ​​performed by leaving connected mode or entering idle mode.

[0047] Preferably, the event includes at least one of the following:

[0048] The current GNSS positioning of the wireless terminal is invalid or will become invalid.

[0049] The data buffer is empty,

[0050] The quality of service (QoS) meets the delay-insensitive requirements.

[0051] The interval between arriving data is greater than the threshold, or

[0052] There is no subsequent data transfer.

[0053] Preferably, the wireless communication method further comprises: if the event occurs, receiving a configuration message enabling execution of GNSS positioning from the wireless network node.

[0054] Preferably, the configuration message comprises at least one of the following: a radio link control message or a system information block.

[0055] Preferably, the wireless communication method further comprises receiving configuration information of the gap from a wireless network node.

[0056] Preferably, the wireless communication method further comprises receiving an indication or activation of a DRX cycle from a radio network node, wherein the gap comprises a DRX inactive time.

[0057] Preferably, the configuration information, indication or activation of the DRX cycle is included in a radio link control message, a system information block, a downlink control information or a medium access control element MAC CE.

[0058] Preferably, the configuration information of the gap includes at least one of the following: a start time, a duration, a period, an indication that the gap is used for GNSS positioning, or an activation indication for activating the gap to be used for GNSS positioning.

[0059] Preferably, the indication or activation of the DRX cycle comprises at least one of the following: a start time, a duration, a period, an on-duration, an indication that the DRX cycle is used for GNSS positioning, or an identifier of the DRX cycle.

[0060] Preferably, if the event occurs, performing GNSS positioning in the gap while in connected mode includes at least one of the following:

[0061] starting a timer, wherein the length of the timer is determined based on the time at which the wireless terminal performs GNSS positioning,

[0062] When GNSS positioning is completed, stop the timer.

[0063] If GNSS positioning fails, GNSS positioning cannot be performed, or the timer expires, RLF is triggered or the idle mode is entered.

[0064] After completing GNSS positioning or restoring uplink synchronization, the random access channel RACH or scheduling request SR is triggered.

[0065] After completing the GNSS positioning, a MAC CE is generated to report the validity duration of the new GNSS positioning obtained through the completed GNSS positioning.

[0066] Sending a MAC CE in the UL source allocated for subsequent transmission,

[0067] Triggering SR or RACH for sending MAC CE,

[0068] If the current GNSS position of the wireless terminal becomes invalid, clearing the HARQ buffer,

[0069] If the current GNSS position of the wireless terminal becomes invalid, the uplink resources are released, or

[0070] After completing GNSS positioning or restoring uplink synchronization, uplink transmission is resumed.

[0071] Preferably, the wireless communication method further comprises sending assistance information associated with performing GNSS positioning to the wireless network node.

[0072] Preferably, the auxiliary information includes at least one of the following:

[0073] The time required by a wireless terminal to perform GNSS positioning,

[0074] The startup type of GNSS positioning,

[0075] The configuration of the gaps used to perform GNSS positioning,

[0076] In the event that the current GNSS position of the wireless terminal is invalid, performing at least one action,

[0077] An indication of whether the wireless terminal supports GNSS positioning in connected mode.

[0078] An indication of whether the wireless terminal supports performing GNSS positioning in the gap, or

[0079] An indication of whether the wireless terminal supports performing neighbor cell measurements in connected mode.

[0080] Preferably, the configuration of the gap includes at least one of: an offset, a start time, or a duration before the current GNSS position of the wireless terminal is invalidated.

[0081] Preferably, the action comprises at least one of: triggering RLF or remaining in connected mode.

[0082] The present disclosure relates to a wireless communication method for use in a wireless network node. The method includes sending a configuration message to a wireless terminal to enable performing a Global Navigation Satellite System (GNSS) positioning if an event occurs.

[0083] Various embodiments may preferably achieve the following features:

[0084] Preferably, if the event occurs, GNSS positioning is enabled to be performed in the gap while in connected mode.

[0085] Preferably, the event includes at least one of the following:

[0086] The current GNSS positioning of the wireless terminal is invalid or will become invalid.

[0087] at least one evaluation period is greater than or equal to the time during which the wireless terminal performs GNSS positioning, wherein the wireless terminal evaluates the radio link quality during the evaluation period,

[0088] At least one discontinuous reception DRX cycle is greater than or equal to the time for the wireless terminal to perform GNSS positioning,

[0089] The DRX inactivity time or DRX cycle is greater than or equal to the time for the wireless terminal to perform GNSS positioning.

[0090] DRX period is equal to sf2048,

[0091] DRX onDurationTimer is less than or equal to psf40,

[0092] The time for the wireless terminal to perform GNSS positioning is less than the threshold.

[0093] The startup type of GNSS positioning is hot start or warm start.

[0094] The data buffer is not empty,

[0095] There is subsequent data transmission,

[0096] The quality of service (QoS) meets delay-sensitive requirements, or

[0097] The interval between arriving data is less than the threshold.

[0098] Preferably, sf2048 is a candidate value configured for DRX configuration (eg, for a DRX cycle).

[0099] Preferably, sf2048 ranges from 0 to 2047 (eg, INTEGER(0..2047)).

[0100] Preferably, psf40 is a candidate value configured for DRX configuration (eg, for DRX onDurationTimer or drx-InactivityTimer).

[0101] Preferably, the gap includes at least one of the following: a period not scheduled for data transmission or a DRX inactive time.

[0102] Preferably, the time period is a physical downlink control channel slot, or a downlink slot, or a slot configured for acquiring a GNSS position fix.

[0103] Preferably, the gap is greater than or equal to the time for the wireless terminal to perform GNSS positioning.

[0104] Preferably, the timing of the gap is no later than when the current GNSS position of the wireless terminal becomes invalid.

[0105] Preferably, the configuration message enables: if an event occurs, performing GNSS positioning after triggering a radio link failure RLF.

[0106] Preferably, the event includes at least one of the following:

[0107] The current GNSS positioning of the wireless terminal is invalid or will become invalid.

[0108] at least one evaluation period is less than the time during which the wireless terminal performs GNSS positioning, wherein the wireless terminal evaluates the radio link quality during the evaluation period,

[0109] At least one DRX cycle is less than or equal to the time for the wireless terminal to perform GNSS positioning,

[0110] The DRX inactivity time or DRX cycle is shorter than the time for the wireless terminal to perform GNSS positioning.

[0111] The time for the wireless terminal to perform GNSS positioning is greater than the threshold.

[0112] The startup type of GNSS positioning is warm start or cold start.

[0113] The data buffer is not empty,

[0114] There is subsequent data transmission,

[0115] The quality of service (QoS) meets delay-sensitive requirements, or

[0116] The interval between arriving data is less than the threshold.

[0117] Preferably, the configuration message enables: if the event occurs, performing GNSS positioning by leaving connected mode or entering idle mode.

[0118] Preferably, the event includes at least one of the following:

[0119] The current GNSS positioning of the wireless terminal is invalid or will become invalid.

[0120] The data buffer is empty,

[0121] The quality of service (QoS) meets the delay-insensitive requirements.

[0122] The interval between arriving data is greater than the threshold, or

[0123] There is no subsequent data transfer.

[0124] Preferably, the configuration message comprises at least one of the following: a radio link control message or a system information block.

[0125] Preferably, the wireless communication method further comprises sending configuration information of the gap to the wireless terminal.

[0126] Preferably, the wireless communication method further comprises sending an indication or activation of a DRX cycle to the wireless terminal, wherein the gap comprises a DRX inactive time.

[0127] Preferably, the configuration information, indication or activation of the DRX cycle is included in a radio link control message, a system information block, a downlink control information or a medium access control element MAC CE.

[0128] Preferably, the configuration information of the gap includes at least one of the following: a start time, a duration, a period, an indication that the gap is used for GNSS positioning, or an activation indication that the gap is activated to be used for GNSS positioning.

[0129] Preferably, the indication or activation of the DRX cycle comprises at least one of the following: a start time, a duration, a period, an on-duration, an indication that the DRX cycle is used for GNSS positioning, or an identifier of the DRX cycle.

[0130] Preferably, the wireless communication method further comprises receiving assistance information associated with performing GNSS positioning from the wireless terminal.

[0131] Preferably, the auxiliary information includes at least one of the following:

[0132] The time required by a wireless terminal to perform GNSS positioning,

[0133] The startup type of GNSS positioning,

[0134] The configuration of the gaps used to perform GNSS positioning,

[0135] In the case where the current GNSS positioning of the wireless terminal is invalid, at least one action is performed,

[0136] An indication of whether the wireless terminal supports GNSS positioning in connected mode.

[0137] An indication of whether the wireless terminal supports performing GNSS positioning in the gap, or

[0138] An indication of whether the wireless terminal supports performing neighbor cell measurements in connected mode.

[0139] Preferably, the configuration of the gap includes at least one of: an offset, a duration, or a start time before the current GNSS position of the wireless terminal is invalidated.

[0140] Preferably, the action comprises at least one of: triggering RLF or remaining in connected mode.

[0141] The present disclosure relates to a wireless communication method for use in a wireless terminal. The method comprises: when in connected mode, triggering neighbor cell measurement no later than the time when a serving cell stops serving the wireless terminal.

[0142] Various embodiments may preferably achieve the following features:

[0143] Preferably, the wireless communication method further comprises: receiving configuration of an offset time or a start time of neighbor cell measurement from a radio network node, wherein the neighbor cell measurement is performed at the offset time before the time when the serving cell stops serving the wireless terminal.

[0144] Preferably, triggering the neighbor cell measurement no later than the time when the serving cell stops serving the wireless terminal when in the connected mode includes at least one of the following:

[0145] If the change in the distance between the wireless terminal and the radio network node of the serving cell is greater than a first threshold, triggering neighboring cell measurement,

[0146] If the increment of the distance between the wireless terminal and the radio network node of the serving cell is greater than a second threshold, triggering neighboring cell measurement,

[0147] If the change in timing advance between the wireless terminal and the radio network node of the serving cell is greater than a third threshold, then triggering neighboring cell measurement, or

[0148] If the increment of the timing advance between the wireless terminal and the radio network node of the serving cell is greater than a fourth threshold, neighboring cell measurement is triggered.

[0149] Preferably, neighboring cells are detected, and a measurement result of the detected neighboring cells is greater than a fifth threshold, and the wireless communication method includes initiating radio resource control reestablishment based on the neighboring cell measurement.

[0150] Preferably, the validation timer for non-terrestrial network specific system information blocks is disabled.

[0151] Preferably, the current GNSS position of the wireless terminal becomes invalid.

[0152] Preferably, the wireless communication method further comprises receiving a request from a radio network node for assistance information associated with performing neighbor cell measurements.

[0153] Preferably, the wireless communication method further comprises sending assistance information associated with performing neighbor cell measurements to the radio network node.

[0154] Preferably, the auxiliary information indicates at least one of the following:

[0155] Neighbor cell measurements cannot be completed before initiating RRC reestablishment.

[0156] The target cell cannot be determined before initiating the radio resource control reestablishment.

[0157] The neighbor cell measurements made before RRC reestablishment is initiated become invalid.

[0158] The gap between the completion time of the neighbor cell measurement and the initiation time of the radio resource control re-establishment is greater than a sixth threshold, or

[0159] The synchronization indication is not received while the timer T310 is running.

[0160] The present disclosure relates to a wireless communication method for use in a wireless network node. The method includes: sending an offset time or a configuration of a start time of neighbor cell measurement performed by the wireless terminal in a connected mode to a wireless terminal, wherein based on the configuration, the neighbor cell measurement is performed by the wireless terminal in the connected mode at the offset time before the time when the serving cell of the wireless terminal stops serving the wireless terminal.

[0161] Various embodiments may preferably achieve the following features:

[0162] Preferably, the wireless communication method further comprises sending a request to the wireless terminal for assistance information associated with performing neighbor cell measurements.

[0163] Preferably, the wireless communication method further comprises receiving, from the wireless terminal, assistance information associated with performing neighbor cell measurements.

[0164] Preferably, the auxiliary information indicates at least one of the following:

[0165] Neighbor cell measurements cannot be completed before initiating RRC reestablishment.

[0166] The target cell cannot be determined before initiating RRC reestablishment.

[0167] The neighbor cell measurements made before RRC reestablishment is initiated become invalid.

[0168] The gap between the completion time of the neighbor cell measurement and the initiation time of the radio resource control re-establishment is greater than a sixth threshold, or

[0169] The synchronization indication is not received while the timer T310 is running.

[0170] The present disclosure relates to a wireless terminal. The wireless terminal comprises:

[0171] a communication unit, and

[0172] The processor is configured to perform a Global Navigation Satellite System (GNSS) positioning if the event occurs.

[0173] Various embodiments may preferably achieve the following features:

[0174] Preferably, the processor is further configured to execute any one of the above wireless communication methods.

[0175] The present disclosure relates to a wireless network node. The wireless network node comprises:

[0176] The communication unit is configured to send a configuration message to the wireless terminal to enable execution of Global Navigation Satellite System (GNSS) positioning if an event occurs.

[0177] Various embodiments may preferably achieve the following features:

[0178] Preferably, the wireless network node further comprises a processor, wherein the processor is configured to execute any one of the above wireless communication methods.

[0179] The present disclosure relates to a wireless terminal. The wireless terminal comprises:

[0180] a communication unit, and

[0181] A processor is configured to: trigger neighbor cell measurement no later than the time when the serving cell stops serving the wireless terminal when in connected mode.

[0182] Various embodiments may preferably achieve the following features:

[0183] Preferably, the processor is further configured to execute any one of the above wireless communication methods.

[0184] The present disclosure relates to a wireless network node. The wireless network node comprises:

[0185] a communication unit configured to send to a wireless terminal an offset time or a configuration of a start time of a neighbor cell measurement performed by the wireless terminal in a connected mode,

[0186] Wherein, based on the configuration, the wireless terminal performs the neighbor cell measurement in the connected mode at the offset time before the time when the serving cell of the wireless terminal stops serving the wireless terminal.

[0187] Various embodiments may preferably achieve the following features:

[0188] Preferably, the wireless network node further comprises a processor, wherein the processor is configured to execute any one of the above wireless communication methods.

[0189] The present disclosure relates to a computer program product, which includes a computer-readable program medium code stored thereon, which, when executed by a processor, causes the processor to implement the wireless communication method described in any one of the aforementioned methods.

[0190] The exemplary embodiments disclosed herein are intended to provide features that will become apparent by reference to the following description when taken in conjunction with the accompanying drawings. According to various embodiments, exemplary systems, methods, devices, and computer program products are disclosed herein. However, it should be understood that these embodiments are presented by way of example and not limitation, and it will be apparent to those of ordinary skill in the art who read this disclosure that various modifications may be made to the disclosed embodiments while remaining within the scope of this disclosure.

[0191] Therefore, the present disclosure is not limited to the exemplary embodiments and applications described and illustrated herein. In addition, the specific order and / or hierarchy of steps in the methods disclosed herein are merely exemplary methods. Based on design preferences, the specific order or hierarchy of steps of the disclosed methods or processes can be rearranged while remaining within the scope of the present disclosure. Therefore, it will be understood by those of ordinary skill in the art that the methods and techniques disclosed herein present various steps or actions in a sample order, and unless otherwise expressly stated, the present disclosure is not limited to the specific order or hierarchy presented. BRIEF DESCRIPTION OF THE DRAWINGS

[0192] The above and other aspects and implementations thereof are described in more detail in the drawings, the description and the claims.

[0193] Figure 1 A schematic diagram of a network according to an embodiment of the present disclosure is shown.

[0194] Figure 2 An example of a schematic diagram of a wireless terminal according to an embodiment of the present disclosure is shown.

[0195] Figure 3 An example of a schematic diagram of a wireless network node according to an embodiment of the present disclosure is shown.

[0196] Figure 4 A flow chart of a method according to an embodiment of the present disclosure is shown.

[0197] Figure 5 A flow chart of a method according to an embodiment of the present disclosure is shown.

[0198] Figure 6 A flow chart of a method according to an embodiment of the present disclosure is shown.

[0199] Figure 7 A flow chart of a method according to an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0200] In some embodiments, when the UE is in radio resource control (RRC) connected mode, the UE's global navigation satellite system (GNSS) positioning and / or uplink (UL) synchronization may lose their effectiveness. In order to reduce the interruption time, the UE can acquire GNSS positioning and resume transmission accordingly. However, the time for the UE to perform GNSS positioning may last for several seconds (e.g., 1 or 2 seconds for a hot start, several seconds for a warm start, and several minutes for a cold start). Due to hardware limitations, when the UE performs GNSS positioning, the IoT module in the UE cannot work, the UE cannot perform radio link monitoring, and downlink (DL) link failure may occur. Therefore, the UE may need to appropriately select the method of performing GNSS positioning in RRC connected mode according to the GNSS operation.

[0201] Note that the UE performing GNSS positioning may mean that the UE determines its GNSS positioning or performs GNSS positioning.

[0202] In one embodiment, the gNB may enable the UE to trigger a radio link failure (RLF) via an RRC message or a system information block (SIB) when the GNSS positioning becomes invalid. If the gNB configures the UE to trigger RLF when the GNSS positioning becomes invalid via an RRC message or SIB, the UE in connected mode triggers RLF when the GNSS positioning becomes invalid. If the gNB does not configure the UE to trigger RLF when the GNSS positioning becomes invalid via an RRC message or SIB, the UE in connected mode may need to leave connected mode (e.g., enter idle mode) when the GNSS positioning becomes invalid.

[0203] In one embodiment, the gNB may enable the UE to perform GNSS positioning by using gaps via RRC messages or SIBs when GNSS positioning becomes invalid or is about to be invalid. In this embodiment, when GNSS positioning becomes invalid or is about to be invalid, the UE in (RRC) connected mode may perform GNSS positioning in the gaps. The gaps may be (multiple) idle time slots that are not scheduled for data transmission, or discontinuous reception (DRX) inactivity time (e.g., DRX off period).

[0204] In one embodiment, when GNSS positioning becomes invalid or is about to become invalid and the condition is met, the gNB may enable the UE to perform GNSS positioning by using gaps via an RRC message or SIB. If the gNB configures the UE to perform GNSS positioning using gaps when GNSS positioning becomes invalid or is about to become invalid via an indication associated with the condition, the UE in connected mode may perform GNSS positioning using gaps when GNSS positioning becomes invalid or is about to become invalid and the condition is met. In this embodiment, the gap may be an idle time slot or DRX inactive time that is not scheduled for data transmission. If the condition is not met, the UE may trigger RLF when GNSS positioning becomes invalid.

[0205] In one embodiment, when the condition is met and the GNSS positioning becomes invalid or is about to become invalid, the UE can use (multiple) idle time slots that are not scheduled for data transmission to reacquire a new GNSS positioning. In this embodiment, the condition may be that at least one evaluation period is greater than or equal to the time when the UE performs GNSS positioning, where the evaluation period is the period during which the UE measures / evaluates the quality of the radio link. The number of evaluation periods is configured by the gNB or N311 (the maximum number of consecutive "in-sync" or "early in-sync" indications of the PCell received from the lower layer) or N310 (the maximum number of consecutive "out-of-sync" or "early out-of-sync" indications of the PCell received from the upper layer). In this embodiment, the condition may be that at least one DRX cycle is greater than or equal to the time when the UE performs GNSS positioning, where the number of DRX cycles is configured by the gNB or determined by the DRX period. The idle time slot may be a physical DL control channel (PDCCH) gap or a DL gap or a configured special gap for acquiring GNSS positioning. The length of the idle time slot is determined by at least one evaluation period or at least one DRX cycle. Note that the gap may be greater than or equal to the time when the UE performs GNSS positioning. In one embodiment, the timing of the gap is close to or before the time when the GNSS position fix becomes invalid.

[0206] In one embodiment, when the condition is met and the GNSS positioning becomes or will become invalid, the UE can use the DRX inactive time to reacquire a new GNSS positioning. In this embodiment, the condition can be that the DRX inactive time is greater than or equal to the first time threshold, the DRX cycle is greater than or equal to the second time threshold, or the DRX cycle is equal to sf2048 and onDurationTimer is less than or equal to psf40. The first time threshold and / or the second time threshold is equal to the time when the UE performs GNSS positioning. In addition, the timing of DRX is a timing close to or before the time when the GNSS positioning becomes or will become invalid.

[0207] Note that sf2048 is a candidate value configured for DRX configuration (e.g., for a DRX cycle). In one embodiment, the value of sf2048 corresponds to 2048 subframes. In addition, psf40 is a candidate value configured for DRX configuration (e.g., for a DRX onDurationTimer). psf40 may correspond to 40 PDCCH subframes.

[0208] In one embodiment, when the condition is met and the GNSS positioning becomes invalid, the UE may use the gap to reacquire a new GNSS positioning. In this embodiment, the condition may be that the time for the UE to perform GNSS positioning is short, for example, the time for the UE to perform GNSS positioning is less than a threshold, or the UE performs a hot start or warm start for GNSS positioning.

[0209] In one embodiment, when the condition is met and the GNSS position becomes invalid, the UE may use the gap to reacquire a new GNSS position. In this embodiment, the condition may be that there is data that needs to be sent or is to be sent (e.g., the data buffer is not empty), there is subsequent data that needs to be sent, the QoS (quality of service) meets the delay-sensitive requirement (e.g., the delay of the packet is less than a threshold), or the interval (time) between arriving data is less than a threshold.

[0210] In one embodiment, when the condition is met and the GNSS positioning becomes or will become invalid, the UE can trigger RLF to reacquire a new GNSS positioning. In this embodiment, the condition may be that the time when the UE performs GNSS positioning has a certain impact on the RLF, for example, when the UE performs GNSS positioning, an out-of-sync indication may be triggered. Alternatively or additionally, the condition may be that at least one evaluation period is less than the time when the UE performs GNSS positioning, where the evaluation period is the period during which the UE measures the quality of the radio link. Alternatively or additionally, the condition may be that at least one DRX cycle is less than the time when the UE performs GNSS positioning, where the length of the DRX cycle is configured by the gNB or is related to the evaluation period.

[0211] In one embodiment, when the condition is met and the GNSS positioning becomes or will become invalid, the UE may trigger RLF to reacquire a new GNSS positioning. In this embodiment, the condition may be that the DRX inactivity time is less than a first time threshold, and / or the DRX cycle is less than a second time threshold. The first time threshold and / or the second time threshold are equal to the time when the UE performs GNSS positioning.

[0212] In one embodiment, when the condition is met and the GNSS positioning becomes invalid, the UE may trigger RLF. In this embodiment, the condition may be that the time for the UE to perform GNSS positioning is large (e.g., the time for the UE to perform GNSS positioning is higher than a threshold), or the UE performs a warm start or a cold start for GNSS positioning.

[0213] In one embodiment, when the condition is met and the GNSS positioning becomes invalid, the UE may trigger RLF to reacquire a new GNSS positioning. In this embodiment, the condition may be that there is data that needs to be sent or to be sent (e.g., the data buffer is not empty), there is subsequent data that needs to be sent, the QoS meets the delay-sensitive requirement (e.g., the delay of the packet is less than a threshold), or the interval (time) between arriving data is less than a threshold.

[0214] In one embodiment, the UE may leave connected mode or enter idle mode when the conditions are met and the GNSS positioning becomes invalid. In this embodiment, the conditions may be that the (data) buffer is empty, there is no subsequent DL and UL data transmission, the service QoS does not meet the delay-sensitive requirements, or the interval (time) between arriving data is large (e.g., above a threshold).

[0215] In some embodiments, if the UE performs GNSS positioning by using gaps, the gNB needs to maintain alignment with the UE.

[0216] In one embodiment, the gNB may indicate a gap to the UE and / or activate the UE to be able to perform GNSS positioning in the gap. For example, the gNB may indicate a PDCCH gap or a DL gap via a medium access control element (MAC CE) or DL ​​control information (DCI) or an RRC message or SIB. The configuration of the gap may be indicated in an RRC message, SIB, MAC CE, or DCI. In one embodiment, the configuration of the gap includes at least one of the following: a start time, a duration, a time period, an index, and an indication that the gap is used for GNSS positioning. Specifically, the start time may be the valid time of the MAC CE or DCI, or an offset time after the UE receives the MAC CE or DCCI. In addition, an activation indication of the activation gap may be carried in the MAC CE or DCI.

[0217] In one embodiment, the gNB may indicate the DRX cycle to the UE, or activate the UE to use the DRX cycle to perform GNSS positioning. For example, the gNB may indicate the DRX cycle to the UE via a MAC CE or DCI or an RRC message or SIB. The configuration of the DRX cycle may be indicated in an RRC message, an SIB, a MAC CE or a DCI, wherein the configuration includes at least one of the following: an indication that the start time of the DRX cycle, the duration of the DRX cycle, the period of the DRX cycle, the on-duration of the DRX cycle, and the inactive time of the DRX cycle are used for GNSS positioning. Note that the start time of using the DRX inactive time for GNSS positioning may be the valid time of the MAC CE or DCI, or an offset time after the UE receives the MAC CE or DCI. In addition, the identifier of the DRX cycle may be carried in the MAC CE or DCI and / or configured in the RRC message or SIB. In one embodiment, an activation indication for activating DRX may be carried in the MAC CE or DCI.

[0218] In some embodiments, if GNSS positioning is performed (using gaps), the UE may perform certain operations / processes.

[0219] In one embodiment, the UE starts a (guard) timer when performing GNSS positioning in the gap, wherein the length of the timer is determined based on the time the UE performs GNSS positioning. If the UE completes the GNSS positioning, the timer stops. If the UE cannot complete the GNSS positioning within the time or the timer expires, the UE triggers RLF or returns to idle mode.

[0220] In one embodiment, if the gNB indicates a gap or the UE selects a gap and the UE cannot perform GNSS positioning during the gap, the UE triggers RLF or returns to idle mode.

[0221] In one embodiment, after the UE completes GNSS positioning, the UE triggers a random access channel (RACH) (message / procedure) or a scheduling request (SR). For example, after the UE completes GNSS positioning and / or UL synchronization is restored, the UE may trigger RACH. In this embodiment, the configuration of RACH or SR is configured in an RRC message or SIB, wherein the configuration includes at least one of the following: (multiple) frequency or time resources of RACH or SR, and an indication that RACH is dedicated / exclusively used for GNSS positioning.

[0222] In one embodiment, after the UE completes / ends GNSS positioning, the UE generates a MAC CE for reporting the GNSS positioning validity duration. The MAC CE may carry a MAC CE type indicating a GNSS report, or an indication that the GNSS positioning has been completed. Alternatively or additionally, the MAC CE may carry a value for the GNSS positioning validity duration. The value of the GNSS positioning validity duration may be the remaining time that the GNSS positioning is valid, or an index of the GNSS duration configured in the RRC message or SIB. If the MAC entity has UL resources allocated for a new transmission, the UE may send a MAC CE. If the MAC entity does not allocate UL resources for a new transmission, the UE may trigger an SR or RACH.

[0223] In one embodiment, when / after GNSS positioning becomes invalid, the UE clears the Hybrid Automatic Repeat Request (HARQ) buffer and / or releases all UL resources and / or stops UL transmission.

[0224] In one embodiment, the UE may resume UL transmission when / after GNSS positioning becomes valid or UL synchronization is restored.

[0225] In some embodiments, if invalid GNSS positioning triggers RLF or release, the UE may report certain assistance information to the gNB, for example, to help the gNB make a decision.

[0226] In one embodiment, the gNB may request the UE to report certain assistance information via an RRC message (e.g., UEInformationRequest). The RRC message may carry an indication requesting the UE to report assistance information associated with GNSS positioning.

[0227] In one embodiment, the UE reports the assistance information to the gNB via an RRC message (e.g., UEInformationResponse or UEAssistanceInformation). The RRC message may carry assistance information associated with GNSS positioning.

[0228] In one embodiment, the auxiliary information may include at least one of the following:

[0229] - The time when the UE needs to perform GNSS positioning, or the GNSS type (such as hot start, warm start);

[0230] - expected gap time (e.g., start time, duration, offset before GNSS becomes invalid);

[0231] - Actions performed by the UE when GNSS positioning becomes invalid (e.g. triggering RLF and / or remaining in connected mode).

[0232] In some embodiments, UE capabilities associated with GNSS and / or neighbor cell measurements may be reported to the gNB.

[0233] In one embodiment, the information in the UE capability may include at least one of the following:

[0234] - an indication of whether the UE supports GNSS operation in connected mode;

[0235] - an indication of whether the UE supports GNSS operation using gaps in connected mode;

[0236] - the duration and / or GNSS type (such as hot start, warm start) required for the UE to perform GNSS positioning; or

[0237] -Indication of whether the UE supports conditions for neighbour cell measurements in connected mode based on timing advance, elevation angle and / or distance.

[0238] In some embodiments, if the (NB-IoT) UE is in connected mode and the serving cell is about to go out of service, the UE may start neighbor cell measurements or RRC reestablishment to facilitate / accelerate the UE's selection of the next cell via RRC reestablishment.

[0239] In one embodiment, before or when the serving cell is about to stop serving the current area where the UE is located, the UE may start measurements of neighbor cells (i.e., neighbor cell measurements) regardless of the quality of service (e.g., RSRP) of the serving cell. The time to start neighbor cell measurements may be controlled by the gNB or the UE. If the exact time to start neighbor cell measurements may be controlled by the gNB, the gNB configures the start time and / or an offset time before the serving cell is about to stop serving.

[0240] In one embodiment, if the change in the distance between the UE and the serving satellite is higher than a first threshold, or the increase / increment in the distance between the UE and the serving satellite is higher than a second threshold, the UE may trigger neighbor cell measurement.

[0241] In one embodiment, if the change in timing advance between the UE and the serving satellite is higher than a third threshold, or the increase / increment in distance between the UE and the serving satellite is higher than a fourth threshold, the UE may trigger neighbor cell measurement.

[0242] In one embodiment, if a neighbor cell is detected or the measurement result of the neighbor cell is higher than the fifth threshold, and the verification timer of the NTN dedicated SIB expires, the UE may initiate an RRC reestablishment (process / procedure).

[0243] In one embodiment, if a neighbor cell is detected or the measurement result of the neighbor cell is higher than the sixth threshold, and the GNSS threshold becomes invalid, the UE may initiate an RRC reestablishment (process / procedure).

[0244] In some embodiments, if the condition for triggering neighbor cell measurement is met too late to allow the UE to complete the neighbor cell measurement before selecting the next serving cell, the delay caused by the RRC reestablishment process cannot be shortened. When the condition for triggering neighbor cell measurement is met too early, if the measurement is a short measurement, or the UE may need to perform another measurement for RRC reestablishment, the measurement result may be invalid for the cell selection for subsequent RRC reestablishment. In other words, the condition for triggering (multiple) intra-frequency or inter-frequency measurements may not be set appropriately.

[0245] In one embodiment, the gNB may request the UE to report certain assistance information via an RRC message (e.g., UEInformationRequest). The RRC message may carry an indication requesting the UE to report assistance information associated with GNSS positioning.

[0246] In one embodiment, the UE may report assistance information to the gNB via an RRC message (e.g., UEInformationResponse, UEAssistanceInformation, RRC Reestablishment Request, or RRC Reestablishment Complete). The RRC message may carry assistance information associated with neighbor cell measurements (results).

[0247] In one embodiment, the condition for triggering neighbor cell measurement may be too late or too early. The too late condition means that the UE cannot complete / end the neighbor cell measurement or detect a suitable cell before RRC reestablishment. The too early condition means that the neighbor cell measurement result becomes invalid before RRC reestablishment, or there is a long interval between the time when the UE ends / completes the neighbor cell measurement and the time when the UE triggers RRC reestablishment.

[0248] In one embodiment, the RRC reestablishment is triggered too late. Triggering too late means that the UE cannot receive a synchronization indication during the running of the timer T310.

[0249] Figure 2 A schematic diagram of a wireless terminal 20 according to an embodiment of the present disclosure is provided. The wireless terminal 20 may be a user equipment (UE), a mobile phone, a laptop, a tablet computer, an e-book, or a portable computer system, and is not limited thereto. The wireless terminal 20 may include a processor 200 such as a microprocessor or an application-specific integrated circuit (ASIC), a storage unit 210, and a communication unit 220. The storage unit 210 may be any data storage device that stores program code 212 accessed and executed by the processor 200. Embodiments of the storage unit 210 include, but are not limited to, a subscriber identity module (SIM), a read-only memory (ROM), a flash memory, a random access memory (RAM), a hard disk, and an optical data storage device. The communication unit 220 may be a transceiver, and is used to transmit and receive signals (e.g., messages or packets) according to the processing results of the processor 200. In one embodiment, the communication unit 220 communicates with the user via a communication device. Figure 2 At least one antenna 222 is shown for transmitting and receiving signals.

[0250] In one embodiment, the storage unit 210 and the program code 212 may be omitted, and the processor 200 may include the storage unit with the stored program code.

[0251] Processor 200 may implement any of the steps in the exemplary embodiments on wireless terminal 20 , for example, by executing program code 212 .

[0252] The communication unit 220 may be a transceiver. Alternatively or additionally, the communication unit 220 may combine a transmitting unit and a receiving unit configured to respectively transmit and receive signals to and from a wireless network node (eg, a base station).

[0253] Figure 3 A schematic diagram of a radio network node 30 according to an embodiment of the present disclosure is provided. The radio network node 30 may be a satellite, a base station (BS), a network entity, a mobility management entity (MME), a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), a radio access network (RAN) node, a next generation RAN (NG-RAN) node, a gNB, an eNB, a gNB central unit (gNB-CU), a gNB distributed unit (gNB-DU), a data network, a core network, or a radio network controller (RNC), and is not limited thereto. In addition, the radio network node 30 may include (execute) at least one network function, such as an access and mobility management function (AMF), a session management function (SMF), a user location function (UPF), a policy control function (PCF), an application function (AF), etc. The radio network node 30 may include a processor 300 such as a microprocessor or an ASIC, a storage unit 310, and a communication unit 320. The storage unit 310 may be any data storage device that stores a program code 312 accessed and executed by the processor 300. Examples of the storage unit 310 include, but are not limited to, a SIM, a ROM, a flash memory, a RAM, a hard disk, and an optical data storage device. The communication unit 320 may be a transceiver and is used to transmit and receive signals (e.g., messages or packets) according to the processing results of the processor 300. In one example, the communication unit 320 communicates with the processor 300 via Figure 3 At least one antenna 322 is shown for transmitting and receiving signals.

[0254] In one embodiment, storage may be omitted for unit 310 and program code 312. Processor 300 may include a storage unit with stored program code.

[0255] The processor 300 may implement any of the steps described in the example embodiments on the radio network node 30 , for example via executing the program code 312 .

[0256] The communication unit 320 may be a transceiver. Alternatively or additionally, the communication unit 320 may combine a transmitting unit and a receiving unit configured to respectively transmit and receive signals to and from a wireless terminal (eg, a user equipment or another wireless network node).

[0257] Figure 4 A flow chart of a method according to an embodiment of the present disclosure is shown. Figure 4 The method shown may be used in a wireless terminal (e.g., UE) and includes the following steps:

[0258] Step 401: If an event occurs, GNSS positioning is performed.

[0259] In this embodiment, if the event occurs, the wireless terminal may perform GNSS positioning.

[0260] In one embodiment, if an event occurs, the wireless terminal in (RRC) connection mode performs GNSS positioning in the gap. In this embodiment, the event may include at least one of the following:

[0261] The current GNSS positioning of the wireless terminal is invalid or will become invalid.

[0262] at least one evaluation period is greater than or equal to the time during which the wireless terminal performs GNSS positioning, wherein the wireless terminal evaluates the radio link quality during the evaluation period,

[0263] At least one DRX cycle is greater than or equal to the time for the wireless terminal to perform GNSS positioning,

[0264] The DRX inactivity time or DRX cycle is greater than or equal to the time for the wireless terminal to perform GNSS positioning.

[0265] DRX period is equal to sf2048,

[0266] DRX onDurationTimer is less than or equal to psf40,

[0267] The time for the wireless terminal to perform GNSS positioning is less than the threshold.

[0268] The startup type of GNSS positioning is hot start or warm start.

[0269] The data buffer is not empty,

[0270] There is subsequent data transmission,

[0271] The quality of service (QoS) meets delay-sensitive requirements, or

[0272] The interval between arriving data is less than the threshold.

[0273] In one embodiment, the gap may include at least one of the following: a period not scheduled for data transmission or a DRX inactive time. For example, the period is a PDCCH gap, a DL gap, or a gap configured for obtaining GNSS positioning. Note that the gap may be greater than or equal to the time when the wireless terminal performs GNSS positioning.

[0274] In one embodiment, the timing of the gap is no later than (ie, before or when) the current GNSS position of the wireless terminal becomes invalid.

[0275] In one embodiment, if an event occurs, the wireless terminal performs GNSS positioning after triggering RLF. In this embodiment, the event includes at least one of the following:

[0276] The current GNSS positioning of the wireless terminal is invalid or will become invalid.

[0277] At least one evaluation period is less than the time for the wireless terminal to perform GNSS positioning, wherein the wireless terminal evaluates the link quality during the evaluation period,

[0278] At least one DRX cycle is less than or equal to the time for the wireless terminal to perform GNSS positioning,

[0279] The DRX inactivity time or DRX cycle is shorter than the time for the wireless terminal to perform GNSS positioning.

[0280] The time for the wireless terminal to perform GNSS positioning is greater than the threshold.

[0281] The startup type of GNSS positioning is warm start or cold start.

[0282] The data buffer is not empty,

[0283] There is subsequent data transmission,

[0284] QoS meets delay-sensitive requirements, or

[0285] The interval between arriving data is less than the threshold.

[0286] In one embodiment, if an event occurs, the wireless terminal may perform GNSS positioning by leaving the connected mode or entering the idle mode. In this embodiment, the event may include at least one of the following:

[0287] The current GNSS positioning of the wireless terminal is invalid or will become invalid.

[0288] The data buffer is empty,

[0289] QoS meets the delay-insensitive requirement,

[0290] The interval between arriving data is greater than the threshold, or

[0291] There is no subsequent data transfer.

[0292] In one embodiment, if the event occurs, the wireless terminal receives a configuration message from a wireless network node (e.g., BS, gNB) that enables GNSS positioning. For example, the configuration message includes at least one of the following: a radio link control message or a system information block.

[0293] In one embodiment, the wireless terminal may receive configuration information of the gap from the wireless network node.

[0294] In one embodiment, the wireless terminal may receive an indication or activation of a DRX cycle from a radio network node, wherein the gaps include DRX inactivity times.

[0295] In one embodiment, the configuration information, indication or activation of the DRX cycle is included in an RRC message, SIB, DCI or MAC CE.

[0296] In one embodiment, the configuration information of the gap includes at least one of the following: a start time, a duration, a period, an indication that the gap is used for GNSS positioning, or an activation indication to activate the gap to be used for GNSS positioning.

[0297] In one embodiment, the indication or activation of the DRX cycle includes at least one of: a start time, a duration, a period, an on-duration, an indication that the DRX cycle is used for GNSS positioning, or an identification of the DRX cycle.

[0298] In one embodiment, if the event occurs, the wireless terminal performs GNSS positioning in the gap while in connected mode by performing at least one of the following:

[0299] starting a timer, wherein the length of the timer is determined based on the time at which the wireless terminal performs GNSS positioning,

[0300] When GNSS positioning is completed, stop the timer.

[0301] If GNSS positioning fails, GNSS positioning cannot be performed, or the timer expires, RLF is triggered or the idle mode is entered.

[0302] After completing GNSS positioning or restoring uplink synchronization, the random access channel RACH or scheduling request SR is triggered.

[0303] After completing the GNSS positioning, a MAC CE is generated to report the validity duration of the new GNSS positioning obtained through the completed GNSS positioning.

[0304] Sending a MAC CE in the UL source allocated for subsequent transmission,

[0305] Triggering SR or RACH for sending MAC CE,

[0306] If the current GNSS position of the wireless terminal becomes invalid, clearing the HARQ buffer,

[0307] If the current GNSS position of the wireless terminal becomes invalid, the uplink resources are released, or

[0308] After completing GNSS positioning or restoring uplink synchronization, uplink transmission is resumed.

[0309] In one embodiment, the wireless terminal sends assistance information associated with (performing) GNSS positioning to the wireless network node. For example, the assistance information includes at least one of the following:

[0310] The time required by a wireless terminal to perform GNSS positioning,

[0311] The startup type of GNSS positioning,

[0312] the (desired) configuration of the gaps to be used to perform GNSS positioning,

[0313] In the event that the current GNSS position of the wireless terminal is invalid, performing at least one action,

[0314] An indication of whether the wireless terminal supports GNSS positioning in connected mode.

[0315] An indication of whether the wireless terminal supports performing GNSS positioning in the gap, or

[0316] An indication of whether the wireless terminal supports performing neighbor cell measurements in connected mode.

[0317] In one embodiment, the (desired) configuration of the gap comprises at least one of: an offset, a start time or a duration before a current GNSS position of the wireless terminal is invalidated.

[0318] In one embodiment, when the current GNSS positioning of the wireless terminal is invalid, the performed action includes at least one of the following: triggering RLF or maintaining in the connected mode.

[0319] Figure 5 A flow chart of a method according to an embodiment of the present disclosure is shown. Figure 5 The method shown may be used in a radio network node (e.g., a BS or a gNB) and comprises the following steps:

[0320] Step 501: Send a configuration message to a wireless terminal to enable GNSS positioning to be performed if an event occurs.

[0321] Specifically, the radio network node sends a configuration message to the wireless terminal (eg, UE) to enable execution of GNSS positioning (function) if the event occurs.

[0322] In one embodiment, if an event occurs, the GNSS positioning is enabled in the gap when in the connected mode. For example, the event includes at least one of the following:

[0323] The current GNSS positioning of the wireless terminal is invalid or will become invalid.

[0324] at least one evaluation period is greater than or equal to the time during which the wireless terminal performs GNSS positioning, wherein the wireless terminal evaluates the radio link quality during the evaluation period,

[0325] At least one DRX cycle is greater than or equal to the time for the wireless terminal to perform GNSS positioning,

[0326] The DRX inactivity time or DRX cycle is greater than or equal to the time for the wireless terminal to perform GNSS positioning.

[0327] DRX period is equal to sf2048,

[0328] DRX onDurationTimer is less than or equal to psf40,

[0329] The time for the wireless terminal to perform GNSS positioning is less than the threshold.

[0330] The startup type of GNSS positioning is hot start or warm start.

[0331] The data buffer is not empty,

[0332] There is subsequent data transmission,

[0333] QoS meets delay-sensitive requirements, or

[0334] The interval between arriving data is less than the threshold.

[0335] In one embodiment, the gap includes at least one of: a period not scheduled for data transmission or a DRX inactive time.

[0336] In one embodiment, the period is a PDCCH gap or a DL gap or a gap configured for acquiring a GNSS position fix.

[0337] In one embodiment, the gap is greater than or equal to the time the wireless terminal performs GNSS positioning.

[0338] In one embodiment, the timing of the gap is no later than (ie, before or when) the current GNSS position of the wireless terminal becomes invalid.

[0339] In one embodiment, the configuration message enables: if an event occurs, then GNSS positioning is performed after triggering RLF. In this embodiment, the event includes at least one of the following:

[0340] The current GNSS positioning of the wireless terminal is invalid or will become invalid.

[0341] at least one evaluation period is less than the time during which the wireless terminal performs GNSS positioning, wherein the wireless terminal evaluates the radio link quality during the evaluation period,

[0342] At least one DRX cycle is less than or equal to the time for the wireless terminal to perform GNSS positioning,

[0343] The DRX inactivity time or DRX cycle is shorter than the time for the wireless terminal to perform GNSS positioning.

[0344] The time for the wireless terminal to perform GNSS positioning is greater than the threshold.

[0345] The startup type of GNSS positioning is warm start or cold start.

[0346] The data buffer is not empty,

[0347] There is subsequent data transmission,

[0348] QoS meets delay-sensitive requirements, or

[0349] The interval between arriving data is less than the threshold.

[0350] In one embodiment, the configuration message enables: if an event occurs, GNSS positioning is performed by leaving the connected mode or entering the idle mode. In this embodiment, the event may include at least one of the following:

[0351] The current GNSS positioning of the wireless terminal is invalid or will become invalid.

[0352] The data buffer is empty,

[0353] QoS meets the delay-insensitive requirement,

[0354] The interval between arriving data is greater than the threshold, or

[0355] There is no subsequent data transfer.

[0356] In one embodiment, the configuration message includes at least one of the following: an RRC message or a SIB.

[0357] In one embodiment, the radio network node sends configuration information of the gap to the wireless terminal.

[0358] In one embodiment, the radio network node sends an indication or activation of a DRX cycle, wherein the gaps include DRX inactivity times.

[0359] In one embodiment, the configuration information, indication or activation of the DRX cycle is included in an RRC message, SIB, DCI or MAC CE.

[0360] In one embodiment, the configuration information of the gap includes at least one of the following: a start time, a duration, a period, an indication that the gap is used for GNSS positioning, or an activation indication to activate the gap to be used for GNSS positioning.

[0361] In one embodiment, the indication or activation of the DRX cycle includes at least one of: a start time, a duration, a period, an on-duration, an indication that the DRX cycle is used for GNSS positioning, or an identification of the DRX cycle.

[0362] In one embodiment, a wireless network node receives assistance information associated with (performing) a GNSS positioning.

[0363] In one embodiment, the auxiliary information includes at least one of the following:

[0364] The time required by a wireless terminal to perform GNSS positioning,

[0365] The startup type of GNSS positioning,

[0366] the (desired) configuration of the gaps to be used to perform GNSS positioning,

[0367] In the case where the current GNSS positioning of the wireless terminal is invalid, at least one action is performed,

[0368] An indication of whether the wireless terminal supports GNSS positioning in connected mode.

[0369] An indication of whether the wireless terminal supports performing GNSS positioning in the gap, or

[0370] An indication of whether the wireless terminal supports performing neighbor cell measurements in connected mode.

[0371] In one embodiment, the (desired) configuration of the gap comprises at least one of: an offset, a duration, or a start time before the wireless terminal's current GNSS position is invalidated.

[0372] In one embodiment, the action performed when the current GNSS positioning of the wireless terminal is invalid includes at least one of the following: triggering RLF or maintaining in a connected mode.

[0373] Figure 6 A flow chart of a method according to an embodiment of the present disclosure is shown. Figure 6 The method shown may be used in a wireless terminal (e.g., UE) and includes the following steps:

[0374] Step 601: When in connected mode, trigger neighbor cell measurement no later than the time when the serving cell stops serving the wireless terminal.

[0375] In this embodiment, the wireless terminal in connected mode performs / trigger neighbour cell measurements no later than (before or when) the serving cell stops serving the wireless terminal.

[0376] In one embodiment, the wireless terminal receives a configuration of an offset time or a start time of neighbor cell measurements from a wireless network node (e.g., a BS or gNB), wherein the neighbor cell measurements are performed at the offset time before the time when the serving cell stops serving the wireless terminal.

[0377] In one embodiment, the wireless terminal triggers neighbor cell measurements when in connected mode no later than the time when the serving cell stops serving the wireless terminal by performing at least one of the following:

[0378] If the change in the distance between the wireless terminal and the radio network node of the serving cell is greater than a first threshold, triggering neighboring cell measurement,

[0379] If the increment of the distance between the wireless terminal and the radio network node of the serving cell is greater than a second threshold, triggering neighboring cell measurement,

[0380] If the change in timing advance between the wireless terminal and the radio network node of the serving cell is greater than a third threshold, then triggering neighboring cell measurement, or

[0381] If the increment of the timing advance between the wireless terminal and the radio network node of the serving cell is greater than a fourth threshold, neighboring cell measurement is triggered.

[0382] In one embodiment, a neighboring cell is detected and the measurement result of the detected neighboring cell is greater than a fifth threshold. In this embodiment, the wireless terminal initiates RRC reconstruction based on the neighboring cell measurement. In addition, the verification timer for the non-terrestrial network dedicated system information block is invalid and / or the current GNSS positioning of the wireless terminal becomes invalid (when or before initiating RRC reconstruction).

[0383] In one embodiment, the wireless terminal receives a request from a radio network node for assistance information associated with performing neighbor cell measurements.

[0384] In one embodiment, the wireless terminal sends assistance information associated with performing neighbor cell measurements to the radio network node.

[0385] In one embodiment, the auxiliary information indicates at least one of the following:

[0386] Neighbor cell measurements cannot be completed before initiating RRC reestablishment.

[0387] The target cell cannot be determined before initiating RRC reestablishment.

[0388] The neighbor cell measurements made before RRC reestablishment is initiated become invalid.

[0389] The gap between the completion time of the neighbor cell measurement and the initiation time of the radio resource control re-establishment is greater than a sixth threshold, or

[0390] The synchronization indication is not received while the timer T310 is running.

[0391] Figure 7 A flow chart of a method according to an embodiment of the present disclosure is shown. Figure 7 The method shown may be used in a radio network node (e.g., a BS or a gNB) and comprises the following steps:

[0392] Step 701, sending an offset time or a configuration of a start time of a neighbor cell measurement performed by the wireless terminal in a connected mode to a wireless terminal.

[0393] Specifically, the radio network node transmits a configuration associated with neighbor cell measurements performed by the wireless terminal in connected mode. The configuration may include a start time for the neighbor cell measurements. Alternatively or additionally, the configuration may include an offset time, wherein based on the configuration, the neighbor cell measurements are performed by the wireless terminal at an offset time before the time when the serving cell of the wireless terminal stops serving the wireless terminal.

[0394] In one embodiment, the radio network node sends a request to the wireless terminal for assistance information associated with performing neighbor cell measurements.

[0395] In one embodiment, the radio network node receives assistance information associated with performing neighbor cell measurements from a wireless terminal.

[0396] In one embodiment, the auxiliary information indicates / includes at least one of the following:

[0397] Neighbor cell measurements cannot be completed before initiating RRC reestablishment.

[0398] The target cell cannot be determined before initiating RRC reestablishment.

[0399] The neighbor cell measurements made before RRC reestablishment is initiated become invalid.

[0400] The gap between the completion time of the neighbor cell measurement and the initiation time of the radio resource control re-establishment is greater than a sixth threshold, or

[0401] The synchronization indication is not received while the timer T310 is running.

[0402] Although various embodiments of the present disclosure have been described above, it should be understood that they are presented by way of example only, and not by way of limitation. Similarly, various figures may depict exemplary architectures or configurations, which are provided to enable those of ordinary skill in the art to understand the exemplary features and functions of the present disclosure. However, these persons will understand that the present disclosure is not limited to the example architectures or configurations shown, but may be implemented using various alternative architectures and configurations. In addition, as will be appreciated by those of ordinary skill in the art, one or more features of an embodiment may be combined with one or more features of another embodiment described herein. Therefore, the breadth and scope of the present disclosure should not be limited by any of the above-described exemplary embodiments.

[0403] It should also be understood that any reference to an element using the names "first", "second", etc. herein generally does not limit the number or order of these elements. Instead, these names can be used as a convenient means of distinguishing two or more elements or element instances in this article. Therefore, the reference to the first element and the second element does not mean that only two elements can be used or that the first element must be in some way before the second element.

[0404] In addition, those skilled in the art will understand that information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, and symbols such as may be referenced in the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0405] Those skilled in the art will further understand that any of the various illustrative logical blocks, units, processors, devices, circuits, methods, and functions described in conjunction with the various aspects disclosed herein may be implemented by electronic hardware (e.g., digital implementation, analog implementation, or a combination of the two), firmware, various forms of programs or design codes including instructions (for convenience, may be referred to herein as "software" or "software units"), or any combination of these technologies.

[0406] In order to clearly illustrate this interchangeability of hardware, firmware and software, the functions of various illustrative components, blocks, units, circuits and steps have been generally described above. Whether such functions are implemented as hardware, firmware or software, or a combination of these technologies depends on the specific application and the design constraints imposed on the entire system. Those skilled in the art can implement the described functions in various ways for each specific application, but such implementation decisions do not lead to deviations from the scope of this disclosure. According to various embodiments, processors, devices, components, circuits, structures, machines, units, etc. can be configured to perform one or more functions of the functions described herein. The terms "configured to" or "configured for" used herein with respect to a specified operation or function refer to a processor, device, component, circuit, structure, machine, unit, etc. that is physically constructed, programmed and / or arranged to perform a specified operation or function.

[0407] In addition, it will be understood by those skilled in the art that the various illustrative logic blocks, units, devices, components and circuits described herein may be implemented or performed within 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 device, or any combination thereof. The logic blocks, units and circuits may also include antennas and / or transceivers to communicate with various components within a network or within a device. The general-purpose processor may be a microprocessor, but in an alternative, 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 plurality of microprocessors, one or more microprocessors combined with a DSP core, or any other suitable configuration for performing the functions described herein. If implemented in software, the functions may be stored as one or more instructions or codes on a computer-readable medium. Therefore, the steps of the method or algorithm disclosed herein may be implemented as software stored on a computer-readable medium.

[0408] Computer-readable media include both computer storage media and communication media, and communication media include any media that can transfer a computer program or code from one place to another. Storage media can be any available media that a computer can access. As an example and not limitation, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, disk storage or other magnetic storage devices, or any other media that can be used to store desired program codes in the form of instructions or data structures and can be accessed by a computer.

[0409] In this document, the term "unit" as used herein refers to software, firmware, hardware, and any combination of these elements for performing the relevant functions described herein. In addition, for the purpose of discussion, various units are described as discrete units; however, as is clear to one of ordinary skill in the art, two or more units may be combined to form a single unit that performs the associated functions according to embodiments of the present disclosure.

[0410] In addition, memory or other storage devices and communication components can be used in embodiments of the present disclosure. It should be understood that, for the sake of clarity, the above description has described embodiments of the present disclosure with reference to different functional units and processors. However, it is clear that any appropriate functional distribution between different functional units, processing logic elements or domains can be used without departing from the present disclosure. For example, the functions shown as being performed by a separate processing logic element or controller can be performed by the same processing logic element or controller. Therefore, reference to a specific functional unit is only a reference to an appropriate means for providing the function, rather than an indication of a strict logical or physical structure or organization.

[0411] Various modifications to the implementations described in this disclosure will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other implementations without departing from the scope of the claims. Therefore, the present disclosure is not intended to be limited to the implementations shown herein, but should be consistent with the widest scope consistent with the novel features and principles disclosed herein, as described in the following claims.

Claims

1. A wireless communication method for use in a wireless terminal, the method comprising: If an event occurs, a Global Navigation Satellite System (GNSS) positioning is performed.

2. The wireless communication method according to claim 1, wherein performing the GNSS positioning if the event occurs comprises: If the event occurs, the GNSS positioning is performed in gaps while in connected mode.

3. The wireless communication method according to claim 2, wherein the event comprises at least one of the following: The current GNSS positioning of the wireless terminal is invalid or will become invalid, at least one evaluation period is greater than or equal to the time during which the wireless terminal performs the GNSS positioning, wherein the wireless terminal evaluates the radio link quality during the evaluation period, At least one discontinuous reception DRX cycle is greater than or equal to the time for the wireless terminal to perform the GNSS positioning, The DRX inactive time or the DRX cycle is greater than or equal to the time for the wireless terminal to perform the GNSS positioning. DRX period is equal to sf2048, DRX onDurationTimer is less than or equal to psf40, The time for the wireless terminal to perform the GNSS positioning is less than a threshold, The startup type of the GNSS positioning is hot start or warm start, The data buffer is not empty, There is subsequent data transmission, The quality of service (QoS) meets delay-sensitive requirements, or The interval between arriving data is less than the threshold. 4 . The wireless communication method according to claim 2 , wherein the gap comprises at least one of the following: a period not scheduled for data transmission or a DRX inactive time. 5 . The wireless communication method according to claim 4 , wherein the time period is a physical downlink control channel gap, a downlink gap, or a gap configured for acquiring the GNSS positioning. 6 . The wireless communication method according to claim 4 , wherein the gap is greater than or equal to a time for the wireless terminal to perform the GNSS positioning. 7 . The wireless communication method according to claim 4 , wherein the timing of the gap is no later than when the current GNSS positioning of the wireless terminal becomes invalid.

8. The wireless communication method according to any one of claims 1 to 7, wherein if the event occurs, performing the GNSS positioning comprises: If the event occurs, the GNSS positioning is performed after a radio link failure RLF is triggered.

9. The wireless communication method according to claim 8, wherein the event comprises at least one of the following: The current GNSS positioning of the wireless terminal is invalid or will become invalid, at least one evaluation period is less than the time for the wireless terminal to perform the GNSS positioning, wherein the wireless terminal evaluates the link quality during the evaluation period, At least one DRX cycle is less than or equal to the time for the wireless terminal to perform the GNSS positioning, The DRX inactivity time or the DRX cycle is shorter than the time for the wireless terminal to perform the GNSS positioning. The time for the wireless terminal to perform the GNSS positioning is greater than a threshold, The startup type of the GNSS positioning is warm start or cold start, The data buffer is not empty, There is subsequent data transmission, The quality of service (QoS) meets delay-sensitive requirements, or The interval between arriving data is less than the threshold.

10. The wireless communication method according to any one of claims 1 to 9, wherein if the event occurs, performing the GNSS positioning comprises: If the event occurs, the GNSS positioning is performed by leaving the connected mode or entering the idle mode.

11. The wireless communication method according to claim 10, wherein the event comprises at least one of the following: The current GNSS positioning of the wireless terminal is invalid or will become invalid, The data buffer is empty, The quality of service (QoS) meets the delay-insensitive requirements. The interval between arriving data is greater than the threshold, or There is no subsequent data transfer.

12. The wireless communication method according to any one of claims 1 to 11, further comprising: If the event occurs, a configuration message is received from a radio network node to enable the GNSS positioning to be performed.

13. The wireless communication method according to claim 12, wherein the configuration message comprises at least one of the following: a radio link control message or a system information block.

14. The wireless communication method according to any one of claims 2 to 13, further comprising: receiving configuration information of the gap from a wireless network node, or An indication or activation of a DRX cycle is received from a radio network node, wherein the gap includes a DRX inactive time.

15. The wireless communication method according to claim 14, wherein the configuration information, the indication of the DRX cycle or the activation is included in a radio link control message, a system information block, a downlink control information, or a media access control element MAC CE.

16. The wireless communication method according to claim 14 or 15, wherein the configuration information of the gap comprises at least one of the following: a start time, a duration, a time period, an indication that the gap is used for the GNSS positioning, or an activation indication that the gap is to be used for the GNSS positioning.

17. A wireless communication method according to any one of claims 14 to 16, wherein the indication or the activation of the DRX cycle comprises at least one of the following: a start time, a duration, a time period, an on-duration, an indication that the DRX cycle is used for the GNSS positioning, or an identifier of the DRX cycle.

18. The wireless communication method according to any one of claims 2 to 17, wherein if the event occurs, performing the GNSS positioning in the gap while in the connected mode comprises at least one of the following: starting a timer, wherein the length of the timer is determined based on the time at which the wireless terminal performs the GNSS positioning, When the GNSS positioning is completed, stopping the timer, If the GNSS positioning fails, the GNSS positioning cannot be performed, or the timer expires, RLF is triggered or the idle mode is entered, After completing the GNSS positioning or restoring uplink synchronization, triggering a random access channel RACH or a scheduling request SR, After completing the GNSS positioning, generating a MAC CE for reporting the validity duration of a new GNSS positioning acquired through the completed GNSS positioning, sending the MAC CE in a UL source allocated for subsequent transmission, triggering an SR or RACH for sending the MAC CE, If the current GNSS position of the wireless terminal becomes invalid, clearing the hybrid automatic repeat request buffer, If the current GNSS position of the wireless terminal becomes invalid, then uplink resources are released, or After the GNSS positioning is completed or uplink synchronization is restored, uplink transmission is resumed.

19. The wireless communication method according to any one of claims 1 to 18, further comprising: Assistance information associated with performing the GNSS positioning is sent to a wireless network node.

20. The wireless communication method according to claim 19, wherein the auxiliary information comprises at least one of the following: the time required by the wireless terminal to perform the GNSS positioning, The startup type of the GNSS positioning, the configuration of the gaps used to perform the GNSS positioning, at least one action performed if the current GNSS position of the wireless terminal is invalid, an indication of whether the wireless terminal supports performing the GNSS positioning in connected mode, an indication of whether the wireless terminal supports performing the GNSS positioning in the gap, or An indication of whether the wireless terminal supports performing neighbor cell measurements in connected mode.

21. The wireless communication method of claim 20, wherein the configuration of the gap comprises at least one of: an offset, a duration, or a start time before a current GNSS position of the wireless terminal is invalidated.

22. The wireless communication method according to claim 20 or 21, wherein the action comprises at least one of the following: triggering RLF or maintaining in the connected mode.

23. A wireless communication method for use in a wireless network node, the method comprising: A configuration message is sent to the wireless terminal to enable a Global Navigation Satellite System (GNSS) positioning to be performed if the event occurs.

24. The wireless communication method of claim 23, wherein the configuration message enables: if the event occurs, performing the GNSS positioning in a gap while in connected mode.

25. The wireless communication method according to claim 23, wherein the event comprises at least one of the following: The current GNSS positioning of the wireless terminal is invalid or will become invalid, at least one evaluation period is greater than or equal to the time during which the wireless terminal performs the GNSS positioning, wherein the wireless terminal evaluates the radio link quality during the evaluation period, At least one discontinuous reception DRX cycle is greater than or equal to the time for the wireless terminal to perform the GNSS positioning, The DRX inactive time or the DRX cycle is greater than or equal to the time for the wireless terminal to perform the GNSS positioning. DRX period is equal to sf2048, DRX onDurationTimer is less than or equal to psf40, The time for the wireless terminal to perform the GNSS positioning is less than a threshold, The startup type of the GNSS positioning is hot start or warm start, The data buffer is not empty, There is subsequent data transmission, The quality of service (QoS) meets delay-sensitive requirements, or The interval between arriving data is less than the threshold.

26. The wireless communication method according to claim 24 or 25, wherein the gap comprises at least one of the following: a period not scheduled for data transmission or a DRX inactive time.

27. The wireless communication method of claim 26, wherein the period is a physical downlink control channel slot, or a downlink slot, or a slot configured for acquiring the GNSS position fix.

28. The wireless communication method according to claim 26 or 27, wherein the gap is greater than or equal to the time for the wireless terminal to perform the GNSS positioning.

29. The wireless communication method according to any one of claims 26 to 28, wherein the timing of the gap is no later than when the current GNSS positioning of the wireless terminal becomes invalid.

30. The wireless communication method according to any one of claims 23 to 29, wherein the configuration message enables: if the event occurs, performing the GNSS positioning after triggering a radio link failure (RLF).

31. The wireless communication method according to claim 30, wherein the event comprises at least one of the following: The current GNSS positioning of the wireless terminal is invalid or will become invalid, at least one evaluation period is less than the time for the wireless terminal to perform the GNSS positioning, wherein the wireless terminal evaluates the radio link quality during the evaluation period, At least one DRX cycle is less than or equal to the time for the wireless terminal to perform the GNSS positioning, The DRX inactivity time or the DRX cycle is shorter than the time for the wireless terminal to perform the GNSS positioning. The time for the wireless terminal to perform the GNSS positioning is greater than a threshold, The startup type of the GNSS positioning is warm start or cold start, The data buffer is not empty, There is subsequent data transmission, The quality of service (QoS) meets delay-sensitive requirements, or The interval between arriving data is less than the threshold.

32. The wireless communication method according to any one of claims 23 to 31, wherein the configuration message enables: if the event occurs, performing the GNSS positioning by leaving a connected mode or entering an idle mode.

33. The wireless communication method according to claim 32, wherein the event comprises at least one of the following: The current GNSS positioning of the wireless terminal is invalid or will become invalid, The data buffer is empty, The quality of service (QoS) meets the delay-insensitive requirements. The interval between arriving data is greater than the threshold, or There is no subsequent data transfer.

34. The wireless communication method according to any one of claims 23 to 33, wherein the configuration message comprises at least one of the following: a radio link control message or a system information block.

35. The wireless communication method according to any one of claims 24 to 34, further comprising: sending configuration information of the gap to the wireless terminal, or An indication or activation of a DRX cycle is sent to the wireless terminal, wherein the gap includes a DRX inactive time.

36. The wireless communication method according to claim 35, wherein the configuration information, the indication of the DRX cycle or the activation is included in a radio link control message, a system information block, a downlink control information, or a media access control element MAC CE.

37. A wireless communication method according to claim 35 or 36, wherein the configuration information of the gap includes at least one of the following: a start time, a duration, a time period, an indication that the gap is used for the GNSS positioning, or an activation indication that the gap is activated to be used for the GNSS positioning.

38. A wireless communication method according to any one of claims 35 to 37, wherein the indication or the activation of the DRX cycle includes at least one of the following: a start time, a duration, a time period, an on-duration, an indication that the DRX cycle is used for the GNSS positioning, or an identifier of the DRX cycle.

39. The wireless communication method according to any one of claims 23 to 38, further comprising: Assistance information associated with performing the GNSS positioning is received from the wireless terminal.

40. The wireless communication method according to claim 39, wherein the auxiliary information comprises at least one of the following: the time required by the wireless terminal to perform the GNSS positioning, The startup type of the GNSS positioning, the configuration of the gaps used to perform the GNSS positioning, at least one action performed if the current GNSS position of the wireless terminal is invalid, an indication of whether the wireless terminal supports performing the GNSS positioning in connected mode, an indication of whether the wireless terminal supports performing the GNSS positioning in the gap, or An indication of whether the wireless terminal supports performing neighbor cell measurements in connected mode.

41. The wireless communication method of claim 40, wherein the configuration of the gap comprises at least one of: an offset, a duration, or a start time before a current GNSS position of the wireless terminal is invalidated.

42. The wireless communication method according to claim 40 or 41, wherein the action comprises at least one of the following: triggering RLF or maintaining in the connected mode.

43. A wireless communication method for use in a wireless terminal, the method comprising: When in connected mode, neighbor cell measurements are triggered no later than the time when a serving cell stops serving the wireless terminal.

44. The wireless communication method according to claim 43, further comprising: An offset time or configuration of a start time of the neighbor cell measurements is received from a radio network node, wherein the neighbor cell measurements are performed at the offset time before the time at which the serving cell stops serving the wireless terminal.

45. The wireless communication method according to claim 43 or 44, wherein when in the connected mode, triggering the neighbor cell measurement no later than the time when the serving cell stops serving the wireless terminal comprises at least one of the following: If the change in the distance between the wireless terminal and the radio network node of the serving cell is greater than a first threshold, triggering the neighboring cell measurement, If the increment of the distance between the wireless terminal and the radio network node of the serving cell is greater than a second threshold, triggering the neighboring cell measurement, If the change in timing advance between the wireless terminal and the radio network node of the serving cell is greater than a third threshold, triggering the neighboring cell measurement, or If the increment of the timing advance between the wireless terminal and the radio network node of the serving cell is greater than a fourth threshold, the neighboring cell measurement is triggered.

46. ​​The wireless communication method according to any one of claims 43 to 45, wherein a neighboring cell is detected, and a measurement result of the detected neighboring cell is greater than a fifth threshold, and The method further comprises: Radio resource control reestablishment is initiated based on the neighbor cell measurements.

47. The wireless communication method according to claim 46, wherein a verification timer for a non-terrestrial network specific system information block is invalid and / or a current GNSS position of the wireless terminal becomes invalid.

48. The wireless communication method according to any one of claims 43 to 47, further comprising: receiving a request from a radio network node for assistance information associated with performing said neighbor cell measurements, and / or Assistance information associated with performing the neighbor cell measurement is sent to a radio network node.

49. The wireless communication method according to claim 48, wherein the assistance information indicates at least one of the following: The neighbor cell measurements cannot be completed before initiating the radio resource control reestablishment, The target cell cannot be determined before initiating RRC reestablishment. The measurement result of the neighbor cell measurement becomes invalid before initiating the radio resource control reestablishment, The gap between the completion time of the neighboring cell measurement and the initiation time of the radio resource control reestablishment is greater than a sixth threshold, or The synchronization indication is not received while the timer T310 is running.

50. A wireless communication method for use in a wireless network node, the method comprising: sending to a wireless terminal an offset time or a configuration of a start time of neighbor cell measurements performed by said wireless terminal in connected mode, Wherein, based on the configuration, the wireless terminal performs the neighbor cell measurement in the connected mode at the offset time before the time when the serving cell of the wireless terminal stops serving the wireless terminal.

51. The wireless communication method according to claim 50, further comprising: sending a request to the wireless terminal for assistance information associated with performing the neighbor cell measurements, and / or Assistance information associated with performing the neighbor cell measurements is received from the wireless terminal.

52. The wireless communication method according to claim 51, wherein the auxiliary information indicates at least one of the following: The neighbor cell measurements cannot be completed before initiating the radio resource control reestablishment, The target cell cannot be determined before initiating RRC reestablishment. The measurement result of the neighbor cell measurement becomes invalid before initiating the radio resource control reestablishment, The gap between the completion time of the neighboring cell measurement and the initiation time of the radio resource control reestablishment is greater than a sixth threshold, or The synchronization indication is not received while the timer T310 is running.

53. A wireless terminal, comprising: a communication unit, and The processor is configured to perform a Global Navigation Satellite System (GNSS) positioning if the event occurs.

54. The wireless terminal according to claim 53, wherein the processor is further configured to execute the wireless communication method according to any one of claims 2 to 22.

55. A wireless network node, comprising: The communication unit is configured to send a configuration message to the wireless terminal to enable execution of Global Navigation Satellite System (GNSS) positioning if an event occurs.

56. The radio network node according to claim 55, further comprising a processor configured to perform the wireless communication method according to any one of claims 24 to 42.

57. A wireless terminal, comprising: a communication unit, and The processor is configured to: when in connected mode, trigger neighbor cell measurement no later than the time when the serving cell stops serving the wireless terminal.

58. The wireless terminal according to claim 57, wherein the processor is further configured to perform the wireless communication method according to any one of claims 44 to 49.

59. A wireless network node, comprising: a communication unit configured to send to a wireless terminal an offset time or a configuration of a start time of a neighbor cell measurement performed by the wireless terminal in a connected mode, Wherein, based on the configuration, the wireless terminal performs the neighbor cell measurement in the connected mode at the offset time before the time when the serving cell of the wireless terminal stops serving the wireless terminal.

60. The radio network node according to claim 59, further comprising a processor, wherein the processor is configured to perform the wireless communication method according to claim 51 or 52.

61. A computer program product comprising computer readable program medium code stored thereon, which, when executed by a processor, causes the processor to implement the wireless communication method according to any one of claims 1 to 52.

Images