EP4690922A1

EP4690922A1 - Geopositioning measurement gaps

Info

Publication number: EP4690922A1
Application number: EP24716801.6A
Authority: EP
Inventors: Talha KHAN; Johan Rune
Original assignee: Telefonaktiebolaget LM Ericsson AB
Current assignee: Telefonaktiebolaget LM Ericsson AB
Priority date: 2023-04-07
Filing date: 2024-04-05
Publication date: 2026-02-11
Also published as: WO2024209046A1; CN121336449A

Abstract

A communication device (18) is configured for use in a communication network (10). The communication device (18) performs a geopositioning measurement (38) during a geopositioning measurement gap (50) triggered by expiration of a validity duration (40) for which a geopositioning fix (20) or timing advance of the communication device (18) is valid. The communication device (18) obtains a geopositioning fix (20) of the communication device (18) using a result of the geopositioning measurement (38).

Description

GEOPOSITIONING MEASUREMENT GAPS

Technical Field

The present application relates generally to a communication network and relates more particularly to geopositioning measurement gaps in such a network.

Background

A non-terrestrial network (NTN) is a network that uses an airborne or space-borne vehicle to embark a transmission equipment relay node or base station. A satellite, for example, is a space-borne vehicle embarking a bent pipe payload or a regenerative payload telecommunication transmitter, e.g., placed into Low-Earth Orbit (LEO), Medium-Earth Orbit (MEO), or Geostationary Earth Orbit (GEO). Using such an airborne or space-borne vehicle, an NTN can provide communication service over a wider area of Earth than a terrestrial network, e.g., so that service is more independent of location.

An NTN nonetheless has a larger propagation delay than a terrestrial network. For a bent pipe satellite network, the round-trip delay may for example range from tens of milliseconds (ms) in the case of LEO satellites to several hundreds of ms for GEO satellites. As a comparison, the round-trip delays in terrestrial networks are typically below 1 ms.

Because of the long propagation delay in an NTN, a timing advance (TA) that a communication device uses for its uplink transmissions has to be much greater than in terrestrial networks in order for the uplink and downlink to be time aligned. When accessing the NTN, then, the communication device performs a random access (RA) procedure to acquire such timing advance. But even the initial message that the communication device transmits as part of the random access procedure, referred to as a random access preamble, has to be transmitted with a timing advance to allow a reasonable size of the random access preamble reception window. The TA the communication device uses for the RA preamble transmission in an NTN is called a “pre-compensation TA”.

Summary

Embodiments herein include a method performed by a communication device configured for use in a communication network. The method comprises performing a geopositioning measurement during a geopositioning measurement gap triggered by expiration of a validity duration for which a geopositioning fix or timing advance of the communication device is valid. The method also comprises obtaining a geopositioning fix of the communication device using a result of the geopositioning measurement.

In some embodiments, the method further comprises receiving, from the communication network, signaling that configures or activates triggering of a geopositioning measurement gap by expiration of a validity duration for which a geopositioning fix or timing advance of the communication device is valid.

In some embodiments, each time a validity duration for which a geopositioning fix or timing advance of the communication device expires, a geopositioning measurement gap is triggered by expiration of that validity duration.

In some embodiments, the geopositioning measurement gap is a periodic geopositioning measurement gap that recurs periodically each time a validity duration for which a geopositioning fix or timing advance of the communication device expires.

In some embodiments, the geopositioning measurement gap is triggered by expiration of a timing advance validity duration for which a timing advance of the communication device is valid. In some embodiments, the timing advance validity duration expires after a geopositioning fix validity duration for which a geopositioning fix of the communication device is valid expires.

In some embodiments, the method further comprises receiving, from the communication network, a measurement gap configuration that configures the geopositioning measurement gap. In some embodiments, the measurement gap configuration includes a gap start offset time indicating an offset between a time when the measurement gap starts and a time when the validity duration expires.

In some embodiments, the geopositioning measurement gap is triggered to start at a time that is offset from a time when the validity duration expires.

In some embodiments, the geopositioning measurement gap is triggered by expiration of a validity duration for which a geopositioning fix of the communication device is valid.

In some embodiments, the method further comprises receiving, from the communication network, signaling indicating that an initial validity duration for which a geopositioning fix of the communication device is valid is to be extended, and the geopositioning measurement gap is triggered by expiration of the extended validity duration.

In some embodiments, the geopositioning measurement gap is triggered by expiration of a validity duration for which a timing advance of the communication device is valid.

In some embodiments, the method further comprises reporting, to the communication network, the validity duration as defined from a reference time. In some embodiments, the reference time is a reference point of a measurement gap during which a geopositioning measurement was last performed. In some embodiments, the reference point is a start time or an end time of the measurement gap during which a geopositioning measurement was last performed. In other embodiments, the reference point is an offset from a start time or an end time of the measurement gap during which a geopositioning measurement was last performed.

In some embodiments, the method further comprises reporting, to the communication network, an absolute time of expiration of the validity duration. In some embodiments, the communication network is a non-terrestrial network, NTN. In some embodiments, the geopositioning measurement is a Global Navigate Satellite System, GNSS, measurement. In some embodiments, the geopositioning measurement gap is a GNSS measurement gap, and the geopositioning fix is a GNSS positioning fix.

In some embodiments, the geopositioning measurement gap is triggered while the communication device is in resource control, RRC, connected state.

Other embodiments herein include a method performed by a network node in a communication network. The method comprises transmitting, to a communication device, signaling that configures or activates triggering of a geopositioning measurement gap by expiration of a validity duration for which a geopositioning fix or timing advance of the communication device is valid. The method also comprises receiving, from the communication device, a report reporting the validity duration.

In some embodiments, according to the signaling, each time a validity duration for which a geopositioning fix or timing advance of the communication device expires, a geopositioning measurement gap is triggered by expiration of that validity duration.

In some embodiments, the signaling comprises a measurement gap configuration that configures the geopositioning measurement gap. In some embodiments, the measurement gap configuration configures timing of the geopositioning measurement gap as a function of timing of expiration of the validity duration. In some embodiments, the measurement gap configuration includes a gap start offset time indicating an offset between a time when the measurement gap starts and a time when the validity duration expires.

In some embodiments, the signaling indicates that an initial validity duration for which a geopositioning fix of the communication device is valid is to be extended, and the geopositioning measurement gap is triggered by expiration of the extended validity duration.

In some embodiments, the reported validity duration is defined from a reference time. In some embodiments, the reference time is a reference point of a measurement gap during which a geopositioning measurement was last performed. In some embodiments, the reference point is a start time or an end time of the measurement gap during which a geopositioning measurement was last performed. In other embodiments, the reference point is an offset from a start time or an end time of the measurement gap during which a geopositioning measurement was last performed.

In some embodiments, the reported validity duration is an absolute time of expiration of the validity duration.

In some embodiments, the communication network is a non-terrestrial network, NTN. In some embodiments, the geopositioning measurement is a Global Navigate Satellite System, GNSS, measurement. In some embodiments, the geopositioning measurement gap is a GNSS measurement gap, and the geopositioning fix is a GNSS positioning fix.

Other embodiments herein include a communication device configured for use in a communication network. The communication device is configured to perform a geopositioning measurement during a geopositioning measurement gap triggered by expiration of a validity duration for which a geopositioning fix or timing advance of the communication device is valid. The communication device is also configured to obtain a geopositioning fix of the communication device using a result of the geopositioning measurement.

In some embodiments, the communication device is configured to perform the steps described above for a communication device configured for use in a communication network.

Other embodiments herein include a network node configured for use in a communication network. The network node is configured to transmit, to a communication device, signaling that configures or activates triggering of a geopositioning measurement gap by expiration of a validity duration for which a geopositioning fix or timing advance of the communication device is valid. The network node is also configured to receive, from the communication device, a report reporting the validity duration.

In some embodiments, the network node is configured to perform the steps described above for a network node in a communication network.

In some embodiments, a computer program comprising instructions which, when executed by at least one processor of a communication device, causes the communication device to perform the steps described above for a communication device configured for use in a communication network.

In some embodiments, a computer program comprising instructions which, when executed by at least one processor of a network node, causes the network node to perform the steps described above for a network node in a communication network.

In some embodiments, a carrier containing the computer program is one of an electronic signal, optical signal, radio signal, or computer readable storage medium. Brief Description of Drawings

Figure 1 is block diagram of an exemplary non-terrestrial network.

Figure 2 is a block diagram of an example architecture of a satellite network with bent pipe transponders.

Figure 3 illustrates an exemplary satellite orbit including a set of parameters,

Figure 4 is a logic flow diagram of a method performed by a communication device configured for use in a communication network according to some embodiments.

Figure 5 is a logic flow diagram of a method performed by a communication device configured for use in a communication network according to other embodiments.

Figure 6 is a logic flow diagram of a method performed by a communication device configured for use in a communication network according to other embodiments.

Figure 7 is a logic flow diagram of a method performed by a communication device configured for use in a communication network according to other embodiments.

Figure 8 is a logic flow diagram of a method performed by a communication device configured for use in a communication network according to other embodiments.

Figure 9 is a logic flow diagram of a method performed by a network node configured for use in a communication network according to other embodiments.

Figure 10 is a logic flow diagram of a method performed by a network node configured for use in a communication network according to other embodiments.

Figure 11 is a logic flow diagram of a method performed by a network node configured for use in a communication network according to other embodiments.

Figure 12 is a logic flow diagram of a method performed by a network node configured for use in a communication network according to other embodiments.

Figure 13 is a logic flow diagram of a method performed by a network node configured for use in a communication network according to other embodiments.

Figure 14 is a block diagram of a communication device according to some embodiments.

Figure 15 is a block diagram of a network node according to some embodiments.

Figure 16 is a block diagram of a communication system in accordance with some embodiments.

Figure 17 is a block diagram of a UE in accordance with some embodiments.

Figure 18 is a block diagram of a network node in accordance with some embodiments.

Figure 19 is a block diagram of a virtualization environment in accordance with some embodiments. Detailed Description

A communication device can determine a pre-compensation timing advance (TA) from a geopositioning fix of the communication device, e.g., a Global Navigation Satellite System (GNSS) fix. The communication device may for example deduce the pre-compensation TA based on a difference between the communication device’s geopositioning fix and a reference geoposition in a non-terrestrial network (NTN) cell for which the communication device has a reference TA. Regardless, after the communication device acquires a geopositioning fix, the communication device starts a validity timer. During the duration of time that the validity timer is running, the geopositioning fix is valid and the communication device is allowed to access the NTN by establishing, re-establishing, or resuming a connection with the NTN. Once the validity timer expires, the communication device must re-acquire its geopositioning fix.

Problematically, if the validity timer expires while the communication device is connected to the NTN, the communication device must re-acquire its geopositioning fix even though data may still need to be transmitted to or from the communication device. If the communication device uses the same radio frequency (RF) circuitry for both accessing the NTN and performing geopositioning measurements, the communication device requires a gap in time during which the NTN avoids scheduling data transmissions for the communication device, so that the communication device can perform geopositioning measurement(s) during that gap using its shared radio frequency (RF) circuitry. But if the time internals during which the NTN schedules geopositioning measurement gaps for the communication device are not narrowly tailored to the time intervals during which the communication device actually needs to perform geopositioning measurement(s), that time misalignment jeopardizes geopositioning measurement performance and/or NTN system performance, e.g., by reducing data throughput, increasing data latency, and/or otherwise reducing the perceived quality of experience. This threat from time misalignment is exacerbated if the communication device is allowed to autonomously decide the duration during which its geopositioning fix is valid, as that autonomous decision threatens synchronization between the communication device and the communication network on when the geopositioning fix’s validity duration expires.

According to some embodiments herein, a geopositioning measurement gap is triggered by expiration of a validity duration for which a geopositioning fix or timing advance of a communication device is valid. In one embodiment, for example, each time a validity duration for which a geopositioning fix or timing advance of the communication device expires, a geopositioning measurement gap is triggered by expiration of that validity duration. That is, a geopositioning measurement gap is triggered by the validity duration’s expiration, as opposed to being triggered by signaling from a communication network. With a geopositioning measurement gap triggered in this way, some embodiments effectively tie or associate a geopositioning measurement gap with expiration of the validity duration for a geopositioning fix or timing advance, e.g., such that the validity duration’s expiration is an event that triggers a geopositioning measurement gap.

Some embodiments effectively time align a geopositioning measurement gap with expiration of a geopositioning fix or timing advance validity duration, at least within a certain offset from one another. Moreover, some embodiments effectively synchronize the communication device’s understanding of when the geopositioning measurement gap occurs with the communication network’s understanding of when the geopositioning measurement gap occurs, even in embodiments where the communication device autonomously decides the geopositioning fix or timing advance validity duration. Some embodiments for example synchronize the communication device’s understanding of when the geopositioning fix or timing advance validity duration expires with the communication network’s understanding of when the geopositioning fix or timing advance validity duration expires. Because a geopositioning measurement gap is tied or associated with the validity duration’s expiration, this synchronization has the effect of synchronizing the communication device’s understanding of when the geopositioning measurement gap occurs with the communication network’s understanding of when the geopositioning measurement gap occurs.

More particularly, Figure 1 shows a non-terrestrial network (NTN) 10 according to some embodiments. The NTN 10 as shown includes a satellite 12 (e.g., a communications satellite) and an earth-based gateway 14 that connects the satellite 12 to a base station or a core network. The satellite 12, potentially in cooperation with the earth-based gateway 14, provides communication coverage for serving a communication device 18, e.g., via a spot beam or cell 16.

In this context, the communication device 18 is capable of acquiring a geopositioning fix 20 of the communication device 18. The geopositioning fix 20 represents a geographical position of the communication device 18. The communication device 18 may for example perform one or more geopositioning measurements 38 and update its geopositioning fix 20 using result(s) of the geopositioning measurement(s) 38. As shown, for example, the communication device 18 acquires its geopositioning fix 20 via a Global Navigation Satellite System (GNSS) comprising multiple GNSS satellites 22. The communication device 18 in this case performs geopositioning measurement(s) 38 on GNSS signals 36 received from GNSS satellites 22, for deriving the geopositioning fix 20 in the form of a GNSS positioning fix. The communication device 18 in these and other embodiments is capable of acquiring its geopositioning fix 20 separate from access to the NTN 10, i.e. , acquisition of the geopositioning fix 20 is not dependent upon access to the NTN 10.

According to embodiments herein, though, the communication device 18 uses the same radio frequency (RF) circuitry for both accessing the NTN 10 and performing the geopositioning measurements 38. This means that the communication device 18 requires a gap 50 in time during which the NTN 10 avoids scheduling data transmissions for the communication device 18, so that the communication device 18 can perform the geopositioning measurement(s) 38 during that gap 50 using its shared RF circuitry. This gap 50 is accordingly referred to herein as a geopositioning measurement gap 50.

In some embodiments, the communication device 18 is configured to exploit its geopositioning fix 20 for determining a pre-compensation timing advance (TA). The communication device 18 may then perform a random access channel transmission (not shown) using the pre-compensation TA, as part of accessing the NTN 10, e.g., establishing, re-establishing, or resuming a connection with the NTN 10. In these and other embodiments, then, the geopositioning fix 20 is a prerequisite for the communication device 18 to access the NTN 10.

According to embodiments herein, though, the communication device’s geopositioning fix 20 or its timing advance (TA) is valid only for a certain duration, referred to as validity duration 40. The communication device 18 accordingly deems its geopositioning fix 20 or its TA as valid for a certain duration 40 of time after having acquired the geopositioning fix 20 or TA. Here, validity of the geopositioning fix 20 may mean that the geopositioning fix 20 still represents a geographical position of the communication device 18 with at least a certain level of accuracy or performance, i.e., that the geopositioning fix 20 has not yet become stale. Similarly, validity of the TA may mean that the TA still provides uplink timing alignment with at least a certain level of accuracy or performance, i.e., that the TA has not yet become stale. The communication device 18 may for example start a validity timer 24 upon acquiring the geopositioning fix 20 or the TA, where the validity timer 24 may be a geopositioning fix validity timer or a TA validity timer. In this case, while the validity timer 24 is running, the communication device 18 deems the geopositioning fix 20 or TA as valid. When the validity timer 24 expires, though, the communication device 18 deems the geopositioning fix 20 or TA as invalid. This may be the case even if the validity timer 24 expires while the communication device 18 is in a connected state (e.g., a radio resource control, RRC, connected state) with an established connection to the NTN 10. When the geopositioning fix 20 or TA becomes invalid due to expiration of the validity duration 40, the communication device 18 must re-acquire its geopositioning fix 20 or TA in order to access or continue accessing the NTN 10, meaning that the communication device 18 needs another geopositioning measurement gap 50 during which to perform geopositioning measurement(s) 38.

According to some embodiments herein, a geopositioning measurement gap 50 is triggered by expiration of the validity duration 40 for which the geopositioning fix 20 or TA is valid. In fact, in one embodiment, each time a validity duration 40 for which the geopositioning fix 20 or TA expires, a geopositioning measurement gap 50 is triggered by expiration of that validity duration 40. That is, the validity duration’s expiration is itself a trigger 34 that triggers a geopositioning measurement gap 50, e.g., as opposed to signaling from the NTN 10 being what triggers the geopositioning measurement gap 50. The geopositioning measurement gap 50 in some embodiments may be automatically and/or periodically triggered by the validity duration’s expiration, e.g., as specified in advance by a rule or configuration at the communication device 18 and/or NTN 10. In some embodiments, then, a geopositioning measurement gap 50 triggered by expiration of the validity duration 40 differs from a geopositioning measurement gap triggered aperiodically by the NTN 10 via a command or other signaling sent to the communication device 10. Regardless, with a geopositioning measurement gap 50 triggered in this way by expiration of the validity duration 40, some embodiments effectively tie or associate a geopositioning measurement gap 50 with expiration of the validity duration 40 for the geopositioning fix 20 or TA, e.g., such that the validity duration’s expiration is an event that triggers a geopositioning measurement gap 50.

Some embodiments effectively time align a geopositioning measurement gap 50 with expiration of the geopositioning fix or timing advance validity duration 40, at least within a certain offset from one another. As shown in Figure 1 in this regard, expiration of the validity duration 40 at an expiration time TE triggers a geopositioning measurement gap 50 to start, with there being an offset 42 in time between the expiration time TE and the start of the geopositioning measurement gap 50. In one embodiment, the offset 42 is zero, so that the geopositioning measurement gap 50 starts exactly when the validity duration 40 expires. In another embodiment, the offset 42 is greater than zero, so that the geopositioning measurement gap 50 starts some set time after the validity duration 40 expires. In yet another embodiment, the offset 42 is less than zero, so that the geopositioning measurement gap 50 starts some set time before the validity duration 40 expires. The offset 42 may thereby indicate how long before the expiration time T_E or how long after the expiration time TE the geopositioning measurement gap 50 starts. Although Figure 1 shows embodiments where the start of the geopositioning measurement gap 50 is defined relative to the expiration time of the validity duration 50, other embodiments may define a different reference point of the geopositioning measurement gap 50 relative to the expiration time of the validity duration 40, e.g., where the reference point may be the start, end, or middle of the geopositioning measurement gap 50. Generally, then, in these and other embodiments, the communication device 18 and/or NTN 10 may determine when the geopositioning measurement gap 50 occurs, based on when the validity duration 40 expires.

In fact, some embodiments effectively synchronize the communication device’s understanding of when the geopositioning measurement gap 50 occurs with the NTN’s understanding of when the geopositioning measurement gap 50 occurs, even in embodiments where the communication device 18 autonomously decides the length of the validity duration 40. Some embodiments for example synchronize the communication device’s understanding of when the validity duration 40 expires with the NTN’s understanding of when the validity duration 40 expires. Because a geopositioning measurement gap 50 is tied or associated with the validity duration’s expiration, this synchronization has the effect of synchronizing the communication device’s understanding of when the geopositioning measurement gap 50 occurs with the NTN’s understanding of when the geopositioning measurement gap 50 occurs.

In some embodiments, the communication device 18 is preconfigured to understand that expiration of the validity duration 40 triggers a geopositioning measurement gap 50. Triggering of a geopositioning measurement gap 50 each time the validity duration 40 expires may for example be specified by 3GPP standards, with the communication device 18 being preconfigured to operate according to those 3GPP standards. In this case, the 3GPP standards may specify not only that a geopositioning measurement gap 50 is triggered by expiration of the validity duration 40, but also when the geopositioning measurement gap 50 occurs relative to when the validity duration 40 expires, e.g., by specifying an offset 42 between the expiration time of the validity duration 40 and the start of the geopositioning measurement gap 50.

In other embodiments, the NTN 10 transmits signaling 28 (e.g., RRC signaling or MAC signaling) that configures triggering of a geopositioning measurement gap 50 by expiration of the validity duration 40. The signaling 28 may for example configure whether a geopositioning measurement gap 50 it to be triggered by expiration of the validity duration 40, e.g., the signaling 28 may include a Boolean field or an optional field for this purpose. Alternatively or additionally, the signaling 28 may configure when a geopositioning measurement gap 50 triggered by expiration of the validity duration 40 is to occur, as a function of when the validity duration 40 expires. The signaling 28 may for example configures a start time or an end time of the geopositioning measurement gap 50 as a function of when the validity duration 40 expires, e.g., by configuring the offset 42.

In still other embodiments, the signaling 28 from the NTN 10 activates triggering of a geopositioning measurement gap 50 by expiration of the validity duration 40, e.g., in which case the signaling 28 may be MAC signaling or physical layer signaling. In this case, the communication device 18 may receive other signaling (e.g., RRC signaling) that provides a configuration for triggering of a geopositioning measurement gap 50 by expiration of the validity duration 40, but the communication device 18 does not use that configuration until it is activated by signaling 28 (e.g., MAC signaling).

Consider now some embodiments as exemplified in a context where the communication device 18 is a New Radio (NR) Internet of Things (loT) user equipment (UE), the NTN 10 is specified by 3GPP, the geopositioning fix 20 is exemplified as a GNSS positioning fix, the geopositioning measurement gap 50 is exemplified as a GNSS measurement gap, and the validity duration 40 is exemplified as a GNSS validity duration.

In particular, some embodiments herein are applicable to NTNs as specified in 3GPP. In one or more embodiments, a satellite radio access network may include the following components: (i) a satellite that refers to a space-borne platform; (ii) an earth-based gateway that connects the satellite to a base station or a core network, depending on the choice of architecture; (iii) a feeder link that refers to the link between a gateway and a satellite; (iv) an access link that refers to the link between a satellite and a user equipment (UE).

Depending on the orbit altitude, a satellite in some embodiments may be categorized as low earth orbit (LEO), medium earth orbit (MEO), or geostationary earth orbit (GEO) satellite. LEO has typical heights ranging from 250 - 1,500 km, with orbital periods ranging from 90 - 120 minutes. MEO has typical heights ranging from 5,000 - 25,000 km, with orbital periods ranging from 3 - 15 hours. And GEO has a typical height at about 35,786 km, with an orbital period of 24 hours.

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

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

The other architecture has a regenerative payload. The satellite includes on-board processing to demodulate and decode the received signal and regenerate the signal before sending it back to the earth. When applied to general 3GPP architecture and terminology, the regenerative payload architecture means that the gNB is located in the satellite.

Figure 2 shows an example architecture of a satellite network with bent pipe transponders (i.e. , the transparent payload architecture). In this case, the satellite 12 forwards signals between the communication device 18 and network equipment on the ground with only amplification and a shift from uplink frequency to downlink frequency. The network node 30 from Figure 1 is shown as a base station (BS) 30, e.g., in the form of a gNB, that is located on the ground with a gateway 14, and the satellite 12 forwards signals/data between the base station 30 and the device 18 via an access link and a feeder link. The base station 30 may be integrated in the gateway 14 or connected to the gateway 14 via a terrestrial connection (wire, optic fiber, wireless link).

In some embodiments, a communication satellite generates multiple beams over a given area. The footprint of a beam may be in an elliptic shape, which may be considered as a cell, but cells consisting of the coverage footprint of multiple beams are not excluded. The footprint of a beam may also be referred to as a spotbeam. The footprint of a beam may move over the earth’s surface with the satellite movement or may be earth fixed with a beam pointing mechanism used by the satellite to compensate for the satellite’s motion. The size of a spotbeam depends on the system design, which may range from tens of kilometers to a few thousands of kilometers.

Propagation delay is an aspect of satellite communications that is different from the delay expected in a terrestrial mobile system. For a bent pipe satellite network, the round-trip delay may, depending on the orbit height, range from tens of ms in the case of LEO satellites to several hundreds of ms for GEO satellites. As a comparison, the round-trip delays in terrestrial cellular networks are typically below 1 ms.

The distance between the UE and a satellite can vary significantly, depending on the position of the satellite and thus the elevation angle E seen by the UE. Assuming circular orbits, the minimum distance is realized when the satellite is directly above the UE (E = 90°), and the maximum distance when the satellite is at the smallest possible elevation angle. Table 1 shows the distances between satellite and UE for different orbital heights and elevation angles together with the one-way propagation delay and the maximum propagation delay difference (the difference from the propagation delay at E = 90°). Note that this table assumes regenerative payload architecture. For the transparent payload case, the propagation delay between gateway and satellite needs to be considered as well, unless the base station corrects for that.

Table 1 : Propagation delay for different orbital heights and elevation angles.

The propagation delay may also be highly variable due to the high velocity of the LEO and MEO satellites and change in the order of 10 - 100 ps every second, depending on the orbit altitude and satellite velocity.

For Non-Terrestrial Networks using 3GPP technology, in particular 5G/NR, the long propagation delay means that the timing advance (TA) the UE uses for its uplink transmissions has to be much greater than in terrestrial networks in order for the uplink and downlink to be 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 later can adjust based on the reception timing of uplink transmission from the UE). However, even the random access preamble (i.e. , the initial message from the UE in the random access procedure) has to be transmitted with a timing advance to allow a reasonable size of the RA preamble reception window in the gNB (and to ensure that the cyclic shift of the preamble’s Zadoff-Chu sequence cannot be so large that it makes the Zadoff-Chu sequence, and thus the preamble, appear as another Zadoff Chu sequence, and thus preamble, based on the same Zadoff-Chu root sequence). But this TA does not have to be as accurate as the TA the UE subsequently uses for other uplink transmissions. The TA the UE uses for the RA preamble transmission in NTN is called “pre-compensation TA”.

Some embodiments herein for geoposition fix update are applicable for supporting any of multiple alternatives for how to determine the pre-compensation TA. All such alternatives may involve information originating both at the gNB and at the UE. In particular, some embodiments herein for geoposition fix update are applicable for supporting a first pre-compensation TA alternative that broadcasts a “common TA” which is valid at a certain reference point, e.g., a center point in the cell. The UE calculates how its own precompensation TA deviates from the common TA, based on the difference between the UE’s own location and the reference point together with the position of the satellite. Herein, the UE acquires its own position using GNSS measurements and the UE obtains the satellite position using satellite orbital data (including satellite position at a certain time) broadcast by the network.

Some embodiments herein for geoposition fix update are alternatively or additionally applicable for a second pre-compensation TA alternative in which the UE autonomously calculates the propagation delay between the UE and the satellite, based on the UE’s and the satellite’s 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. Herein, the UE acquires its own position using GNSS measurements and the UE obtains the satellite position using satellite orbital data (including satellite position at a certain time) broadcast by the network. The pre-compensation TA is then twice the sum of the propagation delay on the feeder link and the propagation delay between the satellite and the UE.

Some embodiments herein for geoposition fix update are alternatively or additionally applicable for a third pre-compensation TA alternative in which the gNB broadcasts a timestamp (in SIB9), which the UE compares with a reference timestamp acquired from 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-compensation TA is twice as long as this propagation delay. In some embodiments, e.g., consistent with 3GPP TR 38.821 v16.1.0, ephemeris data is provided to the UE, for example to assist with pointing a directional antenna (or an antenna beam) towards the satellite, and to calculate a correct Timing Advance (TA) and Doppler shift. Broadcasting of ephemeris data in the system information is one option.

In some embodiments, a satellite orbit is fully described by a set of parameters, e.g., using 6 parameters. Exactly which set of parameters is chosen can be decided by the user; many different representations are possible. For example, a choice of parameters used often in astronomy is the set (a, E, i, Q, co, t). Here, the semi-major axis a and the eccentricity E describe the shape and size of the orbit ellipse; the inclination i, the right ascension of the ascending node Q, and the argument of periapsis co determine its position in space, and the epoch t determines a reference time (e.g. the time when the satellites moves through periapsis). This set of parameters is illustrated in Figure 3.

As an example of a different parametrization, the two-line element sets (TLEs) use mean motion n and mean anomaly M instead of a and t. A completely different set of parameters is the position and velocity vector (x, y, z, v_x, v_y, v_z) of a satellite. These are sometimes called orbital state vectors. They can be derived from the orbital elements and vice versa, since the information they contain is equivalent. All these formulations (and many others) are possible choices for the format of ephemeris data to be used in NTN.

Additionally, the ephemeris data may be accompanied with information on possible coverage area, or timing information when the satellite is going to serve a certain geographical area on Earth.

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

Different levels of integration of the GNSS chip in a 3GPP cellular modem can be anticipated. A UE may support GNSS, but not make use of this support during RRC Connected mode for achieving timing and frequency correction:

In some embodiments, a UE can estimate and pre-compensate timing and frequency offset with sufficient accuracy for UL transmission.

In some embodiments, simultaneous GNSS and NTN NB-loT/eMTC operation is not assumed. Indeed, 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 make use of the same antenna for receiving the GNSS reference signal, and for receiving and transmitting an LTE or NR signal. A switch determines if the antenna should be connected to the cellular RF frontend or the GNSS RF frontend. The switch provides needed isolation between the cellular transmitter and the GNSS receiver but does also prevent simultaneous GNSS and cellular operation.

Some embodiments herein are applicable under the following conditions, assumptions, and/or configurations, e.g., consistent with the following 3GPP agreements.

In TR 36.763 V17.0.0, the impact of GNSS position fix on the battery life of an loT NTN UE has been documented. In addition, several aspects related to GNSS operation e.g., GNSS measurement gaps were also studied and documented in TR 36.763 V17.0.0.

Upon GNSS acquisition, a UE will autonomously determine its GNSS validity duration from an agreed set of values and report it to the network. Upon expiry of GNSS validity duration during RRC_CONNECTED state, a UE is expected to return to idle mode to refresh its GNSS position, i.e. , GNSS acquisition during connected mode is not supported.

For sporadic short transmission, UE in RRC_CONNECTED should go back to idle mode and re-acquire a GNSS position fix if GNSS becomes outdated.

The UE autonomously determines its GNSS validity duration X and reports information associated with this valid duration to the network via RRC signalling.

• X = {10s, 20s, 30s, 40s, 50s, 60s, 5 min, 10 min, 15 min, 20 min, 25 min, 30 min, 60 min, 90 min, 120 min, infinity}

Instead of following the default Rel-17 procedure where a UE in RRC_CONNECTED mode returns to RRCJDLE mode upon GNSS expiry, an enhanced UE behavior is under discussion where the UE is allowed to reacquire its GNSS position fix during the RRC_CONNECTED state. Moreover, another goal is to reduce the number of GNSS position fixes that a UE may need during RRC_CON NESTED mode in order to reduce UE power consumption.

Closed loop time and frequency correction, with potential enhancements, for loT-NTN is considered to reduce the need for UE to update GNSS position fix in long connection time.

At least for the case when frequency error is within frequency error requirements, some mechanisms and conditions may allow UL transmission after original GNSS validity duration expires without GNSS re-acquisition for some duration.

At least the following options can be considered on GNSS measurement in connected for potential enhancements for improved GNSS operations:

• Option 1: UE re-acquires GNSS position fix during RLF procedure

• Option 2: UE re-acquires GNSS position fix with a new gap

Some embodiments support eNB to at least aperiodically trigger UE to make GNSS measurement.

If eNB aperiodically triggers UE to make GNSS measurement, a MAC CE is used.

For GNSS measurement in RRC connected, if eNB aperiodically triggers connected UE to make GNSS measurement, UE can re-acquire GNSS position fix with a gap. The UE may re-acquire GNSS autonomously (when configured by the network) if UE does not receive eNB trigger to make GNSS measurement.

On when the GNSS measurement gap starts, which is aperiodically triggered by eNB with MAC CE, the start time may be at n+ X, where n is the end of MAC CE receiving subframe/slot. Here X may be a predefined value or configured value. Alternatively, the start time may be based on the current GNSS validity duration, with delay or without delay.

On the length of GNSS measurement gap, which is aperiodically triggered by eNB, the gap duration may be equal to or larger than the latest UE reported GNSS position fix time duration. The gap duration may be configured by eNB, or the gap duration may be equal to the latest reported GNSS position fix time duration.

GNSS assistance information that UE reports to eNB at least consists of:

• GNSS position fix time duration for measurement

• GNSS validity duration

When eNB triggers UE to make GNSS measurements, UE re-acquires GNSS position fix.

UE reports GNSS position fix time duration for measurement at least during the initial access stage.

In connected mode, UE may report GNSS validation duration with MAC CE.

UE reports only one GNSS position fix time duration for GNSS measurement at least when moving to RRC connected state.

The following alternatives can be considered to inform eNB the success of GNSS measurement at UE side after GNSS measurement in RRC connected. In one alternative, the UE will report the new GNSS validity duration. In another alternative, the reception of any UL transmission from the UE at eNB after the GNSS measurement.

In some embodiments, the UE autonomously determines its GNSS validity duration upon acquiring a GNSS position fix and reports it to the network. Moreover, the network can also send a GNSS measurement trigger to a UE in RRC_CONNECTED state e.g., when its GNSS validity duration is about to expire.

Since the validity duration is determined autonomously by the UE while the GNSS gap is configured by the network, some embodiments enable the UE and the network to have the full knowledge of the time when the GNSS duration will end and a new GNSS gap will start/end at the UE.

Some embodiments accordingly address a need for methods and signalling to support a common understanding (between eNB and UE) of the timeline of GNSS-related actions performed at an loT NTN UE.

Some embodiments in this regard tie the GNSS validity duration with the GNSS gap configuration so as to ensure that the UE and eNB are synchronized in time with regards to the start/stop of GNSS-related actions performed by the UE. In particular, some embodiments tie the GNSS configuration to GNSS validity duration, introduce support for the above using timealignment timers, and/or introduce signalling to provide information to the network to inform the exact timeline of one or more GNSS related actions performed at the UE.

Certain embodiments may provide one or more of the following technical advantage(s). Some embodiments advantageously ensure that the UE and eNB know the exact onset in time of the GNSS related actions performed by the UE such as GNSS measurement gap and the GNSS validity duration.

Note 1 : The embodiments outlined below are described mainly in terms of LTE based (including loT) NTNs, but they are equally applicable in an NTN based on NR (including loT) technology.

Note 2: The term “network” is used in the solution description to refer to a network node, which typically will be an eNB (e.g., in a LTE based NTN such as loT NTN), but which may also be a gNB (e.g., in a NR based NTN), or a base station or an access point in another type of network, or any other network node with the ability to directly or indirectly communicate with a UE.

Note 3: One example of a Global Navigation Satellite System (GNSS) is the American Global Positioning System (GPS), but there are also other also other similar systems which could provide the functionality utilized in embodiments herein, e.g., the Russian Global Navigation Satellite System (GLONASS), the Chinese BeiDou Navigation Satellite System and the European Galileo.

Note 4: The terms “connected mode”, “RRC_CONNECTED state” or “RRC_CONNECTED mode” are used interchangeably herein.

Note 5: In the following embodiments, the terms aperiodic, event-based, and periodic GNSS measurement events are used as follows: periodic GNSS measurement event means that the UE performs GNSS measurements in a time-periodic manner according to a GNSS measurement command and the configuration sent in that command; event-based GNSS measurement means that the UE performs one or more measurements according to a GNSS measurement command and the configuration sent in that command such that the occurrence of those measurements is tied to an event (e.g., the expiry of GNSS validity duration with or without a certain time offset).

Note 6: Unless otherwise stated, the term periodic may refer to the time-periodic GNSS measurements as well as the event-based GNSS measurements. If further distinction between the two types is intended, the terms “time-periodic” measurement and “event-based” GNSS measurement are used.

Note 7: When a signaling message or parameter, or a UE behavior, is specified in a standard, this is referred to as “standardized”, “specified” or “specified in a standard”. That is, these expressions/terms are equivalent.

Note 8: The term/expression “GNSS position fix time duration” refers to the time the UE needs to perform a GNSS position fix (i.e. , a successful GNSS position measurement), which may vary e.g., depending on the UE’s GNSS state (often referred to as “hot”, “warm”, and “cold” state, or “hot start”, “warm start” and “cold start”).

Tying a GNSS measurement gap configuration to the expiration of the GNSS validity duration

In some embodiments, a GNSS measurement gap can be tied to, or associated with, the expiration of the UE’s GNSS validity duration, irrespective of how long that is. Here, a GNSS measurement gap exemplifies the gap 50 in Figure 1 and the UE’s GNSS validity duration exemplifies the validity duration 40 in Figure 1. This association can be that the GNSS measurement gap always starts exactly at the expiration of the GNSS validity duration, a certain time period X before the expiration of the GNSS validity duration or a certain time period X after the expiration of the GNSS validity duration. Here, X is an example of the offset 42 in Figure 1. When configured/specified, such a GNSS measurement gap would occur every time the UE’s GNSS validity duration expires. If the UE always uses the same GNSS validity duration, such an association between the GNSS measurement gap and the expiration of the GNSS validity duration will result in a periodically recurring GNSS measurement gap. However, it should be noted that a UE is free to change its validity duration (which is reported to the network by the UE), but the association between the GNSS measurement gap and the expiration of the GNSS validity duration remains unchanged regardless of changes of the GNSS validity duration (i.e., in such cases the GNSS measurement gap will not recur periodically).

The association between the GNSS measurement gap and the expiration of the GNSS validity duration may be specified in a standard or configured by the network (e.g., an eNB), or partly standardized and partly configured by the network. This can be seen as a tradeoff between configuration flexibility and minimization of the signaling overhead. Zero signaling overhead can be achieved if the full GNSS measurement gap configuration, including the details of its association with the expiration of the GNSS validity duration, is specified in the standard, and the standard also states that the GNSS measurement gap is always present as specified, and the network is mandated to honor it by not scheduling the UE during the gap. With this option, the network thus cannot choose to not configure the GNSS measurement gap.

As another option, the properties of the GNSS measurement gap, including the details of its association with the expiration of the GNSS validity duration, are standardized, while the network has the flexibility to configure whether the GNSS measurement gap should be used (i.e., present). With this option, the configuration may be signaled (e.g., in an RRCConnectionReconfiguration message) e.g., using a BOOLEAN field, or an optional ENUMERATED field with a single possible value (where presence of the field indicates that the GNSS measurement gap should be used, while absence of the field indicates that the GNSS measurement gap should not be used, i.e., is not configured). This signaling of the configuration is one example of the signaling 28 in Figure 1.

As another option, the standard specifies two or three of the three above-described association variants (i.e., that the GNSS measurement gap starts exactly at, a time period X before, or a time period X after the expiration of the expiration of the GNSS validity duration. With this option, the GNSS measurement gap may be configured (e.g., in an RRCConnectionReconfiguration message) using an ENUMERATED field with one value for each of the two or three association variants. As a further option, the configuration may include a value of X. This signaling of the configuration is another example of the signaling 28 in Figure 1.

As yet another option, the standard specifications could state that the association between the GNSS measurement gap and the expiration of the GNSS validity duration is governed by a configurable parameter, X, indicating the difference (or offset) in time between the expiration of the GNSS validity duration and the start of the GNSS measurement gap. With this option, the parameter X can be configured (e.g., in an RRCConnectionReconfiguration message) to be 0 (zero), < 0 (negative) or > 0 (positive). This signaling of the parameter X is yet another example of the signaling 28 in Figure 1.

There are different options for a configuration parameter (e.g., included in an RRCConnectionReconfiguration message) configuring the value of X in the above description. As one option, the parameter may be an ENUMERATED field with a few selected values, where each value is expressed in e.g., slots, frames or milliseconds. As another option, the parameter may be an INTEGER field indicating e.g., a number of slots, a number of frames or a number of milliseconds.

In some embodiments, the configuration of the GNSS measurement gap may include an indication of a number of times the GNSS measurement gap will occur, or a time period during which the configuration is valid. This signaling of the number of times the GNSS measurement gap will occur, or the time period during which the configuration is valid, is still another example of the signaling 28 in Figure 1.

Optionally, the occurrence of the GNSS measurement gap can be an implicit instruction to the UE to perform a GNSS measurement. This rule may be configurable (e.g., using a BOOLEAN field, e.g., in an RRCConnectionReconfiguration message) or specified in the standard.

In the above, it is described how the start of a GNSS measurement gap can be associated with the expiration of the GNSS validity duration. However, the method will work equally well if the end of the GNSS measurement gap is the reference point for the association instead of the start of the GNSS measurement gap. Another alternative is to have the middle of the GNSS measurement gap as the reference point. In some embodiments, a new MAC CE for TA adjustment is defined to enable closed- loop TA control and the new MAC CE is further associated with a new Time Alignment Timer, i.e.a timing advance validity duration (that is configured with a finite value and which may be called e.g. TimeAlignmentTimer2), and the reception of the new MAC CE indicates to the UE that it is allowed to transmit after the GNSS validity duration has expired, as long as the new Time Alignment Timer is running. Optionally, the value of the new Time Alignment Timer could be explicitly indicated in the new MAC CE, or the indication to the UE whether it is allowed to transmit after the GNSS validity duration has expired could be explicitly indicated with a bit in the new MAC CE. If the new Time Alignment Timer (e.g., TimeAlignmentTimer2) described above is used, and it expires after the end of the GNSS validity duration (as determined and reported by the UE), then, as one option, the start (or end) of the GNSS measurement gap associated with the expiration of the GNSS validity duration is instead associated with the expiration of the new Time Alignment Timer (i.e., TimeAlignmentTimer2), and the same association relation applies. As another option, if the new Time Alignment Timer (i.e., TimeAlignmentTimer2) is configured, and it expires after the end of the GNSS validity duration (as determined and reported by the UE), the GNSS measurement gap associated with the expiration of the GNSS validity duration (if configured (or specified)) is removed, i.e., deconfigured. As yet another option, the new MAC CE for TA adjustment (as described in above) may include an indication of whether a GNSS measurement gap associated with the GNSS validity duration should be removed (i.e., de-configured) or be associated with the expiration of the new Time Alignment Timer (i.e., TimeAlignmentTimer2).

Another possibility is to enable the network to instruct the UE to extend the current GNSS validity duration, e.g. if the network determines that the UE’s transmission timing error (as detected by the network when receiving the UE’s transmission) is small enough to allow the UE to continue using its latest GNSS measurement for further UE autonomous TA calculations beyond the time when the UE’s GNSS validity duration expires. If this possibility is specified and/or used in a network, any configured (or specified) GNSS measurement gap associated with the expiration of the GNSS validity duration may be associated with the expiration of the extended GNSS validity duration. As another option, a GNSS measurement gap associated with the expiration of the GNSS validity duration is removed - i.e., de-configured - if the GNSS validity duration is extended through instruction from the network. As yet another option, the instruction to extend the GNSS validity duration may include an indication of whether a GNSS measurement gap associated with the GNSS validity duration should be remove (i.e., deconfigured) or be associated with the expiration of the extended GNSS validity duration.

The signaling used for the configuration of the GNSS measurement gap, as an example of signaling 28 in Figure 1, may be RRC signaling (e.g., an RRCConnectionReconfiguration message) or MAC signaling. Another option is that the details of the GNSS measurement gap, including the configurable part(s) of its association with the expiration of the GNSS validity duration, are configured using RRC signaling, but this configuration is activated (or deactivated) using MAC signaling. This MAC signaling is yet another example of the signaling in Figure 1.

To enable tying a recurring GNSS measurement gap to the expiration of the GNSS validity duration (exactly at, slightly before, or slightly after the expiration), the UE and the network have to be synchronized with regards to when this happens. Some embodiments achieve this by the UE reporting the full GNSS validity duration from a defined point in time, rather than the remaining GNSS validity duration (which is susceptible to scheduling uncertainty, HARQ retransmissions, etc.) or the full GNSS validity duration with an uncertain starting point, such as the time when the GNSS position fix occurred. As long as the reported GNSS validity duration is defined from a certain well-defined start timepoint, the eNB can determine how much of it that remains at any given time. The defined point in time could be e.g., the start or the end of the GNSS measurement gap during which the last GNSS measurement was performed. Alternatively, the expiration of the validity duration can be indicated as a UTC (or optionally a UTC + SFN + subframe to allow a coarser UTC to be used).

Another alternative is that the GNSS validity duration starts from the point in time when the UE achieved GNSS position fix, and the UE indicates this starting time, e.g., in the form of an offset from the start or the end of the GNSS measurement gap in which the GNSS position fix was achieved, to the network when the UE reports the full GNSS validity duration.

In some embodiments, the mechanisms for configuration of a recurring GNSS measurement gap that is tied to the expiration of the GNSS validity duration are standardized along with mechanisms for configuration of an aperiodic one-time GNSS measurement gap, preferably together with an instruction to the UE to perform a GNSS measurement.

The recurring GNSS measurement gap tied to the expiration of the GNSS validity duration give the UE what it needs during “normal” operation, but in more exceptional cases, e.g., if the UE is moving exceptionally fast and the eNB sees that the UL reception timing error is about to be greater than the cyclic prefix (CP) (even though a fair bit may be left of the GNSS validity duration as a safety margin), then the eNB can instruct the UE to perform a GNSS measurement and configure a one-time GNSS measurement gap in which to do it. (An alternative would be to keep the UL reception timing error within the CP using Timing Advance Command MAC CEs.)

In view of the modifications and variations herein, Figure 4 depicts a method performed by a communication device configured for use in a communication network in accordance with particular embodiments. The method includes performing a geopositioning measurement during a geopositioning measurement gap triggered by expiration of a validity duration for which a geopositioning fix or timing advance of the communication device is valid (Block 400). The method also includes obtaining a geopositioning fix of the communication device using a result of the geopositioning measurement (Block 405).

In some embodiments, the method also includes autonomously determining the validity duration for which a geopositioning fix or timing advance of the communication device is valid (Block 480).

In some embodiments, the method also includes reporting, to the communication network, the validity duration as defined from a reference time (Block 455).

In some embodiments, the method also includes reporting, to the communication network, an absolute time of expiration of the validity duration (Block 460).

In some embodiments, the method also includes determining that the geopositioning measurement gap is triggered, based on a rule or configuration (Block 410). The rule or configuration may for example specify that, each time a validity duration for which a geopositioning fix or timing advance of the communication device expires, a geopositioning measurement gap is triggered by expiration of that validity duration. In some embodiments, the method also includes receiving the rule or configuration from a communication network.

In some embodiments, the method also includes determining when the geopositioning measurement gap occurs, based on when the validity duration expires (Block 420).

In some embodiments, the method also includes receiving, from the communication network, a measurement gap configuration that configures the geopositioning measurement gap.

In some embodiments, the method also includes determining a pre-compensation timing advance from the geopositioning fix (Block 470).

In some embodiments, the method also includes performing a random access channel transmission using the determined pre-compensation timing advance as part of accessing the communication network (Block 475).

In some embodiments, the method also comprises determining that the geopositioning measurement gap is triggered, based on a rule or configuration specifying that, each time a validity duration for which a geopositioning fix or timing advance of the communication device expires, a geopositioning measurement gap is triggered by expiration of that validity duration. In some embodiments, the communication device is preconfigured with the rule or configuration. In some embodiments, the method also comprises receiving the rule or configuration from a communication network.

In some embodiments, each time a validity duration for which a geopositioning fix or timing advance of the communication device expires, a geopositioning measurement gap is triggered by expiration of that validity duration. In some embodiments, the geopositioning measurement gap is a periodic geopositioning measurement gap that recurs periodically each time a validity duration for which a geopositioning fix or timing advance of the communication device expires.

In some embodiments, the geopositioning measurement gap is a periodic geopositioning measurement gap that recurs periodically a number of times, wherein the method further comprises receiving signaling indicating the number of times from the communication network.

In some embodiments, the method also comprises determining when the geopositioning measurement gap occurs, based on when the validity duration expires. In some embodiments, determining when the geopositioning measurement gap occurs comprises determining when a reference point of the geopositioning measurement gap occurs, as a function of when the validity duration expires. In some embodiments, the reference point of the geopositioning measurement gap is a start time or an end time of the geopositioning measurement gap. In some embodiments, the reference point of the geopositioning measurement gap is a middle of the geopositioning measurement gap. In some embodiments, the method also comprises receiving, from the communication network, signaling indicating which reference point of the geopositioning measurement gap, out of multiple possible reference points of the geopositioning measurement gap, the communication device is to determine as a function of when the validity duration expires. In some embodiments, determining when the reference point of the geopositioning measurement gap occurs comprises determining an expiration time as a time at which the validity duration expires. In some embodiments, determining when the reference point of the geopositioning measurement gap occurs comprises determining the reference point by offsetting the expiration time by an offset. In some embodiments, the method also comprises receiving, from the communication network, signaling indicating the offset. In some embodiments, the offset indicates how long before the expiration time, or how long after the expiration time, the reference point occurs. In some embodiments, the method also comprises receiving, from the communication network, signaling indicating whether the offset indicates how long before the expiration time the reference point occurs or indicates how long after the expiration time the reference point occurs.

In some embodiments, the method also comprises receiving, from the communication network, a measurement gap configuration that configures the geopositioning measurement gap. In some embodiments, the measurement gap configuration configures whether or not the geopositioning measurement gap is triggered by expiration of a validity duration for which a geopositioning fix or timing advance of the communication device is valid. In some embodiments, the measurement gap configuration configures timing of the geopositioning measurement gap as a function of timing of expiration of the validity duration. In some embodiments, the measurement gap configuration includes a gap start offset time indicating an offset between a time when the measurement gap starts and a time when the validity duration expires. In some embodiments, the measurement gap configuration includes a validity time duration indicating a duration of time during which the measurement gap configuration is valid.

In some embodiments, the method also comprises receiving, from the communication network, signaling indicating that an initial validity duration for which a geopositioning fix of the communication device is valid is to be extended, and the geopositioning measurement gap is triggered by expiration of the extended validity duration.

In some embodiments, the method also comprises receiving, from the communication network, signaling indicating that, or whether, expiration of a validity duration for which a geopositioning fix or timing advance of the communication device is valid triggers a geopositioning measurement gap.

In some embodiments, the method also comprises reporting, to the communication network, the validity duration as defined from a reference time, wherein the reference time is a reference point of a measurement gap during which a geopositioning measurement was last performed. In some embodiments, the reference point is a start time or an end time of the measurement gap during which a geopositioning measurement was last performed. In other embodiments, the reference point is an offset from a start time or an end time of the measurement gap during which a geopositioning measurement was last performed.

In some embodiments, the method also comprises reporting, to the communication network, an absolute time of expiration of the validity duration. In some embodiments, the absolute time is a Universal Time Coordinated, UTC, value at which the validity duration expired.

In some embodiments, the method also comprises accessing the communication network using the obtained geopositioning fix.

In some embodiments, the method also comprises determining a pre-com pensation timing advance from the geopositioning fix. In some embodiments, the method also comprises performing a random access channel transmission using the determined pre-compensation timing advance as part of accessing the communication network

In some embodiments, the communication network is a non-terrestrial network, NTN. Figure 5 depicts a method performed by a communication device configured for use in a communication network in accordance with other particular embodiments. The method includes determining when a geopositioning measurement gap for the communication device occurs based on when a validity duration for which a geopositioning fix or timing advance of the communication device is valid expires (Block 500). The method also includes performing a geopositioning measurement when the geopositioning measurement gap occurs (Block 510). The method also includes updating the geopositioning fix of the communication device using a result of the geopositioning measurement (Block 520).

In some embodiments, the method also includes autonomously determining the validity duration for which a geopositioning fix or timing advance of the communication device is valid (Block 530).

In some embodiments, determining when the geopositioning measurement gap occurs comprises determining when the geopositioning measurement gap starts, based on when the validity duration expires.

Figure 6 depicts a method performed by a communication device configured for use in a communication network in accordance with other particular embodiments. The method includes receiving, from the communication network, signaling that configures or activates triggering of a geopositioning measurement gap by expiration of a validity duration for which a geopositioning fix or timing advance of the communication device is valid (Block 600).

In some embodiments, the method also includes performing a geopositioning measurement during a geopositioning measurement gap triggered, according to the signaling, by expiration of a validity duration for which a geopositioning fix or timing advance of the communication device is valid (Block 610). In some embodiments, the method also includes obtaining a geopositioning fix of the communication device using a result of the geopositioning measurement (Block 620).

In some embodiments, the method also includes determining a pre-compensation timing advance from the geopositioning fix (Block 640). In some embodiments, the method also includes performing a random access channel transmission using the determined pre-compensation timing advance as part of accessing the communication network (Block 650).

In some embodiments, the method also includes autonomously determining the validity duration for which a geopositioning fix or timing advance of the communication device is valid (Block 660).

In some embodiments, according to the signaling, each time a validity duration for which a geopositioning fix or timing advance of the communication device expires, a geopositioning measurement gap is triggered by expiration of that validity duration. In some embodiments, according to the signaling, the geopositioning measurement gap is a periodic geopositioning measurement gap that recurs periodically each time a validity duration for which a geopositioning fix or timing advance of the communication device expires.

In some embodiments, according to the signaling, the geopositioning measurement gap is a periodic geopositioning measurement gap that recurs periodically a number of times, wherein the signaling indicates the number of times.

In some embodiments, the signaling configures how the communication device is to determine when the geopositioning measurement gap occurs as a function of when the validity duration expires.

In some embodiments, the signaling configures a start time or an end time of the geopositioning measurement gap as a function of when the validity duration expires.

In some embodiments, the signaling configures which reference point of the geopositioning measurement gap, out of multiple possible reference points, is to be defined as a function of when the validity duration expires. In other embodiments, the signaling alternatively or additionally configures an offset between a reference point of the geopositioning measurement gap and an expiration time at which the validity duration expires, wherein the offset indicates how long before the expiration time, or how long after the expiration time, the reference point occurs.

In some embodiments, the signaling configures whether or not a geopositioning measurement gap is to be triggered by expiration of a validity duration that has been extended.

In some embodiments, the signaling configures whether or not a geopositioning measurement gap is to be triggered by expiration of a timing advance validity duration for which a timing advance of the communication device is valid, which has expired after a expiration of a geopositioning fix validity duration for which a geopositioning fix of the communication device is valid.

In some embodiments, the method also comprises performing a geopositioning measurement during a geopositioning measurement gap triggered, according to the signaling, by expiration of a validity duration for which a geopositioning fix or timing advance of the communication device is valid. In some embodiments, the method also comprises obtaining a geopositioning fix of the communication device using a result of the geopositioning measurement. In some embodiments, the method also comprises accessing the communication network using the obtained geopositioning fix. In some embodiments, the method also comprises determining a pre-com pensation timing advance from the geopositioning fix. In some embodiments, the method also comprises performing a random access channel transmission using the determined pre-compensation timing advance as part of accessing the communication network.

In some embodiments, the communication network is a non-terrestrial network, NTN. In some embodiments, the signaling is radio resource control signaling or medium access control signaling.

Figure 7 depicts a method performed by a communication device configured for use in a communication network in accordance with other particular embodiments. The method includes reporting, to the communication network, a validity duration for which a geopositioning fix of the communication device is valid, as defined from a reference time (Block 700). In some embodiments, the reference time is a reference point of a measurement gap during which a geopositioning measurement was last performed by the communication device.

In some embodiments, the reference point is a start time or an end time of the measurement gap during which a geopositioning measurement was last performed. In other embodiments, the reference point is an offset from a start time or an end time of the measurement gap during which a geopositioning measurement was last performed.

In some embodiments, the method also includes autonomously determining the validity duration for which a geopositioning fix or timing advance of the communication device is valid (Block 710).

Figure 8 depicts a method performed by a communication device configured for use in a communication network in accordance with other particular embodiments. The method includes reporting, to the communication network, an absolute time of expiration of a validity duration for which a geopositioning fix of the communication device is valid (Block 800).

In some embodiments, the absolute time is a Universal Time Coordinated, UTC, value at which the validity duration expired.

In some embodiments, the communication device is an Internet of Things, loT, NTN user equipment.

In some embodiments, the communication device is in radio resource control, RRC, connected state.

In some embodiments, the geopositioning measurement is a Global Navigate Satellite System, GNSS, measurement. In some embodiments, the geopositioning measurement gap is a GNSS measurement gap, and the geopositioning fix is a GNSS positioning fix.

In some embodiments, the method also includes autonomously determining the validity duration for which a geopositioning fix or timing advance of the communication device is valid (Block 810).

Figure 9 depicts a method performed by a network node in a communication network in accordance with other particular embodiments. In some embodiments, the method includes transmitting, to the communication device, signaling indicating that, or whether, expiration of a validity duration for which a geopositioning fix or timing advance of the communication device is valid triggers a geopositioning measurement gap (Block 950).

In some embodiments, the method also includes transmitting, to the communication device, a measurement gap configuration that configures the geopositioning measurement gap (Block 940).

In some embodiments, the method also includes receiving, from the communication device, a report reporting the validity duration as defined from a reference time (Block 955).

In some embodiments, the method also includes receiving, from the communication device, a report that reports an absolute time of expiration of the validity duration (Block 960).

In some embodiments the method includes determining a geopositioning measurement gap triggered by expiration of a validity duration for which a geopositioning fix or timing advance of a communication device is valid (Block 900). In some embodiments, the method also includes determining when the geopositioning measurement gap occurs, based on when the validity duration expires (Block 920).

In some embodiments the method also includes restricting scheduling of transmissions to or from the communication device during the geopositioning measurement gap (Block 905).

In some embodiments, the method also comprises determining that the geopositioning measurement gap is triggered, based on a rule or configuration specifying that, each time a validity duration for which a geopositioning fix or timing advance of the communication device expires, a geopositioning measurement gap is triggered by expiration of that validity duration. In some embodiments, the communication device is preconfigured with the rule or configuration. In some embodiments, the method also comprises transmitting the rule or configuration to the communication device.

In some embodiments, the geopositioning measurement gap is a periodic geopositioning measurement gap that recurs periodically a number of times. In some embodiments, the method further comprises transmitting, to the communication device, signaling indicating the number of times.

In some embodiments, the method further comprises determining when the geopositioning measurement gap occurs, based on when the validity duration expires. In some embodiments, determining when the geopositioning measurement gap occurs comprises determining when a reference point of the geopositioning measurement gap occurs, as a function of when the validity duration expires. In some embodiments, the reference point of the geopositioning measurement gap is a start time or an end time of the geopositioning measurement gap. In some embodiments, the reference point of the geopositioning measurement gap is a middle of the geopositioning measurement gap. In some embodiments, the method further comprises transmitting, to the communication device, signaling indicating which reference point of the geopositioning measurement gap, out of multiple possible reference points of the geopositioning measurement gap, the communication device is to determine as a function of when the validity duration expires. In some embodiments, determining when the reference point of the geopositioning measurement gap occurs comprises determining an expiration time as a time at which the validity duration expires. In some embodiments, determining when the reference point of the geopositioning measurement gap occurs comprises determining the reference point by offsetting the expiration time by an offset. In some embodiments, the method further comprises transmitting, to the communication device, signaling indicating the offset. In some embodiments, the offset indicates how long before the expiration time, or how long after the expiration time, the reference point occurs. In some embodiments, the method further comprises transmitting, to the communication device, signaling indicating whether the offset indicates how long before the expiration time the reference point occurs or indicates how long after the expiration time the reference point occurs.

In some embodiments, the method further comprises transmitting, to the communication device, a measurement gap configuration that configures the geopositioning measurement gap. In some embodiments, the measurement gap configuration configures whether or not the geopositioning measurement gap is triggered by expiration of a validity duration for which a geopositioning fix or timing advance of the communication device is valid. In some embodiments, the measurement gap configuration configures timing of the geopositioning measurement gap as a function of timing of expiration of the validity duration. In some embodiments, the measurement gap configuration includes a gap start offset time indicating an offset between a time when the measurement gap starts and a time when the validity duration expires. In some embodiments, the measurement gap configuration includes a validity time duration indicating a duration of time during which the measurement gap configuration is valid.

In some embodiments, the method further comprises transmitting, to the communication device, signaling indicating that an initial validity duration for which a geopositioning fix of the communication device is valid is to be extended, and the geopositioning measurement gap is triggered by expiration of the extended validity duration.

In some embodiments, the geopositioning measurement gap is triggered by expiration of a validity duration for which a timing advance of the communication device is valid. In some embodiments, the geopositioning measurement gap is triggered by expiration of a timing advance validity duration for which a timing advance of the communication device is valid, wherein the timing advance validity duration expires after a geopositioning fix validity duration for which a geopositioning fix of the communication device is valid expires.

In some embodiments, the method further comprises transmitting, to the communication device, signaling indicating that, or whether, expiration of a validity duration for which a geopositioning fix or timing advance of the communication device is valid triggers a geopositioning measurement gap.

In some embodiments, the method further comprises receiving, from the communication device, a report reporting the validity duration as defined from a reference time, wherein the reference time is a reference point of a measurement gap during which a geopositioning measurement was last performed. In some embodiments, the reference point is a start time or an end time of the measurement gap during which a geopositioning measurement was last performed. In other embodiments, the reference point is an offset from a start time or an end time of the measurement gap during which a geopositioning measurement was last performed.

In some embodiments, the method further comprises receiving, from the communication device, a report that reports an absolute time of expiration of the validity duration. In some embodiments, the absolute time is a Universal Time Coordinated, UTC, value at which the validity duration expired.

In some embodiments, the communication network is a non-terrestrial network, NTN.

Figure 10 depicts a method performed by a network node configured for use in a communication network in accordance with other particular embodiments. The method includes determining when a geopositioning measurement gap for a communication device occurs based on when a validity duration for which a geopositioning fix or timing advance of the communication device is valid expires (Block 1000). The method also includes restricting scheduling of transmissions to or from the communication device during the geopositioning measurement gap (Block 1010).

Figure 11 depicts a method performed by a network node configured for use in a communication network in accordance with other particular embodiments. The method includes transmitting, to a communication device, signaling that configures or activates triggering of a geopositioning measurement gap by expiration of a validity duration for which a geopositioning fix or timing advance of the communication device is valid (Block 1100). In some embodiments, according to the signaling, each time a validity duration for which a geopositioning fix or timing advance of the communication device expires, a geopositioning measurement gap is triggered by expiration of that validity duration.

In some embodiments, according to the signaling, the geopositioning measurement gap is a periodic geopositioning measurement gap that recurs periodically each time a validity duration for which a geopositioning fix or timing advance of the communication device expires.

In some embodiments, the signaling is radio resource control signaling or medium access control signaling.

Figure 12 depicts a method performed by a network node configured for use in a communication network in accordance with other particular embodiments. The method includes receiving, from a communication device, a report that reports a validity duration for which a geopositioning fix of the communication device is valid, as defined from a reference time (Block 1200). In some embodiments, the reference time is a reference point of a measurement gap during which a geopositioning measurement was last performed by the communication device.

Figure 13 depicts a method performed by a network node configured for use in a communication network in accordance with other particular embodiments. The method includes receiving, from a communication device, a report that reports an absolute time of expiration of a validity duration for which a geopositioning fix of the communication device is valid (Block 1300).

In some embodiments, the communication device is configured to autonomously determine the validity duration for which a geopositioning fix or timing advance of the communication device is valid.

Embodiments herein also include corresponding apparatuses. Embodiments herein for instance include a communication device 18 configured to perform any of the steps of any of the embodiments described above for the communication device 18.

Embodiments also include a communication device 18 comprising processing circuitry and power supply circuitry. The processing circuitry is configured to perform any of the steps of any of the embodiments described above for the communication device 18. The power supply circuitry is configured to supply power to the communication device 18.

Embodiments further include a communication device 18 comprising processing circuitry. The processing circuitry is configured to perform any of the steps of any of the embodiments described above for the communication device 18. In some embodiments, the communication device 18 further comprises communication circuitry. Embodiments further include a communication device 18 comprising processing circuitry and memory. The memory contains instructions executable by the processing circuitry whereby the communication device 18 is configured to perform any of the steps of any of the embodiments described above for the communication device 18.

Embodiments moreover include a user equipment (UE). The UE comprises an antenna configured to send and receive wireless signals. The UE also comprises radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry. The processing circuitry is configured to perform any of the steps of any of the embodiments described above for the communication device 18. In some embodiments, the UE also comprises an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry. The UE may comprise an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry. The UE may also comprise a battery connected to the processing circuitry and configured to supply power to the UE.

Embodiments herein also include a network node 30 configured to perform any of the steps of any of the embodiments described above for the network node 30.

Embodiments also include a network node 30 comprising processing circuitry and power supply circuitry. The processing circuitry is configured to perform any of the steps of any of the embodiments described above for the network node 30. The power supply circuitry is configured to supply power to the network node 30.

Embodiments further include a network node 30 comprising processing circuitry. The processing circuitry is configured to perform any of the steps of any of the embodiments described above for the network node 30. In some embodiments, the network node 30 further comprises communication circuitry.

Embodiments further include a network node 30 comprising processing circuitry and memory. The memory contains instructions executable by the processing circuitry whereby the network node 30 is configured to perform any of the steps of any of the embodiments described above for the network node 30.

More particularly, the apparatuses described above may perform the methods herein and any other processing by implementing any functional means, modules, units, or circuitry. In one embodiment, for example, the apparatuses comprise respective circuits or circuitry configured to perform the steps shown in the method figures. The circuits or circuitry in this regard may comprise circuits dedicated to performing certain functional processing and/or one or more microprocessors in conjunction with memory. For instance, the circuitry may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory may include program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments. In embodiments that employ memory, the memory stores program code that, when executed by the one or more processors, carries out the techniques described herein.

Figure 14 for example illustrates a communication device 18 as implemented in accordance with one or more embodiments. As shown, the communication device 1400 includes processing circuitry 1410 and communication circuitry 1420. The communication circuitry 1420 (e.g., radio circuitry) is configured to transmit and/or receive information to and/or from one or more other nodes, e.g., via any communication technology. Such communication may occur via one or more antennas that are either internal or external to the communication device 1400. In some embodiments, the communication circuitry 1420 is shared for performing geopositioning measurements 38 and for accessing the NTN 10. The processing circuitry 1410 is configured to perform processing described above, e.g., in any of Figures 4-8, such as by executing instructions stored in memory 1430. The processing circuitry 1410 in this regard may implement certain functional means, units, or modules.

Figure 15 illustrates a network node 30 as implemented in accordance with one or more embodiments. As shown, the network node 30 includes processing circuitry 1510 and communication circuitry 1520. The communication circuitry 1520 is configured to transmit and/or receive information to and/or from one or more other nodes, e.g., via any communication technology. The processing circuitry 1510 is configured to perform processing described above, e.g., in any of Figures 9-13, such as by executing instructions stored in memory 1530. The processing circuitry 1510 in this regard may implement certain functional means, units, or modules.

Those skilled in the art will also appreciate that embodiments herein further include corresponding computer programs.

A computer program comprises instructions which, when executed on at least one processor of an apparatus, cause the apparatus to carry out any of the respective processing described above. A computer program in this regard may comprise one or more code modules corresponding to the means or units described above.

Embodiments further include a carrier containing such a computer program. This carrier may comprise one of an electronic signal, optical signal, radio signal, or computer readable storage medium. In this regard, embodiments herein also include a computer program product stored on a non-transitory computer readable (storage or recording) medium and comprising instructions that, when executed by a processor of an apparatus, cause the apparatus to perform as described above.

Embodiments further include a computer program product comprising program code portions for performing the steps of any of the embodiments herein when the computer program product is executed by a computing device. This computer program product may be stored on a computer readable recording medium.

Figure 16 shows an example of a communication system 1600 in accordance with some embodiments.

In the example, the communication system 1600 includes a telecommunication network 1602 that includes an access network 1604, such as a radio access network (RAN), and a core network 1606, which includes one or more core network nodes 1608. The access network 1604 includes one or more access network nodes, such as network nodes 1610a and 1610b (one or more of which may be generally referred to as network nodes 1610), or any other similar 3^rd Generation Partnership Project (3GPP) access nodes or non-3GPP access points. Moreover, as will be appreciated by those of skill in the art, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network 1602 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network 1602 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication network 1602, including one or more network nodes 1610 and/or core network nodes 1608.

Examples of an ORAN network node include an open radio unit (0-Rll), an open distributed unit (0-Dll), an open central unit (O-CU), including an O-CU control plane (O-CU- CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an A1 , F1, W1, E1 , E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an 0-2 interface defined by the O-RAN Alliance or comparable technologies. The network nodes 1610 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 1612a, 1612b, 1612c, and 1612d (one or more of which may be generally referred to as UEs 1612) to the core network 1606 over one or more wireless connections.

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

The UEs 1612 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and/or operable to communicate wirelessly with the network nodes 1610 and other communication devices. Similarly, the network nodes 1610 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 1612 and/or with other network nodes or equipment in the telecommunication network 1602 to enable and/or provide network access, such as wireless network access, and/or to perform other functions, such as administration in the telecommunication network 1602.

In the depicted example, the core network 1606 connects the network nodes 1610 to one or more hosts, such as host 1616. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 1606 includes one more core network nodes (e.g., core network node 1608) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and/or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 1608. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and/or a User Plane Function (UPF). The host 1616 may be under the ownership or control of a service provider other than an operator or provider of the access network 1604 and/or the telecommunication network 1602, and may be operated by the service provider or on behalf of the service provider. The host 1616 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio/video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

As a whole, the communication system 1600 of Figure 16 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are 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 standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and/or any other appropriate wireless communication standard, such as the 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.

In some examples, the telecommunication network 1602 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 1602 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 1602. For example, the telecommunications network 1602 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and/or Massive Machine Type Communication (mMTC)/Massive loT services to yet further UEs.

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

In the example, the hub 1614 communicates with the access network 1604 to facilitate indirect communication between one or more UEs (e.g., UE 1612c and/or 1612d) and network nodes (e.g., network node 1610b). In some examples, the hub 1614 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 1614 may be a broadband router enabling access to the core network 1606 for the UEs. As another example, the hub 1614 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 1610, or by executable code, script, process, or other instructions in the hub 1614. As another example, the hub 1614 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 1614 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 1614 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 1614 then provides to the UE either directly, after performing local processing, and/or after adding additional local content. In still another example, the hub 1614 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

The hub 1614 may have a constant/persistent or intermittent connection to the network node 1610b. The hub 1614 may also allow for a different communication scheme and/or schedule between the hub 1614 and UEs (e.g., UE 1612c and/or 1612d), and between the hub 1614 and the core network 1606. In other examples, the hub 1614 is connected to the core network 1606 and/or one or more UEs via a wired connection. Moreover, the hub 1614 may be configured to connect to an M2M service provider over the access network 1604 and/or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 1610 while still connected via the hub 1614 via a wired or wireless connection. In some embodiments, the hub 1614 may be a dedicated hub - that is, a hub whose primary function is to route communications to/from the UEs from/to the network node 1610b. In other embodiments, the hub 1614 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 1610b, but which is additionally capable of operating as a communication start and/or end point for certain data channels.

Figure 17 shows a UE 1700 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle, vehicle-mounted or vehicle embedded/integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB- loT) UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.

A UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (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 relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

The UE 1700 includes processing circuitry 1702 that is operatively coupled via a bus 1704 to an input/output interface 1706, a power source 1708, a memory 1710, a communication interface 1712, and/or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 17. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

The processing circuitry 1702 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 1710. The processing circuitry 1702 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 1702 may include multiple central processing units (CPUs).

In the example, the input/output interface 1706 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and/or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE 1700. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, 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 may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

In some embodiments, the power source 1708 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source 1708 may further include power circuitry for delivering power from the power source 1708 itself, and/or an external power source, to the various parts of the UE 1700 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 1708. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 1708 to make the power suitable for the respective components of the UE 1700 to which power is supplied.

The memory 1710 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 1710 includes one or more application programs 1714, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 1716. The memory 1710 may store, for use by the UE 1700, any of a variety of various operating systems or combinations of operating systems.

The memory 1710 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and/or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUlCC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 1710 may allow the UE 1700 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 1710, which may be or comprise a device-readable storage medium. The processing circuitry 1702 may be configured to communicate with an access network or other network using the communication interface 1712. The communication interface 1712 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 1722. The communication interface 1712 may include one or more transceivers used to communicate, such as 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 1718 and/or a receiver 1720 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 1718 and receiver 1720 may be coupled to one or more antennas (e.g., antenna 1722) and may share circuit components, software or firmware, or alternatively be implemented separately.

In the illustrated embodiment, communication functions of the communication interface 1712 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and/or standards, such as IEEE 802.11, Code Division Multiplexing 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 networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 1712, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input. A UE, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot 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/moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like 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 for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and/or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE 1700 shown in Figure 17.

As yet another specific example, in an loT scenario, a UE may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another UE and/or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-loT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.

In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller 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 drone’s speed. The first and/or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

Figure 18 shows a network node 1800 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a UE and/or with other network nodes or equipment, in a telecommunication 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 NodeBs (gNBs)), O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).

Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an O-RAN access node) and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and/or Minimization of Drive Tests (MDTs).

The network node 1800 includes a processing circuitry 1802, a memory 1804, a communication interface 1806, and a power source 1808. The network node 1800 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 1800 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 1800 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 1804 for different RATs) and some components may be reused (e.g., a same antenna 1810 may be shared by different RATs). The network node 1800 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1800, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 1800. The processing circuitry 1802 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node 1800 components, such as the memory 1804, to provide network node 1800 functionality.

In some embodiments, the processing circuitry 1802 includes a system on a chip (SOC). In some embodiments, the processing circuitry 1802 includes one or more of radio frequency (RF) transceiver circuitry 1812 and baseband processing circuitry 1814. In some embodiments, the radio frequency (RF) transceiver circuitry 1812 and the baseband processing circuitry 1814 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 1812 and baseband processing circuitry 1814 may be on the same chip or set of chips, boards, or units.

The memory 1804 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device-readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by the processing circuitry 1802. The memory 1804 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and/or other instructions capable of being executed by the processing circuitry 1802 and utilized by the network node 1800. The memory 1804 may be used to store any calculations made by the processing circuitry 1802 and/or any data received via the communication interface 1806. In some embodiments, the processing circuitry 1802 and memory 1804 is integrated.

The communication interface 1806 is used in wired or wireless communication of signaling and/or data between a network node, access network, and/or UE. As illustrated, the communication interface 1806 comprises port(s)/terminal(s) 1816 to send and receive data, for example to and from a network over a wired connection. The communication interface 1806 also includes radio front-end circuitry 1818 that may be coupled to, or in certain embodiments a part of, the antenna 1810. Radio front-end circuitry 1818 comprises filters 1820 and amplifiers 1822. The radio front-end circuitry 1818 may be connected to an antenna 1810 and processing circuitry 1802. The radio front-end circuitry may be configured to condition signals communicated between antenna 1810 and processing circuitry 1802. The radio front-end circuitry 1818 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 1818 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1820 and/or amplifiers 1822. The radio signal may then be transmitted via the antenna 1810. Similarly, when receiving data, the antenna 1810 may collect radio signals which are then converted into digital data by the radio front-end circuitry 1818. The digital data may be passed to the processing circuitry 1802. In other embodiments, the communication interface may comprise different components and/or different combinations of components.

In certain alternative embodiments, the network node 1800 does not include separate radio front-end circuitry 1818, instead, the processing circuitry 1802 includes radio front-end circuitry and is connected to the antenna 1810. Similarly, in some embodiments, all or some of the RF transceiver circuitry 1812 is part of the communication interface 1806. In still other embodiments, the communication interface 1806 includes one or more ports or terminals 1816, the radio front-end circuitry 1818, and the RF transceiver circuitry 1812, as part of a radio unit (not shown), and the communication interface 1806 communicates with the baseband processing circuitry 1814, which is part of a digital unit (not shown).

The antenna 1810 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. The antenna 1810 may be coupled to the radio front-end circuitry 1818 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In certain embodiments, the antenna 1810 is separate from the network node 1800 and connectable to the network node 1800 through an interface or port.

The antenna 1810, communication interface 1806, and/or the processing circuitry 1802 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node. Any information, data and/or signals may be received from a UE, another network node and/or any other network equipment. Similarly, the antenna 1810, the communication interface 1806, and/or the processing circuitry 1802 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and/or signals may be transmitted to a UE, another network node and/or any other network equipment.

The power source 1808 provides power to the various components of network node 1800 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 1808 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 1800 with power for performing the functionality described herein. For example, the network node 1800 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 1808. As a further example, the power source 1808 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

Embodiments of the network node 1800 may include additional components beyond those shown in Figure 18 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein. For example, the network node 1800 may include user interface equipment to allow input of information into the network node 1800 and to allow output of information from the network node 1800. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 1800.

Figure 19 is a block diagram illustrating a virtualization environment 1900 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 1900 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 1900 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface.

Applications 1902 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.

Hardware 1904 includes processing circuitry, memory that stores software and/or instructions executable by hardware processing circuitry, and/or other hardware devices as described herein, such as a network interface, input/output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 1906 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 1908a and 1908b (one or more of which may be generally referred to as VMs 1908), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein. The virtualization layer 1906 may present a virtual operating platform that appears like networking hardware to the VMs 1908. The VMs 1908 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 1906. Different embodiments of the instance of a virtual appliance 1902 may be implemented on one or more of VMs 1908, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

In the context of NFV, a VM 1908 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 1908, and that part of hardware 1904 that executes that VM, be it hardware dedicated to that VM and/or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 1908 on top of the hardware 1904 and corresponds to the application 1902.

Hardware 1904 may be implemented in a standalone network node with generic or specific components. Hardware 1904 may implement some functions via virtualization. Alternatively, hardware 1904 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 1910, which, among others, oversees lifecycle management of applications 1902. In some embodiments, hardware 1904 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 1912 which may alternatively be used for communication between hardware nodes and radio units.

Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and/or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in 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 the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer- readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and/or by end users and a wireless network generally.

Consider now an example 3GPP standards contribution aimed at discussing certain aspects disclosed herein.

1 INTRODUCTION

Herein is provided views on improved GNSS operation for Internet of Things (loT) NTN.

2 IMPROVED GNSS OPERATION FOR IOT NTN

The following subsections include various views on different GNSS-related aspects.

2.1 Closed loop time and frequency correction

In the previous RAN1 meetings, the following agreements were made on closed loop time and frequency correction.

Agreement

At least for the case when frequency error is within frequency error requirements, study the mechanisms and conditions to allow UL transmission after original GNSS validity duration expires without GNSS re-acquisition for some duration. • FFS: with legacy closed loop time correction or enhanced closed loop time correction

• This mechanism is enabled/configured by eNB

In NTN, a UE can adjust its timing autonomously as long as it has a valid GNSS position. It is already possible to support closed loop timing correction in NTN as in terrestrial eMTC/NB-loT. A key question is if the existing Timing advance (TA) maintenance procedure is sufficient to maintain a moving UE’s timing in loT NTN. To address this, recall that the additional timing uncertainty in NTN stems from a) satellite’s motion and b) UE’s motion. It is expected that an loT NTN UE will apply segmented uplink pre-compensation to account for the timing drift due to satellite’s motion. Therefore, for the sake of argument, let us assume a worst-case TA error due to satellite motion of 0.39 ns (i.e. , 12*Ts where Ts=32.55 ns) for an eMTC UE. We note that this value is an upper bound on the maximum possible TA error due to satellite motion at the end of an uplink transmission segment assuming that the UE is stationary and the satellite contributes to a worstcase TA drift of 100 is/s. We note that for NR NTN, RAN4 has relaxed the initial transmit timing error requirement from 12*Ts to 29*Ts to account for errors in the satellite/UE positions. If we assume a similar relaxation for eMTC NTN (which has a minimum transmit timing error requirement of 12*Ts in terrestrial networks), the net timing error due to satellite/UE motion needs to be within 17*Ts for eMTC NTN. Assuming a worst-case TA error of 12*Ts due to satellite motion at the end of a transmission segment, there remains 5*Ts (0.16 zs) to account for the TA error due to UE mobility. In Table 2, we provide the time duration until which the UE can meet the uplink transmit timing error budget for various UE speeds. The TA error rate due to UE mobility is estimated for LEO at 600 km and 30 degrees elevation angle.

Table 2 Impact of UE mobility on timing error requirements for eMTC NTN.

Without closed loop timing correction, Table 2 shows that for 3 km/h, the UE may need to correct its timing to account for TA error due to UE mobility either via a TA command (TAC) or by refreshing its GNSS after 34 s. At 120 km/h, such an intervention will be needed every 0.83 s. Note that in this analysis, we have assumed that the UE already corrects its timing every segment to account for the TA error due to satellite motion. To conclude, the existing closed loop timing control mechanism is sufficient to address the uncertainty in UE’s position.

Observation 1 The existing TAC mechanism is sufficient to address the timing error due to incorrect UE position in loT NTN.

Enhancements to enable UL transmission despite GNSS validity duration expiry

Minor enhancements to closed-loop mechanism may be needed to enable an energy efficient operation that avoids GNSS position fix. For instance, the network should have the possibility to indicate to the UE if it can continue to transmit on the uplink even if the GNSS position validity duration has expired. This is essential because the role of closed-loop timing control is to reduce the need of GNSS reacquisition - so even if the GNSS position is invalid, the network may continue to send TACs to help the UE maintain its uplink synchronization. In line with the latest RAN1 agreement, we propose the following:

Proposal 1 eNB to indicate a time duration X to an loT NTN UE in connected mode such that the UE can continue its uplink transmission for a time duration X after GNSS validity duration has expired.

We note that it is up to RAN2 to develop specifications to support the above proposal while minimizing the specification impact. For example, it can be achieved by extending the GNSS validity duration, and/or introducing a new validity duration parameter during which the UE is allowed to transmit.

UE-specific timing drift

Moreover, if the network solely relies on TACs to correct UE’s timing before or after GNSS position validity expiry, the signalling overhead could be very high due to the large timing drift. A potential solution is to allow the UE to compute its TA values (until a new TAC is received) based on the service link and common TA drift parameters, where the parameters related to the service link drift can either be tracked by the UE or indicated by the network. This semi-autonomous approach may help reduce the signalling overhead as fewer TACs will be needed; and the UE need not perform a GNSS position fix to correct its timing.

For loT NTN, it is possible for a network to broadcast drift parameters for common TA. If the network additionally indicates the UE-specific timing drift parameters for the TA to a UE in connected mode, it may enable the UE to update its TA values accordingly (until a new TAC is received) to compensate for its inaccurate GNSS position.

Proposal 2 Network to optionally indicate UE-specific timing drift parameters to an loT NTN UE in connected mode.

Proposal 3 Upon GNSS position expiry in connected mode, an loT NTN UE to use UE- specific drift information (in addition to common TA parameters) to calculate TA values before receiving the next TA command.

Unlike the closed loop TA mechanism, the closed loop frequency adjustment (FA) mechanism is not currently supported. Based on the results reported by the proponents of closed-loop FA, it seems that the frequency error in loT NTN is comparable to that in terrestrial networks, barring some corner cases. Therefore, we do not see a strong need to design and introduce a new closed-loop FA signalling mechanism for loT NTN.

Proposal 4 Closed loop frequency correction mechanism shall not be specified unless absolutely necessary.

2.2 GNSS acquisition in connected mode

In RAN1#109-e, it was concluded that an loT NTN UE may need to re-acquire a GNSS position fix during a long connection. In addition, RAN1 has made the following agreements on this front.

Agreement

• Option 1: UE re-acquires GNSS position fix during RLF procedure

• Option 2: UE re-acquires GNSS position fix with a new gap

Note: this does not imply that a Rel-18 loT NTN UE is mandated to support one or both of the options.

Agreement

Further study on whether there is a need for potential enhancements on the following for long connection time

• UE triggered GNSS measurement.

• Network triggered GNSS measurement.

Agreement

Support eNB to at least aperiodically trigger UE to make GNSS measurement.

Agreement

If eNB aperiodically triggers UE to make GNSS measurement, a MAC CE is used.

Agreement

For GNSS measurement in RRC connected, if eNB aperiodically triggers connected UE to make GNSS measurement, UE can re-acquire GNSS position fix with a gap

• FFS details of gap configuration

Agreement

The UE may re-acquire GNSS autonomously (when configured by the network) if UE does not receive eNB trigger to make GNSS measurement

• FFS based on configured timing

Agreement

On when the GNSS measurement gap starts, which is aperiodically triggered by eNB with MAC CE, RAN1 can down select one of the following alternatives:

• Alt 1: the start time should be at n+ X, where n is the end of MAC CE receiving subframe/slot o FFS: details of X, e.g. predefined value or configured value

Alt 2: the start time should be based on the current GNSS validity duration with delay or without delay

Agreement

On the length of GNSS measurement gap, which is aperiodically triggered by eNB, the gap duration should be equal to or larger than the latest UE reported GNSS position fix time duration. FFS: whether the gap duration is configured by eNB, or the gap duration is equal to the latest reported GNSS position fix time duration.

Aperiodic triggering of GNSS measurement

We think that it falls within RAN2 domain to adjudge the merits of using MAC CE and/or RRC signalling for triggering GNSS measurement. RAN1 has already agreed on using a MAC CE for triggering GNSS measurement. For example, a MAC CE that triggers the UE to do GNSS measurements means the UE will stop transmitting PUCCH/PUSCH and stop receiving PDCCH/PDSCH to instead make a GNSS measurement. This is a major security risk, if an attacker sends this triggering MAC CE - the UE will stop communicating and disappear from the network’s point of view.

Observation 2 Using MAC CE to trigger UEs to acquire GNSS position fix carries a major security risk.

Therefore, we should also allow RRC signalling to trigger the UE to start GNSS position acquisition for security reasons - which will also increase the reliability of the signalling with only minor addition in delay compared to a MAC CE. Using RRC also has the benefit that when the report is ready to be transmitted, an SR/BSR will be triggered in case the UE has no grant available - which would be an issue if the UE only reports via MAC CE.

Observation 3 Using RRC for reporting the GNSS validity duration and GNSS position fix time duration will trigger SR/BSR when reports are ready while a MAC CE will not trigger SR/BSR. Further RRC is more secure and can reuse the existing gnss- validityDuration IE for the report.

We think that RAN1 should also agree on supporting RRC signalling to facilitate an unbiased technical discussion in RAN2. Otherwise, RAN2 discussion is rendered ineffective due to RAN1 agreement on a topic which falls within RAN2 expertise. Therefore, we propose the following: Proposal 5 If eNB aperiodically triggers UE to make GNSS measurement, RRC signalling is used.

GNSS measurement trigger time

RAN1 has listed two alternatives for GNSS gap trigger time. We think that Alt 1 should be agreed where X can be a configured value. As for Alt 2, we think that once the timer-based mechanism is in place, this will already be supported if no GNSS measurement gap trigger is received by the UE.

Length of GNSS measurement gap

Before accessing the network, the UE will already have a valid GNSS position. If the GNSS position fix is made at least every 4 hours, it will typically correspond to a hot start. As a result, we mainly need to focus on hot start when specifying the possible values for the GNSS gap duration. Nonetheless, due to UE mobility, there might be scenarios where a warm start will be needed. Therefore, we put forth the following proposal.

Proposal 6 Network to configure the GNSS measurement gap duration from the following set of values: {1, 2, 5, X} seconds, where X is FFS.

GNSS measurements during C-DRX

RAN1 has already agreed to support network-triggered GNSS measurements, which can be realized using GNSS measurement gaps. Additionally, it may be possible for a UE to acquire a position fix during the inactive mode of connected mode discontinuous reception (C-DRX). We think that it is more appropriate to hold the discussion related to C-DRX in RAN2.

Proposal 7 The discussion on supporting UE-triggered GNSS measurements during the sleep mode of C-DRX should be left to RAN2.

2.3 GNSS assistance information

In the Rel-18 Wl on loT NTN, RAN1 has made the following agreements for GNSS assistance information.

Agreement

GNSS assistance information that UE reports to eNB at least consists of:

• GNSS position fix time duration for measurement

• GNSS validity duration

Agreement

• FFS details of signalling

• FFS how UE reports GNSS assistance information after eNB trigger and the detailed content

• Note: further discuss whether a UE is expected to handle all eNB triggers Agreement

UE reports GNSS position fix time duration for measurement at least during the initial access stage. which message carries this information is up to RAN2

Agreement

In connected mode, UE may report GNSS validation duration with MAC CE.

Agreement

The following alternatives can be considered to inform eNB the success of GNSS measurement at UE side after GNSS measurement in RRC connected.

• Alt-1 : The UE will report the new GNSS validity duration

• Alt-2: The reception of any UL transmission from the UE at eNB after the GNSS measurement When a UE reacquires GNSS position fix in connected mode, it should report GNSS assistance information where RAN2 can decide whether to use MAC or RRC for signalling. At least the GNSS validity duration should always be reported after GNSS reacquisition.

Proposal 8 A UE in connected mode shall always report its GNSS validity duration after GNSS reacquisition.

It is essential for the network to know the UE’s latest GNSS validity duration so that it can configure a GNSS measurement gap accordingly. We expect the UE to report its GNSS validity duration after every GNSS position fix regardless of if it changes or not. It is also a simple way to indicate the success of GNSS measurement to the eNB.

Proposal 9 If the eNB receives the GNSS validity duration from the UE, it concludes that the UE’s latest GNSS measurement was successful.

Finally, we also need to discuss the format of reporting the GNSS measurement time duration. Before accessing the network, the UE will already have a valid GNSS position. If the GNSS position fix is made at least every 4 hours, it corresponds to a hot start. As a result, we mainly need to focus on hot start when specifying the format of GNSS measurement time duration for loT NTN. Nonetheless, due to UE mobility, there might be scenarios where a warm start will be needed. Therefore, we put forth the following proposal.

Proposal 10 UE to report its GNSS measurement time duration in connected mode using a 2-bit field from the following set of values: {1, 2, 5, X} seconds, where X is FFS.

We support reporting only a single value for GNSS position fix time duration. Otherwise, if multiple values are reported by the UE, the eNB cannot know which value to use while configuring a GNSS measurement gap for the UE.

Proposal 11 UE reports only one value (from the set of possible values) for the GNSS measurement time duration in RRC connected state.

3 CONCLUSION

Based on the discussion in the previous section we made the following observations:

Observation 3.... Using RRC for reporting the GNSS validity duration and GNSS position fix time duration will trigger SR/BSR when reports are ready while a MAC CE will not trigger SR/BSR. Further RRC is more secure and can reuse the existing gnss-validityDuration IE for the report.

Based on the discussion in the previous sections we propose the following: Proposal 1 eNB to indicate a time duration X to an loT NTN UE in connected mode such that the UE can continue its uplink transmission for a time duration X after GNSS validity duration has expired.

Proposal 2.. Network to optionally indicate UE-specific timing drift parameters to an loT NTN UE in connected mode.

Proposal 3... Upon GNSS position expiry in connected mode, an loT NTN UE to use UE-specific drift information (in addition to common TA parameters) to calculate TA values before receiving the next TA command.

Proposal 5 If eNB aperiodically triggers UE to make GNSS measurement, RRC signalling is used.

Proposal 6.. Network to configure the GNSS measurement gap duration from the following set of values: {1, 2, 5, X} seconds, where X is FFS.

Proposal 7.... The discussion on supporting UE-triggered GNSS measurements during the sleep mode of C-DRX should be left to RAN2.

Proposal 8... A UE in connected mode shall always report its GNSS validity duration after GNSS reacquisition.

Proposal 10. UE to report its GNSS measurement time duration in connected mode using a 2-bit field from the following set of values: {1 , 2, 5, X} seconds, where X is FFS.

The following are Example EMBODIMENTS, according to one or more aspects disclosed herein.

A1. A method performed by a communication device configured for use in a communication network, the method comprising: performing a geopositioning measurement during a geopositioning measurement gap triggered by expiration of a validity duration for which a geopositioning fix or timing advance of the communication device is valid; and obtaining a geopositioning fix of the communication device using a result of the geopositioning measurement.

A2. The method of embodiment A1 , further comprising determining that the geopositioning measurement gap is triggered, based on a rule or configuration specifying that, each time a validity duration for which a geopositioning fix or timing advance of the communication device expires, a geopositioning measurement gap is triggered by expiration of that validity duration. A3. The method of embodiment A2, wherein the communication device is preconfigured with the rule or configuration.

A4. The method of embodiment A2, further comprising receiving the rule or configuration from a communication network.

A5. The method of any of embodiments A1-A4, wherein, each time a validity duration for which a geopositioning fix or timing advance of the communication device expires, a geopositioning measurement gap is triggered by expiration of that validity duration.

A6. The method of any of embodiments A1-A5, wherein the geopositioning measurement gap is a periodic geopositioning measurement gap that recurs periodically each time a validity duration for which a geopositioning fix or timing advance of the communication device expires. A7. The method of any of embodiments A1-A5, wherein the geopositioning measurement gap is a periodic geopositioning measurement gap that recurs periodically a number of times, wherein the method further comprises receiving signaling indicating the number of times from the communication network.

A8. The method of any of embodiments A1-A7, further comprising determining when the geopositioning measurement gap occurs, based on when the validity duration expires.

A9. The method of embodiment A8, wherein determining when the geopositioning measurement gap occurs comprises determining when a reference point of the geopositioning measurement gap occurs, as a function of when the validity duration expires.

A10. The method of embodiment A9, wherein the reference point of the geopositioning measurement gap is a start time or an end time of the geopositioning measurement gap.

A11. The method of embodiment A9, wherein the reference point of the geopositioning measurement gap is a middle of the geopositioning measurement gap.

A12. The method of any of embodiments A9-A11, further comprising receiving, from the communication network, signaling indicating which reference point of the geopositioning measurement gap, out of multiple possible reference points of the geopositioning measurement gap, the communication device is to determine as a function of when the validity duration expires.

A13. The method of any of embodiments A9-A12, wherein determining when the reference point of the geopositioning measurement gap occurs comprises: determining an expiration time as a time at which the validity duration expires; and determining the reference point by offsetting the expiration time by an offset.

A14. The method of embodiment A13, further comprising receiving, from the communication network, signaling indicating the offset.

A15. The method of any of embodiments A13-A14, wherein the offset indicates how long before the expiration time, or how long after the expiration time, the reference point occurs. A16. The method of any of embodiments A13-A15, further comprising receiving, from the communication network, signaling indicating whether the offset indicates how long before the expiration time the reference point occurs or indicates how long after the expiration time the reference point occurs.

A17. The method of any of embodiments A1-A16, further comprising receiving, from the communication network, a measurement gap configuration that configures the geopositioning measurement gap.

A18. The method of embodiment A17, wherein the measurement gap configuration configures whether or not the geopositioning measurement gap is triggered by expiration of a validity duration for which a geopositioning fix or timing advance of the communication device is valid. A19. The method of embodiment A17, wherein the measurement gap configuration configures timing of the geopositioning measurement gap as a function of timing of expiration of the validity duration.

A20. The method any of embodiments A17-A19, wherein the measurement gap configuration includes a gap start offset time indicating an offset between a time when the measurement gap starts and a time when the validity duration expires.

A21. The method of any of embodiments A17-A20, wherein the measurement gap configuration includes a validity time duration indicating a duration of time during which the measurement gap configuration is valid.

A22. The method of any of embodiments A1-A21, wherein the geopositioning measurement gap is triggered by expiration of a validity duration for which a geopositioning fix of the communication device is valid.

A23. The method of any of embodiments A1-A21, further comprising receiving, from the communication network, signaling indicating that an initial validity duration for which a geopositioning fix of the communication device is valid is to be extended, and wherein the geopositioning measurement gap is triggered by expiration of the extended validity duration. A24. The method of any of embodiments A1-A21, wherein the geopositioning measurement gap is triggered by expiration of a validity duration for which a timing advance of the communication device is valid.

A25. The method of any of embodiments A1-A21, wherein the geopositioning measurement gap is triggered by expiration of a timing advance validity duration for which a timing advance of the communication device is valid, wherein the timing advance validity duration expires after a geopositioning fix validity duration for which a geopositioning fix of the communication device is valid expires.

A26. The method of any of embodiments A1-A25, further comprising receiving, from the communication network, signaling indicating that, or whether, expiration of a validity duration for which a geopositioning fix or timing advance of the communication device is valid triggers a geopositioning measurement gap.

A27. The method of any of embodiments A1-A26, further comprising reporting, to the communication network, the validity duration as defined from a reference time, wherein the reference time is a reference point of a measurement gap during which a geopositioning measurement was last performed.

A28. The method of embodiment A27, wherein the reference point is: a start time or an end time of the measurement gap during which a geopositioning measurement was last performed; or an offset from a start time or an end time of the measurement gap during which a geopositioning measurement was last performed.

A29. The method of any of embodiments A1-A28, further comprising reporting, to the communication network, an absolute time of expiration of the validity duration.

A30. The method of embodiment A29, wherein the absolute time is a Universal Time Coordinated, UTC, value at which the validity duration expired.

A31. The method of any of embodiments A1-A30, further comprising accessing the communication network using the obtained geopositioning fix.

A32. The method of any of embodiments A1-A31, further comprising: determining a precompensation timing advance from the geopositioning fix; and performing a random access channel transmission using the determined pre-com pensation timing advance as part of accessing the communication network.

A33. The method of any of embodiments A1-A32, wherein the communication network is a non-terrestrial network, NTN.

AA1. A method performed by a communication device configured for use in a communication network the method comprising: determining when a geopositioning measurement gap for the communication device occurs based on when a validity duration for which a geopositioning fix or timing advance of the communication device is valid expires; performing a geopositioning measurement when the geopositioning measurement gap occurs; and updating the geopositioning fix of the communication device using a result of the geopositioning measurement.

AA2. The method of embodiment AA1, wherein determining when the geopositioning measurement gap occurs comprises determining when the geopositioning measurement gap starts, based on when the validity duration expires.

AAA1. A method performed by a communication device configured for use in a communication network, the method comprising: receiving, from the communication network, signaling that configures or activates triggering of a geopositioning measurement gap by expiration of a validity duration for which a geopositioning fix or timing advance of the communication device is valid. AAA2. The method of embodiment AAA1, wherein, according to the signaling, each time a validity duration for which a geopositioning fix or timing advance of the communication device expires, a geopositioning measurement gap is triggered by expiration of that validity duration. AAA3. The method of any of embodiments AAA1-AAA2, wherein, according to the signaling, the geopositioning measurement gap is a periodic geopositioning measurement gap that recurs periodically each time a validity duration for which a geopositioning fix or timing advance of the communication device expires.

AAA4. The method of any of embodiments AAA1-AAA3, wherein, according to the signaling, the geopositioning measurement gap is a periodic geopositioning measurement gap that recurs periodically a number of times, wherein the signaling indicates the number of times.

AAA5. The method of any of embodiments AAA1-AAA4, wherein the signaling configures how the communication device is to determine when the geopositioning measurement gap occurs as a function of when the validity duration expires.

AAA6. The method of any of embodiments AAA1-AAA5, wherein the signaling configures a start time or an end time of the geopositioning measurement gap as a function of when the validity duration expires.

AAA7. The method of any of embodiments AAA1-AAA6, wherein the signaling configures: which reference point of the geopositioning measurement gap, out of multiple possible reference points, is to be defined as a function of when the validity duration expires; and/or an offset between a reference point of the geopositioning measurement gap and an expiration time at which the validity duration expires, wherein the offset indicates how long before the expiration time, or how long after the expiration time, the reference point occurs.

AAA8. The method of any of embodiments AAA1-AAA7, wherein the signaling configures whether or not a geopositioning measurement gap is to be triggered by expiration of a validity duration that has been extended.

AAA9. The method of any of embodiments AAA1-AAA8, wherein the signaling configures whether or not a geopositioning measurement gap is to be triggered by expiration of a timing advance validity duration for which a timing advance of the communication device is valid, which has expired after expiration of a geopositioning fix validity duration for which a geopositioning fix of the communication device is valid.

AAA10. The method of any of embodiments AAA1-AAA9, further comprising: performing a geopositioning measurement during a geopositioning measurement gap triggered, according to the signaling, by expiration of a validity duration for which a geopositioning fix or timing advance of the communication device is valid; and obtaining a geopositioning fix of the communication device using a result of the geopositioning measurement. AAA11. The method of embodiment AAA10, further comprising accessing the communication network using the obtained geopositioning fix.

AAA12. The method of any of embodiments AAA10-AAA11 , further comprising: determining a pre-compensation timing advance from the geopositioning fix; and performing a random access channel transmission using the determined pre-compensation timing advance as part of accessing the communication network.

AAA13. The method of any of embodiments AAA1-AAA12, wherein the communication network is a non-terrestrial network, NTN.

AAA14. The method of any of embodiments AAA1-AAA13, wherein the signaling is radio resource control signaling or medium access control signaling.

AAAA1. A method performed by a communication device configured for use in a communication network, the method comprising: reporting, to the communication network, a validity duration for which a geopositioning fix of the communication device is valid, as defined from a reference time, wherein the reference time is a reference point of a measurement gap during which a geopositioning measurement was last performed by the communication device. AAAA2. The method of embodiment AAAA1 , wherein the reference point is: a start time or an end time of the measurement gap during which a geopositioning measurement was last performed; or an offset from a start time or an end time of the measurement gap during which a geopositioning measurement was last performed.

AAAAA1. A method performed by a communication device configured for use in a communication network, the method comprising:reporting, to the communication network, an absolute time of expiration of a validity duration for which a geopositioning fix of the communication device is valid.

AAAAA2. The method of embodiment AAAAA1 , wherein the absolute time is a Universal Time Coordinated, UTC, value at which the validity duration expired.

AA. The method of any of Group A Embodiments, wherein the communication device is an Internet of Things, loT, NTN user equipment.

AB. The method of any of Group A Embodiments, wherein the communication device is in radio resource control, RRC, connected state.

AC. The method of any of Group A Embodiments, wherein the geopositioning measurement gap is triggered while the communication device is in resource control, RRC, connected state.

AD. The method of any of Group A Embodiments, wherein the geopositioning measurement is a Global Navigate Satellite System, GNSS, measurement, wherein the geopositioning measurement gap is a GNSS measurement gap, and wherein the geopositioning fix is a GNSS positioning fix.

AE. The method of any of Group A Embodiments, further comprising autonomously determining the validity duration for which a geopositioning fix or timing advance of the communication device is valid.

AF. The method of any of Group A Embodiments, wherein the timing advance is a precompensation timing advance.

AG. The method of any of the previous embodiments, further comprising: providing user data; and forwarding the user data to a host computer via the transmission to a base station. B1. A method performed by a network node in a communication network, the method comprising: determining a geopositioning measurement gap triggered by expiration of a validity duration for which a geopositioning fix or timing advance of a communication device is valid; and restricting scheduling of transmissions to or from the communication device during the geopositioning measurement gap.

B2. The method of embodiment B1 , further comprising determining that the geopositioning measurement gap is triggered, based on a rule or configuration specifying that, each time a validity duration for which a geopositioning fix or timing advance of the communication device expires, a geopositioning measurement gap is triggered by expiration of that validity duration. B3. The method of embodiment B2, wherein the communication device is preconfigured with the rule or configuration.

B4. The method of embodiment B2, further comprising transmitting the rule or configuration to the communication device.

B5. The method of any of embodiments B1-B4, wherein, each time a validity duration for which a geopositioning fix or timing advance of the communication device expires, a geopositioning measurement gap is triggered by expiration of that validity duration.

B6. The method of any of embodiments B1-B5, wherein the geopositioning measurement gap is a periodic geopositioning measurement gap that recurs periodically each time a validity duration for which a geopositioning fix or timing advance of the communication device expires. B7. The method of any of embodiments B1-B5, wherein the geopositioning measurement gap is a periodic geopositioning measurement gap that recurs periodically a number of times, wherein the method further comprises transmitting, to the communication device, signaling indicating the number of times.

B8. The method of any of embodiments B1-B7, further comprising determining when the geopositioning measurement gap occurs, based on when the validity duration expires.

B9. The method of embodiment B8, wherein determining when the geopositioning measurement gap occurs comprises determining when a reference point of the geopositioning measurement gap occurs, as a function of when the validity duration expires.

B10. The method of embodiment B9, wherein the reference point of the geopositioning measurement gap is a start time or an end time of the geopositioning measurement gap.

B11. The method of embodiment B9, wherein the reference point of the geopositioning measurement gap is a middle of the geopositioning measurement gap. B12. The method of any of embodiments B9-B11 , further comprising transmitting, to the communication device, signaling indicating which reference point of the geopositioning measurement gap, out of multiple possible reference points of the geopositioning measurement gap, the communication device is to determine as a function of when the validity duration expires.

B13. The method of any of embodiments B9-B12, wherein determining when the reference point of the geopositioning measurement gap occurs comprises: determining an expiration time as a time at which the validity duration expires; and determining the reference point by offsetting the expiration time by an offset.

B14. The method of embodiment B13, further comprising transmitting, to the communication device, signaling indicating the offset.

B15. The method of any of embodiments B13-B14, wherein the offset indicates how long before the expiration time, or how long after the expiration time, the reference point occurs. B16. The method of any of embodiments B13-B15, further comprising transmitting, to the communication device, signaling indicating whether the offset indicates how long before the expiration time the reference point occurs or indicates how long after the expiration time the reference point occurs.

B17. The method of any of embodiments B1-B16, further comprising transmitting, to the communication device, a measurement gap configuration that configures the geopositioning measurement gap.

B18. The method of embodiment B17, wherein the measurement gap configuration configures whether or not the geopositioning measurement gap is triggered by expiration of a validity duration for which a geopositioning fix or timing advance of the communication device is valid. B19. The method of embodiment B17, wherein the measurement gap configuration configures timing of the geopositioning measurement gap as a function of timing of expiration of the validity duration.

B20. The method any of embodiments B17-B19, wherein the measurement gap configuration includes a gap start offset time indicating an offset between a time when the measurement gap starts and a time when the validity duration expires.

B21. The method of any of embodiments B17-B20, wherein the measurement gap configuration includes a validity time duration indicating a duration of time during which the measurement gap configuration is valid.

B22. The method of any of embodiments B1-B21, wherein the geopositioning measurement gap is triggered by expiration of a validity duration for which a geopositioning fix of the communication device is valid. B23. The method of any of embodiments B1-B21, further comprising transmitting, to the communication device, signaling indicating that an initial validity duration for which a geopositioning fix of the communication device is valid is to be extended, and wherein the geopositioning measurement gap is triggered by expiration of the extended validity duration. B24. The method of any of embodiments B1-B21, wherein the geopositioning measurement gap is triggered by expiration of a validity duration for which a timing advance of the communication device is valid

B25. The method of any of embodiments B1-B21, wherein the geopositioning measurement gap is triggered by expiration of a timing advance validity duration for which a timing advance of the communication device is valid, wherein the timing advance validity duration expires after a geopositioning fix validity duration for which a geopositioning fix of the communication device is valid expires.

B26. The method of any of embodiments B1-B25, further comprising transmitting, to the communication device, signaling indicating that, or whether, expiration of a validity duration for which a geopositioning fix or timing advance of the communication device is valid triggers a geopositioning measurement gap.

B27. The method of any of embodiments B1-B26, further comprising receiving, from the communication device, a report reporting the validity duration as defined from a reference time, wherein the reference time is a reference point of a measurement gap during which a geopositioning measurement was last performed.

B28. The method of embodiment B27, wherein the reference point is: a start time or an end time of the measurement gap during which a geopositioning measurement was last performed; or an offset from a start time or an end time of the measurement gap during which a geopositioning measurement was last performed.

B29. The method of any of embodiments B1-B28, further comprising receiving, from the communication device, a report that reports an absolute time of expiration of the validity duration.

B30. The method of embodiment B29, wherein the absolute time is a Universal Time Coordinated, UTC, value at which the validity duration expired.

B31. The method of any of embodiments B1-B30, wherein the communication network is a non-terrestrial network, NTN.

BB1. A method performed by a network node configured for use in a communication network, the method comprising: determining when a geopositioning measurement gap for a communication device occurs based on when a validity duration for which a geopositioning fix or timing advance of the communication device is valid expires; and restricting scheduling of transmissions to or from the communication device during the geopositioning measurement gap. BB2. The method of embodiment BB1 , wherein determining when the geopositioning measurement gap occurs comprises determining when the geopositioning measurement gap starts, based on when the validity duration expires.

BBB1. A method performed by a network node configured for use in a communication network, the method comprising: transmitting, to a communication device, signaling that configures or activates triggering of a geopositioning measurement gap by expiration of a validity duration for which a geopositioning fix or timing advance of the communication device is valid.

BBB2. The method of embodiment BB1 , wherein, according to the signaling, each time a validity duration for which a geopositioning fix or timing advance of the communication device expires, a geopositioning measurement gap is triggered by expiration of that validity duration. BBB3. The method of any of embodiments BBB1-BBB2, wherein, according to the signaling, the geopositioning measurement gap is a periodic geopositioning measurement gap that recurs periodically each time a validity duration for which a geopositioning fix or timing advance of the communication device expires.

BBB4. The method of any of embodiments BBB1-BBB3, wherein, according to the signaling, the geopositioning measurement gap is a periodic geopositioning measurement gap that recurs periodically a number of times, wherein the signaling indicates the number of times.

BBB5. The method of any of embodiments BBB1-BBB4, wherein the signaling configures how the communication device is to determine when the geopositioning measurement gap occurs as a function of when the validity duration expires.

BBB6. The method of any of embodiments BBB1-BBB5, wherein the signaling configures a start time or an end time of the geopositioning measurement gap as a function of when the validity duration expires.

BBB7. The method of any of embodiments BBB1-BBB6, wherein the signaling configures: which reference point of the geopositioning measurement gap, out of multiple possible reference points, is to be defined as a function of when the validity duration expires; and/or an offset between a reference point of the geopositioning measurement gap and an expiration time at which the validity duration expires, wherein the offset indicates how long before the expiration time, or how long after the expiration time, the reference point occurs.

BBB8. The method of any of embodiments BBB1-BBB7, wherein the signaling configures whether or not a geopositioning measurement gap is to be triggered by expiration of a validity duration that has been extended.

BBB9. The method of any of embodiments BBB1-BBB8, wherein the signaling configures whether or not a geopositioning measurement gap is to be triggered by expiration of a timing advance validity duration for which a timing advance of the communication device is valid, which has expired after a expiration of a geopositioning fix validity duration for which a geopositioning fix of the communication device is valid.

BBB10. The method of any of embodiments BBB1-BBB9, wherein the communication network is a non-terrestrial network, NTN.

BBB11. The method of any of embodiments BBB1-BBB10, wherein the signaling is radio resource control signaling or medium access control signaling.

BBBB1. A method performed by a network node configured for use in a communication network, the method comprising: receiving, from a communication device, a report that reports a validity duration for which a geopositioning fix of the communication device is valid, as defined from a reference time, wherein the reference time is a reference point of a measurement gap during which a geopositioning measurement was last performed by the communication device. BBBB2. The method of embodiment BBBB1 , wherein the reference point is: a start time or an end time of the measurement gap during which a geopositioning measurement was last performed; or an offset from a start time or an end time of the measurement gap during which a geopositioning measurement was last performed.

BBBBB1. A method performed by a network node configured for use in a communication network, the method comprising: receiving, from a communication device, a report that reports an absolute time of expiration of a validity duration for which a geopositioning fix of the communication device is valid.

BBBBB2. The method of embodiment BBBBB1 , wherein the absolute time is a Universal Time Coordinated, UTC, value at which the validity duration expired.

BA. The method of any of Group B Embodiments, wherein the communication device is an Internet of Things, loT, NTN user equipment.

BB. The method of any of Group B Embodiments, wherein the communication device is in radio resource control, RRC, connected state.

BC. The method of any of Group B Embodiments, wherein the geopositioning measurement gap is triggered while the communication device is in resource control, RRC, connected state.

BD. The method of any of Group B Embodiments, wherein the geopositioning measurement is a Global Navigate Satellite System, GNSS, measurement, wherein the geopositioning measurement gap is a GNSS measurement gap, and wherein the geopositioning fix is a GNSS positioning fix.

BE. The method of any of Group B Embodiments, wherein the communication device is configured to autonomously determine the validity duration for which a geopositioning fix or timing advance of the communication device is valid.

BF. The method of any of Group B Embodiments, wherein the timing advance is a precompensation timing advance.

BG. The method of any of the previous embodiments, further comprising: obtaining user data; and forwarding the user data to a host computer or a communication device. C1. A communication device configured to perform the method of any of the Group A embodiments.

02. A communication device comprising processing circuitry configured to perform the method of any of the Group A embodiments.

03. A communication device comprising: communication circuitry; and processing circuitry configured to perform the method of any of the Group A embodiments.

04. A communication device comprising: processing circuitry configured to perform the method of any of the Group A embodiments; and power supply circuitry configured to supply power to the communication device.

05. A communication device comprising: processing circuitry and memory, the memory containing instructions executable by the processing circuitry whereby the communication device is configured to perform the method of any of the Group A embodiments.

06. The communication device of any of embodiments 01-05, wherein the communication device is a wireless communication device.

07. A user equipment (UE) comprising: an antenna configured to send and receive wireless signals; radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; the processing circuitry being configured to perform the method of any of the Group A embodiments; an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the UE.

08. A computer program comprising instructions which, when executed by at least one processor of a communication device, causes the communication device to perform the method of any of the Group A embodiments.

09. A carrier containing the computer program of embodiment 07, wherein the carrier is one of an electronic signal, optical signal, radio signal, or computer readable storage medium.

010. A network node configured to perform the method of any of the Group B embodiments. 011. A network node comprising processing circuitry configured to perform the method of any of the Group B embodiments.

012. A network node comprising: communication circuitry; and processing circuitry configured to perform the method of any of the Group B embodiments.

013. A network node comprising: processing circuitry configured to perform the method of any of the Group B embodiments; power supply circuitry configured to supply power to the network node. C14. A network node comprising: processing circuitry and memory, the memory containing instructions executable by the processing circuitry whereby the network node is configured to perform the method of any of the Group B embodiments. C15. The network node of any of embodiments C10-C14, wherein the network node is a base station.

C16. A computer program comprising instructions which, when executed by at least one processor of a network node, causes the network node to perform the method of any of the Group B embodiments. C17. The computer program of embodiment C16, wherein the network node is a base station.

C18. A carrier containing the computer program of any of embodiments C16-C17, wherein the carrier is one of an electronic signal, optical signal, radio signal, or computer readable storage medium.

Claims

1. A method performed by a communication device (18) configured for use in a communication network (10), the method comprising: performing (400) a geopositioning measurement (38) during a geopositioning measurement gap (50) triggered by expiration of a validity duration (40) for which a geopositioning fix (20) or timing advance of the communication device (18) is valid; and obtaining (405) a geopositioning fix (20) of the communication device (18) using a result of the geopositioning measurement (38).

2. The method of claim 1, further comprising receiving, from the communication network (10), signaling (28) that configures or activates triggering of a geopositioning measurement gap (50) by expiration of a validity duration (40) for which a geopositioning fix (20) or timing advance of the communication device (18) is valid.

3. The method of any of claims 1-2, wherein, each time a validity duration (40) for which a geopositioning fix (20) or timing advance of the communication device (18) expires, a geopositioning measurement gap (50) is triggered by expiration of that validity duration (40).

4. The method of any of claims 1-3, wherein the geopositioning measurement gap (50) is a periodic geopositioning measurement gap (50) that recurs periodically each time a validity duration (40) for which a geopositioning fix (20) or timing advance of the communication device (18) expires.

5. The method of any of claims 1-4, wherein the geopositioning measurement gap (50) is triggered by expiration of a timing advance validity duration (40) for which a timing advance of the communication device (18) is valid, wherein the timing advance validity duration (40) expires after a geopositioning fix validity duration (40) for which a geopositioning fix (20) of the communication device (18) is valid expires.

6. The method of any claims 1-4, further comprising receiving, from the communication network (10), a measurement gap configuration that configures the geopositioning measurement gap (50), wherein the measurement gap configuration includes a gap start offset time indicating an offset (42) between a time when the measurement gap (50) starts and a time when the validity duration (40) expires.

7. The method of any of claims 1-6, wherein the geopositioning measurement gap (50) is triggered to start at a time that is offset (42) from a time when the validity duration (40) expires.

8. The method of any of claims 1-7, wherein the geopositioning measurement gap (50) is triggered by expiration of a validity duration (40) for which a geopositioning fix (20) of the communication device (18) is valid.

9. The method of any of claims 1-8, further comprising receiving, from the communication network (10), signaling (28) indicating that an initial validity duration (40) for which a geopositioning fix (20) of the communication device (18) is valid is to be extended, and wherein the geopositioning measurement gap (50) is triggered by expiration of the extended validity duration (40).

10. The method of any of claims 1-4 and 5-9, wherein the geopositioning measurement gap (50) is triggered by expiration of a validity duration (40) for which a timing advance of the communication device (18) is valid.

11. The method of any of claims 1-10, further comprising reporting, to the communication network (10), the validity duration (40) as defined from a reference time, wherein the reference time is a reference point of a measurement gap (50) during which a geopositioning measurement (38) was last performed, wherein the reference point is: a start time or an end time of the measurement gap (50) during which a geopositioning measurement (38) was last performed; or an offset (42) from a start time or an end time of the measurement gap (50) during which a geopositioning measurement (38) was last performed.

12. The method of any of claims 1-10, further comprising reporting, to the communication network (10), an absolute time of expiration of the validity duration (40).

13. The method of any of claims 1-12, wherein the communication network (10) is a nonterrestrial network, NTN, wherein the geopositioning measurement (38) is a Global Navigate Satellite System, GNSS, measurement, wherein the geopositioning measurement gap (50) is a GNSS measurement gap, and wherein the geopositioning fix (20) is a GNSS positioning fix.

14. The method of any of claims 1-13, wherein the geopositioning measurement gap (50) is triggered while the communication device (18) is in resource control, RRC, connected state.

15. A method performed by a network node (30) in a communication network (10), the method comprising: transmitting (1100), to a communication device (18), signaling (28) that configures or activates triggering of a geopositioning measurement gap (50) by expiration of a validity duration (40) for which a geopositioning fix (20) or timing advance of the communication device (18) is valid; and receiving, from the communication device (18), a report, reporting the validity duration (40).

16. The method of claim 15, wherein, according to the signaling (28), each time a validity duration (40) for which a geopositioning fix (20) or timing advance of the communication device (18) expires, a geopositioning measurement gap (50) is triggered by expiration of that validity duration (40).

17. The method of any of claims 15-16, wherein the geopositioning measurement gap (50) is a periodic geopositioning measurement gap (50) that recurs periodically each time a validity duration (40) for which a geopositioning fix (20) or timing advance of the communication device (18) expires.

18. The method of any of claims 15-17, wherein the signaling (28) comprises a measurement gap configuration that configures the geopositioning measurement gap (50), wherein the measurement gap configuration configures timing of the geopositioning measurement gap (50) as a function of timing of expiration of the validity duration (40).

19. The method any of claim 18, wherein the measurement gap configuration includes a gap start offset time indicating an offset (42) between a time when the measurement gap starts and a time when the validity duration (40) expires.

20. The method of any of claims 15-19, wherein the geopositioning measurement gap (50) is triggered by expiration of a timing advance validity duration (40) for which a timing advance of the communication device (18) is valid, wherein the timing advance validity duration (40) expires after a geopositioning fix validity duration (40) for which a geopositioning fix (20) of the communication device (18) is valid expires.

21. The method of any of claims 15-20, wherein the geopositioning measurement gap (50) is triggered by expiration of a validity duration (40) for which a geopositioning fix (20) of the communication device (18) is valid.

22. The method of any of claims 15-21, wherein the signaling (28) indicates that an initial validity duration (40) for which a geopositioning fix (20) of the communication device (18) is valid is to be extended, and wherein the geopositioning measurement gap (50) is triggered by expiration of the extended validity duration (40).

23. The method of any of claims 15-19, wherein the geopositioning measurement gap (50) is triggered by expiration of a validity duration (40) for which a timing advance of the communication device (18) is valid.

24. The method of any of claims 15-23, wherein the reported validity duration (40) is defined from a reference time, wherein the reference time is a reference point of a measurement gap (50) during which a geopositioning measurement (38) was last performed wherein the reference point is: a start time or an end time of the measurement gap (50) during which a geopositioning measurement (38) was last performed; or an offset (42) from a start time or an end time of the measurement gap (50) during which a geopositioning measurement (38) was last performed.

25. The method of any of claims 15-23, wherein the reported validity duration (40) is an absolute time of expiration of the validity duration (40).

26. The method of any of claims 15-25, wherein the communication network (10) is a nonterrestrial network, NTN, wherein the geopositioning measurement (38) is a Global Navigate Satellite System, GNSS, measurement, wherein the geopositioning measurement gap (50) is a GNSS measurement gap, and wherein the geopositioning fix (20) is a GNSS positioning fix.

27. A communication device (18) configured for use in a communication network (10), the communication device (18) configured to: perform a geopositioning measurement (38) during a geopositioning measurement gap (50) triggered by expiration of a validity duration (40) for which a geopositioning fix (20) or timing advance of the communication device (18) is valid; and obtain a geopositioning fix (20) of the communication device (18) using a result of the geopositioning measurement (38).

28. The communication device (18) of claim 27, configured to perform the method of any of claims 2-14.

29. A network node (30) configured for use in a communication network (10), the network node (30) configured to: transmit, to a communication device (18), signaling (28) that configures or activates triggering of a geopositioning measurement gap (50) by expiration of a validity duration (40) for which a geopositioning fix (20) or timing advance of the communication device (18) is valid; and receive, from the communication device (18), a report reporting the validity duration (40).

30. The network node (30) of claim 29, configured to perform the method of any of claims 16- 26.

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

32. A computer program comprising instructions which, when executed by at least one processor of a network node (30), causes the network node (30) to perform the method of any of claims 15-26.

33. A carrier containing the computer program of any of claims 31-32, wherein the carrier is one of an electronic signal, optical signal, radio signal, or computer readable storage medium.