Positioning of a mobile device using an enhanced exchange of capabilities

Apparatuses and methods for user equipment (UE) positioning are disclosed based on a coverage enhancement level or internal signaling delay for the UE. In one embodiment, a method at a UE may include receiving a request capabilities message from a server, determining one or more capabilities of the UE, where the one or more capabilities include at least one of information for at least one internal signaling path of the UE or information for a coverage enhancement level of the UE, sending a first response message to the server, where the first response message includes the one or more capabilities of the UE, receiving a request for location measurements from the server based at least in part on the one or more capabilities of the UE, obtaining the location measurements, and sending a second response message to the server, where the second response message comprises the location measurements.

FIELD

The present disclosure relates to the field of mobile communications. In particular, the present disclosure relates to apparatuses and methods for supporting positioning of a mobile device using an enhanced exchange of capabilities.

BACKGROUND

In existing mobile devices, different implementations can have varying radio frequency front-end designs with varying numbers of components. These variations in design can produce different internal delays in a Radio Frequency (RF) receiver path. This internal delay can impact the accuracy of timing measurements obtained by a mobile device to support positioning of the mobile device. For example, measurements of a Reference Signal Time Difference (RSTD) to support Observed Time Difference of Arrival (OTDOA) positioning may have reduced accuracy due to differences in RF internal delays for the different signals being measured in the case of, for example, inter-frequency signals.

In addition, coverage enhancement (CE) has been introduced by the Third Generation Partnership Project (3GPP) for Long Term Evolution (LTE) wireless access to provide extended wireless coverage to mobile devices in remote locations/basements etc. With CE, improved RF sensitivity is achieved via added repetitions of transmission on both uplink and downlink. Hence, in scenarios where a mobile device attempts to obtain location measurements (e.g. RSTD measurements) in CE mode, the number of repetitions may impact (e.g. increase) the time taken for the mobile device to complete and send back the measurement results to a location server such as an Enhanced Serving Mobile Location Center (E-SMLC). This extra delay may result in a failure to locate the mobile device—e.g. if the overall delay in obtaining measurement results from a mobile device exceeds the required time to obtain a position for the mobile device.

Therefore, it would be desirable to improve the accuracy of positioning to mitigate or overcome the above effects.

SUMMARY

According to aspects of the present disclosure, a UE can be configured to share details of the current CE Level and an estimate of UE internal delay via either the LPP Provide Capabilities (PC) message or the LPP Provide Location Information (PLI) message to the E-SMLC (or SUPL SLP). The E-SMLC can measure the round trip time (RTT) for the exchange of LPP Request Capabilities (RC) and PC messages or the RTT for exchange of LPP Request Location Information (RLI) and PLI messages. The UE can include in the LPP PC or LPP PLI the internal UE delay between receiving the RC or RLI message, respectively, and send the PC or RLI message. Subtracting internal UE delay from the measured RTT can give the RTT for the message transmission part including the effects of CE mode and receive chain delay. This approach enables the E-SMLC to better estimate the capability of the UE to obtain and return RSTD measurements within certain required response time.

According to aspects of the present disclosure, a UE may be configured to provide the E-SMLC with internal delay information per receive chain, the receive chain tag for a neighbor cell PRS measurement and the CE coverage level for the UE in an LPP PC or LPP PLI. The internal UE delay may include the time taken when a PRS signal is received from the UE antenna until the signal is available internally for baseband processing and measurement. This delay can be characterized and pre-stored in a look up table. Knowledge of this delay can be used to accurately measure an RTT between the E-SMLC and UE. For example, when returning an LPP Provide Capabilities message, a UE may include the internal UE delay which the E-SMLC can subtract to estimate RTT.

Embodiments of apparatuses and methods for enhanced device capability exchange in mobile positioning applications are disclosed. In one embodiment, a method of positioning by a mobile device may include receiving by a transceiver of the mobile device a request capabilities message from a server, determining by a processor of the mobile device one or more capabilities of the mobile device, where the one or more capabilities of the mobile device include at least one of information for at least one internal signaling path of the mobile device or information for a coverage enhancement level of the mobile device, sending by the transceiver a first response message to the server, where the first response message includes the one or more capabilities of the mobile device, receiving by the transceiver a request for location measurements from the server based at least in part on the one or more capabilities of the mobile device, obtaining by the transceiver and the processor the location measurements, and sending by the transceiver a second response message to the server, where the second response message comprises the location measurements.

According to aspects of the present disclosure, the one or more capabilities of the mobile device include the information for the coverage enhancement level, where the request for location measurements is further based at least in part on the information for the coverage enhancement level. The information for the at least one internal signaling path comprises an internal delay of the at least one internal signaling path. The information for the coverage enhancement level may include at least one of a transmission power level for the mobile device, a number of repetitions of a message broadcast by a serving base station and received and successfully decoded by the mobile device, a number of repetitions of a message sent by the mobile device to the serving base station, the message acknowledged by the serving base station, or some combinations thereof. The location measurements may include measurements of a reference signal time difference for Observed Time Difference of Arrival (OTDOA) positioning. The mobile device communicates with the server using Narrow Band Internet of Things (NB-IoT) wireless access. The server is an Enhanced Serving Mobile Location Center (E-SMLC), a Secure User Plane Location (SUPL) Location Platform (SLP), or a Location Management Function (LMF).

In some implementations, the method may further include determining the internal delay of the at least one internal signaling path based on at least one of a type of antenna, a transceiver, a power amplifier or an antenna switch used by the at least one internal signaling path. The method may further include determining a first response delay between a time of receiving the request capabilities message and a time of sending the first response message, where the information for the coverage enhancement level comprises the first response delay. The server may be configured to determine a coverage enhancement level for the mobile device based on a difference between the first response delay and a second response delay, where the server measures the second response delay, and where the second response delay comprises a difference between a time of sending the request capabilities message at the server and a time of receiving the first response message at the server.

According to aspects of the present disclosure, determining the information for the coverage enhancement level may include receiving first repetitions of a signal, the signal broadcast by a serving base station, the first repetitions based on a first coverage enhancement level, determining whether the first repetitions of the signal are successfully decoded, and including the first coverage enhancement level in the information for the coverage enhancement level when the first repetitions of the signal are successfully decoded.

Determining the information for the coverage enhancement level may further include in response to the first repetitions of the signal not being successfully decoded, receiving second repetitions of the signal, the second repetitions based on a second coverage enhancement level, the second repetitions including the first repetitions, determining whether the second repetitions of the signal are successfully decoded, and including the second coverage enhancement level in the information for the coverage enhancement level when the second repetitions of the signal are successfully decoded.

The method of positioning by a mobile device may further include receiving by the transceiver assistance data from the server based at least in part on the one or more capabilities of the mobile device, and obtaining by the transceiver and the processor the location measurements, based at least in part on the assistance data.

In another embodiment, a device may include a transceiver configured to receive a request capabilities message from a server, a processor configured to determine one or more capabilities of the mobile device, where the one or more capabilities of the mobile device include at least one of information for at least one internal signaling path of the mobile device or information for a coverage enhancement level of the mobile device, the transceiver is further configured to send a first response message to the server, where the first response message includes the one or more capabilities of the mobile device, and receive a request for location measurements from the server based at least in part on the one or more capabilities of the mobile device, the processor is further configured to obtain the location measurements; and the transceiver is further configured to send a second response message to the server, where the second response message comprises the location measurements.

DESCRIPTION OF EMBODIMENTS

Embodiments of apparatuses and methods for enhanced device capability exchange for mobile positioning applications are disclosed. The following descriptions are presented to enable any person skilled in the art to make and use the disclosure. Descriptions of specific embodiments and applications are provided only as examples. Various modifications and combinations of the examples described herein will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other examples and applications without departing from the scope of the disclosure. Thus, the present disclosure is not intended to be limited to the examples described and shown, but is to be accorded the scope consistent with the principles and features disclosed herein. The word “exemplary” or “example” is used herein to mean “serving as an example, instance, or illustration.” Any aspect or embodiment described herein as “exemplary” or as an “example” in not necessarily to be construed as preferred or advantageous over other aspects or embodiments.

According to aspects of the present disclosure, the terms device, mobile device, wireless device, terminal, mobile terminal and user equipment (UE) may be used interchangeably without altering the scope of the disclosure. For instance, a device to device communication may refer to communication between two UEs. A mobile device or UE refers to a mobile station such as a cellular or other wireless communication device, personal communication system (PCS) device, personal navigation device, Personal Information Manager (PIM), Personal Digital Assistant (PDA), cellphone, smartphone, laptop, tablet, tracking device or other suitable mobile device which is capable of sending and receiving wireless communications. The term “mobile device” or “UE” is also intended to include devices which communicate with a personal navigation device (PND), such as by short-range wireless, infrared, wireline connection, or other connection, regardless of whether satellite signal reception, assistance data reception, and/or position-related processing occur at the device or at the PND. Also, a “mobile device” or “UE” may include all devices, including wireless communication devices, computers, laptops, etc. which are capable of communication with a server, such as via the Internet, Wi-Fi, or other network, and regardless of whether satellite signal reception, assistance data reception, and/or position-related processing occurs at the device, at a server, or at another device associated with the network. Any operable combination of the above is also considered as a “mobile device” or “UE”.

FIG. 1illustrates an exemplary network architecture100for location support of a UE102that supports and is currently using Narrow Band Internet of Things (NB-IoT) radio access or LTE radio access, which may be used to implement the techniques described herein below. The network architecture100may be referred to as an Evolved Packet System (EPS). As illustrated, the network architecture100may include a UE102, an Evolved Universal Terrestrial Radio Access Network (E-UTRAN)120, and an Evolved Packet Core (EPC)130. The E-UTRAN120and the EPC130may be part of a Visited Public Land Mobile Network (VPLMN) that is a serving network for UE102and communicates with a Home Public Land Mobile Network (HPLMN)140for UE102. The VPLMN E-UTRAN120, VPLMN EPC130and/or HPLMN140may interconnect with other networks. For example, the Internet may be used to carry messages to and from different networks such as the HPLMN140and the VPLMN EPC130. For simplicity these networks and associated entities and interfaces are not shown. As shown, the network architecture100provides packet-switched services to UE102. However, as those skilled in the art will readily appreciate, the various concepts presented throughout this disclosure may be extended to networks providing circuit-switched services.

The UE102may be any electronic device configured for NB-IoT and/or LTE radio access. The UE102may be referred to as a device, a wireless device, a mobile terminal, a terminal, a mobile station (MS), a mobile device, a Secure User Plane Location (SUPL) Enabled Terminal (SET) or by some other name and may correspond to (or be part of) a smart watch, digital glasses or other head-mounted display, fitness monitor, smart car, smart appliance, cellphone, smartphone, laptop, tablet, personal digital assistant (PDA), personal media player, tracking device, control device, or some other portable or moveable device. A UE102may comprise a single entity or may comprise multiple entities such as in a personal area network where a user may employ audio, video and/or data I/O devices and/or body sensors and a separate wireline or wireless modem. Typically, though not necessarily, a UE102may support wireless communication with one or more types of Wireless Wide Area Network (WWAN) such as a WWAN supporting Global System for Mobile Communications (GSM), Code Division Multiple Access (CDMA), Wideband CDMA (WCDMA), LTE, NB-IoT, Enhanced machine type communication (eMTC) also referred to as LTE category M1 (LTE-M), Fifth Generation (5G) New Radio (NR), High Rate Packet Data (HRPD), WiMax, etc. VPLMN EPC130combined with VPLMN E-UTRAN120, and HPLMN140, may be examples of a WWAN. A UE102may also support wireless communication with one or more types of Wireless Local Area Network (WLAN) such as a WLAN supporting IEEE 802.11 WiFi (also referred to as Wi-Fi) or Bluetooth® (BT). UE102may also support communication with one or more types of wireline network such as by using a Digital Subscriber Line (DSL), or packet cable for example. AlthoughFIG. 1shows only one UE102, there may be many other UEs that can each correspond to UE102.

The UE102may enter a connected state with a wireless communication network that may include the E-UTRAN120and EPC130. In one example, UE102may communicate with a cellular communication network by transmitting wireless signals to, and/or receiving wireless signals from, a cellular transceiver, such as an evolved Node B (eNB)104in the E-UTRAN120. The E-UTRAN120may include one or more additional eNBs106. The eNB104provides user plane (UP) and control plane (CP) protocol terminations toward UE102. The eNB104may be a serving eNB for UE102and may also be referred to as a base station, a base transceiver station, a radio base station, a radio transceiver, a radio network controller, a transceiver function, a base station subsystem (BSS), an extended service set (ESS), an NR NodeB (gNB) or by some other suitable terminology. The UE102also may transmit wireless signals to, or receive wireless signals from, a local transceiver (not shown inFIG. 1), such as an access point (AP), femtocell, Home Base Station, small cell base station, Home Node B (HNB) or Home eNodeB (HeNB), which may provide access to a WLAN (e.g., IEEE 802.11 network), a wireless personal area network (WPAN, e.g., Bluetooth network) or a cellular network (e.g., an LTE network or other WWAN such as those discussed in the next paragraph). Of course, it should be understood that these are merely examples of networks that may communicate with a mobile device over a wireless link, and claimed subject matter is not limited in this respect.

Examples of network technologies that may support wireless communication include NB-IoT, but may further include GSM, CDMA, WCDMA, LTE, NR, HRPD and eMTC radio types. NB-IoT, GSM, WCDMA, LTE, eMTC and NR are technologies defined by the Third Generation Partnership Project (3GPP). CDMA and HRPD are technologies defined by the Third Generation Partnership Project 2 (3GPP2). Cellular transceivers, such as eNBs104and106, may comprise deployments of equipment providing subscriber access to a wireless telecommunication network for a service (e.g., under a service contract). Here, a cellular transceiver (e.g. eNB104) may perform functions of a cellular base station in servicing subscriber devices within a cell determined based, at least in part, on a range at which the cellular transceiver is capable of providing access service.

The eNBs104and106are connected by an interface (e.g., the 3GPP S1 interface) to the VPLMN EPC130. The EPC130includes a Mobility Management Entity (MME)108, and a Serving Gateway (SGW)112through which data (e.g., Internet Protocol (IP) packets) may be transferred to and from UE102. The MME108may be the serving MME for UE102and is then the control node that processes the signaling between UE102and the EPC130and supports attachment and network connection of UE102, mobility of UE102(e.g., via handover between network cells and tracking areas) as well as establishing and releasing data bearers on behalf of UE102. The MME108may also support data transfer to and from UE102using a 3GPP Cellular Internet of Things (CIoT) feature known as CIoT CP optimization in which data packets are transferred to and from the UE102via MME108, rather than by bypassing MME108, in order to avoid the overhead of establishing and releasing data bearers for UE102. Generally, MME108provides bearer and connection management for UE102and may be connected to the SGW112, the eNBs104and106, an Enhanced Serving Mobile Location Center (E-SMLC)110and a Visited Gateway Mobile Location Center (V-GMLC)116in the VPLMN EPC130.

The E-SMLC110may be a location server (LS) that supports location of UE102using the 3GPP control plane (CP) location solution defined in 3GPP technical specifications (TSs) 23.271 and 36.305. E-SMLC110may exchange messages with UE102for a positioning protocol as part of a CP location session to obtain a location for UE102. The positioning protocol may be the 3GPP LTE Positioning Protocol (LPP) defined in 3GPP TS 36.355 and/or may be the LPP Extensions protocol (LPPe) defined by the Open Mobile Alliance (OMA). The V-GMLC116, which may also be referred to simply as a Gateway Mobile Location Center (GMLC), may provide access on behalf of an external client (e.g., external client150) or another network (e.g., HPLMN140) to the location of UE102. The external client150may be a web server or remote application that may have some association with UE102(e.g., may be accessed by a user of UE102via VPLMN E-UTRAN120, VPLMN EPC130and HPLMN140). The external client150may also be a server, application or computer system providing a location service to some other user or users which may include obtaining and providing the location of UE102(e.g., to enable a service such as friend or relative finder, asset tracking or child or pet location).

As illustrated, the HPLMN140includes a Home GMLC (H-GMLC)148that may be connected to the V-GMLC116(e.g., via the Internet), as well as a Packet Data Network Gateway (PDG)114that may be connected to the SGW112(e.g., via the Internet). The PDG114may provide UE102with Internet Protocol (IP) address allocation and IP and other data access to external networks (e.g., the Internet) and to external clients (e.g., external client150) and external servers, as well as other data transfer related functions. In some cases, PDG114may be located in VPLMN EPC130and not in HPLMN140when UE102receives local IP breakout from VPLMN EPC130. The PDG114may be connected to a location server (LS), such as a Home SUPL Location Platform (H-SLP)118. The H-SLP118may support the SUPL UP location solution defined by OMA and may support location services for UE102based on subscription information for UE102stored in H-SLP118. In some embodiments of network architecture100, a Discovered SLP (D-SLP) or Emergency SLP (E-SLP) (not shown inFIG. 1), in or accessible from VPLMN EPC130, may be used to locate UE102using the SUPL UP location solution. H-SLP118and E-SMLC110in network architecture100are both examples of an LS that may employ the LPP and/or combined LPP and LPPe (LPP/LPPe) protocols for positioning of UE102.

In a CP location solution, such as the 3GPP CP location solution defined in 3GPP TS 23.271 and TS 36.305, signaling (e.g. including LPP, LPP/LPPe and other messages) to support location of UE102may be transferred between participating entities (e.g. V-GMLC116, MME108, E-SMLC110, eNB104and UE102) using existing signaling interfaces and protocols for VPLMN EPC130and E-UTRAN120. In contrast, in a UP location solution such as SUPL, signaling (e.g. such as SUPL messages carrying embedded LPP and/or LPP/LPPe messages) to support location of UE102may be transferred between participating entities (e.g. UE102and H-SLP118) using data bearers (e.g. using the Internet Protocol (IP)).

The H-GMLC148may be connected to a Home Subscriber Server (HSS)145for UE102, which is a central database that contains user-related and subscription-related information for UE102. H-GMLC148may provide location access to UE102on behalf of external clients such as external client150. One or more of H-GMLC148, PDG114, and H-SLP118may be connected to external client150, e.g., through another network, such as the Internet. In some cases, a Requesting GMLC (R-GMLC) located in another PLMN (not shown inFIG. 1) may be connected to H-GMLC148(e.g., via the Internet) in order to provide location access to UE102on behalf of external clients connected to the R-GMLC. The R-GMLC, H-GMLC148and V-GMLC116may support location access to UE102using the 3GPP CP solution defined in 3GPP TS 23.271.

It should be understood that while a VPLMN (comprising VPLMN E-UTRAN120and VPLMN EPC130) and a separate HPLMN140are illustrated inFIG. 1, both PLMNs (networks) may be the same PLMN. In that case, (i) H-SLP118, PDG114, and HSS145may be in the same network (EPC) as MME108and E-SMLC110, and (ii) V-GMLC116and H-GMLC148may be the same GMLC.

In particular implementations, UE102may have circuitry and processing resources capable of obtaining location related measurements (also referred to as location measurements and as measurements), such as measurements for signals received from Global Positioning System (GPS) or other Satellite Positioning System (SPS) space vehicles (SVs)160, measurements for cellular transceivers such as eNBs104and106, and/or measurements for local transceivers such as WiFi APs. UE102may further have circuitry and processing resources capable of computing a position fix or estimated location of UE102based on these location related measurements. In some implementations, location related measurements obtained by UE102may be transferred to an LS, such as E-SMLC110or H-SLP118, after which the LS may estimate or determine a location for UE102based on the measurements.

Location related measurements obtained by UE102may include measurements of signals received from SVs160belonging to an SPS or Global Navigation Satellite System (GNSS) such as GPS, GLONASS, Galileo or Beidou and/or may include measurements of signals received from terrestrial transmitters fixed at known locations (e.g., such as eNB104, eNB106or other local transceivers). UE102or a separate LS (e.g., E-SMLC110or H-SLP118) may then obtain a location estimate for UE102based on these location related measurements using any one of several position methods such as, for example, GNSS, Assisted GNSS (A-GNSS), Advanced Forward Link Trilateration (AFLT), Observed Time Difference of Arrival (OTDOA), Enhanced Cell ID (ECID), WLAN (also referred to as WiFi), or combinations thereof. In some of these techniques (e.g., A-GNSS, AFLT and OTDOA), pseudoranges or timing differences may be measured by UE102relative to three or more terrestrial transmitters fixed at known locations or relative to four or more SVs with accurately known orbital data, or combinations thereof, based at least in part, on pilot signals, navigation signals, positioning reference signals (PRS) or other positioning related signals transmitted by the transmitters or SVs and received at UE102. Here, LSs, such as E-SMLC110or H-SLP118, may be capable of providing positioning assistance data (AD) to UE102including, for example, information regarding signals to be measured by UE102(e.g., expected signal timing, signal coding, signal frequencies, signal Doppler), locations and/or identities of terrestrial transmitters and/or associated cell antennas, and/or signal, timing and orbital information for GNSS SVs to facilitate positioning techniques such as A-GNSS, AFLT, OTDOA, ECID and WLAN. The facilitation may include improving signal acquisition and measurement accuracy by UE102and/or, in some cases, enabling UE102to compute its estimated location based on the location measurements. For example, an LS may comprise an almanac (e.g., a Base Station Almanac (BSA)) which indicates the locations and identities of cellular transceivers and transmitters (e.g., eNBs104and106) and/or local transceivers and transmitters in a particular region or regions such as a venue, and may further contain information descriptive of signals transmitted by these transceivers and transmitters such as signal power, signal timing, signal bandwidth, signal coding and/or signal frequency.

In the case of ECID, a UE102may obtain measurements of signal strength (e.g., Received Signal Strength Indication (RSSI) or Reference Signal Received Power (RSRP)) for signals received from cellular transceivers (e.g., eNBs104,106) and/or local transceivers and/or may obtain a Signal to Noise ratio (S/N), a Reference Signal Received Quality (RSRQ), and/or a Round Trip signal propagation Time (RTT) between UE102and a cellular transceiver (e.g., eNB104or106) or a local transceiver. A UE102may transfer these measurements to an LS (e.g., E-SMLC110or H-SLP118) to determine a location for UE102, or in some implementations, UE102may use these measurements together with assistance data (e.g., terrestrial almanac data) received from an LS or from a cellular transceiver (e.g. eNB104) to determine a location for UE102using ECID.

In the case of OTDOA, UE102may measure a Reference Signal Time Difference (RSTD) between signals, such as a Positioning Reference Signal (PRS) and/or a Cell specific Reference Signal (CRS), received from nearby transceivers or base stations (e.g., eNBs104and106). An RSTD measurement may provide the time of arrival difference between signals (e.g., CRS or PRS) received at UE102from two different transceivers (e.g., an RSTD between signals received from eNB104and from eNB106). The UE102may return the measured RSTDs to an LS (e.g., E-SMLC110or H-SLP118) which may compute an estimated location for UE102based on the measured RSTDs and the known locations and known signal timing for the measured transceivers. In some implementations of OTDOA, the signals used for RSTD measurements (e.g., PRS or CRS signals) may be accurately synchronized by the transceivers or transmitters to a common universal time such as GPS time or coordinated universal time (UTC), e.g., using a GPS or other GNSS receiver at each transceiver or transmitter to accurately obtain the common universal time.

In the case of A-GNSS, a UE102may obtain measurements of Doppler, pseudorange, code phase and/or carrier phase for one more SVs160for one or more GNSSs. In the case of WLAN positioning, a UE102may obtain the identities of one or more visible WiFi APs and possibly measurements for beacon frames and/or other signals received from visible WiFi APs, such as measurements of RSSI and/or RTT. As described above for ECID and OTDOA, these measurements may be transferred to an LS (e.g. E-SMLC110or H-SLP118) to compute a location for UE102or UE102may compute the location itself based on AD (e.g. AD for SVs160or WLAN APs) received from an LS, cellular transceivers or from the transmitters themselves (e.g. from SVs16). In some implementations, hybrid combinations of two or more position methods may be used by an LS and UE102to obtain a location for UE102.

Position methods such as A-GNSS, OTDOA, AFLT, ECID and WLAN, as described above, may be referred to as downlink (DL) position methods because they are supported by UEs such as UE102based on measurements by the UE of downlink signals transmitted from terrestrial transmitters (e.g., eNBs104and106) and/or SPS SVs (e.g., SVs160). In contrast, with an uplink (UL) position method, an entity on the network side (e.g., eNB104or eNB106) may measure uplinks signals transmitted by a UE (e.g., UE102) in order to obtain a location estimate for the UE. The measurements for an UL position method may then be transferred to an LS (e.g., E-SMLC110) using the LPP Annex (LPPa) protocol defined by 3GPP in 3GPP TS 35.455 in order to enable the LS to determine a location of the UE.

An estimate of a location of a UE102may be referred to as a location, location estimate, location fix, fix, position, position estimate or position fix, and may be geodetic, thereby providing location coordinates for UE102(e.g., latitude and longitude) which may or may not include an altitude component (e.g., height above sea level, height above or depth below ground level, floor level or basement level). Alternatively, a location of UE102may be expressed as a civic location (e.g., as a postal address or the designation of some point or small area in a building such as a particular room or floor). A location of a UE102may also include an uncertainty and may then be expressed as an area or volume (defined either geodetically or in civic form) within which UE102is expected to be located with some given or default probability or confidence level (e.g., 67% or 95%). A location of a UE102may further be an absolute location (e.g., defined in terms of a latitude, longitude and possibly altitude and/or uncertainty) or may be a relative location comprising, for example, a distance and direction or relative X, Y (and Z) coordinates defined relative to some origin at a known absolute location. In the description contained herein, the use of the term location may comprise any of these variants unless indicated otherwise. Measurements (e.g., obtained by UE102or by another entity such as eNB104) that are used to determine (e.g., calculate) a location estimate for UE102may be referred to as measurements, location measurements, location related measurements, positioning measurements or position measurements and the act of determining a location for UE102may be referred to as positioning of UE102or locating UE102.

For downlink position methods and possibly for some uplink position methods, a UE102and a LS (e.g., E-SMLC110or H-SLP118) may need to exchange positioning protocol messages, such as messages for LPP, LPP/LPPe or some other positioning protocol. However, for a UE102with NB-IoT access, messages may need to be transmitted multiple times in an UL and/or DL direction to ensure error free reception when S/N and an associated coverage enhancement (CE) level (e.g. as with a CE level of 2) are poor. Combined with a higher message transmission delay caused by limited bandwidth (e.g. with an NB-IoT bandwidth of only 180 KHz), this may lead to very long message transfer times (e.g. of several seconds) which may limit both the number and size of positioning protocol messages which can be exchanged between a UE102and an LS (e.g. E-SMLC110or H-SLP118) during a location session. Because AD provided by the LS and/or Location Information (LI) provided by UE102(or, more generally, the downlink (DL) AD information provided by the LS and/or the uplink (UL) measurement and location related information provided by the UE) in a location session can comprise several hundred or even several thousand octets, devices may not be able to provide or enable a position fix in cases where a position of UE102is requested more frequently or with a lower delay requirement than a location is able to be determined in view of the transmission delays. In addition, the network bandwidth usage to obtain a location for a UE102with a poor NB-IoT coverage level, and UE102resources (e.g., UE102battery) needed to obtain the location, may need to be limited, leading to a need to limit the amount of AD and/or LI for positioning of UE102.

The network architecture100shown inFIG. 1may apply to UE102wireless access using LTE or NB-IoT to VPLMN E-UTRAN120and VPLMN EPC130. However, other similar network architectures may exist in which a UE102accesses other types of radio access network (RAN) and/or other types of core network. For example, when UE102uses an NR Radio Access Technology (RAT), UE102may access a Next Generation RAN (NG-RAN) and a 5G Core Network (5GCN) which may replace E-UTRAN120and EPC130, respectively, in network architecture100. In this case, some network elements for EPC130shown inFIG. 1may be different. For example, MME108may be replaced by an Access and Mobility Management Function (AMF) and E-SMLC110may be replaced by an LS supporting a CP location solution for NR wireless access such as a Location Management Function (LMF). In the description of the various techniques below, it may therefore be possible to substitute an AMF for MME108and an LMF for E-SMLC110in examples where UE102has NR RAT access rather than NB-IoT or LTE RAT access.

FIG. 2Ashows the structure of an exemplary LTE frame sequence for any cell that supports LTE with PRS positioning occasions according to aspects of the present disclosure. InFIG. 2A, time is represented on the X (horizontal) axis, while frequency is represented on the Y (vertical) axis. As shown inFIG. 2A, downlink and uplink LTE Radio Frames210are of 10 ms duration each. For downlink Frequency Division Duplex (FDD) mode, Radio Frames210are organized into ten subframes212of 1 millisecond (ms) duration each. Each subframe212comprises two slots214, each of 0.5 ms duration.

In the frequency domain, the available bandwidth may be divided into uniformly spaced orthogonal subcarriers216. For example, for a normal length cyclic prefix using 15 KHz spacing, subcarriers216may be grouped into a group of 12 subcarriers. Each grouping, which comprises 12 subcarriers216, inFIG. 2A, is termed a resource block and, in the example above, the number of subcarriers in the resource block may be written as NSCRB=12. For a given channel bandwidth, the number of available resource blocks on each channel222, which is also called the transmission bandwidth configuration222, is given by NRBDL222. For example, for a 3 MHz channel bandwidth in the above example, the number of available resource blocks on each channel222is given by NRBDL=15.

In some embodiments, a set of antennas corresponding to a set of cells, respectively, may transmit PRS signals. PRS signals are transmitted by a base station (e.g. eNB104) in special positioning subframes that are grouped into positioning occasions (also referred to as PRS positioning occasions and PRS occasions). For example, in LTE, a positioning occasion can comprise a number, denoted as NPRS, of between 1 and 160 consecutive positioning subframes and can occur periodically at intervals of 5, 10, 20, 40, 80, 160, 320, 640, or 1280 milliseconds. In the example shown inFIG. 2A, the number of consecutive positioning subframes218is 4 and may be written as NPRS=4. The positioning occasions recur with PRS Periodicity220. InFIG. 2A, PRS Periodicity220is denoted by TPRS. In some embodiments, TPRSmay be measured in terms of the number of subframes between the start of consecutive positioning occasions.

Within each positioning occasion, PRS may be transmitted with a constant power. PRS can also be transmitted with zero power (i.e., muted). Muting, which turns off a regularly scheduled PRS transmission, may be useful when PRS patterns between cells overlap. Muting aids signal acquisition by UE102. Muting may be viewed as the non-transmission of a PRS for a given positioning occasion in a particular cell. Muting patterns may be signaled to UE102using bit strings. For example, in a bit string signaling a muting pattern, if a bit at position j is set to “0”, then an MS may infer that the PRS is muted for the jthpositioning occasion.

To further improve hearability of PRS, positioning subframes may be low-interference subframes that are transmitted without user data channels. As a result, in ideally synchronized networks, PRSs may receive interference from other cell PRSs with the same PRS pattern index (i.e., with the same frequency shift), but not from data transmissions. The frequency shift, in LTE, for example, is defined as a function of the Physical Cell Identifier (PCI) resulting in an effective frequency re-use factor of 6.

The PRS configuration parameters such as the number of consecutive positioning subframes, periodicity, muting pattern, PRS code sequence, etc., may be configured by a network and may be signaled to UE102(e.g., by a server such as E-SMLC110) as part of the OTDOA assistance data. For example, LPP or LPPe messages exchanged between UE102and the server may be used to transfer location assistance data from the server to UE102including OTDOA assistance data. OTDOA assistance data may include reference cell information and neighbor cell information. The reference cell and neighbor cell information may each contain the PCIs of the cells as well as PRS configuration parameters for the cells.

The OTDOA assistance data may include “expected RSTD” parameters, which provide UE102with information about the approximate RSTD values UE102is expected to measure at its current location together with an uncertainty of the expected RSTD parameter. The expected RSTD together with the uncertainty defines then a search window for UE102where UE102is expected to measure the RSTD value. “Expected RSTDs” for cells included in the OTDOA assistance data neighbor cell information are usually provided relative to an OTDOA assistance data reference cell. OTDOA assistance data may also include PRS configuration information parameters, which allow UE102to determine approximately when a PRS positioning occasion occurs on signals received from various cells, and to determine the PRS sequence transmitted from various cells in order to measure a Time of Arrival (TOA) of a PRS at UE102. UE102may then determine an RSTD measurement for a reference cell and a neighbor cell from the difference between a TOA measurement for each cell.

FIG. 2Billustrates the relationship between the System Frame Number (SFN), the cell specific subframe offset (ΔPRS) and the PRS Periodicity220according to aspects of the present disclosure. Typically, the cell specific PRS subframe configuration is defined by a “PRS Configuration Index” IPRSincluded in the OTDOA assistance data. The cell specific subframe configuration period and the cell specific subframe offset for the transmission of positioning reference signals are defined based on the IPRS, in 3GPP TS 36.211 and as listed in Table 1 below.

A PRS configuration is defined with reference to the System Frame Number (SFN) of a cell that transmits PRS. PRS instances, for the first subframe of a PRS positioning occasion, satisfy
(10×nf+└ns/2┘−ΔPRS)modTPRS=0  eq. 1
where,

nfis the SFN with 0≤SFN≤1023,

nsis the slot number of the radio frame with 0≤ns≤19,

TPRSis the PRS period, and

As shown inFIG. 2B, the cell specific subframe offset ΔPRS252may be defined in terms of the number of subframes transmitted starting from System Frame Number 0, Slot Number 0250to the start of a PRS positioning occasion. InFIG. 2B, the number of consecutive positioning subframes218, NPRS=4.

In some embodiments, when UE102receives a PRS configuration index IPRSin the OTDOA assistance data, UE102may determine PRS periodicity TPRSand PRS subframe offset ΔPRSusing Table 1. Upon obtaining information about the frame and slot timing i.e., the SFN and slot number (nf, ns) for a cell, UE102may determine the frame and slot when a PRS is scheduled in the cell.

FIGS. 2A and 2Bdescribed support of PRS signals for LTE wireless access by a UE102(e.g. as defined in 3GPP TS 36.211). A PRS for NB-IoT wireless access by a UE102may be referred to as a narrowband positioning reference signal (NPRS) and may be supported and configured in a similar manner to a PRS as described inFIGS. 2A and 2Bwith the difference that an NPRS may comprise a single resource block with a bandwidth of 200 KHz (or 180 KHz of effective signaling bandwidth). In addition, an NPRS may use frequency hopping between consecutive subframes of the same NPRS positioning occasion and/or between consecutive NPRS positioning occasions. Alternatively, an eNB may transmit multiple NPRS signals, each using a different resource block (and thus a different carrier frequency), which may allow UE102to measure an NPRS for the same eNB using several different frequencies which may improve measurement accuracy in a similar manner to frequency hopping.

FIG. 3illustrates an exemplary process flow300for a system that supports CE level determination for NB-IoT access in accordance with various aspects of the present disclosure. The process flow300includes the UE102and eNB104from network architecture100. In some cases, the process flow300may be an example of aspects of random access procedures. For example, the process flow300may be employed after the UE102has acquired a primary synchronization signal (PSS) and a secondary synchronization signal (SSS) for NB-IoT or LTE access to eNB104.

Process flow300may start at stage305, where the eNB104may send, and the UE102may receive, a broadcast signal which may be periodically repeated. For example, the broadcast signal may comprise the transmission content of a narrowband physical broadcast channel (NPBCH) for NB-IoT access or a physical broadcast channel (PBCH) for LTE access. The broadcast signal may be transmitted by eNB104with a high level of coverage enhancement (e.g., CE level 3) which may comprise transmitting multiple identical samples (e.g. 64 samples) of the broadcast signal by eNB104, which may allow a UE102which has a high CE coverage level (e.g. CE level 2 or 3) to receive and decode the broadcast signal by receiving and combining multiple samples using RF coherent (or non-coherent) integration. In some cases, the broadcast signal includes a Master Information Block (MIB) which may comprise information essential for UE102access to eNB104, e.g. which is conveyed using the NPBCH or PBCH.

At stage310, the UE102may monitor the broadcast signal. In some examples, monitoring the broadcast signal may include test-decoding the broadcast signal at a test CE level (e.g., CE level 0) by UE102that is less than the CE level supported by the signal (e.g., CE level 3). That is, the UE102may attempt to decode the broadcast signal by receiving and combining a smaller number of samples, which may reduce the gain and S/N of the signal compared to decoding the signal only after all the samples have been received and combined. For example, if UE102attempts to decode the broadcast signal after only one sample has been received (which may correspond to a CE level of 0), the S/N of the signal may be around 15 dB less than when 32 samples have been received and combined. In some cases, the UE102may attempt to partially decode the signal. For example, the UE102may attempt to decode only a portion of the signal. Additionally, or alternatively, the UE102may attempt to decode the signal before the highest CE level has been attained. If the decode attempt is successful, the UE102may proceed to stage325and determine the operating CE level. For example, the UE102may select the test decode CE level to be the actual operating CE level of the UE102.

If the decode attempt at stage310is unsuccessful, the UE102may proceed to stage315and increase the test CE level (e.g., the test CE level may be incremented to CE level 1), which may correspond to receiving and combining more samples of the broadcast signal. Subsequently, at stage320, the UE102may monitor the broadcast signal according to the new test CE level (e.g., CE level 1). For instance, the UE102may wait until a gain of 5 dB is reached (e.g. corresponding to receiving and combining four times as many samples of the broadcast signal as at stage310) before attempting to decode the broadcast signal. If the decoding is unsuccessful, the UE102may continue to increase the test CE level for each subsequent test-decoding of the broadcast signal (e.g. by receiving and decoding additional samples of the broadcast signal) until a decoding is successful. Once a decoding is successful, the UE102may proceed to stage325and select the test CE level that resulted in the successful decoding as its operating CE level. Thus, the UE102may determine its CE level based on broadcast signal monitoring.

In certain scenarios, the UE102may verify the test CE level before assigning it as the operating CE level. For example, the UE102may receive subsequent broadcast signals and attempt to decode each broadcast signal using the test CE level. The UE102may continue to decode subsequent broadcast signals until the number of successful decoding attempts has satisfied a threshold. Once a threshold number of decoding attempts have been successful, the UE102may determine the operating CE level as equal to the test CE level. In some cases, determining the operating CE level may include communicating using the operating CE level. In this or other examples, determining the operating CE level may include sending an indication of the operating CE level to the eNB104.

At stage330, the UE102may select random access resources for communication with the eNB104. In one example, the random access resources may be physical random access channel (PRACH) resources (e.g. RF frequencies) for conveying a random access preamble. There may be a number of resources (e.g., NB-IoT resources) available for random access use; however, some resources may be associated with certain levels of coverage enhancement. Accordingly, the UE102may select resources (e.g. frequencies) for a random access procedure that correspond to the CE level selected at stage325. At stage335, the UE102may transmit, and the eNB104may receive, a random access channel (RACH) preamble conveyed by the resources selected at stage330. The UE102may apply the determined CE level to the transmission. The resources used to carry the RACH preamble may intrinsically indicate the CE level of the UE102as determined at stage325. Thus, the eNB104may determine the CE level of the UE102based on the resources (e.g. frequencies) used to convey the RACH preamble.

FIG. 4Aillustrates an example of a process flow400for a system that supports CE level determination in accordance with various aspects of the present disclosure. The process flow400includes the UE102and eNB104from network architecture100. The process flow400may be an example of a random access procedure, such as in a situation in which the UE102has acquired a PSS and SSS from eNB104.

At stage405, the eNB104may send, and the UE102may receive, a downlink signal. In some cases, the downlink signal may be a reference signal, such as a CRS or a Narrowband Reference Signal (NRS). At stage410, the UE102may measure the signal strength of the downlink signal to determine the path loss associated with the eNB104and the UE102. At stage415, the UE102may estimate the CE level based on the path loss. For example, the UE102may estimate the CE level to be high (e.g. CE level 2 or 3) when the estimated path loss is high and may estimate the CE level to be low (e.g. CE level 0 or 1) when the estimated path loss is low. At stage420, the eNB104may transmit, and the UE102may receive, a broadcast signal (e.g. a signal comprising a transmission of a PBCH or NPBCH). Proceeding to stage425, the UE102may monitor the broadcast signal. For example, the UE102may test-decode the broadcast signal once a number of identical samples of the broadcast signal have been received and combined by UE102(e.g. as described forFIG. 3) that provide a gain in broadcast signal S/N consistent with that needed to enable decoding for the estimated CE level. At stage430, if the test-decoding is successful, the UE102may confirm the estimated CE level. Accordingly, at stage435, the UE102may select RACH resources (e.g. an RF frequency) according to the confirmed CE level. At stage440, the UE102may transmit, and the eNB104may receive, a RACH preamble conveyed by the selected random access resources.

If the test-decoding at stage425is unsuccessful, the UE102may return to stage405. That is, the UE102may receive another broadcast signal (e.g. a CRS or NRS) and may measure the signal strength at stage410. In some scenarios, the UE102may obtain a number of consecutive signal strength measurements at stage410and may combine these in order to determine a more reliable path loss. After making the measurements at stage410, the UE102may proceed to stages415-430. Once the appropriate CE level has been confirmed (e.g., at stage430), the UE102may proceed to stage435and stage440.

In some aspects, if the test-decoding at stage425fails, the UE102may monitor the broadcast signal such as described with reference toFIG. 3. For example, instead of repeating stages405-415, the UE102may iteratively test-decode the broadcast signal using an increasing number of identical samples associated with increased CE levels (as described forFIG. 3) until a successful decoding is achieved. Thus, the UE102may utilize the estimated CE level obtained at stage415as an initial CE level for the recursive test-decoding process described with reference toFIG. 3.

FIG. 4Billustrates an exemplary correlation of a CE level of a UE102(e.g. as determined by UE102using the process ofFIG. 3orFIG. 4A) with a response time of the UE102when in communication with a server (e.g. E-SMLC110) according to aspects of the present disclosure.FIG. 4Billustrates a PRACH transmission by UE102to serving eNB104to request eNB104to provide a signaling connection to UE102to enable UE102to progress from an idle state into a connected state (e.g. which may be needed to allow UE102to respond to a paging request from eNB104or to return location measurements to an LS such E-SMLC110). Each PRACH transmission can comprise one or more transmission attempts and one or more repetitions of each transmission attempt, depending on the CE level of UE102, as described next.

As shown inFIG. 4B, at CE level 0, the UE102(not shown inFIG. 4B) may perform 3 transmission attempts410for an NB-IoT or enhanced machine type communication (eMTC) physical random access channel (PRACH) transmission to eNB104(not shown inFIG. 4B). Within each of the 3 attempts410, the UE102may perform no additional repetition (Reps) for the PRACH. The UE102may also operate at a low transmission power level.

At CE level 1, the UE102may perform 5 attempts420for the NB-IOT or eMTC PRACH transmission to eNB104. Within each of the 5 attempts420, the UE may perform 4 repetitions for PRACH. The UE102may also operate at a medium transmission power level.

At CE level 2, the UE102may perform 7 attempts430for the NB-IoT or eMTC PRACH transmission to eNB104. Within each of the 7 attempts430, the UE102may perform 16 repetitions for PRACH. The UE may operate at a high transmission power level.

At CE level 3, the UE102may perform 10 attempts440for the NB-IoT or eMTC PRACH requirement to eNB104. Within each of the 10 attempts440, the UE may perform 64 repetitions for PRACH. The transmission power level may be set to a maximum available level for the UE102.

As shown inFIG. 4B, as the CE level of the UE102increases, the duration for the UE102to send a PRACH transmission to eNB104also increases due to the increasing number of PRACH attempts and PRACH repetitions. The increased duration may increase the delay in a transition of UE102from an idle state to a connected state. A similar increase in delay may occur when UE102sends multiple repetitions of portions of an LPP message (e.g. containing RSTD measurements) to eNB104(e.g. to be forwarded to E-SMLC110) or receives multiple repetitions of portions of an LPP message from eNB104(e.g. containing AD from E-SMLC110to assist RSTD measurements). As for the PRACH example inFIG. 4B, the multiple attempts and repetitions may be associated with a CE level for UE102and may increase when the CE level for UE102is increased. The increased delay in PRACH access to the eNB104and in transferring LPP messages between UE102and eNB104may increase the duration of OTDOA positioning of UE102(and/or positioning of UE102using other position methods such as A-GNSS, ECID or WLAN), which may prevent a location estimate for UE102being obtained by E-SMLC110or may impair the accuracy of a location estimate by reducing the number of RSTD measurements (or the number of other measurements such as A-GNSS, ECID or WLAN measurements) which UE102can obtain and return to E-SMLC110within a limited response time requirement. Note that as described above in association withFIG. 4AandFIG. 4B, different CE levels of the UE102can produce different response delays in UE102communications with the eNB104and an LS (e.g. E-SMLC110), e.g. because of the different number of PRACH attempts and PRACH repetitions (or LPP message attempts and repetitions) performed for the different CE levels of the UE102. In some implementations, such difference in response delays in communications between the UE102and the eNB104or an LS may be used to determine the CE level of the UE102, as described later herein.

According to aspects of the present disclosure, a message (e.g. an LPP message) can be used to enable a current Coverage Enhancement (CE) mode/level for a UE102(e.g. which directly maps to downlink and uplink repetition attempts as described forFIGS. 3-4B) to be provided by a UE102to the E-SMLC110. The E-SMLC110may use the received CE level to estimate the delay in sending and receiving LPP messages to and from the UE102for different sizes of LPP message. The E-SMLC110may then determine reduced LPP message sizes that will enable a location for the UE102to be obtained within a maximum required overall response time. Alternatively, the E-SMLC110may determine an increased response time for obtaining a location of UE102and may send the increased response time (or a portion of the increased response time) to UE102in an LPP message requesting location measurements (e.g. RSTD measurements) or a location estimate from UE102. In order to enable smaller LPP message sizes, the E-SMLC110may, for example, reduce the number of measurements (e.g. RSTD measurements) requested from UE102and/or may provide a smaller amount of AD to UE102to assist in obtaining location measurements.

According to aspects of the present disclosure, providing an internal delay for each RF receive path and other receive path details by a UE102to a location server (e.g. E-SMLC110) may improve the accuracy of OTDOA positioning. In supporting carrier aggregation, mobile devices (e.g. UE102) may typically have four or more RF receive paths, and one of them may be selected to obtain and measure a neighbor cell PRS or NPRS (e.g. via a measurement gap, idle receive path etc.). The capability for UE102to provide the internal RF receive delay of UE102to the E-SMLC120may be extended to each RF receive path for UE102as the internal delay can be dependent on each RF receive path due to different components being used in the RF front-end of UE102. Hence, it may be useful for UE102to provide details of the RF receive path information to E-SMLC110when different PRS or NPRS signals are measured by UE102, in order to achieve an accurate location determination.

FIG. 5Aillustrates exemplary implementations of RF signal paths through a front-end of a UE102according to aspects of the present disclosure. In the example shown inFIG. 5A, to support carrier aggregation (e.g. for LTE), a transceiver for UE102may include a plurality of antennas (502a-502d), one or more power amplifiers and/or antenna switch modules (504a-504f), one or more multi-mode radio frequency transceivers (506a-506b), one or more diplexers (508a-508b) coupled between the corresponding antennas (502a-502d) and the power amplifier and/or antenna switch modules (504a-504f), and a modem510.

In some implementations, a power amplifier and/or antenna switch, such as504a, may be a high-band power amplifier module including duplexer. In some other implementations, a power amplifier and/or antenna switch, such as504b, may include a mid-band and a low-band power amplifier and antenna switch modules. In yet some other implementations, a power amplifier and/or antenna switch, such as504c, may include a high-band, a mid-band, and a low-band antenna switches. In yet some other implementations, a power amplifier and/or antenna switch, such as504d, may be configured to support certain specific bandwidth such as a bandwidth for a LTE band B1 and/or B39. In yet some other implementations, a power amplifier and/or antenna switch, such as504e, may be configured to support a third party power amplifier for GSM signals.

In some implementations, a multi-mode radio frequency transceiver, such as506a, may include one or more of the following: 1) high-band transceiver511; 2) mid-band transceiver512; 3) low-band transceiver513; 4) high-band, mid-band, or low-band receiver514; 5) a mid-band receiver,515; and 6) a low-band receiver516. In some other implementations, a multi-mode radio frequency transceiver, such as506b, may include one or more of the following: 1) a band B1 receiver517; 2) a band B1 or B39 transceiver518; 3) a GSM transceiver519; and 4) a BC0 transceiver520.

According to aspects of the present disclosure, a UE102may be implemented with various capabilities to support carrier aggregation. In supporting the various possible signals received from different carriers, the RF path of a received signal in UE102can vary as it may depend on the type of signal being received. As a result, the delay through the different components in the received path in UE102can change, which can in turn affect the accuracy in measurements of RSTD for OTDOA positioning. For example, as shown inFIG. 5A, one exemplary signal path (shown by the dashed line501) may be through antenna502a, diplexer508a, power amplifier and/or antenna switch504b, multi-mode radio frequency transceiver506a, and modem510. Another exemplary signal path (shown by the dotted line503) may be through antenna502d, power amplifier and/or antenna switch504c, multi-mode radio frequency transceiver506a, and modem510. Since the path of a received signal can change, more accurate positioning may be achieved when information for the internal RF delay of UE102is provided to the server (e.g. E-SMLC110) for positioning applications.

FIG. 5Billustrates other exemplary implementations of signal paths through a front-end of a UE102according to aspects of the present disclosure. The components of the UE102are the same as the components shown inFIG. 5A, and the descriptions of such components are not repeated here. In the exemplary implementations shown inFIG. 5B, one exemplary signal path (shown by the line521) may be through antenna502c, power amplifier and/or antenna switch504a, multi-mode radio frequency transceiver506b, and modem510. Another exemplary signal path (shown by the line523) may be through antenna502b, diplexer508b, power amplifier and/or antenna switch504d, multi-mode radio frequency transceiver506b, and modem510. The path of a received signal can vary as it depends on the type of signal being received. As a result, the delay through the different components in the receive path can change, which can in turn affect the accuracy of RSTD measurements by UE102for OTDOA positioning. Thus, a more accurate positioning may be achieved when information for the internal RF delays of UE102is provided by UE102to the server (e.g. E-SMLC110) for positioning applications.

FIG. 6illustrates an exemplary signaling flow600of a procedure that supports OTDOA position determination according to aspects of the present disclosure. While signaling flow600is shown as occurring between UE102and E-SMLC110in network architecture100, E-SMLC110could be replaced by another location server such as H-SLP118or an LMF in some embodiments. Signaling flow600may be instigated by the sending of a location request for UE102to E-SMLC110by some other entity (e.g. MME108) which is not shown inFIG. 6.

At stage601, E-SMLC110may transmit to UE102a Request Capabilities message (e.g. an LPP Request Capabilities message) to request the positioning capabilities of UE102such as the OTDOA positioning capabilities of UE102. In response, at stage602, the UE102sends a Provide Capabilities message (e.g. an LPP Provide Capabilities message) to the E-SMLC110to provide the positioning capabilities of UE102. If OTDOA positioning capabilities were requested in stage601, the Provide Capabilities message may include the OTDOA positioning capabilities of UE102such as the OTDOA modes supported by UE102(e.g. UE assisted OTDOA and/or UE based OTDOA), supported frequency bands, and support for inter-frequency RSTD measurements.

According to aspects of the present disclosure, the capabilities of the UE102sent at stage602may include information for a coverage enhancement level of UE102. The information for the coverage enhancement (CE) level may include at least one of a transmission power level for UE102, a number of repetitions of a message broadcast by a serving base station for UE102(e.g. eNB104) and received and successfully decoded by UE102(e.g. as described forFIG. 3andFIG. 4A), a number of repetitions of a message sent by UE102to a serving base station (e.g. eNB104) (e.g. as described forFIG. 4B) where the message is acknowledged by the serving base station, or some combination thereof.

According to other aspects of the present disclosure, the capabilities of the UE102sent at stage602may include information for at least one internal signaling path of UE102, such as an internal delay of the at least one internal signaling path. For example, UE102may determine the internal delay of the at least one internal signaling path based on at least one of a type of antenna, a type of transceiver, and/or a power amplifier or an antenna switch used by the at least one internal signaling path, as illustrated inFIGS. 5A and 5B.

At stage603, the E-SMLC110may send a Provide Assistance Data message (e.g. an LPP Provide Assistance Data message) to the UE102with OTDOA assistance data. The OTDOA assistance data may include assistance data (AD) for a reference cell and assistance data for a number of neighbor cells. For example, the assistance data may include PRS configuration parameters defining PRS signals (or NPRS signals) transmitted by the reference cell and each neighbor cell (e.g. as described forFIGS. 2A and 2B). As described previously, E-SMLC110may provide a smaller amount of AD to UE102at stage603(e.g. may provide AD for fewer neighbor cells) if UE102indicates a higher CE level (e.g. CE level 2 or 3) at stage602in order to reduce the overall response time for locating UE102. Conversely UE102may provide a larger amount of AD to UE102at stage603(e.g. may provide AD for a greater number of neighbor cells) if UE102indicates a lower CE level (e.g. CE level 0 or 1) at stage602.

At stage604, the E-SMLC110sends a Request Location Information message (e.g. an LPP Request Location Information message) to the UE102to request RSTD measurements for OTDOA positioning. This message may include information elements such as the location information type required (e.g. indicating RSTD measurements or a location estimate), a desired accuracy of a location estimate, and a response time interval (also referred to as a reporting time interval). As described previously, E-SMLC110may request a smaller number of location measurements from UE102at stage604(e.g. may request RSTD measurements for a smaller number of neighbor cells), may request a lower accuracy and/or may provide a higher response time interval if UE102indicates a higher CE level (e.g. CE level 2 or 3) at stage602in order to reduce the overall response time for locating UE102. Conversely E-SMLC110may request a larger number of location measurements from UE102at stage604(e.g. may request RSTD measurements for more neighbor cells), may request a higher accuracy and/or may provide a smaller response time interval if UE102indicates a lower CE level (e.g. CE level 0 or 1) at stage602

At stage605, the UE102obtains the RSTD measurements using the provided assistance data. For example, UE102may use assistance data comprising PRS configuration parameters to help acquire and measure RSTDs for OTDOA reference and neighbor cells as described in association withFIGS. 2A and 2B.

At stage606, and at or before the response time interval has expired, the UE102sends one or more RSTD measurements for each of for one or more neighbor cells in a Provide Location Information message (e.g. an LPP Provide Location Information message) to the E-SMLC110.

At stage607, the E-SMLC110uses the RSTD measurements provided by the UE102at stage606to determine the location of UE102. For example, the E-SMLC110may use the known locations of the antennas for the reference and neighbor cells measured by the UE102at stage605as well as the measurement information received in stage606to determine the location.

In one aspect of signaling flow600, denoted herein as aspect A1, UE102may determine a first response delay between a time of receiving the request capabilities message sent at stage601and a time of sending the provide capabilities message at stage602. UE102may then include the first response delay in the provide capabilities message sent at stage602, e.g. as part of information for the coverage enhancement level for UE102. Since the provide capabilities message is not yet transmitted when UE102includes the first response delay in this message, UE102may determine the first response delay at the time the first response delay is included in the provide capabilities message or may estimate an additional delay for starting to transmit the provide capabilities message and include this additional delay as part of the first response delay. E-SMLC110may then measure a second response delay, where the second response delay comprises a difference between a time of sending the request capabilities message at stage601and a time of receiving the provide capabilities message sent at stage602. E-SMLC110may then determine a round trip propagation time, RTTdet, as equal to the second response delay less the first response delay. E-SMLC110may then determine or estimate a CE level for UE102based on RTTdet and other information such as a known transmission bandwidth, BW, for the wireless access used by UE102(e.g. such as 180 KHz in the case of UE102with NB-IoT wireless access). For example, E-SMLC110can calculate a minimum RTT, RTTmin, as equal to (M1+M2)/BW, where M1 is the overall size (e.g. in bits) of the request capabilities message sent at stage601and M2 is the overall size (e.g. in bits) of the provide capabilities message sent at stage602(allowing for inclusion of other lower level protocol headers and possible use of segmentation over the wireless access for UE102). If RTTdet is much higher than RTTmin (e.g. 20 times higher or more), E-SMLC110may determine a high CE level for UE102(e.g. CE level 2 or 3) whereas if RTTdet is higher than RTTmin by a smaller multiple, E-SMLC110may determine a smaller CE level (e.g. CE level 0 or 1). The exact ratio of RTTdet to RTTmin for different values of CE level may be refined by testing by the operator of E-SMLC110to determine ratios that are associated with known CE levels of tested UEs.

FIG. 7illustrates an exemplary block diagram of a device that may be configured to perform enhanced device capabilities exchange in mobile positioning applications according to aspects of the present disclosure. A device that may be configured to perform enhanced device capabilities exchange in mobile positioning applications may comprise one or more features of mobile device700shown inFIG. 7. Mobile device700may correspond to UE102forFIGS. 1, 3, 4A, 4B, 5A, 5B and 6. In certain embodiments, mobile device700may include a wireless transceiver721that is capable of transmitting and receiving wireless signals723via wireless antenna722over a wireless communication network. Wireless transceiver721may be connected to bus701by a wireless transceiver bus interface720. Wireless transceiver bus interface720may, in some embodiments be at least partially integrated with wireless transceiver721. Some embodiments may include multiple wireless transceivers similar to wireless transceiver721and multiple wireless antennas similar to wireless antenna722to enable transmitting and/or receiving signals according to a corresponding multiple wireless communication standards such as, for example, versions of Institute of Electrical and Electronics Engineers (IEEE) Std. 802.11, code-division multiple access (CDMA), wideband CDMA (WCDMA), LTE, universal mobile telecommunications service (UMTS), GSM, AMPS, ZigBee and Bluetooth®, etc.

Mobile device700may also comprise a Global Positioning System (GPS) receiver755capable of receiving and acquiring GPS signals759via GPS antenna758(which may be combined with antenna722). GPS is one example of a GNSS, and it is understood that other satellite positioning systems may also be used. GPS receiver755may also process, in whole or in part, acquired GPS signals759for estimating a location of mobile device700. In some embodiments, processor(s)711(which can include one or more processors executing instructions saved in memory), memory740, digital signal processor(s) (DSP(s))712and/or specialized processors (not shown) may also be utilized to process acquired GPS signals, in whole or in part, and/or calculate an estimated location of mobile device700, in conjunction with GPS receiver755. Storage of GPS or other signals may be performed in memory740or registers (not shown).

Also shown inFIG. 7, mobile device700may comprise digital signal processor(s) (DSP(s))712connected to the bus701, processor(s)711connected to the bus701and memory740. A bus interface (not shown inFIG. 7) may be integrated with the DSP(s)712, processor(s)711and memory740or may be separate. According to aspects of the present disclosure, processor(s)711and/or DSP(s)712may act as a controller of one or more components within the mobile device700. In various embodiments, functions may be performed in response to execution of one or more machine-readable instructions stored in memory740such as on a computer-readable storage medium, such as RAM, ROM, FLASH, or disc drive, just to name a few examples. The one or more instructions may be executable by processor(s)711, specialized processors, or DSP(s)712. Memory740may comprise a non-transitory processor-readable memory and/or a computer-readable memory that stores software code (programming code, instructions, etc.) that are executable by processor(s)711and/or DSP(s)712to perform functions described herein. In a particular implementation, wireless transceiver721may communicate with processor(s)711and/or DSP(s)712through bus701to enable mobile device700to be configured as a wireless station. Processor(s)711and/or DSP(s)712may execute instructions to execute one or more aspects of processes/methods discussed in connection withFIG. 1throughFIG. 6andFIG. 8throughFIG. 10, particularlyFIGS. 3, 4A, 6, 8, 9 and 10.

Also shown inFIG. 7, a user interface735may comprise any one of several devices such as, for example, a speaker, microphone, display device, vibration device, keyboard, touch screen, etc. A user interface signal provided to a user may be one or more outputs provided by any of the speaker, microphone, display device, vibration device, keyboard, touch screen, etc. In a particular implementation, user interface735may enable a user to interact with one or more applications hosted on mobile device700. For example, devices of user interface735may store analog or digital signals on memory740to be further processed by DSP(s)712or processor711in response to action from a user. Similarly, applications hosted on mobile device700may store analog or digital signals on memory740to present an output signal to a user. In another implementation, mobile device700may optionally include a dedicated audio input/output (I/O) device770comprising, for example, a dedicated speaker, microphone, digital to analog circuitry, analog to digital circuitry, amplifiers and/or gain control. In another implementation, mobile device700may comprise touch sensors762responsive to touching or pressure on a keyboard or touch screen device.

Mobile device700may also comprise a dedicated camera device764for capturing still or moving imagery. Dedicated camera device764may comprise, for example an imaging sensor (e.g., charge coupled device or complementary metal-oxide-semiconductor imager), lens, analog to digital circuitry, frame buffers, etc. In one implementation, additional processing, conditioning, encoding or compression of signals representing captured images may be performed at processor711or DSP(s)712. Alternatively, a dedicated video processor768may perform conditioning, encoding, compression or manipulation of signals representing captured images. Additionally, dedicated video processor768may decode/decompress stored image data for presentation on a display device (not shown) on mobile device700.

Mobile device700may also comprise sensors760coupled to bus701which may include, for example, inertial sensors and environment sensors. Inertial sensors of sensors760may comprise, for example accelerometers (e.g., collectively responding to acceleration of mobile device700in three dimensions), one or more gyroscopes or one or more magnetometers (e.g., to support one or more compass applications). Environment sensors of mobile device700may comprise, for example, temperature sensors, barometric pressure sensors, ambient light sensors, and camera imagers, microphones, just to name few examples. Sensors760may generate analog or digital signals that may be stored in memory740and processed by DPS(s) or processor711in support of one or more applications such as, for example, applications directed to positioning or navigation operations.

In a particular implementation, mobile device700may comprise a dedicated modem processor766capable of performing baseband processing of signals received and down-converted at wireless transceiver721or GPS receiver755. Similarly, dedicated modem processor766may perform baseband processing of signals to be up-converted for transmission by wireless transceiver721. In alternative implementations, instead of having a dedicated modem processor, baseband processing may be performed by a processor or DSP (e.g., processor711or DSP(s)712).

FIG. 8illustrates an exemplary method of positioning a mobile device (e.g. the UE102), performed generally at the mobile device, according to aspects of the present disclosure. As shown inFIG. 8, in block802, the method receives, by a transceiver of the mobile device, a request capabilities message from a server (e.g. as at stage601inFIG. 6). The server may be an E-SMLC (e.g. E-SMLC110), an SLP (e.g. H-SLP118) or an LMF. In block804, the method determines, by a processor of the mobile device, one or more capabilities of the mobile device, where the one or more capabilities of the mobile device include at least one of information for at least one internal signaling path of the mobile device or information for a coverage enhancement level of the mobile device. In block806, the method sends, by the transceiver, a first response message to the server, where the first response message includes the one or more capabilities of the mobile device (e.g. as at stage602inFIG. 6). In block808, the method receives, by the transceiver, a request for location measurements from the server based at least in part on the one or more capabilities of the mobile device (e.g. as at stage604inFIG. 6). In block810, the method obtains, by the transceiver and the processor, the location measurements (e.g. as at stage605inFIG. 6). In block812, the method sends, by the transceiver, a second response message to the server, where the second response message comprises the location measurements (e.g. as at stage606inFIG. 6). According to aspects of the present disclosure, the one or more capabilities of the mobile device include the information for the coverage enhancement level, where the request for location measurements is further based at least in part on the information for the coverage enhancement level (e.g. as described previously for stage604inFIG. 6).

In an aspect, the information for the at least one internal signaling path comprises an internal delay of the at least one internal signaling path. In this aspect, the method may further include determining, by the processor, the internal delay of the at least one internal signaling path based on at least one of a type of antenna, a transceiver, a power amplifier or an antenna switch used by the at least one internal signaling path (e.g. as described previously for stage602ofFIG. 6).

In an aspect, and as described previously forFIGS. 3, 4A and 4B, the information for the coverage enhancement level determined at block804may comprise at least one of a transmission power level for the mobile device, a number of repetitions of a message broadcast by a serving base station and received and successfully decoded by the mobile device, a number of repetitions of a message sent by the mobile device to the serving base station where the message is acknowledged by the serving base station, or some combination thereof.

In some implementations, the method may further include receiving, by the transceiver, assistance data from the server based at least in part on the one or more capabilities of the mobile device (e.g. as at stage603inFIG. 6), and obtaining, by the transceiver and the processor, the location measurements at block810, based at least in part on the assistance data (e.g. as described for stage605inFIG. 6).

According to aspects of the present disclosure, the location measurements may comprise measurements of a reference signal time difference (RSTD) for Observed Time Difference of Arrival (OTDOA) positioning. The mobile device may communicate with the server using Narrow Band Internet of Things (NB-IoT) wireless access.

FIG. 9illustrates an exemplary method of determining a coverage enhancement level of a mobile device (e.g. UE102), generally performed at the mobile device, according to aspects of the present disclosure. The method inFIG. 9may be combined with the method inFIG. 8(e.g. may extend the method inFIG. 8). As shown inFIG. 9, in block904, the method determines a first response delay between a time of receiving a request capabilities message from a server (e.g. the request capabilities message received at block802) and a time of sending a first response message to the server (e.g. the first response message sent at block806), where the information for the coverage enhancement level comprises the first response delay. The method performed in block904may additionally or optionally include the approach shown in block906. In block906, the server determines a coverage enhancement level for the mobile device based on a difference between the first response delay and a second response delay, where the server measures the second response delay, where the second response delay comprises a difference between a time of sending the request capabilities message at the server and a time of receiving the first response message at the server. Blocks904and906may correspond to aspect A1 described previously forFIG. 6.

FIG. 10Aillustrates an exemplary implementation of a method of determining information for a coverage enhancement level of a mobile device (e.g. UE102), generally performed at the mobile device, according to aspects of the present disclosure. The method inFIG. 10Amay be combined with the method inFIG. 8(e.g. may extend the method inFIG. 8). In the example shown inFIG. 10A, in block1002, the method receives first repetitions of a signal, where the signal is broadcast by a serving base station, and where the first repetitions are based on a first coverage enhancement level. In block1004, the method determines whether the first repetitions of the signal are successfully decoded. In block1006, the method includes the first coverage enhancement level in information for the coverage enhancement level (e.g. as at blocks804and806for the method inFIG. 8) when the first repetitions of the signal are successfully decoded. Blocks1002,1004and1006may correspond to parts of procedure300and/or procedure400as described in association withFIG. 3andFIG. 4A.

According to aspects of the present disclosure, the method performed inFIG. 10Amay additionally or optionally include the method performed inFIG. 10B. As shown inFIG. 10B, in block1012, the method receives second repetitions of the signal in response to the first repetitions of the signal not being successfully decoded at block1004, where the second repetitions are based on a second coverage enhancement level, and where the second repetitions include the first repetitions. In block1014, the method determines whether the second repetitions of the signal are successfully decoded. In block1016, the method includes the second coverage enhancement level in the information for the coverage enhancement level when the second repetitions of the signal are successfully decoded. Blocks1012,1014and1016may correspond to parts of procedure300and/or procedure400as described in association withFIG. 3andFIG. 4A.

FIG. 11Aillustrates an exemplary apparatus for positioning of a mobile device (e.g. a UE102) using enhanced exchange of capabilities according to aspects of the present disclosure. Apparatus1100may correspond to or represent any of E-SMLC110, H-SLP118or an LMF. In the example shown inFIG. 11A, apparatus1100may include one or more processors1102, network interface1104, database1106, positioning engine1108, memory1110, and user interface1112. The one or more processors1102can be configured to control operations of the apparatus1100. The network interface1104can be configured to communicate with a network (as described in association withFIG. 1) and with servers, computers, and/or mobile devices on the network or accessible via the network using one or more transceivers (transmitters and receivers) that may be part of network interface1104. Database1106can be configured to store positioning assistance data, sensor measurements, user interface inputs, positioning estimations, images, encoding and decoding information and other information related to support of one or more positioning protocols and/or one or more position methods. The one or more processors1102and/or the positioning engine1108can be configured to implement methods to support and communicate using one or more positioning protocols. For example, working with the processor(s)1102, the positioning engine1108can be configured to implement positioning protocols described in association withFIG. 1andFIG. 6. In some implementations, positioning engine1108may include dedicated hardware whereas in other implementations positioning engine1108may be a process, program, part of a process or program or other software or firmware running on processor(s)1102and possibly running according to code stored in memory1110.

Memory1110can be configured to store program codes, instructions, and data for the apparatus1100—e.g. data to support positioning protocols and/or position methods according to the exemplary methods described here in association withFIG. 1,FIG. 3,FIGS. 4A-4BandFIG. 6. User interface1112may be configured to enable interactions between apparatus1100and a user. According to aspects of the present disclosure, the apparatus1100may be implemented as a part of a server. In that implementation, the positioning protocols and/or position methods may be used by the server and/or may be communicated to mobile devices (e.g. UE102) via the network interface1104. These implementations or any combinations thereof are within the scope of the present disclosure.

FIG. 11Billustrates an exemplary implementation of positioning of a mobile device (e.g. the UE102), generally performed by a server, using an enhanced exchange of capabilities of the mobile device according to aspects of the present disclosure. The exemplary implementation inFIG. 11Bmay be performed by an E-SMLC (e.g. E-SMLC110), an SLP (e.g. H-SLP118), an LMF, or the apparatus1100. As shown inFIG. 11B, in block1122, the method sends a request capabilities message, by a transceiver of the server, to a mobile device (e.g. as at stage601inFIG. 6), where the mobile device determines one or more capabilities of the mobile device, and where the one or more capabilities of the mobile device include at least one of information for at least one internal signaling path of the mobile device or information for a coverage enhancement level of the mobile device. In block1124, the method receives a first response message, by the transceiver of the server, from the mobile device, where the first response message includes the one or more capabilities of the mobile device (e.g. as at stage602inFIG. 6). In block1126, the method determines, by a processor of the server, positioning assistance data based at least in part on the one or more capabilities of the mobile device and provides the positioning assistance data to the mobile device (e.g. as at stage603inFIG. 6). In block1128, the method sends, by the transceiver of the server, a request for location measurements to the mobile device (e.g. as at stage604inFIG. 6). In block1130, the method receives, by the transceiver of the server, a second response message from the mobile device, where the second response message comprises location measurements obtained by the mobile device (e.g. as at stage606inFIG. 6). In block1132, the method determines, by the processor of the server, a location of the mobile device using the location measurements obtained by the mobile device (e.g. as at stage607inFIG. 6).

According to aspects of the present disclosure, the one or more capabilities of the mobile device may include the information for the coverage enhancement level, where the request for location measurements is further based at least in part on the information for the coverage enhancement level. The information for the at least one internal signaling path may comprises an internal delay of the at least one internal signaling path in the mobile device. The information for the coverage enhancement level may include at least one of a transmission power level for the mobile device, a number of repetitions of a message broadcast by a serving base station and received and successfully decoded by the mobile device, a number of repetitions of a message sent by the mobile device to the serving base station where the message is acknowledged by the serving base station, or some combination thereof. The location measurements may include measurements of a reference signal time difference (RSTD) for Observed Time Difference of Arrival (OTDOA) positioning. The server may communicate with the mobile device using Narrow Band Internet of Things (NB-IoT) wireless access for the mobile device.

In some implementations, the mobile device may further configured to determine the internal delay of the at least one internal signaling path based on at least one of a type of antenna, a transceiver, a power amplifier or an antenna switch used by the at least one internal signaling path of the mobile device.

In some implementations and as described for aspect A1 forFIG. 6, the mobile device may further be configured to determine a first response delay between a time of receiving the request capabilities message and a time of sending the first response message, where the information for the coverage enhancement level comprises the first response delay. The server may further be configured to determine a coverage enhancement level for the mobile device based on a difference between the first response delay and a second response delay, where the server measures the second response delay, and where the second response delay comprises a difference between a time of sending the request capabilities message at the server and a time of receiving the first response message at the server.

According to aspects of the present disclosure and as described forFIG. 3andFIG. 4A, determining the information for the coverage enhancement level by the mobile device may include receiving by the mobile device first repetitions of a signal, the signal broadcast by a serving base station, where the first repetitions are based on a first coverage enhancement level, determining whether the first repetitions of the signal are successfully decoded, and including the first coverage enhancement level in the information for the coverage enhancement level when the first repetitions of the signal are successfully decoded.

Determining the information for the coverage enhancement level by the mobile device may further include in response to the first repetitions of the signal not being successfully decoded by the mobile device, receiving second repetitions of the signal, the second repetitions based on a second coverage enhancement level, the second repetitions including the first repetitions, determining whether the second repetitions of the signal are successfully decoded, and including the second coverage enhancement level in the information for the coverage enhancement level when the second repetitions of the signal are successfully decoded by the mobile device.

The server may further be configured to send assistance data to the mobile device based at least in part on the one or more capabilities of the mobile device, where the mobile device then obtains the location measurements based at least in part on the assistance data.

Note thatFIG. 1throughFIGS. 11A-11Band their corresponding descriptions provide, or make use of, means at a mobile device for receiving a request capabilities message from a server; means for determining one or more capabilities of the mobile device; means for sending a first response message to the server; means for receiving a request for location measurements from the server based at least in part on the one or more capabilities of the mobile device; means for obtaining the location measurements; means for sending a second response message to the server; means for determining a delay of an internal signal path; means for determining a coverage enhancement level of the mobile device; means for receiving a first signal; means for determining whether the first signal is successfully decoded using a first coverage enhancement level; means for communicating using the first coverage enhancement level in response to the first signal being successfully decoded; means for receiving a second signal in response to the first signal not being successfully decoded; means for determining whether the second signal is successfully decoded using a second coverage enhancement level; means for communicating using the second coverage enhancement level in response to the second signal being successfully decoded; and means for repeating the above process with a subsequent signal and a subsequent coverage enhancement level until the subsequent signal is successfully decoded using the subsequent coverage enhancement level.

The methodologies described herein may be implemented by various means depending upon applications according to particular examples. For example, such methodologies may be implemented in hardware, firmware, and software. In a hardware implementation, for example, a processing unit may be implemented within one or more application specific integrated circuits (ASICs), DSPs, digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, micro-controllers, microprocessors, electronic devices, other devices units designed to perform the functions described herein, or combinations thereof.

Wireless communication techniques described herein may be in connection with various wireless communications networks such as a wireless wide area network (WWAN), a wireless local area network (WLAN), a wireless personal area network (WPAN), and so on. The term “network” and “system” may be used interchangeably herein. A WWAN may be a CDMA network, a Time Division Multiple Access (TDMA) network, a Frequency Division Multiple Access (FDMA) network, an Orthogonal FDMA (OFDMA) network, a Single-Carrier FDMA (SC-FDMA) network, or any combination of the above networks, and so on. A CDMA network may implement one or more RATs such as cdma2000, Wideband CDMA (W-CDMA), to name just a few radio technologies. Here, cdma2000 may include technologies implemented according to IS-95, IS-2000, and IS-856 standards. A TDMA network may implement GSM, Digital Advanced Mobile Phone System (“D-AMPS”), or some other RAT. GSM and W-CDMA are described in documents from 3GPP. Cdma2000 is described in documents from 3GPP2. 3GPP and 3GPP2 documents are publicly available. 4G LTE and 5G NR communications networks may also be implemented in accordance with claimed subject matter, in an aspect. A WLAN may comprise an IEEE 802.11x network, and a WPAN may comprise a Bluetooth® network, an IEEE 802.15x, for example. Wireless communication implementations described herein may also be used in connection with any combination of WWAN, WLAN or WPAN.

In another aspect, as previously mentioned, a wireless transmitter or access point may comprise a femtocell, utilized to extend cellular telephone service into a business or home. In such an implementation, one or more mobile devices may communicate with a femtocell via a CDMA cellular communication protocol, for example, and the femtocell may provide the mobile device access to a larger cellular telecommunication network by way of another broadband network such as the Internet.

Techniques described herein may be used with a GNSS that includes any one of several GNSS and/or combinations of GNSS. Furthermore, such techniques may be used with positioning systems that utilize terrestrial transmitters acting as “pseudolites”, or a combination of space vehicles (SVs) and such terrestrial transmitters. Terrestrial transmitters may, for example, include ground-based transmitters that broadcast a pseudorandom noise (PN) code or other ranging code (e.g., similar to a GPS or CDMA cellular signal). Such a transmitter may be assigned a unique PN code so as to permit identification by a remote receiver. Terrestrial transmitters may be useful, for example, to augment a GNSS in situations where GNSS signals from an orbiting SV might be unavailable, such as in tunnels, mines, buildings, urban canyons or other enclosed areas. Another implementation of pseudolites is known as radio-beacons. The term “SV”, as used herein, is intended to include terrestrial transmitters acting as pseudolites, equivalents of pseudolites, and possibly others. The terms “GNSS signals” and/or “SV signals”, as used herein, is intended to include GNSS-like signals from terrestrial transmitters, including terrestrial transmitters acting as pseudolites or equivalents of pseudolites.

The terms, “and,” and “or” as used herein may include a variety of meanings that will depend at least in part upon the context in which it is used. Typically, “or” if used to associate a list, such as A, B or C, is intended to mean A, B, and C, here used in the inclusive sense, as well as A, B or C, here used in the exclusive sense. Reference throughout this specification to “one example” or “an example” means that a particular feature, structure, or characteristic described in connection with the example is included in at least one example of claimed subject matter. Thus, the appearances of the phrase “in one example” or “an example” in various places throughout this specification are not necessarily all referring to the same example. Furthermore, the particular features, structures, or characteristics may be combined in one or more examples. Examples described herein may include machines, devices, engines, or apparatuses that operate using digital signals. Such signals may comprise electronic signals, optical signals, electromagnetic signals, or any form of energy that provides information between locations.