RU2368105C2 - System, method and device of location service (ls) - Google Patents

Abstract

FIELD: physics, communication.

SUBSTANCE: invention is related to the field of wireless data transmission networks. Substance of invention consists in the fact that location identification (LI) and location detection (LD) are processed as separate and independent processes. LI is realised by means of the first set of network objects. Information on location may be placed into cash-memory for further disclosure to any number of applications. LD is realised by means of the second set of network objects. LI uses the first safety procedure for authentication, authorisation and receipt of the first session key used for LI. LD uses the second safety procedure for authentication, authorisation and receipt of the second session key used for LD. For mobile station under roaming, LI may be realised by means of service network, and LD may be realised by means of home network.

EFFECT: higher accuracy of location identification and provision of mobile stations with information on location.

43 cl, 21 dwg, 4 tbl

Description

Related Applications

This application claims priority for provisional application No. 60/452,358 for the grant of a US patent filed March 5, 2003, provisional application No. 60 / 452,914 for the grant of a US patent filed March 7, 2003, and provisional application No. 60 / 460,839 for the grant of a US patent filed April 5, 2003.

FIELD OF THE INVENTION

The present invention relates generally to the field of communication and more specifically to a system, method and apparatus for performing positioning and providing location information by means of a location service architecture (OMP) based on a user plane.

State of the art

It is often desirable, and sometimes necessary, to know the location of a wireless user. For example, the Federal Communications Commission (FCC) has adopted a provision for Advanced Wireless Services 911 (E-9-1-1), which requires the provision of the location of a mobile station (such as a cell phone) to the Public Security Response System (AID) each time when a call is received from the mobile station 911. In addition to the FCC requirement, the network operator / service provider can support various applications using location services, which are services that provide location location of mobile stations. Such applications may include, for example, location-dependent billing, asset tracking, asset tracking and recovery, alert and resource management, personal location service, and so on. Some examples of applications for serving a personal location include (1) providing the mobile station with a location map based on the location of the station, (2) providing recommendations for service locations (e.g., a hotel or restaurant) based on the location of the mobile station, and (3) providing directions to recommended service location from the location of the mobile station.

In many conventional wireless networks, the location of the mobile station and the use of this location are integrated. That is, if the application requires the location of the mobile station, then initiate the procedure for determining the location of the mobile station and messages about it to use this application. Such an integrated design is undesirable for several reasons. First, if multiple applications require the location of a mobile station, then the location of the mobile station may need to be determined multiple times, once for each of these applications. This leads to inefficient use of expensive system resources. Secondly, a network entity designed to control the location and reporting of the location of mobile stations may need to be redesigned whenever the service provider adds a new application.

Therefore, in the prior art there is a need for a system, method and device that can more efficiently perform positioning and provide location information for mobile stations.

Disclosure of invention

The system, method and device described in these materials can effectively provide location services. The system, method and device are based on the architecture of the WMD, whereby the location determination and location detection are treated as separate and independent processes. Positioning refers to determining location information for a mobile station. This location information may include a location estimate for the mobile station, accuracy or uncertainty in the location estimate, other suitable information, or a combination thereof. Location detection refers to the disclosure of location information to applications that request location information.

Positioning can be performed using the first set of network objects using protocols and mechanisms in the level of "location". Various procedures and call flows can be used to perform positioning, as described below. The specific call flow for use in determining the location depends on (1) whether the location request is coming from the mobile station or network, and (2) the specific method used to determine the location of the mobile station (e.g., a method based on IS-801, or ID cell method). The location information obtained by performing the location determination can be cached (i.e., stored in a memory element) in a mobile station and / or network objects for subsequent use.

Location detection can be performed by a second set of network entities using protocols and mechanisms at the “location detection” level, which is constantly located at the top of the location level. Similarly, various procedures and call flows can be used to perform location detection. The specific call flow for use in location detection may depend on (1) whether the location request is coming from the mobile station or network and (2) where the location information is cached.

Positioning can be done as needed. It can be performed, for example, when location information is needed, if the available location information is irrelevant or does not meet the requirements, and so on. Once received, location information can be disclosed to any number of applications. Thus, location determination can only be performed once, while location detection can be performed multiple times to provide location information to multiple applications. Detailed call recording (CDR) can be provided for each location request, and CDR can also be provided for each location request. DRV can be used for accounting, billing (billing) and / or other purposes.

When determining the location, the first security procedure can be used to (1) authenticate and authorize and (2) set the session key to obtain the first session key. The first session key can be used to authenticate and / or encrypt messages exchanged to determine location. When locating a location, a second security procedure can be used to (1) authenticate and authorize and (2) set a session key to obtain a second session key. The second session key can be used to authenticate and / or encrypt messages exchanged when a location is detected. The first and second security procedures can use the same or different security algorithms. For example, the first security procedure may use the MD-5 algorithm, and the second security procedure may use the Authentication and Key Negotiation (ASK, AKA) procedure. For a mobile station that roams outside its home network, positioning can be done via the serving network, and location detection can be done through the home network. The first session key can be used with network entities in the serving network, and the second session key can be used with network entities in the home network.

Various aspects and embodiments of the invention are described in detail below.

Brief Description of the Drawings

The features, nature and advantages of the present invention are obvious from the following detailed description, given with reference to the accompanying drawings, in which like reference numbers indicate similar elements.

Figa and 1B - architecture of the WMD based on the user plane.

Figure 2 - network, which implemented the architecture of the WMD in figure 1.

3A and 3B are call flows that can be used for the mobile station and the OMP server, respectively, to obtain the IP address of the CPU.

4A and 4B illustrate call flows for authenticating, authorizing, and setting a session key for locating and locating locations, respectively.

5A and 5B illustrate call flows for making an outgoing call from a mobile device to a location based on IS-801 and an ID cell method, respectively.

6A to 6B illustrate call flows for performing location determination by a location server from a mobile device when establishing location information and placing it in a cache in various objects.

7 is a call flow for establishing the IP address of a mobile station that is not always in operation.

FIGS. 8A and 8B illustrate call flows for performing an in-place location determination for a mobile device based on IS-801 and an ID cell method, respectively.

Figa - 9B - call flows for making incoming to the mobile device location by the location server when establishing location information and placing it in the cache in various objects.

10A and 10B illustrate call flows for a DRR message for locating and locating, respectively.

11 is a structural diagram of various objects in the network of figure 2.

DETAILED DESCRIPTION

The expression “exemplary” is used in these materials to mean “serve as an example, model, or illustration.” Any embodiment or construction described herein as “exemplary” should not be construed as preferred or more advantageous in comparison with other embodiments or constructions. In addition, in the following description, “location”, “position” and “position” are synonymous terms that are used interchangeably.

FIG. 1A illustrates a location service architecture (WMO) 100 based on a user plane that enables more efficient location service. The user plane is a mechanism that can carry data for higher-level applications. The user plane can be composed of various protocols, such as the User Datagram Protocol (PDD, UDP), the Transmission Control Protocol (TCP, TCP) and the Internet Protocol (IP), each of which is well known in the art. Protocols in the user plane are usually based on other protocols in the (lower) control plane in order to function properly.

The OMP architecture 100 includes an application / content layer 110, a location detection layer 120, and a location determination layer 130. Applications at level 110 use location information to provide location-dependent services. Location information may include a location estimate for each, one or more of the WMD goals, accuracy or uncertainty for each location estimate, or some other suitable information or a combination thereof. The purpose of the WMD is the mobile station whose location is being sought.

Location detection layer 120 includes protocols and mechanisms that can be used to disclose (i.e. provide) location information to target mobile stations. Applications at level 110 may request location information by invoking protocols and mechanisms at level 120. These protocols and mechanisms will then provide location information to applications that require it. The location level 130 includes protocols and mechanisms that can be used to determine (i.e., obtain) location information for the target mobile stations. The protocols and mechanisms at level 130 can be invoked in accordance with the protocols and mechanisms at level 120, if necessary and when it is necessary to determine location information. Protocols and mechanisms at levels 120 and 130 are described in detail below.

The WMD architecture 100 is based on the recognition that positioning and location detection are two independent processes that can be disconnected. This disparate design for the 100 WMD architecture provides various benefits. First, the OMP architecture 100 can easily support new applications without the need to modify or reverse engineer the underlying location and location detection levels. In addition, the OMP architecture 100 allows supporting various types of applications, such as, for example, BREW (Binary Execution Environment for Wireless Devices), WAP (Wireless Application Protocol), SMS (Short Message Service), and Java applications. Secondly, location information can be disclosed to multiple applications without having to separately and redundantly obtain this information. Thirdly, separate procedures for authentication, authorization and accounting (AAA, AAU) can be used to determine the location and location, to obtain various advantages, as described below.

Figure 2 presents a diagram of a network 200, which implemented the architecture of 100 WMD based on the plane of the user. The network 200 includes a home network 210, a serving network 250, and a third party network 290. Home network 210 is a wireless communication network in which a mobile station 280 is registered. (A mobile station is also often referred to as a terminal, a mobile phone, a wireless device, user equipment (UHF), or some other terminology is used). Serving network 250 is a wireless communication network through which mobile station 280 is currently receiving service. The serving network 250 is different from the home network 210 if the mobile station 280 roams and moves outside the coverage of the home network 210. The third-party network 290 is a communication / data network that is not part of the home network 210 or the serving network 250. For example, the network The third party 290 may be a data network supported by an Internet service provider.

Home network 210 includes various network entities that communicate with each other via IP network 212. A network entity is a logical entity within a network that is designed to perform a specific function. Similarly, the serving network 250 includes various network entities that communicate with each other via the IP network 252. The IP networks 212 and 252 further connect the IP network 292 to the Internet. Network objects within home network 210, serving network 250, and third party networks 290 can communicate with each other via IP networks 212, 252, and 292.

Within the network 200, the “location client” and “location server” are two functions that interact with each other to disclose location information. A location client requests location information for one or more WMD targets. The location server provides location information to the requesting location client. Both the location client and the location server may reside in a mobile station or some other network entities. For example, the location client may reside in the mobile station 280, the WMD provider 202a in the home network 210, the WMD provider 202b in the serving network 250, or the WMD provider 202c in the third party network 290. An WMD provider is a network entity that uses location information to provide location services. The location server may reside in the mobile station 280 or the OMP server 216 in the home network 210. The mobile station 280 may serve as the location client, location server and / or OMP target. For example, if the application in the mobile station 280 needs the location of the mobile station 280, then the mobile station 280 serves both the location client and the WMD target. To simplify the presentation in the following description, it is assumed that the mobile station 280 is the target of the WMD.

Within the home network 210, the OMP server 216 is a network entity designed to serve as a location server for locating. The server 216 OMP interacts with the object 218 home authentication, authorization and accounting (D-AAU, H-AAA) to perform authentication and authorization to locate. A database 221 is used to store subscription information for subscribers (ie, users) of the home network 210. Each user is usually required to have a “subscription” for each wireless network that he wishes to have access to. The subscription includes relevant information needed to access the specified wireless network, such as subscriber / user identification information, security information, and so on. A subscription for each user is also called a “subscriber profile” or “user profile”. The subscription information in the database 221 can be modified by the administrator 220 of the subscription WMD and can be accessed by D-AAU 218 for authentication, authorization and accounting. The message switching center 230 is responsible for storing, transmitting and sending SMS messages to mobile stations. Home Position Register 224 (RLP, HLR) stores registration information for mobile stations that have registered in home network 210.

Within the serving network 250, the positioning center of the served mobile device (SMPC) serves as an interface point with the serving network 250 for determining location. SMPC 256 interacts with D-AAU 218 to perform authentication and authorization for determining the location. SMPC 256 also allows mobile stations to access a location service determination object (SPDE) 260 to determine a location. CMPC 256 is used, if necessary, to authenticate and authorize the mobile station 280 in the event that the mobile station 280 needs OOPO 260 as a location resource. OOPO 260 determines the geographic location of the target of the WMD in accordance with the specified Quality of Service Position (CPC). The CPC determines the accuracy of the location of the WMD target, which can be superimposed by the requiring application. Different CPC requirements may necessitate the use of different location methods, as described below. The object 258 guest authentication, authorization and accounting (G-AAU, V-AAA) serves as a proxy server D-AAU 218 and can support authentication and authorization to determine the location. The packet data service unit 270 (PDSN) is responsible for establishing, maintaining, and terminating data transfer sessions for mobile stations in the serving network 250. The mobile device switching center 272 (MSC) performs switching functions (i.e., message and data routing) for mobile stations within their coverage area. A base station controller (BSC) / packet control function (PCF) 274 controls data transmission between the PDSN 270 and the base station with which the mobile station 280 is currently communicating. In the guest position register (RGP) (not shown in FIG. 2), registration information for mobile stations that are registered in the serving network 250 is stored.

Servers 232 and 262 of the domain name system (DNS, DNS) translate domain names (for example, www.domain-name.com) into IP addresses (for example, 204.62.131.129) that require network objects to communicate with each other via IP networks. Each server of the domain name system receives domain name system requests from other network objects to the IP addresses of domain names, determines the IP addresses for these domain names and sends responses of the domain name system with IP addresses back to the requesting network objects. An LED server in a given network (for example, LED server 232) can exchange information with other servers of the domain name system in other networks (for example, LED server 262) to obtain the required IP addresses.

For simplicity, FIG. 2 shows only some of the network objects within the home network 210 and some of the network objects within the serving network 250. The home network 210 typically also includes network objects (eg, OOP and MPC) that support location for mobile stations communicating with the home network 210. Accordingly, the serving network 250 typically also includes network entities (eg, WMD server 216 and WMD subscription manager 220) that support location detection for mobile stations for which the home network is the serving network 250. These additional network entities are not shown in FIG. 2 for simplicity. In addition, each of the networks 210 and 250 may include multiple samples of each network entity. For example, serving network 250 may include multiple DRCs.

Figure 2 shows the logical representation of the network 200, which includes various network objects designed to perform certain functions. These network entities include OMP providers 202a, 202b and 202c, OMP server 216, D-AAU 218, CPOMU 256, OOPO 260, and so on. Network entities are logical entities of their respective networks (home, service, and third party). The network entities shown in FIG. 2 can be implemented in various ways. In addition, these network entities may be combined in one hardware module or may reside in different hardware modules.

On figb shows the implementation of the architecture 100 of the OMP with the network objects shown in figure 2. The positioning may be performed by a first set of network entities for determining location information for the mobile station 280. Network entities that may be involved in positioning include the mobile station 280, OOPO 260, CPMSU 256, and D-AAU 218. OOPO 260 use if his assistance is necessary for determining the location. CMPC 256 can be used if necessary, if the assistance of OOPO 260 is necessary for determining the location. D-AAU 218 can be activated if necessary, if authentication and authorization are necessary for determining the location.

The location detection may be performed by a second set of network entities for disclosing location information for the mobile station 280. Network entities that may be involved in locating the location include the mobile station 280, the MSS server 216, the CPMSU 256 and the D-AAU 218. The CPUs 256. used if necessary, it can be used if the location information is cached (that is, stored) in the CPU 256. D-AAU 218 is also used if necessary, it can be used if for detection m These provisions require authentication and authorization.

Referring again to FIG. 2, it should be noted that network entities within the network 200 can communicate with each other via specially defined interfaces. Some of these interfaces are described additionally.

When determining the location, the following interfaces can be used. The OOPO - MS interface is used to perform the exchange of information between the mobile station 280 and the OOPO 260 to determine the location. The OOPO-MS interface is described in document TIA / EIA / IS-IS-801, entitled "Positioning Service Standards for Dual Mode Extended Spectrum Systems", which is a publicly available document. The CPMMU-D-AAU interface is used to send authentication and authorization information to determine the location. D-AAU 218 may send the information of the subscriber (subscriber) to the CPMC 256 for authentication purposes. CMPC 256 may also send transaction information to D-AAU 218 for accounting and billing purposes, as described below. The OOPA - CPOMU interface is used to exchange information between the OOPO 260 and the CPOMU 256 to determine the location. The OOPO-CPMU interface is described in document TIA / EIA / PN-4747, entitled “Location Service Extensions”, and in document J-036, both of which are publicly available. The CPMSC — MS interface enables the serving network 250 to perform various control functions before positioning takes place.

When locating a location, the following interfaces can be used. The location server-location client interface is used to send location information from a location server to a location client for position disclosure. The OMP server-D-AAU server interface is used to send authentication and authorization information for locating. D-AAU 218 may send a subscriber profile to the WMD server 216. The OMP server 216 may also send accounting information to the D-AAU 218.

If the mobile station 280 is located far from its home network 210 and communicates with the serving network 250, then the location is determined by the serving network 250 (with an assistant from the home network 210, if necessary), and location detection is performed by the home network 210 (with location information obtained through the serving network 250). If the mobile station 280 is in communication with its home network 210, then location determination is performed by network entities (eg, OOP, MPC) in home network 210, and location detection is also performed by home network 210.

Location service includes (1) a location-originating service from a mobile device or a location initiated by a mobile device in which the requesting party is located in the mobile station 280, and (2) a location service, originating from a mobile device or site-initiated by the mobile device, where the requesting party is located on the network 210, 250, or 290. Table 1 shows where the location client and location server can be located for outgoing from a mobile device and inbound for mobile Nogo device's location services. Location service comes from a location client, which may be located in the mobile station 280 or the WMD provider 202a, 202b, or 202c.

Table 1 Outgoing from a Mobile Device Inbox for Mobile Device WMD client Mobile Station 280 Supplier 202 WMD WMD server Mobile station 280 or OMP server 216 Mobile station 280 or OMP server 216

A request for an outgoing WMD from a mobile device may result from an application that is located on a mobile station 280, or from an application that is located on a network 210, 250, or 290. The mobile station 280 performs appropriate control (independently or under the control of a network) to deliver location information to the requestor side. Some examples of requests for outgoing from a mobile WMD device include:

- a request for location information for the mobile station 280 - a location client is located in the mobile station 280;

- offline request for ancillary data - the mobile station 280 requests ancillary data outside the context of determining the location (the request for ancillary data of the WMD is thus not tied to any particular location client); and

- a request for the disclosure of location information to a third party - the location information is sent to the third-party location client (WMD provider 202c), which is assigned by the mobile station 280.

The request for incoming WMD for the mobile device may result from an application located on the network 210, 250 or 290. The server 216 WMD performs appropriate management (for example, authentication, verification and authorization of service, encryption, and so on). Requests for incoming WMD for the mobile device include a request for location information for the mobile station 280, in which the location server is located in the mobile station 280.

Since location and location are considered as separate processes, different call flows can be defined and used for these two processes. A call flow is a sequence of steps that can be performed to achieve a given result. Each step in the call flow can start a specific procedure. Exemplary call flows are described below for (1) detecting the IP address of the CPMC 256 (for a roaming mobile station), (2) authenticating, authorizing, and setting a session key, (3) the location and location of the outgoing data from the mobile device, (4) incoming to the mobile device location and location detection and (5) other functions associated with WMD.

1. CPMU detection

The CMPC detection scheme is provided here to enable the mobile station to dynamically determine the CMPC address for positioning. This scheme supports roaming for the mobile station, since there is no need to reconfigure the CPMC address on the mobile station.

FIG. 3A illustrates an exemplary call flow 300 for a mobile station 280 to obtain an IP address of a central control center 256. Mobile station 280 initiates a data call to establish a PMTT (PPP, PMTT — Point-to-Point Transfer Protocol) session with PDSN 270 (step 312). During the IPCP data call stage (IP-PU, IP Control Protocol), the mobile station 280 obtains the IP address of the LED server 262.

The mobile station 280 then sends a domain name system request to the CPMC 256 using the fully qualified domain name (FQDN, CWI) (step 314). PODI is a domain name that is detailed along the entire return path to the root of the tree. As some examples, the LUT used to determine the position may be “pde.gpsone. <SID> .net.”, “<NID>. <SID> .mpc.net.”, “Mpcgpsone.net” or “<SID > .mpcgpsone.net ”, where <NID> is the network identifier, and <SID> is the system identifier. The CID can be preconfigured at the mobile station 280 or sent to the mobile station 280 via over-the-air signaling. IDN for positioning can also be standardized in wireless networks to enable roaming. The DSI server 262 maps the CID to the IP address of the CPU 256 and sends to the mobile station 280 a DSI response with this IP address (step 316).

The mobile station can roam and can communicate with the visited (guest) network, and the OMP server can be located in the home network, as shown in Fig.2. In this case, the OMP server may need to know the IP address of the CPU. For example, the location information for the roaming mobile station may be cached in the CPMC, and the IP address of the CPCM will be necessary to obtain this location information. The CMPC detection circuitry is provided here to enable the OMP server to dynamically determine the CMPC address for location detection.

FIG. 3B illustrates an exemplary call flow 350 for an OMP server 216 to obtain an IP address of a CMPC 256. The mobile station 280 initiates a data call to establish a PMTT session with PDSN 270 (step 362). During the data call setup, the PDSN 270 sends the D-AAU 218 an Access Request message with both the mobile station ID 280 (MS ID) and the IP address of the CPMCU 256 (step 364). The IP address of the CPMC 256 can be preconfigured in the PDSN 270 in accordance with the topology of the serving network 250. It should be noted that a single CPNC 256 can service a number of PDSN 270. The D-AAU 218 receives the Access Request message from the PDSN 270 and confirms this by returning a message Accepting Access (step 366). D-AAU 218 then sends the ID of the mobile station 280 and the IP address of the CPMCU 256 to the OMP server 216 (step 368). The OMP server 216 issues a confirmation to the D-AAU 218 (step 370).

2. Authentication, Authorization and Session Key Installation

As noted above, positioning and location detection are processed by the OMP architecture 100 as separate processes. Different authentication, authorization, and session key setup procedures can then be used for these two processes to provide different benefits, as described below.

A. Positioning

In order to determine the location of both the outgoing from the mobile device and the inbound location service for the mobile device, the CPMC 256 may perform authentication and authorization based on the identity of the requested. These procedures can be performed, for example, (1) if OOPO 260 is necessary to assist in determining the location, (2) if a session key is used to determine the location (which is referred to as “Session Key 1”), (3) if the validity of the current Session 1 Key has expired and so on. The validity period of the Session Key 1 indicates the period of time during which the Session Key 1 is valid. Upon successful authentication of the mobile station 280, the D-AAU 218 may send security information to the CPMC 256, which may then forward the security information to the mobile station 280. The security information may include, for example, a new Session Key 1, Key 1 expiration date Session and so on. Then, Session Key 1 may be used between the mobile station 280 and the CPMSU 256, or between the mobile station 280 and the OOPO 260 to determine the location. Session Key 1 can be used to authenticate messages and / or encrypt them.

FIG. 4A shows an exemplary call flow 400 for authenticating, authorizing, and setting a session key for location. Call flow 400 uses the Message Profile MD-5 algorithm only to authenticate the mobile station 280 with respect to the network. The MD-5 algorithm is well known in the art and is described by R. Rivest in RFC 1321, entitled “Message Profile MD5 Algorithm,” which is publicly available. The transmission of messages between the CPPCU 256 and the D-AAU 218 is performed by the RPA (EAP, Extensible Authentication Protocol) over the PDP, and the transmission of messages between the CPPCU 256 and the mobile station 280 is performed via the PDP. RPA on RPA is described by P. Engelstad in a document entitled "RPA on RPA (EAPoUDP)", which is publicly available.

Mutual authentication can also be performed to authenticate the mobile station 280 with respect to the network and the network with respect to the mobile station 280. If mutual authentication is required, instead of the MD-5 procedure, the Authentication and Key Negotiation (ASK) procedure or some other mechanisms can be used . ACK procedures for W-CDMA are described in 3GPP TS 33.102 entitled “3G Security;

Security Architecture ”which is publicly available.

For call flow 400, the CPMC 256 initially sends an Access Request OUANP packet to the D-AAU 218 (step 412). OUANP (Remote Authentication Dial-In User Service, RADIUS) is a security system that uses a client-server approach to authenticate remote users through a series of calls and responses that the client (CPU 256) relays between the server (D-AAU 218) and by the user (mobile station 280). The Access Request OUANP package contains the RPA message, which additionally contains the RPA Response field. The RPA Response field contains the Network Access Identifier (ISI, NAI) for the mobile station 280. Before making the call flow 400, the mobile station 280 establishes a PMTT session (not shown in FIG. 4A). The ISD is a user ID (for example, "username@domain-name.com") represented by the mobile station 280 (acting as a client) during the authentication of the PBTT.

D-AAU 218 receives the Access Request OUANP packet from the CPMC 256 and responds by sending back the Access Call OUANP packet. The Access Call OUANP package contains an RPA message that additionally contains an RPA Request field for an MD-5 Call (step 414). The MD-5 call is the authentication call generated by the D-AAU 218 based on the ISD received from the CPU 256. The CPU 256 sends an RPA Request with MD-5 Call (on the PDD) to the mobile station 280 (step 416). The mobile station 280 receives the RPA Request from the CPMC 256 and determines the response to the authentication call. The mobile station 280 then responds by sending an RPA Response with an MD-5 Response (on the PDA) to the CPMC 256 (step 418).

CPMU 256 then re-submits the D-AAU 218 its initial Access Request OUANP packet, which contains the MD-5 Response provided by the mobile station 280 (step 420). D-AAU 218 authenticates the mobile station 280 based on the MD-5 Response. Upon successful authentication of the mobile station 280, the D-AAU 218 sends back the Access Response OUANP packet (step 422). This packet contains an RPA message that additionally contains an RPA Success field. The RPA Success field contains the user profile for the mobile station 280, which is obtained from the database 221. D-AAU 218 may also provide safety information. Security information may include, for example, a new Session Key 1, a random number (RAND) of Session Key 1, and the duration of the Session Key 1. The CPMM 256 then sends the RPA Success (PPD) to the mobile station 280 (step 424). CMPC 256 also authorizes the mobile station 280 by checking the user profile received from the D-AAU 218 (step 426).

B. Location Detection

In order to locate both the outgoing from the mobile device and the inbound for the mobile device location services, the location server may be located in the home network (i.e., in the OMP server 216). In this case, the OMP server 216 may perform authentication and authorization procedures based on the identity of the requester. These procedures can be performed, for example, (1) if the session key used to locate is needed (which is referred to as “Session Key 2” in these materials), (2) if the current Session Key 2 has expired, and so Further. Any one-way authentication can be performed (for example, authentication of the mobile station 280 by calling MD-5, as shown in FIG. 4A) or mutual authentication (for example, using AKA or other mechanisms).

FIG. 4B illustrates an exemplary call flow 450 for authenticating, authorizing, and setting a session key for locating. Call flow 450 uses the AKA procedure to authenticate mobile station 280.

For call flow 450, the mobile station 280 initially sends a Location Detection Session Key Request message to the OMP server 216 (step 462). This message requests a new Session Key 2 for location detection and includes the ISD for the mobile station 280. The OMP server 216 then sends the D-AAU 218 an Access Request OUANP (step 464). This package contains an RPA message, which additionally contains an RPA Response field with ISD. D-AAU 218 performs AKA procedures and generates a random number (CASE) and an authentication value (AUTH, AUTN) (step 466). D-AAU 218 then responds by sending back the Access Response OUANP packet (block 468). This packet contains an RPA message, which additionally contains an RPA Request field. The RPA Request field carries the AKA Call, which includes the AUTN and the CASE generated by D-AAU 218. The OMP server 216 receives the OUANP Access Response packet from the D-AAU 218 and sends the RPA Request with the AKA Call (on the PDA) to the mobile station 280 ( step 470).

Mobile station 280 receives an RPA Request from the OMP server 216, performs AKA procedures, and verifies the received AUTN. If the received AUTN is verified, then the mobile station 280 generates a new Session and RES Key 2, based on the received CASE (step 472). The mobile station 280 then responds by sending the RPA Response to the OMP server 216 with an AKA Response that includes a RES (step 474).

The OMP server 216 then re-submits the D-AAU 218 its initial Access Request OUANP packet (step 476). This packet contains an AKA RES with RES provided by the mobile station 280. The D-AAU 218 authenticates the mobile station 280 based on the AKA Response. Upon successful authentication of the mobile station 280, by checking the RES, the D-AAU 218 sends the Access Response CIDP packet to the OMP server 216 (step 478). This packet contains an RPA message, which further comprises an RPA Success field. The RPA Success field contains the user profile for the mobile station 280, which is obtained from the database 221. D-AAU 218 also provides security information. Security information may include, for example. Session Key 2, CASE of Key 2 sessions and the validity of Key 2 Sessions.

The OMP server 216 receives the Access Response OUANP packet from the D-AAU 218 and can save the user profile and Session Key 2 for its own use. The OMP server 216 then sends the RPA Success (PPD) to the mobile station 280 (step 480). The OMP server 216 subsequently authorizes the mobile station 280 by checking the user profile (step 482). The OMP server 216 then sends to the mobile station 280 a Location Detection Session Key Response message, which includes the duration of the Session Key 2 (step 484).

As shown in FIG. 4B, upon successful authentication of the mobile station 280, the D-AAU 218 can send security information (for example, Session Key 2, the duration of the Session Key 2) to the OMP server 216, which can then send security information to the mobile station 280. Session Key 2 may be used between the mobile station 280 and the OMP server 216 to open a position. Session Key 2 can be obtained for the following events:

- when the mobile station 280 subscribes service on the server 216 WMD;

- when the mobile station 280 or the OMP server 216 detects that the Session Key 2 has expired; or

- when the mobile station 280 (acting as a location client) requests location information from the OMP server 216.

Call flow 400 shows the use of the MD-5 algorithm for determining the location, and call flow 450 shows the use of AKA procedures for locating. Other security algorithms may also be used to determine location and location, and all are within the scope of the present invention. For example, the SAIRC (Cellular Authentication And Voice Encryption CAVE) algorithm can be used for access authentication. CHAP (Challenge Handshake Authentication Protocol, Mutual Authentication Protocol, PVA) and Mobile IP Protocol can be used for IP authentication. The CIRC, PVA, and Mobile IP algorithms are well known in the art.

B. Security and Protection

Authentication and Authorization

Authentication and authorization can be performed independently to determine the location and location, as described above. Authentication and authorization for location determination can be performed, for example, using the call flow 400 of FIG. 4A. Authentication and authorization for location detection can be performed, for example, using the call flow 450 of FIG. 4B.

Encryption

The location information can be sent as a user schedule and encrypted using Link Level Encryption, as described in IS-2000.5-C, entitled “High Level (Level 3) Signaling Standard for Extended Spectrum Systems cdma2000”, which is publicly available. Location information can also be encrypted using a session key (obtained by performing a procedure on a stream of 400 or 450 calls) and sent using end-to-end encryption. If pass-through encryption is used, then D-AAU 218 can generate various session keys from the root key (for example, “KEY” can be used as the root key). These different session keys can be provided to various network entities and can be used by them to encrypt location information.

Separate session keys can be obtained and can be used for location and location detection. Using separate session keys simplifies the WMD architecture and reduces security risks. Mobile station 280 supports security combining with network entities (eg, OMP server 216) in home network 210. The session key for this combination (Session Key 2) is not disclosed to any network entity outside home network 210. Location information exchanges between OMP server 216 and mobile station 280 may be signed and / or encrypted using Session Key 2.

The roaming mobile station 280 may support a different combination of security with network entities (eg, CPMCU 256 and OOPO 260) in the serving network 250. A separate session key (Session Key 1) is set up for objects in the serving network 250. Location information exchanges between the OOPO 260 and by the mobile station 280 or between the MSC 256 and the mobile station 280 may be signed and / or encrypted using the Session Key 1.

Session keys can also be used for message authentication and integrity checks. The use of session keys for message authentication / encryption and the validity period of each session key can be determined by operational parameters. These settings may take into account the data-defined policy. This makes it possible to select or adjust the degree of protection based on the significance of the information to be protected.

3. Mobile Device Outbound Location Service

For an outbound location service from a mobile device, the location client is located in the mobile station 280, and the location server can be located in the mobile station 280 or on the OMP server 216 (see Table 1). If the location server is located in the mobile station 280, then the location client requests location information from the mobile station 280.

A. Determination of Location

IS-801 supports many location methods. The method based on the Satellite Positioning System (MPS, SPS) allows you to provide an accurate position estimate for the mobile station based on signals received from a sufficient number of MSS satellites (usually four). The hybrid method allows providing a location estimate for the mobile station with medium accuracy based on signals received from a sufficient number of MSS satellites and base stations. The Improved Direct Link Trilateration (U-TLS, A-FLT) method provides a location estimate for a mobile station with reduced accuracy based on signals received from a sufficient number of base stations (usually three or more).

FIG. 3A shows an exemplary call flow 500 for performing an outgoing call from a mobile device with a method based on IS-801. The mobile station 280 initiates a data call to establish a PMTT session with the PDSN 270 (step 512). The mobile station 280 then sends to the CMPC 256 an Outgoing Request from the Mobile Positioning Device, which includes the ISD for the mobile station 280 (step 514). CMPC 256 receives this message and determines whether authentication and authorization should be performed for the mobile station 280. Authentication and authorization need not be performed, for example, if the authentication and authorization procedures were previously performed for the mobile station 280, and the Session Key 1 obtained through these procedures is still valid because the Session Key 1 has not expired. Authentication and authorization may be necessary, for example, if the authentication and authorization procedures have not been performed previously for the mobile station 280, or if the Session Key 1 has expired.

If authentication and authorization is not necessary, then steps 516, 518 and 520 are skipped. Otherwise, the call flow 400 is performed in FIG. 4A, and the CPU may or may not receive a new Session Key 1, a new SESSION Key 1 SESSION, and a new Session Key 1 validity period from step D-AAU 218 (step 516). If the CPMC 256 does not receive a new Session Key 1 from the D-AAU 218 in step 516, then steps 518 and 520 are skipped. If the CPU 256 receives a new Session Key 1 from the D-AAU 218 in step 516, then the CPU 256 sends the OPOP 260 a GEOPOSREQ message that includes this Session Key 1 (step 518). OOPO 260 then responds by sending a geoposreq message back to the CPU / CPU 256 (block 520). GEOPOSREQ and geoposreq messages are described in TIA / EIA / PN-4747. Step 516 may or may not be performed for the call flow 500, which is indicated by a dashed line in the form of a rectangle around step 516. Steps 518 and 520 may or may not be performed, and this is also indicated by the dashed line of a rectangle around the steps 518 and 520.

In either case, the CMPC 256 sends an Outgoing Response message from the Mobile Positioning Device to the mobile station 280 (step 522). This message includes the current Session Key 1 CASE, which is either (1) a new Session Key 1 CASE received from D-AAU 218 if this CASE is received as a result of authentication and authorization procedures at step 516, or (2) CASE Session Key 1 obtained during the previous authorization and authentication procedures. The mobile station 280 uses the Session Key 1 CASE from the CPMC 256 to receive the Session Key 1, which can then be used to sign and / or encrypt messages.

Then, between the mobile station 280 and OOPO 260 establish a session IS-801 location to determine the location of the mobile station 280 (step 524). All IS-801 messages for this IS-801 session can be authenticated and / or encrypted with Session Key 1. The mobile station 280 receives location information after the end of the IS-801 session. This location information may include a location estimate for the mobile station 280, accuracy or uncertainty for the location estimate, and so on. If the location determination is performed by the OOPO 260 using the mobile station 280, then the OOPO 260 may send the location information to the mobile station 280.

Upon successful termination of the IS-801 session, the location information may be cached (i.e., stored in the memory element) in the mobile station 280, the OMP server 216 and / or the CPU 256 for later use. If the location information is to be cached in the OMP server 216, then the mobile station 280 sends the location information (which can be authenticated and / or encrypted by Session Key 2) to the OMP server 216 (step 526). If the location information is to be cached in the CPMC 256, then the mobile station 280 sends the location information (which can be authenticated and / or encrypted with Session Key 1) to the CPMC 256 (step 528). Each of steps 526 and 528 may or may not be performed, which is indicated by a dashed line in the form of a rectangle around each of these steps.

FIG. 5B illustrates an exemplary call flow 550 for making an outgoing call from a mobile device with an ID cell method. The ID cell method provides identification of a serving cell with which the mobile station 280 is currently communicating. For the ID cell method, it is assumed that the mobile station 280 is located at a designated location that is associated with a serving cell. The designated location may be, for example, the location of the antenna for the serving cell, the location of the base station for the serving cell, or some other location within the coverage area of the serving cell. The accuracy of the location estimate for the mobile station 280 depends on the size of the serving cell.

For call flow 550, the mobile station 280 initiates a data call to establish a PMTT session with the PDSN 270 (step 552). The mobile station 280 then sends to the CPMM 256 a Request message from the Mobile Positioning Device, which includes the ISD for the mobile station 280 (step 554). The CPMC 256 subsequently determines the ID of the serving cell with which the mobile station 280 is currently communicating. MSC 256 then sends OOPO 260 a GEOPOSREQ message indicating that the ID cell method is being used (step 556). OOPO 260 receives this message from the CPMC 256 and sends back a geoposreq message that includes location information for the mobile station 280. This location information may include a location estimate for the mobile station (based on the ID of the serving cell), location accuracy, or uncertainty and etc.

CMPC 256 then sends to the mobile station 280 an Outgoing Response message from the Mobile Positioning Device, which includes location information for the mobile station 280 (block 560). The WMD server 216, the MCH 256, and / or the mobile station 280 may cache the location information for later use. If the location information is to be cached in the OMP server 216, then the mobile station 280 sends the location information (which can be authenticated and / or encrypted by Session Key 2) to the OMP server 216 (step 562).

B. Location Detection

Once the location information for the mobile station 280 is obtained by performing location determination, this information can be cached for later use. The location information may be cached in the mobile station 280, the CPU 256, and / or the OMP server 216. Where to store location information in the cache can be determined based on various factors, such as, for example, the policy of the service provider, user subscription, and so on.

For outgoing from the mobile location device, the location client is located in the mobile station 280, and the location server can be located in the mobile station 280 or on the OMP server 216. Table 2 summarizes the various call flows that can be used to provide location information for outgoing from a mobile location detection device. The specific call flow to use for locating depends on where the location client is located and where location information is cached.

table 2
Outgoing from a Mobile Device for Locating a Location Where is the WMD Client Where is the WMD Server Where Cached Location Information Location Detection Method Mobile station Mobile station Mobile station Directly provide location information Mobile station Mobile station CPOM 256 Use call flow 600 of FIG. 6A Mobile station OMP Server 216 OMP Server 216 Use call flow 630 of FIG. 6B Mobile station OMP Server 216 CPOM 256 Use call flow 660 of FIG. 6B

If the location server is located in the mobile station 280 and the location information is also cached in the mobile station 280, then the location server can receive location information from the memory and directly provide it to the location client.

FIG. 6A shows an exemplary call flow 600 for performing location detection at which a location server is located in the mobile station 280 and location information is cached in the CPMC 256. The mobile station 280 initiates a data call to establish a PMT session with PDSA 270 (step 612). The mobile station 280 (acting as a location client) then sends to the CPU 256 a Location Service Request message that includes the ISD for the mobile station 280 (step 614). CMPC 256 receives this message and determines whether authentication and authorization should be performed for the mobile station 280. If authentication and authorization are necessary, then the call flow 400 of FIG. 4A is performed to obtain a new Session Key 1 and a new Session Key 1 SESSION (step 616 ) Otherwise, step 616 is skipped. Step 616 may or may not be performed for the call flow 600, which is indicated by a dashed line in the form of a rectangle around step 616. The 400 call flow (instead of the 450 call flow) is used to authenticate, authorize, and set the session key, because the CPU 256 is located in the serving network 250.

CMPC 256 then sends the Location Service Response message to the mobile station 280, which includes location information that has been cached for the mobile station 280 (step 618). If step 616 has been completed, then the CPU 256 may include the new Session Key 1 CASE as part of this Location Service Response message and may also sign and / or encrypt the location information with the new Session Key 1 received in step 616. If step 616 has not been completed, then the MSC 256 may sign and / or encrypt the location information with the Session Key 1 obtained in the previous authentication and authorization procedure, if this Session Key 1 has not expired. For call flow 600, the CPU-MSC 256 actually functions as a location server.

FIG. 6B shows an exemplary call flow 630 for performing location detection at which the location server is located in the OMP server 216 and the location information is also cached on the OMP server 216. The mobile station 280 initiates a data call to establish a PMTT session with the PDSN 270 (step 632). The mobile station 280 (acting as the location client) then sends the OMP server 216 a Location Service Request message that includes the ISD for the mobile station 280 (step 634). The OMP server 216 receives this message and determines whether authentication and authorization should be performed for the mobile station 280. If authentication and authorization are necessary, then the call flow 450 is performed in FIG. 4B and a new Session Key 2 and a new Session Key 2 expire ( step 636). Otherwise, step 636 is skipped. Step 636 may or may not be performed for call flow 630, which is indicated by a dashed line in the form of a rectangle around step 636.

The OMP server 216 then sends the Location Service Response message to the mobile station 280, which includes location information that has been cached for the mobile station 280 (step 638). If step 636 has been completed, then the OMP server 216 may also include the new Session Key 2 expiration date in this Location Service Response message and may sign and / or encrypt the location information with the new Session Key 2. If step 636 has not been completed, then the OMP server 216 may sign and / or encrypt the location information with the Session Key 2 obtained in the previous authentication and authorization procedure if this Session Key 2 has not expired.

FIG. 6B shows an exemplary call flow 660 for performing location detection at which the location server is located on the WMD server 216 and the location information is cached in the CMPC 256. The mobile station 280 initiates a data call to establish a PMT session with PDSA 270 (step 662). The mobile station 280 (acting as the location client) then sends the OMP server 216 a Location Service Request message that includes the ISD for the mobile station 280 (step 634). The OMP server 216 receives this message and determines that it does not have location information that meets the requirements of the CPC for the mobile station 280. The OMP server 216 then requests the location information for the mobile station 280 from the CPMS 256. This is achieved by sending a Request message to the CPPC 256. Location Services, which includes the ISD (block 666). The OMP server 216 can obtain the IP address of the CPMC 256 by performing a call flow 350 of FIG. 3B. CMPC 256 receives the request from the OMP server 216 and sends back the Location Service Response message (step 668). This message includes location information that has been cached at the CPMC 256 for the mobile station 280.

The OMP server 216 then determines whether authentication and authorization need to be performed for the mobile station 280. If authentication and authorization are necessary, then the call flow 450 is performed in FIG. 4B, a new Session Key 2 and a new Session Key 2 expire (block 670) . Otherwise, step 670 is skipped. Step 670 may or may not be performed for call flow 660, which is indicated by a dashed line in the form of a rectangle around step 670.

The OMP server 216 then sends the Location Service Response message to the mobile station 280, which includes location information for the mobile station 280 (step 672). If step 670 has been completed, then the OMP server 216 may also include the new Session Key 2 expiration date in this Location Service Response message and may sign and / or encrypt the location information with the new Session Key 2. If step 670 has not been completed, then the OMP server 216 may sign and / or encrypt the location information with the Session Key 2 obtained in the previous authentication and authorization procedure if this Session Key 2 has not expired.

4. Inbound Mobile Location Service

For an incoming location service mobile device, the location client is located in the OMP provider, and the location server can be located in the mobile station 280 or on the OMP server 216 in the home network 210 (see Table 1).

An OMP session inbound for a mobile device may be initiated by the network if the mobile station 280 (which is the target mobile station) has established an always-on data session and is ready to receive location requests from the OMP server 216. After the power of the mobile station 280 is turned on, it can initiate a data session. In this case, the LED server 262 can be updated with the IP address of the mobile station 280. The mobile station 280 can register its IP address with the OMP server 216 and can perform authentication and authorization procedures to obtain a session key for use in signing and / or encrypting messages . This data session is supported as much as the power of the mobile station 280 is turned on. If the OMP server 216 sends an LED Request message about the IP address of the mobile station 280, then the LED server 262 can quickly respond with the LED response message because the LED server 262 already has the IP address of the mobile station 280.

7 shows an exemplary call flow 700 for establishing the IP address of a mobile station 280 when it is not always on. Call flow 700 uses SMS messaging to start mobile station 280 to initiate an OMP session from the mobile device. The IP address of the mobile station 280 is set further as part of the WMD session originating from the mobile device.

For the call flow 700, the OMP server 216 sends an End-to-End Delivery (SMDPP) SMS message to the message switching center 222 that serves the mobile station 280 (block 712). This SMDPP message includes the Active Delivery Notification and IMSI of the mobile station 280. The Active Delivery Notification is used to start the mobile station 280 to initiate a data call so that its IP address can be set. IMSI (International Mobile Subscriber Identity MIMA) is a number that uniquely identifies a mobile station 280. When sending an SMDPP message, the OMP server 216 starts a timer that is used to limit the time to wait for a response to SMDPP messages. The message switching center 230 receives the SMDPP message from the OMP server 216 and sends the smdpp result back (step 714).

The message switching center 230 needs to know the SMS address of the current serving network for the mobile station 280. The SMS address is used to send SMS messages to the mobile station 280. The message switching center 230 then sends an SMS Start Request (SMSREQ) message to the RDP 224 (step 716). If the RDP 224 has an SMS address of the serving network 250 (which is the current serving network for the mobile station 280), then the RDP 224 responds with an smsreq message that contains this SMS address (step 718). Otherwise, the RDP 224 sends an SMSREQ message to the serving network 250 (not shown in FIG. 7).

After receiving the SMS address of the serving network 250, the message switching center 230 sends an SMDPP message to the MSC 272 in the serving network 250 (step 720). The SMDPP message is sent using the SMS address received from the RDP 224 or the service network 250 in step 718. The MSC 272 receives the SMDPP message from the message switching center 230 and sends a personal call to the mobile station 280. The MSC 272 also retrieves the Active Delivery Notification from the received SMDPP message , includes the Active Delivery Notification in the SMS Delivery Request (SMD-REQ) message and sends the SMD-REQ message over the air to the mobile station 280 (step 722). Mobile station 280 receives an SMD-REQ message and responds with an SMS Delivery Confirmation (SMD-ACK) message (block 724). The MSC 272 receives the SMD-ACK message from the mobile station 280 and issues an smdpp message to the message switching center 230 (step 726).

The Active Delivery notification prompts the mobile station 280 to make an outgoing data call, establish a PMTT session with the PDSN 270, and obtain an IP address (step 728). To provide an IP address for the mobile station 280, the IPCP or Mobile IP procedure that is known in the art can be used. The mobile station 280 then starts an OMP session originating from the mobile device with the OMP server 216 (step 730).

For an incoming location service device for the mobile device, the OMP server 216 can detect the IP address of the SMPC 256 by using procedures in the call flow 350.

A. Positioning

If the location information is cached in the mobile station 280 or on the OMP server 216, then there is no need to initiate a location determination by the network because the mobile station 280 will start a location session. If the location information is allowed to be cached in the CPMC 256, then the WMD inbound session for the mobile device may be initiated by the CPMC 256.

FIG. 8A illustrates an exemplary call flow 800 for making an inbound call to a mobile device using an IS-801 based method. MSC 256 sends an Inbox Request message for the Mobile Positioning Device to the mobile station 280 (block 812). The mobile station 280 receives this message from the CPMC 256 and sends back the Incoming Response message for the Mobile Positioning Device, which includes the ISD for the mobile station 280 (step 814). The remaining steps 816-828 in call flow 800 are the same as steps 516-528 in call flow 500 of FIG. 5A, except that various messages are used. In particular, for step 822, the Incoming Request message is used for the Mobile Positioning Device, while for step 522, the Outgoing Response from the Mobile Positioning Device is used.

FIG. 3B illustrates an exemplary call flow 850 for making an inbound call to a mobile device using an ID cell method. Call flow 850 includes steps 856, 858, 860 and 862 that correspond to steps 556, 558, 560 and 562, respectively, in call flow 550 of FIG. 5B. Steps 552 and 554 in the call flow 850 are omitted. In addition, for step 860, an Incoming Request message is used for the Mobile Positioning Device, while for step 560, an Outgoing Response message from the Mobile Positioning Device is used.

B. Location Detection

For the incoming mobile location device, the location client is located at the WMD provider 202x, which may be the WMD provider 202a in the home network 210, the WMD provider 202b in the serving network 250, or the WMD provider 202c in the third party network 290 of FIG. 2. The location server can be located in the mobile station 280 or the OMP server 216 in the home network 210. The location information can be cached in the OMP server 216, the CPU / CPU 256, or the mobile station 280. Table 3 shows the various call flows that can be used to obtain location information for an incoming location device for the mobile device. The specific call flow to use for locating depends on where the location server is located and where the location information is cached.

Table 3
Inbox for Mobile Device Location Detection Where is the WMD Client Where is the WMD Server Where Cached Location Information Location Detection Method WMD Provider Mobile station Mobile station Directly provide location information WMD Provider OMP Server 216 OMP Server 216 Use call flow 900 of FIG. 9A WMD Provider OMP Server 216 CPOM 256 Use call flow 930 of FIG. 9B WMD Provider OMP Server 216 Mobile station Use call flow 960 of FIG. 9B

If the location server is located in the mobile station 280 and the location information is also cached in the mobile station 280, then the location server can obtain location information from the memory and provide it directly to the location client.

FIG. 9A shows an exemplary call flow 900 for performing location detection at which the location server is located in the OMP server 216, and the location information is also cached in the OMP server 216. The OMP provider 202x (acting as the location client) sends the OMP server 216 a Location Service Request message (block 912). This message requests location information for the mobile station 280, which is the target mobile station. For call flow 900, it is assumed that the location information cached in the WMD server 216 may satisfy the requirements of the CPC. The OMP server 216 may need to authenticate and authorize the location client (i.e., the OMP provider 202x) through an authentication and authorization procedure, which are not shown in FIG. 9A for simplicity.

The user profile for the mobile station 280 may indicate that user verification is required before each location information is disclosed for the mobile station 280. In this case, the MSS server 216 and the mobile station 280 perform mutual authentication using the call flow 450 of FIG. 4B (step 914). The OMP server 216 then sends the User Verification Request message (which can be signed and / or encrypted using the Session Key 2 obtained at step 914) to the mobile station 280. The mobile station 280 responds by sending back the User Verification Response message (which may also be signed and / or encrypted using the Session Key 2 obtained in step 914). This message indicates that the disclosure of location information for the mobile station 280 is allowed. Since steps 914, 916, and 918 may or may not be performed for call flow 900, depending on the user profile, these steps are outlined with dashed lines in the form of rectangles. The OMP server 216 then sends the Location Service Response Response message to the OMP provider 202x, which includes location information for the mobile station 280 (step 920).

FIG. 9B shows an exemplary call flow 930 for performing location detection at which the location server is located in the OMP server 216 and the location information is cached in the CPU 256. The OMP provider 202x (acting as the location client) is sent to the server 216 an OMP location service request message for location information for the mobile station 280 (block 932). An OMP server 216 may need to authenticate and authorize a location client, which is not shown in FIG. 9B for simplicity. Then, steps 934, 936, and 938 can be performed if the user profile for the mobile station 280 indicates that user verification is required before each location information is disclosed for the mobile station 280. Steps 934, 936 and 938 correspond to steps 914, 916 and 918, respectively, of FIG. .9A.

Location information for the mobile station 280 may be cached in the OMP server 216. However, it is assumed that this location information does not meet CPC requirements. The OMP server 216 may then decide to obtain location information for the mobile station 280 from the CMPC 256. This is achieved by sending a Location Service Request message to the CMPC 256 (block 940). If the CPMC 256 has the required location information for the mobile station 280, then it issues this location information to the OMP server 216 in the Location Service Response message (step 942). Otherwise, the CPMC 256 initiates a location session (using the call flow 800 in FIG. 8A or call flow 850 in FIG. 8B) to obtain location information, which is then sent back to the OMP server 216. The OMP server 216 then sends the Location Service Response response message to the provider 202x OMP, which includes location information for the mobile station 280 (step 944).

FIG. 9B shows an exemplary call flow 960 for performing location detection at which the location server is located in the WMD server 216 and the location information is cached in the mobile station 280 (which is the target mobile station). The OMP provider 202x (acting as the location client) sends the OMP server 216 a Location Service Request message for location information for the mobile station 280 (step 962). The OMP server 216 may need to authenticate and authorize a location client, which is not shown in FIG. 9 for simplicity. Location information for the mobile station 280 may be cached in the OMP server 216. However, it is assumed that this location information does not satisfy CPC requirements. The OMP server 216 may then decide to obtain location information from the mobile station 280.

If the user profile for the mobile station 280 indicates that user verification is required before the location information is disclosed, then mutual authentication is performed between the OMP server 216 and the mobile station 280 (step 964). The OMP server 216 then sends a Location Service Request message to the mobile station 280 (step 966). In this message, the User Verification Required field is set to "1" if user verification is necessary, and to "0" if there is no need for user verification. The mobile station 280 then verifies the user, if necessary, as indicated in the Required User Verification field. The mobile station 280 then sends to the OMP server 216 a Location Service Response message that includes location information for the mobile station 280 (step 968). Messages exchanged between the OMP server 216 and the mobile station 280 in steps 966 and 968 can be signed and / or encrypted using the Session Key 2 obtained in step 964. The OMP server 216 then sends the Location Service Response message to the 202x OMP, which includes location information for the mobile station 280 (block 970).

In order to locate both for outgoing from a mobile device and for incoming cases for a mobile device, “ownership” of location information is determined by where the location server is located (that is, either in the mobile station 280 or on the OMP server 216). The owner of location information is an authoritative source for information and may apply its own rules and policies with respect to information disclosure.

If the location server is located in the OMP server 216, then the OMP server 216 controls the disclosure of location information regardless of where the location client can be located. The OMP server 216 can arbitrarily perform authentication and authorization if the mobile station 280 is involved in location detection (for example, if the location information is cached in the mobile station 280).

If the location server is located in the mobile station 280, then the mobile station 280 controls the disclosure of location information regardless of where the location client can be located. However, sending all requests for this location information to the mobile station 280 may result in additional delays. Additional delays can be caused, for example, if the mobile station 280 is idle, busy or out of coverage for a short moment.

In the home network 210, an OMP proxy server can be provided, and it can be used as a proxy server for the mobile station 280 to locate. Mobile station 280 may send its location information to the OMP proxy as well as its disclosure rules / policies. Requests for location information for the mobile station 280 can then be sent to the proxy server OMP, which may be able to serve these requests more efficiently than the mobile station 280. For these requests, the proxy server OMP will act on behalf of the mobile station 280 and apply those the same disclosure rules / policy as the mobile station 280. The OMP proxy server may also request updated location information from the mobile station 280 when necessary. For example, an OMP proxy server may request updated location information from the mobile station 280 if the request from the location client cannot be satisfied with the current location information for the mobile station 280, possibly because it is irrelevant or may not meet the requirements of the CPC.

5. Accounting and Billing (Billing)

Accounting and billing (billing) can be performed on the OMP server 216 within the home network 210 and / or the MSC 256 within the serving network 250. The MSC 256 can generate a detailed call registration (DRC) for each location request. Accordingly, the OMP server 216 may generate an ADR for each location discovery request. DRV can be used for accounting, billing and / or other purposes. Table 4 shows the various elements that can be included in the DRV.

Table 4 Items Description Location Client ID Identity of a location client requesting location information Target Mobile Station ID Identity of the target mobile station to be searched for (e.g., IMSI of the target mobile station) Success or Failure Indicates whether location information has been provided. Time stamp Time when location information was determined Response Time Time at which an answer was provided Location Assessment Estimation of the location of the target mobile station and confidence in this location estimate

FIG. 10A shows an exemplary call flow 1000 for an ADR message for each location discovery request received by the OMP server 216. The location client 204 sends to the OMP server 216 a Location Service Request message for location information for the mobile station 280, which is the target mobile station (step 1012). The location client 204 may be a mobile station 280 or an OMP provider 202a, 202b or 202c. Depending on where the location information is cached, various call flows may be used to obtain location information, as described previously. The OMP server 216 then sends the Location Service Response message to the location client 204, which includes location information for the mobile station 280 (step 1014). The OMP server 216 generates an RTD to disclose location information to the location client 204. The OMP server 216 then sends the D-AAU 218 an Account Request message that includes an ADR (step 1016). DRV can be stored D-AAU 218 and can be used for accounting, billing and / or other purposes. D-AAU 218 responds by sending back the Accounting Response message (step 1018).

FIG. 10B illustrates an exemplary call flow 1050 for reporting an ADR for each location request received by the MSC 256. The mobile station 280 sends the MSC 256 a Location Determination Request message for locating the mobile station 280 (block 1052). Various procedures can be used to determine the location of the mobile station 280, as described previously. CMPC 256 then sends a Location Determination Response message, which includes location information for mobile station 280 (block 1054). SMPC 256 generates an RTD for location request. MSC 256 then sends the D-AAU 218 an Account Request message that includes an ADR (step 1056). DRV can be stored D-AAU 218 and can be used for accounting, billing and / or other purposes. D-AAU 218 responds by sending back the Accounting Response message (block 1058).

6. System

11 is a structural diagram of various objects in a network 200. Mobile station 280 may be a mobile device, a computer with a wireless modem, a standalone positioning unit, or some other module. Base station 274x may perform the function of BSC / FUP 274 of FIG. 2. For simplicity, only one network entity 1100 is shown in FIG. 11. The network entity 1100 can be any of the network entities shown in FIG. 2 (for example, an OMP server 216, CPU 256, OOPO 260, an OMP provider 202a, 202b, or 202c or some other network entity).

On a forward link, base station 274x transmits data, pilot, and signaling to mobile stations within its coverage area. These various types of data are processed (e.g., encode, modulate, filter, amplify, quadrature modulate and upconvert) with a modulator / transmitter (Mod / PRDT) 1120 to provide a forward link modulated signal, which is then transmitted via antenna 1122 to mobile stations .

Mobile station 280 receives modulated forward link signals from one or more base stations (which include base station 274x) to antenna 1152. A receiver input from antenna 1152 (which may include many received signals) is fed to a receiver / demodulator ( PfP / Demod) 1154. The PfP / Demod 1154 then processes the receiver input in an additional manner to provide various types of information that can be used for position determination and location detection . For example, PWM / Demod 1154 can provide the arrival time of received signals (which can be used to determine the location), decrypted messages used for call flows described previously and so on. The processor 1160 performs various processing and control functions for the mobile station 280, and the memory element 1162 stores program codes and data for the processor 1160.

On the reverse link, mobile station 280 can transmit data, pilot, and / or signaling to base station 274x. These various types of data are processed by a modulator / transmitter (Mod / PRDT) 1164 to provide a modulated reverse link signal, which is then transmitted via antenna 1152. Base station 274x receives a modulated reverse link signal from mobile station 280 to antenna 1122, and an input signal the receiver from the antenna 1122 is fed to the receiver / demodulator (PRMN / Demod) 1124. The PRMN / Demod 1124 then processes the input signal of the receiver in an additional way to provide various types of information, which can then be given to the processor 1110. The processor 1110 performs various processing and control functions for the base station 274x, and the memory element 1112 stores program codes and data for the processor 1110. The serial port 1114 allows the base station 274x to exchange data with other network entities.

Within the network entity 1100, the serial port 1136 allows the entity 1100 to communicate with other network entities. The processor 1130 performs various processing and control functions for the object 1100, and the memory element 1132 stores program codes and data for the processor 1130. A database 1134 can be used to store suitable information. For example, database 1134 may implement a database 221 or RDP 224 of FIG. 2.

To determine the location, the location function 1172 (F Odd, Det F) in the mobile station 280 may interact with the peer location function 1142 in the network entity 1100 to perform location determination. Functions 1142 and 1172 can be performed by any of the call flows described above for positioning. To locate a location, a location detection function 1174 (F Ob, Dis F) in the mobile station 280 may interact with a peer location detection function 1144 in the network entity 1100 to perform location detection. Function 1144 may implement a location client or location server, and function 1174 may implement a location client or location server, or both of them. Functions 1144 and 1174 may be performed by any of the call flows described above for location detection.

The system, method and device described in these materials may be implemented by various means, such as hardware, software, or a combination thereof. When executed by hardware, the system, method and device can be implemented in the form of one or more specialized integrated circuits (ASIC, ASIC), digital signal processors (DSP), digital signal processing devices (DSPD, DSPD), programmable logic devices (PLU , PLD), user-programmable gate arrays (FPGAs, FPGAs), processors, controllers, microcontrollers, microprocessors, other electronic modules designed to perform the functions described in these materials, or in the form of okupnosti these devices.

In software execution, the method described in these materials can be implemented by modules (e.g., procedures, functions, and so on) that perform the functions described above. Software codes may be stored in a memory element (e.g., memory element 1112, 1132 or 1162 of FIG. 11) and executed by a processor (e.g., processor 1110, 1130 or 1160). The memory element can be performed in the processor itself or can be external to the processor, in the latter case it can be connected to transmit signals to the processor by various means known from the prior art.

Headings are included in this description as reference information and in order to facilitate the finding of some sections. These headings are not intended to limit the scope and concepts disclosed in the sections below them, and these concepts may be applicable in other sections throughout the description.

The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make and use the present invention. Various modifications to these embodiments are apparent to those skilled in the art, and the universal principles defined herein can be applied to other embodiments without altering the nature and scope of the present invention. Thus, the present invention is not limited to the embodiments presented herein, but has the broadest scope consistent with the principles and new features disclosed in the present materials.

Claims (43)

1. A method of providing location services (WMD), including:
receiving a request for location information for a mobile station;
performing location determination through a first set of at least one network entity to obtain suitable location information for the mobile station in response to a request for location information when the present location information for the mobile station is unavailable or inappropriate; and
performing location detection through a second set of at least one network entity to provide suitable location information for the mobile station in response to a request for location information, and skipping location when the present location information for the mobile station is available and suitable. 2. The method according to claim 1, further comprising:
performing authentication and authorization to determine the location based on the first security procedure; and
performing authentication and authorization to locate based on the second security procedure. 3. The method according to claim 2, in which the first security procedure is based on the MD-5 algorithm, and the second security procedure is based on the Authentication and Key Negotiation (ASK) procedure. 4. The method according to claim 1, further comprising:
performing installation of a first session key to obtain a first session key, wherein the first session key is used to authenticate and encrypt messages exchanged with the first set of at least one network entity; and
performing installation of a second session key to obtain a second session key, the second session key being used to authenticate and encrypt messages exchanged with the second set of at least one network entity. 5. The method according to claim 1, in which the location and location detection is performed in two separate WMD sessions. 6. The method of claim 1, further comprising: caching location information for the mobile station, wherein the location detection is performed using cached location information for the mobile station. 7. The method according to claim 1, wherein the first set of at least one network entity is located in a serving network for the mobile station, and the second set of at least one network entity is located in a home network for the mobile station. 8. The method of claim 1, wherein the location detection is performed by a location client and a location server. 9. The method of claim 8, wherein the second set of at least one network entity includes an OMP provider, wherein the location client is located in a mobile station or OMP provider. 10. The method of claim 8, wherein the second set of at least one network entity includes an OMP server, the location server being located in the mobile station or OMP server. 11. The method according to claim 1, in which the first set of at least one network object includes an object position determination (OOP). 12. The method according to claim 11, wherein the first set of at least one network entity further includes a positioning center of a served mobile device (CPOMU). 13. The method according to claim 11, in which the first set of at least one network object further includes a home object authentication, authorization, and accounting (D-AAU). 14. The method of claim 1, wherein the second set of at least one network entity includes an OMP server. 15. The method according to 14, in which the second set of at least one network object further includes a home object authentication, authorization and accounting (D-AAU). 16. The method of claim 1, wherein the location information for the mobile station includes estimating the location for the mobile station. 17. The method according to clause 16, in which the location information for the mobile station further includes uncertainty for estimating the location for the mobile station. 18. A device for providing location services (OMP), including:
means for receiving a request for location information for the mobile station;
means for performing location determination by a first set of at least one network entity to obtain suitable location information for the mobile station in response to a request for location information when the present location information for the mobile station is unavailable or inappropriate; and
means for performing location detection through a second set of at least one network entity to provide suitable location information for the mobile station in response to a request for location information, and skipping determination
locations when the current location information for the mobile station is available and appropriate. 19. The device according to p. 18, further comprising:
means for performing authentication and authorization for determining the location based on the first security procedure; and
means for performing authentication and authorization for locating based on the second security procedure. 20. The device according to p. 18, further comprising: means for performing the installation of the first session key, to obtain the first session key, the first session key being used for authentication and encryption of messages exchanged with the first set of at least one network object; and
means for performing installation of a second session key to obtain a second session key, wherein the second session key is used to authenticate and encrypt messages exchanged with the second set of at least one network entity. 21. The apparatus of claim 18, further comprising: means for storing location information for the mobile station in the cache, the location detection being performed using the location information in the cache for the mobile station. 22. A wireless mobile station, including:
processor involved for
receiving a request for location information for the mobile station;
performing a first function to obtain suitable location information for the mobile station in response to a request for location information when the present location information for the mobile station is unavailable or inappropriate, and
performing a second function to provide suitable location information for the mobile station in response to a request for location information, and skipping the first function to obtain suitable location information when the present location information for the mobile station is available and suitable,
moreover, the first function interacts with at least one peer first function located in the first set of at least one network object to obtain suitable location information, and the second function interacts with at least one peer second function located in a second set of at least one network entity to provide suitable location information. 23. A material storage medium containing a software product for implementing a method for providing location services (WMD), the software product including executable instructions for
receiving a request for location information for the mobile station;
performing the first function to obtain suitable location information for the mobile station in response to a request for location information when the present location information for the mobile station is unavailable or inappropriate, the first function interacting with at least one peer first function located in the first a set of at least one network entity to obtain suitable location information; and
performing a second function to provide suitable location information for the mobile station in response to a request for location information, and skipping the first function to obtain suitable location information when the present location information for the mobile station is available and suitable, the second function interacting with at least at least one peer second function located in the second set of at least one network entity to provide suitable location information position. 24. A method of providing location services (WMD), including:
receiving a request for location information for a mobile station;
performing location determination through the first WMD session to obtain suitable location information for the mobile station in response to a request for location information when the present location information for the mobile station is unavailable or inappropriate; and
performing location detection through a second WMD session to provide suitable location information for the mobile station in response to a request for location information, and skipping location when the present location information for the mobile station is available and appropriate. 25. The method according to paragraph 24, in which the first and second WMD sessions are performed at different times. 26. The method according to paragraph 24, further comprising:
performing authentication and authorization for the first WMD session based on the first security procedure; and
performing authentication and authorization for the second WMD session based on the second security procedure. 27. The method according to paragraph 24, further comprising:
performing installation of a first session key to obtain a first session key for use in a first WMD session; and
performing installation of a second session key to obtain a second session key for use in a second WMD session. 28. The method according to paragraph 24, further comprising: providing a first detailed call recording (DRV) for the first WMD session; and providing a second DRV for the second WMD session. 29. A device for providing location services (WMD), including:
means for receiving a request for location information for the mobile station;
means for performing location determination by the first WMD session to obtain suitable location information for the mobile station in response to a request for location information when the present location information for the mobile station is unavailable or inappropriate; and
means for performing location detection through the second WMD session, to provide suitable location information for the mobile station in response to a request for location information, and skipping location when the present location information for the mobile station is available and suitable. 30. A method for providing location services (WMD), including:
obtaining suitable location information for mobile
the station in response to a first request for location information for the mobile station when the present location information for the mobile station is unavailable or inappropriate;
providing suitable location information to the first application in response to a first request for location information for the mobile station, and skipping receiving suitable location information when the present location information for the mobile station is available and suitable; and
providing suitable location information to the second application in response to a second location information request for the mobile station, and skipping obtaining suitable location information when the present location information for the mobile station is available and suitable. 31. The method of claim 30, wherein the location information is obtained by performing location determination once by one location session, the location information being provided to the first and second applications by performing location detection twice by two location detection sessions. 32. The method according to clause 30, further comprising: placing in the cache memory location information in a mobile station or network entity. 33. The method according to item 30, further comprising: providing a first detailed call registration (DRV) for
providing location information to the first application; and providing a second RTD to provide location information to the second application. 34. The method of claim 30, wherein the first application is located in the first network and the second application is located in the second network. 35. A device for providing location services (WMD), including:
means for obtaining suitable location information for the mobile station in response to a first request for location information for the mobile station when the present location information for the mobile station is unavailable or inappropriate;
means for providing suitable location information to the first application in response to a first request for location information for the mobile station, and skipping receiving suitable location information when the present location information for the mobile station is available and suitable; and
means for providing suitable location information to the second application in response to a second location information request for the mobile station, and skipping receiving suitable location information when the present location information for the mobile station is available and suitable. 36. A method for providing location services (WMD), including:
receiving a request for location information for a mobile station;
performing location determination by at least one network entity in a serving network, for
obtaining suitable location information for the mobile station in response to a request for location information when the present location information for the mobile station is unavailable or inappropriate; and
performing location detection through at least one network entity in the home network to provide suitable location information for the mobile station in response to a request for location information, and skipping location when the present location information for the mobile station is available and suitable. 37. The method according to clause 36, further comprising:
performing installation of a first session key to obtain a first session key, wherein the first session key is used to authenticate and encrypt messages exchanged with at least one network entity in a serving network; and
performing installation of a second session key to obtain a second session key, the second session key being used to authenticate and encrypt messages exchanged with at least one network entity in the home network. 38. The method according to clause 36, in which at least one network object in the serving network includes a positioning center of the served mobile object (CPOMU), and the method further includes:
Address determination by Internet Protocol (IP) of the CPU. 39. The method of claim 38, wherein the IPPCS IP address is determined using a fully qualified domain name for the CPPCS. 40. The method according to § 38, in which the location detection is performed by the CPU. 41. The method according to clause 36, further comprising: sending a message to the mobile station, to cause the mobile station to initiate the WMD session, to perform location determination. 42. The method according to clause 36, further comprising: storing location information in a cache in a mobile station, a network entity in a serving network, a network entity in a home network, or a combination thereof. 43. A device for providing location services (WMD), including:
means for receiving a request for location information for the mobile station;
means for performing location determination by at least one network entity in the serving network to obtain suitable location information for the mobile station in response to a request for location information when the present location information for the mobile station is unavailable or inappropriate; and
means for performing location detection by at least one network entity in the home network to provide suitable location information for the mobile station in response to a request for location information, and skipping the location when
The present location information for the mobile station is accessible and suitable.

Images