WO2001080587A1 - System and method for emergency call handling in a mobile packet switched network - Google Patents

System and method for emergency call handling in a mobile packet switched network Download PDF

Info

Publication number
WO2001080587A1
WO2001080587A1 PCT/EP2001/004181 EP0104181W WO0180587A1 WO 2001080587 A1 WO2001080587 A1 WO 2001080587A1 EP 0104181 W EP0104181 W EP 0104181W WO 0180587 A1 WO0180587 A1 WO 0180587A1
Authority
WO
WIPO (PCT)
Prior art keywords
emergency call
call
indication
emergency
node
Prior art date
Application number
PCT/EP2001/004181
Other languages
French (fr)
Inventor
Hans Åke LINDGREN
Mats Ola Stille
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Priority to AU54806/01A priority Critical patent/AU5480601A/en
Publication of WO2001080587A1 publication Critical patent/WO2001080587A1/en

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M7/00Arrangements for interconnection between switching centres
    • H04M7/12Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal
    • H04M7/1205Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal where the types of switching equipement comprises PSTN/ISDN equipment and switching equipment of networks other than PSTN/ISDN, e.g. Internet Protocol networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/90Services for handling of emergency or hazardous situations, e.g. earthquake and tsunami warning systems [ETWS]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/50Connection management for emergency connections
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M2242/00Special services or facilities
    • H04M2242/04Special services or facilities for emergency applications

Definitions

  • This invention relates to a telecommunications system, and to a method of operation thereof. More particularly, the invention relates to a telecommunications network using Internet Protocol (IP) , and specifically to a system for handling emergency calls m such a network.
  • IP Internet Protocol
  • BACKGROUND OF THE INVENTION In mobile communication systems, there are situations m which a call request may not be allowed. For example the user may not have paid a bill, or the mobile system may have no information at all about the user, or there may be congestion on the network, or the mobile phone may be reported stolen.
  • emergency calls may be allowed even when one of these factors apply.
  • IP Internet Protocol
  • PSTN public switched telephone network
  • all calls will send the voice signals as packet data, rather than as circuit switched data.
  • GSM on the Net by Granberg, Ericsson Review No. 4, 1998 pages 184-191, describes a voice over IP system, based on the recommendation ITU H.323.
  • the H.323 protocol separates call control (signalling m the call setup phase) from connection control (the actual data flows) .
  • the present invention is concerned with allowing special treatment of emergency calls, so that such a call can be successful even though another voice call would not be allowed.
  • a mobile communication device analyses a dialled number and, m the case of an emergency call, sends a session activation request which includes an emergency call indication.
  • a node in a packet data communication network detects an emergency call indication in a session activation request, and allows call setup, even though a call without such an indication would fail .
  • Figure 1 is a diagram illustrating message flows during call setup in accordance with the invention.
  • Figure 2 is a flow chart showing a method carried out in a mobile phone in accordance with the invention.
  • Figure 3 is a schematic representation of a mobile phone m accordance with the invention.
  • Figure 4 is a diagram illustrating message flows during call setup m accordance with a second embodiment of the invention.
  • FIG. 1 shows the network components required to connect a 3 rd generation mobile phone to an emergency services operator.
  • a radio network controller controls the air interface with a mobile station 10, and operates m the Universal Mobile Telephony System (UMTS) or using Wideband Code Division Multiple Access (WCDMA) .
  • the network operates using the General Packet Radio System (GPRS) , and includes a Serving GPRS Service Node (SGSN) and a Gateway GPRS Service Node (GGSN) .
  • GPRS General Packet Radio System
  • SGSN Serving GPRS Service Node
  • GGSN Gateway GPRS Service Node
  • the GGSN is connected to a call server in the IP multimedia domain, and this is further connected to a gateway, which is connected to the public telephone network, operating for example as a Public Switched Telephone Network (PSTN) or Integrated Services Digital Network (ISDN) system.
  • PSTN Public Switched Telephone Network
  • ISDN Integrated Services Digital Network
  • the emergency services operator is connected to the public telephone network.
  • the call setup procedure is also shown m Figure 1, while Figure 2 shows the procedure m the phone, and Figure 3 is a representation of a phone 10.
  • the procedure is described further with reference to the Session Initiation Protocol (SIP) , described in IETF document IETF/RFC 2543. This protocol is part of the IETF multimedia data and control architecture, and can be used to set up calls between parties.
  • SIP Session Initiation Protocol
  • a user enters a dialled number, for example via a keypad 12, which is sent to a controller 14, which then forms a message to be sent via transceiver circuitry 16 through an antenna 18.
  • the dialled number is received (step 20 m Figure 2) , and the controller recognises from the dialled digits (for example, the numbers 112, 911 or 999), that the call is an emergency call .
  • the session activation request which is then sent (step 24, and also see Figure 1) is then handled accordingly.
  • the mobile phone has to activate a packet (IP) data communication session with the mobile GPRS system over the air interface.
  • IP packet
  • a first PDP activation (Activate PDP Context Request, according to the GSM recommendation 24.008) is sent from the mobile station to the SGSN to get a signalling radio bearer.
  • the mobile station sends a second PDP activation to the SGSN, stipulating the need for a voice communication, allowing the user to speak to an operator at an emergency centre .
  • the second PDP activation includes the requested bandwidth, delay and other quality of service parameters. These two radio bearers remain in parallel until the call is dropped.
  • the two activation messages each include an indication that this is an emergency call
  • the emergency indicator could for example be set by setting the Access Point Name (APN) to "EMERGENCY", Or something similar.
  • the first session activation request is received by the 3G GPRS SGSN element.
  • the SGSN recognises the received emergency call indication, and the SGSN will then not stop the call setup process, even if it would normally fail, for example because it cannot obtain user profile data or if unsuccessful authentication occurs.
  • the SGSN will send a Create PDP context request to the GGSN of the same network as the SGSN, to create a packet session with it.
  • the context request will contain the special indication about an emergency call, received from the mobile phone as described above.
  • the GGSN Since the GGSN has received the emergency call indication from the SGSN, the GGSN will determine the identity of the locally geographical VoIP call server that should receive forthcoming call control signals from the mobile phone. This can be done by software in the GGSN. This has the advantage that the call is routed out from the mobile system and to the public network emergency centre as fast as possible. This avoids the possibility that the call could be routed to the call server belonging to the home network of the user. If the user is roaming, this could conceivably be m another country.
  • This call server identity is thereafter returned by the GGSN to the SGSN m the acknowledgement message which relates to the first activation message.
  • the call server identity can be an IP address in conventional format.
  • the SGSN then returns the call server identity back to the mobile phone, for example m the acknowledgement signal to the first Activate PDP context request message.
  • the mobile phone can start the voice over IP (VoIP) related call control signalling over the session.
  • VoIP voice over IP
  • This call control signalling is as described in the IETF Session Initiation Protocol (SIP) .
  • the first signal that is, the INVITE signal m SIP, will include the VoIP call server identity determined by the GGSN and received from the SGSN.
  • the mobile terminal receives the call server identity in the format of an IP address, the mobile terminal should set this address in the IP packet header "destination address" field at all times when sending SIP messages, including the INVITE message. In this way, network routers will route IP packets that are carrying such SIP messages, directed to the call server, correctly to the call server.
  • the call server can also typically be the same as handling all the normal VoIP calls as well.
  • the initial message for example the SIP INVITE message, includes an emergency indication as well, either the number dialled by the user e.g. 112 m a 3G UMTS European system or 911 m a 3G UMTS North America system, or a separate emergency indication.
  • a new message could be defined, for example a SIP EMERGENCY INVITE message. Including the emergency indication avoids the possibility that the call server could treat the call as a normal voice call, with the possibility that it could stop the call process m the event of a failure to continue.
  • the call server then places an ISUP call to the appropriate PSTN signalling/media gateway for the emergency services operator using ISUP/IP, which routes the call using ISUP/SS7 to the operator. Then, as is conventional, a ringing response is sent using ISUP to the gateway, and using SIP to the call server and then to the mobile station. The response includes the address of the gateway.
  • the mobile terminal sends a second Activate PDP Context request message, including an emergency indication, to the SGSN, which sets up a radio access bearer with the mobile terminal, and also sends a Create PDP Context request to the GGSN.
  • the GGSN responds to this message, and the SGSN sends an Activate PDO Context accepr message to the mobile terminal, after which a speech path is established between the mobile terminal and the emergency services operator.
  • Figure 4 illustrates a second call setup process according to the invention.
  • Figure 4 also shows the network components required to connect a 3 rd generation mobile phone to an emergency services operator, namely a radio network controller (RNC) controlling the air interface with a mobile station 10.
  • the network operates using the GPRS system, and includes a SGSN and a GGSN.
  • the GGSN is connected to a call server in the IP multimedia domain, and this is further connected to a gateway, which is connected to the public telephone network, operating for example as a PSTN or ISDN system.
  • the emergency services operator is connected to the public telephone network.
  • FIG. 4 shows the set up of an emergency call from a mobile station, when the mobile station does not contain a Subscriber Identity Module (SIM) card. In that case, it is conventionally not possible to initiate a call.
  • SIM Subscriber Identity Module
  • the mobile phone has to activate a packet (IP) data communication session with the mobile GPRS system over the air interface.
  • IP packet
  • the mobile station sends an attach request via the RNC to the SGSN.
  • the attach request the International Mobile Station Equipment Identity (IMEI) is transmitted as the mobile identity, and there is no Routing Area Indentification (RAI) or Ciphering Key Sequence Number (CKSN) .
  • RAI Routing Area Indentification
  • CKSN Ciphering Key Sequence Number
  • An alternative is that the attach request should be allowed to be sent without any mobile identity.
  • the only service allowed after formation of a limited attach is an emergency call. Therefore, the receipt by the SGSN of an attach request with the IMEI as the only identifier is a preliminary indication that an emergency call is required.
  • the formation of a limited attach is allowed m some situations where a normal attach would not be allowed, including in this case where no SIM is available. A normal attach should be used if possible.
  • the SGSN accepts the formation of the limited attach, and returns an attach accept message to the mobile station, with a Temporary Mobile Station Identifier (P-TMSI), and a Random Access Identifier (RAI) .
  • P-TMSI Temporary Mobile Station Identifier
  • RAI Random Access Identifier
  • the SGSN does not need to contact the Home Location Register (HLR) of the mobile station subscriber. Moreover, the SGSN does not perform any authentication or ciphering.
  • HLR Home Location Register
  • a request is sent from the mobile station to the SGSN to get a signalling radio bearer.
  • the mobile station sends a second PDP activation request to the SGSN, stipulating the need for a voice communication, allowing the user to speak to an operator at an emergency centre .
  • the second PDP activation includes the requested bandwidth, delay and other quality of service parameters.
  • the two activation messages each include an indication that this is an emergency call.
  • the emergency indicator could for example be set by setting the Access Point Name (APN) to "EMERGENCY" , Or something similar.
  • the first session activation request is received by the 3G GPRS SGSN element.
  • the SGSN recognises the received emergency call indication, and the SGSN will then not stop the call setup process, even if it would normally fail, for example because it cannot obtain user profile data or if unsuccessful authentication occurs.
  • the SGSN will send a Create PDP context request to the GGSN of the same network as the SGSN, to create a packet session with it.
  • the context request will contain the special indication about an emergency call, received from the mobile phone as described above.
  • the GGSN Since the GGSN has received the emergency call indication from the SGSN, the GGSN will determine the identity of the locally geographical VoIP call server that should receive forthcoming call control signals from the mobile phone. This can be done by software m the GGSN. This has the advantage that the call is routed out from the mobile system and to the public network emergency centre as fast as possible. This avoids the possibility that the call could be routed to the call server belonging to the home network of the user. If the user is roaming, this could conceivably be in another country.
  • This call server identity is thereafter returned by the GGSN to the SGSN in the acknowledgement message which relates to the first activation message.
  • the call server identity can be an IP address m conventional format.
  • the SGSN then returns the call server identity back to the mobile phone, for example m the acknowledgement signal to the first Activate PDP context request message .
  • the mobile phone can start the voice over IP (VoIP) related call control signalling over the session.
  • this call control signalling is as described m the IETF Session Initiation Protocol (SIP) .
  • the first signal that is, the INVITE signal m SIP, will include the VoIP call server identity determined by the GGSN and received from the SGSN.
  • the mobile terminal receives the call server identity m the format of an IP address, the mobile terminal should set this address in the IP packet header "destination address" field at all times when sending SIP messages, including the INVITE message. In this way, network routers will route IP packets that are carrying such SIP messages, directed to the call server, correctly to the call server.
  • the call server can also typically be the same as handling all the normal VoIP calls as well.
  • the initial message for example the SIP INVITE message, includes an emergency indication as well, either the number dialled by the user e.g. 112 in a 3G UMTS European system or 911 m a 3G UMTS North America system, or a separate emergency indication.
  • a new message could be defined, for example a SIP EMERGENCY INVITE message. Including the emergency indication avoids the possibility that the call server could treat the call as a normal voice call, with the possibility that it could stop the call process in the event of a failure to continue.
  • the call server then places an ISUP call to the appropriate PSTN signalling/media gateway for the emergency services operator using ISUP/IP, which routes the call using ISUP/SS7 to the operator. Then, as is conventional, a ringing response is sent using ISUP to the gateway, and using SIP to the call server and then to the mobile station. The response includes the address of the gateway.
  • the mobile terminal sends a second Activate PDP Context request message, including an emergency indication, to the SGSN, which sets up a radio access bearer with the mobile terminal, and also sends a Create PDP Context request to the GGSN.
  • the GGSN responds to this message, and the SGSN sends an Activate PDO Context accepr message to the mobile terminal, after which a speech path is established between the mobile terminal and the emergency services operator.

Abstract

There is described a system which, in a voice over IP radiotelecommunications system, allows a mobile station to make an emergency call, even though other calls would not be allowed at that time. The mobile station includes an emergency call indication in the session activation request, and this is recognised by the network nodes, which then allow call set up.

Description

SYSTEM AND METHOD FOR EMERGENCY CALL HANDLING IN A MOBILE PACKET SWITCHED NETWORK
TECHNICAL FIELD OF THE INVENTION
This invention relates to a telecommunications system, and to a method of operation thereof. More particularly, the invention relates to a telecommunications network using Internet Protocol (IP) , and specifically to a system for handling emergency calls m such a network. BACKGROUND OF THE INVENTION In mobile communication systems, there are situations m which a call request may not be allowed. For example the user may not have paid a bill, or the mobile system may have no information at all about the user, or there may be congestion on the network, or the mobile phone may be reported stolen.
In the GSM system, emergency calls may be allowed even when one of these factors apply.
It is expected that 3rd generation (3G) mobile phones will allow voice over IP. That is, the Internet Protocol (IP) will be used for the whole call from the mobile phone to the network gateway which is the connection to the public switched telephone network (PSTN) which includes the emergency services operator. Therefore, all calls will send the voice signals as packet data, rather than as circuit switched data. The document "GSM on the Net", by Granberg, Ericsson Review No. 4, 1998 pages 184-191, describes a voice over IP system, based on the recommendation ITU H.323. The H.323 protocol separates call control (signalling m the call setup phase) from connection control (the actual data flows) .
However, it provides no mechanism to allow for special treatment of emergency calls. SUMMARY OF THE INVENTION The present invention is concerned with allowing special treatment of emergency calls, so that such a call can be successful even though another voice call would not be allowed.
According to one aspect of the invention, a mobile communication device analyses a dialled number and, m the case of an emergency call, sends a session activation request which includes an emergency call indication.
According to another aspect of the invention, a node in a packet data communication network detects an emergency call indication in a session activation request, and allows call setup, even though a call without such an indication would fail .
According to another aspect of the invention, BRIEF DESCRIPTION OF DRAWINGS
Figure 1 is a diagram illustrating message flows during call setup in accordance with the invention.
Figure 2 is a flow chart showing a method carried out in a mobile phone in accordance with the invention. Figure 3 is a schematic representation of a mobile phone m accordance with the invention.
Figure 4 is a diagram illustrating message flows during call setup m accordance with a second embodiment of the invention. DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS
In accordance with the invention, when a mobile phone wishes to place an emergency call, it sets a special emergency call indication when requesting mobile system and radio resources. Figure 1 shows the network components required to connect a 3rd generation mobile phone to an emergency services operator. A radio network controller (RNC) controls the air interface with a mobile station 10, and operates m the Universal Mobile Telephony System (UMTS) or using Wideband Code Division Multiple Access (WCDMA) . The network operates using the General Packet Radio System (GPRS) , and includes a Serving GPRS Service Node (SGSN) and a Gateway GPRS Service Node (GGSN) . The GGSN is connected to a call server in the IP multimedia domain, and this is further connected to a gateway, which is connected to the public telephone network, operating for example as a Public Switched Telephone Network (PSTN) or Integrated Services Digital Network (ISDN) system. The emergency services operator is connected to the public telephone network.
The call setup procedure is also shown m Figure 1, while Figure 2 shows the procedure m the phone, and Figure 3 is a representation of a phone 10. The procedure is described further with reference to the Session Initiation Protocol (SIP) , described in IETF document IETF/RFC 2543. This protocol is part of the IETF multimedia data and control architecture, and can be used to set up calls between parties.
As shown in Figure 1, a user enters a dialled number, for example via a keypad 12, which is sent to a controller 14, which then forms a message to be sent via transceiver circuitry 16 through an antenna 18.
In the controller 14, the dialled number is received (step 20 m Figure 2) , and the controller recognises from the dialled digits (for example, the numbers 112, 911 or 999), that the call is an emergency call . The session activation request which is then sent (step 24, and also see Figure 1) is then handled accordingly. The mobile phone has to activate a packet (IP) data communication session with the mobile GPRS system over the air interface. A first PDP activation (Activate PDP Context Request, according to the GSM recommendation 24.008) is sent from the mobile station to the SGSN to get a signalling radio bearer. When this has been obtained, the mobile station sends a second PDP activation to the SGSN, stipulating the need for a voice communication, allowing the user to speak to an operator at an emergency centre . The second PDP activation includes the requested bandwidth, delay and other quality of service parameters. These two radio bearers remain in parallel until the call is dropped.
In the illustrated embodiment of the invention, the two activation messages each include an indication that this is an emergency call In the context of the GSM recommendation 24.008, the emergency indicator could for example be set by setting the Access Point Name (APN) to "EMERGENCY", Or something similar.
Thus, m more detail, the first session activation request is received by the 3G GPRS SGSN element. The
SGSN recognises the received emergency call indication, and the SGSN will then not stop the call setup process, even if it would normally fail, for example because it cannot obtain user profile data or if unsuccessful authentication occurs.
The SGSN will send a Create PDP context request to the GGSN of the same network as the SGSN, to create a packet session with it. The context request will contain the special indication about an emergency call, received from the mobile phone as described above.
This opens a communication path between the SGSN and the GGSN for this particular emergency call .
Since the GGSN has received the emergency call indication from the SGSN, the GGSN will determine the identity of the locally geographical VoIP call server that should receive forthcoming call control signals from the mobile phone. This can be done by software in the GGSN. This has the advantage that the call is routed out from the mobile system and to the public network emergency centre as fast as possible. This avoids the possibility that the call could be routed to the call server belonging to the home network of the user. If the user is roaming, this could conceivably be m another country. This call server identity is thereafter returned by the GGSN to the SGSN m the acknowledgement message which relates to the first activation message. The call server identity can be an IP address in conventional format. The SGSN then returns the call server identity back to the mobile phone, for example m the acknowledgement signal to the first Activate PDP context request message.
When the mobile phone gets a successful session activation acknowledgement from the mobile system, the mobile phone can start the voice over IP (VoIP) related call control signalling over the session. In this described embodiment, this call control signalling is as described in the IETF Session Initiation Protocol (SIP) . The first signal, that is, the INVITE signal m SIP, will include the VoIP call server identity determined by the GGSN and received from the SGSN. When the mobile terminal receives the call server identity in the format of an IP address, the mobile terminal should set this address in the IP packet header "destination address" field at all times when sending SIP messages, including the INVITE message. In this way, network routers will route IP packets that are carrying such SIP messages, directed to the call server, correctly to the call server.
The call server can also typically be the same as handling all the normal VoIP calls as well. The initial message, for example the SIP INVITE message, includes an emergency indication as well, either the number dialled by the user e.g. 112 m a 3G UMTS European system or 911 m a 3G UMTS North America system, or a separate emergency indication. Alternatively, a new message could be defined, for example a SIP EMERGENCY INVITE message. Including the emergency indication avoids the possibility that the call server could treat the call as a normal voice call, with the possibility that it could stop the call process m the event of a failure to continue.
The call server then places an ISUP call to the appropriate PSTN signalling/media gateway for the emergency services operator using ISUP/IP, which routes the call using ISUP/SS7 to the operator. Then, as is conventional, a ringing response is sent using ISUP to the gateway, and using SIP to the call server and then to the mobile station. The response includes the address of the gateway.
This can then be used by the mobile station to create the required voice bearers to carry speech to the emergency services operator with the desired parameters, using the gateway address so that speech packets can reach the gateway. Thus, the mobile terminal sends a second Activate PDP Context request message, including an emergency indication, to the SGSN, which sets up a radio access bearer with the mobile terminal, and also sends a Create PDP Context request to the GGSN.
The GGSN responds to this message, and the SGSN sends an Activate PDO Context accepr message to the mobile terminal, after which a speech path is established between the mobile terminal and the emergency services operator.
Figure 4 illustrates a second call setup process according to the invention.
In the same way as Figure 1, Figure 4 also shows the network components required to connect a 3rd generation mobile phone to an emergency services operator, namely a radio network controller (RNC) controlling the air interface with a mobile station 10. The network operates using the GPRS system, and includes a SGSN and a GGSN. The GGSN is connected to a call server in the IP multimedia domain, and this is further connected to a gateway, which is connected to the public telephone network, operating for example as a PSTN or ISDN system. The emergency services operator is connected to the public telephone network.
Figure 4 shows the set up of an emergency call from a mobile station, when the mobile station does not contain a Subscriber Identity Module (SIM) card. In that case, it is conventionally not possible to initiate a call.
As in the procedure described with reference to Figure 1, the mobile phone has to activate a packet (IP) data communication session with the mobile GPRS system over the air interface. In this case, when the mobile phone is without a SIM, it is permitted to form a limited attach. Thus, the mobile station sends an attach request via the RNC to the SGSN. In the attach request, the International Mobile Station Equipment Identity (IMEI) is transmitted as the mobile identity, and there is no Routing Area Indentification (RAI) or Ciphering Key Sequence Number (CKSN) . An alternative is that the attach request should be allowed to be sent without any mobile identity.
In this embodiment of the invention, the only service allowed after formation of a limited attach is an emergency call. Therefore, the receipt by the SGSN of an attach request with the IMEI as the only identifier is a preliminary indication that an emergency call is required. The formation of a limited attach is allowed m some situations where a normal attach would not be allowed, including in this case where no SIM is available. A normal attach should be used if possible. In the procedure illustrated in Figure 4, the SGSN accepts the formation of the limited attach, and returns an attach accept message to the mobile station, with a Temporary Mobile Station Identifier (P-TMSI), and a Random Access Identifier (RAI) .
The SGSN does not need to contact the Home Location Register (HLR) of the mobile station subscriber. Moreover, the SGSN does not perform any authentication or ciphering.
Thereafter, a request is sent from the mobile station to the SGSN to get a signalling radio bearer. When this has been obtained, the mobile station sends a second PDP activation request to the SGSN, stipulating the need for a voice communication, allowing the user to speak to an operator at an emergency centre . The second PDP activation includes the requested bandwidth, delay and other quality of service parameters. These two radio bearers remain m parallel until the call is dropped.
Preferably, the two activation messages each include an indication that this is an emergency call. In the context of the GSM recommendation 24.008, the emergency indicator could for example be set by setting the Access Point Name (APN) to "EMERGENCY" , Or something similar.
Thus, in more detail, the first session activation request is received by the 3G GPRS SGSN element. The
SGSN recognises the received emergency call indication, and the SGSN will then not stop the call setup process, even if it would normally fail, for example because it cannot obtain user profile data or if unsuccessful authentication occurs. The SGSN will send a Create PDP context request to the GGSN of the same network as the SGSN, to create a packet session with it. The context request will contain the special indication about an emergency call, received from the mobile phone as described above.
This opens a communication path between the SGSN and the GGSN for this particular emergency call .
Since the GGSN has received the emergency call indication from the SGSN, the GGSN will determine the identity of the locally geographical VoIP call server that should receive forthcoming call control signals from the mobile phone. This can be done by software m the GGSN. This has the advantage that the call is routed out from the mobile system and to the public network emergency centre as fast as possible. This avoids the possibility that the call could be routed to the call server belonging to the home network of the user. If the user is roaming, this could conceivably be in another country. This call server identity is thereafter returned by the GGSN to the SGSN in the acknowledgement message which relates to the first activation message. The call server identity can be an IP address m conventional format. The SGSN then returns the call server identity back to the mobile phone, for example m the acknowledgement signal to the first Activate PDP context request message .
When the mobile phone gets a successful session activation acknowledgement from the mobile system, the mobile phone can start the voice over IP (VoIP) related call control signalling over the session. In this described embodiment, this call control signalling is as described m the IETF Session Initiation Protocol (SIP) . The first signal, that is, the INVITE signal m SIP, will include the VoIP call server identity determined by the GGSN and received from the SGSN. When the mobile terminal receives the call server identity m the format of an IP address, the mobile terminal should set this address in the IP packet header "destination address" field at all times when sending SIP messages, including the INVITE message. In this way, network routers will route IP packets that are carrying such SIP messages, directed to the call server, correctly to the call server.
The call server can also typically be the same as handling all the normal VoIP calls as well. The initial message, for example the SIP INVITE message, includes an emergency indication as well, either the number dialled by the user e.g. 112 in a 3G UMTS European system or 911 m a 3G UMTS North America system, or a separate emergency indication. Alternatively, a new message could be defined, for example a SIP EMERGENCY INVITE message. Including the emergency indication avoids the possibility that the call server could treat the call as a normal voice call, with the possibility that it could stop the call process in the event of a failure to continue.
The call server then places an ISUP call to the appropriate PSTN signalling/media gateway for the emergency services operator using ISUP/IP, which routes the call using ISUP/SS7 to the operator. Then, as is conventional, a ringing response is sent using ISUP to the gateway, and using SIP to the call server and then to the mobile station. The response includes the address of the gateway.
This can then be used by the mobile station to create the required voice bearers to carry speech to the emergency services operator with the desired parameters, using the gateway address so that speech packets can reach the gateway. Thus, the mobile terminal sends a second Activate PDP Context request message, including an emergency indication, to the SGSN, which sets up a radio access bearer with the mobile terminal, and also sends a Create PDP Context request to the GGSN.
The GGSN responds to this message, and the SGSN sends an Activate PDO Context accepr message to the mobile terminal, after which a speech path is established between the mobile terminal and the emergency services operator.
It should be noted that, although the invention has been described with particular reference to a GPRS based mobile telephone system using the IETF SIP, it is applicable to any mobile communication system, which offers real-time packet (IP) data communication, with any type of call control protocol, including for example ITU-T H.323.
There is thus described a method which allows an emergency call to be placed even when other calls would not be allowed.

Claims

1. A mobile communications device, capable of operating in a packet data communications network, the device comprising: means for analysing a dialled number, the device being adapted, in the event that a dialled number is indicative of an emergency call, to send a session activation request which includes an emergency call indication.
2. A mobile communications device as claimed in claim 1, the device being adapted to send the session activation request, in the event that a dialled number is indicative of an emergency call, even if the device has no SIM.
3. A method of handling an emergency call in a mobile device capable of operating in a packet data communication network, the method comprising: analysing a dialled number; and if the dialled number is indicative of an emergency call, sending a session activation request which includes an emergency call indication.
4. A method as claimed m claim 3, comprising sending the session activation request if the dialled number is indicative of an emergency call, even if the mobile device has no SIM.
5. A network node for use in a pocket data communications network, the node comprising means for detecting an emergency call indication m a received session activation request, and being adapted, in the event that an emergency call indication is detected, to set up a call even if normal call setup criteria are not met .
6. A node as claimed in claim 5, wherein the mode is a SGSN element.
7. A node as claimed m claim 6, wherein the node is adapted, in the event that an emergency call indication is detected, to set up a call even if the received session activation request includes no mobile station identifier.
8. A node as claimed in claim 6, adapted, in the event that an emergency call indication is detected, to create a packet session with a GGSN, including a further emergency call indication.
9. A node as claimed m claim 5, wherein the mode is a GGSN element.
10. A node as claimed m claim 7, adapted, in the event that an emergency call is detected, to return a message indicating a call server local to a calling device .
11. A method of operation of a node in a packet data communications network, the method comprising: detecting an emergency call indication in a received session activation request, and if an emergency call indication is detected, setting up a call even if normal call setup criteria are not met .
12. A method as claimed m claim 11, wherein the mode is a SGSN element, and the method further comprises : if an emergency call indication is detected, creating a packet session with a GGSN, including a further emergency call indication.
13. A method as claimed m claim 11, wherein the mode is a SGSN element, and the method further comprises, m the event that an emergency call indication is detected, setting up a call even if the received session activation request includes no mobile station identifier.
14. A method as claimed m claim 11, wherein the mode is a GGSN element, and the method further comprises : if an emergency call indication is detected, returning a message indicating a call server local to a calling device.
PCT/EP2001/004181 2000-04-15 2001-04-11 System and method for emergency call handling in a mobile packet switched network WO2001080587A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU54806/01A AU5480601A (en) 2000-04-15 2001-04-11 System and method for emergency call handling in a mobile packet switched network

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
GB0009290A GB2361389B (en) 2000-04-15 2000-04-15 Telecommunications system
GB0009290.8 2000-04-15

Publications (1)

Publication Number Publication Date
WO2001080587A1 true WO2001080587A1 (en) 2001-10-25

Family

ID=9889959

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2001/004181 WO2001080587A1 (en) 2000-04-15 2001-04-11 System and method for emergency call handling in a mobile packet switched network

Country Status (4)

Country Link
US (1) US6775534B2 (en)
AU (1) AU5480601A (en)
GB (1) GB2361389B (en)
WO (1) WO2001080587A1 (en)

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2002091687A1 (en) * 2001-05-04 2002-11-14 Ericsson Inc. Emergency packet data service
WO2003063536A1 (en) * 2002-01-25 2003-07-31 Nokia Corporation Emergency session request handling in a network
WO2008074669A1 (en) * 2006-12-21 2008-06-26 Nokia Corporation Emergency service in a communication system
WO2009082936A1 (en) * 2007-12-18 2009-07-09 Huawei Technologies Co., Ltd. A method and an apparatus for emergency call
US9137385B2 (en) 2006-11-02 2015-09-15 Digifonica (International) Limited Determining a time to permit a communications session to be conducted
US9143608B2 (en) 2006-11-29 2015-09-22 Digifonica (International) Limited Intercepting voice over IP communications and other data communications
US9154417B2 (en) 2009-09-17 2015-10-06 Digifonica (International) Limited Uninterrupted transmission of internet protocol transmissions during endpoint changes
US9565307B2 (en) 2007-03-26 2017-02-07 Voip-Pal.Com, Inc. Emergency assistance calling for voice over IP communications systems
US10880721B2 (en) 2008-07-28 2020-12-29 Voip-Pal.Com, Inc. Mobile gateway

Families Citing this family (100)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
AU2001258380C1 (en) * 2001-04-27 2008-05-01 Nokia Technologies Oy Method and system for handling a network-identified emergency session
WO2002089515A1 (en) * 2001-04-27 2002-11-07 Nokia Corporation Method and system for enabling emergency sessions to be established in abnormal cases
JP4173293B2 (en) * 2001-08-28 2008-10-29 株式会社エヌ・ティ・ティ・ドコモ Mobile communication system, base station, radio network controller, mobile station, and mobile station power consumption reduction method
US8290505B2 (en) 2006-08-29 2012-10-16 Telecommunications Systems, Inc. Consequential location derived information
US7426380B2 (en) 2002-03-28 2008-09-16 Telecommunication Systems, Inc. Location derived presence information
US8918073B2 (en) 2002-03-28 2014-12-23 Telecommunication Systems, Inc. Wireless telecommunications location based services scheme selection
US7321773B2 (en) * 2002-03-28 2008-01-22 Telecommunication Systems, Inc. Area watcher for wireless network
US9154906B2 (en) 2002-03-28 2015-10-06 Telecommunication Systems, Inc. Area watcher for wireless network
EP1361712B1 (en) * 2002-05-07 2006-03-29 Sony Ericsson Mobile Communications AB Method for communicating messages to an electronic communication equipment
DE10223980A1 (en) * 2002-05-29 2004-01-08 Siemens Ag Process for routing communication connections
GB0216278D0 (en) * 2002-07-12 2002-08-21 Nokia Corp Communication channel selection
US20040043756A1 (en) * 2002-09-03 2004-03-04 Tao Haukka Method and system for authentication in IP multimedia core network system (IMS)
DE10250501B4 (en) * 2002-10-29 2006-09-28 T-Mobile Deutschland Gmbh A method for improving QoS mechanisms in bandwidth allocation in CDMA mobile communication systems
US20040107502A1 (en) * 2002-12-04 2004-06-10 Boone E. Vanessa Headrest
US20070238455A1 (en) 2006-04-07 2007-10-11 Yinjun Zhu Mobile based area event handling when currently visited network doe not cover area
US7164888B2 (en) * 2002-12-23 2007-01-16 Qwest Communications International Inc. Systems and methods for analyzing critical circuits and associated telecommunication resources
US8488462B2 (en) * 2002-12-31 2013-07-16 Nokia Corporation Handling traffic flows in a mobile communications network
US20040203572A1 (en) * 2002-12-31 2004-10-14 Naveen Aerrabotu Emergency call-back for mobile terminals in a limited service mode
GB2398458B (en) * 2003-02-15 2005-05-25 Ericsson Telefon Ab L M Conversational bearer negotiation
US7787855B2 (en) * 2003-03-31 2010-08-31 Motorola, Inc. Establishing emergency sessions in packet data networks for wireless devices having invalid subscriber identities
US7590122B2 (en) * 2003-05-16 2009-09-15 Nortel Networks Limited Method and apparatus for session control
US7899174B1 (en) * 2003-06-26 2011-03-01 Nortel Networks Limited Emergency services for packet networks
GB0326264D0 (en) * 2003-11-11 2003-12-17 Nokia Corp Emergency call support for mobile communications
US7260186B2 (en) 2004-03-23 2007-08-21 Telecommunication Systems, Inc. Solutions for voice over internet protocol (VoIP) 911 location services
US20080126535A1 (en) 2006-11-28 2008-05-29 Yinjun Zhu User plane location services over session initiation protocol (SIP)
US20080090546A1 (en) 2006-10-17 2008-04-17 Richard Dickinson Enhanced E911 network access for a call center using session initiation protocol (SIP) messaging
US7903791B2 (en) * 2005-06-13 2011-03-08 Telecommunication Systems, Inc. Enhanced E911 location information using voice over internet protocol (VoIP)
US7756513B2 (en) * 2004-06-30 2010-07-13 Arinc Incorporated Command and control communications system with sub-networks and interface devices
US20060018448A1 (en) * 2004-07-20 2006-01-26 Qwest Communications International Inc. Routing telephone calls via a data network
US8184793B2 (en) * 2004-07-20 2012-05-22 Qwest Communications International Inc. Multi-line telephone calling
US20060018449A1 (en) * 2004-07-20 2006-01-26 Qwest Communications International Inc. Telephone call routing
US20060018310A1 (en) * 2004-07-20 2006-01-26 Qwest Communications International Inc. Data network call routing
WO2006015474A1 (en) * 2004-08-13 2006-02-16 Research In Motion Limited Methods and apparatus for efficiently establishing and maintaining a data connection between a mobile station and a wireless network
FI20050022A0 (en) * 2005-01-10 2005-01-10 Nokia Corp Control of access to a network
JP4567752B2 (en) * 2005-01-19 2010-10-20 テレフオンアクチーボラゲット エル エム エリクソン(パブル) Method and apparatus for handling emergency calls
ES2333602T3 (en) * 2005-01-26 2010-02-24 Alcatel Lucent PROCEDURE TO ESTABLISH AN EMERGENCY CALL IN A LOCAL, TERMINAL, PASSWAY AND SERVER INFORMATIC NETWORK FOR THE PRACTICE OF THIS PROCEDURE.
US7353034B2 (en) 2005-04-04 2008-04-01 X One, Inc. Location sharing and tracking using mobile phones or other wireless devices
US8116722B2 (en) * 2005-05-26 2012-02-14 Telecommunication Systems, Inc. E911 call blocking for non-initialized wireless telephones
US8175570B2 (en) 2005-05-26 2012-05-08 Telecommunication Systems, Inc. E911 call blocking for non-initialized wireless telephones
US8103242B2 (en) * 2005-05-26 2012-01-24 Telecommunication Systems, Inc. E911 call blocking for non-initialized wireless telephones
US8660573B2 (en) 2005-07-19 2014-02-25 Telecommunications Systems, Inc. Location service requests throttling
US10178522B2 (en) * 2005-08-02 2019-01-08 Qualcomm Incorporated VoIP emergency call support
CN101248685B (en) * 2005-08-22 2011-06-08 艾利森电话股份有限公司 A method and arrangement for establishing a communication session for multimedia
US7933385B2 (en) 2005-08-26 2011-04-26 Telecommunication Systems, Inc. Emergency alert for voice over internet protocol (VoIP)
US20070123271A1 (en) * 2005-08-26 2007-05-31 Richard Dickinson Cellular phone tracking scope
US9282451B2 (en) 2005-09-26 2016-03-08 Telecommunication Systems, Inc. Automatic location identification (ALI) service requests steering, connection sharing and protocol translation
US7626951B2 (en) * 2005-10-06 2009-12-01 Telecommunication Systems, Inc. Voice Over Internet Protocol (VoIP) location based conferencing
US8467320B2 (en) 2005-10-06 2013-06-18 Telecommunication Systems, Inc. Voice over internet protocol (VoIP) multi-user conferencing
DE102005048354A1 (en) * 2005-10-10 2007-04-12 Siemens Ag Emergency call system between a telecommunication device and an emergency call center
US20070121642A1 (en) * 2005-11-02 2007-05-31 Battin Robert D Method and system for supporting an emergency call
US9258386B2 (en) * 2005-11-18 2016-02-09 Telecommunication Systems, Inc. Voice over internet protocol (VoIP) mobility detection
US7676234B2 (en) * 2005-11-23 2010-03-09 Research In Motion Limited Routing of a short message originated by a mobile device
US20070177582A1 (en) * 2006-01-31 2007-08-02 Marian Croak Method and apparatus for providing network interworking for emergency calls
US20070189467A1 (en) * 2006-01-31 2007-08-16 Marian Croak Method and apparatus for bypassing overload control for emergency calls
US8150363B2 (en) 2006-02-16 2012-04-03 Telecommunication Systems, Inc. Enhanced E911 network access for call centers
US8059789B2 (en) 2006-02-24 2011-11-15 Telecommunication Systems, Inc. Automatic location identification (ALI) emergency services pseudo key (ESPK)
US8532266B2 (en) 2006-05-04 2013-09-10 Telecommunication Systems, Inc. Efficient usage of emergency services keys
US8208605B2 (en) 2006-05-04 2012-06-26 Telecommunication Systems, Inc. Extended efficient usage of emergency services keys
US8050395B2 (en) * 2006-06-12 2011-11-01 At&T Intellectual Property I, L.P. Analog telephone adapter and emergency proxy
US20090196284A1 (en) * 2006-06-28 2009-08-06 Nokia Siemens Networks Gmbh & Co.Kg Method for Providing an Emergency Call Service for VoIP Subscribers
JP4889435B2 (en) * 2006-10-11 2012-03-07 株式会社エヌ・ティ・ティ・ドコモ Packet communication method and mobile station
US7966013B2 (en) 2006-11-03 2011-06-21 Telecommunication Systems, Inc. Roaming gateway enabling location based services (LBS) roaming for user plane in CDMA networks without requiring use of a mobile positioning center (MPC)
US8363640B2 (en) * 2007-01-31 2013-01-29 At&T Intellectual Property I, L.P. Methods and apparatus for handling a communication session for an unregistered internet protocol multimedia subsystem (IMS) device
US8050386B2 (en) 2007-02-12 2011-11-01 Telecommunication Systems, Inc. Mobile automatic location identification (ALI) for first responders
US8223630B2 (en) * 2007-04-24 2012-07-17 At&T Intellectual Property I, L.P. System for monitoring operations of an ENUM system
US8520805B2 (en) 2007-05-02 2013-08-27 Telecommunication Systems, Inc. Video E911
US8180032B2 (en) * 2007-05-11 2012-05-15 At&T Intellectual Property I, L.P. Methods and systems for protecting a telecommunication service from Denial of Service (DoS) attack
US20090077077A1 (en) 2007-09-18 2009-03-19 Gerhard Geldenbott Optimal selection of MSAG address for valid civic/postal address
US8576991B2 (en) 2008-03-19 2013-11-05 Telecommunication Systems, Inc. End-to-end logic tracing of complex call flows in a distributed call system
US9148769B2 (en) * 2008-05-07 2015-09-29 Qualcomm Incorporated System, apparatus and method to enable mobile stations to identify calls based on predetermined values set in a call header
US7903587B2 (en) * 2008-05-30 2011-03-08 Telecommunication Systems, Inc. Wireless emergency services protocols translator between ansi-41 and VoIP emergency services protocols
US8068587B2 (en) * 2008-08-22 2011-11-29 Telecommunication Systems, Inc. Nationwide table routing of voice over internet protocol (VOIP) emergency calls
CN101742454B (en) * 2008-11-26 2012-10-17 华为技术有限公司 Management method, device and system of emergency business of mobile restricted terminal
US9301191B2 (en) 2013-09-20 2016-03-29 Telecommunication Systems, Inc. Quality of service to over the top applications used with VPN
CN101909120A (en) * 2009-06-04 2010-12-08 鸿富锦精密工业(深圳)有限公司 Automatic test method of telephone function of mobile device
US8711751B2 (en) * 2009-09-25 2014-04-29 Apple Inc. Methods and apparatus for dynamic identification (ID) assignment in wireless networks
US20110188416A1 (en) * 2010-02-02 2011-08-04 Stefano Faccin System and method for packetized emergency messages
US20110188411A1 (en) * 2010-02-02 2011-08-04 Stefano Faccin System and method for packetized emergency messages
US20110189971A1 (en) * 2010-02-02 2011-08-04 Stefano Faccin System and method for packetized emergency messages
US8688087B2 (en) 2010-12-17 2014-04-01 Telecommunication Systems, Inc. N-dimensional affinity confluencer
US8942743B2 (en) 2010-12-17 2015-01-27 Telecommunication Systems, Inc. iALERT enhanced alert manager
WO2012087353A1 (en) 2010-12-22 2012-06-28 Telecommunication Systems, Inc. Area event handling when current network does not cover target area
WO2012141762A1 (en) 2011-02-25 2012-10-18 Telecommunication Systems, Inc. Mobile internet protocol (ip) location
US9479344B2 (en) 2011-09-16 2016-10-25 Telecommunication Systems, Inc. Anonymous voice conversation
US8831556B2 (en) 2011-09-30 2014-09-09 Telecommunication Systems, Inc. Unique global identifier header for minimizing prank emergency 911 calls
US9313637B2 (en) 2011-12-05 2016-04-12 Telecommunication Systems, Inc. Wireless emergency caller profile data delivery over a legacy interface
US9264537B2 (en) 2011-12-05 2016-02-16 Telecommunication Systems, Inc. Special emergency call treatment based on the caller
US8984591B2 (en) 2011-12-16 2015-03-17 Telecommunications Systems, Inc. Authentication via motion of wireless device movement
US9384339B2 (en) 2012-01-13 2016-07-05 Telecommunication Systems, Inc. Authenticating cloud computing enabling secure services
EP2807809B1 (en) * 2012-01-26 2018-12-26 Telefonaktiebolaget LM Ericsson (publ) Providing an ims voice session via a packet switch network and an emergency voice session via a circuit switch network
US9307372B2 (en) 2012-03-26 2016-04-05 Telecommunication Systems, Inc. No responders online
US9544260B2 (en) 2012-03-26 2017-01-10 Telecommunication Systems, Inc. Rapid assignment dynamic ownership queue
US9338153B2 (en) 2012-04-11 2016-05-10 Telecommunication Systems, Inc. Secure distribution of non-privileged authentication credentials
US9313638B2 (en) 2012-08-15 2016-04-12 Telecommunication Systems, Inc. Device independent caller data access for emergency calls
US9208346B2 (en) 2012-09-05 2015-12-08 Telecommunication Systems, Inc. Persona-notitia intellection codifier
US9456301B2 (en) 2012-12-11 2016-09-27 Telecommunication Systems, Inc. Efficient prisoner tracking
US8983047B2 (en) 2013-03-20 2015-03-17 Telecommunication Systems, Inc. Index of suspicion determination for communications request
US9408034B2 (en) 2013-09-09 2016-08-02 Telecommunication Systems, Inc. Extended area event for network based proximity discovery
US9516104B2 (en) 2013-09-11 2016-12-06 Telecommunication Systems, Inc. Intelligent load balancer enhanced routing
US9479897B2 (en) 2013-10-03 2016-10-25 Telecommunication Systems, Inc. SUPL-WiFi access point controller location based services for WiFi enabled mobile devices

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1109416A2 (en) * 1999-12-17 2001-06-20 Nortel Networks Limited System and method for providing packet-switched telephony in a mobile communication network

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5881131A (en) * 1993-11-16 1999-03-09 Bell Atlantic Network Services, Inc. Analysis and validation system for provisioning network related facilities
US5797091A (en) * 1995-03-07 1998-08-18 Xypoint Corporation Personal communication system and method of use
JPH1013927A (en) * 1996-06-19 1998-01-16 Fujitsu Ltd Urgent call connection processing system in mobile telephone system
US6515989B1 (en) * 1998-12-22 2003-02-04 Telefonaktiebolaget Lm Ericsson (Publ) Collecting per-packet billing data in a packet data service

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1109416A2 (en) * 1999-12-17 2001-06-20 Nortel Networks Limited System and method for providing packet-switched telephony in a mobile communication network

Non-Patent Citations (5)

* Cited by examiner, † Cited by third party
Title
KORPI M ET AL: "SUPPLEMENTARY SERVICES IN THE H.323 IP TELEPHONY NETWORK", IEEE COMMUNICATIONS MAGAZINE,US,IEEE SERVICE CENTER. PISCATAWAY, N.J, vol. 37, no. 7, July 1999 (1999-07-01), pages 118 - 125, XP000835313, ISSN: 0163-6804 *
REED J H ET AL: "AN OVERVIEW OF THE CHALLENGES AND PROGRESS IN MEETING THE E-911 REQUIREMENT FOR LOCATION SERVICE", IEEE COMMUNICATIONS MAGAZINE,US,IEEE SERVICE CENTER. PISCATAWAY, N.J, vol. 36, no. 4, 1 April 1998 (1998-04-01), pages 30 - 37, XP000752568, ISSN: 0163-6804 *
SATYABRATA CHAKRABARTI ET AL: "A NETWORK ARCHITECTURE FOR GLOBAL WIRELESS POSITION LOCATION SERVICES", VANCOUVER, CA, JUNE 6 - 10, 1999,NEW YORK, NY: IEEE,US, 6 June 1999 (1999-06-06), pages 1779 - 1783, XP000903675, ISBN: 0-7803-5285-8 *
SCHULZRINNE HENNING G ET AL: "The Session Initiation Protocol: Providing Advanced Telephony Services Across the Internet", BELL LABS TECHNICAL JOURNAL, October 1998 (1998-10-01), XP002164648 *
WANG J ET AL: "WIRELESS VOICE-OVER-IP AND IMPLICATIONS FOR THIRD-GENERATION NETWORK DESIGN", BELL LABS TECHNICAL JOURNAL,US,BELL LABORATORIES, vol. 3, no. 3, 1 July 1998 (1998-07-01), pages 79 - 97, XP000782375, ISSN: 1089-7089 *

Cited By (25)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2002091687A1 (en) * 2001-05-04 2002-11-14 Ericsson Inc. Emergency packet data service
US7860976B2 (en) 2002-01-25 2010-12-28 Nokia Corporation Emergency session request handling in a network
WO2003063536A1 (en) * 2002-01-25 2003-07-31 Nokia Corporation Emergency session request handling in a network
EP3182748A1 (en) * 2002-01-25 2017-06-21 Nokia Technologies Oy Emergency session request handling in a network
US10218606B2 (en) 2006-11-02 2019-02-26 Voip-Pal.Com, Inc. Producing routing messages for voice over IP communications
US9137385B2 (en) 2006-11-02 2015-09-15 Digifonica (International) Limited Determining a time to permit a communications session to be conducted
US9826002B2 (en) 2006-11-02 2017-11-21 Voip-Pal.Com, Inc. Producing routing messages for voice over IP communications
US9998363B2 (en) 2006-11-02 2018-06-12 Voip-Pal.Com, Inc. Allocating charges for communications services
US9179005B2 (en) 2006-11-02 2015-11-03 Digifonica (International) Limited Producing routing messages for voice over IP communications
US9537762B2 (en) 2006-11-02 2017-01-03 Voip-Pal.Com, Inc. Producing routing messages for voice over IP communications
US9948549B2 (en) 2006-11-02 2018-04-17 Voip-Pal.Com, Inc. Producing routing messages for voice over IP communications
US9935872B2 (en) 2006-11-02 2018-04-03 Voip-Pal.Com, Inc. Producing routing messages for voice over IP communications
US11171864B2 (en) 2006-11-02 2021-11-09 Voip-Pal.Com, Inc. Determining a time to permit a communications session to be conducted
US9813330B2 (en) 2006-11-02 2017-11-07 Voip-Pal.Com, Inc. Producing routing messages for voice over IP communications
US9143608B2 (en) 2006-11-29 2015-09-22 Digifonica (International) Limited Intercepting voice over IP communications and other data communications
US9549071B2 (en) 2006-11-29 2017-01-17 Voip-Pal.Com, Inc. Intercepting voice over IP communications and other data communications
US10038779B2 (en) 2006-11-29 2018-07-31 Voip-Pal.Com, Inc. Intercepting voice over IP communications and other data communications
WO2008074669A1 (en) * 2006-12-21 2008-06-26 Nokia Corporation Emergency service in a communication system
US9565307B2 (en) 2007-03-26 2017-02-07 Voip-Pal.Com, Inc. Emergency assistance calling for voice over IP communications systems
US11172064B2 (en) 2007-03-26 2021-11-09 Voip-Pal.Com, Inc. Emergency assistance calling for voice over IP communications systems
WO2009082936A1 (en) * 2007-12-18 2009-07-09 Huawei Technologies Co., Ltd. A method and an apparatus for emergency call
US10880721B2 (en) 2008-07-28 2020-12-29 Voip-Pal.Com, Inc. Mobile gateway
US9154417B2 (en) 2009-09-17 2015-10-06 Digifonica (International) Limited Uninterrupted transmission of internet protocol transmissions during endpoint changes
US10021729B2 (en) 2009-09-17 2018-07-10 Voip-Pal.Com, Inc. Uninterrupted transmission of internet protocol transmissions during endpoint changes
US10932317B2 (en) 2009-09-17 2021-02-23 VolP-Pal.com, Inc. Uninterrupted transmission of internet protocol transmissions during endpoint changes

Also Published As

Publication number Publication date
GB2361389A (en) 2001-10-17
GB2361389B (en) 2004-01-28
AU5480601A (en) 2001-10-30
US20020002041A1 (en) 2002-01-03
GB0009290D0 (en) 2000-05-31
US6775534B2 (en) 2004-08-10

Similar Documents

Publication Publication Date Title
US6775534B2 (en) Telecommunications system
US7239861B2 (en) System and method for communication service portability
FI111312B (en) Monitoring a connection to a user terminal in a telecommunications system
EP1593250B1 (en) Conversational bearer negotiation
US7200139B1 (en) Method for providing VoIP services for wireless terminals
US7330453B1 (en) System and method for integrating call control and data network access components
EP1123626B1 (en) Ip roaming number gateway
US6721401B2 (en) Method for redirecting a calling phone from a finder service to a destination phone
US20030128819A1 (en) Method for retrieving multimedia messages from a multimedia mailbox
WO2002025923A1 (en) Method for providing a collect call service in a mobile communication system
WO1998052337A1 (en) Method and apparatus for monitoring of telephone calls
JP2006320003A (en) Connection set-up in communication system
WO2006089949A2 (en) Method for controlling quality of service in a communication system by using policy decision function module
US7376419B2 (en) Call triggering to one or more service nodes upon receipt of initial trigger response
CN1379604A (en) Method of group exchange mode calling due to routing
KR100519665B1 (en) Method for Restriction of Anonymity Call in Asynchronous IMT-2000 Network
WO2003065660A1 (en) Method for achieving the interaction between terminals of telecommunication networks and related system
WO2002001889A1 (en) Selecting a numbering plan with the use of indicators
KR20080018749A (en) A method and apparatus for reducing impacts on the csi network originating csi interworking applied
KR101233388B1 (en) System and method for call processing of mobile terminal in private mobile service system connecting wcdma public network thereof
KR20060098637A (en) A method and apparatus for funcion of session initation proxy in umts
EP1832042A1 (en) Method for providing a bearer service to a mobile station in a telecommunications system
MXPA00011313A (en) Intelligent network and packet data network interoperability

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ CZ DE DE DK DK DM DZ EE EE ES FI FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PL PT RO RU SD SE SG SI SK SK SL TJ TM TR TT TZ UA UG UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: JP