Indicating global navigation satellite system availability

Abstract

Aspects of the present disclosure relate to indicating global navigation satellite system availability. Generally, a user equipment (UE) global navigation satellite system (GNSS) interruption or GNSS position inaccuracy indication is determined when in a connected or idle state. This information may be used for the network to determine which solutions may be applied to time and frequency compensation when the GNSS is not available. For example, the techniques discussed herein provide a network-based or UE-based signaling procedure with one or both of implicit or explicit indication methods to understand GNSS unavailability for a connected UE. For example, the indication may be initiated based on a certain explicit request configuration message by the network, or based on an implicit indication by the network (e.g., pre-configured criteria set by the network to initiate the indication), or the UE autonomously decides to initiate the signaling message.

Description

Cross-references to related applications

[0001] This application claims priority to U.S. Patent Application Serial No. 63 / 545,626, filed October 25, 2023, entitled “Indicating Global Navigation Satellite System Availability,” the entire contents of which are incorporated herein by reference. Technical Field

[0002] This disclosure relates to wireless communications, and more specifically to indicating or reporting the availability of a Global Navigation Satellite System (GNSS). Background Technology

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

[0004] In some wireless communication systems, the UE determines its location, such as by using a GNSS system. The UE can use its location to determine various parameters used in communicating with other devices in the wireless communication system. For various reasons (such as due to UE movement), the UE's location may need to be updated periodically. Summary of the Invention

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

[0006] Some implementations of the methods and apparatus described herein may also include a UE for wireless communication. The UE acquires one or more GNSS parameter values ​​based at least in part on a configuration including one or more GNSS parameters related to GNSS availability; and sends first signaling to a network device (NE) indicating one or more GNSS parameter values ​​based at least in part on one or more GNSS parameters related to GNSS availability.

[0007] In some implementations of the methods and apparatus described herein, the UE receives a second signaling from the NE, which indicates the configuration of one or more GNSS parameters related to GNSS availability. Alternatively or additionally, this configuration applies to the UE when it is in a connected or idle state. Alternatively or additionally, one or more GNSS parameter values ​​indicate a GNSS outage. Alternatively or additionally, a GNSS outage corresponds to a period of no GNSS connection or the number of GNSS satellites in the UE's field of view being less than a threshold number of GNSS satellites. Alternatively or additionally, one or more GNSS parameter values ​​indicate GNSS inaccuracy. Alternatively or additionally, one or more GNSS parameters include at least a position accuracy threshold parameter. Alternatively or additionally, GNSS position inaccuracy defines a GNSS position estimate when the GNSS accuracy of the GNSS position is below a GNSS position accuracy threshold. Alternatively or additionally, one or more GNSS parameters indicate the minimum duration for a GNSS outage or GNSS position inaccuracy. Alternatively or additionally, one or more GNSS parameter values ​​include at least one of the following: GNSS constellation identifier (ID), position accuracy, number of GNSS satellites in the UE's field of view, or GNSS signal measurement. Alternatively or additionally, one or more GNSS parameters include parameters defining the measurement periodicity. Alternatively or additionally, one or more GNSS parameter values ​​include at least one of the following: GNSS outage timestamp; last GNSS coordinates; last GNSS measurement; expected GNSS outage duration; rate of change of satellite position; GNSS accuracy; GNSS constellation ID; or number of GNSS satellites in the UE's field of view. Alternatively or additionally, in response to a change in one or more GNSS parameter values, the UE sends a second signaling to the NE indicating one or more updated GNSS parameter values, at least in part based on one or more GNSS parameters. Alternatively or additionally, the first signaling indicates a request for timing advance (TA) adjustment. Alternatively or additionally, this configuration includes criteria for determining the request for TA adjustment from the NE. Alternatively or additionally, the UE receives a second signaling from the NE, the second signaling indicating a reporting configuration for the transmission of one or more GNSS parameter values; and sends a first signaling to the NE based at least in part on the reporting configuration. Alternatively or additionally, the reporting configuration includes one or more of the following: a set of timing opportunities for the transmission of one or more GNSS parameter values, a set of time-frequency resources for the transmission of one or more GNSS parameter values, or at least one criterion for the transmission of one or more GNSS parameter values. Alternatively or additionally, the first signaling includes: reporting one or both of GNSS health or GNSS outage in a timing advance report.Alternatively or additionally, the first signaling includes a parameter indicating the duration of validity of the reported GNSS position estimate. Alternatively or additionally, the validity duration defines a time during which the GNSS position estimate is valid or the UE experiences good GNSS signal strength. Alternatively or additionally, the UE performs GNSS measurements during the GNSS validity duration; and an indication of GNSS interruption during the GNSS validity duration is included in the first signaling.

[0008] Some implementations of the methods and apparatus described herein may also include a base station for wireless communication. The base station sends a first signaling message to a network entity, the first signaling message indicating a request message including information about the GNSS state of the UE; and receives a second signaling message from the network entity, the second signaling message indicating a response message including one or more parameters defining the GNSS state of the UE.

[0009] In some implementations of the methods and apparatus described herein, the network entity includes a Location Management Function (LMF). Additionally or alternatively, one or more parameters defining the GNSS state include at least one of the following: GNSS health, GNSS coverage area, or GNSS frequency band. Additionally or alternatively, the base station receives response messages from the operation and management functions.

[0010] Some implementations of the methods and apparatus described herein may also include a base station for wireless communication. The base station receives first signaling from the UE, indicating values ​​of one or more GNSS parameters, based at least in part on a configuration including one or more GNSS parameters related to GNSS availability.

[0011] In some implementations of the methods and apparatus described herein, the base station sends a second signaling to the UE, the second signaling indicating the configuration of one or more GNSS parameters related to GNSS availability. Alternatively or additionally, this configuration applies to the UE when the UE is in a connected or idle state. Alternatively or additionally, one or more GNSS parameter values ​​indicate a GNSS outage. Alternatively or additionally, a GNSS outage corresponds to a period of no GNSS connection or the number of GNSS satellites in the UE's field of view being less than a threshold number of GNSS satellites. Alternatively or additionally, one or more GNSS parameter values ​​indicate GNSS inaccuracy. Alternatively or additionally, one or more GNSS parameters include at least a position accuracy threshold parameter. Alternatively or additionally, GNSS position inaccuracy defines a GNSS position estimate when the GNSS accuracy of the GNSS position is below a GNSS position accuracy threshold. Alternatively or additionally, one or more GNSS parameters indicate the minimum duration for a GNSS outage or GNSS position inaccuracy. Alternatively or additionally, one or more GNSS parameter values ​​include at least one of the following: GNSS constellation ID, position accuracy, number of GNSS satellites within the UE's field of view, or GNSS signal measurement. Alternatively or additionally, one or more GNSS parameters include parameters defining the measurement periodicity. Alternatively or additionally, one or more GNSS parameter values ​​include at least one of the following: GNSS outage timestamp; last GNSS coordinates; last GNSS measurement; expected GNSS outage duration; rate of change of satellite position; GNSS accuracy; GNSS constellation ID; or number of GNSS satellites within the UE's field of view. Alternatively or additionally, the base station receives, at least in part based on one or more GNSS parameters, a second signaling indicating one or more updated GNSS parameter values ​​in response to a change in one or more GNSS parameter values. Alternatively or additionally, the first signaling indicates a request for TA adjustment. Alternatively or additionally, this configuration includes criteria for determining the request for TA adjustment from the base station. Alternatively or additionally, the base station sends a second signaling to the UE, the second signaling indicating a reporting configuration for the transmission of one or more GNSS parameter values; and receives a first signaling from the UE based at least in part on the reporting configuration. Alternatively or additionally, the reporting configuration includes one or more of the following: a set of timing opportunities for the transmission of one or more GNSS parameter values, a set of time-frequency resources for the transmission of one or more GNSS parameter values, or at least one criterion for the transmission of one or more GNSS parameter values. Alternatively or additionally, the first signaling includes reporting one or both of GNSS health or GNSS outages in a timing advance report. Alternatively or additionally, the first signaling includes a parameter indicating the duration of validity of the reported GNSS position estimate.Additional or alternative ground, the validity duration defines the time during which the GNSS position estimate is valid or the UE experiences good GNSS signal strength. Additional or alternative ground, the first signaling includes an indication of GNSS interruption during the GNSS validity duration.

[0012] Some implementations of the methods and apparatus described herein may also include a processor for wireless communication. The processor acquires one or more GNSS parameter values ​​based at least in part on a configuration including one or more GNSS parameters related to GNSS availability; and sends first signaling to the NE indicating one or more GNSS parameter values ​​based at least in part on the one or more GNSS parameters related to GNSS availability.

[0013] In some implementations of the methods and apparatus described herein, at least one controller is configured to cause a processor to receive a second signaling from the NE, the second signaling indicating a configuration including one or more GNSS parameters related to GNSS availability. Additionally or alternatively, this configuration applies to the UE including the processor when the UE is in a connected or idle state. Additionally or alternatively, one or more GNSS parameter values ​​indicate a GNSS outage. Additionally or alternatively, a GNSS outage corresponds to a period of no GNSS connection or the number of GNSS satellites in the UE's field of view being less than a threshold number of GNSS satellites. Additionally or alternatively, one or more GNSS parameter values ​​indicate GNSS position inaccuracy. Additionally or alternatively, one or more GNSS parameters include at least a position accuracy threshold parameter. Additionally or alternatively, GNSS position inaccuracy defines a GNSS position estimate when the GNSS accuracy of the GNSS position is below a GNSS position accuracy threshold. Additionally or alternatively, one or more GNSS parameters indicate a minimum duration for GNSS outage or GNSS position inaccuracy. Alternatively or additionally, one or more GNSS parameter values ​​include at least one of the following: GNSS constellation ID, position accuracy, the number of GNSS satellites in relation to the UE including the processor, or GNSS signal measurements. Alternatively or additionally, one or more GNSS parameters include parameters defining the periodicity of measurements. Alternatively or additionally, one or more GNSS parameter values ​​include at least one of the following: GNSS outage timestamp; last GNSS coordinates; last GNSS measurement; expected GNSS outage duration; rate of change of satellite position; GNSS accuracy; GNSS constellation ID; or the number of GNSS satellites in relation to the UE including at least one processor. Alternatively or additionally, the processor, in response to a change in one or more GNSS parameter values, sends a second signaling to the NE indicating one or more updated GNSS parameter values, at least in part based on one or more GNSS parameters. Alternatively or additionally, the first signaling indicates a request for TA adjustment. Alternatively or additionally, the configuration includes criteria for determining the request for TA adjustment from the NE. Additionally or alternatively, the processor receives a second signaling from the NE, the second signaling indicating a reporting configuration for the transmission of one or more GNSS parameter values; and sends a first signaling to the NE based at least in part on the reporting configuration. Additionally or alternatively, the reporting configuration includes one or more of the following: a set of timing opportunities for the transmission of one or more GNSS parameter values, a set of time-frequency resources for the transmission of one or more GNSS parameter values, or at least one criterion for the transmission of one or more GNSS parameter values. Additionally or alternatively, the first signaling includes reporting one or both of GNSS health or GNSS outages in the timing advance report.Alternatively or additionally, the first signaling includes a parameter indicating the duration of validity of the reported GNSS position estimate. Alternatively or additionally, the validity duration defines a time during which the GNSS position estimate is valid or the UE, including the processor, experiences good GNSS signal strength. Alternatively or additionally, the processor performs GNSS measurements during the GNSS validity duration; and an indication of GNSS interruption during the validity duration is included in the first signaling.

[0014] Some implementations of the methods and apparatus described herein may also include a method performed by a UE, comprising: acquiring one or more GNSS parameter values ​​based at least in part on a configuration including one or more GNSS parameters relating to GNSS availability; and sending first signaling to a NE indicating one or more GNSS parameter values ​​based at least in part on the one or more GNSS parameters relating to GNSS availability.

[0015] In some implementations of the methods and apparatus described herein, the method further includes: receiving a second signaling from the NE, the second signaling indicating a configuration including one or more GNSS parameters related to GNSS availability. Additionally or alternatively, this configuration applies to the UE when the UE is in a connected or idle state. Additionally or alternatively, one or more GNSS parameter values ​​indicate a GNSS outage. Additionally or alternatively, a GNSS outage corresponds to a period of no GNSS connection or the number of GNSS satellites in the UE's field of view being less than a threshold number of GNSS satellites. Additionally or alternatively, one or more GNSS parameter values ​​indicate GNSS inaccuracy. Additionally or alternatively, one or more GNSS parameters include at least a position accuracy threshold parameter. Additionally or alternatively, GNSS inaccuracy defines a GNSS position estimate when the GNSS accuracy of the GNSS position is below a GNSS position accuracy threshold. Additionally or alternatively, one or more GNSS parameters indicate a minimum duration for GNSS outage or GNSS inaccuracy. Alternatively or additionally, one or more GNSS parameter values ​​include at least one of the following: GNSS constellation ID, position accuracy, number of GNSS satellites in the UE's field of view, or GNSS signal measurement. Alternatively or additionally, one or more GNSS parameters include parameters defining the measurement periodicity. Alternatively or additionally, one or more GNSS parameter values ​​include at least one of the following: GNSS outage timestamp; last GNSS coordinates; last GNSS measurement; expected GNSS outage duration; rate of change of satellite position; GNSS accuracy; GNSS constellation ID; or number of GNSS satellites in the UE's field of view. Alternatively or additionally, the method includes: in response to a change in one or more GNSS parameter values, sending a second signaling to the NE indicating one or more updated GNSS parameter values, at least in part based on one or more GNSS parameters. Alternatively or additionally, the first signaling indicates a request for TA adjustment. Alternatively or additionally, the configuration includes criteria for determining the request for TA adjustment from the NE. Alternatively or additionally, the method includes: receiving a second signaling from the NE, the second signaling indicating a reporting configuration for the transmission of one or more GNSS parameter values; and sending a first signaling to the NE based at least in part on the reporting configuration. Alternatively or additionally, the reporting configuration includes one or more of the following: a set of timing opportunities for the transmission of one or more GNSS parameter values, a set of time-frequency resources for the transmission of one or more GNSS parameter values, or at least one criterion for the transmission of one or more GNSS parameter values. Alternatively or additionally, the first signaling includes: reporting one or both of GNSS health or GNSS outage in a timing advance report.Alternatively or additionally, the first signaling includes: a parameter indicating the duration of validity of the reported GNSS position estimate. Alternatively or additionally, the validity duration defines a time during which the GNSS position estimate is valid or the UE experiences good GNSS signal strength. Alternatively or additionally, the method includes: performing GNSS measurements during the GNSS validity duration; and an indication of a GNSS interruption during the GNSS validity duration is included in the first signaling.

[0016] Some implementations of the methods and apparatus described herein may also include a method performed by a base station, the method comprising: sending a first signaling to a network entity, the first signaling indicating a request message including information about the GNSS state of the UE; and receiving a second signaling from the network entity, the second signaling indicating a response message including one or more parameters defining the GNSS state of the UE.

[0017] In some implementations of the methods and apparatus described herein, the method further includes: a network entity comprising an LMF. Additionally or alternatively, one or more parameters defining the GNSS state include at least one of the following: GNSS health, GNSS coverage area, or GNSS frequency band. Additionally or alternatively, the method includes: receiving a response message from an operational and management function.

[0018] Some implementations of the methods and apparatus described herein may also include a method performed by a base station, the method comprising: receiving, at least in part, first signaling from a UE indicating values ​​of one or more GNSS parameters based on a configuration including one or more GNSS parameters relating to GNSS availability.

[0019] In some implementations of the methods and apparatus described herein, the method further includes: sending a second signaling to the UE, the second signaling indicating a configuration including one or more GNSS parameters related to GNSS availability. Additionally or alternatively, this configuration applies to the UE when the UE is in a connected or idle state. Additionally or alternatively, one or more GNSS parameter values ​​indicate a GNSS outage. Additionally or alternatively, a GNSS outage corresponds to a period of no GNSS connection or the number of GNSS satellites in the UE's field of view being less than a threshold number of GNSS satellites. Additionally or alternatively, one or more GNSS parameter values ​​indicate GNSS position inaccuracy. Additionally or alternatively, one or more GNSS parameters include at least a position accuracy threshold parameter. Additionally or alternatively, GNSS position inaccuracy defines a GNSS position estimate when the GNSS accuracy of the GNSS position is below a GNSS position accuracy threshold. Additionally or alternatively, one or more GNSS parameters indicate a minimum duration for GNSS outage or GNSS position inaccuracy. Alternatively or additionally, one or more GNSS parameter values ​​include at least one of the following: GNSS constellation ID, position accuracy, number of GNSS satellites in the UE's field of view, or GNSS signal measurement. Alternatively or additionally, one or more GNSS parameters include parameters defining the periodicity of the measurement, and a first signaling indicating the GNSS parameter value is transmitted. Alternatively or additionally, one or more GNSS parameter values ​​include at least one of the following: GNSS outage timestamp; last GNSS coordinates; last GNSS measurement; expected GNSS outage duration; rate of change of satellite position; GNSS accuracy; GNSS constellation ID; or number of GNSS satellites in the UE's field of view. Alternatively or additionally, the method includes: receiving from the UE, at least in part based on one or more GNSS parameters, a second signaling indicating one or more updated GNSS parameter values ​​in response to a change in one or more GNSS parameter values. Alternatively or additionally, the first signaling indicates a request for TA adjustment. Alternatively or additionally, the configuration includes criteria for determining a request for TA adjustment from a base station. Alternatively or additionally, the method includes: sending a second signaling to the UE, the second signaling indicating a reporting configuration for the transmission of one or more GNSS parameter values; and receiving a first signaling from the UE based at least in part on the reporting configuration. Alternatively or additionally, the reporting configuration includes one or more of the following: a set of timing opportunities for the transmission of one or more GNSS parameter values, a set of time-frequency resources for the transmission of one or more GNSS parameter values, or at least one criterion for the transmission of one or more GNSS parameter values. Alternatively or additionally, the first signaling includes reporting one or both of GNSS health or GNSS outage in a timing advance report.Alternatively, the first signaling may include a parameter indicating the duration of validity of the reported GNSS position estimate. Alternatively, the validity duration defines a time during which the GNSS position estimate is valid or the UE experiences good GNSS signal strength. Alternatively, the first signaling may include an indication of GNSS interruption during the GNSS validity duration. Attached Figure Description

[0020] Figure 1 An example of a wireless communication system according to aspects of this disclosure is illustrated.

[0021] Figure 2 An example of the timing relationship between a co-located gNB and an NTN gateway according to aspects of this disclosure is illustrated.

[0022] Figure 3A and Figure 3B The illustration shows an example information element (IE) according to aspects of this disclosure.

[0023] Figure 4 An example of a signaling flow for indicating a GNSS interruption according to aspects of this disclosure is illustrated.

[0024] Figure 5 An example of a signaling flow for indicating a GNSS interruption according to aspects of this disclosure is illustrated.

[0025] Figure 6 An example IE is illustrated according to aspects of this disclosure.

[0026] Figure 7 An example IE is illustrated according to aspects of this disclosure.

[0027] Figure 8 An example of a UE according to aspects of this disclosure is illustrated.

[0028] Figure 9 An example of a processor according to aspects of this disclosure is illustrated.

[0029] Figure 10 An example of a network device (NE) according to aspects of this disclosure is illustrated.

[0030] Figure 11 The diagram illustrates a flowchart of a method performed by a UE according to aspects of this disclosure.

[0031] Figure 12 The diagram illustrates a flowchart of a method performed by an NE according to aspects of this disclosure.

[0032] Figure 13 The diagram illustrates a flowchart of a method performed by an NE according to aspects of this disclosure. Detailed Implementation

[0033] To enable UE access to an NTN, such as a New Radio (NR) NTN or an Internet of Things (IoT) NTN, the UE can utilize GNSS capabilities. GNSS coordinates allow the UE to know its location, which is used to pre-compensate for time and frequency offsets for wireless communication with the NTN. For example, NR NTN (also known as NR-NTN) utilizes an open-loop timing adjustment process for a transparent payload NTN architecture, where timing advance (TA) is divided into common TA (e.g., corresponding to delays on the feeder link) and user-specific TA (e.g., corresponding to bidirectional transmission delays on the serving link). To estimate the user-specific TA, the UE uses the serving satellite location (this information is provided to the UE by the network) and its own location (based on GNSS). Furthermore, due to the continuous movement of non-geostationary orbit (NGSO) satellites, the UE can continuously update timing advance and frequency pre-compensation in connected mode. Therefore, the UE uses a reliable GNSS connection for NTN access throughout its connected time period.

[0034] Although GNSS provides highly accurate position and time references, GNSS signals may be unavailable for a certain period of time under various conditions or scenarios. For example, GNSS signals may be interrupted or interfered with, or GNSS signals may be spoofed, leading to inaccurate UE positions, thus causing NTN connection rejection in such cases, as the user-specific TA obtained from an incorrect UE position may make UL communication difficult. Such scenarios may have a simultaneous impact on a group of UEs in the cell for a certain period of time. Additionally, there may be situations where UEs experience NTN service degradation due to a relatively reduced GNSS position estimate (e.g., accuracy reduced to 500 meters (m) or 1 kilometer (km)), caused by a variety of reasons, such as poor GNSS link budget or the unavailability of the required number of satellites, or the UE's position (e.g., in a pocket, bag, etc.).

[0035] Due to either temporary unavailability or inaccuracy of GNSS location, or both, the degradation or rejection of NR NTN services for UEs already in a connected state can have a more severe impact on the connectivity or performance of the entire NTN system. Therefore, the techniques discussed in this paper improve the robustness of NR NTN for time and frequency synchronization during temporary GNSS unavailability, particularly in a connected state. The techniques discussed in this paper include methods and related signaling aspects for the network to determine GNSS outages or location inaccuracies during connected or idle states, so that the network can configure methods for time and frequency synchronization during such GNSS unavailability.

[0036] Typically, the techniques discussed in this paper determine GNSS outages or inaccurate GNSS location indications when the UE is connected or idle. This information can be used by the network to determine which solutions can be applied for time and frequency compensation when GNSS is unavailable. For example, the techniques discussed in this paper provide a network-based or UE-based signaling procedure with one or both of implicit or explicit indication methods to understand GNSS unavailability for the connected UE.

[0037] In one or more implementations, the UE explicitly or implicitly indicates to the network the unavailability or interruption of GNSS (or inaccurate location information) in one or both of the connected or idle states, wherein the indication may be initiated based on an explicit request configuration message made by the network, or based on an implicit indication made by the network (e.g., a pre-configuration standard set by the network to initiate the indication), or the UE may decide to initiate a signaling message autonomously.

[0038] Additionally or alternatively, the network configures the UE to report GNSS outage indications, where a GNSS outage can be defined as "when the UE does not have or cannot find any GNSS connectivity, or there are not the required minimum number of satellites in the field of view." This can be part of the GNSS state configuration, or a separate configuration can be used for this purpose. In one example, the network configures the UE to report when GNSS location accuracy falls below a certain threshold (which can be set by the network), where the network uses higher-level signaling or configures the relevant threshold parameters via dedicated signaling. Higher-level signaling, as used herein, refers to signaling at, for example, the RRC layer or above.

[0039] Alternatively or concurrently, the UE determines the duration of its GNSS validity and reports this duration back to the network using higher-layer signaling or dedicated signaling. This validity duration may specify the time the UE expects to be in good GNSS coverage conditions, based in part on one or both of satellite movement and UE movement. In one example, the GNSS validity duration parameter is reported to the network during initial access and is part of the Random Access Channel (RACH) procedure; for example, in a 4-step RACH procedure, this may be reported in Msg 1, or in a 2-step RACH procedure, this may be reported in MsgA. In another implementation, the UE may send the GNSS validity duration whenever it calculates a user-specific TA.

[0040] Although signaling parameters are defined to enable the network to determine UE RAT-independent location information, there is currently no technology for the UE to indicate GNSS unavailability or for the network to configure parameters to the UE to indicate GNSS outage. If GNSS is unavailable during connected or idle states, the current TA procedure will not function, and there is no method to allow the network to know about the GNSS outage before the uplink synchronization validity period expires and when a new TA adjustment is needed. The techniques discussed in this paper improve the robustness of NTN by allowing the UE to notify the network of GNSS outages and location inaccuracies (including temporary unavailability of GNSS service or GNSS location accuracy below a certain threshold).

[0041] Aspects of this disclosure are described in the context of wireless communication systems.

[0042] Figure 1 An example of a wireless communication system 100 according to aspects of this disclosure is illustrated. The wireless communication system 100 may include one or more NEs 102, one or more UEs 104, and a core network (CN) 106. The wireless communication system 100 may support various radio access technologies. In some implementations, the wireless communication system 100 may be a 4G network, such as an LTE network or an LTE Advanced (LTE-A) network. In some other implementations, the radio communication system 100 may be a new radio (NR) network, such as a 5G network, a 5G evolution (5G-A) network, or a 5G ultra-wideband (5G-UWB) network. In other implementations, the wireless communication system 100 may be a combination of 4G and 5G networks, or other suitable radio access technologies (including IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20). The wireless communication system 100 may go beyond 5G radio access technologies, such as 6G. Additionally, the wireless communication system 100 may support technologies such as time division multiplexing (TDMA), frequency division multiplexing (FDMA), or code division multiplexing (CDMA).

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

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

[0045] One or more UEs 104 may be distributed throughout the geographic area of ​​the wireless communication system 100. UE 104 may include or be referred to as a remote unit, mobile device, wireless device, remote device, subscriber device, transmitter device, receiver device, or some other suitable term. In some implementations, UE 104 may be referred to as a unit, station, terminal, or client, etc. Additionally or alternatively, UE 104 may be referred to as an Internet of Things (IoT) device, Internet of Everything (IoE) device, or machine-type communication (MTC) device, etc.

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

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

[0048] CN 106 can support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. CN 106 can be an evolved packet core (EPC) or a 5G core (5GC), which may include control plane entities that manage access and mobility (e.g., a mobility management entity (MME), access and mobility management functions (AMF)) and user plane entities that route or interconnect packets to external networks (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)). In some implementations, the control plane entities may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signaling bearers, etc.) for one or more UEs 104 served by one or more NEs 102 associated with CN 106.

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

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

[0051] One or more digital technologies may be supported in the wireless communication system 100, and the digital technologies may include subcarrier spacing and cyclic prefix. A first digital technology (e.g., μ =0) can be associated with the first subcarrier spacing (e.g., 15 kHz) and the regular cyclic prefix. In some implementations, the first digital technique (e.g., ...) associated with the first subcarrier spacing (e.g., 15 kHz) is... μ =0) can utilize one time slot per subframe. Second digital technologies (e.g., μ =1) can be associated with the second subcarrier spacing (e.g., 30 kHz) and the conventional cyclic prefix. The third digital technology (e.g., μ =2) can be associated with a third subcarrier spacing (e.g., 60 kHz) and a regular cyclic prefix or an extended cyclic prefix. A fourth digital technology (e.g., μ =3) can be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a conventional cyclic prefix. A fifth digital technology (e.g., μ =4) can be associated with the fifth subcarrier spacing (e.g., 240 kHz) and the regular cyclic prefix.

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

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

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

[0055] FR1 can be associated with one or more digital technologies (e.g., at least three digital technologies). For example, FR1 can be associated with the following: a first digital technology (e.g., μ =0), which includes a 15 kHz subcarrier spacing; second digital technology (e.g., μ =1), which includes a 30 kHz subcarrier spacing; and a third digital technology (e.g., μ =2), which includes a subcarrier spacing of 60 kHz. FR2 can be associated with one or more digital technologies (e.g., at least two digital technologies). For example, FR2 can be associated with a third digital technology (e.g., μ=2), which includes a 60 kHz subcarrier spacing; fourth digital technology (e.g., μ =3), which includes a subcarrier spacing of 120 kHz.

[0056] The technology discussed in this article refers to GNSS. The technology discussed in this article can be used in conjunction with any of a variety of GNSS technologies, such as one or more of the Global Positioning System (GPS), Global Navigation Satellite System (GLONASS), BeiDou, Galileo, and Indian Regional Navigation Satellite System (IRNSS).

[0057] In the NR NTN transparent payload architecture, UE 104 pre-compensates for bidirectional transmission delays on the serving link based on its TA calculation, which is determined by UE 104 using the serving satellite location and its own location. It is assumed that the NR NTN UE has GNSS capability and uses GNSS to calculate its own location. However, GNSSprone is susceptible to spoofing and interference, which can lead to temporary unavailability of GNSS location, ultimately resulting in service rejection for UE 104, even if UE 104 is in connected mode, as UE 104 may need to calculate TA multiple times due to GNSS satellite movement. To improve the robustness of the NTN system, TA calculation is enhanced during the duration of these temporary GNSS outages, especially for UE 104 in idle or connected modes. For this purpose, the network is notified in advance of the temporary unavailability of GNSS service or when the accuracy of GNSS location falls below a certain threshold. The techniques discussed in this paper provide configuration and reporting between the NG-RAN node and UE 104, or even some information exchange between the NG-RAN node and the core network (e.g., LMF).

[0058] This disclosure provides solutions for determining UE GNSS interruption or inaccurate GNSS location indication during connected or idle states. This information may be needed by the network to determine which solutions can be applied for time and frequency compensation when GNSS is unavailable. For example, the techniques discussed herein provide a network-based or UE-based signaling procedure with one or both of implicit or explicit indication methods so that the network knows GNSS unavailability for the connected UE 104.

[0059] The communication between devices discussed in this document (such as the communication between UE 104 and network entity 102) is performed using any of a variety of different signaling methods. For example, such signaling can be any of a variety of messages, requests, or responses, such as trigger messages, configuration messages, etc. As another example, such signaling can be any of a variety of signaling media or protocols through which messages are delivered, such as any combination of Radio Resource Control (RRC), Downlink Control Information (DCI), Uplink Control Information (UCI), Sidelink Control Information (SCI), Media Access Control Element (MAC-CE), Sidelink Positioning Protocol (SLPP), PC5 Radio Resource Control (PC5-RRC), etc.

[0060] Regarding timing adjustment in NTN, the time and frequency synchronization in NTN are as follows.

[0061] The downlink (DL) and uplink (UL) are frame aligned at the uplink time synchronization reference point (RP), where the offset is determined by... N TA,offset Provided.

[0062] To accommodate the propagation delay in NTN, several timing relationships are advanced by a common timing advance (common TA) and two offsets. K offset and k mac Enhanced: - The common TA is the configured timing offset, which is equal to the RTT between the RP and the NTN payload. - K offset It is the configured scheduling offset, which is greater than or equal to the sum of the service link RTT and the common TA. - k mac It is the configured offset, which is approximately equal to the RTT between RP and gNB.

[0063] Scheduling offset K offset It is used to allow the UE sufficient processing time between downlink reception and uplink transmission.

[0064] Offset k mac It is used to delay the application of downlink configuration indicated by Media Access Control (MAC) control element (CE) commands on the Physical Downlink Shared Channel (PDSCH) and to estimate UE-gNB RTT. This is used when downlink and uplink frame timings are misaligned at the gNB. k mac It can be provided online.k mac It is also used in the random access procedure to determine the start time of the random access response (RAR) window / MsgB window after Msg1 / MsgA transmission.

[0065] Figure 2 Example 200 illustrates timing relationships for co-location gNBs and NTN gateways according to various aspects of this disclosure. Example 200 illustrates serving link RTT 202, feeder link RTT 204, RP 206, common TA 208, and k. mac 210, and TA time (T) TA 212.

[0066] The network can be configured with Hybrid Automatic Repeat Request (HARQ) operation as follows: - For the downlink, HARQ feedback can be enabled or disabled per HARQ process. Disabling HARQ feedback allows a previously scheduled HARQ process to proceed even if one HARQ RTT has elapsed since the last scheduling. For the uplink, HARQ modes (e.g., HARQ mode A or HARQ mode B) can be configured per HARQ process. HARQ mode B allows for HARQ processes to run once a HARQ RTT has elapsed since the last scheduling.

[0067] It should be noted that for HARQ processes configured with enabled or disabled HARQ feedback, the network implementation is responsible for ensuring appropriate configuration of HARQ feedback (e.g., all enabled or all disabled) for HARQ processes configured using semi-persistent scheduling (SPS). For HARQ processes configured with HARQ modes, the network implementation is responsible for ensuring appropriate configuration of the HARQ mode (e.g., all HARQ mode A or all HARQ mode B) for HARQ processes configured using configuration authorization (CG).

[0068] Regarding timing advance and frequency pre-compensation, for the serving cell, the network broadcasts valid ephemeris information and common TA parameters. Before connecting to the NTN cell, the UE has a valid GNSS location, ephemeris, and common TA. To achieve synchronization, before and during connection to the NTN cell, the UE calculates the RTT between the UE and RP based on the GNSS location, ephemeris, and common TA parameters, and autonomously pre-compensates the TTA for the RTT between the UE and RP.

[0069] The UE calculates the frequency Doppler shift of the serving link and autonomously pre-compensates for it during uplink transmission by taking into account the UE's location and ephemeris. If the UE does not have a valid GNSS location and / or a valid ephemeris and public TA, it does not transmit until both are regained.

[0070] In connected mode, the UE can continuously update timing advance and frequency pre-compensation.

[0071] The UE can be configured to report timing advance during a random access procedure or in connected mode. In connected mode, event-triggered reporting of timing advance is supported.

[0072] While the pre-compensation for instantaneous Doppler shift experienced on the serving link will be performed by the UE, the management of Doppler shift experienced on the feeder link and transponder frequency error will be left to the network implementation.

[0073] The following section will discuss the transmission timing adjustment process used for TN and NTN.

[0074] The UE can be provided with a timing advance offset value for the serving cell via n-TimingAdvanceOffset for the serving cell. N TA,offset If the UE is not provided with an n-TimingAdvanceOffset for the serving cell, the UE determines a default value for the timing advance offset for the serving cell. N TA,offset .

[0075] If the UE is configured with two UL carriers for the serving cell, the same timing advance offset value N TA,offset This applies to both carriers.

[0076] After receiving the timing advance command for the Timing Advance Group (TAG), the UE uses a value that the UE expects to be the same for all serving cells in the TAG. N TA,offset Furthermore, based on the received timing advance instruction, the uplink timing of one or more of the Physical Uplink Control Channel (PUSCH), Sounding Reference Signal (SRS), or Physical Uplink Control Channel (PUCCH) transmissions in all serving cells of the TAG is adjusted, wherein the uplink timing for PUSCH / SRS / PUCCH transmissions is the same for all serving cells in the TAG.

[0077] For a frequency band with Synchronous Continuous In-Band Evolved Universal Terrestrial Radio Access New Radio (EN) Dual Connectivity (DC) in a frequency band combination with inapplicable maximum transmission timing difference requirements, if the UE indicates ul-TimingAlignmentEUTRA-NR as 'Required' and the UE determines that the uplink transmission timing is different based on the timing adjustment indications for the TAG from the Primary Cell Group (MCG) and the TAG from the Secondary Cell Group (SCG), then the UE adjusts the transmission timing of PUSCH / SRS / PUCCH transmissions on all serving cell portions of the synchronous continuous in-band EN-DC in that frequency band based on the timing adjustment indication for the TAG from the serving cell in the MCG within the frequency band. When PUSCH / SRS / PUCCH overlaps in time with, or even partially overlaps with, a random access preamble transmitted in another CG, the UE is not expected to transmit PUSCH / SRS / PUCCH in one CG.

[0078] For 2 μ • A subcarrier spacing (SCS) of 15 kHz, the timing advance command indication for TAG indicates a change in uplink timing relative to the current uplink timing used for TAG, which is a multiple of 16.64. T c / 2 μ .

[0079] In the case of random access response or in the timing advance command in the absolute timing advance command MAC CE used for TAG ( T A )pass T A = 0, 1, 2, ..., 3846 to indicate N TA Values, where TAG is used with 2 μ • The number of time alignments for the 15kHz SCS is N TA = T A ∙16∙64 / 2 μ . N TA It is relative to the SCS transmitted from the UE on the first uplink after receiving the random access response or absolute timing advance command MAC CE.

[0080] In other cases, the timing advance command for TAG T A pass T A = 0, 1, 2, ..., 63 to indicate the current index value. N TA valueN TA_old The adjustment is for the new N TA value N TA_new For 2 μ • 15kHz SCS, .

[0081] If a UE has multiple active UL bandwidth portions (BWPs) in the same TAG, including UL BWPs in two UL carriers of the serving cell, then the timing advance command value is relative to the largest SCS of the multiple active UL BWPs. Applicable values ​​for UL BWPs with lower SCS are as follows: N TA_new The value can be rounded to align with the timing advance granularity used for UL BWPs with lower SCS, while still meeting timing advance accuracy requirements.

[0082] Will N TA The positive or negative value adjustment indicates the amount by which the uplink transmission timing of the TAG is advanced or delayed.

[0083] For uplink time slots n The timing advance command received from the uplink, and the corresponding adjustment of uplink transmission timing from the uplink time slot for transmissions other than PUSCHs scheduled by RAR UL authorization or fallbackRAR UL authorization, or PUCCHs with HARQ-ACK information in response to successRAR. The beginning of its application, in which , N T,1 It corresponds to the PDSCH processing time used for UE processing capability 1 when the additional PDSCH demodulation reference signal (DM-RS) is configured. N The duration of a symbol (in milliseconds). N T,2 This corresponds to the PUSCH preparation time used for UE processing capability 1. N The duration of the two symbols (in milliseconds). N TA,max It is the maximum timing advance value (in milliseconds) that can be provided by the 12-bit TA command field. It is the number of time slots per subframe. T sf It is the duration of a 1-millisecond subframe. ,in Provided by cellSpecificKoffset, and Provided by the differential Koffset MAC CE command; otherwise, if not provided separately, then or . N 1 and N 2. The minimum SCS among all configured UL BWPs for all uplink carriers used in the TAG and all configured DL BWPs for the corresponding downlink carriers is determined. For μ = 0, UE assumes [6, TS 38.214]. Time slot n and It is determined relative to the minimum SCS among all configured UL BWPs used for all uplink carriers in the TAG. The minimum SCS is determined relative to the SCS of all configured ULBWPs for all uplink carriers used in the TAG and the minimum SCS of all configured initial UL BWPs provided by the initialUplinkBWP. Assuming... T TA =0, uplink time slot n It is the last of multiple uplink time slots that overlap with the PDSCH received time slots, where the PDSCH provides timing advance commands and T TA .

[0084] If the UE changes the active UL BWP between the time the timing advance command is received and the time the corresponding adjustment for uplink transmission timing is applied, the UE determines the timing advance command value based on the SCS of the new active UL BWP. If the UE changes the active UL BWP after the adjustment for uplink transmission timing is applied, the UE assumes the same absolute timing advance command value before and after the change of the active UL BWP.

[0085] If the received downlink timing changes and is not compensated, or is only partially compensated through uplink timing adjustment without a timing advance command, the UE will change accordingly. N TA .

[0086] If two adjacent time slots overlap due to a TA command, the duration of the later time slot is reduced relative to the earlier time slot. The duration remains unchanged during the actual transmission time window used by the UE for PUSCH or PUCCH transmission. N TA .

[0087] Using the high-level ephemeris parameters of the serving satellite (if provided), the UE determines its location based on the location of the serving satellite and its own location. To pre-compensate for bidirectional transmission delay on the service link, the UE pre-compensates for the bidirectional transmission delay between the uplink time synchronization reference point and the serving satellite, based on the one-way propagation delay determined by the UE as follows. Determine [4, TS 38.211]: in TA Common , TA CommonDrift ,as well as TA CommonDriftVariant These are provided by ta-Common, ta-CommonDrift, and ta-CommonDriftVariant, respectively. t epoch Provided by epochTime, which is the epoch time of ta-Common, ta-CommonDrift, and ta-CommonDriftVariant. The time synchronization between the service satellite and the uplink time synchronization reference point t The distance divided by the speed of light. The uplink time synchronization reference points are DL and UL, and are determined by... N TA,offset The point that the given offset frame is aligned with. Regarding RRC signaling used for TA calculation in NTN, and information elements (IE) used for NTN configuration. NTN-Config IE It contains the basic parameter information needed to calculate public TA and user-specific TA.

[0088] Figure 3A and Figure 3B An example information element 300 according to an aspect of this disclosure is illustrated. Information element 300 is... NTN- Configure IE Examples are provided, and multiple fields are included.

[0089] EphemerisInfo The field provides satellite ephemeris information in the format of position and velocity state vectors or in the format of orbital parameters. This field is excluded when determining changes to system information; for example, changes to ephemeris information should neither result in a system information change notification nor in a change to system information block type 1 (…). SIB1 In ) valueTag The modifications.

[0090] epochTime This field indicates the epoch time used for NTN auxiliary information. When explicitly provided via System Information Block (SIB) or via dedicated signaling, EpochTimeThis is the start time of the DL subframe, indicated by the system frame number (SFN) and the subframe number transmitted with auxiliary information via signaling. For the serving cell, the field... sfn Indicates the current SFN or indicates epochTime The message is received after the next incoming SFN. For neighboring cells, sfn Indicator closest to the instruction epochTime The message is received from the SFN of the frame. The epoch time reference point of the Serving NTN payload ephemeris and common TA parameters is the uplink time synchronization reference point. If this field is missing, the epoch time is the end of the System Information (SI) window scheduled by SIB19. This field may be required when provided in a dedicated configuration. If this field is missing via... NTN-NeighCellConfig Provided ntn-Config If the epoch time is missing, the UE uses the epoch time of the serving cell; otherwise, the field is based on the timing of the serving cell (e.g., the SFN and subframe number indicated in this field refer to the SFN and subframe of the serving cell). In the case of handover or conditional handover, this field is based on the timing of the target cell; for example, the SFN and subframe number indicated in this field refer to the SFN and subframe of the target cell. For the target cell, the UE considers the epoch time indicated by the SFN and subframe number in this field to be the frame from which the message indicating the epoch time was received. This field is excluded when determining changes in system information (e.g., for...). epochTime The changes should neither result in system information change notifications nor cause... SIB1 In valueTag (Modifications).

[0091] cellSpecificKoffset This field indicates the scheduling offset used for the timing relationship modified for the NTN. The unit for the K_offset field is the number of time slots for a given subcarrier interval of 15 kHz. If this field does not exist, the UE assumes a value of 0.

[0092] If the downlink and uplink frame timings are not aligned at the gNB, then kmac This field indicates the scheduling offset provided by the network. It may be necessary to configure UE operations and assumptions for the downlink as indicated by the MAC CE command in the PDSCH. If this field is missing, the UE assumes a value of 0.

[0093] For the reference subcarrier spacing value in units of K_mac used in FR1, a value of 15 kHz is used. The unit of K_mac is the number of time slots used for a given subcarrier spacing.

[0094] ntn-PolarizationDLThe field (if present) includes parameters indicating polarization information used for downlink transmission on the serving link: including right-hand circular polarization, left-hand circular polarization (RHCP, LHCP), and linear polarization.

[0095] ntn-PolarizationUL The field (if present) includes parameters indicating the polarization information used for the uplink serving link. If it does not exist and ntn-PolarizationDL exists, the UE assumes the same polarization for UL and DL.

[0096] ntn-UlSyncValidityDuration The field indicates the validity duration configured by the network for auxiliary information (e.g., service and / or neighboring satellite ephemeris tables and common TA parameters), which indicates the maximum duration during which the UE can apply the auxiliary information without having acquired new auxiliary information (from [date]). epochTime rise).

[0097] ntn-UlSyncValidityDuration The unit is seconds. Value s5 Corresponding to 5 seconds, value s10 Indicates 10 seconds, and so on. This parameter applies to both connected and idle mode UEs. If this field is via... NTN-NeighCellConfig Provided ntn-Config If this field is missing, the UE uses the validity duration of the auxiliary information from the serving cell. This field is excluded when determining changes to system information (e.g., ntn-UlSyncValidityDuration The changes should neither result in system information change notifications nor cause... SIB1 In valueTag (Modifications). ntn-UlSyncValidityDuration exist epochTime , ta-Info , ephemerisInfo Update when at least one of them is updated.

[0098] ta-Common This field indicates the common timing advance value for network control, and it can include any timing offsets deemed necessary by the network. A value of 0 indicates a... ta-Common It is supported. ta-Common The granularity is 4.072 × 10^(-3) μs. Values ​​are given in units corresponding to the granularity. This field is excluded when determining changes in system information (e.g., ta- Common The change should neither result in a system information change notification nor in SIB1. valueTag (Modifications).

[0099] ta-CommonDriftThis field indicates the drift rate of the common TA. The granularity of ta-CommonDrift is 0.2 × 10^(-3) μs⁄s. Values ​​are given in units corresponding to the granularity. (This field is excluded when determining changes in system information.) ta-CommonDrift The change should neither result in a system information change notification nor in SIB1. valueTag The modifications.

[0100] ta-CommonDriftVariant This field indicates the drift rate variation of the common drift variable (TA). The granularity of ta-CommonDriftVariation is 0.2 × 10^(-4) μs / s^2. Values ​​are given in units corresponding to the granularity. This field is excluded when determining changes in system information (e.g., ta-CommonDriftVariant The change should neither cause a system information change notification nor affect the SIB1. valueTag (Modifications).

[0101] ta-Report The field indicates (when included in SIB19) that advance timing reporting is enabled during random access caused by RRC connection establishment or restoration, and during RRC connection re-establishment. This is also true when the field is included in dedicated signaling. ServingCellConfigCommon In the meantime, it indicates that the TA report is enabled during random access due to reconfiguration with synchronization.

[0102] In the NR NTN transparent payload architecture, the UE pre-compensates for bidirectional transmission delays on the serving link based on its TA calculation, which is determined by the UE using the serving satellite location and its own location. It is assumed that the NR NTN UE has GNSS capability and uses GNSS to calculate its own location. However, GNSS is susceptible to spoofing and interference, which can lead to temporary unavailability of GNSS location, ultimately resulting in service rejection for the UE, even in connected mode, as the UE may need to calculate TA multiple times due to GNSS satellite movement. To improve the robustness of the NTN system, TA calculation can be enhanced during the duration of these temporary GNSS outages, particularly for UEs in idle or connected mode.

[0103] The network is expected to know in advance of temporary GNSS service unavailability or GNSS location accuracy falling below a certain threshold (this could lead to incorrect TA calculations and potentially service degradation or even service rejection). The techniques discussed in this paper describe the configuration and reporting mechanisms between NG-RAN nodes and UEs, or even some information exchange between NG-RAN nodes and the core network (e.g., LMF). Signaling methods used to determine GNSS outages and corresponding indications and related parameters are discussed, enabling the network to determine which solutions can be applied for time and frequency compensation when GNSS is unavailable.

[0104] After the network becomes aware of a temporary GNSS outage or that the UE's GNSS positioning accuracy has decreased (due to any factor), the network uses signaling mechanisms to calculate the TA (Target Availability) so that, at least for connected UEs, there is no service denial or service degradation is minimal (e.g., minimal).

[0105] In one or more implementations, the UE explicitly or implicitly indicates to the network the unavailability or interruption of GNSS (or inaccurate location information) in at least one of the connected or idle states, wherein the indication may be initiated based on an explicit request configuration message made by the network, or based on an implicit indication made by the network (e.g., a pre-configuration criterion set by the network for initiating the indication), or the UE may decide to initiate a signaling message autonomously.

[0106] Regarding the configuration and reporting of network assistance or control for GNSS outages, in one or more implementations, the network explicitly indicates (e.g., via UE-specific or broadcast signaling) to one or a group of UEs to indicate their GNSS status (with or without their GNSS location information), wherein the network configures parameters for initiating their GNSS status to the UE using higher-layer signaling or dedicated signaling or using group common signaling or a combination thereof. This configuration may include a set of parameters to be reported so that the network determines or may predict the GNSS location accuracy or GNSS signal outage probability for one or more GNSS systems, wherein the set of parameters may include one or more of the following: GNSS constellation ID (e.g., GPS, GALILEO, GLONASS, etc.), the number of GNSS satellites in the field of view, location accuracy, or GNSS signal measurements (e.g., Reference Signal Received Power (RSRP), Doppler, code phase, etc.).

[0107] In one or more implementations, the above configuration parameters can be IE LocationInfo Part of IE LocationInfo It can be used to transmit available detailed location information (including GNSS location information) and provide available measurement results at the UE.

[0108] In one or more implementations, the network also configures the periodicity of reporting GNSS status to the UE based on request messages, where the reporting can be set to periodic, non-periodic, or semi-persistent.

[0109] In one or more implementations, the network may additionally schedule resources for reporting GNSS status, on which the UE will send reports based on a configured reporting periodicity. The UE may include a set of parameters configured in its reports. The UE may include additional aspects such as the rate of change of its location (indicating how fast the UE moves or remains stationary for a period of time).

[0110] In one or more implementations, the network configures the UE to report GNSS outage indications, where a GNSS outage can be defined as "when the UE has no or has not found any GNSS connectivity, or when there is no minimum required number of satellites in the field of view." This can be part of the GNSS state configuration, or a separate configuration can be used for this purpose. The network can additionally allocate resources (e.g., using higher-layer signaling) for reporting GNSS outages in a periodic, non-periodic, or semi-persistent manner. The network can set the reporting frequency based on its current or prior knowledge (e.g., UE RSRP, UE's previous location in the area, last timing adjustment) or based on its initial GNSS state report. In one example, the UE can send reports for GNSS outages periodically as configured, where the report can include only an indication of whether the UE has experienced an outage (e.g., using unit flags where 1 and 0 indicate yes or no, respectively). Additionally or alternatively, the UE can send a report once when it experiences a GNSS outage event. In one example, the UE can perform this report using dedicated signaling, such as via a field in the UCI.

[0111] In one or more implementations, the network configures the UE to report when the GNSS position accuracy reaches below a certain threshold (which can be set by the network), where the network uses high-layer signaling or dedicated signaling to configure the relevant threshold parameters. For example, the UE can be configured via RRC signaling with GNSS accuracy threshold parameters. The GNSS position accuracy can correspond to one or both of the horizontal or vertical position accuracy and the confidence value, where the horizontal accuracy indicates the maximum horizontal error in the position estimate at the indicated confidence level. 'Accuracy' corresponds to the encoded uncertainty, and the horizontal confidence is the confidence (e.g., expressed as a percentage) that the horizontal position of the target entity is within its known shape description, directly mapped from the 7-bit binary number K, but K = 0 is used to indicate 'no information', and 100 < K ≤ 128 need not be used but can be interpreted as "no information" if received. The above similar definitions extend to the vertical accuracy and vertical confidence definitions. The UE can continue to measure the GNSS position while performing NR-NTN operations. The UE can report to the network only when the accuracy drops below a predefined threshold, which can apply to the horizontal accuracy, vertical accuracy, or both.

[0112] Additionally or alternatively, the UE can report integrity-related parameters of the associated position estimate calculated using GNSS to an NE (e.g., gNB) via an RRC message. The integrity of the GNSS position estimate is a measure of trust in the calculated GNSS position estimate. This includes the horizontal protection level (HPL), vertical protection level (VPL), and the achievable target integrity risk (TIR). The HPL provides the HPL for the GNSS position estimate along the semi-major axis of the error ellipse, with a scale factor resolution of 0.01 m and a range of 0 m to 500 m. The VPL for the GNSS position estimate is provided, with a scale factor resolution of 0.01 m and a range of 0 m - 500 m. The achievable TIR indicates the achievable TIR for which the HPL and VPL are provided. According to P = 10 -0.1n [hour -1 , the achievable TIR is given by the probability of occurrence, where n is the value, and the range is 10 per hour -1 to 10 -9 .

[0113] In one or more implementations, a GNSS outage or inaccurate GNSS location means that GNSS is unavailable (or its location is inaccurate) for a low (e.g., minimum) duration, where the duration defining the GNSS outage can be configured by the network using higher-layer signaling or dedicated signaling (e.g., MAC-CE or DCI), or the UE can define the duration itself (e.g., based on historical data). For example, the low (e.g., minimum) duration is defined by the network for GNSS outages or inaccurate location estimates. If GNSS is unavailable during this duration, the UE will not immediately report the GNSS outage; instead, the UE can continue acquiring GNSS location within this predefined minimum duration. If the UE is unable to acquire GNSS location at all within this duration (e.g., predefined by the network), the UE can only notify the network that an outage has occurred and can also indicate the expected outage duration or measurement duration during which GNSS is unavailable. Similarly, if the GNSS accuracy is below a set threshold, the UE will repeatedly acquire GNSS location estimates within the defined duration, and if the accuracy remains below the threshold, the UE can notify the network of the inaccurate GNSS location.

[0114] Figure 4 Example 400 of a signaling flow for indicating a GNSS outage according to aspects of this disclosure is illustrated. The gNB sends a GNSS status configuration to the UE, which receives the GNSS status configuration and reports back the set of parameters in the configuration. The network sends a GNSS outage or accuracy configuration set based on the reporting period of the status reports received from the UE. The UE receives the GNSS outage configuration and sends outage or inaccuracy reports at the configured periodicity. The network initiates alternative time and frequency compensation mechanisms to respond to GNSS outages.

[0115] Figure 5 Example 500 of a signaling flow for indicating a GNSS outage according to aspects of this disclosure is illustrated. The gNB sends a GNSS status configuration to the UE. The UE receives the GNSS status configuration and reports back the set of parameters in that configuration. This status report is received by the gNB. The UE initiates an outage or inaccurate report either periodically as pre-configured or when the UE experiences an outage or inaccurate location estimation. The network receives the outage report and initiates alternative time and frequency compensation mechanisms to respond to the GNSS outage.

[0116] In one or more implementations, information regarding one or more of the UE's GNSS health or status is exchanged between the NG-RAN node (e.g., gNB) and the core network (e.g., LMF) based on the GNSS list. The GNSS health or status indicates the current health of the satellites, which may or may not be satellite-specific; for example, different health status indications may be used for different constellations such as GPS, Galileo, Baidu, etc. The health of each satellite band can also be further indicated based on each GNSS, for example, for L1, L2, and / or L5 bands. In one example, the gNB may use NRPPa request and response messages to request the UE's GNSS status from the LMF, where this information may include information such as the GNSS constellation ID or indications of GNSS signal measurements or areas where the UE may experience GNSS outages.

[0117] In one or more implementations, Operations and Maintenance (O&M) can provide the gNB with GNSS coverage information specific to certain areas, as well as ephemeris information for serving satellites. GNSS coverage information can be useful for the gNB in ​​determining the probability of GNSS outages or low positioning accuracy due to poor GNSS coverage. For example, if the gNB knows an area with low GNSS coverage and also determines the UE's location (e.g., " locationinfo IE If the network can predict the frequency of outages and service degradations caused by poor time and frequency synchronization due to low or inaccurate GNSS locations, it can therefore apply robust alternative techniques to address the impact (e.g., previously known UE locations, using RTT measurements, etc.).

[0118] In one or more implementations, the Timing Advance Report (TAR) procedure is extended to provide the network not only with information about an estimate of the timing advance value of the UE, but also with information about one or both of GNSS outages and GNSS status (e.g., GNSS health). In one example, the GNSS status in the TAR is triggered by " TAR-Config-r17 Additional RRC parameters in the configuration can be configured. New parameters can specify what information is needed in the TAR, such as one or both of GNSS status or interruption. Alternatively, the UE can always include information about GNSS status and TA information in the TAR. Alternatively, multiple specific timing advance values ​​can be used to signal that GNSS-based location accuracy is below multiple specific thresholds. Alternatively, one of the reserved bits can be used to signal that the timing advance field contains an indication of GNSS-based location accuracy. Alternatively, the R bits can be used as follows:

[0119] In one or more implementations, a TAR can be triggered based on the occurrence of a GNSS event (e.g., when the UE experiences a GNSS outage or poor GNSS health). For example, a TAR can be triggered if any of the following events occur, and the TAR includes the GNSS status or outage: - When an instruction from the upper layer triggers a timed advance report or an indication of GNSS status and / or GNSS interruption; - Configured by the upper layer offsetThresholdTA Subsequently, if the UE has not previously reported the timing advance value to the current serving cell; - If the change between the current estimate of the timing advance value and the previously reported timing advance value is equal to or greater than... offsetThresholdTA (If configured); - When configuring parameters at the upper layer due to changes in GNSS health or GNSS interruption.

[0120] In one or more implementations, the network configuration used for reporting by the UE includes the expected validity of available auxiliary information for the UE to obtain its UE-specific TA. Thus, UE reporting may or may not include GNSS validity or accuracy, but may include the UE's expected requirement for one or both of the additional TA procedure or auxiliary information.

[0121] In one or more implementations, upon indication of a GNSS outage or duration of availability, the network also configures the UE to report additional RAT-independent positioning information (e.g., UE altitude or motion information). In some examples, the IE... Sensor- ProvideLocationInformation All or a subset of the information elements (defined for LTE Location Protocol (LPP) IE transmissions from the UE) are utilized in the report to the gNB. In one example, the network utilizes the received... Sensor- ProvideLocationInformation The IE is used to estimate the validity of the current UE location and the validity of the current UE assistance information used for the calculation of UE-specific TA parameters.

[0122] Regarding UE control reporting for GNSS interruption or effectiveness, in one or more implementations, the UE determines the duration of its GNSS effectiveness and reports this duration back to the network using higher-layer signaling or dedicated signaling. This effectiveness duration may be specified in part based on one or both of satellite movement or UE movement during which the UE expects to be in good GNSS coverage conditions. In one example, the GNSS effectiveness duration parameter is reported to the network during initial access and is part of the RACH procedure (e.g., in a 4-step RACH procedure, this may be reported in Msg1, or in a 2-step RACH procedure, this may be reported in MsgA). In another example, the UE may send the GNSS effectiveness duration whenever it calculates a user-specific TA.

[0123] Additionally or alternatively, the UE indicates to the network the expected duration of the validity of its location information or the expected time for the UE to require additional support to obtain UE-specific TA (e.g., the duration in which the UE anticipates obtaining UE-specific TA parameters based on available GNSS measurements without additional network assistance).

[0124] In one or more implementations, the GNSS validity duration parameter is reported by the UE based on a request or indication from the network. For example, the GNSS validity duration may be triggered by an event (e.g., an indication in the TAR). In one example, the network reports the GNSS validity duration in " TAR-Config-r17 A new parameter has been introduced in (which is used to configure advance reporting in NTN) to specify the duration of GNSS validity that will be reported. When enabled, the UE expects to report the duration of GNSS validity in its reports. Additionally or alternatively, the duration of GNSS validity can be part of the TAR whenever a TAR event is triggered.

[0125] Figure 6 The illustration shows an example IE 600 according to an aspect of this disclosure. IE 600 is a TAR-Config IE that includes the GNSS validity duration parameter in the field "GNSSvalidityduration-r19".

[0126] In one or more implementations, the periodicity of the reported GNSS validity duration is configured by the network (e.g., periodic, non-periodic, or semi-persistent).

[0127] In one or more implementations, if a GNSS outage occurs during the GNSS validity period, the UE initiates a new report regarding the GNSS outage or GNSS invalidity, which can be done using higher-level signaling or dedicated signaling. For example, the UE may have reported approximately 10 minutes of GNSS validity, indicating that it is likely to experience good GNSS health (e.g., accurate GNSS positioning) for the next 10 minutes, or that the reported location estimate is valid for the next 10 minutes. During this duration, the UE can continue to monitor its GNSS health / location while performing NR NTN operations. However, if the UE experiences a GNSS outage or persistent inaccurate location estimates for a specific duration, or if the accuracy is less than a predefined threshold during the validity period—for example, after 5 minutes—the UE will generate a new report indicating to the network that the GNSS validity period is no longer valid or that a GNSS outage has occurred. In another implementation, the UE may also trigger a request to the LMF for such GNSS outage or validity information.

[0128] In one or more implementations, the reported GNSS validity duration is coupled to the UL synchronization validity duration, which is configured by the network for auxiliary information (e.g., one or both of serving or neighboring satellite ephemeris and common TA parameters) and indicates the high (e.g., maximum) duration (from epoch time) during which the UE can apply auxiliary information without having acquired new auxiliary information. If the GNSS validity duration is less than a threshold of the UL synchronization validity duration, the UE may only report the GNSS validity duration. For example, for each UL synchronization validity duration configured by the network, the UE will check its GNSS validity duration, and whenever it is less than the UL synchronization duration, a GNSS validity duration reporting event may be triggered by the UE.

[0129] In one or more implementations, whenever such an event occurs, either based on network configuration or indication, or a combination thereof, the UE autonomously generates a GNSS outage or GNSS inaccurate positioning report. A GNSS outage report may include at least one of the following parameters: • GNSS interruption timestamp (e.g., the time when the UE experienced a GNSS interruption) • Last GNSS coordinates (e.g., which can help the network understand the duration of information exchanged between NG-RAN nodes and the core network or via other means). • Final GNSS Measurements • Expected GNSS outage duration (e.g., if the UE can estimate the expected duration of the GNSS signal outage based on its prior knowledge) • The rate at which its location changes (e.g., how quickly the UE changes its location so that the network knows whether the last known location can be used). • GNSS accuracy (e.g., how much accuracy has decreased if it has fallen below a threshold due to poor link budget or clock mismatch). • GNSS Constellation ID • Number of visible GNSS satellites

[0130] In one or more implementations, the UE can also indicate to the network whenever one of the reported parameters in a GNSS outage report changes or is updated, by initiating a new report.

[0131] In one or more implementations, UE indication or reporting of GNSS status includes, for example, in IE GNSS- LocationServerErrorCause Similar information elements or portions thereof as defined in the information element. In one example, the report is directed to the LMF or AMF, and the LMF or AMF may notify the gNB of at least one of the acquired IE, GNSS validity status, or the need for an additional TA procedure for the UE.

[0132] Figure 7 An example of IE 700 according to aspects of this disclosure is illustrated. IE 700 is... GNSS- LocationServerErrorCause IE.

[0133] In one or more implementations, the UE report includes a request for additional auxiliary information for UE-specific TA information, and an indication of the type of auxiliary information required (e.g., the elements described above). In one example, the UE indicates a request for additional TA adjustment to the network via UL Reference Signal (RS) transmission and DL TA feedback (e.g., Msg 1 and Msg 2 of the NR initial access procedure). In one or more implementations, the request includes an indication of the reason (e.g., GNSS failure or status, etc.).

[0134] Figure 8 An example of a UE 800 according to aspects of this disclosure is illustrated. UE 800 may include a processor 802, a memory 804, a controller 806, and a transceiver 808. The processor 802, memory 804, controller 806, or transceiver 808, or various combinations thereof, or various components thereof, may be examples of parts for performing the aspects of this disclosure as described herein. These components may be coupled via one or more interfaces (e.g., operational ground, communication ground, functional ground, electronic ground, electrical ground).

[0135] Processor 802, memory 804, controller 806, or transceiver 808, or various combinations or components thereof, may be implemented in hardware (e.g., a circuit system). The hardware may include a processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof, configured or otherwise supporting components for performing the functions described in this disclosure.

[0136] Processor 802 may include intelligent hardware devices (e.g., a general-purpose processor, DSP, CPU, ASIC, FPGA, or any combination thereof). In some implementations, processor 802 may be configured to operate memory 804. In some other implementations, memory 804 may be integrated into processor 802. Processor 802 may be configured to execute computer-readable instructions stored in memory 804 to cause UE 800 to perform various functions of this disclosure.

[0137] Memory 804 may include volatile or non-volatile memory. Memory 804 may store computer-readable, computer-executable code, including instructions that, when executed by processor 802, cause UE 800 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as memory 804 or another type of memory. Computer-readable media include both non-transitory computer storage media and communication media, including any medium that facilitates the transfer of computer programs from one place to another. Non-transitory storage media may be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0138] In some implementations, processor 802 and memory 804 coupled to processor 802 may be configured to cause UE 800 to perform one or more functions described herein (e.g., instructions stored in memory 804 are executed by processor 802). For example, processor 802 may support wireless communication at UE 800, according to examples disclosed herein. UE 800 may be configured to support components for: acquiring one or more GNSS parameter values ​​based at least in part on a configuration including one or more GNSS parameters related to GNSS availability; and sending first signaling to NE indicating one or more GNSS parameter values ​​based at least in part on one or more GNSS parameters related to GNSS availability.

[0139] Additionally, UE 800 may be configured to support any one or a combination of the following: further comprising receiving a second signaling from the NE, the second signaling indicating a configuration including one or more GNSS parameters related to GNSS availability; wherein the configuration applies to the UE when the UE is in a connected or idle state; wherein one or more GNSS parameter values ​​indicate a GNSS outage; wherein a GNSS outage corresponds to a period of no GNSS connection or the number of GNSS satellites in the UE's field of view being less than a threshold number of GNSS satellites; wherein one or more GNSS parameter values ​​indicate GNSS inaccuracy; wherein one or more GNSS parameters include at least a position accuracy threshold parameter; wherein GNSS inaccuracy is defined when G... GNSS position estimation when GNSS accuracy is below a GNSS position accuracy threshold; one or more GNSS parameters indicate the minimum duration for GNSS outage or GNSS position inaccuracy; one or more GNSS parameter values ​​include at least one of GNSS constellation ID, position accuracy, number of GNSS satellites in the UE's field of view, or GNSS signal measurements; one or more GNSS parameters include parameters defining the measurement period; one or more GNSS parameter values ​​include at least one of the following: GNSS outage timestamp; last GNSS coordinates; last GNSS measurement; expected GNSS outage duration; rate of change of satellite position; GN GNSS accuracy; GNSS constellation ID; or the number of GNSS satellites within the UE's field of view; in response to a change in one or more GNSS parameter values, sending a second signaling to the NE indicating one or more updated GNSS parameter values, at least in part based on one or more GNSS parameters; wherein the first signaling indicates a request for TA adjustment; wherein the configuration includes criteria for determining the request for TA adjustment from the NE; receiving the second signaling from the NE, the second signaling indicating a reporting configuration for the transmission of one or more GNSS parameter values; and sending the first signaling to the NE, at least in part based on the reporting configuration; wherein the reporting configuration includes one or more of the following: for one or more GNSS parameter values. The first signaling includes a set of timing opportunities for the transmission of GNSS parameter values, a set of time-frequency resources for the transmission of one or more GNSS parameter values, or at least one criterion for the transmission of one or more GNSS parameter values; wherein the first signaling includes reporting one or both of GNSS health or GNSS interruption in a timing advance report; wherein the first signaling includes a parameter indicating the duration of validity of the reported GNSS position estimate; wherein the validity duration defines a time during which the GNSS position estimate is valid or the UE experiences good GNSS signal strength; GNSS measurements are performed during the GNSS validity duration; and an indication of a GNSS interruption during the GNSS validity duration is included in the first signaling.

[0140] Additionally or alternatively, the UE 800 may support: obtaining one or more GNSS parameter values ​​based at least in part on a configuration including one or more GNSS parameters related to GNSS availability; and sending a first signaling indicating one or more GNSS parameter values ​​to the NE based at least in part on one or more GNSS parameters related to GNSS availability.

[0141] Additionally, UE 800 can be configured to support any one or a combination of the following: receiving a second signaling from NE indicating a configuration including one or more GNSS parameters related to GNSS availability; wherein the configuration applies to the UE when the UE is in a connected or idle state; wherein one or more GNSS parameter values ​​indicate a GNSS outage; wherein a GNSS outage corresponds to a period of no GNSS connection or the number of GNSS satellites in the UE's field of view is less than a threshold number of GNSS satellites; wherein one or more GNSS parameter values ​​indicate GNSS inaccuracy; wherein one or more GNSS parameters include at least a position accuracy threshold parameter; wherein GNSS inaccuracy is defined when the GNSS... GNSS position estimation when the GNSS accuracy at position S is below the GNSS position accuracy threshold; one or more GNSS parameters indicate the minimum duration for GNSS outage or GNSS position inaccuracy; one or more GNSS parameter values ​​include at least one of GNSS constellation ID, position accuracy, number of GNSS satellites in the UE's field of view, or GNSS signal measurement; one or more GNSS parameters include parameters defining the measurement period; one or more GNSS parameter values ​​include at least one of the following: GNSS outage timestamp; last GNSS coordinates; last GNSS measurement; expected GNSS outage duration; rate of change of satellite position; GNS S accuracy; GNSS constellation ID; or the number of GNSS satellites within the UE's field of view; in response to a change in one or more GNSS parameter values, sending a second signaling to the NE indicating one or more updated GNSS parameter values, at least in part based on one or more GNSS parameters; wherein the first signaling indicates a request for TA adjustment; wherein the configuration includes criteria for determining the request for TA adjustment from the NE; receiving the second signaling from the NE, the second signaling indicating a reporting configuration for the transmission of one or more GNSS parameter values; and sending the first signaling to the NE, at least in part based on the reporting configuration; wherein the reporting configuration includes one or more of the following: for one or more GNSS parameter values. The first signaling includes a set of timing opportunities for the transmission of GNSS parameter values, a set of time-frequency resources for the transmission of one or more GNSS parameter values, or at least one criterion for the transmission of one or more GNSS parameter values; wherein the first signaling includes reporting one or both of GNSS health or GNSS interruption in a timing advance report; wherein the first signaling includes a parameter indicating the duration of validity of the reported GNSS position estimate; wherein the validity duration defines a time during which the GNSS position estimate is valid or the UE experiences good GNSS signal strength; GNSS measurements are performed during the GNSS validity duration; and an indication of a GNSS interruption during the GNSS validity duration is included in the first signaling.

[0142] Controller 806 can manage input and output signals for UE 800. Controller 806 can also manage peripheral devices not integrated into UE 800. In some implementations, controller 806 can utilize an operating system, such as iOS®, Android®, Windows®, or other operating systems. In some implementations, controller 806 can be implemented as part of processor 802.

[0143] In some implementations, UE 800 may include at least one transceiver 808. In other implementations, UE 800 may have more than one transceiver 808. Transceiver 808 may represent a wireless transceiver. Transceiver 808 may include one or more receiver chains 810, one or more transmitter chains 812, or a combination thereof.

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

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

[0146] Figure 9An example of a processor 900 according to aspects of this disclosure is illustrated. Processor 900 may be an example of a processor configured to perform various operations according to examples described herein. Processor 900 may include a controller 902 configured to perform various operations according to examples described herein. Processor 900 may optionally include at least one memory 904, which may be, for example, an L1 / L2 / L3 cache. Additionally or alternatively, processor 900 may optionally include one or more arithmetic logic units (ALUs) 906. One or more of these components may be electronically communicated or otherwise coupled (e.g., operative ground, communicative ground, functional ground, electronic ground, electrical ground) via one or more interfaces (e.g., buses).

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

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

[0149] Controller 902 can be configured to fetch (e.g., fetch, retrieve, receive) instructions from memory 904 and determine subsequent instructions(s) to be executed, such that processor 900 supports various operations according to the examples described herein. Controller 902 can be configured to track the memory addresses of instructions associated with memory 904. Controller 902 can be configured to decode instructions to determine the operations to be performed and the operands involved. For example, controller 902 can be configured to interpret instructions and determine control signals to be output to other components of processor 900, such that processor 900 supports various operations according to the examples described herein. Additionally or alternatively, controller 902 can be configured to manage data flow within processor 900. Controller 902 can be configured to control data transfers between registers, ALU 906, and other functional units of processor 900.

[0150] Memory 904 may include one or more caches (e.g., memory or other memory, such as RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc., local to or included in processor 900). In some implementations, memory 904 may reside within or on the processor chipset (e.g., local to processor 900). In some other implementations, memory 904 may reside outside the processor chipset (e.g., remotely to processor 900).

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

[0152] One or more ALU 906s can be configured to support a variety of operations, as illustrated in the examples described herein. In some implementations, one or more ALU 906s may reside within or on a processor chipset (e.g., processor 900). In some other implementations, one or more ALU 906s may reside outside the processor chipset (e.g., processor 900). One or more ALU 906s can perform one or more computations (such as addition, subtraction, multiplication, and division) on data. For example, one or more ALU 906s can receive input operands and an opcode that determines the operation to be performed. One or more ALU 906s can be configured with a variety of logic and arithmetic circuitry, including adders, subtractors, shifters, and logic gates, to process and manipulate data according to the operations. Additionally or alternatively, one or more ALU 906s may support logical operations (such as AND, OR, XOR, NOR, and NAND), enabling one or more ALU 906s to handle conditional operations, comparisons, and bitwise operations.

[0153] Processor 900 may support wireless communication according to examples disclosed herein. Processor 900 may be configured or operable to: acquire one or more GNSS parameter values ​​based at least in part on a configuration including one or more GNSS parameters related to GNSS availability; and send first signaling to the NE indicating one or more GNSS parameter values ​​based at least in part on one or more GNSS parameters related to GNSS availability.

[0154] Additionally, the processor 900 may be configured to support any one or a combination of the following: receiving a second signaling from the NE, the second signaling indicating a configuration including one or more GNSS parameters related to GNSS availability; wherein the configuration applies to the UE including the processor when the UE is in a connected or idle state; wherein one or more GNSS parameter values ​​indicate a GNSS interruption; wherein a GNSS interruption corresponds to a period of no GNSS connection or the number of GNSS satellites in the UE's field of view is less than a threshold number of GNSS satellites; wherein one or more GNSS parameter values ​​indicate inaccurate GNSS positioning; wherein one or more GNSS parameters include at least a position accuracy threshold parameter; wherein GNSS... GNSS position inaccuracy is defined as the GNSS position estimation when the GNSS accuracy of the GNSS position is below a GNSS position accuracy threshold; one or more GNSS parameters indicate the minimum duration for GNSS outage or GNSS position inaccuracy; one or more GNSS parameter values ​​include at least one of the following: GNSS constellation ID, position accuracy, the number of GNSS satellites in the UE including the processor, or GNSS signal measurements; one or more GNSS parameters include parameters defining the measurement period; and one or more GNSS parameter values ​​include at least one of the following: GNSS outage timestamp; last GNSS coordinates; last GNSS measurement; expected GNSS position. S-interruption duration; rate of change of satellite position; GNSS accuracy; GNSS constellation ID; or, given the number of GNSS satellites in a UE including at least one processor; in response to a change in one or more GNSS parameter values, sending a second signaling to the NE indicating one or more updated GNSS parameter values, at least in part based on one or more GNSS parameters; wherein the first signaling indicates a request for TA adjustment; wherein the configuration includes criteria for determining the request for TA adjustment from the NE; receiving the second signaling from the NE, the second signaling indicating a reporting configuration for the transmission of one or more GNSS parameter values; and sending the first signaling to the NE, at least in part based on the reporting configuration. The report configuration includes one or more of the following: a set of timing opportunities for the transmission of one or more GNSS parameter values, a set of time-frequency resources for the transmission of one or more GNSS parameter values, or at least one criterion for the transmission of one or more GNSS parameter values; wherein the first signaling includes reporting one or both of GNSS health or GNSS outage in the timing advance report; wherein the first signaling includes a parameter indicating the duration of validity of the reported GNSS position estimate; wherein the validity duration defines a time during which the GNSS position estimate is valid or the UE including the processor experiences good GNSS signal strength; GNSS measurements are performed during the GNSS validity duration;Indications for GNSS interruptions during the duration of GNSS availability are included in the first signaling.

[0155] Figure 10 An example of an NE 1000 according to aspects of this disclosure is illustrated. The NE 1000 may include a processor 1002, a memory 1004, a controller 1006, and a transceiver 1008. The processor 1002, memory 1004, controller 1006, or transceiver 1008, or various combinations thereof, or various components thereof, may be examples of parts for performing the aspects of this disclosure as described herein. These components may be coupled via one or more interfaces (e.g., operational ground, communication ground, functional ground, electronic ground, electrical ground).

[0156] Processor 1002, memory 1004, controller 1006, or transceiver 1008, or various combinations or components thereof, may be implemented in hardware (e.g., a circuit system). The hardware may include a processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof, configured or otherwise supporting components for performing the functions described in this disclosure.

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

[0158] Memory 1004 may include volatile or non-volatile memory. Memory 1004 may store computer-readable, computer-executable code, including instructions that, when executed by processor 1002, cause NE 1000 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as memory 1004 or another type of memory. Computer-readable media include both non-transitory computer storage media and communication media, including any medium that facilitates the transfer of computer programs from one place to another. Non-transitory storage media may be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0159] In some implementations, processor 1002 and memory 1004 coupled to processor 1002 may be configured such that NE 1000 performs one or more of the functions described herein (e.g., instructions stored in memory 1004 are executed by processor 1002). For example, processor 1002 may support wireless communication at NE 1000 according to examples disclosed herein. NE 1000 may be configured to support components for: sending a first signaling message to a network entity indicating a request message including information about the GNSS state of the UE; and receiving a second signaling message from the network entity indicating a response message including one or more parameters defining the GNSS state of the UE.

[0160] Additionally, the NE 1000 can be configured to support any one or a combination of the following: where the network entity includes an LMF; where one or more parameters defining the GNSS status include at least one of GNSS health, GNSS coverage area, or GNSS frequency band; and receive response messages from operation and management functions.

[0161] The NE 1000 can be configured to support a component for receiving first signaling from the UE, indicating the values ​​of one or more GNSS parameters, based at least in part on a configuration that includes one or more GNSS parameters related to GNSS availability.

[0162] Additionally, the NE 1000 can be configured to support any one or a combination of the following: sending a second signaling to the UE indicating the configuration of one or more GNSS parameters related to GNSS availability; wherein the configuration applies to the UE when the UE is in a connected or idle state; wherein one or more GNSS parameter values ​​indicate a GNSS outage; wherein a GNSS outage corresponds to a period of no GNSS connection or the number of GNSS satellites in the UE's field of view is less than a threshold number of GNSS satellites; wherein one or more GNSS parameter values ​​indicate GNSS position inaccuracy; wherein one or more GNSS parameters include at least a position accuracy threshold parameter; wherein GNSS position inaccuracy is defined when the GNSS position is inaccurate. GNSS position estimation when the GNSS accuracy is below a GNSS position accuracy threshold; one or more GNSS parameters indicate a minimum duration during which GNSS is interrupted or the GNSS position is inaccurate; one or more GNSS parameter values ​​include at least one of the following: GNSS constellation ID, position accuracy, number of GNSS satellites in the UE's field of view, or GNSS signal measurement; one or more GNSS parameters include parameters defining the measurement period, and a first signaling indicating the GNSS parameter value is sent; one or more GNSS parameter values ​​include at least one of the following: GNSS interruption timestamp; last GNSS coordinates; last GNSS measurement. ; expected GNSS outage duration; rate of change of satellite position; GNSS accuracy; GNSS constellation ID; or the number of GNSS satellites within the UE's field of view; receiving from the UE, at least in part, a second signaling indicating one or more updated GNSS parameter values ​​in response to a change in one or more GNSS parameter values; wherein the first signaling indicates a request for TA adjustment; wherein the configuration includes criteria for determining the request for TA adjustment from the base station; sending the second signaling to the UE, the second signaling indicating a reporting configuration for the transmission of one or more GNSS parameter values; and receiving the first signaling from the UE, at least in part, based on the reporting configuration; wherein The report configuration includes one or more of the following: a set of timing opportunities for the transmission of one or more GNSS parameter values, a set of time-frequency resources for the transmission of one or more GNSS parameter values, or at least one criterion for the transmission of one or more GNSS parameter values; wherein the first signaling includes reporting one or both of GNSS health or GNSS outage in the timing advance report; wherein the first signaling includes a parameter indicating the duration of validity of the reported GNSS position estimate; wherein the validity duration defines a time during which the GNSS position estimate is valid or the UE experiences good GNSS signal strength; wherein the first signaling includes an indication of a GNSS outage during the GNSS validity duration.

[0163] Additionally or alternatively, the NE 1000 may support: sending a first signaling message to a network entity, the first signaling message indicating a request message including information about the GNSS status of the UE; and receiving a second signaling message from a network entity, the second signaling message indicating a response message including one or more parameters defining the GNSS status of the UE.

[0164] Additionally, the NE 1000 can be configured to support any one or a combination of the following: wherein the network entity includes an LMF; wherein one or more parameters defining the GNSS status include at least one of GNSS health, GNSS coverage area, or GNSS frequency band; and receive response messages from operation and management functions.

[0165] Additionally or alternatively, the NE 1000 may support receiving, at least in part, first signaling from the UE indicating the values ​​of one or more GNSS parameters based on a configuration including one or more GNSS parameters related to GNSS availability.

[0166] Additionally, the NE 1000 can be configured to support any one or a combination of the following: sending a second signaling to the UE indicating the configuration of one or more GNSS parameters related to GNSS availability; wherein the configuration applies to the UE when the UE is in a connected or idle state; wherein one or more GNSS parameter values ​​indicate a GNSS outage; wherein a GNSS outage corresponds to a period of no GNSS connection or the number of GNSS satellites in the UE's field of view is less than a threshold number of GNSS satellites; wherein one or more GNSS parameter values ​​indicate GNSS inaccuracy; wherein one or more GNSS parameters include at least a position accuracy threshold parameter; wherein GNSS inaccuracy is defined when GNSS... GNSS position estimation when the GNSS accuracy of the GNSS position is below a GNSS position accuracy threshold; one or more GNSS parameters indicate the minimum duration for GNSS outage or GNSS position inaccuracy; one or more GNSS parameter values ​​include at least one of the following: GNSS constellation ID, position accuracy, number of GNSS satellites in the UE's field of view, or GNSS signal measurement; one or more GNSS parameters include parameters defining the measurement period, and a first signaling indicating the GNSS parameter value is sent; one or more GNSS parameter values ​​include at least one of the following: GNSS outage timestamp; last GNSS coordinates; last GNSS measurement; expected GNSS outage duration; rate of change of satellite position; GNSS accuracy; GNSS constellation ID; or the number of GNSS satellites within the UE's field of view; receiving from the UE, at least in part, a second signaling indicating one or more updated GNSS parameter values ​​in response to a change in one or more GNSS parameter values; wherein the first signaling indicates a request for TA adjustment; wherein the configuration includes criteria for determining the request for TA adjustment from the base station; sending the second signaling to the UE, the second signaling indicating a reporting configuration for the transmission of one or more GNSS parameter values; and receiving the first signaling from the UE, at least in part, based on the reporting configuration; wherein The report configuration includes one or more of the following: a set of timing opportunities for the transmission of one or more GNSS parameter values, a set of time-frequency resources for the transmission of one or more GNSS parameter values, or at least one criterion for the transmission of one or more GNSS parameter values; wherein the first signaling includes reporting one or both of GNSS health or GNSS outage in the timing advance report; wherein the first signaling includes a parameter indicating the duration of validity of the reported GNSS position estimate; wherein the validity duration defines a time during which the GNSS position estimate is valid or the UE experiences good GNSS signal strength; wherein the first signaling includes an indication of a GNSS outage during the GNSS validity duration.

[0167] Controller 1006 can manage input and output signals for the NE 1000. Controller 1006 can also manage peripheral devices not integrated into the NE 1000. In some implementations, controller 1006 can utilize an operating system (such as iOS®, Android®, Windows®, or other operating systems). In some implementations, controller 1006 can be implemented as part of processor 1002.

[0168] In some implementations, the NE 1000 may include at least one transceiver 1008. In other implementations, the NE 1000 may have more than one transceiver 1008. The transceiver 1008 may represent a wireless transceiver. The transceiver 1008 may include one or more receiver chains 1010, one or more transmitter chains 1012, or a combination thereof.

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

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

[0171] Figure 11 A flowchart illustrating a method according to an aspect of this disclosure is shown. The operation of this method can be implemented by a UE as described herein. In some implementations, the UE can execute a set of instructions to control the functional elements of the UE to perform the described functions.

[0172] At 1102, the method may include: acquiring one or more GNSS parameter values ​​based at least in part on a configuration including one or more GNSS parameters related to GNSS availability. The operation at 1102 can be performed according to the examples described herein. In some implementations, aspects of the operation at 1102 may be provided by reference to [reference needed]. Figure 8 The UE execution described.

[0173] At point 1104, the method may include: sending a first signaling to the NE indicating values ​​of one or more GNSS parameters, at least in part, based on one or more GNSS parameters relating to GNSS availability. The operation at point 1104 can be performed according to examples as described herein. In some implementations, aspects of the operation at point 1104 may be provided by reference to [reference needed]. Figure 8 The UE execution described.

[0174] It should be noted that the method described in this paper describes one possible implementation, and the operations and steps can be rearranged or otherwise modified, and other implementations are possible.

[0175] Figure 12 A flowchart illustrating a method according to an aspect of this disclosure is shown. The operation of this method can be implemented by an NE as described herein. In some implementations, the NE can execute an instruction set to control the functional elements of the NE to perform the described functions.

[0176] At 1202, the method may include sending a first signaling to a network entity, the first signaling indicating a request message including information about the GNSS status for the UE. The operation at 1202 can be performed according to the examples described herein. In some implementations, aspects of the operation at 1202 may be derived from references... Figure 10 The NE is executed as described.

[0177] At 1204, the method may include: receiving a second signaling from a network entity, the second signaling indicating a response message including one or more parameters defining the GNSS state of the UE. The operation at 1204 can be performed according to the examples described herein. In some implementations, aspects of the operation at 1204 may be derived from references... Figure 10 The described NE execution.

[0178] Figure 13 A flowchart illustrating a method according to an aspect of this disclosure is shown. The operation of this method can be implemented by an NE as described herein. In some implementations, the NE can execute an instruction set to control the functional elements of the NE to perform the described functions.

[0179] At 1302, the method may include: receiving, at least in part, first signaling from the UE indicating values ​​of one or more GNSS parameters based on a configuration including one or more GNSS parameters related to GNSS availability. The operation of 1302 may be performed according to examples as described herein. In some implementations, aspects of the operation of 1302 may be provided by reference to [reference needed]. Figure 10 The described NE is executed.

[0180] It should be noted that the method described in this paper describes one possible implementation, and the operations and steps can be rearranged or otherwise modified, and other implementations are possible.

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

Claims

1. A user equipment (UE) for wireless communication, comprising: At least one memory; as well as At least one processor, coupled to the at least one memory, and configured such that the UE: One or more GNSS parameter values ​​are obtained, at least in part, based on a configuration that includes one or more GNSS parameters related to the availability of the Global Navigation Satellite System (GNSS). as well as A first signaling indicating the value of the one or more GNSS parameters is sent to the network device (NE) based at least in part on the one or more GNSS parameters related to the availability of the GNSS.

2. The UE of claim 1, wherein the at least one processor is configured to cause the UE to receive second signaling from the NE, the second signaling indicating the configuration including the one or more GNSS parameters related to the availability of the GNSS.

3. The UE according to claim 1, wherein the configuration applies to the UE when the UE is in a connected state or an idle state.

4. The UE according to claim 1, wherein the one or more GNSS parameter values ​​indicate a GNSS interruption, and wherein the GNSS interruption corresponds to a period of time without GNSS connection or the number of GNSS satellites in the field of view of the UE is less than a threshold number of GNSS satellites.

5. The UE of claim 1, wherein the one or more GNSS parameter values ​​indicate GNSS position inaccuracy, and wherein GNSS position inaccuracy is defined as GNSS position estimation when the GNSS position accuracy is below a GNSS position accuracy threshold.

6. The UE of claim 1, wherein the one or more GNSS parameters indicate the minimum duration for GNSS interruption or GNSS position inaccuracy.

7. The UE of claim 1, wherein the one or more GNSS parameter values ​​include at least one of the following: GNSS constellation identifier (ID), position accuracy, number of GNSS satellites in the field of view of the UE, or GNSS signal measurement.

8. The UE of claim 1, wherein the one or more GNSS parameters include parameters defining the measurement periodicity.

9. The UE of claim 1, wherein the one or more GNSS parameter values ​​include at least one of the following: GNSS interruption timestamp; Final GNSS coordinates; Final GNSS measurements; Expected duration of GNSS outage; The rate of change of satellite position; GNSS accuracy; GNSS constellation identifier (ID); or The number of GNSS satellites within the field of view of the UE.

10. The UE of claim 1, wherein the at least one processor is configured to cause the UE to send a second signaling indicating one or more updated GNSS parameter values ​​to the NE in response to a change in one or more GNSS parameter values, at least in part based on the one or more GNSS parameters.

11. The UE of claim 1, wherein the first signaling indicates a request for timing advance (TA) adjustment, and wherein the configuration includes criteria for determining the request for TA adjustment from the NE.

12. The UE of claim 1, wherein the at least one processor is configured such that the UE: The system receives a second signaling message from the NE, the second signaling message indicating a reporting configuration for the transmission of the one or more GNSS parameter values. The reporting configuration described herein includes one or more of the following: a set of timing opportunities for the transmission of the one or more GNSS parameter values, a set of time-frequency resources for the transmission of the one or more GNSS parameter values, or at least one criterion for the transmission of the one or more GNSS parameter values; and The first signaling is sent to the NE, at least in part based on the report configuration.

13. The UE of claim 1, wherein the first signaling comprises: Report one or both of GNSS health or GNSS outage in the scheduled advance report.

14. The UE of claim 1, wherein the first signaling includes a parameter indicating the duration of validity of the reported GNSS location estimate, wherein the duration of validity defines a time during which the GNSS location estimate is valid or the UE experiences good GNSS signal strength, and wherein the at least one processor is configured such that the UE: Perform GNSS measurements during the GNSS validity period; and The indication of a GNSS interruption during the GNSS validity period is included in the first signaling.

15. A base station for wireless communication, comprising: At least one memory; as well as At least one processor, coupled to the at least one memory, and configured such that the base station: The user equipment (UE) receives a first signaling indicating the values ​​of one or more GNSS parameters, based at least in part on a configuration including one or more GNSS parameters related to the availability of the Global Navigation Satellite System (GNSS).

16. The base station of claim 15, wherein the at least one processor is configured to cause the base station to send a second signaling to the UE, the second signaling indicating the configuration including the one or more GNSS parameters related to the availability of the GNSS.

17. A processor for wireless communication, comprising: At least one controller, coupled to at least one memory, and configured such that the processor: One or more GNSS parameter values ​​are obtained, at least in part, based on a configuration that includes one or more GNSS parameters related to the availability of the Global Navigation Satellite System (GNSS). as well as A first signaling indicating the value of the one or more GNSS parameters is sent to the network device (NE) based at least in part on the one or more GNSS parameters related to the availability of the GNSS.

18. The processor of claim 17, wherein the one or more GNSS parameter values ​​indicate a GNSS interruption.

19. A method performed by a user equipment (UE), the method comprising: One or more GNSS parameter values ​​are obtained, at least in part, based on a configuration that includes one or more GNSS parameters related to the availability of the Global Navigation Satellite System (GNSS). as well as A first signaling indicating the value of the one or more GNSS parameters is sent to the network device (NE) based at least in part on the one or more GNSS parameters related to the availability of the GNSS.

20. The method of claim 19, wherein the one or more GNSS parameter values ​​indicate that the GNSS position is inaccurate.

Images