METHOD AND DEVICE TO SUPPORT EMERGENCY CALLS (eCall)

I. CLAIM OF PRIORITY

The present Application for Patent claims priority to Provisional Application number 61 / 041.873 US patent filed April 2, 2008., Provisional application number 61 / 048.116 US patent filed April 25, 2008 and provisional application number 61 / 061.586 US patent, filed June 13, 2008, all entitled "Support of Minimal Network Signaling and Identification for an eCall Terminal", the copyright of which is the applicant of the present application, and incorporated herein by reference documents.

BACKGROUND

I. Field of the Invention

The present disclosure relates generally to communication, and more specifically to techniques for supporting emergency calls.

II. Description of Related Art

Wireless communication networks are widely deployed to provide various communication services such as voice data, video, packet data, messaging, broadcast, etc. Such wireless networks may be multiple-access networks that maintain multiple users by sharing the available network resources. Examples of such networks multiple access include network multiple access, code-division multiplexing (CDMA, CDMA) networks, multiple access and time division multiple access (TDMA, TDMA) networks, multiple access and frequency division (FDMA, FDMA) , network Orthogonal FDMA (OFDMA, OFDMA) networks, and Single-Carrier FDMA (SC-FDMA, FDMA, OH).

The wireless network may support communication for multiple terminals. The terminal may place an urgent call in accordance with an extraordinary event. Urgent call represents a request for urgent services (eg, police, fire brigade, medical care or other emergency services) and may also be called by calling emergency services. Urgent call can be initiated by a user who dials a well-known emergency call number, such as "911" in North America, or "112" in Europe. It may be desirable to perform an efficient exchange of signaling between the terminal and the wireless network for the emergency call in order to reduce costs signaling.

SUMMARY OF THE INVENTION

It describes technologies supporting eCall. eCall is an urgent call, which may be (i) automatically initiated by the wireless terminal due to the occurrence of the triggering event (for example, a vehicle involved in an accident), or manually by the user and (ii) includes additional data sent automatically by the terminal in the receiving entity, example item handling for public safety (PSAP, PSAR). Additional information may include vehicle identification, the location of the vehicle, triggering event, etc., and can be shipped in the same band as the transmission path of voice data, or outside the strip through a separate signaling or data transmission / text. A terminal that supports eCall, may be (i) normal wireless communication terminal that has subscribed to provide normal service, such as voice calls, packet data, text messaging, video, etc., or (ii) a terminal which It supports only eCall, which is called the terminal intended only for eCall. eCall contains urgent challenge (similar to urgent calls originated by the user who dials "911"), and automatic sending of additional data in the object reception.

In one aspect of the eCall indicator can be used to display mounted eCall. In one design, the terminal may generate a message containing an indicator eCall, and may send the message to determine the source of eCall. In one design, eCall indicator may indicate is whether or not a given call eCall. In another design eCall indicator may indicate whether a call is (i) eCall call, initiated automatically by the terminal or (ii) eCall call, initiated manually by the user. ECall indicator may also transmit other information.

ECall indicator may be implemented in various ways. The first structure may include a message category information services having at least one bit used for the eCall indicator. In the second design message can contain new information element containing an indicator eCall. The third structure may comprise a message type information element service connection management (CM, CE) having at least one value used for the eCall indicator. In the fourth construction element may comprise a message code information COS Classmark 2 mobile station (MS, MS) having at least one flag used for the eCall indicator. The fifth design message may contain the calling party number reserved and used for the indicator eCall. ECall indicator may also be transmitted in other ways.

In another aspect, a terminal intended only for emergency calls eCall, can be eliminated the need to send signaling to the mobile communication control (MM) and connection management (CM) in a wireless network, except eCall and designated calls. Scheduled calls may include calls to check the function of eCall, calls for a reconfiguration of the terminal and / or certain other special challenges. For example, the call destination can be resolved to a specific number assigned by the home wireless network associated with the service of the client, which can be used to request a change of terminal configuration (for example, converting a terminal-only eCall, the terminal, which is arranged to provide normal services and eCall and to verify that the terminal is working correctly. A terminal intended only ECall, may periodically search for wireless networks after power, but may eliminate sending signaling to detected networks. A terminal can provide the possibility of preventing the update location, perform registration response to the paging request, etc. The terminal may perform exchange signaling with the wireless network for the eCall or during a special call initiated by the terminal. In one arrangement, after the eCall or initiate a special call, the terminal may perform location update in a local ( in the wireless network) and a connection for the eCall or a special call.

Various aspects and properties of the disclosure are described in further detail below.

BRIEF DESCRIPTION OF DRAWINGS

1 shows an example deployment.

2 shows a message flow for eCall establishment by a terminal.

Figure 3 shows the SETUP message to the emergency situation, in which light is transferred eCall.

Figure 4 shows a request message to the service of CM, which carries light eCall.

5 shows a set-up message SETUP, which carries the eCall indicator.

6 shows a process performed by a terminal for eCall establishment.

7 shows a process performed by the network to support eCall establishment.

8 shows the operation of the terminal during normal signaling.

FIG. 9 shows the operation of the terminal, only works with eCall, with reduced signaling.

FIG. 10 shows a state diagram for a terminal designed for eCall establishment.

FIG. 11 shows a process performed by a terminal.

FIG. 12 shows a process performed by a wireless network.

FIG. 13 is a block diagram of a terminal, a base station and MSC.

DETAILED DESCRIPTION OF THE INVENTION

FIG. 1 shows an example deployment of a network 100, which may include a visited network 102, home network 104 and network 106 to a third party. Visited network 102 may also be called a visited public land mobile network (V-PLMN, n-PLMN), the serving network, etc. Home network 104 may also be called a home PLMN (HPLMN, DONMS). Visited network 102 may be a network service for the terminal 110, which may be roaming with respect to its home network 104, as assumed in much of the description below. Visited network 102 and home network 104 may be the same network if terminal 110 is not in a roaming state.

Visited network 102 may include a radio access network 120 (RAN, MPD), a mobile switching center (MSC, SSC) / visitor location register 130 (VLR, HLR) and other network entities not shown in FIG. 1 for simplicity. RAN 120 may be a network of the Global System for Mobile Communications (GSM, SMS), the network multiple access wideband CDMA (WCDMA, WCDMA) network, a General Packet Radio Service (GPRS, COOP) network, Long Term Evolution (LTE, TDD) CDMA IX network, a network of high-speed packet Packet Data (HRPD), Ultra Mobile Broadband (UMB), etc. GSM, WCDMA, GPRS and LTE are part of Universal Mobile Telecommunications System (UMTS, UMTS) and are described in documents from an organization named "3rd Generation Partnership Project" (3GPP). CDMA IX and HRPD are part of cdma2000, and cdma2000 and UMB are described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2). MSC 130 can perform the switching function to call through the switchboard subscriber lines and can also send messages to the short message service (SMS, SMS). VLR 130 may store registration information for the terminals, which are registered in the visited network 102.

Home network 104 may include network home location register (HLR, RMD) / 140 Authentication Center (AC, CA) and other network entities not shown in FIG. 1 for simplicity. HLR 140 may store subscription information for the terminals that are subscribed to services in the home network 104. AC 140 may perform authentication for the terminals with service subscription in the home network 104.

A third party network 106 may include a router 150 (e.g., a router, a selected PSAP), PSAP 160, the telephone public switched network (PSTN) 170, and possibly other network entities not shown in FIG. 1. The router 150 can route calls between the MSC 130 and PSAP 160. PSAP 160 may be responsible for answering emergency calls and can also be called the center of emergencies (EC, TSCHS). PSAP 160 may belong to and can be controlled by a government agency, such as county or city. PSTN 170 may provide telephony services for traditional wired phones, such as telephone 180.

FIG. 1 shows only some of the network entities that may be present in the visited network 102 and home network 104. For example, the visited network 102 may include network entities supporting packet-switched calls and other services, as well as the location server, which contributes obtaining the location of the terminal.

Terminal 110 may be stationary or mobile and may also be called a mobile station (MS) in GSM and CDMA IX, a user equipment (UE, OP) in WCDMA and LTE, an access terminal (AT, AT) in HRPD, a terminal enabled SUPL (SET ) in a reliable determination of the user plane location (SUPL, NOMPP), a subscriber unit, a station, etc. Terminal 110 may be a device such as a cellular phone or other wireless device data, the device personalized data communication system (PCS, PSP), a personal navigation device (PND, ZC), a personal information manager (PIM, PIM), Personal Digital Assistant (PDA, PDA), laptop or other suitable mobile device that can receive transmitted wireless data and / or navigation signals. Terminal 110 may also be a device which communicate with a personal navigation device (PND), such as wireless, operating in a short distance infrared wired connection or a compound of another type, regardless of whether the reception of the satellite signal, receiving assistance data and / or processing related to locating the device or PND. In addition, the terminal 110 is intended to include all devices, including wireless communication devices, computers, laptops, etc. which are capable of communicating with a server, for example via the Internet, WiFi, or other network, and regardless of the running Whether the satellite signal reception, assistance data reception, and / or processing related to the position determination device in a server or other device connected to the network. Any combination of the above working is also included. Terminal 110 may also be a specialized system installed in the vehicle (IVS, STS) which can be permanently installed, and possibly part of the vehicle.

Terminal 110 may have a subscription to a home network 104 and may be roaming in the visited network 102 as shown in FIG. 1. Terminal 110 may receive signals from RAN 120 in visited network 102 or may communicate with the RAN, to obtain communication services (data transmission). Terminal 110 may also communicate with the home network 104 for providing data services when not roaming (not shown in FIG. 1). Terminal 110 may also receive signals from one or more satellites 190, which may be part of a satellite positioning system (SPS, MSP). SPS typically includes a system of transmitters arranged so that it is possible to determine the location of objects on or above the Earth's surface based at least in part of the signals received from the transmitters. Such a transmitter typically transmits a signal marked with a repeating pseudo noise (PN, PN) code, which consists of a set of a plurality of chips and may be located on the ground control stations, user equipment and / or space vehicles. In a particular example, such transmitters may be located on satellites (SV, SC) orbiting the Earth. For example, SV, belongs to the constellation of Global Satellite Navigation (GNSS, SGSN), such as a global positioning system (GPS), Galileo, Glonass and Compass, can transmit a signal marked with PN code which can be distinguished from PN codes transmitted by other SV in the constellation (e.g., using different PN codes for each satellite as in GPS, or using the same code on different frequencies as in Glonass). In accordance with certain aspects of the technology presented herein is not limited to global systems (e.g., GNSS) for GPS. For example, the technology provided here can be applied to or otherwise implementing them for use in various regional systems, such as, for example, the system satellites Quasi-Zenith (QZSS, RCMS) over Japan, Indian Regional satellite navigation system (IRNSS, IRSSN) over India, the system Beidou over China, etc., and / or a variety of additional systems (such as satellite monitoring and correction (SBAS, URCC)) that may be associated with or otherwise used for one or more global and / or regional navigation satellite systems. By way of example but not limitation, SBAS may include a system (s) monitoring and correction, which provides integrity information, differential corrections, etc., such as, e.g., Wide Area Augmentation System (WAAS, SHZSR), European Geostationary Navigation Overlay System (EGNOS, EGDNS) Multi-Satellite Amplification System (MSAS, MSUS), Global System enhance navigation through GPS, or system extension navigation GPS and the global expansion of the navigation system (GAGAN, GRNS) and / or the like. Thus, as used herein, SPS may include any combination of one or more global and / or regional navigation satellite systems and / or augmentation systems, and SPS signals may include SPS, type signals SPS and / or other signals associated with such one or more SPS. Terminal 110 may measure signals from satellites 190 and obtain measurement results of these pseudo satellites. Terminal 110 may also measure signals from base stations in RAN 120 and obtain timing characteristics and / or signal strength measurements for the base stations. Results pseudorange measurements, the results of timing measurements or signal strength measurements may be used to obtain a position estimate for terminal 110. A location estimate may also be referred to in determining the location estimate, and fix the position etc.

Terminal 110 may have a number of International Mobile Equipment Identification (IMEI), which is a unique number assigned to the terminal. The terminal 110 can be used to subscribe to the service user. Subscription to the service may be associated with a number of International Mobile Subscriber Equipment Identity (IMSI, MIOM), which is a unique number assigned for the subscription in GSM and UMTS. Subscription to the service may also be associated with a number of mobile stations International Digital Network Integrated Services (MSISDN, MNTSSKU), which is a phone number for service subscription. IMSI can be used as a key for the service subscription in the subscriber database in HLR 140. MSISDN can be dialed to call the other user terminal 110 used for the service subscription. IMSI, MSISDN and other subscription information may be stored in the subscriber identification module (SIM, SIM) or Universal Subscriber Identity Module (USIM, Umia) which can be inserted in the terminal 110. The terminal 110 also may have no SIM / USIM, and in this case, the terminal 110 may have only IMEI and IMSI does not have or MSISDN.

Wireless networks may be required to support different types of emergency calls. One type may include a "normal" emergency calls that are users who call in well-known emergency call numbers such as "911" in North America and "112" in Europe. Another type may include eCall, which represent emergency calls, which may have the characteristics described above. Support for eCall may be required by the European Union and in other regions and / or countries. eCall can be different from a normal emergency call, the manner in which they are placed eCall, and to additional data relating to the urgent calls that can be sent (transferred) to establish eCall and which can be used to process eCall. For example, additional information may be denoted as eCall has been initiated, the vehicle type and number of the vehicle identification (VIN, BAT), the time stamp, to assess the situation and the flag of confidentiality provisions, the direction of movement, the number of passengers (eg, wearing seatbelts) service provider for the terminal (if any), the type of initiating event (e.g., triggered airbags, bumper sensors, etc.), and possibly other information. Additional information may enable transmission of precise geographical location of a terminal in the PSAP.

FIG. 2 shows the design flow 200 for establishing communications eCall terminal 110 in FIG. 1. For simplicity, certain network entities (e.g., RAN 120) and at least some of the relevant signaling messages are not shown in FIG. 2. Terminal 110 may receive the first radio access to the serving base station and may send (convey) message CM service request to MSC / VLR 130 to the service request (step 1). MSC / VLR 130 can receive messages and can respond to the message of the reception services CM (step 2). Terminal 110 may then transmit the SETUP message to initiate an emergency eCall (step 3). MSC / VLR 130 may receive the message and may transmit an original address message to the router 150 to initiate a call to the terminal 110 (step 4). Router 150 may then transmit a call setup message 160 to the PSAP call setup terminal 110 (step 5). PSAP 160 may return a connect message to the router 150 (step 6), which may then return a response message to MSC / VLR 130 (step 7). MSC / VLR 130 can then connect message back to the terminal 110 (step 8). Terminal 160 may transmit additional data to eCall network, which may be transmitted PSAP 160 (step 9). Transmitting additional data can also be performed in steps 3, 4 and 5 or some other steps before the step 9. In any case, eCall can be set for terminal 110 after steps 8 and 9. Terminal 110 may then be contacted with the PSAP 160 eCall.

eCall may be initiated automatically by the terminal 110 (e.g., in a collision of the vehicle) or manually by the user (e.g., which is inside the vehicle). Terminal 110 may be any device that supports the functionality of eCall, such as a cell phone, IVS, etc. In one design, terminal 110 may provide the eCall indicator installation emergency call. ECall indicator may transmit one of the following:

• initiated manually by the user eCall (MIeC), or

• automatically initiated eCall (AIeC), transmitted to the terminal.

ECall indicator may be used to distinguish wireless network eCall from normal emergency call, or to filter the corresponding direction eCall PSAP (e.g., PSAP, equipped for receiving eCall), and / or for another purpose. ECall indicator may be transmitted to the terminal 110 in various ways during the emergency call setup. ECall indicator may be transmitted in the CM service request message, in the message Emergency SETUP for emergency situations SETUP message, or some other message transmitted by the terminal 110.

FIG. 3 shows the structure of posts 300 Emergency SETUP, which can carry light eCall. Emergency SETUP message may include various information elements (IE, IE), one of which may be a service category IE used to provide wireless network service information requested by the terminal. For eCall IE search services may include (i) the identifier IE service category (IEI, LEI), which can be set as a specific value assigned to the IE search services, (ii) length of the field service category, which may indicate the length of the IE search services, and (iii) the value field of emergency services category, which can provide information for eCall.

In the arrangement shown in FIG. 3, eCall indicator may be implemented by two bits in the value of the category of emergency services. One bit (designated as bit x) can be set to "1" when the transmission is automatically initiated eCall or otherwise, can be set to "0". Another bit (labeled bits y) may be set to "1" for transmitting manually initiated eCall or otherwise, can be set to "0". In another design eCall indicator may be implemented by a single bit which may be set to "1" to indicate the eCall or "0" otherwise. ECall indicator may also be implemented in other ways IE service category.

In another design, a new IE may be defined to transfer the eCall indicator. For this new IE may be assigned a separate IEI, and it eCall indicator may carry one or two bits, which can be installed as described above for the IE service category.

FIG. 4 shows the structure of a service request message CM 400, which may carry eCall indicator. CM service request message may include various IE, such as the CM service type IE, is used to determine which service is requested from the wireless network. IE CM service type may include (i) IEI, which can be set as a specific value assigned to the CM service type IE, and (ii) the type of service field, which may indicate the requested service.

In one design, for eCall one or more values ​​for the service type field may be reserved and can be used to transmit eCall indicator. In one design, a single value may be reserved for the eCall indicator. Service type field may then be set for this reserved value to request emergency services for an eCall. In another design, the two values ​​may be reserved for the eCall indicator. Service type field may then be set to (i) first reserved value to request emergency services for a manually initiated eCall or (ii) a second reserved value to request emergency services for automatically initiated eCall.

CM service request message may also include an MS Classmark 2 IE, is used to provide information related to a terminal for a wireless network. Octet 1 of this IE can include IEI for MS Classmark 2 IE. Octet 2 may include the length of the MS Classmark 2 IE. Octets 3, 4 and 5 may include various fields / flags described in publication 3GPP TS 24.008, entitled "Mobile radio interface Layer 3 specification; Core network protocols; Stage 3", which is publicly available. As shown in FIG. 4, three spare bits / flags may be present in the MS Classmark 2 IE, and may be in the normal state are set to "0". In one design, one spare bit (e.g., bit 8 of octet 3) may be used for the eCall indicator and may be set to "1" to indicate a terminal for eCall-only, or "0" otherwise. In another design, the two spare bits may be used for the eCall indicator. One spare bit (e.g., bit 8 of octet 3) may be set to "1" to indicate automatically triggered terminal for eCall-only, or "0" otherwise. Another spare bit (e.g., bit 7 of octet 5) may be set to "1" to indicate a triggered manually terminal for eCall-only, or "0" otherwise.

FIG. 5 shows the construction of 500 posts SETUP, which can carry light eCall. SETUP message may include various IE, such as an IE called party BCD numbers used to identify the called party. Octet 1 of this IE may include an IEI for IE called party BCD numbers. Octet 2 may include the length of the IE called party BCD numbers. Octet 3 may include the type of the called party number and numbering plan accessible to the called party number. Each subsequent octets may include up to two digits of the called party.

In one design, the reserved called party number may be used as the eCall indicator, and it can be transmitted in the SETUP message to indicate the eCall. In another design, two reserved called party number can be used to display eCall. First reserved called party number may be passed in the SETUP message to indicate manually initiated eCall. The second reserved called party number may be passed in the SETUP message to indicate automatically initiated eCall.

In one design, the reserved number (s) of the called party can be a full phone number, which can be reserved for eCall all or a plurality of network operators. In another design, the reserved number (s) of the called party may be extended versions of the usual emergency phone numbers. For example, "911-1" and "911-2" can be used as reserved called party number to manually or automatically initiated eCall, respectively, in North America. Accordingly, "112-1" and "112-2" can be used as reserved called party number for the eCall, initiated manually and automatically, respectively, in Europe. Another phone number (s) may also be reserved and can be used as an indicator of eCall.

In yet another design, a subscription information of the HLR can be used to denote a terminal intended only for the eCall. FIG. 1, terminal 110 may begin eCall in the visited network 102 and may perform registration prior to installation of the call. To register VLR 130 in visited network 102 may communicate with HLR 140 in home network 104 to obtain subscription information for terminal 110. HLR 140 may provide information indicating that the terminal 110 is a terminal intended only for the eCall. Visited network 102 may then serve terminal 110 for eCall.

Various designs eCall indicator described above may be used to indicate explicitly that eCall has been placed by the terminal. Some or all of these designs can also be configured to recognize between eCall, initiated manually, which was launched by the user and eCall, initiated automatically, which has been started by the terminal, for example, as a result of an accident. ECall indicator may also be sent in other messages and / or using other fields, bits and values ​​other than those described above.

FIG. 6 shows the structure of a process 600 performed by a terminal for eCall establishment. The terminal may generate a message containing the eCall indicator (block 612). This message may contain a service request message CM, Emergency SETUP message, a SETUP message or some other message. The terminal may send a message to start the eCall (block 614).

The first structure may include a message category information services having at least one bit used for the eCall indicator, e.g., as shown in FIG. 3. In one design, the at least one bit used for the eCall indicator, may comprise (i) a first bit indicating whether the eCall is initiated automatically by the terminal, and (ii) a second bit indicating that eCall has been initiated manually by the user. In another design, the at least one bit used for the eCall indicator, may comprise a single bit indicating whether the eCall is initiated.

In the second configuration message may include a new information element comprising the eCall indicator. The third message may comprise a structure information element CM service type, having at least one value for use as the eCall indicator, e.g., as shown in FIG. 4. In the fourth structure may comprise connection information element MS Classmark 2, having at least one flag is used as the eCall indicator, e.g., as shown in FIG. 4. In the fifth design of a message may comprise a called party number reserved for the eCall indicator, e.g., as shown in FIG. 5. The eCall indicator may also be transmitted in other ways, for example using other messages and other items of information bits or other values, etc.

FIG. 7 shows a design of a process 700 performed by a wireless network to support the establishment of eCall. The network may receive the message for the beginning eCall from a terminal (block 712). The network may receive the eCall indicator from the message (block 714). The network may determine whether the eCall is initiated automatically by the terminal or manually by a user based on the eCall indicator (block 716). In one design, the message may contain a service category information, having first and second bits are used as the eCall indicator. The first bit may indicate whether the eCall is initiated automatically by the terminal and the second bit may indicate whether the eCall is initiated manually by a user. ECall indicator may also be transmitted by other means.

A large number of terminals eCall-only, can be deployed, for example, in vehicles and in other areas. Catering to these terminals, intended only for eCall, can be fed for long periods of time, but they can rarely start eCall. It may be desirable to reduce the amount of signaling exchanged operate with terminals designed only eCall, to reduce costs signaling in wireless networks.

FIG. 8 shows the operation of the terminal 800 110 at an exchange normal alarm. After switching terminal 110 can search for wireless networks, where it can receive the service. Terminal 110 may then perform registration and location updating with the detected network. Registration can allow the network to identify the presence of a terminal. Location update can allow the network to obtain terminal location, so that the network can call the terminal at incoming calls. Terminal 110 may then periodically search for better cells and / or networks. After best detection cell or network, terminal 110 may perform the location update and possibly the registration, if necessary. Terminal 110 may perform a call setup, at any time, in order to start the eCall. Terminal 110 may then communicate with the PSAP for the eCall. Terminal 110 may perform deregistration after eCall.

Terminal 110 may perform location update any number of times and at any frequency, depending on its mobility and network coverage. Terminal 110 may perform exchange signaling with the wireless network in each case the location update. Terminal 110 may eCall is extremely rare, and the information exchanged in most cases, the location update can not be used. For a terminal intended only for the eCall, thus, can be extremely inefficient to perform a location update plurality of times before the call establishment.

FIG. 9 shows operation 900 of terminal 110, which may be a terminal for eCall-only, a reduced amount of signaling. After switching terminal 110 can search for wireless networks, from which it can receive the service. Terminal 110 may receive information about the availability of network information synchronization and / or other information systems of the network discovery and may store this information for eventual use in establishing eCall, if necessary. Terminal 110 may transmit signaling to eliminate the mobility management (MM) and connection management (CM), and can maintain radio silence with the detected network. Wireless networks can have presence information of the terminal 110. Terminal 110 may periodically search for better cells and / or networks, and can update its information to the serving network and the potential of the potential serving cell.

Terminal 110 may receive the designation to start eCall, e.g., from the user or based on a triggering event. In response to this, the terminal 110 may perform registration and location updating with the last detected network. Terminal 110 may then perform call establishment for the eCall, e.g., as shown in FIG. 2. Typically, the terminal 110 may perform registration before or after the call setup for the eCall. Terminal 110 may also perform location update at the beginning or during eCall eCall. Terminal 110 may perform location update when supported callback (e.g., the selected PSAP) and can transmit the location update in other cases.

The terminal 110 can communicate with the PSAP for the eCall. eCall can be stopped at a certain time. In one design, terminal 110 may continue to support the MM and CM procedures for a limited period of time. It may also be desirable to provide support for a callback from the PSAP and provide the terminal 110 can quickly accommodate future recall if necessary. If the service subscription for terminal 110 (which may be stored in the HLR 140) does not prevent incoming calls, then the PSAP may be able to call back to the terminal 110 for a limited period of time. After this limited time period, terminal 110 may perform IMSI detach, if required by the serving network. The serving network may also cancel the registration of the terminal 110 after a predetermined period of time that has elapsed since the end of the eCall. Deregistration can be carried out automatically, without the need to exchange signaling with the terminal 110.

As shown in FIG. 8 and 9, the cost of the alarm can be substantially reduced if the terminal 110 excludes perform location update when the power and performs location update only when initiated eCall.

It may be desirable to perform a location update before the call establishment for eCall, e.g., as shown in FIG. 9. The location update can provide the ability to authenticate terminal 110 and downloads the subscription information for the terminal 110 from the HLR 140 in home network 104 to the VLR 130 in visited network 102. The subscription information may include the MSISDN of the terminal 110. MSC 130 may transmit the authenticated eCall with MSISDN to PSAP 160. PSAP 160 can use the MSISDN for the callback to the terminal 110, if necessary.

In one design, a location update for the eCall may have a higher priority than the normal location update, to facilitate call set-up for eCall. Terminal 110 may transmit a location update request being initiated eCall for CM. Post location update request may indicate incomplete eCall or emergency call in order to inform the visited network 102 (e.g., MSC / VLR 130) of unfinished call and to allow the visited network 102 to set a priority for a location update. In one configuration update request message to the location may include a location update type IE having a predetermined bit that may be set to "1" to indicate the progress eCall or emergency call or a "0" otherwise. Visited network 102 may set the priority during the processing, if the unfinished challenge eCall or emergency call will be indicated in the request message, a location update.

The terminal 110 can not perform the location update and may have no connection before establishing MM eCall, e.g., as shown in FIG. 9. Delay eCall for call establishment can be reduced in several ways. In one design, terminal 110 may be identified by its IMEI, IMSI as to subscribe to the service may be unknown to the VLR 130. unauthenticated eCall, which has no identification callback (e.g., where no MSISDN), can then be transmitted to the PSAP 160 . This arrangement can be used in countries and networks supporting unauthenticated eCall. In another design, terminal 110 may send a request message to the service, CM for eCall and can identify themselves in the IMSI. This may allow for MSC / VLR 130 to query 102 in the visited network authentication information from HLR / AC 140 to the home network 104. MSC / VLR 130 may authenticate terminal 110 and then may transmit the authenticated eCall to PSAP 160. In yet another design, one terminal 110 may include a SIM / USIM, may be authenticated and can handle MSISDN. MSISDN may be transmitted to the PSAP to identify and callback.

FIG. 10 shows a structure diagram 1000 states for mobility management (MM) to a terminal for eCall-only, such as the terminal 110. For simplicity, not all the states and substates available for mobility management is shown in FIG. 10.

After powering the terminal 110 may operate in a non-activated substate eCALL INACTIVE for state MM IDLE. Substate eCALL INACTIVE can claim rimenyatsya in a terminal-only eCall, where the operator of a home network requires a normal support for eCall, for example, to a location update, authentication, identification terminal for PSAP, and may be to refer to the possibility of a callback from the PSAP. Terminal 110 may transition into the INACTIVE substate eCALL, in order to avoid the need for signaling to a mobility management and control compound in the absence eCall or a special call. Special challenges can include calls MSISDN, they are not urgent started home network operator services for testing and reconfiguration of the terminal. For example, a special call can be resolved to a specific number assigned to your home network operator associated with the service of the client, and can be used to request a change of terminal configuration (for example, converting a terminal-only eCall, the terminal adapted to receive a normal service, and eCalls) to check that the terminal is working correctly, etc.

In eCALL INACTIVE substate, the terminal 110 can eliminate the performance of registration, location update and IMSI detach and can also eliminate the need to respond to requests paging. Terminal 110 may also reject any requests from the object, see the terminal 110 for the compounds of MM, except eCalls and designated calls. Terminal 110 periodically searches for wireless networks while in the substate eCALL INACTIVE. However, only eCall and assigned calls can be made available to the terminal 110, while it is in the substate eCALL INACTIVE.

In eCALL INACTIVE substate actual subscriber information may be available for the terminal 110, the update status may be "OFF" (or U4), and the cell that can provide normal service to the terminal 110, may be selected. Update Status DISABLED may indicate that the location update is disabled and that the SIM / USIM does not contain any actual LAI (IO, Id location area), TMSI (VIMA temporary mobile subscriber identity), encryption key GSM, the integrity key UMTS encryption key UMTS, or the sequence number of the encryption key. All of these fields may be set to "deleted" after entering eCALL INACTIVE substate for compatibility reasons. The presence of other values ​​may be regarded as an error of the terminal 110. The "location update condition", stored in the SIM / USIM, can be set to "not updated".

From the INACTIVE substate eCALL, terminal 110 may maintain awareness of the potential of the potential serving cell in the serving network but can not initiate a signaling network MM and may ignore any paging request. Terminal 110 may exit the eCALL INACTIVE substate if one of the conditions described below.

- If the removed SIM / USIM, then terminal 110 may enter a substate NO IMSI.

- If you lose the coverage area, then the terminal 110 can enter the substate PLMN SEARCH.

- If the device is disabled (e.g., turned off) by the user, then the terminal 110 can come out of the MM IDLE state and enter a state of NULL.

- If there is a request to CM eCall, then terminal 110 may attempt to perform IMSI attach procedure, if required by the serving network or may otherwise attempt to perform a normal location update. After this, the terminal 110 can perform other procedures MM and CM to establish eCall.

- If there is a CM request to a designated call (e.g., for testing or configuration changes terminals), then terminal 110 may attempt to perform IMSI attach procedure, if required by the serving network or may otherwise attempt to perform a normal location update. After this, the terminal 110 may perform other MM and CM procedures to establish the call destination.

Terminal 110 may emerge from MM IDLE, when initiated eCall or designated call another. Terminal 110 may then maintain normal procedure, MM and CM, for call setup and communications during a call.

Terminal 110 may go into substate NORMAL state MM IDLE after the eCall or designated call. In one design, terminal 110 may continue to support the MM and CM procedures for a limited period of time, while in the substate NORMAL. This limited period of time may be set to the home network operator (e.g., as a fixed or configurable value), and may be stored in the SIM / USIM. Terminal 110 may support a timer or Txxxx Tyyyy after the eCall or designated call to maintain traceability during this limited period of time. In one design, the timer may be used to Txxxx closure eCall, and Tyyyy timer can be used to call the designated closure. If the service subscription for terminal 110 does not prevent incoming calls, then the PSAP may call back terminal 110 during the limited time period. Upon completion of the limited time period, terminal 110 may perform IMSI separation, if required by the serving network, and may re-enter the INACTIVE substate eCALL.

Terminal 110 may perform process inactive eCall, when the timer Txxxx or timer Tyyyy terminates or if it is determined that their work has been finished, in any sub-state within the state MM IDLE, except NO IMSI, NO CELL AVAILABLE (not shown in FIG. 10) or a PLMN SEARCH substate. Terminal 110 may stop the other active timers and can perform the procedure of separation IMSI, the serving network if required, and if the update status is "UPDATED" (or Ul). Terminal 110 may then move into eCALL INACTIVE substate within the state MM IDLE. Table 1 details the status of timers and Txxxx Tyyyy, in accordance with one design.

Table 1TaymerSostoyanie MMZnachenie time ozhidaniyaPrichina nachalaNormalnaya ostanovkaPosle expiration vremeniTxxxxVse, with the exception-tion NULL3600 sekundTerminal designed-tion only eCall, enters the state MM IDLE after the emergency call • Timeout • Turning off the power • Removing restrictions only eCall Run procedure inactive the first eCall TyyyyVse, with the exception NULL900 sekundTerminal-tion, is-tion only eCall, enters the state MM IDLE after the test call / call reconfiguration • Timeout • Turning off the power • Removing restrictions only eCallVypolnit procedure inactive the first eCall

In all cases the yield of substates eCALL INACTIVE, except for the entrance to the substate PLMN SEARCH or condition NULL, both timers Txxxx and Tyyyy can be reset so that none of the timer is not considered as expired, and any of them can be restarted, when the terminal in the next time is included in the MM IDLE state.

Terminal 110 may transition from the INACTIVE substate eCALL, for example, if it is disabled (switched off), will be deleted if the SIM / USIM or if the terminal 110 is manually re-enabled by the user. Reactivation manual may be optional features, and can be caused by using a special function menu button or switch on the terminal 110.

In one design, which is not shown in Figure 10, the terminal 110 may move into NORMAL substate, after power-up or re-activation by hand, and can operate in NORMAL substate for a predetermined period of time, which may be a fixed or configurable duration again. In one design, terminal 110 may perform attachment IMSI, the location update and possibly other MM and CM procedures (e.g., responding paging) within a predetermined period of time. During this predetermined time period home network 104 may reconfigure the SIM / USIM in the terminal 110 and the normal subscription service to add and delete eCall-only state. HLR 140 may also hinder the implementation of other services for the terminal 110, but may allow incoming calls to support callback PSAP. Terminal 110 may inhibit incoming calls for a predetermined period of time, except when there is a preceding eCall.

Terminal 110 may be a terminal for eCall-only, but may have a subscription to other services provided by the network operator. The configuration of the terminal 110 can be repeatedly changed during or after the eCall so that it has the ability to access the services to which you have subscribed. This may be achieved as follows. Terminal 110 may maintain a normal call service option for a user, for example, via a menu or a special function key on the terminal 110. In case of activation, the terminal 110 can cause the location update. HLR 140 in home network 104 may receive a location update from a terminal 110 and may provide the minimum subscription information to the VLR 130 in visited network 102. HLR 140 may also reconfigure the SIM / USIM in the terminal 110, e.g., via SMS. If the user has a subscription to the service, then the terminal 110 may allow the user to call the service for which you have subscribed to, such as an outgoing call or SMS. If the user does not have a subscription to the service, then it may be a location update, but the terminal 110 may not allow the user to call any services or visited network 102 may not be allowed any services caused by the user. Terminal 110 may perform location update to exclude at other times, except for (i) for a particular duration (e.g., 10-60 minutes) after calling eCall and (ii) within a certain other particular duration (e.g., 15 minutes) after the call normal service.

User terminal 110 can also be configured to change the network operator / service provider, for example, to another SIM / USIM. The user can also modify existing subscription parameters used at the terminal 110.

Terminal 110 may have a normal subscription and your network operator may change the configuration of SIM / USIM in the state only for eCall. Terminal 110 may then enter into the sublevel eCALL INACTIVE after a specified period of time.

11 shows a design of a process 1100 performed by a terminal. The terminal can eliminate the transmission of signaling for mobility management (MM) and connection management (CM) in wireless networks, except for eCall and call destination (block 1112). The terminal may periodically search for wireless networks after power without detectable signaling networks. The terminal may perform location update to exclude, that the registration and reply to a paging request.

The terminal can perform signaling exchange with the wireless network for the eCall or designated call initiated, a terminal, such as terminal is automatically initiated or initiated manually by the user (block 1114). In one design, the terminal may perform location update in a wireless network after the eCall or designated initiating the call. The terminal can transmit a message containing an incomplete designation of eCall emergency call or location update, which can speed up the update location. The terminal may also perform call establishment for the eCall or designated call, e.g., as shown in Figure 2. The terminal may send a message containing the eCall indicator for call establishment. ECall indicator may comprise any of the items of information bits, values, etc., described above.

In one design, the terminal may exchange signaling for mobility management and connection management for a predetermined period of time after the eCall or designated call, e.g., within seconds after closure Thhhh eCall, or Tyyyy seconds after the assigned call. The terminal may prevent transmission of signaling for mobility management and connection management after a preset period of time. In one design, the terminal may perform exchange signaling for mobility management and connection management (e.g., for connection to the network, the location update response to the paging request, reconfiguring of allowed services, etc.) for a limited period of time after power- or manual re-activation of the terminal. The terminal may prevent the transmission of signaling for mobility management and connection management after this limited period of time.

12 shows a design of a process 1200 performed by a wireless network to support eCall establishment. The network can not receive any signaling for mobility management and connection management (e.g., for location update) from a terminal except for the eCall and designated calls (block 1212). The network can exchange signaling with the terminal for the eCall or a designated call initiated by the terminal (block 1214). In one design, the network may perform location update of the terminal when the eCall or designated call is initiated, and can also serve as a connection terminal for the eCall or designated call.

13 shows a block diagram of a design of terminal 110, base station / RAN 120 and the MSC / VLR 130 of FIG. 1. At terminal 110 encoder 1312 may receive data and messages transmitted by terminal 110. These messages can be used for registration, location update, establishing connections, etc. Encoder 1312 may process (e.g., encode, and interleaves) the data and messages and provide coded data and coded signaling. A modulator (Mod) 1314 may further process (e.g., modulate, allocate channels and scramble) the encoded data and signaling and provide output samples. A transmitter (TMTR) 1322 may perform output processing (e.g., convert to analog, filtering, amplification and frequency upconverts) the output samples and generate a signal transmitted on the uplink, which may be transmitted to one or more base stations in RAN 120. Terminal 110 may also receive signals from the downlink data channel transmitted to one or more base stations. A receiver (RCVR) 1326 may perform pre-processing (such as filtering, amplification, downconversion and digitizes) the received signal and provide input samples. A demodulator (Demod) 1316 may process (e.g., descramble, the processing channels and demodulate) the input samples and provide symbol estimates. A decoder 1318 may process (e.g., deinterleave and decode) the symbol estimates and provide decoded data and messages sent to terminal 110. Encoder 1312, modulator 1314, demodulator 1316 and decoder 1318 may be implemented by a modem processor 1310. These units may perform processing in accordance with the radio technology (e.g., GSM, WCDMA, LTE, etc.) used for a wireless network in which the terminal 110 is in the data mode. Controller / processor 1330 may direct the operation of various units at terminal 110. Processor 1330 and / or other modules at terminal 110 may perform or direct process 600 in FIG. 6, process 1100 in FIG. 11 and / or other processing techniques described herein. The memory 1332 may store program codes and data for terminal 110. SIM / USIM 1334 may store subscription information for the subscription of the services used in the terminal 110.

The base station / RAN 120, the transmitter / receiver 1338 may support radio communication with terminal 110 and other terminals. Controller / processor 1340 may perform various functions for communication with the terminals. For uplink data transmission uplink signal from terminal 110 may be received and may be further processed by receiver 1338 and further processed by controller / processor 1340 to recover the data and messages transmitted by terminal 110. For the downlink data channel data and messages may be processed by the controller / processor 1340 and further processed by a transmitter 1338 to generate a downlink signal data which may be transmitted to the terminal 110 and other terminals. The memory 1342 may store program codes and data for base station / RAN 120. Module 1344 data (Comm) can support the transfer of data from MSC / VLR 130 and other network entities.

The MSC / VLR 130, a controller / processor 1350 may perform various functions to support data services for terminals. The memory 1352 may store program codes and data to MSC / VLR 130. The module 1354 can support data communication with a base station / RAN 120 and other network entities. Controller / processor 1350 and / or other modules in the MSC / VLR 130 may directly execute the whole or a part of the processing 700 in Fig. 7, process 1200 in FIG. 12, and / or other processing to the techniques described herein.

Those skilled in the art will understand that information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips for which reference may be made in the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

Those skilled in the art will also appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in the disclosure herein may be implemented as electronic hardware, computer software, or combinations of these approaches. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether these functions are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Those skilled in the art may implement the described functionality in varying ways for each particular application, but such solutions in embodiment should not be interpreted as causing a departure from the scope of the present disclosure.

The techniques described herein may be implemented by various means, depending on application. For example, these techniques may be implemented in hardware, firmware, software, or any combination thereof. For an embodiment in the form of hardware, the processing units may be implemented within one or more application specific integrated circuits (ASIC, SIMS), digital signal processors (DSP, DSP), digital signal processing devices (DSPD, DSPDs), programmable logic devices (PLD , PLDs), field programmable gate arrays (FPGA, FPGAs), processors, controllers, microcontrollers, microprocessors, electronic devices, other electronic units designed to perform the functions described herein, or combinations thereof.

For the embodiment of the firmware and / or software, the techniques may be implemented with modules (e.g., procedures, functions, and so on) that perform the functions described herein. Any device-readable media, physically embodying instructions may be used in implementing the techniques described herein. For example, software codes may be stored in a memory and can execute processing module. The memory unit may be implemented within the processing unit or as an external device to the processing unit. As used herein, the term "memory" refers to any type of long term, short term, volatile, nonvolatile, or other memory and is not limited to any particular type of memory or number of storage devices, or type of media, using embodying memory.

If the functions are embodied as firmware and / or software, they may be stored as one or more instructions or code on a computer readable medium. Examples include computer-readable media encoded data structure and computer-readable media encoded with a computer program. Computer readable media includes physical computer storage. Media-storage media may be any available media which can be accessed from a computer. By way of example, and not limitation, such computer-readable media can comprise RAM, ROM, EEPROM (EEPROM, Electrically Erasable Programmable Read Only Memory), CD-ROM or other optical disk storage, magnetic disk storage or other magnetic device accumulator, or any other medium which can be used to store desired program code in the form of instructions or data structures and which can be accessed from a computer; terms disk and disc, as used herein, includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray, where the disks (disk) usually reproduce data magnetically , while discs (disc) discs reproduce data optically with lasers. The combinations described above should also be included within the scope of computer readable media.

In addition to storing on a computer readable medium, instructions and / or data may be provided as signals transmitted to the transmission media included in the data transmission device. For example, the data transmission apparatus may include a transceiver that works with signals that indicate instructions and data. The instructions and data are configured to ensure that the one or more processors functions presented in the claims. Thus, the data transmission apparatus includes transmission media with signals indicating information to perform disclosed functions. The first time the transmission media included in the communication device may include a first portion of information for performing the disclosed functions, while the second time transmission media included in the communication device may include a second piece of information to perform the disclosed functions.

Technology determining the position / location may be implemented in conjunction with various networks of wireless data transmission, such as a wireless wide area network (WWAN, WWAN), a wireless local area network (WLAN, WLAN), wireless personal area network (WPAN, BPVS) and so on . The term "network" and "system" are often used interchangeably. A WWAN may be a network with multiple access, code-division multiplexing (CDMA), a network with multiple access, time division multiplexing (TDMA), a network with multiple access, frequency division multiplexing (FDMA), a network with multiple access orthogonal frequency division multiplexing ( OFDMA), multiple-access network with single carrier FDMA (SC-FDMA), a network of long term evolution (LTE), and so forth. A CDMA network may implement one or more radio access technologies (RAT), such as cdma2000, wideband-CDMA (W-CDMA) and so on. Cdma2000 includes standards TS-95, IS-2000, and TS-856. A TDMA network may implement Global System for Mobile Communications (GSM), Digital Advanced Mobile Telephone System (D-AMPS, D-USMTS) or some other RAT. GSM and W-CDMA are described in documents from a consortium named "3rd Generation Partnership Project" (3GPP). Cdma2000 is described in documents from a consortium named "3rd Generation Partnership Project 2" (3GPP2). 3GPP and 3GPP2 documents are publicly available. A WLAN may be an IEEE 802.11x network, and a WPAN may be a network of Bluetooth, IEEE 802.15x, or some other type of network. Technology may also be implemented in conjunction with any combination of access networks WW, WLAN and / or WPAN.

The foregoing description of the disclosure is provided to ensure that for any person skilled in the art to use this disclosure. Various modifications to the disclosure will be apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the scope of the disclosure. Thus, the disclosure is not intended to be limited to the examples and described herein constructive approach, but is to be accorded the widest scope disclosed herein corresponds principles and novel features.