Establishment of connections based on satellite unavailability

Abstract

Various aspects of this disclosure relate to methods, apparatus, and devices for wireless communication. A user equipment (UE) can receive (1002) configuration from a network entity. The UE can determine (1004) the unavailability of a Global Navigation Satellite System (GNSS) and calculate (1006) a user-specific timing for performing a Radio Resource Control (RRC) connection establishment procedure based on the unavailability of the GNSS. The UE can perform (1008) the RRC connection establishment procedure according to the received configuration and based on the calculated user-specific timing.

Description

Technical Field

[0001] This disclosure relates to wireless communication, and more specifically to establishing a connection based on a connection establishment process and on the availability (e.g., unavailability) of a network entity (e.g., a satellite) in a wireless communication system (e.g., a satellite communication system). Background Technology

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

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

[0004] Various aspects of this disclosure relate to wireless communications. One or more of the NE and UE may be configured, capable of, or operable to perform the operations and signaling described herein. For example, one or more NEs and UEs may support the management (e.g., establishment) of connections with terrestrial network entities (e.g., base stations) and / or non-terrestrial network entities (e.g., satellites) based on the unavailability of NTN network entities. The UE may receive configuration from the network entity; determine the unavailability of the Global Navigation Satellite System (GNSS); calculate UE-specific timing (also known as user-specific timing) for performing connection procedures (e.g., Radio Resource Control (RRC) connection establishment procedures) based on the GNSS unavailability; and perform the connection procedures according to the received configuration and based on the calculated UE-specific timing. Attached Figure Description

[0005] Figure 1 Examples of wireless communication systems according to various aspects of this disclosure are illustrated.

[0006] Figure 2 An example of timing relationships in a wireless communication system according to various aspects of this disclosure is illustrated.

[0007] Figure 3 An example of a process used during satellite unavailability according to various aspects of this disclosure is illustrated.

[0008] Figure 4 An example of communication with an extended idle state during satellite unavailability is illustrated according to various aspects of this disclosure.

[0009] Figure 5 An example of a process for using a stored location estimate in a process according to various aspects of this disclosure is illustrated.

[0010] Figure 6 An example of a system with SSB-based reference position mapping according to various aspects of this disclosure is illustrated.

[0011] Figure 7 Examples of UEs according to various aspects of this disclosure are illustrated.

[0012] Figure 8 Examples of processors according to various aspects of this disclosure are illustrated.

[0013] Figure 9 Examples of network devices (NEs) according to various aspects of this disclosure are illustrated.

[0014] Figure 10 The diagram illustrates a flowchart of a method performed by a UE according to various aspects of this disclosure.

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

[0016] In wireless communication systems, the UE can rely on satellite systems, such as Global Navigation Satellite Systems (GNSS), to determine the location of the UE and / or GNSS, and facilitate the Radio Resource Control (RRC) establishment process. However, in some situations, GNSS may become unavailable to the UE, such as in environments with weak or obstructed satellite signals. During these periods of unavailability, the UE may repeatedly attempt to connect to the GNSS, leading to increased power consumption and degraded system performance. This inefficiency poses a challenge to maintaining optimal UE operation, especially in power-sensitive or performance-critical applications.

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

[0018] By delaying communication during periods of GNSS unavailability, the UE can achieve several key advantages. First, reducing unnecessary communication attempts significantly lowers power consumption, thereby extending battery life. Second, system performance is improved because the UE avoids inefficient resource allocation during GNSS outages. Overall, these improvements contribute to increased efficiency and reliability of the communication system, particularly in challenging environments with inconsistent GNSS availability.

[0019] Various aspects of this disclosure are described in the context of wireless communication systems.

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

[0021] One or more NEs 102 may be distributed throughout a geographic area to form a wireless communication system 100. The one or more NEs 102 described herein may be, include, or may be referred to as network nodes, base stations, network elements, network functions, network entities, radio access networks (RANs), NodeBs, eNodeBs (eNBs), next-generation NodeBs (gNBs), or other suitable terms. NEs 102 and UEs 104 may communicate via a communication link, which may be a wireless or wired connection. For example, NEs 102 and UEs 104 may perform wireless communication (e.g., receiving signaling, sending signaling) via a Uu interface.

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

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

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

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

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

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

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

[0029] The wireless communication system 100 may support one or more parameter sets, and the parameter sets may include subcarrier spacing and cyclic prefixes. The first parameter set (e.g., μ=0) can be associated with the first subcarrier spacing (e.g., 15 kHz) and the regular cyclic prefix. In some implementations, the first set of parameters (e.g., ) associated with the first subcarrier spacing (e.g., 15 kHz) is... μ =0) can utilize one time slot per subframe. The second parameter set (e.g., μ =1) can be associated with the second subcarrier spacing (e.g., 30 kHz) and the regular cyclic prefix. The third parameter set (e.g., μ =2) can be associated with the third subcarrier spacing (e.g., 60 kHz) and the regular cyclic prefix or extended cyclic prefix. The fourth parameter set (e.g., μ =3) can be associated with the fourth subcarrier spacing (e.g., 120 kHz) and the regular cyclic prefix. The fifth parameter set (e.g., μ =4) can be associated with the fifth subcarrier spacing (e.g., 240 kHz) and the regular cyclic prefix.

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

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

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

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

[0034] In some implementations, the wireless communication system 100 can be an NR NTN or an IoT NTN. UE 104 can access the NR NTN and / or IoT NTN based on its Global Navigation Satellite System (GNSS) capability. UE 104 can use GNSS coordinates to determine its location, which can be used for pre-compensation of time and frequency offsets. NR-NTN can use an open-loop timing adjustment process for a transparent payload NTN architecture, where timing advance (TA) is divided into a common TA (e.g., corresponding to the feeder link round-trip time (RTT)) and a user-specific TA (e.g., corresponding to the bidirectional transmission delay on the serving link). To estimate the user-specific TA, UE 104 can identify the serving satellite location (e.g., information provided to UE 104) and determine its location (e.g., based on GNSS). Due to the continuous movement of non-geostationary orbit (NGSO) satellites, UE 104 may need to continuously update its TA and frequency pre-compensation in connected mode. Therefore, UE 104 may need to establish a reliable GNSS connection throughout its connected time period for NTN access.

[0035] While GNSS provides highly accurate position and time references, there may be multiple instances and / or scenarios where GNSS signals are unavailable for a certain duration. For example, GNSS signals may be interrupted, interfered with, or spoofed, resulting in inaccurate location for UE 104. This inaccuracy can therefore lead to NTN connection rejection, as the user-specific TA derived from UE 104's incorrect location may impede uplink (UL) communication. Such scenarios may simultaneously affect a group of UEs in the cell for a certain duration. Furthermore, there may be instances where UE 104 experiences NTN service degradation due to a relatively reduced accuracy in GNSS position estimation (e.g., accuracy reduced to 300m). This degradation can stem from various reasons, such as poor GNSS link budget, insufficient number of satellites, or the location of UE 104 (e.g., in a pocket, bag, etc.).

[0036] Due to the temporary unavailability and / or inaccuracy of GNSS location, degradation or rejection of NR NTN services may result in excessive power consumption and overall system performance degradation for UE104. This is because UE104, configured with GNSS capability, may continue to attempt to connect to GNSS, even when the GNSS location is unavailable due to spoofing or interference. If the network knows that GNSS signals are temporarily unavailable within its coverage area, the network may prevent UE104 from establishing a connection for a temporary period or provide an alternative timing synchronization method. When GNSS is temporarily unavailable for UE104 or a group of UE104, various methods and related signaling aspects for timing synchronization can be used when UE104 is idle or attempting to establish a new connection.

[0037] Timing adjustments can be made in the NT. Furthermore, time and frequency synchronization in the NTN can be performed as described in this article.

[0038] Downlink (DL) and UL frames can be aligned at the UL time synchronization reference point (RP), with the offset determined by the NTA. offset Given. To accommodate the propagation delay in NTN, a common TA and two offsets can be used. K offset and k mac This enhances several timing relationships. The common TA can be a configured timing offset, which can be equal to the RTT between the RP and NTN payloads. K offset It can be a configured scheduling offset, which can be greater than or equal to the sum of the service link RTT and the common TA. k mac It can be a configured offset, which can be approximately equal to the RTT between RP and gNB (e.g., when rounded to an integer, tenths, thousandths, etc.).

[0039] Scheduling offset K offset This can be used to allow UE 104 sufficient processing time between DL reception and UL transmission. Offset k mac It can be used for the application of DL configuration indicated by Media Access Control (MAC) control element (CE) commands on the delayed physical downlink shared channel (PDSCH) and the estimation of UE-gNB RTT. This offset can be provided by the wireless communication system 100 when the DL and UL frame timings are not aligned at NE 102 (e.g., the base station). k macIt can also be used during the random access procedure to determine the start time of the random access response (RAR) window and / or random access message window following the transmission of another random access message (e.g., Msg1 and / or MsgA transmission).

[0040] Figure 2 An example of timing relationships in a wireless communication system 200 is illustrated. The wireless communication system 200 can implement the references described herein. Figure 1 The wireless communication system 100 may be implemented in various aspects thereof. For example, the wireless communication system 200 may include NE 102-a and NE 102-b, which may be referenced herein. Figure 1 The example of NE 102 described herein. Wireless communication system 200 may include UE 104-a, which may be referenced herein. Figure 1 Example of UE 104.

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

[0042] The NE 102-b can be configured with Hybrid Automatic Repeat Request (HARQ) operation. For example, the network can enable or disable DL HARQ feedback for each HARQ procedure. In some implementations, disabling DL HARQ feedback allows HARQ procedures to be scheduled before a HARQ RTT has elapsed since the last scheduled HARQ procedure. The network can also configure ULHARQ modes (e.g., HARQ mode A, HARQ mode B) for each HARQ procedure. HARQ mode B allows HARQ procedures to be scheduled before a HARQ RTT has elapsed since the last scheduled HARQ procedure.

[0043] For HARQ procedures configured with enabled and / or disabled HARQ feedback, NE 102-b ensures the correct configuration (e.g., all enabled or all disabled) of HARQ feedback for HARQ procedures used by semi-persistent scheduling (SPS) configuration. For HARQ procedures configured with HARQ modes, NE 102-b ensures the correct configuration of HARQ modes (e.g., all HARQ mode A or all HARQ mode B) for HARQ procedures used by configuration authorization (CG) configuration.

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

[0045] UE 104-a can calculate the frequency Doppler shift of the serving link and autonomously pre-compensate for it in UL transmissions by taking into account UE 104-a's location and ephemeris. If UE 104-a does not have a valid GNSS location and / or a valid ephemeris and common TA, it may not send UL transmissions until both are restored.

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

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

[0048] In various configurations, the transmission timing adjustment process for terrestrial networks (TN) and NTN can be performed as described in this document.

[0049] UE 104-a can obtain the TA offset value of the serving cell through the n-TimingAdvanceOffset of the serving cell. N TA,offsetIf UE 104-a is not provided with the n-TimingAdvanceOffset of the serving cell, then UE 104-a determines the default value of the timing advance offset for the serving cell. N TA,offset If UE 104-a is configured with two UL carriers for the serving cell, then the same TA offset value... N TA,offset This applies to both carriers.

[0050] When receiving a TA command for a TA group (TAG), UE 104-a uses a value that the UE expects to be the same for all serving cells in the TAG. N TA,offset Furthermore, based on the received timing advance command, the uplink timing of the Physical Uplink Shared Channel (PUSCH), SRS, and / or Physical Uplink Control Channel (PUCCH) transmissions on all serving cells in the TAG is adjusted, wherein the uplink timing of the PUSCH, SRS, and / or PUCCH transmissions is the same for all serving cells in the TAG.

[0051] For a frequency band with Synchronous Continuous In-Band Evolved Non-Independent Dual Connectivity (EN-DC) in a frequency band combination with an inapplicable maximum transmit timing difference requirement, if UE 104-a indicates ul-TimingAlignmentEUTRA-NR as 'Required', and UE 104-a determines that the uplink transmission timing based on the timing adjustment indications from the TAG from the Primary Cell Group (MCG) and the TAG from the Secondary Cell Group (SCG) are different, then UE 104-a adjusts the transmission timing of PUSCH, SRS, and / or PUCCH transmissions on all serving cell portions of the frequency band belonging to Synchronous Continuous In-Band EN-DC based on the timing adjustment indication from the serving cell's TAG in the MCG within the frequency band. When PUSCH, SRS, and / or PUCCH overlap or even partially overlap with a random access preamble transmitted in another CG in time, UE 104-a anticipates not transmitting PUSCH, SRS, and / or PUCCH on one CG.

[0052] For 2 μ • 15 kHz SCS, TA command for TAG at 16.64. T c / 2 μ The multiple indicates the change in UL timing relative to the current UL timing of the TAG. The start timing of the random access preamble can be determined.

[0053] TA commands used for random access responses or absolute timing advance commands in MAC CE. TA For TAG, through T A The index values ​​= 0, 1, 2, ..., 3846 indicate... N TA Values, where the subcarrier spacing (SCS) is 2. μ • 15 kHz TAG, time alignment amount is . N TA It is defined relative to the SCS of the first UL transmission after the UE 104-a receives the random access response or absolute timing advance command MAC CE.

[0054] In some configurations, the TA command is used for TAGs. T A pass T A The index values ​​= 0, 1, 2, ..., 63 indicate the current... N TA value N TA_old Adjust to new N TA value N TA_new For 2 μ • 15 kHz SCS, .

[0055] If UE 104-a has multiple active UL bandwidth portions (BWPs) in the same TAG, including UL BWPs in two UL carriers of the serving cell, then the timing advance command value is relative to the largest SCS of the multiple active UL BWPs. Applicable to UL BWPs with lower SCS. N TA_new The value can be rounded to align with the TA granularity of the UL BWP with a lower SCS, while still meeting TA accuracy requirements.

[0056] Will N TA The positive or negative value indicates the amount by which the uplink transmission timing for the TAG will be advanced or delayed.

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

[0058] If UE 104-a changes the active UL BWP between the time the TA command is received and the time the corresponding adjustment to the UL transmission timing is applied, UE 104-a determines the TA command value based on the SCS of the new active UL BWP. If UE 104-a changes the active UL BWP after the adjustment to the UL transmission timing has been applied, UE 104-a assumes that the active UL BWP has the same absolute TA command value before and after the change.

[0059] If the received DL timing changes, and compensation is made solely through UL timing adjustment or only partially compensated without a TA command, the UE will change accordingly. N TA .

[0060] If two adjacent time slots overlap due to a TA command, the duration of the later time slot is shortened relative to the earlier time slot. This duration remains unchanged during the actual transmission time window of the UE's PUSCH or PUCCH transmission. N TA .

[0061] Using the high-level ephemeris parameters of the serving satellite (if provided), UE 104-a can determine its location based on the location of the serving satellite and its own location. To pre-compensate for bidirectional transmission delay on the service link. To pre-compensate for bidirectional transmission delay between the UL time synchronization reference point and the serving satellite, UE 104-a is based on the one-way propagation delay determined by UE 104-a as follows. Determine :

[0062]

[0063] in , and Provided by ta-Common, ta-CommonDrift, and ta-CommonDriftVariant respectively. t epoch Provided by epochTime, which is the epoch time of ta-Common, ta-CommonDrift, and ta-CommonDriftVariant. The time synchronization between the service satellite and the uplink time synchronization reference point t The distance divided by the speed of light. The uplink time synchronization reference points are DL and UL, and are determined by... N TA,offset The given offset is at the point of frame alignment.

[0064] RRC signaling can be used for TA calculation in NTN. Information elements (IEs) for NTN configuration (e.g., NTN-Config IEs) may exist, containing basic parameter information needed to calculate common TAs and user-specific information. An implementation of the NTN-Config IE is shown in Table 1, and the NTN-Config fields are described in Table 2. Table 1: NTN-Config IE Table 2: NTN-Config Field Descriptions

[0065] In the NR NTN transparent payload architecture, the UE pre-compensates for bidirectional transmission delay on the serving link based on its TA calculation, which is determined by the UE using the serving satellite location and its own location. The TA is determined using the following formula (referred to as the open-loop TA procedure):

[0066]

[0067] in N TA This represents the TA component based on accumulated "TA commands" received from the network (e.g., via MAC CE commands), and it is reset to zero whenever a Random Access Channel (RACH) procedure is performed to obtain the TA estimate. This represents the TA component specific to satellite communications and is determined by the UE based on its own location and the ephemeris of the NTN serving satellites. The accuracy depends on the accuracy of the location information.

[0068] In some configurations, NR NTN UEs have GNSS capabilities and use GNSS to calculate their own position. However, GNSS can be vulnerable to spoofing and interference. Spoofing can lead to incorrect position reports and potential service rejection, while temporary interference (e.g., during the period of spoofing and interference) can also cause service rejection. Furthermore, natural phenomena such as solar radiation bursts that can affect large areas of the Earth's surface for 10 to 20 minutes can also cause temporary unavailability of GNSS signals, resulting in service rejection.

[0069] The various embodiments found in this document provide potential enhancements to UE pre-compensation for UL timing adjustment, such as in the following two scenarios where GNSS accuracy or availability is temporarily reduced: 1) during idle mode; or 2) during initial access. One or more of the following can be performed: 1) suspending message 1 (Msg1) transmission for a temporary period when GNSS location estimation may be unavailable due to spoofing or interference, particularly for UEs establishing RRC connections from non-connected states (including RRC idle and RRC inactive); 2) extending the idle state duration; 3) updating and storing the GNSS location in the idle state using an effectiveness timer; and / or 4) providing alternative means for calculating the location estimation.

[0070] In a first embodiment, Msg1 preamble transmission can be suspended during GNSS unavailability. According to the first embodiment, a GNSS-capable UE, upon request from the Non-Access Stratum (NAS) layer, will not transmit the Msg1 preamble for a specified duration (e.g., upon receiving a NAS Protocol Data Unit (PDU) when GNSS is unavailable or the location accuracy is below a predefined accuracy value). In one implementation, the first embodiment applies to a UE performing an initial access procedure to transition from an RRC disconnected state to a connected state. For example, if a UE is in an RRC disconnected state and wants to enter an RRC connected state, the UE can acquire and use the serving cell's NTN System Information Block (SIB). The network may include a timer configuration in the NTN SIB that specifies the minimum and / or maximum time the UE can be allowed to wait before transmitting Msg1.

[0071] Figure 3 An example of process 300 used during satellite (e.g., GNSS) unavailability is illustrated according to various aspects of this disclosure. In some implementations, process 300 may implement reference... Figure 1 and Figure 2 Aspects of the described wireless communication system 100 and wireless communication system 200, or those implemented therein, are described. Process 300 may include a gNB 302, which may be an example of NE 102 as described herein. Process 300 may also include a UE 304, which may be an example of UE 104 as described herein. In the following description of process 300, operations between gNB 302 and UE 304 may be transmitted in a different order than the example order shown, or operations performed by gNB 302 and UE 304 may be performed in a different order or at different times. Some operations may also be omitted from process 300, and other operations may be added to process 300.

[0072] At 306, gNB 302 can send a synchronization signal block (SSB) to UE 304. UE 304 can perform DL time and / or frequency synchronization and / or Master Information Block (MIB) detection.

[0073] At 308, gNB 302 can send control resource set (CORESET) #0 to UE 304. UE 304 can perform SIB detection and can receive physical RACH (PRACH) resources, common TA parameters, satellite ephemeris tables, and / or timer configurations.

[0074] At 310, UE 304 can start a timer to pause Msg1 transmission and / or look for improvements in GNSS signal and location inaccuracies within the timing window.

[0075] At 312, UE 304 can send the Msg1 preamble to gNB 302. For example, if UE 304 is available after or within a timing window, it can use the common TA in the SIB and a self-estimated UE-specific TA for the preamble.

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

[0077] In one embodiment, the duration of the timer window can represent the configured duration for which the UE 304 will not perform the RACH procedure. For example, after detecting an SSB and reading the MIB and CORESET#0 parameters, the UE will pause the Msg1 preamble for the configured time or pause GNSS signals for the configured duration, and only perform the RACH procedure after the timer expires. If there is no GNSS interference or spoofing, the network can adjust the timer value based on its understanding of the expected interference and spoofing durations (e.g., the timer is set to zero). If the timer is set to zero, the UE will perform the RACH procedure without any pauses and / or delays. This implementation allows the UE to conserve energy by not attempting to perform the RACH procedure (or detect GNSS signals) repeatedly during periods of interference or spoofing.

[0078] In some embodiments, the original equipment manufacturer (OEM) sends information about the duration of GNSS interference and / or spoofing to NG-RAN nodes (e.g., gNB) or the core network (e.g., AMF). In such embodiments, the core network (e.g., AMF) has information about GNSS spoofing and / or interference and their expected duration, and the core network (e.g., AMF) can then indicate this information to the NG-RAN nodes (e.g., gNB).

[0079] In various embodiments, the duration of the timer can represent the period during which UE 304 can pause the Msg1 preamble based on the detected SSB. During this window, UE 304 can continue searching for a GNSS signal, and UE 304 can transmit the Msg1 preamble after the GNSS signal is available or the GNSS position accuracy reaches a desired threshold. In one implementation, if the GNSS signal or accurate position is available within the timer window, UE 304 can transmit the Msg1 preamble before the timer expires. In another implementation, even if the GNSS signal is available before the timer expires, UE 304 can transmit the Msg1 preamble only after the timer window expires.

[0080] In some embodiments, UE 304 may require a new timer value to be specified and / or predetermined to pause Msg1 preamble transmission. Indications to activate or deactivate the window may be indicated during initial access (e.g., in the Physical Downlink Control Channel (PDCCH) and / or Downlink Control Information (DCI) of SIB1, SIB1, or NTN SIB).

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

[0082] In a second embodiment, the idle state duration can be extended. According to the second embodiment, whenever the network detects and / or becomes aware of a GNSS interference or spoofing event, the network instructs the idle UE to remain in the idle state for a certain duration via an idle state extension timer. Upon receiving such an instruction, the UE will not perform a RACH procedure until the indicated timer expires. For example, the UE may be instructed to have an idle state extension timer during the idle state period. The UE will start the timer in the idle state and 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 necessary, or enter a disconnected state if the GNSS signal is still poor.

[0083] In one example, the idle state extension timer does not bind the UE from the idle state to the connected state, but rather implicitly indicates to the UE that the GNSS signal may be unavailable during the extended idle state period. For example, after receiving the idle state extension timer indication, the UE will begin monitoring its GNSS signal status, and once the UE has good signal strength or GNSS positioning accuracy above a threshold, the UE can perform a RACH procedure within the extended idle state window if needed.

[0084] In some embodiments, the network may extend the idle state extension window multiple times during the idle state for a fixed or variable duration. For example, the network may instruct the UE to extend the idle state for a certain duration. However, if the network realizes that the idle state needs to be extended further, the network may indicate this to the UE using another idle state extension timer indication.

[0085] Figure 4 An example of communication 400 with an idle state extension during satellite unavailability (e.g., when no GNSS is available) according to various aspects of this disclosure is illustrated. The timing of the UE state includes idle state 402, idle state extension 404 (first extension), idle state extension 406 (second extension), and action execution 408 (performing a RACH procedure, remaining in the idle state, or entering a disconnected state). The UE receives 410 an idle state extension timer indication to create 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 idle state extension 406.

[0086] In one embodiment, an idle state extension timer is indicated to the UE or UE group 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 containing information to activate and / or indicate the idle state extension timer. In one implementation, the idle state extension timer information can be used to enhance DCI format 1_0 with a cyclic redundancy period (CRC) scrambled by a paging radio network temporary identifier (P-RNTI). For example, a short message can be used to indicate the activation or deactivation of the idle state extension timer, or the duration of the idle state extension. In one implementation, if GNSS signals are available during the idle state extension period, the network can indicate whether the UE or UE group can initiate a RACH procedure. In another implementation, a field is used in the RRC paging message used to trigger RRC establishment (e.g., RRC request and RRC connection recovery) to indicate when the RRC establishment will be resumed after the message is received. For example, if the UE receives an RRC establishment trigger message, a time period can be configured in that message to indicate when the RACH procedure will be initiated after the message is received (e.g., after 1 second (essentially a delay indication for establishing an RRC connection)). Without such a field, the UE can initiate the RACH procedure immediately after receiving the message.

[0087] In one embodiment, when the idle state extension timer is active for all UEs in a cell (e.g., if the beam corresponds to a cell and / or the cell size is small, or interference and / or spoofing is affecting the entire cell), the activation and / or deactivation or duration of the idle state extension timer can be indicated by a broadcast message (e.g., using NTN SIB).

[0088] In a third embodiment, the GNSS position can be updated and / or stored while the UE is in an idle state. According to the third embodiment, the GNSS position estimate can be valid for a certain duration within the idle state, and if the RACH procedure is performed within the GNSS validity duration, the GNSS position estimate can be used in the RACH procedure to calculate user-specific timing advances. This GNSS position estimate validity duration can represent the idle UE checking its GNSS position and starting a timer corresponding to the GNSS validity duration of its GNSS position estimate. After the timer expires, the UE (if still in an idle state) can search for a new GNSS position estimate and start a GNSS validity timer for its new GNSS position estimate until the timer expires. The UE can continue to repeat this process while remaining in an idle state. In one implementation, if the UE wants to transition from an idle state to an RRC connected state, the UE can search for a new GNSS position estimate to enable the transmission of the Msg1 preamble, and if the GNSS position estimate is unavailable, the UE can use the last GNSS position estimate within the GNSS validity duration to calculate user-specific timing advances. In another implementation, the UE can always use the GNSS position estimate within the GNSS validity duration to calculate user-specific timing advances.

[0089] In some implementations, the UE starts or restarts a configurable validity timer each time its location is acquired with minimum threshold accuracy. If the validity timer is running (e.g., not considered expired) when Msg1 is expected to be transmitted, the UE can have its UE-specific TA for the serving link calculated based on the most recent valid location. If the timer is considered to have expired when Msg1 is expected to be transmitted, the UE can acquire its location first. If it fails to acquire its location, or if the acquired location is deemed inaccurate, the UE can either not initiate RRC connection establishment and / or recovery, or use the default value of the UE-specific TA for the serving link. The default value can be configured by the network and can be a function of one or more of the following: 1) the UE's last known location; and / or 2) the UE's measurements of the serving cell and / or neighboring cells.

[0090] In various implementations, the UE periodically acquires its location. If the accuracy of the acquired location is higher than a certain minimum threshold, the UE can initiate RRC connection establishment and / or recovery upon request from an upper layer (e.g., NAS). However, if the accuracy of the acquired location is lower than a certain minimum threshold, the UE can try to acquire the location again before the next periodic opportunity. If no sufficiently accurate location is available, the UE can acquire its location first. If it fails to acquire its location, or if the acquired location is deemed insufficiently accurate, the UE can either not initiate RRC connection establishment (avoiding execution for a period of time) and / or recovery, or use a default value for the UE-specific TA for the serving link. The default value can be configured by the network and can be a function of one or more of the following: 1) the UE's last known location; and / or 2) the UE's measurements of the serving cell and / or neighboring cells.

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

[0092] At 506, UE 502 can obtain its GNSS position estimate and can start a GNSS position estimate validity timer for GNSS idle state validity duration 508.

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

[0094] At position 512, the validity timer for the new GNSS position estimation may expire.

[0095] At 514, RRC establishment triggering can be executed as part of the RRC establishment process, where UE 502 can attempt to acquire a new GNSS position estimate (if unavailable) and can use the GNSS position estimate within the validity duration.

[0096] In one embodiment, when the UE is in a connected state (before transitioning from a connected state to an idle state), the network can indicate to the UE the idle state validity duration of the GNSS position estimate using higher-layer signaling (e.g., RRC signaling), group common signaling, or via SIB. One or more validity durations can exist throughout the idle period, where these multiple validity durations can have fixed durations or variable durations (e.g., not the same duration), and can depend on many factors such as UE mobility, satellite orbits, etc. In one implementation, if multiple validity durations have a variable nature in the idle state, the network can configure only a first duration of the idle state GNSS position estimate validity in the connected state, and can also use RRC, MAC CE, or DCI signaling to indicate that this duration is valid within the configured period (e.g., if the idle period is longer than the GNSS validity duration, the duration may not repeat). In this implementation, if the GNSS validity duration is shorter than the idle state duration, the GNSS position estimate may not be used for user-specific timing calculations after the timer expires. If needed, the network can configure a new validity duration for the new GNSS position estimate in the idle state. In another implementation, the network can configure multiple validity durations in connected mode using RRC and / or MAC CE signaling. These validity durations are used in idle mode, where the UE can acquire a new GNSS position estimate for each validity duration. For example, if two validity durations of 2 minutes and 4 minutes are configured, the UE can acquire a GNSS position estimate upon entering idle mode, and the GNSS position estimate is valid for up to 2 minutes. After 2 minutes, the UE can acquire a new GNSS position estimate that is valid for up to 4 minutes. In one implementation, a single GNSS validity duration is configured for the entire idle period, and this single GNSS validity duration can be configured to the UE in connected mode using RRC signaling. This means that the GNSS position estimate is valid within the configured period, and the UE can acquire a new GNSS position estimate after the configured period expires and verify the newly acquired GNSS position estimate again for the same validity period.

[0097] In some embodiments, the GNSS validity duration is configured in connected mode, while activation and / or deactivation are performed in idle mode. If activation is to be performed for the entire cell, activation and / or deactivation can be indicated to the UE using a paging message (e.g., using a short message) or a broadcast message (e.g., using an NTN SIB). In one implementation, the activation and / or deactivation and / or duration of the GNSS validity duration can be configured only in idle mode using transmissions to the UE or a group of UEs. Paging messages can be used for this purpose or via broadcast messages (e.g., NTN SIB). In one embodiment, the GNSS validity duration is coupled to a UL synchronization validity timer, where the UE can acquire a GNSS position estimate and use the same GNSS position estimate when the UL synchronization validity timer expires.

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

[0099] In one example, the network can also configure conditions that help the UE decide whether the last known location estimate can be used for the RACH procedure when the UE changes from an idle state to a connected state, from an unconnected state to a connected state, or during a connected state that requires a RACH procedure. For example, the network can define any of the following conditions: 1) Method usage condition: When GNSS signals are unavailable or the location estimate is below a location accuracy threshold, the UE only uses the last known location; 2) Last known location estimation method priority: A field can be defined to describe the priority and indicate to the UE the priority of using the last known location estimate—for example, if multiple methods are supported, such a field can define where the last known location method takes precedence over others; 3) Last location validity duration: The network can set a duration that indicates whether the last known location is valid for use in the RACH process—for example, an idle UE may need to establish a connection while using its last known location estimate. The UE can check its last known location estimate and corresponding timestamp, and can calculate the duration from the time the last known location was estimated. If the calculated duration is within the location validity duration, the UE can use it in the RACH process. Alternatively, the validity duration can also indicate to the UE when a new location estimate will be acquired and considered the last known location; and / or 4) Valid distance: A distance set by the network that indicates whether the UE has moved a considerable distance from the last known location. Such conditions can contribute to UE mobility. For example, a UE can calculate the distance traveled from its last known location and compare it to the validity distance. If it falls within the validity distance, the last known location estimate can be used. In one example, a combination of validity duration and validity distance can be used to check the validity of the last known location.

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

[0101] In various embodiments, the UE determines when the last known location will be used and the duration of its validity. 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 parameters that can help the UE determine the last known location and its duration of validity. For example, the network may set a GNSS position tolerance, and then the UE (based on its own GNSS readings) determines when the actual GNSS position deviates from the previous GNSS position beyond the indicated tolerance, and after such determination, the UE also determines whether to use the last known GNSS location.

[0102] In the fourth embodiment, timing synchronization can be performed during the RACH process without GNSS location estimation. According to the fourth embodiment, when GNSS location estimation is temporarily unavailable or its accuracy is lower than a predefined accuracy, the UE can employ other timing synchronization methods (e.g., methods not involving GNSS location estimation) when performing the RACH process (e.g., from unconnected to connected, from idle to connected, or while in a connected state). If interference or spoofing is present, the UE can be instructed to use other methods (e.g., by the serving network, or by the UE's default during GNSS unavailability, or when GNSS location accuracy is low, or after failing to obtain a sufficiently accurate location within a certain number of attempts or a period of time). These timing synchronization techniques may not provide accurate timing synchronization, but they can provide the UE with sufficient temporary timing synchronization to maintain a connected state until GNSS location estimation becomes available. If GNSS location estimation becomes available, the UE can switch back to the GNSS location estimation-based timing synchronization method.

[0103] In various embodiments, the network may indicate the duration for which other timing synchronization techniques are effective. This may be indicated to the UE when it is idle (e.g., via paging or as part of the SIB) or as part of initial access system information. The UE may apply other synchronization methods only for the indicated duration and may then attempt GNSS location-based synchronization. If GNSS location estimation remains unavailable, the UE may disconnect from the network until it obtains a GNSS location estimate with sufficient accuracy.

[0104] In a first implementation of the fourth embodiment, timing synchronization can be based on region-based location information. According to the first implementation of the fourth embodiment, the network divides the cell into different regions and provides a provisional location estimate for each region. If the UE GNSS location estimate is unavailable, these provisional location estimates are used in place of the UE GNSS location estimate to calculate user-specific timing. For example, a region-based mapping table as shown in Table 3 can be developed for the cell, where each region can be associated with at least one set of reference location coordinates, where the reference location can be any location within the region that best suits the cell type. For example, for an NGSO-based geostationary or quasi-geostationary cell, the reference location can be the center of the region. In one implementation, the location coordinates are represented in Cartesian coordinates (e.g., a position state vector in x, y, and z coordinates). In another implementation, the reference location coordinates are represented in orbital coordinates (e.g., in latitude and longitude). Table 3: Region-based Reference UE Location Mapping Table

[0105] In one embodiment, each region is associated with an SSB beam, where the region index can be an SSB index. For example, the coverage area of ​​an SSB can be considered a region, where the SSB can be beamformed in such a way that it covers the minimum coverage area on the ground. The network can calculate the coverage area coordinates while calculating the beamforming weights of the SSB. In this way, the network knows which region on Earth the SSB covers and how much it covers. The network can associate a reference location with this SSB index. If interference or spoofing occurs in a region (e.g., within the coverage area of ​​an SSB), the UE in that region (e.g., within the coverage area of ​​an SSB) can use the indicated reference location to calculate user-specific timing.

[0106] Figure 6 An example of a system 600 with SSB-based reference position mapping is illustrated according to various aspects of this disclosure.

[0107] In one embodiment, a mapping table with SSB indexes and corresponding reference location information (which will be used to perform user-specific timing calculations in place of the UE's GNSS location) is configured as part of the SIB (e.g., in the NTN SIB). Whenever the UE wants to perform a RACH procedure, the UE can look up its own GNSS location. If the GNSS location is unavailable, the UE can look up a reference location (e.g., the last known location) in the NTN SIB corresponding to its own SSB index, and can use that reference location instead of the UE's GNSS location for user-specific timing calculations.

[0108] In another embodiment, the duration of the mapping table's validity can be indicated along with the mapping table itself. This may be necessary as satellites move and SSB coverage areas can change. Particularly for Earth-mobile cells, frequent mapping table updates may be required. The UE may or may not need to perform a RACH procedure for each change to the mapping table. Depending on cell layout design, satellite orbital constellation, and other factors, the network can determine whether a new RACH procedure is required when the mapping table changes and / or is updated. This can be indicated separately in the same configuration or using RRC, MAC CE, or DCI signaling.

[0109] In some embodiments, the network may include information in the mapping table corresponding to the maximum size of the coverage area of ​​a region (e.g., SSB), and reference an indicated reference location to assist UEs that can move away from the indicated reference location. This information may be described as the maximum coverage distance (e.g., radius) from the reference location. For example, in Figure 6 In the scenario shown, when no GNSS position estimation is available, UE 2 and UE 3 can use the same reference location as UE 1 to calculate user-specific timing. However, UE 2 and UE 3 may experience more timing errors compared to UE 1 because they are farther from the reference location. UEs farther from the reference location have a greater chance of detecting adjacent SSBs because these UEs may fall within the beam overlap area (e.g., UE 2 and UE 3). In NTNs, due to the large beam coverage area, even if the satellite generates a very narrow beam, the beam overlap area can be as high as 100 km; therefore, many UEs may experience similar situations. UEs near the beam edge may need to select one of the reference locations that can be chosen based on the best SSB. For example, a UE can choose the reference location of one or more detected SSBs with the best Reference Signal Received Power (RSRP) value (e.g., UE 2 can use L1). In one implementation, the network can select a criterion for selecting a reference location from multiple detected SSBs (e.g., by defining a reference RSRP threshold). Alternatively, the UE can select a reference location corresponding to a region (e.g., SSB). In this case, if additional information such as the maximum distance from the reference location (e.g., radius) is available, the UE can use the reference location coordinates, the distance from the reference location, and the RSRP value of the SSB to calculate its own approximate position estimate. For example, for UE3, the UE can use triangulation techniques to calculate its own position, and this position can be used for user-specific timing calculations. For UE2, the average of two reference locations can be calculated and used as the UE's own position during RACH. In some implementations, distance-to-RSRP mapping can be used to enhance position estimation.

[0110] In various embodiments, the mapping table may be based on cell ID and reference location, rather than on area and / or SSB mapping. These embodiments can be used if a 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, position estimation can use the time difference of arrival (TDOA) and / or frequency difference of arrival (FDOA) of multiple SSBs beamformed by one or more satellites. According to the second implementation of the fourth embodiment, position estimation is calculated using measurements of the time difference of arrival (TDOA) and frequency difference of arrival (FDOA) of multiple SSBs beamformed by one or more satellites. Such position estimation may require a larger observation window to improve accuracy, which may also depend on the number of satellites in the field of view. After obtaining the position estimates, these estimates can be used to calculate user-specific differential TA.

[0112] For a single satellite, TDOA and / or FDOA measurements can be derived from multiple SSBs at different time intervals using satellite movement. However, this may require the UE to be aware of the satellite ephemeris while measurements are being taken. If the UE detects an SSB, the ephemeris information can be found in the NTN SIB, and the period of the satellite ephemeris information is configured by the network and can vary depending on the satellite altitude. If the position estimation will be calculated using TDOA and / or FDOA measurements within short intervals, it may be necessary to update the period of the ephemeris information with a short window so that the UE can collect reliable measurements. In one embodiment, the network may configure a timing window for calculating TA estimates using TDOA and / or FDOA measurements from SSBs.

[0113] Figure 7 An example of a UE 700 according to various aspects of this disclosure is illustrated. UE 700 may include a processor 702, a memory 704, a controller 706, and a transceiver 708. The processor 702, memory 704, controller 706, or transceiver 708, or various combinations thereof, or various components thereof, may be examples of parts for performing various aspects of this disclosure described herein. These components may be coupled via one or more interfaces (e.g., operational ground, communication ground, functional ground, electronic ground, electrical ground).

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

[0115] Processor 702 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, ASICs, field-programmable gate arrays (FPGAs), or any combination thereof). In some implementations, processor 702 may be configured to operate memory 704. In some other implementations, memory 704 may be integrated into processor 702. Processor 702 may be configured to execute computer-readable instructions stored in memory 704 to cause UE 700 to perform various functions of this disclosure.

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

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

[0118] Controller 706 can manage the input and output signals of UE 700. Controller 706 can also manage peripheral devices not integrated into UE 700. In some implementations, controller 706 can utilize operating systems such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, controller 706 can be implemented as part of processor 702.

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

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

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

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

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

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

[0125] Controller 802 can be configured to fetch (e.g., fetch, retrieve, receive) instructions from memory 804 and determine subsequent instructions(s) to be executed, enabling processor 800 to support various operations according to the examples described herein. Controller 802 can be configured to track the memory addresses of instructions associated with memory 804. Controller 802 can be configured to decode instructions to determine the operations to be performed and the operands involved. For example, controller 802 can be configured to interpret instructions and determine control signals to be output to other components of processor 800, enabling processor 800 to support various operations according to the examples described herein. Additionally or alternatively, controller 802 can be configured to manage data flow within processor 800. Controller 802 can be configured to control data transfers between registers, arithmetic logic unit (ALU), and other functional units of processor 800.

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

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

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

[0129] Based on the examples disclosed herein, processor 800 may support wireless communication. Processor 800 may be configured or operable to support components for: receiving configuration from a network entity, determining GNSS unavailability, calculating user-specific timing for performing the RRC connection establishment procedure based on GNSS unavailability, and performing the RRC connection establishment procedure according to the received configuration and based on the calculated user-specific timing.

[0130] Figure 9 An example of an NE 900 according to various aspects of this disclosure is illustrated. The NE 900 may include a processor 902, a memory 904, a controller 906, and a transceiver 908. The processor 902, memory 904, controller 906, or transceiver 908, or various combinations thereof, or various components thereof, may be examples of parts for performing various aspects of this disclosure described herein. These components may be coupled via one or more interfaces (e.g., operational ground, communication ground, functional ground, electronic ground, electrical ground).

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

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

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

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

[0135] Controller 906 manages the input and output signals of NE 900. Controller 906 can also manage peripheral devices not integrated into NE 900. In some implementations, controller 906 can utilize operating systems such as iOS®, Android®, Windows®, or other operating systems. In some implementations, controller 906 can be implemented as part of processor 902.

[0136] In some implementations, the NE 900 may include at least one transceiver 908. In 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 transmitter chains 912, or a combination thereof.

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

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

[0139] Figure 10 A flowchart of a method 1000 according to various aspects of this disclosure is illustrated. The operation of method 1000 can be implemented by the UE described herein. In some implementations, the UE 700 can execute an instruction set to control the functional elements of a processor to perform the described functions.

[0140] At point 1002, the method may include receiving configuration from a network entity. The operation at 1002 can be performed according to the examples described herein. In some implementations, aspects of the operation at 1002 can be derived from references. Figure 7 The UE is used to execute this.

[0141] At step 1004, the method may include determining the unavailability of the GNSS. The operation at step 1004 can be performed according to the examples described herein. In some implementations, aspects of the operation at step 1004 can be found in the references. Figure 7 The UE is used to execute this.

[0142] At point 1006, the method may include: calculating UE-specific timing for performing the connection procedure with the network entity based on GNSS unavailability. The operation at point 1006 can be performed according to the examples described herein. In some implementations, aspects of the operation at point 1006 may be derived from references... Figure 7 The UE is used to execute this.

[0143] At point 1008, the method may include performing a connection procedure based on the configuration and a calculated UE-specific timing. The operation of point 1008 can be performed according to the examples described herein. In some implementations, aspects of the operation of point 1008 may be derived from references... Figure 7 The UE is used to execute this.

[0144] Figure 11A flowchart of another method 1100 according to various aspects of this disclosure is illustrated. The operation of method 1100 can be implemented by the NE described herein. In some implementations, the NE 900 can execute an instruction set to control the functional elements of the processor to perform the described functions.

[0145] At 1102, the method may include sending configuration to the UE. The operation at 1102 can be performed according to the examples described herein. In some implementations, aspects of the operation at 1102 may be derived from references. Figure 9 The NE is used to execute this.

[0146] At 1104, the method may include: performing a connection procedure with the UE based on the transmitted configuration and UE-specific timing, wherein the UE-specific timing is based on GNSS unavailability. The operation at 1104 can be performed according to the examples described herein. In some implementations, aspects of the operation at 1104 may be derived from references... Figure 9 The NE is used to execute this.

[0147] It should be noted that the methods described in this paper describe possible implementations, and the operations and steps can be rearranged or otherwise modified, and other implementations are also possible.

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

Claims

1. A user equipment (UE), comprising: At least one memory; as well as At least one processor, coupled to the at least one memory, and configured such that the UE: Receive configuration from network entities; Determine the unavailability of the Global Navigation Satellite System (GNSS); Based on the unavailability of the GNSS, calculate the UE-specific timing for performing the connection procedure with the network entity; as well as The connection process is performed according to the configuration and based on the calculated UE-specific timing.

2. The UE of claim 1, wherein the at least one processor is configured such that the UE: receives the configuration during the idle state of the UE.

3. The UE according to claim 1, wherein the configuration includes: An indication of the duration of the suspension of transmission corresponding to the unavailability of the GNSS.

4. The UE according to claim 1, wherein the configuration includes: 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 such that the UE: receives an indication to avoid performing the connection process 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 such that the UE: receives a paging message, the paging message comprising: An indication to extend the period of time associated with the idle state of the UE.

7. The UE of claim 1, wherein the at least one processor is configured such that the UE: receives an indication of a duration for storing at least one location estimate of the GNSS based on the UE being in an idle state.

8. The UE of claim 7, wherein the configuration indicates an effective duration associated with at least one location estimate of the GNSS, wherein the at least one processor is configured such that the UE: Based on the UE being in the idle state and the indicated validity duration, the at least one location estimate of the GNSS is stored up to the specified duration. The duration mentioned therein includes the validity duration.

9. The UE of claim 1, wherein the at least one processor is configured such that the UE: during the connection mode of the UE, receives the configuration via dedicated higher-layer signaling.

10. The UE of claim 1, wherein the at least one processor is configured such that the UE: during the idle state of the UE, receives the configuration via a paging message.

11. The UE according to claim 1, wherein the configuration includes: The location estimates of the one or more stores of the GNSS are used as indications for the connection process based on the validity duration associated with the location estimate of each store in the location estimates of the one or more stores of the GNSS, and wherein the location estimates of the one or more stores 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 such that the UE: receives an instruction to time synchronize using the last known location of the GNSS.

13. The UE of claim 1, wherein the at least one processor is configured such that the UE: receives an instruction for a method of estimating the UE location, wherein a specific timing of the UE is further calculated based on the estimated UE location.

14. The UE according to claim 1, wherein the configuration includes: A table mapping the location estimates to the corresponding areas of the cell.

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

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

17. A method for conducting wireless communication at a user equipment (UE), the method comprising: Receive configuration from network entities; Determine the unavailability of the Global Navigation Satellite System (GNSS); Based on the unavailability of the GNSS, calculate the UE-specific timing for performing the connection procedure with the network entity or the GNSS; as well as The connection process is performed according to the configuration and based on the calculated UE-specific timing.

18. A base station, comprising: At least one memory; as well as At least one processor, coupled to the at least one memory, and configured such that the base station: Send configuration to user equipment (UE); as well as Based on the transmitted configuration and UE-specific timing, a connection procedure with the UE is performed, wherein the UE-specific timing is based on the unavailability of the Global Navigation Satellite System (GNSS).

19. The base station according to claim 18, wherein the configuration includes: An indication of the duration of the suspension of transmission corresponding to the unavailability of the GNSS.

20. The base station according to claim 18, wherein the configuration includes: An indication to activate or deactivate a time window corresponding to a specific timing of the UE.

21. The base station of claim 18, wherein the at least one processor is configured to cause the base station to: send a paging message, the paging message comprising: An indication to extend the period of time associated with the 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 of the duration of at least one location estimate of the GNSS stored.

23. The base station of claim 22, wherein the configuration indicates the 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 such that the base station: transmits the configuration via dedicated higher-layer signaling.

25. The base station according to claim 18, wherein the configuration includes: The location estimates of the one or more stores of the GNSS are used as indications for the connection process based on the validity duration associated with the location estimate of each store in the location estimates of the one or more stores of the GNSS, and wherein the location estimates of the one or more stores 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: send an indication to synchronize time with the UE using the last known location of the GNSS.

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 the location of the UE, wherein the UE-specific timing is further based on the estimated UE location.

28. The base station of claim 18, wherein the configuration includes a table mapping location estimates corresponding to areas of the cell.

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

30. A method for conducting wireless communication at a base station, the method comprising: Send configuration to user equipment (UE); as well as Based on the transmitted configuration and UE-specific timing, a connection procedure with the UE is performed, wherein the UE-specific timing is based on the unavailability of the Global Navigation Satellite System (GNSS).

Images