Non-terrestrial network access

By actively updating geolocation corrections in non-terrestrial networks, the performance problems caused by the invalidity of geolocation corrections are solved, and the stability of the system and data transmission efficiency are improved.

CN118923058APending Publication Date: 2024-11-08TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380026869.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-02-11
Filing Date
2023-02-10
Publication Date
2024-11-08

AI Technical Summary

Technical Problem

In non-terrestrial networks, geolocation correction invalidity of communication devices leads to reduced data throughput, increased latency and system performance degradation, especially when the validity timer expires, geolocation correction becomes invalid and needs to be reacquisitioned to maintain the connection .

Method used

The communication device actively updates the geolocation correction before accessing a non-terrestrial network. If the remaining valid time is less than the threshold time, it will be updated in advance; if the remaining time exceeds the threshold time, it will avoid updates and obtain it from the NTN system information by receiving the threshold duration. And decide whether to update based on the effectiveness of geolocation correction and the configuration of communication equipment.

Benefits of technology

It reduces the connection problems caused by geolocation correction ineffectiveness, improves system performance, reduces data latency and throughput, and ensures the stability and performance of communication devices when accessing NTN.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118923058A_ABST
    Figure CN118923058A_ABST
Patent Text Reader

Abstract

A method performed by a communication device (18) configured for use in a non-terrestrial network (NTN) (10) is disclosed. The communication device (18) makes a decision as to whether the geolocation correction (20) of the communication device (18) is updated before accessing the NTN (10) even if the geolocation correction (20) is valid. In some embodiments, the decision is made based on a remaining duration (26) during which the geolocation correction (20) will be valid. In accordance with this decision, the communication device (18) further updates or avoids updating the geolocation correction (20) prior to accessing the NTN (10).
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates generally to non-terrestrial networks, and more particularly to accessing a non-terrestrial network. Background Art

[0002] A non-terrestrial network (NTN) is a network that uses transmission equipment relay nodes or base stations carried by air or space vehicles. For example, a satellite is a space vehicle carrying a bent-pipe payload or a regenerative payload telecommunication transmitter, such as placed in low earth orbit (LEO), medium earth orbit (MEO), or geostationary orbit (GEO). Using such air or space vehicles, NTNs can provide communication services over a wider area of ​​the earth than terrestrial networks, for example, making the services more location-independent.

[0003] However, the propagation delay of NTN is larger than that of terrestrial networks. For bent-pipe satellite networks, the round-trip delay may range from tens of milliseconds (ms) for LEO satellites to hundreds of milliseconds for GEO satellites, for example. In contrast, the round-trip delay in terrestrial networks is typically less than 1 millisecond.

[0004] Due to the longer propagation delay in the NTN, the timing advance (TA) that the communication device uses for its uplink transmission must be much larger than the timing advance in the terrestrial network so that the uplink and downlink are aligned in time. Then, when accessing the NTN, the communication device performs a random access (RA) procedure to obtain this timing advance. But even the initial message (called the random access preamble) sent by the communication device as part of the random access procedure must be sent with a timing advance to allow a reasonable size random access preamble reception window. The TA that the communication device uses for RA preamble transmission in the NTN is called a "pre-compensated TA". In some methods, the communication device can determine the pre-compensated TA based on a geolocation fix of the communication device, for example, based on the difference between the geolocation fix of the communication device and a reference geographical location in an NTN cell (for which the communication device has a reference TA).

[0005] There are challenges in ensuring that the communication device has an accurate geolocation fix when needed. After the communication device obtains a geolocation fix, the communication device starts a validity timer. While the validity timer is running, the geolocation fix is ​​valid, and the communication device is allowed to establish, reestablish, or resume a connection with the NTN. However, the problem is that if the validity timer expires while the communication device is connected to the NTN, the geolocation fix becomes invalid, and the communication device must take action to resolve this invalidity, for example, by reacquiring a geolocation fix in a measurement gap, by releasing its connection with the NTN to reacquire a geolocation fix, and so on. Resolving geolocation fix invalidity may thereby degrade system performance, for example, by reducing data throughput, increasing data latency, and / or otherwise degrading the perceived quality of experience. Summary of the invention

[0006] According to some embodiments herein, a communication device proactively updates its geolocation fix prior to accessing an NTN, even if the geolocation fix is ​​still valid. For example, the communication device may do this if the remaining duration that the geolocation fix will be valid is less than a threshold duration (e.g., reflecting an estimated connection duration). By proactively updating geolocation fixes in this manner, some embodiments advantageously reduce the likelihood that the communication device will have to resolve the invalidity of geolocation fixes while the device is connected to the NTN. Some embodiments thereby improve system performance.

[0007] More specifically, embodiments herein include a method performed by a communication device configured for use in a non-terrestrial network (NTN). The method includes making a decision as to whether to update a geolocation fix of the communication device even if the geolocation fix is ​​valid before accessing the NTN. In some embodiments, the decision is made based on a remaining duration for which the geolocation fix will be valid. The method also includes updating or refraining from updating the geolocation fix before accessing the NTN based on the decision.

[0008] In some embodiments, the making includes: if the remaining duration is less than a threshold duration, making a decision to update the geolocation correction before accessing the NTN. In some embodiments, the making also includes: if the remaining duration is greater than the threshold duration, making a decision to avoid updating the geolocation correction before accessing the NTN. In one or more of these embodiments, the method also includes: receiving the threshold duration from the NTN. In one or more of these embodiments, receiving the threshold duration includes: receiving the threshold duration in system information of the NTN. In one or more of these embodiments, the receiving of the threshold duration covers a preconfigured threshold duration preconfigured at the communication device. In one or more of these embodiments, the communication device is preconfigured with the threshold duration. In one or more of these embodiments, the threshold duration is specific to the purpose for which the communication device is accessing the NTN or the process that the communication device is using to access the NTN. In one or more of these embodiments, the threshold duration is specific to the type of satellite providing the NTN cell that the communication device is accessing. In one or more of these embodiments, the threshold duration is specific to the orbital altitude of the satellite providing the NTN cell that the communication device is accessing. In one or more of these embodiments, the threshold duration is specific to a type, category, or class of the communications device.

[0009] In some embodiments, the method further comprises determining whether to make the decision based on the remaining duration for which the geolocation correction will be valid. In one or more of these embodiments, the determination is performed based on whether the communication device receives signaling indicating that the communication device is to make the decision based on the remaining duration for which the geolocation correction will be valid. In one or more of these embodiments, the signaling comprises a threshold duration. In one or more of these embodiments, the signaling comprises a flag indicating whether the communication device is to make the decision based on the remaining duration for which the geolocation correction will be valid. In one or more of these embodiments, the determination comprises determining that if the communication device is configured with a power saving mode, the decision is not made based on the remaining duration for which the geolocation correction will be valid. Alternatively, the determination comprises determining that if the communication device is configured to perform at least a threshold number of transmission repetitions, the decision is not made based on the remaining duration for which the geolocation correction will be valid. Alternatively, the determination comprises determining that if the communication device belongs to one or more specific coverage classes, the decision is not made based on the remaining duration for which the geolocation correction will be valid. Alternatively, the determining includes determining that if the communication device belongs to one or more specific coverage enhancement modes, classes or levels, the determination is not made based on the remaining duration for which the geolocation fix will be valid. In one or more of these embodiments, the determining is performed based on the purpose for which the communication device is accessing the NTN or the process that the communication device is using to access the NTN. In one or more of these embodiments, the determining includes determining that if the communication device is performing initial access to the NTN, the determination is made based on the remaining duration for which the geolocation fix will be valid. In one or more of these embodiments, the determining includes determining that if access to the NTN is triggered by a downlink control channel command from the NTN, the determination is not made based on the remaining duration for which the geolocation fix will be valid. Alternatively, the determining includes determining that if coverage of a serving satellite will be lost before the geolocation fix becomes invalid, the determination is not made based on the remaining duration for which the geolocation fix will be valid.

[0010] In some embodiments, the method further comprises determining the threshold duration based on an estimated duration that the communication device will remain accessed to the NTN.

[0011] In some embodiments, the method further comprises determining the threshold duration based on an estimated duration of a connection that the communication device is to establish, re-establish or resume as part of accessing the NTN.

[0012] In some embodiments, accessing the NTN includes performing random access to the NTN and / or establishing, re-establishing or recovering a connection with the NTN.

[0013] In some embodiments, accessing the NTN includes performing an Early Data Transmission (EDT) or a Pre-Configured Uplink Resource (PUR) transmission.

[0014] In some embodiments, accessing the NTN comprises: performing random access to a cell of the NTN and / or establishing, re-establishing or resuming a connection with a cell of the NTN.

[0015] In some embodiments, accessing the NTN comprises: transitioning to a Radio Resource Control (RRC) connected state.

[0016] In some embodiments, the geolocation fix comprises a Global Navigation Satellite System (GNSS) location fix.

[0017] In some embodiments, the geolocation fix is ​​valid while a validity timer is running, wherein the remaining duration for which the geolocation fix will be valid is the remaining duration of the validity timer.

[0018] In some embodiments, the validity timer is started or restarted when the communications device obtains or updates the geolocation fix.

[0019] In some embodiments, the communications device is configured to transition to an RRC idle state upon expiration of the validity timer.

[0020] In some embodiments, the communications device is configured to transition to an RRC idle state when the geolocation fix becomes invalid.

[0021] In some embodiments, the method further comprises: determining a pre-compensated timing advance based on the geolocation correction, whether updated or not depending on the determination. The method further comprises: performing a random access channel transmission using the determined pre-compensated timing advance as part of accessing the NTN.

[0022] In some embodiments, the method further comprises: providing user data; and forwarding the user data to a host computer via transmission to a base station.

[0023] Other embodiments herein include a method performed by a network node configured for use in a non-terrestrial network (NTN). The method includes sending signaling to a communication device, the signaling controlling the communication device's decision on whether to update a geolocation fix of the communication device even if a geolocation fix was valid before accessing the NTN.

[0024] In some embodiments, the signaling indicates a threshold duration for which the geolocation fix must remain valid after accessing the NTN in order for the communication device to access the NTN without updating the geolocation fix. In one or more of these embodiments, the indicated threshold duration is to override a preconfigured threshold duration preconfigured at the communication device. In one or more of these embodiments, the indicated threshold duration is specific to the purpose for which the communication device is accessing the NTN or the process that the communication device is using to access the NTN. In one or more of these embodiments, the indicated threshold duration is specific to the type of satellite providing the NTN cell that the communication device is accessing. In one or more of these embodiments, the indicated threshold duration is specific to the orbital altitude of the satellite providing the NTN cell that the communication device is accessing. In one or more of these embodiments, the indicated threshold duration is specific to the type, category, or class of the communication device.

[0025] In some embodiments, the signaling indicates whether the communications device is to make a decision as to whether to update the geolocation fix while the geolocation fix is ​​valid.

[0026] In some embodiments, the signaling includes a flag indicating whether the communications device is to make the decision based on the remaining duration for which the geolocation fix will be valid.

[0027] In some embodiments, the signaling indicates that the communication device is to update the geolocation fix if the communication device is configured with a particular power saving mode, if the communication device is configured to perform at least a threshold number of transmission repetitions, if the communication device belongs to one or more particular coverage classes, or if the communication device belongs to one or more particular coverage enhancement modes, classes, or levels. In some embodiments, the signaling indicates the particular power saving mode, the threshold number of transmission repetitions, the one or more particular coverage classes, or the one or more particular coverage enhancement modes.

[0028] In some embodiments, the signaling indicates that the communications device is to update the geolocation fix if the communications device accesses the NTN for a specific purpose or using a specific procedure.

[0029] In some embodiments, the signaling indicates that the communications device is to update the geolocation fix if the communications device is performing an initial access to the NTN.

[0030] In some embodiments, the signaling indicates that the communication device does not update the geolocation fix if access to the NTN is triggered by a downlink control channel command from the NTN. Alternatively, the signaling indicates that the communication device does not update the geolocation fix if coverage of the serving satellite will be lost before the geolocation fix becomes invalid.

[0031] In some embodiments, accessing the NTN includes performing random access to the NTN and / or establishing, re-establishing or recovering a connection with the NTN.

[0032] In some embodiments, accessing the NTN includes performing an Early Data Transmission (EDT) or a Pre-Configured Uplink Resource (PUR) transmission.

[0033] In some embodiments, accessing the NTN comprises: performing random access to a cell of the NTN and / or establishing, re-establishing or resuming a connection with a cell of the NTN.

[0034] In some embodiments, accessing the NTN comprises: transitioning to a Radio Resource Control (RRC) connected state.

[0035] In some embodiments, the geolocation fix comprises a Global Navigation Satellite System (GNSS) location fix.

[0036] In some embodiments, the geolocation correction is valid while a validity timer is running. In some embodiments, the signaling controls whether or how the communication device makes the decision based on a remaining duration for which the geolocation correction will be valid. In one or more of these embodiments, the geolocation correction is valid while a validity timer is running. In some embodiments, the remaining duration for which the geolocation correction will be valid is the remaining duration of the validity timer. In one or more of these embodiments, the validity timer is started or restarted when the communication device obtains or updates the geolocation correction. In one or more of these embodiments, the communication device is configured to transition to an RRC idle state when the validity timer expires.

[0037] In some embodiments, the communications device is configured to transition to an RRC idle state when the geolocation fix becomes invalid.

[0038] The embodiments of this document also include corresponding devices, computer programs, and carriers of these computer programs. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] Figure 1 is a block diagram of a non-terrestrial network (NTN) according to some embodiments.

[0040] Figure 2 is a block diagram of a satellite network with bent pipe transponders.

[0041] Figure 3 is a block diagram of a satellite orbit parameterized by a set of orbital elements in accordance with some embodiments.

[0042] Figure 4 is a timing diagram illustrating a GNSS correction timing problem addressed by some embodiments.

[0043] Figure 5 is a timing diagram illustrating GNSS correction timing according to some embodiments.

[0044] Figure 6 is a logic flow diagram of a method performed by a user device according to some embodiments.

[0045] Figure 7 is a logic flow diagram of a method performed by a communication device according to some embodiments.

[0046] Figure 8 is a logic flow diagram of a method performed by a network node according to some embodiments.

[0047] Fig. 9 is a block diagram of a communication device according to some embodiments.

[0048] Fig.10 is a block diagram of a network node according to some embodiments.

[0049] Fig.11 is a block diagram of a communication system according to some embodiments

[0050] Fig.12 is a block diagram of a user equipment according to some embodiments.

[0051] Fig.13 is a block diagram of a network node according to some embodiments.

[0052] Fig.14 is a block diagram of a host according to some embodiments.

[0053] Fig.15 is a block diagram of a virtualization environment according to some embodiments.

[0054] Fig.16 is a block diagram of a host communicating with a UE via a network node over a partial wireless connection according to some embodiments. DETAILED DESCRIPTION

[0055] Figure 1A non-terrestrial network (NTN) 10 is shown according to some embodiments. As shown, the NTN 10 includes a satellite 12 (e.g., a communication satellite) and a ground-based gateway 14 that connects the satellite 12 to a base station or core network. The satellite 12 (which may cooperate with the ground-based gateway 14) provides communication coverage for serving communication devices 18, such as via spot beams or cells 16.

[0056] In this case, the communication device 18 is able to obtain a geolocation fix 20 for the communication device 18. The geolocation fix 20 represents the geographic location of the communication device 18, for example, as derived from one or more positioning measurements. More specifically, the communication device 18 is able to obtain its geolocation fix 20 even before the communication device 18 accesses the NTN 10. In some embodiments, for example, the communication device 18 obtains its geolocation fix 20 via a GNSS including a plurality of Global Navigation Satellite System GNSS satellites 22. In this case, the communication device 18 may have a GNSS receiver that is able to perform GNSS measurements in order to derive the geolocation fix 20 in the form of a GNSS positioning fix.

[0057] In some embodiments, the communication device 18 considers the geolocation fix 20 to be valid for a certain amount of time after having obtained the geolocation fix 20. Here, the validity of the geolocation fix 20 may mean that the geolocation fix 20 still represents the geographic location of the communication device 18 with at least a certain level of accuracy or performance, i.e., the geolocation fix 20 has not become stale. For example, the communication device 18 may start a validity timer 24 when obtaining the geolocation fix 20. In this case, the communication device 18 considers the geolocation fix 20 to be valid while the validity timer 24 is running. However, when the validity timer 24 expires, the communication device 18 considers the geolocation fix 20 to be invalid.

[0058] In some embodiments, the communication device 18 is configured to determine a pre-compensated timing advance (TA) using the geolocation fix 20. The communication device 18 may then perform a random access channel transmission (not shown) using the pre-compensated TA as part of accessing the NTN 10, e.g., to establish, re-establish, or resume a connection with the NTN 10. In these and other embodiments, the validity of the geolocation fix 20 is a prerequisite for the communication device 18 to access the NTN 10.

[0059] However, it is worth noting that the communication device 10 does not simply access the NTN 10 as long as its geolocation fix 20 is valid, but can actively update its geolocation fix 20 before accessing the NTN 10, even if the geolocation fix 20 is still valid. For example, the communication device can do this if the remaining duration 26 that the geolocation fix 20 will be valid is less than a threshold duration (which, for example, reflects an estimated connection duration or otherwise reflects an estimated duration that the communication device 18 will remain accessed to the NTN 10). In this regard, Figure 1 The remaining duration 26 for which the geolocation fix 20 will be valid is shown, which is reflected by the current value of the validity timer 24. In this case, if the current value of the validity timer 24 is less than the threshold duration, the communication device 18 may proactively update its geolocation fix 20 prior to accessing the NTN 10. Regardless, by proactively updating the geolocation fix 20 in this manner, some embodiments advantageously reduce the likelihood that the geolocation fix 20 will become invalid while the device is connected to the NTN 10. This, in turn, reduces the likelihood that the communication device 10 will have to perform geolocation measurements during a measurement gap, release its connection to the NTN 10, or otherwise take actions that would degrade performance.

[0060] According to some embodiments of this aspect, the communication device 10 makes a decision as to whether to update its geolocation fix 20 even if the geolocation fix 20 is valid before accessing the NTN 10. The communication device 10 may make this decision based on a remaining duration 26 for which the geolocation fix 20 will be valid. More specifically, for example, if the remaining duration 26 is less than a threshold duration, the communication device 10 makes a decision to update the geolocation fix 20 before accessing the NTN 10. On the other hand, if the remaining duration 26 is greater than the threshold duration, the communication device 18 makes a decision to avoid updating the geolocation fix 20 before accessing the NTN 10.

[0061] In some embodiments, the communication device 18 receives signaling 28 from a network node 30 in the NTN 10 that controls the communication device's decision in this regard. The signaling 28 may, for example, indicate the threshold duration mentioned above, i.e., the threshold duration for which the geolocation fix 20 must remain valid after accessing the NTN 10 in order for the communication device 18 to access the NTN 10 without updating the geolocation fix 20. Alternatively or additionally, the signaling 28 may indicate whether the communication device 18 is to make a decision as to whether to update the geolocation fix 20 even when the geolocation fix 20 is valid. The signaling 28 may, for example, be a flag indicating whether the communication device 18 is to make such a decision. Alternatively, the signaling 28 may indicate one or more conditions under which the communication device 18 is to make (not make) such a decision.

[0062] Some embodiments herein are applicable to the following example context, in which the communication device 18 is illustrated as a user equipment (UE), the geolocation fix 20 is illustrated as a GNSS positioning fix, and the validity timer 24 is illustrated as a GNSS validity timer.

[0063] Specifically, some embodiments herein are applicable to NTN specified in 3GPP. In one or more embodiments, a satellite radio access network may include the following components: (i) a satellite, which refers to a space launch platform; (ii) a ground-based gateway, which connects the satellite to a base station or a core network according to the choice of architecture; (iii) a feeder link, which refers to a link between a gateway and a satellite; (iv) an access link, which refers to a link between a satellite and a user equipment (UE).

[0064] Based on the orbital altitude, in some embodiments, satellites may be classified as low earth orbit (LEO), medium earth orbit (MEO), or geostationary earth orbit (GEO) satellites. Typical altitudes for LEOs range from 250–1,500 km, with orbital periods ranging from 90–120 minutes. Typical altitudes for MEOs range from 5,000–25,000 km, with orbital periods ranging from 3–15 hours. Typical altitudes for GEOs range from approximately 35,786 km, with orbital periods of 24 hours.

[0065] In some embodiments, the NTN may have one of two basic architectures, depending on the functionality of the satellites in the system.

[0066] One architecture has a transparent payload and is also known as bent pipe architecture. In this case, the satellite forwards the received signal between the terminal and the network equipment on the ground, performing only amplification and shifting from uplink frequency to downlink frequency. When applied to the general 3GPP architecture and terminology, a transparent payload architecture means that the gNB is located on the ground and the satellite forwards the signal / data between the gNB and the UE.

[0067] Another architecture has a regenerative payload. The satellite includes onboard processing to demodulate and decode the received signal and regenerate the signal before sending it back to Earth. When applied to the general 3GPP architecture and terminology, the regenerative payload architecture means that the gNB is located in the satellite.

[0068] Figure 2 An example architecture of a satellite network with bent pipe repeaters (ie, a transparent payload architecture) is shown. In this case, the satellite 12 repeats the signal between the communication device 18 and the network equipment on the ground, performing only amplification and shifting from the uplink frequency to the downlink frequency. Figure 1The network node 30 in FIG. 1 is shown as a base station (BS) 30, for example in the form of a gNB, which is located on the ground together with the gateway 14, and the satellite 12 forwards signals / data between the base station 30 and the device 18 via access links and feeder links. The base station 30 may be integrated in the gateway 14 or connected to the gateway 14 via a terrestrial connection (wired, optical fiber, wireless link).

[0069] In some embodiments, a communications satellite generates multiple beams over a given area. The footprint of the beams may be elliptical, and they may be considered cells, but cells including footprints of multiple beams are not excluded. The footprint of the beam may also be referred to as a spot beam. The footprint of the beam may move on the surface of the earth as the satellite moves, or may be fixed on the earth by a beam pointing mechanism used by the satellite to compensate for the movement of the satellite. The size of the spot beam depends on the system design and may range from tens of kilometers to thousands of kilometers.

[0070] Propagation delay is an aspect of satellite communications that differs from the delays expected in land mobile systems. For bent-pipe satellite networks, the round-trip delay can range from tens of milliseconds for LEO satellites to hundreds of milliseconds for GEO satellites, depending on the orbital altitude. In contrast, the round-trip delay in terrestrial cellular networks is typically less than 1 millisecond.

[0071] The distance between the UE and the satellite can vary widely, depending on the position of the satellite and the elevation angle ε seen by the UE. Assuming a circular orbit, the minimum distance is achieved when the satellite is directly above the UE (ε = 90°) and the maximum distance is achieved when the satellite is at the minimum possible elevation angle. Table 1 shows the distance between the satellite and the UE as well as the one-way propagation delay and the maximum propagation delay difference (the difference from the propagation delay when ε = 90°) for different orbital altitudes and elevation angles. Note that this table assumes a regenerative payload architecture. For the case of a transparent payload, the propagation delay between the gateway and the satellite also needs to be considered, unless the base station corrects for this.

[0072] Table 1: Propagation delays for different orbit altitudes and elevation angles.

[0073]

[0074] Due to the high speeds of LEO and MEO satellites, propagation delays can also be highly variable and vary by about 10–100 microseconds (μs) per second, depending on orbital altitude and satellite speed.

[0075] For non-terrestrial networks using 3GPP technologies (particularly 5G / NR), the long propagation delays mean that the timing advance (TA) that the UE uses for its uplink transmissions must be much larger than in terrestrial networks so that the uplink and downlink are time-aligned at the gNB, as is the case in NR and LTE. One of the purposes of the random access (RA) procedure is to provide the UE with a valid TA (which the network can later adjust based on the reception timing of uplink transmissions from the UE). However, even the random access preamble (i.e., the initial message from the UE in the random access procedure) must be sent with a timing advance to allow a reasonably sized RA preamble reception window in the gNB (and to ensure that the cyclic shift of the Zadoff-Chu sequence of the preamble is not so large as to make the Zadoff-Chu sequence, and therefore the preamble, appear as if it were another Zadoff-Chu sequence based on the same Zadoff-Chu root sequence and therefore another preamble). However, this TA does not have to be as accurate as the TA that the UE subsequently uses for other uplink transmissions. The TA used by the UE for RA preamble transmission in the NTN is called the “pre-compensation TA”.

[0076] Some embodiments herein for geolocation correction updates are applicable to support any of a variety of alternatives for how to determine a pre-compensated TA. All of these alternatives may involve information originating from both the gNB and the UE. Specifically, some embodiments herein for geolocation correction updates are applicable to support a first pre-compensated TA alternative that broadcasts a "common TA" that is valid at a specific reference point (e.g., a center point in a cell). The UE calculates the degree of deviation of its own pre-compensated TA from the common TA based on the difference between the UE's own position and the reference point and the positions of the satellites. Here, the UE uses GNSS measurements to obtain its own position, and the UE uses satellite orbit data broadcast by the network (including satellite positions at a specific time) to obtain satellite positions.

[0077] Some embodiments herein for geolocation correction updates may alternatively or additionally be applied to a second pre-compensated TA alternative, where the UE autonomously calculates the propagation delay between the UE and the satellite based on their respective positions, and the network / gNB broadcasts the propagation delay on the feeder link, i.e., the propagation delay between the gNB and the satellite. Here, the UE uses GNSS measurements to obtain its own position, and the UE uses satellite orbit data (including satellite positions at a specific time) broadcasted by the network to obtain satellite positions. The pre-compensated TA is twice the sum of the propagation delay on the feeder link and the propagation delay between the satellite and the UE.

[0078] Some embodiments herein for geolocation correction updates are alternatively or additionally applicable to a third pre-compensated TA alternative, where the gNB broadcasts a timestamp (in SIB9) that the UE compares with a reference timestamp obtained from the GNSS. Based on the difference between these two timestamps, the UE can calculate the propagation delay between the gNB and the UE, and the pre-compensated TA is twice this propagation delay.

[0079] In conjunction with the random access procedure, the gNB provides the UE with an accurate (i.e., fine-tuned) TA in a Random Access Response message (in a 4-step RA) or MsgB (in a 2-step RA) based on the time of receipt of the random access preamble. The gNB may then adjust the UE's TA using a Timing Advance Command Media Access Control (MAC) Control Element (CE) (or an Absolute Timing Advance Command MAC CE) based on the time of receipt of the uplink transmission from the UE. The goal of such network control of the UE's timing advance is typically to keep the timing error of the UE's uplink transmission at the gNB's receiver within the cyclic prefix (which is required for correct decoding of the uplink transmission). The timing advance control framework also includes a time alignment timer configured by the gNB for the UE. Each time the gNB adjusts the UE's TA, the time alignment timer is restarted, and if the time alignment timer expires, the UE is not allowed to transmit in the uplink without a prior random access procedure (whose purpose is to provide the UE with a valid timing advance). For NTN, in addition to the gNB’s control of the UE’s TA, the UE is allowed to autonomously update its TA based on an estimate of the change in the UE-gNB round trip time (RTT), using the UE’s location (e.g., obtained from GNSS measurements) and knowledge of the serving satellite’s ephemeris data and feeder link latency information from the gNB.

[0080] A second relevant aspect is that not only is the propagation delay between UE and satellite or between UE and gNB very long in NTNs, but also due to the large distances, the difference in propagation delays to two different satellites or two different gNBs can be large on time scales relevant for cellular communications (including signaling procedures), even when the satellites / gNBs serve neighboring cells. This affects all procedures involving reception or transmission in two cells served by different satellites and / or different gNBs.

[0081] A third aspect related to long propagation delay / RTT in non-terrestrial networks is the introduction of additional parameters to compensate for the long propagation delay / RTT. In terrestrial cellular networks, the UE-gNB RTT can range from near zero to tens of microseconds in a cell. Aside from the absolute magnitude of the propagation delay / RTT, the difference in non-terrestrial networks is that even where the propagation delay / RTT is smallest in a cell, it can be large and far from zero. In fact, the variation of propagation delay / RTT within an NTN cell is small compared to the propagation delay / RTT. This facilitates the introduction of an offset that primarily deals with the RTT between the cell’s footprint on the ground and the satellite, while other mechanisms (including signaling and control loops) deal with RTT-related aspects within the smaller range of RTT variations in the cell above the offset.

[0082] To this end, in some embodiments, K offset The parameter K (also called K_offset) can be used in various timing related mechanisms, for example, in scheduling uplink transmissions on the Physical Uplink Shared Channel (PUSCH). offset Used to indicate the additional delay between the uplink (UL) grant and the PUSCH transmission resources allocated by the UL grant, which will be added to the slot offset parameter K2 in the downlink control information (DCI) containing the UL grant. Therefore, the offset between the UL grant and the slot in which the PUSCH transmission resources are allocated is K offset +K2. When used in this way in uplink scheduling, it can be said that K offset This serves to ensure that the UE is never scheduled to transmit at a time that occurs before the time at which the UE receives the UL grant due to the larger TA that the UE must apply. offset The configuration may take into account the TA that the UE may have signaled that it has used.

[0083] A fourth aspect that is closely related to timing is the Doppler frequency shift caused by the motion of the satellite. Access links may experience Doppler shifts of around 10–100 kHz in the sub-6 GHz bands and proportionally higher in the higher frequency bands. Furthermore, the Doppler shift is variable, with rates up to a few hundred hertz per second in the S-band and up to a few thousand hertz per second in the Ka-band.

[0084] In some embodiments, e.g., consistent with 3GPP TR 38.821 v16.1.0, ephemeris data is provided to the UE, e.g., to help point a directional antenna (or antenna beam) to a satellite and calculate the correct timing advance (TA) and Doppler shift. Broadcasting ephemeris data in system information is an option.

[0085] In some embodiments, the satellite orbit is completely described by a set of parameters, for example using 6 parameters. The user can decide which specific parameter set to choose; a variety of different representations are possible. For example, a parameter choice often used in astronomy is the set (a, ε, i, Ω, ω, t). Here, the semi-major axis a and the eccentricity ε describe the shape and size of the orbital ellipse; the inclination i, the right ascension of the ascending node Ω, and the argument of periapsis ω determine its position in space, while the epoch t determines the reference time (e.g., the time when the satellite passes through the periapsis). This parameter set is as follows: Figure 3 shown.

[0086] As an example of a different parameterization, the two-line element set (TLE) uses the mean motion n and the mean anomaly M instead of a and t. A completely different set of parameters is the position and velocity vectors (x, y, z, v x ,v y ,v z ). These are sometimes called orbital state vectors. They can be derived from orbital elements, or vice versa, because the information they contain is equivalent. All of these representations (and many others) are possible choices for the format of ephemeris data to be used in the NTN.

[0087] In some embodiments, the UE is able to determine the position of the satellite with an accuracy of at least a few meters. In one embodiment, the LEO satellites have GNSS receivers and are able to determine their position with meter-level accuracy.

[0088] Another aspect is the validity period of the ephemeris data. Due to atmospheric drag, maneuvers of the satellite, imperfections in the orbital model used, etc., the predictions of the satellite positions generally deteriorate as the ephemeris data used age. Thus, for example, the publicly available TLE data are updated quite frequently. The frequency of updates depends on the satellite and its orbit and can range from once a week to several times a day for satellites in very low orbits (which are subject to strong atmospheric drag and require frequent correction maneuvers).

[0089] Therefore, while it may seem possible to provide satellite positions with the required accuracy, care needs to be taken to meet these requirements when, for example, choosing the ephemeris data format or the orbit model to be used for orbit propagation.

[0090] In some embodiments, supporting service satellite ephemeris broadcast is based on one or more of the following sets.

[0091] Set 1 includes the satellite position and velocity state vectors, including positions X, Y, Z in ECEF(m) and velocities VX, VY, VZ in ECEF(m / s).

[0092] Set 2 includes at least the following parameters in orbital parameter ephemeris format: semi-major axis α [m], eccentricity e, argument of periapsis ω [rad], longitude of ascending node Ω [rad], inclination i [rad], and mean anomaly M [rad] at epoch time t0. A pre-supplied ephemeris based on orbital elements can be used as a reference. Thus, only incremental corrections can be broadcasted to reduce overhead.

[0093] The specification may support the use of two ephemeris formats (ie, state vector and orbit element) to communicate ephemeris information.

[0094] The validity timers for UL synchronization (eg, for satellite ephemeris and possibly other aspects) may be configurable by the network.

[0095] To handle timing and frequency synchronization in NTNs based on NR or LTE, devices can be equipped with a Global Navigation Satellite System (GNSS) receiver. A GNSS receiver allows the device to estimate its geographic location. The UE can then determine the propagation delay, delay variation, Doppler shift, and their rate of change based on its own and satellite position information.

[0096] Different levels of integration of GNSS chips in 3GPP cellular modems can be expected. The UE may support GNSS, but this support is not used for timing and frequency correction in RRC connected mode:

[0097] In some embodiments, the UE may estimate and pre-compensate timing and frequency offsets with sufficient accuracy for UL transmissions.

[0098] In some embodiments, simultaneous GNSS and NTN NB-IoT / eMTC operation is not assumed. In fact, in some embodiments, the UE may share parts of its radio frequency (RF) architecture between the cellular modem and the GNSS chip. One solution is to use the same antenna to receive GNSS reference signals, as well as to receive and transmit LTE or NR signals. A switch determines whether the antenna should be connected to the cellular RF front end or the GNSS RF front end. The switch provides the required isolation between the cellular transmitter and the GNSS receiver, but also prevents simultaneous GNSS and cellular operation.

[0099] In some embodiments, the UE autonomously determines its GNSS validity duration X and reports information related to the validity duration to the network via RRC signaling. In some embodiments, the UE is required to have valid GNSS fixes before entering a connection. In some embodiments, if it is necessary to avoid interruptions during a connection, the UE reacquires GNSS fixes (regardless of whether they were previously valid) before establishing a connection.

[0100] In some embodiments, when a GNSS fix becomes outdated in RRC_CONNECTED mode, the UE enters IDLE mode. This means that every time the UE completes a GNSS fix, a timer of duration determined by the UE is started, and upon expiration the UE will autonomously move to IDLE mode. In one embodiment, the duration of the timer may have the following values: X = {10s, 20s, 30s, 40s, 50s, 60s, 5min, 10min, 15min, 20min, 25min, 30min, 60min, 90min, 120min, infinity}.

[0101] Note that in some embodiments, a GNSS correction refers to the act of obtaining valid GNSS measurements at a given performance level.

[0102] To obtain GNSS corrections, the UE may use GNSS assistance information, i.e., information that may be broadcast to the UE or provided by other means (e.g., preconfigured or signaled in a dedicated message). The GNSS assistance information may simplify the UE's ability to obtain GNSS corrections and may reduce the time to obtain GNSS corrections. Obtaining the assistance information may occur after or before the UE needs to obtain GNSS corrections.

[0103] In some embodiments, it is assumed that the UE obtains its location information from GNSS data. The UE can then use its location for various tasks, such as calculating time and frequency pre-compensation values. When the UE has performed a GNSS correction, a GNSS validity timer will start. When this timer expires, the UE will leave connected mode, which has made network operation very challenging so far.

[0104] In some embodiments, the UE shall perform a GNSS fix before connecting to a cell. This has hitherto created a problem because the UE will have to perform multiple actions before fully connecting to the NTN cell, which may mean that although the UE has performed a GNSS fix before connecting to the NTN cell, the GNSS fix may not be sufficiently recent. Hitherto, this may result in the UE connecting to a cell when the remaining validity duration is still short. This problem can be addressed in Figure 4 As can be seen in FIG. 1 , the GNSS validity duration ends at time T during the data transmission process.

[0105] Certain aspects of the present disclosure and embodiments thereof can provide solutions to these or other challenges.Some embodiments herein require GNSS availability of UEs connected to NTN cells in different scenarios.

[0106] In some embodiments, for example, the UE may obtain GNSS assistance information, perform GNSS measurements, and start a GNSS validity duration timer. The UE may also obtain an indication of a condition regarding the GNSS validity duration. The UE, for example, based on the condition, decides whether to perform another GNSS correction or connect to the network. Depending on the decision, the UE performs either of the following operations: (i) GNSS correction and then connects to the NTN cell, or (ii) directly connects to the NTN cell.

[0107] In some embodiments, the condition is that the GNSS validity duration is above a threshold. In one such embodiment, the threshold is configured by the network. Alternatively, the threshold is hard-coded in a specification (e.g., a 3GPP specification).

[0108] In some embodiments, the indication is related to a specific connection use case, which may be RRC recovery, RRC re-establishment, handover, early data transfer (EDT), preconfigured uplink resources (PUR).

[0109] Certain embodiments may provide one or more of the following technical advantages: According to some embodiments, the network gains more control over the UE synchronization method, so that the possibility of the UE entering idle mode when the GNSS validity duration expires is minimized.

[0110] Generally, some embodiments herein introduce a threshold, where the UE is allowed to connect to a cell only if the GNSS validity duration is greater than the threshold. This requires the UE to perform GNSS sufficiently timely so that the network roughly knows that the UE can stay in the cell for at least a period of time.

[0111] For example, the threshold value may be configured by the network, for example in the system information of the cell. This allows the network to flexibly ensure that the UE can remain connected for a long enough time, and may also allow different values ​​to be configured depending on the time it takes to transmit a typical data packet. In a LEO network, packets may be transmitted much faster than in a GEO network due to propagation delays, so the configurable threshold value for LEO will naturally be lower, while the configurable threshold value for GEO will naturally be higher.

[0112] The threshold may also be hard coded, eg specified in a standard specification, so that for example the UE would be required to have a remaining duration of the GNSS validity duration above a certain value before being allowed to connect to any NTN cell.

[0113] Multiple thresholds may be defined and specified for different UE classes or categories. Such multiple thresholds may be standardized, or the thresholds and their associated UE classes or categories may be indicated in configuration data from the network (eg, in system information).

[0114] Different thresholds may also be specified or configured for different types of network access, such as: random access from the RRC_IDLE state (e.g., RRC connection establishment), random access from the RRC_INACTIVE state (e.g., RRC connection recovery), random access in a target cell during handover or access to a newly added secondary cell, random access triggered by a PDCCH command (i.e., a DCI message from the network on the PDCCH instructing the UE to perform a random access procedure), contention-based random access, and contention-free random access.

[0115] Figure 5 An example with a threshold for the GNSS validity duration can be seen in . As shown, the GNSS validity is checked before establishing a connection with an NTN cell, for example even if the GNSS validity timer has not expired.

[0116] In some embodiments, the above is configurable in that the network configures whether to use a hard-coded threshold. In the case of hard-coded, this can be a flag in the system information indicating whether the requirement should be used, while in the case of a configurable threshold, the network configures this by including the threshold (if it is not included, it is not configured). A hybrid solution is also possible, where the threshold is specified in the standard and this is in effect by default, but it can be overridden by a configured value.

[0117] In one embodiment, the requirement for GNSS validity duration is only for UEs when performing initial access, i.e. performing RRC connection establishment (sending RRCConnectionRequest). This allows the network to at least know that the GNSS state is sufficient when the UE is, for example, performing initial access (where the UE needs to be configured with security, etc.).

[0118] In another embodiment, when the UE performs an RRC resume (sending an RRCConnectionResumeRequest), the requirements for GNSS validity apply. The requirements may be the same as for RRCConnectionRequest, or may be different from those for RRCResume. This is because when the UE performs an RRCResume, the expected connection time should be significantly shorter because the context and configuration are already provisioned and available in the RAN, and the UE typically has little data to send.

[0119] In another embodiment, when the UE performs early data transfer (EDT) (sending RRCConnectionResumeRequest+data or RRC EarlyDataRequest) or pre-configured uplink resources (PUR) (sending RRC EarlyDataRequest), the requirement also applies to RRCConnectionRequest or RRCConnectionResumeRequest, or a separate requirement may be used specifically for EDT or PUR. In this case, there is a further impetus to have different requirements because the expected duration under RRC connection is expected to be much shorter.

[0120] In another embodiment, when the UE has to perform an RRC connection re-establishment (sending an RRCConnectionReestablishmentRequest), the requirement for GNSS validity may or may not be required. For example, this may force the UE to re-make GNSS fixes, or may allow the UE to not have to re-make GNSS fixes. A separate requirement for RRC connection re-establishment may be introduced.

[0121] In another embodiment, when the UE performs a handover, the network signals the requirements (if any) about the target cell, i.e., the requirements or thresholds about the GNSS validity duration. This then affects whether the UE needs to perform GNSS measurements during the handover process. The target cell can signal this, for example, in a HandoverCommand (containing configuration data that the UE should apply when accessing the target cell), which is constructed by the target node (e.g., target eNB / gNB) and sent to the source cell and then to the UE via inter-node signaling (X2).

[0122] If the UE is unable to obtain sufficiently recent GNSS corrections to meet the configured or specified minimum remaining GNSS measurement validity time requirement, then in certain embodiments the UE may still be allowed to access the network if the UE notifies the network of the failure and how long the current remaining GNSS measurement validity time is for the UE's latest GNSS measurement. If the UE accesses the network from RRC_IDLE or RRC_INACTIVE state using contention-based random access, the UE may indicate this in the RRCSetupRequest message or the RRCResumeRequest message in Msg3 or in the RRCSetupComplete message or the RRCResumeComplete message. If the UE uses random access from the RRC_CONNECTED state, the UE may include an indication in the form of a MAC CE in Msg3. If the network access (uplink transmission) is from the RRC_CONNECTED state and / or is not a random access, the UE may include the indication in the MAC CE or possibly in an RRC message (opportunistically in an RRC message that is sent anyway or in an RRC message sent just for this purpose before an expected uplink transmission). The network (e.g., eNB / gNB) may use information about the remaining GNSS measurement validity time to, for example, prioritize UEs during scheduling so that the UE can communicate as much as possible, or may end the communication needs it currently has (e.g., empty its transmission buffer) before the UE's GNSS measurement validity time expires (and possibly receive a response in the downlink). If the UE manages to obtain new GNSS measurements after having indicated to the UE that its remaining GNSS measurement validity time is below a required minimum remaining validity time (e.g., below a configured or specified threshold) and optionally also indicating the actual remaining GNSS measurement validity time, the UE may indicate this to the network (e.g., in a MAC CE or RRC message) and optionally also indicate how long the GNSS measurement validity time is.

[0123] In one embodiment, when the UE accesses the network using a random access procedure triggered by a physical downlink control channel (PDCCH) command from the network, the minimum remaining GNSS measurement validity time requirement does not apply. In one embodiment variant, this is specified in the standard. In another embodiment variant, this is configured in the system information. In yet another embodiment variant, this is indicated in the DCI containing the PDCCH command.

[0124] In one embodiment, the network (e.g., eNB / gNB) indicates in a physical downlink control channel (PDCCH) command (i.e., a DCI message that commands the UE to perform a random access procedure) that the UE may perform a random access procedure according to the PDCCH command even if the UE's remaining GNSS measurement validity time does not meet the minimum remaining GNSS measurement validity time requirement (e.g., even if the UE's remaining GNSS measurement validity time does not exceed a specified or configured threshold), and if the UE's remaining GNSS measurement validity time does not meet the minimum requirement, the UE should indicate this in conjunction with the random access procedure (e.g., in a MAC CE in Msg3). As an option, the indication may include an indication of how much time is left in the UE's GNSS measurement validity time. When the UE receives a PDCCH command containing any of these indications, the UE behaves accordingly.

[0125] In one embodiment, the network (e.g., eNB / gNB) may indicate in a PDCCH command that the time during which the UE expects to initiate a random access of the PDCCH command is extended (and optionally how long the time is) to allow the UE to have sufficient time to perform GNSS measurements before initiating the random access procedure. If the remaining GNSS measurement validity time of a UE that receives a PDCCH command including such an indication does not meet the minimum requirement, the UE performs GNSS measurements before initiating the random access procedure.

[0126] In one embodiment, a UE connected to a cell in a discontinuous coverage scenario may ignore the requirement for GNSS validity duration whenever the remaining time until the end time of coverage of the serving satellite is lower than the current GNSS validity timer of the UE, i.e., a coverage gap will start before the GNSS validity timer expires. Otherwise, if the UE complies with the requirement and obtains a new GNSS fix, the UE may miss the current coverage window and be forced to wait until the next satellite is visible. The discontinuous coverage scenario is characterized by significant coverage gaps due to the low density of satellites in the constellation. This situation may be indicated via system information or dedicated signaling.

[0127] Figure 6 Steps performed by a UE according to some embodiments are shown.

[0128] In step 1, the UE may obtain GNSS assistance information.

[0129] In step 2, the UE performs GNSS measurements and starts a GNSS validity duration timer.

[0130] In step 3, the UE obtains an indication of the conditions for the GNSS validity duration. This may be obtained from a hard-coded value or from configuration information from the network, for example in the form of a configuration parameter signaled via system information or via dedicated signaling (e.g. RRC signaling MAC signaling or DCI signaling). The indication may be the minimum remaining time of the GNSS validity duration that the UE must have when accessing the network.

[0131] In step 4, the UE decides to perform another GNSS fix (eg, if its remaining GNSS validity time does not exceed the minimum required time) or to connect to the network (eg, if the UE's remaining GNSS validity time exceeds the minimum required time).

[0132] In step 5, depending on the decision in step 4, the UE performs either of the following operations: (a) GNSS correction and then connects to the NTN cell, or (b) directly connects to the NTN cell.

[0133] However, some embodiments take into account the fact that frequent GNSS corrections may shorten the battery life of a UE (e.g., an IoT UE). Then, in some embodiments, the IoT UE is allowed to relax the above GNSS correction requirements under certain specified conditions, i.e., it may bypass steps 3 and 4 and perform step 5b instead of step 5a. For example, these conditions may include one or more of the following: (i) when the UE is configured with a power saving mode; (ii) when the UE is configured with a specific number of repetitions; (iii) when the UE belongs to a specific coverage class; or (iv) when the UE belongs to a specific coverage enhancement (CE) mode / class / level.

[0134] As used herein, the terms "GNSS validity duration", "GNSS validity time", "GNSS measurement validity duration", and "GNSS measurement validity time" may be used interchangeably. Similarly, the terms "GNSS validity timer", "GNSS validity duration timer", "GNSS measurement validity timer", and "GNSS measurement validity duration timer" may be used interchangeably. In general, the validity of a geolocation fix 20 herein may be specified or reflected as the validity of a geolocation measurement or data associated with the geolocation fix.

[0135] Furthermore, although some embodiments herein are described in the context of LTE (since GNSS validity duration has only been introduced for IoT NTN so far), the embodiments herein may also be applicable to 5G NR.

[0136] In view of the modifications and changes in this article, Figure 7A method is depicted performed by a communication device 18 configured for use in a non-terrestrial network NTN 10 according to certain embodiments. The method includes making a decision as to whether to update the geolocation fix 20 of the communication device 18 even if the geolocation fix 20 is valid before accessing the NTN 10 (block 700). In some embodiments, the decision is made based on a remaining duration 26 for which the geolocation fix 20 will be valid. Regardless, the method may also include updating or refraining from updating the geolocation fix 20 before accessing the NTN 10 based on the decision (block 710).

[0137] In some embodiments, the making includes: if the remaining duration 26 is less than the threshold duration, then making a decision to update the geolocation fix 20 before accessing the NTN 10. In some embodiments, the making also includes: if the remaining duration is greater than the threshold duration, then making a decision to avoid updating the geolocation fix 20 before accessing the NTN 10. In one or more of these embodiments, the method also includes: receiving the threshold duration from the NTN 10 (e.g., in system information of the NTN 10) (block 705). In one or more of these embodiments, the receiving of the threshold duration overrides a preconfigured threshold duration preconfigured at the communication device 18. In other embodiments, the communication device 18 is preconfigured with the threshold duration.

[0138] In some embodiments, the threshold duration is specific to the purpose for which the communication device 18 is accessing the NTN 10 or the process that the communication device 18 is using to access the NTN 10. In some embodiments, the threshold duration is alternatively or additionally specific to the type of satellite providing the NTN 10 cell that the communication device 18 is accessing. In some embodiments, the threshold duration is alternatively or additionally specific to the orbital altitude of the satellite providing the NTN 10 cell that the communication device 18 is accessing. In some embodiments, the threshold duration is alternatively or additionally specific to the type, category, or class of the communication device 18.

[0139] In some embodiments, the method further includes determining whether to make a decision based on a remaining duration for which the geolocation correction 20 will be valid (block 707). In one or more of these embodiments, the determination is performed based on whether the communication device 18 receives signaling indicating that the communication device 18 is to make a decision based on a remaining duration for which the geolocation correction 20 will be valid. In some embodiments, the signaling includes a threshold duration. In some embodiments, the signaling includes a flag indicating whether the communication device 18 is to make a decision based on a remaining duration for which the geolocation correction 20 will be valid. In some embodiments, the determination includes determining that if the communication device 18 is configured with a power save mode, the decision is not made based on the remaining duration for which the geolocation correction 20 will be valid. Alternatively, the determination includes determining that if the communication device 18 is configured to perform at least a threshold number of transmission repetitions, the decision is not made based on the remaining duration for which the geolocation correction 20 will be valid. Alternatively, the determination includes determining that if the communication device 18 belongs to one or more specific coverage classes, the decision is not made based on the remaining duration for which the geolocation correction 20 will be valid. Alternatively, the determination includes determining that if the communication device 18 belongs to one or more specific coverage enhancement modes, classes, or levels, then the determination is not made based on the remaining duration that the geolocation fix 20 will be valid. In some embodiments, the determination is performed based on the purpose for which the communication device 18 is accessing the NTN 10 or the process that the communication device 18 is using to access the NTN 10. In some embodiments, the determination includes determining that if the communication device 18 is performing an initial access to the NTN 10, then the determination is made based on the remaining duration that the geolocation fix 20 will be valid. In some embodiments, the determination includes determining that if the access to the NTN 10 is triggered by a downlink control channel command from the NTN 10, then the determination is not made based on the remaining duration that the geolocation fix 20 will be valid. Alternatively, the determination includes determining that if the coverage of the serving satellite will be lost before the geolocation fix 20 becomes invalid, then the determination is not made based on the remaining duration that the geolocation fix 20 will be valid.

[0140] In some embodiments, the method further includes determining a threshold duration based on an estimated duration that the communication device 18 will remain connected to the NTN 10 .

[0141] In some embodiments, the method further includes determining a threshold duration based on an estimated duration of a connection that the communication device 18 is to establish, reestablish, or restore as part of accessing the NTN 10 .

[0142] In some embodiments, accessing the NTN 10 includes performing random access to the NTN 10 and / or establishing, re-establishing or recovering a connection with the NTN 10 .

[0143] In some embodiments, accessing the NTN 10 includes performing an Early Data Transfer (EDT) or a Preconfigured Uplink Resource (PUR) transmission.

[0144] In some embodiments, accessing the NTN 10 includes performing random access to a cell of the NTN 10 and / or establishing, re-establishing or resuming a connection with a cell of the NTN 10 .

[0145] In some embodiments, accessing the NTN 10 includes transitioning to a Radio Resource Control (RRC) connected state.

[0146] In some embodiments, the geolocation fix 20 comprises a Global Navigation Satellite System (GNSS) location fix.

[0147] In some embodiments, the geolocation fix 20 is valid while the validity timer is running, wherein the remaining duration for which the geolocation fix 20 will be valid is the remaining duration of the validity timer.

[0148] In some embodiments, when the communication device 18 obtains or updates the geolocation fix 20, the validity timer is started or restarted.

[0149] In some embodiments, the communication device 18 is configured to transition to the RRC Idle state upon expiration of the validity timer.

[0150] In some embodiments, the communication device 18 is configured to transition to the RRC idle state when the geolocation fix 20 becomes invalid.

[0151] In some embodiments, the method further comprises determining, based on the geolocation fix 20, whether the precompensated timing advance is updated depending on the determination (block 720). The method further comprises performing a random access channel transmission as part of accessing the NTN 10 using the determined precompensated timing advance (block 730).

[0152] Figure 8 A method performed by a network node 30 configured for use in a non-terrestrial network is shown. The method includes sending signaling to a communication device 18 that controls a decision of the communication device 18 as to whether to update the geolocation fix 20 of the communication device 18 even if the geolocation fix 20 was valid before accessing the NTN 10 (block 820).

[0153] In some embodiments, the method further includes generating signaling (block 810), eg, as described below.

[0154] In some embodiments, the signaling indicates a threshold duration after accessing the NTN 10 that the geolocation fix 20 must remain valid for the communication device 18 to access the NTN 10 without updating the geolocation fix 20. In one or more of these embodiments, the method may further include determining the threshold duration (block 800).

[0155] In some embodiments, the indicated threshold duration is to override a preconfigured threshold duration that is preconfigured at the communication device 18. In some embodiments, the indicated threshold duration is specific to the purpose for which the communication device 18 is accessing the NTN 10 or the process that the communication device 18 is using to access the NTN 10. In some embodiments, the indicated threshold duration is specific to the type of satellite providing the NTN 10 cell that the communication device 18 is accessing. In some embodiments, the indicated threshold duration is specific to the orbital altitude of the satellite providing the NTN 10 cell that the communication device 18 is accessing. In some embodiments, the indicated threshold duration is specific to the type, category, or class of the communication device 18.

[0156] In some embodiments, the signaling indicates whether the communication device 18 is to make a decision as to whether to update the geolocation fix 20 while the geolocation fix 20 is valid.

[0157] In some embodiments, the signaling includes a flag indicating whether the communication device 18 is to make a decision based on the remaining duration that the geolocation fix 20 will be valid.

[0158] In some embodiments, the signaling indicates that if the communication device 18 is configured with a particular power saving mode, if the communication device 18 is configured to perform at least a threshold number of transmission repetitions, if the communication device 18 belongs to one or more particular coverage classes, or if the communication device 18 belongs to one or more particular coverage enhancement modes, classes, or levels, the communication device 18 is to update the geolocation fix 20. In some embodiments, the signaling indicates a particular power saving mode, a threshold number of transmission repetitions, one or more particular coverage classes, or one or more particular coverage enhancement modes.

[0159] In some embodiments, the signaling indicates that the communication device 18 is to update the geolocation fix 20 if the communication device 18 is accessing the NTN 10 for a specific purpose or using a specific procedure.

[0160] In some embodiments, the signaling indicates that if the communication device 18 is performing an initial access to the NTN 10 , the communication device 18 is to update the geolocation fix 20 .

[0161] In some embodiments, the signaling indicates that the communication device 18 is not to update the geolocation fix 20 if access to the NTN 10 is triggered by a downlink control channel command from the NTN 10. Alternatively, the signaling indicates that the communication device 18 is not to update the geolocation fix 20 if coverage of the serving satellite will be lost before the geolocation fix 20 becomes invalid.

[0162] In some embodiments, accessing the NTN 10 includes performing random access to the NTN 10 and / or establishing, re-establishing or recovering a connection with the NTN 10 .

[0163] In some embodiments, accessing the NTN 10 includes performing an Early Data Transfer (EDT) or a Preconfigured Uplink Resource (PUR) transmission.

[0164] In some embodiments, accessing the NTN 10 includes performing random access to a cell of the NTN 10 and / or establishing, re-establishing or resuming a connection with a cell of the NTN 10 .

[0165] In some embodiments, accessing the NTN 10 includes transitioning to a Radio Resource Control (RRC) connected state.

[0166] In some embodiments, the geolocation fix 20 comprises a Global Navigation Satellite System (GNSS) location fix.

[0167] In some embodiments, the geolocation fix 20 is valid while the validity timer is running. In some embodiments, the signaling controls whether or how the communication device 18 makes a decision based on the remaining duration that the geolocation fix 20 will be valid. In one or more of these embodiments, the geolocation fix 20 is valid while the validity timer is running. In some embodiments, the remaining duration that the geolocation fix 20 will be valid is the remaining duration of the validity timer. In one or more of these embodiments, when the communication device 18 obtains or updates the geolocation fix 20, the validity timer is started or restarted. In one or more of these embodiments, the communication device 18 is configured to transition to the RRC idle state when the validity timer expires.

[0168] In some embodiments, the communication device 18 is configured to transition to the RRC idle state when the geolocation fix 20 becomes invalid.

[0169] The embodiments herein also include corresponding apparatuses. The embodiments herein, for example, include a communication device 18 , which is configured to perform any of the steps of any of the embodiments for the communication device 18 described above.

[0170] Embodiments also include a communication device 18, which includes a processing circuit and a power supply circuit. The processing circuit is configured to perform any of the steps described above for any embodiment of the communication device 18. The power supply circuit is configured to supply power to the communication device 18.

[0171] Embodiments also include a communication device 18 that includes a processing circuit. The processing circuit is configured to perform any of the steps described above for any embodiment of the communication device 18. In some embodiments, the communication device 18 also includes a communication circuit.

[0172] Embodiments also include a communication device 18 that includes a processing circuit and a memory. The memory contains instructions executable by the processing circuit, whereby the communication device 18 is configured to perform any of the steps described above for any embodiment of the communication device 18.

[0173] Embodiments further include user equipment (UE). UE includes an antenna configured to send and receive wireless signals. UE also includes a radio front-end circuit, which is connected to the antenna and the processing circuit and is configured to adjust the signal transmitted between the antenna and the processing circuit. The processing circuit is configured to perform any step of any embodiment of the communication device 18 described above. In some embodiments, the UE also includes an input interface, which is connected to the processing circuit and is configured to allow information to be input into the UE for processing by the processing circuit. The UE may include an output interface, which is connected to the processing circuit and is configured to output information from the UE that has been processed by the processing circuit. The UE may also include a battery, which is connected to the processing circuit and is configured to power the UE.

[0174] The embodiments herein also include a network node 30 configured to perform any of the steps described above for any of the embodiments of the network node 30 .

[0175] The embodiment also includes a network node 30, which includes a processing circuit and a power supply circuit. The processing circuit is configured to perform any of the steps described above for any embodiment of the network node 30. The power supply circuit is configured to supply power to the network node 30.

[0176] The embodiment further comprises a network node 30 comprising a processing circuit. The processing circuit is configured to perform any of the steps described above for any embodiment of the network node 30. In some embodiments, the network node 30 further comprises a communication circuit.

[0177] The embodiment further comprises a network node 30 comprising a processing circuit and a memory. The memory comprises instructions executable by the processing circuit, whereby the network node 30 is configured to perform any of the steps for any of the embodiments of the network node 30 described above.

[0178] More specifically, the above-mentioned device can perform the method and any other processing of this article by implementing any functional component (means), module, unit or circuit. In one embodiment, for example, the device includes a corresponding circuit or circuit system configured to perform the steps shown in the method diagram. In this regard, the circuit or circuit system may include a circuit and / or one or more microprocessors and a memory dedicated to performing a specific functional process. For example, the circuit system may include one or more microprocessors or microcontrollers, and other digital hardware, which may include a digital signal processor (DSP), a dedicated digital logic, etc. The processing circuit may be configured to execute a program code stored in a memory, and the memory may include one or more types of memory, such as a read-only memory (ROM), a random access memory, a cache memory, a flash memory device, an optical storage device, etc. In multiple embodiments, the program code stored in the memory may include program instructions for executing one or more telecommunications and / or data communication protocols and instructions for executing one or more technologies described herein. In an embodiment using a memory, the memory stores a program code, which executes the technology described herein when executed by one or more processors.

[0179] Fig. 9 For example, a communication device 18 implemented according to one or more embodiments is shown. As shown, the communication device 18 includes a processing circuit 910 and a communication circuit 920. The communication circuit 920 (e.g., a radio circuit) is configured to send and / or receive information to one or more other nodes via any communication technology. Such communication can be performed via one or more antennas internal or external to the wireless communication device 900. The processing circuit 910 is configured to perform, for example, by executing instructions stored in the memory 930. Figure 7 In this regard, the processing circuit 910 may implement specific functional components, units or modules.

[0180] Fig.10 100 is a diagram showing a network node 30 implemented in accordance with one or more embodiments. As shown, the network node 30 includes a processing circuit 1010 and a communication circuit 1020. The communication circuit 1020 is configured to send and / or receive information to and / or from one or more other nodes, for example, via any communication technology. The processing circuit 1010 is configured to perform, for example, by executing instructions stored in a memory 1030. Figure 8 In this regard, the processing circuit 1010 may implement specific functional components, units or modules.

[0181] Those skilled in the art will also understand that the embodiments herein also include corresponding computer programs.

[0182] The computer program includes instructions that, when executed on at least one processor of a device, cause the device to perform any of the above-mentioned corresponding processes. In this regard, the computer program may include one or more code modules corresponding to the above-mentioned components or units.

[0183] The embodiment also includes a carrier embodying such a computer program. The carrier may include one of an electronic signal, an optical signal, a radio signal or a computer-readable storage medium.

[0184] In this regard, embodiments herein also include a computer program product stored on a non-transitory computer-readable (storage or recording) medium and including instructions that, when executed by a processor of a device, cause the device to perform as described above.

[0185] The embodiment also includes a computer program product including a program code portion, wherein the program code portion is used to perform the steps of any embodiment described herein when the computer program product is executed by a computing device. The computer program product may be stored on a computer readable recording medium.

[0186] Fig.11 An example of a communication system 1100 is shown in accordance with some embodiments.

[0187] In this example, the communication system 1100 includes a telecommunications network 1102, which includes an access network 1104 (e.g., a radio access network (RAN)) and a core network 1106 (which includes one or more core network nodes 1108). The access network 1104 includes one or more access network nodes, such as network nodes 1110a and 1110b (one or more of which may be collectively referred to as network nodes 1110), or any other similar third generation partnership project (3GPP) access nodes or non-3GPP access points. The network node 1110 facilitates direct or indirect connection of user equipment (UE), such as connecting UE 1112a, 1112b, 1112c, and 1112d (one or more of which may be collectively referred to as UE 1112) to the core network 1106 via one or more wireless connections.

[0188] Example wireless communications over wireless connections include sending and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for transmitting information without the use of wires, cables, or other material conductors. In addition, in different embodiments, the communication system 1100 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that can facilitate or participate in the communication of data and / or signals (whether via a wired connection or a wireless connection). The communication system 1100 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar types of systems.

[0189] UE 1112 may be any of a variety of communication devices, including wireless devices that are arranged, configured and / or operable to wirelessly communicate with network node 1110 and other communication devices. Similarly, network node 1110 is arranged, capable, configured and / or operable to communicate directly or indirectly with UE 1112 and / or other network nodes or devices in telecommunication network 1102 to enable and / or provide network access (e.g., wireless network access) and / or perform other functions (e.g., management) in telecommunication network 1102.

[0190] In the depicted example, the core network 1106 connects the network node 1110 to one or more hosts, such as the host 1116. These connections may be direct connections, or indirect connections via one or more intermediate networks or devices. In other examples, the network node may be directly coupled to the host. The core network 1106 includes one or more core network nodes (e.g., core network node 1108) composed of hardware and software components. The features of these components may be substantially similar to those described for UE, network nodes, and / or hosts, so that their descriptions are generally applicable to the corresponding components of the core network node 1108. The example core network node includes one or more functions of: a mobile switching center (MSC), a mobility management entity (MME), a home subscriber server (HSS), an access and mobility management function (AMF), a session management function (SMF), an authentication server function (AUSF), a subscription identifier de-hiding function (SIDF), a unified data management (UDM), a security edge protection agent (SEPP), a network open function (NEF), and / or a user plane function (UPF).

[0191] The host 1116 may be under the ownership or control of a service provider other than the operator or provider of the access network 1104 and / or the telecommunications network 1102, and may be operated by or on behalf of the service provider. The host 1116 may host various applications to provide one or more services. Examples of such applications include real-time and pre-recorded audio / video content, data collection services (such as obtaining and compiling data about various environmental conditions detected by multiple UEs), analysis functions, social media, functions for controlling or otherwise interacting with remote devices, functions for alarm and monitoring centers, or any other such functions performed by a server.

[0192] on the whole, Fig.11 The communication system 1100 enables connections between UEs, network nodes, and hosts. In this sense, the communication system can be configured to operate according to predefined rules or procedures, such as specific standards, including but not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standards (e.g., 6G); Wireless Local Area Network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard (WiFi); and / or any other suitable wireless communication standards, such as Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-wave, Near Field Communication (NFC), ZigBee, LiFi, and / or any Low Power Wide Area Network (LPWAN) standards, such as LoRa and Sigfox.

[0193] In some examples, telecommunication network 1102 is a cellular network implementing 3GPP standardized features. Thus, telecommunication network 1102 may support network slicing to provide different logical networks to different devices connected to telecommunication network 1102. For example, telecommunication network 1102 may provide ultra-reliable low latency communication (URLLC) services to some UEs while providing enhanced mobile broadband (eMBB) services to other UEs, and / or provide massive machine type communication (mMTC) / massive IoT services to other UEs.

[0194] In some examples, UE 1112 is configured to send and / or receive information without direct human interaction. For example, the UE may be designed to send information to access network 1104 on a predetermined schedule when triggered by an internal or external event or in response to a request from access network 1104. Additionally, the UE may be configured to operate in a single RAT or multi-RAT or multi-standard mode. For example, the UE may operate using any one or a combination of Wi-Fi, NR (New Radio), and LTE, i.e., configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved UMTS Terrestrial Radio Access Network) New Radio-Dual Connectivity (EN-DC).

[0195] In this example, the hub 1114 communicates with the access network 1104 to facilitate indirect communication between one or more UEs (e.g., UE 1112c and / or 1112d) and a network node (e.g., network node 1110b). In some examples, the hub 1114 may be a controller, a router, a content source and analysis, or any other communication device described herein with respect to the UE. For example, the hub 1114 may be a broadband router that enables the UE to access the core network 1106. As another example, the hub 1114 may be a controller that sends commands or instructions to one or more actuators in the UE. The commands or instructions may be received from the UE, the network node 1110, or received by an executable code, a script, a process, or other instructions in the hub 1114. As another example, the hub 1114 may be a data collector that acts as a temporary storage device for UE data, and in some embodiments, analysis or other processing of the data may be performed. As another example, the hub 1114 may be a content source. For example, for a UE that is a VR head-mounted device, display, speaker, or other media delivery device, the hub 1114 can obtain VR assets, video, audio, or other media or data related to the sensory information via the network node, and then the hub 1114 provides it to the UE directly, after performing local processing, and / or after adding additional local content. In another example, the hub 1114 acts as a proxy server or orchestrator for the UE, especially when one or more UEs are low-energy IoT devices.

[0196] Hub 1114 can have constant / persistent or intermittent connection with network node 1110b. Hub 1114 can also allow different communication schemes and / or scheduling between hub 1114 and UE (e.g., UE 1112c and / or 1112d) and hub 1114 and core network 1106. In other examples, hub 1114 is connected to core network 1106 and / or one or more UEs via wired connection. In addition, hub 1114 can be configured to connect to M2M service provider and / or connect to another UE via direct connection through access network 1104. In some scenarios, UE can establish wireless connection with network node 1110, while still connected via hub 1114 by wired or wireless connection. In some embodiments, hub 1114 can be a dedicated hub, that is, its main function is to route communication from network node 1110b to UE / from UE to network node 1110b. In other embodiments, the hub 1114 may be a non-dedicated hub, that is, a device that is operable to route communications between the UE and the network node 1110b, but is also capable of operating as a communications origin and / or endpoint for a particular data channel.

[0197] Fig.12 UE 1200 according to some embodiments is shown. As used herein, UE refers to a device capable of, configured, arranged and / or operable to wirelessly communicate with a network node and / or other UEs. Examples of UEs include, but are not limited to, smart phones, mobile phones, cellular phones, voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, game consoles or devices, music storage devices, playback devices, wearable terminal devices, wireless endpoints, mobile stations, tablet computers, laptop computers, laptop embedded devices (LEEs), laptop mounted devices (LMEs), smart devices, wireless client equipment (CPEs), vehicle-mounted or vehicle-mounted embedded / integrated wireless devices, etc. Other examples include any UE identified by the Third Generation Partnership Project (3GPP), including narrowband Internet of Things (NB-IoT) UEs, machine type communications (MTC) UEs, and / or enhanced MTC (eMTC) UEs.

[0198] The UE may support device-to-device (D2D) communications, for example, by implementing 3GPP standards for sidelink communications, dedicated short-range communications (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the associated device. Rather, a UE may represent a device that is intended to be sold to or operated by a human user but may not be, or may not initially be, associated with a particular human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended to be sold to or operated by an end user but may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0199] UE 1200 includes processing circuitry 1202, which is operatively coupled to input / output interface 1206, power supply 1208, memory 1210, communication interface 1212, and / or any other components or any combination thereof via bus 1204. Some UEs may utilize Fig.12 All or a subset of the components shown in . The level of integration between components may vary depending on the UE. In addition, some UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0200] The processing circuit 1202 is configured to process instructions and data, and may be configured to implement any sequential state machine operable to execute instructions stored as a machine-readable computer program in the memory 1210. The processing circuit 1202 may be implemented as one or more hardware-implemented state machines (e.g., using discrete logic, field programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), etc.); programmable logic and appropriate firmware; one or more stored computer programs, general-purpose processors (e.g., microprocessors or digital signal processors (DSPs)) and appropriate software; or any combination of the above. For example, the processing circuit 1202 may include multiple central processing units (CPUs).

[0201] In this example, the input / output interface 1206 can be configured to provide one or more interfaces to an input device, an output device, or one or more input and / or output devices. Examples of output devices include speakers, sound cards, video cards, displays, monitors, printers, actuators, transmitters, smart cards, another output device, or any combination thereof. An input device can allow a user to capture information into the UE 1200. Examples of input devices include touch-sensitive displays or presence-sensitive displays, cameras (e.g., digital cameras, digital video cameras, web cameras, etc.), microphones, sensors, mice, trackballs, direction pads, trackpads, rollers, smart cards, etc. The presence-sensitive display can include a capacitive or resistive touch sensor to sense input from a user. The sensor can be, for example, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device can use an interface port of the same type as an input device. For example, a universal serial bus (USB) port can be used to provide input devices and output devices.

[0202] In some embodiments, the power supply 1208 is configured as a battery or a battery pack. Other types of power supplies may be used, such as an external power supply (e.g., a power outlet), a photovoltaic device, or a battery. The power supply 1208 may also include a power supply circuit for transmitting power from the power supply 1208 itself and / or an external power supply to various parts of the UE 1200 via an input circuit or interface (e.g., a power cord). The transmitted power may be used, for example, to charge the power supply 1208. The power supply circuit may perform any formatting, conversion, or other modification of the power from the power supply 1208 to make the power suitable for the corresponding components of the UE 1200 to which the power is provided.

[0203] The memory 1210 may be or be configured to include a memory such as a random access memory (RAM), a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a magnetic disk, an optical disk, a hard disk, a removable cassette, a flash drive, etc. In one example, the memory 1210 includes one or more application programs 1214 (e.g., an operating system, a web browser application, a widget, a widget engine, or other application) and corresponding data 1216. The memory 1210 may store any of a variety of operating systems or a combination of operating systems for use by the UE 1200.

[0204] The memory 1210 may be configured to include a plurality of physical drive units, such as a redundant array of independent disks (RAID), a flash memory, a USB flash drive, an external hard drive, a thumb drive, a pen drive, a key drive, a high-density digital versatile disc (HD-DVD) optical drive, an internal hard drive, a Blu-ray optical drive, a holographic digital data storage (HDDS) optical drive, an external mini dual in-line memory module (DIMM), a synchronous dynamic random access memory (SDRAM), an external micro-DIMM SDRAM, a smart card memory (e.g., a tamper-proof module in the form of a universal integrated circuit card (UICC), including one or more subscriber identity modules (SIMs), such as USIM and / or ISIM), other memories, or any combination thereof. The UICC may be, for example, an embedded UICC (eUICC), an integrated UICC (iUICC), or a removable UICC, commonly referred to as a “SIM card”. The memory 1210 may allow the UE 1200 to access instructions, applications, etc. stored on a temporary or non-temporary storage medium to offload data or upload data. An article of manufacture, such as utilizing a communication system, may be tangibly embodied as or in memory 1210 , which may be or include a device-readable storage medium.

[0205] The processing circuit 1202 may be configured to communicate with an access network or other network using a communication interface 1212. The communication interface 1212 may include one or more communication subsystems and may include an antenna 1222 or be communicatively coupled to the antenna 1222. The communication interface 1212 may include one or more transceivers for communicating (e.g., by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network)). Each transceiver may include a transmitter 1218 and / or a receiver 1220 suitable for providing network communications (e.g., optical, electrical, frequency allocation, etc.). In addition, the transmitter 1218 and the receiver 1220 may be coupled to one or more antennas (e.g., antenna 1222), and may share circuit components, software, or firmware, or may be implemented separately instead.

[0206] In the illustrated embodiment, the communication functionality of the communication interface 1212 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communication such as Bluetooth, near field communication, location-based communication such as using a global positioning system (GPS) to determine location, another similar communication functionality, or any combination thereof. Communication may be implemented according to one or more communication protocols and / or standards, such as IEEE 802.11, code division multiple access (CDMA), wideband code division multiple access (WCDMA), GSM, LTE, new radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / Internet protocol (TCP / IP), synchronous optical network (SONET), asynchronous transfer mode (ATM), QUIC, hypertext transfer protocol (HTTP), etc.

[0207] Regardless of the type of sensor, the UE may provide an output of the data captured by its sensor via a wireless connection to a network node through its communication interface 1212. The data captured by the UE's sensor may be transmitted via another UE via a wireless connection to a network node. The output may be periodic (e.g., every 15 minutes if it reports the sensed temperature), random (e.g., to balance the reporting load from multiple sensors), in response to a trigger event (e.g., sending an alarm when humidity is detected), in response to a request (e.g., a user-initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0208] As another example, the UE includes an actuator, motor, or switch associated with a communication interface that is configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input, the state of the actuator, motor, or switch can change. For example, the UE can include a motor that adjusts a control surface or rotor of a drone in flight based on the received input, or adjusts a robotic arm performing a medical procedure based on the received input.

[0209] When in the form of an Internet of Things (IoT) device, a UE may be a device for one or more application areas including, but not limited to, urban wearable technology, extended industry applications, and healthcare. Non-limiting examples of such IoT devices are devices that are or are embedded in: a connected refrigerator or freezer, a television, connected lighting, an electric meter, a robotic vacuum cleaner, a voice-controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / humidity sensor, an electric door lock, a connected doorbell, an air conditioning system such as a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for augmented reality (AR) or virtual reality (VR), a wearable device for tactile enhancement or sensory enhancement, a sprinkler, an animal or item tracking device, a sensor for monitoring plants or animals, an industrial robot, an unmanned aerial vehicle (UAV), and any kind of medical device such as a heart rate monitor or a teleoperated surgical robot. In addition to the above, the present invention also provides a device that is used to monitor the surrounding environment, such as a refrigerator or freezer, a television, a connected lighting device, an electric meter, a robotic vacuum cleaner, a voice-controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / humidity sensor, an electric door lock, a connected doorbell, an air conditioning system such as a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for augmented reality (AR) or virtual reality (VR), a wearable device for tactile enhancement or sensory enhancement, a sprinkler, an animal or item tracking device, a sensor for monitoring plants or animals, an industrial robot, an unmanned aerial vehicle (UAV), and any kind of medical device such as a heart rate monitor or a teleoperated surgical robot. In addition to the above, the present invention also provides a device that is used to monitor the surrounding Fig.12 In addition to the other components depicted in the illustrated UE 1200 , a UE in the form of an IoT device may include circuitry and / or software depending on the intended application of the IoT device.

[0210] As yet another specific example, in an IoT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements and sends the results of such monitoring and / or measurements to another UE and / or a network node. In this case, the UE may be an M2M device, which may be referred to as an MTC device in the 3GPP context. As a specific example, a UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle (e.g., a car, bus, truck), a ship, and an airplane, or other device that is capable of monitoring and / or reporting its operating status or other functions associated with its operation.

[0211] In practice, any number of UEs may be used together for a single use case. For example, a first UE may be or be integrated into a drone and provide the drone's speed information (obtained via a speed sensor) to a second UE that is a remote controller for operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g., by controlling an actuator) to increase or decrease the speed of the drone. The first UE and / or the second UE may also include multiple of the functions described above. For example, a UE may include a sensor and an actuator and handle data communications for both the speed sensor and the actuator.

[0212] Fig.13A network node 1300 according to some embodiments is shown. As used herein, a network node refers to a device capable of, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or other network nodes or devices in a telecommunications network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs), and NR Node Bs (gNBs)).

[0213] Base stations may be classified based on the amount of coverage they provide (or in other words, their transmit power class), and may therefore be referred to as femto base stations, pico base stations, micro base stations, or macro base stations, depending on the amount of coverage provided. A base station may be a relay node or a relay donor node that controls a relay. A network node may also include one or more (or all) parts of a distributed radio base station (e.g., a centralized digital unit and / or a remote radio unit (RRU), sometimes referred to as a remote radio head (RRH)). Such a remote radio unit may or may not be integrated with an antenna as an antenna-integrated radio. Portions of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0214] Other examples of network nodes include a multi-transmission point (multi-TRP) 5G access node, a multi-standard radio MSR device (such as an MSR BS), a network controller such as a radio network controller (RNC) or a base station controller (BSC), a base transceiver station (BTS), a transmission point, a transmission node, a multi-cell / multicast coordination entity (MCE), an operation and maintenance (O&M) node, an operation support system (OSS) node, a self-organizing network (SON) node, a positioning node (e.g., an evolved serving mobile positioning center (E-SMLC)), and / or a minimization of drive tests (MDT).

[0215] The network node 1300 includes a processing circuit 1302, a memory 1304, a communication interface 1306, and a power supply 1308. The network node 1300 may include multiple physically separated components (e.g., a node B component and an RNC component, or a BTS component and a BSC component, etc.), each of which may have its own corresponding components. In certain scenarios where the network node 1300 includes multiple separate components (e.g., BTS and BSC components), one or more separate components may be shared between multiple network nodes. For example, a single RNC may control multiple node Bs. In such a scenario, in some cases, each unique node B and RNC pair may be considered as a single separate network node. In some embodiments, the network node 1300 may be configured to support multiple radio access technologies (RATs). In such an embodiment, some components may be repeated (e.g., separate memories 1304 for different RATs), while some components may be reused (e.g., the same antenna 1310 may be shared by different RATs). The network node 1300 may also include various sets of example components for different wireless technologies (e.g., GSM, WCDMA, LTE, NR, Wi-Fi, Zigbee, Z-wave, LoRaWAN, radio frequency identification (RFID), or Bluetooth wireless technologies) integrated into the network node 1300. These wireless technologies may be integrated into the same or different chips or chipsets and other components within the network node 1300.

[0216] The processing circuit 1302 may include a combination of one or more of a microprocessor, a controller, a microcontroller, a central processing unit, a digital signal processor, an application specific integrated circuit, a field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic that is operable to provide network node 1300 functionality alone or in combination with other network node 1300 components (e.g., memory 1304).

[0217] In some embodiments, processing circuitry 1302 includes a system on a chip (SOC). In some embodiments, processing circuitry 1302 includes one or more of radio frequency (RF) transceiver circuitry 1312 and baseband processing circuitry 1314. In some embodiments, radio frequency (RF) transceiver circuitry 1312 and baseband processing circuitry 1314 may be on separate chips (or chipsets), boards, or units (e.g., a radio unit and a digital unit). In alternative embodiments, some or all of RF transceiver circuitry 1312 and baseband processing circuitry 1314 may be on the same chip or chipset, board, or unit.

[0218] Memory 1304 may include any form of volatile or non-volatile computer-readable memory, including, but not limited to, permanent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (e.g., hard disk), removable storage media (e.g., flash drive, compact disk (CD) or digital video disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable storage device that stores information, data and / or instructions that can be used by processing circuit 1302. Memory 1304 may store any suitable instructions, data or information, including computer programs, software, applications (including one or more of logic, rules, code, tables, etc.) and / or other instructions that can be executed by processing circuit 1302 and utilized by network node 1300. Memory 1304 may be used to store any calculations performed by processing circuit 1302 and / or any data received via communication interface 1306. In some embodiments, processing circuit 1302 and memory 1304 are integrated.

[0219] The communication interface 1306 is used in the wired or wireless communication of signaling and / or data between network nodes, access networks and / or UEs. As shown in the figure, the communication interface 1306 includes a port / terminal 1316 to send and receive data from the network, for example, via a wired connection. The communication interface 1306 also includes a radio front-end circuit 1318 that can be coupled to an antenna 1310 or as a part of an antenna 1310 in some embodiments. The radio front-end circuit 1318 includes a filter 1320 and an amplifier 1322. The radio front-end circuit 1318 can be connected to the antenna 1310 and the processing circuit 1302. The radio front-end circuit 1318 can be configured to adjust the signal transmitted between the antenna 1310 and the processing circuit 1302. The radio front-end circuit 1318 can receive digital data that will be sent to other network nodes or UEs via a wireless connection. The radio front-end circuit 1318 can use a combination of a filter 1320 and / or an amplifier 1322 to convert digital data into a radio signal with appropriate channel and bandwidth parameters. The radio signal can then be transmitted via the antenna 1310. Similarly, when receiving data, antenna 1310 may collect radio signals, which may then be converted into digital data by radio front end circuitry 1318. The digital data may be passed to processing circuitry 1302. In other embodiments, the communication interface may include different components and / or different combinations of components.

[0220] In some alternative embodiments, the network node 1300 does not include a separate radio front end circuit 1318, but rather, the processing circuit 1302 includes the radio front end circuit and is connected to the antenna 1310. Similarly, in some embodiments, all or part of the RF transceiver circuit 1312 is part of the communication interface 1306. In other embodiments, the communication interface 1306 includes one or more ports or terminals 1316, the radio front end circuit 1318, and the RF transceiver circuit 1312 as part of a radio unit (not shown), and the communication interface 1306 communicates with the baseband processing circuit 1314, which is part of the digital unit (not shown).

[0221] Antenna 1310 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals. Antenna 1310 may be coupled to radio front end circuit 1318 and may be any type of antenna capable of wirelessly sending and receiving data and / or signals. In some embodiments, antenna 1310 is separate from network node 1300 and may be connected to network node 1300 via an interface or port.

[0222] Antenna 1310, communication interface 1306 and / or processing circuit 1302 can be configured to perform any receiving operation and / or certain obtaining operation described herein as being performed by a network node. Any information, data and / or signal can be received from a UE, another network node and / or any other network device. Similarly, antenna 1310, communication interface 1306 and / or processing circuit 1302 can be configured to perform any sending operation described herein as being performed by a network node. Any information, data and / or signal can be sent to a UE, another network node and / or any other network device.

[0223] The power supply 1308 provides power to the various components of the network node 1300 in a form suitable for the respective components (e.g., at the voltage and current levels required by each respective component). The power supply 1308 may also include or be coupled to a power management circuit to provide power to the components of the network node 1300 for performing the functions described herein. For example, the network node 1300 may be connected to an external power source (e.g., a power grid, a power outlet) via an input circuit or interface (e.g., a cable), whereby the external power source provides power to the power circuit of the power supply 1308. As yet another example, the power supply 1308 may include a power source in the form of a battery or battery pack connected to or integrated into the power circuit. If the external power source fails, the battery may provide backup power.

[0224] An embodiment of the network node 1300 may include Fig.13Additional components beyond those shown that are used to provide certain aspects of the functionality of the network node, including any functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 1300 may include a user interface device to allow information to be input into the network node 1300 and to allow information to be output from the network node 1300. This may allow a user to perform diagnostics, maintenance, repair, and other management functions for the network node 1300.

[0225] Fig.14 is a block diagram of a host 1400 according to various aspects described herein, and the host 1400 may be Fig.11 1400. As used herein, host 1400 may be or include various combinations of hardware and / or software, including processing resources in a standalone server, blade server, cloud-implemented server, distributed server, virtual machine, container, or server farm. Host 1400 may provide one or more services to one or more UEs.

[0226] Host 1400 includes processing circuitry 1402, which is operatively coupled to input / output interface 1406, network interface 1408, power supply 1410, and memory 1412 via bus 1404. Other components may be included in other embodiments. The features of these components may be substantially similar to those described with respect to previous figures (e.g., Fig.12 and 13 ) so that its description is generally applicable to corresponding components of the host 1400.

[0227] The memory 1412 may include one or more computer programs, including one or more host applications 1414 and data 1416, which may include user data, such as data generated by the UE for the host 1400 or data generated by the host 1400 for the UE. An embodiment of the host 1400 may use only a subset or all of the components shown. The host application 1414 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding of multiple different classes, types or implementations of UEs (e.g., mobile phones, desktop computers, wearable display systems, head-up display systems). The host application 1414 may also provide user authentication and authorization checks, and may periodically report health status, routing, and content availability to a central node (e.g., a device in a core network or on the edge). Thus, the host 1400 can select and / or indicate to the UE a different host for the over-the-top service. The host application 1414 can support various protocols, such as HTTP Live Streaming (HLS) protocol, Real-time Messaging Protocol (RTMP), Real-time Streaming Protocol (RTSP), HTTP Dynamic Adaptive Streaming (MPEG-DASH), etc.

[0228] Fig.15 1500 is a block diagram showing a virtualized environment 1500 in which functions implemented by some embodiments can be virtualized. In the current context, virtualization means creating a virtual version of a device or equipment, which may include a virtualized hardware platform, storage device, and networking resources. As used herein, virtualization may be applied to any device or component thereof described herein, and relates to an implementation in which at least a portion of the functions are implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components performed by one or more virtual machines (VMs), which are implemented in one or more virtual environments 1500 hosted by one or more hardware nodes (e.g., hardware computing devices operating as network nodes, UEs, core network nodes, or hosts). In addition, in embodiments in which a virtual node does not require a radio connection (e.g., a core network node or host), the node may be fully virtualized.

[0229] Application 1502 (which may alternatively be referred to as a software instance, a virtual appliance, a network function, a virtual node, a virtual network function, etc.) runs in a virtualized environment 1500 to implement certain features, functions and / or benefits of some embodiments disclosed herein.

[0230] The hardware 1504 includes processing circuitry, memory storing software and / or instructions executable by the hardware processing circuitry, and / or other hardware devices as described herein, such as network interfaces, input / output interfaces, etc. The software may be executed by the processing circuitry to instantiate one or more virtualization layers 1506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide virtual machines 1508a and 1508b (one or more of which may be generally referred to as virtual machines 1508), and / or perform any of the functions, features, and / or benefits described for some embodiments described herein. The virtualization layer 1506 may present a virtual operating platform that appears to be networked hardware to the virtual machines 1508.

[0231] The virtual machine 1508 includes virtual processing, virtual memory, virtual network or interface, and virtual storage, and can be run by a corresponding virtualization layer 1506. Different embodiments of instances of virtual devices 1502 can be implemented on one or more virtual machines 1508 and can be implemented in different ways. In some contexts, virtualization of hardware is referred to as network function virtualization (NFV). NFV can be used to integrate many network device types onto industry-standard high-volume server hardware, physical switches, and physical storage that can be located in data centers and customer premises equipment.

[0232] In the context of NFV, a virtual machine 1508 may be a software implementation of a physical machine that runs a program as if the program were executed on a physical, non-virtualized machine. Each virtual machine 1508 and the portion of the hardware 1504 that executes the virtual machine (hardware dedicated to the virtual machine and / or hardware shared by the virtual machine with other virtual machines) form a separate virtual network element. Still in the context of NFV, a virtual network function is responsible for handling a specific network function running in one or more virtual machines 1508 on the hardware 1504 and corresponds to an application 1502.

[0233] Hardware 1504 can be implemented in a stand-alone network node with general or specific components. Hardware 1504 can implement some functions via virtualization. Alternatively, hardware 1504 can be part of a larger hardware cluster (e.g., such as in a data center or CPE), where many hardware nodes work together and are managed via management and orchestration 1510, which, among other items, oversees the life cycle management of application 1502. In some embodiments, hardware 1504 is coupled to one or more radio units, each of which includes one or more transmitters and one or more receivers that can be coupled to one or more antennas. The radio unit can communicate directly with other hardware nodes via one or more appropriate network interfaces, and can be used in combination with virtual components to provide a virtual node with radio capabilities, such as a radio access node or base station. In some embodiments, a control system 1512 can be used to provide some signaling, which can be used alternatively for communication between hardware nodes and radio units.

[0234] Fig.16 A communication diagram is shown in which a host 1602 communicates with a UE 1606 via a network node 1604 over a partially wireless connection according to some embodiments. Fig.16 Describe the UE discussed in the previous paragraph (such as Fig.11 UE 1112a and / or Fig.12 UE 1200), network nodes (such as Fig.11 The network node 1110a and / or Fig.13 ), and a host (e.g. Fig.11 Host 1116 and / or Fig.14 Host 1400) according to various embodiments of the example implementation.

[0235] Similar to the host 1400, an embodiment of the host 1602 includes hardware, such as a communication interface, a processing circuit, and a memory. The host 1602 also includes software that is stored in the host 1602 or accessible by the host 1602 and can be executed by the processing circuit. The software includes a host application that can operate to provide services to a remote user (e.g., a UE 1606 connected via an over-the-top (OTT) connection 1650 extending between the UE 1606 and the host 1602). When providing services to the remote user, the host application can provide user data sent using the OTT connection 1650.

[0236] The network node 1604 includes hardware that enables it to communicate with the host 1602 and the UE 1606. The connection 1660 can be direct or through a core network (such as Fig.11The core network 1106 of the present invention) and / or one or more other intermediate networks, such as one or more public, private or managed networks. For example, the intermediate network can be a backbone network or the Internet.

[0237] UE 1606 includes hardware and software, which is stored in UE 1606 or accessible by UE 1606 and can be executed by the processing circuit of UE. The software includes a client application, such as a web browser or an operator-specific "application", which is operable to provide services to human or non-human users via UE 1606 with the support of host 1602. In host 1602, the executing host application can communicate with the executing client application via an OTT connection 1650 terminated at UE 1606 and host 1602. When providing services to the user, the client application of the UE can receive request data from the host application of the host and provide user data in response to the request data. OTT connection 1650 can transmit both request data and user data. The client application of the UE can interact with the user to generate user data that it provides to the host application through OTT connection 1650.

[0238] The OTT connection 1650 may extend via a connection 1660 between the host 1602 and the network node 1604 and via a wireless connection 1670 between the network node 1604 and the UE 1606 to provide connectivity between the host 1602 and the UE 1606. The connection 1660 and the wireless connection 1670 through which the OTT connection 1650 may be provided have been drawn abstractly to illustrate communications between the host 1602 and the UE 1606 via the network node 1604 without explicit reference to any intermediate devices and the precise routing of messages via those devices.

[0239] As an example of sending data via the OTT connection 1650, in step 1608, the host 1602 provides user data, which can be performed by executing a host application. In some embodiments, the user data is associated with a specific human user who interacts with the UE 1606. In other embodiments, the user data is associated with the UE 1606, and the UE 1606 shares data with the host 1602 without explicit human interaction. In step 1610, the host 1602 initiates a transmission carrying the user data toward the UE 1606. The host 1602 may initiate the transmission in response to a request sent by the UE 1606. The request may be caused by human interaction with the UE 1606 or by the operation of a client application executed on the UE 1606. According to the teachings of the embodiments described throughout the present disclosure, the transmission may be through the network node 1604. Therefore, in step 1612, according to the teachings of the embodiments described throughout the present disclosure, the network node 1604 sends the user data carried in the transmission initiated by the host 1602 to the UE 1606. In step 1614 , UE 1606 receives user data carried in the transmission, which may be performed by a client application executing on UE 1606 that is associated with a host application executed by host 1602 .

[0240] In some examples, UE 1606 executes a client application that provides user data to host 1602. The user data may be provided in response to data received from host 1602. Thus, in step 1616, UE 1606 may provide the user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via the input / output interface of UE 1606. Regardless of the specific manner in which the user data is provided, UE 1606 initiates transmission of the user data toward host 1602 via network node 1604 in step 1618. In step 1620, in accordance with the teachings of the embodiments described throughout the present disclosure, network node 1604 receives user data from UE 1606 and initiates transmission of the received user data toward host 1602. In step 1622, host 1602 receives the user data carried in the transmission initiated by UE 1606.

[0241] One or more of the various embodiments improves the performance of OTT services provided to UE 1606 using OTT connection 1650 (with wireless connection 1670 forming the final segment).

[0242] In an example scenario, host 1602 may collect and analyze plant status information. As another example, host 1602 may process audio and video data that may have been obtained from a UE for use in creating a map. As another example, host 1602 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, host 1602 may store surveillance videos uploaded by a UE. As another example, host 1602 may store or control access to media content such as video, audio, VR, or AR, and host 1602 may broadcast, multicast, or unicast the media content to a UE. As other examples, host 1602 may be used for energy pricing, remote control of non-time-critical power loads to balance power generation demand, positioning services, presentation services (e.g., compiling a map based on data collected from a remote device, etc.), or any other function for collecting, obtaining, storing, analyzing, and / or sending data.

[0243] In some examples, a measurement process may be provided for the purpose of monitoring data rates, delays, and other factors on which one or more embodiments are improved. In response to changes in the measurement results, there may also be an optional network function for reconfiguring the OTT connection 1650 between the host 1602 and the UE 1606. The measurement process and / or network function for reconfiguring the OTT connection may be implemented in software and hardware of the host 1602 and / or the UE 1606. In some embodiments, sensors (not shown) may be deployed in other devices through which the OTT connection 1650 passes or associated with such other devices; the sensors may participate in the measurement process by providing the values ​​of the monitored quantities of the above examples or providing the values ​​of other physical quantities from which the software can calculate or estimate the monitored quantities. The reconfiguration of the OTT connection 1650 may include message formats, retransmission settings, preferred routes, etc.; the reconfiguration does not require direct changes to the operation of the network node 1604. Such processes and functions may be known and practiced in the art. In some embodiments, the measurement may involve proprietary UE signaling, which facilitates the host 1602 to measure throughput, propagation time, delay, etc. Measurement can be achieved because the software causes the OTT connection 1650 to be used to send messages, particularly empty or "dummy" messages, during which it monitors propagation time, errors, etc.

[0244] Although the computing devices (e.g., UE, network node, host) described herein may include a combination of the hardware components shown, other embodiments may include computing devices with different combinations of components. It will be understood that these computing devices may include any suitable combination of hardware and / or software required to perform the tasks, features, functions and methods disclosed herein. The determination, calculation, acquisition or similar operations described herein may be performed by a processing circuit, which may process information in the following manner: converting the obtained information into other information, comparing the obtained information or the converted information with the information stored in the network node, and / or performing one or more operations based on the obtained information or the converted information, and making a determination as a result of the processing. In addition, although the components are depicted as a single box located within a larger box or nested within multiple boxes, in fact, the computing device may include multiple different physical components constituting a single shown component, and the functions may be divided between separate components. For example, a communication interface may be configured to include any component described herein, and / or the functions of the components may be divided between the processing circuit and the communication interface. In another example, the non-computationally intensive functions of any such component may be implemented in software or firmware, while the computationally intensive functions may be implemented in hardware.

[0245] In certain embodiments, some or all of the functionality described herein may be provided by a processing circuit executing instructions stored on a memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by a processing circuit without the need to execute instructions stored on a separate or separate device-readable storage medium, such as in a hardwired manner. In any of these specific embodiments, the processing circuit may be configured to perform the described functionality, regardless of whether instructions stored on a non-transitory computer-readable storage medium are executed. The benefits provided by such functionality are not limited to processing circuits or other components of a computing device, but are enjoyed by the computing device as a whole and / or generally by end users and wireless networks.

[0246] Embodiments of the techniques and devices described herein include, but are not limited to, the following examples:

[0247] Group A Embodiment

[0248] A1. A method performed by a communication device configured for use in a non-terrestrial network NTN, the method comprising:

[0249] making a decision as to whether to update a geolocation fix for the communication device even if the geolocation fix is ​​valid prior to accessing the NTN, wherein the decision is made based on a remaining duration for which the geolocation fix will be valid; and

[0250] Based on the decision, the geolocation fixes are updated or avoided before accessing the NTN.

[0251] A2. The method of embodiment A1, wherein the determining comprises:

[0252] If the remaining duration is less than the threshold duration, a decision is made to update the geolocation fix before accessing the NTN; and

[0253] If the remaining duration is greater than the threshold duration, a decision is made to avoid updating the geolocation fix before accessing the NTN.

[0254] A3. The method of embodiment A2, further comprising: receiving a threshold duration from the NTN.

[0255] A4. The method of embodiment A3, wherein receiving the threshold duration comprises: receiving the threshold duration in system information of the NTN.

[0256] A5. A method according to any one of embodiments A3-A4, wherein the reception of the threshold duration covers a preconfigured threshold duration preconfigured at the communication device.

[0257] A6. The method of embodiment A2, wherein the communication device is preconfigured with a threshold duration.

[0258] A7. The method of any one of embodiments A2-A6, wherein the threshold duration is specific to the purpose for which the communication device is accessing the NTN or the process that the communication device is using to access the NTN.

[0259] A8. The method of any one of embodiments A2-A7, wherein the threshold duration is specific to the type of satellite providing the NTN cell that the communication device is accessing.

[0260] A9. A method according to any one of embodiments A2-A8, wherein the threshold duration is specific to the orbital altitude of the satellite providing the NTN cell that the communication device is accessing.

[0261] A10. The method of any one of embodiments A2-A9, wherein the threshold duration is specific to a type, category, or class of communications device.

[0262] A11. The method of any one of embodiments A1-A10, further comprising determining whether to make a decision based on a remaining duration that the geolocation fix will be valid.

[0263] A12. The method of embodiment A11, wherein the determination is performed based on whether the communications device receives signaling indicating that the communications device is to make a decision based on a remaining duration that the geolocation fix will be valid.

[0264] A13. A method according to embodiment A12, wherein the signaling includes a threshold duration.

[0265] A14. The method of embodiment A12, wherein the signaling includes a flag indicating whether the communication device is to make a decision based on a remaining duration that the geolocation fix will be valid.

[0266] A15. The method of any one of embodiments A11-A14, wherein the determining comprises: determining not to make a decision based on a remaining duration that the geolocation fix will be valid if:

[0267] The communication device is configured with a power saving mode;

[0268] The communications device is configured to perform at least a threshold number of transmission repetitions;

[0269] The communications device belongs to one or more specific coverage classes; or

[0270] A communications device belongs to one or more specific coverage enhancement modes, classes or classes.

[0271] A16. The method of any one of embodiments A11-A15, wherein the determination is performed based on a purpose for which the communication device is accessing the NTN or a process that the communication device is using to access the NTN.

[0272] A17. The method of any one of embodiments A11-A16, wherein the determining comprises determining that if the communication device is performing an initial access to the NTN, then making the decision based on a remaining duration that the geolocation fix will be valid.

[0273] A18. The method of any one of embodiments A11-A16, wherein the determining comprises determining that the decision is not made based on the remaining duration that the geolocation fix will be valid if any of the following occurs:

[0274] Access to the NTN is triggered by a downlink control channel command from the NTN; or

[0275] Until the geolocation fix becomes invalid, coverage from the serving satellite will be lost.

[0276] A19. The method of any one of embodiments A2-A10 further comprises determining a threshold duration based on an estimated duration that the communication device will maintain access to the NTN.

[0277] A20. The method of any one of embodiments A2-A10, further comprising determining a threshold duration based on an estimated duration of a connection that the communication device will establish, reestablish, or restore as part of accessing the NTN.

[0278] A21. The method of any one of embodiments A1-A20, wherein accessing the NTN comprises: performing random access to the NTN and / or establishing, reestablishing, or restoring a connection with the NTN.

[0279] A22. The method of any one of embodiments A1-A21, wherein accessing the NTN comprises performing an early data transmission (EDT) or a preconfigured uplink resource (PUR) transmission.

[0280] A23. A method according to any one of embodiments A1-A22, wherein accessing the NTN includes: performing random access to a cell of the NTN and / or establishing, reestablishing or restoring a connection with a cell of the NTN.

[0281] A24. A method according to any one of embodiments A1-A23, wherein accessing the NTN includes: transitioning to a radio resource control (RRC) connected state.

[0282] A25. A method according to any one of embodiments A1-A24, wherein the geolocation correction includes a global navigation satellite system (GNSS) positioning correction.

[0283] A26. A method as described in any of embodiments A1-A25, wherein the geolocation correction is valid while a validity timer is running, and wherein the remaining duration for which the geolocation correction will be valid is the remaining duration of the validity timer.

[0284] A27. A method according to any one of embodiments A1-A26, wherein the validity timer is started or restarted when the communication device obtains or updates the geolocation correction.

[0285] A28. A method according to any one of embodiments A1-A27, wherein the communication device is configured to transition to an RRC idle state when a validity timer expires.

[0286] A29. A method according to any one of embodiments A1-A28, wherein the communication device is configured to transition to an RRC idle state when the geolocation correction becomes invalid.

[0287] A30. The method of any one of embodiments A1-A29, further comprising:

[0288] determining a pre-compensated timing advance based on the geolocation correction, whether updated depending on the determination; and

[0289] A random access channel transmission is performed using the determined pre-compensated timing advance as part of accessing the NTN.

[0290] AA. The method according to any one of the preceding embodiments, further comprising:

[0291] Provide user data; and

[0292] The user data is forwarded to the host computer via transmission to the base station.

[0293] Group B Example

[0294] B1. A method performed by a network node configured for use in a non-terrestrial network NTN, the method comprising:

[0295] Signaling is sent to the communication device that controls a decision of the communication device as to whether to update the geolocation fix of the communication device even if the geolocation fix was valid prior to accessing the NTN.

[0296] B2. The method of embodiment B1, wherein the signaling indicates a threshold duration after accessing the NTN that the geolocation fix must remain valid in order for the communication device to access the NTN without updating the geolocation fix.

[0297] B3. The method of embodiment B2, wherein the indicated threshold duration is to override a preconfigured threshold duration preconfigured at the communication device.

[0298] B4. The method of any one of embodiments B2-B3, wherein the indicated threshold duration is specific to the purpose for which the communication device is accessing the NTN or the process that the communication device is using to access the NTN.

[0299] B5. The method of any one of embodiments B2-B4, wherein the indicated threshold duration is specific to the type of satellite providing the NTN cell that the communication device is accessing.

[0300] B6. A method according to any one of embodiments B2-B5, wherein the indicated threshold duration is specific to the orbital altitude of the satellite providing the NTN cell that the communication device is accessing.

[0301] B8. A method as described in any of embodiments B2-B7, wherein the indicated threshold duration is specific to a type, category, or class of communication device.

[0302] B9. A method according to any one of embodiments B1-B8, wherein the signaling indicates whether the communication device is to make a decision on whether to update the geolocation correction when the geolocation correction is valid.

[0303] B10. The method of any one of embodiments B1-B9, wherein the signaling includes a flag indicating whether the communication device is to make a decision based on a remaining duration that the geolocation fix will be valid.

[0304] B11. A method according to any one of embodiments B1-B10, wherein the signaling indicates that the communication device is to update the geolocation correction if the communication device is configured with a specific power saving mode, if the communication device is configured to perform at least a threshold number of transmission repetitions, if the communication device belongs to one or more specific coverage classes, or if the communication device belongs to one or more specific coverage enhancement modes, classes or levels, wherein the signaling indicates a specific power saving mode, a threshold number of transmission repetitions, one or more specific coverage classes, or one or more specific coverage enhancement modes.

[0305] B12. The method of any one of embodiments B1-B11, wherein the signaling indicates that the communication device is to update the geolocation fix if the communication device is accessing the NTN for a specific purpose or using a specific procedure.

[0306] B13. The method of any one of embodiments B1-B12, wherein the signaling indicates that the communication device is to update geolocation fixes if the communication device is performing initial access to the NTN.

[0307] B14. The method of any one of embodiments B1-B13, wherein the signaling instructs the communication device not to update the geolocation correction when:

[0308] Access to the NTN is triggered by a downlink control channel command from the NTN; or

[0309] Until the geolocation fix becomes invalid, coverage from the serving satellite will be lost.

[0310] B15. The method according to any one of embodiments B1-B14, wherein accessing the NTN includes: performing random access to the NTN and / or establishing, re-establishing or restoring a connection with the NTN.

[0311] B16. The method according to any one of embodiments B1-B15, wherein accessing the NTN comprises: performing early data transmission (EDT) or preconfigured uplink resource (PUR) transmission.

[0312] B17. A method according to any one of embodiments B1-B16, wherein accessing the NTN includes: performing random access to a cell of the NTN and / or establishing, reestablishing or restoring a connection with a cell of the NTN.

[0313] B18. A method according to any one of embodiments B1-B17, wherein accessing the NTN includes: transitioning to a radio resource control (RRC) connected state.

[0314] B19. A method according to any one of embodiments B1-B18, wherein the geolocation correction includes a global navigation satellite system (GNSS) positioning correction.

[0315] B20. A method according to any one of embodiments B1-B19, wherein the geolocation correction is valid while the validity timer is running.

[0316] B21. A method according to any one of embodiments B1-B20, wherein the signaling controls whether or how the communication device makes a decision based on the remaining duration that the geolocation correction will be valid.

[0317] B22. A method according to embodiment B21, wherein the geolocation fix is ​​valid while a validity timer is running, and wherein the remaining duration for which the geolocation fix will be valid is the remaining duration of the validity timer.

[0318] B23. A method according to any one of embodiments B20-B22, wherein the validity timer is started or restarted when the communication device obtains or updates the geolocation correction.

[0319] B24. A method according to any one of embodiments B20-B23, wherein the communication device is configured to transition to an RRC idle state when a validity timer expires.

[0320] B25. A method according to any one of embodiments B1-B24, wherein the communication device is configured to transition to an RRC idle state when the geolocation correction becomes invalid.

[0321] BB. The method according to any of the preceding embodiments, further comprising:

[0322] obtain user data; and

[0323] Forwards user data to a host computer or wireless communication device.

[0324] Group C Example

[0325] C1. A communication device configured to perform any step of any embodiment in Group A.

[0326] C2. A communication device comprising a processing circuit configured to perform any step of any embodiment of group A.

[0327] C3. A communication device comprising:

[0328] communications circuits; and

[0329] A processing circuit configured to perform any step of any embodiment in Group A of embodiments.

[0330] C4. A communication device comprising:

[0331] A processing circuit configured to perform any step of any embodiment of Group A; and

[0332] A power circuit is configured to supply power to the communication device.

[0333] C5. A communication device comprising:

[0334] A processing circuit and a memory, the memory containing instructions executable by the processing circuit, whereby the communication device is configured to perform any step of any embodiment in Group A of embodiments.

[0335] C6. A user equipment (UE), comprising:

[0336] an antenna configured to transmit and receive wireless signals;

[0337] a radio front end circuit connected to the antenna and the processing circuit and configured to condition signals transmitted between the antenna and the processing circuit;

[0338] A processing circuit configured to perform any step of any embodiment of Group A;

[0339] an input interface connected to the processing circuitry and configured to allow information to be input into the UE for processing by the processing circuitry;

[0340] an output interface connected to the processing circuit and configured to output information from the UE that has been processed by the processing circuit; and

[0341] A battery is connected to the processing circuit and configured to supply power to the UE.

[0342] C7. A computer program comprising instructions which, when executed by at least one processor of a communication device, cause the communication device to perform any step of any embodiment of Group A.

[0343] C8. A carrier containing the computer program described in embodiment C7, wherein the carrier is one of an electronic signal, an optical signal, a radio signal or a computer-readable storage medium.

[0344] C9. A network node configured to execute any step of any embodiment in Group B.

[0345] C10. A network node comprising a processing circuit, wherein the processing circuit is configured to perform any step of any embodiment in Group B.

[0346] C11. A network node, comprising:

[0347] communications circuits; and

[0348] A processing circuit configured to perform any step of any embodiment in Group B of embodiments.

[0349] C12. A network node, comprising:

[0350] A processing circuit configured to perform any step of any embodiment of Group B;

[0351] A power supply circuit is configured to supply power to the network node.

[0352] C13. A network node, comprising:

[0353] A processing circuit and a memory, the memory comprising instructions executable by the processing circuit, whereby the network node is configured to perform any step of any embodiment in Group B embodiments.

[0354] C14. A network node according to any one of embodiments C9-C13, wherein the network node is a base station.

[0355] C15. A computer program comprising instructions, which when executed by at least one processor of a network node causes the network node to perform any step of any embodiment of Group B.

[0356] C16. The computer program of embodiment C14, wherein the network node is a base station.

[0357] C17. A carrier comprising the computer program described in any one of embodiments C15-C16, wherein the carrier is one of an electronic signal, an optical signal, a radio signal or a computer-readable storage medium.

[0358] Group D Examples

[0359] D1. A communication system comprising a host computer, the host computer comprising:

[0360] processing circuitry configured to provide user data; and

[0361] a communication interface configured to forward user data to a cellular network for transmission to a user equipment (UE),

[0362] The cellular network comprises a base station having a radio interface and a processing circuit, and the processing circuit of the base station is configured to perform any step of any embodiment in Group B.

[0363] D2. According to the communication system described in the previous embodiment, it also includes: a base station.

[0364] D3. The communication system according to the first two embodiments further includes: a UE, wherein the UE is configured to communicate with the base station.

[0365] D4. A communication system according to the first three embodiments, wherein:

[0366] The processing circuitry of the host computer is configured to execute a host application to provide user data; and

[0367] The UE includes processing circuitry configured to execute a client application associated with a host application.

[0368] D5. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:

[0369] At the host computer, providing user data;

[0370] At a host computer, a transmission is initiated to carry user data to a UE via a cellular network including a base station, wherein the base station performs any step of any embodiment in Group B.

[0371] D6. The method according to the previous embodiment also includes: sending user data at the base station.

[0372] D7. A method according to the first two embodiments, wherein the user data is provided at the host computer by executing a host application, the method further comprising: executing a client application associated with the host application at the UE.

[0373] D8. A user equipment (UE) configured to communicate with a base station, the UE comprising a radio interface and a processing circuit, the processing circuit being configured to perform any step of any of the first three embodiments.

[0374] D9. A communication system comprising a host computer, the host computer comprising:

[0375] processing circuitry configured to provide user data; and

[0376] a communication interface configured to forward user data to a cellular network for transmission to a user equipment (UE),

[0377] The UE includes a radio interface and a processing circuit, and the components of the UE are configured to perform any step of any embodiment in Group A.

[0378] D10. The communication system according to the previous embodiment, wherein the cellular network further includes a base station configured to communicate with the UE.

[0379] D11. A communication system according to the first two embodiments, wherein:

[0380] The processing circuitry of the host computer is configured to execute a host application to provide user data; and

[0381] The processing circuitry of the UE is configured to execute a client application associated with a host application.

[0382] D12. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:

[0383] At the host computer, providing user data; and

[0384] At a host computer, a transmission is initiated to carry user data to a UE via a cellular network including a base station, wherein the UE performs any step of any embodiment in Group A.

[0385] D13. The method according to the aforementioned embodiment further includes: at the UE, receiving user data from the base station.

[0386] D14. A communication system comprising a host computer, the host computer comprising:

[0387] a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station,

[0388] The UE includes a radio interface and a processing circuit, and the processing circuit of the UE is configured to perform any step of any embodiment in Group A of embodiments.

[0389] D15. According to the communication system described in the previous embodiment, it also includes: UE.

[0390] D16. The communication system according to the first two embodiments further includes: a base station, wherein the base station includes a radio interface and a communication interface, the radio interface is configured to communicate with the UE, and the communication interface is configured to forward user data carried by the transmission from the UE to the base station to the host computer.

[0391] D17. A communication system according to the first three embodiments, wherein:

[0392] The processing circuitry of the host computer is configured to execute a host application; and

[0393] The processing circuitry of the UE is configured to execute a client application associated with the host application to provide user data.

[0394] D18. A communication system according to the above four embodiments, wherein:

[0395] The processing circuitry of the host computer is configured to execute the host application to provide the requested data; and

[0396] The processing circuitry of the UE is configured to execute a client application associated with the host application to provide user data in response to the request data.

[0397] D19. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:

[0398] At a host computer, user data sent from a UE to a base station is received, wherein the UE performs any step of any embodiment in Group A of embodiments.

[0399] D20. The method according to the previous embodiment further includes: at the UE, providing user data to the base station.

[0400] D21. The method according to the first two embodiments further includes:

[0401] At the UE, executing a client application, thereby providing user data to be sent; and

[0402] At the host computer, a host application associated with the client application is executed.

[0403] D22. The method according to the first three embodiments further includes:

[0404] At the UE, executing a client application; and

[0405] receiving, at the UE, input data to the client application, the input data being provided at a host computer by executing a host application associated with the client application,

[0406] The user data to be sent is provided by the client application in response to the input data.

[0407] D23. A communication system comprising a host computer, the host computer comprising a communication interface, which is configured to receive user data originating from a transmission from a user equipment (UE) to a base station, wherein the base station comprises a radio interface and a processing circuit, and the processing circuit of the base station is configured to perform any step of any embodiment of Group B.

[0408] D24. According to the communication system described in the previous embodiment, it also includes: a base station.

[0409] D25. The communication system according to the first two embodiments further includes: UE, wherein the UE is configured to communicate with the base station.

[0410] D26. A communication system according to the first three embodiments, wherein:

[0411] The processing circuitry of the host computer is configured to execute a host application;

[0412] The UE is configured to execute a client application associated with a host application, thereby providing user data to be received by a host computer.

[0413] D27. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:

[0414] At a host computer, user data originating from a transmission received by the base station from a UE is received from a base station, wherein the UE performs any step of any one of the embodiments in Group A.

[0415] D28. The method according to the previous embodiment also includes: receiving user data from the UE at the base station.

[0416] D29. The method according to the first two embodiments further includes: initiating transmission of the received user data to a host computer at the base station.

[0417] References

[0418] 1. TR 38.811, New Radio (NR) studies to support non-terrestrial networks

[0419] 2. TR 38.821, NR solutions for supporting non-terrestrial networks, 3GPP, 16.1.0, June 2021.

[0420] 3. RP-193234, NR Solutions for Non-Terrestrial Networks (NTN), 3GPP RAN#86

[0421] 4. RP-193235, Study on NB-IoT / eMTC Support in Non-terrestrial Networks, 3GPP RAN#86

[0422] 5. RP-202689, Study on NB-IoT / eMTC Support in Non-Terrestrial Networks, RAN#90, December 2020.

[0423] 6. RP-211601, NB-IoT / eMTC Support for Non-Terrestrial Networks (NTN), RAN#92-e, June 2021.

[0424] 7.TR 36.763, Study on Narrowband Internet of Things (NB-IoT) / Enhanced Machine Type Communications (eMTC) Support for Non-Terrestrial Networks (NTN), 3GPP, 17.0.0, June 2021.

Claims

1. A method performed by a communication device (18) configured for use in a non-terrestrial network (NTN) (10), the method comprising: making (700) a decision as to whether to update a geolocation fix (20) of the communication device (18) prior to accessing the NTN (10) even if the geolocation fix (20) is valid, wherein the decision is made based on a remaining duration (26) for which the geolocation fix (20) will be valid; and Based on the decision, the geolocation correction (20) is updated or refrained from being updated (710) before accessing the NTN (10).

2. The method according to claim 1, wherein: Said making includes: If the remaining duration (26) is less than a threshold duration, a decision is made to update the geolocation fix (20) before accessing the NTN (10); and If the remaining duration (26) is greater than the threshold duration, a decision is made to avoid updating the geolocation fix (20) prior to accessing the NTN (10).

3. The method according to claim 2, further comprising: The threshold duration is received from the NTN (10).

4. The method according to any one of claims 2 to 3, wherein: The threshold durations are specific to: The communication device (18) is currently accessing the NTN (10) or the communication device (18) is currently in the process of accessing the NTN (10); Providing the type of satellite of the NTN cell that the communication device (18) is accessing; Providing the orbital altitude of the satellite of the NTN cell that the communication device (18) is accessing; and / or The type, category or class of the communication device (18).

5. The method according to any one of claims 1 to 4, further comprising: Receiving signaling (28) indicating that the communication device (18) is to make the decision based on the remaining duration (26) that the geolocation fix (20) will be valid; and determining to make the decision based on the signaling (28).

6. The method according to any one of claims 1 to 4, further comprising: The decision is made based on the remaining duration (26) for which the geolocation fix (20) will be valid, determined based on the purpose for which the communication device (18) is accessing the NTN (10), or the process the communication device (18) is using to access the NTN (10).

7. The method according to any one of claims 1 to 6, further comprising: The threshold duration is determined based on an estimated duration of a connection that the communication device (18) will establish, re-establish or restore as part of accessing the NTN (10).

8. The method according to any one of claims 1 to 7, wherein: Accessing the NTN (10) includes: Performing random access to the NTN (10) and / or establishing, re-establishing or recovering a connection with the NTN (10); Performing random access to a cell of the NTN (10) and / or establishing, re-establishing or restoring a connection with a cell of the NTN (10); Performing early data transmission EDT or preconfigured uplink resource PUR transmission; and / or Transition to the Radio Resource Control (RRC) Connected state.

9. The method according to any one of claims 1 to 8, wherein: The geolocation fix (20) is valid while a validity timer is running, wherein the remaining duration (26) for which the geolocation fix (20) will be valid is the remaining duration of the validity timer, wherein the validity timer is started or restarted when the communication device (18) obtains or updates the geolocation fix (20).

10. The method according to any one of claims 1 to 9, further comprising: determining a pre-compensated timing advance based on the geolocation correction (20), whether updated or not depending on the determination; as well as A random access channel transmission is performed using the determined pre-compensated timing advance as part of accessing the NTN (10).

11. The method according to any one of claims 1 to 10, wherein: The geolocation fix (20) comprises a Global Navigation Satellite System GNSS location fix.

12. A method performed by a network node (30) configured for use in a non-terrestrial network NTN (10), the method comprising: Signaling (28) is sent (820) to a communication device (18), the signaling (28) controlling a decision of the communication device (18) as to whether to update a geolocation fix (20) of the communication device (18) even if the geolocation fix (20) was valid before accessing the NTN (10).

13. The method according to claim 12, wherein: The signaling (28) indicates a threshold duration after accessing the NTN (10) that the geolocation fix (20) must remain valid in order for the communication device (18) to access the NTN (10) without updating the geolocation fix (20).

14. The method according to claim 13, wherein: The indicated threshold durations are specific to: The communication device (18) is currently accessing the NTN (10) or the communication device (18) is currently in the process of accessing the NTN (10); Providing the type of satellite of the NTN cell that the communication device (18) is accessing; Providing the orbital altitude of the satellite of the NTN cell that the communication device (18) is accessing; and / or The type, category or class of the communication device (18).

15. The method according to any one of claims 12 to 14, wherein: The signaling (28) indicates whether the communication device (18) is to make a decision as to whether to update the geolocation fix (20) while the geolocation fix (20) is valid.

16. The method according to any one of claims 12 to 15, wherein: The signaling (28) indicates that the communication device (18) is to update the geolocation correction (20) if the communication device (18) is configured with a specific power saving mode, if the communication device (18) is configured to perform at least a threshold number of transmission repetitions, if the communication device (18) belongs to one or more specific coverage classes, or if the communication device (18) belongs to one or more specific coverage enhancement modes, classes or levels, wherein the signaling (28) indicates the specific power saving mode, the threshold number of transmission repetitions, the one or more specific coverage classes, or the one or more specific coverage enhancement modes.

17. The method according to any one of claims 12 to 16, wherein: The signaling (28) indicates that the communication device (18) is to update the geolocation fix (20) if the communication device (18) accesses the NTN (10) for a specific purpose or using a specific procedure.

18. The method according to any one of claims 12 to 17, wherein: The signaling (28) instructs the communication device (18) not to update the geolocation fix (20) if: Access to the NTN (10) is triggered by a downlink control channel command from the NTN (10); or Before the geolocation fix (20) becomes invalid, coverage from the serving satellite will be lost.

19. The method according to any one of claims 12 to 18, wherein: Accessing the NTN (10) includes: Performing random access to the NTN (10) and / or establishing, re-establishing or recovering a connection with the NTN (10); Performing random access to a cell of the NTN (10) and / or establishing, re-establishing or restoring a connection with a cell of the NTN (10); Performing early data transmission EDT or preconfigured uplink resource PUR transmission; and / or Transition to the Radio Resource Control (RRC) Connected state.

20. The method according to any one of claims 12 to 19, wherein: The signaling (28) controls whether or how the communication device (18) makes the decision based on a remaining duration (26) for which the geolocation fix (20) will be valid, wherein the geolocation fix (20) is valid while a validity timer is running, wherein the remaining duration (26) for which the geolocation fix (20) will be valid is the remaining duration of the validity timer, and wherein the validity timer is started or restarted when the communication device (18) obtains or updates the geolocation fix (20).

21. The method according to any one of claims 12 to 20, wherein: The geolocation fix (20) comprises a Global Navigation Satellite System GNSS location fix.

22. A communication device (18) configured for use in a non-terrestrial network (NTN) (10), the communication device (18) being configured to: making a decision as to whether to update the geolocation fix (20) of the communication device (18) before accessing the NTN (10) even if the geolocation fix (20) is valid, wherein: The determination is made based on a remaining duration (26) for which the geolocation fix (20) will be valid; as well as Based on the decision, updating the geolocation fix (20) is or is avoided before accessing the NTN (10).

23. The communication device (18) according to claim 22, configured to perform the method of any one of claims 2-11.

24. A network node (30) configured for use in a non-terrestrial network NTN (10), the network node (30) being configured to: Signaling (28) is sent to a communication device (18), the signaling (28) controlling a decision of the communication device (18) as to whether to update a geolocation fix (20) of the communication device (18) even if the geolocation fix (20) was valid before accessing the NTN (10).

25. The network node (30) according to claim 24, configured to perform the method of any one of claims 13-21.

26. A computer program comprising instructions which, when executed by at least one processor of a communication device (18), cause the communication device (18) to perform the method of any one of claims 1-11.

27. A computer program comprising instructions which, when executed by at least one processor of a network node (30), cause the network node (30) to perform the method of any one of claims 12-21.

28. A carrier comprising a computer program according to any one of claims 26 to 27, wherein: The carrier is one of an electronic signal, an optical signal, a radio signal or a computer-readable storage medium.

29. A communication device (18) configured for use in a non-terrestrial network (NTN) (10), the communication device (18) comprising: Communication circuit (920); as well as A processing circuit (910) configured to: making a decision as to whether to update a geolocation fix (20) of the communication device (18) before accessing the NTN (10) even if the geolocation fix (20) is valid, wherein the decision is made based on a remaining duration (26) for which the geolocation fix (20) will be valid; as well as Based on the decision, updating the geolocation fix (20) is or is avoided before accessing the NTN (10).

30. The communication device (18) of claim 29, wherein: The processing circuit (910) is configured to perform the method of any one of claims 2-11.

31. A network node (30) configured for use in a non-terrestrial network NTN (10), the network node (30) comprising: Communication circuit (1020); as well as A processing circuit (1010) is configured to send signaling (28) to a communication device (18), the signaling (28) controlling a decision of the communication device (18) as to whether to update a geolocation fix (20) of the communication device (18) even if the geolocation fix (20) was valid before accessing the NTN (10).

32. The network node (30) according to claim 31, wherein: The processing circuit (910) is configured to perform the method of any one of claims 13-21.