EP4666089A1

EP4666089A1 - Correction factors for carrier phase based positioning

Info

Publication number: EP4666089A1
Application number: EP24706077.5A
Authority: EP
Inventors: Gustav Lindmark; Siva Muruganathan; Deep SHRESTHA; Johannes NYGREN
Original assignee: Telefonaktiebolaget LM Ericsson AB
Current assignee: Telefonaktiebolaget LM Ericsson AB
Priority date: 2023-02-17
Filing date: 2024-02-16
Publication date: 2025-12-24
Also published as: WO2024170761A1

Abstract

According to some embodiments, a method (1000) is performed by a wireless device for position determination. The method comprises receiving (1012) one or more carrier phase correction factors and performing (1014) carrier phase-based positioning with differentiation based on the one or more carrier phase correction factors.

Description

Correction Factors for Carrier Phase Based Positioning

TECHNICAL FIELD

[0001] The present disclosure generally relates to communication networks, and more specifically to correction factors for carrier phase based positioning.

BACKGROUND

[0002] One feature provided by wireless networks is positioning for wireless devices. Positioning in fifth generation (5G) New Radio (NR) is supported by the architecture illustrated in Figure 1.

[0003] Figure 1 is a functional block diagram illustrating the next generation radio access network (NG-RAN) location services (LCS) protocols. The Location Management Function (LMF) is the location node in NR. There are also interactions between the location node and the gNodeB via the NR Positioning Protocol A (NRPPa) protocol. The interactions between the gNodeB and the device is supported via the Radio Resource Control (RRC) protocol.

[0004] With respect to the illustrated example, the gNB and ng-eNB may not always both be present. When both the gNB and ng-eNB are present, the NG-C interface is only present for one of them.

[0005] NR currently supports the following radio access technology (RAT) dependent positioning methods.

[0006] DL-TDOA: The downlink time difference of arrival (DL TDOA) positioning method uses the downlink reference signal time difference (RSTD) (and optionally downlink positioning reference signal receive power (PRS RSRP)) of downlink signals received from multiple transmission points (TPs), at the user equipment (UE). The UE measures the DL RSTD (and optionally DL PRS RSRP) of the received signals using assistance data received from the positioning server, and the resulting measurements are used along with other configuration information to locate the UE in relation to the neighboring TPs.

[0007] Multi -RTT: The multiple round trip time (RTT) positioning method uses the UE Rx-

Tx measurements and DL PRS RSRP of downlink signals received from multiple TRPs, measured by the UE and the measured gNB Rx-Tx measurements and uplink (UL) sounding reference signal (SRS) RSRP at multiple TRPs of uplink signals transmitted from UE.

[0008] UL-TDOA:_The UL TDOA positioning method uses the UL TDOA (and optionally UL SRS-RSRP) at multiple reception points (RPs) of uplink signals transmitted from UE. The RPs measure the UL TDOA (and optionally UL SRS-RSRP) of the received signals using assistance data received from the positioning server, and the resulting measurements are used along with other configuration information to estimate the location of the UE.

[0009] DL-AoD: The DL angle of departure (AoD) positioning method uses the measured DL PRS RSRP of downlink signals received from multiple TPs, at the UE. The UE measures the DL PRS RSRP of the received signals using assistance data received from the positioning server, and the resulting measurements are used along with other configuration information to locate the UE in relation to the neighboring TPs.

[0010] UL-AoA: The UL angle of arrival (AoA) positioning method uses the measured azimuth and zenith of arrival at multiple RPs of uplink signals transmitted from the UE. The RPs measure A-AoA and Z-AoA of the received signals using assistance data received from the positioning server, and the resulting measurements are used along with other configuration information to estimate the location of the UE.

[0011] NR-ECID:_NR Enhanced Cell ID (NRE-CID) positioning refers to techniques that use additional UE measurements and/or NR radio resource and other measurements to improve the UE location estimate.

[0012] The positioning modes can be categorized in three areas. The first is UE-assisted, where the UE performs measurements with or without assistance from the network and sends these measurements to the evovled serving mobile location center (E-SMLC) where the position calculation may take place. The second is UE-based, where the UE performs measurements and calculates its own position with assistance from the network. The third is standalone, where the UE performs measurements and calculates its own without network assistance.

[0013] Global navigation satellite system (GNSS) carrier phase positioning has been used successfully for centimeter-level accuracy positioning but is limited to outdoor applications. One Third Generation Partnership Project (3GPP) objective is to specify physical layer measurements and signaling to support NR carrier phase positioning. The Rel. 18 Work Item Description for Expanded and improved NR positioning (RP 223549) includes the following objectives. [0014] One objective is to specify physical layer measurements and signaling to support NR DL and UL carrier phase positioning for UE-based, UE-assisted, and NG-RAN node assisted positioning. The existing DL PRS and UL SRS for positioning are used for NR carrier phase measurements. Another objective is to specify measurements that are limited to a single carrier/positioning frequency layer (PFL). Another objective is to specify corresponding new core requirements, as well as identifying and specifying the impact on the existing specification, including radio resource management (RRM) measurements without measurement gaps in connected and inactive mode (including PRS measurement period/reporting) and procedures.

[0015] Carrier phase measurements are described in the following. Assume a link with one transmitter and one receiver. The transmitted pass-band signal is given by x_pb(t) = s(t) exp(j2?r _ct + j' _o) , where s(t) denotes the baseband signal and f_c denotes the carrier frequency. The term <p_Q is an offset due to Tx imperfect synchronization, it includes the RF phasedifference compared to an ideal oscillator.

[0016] Assuming line-of-sight (LOS) conditions and no multipath, the channel is h(t) = <5(t — T₀), where T₀ = d/c is the transition delay, c the speed of light and d the length of the LOS path between the transmitter and the receiver. The received passband-signal is the convolution

[0017] After down-conversion, the received baseband signal is y_Pb( ) ⁼ the term _X is an offset due to Rx imperfect synchronization, it includes the radio frequency (RF) phase-difference compared to an ideal oscillator. A carrier phase measurement of this transmission will return the phase

[0018] Above, the term 2nN corresponds to a modulus operation such that the measured phase is in the range [0, 2TT] .

[0019] Figure 2 illustrates a carrier phase measurement subject to a transmission phase offset and a receive phase offset.

[0020] The terms “Tx phase offset” or “transmission phase offset” are used herein for <p₀, and the terms “Rx phase offset” or “receive phase offset” are used herein for _X.

[0021] For carrier-phase based positioning, it is the transmission delay T₀ in Equation [1] that is of interest. The offset terms <p₀ — <p need to be estimated or cancelled out for the measurement to be accurate. In a scenario with multiple transmitters and multiple receivers, this can be accomplished by differentiation.

[0022] Rx Phase difference: If the term (f>₁ (which is due to the receiver RF offset) is the same for carrier phase measurements performed by one receiver from multiple transmitters, then (f>₁ can be canceled out if the phase difference between transmitters is computed, e.g. differentiating Eq. (1) between the transmitters.

[0023] Tx Phase difference: If the term <p_Q (which is due to the transmitter RF offset) is the same for carrier phase measurements performed by multiple receivers from one transmitter, then 0o can be canceled out if the phase difference between receivers is computed, e.g. differentiating Eq. (1) between the receivers.

[0024] Double differentiation: By combining the two differentiation methods, a doubledifferentiation scheme can be obtained which results in that all the unknown offsets are cancelled out.

[0025] A basic differentiation scheme presented assumes that

[0026] Assumption 1 : For one specific receiver, the Rx phase offset is the same for received signals from all transmitters, and

[0027] Assumption 2: For one specific transmitter, the Tx phase offset is the same for transmitted signals to all receivers.

(k [0028] Figure 3 illustrates assumptions for differentiation schemes. The Rx phase offset 0( is the same for signals from all transmitters (i and j). The transmission phase offset 0® is the same for all receivers (k and K).

[0029] There currently exist certain challenges. For example, for carrier phase-based positioning in downlink with double differentiation to work, a number of difficulties need to be addressed. One difficulty is the transmitter and receiver phase offsets can be time-varying due to, e.g., frequency error. This means that correction factors have a limited validity time and need to be updated with a frequency that depends on the change-rate. Another difficulty is that carrier phase measurement errors can have spatial variations due to the impact of the local multipath environment. For this reason, the measurements performed by one UE with known position may only be useful (for double differentiation) among UEs in its vicinity but not to other UEs. [0030] Thus, how to signal carrier phase measurements performed by a UE with known position to network nodes and other UEs to overcome the above difficulties is an open problem that needs to be solved.

SUMMARY

[0031] As described above, certain challenges currently exist with carrier phase based positioning. Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. For example, particular embodiments include signaling of carrier phase measurement correction factors. In particular embodiments, a Location Management Function (LMF) provides a target user equipment (UE) with carrier phase correction factors. The validity in both time and space of the correction factors may be ensured by updating the correction factors when needed and providing correction factors that are specific for the target UE or a local environment. Additionally, the provisioning of phase correction factors is resource efficient because it does not consume more radio resources than needed.

[0032] According to some embodiments, a method is performed by a wireless device for position determination. The method comprises receiving one or more carrier phase correction factors and performing carrier phase-based positioning with differentiation based on the one or more carrier phase correction factors.

[0033] In particular embodiments, receiving the one or more carrier phase correction factors comprises receiving the one or more carrier phase correction factors from a LMF or a base station. [0034] In particular embodiments, each of the one or more carrier phase correction factors is associated with a transmission point, a validity time, a geographical area, a confidence metric, and/or a timestamp associated with a positioning measurement associated with the correction factor.

[0035] In particular embodiments, the one or more carrier phase correction factors comprise measurements performed by a positioning reference unit (PRU), and the wireless device determines a correction factor to apply when performing carrier phase-based positioning based on the received measurement performed by the PRU.

[0036] According to some embodiments, a wireless device comprises processing circuitry operable to perform any of the wireless device methods described above.

[0037] Also disclosed is a computer program product comprising a non-transitory computer readable medium storing computer readable program code, the computer readable program code operable, when executed by processing circuitry to perform any of the methods performed by the wireless devices described above.

[0038] According to some embodiments, a method is performed by a network node for wireless device positioning. The method comprises obtaining one or more carrier phase correction factors and transmitting the one or more carrier phase correction factors to a wireless device.

[0039] In particular embodiments, obtaining the one or more carrier phase correction factors comprises receiving the one or more carrier phase correction factors from a PRU or a LMF.

[0040] In particular embodiments, each of the one or more carrier phase correction factors is associated with a transmission point, a validity time, a geographical area, a confidence metric, and/or a timestamp associated with a positioning measurement associated with the correction factor.

[0041] According to some embodiments, a network node comprises processing circuitry operable to perform any of the network node methods described above.

[0042] Another computer program product comprises a non-transitory computer readable medium storing computer readable program code, the computer readable program code operable, when executed by processing circuitry to perform any of the methods performed by the network nodes described above.

[0043] Certain embodiments may provide one or more of the following technical advantages. For example, the signaled carrier phase measurement correction factors enable accurate mitigation of carrier phase measurement offsets. The signaling solutions are efficient by minimizing the signaling overhead. Furthermore, the signaling may be optimized for low latency.

BRIEF DESCRIPTION OF THE DRAWINGS

[0044] The present disclosure may be best understood by way of example with reference to the following description and accompanying drawings that are used to illustrate embodiments of the present disclosure. In the drawings:

Figure l is a functional block diagram illustrating the next generation radio access network (NG-RAN) location services (LCS) protocols;

Figure 2 illustrates a carrier phase measurement subject to a transmission phase offset and a receive phase offset;

Figure 3 illustrates assumptions for differentiation schemes;

Figure 4 shows an example of a communication system, according to certain embodiments; Figure 5 shows a user equipment (UE), according to certain embodiments;

Figure 6 shows a network node, according to certain embodiments;

Figure 7 is a block diagram of a host, according to certain embodiments;

Figure 8 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized;

Figure 9 shows a communication diagram of a host communicating via a network node with a UE over a partially wireless connection in accordance with some embodiments;

Figure 10A is a flowchart illustrating an example method in a target wireless device, according to certain embodiments;

Figure 1 OB is a flowchart illustrating an example method in a wireless device functioning as a positioning reference unit (PRU), according to certain embodiments; and

Figure 11 is a flowchart illustrating an example method in a network node, according to certain embodiments.

DETAILED DESCRIPTION

[0045] As described above, certain challenges currently exist with carrier phase based positioning. Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. For example, particular embodiments include signaling of carrier phase measurement correction factors. In particular embodiments, a Location Management Function (LMF) provides a target user equipment (UE) with carrier phase correction factors. The validity in both time and space of the correction factors may be ensured by updating the correction factors when needed and providing correction factors that are specific for the target UE or a local environment.

[0046] Particular embodiments are described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0047] Particular embodiments described herein include carrier phase-based positioning in downlink and how carrier phase measurements performed by one UE may be distributed to network nodes and other UEs to enable double differentiation as described in the background. Normally, the first UE has a known position (henceforth referred to as “positioning reference unit,” PRU), and the later UEs are referred to as “target UEs.” More generally, the target UEs are provided with phase correction factors that have been obtained from measurements performed by one or more PRUs in the vicinity of target UE(s).

[0048] In the embodiments presented herein, the signaling of correction factors is between one or more UEs and an LMF. This does not limit the applicability of the embodiments and the embodiments are valid when the signaling of correction factors is between one or more UEs and another network node (e.g., gNB, eNB).

[0049] Let = [ i, ... , <p_n] be a vector of carrier phase correction factors. The element <pt, i E 1, n, is the correction factor for transmission/reception point (TRP) i.

[0050] In a particular embodiment, an LMF provides a target UE with phase correction factors for a set of TRPs. The range of each correction factor <pt, i E 1, n can be, in radians [— TT, TT], [— 2n, 0] or [0, 2TT], in degrees [—180, 180], [—360,0], [0, 360] or normalized to [—0.5, 0.5], [-1,0] or [0, 1],

[0051] In some embodiments, each correction factor <p is quantized to a finite number of bits (e.g., N bits providing 2^W quantization levels), where N is a positive integer. The value of N is chosen such that the quantized correction factor meets the accuracy requirements needed for carrier phase based positioning.

[0052] The target UE constructs the differentials between its own carrier phase measurements and the correction factors to cancel out Tx phase offsets of TRPs.

[0053] In some embodiments, when the LMF provides multiple correction factors to the target UE, the LMF provides information on which correction factors correspond to which TRP. In some embodiments, each of the multiple correction factors is associated with an identifier of the TRP (e.g., TRP ID). In some embodiments, the LMF may associate each correction factor with one or more of: an identifier of a TRP; an identifier of a positioning reference signal (PRS) resource; an identifier of a PRS resource set; or an identifier of positioning frequency layer(s) (PFL(s)). This way, the target UE knows which correction factor to apply depending on which TRP, which PRS resource set, which PRS resource and/or PFL(s) on which the target UE performs a carrier phase measurement to which the correction factor is applied.

[0054] The correction factors may have a limited validity time. In some embodiments, the LMF provides the target UE with the validity time of the correction factors. The validity time may be in the form of a validity start time, t_start, and/or a validity end time, t_end . In some embodiments, the validity time may be defined as a length or duration in time (i.e., the provided correction factor is valid for the length or duration in time) from the time the LMF provides the correction factors to the target UE.

[0055] In some embodiments, the target UE applies the correction factors to cancel out Tx phase offsets of TRPs during the validity time or validity duration over which the correction factors are valid).

[0056] In some embodiments, each correction factor includes a timestamp representing the time at which the correction factor was determined by a PRU. The LMF signals the correction factors along with the corresponding time stamps to the target UE. From the timestamp, the target UE may determine whether the correction factors are outdated (e.g., the target UE determines a correction factor to be outdated if the timestamp associated with the correction factors points to a time that is X slots/milliseconds/seconds older than the current time). In some embodiments, the value of X may be configured to the UE by a network node (e.g., LMF or gNB). In some embodiment, the value of X may be predefined in Third Generation Partnership Project (3GPP) specifications.

[0057] In some embodiments, when the validity time or validity duration runs out, the UE may request the LMF to provide updated correction factors to the LMF through higher layer signaling (e.g., via Long Term Evolution (LTE) Positioning Protocol (LPP) signaling). The LMF provides updated correction factors to the target UE in response to receiving the request from the target UE.

[0058] In some embodiments, the LMF signals the correction factors to the target UE periodically via higher layer signaling (e.g., via LPP).

[0059] In some embodiments, the LMF signals the correction factors to the serving cell gNB of the target UE via e.g., New Radio (NR) Positioning Protocol a (NRPPa) signaling. The serving cell gNB then signals the correction factors to the target UE via one of Radio Resource Control (RRC) signaling, downlink control indication (DCI) signaling, or downlink medium access control (MAC) control element (CE) signaling.

[0060] In some embodiments, the serving cell gNB broadcasts the correction factors to multiple target UEs within its cell. In some embodiments, the serving cell gNB signals the correction factors to the target UE(s) via system information block (SIB).

[0061] The correction factors may have a limited validity in space (due to local multipath conditions, for example). In some embodiments, the LMF provides the target UE with a geographical area in which the compensation factors are valid. [0062] The LMF may obtain a new set of phase correction factors that is different compared to those that have already been provided to the target UE. In some embodiments, the LMF may provide updated carrier phase correction factors to the target UE.

[0063] In some cases, the correct phase compensation factors vary over time according to a simple function, e.g. a linear drift. If the drift-rate is known, then the target UE may update the phase correction factors itself. In some embodiments, the LMF may provide the linear drift rate of the correction factors to the UE.

[0064] In some cases, there is no trustworthy estimate for the phase correction factors. For example, there may be several PRUs that report inconsistent carrier phase measurements so that the LMF does not know which one is right. In other cases, a single PRU may report carrier phase measurements with high variance. It may be important that the target UE does not treat the provided phase correction factors are trustworthy when they are not. In some embodiments, the LMF provides the target UE with a metric for the confidence in the provided phase correction factors. The confidence may be expressed as the standard-deviation or variance of the correction factors.

[0065] In some embodiments, when the LMF cannot obtain useful phase correction factors, the LMF may signal this to the target UE. The LMF may use a special error-value outside the regular range for the phase corrections.

[0066] In some embodiments, the LMF may average the correction factors received from multiple PRUs within a close proximity of the target UE(s), and provide the averaged correction factors to the target UE.

[0067] In some cases, it may be useful to limit the signaling overhead and only provide phase correction updates when the changes are large enough to significantly impact the positioning performance.

[0068] In some embodiments, the LMF will only provide updated carrier phase correction factors if the factors have changed more than a given number, in absolute terms.

[0069] A threshold 6 may be configured by the target UE, by LMF or other node. The threshold is used to control the frequency of provisioning of phase correction updates to the target UE.

[0070] An algorithm to provide updated correction factors to the UE can be as follows:

• for each time-instance k

[0071] In some embodiments, when a UE receives updated correction factors from the LFM, the UE may use the updated correction factors to perform carrier phase measurement, or the UE may decide to use one of the previous correction factors and continue performing carrier phase measurement without updating the correction factor. In the latter case, the UE indicates usage of old or correction factor previous to the updated correction factor to the LMF along with the carrier phase measurement. The indication may be done by reporting the correction factor ID it used to perform reported carrier phase measurement(s).

[0072] Figure 4 shows an example of a communication system 100 in accordance with some embodiments. In the example, the communication system 100 includes a telecommunication network 102 that includes an access network 104, such as a radio access network (RAN), and a core network 106, which includes one or more core network nodes 108. The access network 104 includes one or more access network nodes, such as network nodes 110a and 110b (one or more of which may be generally referred to as network nodes 110), or any other similar 3 ^rd Generation Partnership Project (3GPP) access node or non-3GPP access point. The network nodes 110 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 112a, 112b, 112c, and 112d (one or more of which may be generally referred to as UEs 112) to the core network 106 over one or more wireless connections.

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

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

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

[0076] The host 116 may be under the ownership or control of a service provider other than an operator or provider of the access network 104 and/or the telecommunication network 102, and may be operated by the service provider or on behalf of the service provider. The host 116 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio/video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server. [0077] As a whole, the communication system 100 of Figure 4 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and/or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.

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

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

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

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

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

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

[0084] The UE 200 includes processing circuitry 202 that is operatively coupled via a bus 204 to an input/output interface 206, a power source 208, a memory 210, a communication interface 212, and/or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 2. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

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

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

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

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

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

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

[0091] In the illustrated embodiment, communication functions of the communication interface 212 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short- range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and/or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol/internet protocol (TCP/IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0092] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 212, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient). [0093] As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

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

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

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

[0097] Figure 6 shows a network node 300 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a UE and/or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)).

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

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

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

[0101] The processing circuitry 302 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node 300 components, such as the memory 304, to provide network node 300 functionality.

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

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

[0104] The communication interface 306 is used in wired or wireless communication of signaling and/or data between a network node, access network, and/or UE. As illustrated, the communication interface 306 comprises port(s)/terminal(s) 316 to send and receive data, for example to and from a network over a wired connection. The communication interface 306 also includes radio front-end circuitry 318 that may be coupled to, or in certain embodiments a part of, the antenna 310. Radio front-end circuitry 318 comprises filters 320 and amplifiers 322. The radio front-end circuitry 318 may be connected to an antenna 310 and processing circuitry 302. The radio front-end circuitry may be configured to condition signals communicated between antenna 310 and processing circuitry 302. The radio front-end circuitry 318 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 320 and/or amplifiers 322. The radio signal may then be transmitted via the antenna 310. Similarly, when receiving data, the antenna 310 may collect radio signals which are then converted into digital data by the radio front-end circuitry 318. The digital data may be passed to the processing circuitry 302. In other embodiments, the communication interface may comprise different components and/or different combinations of components.

[0105] In certain alternative embodiments, the network node 300 does not include separate radio front-end circuitry 318, instead, the processing circuitry 302 includes radio front-end circuitry and is connected to the antenna 310. Similarly, in some embodiments, all or some of the RF transceiver circuitry 312 is part of the communication interface 306. In still other embodiments, the communication interface 306 includes one or more ports or terminals 316, the radio front-end circuitry 318, and the RF transceiver circuitry 312, as part of a radio unit (not shown), and the communication interface 306 communicates with the baseband processing circuitry 314, which is part of a digital unit (not shown). [0106] The antenna 310 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. The antenna 310 may be coupled to the radio front-end circuitry 318 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In certain embodiments, the antenna 310 is separate from the network node 300 and connectable to the network node 300 through an interface or port.

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

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

[0109] Embodiments of the network node 300 may include additional components beyond those shown in Figure 6 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein. For example, the network node 300 may include user interface equipment to allow input of information into the network node 300 and to allow output of information from the network node 300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 300. [0110] Figure 7 is a block diagram of a host 400, which may be an embodiment of the host 116 of Figure 1, in accordance with various aspects described herein. As used herein, the host 400 may be or comprise various combinations hardware and/or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm. The host 400 may provide one or more services to one or more UEs.

[oni] The host 400 includes processing circuitry 402 that is operatively coupled via a bus 404 to an input/output interface 406, a network interface 408, a power source 410, and a memory 412. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 10 and 3, such that the descriptions thereof are generally applicable to the corresponding components of host 400.

[0112] The memory 412 may include one or more computer programs including one or more host application programs 414 and data 416, which may include user data, e.g., data generated by a UE for the host 400 or data generated by the host 400 for a UE. Embodiments of the host 400 may utilize only a subset or all of the components shown. The host application programs 414 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). The host application programs 414 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host 400 may select and/or indicate a different host for over-the-top services for a UE. The host application programs 414 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.

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

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

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

[0116] The VMs 508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 506. Different embodiments of the instance of a virtual appliance 502 may be implemented on one or more of VMs 508, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

[0117] In the context of NFV, a VM 508 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 508, and that part of hardware 504 that executes that VM, be it hardware dedicated to that VM and/or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 508 on top of the hardware 504 and corresponds to the application 502.

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

[0119] Figure 9 shows a communication diagram of a host 602 communicating via a network node 604 with a UE 606 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE 112a of Figure 4 and/or UE 200 of Figure 2), network node (such as network node 110a of Figure 4 and/or network node 300 of Figure 3), and host (such as host 116 of Figure 4 and/or host 400 of Figure 4) discussed in the preceding paragraphs will now be described with reference to Figure 6.

[0120] Like host 400, embodiments of host 602 include hardware, such as a communication interface, processing circuitry, and memory. The host 602 also includes software, which is stored in or accessible by the host 602 and executable by the processing circuitry. The software includes a host application that may be operable to provide a service to a remote user, such as the UE 606 connecting via an over-the-top (OTT) connection 650 extending between the UE 606 and host 602. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection 650.

[0121] The network node 604 includes hardware enabling it to communicate with the host 602 and UE 606. The connection 660 may be direct or pass through a core network (like core network 106 of Figure 1) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet.

[0122] The UE 606 includes hardware and software, which is stored in or accessible by UE 606 and executable by the UE’s processing circuitry. The software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 606 with the support of the host 602. In the host 602, an executing host application may communicate with the executing client application via the OTT connection 650 terminating at the UE 606 and host 602. In providing the service to the user, the UE's client application may receive request data from the host's host application and provide user data in response to the request data. The OTT connection 650 may transfer both the request data and the user data. The UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT connection 650.

[0123] The OTT connection 650 may extend via a connection 660 between the host 602 and the network node 604 and via a wireless connection 670 between the network node 604 and the UE 606 to provide the connection between the host 602 and the UE 606. The connection 660 and wireless connection 670, over which the OTT connection 650 may be provided, have been drawn abstractly to illustrate the communication between the host 602 and the UE 606 via the network node 604, without explicit reference to any intermediary devices and the precise routing of messages via these devices.

[0124] As an example of transmitting data via the OTT connection 650, in step 608, the host 602 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE 606. In other embodiments, the user data is associated with a UE 606 that shares data with the host 602 without explicit human interaction. In step 610, the host 602 initiates a transmission carrying the user data towards the UE 606. The host 602 may initiate the transmission responsive to a request transmitted by the UE 606. The request may be caused by human interaction with the UE 606 or by operation of the client application executing on the UE 606. The transmission may pass via the network node 604, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 612, the network node 604 transmits to the UE 606 the user data that was carried in the transmission that the host 602 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 614, the UE 606 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 606 associated with the host application executed by the host 602.

[0125] In some examples, the UE 606 executes a client application which provides user data to the host 602. The user data may be provided in reaction or response to the data received from the host 602. Accordingly, in step 616, the UE 606 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input/output interface of the UE 606. Regardless of the specific manner in which the user data was provided, the UE 606 initiates, in step 618, transmission of the user data towards the host 602 via the network node 604. In step 620, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 604 receives user data from the UE 606 and initiates transmission of the received user data towards the host 602. In step 622, the host 602 receives the user data carried in the transmission initiated by the UE 606.

[0126] One or more of the various embodiments improve the performance of OTT services provided to the UE 606 using the OTT connection 650, in which the wireless connection 670 forms the last segment. More precisely, the teachings of these embodiments may improve the data rate and latency and thereby provide benefits such as reduced user waiting time, better responsiveness, and better QoE.

[0127] In an example scenario, factory status information may be collected and analyzed by the host 602. As another example, the host 602 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host 602 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host 602 may store surveillance video uploaded by a UE. As another example, the host 602 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs. As other examples, the host 602 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and/or transmitting data.

[0128] In some examples, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 650 between the host 602 and UE 606, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host 602 and/or UE 606. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 650 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 650 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 604. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host 602. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 650 while monitoring propagation times, errors, etc.

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

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

[0131] FIGURE 10A is a flowchart illustrating an example method in a target wireless device, according to certain embodiments. In particular embodiments, one or more steps of FIGURE 10A may be performed by UE 200 described with respect to FIGURE 5.

[0132] The method begins at step 1012, where the wireless device (e.g., UE 200) receives one or more carrier phase correction factors. The wireless device may receive the one or more carrier phase correction factors from a LMF or a base station.

[0133] In particular embodiments, each of the one or more carrier phase correction factors is associated with a transmission point, a validity time, a geographical area, a confidence metric, and/or a timestamp associated with a positioning measurement associated with the correction factor.

[0134] In particular embodiments, the one or more carrier phase correction factors comprise measurements performed by a PRU, and the wireless device determines a correction factor to apply based on the received measurement.

[0135] Additional examples of correction factors and receiving them are provided with respect to the embodiments and examples described herein.

[0136] At step 1014, the wireless device performs carrier phase-based positioning with differentiation based on the one or more carrier phase correction factors. Performing carrier phasebased positioning with differentiation based on the one or more carrier phase correction factors is described in more detail with respect to the embodiments and examples described herein. [0137] Modifications, additions, or omissions may be made to method 1000 of FIGURE 10A. Additionally, one or more steps in the method of FIGURE 10A may be performed in parallel or in any suitable order.

[0138] FIGURE 10B is a flowchart illustrating an example method in a wireless device functioning as a PRU, according to certain embodiments. In particular embodiments, one or more steps of FIGURE 10B may be performed by UE 200 described with respect to FIGURE 5.

[0139] The method begins at step 1052, where the wireless device (e.g., UE 200) determines one or more carrier phase correction factors. The determination may be based on measurements of positioning reference signals, as described in more detail above.

[0140] At step 1054, the wireless device transmits the one or more carrier phase correction factors to a network node (e.g., LMF, base station, etc.) for sharing with other wireless devices in the vicinity.

[0141] Modifications, additions, or omissions may be made to method 1050 of FIGURE 10B. Additionally, one or more steps in the method of FIGURE 10B may be performed in parallel or in any suitable order.

[0142] FIGURE 11 is a flowchart illustrating an example method in a network node, according to certain embodiments. In particular embodiments, one or more steps of FIGURE 11 may be performed by network node 300 described with respect to FIGURE 6 or a LMF.

[0143] The method begins at step 1112, where the network node (e.g., network node 300, LMF) obtains one or more carrier phase correction factors. For example, the network node may receive the one or more carrier phase correction factors from a PRU or a LMF.

[0144] In particular embodiments, each of the one or more carrier phase correction factors is associated with a transmission point, a validity time, a geographical area, a confidence metric, and/or a timestamp associated with a positioning measurement associated with the correction factor.

[0145] Additional examples of correction factors and receiving them are provided with respect to the embodiments and examples described herein.

[0146] At step 1114, the network node transmits the one or more carrier phase correction factors to a wireless device. The wireless device may use the one or more carrier phase correction factors when performing positioning. [0147] Modifications, additions, or omissions may be made to method 1100 of FIGURE 11. Additionally, one or more steps in the method of FIGURE 11 may be performed in parallel or in any suitable order.

[0148] The foregoing description sets forth numerous specific details. It is understood, however, that embodiments may be practiced without these specific details. In other instances, well-known circuits, structures and techniques have not been shown in detail in order not to obscure the understanding of this description. Those of ordinary skill in the art, with the included descriptions, will be able to implement appropriate functionality without undue experimentation. [0149] References in the specification to “one embodiment,” “an embodiment,” “an example embodiment,” etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to implement such feature, structure, or characteristic in connection with other embodiments, whether or not explicitly described.

[0150] Although this disclosure has been described in terms of certain embodiments, alterations and permutations of the embodiments will be apparent to those skilled in the art. Accordingly, the above description of the embodiments does not constrain this disclosure. Other changes, substitutions, and alterations are possible without departing from the scope of this disclosure, as defined by the claims below.

[0151] Some example embodiments are described below.

Group A Examples

Example 1. A method performed by a wireless device for position determination, the method comprising:

- receiving one or more carrier phase correction factors; and

- performing carrier phased-bad positioning with differentiation based on the one or more carrier phase correction factors.

Example 2. The method of the previous example, wherein receiving the one or more carrier phase correction factors comprises receiving the one or more carrier phase correction factors from a location management function (LMF).

Example 3. The method of any one of the previous examples, wherein receiving the one or more carrier phase correction factors comprises receiving the one or more carrier phase correction factors from a base station

Example 4. The method of any one of the previous examples, wherein each of the one or more carrier phase correction factors are associated with a transmission point.

Example 5. The method of any one of the previous examples, wherein each of the one or more carrier phase correction factors are associated with a validity time.

Example 6. The method of any one of the previous examples, wherein each of the one or more carrier phase correction factors are associated with a geographical area.

Example 7. A method performed by a wireless device for position determination, the method comprising:

- determining one or more carrier phase correction factors; and

- transmitting the one or more carrier phase correction factors to a network node for sharing with other wireless devices in the vicinity.

Example 8. A method performed by a wireless device, the method comprising:

- any of the wireless device steps, features, or functions described above, either alone or in combination with other steps, features, or functions described above.

Example 9. The method of the previous example, further comprising one or more additional wireless device steps, features or functions described above.

Example 10. The method of any of the previous examples, further comprising:

- providing user data; and

- forwarding the user data to a host computer via the transmission to the base station. Group B Examples

Example 11. A method performed by a base station for wireless device positioning, the method comprising:

- obtaining one or more carrier phase correction factors; and

- transmitting the one or more carrier phase correction factors to a target wireless device.

Example 12. The method of the previous example, wherein obtaining the one or more carrier phase correction factors comprises receiving the one or more carrier phase correction factors from a location management function (LMF).

Example 13. The method of any one of the previous examples, wherein each of the one or more carrier phase correction factors are associated with a transmission point.

Example 14. The method of any one of the previous examples, wherein each of the one or more carrier phase correction factors are associated with a validity time.

Example 15. The method of any one of the previous examples, wherein each of the one or more carrier phase correction factors are associated with a geographical area.

Example 16. A method performed by a base station, the method comprising:

- any of the steps, features, or functions described above with respect to base station, either alone or in combination with other steps, features, or functions described above.

Example 17. The method of the previous example, further comprising one or more additional base station steps, features or functions described above.

Example 18. The method of any of the previous examples, further comprising:

- obtaining user data; and

- forwarding the user data to a host computer or a wireless device. Group C Examples

Example 19. A mobile terminal comprising:

- processing circuitry configured to perform any of the steps of any of the Group A examples; and

- power supply circuitry configured to supply power to the wireless device.

Example 20. A base station comprising:

- processing circuitry configured to perform any of the steps of any of the Group B examples;

- power supply circuitry configured to supply power to the wireless device.

Example 21. A user equipment (UE) comprising:

- an antenna configured to send and receive wireless signals;

- radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry;

- the processing circuitry being configured to perform any of the steps of any of the Group A examples;

- an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry;

- an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and

- a battery connected to the processing circuitry and configured to supply power to the UE.

Example 22. A communication system including a host computer comprising:

- processing circuitry configured to provide user data; and

- a communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE),

- wherein the cellular network comprises a base station having a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the Group B examples.

Example 23. The communication system of the pervious example further including the base station.

Example 24. The communication system of the previous 2 examples, further including the UE, wherein the UE is configured to communicate with the base station.

Example 25. The communication system of the previous 3 examples, wherein:

- the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and

- the UE comprises processing circuitry configured to execute a client application associated with the host application.

Example 26. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:

- at the host computer, providing user data; and

- at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the base station performs any of the steps of any of the Group B examples.

Example 27. The method of the previous example, further comprising, at the base station, transmitting the user data.

Example 28. The method of the previous 2 examples, wherein the user data is provided at the host computer by executing a host application, the method further comprising, at the UE, executing a client application associated with the host application.

Example 29. A user equipment (UE) configured to communicate with a base station, the UE comprising a radio interface and processing circuitry configured to performs any of the previous 3 examples. Example 30. A communication system including a host computer comprising:

- processing circuitry configured to provide user data; and

- a communication interface configured to forward user data to a cellular network for transmission to a user equipment (UE),

- wherein the UE comprises a radio interface and processing circuitry, the UE’s components configured to perform any of the steps of any of the Group A examples.

Example 31. The communication system of the previous example, wherein the cellular network further includes a base station configured to communicate with the UE.

Example 32. The communication system of the previous 2 examples, wherein:

- the UE’s processing circuitry is configured to execute a client application associated with the host application.

Example 33. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:

- at the host computer, providing user data; and

- at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the UE performs any of the steps of any of the Group A examples.

Example 34. The method of the previous example, further comprising at the UE, receiving the user data from the base station.

Example 35. A communication system including a host computer comprising:

- communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station,

- wherein the UE comprises a radio interface and processing circuitry, the UE’s processing circuitry configured to perform any of the steps of any of the Group A examples. Example 36. The communication system of the previous example, further including the UE.

Example 37. The communication system of the previous 2 examples, further including the base station, wherein the base station comprises a radio interface configured to communicate with the UE and a communication interface configured to forward to the host computer the user data carried by a transmission from the UE to the base station.

Example 38. The communication system of the previous 3 examples, wherein:

- the processing circuitry of the host computer is configured to execute a host application; and

- the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data.

Example 39. The communication system of the previous 4 examples, wherein:

- the processing circuitry of the host computer is configured to execute a host application, thereby providing request data; and

- the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data in response to the request data.

Example 40. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:

- at the host computer, receiving user data transmitted to the base station from the UE, wherein the UE performs any of the steps of any of the Group A examples.

Example 41. The method of the previous example, further comprising, at the UE, providing the user data to the base station.

Example 42. The method of the previous 2 examples, further comprising:

- at the UE, executing a client application, thereby providing the user data to be transmitted; and - at the host computer, executing a host application associated with the client application.

Example 43. The method of the previous 3 examples, further comprising:

- at the UE, executing a client application; and

- at the UE, receiving input data to the client application, the input data being provided at the host computer by executing a host application associated with the client application,

- wherein the user data to be transmitted is provided by the client application in response to the input data.

Example 44. A communication system including a host computer comprising a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, wherein the base station comprises a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the Group B examples.

Example 45. The communication system of the previous example further including the base station.

Example 46. The communication system of the previous 2 examples, further including the UE, wherein the UE is configured to communicate with the base station.

Example 47. The communication system of the previous 3 examples, wherein:

- the processing circuitry of the host computer is configured to execute a host application;

- the UE is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer.

Example 48. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:

- at the host computer, receiving, from the base station, user data originating from a transmission which the base station has received from the UE, wherein the UE performs any of the steps of any of the Group A examples.

Example 49. The method of the previous example, further comprising at the base station, receiving the user data from the UE.

Example 50. The method of the previous 2 examples, further comprising at the base station, initiating a transmission of the received user data to the host computer.

Appendix A

Title: Improved accuracy based on NR carrier phase measurement

Introduction

GNSS carrier phase positioning has been used successfully for centimeter-accuracy positioning but is limited to outdoor applications. The technique was studied during the Rel. 18 SI. The objective of this work item as stated by the WID is:

This Appendix presents proposals in line with this objective.

Measurement definition

Carrier phase of the first path and additional paths

The Rel. 18 SI concluded that multipath/NLOS deteriorates the performance of carrier phase positioning, and it is necessary to consider multipath mitigation for NR carrier phase positioning [6], We agree with the following multipath mitigation methods, suggested during the SI:

- Identification and separation of the first path and other paths.

- Reporting of the carrier phase of the first path, and optionally, the additional paths.

- The use of LOS/NLOS indication for the carrier phase measurements.

- NOTE: Rel- 17 LOS/NLOS indicator can be considered as a starting point.

- The report of other channel information, such as existing RSRP/RSRPP.

A carrier phase measurement shall be defined per path.

The carrier phase of the first path shall be reported and optionally additional paths.

We note that the mitigation methods that use LOS/NLOS indication and RSRP/RSRPP are already in place for DL-TDOA, UL-TDOA, so there is no additional specification impact when carrier phase measurements are reported together with these methods.

There are different practical methods in both time- and frequency-domain to perform a pathspecific carrier phase measurement. In short, the receiver estimates the channel impulse response h(t) and estimate the delay of the line-of sight path, f ₀. Then, the carrier phase is given by

The carrier phase measurement can be obtained from the argument of the estimated channel impulse response at the delay of the LOS peak.

In line with the reasoning above, we propose the measurement definition below as a starting point for discussions. The proposal is formulated for the DL PRS reference signal, but a similar definition is also needed for the UL SRS for positioning signal.

Define a new measurement called DL PRS reference signal carrier path phase (DL PRS-RSCPP). Define a new measurement called UL SRS reference signal carrier path phase (UL SRS-RSCPP).

Reporting absolute or relative phase measurement

One question is whether the absolute carrier phase measurement should be reported, or a relative phase difference with respect to some reference node. In the first case, both measurements will include an Rx initial phase offset, while in the second case this offset has been cancelled. However, with the first approach LMF can anyway compute the phase difference to cancel out this offset, hence we consider these alternatives to be equivalent.

Either the absolute carrier phase can be reported, or the relative phase difference with respect to some reference node. The options are equivalent.

One or multiple measurement per frequency layer

During the SI, some companies suggested to use several phase measurements corresponding to different subcarriers or parts of the bandwidth. The reasoning was that several measurements at different frequencies can be combined into virtual frequencies with much longer wavelength, hence facilitate the integer ambiguity resolution.

In a previous contribution we showed that reporting the carrier phase of individual subcarriers does not add any information compared to reporting the central carrier phase and the estimated time-of-arrival of the reference signal. In fact, the phase of subcarriers a, <p_a, can be obtained as 0 a 0c 27 TQA0, where <p_c is the estimated phase of the center carrier, fo' the estimated TOA and Af = f_c — f_a, the frequency difference between them.

We note that there is no proven technical benefit from using carrier phase measurements at different subcarriers together with TDOA compared to using only the phase of the central carrier with TDOA.

Based on these technical considerations and in the interest to minimize the specification impact according to the WID, we propose that the phase measurement should be defined for the central carrier of the bandwidth only.

A phase measurement shall be defined for the central carrier frequency, not for individual subcarriers or parts of the bandwidth. Measurement reporting

Stand-alone carrier phase reporting or joint reporting with TDOA

We propose that carrier phase measurements should be reported jointly with either DL-TDOA, UL-TDOA or Multi-RTT but not as a stand-alone procedure. This can be motivated from an accuracy or technical feasibility point of view:

• During the study item, most companies evaluated joint positioning using carrier phase measurements and some other positioning method. The integer ambiguity problem simplifies significantly if e.g. DL-TDOA can be employed to obtain a first coarse position estimate, for instance to reduce the search space of a multi-hypothesis integer resolution algorithm.

• In other cases, companies simply limited the integer ambiguity problem to the true integer vector N plus some uncertainty margin. The technical feasibility of a stand-alone solution without prior information of the UE position has not been demonstrated during the SI.

Additionally, we have already seen that carrier-phase measurements of specific paths requires time-of-arrival estimation. Consequently, there is little or no additional computations needed to obtain those as well. It makes no sense that a receiver computes time-of-arrival and carrier phase for a path and then only reports the carrier phase measurement.

Finally, the specification impact for joint reporting (with DL-TDOA, UL-TDOA) is minimal while a stand-alone solution would require a much larger specification effort that is not supported by the WID. Joint reporting of carrier phase measurements with existing positioning measurements can probably be introduced with a small specification impact. The existing positioning measurement reports often has a structure where the measurement is defined for a specific path. It will be natural to extend this structure to include the carrier phase of specific path.

The existing positioning measurement reports often has a structure where the measurement is defined for a specific path. It will be natural to extend this structure to include the carrier phase of specific path.

Add support to report DL PRS RSCPP for the first path and additional paths with the DL-TDOA positioning method.

Add support to report UL SRS RSCPP for the first path and additional paths with the UL-TDOA positioning method.

Assistance information for double differentiation

Downlink UE-based

The double-differentiation technique was evaluated during the SI, often successfully. Differential corrections is a corner-stone for high-accuracy GNSS, hence we think that assistance data that enables double-differentiation or phase calibration need to be supported by the standard. For UE- based CPP we propose to provide phase correction factors for each TRP and to each UE. Provide phase correction factors for each TRP to each UE.

During the SI, many companies obtained phase correction factors from a nearby PRU. It can also be possible that the network has its own reference units or that there can be some procedure among TRPs to estimate their initial phase-offsets. We think that it is important that the standard supports the provisioning phase correction factors but is neutral to how they were obtained. Phase correction factors shall be neutral regarding how they were obtained.

In GNSS the notion of virtual reference station has proven to enhance the accuracy: A virtual reference station is created nearby the UE with measurements that are obtained by interpolation between different (physical) reference stations. Proposal 10 has the additional advantage that it can be used for virtual reference station. Moreover, if there are multiple reference units and their measurements are inconsistent, then LMF can select the most trustworthy or relevant corrections and provide those to the UE.

Phase correction factors may have a limited validity time. The time-aspect was not sufficiently studied during the SI, but from GNSS RTK we know that real-time streaming of correction factors is needed to reach the best accuracy.

Phase corrections have a limited validity time. The time-variability was not studied during the Rel.

18 Positioning SI.

Consequently, we propose that it should be possible to provide updated correction factor with variable frequency. Whenever a new set of correction factors are available to LMF, then these can be sent to the UE.

It should be possible to provide a UE with updated correction factor with variable frequency.

To reduce the signaling overhead, LMF can skip sending an update if the new correction factors are only marginally different compared to the previous set of correction factors. There can be a threshold specified that defines when updated correction factors need to be sent to the UE. For applications that are less latency-critical another method to reduce the signaling overhead is to provide phase correction factors in batches where the absolute validity time of each set of correction factors is specified.

Investigate how phase correction factors can be provided in a resource efficient way.

Downlink UE-assisted

We don’t see any additional impact for UE-assisted downlink carrier phase-based positioning.

For this case, LMF can collect carrier phase measurements from the Target UE, from PRU UEs or other sources and use them to perform double-differentiation.

Uplink NG-RAN Node-assisted

We don’t see any additional impact for uplink NG-RAN node-assisted carrier phase-based positioning. In this case, LMF can request the Target UE and PRU UEs to transmit UL-SRS for positioning and network TRPs measure and report the carrier phase (and RSTD). This will enable LMF to perform double-differentiation,

Assistance data for error source mitigation

Antenna phase response and antenna phase center

Some companies have raised a concern about antenna phase response or phase center offset (PCO). Ideally, the antenna phase center is aligned with the physical antenna reference point (ARP) or at least fixed. A PCO error appear at both the transmitter and the receiver, it depends on AOA/AOD, frequency. It can also vary during live operation [8], During the Rel. 18 Positioning SI the problem didn’t get much attention and no practical mitigation technique was proposed.

No practical technique to mitigate antenna phase center offset at the Tx and Rx was proposed during the study item.

ARP errors

The study item found that a main source of error is ARP errors (in both TRPs and PRUs). For some cases, double differentiation can mitigate the error but as shown in [9], the ARP errors can impact the Target UE and a PRU differently and then the errors will not be cancelled out by taking the differential. In our view, ARP errors should be ensured minimal by the deployment procedure.

Carrier phase measurement differentials and Rx/Tx branches

The SI found that differential techniques can be used to cancel out initial phases of both the transmitter and the receiver. However, the initial phase of the transmitter depends on the Tx-branch and the initial phase of the receiver depends on the Rx-branch. Consequently, it must be ensured that carrier phase measurement differentials are performed for consistent Rx/Tx branches. Moreover, the notion of Rx- and Tx- timing error groups (TEGs) was introduced during 3 GPP Release 18 to handle the fact that timing measurements performed with different antenna panels may not be comparable. The study item on carrier phase measurements did not consider this aspect, but we expect similar limitations for carrier phase measurements.

Carrier phase measurement differentials (single- or double-differentials) may not be useful on measurements performed with inconsistent Rx/Tx branches or Rx/Tx TEGs.

Conclusion

In the previous sections we made the following observations:

Observation 1 The carrier phase measurement can be obtained from the argument of the estimated channel impulse response at the delay of the LOS peak.

Observation 2 Either the absolute carrier phase can be reported, or the relative phase difference with respect to some reference node. The options are equivalent.

Observation 3 The existing positioning measurement reports often has a structure where the measurement is defined for a specific path. It will be natural to extend this structure to include the carrier phase of specific path.

Observation 4 Phase corrections have a limited validity time. The time-variability was not studied during the Rel. 18 Positioning SI.

Observation 5 No practical technique to mitigate antenna phase center offset at the Tx and Rx was proposed during the study item.

Observation 6 Carrier phase measurement differentials (single- or double-differentials) may not be useful on measurements performed with inconsisten Rx/Tx branches or Rx/Tx TEGs.

Based on the discussion in the previous sections we propose the following:

Proposal 1 A carrier phase measurement shall be defined per path.

Proposal 2 The carrier phase of the first path shall be reported and optionally additional paths.

Proposal 3 Define a new measurement called DL PRS reference signal carrier path phase (DL PRS-RSCPP).

Proposal 4 Define a new measurement called UL SRS reference signal carrier path phase (UL SRS-RSCPP).

Proposal 5 A phase measurement shall be defined for the central carrier frequency, not for individual subcarriers or parts of the bandwidth.

Proposal 6 Add support to report DL PRS RSCPP for the first path and additional paths with the DL-TDOA positioning method.

Proposal 7 Add support to report UL SRS RSCPP for the first path and additional paths with the UL-TDOA positioning method.

Proposal 8 Provide phase correction factors for each TRP to each UE.

Proposal 9 Phase correction factors shall be neutral regarding how they were obtained.

Proposal 10 It should be possible to provide a UE with updated correction factor with variable frequency.

Proposal 11 Investigate how phase correction factors can be provided in a resource efficient way. References

3GPP RP -213561, New SID on Study on expanded and improved NR positioning, 3GPP TSG RAN Meeting #94e, Dec. 6-17, 2021

3GPP TR 38.901 V17.0.0 (2022-03) Study on channel model for frequencies from 0.5 to 100 GHz (Release 17)

Paul de Jonge and Christian Tiberius, The LAMBDA method for integer ambiguity estimation: implementation aspects. Publications of the Delft Geodetic Computing Centre, 1996.

Jay A. Farrel, Aided Navigation. Me Graw Hill, 2006

3 GPP RP-223549, New WID on Expanded and Improved NR Positioning, 3 GPP TSG RAN Meeting #98-e, Dec. 12-16, 2022

3GPP TR 38.859 V18.0.0, Study on expanded and improved NR positioning (Release 18)

Rl-2212515, Improved accuracy based on NR carrier phase measurements, Ericsson. 3GPP TSG- RAN WG1 #111

Rl-2211312, Views on improved accuracy based on NR carrier phase measurements, Nokia. 3GPP TSG RAN WG1#111

Rl-2212124, Phase Measurements in NR Positioning, Qualcomm Incorporated. 3GPP TSG RAN

WG1#111

Claims

1. A method performed by wireless device for position determination, the method comprising: receiving (1012) one or more carrier phase correction factors; and performing (1014) carrier phase-based positioning with differentiation based on the one or more carrier phase correction factors.

2. The method of claim 1, wherein receiving the one or more carrier phase correction factors comprises receiving the one or more carrier phase correction factors from a location management function, LMF.

3. The method of claim 1, wherein receiving the one or more carrier phase correction factors comprises receiving the one or more carrier phase correction factors from a base station.

4. The method of any one of claims 1-3, wherein each of the one or more carrier phase correction factors is associated with a transmission point.

5. The method of any one of claims 1-4, wherein the one or more carrier phase correction factors are associated with a validity time.

6. The method of any one of claims 1-5, wherein the one or more carrier phase correction factors are associated with a geographical area.

7. The method of any one of claims 1-6, wherein the one or more carrier phase correction factors are associated with a confidence metric.

8. The method of any one of claims 1-7, wherein the one or more carrier phase correction factors are associated with a timestamp associated with a positioning measurement associated with the correction factor.

9. The method of any one of claims 1-8, wherein the one or more carrier phase correction factors comprise measurements performed by a positioning reference unit (PRU), and the wireless device determines a correction factor to apply when performing carrier phase-based positioning based on the received measurement performed by the PRU.

10. A wireless device (200) comprising processing circuitry (202) operable to: receive one or more carrier phase correction factors; and perform carrier phase-based positioning with differentiation based on the one or more carrier phase correction factors.

11. The wireless device of claim 10, wherein the processing circuitry is operable to receive the one or more carrier phase correction factors by receiving the one or more carrier phase correction factors from a location management function, LMF.

12. The wireless device of claim 10, wherein the processing circuitry is operable to receive the one or more carrier phase correction factors by receiving the one or more carrier phase correction factors from a base station.

13. The wireless device of any one of claims 10-12, wherein each of the one or more carrier phase correction factors is associated with a transmission point.

14. The wireless device of any one of claims 10-13, wherein the one or more carrier phase correction factors are associated with a validity time.

15. The wireless device of any one of claims 10-14, wherein the one or more carrier phase correction factors are associated with a geographical area.

16. The wireless device of any one of claims 10-15, wherein the one or more carrier phase correction factors are associated with a confidence metric.

17. The wireless device of any one of claims 10-16, wherein the one or more carrier phase correction factors are associated with a timestamp associated with a positioning measurement associated with the correction factor.

18. The wireless device of any one of claims 10-17, wherein the one or more carrier phase correction factors comprise measurements performed by a positioning reference unit (PRU), and the wireless device determines a correction factor to apply when performing carrier phase-based positioning based on the received measurement performed by the PRU.

19. A method performed by a network node for wireless device positioning, the method comprising: obtaining (1112) one or more carrier phase correction factors; and transmitting (1114) the one or more carrier phase correction factors to a wireless device.

20. The method of claim 19, wherein obtaining the one or more carrier phase correction factors comprises receiving the one or more carrier phase correction factors from a positioning reference unit, PRU.

21. The method of claim 19, wherein obtaining the one or more carrier phase correction factors comprises receiving the one or more carrier phase correction factors from a location management function, LMF.

22. The method of any one of claims 19-21, wherein each of the one or more carrier phase correction factors are associated with a transmission point.

23. The method of any one of claims 19-22, wherein each of the one or more carrier phase correction factors are associated with a validity time.

24. The method of any one of claims 19-23, wherein each of the one or more carrier phase correction factors are associated with a geographical area.

25. The method of any one of claims 19-24, wherein each of the one or more carrier phase correction factors are associated with a confidence metric.

26. The method of any one of claims 19-25, wherein the one or more carrier phase correction factors are associated with a timestamp associated with a positioning measurement associated with the correction factor.

27. A network node (300) comprising processing circuitry (302), the processing circuitry operable to: obtain one or more carrier phase correction factors; and transmit the one or more carrier phase correction factors to a wireless device.

28. The network node of claim 27, wherein the processing circuitry is operable to obtain the one or more carrier phase correction factors by receiving the one or more carrier phase correction factors from a positioning reference unit, PRU.

29. The network node of claim 27, wherein the processing circuitry is operable to obtain the one or more carrier phase correction factors by receiving the one or more carrier phase correction factors from a location management function, LMF.

30. The network node of any one of claims 27-29, wherein each of the one or more carrier phase correction factors are associated with a transmission point.

31. The network node of any one of claims 27-30, wherein each of the one or more carrier phase correction factors are associated with a validity time.

32. The network node of any one of claims 27-31, wherein each of the one or more carrier phase correction factors are associated with a geographical area.

33. The network node of any one of claims 27-32, wherein each of the one or more carrier phase correction factors are associated with a confidence metric.

34. The network node of any one of claims 27-33, wherein the one or more carrier phase correction factors are associated with a timestamp associated with a positioning measurement associated with the correction factor.