RU2431941C2 - Terminal registration using location server to locate user plane - Google Patents

Abstract

FIELD: information technology.

SUBSTANCE: terminal can perform registration using a location server if the terminal determines that it can not be normally accessible for the location server. In order to perform registration, the terminal can identify itself for the location server, trigger mutual authentication of the terminal and location server and provide an internet protocol (IP) address of the terminal for the location server. The terminal can perform registration using the location server every time the IP address changes and/or periodically every time the timer runs out. The terminal can set the timer to a value received from the location server. The location server can use the IP address to send the terminal messages for network-initiated location services.

EFFECT: improved location procedure.

43 cl, 9 dwg

Description

This application claims the priority of provisional patent application US No. 60/828902 entitled "Registration of the IP address for determining the location of the user plane", registered October 10, 2006, and provisional patent application US No. 60/864448 called "Registration SUPL 2_0 SET with using H-SLP, "registered November 6, 2006, which are assigned to their assignee and incorporated herein by reference.

State of the art

I. Technical Field

The present disclosure relates generally to communication and more specifically to methods for supporting location services (LCS) for a terminal.

II. State of the art

It is often desirable, and sometimes necessary, to know the location of a terminal, such as a cell phone. The terms "location" and "position" are synonymous and are used interchangeably in this description. For example, an LCS client may need to find out the location of a terminal, and it may establish a connection with a location server to request location information for a terminal. Then, the location server may send a message to the terminal to start the location session. This message may be properly delivered to the terminal based on routing information available to the terminal. Then, the location server and the terminal can exchange messages, as necessary, to obtain location information for the terminal. The location server can then send the required location information to the LCS client.

For a network-initiated location service, as described above, a location server or some other network entity may need routing information for a terminal to send an initial message to the terminal. In some operational scenarios, routing information for the terminal may not be available due to various reasons, as described below. However, it may be desirable to support network-initiated location services even in such scenarios.

SUMMARY OF THE INVENTION

This description provides methods for supporting network-initiated location services for a terminal. The location server may be able to reach the terminal based on various messaging mechanisms. However, each mechanism may require the terminal to register with the designated network entity so that routing information is available to the terminal. The location server in some operational scenarios may not be able to reach the terminal in the normal way based on any of these messaging mechanisms, as described below.

In an aspect, the terminal may perform registration with the location server if the terminal determines that the location server may not be able to reach the terminal in the normal way. For example, a terminal may decide to register if it is able to connect an Internet Protocol (IP) through an access network that is not connected to the terminal’s home network. For registration, the terminal can identify itself for the location server, invoke mutual authentication of the terminal and the location server, and provide the terminal IP address for the location server. The terminal can register with the location server whenever the IP address changes, and / or periodically, every time the timer expires. The terminal may set a timer based on a timer value received from the location server. The location server may use an IP address to send messages to the terminal for network initiated location services.

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

Brief Description of the Drawings

1A and 2B show two exemplary network deployments.

Figure 2 shows the relationship between the terminal and the location server.

Figure 3 shows a diagram of message flows for network initiated location services.

4 shows a flow chart of messages for registration with a location server.

FIG. 5 shows the establishment of communication between a terminal and a network address translation (NAT) location server.

6 shows a process performed by a terminal for registration.

7 shows a process performed by a location server for registration.

FIG. 8 shows a block diagram of a terminal, an access network, and a location server.

Detailed description

The methods described in this description can be used for terminals that establish communication with both wired networks and wireless networks. The terms “network” and “system” are often used interchangeably. For example, these methods can be used for wireless networks defined by an organization called the 3rd Generation Partnership Project (3GPP) and for wireless networks defined by an organization called the 3rd Generation Partnership Project 2 (3GPP2).

These methods can also be used for various user plane location architectures, such as secure user plane location (SUPL) from the Open Society of Mobile Telecommunications Manufacturers (OMA), user plane V1 and V2 from code division multiple access development group (CDMA) (CDG), X.S0024 user plane from 3GPP2, etc. SUPL is suitable for 3GPP, 3GPP2 and WLAN (Wireless LAN) networks. X.S0024, V1 and V2 are suitable for 3GPP2 networks. The user plane is a mechanism for transferring messages / signaling for higher-level applications and using the unidirectional channel of the user plane, which is usually implemented using protocols such as the transmission of user datagrams (UDP), transmission control protocol (TCP) and IP, all of which are known in the art. Messages / signaling supporting location and positioning services can be carried as part of the data (from a network perspective) in the user plane architecture.

For clarity, some aspects of these methods are described below for SUPL. SUPL version 1.0 (SUPL 1.0) is described in OMA-AD-SUPL-V1 under the title “Secure User Plane Location Architecture”, June 15, 2007, and in OMA-TS-ULP-V1 under the UserPlane Positioning Protocol ( user plane), June 15, 2007 SUPL version 2.0 (SUPL 2.0) is described in OMA-AD-SUPL-V2 under the title "Secure User Plane Location Architecture", August 31, 2007, and in OMA-TS-ULP -V2 entitled "UserPlane Positioning Protocol (User Plane)", September 27, 2007. These SUPL documents are published in OMA.

1A shows an example network deployment 100. Terminal 110 may communicate with access network 120 to receive communication services. Terminal 110 may be fixed or mobile, and may also be referred to as user equipment (UE), mobile station, access terminal, subscriber unit, station, etc. Terminal 110 may be a cell phone, personal digital assistant (PDA), wireless device, handheld device, wireless modem, compact laptop computer, telemetry device, tracking device, etc. Terminal 110 may communicate with one or more base stations and / or one or more access points in access network 120. Terminal 110 may also receive signals from one or more satellites 180 in a satellite positioning system (SPS), which may be the United States of America global positioning system (GPS), the Galileo European system (Galileo), the Russian GLONASS system, etc. Terminal 110 may measure signals from base stations in access network 120 and obtain timing correlation measurements for these base stations. Terminal 110 may also measure signals from satellites 180 and obtain pseudorange measurements for satellites. Pseudorange and / or time matching measurements can be used to derive a position estimate for the terminal 110. A position estimate may also be referred to as a location estimate, location determination, etc.

Access network 120 supports communications for terminals located within its area. Access network 120 may be a wireless network and may also be referred to as a radio network, radio access network, etc. Access network 120 may be a 3GPP access network, 3GPP2 access network, wireless local area network (WLAN), etc. The 3GPP access network may be a global system for the Global System for Mobile Communications (GSM) network, an EDGE radio access network (GSM GERAN), a universal terrestrial radio access network (UTRAN) using universal terrestrial radio access (UTRA), e.g. Broadband CDMA (W-CDMA), Advanced UTRAN (E-UTRAN), Using Long Term Evolution (LTE) Radio Access, etc. The 3GPP2 access network may be a CDMA2000 IX network using the cdma2000 network, CDMA2000 1xEV-DO network, etc. WLAN can implement radio technology such as any of the IEEE 802.11 family of standards (Institute of Electrical and Electronics Engineers), Hiperlan (high-performance local radio network), etc. Access network 120 may also be a wireless network supporting another radio technology such as Ultra Mobile Broadband (UMB), IEEE 802.20, Flash-OFDM®, IEEE 802.16 (WiMax) (worldwide broadband wireless access compatibility), etc. UTRA, E-UTRA and GSM are described in documents from 3GPP. cdma2000 and UMB are described in documents from 3GPP2. 3GPP and 3GPP2 documents are publicly available. Access network 120 may also be a wired network such as a local area network (LAN), digital subscriber line network (DSL), packet cable network, telephone network, etc.

The visited network 130 is the network that currently serves the terminal 110, and may also be referred to as the Visited Public Land Mobile Network (V-PLMN). The visited network 130 may include various network entities that provide connectivity for data and / or voice, location services, and / or other functionality and services. For 3GPP, the visited network 130 may include a GPRS (Public Service Packet Radio System) support node (SGSN) 132, and a WLAN Access Gateway (WAG) 134. SGSN 132 is part of a public packet radio communication system (GPRS) core network and provides packet-switched services for terminals communicating with a 3GPP access network. WAG 134 is part of the 3GPP WLAN (I-WLAN) core network and provides packet-switched services for terminals communicating with a WLAN access network. The visited network 130 may include other 3GPP network entities, such as network entities supporting location and positioning services, which are not shown in FIG. 1A for simplicity. For 3GPP2, the visited network 130 may include network entities that perform functions similar to those for 3GPP, but referred to under other names. 3GPP and 3GPP2 generally use different network entities and, for clarity, most of the following description is presented for 3GPP based networks.

Home network 140 is a network with which terminal 110 is subscribed, and may also be referred to as a home PLMN (Public Land Mobile Network) (H-PLMN). Home network 140 may include various entities that provide connectivity for data and / or voice, location services, and / or other functionality and services. For 3GPP, home network 140 may include a GPRS gateway support node (GGSN) 142, a packet data gateway (PDG) 144, a short message service center / message switching center (SMSC / MC) 146, a location reference register / home Subscriber Server (HLR / HSS) 148, Home SUPL Location Platform (H-SLP) 150, and Access, Authorization, and Accounting (AAA) server 152. GGSN 142 performs functions such as routing and filtering to support packet-switched services. PDG 144 supports the interaction between 3GPP and WLAN and performs functions such as protecting the flow of information, assigning an IP address, etc. SMSC / MC 146 supports the Short Message System (SMS) and delivers SMS messages to terminals. HLR / HSS 148 stores subscription related information for terminals for which network 140 is a home network. HLR / HSS 148 also stores registration information and provides routing information for network-initiated calls and SMS for terminals in home network 140, for example, whenever requested by network entities in visited network 130. H-SLP 150 supports SUPL for terminals in the home network 140. The AAA server 152 authorizes the terminals for service and performs the functions of accounting and billing. The home network 140 may include other 3GPP network entities that are not shown in FIG. 1A for simplicity.

An access network 120 (eg, a WLAN) can exchange packets with a router 122 that can be connected to the Internet 124. The H-SLP 150 can communicate with other objects via the Internet 124, for example, terminal 110 via the Internet 124, router 122, and network 120 access.

1B shows another exemplary network deployment 102. In deployment 102, H-SLP 150 may be used by location service provider 108, which may not be the home network operator for terminal 110. Terminal 110 may or may not have a home network. GGSN 142, PDG 144, and H-SLP 150 may be connected to the Internet 124. Terminal 110 may communicate with the H-SLP 150 via a visited network 130 and a home network 140, for example via an access network 120, SGSN 132, GGSN 142, and the Internet 124 Terminal 110 may also communicate with H-SLP 150 via access network 120, router 122, and Internet 124.

1A and 1B show two exemplary network deployments supporting communication between terminal 110 and H-SLP 150. Terminal 110 may also communicate with H-SLP 150 in other network deployments, including other combinations of networks and / or network entities.

FIG. 2 shows the relationship between terminal 110 and H-SLP 150. Terminal 110 supports SUPL for location and positioning services and is referred to in SUPL as a SUPL Authorized Terminal (SET). The terminal 110 may have a SUPL actuator 210 that resides in the terminal. The SUPL actuator is a service access point that accesses network resources for location information. The SUPL actuator may comprise a Mobile Device Location Services (MLS) application program, which may include protocols used to establish communication between the SUPL actuator and the H-SLP. H-SLP 150 may include a SUPL location center (SLC) 220, which supports location services for terminals in home network 140 and visited network 130, and a SUPL positioning center (SPC) 222, which supports positioning for these terminals. SUPL actuator 160 may communicate with H-SLP 150 to obtain location information for terminal 110.

SUPL supports SET-initiated services and network-initiated services. Initiated SET services are services that originate from the SET, with the SUPL actuator residing in the SET. Network-initiated services are services that originate from a SUPL network, with a SUPL actuator resident in the network.

SUPL supports one-way communication from H-SLP 150 to terminal 110, which can be used by H-SLP 150 to send a SUPL INIT message (initiation) to terminal 110 to start a network-initiated location session. The H-SLP 150 can send a SUPL INIT message using various mechanisms, including UDP / IP, Push Protocol (WAP), SMS, and Session Initiation Protocol (SIP) push. For UDP / IP, the H-SLP 150 may send a SUPL INIT message to terminal 110 through various network entities, as described below for TCP / IP. For WAP Push, the H-SLP 150 can send a SUPL INIT message to terminal 110 via a WAP Push (PPG) gateway or through a PPG WAP connected to SMSC / SC 146. For SMS, the H-SLP 150 can send a SUPL INIT message to terminal 110 through SMSC / SC 146, SGSN 132 and access network 120. For SIP Push, the H-SLP 150 may send a SUPL INIT message to terminal 110 via the SIP / IP core.

SUPL also supports bidirectional communication between terminal 110 and H-SLP 150 using TCP / IP. Two-way communication can be used to exchange SUPL messages between terminal 110 and H-SLP 150 for registration, location services, positioning, etc. For 3GPP GPRS, SUPL messages can be exchanged using TCP / IP between terminal 110 and H-SLP 150 via GGSN 142, SGSN 132 and access network 120, which can be GSM, GERAN, UTRAN, etc. For 3GPP I-WLANs, SUPL messages can be exchanged using TCP / IP between terminal 110 and H-SLP 150 via PDG 144, WAG 134, and access network 120, which may be a WLAN. SUPL messages can also be exchanged between terminal 110 and H-SLP 150 via the Internet 124, router 122, and access network 120, which may be WLAN, LAN, DSL network, packet cable network, etc. One-way and two-way communication between terminal 110 and H-SLP 150 is described in detail in the aforementioned OMA-AD-SUPL-V2.

For SET initiated services, terminal 110 may send a SUPL START message (SUPL start) to H-SLP 150 to start a location session. Terminal 110 may be provided with the IP address of the H-SLP 150 platform and may send a SUPL START message to the H-SLP using this provided IP address. In general, an IP address can be a 32-bit IP address of Version 4 (IPv4) or a 128-bit IP address of Version 6 (IPv6). Alternatively, terminal 110 may be provided with a fully qualified domain name (FQDN) of the H-SLP 150 and may use a domain name system (DNS) to obtain an IP address for the H-SLP. Terminal 110 may then send a SUPL START message to the H-SLP 150 using the selected IP address.

For network-initiated services, the H-SLP 150 may send a SUPL INIT message to terminal 110 to start a location session using any of the one-way communication mechanisms shown in FIG. 2. H-SLP 150 may use UDP / IP if the IP address of terminal 110 is known to the H-SLP platform or can be obtained by the H-SLP platform, for example from HLR / HSS 148, GGSN 142, or AAA server 152. Then, the H-SLP 150 may send a SUPL INIT message to the terminal 110 using the IP address of the terminal. H-SLP 150 may use SIP Push if terminal 110 has completed SIP registration with home network 140, and routing information for terminal 110 is available, for example, from HLR / HSS 148. H-SLP 150 may use SMS or WAP Push if terminal 110 has performed wireless access registration (eg, GSM, UMTS (Universal Mobile Telecommunication System) or CDMA registration) with home network 140, and routing information for terminal 110 is available, for example, from HLR / HSS 148.

For normal SUPL, the H-SLP 150 can send a SUPL INIT message to terminal 110 using SMS, WAP Push, or SIP Push without knowing the IP address of the terminal. Later, the H-SLP 150 may receive the IP address of the terminal 110 after the terminal establishes a secure IP connection to the H-SLP. However, as noted above, the H-SLP 150 can use SMS or WAP Push only if the terminal 110 has registered for wireless access, and can use SIP Push only if the terminal 110 has registered for SIP. H-SLP 150 may send a SUPL INIT message to terminal 110 using UDP / IP, but first it must obtain the IP address of terminal 110, for example, by requesting HLR / HSS 148 and / or other network entities such as GGSN 142, server 152 AAA (for WLAN access), etc. For IP access via a 3GPP or 3GPP2 based network, the IP address of terminal 110 can be obtained from HLR / HSS 148 or through a dynamic DNS server (DDNS). However, the IP address of terminal 110 cannot actually be obtained by the H-SLP 150 if DDNS is not supported by network entities typically supporting DDNS.

In some scenarios, terminal 110 may have access to a communication channel, for example via WLAN, LAN, DSL, etc., but for H-SLP 150 it may not be possible to initiate a location session with terminal 110 using UDP / IP, WAP Push, SMS or SIP Push. This can happen if the H-SLP 150 cannot determine the IP address of terminal 110, and terminal 110 gains access to a network that does not support (fully or correctly) interaction with WAP Push, Push, SMS or SIP Push, or does not support the described The above types of registrations are necessary to enable these transfers. In such scenarios, location requests initiated by the SUPL actuator 160 through the H-SLP 150 may fail.

The scenarios described above can occur if the terminal / SET 110 is not registered or is not fully registered with the HLR / HSS 148 in the home network 140 when accessing services based on IP packet switched mode. Terminal 110 may not be registered or not fully registered in any of the following cases or situations for the user:

(a) A terminal 110 user has a temporary or permanent subscription to more than one Internet Service Provider (ISP) and / or VoIP (Voice over Internet Protocol) provider and accepts services from a provider that is neither its home operator, nor its partner roaming (automatic connection to the local communication network) of the home operator. For example, a user may use a hotel or airport WLAN, a wired VoIP provider, or company-provided LAN / VoIP capabilities.

(b) The user accesses the WLAN in connection with the home network 140, but chooses to use the direct WLAN IP access mode in which the home network 140 provides AAA support but does not provide or does not accept the IP address of the terminal 110.

(c) Terminal 110 accepts TCP / IP access through another terminal device. For example, the terminal / SET 110 may reside in a compact laptop computer that accesses TCP / IP via an IP-enabled cell phone.

(d) Terminal 110 accepts TCP / IP access through a virtual private network (VPN); for example, through tunneling a VPN to a corporate LAN.

For the user cases described above, WAP Push and SMS may not work, and UDP / IP will only work if the H-SLP 150 already has the IP address of terminal 110; for example, from a previous location-initiated SET session if it happened once. In addition, for the deployment shown in FIG. 1B, one-way communication from the H-SLP 150 to terminal 110 using the UDP / IP, SMS, WAP Push, or SIP Push shown in FIG. 2 may not be possible because H- SLP 150 is not part of home network 140 and infrequently may have the IP address of terminal 110.

In an aspect, the terminal / SET 110 may register its current IP address with the H-SLP 150 to support network-initiated location services for the user cases described above, and possibly other user cases. Terminal 110 may register with H-SLP 150 whenever terminal 110 communicates with an access network that does not provide normal interaction with home network 140. After this situation is detected, terminal 110 may register with H-SLP 150 and provide its IP address for the H-SLP, which can use this IP address to send messages to terminal 110 for network initiated services.

Terminal 110 may register with H-SLP 150 for any type of access (e.g., via WLAN, W-CDMA, LAN, DSL, etc.) for the deployment shown in Fig. 1B. For the normal case in which the H-SLP 150 is part of the home network 140, as shown in FIG. 1A, the need for registration with the H-SLP 150 may be less common. However, for the case shown in FIG. 1B, registration with the H-SLP 150 may always be necessary. Registration with the H-SLP 150 enables SUPL to be supported by the location service provider 108, which is different from the home network operator. Terminal 110 can be started to initiate registration using the H-SLP 150 on a recurring periodic basis, or according to instructions from the H-SLP (for example, the H-SLP can send information when or as often as registration is performed), etc. .

FIG. 3 shows a message flow diagram 300 for network initiated location services using H-SLP registration. Terminal 110 may initially detect that it may not be accessible in the normal way via UDP / IP, WAP Push, SMS, or SIP Push via H-SLP 150, and that H-SLP registration is required or required (step A). For example, terminal 110 may decide to register using H-SLP 150 when terminal 110 does not receive IP connectivity using either its home network or its home network roaming partner. Then, terminal 110 may register with the H-SLP 150 and may transmit its IP address to the H-SLP, as described below (step B).

At a later time, SUPL executor 160 may need location information for terminal 110, and it can send a standard direct location-to-location request (SLIR) message for the mobile device location protocol (MLP) to the H-SLP 150 (step C). H-SLP 150 may authenticate and authorize SUPL actuator 160 for the desired location service. Then, the H-SLP 150 may obtain routing information for the terminal 110, which is the target SET (step D). Since terminal 110 registered its IP address with H-SLP 150, routing information may include the IP address of the terminal.

Then, the H-SLP 150 may initiate a location session with the terminal 110 by sending a SUPL INIT message using the terminal IP address (step E). In this case, WAP Push, SMS and SIP Push may not be available to send a SUPL INIT message. H-SLP 150 may be able to use UDP / IP to send a SUPL INIT message (because it has terminal IP address 110) or it may be able to use TCP / IP if the TCP / IP connection used to register H- The SLP in step B is still open (that is, it has not been completed). The SUPL INIT message may contain a session identifier used to identify a location session, an intended positioning method, desired positioning quality (QoP), etc. After receiving the SUPL INIT message, terminal 110 may perform a data connection establishment procedure and attach itself to the data network if the terminal is not already connected (step F). Terminal 110 can then establish a secure TCP / IP connection to the H-SLP 150 (also step F) if the secure TCP / IP connection is not already open (for example, it was not used to send the SUPL INIT message to step E). Then, terminal 110 may send a SUPL POS INIT message to start a positioning session using H-SLP 150 (step G). The SUPL POS INIT message may include a session identifier, SET capabilities (e.g., supported positioning methods and protocols), request for auxiliary data, etc.

Thereafter, terminal 110 and H-SLP 150 can exchange messages for the SUPL positioning session (step H). For positioning using SET, the H-SLP 150 may calculate a position estimate for terminal 110 based on positioning measurements received from the terminal. For SET-based positioning, terminal 110 may calculate a position estimate based on assistance received from H-SLP 150. In any case, after position calculation is completed, H-SLP 150 may send a SUPL END message (SUPL end) to inform terminal 110 that no additional positioning procedure will be started, and that the location session is over (step I). Then terminal 110 may disconnect the secure TCP / IP connection for H-SLP 150 and may also release resources associated with the location session. H-SLP 150 may send the requested location information in a standard direct MLP location response (SLIA) message to SUPL actuator 160 and may release resources associated with the location session.

FIG. 3 shows an example message flow diagram for one instance of a network-initiated location service using H-SLP registration. H-SLP registration can also be used to support other message flows for other cases of network-initiated location services, which can cover roaming and non-roaming modes (without automatically connecting to a local communication network), with an intermediary module and without a module- intermediary, services launched and not launched, etc. The SUPL actuator 160 may communicate directly with the H-SLP 150 for scenarios with roaming and no roaming, or implicitly with the H-SLP 150, through the requesting SLP (R-SLP). SPC 222 can communicate directly with terminal 110 in a mode without an intermediary module and can communicate implicitly with terminal 110, via SLC 220, in a mode with an intermediary module. H-SLP 150 may provide location information for terminal 110 for SUPL actuator 160 once for non-triggered services, and possibly more than once, based on event triggers or timers, for triggered services. In general, registration with the H-SLP 150 can be performed for each of the various network-initiated message flows described in the above documents OMA-TS-ULP-V1 and OMA-TS-ULP-V2.

FIG. 4 shows a flow diagram of messages 400 for registration with H-SLP 150, which may be used for step B in FIG. 3. Terminal 110 may receive IP connectivity through an access network that is not its home network or roaming partner of its home network. Then, terminal 110 may decide to invoke registration with H-SLP 150 (step A).

For H-SLP registration, terminal 110 can establish a secure TCP / IP connection to H-SLP 150 using the H-SLP IP address, which can be provided to terminal 110 with home network 140 or can be obtained by the terminal in other ways (step B). A secure IP connection can be established in various ways, as described below. Then, terminal 110 may send a SUPL REGISTRATION message to register its IP address with H-SLP 150 (step C). The SUPL REGISTRATION message may include a session identifier identifying the current session, the IP address of terminal 110, etc. For mobile IP, the IP address of terminal 110 may be a remote IP address assigned by a home executive device (ON) within home network 140. H-SLP 150 may return a SUPL REGISTRATION ACK message containing a repeat timer value (RT) to terminal 110 (step D).

Terminal 110 may periodically perform registration with H-SLP 150 based on a repeat timer. For example, terminal 110 may set the repeat timer to a repeat timer value obtained from the SUPL REGISTRATION ACK message, and may register with the H-SLP 150 when the repeat timer expires, or whenever the IP address of terminal 110 changes. For each registration, the H-SLP terminal 110 may establish a secure IP connection to the H-SLP 150 if this connection has been disconnected, or may save and reuse the previous secure IP connection. Then, terminal 110 may send a SUPL REGISTRATION message with the current terminal IP address for H-SLP 150 (step E). H-SLP 150 may return a SUPL REGISTRATION ACK message with the same or a different repeat timer value to terminal 110 (step F). Terminal 110 may skip or unregister with H-SLP 150 (steps E and F) if the terminal receives IP connectivity from home network 140 or a home network roaming partner.

In general, terminal 110 can only register with H-SLP 150 once (for example, after receiving IP connectivity through an access network that is not connected to the home network) or many times (for example, each time the repeat timer expires or changing the IP address of the terminal). The repeat timer value may or may not be sent in the SUPL REGISTRATION ACK message. If it is sent, the value of the repeat timer can be selected based on the estimated life of the IP address of the terminal 110 and / or other factors. The value of the repeat timer can also be limited so that it is within the range of the minimum and maximum values. Between steps D and E of FIG. 4, the H-SLP 150 and / or terminal 110 may or may not cause the disconnection of the secure IP connection established in step B.

H-SLP 150 may also provide other information in the SUPL REGISTRATION ACK message to assist terminal 110 in deciding when to register again. For example, the H-SLP 150 may include in the SUPL REGISTRATION ACK message a flag instructing terminal 110 to send a SUPL REGISTRATION message if terminal 110 is assigned a new IP address. H-SLP 150 may include a different flag (eg, no flag) in the SUPL REGISTRATION ACK message to instruct terminal 110 not to send a SUPL REGISTRATION message if terminal 110 is assigned a new IP address. Such additional information in the SUPL REGISTRATION ACK message can be used by the H-SLP 150 to ensure that it has the current IP address of the terminal 110 and to limit the frequency of SUPL REGISTRATION messages to avoid network congestion situations.

Figure 4 shows the use of the SUPL REGISTRATION message for registration with the H-SLP 150. In general, terminal 110 may send any message that carries the IP address of the terminal explicitly (for example, in the payload) and / or implicitly (for example, in the address source). Terminal 110 may send this message after a secure IP connection is established while it is being established, or immediately before it is established.

Terminal 110 may be assigned an IP address based on various mechanisms known in the art. This assigned IP address may be referred to as a private IP address. Terminal 110 may communicate with an access network 120 that can translate network addresses (NAT), and can map the private IP address of terminal 110 to a public IP address that can be used by external entities to send IP packets to terminal 110. NAT can be used for various purposes, such as protection (for example, preventing unauthorized IP access to terminal 110), making it possible to share the same public IP address with multiple terminals, etc. The terminal 110 may not be aware of the NAT performed by the access network 120, and may also not be aware of the public IP address used for the terminal.

Figure 5 shows the connection between terminal 110 and H-SLP 150 using NAT. Terminal 110 may exchange IP packets using H-SLP 150 through a router / gateway 520 in access network 120 and other network entities, which are not shown in FIG. 5 for simplicity. For registration with the H-SLP 150 in FIG. 4, terminal 110 may send one or more IP packets for the SUPL REGISTRATION message (step C) to the H-SLP 150 via router 520. Each IP packet sent by terminal 110 may have (i ) the source address field set to the private IP address of terminal 110, (ii) the destination address field set to the H-SLP 150 IP address, and (iii) the payload field carrying the SUPL REGISTRATION message, which may include the private The IP address of terminal 110. Router 520 can receive IP packet (s) from terminal 110, perform NAT, replace rivatny IP-address in each IP packet by the outdoor IP-address for the terminal 110, and send the packet (s) IP at the H-SLP 150.

H-SLP 150 can receive IP packet (s) from router 520, extract the public IP address from the source address field, and extract the private IP address from the sent SUPL REGISTRATION message in the payload field. H-SLP 150 can compare these two IP addresses. If these IP addresses match, then H-SLP 150 may assume that a valid IP address has been received for terminal 110. If these IP addresses are different, then H-SLP 150 may assume that NAT has been performed and may use open The IP address obtained from the IP packet (s) source address field. The H-SLP 150 may support the secure IP connection established in step B in FIG. 4 to avoid the risk of losing the ability to send IP packets to terminal 110 due to packet filtering by the router 520. Alternatively or additionally, the H-SLP 150 may provide lower repeat timer for terminal 110 to more often verify that the terminal still has the same public IP address. If NAT is running, then a lower value of the retry timer can also help to avoid moving the binding of the public-private IP address for terminal 110 in router 520 due to the lack of flow of IP information to and from the terminal. The value of the repeat timer can be chosen so that it is less than the duration of the binding of the public-private IP address performed by the router 520, if it is known.

To register with the H-SLP 150, terminal 110 can establish a secure IP connection to the H-SLP 150 before sending a SUPL REGISTRATION message. To establish a secure IP connection, terminal 110 may first establish an IP connection to H-SLP 150. Then, terminal 110 and H-SLP 150 can authenticate to authenticate each other. Mutual authentication can be performed based on various mechanisms.

In one design that is suitable for 3GPP and 3GPP2, Transport Layer Security (TLS) can be used for mutual authentication of terminal 110 and H-SLP 150. TLS may be used if terminal 110 has completed wireless access registration, for example, for GSM, UMTS, CDMA, etc. H-SLP 150 can authenticate terminal 110, confirming that the IP address of the terminal is valid, for example, by requesting GGSN 142 or AAA server 152. H-SLP 150 may also provide a public key access certificate to terminal 110 (using TLS) to allow the terminal to authenticate the H-SLP. TLS is described in IETF RFC 2246 (Requests for Comments by the Internet Design Problem Group), entitled “TLS Protocol,” January 1999, which is publicly available.

In another design that is suitable for 3GPP2, TLS Pre-Shared Key (PSK) (PSK-TLS) can be used for mutual authentication of terminal 110 and H-SLP 150. PSK-TLS relies on a shared secret key that is previously stored securely in both terminal 110 and H-SLP 150. PSK-TLS is described in IETF RFC 4279 entitled "Pre-shared key suitable for encryption (ciphersuites) Transport Layer Security (TLS), December 2005, which is publicly available. The PSK-TLS authentication procedure is defined in SUPL 1.0 and SUPL 2.0 for 3GPP2 and can be extended to 3GPP.

In yet another design that is suitable for 3GPP and 3GPP2, a variant of the PSK-TLS universal bootstrap architecture (GBA) procedure defined for SUPL 1.0 can be used for mutual authentication of terminal 110 and H-SLP 150. For GBA, PSK- TLS and terminal 110 and H-SLP 150 support GBA and can receive a secure shared key from the bootstrap server (BSF) function in home network 140. This key can then be used to support mutual authentication of PSK-TLS of terminal 110 and H-SLP 150 as described about the project S.P0114 3GPP TS 33.222 or 3GPP2 TSG-S. The key can also be used to support TLS using authentication of HTTP combined messages (Hypertext Transfer Protocol), or only authentication of HTTP combined messages between terminal 110 and H-SLP 150, or some other form of authentication. The GBA procedure includes terminal 110, H-SLP 150, and BSF in home network 140. Therefore, there can be no effect on either access network 120 or visited network 130. GBA is described in 3GPP2 S.S0109-0 under the name "Structure of the universal bootstrap architecture (GBA)", March 2006, 3GPP2 S.S0114-0 entitled "Security mechanisms using GBA", March 2006, 3GPP TS 33.220 called "Universal authentication architecture (GAA); universal bootstrap architecture and 3GPP TS 33.222, titled Universal Authentication Architecture (GAA); access to "network application features that use the protocol to send hypertexts over the secure transport layer (HTTPS)." These documents are publicly available.

In general, mutual authentication of terminal 110 and H-SLP 150 can be supported by GBA, an alternative to PSK-TLS, etc. The mutual authentication capability may support network-initiated location services for the user cases described above, as well as for SET-initiated location services, which may require mutual authentication when establishing a secure IP connection.

6 shows a design of a process 600 performed by a terminal, for example, SET in SUPL. The terminal may initially determine whether to register with the location server (block 612). The terminal may decide to register if it receives IP connectivity through (i) an access network that is not connected to the terminal’s home network, (ii) a WLAN or a wired network, or (iii) some other access network. The terminal may also decide to register if the location server is used by a service provider that is not a home network operator. The location server may be an H-SLP in SUPL, a gateway mobile location center (GMLC) in 3GPP, a mobile positioning center (MPC) in 3GPP2, etc. The terminal may communicate using the location server to perform registration if a registration decision is made (block 614). Establishing a connection for registration can identify the terminal for the location server, invoke mutual authentication of the terminal and the location server, and provide the terminal IP address for the location server. The IP address can be used by the location server to send messages to the terminal for network-initiated location services.

The terminal can establish a secure IP connection using the location server and can send the IP address of the terminal via a secure IP connection to the location server. The terminal may support a secure IP connection for subsequent registration or a location session using the location server. The terminal can register with the location server if the IP address changes. The terminal may also receive a timer value from the location server, set a timer based on the timer value, and register when the timer expires.

The terminal may receive a message to start a network-initiated positioning session, with a message sent by the location server to the terminal based on the IP address provided to the location server during registration (block 616). The terminal may communicate with the location server for the location session (block 618).

7 shows a design of a process 700 performed by a location server, for example, H-SLP, GMLC, MPC, etc. The location server may communicate with the terminal to register the terminal with the location server (block 712). The establishment of communication may identify the terminal for the location server, cause mutual authentication of the terminal and the location server, and provide the terminal IP address for the location server. The location server may receive at least one IP packet from the terminal, obtain a first IP address from the IP packet (s) source address field, obtain a second IP address from the payload of the IP packet (s), and compare the first and second IP addresses . The location server can use the second IP address as the IP address of the terminal if the first and second IP addresses match, and can use the first IP address as the IP address of the terminal if the first and second IP addresses do not match. The location server may send a timer value to the terminal during registration, and the terminal may use the timer value to perform subsequent registration with the location server.

The location server may send a message to start a network-initiated location session (block 714). A message may be sent to the terminal based on the IP address received from the terminal during registration. Then, the location server may communicate with the terminal for the location session (block 716).

FIG. 8 shows a structural block diagram of a terminal 110, an access network 120, and an H-SLP 150 shown in FIGS. 1A and 1B. At terminal 110, modem processor 824 may receive data sent by terminal 110, process (eg, encode and modulate) data, and generate chip chips. A transmitter (TMTR) 832 can condition (eg, convert to analog, filter, amplify, and upconvert) the output chips and generate an uplink signal that can be transmitted through an antenna 834. In a downlink, an antenna 834 can receive downlink signals from access network 120. A receiver (RCVR) 836 can condition (e.g., filter, amplify, downconvert and digitize) the received signal from antenna 834 and provide samples. Modem processor 824 can process (eg, demodulate and decode) samples and provide decoded data. Modem processor 824 may perform processing in accordance with radio technology (eg, W-CDMA, CDMA IX, GSM, 802.11, etc.) used by access network 120. Digital signal processor 826 may perform various types of processing for terminal 110.

A GPS receiver 838 can receive and condition signals from satellites 180. These measurements can be processed to obtain an accurate position estimate for terminal 110. A rough position estimate for terminal 110 can also be determined based on pilot signals received from base stations on network 120 access.

A controller / processor 820 may direct operation at terminal 110. A controller / processor 820 may perform processing for terminal 110 in message flow 300 in FIG. 3 and message flow 400 in FIG. 4. The controller / processor 820 may also perform the process 600 shown in FIG. 6 and / or other processes for the methods described herein. A memory device 822 may store program codes, data, and an IP address of the terminal 110. Processors 820, 824, and 826 and a memory device 822 may be implemented on an application-oriented integrated circuit (ASIC) 810.

For simplicity, FIG. 8 shows one controller / processor 840, one storage device 842, one transmitter / receiver (TMTR / RCVR) 844, and one communication unit (Comm) 846 for access network 120. In general, access network 120 may include any number of controllers, processors, storage devices, transmitters, receivers, communication devices, etc. Controller / processor 840 may perform various functions to establish communication with the terminals, memory 842 may store program codes and data for access network 120, transmitter / receiver 844 may communicate with the terminal, and communications device 846 may communicate with other network entities.

FIG. 8 also shows an embodiment of the H-SLP 150. The H-SLP 150 may include a controller / processor 850 that may perform various functions to support location services and / or positioning, a memory device 852 that can store program codes and data for the H-SLP 150, and a communication device 854 that can communicate with other network entities. The controller / processor 850 may perform processing for the H-SLP 150 in the message stream 300 in FIG. 3 and the message stream 400 in FIG. 4. The controller / processor 850 may also perform the process 700 shown in FIG. 7 and / or other processes for the methods described herein. The storage device 852 may store the IP address of the terminal 110, which can be received during registration performed by the terminal.

The methods described herein can be implemented using various means, depending on the application. For example, these methods may be implemented in hardware, firmware, software, or a combination thereof. For hardware implementations, the data processing units used to execute methods at the facility (for example, in a terminal or location server) can be implemented in one or more 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, and other electronic units designed to perform Nia described herein functions PC or combinations thereof.

For implementation in firmware and / or software, methods can be implemented using modules (eg, procedures, functions, etc.) that perform the functions described in this description. In general, any medium read by a machine / computer / processor that materially embodies the instructions / code of the firmware and / or software can be used to implement the methods described in this description. For example, firmware and / or software instructions / code may be stored in a memory (e.g., memory 822 or 852 in FIG. 8) and executed by a processor (e.g., processor 820 or 850). The storage device may be implemented on or off the processor. The instructions / code of the firmware and / or software can also be stored in an environment read by the machine / computer / processor, such as random access memory (RAM), read-only memory (ROM), long-term random access memory (DV RAM), programmable ROM (EPROM), electrically erasable ROM (EEPROM), flash memory, floppy disk, compact disk (CD), universal digital disk (DVD), magnetic or optical storage device, etc. Commands / code may be executed by one or more processors and may cause the processor (s) to execute some aspects of the functionality described herein.

The previous description of the disclosure is provided to enable any person skilled in the art to make or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the universal principles defined herein may apply to other varieties without departing from the scope or spirit of the disclosure. Thus, the disclosure is not intended to be limited by the examples and design solutions described in this description, but should be consistent with the broadest scope consistent with the principles and new features disclosed in this description.

Claims (43)

1. A communication device, comprising:
at least one processor configured to determine after initial registration with the location server whether to perform subsequent registration with the location server based on one or more detectable events, and establish communication with the location server to perform subsequent registration if a decision has been made to register, the connection identifying the terminal for the location server, causing mutual authentication the terminal and the location server, and provides a private and open terminal Internet Protocol (IP) address for the location server, at least one of the public and private IP addresses for use by the location server to send messages to the terminal for network-initiated location services , and
a storage device connected to at least one processor. 2. The device according to claim 1, in which at least one processor receives a message to start a network-initiated positioning session, the message being received by the terminal from the location server based on at least one of the public and private IP address provided for location server during initial or subsequent registration. 3. The device according to claim 1, in which one or more detectable
event detection includes at least one
by the processor, that the terminal receives IP connectivity through an access network that is not connected to the terminal’s home network. 4. The device according to claim 1, in which one or more of the detected events includes the detection by at least one processor that the location server does not belong to the terminal's home network. 5. The device according to claim 1, in which one or more of the detected events includes the detection by at least one processor that one or more of the open and private IP addresses of the terminal changes. 6. The device according to claim 1, in which one or more detectable events includes the detection of at least one processor that the timer expires. 7. The device according to claim 1, in which at least one processor receives a timer value from the location server, sets a timer based on this timer value, and performs subsequent registration with the location server when the timer expires. 8. The device according to claim 1, in which at least one processor establishes a secure IP connection using the location server, sends at least one of the terminal's public or private IP addresses through the secure IP connection to the location server, and supports secure IP connection for subsequent registration or location session using the location server. 9. The device according to claim 1, in which the terminal is a terminal with authorized secure location of the user plane (SUPL) (SET), and the location server is a home platform for positioning SUPL (H-SLP). 10. The device according to claim 1, in which at least one processor performs mutual authentication with the location server using at least one of transport layer security (TLS), pre-shared key and transport layer protection (PSK-TLS), and universal bootstrap architecture (GBA). 11. The device according to claim 1, in which the terminal is not aware of the IP address. 12. The device according to claim 1, in which the terminal sends an open IP address for the location server by including a private address in the address field of the message source that is sent to the router,
at the same time, the router replaces the private IP address in the source field with the public IP address. 13. A wireless communication method, comprising:
determining after the initial registration with the location server whether to perform subsequent registration with the location server based on one or more detectable events, and
establishing a connection with the location server for subsequent registration, if a registration decision is made, and the connection identifies the terminal for the location server, causes mutual authentication of the terminal and the location server, and provides public and private terminal Internet Protocol (IP) addresses for the location server wherein at least one of the public and private IP addresses is used by the location server to osylat communication terminal for network-initiated location services. 14. The method according to item 13, further comprising:
receiving a message to start a network-initiated positioning session, the message being received by the terminal from the location server based on at least one of the public and private IP addresses provided to the location server during initial or subsequent registration. 15. The method of claim 13, wherein the one or more detectable events includes detecting that the terminal is receiving IP connectivity through an access network that is not associated with the terminal’s home network. 16. The method according to item 13, further comprising:
receiving a timer value from the location server, setting a timer based on this timer value, and performing subsequent registration with the location server when the timer expires. 17. A device for wireless communication, comprising:
means for determining, after initial registration with the location server, whether to register with the location server based on one or more detected events, and
means for communication with the location server to perform subsequent registration if a registration decision is made, the connection identifying the terminal for the location server, causing mutual authentication of the terminal and the location server, and providing public and private terminal Internet Protocol (IP) addresses for a location server, wherein at least one of the public and private IP addresses is used by the location server, which send messages to the terminal for network initiated location services. 18. The device according to 17, additionally containing:
means for receiving a message to initiate a network-initiated positioning session, the message being received by the terminal from the location server based on at least one of the public and private IP addresses provided to the location server during initial or subsequent registration. 19. The device according to 17, in which one or more of the detected events includes detecting that the terminal is receiving IP connectivity through an access network that is not connected to the terminal's home network. 20. The device according to 17, additionally containing:
means for receiving a timer value from a location server,
means for setting a timer based on this timer value, and
means for performing subsequent registration with the location server when the timer expires. 21. Computer-readable media including instructions that, when executed by a computer, force the computer to perform operations, the instructions comprising:
the code for forcing the computer to determine, after initial registration with the location server, whether to register with the location server based on one or more detected events, and the code for forcing the computer to communicate with the location server to perform subsequent registration, if the decision is made registration, and the establishment of communication identifies the terminal for the location server,
causes mutual authentication of the terminal and the location server and provides the public and private terminal Internet Protocol (IP) addresses for the location server, at least one of the public and private IP addresses is used by the location server to send messages to the terminal for network initiated services location determination. 22. The computer-readable medium of claim 21, further comprising:
code to force the computer to receive the message in order to initiate a network-initiated positioning session, the message being received by the terminal from the location server based on at least one of the public and private IP addresses provided to the location server during initial or subsequent registration. 23. The computer-readable medium of claim 21, wherein one or more of the detected events includes detection, the terminal is able to IP connect through an access network that is not connected to the terminal’s home network. 24. The computer-readable medium of claim 21, further comprising:
code to force the computer to accept the timer value from the location server, set a timer based on this timer value, and initiate subsequent registration with the location server when the timer expires. 25. A communication device, comprising:
at least one processor configured to, after initial registration with a location server, communicate with a terminal for subsequent registration of a terminal with a location server based on one or more detectable events in the terminal, and
send a message to the terminal to start the network-initiated positioning session, wherein the connection identifies the terminal for the location server, causes mutual authentication of the terminal and the location server, and provides
open and private terminal Internet Protocol (IP) addresses for the location server, the message being sent from the location server to the terminal based on at least one of the public and private IP addresses received from the terminal during subsequent registration, and a storage device, connected to at least one processor. 26. The device according A.25, in which at least one processor sends a timer value to the terminal during initial registration, and the timer value is used by the terminal to perform subsequent registration using the location server. 27. The device according A.25, in which for the initial and subsequent registration of at least one processor receives at least one IP packet from the terminal, obtains an open IP address from the source address field of at least one IP packet, receives a private IP the address from the payload of at least one IP packet, compares the public and private IP addresses, uses the private IP address as the destination IP address of the terminal, if the public and private IP addresses match, and uses the public IP address as the target IP addresses t terminal if the public and private IP addresses do not match. 28. The device according A.25, in which the terminal is a terminal with an authorized secure location of the user plane (SUPL) (SET), and the location server is a home location platform SUPL (H-SLP). 29. A wireless communication method, comprising:
establishing communication after the initial registration of the terminal with the location server with the terminal for subsequent registration of the terminal with the location server based on one or more detectable events in the terminal, the connection identifying the terminal for the location server, causing mutual authentication of the terminal and the location server, and provides public and private terminal Internet Protocol (IP) addresses for the server determining the month position and
sending a message to start a network-initiated location session, where a message is sent from the location server to the terminal based on at least one of the public and private IP addresses received from the terminal during subsequent registration. 30. The method according to clause 29, further comprising:
sending the timer value to the terminal during initial registration, the timer value being used by the terminal to perform subsequent registration with the location server. 31. The method according to clause 29, further comprising:
receiving at least one IP packet from the terminal,
obtaining an open IP address from the source address field of at least one IP packet,
obtaining a private IP address from the payload of at least one IP packet,
comparing public and private IP addresses,
using the private IP address as the terminal IP address if the public and private IP addresses match, and
use the public IP address as the IP address of the terminal if the public and private IP addresses do not match. 32. A device for wireless communication, comprising:
means for establishing communication after the initial registration of the terminal with the location server with the terminal for subsequent registration of the terminal with the location server based on one or more detectable events in the terminal, the connection identifying the terminal for the location server, causing mutual authentication of the terminal and the determination server location and provides the open and private addresses of the Internet Protocol (IP) terminal for the server op edeleniya locations, and
means for sending a message to start a network-initiated positioning session, the message being sent from the location server to the terminal based on at least one of the public and private IP addresses received from the terminal during subsequent registration. 33. The device according to p, optionally containing:
means for sending the timer value to the terminal during the initial registration, wherein the timer value is used by the terminal to perform subsequent registration with the location server. 34. The device according to p, optionally containing:
means for receiving at least one IP packet from the terminal,
means for obtaining an open IP address from a source address field of at least one IP packet,
means for obtaining a private IP address from the payload of at least one IP packet,
means for comparing public and private IP addresses,
means for using the private IP address as the terminal IP address if the public and private IP addresses match, and
means for using the public IP address as the IP address of the terminal if the public and private IP addresses do not match. 35. Computer-readable media including instructions that, when executed by a computer, force the computer to perform operations, the instructions comprising:
code for forcing the computer to communicate after the initial registration of the terminal with the location server with the terminal for subsequent registration of the terminal with the location server based on one or more detectable events in the terminal, the connection identifying the terminal for the location server, causing mutual authentication of the terminal and location server and provides public and private Internet Protocol (IP) term addresses Nala for the location server, and
code for forcing the computer to send a message to start a network-initiated positioning session, the message being sent from the location server to the terminal based on at least one of the public and private IP addresses received from the terminal during subsequent registration. 36. The computer-readable medium of claim 35, further comprising:
code for forcing the computer to send the timer value to the terminal during initial registration, the timer value being used by the terminal to perform subsequent registration with the location server. 37. The computer-readable medium of claim 35, further comprising:
code to force the computer to receive at least one IP packet from the terminal, obtain an open IP address from the source address field of at least one IP packet, obtain a private IP address from the payload of at least one IP packet, compare open and private IP -addresses, use the private IP address as the IP address of the terminal if the public and private IP addresses match, and use the public IP address as the IP address of the terminal if the public and private IP addresses do not match. 38. A wireless communication method, comprising:
determining whether to register with the location server based on one or more detected events, and
establishing a connection with the location server for registration, if a registration decision is made, and the connection identifies the terminal for the location server, causes mutual authentication of the terminal and the location server, and provides public and private terminal Internet Protocol (IP) addresses for the location server, moreover, at least one of the public and private IP addresses for use by the location server to send scheniya terminal for network-initiated location services. 39. The method of claim 38, wherein the terminal is configured to be included in a positioning session with the location server to determine a position of the terminal. 40. The method of claim 38, wherein the step of establishing communication comprises:
while establishing a secure IP connection between the terminal and the location server;
sending a user plane location registration (SUPL) message to the location server, receiving an ACK to the SUPL registration message from the location server in the terminal. 41. A wireless communication method, comprising:
establishing communication with the terminal for registering the terminal with the location server based on one or more detectable events in the terminal, the connection identifying the terminal for the location server, causing mutual authentication of the terminal and the location server, and providing open and private Internet Protocol (IP) addresses a terminal for a location server; and
sending a message to start the network-initiated location session, the message being sent from the location server to the terminal based on one of the public and private IP addresses received from the terminal during registration. 42. The method according to paragraph 41, wherein the location server is configured to be included in the positioning session with the terminal so as to determine the location of the terminal. 43. The method according to paragraph 41, wherein the step of establishing communication includes:
while establishing a secure IP connection between the terminal and the location server;
receiving a user plane location registration (SUPL) message from a terminal in the location server,
sending the ACK to the SUPL Registration message from the location server to the terminal.

Images