HK1167184A - Method and apparatus for supporting positioning for terminals in a wireless network - Google Patents

Description

Method and apparatus for supporting positioning of terminal in wireless network

I. Priority requirements according to 35U.S.C. § 119

This patent application claims priority from the following provisional U.S. applications:

application S/N.61/171,398 entitled "LPP Generic Capabilities" filed on 21.4.2009,

application S/n.61/172,719 entitled "LPP Stage 2(LPP Stage 2)" filed on 25.4.2009,

application S/n.61/218,929 entitled "LPP" filed on 20.6.2009,

application S/N.61/234,282 entitled "LPP" filed on 8/15/2009, and

application S/n.61/247,363 entitled "LPP" filed on 9, 30, 2009,

all of the above are assigned to the assignee of the present application and are expressly incorporated herein by reference.

Background

I. Field of the invention

The present disclosure relates generally to communication, and more specifically to techniques for supporting positioning of terminals in a wireless network.

II. background

It is often desirable and sometimes necessary to know the location of a terminal, such as a cellular telephone. The terms "position" and "location" are synonymous and are used interchangeably herein. For example, a location services (LCS) client may desire to know the location of a terminal and may communicate with a network server in order to request a location for the terminal. The network server and the terminal may then exchange messages as needed to obtain a location estimate for the terminal. The network server may then return the location estimate to the LCS client.

Different terminals may operate in different scenarios and may have different capabilities in terms of positioning. Positioning refers to the function of determining the geographical location of a target terminal. It may be desirable to flexibly support positioning of terminals having different capabilities.

SUMMARY

Techniques for supporting positioning of terminals in a wireless network are described herein. In an aspect, positioning may be supported by a location server that can reside in different entities. In one design, the location server may obtain positioning information (e.g., measurements, coarse positioning estimates, etc.) for the target device via a common positioning protocol. The location server may reside in a network entity or may be co-located with (e.g., may be part of) the target device. The location server may use the common positioning protocol regardless of where it resides and may communicate with other entities via the common positioning protocol. The location server may determine location information (e.g., assistance data, location estimate, etc.) about the target device based on this positioning information.

In another aspect, positioning may be supported by transmitting multiple positioning messages together, which may improve efficiency and reduce latency. In one design, an entity (e.g., a location server, a positioning unit, or a target device) may exchange (e.g., send or receive) multiple positioning messages transmitted together in one message transaction. The multiple positioning messages may be sent as linked messages or in a single container message. The entity may perform positioning based on the plurality of positioning messages.

In yet another aspect, positioning may be supported by transmitting a positioning message that includes multiple portions defined by different organizations. In one design, entities may exchange positioning messages that include a first portion and a second portion for a particular transaction type. The first portion may include first information defined by a first organization for positioning, and the second portion may include second information defined by a second organization for positioning. The entity may perform positioning based on the positioning message. For example, the entity may determine a location estimate based on first information (e.g., measurements) in the first portion and second information (e.g., more measurements, or a coarse location estimate) in the second portion.

In yet another aspect, positioning may be supported with shared measurement data units and/or shared assistance data units applicable to different positioning methods. In one design, entities may exchange measurement data units suitable for use in a first plurality of positioning methods. Each of the first plurality of positioning methods may be associated with a different set of applicable measurement data units. The entity may perform positioning based on the exchanged measurement data units and according to a positioning method, which may be one of the first plurality of positioning methods. Alternatively or additionally, the entities may exchange assistance data units applicable to the second plurality of positioning methods. Each of the second plurality of positioning methods may be associated with a different set of applicable assistance data units. The entity may perform positioning based on the exchanged assistance data units and according to a positioning method, which may be one of the second plurality of positioning methods.

Various aspects and features of the disclosure are described in greater detail below.

Brief Description of Drawings

Fig. 1 shows a diagram of an exemplary deployment that supports positioning.

Fig. 2A shows a configuration supporting a terminal-assisted positioning method and a terminal-based positioning method.

Fig. 2B shows a configuration supporting a network-based positioning method.

Fig. 2C and 2D show two configurations supporting peer-to-peer positioning.

Fig. 3 shows a hierarchical structure of a positioning protocol.

Fig. 4A shows a design of a positioning message.

Fig. 4B shows a design of a positioning message having multiple portions defined by different organizations.

Fig. 5 shows a message flow for a mobile-originated location request service.

Fig. 6 illustrates a message flow for a location session with multiple transactions.

Fig. 7 to 11 show various procedures for supporting positioning.

Fig. 12 shows a block diagram of a target device, a base station and a location server.

Detailed Description

Fig. 1 shows a diagram of an exemplary deployment 100 that supports positioning. The Target Device (TD)110 is the entity whose location is to be determined. The target device 110 may be stationary or mobile and may also be referred to as a terminal, mobile station, User Equipment (UE), access terminal, a Secure User Plane Location (SUPL) enabled terminal (SET) from the Open Mobile Alliance (OMA), a subscriber unit, a station, and so on. Target device 110 may be a cellular telephone, Personal Digital Assistant (PDA), wireless device, wireless modem, wireless router, laptop computer, telemetry device, tracking device, etc. The target device 110 may communicate with one or more base stations in a wireless network. The target device 110 may also communicate peer-to-peer with other terminals.

Reference Source (RS)140 is an entity that transmits signals (e.g., radio signals) that can be measured to support positioning. The reference source 140 may be a satellite in a Satellite Positioning System (SPS), which may be the united states Global Positioning System (GPS), the european Galileo system, the russian GLONASS system, or some other SPS. The reference source 140 may also be a base station in a wireless network. A base station may also be called an access point, a node B, an evolved node B (eNB), etc. The wireless network may be a global system for mobile communications (GSM) network, a Wideband Code Division Multiple Access (WCDMA) network, a General Packet Radio Service (GPRS) access network, a Long Term Evolution (LTE) network, a CDMA1X network, a High Rate Packet Data (HRPD) network, an Ultra Mobile Broadband (UMB) network, a Wireless Local Area Network (WLAN), etc. GSM, WCDMA, GPRS and LTE are different radio technologies defined by an organization named "third generation partnership project" (3 GPP). CDMA1X, HRPD and UMB are different radio technologies defined by an organization named "third generation partnership project 2" (3GPP 2). The reference source 140 may also be a broadcast station in a broadcast network, which may be a television network, a digital broadcast network, etc. The reference source 140 may be part of a terminal, such as the target device 110. In general, one or more signals from one or more reference sources may be measured to determine the location of the target device 110. For simplicity, only one reference source 140 is shown in FIG. 1. The location of the reference source may be known or can be ascertained and can be used for localization of the target device 110.

Location unit (PU)120 is an entity capable of measuring signals from one or more reference sources, such as reference source 140. The positioning unit 120 may also be able to calculate a position estimate for the target device 110 based on measurements obtained by the positioning unit 120. The positioning unit 120 may be part of the target device 110 or part of a separate device or some other entity. The other entity may be another terminal in the wireless network, a base station, a dedicated Location Measurement Unit (LMU), etc.

Location Server (LS)130 is an entity that can receive positioning messages for a target device and determine location information for the target device. In general, the positioning information may be any information used to support positioning. For example, the positioning information may include measurements, coarse position estimates, and the like. The location information may be any information related to the location of the target device. For example, the location information may include assistance data for making measurements on the signals for positioning, a final location estimate for the target device, and so on. Location server 130 may communicate with positioning unit 120, receive positioning information from positioning unit 120, and provide location information (e.g., assistance data) to positioning unit 120. Location server 130 may also calculate a position estimate for target device 110 based on measurements received from positioning unit 120 and provide the position estimate to positioning unit 120. The location server 130 may reside in any one of a number of entities. For example, location server 130 may be a Serving Mobile Location Center (SMLC), a standalone SMLC (sas), an evolved SMLC (E-SMLC), a SUPL Location Platform (SLP), a Position Determination Entity (PDE), or the like. The location server 130 may also be part of a terminal, such as part of the target device 110. In one design, location server 130 may communicate with other entities (e.g., positioning units 120) via a common positioning protocol regardless of where location server 130 resides. The common positioning protocol may be the LTE Positioning Protocol (LPP) used in LTE or some other positioning protocol.

Fig. 1 shows 4 pervasive entities that can support positioning of a target device 110. The entities shown in fig. 1 may support various configurations. In one design, target device 110 and positioning unit 120 may be co-located. In such a design, the target device 110 may measure one or more signals from one or more reference sources to locate the target device 110. In another design, target device 110 and reference source 140 may be co-located. In such a design, target device 110 may transmit a signal that may be measured and used to locate the target device. In yet another design, the target device 110 may be co-located with the location server 130. In such a design, target device 110 may receive measurements from positioning unit 120 and may perform positioning of target device 110 based on the measurements. In general, the target device 110 may support the positioning unit 120 and/or the reference source 140 in order to measure other signals or have its own signals measured. Other configurations may also be supported by the entities shown in fig. 1. For example, the positioning unit 120 and the location server 130 may be co-located. As another example, the reference source 140 and the location server 130 may be co-located.

Fig. 2A shows a configuration supporting a terminal-assisted positioning method and a terminal-based positioning method. In this configuration, the positioning unit 120 is co-located with the target device 110. Positioning unit 120 may measure signals from reference sources such as satellites 140a, base stations 140b, and the like. Positioning unit 120 may send measurements and/or other information (e.g., coarse or fine position estimates) to position server 130. Location server 130 may determine location information (e.g., assistance data) and may send the location information to positioning unit 120 (e.g., to assist positioning unit 120 in measuring signals and possibly obtaining a location estimate). The location server 130 may also determine a location estimate for the target device 110 based on measurements and/or other information received from the positioning unit 120. Location server 130 may forward the location estimate to some external client (not shown in fig. 2A) and/or to target device 110. The configuration in fig. 2A may be used for terminal assisted positioning methods and terminal based positioning methods such as assisted GNSS (a-GNSS), Observed Time Difference (OTD), enhanced observed time difference (E-OTD), observed time difference of arrival (OTDOA), advanced forward link trilateration (a-FLT), etc.

Fig. 2B shows a configuration supporting a network-based positioning method. In this configuration, the reference source 140 is co-located with the target device 110, while the positioning unit 120 is external to the target device 110. The positioning unit 120 may measure signals from the target device 110. The positioning unit 120 may also receive measurements made by the target device 110 for other reference sources (not shown in fig. 2B). Measurements from target device 110 may be used to support handover of target device 110 and/or for other purposes. Positioning unit 120 may send these measurements and/or other information to location server 130. Location server 130 may determine location information (e.g., assistance data) and may transmit the location information to positioning unit 120 (e.g., to assist positioning unit 120 in measuring signals from reference sources 140). The location server 130 may also determine a location estimate for the target device 110 based on measurements and/or other information received from the positioning unit 120. Location server 130 may forward the location estimate to some external client (not shown in fig. 2B) and/or to target device 110. The configuration in fig. 2B may be used for network-based positioning methods such as enhanced cell identity (E-CID), uplink time difference of arrival (U-TDOA), etc.

For simplicity, fig. 2A and 2B illustrate one positioning unit 120 and one or more reference sources 140. In general, any number of positioning units may measure signals from any number of reference sources and may send their measurements to location server 130. The target device 110 may serve as a reference source for some measurements and/or as a positioning unit for other measurements.

Fig. 2A and 2B illustrate two configurations supporting non-peer-to-peer (P2P) positioning. non-P2P positioning may occur when the reference source 140, positioning unit 120, and location server 130 are not co-located with (e.g., not part of) any terminal that is not the target device 110. For non-P2P positioning, location server 130 may be a network entity or part of target device 110, positioning unit 120 may be either part of target device 110 or part of a network entity, and reference source 140 may be either part of target device 110 or part of an external entity (e.g., a satellite, a base station, a broadcast station, etc.).

In one design, the entities shown in FIG. 1 may support P2P positioning. P2P locating may occur when a first terminal assumes the role of location server 130, or locating unit 120, or reference source 140, or any combination thereof, in order to assist in locating a second terminal assuming the role of target device 110. Different types of P2P positioning may be supported depending on where the location server 130, positioning unit 120 and reference source 140 reside, or whether the first or second terminal plays the role of each of the location server, positioning unit and reference source.

Fig. 2C shows a configuration supporting P2P positioning. In this configuration, the first terminal 102 is the target device 110 and also assumes the roles of the location server 130 and the reference source 140. The second terminal 104 is in peer-to-peer communication with the first terminal 102 and assumes the role of the positioning unit 120. The positioning unit 120 in the terminal 104 may measure signals from the reference source 140 in the terminal 102 and may send the measurements and possibly other information to the location server 130 in the terminal 102. Location server 130 may determine location information (e.g., assistance data) and may transmit the location information to positioning unit 120 (e.g., to assist positioning unit 120 in measuring signals from reference sources 140). The location server 130 may also determine a location estimate for the target device 110 based on measurements and/or other information received from the positioning unit 120. The location server 130 may forward the location estimate to some external client (not shown in fig. 2C) and/or pass the location estimate to some entity (e.g., an application) in the target device 110.

For simplicity, fig. 2C shows the terminal 102 communicating with one peer terminal 104. In general, terminal 102 may communicate with any number of peer terminals and may request measurements from one or more peer terminals. Each peer terminal may act as a positioning unit and may measure signals from the terminal 102. Each peer terminal may send the measurements and its own location to the terminal 102. The location of terminal 102 may be determined based on measurements from all peer terminals and their reported locations.

Fig. 2D shows another configuration that supports P2P positioning. In this configuration, the first terminal 106 is the target device 110 and also takes the role of the positioning unit 120 and the location server 130. The second terminal 108 is in peer-to-peer communication with the first terminal 106 and assumes the role of reference source 140. The positioning unit 120 in the terminal 106 may measure signals from the reference source 140 in the terminal 108 and may send the measurements and/or other information to the location server 130 in the terminal 106. Location server 130 may also receive the location of terminal 108. Location server 130 may determine location information (e.g., assistance data) and may communicate the location information to positioning unit 120 in terminal 108 (e.g., to assist positioning unit 120 in measuring signals from reference sources 140). The location server 130 may also determine a location estimate for the target device 110 based on measurements and/or other information received from the positioning unit 120. The location server 130 may forward the location estimate to some external client (not shown in fig. 2D) and/or pass the location estimate to some entity (e.g., an application) in the target device 110.

For simplicity, fig. 2D shows the terminal 106 communicating with one peer terminal 108. In general, terminal 106 may communicate with any number of peer terminals and may make measurements for one or more peer terminals. Each peer terminal may serve as a reference source for signals that may be measured by terminal 106. Each peer terminal may send its own location to the terminal 106. The location of terminal 106 may be determined based on measurements of all peer terminals and their reported locations.

For P2P positioning, the roles of positioning unit 120 and location server 130 may be assumed by different terminals. To avoid ambiguity, the terminal initiating the seek transaction may specify which end/terminal of the transaction will assume the role of each of the location server and the positioning unit. Each terminal may then assume the role specified by the originating terminal.

P2P positioning may be used to position the terminal as described above. P2P positioning may also be used to help locate access points for femtocells, which may also be referred to as Home Node Bs (HNBs), home enbs (henbs), etc. In this case, the access point may be treated as if it were a terminal.

In one design, a Generalized Positioning Method (GPM) may be used to support positioning of a target device. A ubiquitous positioning method is a method that uses the same type of measurement and location calculation procedures to support positioning of a target device with different types of reference sources.

Table 1 lists some of the ubiquitous location methods that can be supported and provides a short description of each.

TABLE 1 Universal positioning method

One or more of the ubiquitous location methods listed in table 1 may further include detecting the presence of a particular reference source without measuring signals from the reference source, thereby supporting cell-ID based or WLAN based location. A combination of ubiquitous positioning methods may also be used for positioning, for example to improve accuracy.

In one design, a set of Positioning Method Classes (PMCs) may be defined. The PMC may include a set of positioning methods defined by applying one or more pervasive positioning methods to a given type of reference source. Different types of reference sources may be used for positioning and may include LTE enbs, LTE-capable terminals, CDMA1X base stations, 1X-capable terminals, and so on. For a given type of reference source, one or more specific positioning methods may be defined by applying one or more generic positioning methods to this reference source. For example, A-GPS may be obtained by applying a downlink time difference based GPM to a GPS reference source, U-TDOA may be obtained by applying an uplink time difference based GPM to a GSM reference source, E-CID may be obtained by applying a direction based GPM and/or an RF pattern matching GPM to an LTE reference source, and so on.

Each PMC may include one or more positioning methods. The positioning methods in each PMC may be of interest because they employ measurements of the same type of reference source. These measurements may overlap, and the same measurement may be useful for different positioning methods within the PMC. The assistance data used to implement measurements and/or position calculations for positioning methods in the same PMC may also overlap (e.g., if the measurements also overlap). Overlapping measurement and assistance data may be used to more efficiently support several positioning methods within a PMC by using reduced sets of measurement and assistance data. For example, measurement and assistance data applied to multiple positioning methods may be transferred only once instead of for each positioning method.

Fig. 3 illustrates a hierarchical structure 300 of a positioning protocol that may be used by the location server 130. The positioning protocol may support a set of PMCs, which may be defined for different types of reference sources as described above. Each PMC may include a set of one or more positioning methods defined for a particular type of reference source. For example, A-GNSS PMC may include A-GPS and A-Galileo positioning methods, downlink LTE PMC may include OTDOA and E-CID positioning methods, uplink LTE PMC may include E-CID positioning methods, and so on. Other PMCs may be defined for downlink WCDMA, uplink WCDMA, downlink CDMA1X, uplink CDMA1X, downlink WiMAX, uplink WiMAX, 802.11Wi-Fi, sensors, etc.

Location methods (PMs) may be used to determine the location of a target device and may be associated with particular ubiquitous location methods and/or particular reference source types. Each positioning method may support all or a subset of all measurement and assistance data applicable to its PMC. The measurement and assistance data sets supported by a given positioning method may be mandatory, or optional, or conditional on any positioning unit or location server supporting the positioning method.

A positioning unit or location server supporting a given PMC may support at least one positioning method in the PMC. A positioning unit or a location server supporting a given positioning method may support all mandatory (and possibly also optional and/or conditional) measurements and assistance data of the positioning method.

In one design, a set of Measurement Data Units (MDUs) may be defined for all supported positioning methods. An MDU may be a collection of one or more data items that may be used to report measurements and their attributes. The MDU may be adapted to one or more positioning methods within a particular PMC. The MDU is applicable to a variety of positioning methods and can efficiently transmit measurement data once to provide them (rather than separately for each positioning method). For example, MDU2 in fig. 3 may be applied to the positioning methods PMa and PMb and transmitted once for use by both positioning methods. The MDU may be applied to one reference source and may be repeated for multiple reference sources of the same type, e.g., to provide or request pseudoranges for multiple satellites, timing differences for multiple base stations, etc.

The MDUs may enable the capabilities of the location server and the positioning unit to be defined, for example in the sense of which MDUs the location server or the positioning unit supports. The MDU may also enable the location server 130/positioning unit 120 to request/provide measurement data in a flexible and accurate manner. The location server 130 may indicate certain characteristics of the MDU (e.g., accuracy and response time) when requesting the MDU from the positioning unit 120. Positioning unit 120 may indicate (e.g., via its capabilities) characteristics (e.g., accuracy) of the MDU that it is capable of providing.

In one design, a set of Assistance Data Units (ADUs) may be defined for all supported positioning methods. An ADU may be a collection of one or more data items that may be used to assist in measurements. The ADU may be adapted to one or more positioning methods within a particular PMC. The ADU is applicable to a plurality of positioning methods and can efficiently transmit assistance data once to provide them (instead of separately for each positioning method). For example, ADU d in fig. 3 may be applied to location method PMd and PMe and sent once for use by both location methods. The ADU may be applied to one reference source and may be repeated for multiple reference sources of the same type, e.g., to provide or request ephemeris data for multiple satellites within the same SPS, Real Time Differences (RTDs) for multiple base stations of the same access type, etc.

The ADUs may enable the capabilities of the location server and the positioning unit to be defined, for example in the sense of which ADUs are supported by the location server or the positioning unit. The ADU may also enable the positioning unit 120/location server 130 to request/provide assistance data in a flexible and accurate manner. The positioning unit 120 may indicate certain characteristics of the ADU (e.g., the age or accuracy of the GPS ephemeris data) when requesting the ADU from the location server 130.

In one design, PMCs, positioning methods, MDUs, and/or ADUs may be individually identified. Such identification may facilitate capabilities, specific measurements, and specific assistance data being requested and provided. The identification may also be useful for identifying the presence of a particular MDU or ADU in a positioning message, identifying message segments related to a particular positioning method or PMC, etc. The identity of the PMC may be unique across the positioning protocol, while the identities of the positioning method, MDU and ADU may only be unique for a particular PMC. Different ID ranges may be used for identification. For example, PMC ID 0 may be reserved for possible future signaling applicable to all PMCs, PMC IDs 1 through 63 may be used for network-based (uplink) PMCs, PMC IDs 64 through 127 may be used for terminal-assisted and terminal-based (downlink) PMCs, PMC IDs 128 through 191 may be used for operator-specific positioning methods, PMC IDs 192 through 254 may be used for vendor-specific positioning methods, and PMC ID 255 may be used to indicate a PMC ID greater than 255 where needed. In general, IDs may be defined for PMCs, positioning methods, MDUs, and/or ADUs in any suitable manner.

In one design, a calibration PMC may be used to provide calibration data for one or more reference sources to a location server. The calibration data may be used for (i) signal timing and/or signal strength of base stations, access points, and/or other reference sources, (ii) timing and navigation data of GNSS systems, and/or (iii) other signals and data. The calibration data may be used by the location server to obtain assistance data which can later be provided to the positioning unit to assist it in making measurements to locate the target device. As an example, calibration data comprising time base differences in transmission between nearby base stations may be used by a location server to derive assistance data for a downlink time difference positioning method such as OTDOA (e.g. comprising an approximate time difference between nearby base stations that the target device would be expected to measure). Such assistance data may be sent to a location unit co-located in the target device at a later time. Calibrating a PMC (or a calibration positioning method) may support a corresponding normal PMC (or a normal positioning method) as described in the above example by helping to obtain assistance data for the normal PMC (or the normal positioning method) and by helping any positioning method in the normal PMC to calculate a position estimate. For example, calibration PMC for inter-eNB timing measurements may support downlink LTE PMC including OTDOA and E-CID positioning methods.

Using calibration PMC as part of a common positioning protocol that also supports normal PMC may allow the common positioning protocol to be used to calibrate the reference source and thereby avoid the need for additional protocols for this purpose. Calibrating the PMC may not directly support any positioning method, any ADU, and positioning of the target device. The calibration PMC may support MDUs, which may be provided by a positioning unit (e.g., a base station or LMU) as a reference source suitable for a corresponding normal PMC. The MDU may be used by a location server to help obtain ADUs for the corresponding normal PMC, and to help a positioning method in the corresponding normal PMC compute a location estimate.

In one design, location server 130 and target device 110 (or location server 130 and positioning unit 120) may engage in a location session to obtain measurements or locations, provide assistance data, and/or for other purposes. The location session may also be referred to as an LPP session, a positioning session, etc. The location session may include one or more transactions, which may also be referred to as LPP transactions, and the like. Each transaction may encompass a particular operation, such as an exchange of capabilities, a transfer of assistance data, a transfer of location information, and so forth. Each transaction may be assigned a transaction ID and all messages for that transaction may include that transaction ID in order to link the messages to the same transaction.

In one design, a set of positioning messages may be defined and used for communication between a location server and other entities. The positioning messages may also be referred to as LPP messages, LPP Protocol Data Units (PDUs), etc.

Fig. 4A shows a design of a positioning message 400. In this design, the positioning message 400 includes a positioning protocol version field 410, a transaction ID field 412, a transaction end flag field 414, a message type field 416, and N information elements 420a through 420N, where N may be 0 or greater. The field 410 may indicate which version of the positioning protocol is used for the location session and may be included to negotiate the use of the same positioning protocol version by two entities engaged in the location session. The originating entity may set field 410 to the highest version supported by itself. The receiving entity may return the highest version supported by itself. The agreed upon version may be the lower of the two highest versions supported by the two entities.

The field 412 may identify the transaction to which the location message applies. The field 412 may be particularly appropriate when multiple transactions occur concurrently during a location session. Each transaction may be assigned a unique transaction ID. In one design, an originating entity that initiates a transaction may assign a transaction ID to the transaction. The responding entity may use the same transaction ID when responding to the originating entity. For example, location server 130 may assign a transaction ID to a transaction initiated by location server 130, while positioning unit 120 may assign a transaction ID to a transaction initiated by positioning unit 120. When more than one location server is used to locate target device 110, each location server may be assigned a different range of transaction IDs that can be assigned by that location server.

Field 414 may indicate whether the sending entity has terminated the transaction. Field 416 may indicate the type of message being sent. A set of message types may be supported as described below, and the positioning message 400 may be of the type indicated by field 416.

Fields 420a through 420n may include information that may depend on the type of message. Each field 420 may carry a Positioning Data Component (PDC) for one PMC or positioning method. The positioning message 400 may include multiple PDCs to efficiently convey information for more than one PMC at a time and invoke combined/hybrid positioning.

The positioning message may also include different fields and/or fields other than those shown in fig. 4A. For example, the positioning message may include a field for a session ID, a field to indicate whether the sender is acting as a location server or a positioning unit, and so on.

Table 2 lists a set of positioning message types that may be supported according to one design.

TABLE 2 location message types

Message type	Description of the invention
		Request capabilities	A message for requesting capabilities of a positioning protocol and a positioning method of an entity.
Providing capability	Messages for providing capabilities of a positioning protocol and a positioning method of an entity.
		Requesting assistance data	A message for requesting assistance data.
Providing assistance data	A message for providing assistance data.
		Requesting location information	A message for requesting location information.
Providing location information	A message for providing location information.

Location server 130 may provide its capabilities upon request by positioning unit 120 or may unilaterally transmit its capabilities without receiving any request. Similarly, the positioning unit 120 may provide its capabilities upon request by the location server 130 or may unilaterally transmit its capabilities without receiving any request. The capabilities of an entity (e.g., location server 130 or positioning unit 120) may include PMCs and positioning methods supported by the entity, as well as the capabilities of the entity for each supported positioning method (e.g., a list of MDUs that the entity can send or receive and/or a list of ADUs that the entity can send or receive).

Location server 130 may provide assistance data upon request by positioning unit 120 or may unilaterally transmit assistance data without receiving any request. The assistance data may assist the positioning unit 120 in making measurements that may be used for positioning of the target device 110 or for calibration of the reference source 140. The location server 130 may also provide assistance data when the assistance data changes with the positioning method in progress. Such automatic updating of assistance data may enable the positioning method to be reset without having to explicitly be aborted or restarted. For example, target device 110 may change serving cell during the OTDOA positioning method (e.g. due to handover), and location server 130 may send new assistance data applicable to the new serving cell to enable positioning unit 120 (in target device 110) to obtain and communicate measurements of different neighbor base stations associated with the new serving cell. As another example, location unit 120 (e.g., an LMU) may measure data and/or signaling channels transmitted by target device 110 in a particular serving cell for U-TDOA location, and target device 110 may change serving cells (e.g., due to handover). Location server 130 may then send new assistance data to positioning unit 120 to enable it to measure different data and/or signaling channels associated with the new serving cell. It may be useful to have automatic updates in these scenarios.

Positioning unit 120 may send positioning information to location server 130 to support positioning of target device 110 (e.g., for normal PMC) or to determine assistance data for future positioning (e.g., for calibration PMC). The positioning information may include (i) measurements made by the positioning unit 120 within the target device 110 on other reference sources (e.g., as shown in fig. 2A), (ii) measurements made by the positioning unit 120 external to the target device 110 on the reference sources 140 in the target device 110 (e.g., as shown in fig. 2B), (iii) a location estimate for the target device 110 obtained by the positioning unit 120, and/or (iv) other information related to the location of the target device 110. Location server 130 may send location information to positioning unit 120 that includes a location estimate for target device 110, e.g., provided that positioning unit 120 is part of target device 110 and that target device 110 is the intended ultimate recipient of the location estimate. For calibration of reference sources, positioning information may include measurements made by positioning unit 120 on network-based reference sources (e.g., base stations) as well as other sources (e.g., satellites).

The positioning message may also include a field for a common parameter for all PMCs supported by the positioning message. Common parameters of the request capability message and the provide capability message may include a list of supported PMC IDs, PMC versions, and the like. Common parameters of the request assistance data message may include an approximate location of the target device, an indication of whether periodic or triggered assistance data is requested and associated parameters, primary access (e.g., serving cell ID), secondary access (e.g., neighbor cell ID), and so on. Common parameters for providing assistance data messages may include the approximate location of the target device, the current time, and so on. Common parameters of the request location information message may include a required quality of service (QoS) (e.g., for location, measurement accuracy, and/or response time), an indication of whether periodic or triggered location information is requested and associated parameters, a location type of the terminal-assisted and/or terminal-based positioning method, a list of required or preferred PMC IDs and PMC versions, and so forth. Common parameters for providing location information messages may include location estimation and accuracy, time, rate, and so on.

Fig. 4B illustrates a design of a positioning message 450 that includes multiple portions defined by different organizations. The positioning message 450 may include a positioning protocol version field, a transaction ID field, a transaction end flag field, a message type field, and N information elements as described above with respect to fig. 4A. In one design, one portion may be sent in each information element. For example, the first portion may include first information defined by a first organization for positioning, the second portion may include second information defined by a second organization for positioning, and so on. The organization may be 3GPP, 3GPP2, OMA, Internet Engineering Task Force (IETF), Institute of Electrical and Electronics Engineers (IEEE), network operator, equipment vendor, etc. These multiple portions may be for specific transaction types, such as capability transfer, assistance data transfer, location information transfer, and so forth. Such a design may allow an external organization to enhance existing positioning methods or support new positioning methods by defining additional capabilities that may be carried in one or more additional portions of the positioning message.

In one design, several item-related transactions may be invoked in parallel. For example, the positioning unit 120 may be co-located with the target device 110 (e.g., as shown in fig. 2A) and may request its own location from the location server 130, request assistance data from the location server 130, and provide its own capabilities to the location server 130 to enable the location server 130 to obtain its location. As another example, positioning unit 120 may be co-located with target device 110 and may request its own location from location server 130, and may provide measurements for one or more positioning methods (e.g., E-CID and/or a-GNSS) to location server 130 to enable location server 130 to derive a location estimate. The messages sent by the positioning unit 120 to the location server 130 in both examples above may also be combined. As yet another example, location server 130 may request positioning information from positioning unit 120, which may be co-located with target device 110, and may provide assistance data to positioning unit 120 to assist in obtaining the positioning information.

In one design, multiple positioning messages for multiple transactions may be transmitted together in one message transaction/exchange. In one design, a single container message may include the multiple positioning messages. For example, the container message may be a predefined positioning message that can carry multiple positioning messages in multiple information elements, one information element for each individual positioning message. In another design, the multiple positioning messages may be linked and sent separately, either serially or in parallel. A common identifier may be included in each message to enable association of the separate messages at the receiving entity. The multiple positioning messages may also be transmitted together in other manners. The format and content of each positioning message may not depend on whether the positioning message is sent alone or with other positioning messages.

The sending entity may send a container message that includes a plurality of positioning messages for a plurality of transactions. The recipient entity may generate individual replies for the plurality of transactions and may use the relevance of the plurality of positioning messages to provide a more appropriate response, for example, by generating a reply to each received message using the information contained in all received positioning messages. The recipient entity may return a container message that includes multiple positioning messages in reply with respect to these individuals. Transmitting multiple location messages together may provide various advantages, such as (i) reducing latency and avoiding problems with out-of-order delivery of location messages in the case of separate transmissions, and (ii) ensuring that the receiving entity has the most information needed to process and reply to each received message.

Fig. 5 illustrates a message flow 500 for a mobile-originated location request (MO-LR) service in LTE. An LCS client in the UE510 or a user of the UE510 may request location services, for example, to retrieve the location of the UE510 or to communicate the UE location to a third party. The UE510 may send a MO-LR request message to a Mobility Management Entity (MME)540 via the serving eNB 520 (step 1). The MO-LR request message may be used as a container message to carry one or more positioning messages to instigate one or more procedures. For example, the MO-LR request message may include a positioning message for providing capabilities of the UE510, a positioning message for requesting assistance data, a positioning message for providing measurements, and so on. The MME540 may send a location request message to the E-SMLC530 (step 2). The location request message may include any positioning messages received by the MME540 in step 1.

E-SMLC530 and UE510 may engage in a location session and may perform one or more transactions (step 3). For the location session, the UE510 may be a target device and a positioning unit, and the E-SMLC530 may be a location server. The E-SMLC530 may instigate one or more transactions to obtain positioning capabilities of the UE510, provide assistance data to the UE510, and/or obtain positioning information from the UE 510. After receiving the first positioning message from E-SMLC530, UE510 may instigate one or more transactions to request assistance data, request further assistance data, and so on.

E-SMLC530 and eNB 520 may engage in a location session and may perform one or more transactions (step 4). For the location session, the eNB 520 may be a positioning unit and the E-SMLC530 may be a location server. The E-SMLC530 may obtain a positioning message for the UE510 from the eNB 520 via the location session. Steps 3 and 4 may occur in any order or in parallel. The E-SMLC530 may return a location response message to the MME540 (step 5). The location response message may include any location estimates obtained from steps 3 and 4 and/or a final positioning message, which may provide a location estimate if the UE510 requested a location estimate in step 1. If the UE510 requests delivery of the location to a third party, the MME540 may deliver the location estimate received from the E-SMLC530 to the third party (step 6). The MME540 may send a MO-LR response message to the UE510 that may carry any final positioning messages received in step 5 and/or a separate location estimate (step 7).

For control plane location solutions, a network entity (e.g., MME 540) may need to request location services from a location server (e.g., E-SMLC 530) before a location session can occur. For MO-LR service, a target device (e.g., UE 510) may first send a MO-LR request message to a network entity to request location services. The target device may then wait for a response from the network entity, and may thereafter send a first positioning message to the location server. This additional delay may be avoided by having the target device include the first positioning message in the MO-LR request message sent to the network entity. The network entity may then communicate this first positioning message to the location server in a location request message. Subsequent location messages may be sent more directly between the target device and the location server without utilizing the non-access stratum (NAS) layer to which the MO-LR request message belongs. The final location message from the location server may be sent directly to the target device or via a MO-LR response message to the target device, which may reduce the total number of messages to be delivered.

Fig. 6 illustrates a message flow 600 for a location session with multiple transactions. Message flow 600 may be used for the location session in step 3 and/or the location session in step 4 of fig. 5. Target device 110 may send a MO-LR request message to location server 130 (step 1). The MO-LR request message may carry one or more positioning messages to enact one or more procedures. The positioning message may include the required QoS, whether a triggered or periodic seek is requested, and/or other information. If the location capabilities of the target device 110 are not received in step 1, the location server 130 may send a location message to request the location capabilities of the target device 110 (step 2). The target device 110 may return a positioning message with its positioning capabilities (e.g., supported positioning methods) (step 3).

Location server 130 may send a positioning message to request positioning information, such as positioning-related measurements for the positioning methods supported by target device 110 (step 4). The target device 110 may send a positioning message to request assistance data (step 5). Location server 130 may return a location message with the requested assistance data (step 6). Location server 130 may also send one or more subsequent positioning messages (not shown in fig. 6) with updated assistance data, e.g., when triggered by a change or at periodic intervals. The target device 110 may obtain location information (e.g., measurements) and may send a location message with the location information (step 7). The target device 110 may also send one or more subsequent positioning messages (not shown in fig. 6) with updated location information, e.g., when triggered by a change or at periodic intervals. The location server 130 may also use the positioning information received in step 7 to calculate a location estimate for the target device 110. Location server 130 may then send a MO-LR response message, which may include a positioning message and/or a location estimate, to target device 110 (step 8). Location server 130 may also send one or more subsequent positioning messages (not shown in fig. 6) with updated position estimates, e.g., upon being triggered by some event, or at periodic intervals, or upon receiving further positioning information from the target device, etc.

Fig. 6 illustrates an exemplary location session with 3 explicit transactions A, B and C. In general, a location session may include any number of transactions as well as any type of transaction. Multiple transactions of the same type may also be performed. For example, a transaction to obtain positioning information from a target device to support an E-CID positioning may be performed to obtain an approximate position, and a separate a-GNSS association transaction may be performed in parallel or subsequently to obtain an accurate position.

Fig. 6 shows a message flow for the MO-LR service. The message flow for the mobile-terminated location request (MT-LR) service may be defined with steps 2 to 7 in fig. 6.

As shown in FIG. 6, several transactions may be performed. The transaction may involve a pair of positioning messages exchanged between the positioning unit in the target device 110 and the location server 130, as shown in fig. 6. A transaction may also involve a single positioning message sent unilaterally by one entity. For example, the positioning unit in the target device 110 may provide its capabilities unilaterally without receiving a request for capabilities, and the location server 130 may provide assistance data unilaterally without receiving a request for assistance data. Multiple location messages for multiple transactions may be aggregated and passed together. For example, the positioning messages in steps 2 and 4 may be delivered together, the positioning messages in steps 3 and 5 may be delivered together, and so on.

Fig. 7 shows a design of a process 700 used by a location server to support positioning. The location server may obtain location information for the target device via a common location protocol, which may be LPP or some other location protocol (block 712). The location server may reside on one of a number of possible entities and the target device may be one of these entities. For example, the location server may reside in a network entity or may be co-located with the target device. The location server may use the common positioning protocol regardless of where it resides and may communicate with other entities via the common positioning protocol. A common positioning protocol may simply mean that the same positioning protocol is used regardless of where the location server resides. The location server may determine location information about the target device (block 714).

In one design, the positioning information may include measurements of at least one reference source. For example, the location server may obtain measurements of at least one signal from at least one satellite, or at least one base station, or at least one terminal, or a target device, or some other entity, or a combination thereof. The location information may include a location estimate for the target device, which may be determined by the location server based on these measurements. In another design, the positioning information may (i) indicate a location of the target device, which may include, for example, a coarse or fine position estimate, or (ii) may include measurements of a reference source that may be received at the location of the target device. The location information may include assistance data determined by the location server based on the positioning information. In yet another design, the location information may include assistance data and the positioning information may include measurements made based on the assistance data. In general, positioning information may include measurements, position estimates, and the like. The location information may include location estimates, assistance data, and the like. The two steps in fig. 7 may be performed in the order shown in fig. 7, or in the reverse order. The location information may be determined based on the positioning information, or vice versa.

In one design, a positioning unit for a target device may determine positioning information, e.g., make measurements. The positioning unit may reside on one of the second plurality of possible entities and the target device may be one of these entities. The location server may communicate with the positioning units via a common positioning protocol. For example, the location server may exchange capabilities, or assistance data, or location information, or a combination thereof, with the positioning unit via a common positioning protocol.

Fig. 8 shows a design of a process 800 for supporting positioning by an entity, which may be a target device, or a positioning unit, or some other entity. The entity may send location information regarding the target device to a location server via a common location protocol (block 812). The location server may reside on one of a number of possible entities and may use a common positioning protocol regardless of where it resides. The target device may be one of the plurality of possible entities. The entity may receive location information about the target device from a location server (block 814).

In one design, the positioning information may include measurements of at least one reference source, and the location information may include a location estimate for the target device determined by the location server based on the measurements. In another design, the positioning information may include measurements of reference sources that may be received at the location of the target device, and the location information may include assistance data determined by the location server based on the positioning information. In yet another design, the location information may include assistance data and the positioning information may include measurements made based on the assistance data. In this design, block 812 may occur after block 814.

In one design, the entity may measure at least one signal from at least one reference source to obtain a measurement. In one design, the at least one reference source may include at least one satellite, or at least one base station, or at least one terminal, or a combination thereof. In this design, these measurements may be made at the target device. In another design, the at least one reference source may include the target device and possibly other reference sources. In this design, these measurements may be made at a positioning unit external to the target device.

Fig. 9 shows a design of a process 900 for supporting positioning by an entity, which may be a location server, a positioning unit, a target device, or some other entity. The entities may exchange (e.g., send or receive) multiple positioning messages transmitted together in one message transaction (block 912). In one design, the entity may send the multiple location messages as linked messages or in a single container message. In another design, the entity may receive the multiple positioning messages, which may be sent as linked messages or in a single container message. The entity may perform positioning based on the plurality of positioning messages (block 914).

In one design, the multiple positioning messages may be sent by the target device with the MO-LR message to initiate positioning. In another design, the plurality of positioning messages may be sent by a location server and may include (i) a first positioning message carrying assistance data and (ii) a second positioning message requesting location information. In yet another design, the plurality of positioning messages may be sent to a location server (e.g., by a positioning unit or a target device) and may include (i) a first positioning message requesting assistance data, and (ii) a second positioning message carrying measurements. The plurality of messages may also include some other combination of messages.

In one design, each of the plurality of positioning messages may be one of a plurality of message types, which may include a request capability message type, a provide capability message type, a request assistance data message type, a provide assistance data message type, a request location information message type, and a provide location information message type. The plurality of positioning messages may include positioning messages of at least two message types.

Fig. 10 shows a design of a process 1000 for supporting positioning by an entity, which may be a location server, a positioning unit, a target device, or some other entity. The entities may exchange location messages including a first portion and a second portion for a particular transaction type (block 1012). The first portion may include first information defined by a first organization for positioning, and the second portion may include second information defined by a second organization for positioning. For example, the first organization may include 3GPP or some other organization. The second organization may include 3GPP2, OMA, IETF, IEEE, a network operator, an equipment vendor, or some other organization. The entity may perform positioning based on the positioning message (block 1014).

In one design of block 1012, the entity may be a target device that sends or receives positioning messages to/from a location server. In another design, the entity may be a location server that sends or receives positioning messages to/from the target device.

In one design of block 1014, the entity may determine assistance data or a location estimate based on first information (e.g., measurements) in a first portion and second information (e.g., more measurements, or a coarse location estimate) in a second portion. In another design, the entity may make measurements based on first information in the first portion (e.g., assistance data for a satellite) and second information in the second portion (e.g., assistance data for a base station).

Fig. 11 shows a design of a process 1100 for supporting positioning by an entity, which may be a location server, a positioning unit, a target device, or some other entity. The entities may exchange measurement data units applicable to a first plurality of positioning methods, where each positioning method of the first plurality of positioning methods is associated with a different set of applicable measurement data units (block 1112). For example, the exchanged measurement data unit may be MDU2 in fig. 3, the first plurality of positioning methods may include PMa and PMb, positioning method PMa may be associated with a first set having MDUs 1, 2 and 3, and positioning method PMb may be associated with a second set having MDUs 2 and 3. The entity may perform positioning based on the exchanged measurement data units and according to a positioning method, which may be one of the first plurality of positioning methods (block 1114).

Alternatively or additionally, the entities may exchange assistance data units applicable to a second plurality of positioning methods, wherein each positioning method of the second plurality of positioning methods is associated with a different set of applicable assistance data units (block 1116). The entity may perform positioning based on the exchanged assistance data units and according to a positioning method, which may be one of the second plurality of positioning methods (block 1118).

In general, only shared measurement data units may be supported, or only shared auxiliary data units may be supported, or both shared measurement and auxiliary data units may be supported. If only shared measurement data units are supported, blocks 1112 and 1114 may be performed and blocks 1116 and 1118 may be omitted. If only shared auxiliary data units are supported, blocks 1116 and 1118 may be performed, and blocks 1112 and 1114 may be omitted. Blocks 1112 through 1118 may be performed if both shared measurement and assistance data units are supported.

Fig. 12 shows a block diagram of a design of a target device 110, a base station 122 and a location server 130. Target device 110 may be a UE, a SET, or the like. Location server 130 may be an SMLC, E-SMLC, SLP, or the like. Positioning unit 120 may reside in target device 110, base station 122, or some other entity. The reference source 140 may be part of the base station 122, or a satellite, or some other entity. For simplicity, fig. 12 illustrates only one controller/processor 1220, one memory 1222, and one transmitter/receiver (TMTR/RCVR)1224 for target device 110, one controller/processor 1230, one memory 1232, one transmitter/receiver 1234, and one communication (Comm) unit 1236 for base station 122, and one controller/processor 1240, one memory 1242, and one communication unit 1244 for location server 130. In general, each entity may include any number of processing units (processors, controllers, etc.), memories, transmitters/receivers, communication units, etc.

On the downlink, base station 122 may transmit data, signaling, and pilot to terminals that are within its coverage area. These various types of information may be processed by processing unit 1230, conditioned by transmitter 1234, and transmitted on the downlink. At target device 110, downlink signals from base station 122 and other base stations may be received and conditioned by receiver 1224 and further processed by processing unit 1220 to obtain various types of information. Processing unit 1220 may perform process 800 in fig. 8, process 900 in fig. 9, process 1000 in fig. 10, process 1100 in fig. 11, and/or other processes for the techniques described herein. Memories 1222 and 1232 may store program codes and data for target device 110 and base station 122, respectively. On the uplink, target device 110 may transmit data, signaling, and pilot to base station 122. These various types of information may be processed by processing unit 1220, conditioned by transmitter 1224, and transmitted on the uplink. At base station 122, the uplink signals from target device 110 and other terminals may be received and conditioned by receiver 1234 and further processed by a processing unit 1230 to obtain various types of information from the terminals. Base station 122 may communicate with location server 130 directly or indirectly via communication unit 1236.

Within location server 130, a processing unit 1240 may perform processing to support location services and positioning for the terminal. For example, processing unit 1240 may perform process 700 in fig. 7, process 800 in fig. 8, process 900 in fig. 9, process 1000 in fig. 10, process 1100 in fig. 11, and/or other processes for the techniques described herein. The processing unit 1240 may also calculate a location estimate for the target device 110, provide location information, and so on. Memory 1242 may store program codes and data for location server 130. A communication unit 1244 may allow location server 130 to communicate with base stations 122 and/or other network entities. Location server 130 and target device 110 may exchange positioning messages with other network entities (not shown) via base station 122.

Positioning unit 120 may reside in terminal 110, or base station 122, or location server 130. In this case, the processing by the positioning unit 120 may be performed by the processing units 1220, 1230, or 1240, respectively. The positioning unit 120 may also be external to the entity shown in fig. 12. In this case, the positioning unit 120 may include one or more processing units (processors, controllers, etc.), memories, transmitters/receivers, communication units, etc. capable of performing the required functions.

Those of skill in the art would understand that information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

Those of skill would further appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the disclosure herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

The position determination techniques described herein may be implemented in conjunction with various wireless communication 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 terms "network" and "system" are often used interchangeably. The WWAN may be a Code Division Multiple Access (CDMA) network, a Time Division Multiple Access (TDMA) network, a Frequency Division Multiple Access (FDMA) network, an Orthogonal Frequency Division Multiple Access (OFDMA) network, a single carrier frequency division multiple access (SC-FDMA) network, a Long Term Evolution (LTE) network, a WiMAX (IEEE 802.16) network, or the like. A CDMA network may implement one or more Radio Access Technologies (RATs), such as CDMA2000, wideband CDMA (W-CDMA), and so on. Cdma2000 includes IS-95, IS-2000 and IS-856 standards. A TDMA network may implement Global System for Mobile communications (GSM), digital advanced Mobile Phone System (D-AMPS), or some other RAT. GSM and W-CDMA are described in documents from a consortium named "third generation partnership project" (3 GPP). Cdma2000 is described in a document from a consortium named "third generation partnership project 2" (3GPP 2). The 3GPP and 3GPP2 documents are publicly available. The WLAN may be an IEEE 802.11x network, and the WPAN may be a bluetooth network, IEEE 802.15x, or some other type of network. The techniques may also be implemented in conjunction with any combination of WWAN, WLAN and/or WPAN.

Satellite Positioning Systems (SPS) typically include a transmitter system positioned so that entities can determine their own position on or above the earth based, at least in part, on signals received from the transmitter. Such transmitters typically transmit a signal marked with a repeating pseudo-random noise (PN) code having a set number of chips and may be located on ground-based control stations, user equipment, and/or space vehicles. In a particular example, such transmitters may be located on earth-orbiting Satellite Vehicles (SVs). For example, an SV in a constellation of a Global Navigation Satellite System (GNSS), such as Global Positioning System (GPS), Galileo, Glonass, or Compass, may transmit a signal marked with a PN code that may be distinguished from PN codes transmitted by other SVs in the constellation (e.g., using a different PN code for each satellite as in GPS or having the same code on a different frequency as in Glonass). According to certain aspects, the techniques presented herein are not limited to global SPS systems (e.g., GNSS). For example, the techniques provided herein may be applied to or otherwise enabled for use in various regional systems, such as, for example, quasi-zenith satellite system (QZSS) over japan, Indian Regional Navigation Satellite System (IRNSS) over india, beidou over china, etc., and/or various augmentation systems (e.g., satellite-based augmentation systems (SBAS)) that may be associated with or otherwise enabled for use with one or more global and/or regional navigation satellite systems. By way of example and not limitation, the SBAS may include an augmentation system that provides integrity information, differential corrections, and the like, such as, for example, a Wide Area Augmentation System (WAAS), European Geostationary Navigation Overlay Service (EGNOS), a multi-function satellite augmentation system (MSAS), GPS assisted Geo augmented navigation, or GPS and Geo augmented navigation system (GAGAN), and/or the like. Thus, as used herein, an SPS may include any combination of one or more global and/or regional navigation satellite systems and/or augmentation systems, and SPS signals may include SPS signals, SPS-like signals, and/or other signals associated with such one or more SPS.

The methodologies described herein may be implemented by various means depending on the application. For example, these methodologies may be implemented in hardware, firmware, software, or any combination thereof. For an implementation involving hardware, the processing units may be implemented within one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), processors, controllers, micro-controllers, microprocessors, electronic devices, other electronic units designed to perform the functions described herein, or a combination thereof.

For implementations involving firmware and/or software, the methodologies may be implemented with modules (e.g., procedures, functions, and so on) that perform the functions described herein. Any machine-readable medium tangibly embodying instructions may be used in implementing the methodologies described herein. For example, software codes may be stored in a memory and executed by a processing unit. The memory may be implemented within the processing unit or external to the processing unit. As used herein, the term "memory" refers to any type of long term, short term, volatile, nonvolatile, or other memory and is not to be limited to any particular type of memory or number of memories, or type of media upon which memory is stored.

If implemented in firmware and/or software, the functions may be stored on a computer-readable medium as one or more instructions or code. Examples include computer-readable media encoded with a data structure and computer-readable media encoded with a computer program. The computer readable medium may take the form of an article of manufacture. Computer-readable media includes physical computer storage media. A storage media may be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage, semiconductor storage, or other memory devices, or any other medium that can be used to store desired program code in the form of instructions or data structures and that can be accessed by a computer; disk and disc, as used herein, includes Compact Disc (CD), laser disc, optical disc, Digital Versatile Disc (DVD), floppy disk and blu-ray disc where disks (disks) usually reproduce data magnetically, while discs (discs) reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.

In addition to being stored on a computer-readable medium, the instructions and/or data may also be provided as signals on a transmission medium included in the communication device. For example, the communication device may include a transceiver having signals indicative of instructions and data. The instructions and data are configured to cause one or more processing units to implement the functions outlined in the claims. That is, the communication device includes a transmission medium having signals indicative of information to perform the disclosed functions. At a first time, a transmission medium included in the communication device may include a first portion of information to perform the disclosed function, and at a second time, the transmission medium included in the communication device may include a second portion of information to perform the disclosed function.

The previous description of the disclosure is provided to enable any person skilled in the art to make or use the disclosure. Various modifications to the disclosure will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not intended to be limited to the examples and designs described herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims (47)

1. A method for wireless communication, comprising:

obtaining, by a location server via a common positioning protocol, positioning information for a target device, the location server residing on one of a plurality of possible entities and using the common positioning protocol regardless of where the location server resides, and the target device being one of the plurality of possible entities; and

determining, by the location server, location information about the target device.

2. The method of claim 1, wherein the positioning information comprises measurements of at least one reference source, and wherein the location information comprises a location estimate for the target device determined by the location server based on the measurements.

3. The method of claim 1, wherein the positioning information indicates a location of the target device, and wherein the location information comprises assistance data determined by the location server based on the positioning information.

4. The method of claim 1, wherein the positioning information comprises measurements of reference sources receivable at a location of the target device, and wherein the location information comprises assistance data determined by the location server based on the positioning information.

5. The method of claim 1, wherein the location information comprises assistance data, and wherein the positioning information comprises measurements obtained based on the assistance data.

6. The method of claim 1, wherein the positioning information for the target device comprises measurements of at least one signal from at least one satellite, or at least one base station, or at least one terminal, or the target device, or a combination thereof.

7. The method of claim 1, wherein the location server resides in a network entity.

8. The method of claim 1, wherein the location server is co-located with the target device.

9. The method of claim 1, wherein the positioning information for the target device is obtained by a positioning unit residing on one of a second plurality of possible entities, the target device being one of the second plurality of possible entities.

10. The method of claim 9, further comprising:

communicating, by the location server, with the positioning unit via the common positioning protocol.

11. The method of claim 9, further comprising:

exchanging capabilities, or assistance data, or location information, or a combination thereof, with the positioning unit via the common positioning protocol.

12. An apparatus for wireless communication, comprising:

means for obtaining, by a location server via a common positioning protocol, positioning information for a target device, the location server residing on one of a plurality of possible entities and using the common positioning protocol regardless of where the location server resides, and the target device being one of the plurality of possible entities; and

means for determining, by the location server, location information about the target device.

13. The apparatus of claim 12, wherein the positioning information for the target device is obtained by a positioning unit residing on one of a second plurality of possible entities, the target device being one of the second plurality of possible entities.

14. The apparatus of claim 13, further comprising:

means for exchanging capabilities, or assistance data, or location information, or a combination thereof, with the positioning unit via the common positioning protocol.

15. An apparatus for wireless communication, comprising:

at least one processing unit configured to: obtaining, by a location server via a common positioning protocol, positioning information for a target device, and determining, by the location server, the location information for the target device, the location server residing on one of a plurality of possible entities and using the common positioning protocol regardless of where the location server resides, and the target device being one of the plurality of possible entities.

16. The apparatus of claim 15, wherein the positioning information for the target device is obtained by a positioning unit residing on one of a second plurality of possible entities, the target device being one of the second plurality of possible entities.

17. The apparatus as recited in claim 16, said at least one processing unit configured to: exchanging capabilities, or assistance data, or location information, or a combination thereof, with the positioning unit via the common positioning protocol.

18. A computer-readable medium, comprising:

code for causing at least one computer to cause a location server to obtain positioning information about a target device via a common positioning protocol, the location server residing on one of a plurality of possible entities and using the common positioning protocol regardless of where the location server resides, and the target device being one of the plurality of possible entities, an

Code for causing the at least one computer to cause the location server to determine location information about the target device.

19. A method for wireless communication, comprising:

sending positioning information about a target device to a location server via a common positioning protocol, the location server residing on one of a plurality of possible entities and using the common positioning protocol regardless of where the location server resides, and the target device being one of the plurality of possible entities; and

receiving location information about the target device from the location server.

20. The method of claim 19, wherein the sending the positioning information and the receiving the location information are performed by the target device.

21. The method of claim 19, wherein the sending the positioning information and the receiving the location information are performed by a positioning unit external to the target device.

22. The method of claim 19, further comprising:

measuring, at the target device, at least one signal from at least one reference source to obtain measurements for the target device, the at least one reference source comprising at least one satellite, or at least one base station, or at least one terminal, or a combination thereof, and the positioning information comprising the measurements.

23. The method of claim 19, further comprising:

measuring a signal from the target device at a positioning unit to obtain a measurement of the target device, the positioning unit being external to the target device, and the positioning information comprising the measurement.

24. An apparatus for wireless communication, comprising:

means for sending positioning information regarding a target device to a location server via a common positioning protocol, the location server residing on one of a plurality of possible entities and using the common positioning protocol regardless of where the location server resides, and the target device being one of the plurality of possible entities; and

means for receiving location information about the target device from the location server.

25. The apparatus of claim 24, further comprising:

means for measuring, at the target device, at least one signal from at least one reference source to obtain a measurement for the target device, the at least one reference source comprising at least one satellite, or at least one base station, or at least one terminal, or a combination thereof, and the positioning information comprising the measurement.

26. The apparatus of claim 24, further comprising:

means for measuring a signal from the target device at a positioning unit to obtain a measurement of the target device, the positioning unit being external to the target device, and the positioning information comprising the measurement.

27. A method for wireless communication, comprising:

exchanging a plurality of positioning messages transmitted together in a message transaction; and

performing positioning based on the plurality of positioning messages.

28. The method of claim 27, wherein the exchanging the plurality of positioning messages comprises sending the plurality of positioning messages as linked messages or in a single container message.

29. The method of claim 27, wherein the exchanging the plurality of positioning messages comprises receiving the plurality of positioning messages sent as linked messages or in a single container message.

30. The method of claim 27, wherein the plurality of positioning messages are sent by a target device with a mobile originated location request (MO-LR) message to initiate positioning.

31. The method of claim 27, wherein the plurality of positioning messages are sent by a location server and comprise a first positioning message carrying assistance data and a second positioning message requesting location information.

32. The method of claim 27, wherein the plurality of positioning messages are sent to a location server and comprise a first positioning message requesting assistance data and a second positioning message carrying measurements.

33. The method of claim 27, wherein each of the plurality of positioning messages is one of a plurality of message types, the plurality of message types including a request capability message type, a provide capability message type, a request assistance data message type, a provide assistance data message type, a request location information message type, and a provide location information message type.

34. The method of claim 27, wherein the plurality of positioning messages comprises positioning messages of at least two message types.

35. An apparatus for wireless communication, comprising:

means for exchanging a plurality of positioning messages transmitted together in a message transaction; and

means for performing positioning based on the plurality of positioning messages.

36. The apparatus of claim 35, wherein the means for exchanging the plurality of positioning messages comprises means for sending the plurality of positioning messages as linked messages or in a single container message.

37. The apparatus of claim 35, wherein the means for exchanging the plurality of positioning messages comprises means for receiving the plurality of positioning messages sent as linked messages or in a single container message.

38. The apparatus of claim 35, wherein the plurality of positioning messages are sent by a target device with a mobile originated location request (MO-LR) message to initiate positioning.

39. A method for wireless communication, comprising:

exchanging positioning messages comprising a first part and a second part for a specific transaction type, the first part comprising first information for positioning defined by a first organization and the second part comprising second information for positioning defined by a second organization; and

performing positioning based on the positioning message.

40. The method of claim 39, wherein the exchanging the positioning messages comprises sending the positioning messages from a target device to a location server or from the location server to the target device.

41. The method of claim 39, wherein the exchanging the positioning messages comprises receiving the positioning messages by a location server from a target device or by the target device from the location server.

42. The method of claim 39, wherein the first organization comprises "third generation partnership project" (3GPP), and wherein the second organization comprises "third generation partnership project 2" (3GPP2), or Open Mobile Alliance (OMA), or Internet Engineering Task Force (IETF), or Institute of Electrical and Electronics Engineers (IEEE), or a network operator, or an equipment vendor.

43. An apparatus for wireless communication, comprising:

means for exchanging positioning messages comprising a first part and a second part for a specific transaction type, the first part comprising first information for positioning defined by a first organization and the second part comprising second information for positioning defined by a second organization; and

means for performing positioning based on the positioning message.

44. The apparatus of claim 43, wherein the means for exchanging the positioning messages comprises means for sending the positioning messages from a target device to a location server or from the location server to the target device.

45. The apparatus of claim 43, wherein the means for exchanging the positioning messages comprises means for receiving the positioning messages by a location server from a target device or by the target device from the location server.

46. A method for wireless communication, comprising:

exchanging measurement data units applicable to a plurality of positioning methods, each of the plurality of positioning methods being associated with a different set of applicable measurement data units; and

performing a positioning based on the exchanged measurement data units and according to a positioning method, which is one of the plurality of positioning methods.

47. A method for wireless communication, comprising:

exchanging assistance data units applicable for a plurality of positioning methods, each positioning method of the plurality of positioning methods being associated with a different set of applicable assistance data units; and

performing a positioning based on the exchanged assistance data units and according to a positioning method, the positioning method being one of the plurality of positioning methods.