WO2022154733A1

WO2022154733A1 - Method for gnss rtk observation resolution indication

Info

Publication number: WO2022154733A1
Application number: PCT/SE2022/050033
Authority: WO
Inventors: Fredrik Gunnarsson; Ritesh SHREEVASTAV
Original assignee: Telefonaktiebolaget Lm Ericsson (Publ)
Priority date: 2021-01-14
Filing date: 2022-01-13
Publication date: 2022-07-21

Abstract

A method, system and apparatus are disclosed for GNSS RTK observation resolution indication. In one embodiment, a network node is configured to determine an assistance data resolution indication based on an assistance data configuration (S134); and send the determined assistance data resolution indication to a wireless device (S136). In one embodiment, a wireless device is configured to obtain Global Navigation Satellite System (GNSS) assistance data and an assistance data resolution indication; and determine an assistance data resolution associated with the GNSS assistance data based on the obtained assistance data resolution indication.

Description

METHOD FOR GNSS RTK OBSERVATION RESOLUTION INDICATION

FIELD

The present disclosure relates to wireless communications, and in particular, to GNSS (Global Navigation Satellite System) RTK (Real Time Kinematic) observation resolution indication.

BACKGROUND

Positioning in 3^rd Generation Partnership Project (3GPP) 4^th Generation/Long Term Evolution/Evolved Packet core (4G/LTE/EPC) and 5^th Generation/New Radio/5G core (5G/NR/5GC) is supported by the architecture in FIG. 1, with direct interactions between a wireless device (WD, also called user equipment or UE) and a location server 2 via the LTE Positioning Protocol, LPP. Moreover, there are also interactions between the location server 2 and the serving radio base station (BS) 4 via the LPPa protocol, to some extent supported by interactions between the radio base station 4 and the WD via the Radio Resource Control (RRC) protocol. The radio base station 4 interacts with a mobility network entity (MNE) 6 via a first interface protocol (also referred to as a “1^st interface”), and the mobility network entity 6 interacts with the location server 2 via a second interface protocol (also referred to as a “2^nd interface”). In some applications, the location server interacts with a GNSS correction data provider 8 via a third interface protocol (also referred to as a “3^rd interface”).

In 3GPP LTE

In 4G/LTE/EPC and 5G/NR/5GC, the servers/nodes/functions/interfaces/protocols are generally named as follows:

In both cases, the location server 2 can also be interacting with the WD directly over user plane communication carrying LPP with signaling defined by Open Mobile Alliance (OMA) Secure User Plane Location (SUPL) or some other user plane signaling. In case of SUPL, the location server 2 is denoted SUPL Location Platform (SLP) and the WD is denoted SUPL Enabled Terminal (SET).

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

3GPP Release 9 (Rel 9) introduced support for assisted Global Navigation Satellite System (GNSS), and the scope of the assistance data has been refined over the releases. In Release 5 (Rel 15), support for Real Time Kinematics (RTK) GNSS was introduced. The assistance data is generated based on observations from one or more reference stations, where a reference station is a node with known position and known antenna configuration, and a GNSS receiver capable of measuring signals from one or more satellite systems, where the satellite systems comprise one or more satellites, and each satellite transmits one or more signals. Typically, the GNSS RTK assistance data is provided by a separate function, correction data provider or NRTK server.

FIG. 2 illustrates an example of the different 4G/LTE/EPC and 5G/NR/5GC entities in another architecture, including a home subscriber system (HSS), unified data management (UDM), location service (LCS) client, Gateway Mobile Location Center (GMLC), mobility management entity (MME), Enhanced Serving Mobile Location Center (E-SMLC), Evolved Universal UMTS Terrestrial Radio Access Network (E-UTRAN), network exposure function (NEF), location management function (LMF), application function (AF), access and mobility management function (AMF) and radio access network (RAN).

The GNSS satellites transmit well-defined signals, such as those illustrated in the example of FIG. 3. Each signal is associated with a code, where the code symbols are provided at a specific code rate. By correlating the received code signal with an expected code signal, the device can estimate the arrival time of the signal, also referred to the code phase of the received signal. RTCM SC initially defined differential GNSS corrections to compensate for large errors in code phase. If instead, the arrival time of the signal is estimated based on the carrier signal, which varies at a higher frequency, then the arrival time, or carrier phase, can be estimated very precise. However, then the device also needs to determine how many integer wave lengths of the carrier signal it is between the device and the satellite. GNSS RTK correction data enables this determination, and therefore enables precise positioning. Initially, GNSS RTK was defined for using Global Positioning System (GPS) and Global Navigation Satellite System (GLONASS), but has since then been generalized to all GNSS via the generic RTCM Multiple Signal Messages (MSM). MSM1-MSM7 defines GNSS RTK observations with a scope that increases with MSM number, and also with two different correction resolution - standard or high.

Table 1. Multiple Signal Messages

3 GPP LPP adopted the MSM format and has represented MSM7 with optional attributes to be able to represent MSM1-6 which is a subset of MSM7.

SUMMARY

Some embodiments advantageously provide methods, systems, and apparatuses for GNSS RTK observation resolution indication.

In one embodiment, a network node is configured to determine an assistance data resolution indication based on assistance data configuration; and send the determined assistance data resolution indication to a wireless device.

In one embodiment, a wireless device is configured to obtain Global Navigation Satellite System (GNSS) assistance data and assistance data resolution indication; and determine an assistance data resolution based on the obtained assistance data resolution indication.

According to an aspect, a method implemented in a network node is provided. The method includes determining an assistance data resolution indication based on an assistance data configuration; and sending the determined assistance data resolution indication to a wireless device, WD.

In some embodiments of this aspect, the method further includes receiving a request message for Global Navigation Satellite System, GNSS, assistance data from the wireless device. In some embodiments of this aspect, sending the determined assistance data resolution indication together with the GNSS assistance data to the WD. In some embodiments of this aspect, the assistance data resolution indication indicates that the GNSS assistance data is one of a standard resolution and a high resolution. In some embodiments of this aspect, when the assistance data resolution indication indicates the standard resolution, the GNSS assistance data corresponds to a first type of Radio Technical Commission for Maritime, RTCM, Multiple Signal Message, MSM; and when the assistance data resolution indication indicates the high resolution, the GNSS assistance data corresponds to a second type of RTCM MSM.

In some embodiments of this aspect, the assistance data resolution indication indicates an amount of accuracy associated with a positioning estimate that is based on the GNSS assistance data. In some embodiments of this aspect, the assistance data resolution indication is comprised in a Global Navigation Satellite System, GNSS, Real Time Kinematics, RTK, information element, IE. In some embodiments of this aspect, a presence of the assistance data resolution indication in the GNSS RTK IE indicates that the GNSS assistance data is a standard resolution and an absence of the assistance data resolution indication in the GNSS RTK IE indicates that the GNSS assistance data is a high resolution.

In some embodiments of this aspect, a presence of the assistance data resolution indication in the GNSS RTK IE indicates that the GNSS assistance data is a high resolution and an absence of the assistance data resolution indication in the GNSS RTK IE indicates that the GNSS assistance data is a standard resolution. In some embodiments of this aspect, the method further includes receiving information about a capability to support at least one GNSS assistance data resolution from the WD.

According to another aspect of the present disclosure, a method implemented in a wireless device, WD, configured to communicate with a network node is provided. The method includes obtaining Global Navigation Satellite System, GNSS, assistance data and an assistance data resolution indication; and determining an assistance data resolution associated with the GNSS assistance data based on the obtained assistance data resolution indication.

In some embodiments of this aspect, the method further includes sending a request message for the GNSS assistance data to the network node. In some embodiments of this aspect, the method further includes using the GNSS assistance data and the determined assistance data resolution for positioning. In some embodiments of this aspect, the assistance data resolution indication indicates that the GNSS assistance data is one of a standard resolution and a high resolution. In some embodiments of this aspect, when the assistance data resolution indication indicates the standard resolution, the GNSS assistance data corresponds to a first type of Radio Technical Commission for Maritime, RTCM, Multiple Signal Message, MSM; and when the assistance data resolution indication indicates the high resolution, the GNSS assistance data corresponds to a second type of RTCM MSM.

In some embodiments of this aspect, a presence of the assistance data resolution indication in the GNSS RTK IE indicates that the GNSS assistance data is a high resolution and an absence of the assistance data resolution indication in the GNSS RTK IE indicates that the GNSS assistance data is a standard resolution. In some embodiments of this aspect, the method further includes sending information about a capability to support at least one GNSS assistance data resolution to the network node.

According to yet another aspect of the present disclosure, a network node comprising processing circuitry is provided. The processing circuitry is configured to cause the network node to determine an assistance data resolution indication based on an assistance data configuration; and send the determined assistance data resolution indication to a wireless device, WD.

In some embodiments of this aspect, the processing circuitry is further configured to cause the network node to receive a request message for Global Navigation Satellite System, GNSS, assistance data from the wireless device. In some embodiments of this aspect, the processing circuitry is configured to send the determined assistance data resolution indication together with the GNSS assistance data to the WD. In some embodiments of this aspect, the assistance data resolution indication indicates that the GNSS assistance data is one of a standard resolution and a high resolution.

In some embodiments of this aspect, when the assistance data resolution indication indicates the standard resolution, the GNSS assistance data corresponds to a first type of Radio Technical Commission for Maritime, RTCM, Multiple Signal Message, MSM; and when the assistance data resolution indication indicates the high resolution, the GNSS assistance data corresponds to a second type of RTCM MSM. In some embodiments of this aspect, the assistance data resolution indication indicates an amount of accuracy associated with a positioning estimate that is based on the GNSS assistance data.

In some embodiments of this aspect, the assistance data resolution indication is comprised in a Global Navigation Satellite System, GNSS, Real Time Kinematics, RTK, information element, IE. In some embodiments of this aspect, a presence of the assistance data resolution indication in the GNSS RTK IE indicates that the GNSS assistance data is a standard resolution and an absence of the assistance data resolution indication in the GNSS RTK IE indicates that the GNSS assistance data is a high resolution.

In some embodiments of this aspect, a presence of the assistance data resolution indication in the GNSS RTK IE indicates that the GNSS assistance data is a high resolution and an absence of the assistance data resolution indication in the GNSS RTK IE indicates that the GNSS assistance data is a standard resolution. In some embodiments of this aspect, the processing circuitry is further configured to cause the network node to receive information about a capability to support at least one GNSS assistance data resolution from the WD.

According to another aspect of the present disclosure, a wireless device, WD, configured to communicate with a network node is provided. The WD includes processing circuitry. The processing circuitry is configured to cause the WD to obtain Global Navigation Satellite System, GNSS, assistance data and an assistance data resolution indication; and determine an assistance data resolution associated with the GNSS assistance data based on the obtained assistance data resolution indication.

In some embodiments of this aspect, the processing circuitry is further configured to cause the WD to send a request message for the GNSS assistance data to the network node. In some embodiments of this aspect, the processing circuitry is further configured to cause the WD to use the GNSS assistance data and the determined assistance data resolution for positioning. In some embodiments of this aspect, the assistance data resolution indication indicates that the GNSS assistance data is one of a standard resolution and a high resolution. In some embodiments of this aspect, when the assistance data resolution indication indicates the standard resolution, the GNSS assistance data corresponds to a first type of Radio Technical Commission for Maritime, RTCM, Multiple Signal Message, MSM; and when the assistance data resolution indication indicates the high resolution, the GNSS assistance data corresponds to a second type of RTCM MSM.

In some embodiments of this aspect, a presence of the assistance data resolution indication in the GNSS RTK IE indicates that the GNSS assistance data is a high resolution and an absence of the assistance data resolution indication in the GNSS RTK IE indicates that the GNSS assistance data is a standard resolution. In some embodiments of this aspect, the processing circuitry is further configured to cause the WD to send information about a capability to support at least one GNSS assistance data resolution to the network node.

BRIEF DESCRIPTION OF THE DRAWINGS

A more complete understanding of the present embodiments, and the attendant advantages and features thereof, will be more readily understood by reference to the following detailed description when considered in conjunction with the accompanying drawings wherein:

FIG. 1 illustrates an example of LTE positioning architecture;

FIG. 2 illustrates an example of the different 4G/LTE/EPC and 5G/NR/5GC entities in an architecture;

FIG. 3 illustrates an example of signals that GNSS satellites transmit; FIG. 4 is a schematic diagram of an exemplary network architecture illustrating a communication system connected via an intermediate network to a host computer according to the principles in the present disclosure;

FIG. 5 is a block diagram of a host computer communicating via a network node with a wireless device over an at least partially wireless connection according to some embodiments of the present disclosure;

FIG. 6 is a flowchart illustrating exemplary methods implemented in a communication system including a host computer, a network node and a wireless device for executing a client application at a wireless device according to some embodiments of the present disclosure;

FIG. 7 is a flowchart illustrating exemplary methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data at a wireless device according to some embodiments of the present disclosure;

FIG. 8 is a flowchart illustrating exemplary methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data from the wireless device at a host computer according to some embodiments of the present disclosure;

FIG. 9 is a flowchart illustrating exemplary methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data at a host computer according to some embodiments of the present disclosure;

FIG. 10 is a flowchart of an exemplary process in a network node according to some embodiments of the present disclosure;

FIG. 11 is a flowchart of an exemplary process in a wireless device according to some embodiments of the present disclosure;

FIG. 12 is a flowchart of an example process according to some embodiments of the present disclosure;

FIG. 13 is a flowchart of another example process according to some embodiments of the present disclosure;

FIG. 14 is an example signaling diagram according to some embodiments of the present disclosure; FIG. 15 is an example architecture with two WDs according to some embodiments of the present disclosure;

FIG. 16 is a flowchart of an example process according to some embodiments of the present disclosure;

FIG. 17 is a flowchart of another example process according to some embodiments of the present disclosure;

FIG. 18 is a flowchart of an example process according to some embodiments of the present disclosure; and

FIG. 19 is a flowchart of another example process according to some embodiments of the present disclosure.

DETAILED DESCRIPTION

MSMs are originally provided in two different resolutions, standard and high. Therefore, MSM4 and MSM6 represent the same content, but MSM4 uses standard resolution and MSM6 uses high resolution. Similarly, MSM5 and MSM7 represent the same content, but MSM5 uses standard resolution and MSM7 uses high resolution.

Since 3 GPP uses MSM7 with optional fields, it may not be possible for the target device to understand if the data originally was provided in standard or high resolution.

Some embodiments of the present disclosure include an assistance data resolution indicator to indicate to the device whether the original GNSS correction data was provided in standard or high resolution.

Some embodiments may advantageously provide that, with the GNSS assistance data resolution indication, the device (e.g., WD) may be able to determine the resolution of the original GNSS correction data, which may be useful when assessing uncertainty of the resulting positioning estimates. Furthermore, a device that internally translates the LPP information into corresponding RTCM MSM-messages may use the resolution indication in order to translate to the correct MSM-message.

Before describing in detail exemplary embodiments, it is noted that the embodiments reside primarily in combinations of apparatus components and processing steps related to GNSS RTK observation resolution indication. Accordingly, components have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein. Like numbers refer to like elements throughout the description.

As used herein, relational terms, such as “first” and “second,” “top” and “bottom,” and the like, may be used solely to distinguish one entity or element from another entity or element without necessarily requiring or implying any physical or logical relationship or order between such entities or elements. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises,” “comprising,” “includes” and/or “including” when used herein, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

In embodiments described herein, the joining term, “in communication with” and the like, may be used to indicate electrical or data communication, which may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example. One having ordinary skill in the art will appreciate that multiple components may interoperate and modifications and variations are possible of achieving the electrical and data communication.

In some embodiments described herein, the term “coupled,” “connected,” and the like, may be used herein to indicate a connection, although not necessarily directly, and may include wired and/or wireless connections.

The term “network node” used herein can be any kind of network node comprised in a radio network which may further comprise any of a location server, a base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), g Node B (gNB), evolved Node B (eNB or eNodeB), Node B, multi-standard radio (MSR) radio node such as MSR BS, multi-cell/multicast coordination entity (MCE), integrated access and backhaul (IAB) node, relay node, donor node controlling relay, radio access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU) Remote Radio Head (RRH), a core network node (e.g., mobile management entity (MME), self-organizing network (SON) node, a coordinating node, positioning node, MDT node, etc.), an external node (e.g., 3rd party node, a node external to the current network), nodes in distributed antenna system (DAS), a spectrum access system (SAS) node, an element management system (EMS), etc. The network node may also comprise test equipment. The term “radio node” used herein may be used to also denote a wireless device (WD) such as a wireless device (WD) or a radio network node.

In some embodiments, the non-limiting terms wireless device (WD) or a user equipment (UE) are used interchangeably. The WD herein can be any type of wireless device capable of communicating with a network node or another WD over radio signals, such as wireless device (WD). The WD may also be a radio communication device, target device, device to device (D2D) WD, machine type WD or WD capable of machine to machine communication (M2M), low-cost and/or low-complexity WD, a sensor equipped with WD, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), an Internet of Things (loT) device, or a Narrowband loT (NB-IOT) device, etc.

Also, in some embodiments the generic term “radio network node” is used. It can be any kind of a radio network node which may comprise any of base station, radio base station, base transceiver station, base station controller, network controller, RNC, evolved Node B (eNB), Node B, gNB, Multi-cell/multicast Coordination Entity (MCE), IAB node, relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH).

In some embodiments, the “assistance data configuration” may indicate one or more resolutions associated with corresponding data.

In some embodiments, the “assistance data resolution indication” may indicate a resolution (e.g., standard or high) associated with data. The term “signaling” used herein may comprise any of: high-layer signaling (e.g., via Radio Resource Control (RRC) or a like), lower-layer signaling (e.g., via a physical control channel or a broadcast channel), or a combination thereof. The signaling may be implicit or explicit. The signaling may further be unicast, multicast or broadcast. The signaling may also be directly to another node or via a third node.

Signaling may generally comprise one or more symbols and/or signals and/or messages. A signal may comprise or represent one or more bits. An indication may represent signaling, and/or be implemented as a signal, or as a plurality of signals. One or more signals may be included in and/or represented by a message. Signaling, in particular control signaling, may comprise a plurality of signals and/or messages, which may be transmitted on different carriers and/or be associated to different signaling processes, e.g., representing and/or pertaining to one or more such processes and/or corresponding information. An indication may comprise signaling, and/or a plurality of signals and/or messages and/or may be comprised therein, which may be transmitted on different carriers and/or be associated to different acknowledgement signaling processes, e.g., representing and/or pertaining to one or more such processes. Signaling associated to a channel may be transmitted such that represents signaling and/or information for that channel, and/or that the signaling is interpreted by the transmitter and/or receiver to belong to that channel. Such signaling may generally comply with transmission parameters and/or format/s for the channel.

An indication generally may explicitly and/or implicitly indicate the information it represents and/or indicates. Implicit indication may for example be based on position and/or resource used for transmission. Explicit indication may for example be based on a parametrization with one or more parameters, and/or one or more index or indices corresponding to a table, and/or one or more bit patterns representing the information.

Configuring a radio node, in particular a terminal or WD (e.g., WD), may refer to the radio node being adapted or caused or set and/or instructed to operate according to the configuration (e.g., to monitor an x-RNTI or a binary sequence for C-RNTI to determine which table to be used to interpret an indication or signal). Configuring may be done by another device, e.g., a network node (e.g., network node) (for example, a base station or gNB) or network, in which case it may comprise transmitting configuration data to the radio node to be configured. Such configuration data may represent the configuration to be configured and/or comprise one or more instruction pertaining to a configuration, e.g., a configuration for transmitting and/or receiving on allocated resources, in particular frequency resources. A radio node may configure itself, e.g., based on configuration data received from a network or network node. A network node may utilize, and/or be adapted to utilize, its circuitry/ies for configuring. Configuration data may comprise and/or be represented by configuration information, and/or one or more corresponding indications and/or message/s.

Configuring a terminal or wireless device (WD) or node may involve instructing and/or causing the wireless device or node to change its configuration, e.g., at least one setting and/or register entry and/or operational mode. A terminal or wireless device or node may be adapted to configure itself, e.g., according to information or data in a memory of the terminal or wireless device (e.g., the indication of the resource allocation as discussed above). Configuring a node or terminal or wireless device by another device or node or a network may refer to and/or comprise transmitting information and/or data and/or instructions to the wireless device or node by the other device or node or the network.

Predefined in the context of this disclosure may refer to the related information being defined for example in a standard, and/or being available without specific configuration from a network or network node, e.g., stored in memory, for example independent of being configured. Configured or configurable may be considered to pertain to the corresponding information being set/configured, e.g., by the network or a network node.

In some embodiments, the term “obtain” or “obtaining” is used herein and may indicate obtaining in e.g., memory such as in the case where the information is predefined. The term “obtain” or “obtaining” as used herein may also indicate obtaining by receiving signaling indicating the information obtained.

Note that although terminology from one particular wireless system, such as, for example, 3GPP LTE and/or New Radio (NR), may be used in this disclosure, this should not be seen as limiting the scope of the disclosure to only the aforementioned system. Other wireless systems, including without limitation Wide Band Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMax), Ultra Mobile Broadband (UMB) and Global System for Mobile Communications (GSM), may also benefit from exploiting the ideas covered within this disclosure.

Note further, that functions described herein as being performed by a wireless device or a network node may be distributed over a plurality of wireless devices and/or network nodes. In other words, it is contemplated that the functions of the network node and wireless device described herein are not limited to performance by a single physical device and, in fact, can be distributed among several physical devices.

Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. It will be further understood that terms used herein should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

Some embodiments provide arrangements for GNSS RTK observation resolution indication. Referring again to the drawing figures, in which like elements are referred to by like reference numerals, there is shown in FIG. 4 a schematic diagram of a communication system 10, according to an embodiment, such as a 3GPP-type cellular network that may support standards such as LTE and/or NR (5G), which comprises an access network 12, such as a radio access network, and a core network 14. The access network 12 comprises a plurality of network nodes 16a, 16b, 16c (referred to collectively as network nodes 16), such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 18a, 18b, 18c (referred to collectively as coverage areas 18). Each network node 16a, 16b, 16c is connectable to the core network 14 over a wired or wireless connection 20. A first wireless device (WD) 22a located in coverage area 18a is configured to wirelessly connect to, or be paged by, the corresponding network node 16a. A second WD 22b in coverage area 18b is wirelessly connectable to the corresponding network node 16b. While a plurality of WDs 22a, 22b (collectively referred to as wireless devices 22) are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole WD is in the coverage area or where a sole WD is connecting to the corresponding network node 16. Note that although only two WDs 22 and three network nodes 16 are shown for convenience, the communication system may include many more WDs 22 and network nodes 16.

Also, it is contemplated that a WD 22 can be in simultaneous communication and/or configured to separately communicate with more than one network node 16 and more than one type of network node 16. For example, a WD 22 can have dual connectivity with a network node 16 that supports LTE and the same or a different network node 16 that supports NR. As an example, WD 22 can be in communication with an eNB for LTE/E-UTRAN and a gNB for NR/NG-RAN.

The communication system 10 may itself be connected to a host computer 24, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm. The host computer 24 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. The connections 26, 28 between the communication system 10 and the host computer 24 may extend directly from the core network 14 to the host computer 24 or may extend via an optional intermediate network 30. The intermediate network 30 may be one of, or a combination of more than one of, a public, private or hosted network. The intermediate network 30, if any, may be a backbone network or the Internet. In some embodiments, the intermediate network 30 may comprise two or more sub-networks (not shown).

The communication system of FIG. 3 as a whole enables connectivity between one of the connected WDs 22a, 22b and the host computer 24. The connectivity may be described as an over-the-top (OTT) connection. The host computer 24 and the connected WDs 22a, 22b are configured to communicate data and/or signaling via the OTT connection, using the access network 12, the core network 14, any intermediate network 30 and possible further infrastructure (not shown) as intermediaries. The OTT connection may be transparent in the sense that at least some of the participating communication devices through which the OTT connection passes are unaware of routing of uplink and downlink communications. For example, a network node 16 may not or need not be informed about the past routing of an incoming downlink communication with data originating from a host computer 24 to be forwarded (e.g., handed over) to a connected WD 22a. Similarly, the network node 16 need not be aware of the future routing of an outgoing uplink communication originating from the WD 22a towards the host computer 24.

A network node 16 is configured to include a determination unit 32 which is configured to determine an assistance data resolution indication based on assistance data configuration; and send the determined assistance data resolution indication to a wireless device.

A wireless device 22 is configured to include a resolution unit 34 which is configured to obtain Global Navigation Satellite System (GNSS) assistance data and assistance data resolution indication; and determine an assistance data resolution based on the obtained assistance data resolution indication.

Example implementations, in accordance with an embodiment, of the WD 22, network node 16 and host computer 24 discussed in the preceding paragraphs will now be described with reference to FIG. 5. In a communication system 10, a host computer 24 comprises hardware (HW) 38 including a communication interface 40 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system 10. The host computer 24 further comprises processing circuitry 42, which may have storage and/or processing capabilities. The processing circuitry 42 may include a processor 44 and memory 46. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 42 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 44 may be configured to access (e.g., write to and/or read from) memory 46, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read- Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).

Processing circuitry 42 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by host computer 24. Processor 44 corresponds to one or more processors 44 for performing host computer 24 functions described herein. The host computer 24 includes memory 46 that is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software 48 and/or the host application 50 may include instructions that, when executed by the processor 44 and/or processing circuitry 42, causes the processor 44 and/or processing circuitry 42 to perform the processes described herein with respect to host computer 24. The instructions may be software associated with the host computer 24.

The software 48 may be executable by the processing circuitry 42. The software 48 includes a host application 50. The host application 50 may be operable to provide a service to a remote user, such as a WD 22 connecting via an OTT connection 52 terminating at the WD 22 and the host computer 24. In providing the service to the remote user, the host application 50 may provide user data which is transmitted using the OTT connection 52. The “user data” may be data and information described herein as implementing the described functionality. In one embodiment, the host computer 24 may be configured for providing control and functionality to a service provider and may be operated by the service provider or on behalf of the service provider. The processing circuitry 42 of the host computer 24 may enable the host computer 24 to observe, monitor, control, transmit to and/or receive from the network node 16 and/or the wireless device 22. The processing circuitry 42 of the host computer 24 may include a monitor unit 54 configured to enable the service provider to observe, monitor, control, transmit to and/or receive from the network node 16 and/or the wireless device 22.

The communication system 10 further includes a network node 16 provided in a communication system 10 and including hardware 58 enabling it to communicate with the host computer 24 and with the WD 22. The hardware 58 may include a communication interface 60 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 10, as well as a radio interface 62 for setting up and maintaining at least a wireless connection 64 with a WD 22 located in a coverage area 18 served by the network node 16. The radio interface 62 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and/or one or more RF transceivers. The communication interface 60 may be configured to facilitate a connection 66 to the host computer 24. The connection 66 may be direct or it may pass through a core network 14 of the communication system 10 and/or through one or more intermediate networks 30 outside the communication system 10.

In the embodiment shown, the hardware 58 of the network node 16 further includes processing circuitry 68. The processing circuitry 68 may include a processor 70 and a memory 72. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 68 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 70 may be configured to access (e.g., write to and/or read from) the memory 72, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).

Thus, the network node 16 further has software 74 stored internally in, for example, memory 72, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the network node 16 via an external connection. The software 74 may be executable by the processing circuitry 68. The processing circuitry 68 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by network node 16. Processor 70 corresponds to one or more processors 70 for performing network node 16 functions described herein. The memory 72 is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software 74 may include instructions that, when executed by the processor 70 and/or processing circuitry 68, causes the processor 70 and/or processing circuitry 68 to perform the processes described herein with respect to network node 16. For example, processing circuitry 68 of the network node 16 may include determination unit 32 configured to perform network node methods discussed herein, such as the methods discussed with reference to FIG. 10 as well as other figures. The communication system 10 further includes the WD 22 already referred to. The WD 22 may have hardware 80 that may include a radio interface 82 configured to set up and maintain a wireless connection 64 with a network node 16 serving a coverage area 18 in which the WD 22 is currently located. The radio interface 82 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and/or one or more RF transceivers.

The hardware 80 of the WD 22 further includes processing circuitry 84. The processing circuitry 84 may include a processor 86 and memory 88. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 84 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 86 may be configured to access (e.g., write to and/or read from) memory 88, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).

Thus, the WD 22 may further comprise software 90, which is stored in, for example, memory 88 at the WD 22, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the WD 22. The software 90 may be executable by the processing circuitry 84. The software 90 may include a client application 92. The client application 92 may be operable to provide a service to a human or non-human user via the WD 22, with the support of the host computer 24. In the host computer 24, an executing host application 50 may communicate with the executing client application 92 via the OTT connection 52 terminating at the WD 22 and the host computer 24. In providing the service to the user, the client application 92 may receive request data from the host application 50 and provide user data in response to the request data. The OTT connection 52 may transfer both the request data and the user data. The client application 92 may interact with the user to generate the user data that it provides.

The processing circuitry 84 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by WD 22. The processor 86 corresponds to one or more processors 86 for performing WD 22 functions described herein. The WD 22 includes memory 88 that is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software 90 and/or the client application 92 may include instructions that, when executed by the processor 86 and/or processing circuitry 84, causes the processor 86 and/or processing circuitry 84 to perform the processes described herein with respect to WD 22. For example, the processing circuitry 84 of the wireless device 22 may include a resolution unit 34 configured to perform WD methods discussed herein, such as the methods discussed with reference to FIG. 11 as well as other figures.

In some embodiments, the inner workings of the network node 16, WD 22, and host computer 24 may be as shown in FIG. 5 and independently, the surrounding network topology may be that of FIG. 4.

In FIG. 5, the OTT connection 52 has been drawn abstractly to illustrate the communication between the host computer 24 and the wireless device 22 via the network node 16, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure may determine the routing, which it may be configured to hide from the WD 22 or from the service provider operating the host computer 24, or both. While the OTT connection 52 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).

The wireless connection 64 between the WD 22 and the network node 16 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to the WD 22 using the OTT connection 52, in which the wireless connection 64 may form the last segment. More precisely, the teachings of some of these embodiments may improve the data rate, latency, and/or power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, better responsiveness, extended battery lifetime, etc.

In some embodiments, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 52 between the host computer 24 and WD 22, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection 52 may be implemented in the software 48 of the host computer 24 or in the software 90 of the WD 22, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which the OTT connection 52 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 48, 90 may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 52 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect the network node 16, and it may be unknown or imperceptible to the network node 16. Some such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary WD signaling facilitating the host computer’s 24 measurements of throughput, propagation times, latency and the like. In some embodiments, the measurements may be implemented in that the software 48, 90 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 52 while it monitors propagation times, errors etc.

Thus, in some embodiments, the host computer 24 includes processing circuitry 42 configured to provide user data and a communication interface 40 that is configured to forward the user data to a cellular network for transmission to the WD 22. In some embodiments, the cellular network also includes the network node 16 with a radio interface 62. In some embodiments, the network node 16 is configured to, and/or the network node’s 16 processing circuitry 68 is configured to perform the functions and/or methods described herein for preparing/initiating/maintaining/supporting/ending a transmission to the WD 22, and/or preparing/terminating/maintaining/supporting/ending in receipt of a transmission from the WD 22.

In some embodiments, the host computer 24 includes processing circuitry 42 and a communication interface 40 that is configured to a communication interface 40 configured to receive user data originating from a transmission from a WD 22 to a network node 16. In some embodiments, the WD 22 is configured to, and/or comprises a radio interface 82 and/or processing circuitry 84 configured to perform the functions and/or methods described herein for preparing/initiating/maintaining/supporting/ending a transmission to the network node 16, and/or preparing/terminating/maintaining/supporting/ending in receipt of a transmission from the network node 16.

Although FIGS. 4 and 5 show various “units” such as determination unit 32, and resolution unit 34 as being within a respective processor, it is contemplated that these units may be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuitry. In other words, the units may be implemented in hardware or in a combination of hardware and software within the processing circuitry.

FIG. 6 is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of FIGS. 4 and 5, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIG. 5. In a first step of the method, the host computer 24 provides user data (Block SI 00). In an optional substep of the first step, the host computer 24 provides the user data by executing a host application, such as, for example, the host application 50 (Block SI 02). In a second step, the host computer 24 initiates a transmission carrying the user data to the WD 22 (Block SI 04). In an optional third step, the network node 16 transmits to the WD 22 the user data which was carried in the transmission that the host computer 24 initiated, in accordance with the teachings of the embodiments described throughout this disclosure (Block SI 06). In an optional fourth step, the WD 22 executes a client application, such as, for example, the client application 92, associated with the host application 50 executed by the host computer 24 (Block SI 08).

FIG. 7 is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of FIG. 4, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS. 4 and 5. In a first step of the method, the host computer 24 provides user data (Block SI 10). In an optional substep (not shown) the host computer 24 provides the user data by executing a host application, such as, for example, the host application 50. In a second step, the host computer 24 initiates a transmission carrying the user data to the WD 22 (Block SI 12). The transmission may pass via the network node 16, in accordance with the teachings of the embodiments described throughout this disclosure. In an optional third step, the WD 22 receives the user data carried in the transmission (Block SI 14).

FIG. 8 is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of FIG. 4, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS. 4 and 5. In an optional first step of the method, the WD 22 receives input data provided by the host computer 24 (Block SI 16). In an optional substep of the first step, the WD 22 executes the client application 92, which provides the user data in reaction to the received input data provided by the host computer 24 (Block SI 18). Additionally or alternatively, in an optional second step, the WD 22 provides user data (Block S120). In an optional substep of the second step, the WD provides the user data by executing a client application, such as, for example, client application 92 (Block S122). In providing the user data, the executed client application 92 may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the WD 22 may initiate, in an optional third substep, transmission of the user data to the host computer 24 (Block S124). In a fourth step of the method, the host computer 24 receives the user data transmitted from the WD 22, in accordance with the teachings of the embodiments described throughout this disclosure (Block S126).

FIG. 9 is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of FIG. 4, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS. 4 and 5. In an optional first step of the method, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 16 receives user data from the WD 22 (Block S128). In an optional second step, the network node 16 initiates transmission of the received user data to the host computer 24 (Block S130). In a third step, the host computer 24 receives the user data carried in the transmission initiated by the network node 16 (Block SI 32).

FIG. 10 is a flowchart of an exemplary process in a network node 16 according to some embodiments of the present disclosure. One or more Blocks and/or functions and/or methods performed by the network node 16 may be performed by one or more elements of network node 16 such as by determination unit 32 in processing circuitry 68, processor 70, radio interface 62, etc. according to the example method. The example method includes determining (Block SI 34), such as via determination unit 32, processing circuitry 68, processor 70 and/or radio interface 62, an assistance data resolution indication based on an assistance data configuration. The method includes sending (Block S136), such as via determination unit 32, processing circuitry 68, processor 70 and/or radio interface 62, the determined assistance data resolution indication to a wireless device.

In some embodiments, the method further includes receiving a request message for Global Navigation Satellite System (GNSS) assistance data from the wireless device. In some embodiments, sending, such as via determination unit 32, processing circuitry 68, processor 70 and/or radio interface 62, the determined assistance data resolution indication together with the GNSS assistance data to the WD. In some embodiments, the assistance data resolution indication indicates that the GNSS assistance data is one of a standard resolution and a high resolution. In some embodiments, when the assistance data resolution indication indicates the standard resolution, the GNSS assistance data corresponds to a first type of Radio Technical Commission for Maritime, RTCM, Multiple Signal Message, MSM; and when the assistance data resolution indication indicates the high resolution, the GNSS assistance data corresponds to a second type of RTCM MSM.

In some embodiments, the assistance data resolution indication indicates an amount of accuracy associated with a positioning estimate that is based on the GNSS assistance data. In some embodiments, the assistance data resolution indication is comprised in a Global Navigation Satellite System, GNSS, Real Time Kinematics, RTK, information element, IE. In some embodiments, a presence of the assistance data resolution indication in the GNSS RTK IE indicates that the GNSS assistance data is a standard resolution and an absence of the assistance data resolution indication in the GNSS RTK IE indicates that the GNSS assistance data is a high resolution.

In some embodiments, a presence of the assistance data resolution indication in the GNSS RTK IE indicates that the GNSS assistance data is a high resolution and an absence of the assistance data resolution indication in the GNSS RTK IE indicates that the GNSS assistance data is a standard resolution. In some embodiments, the method further includes receiving, such as via determination unit 32, processing circuitry 68, processor 70 and/or radio interface 62, information about a capability to support at least one GNSS assistance data resolution from the WD.

FIG. 11 is a flowchart of an example process in a wireless device 22 according to some embodiments of the present disclosure. One or more Blocks and/or functions and/or methods performed by WD 22 may be performed by one or more elements of WD 22 such as by resolution unit 34 in processing circuitry 84, processor 86, radio interface 82, etc. The example method includes obtaining (Block S138), such as via resolution unit 34, processing circuitry 84, processor 86 and/or radio interface 82, Global Navigation Satellite System (GNSS) assistance data and an assistance data resolution indication. The method includes determining (Block S140), such as via resolution unit 34, processing circuitry 84, processor 86 and/or radio interface 82, an assistance data resolution associated with the GNSS assistance data based on the obtained assistance data resolution indication.

In some embodiments, the method further includes sending, such as via resolution unit 34, processing circuitry 84, processor 86 and/or radio interface 82, a request message for Global Navigation Satellite System (GNSS) assistance data to the network node. In some embodiments, the method further includes using, such as via resolution unit 34, processing circuitry 84, processor 86 and/or radio interface 82, the GNSS assistance data and the determined assistance data resolution for positioning. In some embodiments, the assistance data resolution indication indicates that the GNSS assistance data is one of a standard resolution and a high resolution. In some embodiments, when the assistance data resolution indication indicates the standard resolution, the GNSS assistance data corresponds to a first type of Radio Technical Commission for Maritime, RTCM, Multiple Signal Message, MSM; and when the assistance data resolution indication indicates the high resolution, the GNSS assistance data corresponds to a second type of RTCM MSM.

In some embodiments, a presence of the assistance data resolution indication in the GNSS RTK IE indicates that the GNSS assistance data is a high resolution and an absence of the assistance data resolution indication in the GNSS RTK IE indicates that the GNSS assistance data is a standard resolution. In some embodiments, the method further includes sending, such as via resolution unit 34, processing circuitry 84, processor 86 and/or radio interface 82, information about a capability to support at least one GNSS assistance data resolution to the network node.

Having described the general process flow of arrangements of the disclosure and having provided examples of hardware and software arrangements for implementing the processes and functions of the disclosure, the sections below provide details and examples of arrangements for GNSS RTK observation resolution indication, which may be implemented by the network node 16, wireless device 22 and/or host computer 24.

FIG. 12 illustrates some embodiments of the present disclosure from the perspective of the WD 22. Optionally (step S142), the WD 22 provides to the network node 16 (optionally upon request from the network node 16) capabilities for supporting different GNSS assistance data resolutions. Furthermore, optionally (step S144), the target WD 22 provides an assistance data request to the network node 16 for GNSS assistance data. In step S146, the WD 22 obtains, from the network node 16, GNSS assistance data together with a GNSS assistance data resolution indication. In one embodiment, the GNSS assistance data resolution indicator is obtained from a different network node 16, from higher layer in the WD 22 or is pre-configured. In step S148, the WD 22 uses the GNSS assistance data indicator to assess the resolution of the GNSS assistance data and uses the assistance data for supporting positioning.

FIG. 13 illustrates some embodiments of the present disclosure from the perspective of the network node 16. Optionally (step SI 50), the network node 16 receives, from the WD 22, (optionally upon request from the network node 16) capabilities for supporting different GNSS assistance data resolutions. Furthermore, optionally (step SI 52), the network node 16 obtains, from the target WD 22, an assistance data request for GNSS assistance data. In step S154, the network node 16 determines, based on stored assistance data configuration, an assistance data resolution indication. In step SI 56, the network node 16 provides, to the WD 22, GNSS assistance data together with a GNSS assistance data resolution indication.

FIG. 14 provides a signaling chart of some example steps of the present disclosure. Optionally (step S158), the WD 22 provides to the network node 16 (optionally upon request from the network node 16) capabilities for supporting different GNSS assistance data resolutions. Furthermore, optionally (step S160), the target WD 22 provides an assistance data (AD) request to the network node 16 for GNSS assistance data. In step S162, the network node 16 determines, based on stored assistance data configuration, an assistance data resolution indication. In step SI 64, the network node 16 provides, to the WD 22, GNSS assistance data together with a GNSS assistance data resolution indication. In one embodiment, the GNSS assistance data resolution indicator is obtained from a different network node 16, from a higher layer in the WD 22 or is pre-configured at the WD 22.

In step S166, the WD 22 uses the GNSS assistance data indicator to assess the resolution of the GNSS assistance data and uses the assistance data for supporting positioning.

In some embodiments, the network node 16 may be considered a location server 2, but could also be a radio base station 4 or some other network node. a) GNSS assistance data resolution indication

In some embodiments, the resolution of the GNSS assistance data may enable the WD 22 to assess uncertainty of the resulting positioning estimates. It may also enable WDs 22 that internally translates LPP messages into the corresponding RTCM MSM messages to correctly determine which MSM type to translate to.

FIG. 15 shows two examples of a WD 22 architecture. In the example, a correction data provider 8 provides RTCM encoded correction data for example via NTRIP signaling over an IP interface. The RTCM encoded correction data is represented by MSM messages, where MSM4 and MSM6 uses standard resolution, while MSM5 and MSM7 uses high resolution of the assistance data. A WD 22 communicates with a location server 2 and obtains GNSS assistance data via LPP.

FIG. 15 includes a WD 22 with an LPP protocol stack, a GNSS receiver and a positioning engine can benefit from the GNSS assistance data resolution indication to understand the uncertainty of the different attributes.

FIG. 15 further shows a WD 22 with an LPP protocol stack, a GNSS receiver, a legacy positioning engine supporting only RTCM messages and a translator entity translating from 3GPP LPP to RTCM as described further below.

In some embodiments, the LPP representation of the GNSS observations associated to a specific GNSS signal from a specific satellite is given by:

- ASN1 START

GNSS-RTK-Observations-rl5 ::= SEQUENCE { epochTime-rl5 GNSS-

SystemTime, gnss-Ob servationLi st-r 15 GN S S-Ob servationLi st- rl5,

}

GNSS-ObservationList-rl5 ::= SEQUENCE (SIZE(1..64)) OF GNSS-RTK- SatelliteDataElement-r 15

GNSS-RTK-SatelliteDataElement-rl5 ::= SEQUENCE { svID-rl5 SV-ID, integer-ms-rl5 INTEGER

(0..254) OPTIONAL, - Need ON rough-range-rl5 INTEGER

(0..1023), rough-phase-range-rate-r 15 INTEGER (-8192..8191)

OPTIONAL, - Need ON gnss-rtk-SatelliteSignalDataList-rl 5 GNSS-RTK-SatelliteSignalDataList-rl 5,

}

GNSS-RTK-SatelliteSignalDataList-rl5 ::= SEQUENCE (SIZE(1..24)) OF

GNSS-RTK-SatelliteSignalDataElement-rl5

GNSS-RTK-SatelliteSignalDataElement-rl5 ::= SEQUENCE { gnss-SignalID-rl5 GNSS-SignallD, fine-PseudoRange-r 15 INTEGER (-524288..524287), fine-PhaseRange-r 15 INTEGER (-

8388608..8388607), lockTimelndicator-r 15 INTEGER (0 .1023), halfCy cl eAmbiguity Indicator-r 15 BIT STRING (SIZE (1)), carrier-to-noise-ratio-r 15 INTEGER (0 .1023)

OPTIONAL, - Need ON fine-PhaseRangeRate-r 15 INTEGER (- 16384..16383) OPTIONAL, - Need ON

}

- ASN1STOP

The attributes may be optional to make it possible to represent MSM1 - MSM7. However, all attributes may be represented using high resolution, which may mean that it is not possible to explicitly indicate that a particular attribute was originally represented using standard resolution. An example of the MSM attribute resolutions are summarized in Table 2.

Table 1. MSM attribute resolutions

However, in some embodiments, given an GNSS assistance data resolution indicator standard/high, the WD 22 can determine the original attribute resolution as well as the MSM type given the information about what attributes that are present in the assistance data. For example, if all attributes except GNSS signal fine Phase range Rates is provided, and the resolution is indicated as ‘standard’, then the WD 22 may determine that MSM4 was originally used. If the resolution instead would have been indicated as ‘high’, then the WD 22 may determine that MSM6 was originally used etc.

In some embodiments, the GNSS assistance data resolution indication can be in one mode of the present disclosure represented in 3GPP LPP as a Boolean, indicating by its presence that high resolution is adopted (standard resolution if omitted).

- ASN1 START gnss-ObservationHighRes-rl6 NULL

OPTIONAL

- ASN1STOP

For example, in the GNSS RTK observations information element (IE): Option 1: Indicate optionally that a standard resolution has been used. If omitted, the assumption is that a high resolution has been used.

- ASN1 START

GNSS-RTK-Observations-rl5 ::= SEQUENCE { epochTime-rl5 GNSS-

SystemTime, gnss-ObservationList-r 15 GN S S -Ob servati onLi st- rl5,

[[ gnss-ObservationStdRes-r!6 NULL

OPTIONAL

]] } GNSS-ObservationList-rl5 : := SEQUENCE (SIZE(1..64)) OF GNSS-RTK- SatelliteDataElement-r 15

GNSS-RTK-SatelliteDataElement-rl5 : := SEQUENCE { svID-rl5 SV-ID, integer-ms-rl5 INTEGER

(0..254) OPTIONAL, - Need ON rough-range-rl5 INTEGER

(0..1023), rough-phase-range-rate-r 15 INTEGER (-8192..8191)

}

GNSS-RTK-SatelliteSignalDataList-rl5 ::= SEQUENCE (SIZE(1..24)) OF

GNSS-RTK-SatelliteSignalDataElement-rl5

GNSS-RTK-SatelliteSignalDataElement-rl5 : := SEQUENCE { gnss-SignalID-rl5 GNSS-SignaUD, fme-PseudoRange-r 15 INTEGER (-524288..524287), fine-PhaseRange-r 15 INTEGER (- 8388608..8388607), lockTimelndicator-r 15 INTEGER (0 . 1023), halfCy cl eAmbiguity Indicator-r 15 BIT STRING (SIZE (1)), carner-to-noise-ratio-rl5 INTEGER (0..1023)

OPTIONAL, - Need ON fine-PhaseRangeRate-rl 5 INTEGER (-

16384 .16383) OPTIONAL, - Need ON

}

- ASN1STOP

Option 2: Indicate optionally that a high resolution has been used. If omitted, the assumption is that a standard resolution has been used.

- ASN1 START

GNSS-RTK-Observations-rl5 ::= SEQUENCE { epochTime-rl5 GNSS-

SystemTime, gnss-Ob servationLi st-r 15 GN S S-Ob servationLi st- rl5, •••? [[ gnss-ObservationHighRes-r!6 NULL

OPTIONAL

]] } GNSS-ObservationList-rl5 ::= SEQUENCE (SIZE(1..64)) OF GNSS-RTK- SatelliteDataElement-r 15 GNSS-RTK-SatelliteDataElement-rl5 ::= SEQUENCE) svID-rl5 SV-ID, integer-ms-rl5 INTEGER

(0..254) OPTIONAL, - Need ON rough-range-rl5 INTEGER

(0..1023), rough-phase-range-rate-r 15 INTEGER (-8192..8191)

OPTIONAL, - Need ON gnss-rtk-SatelliteSignalDataList-rl 5 GNSS-RTK-SatelliteSignalDataList-rl 5, GNSS-RTK-SatelliteSignalDataList-rl5 ::= SEQUENCE (SIZE(1..24)) OF

GNSS-RTK-SatelliteSignalDataElement-rl5

GNSS-RTK-SatelliteSignalDataElement-rl5 ::= SEQUENCE { gnss-SignalID-rl5 GNSS-SignallD, fme-PseudoRange-r 15 INTEGER (-524288..524287), fine-PhaseRange-r 15 INTEGER (-

OPTIONAL, - Need ON fme-PhaseRangeRate-r 15 INTEGER (- 16384..16383) OPTIONAL, - Need ON

}

- ASN1STOP

In one embodiment, the GNSS assistance data resolution indicator is obtained from a different network node 16, from higher layer in the WD 22 or is preconfigured. One example of a pre-configured indication is that the positioning engine is only supporting standard resolution of GNSS assistance data, and no matter what is provided via LPP, the WD 22 uses the data as if it was standard resolution. In case of translation into MSM messages, this may mean that MSM6 and MSM7 would never be used in that case, and instead the 3 GPP LPP messages are translated into MSM4 and MSM5 respectively. b) Unicast signaling

The signaling is mainly described using steps of the present disclosure. The LPP transactions are the same independent of whether control plane signaling or user plane signaling via SUPL is used. FIG. 16 illustrates an example of one embodiment of the present disclosure from the perspective of the WD 22. FIG. 16 also includes details about a translation step from 3 GPP LPP to RTCM.

Optionally (step SI 68), the WD 22 provides to the network node 16 (optionally upon request from the network node 16) capabilities for supporting different GNSS assistance data resolutions. Furthermore, optionally (step S170), the target WD 22 provides an assistance data request to the network node 16 for GNSS assistance data. In step S172, the WD 22 obtains, from the network node 16, GNSS assistance data together with a GNSS assistance data resolution indication. In one embodiment, the GNSS assistance data resolution indicator is obtained from a different network node 16, from higher layer in the WD 22 or is pre-configured. In step S174, the WD 22 uses the GNSS assistance data indicator to translate the GNSS assistance data to a different representation. In one mode, the WD 22 translates 3GPP LPP to RTCM MSM. In step S176, the WD 22 uses the translated GNSS assistance data for positioning, for example by using a legacy positioning engine with support for RTCM MSM. c) Broadcast signaling

In addition, the information can also be broadcasted, which is described by FIG. 16.

In step SI 78, the network node 16 determines, based on stored assistance data configuration, an assistance data resolution indication. In step SI 80, the network node (e.g., location server) 16 compiles assistance data for broadcast, comprising the assistance data resolution indication. In step SI 82, the network node 16 provides, to the radio base station, GNSS assistance data together with a GNSS assistance data resolution indication.

FIG. 17 illustrates an example from the perspective of the WD 22. In step SI 84, the WD 22 obtains GNSS assistance data and an assistance data resolution indicator from radio base station broadcast. In one embodiment, the GNSS assistance data resolution indicator is obtained from a different network node 16, from higher layer in the WD 22 or is pre-configured. In step SI 86, the WD 22 uses the assistance data resolution indication to assess the resolution of the GNSS assistance data. Steps SI 84 and SI 86 may be different in case the WD 22 translates the GNSS assistance data into a different representation. In this case, the steps of FIG. 19 may apply. Referring to FIG. 18, in step SI 88, the WD 22 obtains GNSS assistance data and an assistance data resolution indicator from radio base station broadcast. In one embodiment, the GNSS assistance data resolution indicator is obtained from a different network node 16, from higher layer in the WD 22 or is pre-configured. In step 1 S 190, the WD 22 uses the GNSS assistance data indicator to translate the GNSS assistance data to a different representation. In one mode, the WD 22 translates 3GPP LPP to RTCM MSM. In step S192, the WD 22 uses the translated GNSS assistance data for positioning, for example by using a legacy positioning engine with support for RTCM MSM.

In another embodiment, the GNSS assistance data resolution indication is combined with an encryption strategy, where the standard resolution is associated with a first ciphering key or even no ciphering key, and the high resolution is associated with a second ciphering key. Such an association enables ser differentiation.

Some embodiments provide arrangements for a compact GNSS assistance data resolution indication provided to the WD 22 as part of the GNSS assistance data to enable the WD 22 to assess the original GNSS correct data resolution.

Some embodiments may include one or more of the following:

Embodiment Al . A network node configured to communicate with a wireless device (WD), the network node configured to, and/or comprising a radio interface and/or comprising processing circuitry configured to: determine an assistance data resolution indication based on assistance data configuration; and send the determined assistance data resolution indication to a wireless device.

Embodiment A2. The network node of Embodiment Al, wherein the network node and/or the radio interface and/or the processing circuitry is further configured to: receive a request message comprising Global Navigation Satellite System (GNSS) assistance data from the wireless device. Embodiment Bl. A method implemented in a network node, the method comprising: determining an assistance data resolution indication based on assistance data configuration; and sending the determined assistance data resolution indication to a wireless device.

Embodiment B2. The method of Embodiment Bl, further comprising: receiving a request message comprising Global Navigation Satellite System (GNSS) assistance data from the wireless device.

Embodiment Cl. A wireless device (WD) configured to communicate with a network node, the WD configured to, and/or comprising a radio interface and/or processing circuitry configured to: obtain Global Navigation Satellite System (GNSS) assistance data and assistance data resolution indication; and determine an assistance data resolution based on the obtained assistance data resolution indication.

Embodiment C2. The WD of Embodiment Cl, wherein the WD and/or the radio interface and/or the processing circuitry is further configured to: send a request message comprising Global Navigation Satellite System (GNSS) assistance data to the network node.

Embodiment DI . A method implemented in a wireless device (WD), the method comprising: obtaining Global Navigation Satellite System (GNSS) assistance data and assistance data resolution indication; and determining an assistance data resolution based on the obtained assistance data resolution indication.

Embodiment D2. The method of Embodiment DI, further comprising: sending a request message comprising Global Navigation Satellite System (GNSS) assistance data to the network node.

As will be appreciated by one of skill in the art, the concepts described herein may be embodied as a method, data processing system, computer program product and/or computer storage media storing an executable computer program. Accordingly, the concepts described herein may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects all generally referred to herein as a “circuit” or “module.” Any process, step, action and/or functionality described herein may be performed by, and/or associated to, a corresponding module, which may be implemented in software and/or firmware and/or hardware. Furthermore, the disclosure may take the form of a computer program product on a tangible computer usable storage medium having computer program code embodied in the medium that can be executed by a computer. Any suitable tangible computer readable medium may be utilized including hard disks, CD-ROMs, electronic storage devices, optical storage devices, or magnetic storage devices.

Some embodiments are described herein with reference to flowchart illustrations and/or block diagrams of methods, systems and computer program products. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer (to thereby create a special purpose computer), special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer readable memory or storage medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instruction means which implement the function/act specified in the flowchart and/or block diagram block or blocks.

The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

It is to be understood that the functions/acts noted in the blocks may occur out of the order noted in the operational illustrations. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality/acts involved. Although some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows.

Computer program code for carrying out operations of the concepts described herein may be written in an object oriented programming language such as Java® or C++. However, the computer program code for carrying out operations of the disclosure may also be written in conventional procedural programming languages, such as the "C" programming language. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer. In the latter scenario, the remote computer may be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

Many different embodiments have been disclosed herein, in connection with the above description and the drawings. It will be understood that it would be unduly repetitious and obfuscating to literally describe and illustrate every combination and subcombination of these embodiments. Accordingly, all embodiments can be combined in any way and/or combination, and the present specification, including the drawings, shall be construed to constitute a complete written description of all combinations and subcombinations of the embodiments described herein, and of the manner and process of making and using them, and shall support claims to any such combination or subcombination.

Abbreviations that may be used in the preceding description include:

Abbreviation Explanation

5GC 5G Core EPC Evolved Packet Core

E-SMLC Evolved-Serving Mobile Location Centre

GNSS Global Navigation Satellite System

LMF Location Management Function

LPP LTE Positioning Protocol

LPPa LTE Positioning Protocol Annex

LTE Long Term Evolution

MME Mobility Management Entity

MSM Multiple Signal Message

NR New Radio

RRC Radio Resource Control

RTCM Radio Technical Commission for Maritime

RTK Real Time Kinematic

SET SUPL Enabled Terminal

SLP SUPL Location Platform

SUPL Secure User Plane Location

It will be appreciated by persons skilled in the art that the embodiments described herein are not limited to what has been particularly shown and described herein above. In addition, unless mention was made above to the contrary, it should be noted that all of the accompanying drawings are not to scale. A variety of modifications and variations are possible in light of the above teachings without departing from the scope of the following claims.

Claims

What is claimed is:

1. A method implemented in a network node (16), the method comprising: determining (SI 34) an assistance data resolution indication based on an assistance data configuration; and sending (S136) the determined assistance data resolution indication to a wireless device, WD (22).

2. The method of Claim 1, further comprising: receiving a request message for Global Navigation Satellite System, GNSS, assistance data from the wireless device.

3. The method of Claim 3, wherein sending the determined assistance data resolution indication together with the GNSS assistance data to the WD (22).

4. The method of any one of Claims 1-3, wherein the assistance data resolution indication indicates that the GNSS assistance data is one of a standard resolution and a high resolution.

5. The method of Claim 4, wherein: when the assistance data resolution indication indicates the standard resolution, the GNSS assistance data corresponds to a first type of Radio Technical Commission for Maritime, RTCM, Multiple Signal Message, MSM; and when the assistance data resolution indication indicates the high resolution, the GNSS assistance data corresponds to a second type of RTCM MSM.

6. The method of Claim 4, wherein the assistance data resolution indication indicates an amount of accuracy associated with a positioning estimate that is based on the GNSS assistance data.

7. The method of any one of Claims 1-6, wherein the assistance data resolution indication is comprised in a Global Navigation Satellite System, GNSS, Real Time Kinematics, RTK, information element, IE.

8. The method of Claim 7, wherein a presence of the assistance data resolution indication in the GNSS RTK IE indicates that the GNSS assistance data is a standard resolution and an absence of the assistance data resolution indication in the GNSS RTK IE indicates that the GNSS assistance data is a high resolution.

9. The method of Claim 7, wherein a presence of the assistance data resolution indication in the GNSS RTK IE indicates that the GNSS assistance data is a high resolution and an absence of the assistance data resolution indication in the GNSS RTK IE indicates that the GNSS assistance data is a standard resolution.

10. The method of any one of Claims 1-9, further comprising: receiving information about a capability to support at least one GNSS assistance data resolution from the WD (22).

11. A method implemented in a wireless device, WD (22), configured to communicate with a network node (16), the method comprising: obtaining (S138) Global Navigation Satellite System, GNSS, assistance data and an assistance data resolution indication; and determining (S140) an assistance data resolution associated with the GNSS assistance data based on the obtained assistance data resolution indication.

12. The method of Claim 11, further comprising: sending a request message for the GNSS assistance data to the network node (16).

13. The method of Claim 12, further comprising: using the GNSS assistance data and the determined assistance data resolution for positioning.

14. The method of any one of Claims 11-13, wherein the assistance data resolution indication indicates that the GNSS assistance data is one of a standard resolution and a high resolution.

15. The method of Claim 14, wherein: when the assistance data resolution indication indicates the standard resolution, the GNSS assistance data corresponds to a first type of Radio Technical Commission for Maritime, RTCM, Multiple Signal Message, MSM; and when the assistance data resolution indication indicates the high resolution, the GNSS assistance data corresponds to a second type of RTCM MSM.

16. The method of Claim 14, wherein the assistance data resolution indication indicates an amount of accuracy associated with a positioning estimate that is based on the GNSS assistance data.

17. The method of any one of Claims 11-16, wherein the assistance data resolution indication is comprised in a Global Navigation Satellite System, GNSS, Real Time Kinematics, RTK, information element, IE.

18. The method of Claim 17, wherein a presence of the assistance data resolution indication in the GNSS RTK IE indicates that the GNSS assistance data is a standard resolution and an absence of the assistance data resolution indication in the GNSS RTK IE indicates that the GNSS assistance data is a high resolution.

19. The method of Claim 17, wherein a presence of the assistance data resolution indication in the GNSS RTK IE indicates that the GNSS assistance data is a high resolution and an absence of the assistance data resolution indication in the GNSS RTK IE indicates that the GNSS assistance data is a standard resolution.

20. The method of any one of Claims 11-19, further comprising: sending information about a capability to support at least one GNSS assistance data resolution to the network node (16).

21. A network node (16) comprising processing circuitry (68), the processing circuitry (68) configured to cause the network node (16) to: determine an assistance data resolution indication based on an assistance data configuration; and send the determined assistance data resolution indication to a wireless device, WD

22. The network node (16) of Claim 21, wherein the processing circuitry (68) is further configured to cause the network node (16) to: receive a request message for Global Navigation Satellite System, GNSS, assistance data from the wireless device.

23. The network node (16) of Claim 23, wherein the processing circuitry (68) is configured to send the determined assistance data resolution indication together with the GNSS assistance data to the WD (22).

24. The network node (16) of any one of Claims 21-23, wherein the assistance data resolution indication indicates that the GNSS assistance data is one of a standard resolution and a high resolution.

25. The network node (16) of Claim 24, wherein: when the assistance data resolution indication indicates the standard resolution, the GNSS assistance data corresponds to a first type of Radio Technical Commission for Maritime, RTCM, Multiple Signal Message, MSM; and when the assistance data resolution indication indicates the high resolution, the GNSS assistance data corresponds to a second type of RTCM MSM.

26. The network node (16) of Claim 24, wherein the assistance data resolution indication indicates an amount of accuracy associated with a positioning estimate that is based on the GNSS assistance data.

27. The network node (16) of any one of Claims 21-26, wherein the assistance data resolution indication is comprised in a Global Navigation Satellite System, GNSS, Real Time Kinematics, RTK, information element, IE.

28. The network node (16) of Claim 27, wherein a presence of the assistance data resolution indication in the GNSS RTK IE indicates that the GNSS assistance data is a standard resolution and an absence of the assistance data resolution indication in the GNSS RTK IE indicates that the GNSS assistance data is a high resolution.

29. The network node (16) of Claim 27, wherein a presence of the assistance data resolution indication in the GNSS RTK IE indicates that the GNSS assistance data is a high resolution and an absence of the assistance data resolution indication in the GNSS RTK IE indicates that the GNSS assistance data is a standard resolution.

30. The network node (16) of any one of Claims 21-29, wherein the processing circuitry (68) is further configured to cause the network node (16) to: receive information about a capability to support at least one GNSS assistance data resolution from the WD (22).

31. A wireless device, WD (22), configured to communicate with a network node (16), the WD (22) comprising processing circuitry (84), the processing circuitry (84) configured to cause the WD (22) to: obtain Global Navigation Satellite System, GNSS, assistance data and an assistance data resolution indication; and determine an assistance data resolution associated with the GNSS assistance data based on the obtained assistance data resolution indication.

32. The WD (22) of Claim 31, wherein the processing circuitry (84) is further configured to cause the WD (22) to: send a request message for the GNSS assistance data to the network node (16).

33. The WD (22) of Claim 32, wherein the processing circuitry (84) is further configured to cause the WD (22) to: use the GNSS assistance data and the determined assistance data resolution for positioning.

34. The WD (22) of any one of Claims 31-33, wherein the assistance data resolution indication indicates that the GNSS assistance data is one of a standard resolution and a high resolution.

35. The WD (22) of Claim 34, wherein: when the assistance data resolution indication indicates the standard resolution, the GNSS assistance data corresponds to a first type of Radio Technical Commission for Maritime, RTCM, Multiple Signal Message, MSM; and when the assistance data resolution indication indicates the high resolution, the GNSS assistance data corresponds to a second type of RTCM MSM.

36. The WD (22) of Claim 34, wherein the assistance data resolution indication indicates an amount of accuracy associated with a positioning estimate that is based on the GNSS assistance data.

37. The WD (22) of any one of Claims 31-36, wherein the assistance data resolution indication is comprised in a Global Navigation Satellite System, GNSS, Real Time Kinematics, RTK, information element, IE.

38. The WD (22) of Claim 37, wherein a presence of the assistance data resolution indication in the GNSS RTK IE indicates that the GNSS assistance data is a standard resolution and an absence of the assistance data resolution indication in the GNSS RTK IE indicates that the GNSS assistance data is a high resolution.

39. The WD (22) of Claim 37, wherein a presence of the assistance data resolution indication in the GNSS RTK IE indicates that the GNSS assistance data is a high resolution and an absence of the assistance data resolution indication in the GNSS RTK IE indicates that the GNSS assistance data is a standard resolution.

40. The WD (22) of any one of Claims 31-39, wherein the processing circuitry (84) is further configured to cause the WD (22) to: send information about a capability to support at least one GNSS assistance data resolution to the network node (16).