Methods for performing global navigation satellite system measurements and for facilitating global navigation satellite system measurements, user equipment, and network node

Description

62 METHODS FOR PERFORMING GLOBAL NAVIGATION SATELLITE SYSTEM MEASUREMENTS AND FOR FACILITATING GLOBAL NAVIGATION SATELLITE SYSTEM MEASUREMENTS, USER EQUIPMENT, AND NETWORK NODE FIELD OF TECHNIQUE

[001] The present description relates generally to wireless communications and, more particularly, to techniques for performing positioning measurements by a user's equipment during operation on a non-terrestrial network (NTN). FUNDAMENTALS

[002] There is an ongoing resurgence of satellite communications. Several plans for satellite networks have been announced in recent years. Satellite networks could complement mobile networks on the ground by providing connectivity to underserved areas and multicast / broadcast services.

[003] To take advantage of the strong mobile ecosystem and economies of scale, the adaptation of terrestrial wireless access technologies, including LTE and NR radio access technologies, to satellite networks is attracting significant interest, which has been reflected in the 3rd Generation Partnership Project (3GPP) standardization work.

[004] In Version 15, 3GPP began work to prepare NR for operation on a Non-Terrestrial Network (NTN). This work was carried out within the study item “Non-Terrestrial Networks” and resulted in 3GPP TR 38.811 V15.4.0. In Version 16, work to prepare NR for operation on an NTN network continued with the study item “Solutions for NR to support Non-Terrestrial Network”.

[005] A satellite network or satellite-based mobile network may also be called a non-terrestrial network (NTN). In contrast, a mobile network with base stations in the group may be referred to as a network Petition 870250111433, dated 04 / 12 / 2025, p. 6 / 153 / 62 terrestrial (TN) or non-NTN network. A satellite within the NTN may be referred to as an NTN node, NTN satellite, satellite node, or simply a satellite.

[006] A satellite radio access network typically includes the following components: • a satellite, which refers to a space platform.

[007] • A terrestrial connection port that connects the satellite to a base station or a main network, depending on the chosen architecture. This may be referred to as a “sat-gateway.”

[008] • A feeder link, which is the link between a connection port and a satellite.

[009] • An access link, or service link, which is the link between a satellite and a UE.

[0010] A satellite (or UAS platform) can implement a transparent or regenerative payload (with onboard processing). A transparent payload architecture, which may also be referred to as a “curved tube” architecture, means that only radio frequency filtering, frequency conversion, and amplification are performed on the signals traversing the satellite on their way to and from the terminal equipment and network equipment on the ground. Consequently, the waveform signal repeated by the payload is unaltered. When applied to the 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.

[0011] With a regenerative payload, radio frequency filtering, frequency conversion and amplification, as well as demodulation / decoding, switching and / or routing, encoding / modulation are performed by the satellite. This is effectively equivalent to having all or part of the functions of a base station (e.g., Petition 870250111433, dated 04 / 12 / 2025, p. 7 / 153 / 62 gNB) on board the satellite (or UAS platform).

[0012] In the work item for NR NTN in 3GPP version 17, only the transparent payload architecture is considered.

[0013] Depending on its orbital altitude, a satellite can be categorized as a low Earth orbit (LEO), medium Earth orbit (MEO), or geostationary Earth orbit (GEO) satellite: • LEO: typical altitudes in the range of 250 - 1,500 km, with orbital periods in the range of 90 - 120 minutes.

[0014] · MEO: typical altitudes in the range of 5,000 - 25,000 km, with orbital periods in the range of 3 - 15 hours.

[0015] · GEO: altitude of approximately 35,786 km, with an orbital period of 24 hours.

[0016] A satellite that does not operate in geostationary Earth orbit is also commonly called a Non-Geostationary Orbit (NGSO) satellite. MEO satellites and LEO satellites are NGSO satellites.

[0017] There may be different types of satellites or Unmanned Aerial System (UAS) platforms in any given NTN. Exemplary characteristics of various satellites and UAS platforms are illustrated in Table 1. Platforms Altitude Range Orbit Typical Beam Footprint Size Low Earth Orbit (LEO) Satellite 300 - 1500 km Circular around the Earth 100 - 1000 km Medium Earth Orbit (MEO) Satellite 7000 - 25000 km 100 - 1000 km Geostationary Earth Orbit (GEO) Satellite 35786 km Theoretical station maintains a fixed position in terms of elevation / azimuth relative to a specific terrestrial point. 200 - 3500 km UAS platform (including HAPS) 8 - 50 km (20 km for HAPS) 5 - 200 km High Elliptical Orbit (HEO) Satellite 400 - 50000 km Elliptical around the Earth 200 - 3500 km Table 1

[0018] A geosynchronous Earth orbit (GEO) satellite in an NTN is fed by one or more sat-gateways that are deployed across the coverage targeted by the satellite (e.g., regional coverage or Petition 870250111433, dated 04 / 12 / 2025, p. 8 / 153 / 62 (to continental). A non-GEO satellite in an NTN is successfully served by one or more sat-gateways at once. The system ensures feeder link and service continuity between successive service satgateways with sufficient duration to proceed with docking and transfer between mobility cells. A wireless device, or “UE”, in a given cell is served by only one satgateway.

[0019] Significant orbital altitude means that satellite systems are distinguished by a path loss that is significantly higher than what is expected in terrestrial networks. To overcome path loss, it is often required that access links and feeders be operated under line-of-sight conditions and that the UE be equipped with an antenna that offers high beam directivity.

[0020] Figure 1 shows an exemplary architecture of a satellite network with curved tube transponders. The gNB, illustrated simply as a base station (BS) in Figure 1, can be integrated into the connection port or connected to the connection port via a terrestrial connection (wire, fiber optic, wireless link). As seen in Figure 1, a communication satellite can generate multiple beams over a given area. The footprint of a beam is usually in an elliptical shape, which has traditionally been considered a cell. The footprint of a beam is also frequently referred to as a directed beam. The directed beam can move across the Earth's surface with the satellite's movement or can be fixed to the Earth with some beam pointing mechanism used by the satellite to compensate for its movement.The first is referred to as a mobile cell (or mobile beam) deployment scenario, while the latter is referred to as a near-fixed-on-Earth cell (or near-fixed-on-Earth beam) deployment scenario. The size of a directed beam depends on the system design, which may be situated in... Petition 870250111433, dated 04 / 12 / 2025, page 9 / 153 / 62 range from tens of kilometers to several thousand kilometers.

[0021] As noted above, in the work item for NR NTN in 3GPP version 17, only the transparent payload architecture is considered, for example, as illustrated in Figure 2. This figure illustrates a networked RAN architecture with a transparent satellite that effectively relays communications between a 5G base station (gNB) and the UE.

[0022] Compared to beams observed in a terrestrial network, an NTN beam can be very wide and cover an area outside the area defined by the served cell. Beams covering adjacent cells will overlap and cause significant levels of intercell interference. To overcome the large levels of interference, a typical approach is for the NTN to configure different cells with different carrier frequencies and polarization modes.

[0023] In a LEO or MEO communication system, a large number of satellites deployed in a range of orbits is required to provide continuous coverage across the globe. Launching a very large satellite constellation is both an expensive and time-consuming procedure. Therefore, it is expected that all LEO and MEO satellite constellations will for some time provide only partial terrestrial coverage. In the case of some constellations dedicated to massive IoT services with relaxed latency requirements, it may not even be necessary to support complete terrestrial coverage. It may be sufficient to provide occasional or periodic coverage according to the constellation's orbital period.

[0024] Propagation delay is an important aspect of satellite communications that differs from the expected delay in a terrestrial mobile system. For a curved tube satellite network, the round-trip delay can, depending on the orbital altitude, range from tens of milliseconds (ms) for LEO satellites to several hundred milliseconds for GEO satellites. As a comparison, the round-trip and Petition 870250111433, dated 04 / 12 / 2025, page 10 / 153 6 / 62 rounds on terrestrial cellular networks are typically below 1 ms.

[0025] The distance between the UE and a satellite can vary significantly depending on the satellite's position and thus the elevation angle ε seen by the UE. Considering circular orbits, the minimum distance is achieved when the satellite is directly above the UE (ε = 90°), and the maximum distance when the satellite is at the lowest possible elevation angle. Table 2 shows the distances between satellite and UE for different orbital altitudes and elevation angles along with the one-way propagation delay and the maximum propagation delay difference (the propagation delay difference at ε = 90°). Note that this table considers a regenerative payload architecture. For the transparent payload case, the propagation delay between the connection port and the satellite also needs to be considered, unless the base station is corrected for this. Orbital altitude Elevation angle Distance UE <-> satellite One-way propagation delay Propagation delay difference 600 km 90° 600 km 2.0 ms ___ 30° 1075 km 3.6 ms 1.6 ms 10° 1932 km 6.4 ms 4.4 ms 1200 km 90° 1200 km 4.0 ms — 30° 1999 km 6.7 ms 2.7 ms 10° 3131 km 10.4 ms 6.4 ms 35786 km 90° 35786 km 119.4 ms ___ 30° 38609 km 128.8 ms 9.4 ms 10° 40581 km 135.4 ms 16.0 ms Table 2

[0026] Propagation delay can also be highly variable due to the high speed of satellites in LEO and MEO, and can change on the order of 10 to 100 ps per second, depending on orbital altitude and satellite speed.

[0027] In 3GPP TR 38.821, which is a technical report by 3GPP describing “Solutions for NR to Support Non-Terrestrial Networks (NTN)”, it was provided that ephemeris data should be supplied to the UE, for example, to assist with pointing a directional antenna (or antenna beam) towards the satellite. A UE that knows its own position, for example, thanks to GNSS support, can also use the data from Petition 870250111433, dated 04 / 12 / 2025, page 11 / 153 / 62 ephemerides to calculate correct timing-related parameters, such as Timing Advance (TA) and / or to consider frequency deviations, for example, Doppler shift. The content of ephemeris data and the procedures for providing and updating this data have not yet been studied in detail.

[0028] A satellite orbit can be completely described using 6 parameters. The exact set of parameters to be used can be decided by the user; many different representations are possible. For example, a choice of parameters frequently used in astronomy is the set (a, ε, i, Ω, ω, t). Here, the semimajor geometric axis a and the eccentricity ε describe the shape and size of the orbital ellipse; the inclination i, the right ascension of the ascending node Ω, and the argument of periastron ω determine its position in space, and the epoch t determines a reference time (e.g., the time when the satellites pass through periastron). This set of parameters is illustrated in Figure 3.

[0029] A two-line element set (TLE) is a data format that encodes a list of orbital elements of an object orbiting Earth for a given point in time, the epoch. As an example of a different parameterization, TLEs use mean motion ne mean anomaly M instead of the semimajor geometric axis aeo reference time t.

[0030] A completely different set of parameters is the position and velocity vector (x, y, z, vx, vy, vz) of a satellite. These are sometimes called orbital state vectors. They can be derived from orbital elements and vice versa since the information they contain is equivalent. All these formulations (and many others) are possible choices for the ephemeris data format to be used in NTN.

[0031] Additionally, ephemeris data can be Petition 870250111433, dated 04 / 12 / 2025, page 12 / 153 / 62 accompanied by information on possible coverage area, or timing information when the satellite is going to serve a certain geographic area on Earth.

[0032] To handle timing and frequency synchronization in an NR-based or LTE-based NTN, the end-user device, or UE, is equipped with a Global Navigation Satellite System (GNSS) receiver. The GNSS receiver allows a device to estimate its geographic position. The UE can then determine the propagation delay, delay variance, Doppler shift, and its rate of change based on its own location and satellite location information.

[0033] In the 3GPP Version 17 study item on NB-IoT and LTE M for NTN and the work items Rel-17 and Rel-18 on IoT NTN, the simultaneous operation of NB-IoT / eMTC and GNSS is not considered.

[0034] The 3GPP premise assumes that a cellular device can share parts of its radio frequency architecture between the cellular modem and the GNSS chip. A basic solution is to use the same antenna to receive the GNSS reference signal and to receive and transmit an LTE or NR signal. A switch determines whether the antenna should be connected to the cellular RF front end or the GNSS RF front end. The switch provides the necessary isolation between the cellular transmitter and the GNSS receiver, but also prevents simultaneous GNSS and cellular operation.

[0035] A 3GPP device in the RRC_IDLE or RRC_INACTIVE states needs to perform several procedures, including measurements for mobility purposes, paging monitoring, recording measurement results, updating the tracking area, and searching for a new PLMN, among others. These procedures will consume power on devices, and a general trend in 3GPP has been to allow the Petition 870250111433, dated 04 / 12 / 2025, page 13 / 153 / 62, requesting flexibility in these procedures to extend device battery life. This trend has been particularly pronounced for IoT devices supporting reduced capabilities (redcap), NB-IoT, and LTE-M.

[0036] In 3GPP TR 36.763, which documents a “Study on NarrowBand Internet of Things (IoT) / enhanced Machine Type Communication (eMTC) Support for Non-Terrestrial Networks (NTN)”, the impact of fixed GNSS position on the battery life of an IoT NTN UE is described. Furthermore, several aspects related to GNSS operation, for example, GNSS measurement intervals, were also studied and documented in this report.

[0037] The GPP reached several agreements related to GNSS improvements at the 3GPP RAN1 meetings during the IoT NTN Work Item (WI) of Rel-17. In this WI, a GNSS validity duration parameter was introduced. Upon GNSS acquisition, a UE will autonomously determine its GNSS validity duration from the agreed set of values ​​and report it to the network. After the GNSS validity period expires while in the RRC_CONNECTED state, a UE is expected to return to idle mode to update its GNSS status, as GNSS acquisition while connected mode is not supported / required by existing standards. The relevant agreements include: Agreement: For sporadic short transmissions, the UE in RRC_CONNECTED should return to idle mode and reacquire a GNSS position if the GNSS signal becomes outdated.

[0038] Agreement: The UE autonomously determines its GNSS validity period X and reports the information associated with that validity period to the network via RRC signaling. Petition 870250111433, dated 04 / 12 / 2025, page 14 / 153 / 62

[0039] ·

[0040] In the NTN IoT WI Rel-18, the focus is on long connections where GNSS expires during connected mode. Instead of following the standard Rel-17 procedure, where an UE in RRC_CONNECTED mode returns to RRC_IDLE mode after GNSS expiration, an enhanced UE behavior is being discussed, in which the UE is allowed to reacquire its GNSS position during the RRC_CONNECTED state. Additionally, another objective is to reduce the number of fixed GNSS positions a UE may need during RRC_CONNECTED mode in order to reduce UE power consumption.

[0041] The agreements in the IoT NTN Rel-18 WI related to closed-loop time and frequency correction include: Agreement Closed-loop time and frequency correction, with potential enhancements, for IoT-NTN is considered a way to reduce the need for the UE to update the GNSS position in long-duration connections.

[0042] Agreement

[0043] At least in cases where the frequency error is within the frequency error requirements, study the mechanisms and conditions to allow UL transmission after the expiration of the original GNSS validity, without the need for new GNSS acquisition for a given period.

[0044] • FFS: with legacy closed-loop time correction or enhanced closed-loop time correction.

[0045] • This mechanism is enabled / configured by eNB

[0046] FFS: whether such a mechanism will be specified depends on the outcome of this study. Petition 870250111433, dated 04 / 12 / 2025, page 15 / 153 / 62

[0047] Agreements related to fixed GNSS position in RRC_Connected state include: Agreement At least the following options can be considered in connected GNSS measurement for potential enhancements to improved GNSS operations: • Option 1: UE regains fixed GNSS position during the RLF procedure • Option 2: UE regains fixed GNSS position with a new interval

[0048] Note: this does not imply that an NTN Rel-18 IoT UE is required to support one or both options.

[0049] Agreement

[0050] Further study on whether there is a need for possible improvements regarding the following for long connection time.

[0051] • GNSS measurement triggered by EU.

[0052] • GNSS measurement triggered by network.

[0053] Agreement

[0054] eNB support to trigger at least aperiodically UE to perform GNSS measurement.

[0055] Agreement

[0056] If eNB periodically triggers the UE to perform GNSS measurement, a MAC CE is used.

[0057] Agreement

[0058] For GNSS measurement in connected RRC, if eNB triggers a periodic UE connected to perform GNSS measurement, UE can reacquire a fixed GNSS position with an interval

[0059] • FFS interval configuration details

[0060] Agreement Petition 870250111433, dated 04 / 12 / 2025, page 16 / 153 n / 62

[0061] The UE can autonomously reacquire GNSS (when configured by the network) if the UE does not receive an eNB trigger to perform GNSS measurement.

[0062] · FFS based on configured timing

[0063] Agreement

[0064] When the GNSS measurement interval starts, which is triggered aperiodically by the eNB with MAC CE, RAN1 can select one of the following alternatives: Alt 1: the start time must be n + X, where n is the end of CE of MAC receiving subframe / slot. FFS: details of X, for example, default value or configured value. Alt 2: the start time must be based on the validity period of the current GNSS with or without delay

[0065] Agreement

[0066] Regarding the GNSS measurement interval length, which is triggered aperiodically by the eNB, the interval duration must be equal to or greater than the last GNSS position determination time duration reported by the UE.

[0067] FFS: if the interval duration is set by the eNB, or the interval duration is equal to the last reported GNSS position determination time duration.

[0068] Agreements related to GNSS assistance information include: Agreement The GNSS assistance information that the EU reports to the eNB consists of at least: • GNSS position determination time for measurement Petition 870250111433, dated 04 / 12 / 2025, page 17 / 153 13 / 62 • GNSS validity period

[0069] Agreement

[0070] When the eNB triggers the UE to perform GNSS measurements, The EU regains GNSS position fixation.

[0071] • FFS signaling details

[0072] • FFS: how the EU reports assistance information GNSS after the eNB is triggered and the detailed content.

[0073] • Note: further discussion if an EU is expected to handle all eNB shots

[0074] Agreement

[0075] EU reports on the duration of the position determination period GNSS for measurement, at least during the initial access stage.

[0076] information. - It is up to RAN2 to decide which message contains this

[0077] Agreement

[0078] In connected mode, the UE can report validation duration. GNSS with MAC CE.

[0079] Agreement

[0080] EU reports only a determination time duration of GNSS position for GNSS measurement at least when moving to RRC connected state.

[0081] Agreement

[0082] The following alternatives may be considered for Inform the eNB about the successful GNSS measurement on the EU side following the GNSS measurement on the connected RRC.

[0083] • Alt-1: The EU will report the new validity period of GNSS

[0084] • Alt-2: Receipt of any UL transmission from the EU in eNB after GNSS measurement SUMMARY Petition 870250111433, dated 04 / 12 / 2025, page 18 / 153 / 62

[0085] In the 3GPP Version 18 NTN IoT WI, RAN1 agreed to periodically trigger an NTN IoT UE to perform a GNSS measurement using a GNSS measurement interval using a MAC CE. However, the details of the measurement interval and UE behavior are yet to be designed.

[0086] RAN1 also agreed that the EU will report GNSS assistance information to the network, but the detailed plan has not yet been specified.

[0087] The description of the various modalities presented in this document includes details on how to trigger GNSS measurements of different types to an IoT NTN UE. Details on the UE's behavior when receiving a GNSS measurement signal are also described, as well as methods for reporting the validity period of GNSS assistance information and for configuring the UE's behavior to report this information.

[0088] The embodiments described in this document include, for example, a method, in a UE, for carrying out GNSS measurements, wherein the method comprises receiving an indication of a selection of a type of GNSS measurement to be carried out by the UE from at least two of: an aperiodic GNSS measurement, an event-based GNSS measurement, a time-periodic GNSS measurement and a periodic GNSS measurement, wherein “periodic GNSS measurement” encompasses both time-periodic GNSS measurements and event-based GNSS measurements. The method further comprises carrying out one or more GNSS measurements in accordance with the indication.

[0089] The methods described in this document also include corresponding methods performed at a network node to facilitate GNSS measurements by an UE. An example method, at a network node, comprises the step of sending an indication of a selection to the UE. Petition 870250111433, dated 04 / 12 / 2025, page 19 / 153 / 62, concerning a type of GNSS measurement to be performed by the EU from among at least two of: an aperiodic GNSS measurement, an event-based GNSS measurement, a time-periodic GNSS measurement, and a periodic GNSS measurement, wherein “periodic GNSS measurement” encompasses both time-periodic GNSS measurements and event-based GNSS measurements. The exemplary method further comprises the steps of receiving GNSS assistance information from the EU, and receiving from the EU, with or in association with the GNSS assistance information, information indicating a validity period corresponding to all or part of the GNSS assistance information.

[0090] Devices and systems adapted / configured to perform some or all of the methods summarized above, and variants thereof, are also described in detail below.

[0091] The use of various modalities of the techniques, devices and systems described in this document allows a network to configure a UE with different types of GNSS measurement intervals, as well as the UE's behavior for GNSS reacquisition. Some implementations allow the UE to report the validity period of the GNSS assistance information reported by the UE to the eNB and / or allow the eNB to configure the UE's behavior for reporting GNSS assistance information. BRIEF DESCRIPTION OF THE FIGURES

[0092] Figure 1 shows an exemplary architecture of a satellite network with curved tube transponders.

[0093] Figure 2 illustrates the so-called transparent payload architecture for an NTN and its integration with the 5G network.

[0094] Figure 3 illustrates various parameters for describing a satellite orbit.

[0095] Figure 4 illustrates an example method as executed. Petition 870250111433, dated 04 / 12 / 2025, p. 20 / 153 / 62 for an EU, in accordance with some modalities.

[0096] Figure 5 illustrates an exemplary method as performed by a UE, according to some embodiments.

[0097] Figure 6 illustrates an exemplary method as performed by a UE, according to some embodiments.

[0098] Figure 7 is a process flowchart that illustrates an exemplary method executed by a network node, according to some modalities.

[0099] Figure 8 shows an exemplary communication system, according to some modalities.

[00100] Figure 9 illustrates components of an exemplary UE, according to some embodiments.

[00101] Figure 10 illustrates components of an exemplary network node, according to some modalities.

[00102] Figure 11 illustrates an exemplary virtualization environment. DETAILED DESCRIPTION

[00103] Some of the embodiments contemplated in this document will now be described in more detail with reference to the accompanying drawings. The embodiments are provided by way of example to convey the scope of the subject to those skilled in the art in the field.

[00104] Although the modalities described below are presented primarily in terms of LTE-based NTNs (including IoT), they are equally applicable to an NR-based NTN (including IoT). The term “network” is used as an adjective in the solution description below to refer to a network node, which will typically be an eNB (e.g., in an LTE-based NTN, such as the IoT NTN), but which may also be a gNB (e.g., in an NR-based NTN), a base station or access point in another type of network, or any other Petition 870250111433, dated 04 / 12 / 2025, p. 21 / 153 / 62 network node with the ability to communicate directly or indirectly with a UE.

[00105] Global Navigation Satellite Systems (GNSS) play an important role in the proposed solutions. The best known is the American Global Positioning System (GPS), but there are also other similar systems that could provide the functionality used in the proposed solution, for example, the Russian Global Navigation Satellite System (GLONASS), the Chinese BeiDou Navigation Satellite System and the European Galileo.

[00106] The terms “connected mode”, “RRC_CONNECTED state” or “RRC_CONNECTED mode” are used interchangeably in this document and refer to a state in which the end-user terminal, or UE, maintains a connection to the network so that data can be readily exchanged between the terminal. This does not imply continuous transmissions in either direction, but rather that a connection and the information that defines it are being controlled by the network and that resources are readily available for end-user data exchange through that connection.

[00107] The following discussion uses the terms aperiodic, event-based, and time-periodic GNSS measurement events. A time-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. An 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 expiration of GNSS validity duration with or without a certain time offset). Note that the term periodic itself, as used in this document, refers to Petition 870250111433, dated 04 / 12 / 2025, page 22 / 153 18 / 62 GNSS measurements are both periodic over time and event-based. If further distinction is desired between these two types, the terms "periodic over time measurement" and "event-based GNSS measurement" are used.

[00108] The symbols ... are used in this document to refer to the first, second, third and nth GNSS measurement that a UE performs in RRC_CONNECTED state.

[00109] When a signaling message or parameter, or a UE behavior, is specified in a standard, in this document it is referred to as “standardized”, “specified” or “specified in a standard”. That is, these expressions / terms are equivalent.

[00110] The term / expression “GNSS position determination time duration” refers to the time the UE needs to perform a GNSS position fix (i.e., a successful GNSS position measurement), which can vary, for example, depending on the UE’s GNSS state (often referred to as “hot”, “momo” and “cold” states, or “hot initialization”, “warm initialization” and “cold initialization”).

[00111] In the 3GPP Version 18 IoT NTN WI, RAN1 agreed that the standards will allow the network to aperiodically trigger an IoT NTN UE to perform a GNSS measurement using a GNSS measurement interval, with the triggering using a Medium Access Control Element (MAC CE) sent over the network to the UE. However, the details of the measurement interval and the UE's behavior in response to the MAC CE were not previously defined.

[00112] In some embodiments according to the techniques presently described, an X bit indicator is included in the MAC CE that triggers GNSS measurement to indicate one or more (or any combination) of the following information: - if the GNSS measurement to be performed is: Petition 870250111433, dated 04 / 12 / 2025, p. 23 / 153 / 62 the aperiodic, event-based or time-periodic (as a modality variant), the aperiodic or event-based (as another modality variant), the event-based or time-periodic (as another modality variant).

[00113] - If the GNSS measurement interval duration is set to the nearest value greater than or equal to the value reported by the EU for the GNSS position determination time duration, or to the value indicated by the eNB.

[00114] - If the UE needs to report its GNSS position determination time duration after performing the next GNSS measurement

[00115] - If the UE needs to report its GNSS position determination time duration each time it performs a measurement GNSS

[00116] - Whether the EU needs to report one, two or three values ​​for the GNSS position determination time duration.

[00117] - If the EU needs to report more than one value for the GNSS position determination time duration

[00118] - The number of GNSS measurements for which the measurement configuration is valid.

[00119] - The time period during which the GNSS measurement interval setting is valid.

[00120] As an example, a 1-bit flag can be included in the MAC CE used to trigger GNSS measurement to indicate whether the measurement configuration is periodic (i.e., event-based or time-periodic) or aperiodic. If the flag is set to 1, the UE will reuse the same GNSS configuration for its next GNSS measurement, i.e., it will use the same measurement interval duration. Petition 870250111433, dated 04 / 12 / 2025, page 24 / 153 20 / 62 GNSS and the trigger time (i.e., a periodically recurring trigger time) for the GNSS measurement interval for its subsequent GNSS measurements.

[00121] In other modes, separate GNSS measurement commands are used to trigger aperiodic GNSS measurements, time-periodic GNSS measurements, and event-based GNSS measurements.

[00122] In other modes, an X bit indicator is included in the RRC message that triggers GNSS measurement to indicate one or more (or any combination) of the information mentioned in the previous mode based on MAC CE.

[00123] In other embodiments, the bit X indicator mentioned above is indicated separately, i.e., not in the MAC or RRC message that triggers GNSS measurement. In yet another embodiment, one or more bits of the bit X indicator are indicated using the MAC or RRC message that triggers GNSS measurement, while one or more bits (if any) remain that are indicated separately using MAC, DCI, or RRC signaling.

[00124] This bit X indicator can be a bitmap in the MAC or RRC CE, for example, one bit to indicate aperiodic measurements, one bit to indicate event-based measurements and one bit to indicate time-periodic measurements, or code points where each code point refers to a certain measurement configuration or a combination of measurement configurations.

[00125] UE behavior upon receiving GNSS measurement trigger: If an aperiodic GNSS measurement trigger is received by the UE to perform GNSS measurement Y, and the GNSS measurement configuration is indicated as periodic, - If the UE is instructed to start the measurement interval of Petition 870250111433, dated 04 / 12 / 2025, page 25 / 153 21 / 62 GNSS after the expiration of its GNSS validity period, the UE will reuse the same GNSS measurement interval setting for the next GNSS measurement^2 unless it receives a new GNSS measurement trigger from the network.

[00126] - If the UE is instructed to start the measurement interval of GNSS before the expiration of its GNSS validity period, the UE will “partially reuse” the same GNSS measurement interval setting for the next GNSS measurement ^2 unless it receives a new GNSS measurement trigger from the network for JV, jí2. Here, “partial reuse” means that the UE will use the same setting for the interval duration and / or GNSS assistance information for measurement ^2 (as indicated by the network for measurement) except for the GNSS measurement trigger time instance, which will be set to start after the passage of a time duration X after the expiration of the GNSS validity period where X can be fixed in the specification (e.g., X=0 or X=1 ms) or configured by the network.

[00127] If an aperiodic GNSS measurement trigger is received by the UE to perform GNSS measurement ^1, and the GNSS measurement setting is indicated as aperiodic, the UE applies the setting only to measurement ^1.

[00128] If a new GNSS measurement trigger is received, the UE will discard the instruction received in the previous GNSS measurement trigger.

[00129] If a new GNSS measurement trigger is received and the network indicates one or more measurement intervals for which this trigger will be valid and / or the duration of time for which the GNSS measurement trigger will be applicable, the UE will discard the instructions received in the previous GNSS measurement trigger and apply the new instructions only for the GNSS measurement intervals indicated in the new GNSS measurement trigger and / or for Petition 870250111433, dated 04 / 12 / 2025, p. 26 / 153 / 62 the duration of time during (or after) which the GNSS measurement trigger will be activated, for example, the same may apply the GNSS measurement received in the penultimate GNSS measurement trigger until the GNSS measurement trigger activation time of the last GNSS measurement trigger is reached.

[00130] One or more combinations of the above methods may be used.

[00131] GNSS Validity Assistance and Reporting Information

[00132] In some embodiments, the UE includes the validity period of the GNSS assistance information that it reports to the eNB. In some embodiments, a single value may be used for all parameters reported as part of the GNSS assistance information. Alternatively, a separate validity period may be reported for each parameter value reported as part of the GNSS assistance information. Yet another alternative, one or more validity periods may be reported for the GNSS assistance information where one validity period is applicable to one or more parameter values ​​reported as part of the GNSS assistance information. In another embodiment, validity periods are also reported as part of the GNSS assistance information.

[00133] For example, if the EU reports GNSS position determination time duration as part of the assistance information, this also includes how long that value can be considered valid by the network.

[00134] In some modes, after having reported the GNSS position determination time duration for the first time by entering the RRC_CONNECTED state, the UE reports the GNSS position determination time duration only when it has changed since the last time the UE reported it. Petition 870250111433, dated 04 / 12 / 2025, page 27 / 153 / 62

[00135] In some modes, the eNB configures the UE's behavior regarding the reporting of the GNSS position determination time duration. For example, the eNB could configure the UE to: - Report the GNSS position determination time only when the RRC_CONNECTED state is entered. - report the duration of GNSS position determination time after each new GNSS measurement, - report the GNSS position determination time duration when reporting the GNSS validity period (i.e., together with the GNSS validity period), - report the duration of GNSS position determination time by entering the RRC_CONNECTED state and then when it has changed since the last time the EU reported it, - Report the GNSS position determination time duration by entering the RRC_CONNECTED state and then, after each new GNSS measurement, if the GNSS position determination time duration has changed since the last time the UE reported it, - Report the GNSS position determination time duration by entering the RRC_CONNECTED state and then, along with the GNSS validity duration reports, report if the GNSS position determination time duration has changed since the last time the EU reported it.

[00136] In other modalities, similar behavior can be defined for other types (i.e., in addition to GNSS position fix duration and GNSS validity duration) of GNSS assistance information.

[00137] In view of the examples and detailed explanations provided above, it will be appreciated that Figure 4, Figure 5, and Figure 6 are process flowcharts illustrating generalized methods as executed by Petition 870250111433, dated 04 / 12 / 2025, page 28 / 153 / 62, a UE, to perform GNSS measurements. The methods illustrated in these figures are intended to be generalizations of various techniques described above, from the perspective of a UE, such as a UE operating in an NTN. Thus, where the terminology used in these figures and in the description below differs from similar or clearly related terminology used above, the terminology in the figures and below should be understood as at least encompassing the terminology used to describe specific examples above. Note that while these figures illustrate three distinct methods, a given UE may be configured to perform any, some, or all of the methods.

[00138] Referring first to Figure 4, the illustrated method includes, as shown in block 410, the step of receiving an indication of a selection of a GNSS measurement type to be performed by the UE. Several approaches to how this indication works are provided below. In some examples, the indication may be received in or associated with a command that configures a GNSS measurement for the UE. The indication may, in several modes, be configured to select a GNSS measurement type from at least two of the following types: an aperiodic GNSS measurement, an event-based GNSS measurement, a time-periodic GNSS measurement, and a periodic GNSS measurement, where “periodic GNSS measurement” encompasses both time-periodic GNSS measurements and event-based GNSS measurements.

[00139] As shown in block 420, the method further comprises performing one or more GNSS measurements as indicated.

[00140] In some modes or instances, the indication shows whether the GNSS measurement to be performed by the UE is an aperiodic GNSS measurement or an event-based GNSS measurement. In other modes or instances, the indication shows whether the GNSS measurement to be Petition 870250111433, dated 04 / 12 / 2025, page 29 / 153 / 62, states that the measurement performed by the UE is an event-based GNSS measurement or a time-periodic measurement. In other instances, the indication specifies whether the GNSS measurement to be performed by the UE is an aperiodic measurement or a periodic measurement, where a periodic measurement is either a time-periodic measurement or an event-based measurement.

[00141] The indication may be a 1-bit flag in some modes or instances, for example, where the indication selects one of two types of GNSS measurements. In some modes or instances, the indication is instead a multi-bit indicator, the definition of bits in the multi-bit indicator indicating the types of GNSS measurement to be performed by the UE. This may be by means of a bitmap, for example, where each bit in the indicator corresponds to a GNSS type. Alternatively, each of the several possible definitions of the multi-bit indicator may be a code point that maps to a GNSS measurement type and / or predefined GNSS measurement configuration.

[00142] In several modes or instances, the indication is included in a MAC or RRC CE message that triggers GNSS measurement. In others, the indication may be sent separately from a MAC or RRC CE message that triggers GNSS measurement.

[00143] In some embodiments or instances, the method may additionally comprise receiving, with or in association with the indication, one or more of the following: an indication of a GNSS measurement interval for performing the GNSS measurement(s); an indication as to whether the GNSS measurement interval for performing the GNSS measurement(s) is set to a value nearest greater than or equal to a value reported by the UE for a GNSS position determination time duration or to a value indicated by the network node anchoring the feeder link of a connection between the UE and the network node, via an NTN node; an indication as to whether the UE is to report its time duration of Petition 870250111433, dated 04 / 12 / 2025, page 30 / 153 26 / 62 GNSS position determination after performing a subsequent GNSS measurement; an indication of whether the UE is to report its GNSS position determination time duration each time it performs a GNSS measurement; an indication of whether the UE needs to report one, two, or three values ​​for the GNSS position determination time duration; an indication of whether the UE needs to report more than one value for the GNSS position determination time duration; a number of GNSS measurements for which a measurement setting provided to the UE is valid; and a time period during which a GNSS measurement interval setting provided to the UE is valid.

[00144] Figure 5 illustrates another exemplary method that can be implemented in a UE to perform GNSS measurements. As noted above, this method can be performed in conjunction with the method shown in Figure 4, in some modes or instances.

[00145] The method shown in Figure 5 includes, as shown in block 510, the step of receiving a message or command that triggers an aperiodic GNSS measurement ^i, where the UE has been provided with a GNSS measurement configuration indicated as being periodic. The method further comprises, as shown in block 520, reusing at least part of the GNSS measurement configuration according to a certain rule. This rule may be as follows: • If the UE is instructed to start the GNSS measurement interval for Mi after its GNSS validity period expires, the UE will reuse the same GNSS measurement interval setting for the next GNSS measurement unless it receives a new GNSS measurement trigger from the network for ^2, and • If the UE is instructed to start the GNSS measurement interval for before its GNSS validity period expires, the UE will “partially reuse” the same measurement interval setting for Petition 870250111433, dated 04 / 12 / 2025, page 31 / 153 27 / 62 GNSS for the next GNSS measurement unless it receives a new GNSS measurement trigger from the network for ^2, wherein, “partial reuse” means that the UE will use the same configuration for the interval duration and / or GNSS assistance information for measurement ^2 (as indicated by the network for measurement except for the GNSS measurement trigger time instance, which will be set to start after the passage of a time duration X after the GNSS validity duration expires, wherein X can be fixed in the specification (e.g., X=0 or X=1 ms) or configured by the network.

[00146] Figure 6 illustrates yet another exemplary method that can be implemented in a UE to perform GNSS measurements. As noted above, this method can be performed in conjunction with one or both of the methods shown in Figure 4 and Figure 5, in some modes or instances.

[00147] As shown in block 610, this method includes the step of sending GNSS assistance information to a network node. As shown in block 620, the method further comprises sending, with or in association with the GNSS assistance information, information indicating a validity period corresponding to all or part of the GNSS assistance information. In some embodiments or instances, the information indicating a validity period comprises an indication of a GNSS position determination time duration reported by the UE to the network node. The discussion above included detailed descriptions of various examples and variations of how this validity period information can be conducted, and when.

[00148] Figure 7 is a process flowchart illustrating a generalized method, as executed by a network node, to facilitate GNSS measurements by a UE. Thus, this method complements those described above. Again, the method illustrated in this Petition 870250111433, dated 04 / 12 / 2025, page 32 / 153 / 62. The figure is intended to be a generalization of several techniques described above, from the perspective of a network node, such as a gNB or eNB operating on an NTN. Thus, where the terminology used in these figures and in the description below differs from similar or clearly related terminology used above, the terminology in the figures and below should be understood as at least encompassing the terminology used to describe specific examples above.

[00149] The method shown in Figure 7 includes, as shown in block 710, the step of sending, to the UE, an indication of a selection of a GNSS measurement type to be performed by the UE. Several approaches to how this indication works have been provided below. In some examples, this may be in or associated with a command that configures a GNSS measurement for the UE.The indication can, in several modes, be configured to select a GNSS measurement type from at least two of the following types: an aperiodic GNSS measurement, an event-based GNSS measurement, a time-periodic GNSS measurement, and a periodic GNSS measurement, where "periodic GNSS measurement" encompasses both time-periodic GNSS measurements and event-based GNSS measurements.

[00150] As was the case with the corresponding method shown in Figure 4, in some modes or instances, this indication indicates whether the GNSS measurement to be performed by the UE is an aperiodic GNSS measurement or an event-based GNSS measurement. In other modes or instances, the indication indicates whether the GNSS measurement to be performed by the UE is an event-based GNSS measurement or a time-periodic measurement. In still others, the indication indicates whether the GNSS measurement to be performed by the UE is an aperiodic measurement or a periodic measurement, wherein a periodic measurement is either a time-periodic measurement or an event-based measurement.

[00151] The indication may be a 1-bit flag in some Petition 870250111433, dated 04 / 12 / 2025, p. 33 / 153 / 62 modalities or instances, for example, where the indication selects one of two types of GNSS measurements. In some modalities or instances, the indication is instead a multi-bit indicator, the definition of bits in the multi-bit indicator indicating the types of GNSS measurement to be performed by the UE. This can be by means of a bitmap, for example, where each bit in the indicator corresponds to a GNSS type. Alternatively, each of the several possible definitions of the multi-bit indicator can be a code point that maps to a GNSS measurement type and / or predefined GNSS measurement configuration.

[00152] In several modes or instances, the indication is included in a MAC or RRC CE message that triggers GNSS measurement. In others, the indication may be sent separately from a MAC or RRC CE message that triggers GNSS measurement.

[00153] In some embodiments or instances, the method may additionally comprise sending, with or in association with the indication, one or more of any of the following: an indication of a GNSS measurement interval for performing the GNSS measurement(s); an indication as to whether the GNSS measurement interval for performing the GNSS measurement(s) is set to a value nearest greater than or equal to a value reported by the UE for a GNSS position determination time duration or to a value indicated by the network node anchoring the feeder link of a connection between the UE and the network node, via an NTN node; an indication as to whether the UE is to report its GNSS position determination time duration after performing a subsequent GNSS measurement; an indication as to whether the UE is to report its GNSS position determination time duration each time it performs a GNSS measurement;an indication of whether the EU needs to report one, two or three values ​​for the GNSS position determination time duration; an indication of whether the EU needs to report more than one value for the duration of; Petition 870250111433, dated 04 / 12 / 2025, page 34 / 153 / 62 GNSS position determination time; a number of GNSS measurements for which a measurement configuration provided for the UE is valid; and a time period during which a GNSS measurement interval configuration provided for the UE is valid.

[00154] In some embodiments or instances of the method shown in Figure 7, the method additionally comprises, as shown in block 720, the step of receiving GNSS assistance information. In these embodiments or instances, the method may further comprise receiving from the UE, with or in association with the GNSS assistance information, information indicating a validity period corresponding to all or part of the GNSS assistance information. This is shown in block 730. Again, the discussion above includes detailed descriptions of various examples and variations of how this validity period information may be conducted, and when.

[00155] Figure 8 shows an example of an 800 communication system according to some embodiments. Not shown here is an NTN node and the feeder link from an eNB or gNB to an NTN node, through which the system communicates with a UE via an NTN node – this is shown in Figure 1. This exemplary system provides a general context for the techniques described above. Some of the details or variants described may not be applicable to an NTN system or other network deployment in which the described techniques are implemented.

[00156] In the example, the 800 communication system includes an 802 telecommunication network which includes an 804 access network, such as a radio access network (RAN), and an 806 core network, which includes one or more 808 core network nodes. The 804 access network includes one or more access network nodes, such as 810a and 810b network nodes (one or more of which may be generally referred to as 810 network nodes) or any other similar 3rd Generation Partnership Project (3GPP) access nodes or points. Petition 870250111433, dated 04 / 12 / 2025, page 35 / 153 / 62 non-3GPP access. Furthermore, as will be observed by those skilled in the art, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are provided 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 802 telecommunications network includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the 802 telecommunications network that supports an ORAN specification (for example, 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 802 telecommunications network, including one or more 810 network nodes and / or 808 core network nodes.

[00157] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU-CP) or an O-CU user plane (O-CU-UP), an intelligent RAN controller (near real-time or non-real-time) hosting software or software plugins, 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” designates support for 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. Furthermore, an ORAN access node can be a logical node on a physical node.Additionally, an ORAN network node can be implemented in a virtualization environment (described further below) in which one or more network functions are... Petition 870250111433, dated 04 / 12 / 2025, page 36 / 153 / 62 virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework through an O-2 interface defined by the O-RAN Alliance or comparable technologies. 810 network nodes facilitate the direct or indirect connection of user equipment (UE), such as by connecting 812a, 812b, 812c, and 812d UEs (one or more of which may be generally referred to as 812 UEs) to the 806 main network via one or more wireless connections.

[00158] Exemplary wireless communications via 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 carrying information without the use of wires, cables, or other material conductors. Furthermore, in different embodiments, the 800 communication system 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 via wired or wireless connections. The 800 communication system may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[00159] 812 UEs can be any type of a wide variety of communication devices, including wireless devices arranged, configured, and / or operational to communicate wirelessly with 810 network nodes and other communication devices. Similarly, 810 network nodes are arranged, capable, configured, and / or operational to communicate directly or indirectly with 812 UEs and / or with other network nodes or equipment in the 802 telecommunications network to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the 802 telecommunications network.

[00160] In the example shown, the main 806 network connects the nodes Petition 870250111433, dated 04 / 12 / 2025, page 37 / 153 / 62 of network 810 to one or more hosts, such as host 816. These connections can be direct or indirect through one or more intermediate networks or devices. In other examples, network nodes can be directly coupled to hosts. The core network 806 includes one or more core network nodes (e.g., core network node 808) that are structured with hardware and software components. The characteristics of these components may be substantially similar to those described in relation to UEs, network nodes, and / or hosts, so the descriptions thereof are generally applicable to the corresponding components of the core network node 808.Exemplary core network nodes include functions from one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Service (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Signature Identifier Unveiling Function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[00161] The 816 host may be owned or controlled by a service provider other than an operator or provider of the 804 access network and / or the 802 telecommunication network and may be operated by the service provider or on behalf of the service provider. The 816 host may host a variety of applications to provide one or more services. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieval and compilation of data under various ambient conditions detected by a plurality of UEs, analytics functionality, social networking, functions to control or otherwise interact with remote devices, functions for an alarm and surveillance center, or any other such function performed by Petition 870250111433, dated 04 / 12 / 2025, page 38 / 153 / 62 a server.

[00162] As a whole, the 800 communication system in Figure 8 enables connectivity between UEs, network nodes, and hosts. In this sense, the communication system can be configured to operate according to predefined rules or procedures, such as specific standards 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 2G, 3G, 4G, 5G standards or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the 802.11 (WiFi) standards of the Institute of Electrical and Electronics Engineers (IEEE); and / or any other suitable wireless communication standard, such as Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, ZigBee Near Field Communication (NFC), LiFi and / or any low-power wide area network (LPWAN) standard, such as LoRa and Sigfox.

[00163] In some instances, the 802 telecommunications network is a cellular network that implements standardized 3GPP features. Consequently, the 802 telecommunications network can support network slicing to provide different logical networks for different devices that are connected to the 802 telecommunications network. For example, the 802 telecommunications network can provide Ultra-Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Wideband (eMBB) services to other UEs and / or Massive Machine Type Communication (mMTC) / Massive IoT services to still other UEs.

[00164] In some examples, 812 UEs are configured to transmit and / or receive information without direct human interaction. For example, a UE may be designed to transmit information to the 804 access network on a predetermined schedule when triggered by a Petition 870250111433, dated 04 / 12 / 2025, page 39 / 153 / 62 internal or external event, or in response to requests from the 804 access network. Additionally, a UE can be configured to operate in single or multiple RAT mode or multiple patterns. For example, a UE can operate with any one or a combination of Wi-Fi, NR (New Radio) and LTE, i.e., it is configured for dual multi-radio connectivity (MR-DC), such as E-UTRAN (Evolved UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

[00165] In the example, concentrator 814 communicates with access network 804 to facilitate indirect communication between one or more UEs (e.g., UE 812c and / or 812d) and network nodes (e.g., network node 810b). In some examples, concentrator 814 may be a controller, router, content and analytics source, or any of the other communication devices described in this document in relation to UEs. For example, concentrator 814 may be a wideband router that allows access to the main network 806 for the UEs. As another example, concentrator 814 may be a controller that sends commands or instructions to one or more actuators on the UEs. The commands or instructions may be received from the UEs, network nodes 810, or through executable code, script, process, or other instructions on concentrator 814.As another example, the 814 concentrator can be a data collector that acts as temporary storage for UE data and, in some embodiments, can perform analysis or other processing of the data. As another example, the 814 concentrator can be a content source. For example, for a UE that is a VR headset, display, speaker, or other media delivery device, the 814 concentrator can retrieve VR resources, video, audio, or other media or data related to sensory information through a network node, which the 814 concentrator then provides to the UE directly after performing local processing and / or after adding additional local content. In yet another example, the 814 concentrator acts... Petition 870250111433, dated 04 / 12 / 2025, page 40 / 153 / 62 as a proxy or orchestrator server for UEs, in particular, if one or more of the UEs are low-energy IoT devices.

[00166] The 814 concentrator can have a constant / persistent or intermittent connection with the 810b network node. The 814 concentrator can also allow a different communication scheme and / or schedule between the 814 concentrator and the UEs (e.g., UE 812c and / or 812d) and between the 814 concentrator and the 806 main network. In other examples, the 814 concentrator is connected to the 806 main network and / or one or more UEs via a wired connection. Additionally, the 814 concentrator can be configured to connect to an M2M service provider via the 804 access network and / or to another UE via a direct connection. In some scenarios, the UEs can establish a wireless connection with the 810 network nodes while still connected through the 814 concentrator via a wired or wireless connection. In some configurations, the 814 concentrator may be a dedicated concentrator—that is, a concentrator whose primary function is to route communications to / from UEs from / to the 810b network node.In other configurations, the 814 concentrator may be a non-dedicated concentrator – that is, a device that is capable of operating to route communications between the UEs and the 810b network node, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[00167] Figure 9 shows a UE 900 according to some embodiments. Several of the methods described above can be implemented in some of these embodiments. However, some of the details or variants described here may not be applicable, for example, to an NTN. As used in this document, a UE refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other UEs. In some embodiments, the UE is configured, arranged and / or operable to communicate wirelessly with an NTN, for example, through Petition 870250111433, dated 04 / 12 / 2025, page 41 / 153 / 62 from an NTN node to a gNB, as in Figure 1. Examples of a UE include, but are not limited to, a smartphone, mobile phone, cellular phone, voice over IP (VoIP) phone, wireless local link phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, portable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop embedded equipment (LEE), laptop mounted equipment (LME), smart device, wireless client 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 Narrowband Internet of Things (NB-IoT) UE, a Machine-Type Communication (MTC) UE, and / or an Enhanced MTC (eMTC) UE.

[00168] A UE can support device-to-device (D2D) communication, for example, through the implementation of a 3GPP standard for side-link 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 cannot or 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 can be associated with or operated for the benefit of a user (e.g., a smart energy meter).

[00169] The UE 900 includes a set of 902 processing circuits Petition 870250111433, dated 04 / 12 / 2025, p. 42 / 153 / 62, which is operatively coupled via a bus 904 to an input / output interface 906, a power supply 908, a memory 910, a communication interface 912 and / or any other component, or any combination thereof. Certain UEs may use all or a subset of the components shown in Figure 9. The level of integration between components may vary from one UE to another. Additionally, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[00170] The 902 processing circuit set is configured to process instructions and data and can be configured to implement any operational sequential state machine to execute instructions stored as machine-readable computer programs in memory 910. The 902 processing circuit set can be implemented as one or more hardware-implemented state machines (e.g., in distinct logic field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), etc.); programmable logic in conjunction with suitable firmware; one or more stored computer programs, general-purpose processors such as a microprocessor or digital signal processor (DSP), in conjunction with suitable software; or any combination of the above. For example, the 902 processing circuit set may include multiple central processing units (CPUs).

[00171] In the example, the 906 input / output interface can be configured to provide an interface to, or interface with, an input device, an output device, or one or more input and / or output devices. Examples of an output device include a loudspeaker, a sound card, a video card, a display, a monitor, a printer, an actuator, a transmitter, a smart card, another output device, or any combination thereof. An input device Petition 870250111433, dated 04 / 12 / 2025, page 43 / 153 / 62, may allow a user to capture information in EU 900. 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 webcam, etc.), a microphone, a sensor, a mouse, a moving sphere, a directional panel, a touch panel, a scroll wheel, a smart card, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to detect user input. A sensor may be, for example, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device.For example, a Universal Serial Bus (USB) port can be used to provide both an input device and an output device.

[00172] In some embodiments, the 908 power supply is structured as a battery or battery pack. Other types of power supplies, such as an external power supply (e.g., an electricity outlet), photovoltaic device, or energy cell, may be used. The 908 power supply may additionally include a power circuitry to deliver power from the 908 power supply itself and / or from an external power supply to various parts of the UE 900 via the input circuitry or an interface such as a power cable. The power delivery may be, for example, to charge the 908 power supply. The power circuitry may perform any shaping, conversion, or other modification to the power from the 908 power supply to make the power suitable for the respective UE 900 components to which the power is supplied.

[00173] Memory 910 can be configured to include memory such as random access memory (RAM), memory only Petition 870250111433, dated 04 / 12 / 2025, page 44 / 153 / 62 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 others. In one example, memory 910 includes one or more application programs 914, such as an operating system, web browser application, a widget, gadget engine or other application and corresponding data 916. Memory 910 may store, for use by UE 900, any one of a variety of different operating systems or combinations of operating systems.

[00174] The 910 memory can be configured to include numerous physical drive units, such as a redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, mini-USB drive, pen drive, key drive, high-density digital versatile disk (HD-DVD), optical disk drive, internal hard disk drive, Blu-ray optical disk drive, holographic digital data storage (HDDS) optical disk drive, external dual mini-DIMM in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smart card memory, such as a 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 can, for example, be an embedded UICC (eUICC), an integrated UICC (iUICC), or a removable UICC commonly known as a "SIM card". Memory 910 can allow UE 900 to access instructions, application programs, and the like, stored in transient or non-transient memory media to download or load data. A manufactured item, such as one that utilizes a communication system, can be tangibly incorporated. Petition 870250111433, dated 04 / 12 / 2025, page 45 / 153 / 62 as or in memory 910, which may be or comprise a device-readable storage medium.

[00175] The processing circuitry 902 can be configured to communicate with an access network or another network using the communication interface 912. The communication interface 912 may comprise one or more communication subsystems and may include, or be communicatively coupled to, an antenna 922. The communication interface 912 may include one or more transceivers used to communicate, such as through communication with one or more remote transceivers of another wirelessly communicative device (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter 918 and / or a receiver 920 suitable for providing network communications (e.g., frequency allocations, optical, electrical, and others).Furthermore, the transmitter 918 and the receiver 920 can be coupled to one or more antennas (for example, antenna 922) and can share circuit components, software or firmware, or alternatively, be implemented separately.

[00176] In the illustrated embodiment, the communication functions of the 912 communication interface 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, other similar communication functions, or any combination thereof. Communications may be implemented in accordance with one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, Petition 870250111433, dated 04 / 12 / 2025, page 46 / 153 / 62 Transmission Control Protocol / Internet Protocol (TCP / IP), Synchronous Optical Network Link (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP) and others.

[00177] Regardless of the sensor type, a UE can provide an output of data captured by its sensors, through its 912 communication interface, via a wireless connection to a network node. The data captured by the sensors of a UE can be communicated via a wireless connection to a network node through another UE. The output can be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to regulate the reporting load of multiple sensors), in response to a trigger event (e.g., when humidity 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).

[00178] 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, motor, or 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 a robotic arm that performs a medical procedure according to the received input.

[00179] A UE, when in the form of an Internet of Things (IoT) device, may be a device for use in one or more application domains, wherein these domains comprise, but are not limited to, city wearable technology, extended industrial application, and healthcare. Non-limiting examples of such an IoT device are a device that is, or is embedded in: a connected refrigerator or freezer, a Petition 870250111433, dated 04 / 12 / 2025, page 47 / 153 / 62 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 / humidity sensor, an electric door lock, a connected doorbell, an air conditioning system such as a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smartwatch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable item 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 type of medical device, such as a heart rate monitor or a remotely controlled surgical robot. A UE in the form of an IoT device comprises a set of circuits and / or software depending on the intended application of the IoT device in addition to other components, as described in relation to UE 900 shown in Figure 9.

[00180] As yet another specific example, in an IoT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements and 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 a particular example, the UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a vessel, and an aircraft,or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation. Petition 870250111433, dated 04 / 12 / 2025, page 48 / 153 / 62

[00181] In practice, any number of UEs can be used together in relation to a single use case. For example, a first UE might be integrated into a drone and provide the drone's speed information (obtained via a speed sensor) to a second UE which is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE can adjust the drone's acceleration (e.g., by controlling an actuator) to increase or decrease the drone's speed. The first and / or second UE can also include more than one of the functionalities described above. For example, a UE might understand both the sensor and the actuator and handle data communication for both the speed sensor and the actuators.

[00182] Figure 10 shows a 1000 network node according to some embodiments. Several techniques described in this document relating to network nodes, base stations or similar can be implemented in a 1000 network node that has some or all of these features. However, some of the details or variants may be inapplicable or unnecessary for, for example, a gNB in ​​an NTN deployment that uses the techniques described in this document.

[00183] As used in this document, a 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 telecommunications network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, B Nodes, evolved B Nodes (eNBs), and NR B Nodes (gNBs)), ORAN nodes, or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).

[00184] Base stations can be categorized based on the amount of coverage they provide (or, otherwise, their Petition 870250111433, dated 04 / 12 / 2025, page 49 / 153 / 62 level of transmitted energy) and others, depending on the amount of coverage provided, may be provided 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 that controls 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 ORAN 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. The parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[00185] Other examples of network nodes include 5G multi-point transmission point (multi-TRP) access nodes, multi-standard radio equipment (MSR) 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 / multi-cast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Service Mobile Location Centres (E-SMLCs)) and / or Drive Test Minimization (MDTs).

[00186] Network node 1000 includes a set of processing circuits 1002, a memory 1004, a communication interface 1006 and a power supply 1008.Network node 1000 can be composed of multiple physically separate components (e.g., a NodeB component and an RNC component, or a BTS component and a BSC component, etc.), each of which can have its own respective components. In certain scenarios where network node 1000... Petition 870250111433, dated 04 / 12 / 2025, page 50 / 153 / 62, 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 single NodeB and pair of RNCs may, in some cases, be considered a single separate network node. In some embodiments, network node 1000 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 1004 for different RATs) and some components may be reused (e.g., the same antenna 1010 may be shared by different RATs).The 1000 network node may also include multiple sets of the various components illustrated for different wireless technologies integrated into the 1000 network node, 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 chip or a different chip or set of chips and other components within the 1000 network node.

[00187] The processing circuitry set 1002 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, feature, or combination of operable hardware, software, and / or coded logic to provide, individually or in conjunction with other network node components 1000, such as memory 1004, network node functionality 1000.

[00188] In some embodiments, the 1002 processing circuitry includes a system-on-a-chip (SOC). In some embodiments, the 1002 processing circuitry includes one or Petition 870250111433, dated 04 / 12 / 2025, p. 51 / 153 / 62 more among radio frequency (RF) transceiver circuit assembly 1012 and baseband processing circuit assembly 1014. In some embodiments, the radio frequency (RF) transceiver circuit assembly 1012 and the baseband processing circuit assembly 1014 may be on separate chips (or chip assemblies), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of the RF transceiver circuit assembly 1012 and baseband processing circuit assembly 1014 may be on the same chip or chip assemblies, boards, or units.

[00189] Memory 1004 may comprise any form of computer-readable volatile or non-volatile 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 (e.g., a hard disk), removable storage media (e.g., a flash drive, a Compact Disc (CD) or a Digital Video Disc (DVD)) and / or any other volatile or non-volatile, device-readable, non-transient and / or computer-executable memory device that stores information, data and / or instructions that can be used by the processing circuitry 1002.Memory 1004 can store any suitable instruction, data, or information that includes a computer program, software, or application that includes one or more logic, rules, codes, tables, and / or other instructions capable of being executed by the processing circuitry 1002 and used by the network node 1000. Memory 1004 can be used to store any calculation performed by the processing circuitry 1002 and / or any data received through the communication interface 1006. In some embodiments, the processing circuitry 1002 and memory 1004 are... Petition 870250111433, dated 04 / 12 / 2025, p. 52 / 153 / 62 integrated.

[00190] The 1006 communication interface is used in wired or wireless signaling and / or data communication between a network node, access network and / or UE. As illustrated, the 1006 communication interface comprises one or more 1016 port(s) / terminal(s) for sending and receiving data, for example, to and from a network via a wired connection. The communication interface 1006 also includes a set of initial radio interface circuits 1018 that can be coupled to, or in certain embodiments, a part of, the antenna 1010. The initial radio interface circuit set 1018 comprises filters 1020 and amplifiers 1022. The initial radio interface circuit set 1018 can be connected to an antenna 1010 and to the processing circuit set 1002. The initial radio interface circuit set can be configured to condition signals communicated between the antenna 1010 and the processing circuit set 1002.The initial radio interface circuit set 1018 can receive digital data that must be sent to other network nodes or UEs via a wireless connection. The initial radio interface circuit set 1018 can convert the digital data into a radio signal that has the appropriate channel and bandwidth parameters using a combination of filters 1020 and / or amplifiers 1022. The radio signal can then be transmitted through antenna 1010. Similarly, upon receiving data, antenna 1010 can collect radio signals that are then converted into digital data by the initial radio interface circuit set 1018. The digital data can be passed to the processing circuit set 1002. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[00191] In certain alternative embodiments, network node 1000 does not include a separate initial radio interface circuitry set 1018, Petition 870250111433, dated 04 / 12 / 2025, p. 53 / 153 / 62 instead, the processing circuit assembly 1002 includes an initial radio interface circuit assembly and is connected to antenna 1010. Similarly, in some embodiments, all or part of the RF transceiver circuit assembly 1012 is part of the communication interface 1006. In still other embodiments, the communication interface 1006 includes one or more ports or terminals 1016, the initial radio interface circuit assembly 1018, and the RF transceiver circuit assembly 1012, as part of a radio unit (not shown), and the communication interface 1006 communicates with the baseband processing circuit assembly 1014, which is part of a digital unit (not shown).

[00192] Antenna 1010 may include one or more antennas or antenna arrays, configured to send and / or receive wireless signals. Antenna 1010 may be coupled to the initial radio interface circuitry 1018 and may be any type of antenna capable of transmitting and receiving wireless data and / or signals. In certain embodiments, antenna 1010 is separate from network node 1000 and is connectable to network node 1000 via an interface or port.

[00193] Antenna 1010, communication interface 1006 and / or processing circuitry 1002 can be configured to perform any reception operations and / or certain acquisition operations described herein as being performed by the network node. Any information, data and / or signals can be received from a UE, another network node and / or any other network equipment. Similarly, antenna 1010, communication interface 1006 and / or processing circuitry 1002 can be configured to perform any transmission operations described herein as being performed by the network node. Any information, data and / or signals can be transmitted to a UE, another network node and / or any other network equipment.

[00194] The 1008 power supply provides power to the various Petition 870250111433, dated 04 / 12 / 2025, page 54 / 153 / 62 network node 1000 components in a form suitable for the respective components (e.g., at a voltage and current level required for each respective component). The power supply 1008 may additionally comprise or be coupled to the power management circuitry to supply the network node 1000 components with power to perform the functionality described herein. For example, the network node 1000 may be connectable to an external power supply (e.g., a power grid, an electricity outlet) via an input circuitry or interface such as a power cable, wherein the external power supply provides power to the power supply circuitry of the power supply 1008.As a further example, the 1008 power supply may comprise a power supply in the form of a battery or battery pack that is connected to, or integrated into, the power circuitry. The battery may provide backup power should the external power supply fail.

[00195] Network node 1000 configurations may include additional components beyond those shown in Figure 10 to provide certain aspects of network node functionality, including any of the functionalities described herein and / or any functionality necessary to support the subject matter described herein. For example, network node 1000 may include user interface equipment to allow input of information into network node 1000 and to allow output of information from network node 1000. This may allow a user to perform diagnostics, maintenance, repair, and other administrative functions for network node 1000.

[00196] Figure 11 is a block diagram illustrating a virtualization environment 1100 in which the functions implemented by some modalities can be virtualized. In the present context, virtualization means creating virtual versions of appliances or devices that may include Petition 870250111433, dated 04 / 12 / 2025, page 55 / 153 / 62, virtualization of hardware platforms, storage devices, and network linking resources. As used in this document, virtualization can be applied to any device described herein or components thereof, and refers 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 running on one or more virtual machines (VMs) deployed in one or more virtual environments hosted by one or more hardware nodes, such as a hardware computing device operating as a network node, UE, primary network node, or host.Additionally, in modes where the virtual node does not require radio connectivity (for example, a core or host network node), then the node can be fully virtualized. In some modes, the 1100 virtualization environment includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Orchestration and Management Framework via an O-2 interface.

[00197] The 1102 applications (which may alternatively be referred to as software cases, virtual tools, network functions, virtual nodes, virtual network functions, etc.) are executed in the Q400 virtualization environment to implement some of the features, functions and / or benefits of some of the modalities described in this document.

[00198] Hardware 1104 includes the set of processing circuits, memory that stores software and / or instructions executable by the hardware processing circuitry and / or other hardware devices, as described herein, such as a network interface, input / output interface, and others. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 1106 (also referred to as hypervisors or Petition 870250111433, dated 04 / 12 / 2025, page 56 / 153 / 62 virtual machine monitors (VMMs)), provide VMs 1108a and 1108b (one or more of which may be generally referred to as VMs 1108) and / or perform any of the functions, features and / or benefits described in relation to some embodiments described in this document. The 1106 virtualization layer may present a virtual operating platform that appears as network-linked hardware to the VMs 1108.

[00199] VMs 1108 comprise virtual processing, virtual memory, virtual network link or interface, and virtual storage, and may be executed by a corresponding virtualization layer 1106. Different modalities of a virtual appliance case 1102 may be implemented in one or more of the VMs 1108, and the implementations may be done in different ways. Hardware virtualization is, in some contexts, referred to as network function virtualization (NFV). NFV can be used to consolidate many types of network equipment into high-volume, industry-standard server hardware, physical switches, and physical storage, which may be located in data centers and client-premise equipment.

[00200] In the context of NFV, a VM 1108 can be a software implementation of a physical machine that executes programs as if they were executed on a non-virtualized physical machine. Each of the VMs 1108 and the hardware part 1104 that runs that VM, being dedicated by hardware to that VM and / or shared by hardware by that VM with other VMs, form separate virtual network elements. Also in the context of NFV, a virtual network function is responsible for handling specific network functions that are executed by one or more VMs 1108 on top of the hardware 1104 and correspond to the application 1102.

[00201] The 1104 hardware can be implemented in an individual network node with generic or specific components. The 1104 hardware can Petition 870250111433, dated 04 / 12 / 2025, page 57 / 153 / 62 implement some functions through virtualization. Alternatively, the 1104 hardware can be part of a larger hardware cluster (such as in a data center or CPE) where many hardware nodes work together and are managed through 1110 management and orchestration, which, among other things, oversees the application lifecycle management 1102. In some embodiments, the 1104 hardware is coupled with one or more radio units, each including one or more transmitters and one or more receivers that can be coupled to one or more antennas. The radio units can communicate directly with other hardware nodes through one or more suitable network interfaces and can be used in combination with virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station.In some embodiments, some signaling may be provided using an 1112 control system that can alternatively be used for communication between hardware nodes and radio units.

[00202] Although the computing devices described in this document (e.g., UEs, network nodes, hosts) may include the combination of hardware components illustrated, other embodiments may comprise computing devices with different combinations of components. It should be understood that these computing devices may comprise any suitable combination of hardware and / or software necessary to perform the tasks, features, functions, and methods described in this document. Determination, calculation, acquisition, or similar operations described in this document may be performed through the processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the information or converted information into information stored in the network node, and / or performing one or more operations based on the obtained or converted information and, as a Petition 870250111433, dated 04 / 12 / 2025, page 58 / 153 / 62 result of said processing, to make a determination. Furthermore, although the components are graphically represented as single boxes located within a larger box or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that constitute a single illustrated component, and functionality may be divided among separate components. For example, a communication interface may be configured to include any of the components described in this document and / or the functionality of the components may be divided between the processing circuitry and the communication interface. In another example, the non-computationally intensive functions of any of these components may be implemented in software or firmware, and the computationally intensive functions may be implemented in hardware.

[00203] In certain embodiments, some or all of the functionality described herein may be provided by the processing circuitry executing instructions stored in memory, wherein certain embodiments may be a computer program product in the form of a non-transient computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored in a separate or distinct device-readable storage medium, such as in a non-adjustable manner. In either of these particular embodiments, whether executing instructions stored in a non-transient or non-transient computer-readable storage medium, the processing circuitry may be configured to perform the described functionality.The benefits provided by such functionality are not limited to the individual processing circuitry or other components of the device. Petition 870250111433, dated 04 / 12 / 2025, page 59 / 153 / 62 computing, but are leveraged by the computing device as a whole and / or by end users and generally a wireless network. EXEMPLARY MODALITIES

[00204] The types of techniques, apparatus and systems described in this document include, but are not limited to, the following enumerated examples: 1. A method, on a user equipment (UE), for performing Global Navigation Satellite System (GNSS) measurements, wherein the method comprises: receiving, in or associated with a command that configures a GNSS measurement for the UE, an indication of a selection of a type of GNSS measurement to be performed by the UE from at least two of: an aperiodic GNSS measurement, an event-based GNSS measurement, a time-periodic GNSS measurement, and a periodic GNSS measurement, wherein “periodic GNSS measurement” encompasses both time-periodic GNSS measurements and event-based GNSS measurements; and performing one or more GNSS measurements in accordance with the indication.

[00205] 2. The method of exemplary embodiment 1, wherein the indication indicates whether the GNSS measurement to be performed by the UE is an aperiodic GNSS measurement or an event-based GNSS measurement.

[00206] 3. The method of exemplary embodiment 1, wherein the indication indicates whether the GNSS measurement to be performed by the UE is an event-based GNSS measurement or a time-periodic measurement.

[00207] 4. The method of exemplary embodiment 1, wherein the indication indicates whether the GNSS measurement to be performed by the UE is an aperiodic measurement or a periodic measurement, wherein a periodic measurement is a time-periodic measurement or an event-based measurement.

[00208] 5. The method of any of the modalities Petition 870250111433, dated 04 / 12 / 2025, p. 60 / 153 / 62, examples 1-4, where the indication is a 1-bit flag.

[00209] 6. The method of any of the exemplary modalities 1-4, where the indication is a multi-bit indicator, the definition of bits in the multi-bit indicator indicates the types of GNSS measurement to be performed by the UE.

[00210] 7. The method of any of the exemplary embodiments 1-6, in which the indication is included in a MAC or RRC CE message that triggers GNSS measurement.

[00211] 8. The method of any of the exemplary embodiments 1-6, in which the indication is sent separately from a MAC or RRC CE message that triggers GNSS measurement.

[00212] 9. The method of any of the exemplary embodiments 1-8, wherein the method further comprises receiving, with or in association with the indication, one or more of any of the following: an indication of a GNSS measurement interval for performing the GNSS measurement(s); an indication as to whether the GNSS measurement interval for performing the GNSS measurement(s) is set to a value nearest greater than or equal to a value reported by the UE for a GNSS position determination time duration or to a value indicated by the network node anchoring the feeder link of a connection between the UE and the network node, via an NTN node; an indication as to whether the UE is to report its GNSS position determination time duration after performing a subsequent GNSS measurement; an indication as to whether the UE is to report its GNSS position determination time duration each time it performs a GNSS measurement;an indication of whether the EU needs to report one, two, or three values ​​for the GNSS position determination time duration; an indication of whether the EU needs to report more than one value for the GNSS position determination time duration; a number of GNSS measurements for which one; Petition 870250111433, dated 04 / 12 / 2025, page 61 / 153 57 / 62 measurement configuration provided for the UE is valid; and a period of time during which a GNSS measurement interval configuration provided for the UE is valid.

[00213] 10. The method of any of the exemplary embodiments 1-9, which further comprises: receiving a message or command that triggers an aperiodic GNSS measurement ^i, wherein the UE has been provided with a GNSS measurement configuration indicated as being periodic; and reuse at least part of the GNSS measurement configuration according to the rule: if the UE was instructed to start the GNSS measurement interval after the expiration of its GNSS validity period, the UE will reuse the same GNSS measurement interval configuration for the next GNSSM2 measurement unless it receives a new GNSS measurement trigger from the network for Ma, and if the UE is instructed to start the GNSS measurement interval for Mi before the expiration of its GNSS validity period, the UE will “partially reuse” the same GNSS measurement range configuration for the next GNSSiV12 measurement unless it receives a new GNSS measurement trigger from the network for ^2, where,"Partial reuse" means that the UE will use the same configuration for the interval duration and / or GNSS assistance information for measurement (as indicated by the network for measurement except for the GNSS measurement trigger time instance, which will be set to start after a time duration X has passed after the GNSS validity duration expires, where X can be fixed in the specification (e.g., X=0 or X=1 ms) or configured by the network.

[00214] 11. The method of any of the exemplary embodiments 1-10, wherein the method further comprises: sending GNSS assistance information to a network node; and sending, with or in association with the GNSS assistance information, information that Petition 870250111433, dated 04 / 12 / 2025, page 62 / 153 58 / 62 indicates a validity period corresponding to all or part of the GNSS assistance information.

[00215] 12. A method, on a user equipment, UE, for performing Global Navigation Satellite System, GNSS, measurements, wherein the method comprises: receiving a message or command that triggers an aperiodic GNSS measurement ^i, wherein the UE has been provided with a GNSS measurement configuration indicated as being periodic; and reusing at least part of the GNSS measurement configuration in accordance with the rule: if the UE is instructed to start the GNSS measurement interval after the expiration of its GNSS validity period, the UE will reuse the same GNSS measurement interval configuration for the next GNSS measurement ^2 unless it receives a new GNSS measurement trigger from the network for ^2, and if the UE is instructed to start the GNSS measurement interval before the expiration of its GNSS validity period,The UE will “partially reuse” the same GNSS measurement interval configuration for the next GNSS measurement ^2 unless it receives a new GNSS measurement trigger from the network for ^2, wherein, “partial reuse” means that the UE will use the same configuration for the interval duration and / or GNSS assistance information for measurement ^2 (as indicated by the network for measurement ^1) except for the GNSS measurement trigger time instance, which will be set to start after a time duration X has passed after the GNSS validity duration expires, where X can be fixed in the specification (e.g., X=0 or X=1 ms) or configured by the network.

[00216] 13. A method, on a user's equipment, UE, for carrying out Global Navigation Satellite System, GNSS, measurements, wherein the method comprises: sending GNSS assistance information to a network node; and sending, with or in association with the information of Petition 870250111433, dated 04 / 12 / 2025, page 63 / 153 / 62 GNSS assistance, information indicating a validity period corresponding to all or part of the GNSS assistance information.

[00217] 14. The exemplary modality method 13, in which the information indicating a validity period comprises an indication of a GNSS position determination time period reported by the UE for the network node.

[00218] 15. A method, at a network node, to facilitate measurements of Global Navigation Satellite System, GNSS, by a user equipment, UE, wherein the method comprises: sending, in or associated with a command that configures a GNSS measurement to the UE, an indication of a selection of a type of GNSS measurement to be performed by the UE from at least two of: an aperiodic GNSS measurement, an event-based GNSS measurement, a time-periodic GNSS measurement and a periodic GNSS measurement, wherein “periodic GNSS measurement” encompasses both time-periodic GNSS measurements and event-based GNSS measurements.

[00219] 16. The exemplary modality method 15, in which the indication indicates whether the GNSS measurement to be performed by the UE is an aperiodic GNSS measurement or an event-based GNSS measurement.

[00220] 17. The exemplary modality method 15, wherein the indication indicates whether the GNSS measurement to be performed by the UE is an event-based GNSS measurement or a time-periodic measurement.

[00221] 18. The exemplary modality method 15, wherein the indication indicates whether the GNSS measurement to be performed by the UE is an aperiodic measurement or a periodic measurement, wherein a periodic measurement is a time-periodic measurement or an event-based measurement.

[00222] 19. The method of any of the exemplary modes 15-18, where the indication is a 1-bit flag. Petition 870250111433, dated 04 / 12 / 2025, p. 64 / 153 / 62

[00223] 20. The method of any of the exemplary modalities 15-18, where the indication is a multi-bit indicator, the definition of bits in the multi-bit indicator indicates the types of GNSS measurement to be performed by the UE.

[00224] 21. The method of any of the exemplary embodiments 15-20, in which the indication is included in a MAC or RRC CE message that triggers GNSS measurement.

[00225] 22. The method of any of the exemplary embodiments 15-21, wherein the indication is sent separately from a MAC or RRC CE message that triggers GNSS measurement. 23. The method of any of the exemplary embodiments 15-22, wherein the method further comprises sending to the UE, with or in association with the indication, one or more of the following: an indication of a GNSS measurement interval for performing the GNSS measurement(s); an indication as to whether the GNSS measurement interval for performing the GNSS measurement(s) is set to a value nearest greater than or equal to a value reported by the UE for a GNSS position determination time duration or to a value indicated by the network node anchoring the feeder link of a connection between the UE and the network node, via an NTN node; an indication of whether the UE is to report its GNSS position determination time duration after performing a subsequent GNSS measurement;an indication of whether the UE is to report its GNSS position determination time duration each time it performs a GNSS measurement; an indication of whether the UE needs to report one, two, or three values ​​for the GNSS position determination time duration; an indication of whether the UE needs to report more than one value for the GNSS position determination time duration; a number of GNSS measurements for which a measurement configuration provided to the UE is valid; and a time period during which a measurement is performed. Petition 870250111433, dated 04 / 12 / 2025, page 65 / 153 / 62, states that the GNSS measurement interval configuration provided for the EU is valid.

[00226] 24. The method of any of the exemplary modalities 15-23, which additionally includes: receiving GNSS assistance information from the EU; and receiving, from the EU, with or in association with GNSS assistance information, information indicating a validity period corresponding to all or part of the GNSS assistance information.

[00227] 25. A user device for adjusting timing relative to a server cell in a wireless network, comprising: a set of processing circuits configured to perform any of the exemplary modes 1-14; and a set of power supply circuits configured to provide power to the set of processing circuits.

[00228] 26. A network node to assist a user device, EU, for adjusting timing relative to a server cell in a wireless network, wherein the network node comprises: a set of processing circuits configured to perform any of the exemplary modes 15-24; a set of power supply circuits configured to provide power to the set of processing circuits.

[00229] 27. A user equipment (UE) for adjusting timing relative to a server cell in a wireless network, wherein the UE comprises: an antenna configured to send and receive wireless signals; an initial radio interface circuit set connected to the antenna and to the processing circuit set, and configured to condition signals communicated between the antenna and the processing circuit set; wherein the processing circuit set is configured to perform any of the steps of any of the modes of Group C; an input interface connected to the processing circuit set and configured to allow the input of information into the UE to be Petition 870250111433, dated 04 / 12 / 2025, page 66 / 153 / 62 processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output UE information that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the UE. Petition 870250111433, dated 04 / 12 / 2025, page 67 / 153

Claims

1 / 11 CLAIMS 1. A method, on a user equipment, UE, for carrying out Global Navigation Satellite System, GNSS, measurements, characterized in that the method comprises: receiving (410) an indication of a selection of a type of GNSS measurement to be carried out by the UE from at least two of: an aperiodic GNSS measurement, an event-based GNSS measurement, a time-periodic GNSS measurement and a periodic GNSS measurement, wherein “periodic GNSS measurement” encompasses both time-periodic GNSS measurements and event-based GNSS measurements; and carrying out (420) one or more GNSS measurements as indicated.

2. Method according to claim 1, characterized in that the indication shows whether the GNSS measurement to be performed by the UE is an aperiodic measurement or a periodic measurement, wherein a periodic measurement is a time-periodic measurement or an event-based measurement.

3. Method according to claim 1 or 2, characterized in that the indication is a 1-bit flag.

4. Method according to any one of claims 1 to 3, characterized in that the indication is included in a MAC or RRC CE message that triggers the GNSS measurement.

5. A method according to any one of claims 1 to 4, characterized in that it further comprises: receiving a configuration for the UE to report the GNSS position determination time duration; and reporting the GNSS position determination time duration upon entering the RRC_CONNECTED state.

6. Method according to any one of claims 1 to Petition 870250111433, dated 04 / 12 / 2025, page 68 / 153 2 / 11 5, characterized in that the method further comprises receiving, with or in association with the indication, one or more of any of the following: an indication of a GNSS measurement interval for performing the GNSS measurement(s); an indication as to whether the GNSS measurement interval for performing the GNSS measurement(s) is set to a value nearest greater than or equal to a value reported by the UE for a GNSS position determination time duration or to a value indicated by the network node anchoring the feeder link of a connection between the UE and the network node, via an NTN node; an indication as to whether the UE must report its GNSS position determination time duration after performing a subsequent GNSS measurement;An indication of whether the UE should report its GNSS position determination time duration each time it performs a GNSS measurement; an indication of whether the UE needs to report one, two, or three values ​​for the GNSS position determination time duration; an indication of whether the UE needs to report more than one value for the GNSS position determination time duration; a series of GNSS measurements for which a measurement setting provided to the UE is valid; and a time period during which a GNSS measurement interval setting provided to the UE is valid.

7. Method according to any one of claims 1 to 6, characterized in that it further comprises: receiving (510) a message or command that triggers an aperiodic GNSS measurement, the UE having been provided with a Petition 870250111433, dated 04 / 12 / 2025, page 69 / 153 3 / 11 GNSS measurement configuration indicated as being periodic; and reuse (520) at least part of the GNSS measurement configuration as per the rule: if the UE was instructed to start the GNSS measurement interval after the end of its GNSS validity period, the UE will reuse the same GNSS measurement interval configuration for the next GNSS measurement, unless it receives a new GNSS measurement trigger from the network, and if the UE was instructed to start the GNSS measurement interval before the end of its GNSS validity period, the UE will “partially reuse” the same M2 GNSS measurement interval configuration for the next GNSS measurement,Unless it receives a new M2 GNSS measurement trigger from the network, where “partial reuse” means that the UE will use the same configuration for the interval duration and / or GNSS assistance information for measurement (as indicated by the network for measurement), except for the GNSS measurement trigger time instance, which will be set to start after a time duration X has elapsed after the GNSS validity period ends, where X may be fixed in the specification or configured by the network.

8. Method according to any one of claims 1 to 7, characterized in that the method further comprises: sending (610), to a network node, GNSS assistance information; and sending (620), with or in association with the GNSS assistance information, information indicating a validity period corresponding to all or part of the GNSS assistance information.

9. Method, at a network node, for facilitating Global Navigation Satellite System, GNSS, measurements by a user equipment, Petition 870250111433, dated 04 / 12 / 2025, page 70 / 153 4 / 11, characterized in that the method comprises: sending (710) to the UE an indication of a selection of a type of GNSS measurement to be performed by the UE from at least two of: an aperiodic GNSS measurement, an event-based GNSS measurement, a time-periodic GNSS measurement and a periodic GNSS measurement, wherein “periodic GNSS measurement” encompasses time-periodic GNSS measurements and event-based GNSS measurements; receiving (720) from the UE GNSS assistance information; and receive (730), from the EU, with or in association with GNSS assistance information, information indicating a validity period corresponding to all or part of the GNSS assistance information.

10. Method according to claim 9, characterized in that the indication shows whether the GNSS measurement to be performed by the UE is an aperiodic measurement or a periodic measurement, wherein a periodic measurement is a time-periodic measurement or an event-based measurement.

11. Method according to claim 9 or 10, characterized in that the indication is a 1-bit flag.

12. Method according to any one of claims 9 to 11, characterized in that the indication is included in a MAC or RRC CE message that triggers the GNSS measurement.

13. Method according to any one of claims 9 to 12, characterized in that the method further comprises sending to the UE, with or in association with the indication, one or more of the following: an indication of a GNSS measurement interval for carrying out the GNSS measurement(s); an indication as to whether the GNSS measurement interval for carrying out the GNSS measurement(s) is set to a value closer to or equal to a value reported by the UE for a GNSS position determination time duration or to a value indicated by the network node anchoring the feeder link of a connection between the UE and the network node, via an NTN node; an indication as to whether the UE should report its GNSS position determination time duration after performing a subsequent GNSS measurement;An indication of whether the UE should report its GNSS position determination time duration each time it performs a GNSS measurement; an indication of whether the UE needs to report one, two, or three values ​​for the GNSS position determination time duration; an indication of whether the UE needs to report more than one value for the GNSS position determination time duration; a series of GNSS measurements for which a measurement setting provided to the UE is valid; and a time period during which a GNSS measurement interval setting provided to the UE is valid.

14. A method according to any one of claims 9 to 13, characterized in that it further comprises: sending a configuration for the UE to report the GNSS position determination time duration; and receiving the GNSS position determination time duration upon entering the RRC_CONNECTED state.

15. User equipment (UE) for performing Global Navigation Satellite System, GNSS measurements, characterized in that the UE comprises: an antenna (922) configured to send and receive wireless signals; Petition 870250111433, dated 04 / 12 / 2025, p.72 / 153 6 / 11 initial radio interface circuitry (918, 920) connected to the antenna (9220) and to the processing circuitry (902) and configured to condition signals communicated between the antenna (922) and the processing circuitry (902); the processing circuitry (902) being configured to: receive an indication of a selection of a type of GNSS measurement to be performed by the UE from at least two of: an aperiodic GNSS measurement, an event-based GNSS measurement, a time-periodic GNSS measurement and a periodic GNSS measurement, wherein “periodic GNSS measurement” encompasses time-periodic GNSS measurements and event-based GNSS measurements; and perform one or more GNSS measurements as indicated.

16. User equipment (UE) according to claim 15, characterized in that the indication shows whether the GNSS measurement to be performed by the UE is an aperiodic measurement or a periodic measurement, wherein a periodic measurement is either a time-periodic measurement or an event-based measurement.

17. User equipment (UE) according to claim 15 or 16, characterized in that the indication is a 1-bit flag.

18. User equipment (UE) according to any one of claims 15 to 17, characterized in that the indication is included in a MAC or RRC CE message that triggers the GNSS measurement.

19. User equipment (UE) according to any one of claims 15 to 18, characterized in that the processing circuitry (902) is additionally configured to: Petition 870250111433, dated 04 / 12 / 2025, page 73 / 153 7 / 11 receive a configuration for the UE to report the GNSS position determination time duration; and report the GNSS position determination time duration when entering the RRC_CONNECTED state.

20. User equipment (UE) according to any one of claims 15 to 19, characterized in that the processing circuitry is additionally configured to receive, with or in association with the indication, one or more of the following: an indication of a GNSS measurement interval for performing the GNSS measurement(s); an indication as to whether the GNSS measurement interval for performing the GNSS measurement(s) is set to a value closest to or equal to a value reported by the UE for a GNSS position determination time duration or to a value indicated by the network node anchoring the feeder link of a connection between the UE and the network node, via an NTN node; an indication as to whether the UE should report its GNSS position determination time duration after performing a subsequent GNSS measurement;an indication as to whether the UE must report its GNSS position determination time duration each time it performs a GNSS measurement; an indication as to whether the UE needs to report one, two, or three values ​​for the GNSS position determination time duration; an indication as to whether the UE needs to report more than one value for the GNSS position determination time duration; a series of GNSS measurements for which a measurement configuration provided to the UE is valid; and a time period during which a GNSS measurement interval configuration provided to the UE is valid.

21. User equipment (UE) according to any one of claims 15 to 20, characterized in that the processing circuitry (902) is additionally configured to: receive a message or command that triggers an aperiodic GNSS measurement, the UE having been provided with a GNSS measurement configuration indicated as being periodic; and reuse at least part of the GNSS measurement configuration according to the rule: if the UE has been instructed to start the GNSS measurement interval after the end of its GNSS validity period, the UE will reuse the same GNSS measurement interval configuration for the next GNSS measurement, unless it receives a new GNSS measurement trigger from the network, and if the UE has been instructed to start the GNSS measurement interval before the end of its GNSS validity period, the UE will “partially reuse” the same GNSS measurement interval configuration for the next GNSS measurement.Unless it receives a new GNSS measurement trigger from the network, where “partial reuse” means that the UE will use the same configuration for the M2 interval duration and / or GNSS assistance information for measurement (as indicated by the network for measurement), except for the GNSS measurement trigger time instance, which will be set to start after a time duration X has elapsed after the GNSS validity period ends, where X may be fixed in the specification or configured by the network.

22. User equipment (UE) according to any one of claims 15 to 21, characterized in that the processing circuitry (902) is additionally configured to: Petition 870250111433, dated 04 / 12 / 2025, page 75 / 153 9 / 11 send, to a network node, GNSS assistance information; and send, with or in association with the GNSS assistance information, information indicating a validity period corresponding to all or part of the GNSS assistance information.

23. Network node for assisting a user equipment, UE, in performing Global Navigation Satellite System, GNSS, measurements on a wireless network, characterized in that the network node comprises: a set of communication interface circuits (1006); and a set of processing circuits (1002) operatively coupled to the set of communication interface circuits (1006), and configured to: send to the UE an indication of a selection of a type of GNSS measurement to be performed by the UE from at least two of: an aperiodic GNSS measurement, an event-based GNSS measurement, a time-periodic GNSS measurement and a periodic GNSS measurement, wherein “periodic GNSS measurement” includes time-periodic GNSS measurements and event-based GNSS measurements; receive GNSS assistance information from the UE;and receive from the EU, with or in association with GNSS assistance information, information indicating a validity period corresponding to all or part of the GNSS assistance information.

24. Network node according to claim 23, characterized in that the indication shows whether the GNSS measurement to be performed by the UE is an aperiodic measurement or a periodic measurement, wherein a periodic measurement is a time-periodic measurement or an event-based measurement.

25. Network node according to claim 23 or 24, characterized in that the indication is a 1-bit flag. Petition 870250111433, dated 04 / 12 / 2025, page 76 / 153 10 / 11 26. Network node according to any one of claims 23 to 25, characterized in that the indication is included in a MAC or RRC CE message that triggers the GNSS measurement.

27. Network node according to any one of claims 23 to 26, characterized in that the processing circuitry (1002) is additionally configured to send to the UE, with or in association with the indication, one or more of the following: an indication of a GNSS measurement interval for performing the GNSS measurement(s); an indication as to whether the GNSS measurement interval for performing the GNSS measurement(s) is set to a value closest to or equal to a value reported by the UE for a GNSS position determination time duration or to a value indicated by the network node anchoring the feeder link of a connection between the UE and the network node, via an NTN node; an indication as to whether the UE should report its GNSS position determination time duration after performing a subsequent GNSS measurement;an indication as to whether the UE should report its GNSS position determination time duration whenever it performs a GNSS measurement; an indication as to whether the UE needs to report one, two, or three values ​​for the GNSS position determination time duration; an indication as to whether the UE needs to report more than one value for the GNSS position determination time duration; a series of GNSS measurements for which a measurement configuration provided to the UE is valid; and a time period during which a GNSS measurement interval configuration provided to the UE is valid. Petition 870250111433, dated 04 / 12 / 2025, p. 77 / 153 11 / 11; 28. Network node according to any one of claims 23 to 27, characterized in that the processing circuit set (1002) is additionally configured to: send a configuration for the UE to report the GNSS position determination time duration; and receive the GNSS position determination time duration when entering the RRC_CONNECTED state.

29. User equipment (UE) for performing Global Navigation Satellite System, GNSS, measurements, characterized in that the UE is adapted to perform a method as defined in any one of claims 1 to 8.

30. Network node for assisting a user's equipment, UE, in performing Global Navigation Satellite System, GNSS, measurements, characterized in that the network node is adapted to perform a method as defined in any one of claims 9 to 14. Petition 870250111433, dated 04 / 12 / 2025, p. 78 / 153

Images