EP4666447A1 - Ntn positioning using neighbor cell measurements - Google Patents

Ntn positioning using neighbor cell measurements

Info

Publication number
EP4666447A1
EP4666447A1 EP24719898.9A EP24719898A EP4666447A1 EP 4666447 A1 EP4666447 A1 EP 4666447A1 EP 24719898 A EP24719898 A EP 24719898A EP 4666447 A1 EP4666447 A1 EP 4666447A1
Authority
EP
European Patent Office
Prior art keywords
positioning
wireless device
indication
cell
measurements
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
EP24719898.9A
Other languages
German (de)
French (fr)
Inventor
Zhilan XIONG
Min Wang
Johan Rune
Talha KHAN
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Telefonaktiebolaget LM Ericsson AB
Original Assignee
Telefonaktiebolaget LM Ericsson AB
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget LM Ericsson AB filed Critical Telefonaktiebolaget LM Ericsson AB
Publication of EP4666447A1 publication Critical patent/EP4666447A1/en
Pending legal-status Critical Current

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04BTRANSMISSION
    • H04B7/00Radio transmission systems, i.e. using radiation field
    • H04B7/14Relay systems
    • H04B7/15Active relay systems
    • H04B7/185Space-based or airborne stations; Stations for satellite systems
    • H04B7/1851Systems using a satellite or space-based relay
    • H04B7/18513Transmission in a satellite or space-based system
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04BTRANSMISSION
    • H04B7/00Radio transmission systems, i.e. using radiation field
    • H04B7/14Relay systems
    • H04B7/15Active relay systems
    • H04B7/185Space-based or airborne stations; Stations for satellite systems
    • H04B7/1853Satellite systems for providing telephony service to a mobile station, i.e. mobile satellite service
    • H04B7/18545Arrangements for managing station mobility, i.e. for station registration or localisation
    • H04B7/18547Arrangements for managing station mobility, i.e. for station registration or localisation for geolocalisation of a station

Definitions

  • the present disclosure generally relates to communication networks, and more specifically to non-terrestrial network (NTN) positioning using neighbor cell measurements.
  • NTN non-terrestrial network
  • the Third Generation Partnership Project (3GPP) fifth generation (5G) system is a new generation radio access technology intended to serve use cases such as enhanced mobile broadband (eMBB), ultra-reliable and low-latency communication (URLLC), narrowband Internet of Things (NB-IoT) and massive machine-type communications (mMTC).
  • 5G includes the New Radio (NR) access stratum interface and the 5G core network (5GC).
  • NR New Radio
  • the NR physical and higher layers are reusing parts of the Long Term Evolution (LTE) specification and add additional components when motivated by new use cases.
  • a satellite network based on the terrestrial wireless access technologies including LTE and NR may also be referred to as nonterrestrial network (NTN).
  • NTN nonterrestrial network
  • a mobile network with base stations on the ground may be referred to as terrestrial network (TN) or non-NTN network.
  • TN terrestrial network
  • a satellite within NTN may be referred to as a NTN node, NTN satellite or simply a satellite.
  • the objective on network verified user equipment (UE) location is to specify enhancements to multiple round trip time (multi-RTT) to support the network verified UE location in NTN assuming a single satellite in view and consider downlink time different of arrival (DL-TDoA) methods for verification.
  • multi-RTT multiple round trip time
  • DL-TDoA downlink time different of arrival
  • Enhancements assume reuse of the radio access technology (RAT) dependent positioning framework.
  • RAT radio access technology
  • the specification of DL-TDoA enhancements will be subject to the study of the impact of realistic UE clock drift onto DL-TDoA performance.
  • the target accuracy for position verification purposes is as documented in 3GPP TR 38.882 (i.e., 10 km granularity).
  • Multiple satellites in view by the UE may be considered.
  • the enhancements may be subject to relevant working groups (e.g., SA3/SA3-LI) feedbacks on the reliability of UE reports involved.
  • the enhancements may account for the minor-image ambiguity.
  • Network verified UE location is an optional UE feature.
  • NTN will reuse the location services (LCS) framework of the location management function (LMF) for the network verification of UE reported location information.
  • LMF location management function
  • the mirror point issue may be resolved by properly configuring neighbor cell measurement for a UE, such as, measurement of two neighbor cells on the opposite side of a satellite beam.
  • the UE Rx-Tx time difference is defined as TUE-RX -TUE-TX, where TUE-RX-TUE-TXIS directly derived from the timing advance TTA applied by the UE at a given subframe.
  • Ehancemets may include other assistance data (e.g., ephemeris) to be transferred from gNB to the LMF and other assistance data (e.g., to resolve ambiguity on mirror position issue) to be transferred from UE to LMF.
  • assistance data e.g., ephemeris
  • assistance data e.g., to resolve ambiguity on mirror position issue
  • Another enhancment may include adaptations enabling Rx-TX measurements for multi-RTT involving multiple cells within the same satellite.
  • Option 1 gNB or LMF implementation to solve the mirror error issue.
  • Option 2 Reuse existing enhanced cell identity (ECID) method (e.g., combine UE neighbor measurements to solve the ambiguity between mirror positions) with potential enhancements.
  • EID enhanced cell identity
  • NR NTN UE should report the Doppler calculated on the service link.
  • a very small aperture terminal (VS AT) UE should report its beam pointing in respect to satellite beam line of sight.
  • Option 5 Reporting of cell coverage information (e.g., cell footprint and reference point, or antenna pattern) to the LMF.
  • cell coverage information e.g., cell footprint and reference point, or antenna pattern
  • Option 6 Support and potentially enhance the optional Rel-17 uplink angle of arrival (UL- AoA) measurements defined for multi-RTT positioning.
  • UL- AoA uplink angle of arrival
  • NTN NTN
  • the location server may get two UE positions if using multi-RTT positioning or DL-TDoA positioning as shown in Figure 1. This is referred to as the mirror positions ambiguity for multi-RTT positioning and DL-TDoA positioning in NTN.
  • Issue 1 the existing neighbor cell measurement mechanism (based on synchronization signal block (SSB)) may be insufficient to ensure timely positioning measurement. Additional latency may be caused due to SSB measurement, while a positioning procedure/service may require a tight delay.
  • SSB synchronization signal block
  • the network may not be aware whether or when the UE may experience the mirror point ambiguity issue.
  • the network may be forced to always provide measurement configurations for some unnecessary neighbor cells to the UE, which may result in that that the UE has to measure those neighbor cells even if the UE may not experience mirror point ambiguity. This would waste UE energy and introduce signaling overhead.
  • NTNs nonterrestrial networks
  • PRS neighbor cell positioning reference signal
  • RSRP reference signal received power
  • ToA time of arrival
  • multi-RTT multiple round trip time
  • TDOA time difference of arrival
  • one network node (which may be network node# 1 that identifies whether there is UE location mirror ambiguity or may be the network node#2 receiving the related information from the network node#l) sends the information to the UE about PRS information of at least one neighbor cell of at least one main cell, where the main cell is the cell for which the UE needs to measure its related UE Rx-Tx time difference measurement in multi-RTT positioning.
  • the network node also requests the UE to measure and report PRS RSRP of the neighbor cells besides the UE Rx-Tx time difference measurement and/or PRS RSRP measurement of the main cells. The UE reports the measurement results accordingly.
  • One network node (which may be the network node# 1 that identifies whether there is UE location mirror ambiguity or may be the network node#2 receiving the related information from the network node#l) sends the information to the UE about PRS information of at least one neighbor cell of at least one main cell, where the main cell is the cell for which the UE need to measure its related reference signal time different (RSTD) measurement in DL-TDOA positioning.
  • the network node also requests the UE to measure and report PRS RSRP of the neighbor cell(s) besides the RSTD measurement and/or PRS RSRP measurement of the main cells. The UE reports the measurement results accordingly.
  • the configured PRS time-frequency resources for each main cell and its neighbor cells enable the requested ToA measurement and the requested PRS RSRP measurement within a short time duration.
  • the UE is configured with measurement configurations for one or multiple concerned neighbor cells that are close to an orbit that may cause mirror point issue.
  • the configurations are associated with specific locations (e.g., configured/preconfigured coordinates), and the UE only performs measurements towards those configured neighbor cells when the UE moves to the specific locations.
  • the configurations are associated with specific time instants (e.g., configured/preconfigured coordinates), and the UE only performs measurements towards those configured neighbor cells at those specific time instants.
  • the UE or the gNB may inform the location server of the handover, and the location server may then send new PRS information to the UE wherein the new PRS information is adapted to the UE’s new location (and/or new cell).
  • the location server may when the UE Rx-Tx time difference measurement for multi-RTT positioning or RSTD measurement for DL-TDOA positioning is initially configured proactively provide information about additional PRSs (in additional neighbor cells), wherein the UE does not apply the information for an additional PRS unless a condition associated with the information is fulfilled, e.g. that the UE is handed over to a certain target cell.
  • the PRS information the location server provides to the UE may have to take this into account by providing PRS information that is valid for different time periods, and provide indications of the time periods associated with the PRS information, so that the UE knows which PRS information to use at any given time.
  • the UE may skip measurements to one or multiple concerned neighbor cells even though they are configured by the network to measure.
  • the UE may signal the network information comprising at least one of: (a) IDs of neighbor cells that the UE has skipped for measurements; (b) IDs of measurement configuration that the UE has skipped; (c) time instants that the UE has skipped measurements for those neighbor cells; and (d) cause indicating why the UE has skipped measurements forthose neighbor cells.
  • the network may also send a signaling to the UE indicating at least one of: (a) a time instant at which the UE may start measurements on the concerned neighbor cells, where a different time instant may be configured for different neighbor cells; (b) a time instant at which the UE may stop measurements on the concerned neighbor cells, where a different time instant may be configured for different neighbor cells; (c) an indicator for a neighbor cell indicating that the UE may start measurements on the neighbor cell; and (d) an indicator for a neighbor cell indicating that the UE may stop measurements on the neighbor cell.
  • the signaling may be included in the same signaling message that comprises measurement configuration for the concerned neighbor cells.
  • the signaling may be included in a separate signaling message that does not comprise measurement configuration for the concerned neighbor cells.
  • One or multiple UE capabilities may be defined for the UE to indicate whether the UE supports additional measurements of neighbor cells for addressing mirror point ambiguity.
  • signaling exchanged between the UE and the location management function may be carried via a Long Term Evolution (LTE) positioning protocol (LPP) message (3GPP TS 37.355 version 17.4.0) or non-access stratum (NAS) signaling.
  • LTE Long Term Evolution
  • LPF positioning protocol
  • NAS non-access stratum
  • signaling exchanged between the gNB and the LMF may be carried via a New Radio Positioning Protocol a (NRPPa) message (3GPP TS 38.455 version 17.4.0) or next generation access protocol (NGAP) signaling.
  • NRPPa New Radio Positioning Protocol a
  • NGAP next generation access protocol
  • signaling exchanged between the UE and the gNB may be carried via: system information; Radio Resource Control (RRC) signaling; medium access control (MAC) control element (CE); and/or layer one (LI) signaling (e.g., downlink signaling carried in physical downlink control channel (PDCCH), or uplink signaling carried in physical uplink control channel (PUCCH) or physical random access channel (PRACH)).
  • RRC Radio Resource Control
  • MAC medium access control
  • LI layer one
  • one or more of the aforementioned methods may be used in conjunction with other positioning or non-positioning related measurements performed and reported by the UE or gNB for mirror image resolution.
  • UL-AoA measurements reported by the gNB may be used in conjunction with PRS-RSRP to further improve the reliability (e.g., increase the probability of correctly resolving the mirror image ambiguity) of mirror image ambiguity and/or to reduce the need to perform a large number of neighbor cell measurements.
  • a method performed by a wireless device operating in a non-terrestrial network comprises receiving a positioning configuration to measure downlink signals from a plurality of transmission/reception positions of at least one transmission/reception point.
  • the positioning configuration comprises an indication of a plurality of transmission/reception positions of at least one main cell for which to perform positioning measurements and an indication of at least one associated cell for which to perform positioning measurements when the wireless device is subject to mirror position ambiguity.
  • the method further comprises measuring two or more downlink signals according to the received positioning configuration.
  • the positioning configuration further comprises an indication of time windows associated with the indication of the plurality of transmission/reception positions of the at least one main cell.
  • the indication of time windows indicating time windows when the wireless device is able to perform positioning measurements in the at least one associated cell to resolve mirror position ambiguity.
  • the positioning configuration may further comprise an indication of locations associated with the indication of the plurality of transmission/reception positions of the at least one main cell. The indication of locations indicating locations where the wireless device is able to perform positioning measurements in the at least one associated cell to resolve mirror position ambiguity.
  • one of the at least one associated cell is on a different side of an orbit of at least one of the at least one main cell.
  • the downlink signals comprise a reference signal, such as a positioning reference signal.
  • the positioning configuration is for one of multiple round trip time positioning or downlink time difference of arrival positioning.
  • the wireless device determines whether to perform measurements on the downlink signals based on a time for performing the measurement.
  • the wireless device may determine whether to perform measurements on the downlink signals based on a location of the wireless device.
  • the wireless device may transmit a report to a network node indicating at least one of which measurements were performed and which measurements were not performed.
  • a wireless device comprises processing circuitry operable to perform any of the wireless device methods described above.
  • a computer program product comprising a non-transitory computer readable medium storing computer readable program code, the computer readable program code operable, when executed by processing circuitry to perform any of the methods performed by the wireless devices described above.
  • a method is performed by a network node operating in a non-terrestrial network.
  • the method comprises determining a positioning configuration for a wireless device to measure downlink signals from a plurality of transmission/reception positions of at least one transmission/reception point.
  • the positioning configuration comprises an indication of a plurality of transmission/reception positions of at least one main cell for which to perform positioning measurements and an indication of at least one associated cell for which to perform positioning measurements when the wireless device is subject to mirror position ambiguity.
  • the method further comprises transmitting the positioning configuration to the wireless device.
  • the positioning configuration further comprises an indication of time windows associated with the indication of the plurality of transmission/reception positions of the at least one main cell.
  • the indication of time windows indicating time windows when the wireless device is able to perform positioning measurements in the at least one associated cell to resolve mirror position ambiguity.
  • the positioning configuration may further comprise an indication of locations associated with the indication of the plurality of transmission/reception positions of the at least one main cell, the indication of locations indicating locations where the wireless device is able to perform positioning measurements in the at least one associated cell to resolve mirror position ambiguity.
  • one of the at least one associated cell is on a different side of an orbit of at least one of the at least one main cell.
  • the downlink signals comprise a reference signal, such as a positioning reference signal.
  • the positioning configuration is for one of multiple round trip time positioning or downlink time difference of arrival positioning.
  • network node comprises a location management function or a base station.
  • a network node comprises processing circuitry operable to perform any of the network node methods described above.
  • Another computer program product comprises a non-transitory computer readable medium storing computer readable program code, the computer readable program code operable, when executed by processing circuitry to perform any of the methods performed by the network nodes described above.
  • Certain embodiments may provide one or more of the following technical advantages. For example, particular embodiments solve the mirror positions ambiguity in NTN positioning within a short time duration.
  • Figure 1 illustrates an example of mirror positions ambiguity in a non-terrestrial network (NTN);
  • Figure 2 illustrates carrier frequency allocation of satellite cells in one satellite
  • FIG. 3 illustrates positioning reference signal (PRS) measurement indication in time and frequency domain
  • Figure 4 shows an example of a communication system, according to certain embodiments
  • FIG. 5 shows a user equipment (UE), according to certain embodiments
  • Figure 6 shows a network node, according to certain embodiments.
  • Figure 7 is a block diagram of a host, according to certain embodiments.
  • Figure 8 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized;
  • Figure 9 shows a communication diagram of a host communicating via a network node with a UE over a partially wireless connection in accordance with some embodiments
  • Figure 10 is a flowchart illustrating an example method in a network node, according to certain embodiments.
  • Figure 11 is a flowchart illustrating an example method in a wireless device, according to certain embodiments.
  • NTNs nonterrestrial networks
  • PRS neighbor cell positioning reference signal
  • RSRP reference signal received power
  • ToA time of arrival
  • multi-RTT multiple round trip time
  • TDOA time difference of arrival
  • NR New Radio
  • LTE Long Term Evolution
  • LoT Internet of Things
  • a terrestrial network node may comprise a radio network node (e.g., base station (BS), gNB, gNB-DU, gNB-CU, relay or integrated access and backhaul (IAB) node, radio network controller, transmission reception point (TRP), etc.) or a core network node (e.g., mobile switching center (MSC), mobility management entity (MME), operations and management (O&M), operations support system (OSS), self-optimizing network (SON), positioning node, etc.).
  • a radio network node e.g., base station (BS), gNB, gNB-DU, gNB-CU, relay or integrated access and backhaul (IAB) node, radio network controller, transmission reception point (TRP), etc.
  • a core network node e.g., mobile switching center (MSC), mobility management entity (MME), operations and management (O&M), operations support system (OSS), self-optimizing network (SON), positioning node, etc.
  • MSC mobile switching center
  • Non-terrestrial networks are networks, or segments of networks, using an airborne or space-borne vehicle to embark a transmission equipment relay node or base station.
  • NTN node is used to denote one or more radio network nodes or equipment at an airborne or space-borne vehicle, satellite (e.g., low Earth orbit (LEO), medium Earth orbit (MEO), geo-stationary Earth orbit (GEO), highly elliptical orbit (HEO), etc.), unmanned aerial system (UAS) platform, etc. capable of at least receiving radio signals from UE operating on the Earth.
  • NTN node’s receivers may have specific radio frequency (RF) characteristics (e.g., sensitivity) and may operate in specific RF bands dedicated for NTN operation.
  • RF radio frequency
  • a NTN node may also comprise a gNB of a special type, i.e., capable ofNTN operation.
  • location server positioning, location management function (LMF), evolved serving mobile location center (E-SMLC) may be used interchangeably, at least in some examples.
  • LMF location management function
  • E-SMLC evolved serving mobile location center
  • time resource may correspond to any type of physical resource or radio resource expressed in terms of length of time. Examples of time resources are: symbol, time slot, subframe, radio frame, transmission time interval (TTI), interleaving time, slot, sub-slot, mini-slot, etc.
  • TTI transmission time interval
  • PRS resources are assumed to be used in positioning procedure for NTN UE.
  • the embodiments are not limited by this.
  • the same/similar embodiments are equally applicable when other downlink reference signal or downlink transmissions are measured by the NTN UE for positioning purpose.
  • the embodiments are described assuming that DL-TDOA and multi-RTT positioning methods are applied to the UE. However, the embodiments are not limited by positioning methods. The embodiments are equally applicable to the UE with any positioning method that may suffer from the mirror point ambiguity issue.
  • the UE when it is indicated that the UE may experience the mirror point ambiguity issue in a positioning procedure, the UE is configured to perform positioning measurements in one or multiple concerned neighbor cells (e.g., located on both sides of an orbit), in addition to the positioning measurement in configured serving cells/satellites.
  • concerned neighbor cells e.g., located on both sides of an orbit
  • one network node e.g., location server
  • the PRS measurement information includes PRS time-frequency resource information, measurement time or measurement time window, bandwidth, subcarrier spacing, cyclic prefix (CP), PRS ID, physical cell ID and/or global cell ID.
  • the PRS measurement information including measurement request may be sent from the location server to the UE via one or more messages.
  • the UE reports the measurement results to the network node based on the measurement request.
  • the PRS measurement information may also comprise any of the PRS-related information that may be included in the ProvideAssistanceDcita message in the LTE Positioning Protocol (LPP) which is specified in 3GPP TS 37.355 version 17.4.0.
  • LTP LTE Positioning Protocol
  • one network node e.g., location server
  • the PRS measurement information includes PRS time-frequency resource information, measurement time or measurement time window, bandwidth, subcarrier spacing, CP, PRS ID, physical cell ID and/or global cell ID.
  • the PRS measurement information including measurement request may be sent from the location server to the UE via one or more messages.
  • the UE reports the measurement results to the network node based on the measurement request.
  • the LPP messages ProvideAssistancelnformation and RequestLocationlnformation (both specified in 3GPP TS 37.355 version 17.4.0) may be used.
  • Figures 2 and 3 illustrate an example of the PRS frequency allocation for different cells in NTN.
  • Figure 2 illustrates carrier frequency allocation of satellite cells in one satellite.
  • Figure 3 illustrates PRS measurement indication in time and frequency domain.
  • one network node e.g., location server
  • the PRS information of cell# 1 for TDOA measurement and PRS-RSRP measurement is also associated with the PRS information of cell# 1-1, cell# 1-3 and cell# 1-5 for PRS-RSRP measurement in the given time and frequency domain for each PRS
  • the PRS information of cell#2 for TDOA measurement and PRS-RSRP measurement is also associated with the PRS information of at least one of cell#2-l, cell#2-3 and cell#2-5 for PRS- RSRP measurement in the given time and frequency domain for each PRS.
  • the UE reports RSTD of PRS of cell#l and cell#2, PRS-RSRP of cell#l, PRS-RSRP of cell#l-l, PRS-RSRP of cell#l- 3, PRS-RSRP of cell#l-5, PRS-RSRP of cell#2, PRS-RSRP of cell#2-l, PRS-RSRP of cell#2-3, and PRS-RSRP of cell#2-5 to the network node.
  • cell# 1 - 1 , cell# 1 -4, cell#2-4 and cell#2- 1 may be assumed to have the same spatial relation to the satellite orbit as cell# 1 and cell#2, PRS signals transmitted in cell# 1-1, cell# 1-4, cell#2-4 and cell#2-l may not provide much assistance in the resolution of the mirror ambiguity potentially resulting from the multi-RTT measurements.
  • the set of neighbor cells for which PRS information is provided may be reduced to reduce the UE’s measurement burden as well as the signaling overhead.
  • the set of neighbor cells for which the location server provides PRS information in the example may, e.g., be limited to cell# 1-3, cell# 1-5, cell#2-3 and cell#2-5, or as another option, cell#l-2, cell# 1-6, cell#2-2 and cell#2-6.
  • the location server may provide the UE with PRS information for cell# 1-2, cell# 1-3, cell# 1-5 and cell# 1-6.
  • the situation for the RTT measurement(s) in cell#2 may be similar, and consequently the location server may choose to provide PRS information for cell#2-2, cell#2-3, cell#2-5 and cell#2-6.
  • one network node e.g., location server
  • the PRS information of cell# 1 for TDOA measurement and PRS-RSRP measurement is also associated with the PRS information of cell# 1-1, cell# 1-3 and cell# 1-5 for PRS-RSRP measurement in the given time and frequency domain for each PRS
  • the PRS information of cell#2 for TDOA measurement and PRS-RSRP measurement is also associated with the PRS information of at least one of cell#2-l, cell#2-3 and cell#2-5 for PRS- RSRP measurement in the given time and frequency domain for each PRS.
  • the UE reports UE Rx-Tx time difference related to PRS of cell# 1 , UE Rx-Tx time difference related to PRS of cell#2, PRS-RSRP of cell#l, PRS-RSRP of cell#l-l, PRS-RSRP of cell#l-3, PRS-RSRP of cell#l-5, PRS-RSRP of cell#2, PRS-RSRP of cell#2-l, PRS-RSRP of cell#2-3, and PRS-RSRP of cell#2-5 to the network node.
  • the UE is configured with measurement configurations for one or multiple concerned neighbor cells that are close to an orbit, which may cause the mirror point issue.
  • the configurations are associated with specific locations (e.g., configured/preconfigured coordinates). The UE only performs measurements towards those configured neighbor cells when the UE moves to the specific locations.
  • a multi -RTT measurement in NTN typically involves multiple RTT measurements distributed in time. Due to this circumstance, there is a non-negligible probability that a handover occurs (i.e., the UE is handed over from one cell to another) during the multi -RTT measurement (e.g., between two of the RTT measurements), not only because of cell movement or cell switches, but also because of UE movements (or a combination of UE movements and cell movements/switches).
  • the neighbor cells whose PRSs the UE measures on may preferably also be changed so that they are properly located in relation to the UE’s new location.
  • the UE or the gNB may inform the location server of the handover, and the location server may then send new PRS information to the UE wherein the new PRS information is adapted to the UE’s new location (and/or new cell).
  • the location server may already when the multi-RTT measurement is initially configured proactively provide information about additional PRSs (in additional neighbor cells), wherein the UE does not apply the information for an additional PRS unless a condition associated with the information is fulfilled, e.g. that the UE is handed over to a certain target cell.
  • the UE is configured with measurement configurations for one or multiple concerned neighbor cells that are close to an orbit, which may cause the mirror point issue.
  • the configurations are associated with specific time instants (e.g., configured/preconfigured coordinates). The UE only performs measurements towards those configured neighbor cells at those specific time instants.
  • the NTN cell covering a certain location changes over time due to moving cells (in moving cells deployments) or switches of the cell that cover a certain area (in quasi-Earth-fixed cells deployments).
  • the neighbor cells that are suitable for provision of the PRSs the UE should measure on for the purpose of resolving the mirror ambiguity of the result of the multi - RTT measurement may also change over time.
  • the PRS information the location server provides to the UE may account for this by providing PRS information that is valid for different time periods, and provide indications of the time periods associated with the PRS information, so that the UE knows which PRS information to use at any given time.
  • the UE may skip measurements to one or multiple concerned neighbor cells even though they are configured by the network to measure.
  • the UE may signal the network the information comprising at least one of: IDs of neighbor cells that the UE has skipped for measurements; IDs of measurement configuration that the UE has skipped; time instants that the UE has skipped measurements for those neighbor cells; and cause indicating why the UE has skipped measurements for those neighbor cells.
  • the network may also send signaling to the UE indicating at least one of: a time instant at which the UE can start measurements to the concerned neighbor cells, where a different time instant may be configured for different neighbor cell; a time instant at which the UE can stop measurements to the concerned neighbor cells, where a different time instant may be configured for different neighbor cell; an indicator for a neighbor cell indicating that the UE can start measurements to the neighbor cell; and/or an indicator for a neighbor cell indicating that the UE can stop measurements to the neighbor cell.
  • the signaling may be included in the same signaling message that comprises measurement configuration for the concerned neighbor cells.
  • the signaling may be included in a separate signaling message that does not comprise measurement configuration for the concerned neighbor cells.
  • one or multiple UE capability bits are defined for the UE to indicate whether the UE supports additional measurements of neighbor cells for addressing mirror point ambiguity.
  • signalling exchanged between the UE and the LMF may be carried via a LPP message (3GPP TS 37.355 version 17.4.0) or NAS signaling.
  • signalling exchanged between the gNB and the LMF may be carried via aNRPPa message (3GPP TS 38.455 version 17.4.0) or NGAP signaling.
  • signaling exchanged between the UE and the gNB may be carried via one of: system information; RRC signaling; MAC CE; and/or LI signaling (e.g., DL signaling carried in PDCCH, or UL signaling carried in PUCCH, PRACH).
  • system information e.g., system information
  • RRC signaling e.g., RRC signaling
  • MAC CE e.g., MAC CE
  • LI signaling e.g., DL signaling carried in PDCCH, or UL signaling carried in PUCCH, PRACH.
  • one or more of the aforementioned methods may be used in conjunction with other positioning or non-positioning related measurements performed and reported by the UE or gNB for mirror image resolution.
  • UL-AoA measurements reported by the gNB may be used in conjunction with PRS-RSRP to further improve the reliability (e.g., increase the probability of correctly resolving the mirror image ambiguity) of mirror image ambiguity and/or to reduce the need to perform a large number of neighbor cell measurements.
  • the location server and/or other network entity or node collects the RSRP data (e.g., PRS RSRP measurement data of serving cell and/or neighbor cells) of one or more UEs and the result of mirror image resolution.
  • RSRP data e.g., PRS RSRP measurement data of serving cell and/or neighbor cells
  • other parameters reported by the UE and/or gNB/LMF/OAM such as the respective PRS ID(s), satellite ID(s), cell ID(s), timestamp(s), UE reported location, satellite trajectory data (e.g., ephemeris), network-verified UE location, etc. related to the UE and the reported RSRP measurement may also be collected.
  • the network can leverage this dataset to train a learning algorithm (e.g., based on the existing deep neural network-based learning models) to resolve mirror image ambiguity problem.
  • the network may input the UE reported information (which may be obtained using one or more embodiments described herein) for a UE requiring mirror image resolution to resolve mirror image ambiguity.
  • This model-based result may be used exclusively or in conjunction with one or more of the measurement-based results for mirror image ambiguity to further refine the reliability (e.g., increase the probability of correctly resolving the mirror image ambiguity) of mirror image ambiguity solution.
  • the UE may report fewer neighbor cell measurements (as opposed to the case where mirror image ambiguity resolution is performed based on direct measurements reported by the UE).
  • FIG. 4 shows an example of a communication system 100 in accordance with some embodiments.
  • the communication system 100 includes a telecommunication network 102 that includes an access network 104, such as a radio access network (RAN), and a core network 106, which includes one or more core network nodes 108.
  • the access network 104 includes one or more access network nodes, such as network nodes 110a and 110b (one or more of which may be generally referred to as network nodes 110), or any other similar 3 rd Generation Partnership Project (3GPP) access node or non-3GPP access point.
  • 3GPP 3 rd Generation Partnership Project
  • the network nodes 110 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 112a, 112b, 112c, and 112d (one or more of which may be generally referred to as UEs 112) to the core network 106 over one or more wireless connections.
  • UE user equipment
  • Example wireless communications over a wireless connection include transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors.
  • the communication system 100 may include any number of wired or wireless networks, network nodes, UEs, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.
  • the communication system 100 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.
  • the UEs 112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and/or operable to communicate wirelessly with the network nodes 110 and other communication devices.
  • the network nodes 110 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 112 and/or with other network nodes or equipment in the telecommunication network 102 to enable and/or provide network access, such as wireless network access, and/or to perform other functions, such as administration in the telecommunication network 102.
  • the core network 106 connects the network nodes 110 to one or more hosts, such as host 116. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts.
  • the core network 106 includes one more core network nodes (e.g., core network node 108) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and/or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 108.
  • Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and/or a User Plane Function (UPF).
  • MSC Mobile Switching Center
  • MME Mobility Management Entity
  • HSS Home Subscriber Server
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • AUSF Authentication Server Function
  • SIDF Subscription Identifier De-concealing function
  • UDM Unified Data Management
  • SEPP Security Edge Protection Proxy
  • NEF Network Exposure Function
  • UPF User Plane Function
  • the host 116 may be under the ownership or control of a service provider other than an operator or provider of the access network 104 and/or the telecommunication network 102, and may be operated by the service provider or on behalf of the service provider.
  • the host 116 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio/video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.
  • the communication system 100 of Figure 4 enables connectivity between the UEs, network nodes, and hosts.
  • the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and/or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.
  • GSM Global System for Mobile Communications
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • the telecommunication network 102 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 102. For example, the telecommunications network 102 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and/or Massive Machine Type Communication (mMTC)ZMassive loT services to yet further UEs.
  • URLLC Ultra Reliable Low Latency Communication
  • eMBB Enhanced Mobile Broadband
  • mMTC Massive Machine Type Communication
  • the UEs 112 are configured to transmit and/or receive information without direct human interaction.
  • a UE may be designed to transmit information to the access network 104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 104.
  • a UE may be configured for operating in single- or multi -RAT or multi-standard mode.
  • a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi -radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).
  • MR-DC multi -radio dual connectivity
  • the hub 114 communicates with the access network 104 to facilitate indirect communication between one or more UEs (e.g., UE 112c and/or 112d) and network nodes (e.g., network node 110b).
  • the hub 114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs.
  • the hub 114 may be a broadband router enabling access to the core network 106 for the UEs.
  • the hub 114 may be a controller that sends commands or instructions to one or more actuators in the UEs.
  • the hub 114 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data.
  • the hub 114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 114 then provides to the UE either directly, after performing local processing, and/or after adding additional local content.
  • the hub 114 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy loT devices.
  • the hub 114 may have a constant/persistent or intermittent connection to the network node 110b.
  • the hub 114 may also allow for a different communication scheme and/or schedule between the hub 114 and UEs (e.g., UE 112c and/or 112d), and between the hub 114 and the core network 106.
  • the hub 114 is connected to the core network 106 and/or one or more UEs via a wired connection.
  • the hub 114 may be configured to connect to an M2M service provider over the access network 104 and/or to another UE over a direct connection.
  • UEs may establish a wireless connection with the network nodes 110 while still connected via the hub 114 via a wired or wireless connection.
  • the hub 114 may be a dedicated hub - that is, a hub whose primary function is to route communications to/from the UEs from/to the network node 110b.
  • the hub 114 may be a nondedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 110b, but which is additionally capable of operating as a communication start and/or end point for certain data channels.
  • FIG. 5 shows a UE 200 in accordance with some embodiments.
  • a UE refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other UEs.
  • Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle-mounted or vehicle embedded/integrated wireless device, etc.
  • VoIP voice over IP
  • LME laptop-embedded equipment
  • LME laptop-mounted equipment
  • CPE wireless customer-premise equipment
  • UEs identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.
  • 3GPP 3rd Generation Partnership Project
  • NB-IoT narrow band internet of things
  • MTC machine type communication
  • eMTC enhanced MTC
  • a UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to- everything (V2X).
  • a UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device.
  • a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller).
  • a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).
  • the UE 200 includes processing circuitry 202 that is operatively coupled via a bus 204 to an input/output interface 206, a power source 208, a memory 210, a communication interface 212, and/or any other component, or any combination thereof.
  • Certain UEs may utilize all or a subset of the components shown in Figure 2. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.
  • the processing circuitry 202 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 210.
  • the processing circuitry 202 may be implemented as one or more hardware -implemented state machines (e.g., in discrete logic, field- programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above.
  • the processing circuitry 202 may include multiple central processing units (CPUs).
  • the input/output interface 206 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and/or output devices.
  • Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof.
  • An input device may allow a user to capture information into the UE 200.
  • Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like.
  • the presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user.
  • a sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof.
  • An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.
  • USB Universal Serial Bus
  • the power source 208 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used.
  • the power source 208 may further include power circuitry for delivering power from the power source 208 itself, and/or an external power source, to the various parts of the UE 200 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 208.
  • Power circuitry may perform any formatting, converting, or other modification to the power from the power source 208 to make the power suitable for the respective components of the UE 200 to which power is supplied.
  • the memory 210 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth.
  • the memory 210 includes one or more application programs 214, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 216.
  • the memory 210 may store, for use by the UE 200, any of a variety of various operating systems or combinations of operating systems.
  • the memory 210 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and/or ISIM, other memory, or any combination thereof.
  • RAID redundant array of independent disks
  • HD-DVD high-density digital versatile disc
  • HDDS holographic digital data storage
  • DIMM external mini-dual in-line memory module
  • SDRAM synchronous dynamic random access memory
  • SDRAM synchronous dynamic random access memory
  • the UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’
  • the memory 210 may allow the UE 200 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data.
  • An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 210, which may be or comprise a device -readable storage medium.
  • the processing circuitry 202 may be configured to communicate with an access network or other network using the communication interface 212.
  • the communication interface 212 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 222.
  • the communication interface 212 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network).
  • Each transceiver may include a transmitter 218 and/or a receiver 220 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth).
  • the transmitter 218 and receiver 220 may be coupled to one or more antennas (e.g., antenna 222) and may share circuit components, software or firmware, or alternatively be implemented separately.
  • communication functions of the communication interface 212 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short- range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof.
  • GPS global positioning system
  • Communications may be implemented in according to one or more communication protocols and/or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol/intemet protocol (TCP/IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.
  • CDMA Code Division Multiplexing Access
  • WCDMA Wideband Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • GSM Global System for Mobile communications
  • LTE Long Term Evolution
  • NR New Radio
  • UMTS Worldwide Interoperability for Microwave Access
  • WiMax Ethernet
  • TCP/IP transmission control protocol/intemet protocol
  • SONET synchronous optical networking
  • ATM Asynchronous Transfer Mode
  • QUIC Hypertext Transfer Protocol
  • HTTP Hypertext Transfer Protocol
  • a UE may provide an output of data captured by its sensors, through its communication interface 212, via a wireless connection to a network node.
  • Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE.
  • the output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).
  • a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection.
  • the states of the actuator, the motor, or the switch may change.
  • the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.
  • a UE when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare.
  • loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door/window sensor, a flood/moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal-
  • AR Augmented Reality
  • VR
  • a UE may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another UE and/or a network node.
  • the UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device.
  • the UE may implement the 3GPP NB-IoT standard.
  • a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.
  • any number of UEs may be used together with respect to a single use case.
  • a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone.
  • the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed.
  • the first and/or the second UE can also include more than one of the functionalities described above.
  • a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.
  • FIG. 6 shows a network node 300 in accordance with some embodiments.
  • network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a UE and/or with other network nodes or equipment, in a telecommunication network.
  • network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NRNodeBs (gNBs)).
  • APs access points
  • BSs base stations
  • Node Bs Node Bs
  • eNBs evolved Node Bs
  • gNBs NRNodeBs
  • Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations.
  • a base station may be a relay node or a relay donor node controlling a relay.
  • a network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio.
  • RRUs remote radio units
  • RRHs Remote Radio Heads
  • Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio.
  • Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).
  • DAS distributed antenna system
  • network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and/or Minimization of Drive Tests (MDTs).
  • MSR multi-standard radio
  • RNCs radio network controllers
  • BSCs base station controllers
  • BTSs base transceiver stations
  • OFDM Operation and Maintenance
  • OSS Operations Support System
  • SON Self-Organizing Network
  • positioning nodes e.g., Evolved Serving Mobile Location Centers (E-SMLCs)
  • the network node 300 includes a processing circuitry 302, a memory 304, a communication interface 306, and a power source 308.
  • the network node 300 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components.
  • the network node 300 comprises multiple separate components (e.g., BTS and BSC components)
  • one or more of the separate components may be shared among several network nodes.
  • a single RNC may control multiple NodeBs.
  • each unique NodeB and RNC pair may in some instances be considered a single separate network node.
  • the network node 300 may be configured to support multiple radio access technologies (RATs).
  • RATs radio access technologies
  • some components may be duplicated (e.g., separate memory 304 for different RATs) and some components may be reused (e.g., a same antenna 310 may be shared by different RATs).
  • the network node 300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 300, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 300.
  • RFID Radio Frequency Identification
  • the processing circuitry 302 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node 300 components, such as the memory 304, to provide network node 300 functionality.
  • the processing circuitry 302 includes a system on a chip (SOC). In some embodiments, the processing circuitry 302 includes one or more of radio frequency (RF) transceiver circuitry 312 and baseband processing circuitry 314. In some embodiments, the radio frequency (RF) transceiver circuitry 312 and the baseband processing circuitry 314 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 312 and baseband processing circuitry 314 may be on the same chip or set of chips, boards, or units.
  • SOC system on a chip
  • the processing circuitry 302 includes one or more of radio frequency (RF) transceiver circuitry 312 and baseband processing circuitry 314.
  • the radio frequency (RF) transceiver circuitry 312 and the baseband processing circuitry 314 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF trans
  • the memory 304 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device-readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by the processing circuitry 302.
  • volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-
  • the memory 304 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and/or other instructions capable of being executed by the processing circuitry 302 and utilized by the network node 300.
  • the memory 304 may be used to store any calculations made by the processing circuitry 302 and/or any data received via the communication interface 306.
  • the processing circuitry 302 and memory 304 is integrated.
  • the communication interface 306 is used in wired or wireless communication of signaling and/or data between a network node, access network, and/or UE. As illustrated, the communication interface 306 comprises port(s)/terminal(s) 316 to send and receive data, for example to and from a network over a wired connection.
  • the communication interface 306 also includes radio front-end circuitry 318 that may be coupled to, or in certain embodiments a part of, the antenna 310. Radio front-end circuitry 318 comprises fdters 320 and amplifiers 322. The radio front-end circuitry 318 may be connected to an antenna 310 and processing circuitry 302. The radio front-end circuitry may be configured to condition signals communicated between antenna 310 and processing circuitry 302.
  • the radio front-end circuitry 318 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection.
  • the radio front-end circuitry 318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of fdters 320 and/or amplifiers 322.
  • the radio signal may then be transmitted via the antenna 310.
  • the antenna 310 may collect radio signals which are then converted into digital data by the radio front-end circuitry 318.
  • the digital data may be passed to the processing circuitry 302.
  • the communication interface may comprise different components and/or different combinations of components.
  • the network node 300 does not include separate radio front-end circuitry 318, instead, the processing circuitry 302 includes radio front-end circuitry and is connected to the antenna 310.
  • the processing circuitry 302 includes radio front-end circuitry and is connected to the antenna 310.
  • all or some of the RF transceiver circuitry 312 is part of the communication interface 306.
  • the communication interface 306 includes one or more ports or terminals 316, the radio front-end circuitry 318, and the RF transceiver circuitry 312, as part of a radio unit (not shown), and the communication interface 306 communicates with the baseband processing circuitry 314, which is part of a digital unit (not shown).
  • the antenna 310 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals.
  • the antenna 310 may be coupled to the radio front-end circuitry 318 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly.
  • the antenna 310 is separate from the network node 300 and connectable to the network node 300 through an interface or port.
  • the antenna 310, communication interface 306, and/or the processing circuitry 302 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node. Any information, data and/or signals may be received from a UE, another network node and/or any other network equipment. Similarly, the antenna 310, the communication interface 306, and/or the processing circuitry 302 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and/or signals may be transmitted to a UE, another network node and/or any other network equipment.
  • the power source 308 provides power to the various components of network node 300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component).
  • the power source 308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 300 with power for performing the functionality described herein.
  • the network node 300 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 308.
  • the power source 308 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.
  • Embodiments of the network node 300 may include additional components beyond those shown in Figure 6 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein.
  • the network node 300 may include user interface equipment to allow input of information into the network node 300 and to allow output of information from the network node 300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 300.
  • FIG. 7 is a block diagram of a host 400, which may be an embodiment of the host 116 of Figure 4, in accordance with various aspects described herein.
  • the host 400 may be or comprise various combinations hardware and/or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm.
  • the host 400 may provide one or more services to one or more UEs.
  • the host 400 includes processing circuitry 402 that is operatively coupled via a bus 404 to an input/output interface 406, a network interface 408, a power source 410, and a memory 412.
  • processing circuitry 402 that is operatively coupled via a bus 404 to an input/output interface 406, a network interface 408, a power source 410, and a memory 412.
  • Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 10 and 3, such that the descriptions thereof are generally applicable to the corresponding components of host 400.
  • the memory 412 may include one or more computer programs including one or more host application programs 414 and data 416, which may include user data, e.g., data generated by a UE for the host 400 or data generated by the host 400 for a UE.
  • Embodiments of the host 400 may utilize only a subset or all of the components shown.
  • the host application programs 414 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems).
  • the host application programs 414 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network.
  • the host 400 may select and/or indicate a different host for over-the-top services for a UE.
  • the host application programs 414 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.
  • HLS HTTP Live Streaming
  • RTMP Real-Time Messaging Protocol
  • RTSP Real-Time Streaming Protocol
  • MPEG-DASH Dynamic Adaptive Streaming over HTTP
  • FIG. 8 is a block diagram illustrating a virtualization environment 500 in which functions implemented by some embodiments may be virtualized.
  • virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources.
  • virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components.
  • Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 500 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host.
  • VMs virtual machines
  • the node may be entirely virtualized.
  • Applications 502 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.
  • Hardware 504 includes processing circuitry, memory that stores software and/or instructions executable by hardware processing circuitry, and/or other hardware devices as described herein, such as a network interface, input/output interface, and so forth.
  • Software may be executed by the processing circuitry to instantiate one or more virtualization layers 506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 508a and 508b (one or more of which may be generally referred to as VMs 508), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein.
  • the virtualization layer 506 may present a virtual operating platform that appears like networking hardware to the VMs 508.
  • the VMs 508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 506.
  • a virtualization layer 506 Different embodiments of the instance of a virtual appliance 502 may be implemented on one or more of VMs 508, and the implementations may be made in different ways.
  • Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV).
  • NFV network function virtualization
  • NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.
  • a VM 508 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine.
  • Each of the VMs 508, and that part of hardware 504 that executes that VM be it hardware dedicated to that VM and/or hardware shared by that VM with others of the VMs, forms separate virtual network elements.
  • a virtual network function is responsible for handling specific network functions that run in one or more VMs 508 on top of the hardware 504 and corresponds to the application 502.
  • Hardware 504 may be implemented in a standalone network node with generic or specific components. Hardware 504 may implement some functions via virtualization. Alternatively, hardware 504 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 510, which, among others, oversees lifecycle management of applications 502.
  • hardware 504 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station.
  • some signaling can be provided with the use of a control system 512 which may alternatively be used for communication between hardware nodes and radio units.
  • Figure 9 shows a communication diagram of a host 602 communicating via a network node 604 with a UE 606 over a partially wireless connection in accordance with some embodiments.
  • host 602 Like host 400, embodiments of host 602 include hardware, such as a communication interface, processing circuitry, and memory.
  • the host 602 also includes software, which is stored in or accessible by the host 602 and executable by the processing circuitry.
  • the software includes a host application that may be operable to provide a service to a remote user, such as the UE 606 connecting via an over-the-top (OTT) connection 650 extending between the UE 606 and host 602.
  • OTT over-the-top
  • the network node 604 includes hardware enabling it to communicate with the host 602 and UE 606.
  • the connection 660 may be direct or pass through a core network (like core network 106 of Figure 4) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks.
  • a core network like core network 106 of Figure 4
  • an intermediate network may be a backbone network or the Internet.
  • the UE 606 includes hardware and software, which is stored in or accessible by UE 606 and executable by the UE’s processing circuitry.
  • the software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 606 with the support of the host 602.
  • a client application such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 606 with the support of the host 602.
  • an executing host application may communicate with the executing client application via the OTT connection 650 terminating at the UE 606 and host 602.
  • the UE's client application may receive request data from the host's host application and provide user data in response to the request data.
  • the OTT connection 650 may transfer both the request data and the user data.
  • the UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT
  • the OTT connection 650 may extend via a connection 660 between the host 602 and the network node 604 and via a wireless connection 670 between the network node 604 and the UE 606 to provide the connection between the host 602 and the UE 606.
  • the connection 660 and wireless connection 670, over which the OTT connection 650 may be provided, have been drawn abstractly to illustrate the communication between the host 602 and the UE 606 via the network node 604, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • the host 602 provides user data, which may be performed by executing a host application.
  • the user data is associated with a particular human user interacting with the UE 606.
  • the user data is associated with a UE 606 that shares data with the host 602 without explicit human interaction.
  • the host 602 initiates a transmission carrying the user data towards the UE 606.
  • the host 602 may initiate the transmission responsive to a request transmitted by the UE 606.
  • the request may be caused by human interaction with the UE 606 or by operation of the client application executing on the UE 606.
  • the transmission may pass via the network node 604, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 612, the network node 604 transmits to the UE 606 the user data that was carried in the transmission that the host 602 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 614, the UE 606 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 606 associated with the host application executed by the host 602.
  • the UE 606 executes a client application which provides user data to the host 602.
  • the user data may be provided in reaction or response to the data received from the host 602.
  • the UE 606 may provide user data, which may be performed by executing the client application.
  • the client application may further consider user input received from the user via an input/output interface of the UE 606. Regardless of the specific manner in which the user data was provided, the UE 606 initiates, in step 618, transmission of the user data towards the host 602 via the network node 604.
  • the network node 604 receives user data from the UE 606 and initiates transmission of the received user data towards the host 602.
  • the host 602 receives the user data carried in the transmission initiated by the UE 606.
  • One or more of the various embodiments improve the performance of OTT services provided to the UE 606 using the OTT connection 650, in which the wireless connection 670 forms the last segment. More precisely, the teachings of these embodiments may improve the data rate and latency and thereby provide benefits such as reduced user waiting time, better responsiveness, and better QoE.
  • factory status information may be collected and analyzed by the host 602.
  • the host 602 may process audio and video data which may have been retrieved from a UE for use in creating maps.
  • the host 602 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights).
  • the host 602 may store surveillance video uploaded by a UE.
  • the host 602 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs.
  • the host 602 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and/or transmitting data.
  • a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve.
  • the measurement procedure and/or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host 602 and/or UE 606.
  • sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 650 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities.
  • the reconfiguring of the OTT connection 650 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 604. Such procedures and functionalities may be known and practiced in the art.
  • measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host 602.
  • the measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 650 while monitoring propagation times, errors, etc.
  • computing devices described herein may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • processing circuitry may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components.
  • a communication interface may be configured to include any of the components described herein, and/or the functionality of the components may be partitioned between the processing circuitry and the communication interface.
  • non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.
  • processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer- readable storage medium.
  • some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner.
  • the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and/or by end users and a wireless network generally.
  • Figure 10 is a flowchart illustrating an example method in a network node, according to certain embodiments. In particular embodiments, one or more steps of Figure 10 may be performed by network node 300 described with respect to Figure 6 or a LMF. The network node is operating in an NTN.
  • the method begins at step 1012, where the network node (e.g., network node 300, LMF) determines a positioning configuration for a wireless device to measure downlink signals from a plurality of transmission/reception positions of at least one transmission/reception point.
  • the positioning configuration comprises an indication of a plurality of transmission/reception positions of at least one main cell for which to perform positioning measurements and an indication of at least one associated cell for which to perform positioning measurements when the wireless device is subject to mirror position ambiguity.
  • the positioning configuration further comprises an indication of time windows associated with the indication of the plurality of transmission/reception positions of the at least one main cell.
  • the indication of time windows indicating time windows when the wireless device is able to perform positioning measurements in the at least one associated cell to resolve mirror position ambiguity.
  • the positioning configuration may further comprise an indication of locations associated with the indication of the plurality of transmission/reception positions of the at least one main cell, the indication of locations indicating locations where the wireless device is able to perform positioning measurements in the at least one associated cell to resolve mirror position ambiguity.
  • one of the at least one associated cell is on a different side of an orbit of at least one of the at least one main cell.
  • the positioning configuration is for one of multiple round trip time positioning, downlink time difference of arrival positioning, or any other positioning method that may be subject to mirror position ambiguity.
  • network node comprises a location management function or a base station.
  • the positioning configuration comprises any of the positioning configurations described in the embodiments and examples above.
  • the network node transmits the positioning configuration to the wireless device.
  • the wireless device using the positioning configuration to determine when and on what cells to perform measurements to resolve mirror position ambiguity.
  • Figure 11 is a flowchart illustrating an example method in a wireless device, according to certain embodiments. In particular embodiments, one or more steps of Figure 11 may be performed by UE 200 described with respect to Figure 5. The wireless device is operating in an NTN.
  • the method begins at step 1112, where the wireless device (e.g., UE 200) receives a positioning configuration to measure downlink signals from a plurality of transmission/reception positions of at least one transmission/reception point.
  • the positioning configuration comprises an indication of a plurality of transmission/reception positions of at least one main cell for which to perform positioning measurements and an indication of at least one associated cell for which to perform positioning measurements when the wireless device is subject to mirror position ambiguity.
  • the positioning configuration further comprises an indication of time windows associated with the indication of the plurality of transmission/reception positions of the at least one main cell.
  • the indication of time windows indicating time windows when the wireless device is able to perform positioning measurements in the at least one associated cell to resolve mirror position ambiguity.
  • the positioning configuration may further comprise an indication of locations associated with the indication of the plurality of transmission/reception positions of the at least one main cell. The indication of locations indicating locations where the wireless device is able to perform positioning measurements in the at least one associated cell to resolve mirror position ambiguity.
  • one of the at least one associated cell is on a different side of an orbit of at least one of the at least one main cell.
  • the downlink signals comprise a reference signal, such as a positioning reference signal, a CSI-RS, an SSB, or any other suitable signal.
  • a reference signal such as a positioning reference signal, a CSI-RS, an SSB, or any other suitable signal.
  • the positioning configuration is for one of multiple round trip time positioning, downlink time difference of arrival positioning, or any other positioning method that may be subject to mirror position ambiguity.
  • the positioning configuration comprises any of the positioning configurations described in the embodiments and examples above.
  • the wireless device measures two or more downlink signals according to the received positioning configuration. In particular embodiments, the wireless device determines whether to perform measurements on the downlink signals based on a time for performing the measurement. The wireless device may determine whether to perform measurements on the downlink signals based on a location of the wireless device. The wireless device may transmit a report to a network node indicating at least one of which measurements were performed and which measurements were not performed.
  • NTN non-terrestrial network
  • the positioning configuration comprises an indication of a plurality of main cells for which to perform positioning measurements and an indication of associated cells for which to perform positioning measurements when the wireless device is subject to mirror position ambiguity;
  • the positioning configuration further comprises an indication of time windows associated with the indication of the plurality of main cells indicating time windows when the wireless device should perform positioning measurements in the associated cell to resolve mirror position ambiguity.
  • the positioning configuration further comprises an indication of locations associated with the indication of the plurality of main cells indicating locations where the wireless device should perform positioning measurements in the associated cell to resolve mirror position ambiguity.
  • the positioning configuration comprises an indication of a plurality of main cells for which to perform positioning measurements and an indication of associated cells for which to perform positioning measurements when the wireless device is subject to mirror position ambiguity;
  • the positioning configuration further comprises an indication of time windows associated with the indication of the plurality of main cells indicating time windows when the wireless device should perform positioning measurements in the associated cell to resolve mirror position ambiguity.
  • the positioning configuration further comprises an indication of locations associated with the indication of the plurality of main cells indicating locations where the wireless device should perform positioning measurements in the associated cell to resolve mirror position ambiguity.
  • the positioning configuration comprises any of the time positioning configurations in the embodiments and examples described above.
  • the wireless device determines whether to perform measurements in an associated cell based on a time for performing the measurement.
  • the wireless device determines whether to perform measurements in an associated cell based on a location of the wireless device.
  • the wireless device transmits a report to a network node indicating which measurements were performed or which measurements were not performed.
  • any of the wireless device steps, features, or functions described above either alone or in combination with other steps, features, or functions described above.
  • the method of the previous embodiment further comprising one or more additional wireless device steps, features or functions described above.
  • a method performed by a base station comprising:
  • a mobile terminal comprising:
  • - power supply circuitry configured to supply power to the wireless device.
  • a base station comprising:
  • - power supply circuitry configured to supply power to the wireless device.
  • a user equipment comprising:
  • radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; - the processing circuitry being configured to perform any of the steps of any of the Group A embodiments;
  • an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry
  • a communication system including a host computer comprising:
  • UE user equipment
  • the cellular network comprises a base station having a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the Group B embodiments.
  • the communication system of the pervious embodiment further including the base station.
  • the communication system of the previous 3 embodiments wherein:
  • the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data
  • the UE comprises processing circuitry configured to execute a client application associated with the host application.
  • a user equipment (UE) configured to communicate with a base station, the UE comprising a radio interface and processing circuitry configured to performs any of the previous 3 embodiments.
  • a communication system including a host computer comprising:
  • UE user equipment
  • the UE comprises a radio interface and processing circuitry, the UE’s components configured to perform any of the steps of any of the Group A embodiments.
  • the communication system of the previous embodiment wherein the cellular network further includes a base station configured to communicate with the UE.
  • the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data
  • a communication system including a host computer comprising:
  • a - communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station
  • the UE comprises a radio interface and processing circuitry, the UE’s processing circuitry configured to perform any of the steps of any of the Group A embodiments.
  • the communication system of the previous embodiment further including the UE.
  • the communication system of the previous 2 embodiments further including the base station, wherein the base station comprises a radio interface configured to communicate with the UE and a communication interface configured to forward to the host computer the user data carried by a transmission from the UE to the base station.
  • the communication system of the previous 3 embodiments wherein:
  • the processing circuitry of the host computer is configured to execute a host application
  • the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data.
  • the host computer receiving user data transmitted to the base station from the UE, wherein the UE performs any of the steps of any of the Group A embodiments.
  • the method of the previous embodiment further comprising, at the UE, providing the user data to the base station.
  • the method of the previous 2 embodiments further comprising:
  • a communication system including a host computer comprising a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, wherein the base station comprises a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the Group B embodiments.
  • the communication system of the previous embodiment further including the base station.
  • the processing circuitry of the host computer is configured to execute a host application
  • the UE is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer.
  • the host computer receiving, from the base station, user data originating from a transmission which the base station has received from the UE, wherein the UE performs any of the steps of any of the Group A embodiments.
  • the method of the previous embodiment further comprising at the base station, receiving the user data from the UE.
  • the method of the previous 2 embodiments further comprising at the base station, initiating a transmission of the received user data to the host computer.

Landscapes

  • Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Astronomy & Astrophysics (AREA)
  • Aviation & Aerospace Engineering (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Position Fixing By Use Of Radio Waves (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

According to some embodiments, a method is performed by a network node operating in a non-terrestrial network. The method comprises determining a positioning configuration for a wireless device to measure downlink signals from a plurality of transmission/reception positions of at least one transmission/reception point. The positioning configuration comprises an indication of a plurality of transmission/reception positions of at least one main cell for which to perform positioning measurements and an indication of at least one associated cell for which to perform positioning measurements when the wireless device is subject to mirror position ambiguity. The method further comprises transmitting the positioning configuration to the wireless device.

Description

NTN Positioning Using Neighbor Cell Measurements
TECHNICAL FIELD
[0001] The present disclosure generally relates to communication networks, and more specifically to non-terrestrial network (NTN) positioning using neighbor cell measurements.
BACKGROUND
[0002] The Third Generation Partnership Project (3GPP) fifth generation (5G) system (5GS) is a new generation radio access technology intended to serve use cases such as enhanced mobile broadband (eMBB), ultra-reliable and low-latency communication (URLLC), narrowband Internet of Things (NB-IoT) and massive machine-type communications (mMTC). 5G includes the New Radio (NR) access stratum interface and the 5G core network (5GC). The NR physical and higher layers are reusing parts of the Long Term Evolution (LTE) specification and add additional components when motivated by new use cases.
[0003] To benefit from the strong mobile ecosystem and economy of scale, 3GPP is specifying a satellite network based on the terrestrial wireless access technologies including LTE and NR. A satellite network or satellite based mobile network may also be referred to as nonterrestrial network (NTN). A mobile network with base stations on the ground may be referred to as terrestrial network (TN) or non-NTN network. A satellite within NTN may be referred to as a NTN node, NTN satellite or simply a satellite.
[0004] In a NR Release- 18 work item on NTN enhancement, the objective on network verified user equipment (UE) location is to specify enhancements to multiple round trip time (multi-RTT) to support the network verified UE location in NTN assuming a single satellite in view and consider downlink time different of arrival (DL-TDoA) methods for verification.
[0005] Enhancements assume reuse of the radio access technology (RAT) dependent positioning framework. The specification of DL-TDoA enhancements will be subject to the study of the impact of realistic UE clock drift onto DL-TDoA performance. The target accuracy for position verification purposes is as documented in 3GPP TR 38.882 (i.e., 10 km granularity). Multiple satellites in view by the UE may be considered. The enhancements may be subject to relevant working groups (e.g., SA3/SA3-LI) feedbacks on the reliability of UE reports involved. The enhancements may account for the minor-image ambiguity. Network verified UE location is an optional UE feature. [0006] NTN will reuse the location services (LCS) framework of the location management function (LMF) for the network verification of UE reported location information. In general, the mirror point issue may be resolved by properly configuring neighbor cell measurement for a UE, auch as, measurement of two neighbor cells on the opposite side of a satellite beam.
[0007] For network verification of UE location in NR NTN based on multi-RTT using UE RX-TX time difference report, if the UE reports needed to perform multi-RTT can be assumed to be trusted, existing multi-RTT framework may be reused with potential enhancements to adapt it to NTN context. This may include, but not limited to, the following. NTN-specific definition of UE RX-TX time difference, including as an example, potential modifications to UE Rx-Tx time difference to enable network verification of UE location without introducing any additional measurements at the UE (with respect to Rel-17 NTN). The following is not precluded: the UE Rx-Tx time difference is defined as TUE-RX -TUE-TX, where TUE-RX-TUE-TXIS directly derived from the timing advance TTA applied by the UE at a given subframe.
[0008] Ehancemets may include other assistance data (e.g., ephemeris) to be transferred from gNB to the LMF and other assistance data (e.g., to resolve ambiguity on mirror position issue) to be transferred from UE to LMF. Another enhancment may include adaptations enabling Rx-TX measurements for multi-RTT involving multiple cells within the same satellite.
[0009] The following options have been investigated to resolve the mirror positions ambiguity for multi-RTT positioning:
Option 1: gNB or LMF implementation to solve the mirror error issue.
Option 2: Reuse existing enhanced cell identity (ECID) method (e.g., combine UE neighbor measurements to solve the ambiguity between mirror positions) with potential enhancements.
Option 3: NR NTN UE should report the Doppler calculated on the service link.
Option 4: a very small aperture terminal (VS AT) UE should report its beam pointing in respect to satellite beam line of sight.
Option 5: Reporting of cell coverage information (e.g., cell footprint and reference point, or antenna pattern) to the LMF.
Option 6: Support and potentially enhance the optional Rel-17 uplink angle of arrival (UL- AoA) measurements defined for multi-RTT positioning.
[0010] There currently exist certain challenges. For example, in NTN, one satellite moves along a given orbit so that the location server may get two UE positions if using multi-RTT positioning or DL-TDoA positioning as shown in Figure 1. This is referred to as the mirror positions ambiguity for multi-RTT positioning and DL-TDoA positioning in NTN.
[0011] This issue has been under discussion in 3GPP and assumes in general the mirror point issue can be resolved by properly configuring neighbor cell measurement for the UE, such as for example, measurement of two neighbor cells on the opposite side of a satellite beam.
[0012] The issue can be addressed through UE neighbour cell measurement which is configured by the network. It is expected that the below issues will be further discussed.
[0013] Issue 1 : the existing neighbor cell measurement mechanism (based on synchronization signal block (SSB)) may be insufficient to ensure timely positioning measurement. Additional latency may be caused due to SSB measurement, while a positioning procedure/service may require a tight delay.
[0014] Issue 2: for a UE in a positioning session/procedure, the network may not be aware whether or when the UE may experience the mirror point ambiguity issue. To address potential mirror point ambiguity, the network may be forced to always provide measurement configurations for some unnecessary neighbor cells to the UE, which may result in that that the UE has to measure those neighbor cells even if the UE may not experience mirror point ambiguity. This would waste UE energy and introduce signaling overhead.
SUMMARY
[0015] As described above, certain challenges currently exist with positioning in nonterrestrial networks (NTNs). Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. For example, particular embodiments include signaling and procedures to support neighbor cell positioning reference signal (PRS) reference signal received power (RSRP) measurement for each cell involved in time of arrival (ToA) measurement in multiple round trip time (multi-RTT) positioning and downlink (DL) time difference of arrival (TDOA) positioning in NTN for the identification of correct user equipment (UE) location in mirror UE positions ambiguity.
[0016] In general, one network node (which may be network node# 1 that identifies whether there is UE location mirror ambiguity or may be the network node#2 receiving the related information from the network node#l) sends the information to the UE about PRS information of at least one neighbor cell of at least one main cell, where the main cell is the cell for which the UE needs to measure its related UE Rx-Tx time difference measurement in multi-RTT positioning. The network node also requests the UE to measure and report PRS RSRP of the neighbor cells besides the UE Rx-Tx time difference measurement and/or PRS RSRP measurement of the main cells. The UE reports the measurement results accordingly.
[0017] One network node (which may be the network node# 1 that identifies whether there is UE location mirror ambiguity or may be the network node#2 receiving the related information from the network node#l) sends the information to the UE about PRS information of at least one neighbor cell of at least one main cell, where the main cell is the cell for which the UE need to measure its related reference signal time different (RSTD) measurement in DL-TDOA positioning. The network node also requests the UE to measure and report PRS RSRP of the neighbor cell(s) besides the RSTD measurement and/or PRS RSRP measurement of the main cells. The UE reports the measurement results accordingly.
[0018] The configured PRS time-frequency resources for each main cell and its neighbor cells enable the requested ToA measurement and the requested PRS RSRP measurement within a short time duration.
[0019] The UE is configured with measurement configurations for one or multiple concerned neighbor cells that are close to an orbit that may cause mirror point issue. The configurations are associated with specific locations (e.g., configured/preconfigured coordinates), and the UE only performs measurements towards those configured neighbor cells when the UE moves to the specific locations. In some embodiments, the configurations are associated with specific time instants (e.g., configured/preconfigured coordinates), and the UE only performs measurements towards those configured neighbor cells at those specific time instants.
[0020] The UE or the gNB (or one of the involved gNBs for an inter-gNB handover) may inform the location server of the handover, and the location server may then send new PRS information to the UE wherein the new PRS information is adapted to the UE’s new location (and/or new cell). Alternatively, the location server may when the UE Rx-Tx time difference measurement for multi-RTT positioning or RSTD measurement for DL-TDOA positioning is initially configured proactively provide information about additional PRSs (in additional neighbor cells), wherein the UE does not apply the information for an additional PRS unless a condition associated with the information is fulfilled, e.g. that the UE is handed over to a certain target cell. The PRS information the location server provides to the UE may have to take this into account by providing PRS information that is valid for different time periods, and provide indications of the time periods associated with the PRS information, so that the UE knows which PRS information to use at any given time.
[0021] If the UE determines that there is no mirror point ambiguity issue foreseen, the UE may skip measurements to one or multiple concerned neighbor cells even though they are configured by the network to measure. In this case, the UE may signal the network information comprising at least one of: (a) IDs of neighbor cells that the UE has skipped for measurements; (b) IDs of measurement configuration that the UE has skipped; (c) time instants that the UE has skipped measurements for those neighbor cells; and (d) cause indicating why the UE has skipped measurements forthose neighbor cells.
[0022] In addition to one or multiple measurement configurations for one or multiple concerned neighbor cells for addressing potential mirror point ambiguity issue, the network may also send a signaling to the UE indicating at least one of: (a) a time instant at which the UE may start measurements on the concerned neighbor cells, where a different time instant may be configured for different neighbor cells; (b) a time instant at which the UE may stop measurements on the concerned neighbor cells, where a different time instant may be configured for different neighbor cells; (c) an indicator for a neighbor cell indicating that the UE may start measurements on the neighbor cell; and (d) an indicator for a neighbor cell indicating that the UE may stop measurements on the neighbor cell.
[0023] The signaling may be included in the same signaling message that comprises measurement configuration for the concerned neighbor cells. Alternatively, the signaling may be included in a separate signaling message that does not comprise measurement configuration for the concerned neighbor cells.
[0024] One or multiple UE capabilities may be defined for the UE to indicate whether the UE supports additional measurements of neighbor cells for addressing mirror point ambiguity.
[0025] For the above embodiments, signaling exchanged between the UE and the location management function (LMF) may be carried via a Long Term Evolution (LTE) positioning protocol (LPP) message (3GPP TS 37.355 version 17.4.0) or non-access stratum (NAS) signaling. [0026] For the above embodiments, signaling exchanged between the gNB and the LMF may be carried via a New Radio Positioning Protocol a (NRPPa) message (3GPP TS 38.455 version 17.4.0) or next generation access protocol (NGAP) signaling.
[0027] For the above embodiments, signaling exchanged between the UE and the gNB may be carried via: system information; Radio Resource Control (RRC) signaling; medium access control (MAC) control element (CE); and/or layer one (LI) signaling (e.g., downlink signaling carried in physical downlink control channel (PDCCH), or uplink signaling carried in physical uplink control channel (PUCCH) or physical random access channel (PRACH)).
[0028] In one embodiment, one or more of the aforementioned methods may be used in conjunction with other positioning or non-positioning related measurements performed and reported by the UE or gNB for mirror image resolution. For example, UL-AoA measurements reported by the gNB may be used in conjunction with PRS-RSRP to further improve the reliability (e.g., increase the probability of correctly resolving the mirror image ambiguity) of mirror image ambiguity and/or to reduce the need to perform a large number of neighbor cell measurements.
[0029] According to some embodiments, a method performed by a wireless device operating in a non-terrestrial network. The method comprises receiving a positioning configuration to measure downlink signals from a plurality of transmission/reception positions of at least one transmission/reception point. The positioning configuration comprises an indication of a plurality of transmission/reception positions of at least one main cell for which to perform positioning measurements and an indication of at least one associated cell for which to perform positioning measurements when the wireless device is subject to mirror position ambiguity. The method further comprises measuring two or more downlink signals according to the received positioning configuration.
[0030] In particular embodiments, the positioning configuration further comprises an indication of time windows associated with the indication of the plurality of transmission/reception positions of the at least one main cell. The indication of time windows indicating time windows when the wireless device is able to perform positioning measurements in the at least one associated cell to resolve mirror position ambiguity. The positioning configuration may further comprise an indication of locations associated with the indication of the plurality of transmission/reception positions of the at least one main cell. The indication of locations indicating locations where the wireless device is able to perform positioning measurements in the at least one associated cell to resolve mirror position ambiguity.
[0031] In particular embodiments, one of the at least one associated cell is on a different side of an orbit of at least one of the at least one main cell.
[0032] In particular embodiments, the downlink signals comprise a reference signal, such as a positioning reference signal. [0033] In particular embodiments, the positioning configuration is for one of multiple round trip time positioning or downlink time difference of arrival positioning.
[0034] In particular embodiments, the wireless device determines whether to perform measurements on the downlink signals based on a time for performing the measurement. The wireless device may determine whether to perform measurements on the downlink signals based on a location of the wireless device. The wireless device may transmit a report to a network node indicating at least one of which measurements were performed and which measurements were not performed.
[0035] According to some embodiments, a wireless device comprises processing circuitry operable to perform any of the wireless device methods described above.
[0036] Also disclosed is a computer program product comprising a non-transitory computer readable medium storing computer readable program code, the computer readable program code operable, when executed by processing circuitry to perform any of the methods performed by the wireless devices described above.
[0037] According to some embodiments, a method is performed by a network node operating in a non-terrestrial network. The method comprises determining a positioning configuration for a wireless device to measure downlink signals from a plurality of transmission/reception positions of at least one transmission/reception point. The positioning configuration comprises an indication of a plurality of transmission/reception positions of at least one main cell for which to perform positioning measurements and an indication of at least one associated cell for which to perform positioning measurements when the wireless device is subject to mirror position ambiguity. The method further comprises transmitting the positioning configuration to the wireless device.
[0038] In particular embodiments, the positioning configuration further comprises an indication of time windows associated with the indication of the plurality of transmission/reception positions of the at least one main cell. The indication of time windows indicating time windows when the wireless device is able to perform positioning measurements in the at least one associated cell to resolve mirror position ambiguity. The positioning configuration may further comprise an indication of locations associated with the indication of the plurality of transmission/reception positions of the at least one main cell, the indication of locations indicating locations where the wireless device is able to perform positioning measurements in the at least one associated cell to resolve mirror position ambiguity. [0039] In particular embodiments, one of the at least one associated cell is on a different side of an orbit of at least one of the at least one main cell.
[0040] In particular embodiments, the downlink signals comprise a reference signal, such as a positioning reference signal.
[0041] In particular embodiments, the positioning configuration is for one of multiple round trip time positioning or downlink time difference of arrival positioning.
[0042] In particular embodiments, network node comprises a location management function or a base station.
[0043] According to some embodiments, a network node comprises processing circuitry operable to perform any of the network node methods described above.
[0044] Another computer program product comprises a non-transitory computer readable medium storing computer readable program code, the computer readable program code operable, when executed by processing circuitry to perform any of the methods performed by the network nodes described above.
[0045] Certain embodiments may provide one or more of the following technical advantages. For example, particular embodiments solve the mirror positions ambiguity in NTN positioning within a short time duration.
BRIEF DESCRIPTION OF THE DRAWINGS
[0046] The present disclosure may be best understood by way of example with reference to the following description and accompanying drawings that are used to illustrate embodiments of the present disclosure. In the drawings:
Figure 1 illustrates an example of mirror positions ambiguity in a non-terrestrial network (NTN);
Figure 2 illustrates carrier frequency allocation of satellite cells in one satellite;
Figure 3 illustrates positioning reference signal (PRS) measurement indication in time and frequency domain;
Figure 4 shows an example of a communication system, according to certain embodiments;
Figure 5 shows a user equipment (UE), according to certain embodiments;
Figure 6 shows a network node, according to certain embodiments;
Figure 7 is a block diagram of a host, according to certain embodiments; Figure 8 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized;
Figure 9 shows a communication diagram of a host communicating via a network node with a UE over a partially wireless connection in accordance with some embodiments;
Figure 10 is a flowchart illustrating an example method in a network node, according to certain embodiments; and
Figure 11 is a flowchart illustrating an example method in a wireless device, according to certain embodiments.
DETAILED DESCRIPTION
[0047] As described above, certain challenges currently exist with positioning in nonterrestrial networks (NTNs). Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. For example, particular embodiments include signaling and procedures to support neighbor cell positioning reference signal (PRS) reference signal received power (RSRP) measurement for each cell involved in time of arrival (ToA) measurement in multiple round trip time (multi-RTT) positioning and downlink (DL) time difference of arrival (TDOA) positioning in NTN for the identification of correct user equipment (UE) location in mirror UE positions ambiguity.
[0048] Particular embodiments are described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.
[0049] Particular embodiments and/or examples may be described primarily in terms of New Radio (NR) NTN, but the embodiments and/or examples are applicable also to the Long Term Evolution (LTE)-based Internet of Things (loT) NTN.
[0050] A terrestrial network node may comprise a radio network node (e.g., base station (BS), gNB, gNB-DU, gNB-CU, relay or integrated access and backhaul (IAB) node, radio network controller, transmission reception point (TRP), etc.) or a core network node (e.g., mobile switching center (MSC), mobility management entity (MME), operations and management (O&M), operations support system (OSS), self-optimizing network (SON), positioning node, etc.).
[0051] Non-terrestrial networks are networks, or segments of networks, using an airborne or space-borne vehicle to embark a transmission equipment relay node or base station. [0052] Herein, the term NTN node is used to denote one or more radio network nodes or equipment at an airborne or space-borne vehicle, satellite (e.g., low Earth orbit (LEO), medium Earth orbit (MEO), geo-stationary Earth orbit (GEO), highly elliptical orbit (HEO), etc.), unmanned aerial system (UAS) platform, etc. capable of at least receiving radio signals from UE operating on the Earth. NTN node’s receivers may have specific radio frequency (RF) characteristics (e.g., sensitivity) and may operate in specific RF bands dedicated for NTN operation. A NTN node may also comprise a gNB of a special type, i.e., capable ofNTN operation. [0053] The terms location server, positioning, location management function (LMF), evolved serving mobile location center (E-SMLC) may be used interchangeably, at least in some examples. [0054] The term gNB, eNB, base station or TRP may be used interchangeably, at least in some examples.
[0055] The term time resource as used herein may correspond to any type of physical resource or radio resource expressed in terms of length of time. Examples of time resources are: symbol, time slot, subframe, radio frame, transmission time interval (TTI), interleaving time, slot, sub-slot, mini-slot, etc.
[0056] In the below embodiments, PRS resources are assumed to be used in positioning procedure for NTN UE. However, the embodiments are not limited by this. The same/similar embodiments are equally applicable when other downlink reference signal or downlink transmissions are measured by the NTN UE for positioning purpose.
[0057] The embodiments are described assuming that DL-TDOA and multi-RTT positioning methods are applied to the UE. However, the embodiments are not limited by positioning methods. The embodiments are equally applicable to the UE with any positioning method that may suffer from the mirror point ambiguity issue.
[0058] In some embodiments, when it is indicated that the UE may experience the mirror point ambiguity issue in a positioning procedure, the UE is configured to perform positioning measurements in one or multiple concerned neighbor cells (e.g., located on both sides of an orbit), in addition to the positioning measurement in configured serving cells/satellites.
[0059] In some embodiments, for DL-TDOA positioning, one network node (e.g., location server) sends the information to one UE about the PRS measurement information of a list of cells for the time of arrival (TOA) measurement and PRS RSRP measurement as well as the PRS measurement information of neighbor cells of each cell (e.g., at least one neighbor cell in the first inner circle of each cell) in the cell list for PRS RSRP measurement. The PRS measurement information includes PRS time-frequency resource information, measurement time or measurement time window, bandwidth, subcarrier spacing, cyclic prefix (CP), PRS ID, physical cell ID and/or global cell ID. The PRS measurement information including measurement request may be sent from the location server to the UE via one or more messages. The UE reports the measurement results to the network node based on the measurement request. The PRS measurement information may also comprise any of the PRS-related information that may be included in the ProvideAssistanceDcita message in the LTE Positioning Protocol (LPP) which is specified in 3GPP TS 37.355 version 17.4.0.
[0060] In some embodiments, for multi-RTT positioning, one network node (e.g., location server) sends the information to one UE about the PRS measurement information of a list of cells for UE Rx-Tx time difference measurement and PRS RSRP measurement as well as the PRS measurement information of neighbor cells of each cell (e.g., at least one neighbor cell in the first inner circle of each cell) in the cell list for PRS RSRP measurement. The PRS measurement information includes PRS time-frequency resource information, measurement time or measurement time window, bandwidth, subcarrier spacing, CP, PRS ID, physical cell ID and/or global cell ID. The PRS measurement information including measurement request may be sent from the location server to the UE via one or more messages. The UE reports the measurement results to the network node based on the measurement request. For the purpose of conveying this information from the location server to the UE, in some embodiments, either or both of the LPP messages ProvideAssistancelnformation and RequestLocationlnformation (both specified in 3GPP TS 37.355 version 17.4.0) may be used.
[0061] Figures 2 and 3 illustrate an example of the PRS frequency allocation for different cells in NTN. Figure 2 illustrates carrier frequency allocation of satellite cells in one satellite. Figure 3 illustrates PRS measurement indication in time and frequency domain.
[0062] In one example, for DL-TDOA positioning, one network node (e.g., location server) sends the information to the UE about the PRS information in Figure 3 of cell# 1 and cell#2 in Figure 2 for the TDOA measurement and PRS-RSRP measurement in the given time and frequency domain for each PRS, and the PRS information of cell# 1 for TDOA measurement and PRS-RSRP measurement is also associated with the PRS information of cell# 1-1, cell# 1-3 and cell# 1-5 for PRS-RSRP measurement in the given time and frequency domain for each PRS, and the PRS information of cell#2 for TDOA measurement and PRS-RSRP measurement is also associated with the PRS information of at least one of cell#2-l, cell#2-3 and cell#2-5 for PRS- RSRP measurement in the given time and frequency domain for each PRS. The UE reports RSTD of PRS of cell#l and cell#2, PRS-RSRP of cell#l, PRS-RSRP of cell#l-l, PRS-RSRP of cell#l- 3, PRS-RSRP of cell#l-5, PRS-RSRP of cell#2, PRS-RSRP of cell#2-l, PRS-RSRP of cell#2-3, and PRS-RSRP of cell#2-5 to the network node.
[0063] As another option, because the concerned satellite orbit may be assumed to be such that cell# 1 and cell#2 will cover the UE at different points in time, cell# 1 - 1 , cell# 1 -4, cell#2-4 and cell#2- 1 may be assumed to have the same spatial relation to the satellite orbit as cell# 1 and cell#2, PRS signals transmitted in cell# 1-1, cell# 1-4, cell#2-4 and cell#2-l may not provide much assistance in the resolution of the mirror ambiguity potentially resulting from the multi-RTT measurements. Thus, the set of neighbor cells for which PRS information is provided may be reduced to reduce the UE’s measurement burden as well as the signaling overhead. To this end, the set of neighbor cells for which the location server provides PRS information in the example may, e.g., be limited to cell# 1-3, cell# 1-5, cell#2-3 and cell#2-5, or as another option, cell#l-2, cell# 1-6, cell#2-2 and cell#2-6.
[0064] Furthermore, it may be uncertain where in cell# 1 (e.g., in which part of cell# 1) the UE is located at the time of the RTT measurement(s) in cell# 1. Therefore, to be safe and possibly provide some redundancy, the location server may provide the UE with PRS information for cell# 1-2, cell# 1-3, cell# 1-5 and cell# 1-6. The situation for the RTT measurement(s) in cell#2 may be similar, and consequently the location server may choose to provide PRS information for cell#2-2, cell#2-3, cell#2-5 and cell#2-6.
[0065] In one example, for multi-RTT positioning, one network node (e.g., location server) sends the information to the UE about the PRS information in Figure 3 of cell# 1 and cell#2 in Figure 2 for the TDOA measurement and PRS-RSRP measurement in the given time and frequency domain for each PRS, and the PRS information of cell# 1 for TDOA measurement and PRS-RSRP measurement is also associated with the PRS information of cell# 1-1, cell# 1-3 and cell# 1-5 for PRS-RSRP measurement in the given time and frequency domain for each PRS, and the PRS information of cell#2 for TDOA measurement and PRS-RSRP measurement is also associated with the PRS information of at least one of cell#2-l, cell#2-3 and cell#2-5 for PRS- RSRP measurement in the given time and frequency domain for each PRS. The UE reports UE Rx-Tx time difference related to PRS of cell# 1 , UE Rx-Tx time difference related to PRS of cell#2, PRS-RSRP of cell#l, PRS-RSRP of cell#l-l, PRS-RSRP of cell#l-3, PRS-RSRP of cell#l-5, PRS-RSRP of cell#2, PRS-RSRP of cell#2-l, PRS-RSRP of cell#2-3, and PRS-RSRP of cell#2-5 to the network node.
[0066] In another embodiment, the UE is configured with measurement configurations for one or multiple concerned neighbor cells that are close to an orbit, which may cause the mirror point issue. The configurations are associated with specific locations (e.g., configured/preconfigured coordinates). The UE only performs measurements towards those configured neighbor cells when the UE moves to the specific locations.
[0067] As a further elaboration (or extension) of this embodiment, a multi -RTT measurement in NTN typically involves multiple RTT measurements distributed in time. Due to this circumstance, there is a non-negligible probability that a handover occurs (i.e., the UE is handed over from one cell to another) during the multi -RTT measurement (e.g., between two of the RTT measurements), not only because of cell movement or cell switches, but also because of UE movements (or a combination of UE movements and cell movements/switches). If this happens because of a UE movement (or partly caused by UE movement, the neighbor cells whose PRSs the UE measures on (e.g., RSRP measurements) for the purpose of resolving the mirror ambiguity of the result of the multi-RTT measurement may preferably also be changed so that they are properly located in relation to the UE’s new location. To cope with this situation, the UE or the gNB (or one of the involved gNBs for an inter-gNB handover) may inform the location server of the handover, and the location server may then send new PRS information to the UE wherein the new PRS information is adapted to the UE’s new location (and/or new cell). Alternatively, the location server may already when the multi-RTT measurement is initially configured proactively provide information about additional PRSs (in additional neighbor cells), wherein the UE does not apply the information for an additional PRS unless a condition associated with the information is fulfilled, e.g. that the UE is handed over to a certain target cell.
[0068] In an embodiment, the UE is configured with measurement configurations for one or multiple concerned neighbor cells that are close to an orbit, which may cause the mirror point issue. The configurations are associated with specific time instants (e.g., configured/preconfigured coordinates). The UE only performs measurements towards those configured neighbor cells at those specific time instants.
[0069] As a further elaboration (or extension) of this embodiment, as previously described, the NTN cell covering a certain location changes over time due to moving cells (in moving cells deployments) or switches of the cell that cover a certain area (in quasi-Earth-fixed cells deployments). This means that the neighbor cells that are suitable for provision of the PRSs the UE should measure on for the purpose of resolving the mirror ambiguity of the result of the multi - RTT measurement may also change over time. Thus, the PRS information the location server provides to the UE may account for this by providing PRS information that is valid for different time periods, and provide indications of the time periods associated with the PRS information, so that the UE knows which PRS information to use at any given time.
[0070] In an embodiment, if the UE determines that there is no mirror point ambiguity issue foreseen, the UE may skip measurements to one or multiple concerned neighbor cells even though they are configured by the network to measure. In this case, the UE may signal the network the information comprising at least one of: IDs of neighbor cells that the UE has skipped for measurements; IDs of measurement configuration that the UE has skipped; time instants that the UE has skipped measurements for those neighbor cells; and cause indicating why the UE has skipped measurements for those neighbor cells.
[0071] In an embodiment, in addition to one or multiple measurement configurations for one or multiple concerned neighbor cells for addressing potential mirror point ambiguity issue, the network may also send signaling to the UE indicating at least one of: a time instant at which the UE can start measurements to the concerned neighbor cells, where a different time instant may be configured for different neighbor cell; a time instant at which the UE can stop measurements to the concerned neighbor cells, where a different time instant may be configured for different neighbor cell; an indicator for a neighbor cell indicating that the UE can start measurements to the neighbor cell; and/or an indicator for a neighbor cell indicating that the UE can stop measurements to the neighbor cell.
[0072] The signaling may be included in the same signaling message that comprises measurement configuration for the concerned neighbor cells. Alternatively, the signaling may be included in a separate signaling message that does not comprise measurement configuration for the concerned neighbor cells.
[0073] In one embodiment, one or multiple UE capability bits are defined for the UE to indicate whether the UE supports additional measurements of neighbor cells for addressing mirror point ambiguity.
[0074] For the above embodiments, signalling exchanged between the UE and the LMF may be carried via a LPP message (3GPP TS 37.355 version 17.4.0) or NAS signaling. [0075] For the above embodiments, signalling exchanged between the gNB and the LMF may be carried via aNRPPa message (3GPP TS 38.455 version 17.4.0) or NGAP signaling.
[0076] For the above embodiments, signaling exchanged between the UE and the gNB may be carried via one of: system information; RRC signaling; MAC CE; and/or LI signaling (e.g., DL signaling carried in PDCCH, or UL signaling carried in PUCCH, PRACH).
[0077] In one embodiment, one or more of the aforementioned methods may be used in conjunction with other positioning or non-positioning related measurements performed and reported by the UE or gNB for mirror image resolution. For example, UL-AoA measurements reported by the gNB may be used in conjunction with PRS-RSRP to further improve the reliability (e.g., increase the probability of correctly resolving the mirror image ambiguity) of mirror image ambiguity and/or to reduce the need to perform a large number of neighbor cell measurements.
[0078] In one embodiment, the location server and/or other network entity or node collects the RSRP data (e.g., PRS RSRP measurement data of serving cell and/or neighbor cells) of one or more UEs and the result of mirror image resolution. In addition, other parameters reported by the UE and/or gNB/LMF/OAM such as the respective PRS ID(s), satellite ID(s), cell ID(s), timestamp(s), UE reported location, satellite trajectory data (e.g., ephemeris), network-verified UE location, etc. related to the UE and the reported RSRP measurement may also be collected. The network can leverage this dataset to train a learning algorithm (e.g., based on the existing deep neural network-based learning models) to resolve mirror image ambiguity problem. After the model is trained, the network may input the UE reported information (which may be obtained using one or more embodiments described herein) for a UE requiring mirror image resolution to resolve mirror image ambiguity. This model-based result may be used exclusively or in conjunction with one or more of the measurement-based results for mirror image ambiguity to further refine the reliability (e.g., increase the probability of correctly resolving the mirror image ambiguity) of mirror image ambiguity solution. It may also reduce the need to fetch multiple measurements from the UE while achieving the same reliability in mirror image resolution, e.g., the UE may report fewer neighbor cell measurements (as opposed to the case where mirror image ambiguity resolution is performed based on direct measurements reported by the UE).
[0079] Figure 4 shows an example of a communication system 100 in accordance with some embodiments. In the example, the communication system 100 includes a telecommunication network 102 that includes an access network 104, such as a radio access network (RAN), and a core network 106, which includes one or more core network nodes 108. The access network 104 includes one or more access network nodes, such as network nodes 110a and 110b (one or more of which may be generally referred to as network nodes 110), or any other similar 3rd Generation Partnership Project (3GPP) access node or non-3GPP access point. The network nodes 110 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 112a, 112b, 112c, and 112d (one or more of which may be generally referred to as UEs 112) to the core network 106 over one or more wireless connections.
[0080] Example wireless communications over a wireless connection include transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 100 may include any number of wired or wireless networks, network nodes, UEs, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections. The communication system 100 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.
[0081] The UEs 112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and/or operable to communicate wirelessly with the network nodes 110 and other communication devices. Similarly, the network nodes 110 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 112 and/or with other network nodes or equipment in the telecommunication network 102 to enable and/or provide network access, such as wireless network access, and/or to perform other functions, such as administration in the telecommunication network 102.
[0082] In the depicted example, the core network 106 connects the network nodes 110 to one or more hosts, such as host 116. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 106 includes one more core network nodes (e.g., core network node 108) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and/or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 108. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and/or a User Plane Function (UPF).
[0083] The host 116 may be under the ownership or control of a service provider other than an operator or provider of the access network 104 and/or the telecommunication network 102, and may be operated by the service provider or on behalf of the service provider. The host 116 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio/video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.
[0084] As a whole, the communication system 100 of Figure 4 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and/or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.
[0085] In some examples, the telecommunication network 102 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 102. For example, the telecommunications network 102 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and/or Massive Machine Type Communication (mMTC)ZMassive loT services to yet further UEs.
[0086] In some examples, the UEs 112 are configured to transmit and/or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 104. Additionally, a UE may be configured for operating in single- or multi -RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi -radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).
[0087] In the example, the hub 114 communicates with the access network 104 to facilitate indirect communication between one or more UEs (e.g., UE 112c and/or 112d) and network nodes (e.g., network node 110b). In some examples, the hub 114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 114 may be a broadband router enabling access to the core network 106 for the UEs. As another example, the hub 114 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 110, or by executable code, script, process, or other instructions in the hub 114. As another example, the hub 114 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 114 then provides to the UE either directly, after performing local processing, and/or after adding additional local content. In still another example, the hub 114 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy loT devices.
[0088] The hub 114 may have a constant/persistent or intermittent connection to the network node 110b. The hub 114 may also allow for a different communication scheme and/or schedule between the hub 114 and UEs (e.g., UE 112c and/or 112d), and between the hub 114 and the core network 106. In other examples, the hub 114 is connected to the core network 106 and/or one or more UEs via a wired connection. Moreover, the hub 114 may be configured to connect to an M2M service provider over the access network 104 and/or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 110 while still connected via the hub 114 via a wired or wireless connection. In some embodiments, the hub 114 may be a dedicated hub - that is, a hub whose primary function is to route communications to/from the UEs from/to the network node 110b. In other embodiments, the hub 114 may be a nondedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 110b, but which is additionally capable of operating as a communication start and/or end point for certain data channels.
[0089] Figure 5 shows a UE 200 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle-mounted or vehicle embedded/integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.
[0090] A UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to- everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).
[0091] The UE 200 includes processing circuitry 202 that is operatively coupled via a bus 204 to an input/output interface 206, a power source 208, a memory 210, a communication interface 212, and/or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 2. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.
[0092] The processing circuitry 202 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 210. The processing circuitry 202 may be implemented as one or more hardware -implemented state machines (e.g., in discrete logic, field- programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 202 may include multiple central processing units (CPUs).
[0093] In the example, the input/output interface 206 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and/or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE 200. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.
[0094] In some embodiments, the power source 208 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source 208 may further include power circuitry for delivering power from the power source 208 itself, and/or an external power source, to the various parts of the UE 200 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 208. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 208 to make the power suitable for the respective components of the UE 200 to which power is supplied.
[0095] The memory 210 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 210 includes one or more application programs 214, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 216. The memory 210 may store, for use by the UE 200, any of a variety of various operating systems or combinations of operating systems.
[0096] The memory 210 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and/or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 210 may allow the UE 200 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 210, which may be or comprise a device -readable storage medium.
[0097] The processing circuitry 202 may be configured to communicate with an access network or other network using the communication interface 212. The communication interface 212 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 222. The communication interface 212 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter 218 and/or a receiver 220 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 218 and receiver 220 may be coupled to one or more antennas (e.g., antenna 222) and may share circuit components, software or firmware, or alternatively be implemented separately.
[0098] In the illustrated embodiment, communication functions of the communication interface 212 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short- range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and/or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol/intemet protocol (TCP/IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.
[0099] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 212, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient). [0100] As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.
[0101] A UE, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door/window sensor, a flood/moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or itemtracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and/or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE 200 shown in Figure 2.
[0102] As yet another specific example, in an loT scenario, a UE may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another UE and/or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.
[0103] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and/or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.
[0104] Figure 6 shows a network node 300 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a UE and/or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NRNodeBs (gNBs)).
[0105] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).
[0106] Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and/or Minimization of Drive Tests (MDTs).
[0107] The network node 300 includes a processing circuitry 302, a memory 304, a communication interface 306, and a power source 308. The network node 300 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 300 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 300 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 304 for different RATs) and some components may be reused (e.g., a same antenna 310 may be shared by different RATs). The network node 300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 300, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 300.
[0108] The processing circuitry 302 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node 300 components, such as the memory 304, to provide network node 300 functionality.
[0109] In some embodiments, the processing circuitry 302 includes a system on a chip (SOC). In some embodiments, the processing circuitry 302 includes one or more of radio frequency (RF) transceiver circuitry 312 and baseband processing circuitry 314. In some embodiments, the radio frequency (RF) transceiver circuitry 312 and the baseband processing circuitry 314 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 312 and baseband processing circuitry 314 may be on the same chip or set of chips, boards, or units.
[0110] The memory 304 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device-readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by the processing circuitry 302. The memory 304 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and/or other instructions capable of being executed by the processing circuitry 302 and utilized by the network node 300. The memory 304 may be used to store any calculations made by the processing circuitry 302 and/or any data received via the communication interface 306. In some embodiments, the processing circuitry 302 and memory 304 is integrated.
[oni] The communication interface 306 is used in wired or wireless communication of signaling and/or data between a network node, access network, and/or UE. As illustrated, the communication interface 306 comprises port(s)/terminal(s) 316 to send and receive data, for example to and from a network over a wired connection. The communication interface 306 also includes radio front-end circuitry 318 that may be coupled to, or in certain embodiments a part of, the antenna 310. Radio front-end circuitry 318 comprises fdters 320 and amplifiers 322. The radio front-end circuitry 318 may be connected to an antenna 310 and processing circuitry 302. The radio front-end circuitry may be configured to condition signals communicated between antenna 310 and processing circuitry 302. The radio front-end circuitry 318 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of fdters 320 and/or amplifiers 322. The radio signal may then be transmitted via the antenna 310. Similarly, when receiving data, the antenna 310 may collect radio signals which are then converted into digital data by the radio front-end circuitry 318. The digital data may be passed to the processing circuitry 302. In other embodiments, the communication interface may comprise different components and/or different combinations of components.
[0112] In certain alternative embodiments, the network node 300 does not include separate radio front-end circuitry 318, instead, the processing circuitry 302 includes radio front-end circuitry and is connected to the antenna 310. Similarly, in some embodiments, all or some of the RF transceiver circuitry 312 is part of the communication interface 306. In still other embodiments, the communication interface 306 includes one or more ports or terminals 316, the radio front-end circuitry 318, and the RF transceiver circuitry 312, as part of a radio unit (not shown), and the communication interface 306 communicates with the baseband processing circuitry 314, which is part of a digital unit (not shown).
[0113] The antenna 310 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. The antenna 310 may be coupled to the radio front-end circuitry 318 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In certain embodiments, the antenna 310 is separate from the network node 300 and connectable to the network node 300 through an interface or port.
[0114] The antenna 310, communication interface 306, and/or the processing circuitry 302 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node. Any information, data and/or signals may be received from a UE, another network node and/or any other network equipment. Similarly, the antenna 310, the communication interface 306, and/or the processing circuitry 302 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and/or signals may be transmitted to a UE, another network node and/or any other network equipment.
[0115] The power source 308 provides power to the various components of network node 300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 300 with power for performing the functionality described herein. For example, the network node 300 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 308. As a further example, the power source 308 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.
[0116] Embodiments of the network node 300 may include additional components beyond those shown in Figure 6 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein. For example, the network node 300 may include user interface equipment to allow input of information into the network node 300 and to allow output of information from the network node 300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 300.
[0117] Figure 7 is a block diagram of a host 400, which may be an embodiment of the host 116 of Figure 4, in accordance with various aspects described herein. As used herein, the host 400 may be or comprise various combinations hardware and/or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm. The host 400 may provide one or more services to one or more UEs.
[0118] The host 400 includes processing circuitry 402 that is operatively coupled via a bus 404 to an input/output interface 406, a network interface 408, a power source 410, and a memory 412. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 10 and 3, such that the descriptions thereof are generally applicable to the corresponding components of host 400.
[0119] The memory 412 may include one or more computer programs including one or more host application programs 414 and data 416, which may include user data, e.g., data generated by a UE for the host 400 or data generated by the host 400 for a UE. Embodiments of the host 400 may utilize only a subset or all of the components shown. The host application programs 414 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). The host application programs 414 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host 400 may select and/or indicate a different host for over-the-top services for a UE. The host application programs 414 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.
[0120] Figure 8 is a block diagram illustrating a virtualization environment 500 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 500 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized.
[0121] Applications 502 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.
[0122] Hardware 504 includes processing circuitry, memory that stores software and/or instructions executable by hardware processing circuitry, and/or other hardware devices as described herein, such as a network interface, input/output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 508a and 508b (one or more of which may be generally referred to as VMs 508), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein. The virtualization layer 506 may present a virtual operating platform that appears like networking hardware to the VMs 508.
[0123] The VMs 508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 506. Different embodiments of the instance of a virtual appliance 502 may be implemented on one or more of VMs 508, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.
[0124] In the context of NFV, a VM 508 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 508, and that part of hardware 504 that executes that VM, be it hardware dedicated to that VM and/or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 508 on top of the hardware 504 and corresponds to the application 502.
[0125] Hardware 504 may be implemented in a standalone network node with generic or specific components. Hardware 504 may implement some functions via virtualization. Alternatively, hardware 504 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 510, which, among others, oversees lifecycle management of applications 502. In some embodiments, hardware 504 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 512 which may alternatively be used for communication between hardware nodes and radio units.
[0126] Figure 9 shows a communication diagram of a host 602 communicating via a network node 604 with a UE 606 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE 112a of Figure 4 and/or UE 200 of Figure 5), network node (such as network node 110a of Figure 4 and/or network node 300 of Figure 6), and host (such as host 116 of Figure 4 and/or host 400 of Figure 7) discussed in the preceding paragraphs will now be described with reference to Figure 9.
[0127] Like host 400, embodiments of host 602 include hardware, such as a communication interface, processing circuitry, and memory. The host 602 also includes software, which is stored in or accessible by the host 602 and executable by the processing circuitry. The software includes a host application that may be operable to provide a service to a remote user, such as the UE 606 connecting via an over-the-top (OTT) connection 650 extending between the UE 606 and host 602. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection 650.
[0128] The network node 604 includes hardware enabling it to communicate with the host 602 and UE 606. The connection 660 may be direct or pass through a core network (like core network 106 of Figure 4) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet.
[0129] The UE 606 includes hardware and software, which is stored in or accessible by UE 606 and executable by the UE’s processing circuitry. The software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 606 with the support of the host 602. In the host 602, an executing host application may communicate with the executing client application via the OTT connection 650 terminating at the UE 606 and host 602. In providing the service to the user, the UE's client application may receive request data from the host's host application and provide user data in response to the request data. The OTT connection 650 may transfer both the request data and the user data. The UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT connection 650.
[0130] The OTT connection 650 may extend via a connection 660 between the host 602 and the network node 604 and via a wireless connection 670 between the network node 604 and the UE 606 to provide the connection between the host 602 and the UE 606. The connection 660 and wireless connection 670, over which the OTT connection 650 may be provided, have been drawn abstractly to illustrate the communication between the host 602 and the UE 606 via the network node 604, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
[0131] As an example of transmitting data via the OTT connection 650, in step 608, the host 602 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE 606. In other embodiments, the user data is associated with a UE 606 that shares data with the host 602 without explicit human interaction. In step 610, the host 602 initiates a transmission carrying the user data towards the UE 606. The host 602 may initiate the transmission responsive to a request transmitted by the UE 606. The request may be caused by human interaction with the UE 606 or by operation of the client application executing on the UE 606. The transmission may pass via the network node 604, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 612, the network node 604 transmits to the UE 606 the user data that was carried in the transmission that the host 602 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 614, the UE 606 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 606 associated with the host application executed by the host 602.
[0132] In some examples, the UE 606 executes a client application which provides user data to the host 602. The user data may be provided in reaction or response to the data received from the host 602. Accordingly, in step 616, the UE 606 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input/output interface of the UE 606. Regardless of the specific manner in which the user data was provided, the UE 606 initiates, in step 618, transmission of the user data towards the host 602 via the network node 604. In step 620, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 604 receives user data from the UE 606 and initiates transmission of the received user data towards the host 602. In step 622, the host 602 receives the user data carried in the transmission initiated by the UE 606.
[0133] One or more of the various embodiments improve the performance of OTT services provided to the UE 606 using the OTT connection 650, in which the wireless connection 670 forms the last segment. More precisely, the teachings of these embodiments may improve the data rate and latency and thereby provide benefits such as reduced user waiting time, better responsiveness, and better QoE. [0134] In an example scenario, factory status information may be collected and analyzed by the host 602. As another example, the host 602 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host 602 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host 602 may store surveillance video uploaded by a UE. As another example, the host 602 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs. As other examples, the host 602 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and/or transmitting data.
[0135] In some examples, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 650 between the host 602 and UE 606, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host 602 and/or UE 606. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 650 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 650 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 604. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host 602. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 650 while monitoring propagation times, errors, etc.
[0136] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and/or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.
[0137] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer- readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and/or by end users and a wireless network generally.
[0138] Figure 10 is a flowchart illustrating an example method in a network node, according to certain embodiments. In particular embodiments, one or more steps of Figure 10 may be performed by network node 300 described with respect to Figure 6 or a LMF. The network node is operating in an NTN.
[0139] The method begins at step 1012, where the network node (e.g., network node 300, LMF) determines a positioning configuration for a wireless device to measure downlink signals from a plurality of transmission/reception positions of at least one transmission/reception point. The positioning configuration comprises an indication of a plurality of transmission/reception positions of at least one main cell for which to perform positioning measurements and an indication of at least one associated cell for which to perform positioning measurements when the wireless device is subject to mirror position ambiguity.
[0140] In In particular embodiments, the positioning configuration further comprises an indication of time windows associated with the indication of the plurality of transmission/reception positions of the at least one main cell. The indication of time windows indicating time windows when the wireless device is able to perform positioning measurements in the at least one associated cell to resolve mirror position ambiguity. The positioning configuration may further comprise an indication of locations associated with the indication of the plurality of transmission/reception positions of the at least one main cell, the indication of locations indicating locations where the wireless device is able to perform positioning measurements in the at least one associated cell to resolve mirror position ambiguity.
[0141] In particular embodiments, one of the at least one associated cell is on a different side of an orbit of at least one of the at least one main cell.
[0142] In particular embodiments, the positioning configuration is for one of multiple round trip time positioning, downlink time difference of arrival positioning, or any other positioning method that may be subject to mirror position ambiguity.
[0143] In particular embodiments, network node comprises a location management function or a base station.
[0144] In particular embodiments, the positioning configuration comprises any of the positioning configurations described in the embodiments and examples above.
[0145] At step 1014, the network node transmits the positioning configuration to the wireless device. The wireless device using the positioning configuration to determine when and on what cells to perform measurements to resolve mirror position ambiguity.
[0146] Modifications, additions, or omissions may be made to method 1000 of Figure 10. Additionally, one or more steps in the method of Figure 10 may be performed in parallel or in any suitable order.
[0147] Figure 11 is a flowchart illustrating an example method in a wireless device, according to certain embodiments. In particular embodiments, one or more steps of Figure 11 may be performed by UE 200 described with respect to Figure 5. The wireless device is operating in an NTN.
[0148] The method begins at step 1112, where the wireless device (e.g., UE 200) receives a positioning configuration to measure downlink signals from a plurality of transmission/reception positions of at least one transmission/reception point. The positioning configuration comprises an indication of a plurality of transmission/reception positions of at least one main cell for which to perform positioning measurements and an indication of at least one associated cell for which to perform positioning measurements when the wireless device is subject to mirror position ambiguity.
[0149] In particular embodiments, the positioning configuration further comprises an indication of time windows associated with the indication of the plurality of transmission/reception positions of the at least one main cell. The indication of time windows indicating time windows when the wireless device is able to perform positioning measurements in the at least one associated cell to resolve mirror position ambiguity. The positioning configuration may further comprise an indication of locations associated with the indication of the plurality of transmission/reception positions of the at least one main cell. The indication of locations indicating locations where the wireless device is able to perform positioning measurements in the at least one associated cell to resolve mirror position ambiguity.
[0150] In particular embodiments, one of the at least one associated cell is on a different side of an orbit of at least one of the at least one main cell.
[0151] In particular embodiments, the downlink signals comprise a reference signal, such as a positioning reference signal, a CSI-RS, an SSB, or any other suitable signal.
[0152] In particular embodiments, the positioning configuration is for one of multiple round trip time positioning, downlink time difference of arrival positioning, or any other positioning method that may be subject to mirror position ambiguity.
[0153] In particular embodiments, the positioning configuration comprises any of the positioning configurations described in the embodiments and examples above.
[0154] At step 1114, the wireless device measures two or more downlink signals according to the received positioning configuration. In particular embodiments, the wireless device determines whether to perform measurements on the downlink signals based on a time for performing the measurement. The wireless device may determine whether to perform measurements on the downlink signals based on a location of the wireless device. The wireless device may transmit a report to a network node indicating at least one of which measurements were performed and which measurements were not performed.
[0155] Modifications, additions, or omissions may be made to method 1100 of Figure 11. Additionally, one or more steps in the method of Figure 11 may be performed in parallel or in any suitable order.
[0156] The foregoing description sets forth numerous specific details. It is understood, however, that embodiments may be practiced without these specific details. In other instances, well-known circuits, structures and techniques have not been shown in detail in order not to obscure the understanding of this description. Those of ordinary skill in the art, with the included descriptions, will be able to implement appropriate functionality without undue experimentation. [0157] References in the specification to “one embodiment,” “an embodiment,” “an example embodiment,” etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to implement such feature, structure, or characteristic in connection with other embodiments, whether or not explicitly described.
[0158] Although this disclosure has been described in terms of certain embodiments, alterations and permutations of the embodiments will be apparent to those skilled in the art. Accordingly, the above description of the embodiments does not constrain this disclosure. Other changes, substitutions, and alterations are possible without departing from the scope of this disclosure, as defined by the claims below.
[0159] Some example embodiments are described below.
1. A method performed by a location server for a non-terrestrial network (NTN), the method comprising:
- determining a positioning configuration for a wireless device to measure positioning reference signals (PRSs) from a plurality of transmission/reception points (TRPs), wherein the positioning configuration comprises an indication of a plurality of main cells for which to perform positioning measurements and an indication of associated cells for which to perform positioning measurements when the wireless device is subject to mirror position ambiguity; and
- transmitting the positioning configuration to the wireless device.
2. The method of the previous embodiment, wherein the positioning configuration further comprises an indication of time windows associated with the indication of the plurality of main cells indicating time windows when the wireless device should perform positioning measurements in the associated cell to resolve mirror position ambiguity.
3. The method of any one of the previous embodiments, wherein the positioning configuration further comprises an indication of locations associated with the indication of the plurality of main cells indicating locations where the wireless device should perform positioning measurements in the associated cell to resolve mirror position ambiguity.
4. The method of any one of the previous embodiments, wherein the positioning configuration comprises any of the time positioning configurations in the embodiments and examples described above.
Group A Embodiments
5. A method performed by a wireless device operating in a non-terrestrial network (NTN), the method comprising:
- receiving a positioning configuration to measure positioning reference signals (PRSs) from a plurality of transmission/reception points (TRPs), wherein the positioning configuration comprises an indication of a plurality of main cells for which to perform positioning measurements and an indication of associated cells for which to perform positioning measurements when the wireless device is subject to mirror position ambiguity; and
- measuring two or more PRSs according to the received positioning configuration.
6. The method of the previous embodiment, wherein the positioning configuration further comprises an indication of time windows associated with the indication of the plurality of main cells indicating time windows when the wireless device should perform positioning measurements in the associated cell to resolve mirror position ambiguity. The method of any one of the previous embodiments, wherein the positioning configuration further comprises an indication of locations associated with the indication of the plurality of main cells indicating locations where the wireless device should perform positioning measurements in the associated cell to resolve mirror position ambiguity. The method of any one of the previous embodiments, wherein the positioning configuration comprises any of the time positioning configurations in the embodiments and examples described above. The method of any one of the previous embodiments, wherein the wireless device determines whether to perform measurements in an associated cell based on a time for performing the measurement. The method of any one of the previous embodiments, wherein the wireless device determines whether to perform measurements in an associated cell based on a location of the wireless device. The method of any one of embodiments 9 and 10, wherein the wireless device transmits a report to a network node indicating which measurements were performed or which measurements were not performed. A method performed by a wireless device, the method comprising:
- any of the wireless device steps, features, or functions described above, either alone or in combination with other steps, features, or functions described above. The method of the previous embodiment, further comprising one or more additional wireless device steps, features or functions described above. The method of any of the previous embodiments, further comprising:
- providing user data; and
- forwarding the user data to a host computer via the transmission to the base station. Group B Embodiments
15. A method performed by a base station, the method comprising:
- any of the steps, features, or functions described above with respect to base station, either alone or in combination with other steps, features, or functions described above.
16. The method of the previous embodiment, further comprising one or more additional base station steps, features or functions described above.
17. The method of any of the previous embodiments, further comprising:
- obtaining user data; and
- forwarding the user data to a host computer or a wireless device.
Group C Embodiments
18. A mobile terminal comprising:
- processing circuitry configured to perform any of the steps of any of the Group A embodiments; and
- power supply circuitry configured to supply power to the wireless device.
19. A base station comprising:
- processing circuitry configured to perform any of the steps of any of the Group B embodiments;
- power supply circuitry configured to supply power to the wireless device.
20. A user equipment (UE) comprising:
- an antenna configured to send and receive wireless signals;
- radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; - the processing circuitry being configured to perform any of the steps of any of the Group A embodiments;
- an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry;
- an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and
- a battery connected to the processing circuitry and configured to supply power to the UE. A communication system including a host computer comprising:
- processing circuitry configured to provide user data; and
- a communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE),
- wherein the cellular network comprises a base station having a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the Group B embodiments. The communication system of the pervious embodiment further including the base station. The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station. The communication system of the previous 3 embodiments, wherein:
- the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and
- the UE comprises processing circuitry configured to execute a client application associated with the host application. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:
- at the host computer, providing user data; and
- at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the base station performs any of the steps of any of the Group B embodiments. The method of the previous embodiment, further comprising, at the base station, transmitting the user data. The method of the previous 2 embodiments, wherein the user data is provided at the host computer by executing a host application, the method further comprising, at the UE, executing a client application associated with the host application. A user equipment (UE) configured to communicate with a base station, the UE comprising a radio interface and processing circuitry configured to performs any of the previous 3 embodiments. A communication system including a host computer comprising:
- processing circuitry configured to provide user data; and
- a communication interface configured to forward user data to a cellular network for transmission to a user equipment (UE),
- wherein the UE comprises a radio interface and processing circuitry, the UE’s components configured to perform any of the steps of any of the Group A embodiments. The communication system of the previous embodiment, wherein the cellular network further includes a base station configured to communicate with the UE. The communication system of the previous 2 embodiments, wherein:
- the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and
- the UE’s processing circuitry is configured to execute a client application associated with the host application. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:
- at the host computer, providing user data; and
- at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the UE performs any of the steps of any of the Group A embodiments. The method of the previous embodiment, further comprising at the UE, receiving the user data from the base station. A communication system including a host computer comprising:
- communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station,
- wherein the UE comprises a radio interface and processing circuitry, the UE’s processing circuitry configured to perform any of the steps of any of the Group A embodiments. The communication system of the previous embodiment, further including the UE. The communication system of the previous 2 embodiments, further including the base station, wherein the base station comprises a radio interface configured to communicate with the UE and a communication interface configured to forward to the host computer the user data carried by a transmission from the UE to the base station. The communication system of the previous 3 embodiments, wherein:
- the processing circuitry of the host computer is configured to execute a host application; and
- the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data. The communication system of the previous 4 embodiments, wherein:
- the processing circuitry of the host computer is configured to execute a host application, thereby providing request data; and - the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data in response to the request data. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:
- at the host computer, receiving user data transmitted to the base station from the UE, wherein the UE performs any of the steps of any of the Group A embodiments. The method of the previous embodiment, further comprising, at the UE, providing the user data to the base station. The method of the previous 2 embodiments, further comprising:
- at the UE, executing a client application, thereby providing the user data to be transmitted; and
- at the host computer, executing a host application associated with the client application. The method of the previous 3 embodiments, further comprising:
- at the UE, executing a client application; and
- at the UE, receiving input data to the client application, the input data being provided at the host computer by executing a host application associated with the client application,
- wherein the user data to be transmitted is provided by the client application in response to the input data. A communication system including a host computer comprising a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, wherein the base station comprises a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the Group B embodiments. The communication system of the previous embodiment further including the base station. The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station. The communication system of the previous 3 embodiments, wherein:
- the processing circuitry of the host computer is configured to execute a host application;
- the UE is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:
- at the host computer, receiving, from the base station, user data originating from a transmission which the base station has received from the UE, wherein the UE performs any of the steps of any of the Group A embodiments. The method of the previous embodiment, further comprising at the base station, receiving the user data from the UE. The method of the previous 2 embodiments, further comprising at the base station, initiating a transmission of the received user data to the host computer.

Claims

Claims
1. A method performed by a network node operating in a non-terrestrial network, the method comprising: determining (1012) a positioning configuration for a wireless device to measure downlink signals from a plurality of transmission/reception positions of at least one transmission/reception point, wherein the positioning configuration comprises an indication of a plurality of transmission/reception positions of at least one main cell for which to perform positioning measurements and an indication of at least one associated cell for which to perform positioning measurements when the wireless device is subject to mirror position ambiguity; and transmitting (1014) the positioning configuration to the wireless device.
2. The method of claim 1, wherein the positioning configuration further comprises an indication of time windows associated with the indication of the plurality of transmission/reception positions of the at least one main cell, the indication of time windows indicating time windows when the wireless device is able to perform positioning measurements in the at least one associated cell to resolve mirror position ambiguity.
3. The method of any one of claims 1 -2, wherein the positioning configuration further comprises an indication of locations associated with the indication of the plurality of transmission/reception positions of the at least one main cell, the indication of locations indicating locations where the wireless device is able to perform positioning measurements in the at least one associated cell to resolve mirror position ambiguity.
4. The method of any one of claims 1-3, wherein one of the at least one associated cell is on a different side of an orbit of at least one of the at least one main cell.
5. The method of any one of claims 1-4, wherein the downlink signals comprise a reference signal.
6. The method of claim 5, wherein the reference signal comprises a positioning reference signal.
7. The method of any one of claims 1-6, wherein the positioning configuration is for one of multiple round trip time positioning or downlink time difference of arrival positioning.
8. The method of any one of claims 1-7, wherein network node comprises a location management function.
9. A network node (300) comprising processing circuitry (302) operable to: determine a positioning configuration for a wireless device to measure downlink signals from a plurality of transmission/reception positions of at least one transmission/reception point, wherein the positioning configuration comprises an indication of a plurality of transmission/reception positions of at least one main cell for which to perform positioning measurements and an indication of at least one associated cell for which to perform positioning measurements when the wireless device is subject to mirror position ambiguity; and transmit the positioning configuration to the wireless device.
10. The network node of claim 9, wherein the positioning configuration further comprises an indication of time windows associated with the indication of the plurality of transmission/reception positions of the at least one main cell, the indication of time windows indicating time windows when the wireless device is able to perform positioning measurements in the at least one associated cell to resolve mirror position ambiguity.
11. The network node of any one of claims 9-10, wherein the positioning configuration further comprises an indication of locations associated with the indication of the plurality of transmission/reception positions of the at least one main cell, the indication of locations indicating locations where the wireless device is able to perform positioning measurements in the at least one associated cell to resolve mirror position ambiguity.
12. The network node of any one of claims 9-11, wherein one of the at least one associated cell is on a different side of an orbit of at least one of the at least one main cell.
13. The network node of any one of claims 9-12, wherein the downlink signals comprise a reference signal.
14. The network node of claim 13, wherein the reference signal comprises a positioning reference signal.
15. The network node of any one of claims 9-14, wherein the positioning configuration is for one of multiple round trip time positioning or downlink time difference of arrival positioning.
16. The network node of any one of claims 9-15, wherein network node comprises a location management function.
17. A method performed by a wireless device operating in a non-terrestrial network, the method comprising: receiving (1112) a positioning configuration to measure downlink signals from a plurality of transmission/reception positions of at least one transmission/reception point, wherein the positioning configuration comprises an indication of a plurality of transmission/reception positions of at least one main cell for which to perform positioning measurements and an indication of at least one associated cell for which to perform positioning measurements when the wireless device is subject to mirror position ambiguity; and measuring (1114) two or more downlink signals according to the received positioning configuration.
18. The method of claim 17, wherein the positioning configuration further comprises an indication of time windows associated with the indication of the plurality of transmission/reception positions of the at least one main cell, the indication of time windows indicating time windows when the wireless device is able to perform positioning measurements in the at least one associated cell to resolve mirror position ambiguity.
19. The method of any one of claims 17-18, wherein the positioning configuration further comprises an indication of locations associated with the indication of the plurality of transmission/reception positions of the at least one main cell, the indication of locations indicating locations where the wireless device is able to perform positioning measurements in the at least one associated cell to resolve mirror position ambiguity.
20. The method of any one of claims 17-19, wherein one of the at least one associated cell is on a different side of an orbit of at least one of the at least one main cell.
21. The method of any one of claims 17-20, wherein the downlink signals comprise a reference signal.
22. The method of claim 21, wherein the reference signal comprises a positioning reference signal.
23. The method of any one of claims 17-22, wherein the positioning configuration is for one of multiple round trip time positioning or downlink time difference of arrival positioning.
24. The method of any one of claims 17-23, wherein the wireless device determines whether to perform measurements on the downlink signals based on a time for performing the measurement.
25. The method of any one of claims 17-24, wherein the wireless device determines whether to perform measurements on the downlink signals based on a location of the wireless device.
26. The method of any one of claims 24 and 25, wherein the wireless device transmits a report to a network node indicating at least one of which measurements were performed and which measurements were not performed.
27. A wireless device (200) comprising processing circuitry (202), the processing circuitry operable to: receive a positioning configuration to measure downlink signals from a plurality of transmission/reception positions of at least one transmission/reception point, wherein the positioning configuration comprises an indication of a plurality of transmission/reception positions of at least one main cell for which to perform positioning measurements and an indication of at least one associated cell for which to perform positioning measurements when the wireless device is subject to mirror position ambiguity; and measure two or more downlink signals according to the received positioning configuration.
28. The wireless device of claim 27, wherein the positioning configuration further comprises an indication of time windows associated with the indication of the plurality of transmission/reception positions of the at least one main cell, the indication of time windows indicating time windows when the wireless device is able to perform positioning measurements in the at least one associated cell to resolve mirror position ambiguity.
29. The wireless device of any one of claims 27-28, wherein the positioning configuration further comprises an indication of locations associated with the indication of the plurality of transmission/reception positions of the at least one main cell, the indication of locations indicating locations where the wireless device is able to perform positioning measurements in the at least one associated cell to resolve mirror position ambiguity.
30. The wireless device of any one of claims 27-29, wherein one of the at least one associated cell is on a different side of an orbit of at least one of the at least one main cell.
31. The wireless device of any one of claims 27-30, wherein the downlink signals comprise a reference signal.
32. The wireless device of claim 31, wherein the reference signal comprises a positioning reference signal.
33. The method of any one of claims 27-32, wherein the positioning configuration is for one of multiple round trip time positioning or downlink time difference of arrival positioning.
34. The wireless device of any one of claims 27-33, wherein the wireless device determines whether to perform measurements on the downlink signals based on a time for performing the measurement.
35. The wireless device of any one of claims 27-34, wherein the wireless device determines whether to perform measurements on the downlink signals based on a location of the wireless device.
36. The wireless device of any one of claims 34 and 35, wherein the wireless device transmits a report to a network node indicating at least one of which measurements were performed and which measurements were not performed.
EP24719898.9A 2023-04-07 2024-04-05 Ntn positioning using neighbor cell measurements Pending EP4666447A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202363495024P 2023-04-07 2023-04-07
PCT/IB2024/053362 WO2024209425A1 (en) 2023-04-07 2024-04-05 Ntn positioning using neighbor cell measurements

Publications (1)

Publication Number Publication Date
EP4666447A1 true EP4666447A1 (en) 2025-12-24

Family

ID=90789342

Family Applications (1)

Application Number Title Priority Date Filing Date
EP24719898.9A Pending EP4666447A1 (en) 2023-04-07 2024-04-05 Ntn positioning using neighbor cell measurements

Country Status (2)

Country Link
EP (1) EP4666447A1 (en)
WO (1) WO2024209425A1 (en)

Also Published As

Publication number Publication date
WO2024209425A1 (en) 2024-10-10

Similar Documents

Publication Publication Date Title
US20240406923A1 (en) Positioning Reference Signal Transmission and Measurement in a Wireless Communication Network
US20220369069A1 (en) Modifying an event-based positioning procedure configured in a wireless device
WO2024102050A1 (en) Data collection for positioning
WO2024171135A1 (en) Systems and methods for optimization of time division duplex slot utilization for air to ground
EP4666105A1 (en) Methods to convey the environment type knowledge to assist in radio signal based sensing
EP4666447A1 (en) Ntn positioning using neighbor cell measurements
WO2024209430A1 (en) Ntn positioning time sequence based measurement
US20250291049A1 (en) Associating carrier phase measurements with paths for positioning
US20250063574A1 (en) Mac ce signaling for supporting both joint dl/ul tci and separate dl/ul tci operations
WO2025233806A1 (en) Positioning measurement configuration
WO2024237846A1 (en) Carrier/positioning frequency layer configuration for carrier phase measurement performed together with legacy positioning measurement
WO2024209445A1 (en) Methods for signaling information for aggregated reference signals for positioning measurement
WO2025034156A1 (en) Methods for distributing reference measurements for carrier phase based positioning
WO2025172969A1 (en) Determining an rtoa reference time for ai/ml based user equipment positioning
WO2025134067A1 (en) Ai/ml positioning for location management function
WO2024209427A1 (en) Sequence initialization for sidelink reference signals
WO2024237834A1 (en) Measurement report enhancement for frequency hopping in positioning
WO2025172485A1 (en) Network assisted ai/ml model validation for positioning
WO2023132773A1 (en) Signaling communication device transmission timing error group association for uplink time difference of arrival
WO2025172964A1 (en) Complex valued data for ai/ml
WO2024033887A1 (en) Measurement assisted sidelink ranging
WO2025134060A1 (en) Methods to support enhanced reporting of positioning information based on gnb-du ai/ml inference side model
WO2025233919A1 (en) Efficient signaling of path timing for machine learning
WO2024236432A1 (en) Methods and apparatuses for selecting a ranging technique
WO2025233913A1 (en) Efficient signaling of sample timing for machine learning

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: UNKNOWN

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20250917

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC ME MK MT NL NO PL PT RO RS SE SI SK SM TR