Indication information for determining location

Abstract

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

Description

Technical Field

[0001] The present disclosure relates to the provision of information for use by a User Equipment (UE) in determining the UE's location using signals from one or more signal sources. Background Art

[0002] Positioning in 4th Generation (4G) / Long Term Evolution (LTE) / Evolved Packet Core (EPC) and 5th Generation (5G) / New Radio (NR) / 5G Core (5GC) is performed by Figure 1 15. The present invention provides an architecture support in which the direct interaction between the user equipment (UE) 100 and the location server 130 is via the LTE Positioning Protocol (LPP) 151. In addition, there is also interaction between the location server 130 and the serving radio base station 110 via the LPPa protocol 152, which is supported to some extent by the interaction 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 the 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.

[0003] The location server 130 is an entity in the network architecture that is responsible for collecting information / measurements from the UE 100 and / or radio base stations 110 (or more generally, the Radio Access Network (RAN)) and calculating the location of the UE 100 based on the information / measurements.

[0004] In 4G / LTE / EPC and 5G / NR / 5GC, the servers / nodes / functions / interfaces / protocols mentioned above are as follows:

[0005] The names are shown in Table 1:

[0006]

[0007] Table 1

[0008] In both cases, the location server may also interact directly with the UE via user plane (UP) communications carrying the LPP 151 using signaling defined by the Open Mobile Alliance (OMA) Secure User Plane Location (SUPL) or some other user plane signaling. In the case of SUPL, the location server is denoted as a SUPL Location Platform (SLP) and the UE is denoted as a SUPL Enabled Terminal (SET).

[0009] There are several options for the interface, signaling, and message handling on the third interface 155 between the location server 130 and the correction data provider 140. One option is to use the message handling defined by the user plane signaling protocol Network Transport of RTCM over Internet Protocol (NTRIP) defined by the Radio Technical Commission for Maritime (RTCM) Special Committee 104. The RTCMSC 104 originally defined differential corrections for GNSS.

[0010] The 3rd Generation Partnership Project (3GPP) Release (Rel.) 9 introduced support for assisted global navigation satellite systems (GNSS), and the scope of assistance data has been refined through some releases. In Rel. 15, support for real-time kinematic (RTK) GNSS was introduced. Assistance data is generated based on observations from one or more reference stations and GNSS receivers capable of measuring signals from one or more satellite systems, where a reference station is a node with a known position and a known antenna configuration, where a satellite system includes one or more satellites and each satellite transmits one or more signals. Typically, GNSS RTK assistance data is provided by a separate function, namely a correction data provider or a network RTK (NRTK) server (140). GNSS stands for General Purpose System, examples of which are Global Positioning System (GPS), Global Navigation Satellite System (GLONASS), Galileo (GALILEO) and BeiDou (BeiDou). These systems are based on multiple GNSS satellites, each of which transmits a GNSS signal associated with a specific GNSS signal identifier. The satellites follow a customized orbit around the earth.

[0011] Figure 2 The different 4G / LTE / EPC and 5G / NR / 5GC entities are illustrated in a more complete and general architecture 200 . Figure 2 The nodes and functions on the left hand side are typically related to the 4G / LTE / EPC architecture, and Figure 2 The nodes and functions on the right-hand side are typically related to the 5G / NR / 5GC architecture.

[0012] 5G signal-based 5G positioning methods are implemented using downlink positioning reference signals (PRSs) associated with specific radio resources. These PRSs can be transmitted using directional radio beams. Each PRS is associated with an identifier. One or more PRSs are transmitted from a specific transmission point associated with radio base station 110.

[0013] Positioning methods rely on measurements, and several positioning methods rely on measurements by the UE, whose position is to be determined, of GNSS signals, WiFi signals, Bluetooth signals, beacon signals, signals depending on the Radio Access Technology (RAT), etc. Such measurements are subject to errors or alarming events, and a subset of such errors or alarming events are due to the local environment of the UE.

[0014] The information element (IE) SV-ID is used to identify a specific GNSS satellite. The interpretation of the SV-ID depends on the GNSS-ID.

[0015]

[0016] Explanation of satellite-id

[0017] Summary of the Invention

[0018] There are certain challenges.

[0019] Figure 3a and 3b A typical example of the effect of the local environment on the received signal in an urban canyon (e.g. between buildings) is shown. Figure 3a In FIG, some GNSS signals from satellites 160 are received by UE 100 via a line-of-sight (LoS) path, and some GNSS signals are received via a reflected non-line-of-sight path (NLoS). Figure 3b A similar situation is illustrated for a terrestrial radio network, where some signals from the radio base station 110 are received via a line-of-sight path and some signals are received via a reflected non-line-of-sight path. In both cases, the time of flight of the non-line-of-sight signal is not representative of the distance between the transmitter and the UE, leading to measurement errors due to the UE's local environment.

[0020] The difficulty with the LoS / NLoS problem is that it potentially has a degrading effect on positioning performance. At the very least, the UE 100 needs to be aware of and attempt to identify NLoS satellites via complex and lengthy calculations, which may be impossible for small and / or low-complexity UEs.

[0021] This may also imply that the UE estimates a position that does not match the expected uncertainty, meaning that the UE may assume a more accurate position than the actual estimated position, which can potentially cause serious consequences if used in some automated or collaborative contexts.

[0022] Certain aspects of the present disclosure and embodiments thereof may provide solutions to these and other challenges.

[0023] To facilitate accurate and reliable positioning with limited complexity, the network may provide information about the line-of-sight (LoS) and non-line-of-sight (NLoS) properties of each satellite over a region of space to the UE as assistance data. Based on the provided assistance data, the UE may identify satellite signals that are expected to be reliable, thereby facilitating position estimation. LoS / NLoS information may be provided in a number of different ways, such as via a spatial LoS / NLoS indicator, the duration that a satellite signal is expected to be in LoS at a particular spatial location, and the like, and may be provided unsolicited from the network to the UE or based on a feedback process utilizing communications from the UE to the network.

[0024] More generally, the techniques described herein provide for a UE to receive LoS-NLoS indication information for determining the UE's location using signals from one or more signal sources (e.g., satellites, WiFi signal sources, Bluetooth transmitters, beacon signal sources, base stations, RAT-dependent signal sources, base stations in a terrestrial RAN, etc.). The LoS-NLoS indication information indicates whether the UE will (e.g., is expected to) have LoS to the one or more signal sources at one or more locations of the UE.

[0025] According to a first aspect, a method performed by a UE is provided. The method comprises receiving indication information from a network node for determining a location of the UE using signals from one or more signal sources, wherein the indication information indicates whether the UE will have LoS to the one or more signal sources at one or more locations.

[0026] According to a second aspect, a method performed by a network node is provided. The method includes sending indication information to a UE for use by the UE in determining a location of the UE using signals from one or more signal sources. The indication information indicates whether the UE will have a LoS to the one or more signal sources at one or more locations.

[0027] 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, when executed by a suitable computer or processor, the computer or processor performs a method according to the first aspect, the second aspect or any embodiment thereof.

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

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

[0030] 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.

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

[0032] According to an eighth aspect, a user device is provided, comprising: a processing circuit configured to cause the user device to perform any steps of the method according to the first aspect or any embodiment thereof; and a power supply circuit configured to supply power to the processing circuit.

[0033] According to a ninth aspect, a network node is provided, comprising: a processing circuit configured to cause the network node to perform any step of the method according to the second aspect or any embodiment thereof; and a power supply circuit configured to supply power to the processing circuit.

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

[0035] Certain embodiments may provide one or more of the following technical advantages: One advantage of providing LoS-NLoS indication information is to facilitate signal selection and positioning (ie, time-of-flight) measurements to improve positioning and its convergence, as well as to support low-complexity implementation.

[0036] The relative location information feedback described in some embodiments enables a solution in which the UE does not need to provide accurate location information to the network, which may be associated with avoiding privacy issues with sharing accurate location information. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0038] Figure 1 An architecture for supporting positioning in a communication network is shown;

[0039] Figure 2is a detailed illustration of an architecture for supporting positioning in a communication network;

[0040] Figure 3a and 3b The figure shows the impact of the local environment on the received signal in an urban canyon;

[0041] Figure 4 is a signaling diagram illustrating signaling between a UE and a network node in a communication network;

[0042] Figure 5 is a flow chart illustrating a method performed by a UE;

[0043] Figure 6 is a flow chart illustrating a method performed by a network node;

[0044] Figure 7a 、 7b and 7c illustrate different examples of LoS-NLoS indication information;

[0045] Figure 8 This diagram illustrates a situation where a UE may need new / updated LoS-NloS indication information;

[0046] Figure 9 is a flow chart illustrating another method performed by a UE;

[0047] Figure 10 is a flow chart illustrating another method performed by a network node;

[0048] Figure 11 shows an example of a communication system according to some embodiments;

[0049] Figure 12 illustrates a UE according to some embodiments;

[0050] Figure 13 shows a network node according to some embodiments; and

[0051] Figure 14 is a block diagram illustrating a virtualization environment in which functionality implemented by some embodiments may be virtualized. DETAILED DESCRIPTION

[0052] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. The embodiments are provided by way of example to convey the scope of the present subject matter to those skilled in the art. Additional information regarding how the techniques described herein can be implemented in relevant 3GPP standards can be found in the appendix at the end of this detailed description.

[0053] Figure 4is a signaling diagram illustrating signaling between a UE (or any other type of wireless device that uses GNSS signals to determine its location) 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 a location management function (LMF) (e.g., in a 4G network or a 5G network), or other network node that is responsible for or participates in positioning calculations for the UE in the network. It will be understood that the UE typically communicates with nodes in the core network via one or more RAN nodes (base stations), but for simplicity, Figure 4 Those intermediate communication links or hops are not shown.

[0054] As described above, to facilitate accurate and reliable positioning with limited complexity, the network can provide the UE with information regarding the LoS and NLoS properties of each satellite over a region of space. This assistance data is referred to herein as "LoS / NLoS indication information," or simply "LoS / NLoS information." Based on the provided assistance data, the UE can identify satellite signals that are expected to be reliable, thereby facilitating position estimation. The LoS-NLoS indication information can be related to GNSS satellite signals, cellular signals, and / or other radio access technology (RAT) signals.

[0055] The LoS-NLoS indication information may be provided on a spatial grid, where each grid point (e.g., corresponding to a location in the environment) is associated with LoS-NLoS indication information for a particular satellite, base station anchor, or the like. The spatial grid may be associated with altitude information. For example, each grid point of the spatial grid may be associated with one or more altitudes, such that the corresponding LoS-NLoS indication information for that grid point is related to the associated one or more altitudes at that spatial grid (e.g., latitude, longitude) location. The LoS-NLoS indication information may alternatively be provided in association with a logical network element, such as a cell, beam, reference signal(s), cell list, tracking area (TA), radio network area, or the like. The LoS-NLoS indication information may also or alternatively be provided in conjunction with a broadcast, for example, in a system information block (SIB), such as a positioning SIB (posSIB) or a non-positioning SIB. Further details regarding the LoS-NLoS indication information are provided below.

[0056] like Figure 4 As shown, a capability handshake may occur between the UE and the LS so that the LS may determine whether the UE supports the use of LoS-NLoS indication information. Thus, the LS may send a request 400 to the UE requesting information about the UE's capabilities, and the UE may send a response 410 indicating the UE's capabilities (and specifically, capabilities related to the use of LoS-NLoS indication information).

[0057] Optionally, the LS may send a location information network request 420 to the UE requesting the UE to provide location information indicating the UE's location. The UE may provide a response 430 including the location information for the UE. The LS may use the location information to support selection of specific LoS-NLoS indication information associated with the UE.

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

[0059] At step 460, the UE uses the obtained LoS-NLoS indication information to facilitate or enable selection of signals and / or measurements (of specific signals) for performing positioning calculations and to estimate position based on those signals and / or measurements. In particular, the UE may prioritize signals for which range estimates are performed for the UE (based on time of flight) based on GNSS satellites that are considered to be in LoS. Range estimates from different signal sources (e.g., different satellites) are then combined to derive the UE's position. Signals from satellites that are considered to be NLoS may be ignored, or any timing measurements determined associated with those signals may be discarded or ignored when determining the UE's position.

[0060] Optionally, the UE may send a request 470 for LoS-NLoS indication information to the LS that includes relative position information. Examples of such relative position information are an indication of what new spatial information the UE requests, such as spatial information north / east / south / west of 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 specific altitude and / or corresponding LoS-NLoS indication information is provided for different possible altitudes of the UE), the relative position information may indicate whether the UE is above or below its current altitude (e.g., because the UE has moved floors in a building). When the expiration time of the current LoS-NLoS indication information has expired or is about to expire, the UE may trigger a request for assistance data via request 470.

[0061] Based on the request 470, the LS may send a response 480 containing new assistance data corresponding to the mobility of the UE.

[0062] The UE may then use the new assistance data to perform another positioning estimate (step 490).

[0063] Figure 5 The basic steps and some optional steps of the technology described in this article are illustrated from the perspective of the UE. Many of these steps correspond to the above Figure 4 The UE 100 may perform the following operations in response to executing appropriately formulated computer readable code: Figure 5 The computer readable code may be embodied or stored on a computer readable medium, such as a memory chip, an optical disc, or other storage medium in a UE / device. The computer readable medium may be part of a computer program product.

[0064] In optional step 500, the UE provides information about UE capabilities related to the LoS-NLoS indication information (eg, the capability to use the LoS-NLoS indication information in determining the UE's location). The capability information is provided to a location server (LS) in the network.

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

[0066] Optionally, the UE requests assistance data from a network node (eg, LS) in step 530. The request may be a general request for assistance data, or it may be a specific request for LoS-NLoS indication information.

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

[0068] In step 550, the UE uses the obtained LoS-NLoS indication information to facilitate or enable selection of signals and / or measurements for performing positioning calculations and estimates position based on those signals and / or measurements. Although step 550 shows the selection of signals and / or measurements based on the LoS-NLoS indication information and the determination of the device position as a single step or operation, it will be understood that these operations may be performed separately in their own steps or sub-steps.

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

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

[0071] Then, in step 580, the UE uses the obtained LoS-NLoS indication information to facilitate or enable selection of signals and / or measurements for performing positioning calculations and thereby estimate the UE's position.

[0072] Figure 6 The basic steps and some optional steps of the technology described in this article are illustrated from the perspective of a network node (such as LS). Many of these steps correspond to the above steps about Figure 4 The network node may perform the operations of the LS in response to executing appropriately formulated computer readable code. Figure 6 The computer readable code may be embodied or stored on a computer readable medium, such as a memory chip, an optical disk, or other storage medium in a network node. The computer readable medium may be part of a computer program product.

[0073] It will be understood that although Figure 6 Involves interactions between a network node and a single UE, but in practice such a network node will perform these operations and steps for multiple UEs at any given time.

[0074] In optional step 610, the network node obtains information from the UE regarding UE capabilities related to the LoS-NLoS indication information. Such capability information may relate to the UE's ability to use the LoS-NLoS indication information in determining the UE's location. Step 610 may include 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 sending a request to the UE.

[0075] 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). The location information can be used by the network node to support selection of LoS-NLoS indication information that is beneficial or appropriate for the UE.

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

[0077] In step 640 (which may occur in response to the request received in step 630 or without a specific request from the UE), the network node provides assistance data including 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 provided in addition to the LoS-NLoS indication information).

[0078] Optionally, in step 650, the network node may obtain or receive a request for LoS-NLoS indication information assistance data from the UE, including relative location information. Examples of such relative location information include an indication of what new spatial information the UE is requesting, such as spatial information to the north / east / south / west / higher / lower altitude than the current spatial information, or a specific subset of the current grid. In some embodiments, the UE may have already 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 identifier in the request for assistance data (AD).

[0079] Based on such a request, in step 660, the network node determines the scope of new assistance data for the LoS-NLoS indication information based on the provided relative position information, and provides the assistance data to the UE in step 670. In particular, satellite information about LoS / NLoS varies from one location area to another. Therefore, if the UE provides the previous location at which it obtained the previous LoS-NLoS indication information, and what the relative change in the UE's position is (e.g., a distance X to the north, or just a moving direction, such as north), the network will be able to identify which new LoS-NLoS indication information is applicable to the UE.

[0080] The following sections describe in more detail the form and / or content of the LoS-NLoS indication information, and how the LoS-NLoS indication information is processed.

[0081] Figure 7a 、 7b 7c and 7d are three examples of LoS-NLoS indication information. Figure 7a and 7b As shown, the LoS-NLoS indication information is represented by or takes the form of a spatial grid 720 and is Figure 7cIn the present invention, the LoS-NLoS indication information is represented by or takes the form of a spatial grid with or taking into account altitude information. The spatial grid 720 may include 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, an incremental step in a direction (e.g., north), an incremental step in a different direction (e.g., east), a number of steps in a first direction, and a number of steps in a different direction. For each grid point 730, and for each considered signal, there is a "LoS-NLoS indication," i.e., an indication of whether the UE 100 at that grid point will have LoS or NLoS to the satellite transmitting the corresponding signal.

[0082] As described 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 reference altitudes include ellipsoid level, mean sea level, ground level, etc. In other embodiments, the altitude information can be provided as a valid range (such as a lower altitude and a higher altitude within which the spatial grid data is considered valid). In other words, the altitude information can be an altitude range of the UE, within which the corresponding LoS-NLoS indication information is valid. In yet other embodiments, the altitude information can be provided as multiple layers in the spatial grid, wherein each layer in the spatial grid corresponds to an altitude or altitude range.

[0083] In an alternative embodiment, the spatial grid (or corresponding grid points in the spatial grid) can be associated with a pressure sensor (e.g., a barometer) validity region, as shown below in an ASN.1 modification. That is, a mapping can exist between pressure measurements and altitudes for different regions (valid regions). Thus, for a particular pressure sensor value that is valid in a particular region (and whose value is mapped to altitude), the LoS-NLoS indication information can provide a list of satellites that are (probably) in LoS or NLoS.

[0084] 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 the proposed changes are underlined and the different introduced components are specifically defined in the appendix below.

[0085] 6.5.5.8 Sensor Auxiliary Data Elements

[0086] -Sensor-AssistanceDataList

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

[0088]

[0089]

[0090]

[0091] In some embodiments, the LoS-NLoS indication is a binary indication for the signal, such as LoS: True / False (or alternatively, it can take the form of NLoS: True / False). Alternatively, it can be more granular and include an option for the LoS-NLoS status to be 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 metric (or probability) as a percentage (1..100). As an example, if LoS is predicted to be 70%, a value of 70 would be provided with the LoS-NLoS indication. In other or further embodiments, the indication can be or include a duration during which the corresponding signal is predicted to be in LoS (or alternatively, in NLoS) at that grid point 730.

[0092] In some embodiments, the grid 720 may also be provided with a binary mask (binmask) that indicates which grid points 730 are provided with LoS-NLoS indication values. For example, a building 710 may exist within the area covered by the grid 720, and the grid points 730 inside the building 710 may be omitted, such as Figure 7a As shown by the non-solid grid points 730 in .

[0093] Figure 7a Also illustrated is an update mechanism for the network node to supply updated LoS-NLoS indication information to the UE 100 based on UE feedback (and in particular, UE location). Figure 7a In the example of FIG. 7 , a UE 100 (eg, which may be part of or in a car or other vehicle) travels along an illustrated path 740 between buildings 710. As shown in FIG.

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

[0095] When the UE 100 has moved along the path 740 and is about to leave the spatial region associated with the current grid 720 (e.g., as indicated by the device location 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 may be represented by directions such as north, west, south, east (and / or higher / lower altitude if the LoS-NLoS indication information takes altitude into account) relative to the current grid 720. The relative location information indicates or implies that the UE 100 desires or needs an updated spatial region of the grid (e.g., as described above with reference to step 470).

[0096] The network node determines a new spatial grid to be provided to the UE 100 taking into account the provided relative position information and provides assistance data including the new grid to the UE 100 (e.g. according to step 480). Figure 7a In the example of , this new / updated grid is shown by grid 750. The further updated grid required as UE 100 continues along path 740 is shown by grid 760.

[0097] This is Figure 7a In a specific example, based on initial knowledge of UE 100's location, UE 100 is first provided with a grid 720 consisting of 4 x 4 grid points 730. When UE 100 is about to leave the area covered by grid 720, it sends a new assistance data request to the network node, indicating relative position information (in this case, south). Based on the relative position information provided by UE 100, the network node determines a new grid 750 south of the current grid 720, this time formed by 4 x 2 grid points 720. The network node provides LoS-NLoS indication information for this grid 750 to UE 100. When UE 100 is about to leave this second grid 750, it sends a new assistance data request to the network node, indicating "Relative position information: East." The network node then determines a new grid 760 east of the current grid 750, this time formed by 2 x 2 grid points 730, and provides LoS-NLoS indication information for this new grid 760 to UE 100.

[0098] In an embodiment of the above process, the network node may adapt the extent of the grid provided to the UE 100 in terms of either or both of the spatial extent of the grid (i.e., the size of the area covered by the grid) and the size used for zoomed-in display at the location where the UE 100 is located. In both cases, these adjustments may be used to reduce the signaling bandwidth (i.e., the bandwidth required to signal the LoS-NLoS indication information to the UE 100).

[0099] Figure 7bAnother embodiment is illustrated in which the UE 100 instead provides relative position information within the current grid 770, for example, in the upper left, upper right, lower left, and lower right quadrants. In this example, the UE 100 first obtains a 4x4 grid 770, and the device 100 then provides relative position information indicating the lower right portion of the current grid 770 to the network node. The network node can then determine a new grid 780 (in this case, a 2x2 grid) based on the provided relative position information from the UE 100. The new grid 780 is provided by the network node to the UE 100. In this way, the range of grids 770 / 780 can be zoomed / focused toward the location of the UE 100 without the UE providing its exact location. In some embodiments, by providing relative position information within the current grid 770 by the UE 100, the grid resolution can be finer for the new ("zoomed-in") grid.

[0100] Figure 7c Two different examples of spatial grids, each with a different altitude reference, are shown. The two spatial grids are viewed from the side relative to a sloping ground 782, and each spatial grid contains only one altitude "layer." The spatial grids are illustrated in an area where the ground 782 slopes upward from left to right. Dashed line 784 represents mean sea level (or another reference altitude) from which altitude information in the spatial grids can be measured (in some embodiments). Spatial grid 786 is a first example of a spatial grid defined with altitude information relative to ground plane 782, and as such, the grid points in spatial grid 786 do not necessarily refer to the same altitude at a common reference altitude (e.g., mean sea level). Instead, the grid points in spatial grid 786 "track" changes in the altitude of the ground 782. This approach may be suitable or preferred in areas where UEs may only be on or near the ground 782 (e.g., UEs on a road, drones flying at a constant altitude above the ground, etc.). The spatial grid 788 is a second example of a spatial grid 788 defined with altitude information relative to mean sea level 784 (or another reference altitude), and as such, the grid points in the spatial grid 788 relate to the same altitude as one another above mean sea level (or another reference altitude). Figure 7c Although not shown, the grid 786 or 788 may have multiple layers of grid points, each layer being associated with a respective altitude. This approach may be more suitable or preferred in situations where the UE is in an area where the altitude of the UE relative to a reference altitude may vary (e.g., a drone flying at varying altitudes, UEs that may be on different floors of a building, etc.).

[0101] In some embodiments, as part of the request for assistance data in step 530, the UE 100 may request or indicate that the UE 100 requires an altitude reference for the assistance data. For example, if LoS-NLoS indication information is required, the UE 100 may indicate its current altitude or provide some other indicator of altitude. In response to the request, the network node may provide LoS-NLoS indication information appropriate for the indicated altitude. As described above, the altitude reference indication may include an ellipsoid, mean sea level, ground level, etc.

[0102] 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 may depend on the mobility state of the UE 100. For example, if the UE 100 is moving at a high speed, the LoS-NLoS indication information may be formed to cover a larger area than if the UE 100 is stationary or moving at a low speed. In a similar manner, if the UE 100 is moving at a high speed and the current location of the UE 100 indicates that it is on a road, the LoS-NLoS indication information may be formed to relate to a further portion of the road rather than the entire area surrounding the UE 100. Likewise, the "zoom" level of the grid may depend on the speed of the UE 100, where a higher speed of the UE 100 indicates that the data points in the LoS-NLoS indication information may be quite coarse, while a finer level of data points may be provided when the UE is stationary or moving at a low speed.

[0103] Figure 8 Another scenario where the UE may need new / updated LoS-NLoS indication information is illustrated. Figure 8 A network node 810 (referred to as a base station in this embodiment) is shown having 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. When a UE changes its logical location (e.g., is served by beam 840 instead of beam 830), it may request new LoS-NLoS indication information for the new location (i.e., the cell served by beam 840). In some embodiments, the change in the UE's logical location may be used by the network to preemptively determine and send new LoS-NLoS indication information to the UE.

[0104] Figure 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 appropriately formulated computer readable code. The computer readable code may be embodied or stored on a computer readable medium, such as a memory chip, an optical disc, or other storage medium. The computer readable medium may be part of a computer program product. The UE may refer to the following Figure 12 As stated.

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

[0106] The indication information is used to determine the position of the UE using signals from one or more signal sources. The signal source(s) may include any one of the following: satellites; satellites in GNSS; base stations; base stations in terrestrial RAN; WiFi signal sources, and Bluetooth signal sources.

[0107] The indication information indicates whether the UE will have LoS to one or more signal sources at one or more locations.

[0108] The indication information may include information for each of the one or more signal sources indicating whether the UE will have LoS to the signal source. The indication information may include information for each of the one or more locations indicating whether the UE will have LoS to the one or more signal sources at the location. Alternatively, the indication information may include information for each signal source at each of the one or more locations indicating whether the UE will have LoS to the signal source at the location.

[0109] One or more locations may be defined by latitude and / or longitude coordinates. Each location may additionally or alternatively be defined by altitude, altitude coordinates, or by a mapping between altitude and barometric pressure measurements for a valid area. In this latter embodiment, one or more of the locations may have different altitudes.

[0110] The indication information may include any one or more of the following:

[0111] - A binary indication of whether the UE will have LoS to one or more signal sources at one or more locations

[0112] - a binary indication of whether the UE will have NLoS to one or more signal sources at one or more locations;

[0113] - one of: an indication that the UE will have LoS to the one or more signal sources at the one or more locations, an indication that the UE will not have LoS to the one or more signal sources at the one or more locations, 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 locations;

[0114] - one of: an indication that the UE will have NLoS to the one or more signal sources at the one or more locations, an indication that the UE will not have NLoS to the one or more signal sources at the one or more locations, 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 locations;

[0115] - the probability that the UE will have LoS to one or more signal sources at one or more locations; and

[0116] - The probability that the UE will have NLoS to one or more signal sources at one or more locations.

[0117] In addition to the indication information, the UE may also receive duration information, which indicates a duration during which the received indication information is valid.

[0118] After receiving the indication information, the UE may use the indication information to determine the location of the UE. Using the received indication information may mean prioritizing signals for measurement from signal sources determined to be in LoS with the UE.

[0119] In certain embodiments, the location of the UE may be determined by determining one or more signal sources that are in LoS with the UE based on the received indication information, performing measurements of signals from those one or more signal sources, and determining the location of the UE using the measurements. The signal measurements may be measurements of the flight time of the signals from the signal sources to the UE.

[0120] The method performed by the UE may further include the UE sending capability information to the network node. The capability information may indicate the UE's ability to receive and / or use the indication information. In response to receiving the request for capability information, the capability information may be sent to the network node.

[0121] 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 include sending a request for indication information to the network node.

[0122] The method performed by the UE may further include the UE sending a request for updated indication information to the network node. The request for updated indication information may include relative position information for the UE. The relative position information may include any one of the following: an indication of a direction of movement of the UE, an indication of an amount of movement of the UE, an indication of a direction of change in altitude of the UE, and / or an amount of change in altitude of the UE. Alternatively, the relative position information may include any one of the following: an indication of a direction of movement of the UE since the indication information was received from the network node; an indication of an amount of movement of the UE since the indication information was received from the network node; an indication of a direction of change in altitude of the UE since the indication information was received from the network node; and / or an amount of change in altitude of the UE since the indication information was received from the network node.

[0123] If the received indication information is considered invalid or expired, the UE may send a request for updated indication information. The request for updated indication information may include a mesh set identifier and / or mobility state for the UE.

[0124] Figure 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 appropriately formulated computer readable code. The computer readable code may be embodied or stored on a computer readable medium, such as a memory chip, an optical disk, or other storage medium. The computer readable medium may be part of a computer program product. The network node may be configured as follows: Figure 13 The network node may be any one of the following: a location server (LS); a LMF; an E-SMLC; or an SLP.

[0125] In step 1001, a network node may send indication information to a UE. The indication information is used to instruct the UE to use signals from one or more signal sources to determine the UE's location. The signal source(s) may include any of the following: a satellite; a satellite in a GNSS; a base station; a base station in a terrestrial RAN; a WiFi signal source; and a Bluetooth signal source.

[0126] The indication information indicates whether the UE will have LoS to one or more signal sources at one or more locations.

[0127] The indication information may include information for each of the one or more signal sources indicating whether the UE will have LoS to the signal source. The indication information may include information for each of the one or more locations indicating whether the UE will have LoS to the one or more signal sources at the location. Alternatively, the indication information may include information for each signal source at each of the one or more locations indicating whether the UE will have LoS to the signal source at the location.

[0128] One or more locations may be defined by latitude and / or longitude coordinates. Each location may additionally or alternatively be defined by altitude, altitude coordinates, or by a mapping between altitude and barometric pressure measurements for a valid area. In this latter embodiment, one or more of the locations may have different altitudes.

[0129] The indication information may include any one or more of the following:

[0130] - A binary indication of whether the UE will have LoS to one or more signal sources at one or more locations

[0131] - a binary indication of whether the UE will have NLoS to one or more signal sources at one or more locations;

[0132] - one of: an indication that the UE will have LoS to the one or more signal sources at the one or more locations, an indication that the UE will not have LoS to the one or more signal sources at the one or more locations, 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 locations;

[0133] - one of: an indication that the UE will have NLoS to the one or more signal sources at the one or more locations, an indication that the UE will not have NLoS to the one or more signal sources at the one or more locations, 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 locations;

[0134] - the probability that the UE will have LoS to one or more signal sources at one or more locations; and

[0135] - The probability that the UE will have NLoS to one or more signal sources at one or more locations.

[0136] In addition to sending the indication information, the network node may also send duration information to the UE, which indicates a duration during which the sent indication information is valid.

[0137] The method performed by the network node may further include the network node receiving capability information from the UE. The capability information may indicate the UE's ability to receive and / or use the indication information. The capability information may be received from the UE in response to sending a request for capability information to the UE.

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

[0139] The method performed by the network node may further include the network node receiving a request for updated indication information from the UE. The request for updated indication information may include relative location information for the UE. The request for updated indication information may further include a mesh set identifier and / or a mobility state for the UE. The relative location information may include any of the following: an indication of a direction of movement of the UE, an indication of an amount of movement of the UE, an indication of a direction of change in altitude of the UE, and / or an amount of change in altitude of the UE. Alternatively, the relative location information may include any of the following: an indication of a direction of movement of the UE since the indication information was sent by the network node; an indication of an amount of movement of the UE since the indication information was sent by the network node; an indication of a direction of change in altitude of the UE since the indication information was sent by the network node; and / or an amount of change in altitude of the UE since the indication information was sent by the network node.

[0140] The method performed by the network node may further include the network node determining updated indication information for the UE based on the received relative location information. The updated indication information may be determined by determining an area to be covered by the updated indication information based on the received relative location information, determining a size of the area to be covered by the updated indication information based on the received relative location information, and determining a resolution of the updated indication information based on the received relative location information.

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

[0142] In this example, a communication system 1100 includes a telecommunications network 1102 including an access network 1104, such as a radio access network (RAN), and a core network 1106 including 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 third generation partnership project (3GPP) access nodes or non-3GPP access points. The access network nodes 1110 facilitate direct or indirect connections of wireless devices (also interchangeably referred to 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 UE 1112) to the core network 1106 via one or more wireless connections. The access network node 1110 may be, for example, an access point (AP) (e.g., a radio access point), a base station (BS) (e.g., a radio base station, a Node B, an evolved Node B (eNB), and an NR Node B (gNB)).

[0143] Unless otherwise indicated, the term “network node” is used herein to refer to both access network nodes 1110 and core network nodes 1108 .

[0144] Example wireless communications over wireless connections include sending and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Additionally, in various 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 a wired or wireless connection. The communication system 1100 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar types of systems.

[0145] The wireless device / UE 1112 may be any of a variety of communication devices, including a wireless device that is arranged, configured, and / or operable to communicate wirelessly with the network node 1110 and other communication devices. Similarly, the access network node 1110 is arranged, capable, configured, and / or operable to communicate directly or indirectly with the UE 1112 and / or with other network nodes or devices in the telecommunications network 1102 to enable and / or provide network access (such as wireless network access) and / or perform other functions (such as management in the telecommunications network 1102).

[0146] In the depicted example, core network 1106 connects access network node 1110 to one or more hosts, such as host 1116. These connections can be direct or indirect connections via one or more intermediate networks or devices. In other examples, the network node can be directly coupled to the host. Core network 1106 includes one or more core network nodes (e.g., core network node 1108) constructed using hardware and software components. The features of these components can be substantially similar to those described with respect to wireless devices / UEs, access network nodes, and / or hosts, so that the description is generally applicable to the corresponding components of core network node 1108. Example core network nodes include the functionality of one or more of a location server (LS), an E-SMLC, a SLP, a location management function (LMF), a mobile switching center (MSC), a mobility management entity (MME), a home subscriber server (HSS), an access and mobility management function (AMF), a session management function (SMF), an authentication server function (AUSF), a subscription identifier dehiding function (SIDF), a unified data management (UDM), a security edge protection proxy (SEPP), a network exposure function (NEF), and / or a user plane function (UPF).

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

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

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

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

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

[0152] The hub 1114 may have a constant / persistent or intermittent connection to the network node 1110b. The hub 1114 may also allow different communication schemes and / or scheduling between the hub 1114 and the UE (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. In addition, the hub 1114 may be configured to connect to an M2M service provider via the access network 1104 and / or to another UE via a direct connection. In some scenarios, the UE may establish a wireless connection with the network node 1110 while still being connected via a wired or wireless connection via the hub 1114. In some embodiments, the hub 1114 may be a dedicated hub, that is, its primary function is to route communications from the network node 1110b to the UE / from the UE to the network node 1110b. In other embodiments, hub 1114 may be a non-dedicated hub, that is, a device operable to route communications between UEs and network node 1110b, but also capable of operating as a communications origin and / or endpoint for certain data channels.

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

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

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

[0156] The processing circuitry 1202 is configured to process instructions and data, and may be configured to implement any sequential state machine operable to execute instructions stored in the memory 1210 as a machine-readable computer program. The processing circuitry 1202 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, a field programmable gate array (FPGA), an application-specific integrated circuit (ASIC), etc.); programmable logic and appropriate firmware; one or more stored computer programs, general-purpose processors such as a microprocessor or a digital signal processor (DSP), and 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 UE 1200 functionality alone or in combination with other UE 1200 components (such as the memory 1210). For example, the processing circuitry 1202 may be configured to cause the UE 1202 to execute a reference Figure 4 、 5 Or the method described in 9.

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

[0158] In some embodiments, the power supply 1208 is configured as a battery or battery pack. Other types of power sources may be used, such as an external power source (e.g., an electrical outlet), a photovoltaic device, or a power cell. The power supply 1208 may also include power circuitry for delivering power from the power supply 1208 itself and / or an external power source to various components of the UE 1200 via an input circuit or an interface such as a power cable. The delivered power may be used, for example, to charge the power supply 1208. The power circuitry may perform any formatting, conversion, or other modifications to the power from the power supply 1208 to make the power suitable for the various components of the UE 1200 being supplied with power.

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

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

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

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

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

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

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

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

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

[0168] Figure 13 A network node 1300 is shown according to some embodiments.

[0169] As used herein, a network node includes a device that is capable of, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or other network nodes or devices in a telecommunications network. Examples of network nodes include, but are not limited to, access 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 node Bs (gNBs)). Other examples of network nodes include, but are not limited to, core network nodes, such as nodes that include the functionality of one or more of the following: location server (LS), E-SMLC, SLP, location management function (LMF), 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-hiding function (SIDF), unified data management (UDM), security edge protection proxy (SEPP), network open function (NEF), and / or user plane function (UPF).

[0170] Base stations can be categorized based on the amount of coverage they provide (or, stated differently, based on their transmit power level), and thus, depending on the amount of coverage provided, a base station can be referred to as a femto base station, a pico base station, a micro base station, or a macro base station. A base station can be a relay node or a relay donor node that controls a relay. A network node can also include one or more (or all) parts of a distributed radio base station, such as a centralized digital unit and / or a remote radio unit (RRU), which is sometimes referred to as a remote radio head (RRH). Such a remote radio unit may or may not be integrated with an antenna as an antenna-integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

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

[0172] Network node 1300 includes processing circuitry 1302, memory 1304, a communication interface 1306, and a power supply 1308, and / or any other components, or any combination thereof. Network node 1300 may be comprised of multiple physically separate components (e.g., a NodeB component and an RNC component, or a BTS component and a BSC component, etc.), each of which may have its own corresponding components. In certain scenarios where network node 1300 includes 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 scenarios, each unique NodeB and RNC pair may be considered a separate network node in some cases. In some embodiments, 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., the same antenna 1310 may be shared by different RATs). The network node 1300 may also include multiple sets of various illustrated components for different wireless technologies, such as GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, radio frequency identification (RFID), or Bluetooth wireless technologies, integrated into the network node 1300. These wireless technologies may be integrated into the same or different chips or chipsets and other components within the network node 1300.

[0173] The processing circuitry 1302 may include a combination of one or more of a microprocessor, a controller, a microcontroller, a central processing unit, a digital signal processor, an application specific integrated circuit, a field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and / or encoded logic operable to provide the functionality of the network node 1300 alone or in conjunction with other network node 1300 components (such as the memory 1304). For example, the processing circuitry 1302 may be configured to cause the network node to execute a reference Figure 4 、 6 Or the method described in 10.

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

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

[0176] The communication interface 1306 is used for wired or wireless communication of signaling and / or data between network nodes, access networks, core networks and / or UEs. As shown, the communication interface 1306 includes one or more ports / terminals 1316 for sending data to the network and receiving data from the network, for example, via a wired connection.

[0177] If network node 1300 is an access network node, communication interface 1306 also includes radio front-end circuitry 1318, which may be coupled to antenna 1310 or, in some embodiments, be part of antenna 1310. If 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 includes filter 1320 and amplifier 1322. Radio front-end circuitry 1318 may be connected to antenna 1310 and processing circuitry 1302. The radio front-end circuitry may be configured to condition signals transmitted between antenna 1310 and processing circuitry 1302. Radio front-end circuitry 1318 may receive digital data to be transmitted to other network nodes or UEs via a wireless connection. Radio front-end circuitry 1318 may use a combination of filter 1320 and / or amplifier 1322 to convert the digital data into a radio signal with appropriate channel and bandwidth parameters. The radio signal may then be transmitted via antenna 1310. Similarly, when receiving data, antenna 1310 may collect radio signals, which are then converted into digital data by radio front-end circuitry 1318. The digital data may be passed to processing circuitry 1302. In other embodiments, the communication interface may include different components and / or different combinations of components.

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

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

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

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

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

[0183] Figure 141400 is a block diagram illustrating a virtualized environment 1400 in which the functions implemented by some embodiments may be virtualized. In this context, virtualization means creating a virtual version of an apparatus or device, which may include virtualizing a hardware platform, storage device, and network resources. As used herein, virtualization may be applied to any device described herein or components thereof, and relates to an implementation in which at least a portion of a function is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components performed by one or more virtual machines (VMs), which are implemented in one or more virtual environments 1400 hosted by one or more hardware nodes (such as hardware computing devices operating as access network nodes, wireless devices / UEs, or core network nodes). In addition, in embodiments where a virtual node does not require a radio connection (e.g., a core network node), the node may be fully virtualized.

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

[0185] The hardware 1404 includes processing circuitry, memory storing software and / or instructions executable by the hardware processing circuitry, and / or other hardware devices described herein, such as network interfaces, input / output interfaces, and the like. The 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 connection with some embodiments described herein. The virtualization layer 1406 may present a virtual operating platform that appears to be network hardware to the VMs 1408.

[0186] VMs 1408 include virtual processing, virtual memory, virtual networking or interfaces, and virtual storage, and can be run by corresponding virtualization layers 1406. Different embodiments of instances of virtual devices 1402 can be implemented on one or more of VMs 1408 and can be implemented in different ways. Virtualization of hardware is referred to in some contexts as network function virtualization (NFV). NFV can be used to consolidate many network device types onto industry-standard high-volume server hardware, physical switches, and physical storage, which can be located in data centers and customer premises equipment.

[0187] In the context of NFV, VMs 1408 can be software implementations of physical machines that run programs as if they were executed on a physical, non-virtualized machine. Each VM 1408 and the portion of hardware 1404 on which it executes, whether dedicated to that VM and / or shared with other VMs in the VM stack, form a separate virtual network element. Still in the context of NFV, a virtual network function is responsible for handling specific network functions running in one or more VMs 1408 on hardware 1404 and corresponds to an application 1402.

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

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

[0190] In some embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored in a memory, which in some 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 processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hardwired manner. In any of these particular embodiments, the processing circuitry may be configured to perform the described functionality regardless of whether instructions stored on a non-transitory computer-readable storage medium are executed. The benefits provided by such functionality are not limited to the processing circuitry itself or other components of the computing device, but are enjoyed by the computing device as a whole and / or generally by end users and wireless networks.

[0191] The above merely illustrates the principles of the present disclosure. In view of the teachings herein, various modifications and changes to the described embodiments will be apparent to those skilled in the art. Therefore, it will be understood that those skilled in the art will be able to design many systems, devices, and processes that, although not explicitly shown or described herein, embody the principles of the present disclosure and are therefore within the scope of the present disclosure. As will be understood by those skilled in the art, the various exemplary embodiments may be used together and interchangeably with each other.

[0192] appendix

[0193] In this appendix, additional information is provided regarding how the techniques described herein can be implemented in relevant 3GPP standards. In particular, the techniques described herein can be implemented in the 3GPP LPP specification (3GPP TS 37.355 v17.2.0), which is exemplified below. Stage 2 modifications may also be present, such as in 3GPP TS 38.305 v17.3.0 and 3GPP TS 36.305 v17.2.0. Proposed changes are underlined.

[0194] The specification examples provided here consider GNSS signals, but the examples can also be adapted to 3GPP RAT signals (5G, 6G, etc.) and signals from other radio technologies.

[0195] GNSS provides capabilities

[0196] -GNSS-GenericAssistanceDataSupport

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

[0198]

[0199]

[0200]

[0201] GNSS request assistance data

[0202] -GNSS-GenericAssistDataReq

[0203] The IE GNSS-GenericAssistDataReq is used by the target device to request assistance data for one or more specific GNSSs from the location server. The specific GNSS for which assistance data is requested is indicated by the IE GNSS-ID and (if applicable) the IE SBAS-ID. Assistance for up to 16 GNSSs can be requested.

[0204]

[0205]

[0206]

[0207] The following LoS-NLoS-GridPointsReq relates to embodiments where altitude information is not included in the request and / or is not considered in the provided LoS-NLoS indication information.

[0208] LoS-NLoS-GridPointsReq

[0209] IE LoS-NLoS-GridPointsReq is used by the target device to request LoS-NLoS- GridPoints assistance.

[0210]

[0211] As mentioned above, in some embodiments, the request also includes reference altitude information. For example, this can be represented by the referenceAltitudeType attribute, which can indicate the ellipsoid, mean sea level, ground level, etc. In other embodiments, the request includes relative position information relative to the altitude of the current spatial grid, such as:

[0212] - Above - indicates that the UE requests spatial data on a spatial grid corresponding to an altitude above the current spatial grid; - Below - indicates that the UE requests spatial data on a spatial grid corresponding to an altitude below the current spatial grid. This altitude information can be implemented in LoS-NLoS-GridPointsReq as follows:

[0213] -LoS-NLoS-GridPointsReq

[0214] IE LoS-NLoS-GridPointsReq is used by the target device to request LoS-NLoS- GridPoints assistance.

[0215]

[0216] GNSS provides assistance data - preferred mode

[0217] This is the preferred mode for providing GNSS AD with LoS-NLoS

[0218] -GNSS-CommonAssistData

[0219] IE GNSS-CommonAssistData is used by the location server to provide assistance data that can be used for any GNSS.

[0220]

[0221]

[0222] -GNSS-GenericAssistData

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

[0224]

[0225]

[0226] The following LoS-NLoS-GridPoints relate to embodiments where altitude information is not included in the request and / or is not considered in the provided LoS-NLoS indication information.

[0227] –LoS-NLoS-GridPoints

[0228] IE LoS-NLoS-GridPoints is used by the location server to provide a list of grid point coordinates or correction points An array ("grid") of for which LoS-NLoS-GriddedIndications are valid.

[0229]

[0230]

[0231] The following LoS-NLoS-GridPoints relate to embodiments where altitude information is not included in the request and / or is not considered in the provided LoS-NLoS indication information.

[0232] –LoS-NLoS-GridPoints

[0233] IE LoS-NLoS-GridPoints is used by the location server to provide a list of grid point coordinates or correction points An array ("grid") of for which LoS-NLoS-GriddedIndications are valid.

[0234]

[0235]

[0236]

[0237] The following LoS-NLoS-GriddedIndications relate to embodiments where altitude information is not included in the request and / or is not considered in the provided LoS-NLoS indication information.

[0238]

[0239]

[0240] The following LoS-NLoS-GriddedIndications relates to an embodiment that includes altitude information in the request and / or considers altitude information in the provided LoS-NLoS indication information. In this example, the data can be represented as follows, where the GridList is expanded to accommodate data at up to two altitude levels. In addition, the LosInfoList is a sequence across multiple satellites, with one LoSInfoElement for each satellite.

[0241] -LoS-NLoS-GriddedIndications

[0242] IELoS-NLoS-GriddedIndications is used by the location server to provide GNSSLoS_NLoS indication information interest. IE LoS-NLoS-Gridded Indications The parameters provided in apply to all GNSS.

[0243]

[0244]

[0245] Alternative grid defined in lat-long (latitude-longitude)

[0246]

[0247]

[0248] Extended GNSS-SSR-CorrectionPoints

[0249] Example embodiment in which satellite signal predictions for LOS / NLOS in a particular area are mapped to GNSS SSR correction points.

[0250] The IE GNSS-SSR-CorrectionPoints is used by a location server to provide a list of correction point coordinates or an array ("grid") of correction points for which the GNSS SSR GriddedCorrection is valid.

[0251]

[0252]

[0253] There are advantages and disadvantages to using SSR grid correction points. The advantage is that there is no need to define new grid information, and the existing grid points of SSR can be reused. The disadvantage is that the GNSS satellites (LOS / NLOS) are tied to the SSR grid, and if the network (NW) does not provide SSR corrections or does not have a provisioning that supports SSR, it will be difficult to implement the provisioning of GNSS satellite LOS / NLOS classification.

[0254] PosSIB

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

[0256] Here is an example.

[0257] -posSIBX

[0258] SIBX contains LOS / NLOS information of GNSS satellites in different cells.

[0259] posSIBX information element

[0260]

[0261] Example

[0262] Group A Examples

[0263] 1. A method performed by a user equipment (UE), the method comprising:

[0264] Indication information is received from a network node for determining a location of a UE using signals from one or more signal sources, wherein the indication information indicates whether the UE will have a line of sight (LoS) to the one or more signal sources at one or more locations.

[0265] 2. The method of embodiment 1, wherein the one or more signal sources include any one of the following: a satellite; a satellite in a global navigation satellite system (GNSS); a base station; a base station in a terrestrial radio access network (RAN); a WiFi signal source, and a Bluetooth signal source.

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

[0267] 4. The method of embodiment 1, 2, or 3, wherein the indication information includes information for each of the one or more locations indicating whether the UE will have LoS to the one or more signal sources at that location.

[0268] 5. The method of embodiment 1, 2, or 3, wherein the indication information includes information for each signal source at each of the one or more locations indicating whether the UE will have LoS to the signal source at that location.

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

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

[0271] 8. The method of embodiment 7, wherein the one or more locations have different heights.

[0272] 9. The method of any one of embodiments 1-8, wherein the indication information includes any one of the following:

[0273] - a binary indication of whether the UE will have LoS to one or more signal sources at one or more locations;

[0274] - a binary indication of whether the UE will have non-LoS, i.e. NLoS, to one or more signal sources at one or more locations;

[0275] - one of: an indication that the UE will have LoS to the one or more signal sources at the one or more locations, an indication that the UE will not have LoS to the one or more signal sources at the one or more locations, 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 locations;

[0276] - one of: an indication that the UE will have NLoS to the one or more signal sources at the one or more locations, an indication that the UE will not have NLoS to the one or more signal sources at the one or more locations, 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 locations;

[0277] - the probability that the UE will have LoS to one or more signal sources at one or more locations;

[0278] - The probability that the UE will have NLoS to one or more signal sources at one or more locations.

[0279] 10. The method as described in any one of embodiments 1-9, wherein the UE further receives duration information, which indicates a duration during which the received indication information is valid.

[0280] 11. The method of any one of embodiments 1-10, further comprising:

[0281] The received indication information is used to determine the location of the UE.

[0282] 12. The method of embodiment 11, wherein the step of using the received indication information comprises:

[0283] determining, based on the received indication information, one or more signal sources in LoS with the UE;

[0284] performing measurements of signals from the determined one or more signal sources; and

[0285] The measurements are used to determine the position of the UE.

[0286] 13. The method of embodiment 12, wherein the measurement of the signal is a measurement of the flight time of the signal from the signal source to the UE.

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

[0288] 15. The method of any one of embodiments 1-13, further comprising:

[0289] Capability information is sent to the network node, wherein the capability information indicates a capability of the UE to receive and / or use indication information.

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

[0291] 17. The method of any one 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.

[0292] 18. The method of any one of embodiments 1-17, further comprising:

[0293] A request for indication information is sent to a network node.

[0294] 19. The method of any one of embodiments 1-18, further comprising:

[0295] A request for updated indication information is sent to the network node.

[0296] 20. The method of embodiment 19, wherein the request for updated indication information includes relative location information for the UE.

[0297] 21. The method of embodiment 20, wherein the relative position information comprises any one of: an indication of a direction of movement of the UE, an indication of an amount of movement of the UE, an indication of a direction of a change in altitude of the UE, and / or an amount of a change in altitude of the UE.

[0298] 22. The method of embodiment 20, wherein the relative position information includes any one of the following:

[0299] - an indication of the direction of movement of the UE since the indication information was received from the network node;

[0300] - the amount of movement of the UE since the indication information was received from the network node;

[0301] - an indication of the UE's altitude change direction since the indication information was received from the network node; and / or

[0302] -The amount by which the UE's altitude has changed since the indication information was received from the network node.

[0303] 23. The method of any one of embodiments 19-22, wherein if the received indication information is deemed invalid or expired, a request for updated indication information is sent.

[0304] 24. The method of any one of embodiments 19-23, wherein the request for updated indication information includes a grid set identifier.

[0305] 25. The method of any one of embodiments 19-24, wherein the request for updated indication information further includes a mobility state for the UE.

[0306] 26. The method of any one of embodiments 1-25, wherein the network node is any one of: a location server (LS); a location management function (LMF); an evolved serving mobile location center (E-SMLC); or a secure user plane location (SUPL) location platform (SLP).

[0307] Group B Examples

[0308] 27. A method performed by a network node, the method comprising:

[0309] Indication information is sent to a user equipment (UE) for use by the UE to determine a position of the UE using signals from one or more signal sources, wherein the indication information indicates whether the UE will have a line of sight (LoS) to the one or more signal sources at one or more locations.

[0310] 28. The method of embodiment 27, wherein the one or more signal sources include any one of the following: a satellite; a satellite in a global navigation satellite system (GNSS); a base station; a base station in a terrestrial radio access network (RAN); a WiFi signal source, and a Bluetooth signal source.

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

[0312] 30. The method of embodiment 27, 28, or 29, wherein the indication information includes information for each of the one or more locations indicating whether the UE will have LoS to the one or more signal sources at that location.

[0313] 31. The method of embodiment 27, 28, or 29, wherein the indication information includes information for each signal source at each of the one or more locations indicating whether the UE will have LoS to the signal source at that location.

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

[0315] 33. The method of embodiment 30, 31 or 32, wherein each location is defined by an altitude or altitude coordinates or by a mapping between altitude and air pressure measurements for a valid area.

[0316] 34. The method of embodiment 33, wherein the one or more locations have different altitudes.

[0317] 35. The method of any one of embodiments 27-34, wherein the indication information includes any one of the following:

[0318] - a binary indication of whether the UE will have LoS to one or more signal sources at one or more locations;

[0319] - a binary indication of whether the UE will have non-LoS, i.e. NLoS, to one or more signal sources at one or more locations;

[0320] - one of: an indication that the UE will have LoS to the one or more signal sources at the one or more locations, an indication that the UE will not have LoS to the one or more signal sources at the one or more locations, 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 locations;

[0321] - one of: an indication that the UE will have NLoS to the one or more signal sources at the one or more locations, an indication that the UE will not have NLoS to the one or more signal sources at the one or more locations, 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 locations;

[0322] - the probability that the UE will have LoS to one or more signal sources at one or more locations;

[0323] - The probability that the UE will have NLoS to one or more signal sources at one or more locations.

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

[0325] 37. The method of any one of embodiments 27-36, further comprising:

[0326] Capability information is received from the UE, wherein the capability information indicates a capability of the UE to receive and / or use indication information.

[0327] 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.

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

[0329] 40. The method of any one of embodiments 27-39, further comprising:

[0330] A request for indication information is received from the UE.

[0331] 41. The method of any one of embodiments 27-40, further comprising:

[0332] A request for updated indication information is received from the UE.

[0333] 42. The method of embodiment 41, wherein the request for updated indication information includes relative location information for the UE.

[0334] 43. The method of embodiment 42, wherein the relative position information comprises any one of: an indication of a direction of movement of the UE, an indication of an amount of movement of the UE, an indication of a direction of a change in altitude of the UE, and / or an amount of a change in altitude of the UE.

[0335] 44. The method of embodiment 42, wherein the relative position information includes any one of the following:

[0336] - an indication of the direction since the indication information was sent by the network node;

[0337] - the amount of movement of the UE since the indication information was sent by the network node;

[0338] - an indication of the UE's altitude change direction since the indication information was sent by the network node; and / or

[0339] -The amount by which the UE's altitude has changed since the indication information was sent by the network node.

[0340] 45. The method of any one of embodiments 42-44, further comprising:

[0341] Updated indication information for the UE is determined based on the received relative location information.

[0342] 46. ​​The method of embodiment 45, wherein the step of determining updated indication information comprises:

[0343] determining, based on the received relative position information, an area to which the updated indication information will relate;

[0344] determining, based on the received relative position information, a size of an area to be covered by the updated indication information;

[0345] The resolution of the updated indication information is determined based on the received relative position information.

[0346] 47. The method of any one of embodiments 41-46, wherein the request for updated indication information includes a grid set identifier.

[0347] 48. The method of any one of embodiments 41-47, wherein the request for updated indication information further includes a mobility state for the UE.

[0348] 49. The method of any one of embodiments 27-48, wherein the network node is any one of: a location server (LS); a location management function (LMF); an evolved serving mobile location center (E-SMLC); or a secure user plane location (SUPL) location platform (SLP).

[0349] Group C Examples

[0350] 50. A computer program product comprising a computer-readable medium having computer-readable code embodied therein, the computer-readable code being configured to, when executed by a suitable computer or processor, cause the computer or processor to perform the method of any one of Group A embodiments or Group B embodiments.

[0351] 51. A user equipment (UE), configured to perform the method of any one of Group A embodiments.

[0352] 52. A user equipment (UE) comprising a processor and a memory, the memory containing instructions executable by the processor, whereby the UE is operable to perform the method of any one of Group A embodiments.

[0353] 53. A network node configured to perform the method of any one of Group B embodiments.

[0354] 54. A network node comprising a processor and a memory, the memory containing instructions executable by the processor, whereby the network node is operable to perform the method of any one of Group B embodiments.

[0355] 55. A user equipment comprising:

[0356] Processing circuitry configured to cause a user device to perform any of the steps of any one of Group A embodiments; and

[0357] A power supply circuit is configured to supply power to the processing circuit.

[0358] 56. A network node, comprising:

[0359] a processing circuit configured to cause the network node to perform any of the steps of any one of Group B embodiments;

[0360] A power supply circuit is configured to supply power to the processing circuit.

[0361] 57. A user equipment (UE), comprising:

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

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

[0364] The processing circuit is configured to perform any of the steps of any one of Group A embodiments;

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

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

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

Claims

1. A method performed by a user equipment (UE), the method comprising: Indication information for determining a location of the UE using signals from one or more signal sources is received from a network node, wherein the indication information indicates whether the UE will have a line of sight (LoS) to the one or more signal sources at one or more locations.

2. The method according to claim 1, wherein The one or more signal sources include any one of: a satellite; a satellite in a global navigation satellite system GNSS; a base station; a base station in a terrestrial radio access network RAN; a WiFi signal source, and a Bluetooth signal source.

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

4. The method of claim 1, 2 or 3, wherein: The indication information includes information for each of the one or more locations indicating whether the UE will have LoS to the one or more signal sources at that location.

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

6. The method according to claim 4 or 5, wherein: The one or more locations are defined by latitude and / or longitude coordinates.

7. The method of claim 4, 5 or 6, wherein: Each location is defined by an altitude, altitude coordinates, or by a mapping between altitude and barometric pressure measurements for a valid area.

8. The method of claim 7, wherein: One or more of the locations have different altitudes.

9. The method according to any one of claims 1 to 8, wherein The instruction information includes any one of the following: - a binary indication of whether the UE will have LoS to the one or more signal sources at the one or more locations; - a binary indication of whether the UE will have non-LoS (NLoS) to the one or more signal sources at the one or more locations; - one of: an indication that the UE will have LoS to the one or more signal sources at the one or more locations, an indication that the UE will not have LoS to the one or more signal sources at the one or more locations, 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 locations; - one of: the UE will have an indication of NLoS to the one or more signal sources at the one or more locations, the UE will not have an indication of NLoS to the one or more signal sources at the one or more locations, and it being uncertain whether the UE will have an indication of NLoS to the one or more signal sources at the one or more locations; - a probability that the UE will have LoS to the one or more signal sources at the one or more locations; - a probability that the UE will have NLoS to the one or more signal sources at the one or more locations.

10. The method according to any one of claims 1 to 9, wherein The UE also receives duration information indicating a duration during which the received indication information is valid.

11. The method according to any one of claims 1 to 10, wherein The method further comprises: The received indication information is used to determine the location of the UE.

12. The method of claim 11, wherein: The steps of using the received instruction information include: determining, based on the received indication information, one or more signal sources that are in LoS with the UE; performing measurements of signals from the determined one or more signal sources; and The measurements are used to determine a location of the UE.

13. The method of claim 12, wherein: The measurement of a signal is a measurement of a flight time of the signal from the signal source to the UE.

14. The method according to claim 12 or 13, wherein: The step of using the received indication information further includes prioritizing signals for measurement from signal sources determined to be in LoS with the UE.

15. The method according to any one of claims 1 to 14, wherein The method further comprises: Capability information is sent 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 according to any one of claims 1 to 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 according to any one of claims 1 to 17, wherein The method further comprises: A request for indication information is sent to the network node.

19. The method according to any one of claims 1 to 18, wherein The method further comprises: A request for updated indication information is sent to the network node.

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

21. The method of claim 20, wherein: The relative position information includes any one of: an indication of a direction of movement of the UE, an indication of an amount of movement of the UE, an indication of a direction of a change in altitude of the UE, and / or an amount of a change in altitude of the UE.

22. The method of claim 20, wherein: The relative position information includes any one of the following: - an indication of the direction of movement of the UE since the indication information was received from the network node; - the amount of movement of the UE since the indication information was received from the network node; - an indication of the UE's altitude change direction since the indication information was received from the network node; as well as - An amount by which the UE's altitude has changed since the indication information was received from the network node.

23. The method of any one of claims 19 to 22, wherein: If the received indication information is deemed invalid or expired, the request for updated indication information is sent.

24. The method of any one of claims 19 to 23, wherein The request for updated indication information includes a grid set identifier.

25. The method of any one of claims 19 to 24, wherein The request for updated indication information also includes a mobility state for the UE.

26. The method of any one of claims 1 to 25, wherein The network node is any one of the following: a Location Server LS; a Location Management Function LMF; an Evolved Serving Mobile Location Centre E-SMLC; or a Secure User Plane Location SUPL Location Platform SLP.

27. A method performed by a network node, the method comprising: Indication information is sent to a user equipment (UE) for use by the UE to determine a position of the UE using signals from one or more signal sources, wherein the indication information indicates whether the UE will have a line of sight (LoS) to the one or more signal sources at one or more locations.

28. The method of claim 27, wherein: The one or more signal sources include any one of: a satellite; a satellite in a global navigation satellite system GNSS; a base station; a base station in a terrestrial radio access network RAN; a WiFi signal source, and a Bluetooth signal source.

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

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

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

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

33. The method of claim 30, 31 or 32, wherein: Each location is defined by an altitude or altitude coordinates or by a mapping between altitude and air pressure measurements for a valid area.

34. The method of claim 33, wherein: One or more of the locations have different altitudes.

35. The method of any one of claims 27 to 34, wherein The instruction information includes any one of the following: - a binary indication of whether the UE will have LoS to the one or more signal sources at the one or more locations; - a binary indication of whether the UE will have non-LoS (NLoS) to the one or more signal sources at the one or more locations; - one of: an indication that the UE will have LoS to the one or more signal sources at the one or more locations, an indication that the UE will not have LoS to the one or more signal sources at the one or more locations, 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 locations; - one of: the UE will have an indication of NLoS to the one or more signal sources at the one or more locations, the UE will not have an indication of NLoS to the one or more signal sources at the one or more locations, and it being uncertain whether the UE will have an indication of NLoS to the one or more signal sources at the one or more locations; - a probability that the UE will have LoS to the one or more signal sources at the one or more locations; - a probability that the UE will have NLoS to the one or more signal sources at the one or more locations.

36. The method of any one of claims 27 to 35, wherein The network node further sends, to the UE, duration information indicating a duration during which the sent indication information is valid.

37. The method of any one of claims 27 to 36, wherein The method further comprises: Capability information is received 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 one 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 one of claims 27 to 39, wherein The method further comprises: A request for indication information is received from the UE.

41. The method of any one of claims 27 to 40, wherein The method further comprises: A request for updated indication information is received from the UE.

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

43. The method of claim 42, wherein: The relative position information includes any one of: an indication of a direction of movement of the UE, an indication of an amount of movement of the UE, an indication of a direction of a change in altitude of the UE, and / or an amount of a change in altitude of the UE.

44. The method of claim 42, wherein: The relative position information includes any one of the following: - an indication of the direction since said indication information was sent by said network node; - the amount of movement of the UE since the indication information was sent by the network node; - an indication of the UE's altitude change direction since the indication information was sent by the network node; and - an amount by which the UE's altitude has changed since the indication information was sent by the network node.

45. The method of any one of claims 42 to 44, wherein The method further comprises: Updated indication information for the UE is determined based on the received relative location information.

46. ​​The method of claim 45, wherein The steps to determine updated instructions include: determining, based on the received relative position information, an area to which the updated indication information will relate; determining, based on the received relative position information, a size of an area to be covered by the updated indication information; The resolution of the updated indication information is determined based on the received relative position information.

47. The method of any one of claims 41 to 46, wherein The request for updated indication information includes a grid set identifier.

48. The method of any one of claims 41 to 47, wherein The request for updated indication information also includes a mobility state for the UE.

49. The method of any one of claims 27-48, wherein The network node is any one of the following: a Location Server LS; a Location Management Function LMF; an Evolved Serving Mobile Location Centre E-SMLC; or a Secure User Plane 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 to, when executed by a suitable computer or processor, cause the computer or processor to perform the method of any one of Group A claims or Group B claims.

51. A user equipment (UE), configured to perform the method according to any one of claims 1 to 26.

52. A user equipment (UE), comprising a processor and a memory, the memory containing instructions executable by the processor, whereby the UE is operable to perform the method according to any one of claims 1 to 26.

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

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

Images