RU2396733C2 - Supporting emergency calls in mode of channels switching - Google Patents

Abstract

FIELD: information technologies.

SUBSTANCE: procedures may be used for various networks 3GPP and 3GPP2, various architectures for detection of location and various types of user equipment (UE). UE establishes call in mode of channels switching with the help of wireless network for emergency services. UE interacts with server of location detection specified by wireless network. UE detects location in user plane with the help of location detection server in process of call in mode of channels switching in order to obtain assessment of UE position. UE exchanges data with PSAP, which may be selected on the basis of position assessment, for emergency call in mode of channels switching. UE may realise positioning with the help of location detection server to obtain updated assessment of UE position, for instance each time when requested by means of PSAP.

EFFECT: improved routing of emergency calls.

51 cl, 10 dwg

Description

FIELD OF THE INVENTION

The present invention generally relates to communications, and more particularly to emergency call support techniques.

BACKGROUND

Wireless networks are widely deployed to provide various communication services, such as voice, video, packet data, messaging, broadcast, and the like. These wireless networks can be multiple access networks capable of communicating with multiple users by sharing available network resources. Examples of such multiple access networks include code division multiple access (CDMA) networks, time division multiple access (TDMA) networks, frequency division multiple access (FDMA) networks and orthogonal FDMA networks ( OFDMA).

Wireless networks typically support communications for users who have subscribed to the services of these networks. Subscribing to services may be associated with information on security, routing, quality of service (QoS), billing, etc. Subscription related information can be used to make calls with a wireless network.

The user may place an emergency voice call with a wireless network, which may or may not be the home network for which the user has a subscription to services. The main problem is to route the emergency call to the appropriate public safety answering point (PSAP) that can serve the call. This may entail obtaining an estimate of the intermediate position for the user and determining the appropriate PSAP based on the evaluation of the temporary position. The problem is complicated if the user is roaming and / or has no subscription to services on any network.

Therefore, in the art there is a need to support emergency calls.

SUMMARY OF THE INVENTION

This document describes techniques for supporting emergency calls in circuit switched mode. The techniques can be used for various 3GPP and 3GPP2 networks, various location architectures and subscriber units (UEs) with or without subscription to services.

In an embodiment, the UE establishes a circuit switched call with a wireless network for emergency services. The UE communicates with the location server indicated by the wireless network. The UE performs user plane positioning using the location server during a circuit switched call to obtain a location (position) estimate of the UE. User plane location means a process for determining the location of a target UE in which signals are transmitted between the UE and the location server using data transmission capabilities provided by a serving wireless network and / or other networks. User plane positioning can be based on a user plane solution / architecture, such as OMA Reliable User Plane Location (SUPL) or 3GPP2 X.S0024. The transmission of signals for determining the location in the user plane can be carried out through communication in the mode of packet switching. The UE sets up a circuit switched emergency call with PSAP, which can be selected based on the location estimate of the UE. The UE may perform positioning using the location server to obtain an updated location (position) estimate of the UE, for example, each time requested by the PSAP.

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

BRIEF DESCRIPTION OF THE DRAWINGS

Figure 1 illustrates a deployment that supports emergency circuit-switched calls.

2 illustrates the architecture of 3GPP and 3GPP2 networks.

3 illustrates a network architecture for determining SUPL location.

Figures 4, 5 and 6 illustrate several message flows for an emergency call in circuit switching mode using SUPL location.

7 illustrates a network architecture for locating an X.S0024.

FIG. 8 illustrates a message flow for an emergency call in circuit switched mode using X.S0024 location.

9 illustrates communication protocols between various entities.

Figure 10 illustrates a block diagram of various objects in figure 2.

DETAILED DESCRIPTION OF THE INVENTION

This document describes methods for supporting emergency calls in circuit switched mode. A call in circuit switching mode is a call in which the allocated resources (for example, traffic radio channels) are allocated for the call. A circuit switched call is also referred to as a circuit switched call and is different from a packet switched call in which data is sent in packets using shared resources. An emergency call in channel switching mode is a call in emergency mode channel switching mode. An emergency call in channel switching mode can be identified as such and can be distinguished from a normal call in channel switching mode in several ways, as described below. An emergency call in channel switching mode can be associated with various characteristics that differ from a normal call in channel switching mode, such as, for example, obtaining an appropriate estimate of a user's location, routing an emergency call in channel switching mode to an appropriate PSAP, user support even without subscribing to services, etc. As used herein, the term “location” typically refers to a process for obtaining and providing the geographical location of a target UE. The term "positioning" typically means a process for measuring / calculating an estimate of the geographical position (position) of a target UE. Positioning may or may not entail positioning, depending on whether an appropriate position estimate is already available. Position estimation is also referred to as position estimation, position fixing, etc.

1 illustrates a deployment 100 that supports circuit-switched emergency calls. A subscriber unit (UE) 110 communicates with a radio access network (RAN) 120 in order to receive communication services. UE 110 may be fixed or mobile, and may also be called a mobile station (MS), terminal, subscriber unit, station, or some other terminology. The UE 110 may be a cell phone, a personal digital device (PDA), a wireless device, a travel computer, a telemetry device, a tracking device, and the like. UE 110 can exchange data from one or more base stations in RAN 120. UE 110 can also receive signals from one or more satellites 190, which can be part of the US global positioning system (GPS), European Galileo system, Russian GLONASS system or some or another satellite positioning system (SPS). UE 110 may measure signals from base stations in RAN 120 and / or signals from satellites 190. UE 110 may receive pseudorange measurements for satellites and / or synchronization measurements for base stations. Pseudorange and / or time synchronization measurements can be used to derive the location estimate of the UE 110 using one or more positioning methods, for example using GPS (A-GPS), stand-alone GPS, advanced forward link trilateration (A-FLT ), Advanced Tracked Time Difference (E-OTD), Tracked Time Difference in Arrival (OTDOA), Advanced Cell Identifier, and the like.

RAN 120 provides radio communications to UEs located in the RAN coverage area. RAN 120 is associated with the guest network 130, which is the network currently serving the UE 110. The guest network may also be referred to as the Public Guest Terrestrial Mobile Network (V-PLMN). Home network 150, which may also be called PLMN (H-PLMN), is a network for which UE 110 is subscribed. The guest network 130 and the home network 150 may be the same or different networks, and, if they are different networks, may or may not have a roaming agreement.

Network 160 may include a Public Switched Telephone Network (PSTN) and / or other voice and data networks. PSTN supports communications for traditional plain old telephone services (POTS). PSAP 180 is the facility responsible for responding to emergency calls (such as the police, fire and medical services), and it may also be referred to as an emergency call center (EC). An emergency call can be initiated when the user dials a fixed, well-known number, such as 911 in North America or 112 in Europe. PSAP 180 is typically managed and owned by a government agency, such as a county or city. The PSAP 180 communicates with the PSTN 160.

The techniques described herein can be used for emergency circuit-switched calls of various wireless networks, such as CDMA, TDMA, FDMA and OFDMA networks, wireless local area networks (WLANs) and / or other networks. A CDMA network may implement one or more radio technologies, for example, Broadband CDMA (W-CDMA), cdma2000, etc. Cdma2000 covers IS-2000, IS-856, and IS-95 standards. A TDMA network may implement one or more radio technologies, for example, Global System for Mobile Communications (GSM), Digital Advanced Mobile Phone System (D-AMPS), and the like. D-AMPS covers IS-248 and IS-54. W-CDMA and GSM are described in documents from an organization called the Third Generation Partnership Project (3GPP). Cdma2000 is described in documents from an organization called the Third Generation Partnership Project 2 (3GPP2). 3GPP and 3GPP2 documents are publicly available. These various radio technologies and standards are known in the art. The 3GPP Shared Access Network (GAN) can use WLAN to provide circuit switched access, as described in 3GPP TS 43.318.

2 illustrates the architecture of 3GPP and 3GPP2 networks. UE 110 may receive radio access via 3GPP RAN 120a, which may be a GSM EDGE radio access network (GERAN), a universal terrestrial radio access network (UTRAN), a developed UTRAN (E-UTRAN), WLAN, or some other access network. 3GPP RAN 120a includes base stations 220a, radio network controllers / base station controllers (RNC / BSC) 222a, and other entities not shown in FIG. A base station may also be referred to as Node B, Enhanced Node B (e-Node B), Base Transceiver Station (BTS), Access Point (AP), or some other terminology.

3GPP V-PLMN 130a is one embodiment of the guest network 130 of FIG. 1, and it may include a Mobile Switching Center (MSC) 230a, a Gateway Mobile Location Center (GMLC) 232a, an emergency location platform SUPL Services (E-SLP) 234a and Guest SLP (V-SLP) 236a. GMLC 232a, E-SLP 234a and V-SLP 236a provide location services for UEs communicating with V-PLMN 130a. GMLC 232a supports some functions of the traditional GMLC (for example, defined in 3GPP TS 23.271 and J-STD-036) and some functions associated with the use of SUPL for location and routing of emergency calls. E-SLP 234a and V-SLP 236a support SUPL from the Open Mobile Alliance (OMA). E-SLP 234a replaces home SLP (H-SLP) in case of emergency call location and can be combined with GMLC 232a. V-SLP 236a may be within or outside of V-PLMN 130a and may be geographically closer to UE 110.

UE 110 may also receive radio access via 3GPP2 RAN 120b, which may be a CDMA2000 1X network or some other access network. 3GPP2 RAN 120b includes base stations 220b, BSC 222b, and other entities not shown in FIG. 2.

3GPP2 V-PLMN 130b is another embodiment of the guest network 130 of FIG. 1, and it may include an MSC 230b, a mobile positioning center (MPC) 232b, an E-SLP 234b, and a V-SLP 236b. MPC 232b, E-SLP 234b and V-SLP 236b provide location services for UEs communicating with V-PLMN 130b. MPC 232b supports some functions of the traditional MPC (for example, defined in 3GPP2 X.S0002, TIA-881 and J-STD-036) and some functions associated with the use of SUPL for location and routing of emergency calls. E-SLP 234b and V-SLP 236b support OMA SUPL. E-SLP 234b can be combined with MPC 232b. Alternatively or in addition, the V-PLMN 130b may include an emergency positioning server (E-PS) 238 and a guest PS (V-PS) 240. The E-PS 238 and V-PS 240 are location servers that support location X.S0024 for cdma2000 networks and are similar to E-SLP 234b and V-SLP 236b for SUPL. V-SLP 236b and V-PS 240 may be located within or outside of V-PLMN 130b and may be geographically closer to UE 110. V-PLMN 130b may also include a positioning object (PDE) and / or other objects.

The 3GPP H-PLMN 150a is one embodiment of the home network 150 of FIG. 1, and it may include H-SLP 252a and / or other network entities. 3GPP2 H-PLMN 150b is another embodiment of the home network 150 of FIG. 1, and it may include H-SLP 252b and H-PS 254 and / or other network entities. Objects in SUPL are described in OMA-AD-SUPL-V2_0-20060823-D, entitled "Secure User Plane Location Architecture", draft version 2.0, August 23, 2006, and in OMA-TS-ULP-V2_0-20060907-D, entitled "User Plane Location Protocol", draft version 22.0, September 7, 2006. The objects in the X.S0024 location are described in 3GPP2 X.S0024, entitled "IP-Based Location Services", version 1.0, October 2005. These documents are publicly available.

For simplicity, FIG. 2 shows only some of the entities in 3GPP and 3GPP2, which are mentioned in the description below. 3GPP and 3GPP2 networks may include other entities defined by 3GPP and 3GPP2, respectively.

A wireless network may support location services (LCS) using a control plane (CP) solution and / or a user plane (UP) solution. The control plane (also called the signal transmission plane) is a signal transfer mechanism for higher-level applications, and it is typically implemented using network-specific protocols, interfaces, and signaling messages. The user plane is a signal transfer mechanism for higher-level applications, and it uses a unidirectional user plane channel, which is typically implemented using protocols such as the User Datagram Protocol (UDP), Transmission Control Protocol (TCP), and Internet Protocol (IP). Messages that support location and positioning services are carried as part of the signals in the architecture of the control plane and as part of the data (from the point of view of the network) in the architecture of the user plane. However, the message content may be the same or similar in both architectures. The 3GPP control plane is described in 3GPP TS 23.271, TS 43.059 and TS 25.305. The 3GPP2 control plane is described in IS-881 and 3GPP2 X.S0002. SUPL and pre-SUPL are described in documents from OMA.

Emergency calls in circuit switched mode on a wireless network are typically supported using a control plane solution rather than a user plane solution. This means that the network operator may need to deploy solutions for both the control plane and the user plane in order to support all location-related applications.

The techniques described in this document support emergency calls in circuit-switched mode using a combination of control plane and user plane solutions. This may have the advantage of simplifying the implementation, since objects in order to support parts of the LCS control plane are deployed and supported through a variety of 3GPP and 3GPP2 network operators. However, the techniques contain only a small part of the control plane solution, thereby preventing a significant increase in cost and complexity when updating the user plane solution. In particular, the network operator may be able to support all location-related applications without deploying a complete control plane solution.

The techniques support registered UEs as well as unregistered UEs. A registered UE is a UE that is registered in the home network and can be authenticated through the home network. An unregistered UE is a UE that is not registered on any network and is not authenticated. The 3GPP UE can be equipped with a universal integrated circuit board (UICC) or subscriber identity module (SIM). The 3GPP2 UE may be equipped with a user identification module (UIM). UICC, SM, or UIM are typically specific to one subscriber and may store personal information, subscription information, and / or other information. A UE without a UICC is a UE with no UICC or SIM. A UE without a UIM is a UE with a missing UIM. A UE without UICC / UIM is not registered on any network and has a subscription, home network, and authentication credentials (such as a secret key) to verify the claimed identity, which makes location services more at risk.

3 illustrates an embodiment of a network architecture 300 for an emergency call in a circuit switched SUPL location mode. Network architecture 300 is applicable for 3GPP and 3GPP2 networks. For simplicity, FIG. 3 shows only objects and interfaces that are important in order to support an emergency call in circuit switched mode using SUPL. In general, network architecture 300 may include other entities to support call and / or location in circuit switched mode.

UE 110 is referred to as a SUPL capable terminal (SET) in SUPL. RAN 120 may be a 3GPP RAN 120a, 3GPP2 RAN 120b, or some other access network. E-SLP 234 may include a SUPL location center (E-SLC) 312 that performs various functions for location services, and a SUPL positioning center (E-SPC) 314 that supports positioning for the UE. V-SLP 236 likewise may include V-SLC 322 and V-SPC 324. E-SLP 234 is associated with MPC / GMLC 232 and replaces H-SLP 252 in H-PLMN 150 in case of emergency call location. V-SLP 236 may be closer and / or more able to find UE 110. In most cases, only E-SLP 234 is sufficient, and V-SLP 236 is not required.

SUPL supports two communication modes between SET and SLP for positioning using SPC. In proxy mode, the SPC does not directly communicate with SET, and the SLP acts as a proxy between SET and SPC. In non-proxy mode, SPC has a direct connection with SET.

PSTN 160 may include a selective router (S / R) 260 and / or other tandems used to set up an emergency call in circuit switching mode from the MSC 230 to the PSAP 180. S / R 260 may belong to the PSAP 180 or may be shared and connected to the PSAP kit. UE 110 can communicate with the PSAP 180 through the MSC 230 and S / R 260.

Figure 3 also shows the interfaces between various objects. Call-related interfaces between the UE 110 and the RAN 120 and between the RAN 120 and the MSC 230 are network specific. The call-related interface between the MSC 230, S / R 260 and the PSAP 180 can be a multi-frequency / ISDN subscriber unit / ISDN (MF / ISUP / ISDN).

The location-related interface between the UE 110 and the E-SLP 234 and the V-SLP 236 may be a SUPL User Plane Location Protocol (ULP). The interface between the E-SLP 234 and the V-SLP 236 may be a roaming location protocol (RLP). The interface between the MSC 230 and the GMLC / MPC 232 may be a mobile application node (MAP). The interface between the MPC / GMLC 232 and the E-SLP 234 resembles both the Le / L1 interface between the SUPL agent and the H-SLP and the Lr / LCS-z interface between the SLP pair in SUPL 1.0. Thus, the interface between the MPC / GMLC 232 and the E-SLP 234 can be supported using the Mobile Terminal Location Protocol (MLP), RLP, an enhanced version of MLP or RLP, or some other interface. For RLP, GMLC support has already been defined with respect to initiating RLP transactions. For MLPs, GMLC usually acts as the receiver of the transaction. The interface between the E-SLP 234 and PSAP 180 can be an E2 interface defined in J-STD-036 revision B, MLP, an HTTP interface, or some other interface.

Several exemplary circuit-switched emergency call message flows in 3GPP and 3GPP2 with SUPL location are described below. For simplicity, objects that are less relevant (for example, RAN 120 and S / R 260) are omitted from these message flows, but are included in the descriptions. These message flows assume that the UE 110 has a UICC or UIM and that there is a roaming agreement between the V-PLMN 130 and the H-PLMN 150. The message flows also assume that the UE 110 supports parallel communication and circuit switched mode (for emergency calls ), and in packet switching mode (for example, to determine the location). This feature is currently enabled for registered users through 3GPP in UMTS and GSM / GPRS and through 3GPP2 in cdma2000.

1. Emergency circuit-switched call in 3GPP with SUPL location

FIG. 4 illustrates an embodiment of a message flow 400 for an emergency call in circuit switched mode in 3GPP using SUPL with location initiated prior to call setup. In step 1, the UE 110 sends a call request for emergency services (for example, E911 in North America or E112 in Europe) in the MSC 230a in 3GPP V-PLMN 130a. This request is referred to as Emergency Call Initiation (ESC).

In step 2, the MSC 230a may allow or determine that the UE 110 supports SUPL positioning, for example, based on the subscription information of the UE or the characteristics information of the UE received from the UE, or as a V-PLMN policy 130a. The MSC 230a then sends a MAP Subscriber Location Report (SLR) message to the GMLC 232a, which is in a network that is associatively connected (e.g., contains or connected) with the E-SLP 234a. The MAP SLR is used to create an emergency call record in GMLC 232a (and associative communication with MSC 230a), as well as to receive PSAP routing information from GMLC. The MAP SLR may comprise UE identity, serving cell identity (ED), and / or other information. The identity of the UE may be an international mobile subscriber identifier (IMSI), an ISDN mobile subscriber number (MSISDN), an international mobile device identifier (IMEI), and / or any other identification data. Other information may include measurements from a UE or network that can be used to calculate a location estimate for the UE. For calls in North America, the MSC 230a can assign an Emergency Routing Key (ESRK) or Emergency Routing Code (ESRD) and should then include it in the MAP SLR. ESRD is a non-dialing number that identifies the PSAP. ESRK is a non-dialing subscriber number that can be used to route to the PSAP. Each PSAP can be associated with one ESRD and a pool of several ESRKs. For an emergency call by the UE to this PSAP, one ESRK from the pool can be assigned to the UE for the time of the emergency call and can be used to identify the PSAP, GMLC and / or MSC and UE.

In step 3, the GMLC 232a creates an entry for the call. GMLC 232a may determine an estimate of the intermediate position of UE 110 based on the location information received in step 2. The location information may include a cell identifier, measurements, position estimate, etc. Evaluating an intermediate position typically means the approximate position used to route the call. GMLC 232a may also initiate steps 8-13 in advance to obtain an estimate of the intermediate position for UE 110. GMLC 232a may select a PSAP based on the estimate of the intermediate position (if received) or the serving cell ID received in step 2. This ensures that the selected The PSAP covers emergency calls from the geographic area where the UE 110 is located. For calls in North America, the GMLC 232a may assign an ESRD or ESRK to indicate the selected PSAP. In the following description, PSAP 180 is the selected PSAP. GMLC 232a can also initiate steps 8-13 in advance to obtain an accurate estimate of the starting position, which can then be used to request location from the PSAP. The assessment of the initial position in a typical embodiment refers to the first accurate assessment of the position. In step 4, the GMLC 232a returns an acknowledgment of the MAP SLR to the MSC 230a. For calls in North America, this acknowledgment may include any ESRD or ESRK assigned by GMLC 232a in step 3.

In step 5, the MSC 230a sends an emergency circuit-switched call to the PSAP 180. For calls in North America, if the ESRK or ESRD is returned in step 4, then the PSAP 180 is selected by GMLC 232a in step 3. Otherwise, the MSC 230a may determine the PSAP for example, based on the current or initial serving cell for UE 110. For calls in North America, a call setup message or indication sent by the MSC 230a to the PSAP 180 includes any of the ESRD or ESRK returned by the GMLC 232a in step 4 or assigned by MSC 230a in step 2 or 5. C The call establishment message may include a callback number for UE 110 (e.g., MSISDN).

In step 6, a call is established between the UE 110 and the PSAP 180 through the MSC 230a. In step 7, the PSAP 180 sends a position request from emergency services to the GMLC 232a to request an accurate estimate of the starting position of the UE 110. For calls in North America, the PSAP 180 can identify the GMLC 232a using the ESRK or ESRD received in step 5. In this case, the request emergency service positions includes ESRK and / or ESRD and callback number. PSAP 180 does not need to be aware that SUPL is used for positioning.

In step 8, GMLC 232a identifies the call record created in step 3 using (a) the ESRK or callback number received in step 7 for calls in North America, or (b) other caller information (e.g., MSISDN or IMSI ) for calls in other regions. If GMLC 232a received an accurate position estimate in step 3 (for example, by performing steps 8-13 in advance), then GMLC 232a can return this position estimate immediately to PSAP 180 in step 14 and skip steps 8-13. Otherwise, GMLC 232a sends an emergency position request to the E-SLP 234a, which may contain UE credentials (e.g. MSISDN and / or IMSI), cell identifier (if known), required positioning quality (QoP) and / or other information. QoP transfers the requirements for evaluating a position, for example, the accuracy and term of an evaluation of a position. QoP is also referred to as QoS.

In step 9, the E-SLP 234a determines whether positioning should be supported by a V-SLP closer and / or better able to support the positioning of the UE 110, for example, based on the cell identifier (if any) adopted in step 8. If so, then the E-SLP 234a exchanges signals with the V-SLP (not shown in FIG. 4). Otherwise, the E-SLP 234a prompts the network-initiated SUPL location procedure, with the E-SLP replacing the H-SLP. E-SLP 234a first sends the SUPL INIT to UE 110 to begin the SUPL location procedure. SUPL INIT can be sent, for example, by pushing the Wireless Application Protocol (WAP), a short message service (SMS) trigger, or UDP / IP, if the E-SLP 234a knows or can obtain the IP address of the UE 110. SUPL INIT can include the IP address of the E-SLP 234a, for example, if the UE 110 is not in the home network, if the E-SLP 234a is not an H-SLP for the UE, or if the E-SLP 234a chooses not to work in the H-SLP mode (to for example, in order to simplify the implementation). SUPL INIT can also include an emergency call indicator, for example, in the SUPL INIT alert parameter. If non-proxy mode is used, then SUPL INIT may also contain the IP address of the SPC, which is associated with the E-SLP 234a or with a separate V-SLP. UE 110 in this case must interact with the SPC in order to perform positioning.

In step 10, the UE 110 establishes a reliable (secure) IP connection with its H-SLP if the E-SLP 234a is an H-SLP (and selects H-SLP operation) for the UE. However, if E-SLP 234a is not an H-SLP for UE 110 and / or if E-SLP 234a includes its IP address in SUPL INIT in step 9, then UE 110 establishes an IP connection or a secure IP connection with E-SLP 234a instead of H-SLP. For proxy-free mode, authentication-related SUPL messages can then be transmitted between UE 110 and E-SLP 234a and between E-SLP 234a and any V-SLP selected in step 9 (not shown in FIG. 4), and UE 110 further establishes an IP connection or a secure IP connection with the SPC indicated by SUPL INIT in step 9. For proxy mode, the UE 110 returns SUPL POS INIT to E-SLP 234a. For proxy-free mode, the UE 110 sends a SUPL POS INIT to the SPC (not shown in FIG. 4). SUPL POS INIT may include positioning methods and positioning protocols supported by the UE 110, a serving cell identifier, network measurements to aid in location calculations, a request for ancillary data (e.g., for A-GPS), if ancillary UE 110 is required data, position evaluation, if UE 110 already has it, and / or other information. If the E-SLP 234a or SPC can obtain a position estimate with the required accuracy from the information received in SUPL POS INIT, then the E-SLP or SPC can go directly to step 12.

At step 11, the UE 110 continues the SUPL location procedure with the E-SLP 234a for proxy mode or with SPC for non-proxy mode. UE 110 may exchange one or more SUPL POS messages with E-SLP 234a (for proxy mode) or SPC (for non-proxy mode). Each SUPL POS message may comprise a positioning message according to the 3GPP Radio Resource Protocol (RRLP), 3GPP Radio Resource Control (RRC), or some other positioning protocol. The E-SLP 234a or SPC may provide ancillary data to UE 110 in these messages, and UE 110 may subsequently return location-related measurements or position estimates.

At step 12, the E-SLP 234a or the SPC obtains a position estimate either by calculating it from the measurements received from the UE 110 in step 11, or by checking the position estimate received from the UE in step 11. The E-SLP 234a or SPC then sends the SUPL END at UE 110 to complete the SUPL location procedure. At step 13, the E-SLP 234a returns a position estimate (which may have been redirected from the selected V-SLP, not shown in FIG. 4) to the GMLC 232a in the emergency response position. At step 14, the GMLC 232a returns a position estimate in the PSAP 180 in response to a position request from emergency services.

In step 15, after some time, the PSAP 180 may send another position request from the emergency services to the GMLC 232a to obtain an updated position estimate for the UE 110. In this case, the GMLC 232a may repeat steps 8-13 in order to obtain a new position estimate with using SUPL and returning it to PSAP 180 in response to a position request from emergency services. When requesting a position estimate from E-SLP 234a in a repeat of step 8, GMLC 232a may transmit the last position estimate received to E-SLP 234a to help it determine the V-SLP, if this option is supported.

At step 16, after some time, the call between the UE 110 and the PSAP 180 ends. In step 17, the MSC 230a sends to the GMLC 232a a MAP subscriber location report identifying the UE 110 (e.g., via MSI or MSISDN) and indicating that the call has ended. In step 18, the GMLC 232a may delete the call record created in step 3 and return an acknowledgment of the MAP subscriber location report to the MSC 230a.

FIG. 5 illustrates an embodiment of a message flow 500 for an emergency call in circuit switched mode in 3GPP using SUPL with location initiated after call setup. In step 1, the UE 110 sends an emergency call request to the MSC 230a. In step 2, the emergency call procedure is applied. MSC 230a determines the appropriate PSAP (or emergency call client) based on the identifier of the serving cell. In the following description, PSAP 180 is the selected PSAP. MSC 230a, RAN 120a, and UE 110 continue the normal emergency call initiation procedure to PSAP 180. Call setup information sent to PSAP 180 (eg, via PSTN 160) may include determining the location of the UE (if already received), information, which will enable the emergency service provider to request the location of the UE later (for example, an ISUP / BICC IAM message with the location number parameter specified by the MSC number and the calling party parameter equal to the MSISDN in Europe) and / or other information.

In step 3, the MSC 230a may allow or determine that the UE 110 supports SUPL location determination. The MSC 230a then sends the MAP SLR to the GMLC 232a, which is associated with the E-SLP 234a and the PSAP 180, to which the emergency call was or will be sent in step 3. The MAP SLR may contain the identity of the UE, the identifier of the serving cell, the identifier of the service area ( SAI) UE and / or other information. In the case of an emergency call without a SIM or an emergency call with an unregistered (U) SIM, IMEI can always be sent, and the MSISDN can be filled in without a dialing number. In Europe, the MSC 230a may provide the identity of the PSAP 180 to which the emergency call is connected.

In step 4, the GMLC 232a creates an entry for the call. In step 5, the GMLC 232a returns an acknowledgment of the MAP SLR to the MSC 230a. In step 6, the GMLC 232a sends to the E-SLP 234a a position request from the emergency services, which may contain UE credentials (for example, MSISDN and / or IMSI), cell identifier or SAI (if known), required QoP and / or other information .

In steps 7-10, the E-SLPs 234a and UE 110 are included in the SUPL positioning procedure, as described above for steps 9-12 in FIG. 4. The need for the V-SLP can be determined from the cell identifier or SAI (if any) adopted in step 6. In step 10, the E-SLP 234a (for proxy mode) or the SPC associated with the E-SLP 234a or the selected V- SLP (for non-proxy mode) obtains the position estimate of UE 110. The E-SLP 234a or SPC then sends the SUPL END to UE 110 to complete the SUPL location discovery procedure. At step 11, the E-SLP 234a returns a position estimate (which may have been redirected from the selected V-SLP, not shown in FIG. 5) to the GMLC 232a. At step 12, the GMLC 232a can redirect the location information received at step 11, information about the positioning method used and / or other information to the PSAP 180. Otherwise, the PSAP 180 is expected to receive location information by requesting it from the GMLC 232a.

At step 13, after some time, the call between the UE 110 and the PSAP 180 ends. At step 14, the MSC 230a sends to the GMLC 232a a MAP subscriber location report identifying the UE 110 and indicating that the call is completed. In step 15, the GMLC 232a may delete the call record created in step 4 and return an acknowledgment of the MAP subscriber location report to the MSC 230a.

2. Emergency call in circuit switching mode in 3GPP2 with SUPL location

6 illustrates an embodiment of a network architecture 600 for emergency circuit-switched call in 3GPP2 using SUPL. In step 1, the UE 110 sends an emergency call request to the MSC 230b in the 3GPP2 PLMN 130b. In step 2, the MSC 230b may allow or determine that the UE 110 supports SUPL positioning, for example, based on the subscription information of the UE or the characteristics information of the UE received from the UE or the PLMN policy 130b. MSC 230b then sends an ANSI-41 MAP initiation request to MPC 232b, which is located on a network that is associatively connected (for example, contains or is connected) with E-SLP 234b. The initiation request may comprise UE identity (e.g., IMSI and / or MIN), a serving cell identifier, and / or other information (e.g., measurements from a UE or network that can be used to determine a position estimate).

In step 3, the MPC 232b creates an entry for the call. MPC 232b may determine an estimate of the intermediate position of UE 110 based on the cell identifier and all measurements taken in step 2. MPC 232b may also initiate steps 8-13 in advance to obtain an estimate of the intermediate position for UE 110. MPC 232b may select a PSAP based on the estimate an intermediate position (if received) or a serving cell identifier adopted in step 2. If so, the MPC 232b may designate an ESRD or ESRK to indicate the selected PSAP. In the following description, PSAP 180 is the selected PSAP. In step 4, the MPC 232b returns to the MSC 230b an acknowledgment of receipt of an ANSI-41 MAP initiation request containing any ESRD or ESRK assigned in step 3.

In step 5, the MSC 230b sends an emergency call to the PSAP 180. If the ESRK or ESRD is returned in step 4, then the PSAP 180 is selected by the MPC 232b in step 3. Otherwise, the MSC 230b may determine the PSAP (for example, based on the current or initial serving cell UE 110) and may assign ESRD and / or ESRK. The call setup message sent by the MSC 230b to the PSAP 180 may include any ESRD or ESRK returned in step 4 or assigned in step 5, and a callback number for UE 110 (e.g., MSISDN).

In step 6, a call is established between the UE 110 and the PSAP 180 via the MSC 230b. In step 7, the PSAP 180 sends a position request from the emergency services to the MPC 232b to request an accurate estimate of the starting position of the UE 110. The PSAP 180 can identify the MPC 232b using the ESRK or ESRD received in step 5. In this case, the request for the position from the emergency services includes ESRK and / or ESRD and callback number. In step 8, the MPC 232b identifies the call record created in step 3 using the ESRK or callback number received in step 7. If the MPC 232b received an accurate position estimate in step 3 (for example, by performing steps 8-13 in advance), then MPC 232b may return it directly to PSAP 180 in step 14 and skip steps 8-13. Otherwise, the MPC 232b sends to the E-SLP 234b a position request from the emergency services, which may contain the identification data of the UE (for example, MIN and / or IMSI), the cell identifier (if known), the required QoP and / or other information.

In steps 9-12, the E-SLPs 234b and UE 110 are included in the SUPL positioning procedure as described above for steps 9-12 in FIG. 4. If the E-SLP 234b (for proxy mode) or SPC (for non-proxy mode) can obtain a position estimate with the required accuracy from the information received in SUPL POS INIT in step 10, then the E-SLP or SPC can go directly to step 12 Otherwise, the UE 110 may exchange one or more SUPL POS messages with E-SLP 234b (for proxy mode) or SPC (for non-proxy mode) in step 11. Each SUPL POS message may contain a positioning message according to 3GPP2 C.S0022 , TIA-801, 3GPP RRLP, RRC, or some other positioning protocol. The E-SLP 234b or SPC may provide ancillary data to the UE in these messages, and the UE may subsequently return location-related measurements or position estimates. At step 12, the E-SLP 234b or SPC obtains a position estimate and sends the SUPL END to UE 110 to complete the SUPL location procedure.

At step 13, the E-SLP 234b returns the position estimate (which may be redirected from the selected V-SLP, not shown in FIG. 6) to the MPG 232b. At step 14, the MPC 232b returns the position estimate in the PSAP 180 in the response message to the position request from the emergency services. At step 15, after some time, the PSAP 180 may send another position request from emergency services to MPC 232b to obtain an updated position estimate for UE 110. In this case, MPC 232b may repeat steps 8-13 in order to obtain a new position estimate from using SUPL and returning it to PSAP 180 in response to a position request from emergency services. When requesting a position estimate from the E-SLP 234b in a repeat of step 8, the MPC 232b may transmit the last position estimate received to the E-SLP 234b to help it determine the V-SLP, if this option is supported.

At step 16, after some time, the call between the UE 110 and the PSAP 180 ends. At step 17, the MSC 230b sends to the MPC 232b a call completion report message ANSI-41 MAP identifying the UE 110 (for example, via IMSI or MSISDN) and indicating that the call is completed. In step 18, the MPC 232b may delete the call record created in step 3 and return an ANSI-41 MAP call completion report acknowledgment to the MSC 230b.

3. Emergency call in circuit switching mode in 3GPP2 with X.S0024 location

FIG. 7 illustrates an embodiment of a network architecture 700 for emergency circuit-switched channel calling X.S0024. For 3GPP2, the user plane positioning solution defined in 3GPP2 X.S0024 can be used in place of SUPL. The network architecture 700 is thus applicable to 3GPP2 networks. RAN 120 may be 3GPP2 RAN 120b or some other access network. V-PLMN 130b may include MSC 230b, MPC 232b, E-PS 238 and V-PS 240. MPC 232b may activate E-PS 238 and use X.S0024 to locate the emergency call UE.

The location-related interfaces between UE 110, E-PS 238, and V-PS 240 may be LCS-x, LCS-y, and LCS-z, as shown in FIG. 7, which are described in 3GPP2 X.S0024. The interface between the MSC 230b and the MPC 232b may be an ANSI-41 MAP. The interface between the MPC 232b and the E-PS 238 may be MLP, RLP, or some other interface.

FIG. 8 illustrates an embodiment of a network architecture 800 for circuit switched emergency call in 3GPP2 using X.S0024. In step 1, the UE 110 sends an emergency call request to the MSC 230b in the 3GPP2 PLMN 130b. In step 2, the MSC 230b may allow or determine that the UE 110 supports X.S0024 positioning, for example, based on the subscription information of the UE or the characteristics information of the UE received from the UE or PLMN policy 130b. MSC 230b then sends an ANSI-41 MAP Initiation Request message to MPC 232b. The initiation request may comprise UE identity (e.g., IMSI and / or MIN), a serving cell identifier, and / or other information (e.g., measurements from a UE or network that can be used to determine a position estimate).

In step 3, the MPC 232b creates an entry for the call. MPC 232b may determine an intermediate position estimate of UE 110 based on the cell identifier and all measurements taken in step 2. MPC 232b may also initiate steps 8-15 in advance and obtain an intermediate position estimate for UE 110. MPC 232b may select a PSAP based on the intermediate estimate the position (if received) or the serving cell identifier adopted in step 2. If so, the MPC 232b may designate an ESRD or ESRK to indicate the selected PSAP. In the following description, PSAP 180 is the selected PSAP. In step 4, the MPC 232b returns to the MSC 230b an acknowledgment of receipt of the ANSL41 MAP initiation request containing any ESRD or ESRK assigned in step 3. In step 5, the MSC 230b sends an emergency call to PSAP 180. If the ESRK or ESRD is returned in step 4, then The PSAP 180 is selected by the MPC 232b in step 3. Otherwise, the MSC 230b may determine the PSAP (for example, based on the current or initial serving cell of the UE 110) and may allocate ESRD and / or ESRK. The call setup message sent by the MSC 230b to the PSAP 180 may include any ESRD or ESRK returned in step 4 or assigned in step 5, and a callback number for the UE 110 (e.g., mobile subscriber number, MDN). The MSC 230b may send a call to the PSAP 180 prior to step 2 to prevent a call delay. In step 6, a call is established between the UE 110 and the PSAP 180 through the MSC 230b. In step 7, the PSAP 180 sends a position request from the emergency services to the MPC 232b to request an accurate estimate of the starting position of the UE 110. The PSAP 180 can identify the MPC 232b using the ESRK or ESRD received in step 5. In this case, the request for the position from the emergency services includes ESRK and / or ESRD and callback number. In step 8, the MPC 232b identifies the call record created in step 3 using the ESRK or callback number received in step 7. If the MPC 232b obtained an accurate position estimate in step 3, then the MPC 232b can return it immediately to PSAP 180 in step 16 and skip steps 8-15. Otherwise, the MPC 232b sends to the E-PS 238 a position request from the emergency services, which may contain the identification data of the UE (for example, MIN and / or IMSI), the cell identifier (if known), the required QoP and / or other information.

In step 9, the E-PS 238 prompts the X.S0024 location procedure and sends the X.S0024 SUPL_INIT to the UE 110 via SMS, WAP Push, or UDP / IP if the E-PS 238 knows or can obtain the IP address of the UE 110. SUPL_INIT may include the required QoP, supported positioning methods, the IP address of the E-PS 238, for example, if the UE 110 is not in its home network, if the E-PS 238 is not an H-PS for the UE, or if the E-PS 238 chooses not to work in H-PS mode. SUPL_INIT may also include an emergency call indicator, for example, in the SUPL_INIT alert parameter. The position request from the emergency services in step 8 can be sent immediately after step 4 without waiting for the position request from the emergency services from the PSAP 180 in step 7. In this case, steps 8-15 can be performed before the MPG 232b receives the position request from the emergency services from the PSAP 180 in step 7, and the MPG 232b can go directly from step 7 to step 16.

In step 10, the UE 110 establishes a secure IP connection with the E-PS 238 if it is an H-PS for the UE. However, if the E-PS 238 is not an H-PS for UE 110 and / or if the E-PS 238 includes its IP address in SUPL_INIT in step 9, then UE 110 establishes an IP connection or a secure IP connection with E -PS 238 instead of H-PS. UE 110 then sends to E-PS 238 SUPL_START, which may include the positioning methods and characteristics supported by UE 110, a serving cell identifier, measurements, position estimation, ancillary data request and / or other information.

At step 11, the E-PS 238 may expand the positioning procedure to the selected PDE, which may be a PDE associated with the E-PS 238 or V-PS. The selected PDE in this case should control the positioning procedure and help in calculating the position. The extension may use either (a) a proxy mode in which the UE 110 communicates with the selected PDE via the E-PS 238 (as shown in FIG. 8), or (b) a non-proxy mode in which the UE 110 communicates directly with selected PDE (not shown in FIG. 8).

At step 12, the E-PS 238 sends SUPL_RESPONSE to the UE 110. For proxy mode at step 13, the UE 110 sends to the E-PS 238 SUPL_POS, which can carry information from the serving cell, an integrated positioning message (for example, using 3GPP2 C.S0022 or TIA-801 protocol) and / or other information. The E-PS 238 then redirects SUPL_POS to the selected PDE (not shown in FIG. 8). For non-proxy mode, SUPL_RESPONSE transfers the address of the selected PDE in step 12, and the UE 110 establishes a secure IP connection with the selected PDE and sends SUPL_POS directly to this PDE in step 13.

At step 14, the UE 110 may exchange additional SUPL_POS messages with the E-PS 238 (for proxy mode) or PDE (for non-proxy mode). The E-PS 238 or PDE may provide ancillary data to the UE 110 in these messages, and the UE may provide measurements for determining the location (eg, A-GPS and / or A-FLT measurements) or position estimation in the E-PS or PDE. In step 15, the selected PDE obtains a position estimate either by calculating it from the measurements received from UE 110 in steps 13 and 14, or by checking the position estimate received from the UE. The PDE further returns a position estimate in the E-PS 238, either directly if the PDE is associated with the E-PS 238, or indirectly (not shown in FIG. 8) if the PDE is associated with the V-PS. Next, the E-PS 238 redirects the position estimate to the MPC 232b in the emergency position response. In step 16, the MPC 232b returns the position estimate in the PSAP 180 in a response message to the position request from the emergency services.

At step 17, after a while, the PSAP 180 may send another position request from emergency services to MPC 232b to obtain an updated position estimate for UE 110. In this case, MPC 232b may repeat steps 8-15 in order to obtain a new position estimate from using X.S0024 and return it to PSAP 180 in response to a position request from emergency services. At step 18, after some time, the call between the UE 110 and the PSAP 180 ends. At step 19, the MSC 230b sends to the MPC 232b a call completion report message ANSI-41 MAP identifying the UE 110 (for example, via IMSI or MIN) and indicating that the call is completed. In step 20, the MPC 232b may delete the call record created in step 3 and return an ANSI-41 MAP call completion report confirmation to the MSC 230b.

4. Using SUPL 1.0 or X.S0024 version 1.0

V-PLMN 130 may or may not use E-SLP or E-PS at all in order to support SUPL or X.S0024 positioning on behalf of emergency calls in circuit switched mode. Instead, the V-PLMN 130 can use the previous version of OMA SUPL (for example, SUPL 1.0) or the previous version of X.S0024, both of which do not have special location support for emergency calls. This may be advantageous for a network operator who has not yet deployed a version of SUPL or X.S0024, containing special location support for emergency calls, which provides the use of E-SLP or E-PS, as described above. It may also be advantageous if the network operator wants to support emergency circuit-switched calls for UEs that support only the previous version of SUPL or X.S0024 (for example, even if the network operator can support the latest version of SUPL or X.S0024).

In an embodiment, V-PLMN 130 may use a requesting SLP (R-SLP) instead of an E-SLP that is associated or combined with GMLC 232a or MPC 232b. In this case, support for emergency calls in the circuit switching mode can still be carried out as described above in FIGS. 4, 5 and 6, but with the following differences. First, the R-SLP should replace the E-SLP 234a or E-SLP 234b in each drawing. Secondly, the R-SLP should receive position requests from GMLC 232a or MPC 232b in step 8 of FIGS. 4 and 6 and in step 6 of FIG. 5. The R-SLP should then return the received UE position to the GMLC 232a or MPC 232b in step 13 of FIGS. 4 and 6 and in step 11 of FIG. 5. Thirdly, the SUPL location procedure described for steps 9-12 in FIGS. 4 and 6 and for steps 7-10 in FIG. 5 should be replaced by an alternative SUPL location procedure in which the R-SLP first requests a determination locations from the H-SLP to the UE 110. The H-SLP must then interact with the UE 110 using the SUPL to obtain the location of the UE, and should return the location of the UE to the R-SLP. This alternative SUPL location procedure is defined in OMA-AD-SUPL-V1_0-20060906-C, entitled "Secure User Plane Location Architecture Candidate Version 1.0," September 6, 2006, which is publicly available.

If V-PLMN 130 is an H-PLMN 150 for UE 110, then the R-SLP may be H-SLP for UE 110, and the modified procedure described above can be used without any location request and response between R-SLP and H-SLP, because they are now the same object.

In the case of X.S0024, this embodiment can be used in a similar manner, but with a requesting PS (R-PS) replacing the E-PS 238 associated or combined with MPC 232b in V-PLMN 130b. In this case, the location procedure described in steps 9-14 of FIG. 8 should be replaced by a procedure in which the R-PS requests the location of the UE 110 from the H-PS for the UE 110, and the H-PS then interacts with the UE 110 in order to obtain a location determination (and return it to R-PS) as described in X.S0024, “IP Based Location Services”, version 1.0, revision 0, October 2005. As with SUPL, if UE 110 is not in its H-PLMN, then R-PS may be H-PS.

5. Support unregistered UE, UE without UICC, SIM and UIM

To initiate the SUPL location determination (for example, in step 9 of FIGS. 4 and 6 and step 7 of FIG. 5), the E-SLP sends the SUPL INIT to the UE using WAP Push, SMS, UDP / IP or some other means. To initiate the X.S0024 location determination (for example, in step 9 of FIG. 8), the E-PS sends SUPL_INIT to the UE using WAP Push, SMS, UDP / IP, or some other means. Sending SUPL INIT in some cases (for example, using WAP Push or SMS) can be difficult and time-consuming if the UE moves from its H-PLMN, and can also be unreliable due to interworking with the H-PLMN. In an embodiment, the E-SLP or E-PS sends an SMS message directly to the serving MSC and emulates an MSC SMS gateway in 3GPP or an SMS message center in 3GPP2.

In another embodiment, the E-SLP or E-PS sends an SMS message via GMLC or MPC to the serving MSC to reduce the impact on the E-SLP or E-PS. These embodiments can also be used for unregistered UE, UE without UICC in 3GPP, UE without SIM in GSM, and UE without UIM in 3GPP2. In this case, the MSC may provide a GMLC or MPC with a temporary UE identifier to replace the usual IMSI, MSISDN or MIN. The temporary UE identifier may be included in the MAP subscriber location report sent in step 2 of FIG. 4 and step 3 of FIG. 5 for 3GPP, and the ANSI-41 initiation request sent in step 2 of FIG. 6 and 8 for 3GPP2. After the UE receives the SUPL INIT, it can establish an IP connection or a secure IP connection with the E-SLP or E-PS. An unregistered UE, a UE without a UICC, a UE without a SIM, or a UE without a UIM can establish restricted IP connections for emergency calls, which should provide an IP connection to an E-SLP or E-PS on the same network. IP connections can be established, for example, using the procedures described for “VoIP Emergency Call Support” in 3GPP SA2 article S2-051950, which is publicly available. In this case, a separate V-SLP may not be used.

Most of the above description assumes that the UE supports simultaneous call in circuit switched mode (for voice) and data transmission in packet switched mode (for location). If the UE or the network does not support simultaneous communication in the channel switching mode and the packet switching mode, then the signal exchange between the UE and the E-SLP or E-PS can be supported in other ways.

9 illustrates several embodiments of communication between various entities. In an embodiment, SMSs are used for all SUPL communications. Using SMS, service signals and location information (for example, SUPL messages) are sent as part of SMS messages sent between MPC / GMLC and MSC and between MSC and UE using existing point-to-point SMS transport protocols ( for example, SMS MAP messages) in 3GPP and 3GPP2. Signaling via SMS can be sent directly between the MSC and the GMLC or MPC. Between E-SLP and GMLC or MPG, SUPL messages can be transmitted using TCP / IP, for example, on the same TCP / IP connection that is used to exchange request and response by position from emergency services, or by another connection.

In the embodiment that is indicated by (a) in FIG. 9, SUPL ULP (but not TCP or IP) is used in end-to-end mode between the UE and the E-SLP or E-PS. In another embodiment, which is indicated by (b) in FIG. 9, the SUPL ULP is transmitted using an end-to-end TCP connection. In yet another embodiment, which is indicated by (c) in FIG. 9, SUPL ULP is transmitted using end-to-end TCP / IP with some protocol duplication on the route. This feature can be supported through special SMS processing in the MSC for SMS messages sent from the UE. For example, the MSC may assume that any SMS message sent by the UE during an emergency call using SUPL is for the SUPL, and then must send the SMS message to the GMLC or MPC.

6. Security

For SUPL, security procedures can be established to support E-SLP in a guest network replacing H-SLP, to locate scenarios with and without roaming roaming, as well as for proxy mode or mode without proxy. Existing SUPL security procedures are generally based on shared keys in the UE and H-SLP and / or based on other information prepared by the UE regarding the H-SLP (for example, FQDN, root public key certificate X. 509 etc.). This information may not be available to the E-SLP until the UE is in the home network. For E-SLP, authentication in proxy and non-proxy modes can be supported as described below.

For X.S0024, security procedures can also be established in order to support an E-PS replacing the H-PS for positioning. Existing X.S0024 security procedures are described in 3GPP2 X.S0024-0 and 3GPP2 S.P0110-0. These procedures use a common root key provided in both the user's H-PS and user UIM. Additional keys can be extracted from the provided root key as follows:

(a) a key to support secure storage and direct encapsulation (S-SAFE), in which the SUPL EMIT is sent to the UE via SMS or WAP Push and authenticated (as follows from the H-PS), and is optionally encrypted.

(b) a key to maintain a secure IP connection between the UE and the H-PS, in which X.S0024 messages are sent between the UE and the H-PS with encryption and authentication.

(c) a key to maintain a secure IP connection between the UE and PDE for non-proxy mode, in which X.S0024 messages are sent between the UE and PDE with encryption and authentication.

Each of these three keys described above is fixed in the sense that there is a deterministic value for any root key value. However, additional keys can be extracted from each of these fixed keys for encryption and authentication, the values of which depend on the random numbers provided for a particular positioning session by means of a UE and an H-PS or PDE. This key extraction and the associated security procedures use the Transport Layer Security (TLS) procedure described in IETF RFC 2246 and its PSK-TLS variant described in the IETF draft Pre-Shared Key Ciphersuites for Transport Layer Security (TLS). If X.S0024 is used for positioning in an emergency call in circuit switched mode and the E-PS is not an H-PS, then it is no longer possible to rely on a common pre-configured root key in the UE and E-PS for mutual authentication and encryption.

For SUPL, the UE can authenticate the E-SLP in order to avoid unauthorized access to the location of the UE even during an emergency call. For X.S0024, the UE and E-PS can perform mutual authentication. Table 1 lists five authentication methods, designated as Methods A, B, C, D, and E, and the characteristics of each method.

Table 1 Authentication Methods Characteristic Method A Method B Method C Method D Method E E-SLP or E-PS Authentication No Yes Yes Yes Yes UE Authentication No Limited Yes Yes Yes Roaming support Yes Yes Yes Yes No The effect of H-PLMN No No No Yes Yes Secure UE connection with V-PLMN required No No Yes No No Support without UICC / UIM Yes Yes
(note 1) Limited No No Note 1. It is assumed that the public key root certificates are provided on the mobile device (ME).

Method A provides minimal authentication. The UE enables the network-initiated positioning of the SUPL or X.S0024 from an unauthenticated E-SLP or E-PS if the SUPL INIT indicates the location for the emergency session and the UE is currently participating in the emergency session. The emergency session restriction provides some protection. In addition, SUPL INIT porting via SMS or WAP Push can provide additional confidence in the authenticity of the UE, as the porting of SMS or WAP is based on support and verification from V-PLMN and / or H-PLMN. The UE may select method A by activating security procedures using the E-SLP or E-PS. In this case, for SUPL, the E-SLP can verify the UE to a limited extent through the hash code SUPL INIT contained in the SUPL POS INIT.

Method B is for TLS public key authentication. UE and E-SLP or E-PS support TLS public key authentication, as described in IETF RFC 2246, and also described for an alternative client authentication mechanism in OMA SUPL 1.0, entitled "Secure User Plane Location Architecture". This mechanism supports E-SLP or E-PS authentication through a UE using TLS with ITU X.509 public key certificates sent via E-SLP or E-PS to the UE during the TLS phase of the handshake. Public key certificates provide a chain of digital signatures, with each signature authenticating the next, so that the UE can authenticate the E-SLP or E-PS public key, provided that the UE is provided with the public key of at least one root certification authority. The public key TLS authentication procedure supports the transfer of symmetric keys for use in subsequent encryption and authentication of signals, for example, for further SUPL or X.S0024 messages. Authentication and encryption between the UE and the SPC or PDE in non-proxy mode can also be supported using these keys or by extracting additional keys from these keys.

Method B is based on E-SLP certification or an E-public key certificate through one or more root certification authorities (for example, defined by OMA) and providing a certificate to UEs supporting SUPL or X.S0024 for emergency calls. The UE recognizes the E-SLP or E-PS name in this certificate, for example, using the fully qualified domain name for E-SLP or E-PS or the MCC-MNC identification, which the UE can match with information already known from the serving network. This enables E-SLP or E-PS authentication by the UE and, for SUPL, limited authentication of the UE by E-SLP using the 64-bit hash of the SUPL INIT included in the SUPL POS INIT and sent by the UE to the E-SLP.

For method B, a UE (e.g., a UICC or UIM) may be provided with one or more public key certificates allowing the UE to verify the E-SLP or E-PS public key (s). UEs and E-SLPs or E-PSs can establish a shared encryption key and a message authentication code (MAC) key using the TLS procedures described in RFC 2246 and one or more secure public key transfer procedures, such as RSA, DSS, or Diffie -Hellman. Encryption and authentication of SUPL or X.S0024 messages can be performed after a secure TLS connection is established. For non-proxy mode, the method set for non-3GPP2 proxy mode in SUPL 1.0 can be used to generate a shared key for authentication and encryption, according to the PSK-TLS IETF, between the UE and SPC in the SUPL or between the UE and PDE in X.S0024.

Method C is used to authenticate PSK-TLS. UE and E-SLP or E-PS support PSK-TLS (for example, as described in SUPL 1.0 for 3GPP2 SET or 3GPP2 X.S0024-0 and S.P0110-0) according to the IETF draft "Pre-Shared Key Ciphersuites for Transport Layer Security (TLS). " A pre-shared key (PSK) may be formed from (a) information (e.g., arbitrary information) provided by a UE, a network (e.g., MSC or HLR) and / or E-SLP or E-PS, (b) information (e.g., parameters) sent by or to the UE during the establishment of the emergency call, (c) security information (e.g., encryption key) already present in the MSC and the UE in order to maintain secure access in the circuit switched mode from the UE , and / or (d) other information. The security information in (c) may be available if the UE registers with the V-PLMN.

The PSK or information used to retrieve it can be made available to the UE and E-SLP (either MPC or GMLC) or E-PS (or MPC) during the establishment of an emergency call. The trust relationship established during the establishment of a call between these entities is used to obtain a secure PSK or general information from which a secure key can be extracted. UEs and E-SLPs can then use PSK-TLS to determine the location of SUPL using the received PSK. PSKs can be used to receive additional PSKs for authentication in non-proxy mode. For SUPL, mutual authentication of the UE and the E-SLP can be supported using PSK-TLS when the UE establishes an IP (PSK-TLS) connection with the E-SLP after the SUPL INIT is transferred from the E-SLP to the UE. For X.S0024, the secure PSK can be used as the root key from which the remaining security information can be retrieved as described in 3GPP2 X.S0024-0 and S.P0110-0.

Method C is based on a secure (secure) connection between the UE and the V-PLMN during the establishment of an emergency call, which involves registering the UE in the V-PLMN and mutual authentication of the UE and V-PLMN. If the UE does not have UICC / UIM or if there is no roaming agreement between the V-PLMN and the H-PLMN, mutual authentication and reliable (secure) transmission between the V-PLMN and the UE may not be achieved during the establishment of the emergency call, and any generated PSK should provide more limited protection.

Method D is used for authentication using the generic boot architecture (GBA) described in 3GPP TS 33.220 or 3GPP2 TSG-S version S.P0109. UE and E-SLP or E-PS support GBA. This allows the UE and E-SLP or E-PS to receive a secure shared key from the H-PLMN. For SUPL, this key can be used to support PSK-TLS mutual authentication between the UE and the E-SLP, as described in 3GPP TS 33.222 or 3GPP2 TSG-S version S.P0114. This method is used in SUPL 1.0 in order to support 3GPP proxy mode. The key can also be used to support TLS with HTTP Digest authentication (for example, as described in 3GPP TS 33.222), only HTTP Digest authentication between UE and E-SLP (for example, as described in 3GPP2 TSG-S version S .P0114) or other forms of authentication. For X.S0024, this key can be used as the root key from which all remaining security information can be retrieved.

Method D is based on GBA support in H-PLMN and V-PLMN and a roaming agreement between H-PLMN and V-PLMN to allow key information from the initialization serving function (BSF) in the H-PLMN to be transferred to the network application function (NAF) E-SLP in V-PLMN. Method E is used to authenticate SUPL 1.0 or X.S0024. For SUPL, if the UE is in the H-PLMN, then the E-SLP may be H-SLP, and existing authentication mechanisms specified in SUPL 1.0 can be used. For X.S0024, if the UE is in the H-PLMN, then the E-PS may be H-PS, and existing authentication mechanisms defined in X.S0024 can be used.

10 illustrates a block diagram of an embodiment of a UE 110, RAN 120, MSC 230, a location center 242, and a location server 244. The location center 242 may be GMLC 232a, MPC 232b, and / or some other entity. The location server 244 may be an E-SLP 234a, E-SLP 234b, E-PS 238 and / or some other entity. For simplicity, FIG. 10 illustrates only one processor 1010, one storage device 1012 and one transceiver 1014 for UE 110, only one processor 1020, one storage 1022, one transceiver 1024 and one communication unit 1026 for RAN 120 , only one processor 1030, one storage device 1032 and one communication unit 1034 for the MSC 230, only one processor 1040, one storage device 1042 and one communication unit 1044 for the location center 242 and only one processor 1050, one storage device 1052 and one block 1054 tie for the server 244 of the positioning. In general, each object can include any number of processors, storage devices, transceivers, communication units, controllers, etc.

In the downlink, base stations in RAN 120 transmit traffic data, overheads, and pilots to the UEs in their coverage area. These various types of data are processed by processor 1020 and adjusted to desired parameters by transceiver 1024 to generate a downlink signal that is transmitted through an antenna. At UE 110, downlink signals from base stations are received via an antenna, adjusted to a desired parameter by a transceiver 1014, and processed by a processor 1010 to obtain various types of information for calling, positioning, and other circuit switched services. For example, processor 1010 may perform processing for UE 110 in the message flow described above. Storage devices 1012 and 1022 store program codes and data for UE 110 and RAN 120, respectively. In the uplink, the UE 110 may transmit traffic data, overheads, and pilot signals to the base stations in the RAN 120. These various types of data are processed by the processor 1010 and adjusted to the desired parameters by the transceiver 1014 to generate an uplink signal, which is transmitted through the antenna of the UE. In RAN 120, uplink signals from UE 110 and other UEs are received and adjusted to parameters by a transceiver 1024 and further processed by a processor 1020 to obtain various types of information (e.g., data, service signals, reports, etc.). d.). RAN 120 communicates with MSC 230 and other entities through communication unit 1026.

At MSC 230, processor 1030 performs processing for the MSC, memory 1032 stores program codes and data for the MSC, and communication unit 1034 allows the MSC to exchange data with other entities. A processor 1030 may perform processing for the MSC 230 in the message flows described above.

At the location center 242, a processor 1040 supports positioning for the UE, a memory 1042 stores program codes and data for the location center, and a communication unit 1044 allows the location center to exchange data with other objects. Processor 1040 may perform processing for GMLC 232a and / or MPG 232b in the message flows described above.

In the location server 244, a processor 1050 performs position and / or positioning processing for the UE, a memory 1052 stores program codes and data of the location center server, and a communication unit 1054 allows the location server to exchange data with other objects. The processor 1050 may perform processing for the E-SLP 234a, E-SLP 234b and / or E-PS 238 in the message flows described above.

The techniques described herein may be implemented by various means. For example, these techniques may be implemented in hardware, firmware, software, or a combination thereof. When implemented in hardware, the processing units used to execute these techniques can be implemented in one or more specialized integrated circuits (ASIC), digital signal processors (DSP), digital signal processing devices (DSPD), programmable logic devices ( PLD), user-programmable matrix LSI (FPGA), processors, controllers, microcontrollers, microprocessors, electronic devices, other electronic units designed to perform the description functions described in this document, or combinations thereof.

When implemented in firmware and / or software, the techniques can be implemented using modules (for example, procedures, functions, etc.) that perform the functions described in this document. Firmware and / or software codes may be stored in a storage device (e.g., storage device 1012, 1022, 1032, 1042 and / or 1052 in FIG. 10) and executed by a processor (e.g., processor 1010, 1020, 1030 1040 and / or 1050). The storage device may be implemented in the processor or externally with respect to the processor.

Headings are included in this document for reference purposes, as well as to assist in the search for specific sections. These headings are not intended to limit the scope of the concepts described herein, and these concepts may be applicable in other sections throughout the detailed description.

The foregoing description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the invention. Various modifications in these embodiments should be apparent to those skilled in the art, and the general principles described herein can be applied to other embodiments without departing from the spirit and scope of the disclosure. Thus, the invention is not limited to the embodiments shown in this document, but should satisfy the widest scope consistent with the principles and new features disclosed in this document.

Claims (51)

1. A subscriber unit (UE) configured to make an emergency call in circuit-switched mode with a wireless network, interact with a location server indicated by a wireless network, and perform location determination in a user plane using a location server during a call in switching mode channels to obtain an estimate of the position of the UE before performing call setup with the public safety answering point (PSAP) 2. The UE according to claim 1, wherein the PSAP is selected based on the position estimate. 3. The UE according to claim 1, further configured to perform location determination in a user plane using a location server after performing a call setup with a public safety answering point (PSAP). 4. The UE according to claim 1, further configured to perform positioning in a user plane using a SUPL positioning platform (SLP) in accordance with reliable positioning in a user plane (SUPL) to obtain a position estimate, wherein the SLP is a determination server locations indicated by the wireless network. 5. The UE according to claim 1, further configured to perform positioning in a user plane using a positioning server (PS) in accordance with X.S0024 to obtain a position estimate, wherein the positioning server is a location server indicated by the wireless network. 6. The UE according to claim 1, further configured to receive a message from the location server to initiate location determination in the user plane, including the Internet Protocol (IP) address of the location server and communicating with the location server using IP addresses. 7. The UE according to claim 1, further configured to send location information to the wireless network during the establishment of an emergency call in the circuit switching mode, wherein the position estimate of the UE is obtained based on the location information. 8. The UE according to claim 1, further configured to receive a request for an updated position estimate of the UE and perform location determination in a user plane using a location server to obtain an updated position estimate. 9. The UE according to claim 1, further configured to authenticate the location server or to be authenticated by the location server, or to perform both before performing location in the user plane. 10. The UE according to claim 1, further configured to send UE location capabilities to the wireless network, wherein the location server is selected based on the UE's location capabilities. 11. The UE according to claim 1, further configured to send location information to the wireless network, wherein the location server is selected based on the location information. 12. The UE according to claim 1, further configured to exchange data with a wireless network for emergency call in circuit-switched mode and exchange messages with a wireless network by communication in packet-switched mode to determine a location in a user plane. 13. The UE according to claim 1, additionally configured to exchange messages to determine the location in the user plane using the short message service (SMS). 14. The UE according to claim 1, further configured to exchange messages for determining a location in a user plane using a Transmission Control Protocol (TCP) or both TCP and an Internet Protocol (IP). 15. The UE according to claim 1, wherein the wireless network is a 3GPP network and wherein the UE is configured to establish an emergency call in channel switching mode with a 3GPP network for emergency services. 16. The UE according to claim 1, wherein the wireless network is a 3GPP2 network and wherein the UE is configured to establish an emergency call in channel switching mode with a 3GPP2 network for emergency services. 17. A method for determining location, comprising the steps of establishing an emergency call in circuit-switched mode with a wireless network for emergency services; communicate with a location server indicated by the wireless network; and performing location determination in the user plane using the location server during an emergency call in circuit switching mode to obtain an estimate of the position of the UE before making a call with a public safety answering point (PSAP) to provide emergency services. 18. The method according to 17, in which the implementation of positioning in the user plane comprises the step of performing positioning in the user plane using the SUPL location platform (SLP) in accordance with reliable positioning in the user plane (SUPL) to obtain a position estimate, wherein the SLP is the location server indicated by the wireless network. 19. The method according to 17, in which the implementation of positioning in the user plane includes the steps of receiving from the location server a message to initiate location in the user plane, including the Internet Protocol (IP) address of the location server, and exchange data with the location server using the IP address. 20. The method according to 17, further comprising the steps of exchanging data with the wireless network for an emergency call in circuit switching mode and exchanging messages with the wireless network through communication in packet switching mode to determine a location in the user plane. 21. A positioning device, comprising means for establishing an emergency call in circuit-switched mode with a wireless network for emergency services; means for interacting with a location server indicated by the wireless network; and means for performing location determination in a user plane using a location server during an emergency call in channel switching mode to obtain an estimate of the position of the UE before performing call setup with a public safety answering point (PSAP) for providing emergency services. 22. The device according to item 21, in which the means for determining the location in the user plane contains means for implementing positioning in the user plane using the platform for determining the location of SUPL (SLP) in accordance with reliable location in the user plane (SUPL) to obtain a position estimate wherein the SLP is the location server indicated by the wireless network. 23. The device according to item 21, in which the means of determining the location in the user plane contains means for receiving from the server location of the message to initiate location in the user plane, including the Internet Protocol (IP) address of the location server, and means of exchange data with the location server using the IP address. 24. The device according to item 21, further comprising means for exchanging data with a wireless network for emergency calls in circuit switching mode and means for exchanging messages with a wireless network through communication in packet switching mode for determining a location in a user plane. 25. The location center, configured to receive from the first object a request for information for routing an emergency call in channel switching mode from a subscriber unit (UE) to a second object, providing information to the first object, receiving a request from the second object to evaluate the position of the UE, receiving a position estimate from a location server supporting positioning in a user plane, and providing a position estimate to the second object. 26. The location center of claim 25, wherein the first object is a mobile switching center (MSC) and the second object is a public safety response point (PSAP). 27. The location center of claim 25, further configured to use position estimation to provide information to the first entity. 28. The location center of claim 25, wherein the information provided to the first entity comprises an Emergency Routing Key (ESRK) or Emergency Routing Code (ESRD) for a Public Security Response Point (PSAP). 29. The location center of claim 25, configured to obtain a position estimate from a SUPL location platform (SLP) supporting reliable location in a user plane (SUPL), wherein the SLP is a location server supporting position in a user plane . 30. The location center of claim 25, configured to obtain a position estimate from a requesting SUPL location platform (R-SLP), wherein the R-SLP obtains a position estimate from a home SLP (H-SLP) acting as the location server that supports user plane positioning. 31. The location center of claim 25, configured to obtain a position estimate from a positioning server (PS) supporting X.S0024, wherein the PS is a location server supporting positioning in a user plane. 32. The location center of claim 25, configured to obtain a position estimate from a requesting SUPL positioning server (R-PS), wherein the R-PS obtains a position estimate from a home PS (H-PS) acting as the location server, supporting positioning in the user plane. 33. The location center according A.25, corresponding to the gateway center for determining the location of mobile communications (GMLC) in a 3GPP network. 34. The location center of claim 25, corresponding to a mobile positioning center (MPC) in a 3GPP2 network. 35. A method for determining location, comprising the steps of receiving from the first object a request for information for routing an emergency call in circuit switching mode from a subscriber unit (UE) to a second object; provide information to the first object; receive from the second object a request to evaluate the position of the UE; exchanging data with a location server supporting positioning in a user plane to obtain a position estimate before making a call with the second entity; and provide an estimate of the position in the second object. 36. A location server configured to receive a request for an estimate of the position of a subscriber unit (UE) having an emergency call in channel switching mode with a wireless network for emergency services, performing positioning in the user plane using the UE to obtain a position estimate and return an estimate position. 37. The location server according to clause 36, configured to perform positioning in the user plane using the UE in accordance with reliable location in the user plane (SUPL) to obtain a position estimate. 38. The location server according to clause 36, configured to perform positioning in the user plane using the UE in accordance with X.S0024 to obtain a position estimate. 39. The location server according to clause 36, configured to send a message to initiate positioning in the user plane with the UE, the message includes the Internet Protocol (IP) address of the location server and is used by the UE to communicate with the location server to determine the location in the user plane. 40. The location server according to clause 36, configured to replace the home location server of the UE during an emergency call in the circuit switching mode for emergency services. 41. The location server according to clause 36, configured to select a guest location server to support the positioning of the UE and the transmission of messages exchanged between the guest location server and the UE. 42. A method for determining location, comprising the steps of receiving a request to evaluate the position of a subscriber unit (UE) having an emergency call in circuit-switched mode with a wireless network for emergency services; performing positioning in the user plane using the UE to obtain a position estimate before making a call with a public safety answering point (PSAP) and returning the position estimate. 43. The method according to § 42, in which the implementation of positioning in the user plane comprises the step of sending a message to initiate location in the user plane using the UE, the message including the Internet Protocol (IP) address of the location server and used by the UE to communicate with a location server for determining a location in a user plane. 44. A subscriber unit (UE) configured to establish an emergency call in channel switching mode with a wireless network for emergency services, authenticate the location server selected by the wireless network for an emergency call in channel switching mode, and interact with the location server to obtain at least one position estimate of the UE for an emergency call in circuit switched mode. 45. The UE according to item 44, further configured to perform mutual authentication with the location server. 46. The UE of claim 44, further configured to receive a message from the location server to initiate location processing and authentication of the location server if the message indicates location processing for an emergency call and the UE participates in an emergency call in circuit switched mode. 47. The UE of claim 44, further configured to perform public key authentication for Transport Layer Security (TLS) using a public key root certificate stored in the UE to verify the public key of the location server. 48. The UE of claim 44, further configured to generate a pre-shared key (PSK) based on common information available in the UE and the wireless network and to authenticate using the pre-shared key. 49. The UE according to item 44, further configured to perform authentication based on a common bootstrapping architecture (GBA). 50. The UE according to item 44, further configured to perform authentication in accordance with reliable location in the user plane (SUPL) or X.S0024. 51. A method for determining location, comprising the steps of establishing an emergency call in circuit-switched mode with a wireless network for emergency services; authenticating the location server selected by the wireless network for an emergency call in circuit switching mode; and interacting with the location server to obtain at least one estimate of the position of the UE for the emergency call in the circuit switching mode before making a call with a public safety answering point (PSAP).

Images