EP4652471A1

EP4652471A1 - Indication information for use in determining a position

Info

Publication number: EP4652471A1
Application number: EP24702661.0A
Authority: EP
Inventors: Fredrik Gunnarsson; Ritesh SHREEVASTAV; Mattias BERGSTRÖM
Original assignee: Telefonaktiebolaget LM Ericsson AB
Current assignee: Telefonaktiebolaget LM Ericsson AB
Priority date: 2023-01-19
Filing date: 2024-01-19
Publication date: 2025-11-26
Also published as: CN120548484A; WO2024155229A1

Abstract

According to an aspect, there is provided a method performed by a user equipment, UE The method comprises receiving (901), from a network node, indication information for use in determining a position of the UE using signals from one or more signal sources. The indication information indicates whether the UE will have Line of Sight, LoS, to one or more signal sources at one or more positions. A corresponding method in the network node is also provided.

Description

Indication information for use in determining a position

Technical Field

This disclosure relates to the provision of information for use by a User Equipment (UE) in determining a position of the UE using signals from one or more signal sources.

Background

Positioning in 4^th Generation (4G)/Long Term Evolution (LTE)ZEvolved Packet Core (EPC) and 5^th Generation (5G)/New Radio (NR)/5G Core (5GC) is supported by the architecture in Fig. 1 , in which direct interactions between a User Equipment (UE) 100 and a location server 130 are via the LTE Positioning Protocol (LPP) 151. Moreover, there are also interactions between the location server 130 and a serving radio base station 110 via the LPPa protocol 152, to some extent supported by interactions between the radio base station 110 and the UE 100 via the Radio Resource Control (RRC) protocol 150. The radio base station 110 interacts with a mobility network entity 120 via a first interface protocol 153, and the mobility network entity 120 interacts with the location server 130 via a second interface protocol 154. In some applications, the location server interacts with a Global Navigation Satellite System (GNSS) correction data provider 140 via a third interface protocol 155.

The location server 130 is the entity in the network architecture that is responsible for collecting information/measurements from the UE 100 and/or radio base station 110 (or more generally the radio access network (RAN)), and calculating the position of the UE 100 from that information/measurements.

In 4G/LTE/EPC and 5G/NR/5GC, the servers/nodes/functions/interfaces/protocols mentioned above are named as shown in Table 1 below:

Table 1

In both cases, the location server can also be interacting with the UE directly over user plane (UP) communications carrying LPP 151 with signalling defined by the Open Mobile Alliance (OMA) Secure UserPlane Location (SUPL), or some other user plane signalling. In the case of SUPL, the location server is denoted SUPL Location Platform (SLP) and the UE is denoted SUPL Enabled Terminal (SET).

There are several options for the interface, signalling and message handling over the third interface 155 between the location server 130 and a correction data provider 140. One option is message handling defined by the Radio Technical Commission for Maritime (RTCM) special committee 104 with the user plane signalling protocol Networked Transport of RTCM via Internet Protocol (NTRIP). RTCM SC 104 initially defined differential corrections to GNSS.

The 3^rd Generation Partnership Project (3GPP) Release (Rel.) 9 introduced support for assisted Global Navigation Satellite System (GNSS), and the scope of the assistance data has been refined over the releases. In Rel. 15, support for Real Time Kinematics (RTK) GNSS was introduced. The assistance data is generated based on observations from one or more reference stations, where a reference station is a node with known position and known antenna configuration, and a GNSS receiver capable of measuring signals from one or more satellite systems, where the satellite systems comprise one or more satellites, and each satellite transmits one or more signals. Typically, the GNSS RTK assistance data is provided by a separate function, correction data provider or Network RTK (NRTK) server (140). GNSS represents a generic system, with examples such as Global Positioning System (GPS), Global Navigation Satellite System (GLONASS), GALILEO and BeiDou. These systems are based on a number of GNSS satellites, each transmitting GNSS signals associated to a specific GNSS signal identity. The satellites follow tailored orbits around the globe.

Fig. 2 illustrates the different 4G/LTE/EPC and 5G/NR/5GC entities in the more complete and common architecture 200. The nodes and functions generally on the left hand side of Figure 2 relate to the 4G/LTE/EPC architecture, and the nodes and functions generally on the right hand side of Figure 2 relate to the 5G/NR/5GC architecture.

5G positioning methods based on 5G signals is realised with downlink positioning reference signals, associated to a specific radio resource, which may be transmitted using a radio beam with directivity. Each positioning reference signal is associated to an identifier. One or more such signals are transmitted from a specific transmission point associated to a radio base station 110.

Positioning methods rely on measurements, and several positioning methods rely on measurements of GNSS signals, WiFi signals, Bluetooth signals, beacon signals, radio access technology (RAT)-dependent signals, etc. by the UE whose position is to be determined. Such measurements are subject to errors or feared events, and a subset of such errors or feared events are due to the local environment of the UE.

The Information Element (IE) SV-ID is used to indicate a specific GNSS satellite. The interpretation of SV-ID depends on the GNSS-1D.

SV-ID field descriptions satellite-id

This field specifies a particular satellite within a specific GNSS. The interpretation of satellite-id depends on the GIMSS-/D see the table below.

Interpretation of satellite-id

Summary

There currently exist certain challenge(s).

Figs. 3a and 3b illustrate one typical example of a local environment impact on the received signal in an urban canyon (e.g. between buildings). In Fig. 3a, some GNSS signals from satellites 160 are received by UE 100 via a line of sight (LoS) path and some via a reflected non-line of sight path (NLoS). Fig. 3b illustrates a similar situation for a terrestrial radio network, where some signals from radio base stations 110 are received via a line of sight path and some via a reflected non-line of sight path. In both cases, the time of flight of a non-line-of-sight signal does not represent the distance between the transmitter and UE, leading to a measurement error due to the local environment of the UE.

The problem with the LoS/NLoS issues is that they potentially have a degrading impact on the positioning performance. At least, the UE 100 needs to be aware and need to try to identify the NLoS satellites via complex and tedious computations which may not be possible for small and/or low complexity UEs.

It can also imply that the UE estimates a position that does not correspond to the expected uncertainty, meaning that the UE can assume a more precise position than what is actually estimated, potentially causing serious implications if used in some automated or collaborative context.

Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. In order to facilitate accurate and reliable positioning with limited complexity, the network can provide, as assistance data, information to the UE about line-of-sight (LoS) and Non-Line-of-sight (NLoS) properties per satellite over a spatial region. Thereby, based on the provided assistance data, the UE can identify satellite signals that are expected to be reliable, and thereby facilitate position estimation. The LoS/NLoS information can be represented in some different ways, such as via a spatial LoS/NLoS indicator, a duration within which a satellite signal is expected to be in LoS at a specific spatial location etc, and the provisioning can be subject to unsolicited provisioning from network to the UE or based on a feedback procedure with communication from the UE to the network.

More generally, the techniques described herein provide that a UE receives LoS-NLoS indication information for use in determining a position of the UE using signals from one or more signal sources (e.g. satellites, sources of WiFi signals, Bluetooth transmitters, sources of beacon signals, base stations, sources of RAT-dependent signals, base stations in a terrestrial RAN, etc.). This LoS-NLoS indication information indicates whether the UE will (e.g. is expected to) have LoS to one or more signal sources at one or more positions of the UE.

According to a first aspect, there is provided a method performed by a UE. The method comprises receiving, from a network node, indication information for use in determining a position of the UE using signals from one or more signal sources, wherein the indication information indicates whether the UE will have LoS to one or more signal sources at one or more positions.

According to a second aspect, there is provided a method performed by a network node. The method comprises sending, to a UE, indication information for use by the UE in determining a position of the UE using signals from one or more signal sources. The indication information indicates whether the UE will have LoS to one or more signal sources at one or more positions.

According to a third aspect, there is provided a computer program product comprising a computer readable medium having computer readable code embodied therein, the computer readable code being configured such that, on execution by a suitable computer or processor, the computer or processor is caused to perform the method according to the first aspect, the second aspect, or any embodiment thereof.

According to a fourth aspect, there is provided a UE configured to perform the method according to the first aspect or any embodiment thereof.

According to a fifth aspect, there is provided a UE comprising a processor and a memory, said memory containing instructions executable by said processor whereby said UE is operative to perform the method according to the first aspect or any embodiment thereof.

According to a sixth aspect, there is provided a network node configured to perform the method according to the second aspect or any embodiment thereof.

According to a seventh aspect, there is provided a network node comprising a processor and a memory, said memory containing instructions executable by said processor whereby said network node is operative to perform the method according to the second aspect or any embodiment thereof.

According to an eighth aspect, there is provided a user equipment, comprising processing circuitry configured to cause the user equipment to perform any of the steps of the method according to the first aspect or any embodiment thereof; and power supply circuitry configured to supply power to the processing circuitry.

According to a ninth aspect, there is provided a network node, the network node comprising processing circuitry configured to cause the network node to perform any of the steps of the method according to the second aspect or any embodiment thereof; power supply circuitry configured to supply power to the processing circuitry.

According to a tenth aspect, there is provided a UE comprising an antenna configured to send and receive wireless signals; radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; the processing circuitry being configured to perform any of the steps of any of the methods according to the first aspect or any embodiment thereof; an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the UE.

Certain embodiments may provide one or more of the following technical advantage(s). An advantage of providing LoS-NLoS indication information is to facilitate signal selection and positioning (i.e. time of flight) measurements to improve positioning, and its convergence, as well as support low-complexity implementations.

The relative location information feedback described in some embodiments enables a solution where the UE does not need to provide accurate location information to the network, which can be relevant to avoiding privacy concerns from sharing accurate location information.

Brief Description of the Drawings

Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings, in which:

Fig. 1 shows an architecture for supporting positioning in communication networks;

Fig. 2 is a detailed illustration of an architecture for supporting positioning in communication networks;

Figs. 3a and 3b illustrate local environment impact on a received signal in an urban canyon;

Fig. 4 is a signalling diagram showing the signalling between a UE and a network node in a communication network;

Fig. 5 is a flow chart illustrating methods performed by a UE;

Fig. 6 is a flow chart illustrating methods performed by a network node;

Figs. 7a, 7b and 7c illustrate different examples of LoS-NLoS indication information;

Fig. 8 illustrates a situation in which a UE could require new/updated LoS-NloS indication information;

Fig. 9 is a flow chart illustrating another method performed by a UE;

Fig. 10 is a flow chart illustrating another method performed by a network node; Fig. 11 shows an example of a communication system in accordance with some embodiments;

Fig. 12 shows a UE in accordance with some embodiments;

Fig. 13 shows a network node in accordance with some embodiments; and

Fig. 14 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized.

DETAILED DESCRIPTION

Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art. Additional information relating to ways in which the techniques described herein can be implemented in the relevant 3GPP standards are found in the Appendix towards the end of the Detailed Description section.

Fig. 4. is a signalling diagram showing the signalling between a UE (or any other type of wireless device that uses GNSS signals to determine its position) and a network node in a communication network according to an exemplary embodiment of the techniques described herein. In some embodiments the network node is a location server (LS) or Location Management Function (LMF) (e.g. in a 4G network or a 5G network), or other network node that is responsible for, or involved in, positioning calculations for UEs in the network. It will be appreciated that a UE typically communicates with nodes in the core network via one or more RAN nodes (base stations), but those intermediate communication links or hops are not shown in Fig. 4 for brevity.

As noted above, in order to facilitate accurate and reliable positioning with limited complexity, the network can provide information to the UE about LoS and NLoS properties per satellite over a spatial region. This assistance data is referred to herein as "LoS/NLoS indication information”, or just "LoS/NLoS information”. Based on the provided assistance data, the UE can identify satellite signals that are expected to be reliable, and thereby facilitate position estimation. The LoS-NLoS indication information may be with respect to GNSS satellite signals, cellular signals and/or other radio access technology (RAT) signals.

The LoS-NLoS indication information may be provided over a spatial grid, where each grid point (e.g. corresponding to a position in the environment) associates LoS-NLoS indication information for a specific satellite, base station anchor, etc. The spatial grid can be associated with altitude information. For example, each grid point of the spatial grid can be associated with one or more altitudes, such that the respective LoS-NLoS indication information for that grid point relates to the associated one or more altitudes at that spatial grid (e.g. latitude, longitude) position. The LoS-NLoS indication information may alternatively be provided associated to logical network elements such as a cell, beam, reference signal(s), list of cells, tracking area (TA), radio network area, etc. The LoS-NLoS indication information may also or alternatively be provided with a broadcast, for example in a System Information Block (SIB), e.g. in a positioning SIB (posSIB) or a non-positioning SIB. Further details about the LoS-NLoS indication information is provided below. As shown in Fig. 4, a capability handshake may take place between the UE and the LS, so that the LS can determine whether the UE supports use of LoS-NLoS indication information. Thus, the LS can send a request 400 to the UE that requests information on the UE's capabilities, and the UE can send a response 410 that indicates the UE's capabilities (and specifically capabilities relating to use of LoS-NLoS indication information).

Optionally, the LS may send a location information network request 420 to the UE, which requests the UE to provide location information indicating the location of the UE. The UE can provide a response 430 that comprises the location information for the UE. The LS can use this location information to support the selection of particular LoS- NLoS indication information that is relevant to the UE.

Optionally, a UE may send a request 440 for assistance data from a network node. This request 440 is received by the LS, and the network node (LS) sends a response 450 comprising assistance data, such as LoS-NLoS indication information. Optionally, the response 450 or the assistance data contained therein is provided with an expiration time, which indicates how long the assistance data is valid for.

At step 460, the UE uses the obtained LoS-NLoS indication information to facilitate or enable selection of signals and/or measurements (of particular signals) for use in performing positioning calculations, and estimates a position from those signals and/or measurements. In particular, the UE can prioritise the signals that it makes range estimations for (based on time-of-flight) based on the GNSS satellites that are considered to be in LoS. The range estimations from different signal sources (e.g. different satellites) are then combined to derive the position of the UE. Signals from satellites that are considered to be NLoS may be ignored, or any timing measurements determined relating to those signals can be discarded or ignored when determining the position of the UE.

Optionally, the UE may send a request 470 to the LS for LoS-NLoS indication information that includes relative location information. An example of such relative location information is an indication of what new spatial information the UE requests, such as the spatial information to the north/east/south/west of the previous spatial information, or a specific subset of the current grid. In embodiments where the LoS-NLoS indication information has an altitude element (e.g. the LoS-NLoS indication information is defined for a particular altitude and/or respective LoS-NLoS indication information is provided for different possible altitudes of the UE), the relative location information may indicate above or below a current altitude of the UE (e.g. because the UE has moved floors in a building). The UE may trigger the request for assistance data via request 470 as the expiration time of the current LoS-NLoS indication information has expired or is about to expire.

Based on the request 470, the LS can send a response 480 that contains new assistance data corresponding to the UE's mobility.

Subsequently, the UE can perform another positioning estimation (step 490) using the new assistance data.

Fig. 5 illustrates the basic steps and some optional steps of the techniques described herein from the perspective of a UE. Many of these steps correspond to the operations of the UE described above with respect to Fig. 4. A UE 100 may perform the method in Fig. 5 in response to executing suitably formulated computer readable code. The computer readable code may be embodied or stored on a computer readable medium, such as a memory chip, optical disc, or other storage medium in the UE/device. The computer readable medium may be part of a computer program product.

In optional step 500, the UE provides information on the UE's capabilities relating to LoS-NLoS indication information (e.g. a capability to use LoS-NLoS indication information in determining a position of the UE). This capability information is provided to a location server (LS) in the network.

In optional step 510, the UE obtains or receives a location information network request from the LS, in optional step 520 the UE provides location information to the LS to support the selection of suitable LoS-NLoS indication information for the UE.

Optionally, in step 530, the UE requests assistance data from a network node (e.g. the LS). This request can be a general request for assistance data, or it can be a specific request for LoS-NLoS indication information.

In step 540 (which can occur in response to the request in step 530, or without a specific request by the UE), the UE obtains assistance data comprising LoS-NLoS indication information. Optionally, an expiration time is provided for the information (e.g. provided as part of the LoS-NLoS indication information or in addition to the LoS-NLoS indication information).

In step 550, the UE uses the obtained LoS-NLoS indication information to facilitate or enable selection of signals and/or measurements for use in performing positioning calculations, and estimating a position from those signals and/or measurements. While step 550 shows the selection of signals and/or measurements according to the LoS-NLoS indication information and determining the device position as a single step or operation, it will be appreciated that these operations can be performed separately in their own respective steps or sub-steps.

Optionally, in step 560, the UE may request, from the LS, LoS-NLoS indication information assistance data including relative location information. An example of such relative location information comprises an indication of what new spatial information the UE requests, such as the spatial information to the north/east/south/west/higher altitude/lower altitude of the current spatial information, or a specific subset of the current grid. In some embodiments, step 560 may be performed as the expiration time of the current information has expired or is about to expire. The UE may have included a grid set identity in the request for assistance data (AD).

In response to the request sent according to step 560, the UE may obtain new assistance data (step 570).

Subsequently, in step 580, the UE uses the obtained LoS-NLoS indication information to facilitate or enable selection of signals and/or measurements for use in performing positioning calculations, and thereby estimating a position of the UE.

Fig. 6 illustrates the basic steps and some optional steps of the techniques described herein from the perspective of a network node (e.g. a LS). Many of these steps correspond to the operations of the LS described above with respect to Fig. 4. A network node may perform the method in Fig. 6 in response to executing suitably formulated computer readable code. The computer readable code may be embodied or stored on a computer readable medium, such as a memory chip, optical disc, or other storage medium in the network node. The computer readable medium may be part of a computer program product. It will be appreciated that while Fig. 6 relates to interactions between the network node and a single UE, in practice such a network node will be performing these operations and steps with respect to multiple UEs at any given time.

In optional step 610 the network node obtains information on capabilities of the UE relating to LoS-NLoS indication information from the UE. Such capability information can relate to the capability of the UE to use LoS-NLoS indication information in determining a position of the UE. Step 610 may comprise the network node sending a request for the capability information to the UE, or the UE may send the capability information to the network node in step 610 without a request to the UE being sent.

Optionally, in step 610, the network node sends a location information network request to the UE, and in response obtains location information from the UE (step 620). This location information can be used by the network node to support the selection of LoS-NLoS indication information that is useful to or suitable for the UE.

Optionally, in step 630, the network node may obtain or receive a request from the UE for assistance data.

In step 640 (which can occur in response to the request received step 630, or without a specific request by the UE), the network node provides assistance data comprising LoS-NLoS indication information to the UE. Optionally, an expiration time is provided for the information (e.g. provided as part of the LoS-NLoS indication information or in addition to the LoS-NLoS indication information).

Optionally, in step 650, the network node may obtain or receive a request from the UE for LoS-NLoS indication information assistance data including relative location information. An example of such relative location information comprises an indication of what new spatial information the UE requests, such as the spatial information to the north/east/south/west/h i gher alti tude/lower altitude of the current spatial information, or a specific subset of the current grid. In some embodiments, the UE may have sent the request for assistance data because the expiration time of the current information has expired, or is about to expire. The UE may include a grid set identity in the request for assistance data (AD).

Based on such request, in step 660 the network node determines, based on the provided relative location information, the scope of new assistance data for LoS-NLoS indication information, and in step 670 provides the assistance data to the UE. In particular, the satellite information about LoS/NLoS differs from one location area to another. Therefore, if the UE provides its previous location where it obtained the previous LoS-NLoS indication information, and what the relative change of position of the UE is (e.g. a distance X North, or just a direction of movement, e.g. North); the network would be able to identify which new LoS-NLoS indication information is applicable to the UE.

The following section describes the form and/or content of the LoS-NLoS indication information in more detail, and how this LoS-NLoS indication information is handled.

Figs. 7a, 7b and 7c are three examples of LoS-NLoS indication information. Thus, in some embodiments the LoS-NLoS indication information is represented by or is in the form of a spatial grid 720 as shown in Fig. 7a and 7b, and in Fig. 7c the LoS-NLoS indication information is represented by or is in the form of a spatial grid that has, or takes into account, altitude information. The spatial grid 720 can comprise a set of coordinates or grid points 730. Some examples of such a grid (i.e. how the grid points 730 are defined) include: a reference coordinate, a delta step in a direction (e.g. north), a delta step in a different direction (e.g. east), a number of steps in the first direction, and a number of steps in the different direction. For each grid point 730, and for each considered signal there is a "LoS- NLoS indication”, i.e. an indication of whether a UE 100 at that grid point will have LoS or NLoS to the satellite transmitting the respective signal.

As noted above, the spatial grid can be associated with altitude information. In some embodiments, this means that each grid point in the spatial grid is associated with a specific altitude. In this case, the specific altitude can be provided as an altitude relative to a reference altitude. Examples of a reference altitude include ellipsoid level, mean sea level, ground level, etc. In other embodiments, the altitude information can be provided as a validity range, such as a lower altitude and upper altitude within which the spatial grid data is considered valid. That is, the altitude information can be a range of altitudes of the UE in which the respective LoS-NLoS indication information is valid. In yet other embodiments, the altitude information can be provided as multiple layers in the spatial grid, where each layer in the spatial grid corresponds to an altitude or an altitude range.

In alternative embodiments, the spatial grid (or respective grid points in the spatial grid) can be associated with an air pressure sensor (e.g. a barometer) validity area, as shown below in the ASN.1 changes. That is, there can be a mapping between air pressure measurements and altitude for different areas (a validity area). Thus, for a certain air pressure sensor value which is valid in a certain area (and which value maps to an altitude); the LoS-NLoS indication information can provide a list of satellites which has (probability of) LoS or NLoS.

The following section indicates how the above can be implemented in the "Sensor Assistance Data Elements” section of 3GPP TS 37.355 v17.2.0, where proposed changes are underlined, and the different introduced components are specifically defined in the Appendix below.

6.5.5.8 Sensor Assistance Data Elements

- Sensor-AssistanceDataList

The IE Sensor-AssistanceDataList is used by the location server to provide the Sensor specific assistance data to the UE.

Sensor-AssistanceDataList field descriptions refPressure

This field specifies the atmospheric pressure (Pa) nominal at sea level, EGM96 [29] to the target.

The scale factor is 1 Pa. The value is added to the nominal pressure of 101325 Pa. refPosition

This field specifies the reference position at which the pressure measurement is made, as an ellipsoid point with altitude and uncertainty ellipsoid. refT emperature

Local temperature measurement at the reference where the pressure measurement is made.

The scale factor 1 K. The value is added to 273K. period

This field specifies the pressure validity period and reference pressure rate. pressureValidityPeriod

- beginTime. this field specifies the start time of the pressure validity period in G/VSS System Time.

- beginTimeAlt. this field specifies an alternative start time. It may be used by the target device if GNSS-System i Time is not available. The alternative start time is relative to the time the message was received. The scale factor is 15 min. The range is from 0 minutes to 43215 minutes = 30 days. duration, this field specifies the duration of the validity period after the begin time. The scale factor is 15 minutes. The range is from 15 minutes to 43215 minutes = 30 days. referencePressureRate

This field specifies the rate of change of pressure. When this field is included, the reference pressure applies only at the start of the pressure validity period. The scale factor is 10Pa/hour. area

This field specifies the area within which the provided atmospheric reference pressure is valid and any spatial drift. pressureValidityArea

- centerPoint. this field specifies the coordinates of the centre of the rectangular validity area.

- validityAreaWidth. this field specifies the width of the rectangular validity area. Width is measured from the centre along the latitude and is measured as the total width of the rectangle. The scale factor is 1 km. The range is from 1 km to 128km.

- validityAreaHeight. this fields specifies the height of the rectangular validity area. Height is measured from the I centre along the longitude and is measured as the total height of the rectangle. The scale factor is 1 km. The range is from 1 km to 128km.

If this field is present, refPosition should not be provided by the location server and if provided, shall be ignored by the I target device. gN-pressure

This field specifies the northward gradient of the reference pressure calculated from the centre of the pressureValidityArea. The scale factor is 1 Pa/km. If this field is not provided, the gradient is assumed to be zero. gE-pressure

This field specifies the eastward gradient of the reference pressure calculated from the centre of the pressureValidityArea. The scale factor is 1 Pa/km. If this field is not provided, the gradient is assumed to be zero.

In some embodiments, the LoS-NLoS indication is a binary indication for a signal, e.g. LoS: True/False (or alternatively it could be in the form: NLoS: True/False). Alternatively, it can be more refined and include the option of the LoS-NLoS state being uncertain, such as LoS True/False/Uncertain (or NLoS True/False/Uncertain). Alternatively, the LoS-NLoS indication can be provided in the form of a confidence measure (or probability) as a percentage (1..100).

As an example, if LoS is predicted as 70%, the value 70 would be provided with the LoS-NLoS indication. In other or further embodiments, the indication can be or include a duration within which the respective signal is predicted to be in LoS at that grid point 730 (or alternatively in NLoS).

In some embodiments, the grid 720 can also be provided with a binmask indicating which of the grid points 730 are provided with a LoS-NLoS indication value. For example, there can be buildings 710 within the region covered by the grid 720, and grid points 730 inside buildings 710 may be omitted, as shown by non-solid grid points 730 in Fig. 7a.

Fig. 7a also illustrates an update mechanism for the network node to provision updated LoS-NLoS indication information to the UE 100 based on UE feedback (and in particular the UE position). In the example of Fig. 7a, the UE 100 (e.g. which can be, be part of, or be in, a car or other vehicle) travels along the illustrated path 740 between the buildings 710.

Initially, the UE 100 obtains LoS-NLoS indication information corresponding to a first grid (grid 720) to facilitate positioning. This LoS-NLoS indication information can be obtained according to one or more of steps 400-460 described above.

When the UE 100 has moved along path 740 and is about to leave the spatial area associated with the current grid 720 (e.g. as indicated by the device position determined by the UE 100), the UE 100 determines "relative location information”. The relative location information may be relative to the current grid 720 and could be represented by a direction such as North, West, South, East in relation to the current grid 720 (and/or higher/lower altitude in the case where the LoS-NLoS indication information takes altitude into account). This relative location information indicates or suggests the spatial area that the UE 100 wants or needs an updated grid for (e.g. as described above with reference to step 470).

The network node takes the provided relative location information into consideration to determine a new spatial grid to provide to the UE 100, and provides assistance data to the UE 100 (e.g. according to step 480) comprising a new grid. In the example of Fig. 7a, this new/updated grid is shown by grid 750. A further updated grid required as the UE 100 continues along the path 740 is shown by grid 760.

This, in the specific example of Fig. 7a, the UE 100 is first provided with a grid 720 comprising 4 x 4 grid points 730, according to the initial knowledge about the location of the UE 100. When the UE 100 is about to leave the area covered by the grid 720, it sends a new assistance data request to the network node indicating a relative location information, which in this case is South. The network node determines a new grid 750 to the south of the current grid 720, this time formed of 4 x 2 grid points 720, based on the provided relative location information from the UE 100. The network node provides LoS-NLoS indication information for this grid 750 to the UE 100. When the UE 100 is about to leave this second grid 750 it sends a new assistance data request to the network node indicating ‘relative location information: East'. The network node therefore determines a new grid 760 to the east of the current grid 750, this time formed of 2 x 2 grid points 730, and provides LoS-NLoS indication information for this new grid 760 to the UE 100.

In embodiments of the above procedure, the network node can adapt the scope of the grid provided to the UE 100, either or both in terms of spatial scope of the grid (i.e. the size of the area covered by the grid) as well as a size to zoom in on where the UE 100 is located. In both cases these adjustments can be used to reduce signalling bandwidth (i.e. the bandwidth required to signal the LoS-NLoS indication information to the UE 100).

Fig. 7b illustrates another embodiment, where the UE 100 instead provides relative location information within a current grid 770, for example in quadrants upper-left, upper-right, lower-left, lower-right. In this example, the UE 100 first obtains a 4 x 4 grid 770, and the device 100 subsequently provides relative location information to the network node indicating the lower-right of the current grid 770. The network node can then determine a new grid 780 based on the provided relative location information from the UE 100 (which in this case is a 2 x 2 grid). The new grid 780 is provided to the UE 100 by the network node. In this way, the scope of the grid 770/780 can be zoomed/focussed towards the location of the UE 100 without the UE providing its accurate position. In some embodiments, the grid resolution can be finer for a new ('zoomed-in') grid by the UE 100 providing relative location information inside the current grid 770.

Fig. 7c shows two different examples of spatial grids that have respectively different altitude references. Both spatial grids are seen from the side with respect to sloping ground 782, and each contains only one altitude ayer'. The spatial grids are illustrated in a region where the ground 782 is inclining upwards from left to right. Dashed line 784 represents mean sea level (or another reference altitude), from which the altitude information in the spatial grids can be measured (in some embodiments). Spatial grid 786 is a first example of a spatial grid that is defined with altitude information relative to ground level 782, and as such, the grid points in spatial grid 786 do not necessarily relate to the same altitude over a common reference altitude, e.g., mean sea level. Instead, the grid points in spatial grid 786 'track' the changes in altitude of the ground 782. This approach may be suitable or preferable in areas where the UE is only likely to be on or near the ground 782 (e.g. UEs on roads, drones flying at a constant altitude over the ground, etc.). Spatial grid 788 is a second example of a spatial grid 788 that is defined with altitude information relative to mean sea level 784 (or another reference altitude), and as such, the grid points in spatial grid 788 relate to the same altitude as each other over mean sea level (or another reference altitude). Although not shown in Fig. 7c, the grids 786 or 788 can have multiple layers of grid points, with each layer associated with a respective altitude. This approach may be more suitable or preferable where the UE is in an area where the altitude of the UE with respect to the reference altitude can vary, e.g. a drone flying at varying altitude, a UE that could be on different floors in a building, etc.

In some embodiments, the UE 100 can request or indicate, as part of the request for assistance data in step 530, which altitude reference the UE 100 requires the assistance data for. For example, the UE 100 can indicate its current altitude, or provide some other indicator of the altitude if requires LoS-NLoS indication information for. In response to this request, the network node can provide LoS-NLoS indication information appropriate to the indicated altitude. As noted above, the altitude reference indication can comprise an ellipsoid level, mean sea level, ground level, etc.

In some embodiments, the size of the area covered by the LoS-NLoS indication information and/or the resolution of the data points in the LoS-NLoS indication information can depend on the mobility status of the UE 100. For example, if the UE 100 is moving at high speed, the LoS-NLoS indication information might be formed to cover a larger area than if the UE 100 was stationary or moving at low speed. In a similar way, if the UE 100 is moving at high speed and the current position of the UE 100 indicates that it is on a highway, the LoS-NLoS indication information may be formed to relate to further parts of the highway rather than all areas around the UE 100. Likewise, the level of 'zoom' of the grid can depend on the speed of the UE 100, with a higher speed of the UE 100 indicating that the data points in the LoS-NLoS indication information can be quite coarse, whereas a finer level of data points can be provided when the UE is stationary or moving at low speed.

Fig. 8 illustrates another situation in which a UE could require new/updated LoS-NLoS indication information. Fig. 8 shows a network node 810 (which is referred to as a base station in this embodiment) that has a coverage area 820 served by multiple beams 830, 840, 850. Each beam 830, 840, 850 may serve a respective cell in the coverage area 820. As the UE changes its logical location (e.g. served by beam 840 instead of beam 830), it can request new LoS-NLoS indication information for the new location (i.e. the cell served by beam 840). In some embodiments, the change of logical location of the UE can be used by the network to pre-emptively determine and send the new LoS- NLoS indication information to the UE.

Fig. 9 is a flow chart illustrating a method according to various embodiments performed by a UE. The UE may perform the method in response to executing suitably formulated computer readable code. The computer readable code may be embodied or stored on a computer readable medium, such as a memory chip, optical disc, or other storage medium. The computer readable medium may be part of a computer program product. The UE may be as described below with reference to Fig. 12.

In step 901 , the UE receives indication information from a network node. The network node may be any of: a location server (LS); a LMF; an E-SMLC; or a SLP.

The indication information is for use in determining a position of the UE using signals from one or more signal sources. The signal source(s) can comprise any of: satellites; satellites in a GNSS; base stations; base stations in a terrestrial RAN; sources of WiFi signals, and sources of Bluetooth signals.

The indication information indicates whether the UE will have LoS to one or more signal sources at one or more positions.

The indication information may comprise information for each signal source in the one or more signal sources indicating whether the UE will have LoS to that signal source. The indication information may comprise information for each position in the one or more positions indicating whether the UE will have LoS to the one or more signal sources at that position. Alternatively, the indication information can comprise information, for each signal source at each of the one or more positions, indicating whether the UE will have LoS to that signal source at that position.

The one or more positions may be defined by latitude and/or longitude coordinates. Each position may additionally or alternatively be defined by an altitude, an altitude coordinate or by a mapping between altitude and air pressure measurements for a validity area. In this latter embodiment, one or more of the positions may have different altitudes.

The indication information can comprise any one or more of the following: a binary indication of whether or not the UE will have LoS to the one or more signal sources at the one or more positions a binary indication of whether or not the UE will have NLoS to the one or more signal sources at the one or more positions; one of: an indication that the UE will have LoS to the one or more signal sources at the one or more positions, an indication that the UE will not have LoS to the one or more signal sources at the one or more positions, and an indication that it is uncertain whether the UE will have LoS to the one or more signal sources at the one or more positions; one of: an indication that the UE will have NLoS to the one or more signal sources at the one or more positions, an indication that the UE will not have NLoS to the one or more signal sources at the one or more positions, and an indication that it is uncertain whether the UE will have NLoS to the one or more signal sources at the one or more positions; a probability that the UE will have LoS to the one or more signal sources at the one or more positions; and a probability that the UE will have NLoS to the one or more signal sources at the one or more positions.

In addition to the indication information, the UE may also receive duration information that indicates a duration for which the received indication information is valid.

After receiving the indication information, the UE can use the indication information to determine the position of the UE. Using the received indication information may mean prioritising signals for measurement that are from signal sources determined to be in LoS with the UE.

In particular embodiments, the position of the UE can be determined by determining one or more signal sources that are in LoS with the UE based on the received indication information, perform measurements of signals from those one or more signal sources, and determine the position of the UE using the measurements. The measurements of signals may be measurements of the time of flight of the signal from the signal source to the UE.

The method performed by the UE may further comprise the UE sending capability information to the network node. The capability information can indicate a capability of the UE to receive and/or use indication information. The capability information may be sent to the network node in response to receiving a request for capability information.

The indication information received in step 901 may be received from the network node in response to the UE sending a request for indication information. In these embodiments, the method performed by the UE may further comprise sending a request for indication information to the network node.

The method performed by the UE may further comprise the UE sending a request to the network node for updated indication information. The request for updated indication information may comprise relative location information for the UE. The relative location information may comprise any of: an indication of a direction of movement by the UE, an indication of an amount of movement by the UE, an indication of a direction of altitude change by the UE, and/or an amount of altitude change by the UE. Alternatively, the relative location information may comprise any of: an indication of a direction of movement by the UE since the indication information was received from the network node; an amount of movement by the UE since the indication information was received from the network node; an indication of a direction of altitude change by the UE since the indication information was received from the network node; and/or an amount of altitude change by the UE since the indication information was received from the network node.

The request for updated indication information may be sent by the UE if the received indication information is considered invalid or expired. The request for updated indication information may comprise a grid set identity and/or a mobility status for the UE.

Fig. 10 is a flow chart illustrating a method according to various embodiments performed by a network node. The network node may perform the method in response to executing suitably formulated computer readable code. The computer readable code may be embodied or stored on a computer readable medium, such as a memory chip, optical disc, or other storage medium. The computer readable medium may be part of a computer program product. The network node may be as described below with reference to Fig. 13. The network node may be any of: a location server (LS); a LMF; an E-SMLC; or a SLP.

In step 1001 , the network node can send indication information to a UE. The indication information is for use by the UE in determining a position of the UE using signals from one or more signal sources. The signal source(s) can comprise any of: satellites; satellites in a GNSS; base stations; base stations in a terrestrial RAN; sources of WiFi signals, and sources of Bluetooth signals.

In addition to sending the indication information, the network node may also send duration information to the UE that indicates a duration for which the sent indication information is valid.

The method performed by the network node may further comprise the network node receiving capability information from the UE. The capability information can indicate a capability of the UE to receive and/or use indication information. The capability information may be received from the UE in response to sending a request for capability information to the UE.

The indication information may be sent by the network node sent in step 1001 in response to receiving a request for indication information from the UE. In these embodiments, the method performed by the network node may further comprise receiving a request for indication information from the UE.

The method performed by the network node may further comprise the network node receiving a request from the UE for updated indication information. The request for updated indication information may comprise relative location information for the UE. The request for updated indication information may further comprise a grid set identity and/or a mobility status for the UE. The relative location information may comprise any of: an indication of a direction of movement by the UE, an indication of an amount of movement by the UE, an indication of a direction of altitude change by the UE, and/or an amount of altitude change by the UE. Alternatively, the relative location information may comprise any of: an indication of a direction of movement by the UE since the indication information was sent by the network node; an amount of movement by the UE since the indication information was sent by the network node; an indication of a direction of altitude change by the UE since the indication information was sent by the network node; and/or an amount of altitude change by the UE since the indication information was sent by the network node.

The method performed by the network node may further comprise the network node determining updated indication information for the UE based on the received relative location information. The updated indication information can be determined by determining an area that the updated indication information is to relate to based on the received relative location information; determining a size of the area that the updated indication information is to relate to based on the received relative location information; and determining a resolution of the updated indication information based on the received relative location information.

Fig. 11 shows an example of a communication system 1100 in accordance with some embodiments.

In the example, the communication system 1100 includes a telecommunication network 1102 that includes an access network 1104, such as a radio access network (RAN), and a core network 1106, which includes one or more core network nodes 1108. The access network 1104 includes one or more access network nodes, such as access network nodes 1110a and 1110b (one or more of which may be generally referred to as access network nodes 1110), or any other similar 3^rd Generation Partnership Project (3GPP) access node or non-3GPP access point. The access network nodes 1110 facilitate direct or indirect connection of wireless devices (also referred to interchangeably herein as user equipment (UE)), such as by connecting UEs 1112a, 1112b, 1112c, and 1112d (one or more of which may be generally referred to as UEs 1112) to the core network 1106 over one or more wireless connections. The access network nodes 1110 may be, for example, access points (APs) (e.g. radio access points), base stations (BSs) (e.g. radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)).

Unless otherwise indicated, the term ‘network node' is used herein to refer to both access network nodes 1110 and core network nodes 1108.

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

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

In the depicted example, the core network 1106 connects the access network nodes 1110 to one or more hosts, such as host 1116. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 1106 includes one more core network nodes (e.g. core network node 1108) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the wireless devices/UEs, access network nodes, and/or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 1108. Example core network nodes include functions of one or more of a location server (LS), an E-SMLC, a SLP, a Location Management Function (LMF), a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier Deconcealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and/or a User Plane Function (UPF).

The host 1116 may be under the ownership or control of a service provider other than an operator or provider of the access network 1104 and/or the telecommunication network 1102, and may be operated by the service provider or on behalf of the service provider. The host 1116 may host a variety of applications to provide one or more services. Examples of such applications include the provision of live and/or pre-recorded audio/video content, data collection services, for example, retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

As a whole, the communication system 1100 of Fig. 11 enables connectivity between the wireless devices/UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g. 6^th Generation (6G)); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and/or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.

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

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

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

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

Fig. 12 shows a UE 1200 in accordance with some embodiments.

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

A UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to- infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g. a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g. a smart power meter).

The UE 1200 includes processing circuitry 1202 that is operatively coupled via a bus 1204 to an input/output interface 1206, a power source 1208, a memory 1210, a communication interface 1212, and/or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Fig. 12. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

The processing circuitry 1202 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 1210. The processing circuitry 1202 may be implemented as one or more hardware- implemented state machines (e.g. in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 1202 may include multiple central processing units (CPUs). The processing circuitry 1202 may be operable to provide, either alone or in conjunction with other UE 1200 components, such as the memory 1210, to provide UE 1200 functionality. For example, the processing circuitry 1202 may be configured to cause the UE 1202 to perform the methods as described with reference to Figs. 4, 5 or 9.

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

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

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

The memory 1210 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and/or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUlCC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.' The memory 1210 may allow the UE 1200 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 1210, which may be or comprise a device-readable storage medium.

The processing circuitry 1202 may be configured to communicate with an access network or other network using the communication interface 1212. The communication interface 1212 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 1222. The communication interface 1212 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g. another UE or a network node in an access network). Each transceiver may include a transmitter 1218 and/or a receiver 1220 appropriate to provide network communications (e.g. optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 1218 and receiver 1220 may be coupled to one or more antennas (e.g. antenna 1222) and may share circuit components, software or firmware, or alternatively be implemented separately.

In some embodiments, communication functions of the communication interface 1212 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and/or standards, such as IEEE 802.11 , Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol/internet protocol (TCP/IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth. Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 1212, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g. once every 15 minutes if it reports the sensed temperature), random (e.g. to even out the load from reporting from several sensors), in response to a triggering event (e.g. when moisture is detected an alert is sent), in response to a request (e.g. a user initiated request), or a continuous stream (e.g. a live video feed of a patient).

As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or controls a robotic arm performing a medical procedure according to the received input.

A UE, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are devices which are or which are embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door/window sensor, a flood/moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and/or software in dependence on the intended application of the loT device in addition to other components as described in relation to the UE 1200 shown in Fig. 12.

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

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

Fig. 13 shows a network node 1300 in accordance with some embodiments.

As used herein, network node includes equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a UE and/or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access network nodes such as access points (APs) (e.g. radio access points), base stations (BSs) (e.g. radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)). Other examples of network nodes include, but are not limited to, core network nodes such as nodes that include functions of one or more of a location server (LS), an E-SMLC, a SLP, a Location Management Function (LMF), a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and/or a User Plane Function (UPF).

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

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

The network node 1300 includes processing circuitry 1302, a memory 1304, a communication interface 1306, and a power source 1308, and/or any other component, or any combination thereof. The network node 1300 may be composed of multiple physically separate components (e.g. a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 1300 comprises multiple separate components (e.g. BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 1300 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g. separate memory 1304 for different RATs) and some components may be reused (e.g. a same antenna 1310 may be shared by different RATs). The network node 1300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1300, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 1300.

The processing circuitry 1302 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node 1300 components, such as the memory 1304, to provide network node 1300 functionality. For example, the processing circuitry 1302 may be configured to cause the network node to perform the methods as described with reference to Figs. 4, 6 or 10.

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

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

The communication interface 1306 is used in wired or wireless communication of signalling and/or data between network nodes, the access network, the core network, and/or a UE. As illustrated, the communication interface 1306 comprises port(s)/terminal(s) 1316 to send and receive data, for example to and from a network over a wired connection.

Where the network node 1300 is an access network node, the communication interface 1306 also includes radio front-end circuitry 1318 that may be coupled to, or in certain embodiments a part of, the antenna 1310. Where the network node 1300 is a core network node, such as a location server, the core network node may not include radio front-end circuitry 1318 and antenna 1310. Radio front-end circuitry 1318 comprises filters 1320 and amplifiers 1322. The radio front-end circuitry 1318 may be connected to an antenna 1310 and processing circuitry 1302. The radio front-end circuitry may be configured to condition signals communicated between antenna 1310 and processing circuitry 1302. The radio front-end circuitry 1318 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 1318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1320 and/or amplifiers 1322. The radio signal may then be transmitted via the antenna 1310. Similarly, when receiving data, the antenna 1310 may collect radio signals which are then converted into digital data by the radio front-end circuitry 1318. The digital data may be passed to the processing circuitry 1302. In other embodiments, the communication interface may comprise different components and/or different combinations of components.

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

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

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

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

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

Fig. 14 is a block diagram illustrating a virtualization environment 1400 in which functions implemented by some embodiments may be virtualized.

In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 1400 hosted by one or more of hardware nodes, such as a hardware computing device that operates as an access network node, a wireless device/UE, or a core network node. Further, in embodiments in which the virtual node does not require radio connectivity (e.g. a core network node), then the node may be entirely virtualized.

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

Hardware 1404 includes processing circuitry, memory that stores software and/or instructions executable by hardware processing circuitry, and/or other hardware devices as described herein, such as a network interface, input/output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 1406 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 1408a and 1408b (one or more of which may be generally referred to as VMs 1408), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein. The virtualization layer 1406 may present a virtual operating platform that appears like networking hardware to the VMs 1408.

The VMs 1408 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 1406. Different embodiments of the instance of a virtual appliance 1402 may be implemented on one or more of VMs 1408, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment. In the context of NFV, a VM 1408 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 1408, and that part of hardware 1404 that executes that VM, be it hardware dedicated to that VM and/or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 1408 on top of the hardware 1404 and corresponds to the application 1402.

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

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

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

The foregoing merely illustrates the principles of the disclosure. Various modifications and alterations to the described embodiments will be apparent to those skilled in the art in view of the teachings herein. It will thus be appreciated that those skilled in the art will be able to devise numerous systems, arrangements, and procedures that, although not explicitly shown or described herein, embody the principles of the disclosure and can be thus within the scope of the disclosure. Various exemplary embodiments can be used together with one another, as well as interchangeably therewith, as should be understood by those having ordinary skill in the art.

Appendix

In this Appendix additional information is provided relating to ways in which the techniques described herein can be implemented in the relevant 3GPP standards. In particular, the techniques described herein can be implemented in the 3GPP LPP specifications (3GPP TS 37.355 v17.2.0), which are exemplified below. There may also be modifications of stage 2 such as in 3GPP TS 38.305 v17.3.0 and 3GPP TS 36.305 v17.2.0. Proposed changes are marked with underlining.

The specification examples provided here consider GNSS signals, but the examples can be adapted to 3GPP RAT signals (5G, 6G, etc) as well as signals from other radio technologies. GNSS Provide capabilities

GNSS-GenericAssistanceDataSupport

The IE GNSS-GenericAssistanceDataSupport is used by the target device to provide information on supported GNSS generic assistance data types to the location server for each supported GNSS. ,

DBDS-Sup The field is mandatory present if the target device supports BDS-DifferentialCorrections, i otherwise it is not present. This field may only be present i gnss-ID indicates 'bds¹. The field is mandatory present if the target device supports BDS-Grid Model otherwise it is not present. This field may only be present if gnss-ID indicates 'bds¹. The field is mandatory present if the target device supports GNSS-RTK-Observations, otherwise it is not present. Note, support for GNSS-RTK-Observations implies support for GNSS-RTK-CommonObservationlnfo as well. The field is mandatory present if the target device supports GLO-RTK-Biaslnformation, otherwise it is not present. This field may only be present if gnss-ID indicates 'glonass¹. Conditi Explanation

MAC-Sup The field is mandatory present if the target device supports

GNSS-RTK-MAC-CorrectionDifferences, otherwise it is not present.

Res-Sup The field is mandatory present if the target device supports GNSS-RTK-Residuals otherwise it is not present.

FKP-Sup The field is mandatory present if the target device supports GNSS-RTK-FKP-Gradients, otherwise it is not present.

OC-Sup The field is mandatory present if the target device supports GNSS-SSR-OrbitCorrections, otherwise it is not present.

CC-Sup The field is mandatory present if the target device supports GNSS-SSR-ClockCorrections, otherwise it is not present.

CB-Sup The field is mandatory present if the target device supports GNSS-SSR-CodeBias, otherwise it is not present.

URA-Sup The field is mandatory present if the target device supports GNSS-SSR-URA, otherwise it is not present.

PB-Sup The field is mandatory present if the target device supports GNSS-SSR-PhaseBias, i otherwise it is not present.

STEC-Sup The field is mandatory present if the target device supports GNSS-SSR-STEC-Correctiorr, i otherwise it is not present.

Grid-Sup The field is mandatory present if the target device supports

GNSS-SSR-GriddedCorrection, otherwise it is not present. Note, support for GNSS-SSR-GriddedCorrection implies support for GNSS-SSR-CorrectionPoints as well.

DNavIC-Sup The field is mandatory present if the target device supports NavlC-DifferentialCorrections otherwise it is not present. This field may only be present if the gnss-ID indicates 'navic¹.

NavIC-GridModSup The field is mandatory present if the target device supports Navi C-Grid odel otherwise it is not present. This field may only be present if the gnss-ID indicates 'navic¹.

LoS-NLoS-Grid-Sup The field is mandatory present if the target device supports LoS-NLoS-

Griddedlndications; otherwise it is not present. Note, support for LoS-A/LoS-

I Griddedlndications implies support for LoS-NLoS-GridPoints as well,

GNSS Request Assistance Data

GNSS-GenericAssistDataReq

The IE GNSS-GenericAssistDataReq is used by the target device to request assistance data from a location server for one or more specific GNSSs. The specific GNSS for which the assistance data are requested is indicated by the IE

GNSS-ID and (if applicable) by the IE SBAS-ID. Assistance for up to 16 GNSSs can be requested. Conditi Explanation

GLO-CPB The field is mandatory present if the target device requests GLO-RTK-Biaslnformation otherwise it is not present. MAC-Req The field is mandatory present if the target device requests

GNSS-RTK-MAC-CorrectionDifferences, otherwise it is not present.

Res-Req The field is mandatory present if the target device requests GNSS-RTK-Residuals', otherwise it is not present.

FKP-Req The field is mandatory present if the target device requests GNSS-RTK-FKP-Gradients', otherwise it is not present.

OC-Req The field is mandatory present if the target device requests GNSS-SSR-OrbitCorrections', otherwise it is not present.

CC-Req The field is mandatory present if the target device requests GNSS-SSR-ClockCorrections', otherwise it is not present.

CB-Req The field is mandatory present if the target device requests GNSS-SSR-CodeBias', otherwise it is not present.

URA-Req The field is mandatory present if the target device requests G/VSS-SSR-URA; otherwise it is not present.

PB-Req The field is mandatory present if the target device requests G/VSS-SSR-PhaseBias;

I otherwise it is not present.

STEC-Req The field is mandatory present if the target device requests GNSS-SSR-STEC-Correctioir,

I otherwise it is not present

The following LoS-NLoS-GridPointsReq relates to embodiments that do not include altitude information in the request and/or do not take altitude information into account in the provided LoS-NLoS indication information. LoS-NLoS-GridPointsRea

The IE LoS-NLoS-GridPointsReq is used by the target device to request the LoS-NLoS-GridPoints assistance from the location server. LoS-NLoS-GridPointsReq field descriptions> qridPointSetID-Req

This field specifies the ID of the grid point set for which the LoS-NLoS-lndication is requested, optionally with relative location information. relativeLocationlnfo

This field specifies the relative location info in relation to the requested grid. The relative location info can be Inside to narrow down the grid scope

Outside to describe which side of the specified grid the target device wants new grid data

As noted above, in certain embodiments, the request also comprises reference altitude information. For example, this may be represented by a referenceAltitudeType attribute that may indicate an ellipsoid level, mean sea level, ground level, etc. In other embodiments, the request comprises relative location information that relates to the altitude of a current spatial grid such as: above - to indicate that the UE requests spatial data over a spatial grid corresponding to an altitude above the current spatial grid; below - to indicate that the UE requests spatial data over a spatial grid corresponding to an altitude below the current spatial grid. This altitude information can be implemented in LoS-NLoS-G rid Points Req as shown below:

- LoS-NLoS-GridPointsRea

The IE LoS-NLoS-GridPointsReq is used by the target device to request the LoS-NLoS-GridPoints assistance from the location server.

LoS-NLoS-GridPointsReq field descriptions> i qridPointSetID-Req i This field specifies the ID of the grid point set for which the LoS-NLoS-lndication is requested, optionally with relative i location information. i relativeLocationlnfo

I This field specifies the relative location info in relation to the requested grid. The relative location info can be Inside to narrow down the grid scope

Outside to describe which side (north, west, south, east, above, below) of the specified grid the target device wants new grid data i reference AltitudeType i This field specifies the type of altitude reference that is requested by the target device.

GNSS Provide Assistance Data - preferred mode

This is a preferred mode for providing GNSS AD with LoS-NLoS - GNSS-CommonAssistData

The IE GNSS-CommonAssistData is used by the location server to provide assistance data which can be used for any GNSS.

Conditional presence Explanation i RTK i The field is mandatory present if the IE GNSS-RTK Observations is included in IE i i GNSS-GenericAssistData, otherwise it is not present. - GNSS-GenericAssistData

The IE GNSS-GenericAssistData is used by the location server to provide assistance data for a specific GNSS. The specific GNSS for which the provided assistance data are applicable is indicated by the IE GNSS-ID and (if applicable) by the IE SBAS-ID. Assistance for up to 16 GNSSs can be provided.

The following LoS-NLoS-GridPoints relates to embodiments that do not include altitude information in the request and/or do not take altitude information into account in the provided LoS-NLoS indication information. - LoS-NLoS-GridPoints

The IE LoS-NLoS-GridPoints is used by the location server to provide a list of grid point coordinates or an array of correction points ("grid") for which the LoS-NLoS-Griddedlndications are valid. LoS-NLoS-G/'/'dPo/'nts field descriptions qridPointsSetID

This field provides the ID of the LoS-NLoS Grid Point set. It is a regionally unique arbitrary number that is used by the UE to ensure that the LoS-NLoS indications are being applied to the correct set of points. referencePointLatitude

This field specifies the latitude for the reference point, expressed in the range of -90° , +90°, coded as a number between -2¹⁴ and 2¹⁴-1 , coded in 2’s complement binary on 15 bits. The relation between the latitude X in the range [-90°, 90°] and the coded number N is: where J denotes the greatest integer less than or equal to x (floor operator).

For the HstOfGridPoints, the reference point defines the 1^st grid point location.

For the arrayOfGrid Points, the reference point defines the northwest corner of the grid point array. referencePointLonqitude

This field specifies the longitude for the reference point, expressed in the range -180°, +180°, coded as a number between -2¹⁵ and 2¹⁵-1 , coded in 2’s complement binary on 16 bits. The relation between the longitude X in the range [-180°, 180°) and the coded number N is:

For the arrayOfGrid Points, the reference point defines the northwest corner of the grid point array. relativeLocationsList

This field specifies the 2^nd, 3^rd, .... 64^th grid point location. deltaNorth

This field specifies the delta value in the north direction of this grid point location relative to the previous point on the list or the reference point in the case of the first additional point, defined as "grid point location" minus "previous grid point location" in units of meters. Note scale factor FFS.. deltaEast

This field specifies the delta value in the east direction of this grid point location relative to the previous point on the list or the reference point in the case of the first additional point, defined as "grid point location" minus "previous correction point location" in units of meters. Note scale factor FFS. numberOfStepsNorth, numberOfStepsEast

These fields specify the number of steps for north and east direction respectively. stepOfNorth, stepOfNorth

These fields specify the spacing of the grid points for north and east respectively. The unit is meters and scale factor FFS. bitmaskOfGrids

This field specifies the availability of grid data at the grid points in the array. If a specific bit is enabled (set to '1 '), the grid is available. Only the first numberOfStepsNorth^numberOfStepsEast bits are used, the remainder are set to 'O'. Starting with the northwest corner of the array (top left on a north oriented map) the grid points are enumerated with row precedence - first row west to east, second row west to east, until last row west to east - ending with the southeast corner of the array. If the field is omitted all grid points are used and none omitted.

The following LoS-NLoS-GridPoints relates to embodiments that do include altitude information in the request and/or do take altitude information into account in the provided LoS-NLoS indication information. The IE LoS-NLoS-GridPoints is used by the location server to provide a list of grid point coordinates or an array of correction points ("grid") for which the LoS-NLoS-Griddedlndications are valid.

>

LoS-NLoS-GridPoints field descriptions qridPointsSetID

This field specifies the latitude for the reference point, expressed in the range of -90° , +90°, coded as a number between -2¹⁴ and 2¹⁴-1 , coded in 2's complement binary on 15 bits. The relation between the latitude X in the range [-90°, 90°] and the coded number N is: where J denotes the greatest integer less than or equal to x (floor operator).

This field specifies the longitude for the reference point, expressed in the range -180°, +180°, coded as a number between -2¹⁵ and 2¹⁵-1 , coded in 2's complement binary on 16 bits. The relation between the longitude X in the range [-180°, 180°) and the coded number N is:

For the arrayOfGrid Points, the reference point defines the northwest corner of the grid point array. >

> LoS-lVLoS-G/'/dPo/nts field descriptions> relativeLocationsList

This field specifies the 2^nd, 3^rd . 64^th grid point location. deltaNorth

This field specifies the delta value in the east direction of this grid point location relative to the previous point on the list i or the reference point in the case of the first additional point, defined as "grid point location" minus "previous correction I point location" in units of meters. Note scale factor FFS. numberOfStepsNorth, numberOfStepsEast

This field specifies the availability of grid data at the horizontal grid points in the array, and applies to all altitude layers I of the grid. If a specific bit is enabled (set to '1'), the grid is available. Only the first numberOfStepsNorthxnumberOfStepsEast bits are used, the remainder are set to 'O'. Starting with the northwest corner of the array (top left on a north oriented map) the grid points are enumerated with row precedence - first row west to east, second row west to east, until last row west to east - ending with the southeast corner of the array. If the i field is omitted all grid points are used and none omitted. referenceAltitudeType

This field specifies the type of altitude reference that is used to describe the altitude properties of the grid. referenceAltitude

This field specifies the altitude of the upmost layer of the grid relative to the reference altitude. stepAltitude

This field specifies the difference in altitude between the upper and lower altitude layer if the grid. If this field is not present, the grid represents only one altitude layer. The values n05, n1 , n2, n3, n4, n5, n10, n20 encodes 0.5, 1 , 2, 3, 4, 5, 10, 20 meters respectively. uppefValidityStepA Ititude

This field, if present, specifies the upper validity altitude relative to the reference altitude, indicating that the data associated to the spatial grid is valid for device altitudes up to the upper validity altitude. The upper validity altitude is (referenceAltitude + upperValidityStepAltitude) in meters with an encoding described for the stepAltitude field. lowerValidityStepAltitude

This field, if present, specifies the lower validity altitude relative to the lowest grid layer altitude, indicating that the data i associated to the spatial grid is valid for device altitudes down to the lower validity altitude. The lower validity altitude is (referenceAltitude - stepAltitude - lowerValidityStepAltitude) in meters with an encoding described for the stepAltitude field. If the field stepAltitude is not present, then the lower validity altitude is (referenceAltitude - lowerValidityStepAltitude) in meters.

>

The following LoS-NLoS-Griddedlndications relates to embodiments that do not include altitude information in the request and/or do not take altitude information into account in the provided LoS-NLoS indication information.

>

> LoS-NLoS-Griddedlndications field descriptions> qridPointsSetID

This field provides the ID of the LoS-NLoS Grid Point set. It is a regionally unique arbitrary number that is used by the UE to ensure that the LoS-NLoS indications are being applied to the correct set of points. qridList

This field provides the LoS-NLoS indications for up to 64 g rid points defined in IE LoS-NLoS-GridPoints.

If the IE LoS-NLoS-GridPoints, which belongs to the qridPointSetID, includes the HstOfGridPoints, the qridList includes the same number of entries, and listed in the same order, as in the HstOfGridPoints.

If the IE LoS-NLoS-GridPoints, which belongs to this qridPointSetID, includes the arrayOfGridPointsthe qridList includes the same number of entries, and listed in the same order, as defined by the enabled bits in the bitmaskOfGrids. svID

This field specifies the GNSS satellite forwhich the LoS-NLoS indications are provided. ios

>

The following LoS-NLoS-Griddedlndications relates to embodiments that do include altitude information in the request and/or do take altitude information into account in the provided LoS-NLoS indication information. In this example, the data can be represented as follows, where the GridList is extended to accommodate data over up to two altitude layers. In addition, the LosInfoList is a sequence over multiple satellites, each with a LoSInfoElement.

LoS-NLoS-Griddedlndications The IE LoS-NLoS-Griddedlndications is used by the location server to provide GNSS LoS NLoS indication information. The parameters provided in IE LoS-NLoS-Griddedlndications apply to all GNSSs.

>

> LoS-NLoS-Griddedlndications field descriptions> qridPointsSetID

This field provides the LoS-NLoS indications for up to 128 grid points (up to 64 grid points per altitude layer) defined in IE LoS-NLoS-GridPoints.

If the IE LoS-NLoS-GridPoints, which belongs to this qridPointSetID, includes the arrayOfGridPointsthe qridList includes the same number of entries, and listed in the same order, as defined by the enabled bits in the bitmaskOfGrids. The upmost grid layer is populated first, followed by the lower layer. svID

This field specifies the GNSS satellite forwhich the LoS-NLoS indications are provided. los, nlos, los-Probability, nLOS-Probability

Different ways to represent the LoS-NLoS indication information

>

Alternative grid defined in lat-lonq

Extend the GNSS-SSR-CorrectionPoints

An example embodiment where the satellite signals prediction of LOS/NLOS in a certain area is mapped to GNSS SSR correction points. The IE GNSS-SSR-CorrectionPoints is used by the location server to provide a list of correction point coordinates or an array of correction points ("grid") for which the GNSS SSR GriddedCorrection are valid.

GNSS-SSR-CorrectionPoints field descriptions i correctionPointSetID i This field provides the ID of the Atmospheric Correction Point set. It is a regionally unique arbitrary number that is

: used by the UE to ensure that the atmospheric corrections are being applied to the correct set of points. i referencePointLatitude i This field specifies the latitude for the reference point, expressed in the range of -90° , +90°, coded as a number i between -2¹⁴ and 2¹⁴-1 , coded in 2's complement binary on 15 bits. The relation between the latitude X in the range

: [-90°, 90°] and the coded number N is:

: where denotes the greatest integer less than or equal to x (floor operator). i For the HstOfCorrectionPoints, the reference point defines the 1^st correction point location.

: For the arrayOfCorrectionPoints, the reference point defines the northwest corner of the correction point array. i referencePointLongitude

: This field specifies the longitude for the reference point, expressed in the range -180°, +180°, coded as a number i between -2¹⁵ and 2¹⁵-1 , coded in 2's complement binary on 16 bits. The relation between the longitude X in the range i [-180°, 180°) and the coded number N is:

: For the HstOfCorrectionPoints, the reference point defines the 1^st correction point location. i For the arrayOfCorrectionPoints, the reference point defines the northwest corner of the correction point array.

: relativeLocationsList

: This field specifies the 2^nd, 3^rd 64^th correction point location.

: deltaLatitude i This field specifies the delta value in latitude of this correction point location relative to the previous point on the list or : the reference point in the case of the first additional point, defined as "correction point location" minus "previous : correction point location" in units of 0.01 degrees.

: deltaLongitude

: This field specifies the delta value in longitude of this correction point location relative to the previous point on the list i or the reference point in the case of the first additional point, defined as "correction point location" minus "previous : correction point location" in units of 0.01 degrees. i numberOfStepsLatitude, numberOfStepsLongitude

: These fields specify the number of steps for latitude and longitude direction respectively. i stepOfLatitude, stepOfLongitude

: These fields specify the spacing of the correction points for latitude and longitude respectively. The unit and scale i factor is 0.01 degrees.

: bitmaskOfGrids i This field specifies the availability of correction data at the correction points in the array. If a specific bit is enabled (set : to '1 '), the correction is available. Only the first numberOfStepsLatitude^numberOfStepsLongitude bits are used, the i remainder are set to 'O'. Starting with the northwest corner of the array (top left on a north oriented map) the correction i points are enumerated with row precedence - first row west to east, second row west to east, until last row west to : east - ending with the southeast corner of the array. If the field is omitted all correction points are used and none i omitted.

: los-Nlos-GNSS-SSR-CorrectionList i This field indicates whether a space vehicle (GNSS satellite) is LOS or NLOS in the relative area provided by the SSR : correction. Each SSR grid correction relative point (delta long, delta lat area) has information about 64 space vehicle i information on LOS/NLOS status in the area.

/os-/V/os-G/VSS-SSR-ArrayL/st i This field indicates whether a space vehicle (GNSS satellites) is LOS or NLOS in the area provided by the array list. There are advantages as well as disadvantages of using the SSR grid correction point. The advantage is that no new grid information has to be defined and existing grid point of SSR can be reused. The disadvantage is that the GNSS satellites (LOS/NLOS) would be tied to SSR grid and if the network (NW) is not providing the SSR correction or do not have provisioning of supporting SSR then provisioning of GNSS Satellite LOS/NLOS classification would be difficult to realize.

PosSIB

Alternatively, a new posSIB or SIB can be defined or an existing SIB used to relay this information. The example below provides the information about LOS/NLOS information on different cells. This can be extended to show per area (group of cells), tracking area, beam level (communication or positioning reference signal), resource level, resource set level or TRP level.

Below is an example. posSIBX SIBX contains GNSS Satellite LOS/NLOS information on different cells. posS/BX information element

> s o sa e es w c are e er or n e ce . EMBODIMENTS

Group A Embodiments

1 . A method performed by a user equipment, UE, the method comprising: receiving, from a network node, indication information for use in determining a position of the UE using signals from one or more signal sources, wherein the indication information indicates whether the UE will have Line of Sight, LoS, to one or more signal sources at one or more positions.

2. The method of embodiment 1 , wherein the one or more signal sources comprise any of: satellites; satellites in a Global Navigation Satellite System, GNSS; base stations; base stations in a terrestrial radio access network, RAN; sources of WiFi signals, and sources of Bluetooth signals.

3. The method of embodiment 1 or 2, wherein the indication information comprises information for each signal source in the one or more signal sources indicating whether the UE will have LoS to that signal source.

4. The method of embodiment 1 , 2 or 3, wherein the indication information comprises information for each position in the one or more positions indicating whether the UE will have LoS to the one or more signal sources at that position.

5. The method of embodiment 1 , 2 or 3, wherein the indication information comprises information, for each signal source at each of the one or more positions indicating whether the UE will have LoS to that signal source at that position.

6. The method of embodiment 4 or 5, wherein the one or more positions are defined by latitude and/or longitude coordinates.

7. The method of embodiment 4, 5 or 6, wherein each position is defined by an altitude, an altitude coordinate or by a mapping between altitude and air pressure measurements for a validity area.

8. The method of embodiment 7, wherein one or more of the positions have different altitudes.

9. The method of any of embodiments 1-8, wherein the indication information comprises any of: a binary indication of whether or not the UE will have LoS to the one or more signal sources at the one or more positions; a binary indication of whether or not the UE will have non-LoS, NLoS, to the one or more signal sources at the one or more positions; one of: an indication that the UE will have LoS to the one or more signal sources at the one or more positions, an indication that the UE will not have LoS to the one or more signal sources at the one or more positions, and an indication that it is uncertain whether the UE will have LoS to the one or more signal sources at the one or more positions; one of: an indication that the UE will have NLoS to the one or more signal sources at the one or more positions, an indication that the UE will not have NLoS to the one or more signal sources at the one or more positions, and an indication that it is uncertain whether the UE will have NLoS to the one or more signal sources at the one or more positions; a probability that the UE will have LoS to the one or more signal sources at the one or more positions. a probability that the UE will have NLoS to the one or more signal sources at the one or more positions.

10. The method of any of embodiments 1-9, wherein the UE further receives duration information that indicates a duration for which the received indication information is valid.

11 . The method of any of embodiments 1-10, wherein the method further comprises: using the received indication information to determine the position of the UE.

12. The method of embodiment 11, wherein the step of using the received indication information comprises: determining one or more signal sources that are in LoS with the UE based on the received indication information; performing measurements of signals from the determined one or more signal sources; and determining the position of the UE using the measurements.

13. The method of embodiment 12, wherein the measurements of signals are measurements of the time of flight of the signal from the signal source to the UE.

14. The method of embodiment 12 or 13, wherein the step of using the received indication information further comprises prioritising signals for measurement that are from signal sources determined to be in LoS with the UE.

15. The method of any of embodiments 1-13, wherein the method further comprises: sending capability information to the network node, wherein the capability information indicates a capability of the UE to receive and/or use indication information.

16. The method of embodiment 15, wherein the capability information is sent to the network node in response to receiving a request for capability information. 17. The method of any of embodiments 1-16, wherein the indication information is received from the network node in response to the UE sending a request for indication information.

18. The method of any of embodiments 1-17, wherein the method further comprises: sending a request for indication information to the network node.

19. The method of any of embodiments 1-18, wherein the method further comprises: sending a request to the network node for updated indication information.

20. The method of embodiment 19, wherein the request for updated indication information comprises relative location information for the UE.

21. The method of embodiment 20, wherein the relative location information comprises any of: an indication of a direction of movement by the UE, an indication of an amount of movement by the UE, an indication of a direction of altitude change by the UE, and/or an amount of altitude change by the UE.

22. The method of embodiment 20, wherein the relative location information comprises any of: an indication of a direction of movement by the UE since the indication information was received from the network node; an amount of movement by the UE since the indication information was received from the network node; an indication of a direction of altitude change by the UE since the indication information was received from the network node; and/or an amount of altitude change by the UE since the indication information was received from the network node.

23. The method of any of embodiments 19-22, wherein the request for updated indication information is sent if the received indication information is considered invalid or expired.

24. The method of any of embodiments 19-23, wherein the request for updated indication information comprises a grid set identity.

25. The method of any of embodiments 19-24, wherein the request for updated indication information further comprises a mobility status for the UE. 26. The method of any of embodiments 1-25, wherein the network node is any of: a location server, LS; a Location Management Function, LMF; a Evolved Serving Mobile Location Center, E-SMLC; or a Secure UserPlane Location, SUPL, Location Platform, SLP.

Group B Embodiments

27. A method performed by a network node, the method comprising: sending, to a user equipment, UE, indication information for use by the UE in determining a position of the UE using signals from one or more signal sources, wherein the indication information indicates whether the UE will have Line of Sight, LoS, to one or more signal sources at one or more positions.

28. The method of embodiment 27, wherein the one or more signal sources comprise any of: satellites; satellites in a Global Navigation Satellite System, GNSS; base stations; base stations in a terrestrial radio access network, RAN; sources of WiFi signals, and sources of Bluetooth signals.

29. The method of embodiment 27 or 28, wherein the indication information comprises information for each signal source in the one or more signal sources indicating whether the UE will have LoS to that signal source.

30. The method of embodiment 27, 28 or 29, wherein the indication information comprises information for each position in the one or more positions indicating whether the UE will have LoS to the one or more signal sources at that position.

31 . The method of embodiment 27, 28 or 29, wherein the indication information comprises information, for each signal source at each of the one or more positions indicating whether the UE will have LoS to that signal source at that position.

32. The method of embodiment 30 or 31 , wherein the one or more positions are defined by latitude and/or longitude coordinates.

33. The method of embodiment 30, 31 or 32, wherein each position is defined by an altitude or an altitude coordinate or by a mapping between altitude and air pressure measurements for a validity area.

34. The method of embodiment 33, wherein one or more of the positions have different altitudes.

35. The method of any of embodiments 27-34, wherein the indication information comprises any of: a binary indication of whether or not the UE will have LoS to the one or more signal sources at the one or more positions; a binary indication of whether or not the UE will have non-LoS, NLoS, to the one or more signal sources at the one or more positions; one of: an indication that the UE will have LoS to the one or more signal sources at the one or more positions, an indication that the UE will not have LoS to the one or more signal sources at the one or more positions, and an indication that it is uncertain whether the UE will have LoS to the one or more signal sources at the one or more positions; one of: an indication that the UE will have NLoS to the one or more signal sources at the one or more positions, an indication that the UE will not have NLoS to the one or more signal sources at the one or more positions, and an indication that it is uncertain whether the UE will have NLoS to the one or more signal sources at the one or more positions; a probability that the UE will have LoS to the one or more signal sources at the one or more positions. a probability that the UE will have NLoS to the one or more signal sources at the one or more positions.

36. The method of any of embodiments 27-35, wherein the network node further sends duration information to the UE that indicates a duration for which the sent indication information is valid.

37. The method of any of embodiments 27-36, wherein the method further comprises: receiving capability information from the UE, wherein the capability information indicates a capability of the UE to receive and/or use indication information.

38. The method of embodiment 37, wherein the capability information is received from the UE in response to sending a request for capability information to the UE.

39. The method of any of embodiments 27-38, wherein the indication information is sent to the UE in response to receiving a request for indication information from the UE.

40. The method of any of embodiments 27-39, wherein the method further comprises: receiving, from the UE, a request for indication information.

41 . The method of any of embodiments 27-40, wherein the method further comprises: receiving, from the UE, a request for updated indication information. 42. The method of embodiment 41, wherein the request for updated indication information comprises relative location information for the UE.

43. The method of embodiment 42, wherein the relative location information comprises any of: an indication of a direction of movement by the UE, an indication of an amount of movement by the UE, an indication of a direction of altitude change by the UE, and/or an amount of altitude change by the UE.

44. The method of embodiment 42, wherein the relative location information comprises any of: an indication of a direction since the indication information was sent by the network node; an amount of movement by the UE since the indication information was sent by the network node; an indication of a direction of altitude change by the UE since the indication information was sent by the network node; and/or an amount of altitude change by the UE since the indication information was sent by the network node.

45. The method of any of embodiments 42-44, wherein the method further comprises: determining updated indication information for the UE based on the received relative location information.

46. The method of embodiment 45, wherein the step of determining updated indication information comprises: determining an area to which the updated indication information is to relate based on the received relative location information; determining a size of the area to which the updated indication information is to relate based on the received relative location information; determining a resolution of the updated indication information based on the received relative location information.

47. The method of any of embodiments 41-46, wherein the request for updated indication information comprises a grid set identity.

48. The method of any of embodiments 41-47, wherein the request for updated indication information further comprises a mobility status for the UE.

49. The method of any of embodiments 27-48, wherein the network node is any of: a location server, LS; a Location Management Function, LMF; a Evolved Serving Mobile Location Center, E-SMLC; or a Secure UserPlane Location, SUPL, Location Platform, SLP. Group C Embodiments

50. A computer program product comprising a computer readable medium having computer readable code embodied therein, the computer readable code being configured such that, on execution by a suitable computer or processor, the computer or processor is caused to perform the method of any of the Group A embodiments or the Group B embodiments.

51 . A user equipment, UE, configured to perform the method of any of the Group A embodiments.

52. A user equipment, UE, comprising a processor and a memory, said memory containing instructions executable by said processor whereby said UE is operative to perform the method of any of the Group A embodiments.

53. A network node, configured to perform the method of any of the Group B embodiments.

54. A network node comprising a processor and a memory, said memory containing instructions executable by said processor whereby said network node is operative to perform the method of any of the Group B embodiments.

55. A user equipment, comprising: processing circuitry configured to cause the user equipment to perform any of the steps of any of the Group A embodiments; and power supply circuitry configured to supply power to the processing circuitry.

56. A network node, the network node comprising: processing circuitry configured to cause the network node to perform any of the steps of any of the Group B embodiments; power supply circuitry configured to supply power to the processing circuitry.

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

Claims

1 . A method performed by a user equipment, U E, the method comprising: receiving, from a network node, indication information for use in determining a position of the UE using signals from one or more signal sources, wherein the indication information indicates whether the UE will have Line of Sight, LoS, to one or more signal sources at one or more positions.

2. The method of claim 1 , wherein the one or more signal sources comprise any of: satellites; satellites in a Global Navigation Satellite System, GNSS; base stations; base stations in a terrestrial radio access network, RAN; sources of WiFi signals, and sources of Bluetooth signals.

3. The method of claim 1 or 2, wherein the indication information comprises information for each signal source in the one or more signal sources indicating whether the UE will have LoS to that signal source.

4. The method of claim 1, 2 or 3, wherein the indication information comprises information for each position in the one or more positions indicating whether the UE will have LoS to the one or more signal sources at that position.

5. The method of claim 1, 2 or 3, wherein the indication information comprises information for each signal source at each of the one or more positions indicating whether the UE will have LoS to that signal source at that position.

6. The method of claim 4 or 5, wherein the one or more positions are defined by latitude and/or longitude coordinates.

7. The method of claim 4, 5 or 6, wherein each position is defined by an altitude, an altitude coordinate or by a mapping between altitude and air pressure measurements for a validity area.

8. The method of claim 7, wherein one or more of the positions have different altitudes.

9. The method of any of claims 1-8, wherein the indication information comprises any of: a binary indication of whether or not the UE will have LoS to the one or more signal sources at the one or more positions; a binary indication of whether or not the UE will have non-LoS, NLoS, to the one or more signal sources at the one or more positions; one of: an indication that the UE will have LoS to the one or more signal sources at the one or more positions, an indication that the UE will not have LoS to the one or more signal sources at the one or more positions, and an indication that it is uncertain whether the UE will have LoS to the one or more signal sources at the one or more positions; one of: an indication that the UE will have NLoS to the one or more signal sources at the one or more positions, an indication that the UE will not have NLoS to the one or more signal sources at the one or more positions, and an indication that it is uncertain whether the UE will have NLoS to the one or more signal sources at the one or more positions; a probability that the UE will have LoS to the one or more signal sources at the one or more positions. a probability that the UE will have NLoS to the one or more signal sources at the one or more positions.

10. The method of any of claims 1-9, wherein the UE further receives duration information that indicates a duration for which the received indication information is valid.

11. The method of any of claims 1-10, wherein the method further comprises: using the received indication information to determine the position of the UE.

12. The method of claim 11, wherein the step of using the received indication information comprises: determining one or more signal sources that are in LoS with the UE based on the received indication information; performing measurements of signals from the determined one or more signal sources; and determining the position of the UE using the measurements.

13. The method of claim 12, wherein the measurements of signals are measurements of the time of flight of the signal from the signal source to the UE.

14. The method of claim 12 or 13, wherein the step of using the received indication information further comprises prioritising signals for measurement that are from signal sources determined to be in LoS with the UE.

15. The method of any of claims 1-14, wherein the method further comprises: sending capability information to the network node, wherein the capability information indicates a capability of the UE to receive and/or use indication information.

16. The method of claim 15, wherein the capability information is sent to the network node in response to receiving a request for capability information.

17. The method of any of claims 1-16, wherein the indication information is received from the network node in response to the UE sending a request for indication information.

18. The method of any of claims 1-17, wherein the method further comprises: sending a request for indication information to the network node.

19. The method of any of claims 1-18, wherein the method further comprises: sending a request to the network node for updated indication information.

20. The method of claim 19, wherein the request for updated indication information comprises relative location information for the UE.

21 . The method of claim 20, wherein the relative location information comprises any of: an indication of a direction of movement by the UE, an indication of an amount of movement by the UE, an indication of a direction of altitude change by the UE, and/or an amount of altitude change by the UE.

22. The method of claim 20, wherein the relative location information comprises any of: an indication of a direction of movement by the UE since the indication information was received from the network node; an amount of movement by the UE since the indication information was received from the network node; an indication of a direction of altitude change by the UE since the indication information was received from the network node; and/or an amount of altitude change by the UE since the indication information was received from the network node.

23. The method of any of claims 19-22, wherein the request for updated indication information is sent if the received indication information is considered invalid or expired.

24. The method of any of claims 19-23, wherein the request for updated indication information comprises a grid set identity.

25. The method of any of claims 19-24, wherein the request for updated indication information further comprises a mobility status for the UE.

26. The method of any of claims 1-25, wherein the network node is any of: a location server, LS; a Location Management Function, LMF; a Evolved Serving Mobile Location Center, E-SMLC; or a Secure UserPlane Location, SUPL, Location Platform, SLP.

28. The method of claim 27, wherein the one or more signal sources comprise any of: satellites; satellites in a Global Navigation Satellite System, GNSS; base stations; base stations in a terrestrial radio access network, RAN; sources of WiFi signals, and sources of Bluetooth signals.

29. The method of claim 27 or 28, wherein the indication information comprises information for each signal source in the one or more signal sources indicating whether the UE will have LoS to that signal source.

30. The method of claim 27, 28 or 29, wherein the indication information comprises information for each position in the one or more positions indicating whether the UE will have LoS to the one or more signal sources at that position.

31. The method of claim 27, 28 or 29, wherein the indication information comprises information, for each signal source at each of the one or more positions indicating whether the UE will have LoS to that signal source at that position.

32. The method of claim 30 or 31, wherein the one or more positions are defined by latitude and/or longitude coordinates.

33. The method of claim 30, 31 or 32, wherein each position is defined by an altitude or an altitude coordinate or by a mapping between altitude and air pressure measurements for a validity area.

34. The method of claim 33, wherein one or more of the positions have different altitudes.

35. The method of any of claims 27-34, wherein the indication information comprises any of: a binary indication of whether or not the UE will have LoS to the one or more signal sources at the one or more positions; a binary indication of whether or not the UE will have non-LoS, NLoS, to the one or more signal sources at the one or more positions; one of: an indication that the UE will have LoS to the one or more signal sources at the one or more positions, an indication that the UE will not have LoS to the one or more signal sources at the one or more positions, and an indication that it is uncertain whether the UE will have LoS to the one or more signal sources at the one or more positions; one of: an indication that the UE will have NLoS to the one or more signal sources at the one or more positions, an indication that the UE will not have NLoS to the one or more signal sources at the one or more positions, and an indication that it is uncertain whether the UE will have NLoS to the one or more signal sources at the one or more positions; a probability that the UE will have LoS to the one or more signal sources at the one or more positions. a probability that the UE will have NLoS to the one or more signal sources at the one or more positions.

36. The method of any of claims 27-35, wherein the network node further sends duration information to the UE that indicates a duration for which the sent indication information is valid.

37. The method of any of claims 27-36, wherein the method further comprises: receiving capability information from the UE, wherein the capability information indicates a capability of the UE to receive and/or use indication information.

38. The method of claim 37, wherein the capability information is received from the UE in response to sending a request for capability information to the UE.

39. The method of any of claims 27-38, wherein the indication information is sent to the UE in response to receiving a request for indication information from the UE.

40. The method of any of claims 27-39, wherein the method further comprises: receiving, from the UE, a request for indication information.

41 . The method of any of claims 27-40, wherein the method further comprises: receiving, from the UE, a request for updated indication information.

42. The method of claim 41, wherein the request for updated indication information comprises relative location information for the UE.

43. The method of claim 42, wherein the relative location information comprises any of: an indication of a direction of movement by the UE, an indication of an amount of movement by the UE, an indication of a direction of altitude change by the UE, and/or an amount of altitude change by the UE.

44. The method of claim 42, wherein the relative location information comprises any of: an indication of a direction since the indication information was sent by the network node; an amount of movement by the UE since the indication information was sent by the network node; an indication of a direction of altitude change by the UE since the indication information was sent by the network node; and/or an amount of altitude change by the UE since the indication information was sent by the network node.

45. The method of any of claims 42-44, wherein the method further comprises: determining updated indication information for the UE based on the received relative location information.

46. The method of claim 45, wherein the step of determining updated indication information comprises: determining an area to which the updated indication information is to relate based on the received relative location information; determining a size of the area to which the updated indication information is to relate based on the received relative location information; determining a resolution of the updated indication information based on the received relative location information.

47. The method of any of claims 41-46, wherein the request for updated indication information comprises a grid set identity.

48. The method of any of claims 41-47, wherein the request for updated indication information further comprises a mobility status for the UE.

49. The method of any of claims 27-48, wherein the network node is any of: a location server, LS; a Location Management Function, LMF; a Evolved Serving Mobile Location Center, E-SMLC; or a Secure UserPlane Location, SUPL, Location Platform, SLP.

50. A computer program product comprising a computer readable medium having computer readable code embodied therein, the computer readable code being configured such that, on execution by a suitable computer or processor, the computer or processor is caused to perform the method of any of the Group A claims or the Group B claims.

51 . A user equipment, UE, configured to perform the method of any of claims 1-26.

52. A user equipment, UE, comprising a processor and a memory, said memory containing instructions executable by said processor whereby said UE is operative to perform the method of any of claims 1-26.

53. A network node, configured to perform the method of any of claims 27-49.

54. A network node comprising a processor and a memory, said memory containing instructions executable by said processor whereby said network node is operative to perform the method of any of claims 27-49.