WO2024175799A1

WO2024175799A1 - Reporting error group consistency for joint carrier phase measurement reporting

Info

Publication number: WO2024175799A1
Application number: PCT/EP2024/054711
Authority: WO
Inventors: Siva Muruganathan; Gustav Lindmark
Original assignee: Telefonaktiebolaget LM Ericsson AB
Current assignee: Telefonaktiebolaget LM Ericsson AB
Priority date: 2023-02-24
Filing date: 2024-02-23
Publication date: 2024-08-29
Anticipated expiration: 2025-08-24

Abstract

A communication device can measure (520) a downlink, DL, reference signal time difference, RSTD, and a corresponding DL carrier phase measurement on a DL positioning reference signal, PRS, received from the first network node The communication device further transmits (570) a joint report to second network node, the joint reporting including at least one of: 1) an indication of the DL RSTD and the corresponding DL carrier phase measurement and an indication of an error group identifier for the DL RSTD and the corresponding DL carrier phase measurement; and 2) an indication of a reference time and a reference phase corresponding to a third network node and an indication of an error group identifier of the reference time and the reference phase.

Description

REPORTING ERROR GROUP CONSISTENCY FOR JOINT CARRIER PHASE MEASUREMENT REPORTING

TECHNICAL FIELD

The present disclosure is related to wireless communication systems and more particularly to reporting error group consistency for joint carrier phase measurement reporting.

BACKGROUND

FIG. 1 illustrates an example of a new radio (“NR”) network (e.g., a 5th Generation (“5G”) network) including a 5G core (“5GC”) network 130, network nodes 120a-b (e.g., 5G base station (“gNB”)), multiple communication devices 110 (also referred to as user equipment (“UE”)).

FIG. 2 illustrates an example of NR architecture for supporting NR positioning. In this example, the location node in NR is a location management function (“LMF”). There are also interactions between the location node and the gNodeB via the NR positioning protocol A (“NRPPa”). The interactions between the gNodeB and the device is supported via the Radio Resource Control (“RRC”) protocol. In additional or alternative examples, the gNB and ng-eNB may not both be present. In additional or alternative examples, when both the gNB and ng-eNB are present the NG-C interface is only present for one of them.

NR currently supports the following radio access technology (“RAT”) dependent positioning procedures: 1) Downlink time-difference-of-arrival (“DL-TDOA”); 2) Multi-round trip time (“RTT”); 3) Uplink time-difference-of-arrival (“UL-TDOA”); 4) Downlink angle-of- departure (“DL-AoD”); 5) Uplink angle-of-arrival (“UL-AoA”); and 6) NR enhanced cell identifier (“NR-ECID”).

The DL TDOA positioning procedure makes use of the downlink (“DL”) reference signal time difference (“RSTD”) (and optionally DL positioning reference signal (“PRS”) reference signal received power (“RSRP”)) of downlink signals received from multiple transmission points (“TPs”), at the 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.

The Multi-RTT positioning procedure makes use of the UE reception (“Rx”)-transmission (“Tx”) measurements and DL PRS RSRP of downlink signals received from multiple transmission/reception points (“TRPs”), measured by the UE and the measured gNB Rx-Tx measurements and UL sounding reference signal (“SRS”)-RSRP at multiple TRPs of uplink signals transmitted from UE.

The UL TDOA positioning procedure makes use of the UL TDOA (and optionally UL SRS-RSRP) at multiple 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.

The DL AoD positioning procedure makes use of 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.

The UL AoA positioning procedure makes use of the measured azimuth and zenith of arrival at multiple reception points (“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.

NR-ECID positioning refers to techniques that use additional UE measurements and/or NR radio resource and other measurements to improve the UE location estimate.

The positioning modes can be categorized into three areas: 1) UE-Assisted; 2) UE- Based; and 3) Standalone. UE-Assisted can refer to the UE performing measurements with or without assistance from the network and sending these measurements to the evolved serving mobile location center (“E-SMLC”) where the position calculation may take place. UE-Based can refer to the UE performing measurements and calculating its own position with assistance from the network. Standalone can refer to the UE performing measurements and calculating its own without network assistance.

SUMMARY

According to some embodiments, a method of operating a communication device is provided. The communication device is in a communications network that includes a first network node, a second network node, and a third network node. The method includes measuring a downlink, DL, reference signal time difference, RSTD, and a corresponding DL carrier phase measurement on a DL positioning reference signal, PRS, received from the first network node. The method further includes transmitting a joint report to second network node, the joint reporting including at least one of: a first combination and a second combination. The first combination including an indication of the DL RSTD and the corresponding DL carrier phase measurement and an indication of an error group identifier for the DL RSTD and the corresponding DL carrier phase measurement. The second combination including an indication of a reference time and a reference phase corresponding to a third network node and an indication of an error group identifier of the reference time and the reference phase.

According to other embodiments, a method of operating a first network node is provided. The first network node is in a communications network that includes a communication device and a second network node. The method includes measuring an uplink, UL, relative time of arrival, RTOA, and a corresponding UL carrier phase measurement on a UL sounding reference signal, SRS, received from the communication device. The method further includes transmitting a joint report to second network node, the joint reporting including: an indication of the UL RTOA and the corresponding UL carrier phase measurement; and an indication of an error group identifier for the UL RTOA and the corresponding UL carrier phase measurement.

According to other embodiments, a method of operating a second network node is provided. The second network node is in a communications network that includes a communication device and a first network node. The method includes receiving a joint report including: an indication of measurement; and an indication of an error group identifier for the measurement. The method includes determining whether to combine the measurement with other measurements based on the error group identifier.

According to other embodiments, a communication device, network node, TRP, LMF, computer program, computer program product, or system is provided to perform one of the above methods.

Certain embodiments may provide one or more of the following technical advantages. In some embodiments, a positioning server node (e.g., an LMF) knows which joint carrier phase and timing-based measurements can be combined to position a UE. In some examples, the innovations are proposed for both UL and DL joint reports.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are included to provide a further understanding of the disclosure and are incorporated in and constitute a part of this application, illustrate certain nonlimiting embodiments of inventive concepts. In the drawings:

FIG. l is a schematic diagram illustrating an example of a 5^th generation (“5G”) network;

FIG. 2 is a block diagram illustrating an example of NR architecture for supporting positioning in NR; FIG. 3 is a schematic illustrating an example of a carrier phase measurement subject to a transmission phase offset and a receive phase offset in accordance with some embodiments;

FIG. 4 is a schematic illustrating an example of assumptions for differentiation schemes in accordance with some embodiments;

FIG. 5 is a flow chart illustrating an example of operations performed by a communication device in accordance with some embodiments;

FIG. 6 is a flow chart illustrating an example of operations performed by a first network node in accordance with some embodiments;

FIG. 7 is a flow chart illustrating an example of operations performed by a second network node in accordance with some embodiments;

FIG. 8 is a block diagram of a communication system in accordance with some embodiments;

FIG. 9 is a block diagram of a user equipment in accordance with some embodiments;

FIG. 10 is a block diagram of a network node in accordance with some embodiments;

FIG. 11 is a block diagram of a virtualization environment in accordance with some embodiments; and

DETAILED DESCRIPTION

Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art, in which examples of embodiments of inventive concepts are shown. Inventive concepts may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of present inventive concepts to those skilled in the art. It should also be noted that these embodiments are not mutually exclusive. Components from one embodiment may be tacitly assumed to be present/used in another embodiment.

Global Navigation Satellite System (“GNSS”) carrier phase positioning has been used successfully for centimeter-level accuracy positioning but is limited to outdoor applications. It can be desirable to specify physical layer measurements and signaling to support new radio (“NR”) carrier phase positioning. In some examples, it can be advantageous to specify physical layer measurements and signaling to support NR downlink (“DL”) and uplink (“UL”) carrier phase positioning for user equipment (“UE”) (also referred to herein as a communication device)-based, UE-assisted, and next generation radio access network (“NG-RAN”) node assisted positioning. Existing DL positioning reference signals (“PRSs”) and UL sounding reference signals (“SRSs”) for positioning are used for NR carrier phase measurements. In additional or alternative examples, measurements can be limited to a single carrier/PFL. In additional or alternative examples, new core requirements may be specified and the impact on the existing RAN4 specification, including RRM measurements without measurement gaps in connected and inactive mode (including PRS measurement period/reporting) and procedures may be specified.

In some examples, a link can be formed with one transmitter and one receiver. The transmitted pass-band signal can be given by:

where s(t) denotes the baseband signal and f_c denotes the carrier frequency. The term <p₀ is an offset due to Tx imperfect synchronization, it includes the RF phase-difference compared to an ideal oscillator.

In additional or alternative examples, line-of-sight (“LOS”) conditions and no multipath can be assumed. The channel is h(t) = <5(t - r₀), where T₀ = dfc 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:

After down-conversion, the received baseband signal is

where the term <p₁ is an offset due to Rx imperfect synchronization, it includes the RF phasedifference compared to an ideal oscillator. A carrier phase measurement of this transmission will return the phase

Above, the term 2nN corresponds to a modulus operation such that the measured phase is in the range [0, 2TT] , In order to attain accurate positioning with carrier phase measurements, the integer N needs to be resolved. The ambiguity caused by the integer value N in Equation (1) is called the integer ambiguity problem.

FIG. 3 illustrates an example of a carrier phase measurement subject to a transmission phase offset and a receive phase offset. Herein the terms “Tx phase offset” or “transmission phase offset” for _O, and the terms “Rx phase offset” or “receive phase offset” for <p₁ are used.

Joint carrier phase reporting with timing-based positioning measurements are described below. In some examples, it is proposed to report carrier phase measurements jointly with one of the timing-based measurements such as DL reference signal time difference (“RSTD”) measurements and reception (“Rx”)-transmission (“Tx”) measurements. The timing-based procedures (e.g., DL TDOA, Multi-RTT) can be used to first obtain a coarse position estimate, and then use the coarse position estimate to simplify the integer ambiguity problem significantly. For example, by employing the coarse positioning estimate the search space for a multi-hypothesis integer resolution algorithm can be reduced.

Differentiation schemes are described below. For carrier-phase based positioning, it is the transmission delay T₀ iⁿ Equation (1) which 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.

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 <p₁ can be canceled out if the phase difference between transmitters is computed, e.g. differentiating Eq. (1) between the transmitters.

As an example, consider a UE measuring the phase

on a DL PRS reference signal from TRP 1 and the phase

on a DL PRS from TRP 2. If we consider TRP1 as a reference TRP, then the carrier phase-difference measurement of TRP 2 is given by

Ad/²) = cp^LcpL) (2)

In fact, in the ongoing discussions in 3GPP Rel. 18 WI on positioning enhancements, some companies propose to introduce reporting of the phase difference measurement (2) rather than the direct phase measurement of each TRP (1).

If the term _O (which is due to the transmitter RF offset) is the same for carrier phase measurements performed by multiple receivers from one transmitter, then _O can be canceled out if the phase difference between receivers is computed, e.g. differentiating Eq. (1) between the receivers.

By combining the two differentiation methods, a double-differentiation scheme can be obtained which results in that all the unknown offsets are cancelled out.

In some examples, a basic differentiation scheme presented has two assumptions.

Assumption 1 : For one specific receiver, the Rx phase offset is the same for received signals from all transmitters. Assumption 2: For one specific transmitter, the Tx phase offset is the same for transmitted signals to all receivers.

FIG. 4 illustrates an example of assumptions for differentiation schemes. The Rx phase offset is the same for signals from all transmitters (i and j). The transmission phase offset the same for all receivers (k and K).

Timing error groups are described below. In some examples, the accuracy enhancements for time-based procedures (e.g., multi-RTT, DL TDOA, UL TDOA) have been proposed to mitigate timing errors, which resulted in the introduction of the timing error group (“TEG”) concept. The principle stems from the observation that signals transmitted or received on different beams may be carried over different RF chains or different antenna panels. Even after calibration in the UE/TRP implementation, there will always be a residual timing error in transmission and reception timing between signals transmitted over these different RF chains / antenna panels. The following types of TEGs are captured in 3GPP TS 38.214 V17.4.0.

Timing Error Group(s) (TEG(s)) at UE side are defined as follows.

UE Rx TEG is associated with one or more DL measurements, which have the Rx timing error difference within a certain margin.

UE RxTx TEG is associated with one or more UE Rx-Tx time difference measurements, which have the 'Rx timing errors+Tx timing errors' difference within a certain margin.

UE Tx TEG is associated with the transmissions of one or more UL SRS resources for the positioning purpose, which have the Tx timing error difference within a certain margin.

If two DL measurements are associated with the same UE Rx TEG, then the two DL measurements have a Rx timing error difference that is within a certain UE Rx TEG margin. Hence, these two DL measurements may be combined when estimating the position of the UE as the node computing the position (e.g., LMF) knows that the Rx timing error difference is within the margin.

If two UE Rx-Tx time difference measurements are associated with the same UE RxTx TEG, then the two UE Rx-Tx time difference measurements have a “Rx timing error+Tx timing error‘ difference within a UE RxTx TEG margin. Hence, these UE Rx-Tx time difference measurements may be combined when estimating the position of the UE as the node computing the position (e.g., LMF) knows that the “Rx timing error+Tx timing error‘ difference is within the margin.

If two UL SRS transmissions are associated with the same UE Tx TEG, then the two UL SRS transmissions have a Tx timing error difference that is within a certain UE Tx TEG margin. Hence, UL measurements made by one or more TRPs on these two UL SRS transmissions may be combined when estimating the position of the UE as the node computing the position (e.g., LMF) knows that the Tx timing error difference between the two UL SRS transmissions is within the margin. gNB Rx TEGs are defined similar to above when gNB is performing UL measurements. gNB Rx-Tx TEG are defined similar to above when gNB is performing gNB Rx-Tx time difference measurements. gNB Tx TEGs are defined for the similar to above when gNB is transmitting DL PRS in the downlink. In some examples, it is briefly mentioned that two carrier phase measurements need to be performed using consistent Rx branches for them to be compatible (e.g., used together for estimating position of the UE).

In additional or alternative examples, a notion of phase error groups (“PEG”) for two carrier phase measurements is discussed. If two carrier phase measurements belong to the same Rx PEG, then it means that the Rx phase error difference within a margin. Hence, two carrier phase measurements belonging to the same Rx PEG can be used together for estimating position of the UE.

Two DL measurements associated with the same UE Rx TEG are likely measured using the same Rx branch or two well calibrated Rx branches in order to ensure that the timing error difference between the two DL measurements are within the UE Rx TEG margin.

Even for two timing-based measurements done within the same Rx chain, the timing error difference between the two measurements may drift with time due to group delay variations due to temperature etc. Hence, the UE Rx TEGs may be different for two DL measurements done using the same Rx chain if the two DL measurements are done at different times.

In general, the group delay associated with an Rx chain may vary slowly with time. In comparison, phase measurements made using an Rx chain may vary more due to various reasons such as DRX, frequency adjustment, switching between Rx and Tx, etc. Furthermore, to ensure good accuracy for positioning, finer margins (compared to existing TEG margin values defined in 3GPP TS 38.133 V18.0.0) may need to be used to ensure phase difference between two carrier phase measurements are within those margins.

There currently exist certain challenges. In some examples, time/phase error handling are discussed at a high level in the context of two carrier phase measurements. However, how to handle time/phase errors when carrier phase measurements are jointly reported with timingbased measurements such as DL RSTD measurements, Rx-Tx measurements are not addressed. Since joint reporting of carrier phase measurements with timing-based measurements is needed to resolve the integer ambiguity problem, how to handle time/phase errors for this case of joint reporting is an open problem to be solved.

Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. In some embodiments, for both UL and DL, one TPEG is associated with a joint carrier phase measurement and timing-based measurement. Two joint reports can be combined to perform positioning of a UE if the two joint reports have the same TPEG ID.

In additional or alternative embodiments, for both UL and DL, one TEG and one PEG are associated with a j oint carrier phase measurement and timing-based measurement. Two j oint reports can be combined to perform positioning of a UE if the two joint reports have the same TEG ID and the same PEG ID.

Various embodiments herein describe how to handle time/phase error differences for the case when carrier phase measurement is jointly reported with timing-based measurements.

Embodiments associated with reporting a single UE Rx error group is with two different margins are described below. The carrier phase measurements described in this embodiment are (1) DL carrier phase measurements or (2) DL carrier phase difference measurements.

In additional or alternative embodiments, when carrier phase measurement is jointly reported with DL RSTD measurement, then two margins are defined within the same error group. The error group may be called a timing error group (“TEG”) or a joint timing-phase error group (“TPEG”). A first margin is defined as the timing error margin which is used to indicate if the timing error difference between two DL RSTD measurements are within this timing error margin. A second margin is defined as the phase error margin which is used to indicate if the phase error difference between two carrier phase measurements are within this phase error margin.

In additional or alternative embodiments, the phase error margin can be derived from the timing error margin according to a predefined conversion formula.

In additional or alternative embodiments, using the two margins, two different jointly reported carrier phase measurements and DL RSTD measurements are associated with the same receive error group (e.g., Rx TPEG or Rx TEG) if both the following conditions are satisfied: 1) If the Rx timing error difference between a first DL RSTD measurement in the first joint report and a second DL RSTD measurement in the second joint report are within the first margin (e.g., the timing error margin); and 2) If the Rx phase error difference between a first carrier phase measurement in the first joint report and a second carrier phase measurement in the second joint report are within the second margin (e.g., the phase error margin).

In additional or alternative embodiments, if two joint reports have the same receive error group (e.g., Rx TPEG or RX TEG), then the two joint reports can be used together for estimating the position of the UE.

In additional or alternative embodiments, the UE reports an identifier associated with the Rx error group (e.g., Rx TPEG ID or Rx TEG ID) along with the joint report to the LMF via LPP signaling.

In additional or alternative embodiments, as part of the joint report, the UE may report one or more of the following. In some examples, the UE can report a reference time for the reference TRP, a reference phase for the reference TRP, and a first Rx error group identifier (e.g., a first Rx TPEG ID) associated with the reference time and the reference phase. In additional or alternative examples, the UE can report a first DL RSTD for a first target TRP, a first DL relative carrier phase measurement (relative to the phase of the reference TRP), and a second Rx error group identifier (e.g., a second Rx TPEG ID) associated with the first DL RSTD and the first DL relative carrier phase measurement. In additional or alternative examples, the UE can report a second DL RSTD for a second target TRP, a second DL relative carrier phase measurement (relative to the phase of the reference TRP), and a third Rx error group identifier (e.g., a third Rx TPEG ID) associated with the second DL RSTD and the second DL relative carrier phase measurement.

In additional or alternative embodiments, the network node (e.g., a LMF) configures the UE to jointly report DL RSRP measurement s) and DL carrier phase measurements (the carrier phase measurement here can be either an absolute measurement or a relative measurement with respect to a reference phase corresponding to a reference TRP, e.g., equation (1) or (2)).

In additional or alternative embodiments, the UE determines a timing error margin and a phase error margin. In some examples, the UE determines the timing error margin from a list of prespecified or preconfigured candidate timing error margin values (e.g., these candidate values may be specified in 3GPP specifications). In additional or alternative examples, the UE determines the phase error margin from a list of prespecified or preconfigured candidate phase error margin values (e.g., these candidate values may be specified in 3GPP specifications). The phase error margin can be related to the timing error margin according to a predefined conversion formula.

In additional or alternative embodiments, the UE measures one or more DL RSTDs and the corresponding DL carrier phase measurements (either absolute or relative) on DL PRSs received from one or more target TRPs. In some examples, the UE also determines a reference time and a reference phase corresponding to reference TRP.

In additional or alternative embodiments, the UE determines an error group identifier (e.g., TPEG ID) for each DL RSTD and the corresponding DL carrier phase measurement (either absolute or relative).

In additional or alternative embodiments, the UE determines an error group identifier (e.g., TPEG ID) for the reference time and the reference phase.

In additional or alternative embodiments, the UE reports the joint report to the network node (e.g., LMF). In some examples, the joint report includes the determined reference time and the determined reference phase. In additional or alternative examples, the joint report includes the measured one or more DL RSTDs and the corresponding DL carrier phase measurements (either absolute or relative). In additional or alternative examples, the joint report includes the determined error group identifier (e.g., TPEG ID) for the reference time and the reference phase. In additional or alternative examples, the joint report includes the determined error group identifiers (e.g., TPEG ID) for each DL RSTD and the corresponding DL carrier phase measurement (either absolute or relative).

Embodiments associated with reporting a single gNB Rx error group with two different margins are described below. The carrier phase measurements described in these embodiments can be UL carrier phase measurements.

In some embodiments, when carrier phase measurement is jointly reported with UL RTOA (relative time or arrival as defined in 3 GPP TS 38.215 V17.2.0) or UL TDOA measurement, then two margins are defined within the same error group. Henceforth, we’ll only use the term UL RTOA for describing the embodiment. The error group may be called a timing error group (TEG) or a joint timing-phase error group (TPEG). A first margin is defined as the timing error margin which is used to indicate if the timing error difference between two UL RTOA measurements are within this timing error margin. A second margin is defined as the phase error margin which is used to indicate if the phase error difference between two carrier phase measurements are within this phase error margin.

In additional or alternative embodiments, using the two margins, two different jointly reported carrier phase measurements and UL RTOA measurements are associated with the same receive error group (e.g., Rx TPEG or Rx TEG) if both the following conditions are satisfied: 1) If the Rx timing error difference between a first UL RTOA measurement in the first joint report and a second UL RTOA measurement in the second joint report are within the first margin (i.e., the timing error margin); and 2) If the Rx UL phase error difference between a first carrier phase measurement in the first joint report and a second carrier phase measurement in the second joint report are within the second margin (i.e., the phase error margin).

In additional or alternative embodiments, the gNB reports an identifier associated with the Rx error group (e.g., Rx TPEG ID or Rx TEG ID) along with the joint report to the LMF via NRPPa signaling.

In additional or alternative embodiments, as part of the joint report, the gNB may report one or more of the following. In some examples, the gNB may report a first UL RTOA, a first UL relative carrier phase measurement (relative to a reference phase), and a first Rx error group identifier (e.g., a first Rx TPEG ID) associated with the first UL RTOA and the first UL relative carrier phase measurement. In additional or alternative examples, the gNB may report a second UL RTOA, a second UL relative carrier phase measurement (relative to the reference phase), and a second Rx error group identifier (e.g., a second Rx TPEG ID) associated with the second UL RTOA and the second UL relative carrier phase measurement.

In some embodiments, the network node (e.g., LMF) configures the gNB or TRP to jointly report UL RTOA measurement s) and UL carrier phase measurements (note that carrier phase measurement here can be either an absolute measurement or a relative measurement with respect to a reference phase).

In additional or alternative embodiments, the gNB or TRP determines a timing error margin and a phase error margin. In some examples, the gNB or TRP determines the timing error margin from a list of prespecified or preconfigured candidate timing error margin values (e.g., these candidate values may be specified in 3GPP specifications). In additional or alternative examples, the gNB or TRP determines the phase error margin from a list of prespecified or preconfigured candidate phase error margin values (e.g., these candidate values may be specified in 3GPP specifications). The phase error margin can be related to the timing error margin according to a predefined conversion formula.

In additional or alternative embodiments, the gNB or TRP measures one or more UL RTOAs and the corresponding UL carrier phase measurements (either absolute or relative) on UL SRSs received from a UE.

In additional or alternative embodiments, the gNB or TRP determines an error group identifier (e.g., TPEG ID) for each UL RTOA and the corresponding UL carrier phase measurement (either absolute or relative).

In additional or alternative embodiments, the gNB or TRP reports the joint report to the network node (e.g., LMF), including one or more of the following: 1) The measured one or more UL RTOAs and the corresponding UL carrier phase measurements (either absolute or relative); and 2) The determined error group identifiers (e.g., TPEG ID) for each UL RTOA and the corresponding UL carrier phase measurement (either absolute or relative)

Embodiments associated with reporting two UE Rx error groups with respective two margins are described below. The carrier phase measurements described in these embodiments are (1) DL carrier phase measurements or (2) DL carrier phase difference measurement.

In some embodiments, when carrier phase measurement is jointly reported with DL RSTD measurement, then two error groups are defined with corresponding error group margins. The timing error group may be called a timing error group (TEG), and the phase error group may be called a phase error group (PEG). A first margin associated with a TEG is defined as the timing error margin which is used to indicate if the timing error difference between two DL RSTD measurements are within this timing error margin. A second margin associated with a PEG is defined as the phase error margin which is used to indicate if the phase error difference between two carrier phase measurements are within this phase error margin.

In additional or alternative embodiments, using the two error groups, two different jointly reported carrier phase measurements and DL RSTD measurements can be combined together for estimating positioning by the LMF if both the following conditions are satisfied: 1) If the Rx timing error difference between a first DL RSTD measurement in the first joint report and a second DL RSTD measurement in the second joint report are within the first margin (i.e., the timing error margin); and 2) If the Rx phase error difference between a first carrier phase measurement in the first joint report and a second carrier phase measurement in the second joint report are within the second margin (i.e., the phase error margin).

In additional or alternative embodiments, if two joint reports have both the same TEG (e.g., Rx TEG) and the same PEG (e.g., Rx PEG), then the two joint reports can be used together for estimating the position of the UE.

In additional or alternative embodiments, the UE reports identifiers associated with the Rx TEG and the Rx PEG along with the joint report to the LMF via LPP signaling.

In additional or alternative embodiments, as part of the joint report, the UE may report one or more of the following. In some examples, the UE may report a reference time for the reference TRP, a reference phase for the reference TRP, a first Rx timing error group identifier (e.g., a first Rx TEG ID) associated with the reference time, and a first Rx phase error group identifier (e.g., a first Rx PEG ID) associated with the reference phase. In additional or alternative examples, the UE may report a first DL RSTD for a first target TRP, a first DL relative carrier phase measurement (relative to the reference phase), a second Rx timing error group identifier (e.g., a second Rx TEG ID) associated with the first DL RSTD, and a second Rx phase error group identifier (e.g., a second Rx PEG ID) associated with the first DL relative carrier phase measurement. In additional or alternative examples, the UE may report a second DL RSTD for a second target TRP, a second DL relative carrier phase measurement (relative to the reference phase), a third Rx timing error group identifier (e.g., a third Rx TEG ID) associated with the second DL RSTD, and a third Rx phase error group identifier (e.g., a third Rx PEG ID) associated with the second DL relative carrier phase measurement.

In some embodiments, the network node (e.g., LMF) configures the UE to jointly report DL RSRP measurement s) and DL carrier phase measurements (note that carrier phase measurement here can be either an absolute measurement or a relative measurement with respect to a reference phase corresponding to a reference TRP).

In additional or alternative embodiments, the UE determines a timing error margin (associated with TEG) and a phase error margin (associated with PEG). In some examples, the UE determines the timing error margin from a list of prespecified or preconfigured candidate timing error margin values (e.g., these candidate values may be specified in 3GPP specifications). In additional or alternative examples, the UE determines the phase error margin from a list of prespecified or preconfigured candidate phase error margin values (e.g., these candidate values may be specified in 3GPP specifications). The phase error margin can be related to the timing error margin according to a predefined conversion formula.

In additional or alternative embodiments, the UE determines a timing error group identifier (e.g., TEG ID) for each DL RSTD and a phase error group identifier (e.g., PEG ID) for each of the corresponding DL carrier phase measurement (either absolute or relative).

In additional or alternative embodiments, the UE determines a timing error group identifier (e.g., TEG ID) for the reference time and a phase error group identifier for the reference phase.

In additional or alternative embodiments, the UE reports the joint report to the network node (e.g., LMF), including one or more of the following. In some examples, the UE reports the determined reference time and the determined reference phase. In additional or alternative examples, the UE reports the measured one or more DL RSTDs and the corresponding DL carrier phase measurements (either absolute or relative). In additional or alternative examples, the UE reports the determined timing error group identifier (e.g., TEG ID) for the reference time and the phase error group identifier (e.g., PEG ID) for the reference phase. In additional or alternative examples, the UE reports the determined error timing group identifiers (e.g., TEG ID) for each DL RSTD and the phase group identifier (e.g., PEG ID) for the corresponding DL carrier phase measurement (either absolute or relative).

Embodiment associated with reporting two gNB Rx error groups with respective two margins are described below. The carrier phase measurements described in these embodiments are UL carrier phase measurements.

In some embodiments, when carrier phase measurement is jointly reported with UL RTOA measurement, then two error groups are defined with corresponding error group margins. The timing error group may be called a timing error group (TEG), and the phase error group may be called a phase error group (PEG). A first margin associated with a TEG is defined as the timing error margin which is used to indicate if the timing error difference between two UL RTOA measurements are within this timing error margin. A second margin associated with a PEG is defined as the phase error margin which is used to indicate if the phase error difference between two carrier phase measurements are within this phase error margin.

In additional or alternative embodiments, using the two error groups, two different jointly reported carrier phase measurements and DL RSTD measurements can be combined together for estimating positioning by the LMF if both the following conditions are satisfied: 1) If the Rx timing error difference between a first UL RTOA measurement in the first joint report and a second UL RTOA measurement in the second joint report are within the first margin (i.e., the timing error margin); and 2) If the Rx phase error difference between a first carrier phase measurement in the first joint report and a second carrier phase measurement in the second joint report are within the second margin (i.e., the phase error margin).

In additional or alternative embodiments, the gNB or TRP reports identifiers associated with the Rx TEG and the Rx PEG along with the joint report to the LMF via NRPPa signaling.

In additional or alternative embodiments, as part of the joint report, the gNB or TRP may report one or more of the following. In some examples, the joint report may include a first UL RTOA, a first UL relative carrier phase measurement (relative to the reference phase), a first Rx timing error group identifier (e.g., a first Rx TEG ID) associated with the first DL RSTD, and a second Rx phase error group identifier (e.g., a second Rx PEG ID) associated with the first UL relative carrier phase measurement.

In additional or alternative examples, the joint report may include a second UL RTOA, a second UL relative carrier phase measurement (relative to the reference phase), a second Rx timing error group identifier (e.g., a second Rx TEG ID) associated with the second UL RTOA, and a second Rx phase error group identifier (e.g., a second Rx PEG ID) associated with the second UL relative carrier phase measurement.

In some embodiments, the network node (e.g., LMF) configures the gNB/TRP to jointly report UL RTOA measurement s) and UL carrier phase measurements (note that carrier phase measurement here can be either an absolute measurement or a relative measurement with respect to a reference phase).

In additional or alternative embodiments, gNB or TRP determines a timing error margin (associated with TEG) and a phase error margin (associated with PEG). In some examples, the gNB or TRP determines the timing error margin from a list of prespecified or preconfigured candidate timing error margin values (e.g., these candidate values may be specified in 3GPP specifications). In additional or alternative examples, the gNB or TRP determines the phase error margin from a list of prespecified or preconfigured candidate phase error margin values (e.g., these candidate values may be specified in 3GPP specifications). The phase error margin can be related to the timing error margin according to a predefined conversion formula.

In additional or alternative embodiments, the gNB or TRP determines a timing error group identifier (e.g., TEG ID) for each gNB or TRP and a phase error group identifier (e.g., PEG ID) for each of the corresponding UL carrier phase measurement (either absolute or relative).

In additional or alternative embodiments, the gNB or TRP reports the joint report to the network node (e.g., LMF), including one or more of the following: 1) The measured one or more UL RTOAs and the corresponding UL carrier phase measurements (either absolute or relative); and 2) The determined error timing group identifiers (e.g., TEG ID) for each UL RTOA and the phase group identifier (e.g., PEG ID) for the corresponding UL carrier phase measurement (either absolute or relative).

Embodiments associated with reporting a single UE RxTx error group with two different margins are described below. The carrier phase measurements described in these embodiments are absolute DL carrier phase measurements, not relative to a reference TRP. The time difference measurements described in this embodiment are UE Rx-Tx time difference measurements, defined in 3GPP TS 38.215 V17.2.0.

In some embodiments, when carrier phase measurement is jointly reported with UE Rx-Tx measurement, then two margins are defined within the same error group. The error group may be called a timing error group (TEG) or a joint timing-phase error group (TPEG). A first margin is defined as the timing error margin which is used to indicate if the timing error difference between two UE Rx-Tx measurements are within this timing error margin. A second margin is defined as the phase error margin which is used to indicate if the phase error difference between two DL carrier phase measurements are within this phase error margin. In additional or alternative embodiments, the phase error margin can be derived from the timing error margin according to a predefined conversion formula.

In additional or alternative embodiments, using the two margins, two different jointly reported carrier phase measurements and UE Rx-Tx measurements are associated with the same error group (e.g., RxTx TPEG or RxTx TEG) if both the following conditions are satisfied: 1) If the timing error difference between a first UE Rx-Tx measurement in the first joint report and a second UE Rx-Tx measurement in a second joint report are within the first margin (i.e., the timing error margin); and 2) If the phase error difference between a first carrier phase measurement in the first joint report and a second carrier phase measurement in the second joint report are within the second margin (i.e., the phase error margin).

In additional or alternative embodiments, the UE reports an identifier associated with the RxTx error group (e.g., RxTx TPEG ID or RxTx TEG ID) along with the joint report to the LMF via LPP signaling.

In additional or alternative embodiments, as part of the joint report, the UE may report one or more of the following. In some examples, the UE may report a first UE Rx-Tx measurement for a first target TRP, a first DL carrier phase measurement for the same TRP, and a first RxTx error group identifier (e.g., a first RxTx TPEG ID) associated with the first UE Rx-Tx measurement and the first DL carrier phase measurement. In additional or alternative examples, the UE may report a second UE Rx-Tx measurement for a second target TRP, a second DL carrier phase measurement for the same TRP, and a second RxTx error group identifier (e.g., a second RxTx TPEG ID) associated with the second UE Rx-Tx measurement and the second DL carrier phase measurement.

In some embodiments, the network node (e.g., LMF) configures the UE to jointly report UE Rx-Tx time difference measurement s) and DL carrier phase measurements.

In additional or alternative embodiments, the UE measures one or more UE Rx-Tx measurements and the corresponding DL carrier phase measurements on DL PRSs received from one or more target TRPs. In additional or alternative embodiments, the UE determines an error group identifier (e.g., TPEG ID) for each UE Rx-Tx and the corresponding DL carrier phase measurement.

In additional or alternative embodiments, the UE reports the joint report to the network node (e.g., LMF), including one or more of the following. In some examples, the UE reports the measured one or more UE Rx-Tx and the corresponding DL carrier phase measurements. In additional or alternative examples, the UE reports the determined error group identifiers (e.g., TPEG ID) for each UE Rx-Tx and the corresponding DL carrier phase measurement.

Embodiments associated with reporting single UE Rx error group with two different margins and single UE Tx error group with one margin are described below. Similar to some of the embodiments above, the carrier phase measurements described in these embodiments are absolute DL carrier phase measurements, not relative to a reference TRP. The time difference measurements described in these embodiments are UE Rx-Tx time difference measurements, defined in 3GPP TS 38.215 V17.2.0.

In some embodiments, UE Rx-Tx time is defined as: TUE,R_X - TUE,TX. A UE Rx-Tx measurement can be associated with one UE Rx error group and one UE Tx error group.

In additional or alternative embodiments, when carrier phase measurement is jointly reported with UE Rx-Tx measurement, then two margins are defined within one UE Rx error group. The error group may be called a timing error group (TEG) or a joint timing-phase error group (TPEG). A first margin is defined as the Rx timing error margin which is used to indicate if the Rx timing error difference between two UE Rx-Tx measurements are within this timing error margin. A second margin is defined as the phase error margin which is used to indicate if the phase error difference between two carrier phase measurements are within this phase error margin. Additionally, a third margin is defined within one UE Tx error group. The error group may be called a timing error group (TEG). This third margin is defined as the Tx timing error margin which is used to indicate if the Tx timing error difference between two UE Rx-Tx measurements are within this timing error margin.

In additional or alternative embodiments, the Rx phase error margin can be derived from the Rx timing error margin according to a predefined conversion formula.

In additional or alternative embodiments, two different jointly reported carrier phase measurements and UE Rx-Tx measurements are associated with the same Rx error group (e.g., Rx TPEG or Rx TEG) if both the following conditions are satisfied: 1) If the Rx timing error difference between a first UE Rx-Tx measurement in the first joint report and a second UE Rx- Tx measurement in the second joint report are within the first margin (i.e., the timing error margin); and 2) If the phase error difference between a first carrier phase measurement in the first joint report and a second carrier phase measurement in the second joint report are within the second margin (i.e., the phase error margin).

In additional or alternative embodiments, two different jointly reported carrier phase measurements and UE Rx-Tx measurements are associated with the same Tx error group (e.g., Tx TEG) if the following condition is satisfied: If the Tx timing error difference between a first UE Rx-Tx measurement in the first joint report and a second UE Rx-Tx measurement in the second joint report are within the first margin (i.e., the timing error margin).

In additional or alternative embodiments, the UE reports an identifier associated with the Rx error group (e.g., Rx TPEG ID or Rx TEG ID) along with the joint report to the LMF via LPP signaling. Additionally, the UE reports an identifier associated with the Tx error group (e g. Tx TEG ID).

In additional or alternative embodiments, as part of the joint report, the UE may report one or more of the following. In some examples, a UE may report a first UE Rx-Tx measurement for a first target TRP, a first DL carrier phase measurement, and a first Rx error group identifier (e.g., a first Rx TPEG ID) associated with the first UE Rx-Tx measurement and the first DL carrier phase measurement and a first Tx error group identifier (e.g. a first Tx TEG ID) associated with the first UE Rx-Tx measurement. In additional or alternative examples, a UE may report a second UE Rx-Tx measurement for a second target TRP, a second DL carrier phase measurement, and a second Rx error group identifier (e.g., a second Rx TPEG ID) associated with the second UE Rx-Tx measurement and the second DL carrier phase measurement and a second Tx error group identifier (e.g. a second Tx TEG ID) associated with the second UE Rx- Tx measurement.

In additional or alternative embodiments, the UE determines an Rx timing error margin, a Tx timing error margin and a phase error margin. In some examples, the UE determines each of the timing error margins from a list of prespecified or preconfigured candidate timing error margin values (e.g., these candidate values may be specified in 3GPP specifications). In additional or alternative examples, the UE determines the phase error margin from a list of prespecified or preconfigured candidate phase error margin values (e.g., these candidate values may be specified in 3 GPP specifications). The phase error margin can be related to the timing error margin according to a predefined conversion formula.

In additional or alternative embodiments, the UE measures one or more UE Rx-Tx measurements and the corresponding DL carrier phase measurements on DL PRSs received from one or more target TRPs. In additional or alternative embodiments, the UE determines an Rx error group identifier (e.g., Rx TPEG ID) for the UE Rx-Tx measurement and the corresponding DL carrier phase measurement.

In additional or alternative embodiments, the UE determines a Tx error group identifier (e.g. Tx TEG ID) for the UE Rx-Tx measurement.

In additional or alternative embodiments, the UE reports the joint report to the network node (e.g., LMF), including one or more of the following. In some examples, the UE reports the UE Rx-Tx measurement and the corresponding DL carrier phase measurements. In additional or alternative examples, the UE reports the determined error group identifiers (e.g., Rx TPEG ID and Tx TEG ID) for each UE Rx-Tx and the corresponding DL carrier phase measurement .

Embodiments associated with reporting single gNB RxTx error group with two different margins are described below. The carrier phase measurements described in these embodiments are absolute UL carrier phase measurements, not relative to a reference TRP. The time difference measurements described in these embodiments are gNB Rx-Tx time difference measurements, defined in 3GPP TS 38.215 V17.2.0.

In some embodiments, when carrier phase measurement is jointly reported with gNB Rx- Tx measurement, then two margins are defined within the same error group. The error group may be called a timing error group (TEG) or a joint timing-phase error group (TPEG). A first margin is defined as the timing error margin which is used to indicate if the timing error difference between two gNB Rx-Tx time difference measurements are within this timing error margin. A second margin is defined as the phase error margin which is used to indicate if the phase error difference between two carrier phase measurements are within this phase error margin.

In additional or alternative embodiments, using the two margins, two different jointly reported carrier phase measurements and gNB Rx-Tx measurements are associated with the same error group (e.g., RxTx TPEG or RxTx TEG) if both the following conditions are satisfied: 1) If the timing error difference between a first gNB Rx-Tx measurement in the first joint report and a second gNB Rx-Tx measurement in the second joint report are within the first margin (i.e., the timing error margin); and 2) If the phase error difference between a first carrier phase measurement in the first joint report and a second carrier phase measurement in the second joint report are within the second margin (i.e., the phase error margin). In additional or alternative embodiments, the gNB or TRP reports an identifier associated with the RxTx error group (e.g., RxTx TPEG ID or RxTx TEG ID) along with the joint report to the LMF via LPP signaling.

In additional or alternative embodiments, as part of the joint report, the gNB or TRP may report one or more of the following: a gNB Rx-Tx measurement for a target UE, a UL carrier phase measurement, a RxTx error group identifier (e.g., a RxTx TPEG ID) associated with the gNB Rx-Tx measurement and the UL carrier phase measurement.

In some embodiments, the network node (e.g., LMF) configures the gNB to jointly report gNB Rx-Tx time difference measurement s) and UL carrier phase measurements for a TRP.

In additional or alternative embodiments, the gNB determines a timing error margin and a phase error margin. In some examples, the gNB determines the timing error margin from a list of prespecified or preconfigured candidate timing error margin values (e.g., these candidate values may be specified in 3GPP specifications). In additional or alternative examples, the gNB determines the phase error margin from a list of prespecified or preconfigured candidate phase error margin values (e.g., these candidate values may be specified in 3GPP specifications). The phase error margin can be related to the timing error margin according to a predefined conversion formula.

In additional or alternative embodiments, the gNB or TRP measures one or more gNB RxTx and the corresponding UL carrier phase measurements on UL SRSs received from a UE.

In additional or alternative embodiments, the gNB or TRP determines an error group identifier (e.g., TPEG ID) for each gNB Rx-Tx measurement and the corresponding UL carrier phase measurement.

In additional or alternative embodiments, the gNB or TRP reports the joint report to the network node (e.g., LMF), including one or more of the following: 1) The measured one or more gNB Rx-Tx and the corresponding UL carrier phase measurements; and 2) The determined error group identifiers (e.g., TPEG ID) for each gNB Rx-Tx and the corresponding UL carrier phase measurement.

Embodiments associated with reporting single gNB Rx error group with two different margins and single gNB Tx error group with one margin are described below. The carrier phase measurements described in these embodiments are absolute UL carrier phase measurements, not relative to a reference TRP. The time difference measurements described in these embodiments are gNB Rx-Tx time difference measurements, defined in 3GPP TS 38.215 V17.2.0. In some examples, the gNB Rx-Tx time is defined as T_gNB,Rx - T_gNB,Tx

In some embodiments, a gNB Rx-Tx measurement can be associated with one gNB Rx error group and one gNB Tx error group. In additional or alternative embodiments, when carrier phase measurement is jointly reported with gNB Rx-Tx measurement, then two margins are defined within one gNB Rx error group. The error group may be called a timing error group (TEG) or a joint timing-phase error group (TPEG). A first margin is defined as the timing error margin which is used to indicate if the Rx timing error difference between two gNB Rx-Tx measurements are within this timing error margin. A second margin is defined as the phase error margin which is used to indicate if the phase error difference between two carrier phase measurements are within this phase error margin. Additionally, a third margin is defined within one gNB Tx error group. The error group may be called a timing error group (TEG). This third margin is defined as the Tx timing error margin which is used to indicate if the Tx timing error difference between two UE Rx-Tx measurements are within this timing error margin.

In additional or alternative embodiments, two different jointly reported carrier phase measurements and gNB Rx-Tx measurements are associated with the same Rx error group (e.g., RxTx TPEG or RxTx TEG) if both the following conditions are satisfied: 1) If the timing error difference between a first gNB Rx-Tx measurement in the first joint report and a second gNB Rx-Tx measurement in the second joint report are within the first margin (i.e., the timing error margin); and 2) If the phase error difference between a first carrier phase measurement in the first joint report and a second carrier phase measurement in the second joint report are within the second margin (i.e., the phase error margin).

In additional or alternative embodiments, two different jointly reported carrier phase measurements and gNB Rx-Tx measurements are associated with the same Tx error group (e.g., Tx TEG) if the following condition is satisfied: If the Tx timing error difference between a first gNB Rx-Tx measurement in the first joint report and a second gNB Rx-Tx measurement in the second joint report are within the first margin (i.e., the timing error margin).

In additional or alternative embodiments, the gNB or TRP reports an identifier associated with the RxTx error group (e.g., RxTx TPEG ID or RxTx TEG ID) along with the joint report to the LMF via LPP signaling. Additionally, the gNB reports an identifier associated with the Tx error group (e.g. Tx TEG ID).

In additional or alternative embodiments, as part of the joint report, the gNB or TRP may report one or more of the following. In some examples, the joint report may include a gNB RxTx measurement for a target UE, a UL carrier phase measurement, a Rx error group identifier (e.g., a Rx TPEG ID) associated with the gNB Rx-Tx measurement and the UL carrier phase measurement and a Tx error group identifier (e.g. a first Tx TEG ID) associated with the gNB Rx-Tx measurement.

In additional or alternative embodiments, the gNB or TRP measures one or more gNB Rx- Tx and the corresponding UL carrier phase measurements on UL SRSs received from a UE.

In additional or alternative embodiments, the gNB or TRP determines an error group identifier (e.g., TPEG ID) for the gNB Rx-Tx measurement and the corresponding UL carrier phase measurement.

In additional or alternative embodiments, the gNB or TRP determines a Tx error group identifier (e.g. Tx TEG ID) for the gNB Rx-Tx measurement.

In additional or alternative embodiments, the gNB or TRP reports the joint report to the network node (e.g., LMF), including one or more of the following. In some examples, the joint report includes the measured one or more gNB Rx-Tx and the corresponding UL carrier phase measurements. In additional or alternative examples, the joint report includes the determined error group identifiers (e.g., Rx TPEG ID and Tx TEG ID) for each gNB Rx-Tx and the corresponding UL carrier phase measurement.

Embodiments associated with conversion between timing error margin and phase error margin are described below. In some embodiments, a phase error margin can be derived from a timing error margin according to a predefined conversion formula.

In additional or alternative embodiments, the conversion formula is given by phase error margin = k * time error margin+m, where k is a scaling factor and m an offset that can be selected by the UE or the TRP from a prespecified or preconfigured list of scaling factors or offsets.

Operations of the communication device 900 (implemented using the structure of the block diagram of FIG. 9) will now be discussed with reference to the flow chart of FIG. 5 according to some embodiments of inventive concepts. For example, modules may be stored in memory 910 of FIG. 9, and these modules may provide instructions so that when the instructions of a module are executed by respective communication device processing circuitry 902, processing circuitry 902 performs respective operations of the flow chart.

FIG. 5 illustrates an example of operations performed by a communication device. The communication device can be in a communications network that includes a first network node, a second network node, and a third network node. In some embodiments, the first network node is a target transmission/reception point, TRP. In additional or alternative embodiments, the second network node is configured to provide a location management function, LMF. In additional or alternative embodiments, the third network node is a reference TRP.

At block 510, processing circuitry 902 receives, via communication interface 912, configuration information from the second network node (e.g., an LMF). In some embodiments, the configuration information includes an indication that the communication device jointly report the DL RSTD and the DL carrier phase measurement to the second network node.

At block 520, processing circuitry 902 measures a DL RSTD and a corresponding DL carrier phase measurement on a DL PRS. The DL PRS being received from the first network node.

At block 530, processing circuitry 902 determines a timing error margin and a phase error margin. In some embodiments, determining the timing error margin includes selecting the timing error margin from a list of preconfigured candidate timing error margin values. In some examples, determining the phase error margin includes determining the phase error margin based on the time error margin.

In additional or alternative embodiments, determining the phase error margin comprises selecting the phase error margin from a list of preconfigured candidate phase error margin values. In some examples, determining the timing error margin includes determining the timing error margin based on the phase error margin.

At block 535, processing circuitry 902 transmits, via communication interface 912, an indication of the timing error margin and an indication of the phase error margin to the second network node.

At block 540, processing circuitry 902 determines an error group identifier of the DL RSTD and the corresponding DL carrier phase measurement. In some embodiments, the error group identifier for the DL RSTD and the corresponding DL carrier phase measurement includes at least one of: 1) a timing and phase error group, TPEG, identifier, ID, for both the DL RSTD and the corresponding DL carrier phase measurement; and 2) a timing error group, TEG, ID for the DL RSTD and a phase error group, PEG, ID for the corresponding DL carrier phase, At block 550, processing circuitry 902 determines the reference time and the reference phase corresponding to the third network node.

At block 560, processing circuitry 902 determines an error group identifier for the reference time and the reference phase. In some embodiments, the error group identifier for the reference time and the reference phase includes at least one of: 1) a TPEG ID for both the reference time and the reference phase; and 2) a TEG ID for the reference time and a PEG ID for the reference phase.

In some embodiments, the DL RSTD is a first DL RSTD of a plurality of DL RSTD. At block 565, processing circuitry 902 determines whether the first DL RSTD and a second DL RSTD have a joint timing error group. In some examples, determines whether the first DL RSTD and a second DL RSTD have a joint timing error group includes determining whether the first DL RSTD of the plurality of DL RSTD and a second DL RSTD of the plurality of DL RSTD have a joint timing error group based on the timing error margin and the phase error margin.

In additional or alternative examples, determining whether the first DL RSTD of the plurality of DL RSTD and the second DL RSTD of the plurality of DL RSTD have the joint timing error group includes determining that the first DL RSTD of the plurality of DL RSTD and the second DL RSTD of the plurality of DL RSTD have the joint timing error group based on: 1) determining that a timing error difference between the first DL RSTD and the second DL RSTD is within to the timing error margin; and 2) determining that a phase error difference between a first carrier phase measurement corresponding to the first DL RSTD and a second carrier phase measurement corresponding to the second DL RSTD is within the phase error margin.

At block 570, processing circuitry 902 transmits a joint report to the second network node. In some embodiments, the joint report includes at least one of: a first combination and a second combination. In some examples, the first combination includes: 1) an indication of the DL RSTD and the corresponding DL carrier phase measurement; and 2) an indication of an error group identifier for the DL RSTD and the corresponding DL carrier phase measurement. In additional or alternative examples, a second combination includes: 1) an indication of a reference time and a reference phase corresponding to a third network node; and 2) an indication of an error group identifier of the reference time and the reference phase.

Various operations from the flow chart of FIG. 5 may be optional with respect to some embodiments of communication devices and related methods.

Operations of the RAN node 1000 (implemented using the structure of FIG. 10) will now be discussed with reference to the flow chart of FIG. 6 according to some embodiments of inventive concepts. For example, modules may be stored in memory 1004 of FIG. 10, and these modules may provide instructions so that when the instructions of a module are executed by respective RAN node processing circuitry 920, RAN node 1000 performs respective operations of the flow chart.

FIG. 6 illustrates an example of operations performed by a first network node. The first network node is in a communications network that includes a communication device and a second network node. In some embodiments, the second network node is configured to provide a location management function, LMF.

At block 610, processing circuitry 1002 receives, via communication interface 1006, configuration information from the second network node. In some embodiments, the configuration information includes an indication that the first network node jointly report the UL RTOA and the UL carrier phase measurement to the second network node.

At block 620, processing circuitry 1002 measures an UL RTOA and a corresponding UL carrier phase measurement on an UL SRS received from the communication device.

At block 630, processing circuitry 1002 determines a timing error margin and a phase error margin. In some embodiments, determining the timing error margin includes selecting the timing error margin from a list of preconfigured candidate timing error margin values. In some examples, determining the phase error margin comprises determining the phase error margin based on the time error margin.

In additional or alternative embodiments, determining the phase error margin includes selecting the phase error margin from a list of preconfigured candidate phase error margin values. In some examples, determining the timing error margin includes determining the timing error margin based on the phase error margin.

At block 635, processing circuitry 1002 transmits, via communication interface 1006, an indication of the timing error margin and an indication of the phase error margin to the second network node.

At block 640, processing circuitry 1002 determines an error group identifier for the UL RTOA and the corresponding UL carrier phase measurement. In some embodiments, the error group identifier for the UL RTOA and the corresponding UL carrier phase measurement includes at least one of: 1) a timing and phase error group, TPEG, identifier, ID, for both the UL RTOA and the corresponding UL carrier phase measurement; and 2) a timing error group, TEG, ID for the UL RTOA and a phase error group, PEG, ID for the corresponding UL carrier phase.

In some embodiments, the UL RTOA is a first UL RTOA of a plurality of UL RTOA. At block 645, processing circuitry 1102 determines whether the first UL RTOA and a second UL RTOA have a joint timing error group. In some examples, determining whether the first UL RTOA and a second UL RTOA have a joint timing error group includes determining whether the first UL RTOA of the plurality of UL RTOA and a second UL RTOA of the plurality of UL RTOA have a joint timing error group based the timing error margin and the phase error margin.

In additional or alternative examples, determining whether the first UL RTOA of the plurality of UL RTOA and the second UL RTOA of the plurality of UL RTOA have the joint timing error group includes determining that the first UL RTOA of the plurality of UL RTOA and the second UL RTOA of the plurality of UL RTOA have the joint timing error group based on: 1) determining that a timing error difference between the first UL RTOA and the second UL RTOA is within to the timing error margin; and 2) determining that a phase error difference between a first carrier phase measurement corresponding to the first UL TDOA and a second carrier phase measurement corresponding to the second UL TDOA is within the phase error margin.

At block 650, processing circuitry 1002 transmits, via communication interface 1006, a joint report to the second network node. The joint report can include an indication of the UL RTOA and the corresponding UL carrier phase measurement. The joint report can further include an indication of an error group identifier for the UL RTOA and the corresponding UL carrier phase measurement.

FIG. 7 illustrates an example of operations performed by a second network node. In some embodiments, the second network node is in a communications network that includes a communication device and a first network node. In some examples, the second network node is configured to provide a location management function, LMF.

At block 710, processing circuitry 1002 transmits, via communication interface 1006, configuration information. In some embodiments, the configuration information includes an indication that the communication device or the first network node transmit the jointly report to the second network node.

At block 720, processing circuitry 1002 receives, via communication interface 1006, a joint report. In some embodiments, the joint report includes an indication of a measurement and an indication of an error group identifier for the measurement.

In additional or alternative embodiments, receiving the joint report includes receiving the joint report from the communication device. In some examples, the joint report including at least one of 1) a first combination; and 2) a second combination. The first combination can include: an indication of a downlink, DL, reference signal time difference, RSTD, and a corresponding DL carrier phase measurement; and an indication of an error group identifier for the DL RSTD and the corresponding DL carrier phase measurement. The second combination can include: an indication of a reference time and a reference phase corresponding to a third network node; and an indication of an error group identifier of the reference time and the reference phase.

In additional or alternative embodiments, receiving the joint report includes receiving the joint report from the first network node. In some examples, the joint report includes: an indication of an uplink, UL, relative time of arrival, RTOA, and the corresponding UL carrier phase measurement; and an indication of an error group identifier for the UL RTOA and the corresponding UL carrier phase measurement.

At block 725, processing circuitry 1002 receives, via communication interface 1006, an indication of a timing error margin and an indication of a phase error margin.

At block 730, processing circuitry 1002 determines whether to combine the measurement with other measurements based on the error group identifier.

Various operations from the flow chart of FIG. 6 may be optional with respect to some embodiments of RAN nodes and related methods.

FIG. 8 shows an example of a communication system 800 in accordance with some embodiments.

In the example, the communication system 800 includes a telecommunication network 802 that includes an access network 804, such as a radio access network (RAN), and a core network 806, which includes one or more core network nodes 808. The access network 804 includes one or more access network nodes, such as network nodes 810a and 810b (one or more of which may be generally referred to as network nodes 810), or any other similar 3rd Generation Partnership Project (3 GPP) access node or non-3GPP access point. Moreover, as will be appreciated by those of skill in the art, the network nodes 810 are not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that the network nodes 810 may include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network 802 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network 802 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication network 802, including one or more network nodes 810 and/or core network nodes 808.

Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU- CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time RAN control application (e.g., xApp) or a non-real time RAN automation application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Intents and content-aware notifications described herein may be communicated from a 3 GPP network node or an ORAN network node over 3GPP-defined interfaces (e.g., N2, N3) and/or ORAN Alliance-defined interfaces (e.g., Al, 01). Moreover, an ORAN network node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an 0-2 interface defined by the 0-RAN Alliance. The network nodes 810 facilitate direct or indirect connection of user equipment (UE), such as by connecting wireless devices 812a, 812b, 812c, and 812d (one or more of which may be generally referred to as UEs 812) to the core network 806 over one or more wireless connections. The network nodes 810 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 812a, 812b, 812c, and 812d (one or more of which may be generally referred to as UEs 812) to the core network 806 over one or more wireless connections.

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 800 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 800 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.

The UEs 812 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 810 and other communication devices. Similarly, the network nodes 810 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 812 and/or with other network nodes or equipment in the telecommunication network 802 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 802. In the depicted example, the core network 806 connects the network nodes 810 to one or more hosts, such as host 816. 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 806 includes one more core network nodes (e.g., core network node 808) 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 808. 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).

The host 816 may be under the ownership or control of a service provider other than an operator or provider of the access network 804 and/or the telecommunication network 802, and may be operated by the service provider or on behalf of the service provider. The host 816 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.

As a whole, the communication system 800 of FIG. 8 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.

In some examples, the telecommunication network 802 is a cellular network that implements 3 GPP standardized features. Accordingly, the telecommunications network 802 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 802. For example, the telecommunications network 802 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.

In some examples, the UEs 812 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 804 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 804. Additionally, a UE may be configured for operating in single- or multi-RAT or multi -standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

In the example, the hub 814 communicates with the access network 804 to facilitate indirect communication between one or more UEs (e.g., UE 812c and/or 812d) and network nodes (e.g., network node 810b). In some examples, the hub 814 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 814 may be a broadband router enabling access to the core network 806 for the UEs. As another example, the hub 814 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 810, or by executable code, script, process, or other instructions in the hub 814. As another example, the hub 814 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 814 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 814 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 814 then provides to the UE either directly, after performing local processing, and/or after adding additional local content. In still another example, the hub 814 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy loT devices.

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

FIG. 9 shows a UE 900 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 (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.

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

The UE 900 includes processing circuitry 902 that is operatively coupled via a bus 904 to an input/output interface 906, a power source 908, a memory 910, a communication interface 912, and/or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in FIG. 9. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc. The processing circuitry 902 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 910. The processing circuitry 902 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 902 may include multiple central processing units (CPUs).

In the example, the input/output interface 906 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 900. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

In some embodiments, the power source 908 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 908 may further include power circuitry for delivering power from the power source 908 itself, and/or an external power source, to the various parts of the UE 900 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 908. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 908 to make the power suitable for the respective components of the UE 900 to which power is supplied.

The memory 910 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 910 includes one or more application programs 914, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 916. The memory 910 may store, for use by the UE 900, any of a variety of various operating systems or combinations of operating systems.

The memory 910 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 910 may allow the UE 900 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 910, which may be or comprise a device-readable storage medium.

The processing circuitry 902 may be configured to communicate with an access network or other network using the communication interface 912. The communication interface 912 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 922. The communication interface 912 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 918 and/or a receiver 920 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 918 and receiver 920 may be coupled to one or more antennas (e.g., antenna 922) and may share circuit components, software or firmware, or alternatively be implemented separately.

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

Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 912, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

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

A UE, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are 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 item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and/or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE 900 shown in FIG. 9.

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 3 GPP 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.

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

FIG. 10 shows a network node 1000 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), NRNodeBs (gNBs)), 0-RAN nodes, or components of an 0-RAN node (e.g., intelligent controller, 0-RU, 0-DU, O-CU).

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

The network node 1000 includes a processing circuitry 1002, a memory 1004, a communication interface 1006, and a power source 1008. The network node 1000 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 1000 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 1000 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 1004 for different RATs) and some components may be reused (e.g., a same antenna 1010 may be shared by different RATs). The network node 1000 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1000, 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 1000.

The processing circuitry 1002 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 1000 components, such as the memory 1004, to provide network node 1000 functionality.

In some embodiments, the processing circuitry 1002 includes a system on a chip (SOC). In some embodiments, the processing circuitry 1002 includes one or more of radio frequency (RF) transceiver circuitry 1012 and baseband processing circuitry 1014. In some embodiments, the radio frequency (RF) transceiver circuitry 1012 and the baseband processing circuitry 1014 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 1012 and baseband processing circuitry 1014 may be on the same chip or set of chips, boards, or units.

The memory 1004 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 1002. The memory 1004 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 1002 and utilized by the network node 1000. The memory 1004 may be used to store any calculations made by the processing circuitry 1002 and/or any data received via the communication interface 1006. In some embodiments, the processing circuitry 1002 and memory 1004 is integrated.

The communication interface 1006 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 1006 comprises port(s)/terminal(s) 1016 to send and receive data, for example to and from a network over a wired connection. The communication interface 1006 also includes radio front-end circuitry 1018 that may be coupled to, or in certain embodiments a part of, the antenna 1010. Radio front-end circuitry 1018 comprises filters 1020 and amplifiers 1022. The radio front-end circuitry 1018 may be connected to an antenna 1010 and processing circuitry 1002. The radio front-end circuitry may be configured to condition signals communicated between antenna 1010 and processing circuitry 1002. The radio front-end circuitry 1018 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 1018 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1020 and/or amplifiers 1022. The radio signal may then be transmitted via the antenna 1010. Similarly, when receiving data, the antenna 1010 may collect radio signals which are then converted into digital data by the radio front-end circuitry 1018. The digital data may be passed to the processing circuitry 1002. In other embodiments, the communication interface may comprise different components and/or different combinations of components.

In certain alternative embodiments, the network node 1000 does not include separate radio front-end circuitry 1018, instead, the processing circuitry 1002 includes radio front-end circuitry and is connected to the antenna 1010. Similarly, in some embodiments, all or some of the RF transceiver circuitry 1012 is part of the communication interface 1006. In still other embodiments, the communication interface 1006 includes one or more ports or terminals 1016, the radio front-end circuitry 1018, and the RF transceiver circuitry 1012, as part of a radio unit (not shown), and the communication interface 1006 communicates with the baseband processing circuitry 1014, which is part of a digital unit (not shown).

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

The antenna 1010, communication interface 1006, and/or the processing circuitry 1002 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 1010, the communication interface 1006, and/or the processing circuitry 1002 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and/or signals may be transmitted to a UE, another network node and/or any other network equipment.

The power source 1008 provides power to the various components of network node 1000 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 1008 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 1000 with power for performing the functionality described herein. For example, the network node 1000 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 1008. As a further example, the power source 1008 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

Embodiments of the network node 1000 may include additional components beyond those shown in FIG. 10 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 1000 may include user interface equipment to allow input of information into the network node 1000 and to allow output of information from the network node 1000. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 1000.

FIG. 11 is a block diagram illustrating a virtualization environment 1200 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 1200 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. In some embodiments, the virtualization environment 1200 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface.

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

Hardware 1204 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 1206 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 1208a and 1208b (one or more of which may be generally referred to as VMs 1208), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein. The virtualization layer 1206 may present a virtual operating platform that appears like networking hardware to the VMs 1208.

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

In the context of NFV, a VM 1208 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 1208, and that part of hardware 1204 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 1208 on top of the hardware 1204 and corresponds to the application 1202.

Hardware 1204 may be implemented in a standalone network node with generic or specific components. Hardware 1204 may implement some functions via virtualization. Alternatively, hardware 1204 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 1210, which, among others, oversees lifecycle management of applications 1202. In some embodiments, hardware 1204 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 1212 which may alternatively be used for communication between hardware nodes and radio units.

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.

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.

Examples of embodiments are described below.

Example 1. A method of operating a communication device in a communications network that includes a first network node, a second network node, and a third network node, the method comprising: measuring (520) a downlink, DL, reference signal time difference, RSTD, and a corresponding DL carrier phase measurement on a DL positioning reference signal, PRS, received from the first network node; and transmitting (570) a joint report to second network node, the joint reporting including at least one of: an indication of the DL RSTD and the corresponding DL carrier phase measurement; an indication of an error group identifier for the DL RSTD and the corresponding DL carrier phase measurement; an indication of a reference time and a reference phase corresponding to a third network node; and an indication of an error group identifier of the reference time and the reference phase.

Example 2. The method of Example 1, further comprising at least one of: determining (540) the error group identifier for the DL RSTD and the corresponding DL carrier phase measurement; determining (550) the reference time and the reference phase corresponding to the third network node; and determining (560) the error group identifier of the reference time and the reference phase.

Example 3. The method of any of Examples 1-2, wherein the first network node is a target transmission/reception point, TRP, wherein the second network node is configured to provide a location management function, LMF, and wherein the third network node is a reference TRP.

Example 4. The method of any of Examples 1-3, further comprising: receiving (510) configuration information from the second network node, the configuration information including an indication that the communication device jointly report the DL RSTD and the DL carrier phase measurement to the second network node.

Example 5. The method of any of Examples 1-4, further comprising: determining (530) a timing error margin; and determining (530) a phase error margin.

Example 6. The method of Example 5, wherein determining the timing error margin comprises selecting the timing error margin from a list of preconfigured candidate timing error margin values, and/or wherein determining the phase error margin comprises selecting the phase error margin from a list of preconfigured candidate phase error margin values.

Example 7. The method of Example 6, wherein determining the timing error margin comprises determining the timing error margin based on the phase error margin, or wherein determining the phase error margin comprises determining the phase error margin based on the time error margin.

Example 8. The method of Examples 4-7, wherein the DL RSTD is a first DL RSTD of a plurality of DL RSTD, the method further comprising: determining whether the first DL RSTD of the plurality of DL RSTD and a second DL RSTD of the plurality of DL RSTD have a joint timing error group based on the timing error margin and the phase error margin.

Example 9. The method of Example 8, wherein determining whether the first DL RSTD of the plurality of DL RSTD and the second DL RSTD of the plurality of DL RSTD have the joint timing error group comprises determining that the first DL RSTD of the plurality of DL RSTD and the second DL RSTD of the plurality of DL RSTD have the joint timing error group based on: determining that a timing error difference between the first DL RSTD and the second DL RSTD is within to the timing error margin; and determining that a phase error difference between a first carrier phase measurement corresponding to the first DL RSTD and a second carrier phase measurement corresponding to the second DL RSTD is within the phase error margin.

Example 10. The method of any of Examples 1-9, wherein the error group identifier for the DL RSTD and the corresponding DL carrier phase measurement comprises at least one of: a timing and phase error group, TPEG, identifier, ID, for both the DL RSTD and the corresponding DL carrier phase measurement; and a timing error group, TEG, ID for the DL RSTD and a phase error group, PEG, ID for the corresponding DL carrier phase, wherein the error group identifier for the reference time and the reference phase comprises at least one of: a TPEG ID for both the reference time and the reference phase; and a TEG ID for the reference time and a PEG ID for the reference phase.

Example 11. A method of operating a first network node in a communications network that includes a communication device and a second network node, the method comprising: measuring (620) an uplink, UL, relative time of arrival, RTOA, and a corresponding UL carrier phase measurement on a UL sounding reference signal, SRS, received from the communication device; and transmitting (670) a joint report to second network node, the joint reporting including at least one of: an indication of the UL RTOA and the corresponding UL carrier phase measurement; and an indication of an error group identifier for the UL RTOA and the corresponding UL carrier phase measurement.

Example 12. The method of Example 11, further comprising: determining (640) the error group identifier for the UL RTOA and the corresponding UL carrier phase measurement.

Example 13. The method of any of Examples 11-12, wherein the second network node is configured to provide a location management function, LMF. Example 14. The method of any of Examples 11-13, further comprising: receiving (610) configuration information from the second network node, the configuration information including an indication that the first network node jointly report the UL RTOA and the UL carrier phase measurement to the second network node.

Example 15. The method of any of Examples 11-14, further comprising: determining (630) a timing error margin; and determining (630) a phase error margin.

Example 16. The method of Example 15, wherein determining the timing error margin comprises selecting the timing error margin from a list of preconfigured candidate timing error margin values, and/or wherein determining the phase error margin comprises selecting the phase error margin from a list of preconfigured candidate phase error margin values.

Example 17. The method of Example 16, wherein determining the timing error margin comprises determining the timing error margin based on the phase error margin, or wherein determining the phase error margin comprises determining the phase error margin based on the time error margin.

Example 18. The method of Examples 14-17, wherein the UL RTOA is a first UL RTOA of a plurality of UL RTOA, the method further comprising: determining whether the first UL RTOA of the plurality of UL RTOA and a second UL RTOA of the plurality of UL RTOA have a joint timing error group based the timing error margin and the phase error margin.

Example 19. The method of Example 18, wherein determining whether the first UL RTOA of the plurality of UL RTOA and the second UL RTOA of the plurality of UL RTOA have the joint timing error group comprises determining that the first UL RTOA of the plurality of UL RTOA and the second UL RTOA of the plurality of UL RTOA have the joint timing error group based on: determining that a timing error difference between the first UL RTOA and the second UL RTOA is within to the timing error margin; and determining that a phase error difference between a first carrier phase measurement corresponding to the first UL TDOA and a second carrier phase measurement corresponding to the second UL TDOA is within the phase error margin.

Example 20. The method of any of Examples 11-19, wherein the error group identifier for the UL RTOA and the corresponding UL carrier phase measurement comprises at least one of: a timing and phase error group, TPEG, identifier, ID, for both the UL RTOA and the corresponding UL carrier phase measurement; and a timing error group, TEG, ID for the UL RTOA and a phase error group, PEG, ID for the corresponding UL carrier phase.

Example 21. A communication device (900), the communication device comprising: processing circuitry (902); and memory (910) coupled to the processing circuitry and having instructions stored therein that are executable by the processing circuitry to cause the communication device to perform operations comprising any of the operations of Examples 1-10.

Example 22. A computer program comprising program code to be executed by processing circuitry (902) of a communication device (900), whereby execution of the program code causes the communication device to perform operations comprising any operations of Examples 1-10.

Example 23. A computer program product comprising a non-transitory storage medium (910) including program code to be executed by processing circuitry (902) of a communication device (900), whereby execution of the program code causes the entity to perform operations comprising any operations of Examples 1-10.

Example 24. A non-transitory computer-readable medium having instructions stored therein that are executable by processing circuitry (902) of an communication device (900) to cause the communication device to perform operations comprising any of the operations of Examples 1-10.

Example 25. A network node (1000), the network node comprising: processing circuitry (1002); and memory (1004) coupled to the processing circuitry and having instructions stored therein that are executable by the processing circuitry to cause the network node to perform operations comprising any of the operations of Examples 11-20.

Example 26. A computer program comprising program code to be executed by processing circuitry (1002) of a network node (1000), whereby execution of the program code causes the network node to perform operations comprising any operations of Examples 11-20.

Example 27. A computer program product comprising a non-transitory storage medium (1004) including program code to be executed by processing circuitry (1002) of a network node (1000), whereby execution of the program code causes the network node to perform operations comprising any operations of Examples 11-20. Example 28. A non-transitory computer-readable medium having instructions stored therein that are executable by processing circuitry (1002) of a network node (1000) to cause the network node to perform operations comprising any of the operations of Examples 11-20.

Claims

1. A method of operating a communication device in a communications network that includes a first network node, a second network node, and a third network node, the method comprising: measuring (520) a downlink, DL, reference signal time difference, RSTD, and a corresponding DL carrier phase measurement on a DL positioning reference signal, PRS, received from the first network node; and transmitting (570) a joint report to second network node, the joint reporting including at least one of: a first combination of: an indication of the DL RSTD and the corresponding DL carrier phase measurement; and an indication of an error group identifier for the DL RSTD and the corresponding DL carrier phase measurement; and a second combination of: an indication of a reference time and a reference phase corresponding to a third network node; and an indication of an error group identifier of the reference time and the reference phase.

2. The method of Claim 1, further comprising at least one of: determining (540) the error group identifier for the DL RSTD and the corresponding DL carrier phase measurement; determining (550) the reference time and the reference phase corresponding to the third network node; and determining (560) the error group identifier of the reference time and the reference phase.

3. The method of any of Claims 1-2, wherein the first network node is a target transmission/reception point, TRP, wherein the second network node is configured to provide a location management function, LMF, and wherein the third network node is a reference TRP.

4. The method of any of Claims 1-3, further comprising: receiving (510) configuration information from the second network node, the configuration information including an indication that the communication device jointly report the DL RSTD and the DL carrier phase measurement to the second network node.

5. The method of any of Claims 1-4, further comprising: determining (530) a timing error margin; determining (530) a phase error margin; and transmitting (535) an indication of the timing error margin and an indication of the phase error margin to the second network node

6. The method of Claim 5, wherein determining the timing error margin comprises selecting the timing error margin from a list of preconfigured candidate timing error margin values, and/or wherein determining the phase error margin comprises selecting the phase error margin from a list of preconfigured candidate phase error margin values.

7. The method of Claim 6, wherein determining the timing error margin comprises determining the timing error margin based on the phase error margin, or wherein determining the phase error margin comprises determining the phase error margin based on the time error margin.

8. The method of Claims 4-7, wherein the DL RSTD is a first DL RSTD of a plurality of DL RSTD, the method further comprising: determining (565) whether the first DL RSTD of the plurality of DL RSTD and a second DL RSTD of the plurality of DL RSTD have a joint timing error group based on the timing error margin and the phase error margin.

9. The method of Claim 8, wherein determining whether the first DL RSTD of the plurality of DL RSTD and the second DL RSTD of the plurality of DL RSTD have the joint timing error group comprises determining that the first DL RSTD of the plurality of DL RSTD and the second DL RSTD of the plurality of DL RSTD have the joint timing error group based on: determining that a timing error difference between the first DL RSTD and the second DL

RSTD is within to the timing error margin; and determining that a phase error difference between a first carrier phase measurement corresponding to the first DL RSTD and a second carrier phase measurement corresponding to the second DL RSTD is within the phase error margin.

10. The method of any of Claims 1-9, wherein the error group identifier for the DL RSTD and the corresponding DL carrier phase measurement comprises at least one of: a timing and phase error group, TPEG, identifier, ID, for both the DL RSTD and the corresponding DL carrier phase measurement; and a timing error group, TEG, ID for the DL RSTD and a phase error group, PEG, ID for the corresponding DL carrier phase, wherein the error group identifier for the reference time and the reference phase comprises at least one of: a TPEG ID for both the reference time and the reference phase; and a TEG ID for the reference time and a PEG ID for the reference phase.

11. A method of operating a first network node in a communications network that includes a communication device and a second network node, the method comprising: measuring (620) an uplink, UL, relative time of arrival, RTOA, and a corresponding UL carrier phase measurement on a UL sounding reference signal, SRS, received from the communication device; and transmitting (650) a joint report to second network node, the joint reporting including: an indication of the UL RTOA and the corresponding UL carrier phase measurement; and an indication of an error group identifier for the UL RTOA and the corresponding UL carrier phase measurement.

12. The method of Claim 11, further comprising: determining (640) the error group identifier for the UL RTOA and the corresponding UL carrier phase measurement.

13. The method of any of Claims 11-12, wherein the second network node is configured to provide a location management function, LMF.

14. The method of any of Claims 11-13, further comprising: receiving (610) configuration information from the second network node, the configuration information including an indication that the first network node jointly report the UL RTOA and the UL carrier phase measurement to the second network node.

15. The method of any of Claims 11-14, further comprising: determining (630) a timing error margin; determining (630) a phase error margin; and transmitting (635) an indication of the timing error margin and an indication of the phase error margin to the second network node.

16. The method of Claim 15, wherein determining the timing error margin comprises selecting the timing error margin from a list of preconfigured candidate timing error margin values, and/or wherein determining the phase error margin comprises selecting the phase error margin from a list of preconfigured candidate phase error margin values.

17. The method of Claim 16, wherein determining the timing error margin comprises determining the timing error margin based on the phase error margin, or wherein determining the phase error margin comprises determining the phase error margin based on the time error margin.

18. The method of Claims 14-17, wherein the UL RTOA is a first UL RTOA of a plurality of UL RTOA, the method further comprising: determining (645) whether the first UL RTOA of the plurality of UL RTOA and a second UL RTOA of the plurality of UL RTOA have a joint timing error group based the timing error margin and the phase error margin.

19. The method of Claim 18, wherein determining whether the first UL RTOA of the plurality of UL RTOA and the second UL RTOA of the plurality of UL RTOA have the joint timing error group comprises determining that the first UL RTOA of the plurality of UL RTOA and the second UL RTOA of the plurality of UL RTOA have the joint timing error group based on: determining that a timing error difference between the first UL RTOA and the second UL RTOA is within to the timing error margin; and determining that a phase error difference between a first carrier phase measurement corresponding to the first UL TDOA and a second carrier phase measurement corresponding to the second UL TDOA is within the phase error margin.

20. The method of any of Claims 11-19, wherein the error group identifier for the UL RTOA and the corresponding UL carrier phase measurement comprises at least one of: a timing and phase error group, TPEG, identifier, ID, for both the UL RTOA and the corresponding UL carrier phase measurement; and a timing error group, TEG, ID for the UL RTOA and a phase error group, PEG, ID for the corresponding UL carrier phase.

21. A method of operating a second network node in a communications network that includes a communication device and a first network node, the method comprising: receiving (720) a joint report including: an indication of a measurement; and an indication of an error group identifier for the measurement; determining (730) whether to combine the measurement with other measurements based on the error group identifier.

22. The method of Claim 21, wherein receiving the joint report comprises receiving the joint report from the communication device, the joint report including at least one of: a first combination of: an indication of a downlink, DL, reference signal time difference, RSTD, and a corresponding DL carrier phase measurement; and an indication of an error group identifier for the DL RSTD and the corresponding DL carrier phase measurement; and a second combination of: an indication of a reference time and a reference phase corresponding to a third network node; and an indication of an error group identifier of the reference time and the reference phase.

23. The method of Claim 21 , wherein receiving the j oint report comprises receiving the j oint report from the first network node, the joint report including: an indication of an uplink, UL, relative time of arrival, RTOA, and the corresponding UL carrier phase measurement; and an indication of an error group identifier for the UL RTOA and the corresponding UL carrier phase measurement.

24. The method of any of Claims 21-23, wherein the second network node is configured to provide a location management function, LMF.

25. The method of any of Claims 21-24, further comprising: transmitting (710) configuration information to the communication device or the first network node, the configuration information including an indication that the communication device or the first network node transmit the jointly report to the second network node.

26. The method of any of Claims 21-25, further comprising: receiving (725) an indication of a timing error margin and an indication of a phase error margin.

27. A communication device (900) adapted to perform operations comprising: measuring (520) a downlink, DL, reference signal time difference, RSTD, and a corresponding DL carrier phase measurement on a DL positioning reference signal, PRS, received from the first network node; and transmitting (570) a joint report to second network node, the joint reporting including at least one of: a first combination of: an indication of the DL RSTD and the corresponding DL carrier phase measurement; and an indication of an error group identifier for the DL RSTD and the corresponding DL carrier phase measurement; and a second combination of: an indication of a reference time and a reference phase corresponding to a third network node; and an indication of an error group identifier of the reference time and the reference phase.

28. The communication device of Claim 27, the operations further comprising any of the operations of Claims 2-10.

29. A computer program comprising program code to be executed by processing circuitry (902) of a communication device (900), whereby execution of the program code causes the communication device to perform operations comprising: measuring (520) a downlink, DL, reference signal time difference, RSTD, and a corresponding DL carrier phase measurement on a DL positioning reference signal, PRS, received from the first network node; and transmitting (570) a joint report to second network node, the joint reporting including at least one of: a first combination of: an indication of the DL RSTD and the corresponding DL carrier phase measurement; and an indication of an error group identifier for the DL RSTD and the corresponding DL carrier phase measurement; and a second combination of: an indication of a reference time and a reference phase corresponding to a third network node; and an indication of an error group identifier of the reference time and the reference phase.

30. The computer program of Claims 29, the operations further comprising any of the operations of Claims 2-10.

31. A computer program product comprising a non-transitory storage medium (910) including program code to be executed by processing circuitry (902) of a communication device (900), whereby execution of the program code causes the entity to perform operations comprising: measuring (520) a downlink, DL, reference signal time difference, RSTD, and a corresponding DL carrier phase measurement on a DL positioning reference signal, PRS, received from the first network node; and transmitting (570) a joint report to second network node, the joint reporting including at least one of: a first combination of: an indication of the DL RSTD and the corresponding DL carrier phase measurement; and an indication of an error group identifier for the DL RSTD and the corresponding DL carrier phase measurement; and a second combination of: an indication of a reference time and a reference phase corresponding to a third network node; and an indication of an error group identifier of the reference time and the reference phase.

32. The computer program product of Claim 31, the operations further comprising any of the operations of Claims 2-10.

33. A first network node (1000) adapted to perform operations comprising: measuring (620) an uplink, UL, relative time of arrival, RTOA, and a corresponding UL carrier phase measurement on a UL sounding reference signal, SRS, received from the communication device; and transmitting (670) a joint report to second network node, the joint reporting including: an indication of the UL RTOA and the corresponding UL carrier phase measurement; and an indication of an error group identifier for the UL RTOA and the corresponding UL carrier phase measurement.

34. The first network node of Claim 33 further adapted to perform any of the operations of Claims 12-20.

35. A computer program comprising program code to be executed by processing circuitry (1002) of a first network node (1000), whereby execution of the program code causes the network node to perform operations comprising: measuring (620) an uplink, UL, relative time of arrival, RTOA, and a corresponding UL carrier phase measurement on a UL sounding reference signal, SRS, received from the communication device; and transmitting (670) a joint report to second network node, the joint reporting including: an indication of the UL RTOA and the corresponding UL carrier phase measurement; and an indication of an error group identifier for the UL RTOA and the corresponding UL carrier phase measurement.

36. The computer program of Claim 35, the operations further comprising any operations of Claims 12-20.

37. A computer program product comprising a non-transitory storage medium (1004) including program code to be executed by processing circuitry (1002) of a first network node (1000), whereby execution of the program code causes the first network node to perform operations comprising: measuring (620) an uplink, UL, relative time of arrival, RTOA, and a corresponding UL carrier phase measurement on a UL sounding reference signal, SRS, received from the communication device; and transmitting (670) a joint report to second network node, the joint reporting including: an indication of the UL RTOA and the corresponding UL carrier phase measurement; and an indication of an error group identifier for the UL RTOA and the corresponding UL carrier phase measurement.

38. The computer program product of Claim 37 further comprising any of the operations of Claims 12-20.

39. A second network node (1000) adapted to perform operations comprising: receiving (720) a joint report including: an indication of measurement; and an indication of an error group identifier for the measurement; determining (730) whether to combine the measurement with other measurements based on the error group identifier.

40. The first network node of Claim 39 further adapted to perform any of the operations of Claims 22-26.

41. A computer program comprising program code to be executed by processing circuitry (1002) of a second network node (1000), whereby execution of the program code causes the network node to perform operations comprising: receiving (720) a joint report including: an indication of measurement; and an indication of an error group identifier for the measurement; determining (730) whether to combine the measurement with other measurements based on the error group identifier.

42. The computer program of Claim 41, the operations further comprising any operations of Claims 22-26.

43. A computer program product comprising a non-transitory storage medium (1004) including program code to be executed by processing circuitry (1002) of a second network node (1000), whereby execution of the program code causes the second network node to perform operations comprising: receiving (720) a joint report including: an indication of measurement; and an indication of an error group identifier for the measurement; determining (730) whether to combine the measurement with other measurements based on the error group identifier.

44. The computer program product of Claim 43 further comprising any of the operations of Claims 22-26.