WO2007098713A1 - Procédé et système d'appel d'urgence - Google Patents

Procédé et système d'appel d'urgence Download PDF

Info

Publication number
WO2007098713A1
WO2007098713A1 PCT/CN2007/000693 CN2007000693W WO2007098713A1 WO 2007098713 A1 WO2007098713 A1 WO 2007098713A1 CN 2007000693 W CN2007000693 W CN 2007000693W WO 2007098713 A1 WO2007098713 A1 WO 2007098713A1
Authority
WO
WIPO (PCT)
Prior art keywords
emergency call
emergency
domain
cscf
session
Prior art date
Application number
PCT/CN2007/000693
Other languages
English (en)
French (fr)
Inventor
Yanfei Yang
Original Assignee
Huawei Technologies Co., Ltd.
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 Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Publication of WO2007098713A1 publication Critical patent/WO2007098713A1/zh
Priority to US12/203,538 priority Critical patent/US20100014508A1/en

Links

Classifications

    • 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
    • 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/1083—In-session procedures
    • H04L65/1095—Inter-network session transfer or sharing
    • 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
    • H04M—TELEPHONIC COMMUNICATION
    • H04M7/00—Arrangements for interconnection between switching centres
    • H04M7/0024—Services and arrangements where telephone services are combined with data services
    • H04M7/0057—Services where the data services network provides a telephone service in addition or as an alternative, e.g. for backup purposes, to the telephone service provided by the telephone services network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2242/00—Special services or facilities
    • H04M2242/04—Special services or facilities for emergency applications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
    • H04Q2213/1307—Call setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
    • H04Q2213/13091—CLI, identification of calling line
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
    • H04Q2213/13097—Numbering, addressing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
    • H04Q2213/13204—Protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
    • H04Q2213/13248—Multimedia
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
    • H04Q2213/1337—Operator, emergency services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
    • H04Q2213/13389—LAN, internet
    • 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

Definitions

  • the present invention relates to the field of mobile communication technologies, and in particular, to an emergency call method and system. Background of the invention
  • IMS IP Multimedia Subsystem
  • PS Packet Control Protocol
  • IMS IP Multimedia Subsystem
  • IMS IP Multimedia Subsystem
  • PS Packet Control Protocol
  • IMS IP Multimedia Subsystem
  • IMS IP Multimedia Subsystem
  • IMS IP Multimedia Subsystem
  • PS Packet Control Protocol
  • IMS can be conveniently used for real-time user-to-user mobile services such as multimedia voice and video telephony services.
  • IMS supports user-to-user communication services through a range of mechanisms, including: session negotiation and management, quality of service (QoS), and mobility management.
  • QoS quality of service
  • Operator can also introduce non-real-time user-to-user services such as: chat and instant messaging, multi-user services such as: multimedia conferencing and chat rooms, and server-to-user services such as: dynamic push services and click-to-dial services.
  • Emergency call is a voice service function unique to mobile communication systems. As long as the user dials a special number such as 110, 119, 120 or other public service number in the area covered by the mobile network, the call will be transferred to the corresponding emergency call center (PSAP) such as: police station, fire brigade, Emergency centers or other public service centers provide 24-hour emergency assistance to the public.
  • PSAP emergency call center
  • police station police station
  • fire brigade emergency centers
  • Emergency centers or other public service centers provide 24-hour emergency assistance to the public.
  • emergency services such as public security, fire protection, hospitals or other public service agencies.
  • emergency calls are implemented in the circuit (CS) domain.
  • the PS domain With the gradual IPization of the network, the PS domain is now gradually supporting emergency calls and using IMS for emergency calls.
  • the call signaling control is performed.
  • an emergency call service in the IMS domain can be referred to an emergency call IMS domain (IMS-EMER, IMS Emergency Call ) 0
  • 3GPP specifies the emergency session situation of two IMS domains: One is that after the user dials the emergency number or emergency uniform resource identifier (URI), the user terminal (UE) detects that the user-initiated call is an emergency call.
  • URI emergency uniform resource identifier
  • UE user terminal
  • Steps 101 to 103 After detecting that the number or URI dialed by the UE matches the emergency number or emergency URI configured by the UE, the UE sends the emergency session request message carrying the emergency identifier to the emergency through the proxy call session control function entity (P-CSCF). Call Session Control Function Entity (E-CSCF).
  • P-CSCF proxy call session control function entity
  • E-CSCF Call Session Control Function Entity
  • Steps 104-106 After receiving the emergency session request message, the E-CSCF forwards the emergency session request message to the corresponding PSAP, and then the PSAP returns a response message to the UE through the E-CSCF and the P-CSCF, and the UE passes the P-CSCF. The E-CSCF sends a response confirmation message to the PSAP. After the PSAP receives the response confirmation message, the emergency session is established.
  • the UE does not detect that the user-initiated call is an emergency call.
  • the first processing mode on the network side is as shown in FIG. 2, and the specific steps are as follows: :
  • Steps 201 to 202 After detecting that the number or URI dialed by the user does not match the emergency number or emergency URI configured by the user, the UE carries the number or URI dialed by the user in the session request message and sends the message to the P-CSCF.
  • the session request is a normal session request, and the session request message does not carry an emergency identifier.
  • the emergency number of the area where the visited network is located is different from the emergency number of the area where the home network is located, since the UE saves the emergency number of the area where the home network is located, the user makes a call on the visited network. After the emergency number in the area where the network is located, the UE cannot detect that the user dialed the number as an emergency number.
  • Step 203 After receiving the session request message, the P-CSCF determines whether the number or URI carried in the session request message matches the emergency number or emergency URI configured by itself, and if yes, performs step 204; otherwise, establishes the current session according to the normal session process. Session, the process ends.
  • Steps 204 to 207 The P-CSCF carries the emergency identifier to the E-CSCF in the emergency session request message, and the E-CSCF forwards the emergency session request message to the PSAP, and then the PSAP returns to the UE through the E-CSCF and the P-CSCF.
  • the UE sends a response confirmation message to the PSAP through the P-CSCF and the E-CSCF, and after the PSAP receives the response confirmation message, the emergency session is established.
  • the UE After the user dials the emergency number or the emergency II I, the UE does not detect that the user-initiated call is an emergency call, and the two processes on the network side return a session rejection message indicating that the CS domain emergency call is re-initiated, as shown in FIG.
  • the flow chart of the second processing is shown in FIG. 3, and the specific steps are as follows:
  • Step 301 After detecting the number or URI dialed by the user, the UE detects that the number or URI does not match the emergency number or emergency URI configured by itself.
  • Step 302 The UE sends the number or URI in the session request message to the UE.
  • the session request is a normal session request, and the session request message does not carry an emergency identifier.
  • the P-CSCF determines whether the number or URI carried in the session request message matches the emergency number or emergency URI configured by itself, and if yes, step 304 is performed; otherwise, the current session is established according to the normal session process. Session, the process ends.
  • Step 304 The P-CSCF returns a session reject message to the UE, where the session reject message carries indication information indicating that the CS domain emergency call is re-initiated.
  • Step 305 After receiving the session reject message, the UE re-initiates the emergency call of the CS domain according to the indication that the session rejection message is re-initiated.
  • the P-CSCF detects that the call initiated by the UE is an emergency call. After the call, the UE is only notified to re-initiate the emergency call of the CS domain. Thereafter, the UE can only re-execute the emergency session of the CS domain.
  • the problem caused by this is: When the CS domain does not support the emergency session, the emergency call fails; When the IMS domain supports the emergency session, the UE can only initiate an emergency call in the CS domain, but cannot initiate an emergency call in the IMS domain, which reduces the success rate of the emergency call.
  • the present invention provides an emergency call method and system to improve the success rate of an emergency call.
  • the technical solution of the present invention is implemented as follows:
  • An emergency call method including:
  • the CSCF detects that the session request sent by the UE is an emergency session request, and the information indicating that the emergency call is re-initiated is carried in the session reject message and sent to the UE according to the local policy.
  • the UE re-initiates the CS domain or the IMS domain according to the indication information.
  • Emergency call is carried in the session reject message and sent to the UE according to the local policy.
  • An emergency call system includes: a UE and a CSCF, and the CSCF includes: an emergency call determination unit and an emergency call domain selection unit, where
  • the UE is configured to initiate a session request to the emergency call determining unit, and re-initiate the emergency call of the CS domain or the IMS domain according to the session reject message sent by the emergency call domain selection unit;
  • An emergency call determining unit configured to: after determining that the session request initiated by the UE is an emergency session request, forwarding the session request sent by the UE to the emergency call domain selecting unit;
  • the emergency call domain selection unit is configured to: after receiving the session request sent by the emergency call determination unit, carry the information indicating that the emergency call is re-initiated in the session rejection message to the UE according to the local policy.
  • the method and system provided by the present invention when the CSCF detects that the session request sent by the UE is an emergency session request, will indicate to re-initiate the CS domain or the IMS domain emergency call according to the local policy configured by itself.
  • the indication information is carried in the session rejection message.
  • the UE After receiving the session reject message, the UE re-initiates the emergency call of the CS domain or the IMS domain according to the indication information.
  • the method and the system of the present invention can instruct the UE to re-initiate an emergency call in the CS domain or the IMS domain according to whether the current network side supports the emergency session of the CS domain or the emergency session of the IMS domain.
  • FIG. 1 is a schematic flowchart of an emergency call message when a UE detects that a user-initiated call is an emergency call according to the 3GPP;
  • FIG. 2 is a schematic diagram of a first emergency call message flow when the UE does not detect that the user-initiated call is an emergency call according to the 3GPP;
  • 3 is a flow chart of a second type of emergency call when the UE does not detect that the user-initiated call is an emergency call according to the 3GPP;
  • FIG. 4 is a flow chart of an emergency call when the UE does not detect that the user-initiated call is an emergency call according to the present invention
  • FIG. 5 is a flowchart of a first embodiment of a first embodiment of an emergency call when a UE does not detect that a user-initiated call is an emergency call according to the present invention
  • FIG. 6 is a flowchart of a second embodiment of a second embodiment of the present invention, in which the UE does not detect that the user-initiated call is an emergency call;
  • FIG. 8 is a system block diagram of a specific embodiment of an emergency call provided by the present invention. Mode for carrying out the invention
  • FIG. 4 is a flow chart of an emergency call when the UE does not detect that the user-initiated call is an emergency call according to the present invention. As shown in FIG. 4, the specific steps are as follows:
  • Step 401 After detecting the number or URI dialed by the user, the UE detects that the number or URI does not match the emergency number or emergency URI configured by itself.
  • Step 402 The UE carries the number or URI dialed by the user in the session request message and sends the message to the CSCF.
  • the session request is a normal session request, and the session request message does not carry an emergency identifier.
  • the CSCF determines whether the number or UI carried in the session request message matches the emergency number or emergency URI configured by itself, and if yes, step 404 is performed; otherwise, the session is established according to the normal session process. This process ends.
  • Step 404 The CSCF selects the CS domain or the IMS domain as the network domain for re-initiating the emergency call by the UE according to the local policy configured by itself.
  • the local policy saved by the CSCF itself can be configured by the operator according to whether the network side only supports the emergency session of the CS domain, or only the emergency session of the IMS domain, or both.
  • the CS domain and the IMS domain priority can be configured.
  • the CSCF can select the domain with the higher priority as the network domain in which the UE re-initiates the emergency call.
  • Step 405 The CSCF carries the indication information indicating that the CS domain or the IMS domain emergency call is re-initiated, and sends the indication information to the UE in the session rejection message.
  • Step 406 After receiving the session reject message, the UE re-initiates the emergency call of the CS domain or the IMS domain according to the indication that the CS domain or the IMS domain emergency call is re-initiated according to the indication carried in the session rejection message.
  • the session reject message carries an indication indicating that the CS domain emergency session is re-initiated. Then, the UE re-initiates the emergency call of the CS domain. If the session reject message carries the indication information indicating that the IMS domain emergency session is re-initiated, the UE re-initiates the emergency call of the IMS domain.
  • the present invention can implement a session reject message indicating that an emergency call of the CS domain or the IMS domain is re-initiated by extending the type parameter in the 380 response message, specifically, expanding the value of the type parameter in the 380 response message to two.
  • Step 501 The UE detects that the user dials After the number or URI, it is detected that the number or UI does not match the emergency number or emergency URI configured by itself.
  • Step 502 The UE carries the number or URI dialed by the user in the session request message and sends the message to the P-CSCF.
  • the session request is a normal session request, and the session request message does not carry an emergency identifier.
  • the P-CSCF determines whether the number or URI carried in the session request message matches the emergency number or emergency URI configured by itself, and if yes, step 504 is performed; otherwise, the current session is established according to the normal session process. Session, the process ends.
  • Step 504 The P-CSCF selects a CS domain or an IMS domain as a network domain in which the UE re-initiates an emergency call according to a local policy configured by itself.
  • Step 505 The P-CSCF will indicate an indication to re-initiate the CS domain or IMS domain emergency call.
  • the information is carried in the session reject message and sent to the UE.
  • Step 506 After receiving the session reject message, the UE re-initiates the emergency call of the CS domain or the IMS domain according to the indication that the CS domain or the IMS domain emergency call is re-initiated according to the indication carried in the session rejection message.
  • FIG. 6 is a flowchart of a second embodiment of the present invention, in which the UE does not detect an emergency call when the user-initiated call is an emergency call. As shown in FIG. 6, the specific steps are as follows: Step 601: The UE detects that the user dials After the number or URI, it is detected that the number or UI does not match the emergency number or emergency URI configured by itself.
  • Step 602 The UE carries the number or URI dialed by the user in the session request message and sends the message to the P-CSCF.
  • the session request is a normal session request, and the session request message does not carry an emergency identifier.
  • the P-CSCF determines whether the number or URI carried in the session request message matches the emergency number or emergency URI configured by itself, and if yes, step 604 is performed; otherwise, step 606 is performed.
  • Step 604 The P-CSCF selects the CS domain or the IMS domain as the network domain in which the UE re-initiates the emergency call according to the local policy configured by itself.
  • Step 605 The P-CSCF sends an indication that the re-initiation of the CS domain or the IMS domain emergency call is carried in the session reject message to the UE, and the process goes to step 610.
  • Step 606 The P-CSCF forwards the session request message sent by the UE to the serving call session control function entity (S-CSCF).
  • S-CSCF serving call session control function entity
  • Step 607 After receiving the session request message, the S-CSCF determines whether the number or URI carried in the session request message matches the emergency number or emergency URI configured by itself, and if yes, step 608 is performed; otherwise, the current session process is established according to the normal session process. Session, the process ends.
  • Step 608 The S-CSCF selects the CS domain or the IMS domain as the network domain in which the UE re-initiates the emergency call according to the local policy configured by itself.
  • Step 609 The S-CSCF sends the indication information indicating that the CS domain or the IMS domain emergency call is re-initiated in the session reject message to the UE through the P-CSCF, and proceeds to step .610.
  • Step 610 After receiving the session reject message, the UE re-initiates the emergency call of the CS domain or the IMS domain according to the indication that the CS domain or the IMS domain emergency call is re-initiated according to the indication carried in the session rejection message.
  • FIG. 7 is a system block diagram of an emergency call provided by the present invention. As shown in FIG. 7, it mainly includes a UE 71 and a CSCF 72, and the CSCF 72 includes an emergency call determining unit 721 and an emergency call domain selecting unit 722, where
  • the UE 71 is configured to send a session request message to the emergency call determining unit 721, and after receiving the session reject message sent by the emergency call domain selecting unit 722, re-initiate the CS domain or the IMS domain emergency call according to the indication carried in the session reject message. Indicates that the emergency call for the CS domain or IMS domain is re-initiated.
  • the emergency call determining unit 721 is configured to forward the session request message sent by the UE to the emergency call domain selecting unit 722 after determining that the session request sent by the UE 71 without the emergency identifier is an emergency session request.
  • the emergency call domain selection unit 722 is configured to: after receiving the session request message sent by the emergency call determining unit 721, select a circuit CS domain or an IMS domain as a network domain in which the UE re-initiates an emergency call according to a local policy configured by itself, and The indication information indicating that the CS domain or the IMS domain emergency call is re-initiated is carried in the session rejection message and sent to the UE 71.
  • the CSCF may be a P-CSCF.
  • FIG. 8 is a system block diagram of a specific embodiment of an emergency call provided by the present invention.
  • the method mainly includes a UE 71 and a CSCF 72, and the CSCF 72 includes a P-CSCF and an S-CSCF, and the P-CSCF includes: an emergency call judgment.
  • the UE 71 is configured to send a session request message to the emergency call determination unit 721 of the P-CSCF, and reject the session sent by the emergency call domain selection unit 722 of the P-CSCF or the second emergency call domain selection unit 7222 of the S-CSCF.
  • the emergency message of the CS domain or the IMS domain is re-initiated according to the indication of the emergency message of the CS domain or the IMS domain.
  • the emergency call determining unit 721 is configured to: after determining that the session request not sent by the UE 71 is an emergency session request, forwarding the session request message sent by the UE to the emergency call domain selecting unit 722; After the session request not carrying the emergency identity is not requested for the emergency session, the second emergency call determination unit 7212 of the S-CSCF forwards the session request message sent by the UE.
  • the emergency call domain selection unit 722 is configured to: after receiving the session request message sent by the emergency call determining unit 721, select a circuit CS domain or an IMS domain as a network domain in which the UE re-initiates an emergency call according to a local policy configured by itself, and The indication information indicating that the CS domain or the IMS domain emergency call is re-initiated is carried in the session rejection message and sent to the UE 71.
  • the second emergency call determining unit 7212 is configured to: after determining that the session request not sent by the emergency call determining unit 721 of the P-CSCF is an emergency session request, to the second emergency call domain selecting unit 7222 of the S-CSCF Forward the session request message.
  • the second emergency call domain selecting unit 7222 is configured to: after receiving the session request message sent by the second emergency call determining unit 7212 of the S-CSCF, select the circuit CS domain or the MS domain as the UE according to the local policy configured by itself.
  • the network domain that initiates the emergency call, and the indication information indicating that the CS domain or the IMS domain emergency call is re-initiated is carried in the session rejection message and sent to the UE 71.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • General Engineering & Computer Science (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephonic Communication Services (AREA)

Description

紧急呼叫方法及***
技术领域
本发明涉及移动通信技术领域， 具体涉及一种紧急呼叫方法及系 统。 发明背景
IP多媒体子***（ IMS )是第三代合作伙伴組织 （ 3GPP )在 R5版 本提出的支持 IP多媒体业务的子***，它的核心特点是釆用会话初始化 协议（SIP )和与接入的无关性。 IMS 是一个在分组（PS )域上的多媒 体控制 /呼叫控制平台， 支持会话类和非会话类多媒体业务， 为未来的多 媒体应用提供了一个通用的业务平台。 IMS可方便地用于实时的用户到 用户移动业务如： 多媒体语音及视频电话业务等。 IMS通过一系列机制 来支持用户到用户的通信业务， 这些机制包括： 会话协商和管理、 服务 质量（QoS )和移动性管理等。 借助 IMS技术， 运营商还可推出非实时 的用户到用户业务如： 聊天和即时消息、 多用户业务如： 多媒体会议和 聊天室、 以及服务器到用户业务如： 动态推式业务和点击拨号业务。
紧急呼叫是移动通信***中特有的一种话音业务功能。 只要在移动 网络覆盖的区域内， 当用户拨打一些特殊号码如： 110、 119、 120 或其 它公共服务号码等后， 呼叫会转到相应的紧急呼叫中心（PSAP )如： 警 察局、 消防队、 急救中心或其它公共服务中心等， 从而向群众提供 24 小时的紧急救助服务。 整个***的运行由电信运营商和公安、 消防、 医 院或其它公共服务机构等紧急服务机构共同协作完成。
一般情况下， 紧急呼叫都是在电路（CS )域中实现的， 随着网络的 逐步 IP化， 目前 PS域也开始逐步支持紧急呼叫， 并利用 IMS对紧急会 话进行呼叫信令控制。 当前， 利用 IMS域提供的紧急呼叫业务可以简称 为 IMS域紧急呼叫 （IMS-EMER, IMS Emergency Call )0
目前， 3GPP明确规定了两种 IMS域的紧急会话情况： 一种是在用 户拨打紧急号码或紧急统一资源标识符（URI )后， 用户终端 （UE )检 测到用户发起的呼叫为紧急呼叫， 图 1给出了这种情况下的紧急呼叫消 息流程示意图， 如图 1所示， 其具体步骤如下：
步驟 101~103： UE检测到用户拨打的号码或 URI与自身配置的紧 急号码或紧急 URI匹配后，将携带紧急标识的紧急会话请求消息通过代 理呼叫会话控制功能实体（ P-CSCF )发送给紧急呼叫会话控制功能实体 ( E-CSCF )。
步驟 104~106： E-CSCF收到该紧急会话请求消息后，将该紧急会话 请求消息转发给对应的 PSAP, 之后 PSAP通过 E-CSCF、 P-CSCF向 UE 返回响应消息， UE通过 P-CSCF、 E-CSCF向 PSAP发送响应确认消息， PSAP收到该响应确认消息后， 本次紧急会话建立。
另一种是用户拨打了紧急号码或紧急 URI后， UE没有检测到用户 发起的呼叫为紧急呼叫， 在这种情况下， 网络侧的第一种处理方式如图 2所示， 其具体步驟如下：
步驟 201〜202： UE检测到用户拨打的号码或 URI不与自身配置的 紧急号码或紧急 URI匹配后，将用户拨打的号码或 URI携带在会话请求 消息中发送给 P-CSCF。
这里，会话请求为普通会话请求，会话请求消息中未携带紧急标识。 当 UE由归属网络漫游到拜访网络后， 且拜访网络所在区域的紧急 号码与归属网络所在区域的紧急号码不同， 由于 UE 自身保存的是归属 网络所在区域的紧急号码， 则用户在拜访网络拨打拜访网络所在区域的 紧急号码后， UE就无法检测出用户拨打号码为紧急号码。 步驟 203: P-CSCF收到会话请求消息后， 判断该会话请求消息携带 的号码或 URI是否与自身配置的紧急号码或紧急 URI匹配，若是，执行 步骤 204; 否则， 按照普通会话流程建立本次会话， 本流程结束。
步骤 204~207： P-CSCF将紧急标识携带在紧急会话请求消息中发送 至 E-CSCF, E-CSCF将该紧急会话请求消息转发给 PSAP, 之后 PSAP 通过 E-CSCF、 P-CSCF向 UE返回响应消息， UE通过 P-CSCF、 E-CSCF 向 PSAP发送响应确认消息， PSAP收到该响应确认消息后， 本次紧急 会话建立。
在用户拨打紧急号码或紧急 II I后， UE没有检测到用户发起的呼 叫为紧急呼叫时， 网络侧的笫二种处理是向 UE返回指示重新发起 CS 域紧急呼叫的会话拒绝消息， 图 3给出了该第二种处理时的流程图， 如 图 3所示， 其具体步骤如下：
步骤 301： UE检测到用户拨打的号码或 URI后， 且检测到该号码 或 URI不与自身配置的紧急号码或紧急 URI匹配。
步骤 302: UE 将该号码或 URI 携带在会话请求消息中发送给
P-CSCF。
这里，会话请求为普通会话请求，会话请求消息中未携带緊急标识。 步骤 303: P-CSCF收到会话请求消息后， 判断该会话请求消息携带 的号码或 URI是否与自身配置的紧急号码或紧急 URI匹配，若是，执行 步驟 304; 否则， 按照普通会话流程建立本次会话， 本流程结束。
步骤 304: P-CSCF向 UE返回会话拒绝消息， 该会话拒绝消息携带 指示重新发起 CS域紧急呼叫的指示信息。
步骤 305: UE收到该会话拒绝消息后，根据该会话拒绝消息携带的 指示重新发起 CS域紧急呼叫的指示信息， 重新发起 CS域的紧急呼叫。
从图 3所示流程可以看出： P-CSCF检测到 UE发起的呼叫为紧急呼 叫后， 只通知 UE重新发起 CS域的紧急呼叫， 此后 UE只能重新进行 CS域的紧急会话， 这样引起的问题是： 当 CS域不支持紧急会话时， 会 导致紧急呼叫失败； 同时， 当 IMS域支持紧急会话时， UE只能发起 CS 域的紧急呼叫， 而无法发起 IMS域的紧急呼叫， 降低了紧急呼叫的成功 率。 发明内容
本发明提供一种紧急呼叫方法及***， 以提高紧急呼叫的成功率。 本发明的技术方案是这样实现的：
一种紧急呼叫方法， 包括：
CSCF检测到 UE发来的会话请求为紧急会话请求， 根据本地策略， 将指示重新发起紧急呼叫的信息携带在会话拒绝消息中发送给 UE; UE 根据所述指示信息， 重新发起 CS域或 IMS域的紧急呼叫。
一种紧急呼叫***， 包括： UE和 CSCF, 且， CSCF包括： 紧急呼 叫判断单元和紧急呼叫域选择单元， 其中，
UE, 用于向紧急呼叫判断单元发起会话请求， 并根据紧急呼叫域选 择单元发来的会话拒绝消息重新发起 CS域或 IMS域的紧急呼叫；
紧急呼叫判断单元， 用于在判定 UE发起的会话请求为紧急会话请 求后， 向紧急呼叫域选择单元转发 UE发来的会话请求；
紧急呼叫域选择单元， 用于在收到紧急呼叫判断单元发来的会话请 求后， 根据本地策略， 将指示重新发起紧急呼叫的信息携带在会话拒绝 消息中发送给 UE。
与现有技术相比， 本发明所提供的方法及***在 CSCF检测到 UE 发来的会话请求为紧急会话请求时， 根据自身配置的本地策略， 将指示 重新发起 CS域或 IMS域紧急呼叫的指示信息携带在会话拒绝消息中发 送给 UE, UE收到会话拒绝消息后， 根据所述指示信息， 重新发起 CS 域或 IMS域的紧急呼叫。本发明方法及***在网络侧检测到当前呼叫为 紧急呼叫后， 可根据当前网络侧支持 CS域的紧急会话还是支持 IMS域 的紧急会话， 指示 UE重新发起 CS域或 IMS域的紧急呼叫， 避免了单 一返回重新在 CS域发起紧急呼叫指示时所造成的紧急会话失败情况的 发生， 提高了紧急呼叫的成功率； 同时， 完善了现有协议中关于紧急呼 叫的流程。 附图简要说明
图 1为 3GPP规定的 UE检测到用户发起的呼叫为紧急呼叫时的紧 急呼叫消息流程示意图；
图 2为 3GPP规定的 UE未检测到用户发起的呼叫为紧急呼叫时的 第一种紧急呼叫消息流程示意图；
图 3为 3GPP规定的 UE未检测到用户发起的呼叫为紧急呼叫时的 第二种紧急呼叫流程图；
图 4为本发明提供的 UE未检测到用户发起的呼叫为紧急呼叫时的 紧急呼叫流程图；
图 5为本发明提供的 UE未检测到用户发起的呼叫为紧急呼叫时的 紧急呼叫的具体实施例一的流程图；
图 6为本发明提供的 UE未检测到用户发起的呼叫为紧急呼叫时的 紧急呼叫的具体实施例二的流程图；
图 7为本发明提供的紧急呼叫的***框图；
图 8为本发明提供的紧急呼叫的具体实施例的***框图。 实施本发明的方式
下面结合附图及具体实施例对本发明再作进一步详细的说明。
图 4是本发明提供的 UE未检测到用户发起的呼叫为紧急呼叫时的 紧急呼叫流程图， 如图 4所示， 其具体步骤如下：
步骤 401 : UE检测到用户拨打的号码或 URI后， 且检测到该号码 或 URI不与自身配置的紧急号码或紧急 URI匹配。
步骤 402: UE将用户拨打的号码或 URI携带在会话请求消息中发 送给 CSCF。
这里，会话请求为普通会话请求，会话请求消息中未携带紧急标识。 步骤 403: CSCF收到会话请求消息后，判断该会话请求消息携带的 号码或 U I是否与自身配置的紧急号码或紧急 URI匹配，若是，执行步 骤 404; 否则， 按照普通会话流程建立本次会话， 本流程结束。
步骤 404: CSCF根据自身配置的本地策略，选择 CS域或 IMS域作 为 UE重新发起紧急呼叫的网络域。
CSCF自身保存的本地策略，可由运营商根据网络侧只支持 CS域的 紧急会话， 还是只支持 IMS域的紧急会话， 还是二者同时支持， 将 UE 重新发起 CS域或 IMS域紧急呼叫的信息配置在 CSCF上； 在网絡侧同 时支持 CS域和 IMS域的紧急会话时，可配置 CS域和 IMS域的优先级， CSCF可选择优先级高的域作为 UE重新发起紧急呼叫的网络域。
步骤 405: CSCF将指示重新发起 CS域或 IMS域紧急呼叫的指示信 息携带在会话拒绝消息中发送给 UE。
步骤 406: UE收到会话拒绝消息后，根据该会话拒绝消息携带的指 示重新发起 CS域或 IMS域紧急呼叫的指示信息，重新发起 CS域或 IMS 域的紧急呼叫。
若该会话拒绝消息携带指示重新发起 CS域紧急会话的指示信息， 则 UE重新发起 CS域的紧急呼叫， 若该会话拒绝消息携带指示重新发 起 IMS域紧急会话的指示信息， 则 UE重新发起 IMS域的紧急呼叫。
若 UE重新发起 IMS域的紧急呼叫， 则具体流程如图 1所示的步骤 102-1060
由于现有的 SIP 380响应消息是一个重选艮务消息， 且 380响应消 息的重选服务（ alternative -service )参数包含的类型 ( type )和原因 ( reason ) 子参数中， 类型参数只有一个取值： "紧急"， 代表指示 UE重新发起 CS 域的紧急呼叫。 因此， 本发明可通过对 380响应消息中的类型参数的扩 展实现指示重新发起 CS域或 IMS域的紧急呼叫的会话拒绝消息， 具体 地， 将 380响应消息中的类型参数的取值扩展为两个： "紧急 "和 "IMS紧 急"，其中， "紧急 "代表指示 UE重新发起 CS域的紧急呼叫， "IMS紧急" 代表指示 UE重新发起 IMS域的紧急呼叫。
图 5是本发明提供的 UE未检测到用户发起的呼叫为紧急呼叫时的 紧急呼叫的具体实施例一的流程图， 如图 5所示， 其具体步骤如下： 步骤 501: UE检测到用户拨打的号码或 URI后， 且检测到该号码 或 U I不与自身配置的紧急号码或紧急 URI匹配。
步骤 502: UE将用户拨打的号码或 URI携带在会话请求消息中发 送给 P-CSCF。
这里，会话请求为普通会话请求，会话请求消息中未携带紧急标识。 步骤 503: P-CSCF收到会话请求消息后， 判断该会话请求消息携带 的号码或 URI是否与自身配置的紧急号码或紧急 URI匹配，若是，执行 步骤 504; 否则， 按照普通会话流程建立本次会话， 本流程结束。
步骤 504: P-CSCF根据自身配置的本地策略，选择 CS域或 IMS域 作为 UE重新发起紧急呼叫的网络域。
步驟 505: P-CSCF将指示重新发起 CS域或 IMS域紧急呼叫的指示 信息携带在会话拒绝消息中发送给 UE。
步骤 506: UE收到会话拒绝消息后，根据该会话拒绝消息携带的指 示重新发起 CS域或 IMS域紧急呼叫的指示信息，重新发起 CS域或 IMS 域的紧急呼叫。
图 6是本发明提供的 UE未检测到用户发起的呼叫为紧急呼叫时的 紧急呼叫的具体实施例二的流程图， 如图 6所示， 其具体步驟如下： 步骤 601: UE检测到用户拨打的号码或 URI后， 且检测到该号码 或 U I不与自身配置的紧急号码或紧急 URI匹配。
步骤 602: UE将用户拨打的号码或 URI携带在会话请求消息中发 送给 P-CSCF。
这里，会话请求为普通会话请求，会话请求消息中未携带紧急标识。 步骤 603: P-CSCF收到会话请求消息后， 判断该会话请求消息携带 的号码或 URI是否与自身配置的紧急号码或紧急 URI匹配，若是，执行 步骤 604; 否则， 执行步骤 606。
步骤 604: P-CSCF根据自身配置的本地策略， 选择 CS域或 IMS域 作为 UE重新发起紧急呼叫的网络域。
步骤 605: P-CSCF将指示重新发起 CS域或 IMS域紧急呼叫的指示 信息携带在会话拒绝消息中发送给 UE, 转至步驟 610。
步骤 606: P-CSCF将 UE发来的会话请求消息转发给服务呼叫会话 控制功能实体（S-CSCF )。
步骤 607: S-CSCF收到会话请求消息后， 判断该会话请求消息携带 的号码或 URI是否与自身配置的紧急号码或紧急 URI匹配，若是，执行 步骤 608; 否则， 按照普通会话流程建立本次会话， 本流程结束。
步驟 608: S-CSCF根据自身配置的本地策略，选择 CS域或 IMS域 作为 UE重新发起紧急呼叫的网络域。 步驟 609: S-CSCF将指示重新发起 CS域或 IMS域紧急呼叫的指示 信息携带在会话拒绝消息中通过 P-CSCF发送给 UE, 转至步骤.610。
步骤 610: UE收到会话拒绝消息后，根据该会话拒绝消息携带的指 示重新发起 CS域或 IMS域紧急呼叫的指示信息，重新发起 CS域或 IMS 域的紧急呼叫。
图 7为本发明提供的紧急呼叫的***框图， 如图 7所示， 其主要包 括 UE71和 CSCF72, 且， CSCF72包括紧急呼叫判断单元 721和紧急呼 叫域选择单元 722, 其中，
UE71: 用于向紧急呼叫判断单元 721发送会话请求消息，在收到紧 急呼叫域选择单元 722发来的会话拒绝消息后， 根据该会话拒绝消息携 带的指示重新发起 CS域或 IMS域紧急呼叫的指示信息， 重新发起 CS 域或 IMS域的紧急呼叫。
紧急呼叫判断单元 721 : 用于在判定 UE71发来的未携带紧急标识 的会话请求为紧急会话请求后， 向紧急呼叫域选择单元 722转发该 UE 发来的会话请求消息。
紧急呼叫域选择单元 722: 用于在收到紧急呼叫判断单元 721发来 的会话请求消息后， 根据自身配置的本地策略， 选择电路 CS域或 IMS 域作为 UE重新发起紧急呼叫的网络域，并将指示重新发起 CS域或 IMS 域紧急呼叫的指示信息携带在会话拒绝消息中发送给 UE71。
具体地， CSCF可为 P-CSCF。
图 8为本发明提供的紧急呼叫的具体实施例的***框图， 如图 8所 示，其主要包括 UE71和 CSCF72,且， CSCF72包括 P-CSCF和 S-CSCF, P-CSCF 包括： 紧急呼叫判断单元 721 和紧急呼叫域选择单元 722, S-CSCF包括： 笫二紧急呼叫判断单元 7212和第二紧急呼叫域选择单元 7222其中， UE71:用于向 P-CSCF的紧急呼叫判断单元 721发送会话请求消息， 在收到 P-CSCF的紧急呼叫域选择单元 722或 S-CSCF的第二紧急呼叫 域选择单元 7222发来的会话拒绝消息后， 根据该会话拒绝消息携带的 指示重新发起 CS域或 IMS域紧急呼叫的指示信息， 重新发起 CS域或 IMS域的紧急呼叫。
紧急呼叫判断单元 721 : 用于在判定 UE71发来的未携带紧急标识 的会话请求为紧急会话请求后， 向紧急呼叫域选择单元 722转发该 UE 发来的会话请求消息； 在判定 UE71发来的未携带紧急标识的会话请求 不为紧急会话请求后，向 S-CSCF的第二紧急呼叫判断单元 7212转发该 UE发来的会话请求消息。
紧急呼叫域选择单元 722: 用于在收到紧急呼叫判断单元 721发来 的会话请求消息后， 根据自身配置的本地策略， 选择电路 CS域或 IMS 域作为 UE重新发起紧急呼叫的网络域，并将指示重新发起 CS域或 IMS 域紧急呼叫的指示信息携带在会话拒绝消息中发送给 UE71。
第二紧急呼叫判断单元 7212: 用于在判定 P-CSCF的紧急呼叫判断 单元 721 发来的未携带紧急标识的会话请求为紧急会话请求后， 向 S-CSCF的第二紧急呼叫域选择单元 7222转发该会话请求消息。
第二紧急呼叫域选择单元 7222: 用于在收到 S-CSCF的第二紧急呼 叫判断单元 7212发来的会话请求消息后， 根据自身配置的本地策略， 选择电路 CS域或 MS域作为 UE重新发起紧急呼叫的网络域， 并将指 示重新发起 CS域或 IMS域紧急呼叫的指示信息携带在会话拒绝消息中 发送给 UE71。

Claims

权利要求书
1、 一种紧急呼叫方法， 其特征在于， 该方法包括：
呼叫会话控制功能实体 CSCF检测到用户终端 UE发来的会话请求 为紧急会话请求， 根据本地策略， 将指示重新发起紧急呼叫的信息携带 在会话拒绝消息中发送给 UE; UE根据所述指示信息， 重新发起电路 CS域或 IP多媒体子*** IMS域的紧急呼叫。
2、 如权利要求 1 所述的方法， 其特征在于， 所述会话请求为未携 带紧急标识的会话请求。
3、 如权利要求 1所述的方法， 其特征在于， 所述 UE根据所述指示 信息， 重新发起 CS域或 IMS域的紧急呼叫包括： 若 UE检测到该会话 拒绝消息指示重新发起 CS域的紧急呼叫，则重新发起 CS域的紧急呼叫； 若 UE检测到该会话拒绝消息指示重新发起 IMS域的紧急呼叫， 则重新 发起 IMS域的紧急呼叫。
4、 如权利要求 1 所述的方法， 其特征在于， 所述会话拒绝消息为 会话初始化协议 SIP中定义的 380响应消息，
且 380响应消息的重选服务参数包含的类型参数的取值为： 指示发 起 CS域紧急呼叫的"紧急"或指示发起 IMS域紧急呼叫的" IMS紧急"。
5、如权利要求 1所述的方法，其特征在于，所述 CSCF为代理 CSCF。
6、 如权利要求 5所述的方法， 其特征在于， 所述方法进一步包括： 代理 CSCF收到 UE发来的会话请求消息后， 检测到该会话请求不为紧 急会话请求， 将 UE发来的会话请求消息转发给服务 CSCF, 服务 CSCF 收到该会话请求消息后， 检测到该会话请求为紧急会话请求， 则根据本 地策略， 将指示重新发起紧急呼叫的信息携带在会话拒绝消息中发送给 UE, UE根据所述指示信息， 重新发起 CS域或 IMS域的紧急呼叫。
7、如权利要求 6所述的方法， 其特征在于， 所述服务 CSCF根据本 地策略， 将指示重新发起紧急呼叫的信息携带在会话拒绝消息中包括： 服务 CSCF检测到该本地策略为网絡侧同时支持 CS域和 IMS域的紧急 呼叫， 则根据 CS域和 IMS域的优先级， 选定优先级高的域作为 UE重 新发起紧急呼叫的网络域， 将指示重新发起所选定的域的紧急呼叫的信 息携带在会话拒绝消息中。
8、如权利要求 1所述的方法， 其特征在于， 所述 CSCF根据本地策 略，将指示重新发起紧急呼叫的信息携带在会话拒绝消息中包括： CSCF 检测到该本地策略为网络侧同时支持 CS域和 IMS域的紧急会话， 则根 据 CS域和 IMS域的优先级， 选定优先级高的域作为 UE重新发起紧急 呼叫的网络域， 将指示重新发起所选定的域的紧急呼叫的信息携带在会 话拒绝消息中。
9、 如权利要求 1 所述的方法， 其特征在于， 当所述指示重新发起 紧急呼叫的信息指示重新发起 IMS域的紧急呼叫时， 所述 UE重新发起 紧急呼叫包括：
UE向代理 CSCF发送携带紧急标识的紧急会话请求消息， 之后代 理 CSCF将该紧急会话请求消息发送给紧急 CSCF, 紧急 CSCF收到该 紧急会话请求消息后 , 将该紧急会话请求消息转发给对应的紧急呼叫中 心 PSAP, PSAP收到紧急会话请求消息后，通过紧急 CSCF、代理 CSCF 向 UE返回响应消息， 之后 UE通过代理 CSCF、 紧急 CSCF向 PSAP发 送响应确认消息， PSAP收到该响应确认消息后， 本次紧急会话建立。
10、 一种紧急呼叫***， 其特征在于， 该***包括： UE和 CSCF, 且， CSCF包括： 紧急呼叫判断单元和紧急呼叫域选择单元， 其中，
UE, 用于向紧急呼叫判断单元发起会话请求， 并根据紧急呼叫域选 择单元发来的会话拒绝消息重新发起 CS域或 IMS域的紧急呼叫； 紧急呼叫判断单元， 用于在判定 UE发起的会话请求为紧急会话请 求后， 向紧急呼叫域选择单元转发 UE发来的会话请求；
紧急呼叫域选择单元， 用于在收到紧急呼叫判断单元发来的会话请 求后， 根据本地策略， 将指示重新发起紧急呼叫的信息携带在会话拒绝 消息中发送给 UE。
11、如权利要求 10所述的***，其特征在于，所述 CSCF为 P-CSCF。
12、 如权利要求 10所述的***， 其特征在于， 所述 CSCF包括： P-CSCF和 S-CSCF, 所述紧急呼叫判断单元和紧急呼叫域选择单元位于 P-CSCF中，且所述 S-CSCF包括： 第二紧急呼叫判断单元和第二紧急呼 叫域选择单元， 其中，
所述紧急呼叫判断单元进一步用于在判定 UE发起的会话请求不为 紧急会话请求后， 向 S-CSCF的第二紧急呼叫判断单元转发 UE发来的 会话请求；
第二紧急呼叫判断单元， 用于在判定 P-CSCF的紧急呼叫判断单元 发来的会话请求为紧急会话请求后， 向 S-CSCF的第二紧急呼叫域选择 单元转发该会话请求；
第二紧急呼叫域选择单元， 用于在收到 S-CSCF的第二紧急呼叫判 断单元发来的会话请求后， 根据本地策略， 将指示重新发起紧急呼叫的 信息携带在会话拒绝消息中发送给 UE。
PCT/CN2007/000693 2006-03-03 2007-03-05 Procédé et système d'appel d'urgence WO2007098713A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US12/203,538 US20100014508A1 (en) 2006-03-03 2008-09-03 Method And System For Emergency Call

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200610058358.5 2006-03-03
CN200610058358A CN100579278C (zh) 2006-03-03 2006-03-03 紧急呼叫方法、***及呼叫会话控制功能实体

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US12/203,538 Continuation US20100014508A1 (en) 2006-03-03 2008-09-03 Method And System For Emergency Call

Publications (1)

Publication Number Publication Date
WO2007098713A1 true WO2007098713A1 (fr) 2007-09-07

Family

ID=38458678

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2007/000693 WO2007098713A1 (fr) 2006-03-03 2007-03-05 Procédé et système d'appel d'urgence

Country Status (3)

Country Link
US (1) US20100014508A1 (zh)
CN (2) CN100579278C (zh)
WO (1) WO2007098713A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2010130088A1 (zh) * 2009-05-12 2010-11-18 华为技术有限公司 一种网络选择的方法及装置

Families Citing this family (37)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2218242B1 (en) * 2007-10-27 2019-09-11 BlackBerry Limited Content disposition system and method for processing message content in a distributed environment
CN101227720B (zh) * 2008-01-09 2012-05-09 中兴通讯股份有限公司 一种ip多媒体子***的本地转出控制方法
CN101911773B (zh) * 2008-01-16 2013-12-04 阿尔卡特朗讯美国公司 用于有限目的的接入网络
CN101222763B (zh) * 2008-01-21 2012-02-29 中兴通讯股份有限公司 一种用户设备漫游情况下媒体路由选择的方法
CN101227648B (zh) * 2008-02-13 2012-01-11 中兴通讯股份有限公司 Ip多媒体子***紧急呼叫业务的实现方法
CN101568091B (zh) * 2008-04-24 2011-02-02 华为技术有限公司 一种提供业务的方法、***和设备
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
GB2463230A (en) * 2008-08-28 2010-03-10 Nec Corp Provision of emergency call service in a cellular communication system
CN101577888B (zh) * 2008-11-06 2011-12-07 中兴通讯股份有限公司 Ip多媒体子***紧急呼叫的切换方法和基站
CN101742454B (zh) * 2008-11-26 2012-10-17 华为技术有限公司 一种移动受限终端紧急业务的管理方法、装置与***
US8265022B2 (en) * 2009-02-10 2012-09-11 Apple Inc. Apparatus and methods for transmission of emergency call data over wireless networks
WO2010124443A1 (zh) * 2009-04-27 2010-11-04 华为技术有限公司 支持多级受限模式紧急呼叫的方法、装置和***
EP2449825B1 (en) * 2009-06-29 2016-12-07 BlackBerry Limited System and methods for accessing voice services based on voice service indicators in an evolved packet system
US10313400B2 (en) * 2009-06-30 2019-06-04 3G Licensing S.A. Method of selecting a network resource
US20110014892A1 (en) * 2009-07-17 2011-01-20 Peter Hedman Network-Assisted Initiation of Emergency Calls from a Multi-Mode Wireless Communication Device
US9560509B2 (en) * 2009-11-02 2017-01-31 Telefonaktiebolaget Lm Ericsson (Publ) Emergency signalling in an IP multimedia subsystem network
CN102256227B (zh) * 2010-05-18 2016-03-30 中兴通讯股份有限公司 紧急消息的实现方法、装置及***
GB2481395A (en) * 2010-06-21 2011-12-28 Nec Casio Mobile Comm Ltd Call set-up management in a mobile radio communications network
US8867411B2 (en) * 2011-02-03 2014-10-21 T-Mobile Usa, Inc. Emergency call mode preference in wireless communication networks
EP2848074B1 (en) * 2012-05-09 2016-04-06 Telefonaktiebolaget LM Ericsson (publ) Handling communication sessions in a communications network
CN103812757A (zh) * 2012-11-13 2014-05-21 中兴通讯股份有限公司 一种实时通信的浏览器紧急呼叫方法、***和移动装置
US9426833B2 (en) * 2013-03-01 2016-08-23 T-Mobile Usa, Inc. Systems and methods for emergency call route failover
US9814081B2 (en) 2013-08-02 2017-11-07 Mediatek Inc. Methods for processing emergency call and communications apparatuses utilizing the same
US9380609B2 (en) * 2013-08-28 2016-06-28 Qualcomm Incorporated Method and apparatus for processing emergency calls
WO2016081098A1 (en) * 2014-11-17 2016-05-26 Intel IP Corporation An apparatus and method for network assisted domain selection
EP3073771B1 (en) * 2015-03-26 2020-06-17 Deutsche Telekom AG Method for improved handling of emergency calls in a roaming scenario and corresponding system, computer program and computer-readable medium
JP6940592B2 (ja) * 2017-03-28 2021-09-29 京セラ株式会社 無線通信機器およびその制御方法
CN107172605B (zh) * 2017-06-14 2020-03-31 努比亚技术有限公司 一种紧急呼叫方法、移动终端及计算机可读存储介质
CN109257512B (zh) * 2017-07-13 2022-03-04 中兴通讯股份有限公司 一种呼叫前转方法、装置及计算机可读存储介质
EP4184890A1 (en) 2017-12-29 2023-05-24 BlackBerry Limited Methods and systems for provisioning emergency numbers
CN108391262A (zh) * 2018-02-09 2018-08-10 上海京颐科技股份有限公司 紧急呼叫方法、装置、***以及电子设备
US20210258763A1 (en) * 2018-07-03 2021-08-19 Deutsche Telekom Ag Method for improved handling of ip multimedia subsystem calls in a home mobile communication network and a visited mobile communication network
CN111328062A (zh) * 2018-12-14 2020-06-23 ***通信集团河南有限公司 一种VoLTE紧急电话的接通方法和装置
US10805982B1 (en) * 2019-04-29 2020-10-13 Blackberry Limited Supported extended emergency information type
US11770710B2 (en) * 2019-09-13 2023-09-26 Intel Corporation Man in the middle attack detection using operating channel validation under protected beacon
CN110972125A (zh) * 2019-11-27 2020-04-07 惠州Tcl移动通信有限公司 呼叫的方法、装置、存储介质以及终端
CN116601933A (zh) * 2020-12-04 2023-08-15 宇龙计算机通信科技(深圳)有限公司 紧急呼叫方法、装置、存储介质以及终端

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2003009627A1 (en) * 2001-04-27 2003-01-30 Nokia Corporation Method and system for handling a network-identified emergency session
WO2003094563A1 (en) * 2002-05-06 2003-11-13 Nokia Corporation System and method for handling sessions of specific type in communication networks
KR20040090023A (ko) * 2003-04-16 2004-10-22 에스케이 텔레콤주식회사 Ｉｍｔ-2000 ｉｍｓ망에서의 비상호 서비스 제공방법

Family Cites Families (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7623447B1 (en) * 2000-04-10 2009-11-24 Nokia Corporation Telephony services in mobile IP networks
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
WO2002082729A1 (en) * 2001-04-04 2002-10-17 Nokia Corporation Tracing method and system
CN100521813C (zh) * 2001-04-27 2009-07-29 诺基亚公司 处理网络识别紧急会话的方法和***
WO2002089515A1 (en) * 2001-04-27 2002-11-07 Nokia Corporation Method and system for enabling emergency sessions to be established in abnormal cases
US7031706B2 (en) * 2001-08-21 2006-04-18 Nokia Corporation Internet protocol (IP) multimedia subsystem (IMS) availability detection
CN1155181C (zh) * 2001-10-09 2004-06-23 华为技术有限公司 一种基于移动台位置的用户业务限制方法
US7533160B2 (en) * 2003-02-18 2009-05-12 Qualcomm Incorporated Provisioning server information in a mobile station
US7359373B2 (en) * 2003-10-17 2008-04-15 Nokia Corporation System, apparatus, and method for establishing circuit-switched communications via packet-switched network signaling
US7184746B2 (en) * 2004-07-13 2007-02-27 Lucent Technologies Inc. Method and apparatus for providing network support for a wireless emergency call
WO2006114120A1 (en) * 2005-04-27 2006-11-02 Telefonaktiebolaget Lm Ericsson (Publ) Service routing decision entity
WO2007045266A1 (en) * 2005-10-21 2007-04-26 Telefonaktiebolaget Lm Ericsson (Publ) System and method for selecting a subsystem for call termination
US20070121642A1 (en) * 2005-11-02 2007-05-31 Battin Robert D Method and system for supporting an emergency call

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2003009627A1 (en) * 2001-04-27 2003-01-30 Nokia Corporation Method and system for handling a network-identified emergency session
WO2003094563A1 (en) * 2002-05-06 2003-11-13 Nokia Corporation System and method for handling sessions of specific type in communication networks
KR20040090023A (ko) * 2003-04-16 2004-10-22 에스케이 텔레콤주식회사 Ｉｍｔ-2000 ｉｍｓ망에서의 비상호 서비스 제공방법

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2010130088A1 (zh) * 2009-05-12 2010-11-18 华为技术有限公司 一种网络选择的方法及装置

Also Published As

Publication number Publication date
CN101317492A (zh) 2008-12-03
CN101031135A (zh) 2007-09-05
US20100014508A1 (en) 2010-01-21
CN100579278C (zh) 2010-01-06

Similar Documents

Publication Publication Date Title
WO2007098713A1 (fr) Procédé et système d'appel d'urgence
EP1386509B1 (en) User equipment, network element, and method and communication system for establishing an emergency session
AU2011374206B2 (en) Methods and apparatuses for enabling an Single Radio Voice Call Continuity (SRVCC) access transfer of an emergency call back session
US10044553B2 (en) Media resource reservation request failure handling for voice over mobile wireless network
EP2160910B1 (en) Enabling ue access domain selection for terminated speech/video calls
US20110076982A1 (en) Emergency calls for internet protocol multimedia subsystem (ims) over packet switched code division multiple access (cdma) networks
EP2487840B1 (en) User equipment and method for performing an ims session
JP5255123B2 (ja) 通信ネットワークにおいてセッションを確立する方法
WO2008011833A1 (fr) Procédé et système permettant d'établir un appel d'urgence et p-cscf
AU2001258380A1 (en) Method and system for handling a network-identified emergency session
WO2008028416A1 (fr) Procédé de commande de transfert intercellulaire d'appel et système de communication mettant en oeuvre ce procédé et dispositif utilisateur
WO2008046319A1 (fr) Procédé et système pour assurer la continuité d'un appel vocal lors de la gestion d'une affaire urgente
WO2007025450A1 (fr) Methode pour realiser un declenchement d'inscription d'utilisateur dans un sous-systeme multimedia ip
EP2257103A1 (en) A method, system and device for service providing
WO2009100638A1 (zh) Ip多媒体子***紧急呼叫业务的实现方法及p-cscf
WO2009015525A1 (en) A method for switching the session control path of ip multimedia core network subsystem centralized service
EP2117251B1 (en) Realizing method of emergency call registration
WO2009024006A1 (fr) Contrôleur de session locale, sous-système multimédia ip et procédé d'enregistrement de session
JP2010515311A (ja) パケット交換ドメインの状態を変化させるための方法、端末及びネットワークデバイス
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
WO2007014511A1 (fr) Procédé, système et fonction de contrôle d’accès pour tester le service émergent
WO2008110110A1 (fr) Procédé et système de fourniture de service de sous-système multimédia ip
EP2173085B1 (en) A method for realizing user decision user busy forwarding

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 200780000322.4

Country of ref document: CN

121 Ep: the epo has been informed by wipo that ep was designated in this application
NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 07720318

Country of ref document: EP

Kind code of ref document: A1