Methods and apparatus related to GNSS measurements

Abstract

Methods, apparatus, and computer readable media for global navigation satellite system (GNSS) measurements are disclosed. In an embodiment, a method for a user equipment (UE) is provided. The method includes transmitting an indication to a network node indicating that the UE requires GNSS measurements before a GNSS validity duration of the UE associated with a last successful GNSS measurement has expired. The indication is carried in at least one of a GNSS validity duration report, an uplink medium access control (MAC) control element (CE), a scheduling request, or a radio resource control (RRC) message.

Description

Technical Field

[0001] Embodiments of this disclosure generally relate to wireless communication technologies, and more particularly to methods and apparatus for triggering Global Navigation Satellite System (GNSS) measurements from a User Equipment (UE). Background Technology

[0002] User equipment (UE) can use GNSS to determine its location. This GNSS location information can be used to compensate for frequency offsets (caused by Doppler shift) and timing offsets in radio propagation between the UE and the satellite. For example, for geostationary orbit satellites (altitude approximately 36,000 km), the UE must compensate for propagation delay. For low Earth orbit satellites (altitude approximately 250 km - 1500 km), the UE must also compensate for Doppler shift and time shift due to satellite movement (approximately 28,000 km / h relative to Earth).

[0003] In technologies supporting the Internet of Things (IoT) over non-terrestrial networks (NTNs), it is assumed that the UE cannot simultaneously operate GNSS and the IoT NTN. In other words, the UE cannot communicate with the NTN system and simultaneously perform GNSS measurements. The UE needs to perform pre-compensation for uplink transmissions in terms of time and frequency adjustments. This pre-compensation is required when the NTN system operates on a low Earth orbit satellite moving at approximately 28,000 km / h relative to the Earth. This pre-compensation is based on the UE knowing the location of the target satellite (e.g., via satellite-aided information broadcast in SIB31 as defined in 3GPP TS 36.331) and its own location acquired via GNSS. By calculating the distance between the UE and the satellite and how the distance will change during transmission, the UE can determine when to transmit. Several challenges exist in this scenario. Summary of the Invention

[0004] The summary of this invention is provided to illustrate the simplified concepts of this disclosure. This summary is not intended to identify key or essential features of the claimed subject matter, nor is it intended to limit the scope of the claimed subject matter.

[0005] According to a first aspect of this disclosure, an apparatus for a user equipment (UE) is provided. The apparatus includes: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least: transmit an indication to a network node indicating that the UE requires GNSS measurements before the GNSS validity duration associated with the UE's last successful Global Navigation Satellite System (GNSS) measurement has expired. The indication is carried in at least one of: a GNSS validity duration report, an uplink media access control (MAC) control element (CE), a scheduling request, or a radio resource control (RRC) message.

[0006] According to some embodiments, the apparatus may also be configured to receive from a network node an indication of receipt, an acknowledgment of the indication, or a trigger command for a desired GNSS measurement.

[0007] According to some embodiments, the indication can be transmitted if the remaining time of the GNSS validity duration is longer than a pre-configured threshold.

[0008] According to some embodiments, the device may also be configured to move to an RRC idle state in the event of an indicated transmission failure.

[0009] According to some embodiments, the device can also be configured to move to an RRC idle state if a confirmation or trigger command for the required GNSS measurement is not received from the network node in response to an indication.

[0010] According to some embodiments, the device may also be configured to disable uplink transmissions after the indicated transmission until the required GNSS measurements are successfully performed.

[0011] According to some embodiments, the indication can be used to instruct the UE to request the network node to trigger the required GNSS measurements. The apparatus can also be configured to receive a trigger command from the network node to initiate the required GNSS measurements.

[0012] According to some embodiments, the instruction is used to instruct the UE to autonomously initiate the required GNSS measurements upon the indicated transmission. The device can also be configured to autonomously initiate the required GNSS measurements upon the indicated transmission.

[0013] According to some embodiments, the indication can be used to instruct the UE to autonomously begin the required GNSS measurements after an offset from the transmission of the indication. The device can also be configured to autonomously begin the required GNSS measurements after an offset from the transmission of the indication.

[0014] According to some embodiments, the indication can be used to instruct the UE to autonomously initiate the required GNSS measurements according to network pre-configuration at the time of the indicated transmission or after an offset from the time of the indicated transmission. The apparatus can also be configured to autonomously initiate the required GNSS measurements according to network pre-configuration at the time of the indicated transmission or after an offset from the time of the indicated transmission.

[0015] According to some embodiments, an indication may be carried in a GNSS validity duration report, and the indication may be one or more values ​​of validity duration in the GNSS validity duration information element of the GNSS validity duration report. The indication may be 0 or a negative value defined as validity duration. Alternatively, the indication may be a value of validity duration shorter than the remaining time of GNSS validity duration associated with the last successful GNSS measurement.

[0016] According to some embodiments, the indication may be a sign.

[0017] According to some embodiments, scheduling requests can be transmitted using a dedicated configuration from the network.

[0018] According to a second aspect of this disclosure, an apparatus for a network node is provided. The apparatus includes: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least: receive from the user equipment (UE) an indication that the UE requires GNSS measurements before the GNSS validity duration associated with the last successful Global Navigation Satellite System (GNSS) measurement has expired. The indication is carried in at least one of: a GNSS validity duration report, an uplink media access control (MAC) control element (CE), a scheduling request, or a radio resource control (RRC) message.

[0019] According to some embodiments, the apparatus may also be configured to transmit to the UE a receipt of an indication, an acknowledgment of an indication, or a trigger command for a required GNSS measurement.

[0020] According to some embodiments, the indication can be used to indicate one of the following: the UE requests the network node to trigger the required GNSS measurement, the UE autonomously starts the required GNSS measurement at the time of the indicated transmission, the UE autonomously starts the required GNSS measurement after an offset from the time of the indicated transmission, or the UE autonomously starts the required GNSS measurement according to network pre-configuration at the time of the indicated transmission or after an offset from the time of the indicated transmission.

[0021] According to some embodiments, an indication may be carried in the GNSS validity duration report, and the indication includes one or more values ​​of validity duration in the GNSS validity duration information element. The indication may be 0 or a negative value defined as validity duration. Alternatively, the indication may be a value of validity duration shorter than the remaining time of GNSS validity duration associated with the last successful GNSS measurement.

[0022] According to some embodiments, the indication may be a flag.

[0023] According to some embodiments, the apparatus can also be configured to: configure a special configuration for scheduling requests.

[0024] According to a third aspect of this disclosure, a method is provided to be performed at a user equipment (UE). The method includes transmitting an indication to a network node, prior to the expiration of the GNSS validity duration associated with the UE's last successful Global Navigation Satellite System (GNSS) measurement. The indication is carried in at least one of the following: a GNSS validity duration report, an uplink media access control (MAC) control element (CE), a scheduling request, or a radio resource control (RRC) message.

[0025] According to a fourth aspect of this disclosure, a method is provided to be performed at a network node. The method includes receiving from the user equipment (UE) an indication that the UE requires GNSS measurements before the GNSS validity duration associated with the last successful Global Navigation Satellite System (GNSS) measurement has expired. The indication is carried in at least one of the following: a GNSS validity duration report, an uplink media access control (MAC) control element (CE), a scheduling request, or a radio resource control (RRC) message.

[0026] According to a fifth aspect of this disclosure, a computer-readable storage medium is provided on which instructions are stored. When executed by at least one processor, the instructions cause the at least one processor to perform any method according to a third or fourth aspect.

[0027] According to a sixth aspect of this disclosure, a computer program product including instructions is provided, which, when executed by at least one processor, cause at least one processor to perform any method according to the third or fourth aspect.

[0028] According to a seventh aspect of this disclosure, an apparatus for a user equipment (UE) is provided, the apparatus comprising: a component for transmitting, to a network node, an indication indicating that the UE requires GNSS measurements before the GNSS validity duration associated with the last successful Global Navigation Satellite System (GNSS) measurement of the UE has expired. The indication is carried in at least one of the following: a GNSS validity duration report, an uplink media access control (MAC) control element (CE), a scheduling request, or a radio resource control (RRC) message.

[0029] According to an eighth aspect of this disclosure, an apparatus for a network node is provided, the apparatus comprising: a component for receiving from a user equipment (UE) an indication that the UE requires GNSS measurements before the GNSS validity duration associated with the last successful Global Navigation Satellite System (GNSS) measurement has expired. The indication is carried in at least one of the following: a GNSS validity duration report, an uplink media access control (MAC) control element (CE), a scheduling request, or a radio resource control (RRC) message.

[0030] It should be understood that the summary portion is not intended to identify key or essential features of the embodiments of this disclosure, nor is it intended to limit the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0031] Some exemplary embodiments will now be described with reference to the accompanying drawings, in which: Figure 1 An exemplary communication system architecture in which embodiments of the present disclosure may be implemented is shown; Figure 2 A timeline of an exemplary procedure for GNSS measurements according to embodiments of the present disclosure is shown; Figure 3 This is a flowchart depicting a method performed at a UE according to an embodiment of the present disclosure; Figure 4 This is a flowchart depicting a method performed at a network node according to an embodiment of the present disclosure; Figure 5 This is an exemplary signaling flow depicting an exemplary process according to an embodiment of this disclosure; Figure 6 This is an exemplary signaling flow depicting another exemplary process according to an embodiment of this disclosure; Figure 7 This is an exemplary signaling flow depicting yet another exemplary process according to embodiments of the present disclosure; and Figure 8 A simplified block diagram of an apparatus according to an embodiment of the present disclosure is shown. Detailed Implementation

[0032] Some exemplary embodiments will now be described in more detail below with reference to the accompanying drawings, which illustrate some, but not all, of the embodiments. In fact, exemplary embodiments may take many different forms and should not be construed as fixed to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will satisfy applicable legal requirements. The same reference numerals throughout refer to the same elements.

[0033] References to "an embodiment," "embodiment," "example embodiment," etc., in this disclosure indicate that the described embodiment may include a particular feature, structure, or characteristic, but not every embodiment needs to include that particular feature, structure, or characteristic. Furthermore, such phrases do not necessarily refer to the same embodiment. Moreover, when a particular feature, structure, or characteristic is described in connection with an example embodiment, whether explicitly described or not, it is believed that the influence of such feature, structure, or characteristic on other embodiments is within the knowledge of those skilled in the art.

[0034] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.

[0035] As used herein, the terms “data,” “content,” “information,” and similar terms are used interchangeably to refer to data that can be transmitted, received, and / or stored according to embodiments of the invention. Therefore, the use of any such terms should not be construed as limiting the spirit and scope of the embodiments of the invention.

[0036] As used in this application, the term "circuit system" may refer to one or more or all of the following: (a) Hardware circuit implementation only (such as implementation only in analog and / or digital circuit systems), and (b) A combination of hardware circuitry and software, such as (if applicable): (i) A combination of analog and / or digital hardware circuitry with software / firmware, and (ii) Any part of a hardware processor with software (including digital signal processors, software, and memory that work together to enable devices (such as mobile phones or servers) to perform various functions), and (c) Hardware circuitry and / or processors, such as microprocessors or parts thereof, that require software (e.g., firmware) to operate, but the software may not be present when operation is not required.

[0037] This definition of "circuit system" applies to all uses of the term in this application, including in any claim. As another example, as used in this application, the term "circuit system" also covers implementations of hardware circuitry or processors (or processors) or portions thereof and their accompanying software and / or firmware. The term "circuit system" also covers, for example and if applicable to a particular claim element, baseband integrated circuits or processor integrated circuits used in mobile devices or servers, cellular network devices, or other computing or networking devices.

[0038] As defined herein, a “computer-readable storage medium” referring to a non-transitory physical storage medium (e.g., a volatile or non-volatile memory device) can be distinguished from a “computer-readable transmission medium” referring to an electromagnetic signal. Such media can take many forms, including but not limited to non-transitory computer-readable storage media (e.g., non-volatile media, volatile media) and transmission media. Transmission media include, for example, coaxial cables, copper wires, fiber optic cables, and carrier waves that travel through space without wires or cables, such as sound waves and electromagnetic waves, including radio waves, light waves, and infrared waves. Signals include artificial transient changes in amplitude, frequency, phase, polarization, or other physical properties transmitted through the transmission medium. Examples of non-transitory computer-readable media include magnetic computer-readable media (e.g., floppy disks, hard disks, magnetic tapes, any other magnetic media), optical computer-readable media (e.g., optical disc read-only memory (CD-ROM), digital versatile optical disc (DVD), Blu-ray disc, etc.), random access memory (RAM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), flash memory-EPROM, or any other non-transitory media that a computer can read. The term computer-readable storage medium is used herein to refer to any computer-readable medium other than a transmission medium. However, it should be understood that while embodiments are described using computer-readable storage media, in alternative embodiments, other types of computer-readable media may be used instead of computer-readable storage media.

[0039] In the following text, the non-limiting term User Equipment (UE) means any wireless device that communicates with a network node and / or another UE in a cellular or mobile communication system. A UE may include any suitable device capable of performing at least GNSS cellular and satellite communications. For example, a UE may be a data processing device equipped with a wireless transceiver for transmitting and receiving cellular communication signals, a GNSS receiver for receiving satellite position signals, data processing, and a user interface. Non-limiting examples of UEs include IoT devices, enhanced machine-type communication (eMTC) devices, vehicular wireless terminal equipment, mobile terminals (MT), wearable wireless devices, mobile phones or so-called "smartphones," portable computers, personal data assistants (PDAs), or any combination thereof.

[0040] In the following text, the non-limiting term "network node" refers to any node that is part of a radio access network (e.g., radio access node or equivalent term). A network node may communicate directly or indirectly with the UE and / or with other network nodes in the cellular communication network to enable and / or provide radio access to the UE, and / or perform other functions (e.g., management) in the cellular communication network. Non-limiting examples of network nodes include base stations (BS), NodeBs, eNodeBs (eNBs), gNodeBs (gNBs), access points, etc.

[0041] The embodiments of this disclosure can be implemented in non-terrestrial network (NTN) systems. Typical NTNs include transparent payload-based NTNs (also known as transparent payload NTNs) and regenerative payload-based NTNs (also known as regenerative payload NTNs). Figure 1 A system 100A for transparent payload NTN is shown. (Example) Figure 1 As shown in the upper part, system 100A includes user equipment (UE) 101, eNB 102, core network 103, satellite 104, and NTN gateway 105. The transparent payload NTN can be considered a relay node on the network side, altering the frequency carriers of the uplink and downlink RF signals and filtering and amplifying them before downlink transmission, while maintaining the waveform of the loaded signal. The satellite acts as an RF repeater. Satellite 104 relays the LTE-Uu radio interface from the feed link (between NTN gateway 105 and satellite 104) to the serving link (between satellite 104 and UE 104), and vice versa. Different transparent satellites can connect to the same eNB 102 on the ground.

[0042] Figure 1The lower part shows a system 100B for regenerating the NTN payload. System 100B includes a user equipment (UE) 101, an eNB 102, a core network 103, a satellite 104, and an NTN gateway 105. The satellite 104 hosts the eNB 102 and therefore acts as a base station, either entirely or partially.

[0043] As described above, it is assumed that the UE cannot simultaneously operate NTN communication and GNSS. When the UE must perform GNSS measurements, it will move to the RRC idle state. The network is aware of this requirement based on the UE reporting the remaining GNSS validity duration via the GNSS-ValidityDuration RRC information element, as defined in 3GPP TS36.331. -GNSS-ValidityDuration IE GNSS-ValidityDuration Indicates the remaining duration of GNSS availability in the UE. A value of s10 corresponds to 10 seconds, s20 to 20 seconds, and so on. A value of min5 corresponds to 5 minutes, min10 to 10 minutes, and so on.

[0044] GNSS-ValidityDuration information element - - ASN1START GNSS-ValidityDuration-r17:: Enumeration { s10, s20, s30, s40, s50, s60, min5, min10, min15, min20, min25, min30, min50, min90, min120, infinity} -- ASN1STOP However, if the UE has a long connection time and is not stationary, this means the UE may need to move to the RRC idle state to measure GNSS multiple times. Moving to the RRC idle state will incur more overhead in terms of connection establishment signaling. Therefore, standardization work on IoT support for NTN (such as the 3GPP working group) aims to: improve GNSS operation during long connection times for new location fixation with UE pre-compensation, and reduce power consumption. Furthermore, simultaneous GNSS and NTN narrowband (NB)-IoT / eMTC operation is not assumed.

[0045] According to the protocols in the standardization work, a base station (e.g., an eNB) can trigger the UE to perform GNSS measurements (which may be referred to as network-triggered GNSS measurements). For example, when the current GNSS validity duration is about to expire, and if the UE does not receive such a trigger from the eNB, the UE can autonomously trigger GNSS measurements (which may be referred to as autonomous GNSS measurements). Furthermore, after completing GNSS location-fixed measurements, the UE provides the remaining GNSS validity duration in the uplink MAC CE.

[0046] Specifically, a base station (such as an eNB) can periodically trigger GNSS measurement gaps (MGs) for UEs in which they can perform GNSS measurements. During a GNSS MG, the UE cannot monitor the Physical Downlink Control Channel (PDCCH) and perform other cellular communications. This triggering is based on a Downlink Medium Access Control (MAC) control element (CE). At this point, a new downlink MAC CE can be introduced to trigger UEs in Radio Resource Control (RRC) connected states to perform GNSS measurements. The base station (or other network node) is free to decide when to trigger GNSS measurements or GNSS measurement gaps. When a base station or network node triggers GNSS measurements is determined by the network implementation.

[0047] For GNSS measurement gaps triggered aperiodically using MAC CE, the duration of the GNSS measurement gap can be configured by the base station (such as an eNB). When the duration of the GNSS measurement gap is not included in the eNB's configuration, the duration of the GNSS measurement gap can be equal to the duration of the GNSS measurement associated with the most recently reported GNSS location.

[0048] The UE can report the GNSS location-fixed duration for measurements, at least during the initial access phase. The location-fixed duration defines the time the UE expects to require to perform GNSS measurements. Therefore, the eNB can use it to estimate the length of the GNSS MG. Essentially, the MG should be equal to or longer than the location-fixed duration to allow the UE to perform and complete GNSS measurements. Therefore, the eNB can configure a corresponding GNSS MG duration for the UE based on the GNSS location-fixed duration reported by the UE.

[0049] For GNSS measurements in RRC-connected state, if the eNB non-periodically triggers the UE in RRC-connected state to perform GNSS measurements, the UE can reacquire the GNSS location fixed within the gap. The UE is not required to transmit or receive any channels / signals during the duration of the non-periodic GNSS measurement gap until it successfully reacquires GNSS data (through GNSS measurements).

[0050] Autonomous GNSS measurement or reacquisition mechanisms can be enabled or disabled by the network. According to the protocol, if the UE does not receive a trigger for GNSS measurement from the network (such as an eNB or other network node), the UE can autonomously (when configured / enabled by the network) reacquire GNSS. For NB-IoT and eMTC, at least for cases where the network configuration does not include periodicity (if supported), for autonomous GNSS measurement or reacquisition, the UE can autonomously reacquire GNSS during a GNSS measurement timer, the start time of which is based on the original GNSS validity duration. Autonomous GNSS measurement or reacquisition can be periodic under certain conditions.

[0051] The UE can trigger a GNSS measurement report each time it completes a GNSS fixing operation. In RRC connected mode, the UE can utilize the MAC CE to report the GNSS validity duration. Besides the NB-IoT control plane solution, the uplink MAC CE for GNSS validity duration reporting can also be used in NB-IoT user plane solutions and eMTC UEs. The reported GNSS validity duration is the remaining validity duration of the GNSS validity period. This allows the UE and eNB to have a shared understanding of the UE's GNSS state, i.e., when it is valid and when it is obsolete.

[0052] According to the agreement, at least for cases where the frequency and timing errors are within the frequency and timing error requirements with conventional closed-loop time correction, uplink transmission can be permitted for a period after the original GNSS validity period expires without requiring GNSS reacquisition.

[0053] In summary, two methods for triggering GNSS measurements are currently defined: 1. The network (such as a base station) periodically triggers the UE to perform GNSS measurements (this may also be referred to as network-triggered GNSS measurements). The network may trigger GNSS measurements based on the UE's previously reported remaining GNSS validity duration. As discussed above, the current UE will trigger such a report on the remaining GNSS validity duration upon completion of GNSS fixing operations. There is no discussion of the UE providing an updated validity duration "prematurely". Alternatively, the network may trigger GNSS measurements based on some internal network means (e.g., after detecting uplink transmission misalignment of the UE).

[0054] 2. The UE autonomously triggers GNSS measurements (also known as autonomous GNSS measurements), as discussed above in the section on autonomous GNSS reacquisition mechanisms. The start time of autonomous GNSS measurements is based on the original GNSS validity duration reported to the network. Therefore, the UE cannot start autonomous measurements at any time based solely on the previously reported GNSS validity duration. In other words, the UE can start autonomous measurements when the last successful GNSS measurement expires. This is to ensure the network knows when the UE is performing GNSS measurements.

[0055] Currently, there is no mechanism for a UE to trigger GNSS measurements whenever it detects a need for such measurements. For example, a UE could detect that its current GNSS position is fixed or has become invalid based on downlink measurements. For instance, a UE could compare the expected time / frequency of a downlink signal with the actual time / frequency of the received downlink signal based on a previously determined position. If the difference between the expected downlink signal and the measured downlink signal exceeds a threshold, the UE can detect a need for new GNSS measurements. One approach is to use the Physical Random Access Channel (PRACH) to request a trigger command from the eNB for new GNSS measurements. However, using PRACH to request a trigger command would require dedicated resources for that specific PRACH to be interpreted by the network as a request for new GNSS measurements. This results in PRACH resource fragmentation, which is undesirable.

[0056] Figure 2 A timeline of an exemplary GNSS measurement process in this scenario is shown. In this exemplary process, when the UE detects the need for a new GNSS measurement, the current remaining GNSS validity duration associated with the last successful GNSS MG remains valid. In the last GNSS MG, as shown in 210, the UE has performed a GNSS measurement to successfully reacquire the GNSS position fix. The UE can report the GNSS validity duration of the reacquired GNSS position fix to the eNB, as shown at 220. The reported GNSS validity duration indicates the expected duration for which the reacquired GNSS position fix is ​​valid. Note that the reported GNSS validity duration is the duration referenced to the time when the GNSS validity duration was reported (as shown in 202). At this point, it is the remaining validity duration of the UE's current GNSS position fix, i.e., the position fix obtained in step 210.

[0057] As time progresses and the remaining time of the current validity period becomes as shown in 204 and far from its expiration, the UE can detect that its fixed position obtained in step 210 is invalid or has become invalid (e.g., due to unexpected movement), thus requiring new GNSS measurements. For example, the UE can determine that a change in the UE's mobility state requires new GNSS measurements based on the time / frequency difference between the received downlink signal and an estimate based on the UE's last known position. The requirement for new GNSS measurements can be further determined by using external components such as accelerometers / gyroscopes.

[0058] According to the solution proposed in this disclosure, before the GNSS validity duration associated with the last successful GNSS MG has expired, the UE is allowed to transmit an indication indicating the UE's request for a new GNSS measurement, as shown in 230. Then, based on this indication, the UE can perform a new GNSS measurement before the GNSS validity duration associated with the last successful GNSS MG has expired, as shown in 240. The new GNSS measurement can be a network-triggered GNSS measurement or an autonomous GNSS measurement.

[0059] According to some embodiments, the trigger may be or be included in the GNSS validity duration report. As mentioned above, conventionally, the UE transmits a GNSS validity duration report (e.g., as defined in 3GPP TS36.331) upon completion of GNSS location fixing (i.e., after or at the end of GNSS measurements). Except after the completion of GNSS measurements, the current protocol does not define that the UE can transmit a new remaining GNSS validity duration. Embodiments of this disclosure enable the UE to reuse the GNSS validity duration report to indicate the need for new GNSS measurements. It is suggested that the UE can transmit a new (remaining) GNSS validity duration report at any time and not only after or at the end of GNSS measurements.

[0060] The new (remaining) GNSS validity duration report can include a newly defined value for the GNSS validity duration to indicate that the UE requires GNSS measurements. For example, the UE can transmit, for instance, in... GNSS-ValidityDurationThe "0 s" or "-1 s" or another specified value in the information element serves as the GNSS validity duration. In the example, "0 s" could be defined as indicating that the UE will wait for a GNSS measurement gap to be triggered from a network node (such as a base station); "-1 s" could be defined as indicating that the UE will immediately begin autonomous GNSS measurements upon the transmission of the GNSS validity duration report. In another example, considering the report transmission time between the UE and the network, or after receiving network confirmation of the GNSS validity duration report, "-1 s" could be defined as indicating that the UE will begin autonomous GNSS measurements after an offset (e.g., UE-eNB round-trip time (RTT)). In yet another embodiment, a new value could be defined as indicating that the UE will begin autonomous GNSS measurements or wait for a trigger, depending on what the network is configured with, such as some pre-configuration from network nodes (such as eNBs).

[0061] In this implementation, which differs from traditional GNSS validity duration reporting, the UE is not allowed to perform any further uplink transmissions after a new GNSS validity duration has been transmitted, until the UE has successfully performed the required new GNSS measurements. This is because the UE may consider itself out of sync when or after the transmission of a new GNSS validity duration.

[0062] In an embodiment, the new GNSS validity duration report may include a new estimated remaining GNSS validity duration, which is shorter than the remaining time of the previously reported validity duration. Figure 2 The exemplary procedure for GNSS measurement shown illustrates the remaining time of the previously reported validity duration at the current remaining GNSS validity duration 204. This remaining validity duration can be determined equally on both the UE and network sides based on the reported GNSS validity duration 202, for example, by using a timer to account for the elapsed time. The newly estimated remaining GNSS validity duration reported at 230 may be shorter than the current remaining GNSS validity duration. This shorter remaining GNSS validity duration will notify the network that GNSS measurements are needed, but not necessarily that the measurements are urgent.

[0063] In an embodiment, the new GNSS validity duration report may include a newly defined flag to indicate that the UE requires GNSS measurements. This flag may indicate that the UE will perform any of the following actions: i) wait for a GNSS measurement gap to be triggered from the network node; ii) immediately begin autonomous GNSS measurements; iii) begin autonomous GNSS measurements after an offset; iv) begin autonomous GNSS measurements or wait for a trigger, depending on what is configured by the network node.

[0064] Alternatively, in some embodiments, a new uplink MAC CE can be defined to indicate that new GNSS measurements are required before the GNSS validity duration associated with the last successful GNSS MG expires. According to embodiments, the MAC CE can be a 1-bit indicator used to convey "true" or "false," indicating whether the UE needs or does not need GNSS measurements. According to embodiments, the MAC CE can also instruct the UE to do any of the following: wait for a GNSS measurement gap trigger from the network node; immediately begin autonomous GNSS measurements; begin autonomous GNSS measurements after an offset; or, depending on what is configured by the network node, begin autonomous GNSS measurements or wait for a trigger.

[0065] Alternatively, in some embodiments, the UE may trigger a new GNSS measurement via a scheduling request (SR) configured with a dedicated SR or via a newly defined RRC message. The scheduling request or RRC message may instruct the UE that a new GNSS measurement is required before the GNSS validity duration associated with the last successful GNSS MG expires. For example, the scheduling request or RRC message may instruct the UE to do any of the following: wait for a GNSS measurement gap to be triggered from the network node; immediately begin autonomous GNSS measurement; begin autonomous GNSS measurement after an offset; or begin autonomous GNSS measurement or wait for a trigger, depending on what is configured by the network node.

[0066] The solutions disclosed herein can be applied to UEs (or wireless devices) and network nodes in NTN environments involving GNSS, or any other positioning procedures and systems, such as 3GPP-based positioning procedures and systems (which, for brevity, are generally referred to as GNSS in this disclosure). References will be made below. Figures 3 to 8 The solution disclosed herein is described in detail.

[0067] Figure 3 This is a flowchart depicting a method performed at a UE according to embodiments of the present disclosure. At block 310, before the GNSS validity duration associated with the UE's last successful GNSS measurement has expired, the UE transmits an indication to a network node (such as an eNB) indicating that the UE needs to perform a GNSS measurement. The UE transmits the indication without performing a current GNSS measurement. In other words, the indication is not transmitted in response to a successful or failed GNSS measurement. According to embodiments of the present disclosure, the indication is carried in at least one of the following: a GNSS validity duration report, an uplink MAC CE, an SR, or an RRC message.

[0068] GNSS Effective Duration Report (SAD) and Uplink MAC CE can be transmitted using uplink transmission resources allocated to the UE. The Uplink MAC CE can be a dedicated MAC CE. A dedicated SR configuration from the network can be used to transmit the SR, allowing network nodes to recognize that the SR includes the indication. The RRC message can be a newly defined RRC message. In one embodiment, the UE can choose which of the following—GNSS Effective Duration Report, Uplink MAC CE, SR, or RRC message—to transmit the indication. In another embodiment, the network (e.g., network nodes) pre-configures or predefines (e.g., in a protocol or specification) which will be used to transmit the indication. The transmission of the indication enables both the UE side (e.g., the UE) and the network side (e.g., network nodes) to have a common understanding of when and how the UE performs the required GNSS measurements.

[0069] although Figure 3 Although not shown in the diagram, in an embodiment, the method further includes determining that GNSS measurements are required. For example, the indication may be transmitted in response to detecting that the UE's GNSS location fix is ​​becoming invalid, and thereby it can determine that GNSS measurements are required to reacquire a new GNSS location fix.

[0070] Despite Figure 3 Not shown, but in an embodiment, the method further includes receiving from a network node a receipt of an indication, an acknowledgment of the indication, or a trigger command for a desired GNSS measurement. The receipt of the indication, the acknowledgment of the indication, and the trigger command are received in response to the transmission of the indication.

[0071] In this embodiment, the indication is transmitted if the remaining time of the GNSS validity duration is longer than a pre-configured threshold. For example, the pre-configured threshold may be pre-configured by the network node. In this example, the UE can determine whether the remaining time of the GNSS validity duration is longer than the pre-configured threshold, and trigger the transmission of the indication if it is determined that the remaining time of the GNSS validity duration is longer than the pre-configured threshold. This is to prevent the UE from transmitting the indication near a time when the network (e.g., a network node) will inevitably trigger a new GNSS measurement or a time when the UE can trigger an autonomous measurement.

[0072] In an embodiment, in the event of an indicated transmission failure, the UE moves to an RRC idle state. For example, if the indicated transmission fails within a number of network-configured attempts (e.g., 2 or 3) via any of the GNSS validity duration report, SR, uplink MAC CE, or RRC message, the UE considers itself to be outside of uplink synchronization. The UE then moves to an RRC idle state.

[0073] In this embodiment, if a confirmation or trigger command for a required GNSS measurement is not received from the network node in response to an indication, the UE moves to the RRC idle state. In this respect, if the UE requests the network node to trigger a required GNSS measurement or confirm the MG for a required autonomous GNSS measurement, but fails to receive a new GNSS measurement trigger command or any confirmation from the network node within a network-configured timer, the UE considers itself to be outside uplink synchronization. The UE then moves to the RRC idle state.

[0074] In this embodiment, after the indicated transmission, the UE is prohibited from performing uplink transmissions until the required GNSS measurements are successfully performed.

[0075] In an embodiment, the instruction may also indicate further details regarding the required GNSS measurement, such as the following four different methods for performing the required GNSS measurement. In the example, the instruction is used to instruct the UE to request the network node to trigger the required GNSS measurement. The method may then further include receiving a trigger command from the network node to initiate the required GNSS measurement.

[0076] In another example, the instruction is used to instruct the UE to autonomously initiate the required GNSS measurements upon the indicated transmission. The method may then further include autonomously initiating the required GNSS measurements upon the indicated transmission.

[0077] In yet another example, the indication is used to instruct the UE to autonomously begin the required GNSS measurements after an offset from the indicated transmission. The method may then further include autonomously initiating the required GNSS measurements after an offset from the indicated transmission.

[0078] In yet another example, the indication is used to instruct the UE to autonomously initiate the required GNSS measurements according to network pre-configuration at the time of the indicated transmission or after an offset from the time of the indicated transmission. The method may then further include autonomously initiating the required GNSS measurements according to network pre-configuration at the time of the indicated transmission or after an offset from the time of the indicated transmission.

[0079] In one embodiment, the UE can select or set different values ​​for the indication to indicate any of the different methods described above for performing the required GNSS measurements. In another embodiment, by default, only one of the different methods described above is indicated for performing the required GNSS measurements.

[0080] In some embodiments, an indication is carried in the GNSS validity duration report. The indication includes one or more values ​​of the validity duration in the GNSS-ValidationDuration information element of the GNSS validity duration report. For example, the indication is 0 or a negative value (such as -1), which is defined as a value of the validity duration. These specified values ​​are significantly different from other normal values ​​of the validity duration and will then be easily identified by the receiver as a trigger for a GNSS measurement, rather than a normal GNSS validity duration report. In another example, the indication is a value of the validity duration that is shorter than the remaining duration of the GNSS validity duration associated with the last successful GNSS measurement. In this regard, the UE may, for example, determine the remaining duration of the GNSS validity duration associated with the last successful GNSS measurement based on a timer, and then set the validity duration in the GNSS validity duration report to a value much shorter than the determined remaining duration.

[0081] In some embodiments, the indication includes a flag in the GNSS validity duration report. For example, the UE may set a flag to indicate that the UE needs GNDSS measurements, and may also select a corresponding value for the flag to indicate any of the different methods described above for performing the required GNSS measurements.

[0082] Figure 4 This is a flowchart depicting an exemplary method performed at a network node such as an eNB according to embodiments of the present disclosure. At block 410, before the GNSS validity duration associated with the UE's last successful GNSS measurement has expired, an indication is received from the UE indicating that the UE needs to perform GNSS measurements. The indication is carried in at least one of the following: a GNSS validity duration report, an uplink MAC CE, an SR, or an RRC message. Based on this indication, the network node can have a common understanding of when and how the UE performs the required GNSS measurements.

[0083] In this embodiment, the indication is carried within the GNSS validity duration report. Because the GNSS validity duration report is not transmitted in response to a successful or failed current GNSS measurement, network nodes can identify that the GNSS validity duration report is used to indicate a required GNSS measurement, rather than a normal GNSS validity duration report. The uplink MAC CE can be a dedicated MAC CE. The RRC message can be a newly defined RRC message.

[0084] Despite Figure 4 Although not shown in the figure, in an embodiment, the method also includes a dedicated configuration for the SR configuration, so that the SR can be transmitted by the UE using the dedicated SR configuration.

[0085] although Figure 4 Not shown, but in embodiments, the method further includes receiving an indication, acknowledging an indication, or triggering a command for a desired GNSS measurement.

[0086] Figure 5 This is an exemplary signaling flow 500 depicting an exemplary process according to embodiments of this disclosure. (e.g.) Figure 5 As shown, at step 510, upon successfully performing a GNSS measurement, UE 501 transmits a GNSS validity duration report to network node 502 (such as an eNB). The GNSS validity duration report includes the GNSS validity duration associated with the successful GNSS measurement.

[0087] At step 520, during the GNSS validity duration reported in step 510, UE 501 transmits a new GNSS validity duration report to network node 502. The new GNSS validity duration report may include a new GNSS validity duration or flag to indicate that the UE requires GNSS measurements, as described above. In this example, the new GNSS validity duration or flag indicates that the UE will wait for a GNSS measurement trigger command from the network node.

[0088] In response to receiving a new GNSS validity duration report, network node 502 may transmit a GNSS measurement trigger command to UE 501 to trigger a GNSS MG, as shown in step 530. UE 501 may then perform GNSS measurements in the triggered GNSS MG, as shown in step 540.

[0089] Figure 6 This is an exemplary signaling flow 600 depicting an exemplary process according to embodiments of the present disclosure. Figure 6 As shown, at step 610, upon successfully performing a GNSS measurement, UE 601 transmits a GNSS validity duration report to network node 602 (such as an eNB). The GNSS validity duration report includes the GNSS validity duration associated with the successful GNSS measurement.

[0090] At step 620, during the GNSS validity duration reported in step 610, UE 601 transmits a new GNSS validity duration report to network node 602. The new GNSS validity duration report may include a new GNSS validity duration or flag to indicate that the UE requires GNSS measurements, as described above. In this example, the new GNSS validity duration or flag indicates that UE 601 will begin autonomous GNSS measurements upon the transmission of the new GNSS validity duration report.

[0091] Then, at step 630, after transmitting a new GNSS validity duration report, UE 601 can perform autonomous GNSS measurements.

[0092] Figure 7 This is an exemplary signaling flow 700 depicting an exemplary process according to embodiments of this disclosure. Figure 7 As shown, at step 710, upon successfully performing a GNSS measurement, UE 701 transmits a GNSS validity duration report to network node 702 (such as an eNB). The GNSS validity duration report includes the GNSS validity duration associated with the successful GNSS measurement.

[0093] At step 720, during the GNSS validity duration reported in step 710, UE 701 attempts to transmit a new GNSS validity duration report to network node 702. The new GNSS validity duration report may include a new GNSS validity duration or a flag indicating that the UE requires GNSS measurements, as described above. In this example, UE 701 requires feedback from network node 702, such as acknowledgment, confirmation, or a trigger command for GNSS measurements. However, UE 701 does not receive feedback in response to the new GNSS validity duration report, as indicated by the X mark at step 720. Network node 702 may not receive the new GNSS validity duration report, or network node 702 may not provide feedback, or the provided feedback may be lost during transmission to UE 701.

[0094] UE 701 may attempt to transmit new GNSS validity duration reports multiple times, as shown in step 730.

[0095] If UE 701 does not receive the expected feedback from network node 702 after the number of attempts to preconfigure or within the preconfigured duration (e.g., due to the first report in step 720), UE 701 can move to the RRC idle state. In this regard, a network-configured timer can be set to wait for the expected feedback.

[0096] The embodiments of this disclosure address the problem of how a UE notifies a network node to update the previously reported GNSS validity duration, for example, due to a change in the UE's mobility state. Through these embodiments, a shared understanding between the UE and the network node regarding measurement gaps for new GNSS measurements can be achieved.

[0097] Furthermore, some embodiments of this disclosure reuse GNSS validity duration reports to indicate the need for GNSS measurements before the GNSS validity duration associated with the last successful GNSS measurement has expired. This reduces the impact of embodiments of this disclosure on existing mechanisms for GNSS measurements. Simultaneously, reusing GNSS validity duration reports is signaling efficient and will allow the UE to react to whether GNSS measurements are urgent.

[0098] Now for reference Figure 8 ,Should Figure 8 A simplified block diagram of an apparatus 800 that can be embodied in / as a UE or network node (such as an eNB) is shown. Apparatus 800 may include at least one processor 801, such as a data processor (DP); and at least one memory 802 coupled to at least one processor 801. Apparatus 800 may also include one or more transmitters TX, one or more receivers RX 803, or one or more transceivers coupled to one or more processors 801 for wireless communication and / or wired communication. For example, transmitters TX / RX 803 may include radio transceivers for transmitting and receiving cellular communication signals, and GNSS receivers for receiving satellite position signals.

[0099] Although not shown, device 800 may have at least one communication interface, for example, the communication interface may be as follows: Figure 8 At least one antenna or transceiver is shown. The communication interface can represent any interface necessary for communication with other UEs and / or network nodes.

[0100] The processor 801 can be any type suitable for the local technical environment, and by way of non-limiting example, it can include one or more of the following: general-purpose computer, special-purpose computer, microprocessor, digital signal processor (DSP), and processor based on a multi-core processor architecture.

[0101] As a non-limiting example, memory 802 can be of any type suitable for the local technical environment and can be implemented using any suitable data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory.

[0102] Memory 802 stores program 804. Program 804 may include instructions that, when executed on an associated processor 801, enable device 800 to operate according to embodiments of the present disclosure. A combination of at least one processor 701 and at least one memory 802 may form a processing circuitry system or component 805 suitable for implementing various embodiments of the present disclosure.

[0103] Various embodiments of this disclosure may be implemented by computer programs, software, firmware, hardware, or combinations thereof that can be executed by one or more of processors 801.

[0104] Generally, various exemplary embodiments can be implemented in hardware or dedicated circuitry, software, logic, modules, components, or any combination thereof. For example, some aspects may be implemented in hardware, while others may be implemented in firmware or software executable by a controller, microprocessor, or other computing device, but the invention is not limited thereto. While various aspects of the exemplary embodiments of this disclosure may be shown and described as block diagrams, flowcharts, or using some other graphical representation, it should be understood that these blocks, apparatuses, systems, techniques, or methods described herein may be implemented in components, modules, hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers or other computing devices, or some combination thereof, as non-limiting examples.

[0105] Therefore, it should be understood that at least some aspects of the exemplary embodiments of this disclosure can be practiced in various components such as integrated circuit chips and modules. Therefore, it should be understood that the exemplary embodiments of this disclosure can be implemented in devices embodied as integrated circuits, wherein the integrated circuits may include circuit systems (and possible firmware) embodying at least one or more of a data processor, digital signal processor, baseband circuit system, and radio frequency circuit system configurable to operate according to the exemplary embodiments of this disclosure.

[0106] It should be understood that at least some aspects of the exemplary embodiments of this disclosure may be embodied in computer-executable instructions, which are executed by one or more computers or other devices, such as in one or more program modules. Typically, program modules include routines, programs, objects, components, data structures, etc., which perform a specific task or implement a specific abstract data type when executed by a processor in a computer or other device. The computer-executable instructions may be stored on a computer-readable medium, such as a non-transitory computer-readable medium, such as a hard disk, optical disk, removable storage medium, solid-state memory, RAM, etc. As those skilled in the art will understand, the functionality of a program module can be combined or distributed as needed in various embodiments. Furthermore, this functionality may be wholly or partially embodied in firmware or hardware equivalents, such as integrated circuits, field-programmable gate arrays (FPGAs), etc.

[0107] Furthermore, although the operations are described in a specific order, this should not be construed as requiring that such operations be performed in the specific order shown or sequentially, or requiring that all the operations shown be performed to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, while several specific implementation details are included in the above discussion, these should not be construed as limiting the scope of this disclosure, but rather as a description of features that may be specific to particular embodiments. Certain features described in the context of different embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments.

[0108] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the exemplary embodiments. As used herein, the singular forms “a,” “an,” and “the” are also intended to include the plural forms unless the context clearly indicates otherwise. It will be further understood that the terms “comprising,” “including,” “having,” “having,” “containing,” and / or “comprising” as used herein specify the presence of the stated features, elements, and / or components, etc., but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof. As used herein, the term “and / or” includes any and all combinations of one or more of the listed terms.

[0109] As used herein, the phrase “at least one of A and B” or “at least one of A or B” should be understood as meaning “only A, only B, or both A and B”. The phrase “A and / or B” should be understood as meaning “only A, only B, or both A and B”.

[0110] This disclosure includes any novel features or combinations of features expressly disclosed herein, or any generalization thereof. Various modifications and variations to the foregoing exemplary embodiments of this disclosure will become apparent to those skilled in the art when read in conjunction with the accompanying drawings, in light of the foregoing description. However, any and all modifications will still fall within the scope of the non-limiting and exemplary embodiments of this disclosure.

Claims

1. An apparatus for a user equipment (UE), the apparatus comprising: At least one processor; as well as At least one memory stores instructions that, when executed by the at least one processor, cause the device to at least: Before the GNSS validity period associated with the UE's last successful Global Navigation Satellite System (GNSS) measurement expires, an indication indicating that the UE requires GNSS measurements is transmitted to the network node. The indicated instruction is carried in at least one of the following: GNSS Effectiveness Duration Report Uplink Media Access Control (MAC) control element (CE). Scheduling request, or Radio Resource Control (RRC) message.

2. The apparatus of claim 1, wherein the apparatus is further configured such that, Receive from the network node the receipt of the indication, or confirmation, or the trigger command for the required GNSS measurement.

3. The apparatus of claim 1 or 2, wherein the indication is transmitted if the remaining time of the GNSS validity duration is longer than a pre-configured threshold.

4. The apparatus according to any one of claims 1 to 3, wherein the apparatus is further configured such that, In the event of the transmission failure indicated, the system moves to the RRC idle state.

5. The apparatus according to any one of claims 1 to 4, wherein the apparatus is further configured such that, If the network node does not receive a confirmation or trigger command for the required GNSS measurement in response to the instruction, it moves to the RRC idle state.

6. The apparatus according to any one of claims 1 to 5, wherein the apparatus is further configured to: Following the transmission indicated, uplink transmissions are prohibited until the required GNSS measurements are successfully performed.

7. The apparatus according to any one of claims 1 to 6, wherein the indication is used to instruct the UE to request the network node to trigger the required GNSS measurement.

8. The apparatus of claim 7, wherein the apparatus is further configured to: Receive a trigger command from the network node to initiate the required GNSS measurements.

9. The apparatus according to any one of claims 1 to 6, wherein the indication is used to instruct the UE to autonomously begin the required GNSS measurement upon transmission of the indication; and Furthermore, the device is also configured to autonomously initiate the required GNSS measurements upon the indicated transmission.

10. The apparatus according to any one of claims 1 to 6, wherein the indication is used to instruct the UE to autonomously begin the required GNSS measurement after an offset from the transmission start of the indication; Furthermore, the device is also configured to autonomously initiate the required GNSS measurement after an offset from the indicated transmission start point.

11. The apparatus according to any one of claims 1 to 6, wherein the indication is used to instruct the UE to autonomously begin the required GNSS measurement according to network pre-configuration at the time of the transmission indicated or after an offset from the transmission indicated; Furthermore, the device is also configured to autonomously initiate the required GNSS measurements according to the network pre-configuration at the time of the indicated transmission or after an offset from the indicated transmission.

12. The apparatus according to any one of claims 1 to 11, wherein the indication is carried in a GNSS validity duration report, and the indication includes one or more values ​​of validity duration in the GNSS validity duration information element of the GNSS validity duration report.

13. The apparatus of claim 12, wherein the indication is a value of 0 or a negative value defined as the duration of validity.

14. The apparatus of claim 12, wherein the indication is a value of an effectiveness duration shorter than the remaining time of the GNSS effectiveness duration associated with the last successful GNSS measurement.

15. The apparatus according to any one of claims 1 to 11, wherein the indication is a mark.

16. The apparatus according to any one of claims 1 to 11, wherein the scheduling request is transmitted using a dedicated configuration from the network.

17. An apparatus for a network node, the apparatus comprising: At least one processor; as well as At least one memory stores instructions that, when executed by the at least one processor, cause the device to at least: Before the GNSS validity period associated with the last successful Global Navigation Satellite System (GNSS) measurement for the User Equipment (UE) has expired, receive an indication from the UE indicating that the UE needs GNSS measurements. The indicated instruction is carried in at least one of the following: GNSS Effectiveness Duration Report Uplink Media Access Control (MAC) control element (CE). Scheduling request, or Radio Resource Control (RRC) message.

18. The apparatus of claim 17, wherein the apparatus is further configured such that, Transmit to the UE a command to receive or acknowledge the indication, or to trigger the required GNSS measurement.

19. The apparatus according to any one of claims 17 to 18, wherein the indication is used to indicate one of the following: The UE requests the network node to trigger the necessary GNSS measurement. The UE autonomously initiates the required GNSS measurements upon the indicated transmission. The UE autonomously begins the required GNSS measurement after an offset from the indicated transmission start point, or The UE autonomously initiates the required GNSS measurements according to network pre-configuration at the time of the indicated transmission or after an offset from the indicated transmission.

20. The apparatus according to any one of claims 17 to 19, wherein the indication is carried in the GNSS validity duration report, and the indication includes one or more values ​​of validity duration in the GNSS validity duration information element.

21. The apparatus of claim 20, wherein the indication is a value of 0 or a negative value defined as the duration of validity.

22. The apparatus of claim 20, wherein the indication is a value of an effectiveness duration shorter than the remaining time of the GNSS effectiveness duration associated with the last successful GNSS measurement.

23. The apparatus according to any one of claims 17 to 19, wherein the indication includes a flag in the GNSS validity duration report.

24. The apparatus according to any one of claims 17 to 19, wherein the apparatus is further configured to: Configure a dedicated configuration for the scheduling request.

25. A method performed at a user equipment (UE), the method comprising: Before the GNSS validity period associated with the UE's last successful Global Navigation Satellite System (GNSS) measurement expires, an indication indicating that the UE requires GNSS measurements is transmitted to the network node. The indicated instruction is carried in at least one of the following: GNSS Effectiveness Duration Report Uplink Media Access Control (MAC) control element (CE). Scheduling request, or Radio Resource Control (RRC) message.

26. A method executed at a network node, the method comprising: Before the GNSS validity period associated with the last successful Global Navigation Satellite System (GNSS) measurement for the User Equipment (UE) has expired, receive an indication from the UE indicating that the UE needs GNSS measurements. The indicated instruction is carried in at least one of the following: GNSS Effectiveness Duration Report Uplink Media Access Control (MAC) control element (CE). Scheduling request, or Radio Resource Control (RRC) message.

27. A computer-readable medium having computer program code thereon, which, when executed on a computer, causes the computer to perform the method according to claim 25.

28. A computer-readable medium having computer program code thereon, which, when executed on a computer, causes the computer to perform the method according to claim 26.

Images