Carrier / positioning frequency layer configuration for carrier phase measurements performed with conventional positioning measurements

Abstract

A communication device may obtain (410) configuration information to perform carrier phase measurements along with time difference measurements. The communication device may further perform (420) carrier phase measurements along with time difference measurements based on the configuration information. The communication device may also perform (430) an operational task based on the carrier phase measurement and the time difference measurement.

Description

Technical Field

[0001] This disclosure relates to wireless communication systems, and more specifically, to a carrier / positioning frequency layer (“PFL”) configuration for carrier phase measurements performed in conjunction with conventional positioning measurements. Background Technology

[0002] This disclosure relates to wireless communication systems, and more specifically, to a carrier / positioning frequency layer (“PFL”) configuration for carrier phase measurements performed in conjunction with conventional positioning measurements.

[0003] Figure 1 An example of a new radio (“NR”) network (e.g., a fifth-generation (“5G”) network) is shown, including a 5G core (“5GC”) network 130, network nodes 120a-b (e.g., 5G base stations (“gNB”), and multiple communication devices 110 (also referred to as user equipment (“UE”)).

[0004] Location has been a central theme in LTE standardization since 3GPP Release 9. The primary objective is to meet regulatory requirements for emergency call location. Location in NR was proposed by... Figure 1 The architecture shown supports this. The LMF is the location node in the NR. The location node and gNodeB also interact via the NRPPa protocol. Interaction between the gNodeB and the device is supported via the Radio Resource Control ("RRC") protocol. Summary of the Invention

[0005] According to some embodiments, a method for operating a communication device is provided. The method includes obtaining configuration information to perform carrier phase measurement along with time difference measurement. The method further includes performing carrier phase measurement along with time difference measurement based on the configuration information. The method also includes performing an operational task based on the carrier phase measurement and the time difference measurement.

[0006] According to other embodiments, a method for operating a network node is provided. The network node is configured to provide a location server. The method includes configuring a communication device to perform a carrier phase difference measurement along with a time difference measurement. The method includes transmitting to the communication device an indication of information to be considered when performing the carrier phase difference measurement along with the time difference measurement. The method includes receiving a measurement report from the communication device, the measurement report including the carrier phase measurement performed together with the time difference measurement.

[0007] Certain aspects of these embodiments can provide technical advantages. In some embodiments, the carrier phase difference measurement is consistent because it is performed by the UE on the same carrier / PFL. The location server will know which carrier / PFL was used. This is necessary for the location server to be able to compare measurements from different UEs, including the Positioning Reference Unit (“PRU”) UE. The auxiliary and measurement configuration data is suitable for situations where the UE is configured to perform time difference measurements (e.g., RSTD measurement) along with carrier phase difference measurements (e.g., RSCPD measurement). The UE completes the RSCPD measurement along with the RSTD measurement without additional delay. Attached Figure Description

[0008] The accompanying drawings (included to provide a further understanding of this disclosure and incorporated into and constituting a part of this application) illustrate certain non-limiting embodiments of the inventive concept. In the drawings: Figure 1 This is a schematic diagram illustrating an example of a fifth-generation (“5G”) network; Figure 2 This is a block diagram illustrating an example of an NR architecture used to support positioning in NR; Figure 3 This is a graph illustrating an example of carrier phase measurements affected by transmit phase offset and receive phase offset; Figure 4 This is a flowchart illustrating examples of operations performed by a communication device according to some embodiments; Figure 5 This is a flowchart illustrating examples of operations performed by a network node according to some embodiments; Figure 6 This is a block diagram of a communication system according to some embodiments; Figure 7 This is a block diagram of a user equipment according to some embodiments; Figure 8 This is a block diagram of network nodes according to some embodiments; Figure 9 This is a block diagram of a host according to some embodiments, the host may be Figure 6 An example of a host computer; Figure 10 This is a block diagram of a virtualized environment according to some embodiments; and Figure 11 A communication diagram is shown, illustrating a host communicating with a user equipment via a network node through a partial wireless connection, according to some embodiments. Detailed Implementation

[0009] Some 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, wherein examples of embodiments of the inventive concept are shown. However, the inventive concept can be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided to make this disclosure thorough and complete and to fully convey the scope of the inventive concept to those skilled in the art. It should also be noted that these embodiments are not mutually exclusive. Components from one embodiment may be assumed to be present / used in another embodiment.

[0010] Figure 2 An example of an NR architecture for supporting NR positioning is shown. In this example, the location node in NR is a location management function (“LMF”). Interaction also exists between the location node and the gNodeB via NR Positioning Protocol A (“NRPPa”). Interaction between the gNodeB and the device is supported via the Radio Resource Control (“RRC”) protocol, while the location node interfaces with the UE via the LTE Positioning Protocol (“LPP”). LPP is common for both NR and LTE. Although... Figure 2 Both gNB and ng-eNB are shown, but both may not always be present. Furthermore, when both gNB and ng-eNB are present, NG-C is usually only present in one of them.

[0011] LTE supports: 1) Enhanced Cell Identifier (“ID”); 2) Assisted Global Navigation Satellite System (“GNSS”); 3) Observation Time Difference of Arrival (“OTDOA”); 4) Uplink (“UL”) Time Difference of Arrival (“TDOA”); and 5) Sensor technologies. The Enhanced Cell ID includes cell ID information that associates the device with the serving area of ​​the serving cell, as well as additional information then used to determine a finer-grained location. Assisted GNSS information can be retrieved by the device and is supported by auxiliary information provided to the device from (“E-SMLC”). OTDOA includes the device estimating the time difference of reference signals from different base stations and sending the information to the E-SMLC for multilateral positioning. UTDOA includes the device requesting the transmission of a specific waveform detected by multiple location measurement units (e.g., eNBs) at known locations. These measurements are forwarded to the SMLC for multilateral positioning. LTE sensor technologies may include a bio-pressure sensor providing the device’s vertical position and an inertial motion unit (“IMU”) providing displacement.

[0012] Compared to LTE, NR positioning benefits from greater bandwidth and finger beamforming, and can locate the UE with higher accuracy. NR currently supports positioning procedures related to the following radio access technologies (“RATs”): 1) Downlink Time Difference of Arrival (“DL-TDOA”); 2) Multiple 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”).

[0013] The DL TDOA positioning process utilizes the downlink (“DL”) reference signal time difference (“RSTD”) of downlink signals received from multiple transmission points (“TPs”) (and optional DL positioning reference signal (“PRS”) reference signal received power (“RSRP”) at the UE). The UE uses auxiliary data received from the positioning server to measure the DL RSTD (and optional DL PRS RSRP) of the received signal, and the resulting measurement, along with other configuration information, is used to position the UE relative to neighboring TPs.

[0014] The multi-RTT positioning process utilizes UE receive (“Rx”)-transmit (“Tx”) measurements and downlink signals received from multiple transmit / receive points (“TRPs”) as measured by the UE, as well as gNB Rx-Tx measurements and UL probe reference signals (“SRS”)-RSRPs measured at multiple TRPs of uplink signals transmitted from the UE.

[0015] The UL TDOA positioning process utilizes UL TDOA (and optional UL SRS-RSRP) on multiple RPs of the uplink signal transmitted from the UE. The RP uses auxiliary data received from the positioning server to measure the UL TDOA (and optional UL SRS-RSRP) of the received signal, and the resulting measurements, along with other configuration information, are used to estimate the UE's location.

[0016] At the UE, the DL AoD positioning process utilizes the measured DL PRSRSRP of downlink signals received from multiple TPs. The UE uses auxiliary data received from the positioning server to measure the DL PRSRSRP of the received signals, and the resulting measurement, along with other configuration information, is used to locate the UE relative to neighboring TPs.

[0017] The UL AoA positioning process utilizes the vertex of arrival and azimuth angle measured at multiple receiving points (“RPs”) of the uplink signal transmitted from the UE. The RPs use auxiliary data received from the positioning server to measure the A-AoA and Z-AoA of the received signal, and the resulting measurements, along with other configuration information, are used to estimate the UE's position.

[0018] NR-ECID positioning refers to techniques that use additional UE measurements and / or NR radio resources and other measurements to improve UE location estimation.

[0019] Positioning modes can be categorized into three areas: 1) UE-assisted; 2) UE-based; and 3) Independent. UE-assisted refers to the UE performing measurements with or without network assistance and sending these measurements to an E-SMLC capable of location calculation. UE-based refers to the UE performing measurements and calculating its own location with network assistance. Independent refers to the UE performing measurements and calculating its own location without network assistance.

[0020] Several challenges exist. For Reference Signal Time Difference (“RSTD”) measurements, the Location Management Function (“LMF”) provides the following information as part of the auxiliary data for positioning measurements: 1) Positioning Reference Signal (“PRS”) identifier (“ID”); 2) PRS set ID; and 3) PRS resource ID. Upon receiving the auxiliary data, the UE can perform RSTD measurements on reference and neighboring transport / receive points (“TRPs”) and report them to the LMF for location estimation. The UE can perform RSTD measurements by considering the reference TRP indicated in the auxiliary data or by selecting one of the TRPs in the auxiliary data as the reference TRP and reporting the performed RSTD measurements to the LMF. The auxiliary data provided to the UE by the LMF does not indicate the positioning frequency layer (“PFL”) to be considered when performing RSTD measurements. At this point, when performing RSTD measurements during a positioning session, the UE is free to choose the reference TRP and PFL to consider, where the reference TRP and neighboring TRP can be in different PFLs.

[0021] It is unclear how to determine the PFL of carrier phase measurement and / or carrier phase difference measurement.

[0022] Certain aspects of this disclosure and its embodiments may provide solutions to these or other challenges. In some embodiments, the UE performs carrier phase difference measurements on a reference signal of the same carrier / PFL operated by a reference TRP and a neighboring TRP. Time difference measurements are performed on the same carrier / PFL where the UE performs RSCPD, such as RSTD measurements reported together with the carrier phase difference measurements (e.g., as reference signal carrier phase difference (“RSCPD”)). When the UE is configured to perform carrier phase difference and time difference measurements together, signaling details between the location server and the UE are disclosed. When carrier phase difference and time difference measurements cannot be performed together by the UE, UE behavior is disclosed.

[0023] Timing measurements used for UE positioning can be unidirectional or bidirectional. A first node (Node 1) can use unidirectional timing measurements to measure the transmission timing of a signal transmitted by Node 1, or the reception timing of a signal received by Node 1 from a second node (Node 2). Node 1 can use bidirectional timing measurements to measure the relationship between the transmission timing of a signal transmitted by Node 1 and the reception timing of a signal received by Node 1 from Node 2. An example of this relationship is the difference between transmission and reception timing. In one example, Node 1 can measure the absolute reception timing of a signal, and / or it can measure the reception timing of a signal relative to a reference time. In additional or alternative examples, Node 1 can measure the absolute transmission timing of a signal, and / or it can measure the transmission timing of a signal relative to a reference time.

[0024] In the New Radio (“NR”), several timing measurements for positioning are specified. An example of a bidirectional timing measurement is the round-trip time (“RTT”). Specific examples of bidirectional timing measurements are the UE receive-transmit (“Rx-Tx”) time difference, the gNB Rx-Tx time difference, and time advance (“TA”). Examples of unidirectional timing measurements are the reference signal time difference (“RSTD”) performed by the UE and the uplink (“UL”) relative arrival time (“RTOA”) performed by the base station.

[0025] The following NR positioning measurements are specified in relation to timing performed by the UE: RSTD; and UE Rx-Tx time difference.

[0026] RSTD is the reference signal time difference between location node j and reference location node i. It is measured on the downlink (“DL”) location reference signal (“PRS”) and always involves two cells (cells are sometimes used interchangeably with TRP in this document).

[0027] The time difference between UE Rx and Tx can be defined as T. UE-RX -T UE-TX T UE-RXThis is the timing of the downlink subframe #i received by the UE from the positioning node, defined by the first detected path in time. It is measured based on the PRS signal received from the gNB. UE-TX It is the UE transmission timing of uplink subframe #j, which is the closest in time to subframe #i received from the positioning node.

[0028] The following NR positioning measurements related to timing performed by the base station (e.g., gNB) are specified: gNB Rx-Tx time difference; TA; and UL·RTOA.

[0029] The time difference between gNB Rx-Tx can be defined as T. gNB-RX - T gNB-TX T gNB-RX It is the timing of the uplink subframe #i received by the positioning node, containing the SRS associated with the UE, defined by the first detected path in time. It is measured on the SRS signal received from the UE. gNB-TX It is the timing of the location node transmission of the downlink subframe #j that is closest in time to the subframe #i received from the UE.

[0030] TA (T) ADV () can be defined as time difference T ADV = (T gNB-RX –T gNB-TX T gNB-RX It is the timing of the uplink subframe #i containing the PRACH transmitted from the UE, received by the Transmit and Receive Point (TRP)

[18] , defined by the first detected path in time. gNB-TX It is the TRP transmission timing of the downlink subframe #j that is closest in time to the subframe #i received from the UE. The detected PRACH is used to determine the start of a subframe containing that PRACH.

[0031] The UL RTOA can be defined relative to a configurable reference time as the start of subframe i of the SRS received in location node j. For example, node 1 (e.g., a base station) measures the reception time of the signal transmitted by the UE relative to the reference time.

[0032] Assuming the link has one transmitter and one receiver, the transmitted passband signal can be given by the following formula: , in Indicates baseband signal, and Indicates the carrier frequency. (Item) The offset is caused by imperfect synchronization of Tx, which includes the RF phase difference compared to an ideal oscillator.

[0033] Assuming line-of-sight (“LOS”) conditions and no multipath, the channel can be given by the following equation: , in It is transmission delay, It is the speed of light, and This is the LOS path length between the transmitter and receiver. The received bandpass signal is a convolution: After the change, the received baseband signal is: Among them, items This offset is due to imperfect synchronization of Rx, and it includes the RF phase difference compared to an ideal oscillator. The carrier phase measurement for this transmission will return the phase: (1) The above items Corresponding to analog-to-digital arithmetic, this ensures that the measured phase is within the range Inside.

[0034] Figure 3 An example of carrier phase measurement affected by transmit phase offset and receive phase offset is shown.

[0035] In the following text, the terms "Tx phase offset" or "transmission phase offset" will be used to refer to... And the terms "Rx phase offset" or "receive phase offset" are used for .

[0036] For positioning, the following carrier phase measurements can be used: carrier phase measurement; and carrier phase difference measurement.

[0037] Carrier phase measurements may include phase measurements of the carrier / PFL used by the TRP for reference signal transmission. An example of a carrier phase measurement is the reference signal carrier phase (“RSCP”).

[0038] Carrier phase difference measurement can include the difference between the carrier phase measurements of the reference TRP and the neighboring TRP used for reference signal transmission on the carrier / PFL. Assume the carrier phase measured by the UE on the reference signal transmitted on the carrier / PFL operated by the reference TRP is... And the carrier phase measured by the UE on the reference signal transmitted on the carrier / PFL operated by the neighboring TRP is Then, carrier phase difference measurement (“CPDM”) can be expressed as ( In other or alternative examples, CPDM can be represented as ( CPDM can also be indicated as an absolute value (e.g., |( ) | or | ( CPDM can also be called carrier phase difference measurement, carrier phase relative measurement, and relative carrier phase measurement. In some examples, carrier phase difference measurement is the reference signal carrier phase difference (“RSCPD”).

[0039] The UE can perform carrier phase and carrier phase difference measurements on the carrier / PFL used by the TRP to transmit reference signals (such as PRS, CSI-RS, and CS-RS). Carrier phase or carrier phase difference measurements can be expressed in degrees (e.g., π / 6, π / 3, and π / 2).

[0040] In some embodiments, the UE obtains information about at least one carrier / PFL based on a standard autonomously or by receiving information from a location server (e.g., LMF) for carrier phase difference measurement (e.g., RSCPD measurement). The indicated carrier / PFL is common between the reference TRP and adjacent TRPs.

[0041] In some examples of autonomous carrier / PFL selection, the UE obtains a configuration including two or more carriers / PFLs from a location server (e.g., LMF) and selects at least one of the configured carriers / PFLs for carrier phase difference measurements, such as RSCPD measurements. In some examples of this standard, the UE selects at least one carrier / PFL to perform a common RSCPD measurement between a reference TRP and a neighboring TRP. In additional or alternative examples of this standard, if the UE is configured to report RSCPD along with RSTD, the UE selects the same carrier frequency / PFL to perform both RSCPD and RSTD. In this example, the UE performs both RSCPD and RSTD by measuring a reference signal (e.g., PRS) transmitted by the reference TRP and neighboring TRPs on the same / common carrier / PFL.

[0042] In additional or alternative embodiments, the UE performs carrier phase difference measurements such as RSCPD and time difference measurements such as RSTD on the acquired carrier / PFL (e.g., autonomously or based on indications received from a location server (e.g., LMF)). The UE can use the results of the performed / acquired measurements to perform one or more operational tasks.

[0043] Examples of tasks include: the UE using the results to determine UE location, and the UE reporting RSCPD measurements along with RSTD measurements in its measurement report to the location server. In the measurement report, the UE may indicate to the location server which carrier / PFL was selected by the UE and used for measurement. The indicated carrier / PFL may be the carrier / PFL indicated by the location server in auxiliary data, or it may be the carrier / PFL selected by the UE from carrier / PFLs configured by the location server. In both cases, the indicated carrier / PFL may be common between the reference TRP and the neighboring TRP (e.g., RSCPD is measured on a reference signal (e.g., PRS) transmitted on the same carrier frequency by the reference TRP and the neighboring TRP).

[0044] In additional or alternative embodiments, the UE is configured by a location server (e.g., LMF), or the UE determines its fallback behavior based on predefined rules if the UE fails to perform RSCPD measurements on the carrier / PFL indicated by the location server.

[0045] In some examples, if the UE cannot perform RSCPD measurements on the carrier / PFL indicated by the location server, the UE only reports the RSTD measurement results to the location server. For example, this can be considered a partial measurement failure, i.e., only RSCPD fails. For instance, if the UE cannot detect the carrier phase or cannot reliably detect the carrier phase of the reference signal transmitted by the reference TRP and / or the reference signal transmitted by adjacent TRPs, the UE may be unable to perform RSCPD. The estimated / measured carrier phase is reliable if it is within the expected carrier phase value or the expected carrier phase difference (e.g., configured by the location server).

[0046] In an additional or alternative example, if the UE cannot perform RSTS measurements on the carrier / PFL indicated by the location server, the UE will not report the RSCPD measurement result to the location server, even if the UE has already measured RSCPD. For example, in this case, the UE declares the measurement failed, meaning both RSCPD and RSTD failed. For example, if the estimated RSTD is outside the expected RSTD value (e.g., configured by the location server), the UE may be unable to perform RSTS.

[0047] In some embodiments, the communication network may include a UE, a first network node (“NW1”) (which may serve as a TRP, reference TRP, or neighbor TRP for transmitting reference signals (e.g., PRS) for positioning measurements), and a second network node (“NW2”) (which may be a location server that provides auxiliary data for positioning measurements to the UE).

[0048] Location measurements can be one of RSTD, UE Rx-Tx, RSTD + carrier phase difference, or UE Rx-Tx + carrier phase measurement. The UE can also be interchangeably referred to as the target device or the radio device. The TRP can also be interchangeably referred to as a base station, access point, gNB, eNB, satellite access node (“SAN”), high-altitude platform station (“HAPS”), and integrated access and backhaul (“IAB”) node. The location server can also be interchangeably referred to as a location node, SMLC, E-SMLC, and LMF. The NW2 provides auxiliary data to the UE via higher-layer signaling (e.g., LPP messages). After performing location measurements based on the configuration / auxiliary data provided to the UE by the NW2, the UE reports the location measurements to the NW2. When performing location measurements configured by the NW2, the UE can be in any RRC state (e.g., any of the RRC_CONNECTED, RRC_INACTIVE, and RRC_IDLE states). While the UE is performing location measurements configured by the NW2, the auxiliary data provided to the UE by the NW2 remains valid regardless of the UE's RRC state. NW2 knows that NW1 uses PFL to transmit reference signals for positioning measurements.

[0049] The term Positioning Frequency Layer (“PFL”) may be referred to herein as carrier frequency, component carrier (“CC”), frequency layer, serving carrier, or frequency channel. A PFL belongs to a frequency band, which may include one or more PFL / carrier frequencies based on its passband (e.g., the size of the band in the frequency domain) and / or the bandwidth of the carrier and / or the channel grating. Network nodes transmit PFL / carrier frequency related information to the UE via messages (e.g., RRCs) using channel numbers or identifiers. Examples of predefined channel numbers or identifiers are the absolute radio frequency channel number (“ARFCN”), NR-ARFCN, PFL identifier, absoluteFrequencyPointA (absolute frequency location of the reference resource block), and the number of PRBs.

[0050] In some embodiments, the UE may receive and use a carrier / PFL indication from auxiliary data for carrier phase measurement from a location server. In some examples, the UE receives a PFL configuration to be considered for carrier phase measurement from the auxiliary data of the location server (e.g., LMF). In this example, the UE is configured by the location server to perform carrier phase measurement (e.g., carrier phase difference measurement) along with time difference measurement (e.g., RSTD).

[0051] In additional or alternative examples, the UE obtains configuration information (e.g., auxiliary data) to perform carrier phase measurements (e.g., carrier phase difference measurement (“CPDM”) along with time difference measurements (e.g., RSTD). The configuration information may indicate to the UE that one or more PFLs of CPDM need to be performed on it. The UE obtains the configuration information by receiving messages, or the UE obtains the configuration information autonomously or at least partially or entirely based on rules.

[0052] In one option, the UE receives a message from the NW2 (e.g., a location server) indicating information about the carrier / PFL to be considered / used when performing carrier phase measurements (e.g., carrier phase difference measurements) along with time difference measurements (e.g., RSTD). In this step, the UE receives from the NW2 an indication of the single carrier / PFL common between the reference and neighbor TRPs or TRP lists or PRS ID lists, for the UE to consider when performing carrier phase measurements (e.g., carrier phase difference measurements) along with time difference measurements (e.g., RSTD). In this step, the NW2 may not signal explicit indications of the reference TRP or PRS ID to the UE.

[0053] In the additional or alternative option, the UE does not receive from the NW2 an indication of the carrier / PFL to be considered when performing carrier phase measurement (CPDM) (e.g., carrier phase difference measurement) along with time difference measurement (e.g., RSTD). Instead, the NW2 configures the UE to select one of the carrier / PFLs to perform the measurement. Therefore, the UE is configured by the NW2 to have at least two carrier / PFLs, from which the UE itself selects one for CPDM. Thus, in this case, the UE autonomously selects the same carrier / PFL in both the reference TRP and the neighbor TRP to perform carrier phase measurement, such as carrier phase difference measurement along with time difference measurement, such as RSTD. However, the UE receives auxiliary data from the NW2 instructing the UE to perform CPDM measurement along with RSTD.

[0054] In an additional or alternative example, the UE performs carrier phase measurements (e.g., carrier phase difference measurements) along with time difference measurements (e.g., RSTD) based on the configuration information obtained in the previous steps. The UE performs joint CPDM and RSTD by treating one of the TRPs or dl-PRS-IDs in the PFL in the auxiliary data as a reference TRP. In this step, the UE can select a TRP or dl-PRS-ID that may or may not belong to its serving cell.

[0055] In additional or alternative examples, the UE uses the obtained CPDM and RSTD results to perform one or more operational tasks (e.g., reporting the carrier phase difference measurement along with the timing difference measurement to NW2, or using the results of the performed measurements to determine the UE's location).

[0056] In additional or alternative embodiments, a list of multiple carriers / PFLs is used to measure the carrier phase difference.

[0057] In some examples, the location server configures the UE to perform time difference measurements, such as RSTD. The UE measures and reports multiple RSTD measurements (e.g., via a list nr-DL-TDOA-MeasList-r16 in the information element NR-DL-TDOA-SignalMeasurementInformation as defined in 3GPP TS 37.355 v17.4.0). The multiple RSTD measurements are relative to the “RSTD Reference” TRP given by dl-PRS-ReferenceInfo in the information element NR-DL-TDOA-SignalMeasurementInformation.

[0058] In additional or alternative examples, the location server configures the UE to perform carrier phase difference measurements along with time difference measurements such as RSTD. In one case, for each of the multiple RSTD measurements in list nr-DL-TDOA-MeasList-r16, the UE reports the corresponding carrier phase difference measurement, such as RSCPD measurement.

[0059] In an additional or alternative example, the UE includes the RSCPD measurement along with the DL RSTD measurement in nr-DL-TDOA-MeasElement-r16. A second alternative is that the UE can report another list with RSCPD measurements, where each element in the list has a corresponding element in nr-DL-TDOA-MeasElement-r16.

[0060] The same reference TRP (e.g., the “RSTD Reference” TRP given by dl-PRS-ReferenceInfo) is used for all RSTD and RSCPD measurements.

[0061] Considering the nth RSTD measurement element in list nr-DL-TDOA-MeasList-r16 and the corresponding nth RSCPD measurement in the new list with RSCPD measurements, the carrier / PFL for the nth RSCPD measurement is determined as follows: 1) The reference carrier phase measured on the reference TRP is measured using the same carrier / PFL used to measure the neighbor TRP, which is given by 'dl-PRS-ID-r16' in the nth RSTD measurement element in list nr-DL-TDOA-MeasList-r16; 2) The carrier phase measured on the neighbor TRP uses the same carrier / PFL used to measure the neighbor TRP, given by 'dl-PRS-ID-r16' in the nth RSTD measurement element in list nr-DL-TDOA-MeasList-r16; and 3) The nth RSCPD measurement is then determined by the difference between the neighbor TRP carrier phase and the reference carrier phase. In additional or alternative examples, which carrier / PFL is used to measure the reference carrier phase and neighbor TRP carrier phase of the nth RSCPD measurement is implicitly determined by the carrier / PFL used to measure the neighbor TRP in the nth RSTD measurement.

[0062] In additional or alternative embodiments, auxiliary data for carrier phase measurement is provided to the UE.

[0063] In some examples, the location server NW2 indicates in the auxiliary data given to the UE that the carrier / PFL will be considered for carrier phase measurement (e.g., carrier phase difference measurement) along with time difference measurement (e.g., RSTD). In this example, the location server NW2 configures the UE to perform carrier phase measurement (e.g., carrier phase difference measurement) along with time difference measurement (e.g., RSTD).

[0064] In additional or alternative examples, NW2 configures the UE to perform carrier phase difference measurements along with time difference measurements such as RSTD.

[0065] In one option, NW2 indicates the PFL to be considered when performing carrier phase difference measurements along with time difference measurements (such as RSTD). In this step, NW2 indicates the carrier / PFL or TRP list or PRS ID list to be considered by the UE when performing carrier phase difference measurements along with time difference measurements such as RSTD. NW2 does not explicitly indicate a reference TRP or PRS ID.

[0066] In the additional or alternative options, NW2 does not indicate the carrier / PFL to be considered when performing carrier phase difference measurements such as RSCPD along with time difference measurements such as RSTD. Instead, NW2 indicates that the UE determines the carrier / PFL, but the PFL in the reference TRP and the neighbor TRP must be the same.

[0067] In an additional or alternative example, the NW2 receives a measurement report from the UE. The measurement report includes a carrier phase difference measurement performed along with a time difference measurement (e.g., RSTD). The NW2 also receives an indication of the carrier / PFL used to perform the carrier phase difference measurement along with the time difference measurement.

[0068] In additional or alternative embodiments, the TRP indication is included in the auxiliary data used for carrier phase measurement.

[0069] In some examples, the auxiliary data indicates to the UE that the TRP used for carrier phase measurement should be considered. In this example, the UE is configured to perform carrier phase measurements, such as carrier phase difference measurement along with time difference measurement.

[0070] In an additional or alternative example, the UE receives auxiliary data from the NW2 to perform carrier phase difference measurement (e.g., RSCPD) along with time difference measurement (e.g., RSTD) by taking into account the reference TRP and neighbor TRP indicated in the auxiliary data.

[0071] In some options, the NW2 configures the UE to perform carrier phase difference measurement (e.g., RSCPD) along with time difference measurement (e.g., RSTD).

[0072] In an additional or alternative option, the NW2 configures the UE to indicate that if the carrier phase difference measurement using the indicated auxiliary data fails, the UE may only report time difference measurements such as RSTD measurements, and not carrier phase difference measurements such as RSCPD.

[0073] In the additional or alternative option, NW2 indicates the reference TRP to be considered when performing carrier phase difference measurement along with time difference measurement. In this step, NW2 does not explicitly indicate the carrier / PFL, but rather implicitly does so by indicating the reference TRP via dl-PRS-ID, for the UE to consider when performing carrier phase difference measurement along with time difference measurement. NW2, along with the dl-PRS-ID of the reference TRP, also indicates the dl-PRS-ID of the neighboring TRP to be considered by the UE when performing carrier phase difference measurement along with time difference measurement.

[0074] In some examples, NW2 can indicate a list of dl-PRS-IDs corresponding to a reference TRP and neighbor TRPs for a carrier / PFL.

[0075] In additional or alternative examples, NW2 may indicate multiple ([2, 4]) lists of dl-PRS-IDs for the reference TRP and neighboring TRPs, with each list corresponding to a carrier / PFL. In this case, the UE can select one list.

[0076] In some options (where reporting only time difference measurements is not indicated as a fallback), the UE reports carrier phase difference measurements along with time difference measurements to the NW2. In the measurement report, if the UE can select one of multiple carriers / PFLs for carrier phase difference measurements, the UE indicates the carrier / PFL used for the carrier phase difference measurement (e.g., RSCPD measurement). For example, carrier / PFL information can be obtained from the dl-PRS-ID of the reference TRP. If the UE cannot detect the reference TRP indicated in the auxiliary data, the UE selects one of the TRPs in the auxiliary data as the reference TRP and reports only the time difference measurement, such as the RSTD measurement.

[0077] In the additional or alternative options (indicating a fallback for reporting only time difference measurements), the UE reports the carrier phase difference measurement along with the time difference measurement to the NW2. In the measurement report, if the UE can select one of multiple carriers / PFLs for carrier phase difference measurement, the UE indicates the carrier / PFL it uses for carrier phase difference measurement (e.g., RSCPD), for example, carrier / PFL information can be obtained from the dl-PRS-ID of the reference TRP. If the UE cannot detect the reference TRP indicated in the auxiliary data, and the UE is instructed that if carrier phase difference measurement cannot be performed, the NW2 can receive only time difference measurements such as RSTD measurements, the UE selects one of the TRPs in the auxiliary data as the reference TRP and reports only the time difference measurement. If the UE is instructed that the NW2 is not interested in time difference-only (e.g., RSTD) measurements, the UE reports a measurement failure.

[0078] In some embodiments, the UE receives auxiliary data from the NW2 to perform carrier phase difference measurements such as RSCPD along with time difference measurements such as RSTD, but cannot perform the measurements. According to the present invention, the UE NW2 performs the following steps.

[0079] In some examples, the UE receives auxiliary data from the NW2. If the UE cannot receive the reference signal used for positioning in the carrier / PFL indicated in the auxiliary data, or the reference TRP indicated in the auxiliary data, or the reference PRS ID indicated in the auxiliary data, the UE does not perform a carrier phase difference measurement or a time difference measurement, or a carrier phase difference measurement together with a time difference measurement, and reports a measurement failure to the NW2.

[0080] In additional or alternative examples, the UE requests updated assistance to perform carrier phase difference measurement (e.g., RSCPD) along with time difference measurement (e.g., RSTD).

[0081] In the additional or alternative examples, the UE receives updated auxiliary data from the NW2. The UE performs carrier phase difference measurements such as RSCPD along with time difference measurements such as RSTD and reports them to the NW2.

[0082] In some embodiments, when configuring auxiliary data for carrier phase difference measurement, the NW2 provides a default or first configured carrier / PFL as a reference carrier / PFL. In this case, the UE does not report any carrier / PFL used for measurement because it is implicitly derived by the NW2.

[0083] In some examples, NW2 can also provide a restricted configuration where only one carrier / PFL is configured when positioning requires carrier phase difference measurement along with time difference measurement. This is also implicitly derived in this restricted case.

[0084] In additional or alternative examples, NW2 can also provide a preferred carrier / PFL for carrier phase measurement. Therefore, the UE will perform carrier phase measurement in such a preferred carrier / PFL, which can be a different carrier / PFL, where time difference measurements such as RSTD are performed.

[0085] Now, based on some embodiments of the inventive concept, reference will be made to... Figure 6 The flowchart is used to discuss the communication device 700 (using... Figure 7 The structure of the module (implementation) is used for operations. For example, a module can be stored in... Figure 7 The memory 710 contains these modules, and these modules can provide instructions such that when the corresponding communication device processing circuit 702 executes the instructions of the module, the communication device 700 performs the corresponding operation of the flowchart.

[0086] Figure 4 An example of an operation performed by a communication device is shown.

[0087] In block 410, processing circuitry 702 obtains configuration information. This configuration information can be used to perform carrier phase measurements along with time difference measurements. In some embodiments, obtaining the configuration information includes receiving messages from a network node configured to provide a location server. In additional or alternative embodiments, obtaining the configuration information includes determining configuration information from a list of potential configuration information.

[0088] In block 420, processing circuitry 702 performs carrier phase measurement along with time difference measurement based on configuration information. In some examples, carrier phase measurement includes carrier phase difference measurement (CPDM). Time difference measurement includes reference signal time difference (RSTD).

[0089] In additional or alternative embodiments, the configuration information includes an indication of the location frequency layer (PFL) on which the communication device is instructed to perform carrier phase measurements. In some examples, the PFL includes a single PFL shared between a reference node and neighboring nodes to be considered when performing carrier phase measurements. In additional or alternative examples, the reference node is a reference transmit-receive point (TRP). In additional or alternative examples, the neighboring node is a neighboring TRP.

[0090] In additional or alternative embodiments, performing carrier phase measurement along with time difference measurement includes: 1) measuring the reference carrier phase on the reference TRP using the carrier / PFL used to measure the neighboring TRP; 2) measuring the carrier phase on the neighboring TRP using the carrier PFL used to measure the neighboring TRP; and 3) determining the reference signal carrier phase difference (RSCPD) measurement based on the difference between the carrier phase and the reference carrier phase.

[0091] In additional or alternative embodiments, performing carrier phase measurement along with time difference measurement includes: 1) failing to perform carrier phase measurement or time difference measurement; 2) requesting updated configuration information; and 3) re-performing carrier phase measurement along with time difference measurement.

[0092] In block 430, processing circuitry 702 performs operational tasks based on carrier phase measurements and time difference measurements. In some embodiments, performing operational tasks includes reporting the results of performing carrier phase measurements along with time difference measurements. In additional or alternative embodiments, performing operational tasks includes determining the location of a communication device.

[0093] For some embodiments of communication devices and related methods, from Figure 6 Various operations in the flowchart can be optional.

[0094] Now, based on some embodiments of the inventive concept, reference will be made to... Figure 7-8 The flowchart will be used to discuss the operation of RAN node 800 (using...) Figure 8 (Structure implementation). For example, modules can be stored in... Figure 8 The modules are stored in the memory 804, and these modules can provide instructions such that when the instructions of the modules are executed by the corresponding RAN node processing circuit 802, the RAN node 800 performs the corresponding operation of the flowchart.

[0095] Figure 5 Examples of operations performed by network nodes are shown. In some examples, network nodes are configured to provide location servers (e.g., location management servers).

[0096] In block 510, processing circuitry 802 configures the communication device, for example, to perform carrier phase difference measurement along with time difference measurement. In some embodiments, configuration information includes a list of potential configuration information to be transmitted.

[0097] In block 520, processing circuitry 802 transmits instructions via communication interface 806 regarding information to be considered when performing carrier phase difference measurement along with time difference measurement. In some examples, carrier phase measurement includes carrier phase difference measurement (CPDM). In additional or alternative examples, time difference measurement includes reference signal time difference (RSTD).

[0098] In some embodiments, the configuration information includes an indication of the location frequency layer (PFL) on which the communication device is instructed to perform carrier phase measurements. In additional or alternative embodiments, the PFL includes a single PFL common to both the reference node and neighboring nodes, which is considered when performing carrier phase measurements. In some examples, the reference node is a reference transmit-receive point (TRP). In additional or alternative examples, the neighboring node is a neighboring TRP.

[0099] In block 530, processing circuit 802 receives measurement reports from communication device via communication interface 806.

[0100] For some embodiments of RAN nodes and related methods, from Figure 7-8 Various operations in the flowchart can be optional.

[0101] Figure 6 An example of a communication system 600 according to some embodiments is shown.

[0102] In this example, communication system 600 includes a telecommunications network 602, which includes an access network 604, such as a radio access network (RAN), and a core network 606, which includes one or more core network nodes 608. Access network 604 includes one or more access network nodes, such as network nodes 610a and 610b (one or more of which are generally referred to as network node 610), or any other similar 3GPP access node or non-3GPP access point. Furthermore, as those skilled in the art will understand, network node 610 is not necessarily limited to an implementation of the radio and baseband portions provided and integrated by a single vendor. Therefore, it will be understood that network node 610 may include a decomposed implementation or portions thereof. For example, in some embodiments, telecommunications network 602 includes one or more Open RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunications network 602 that supports ORAN specifications (e.g., specifications published by the O-RAN Alliance or any similar organization) and can operate independently or together with other nodes to enable one or more functionalities of any node in the telecommunications network 602, including one or more network nodes 610 and / or core network nodes 608.

[0103] Examples of ORAN network nodes include Open Radio Units (O-RUs), Open Distributed Units (O-DUs), Open Central Units (O-CUs) including O-CU Control Panels (O-CU-CPs) or O-CU User Panels (O-CU-UPs), RAN Intelligent Controllers (near real-time or non-real-time) with managed software or software plug-ins, such as near real-time RAN control applications (e.g., xApps) or non-real-time RAN automation applications (e.g., rApps), or any combination thereof (the adjective "open" indicates support for the ORAN specification). Network nodes can support the specification by, for example, supporting interfaces defined by the ORAN specification, such as A1, F1, W1, E1, E2, X2, Xn interfaces, Open Front-End Transport User Panel interfaces, or Open Forward Backhaul Management Panel interfaces. The intent and content-aware notifications described herein can be transmitted from 3GPP network nodes or ORAN network nodes through 3GPP-defined interfaces (e.g., N2, N3) and / or ORAN Consortium-defined interfaces (e.g., A1, O1). Furthermore, an ORAN network node can be a logical node within a physical node. Furthermore, ORAN network nodes can be implemented in a virtualized environment (described further below) where one or more network functions are virtualized. For example, the virtualized environment may include an O-cloud computing platform coordinated by a service management and coordination framework via the O-2 interface defined by the O-RAN Alliance. Network node 610 facilitates direct or indirect connectivity of user equipment (UEs), such as connecting wireless devices 612a, 612b, 612c, and 612d (one or more of which may be collectively referred to as UE 612) to the core network 606 via one or more wireless connections.

[0104] Examples of wireless communication via wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for transmitting information without the use of wires, cables, or other conductors. Furthermore, in various embodiments, communication system 600 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that can facilitate or participate in the transmission of data and / or signals, whether via wired or wireless connections. Communication system 600 may include any type of communication, telecommunications, data, cellular, radio network, and / or other similar system and / or be connected to any type of communication, telecommunications, data, cellular, radio network, and / or other similar system via an interface.

[0105] UE 612 can be any communication device of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with network node 610 and other communication devices. Similarly, network node 610 is arranged, capable, configured, and / or operable to communicate directly or indirectly with UE 612 and / or with other network nodes or devices in telecommunication network 602 to enable and / or provide network access (such as wireless network access) and / or to perform other functions (such as management in telecommunication network 602).

[0106] In the depicted example, core network 606 connects network node 610 to one or more hosts (such as host 616). These connections may be direct or indirect, via one or more intermediate networks or devices. In other examples, network nodes may be directly coupled to hosts. Core network 606 includes one or more core network nodes (e.g., core network node 608) constructed from hardware and software components. The characteristics of these components may be substantially similar to those described with respect to UEs, network nodes, and / or hosts, such that the description generally applies to the corresponding components of core network node 608. Example core network nodes include one or more of the following: 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 Dehiding Function (SIDF), Unified Data Management (UDM), Secure Edge Protection Agent (SEPP), Network Open Function (NEF), and / or User Plane Function (UPF).

[0107] Host 616 may be under the ownership or control of a service provider other than the operator or provider of telecommunications network 602 and / or access network 604, and may be operated by or on behalf of the service provider. Host 616 may host various applications to provide one or more services. Examples of such applications include live and pre-recorded audio / video content, data collection services (such as retrieving and compiling data about various environmental conditions detected by multiple UEs), analytics functionality, social media, functionality for controlling or otherwise interacting with remote devices, functionality for alarm and monitoring centers, or any other such functionality performed by a server.

[0108] on the whole, Figure 6The communication system 600 enables connectivity between the UE, network nodes, and hosts. In that sense, the communication system can be configured to operate according to predefined rules or procedures, such as specific standards, including but not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); Wireless Local Area Network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard (WiFi); and / or any other suitable wireless communication standards, such as 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.

[0109] In some examples, telecommunications network 602 is a cellular network implementing 3GPP standardized features. Therefore, telecommunications network 602 can support network slicing to provide different logical networks to different devices connected to it. For example, telecommunications network 602 can 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 IoT services to yet another UE.

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

[0111] In the example, hub 614 communicates with access network 604 to facilitate indirect communication between one or more UEs (e.g., UE 612c and / or 612d) and network nodes (e.g., network node 610b). In some examples, hub 614 may be a controller, router, content source, and analytics tool, or any other communication device described herein with respect to a UE. For example, hub 614 may be a broadband router for enabling access to core network 606 for a UE. As another example, hub 614 may be a controller that sends commands or instructions to one or more actuators in a UE. Commands or instructions may be received from the UE, network node 610, or may be received via executable code, scripts, procedures, or other instructions in hub 614. As another example, hub 614 may be a data collector that acts as a temporary storage device for UE data, and in some embodiments, data analysis or other processing may be performed. As another example, hub 614 may be a content source. For example, for a UE that is a VR headset, display, speaker, or other media delivery device, hub 614 can retrieve VR assets, video, audio, or other media or data related to sensory information via network nodes. Hub 614 then provides the VR assets, video, audio, or other media or data related to sensory information to the UE either directly, after performing local processing, and / or after adding additional local content. In another example, hub 614 acts as a proxy server or coordinator for the UE, particularly if one or more of the UEs are low-power IoT devices.

[0112] Hub 614 may have a constant / persistent or intermittent connection to network node 610b. Hub 614 may also accommodate different communication schemes and / or scheduling between hub 614 and UEs (e.g., UEs 612c and / or 612d) and between hub 614 and core network 606. In other examples, hub 614 is connected to core network 606 and / or one or more UEs via a wired connection. Furthermore, hub 614 may be configured to connect to an M2M service provider via access network 604 and / or to another UE via a direct connection. In some scenarios, a UE can establish a wireless connection to network node 610 while still being connected via hub 614, either via a wired or wireless connection. In some embodiments, hub 614 may be a dedicated hub, i.e., a hub whose primary function is to route communication from network node 610b to UE / to route communication from UE to network node 610b. In other embodiments, hub 614 may be a non-dedicated hub, that is, a device capable of operating to route communication between the UE and network node 610b, but also capable of operating as a communication start and / or end point for certain data channels.

[0113] Figure 7 A UE 700 according to some embodiments is illustrated. As used herein, UE refers to a device capable of, configured to, arranged to, and / or operable to wirelessly communicate with network nodes and / or other UEs. Examples of UEs include, but are not limited to, smartphones, mobile phones, cellular phones, Voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, game consoles or devices, music storage devices, playback devices, wearable terminal devices, wireless endpoints, mobile stations, tablets, laptops, laptop embedded devices (LEEs), laptop mounted devices (LMEs), smart devices, wireless customer premises equipment (CPEs), vehicle-mounted or vehicle-embedded / integrated wireless devices, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including Narrowband Internet of Things (NB-IoT) UEs, Machine Type Communication (MTC) UEs, and / or Enhanced MTC (eMTC) UEs.

[0114] The UE can support device-to-device (D2D) communication, for example, by implementing 3GPP standards for sidelink communication, dedicated short-range communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, the UE may not necessarily be a user in the sense of a human user owning and / or operating the associated device. Instead, the UE may represent a device intended for sale to or operated by a human user but which may not or can not initially be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, the UE may represent a device not intended for sale to or operated by an end user but which may be associated with a user or operated for the user's benefit (e.g., a smart meter).

[0115] UE 700 includes processing circuitry 702, which is operatively coupled via bus 704 to input / output interface 706, power supply 708, memory 710, communication interface 712, and / or any other component, or any combination thereof. Some UEs may utilize... Figure 7 All or a subset of the components shown. The level of integration between components can vary from one UE to another. Furthermore, some UEs may contain multiple instances of components, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0116] Processing circuitry 702 is configured to process instructions and data and can be configured to implement any sequential state machine that operates to execute instructions stored in memory 710 as a machine-readable computer program. Processing circuitry 702 can 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 along with appropriate firmware; one or more stored computer programs, a general-purpose processor such as a microprocessor or digital signal processor (DSP), along with appropriate software; or any combination of the above. For example, processing circuitry 702 may include multiple central processing units (CPUs).

[0117] In the example, input / output interface 706 can be configured to provide one or more interfaces to input devices, output devices, or one or more input and / or output devices. Examples of output devices include speakers, sound cards, video cards, displays, monitors, printers, actuators, transmitters, smart cards, other output devices, or any combination thereof. Input devices can allow users to capture information into UE 700. Examples of input devices include touch-sensitive or presence-sensitive displays, cameras (e.g., digital cameras, digital camcorders, webcams, etc.), microphones, sensors, mice, trackballs, orientation pads, trackpads, scroll wheels, smart cards, etc. Presence-sensitive displays may include capacitive or resistive touch sensors to sense input from the user. Sensors may be, for example, accelerometers, gyroscopes, tilt sensors, force sensors, magnetometers, light sensors, proximity sensors, biosensors, etc., or any combination thereof. Output devices can use the same type of interface port as input devices. For example, a Universal Serial Bus (USB) port can be used to provide both input and output devices.

[0118] In some embodiments, power supply 708 is configured as a battery or battery pack. Other types of power sources, such as external power sources (e.g., electrical outlets), photovoltaic devices, or power cells, can be used. Power supply 708 may further include power supply circuitry for delivering power from power supply 708 itself and / or external power sources to various parts of UE 700 via an interface or input circuitry such as a power cable. The delivered power can be used, for example, for charging power supply 708. The power supply circuitry can perform any formatting, conversion, or other modification on the power from power supply 708 to adapt the power to the corresponding components of the UE 700 being powered.

[0119] Memory 710 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), disk, optical disk, hard disk, removable cassette tape, flash drive, etc. In one example, memory 710 includes one or more applications 714 (such as an operating system, web browser application, widget, gadget engine, or other application) and corresponding data 716. Memory 710 can store any operating system or combination of operating systems from a wide variety of operating systems used by UE 700.

[0120] The memory 710 can be configured to include multiple physical drive units such as a redundant array of independent disks (RAID), flash memory, USB flash drive, external hard drive, thumb drive, pen drive, key drive, high-density digital universal disc (HD-DVD) optical disc drive, internal hard drive, Blu-ray 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, tamper-proof smart card memory such as a Universal Integrated Circuit Card (UICC) (including one or more subscriber identity modules (SIM) such as USIM and / or ISIM), other memory, or any combination thereof. The UICC can be, for example, an embedded UICC (eUICC), an integrated UICC (iUICC), or a removable UICC commonly referred to as a "SIM card". The memory 710 can allow the UE 700 to access instructions, applications, etc., stored on temporary or non-temporary storage media to offload or upload data. Articles of manufacture, such as those utilizing communication systems, may be tangibly embodied in or contained in memory 710, which may be or include a device-readable storage medium.

[0121] Processing circuitry 702 can be configured to communicate with an access network or other network using communication interface 712. Communication interface 712 may include one or more communication subsystems and may include or be communicatively coupled to antenna 722. Communication interface 712 may include one or more transceivers for communication, such as through communication with one or more remote transceivers of another device capable of wireless communication (e.g., a network node in the access network or another UE). Each transceiver may include a transmitter 718 and / or a receiver 720 adapted to provide network communication (e.g., optical, electrical, frequency allocation, etc.). Furthermore, transmitter 718 and receiver 720 may be coupled to one or more antennas (e.g., antenna 722) and may share circuitry, software, or firmware, or alternatively, transmitter 718 and receiver 720 may be implemented separately.

[0122] In the illustrated embodiments, the communication functions of the communication interface 712 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communication such as Bluetooth, near-field communication, location-based communication such as using a Global Positioning System (GPS) to determine location, another similar communication function, or any combination thereof. Communication may be implemented according to one or more communication protocols and / or standards such as IEEE 802.11, Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, Transmission Control Protocol / Internet Protocol (TCP / IP), Synchronous Optical Networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), etc.

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

[0124] As another example, the UE includes actuators, motors, or switches associated with a communication interface configured to receive wireless input from a network node via a wireless connection. The state of the actuator, motor, or switch can change in response to the received wireless input. For example, the UE may include a motor for adjusting the control surfaces or rotors of a drone in flight based on the received input, or for adjusting the motor of a robotic arm performing medical procedures based on the received input.

[0125] When a UE is in the form of an Internet of Things (IoT) device, it can be a device for use in one or more application domains, including but not limited to urban wearable technology, extended industrial applications, and healthcare. Non-limiting examples of such IoT devices are devices or devices embedded in the following: connected refrigerators or freezers, TVs, connected lighting devices, electricity meters, robotic vacuum cleaners, voice-controlled smart speakers, home security cameras, motion detectors, thermostats, smoke detectors, door / window sensors, flood / humidity sensors, electric door locks, connected doorbells, heat pump-like air conditioning systems, autonomous vehicles, monitoring systems, weather monitoring devices, vehicle parking monitoring devices, electric vehicle charging stations, smartwatches, fitness trackers, head-mounted displays for augmented reality (AR) or virtual reality (VR), wearable devices for haptic or sensory enhancement, sprinklers, animal or object tracking devices, sensors for monitoring plants or animals, industrial robots, unmanned aerial vehicles (UAVs), and any kind of medical device such as heart rate monitors or remotely controlled surgical robots. (Except as per the above...) Figure 7 In addition to the other components described in UE 700 shown, UEs in the form of IoT devices include circuitry and / or software that depend on the intended application of the IoT device.

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

[0127] In practice, any number of UEs can be used together for a single use case. For example, the first UE can be an unmanned aerial vehicle (UAV) or can be integrated into the UAV and provide the UAV's speed information (obtained via a speed sensor) to a second UE, which acts as a remote controller for operating the UAV. When a user makes a change from the remote controller, the first UE can adjust a throttle valve on the UAV (e.g., by controlling an actuator) to increase or decrease the UAV's speed. The first and / or second UEs can also include more than one of the functionalities described above. For example, the UE can include sensors and actuators and handle the transmission of data from both the speed sensor and the actuator.

[0128] Figure 8A network node 800 according to some embodiments is illustrated. As used herein, a network node refers to a device capable of, configured to, arranged to, and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or devices in a telecommunications 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), NR Node Bs (gNBs)), O-RAN nodes, or components of O-RAN nodes (e.g., intelligent controllers, O-RUs, O-DUs, O-CUs).

[0129] Base stations can be classified based on the coverage they provide (or, in other words, their transmit power levels), and therefore, depending on the coverage provided, a base station can be referred to as a femtobase, picobase, microbase, or macrobase. A base station can be a relay node or a relay donor node controlling a relay. A network node can also include one or more (or all) portions of a distributed radio base station such as a centralized digital unit and / or a remote radio unit (RRU) sometimes referred to as a remote radio headend (RRH). Such a remote radio unit may or may not be integrated with an antenna as an antenna-integrated radio device. A portion of a distributed radio base station can also be referred to as a node in a distributed antenna system (DAS).

[0130] Other examples of network nodes include multi-transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) devices such as MSR BS, network controllers such as radio network controllers (RNC) or base station controllers (BSC), base transceiver stations (BTS), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCE), operation and maintenance (O&M) nodes, operation support system (OSS) nodes, self-organizing network (SON) nodes, location nodes (such as evolved servicing mobile location centers (E-SMLC)), and / or minimized drive tests (MDT).

[0131] Network node 800 includes processing circuitry 802, memory 804, communication interface 806, and power supply 808. Network node 800 may consist of multiple physically separate components (e.g., NodeB components and RNC components, or BTS components and BSC components, etc.), each of which may have its own corresponding components. In some scenarios where network node 800 includes multiple separate components (e.g., BTS and BSC components), one or more of these separate components may be shared among several network nodes. For example, a single RNC can control multiple NodeBs. In such scenarios, each unique NodeB and RNC pair may be considered a single separate network node in some instances. In some embodiments, network node 800 may be configured to support multiple Radio Access Technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 804 for different RATs) and some components may be reused (e.g., the same antenna 810 may be shared by different RATs). Network node 800 may also include multiple sets of components for integrating various wireless technologies, such as 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 chips or chipsets and other components within network node 800.

[0132] The processing circuitry 802 may include 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 or resource, or a combination of hardware, software, and / or coding logic operable to provide functionality of the network node 800, either alone or in combination with other network node 800 components such as memory 804.

[0133] In some embodiments, the processing circuitry 802 includes a system-on-a-chip (SoC). In some embodiments, the processing circuitry 802 includes one or more of a radio frequency (RF) transceiver circuitry 812 and a baseband processing circuitry 814. In some embodiments, the RF transceiver circuitry 812 and the baseband processing circuitry 814 may be on separate chips (or chipsets), boards, or units such as radio units and digital units. In alternative embodiments, some or all of the RF transceiver circuitry 812 and the baseband processing circuitry 814 may be on the same chip or chipset, board, or unit.

[0134] Memory 804 may include any form of volatile or non-volatile computer-readable memory, including, but not limited to, permanent storage devices, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (e.g., hard disk), removable storage media (e.g., flash drives, CDs, or DVDs), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory that stores information, data, and / or instructions that can be used by processing circuitry 802. Memory 804 may store any suitable instructions, data, or information, including applications, software, computer programs, and / or other instructions that contain one or more of logic, rules, codes, tables, and can be executed by processing circuitry 802 and utilized by network node 800. Memory 804 may be used to store any calculations performed by processing circuitry 802 and / or any data received via communication interface 806. In some embodiments, processing circuitry 802 and memory 804 are integrated.

[0135] Communication interface 806 is used in wired or wireless communication of signaling and / or data between network nodes, access networks, and / or UEs. As illustrated, communication interface 806 includes one or more ports / terminals 816 for transmitting data to and receiving data from the network, for example, via a wired connection. Communication interface 806 also includes radio front-end circuitry 818 that may be coupled to antenna 810 or, in some embodiments, is part of antenna 810. Radio front-end circuitry 818 includes filter 820 and amplifier 822. Radio front-end circuitry 818 may be connected to antenna 810 and processing circuitry 802. Radio front-end circuitry 818 may be configured to modulate the signal transmitted between antenna 810 and processing circuitry 802. Radio front-end circuitry 818 may receive digital data to be transmitted to other network nodes or UEs via a wireless connection. Radio front-end circuitry 818 may use a combination of filter 820 and / or amplifier 822 to convert the digital data into radio signals with appropriate channel and bandwidth parameters. The radio signals may then be transmitted via antenna 810. Similarly, upon receiving data, antenna 810 can collect radio signals and then convert the radio signals into digital data via radio front-end circuitry 818. The digital data can then be transmitted to processing circuitry 802. In other embodiments, the communication interface may include different components and / or different combinations of components.

[0136] In some alternative embodiments, network node 800 does not include a separate radio front-end circuitry 818; instead, processing circuitry 802 includes radio front-end circuitry and is connected to antenna 810. Similarly, in some embodiments, all or some of the RF transceiver circuitry 812 is part of communication interface 806. In other embodiments, communication interface 806 includes one or more ports or terminals 816, radio front-end circuitry 818, and RF transceiver circuitry 812 as part of a radio unit (not shown), and communication interface 806 communicates with baseband processing circuitry 814, which is part of a digital unit (not shown).

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

[0138] Antenna 810, communication interface 806, and / or processing circuitry 802 can be configured to perform any receive operation and / or certain acquire operation described herein as being performed by a network node. Any information, data, and / or signals can be received from the UE, another network node, and / or any other network device. Similarly, antenna 810, communication interface 806, and / or processing circuitry 802 can be configured to perform any transmit operation described herein as being performed by a network node. Any information, data, and / or signals can be transmitted to the UE, another network node, and / or any other network device.

[0139] Power supply 808 provides power to various components of network node 800 in a form suitable for the respective components (e.g., at the voltage and current levels required by each respective component). Power supply 808 may further include or be coupled to power management circuitry to power the components of network node 800 for performing the functionality described herein. For example, network node 800 may be connectable to an external power source (e.g., mains, electrical outlet) via input circuitry or interface such as a cable, thereby supplying power to the power circuitry of power supply 808. As another example, power supply 808 may include a power source in the form of a battery or battery pack, connected to or integrated into the power circuitry. The battery can provide backup power in the event of an external power failure.

[0140] Implementations of network node 800 may include, except Figure 8Additional components beyond those shown herein are used to provide certain aspects of the functionality of the network node, including any functionality described herein and / or any functionality necessary to support the topics described herein. For example, network node 800 may include user interface devices for allowing information to be input to and output from network node 800. This allows users to perform diagnostic, maintenance, repair, and other management functions for network node 800.

[0141] Figure 9 It is based on the various aspects described in this article, and may be Figure 6 A block diagram of host 900 in an embodiment of host 616. As used herein, host 900 can be or include various combinations of hardware and / or software, including standalone servers, blade servers, cloud-implemented servers, distributed servers, virtual machines, containers, or processing resources in a server farm. Host 900 can provide one or more services to one or more UEs.

[0142] Host 900 includes processing circuitry 902, which is operatively coupled via bus 904 to input / output interface 906, network interface 908, power supply 910, and memory 912. Other components may be included in other embodiments. These components may be characterized substantially similarly to those relating to... Figure 7 and Figure 8 The features described in the previous diagram of the device make its description generally applicable to the corresponding components of host 900.

[0143] Memory 912 may include one or more computer programs, including one or more host applications 914 and data 916, the data 916 including user data (e.g., data generated by the UE for the host 900 or data generated by the host 900 for the UE). Embodiments of the host 900 may utilize only a subset or all of the components shown. The host application 914 may be implemented in a container-based architecture, and the host application 914 may provide support for video codecs (e.g., Universal Video Codec (VVC), High Efficiency Video Codec (HEVC), Advanced Video Codec (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Codec (AAC), MPEG, G.711), including code conversion for multiple different categories, types, or implementations of the UE (e.g., mobile phone, desktop computer, wearable display system, head-up display system). The host application 914 may also provide user authentication and permission checks and may periodically report health, routing, and content availability to a central node (such as a device in the core network or at the edge). Therefore, host 900 can select and / or instruct different hosts for the UE to use for overhead services. Host application 914 can support various protocols, such as HTTP Live Streaming (HLS), Real-time Messaging Protocol (RTMP), Real-time Streaming Protocol (RTSP), and HTTP-based Dynamic Adaptive Streaming (MPEG-DASH).

[0144] Figure 10 This is a block diagram illustrating a virtualization environment 1000 in which functionality implemented by some embodiments can be virtualized. In this context, virtualization means creating a virtual version of a device or apparatus that may include a virtualized hardware platform, storage devices, and networking resources. As used herein, virtualization can be applied to any apparatus or component thereof described herein and relates to an implementation where at least a portion of its functionality is implemented as one or more virtual components. Some or all of the functionality described herein can be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtualization environments 1000 hosted by one or more hardware nodes, such as hardware computing devices operating as network nodes, UEs, core network nodes, or hosts. Furthermore, in embodiments where virtual nodes do not require radio connectivity (e.g., core network nodes or hosts), the nodes can be fully virtualized. In some embodiments, the virtualization environment 1000 includes components defined by the O-RAN Alliance, such as an O-cloud environment orchestrated via an O-2 interface by a service management and orchestration framework.

[0145] Application 1002 (which may alternatively be referred to as a software instance, virtual device, network function, virtual node, virtual network function, etc.) is run in virtualized environment 1000 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0146] Hardware 1004 includes processing circuitry, memory storing software and / or instructions executable by the hardware processing circuitry, and / or other hardware devices as described herein, such as network interfaces, input / output interfaces, etc. The processing circuitry can execute software to instantiate one or more virtualization layers 1006 (also referred to as a hypervisor or virtual machine monitor (VMM)), provide VMs 1008a and 1008b (one or more of which may be generally referred to as VM 1008), and / or perform any of the functions, features, and / or benefits described in relation to some embodiments described herein. Virtualization layer 1006 can present a virtual operating platform to VM 1008 that appears to be networked hardware.

[0147] VM 1008 includes virtual processing, virtual memory, virtual networking or interfaces, and virtual storage devices, and can run through a corresponding virtualization layer 1006. Different embodiments of instances of virtual device 1002 can be implemented on one or more VMs in VM 1008, and can be implemented in different ways. Hardware virtualization is referred to as Network Functions Virtualization (NFV) in some contexts. NFV can be used to consolidate many types of network devices into industry-standard high-capacity server hardware, physical switches, and physical storage devices that can be located in data centers and customer premises.

[0148] In the context of NFV, VM 1008 can be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each VM in VM 1008, and the portion of hardware 1004 that executes that VM, whether it is hardware dedicated to that VM and / or hardware shared by that VM and other VMs within it, forms a separate virtual network element. Still within the context of NFV, the virtual network function is responsible for handling specific network functions running in one or more VMs 1008 on top of hardware 1004 and corresponds to application 1002.

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

[0150] Figure 11 A communication diagram is shown illustrating how host 1102 communicates with UE 1106 via network node 1104 through a partial wireless connection, according to some embodiments. Reference will now be made to... Figure 11 Describe the UEs discussed in the preceding paragraphs (such as...) Figure 6 UE612a and / or Figure 7 UE 700), network nodes (such as Figure 6 Network node 610a and / or Figure 8 Network node 800) and host (such as Figure 6 Host 616 and / or Figure 9 Example implementations of the host 900 according to various embodiments.

[0151] Like host 900, embodiments of host 1102 include hardware such as a communication interface, processing circuitry, and memory. Host 1102 also includes software stored in or accessible by host 1102 and executable by the processing circuitry. The software includes a host application operable to provide services to remote users of UE 1106, such as those connected via an over-the-top (OTT) connection 1150 extending between UE 1106 and host 1102. In providing services to remote users, the host application can provide user data transmitted using the OTT connection 1150.

[0152] Network node 1104 includes hardware that enables it to communicate with host 1102 and UE 1106. Connection 1160 can be direct or via a core network (like...). Figure 6The core network (similar to 606) and / or one or more other intermediate networks (such as one or more public, private, or hosted networks). For example, an intermediate network could be a backbone network or the Internet.

[0153] UE 1106 includes hardware and software, the software being stored in or accessible by UE 1106 and executable by the UE's processing circuitry. The software includes client applications, such as web browsers or carrier-specific "apps," operable to provide services to human or non-human users via UE 1106 with the support of host 1102. In host 1102, the executing host application can communicate with the executing client application via OTT connection 1150 terminated at both UE 1106 and host 1102. When providing services to a user, the UE's client application can receive request data from the host application of the host and provide user data in response to the request data. OTT connection 1150 can transmit both request data and user data. The UE's client application can interact with the user to generate the user data it provides to the host application via OTT connection 1150.

[0154] OTT connection 1150 can be extended via connection 1160 between host 1102 and network node 1104 and via wireless connection 1170 between network node 1104 and UE 1106 to provide connectivity between host 1102 and UE 1106. Connection 1160 and wireless connection 1170, on which OTT connection 1150 can be provided, have been abstractly depicted to illustrate communication between host 1102 and UE 1106 via network node 1104, without explicitly mentioning any intermediate devices or the precise routing of messages via these devices.

[0155] As an example of data transmission via OTT connection 1150, in step 1108, host 1102 provides user data, which can be executed by executing a host application. In some embodiments, the user data is associated with a specific human user interacting with UE 1106. In other embodiments, the user data is associated with UE 1106, which shares data with host 1102 without explicit human interaction. In step 1110, host 1102 initiates a transmission carrying user data toward UE 1106. Host 1102 may initiate the transmission in response to a request transmitted by UE 1106. The request may be caused by human interaction with UE 1106 or by an operation of a client application executed on UE 1106. According to the teachings of the embodiments described throughout this disclosure, the transmission may pass through network node 1104. Therefore, in step 1112, according to the teachings of the embodiments described throughout this disclosure, network node 1104 transmits the user data carried in the transmission initiated by host 1102 to UE 1106. In step 1114, UE 1106 receives user data carried in the transmission, which can be executed by a client application that is executed on UE 1106 and associated with a host application executed by host 1102.

[0156] In some examples, UE 1106 executes a client application that provides user data to host 1102. User data can be provided as a response to or in response to data received from host 1102. Therefore, in step 1116, UE 1106 can provide user data, which can be done by executing the client application. When providing user data, the client application may further consider user input received from a user via the input / output interface of UE 1106. Regardless of the specific manner in which user data is provided, UE 1106 initiates a transmission of user data to host 1102 via network node 1104 in step 1118. In step 1120, in accordance with the teachings of the embodiments described throughout this disclosure, network node 1104 receives user data from UE 1106 and initiates a transmission of the received user data to host 1102. In step 1122, host 1102 receives the user data carried in the transmission initiated by UE 1106.

[0157] One or more embodiments in various implementations use OTT connection 1150 to improve the performance of OTT services provided to UE 1106, wherein wireless connection 1170 forms the final segment. More specifically, the teachings of these embodiments can allow carrier phase difference measurements to be consistent with those performed by the UE on the same carrier / PFL. The location server can know which carrier / PFL was used. This is useful for the location server to be able to compare measurements from different UEs, including PRU UEs. Auxiliary and measurement configuration data can be customized for cases where the UE is configured to perform time difference measurements such as RSTD measurements along with carrier phase difference measurements such as RSCPD measurements. The UE can complete RSCPD measurements along with RSTD measurements without additional latency.

[0158] In the example scenario, factory status information can be collected and analyzed by host 1102. As another example, host 1102 can process audio and video data already acquired from the UE for map creation. As another example, host 1102 can collect and analyze real-time data to help control traffic congestion (e.g., control traffic lights). As another example, host 1102 can store surveillance video uploaded by the UE. As another example, host 1102 can store or control access to media content, such as video, audio, VR, or AR, which can be broadcast, multicast, or unicast to the UE. As other examples, host 1102 can be used for energy pricing, remote control of non-time-critical electrical loads to balance generation demand, location services, presentation services (such as compiled graphs based on data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing, and / or transmitting data.

[0159] In some examples, measurement procedures may be provided for the purpose of monitoring data rates, latency, and other factors that improve upon one or more of the embodiments. Optional network functionality may also be available for reconfiguring the OTT connection 1150 between host 1102 and UE 1106 in response to changes in measurement results. The measurement procedures and / or network functionality for reconfiguring the OTT connection may be implemented in the software and hardware of host 1102 and / or in the software and hardware of UE 1106. In some embodiments, sensors (not shown) may be deployed in or associated with other devices traversed by the OTT connection 1150; the sensors may participate in the measurement procedure by providing values ​​of the monitored quantities as described above or by providing values ​​of other physical quantities from which the software can calculate or estimate the monitored quantities. Reconfiguration of the OTT connection 1150 may include message formats, retransmission settings, preferred routing, etc.; reconfiguration does not require a direct change in the operation of network node 1104. Such procedures and functionalities may be known and practiced in the art. In some embodiments, the measurements may involve dedicated UE signaling, which helps host 1102 measure throughput, propagation time, latency, and the like. These measurements can be implemented because the software uses OTT connection 1150 to transmit messages (particularly empty or “pseudo” messages) while monitoring propagation time, errors, etc.

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

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

[0162] The following describes an example implementation.

[0163] Example 1. A method for operating a communication device, the method comprising: Obtain (410) configuration information to perform carrier phase measurement along with time difference measurement; Based on the configuration information, perform (420) the carrier phase measurement along with the time difference measurement; and The (430) operation task is performed based on the carrier phase measurement and the time difference measurement.

[0164] Example 2. The method according to Example 1, wherein obtaining the configuration information includes receiving messages from a network node configured to provide a location server.

[0165] Example 3. According to the method of Example 1, obtaining the configuration information includes determining the configuration information from a list of potential configuration information.

[0166] Example 4. The method according to any one of Examples 1-3, wherein the carrier phase measurement includes carrier phase difference measurement (CPDM), and The time difference measurement mentioned therein includes the reference signal time difference (RSTD).

[0167] Example 5. The method according to any one of Examples 1-4, wherein the configuration information includes an indication of the positioning frequency layer (PFL) instructing the communication device to perform the carrier phase measurement on the positioning frequency layer.

[0168] Example 6. According to the method of Example 5, the PFL includes a single PFL shared between the reference node and neighboring nodes to be considered when performing the carrier phase measurement. The reference node is the Reference Transmitter-Receiver Point (TRP), and The neighbor node mentioned above is the neighbor TRP.

[0169] Example 7. The method according to Example 6, wherein performing the carrier phase measurement together with the time difference measurement includes: The reference carrier phase on the reference TRP is measured using the carrier / PFL used to measure the neighboring TRP; The carrier phase on the neighboring TRP is measured using the carrier PFL used to measure the neighboring TRP; and The reference signal carrier phase difference (RSCPD) measurement is determined based on the difference between the carrier phase and the reference carrier phase.

[0170] Example 8. The method according to any one of Examples 1-7, wherein performing the carrier phase measurement together with the time difference measurement includes: Failed to perform the carrier phase measurement or the time difference measurement; Request updated configuration information; and Re-execute the carrier phase measurement along with the time difference measurement.

[0171] Example 9. The method according to any one of Examples 1-7, wherein performing the operational task includes reporting the results of performing the carrier phase measurement together with the time difference measurement.

[0172] Example 10. The method according to any one of Examples 1-7, wherein performing the operational task includes determining the location of the communication device.

[0173] Example 11. A method for configuring a network node to provide a location server, the method comprising: Configure (510) the communication device to perform carrier phase difference measurement together with time difference measurement; Instructions are transmitted to the communication device (520) to indicate information to be considered when performing the carrier phase difference measurement together with the time difference measurement; and A measurement report is received from the communication device (530), the measurement report including the carrier phase measurement performed together with the time difference measurement.

[0174] Example 12. The method according to Example 11, wherein the network node is configured to provide a location server.

[0175] Example 13. The method according to any one of Examples 11-12, wherein configuring the configuration information includes transmitting a list of potential configuration information.

[0176] Example 14. The method according to any one of Examples 11-13, wherein the carrier phase measurement includes carrier phase difference measurement (CPDM), and The time difference measurement mentioned therein includes the reference signal time difference (RSTD).

[0177] Example 15. The method according to any one of Examples 11-14, wherein the configuration information includes an indication of the Positioning Frequency Layer (PFL) instructing the communication device to perform the carrier phase measurement on the Positioning Frequency Layer.

[0178] Example 16. The method according to Example 15, wherein the PFL includes a single PFL shared between the reference node and neighboring nodes to be considered when performing the carrier phase measurement. The reference node is the Reference Transmitter-Receiver Point (TRP), and The neighbor node mentioned above is the neighbor TRP.

[0179] Example 17. A communication device (700), the communication device comprising: Processing circuit (702); and A memory (710) is coupled to the processing circuit and stores instructions that can be executed by the processing circuit to cause the communication device to perform any of the operations of embodiments 1-10.

[0180] Example 18. A computer program comprising program code to be executed by a processing circuit (702) of a communication device (700), wherein execution of the program code causes the communication device to perform any of the operations of Examples 1-10.

[0181] Example 19. A computer program product including a non-transitory storage medium (710) comprising program code to be executed by a processing circuit (702) of a communication device (700), wherein execution of the program code causes the communication device to perform any of the operations of Examples 1-10.

[0182] Example 20. A non-transitory computer-readable medium storing instructions executable by a processing circuit (702) of the communication device (700) to cause the communication device to perform any of the operations of Examples 1-10.

[0183] Example 21. A network node (800), the network node comprising: Processing circuit (802); and A memory (804) is coupled to the processing circuitry and stores instructions that can be executed by the processing circuitry to cause the network node to perform any of the operations included in embodiments 11-16.

[0184] Example 22. A computer program comprising program code to be executed by a processing circuitry (802) of a network node (800), wherein execution of the program code causes the network node to perform any of the operations of Examples 11-16.

[0185] Example 23. A computer program product including a non-transitory storage medium (804) comprising program code to be executed by a processing circuitry (802) of a network node (800), wherein execution of the program code causes the network node to perform any of the operations of Examples 11-16.

[0186] Example 24. A non-transitory computer-readable medium storing instructions that can be executed by processing circuitry (802) of a network node (800) to cause the network node to perform any of the operations of Examples 11-16.

[0187] Example 25. A host configured to operate in a communication system to provide over-the-top (OTT) services, the host comprising: Processing circuitry configured to provide user data; and A network interface configured to initiate the transmission of the user data to a cellular network for transmission to a user equipment (UE). The UE includes a communication interface and a processing circuit, which are configured to perform any of the operations described in Embodiments 1-10 to receive the user data from the host.

[0188] Example 26. A host according to the foregoing embodiments, wherein the cellular network further includes a network node configured to communicate with the UE to transmit the user data from the host to the UE.

[0189] Example 27. The host according to the foregoing two examples, wherein: The host's processing circuitry is configured to execute a host application, thereby providing the user data; and The host application is configured to interact with a client application running on the UE, the client application being associated with the host application.

[0190] Example 28. A method implemented by a host operating in a communication system further comprising network nodes and user equipment (UE), the method comprising: Provide user data for the UE; and A transmission carrying the user data is initiated to the UE via a cellular network including the network node, wherein the UE performs any of the operations in embodiments 1-10 to receive the user data from the host.

[0191] Example 29. The method according to the foregoing embodiments further includes: On the host, a host application associated with a client application running on the UE is executed to receive the user data from the UE.

[0192] Example 30. The method according to the foregoing embodiments further includes: On the host, input data is transmitted to the client application running on the UE, the input data being provided by executing the host application. The user data is provided through the client application in response to the input data from the host application.

[0193] Example 31. A host configured to operate in a communication system to provide over-the-top (OTT) services, the host comprising: Processing circuitry configured to provide user data; and A network interface configured to initiate the transmission of the user data to a cellular network for transmission to a user equipment (UE). The UE includes a communication interface and processing circuitry, which are configured to perform any of the operations described in Embodiments 1-10 to transmit the user data to the host.

[0194] Example 32. A host according to the foregoing embodiments, wherein the cellular network further includes a network node configured to communicate with the UE to transmit the user data from the UE to the host.

[0195] Example 33. The host according to the foregoing two examples, wherein: The host's processing circuitry is configured to execute a host application, thereby providing the user data; and The host application is configured to interact with a client application running on the UE, the client application being associated with the host application.

[0196] Example 34. A method implemented by a host configured to operate in a communication system further comprising network nodes and user equipment (UE), the method comprising: The host receives user data transmitted by the UE to the host via the network node, wherein the UE performs any of the operations in Embodiments 1-10 to transmit the user data to the host.

[0197] Example 35. The method according to the foregoing embodiments further includes: On the host, a host application associated with a client application running on the UE is executed to receive the user data from the UE.

[0198] Example 36. The method according to the foregoing embodiments further includes: On the host, input data is transmitted to the client application running on the UE, the input data being provided by executing the host application. The user data is provided via the client application in response to the input data from the host application.

[0199] Example 37. A host configured to operate in a communication system to provide over-the-top (OTT) services, the host comprising: Processing circuitry configured to provide user data; and A network interface configured to initiate the transmission of user data to a network node in a cellular network for transmission to a user equipment (UE), the network node having a communication interface and processing circuitry, the processing circuitry of the network node being configured to perform any of the operations of Embodiments 11-16 to transmit the user data from the host to the UE.

[0200] Example 38. The host according to the foregoing embodiments, wherein: The processing circuitry of the host is configured to execute a host application that provides the user data; and The UE includes processing circuitry configured to execute a client application associated with the host application to receive the transmission of user data from the host.

[0201] Example 39. A method implemented in a host configured to operate in a communication system further comprising network nodes and user equipment (UE), the method comprising: Provide user data for the UE; and Initiate a transmission carrying the user data to the UE via a cellular network including the network node, wherein the network node performs any of the operations of Embodiments 11-16 to transmit the user data from the host to the UE.

[0202] Example 40. The method according to the foregoing embodiments further includes, at the network node, transmitting the user data provided by the host to the UE.

[0203] Example 41. The method according to any one of the preceding two examples, wherein the user data is provided by the host through executing a host application that interacts with a client application executed on the UE, the client application being associated with the host application.

[0204] Example 42. A communication system configured to provide overhead service, the communication system comprising: The host includes: Processing circuitry configured to provide user data for a user equipment (UE), the user data being associated with the overlay service; and A network interface configured to initiate the transmission of the user data to a cellular network node for transmission to the UE, the network node having a communication interface and processing circuitry, the processing circuitry of the network node being configured to perform any of the operations of Embodiments 11-16 to transmit the user data from the host to the UE.

[0205] Example 43. The communication system according to the foregoing embodiments further includes: The network node; and / or The user equipment.

[0206] Example 44. A host configured to operate in a communication system to provide over-the-top (OTT) services, the host comprising: Processing circuitry configured to initiate the reception of user data; and A network interface configured to receive the user data from a network node in a cellular network, the network node having a communication interface and processing circuitry, the processing circuitry of the network node being configured to perform any of the operations of Embodiments 11-16 to receive the user data from the user equipment (UE) for the host.

[0207] Example 45. The host according to the foregoing two examples, wherein: The host's processing circuitry is configured to execute a host application, thereby providing the user data; and The host application is configured to interact with a client application running on the UE, the client application being associated with the host application.

[0208] Example 46. A host according to any one of the foregoing two embodiments, wherein initiating the reception of the user data includes requesting the user data.

[0209] Example 47. A method implemented by a host configured to operate in a communication system further comprising network nodes and user equipment (UE), the method comprising: The host initiates the reception of user data from the UE, the user data originating from a transmission that the network node has already received from the UE, wherein the network node performs any of the operations of Embodiments 11-16 to receive the user data from the UE for the host.

[0210] Example 48. The method according to the foregoing embodiments further includes transmitting the received user data to the host at the network node.

Claims

1. A method of operating a communication device, the method comprising: Obtain (410) configuration information to perform carrier phase measurement along with time difference measurement; Based on the configuration information, perform (420) the carrier phase measurement along with the time difference measurement; as well as The (430) operation task is performed based on the carrier phase measurement and the time difference measurement.

2. The method of claim 1, wherein obtaining the configuration information includes receiving messages from a network node configured to provide a location server.

3. The method of claim 1, wherein obtaining the configuration information includes determining the configuration information from a list of potential configuration information.

4. The method according to any one of claims 1-3, wherein the carrier phase measurement includes carrier phase difference measurement (CPDM), and The time difference measurement mentioned therein includes the reference signal time difference (RSTD).

5. The method according to any one of claims 1-4, wherein the configuration information includes an indication of the positioning frequency layer (PFL) instructing the communication device to perform the carrier phase measurement on the positioning frequency layer.

6. The method of claim 5, wherein the PFL comprises a single PFL shared between the reference node and neighboring nodes to be considered when performing the carrier phase measurement. The reference node is the Reference Transmitter-Receiver Point (TRP), and The neighbor node mentioned above is the neighbor TRP.

7. The method of claim 6, wherein performing the carrier phase measurement together with the time difference measurement comprises: The reference carrier phase on the reference TRP is measured using the carrier / PFL used to measure the neighboring TRP; The carrier phase on the neighboring TRP is measured using the carrier PFL used to measure the neighboring TRP; and The reference signal carrier phase difference (RSCPD) measurement is determined based on the difference between the carrier phase and the reference carrier phase.

8. The method according to any one of claims 1-7, wherein performing the carrier phase measurement together with the time difference measurement comprises: Failed to perform the carrier phase measurement or the time difference measurement; Requesting updated configuration information; and Re-execute the carrier phase measurement along with the time difference measurement.

9. The method according to any one of claims 1-7, wherein performing the operational task includes reporting the results of performing the carrier phase measurement together with the time difference measurement.

10. The method according to any one of claims 1-7, wherein performing the operational task includes determining the location of the communication device.

11. A method of operating a network node configured to provide a location server, the method comprising: Configure (510) the communication device to perform carrier phase difference measurement together with time difference measurement; Transmit (520) an instruction to the communication device to take into account the information to be considered when performing the carrier phase difference measurement together with the time difference measurement; and A measurement report is received from the communication device (530), the measurement report including the carrier phase measurement performed together with the time difference measurement.

12. The method of claim 11, wherein the network node is configured to provide a location management server.

13. The method according to any one of claims 11-12, wherein configuring the configuration information includes transmitting a list of potential configuration information.

14. The method according to any one of claims 11-13, wherein the carrier phase measurement includes carrier phase difference measurement (CPDM), and The time difference measurement mentioned therein includes the reference signal time difference (RSTD).

15. The method according to any one of claims 11-14, wherein the configuration information includes an indication of a positioning frequency layer (PFL) instructing the communication device to perform the carrier phase measurement on the positioning frequency layer.

16. The method of claim 15, wherein the PFL comprises a single PFL shared between the reference node and neighboring nodes to be considered when performing the carrier phase measurement. The reference node is the Reference Transmitter-Receiver Point (TRP), and The neighbor node mentioned above is the neighbor TRP.

17. A communication device (700) suitable for performing operations, said operations including: Obtain (410) configuration information to perform carrier phase measurement along with time difference measurement; Based on the configuration information, perform (420) the carrier phase measurement along with the time difference measurement; as well as The (430) operation task is performed based on the carrier phase measurement and the time difference measurement.

18. The communication device according to claim 17, wherein the operation further includes any operation of claims 2-10.

19. A computer program comprising program code executable by a processing circuitry (702) of a communication device (700), wherein execution of the program code causes the communication device to perform operations, the operations including: Obtain (410) configuration information to perform carrier phase measurement along with time difference measurement; Based on the configuration information, perform (420) the carrier phase measurement along with the time difference measurement; as well as The (430) operation task is performed based on the carrier phase measurement and the time difference measurement.

20. The computer program of claim 19, wherein the operation further includes any operation of claims 2-10.

21. A computer program product comprising a non-transitory storage medium (710), the non-transitory storage medium comprising program code to be executed by a processing circuitry (702) of a communication device (700), wherein execution of the program code causes the communication device to perform operations, the operations including: Obtain (410) configuration information to perform carrier phase measurement along with time difference measurement; Based on the configuration information, perform (420) the carrier phase measurement along with the time difference measurement; as well as The (430) operation task is performed based on the carrier phase measurement and the time difference measurement.

22. The computer program product of claim 21, further comprising any operation of claims 2-10.

23. A communication device (700), comprising: Processing circuitry; and A memory coupled to the processing circuitry and having instructions stored therein, which are executable by the processing circuitry to cause the communication device to perform operations, including: Obtain (410) configuration information to perform carrier phase measurement along with time difference measurement; Based on the configuration information, perform (420) the carrier phase measurement along with the time difference measurement; and The (430) operation task is performed based on the carrier phase measurement and the time difference measurement.

24. The communication device according to claim 23, wherein the operation further includes any operation of claims 2-10.

25. A network node (800) suitable for performing operations, said operations including: Configure (510) the communication device to perform carrier phase difference measurement together with time difference measurement; Transmit (520) an instruction to the communication device to take into account the information to be considered when performing the carrier phase difference measurement together with the time difference measurement; and A measurement report is received from the communication device (530), the measurement report including the carrier phase measurement performed together with the time difference measurement.

26. The network node of claim 25, wherein the operation further includes any operation of claims 12-16.

27. A computer program comprising program code executable by processing circuitry (802) of a network node (800), wherein execution of the program code causes the network node to perform operations, the operations including: Configure (510) the communication device to perform carrier phase difference measurement together with time difference measurement; Transmit (520) an instruction to the communication device to take into account the information to be considered when performing the carrier phase difference measurement together with the time difference measurement; and A measurement report is received from the communication device (530), the measurement report including the carrier phase measurement performed together with the time difference measurement.

28. The computer program of claim 27, wherein the operation further includes any operation of claims 12-16.

29. A computer program product comprising a non-transitory storage medium (804), the non-transitory storage medium comprising program code to be executed by processing circuitry (802) of a network node (800), wherein execution of the program code causes the network node to perform operations, the operations including: Configure (510) the communication device to perform carrier phase difference measurement together with time difference measurement; Transmit (520) an instruction to the communication device to take into account the information to be considered when performing the carrier phase difference measurement together with the time difference measurement; and A measurement report is received from the communication device (530), the measurement report including the carrier phase measurement performed together with the time difference measurement.

30. The computer program product of claim 29, further comprising any operation of claims 12-16.

31. A network node (800), comprising: Processing circuitry; and A memory coupled to the processing circuitry and storing instructions executable by the processing circuitry to cause the network node to perform operations, including: Configure (510) the communication device to perform carrier phase difference measurement together with time difference measurement; Instructions are transmitted to the communication device (520) to indicate information to be considered when performing the carrier phase difference measurement together with the time difference measurement; and A measurement report is received from the communication device (530), the measurement report including the carrier phase measurement performed together with the time difference measurement.

32. The network node of claim 31, wherein the operation further includes any operation of claims 12-16.

Images