WO2003009627A1 - Method and system for handling a network-identified emergency session - Google Patents

Method and system for handling a network-identified emergency session Download PDF

Info

Publication number
WO2003009627A1
WO2003009627A1 PCT/EP2001/004830 EP0104830W WO03009627A1 WO 2003009627 A1 WO2003009627 A1 WO 2003009627A1 EP 0104830 W EP0104830 W EP 0104830W WO 03009627 A1 WO03009627 A1 WO 03009627A1
Authority
WO
WIPO (PCT)
Prior art keywords
session
emergency
user equipment
message
information
Prior art date
Application number
PCT/EP2001/004830
Other languages
French (fr)
Inventor
Risto Kauppinen
Miikka POIKSELKÄ
Original Assignee
Nokia Corporation
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
Priority to DE60142450T priority Critical patent/DE60142450D1/en
Priority to PT01931670T priority patent/PT1386509E/en
Priority to JP2003514836A priority patent/JP4545436B2/en
Priority to EP01931670A priority patent/EP1386509B1/en
Priority to CNB018231756A priority patent/CN1282390C/en
Priority to AT01931670T priority patent/ATE472218T1/en
Application filed by Nokia Corporation filed Critical Nokia Corporation
Priority to CA2445156A priority patent/CA2445156C/en
Priority to PCT/EP2001/004830 priority patent/WO2003009627A1/en
Priority to US10/475,832 priority patent/US7116967B2/en
Priority to AU2001258380A priority patent/AU2001258380C1/en
Publication of WO2003009627A1 publication Critical patent/WO2003009627A1/en
Priority to US11/448,974 priority patent/US7623840B2/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M7/00—Arrangements for interconnection between switching centres
    • H04M7/006—Networks other than PSTN/ISDN providing telephone service, e.g. Voice over Internet Protocol (VoIP), including next generation networks with a packet-switched transport layer
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1069—Session establishment or de-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1101—Session protocols
    • H04L65/1104—Session initiation protocol [SIP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications
    • H04L65/401—Support for services or applications wherein the services involve a main real-time session and one or more additional parallel real-time or time sensitive sessions, e.g. white board sharing or spawning of a subconference
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/90—Services for handling of emergency or hazardous situations, e.g. earthquake and tsunami warning systems [ETWS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/50—Connection management for emergency connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1016—IP multimedia subsystem [IMS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2242/00—Special services or facilities
    • H04M2242/04—Special services or facilities for emergency applications

Definitions

  • the invention generally relates to the connection of emergency sessions such as emergency calls.
  • IP Multimedia networks IMS
  • the UE User Equipment
  • the UE may usually be able to indicate in the initial session setup (e.g. in the INVITE message of SIP) that the session is an emergency session.
  • the present invention provides method and system for enabling emergency sessions to be established in a reliable manner.
  • the invention provides a method and/or system as defined in the claims.
  • This invention discloses means and functions of how the network can detect an emergency session, how the UE can be informed about it and what effects this information has on later session setup.
  • the invention provides among others a Network-identification of an emergency session initiated by a session initiating entity such as a user equipment (UE) including mobile or stationary stations or terminals, or the like.
  • a session initiating entity such as a user equipment (UE) including mobile or stationary stations or terminals, or the like.
  • UE user equipment
  • a response is sent back to the UE immediately after a control means such as P-CSCF has discovered that the session is an emergency session.
  • a control means such as P-CSCF
  • the UE receives such a response it will perform a normal emergency session procedure, e.g. as defined in 3GPP specifications.
  • the UE will e.g. obtain or query location information and send it in the INVITE message and also the UE will activate an emergency PDP context for the session.
  • the invention enables to identify the session to _be an emergency session as soon as possible so that the network and the UE can perform the necessary special actions for the emergency session as quickly as possible.
  • the control entity such as P-CSCF does not respond immediately to UE when it has received an INVITE message from the UE but waits for the reception of a message, e.g. 183 Session Progress, from an emergency center or an intermediate network entity, and adds to that message the emergency information.
  • the information about the emergency call is not delayed at all, and the call establishment is continued in the conventional or any other manner such as with the 183 Session Progress message.
  • Sending an INVITE message takes remarkable radio resources and it is not preferable to send multiple INVITE messages.
  • This invention concerns a situation, in which PDP context activation can not or will not be performed at first when initiating a session for any reason, but a message such as an INVITE message is sent first from the UE to the CSCF.
  • Fig. 1 shows a first embodiment of a method and system in accordance with the present invention
  • Fig. 2 shows a second embodiment of a method and system in accordance with the present invention
  • Fig. 3 illustrates a third embodiment of a method and system in accordance with the present invention
  • Fig. 4 shows an implementation for emergency session processing in a normal case.
  • the UE is able to activate an emergency PDP context after it has been informed about the session characteristics. This is important to get high priority for the PDP context in the GPRS (General Packet Radio Service) and RAN (Radio Access Network) .
  • GPRS General Packet Radio Service
  • RAN Radio Access Network
  • the UE sends location information after it- is being informed about the session characteristics (it ' is assumed that location information is not sent in every INVITE message) .
  • the location information is used for selecting the most suitable Emergency Centre (EC) .
  • Fig. 1 shows an embodiment of the invention which includes a call originating element, i.e. a session initiating element, such as a mobile station (UE) 10, and a network which comprises a serving network element such as a Serving GPRS Support Node (SGSN) , and a further control element such as a Call State Control Function (CSCF) or Proxy Call State Control Function (P-CSCF) 11.
  • a serving network element such as a Serving GPRS Support Node (SGSN)
  • CSCF Call State Control Function
  • P-CSCF Proxy Call State Control Function
  • the further network elements necessary for completing an IP multimedia session such as a terminating element, a gateway node if needed, a subscriber information register such as a home location register (HLR) or home subscriber server (HSS) , etc. are known to the skilled man and are therefore neither shown nor described in more detail.
  • a MSC Mobile Switching Centre, not shown
  • the UE 1 may be equipped with a USIM (User Services Identity Module) .
  • USIM User Services Identity Module
  • Figs. 1, 2, and 3 relate to a Network-identified emergency session.
  • a solution to guarantee resources at the transport level to perform the emergency call is to respond back to the UE 10 immediately after a network entity, e.g. a control means such as P-CSCF 11, has discovered that the session is an emergency session.
  • a network entity e.g. a control means such as P-CSCF 11
  • P-CSCF 11 a control means such as P-CSCF 11
  • the UE 10 receives the response, i.e. is informed, by the network, on the initiated session being an emergency session, it will perform normal emergency session procedure, e.g. as defined in 3GPP specifications.
  • Fig. 1 shows the solution at a general level.
  • step 1 the UE 10 sends a session initiation message, e.g. an INVITE message of SIP (Session Initiation Protocol), which indicatess an identifier, e.g. the E.164 number or LN (logical name), of the called entity, to the P-CSCF -11.
  • a session initiation message e.g. an INVITE message of SIP (Session Initiation Protocol)
  • SIP Session Initiation Protocol
  • LN logical name
  • a step 2 the P-CSCF 11 analyses the number or LN. When detecting that a normal session is to initiated, a normal connection procedure is continued. When, however, the P-CSCF 11 discovers that the call is emergency call, steps 3 to 6 shown in Fig. 1 are performed.
  • step 3 a response is sent to the UE 10 indicating that the session is an emergency session.
  • Step 4 The UE 10 returns an acknowledgement message ACK to the P-CSCF 11.
  • the UE 10 may inform the user that the session is emergency session, e.g. by displaying an appropriate message on a display of the UE 10.
  • a normal emergency session is executed (performed) as indicated by step 6.
  • the execution of a normal emergency session means that the UE 10 will e.g. obtain location information and send it in the INVITE message and also that the UE 10 will activate an emergency PDP context for the session.
  • the response message at step 3 can be a new message, or an existing SIP message or other known message can be used.
  • the information in the response message may be a new parameter in SIP protocol, but an existing parameter may also be used.
  • Fig. 2 shows a solution in which, in step 3, a SIP 302 message "Moved Temporarily" is used as response.
  • the parameter value in the 302 message indicates that the session is an emergency session.
  • the parameter may e.g. " be "Contact: sip: emergency ⁇ visited. cscf. com” .
  • This value can e.g. be used in SIP URI when sending a new INVITE message to P-CSCF 11, or the UE 10 just generates a new INVITE message with the indication of an emergency session.
  • Another alternative can be to use the SIP NOTIFY method.
  • Fig. 2 has the same structure and functioning as the one of Fig. 1.
  • Fig. 3 illustrates another embodiment of the invention.
  • a Serving CSCF (S- CSCF) 12 and an Emergency Centre (EC) 13 are shown.
  • the embodiment according to Fig. 3 provides an alternative functioning as compared to the embodiments of Figs. 1 and 2.
  • the P-CSCF 11 does not respond back to the UE 10 immediately after P-CSCF 11 has discovered that the session is an emergency session. On the contrary it continues session establishment and optionally, if possible, the P-CSCF 11 adds an indication of emergency session to the messages generated by P-CSCF 11 for ensuring high priority treatment of the messages.
  • Fig. 3 The details of the procedure are shown in Fig. 3. Taking account of the nature of emergency session it is highly desirable not to add any additional delay also in case of abnormal situations to session establishment. By using the alternative of Fig. 3, it is possible to avoid the transfer of another INVITE message over the air interface, which is probably the largest and slowest message and thus very time- consuming.
  • the response message (in SIP, preferably a message "183 Progress") to the UE 10 preferably includes an indication of emergency session. This allows to activate an emergency PDP context for the session.
  • the S-CSCF 12 (or relevant server) will select an emergency center 13 without location information of the user (e.g. it selects a default emergency center, nearest emergency center or it may use some other technique to select the emergency center e.g. based on the address of P-CSCF 11.
  • the UE 10 initiates a session establishment and sends a session setup message, e.g. an INVITE message, to the P-CSCF 11.
  • the P-CSCF 11 analyses the number or logical name (LN) of the called party/entity indicated in the session setup message, and discovers that the call is an emergency call.
  • the P-CSCF 11 may add an indication of emergency session to the INVITE message (it is also possible that other elements add this indication of emergency session to the INVITE message) .
  • step 2 the INVITE message is forwarded to the S-CSCF 12.
  • Step 3 the S-CSCF 12 selects an emergency center (EC) 13 and forwards the INVITE message to the EC 13.
  • EC emergency center
  • Step 4 The EC 13 responds to the INVITE request by returning a response such as SIP 183 "Session Progress" to the S-CSCF 12.
  • SIP 183 Session Progress
  • Step 5 The S-CSCF 12 forwards the response such as SIP 183 "Session Progress" back to the P-CSCF 11.
  • Step 6 The P-CSCF 11 forwards the response such as SIP 183 "Session Progress" back to the UE 10.
  • the response includes the indication of emergency session.
  • the UE 10 thus learns that this session is an emergency session and can act properly.
  • Fig. 3 mean "Emergency call detected, Possibility to add an emergency indication" .
  • Fig. 4 presents a proposal for normal emergency session establishment for the case where the UE has USIM. It is assumed that the UE has activated a signalling PDP context to the GGSN in the visited PLMN.
  • UE may request SAI (Service Area Identity) from SGSN .
  • SAI Service Area Identity
  • SGSN sends response message to UE.
  • UE sends the SIP INVITE request, containing an initial SDP, to a P-CSCF determined via the CSCF discovery mechanism.
  • Information about emergency call is sent in the INVITE message.
  • UE includes the location information in the INVITE message.
  • P-CSCF detects that the call is an emergency call using the information in the INVITE message e.g. by analysing the number or name requested. P-CSCF selects a S-CSCF in the visited network and forwards the SIP INVITE request including the information about emergency call to S-CSCF.
  • S-CSCF uses the location information to select an appropriate EC. S-CSCF forwards the request to EC.
  • the media stream capabilities of the destination are returned along the signaling path.
  • S-CSCF forwards the message containing the destination SDP cababilities to P-CSCF.
  • P-CSCF authorizes the resources necessary for this session.
  • P-CSCF forwards the SDP message to the originating endpoint.
  • UE decides the final set of media streams for this session, and sends the Final SDP to P-CSCF.
  • P-CSCF forwards the final SDP to S-CSCF.
  • S-CSCF forwards this message to EC.
  • the UE activates a PDP context for the emergency session by sending the Activate Secondary PDP Context Request message to the SGSN.
  • the UE indicates that the PDP context is used for an emergency session.
  • the Allocation / Retention Priority shall be at once set to the high value.
  • the SGSN when recognising that the PDP context is for an emergency session, may itself request location information from SRNC, in order to receive updated or more accurate location information regarding the UE. SGSN thereafter sends a location report to Gateway Mobile Location services Centre (GMLC) as specified in TS 23.271, and the EC may obtain this location information from GMLC.
  • GMLC Gateway Mobile Location services Centre
  • UE sends the "Resource Reservation Successful" message to the terminating endpoint, via the signaling path established by the INVITE message.
  • P-CSCF forwards this message to S-CSCF.
  • S-CSCF forwards this message to EC.
  • EC sends information about alerting to S-CSCF.
  • S-CSCF forwards the Ringing message to P-CSCF.
  • P-CSCF forwards this message to UE.
  • S-CSCF forwards final 200 OK message to P-CSCF.
  • P-CSCF indicates the resources reserved for this session should now be committed.
  • P-CSCF forwards final 200 OK message to UE.
  • the calling party responds to the 200-OK final response with a SIP ACK message which is sent to P-CSCF.
  • P-CSCF forwards the SIP ACK message to S-CSCF
  • S-CSCF forwards the ACK message to EC.
  • the teaching according to the invention is preferably implemented in an All-IP Network but may also be employed in networks of various other types, i.e. in IM, GPRS and UMTS domains .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Environmental & Geological Engineering (AREA)
  • Public Health (AREA)
  • Emergency Management (AREA)
  • Health & Medical Sciences (AREA)
  • Telephonic Communication Services (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Computer And Data Communications (AREA)
  • Communication Control (AREA)

Abstract

The invention relates to a method and system for establishing an emergency session in a communication system which includes at least one user equipment and one or more network entities involved in establishing an emergency session. When the user equipment initiates a session by sending a message to a network entity indicating an identifier, e.g. the call number or logical name of a called entity, one of said network entities analyses the received identifier. When detecting that the session to be initiated is an emergency session, an information is returned to the user equipment for informing the latter that the initiated session is an emergency session. The user equipment thereupon initiates the execution of an emergency session. Thus, even when the user equipment is unable to detect, by itself, that the intended session is an emergency session, the network will inform the user equipment on the emergency session for ensuring appropriate handling thereof.

Description

TITLE
METHOD AND SYSTEM FOR HANDLING A NETWORK-IDENTIFIED EMERGENCY SESSION
FIELD AND BACKGROUND OF THE INVENTION
The invention generally relates to the connection of emergency sessions such as emergency calls.
Emergency calls shall be supported in IP Multimedia networks (IMS) . The UE (User Equipment) may usually be able to indicate in the initial session setup (e.g. in the INVITE message of SIP) that the session is an emergency session.
However, there may be situations where the initial session setup message is just sent with an ordinary number and there is no indication about the emergency. These situations may e.g. occur when a subscriber is roaming in another IMS network.
It is important to identify the intended emergency session as soon as possible, because the network and the UE need to perform some special actions for performing the emergency session.
SUMMARY OF THE INVENTION
The present invention provides method and system for enabling emergency sessions to be established in a reliable manner. The invention provides a method and/or system as defined in the claims.
This invention discloses means and functions of how the network can detect an emergency session, how the UE can be informed about it and what effects this information has on later session setup.
The invention provides among others a Network-identification of an emergency session initiated by a session initiating entity such as a user equipment (UE) including mobile or stationary stations or terminals, or the like.
Even when the user equipment is unable to detect by itself that the initiated session is an emergency session, it is quickly informed thereon and can then initiate the appropriate steps for establishing the emergency session.
According to a first embodiment of the invention, in order to guarantee resources at the transport level for the emergency call, a response is sent back to the UE immediately after a control means such as P-CSCF has discovered that the session is an emergency session. When the UE receives such a response it will perform a normal emergency session procedure, e.g. as defined in 3GPP specifications. To execute a normal emergency session, the UE will e.g. obtain or query location information and send it in the INVITE message and also the UE will activate an emergency PDP context for the session.
The invention enables to identify the session to _be an emergency session as soon as possible so that the network and the UE can perform the necessary special actions for the emergency session as quickly as possible. In one of the alternative implementations of the invention, the control entity such as P-CSCF does not respond immediately to UE when it has received an INVITE message from the UE but waits for the reception of a message, e.g. 183 Session Progress, from an emergency center or an intermediate network entity, and adds to that message the emergency information.
The information about the emergency call is not delayed at all, and the call establishment is continued in the conventional or any other manner such as with the 183 Session Progress message.
Sending an INVITE message takes remarkable radio resources and it is not preferable to send multiple INVITE messages.
Actually there is no delay in session establishment, since UE has not yet started creating secondary PDP Context before UE receives the SDP message. This means that the indication can be included with high priority for the user plane. If no emergency centre is indicated, a default emergency center may be chosen.
This invention concerns a situation, in which PDP context activation can not or will not be performed at first when initiating a session for any reason, but a message such as an INVITE message is sent first from the UE to the CSCF.
Further details, aspects and advantages of the invention will become apparent from the following reference to specific embodiments and the attached drawings.
BRIEF DESCRIPTION OF THE DRAWINGS
Fig. 1 shows a first embodiment of a method and system in accordance with the present invention;
Fig. 2 shows a second embodiment of a method and system in accordance with the present invention;
Fig. 3 illustrates a third embodiment of a method and system in accordance with the present invention;
Fig. 4 shows an implementation for emergency session processing in a normal case.
DESCRIPTION OF PREFERRED EMBODIMENTS OF THE INVENTION
This invention discloses solutions to several problems such as:
- The UE is able to activate an emergency PDP context after it has been informed about the session characteristics. This is important to get high priority for the PDP context in the GPRS (General Packet Radio Service) and RAN (Radio Access Network) .
- The UE sends location information after it- is being informed about the session characteristics (it' is assumed that location information is not sent in every INVITE message) . The location information is used for selecting the most suitable Emergency Centre (EC) .
Fig. 1 shows an embodiment of the invention which includes a call originating element, i.e. a session initiating element, such as a mobile station (UE) 10, and a network which comprises a serving network element such as a Serving GPRS Support Node (SGSN) , and a further control element such as a Call State Control Function (CSCF) or Proxy Call State Control Function (P-CSCF) 11. The further network elements necessary for completing an IP multimedia session such as a terminating element, a gateway node if needed, a subscriber information register such as a home location register (HLR) or home subscriber server (HSS) , etc. are known to the skilled man and are therefore neither shown nor described in more detail. Generally, a MSC (Mobile Switching Centre, not shown) may return to UE a Call Proceedings message which contains a Priority information field defining also EC (Emergency Centre) .
In all embodiments described above or below, the UE 1 may be equipped with a USIM (User Services Identity Module) .
The embodiments shown in Figs. 1, 2, and 3 relate to a Network-identified emergency session.
A solution to guarantee resources at the transport level to perform the emergency call is to respond back to the UE 10 immediately after a network entity, e.g. a control means such as P-CSCF 11, has discovered that the session is an emergency session. When the UE 10 receives the response, i.e. is informed, by the network, on the initiated session being an emergency session, it will perform normal emergency session procedure, e.g. as defined in 3GPP specifications.
Fig. 1 shows the solution at a general level.
In step 1, the UE 10 sends a session initiation message, e.g. an INVITE message of SIP (Session Initiation Protocol), which indicatess an identifier, e.g. the E.164 number or LN (logical name), of the called entity, to the P-CSCF -11.
In a step 2, the P-CSCF 11 analyses the number or LN. When detecting that a normal session is to initiated, a normal connection procedure is continued. When, however, the P-CSCF 11 discovers that the call is emergency call, steps 3 to 6 shown in Fig. 1 are performed.
In step 3, a response is sent to the UE 10 indicating that the session is an emergency session.
Step 4: The UE 10 returns an acknowledgement message ACK to the P-CSCF 11.
In an optional step 5, the UE 10 may inform the user that the session is emergency session, e.g. by displaying an appropriate message on a display of the UE 10.
Then, a normal emergency session is executed (performed) as indicated by step 6. The execution of a normal emergency session means that the UE 10 will e.g. obtain location information and send it in the INVITE message and also that the UE 10 will activate an emergency PDP context for the session.
The response message at step 3 can be a new message, or an existing SIP message or other known message can be used. The information in the response message may be a new parameter in SIP protocol, but an existing parameter may also be used.
Fig. 2 shows a solution in which, in step 3, a SIP 302 message "Moved Temporarily" is used as response. The parameter value in the 302 message indicates that the session is an emergency session. The parameter may e.g." be "Contact: sip: emergencyΘvisited. cscf. com" . This value can e.g. be used in SIP URI when sending a new INVITE message to P-CSCF 11, or the UE 10 just generates a new INVITE message with the indication of an emergency session. Another alternative can be to use the SIP NOTIFY method.
Apart from the above discusion, the embodiment shown in Fig. 2 has the same structure and functioning as the one of Fig. 1.
Fig. 3 illustrates another embodiment of the invention. In addition to the UE 10 and the P-CSCF 11, a Serving CSCF (S- CSCF) 12 and an Emergency Centre (EC) 13 are shown. The embodiment according to Fig. 3 provides an alternative functioning as compared to the embodiments of Figs. 1 and 2.
In order to achieve a very fast session establishment the P- CSCF 11 does not respond back to the UE 10 immediately after P-CSCF 11 has discovered that the session is an emergency session. On the contrary it continues session establishment and optionally, if possible, the P-CSCF 11 adds an indication of emergency session to the messages generated by P-CSCF 11 for ensuring high priority treatment of the messages.
The details of the procedure are shown in Fig. 3. Taking account of the nature of emergency session it is highly desirable not to add any additional delay also in case of abnormal situations to session establishment. By using the alternative of Fig. 3, it is possible to avoid the transfer of another INVITE message over the air interface, which is probably the largest and slowest message and thus very time- consuming.
The response message (in SIP, preferably a message "183 Progress") to the UE 10 preferably includes an indication of emergency session. This allows to activate an emergency PDP context for the session.
If there should not exist location information in S-CSCF 12 (or the relevant server) to select an emergency center 13, the S-CSCF 12 (or relevant server) will select an emergency center 13 without location information of the user (e.g. it selects a default emergency center, nearest emergency center or it may use some other technique to select the emergency center e.g. based on the address of P-CSCF 11. As shown in Fig. 3, in step 1, the UE 10 initiates a session establishment and sends a session setup message, e.g. an INVITE message, to the P-CSCF 11. The P-CSCF 11 analyses the number or logical name (LN) of the called party/entity indicated in the session setup message, and discovers that the call is an emergency call. The P-CSCF 11 may add an indication of emergency session to the INVITE message (it is also possible that other elements add this indication of emergency session to the INVITE message) .
In step 2, the INVITE message is forwarded to the S-CSCF 12.
In Step 3, the S-CSCF 12 selects an emergency center (EC) 13 and forwards the INVITE message to the EC 13.
Step 4: The EC 13 responds to the INVITE request by returning a response such as SIP 183 "Session Progress" to the S-CSCF 12. The subset of the media flows shown in steps 4 to 6 indicates that messages are returned back to originating endpoints proposing an EC 13 for providing support, or requesting the emergency session.
Step 5: The S-CSCF 12 forwards the response such as SIP 183 "Session Progress" back to the P-CSCF 11.
Step 6: The P-CSCF 11 forwards the response such as SIP 183 "Session Progress" back to the UE 10. The response includes the indication of emergency session. The UE 10 thus learns that this session is an emergency session and can act properly.
The circles and ovals shown in Fig. 3 mean "Emergency call detected, Possibility to add an emergency indication" . Fig. 4 presents a proposal for normal emergency session establishment for the case where the UE has USIM. It is assumed that the UE has activated a signalling PDP context to the GGSN in the visited PLMN.
In the following, the steps shown in Fig. 4 are described in more detail, referring to the step numbering of Fig. 4.
1. UE may request SAI (Service Area Identity) from SGSN .
2. SGSN sends response message to UE.
3. UE sends the SIP INVITE request, containing an initial SDP, to a P-CSCF determined via the CSCF discovery mechanism. Information about emergency call is sent in the INVITE message. UE includes the location information in the INVITE message.
4. P-CSCF detects that the call is an emergency call using the information in the INVITE message e.g. by analysing the number or name requested. P-CSCF selects a S-CSCF in the visited network and forwards the SIP INVITE request including the information about emergency call to S-CSCF.
5. S-CSCF uses the location information to select an appropriate EC. S-CSCF forwards the request to EC.
6. The media stream capabilities of the destination are returned along the signaling path.
7. S-CSCF forwards the message containing the destination SDP cababilities to P-CSCF.
8. P-CSCF authorizes the resources necessary for this session.
9. P-CSCF forwards the SDP message to the originating endpoint.
10. UE decides the final set of media streams for this session, and sends the Final SDP to P-CSCF.
11. P-CSCF forwards the final SDP to S-CSCF.
12. S-CSCF forwards this message to EC.
13. Activate PDP Context Request. The UE activates a PDP context for the emergency session by sending the Activate Secondary PDP Context Request message to the SGSN. The UE indicates that the PDP context is used for an emergency session. For the PDP context, the Allocation / Retention Priority shall be at once set to the high value.
14. The SGSN, when recognising that the PDP context is for an emergency session, may itself request location information from SRNC, in order to receive updated or more accurate location information regarding the UE. SGSN thereafter sends a location report to Gateway Mobile Location services Centre (GMLC) as specified in TS 23.271, and the EC may obtain this location information from GMLC.
15. Radio Access Bearer Setup
16. Create PDP Context Request
17. Create PDP Context Response
18. Activate PDP Context Accept
19. UE sends the "Resource Reservation Successful" message to the terminating endpoint, via the signaling path established by the INVITE message.
20. P-CSCF forwards this message to S-CSCF. 21. S-CSCF forwards this message to EC.
22. Resources are reserved successfully.
23. EC sends information about alerting to S-CSCF.
24. S-CSCF forwards the Ringing message to P-CSCF. 25. P-CSCF forwards this message to UE.
26. EC answers the call and sends final 200 OK message to S- CSCF.
27. S-CSCF forwards final 200 OK message to P-CSCF.
28. P-CSCF indicates the resources reserved for this session should now be committed.
29. P-CSCF forwards final 200 OK message to UE.
30. UE starts the media flow for this session.
31. The calling party responds to the 200-OK final response with a SIP ACK message which is sent to P-CSCF.
32. P-CSCF forwards the SIP ACK message to S-CSCF
33. S-CSCF forwards the ACK message to EC.
Although the invention has been described above with reference to specific embodiments, the scope of protection of the invention intends to cover all modifications, omissions, additions and amendments of the disclosed features as well.
The teaching according to the invention is preferably implemented in an All-IP Network but may also be employed in networks of various other types, i.e. in IM, GPRS and UMTS domains .

Claims

1. A method for establishing an emergency session in a communication system which includes at least one user equipment and one or more network entities involved in establishing an emergency session, wherein, when said user equipment initiates a session by sending a message to a network entity indicating an identifier of a called entity, one of said network entities analyses the received identifier, and, when detecting that the session to be initiated is an emergency session, an information is sent to the user equipment for informing the user equipment that the initiated session is an emergency session. -
2. A method of claim 1 comprising a further step wherein the user equipment initiates the execution of an emergency session upon receipt of said information sent to the user equipment for informing the user equipment that the initiated session is an emergency session.
3. Method according to claim 2, wherein the execution of the emergency session includes the step of obtaining location information of the user equipment and of sending the location information to one of the network entities.
4. Method according to claim 2 or 3, wherein the execution of the emergency session includes the step of activating an emergency PDP context for the session.
5. Method according to any one of the preceding claims, wherein the information returned to the user equipment is a message, preferably a SIP (Session Initiation Protocol) message, which includes a parameter indicating an address of a network entity to be addressed for establishing an emergency session.
6. Method according to any one of the preceding claims, wherein the identifier of the called entity is the call number or logical name of the called entity.
7. Method according to any one of the preceding claims, wherein, when the network entity detects that the session to be initiated is an emergency session, an emergency center is informed on the emergency session to be established, and said information is returned to the user equipment only after receipt of a response from the emergency center, the emergency session then being established between the user equipment and the emergency center.
8. Method according to any one of the preceding claims, wherein the network entity analysing the received identifier is a Call State Control Function (CSCF) .
9. A method for establishing an emergency session in a communication system which includes at least one user equipment and at least one call controlling network element involved in establishing an emergency session, wherein, when said user equipment initiates a session by sending a message to the call controlling network element indicating an identifier of a called entity, the call controlling network element analyses the received identifier, and, when detecting that the session to be initiated is an emergency session, an information is returned to the user equipment for informing the user equipment that the initiated session is an emergency session.
10. A method of claim 9, wherein the call controlling network element is a P-CSCF.
11. A method of claim 9 or 10, comprising a further step wherein the user equipment reinitiates the session by sending a message to the call controlling network element, the message comprising the said information.
12. A Method of claim 9 or 10, comprising a further step wherein the user equipment initiates a new session by sending a message to the call controlling network element the message comprising the said information.
13. A method of claims 11 or 12, comprising the further step of, in response to receiving the information, the network initiating the execution of the emergency session.
14. A method for establishing an emergency session in a communication system which includes at least one user equipment, at least one call controlling network element involved in establishing an emergency session, and an emergency center, wherein, when said user equipment initiates a session by sending a message to the call controlling network element indicating an identifier of a called entity, the call controlling network element analyses the received identifier, and, when detecting that the session to be initiated is an emergency session, the network element sends an information to the emergency center or to an intermediate network element for forwarding the information to the emergency center, said information informing the emergency center on the emergency session to be established., an indication of the emergency session being sent to the user equipment for informing the user equipment that the initiated session is an emergency session.
15. Method according to claim 14, wherein after receipt of a response from the emergency center, the emergency session is established between the user equipment and the emergency center.
16. A method of claim 14 or 15, wherein the call controlling network element is a P-CSCF.
17. A communication system for establishing an emergency session, the communication system including at least one user equipment and one or more network entities involved in establishing an emergency session, wherein said user equipment is adapted to initiate a session by sending a message to a network entity indicating an identifier of a called entity, one of said network entities is adapted to analyse the received identifier, when detecting that the session to be initiated is an emergency session, said analysing network entity or another network entity is adapted to send an information to the user equipment for informing the latter that the initiated session is an emergency session.
18. A system according to claim 17, wherein the user equipment is adapted to initiate, when receiving the information that the initiated session is an emergency session, the execution of an emergency session.
19. System according to claim 18, wherein the execution of the emergency session includes the step of obtaining location information of the user equipment and of sending the location information to one of the network entities.
20. System according to claim 18 or 19, wherein the execution of the emergency session includes the step of activating an emergency PDP context for the session.
21. System according to any one of the preceding system claims, wherein the information returned to the user equipment is a message, preferably a SIP (Session Initiation Protocol) message, which includes a parameter indicating an address of a network entity to be addressed for establishing an emergency session.
22. System according to any one of the preceding system claims, wherein the identifier of the called entity is the call number or logical name of the called entity.
23. System according to any one of the preceding system claims, wherein the network entity, when detecting that the session to be initiated is an emergency session, is adapted to inform an emergency center on the emergency session to be established, and to send said information to the user equipment only after receipt of a response from the emergency center, the emergency session then being established between the user equipment and the emergency center.
24. System according to any one of the preceding system claims, wherein the network entity analysing the received identifier is a Call State Control Function (CSCF) .
25. A communication system for establishing an emergency session, the communication system including at least one user equipment and at least one call controlling network element involved in establishing an emergency session, wherein, when said user equipment initiates a session by sending a message to the call controlling network element indicating an identifier of a called entity, the call controlling network element is adapted to analyse the received identifier, wherein, when detecting that the session to be initiated is an emergency session, to send an information to the user equipment for informing the user equipment that the initiated session is an emergency session.
26. A system of claim 25, wherein the call controlling network element is a P-CSCF.
27. A system of claim 25 or 26, wherein the user equipment is adapted to reinitiate the session by sending a message to the call controlling network element, the message comprising the said information.
28. A system of claim 25 or 26, wherein the user equipment is adapted to initiate a new session by sending a message to the call controlling network element, the message comprising the said information.
29. A system of claims 25 or 26, wherein the network is adapted to initiate the execution of the emergency session in response to receiving the information.
30. A communication system for establishing an emergency session, the communication system including at least one user equipment, at least one call controlling network element involved in establishing an emergency session, and an emergency center, wherein, when said user equipment initiates a session by sending a message to the call controlling network element indicating an identifier of a called entity, the call controlling network element is adapted to analyse the received identifier, and, when detecting that the session to be initiated is an emergency session, to send an information to the emergency center or to an intermediate network element for forwarding the information to the emergency center, said information informing the emergency center on the emergency session to be established, an indication of the emergency session being sent to the user equipment for informing the user equipment that the initiated session is an emergency session.
31. A system according to claim 30, wherein after receipt of a response from the emergency center, the emergency session is established between the user equipment and the emergency center.
32. A system of claim 31 or 32, wherein the call controlling network element is a P-CSCF.
PCT/EP2001/004830 2001-04-27 2001-04-27 Method and system for handling a network-identified emergency session WO2003009627A1 (en)

Priority Applications (11)

Application Number Priority Date Filing Date Title
PT01931670T PT1386509E (en) 2001-04-27 2001-04-27 User equipment, network element, and method and communication system for establishing an emergency session
JP2003514836A JP4545436B2 (en) 2001-04-27 2001-04-27 Method and system for handling network-identified emergency sessions
EP01931670A EP1386509B1 (en) 2001-04-27 2001-04-27 User equipment, network element, and method and communication system for establishing an emergency session
CNB018231756A CN1282390C (en) 2001-04-27 2001-04-27 Method and system for handling a network-identified emergency session
AT01931670T ATE472218T1 (en) 2001-04-27 2001-04-27 SUBSCRIBER TERMINAL, NETWORK ELEMENT, AND METHOD AND COMMUNICATIONS SYSTEM FOR ESTABLISHING AN EMERGENCY MEETING
DE60142450T DE60142450D1 (en) 2001-04-27 2001-04-27 SUBSCRIBER DEVICE, NETWORK ELEMENT, AND METHOD AND COMMUNICATION SYSTEM FOR MAKING AN EMERGENCY SESSION
CA2445156A CA2445156C (en) 2001-04-27 2001-04-27 Method and system for handling a network-identified emergency session
PCT/EP2001/004830 WO2003009627A1 (en) 2001-04-27 2001-04-27 Method and system for handling a network-identified emergency session
US10/475,832 US7116967B2 (en) 2001-04-27 2001-04-27 Method and system for handling a network-identified emergency session
AU2001258380A AU2001258380C1 (en) 2001-04-27 2001-04-27 Method and system for handling a network-identified emergency session
US11/448,974 US7623840B2 (en) 2001-04-27 2006-06-08 Method and system for handling a network-identified emergency session

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2001/004830 WO2003009627A1 (en) 2001-04-27 2001-04-27 Method and system for handling a network-identified emergency session

Related Child Applications (2)

Application Number Title Priority Date Filing Date
US10475832 A-371-Of-International 2001-04-27
US11/448,974 Continuation US7623840B2 (en) 2001-04-27 2006-06-08 Method and system for handling a network-identified emergency session

Publications (1)

Publication Number Publication Date
WO2003009627A1 true WO2003009627A1 (en) 2003-01-30

Family

ID=8164395

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2001/004830 WO2003009627A1 (en) 2001-04-27 2001-04-27 Method and system for handling a network-identified emergency session

Country Status (10)

Country Link
US (2) US7116967B2 (en)
EP (1) EP1386509B1 (en)
JP (1) JP4545436B2 (en)
CN (1) CN1282390C (en)
AT (1) ATE472218T1 (en)
AU (1) AU2001258380C1 (en)
CA (1) CA2445156C (en)
DE (1) DE60142450D1 (en)
PT (1) PT1386509E (en)
WO (1) WO2003009627A1 (en)

Cited By (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2005039227A1 (en) * 2003-10-17 2005-04-28 Nortel Networks Limited Method for obtaining location information for emergency services in wireless multimedia networks
FR2869190A1 (en) * 2004-04-19 2005-10-21 Alcatel Sa METHOD FOR USING A WIRELESS TELEPHONE TERMINAL TO ESTABLISH AN EMERGENCY CONNECTION IN A LOCAL NETWORK; TERMINAL AND SERVER FOR IMPLEMENTING SAID METHOD
WO2006078202A1 (en) * 2005-01-19 2006-07-27 Telefonktiebolaget Lm Ericsson (Publ) A method and apparatus for handling emergency calls
WO2007014511A1 (en) 2005-08-04 2007-02-08 Huawei Technologies Co., Ltd. A method, system and access control function for testing the emergent service
WO2007072176A1 (en) * 2005-12-21 2007-06-28 Nokia Corporation Prioritized network access for wireless access networks
WO2007098713A1 (en) * 2006-03-03 2007-09-07 Huawei Technologies Co., Ltd. An emergency call method and system
WO2007106005A1 (en) * 2006-03-15 2007-09-20 Teliasonera Ab Automatic positioning of equipment connected to a telecommunication and data communication system
WO2007072462A3 (en) * 2005-12-23 2007-10-18 Ericsson Telefon Ab L M Voice call continuity for emergency calls
WO2007127991A3 (en) * 2006-04-28 2008-01-03 Qualcomm Inc System and method for supporting voice call continuity for voip emergency calls
EP2073467A1 (en) * 2007-12-21 2009-06-24 Nokia Siemens Networks Oy Messaging mechanism
WO2009137617A1 (en) * 2008-05-07 2009-11-12 Qualcomm Incorporated System, apparatus and method to enable mobile stations to identify calls based on predetermined values set in a call header
CN101123822B (en) * 2007-08-01 2010-07-14 中兴通讯股份有限公司 Implementation method for emergent call service in IP multimedia subsystem central service
WO2011123794A1 (en) * 2010-04-02 2011-10-06 Interdigital Patent Holdings, Inc. Enhancements to ip multimedia subsystem (ims) emergency services architecture
US8327136B2 (en) 2005-09-15 2012-12-04 Samsung Electronics Co., Ltd. Inter-entity coupling method, apparatus and system for content protection
EP2536178A1 (en) * 2010-02-12 2012-12-19 Huawei Technologies Co., Ltd. Method, apparatus and system for processing priority services
EP2615795A3 (en) * 2008-06-02 2013-08-14 Research In Motion Limited Coding and behavior when receiving an IMS emergency session indicator from authorized source
US8755765B2 (en) 2008-06-02 2014-06-17 Blackberry Limited System and method for managing emergency requests
US9462616B2 (en) 2008-06-02 2016-10-04 Blackberry Limited System and method for managing emergency requests
US9814081B2 (en) 2013-08-02 2017-11-07 Mediatek Inc. Methods for processing emergency call and communications apparatuses utilizing the same

Families Citing this family (40)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
ATE313193T1 (en) * 2001-10-31 2005-12-15 Nokia Corp A METHOD FOR HANDLING MESSAGES BETWEEN A TERMINAL AND A DATA NETWORK
US7606556B2 (en) * 2002-05-06 2009-10-20 Nokia Corporation System and method for handling sessions of specific type in communication networks
BRPI0417128B1 (en) 2003-12-01 2017-07-04 Interdigital Technology Corporation Method for the process of passing a real-time session to a first wireless device from a second wireless device
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.
KR100735328B1 (en) * 2005-02-04 2007-07-04 삼성전자주식회사 Method for updating user data in ptt system and system therefor
FR2888071A1 (en) * 2005-06-30 2007-01-05 France Telecom MODULE AND COMMUNICATION SYSTEM FOR IMPLEMENTING A SYSTEM FOR REMOTELY MANAGING EQUIPMENT
HUE046984T2 (en) * 2005-08-02 2020-04-28 Qualcomm Inc location based routing of VoIP emergency calls
US10178522B2 (en) * 2005-08-02 2019-01-08 Qualcomm Incorporated VoIP emergency call support
US7548158B2 (en) * 2005-08-08 2009-06-16 Telecommunication Systems, Inc. First responder wireless emergency alerting with automatic callback and location triggering
US9137770B2 (en) 2005-09-15 2015-09-15 Qualcomm Incorporated Emergency circuit-mode call support
US20070121797A1 (en) * 2005-11-28 2007-05-31 Lucent Technologies Inc. Automatic establishment of emergency call to PSAP via IP session
DE102006019719A1 (en) * 2006-04-27 2007-10-31 Siemens Ag Emergency call connection installing method, involves avoiding emergency call connection on Internet protocol multimedia system registration of equipment at system for emergency call connection, if equipment is already registered at system
CN101444117B (en) * 2006-05-02 2011-11-23 株式会社Ntt都科摩 Mobile terminal and mobile communication system
US20070275743A1 (en) * 2006-05-24 2007-11-29 Sybase 365, Inc. System and Method for Emergency Notification
US20080008157A1 (en) * 2006-07-06 2008-01-10 Edge Stephen W Method And Apparatus For Parallel Registration And Call Establishment
CN101110991B (en) * 2006-07-14 2010-06-23 华为技术有限公司 Method, device and system for recognizing abuse of emergency bearing resource in IMS
CN101106813B (en) * 2006-07-14 2010-04-21 华为技术有限公司 Method for recognizing abuse of emergent carrier resource and carrier control IP gateway in network
CN100563373C (en) * 2006-08-25 2009-11-25 华为技术有限公司 Realize the method and the system thereof of urgency traffic
CN101132623B (en) * 2006-08-25 2011-08-10 华为技术有限公司 Emergency business processing method and communication network
US8929360B2 (en) 2006-12-07 2015-01-06 Cisco Technology, Inc. Systems, methods, media, and means for hiding network topology
US8041331B2 (en) * 2007-01-05 2011-10-18 Research In Motion Limited System and method for conditionally attempting an emergency call setup
US8223630B2 (en) * 2007-04-24 2012-07-17 At&T Intellectual Property I, L.P. System for monitoring operations of an ENUM system
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
CN101227648B (en) * 2008-02-13 2012-01-11 中兴通讯股份有限公司 Method for implementing IP multimedia subsystem urgent call business
US8254529B2 (en) * 2008-02-20 2012-08-28 Oldham Eamonn John Method and apparatus for emergency services number alerting in an internet protocol network
US20090296689A1 (en) * 2008-06-02 2009-12-03 Research In Motion Limited Privacy-Related Requests for an IMS Emergency Session
CN101764872B (en) * 2008-12-26 2014-02-05 展讯通信（上海）有限公司 Mobile terminal with help-asking mode and search and rescue device
EP2412152B1 (en) * 2009-03-24 2022-01-26 BlackBerry Limited System and method for providing a circuit switched domain number
US8457114B2 (en) * 2009-09-28 2013-06-04 Telefonaktiebolaget Lm Ericsson (Publ) Method to optimize call establishment in mobile satellite communication systems
US9560509B2 (en) * 2009-11-02 2017-01-31 Telefonaktiebolaget Lm Ericsson (Publ) Emergency signalling in an IP multimedia subsystem network
IN2012DN01872A (en) * 2009-11-02 2015-08-21 Ericsson Telefon Ab L M
CN102055744A (en) * 2009-11-06 2011-05-11 中兴通讯股份有限公司 Implementing system and method of IP (Internet Protocol) multimedia subsystem emergency call service
JP5456708B2 (en) * 2011-02-14 2014-04-02 株式会社Ｎｔｔドコモ Mobile communication method and call session control node
US8849237B2 (en) 2011-05-11 2014-09-30 Qualcomm Incorporated Priority registration for in-vehicle emergency call service
US8989697B2 (en) 2011-05-11 2015-03-24 Qualcomm Incorporated Priority registration for in-vehicle emergency call service
TWI514903B (en) * 2011-12-08 2015-12-21 Ind Tech Res Inst Apparatus and method for determining and routing emergency communications
US9832234B2 (en) * 2012-06-01 2017-11-28 Telefonaktiebolaget Lm Ericsson (Publ) IMS inbound roamer and short number dialing
CN102868986A (en) * 2012-09-20 2013-01-09 中兴通讯股份有限公司 Number association implementation method and system
US9204256B2 (en) * 2013-03-11 2015-12-01 Qualcomm Incorporated Method and apparatus for providing user plane or control plane position services
US9807580B1 (en) 2016-06-01 2017-10-31 T-Mobile Usa, Inc. Emergency call handling within IP multimedia system (IMS) networks

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1992016077A1 (en) * 1991-03-05 1992-09-17 Motorola, Inc. Radio capable of automatic system selection in emergency situations
US5689548A (en) * 1996-05-21 1997-11-18 Ericsson, Inc. Emergency call back using MSC numbers
DE19638112A1 (en) * 1996-09-11 1998-04-23 Siemens Ag Method for controlling emergency call connections in cordless telecommunication systems, in particular DECT / GAP systems
WO1999021380A1 (en) * 1997-10-22 1999-04-29 Telefonaktiebolaget Lm Ericsson (Publ) System and method of routing emergency services calls in a radio telecommunications network

Family Cites Families (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP3255319B2 (en) * 1993-09-14 2002-02-12 ソニー株式会社 Emergency message communication method
US5493582A (en) * 1994-02-04 1996-02-20 Ericsson Ge Mobile Communications Method and apparatus for encoding and decoding automatic radio identification data
WO1997021314A1 (en) 1995-12-07 1997-06-12 Telefonaktiebolaget Lm Ericsson (Publ) Emergency call handling in a cellular telecommunications system
FI960986A (en) 1996-03-01 1997-09-02 Nokia Telecommunications Oy Allocation of emergency speech in a mobile communication system
US6233445B1 (en) * 1997-01-14 2001-05-15 Ericsson, Inc. Establishing emergency calls within a mobile telecommunications network
US6374099B1 (en) 1999-05-10 2002-04-16 Lucent Technologies Inc. High priority and/or emergency overload access control system
GB0006464D0 (en) * 2000-03-18 2000-05-10 Ericsson Telefon Ab L M Ip communication in a cellular telecommunications system
US7298697B2 (en) 2000-04-10 2007-11-20 Nokia Corporation Setting a communication channel
US7623447B1 (en) 2000-04-10 2009-11-24 Nokia Corporation Telephony services in mobile IP networks
GB2361389B (en) * 2000-04-15 2004-01-28 Ericsson Telefon Ab L M Telecommunications system
US7302251B2 (en) * 2000-10-06 2007-11-27 Nortel Networks Limited Channel request and contention resolution apparatus and method
US6571092B2 (en) * 2001-02-15 2003-05-27 Nokia Networks Oy Technique for enabling emergency call callback of a terminal without a valid subscriber identity
US7437142B2 (en) * 2001-04-27 2008-10-14 Nokia Corporation Method and system for enabling emergency sessions to be established in abnormal cases
GB2382203A (en) * 2001-11-20 2003-05-21 Hewlett Packard Co Alerting users to impending events
US6697628B1 (en) * 2002-03-01 2004-02-24 Nokia Corporation Apparatus, and associated method, for determining geographical positioning of a mobile station operable in a radio communication system
US6927727B2 (en) * 2003-01-21 2005-08-09 Monica Cleghorn Internet protocol based 911 system
US7130384B2 (en) * 2005-03-30 2006-10-31 Lucent Technologies Inc. End user device supported emergency 9-1-1 function

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1992016077A1 (en) * 1991-03-05 1992-09-17 Motorola, Inc. Radio capable of automatic system selection in emergency situations
US5689548A (en) * 1996-05-21 1997-11-18 Ericsson, Inc. Emergency call back using MSC numbers
DE19638112A1 (en) * 1996-09-11 1998-04-23 Siemens Ag Method for controlling emergency call connections in cordless telecommunication systems, in particular DECT / GAP systems
WO1999021380A1 (en) * 1997-10-22 1999-04-29 Telefonaktiebolaget Lm Ericsson (Publ) System and method of routing emergency services calls in a radio telecommunications network

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
MOH M ET AL: "Mobile IP telephony: mobility support of SIP", PROCEEDINGS OF THE INTERNATIONAL CONFERENCE ON COMPUTER COMMUNICATIONS AND NETWORKS, XX, XX, 11 October 1999 (1999-10-11), pages 554 - 559, XP002143545 *

Cited By (48)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8417214B2 (en) 2003-10-17 2013-04-09 Apple Inc. Method for obtaining location information for emergency services in wireless multimedia networks
WO2005039227A1 (en) * 2003-10-17 2005-04-28 Nortel Networks Limited Method for obtaining location information for emergency services in wireless multimedia networks
US8229389B2 (en) 2003-10-17 2012-07-24 Apple Inc. Method for obtaining location information for emergency services in wireless multimedia networks
US9125038B2 (en) 2003-10-17 2015-09-01 Apple Inc. Method for obtaining location information for emergency services in wireless multimedia networks
US8655306B2 (en) 2003-10-17 2014-02-18 Apple Inc. Method for obtaining location information for emergency services in wireless multimedia networks
FR2869190A1 (en) * 2004-04-19 2005-10-21 Alcatel Sa METHOD FOR USING A WIRELESS TELEPHONE TERMINAL TO ESTABLISH AN EMERGENCY CONNECTION IN A LOCAL NETWORK; TERMINAL AND SERVER FOR IMPLEMENTING SAID METHOD
WO2005109930A3 (en) * 2004-04-19 2006-06-15 Cit Alcatel Method for establishing an emergency connection in a local wireless network
US9807579B2 (en) 2004-04-19 2017-10-31 Alcatel Lucent Method that enables the user of a wireless telephone terminal to establish an emergency connection in a local network, and terminal and server for carrying out this method
US9002314B2 (en) 2004-04-19 2015-04-07 Alcatel Lucent Method that enables the user of a wireless telephone terminal to establish an emergency connection in a local network, and terminal and server for carrying out this method
WO2005109930A2 (en) * 2004-04-19 2005-11-17 Alcatel Method for establishing an emergency connection in a local wireless network
WO2006078202A1 (en) * 2005-01-19 2006-07-27 Telefonktiebolaget Lm Ericsson (Publ) A method and apparatus for handling emergency calls
WO2007014511A1 (en) 2005-08-04 2007-02-08 Huawei Technologies Co., Ltd. A method, system and access control function for testing the emergent service
EP1821458A1 (en) * 2005-08-04 2007-08-22 Huawei Technologies Co., Ltd. A method, system and access control function for testing the emergent service
US20070274462A1 (en) * 2005-08-04 2007-11-29 Huawei Technologies Co., Ltd. Method, System and Access Control Function for Detecting Emergency Service
EP1821458A4 (en) * 2005-08-04 2008-03-12 Huawei Tech Co Ltd A method, system and access control function for testing the emergent service
US8327136B2 (en) 2005-09-15 2012-12-04 Samsung Electronics Co., Ltd. Inter-entity coupling method, apparatus and system for content protection
WO2007072176A1 (en) * 2005-12-21 2007-06-28 Nokia Corporation Prioritized network access for wireless access networks
WO2007072462A3 (en) * 2005-12-23 2007-10-18 Ericsson Telefon Ab L M Voice call continuity for emergency calls
WO2007098713A1 (en) * 2006-03-03 2007-09-07 Huawei Technologies Co., Ltd. An emergency call method and system
WO2007106005A1 (en) * 2006-03-15 2007-09-20 Teliasonera Ab Automatic positioning of equipment connected to a telecommunication and data communication system
US8340626B2 (en) 2006-04-28 2012-12-25 Qualcomm Incorporated System and method for supporting voice call continuity for VOIP emergency calls
WO2007127991A3 (en) * 2006-04-28 2008-01-03 Qualcomm Inc System and method for supporting voice call continuity for voip emergency calls
CN101123822B (en) * 2007-08-01 2010-07-14 中兴通讯股份有限公司 Implementation method for emergent call service in IP multimedia subsystem central service
WO2009080605A1 (en) * 2007-12-21 2009-07-02 Nokia Siemens Networks Oy Messaging mechanism
EP2073467A1 (en) * 2007-12-21 2009-06-24 Nokia Siemens Networks Oy Messaging mechanism
US8527607B2 (en) 2007-12-21 2013-09-03 Nokia Siemens Networks Oy Messaging mechanism
US9706378B2 (en) 2008-05-07 2017-07-11 Qualcomm Incorporated System, apparatus and method to enable mobile stations to identify calls based on predetermined values set in a call header
RU2482622C2 (en) * 2008-05-07 2013-05-20 Квэлкомм Инкорпорейтед System, apparatus and method to enable mobile stations to identify calls based on predetermined values set in call header
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
WO2009137617A1 (en) * 2008-05-07 2009-11-12 Qualcomm Incorporated System, apparatus and method to enable mobile stations to identify calls based on predetermined values set in a call header
CN102017669A (en) * 2008-05-07 2011-04-13 高通股份有限公司 System, apparatus and method to enable mobile stations to identify calls based on predetermined values set in a call header
US9215734B2 (en) 2008-06-02 2015-12-15 Blackberry Limited System and method for managing emergency requests
US9814082B2 (en) 2008-06-02 2017-11-07 Blackberry Limited System and method for managing emergency requests
US10856359B2 (en) 2008-06-02 2020-12-01 Blackberry Limited System and method for managing emergency requests
US8755765B2 (en) 2008-06-02 2014-06-17 Blackberry Limited System and method for managing emergency requests
EP2615795A3 (en) * 2008-06-02 2013-08-14 Research In Motion Limited Coding and behavior when receiving an IMS emergency session indicator from authorized source
US10631360B2 (en) 2008-06-02 2020-04-21 Blackberry Limited System and method for managing emergency requests
US9462616B2 (en) 2008-06-02 2016-10-04 Blackberry Limited System and method for managing emergency requests
US9602552B2 (en) 2008-06-02 2017-03-21 Blackberry Limited Coding and behavior when receiving an IMS emergency session indicator from authorized source
US10187924B2 (en) 2008-06-02 2019-01-22 Blackberry Limited System and method for managing emergency requests
EP2536178A4 (en) * 2010-02-12 2013-02-20 Huawei Tech Co Ltd Method, apparatus and system for processing priority services
EP2536178A1 (en) * 2010-02-12 2012-12-19 Huawei Technologies Co., Ltd. Method, apparatus and system for processing priority services
EP3185596A1 (en) * 2010-02-12 2017-06-28 Huawei Technologies Co., Ltd. Method, apparatus and system for processing priority services
EP3570604A1 (en) * 2010-02-12 2019-11-20 Huawei Technologies Co., Ltd. Method, apparatus and system for processing priority services
US8897176B2 (en) 2010-02-12 2014-11-25 Huawei Technologies Co. Ltd. Method, apparatus and system for processing priority services
WO2011123794A1 (en) * 2010-04-02 2011-10-06 Interdigital Patent Holdings, Inc. Enhancements to ip multimedia subsystem (ims) emergency services architecture
US8942665B2 (en) 2010-04-02 2015-01-27 Interdigital Patent Holding, Inc. Enhancements to IP multimedia subsystems (IMS) emergency services architecture
US9814081B2 (en) 2013-08-02 2017-11-07 Mediatek Inc. Methods for processing emergency call and communications apparatuses utilizing the same

Also Published As

Publication number Publication date
JP4545436B2 (en) 2010-09-15
US7623840B2 (en) 2009-11-24
CA2445156C (en) 2013-04-09
US20070097967A1 (en) 2007-05-03
US7116967B2 (en) 2006-10-03
CN1282390C (en) 2006-10-25
EP1386509A1 (en) 2004-02-04
AU2001258380C1 (en) 2008-05-01
AU2001258380B2 (en) 2007-08-23
EP1386509B1 (en) 2010-06-23
DE60142450D1 (en) 2010-08-05
US20040137873A1 (en) 2004-07-15
CA2445156A1 (en) 2003-01-30
CN1505908A (en) 2004-06-16
ATE472218T1 (en) 2010-07-15
PT1386509E (en) 2010-07-27
JP2004535645A (en) 2004-11-25

Similar Documents

Publication Publication Date Title
US7116967B2 (en) Method and system for handling a network-identified emergency session
AU2001258380A1 (en) Method and system for handling a network-identified emergency session
US8150393B2 (en) Method for handling service failures
EP1593250B1 (en) Conversational bearer negotiation
KR101276002B1 (en) Call handling for ims registered user
US10044553B2 (en) Media resource reservation request failure handling for voice over mobile wireless network
US20100014508A1 (en) Method And System For Emergency Call
US8457114B2 (en) Method to optimize call establishment in mobile satellite communication systems
US9337917B2 (en) Call establishment optimization for IMS based mobile satellite system
US7437142B2 (en) Method and system for enabling emergency sessions to be established in abnormal cases
WO2008046319A1 (en) A method and system to realize voice call continuity when dealing with emergency business
US20100284267A1 (en) Call set-up in a communication network
US8335485B2 (en) Call routing
WO2009039688A1 (en) Late call forwarding method in ip multimedia core network subsystem centralized service
US20090052438A1 (en) Method, system and device for processing supplementary services
US7672312B1 (en) Connection release in a two-layer communication network
RU2259642C2 (en) Method and system for processing emergency communication session including network identification
WO2008046313A1 (en) Reselecting method for called user terminal in redirection service, system and apparatus thereof
JP2008092599A (en) Method and system for dealing with emergency session to be subjected to network identification
RU2377743C2 (en) Method and system for processing emergency communication session with network identification
KR20060098637A (en) A method and apparatus for funcion of session initation proxy in umts

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CR CU CZ DE DK DM DZ EE ES 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 SL TJ TM TR TT TZ UA UG US 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)
WWE Wipo information: entry into national phase

Ref document number: 2003514836

Country of ref document: JP

WWE Wipo information: entry into national phase

Ref document number: 1673/CHENP/2003

Country of ref document: IN

WWE Wipo information: entry into national phase

Ref document number: 2445156

Country of ref document: CA

Ref document number: 2001258380

Country of ref document: AU

WWE Wipo information: entry into national phase

Ref document number: 018231756

Country of ref document: CN

WWE Wipo information: entry into national phase

Ref document number: 10475832

Country of ref document: US

WWE Wipo information: entry into national phase

Ref document number: 2001931670

Country of ref document: EP

WWP Wipo information: published in national office

Ref document number: 2001931670

Country of ref document: EP

REG Reference to national code

Ref country code: DE

Ref legal event code: 8642