Abstract: Techniques for supporting location services are disclosed. In an aspect, a generic location session between a terminal and a location server may be established for a particular duration or until the generic location session is terminated by a trigger condition. Parameters related to the generic location session may be exchanged between the terminal and the location server during session establishment. Thereafter, the terminal and the location server may engage in one or more positioning activities at any time during the generic location session. Each positioning activity may be of any type supported by the terminal and the location server. The generic location session can be initiated by either the terminal or the location server. In one design, one entity (e.g., the location server) may initiate the generic location session, and the other entity (e.g., the terminal) may send an end message to terminate the generic location session.

Abstract: Techniques to support positioning for access points and terminals in WLANs and other wireless networks are described. In one aspect, WLAN positioning is supported with Secure User Plane Location (SUPL). A terminal obtains measurements for an access point in a WLAN and/or receives measurements made by the access point for the terminal. The terminal determines WLAN AP information for the access point and/or the terminal based on the measurements and sends the WLAN AP information to a SUPL Location Platform (SLP). The SLP determines a location estimate for the terminal based on the WLAN AP information. In another aspect, the terminal receives supported network information from the SLP. The terminal obtains network measurement information (e.g., measurements) for a radio access network and determines which particular network measurement information to send based on the supported network information. The terminal sends network measurement information permitted by the supported network information to the SLP.

Abstract: An example method includes: obtaining a location of a reference mobile terminal; and either: (1) sending, to a target mobile terminal, the location of the reference mobile terminal and a trigger parameter associated with a trigger event, the trigger parameter defining a moving geographical target area; and receiving an indication that the trigger event has occurred; or (2) determining a location of the moving geographical target area; determining a location of the target mobile terminal relative to the moving geographical target area; and determining whether the trigger event has occurred; where the trigger event comprises the target mobile terminal being inside the moving geographical target area, being outside the moving geographical target area, entering the moving geographical target area, and/or leaving the moving geographical target area.

Abstract: Techniques for supporting triggered location services are described. In one design, at least one location related measurement for a terminal may be obtained and used to detect for a trigger event. For an equidistance triggered service, a trigger event may be declared if the distance traveled by the terminal exceeds a predefined distance. For a relative terminal to terminal triggered service, a trigger event may be declared if the terminal is inside or outside, or enters, or leaves a moving geographical target area defined by a reference terminal. For a velocity triggered service, a trigger event may be declared if the maximum velocity of the terminal exceeds a predefined velocity. For a time-distance-velocity combination triggered service, a trigger event may be declared based on distance traveled by the terminal, velocity of the terminal, and time since the last report. For all services, a report may be sent if a trigger event has occurred.

Abstract: Techniques for supporting network-initiated location services for a terminal are described. A location server may not be able to reach the terminal in a normal manner in certain operating scenarios. The terminal may perform registration with the location server if the terminal determines that it may not be reachable by the location server in the normal manner. For the registration, the terminal may identify itself to the location server, instigate mutual authentication of the terminal and the location server, and provide an Internet Protocol (IP) address of the terminal to the location server. The terminal may perform registration with the location server whenever the IP address changes and/or periodically whenever a timer expires. The terminal may set the timer to a value received from the location server. The location server may use the IP address to send messages to the terminal for network-initiated location services.

Abstract: Techniques to support positioning for terminals in Secure User Plane Location (SUPL) are described. A SUPL Enabled Terminal (SET) may receive supported network information from a SUPL Location Platform (SLP), which is a location server in SUPL. The supported network information may indicate one or more radio access networks supported by the SLP, one or more types of measurement supported by the SLP, and/or information that the SET is allowed to send to the SLP. The SET may send network measurement information for a supported radio access network to the SLP. The network measurement information may include cell and/or access point (AP) information for one or more access points or base stations in the supported radio access network. The SLP may determine a location estimate for the SET based on the network measurement information from the SET.

Abstract: Techniques for selecting positioning protocols consistent with the capabilities of the location server in a Secure User Plane Location (SUPL) based service are described. The SUPL Location Platform (SLP) transmits the service capabilities of the SLP, such as the positioning protocol capabilities of the SLP. The SLP transmits its capabilities of the SLP in an initiation message to the SUPL enabled terminal (SET) or after receiving an initiation message from the SET. The SET may transmit a positioning initiation message and the SLP and SET communicate to determinate one or more position estimates for the SET. The SET may include in the positioning initiation message a positioning protocol positioning message that is consistent with the SLP service capabilities.

Abstract: Techniques for selecting positioning protocols consistent with the capabilities of the location server in a Secure User Plane Location (SUPL) based service are described. The SUPL Location Platform (SLP) transmits the service capabilities of the SLP, such as the positioning protocol capabilities of the SLP. The SLP transmits its capabilities of the SLP in an initiation message to the SUPL enabled terminal (SET) or after receiving an initiation message from the SET. The SET may transmit a positioning initiation message and the SLP and SET communicate to determine one or more position estimates for the SET. The SET may include in the positioning initiation message a positioning protocol positioning message that is consistent with the SLP service capabilities.

Abstract: The subject matter disclosed herein relates to a system and method for determining indoor context information relating to a location of a mobile device. Indoor context information may be utilized by a mobile device or a network element to obtain an estimate of a location of the mobile device within an indoor environment.

Abstract: Techniques for sending and receiving broadcast information are described. In an aspect, broadcast metadata may be generated for broadcast information and may include location and time criteria used by terminals to filter the broadcast information. Each location and time criterion may include (i) a location criterion given by a target location and a presence or absence requirement and (ii) a time criterion given by a time period in which the location criterion applies. A terminal may receive the broadcast metadata prior to or with the broadcast information, obtain location and time criteria from the broadcast metadata, and filter the broadcast information based on the location and time criteria. The terminal may evaluate each location and time criterion by determining its location within a specified time period and determining whether its location is within or outside a specified target location, as indicated by the presence or absence requirement.

Abstract: Systems and techniques to determine an approximate location for a mobile device using historic location information. In an aspect, a SUPL Location Platform (SLP), which is a location server in SUPL, may receive data from SUPL Enabled Terminal (SET). The data may include the Multiple Location IDs Parameter. The real time Location ID Parameter may not have a current status. The SLP may determine an approximate position for the SET based on the Multiple Location IDs Parameter data received from the SET. The SLP may then send the approximate position to the SET or a SUPL Agent, or may use the approximate position information in another way.

Abstract: The subject matter disclosed herein relates to a system and method for negotiating a version of Secure User Plane Location (SUPL) between a network entity and a SUPL enabled terminal. In a particular implementation, a SUPL initiation message is transmitted from a network entity to a SUPL entity, where the SUPL initiation message identifies a plurality of SUPL versions capable of supporting a desired service. A response is received from the SUPL entity that is based, at least in part, on an ability of the SUPL entity to support at least one of the plurality of versions.

Abstract: Techniques for supporting location services in a user plane location architecture such as Secure User Plane Location (SUPL) are described. In an aspect, a terminal informs a location server of service capabilities of the terminal. The location server uses the service capabilities to request only location services supported by the terminal and to avoid requesting unsupported location services. The terminal generates a message containing its service capabilities and sends the message via a user plane, e.g., SUPL. The location server receives the message, obtains the service capabilities of the terminal, and stores these service capabilities for future network-initiated location sessions with the terminal. The location server determines whether a location service is supported by the terminal based on the service capabilities of the terminal. The location server communicates with the terminal via the user plane for the location service if supported by the terminal.

Abstract: Techniques for initiating and, if desired, modifying location services for Secure User Plane Location (SUPL) and other location architectures are described. To initiate SUPL service, a SUPL Location Platform (SLP) transmits a SUPL initial session message applicable to any service request to a SUPL enabled terminal (SET) and receives in response the service capabilities of the SET. The SLP selects and requests service from the SET consistent with the service capabilities of the SET. The SET may initiate SUPL service by requesting the service capabilities of the SLP. The SET selects and requests service from the SLP that is consistent with the service capabilities received from the SLP. The SET and SLP communicate to determine a position estimate for the SET. The service may be modified before or while communicating between the SET and the SLP to determine a position estimate for the SET.

Abstract: A method for a server to initiate resynchronization with an access terminal, when synchronization has been lost, that cannot be exploited by attackers is provided. The server may provide the access terminal with a secret key that is only known to the access terminal and the server. The access terminal may store the secret key in a secure storage device to prevent the secret key from being hacked. If the server determines that synchronization has been lost, the server may send a resynchronization message to the access terminal with the secret key attached. The access terminal retrieves the stored secret key from the secure memory device and compares it to the secret key attached to the resynchronization message. If there is a match, the access terminal may initiate a secure communication link with the server to reestablish synchronization.

Abstract: Techniques for querying for information on location sessions in a user plane location architecture are described. In an aspect, a location server may send a query message to a terminal to query for information on active location sessions, e.g., when at least one location session for periodic triggered service or area event triggered service is deemed to be active. The terminal may return a response message containing a list of session identifiers (IDs) for the active location sessions, parameters for the active location sessions, capabilities of the terminal, etc. The location server may compare the information received from the terminal and information stored at the location server. The location server may terminate each location session deemed to be active at only the terminal or only the location server. The location server may restart or terminate each location session having inconsistent parameters at the terminal and the location server.

Abstract: Techniques for supporting location services with a streamlined location service layer are described. In one design, a terminal may receive a location service request from an application that is internal or external to the terminal. The terminal may exchange at least one message with a location server to establish an extended location session of a particular duration via the streamlined location service layer. The terminal can thereafter obtain location service from the location server at any time within the particular duration of the extended location session, e.g., whenever a location request is received from the application. The terminal may obtain location service any number of times and at any time during the extended location session. The terminal or application may emulate a more complex location service based on location information received from all of the times in which location service is obtained by the terminal.

Abstract: The subject matter disclosed herein relates to a system and method for negotiating a version of Secure User Plane Location (SUPL) between a network entity and a SUPL enabled terminal. In a particular implementation, a SUPL initiation message is transmitted from a network entity to a SUPL entity, where the SUPL initiation message identifies a plurality of SUPL versions capable of supporting a desired service. A response is received from the SUPL entity that is based, at least in part, on an ability of the SUPL entity to support at least one of the plurality of versions.

Abstract: Techniques for supporting triggered location services are described. In one design, at least one location related measurement for a terminal may be obtained and used to detect for a trigger event. For an equidistance triggered service, a trigger event may be declared if the distance traveled by the terminal exceeds a predefined distance. For a relative terminal to terminal triggered service, a trigger event may be declared if the terminal is inside or outside, or enters, or leaves a moving geographical target area defined by a reference terminal. For a velocity triggered service, a trigger event may be declared if the maximum velocity of the terminal exceeds a predefined velocity. For a time-distance-velocity combination triggered service, a trigger event may be declared based on distance traveled by the terminal, velocity of the terminal, and time since the last report. A report may be sent if a trigger event has occurred.

Abstract: The subject matter disclosed herein relates to a system and method for negotiating a version of Secure User Plane Location (SUPL) between a network entity and a SUPL enabled terminal. In a particular implementation, a SUPL initiation message is transmitted from a network entity to a SUPL entity, where the SUPL initiation message identifies a plurality of SUPL versions capable of supporting a desired service. A response is received from the SUPL entity that is based, at least in part, on an ability of the SUPL entity to support at least one of the plurality of versions.