Method for indicating reference station gnss rtk integer ambiguity level

Abstract

According to one aspect of the disclosure, a location node configured to communicate with a wireless device is provided. The location node includes processing circuitry configured to: receive spatial information; determine a wireless device relationship between a first reference station and a second reference station based at least in part on the spatial information; compare a first integer ambiguity level of the first reference station to a second integer ambiguity level of the second reference station, the second reference station corresponding to a current reference station of the wireless device; and transmit an indication of suitability of the second integer ambiguity level of the second reference station to the first integer ambiguity level of the first reference station for position estimation, the indication based on the comparison of the first integer ambiguity level to the second integer ambiguity level.

Description

Technical Field

[0001] The present disclosure relates to wireless communications and, in particular, to indication of reference station Global Navigation Satellite System (GNSS) Real-Time Kinematic (RTK) integer ambiguity levels. Background Art

[0002] Figure 1 The architecture in [1] generally supports positioning in wireless communication systems based on the 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) standard, with direct interaction between wireless devices (WDs) and the Evolved Serving Mobile Location Center (E-SMLC) server via the LTE Positioning Protocol (LPP). In addition, there is interaction between the location server and the base station (eNodeB) via LPP, which is supported, to some extent, by interaction between the eNodeB and the WD via the Radio Resource Control (RRC) protocol.

[0003] As described in the 3rd Generation Partnership Project (3GPP) Technical Standard (TS) 36.305 V15.4.0, the following positioning technologies are considered in LTE:

[0004] Enhanced Cell ID. Essentially, the Cell ID information is used to associate the WD with the service area of ​​the serving cell, and then the additional information is used to determine a finer granularity location.

[0005] Assisted GNSS: GNSS information retrieved by the WD, supported by assistance information provided to the WD from the E-SMLC.

[0006] OTDOA (Observed Time Difference of Arrival): The WD estimates the time difference of reference signals from different base stations and sends it to the E-SMLC for multilateration.

[0007] UTDOA (Uplink TDOA). Requests the WD to send a specific waveform detected by multiple location measurement units (e.g., eNBs) at known locations. These measurements are forwarded to the E-SMLC for multilateration.

[0008] In 3GPP LTE Release 15 (Rel. 15) positioning, one goal is to provide support for Real-Time Kinematic (RTK) GNSS positioning. Support for WD-based and WD-assisted GNSS RTK positioning is also discussed.

[0009] A network of reference stations (at a server, such as an NRTK (Network RTK) server) collects all observations and can interpolate to generate calculated observations at non-physical reference station locations. The served WD obtains observations from one or more physical or non-physical reference stations. Figure 2An example of a reference station network is shown. The reference stations can provide positioning information and integer ambiguity information to wireless devices and / or network nodes.

[0010] Figure 3 The figure shows a comparison of carrier phase and code measurements of satellite signals. It can be seen that the carrier frequency is difficult to count because it is extremely uniform. Each cycle looks identical. On the other hand, the pseudorandom code is intentionally complex to make it easier to distinguish. The receiver's carrier phase measurement is very accurate, but the integer number of wavelengths to the satellite is unknown. However, the WD can determine this integer based on the assistance data with the observations.

[0011] The WD then obtains observations associated with one or more reference stations, and uses these observations to determine satellite time and receiver position.

[0012] Navpedia provides the following general description of phase measurements, integer ambiguities N, and error contributions:

[0013] φ=ρ-I+Tr+c(b Rx -b Sat )+Nλ+ε φ (1)

[0014] in:

[0015] I is the signal path delay caused by the ionosphere;

[0016] Tr is the signal path delay caused by the troposphere;

[0017] b Rx is the offset of the receiver clock from the reference (GPS) time;

[0018] b Sat is the offset of the satellite clock from the reference (GPS) time;

[0019] c is the vacuum speed of light;

[0020] λ is the nominal wavelength of the carrier;

[0021] N is the carrier phase ambiguity (integer);

[0022] ε φ is the measurement noise component, including multipath and other effects;

[0023] ρ is the geometric range between the satellite and the receiver, which is the satellite (x Sat ,y Sat , z Sat ) and receiver (x Rx ,y Rx , z Rx) coordinates is calculated as:

[0024]

[0025] The receiver then forms the double difference equation. For two receivers a and b measuring satellites 1 and 2 simultaneously at the same nominal time, the observed double difference is:

[0026]

[0027] in:

[0028]

[0029] In practice, the superscripts 1 and 2 represent two different satellites, a is the WD, and b is the reference station. Using this double difference, several error terms are canceled out, and the WD can be calculated to the unknown integer This is tedious and requires some initialization time. When the WD moves into the service area, the current reference station becomes distant and a new reference station may become more attractive. The WD then needs to reinitialize the integer ambiguity solution with the new reference station instead.

[0030] Initialization when changing reference stations is time-consuming and can result in poor accuracy for a period of time. An alternative is to send observations associated with several reference stations to the WD, so that the WD can initialize a new reference station before the current reference station becomes too far away. However, this exponentially increases the signaling cost of the observables. Summary of the Invention

[0031] Some embodiments advantageously provide methods, systems, and apparatus for indicating reference station Global Navigation Satellite System (GNSS) Real-Time Kinematic (RTK) integer ambiguity levels.

[0032] UE-based (WD) GNSS RTK positioning is used, where the WD obtains assistance data from a location server / network node to support positioning in the device. The assistance data is generated based on observations from one or more reference stations, where a reference station is a node with a known location and a known antenna configuration, and the GNSS receiver is capable of measuring signals from one or more satellite systems, where the satellite system includes one or more satellites, each transmitting one or more signals. A similar architecture is applicable to 3GPP New Radio (NR) and other communication networks.

[0033] According to one aspect of the present disclosure, a location node configured to communicate with a wireless device is provided. The location node includes processing circuitry configured to: receive spatial information; determine a wireless device relationship between a first reference station and a second reference station based at least in part on the spatial information; compare a first integer ambiguity level for the first reference station with a second integer ambiguity level for the second reference station, wherein the second reference station corresponds to a current reference station of the wireless device; and transmit an indication of the suitability of the second integer ambiguity level for the second reference station with the first integer ambiguity level for position estimation, the indication being based on the comparison of the first integer ambiguity level with the second integer ambiguity level.

[0034] According to one or more embodiments of this aspect, the indication indicates that the first integer ambiguity level of the first reference station is transferable to the second reference station. According to one or more embodiments of this aspect, the indication indicates that the first integer ambiguity level of the first reference station is not transferable to the second reference station. According to one or more embodiments of this aspect, the spatial information indicates a cell identifier.

[0035] According to one or more embodiments of this aspect, the spatial information indicates that the wireless device is monitoring system information broadcast in a spatial region associated with a cell identifier. According to one or more embodiments of this aspect, the indication to the wireless device indicates that the wireless device is monitoring real-time kinematic (RTK) signaling from a second reference station instead of the first reference station. According to one or more embodiments of this aspect, the first reference station corresponds to a first node having a known first physical location and a first antenna configuration, the first antenna configuration having a first global navigation satellite system receiver for measuring signals from at least one satellite, and wherein the second reference station corresponds to a second node having a known second physical location and a second antenna configuration, the second antenna configuration having a second global navigation satellite system receiver for measuring signals from at least one satellite. According to one or more embodiments of this aspect, the indication is sent to a network node serving the wireless device for broadcasting to the wireless device.

[0036] According to another aspect of the present disclosure, a wireless device configured to communicate with a location node is provided. The wireless device includes processing circuitry configured to: send spatial information, receive an indication of applicability of a first integer ambiguity level for a first reference station and a second integer ambiguity level for a second reference station, wherein the indication is based at least in part on the spatial information; and estimate a location of the wireless device based at least in part on the indication.

[0037] According to one or more embodiments of this aspect, the indication indicates that the first integer ambiguity level of the first reference station is transferable to the second reference station. According to one or more embodiments of this aspect, the indication indicates that the first integer ambiguity level of the first reference station is not transferable to the second reference station. According to one or more embodiments of this aspect, the spatial information indicates a cell identifier.

[0038] According to one or more embodiments of this aspect, the spatial information indicates that the wireless device is monitoring system information broadcast in a spatial region associated with the cell identifier. According to one or more embodiments of this aspect, the first reference station corresponds to a first node having a known first physical location and a first antenna configuration, the first antenna configuration having a first global navigation satellite system receiver for measuring signals from at least one satellite, and wherein the second reference station corresponds to a second node having a known second physical location and a second antenna configuration, the second antenna configuration having a second global navigation satellite system receiver for measuring signals from at least one satellite. According to one or more embodiments of this aspect, the processing circuit is further configured to determine a carrier phase of the second reference station, the estimate of the position being based at least in part on the determined carrier phase of the second reference station.

[0039] According to one or more embodiments of this aspect, the wireless device is reassigned from a first reference station to a second reference station. According to one or more embodiments of this aspect, the indication indicates that the wireless device monitors real-time kinematic (RTK) signaling from the second reference station instead of the first reference station. According to one or more embodiments of this aspect, the indication is received in a broadcast from a network node serving the wireless device.

[0040] According to another aspect of the present disclosure, a method for a location node configured to communicate with a wireless device is provided. Spatial information is received. A wireless device relationship between a first reference station and a second reference station is determined based at least in part on the spatial information. A first integer ambiguity level for the first reference station is compared with a second integer ambiguity level for the second reference station, where the second reference station corresponds to a current reference station of the wireless device. An indication of the suitability of the first integer ambiguity level for the first reference station and the second integer ambiguity level for the second reference station for use in position estimation is transmitted. The indication is based on the comparison of the first integer ambiguity level with the second integer ambiguity level.

[0041] According to one or more embodiments of this aspect, the indication indicates that the first integer ambiguity level of the first reference station is transferable to the second reference station. According to one or more embodiments of this aspect, the indication indicates that the first integer ambiguity level of the first reference station is not transferable to the second reference station. According to one or more embodiments of this aspect, the spatial information indicates a cell identifier.

[0042] According to one or more embodiments of this aspect, the spatial information indicates that the wireless device is monitoring system information broadcast in a spatial region associated with a cell identifier. According to one or more embodiments of this aspect, the indication to the wireless device indicates that the wireless device is monitoring real-time kinematic (RTK) signaling from a second reference station instead of the first reference station. According to one or more embodiments of this aspect, the first reference station corresponds to a first node having a known first physical location and a first antenna configuration, the first antenna configuration having a first global navigation satellite system receiver for measuring signals from at least one satellite, and wherein the second reference station corresponds to a second node having a known second physical location and a second antenna configuration, the second antenna configuration having a second global navigation satellite system receiver for measuring signals from at least one satellite. According to one or more embodiments of this aspect, the indication is sent to a network node serving the wireless device for broadcasting to the wireless device.

[0043] According to another aspect of the present disclosure, a method is provided for a wireless device configured to communicate with a location node. Spatial information is transmitted. An indication of applicability of a first integer ambiguity level for a first reference station and a second integer ambiguity level for a second reference station is received, wherein the indication is based at least in part on the spatial information. A location of the wireless device is estimated based at least in part on the indication.

[0044] According to one or more embodiments of this aspect, the indication indicates that the first integer ambiguity level of the first reference station is transferable to the second reference station. According to one or more embodiments of this aspect, the indication indicates that the first integer ambiguity level of the first reference station is not transferable to the second reference station. According to one or more embodiments of this aspect, the spatial information indicates a cell identifier.

[0045] According to one or more embodiments of this aspect, the spatial information indicates that the wireless device is monitoring system information broadcast in a spatial region associated with the cell identifier. According to one or more embodiments of this aspect, the first reference station corresponds to a first node having a known first physical location and a first antenna configuration, the first antenna configuration having a first global navigation satellite system receiver for measuring signals from at least one satellite, and wherein the second reference station corresponds to a second node having a known second physical location and a second antenna configuration, the second antenna configuration having a second global navigation satellite system receiver for measuring signals from at least one satellite. According to one or more embodiments of this aspect, a carrier phase of the second reference station is determined, wherein the estimate of position is based at least in part on the determined carrier phase of the second reference station.

[0046] According to one or more embodiments of this aspect, the wireless device is reassigned from a first reference station to a second reference station. According to one or more embodiments of this aspect, the indication indicates that the wireless device monitors real-time kinematic (RTK) signaling from the second reference station instead of the first reference station. According to one or more embodiments of this aspect, the indication is received in a broadcast from a network node serving the wireless device. BRIEF DESCRIPTION OF THE DRAWINGS

[0047] A more complete understanding of the present embodiments and its attendant advantages and features will be more readily appreciated by reference to the following detailed description when considered in conjunction with the accompanying drawings, in which:

[0048] Figure 1 An example LTE architecture is shown;

[0049] Figure 2 An example of a reference station network is shown;

[0050] Figure 3 The carrier and code are shown;

[0051] Figure 4 is a schematic diagram illustrating an exemplary network architecture of a communication system connected to a host computer via an intermediate network according to the principles of the present disclosure;

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

[0053] Figure 6 is a flow chart illustrating an exemplary method for executing a client application at a wireless device implemented in a communication system including a host computer, a network node, and a wireless device according to some embodiments of the present disclosure;

[0054] Figure 7 is a flow chart illustrating an exemplary method for receiving user data at a wireless device implemented in a communication system including a host computer, a network node, and a wireless device according to some embodiments of the present disclosure;

[0055] Figure 8 is a flow chart illustrating an exemplary method implemented in a communication system including a host computer, a network node, and a wireless device for receiving user data at a host computer from a wireless device according to some embodiments of the present disclosure;

[0056] Figure 9 is a flow chart illustrating an exemplary method for receiving user data at a host computer implemented in a communication system including a host computer, a network node, and a wireless device according to some embodiments of the present disclosure;

[0057] Figure 10 is a flow chart of an example process in a network node according to the principles of the present disclosure;

[0058] Figure 11 is a flow chart of another example process in a network node according to the principles of the present disclosure;

[0059] Figure 12 is a flow chart of an example process in a wireless device according to the principles of the present disclosure;

[0060] Figure 13 is a flow chart of another example process in a wireless device according to the principles of the present disclosure;

[0061] Figure 14 is a flow chart of an exemplary process for obtaining integer ambiguity information in WD;

[0062] Figure 15 is a flow chart of an exemplary process for resolving integer ambiguities in a network node;

[0063] Figure 16 shows signaling between a network node and a UE; and

[0064] Figure 17 is a flow chart of an exemplary process for resolving integer ambiguities in a network node. DETAILED DESCRIPTION

[0065] Before describing the exemplary embodiments in detail, it should be noted that the embodiments reside primarily in a combination of apparatus components and processing steps related to indicating integer ambiguity levels for a reference station Global Navigation Satellite System (GNSS) Real-Time Kinematics (RTK). Accordingly, components are appropriately represented in the drawings by conventional symbols, with only those specific details relevant to understanding the embodiments being shown so as not to obscure the disclosure with details that would be apparent to one of ordinary skill in the art having the benefit of the description herein. Like reference numerals refer to like elements throughout the specification.

[0066] As used herein, relational terms (such as "first" and "second", "top" and "bottom", etc.) may be used solely to distinguish one entity or element from another entity or element, and do not necessarily require or imply any physical or logical relationship or order between these entities or elements. The terms used herein are for the purpose of describing specific embodiments only and are not intended to limit the concepts described herein. As used herein, the singular forms "a", "an", and "said" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the terms "comprises", "having", "including", and / or "containing" when used herein indicate the presence of the 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 combinations thereof.

[0067] In the embodiments described herein, connection terms such as "in communication with..." may be used to indicate electrical or data communication, which may be achieved, for example, through physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling, or optical signaling. Those skilled in the art will appreciate that various components may interoperate and that modifications and variations in achieving electrical and data communication are possible.

[0068] In some embodiments described herein, the terms "coupled," "connected," and the like may be used herein to indicate connection, although not necessarily direct, and may include wired and / or wireless connections.

[0069] The term "network node" as used herein may be any type of network node included in a radio network, and may also include any of the following: base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), gNodeB (gNB), evolved NodeB (eNB or eNodeB), NodeB, multi-standard radio (MSR) radio node (e.g., MSR BS), multi-cell / multicast coordination entity (MCE), integrated access and backhaul (IAB) node, relay node, donor node controlled relay, radio access point (AP), transmission point, transmission node, remote radio unit (RRU) remote radio head (RRH), core network node (e.g., mobility management entity (MME), self-organizing network (SON) node, coordination node, location node, MDT node, etc.), external node (e.g., third-party node, node outside the current network), node in a distributed antenna system (DAS), spectrum access system (SAS) node, element management system (EMS), etc. Network nodes may also include test equipment. As used herein, the term "radio node" may also be used to denote a wireless device (WD) or a radio network node.

[0070] In some embodiments, the non-limiting terms wireless device (WD) or user equipment (UE) are used interchangeably. A WD herein may be any type of wireless device capable of communicating with a network node or another WD via radio signals. A WD may also be a radio communication device, a target device, a device-to-device (D2D) WD, a machine-type WD, or a WD capable of machine-to-machine communication (M2M), a low-cost and / or low-complexity WD, a sensor equipped with a WD, a tablet computer, a mobile terminal, a smartphone, a laptop embedded device (LEE), a laptop mounted device (LME), a USB adapter, a customer premises equipment (CPE), an Internet of Things (IoT) device, or a narrowband IoT (NB-IOT) device, etc.

[0071] In addition, in some embodiments, the general term "radio network node" is used. It can be any type of radio network node, including any of the following: base station, radio base station, base transceiver site, 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).

[0072] Note that although terminology from one particular wireless system (e.g., 3GPP LTE and / or New Radio (NR)) may be used in this disclosure, this should not be considered to limit the scope of this disclosure to only the aforementioned systems. Other wireless systems (including but not limited to Wideband 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 utilizing the concepts encompassed by this disclosure.

[0073] It should also be noted that the functions described herein as being performed by a wireless device or network node may be distributed across multiple wireless devices and / or network nodes. In other words, it is contemplated that the functions of the network nodes and wireless devices described herein are not limited to being performed by a single physical device and may, in fact, be distributed across multiple physical devices. As used herein, "ambiguity level" may include the level of uncertainty in determining the number of cycles of a carrier wave from a reference station to a WD.

[0074] 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 should also be understood that the terms used herein should be interpreted as having a meaning consistent with their meaning in the context of this specification and the relevant art, and should not be interpreted as an ideal or overly superficial meaning, unless otherwise explicitly defined herein.

[0075] A method, system, and apparatus for indicating integer ambiguity levels for Global Navigation Satellite System (GNSS) Real-Time Kinematic (RTK) reference stations is disclosed. According to one aspect, a network node is configured to receive spatial information from a wireless device (WD). The network node is further configured to determine, based at least in part on the spatial information, whether the WD is to be configured to obtain RTK data from a subsequent reference station that is different from a current reference station providing RTK data to the WD. The network node is further configured to analyze the integer ambiguity levels of the subsequent reference station and the current reference station and to send an indication indicating whether the WD is to use the same integer ambiguity level for the subsequent reference station as the integer ambiguity level for the current reference station.

[0076] Referring again to the drawings, wherein like elements are referred to by like reference numerals, Figure 4 A schematic diagram of a communication system 10 according to an embodiment is shown, which may, for example, support a standard 3GPP-type cellular network such as LTE and / or NR (5G), and includes an access network 12, such as a radio access network, and a core network 14. Access network 12 includes a plurality of network nodes 16a, 16b, 16c (collectively, network nodes 16) (e.g., NBs, eNBs, gNBs, or other types of wireless access points), and at least one location node 17 (collectively, location node 17). Each of the plurality of network nodes 16 defines a corresponding coverage area 18a, 18b, 18c (collectively, coverage area 18). Each network node 16a, 16b, 16c may be connected to core network 14 via 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 may be wirelessly connected to the corresponding network node 16b. Although multiple WDs 22a, 22b (collectively referred to as wireless devices 22) are shown in this example, the disclosed embodiments are equally applicable to situations where only a single WD is located in the coverage area or a single WD is connected to a 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 more WDs 22 and network nodes 16. In addition to the WDs 22 and network nodes 16, at least one reference station 36 is in communication with the WDs 22 and network nodes 16. The reference station 36 may be configured to provide positioning information and information for determining integer ambiguity levels.

[0077] In some embodiments, the location node 17 may be configured to communicate with the WD 22 and / or the network node 16 via one or more positioning protocols (e.g., LPPaTS 36.455 V15.2.1 and LPP TS 36.355 V15.4.0), such as Figure 1In one or more embodiments, the location node 17 is a positioning server or an E-SMLC.

[0078] Additionally, it is contemplated that the WD 22 may communicate concurrently and / or be configured to communicate with more than one network node 16 and more than one type of network node 16, respectively. For example, the WD 22 may have dual connectivity with a network node 16 that supports LTE and the same or different network nodes 16 that support NR. As an example, the WD 22 may communicate with an eNB for LTE / E-UTRAN and a gNB for NR / NG-RAN.

[0079] The communication system 10 itself can be connected to a host computer 24, which can be implemented as hardware and / or software of a stand-alone server, a cloud-implemented server, a distributed server, or as a processing resource in a server cluster. The host computer 24 can be owned or under the control of a service provider, or can be operated by or on behalf of a service provider. The connections 26, 28 between the communication system 10 and the host computer 24 can extend directly from the core network 14 to the host computer 24, or can extend via an optional intermediate network 30. The intermediate network 30 can be a public network, a private network, or a combination of more than one of a servo network. The intermediate network 30, if any, can be a backbone network or the Internet. In some embodiments, the intermediate network 30 can include two or more subnetworks (not shown).

[0080] Figure 4 The communication system as a whole implements a connection between one of the connected WDs 22a, 22b and the host computer 24. This connection can be described as an over-the-top (OTT) connection. The host computer 24 and the connected WDs 22a, 22b are configured to use the access network 12, the core network 14, any intermediate networks 30, and possibly other intermediate infrastructure (not shown) as intermediaries to transmit data and / or signaling via the OTT connection. The OTT connection can be transparent in the sense that at least some of the participating communication devices through which the OTT connection passes are unaware of the routing of uplink and downlink communications. For example, the network node 16 may not be informed or may not need to be informed of the past routing of incoming downlink communications with data originating from the host computer 24 to be forwarded (e.g., handed over) to the connected WD 22a. Similarly, the network node 16 does not need to be aware of the future routing of outgoing uplink communications originating from the WD 22a to the host computer 24.

[0081] The location node 17 is configured to include an ambiguity indication unit 32 configured to determine, based at least in part on the spatial information, whether the WD is to be configured to obtain real-time kinematic (RTK) data from a subsequent reference station that is different from the current reference station providing RTK data to the WD. The wireless device 22 is configured to include an ambiguity level selector 34 configured to select an integer ambiguity level based on the indication.

[0082] Now refer to Figure 5 to describe an example implementation of the WD 22, network node 16, location server 17, and host computer 24 discussed in the previous paragraphs according to an embodiment. In the communication system 10, the host computer 24 includes hardware (HW) 38, which includes a communication interface 40 that is configured to establish and maintain a wired or wireless connection to an interface with different communication devices of the communication system 10. The host computer 24 also includes processing circuitry 42, which may have storage and / or processing capabilities. The processing circuitry 42 may include a processor 44 and a memory 46. In particular, as a supplement or alternative to a processor (e.g., a central processing unit) and a memory, the processing circuitry 42 may include an integrated circuit for processing and / or control, such as one or more processors and / or processor cores and / or an FPGA (field programmable gate array) and / or an ASIC (application-specific integrated circuit) suitable for executing instructions. The processor 44 may be configured to access (e.g., write to or read from) a memory 46, which may include any type of volatile and / or non-volatile memory, such as 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).

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

[0084] The software 48 can be executed by the processing circuit 42. The software 48 includes a host application 50. The host application 50 is operable to provide services to a remote user (e.g., WD 22), which is connected via an OTT connection 52 terminated at the WD 22 and the host computer 24. When providing services to the remote user, the host application 50 can provide user data sent using the OTT connection 52. "User data" can be data and information described herein as implementing the described functions. In one embodiment, the host computer 24 can be configured to provide control and functionality to a service provider and can be operated by or on behalf of the service provider. The processing circuit 42 of the host computer 24 can enable the host computer 24 to observe, monitor, control, send to, and / or receive from the network node 16 and / or wireless device 22.

[0085] The communication system 10 also includes a network node 16 disposed within the communication system 10, which includes hardware 58 that enables it to communicate with the host computer 24 and the WD 22. The hardware 58 may include a communication interface 60 for establishing and maintaining wired or wireless connections with various communication devices of the communication system 10, and a radio interface 62 for establishing and maintaining at least a wireless connection 64 with the WD 22 located within the coverage area 18 served by the network node. 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 the core network 14 of the communication system 10 and / or one or more intermediate networks 30 external to the communication system 10.

[0086] In the illustrated embodiment, the hardware 58 of the network node 16 also includes processing circuitry 68. The processing circuitry 68 may include a processor 70 and a memory 72. In particular, in addition to or in lieu of a processor (e.g., a central processing unit) and memory, the processing circuitry 68 may include an integrated circuit for processing and / or control, such as one or more processors and / or processor cores and / or an FPGA (field programmable gate array) and / or an ASIC (application-specific integrated circuit) adapted to execute instructions. The processor 70 may be configured to access (e.g., write to or read from) the memory 72, which may include any type of volatile and / or non-volatile memory, such as a 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).

[0087] Thus, network node 16 also has software 74, which is stored internally, for example, in memory 72 or in external memory (e.g., a database, storage array, network storage device, etc.) accessible by network node 16 via an external connection. Software 74 can be executed by processing circuitry 68. Processing circuitry 68 can be configured to control any of the methods and / or processes described herein and / or cause such methods and / or processes to be performed, for example, by network node 16. Processor 70 corresponds to one or more processors 70 for performing the network node 16 functions described herein. Memory 72 is configured to store data, program software code, and / or other information described herein. In some embodiments, software 74 may include instructions that, when executed by processor 70 and / or processing circuitry 68, cause processor 70 and / or processing circuitry 68 to perform the processes described herein for network node 16.

[0088] The communication system 10 also includes the already mentioned WD 22. The WD 22 may have hardware 80 that may include a radio interface 82 configured to establish and maintain a wireless connection 64 with a network node 16 serving the 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.

[0089] The hardware 80 of the WD 22 also includes a processing circuit 84. The processing circuit 84 may include a processor 86 and a memory 88. In particular, in addition to or in lieu of a processor (e.g., a central processing unit) and a memory, the processing circuit 84 may include an integrated circuit for processing and / or control, such as one or more processors and / or processor cores and / or an FPGA (field programmable gate array) and / or an ASIC (application-specific integrated circuit) suitable for executing instructions. The processor 86 may be configured to access (e.g., write to or read from) the memory 88, which may include any type of volatile and / or non-volatile memory, such as a 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).

[0090] Therefore, WD 22 also includes software 90, which is stored in, for example, memory 88 at WD 22, or in an external memory accessible by WD 22 (e.g., a database, storage array, network storage device, etc.). The software 90 can be executed by the processing circuit 84. The software 90 can include a client application 92. The client application 92 is operable to provide services to human or non-human users via WD 22 with the support of the host computer 24. In the host computer 24, the executed host application 50 can communicate with the executing client application 92 via the OTT connection 52 terminated at WD 22 and the host computer 24. When providing services to the user, the client application 92 can receive request data from the host application 50 and provide user data in response to the request data. The OTT connection 52 can transmit both the request data and the user data. The client application 92 can interact with the user to generate the user data it provides.

[0091] The processing circuitry 84 may be configured to control any of the methods and / or processes described herein and / or cause such methods and / or processes to be performed, for example, by the WD 22. The processor 86 corresponds to one or more processors 86 for performing the functions of the WD 22 described herein. The WD 22 includes a memory 88 configured to store data, program software code, and / or other information described herein. In some embodiments, the software 90 and / or client application 92 may include instructions that, when executed by the processor 86 and / or the processing circuitry 84, cause the processor 86 and / or the processing circuitry 84 to perform the processes described herein for the WD 22. For example, the processing circuitry 84 of the wireless device 22 may include an ambiguity level selector 34 configured to select an integer ambiguity level based on an indication.

[0092] The communication system 10 also includes a location node 17 provided in the communication system 10 and including hardware 94 that enables it to communicate with the WD 22 and / or the network node 16. The hardware 94 may include a communication interface 96 for establishing and maintaining a wired or wireless connection with different communication devices (e.g., the host computer 24) of the communication system 10, and a radio interface 98 for communicating at least the wireless connection 64 with the WD 22 and / or the network node 16. The radio interface 98 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.

[0093] In the illustrated embodiment, the hardware 94 of the location node 17 also includes processing circuitry 100. The processing circuitry 100 may include a processor 102 and a memory 104. In particular, in addition to or in lieu of a processor (e.g., a central processing unit) and memory, the processing circuitry 100 may include an integrated circuit for processing and / or control, such as one or more processors and / or processor cores and / or an FPGA (field programmable gate array) and / or an ASIC (application-specific integrated circuit) adapted to execute instructions. The processor 102 may be configured to access (e.g., write to or read from) the memory 104, which may include any type of volatile and / or non-volatile memory, such as a 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).

[0094] Thus, location node 17 also has software 106, which is stored internally, for example, in memory 104 or in an external memory (e.g., a database, storage array, network storage device, etc.) accessible by location node 17 via an external connection. Software 106 can be executed by processing circuit 100. Processing circuit 100 can be configured to control any of the methods and / or processes described herein and / or cause such methods and / or processes to be performed, for example, by location node 17. Processor 102 corresponds to one or more processors 102 for performing the location node 17 functions described herein. Memory 104 is configured to store data, program software code, and / or other information described herein. In some embodiments, software 106 may include instructions that, when executed by processor 102 and / or processing circuit 100, cause processor 102 and / or processing circuit 100 to perform the processes described herein for location node 17. For example, the processing circuitry 100 of the location node 17 may include an ambiguity indication unit 32 configured to determine, based at least in part on the spatial information, whether the WD 22 is to be configured to obtain real-time kinematic (RTK) data from a subsequent reference station that is different from the current reference station 36 providing RTK data to the WD.

[0095] Reference stations 36 are in communication with WD 22 and network nodes 16. Reference stations 36 may provide positioning information and information used to determine integer ambiguity levels.

[0096] In some embodiments, the internal operations of the network node 16, location node 17, WD 22, and host computer 24 may be as follows: Figure 2 shown, and independently, the surrounding network topology can be Figure 4 network topology.

[0097] exist Figure 5, an OTT connection 52 has been abstractly depicted to illustrate communication between a host computer 24 and a wireless device 22 via a network node 16, without explicitly involving any intermediate devices and the precise routing of messages through these devices. The network infrastructure can determine the routing, which can be configured to be hidden 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 can also make decisions to dynamically change the routing (e.g., based on load balancing considerations or network reconfiguration).

[0098] 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 improves the performance of OTT services provided to the WD 22 using the OTT connection 52, wherein the wireless connection 64 may form the last leg in the OTT connection 52. More specifically, the teachings of some of these embodiments may improve data rates, latency, and / or power consumption, thereby providing benefits such as reduced user wait time, relaxed file size limits, better responsiveness, and extended battery life.

[0099] In some embodiments, a measurement process may be provided for the purpose of monitoring data rates, latency, and other factors improved by one or more embodiments. Optional network functionality may also be present for reconfiguring the OTT connection 52 between the host computer 24 and the WD 22 in response to changes in measurement results. The measurement process and / or network functionality for reconfiguring the OTT connection 52 may be implemented in the software 48 of the host computer 24, in the software 90 of the WD 22, or in both. In embodiments, sensors (not shown) may be deployed in or associated with the communication devices through which the OTT connection 52 passes. The sensors may participate in the measurement process by providing values ​​for the monitored quantities exemplified above or other physical quantities that the software 48, 90 may use to calculate or estimate the monitored quantities. Reconfiguration of the OTT connection 52 may include message formats, retransmission settings, preferred routing, and the like. This reconfiguration need not affect the network node 16 and may be unknown or imperceptible to the network node 16. Some of these processes and functionality may be known and practiced in the art. In certain embodiments, the measurements may involve proprietary WD signaling that facilitates the host computer 24's measurement of throughput, propagation time, latency, etc. In some embodiments, the measurements may be implemented as follows: the software 48, 90 enables the sending of messages (specifically, empty or "dummy" messages) using the OTT connection 52 while it monitors propagation time, errors, etc.

[0100] Thus, in some embodiments, host computer 24 includes processing circuitry 42 configured to provide user data and communication interface 40 configured to forward the user data to a cellular network for transmission to WD 22. In some embodiments, cellular network also includes a network node 16 having a radio interface 62. In some embodiments, network node 16 is configured and / or processing circuitry 68 of network node 16 is configured to perform the functions and / or methods described herein to prepare / initiate / maintain / support / end a transmission to WD 22 and / or to prepare / terminate / maintain / support / end receipt of a transmission from WD 22.

[0101] In some embodiments, host computer 24 includes processing circuitry 42 and communication interface 40 configured to receive user data originating from a transmission from WD 22 to network node 16. In some embodiments, WD 22 is configured to and / or includes a radio interface 82 and / or processing circuitry 84 configured to perform the functions and / or methods described herein to prepare / initiate / maintain / support / terminate transmissions to network node 16 and / or to prepare / terminate / maintain / support / terminate receipt of transmissions from network node 16.

[0102] although Figure 4 and Figure 5 Various "units," such as the ambiguity indication unit 32 and the ambiguity level selector 34, are shown as being within respective processors, but it is contemplated that these units may be implemented such that portions of the units are stored in corresponding memories within the processing circuitry. In other words, these units may be implemented within the processing circuitry in hardware or in a combination of hardware and software.

[0103] Figure 6 FIG. 1 is a diagram illustrating a communication system (eg, Figure 4 and Figure 5 The communication system may include a host computer 24, a network node 16 and a WD 22, which may be a reference Figure 51 and 2. The method further includes a host computer 24, a network node 16, and a WD 22 as described above. In a first step of the method, the host computer 24 provides user data (block S100). In an optional substep of the first step, the host computer 24 provides the user data by executing a host application (e.g., host application 50) (block S102). In a second step, the host computer 24 initiates a transmission carrying the user data to the WD 22 (block S104). In an optional third step, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 16 sends the user data carried in the transmission initiated by the host computer 24 to the WD 22 (block S106). In an optional fourth step, the WD 22 executes a client application, e.g., client application 92, associated with the host application 50 executed by the host computer 24 (block S108).

[0104] Figure 7 FIG. 1 is a diagram illustrating a communication system (eg, Figure 4 The communication system may include a host computer 24, a network node 16 and a WD 22, which may be a reference Figure 4 and Figure 5 1 . In the first step of the method, the host computer 24 provides user data (block S110). In an optional sub-step (not shown), the host computer 24 provides the user data by executing a host application (e.g., host application 50). In a second step, the host computer 24 initiates a transmission carrying the user data to the WD 22 (block S112). In accordance with the teachings of the embodiments described throughout this disclosure, the transmission may be via the network node 16. In an optional third step, the WD 22 receives the user data carried in the transmission (block S114).

[0105] Figure 8 FIG. 1 is a diagram illustrating a communication system (eg, Figure 4 The communication system may include a host computer 24, a network node 16 and a WD 22, which may be a reference Figure 4 and Figure 5The method further includes the host computers 24, network nodes 16, and WDs 22 described above. In an optional first step of the method, WD 22 receives input data provided by host computer 24 (block S116). In an optional sub-step of the first step, WD 22 executes client application 92, which provides user data in response to the received input data provided by host computer 24 (block S118). Additionally or alternatively, in an optional second step, WD 22 provides user data (block S120). In an optional sub-step of the second step, WD 22 provides user data by executing a client application (e.g., client application 92) (block S122). When providing user data, the executed client application 92 may also consider user input received from the user. Regardless of the specific manner in which the user data is provided, WD 22 initiates transmission of the user data to host computer 24 in an optional third sub-step (block S124). In a fourth step of the method, in accordance with the teachings of the embodiments described throughout this disclosure, host computer 24 receives user data sent from WD 22 (block S126).

[0106] Figure 9 FIG. 1 is a diagram illustrating a communication system (eg, Figure 4 The communication system may include a host computer 24, a network node 16 and a WD 22, which may be a reference Figure 4 and Figure 5 1 and 2. The method further includes host computer 24, network node 16, and WD 22 as described above. In an optional first step of the method, network node 16 receives user data from WD 22 in accordance with the teachings of the embodiments described throughout this disclosure (block S128). In an optional second step, network node 16 initiates a transmission of the received user data to host computer 24 (block S130). In a third step, host computer 24 receives the user data carried in the transmission initiated by network node 16 (block S132).

[0107] Figure 101 is a flow chart of an example process for resolving potential integer ambiguities in a location node 17. One or more blocks described herein may be performed by one or more elements of the location node 17, such as one or more of the processing circuitry 100 (including the ambiguity indication unit 32), the processor 102, the radio interface 98, and / or the communication interface 96. The location node 17 is configured, for example, via the processing circuitry 100 and / or the processor 102 and / or the radio interface 98 and / or the communication interface 96, to receive spatial information from the WD 22 (block S134). The process also includes determining, based at least in part on the spatial information, whether the WD 22 will be configured to obtain real-time kinematic (RTK) data from a subsequent reference station 36 that is different from the current reference station 36 providing RTK data to the WD 22 (block S136). The process also includes analyzing the integer ambiguity levels of the subsequent reference station 36 and the current reference station 36 (block S138). The process also includes sending an indication whether the WD 22 is to use the same integer ambiguity level for the subsequent reference station 36 as the integer ambiguity level for the current reference station 36 (block S140).

[0108] Figure 11 1 is a flow chart of an example process for resolving potential integer ambiguities in location node 17. One or more blocks described herein may be performed by one or more elements of location node 17, such as by one or more of processing circuitry 100 (including ambiguity indication unit 32), processor 102, radio interface 98, and / or communication interface 96. As described herein, location node 17 is configured, for example, via processing circuitry 100 and / or processor 102 and / or radio interface 98 and / or communication interface 96, to receive (block S142) spatial information. As described herein, location node 17 is configured, for example, via processing circuitry 100 and / or processor 102 and / or radio interface 98 and / or communication interface 96, to determine (block S144) a wireless device 22 relationship between a first reference station 36 and a second reference station 36 based, at least in part, on the spatial information.

[0109] As described herein, the location node 17 is configured, such as via the processing circuitry 100 and / or the processor 102 and / or the radio interface 98 and / or the communication interface 96, to compare (block S146) the first integer ambiguity level of the first reference station 36 with the second integer ambiguity level of the second reference station 36, where the second reference station 36 corresponds to the current reference station 36 of the wireless device 22. As described herein, the location node 17 is configured, such as via the processing circuitry 100 and / or the processor 102 and / or the radio interface 98 and / or the communication interface 96, to send (block S148) an indication of the suitability of the first integer ambiguity level of the first reference station 36 and the second integer ambiguity level of the second reference station 36 for position estimation, where the indication is based on the comparison of the first integer ambiguity level with the second integer ambiguity level.

[0110] According to one or more embodiments, the indication indicates that the first integer ambiguity level of the first reference station 36 is transferable to the second reference station 36. According to one or more embodiments, the indication indicates that the first integer ambiguity level of the first reference station 36 is not transferable to the second reference station 36. According to one or more embodiments, the spatial information indicates a cell identifier.

[0111] According to one or more embodiments, the spatial information indicates that the wireless device 22 is monitoring system information (SIB) broadcast in a spatial region associated with the cell identifier. According to one or more embodiments, the indication to the wireless device 22 indicates that the wireless device 22 is monitoring real-time kinematic (RTK) signaling from the second reference station 36 instead of the first reference station 36. According to one or more embodiments, the first reference station 36 corresponds to a first node having a known first physical location and a first antenna configuration having a first global navigation satellite system receiver for measuring signals from at least one satellite, and the second reference station 36 corresponds to a second node having a known second physical location and a second antenna configuration having a second global navigation satellite system receiver for measuring signals from at least one satellite. According to one or more embodiments, the indication is sent to the network node 16 serving the wireless device 22 for broadcast to the wireless device 22.

[0112] Figure 12is a flow chart of an exemplary process in a wireless device 22 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of the wireless device 22, such as one or more of the processing circuitry 84 (including the ambiguity level selector 34), the processor 86, the radio interface 82, and / or the communication interface 60. The wireless device 22 is configured, for example, via the processing circuitry 84 and / or the processor 86 and / or the radio interface 82, to send spatial information to the location node 17 (Block S150). The process also includes receiving an integer ambiguity level indication indicating whether the WD 22 is to use the same integer ambiguity level for a subsequent reference station 36 as the integer ambiguity level used by the current reference station 36 (Block S152). The process also includes selecting an integer ambiguity level based on the indication (Block S154).

[0113] Figure 13 is a flow chart of an exemplary process in the wireless device 22 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of the wireless device 22, such as by one or more of the processing circuitry 84 (including the ambiguity level selector 34), the processor 86, the radio interface 82, and / or the communication interface 60. As described herein, the wireless device 22, such as via the processing circuitry 84 and / or the processor 86 and / or the radio interface 82, is configured to send (Block S156) spatial information. As described herein, the wireless device 22, such as via the processing circuitry 84 and / or the processor 86 and / or the radio interface 82, is configured to receive (Block S158) an indication of the suitability of a first integer ambiguity level for a first reference station and a second integer ambiguity level for a second reference station, wherein the indication is based at least in part on the spatial information.

[0114] As described herein, the wireless device 22 is configured, eg, via the processing circuitry 84 and / or the processor 86 and / or the radio interface 82 , to estimate (Block S160 ) the location of the wireless device based at least in part on the indication.

[0115] According to one or more embodiments, the indication indicates that the first integer ambiguity level of the first reference station 36 is transferable to the second reference station 36. According to one or more embodiments, the indication indicates that the first integer ambiguity level of the first reference station 36 is not transferable to the second reference station 36. According to one or more embodiments, the spatial information indicates a cell identifier.

[0116] According to one or more embodiments, the spatial information indicates that the wireless device 22 is monitoring system information broadcast in the spatial region associated with the cell identifier. According to one or more embodiments, the first reference station 36 corresponds to a first node having a known first physical location and a first antenna configuration, the first antenna configuration having a first global navigation satellite system receiver for measuring signals from at least one satellite, and the second reference station corresponds to a second node having a known second physical location and a second antenna configuration, the second antenna configuration having a second global navigation satellite system receiver for measuring signals from at least one satellite. According to one or more embodiments, the processing circuit 84 is further configured to determine a carrier phase of the second reference station, the estimate of the position being based at least in part on the determined carrier phase of the second reference station.

[0117] According to one or more embodiments, the wireless device 22 is reassigned from the first reference station 36 to the second reference station 36. According to one or more embodiments, the indication indicates that the wireless device 22 monitors real-time kinematic (RTK) signaling from the second reference station 36 instead of the first reference station 36. According to one or more embodiments, the indication is received in a broadcast from the network node 16 serving the wireless device 22.

[0118] Having described the general processing flow of the apparatus of the present disclosure, and having provided examples of hardware and software apparatus for implementing the processes and functions of the present disclosure, the following sections provide details and examples of apparatus for indicating integer ambiguity levels for global navigation satellite system (GNSS) real-time kinematic (RTK) of reference station 36.

[0119] Figure 14 The steps of some embodiments are shown from the perspective of a device (UE). WD 22 optionally provides information to location node 17 regarding its ability to support integer ambiguity level indications, for example, via processing circuitry 84 (block S162). WD 22 optionally provides spatial information to location node 17 in a request message (block S164). The spatial information can be logical, such as a cell ID. The request message can also be implicit (e.g., when WD 22 is monitoring GNSS RTK via broadcast and switches from monitoring one cell to monitoring a new cell), where a change in cell implies a change in the monitored system information broadcast.

[0120] If the current cell and the new cell broadcast data from the current reference station 36 and the new reference station 36, respectively, this is considered a change of reference station 36, i.e., the relationship between the first reference station 36 (i.e., the current reference station) and the second reference station 36 (i.e., the new reference station) is determined (block S166). Additionally, the position node 17 may provide an integer ambiguity level indicator indicating whether the new reference station 36 is at the same integer ambiguity level as the old reference station 36. Based on this indicator, the WD 22 may determine whether the integer ambiguity solution associated with the current reference station 36 can be transferred to the integer ambiguity solution associated with the new reference station 36 (block S168). If so, the WD 22 uses the integer ambiguity solution associated with the new reference station 36 along with the carrier phase observations from the new reference station to accurately estimate its position.

[0121] Figure 15 The basic principle for resolving integer ambiguities is shown from the perspective of location node 17. Optionally, location node 17 receives an indication of supported integer ambiguity levels from WD 22 via radio interface 98 (block S170). Location node 17 obtains a request message from WD 22 (block S172), which includes spatial information such as a cell ID. Location node 17 uses the spatial information to determine whether WD 22 should obtain RTK data from a reference station 36 that is different from its current reference station. If reference station 36 is to be changed, location node 17 analyzes the integer ambiguity levels of the current and new reference stations (block S174). Location node 17 sends information about the new reference station 36 to WD 22 (block S176), including an indication of whether the integer ambiguity levels are the same as the old reference station.

[0122] Figure 16 A signaling diagram outlining the above steps is provided. WD 22 optionally provides location node 17 with information about its ability to support integer ambiguity level indications via, for example, processing circuitry 84 (S177). WD optionally provides spatial information to location node 17 in a request message (S178). The spatial information can be logical, such as a cell ID. The request message can also be implicit (e.g., when WD 22 monitors GNSS RTK via broadcast and switches from monitoring one cell to the new cell), where a change in cell implies a change in the monitored system information broadcasts, in which case the current cell and the new cell broadcast data from the current and new reference stations, respectively.

[0123] The location node 17 can use the spatial information to determine whether the WD 22 should obtain RTK data from a reference station 36 that is different from its current reference station. If the reference station 36 is to be changed, the location node 17 can analyze the integer ambiguity levels of the current reference station and the new reference station (block S180). The location node 17 can send information about the new reference station 36 to the WD (block S182), including an indication of whether the integer ambiguity levels are the same as the old reference station 36. Based on this indicator, the WD 22 can determine whether the integer ambiguity solution associated with the current reference station 36 can be transferred to the integer ambiguity solution associated with the new reference station 36 (block S184). If so, the WD can use the integer ambiguity solution associated with the new reference station 36 and the carrier phase observations from the new reference station to accurately estimate its position.

[0124] An alternative is to provide some additional information to the WD 22 when the location server exchanges the reference station 36 from which the observations originated. For two receivers a and b making simultaneous measurements of satellites 1 and 2 at the same nominal time, the observed double difference is:

[0125]

[0126] in:

[0127]

[0128] against Solve the integer ambiguity solution, where:

[0129]

[0130] For a WD 22 denoted as r (rover) and a current reference station 36c, the WD 22 maintains an integer solution for two satellites i and j Finally, when WD 22 has moved to the new reference station 36n, WD 22 needs to be solved instead This will require some initialization time, etc. Fortunately, given equation (5), we can use and The relationship between:

[0131]

[0132] If for all satellite pairs i and j, (If for all satellite pairs the new reference station and the current reference station 36, is true), the current reference station and the new reference station 36 are said to be at the same integer ambiguity level.

[0133] The WD 22 may send a request message including the spatial information via the radio interface 82 or the WD 22 will change cells to monitor the system information broadcast for GNSS RTK data.

[0134] The location node 17 may compute double-difference integer ambiguity solutions for the receiver pair associated with the current reference station and the new reference station and for the satellite pair via, for example, processing circuitry 100. In one embodiment, the location node 17 utilizes carrier phase measurements from both reference stations and for the satellite pair.

[0135] In one embodiment, the location node 17 explicitly indicates whether two reference stations are at the same integer ambiguity level. This can be an explicit indication for each pair of reference stations or a general indication that all reference stations in the area are at the same integer ambiguity level.

[0136] In another embodiment, the WD 22 obtains the integer ambiguity level indication via system information broadcast from a radio base station via, for example, the radio interface 82 . Figure 17 Steps for preparing assistance data by a location server or a different location node 17 are described for a situation where reference stations have the same integer ambiguity level. Specifically, as described herein, the location node 17 is configured, for example, via the processing circuitry 100 and / or the processor 102 and / or the radio interface 98 and / or the communication interface 96, to receive (block S186) an integer ambiguity level indication capability from the WD 22. As described herein, the location node 17 is configured, for example, via the processing circuitry 100 and / or the processor 102 and / or the radio interface 98 and / or the communication interface 96, to prepare (block S188) GNSS RTK data for a plurality of reference stations, where the integer ambiguity level is the same. The location node 17 is configured, for example, via the processing circuitry 100 and / or the processor 102 and / or the radio interface 98 and / or the communication interface 96, to compile (block S190) GNSS RTK data for broadcast, the broadcast being associated with reference station n and including an indicator indicating whether the integer ambiguity level is the same as that of reference station c. As described herein, the location node 17 is configured to send (block S192) GNSS RTK data to the network node 16 for broadcast, for example, via the processing circuit 100 and / or the processor 102 and / or the radio interface 98 and / or the communication interface 96. In yet another embodiment, for example, when the operator network causes all reference stations to be at the same integer ambiguity level, the WD 22 obtains the integer ambiguity level indication through subscription information via, for example, the radio interface 82.

[0137] In yet another embodiment, the WD 22 assumes that both reference stations are at the same integer ambiguity level and verifies the assumption by analyzing whether the assumption matches the GNSS observations and assistance data after switching to the new reference station.

[0138] According to the 3rd Generation Partnership Project (3GPP) Technical Standard (TS) 36.355, the following standard languages ​​are provided:

[0139] The IE GNSS-RTK-ReferenceStationInfo is used by the location server to provide the Earth-centered Earth Fixed (ECEF) coordinates of the Antenna Reference Point (ARP) of a stationary reference station 36 , where GNSS-RTK-Observations assistance data is provided together with the reference station 36 antenna description.

[0140] The parameters provided in the information element (IE) GNSS-RTK-ReferenceStationInfo are used as specified for message types 1006 , 1033 , and 1032 .

[0141] Additionally, the following computer code is provided, where boldface may indicate modifications according to the teachings described herein:

[0142]

[0143]

[0144]

[0145] The following fields and explanations are provided:

[0146]

[0147]

[0148]

[0149] According to one aspect, a location node 17 configured to communicate with a wireless device (WD 22) includes a radio interface 98 and / or includes processing circuitry 100 configured to receive spatial information from WD 22 and determine, based at least in part on the spatial information, whether WD 22 is to be configured to obtain real-time kinematic (RTK) data from a subsequent reference station 36 that is different from current reference station 36 providing RTK data to WD 22. Location node 17 is further configured to analyze integer ambiguity levels of subsequent reference station 36 and current reference station 36 and to send an indication indicating whether WD 22 is to use the same integer ambiguity level for subsequent reference station 36 as for the current reference station.

[0150] According to this aspect, in some embodiments, the location node 17, the radio interface 98, and / or the processing circuitry 100 are further configured to receive from the WD 22 an indication of integer ambiguity level capabilities supported by the WD 22. In some embodiments, the indication includes an indication that the current reference station and the subsequent reference station 36 have the same integer ambiguity level.

[0151] According to another aspect, a method implemented in position node 17 includes receiving spatial information from WD 22, determining, based at least in part on the spatial information, whether WD 22 is to be configured to obtain real-time kinematic (RTK) data from a subsequent reference station 36 that is different from a current reference station 36 providing RTK data to WD 22, and analyzing integer ambiguity levels for subsequent reference station 36 and the current reference station. The method also includes sending an indication indicating whether WD 22 is to use the same integer ambiguity level for subsequent reference station 36 as for the current reference station.

[0152] According to this aspect, in some embodiments, the method further includes receiving from WD 22 an integer ambiguity level indication capability of WD 22. In some embodiments, the indication includes an indication that the current reference station and the subsequent reference station 36 have the same integer ambiguity level.

[0153] According to yet another aspect, a wireless device (WD 22) configured to communicate with a location node 17 includes a radio interface 82 and / or processing circuitry 84 configured to send spatial information to the location node 17, receive an integer ambiguity level indication indicating whether the WD 22 is to use the same integer ambiguity level for a subsequent reference station 36 as the integer ambiguity level used by the current reference station, and select an integer ambiguity level based on the indication.

[0154] According to this aspect, in some embodiments, the indication is received in a system broadcast message or subscription information. In some embodiments, the WD 22, radio interface 82, and / or processing circuitry 84 are further configured to verify the assumption that the subsequent reference station 36 and the current reference station 36 have the same integer ambiguity level.

[0155] According to another aspect, a method implemented in a wireless device (WD 22) includes sending spatial information to a location node 17, receiving an integer ambiguity level indication indicating whether the WD 22 is to use the same integer ambiguity level for a subsequent reference station 36 as the integer ambiguity level used by the current reference station, and selecting an integer ambiguity level based on the indication.

[0156] According to this aspect, in some embodiments, the indication is received in a system broadcast message or subscription information.In some embodiments, the method further comprises verifying the assumption that the subsequent reference station 36 and the current reference station 36 have the same integer ambiguity level.

[0157] The core of the solution is a signaling framework that is used to provide an indication of the same integer ambiguity level between reference stations in order to facilitate a fast transfer of integer ambiguity solutions when moving from a current reference station 36 to a new reference station.

[0158] Some examples

[0159] Example A1. A network node 16 configured to communicate with a wireless device 22 (WD 22) and at least one reference station 36, the network node 16 being configured to and / or including a radio interface 62 and / or including processing circuitry 68 configured to:

[0160] receiving spatial information from the WD 22;

[0161] determining, based at least in part on the spatial information, whether the WD 22 is to be configured to obtain real-time kinematic (RTK) data from a subsequent reference station 36 that is different from a current reference station providing RTK data to the WD 22;

[0162] analyzing integer ambiguity levels of the subsequent reference station 36 and the current reference station 36; and

[0163] Sends an indication whether the WD 22 is to use the same integer ambiguity level for the subsequent reference station 36 as the integer ambiguity level for the current reference station 36 .

[0164] Example A2. The network node 16 of Example A1, wherein the network node 16, the radio interface 62, and / or the processing circuit 68 are further configured to receive from the WD 22 an integer ambiguity level indication capability supported by the WD 22.

[0165] Example A3. The network node 16 of Example A1, wherein the indication comprises an indication that the current reference station and a subsequent reference station have the same integer ambiguity level.

[0166] Example B1. A method implemented in a network node 16, the method comprising:

[0167] receiving spatial information from the WD 22;

[0168] determining, based at least in part on the spatial information, whether the WD 22 is to be configured to obtain real-time kinematic (RTK) data from a subsequent reference station 36 that is different from a current reference station providing RTK data to the WD 22;

[0169] analyzing integer ambiguity levels of the subsequent reference station 36 and the current reference station 36; and

[0170] Sends an indication whether the WD 22 is to use the same integer ambiguity level for the subsequent reference station 36 as the integer ambiguity level for the current reference station 36 .

[0171] Example B2. The method of Example B1, further comprising receiving, from the WD 22, an integer ambiguity level indication capability of the WD 22.

[0172] Example B3. The method of Example B1, wherein the indication comprises an indication that the current reference station and subsequent reference station 36 have the same integer ambiguity level.

[0173] Example C1. A wireless device 22 (WD 22) configured to communicate with a network node 16 and at least one reference station, the WD 22 being configured to and / or including a radio interface 82 and / or processing circuitry 84 configured to:

[0174] Sending spatial information to the network node 16;

[0175] receiving an integer ambiguity level indication indicating whether the WD 22 is to use the same integer ambiguity level for a subsequent reference station 36 as the integer ambiguity level used by the current reference station 36; and

[0176] An integer ambiguity level is selected based on the indication.

[0177] Example C2. The WD 22 of Example C1, wherein the indication is received in a system broadcast message or a subscription message.

[0178] Example C3. The WD 22 of Example C1, wherein the WD 22, radio interface 82, and / or processing circuitry 84 are further configured to verify an assumption that the subsequent reference station 36 and the current reference station 36 have the same integer ambiguity level.

[0179] Example D1. A method implemented in a wireless device 22 (WD 22), the method comprising:

[0180] Sending spatial information to the network node 16;

[0181] receiving an integer ambiguity level indication indicating whether the WD 22 is to use the same integer ambiguity level for a subsequent reference station as used by the current reference station 36; and

[0182] An integer ambiguity level is selected based on the indication.

[0183] Example D2. The method of Example D1, wherein the indication is received in a system broadcast message or subscription information.

[0184] Example D3. The method of Example D1, further comprising verifying an assumption that the subsequent reference station 36 and the current reference station 36 have the same integer ambiguity level.

[0185] As will be appreciated by those skilled in the art, the concepts described herein may be embodied as methods, data processing systems, computer program products, and / or computer storage media storing executable computer programs. Thus, the concepts described herein may take the form of all-hardware embodiments, all-software embodiments, or embodiments combining aspects of hardware and software, all of which are collectively referred to herein as "circuits" or "modules." Any process, step, action, and / or function described herein may be performed and / or associated with a corresponding module, which may be implemented in software and / or firmware and / or hardware. In addition, the present disclosure may take the form of a computer program product on a tangible computer-usable storage medium having computer program code embodied therein that is executable by a computer. Any suitable tangible computer-readable medium may be utilized, including a hard disk, a CD-ROM, an electrical storage device, an optical storage device, or a magnetic storage device.

[0186] Some embodiments are described herein with reference to flowchart illustrations and / or block diagrams of methods, systems, and computer program products. It should be understood that each block in 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 can be provided to a general-purpose computer (thereby creating a special-purpose computer), a processor of a special-purpose computer, or other programmable data processing apparatus used to produce a machine, so that the instructions (executed via the processor of the computer or other programmable data processing apparatus) create a program that implements the flowchart and / or block diagrams. Figure 1 means for performing the functions / actions specified in one or more blocks.

[0187] These computer program instructions may also be stored in a computer-readable memory or storage medium that directs a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory generate instructions including implementing the flowcharts and / or block diagrams. Figure 1An article of manufacture that instructs means for performing the functions / actions specified in one or more blocks.

[0188] Computer program instructions may also be loaded into a computer or other programmable data processing apparatus to cause a series of operable steps to be executed on the computer or other programmable apparatus to generate a computer-implemented process, so that the instructions executed on the computer or other programmable apparatus provide for implementing the flowcharts and / or block diagrams. Figure 1 The steps of the functions / actions specified in one or more boxes.

[0189] It should be understood that the functions and / or actions marked in the blocks may not occur in the order marked in the operational description. For example, depending on the functions / actions involved, two blocks shown in succession may actually be executed substantially simultaneously, or the blocks may sometimes be executed in the reverse order. Although some figures include arrows on communication paths to indicate the primary direction of communication, it will be understood that communication may occur in the opposite direction of the indicated arrows.

[0190] Computer program code for carrying out operations of the concepts described herein may be used, for example, The computer program code for performing the operations of the present disclosure may be written in an object-oriented programming language such as C or C++. However, the computer program code for performing the operations of the present disclosure may also be written in a conventional procedural programming language such as the "C" programming language. The program code may be executed entirely on the user's computer, partially on the user's computer, as a stand-alone software package, partially on the user's computer and partially on a remote computer, or entirely on the remote computer. In the latter case, the remote computer may be connected to the user's computer via a local area network (LAN) or a wide area network (WAN), or an external computer may be connected (e.g., via the Internet using an Internet service provider).

[0191] In conjunction with the above description and accompanying drawings, many different embodiments are disclosed herein. It will be understood that verbatim describing and illustrating every combination and subcombination of these embodiments would be unduly repetitive and obfuscating. Therefore, all embodiments may be combined in any manner and / or combination, and this specification, including the accompanying drawings, is to be construed to constitute a complete written description of all combinations and subcombinations of the embodiments described herein, as well as the manner and process of making and using them, and will support claims for any such combination or subcombination.

[0192] Abbreviations that may be used in the previous description include:

[0193] Explanation of abbreviations

[0194] E-SMLC Evolved Serving Mobile Location Center

[0195] GNSS Global Navigation System

[0196] RTK Real-Time Kinematics

[0197] RMS root mean square

[0198] Those skilled in the art will recognize that the embodiments described herein are not limited to what has been specifically shown and described above. In addition, unless otherwise indicated above, it should be noted that all drawings are not drawn to scale. Various modifications and variations are possible in light of the above teachings without departing from the scope of the appended claims.

Claims

1. A location node (17) configured to communicate with a wireless device (22), the location node (17) comprising: The processing circuit (100) is configured to: receiving a request message including a cell identifier of a cell serving the wireless device (22); and An indication of applicability of a first integer ambiguity level for a first Global Navigation Satellite System Real-Time Kinematic (GNSS-RTK) reference station (36) and a second integer ambiguity level for a second GNSS-RTK reference station (36) is transmitted, the first GNSS-RTK reference station (36) and the second GNSS-RTK reference station (36) being associated with spatial information associated with a cell identifier of a cell serving the wireless device (22).

2. The location node (17) according to claim 1, wherein The indication indicates that the first integer ambiguity level of the first GNSS-RTK reference station (36) can be transferred to the second GNSS-RTK reference station (36).

3. The location node (17) according to claim 1, wherein The indication indicates that the first integer ambiguity level of the first GNSS-RTK reference station (36) cannot be transferred to the second GNSS-RTK reference station (36).

4. The location node (17) according to claim 1, wherein The processing circuit (100) is further configured to: determining a wireless device relationship between the first GNSS-RTK reference station (36) and the second GNSS-RTK reference station (36) based at least in part on spatial information associated with a cell identifier of a cell serving the wireless device (22); as well as The first integer ambiguity level of the first GNSS-RTK reference station (36) is compared with the second integer ambiguity level of the second GNSS-RTK reference station (36), the second GNSS-RTK reference station (36) corresponding to a current GNSS-RTK reference station (36) of the wireless device (22).

5. The location node (17) according to any one of claims 1 to 4, wherein: The spatial information indicates that the wireless device (22) is monitoring system information broadcast in a spatial region associated with the cell identifier.

6. The location node (17) according to any one of claims 1-4, wherein: The indication to the wireless device (22) indicates that the wireless device (22) monitors RTK signaling from the second GNSS-RTK reference station (36) instead of the first GNSS-RTK reference station (36).

7. The location node (17) according to any one of claims 1 to 4, wherein: The first GNSS-RTK reference station (36) corresponds to a first node having a known first physical location and a first antenna configuration having a first global navigation satellite system receiver for measuring signals from at least one satellite; as well as The second GNSS-RTK reference station (36) corresponds to a second node having a known second physical location and a second antenna configuration having a second global navigation satellite system receiver for measuring signals from at least one satellite.

8. The location node (17) according to any one of claims 1 to 4, wherein: The wireless device (22) is reassigned from the first GNSS-RTK reference station (36) to the second GNSS-RTK reference station (36); and The indication indicates that the wireless device (22) monitors RTK signaling from the second GNSS-RTK reference station (36) instead of the first GNSS-RTK reference station (36).

9. A wireless device (22) configured to communicate with a network node (17), the wireless device (22) comprising: The processing circuit (84) is configured to: sending a request message, the request message including a cell identifier of a cell serving the wireless device (22); receiving an indication of applicability of a first integer ambiguity level for a first Global Navigation Satellite System Real-Time Kinematic (GNSS-RTK) reference station (36) and a second integer ambiguity level for a second GNSS-RTK reference station (36), the first GNSS-RTK reference station (36) and the second GNSS-RTK reference station (36) being associated with spatial information associated with a cell identifier of a cell serving the wireless device (22); and A location of the wireless device (22) is estimated based at least in part on the indication.

10. The wireless device (22) of claim 9, wherein: The indication indicates that the first integer ambiguity level of the first GNSS-RTK reference station (36) can be transferred to the second GNSS-RTK reference station (36).

11. The wireless device (22) of claim 9, wherein: The indication indicates that the first integer ambiguity level of the first GNSS-RTK reference station (36) cannot be transferred to the second GNSS-RTK reference station (36).

12. The wireless device (22) according to any one of claims 9 to 11, wherein The spatial information indicates a cell identifier of a cell serving the wireless device (22).

13. The wireless device (22) according to any one of claims 9 to 11, wherein The spatial information indicates that the wireless device (22) is monitoring system information broadcast in a spatial region associated with a cell identifier.

14. The wireless device (22) according to any one of claims 9 to 11, wherein The first GNSS-RTK reference station (36) corresponds to a first node having a known first physical location and a first antenna configuration having a first global navigation satellite system receiver for measuring signals from at least one satellite; as well as The second GNSS-RTK reference station (36) corresponds to a second node having a known second physical location and a second antenna configuration having a second global navigation satellite system receiver for measuring signals from at least one satellite.

15. The wireless device (22) according to any one of claims 9 to 11, wherein The processing circuit (84) is further configured to determine a carrier phase of the second GNSS-RTK reference station (36), the estimate of the position being based at least in part on the determined carrier phase of the second GNSS-RTK reference station (36).

16. The wireless device (22) according to any one of claims 9 to 11, wherein The wireless device is reassigned from the first GNSS-RTK reference station (36) to the second GNSS-RTK reference station (36).

17. The wireless device (22) of claim 16, wherein: The indication indicates that the wireless device (22) monitors RTK signaling from the second GNSS-RTK reference station (36) instead of the first GNSS-RTK reference station (36).

18. The wireless device (22) according to any one of claims 9 to 11, wherein The indication is received in a broadcast from a network node (16) serving the wireless device (22).

19. A method for a location node (17) configured to communicate with a wireless device (22), the method comprising: receiving ( S142 ) a request message, the request message including a cell identifier of a cell serving the wireless device ( 22 ); as well as An indication of the applicability of a first integer ambiguity level of a first Global Navigation Satellite System Real-Time Kinematic (GNSS-RTK) reference station (36) and a second integer ambiguity level of a second GNSS-RTK reference station (36) is sent (S148), the first GNSS-RTK reference station (36) and the second GNSS-RTK reference station (36) being associated with spatial information associated with a cell identifier of a cell serving the wireless device (22).

20. The method according to claim 19, wherein The indication indicates that the first integer ambiguity level of the first GNSS-RTK reference station (36) can be transferred to the second GNSS-RTK reference station (36).

21. The method according to claim 19, wherein The indication indicates that the first integer ambiguity level of the first GNSS-RTK reference station (36) cannot be transferred to the second GNSS-RTK reference station (36).

22. The method of claim 19, further comprising: determining (S144) a wireless device relationship between the first GNSS-RTK reference station (36) and the second GNSS-RTK reference station (36) based at least in part on spatial information associated with a cell identifier of a cell serving the wireless device (22); and The first integer ambiguity level of the first GNSS-RTK reference station (36) is compared (S146) with the second integer ambiguity level of the second GNSS-RTK reference station (36), the second GNSS-RTK reference station (36) corresponding to the current GNSS-RTK reference station (36) of the wireless device (22).

23. The method according to any one of claims 19 to 22, wherein: The spatial information indicates that the wireless device (22) is monitoring system information broadcast in a spatial region associated with the cell identifier.

24. The method according to any one of claims 19 to 22, wherein: The indication to the wireless device (22) indicates that the wireless device (22) monitors RTK signaling from the second GNSS-RTK reference station (36) instead of the first GNSS-RTK reference station (36).

25. The method according to any one of claims 19 to 22, wherein: The first GNSS-RTK reference station (36) corresponds to a first node having a known first physical location and a first antenna configuration having a first global navigation satellite system receiver for measuring signals from at least one satellite; as well as The second GNSS-RTK reference station (36) corresponds to a second node having a known second physical location and a second antenna configuration having a second global navigation satellite system receiver for measuring signals from at least one satellite.

26. The method according to any one of claims 19 to 22, wherein: The wireless device (22) is reassigned from the first GNSS-RTK reference station (36) to the second GNSS-RTK reference station (36); and The indication indicates that the wireless device (22) monitors RTK signaling from the second GNSS-RTK reference station (36) instead of the first GNSS-RTK reference station (36).

27. A method for a wireless device (22) configured to communicate with a location node (17), the method comprising: sending (S156) a request message, the request message including a cell identifier of a cell serving the wireless device (22); receiving (S158) an indication of the applicability of a first integer ambiguity level of a first Global Navigation Satellite System Real-Time Kinematic (GNSS-RTK) reference station (36) and a second integer ambiguity level of a second GNSS-RTK reference station (36), the first GNSS-RTK reference station (36) and the second GNSS-RTK reference station (36) being associated with spatial information associated with a cell identifier of a cell serving the wireless device (22); and A location of the wireless device (22) is estimated (s160) based at least in part on the indication.

28. The method according to claim 27, wherein The indication indicates that the first integer ambiguity level of the first GNSS-RTK reference station (36) can be transferred to the second GNSS-RTK reference station (36).

29. The method according to claim 27, wherein The indication indicates that the first integer ambiguity level of the first GNSS-RTK reference station (36) cannot be transferred to the second GNSS-RTK reference station (36).

30. The method according to any one of claims 27 to 29, wherein The spatial information indicates a cell identifier of a cell serving the wireless device (22).

31. The method according to any one of claims 27 to 29, wherein The spatial information indicates that the wireless device (22) is monitoring system information broadcast in a spatial region associated with a cell identifier.

32. The method according to any one of claims 27 to 29, wherein: The first GNSS-RTK reference station (36) corresponds to a first node having a known first physical location and a first antenna configuration having a first global navigation satellite system receiver for measuring signals from at least one satellite; as well as The second GNSS-RTK reference station (36) corresponds to a second node having a known second physical location and a second antenna configuration having a second global navigation satellite system receiver for measuring signals from at least one satellite.

33. The method according to any one of claims 27 to 29, further comprising: A carrier phase of the second GNSS-RTK reference station (36) is determined, and the estimate of the position is based at least in part on the determined carrier phase of the second GNSS-RTK reference station (36).

34. The method according to any one of claims 27 to 29, wherein: The wireless device (22) is reassigned from the first GNSS-RTK reference station (36) to the second GNSS-RTK reference station (36).

35. The method according to claim 34, wherein The indication indicates that the wireless device (22) monitors RTK signaling from the second GNSS-RTK reference station (36) instead of the first GNSS-RTK reference station (36).

36. The method according to any one of claims 27 to 29, wherein The indication is received in a broadcast from a network node (16) serving the wireless device (22).

Images