RU2389156C2 - Location reporting through secure user plane location (supl) - Google Patents

Abstract

FIELD: information technology.

SUBSTANCE: techniques for supporting periodic and other location services with secure user plane location (SUPL) and other location architectures are described. The techniques can provide position estimates for a SUPL enabled terminal (SET) to a SUPL agent periodically and/or based on trigger events. A home SUPL location platform (H-SLP) receives from the SUPL agent a request for position estimates for the SET. The H-SLP starts a SUPL location session with the SET. For each of at least one reporting event during the location session, the H-SLP obtains a position estimate for the SET and sends the position estimate to the SUPL agent. The position estimate may be derived by the SET and sent to the H-SLP. Alternatively, the position estimate may be derived by the H-SLP based on measurements from the SET.

EFFECT: improved location.

39 cl, 20 dwg, 6 tbl

Description

FIELD OF THE INVENTION

The present invention relates generally to communications, and more particularly to techniques for supporting location services.

BACKGROUND

It is often desirable and sometimes necessary to know the location or position of a wireless device on a network. The terms “location” and “position” are synonymous and are used interchangeably in this document. For example, a user may use a wireless device to browse a website and may select location-dependent content with a mouse. The web server may then query the network for the position of the wireless device. The network may initiate position processing using the wireless device in order to establish the position of the wireless device. The network may then return the position estimate for the wireless device to the web server, which can use this position estimate to provide relevant content to the user. There are many scenarios in which knowing the position of a wireless device is useful or necessary.

A message flow (which can also be called a call flow or procedure) is typically performed to obtain a position estimate for a wireless device and to send this position estimate to a client entity, such as a web server. Various messages are typically exchanged between one or more network entities, a wireless device, and a client entity for a message flow. These messages ensure that each object is provided with relevant information, or that this information can be obtained from another object in order to implement position determination for a wireless device and / or to deliver a position estimate to a client object. However, these messages are added to traffic among various network entities. The additional traffic can be especially large for location services in which a position estimate for a wireless device is periodically provided to a client entity. Messages can also extend the response time to send a position estimate to a client entity.

Therefore, there is a need in the art for techniques for providing location services.

SUMMARY OF THE INVENTION

This document describes techniques for supporting periodic and other location services using Reliable User Plane Location (SUPL) and other location architectures. The techniques may provide position estimates for the SUPL supporting terminal (SET) to the SUPL agent periodically and / or based on triggering events (event actions) or conditions.

In an embodiment, the home SUPL location platform (H-SLP) receives from the SUPL agent a request for location estimates for the SET. H-SLP starts a SUPL location session using SET. For each at least one alert event during the location session, the H-SLP obtains a position estimate for the SET and sends the position estimate to the SUPL agent. The position estimate can be retrieved using SET and sent to the H-SLP. Alternatively, a position estimate may be derived using H-SLP based on measurements from SET. Various details are described below.

Additionally, various aspects and embodiments of the invention are described in detail below.

BRIEF DESCRIPTION OF THE DRAWINGS

Aspects and embodiments of the present invention will become more apparent from the detailed description set forth below, taken in connection with the drawings, in which similar reference symbols are defined, respectively.

1A and 1B show two exemplary network architectures.

2-18 show exemplary message flows for triggered location services.

Fig. 19 shows a block diagram of various objects in Figs. 1A and 1B.

DETAILED DESCRIPTION

The word “exemplary” is used herein to mean “serving as an example, sample, or illustration.” Any embodiment or scheme described herein as “exemplary” need not be construed as preferred or advantageous over other embodiments or schemes.

The techniques described in this document can be used for various wireless networks, for example, CDMA (code division multiple access) networks, TDMA (time division multiple access) networks, FDMA (frequency division multiple access) networks, OFDMA networks ( orthogonal frequency division multiple access), networks supporting a combination of the above technologies, WAN (wide area network) and / or WLAN (wireless local area network) networks, and so on. A CDMA network may implement one or more radio technologies, for example, Broadband CDMA (W-CDMA), cdma2000, and so on. cdma2000 covers IS-2000, IS-856, and IS-95 standards. A TDMA network may implement one or more radio technologies such as Global System for Mobile Communications (GSM), Digital Advanced Mobile Communications System (D-AMPS), and so on. D-AMPS covers IS-136 and IS-54. These various radio technologies and standards are known in the art. W-CDMA and GSM are described in documents from an organization called the Third Generation Partnership Project (3GPP). cdma2000 is described in documents from an organization called "Third Generation Partnership Project 2" (3GPP2). 3GPP and 3GPP2 documents are publicly available.

The techniques may also be used to aid in the discovery of a device that communicates with a wired network that supports IP, such as a network that provides DSL or cable access, and / or can be used to support client devices that communicate using a wired network.

Techniques may also be used for various location architectures, for example, control plane and user plane architectures. The control plane (also called the signal plane) is a device for signaling transfer for higher level applications and is typically implemented using specific network protocols and signaling messages. The user plane is a signaling transfer device for higher-level applications using a user plane unidirectional channel, which is typically implemented using protocols such as User Datagram Protocol (UDP), Transmission Control Protocol (TCP), and Internet Protocol (IP), each which are known in the art. Messages supporting location and positioning services are carried as part of the signaling in the control plane architecture and as part in the user plane architecture. The content of the messages may, however, be the same or similar in both architectures. The techniques can be used for SUPL and preliminary Open Mobile Alliance (OMA) SUPL architectures, 3GPP control plane architectures described in 3GPP TS 23.271, TS 43.059 and TS 25.305, 3GPP2 control plane architecture described in IS-881 and 3GPP2 X.S0002 , the 3GPP2 user plane architecture described in X.S0024, and so on. For clarity, the procedures are described below for SUPL.

1A shows a network architecture 100 configured to provide location services for terminals supporting SUPL (SET). SET is a device that is configured to interact with SUPL supporting entities that support location and location services for SET. For simplicity, only one SET 120 is shown in FIG. 1A. SET 120 may be fixed or mobile and may also be referred to as a mobile station (MS), user equipment (UE), terminal, station, subscriber unit or other terminology. SET 120 may be a cell phone, personal digital assistant (PDA), wireless modem, personal computer, laptop computer, telemetry device, tracking device, and so on. For example, SET 120 can be UE in UMTS (universal mobile communication system) and MS in GSM or cdma2000, a personal computer in an IP-based network, and so on.

SET 120 may include a SUPL agent 122 configured to access SUPL-enabled entities. SET 120 may also be a target SET, which is a SET whose position is requested by the SUPL agent, which may be internal or external to the SET. SET 120 may perform functions, for example, protection of personal information, security, position measurement and position calculation for location services.

SET 120 may interact with communication network 130 for various services, such as voice, packet data, messaging, and so on. SET 120 may also communicate with SUPL-enabled entities via network 130. Network 130 may be wireless, such as a cdma2000 network, a UMTS network, a GSM network, another radio access network (RAN), a WLAN, and so on. The network 130 may also be a wireless network, for example, an IP-based network, a telephone network, a cable network, and so on. SET 120 may also receive signals from one or more satellites 190, which may be part of a global positioning system (GPS), the European Galileo system, the Russian GLONASS system, or another satellite positioning system. SET 120 may measure signals from satellites 190 and / or base stations in network 130 and may receive pseudorange measurements for satellites and network measurements from base stations. Pseudorange measurements can be used to extract position estimates for SET 120.

The SUPL Home Location Platform (H-SLP) 150 is responsible for managing the SUPL service and positioning. SUPL service management may include SET location management and storage, retrieval and modification of the location information of the target SETs.

H-SLP 150 includes a SUPL location center (SLC) 152 and may include a SUPL position center (SPC) 154. SLC 152 performs various functions for location services, coordinates the operation of SUPL and interacts with SET over a user bearer channel the plane. SLC 152 can perform functions to protect personal information, launch, security, support roaming, pricing / billing, service management, position calculation and so on. SPC 154 supports positioning for the SET, is responsible for the messages and procedures used to calculate the position, and supports the delivery of auxiliary data to the SET. SPC 154 can perform functions for security, auxiliary data delivery, link search, position calculation, and so on. The SPC has access to GPS receivers (a core network, possibly global) and receives signals for satellites so that they can provide ancillary data.

A SUPL agent (e.g., SUPL agent 122 or 170) is a function or entity that obtains location information for a target SET. In general, a SUPL agent may be permanently stored in a network entity (e.g., SUPL agent 170) or SET (e.g., SUPL agent 122) or may be external to both the network and the SET. In the case where the SET is a resident SUPL agent, it may or may not access network resources to obtain location information, and, as in SET-based mode, the location and use of resources may not be one-to-one. The SUPL Network Resident Agent can use Mobile Location Services (MLS Apps) to access H-SLP or R-SLP. An MLS application is an application that requests and uses location information. The location information may be any information related to the location, and may contain various types of position estimates (for example, latitude and longitude coordinates, latitude and longitude with an expected estimation error, etc.). MLS covers the interaction between the SUPL agent and H-SLP or R-SLP, while SUPL covers the interaction between H-SLP or V-SLP and SET.

FIG. 1B shows a network architecture 102 that includes a guest / serving network 104, a home network 106, and a requesting network 108. The guest network 104 includes a guest location platform SUPL (V-SLP) 160. The home network 106 includes H-SLP 150, which supports location services and position control. The request network 108 includes a request SLP (R-SLP) 162 that supports location services for SUPL agents. H-SLP 150, V-SLP 160 and R-SLP 162 each each includes an SLC and may include an SPC that operates as described above for FIG. 1A.

The SUPL objects in FIGS. 1A and 1B are described in OMA-AD-SUPL-V2_0-20060619-D, which is entitled "User Reliable Positioning Architecture", Preview Version 2.0, June 2006, which is publicly available from OMA. The network entities in FIGS. 1A and 1B may also be referred to by other names in other networks and other network architectures. For example, in a 3GPP-based network (for example, a UMTS network), the SLC is called the Mobile Network Gateway Center (GMLC), the SPC is called the Mobile Service Center (SMLC), the SET is called the UE, and the SUPL agent is called the LCS client. The functions and signaling performed by the 3GPP entities are similar to those implemented by the corresponding SUPL entities, thereby providing the opportunity for comparable services and capabilities. In general, an SLC may be called a location center, an LCS server, a location server, a mobile positioning center (MPC), and so on. An SPC may be referred to as a position determination object, a position determination center, a position determination object (PDE), and so on.

SUPL may support the following positioning methods (among others):

- Auxiliary GPS (A-GPS) or only an auxiliary SET A-Galileo (A-Galileo),

- A-GPS or only SET based on A-Galileo,

- A-GPS or an auxiliary SET A-Galileo, preferred with an A-GPS or SET A-Galileo based on the fault mitigation mode,

- A-GPS or A-Galileo Auxiliary SET, preferred with A-GPS or A-Galileo Auxiliary SET based on Failover Mode,

- Standalone GPS or standalone Galileo,

- Hybrid

- Improved forward link trilateration (A-FLT),

- Improved Observed Time Difference (EOTD),

- Observed time difference of arrival (OTDOA) and

- Improved cell / sector and cell ID.

For a SET-based mode, the SET position is determined using SET, possibly with auxiliary data from the SPC. For the auxiliary SET mode, the SET position is determined using the SPC, with support (for example, measurement) from the SET. The stand-alone GPS and A-GPS methods extract a position estimate for the SET based on satellite measurements alone and are highly accurate. The hybrid method extracts a position estimate based on both satellite measurements and base station measurements and has high accuracy and high reliability. The A-FLT, EOTD, and OTDOA methods retrieve a position estimate based on base station clock measurements made by SET and have high accuracy. Improved cell / sector and cell identification methods derive a position estimate based on known positions of the cell / sectors of the cellular network and have gross accuracy. For an improved cell / sector method, a position estimate may also be derived based on network measurements, for example, radio signal timing and signal strength. Network-based positioning methods, such as uplink arrival time (U-TOA) and uplink arrival time difference (U-TDOA), can also be supported using specific location solutions. The U-TOA and U-TDOA methods extract a position estimate based on SET clock measurements made by the network and are highly accurate. These various positioning methods are known in the art. The terms "position estimation", "position estimation" and "positioning" are often used interchangeably. The position estimate can be given in coordinates (for example, latitude and longitude) or in the form of a public address and with a possible expected error.

SUPL can support various location services, such as those shown in the table. one.

Table 1 Location service Description Instant Location Service Provide location information (e.g., location of the target SET) instantly when requested Zone Location Related Service Provide location information after a specific event Periodic Location Service Provide numerous settings with location information based on periodic actions Periodic Location Location Service in the Zone Determine location information periodically, but only report when events occur in the zone Historical Location Service Provide location information previously obtained when specific conditions are met

Instant location services may also be referred to as network-initiated, SET-initiated, roaming, roaming-free, and so on. Periodic, with an event in the zone and historical location services are also referred to as periodic, with an event in the zone and, accordingly, triggered historical services. For triggered services, notification of service estimates is determined by an action or action mechanism that indicates when to notify the SUPL agent's SET location. Actions can be determined using the SUPL agent sent to the H-SLP and then sent to the target SET. Periodic actions for a periodically triggered service may include a periodic interval, the number of position alerts and the possible initial time to start the alert. Actions in the case of an event in a zone for a service triggered by an event in a zone can correspond to entering a SET, exiting roaming, or staying in a predetermined geographical area, location of a SET, speed or change in congestion using predetermined thresholds, and so on. For a historically initiated service, a SET may decide to save position / measurement estimates when they are computed / collected to be sent directly to the H-SLP. The SET may send back the previous stored position / measurement estimates when certain predetermined conditions are met. For example, a SET may be temporarily outside the cellular coverage area and may send previous position estimates when it re-enters the cellular coverage area.

Location services can be categorized as shown in the table. 2.

table 2 Location service Description Network Initiated (NI) Services Services that originate from the network with the SUPL agent resident on the network SET Initiated Services (SI) Services that originate from SET with a SUPL agent resident in SET

Network initiated services may also be referred to as terminated by a mobile terminal. Triggered SETs may also be referred to as outgoing from a mobile terminal.

SUPL supports two communication modes between SET and SLP for location in the SPC. Tab. 3 summarizes two communication modes.

Table 3 Communication mode Description Intermediate mode The SPC does not directly communicate with SET, and the SLC acts as an intermediary between SET and SPC Non-intermediate mode SPC has a direct relationship with SET

SUPL supports roaming and no roaming for SET. Tab. 4 summarizes several roaming and non-roaming modes.

Table 4 Roaming / No roaming Description Lack of roaming SET is in the service area of its H-SLP H-SLP Positioning Roaming SET is out of range of its H-SLP, but the H-SLP still provides location functionality V-SLP Positioning Roaming SET is outside the service area of its H-SLP, but V-SLP provides location functionality

As used herein, roaming and lack of roaming are considered with respect to SUPL and not with respect to communication network 130. Network 130 may have a different definition and criteria for roaming and lack of roaming, which are not discussed in this document.

The H-SLP service area is the area in which the H-SLP can provide position estimates for the SET or significant supporting data for the SET without interacting with other SLPs. When the SET is roaming, the H-SLP may provide positioning functionality (eg, positioning and SPC functionality) or may request a V-SLP to provide this positioning functionality.

A set of message flows can be defined for each supported location services. Each message flow can be used for a specific location service and a specific set of conditions, for example, intermediate or non-intermediate, roaming or no roaming initiated by the network or initiated by SET and so on. A particular message flow may be used to obtain the desired location service for the applicable conditions.

For clarity, many exemplary message flows for various location services and conditions are described below. Tab. 5 summarizes the message flows shown in FIGS. 2-18 below. Each row in the table. 5 is for one message flow in the drawings, and “Xs” in the line indicates the conditions applicable to that message flow. For example, the first line indicates that FIG. 2 exists for a periodic location service, an intermediate mode initiated by the network, and in the absence of roaming. A roaming-free message flow is used for the network architecture shown in FIG. 1A. Roaming message flows are used for the network architecture shown in FIG. Many of the SUPL messages in the message flow are described in OMA-TS-ULP-V1_0-20060704-C, entitled "User Plane Location Protocol", preview 1.0, July 2006, and in OMA-TS-ULP- V2_0-20060727-D, entitled "User Plane Location Protocol," Preview Version 2.0, July 27, 2006, which are publicly available from OMA. However, other and / or additional message flows may also be defined for location services.

FIG. 2 shows an embodiment of a message flow 200 for a network triggered periodically called service for a roaming-free auxiliary mode. The SUPL agent 170 requires a position estimate for the target SET 120 and sends a triggered request-response message to determine the location of the mobile location protocol (MLP TLRR) in the H-SLP 150 (step A). H-SLP 150 is an SLP with which SUPL agent 170 is associated. The TLRR MLP message may include a client identifier (ID) for the SUPL agent 170 (client identifier), a mobile station identifier (ms-id) for the target SET 120, and position determination quality (QoP). QoP indicates the quality of the position estimates that are requested, which can be quantized using the accuracy of the position estimates and / or other criteria. The message may also transmit periodic action or other information of the initiating event, for example, the interval of the message and the number of alerts.

H-SLP 150 authenticates the SUPL agent 170 and checks if the agent is authorized

SUPL for the requested location service based on the customer ID. H-SLP 150 also applies personal information protection to SUPL agent 170 based on the identifier of the mobile station. To verify personal information, the H-SLP 150 may check whether the SUPL agent 170 or this type of SUPL agent is allowed to request periodic location information for SET 120, and whether SET 120 needs to be notified of this request, and whether it is allowed to accept or reject the request. The H-SLP 150 then searches for SET 120, verifies that SET 120 is currently roaming-free, and can also verify that SET 120 supports SUPL (step B). H-SLP 150 obtains routing information for SET 120 and uses routing information to send messages to SET (also step B).

H-SLP 150 initiates a SUPL location session for a periodic triggered service using SET 120 by sending a SUPL start message, for example, using active WAP delivery (wireless application protocol), SMS action (short message service), or UDP / IP (step C) . The SUPL start message may include a session identifier (session id), an action type indicator, an intermediate / non-intermediate mode indicator (SLP mode), a proposed position determination method (a position determination method), QoP, a key identifier (key id), a message authentication code (MAC) and / or other information. The session ID includes an ID of a SET session selected by SET 120 associated with an SLP session ID selected by H-SLP 150. The session ID is used to determine this SUPL session. Multiple concurrent SUPL sessions can be supported by both H-SLP 150 and SET 120 with different session IDs. For a message flow 200, an action type indicator indicates a periodic triggered service as a requested location service, and an intermediate / non-intermediate mode indicator indicates an intermediate mode. The key ID defines the main MAC key used to verify the MAC and authenticate the SUPL start message. The SUPL start message may also include a notification element if the result of the personal information protection check at step A indicates that a check notification is necessary in the target SET 120. The H-SLP 150 also calculates and stores a hash of the SUPL start message prior to sending the message to SET 120 .

SET 120 receives the SUPL start message from the H-SLP 150 and either connects to the packet data network itself if SET is not already connected or does not establish a circuit switched connection (step D). SET 120 may determine whether the SUPL start message is true based on the key Id if these parameters are included in the message and are supported by SET.

SET 120 evaluates notification rules and follows appropriate actions. SET 120 also checks the intermediate / non-intermediate mode indicator to determine if the H-SLP 150 is using intermediate or non-intermediate mode. In message flow 200, the intermediate mode is used, and SET 120 establishes a reliable IP connection to H-SLP 150 using the H-SLP address that is provided by SET to the home network. SET 120 then sends an initial SUPL triggered message to start a periodic triggered session with H-SLP 150. This message may include session ID, location ID (lid), SET 120 capabilities, random SUPL start message data (Ver), and so on. . The location ID provides cellular information for SET 120. SET capabilities may include positioning methods supported by SET 120 (eg, auxiliary A-GPS SET, A-GPS based SET and so on), positioning protocols supported by SET 120 ( for example, LCS radio resource protocol (RRLP) in 3GPP, radio resource management (RRC) in 3GPP, TIA-801 and so on) and / or other information. SET 120 sends the initial SUPL triggered message, even if the proposed position determination method included in the SUPL start message is not among the position determination methods supported by SET.

H-SLP 150 receives the initial SUPL triggered message and can compare the received random data with the stored random data to determine if the SUPL start message was received correctly. H-SLP 150 adopts a positioning method to utilize a periodic triggered session, considering the SET capabilities included in the initial SUPL triggered message. H-SLP 150 then sends to SET 120 a SUPL triggered response message that includes a session ID, a selected positioning method (positioning method), and periodic actions (step F). Alternatively, the H-SLP 150 may send a list of supported positioning methods (to which priorities may or may not be assigned) in step C, and SET 120 may choose one of the supported positioning methods in step E. In any case, after step F, SET 120 and H-SLP 150s can disconnect a reliable IP connection. H-SLP 150 sends an MLP Location Alert Response Response (TLRA) message to inform SUPL agent 170 that the initiated location request has been accepted (step G). This message may include a request ID (req_id), which must be used as a transaction ID for the entire duration of the periodic initiated session. The request ID is used for the MLP between the SUPL agent 170 and the H-SLP 150, and the session ID is used for the SUPL between the SET 120 and the H-SLP 150.

Steps A through G are creation steps for a periodic triggered service. Step C initiates and notifies SET 120 of the SUPL session. Stage F completes the initiation phase and begins the alert phase. The location information for SET 120 may therefore be communicated according to periodic actions determined in the installation steps and sent out in step F.

When the first position estimate is appropriate, as indicated by periodic actions, SET 120 independently connects to the packet data network if it is not already connected or does not establish a connection with circuit switched data. SET 120 then sends a SUPL POS INIT message (start of SUPL POS) to initiate a positioning session (eg, a positioning protocol session in RRLP, RRC or TIA-S01) using the H-SLP 150 (step H). This message may include session ID, location ID, and / or other information. SET 120 may provide a network measurement alert (NMR) defined for the radio technology that is being used. For example, the NMR may include arrival time (TA) and / or received signal strength (RXLEV) for GSM and may include other measurements for other radio technologies. SET 120 may also provide its position, if available. SET 120 may also request auxiliary data, for example, using the requested auxiliary data element in a SUPL POS INIT message and may then exchange messages with the H-SLP 150 to download the requested auxiliary data from SET. The auxiliary data may be any data that is useful for position determination and may depend on position determination methods. The auxiliary data may contain almanac and ephemeris data for determining the position of the A-GPS and may contain any data for other methods of determining the position.

H-SLP 150 receives the SUPL POS INIT message and determines if an appropriate position estimate is available. An appropriate position estimate is a position estimate that satisfies a certain QoP. If the H-SLP 150 can calculate the appropriate position estimate (for example, the cell id based on the position estimate) based on the information included in the SUPL POS INIT message, then the H-SLP 150 can go directly to step J and not connect to the line in the SUPL session POS (or positioning session) in step I. Otherwise, the H-SLP 150 and SET 120 connect to the line in the SUPL POS session and can exchange several consecutive positioning procedure messages (step I). H-SLP 150 and SET 120 can use the SUPL POS message to exchange position determination procedures (RRLP / RRC / TIA-801) used to calculate the position estimate for the SET. For the SET auxiliary mode, the H-SLP 150 can calculate the position estimate based on the position determination measurements received from SET 120. For the SET mode, the SET 120 can calculate the position estimate based on the support received from the H-SLP 150. In any case, if a corresponding position estimate is available, the H-SLP 150 sends an MLP location initiated message (TLREP) to the SUPL agent 170, which includes the requested ID and the position result (posresult). A position result may include a position estimate, a date and time for position estimation, a position determination method used to extract a position estimate, and / or other information. SET 120 can disconnect a reliable IP connection in H-SLP 150 after step I.

A second position estimate can be obtained and communicated in steps K through M, which correspond to steps H through, respectively, J. Each subsequent position estimate can be obtained and communicated in a similar way. The last position estimate was obtained and reported in steps N through P. After the result of determining the last position was reported to the SUPL agent 170 in step P, the H-SLP 150 ends the periodic initiated session that begins in step C by sending a SUPL END message ( ending SUPL) in SET 120 (step Q).

In the message stream 200, the H-SLP 150 may set the timer ST2 when sending a SUPL INIT message in step C and may terminate the session if the initial initiated SUPL message is not received from SET 120 preceding the end of the timer ST2. Similarly, SET 120 may set a timer UT1 when sending an initial initiated SUPL message in step E, and may terminate a session if the initiated SUPL response message is not received from the H-SLP 150 prior to the end of the timer UT1. SET 120 may also set the UT2 timer when sending a SUPL POS INIT message and may terminate the session if no response is received from the H-SLP 150 prior to the end of the UT2 timer. Timers can be set to any suitable value.

Message flow 200 may also be used for (out of band) event triggered location determination. Message flow 200 may also be used for all positioning methods. For the A-GPS SET based mode, there is no need for GPS assist data from the H-SLP 150, and SET 120 autonomously calculates a position estimate using the GPS assist data currently available in SET. A simpler message stream can be used for A-GPS SET based mode.

FIG. 3 shows an embodiment of a message flow 300 for a network-initiated periodically called service for a roaming-free intermediate mode based on A-GPS SET. Steps A through G of the initial setup in message flow 300 are the same as steps A through G in message flow 200. When the first position estimate is appropriate, SET 120 calculates the position estimate without interacting with the H-SLP 150 and sends the position determination result in the SUPL REPORT message to the H-SLP (step H). The H-SLP 150 sends the position assessment result in the MLP TLREP message to the SUPL agent 170 (step I). Each subsequent position assessment can be obtained and communicated in a similar way. If SET 120 wants updated auxiliary data, then SET sends a SUPL POS INIT message (step L) and connects to the line in the SUPL POS session using H-SLP 150 to receive the auxiliary data (step M). Steps L and M are always executed when SET 120 requires updated auxiliary data. After the last position determination result is reported to the SUPL agent 170 in step O, the H-SLP 150 ends the periodic initiated session by sending a SUPL END SUPL message to SET 120 (step P).

4 shows an embodiment of a message flow 400 for a network-initiated periodic called roaming service with position determination using V-SLP in intermediate mode. Steps A through E of message flow 400 are similar to steps A through E of message flow 200 in FIG. However, in step B of the message flow 400, the H-SLP 150 determines that SET 120 is moving. The H-SLP 150 receives the initial SUPL triggered message from SET 120 in step E and determines the V-SLP 160 based on the location ID included in the received message or some other device. The H-SLP 150 then sends to the V-SLP 160 a Roaming Location Protocol SUPL Roaming Location Alert Request (RLP TSRLRR) message that includes an initial SUPL triggered message (step F). RLP TSRLRR message informs V-SLP 160 that target SET 120 will begin the SUPL position determination procedure. V-SLP 160 selects a positioning method by considering the SET capabilities included in the initial SUPL triggered message. V-SLP 160 indicates its readiness for the SUPL positioning procedure by sending a SUPL triggered response message in a SUPL RLP roaming location triggered response message (RLP TSRLRA) to H-SLP 150 (step G). H-SLP 150 sends a SUPL triggered response message that includes a session ID and a selected positioning method to SET 120 (step H). H-SLP 150 also sends an MLP TLRA message to inform SUPL agent 170 that the request sent in step A has been accepted.

For a first position estimate, SET 120 sends a SUPL POS INIT message to H-SLP 150 to start a positioning session using V-SLP 160 (step J). If the SUPL POS INIT message contains an appropriate position estimate, then the H-SLP 150 proceeds directly to step N. Otherwise, the H-SLP 150 sends the SUPL POS INTT message to the normal roaming SUPL RLP (RLP SSRP) message to the V-SLP 160 (step K ) V-SLP 160 may go directly to step M and not connect to the line in the SUPL POS session if the corresponding position estimate can be calculated based on the information received in the SUPL POS INIT message. Otherwise, the V-SLP 160 and SET 120 are connected to the line in the SUPL POS session and can exchange several consecutive positioning procedure messages that can be tunneled over the RLP through the H-SLP 150 (step L). V-SLP 160 or SET 120 calculate a position estimate. V-SLP 160 then sends to the H-SLP 150 a SUPL alert message that includes a session ID and a position estimate (step M). The H-SLP 150 then sends the MLP TLREP message to the SUPL agent 170, which contains the request ID and position estimate (step N). Each subsequent position assessment can be obtained and communicated in a similar way. After notifying the result of the last position, the H-SLP 150 ends the periodic initiated session by sending the SUPL end message to SET 120 (step Y).

5 shows an embodiment of a message flow 500 for a network-initiated periodic called roaming service with position determination using H-SLP in an intermediate mode. Steps A through I of message flow 500 are similar to steps A through I of message flow 400 in FIG. However, the H-SLP 150 sends an RLP TSRLRR message to the V-SLP 160 that the periodic initiated session is called using the H-SLP (step F), and selects a positioning method for the periodic initiated session (step H).

For a first position estimate, SET 120 sends a SUPL POS INIT message to H-SLP 150 to start a positioning session using H-SLP. H-SLP 150 may send an RLP SRLIR message to V-SLP 160 to obtain a rough determination of the position of SET 120 based on the location ID received in step J (step K). V-SLP 160 can translate the location ID into a rough position determination and returns the result in the RLP SRLIA message to H-SLP 150 (step L). The H-SLP 150 may use coarse positioning as the final position estimate, if accurate enough, or may use coarse positioning to provide auxiliary data to send to SET 120 in step M. H-SLP 150 and SET 120 can connect to the line in a SUPL POS session to obtain a more accurate position estimate for SET (step M). H-SLP 150 then sends the position estimate in the MLP TLREP message to SUPL agent 170 (step N). Each subsequent position assessment can be obtained and communicated in a similar way. After notifying the result of the last position, the H-SLP 150 ends the periodic initiated session by sending the SUPL end message to SET 120 (step Y).

6 shows an embodiment of a message flow 600 for a network periodically called SET service for a roaming-free auxiliary mode. SUPL agent 122 residing in SET 120 (as shown in FIGS. 1A and 1B) receives a request for a periodic triggered service from an application running in SET. SET 120 connects to a packet data network or establishes a circuit switched data connection (step A). SUPL Agent 122 uses the default address provided by the home network to establish a reliable IP connection with the H-SLP 150, and sends the initial SUPL initiated message to start the SUPL session using the H-SLP (step B). This message may include session ID, SET capabilities, action type indicator, and location ID. The H-SLP 150 verifies that SET 120 is not currently a roaming SUPL, selects a positioning method consistent with the capabilities of the SET, and determines routing information for SET 120 (step C). H-SLP 150 then sends to SET 120 a SUPL triggered response message that contains a session ID, a method for determining the position, but no H-SLP address, to indicate to SET that a new connection will not be established (step D). SET 120 and H-SLP 150 can disconnect a reliable IP connection.

For a first position estimate, SET 120 sends a SUPL POS INIT message to start a positioning session using the H-SLP 150 (step E). This message may include session ID, SET capabilities, location ID, NMR, position estimation, and so on. SET 120 may also set the requested auxiliary data element in the SUPL POS INIT message. If an appropriate position estimate is available, then the H-SLP 150 proceeds directly to step G and does not connect to the line in the SUPL POS session. Otherwise, SET 120 and H-SLP 150 may exchange several consecutive messages of the position determination procedure and either H-SLP or SET calculates a position estimate (step F). The H-SLP 150 then sends to SET 120 a SUPL alert message that includes a session ID and a position estimate (step G). For an A-GPS SET based mode, steps E through G can be omitted, and SET 120 can autonomously calculate a position estimate based on GPS assist data available in the SET. Each subsequent position assessment can be obtained and communicated in a similar way. After receiving the result of the last position, SET 120 ends the periodic initiated session by sending the SUPL end message to the H-SLP 150 (step N).

7 shows an embodiment of a message flow 700 for a network-initiated periodically called service for a roaming-free non-roaming mode. Message flow 700 includes all steps of message flow 200 in FIG. 2 and further includes additional steps for interaction between SLC 152 and SPC 154 in H-SLP 150. SUPL agent 170 sends an MLP TLRR message to H-SLC 152 (step A). The H-SLC 152 verifies that SET 120 is not currently moving and obtains routing information for the SET (step B). The H-SLC 152 requests a service for a periodic initiated session from the H-SPC 154 (step C). The H-SPC 154 grants or denies the request and reports, respectively, the H-SLC 152 (also step C).

H-SLC 152 initiates a periodic initiated session using SET 120 (step D). SET 120 independently connects to a packet data network or establishes a circuit-switched data connection (step E) and starts a periodic initiated session using H-SLP 150 (step F). For authentication in non-intermittent mode, SET 120 includes this case of SET and id 2 of the key in the initial SUPL initiated message sent to the H-SLC 152 in step F. The key id 2 corresponds to the main key PP2_SPC used to generate the PSK_SPC key, which is used to PSK-TLS session between the H-SPC 154 and SET 120. The H-SLC 152 uses the key id 2 and this SET case to create the key to use for mutual authentication of the H-SPC and SET. The H-SLC 152 routes the generated key to the H-SPC 154 via an intercom (step G). The H-SLC 152 selects a positioning method for a periodic triggered session and sends a SUPL triggered response message that contains a session ID, a positioning method, and an H-SPC address to SET 120 (step H). The H-SLC 152 also informs the SUPL agent 170 that the request has been accepted (step I).

For a first position estimate, SET 120 sends a SUPL POS INIT message to start a positioning session using the H-SPC 154 (step J). SET 120 and H-SPC 154 can exchange position determination procedure messages and calculate a position estimate for SET (step K). The H-SPC 154 then sends the position estimate via intercom to the H-SLC 152 (step L), which in turn sends the position determination result to the SUPL agent 170 (step M). Each subsequent position assessment can be obtained and communicated in a similar way.

The H-SPC 154 reports the end of the periodic triggered service via intercom in step T. After announcing the result of the last position, the H-SPC 154 ends the periodic triggered session by sending the SUPL end message to SET 120 (step V).

For a service triggered by an event in a service area, SET 120 can store events in the service area, continuously update its position and determine if an event has occurred in the service area based on its current position. For simplicity, message flows exist for cases in which a single event action in a service area ends a session initiated by a service area event. In general, events in the service area can take place any number of times before the end of a session initiated by an event in the service area.

FIG. 8 shows an embodiment of a message flow 800 for a network triggered periodically called service for a roaming-free auxiliary mode. Steps A through G of the message flow 800 are similar to steps A through G of the message flow 200 in FIG. with the following differences. The SUPL agent 170 requests the location information of the event in the zone in the MLP TLRR message sent to the H-SLP 150 in step A. The H-SLP 150 initiates the zone event initiating session using SET 120 by sending the SUPL INIT message using the action type indicator set with an event in the zone in step C. The H-SLP 150 may include determining the zone of the event in a SUPL triggered response message sent to SET 120 in step F.

When the first position estimate is appropriate, as indicated by the zone event action mechanism in SET 120, the SET sends a SUPL POS INIT message to start a position determination session using the H-SLP 150 (step H). H-SLP 150 and SET 120 can connect to the line in the SUPL POS session and receive a position estimate for the SET (step I). If the position estimate is calculated using the H-SLP 150, then the H-SLP sends the position estimate in the SUPL alert message to SET 120 (step J). SET 120 compares the position estimate with the event area and determines whether the event triggering condition is met (step K). In this example, the zone event is not triggered in step J. Steps H through K are repeated each time the mechanism of the events in the zone in SET 120 indicates that a new position estimate is to be achieved. In this example, the zone event is triggered in step S. SET 120 then sends a SUPL alert message, which includes the session ID and position estimate, to the H-SLP 150 (step T). H-SLP 150 sends a position estimate in the MLP TLREP message to SUPL agent 170 (step U). H-SLP 150 ends the session triggered by an event in the zone by sending a SUPL end message to SET 120 (step V).

Message stream 800 may be used for various positioning methods. However, certain steps in message flow 800 may be omitted for some positioning methods. For example, steps I, M, and Q for SUPL POS sessions may be omitted for cell id based on position determination methods. Steps J, N, and R for sending position estimates to SET 120 may be performed if position estimates are computed in H-SLP 150, for example, for auxiliary modes based on A-GPS SET and cell id. Steps H through R, with the exception of steps K and O, can be omitted for the A-GPS SET based mode where no GPS auxiliary data is needed from the network and no interaction with the H-SLP 150 is required to calculate the position estimate. For the A-GPS SET based mode, steps H and I can be performed whenever interaction with the H-SLP 150 is necessary to update GPS assist data.

FIG. 9 shows an embodiment of a message flow 900 for a network triggered event triggered in a coverage area roaming service with V-SLP positioning in an intermediate mode. Steps A through I of message flow 900 are similar to steps A through I of message flow 400 in FIG. 4, except for this event-triggered service in the service area (instead of the periodic triggered service) that is requested in steps A and C. H-SLP 150 may include determining a zone event in a SUPL triggered response message sent to SET 120 in step H.

For a first position estimate indicated by an event-triggered event in the service area of the device in SET 120, steps J through M are performed in the same manner as steps J through M in message flow 400. If the position estimate is calculated in the V-SLP 160 or H-SLP 150, then the H-SLP 150 sends the position estimate in the SUPL alert message to SET 120 (step N). SET 120 compares the position estimate with the zone event and determines whether the condition for triggering the event is fulfilled (step O). Steps J to N are repeated whenever the mechanism of action of events in the zone in SET 120 indicates a new position estimate to be obtained. When a zone event is triggered in step AA, SET 120 sends a SUPL alert message that contains the session ID and position estimate to H-SLP 150 (step BB). The H-SLP 150 sends the position estimate to the SUPL agent 170 (step CC) and ends the session event triggered by sending a SUPL END message to SET 120 (step DD).

10 shows an embodiment of a message flow 1000 for a network triggered event triggered in a coverage area roaming service with H-SLP positioning in an intermediate mode. Steps A through I of the message flow 1000 are similar to steps A through I of the message flow 500 in FIG. 5, with the exception of this event-triggered service coverage area (instead of the periodic triggered service), which is requested in steps A through C. H-SLP 150 may include determining a zone event in a SUPL triggered response message sent to SET 120 in step H.

For a first position estimate indicated by an event-triggered event in the service area of the device in SET 120, steps J through M are performed in the same manner as steps J through M in message flow 500. If the position estimate is calculated in the H-SLP 150 or V-SLP 160, then the H-SLP 150 sends the position estimate in the SUPL alert message to SET 120 (step N). SET 120 compares the position estimate with the zone event and determines whether the condition for triggering the event is fulfilled (step O). Steps J to N are repeated whenever the mechanism of action of events in the zone in SET 120 indicates a new position estimate to be obtained. When a zone event is triggered in step AA, SET 120 sends a SUPL alert message that contains the session ID and position estimate to H-SLP 150 (step BB). The H-SLP 150 forwards the position estimate to the SUPL agent 170 (step CC) and ends the event triggered session by sending a SUPL END message to SET 120 (step DD).

11 shows an embodiment of a message flow 1100 for an event-triggered SET service coverage area for a roaming-free intermediate mode. Steps A through D of message flow 1100 are similar to steps A through D of message flow 600 in FIG. 6, with the exception of this event-triggered service in the service area (instead of the periodic triggered service) that is requested in step B.

For a first position estimate indicated by an event-triggered event in the service area of the device in SET 120, steps E through G are performed in the same way as steps E through G in message flow 600. SET 120 compares the position estimate with the service area event and determines whether the event triggering condition is met (step H). Steps E through H are repeated whenever the mechanism of action of events in the service area in SET 120 indicates a new position estimate to be obtained. When an event in the service area is triggered in step P, SET 120 sends the position estimate to SUPL agent 122 to SET 120 (as shown in FIGS. 1A and 1B) (step Q). SET 120 ends a service-area event session by sending a SUPL END message to the H-SLP 150 (step R).

12 shows an embodiment of a message flow 1200 for a network-triggered event-triggered service area of a SET service for a roaming-free non-roaming mode. Steps A through I of the 1200 message flow are similar to steps A through I of the 700 message flow of FIG. 7, except for this event-triggered service in the service area (instead of the periodic triggered service) that is requested in steps A and D. H-SLP 150 may include determining a zone event in a SUPL triggered response message sent to SET 120 in step H.

For a first position estimate indicated by an event-triggered event in the device service area in SET 120, steps J through K are performed in the same way as steps J through K in message flow 700. If the position estimate is calculated in the H-SPC 154, then the H-SPC sends the position estimate in the SUPL alert message to SET 120 (step L). SET 120 compares the position estimate with the service area event and determines whether the event triggering condition is met (step M). Steps J through M are repeated whenever the mechanism of action of events in the service area in SET 120 indicates a new position estimate to be obtained. When a service area event is triggered in step U, SET 120 sends a SUPL alert message that contains a position estimate to the H-SLC 152 (step V). The H-SLC 152 informs the H-SPC 154 that the event-triggered end of the session coverage area has been internally communicated (step W). The H-SLC 152 sends the position estimate in the MLP TLREP message to the SUPL agent 170 (step X) and ends the session triggered by the coverage event by sending the SUPL END message to SET 120 (step Y).

A historically triggered service can be similar to a periodic triggered service in these dimensions, and / or a position estimate can be obtained periodically, or when certain triggered events occur for the target SET. However, measurements and / or position estimates may or may not be reported instantly for a historical initiated service. If the SET saves and later sends historical measurements, not historical position estimates, then V-SLP, H-SLP, or SPC can convert the measurements to historical position estimates to send to the SUPL agent. Tab. 6 lists some alert modes for a historical initiated service. Different services may have different requirements and may use different alert modes.

Table 6 Alert mode Description Real time Real-time measurements and / or position estimates Quasireal time Real-time measurements and / or position estimates are preferred, but historical measurements and / or position estimates are also accepted. Batch mode Historical measurements and / or position estimates are provided, for example, in batch mode

FIG. 13 shows an embodiment of a message flow 1300 for a network initiated historical called service for a roaming-free non-roaming mode. Steps A through G of message flow 1300 are similar to steps A through G of message flow 200 in FIG. 2, with the exception of the following. The historical triggered service is requested in steps A through C. An MLP TLRR message sent by the SUPL agent 170 in step A can indicate which notification mode (packet mode, real time or quasi-real time) is expected from the target SET 120. In case of notification about burst mode, the TLRR message can indicate the conditions for sending burst reports to the H-SLP 150 and any criteria (for example, the QoP time window) to include or exclude historical measurements and / or position estimates stored in SET 120. SET 120 sends its options rep_capabilities, which indicates whether they are supported in real time, quasi-real time and / or in batch mode in step E. SET 120 can always send its notification capabilities in the initial SUPL triggered message, or it can only send its notification capabilities in response to receive a historical initiated service request in step C. The H-SLP 150 selects a notification mode (rep_mode) consistent with the SET notification capabilities and sends the selected notification mode in step F. For packet notification, the H-SLP 150 also provides a response for sending packet alerts to the H-SLP 150 and any criteria for including or excluding historical measurements and / or position estimates (e.g., QoP, time window) in step F. To alert the packet mode or in quasi-real time, a SUPL triggered response message in step F may indicate whether SET 120 is allowed to send historical measurements. In this case, if a packet alert was selected, then SET 120 may skip steps H, I, and J.

For the first event indicated by the periodic action mechanism in SET 120, steps H and I can be performed in the same way as steps H and I in the message flow 200. If the position estimate is calculated in the H-SLP 150 and a packet alert is selected, then the H-SLP sends the position estimate in the SUPL alert message to SET 120 (step J). If a real-time or quasi-real-time alert is selected, then the H-SLP 150 sends the position estimate in the MLP TLREP message to the SUPL agent 170 (step K). For a given event, if

SET 120 cannot interact with the H-SLP 150 (for example, due to a lack of coverage in the cellular area), and if a packet alert or a quasi-real time alert is selected, then SET can calculate and store an offline position estimate, for example, for offline modes on GPS-based or A-GPS SET, where SET has current auxiliary data (step L). SET 120 may also store measurements in step L if H-SLP 150 is enabled in step F, provided that either a packet alert with H-SLP 150 in step F was selected or a quasi-real time alert was selected in step F, and SET 120 cannot interact using H-SLP 150.

SET 120 may send a SUPL alert message that contains historical result (s) when appropriate (step M). For example, step M may be performed if (1) a packet alert is selected and the conditions for sending packet reports are met, or (2) a quasi-real time alert is selected, and SET 120 re-establishes communication with the H-SLP 150 after missing one or more previous reports. For a burst alert, the SUPL alert message may include (1) saved measurements and / or position estimates selected based on the criteria adopted in step F, or (2) all stored measurements and / or position estimates not previously reported, if not criteria were not accepted in step F. H-SLP 150 may calculate position estimate (s) if measurements are received from SET 120. H-SLP 150 sends the reported or calculated position estimate (s) in MLP TLREP message to SUPL agent 170 (step N) .

Steps H through J or step L may be carried out for each subsequent event indicated by a periodic action mechanism. After the latest measurements and / or position estimates have been obtained or have been appropriate, SET 120 may send a SUPL alert message that contains all stored measurements and / or position estimates to the H-SLP 150 (step R). This message can also be sent if (1) a batch or quasi-real-time alert is used, (2) SET 120 has stored measurements and / or position estimates that have not yet been sent to the H-SLP, (3) SET 120 can communicate with H-SLP 150, (4) a packet alert is used and conditions for the dispatch have arisen (for example, conditions specify the dispatch after the last measurements and / or position estimates have been received). H-SLP 150 may calculate the position estimate (s) based on the received measurements, if necessary, and sends the position estimate (s) in the MLP TLREP message to the SUPL agent 170 (step S). H-SLP 150 may also retain a historical position estimate (s) for subsequent retrieval by SUPL agent 170. H-SLP 150 ends the historical initiated session by sending a SUPL end message to SET 120 (step T).

FIG. 14 shows an embodiment of a message stream 1400 for retrieving historical measurements and / or position results in the absence of roaming in non-intermittent mode. The SUPL agent 170 sends a historical instantaneous request (HLIR) MLP message to the H-SLP 150 (step A). This message may include parameters / criteria (historical parameters) (eg, time window, QoP, position determination method, and so on) that SET 120 needs to use when selecting historical measurements and / or position estimates to return to SUPL agent 170. The H-SLP 150 authenticates the SUPL agent 170, checks to see if the SUPL agent is authorized for the requested service, and applies the protection of the subscriber’s personal information. H-SLP 150 obtains routing information for SET 120 and uses routing information to send messages to SET (also step B). H-SLP 150 then initiates the extraction of historical measurements and / or position estimates using SET 120, sending out a SUPL position request message (step C). This message may include a session ID, criteria for selecting historical measurements and / or position estimates, and / or other information.

SET 120 establishes a reliable IP connection with the H-SLP 150 (step D). SET 120 selects historical measurements and / or position estimates based on accepted criteria and sends the position determination results in a SUPL alert message to H-SLP 150 (step E). The H-SLP 150 translates any historical measurements taken in step E into appropriate position estimates. The H-SLP sends position estimates in the historical location instant response message (HLIA) of the MLP to the SUPL agent 170 (step F).

FIG. 15 shows an embodiment of a message flow 1500 for a network-initiated periodic or triggered event in a service area of a roaming service in an intermediate mode. For roaming scenarios, the initiated session can be started in one SLP and can switch to another new SLP during the session. The initiating session can go from H-SLP to V-SLP, from one V-SLP to another V-SLP, or from V-SLP to H-SLP. Message flow 1500 includes an initiation / establishment phase, a first position determination phase, a re-initiation phase, and a second position determination phase. Dotted line steps C, D, G, H, and N can be performed when the initiated session starts on the guest network, and can be omitted if the initiated session starts on the home network.

In the initiation phase, the SUPL agent 170 sends the MLP TLRR message to the H-SLP 150. This message may include periodic information or information triggered by an event in the service area, QoP, client ID and / or other information. H-SLP 150 determines the V-SLP 160a in the guest network to which SET 120 has moved, and also determines that SET 120 supports the initiated service (step B). The H-SLP 150 communicates with the V-SLP 160a to request a service and determine the positioning method (s) offered by the V-SLP 160a (step C). V-SLP 160a responds by sending the proposed position determination method (s) to H-SLP 150 (step D). H-SLP 150 sends a SUPL INIT message to SET 120 using SMS, active WAP or UDP / IP delivery (step E). This message may include the proposed positioning method (s), notification and verification information, QoP, type of service (e.g., periodic or with an event in the service area) and / or other information.

SET 120 provides notifications and verification, if necessary. If SET 120 supports the initiated service and one of the proposed positioning methods, and if the user grants permission when requested, then SET 120 establishes a reliable IP connection with the H-SLP 150 and sends the initial SUPL initiated message to the H-SLP 150. This message may include SET capabilities, SET location (e.g., approximate coordinates or location ID) and / or other information (step F). H-SLP 150 sends an initial triggered SUPL V-SLP message I60a (step G). V-SLP 160a responds with a SUPL triggered message (step H), which the H-SLP 150 sends to SET 120 (step I). This message may include a positioning method selected for the initiated session, action parameters for periodic or with an event in the service area, and so on. H-SLP 150 and SET 120 save the selected positioning method. SET 120 and / or H-SLP 150 may disconnect the IP connection, for example, after some delay or inaction. H-SLP 150 returns an MLP TLRA message to SUPL agent 170 to indicate that the initiated service request has been accepted.

In the first phase of the positioning, SET 120 is connected to the line in the location session using the H-SLP 150 for a first position estimate (step K). The corresponding message flow can be used for the location session, depending on the selected method for determining the position and type of action (for example, periodic and with an event in the service area). For staging mode with the V-SLP, the H-SLP 150 may tunnel the location session via RLP to the V-SLP 160a. For the intermediate mode with the H-SLP, the H-SLP 150 may receive the location ID in the SUPL POS INIT message and may send this information via RLP to the V-SLP 160a in order to obtain an initial rough positioning. H-SLP 150 and SET 120 may perform a location session. For periodic alerts, or when a triggering event in the service area has occurred, the H-SLP 150 may send a position estimate in the MLP TLREP message to the SUPL agent 170 (step L). Steps K and L may be repeated any number of times for the initiated session. When SET 120 attempts to connect to the line in the location session in step M, the location session fails because SET 120 left the service area of V-SLP 160a (or H-SLP 150 if the initiated session started on the home network), V- SLP 160a may send a SUPL END message (SUPL end) with a continue and re-initiate status code to H-SLP 150 (step N), which forwards the message to SET 120 (step O). This message notifies SET 120 of the unsuccessful location session.

In the re-initiation phase that occurs each time SET 120 moves outside the V-SLP or H-SLP coverage area, SET 120 sends the initial SUPL initiated message to H-SLP 150 to re-initiate the initiated session (step P). This message may include location IDs and updated action parameters, for example, the remaining number of position estimates for a periodic action service or a new interval for an initiating event service in a service area. H-SLP 150 determines the new V-SLP 160b based on the location ID and sends the initial SUPL triggered message to V-SLP 160b (step Q). V-SLP 160b selects a positioning method and returns a SUPL triggered response message to H-SLP 150 (step R), which routes the message to SET 120 (step S). The re-initiator in FIG. 15 can also be used for the called location-triggered SET service.

In the second location phase, SET 120 continues the initiated session with V-SLP 160b until it reaches the end (steps T through Y).

FIG. 16 shows an embodiment of a message flow 1600 for a network initiated periodic called up service for a roaming-free non-roaming mode. Message stream 1600 can be used in place of message stream 200 in FIG. 2 or message stream 800 in FIG. Message stream 1600 includes a wake-up / establishment phase and a positioning phase.

In the wake-up phase, the SUPL agent 170 sends to the H-SLP 150 an MLP TLRR message, which may include periodic, historical, or pending location information, QoP, client ID, and / or other information (step A). H-SLP 150 verifies that SET 120 is not moving and supports SUPL (step B). H-SLP 150 sends a SUPL INIT message to SET 120, for example, using SMS, active WAP or UDP / IP delivery (step C). This message may include a session ID, an indicator of the type of action (e.g., periodic, service area event, historical or pending), an intermediate / non-intermediate mode indicator, a proposed positioning method, QoP, notification and verification information, and / or other information. SET 120 may notify the user of a location request and, if necessary, obtain user permission. If SET 120 supports the proposed positioning method and if user permission is obtained as necessary, then SET establishes a reliable IP connection with the H-SLP 150 and sends a pending SUPL confirmation message to the H-SLP 150 (step D). This message may include SET capabilities, SET location, and so on. The coordination of the positioning method to be used may be deferred to the positioning phase in order to simplify the motivation phase. H-SLP 150 sends an MLP TLRA message to SUPL agent 170 to indicate that the initiated service request has been accepted (step E).

In the location phase, when the first position estimate is triggered, SET 120 sends an initial SUPL message, which may include a session ID, a location ID, an triggered event (for example, the end of a period interval), and so on (step F). H-SLP 150 returns a SUPL response message (step G). Steps F and G may be performed for a first position estimate and may be omitted for the remaining position estimates. SET 120 then sends the SUPL POS INIT message to the H-SLP 150 (step H). This message may include position estimation for SET 120 if a SET based positioning mode is selected. SET 120 and H-SLP 150 can connect to a line in a SUPL POS session and receive a position estimate for SET (step I). H-SLP 150 sends a position estimate in the MLP TLREP message to SUPL agent 170 (step J). The H-SLP 150 (or H-SPC, V-SLP or V-SPC) may send a SUPL continuation message to confirm that the current location attempt is complete (step K) and may indicate if SET 120 is to neutralize the fault in the full determination procedure locations starting at step F for the next location attempt, and may start the next location attempt at step N. For example, the troubleshooting at step F can be used if SET 120 left the coverage area of H-SLP 150, and H-SLP 150 is necessary will request Use V-SLP. H-SLP 150 may also send a SUPL end message at the end of the initiated session (step K).

17 shows an embodiment of a message flow 1700 for a network triggered periodically called service for a roaming-free intermediate mode. Message stream 1700 can also be used instead of message stream 200 in FIG. 2, message stream 800 in FIG. 8, or message stream 1600 in FIG.

Steps A, B, C, and E may be performed as described above for steps A, B, C, and G, respectively, in FIG. 2. SET 120 performs notification and verification, if necessary, establishes a reliable IP connection with the H-SLP 150 and sends a SUPL POS INIT message to the H-SLP 150 (step D). This message may include SET capabilities, a query for ancillary data, position estimation, and so on. H-SLP 150 and SET 120 can exchange SUPL POS messages to provide any requested assistance data, positioning method instructions, QoP, periodic location information, and so on (step F).

When the first position estimate is appropriate, SET 120 receives measurements or a position estimate according to the selected position determination method and sends information in the SUPL POS message (step G). H-SLP 150 may calculate a position estimate based on measurements received from SET 120, or may check a position estimate received from SET 120. H-SLP 150 then sends the position estimate in the MLP TLREP message to SUPL agent 170 (step H). Steps G and H may be repeated (e.g., in steps I and J) whenever another position estimate is appropriate. H-SLP 150 may send a SUPL SET 120 termination message to interrupt the periodic triggered service, for example, after sending the last position estimate to SUPL agent 170 (step K). SET 120 may also send a SUPL end message to end a periodic triggered service (not shown).

FIG. 18 shows an embodiment of a message flow 1800 for a triggered periodic called SET service for a roaming-free intermediate mode. Message flow 1800 can be used instead of message flow 600 in FIG. 6 or message flow 1100 in FIG. 11.

SET 120 receives a request for periodic position assessments from an internal LCS client or from an external LCS client associated with an internal application (step A). SET 120 may perform notification and authorization, if necessary. SET 120 then establishes a reliable IP connection with the H-SLP 150 and sends an initial SUPL message, which may include a request for periodic self-location, SET capabilities, position estimation, QoP, and so on (step B). H-SLP 150 offers or selects a positioning method based on SET capabilities and sends a SUPL response message to SET 120 (step C). SET 120 sends to the H-SLP 150 a SUPL POS INIT message that contains the capabilities of the UE, a request for auxiliary data, and so on (step D). The H-SLP 150 selects a positioning method based on the H-SLP offer in step C and the SET capabilities provided in steps B and / or D. The H-SLP 150 and SET 120 can then exchange SUPL POS messages to provide any requested assistance data , instructions for the positioning method, QoP, periodic location information, and so on (step E).

When the first position estimate is appropriate, SET 120 may receive measurements according to the selected position determination method and send measurements and / or a request for auxiliary data in the SUPL POS message (step F). H-SLP 150 may calculate a position estimate based on measurements received from SET 120 and return a position estimate and / or auxiliary data in the SUPL POS message (step G). Steps F and G may be repeated whenever another position assessment is appropriate. H-SLP 150 may send a SUPL end message to SET 120 to interrupt a periodic triggered service (step H), or SET 120 may send a SUPL end message.

FIG. 19 shows a block diagram of an embodiment of SET 120, H-SLP 150 and communication network 130 in network architectures 100 and 102 of FIGS. 1A and 1B. The communication network 130 provides communication for the terminals and may include base stations (or node B) and network controllers. For simplicity, FIG. 19 shows only one processor 1920, one memory unit 1922 and one transceiver 1924 for SET 120, only one processor 1930, one memory unit 1932, one transceiver 1934 and one Comm unit 1936 for network 130 and only one a processor 1940, one memory unit 1942 and one transceiver 1944 for the H-SLP 150. In general, each object may include any number of processors, memory blocks, transceivers, communication blocks, controllers, and so on. SET 120 can support wireless communications and can also receive and process GPS signals.

On a downlink, base stations in a network 130 transmit traffic data, signaling, and control signals to terminals in their coverage area. These various types of data are processed by processor 1930 and conditioned (adjusted according to appropriate parameters) by transceiver 1934 to generate a downlink signal that is transmitted through an antenna. At SET 120, downlink signals from one or more base stations are received through an antenna, conditioned by transceiver 1924, and processed by processor 1920 to obtain various types of information for location services. For example, processor 1920 may decode messages used for the message flows described above. Memory units 1922 and 1932 store program codes and data for SET 120 and, respectively, network 130. On an uplink, SET 120 can transmit traffic data, signaling, and control signals to one or more base stations in network 130. These various types of data are processed by a processor 1920 and are conditioned by the transceiver 1924 to generate an uplink signal, which is transmitted through the SET antenna. In network 130, uplink signals from SET 120 and other terminals are received and conditioned by transceiver 1934 and further processed by processor 1930 to obtain various types of information (e.g., data, signaling, reports, and so on). The network 130 interacts with the H-SLP 150 and other network entities via a communications unit 1936.

In the H-SLP 150, the processor 1940 performs processing for the H-SLP, the memory unit 1942 stores program codes and data for the H-SLP, and the communication unit 1944 allows the H-SLP to communicate with the network 130 and other network entities. A processor 1940 may perform processing for the H-SLP 150 for the message flows described above.

The techniques described in this document can be implemented by various means. For example, techniques may be implemented in hardware, firmware, software, or a combination thereof. For a hardware implementation, the modules used to perform processing at each object can be implemented in one or more specialized integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), user-programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, electronic devices, other electronic modules designed to perform the functions described in this document th, or combinations thereof.

For a software implementation or an implementation of embedded software, techniques can be implemented using modules (eg, procedures, functions, and so on) that perform the functions described in this document. Software codes may be stored in a memory unit (e.g., memory block 1922, 1932 or 1942 in FIG. 19) and executed by a processor (e.g., processor 1920, 1930, or 1940). The memory unit may be implemented in the processor or may be external to the processor.

The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the invention. Various modifications in these embodiments will become readily apparent to those skilled in the art and the general principles defined herein may be used in other embodiments without departing from the spirit or scope of the invention. Thus, the invention is not intended to be limited by the embodiments shown herein, but rather should satisfy the broadest scope consistent with the principles and new features disclosed herein.

Claims (39)

1. A location device containing
at least one processor configured to receive from the agent a reliable positioning in the user plane (SUPL) request for position estimates for a terminal supporting SUPL (SET), to start a location session using SET to communicate with SET for determining a plurality of position estimates for a SET at a plurality of time points set by a SET during a location session, for obtaining a position estimate for a SET for each of the at least one event escheniya for positioning session and to send the position estimate obtained for each alert event agent SUPL. 2. The device according to claim 1, in which at least one processor is configured to select a position determination method from at least one position determination method that is supported by SET, and each position estimate is obtained according to the selected a method for determining the position. 3. The device according to claim 1, in which at least one processor is configured to send to the SET a list of supported position determination methods and receive a position determination method selected using the SET from the list of supported position determination methods, and each rating position obtained according to the selected position determination method. 4. The device according to claim 1, in which for each of the many points in time, at least one processor is configured to retrieve a position estimate for the SET when the method for determining the position using the SET is selected. 5. The device according to claim 1, in which for each of the many points in time, at least one processor is configured to receive a position estimate from the SET for each notification event when a method for determining a position based on SET is selected. 6. The device according to claim 1, in which for each of the many points in time, at least one processor is configured to receive measurements from the SET for each alert event and retrieve a position estimate for the SET based on the received measurements. 7. The device according to claim 1, in which for each of the many points in time, at least one processor is configured to receive a message from the SET to start a positioning session and to perform positioning using SET to obtain a position estimate for the SET, wherein position estimation is used for one or more alert events. 8. The device according to claim 1, in which for each of the many points in time, at least one processor is configured to receive a message from the SET, including the position estimate obtained using the SET. 9. The device according to claim 1, in which for each of the many points in time, at least one processor is configured to receive a message from SET to start a positioning session, sending a message to the SUPL guest location platform (V-SLP), facilitating the exchange of messages between the V-SLP and the SET for the positioning session, receiving the position estimate for the SET from the V-SLP, the position estimation being used for one or more alert events. 10. The device according to claim 1, in which for each of the many points in time, at least one processor is configured to receive a message from the SET to start a positioning session, to obtain a rough SET position from the SUPL guest location platform (V-SLP ) and performing position determination using SET using the coarse SET position, wherein the position estimate is used for one or more alert events. 11. The device according to claim 1, in which at least one processor is configured to select a notification mode from multiple notification modes comprising a real-time notification mode, a quasi-real time notification mode, and a batch notification mode. 12. The device according to claim 11, in which the at least one processor is configured to send at least one condition for sending reports to the SET if the packet notification mode is selected. 13. The device according to claim 11, in which the at least one processor is configured to send to the SET at least one criterion for selecting position estimates to be reported. 14. The device according to claim 1, in which the SUPL agent is external to the SET. 15. The device according to claim 1, in which the SUPL agent is internal to the SET and wherein at least one processor is configured to send a position estimate to the SET for each alert event. 16. The device according to claim 1, in which at least one processor is configured to authenticate the SUPL agent and verify that the SUPL agent is authorized to request position estimates for the SET. 17. A method for determining location, comprising the steps of receiving from the agent a reliable positioning in the user plane (SUPL) request for position estimates for the terminal supporting SUPL, (SET);
start a location session using SET;
communicating with the SET to determine a plurality of position estimates for the SET at a plurality of time points set by the SET during the location session,
get a position estimate for the SET for each of the at least one alert event during the location session, and
send the position estimate obtained for each alert event to the SUPL agent. 18. The method according to 17, further comprising stages, in which
receive a message from the SET to start a positioning session for each of the plurality of times and
performing position determination using the SET for each of the plurality of points in time to obtain a position estimate for the SET, wherein the position estimate is used for one or more alert events. 19. The method according to 17, further comprising stages, in which
receiving a message from the SET to start a positioning session for each of the plurality of times;
send a message to the SUPL Guest Location Platform (V-SLP);
facilitate messaging between the V-SLP and SET for the positioning session, and
receiving a position estimate for SET from the V-SLP, wherein the position estimate is used for one or more alert events. 20. The method according to 17, further comprising stages, in which
receiving a message from the SET to start a positioning session for each of the plurality of times; and
receive a rough SET position from a SUPL guest location platform (V-SLP) and
performing position determination using the SET using the coarse SET position to obtain a position estimate for the SET, wherein the position estimate is used for one or more alert events. 21. The location device containing
means for receiving from the agent a reliable positioning in a user plane (SUPL) request for position estimates for a terminal supporting SUPL (SET);
means for starting a location session using SET;
means for communicating with the SET to determine a plurality of position estimates for the SET at a plurality of time points set by the SET during the location session,
means for obtaining a position estimate for the SET for each of the at least one alert event during the location session, and
means for sending a position estimate received for each alert event to the SUPL agent. 22. The device according to item 21, further containing
means for receiving a message from the SET to start a positioning session for each of the plurality of times and
means for performing position determination using the SET for each of the plurality of points in time to obtain a position estimate for the SET, wherein the position estimate is used for one or more alert events. 23. The device according to item 21, further containing
means for receiving a message from the SET to start a positioning session for each of the plurality of times;
means for sending a message to the SUPL guest location platform (V-SLP);
means for facilitating the exchange of messages between the V-SLP and SET for the positioning session, and
means for receiving a position estimate for the SET from the V-SLP, wherein the position estimate is used for one or more alert events. 24. The device according to item 21, further containing
means for receiving a message from the SET to start a positioning session for each of the plurality of times;
means for obtaining the rough position of the SET from the guest location platform SUPL (V-SLP) and
means for performing position determination using the SET using the rough position of the SET to obtain a position estimate for the SET, wherein the position estimate is used for one or more alert events. 25. A location device containing
at least one processor configured to receive a request from the user plane reliable positioning agent (SUPL) for position estimates for a terminal supporting SUPL (SET) to start a location session using a home SUPL location platform (H -SLP) to communicate with the H-SLP to determine a plurality of position estimates for the SET at a plurality of time points set by the SET during the location session, and for each of at least about one alert event during the location session to communicate with the H-SLP to provide the SUPL agent with a position estimate for the SET. 26. The device according A.25, in which at least one processor is configured to determine each alert event based on at least one initiating condition. 27. The device according to p, in which at least one processor is configured to determine whether at least one initiating condition is satisfied based on the expiration of a timer. 28. The device according to p. 26, in which for each of the many points in time, at least one processor is configured to compare a position estimate for SET with an event in the service area and determine if at least one initiating condition is satisfied based on the result of the comparison. 29. The device according A.25, in which for each of the many points in time, at least one processor is configured to send a message to the H-SLP to start a positioning session and perform positioning using H-SLP to obtain a position estimate for SET, wherein a position estimate is used for one or more alert events. 30. The device according A.25, in which for each of the many points in time, at least one processor is configured to retrieve the position estimate for the SET and send the position estimate to the H-SLP. 31. The device according A.25, in which at least one processor is configured to send a message to the H-SLP to start a positioning session and perform positioning using the SUPL guest location platform (V-SLP) to obtain a position estimate for SET, wherein a position estimate is used for one or more alert events. 32. The device according A.25, in which the SUPL agent is external to the SET and at least one processor is configured to receive a request from the SUPL agent through the H-SLP. 33. The apparatus of claim 25, wherein the SUPL agent is internal to the SET and wherein at least one processor is configured to send a message to the H-SLP to start a location session. 34. A method for determining location, comprising the steps of
receiving a request from a user plane reliable positioning agent (SUPL) for position estimates for a terminal supporting SUPL (SET);
starting a location session using the SUPL home location platform (H-SLP);
communicating with the H-SLP to determine a plurality of position estimates for the SET at a plurality of time points set by the SET during the location session and
communicate with the H-SLP for each of the at least one alert event during the location session to provide the SUPL agent with a position estimate for the SET. 35. The method according to clause 34, further comprising the steps of sending a message to the H-SLP to start a positioning session for each of the plurality of times and
performing position determination using the H-SLP for each of the plurality of points in time to obtain a position estimate for the SET, wherein the position estimate is used for one or more alert events. 36. The method according to clause 34, further comprising the steps of sending a message to the H-SLP to start a positioning session for each of the plurality of times and
performing position determination using the SUPL guest location platform (V-SLP) for each of the plurality of times to obtain a position estimate for the SET, wherein the position estimate is used for one or more alert events. 37. A location device containing
means for receiving a request from the user plane reliable positioning agent (SUPL) for position estimates for a terminal supporting SUPL (SET);
means for starting a location session using the SUPL home location platform (H-SLP);
means for communicating with an H-SLP for determining a plurality of position estimates for a SET at a plurality of time points set by a SET during a location session; and
means for communicating with the H-SLP for each of the at least one alert event during the location session to provide the SUPL agent with a position estimate for the SET. 38. The device according to clause 37, further comprising
means for sending messages to the H-SLP to start a positioning session for each of the plurality of times and
means for performing position determination using the H-SLP for each of the plurality of points in time to obtain a position estimate for the SET, wherein the position estimate is used for one or more alert events. 39. The device according to clause 37, further comprising
means for sending messages to the H-SLP to start a positioning session for each of the plurality of times and
means for performing position determination using the SUPL guest location platform (V-SLP) for each of the plurality of times to obtain a position estimate for the SET, wherein the position estimate is used for one or more alert events.

Images