Connection establishment based on satellite unavailability

Abstract

Various aspects of the present disclosure relate to methods, apparatuses, and devices for wireless communication. A user equipment (UE) may receive (1002), from a network entity, a configuration. The UE may determine (1004) an unavailability of a global navigation satellite system (GNSS), and calculate (1006), based on the unavailability of the GNSS, user-specific timing to perform a radio resource control (RRC) connection establishment procedure. The UE may perform (1008) the RRC connection establishment procedure according to the received configuration and based on the calculated user-specific timing.

Description

CONNECTION ESTABLISHMENT BASED ON SATELLITE UNAVAILABILITYTECHNICAL FIELD

[0001] The present disclosure relates to wireless communications, and more specifically to establishing a connection according to a connection establishment procedure and based on an availability (e.g., unavailability) of a network entity (e.g., a satellite) in a wireless communication system (e.g., a satellite communication system).BACKGROUND

[0002] A wireless communications system may include one or multiple network communication devices, which may be otherwise known network equipment (NE), supporting wireless communications for one or multiple user communication devices, which may be otherwise known as user equipment (UE), or other suitable terminology. The wireless communications system may support wireless communications with one or multiple user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers, or the like). Additionally, the wireless communications system may support wireless communications across various radio access technologies including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, among other suitable radio access technologies beyond 5G (e.g., 5G-Advanced (5G-A), sixth generation (6G)).SUMMARY

[0003] An article “a” before an element is unrestricted and understood to refer to “at least one” of those elements or “one or more” of those elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” may be interchangeable. As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of’ or “one or more of’ or “one or both 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). Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a conditionA and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on.” Further, as used herein, including in the claims, a “set” may include one or more elements.

[0004] Various aspects of the present disclosure relate to wireless communications. One or more of NE and UE may be configured to, capable of, or operable to perform the operations and signaling described herein. For example, one or more NE and UE may support managing (e.g., establishing) a connection with a terrestrial network entity (e.g., a base station) and / or a non-terrestrial network entity (e.g., a satellite) based on an unavailability of the NTN network entity. A UE may receive, from a network entity, a configuration; determine an unavailability of a global navigation satellite system (GNSS); calculate, based on the unavailability of the GNSS, UE-specific timing (also referred to as user-specific timing) to perform a connection procedure (e.g., a radio resource control (RRC) connection establishment procedure); and perform the connection procedure according to the received configuration and based on the calculated UE-specific timing.BRIEF DESCRIPTION OF THE DRAWINGS

[0005] Figure 1 illustrates an example of a wireless communications system in accordance with aspects of the present disclosure.

[0006] Figure 2 illustrates an example of a timing relationship in a wireless communications system in accordance with aspects of the present disclosure.

[0007] Figure 3 illustrates an example of a procedure for use during satellite unavailability in accordance with aspects of the present disclosure.

[0008] Figure 4 illustrates an example of communications having an idle state extension during satellite unavailability in accordance with aspects of the present disclosure.

[0009] Figure 5 illustrates an example of a procedure for using a stored location estimate for a procedure in accordance with aspects of the present disclosure.

[0010] Figure 6 illustrates an example of a system with SSB based reference location mapping in accordance with aspects of the present disclosure.

[0011] Figure 7 illustrates an example of a UE in accordance with aspects of the present disclosure.

[0012] Figure 8 illustrates an example of a processor in accordance with aspects of the present disclosure.

[0013] Figure 9 illustrates an example of a network equipment (NE) in accordance with aspects of the present disclosure.

[0014] Figure 10 illustrates a flowchart of a method performed by a UE in accordance with aspects of the present disclosure.

[0015] Figure 11 illustrates a flowchart of a method performed by a NE in accordance with aspects of the present disclosure.DETAILED DESCRIPTION

[0016] In a wireless communication system, a UE may rely on a satellite system, such as a Global Navigation Satellite System (GNSS) to determine a location of the UE and / or the GNSS and facilitate radio resource control (RRC) establishment procedures. However, there are scenarios where the GNSS might become unavailable to the UE, such as in environments with weak satellite signals or obstructions. During these periods of unavailability, the UE may repeatedly attempt to connect to the GNSS, leading to increased power consumption and reduced system performance. This inefficiency poses challenges in maintaining optimal UE operation, particularly in power-sensitive or performance-critical applications.

[0017] Various aspects of the present disclosure enable a UE to be configured to or operable to perform one or more procedures, such as one or more RRC connection establishment procedures based at least in part on GNSS unavailability. The UE may be configured with or operable to be configured with one or more configurations, according to which the UE can detect GNSS unavailability and adapt a behavior of the UE accordingly. For example, the UE may delay (e.g. refrain from) communications when the GNSS is unavailable.

[0018] By delaying communications during periods of GNSS unavailability, the UE can achieve several key benefits. Firstly, the reduction in unnecessary communication attempts significantly decreases power consumption, thereby prolonging battery life. Secondly, system performance is enhanced as the UE avoids inefficient resourceallocation during GNSS downtime. Collectively, these improvements contribute to a more efficient and reliable communication system, particularly in challenging environments where GNSS availability is inconsistent.

[0019] Aspects of the present disclosure are described in the context of a wireless communications system.

[0020] Figure 1 illustrates an example of a wireless communications system 100 in accordance with aspects of the present disclosure. The wireless communications system 100 may include one or more NE 102, one or more UE 104, and a core network (CN) 106. The wireless communications system 100 may support various radio access technologies. In some implementations, the wireless communications system 100 may be a 4G network, such as an LTE network or an LTE-Advanced (LTE-A) network. In some other implementations, the wireless communications system 100 may be a new radio (NR) network, such as a 5G network, a 5G-Advanced (5G-A) network, or a 5G ultrawideband (5G-UWB) network. In other implementations, the wireless communications system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technology including Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20. The wireless communications system 100 may support radio access technologies beyond 5G, for example, 6G. Additionally, the wireless communications system 100 may support technologies, such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA), etc.

[0021] The one or more NE 102 may be dispersed throughout a geographic region to form the wireless communications system 100. One or more of the NE 102 described herein may be or include or may be referred to as a network node, a base station, a network element, a network function, a network entity, a radio access network (RAN), a NodeB, an eNodeB (eNB), a next-generation NodeB (gNB), or other suitable terminology. An NE 102 and a UE 104 may communicate via a communication link, which may be a wireless or wired connection. For example, an NE 102 and a UE 104 may perform wireless communication (e.g., receive signaling, transmit signaling) over a Uu interface.

[0022] An NE 102 may provide a geographic coverage area for which the NE 102 may support services for one or more UEs 104 within the geographic coverage area. For example, an NE 102 and a UE 104 may support wireless communication of signals relatedto services (e.g., voice, video, packet data, messaging, broadcast, etc.) according to one or multiple radio access technologies. In some implementations, an NE 102 may be moveable, 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 may overlap, but the different geographic coverage areas may be associated with different NE 102.

[0023] The one or more UE 104 may be dispersed throughout a geographic region of the wireless communications system 100. A UE 104 may include or may be referred to as a remote unit, a mobile device, a wireless device, a remote device, a subscriber device, a transmitter device, a receiver device, or some other suitable terminology. In some implementations, the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples. Additionally, or alternatively, the UE 104 may be referred to as an Intemet-of-Things (loT) device, an Intemet-of-Everything (loE) device, or machinetype communication (MTC) device, among other examples.

[0024] A UE 104 may be able to support wireless communication directly with other UEs 104 over a communication link. For example, a UE 104 may support wireless communication directly with another UE 104 over 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, a UE 104 may support wireless communication directly with another UE 104 over a UE-to-UE interface (PC5 interface).

[0025] An NE 102 may support communications with the CN 106, or with another NE 102, or both. For example, an NE 102 may interface with other NE 102 or the CN 106 through one or more backhaul links (e.g., SI, N2, N2, or network interface). In some implementations, the NE 102 may communicate with each other directly. In some other implementations, the NE 102 may communicate with each other or indirectly (e.g., via the CN 106. In some implementations, one or more NE 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC). An ANC may communicate with the one or more UEs 104 through one or more other access network transmission entities, which may be referred to as a radio heads, smart radio heads, or transmission-reception points (TRPs).

[0026] The CN 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The CN 106 may be an evolved packet core (EPC), or a 5G core (5GC), which may include a control plane entity that manages access and mobility (e.g., a mobility management entity (MME), an access and mobility management functions (AMF)) and a user plane entity that routes packets or interconnects 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 entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc.) for the one or more UEs 104 served by the one or more NE 102 associated with the CN 106.

[0027] The CN 106 may communicate with a packet data network over one or more backhaul links (e.g., via an S I, N2, N2, or another network interface). The packet data network may include an application server. In some implementations, one or more UEs 104 may communicate with the application server. A UE 104 may establish a session (e.g., a protocol data unit (PDU) session, or the like) with the CN 106 via an NE 102. The CN 106 may route traffic (e.g., control information, data, and the like) between the UE 104 and the application server using the established session (e.g., the established PDU session). The PDU session may be an example of a logical connection between the UE 104 and the CN 106 (e.g., one or more network functions of the CN 106).

[0028] In the wireless communications system 100, the NEs 102 and the UEs 104 may use resources of the wireless communications system 100 (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communications). In some implementations, the NEs 102 and the UEs 104 may support different resource structures. For example, the NEs 102 and the UEs 104 may support different frame structures. In some implementations, such as in 4G, the NEs 102 and the UEs 104 may support a single frame structure. In some other implementations, such as in 5G and among other suitable radio access technologies, the NEs 102 and the UEs 104 may support various frame structures (i.e., multiple frame structures). The NEs 102 and the UEs 104 may support various frame structures based on one or more numero logics.

[0029] One or more numerologies may be supported in the wireless communications system 100, and a numerology may include a subcarrier spacing and a cyclic prefix. A first numerology (e.g., i=0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first numerology (e.g., =0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe. A second numerology (e.g., jU=l) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third numerology (e.g., ^=2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth numerology (e.g., ju=3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth numerology (e.g., [1=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.

[0030] A time interval of a resource (e.g., a communication resource) may be organized according to frames (also referred to as radio frames). Each frame may have a duration, for example, a 10 millisecond (ms) duration. In some implementations, each frame may include multiple subframes. For example, each frame may include 10 subframes, and each subframe may have a duration, for example, a 1 ms duration. In some implementations, each frame may have the same duration. In some implementations, each subframe of a frame may have the same duration.

[0031] Additionally or alternatively, a time interval of a resource (e.g., a communication resource) may be organized according to slots. For example, a subframe may include a number (e.g., quantity) of slots. The number of slots in each subframe may also depend on the one or more numerologies supported in the wireless communications system 100. For instance, the first, second, third, fourth, and fifth numerologies (i.e., [1=0, [1=1, [1=2, [1=3, [1=4) associated with respective subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may utilize a single slot per subframe, two slots per subframe, four slots per subframe, eight slots per subframe, and 16 slots per subframe, respectively. Each slot may include a number (e.g., quantity) of symbols (e.g., orthogonal frequency division multiplexing (OFDM) symbols). In some implementations, the number (e.g., quantity) of slots for a subframe may depend on a numerology. For a normal cyclic prefix, a slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable for 60 kHz subcarrier spacing), a slot may include 12 symbols. The relationship between the number of symbols per slot, the number of slots per subframe, and thenumber of slots per frame for a normal cyclic prefix and an extended cyclic prefix may depend on a numerology. It should be understood that reference to a first numerology (e.g.,=0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.

[0032] In the wireless communications system 100, an electromagnetic (EM) spectrum may be split, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc. By way of example, the wireless communications system 100 may support one or multiple operating frequency bands, such as frequency range designations FR1 (410 MHz - 7.125 GHz), FR2 (24.25 GHz - 52.6 GHz), FR3 (7.125 GHz - 24.25 GHz), FR4 (52.6 GHz - 114.25 GHz), FR4a or FR4-1 (52.6 GHz - 71 GHz), and FR5 (114.25 GHz - 300 GHz). In some implementations, the NEs 102 and the UEs 104 may perform wireless communications over one or more of the operating frequency bands. In some implementations, FR1 may be used by the NEs 102 and the UEs 104, among other equipment or devices for cellular communications traffic (e.g., control information, data). In some implementations, FR2 may be used by the NEs 102 and the UEs 104, among other equipment or devices for short-range, high data rate capabilities.

[0033] FR1 may be associated with one or multiple numerologies (e.g., at least three numerologies). For example, FR1 may be associated with a first numerology (e.g., ^=0), which includes 15 kHz subcarrier spacing; a second numerology (e.g., ^=1), which includes 30 kHz subcarrier spacing; and a third numerology (e.g., ^=2), which includes 60 kHz subcarrier spacing. FR2 may be associated with one or multiple numerologies (e.g., at least 2 numerologies). For example, FR2 may be associated with a third numerology (e.g., i =2), which includes 60 kHz subcarrier spacing; and a fourth numerology (e.g., i=3), which includes 120 kHz subcarrier spacing.

[0034] In some implementations, the wireless communications system 100 may be an NR NTN or an loT NTN. A UE 104 may access the NR NTN and / or the loT NTN based on the UE 104 having global navigation satellite system (GNSS) capabilities. The UE 104 may use coordinates of a GNSS to determine a position of the UE 104, which may be used to pre-compensate for time and frequency shift. An NR-NTN may use an open-loop timing adjustment procedure for a transparent payload NTN architecture, in which a timing advance (TA) is partitioned into common TA (e.g., corresponding to a feeder link round trip time (RTT)) and a user-specific TA (e.g., corresponding to a two-waytransmission delay on a service link). To estimate the user-specific TA, the UE 104 may identify a serving satellite position (e.g., information provided to the UE 104) and determine a location of the UE 104 (e.g., based on GNSS). Because non-geo stationary orbit (NGSO) satellites are continuously moving, the UE 104 may have to continuously update the TA and frequency pre-compensation when in a connected mode. Therefore, the UE 104 may require a reliable GNSS connection over a period of time of its entire connectivity to have NTN access.

[0035] Although GNSS provides a highly accurate position and time reference, there may be multiple occasions and / or scenarios when signals from the GNSS may be unavailable for a certain duration. For example, signals from the GNSS may experience outages, be jammed, or be spoofed, leading to an inaccurate position of the UE 104. Thus, this inaccuracy may result in the denial of NTN connectivity, as a user-specific TA derived from an incorrect position of the UE 104 may hinder uplink (UL) communication. Such scenarios may simultaneously impact a group of UEs in a cell for a certain duration. Additionally, there may be occasions when a UE 104 may experience degradation of NTN service due to relatively reduced GNSS location estimates (e.g., accuracy reduced to 300 m). This reduction may stem from various reasons, such as poor GNSS link budget, unavailability of a number of satellites, or a position of the UE 104 (e.g., in pocket, bag, etc.).

[0036] The degradation or denial of NR NTN service, due to temporary unavailability and / or inaccuracy of a GNSS location, may result in excessive power consumption from the UE 104 and an overall degradation in system performance. This is because the UE 104, configured with GNSS capability, may continue to attempt to connect to the GNSS, even when the location of the GNSS is unavailable due to spoofing or jamming. If the network has the knowledge of this temporary unavailability of the GNSS signals in its coverage area, then the network may either prevent UEs 104 from connection establishment for a temporary period or provide another means for timing synchronization. Various methods and related signaling aspects for timing synchronization, when the GNSS is temporarily unavailable for a UE 104 or a group of UEs 104 may be used while the UEs 104 in an idle state or trying to establish a new connection.

[0037] Timing adjustments may be made in NT. Moreover, time and frequency synchronization in NTN may be done as described herein.

[0038] Downlink (DL) and UL frames may be aligned at an UL time synchronization reference point (RP) with an offset given by NTAOffSet. To accommodate for propagation delay in NTNs, several timing relationships may be enhanced by a common TA and two offsetsand kmac. A common TA may be a configured timing offset that may be equal to the RTT between a RP and an NTN payload. The Koj jseLmay be a configured scheduling offset that may be larger or equal to the sum of the service link RTT and the common TA. The kmacmay be a configured offset that may be approximately equal (e.g., when rounded to a whole number, a tenth place, a thousandth place, and so forth) to the RTT between the RP and the gNB.

[0039] The scheduling offset KojjseLmay be used to allow a UE 104 sufficient processing time between a DL reception and an UL transmission. The offset kmacmay be used to delay an application of a DL configuration indicated by a medium access control (MAC) control element (CE) command on a physical downlink shared channel (PDSCH), and in estimation of UE-gNB RTT. It may be provided by the wireless communication system 100 when DL and UL frame timing are unaligned at a NE 102 (e.g., a base station). The kmacmay also be used during a random access procedure to determine a start time of a random access response (RAR) window and / or a random access message (e.g., a MsgB) window after transmission of another random access message (e.g., Msgl and / or MsgA transmission).

[0040] figure 2 illustrates an example of a timing relationship in a wireless communications system 200. The wireless communications system 200 may implement or be implemented by aspects of the wireless communications system 100 as described herein with reference to Figure 1. For example, the wireless communications system 200 may include a NE 102-a and a NE 102-b, which may be examples of a NE 102 as described herein with reference to Figure 1. The wireless communications system 200 may include a UE 104-a, which may be examples of a UE 104 as described herein with reference to Figure 1.

[0041] The NE 102-a may be referred to as a NTN network entity and may be, for example, a satellite, which may be any suitable type of communication satellite configured to relay or otherwise support wireless communications between differentdevices in the wireless communication system 200. In some implementations, the satellite may be in a geosynchronous or geostationary earth orbit, a low earth orbit, or a medium earth orbit. The NE 102-b may be a base station and may be referred to as an NTN gateway. The NE 102 -a may perform (e.g., transmit, receive, forward, route) wireless communication with the UE 104-a via a service link RTT 202. Additionally, the UE 104- a may perform (e.g., transmit, receive) wireless communication with the network entity 104-a via the service link RTT 202. The NE 102-a may perform (e.g., transmit, receive, forward, route) wireless communication with the NE 102-b via a feeder link RTT 204.

[0042] The NE 102-b may configure a hybrid automatic repeat request (HARQ) operation. For example, the network may enable or disable DL HARQ feedback per HARQ process. In some implementations, disabling the DL HARQ feedback may allow scheduling a HARQ process before one HARQ RTT has elapsed since a last scheduled HARQ process. The network may also configure an UL HARQ mode (e.g., a HARQ mode A, HARQ mode B) per HARQ process. HARQ mode B may allow scheduling a HARQ process before one HARQ RTT has elapsed since last scheduled HARQ process.

[0043] For the HARQ processes configured with HARQ feedback enabled and / or disabled, the NE 102-b may ensure a proper configuration of HARQ feedback (e.g., either all enabled or all disabled) for HARQ processes used by a semi-persistent scheduling (SPS) configuration. For the HARQ processes configured with a HARQ mode, the NE 102-b may ensure a proper configuration of a HARQ mode (e.g., either all HARQ mode A or all HARQ mode B) for HARQ processes used by a configured grant (CG) configuration.

[0044] Some configurations may use TA and frequency pre-compensation. For a serving cell, the NE 102-a and / or NE- 102-b broadcasts valid ephemeris information and common TA parameters. The UE 104-a may have a valid GNSS position as well as ephemeris and common TA before connecting to an NTN cell. To achieve synchronization, before and during connection to an NTN cell, the UE 104-a may compute a RTT between the UE 104-a and the RP based on the GNSS position, the ephemeris, and the common TA parameters, and autonomously pre -compensate a transmission TA (TTA) for the RTT between the UE 104-a and the RP.

[0045] The UE 104-a may compute a frequency Doppler shift of the service link, and autonomously pre-compensate for it in UL transmissions by considering UE 104-aposition and the ephemeris. If the UE 104-a does not have a valid GNSS position and / or valid ephemeris and common TA, it may not transmit UL transmissions until both are regained.

[0046] In a connected mode, the UE 104-a may be able to continuously update the TA and frequency pre-compensation. The UE 104-a may be configured to report the TA during random access procedures or in a connected mode. In the connected mode, event- triggered reporting of the TA may be used.

[0047] While the pre-compensation of the instantaneous Doppler shift experienced on the service link is to be performed by the UE 104-a, the management of Doppler shift experienced over the feeder link and transponder frequency error is left to network implementation.

[0048] In various configurations, a transmission timing adjustment procedure for terrestrial network (TN) and NTN may be performed as described herein.

[0049] A UE 104-a may be provided a value NTA o^setof a TA offset for a serving cell by n-Timing Ad vance Offset for the serving cell. If the UE 104-a is not provided n- TimingAdvanceOffset for a serving cell, the UE 104-a determines a default value NTA,offset °f the timing advance offset for the serving cell. If a UE 104-a is configured with two UL carriers for a serving cell, a same TA offset value NTA,OjseLapplies to both carriers.

[0050] Upon reception of a TA command for a TA group (TAG), the UE 104-a adjusts uplink timing for physical uplink shared channel (PUSCH), SRS, and / or physical uplink control channel (PUCCH) transmission on all the serving cells in the TAG based on a value NTA,OffSetthat the UE expects to be same for all the serving cells in the TAG and based on the received timing advance command where the uplink timing for PUSCH, SRS, and / or PUCCH transmissions is the same for all the serving cells in the TAG.

[0051] For a band with synchronous contiguous intra-band evolved non-standalone dual connectivity (EN-DC) in a band combination with non-applicable maximum transmit timing difference requirements, if the UE 104-a indicates ul- TimingAlignmentEUTRA-NR as 'required' and uplink transmission timing based on timing adjustment indication for a TAG from a master cell group (MCG) and a TAG from a secondary cell group (SCG) are determined to be different by the UE 104-a, the UE104-a adjusts the transmission timing for PUSCH, SRS, and / or PUCCH transmission on all serving cells part of the band with the synchronous contiguous intra-band EN-DC based on a timing adjustment indication for a TAG from a serving cell in MCG in the band. The UE 104-a is not expected to transmit a PUSCH, SRS, and / or PUCCH in one CG when the PUSCH, SRS, and / or PUCCH is overlapping in time, even partially, with random access preamble transmitted in another CG.

[0052] For a SCS of 2M■ 15 kHz, the TA command for a TAG indicates the change of the UL timing relative to the current UL timing for the TAG in multiples of 16 ■ 64 ■ TC / 2 . The start timing of the random access preamble may be determined.

[0053] A TA command for a random access response or in an absolute timing advance command MAC CE, TA, for a TAG indicates NTAvalues by index values of TA= 0, 1, 2, ..., 3846, where an amount of the time alignment for the TAG with subcarrier spacing (SCS) of 2^ ■ 15 kHz is NTA= TA■ 16 ■ 64 / 2^. NTAis defined and is relative to the SCS of the first UL transmission from the UE 104-a after the reception of the random access response or absolute timing advance command MAC CE.

[0054] In some configurations, a TA command, TA, for a TAG indicates adjustment of a current NTAvalue, NTA oid, to the new NTAvalue, NTA_new, by index values of TA= 0, 1, 2,..., 63, where for a SCS of 2 ■ 15 kHz, NTA_new= NTA-o i+ (TA— 31) ■ 16 ■ 64 / 2 .

[0055] If a UE 104-a has multiple active UL bandwidth parts (BWPs), in a same TAG, including UL BWPs in two UL carriers of a serving cell, the timing advance command value is relative to the largest SCS of the multiple active UL BWPs. The applicable NTA_newvalue for an UL BWP with lower SCS may be rounded to align with the TA granularity for the UL BWP with the lower SCS while satisfying TA accuracy requirements.

[0056] Adjustment of an NTAvalue by a positive or a negative amount indicates advancing or delaying the uplink transmission timing for the TAG by a corresponding amount, respectively.

[0057] For a timing advance command received on uplink slot n and for a transmission other than a PUSCH scheduled by a RAR UL grant or a fallbackRAR UL grant, or a PUCCH with HARQ-ACK information in response to a successRAR, thecorresponding adjustment of the uplink transmission timing applies from the beginning of uplink slotis a time duration in msecsymbols corresponding to a PDSCH processing time for UE 104-a processing capability 1 when additional PDSCH DM-RS is configured, NT 2is a time duration in msec of N2symbols corresponding to a PUSCH preparation time for UE 104-a processing capability 1, NTA,max is the maximum timing advance value in msec that can be provided by a TA command field of 12 bits, [\i^bJrame^ is the number of slots per subframe, Tsj is the subframe duration of 1 msec, and Koffset= KCeii,offset - KUE:Offset, where Kceu:Offsetis provided by cellSpecificKoffset andis provided by a Differential KoffsetMAC CE command; otherwise, if not respectively provided, Kceu0^set= 0 or KuE,Offsetand N2are determined with respect to the minimum SCS among the SCSs of all configured UL BWPs for all uplink carriers in the TAG and of all configured DL BWPs for the corresponding downlink carriers. For i = 0, the UE assumes N10= 14. Slot n andaredetermined with respect to the minimum SCS among theSCSs of all configured UL BWPs for all uplink carriers in the TAG. NTA,maxis determined with respect to the minimum SCS among the SCSs of all configured UL BWPs for all uplink carriers in the TAG and for all configured initial UL BWPs provided by initialUplinkBWP. The uplink slot n is the last slot among uplink slot(s) overlapping with the slot(s) of PDSCH reception assuming TTA= 0, where the PDSCH provides the timing advance command and TTAis defined.

[0058] If a UE 104-a changes an active UL BWP between a time of a TA command reception and a time of applying a corresponding adjustment for the UL transmission timing, the UE 104-a determines the TA command value based on the SCS of the new active UL BWP. If the UE 104-a changes an active UL BWP after applying an adjustment for the UL transmission timing, the UE 104-a assumes a same absolute TA command value before and after the active UL BWP change.

[0059] If the received DL timing changes and is not compensated or is only partly compensated by the UL timing adjustment without TA command, the UE changes NTAaccordingly.

[0060] If two adjacent slots overlap due to a TA command, the latter slot is reduced in duration relative to the former slot. The UE does not change NTAduring an actual transmission time window for a PUSCH or a PUCCH transmission.

[0061] Using higher-layer ephemeris parameters for a serving satellite, if provided, a UE 104-a may pre -compensate the two-way transmission delay on the service link based on iV^adj that the UE 104-a determines using the serving satellite position and its own position. To pre -compensate the two-way transmission delay between the UL time synchronization reference point and the serving satellite, the UE 104-a determines ^TAadj°nbased on one-way propagation delay Delaycommon(t) that the UE 104-a determines as:

[0063] where TAcommon, TAcommon rij’t:, and TA^ommon]jrij’iyariani:are respectively provided by ta-Common, ta-CommonDrift, and ta-CommonDriftVariant and tepoch is provided by epochTime which is the epoch time of ta-Common, ta- CommonDrift, and ta-CommonDriftVariant. Delaycommon(t) provides a distance at time t between the serving satellite and the uplink time synchronization reference point divided by the speed of light. The uplink time synchronization reference point is the point where DL and UL are frame aligned with an offset given by NTA o^set.

[0064] RRC signaling may be used for TA calculation in NTN. There may be an information element (IE) for NTN configuration (e.g., NTN-Config IE) that contains the essential parameter information needed for calculation of common TA and user specific information. One embodiment of a NTN-Config IE is shown in Table 1 , and NTN-Config field descriptions are shown in Table 2.Table 1 : NTN-Config IETable 2: NTN-Config Filed Descriptions

[0065] In an NR NTN transparent payload architecture, a UE pre-compensates the two-way transmission delay on the service link based on its TA calculation, which is determined by the UE using the serving satellite position and its own position. For this purpose, the following formula is used to determine the TA (referred to as open loop TA procedure):

[0067] where / VTAdenotes the TA component based on accumulating “TA commands” received from the network (e.g., by MAC CE command) and is reset to zero whenever there is a random access channel (RACH) procedure to acquire TA estimates, whileadj denotes the TA component specific to satellite communications and is determined by the UE based on the UE’s own location and the NTN serving satellite’s ephemeris, thus accuracy ofadj depends on the accuracy of the location information.

[0068] In some configurations, NR NTN UE has GNSS capabilities and calculates its own position using GNSS. However, GNSS may be prone to spoofing and jamming,which may either lead to incorrect location reporting and potentially denial of service if there is spoofing or lead to denial of service if there is jamming on a temporary basis (e.g., for the time period of spoofing and jamming). Additionally, natural phenomena, such as solar radiation bursts, which can affect large parts of the earth surface for 10 to 20 minutes, may also result in temporary unavailability of GNSS signals, resulting in denial of service.

[0069] Various embodiments found herein provide potential enhancements for UE pre-compensation for UL timing adjustments such as in the following two scenarios when GNSS accuracy or availability is reduced on a temporary basis: 1) during idle mode; or 2) during initial access. One or more of the following may be performed: 1) pausing the message 1 (Msgl) transmission for a temporary time period when the GNSS location estimates may not be available due spoofing or jamming especially for UEs that are establishing an RRC connection from not-connected states including RRC idle and RRC inactive; 2) extending an idle state duration; 3) updating and storing the GNSS location in the idle state with a validity timer; and / or 4) providing alternate means for calculating location estimates.

[0070] In a first embodiment, a Msg 1 preamble transmission may be paused during unavailability of the GNSS. According to the first embodiment, a UE with a GNSS capability does not transmit the Msgl preamble for a time duration upon a request from a non-access stratum (NAS) layer (e.g., upon receiving a NAS protocol data unit (PDU), when either the GNSS is not available or the location accuracy is lower than a predefined accuracy value. In one implementation, the first embodiment is applicable to UEs that are performing an initial access procedure to transition from an RRC not-connected state to a connected state. For instance, if a UE is in an RRC not-connected state and would like to go to an RRC connected state, the UE may acquire and use an NTN system information block (SIB) of the serving cell. The network may include a timer configuration in the NTN SIB that stipulates a minimum and / or maximum time for which the UE may be allowed to wait before transmitting Msg 1.

[0071] Figure 3 illustrates an example of aprocedure 300 for use during satellite (e.g., GNSS) unavailability in accordance with aspects of the present disclosure. In some implementations, the procedure 300 may implement, or be implemented by, aspects of the wireless communication system 100 and the wireless communication system 200 asdescribed with reference to Figures 1 and 2. The procedure 300 may include a gNB 302 which may be an example of a NE 102 as described herein. The procedure 300 may also include a UE 304 which may be an example of a UE 104 as described herein. In the following description of the procedure 300, the operations between the gNB 302 and the UE 304 may be transmitted in a different order than the example order shown, or the operations performed by the gNB 302 and the UE 304 may be performed in different orders or at different times. Some operations may also be omitted from the procedure 300, and other operations may be added to the procedure 300.

[0072] At 306, the gNB 302 may transmit a synchronization signal block (SSB) to the UE 304. The UE 304 may perform a DL time and / or frequency synchronization and / or master information block (MIB) detection.

[0073] At 308, the gNB 302 may transmit a control resource set (CORESET) #0 to the UE 304. The UE 304 may perform SIB detection and may receive a physical RACH (PRACH) resource, common TA parameter, satellite ephemeris, and / or timer configuration.

[0074] At 310, the UE 304 may start a timer, pause a Msgl transmission, and / or look for a GNSS signal and improvement of location inaccuracy within a timing window.

[0075] At 312, the UE 304 may transmit the Msgl preamble to the gNB 302. For example, the UE 304 may use the common TA in SIB and self estimated UE-specific TA for the preamble if its location is available after or within the timing window.

[0076] At 314, the gNB 302 may transmit a Msg2 (RAR with TAC) to the UE 304. The UE 304 may use the common TA in SIB, the self estimated UE-specific TA, and TAC in RAR for UL synchronization.

[0077] In one embodiment, a duration of a timer window may imply that the UE 304 would not perform the RACH procedure for the configured duration. For example, upon detection of SSB and by reading the MIB and CORESET#0 parameters, the UE would pause the Msgl preamble for the configured time or GNSS signals for the configured duration and would only perform the RACH procedure after the expiry of timer. The network may adjust the value of the timer based on its knowledge of intended jamming and spoofing duration if there is no GNSS jamming or spoofing (e.g., timer is set to zero). If the timer is set to zero, the UE would perform the RACH procedure without any pauseand / or delay. Such an implementation may allow UEs to conserve energy by not trying to perform a RACH procedure again and again (or detecting GNSS signals) during a jamming or spoofing period.

[0078] In certain embodiments, an original equipment manufacturer (OEM) transmits information about GNSS jamming and / or spoofing duration to a NG-RAN node (e.g., gNB) or a core network (e.g., AMF). In such embodiments, the core network (e.g., AMF) has the information about GNSS spoofing and / or jamming and its expected duration, then the core network (e.g., AMF) may indicate the information to the NG-RAN node (e.g., gNB).

[0079] In various embodiments, a duration of a timer may imply that the UE 304 may pause the Msgl preamble based on a detected SSB for a duration for which GNSS signals are not available or location accuracy is low. During this window, the UE 304 may keep on looking for GNSS signals and once the GNSS signals are there or GNSS location accuracy has reached a desired threshold, then the UE 304 may transmit the Msgl preamble. In one implementation, the UE 304 may transmit the Msgl preamble before the expiry of timer if the GNSS signals or accurate location are available within the timer window. In another implementation, the UE 304 may transmit the Msgl preamble only after the expiry of timing window, even if the GNSS signals are available before the timer expiry.

[0080] In some embodiments, a new timer value for which the UE 304 may need to pause the Msgl preamble transmission is specified and / or predetermined. An indication to activate or deactivate this window may be indicated during initial access (e.g., in a physical downlink control channel (PDCCH) and / or downlink control information (DCI) of SIB1, in SIB1, orNTN SIB).

[0081] In various embodiments, a duration of a timing window is variable and is adjusted by a network based on jamming or spoofing information, whereas the duration may be indicated to the UE 304 as part of a radio resource control (RRC) scheduling configuration message (e.g., in SIB 1 or NTN SIB). For example, a field corresponding to a duration may be defined with multiple durations in time and one of the durations is configured by the network. If there is no jamming or spoofing, the time duration may be set to zero.

[0082] In a second embodiment, an idle state duration may be extended. According to the second embodiment, a network indicates to idle UEs to remain in the idle state for a certain duration with an idle state extension timer whenever the network detects and / or knows about a GNSS jamming or spoofing event. The UE, upon receiving such indication, would not perform the RACH procedure before the expiry of the indicated timer. For example, the UE may be indicated during the idle state with an idle state extension timer. The UE would start the timer in the idle state and would remain in the idle state until the timer stops. After the timer has stopped, the UE may remain in the idle state or perform a RACH procedure if needed or go to a not-connected state if GNSS signals are still bad.

[0083] In one example, the idle state extension timer does not bind a UE to go from the idle state to the connected state, rather is an implicit indication to the UE that GNSS signals may not be available during this idle state extended period. For example, once an idle state extension timer indication is received by the UE, the UE would start monitoring its GNSS signal status and as soon as the UE has good signal strength or GNSS location accuracy above the threshold, then only the UE may perform RACH procedure within the idle state extension window, if needed.

[0084] In certain embodiments, the network may extend the idle state extension window multiple times during the idle state with fixed or variable durations. For example, the network may indicate to the UE to extend the idle state by a certain duration. However, if network realizes the need to extend the idle state further, the network may indicate this to the UE with another idle state extension timer indication.

[0085] Figure 4 illustrates an example of communications 400 having an idle state extension during satellite unavailability (e.g., when no GNSS is available) in accordance with aspects of the present disclosure. Timing of UE status / states include an idle state 402, an idle state extension 404 (first extension), an idle state extension 406 (second extension), performing actions 408 (performs RACH procedure, remains in idle state, or goes to a not-connected state). The UE receives 410 an idle state extension timer indication to create the idle state extension 404. The idle state extension timer has a duration 412. The UE receives 412 a second idle state extension timer indication to create the idle state extension 406.

[0086] In one embodiment, the idle state extension timer is indicated to a UE or group of UEs using a paging message. In one example, the duration of the idle state extension timer is fixed and is activated or deactivated using a paging message. In another example, the duration of the idle state extension is also indicated in a paging message with information that activates and / or indicates the idle state extension timer. In one realization, DCI format 1 0 with cyclic redundancy cycle (CRC) scrambled by a paging radio network temporary identifier (P-RNTI) may be enhanced with idle state extension timer information. For instance, short messages may be used to indicate either the activation or deactivation of the idle state extension timer or the duration of extension of the idle state. In one implementation, the network may indicate whether a UE or group of UEs may initiate the RACH process if GNSS signals are available within the idle state extension period. In another implementation, a field is used in RRC paging messages that is used for triggering RRC setup (e.g., RRC request and RRC connection resumption) to indicate when to resume the RRC setup after receiving the message. For example, if a UE receives a RRC setup triggering message, a time period may also be configured in the message that indicates when to initiate a RACH procedure after the reception of the message (e.g., after 1 second (basically a delay indication for setting up RRC connection)). If there is no such field, then the UE may initiate the RACH procedure instantly after the reception of the message.

[0087] In one embodiment, when the idle state extension timer is valid for all UEs in a cell (e.g., if a beam corresponds to a cell and / or cell size is small or jamming and / or spoofing is affecting the whole cell), the idle state extension timer activation and / or deactivation or duration may be indicated through broadcast messages (e.g., using NTN SIB).

[0088] In a third embodiment, the GNSS location may be updated and / or stored while a UE is in an idle state. According to third embodiment, the GNSS location estimates may be valid for a certain duration within the idle state and the GNSS location estimates may be used for a RACH procedure to calculate user specific timing calculations if a RACH procedure is performed within a GNSS validity duration. Such GNSS location estimate validity duration may imply that a UE in idle state checks for its GNSS location and starts a timer corresponding to GNSS validity duration for its GNSS location estimates. After the timer expires, the UE (if still in an idle state) may look for a new GNSS location estimate and may start the GNSS validity timer for its new GNSS location estimates untilthe timer expires. The UE may keep on repeating this procedure while the UE remains in the idle state. In one implementation, if the UE wants to go to an RRC connected state from the idle state, the UE may look for new GNSS location estimates to be able to transmit Msgl preamble and, if the GNSS location estimates are not available, the UE may use the last GNSS location estimates that are within the GNSS validity duration for the calculation of user specific timing advance. In another implementation, the UE may always use the GNSS location estimates that are within the GNSS validity duration for the calculation of user specific timing calculations.

[0089] In some implementations, a UE starts or restarts a configurable validity timer each time its location is acquired with a minimum threshold accuracy. If at the time of an intended Msgl transmission, the validity timer is running (e.g., is not considered expired), a UE may base its UE specific TA calculation for a service link on a most recent valid location. If the timer is considered expired at the time of intended Msg 1 transmission, the UE may first obtain it location. If it fails to obtain its location or if the obtained location is not considered accurate enough, a UE may either not initiate an RRC connection establishment and / or resumption or use a default value of the UE specific TA for the service link. The default value may be configured by the network and may be a function of one or more of the following: 1) a UE’s last known location; and / or 2) a UE’s measurement results of serving and / or neighboring cells.

[0090] In various implementations, a UE periodically acquires its location. The UE may initiate RRC connection establishment and / or resumption when required by upper layer (e.g., NAS) if the accuracy ofthe acquired location is higher than a certain minimum threshold value. However, if the accuracy of the acquired location is lower than a certain minimum threshold value, the UE may try to acquire the location again before the next periodic occasion to obtain its location. If an accurate-enough location is not available, the UE may first obtain it location. If it fails to obtain its location or if the obtained location is not considered accurate enough, a UE may either not initiate an RRC connection establishment (refrain from performing for a period of time) and / or resumption or use a default value of the UE specific TA for the service link. The default value may be configured by the network and may be a function of one or more of the following: 1) a UE’s last known location; and / or 2) a UE’s measurement results of the serving and / or neighboring cells.

[0091] Figure 5 illustrates an example of a procedure 500 for using a stored location estimate (e.g., GNSS location estimate) for a procedure (e.g., RACH procedure) in accordance with aspects of the present disclosure. In some implementations, the procedure 500 may implement, or be implemented by, aspects of the wireless communication system 100 and the wireless communication system 200 as described with reference to Figures 1 and 2. The procedure 500 may include a UE 502 (in RRC idle state) which may be an example of a UE 104 as described herein. The procedure 500 may also include a gNB 504 which may be an example of a NE 102 as described herein. In the following description of the procedure 400, the operations between the UE 502 and the gNB 504 may be transmitted in a different order than the example order shown, or the operations performed by the UE 502 and the gNB 504 may be performed in different orders or at different times. Some operations may also be omitted from the procedure 500, and other operations may be added to the procedure 500.

[0092] At 506, the UE 502 may acquire its GNSS location estimates and may start a GNSS location estimate validity timer for a GNSS idle state validity duration 508.

[0093] At 510, the GNSS location estimate validity timer may expire and the UE may acquire new GNSS location estimates and may start a new GNSS location estimate validity timer for another GNSS idle state validity duration 512.

[0094] At 512, the new GNSS location estimate validity timer may expire.

[0095] At 514, RRC setup triggering may be performed as part of an RRC setup procedure where the UE 502 may try to acquire new GNSS location estimates if not available and may use the GNSS location estimates that are within the validity duration.

[0096] In one embodiment, a network may indicate an idle state validity duration of GNSS location estimates to a UE when the UE is in a connected state (before going to the idle state from the connected state) using higher layer signaling (e.g., RRC signaling), group common signaling, or through SIB. There may be one or more validity durations within a whole idle period where these multiple validity durations may have a fixed duration or have variable durations (e.g., not of the same duration) and may depend on a number of factors such as UE mobility, satellite orbit, and so forth. In one implementation, if the multiple validity durations are of a variable nature in the idle state, the network may configure only the first duration of the idle state GNSS location estimate validity in the connected state and may also indicate that this duration is valid for theconfigured period (e.g., duration may not be repeated if the idle period is more than the GNSS validity duration) using RRC, MAC-CE, or DCI signaling. In such an implementation, if the GNSS validity duration is less than the idle state duration, then the GNSS location estimates may not be used after the expiration of the timer for the purpose of a user specific timing calculation. The network may configure new validity durations of new GNSS location estimates in the idle state, if needed. In another implementation, the network may configure multiple validity durations in the connected mode that are to be used in the idle state using RRC and / or MAC-CE signaling, where the UE may acquire new GNSS location estimates for each validity duration. For example, if two validity durations of 2 and 4 minutes are configured, the UE may acquire GNSS location estimates as it goes to the idle state and the GNSS location estimates may be valid for 2 minutes and, after 2 minutes, the UE may acquire new GNSS location estimates that may be valid for 4 minutes. In one implementation, a single GNSS validity duration is configured for an entire idle period and may be configured to a UE in the connected mode using RRC signaling. This may imply that a GNSS location estimate may be valid for a configured period and a UE may acquire new GNSS location estimates after expiration of the configured period and again validate the newly acquired GNSS location estimates for the same validity period.

[0097] In certain embodiments, a GNSS validity duration is configured in a connected mode, while activation and / or deactivation is carried out in an idle mode. The activation and / or deactivation may be indicated to UEs using a paging message (e.g., using a short message) or using a broadcast message (e.g., using NTN SIB) if it is to be activated for a whole cell. In one implementation, the activation and / or deactivation and / or duration of GNSS validity duration may be configured using a transmission to a UE or group of UEs only in the idle state. A paging message may be used for this purpose orthrough broadcast messages (e.g., NTN SIB). In one embodiment, a GNSS validity duration is coupled with an UL synchronization validity timer, where a UE may acquire GNSS location estimates and may use the same GNSS location estimates when the UL synchronization validity timer expires.

[0098] In some embodiments, a UE in an idle state may use its last known location to perform a RACH procedure (e.g., for the purpose of user specific differential timing calculation), where the last known location may be defined as location coordinates estimated by the UE by positioning methods such as GNSS, wireless local area network(WLAN), or from any other positioning estimate method. The network may configure a UE with information about when to use a last known location.

[0099] In one example, the network may also configure conditions that may help a UE to decide whether last known location estimates may be used for a RACH process when a UE goes from an idle state to a connected state, from a not-connected state to a connected state, or during the connected state when a RACH procedure is needed. For instance, any of the following set of conditions may be defined by the network: 1) a method usage condition: a UE only uses the last known location when GNSS signals are not available or location estimates are below a location accuracy threshold; 2) a last known location estimate method priority: a field describing the priority may be defined to indicate to the UE about the priority of using last known location estimates - for example, if multiple methods are supported, then such field may define where to prioritize the last known location methodology over others; 3) a last location validity duration: a duration may be set by the network that may indicate whether the last known location is valid to be used for a RACH process - for example, a UE in an idle state may need to establish a connection while employing its last known location estimates - the UE may check for its last known location estimates and corresponding time stamp and may calculate the duration from the time when the last known location was estimated - if the calculated location is within the location validity duration, a UE may make use of this in the RACH process - alternatively, the validity duration may also indicate to a UE about when to acquire a new position estimate and consider those as last known locations; and / or 4) a validity distance: a distance set by the network indicating whether a UE has moved a considerable distance from the last known location. Such condition may be helpful for UE mobility. For example, a UE may calculate the distance that has been travelled from its last known location and compare it with the validity distance. If it falls within the validity distance, then the last known location estimates may be used. In one example, a combination of validity duration and validity distance may be used to check for the validity of a last known location.

[0100] In one example, conditions and / or parameters are indicated to a UE when a UE is in a connected state (e.g., as part of RRC signaling) and the UE is further indicated that these parameters are valid for an idle state and / or inactive state. In one implementation, these parameters are indicated during an idle state using paging or included in SIBs that are valid for the idle state.

[0101] In various embodiments, a UE determines when a last known location is to be used and a validity duration for the last known location. The UE may determine this information based on its mobility history (e.g., speed, direction) or based on satellite ephemeris information. In other embodiments, the network may set some parameter that may be helpful for a UE to determine the last known location and the validity duration. For instance, the network may set a GNSS position tolerance limit, then the UE determines (based on its own GNSS readings) when the actual GNSS position is away from the previously GNSS position more than the indicated tolerance, and upon such determination, the UE further determines whether to use the last known GNSS location.

[0102] In a fourth embodiment, timing synchronization may be performed without GNSS location estimates during a RACH procedure. According the fourth embodiment, a UE may resort to other timing synchronization methods (e.g., methods not involving GNSS location estimates) while performing the RACH procedure (e.g., from the not- connected state to the connected state, from the idle state to the connected state, or in the connected state), when GNSS location estimates are temporarily not available or location estimation accuracy is lower than a predefined location accuracy, where resorting to other methods may either be indicated to a UE if there is jamming or spoofing (e.g., by the serving network or UE by default resort to other methods during the GNSS unavailability or lower GNSS location accuracy after failing to acquire accurate enough location in certain number of attempts or over a period of time). These time synchronization techniques may not provide accurate time synchronization but may provide temporary sufficient time synchronization for a UE to remain in the connected state on a temporary basis until GNSS location estimates are available. If the GNSS location estimates are available, then the UE may switch back to GNSS location estimate based time synchronization methods.

[0103] In various embodiments, the network may indicate a time duration for the validity of other timing synchronization techniques. This may be indicated to a UE while the UE is in an idle state (e.g., using paging or as part of SIB) or indicated as part of initial access system information. The UE may apply other synchronization methods only for the indicated duration and after that may try to resort to GNSS location based synchronization. If GNSS location estimates are still not available, then the UE may disconnect from the network until the UE retains GNSS location estimates with sufficient accuracy.

[0104] In a first implementation of the fourth embodiment, timing synchronization may be based on zone-based location information. According to the first implementation of the fourth embodiment, the network divides the cell into different zones and provide temporary location estimates for each zone that are to be used instead of UE GNSS location estimates for the calculation of user specific timing calculations if UE GNSS location estimates are not available. For example, a zone-based mapping table, as shown in Table 3, may be formulated for a cell, where each zone may be associated with at least one reference location coordinate set, where this reference location may be any location in the zone that is best suited for the type of cells. For instance, for NGSO based earth fixed cells or quasi earth fixed cells, the reference location may be the center of a zone. In one implementation, the location coordinates are expressed in terms of position cartesian coordinates (e.g., position state vector in x, y, and z coordinates). In another implementation, the reference location coordinates are expressed in terms of orbital coordinates (e.g., in latitude and longitude).Table 3: Zone-based Reference UE Location Mapping Table

[0105] In one embodiment, each zone is associated with a SSB beam, where the zone index may be an SSB index. For instance, the coverage area of an SSB may be considered as one zone, where SSB may be beamformed in such a way that the SSB covers a minimum coverage area on the ground. The network may calculate the coverage area coordinates while calculating the beamforming weights of an SSB. In this way, the network knows which and how much area on the earth is covered by an SSB. The network may associate a reference location to that SSB index. If jamming or spoofing happens in one zone (e .g. , in the coverage area of one S SB), the UEs in that zone (e.g., in the coverage area of one SSB) may use the indicated reference location for the calculation of user specific timing.

[0106] Figure 6 illustrates an example of a system 600 with SSB based reference location mapping in accordance with aspects of the present disclosure.

[0107] In one embodiment, the mapping table having the information of SSB index and corresponding reference location (to be used instead of UE GNSS location for the purpose of user specific timing calculation) is configured as part of an SIB (e.g., in NTN SIB). Whenever a UE would like to perform a RACH procedure, the UE may look for its own GNSS location. If the GNSS location is not available, the UE may look for a reference location (e.g., a last known location) in an NTN SIB corresponding to its own SSB index and may use that reference location instead of a UE GNSS location for the purpose of user specific timing calculation.

[0108] In another embodiment, a time duration for the validity of the mapping table may be indicated along with the mapping table. This may be needed as satellites are moving and the coverage area may change for an SSB. Especially for an earth moving cell, a frequent update of the mapping table may be needed. The UE may or may not need to perform a RACH procedure for each change of a mapping table. Depending on a cell layout design, satellite orbital constellation, and other factors, a network may decide whether a new RACH procedure is needed with a change and / or update of a mapping table. This may additionally be indicated in the same configuration or separately using RRC, MAC-CE, or DCI signaling.

[0109] In some embodiments, a network may include information in a mapping table corresponding to a maximum size of a coverage area of a zone (e.g., SSB) with reference to an indicated reference location to help UEs that may be located far from an indicated reference location. This information may be depicted as a maximum coverage distance (e.g., radius) from a reference location. For example, in a scenario shown in Figure 6, UE 2 and UE 3 may use the same reference location as UE 1 for the calculation of user specific timing calculations when no GNSS location estimates are available. However, UE 2 and UE 3 may experience more timing errors compared to UE 1 as UE 2 and UE 3 are located far away from the reference location. The UEs that are located far from a reference location have more chances to detect neighboring SSBs as these UEs may fall in overlapping areas of beams (e.g., UE 2 and UE 3). In NTN, owing to large beam footprint size, the beam overlapping areas may be as large as 100 kilometers even with generation of very narrow beams from a satellite; therefore, many UEs may experience similar conditions. The UEs that are near the beam edges may need to select one of the reference locations that may be selected based on a best SSB. For instance, UEs may select the reference location of one of the more detected SSBs that have the best referencesignal received power (RSRP) values (e.g., UE 2 may use the LI). In one implementation, the network may select the criteria for selecting the reference location from multiple detected SSBs (e.g., by defining a reference RSRP threshold value). Alternatively, it may be left to a UE to select a reference location corresponding to a zone (e.g., SSB). In such cases, if additional information such as maximum distance (e.g., radius) from the reference location is available, the UE may calculate its own approximate location estimates using the reference location coordinates, the distance from the reference location, and RSRP values of SSBs. For example, for UE3, a triangulation technique may be used by the UE to calculate its own position and that may be used for the calculation of user specific timing calculations. For UE 2, a mean value from the two reference locations may be calculated and may be used as the UE’s own location in a RACH process. In certain implementations, a distance to RSRP mapping may be used to enhance location estimates.

[0110] In various embodiments, a mapping table may be based on cell-ids and reference locations instead of being zone and / or SSB based mapping. These embodiments may be used if one beam is associated with a cell (e.g., each SSB-ID corresponds to one cell-ID).

[0111] In a second implementation of the fourth embodiment, a location estimate may use a time and / or frequency difference of arrival of SSBs. According to the second implementation of the fourth embodiment, the location estimates are calculated by using time difference of arrival (TDOA) and frequency difference of arrival (FDOA) measurements of multiple SSBs that are beamformed by one satellite or multiple satellites, where such location estimates may require a large observation window for enhanced accuracy which may further depend on a number of satellites in view. Once the location estimates are derived, then these may be used for the calculation of user specific differential TAs.

[0112] For a single satellite, TDOA and / or FDOA measurements may be derived from multiple SSBs at different time intervals by using satellite movement. However, this may require that a satellite ephemeris is known to a UE when the measurements are taken. If a UE detects an SSB, the ephemeris information may be found in NTN SIB, whereas satellite ephemeris information periodicity is configured by the network and may vary depending on a satellite altitude. If location estimates are to be calculated within a shortinterval using TDOA and / or FDOA measurements, the periodicity of ephemeris information may need to be updated with a short window for the UE to collect reliable measurements. In one embodiment, the network may configure a timing window for the calculation of TA estimates using TDOA and / or FDOA measurements of SSBs.

[0113] Figure 7 illustrates an example of a UE 700 in accordance with aspects of the present disclosure. The UE 700 may include a processor 702, a memory 704, a controller 706, and a transceiver 708. The processor 702, the memory 704, the controller 706, orthe transceiver 708, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.

[0114] The processor 702, the memory 704, the controller 706, or the transceiver 708, or various combinations or components thereof may be implemented in hardware (e.g., circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.

[0115] The processor 702 may include an intelligent hardware device (e.g., a general- purpose processor, a DSP, a CPU, an ASIC, a field programmable gate array (FPGA), or any combination thereof). In some implementations, the processor 702 may be configured to operate the memory 704. In some other implementations, the memory 704 may be integrated into the processor 702. The processor 702 may be configured to execute computer-readable instructions stored in the memory 704 to cause the UE 700 to perform various functions of the present disclosure.

[0116] The memory 704 may include volatile or non-volatile memory. The memory 704 may store computer-readable, computer-executable code including instructions when executed by the processor 702 cause the UE 700 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such the memory 704 or another type of memory. Computer-readable media includes both non- transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitorystorage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.

[0117] In some implementations, the processor 702 and the memory 704 coupled with the processor 702 may be configured to cause the UE 700 to perform one or more of the functions described herein (e.g., executing, by the processor 702, instructions stored in the memory 704). For example, the processor 702 may support wireless communication at the UE 700 in accordance with examples as disclosed herein. For example, the processor 702 coupled with the memory 704 may be configured to cause the UE 700 to receive, from a network entity, a configuration via a paging message, determine an unavailability of a GNSS, and establish an RRC connection with the network entity based on the received configuration and the unavailability of the GNSS.

[0118] The controller 706 may manage input and output signals for the UE 700. The controller 706 may also manage peripherals not integrated into the UE 700. In some implementations, the controller 706 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 706 may be implemented as part of the processor 702.

[0119] In some implementations, the UE 700 may include at least one transceiver 708. In some other implementations, the UE 700 may have more than one transceiver 708. The transceiver 708 may represent a wireless transceiver. The transceiver 708 may include one or more receiver chains 710, one or more transmitter chains 712, or a combination thereof.

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

[0121] A transmitter chain 712 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 712 may include at leastone 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 like phase-shift keying (PSK) or quadrature amplitude modulation (QAM). The transmitter chain 712 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmitter chain 712 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0122] Figure 8 illustrates an example of a processor 800 in accordance with aspects of the present disclosure. The processor 800 may be an example of a processor configured to perform various operations in accordance with examples as described herein. The processor 800 may include a controller 802 configured to perform various operations in accordance with examples as described herein. The processor 800 may optionally include at least one memory 804, which may be, for example, an L1 / L2 / L3 cache. Additionally, or alternatively, the processor 800 may optionally include one or more arithmetic -logic units (ALUs) 806. One or more of these components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0123] The processor 800 may be a processor chipset and include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) in accordance with examples as described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to or included in the processor chipset (e.g., the processor 800) or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase change memory (PCM), and others).

[0124] The controller 802 may be configured to manage and coordinate various operations (e.g., signaling, receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) of theprocessor 800 to cause the processor 800 to support various operations in accordance with examples as described herein. For example, the controller 802 may operate as a control unit of the processor 800, generating control signals that manage the operation of various components of the processor 800. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.

[0125] The controller 802 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 804 and determine subsequent instruction(s) to be executed to cause the processor 800 to support various operations in accordance with examples as described herein. The controller 802 may be configured to track memory address of instructions associated with the memory 804. The controller 802 may be configured to decode instructions to determine the operation to be performed and the operands involved. For example, the controller 802 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 800 to cause the processor 800 to support various operations in accordance with examples as described herein. Additionally, or alternatively, the controller 802 may be configured to manage flow of data within the processor 800. The controller 802 may be configured to control transfer of data between registers, arithmetic logic units (ALUs), and other functional units of the processor 800.

[0126] The memory 804 may include one or more caches (e.g., memory local to or included in the processor 800 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, the memory 804 may reside within or on a processor chipset (e.g., local to the processor 800). In some other implementations, the memory 804 may reside external to the processor chipset (e.g., remote to the processor 800).

[0127] The memory 804 may store computer-readable, computer-executable code including instructions that, when executed by the processor 800, cause the processor 800 to perform 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. The controller 802 and / or the processor 800 may be configured to execute computer-readable instructions stored in the memory 804 to cause the processor 800 to perform various functions. For example, the processor 800 and / or the controller 802 may be coupled withor to the memory 804, the processor 800, the controller 802, and the memory 804 may be configured to perform various functions described herein. In some examples, the processor 800 may include multiple processors and the memory 804 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein.

[0128] The one or more ALUs 806 may be configured to support various operations in accordance with examples as described herein. In some implementations, the one or more ALUs 806 may reside within or on a processor chipset (e.g., the processor 800). In some other implementations, the one or more ALUs 806 may reside external to the processor chipset (e.g., the processor 800). One or more ALUs 806 may perform one or more computations such as addition, subtraction, multiplication, and division on data. For example, one or more ALUs 806 may receive input operands and an operation code, which determines an operation to be executed. One or more ALUs 806 be configured with a variety of logical and arithmetic circuits, including adders, subtractors, shifters, and logic gates, to process and manipulate the data according to the operation. Additionally, or alternatively, the one or more ALUs 806 may support logical operations such as AND, OR, exclusive-OR (XOR), not-OR (NOR), and not-AND (NAND), enabling the one or more ALUs 806 to handle conditional operations, comparisons, and bitwise operations.

[0129] The processor 800 may support wireless communication in accordance with examples as disclosed herein. The processor 800 may be configured to or operable to support a means for: receiving, from a network entity, a configuration, determining an unavailability of a GNSS, calculating, based on the unavailability of the GNSS, userspecific timing to perform an RRC connection establishment procedure, and performing the RRC connection establishment procedure according to the received configuration and based on the calculated user-specific timing.

[0130] Figure 9 illustrates an example of a NE 900 in accordance with aspects of the present disclosure. The NE 900 may include a processor 902, a memory 904, a controller 906, and a transceiver 908. The processor 902, the memory 904, the controller 906, or the transceiver 908, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as describedherein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.

[0131] The processor 902, the memory 904, the controller 906, or the transceiver 908, or various combinations or components thereof may be implemented in hardware (e.g., circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.

[0132] The processor 902 may include an intelligent hardware device (e.g., a general- purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some implementations, the processor 902 may be configured to operate the memory 904. In some other implementations, the memory 904 may be integrated into the processor 902. The processor 902 may be configured to execute computer-readable instructions stored in the memory 904 to cause the NE 900 to perform various functions of the present disclosure.

[0133] The memory 904 may include volatile or non-volatile memory. The memory 904 may store computer-readable, computer-executable code including instructions when executed by the processor 902 cause the NE 900 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such the memory 904 or another type of memory. Computer-readable media includes both non- transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.

[0134] In some implementations, the processor 902 and the memory 904 coupled with the processor 902 may be configured to cause the NE 900 to perform one or more of the functions described herein (e.g., executing, by the processor 902, instructions stored in the memory 904). For example, the processor 902 may support wireless communication at the NE 900 in accordance with examples as disclosed herein. The processor 902 may be configured to or operable to support a means for: transmitting, to a UE, a configuration, and performing a RRC connection establishment procedure with the UE according to thetransmited configuration and based on a user-specific timing, wherein the user-specific timing is based on an unavailability of a GNSS.

[0135] The controller 906 may manage input and output signals for the NE 900. The controller 906 may also manage peripherals not integrated into the NE 900. In some implementations, the controller 906 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 906 may be implemented as part of the processor 902.

[0136] In some implementations, the NE 900 may include at least one transceiver 908. In some other implementations, the NE 900 may have more than one transceiver 908. The transceiver 908 may represent a wireless transceiver. The transceiver 908 may include one or more receiver chains 910, one or more transmiter chains 912, or a combination thereof.

[0137] A receiver chain 910 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 910 may include one or more antennas for receive the signal over the air or wireless medium. The receiver chain 910 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain 910 may include at least one demodulator configured to demodulate the receive signal and obtain the transmited data by reversing the modulation technique applied during transmission of the signal. The receiver chain 910 may include at least one decoder for decoding the processing the demodulated signal to receive the transmited data.

[0138] A transmiter chain 912 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmiter chain 912 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 like phase-shift keying (PSK) or quadrature amplitude modulation (QAM). The transmiter chain 912 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmiter chain 912 may also include one or more antennas for transmiting the amplified signal into the air or wireless medium.

[0139] Figure 10 illustrates a flowchart of a method 1000 in accordance with aspects of the present disclosure. The operations of the method 1000 may be implemented by a UE as described herein. In some implementations, a UE 700 may execute a set of instructions to control the function elements of a processor to perform the described functions.

[0140] At 1002, the method may include receiving, from a network entity, a configuration. The operations of 1002 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1002 may be performed by a UE as described with reference to Figure 7.

[0141] At 1004, the method may include determining an unavailability of a GNSS. The operations of 1004 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1004 may be performed by a UE as described with reference to Figure 7.

[0142] At 1006, the method may include calculating, based on the unavailability of the GNSS, a UE-specific timing to perform a connection procedure with the network entity. The operations of 1006 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1006 may be performed by a UE as described with reference to Figure 7.

[0143] At 1008, the method may include performing the connection procedure according to a configuration and based on the calculated UE-specific timing. The operations of 1008 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1008 may be performed by a UE as described with reference to Figure 7.

[0144] Figure 11 illustrates a flowchart of another method 1100 in accordance with aspects of the present disclosure. The operations ofthe method 1100 may be implemented by a NE as described herein. In some implementations, a NE 900 may execute a set of instructions to control the function elements of a processor to perform the described functions.

[0145] At 1102, the method may include transmitting, to a UE, a configuration. The operations of 1102 may be performed in accordance with examples as described herein.In some implementations, aspects of the operations of 1102 may be performed by a NE as described with reference to Figure 9.

[0146] At 1104, the method may include performing a connection procedure with the UE according to the transmitted configuration and based on a UE -specific timing, wherein the UE-specific timing is based on an unavailability of a GNSS. The operations of 1104 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1104 may be performed by a NE as described with reference to Figure 9.

[0147] It should be noted that the methods described herein describe possible implementations, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.

[0148] The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.

Claims

CLAIMSWhat is claimed is:1 . A user equipment (UE), comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the UE to: receive, from a network entity, a configuration; determine an unavailability of a global navigation satellite system (GNSS); calculate, based on the unavailability of the GNSS, a UE-specific timing to perform a connection procedure with the network entity; and perform the connection procedure according to a configuration and based on the calculated UE-specific timing.

2. The UE of claim 1, wherein the at least one processor is configured to cause the UE to receive the configuration during an idle state of the UE.

3. The UE of claim 1, wherein the configuration comprises an indication to pause transmission for a duration corresponding to the unavailability of the GNSS.

4. The UE of claim 1, wherein the configuration comprises an indication to activate or deactivate a time window corresponding to the calculated UE-specific timing.

5. The UE of claim 1, wherein the at least one processor is configured to cause the UE to receive an indication to refrain from performing the connection procedure for a duration based on the UE being in an idle state.

6. The UE of claim 1, wherein the at least one processor is configured to cause the UE to receive a paging message that includes an indication to extend a period associated with an idle state of the UE.

7. The UE of claim 1, wherein the at least one processor is configured to cause the UE to receive an indication to store at least one location estimate of the GNSS for a duration based on the UE being in an idle state.

8. The UE of claim 7, wherein the configuration indicates a validity duration associated with at least one location estimate of the GNSS, wherein the at least one processor is configured to cause the UE to: store the at least one location estimate of the GNSS for the duration based on the UE being in the idle state and the indicated validity duration, wherein the duration comprises the validity duration.

9. The UE of claim 1, wherein the at least one processor is configured to cause the UE to receive the configuration via dedicated higher layer signaling during a connected mode of the UE.

10. The UE of claim 1, wherein the at least one processor is configured to cause the UE to receive the configuration via a paging message during an idle state of the UE.

11. The UE of claim 1, wherein the configuration comprises an indication to use one or more stored location estimates of the GNSS for the connection procedure based on a validity duration associated with each of the one or more stored location estimates of the GNSS, and wherein the one or more stored location estimates of the GNSS correspond to one or more estimated locations of the UE.

12. The UE of claim 1, wherein the at least one processor is configured to cause the UE to receive an indication to use a last known location of the GNSS for time synchronization.

13. The UE of claim 1, wherein the at least one processor is configured to cause the UE to receive an indication of a method for estimating a UE location, wherein the UE -specific timing is further calculated based on the estimated UE location.

14. The UE of claim 1, wherein the configuration comprises a table that maps a location estimate corresponding to a zone of a cell.

15. The UE of claim 14, wherein the configuration comprises an index corresponding to a row of the table, and wherein the row indicates the location estimate corresponding to the zone of the cell.

16. The UE of claim 15, wherein the at least one processor is configured to cause the UE to select a location estimate based on the index corresponding to the row of the table, and wherein the UE-specific timing is calculated based on the selected location estimate.

17. A method for wireless communication at a user equipment (UE), the method comprising: receiving, from a network entity, a configuration; determining an unavailability of a global navigation satellite system (GNSS); calculating, based on the unavailability of the GNSS, a UE-specific timing to perform a connection procedure with the network entity or the GNSS; and performing the connection procedure according to a configuration and based on the calculated UE-specific timing.

18. A base station, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the base station to: transmit, to a user equipment (UE), a configuration; and perform a connection procedure with the UE according to the transmitted configuration and based on a UE-specific timing, wherein the UE- specific timing is based on an unavailability of a global navigation satellite system (GNSS).

19. The base station of claim 18, wherein the configuration comprises an indication to pause transmission for a duration corresponding to the unavailability of the GNSS.

20. The base station of claim 18, wherein the configuration comprises an indication to activate or deactivate a time window corresponding to the UE -specific timing.

21. The base station of claim 18, wherein the at least one processor is configured to cause the base station to transmit a paging message that includes an indication to extend a period associated with an idle state of the UE.

22. The base station of claim 18, wherein the at least one processor is configured to cause the base station to transmit an indication to store at least one location estimate of the GNSS for a duration.

23. The base station of claim 22, wherein the configuration indicates a validity duration associated with at least one location estimate of the GNSS.

24. The base station of claim 18, wherein the at least one processor is configured to cause the base station to transmit the configuration via dedicated higher layer signaling.

25. The base station of claim 18, wherein the configuration comprises an indication to use one or more stored location estimates of the GNSS for the connection procedure based on a validity duration associated with each of the one or more stored location estimates of the GNSS, and wherein the one or more stored location estimates of the GNSS correspond to one or more estimated locations of the UE.

26. The base station of claim 18, wherein the at least one processor is configured to cause the base station to transmit an indication to use a last known location of the GNSS for time synchronization with the UE.

27. The base station of claim 18, wherein the at least one processor is configured to cause the base station to transmit an indication of a method for estimating a UE location, wherein the UE-specific timing is further based on the estimated UE location.

28. The base station of claim 18, wherein the configuration comprises a table that maps a location estimate corresponding to a zone of a cell.

29. The base station of claim 28, wherein the configuration comprises an index corresponding to a row of the table, and wherein the row indicates the location estimate corresponding to the zone of the cell.

30. A method for wireless communication at a base station, the method comprising: transmitting, to a user equipment (UE), a configuration; and performing a connection procedure with the UE according to the transmitted configuration and based on a UE-specific timing, wherein the UE-specific timing is based on an unavailability of a global navigation satellite system (GNSS).

Images