WO2011017978A1 - Method and apparatus for call management in internet protocol multimedia subsystem - Google Patents

Method and apparatus for call management in internet protocol multimedia subsystem Download PDF

Info

Publication number
WO2011017978A1
WO2011017978A1 PCT/CN2010/074099 CN2010074099W WO2011017978A1 WO 2011017978 A1 WO2011017978 A1 WO 2011017978A1 CN 2010074099 W CN2010074099 W CN 2010074099W WO 2011017978 A1 WO2011017978 A1 WO 2011017978A1
Authority
WO
WIPO (PCT)
Prior art keywords
call
message
control function
session
function entity
Prior art date
Application number
PCT/CN2010/074099
Other languages
French (fr)
Chinese (zh)
Inventor
任鹏
田利荣
苏登军
Original Assignee
中兴通讯股份有限公司
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 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2011017978A1 publication Critical patent/WO2011017978A1/en

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/40Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10Architectures or entities
    • H04L65/1016IP multimedia subsystem [IMS]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10Architectures or entities
    • H04L65/1045Proxies, e.g. for session initiation protocol [SIP]

Definitions

  • the present invention relates to the field of communications, and in particular to a call management method and apparatus for an IP multimedia subsystem. Background technique
  • the IP Multimedia Subsystem provides call services.
  • the IMS call uses the Session Initiation Protocol (SIP) as the control signaling protocol in the control layer.
  • SIP defines a call detection mechanism in RFC4028, that is, the terminal supporting RFC4028 periodically sends the session request.
  • a message (re-INVITE, also known as a call request message) or a session refresh request message (UPDATE) is used to maintain the activity of the session.
  • the time interval of the session refresh request message is determined by the negotiation mechanism of RFC4028. If the session refresh request message is not received within the interval, the session is considered to have been terminated, the terminal will send a session release message (BYE, also referred to as an end session message), and the stateful proxy server removes all states of the call. .
  • BYE session release message
  • FIG. 1 is a schematic diagram of a SIP control message for an IMS call, including the following network elements: Calling User Equipment UE-A (User Equipment A) 101, Calling Agent Call Session Control Function Entity P-CSCF-A (Proxy Call Session) Control Function A) 102, the calling call session control function entity S-CSCF-A (Serving Call Session Control Function A) 103, the query call session control function entity I-CSCF (Interrogating Call Session Control Function) 104, The called call session control function entity S-CSCF-B (Serving Call Session Control function B) 105, the called proxy call session control function entity P-CSCF-B (Proxy Call Session B) 106 and the called user equipment UE-B ( User Equipment B ) 107.
  • Calling User Equipment UE-A User Equipment A
  • P-CSCF-A Calling Agent Call Session Control Function Entity
  • P-CSCF-A Proxy Call Session Control Function A
  • Step 201 UE-A sends a session request message to initiate a call, where UE-A supports RFC4028 call detection mechanism, this message contains session timeout (such as setting the session timeout time to 1800 seconds) and session refresh negotiation parameters (such as setting UE-A as the refresher and caller);
  • Step 202 The P-CSCF-A receives the session request message, and learns that the calling party UE-A supports the call detection mechanism of the RFC 4028, and forwards the session request message to the serving call session control point S-CSCF-A of the user;
  • the S-CSCF-A receives the session request message, and learns that the calling party UE-A supports the call detection mechanism of the RFC 4028, and forwards the session request message to the I-CSCF to find the called S-CSCF;
  • Step 204 the I-CSCF will session The request message is sent to the called S-CSCF
  • Step 205 The S-CSCF-B learns that the calling party UE-A supports the call detection mechanism of the RFC 4028, and sends a session request message to the P-CSCF-B.
  • Step 206 The P-CSCF-B learns that the calling party UE-A supports the call detection mechanism of the RFC 4028, and sends a session request message to the UE-B.
  • step 207 the UE-B receives the session request message, where the UE-B also supports the RFC 4028.
  • the call detection mechanism, UE-B will update the negotiation parameters through the session in the message, determine the refresher and session timeout time, and send the negotiated session request response message;
  • Step 208 P-CSCF-B sets according to the session request response message Session timeout, forwarding session request response message;
  • Step 209 SC The SCF-B sets the session timeout time according to the session request response message, and forwards the session request response message.
  • Step 210 The I-CSCF forwards the session request response message, and releases the jt call resource because it does not participate in the subsequent session;
  • Step 211, S-CSCF- The session timeout time is set according to the session request response message, and the session request response message is forwarded.
  • Step 212 The P-CSCF-A sets the session timeout time according to the session request response message, forwards the session request response message, and starts the timeout timer to start timing.
  • Step 213 - 217 UE-A obtains the refresher and the session timeout time from the session response, UE-A sends a session confirmation message, and the session confirmation message arrives at UE-B through each IMS network element;
  • the IMS network element receiving the session refresh request message updates the session timeout time, that is, restarts the startup timeout timer to restart the timing;
  • Steps 223-227, UE-B sends a session refresh response message, and the session refresh response message
  • the IMS network element arrives at the UE-A;
  • the step 4 is 228, and the UE-A is abnormally dead;
  • Step 229 the UE-B does
  • the SIP session timeout time of the RFC 4028 is determined by the UE-A and UE-B that support the protocol. If the session time expires due to the network or the terminal, the S-CSCF, the P-CSCF, and the UE on the session path respectively perform the release call process to release the local resources.
  • the inventor has found that the call management method in the related art relies on the support of the RFC4028 call detection mechanism by both terminals. When both terminals of the call do not support the RFC4028 call detection mechanism, both terminals cannot initiate a session refresh request message to initiate call detection.
  • the present invention is directed to a call management method and apparatus for an IP multimedia subsystem, which can solve the call management method in the related art, which relies on the support of the terminal for the RFC4028 call detection mechanism, and is not supported by both parties of the call.
  • the RFC4028 call detection mechanism is used, both terminals cannot initiate a session refresh request message to initiate call detection.
  • a call management method for an IP multimedia subsystem including the following steps: establishing a call of an IP multimedia subsystem between a calling terminal and a called terminal; proxy call session The control function entity sends a status detection request to its corresponding terminal; if the detection result As an exception, the network element of the IP Multimedia Subsystem is notified to release the call.
  • the establishing an IP multimedia subsystem call between the calling terminal and the called terminal comprises: the calling terminal sending a session request message to the called terminal; and the called terminal according to the received session request message Sending a session request response message; the proxy call session control function entity sets a detection duration according to the session request response message, and starts timing, and the proxy call session control function entity includes a calling proxy call session control function entity and a called proxy call session control function entity; The calling terminal sends a session confirmation message to the called terminal.
  • the proxy call session control function entity sends a status detection request to its corresponding terminal, including: the calling proxy call session control function entity sends a selection OPTIONS to the calling terminal when the detection time is half of the detection duration (Capability Query) message; The called proxy call session control function entity sends an OPTIONS message to the called terminal when it reaches half of the detection duration.
  • the detection result is abnormal: the calling proxy call session control function entity does not receive the OPTIONS response message within the detection duration.
  • the detection result is abnormal: the calling proxy call session control function entity receives the OPTIONS response message, and the response code of the OPTIONS response message is 481.
  • the network element that notifies the IP multimedia subsystem releases the call includes: the calling agent call session control function entity releases the call, and sends an end session message to the called terminal; the intermediate network of the IP multimedia subsystem The meta and the called terminal release the call according to the end session message.
  • the method further includes: if the calling proxy call session control function entity receives the OPTIONS response message, and the response code of the OPTIONS response message is not 481, the calling proxy call session control function entity restarts timing .
  • the detection result is abnormal: the called proxy call session control function entity does not receive the OPTIONS response message from the called terminal within the detection duration.
  • the detection result is abnormal: the called proxy call session control function entity receives an OPTIONS response message from the called terminal, and the response code of the OPTIONS response message is 481.
  • the network element notifying the IP multimedia subsystem to release the call includes: the called proxy call session control function entity releases the call, and sends an end session message to the calling terminal; the intermediate network of the IP multimedia subsystem The meta and the calling terminal release the call according to the end session message.
  • the method further includes: if the called proxy call session control function entity receives the OPTIONS response message, and the response code of the OPTIONS response message is not 481, the called proxy call session control function entity restarts timing .
  • a call management apparatus for an IP multimedia subsystem including: an establishing module, configured to establish an IP multimedia subsystem between a calling terminal and a called terminal.
  • the detecting module is configured to send a status detection request to the corresponding terminal by the proxy call session control function entity, and the release module is configured to notify the network element of the IP multimedia subsystem to release the call when the detection result is abnormal.
  • the foregoing embodiment sends a status detection request to the terminal at both ends of the call to detect the session survival state of the terminal, and notifies the network element of the IP multimedia subsystem to release the current when the detection result is abnormal.
  • the call management method in the related art relies on the terminal to the RFC4028 call.
  • the detection mechanism when both terminals of the calling party do not support the RFC4028 call detection mechanism, both terminals cannot initiate a session refresh request message to initiate call detection. In the event of a failure, the terminal and the S-CSCF, P-CSCF, etc.
  • FIG. 1 is a schematic diagram showing a SIP control message of an IMS call
  • FIG. 2 is a flowchart showing a call management method in the related art
  • 3 is a flow chart showing a call management method according to a first embodiment of the present invention
  • FIG. 4 is a flow chart showing a call management method according to a second embodiment of the present invention
  • FIG. 5 is a third embodiment of the present invention.
  • FIG. 3 is a flowchart of a call management method according to a first embodiment of the present invention.
  • the method includes the following steps: Step 4: 301, establishing an IMS call between the calling terminal and the called terminal; Step 302, The proxy call session control function entity P-CSCF sends a status detection request to its corresponding terminal. Step 303: If the detection result is abnormal, notify the IMS network element to release the call. After the IMS call is established, the IMS network sends a state detection request to the calling terminal and the called terminal at both ends of the call to detect the session survival state of the terminal, and notifies the IMS network element to release the current call when the detection result is abnormal.
  • the call management method in the related art relies on the terminal to the RFC4028 call detection mechanism.
  • the terminal and the IMS intermediate network element such as S-CSCF and P-CSCF will be caused.
  • the session resources are hanged, resulting in a problem of low processing power and utilization of the IMS network element and poor user experience, thereby improving the processing of the IMS network element when the call terminals do not support the RFC4028 call detection mechanism.
  • step 301 includes: the calling terminal UE-A sends a session request message to the called terminal UE-B; the UE-B sends a session request response message according to the received session request message;
  • the session control function entity P-CSCF sets the detection duration T according to the session request response message, and starts timing.
  • the P-CSCF includes a calling proxy call session control function entity P-CSCF-A and a called proxy call session control function entity P-CSCF.
  • UE-A sends a session confirmation message to UE-B.
  • step 302 includes: P-CSCF-A sends an OPTIONS message to UE-A when it reaches half of the detection duration (T/2); when P-CSCF-B is at T/2 , Send an OPTIONS message to UE-B.
  • the P-CSCF-A and the P-CSCF-B respectively send an OPTIONS message to their respective terminals UE-A and UE-B when they are timed to T/2, wherein the OPTIONS message is initiated by the P-CSCF.
  • the OPTIONS message is sent to initiate call detection, so that the call detection can be performed to know the current session survival state regardless of whether the terminal supports the RFC4028 call detection mechanism, and the UE does not support the RFC4028 call. IMS network element processing capability and utilization when detecting mechanisms.
  • the detection result is abnormal: the P-CSCF-A does not receive the OPTIONS response message within the detection duration T.
  • the P-CSCF-A in this embodiment does not receive the OPTIONS response message within the detection duration T.
  • the detection result is abnormal, and the reason that the timeout is not received may be due to the UE-A abnormal crash and the inability to respond to the reception.
  • the OPTIONS message may also be due to the network failure causing the transmission of the OPTIONS response message to time out.
  • the abnormal detection of the call is easily implemented, which is beneficial to the targeted processing of the abnormal situation.
  • the detection result is abnormal: the P-CSCF-A receives the OPTIONS response message, and the response code of the OPTIONS response message is 481.
  • the P-CSCF-A in this embodiment receives the OPTIONS response message, but the response code carried in the OPTIONS response message is 481. At this time, the detection result is abnormal, and the response code 481 indicates that the session does not exist. The reason may be due to The abnormal restart of the UE-A causes the session to be incorrectly recognized. In this way, the abnormal detection of the call is easily implemented, which facilitates the targeted processing of the abnormal situation.
  • the network element that notifies the IMS to release the call specifically includes: the P-CSCF-A releases the call, and sends an end session message to the UE-B; the IMS intermediate network element and the UE-B according to the end session message Release the call.
  • the P-CSCF-A if the P-CSCF-A does not receive the OPTIONS response message due to the timeout or receives the OPTIONS response message with the response code of 481, the detection result is abnormal, and the P-CSCF-A first releases the local call resource. Then, the end session message is sent to the UE-B to notify the UE-B and other IMS intermediate network elements to release the call. Finally, the IMS intermediate network element and the UE-B release the call according to the end session message, and the P-CSCF is determined because the call is abnormal. -A is based on whether the OPTIONS response message and its response code are received.
  • the end session message is directly initiated by the P-CSCF-A in this embodiment, so that the current call is abnormal, and the UE-B and the IMS are in the middle.
  • the network element is released in time for more efficient use, avoiding the phenomenon that the data area hangs due to the terminal and the IMS intermediate network element are not released.
  • the method further includes: if the P-CSCF-A receives the OPTIONS response message, and the response code of the OPTIONS response message is not 481, the P-CSCF-A restarts timing.
  • the P-CSCF-A in this embodiment receives the OPTIONS response message, and the response code of the OPTIONS response message is not 481.
  • FIG. 4 is a flowchart of a call management method according to a second embodiment of the present invention.
  • the call parties UE-A and UE-B in this embodiment do not support the RFC 4028 session refresh mechanism.
  • the method includes the following steps: Step 401: UE-A sends a session request message to initiate a call, where the session request message does not include a flag supporting RFC 4028.
  • Step 403 The S-CSCF-A receives the session request message, and learns that the calling party UE-A does not support the call detection mechanism of the RFC 4028, and the session is The request message is forwarded to the I-CSCF to find the called S-CSCF; Step 404, the I-CSCF sends a session request message to the called S-CSCF-B; Step 405, the S-CSCF-B learns the calling party UE- A does not support the call detection mechanism of RFC4028, and sends a session request message to P-CSCF-B; Step 406: The P-CSCF-B learns that the calling party UE-A does not support the RFC4028 detection mechanism, and sends a session request message to the UE-B.
  • step 407 the UE-B receives the session request message, because the UE-B does not. Supporting the call detection mechanism of RFC4028, the session request response message is directly sent.
  • Step 408 The P-CSCF-B receives the session request response message, and learns that the calling and the called UE do not support the call detection mechanism of the RFC 4028, and responds according to the session request.
  • the message sets the timeout period of the local timeout timer to be the detection time length T, and starts the timeout timer;
  • Step 409 the P-CSCF-B forwards the session request response message;
  • Step 410 the S-CSCF-B receives the session request response message, and Sending it to the I-CSCF, because there is no negotiation parameter of the RFC4028 in the message, the timeout timer is not started;
  • Step 411 the I-CSCF forwards the session request response message to the S-CSCF-A;
  • Step 412, S-CSCF- A receives the session request response message and forwards it to the P-CSCF-A. Since there is no negotiation parameter of the RFC 4028 in the message, the timeout timer is not started.
  • Step 413 the P-CSCF-A receives the session request response message, and learns The primary and secondary UEs do not support RFC.
  • the call detection mechanism of the 4028 sets the timeout period of the local timeout timer to the detection duration T, and starts the timeout timer;
  • Step 414 the P-CSCF-A forwards the response to the UE-A;
  • Steps 415-419 the UE-A sends The session confirmation message, the session confirmation message arrives at the UE-B through each IMS network element;
  • step 420 the P-CSCF-A sends an OPTIONS message to the UE-A at T/2;
  • Step 421, P-CSCF-A is connected) UE-A's OPTIONS response message, and the response code of the OPTIONS response message is 200, P-CSCF-A restarts the timeout timer;
  • Step 422 P-CSCF-B sends an OPTIONS message to UE-B at T/2
  • Step 423 P-CSCF-
  • the P-CSCF-A sends an OPTIONS message to the UE-A at the time of T/2.
  • the UE-A restarts, and therefore does not match the pre-restart session information carried in the OPTIONS message received at this time.
  • the UE-A sends an OPTIONS response message to the P-CSCF-A, but the response code is 481, indicating that the session does not exist.
  • Step 427 after receiving the OPTION 481 response message in the session, the P-CSCF-A releases the session resource and sends the session resource.
  • Steps 428-430 the IMS intermediate network element receives the end session message, releases the call resource, and forwards the end session message to the UE-B; Step 431, the UE-B receives the end session message, and releases Calling the resource, and sending an end session response message; Steps 432-434, the IMS network element pre-passes the end session response message to the P-CSCF-A.
  • the detection duration T is set by the P-CSCF, and the session survival state of the calling UE and the called UE is detected by the SIP OPTIONS message, instead of the call management method like the related art: by the master, the called The UE sets the call detection mechanism (steps 201 and 207), and the P-CSCF and the S-CSCF obtain and save the session timeout time from the session request response message (step 208, step 209, step 211, and step 212).
  • This embodiment reduces the requirement for the terminal, and the call detection can be implemented regardless of whether the terminal supports the RCF4028 call detection mechanism to complete the management of the call.
  • the detection result is abnormal: the P-CSCF-B does not receive the OPTIONS response message from the UE-B within the detection duration T.
  • the P-CSCF-B does not respond to the OPTIONS response message during the detection duration T.
  • the detection result is abnormal, and the reason that the timeout is not received may be due to the abnormal crash of the UE-B and the inability to respond to the reception.
  • the OPTIONS message may also be due to the network failure causing the transmission of the OPTIONS response message to time out. In this way, the abnormal detection of the call is easily implemented, which is beneficial to the targeted processing of the abnormal situation.
  • the detection result is abnormal: the P-CSCF-B receives the OPTIONS response message from the UE-B, and the response code of the OPTIONS response message is 481.
  • the P-CSCF-B in this embodiment receives the OPTIONS response message, but the response code carried in the OPTIONS response message is 481.
  • the detection result is abnormal, and the response code 481 indicates that the session does not exist.
  • the reason may be due to The abnormal restart of the UE-B causes the session to be incorrectly recognized. In this way, the abnormal detection of the call is easily implemented, which facilitates the targeted processing of the abnormal situation.
  • the network element that notifies the IMS to release the call specifically includes: the P-CSCF-B releases the call, and sends an end session message to the UE-A; the IMS intermediate network element and the UE-A according to the end session message Release the call.
  • the P-CSCF-B does not receive the OPTIONS response message due to the timeout or receives the OPTIONS response message with the response code of 481
  • the detection result is abnormal
  • the P-CSCF-B first releases the local call resource.
  • the end session message is sent to the UE-A to notify the UE-A and other IMS intermediate network elements to release the call.
  • the IMS intermediate network element and the UE-A release the call according to the end session message, and the P-CSCF is determined because the call is abnormal.
  • -B is made according to whether the OPTIONS response message and its response code are received. Therefore, the end session message is directly initiated by the P-CSCF-B in this embodiment, so that when the call is abnormal, the UE-A and the IMS are in the middle.
  • the network element is released in time for more efficient use, avoiding the phenomenon that the data area hangs due to the terminal and the IMS intermediate network element are not released.
  • the method further includes: if the P-CSCF-B receives the OPTIONS response message, and the response code of the OPTIONS response message is not 481, the P-CSCF-B restarts timing.
  • the P-CSCF-B in this embodiment receives the OPTIONS response message, and the response code of the OPTIONS response message is not 481.
  • the call is considered to be in a normal state, and the P-CSCF-B restarts the timeout timer to restart the timing and enters.
  • the next call detection cycle enables uninterrupted call detection.
  • FIG. 5 is a structural diagram of a call management apparatus according to a third embodiment of the present invention, including: an establishing module 10, configured to establish an IMS call between a calling terminal and a called terminal; and a detecting module 20, configured to proxy The call session control function entity sends a status detection request to its corresponding terminal.
  • the release module 30 is configured to notify the network element of the IP multimedia subsystem to release the call when the detection result is abnormal.
  • the IMS call setup module 10 first establishes an IMS call between the calling terminal and the called terminal, and then the proxy call session control function entity uses the detecting module 20 to send a status detection request to the corresponding terminal to survive the session of the terminal.
  • the release module 30 notifies the IMS network element to release the call when the detection result is abnormal, because the terminal initiates a request to initiate call detection, and does not need to rely on the terminal supporting the RFC4028 call detection mechanism to initiate the session.
  • the request message is refreshed. Therefore, the call management method in the related art relies on the support of the RFC4028 call detection mechanism by both terminals. When both terminals of the call do not support the RFC4028 call detection mechanism, both terminals cannot initiate a session refresh request message.
  • the session resources of the IMS intermediate network element such as the S-CSCF and the P-CSCF are suspended, resulting in lower processing capability and utilization of the IMS network element and poor user experience.
  • the problem which in turn increases the RFC4028 call in both terminals of the calling party.
  • the processing capability and utilization of the IMS network element in the case of the detection mechanism improves the user experience. From the above description, it can be seen that, in the case that the caller terminal does not support the RFC4028 call detection mechanism, the foregoing embodiment of the present invention improves the processing capability and utilization of the IMS network element, and improves the user experience.
  • the above modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices.
  • the invention is not limited to any specific combination of hardware and software.
  • the above is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the scope of the present invention are intended to be included within the scope of the present invention.

Abstract

A method and an apparatus for call management in an Internet protocol (IP) multimedia subsystem (IMS) are provided. The method includes the following steps: establishing an IMS call between a calling terminal and a called terminal (301); sending, by a proxy call session control function entity, a state detection request to its corresponding terminal (302); if the detection result is abnormal, notifying the network elements of the IMS to release the call (303). The present invention overcomes the problem of the call management method in relevant technology that the processing capability and utilization ratio of the IMS network elements are lower and user's experience is worse, which is caused when both terminals of a call do not support the Request For Comments (RFC) 4028 call detection mechanism, thus improving the processing capability and utilization of the IMS network elements under the situation that both parties of the call do not support the RFC 4028 call detection mechanization and enhancing the user's experience.

Description

用于 IP多媒体子系统的呼叫管理方法^^置 技术领域 本发明涉及通信领域, 具体而言, 涉及一种用于 IP多媒体子系统的呼叫 管理方法及装置。 背景技术  TECHNICAL FIELD The present invention relates to the field of communications, and in particular to a call management method and apparatus for an IP multimedia subsystem. Background technique
IP多媒体子系统 ( IP Multimedia Subsystem, 简称为 IMS )提供呼叫业 务。 The IP Multimedia Subsystem (IMS) provides call services.
IMS呼叫在控制层釆用会话启动协议 ( Session Initiation Protocol, 简称 为 SIP )作为控制信令的协议, SIP在 RFC4028中定义了一种呼叫检测机制, 即支持 RFC4028的终端会周期性地发送会话请求消息 (re-INVITE, 也称为 呼叫请求消息) 或会话刷新请求消息 (UPDATE ) 用来保持会话的活动。 会 话刷新请求消息的时间间隔通过 RFC4028的协商机制确定。如果在间隔内未 收到会话刷新请求消息, 则认为该会话已经被终止, 终端将发送会话释放消 息 (BYE, 也称为结束会话消息), 有状态代理服务器则将该呼叫的所有状 态移除。 图 1示出了 IMS呼叫的 SIP控制消息的示意图, 包括以下网元: 主叫用 户设备 UE-A ( User Equipment A ) 101、 主叫代理呼叫会话控制功能实体 P-CSCF-A ( Proxy Call Session Control Function A ) 102、 主叫月艮务呼叫会话 控制功能实体 S-CSCF-A ( Serving Call Session Control Function A ) 103、 查 询呼叫会话控制功能实体 I-CSCF( Interrogating Call Session Control Function ) 104、被叫服务呼叫会话控制功能实体 S-CSCF-B( Serving Call Session Control function B ) 105、 被叫代理呼叫会话控制功能实体 P-CSCF-B ( Proxy Call Session B ) 106和被叫用户设备 UE-B ( User Equipment B ) 107。 相关技术中提供了一种用于 IP多媒体子系统的呼叫管理方法,参见图 2 , 该方法包括以下步 4聚: 步骤 201 , UE-A发送会话请求消息以发起一个呼叫, 其中 UE-A 支持 RFC4028的呼叫检测机制, 此消息包含会话超时时间 (例如设置会话超时时 间为 1800秒) 和会话刷新协商参数 (例如设置 UE-A为刷新者和主叫方); 步骤 202 , P-CSCF-A接收会话请求消息,得知主叫方 UE-A支持 RFC4028 的呼叫检测机制, 将会话请求消息转发到用户的服务呼叫会话控制点 S-CSCF-A; 步骤 203 , S-CSCF-A接收会话请求消息,得知主叫方 UE-A支持 RFC4028 的呼叫检测机制, 将会话请求消息转发到 I-CSCF, 寻找被叫 S-CSCF; 步骤 204, I-CSCF将会话请求消息发送到被叫 S-CSCF-B; 步骤 205 , S-CSCF-B得知主叫方 UE-A支持 RFC4028的呼叫检测机制, 将会话请求消息发送到 P-CSCF-B; 步骤 206, P-CSCF-B得知主叫方 UE-A支持 RFC4028的呼叫检测机制, 将会话请求消息发送到 UE-B; 步骤 207, UE-B收到会话请求消息, 其中 UE-B也支持 RFC4028的呼 叫检测机制, 则 UE-B会通过消息中的会话刷新协商参数, 确定刷新者和会 话超时时间, 并发送协商后的会话请求响应消息; 步骤 208, P-CSCF-B根据会话请求响应消息设置会话超时时间, 转发会 话请求响应消息; 步骤 209, S-CSCF-B根据会话请求响应消息设置会话超时时间, 转发会 话请求响应消息; 步骤 210, I-CSCF转发会话请求响应消息, 由于不参加后续会话, 释放 jt匕次呼叫资源; 步骤 211 , S-CSCF-A根据会话请求响应消息设置会话超时时间, 转发会 话请求响应消息; 步骤 212, P-CSCF-A根据会话请求响应消息设置会话超时时间, 转发会 话请求响应消息, 启动超时定时器开始计时; 步骤 213-217 , UE-A从会话响应中获取刷新者和会话超时时间, UE-A 发送会话确认消息, 会话确认消息经过各 IMS网元到达 UE-B; 步骤 218, UE-A在会话超时时间的 1/2时间点主动发送会话刷新请求消 息到 P-CSCF-A; 步骤 219-222,收到会话刷新请求消息的各 IMS网元更新会话超时时间, 即重启启动超时定时器以重新开始计时; 步骤 223-227 , UE-B发送会话刷新响应消息,会话刷新响应消息经各 IMS 网元到达 UE-A; 步 4聚 228, UE-A出现异常死机; 步骤 229, UE-B在会话超时时间内未收到会话刷新确认消息, 发送结束 会话消息; 步骤 230-233 , 结束会话消息经各 IMS网元的转发到达 UE-A; 步骤 234-237, 由于 UE-A死机无法回应消息, P-CSCF-A发送结束会话 超时响应消息, 并经各 IMS网元的转发到达被叫 UE-B。 该方法中, RFC4028的 SIP会话超时时间由支持该协议的 UE-A和 UE-B 协商确定。 若由于网络或者终端的原因而导致会话时间超时, 会话路径上的 S-CSCF、 P-CSCF、 UE将分别执行释放呼叫过程, 释放本地资源。 发明人发现相关技术中的呼叫管理方法依赖于双方终端对 RFC4028 呼 叫检测机制的支持, 当呼叫双方终端均不支持 RFC4028呼叫检测机制时, 双 方终端均无法发起会话刷新请求消息以启动呼叫检测, 一旦出现故障, 将造 成终端和 S-CSCF、 P-CSCF等 IMS 中间网元的会话资源被挂死, 从而导致 IMS网元的处理能力和利用率较低, 用户体验较差。 发明内容 本发明旨在提供一种用于 IP多媒体子系统的呼叫管理方法及装置,能够 解决相关技术中的呼叫管理方法依赖于双方终端对 RFC4028 呼叫检测机制 的支持, 当呼叫双方终端均不支持 RFC4028呼叫检测机制时, 双方终端均无 法发起会话刷新请求消息以启动呼叫检测, 一旦出现故障, 将造成终端和 S-CSCF、 P-CSCF等 IMS 中间网元的会话资源被挂死, 从而导致 IMS 网元 的处理能力和利用率较低, 用户体验较差的问题。 在本发明的实施例中, 提供了一种用于 IP 多媒体子系统的呼叫管理方 法,包括以下步 4聚:在主叫终端与被叫终端之间建立 IP多媒体子系统的呼叫; 代理呼叫会话控制功能实体向其对应的终端发送状态检测请求; 若检测结果 为异常, 通知 IP多媒体子系统的网元释放呼叫。 优选地, 在上述呼叫管理方法中, 在主叫终端与被叫终端之间建立 IP多 媒体子系统呼叫包括: 主叫终端向被叫终端发送会话请求消息; 被叫终端根 据接收到的会话请求消息发送会话请求响应消息; 代理呼叫会话控制功能实 体根据会话请求响应消息设置检测时长, 并开始计时, 代理呼叫会话控制功 能实体包括主叫代理呼叫会话控制功能实体和被叫代理呼叫会话控制功能实 体; 主叫终端向被叫终端发送会话确认消息。 优选地, 在上述呼叫管理方法中, 代理呼叫会话控制功能实体向其对应 的终端发送状态检测请求包括: 主叫代理呼叫会话控制功能实体在到达检测 时长的一半时, 向主叫终端发送选择 OPTIONS (能力查询)消息; 被叫代理 呼叫会话控制功能实体在到达检测时长的一半时,向被叫终端发送 OPTIONS 消息。 优选地, 在上述呼叫管理方法中, 检测结果为异常具体包括: 主叫代理 呼叫会话控制功能实体在检测时长内未收到 OPTIONS响应消息。 优选地, 在上述呼叫管理方法中, 检测结果为异常包括: 主叫代理呼叫 会话控制功能实体收到 OPTIONS响应消息,且 OPTIONS响应消息的响应码 为 481。 优选地, 在上述呼叫管理方法中, 通知 IP多媒体子系统的网元释放呼叫 包括: 主叫代理呼叫会话控制功能实体释放呼叫, 并向被叫终端发送结束会 话消息; IP 多媒体子系统的中间网元与被叫终端根据结束会话消息释放呼 叫。 优选地, 在上述呼叫管理方法中, 还包括: 若主叫代理呼叫会话控制功 能实体收到 OPTIONS响应消息, 且 OPTIONS响应消息的响应码不为 481 , 主叫代理呼叫会话控制功能实体重新开始计时。 优选地, 在上述呼叫管理方法中, 检测结果为异常包括: 被叫代理呼叫 会话控制功能实体在检测时长内未收到来自被叫终端的 OPTIONS响应消息。 优选地, 在上述呼叫管理方法中, 检测结果为异常包括: 被叫代理呼叫 会话控制功能实体收到来自被叫终端的 OPTIONS 响应消息, 且 OPTIONS 响应消息的响应码为 481。 优选地, 在上述呼叫管理方法中, 通知 IP多媒体子系统的网元释放呼叫 包括: 被叫代理呼叫会话控制功能实体释放呼叫, 并向主叫终端发送结束会 话消息; IP 多媒体子系统的中间网元与主叫终端根据结束会话消息释放呼 叫。 优选地, 在上述呼叫管理方法中, 还包括: 若被叫代理呼叫会话控制功 能实体收到 OPTIONS响应消息, 且 OPTIONS响应消息的响应码不为 481 , 被叫代理呼叫会话控制功能实体重新开始计时。 另一方面, 在本发明的实施例中, 还提供了一种用于 IP多媒体子系统的 呼叫管理装置, 包括: 建立模块, 用于在主叫终端与被叫终端之间建立 IP多 媒体子系统的呼叫; 检测模块, 用于代理呼叫会话控制功能实体向其对应的 终端发送状态检测请求; 释放模块, 用于当检测结果为异常时, 通知 IP多媒 体子系统的网元释放呼叫。 上述实施例在 IP多媒体子系统的呼叫建立后,向呼叫两端的终端发送状 态检测请求以对终端的会话存活状态进行检测, 并在检测结果为异常时通知 IP多媒体子系统的网元释放本次呼叫, 由于釆用向终端发起请求以启动呼叫 检测,而无需依赖支持 RFC4028呼叫检测机制的终端主动发起会话刷新请求 消息, 所以克月艮了相关技术中的呼叫管理方法依赖于双方终端对 RFC4028 呼叫检测机制的支持, 当呼叫双方终端均不支持 RFC4028呼叫检测机制时, 双方终端均无法发起会话刷新请求消息以启动呼叫检测, 一旦出现故障, 将 造成终端和 S-CSCF、 P-CSCF等 IMS中间网元的会话资源被挂死,从而导致 IMS网元的处理能力和利用率较低, 用户体验较差的问题, 进而提高了在呼 叫双方终端均不支持 RFC4028呼叫检测机制的情况下 IMS 网元的处理能力 和利用率, 改善了用户体 -险。 附图说明 此处所说明的附图用来提供对本发明的进一步理解, 构成本申请的一部 分, 本发明的示意性实施例及其说明用于解释本发明, 并不构成对本发明的 不当限定。 在附图中: 图 1示出了 IMS呼叫的 SIP控制消息的示意图; 图 2示出了相关技术中呼叫管理方法的流程图; 图 3示出了 居本发明第一实施例的呼叫管理方法的流程图; 图 4示出了 居本发明第二实施例的呼叫管理方法的流程图; 图 5示出了 居本发明第三实施例的呼叫管理装置的结构图。 具体实施方式 下面将参考附图并结合实施例, 来详细说明本发明。 图 3示出了 居本发明第一实施例的呼叫管理方法的流程图, 该方法包 括以下步 4聚: 步 4聚 301 , 在主叫终端与被叫终端之间建立 IMS呼叫; 步骤 302, 代理呼叫会话控制功能实体 P-CSCF向其对应的终端发送状 态检测请求; 步骤 303 , 若检测结果为异常, 通知 IMS的网元释放呼叫。 本实施例在 IMS呼叫建立后, 向呼叫两端的主叫终端与被叫终端发送 态检测请求以对终端的会话存活状态进行检测, 并在检测结果为异常时通知 IMS网元释放本次呼叫, 由于釆用向终端发起请求以启动呼叫检测, 而无需 依赖支持 RFC4028呼叫检测机制的终端主动发起会话刷新请求消息,所以克 月艮了相关技术中的呼叫管理方法依赖于双方终端对 RFC4028 呼叫检测机制 的支持, 当呼叫双方终端均不支持 RFC4028呼叫检测机制时, 双方终端均无 法发起会话刷新请求消息以启动呼叫检测, 一旦出现故障, 将造成终端和 S-CSCF、 P-CSCF等 IMS 中间网元的会话资源被挂死, 从而导致 IMS 网元 的处理能力和利用率较低, 用户体验较差的问题, 进而提高了在呼叫双方终 端均不支持 RFC4028呼叫检测机制的情况下 IMS网元的处理能力和利用率, 改善了用户体 -险。 优选地, 在上述呼叫管理方法中, 步骤 301包括: 主叫终端 UE-A向被 叫终端 UE-B发送会话请求消息; UE-B根据接收到的会话请求消息发送会话 请求响应消息; 代理呼叫会话控制功能实体 P-CSCF根据会话请求响应消息 设置检测时长 T, 并开始计时, P-CSCF包括主叫代理呼叫会话控制功能实体 P-CSCF-A和被叫代理呼叫会话控制功能实体 P-CSCF-B; UE-A向 UE-B发 送会话确认消息。 本实施例在建立 IMS呼叫的过程中, P-CSCF-A和 P-CSCF-B根据会话 请求响应消息中携带的信息对自身进行检测时长 T的配置, 并启动超时定时 器开始计时,使得呼叫一旦建立便处于可检测状态, 消除了呼叫的检测死区, 提高了呼叫检测的准确度。 优选地, 在上述呼叫管理方法中, 步骤 302 包括: P-CSCF-A在到达检 测时长的一半 (T/2 ) 时, 向 UE-A发送 OPTIONS 消息; P-CSCF-B在 T/2 时, 向 UE-B发送 OPTIONS消息。 本实施例由 P-CSCF-A、 P-CSCF-B在其计时到 T/2时分别向其相应的终 端 UE-A、 UE-B发送 OPTIONS消息, 其中 OPTIONS消息由 P-CSCF发起, 原本用于探测网元能力, 本实施例中利用发送 OPTIONS 消息以启动呼叫检 测,使得无论终端是否支持 RFC4028呼叫检测机制均可进行呼叫检测以获知 当前的会话存活状态, 提高了当 UE不支持 RFC4028呼叫检测机制时 IMS 网元处理能力和利用率。 优选地, 在上述呼叫管理方法中, 检测结果为异常具体包括: P-CSCF-A 在检测时长 T内未收到 OPTIONS响应消息。 本实施例中的 P-CSCF-A在检测时长 T内未收到 OPTIONS响应消息, 此时认为检测结果异常, 其中超时未收到的原因可能是由于 UE-A异常死机 而无能力响应接收到的 OPTIONS 消息, 也可能是由于网络故障造成 OPTIONS响应消息的发送超时, 这样做, 简单易行地实现了对呼叫的异常检 测, 有利于对该异常情况进行有针对性的处理。 优选地, 在上述呼叫管理方法中, 检测结果为异常具体包括: P-CSCF-A 收到 OPTIONS响应消息, 且 OPTIONS响应消息的响应码为 481。 本实施例中的 P-CSCF-A虽然收到 OPTIONS响应消息, 但是 OPTIONS 响应消息中携带的响应码为 481 , 此时认为检测结果异常, 其中响应码 481 表示会话不存在, 其原因可能是由于 UE-A异常重启而导致会话无法被正确 识别, 这样做, 简单易行地实现了对呼叫的异常检测, 有利于对该异常情况 进行有针对性的处理。 优选地, 在上述呼叫管理方法中, 通知 IMS的网元释放呼叫具体包括: P-CSCF-A释放呼叫, 并向 UE-B发送结束会话消息; IMS中间网元与 UE-B 根据结束会话消息释放呼叫。 本实施例中若 P-CSCF-A由于超时未收到 OPTIONS响应消息或接收到 响应码为 481的 OPTIONS响应消息,则认为检测结果为异常,此时 P-CSCF-A 首先释放本端的呼叫资源, 然后向 UE-B发送结束会话消息以通知 UE-B和 其他 IMS中间网元释放呼叫,最后 IMS中间网元与 UE-B根据结束会话消息 释放呼叫, 由于呼叫是否异常的判断是 P-CSCF-A根据是否收到 OPTIONS 响应消息及其响应码作出的, 故本实施例中结束会话消息直接由 P-CSCF-A 发起, 这样 #丈, 使得当本次呼叫异常时 UE-B和 IMS中间网元及时地被释放 掉以供更有效地使用,避免了由于终端和 IMS中间网元未被释放而导致数据 区挂死的现象。 优选地, 在上述呼叫管理方法中, 还包括: 若 P-CSCF-A收到 OPTIONS 响应消息, 且 OPTIONS响应消息的响应码不为 481 , P-CSCF-A重新开始计 时。 本实施例中的 P-CSCF-A收到 OPTIONS响应消息,且 OPTIONS响应消 息的响应码不为 481 , 此时认为呼叫为正常状态, P-CSCF-A重启超时定时器 以重新开始计时, 进入下一个呼叫检测周期, 实现了不间断的呼叫检测。 图 4示出了 居本发明第二实施例的呼叫管理方法的流程图, 本实施例 中的呼叫双方 UE-A、 UE-B均不支持 RFC4028会话刷新机制, 该方法包括 以下步 4聚: 步骤 401 , UE-A发送会话请求消息以发起一个呼叫, 其中会话请求消息 中未包含支持 RFC4028的标记; 步骤 402, P-CSCF-A接收会话请求消息时, 得知主叫方 UE-A 不支持 RFC4028的呼叫检测机制。 将会话请求消息转发到用户的服务呼叫会话控制 点 S-CSCF-A; 步骤 403 , S-CSCF-A 接收会话请求消息, 得知主叫方 UE-A 不支持 RFC4028 的呼叫检测机制, 将会话请求消息转发到 I-CSCF , 寻找被叫 S-CSCF; 步骤 404, I-CSCF将会话请求消息发送到被叫 S-CSCF-B; 步骤 405 , S-CSCF-B得知主叫方 UE-A不支持 RFC4028的呼叫检测机 制, 将会话请求消息发送到 P-CSCF-B;; 步骤 406, P-CSCF-B得知主叫方 UE-A不支持 RFC4028检测机制, 将 会话请求消息发送到 UE-B; 步骤 407, UE-B收到会话请求消息, 由于 UE-B也不支持 RFC4028的 呼叫检测机制, 故直接发送会话请求响应消息; 步骤 408 , P-CSCF-B接收会话请求响应消息, 得知主、 被叫 UE均不支 持 RFC4028的呼叫检测机制,根据该会话请求响应消息设置本端的超时定时 器的计时时长为检测时长 T, 并启动超时定时器; 步骤 409, P-CSCF-B转发会话请求响应消息; 步骤 410, S-CSCF-B接收会话请求响应消息, 并将其发送到 I-CSCF, 由于消息中无 RFC4028的协商参数, 故不启动超时定时器; 步骤 411 , I-CSCF将会话请求响应消息前传到 S-CSCF-A; 步骤 412, S-CSCF-A接收会话请求响应消息,并将其前传到 P-CSCF-A, 由于消息中无 RFC4028的协商参数, 故不启动超时定时器; 步骤 413 , P-CSCF-A接收会话请求响应消息, 得知主被叫 UE均不支持 RFC4028的呼叫检测机制,设置本端的超时定时器的计时时长为检测时长 T , 并启动超时定时器; 步骤 414, P-CSCF-A前传响应到 UE-A; 步骤 415-419, UE-A发送会话确认消息, 会话确认消息经过各 IMS 网 元到达 UE-B; 步骤 420, P-CSCF-A在 T/2时, 发送 OPTIONS消息到 UE-A; 步骤 421 , P-CSCF-A 接) 来自 UE-A 的 OPTIONS 响应消息, 且该 OPTIONS响应消息的响应码为 200, P-CSCF-A重启超时定时器; 步骤 422, P-CSCF-B在 T/2时, 发送 OPTIONS消息到 UE-B; 步骤 423 , P-CSCF-B 接) 来自 UE-B 的 OPTIONS 响应消息, 且该 OPTIONS响应消息的响应码为 200, P-CSCF-B重启超时定时器; 步骤 424, UE-A异常断线重启; 步骤 425 , P-CSCF-A在 T/2时, 发送 OPTIONS消息到 UE-A; 步骤 426 , 由于 UE- A重启, 故与此时收到的 OPTIONS消息中携带的重 启前会话信息不匹配, UE-A向 P-CSCF-A发送 OPTIONS响应消息, 但其响 应码为 481 , 表示会话不存在; 步骤 427, P-CSCF-A收到对话内 OPTION 481响应消息后, 释放会话资 源, 并且发送结束会话消息到 S-CSCF-A; 步骤 428-430, IMS 中间网元接收结束会话消息, 释放呼叫资源, 并转 发结束会话消息到 UE-B; 步骤 431 , UE-B接收结束会话消息, 释放呼叫资源, 并发送结束会话响 应消息; 步骤 432-434, IMS网元前传结束会话响应消息到 P-CSCF-A。 本实施例中由 P-CSCF设置检测时长 T,并通过 SIP的 OPTIONS消息对 主叫 UE和被叫 UE的会话存活状态进行检测, 而不是像相关技术的呼叫管 理方法那样: 由主、 被叫 UE来设置呼叫检测机制 (步骤 201和步骤 207 ) , 由 P-CSCF、 S-CSCF从会话请求响应消息中获取并保存该会话超时时间 (步 骤 208、 步骤 209、 步骤 211和步骤 212 )。 本实施例降低了对终端的要求, 无论终端是否支持 RCF4028呼叫检测机制均可实现对呼叫的检测,以完成对 呼叫的管理。 优选地, 在上述呼叫管理方法中, 检测结果为异常具体包括: P-CSCF-B 在检测时长 T内未收到来自 UE-B的 OPTIONS响应消息。 本实施例中的 P-CSCF-B在检测时长 T内未) 到 OPTIONS响应消息, 此时认为检测结果异常, 其中超时未收到的原因可能是由于 UE-B异常死机 而无能力响应接收到的 OPTIONS 消息, 也可能是由于网络故障造成 OPTIONS响应消息的发送超时, 这样做, 简单易行地实现了对呼叫的异常检 测, 有利于对该异常情况进行有针对性的处理。 优选地, 在上述呼叫管理方法中, 检测结果为异常具体包括: P-CSCF-B 收到来自 UE-B的 OPTIONS响应消息, 且 OPTIONS响应消息的响应码为 481。 本实施例中的 P-CSCF-B虽然收到 OPTIONS响应消息, 但是 OPTIONS 响应消息中携带的响应码为 481 , 此时认为检测结果异常, 其中响应码 481 表示会话不存在, 其原因可能是由于 UE-B异常重启而导致会话无法被正确 识别, 这样做, 简单易行地实现了对呼叫的异常检测, 有利于对该异常情况 进行有针对性的处理。 优选地, 在上述呼叫管理方法中, 通知 IMS的网元释放呼叫具体包括: P-CSCF-B释放呼叫, 并向 UE-A发送结束会话消息; IMS中间网元与 UE-A 根据结束会话消息释放呼叫。 本实施例中若 P-CSCF-B 由于超时未收到 OPTIONS响应消息或接收到 响应码为 481的 OPTIONS响应消息,则认为检测结果为异常,此时 P-CSCF-B 首先释放本端的呼叫资源, 然后向 UE-A发送结束会话消息以通知 UE-A和 其他 IMS中间网元释放呼叫,最后 IMS中间网元与 UE-A根据结束会话消息 释放呼叫, 由于呼叫是否异常的判断是 P-CSCF-B根据是否收到 OPTIONS 响应消息及其响应码作出的, 故本实施例中结束会话消息直接由 P-CSCF-B 发起, 这样 #丈, 使得当本次呼叫异常时 UE-A和 IMS中间网元及时地被释放 掉以供更有效地使用,避免了由于终端和 IMS中间网元未被释放而导致数据 区挂死的现象。 优选地, 在上述呼叫管理方法中, 还包括: 若 P-CSCF-B收到 OPTIONS 响应消息, 且 OPTIONS响应消息的响应码不为 481 , P-CSCF-B重新开始计 时。 本实施例中的 P-CSCF-B收到 OPTIONS响应消息,且 OPTIONS响应消 息的响应码不为 481 , 此时认为呼叫为正常状态, P-CSCF-B重启超时定时器 以重新开始计时, 进入下一个呼叫检测周期, 实现了不间断的呼叫检测。 图 5示出了 居本发明第三实施例的呼叫管理装置的结构图, 包括: 建立模块 10, 用于在主叫终端与被叫终端之间建立 IMS的呼叫; 检测模块 20 , 用于代理呼叫会话控制功能实体向其对应的终端发送状态 检测请求; 释放模块 30, 用于当检测结果为异常时, 通知 IP多媒体子系统的网元 释放呼叫。 本实施例首先釆用建立模块 10在主叫终端与被叫终端之间建立 IMS呼 叫, 然后代理呼叫会话控制功能实体釆用检测模块 20 向其对应的终端发送 状态检测请求以对终端的会话存活状态进行检测, 最后釆用释放模块 30 在 检测结果为异常时通知 IMS网元释放本次呼叫, 由于釆用向终端发起请求以 启动呼叫检测,而无需依赖支持 RFC4028呼叫检测机制的终端主动发起会话 刷新请求消息, 所以克月艮了相关技术中的呼叫管理方法依赖于双方终端对 RFC4028呼叫检测机制的支持, 当呼叫双方终端均不支持 RFC4028呼叫检 测机制时, 双方终端均无法发起会话刷新请求消息以启动呼叫检测, 一旦出 现故障,将造成终端和 S-CSCF、P-CSCF等 IMS中间网元的会话资源被挂死, 从而导致 IMS网元的处理能力和利用率较低, 用户体验较差的问题, 进而提 高了在呼叫双方终端均不支持 RFC4028呼叫检测机制的情况下 IMS 网元的 处理能力和利用率, 改善了用户体验。 从以上的描述中, 可以看出, 在呼叫双方终端均不支持 RFC4028呼叫检 测机制的情况下, 通过本发明上述的实施例, 提高了 IMS网元的处理能力和 利用率, 提高了用户体验。 显然, 本领域的技术人员应该明白, 上述的本发明的各模块或各步骤可 以用通用的计算装置来实现, 它们可以集中在单个的计算装置上, 或者分布 在多个计算装置所组成的网络上, 可选地, 它们可以用计算装置可执行的程 序代码来实现, 从而, 可以将它们存储在存储装置中由计算装置来执行, 或 者将它们分别制作成各个集成电路模块, 或者将它们中的多个模块或步骤制 作成单个集成电路模块来实现。 这样, 本发明不限制于任何特定的硬件和软 件结合。 以上所述仅为本发明的优选实施例而已, 并不用于限制本发明, 对于本 领域的技术人员来说, 本发明可以有各种更改和变化。 凡在本发明的 ^"神和 原则之内, 所作的任何修改、 等同替换、 改进等, 均应包含在本发明的保护 范围之内。 The IMS call uses the Session Initiation Protocol (SIP) as the control signaling protocol in the control layer. SIP defines a call detection mechanism in RFC4028, that is, the terminal supporting RFC4028 periodically sends the session request. A message (re-INVITE, also known as a call request message) or a session refresh request message (UPDATE) is used to maintain the activity of the session. The time interval of the session refresh request message is determined by the negotiation mechanism of RFC4028. If the session refresh request message is not received within the interval, the session is considered to have been terminated, the terminal will send a session release message (BYE, also referred to as an end session message), and the stateful proxy server removes all states of the call. . FIG. 1 is a schematic diagram of a SIP control message for an IMS call, including the following network elements: Calling User Equipment UE-A (User Equipment A) 101, Calling Agent Call Session Control Function Entity P-CSCF-A (Proxy Call Session) Control Function A) 102, the calling call session control function entity S-CSCF-A (Serving Call Session Control Function A) 103, the query call session control function entity I-CSCF (Interrogating Call Session Control Function) 104, The called call session control function entity S-CSCF-B (Serving Call Session Control function B) 105, the called proxy call session control function entity P-CSCF-B (Proxy Call Session B) 106 and the called user equipment UE-B ( User Equipment B ) 107. A call management method for an IP multimedia subsystem is provided in the related art. Referring to FIG. 2, the method includes the following steps: Step 201: UE-A sends a session request message to initiate a call, where UE-A supports RFC4028 call detection mechanism, this message contains session timeout (such as setting the session timeout time to 1800 seconds) and session refresh negotiation parameters (such as setting UE-A as the refresher and caller); Step 202: The P-CSCF-A receives the session request message, and learns that the calling party UE-A supports the call detection mechanism of the RFC 4028, and forwards the session request message to the serving call session control point S-CSCF-A of the user; Step 203; The S-CSCF-A receives the session request message, and learns that the calling party UE-A supports the call detection mechanism of the RFC 4028, and forwards the session request message to the I-CSCF to find the called S-CSCF; Step 204, the I-CSCF will session The request message is sent to the called S-CSCF-B. Step 205: The S-CSCF-B learns that the calling party UE-A supports the call detection mechanism of the RFC 4028, and sends a session request message to the P-CSCF-B. Step 206 The P-CSCF-B learns that the calling party UE-A supports the call detection mechanism of the RFC 4028, and sends a session request message to the UE-B. In step 207, the UE-B receives the session request message, where the UE-B also supports the RFC 4028. The call detection mechanism, UE-B will update the negotiation parameters through the session in the message, determine the refresher and session timeout time, and send the negotiated session request response message; Step 208, P-CSCF-B sets according to the session request response message Session timeout, forwarding session request response message; Step 209, SC The SCF-B sets the session timeout time according to the session request response message, and forwards the session request response message. Step 210: The I-CSCF forwards the session request response message, and releases the jt call resource because it does not participate in the subsequent session; Step 211, S-CSCF- The session timeout time is set according to the session request response message, and the session request response message is forwarded. Step 212: The P-CSCF-A sets the session timeout time according to the session request response message, forwards the session request response message, and starts the timeout timer to start timing. Step 213 - 217, UE-A obtains the refresher and the session timeout time from the session response, UE-A sends a session confirmation message, and the session confirmation message arrives at UE-B through each IMS network element; Step 218, UE-A is in the session timeout period 1/2 time point actively sends a session refresh request message to the P-CSCF-A; Steps 219-222: The IMS network element receiving the session refresh request message updates the session timeout time, that is, restarts the startup timeout timer to restart the timing; Steps 223-227, UE-B sends a session refresh response message, and the session refresh response message After the IMS network element arrives at the UE-A; the step 4 is 228, and the UE-A is abnormally dead; Step 229, the UE-B does not receive the session refresh confirmation message within the session timeout period, and sends the end session message; Steps 230-233 End session message arrives at UE-A through forwarding of each IMS network element; Steps 234-237, P-CSCF-A sends an end session timeout response message and is forwarded by each IMS network element because UE-A crashes and cannot respond to the message. Arrived at the called UE-B. In this method, the SIP session timeout time of the RFC 4028 is determined by the UE-A and UE-B that support the protocol. If the session time expires due to the network or the terminal, the S-CSCF, the P-CSCF, and the UE on the session path respectively perform the release call process to release the local resources. The inventor has found that the call management method in the related art relies on the support of the RFC4028 call detection mechanism by both terminals. When both terminals of the call do not support the RFC4028 call detection mechanism, both terminals cannot initiate a session refresh request message to initiate call detection. If the fault occurs, the session resources of the IMS intermediate network element, such as the S-CSCF and the P-CSCF, are hanged. As a result, the processing capability and utilization of the IMS network element are low, and the user experience is poor. SUMMARY OF THE INVENTION The present invention is directed to a call management method and apparatus for an IP multimedia subsystem, which can solve the call management method in the related art, which relies on the support of the terminal for the RFC4028 call detection mechanism, and is not supported by both parties of the call. When the RFC4028 call detection mechanism is used, both terminals cannot initiate a session refresh request message to initiate call detection. In the event of a fault, the session resources of the IMS intermediate network element such as the S-CSCF and the P-CSCF are hanged, resulting in IMS. The processing capacity and utilization of network elements are low, and the user experience is poor. In an embodiment of the present invention, a call management method for an IP multimedia subsystem is provided, including the following steps: establishing a call of an IP multimedia subsystem between a calling terminal and a called terminal; proxy call session The control function entity sends a status detection request to its corresponding terminal; if the detection result As an exception, the network element of the IP Multimedia Subsystem is notified to release the call. Preferably, in the foregoing call management method, the establishing an IP multimedia subsystem call between the calling terminal and the called terminal comprises: the calling terminal sending a session request message to the called terminal; and the called terminal according to the received session request message Sending a session request response message; the proxy call session control function entity sets a detection duration according to the session request response message, and starts timing, and the proxy call session control function entity includes a calling proxy call session control function entity and a called proxy call session control function entity; The calling terminal sends a session confirmation message to the called terminal. Preferably, in the foregoing call management method, the proxy call session control function entity sends a status detection request to its corresponding terminal, including: the calling proxy call session control function entity sends a selection OPTIONS to the calling terminal when the detection time is half of the detection duration (Capability Query) message; The called proxy call session control function entity sends an OPTIONS message to the called terminal when it reaches half of the detection duration. Preferably, in the foregoing call management method, the detection result is abnormal: the calling proxy call session control function entity does not receive the OPTIONS response message within the detection duration. Preferably, in the foregoing call management method, the detection result is abnormal: the calling proxy call session control function entity receives the OPTIONS response message, and the response code of the OPTIONS response message is 481. Preferably, in the foregoing call management method, the network element that notifies the IP multimedia subsystem releases the call includes: the calling agent call session control function entity releases the call, and sends an end session message to the called terminal; the intermediate network of the IP multimedia subsystem The meta and the called terminal release the call according to the end session message. Preferably, in the foregoing call management method, the method further includes: if the calling proxy call session control function entity receives the OPTIONS response message, and the response code of the OPTIONS response message is not 481, the calling proxy call session control function entity restarts timing . Preferably, in the foregoing call management method, the detection result is abnormal: the called proxy call session control function entity does not receive the OPTIONS response message from the called terminal within the detection duration. Preferably, in the foregoing call management method, the detection result is abnormal: the called proxy call session control function entity receives an OPTIONS response message from the called terminal, and the response code of the OPTIONS response message is 481. Preferably, in the foregoing call management method, the network element notifying the IP multimedia subsystem to release the call includes: the called proxy call session control function entity releases the call, and sends an end session message to the calling terminal; the intermediate network of the IP multimedia subsystem The meta and the calling terminal release the call according to the end session message. Preferably, in the foregoing call management method, the method further includes: if the called proxy call session control function entity receives the OPTIONS response message, and the response code of the OPTIONS response message is not 481, the called proxy call session control function entity restarts timing . In another aspect, in an embodiment of the present invention, a call management apparatus for an IP multimedia subsystem is provided, including: an establishing module, configured to establish an IP multimedia subsystem between a calling terminal and a called terminal. The detecting module is configured to send a status detection request to the corresponding terminal by the proxy call session control function entity, and the release module is configured to notify the network element of the IP multimedia subsystem to release the call when the detection result is abnormal. After the call setup of the IP multimedia subsystem is performed, the foregoing embodiment sends a status detection request to the terminal at both ends of the call to detect the session survival state of the terminal, and notifies the network element of the IP multimedia subsystem to release the current when the detection result is abnormal. The call, because the terminal initiates a request to the terminal to initiate call detection without relying on the terminal supporting the RFC4028 call detection mechanism to initiate the session refresh request message, the call management method in the related art relies on the terminal to the RFC4028 call. Supported by the detection mechanism, when both terminals of the calling party do not support the RFC4028 call detection mechanism, both terminals cannot initiate a session refresh request message to initiate call detection. In the event of a failure, the terminal and the S-CSCF, P-CSCF, etc. The session resources of the network element are hanged, resulting in a problem that the processing capability and utilization of the IMS network element are low, and the user experience is poor, thereby improving the IMS network element when the calling terminal does not support the RFC4028 call detection mechanism. The processing power and utilization rate have improved the user's body-risk. BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawings, which are set to illustrate,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, In the drawings: FIG. 1 is a schematic diagram showing a SIP control message of an IMS call; FIG. 2 is a flowchart showing a call management method in the related art; 3 is a flow chart showing a call management method according to a first embodiment of the present invention; FIG. 4 is a flow chart showing a call management method according to a second embodiment of the present invention; FIG. 5 is a third embodiment of the present invention. A block diagram of a call management apparatus of an embodiment. BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, the present invention will be described in detail with reference to the accompanying drawings in conjunction with the embodiments. FIG. 3 is a flowchart of a call management method according to a first embodiment of the present invention. The method includes the following steps: Step 4: 301, establishing an IMS call between the calling terminal and the called terminal; Step 302, The proxy call session control function entity P-CSCF sends a status detection request to its corresponding terminal. Step 303: If the detection result is abnormal, notify the IMS network element to release the call. After the IMS call is established, the IMS network sends a state detection request to the calling terminal and the called terminal at both ends of the call to detect the session survival state of the terminal, and notifies the IMS network element to release the current call when the detection result is abnormal. Since the terminal initiates a call to the terminal to initiate call detection without relying on the terminal supporting the RFC4028 call detection mechanism to actively initiate a session refresh request message, the call management method in the related art relies on the terminal to the RFC4028 call detection mechanism. Support, when both terminals of the calling party do not support the RFC4028 call detection mechanism, both terminals cannot initiate a session refresh request message to initiate call detection. In case of failure, the terminal and the IMS intermediate network element such as S-CSCF and P-CSCF will be caused. The session resources are hanged, resulting in a problem of low processing power and utilization of the IMS network element and poor user experience, thereby improving the processing of the IMS network element when the call terminals do not support the RFC4028 call detection mechanism. Capacity and utilization, improved user body-risk. Preferably, in the foregoing call management method, step 301 includes: the calling terminal UE-A sends a session request message to the called terminal UE-B; the UE-B sends a session request response message according to the received session request message; The session control function entity P-CSCF sets the detection duration T according to the session request response message, and starts timing. The P-CSCF includes a calling proxy call session control function entity P-CSCF-A and a called proxy call session control function entity P-CSCF. -B; UE-A sends a session confirmation message to UE-B. In the process of establishing an IMS call, the P-CSCF-A and the P-CSCF-B configure the detection time length T according to the information carried in the session request response message, and start the timeout timer to start timing, so that the call is made. Once established, it is in a detectable state, eliminating the dead zone of call detection and improving the accuracy of call detection. Preferably, in the foregoing call management method, step 302 includes: P-CSCF-A sends an OPTIONS message to UE-A when it reaches half of the detection duration (T/2); when P-CSCF-B is at T/2 , Send an OPTIONS message to UE-B. In this embodiment, the P-CSCF-A and the P-CSCF-B respectively send an OPTIONS message to their respective terminals UE-A and UE-B when they are timed to T/2, wherein the OPTIONS message is initiated by the P-CSCF. For detecting network element capability, in this embodiment, the OPTIONS message is sent to initiate call detection, so that the call detection can be performed to know the current session survival state regardless of whether the terminal supports the RFC4028 call detection mechanism, and the UE does not support the RFC4028 call. IMS network element processing capability and utilization when detecting mechanisms. Preferably, in the foregoing call management method, the detection result is abnormal: the P-CSCF-A does not receive the OPTIONS response message within the detection duration T. The P-CSCF-A in this embodiment does not receive the OPTIONS response message within the detection duration T. At this time, the detection result is abnormal, and the reason that the timeout is not received may be due to the UE-A abnormal crash and the inability to respond to the reception. The OPTIONS message may also be due to the network failure causing the transmission of the OPTIONS response message to time out. In this way, the abnormal detection of the call is easily implemented, which is beneficial to the targeted processing of the abnormal situation. Preferably, in the foregoing call management method, the detection result is abnormal: the P-CSCF-A receives the OPTIONS response message, and the response code of the OPTIONS response message is 481. The P-CSCF-A in this embodiment receives the OPTIONS response message, but the response code carried in the OPTIONS response message is 481. At this time, the detection result is abnormal, and the response code 481 indicates that the session does not exist. The reason may be due to The abnormal restart of the UE-A causes the session to be incorrectly recognized. In this way, the abnormal detection of the call is easily implemented, which facilitates the targeted processing of the abnormal situation. Preferably, in the foregoing call management method, the network element that notifies the IMS to release the call specifically includes: the P-CSCF-A releases the call, and sends an end session message to the UE-B; the IMS intermediate network element and the UE-B according to the end session message Release the call. In this embodiment, if the P-CSCF-A does not receive the OPTIONS response message due to the timeout or receives the OPTIONS response message with the response code of 481, the detection result is abnormal, and the P-CSCF-A first releases the local call resource. Then, the end session message is sent to the UE-B to notify the UE-B and other IMS intermediate network elements to release the call. Finally, the IMS intermediate network element and the UE-B release the call according to the end session message, and the P-CSCF is determined because the call is abnormal. -A is based on whether the OPTIONS response message and its response code are received. Therefore, the end session message is directly initiated by the P-CSCF-A in this embodiment, so that the current call is abnormal, and the UE-B and the IMS are in the middle. The network element is released in time for more efficient use, avoiding the phenomenon that the data area hangs due to the terminal and the IMS intermediate network element are not released. Preferably, in the foregoing call management method, the method further includes: if the P-CSCF-A receives the OPTIONS response message, and the response code of the OPTIONS response message is not 481, the P-CSCF-A restarts timing. The P-CSCF-A in this embodiment receives the OPTIONS response message, and the response code of the OPTIONS response message is not 481. At this time, the call is considered to be in a normal state, and the P-CSCF-A restarts the timeout timer to restart the timing and enters. The next call detection cycle enables uninterrupted call detection. FIG. 4 is a flowchart of a call management method according to a second embodiment of the present invention. The call parties UE-A and UE-B in this embodiment do not support the RFC 4028 session refresh mechanism. The method includes the following steps: Step 401: UE-A sends a session request message to initiate a call, where the session request message does not include a flag supporting RFC 4028. Step 402: When receiving the session request message, the P-CSCF-A learns that the calling party UE-A does not Supports the call detection mechanism of RFC4028. Forwarding the session request message to the serving call session control point S-CSCF-A of the user; Step 403: The S-CSCF-A receives the session request message, and learns that the calling party UE-A does not support the call detection mechanism of the RFC 4028, and the session is The request message is forwarded to the I-CSCF to find the called S-CSCF; Step 404, the I-CSCF sends a session request message to the called S-CSCF-B; Step 405, the S-CSCF-B learns the calling party UE- A does not support the call detection mechanism of RFC4028, and sends a session request message to P-CSCF-B; Step 406: The P-CSCF-B learns that the calling party UE-A does not support the RFC4028 detection mechanism, and sends a session request message to the UE-B. In step 407, the UE-B receives the session request message, because the UE-B does not. Supporting the call detection mechanism of RFC4028, the session request response message is directly sent. Step 408: The P-CSCF-B receives the session request response message, and learns that the calling and the called UE do not support the call detection mechanism of the RFC 4028, and responds according to the session request. The message sets the timeout period of the local timeout timer to be the detection time length T, and starts the timeout timer; Step 409, the P-CSCF-B forwards the session request response message; Step 410, the S-CSCF-B receives the session request response message, and Sending it to the I-CSCF, because there is no negotiation parameter of the RFC4028 in the message, the timeout timer is not started; Step 411, the I-CSCF forwards the session request response message to the S-CSCF-A; Step 412, S-CSCF- A receives the session request response message and forwards it to the P-CSCF-A. Since there is no negotiation parameter of the RFC 4028 in the message, the timeout timer is not started. Step 413, the P-CSCF-A receives the session request response message, and learns The primary and secondary UEs do not support RFC. The call detection mechanism of the 4028 sets the timeout period of the local timeout timer to the detection duration T, and starts the timeout timer; Step 414, the P-CSCF-A forwards the response to the UE-A; Steps 415-419, the UE-A sends The session confirmation message, the session confirmation message arrives at the UE-B through each IMS network element; in step 420, the P-CSCF-A sends an OPTIONS message to the UE-A at T/2; Step 421, P-CSCF-A is connected) UE-A's OPTIONS response message, and the response code of the OPTIONS response message is 200, P-CSCF-A restarts the timeout timer; Step 422, P-CSCF-B sends an OPTIONS message to UE-B at T/2 Step 423, P-CSCF-B is connected to the OPTIONS response message from the UE-B, and the response code of the OPTIONS response message is 200, and the P-CSCF-B restarts the timeout timer; Step 424, the UE-A is abnormally disconnected. Restart In step 425, the P-CSCF-A sends an OPTIONS message to the UE-A at the time of T/2. In step 426, the UE-A restarts, and therefore does not match the pre-restart session information carried in the OPTIONS message received at this time. The UE-A sends an OPTIONS response message to the P-CSCF-A, but the response code is 481, indicating that the session does not exist. Step 427, after receiving the OPTION 481 response message in the session, the P-CSCF-A releases the session resource and sends the session resource. Ending the session message to the S-CSCF-A; Steps 428-430, the IMS intermediate network element receives the end session message, releases the call resource, and forwards the end session message to the UE-B; Step 431, the UE-B receives the end session message, and releases Calling the resource, and sending an end session response message; Steps 432-434, the IMS network element pre-passes the end session response message to the P-CSCF-A. In this embodiment, the detection duration T is set by the P-CSCF, and the session survival state of the calling UE and the called UE is detected by the SIP OPTIONS message, instead of the call management method like the related art: by the master, the called The UE sets the call detection mechanism (steps 201 and 207), and the P-CSCF and the S-CSCF obtain and save the session timeout time from the session request response message (step 208, step 209, step 211, and step 212). This embodiment reduces the requirement for the terminal, and the call detection can be implemented regardless of whether the terminal supports the RCF4028 call detection mechanism to complete the management of the call. Preferably, in the foregoing call management method, the detection result is abnormal: the P-CSCF-B does not receive the OPTIONS response message from the UE-B within the detection duration T. In this embodiment, the P-CSCF-B does not respond to the OPTIONS response message during the detection duration T. At this time, the detection result is abnormal, and the reason that the timeout is not received may be due to the abnormal crash of the UE-B and the inability to respond to the reception. The OPTIONS message may also be due to the network failure causing the transmission of the OPTIONS response message to time out. In this way, the abnormal detection of the call is easily implemented, which is beneficial to the targeted processing of the abnormal situation. Preferably, in the foregoing call management method, the detection result is abnormal: the P-CSCF-B receives the OPTIONS response message from the UE-B, and the response code of the OPTIONS response message is 481. The P-CSCF-B in this embodiment receives the OPTIONS response message, but the response code carried in the OPTIONS response message is 481. At this time, the detection result is abnormal, and the response code 481 indicates that the session does not exist. The reason may be due to The abnormal restart of the UE-B causes the session to be incorrectly recognized. In this way, the abnormal detection of the call is easily implemented, which facilitates the targeted processing of the abnormal situation. Preferably, in the foregoing call management method, the network element that notifies the IMS to release the call specifically includes: the P-CSCF-B releases the call, and sends an end session message to the UE-A; the IMS intermediate network element and the UE-A according to the end session message Release the call. In this embodiment, if the P-CSCF-B does not receive the OPTIONS response message due to the timeout or receives the OPTIONS response message with the response code of 481, the detection result is abnormal, and the P-CSCF-B first releases the local call resource. Then, the end session message is sent to the UE-A to notify the UE-A and other IMS intermediate network elements to release the call. Finally, the IMS intermediate network element and the UE-A release the call according to the end session message, and the P-CSCF is determined because the call is abnormal. -B is made according to whether the OPTIONS response message and its response code are received. Therefore, the end session message is directly initiated by the P-CSCF-B in this embodiment, so that when the call is abnormal, the UE-A and the IMS are in the middle. The network element is released in time for more efficient use, avoiding the phenomenon that the data area hangs due to the terminal and the IMS intermediate network element are not released. Preferably, in the foregoing call management method, the method further includes: if the P-CSCF-B receives the OPTIONS response message, and the response code of the OPTIONS response message is not 481, the P-CSCF-B restarts timing. The P-CSCF-B in this embodiment receives the OPTIONS response message, and the response code of the OPTIONS response message is not 481. At this time, the call is considered to be in a normal state, and the P-CSCF-B restarts the timeout timer to restart the timing and enters. The next call detection cycle enables uninterrupted call detection. FIG. 5 is a structural diagram of a call management apparatus according to a third embodiment of the present invention, including: an establishing module 10, configured to establish an IMS call between a calling terminal and a called terminal; and a detecting module 20, configured to proxy The call session control function entity sends a status detection request to its corresponding terminal. The release module 30 is configured to notify the network element of the IP multimedia subsystem to release the call when the detection result is abnormal. In this embodiment, the IMS call setup module 10 first establishes an IMS call between the calling terminal and the called terminal, and then the proxy call session control function entity uses the detecting module 20 to send a status detection request to the corresponding terminal to survive the session of the terminal. The state is detected, and finally the release module 30 notifies the IMS network element to release the call when the detection result is abnormal, because the terminal initiates a request to initiate call detection, and does not need to rely on the terminal supporting the RFC4028 call detection mechanism to initiate the session. The request message is refreshed. Therefore, the call management method in the related art relies on the support of the RFC4028 call detection mechanism by both terminals. When both terminals of the call do not support the RFC4028 call detection mechanism, both terminals cannot initiate a session refresh request message. In order to initiate call detection, in the event of a failure, the session resources of the IMS intermediate network element such as the S-CSCF and the P-CSCF are suspended, resulting in lower processing capability and utilization of the IMS network element and poor user experience. The problem, which in turn increases the RFC4028 call in both terminals of the calling party. The processing capability and utilization of the IMS network element in the case of the detection mechanism improves the user experience. From the above description, it can be seen that, in the case that the caller terminal does not support the RFC4028 call detection mechanism, the foregoing embodiment of the present invention improves the processing capability and utilization of the IMS network element, and improves the user experience. Obviously, those skilled in the art should understand that the above modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device, such that they may be stored in the storage device by the computing device, or they may be separately fabricated into individual integrated circuit modules, or they may be Multiple modules or steps are made into a single integrated circuit module. Thus, the invention is not limited to any specific combination of hardware and software. The above is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the scope of the present invention are intended to be included within the scope of the present invention.

Claims

权 利 要 求 书 Claim
1. 一种用于因特网协议 IP多媒体子系统的呼叫管理方法, 其特征在于, 包 括以下步 4聚: A call management method for an Internet Protocol IP Multimedia Subsystem, comprising the following steps:
在主叫终端与被叫终端之间建立 IP多媒体子系统的呼叫; 代理呼叫会话控制功能实体向其对应的终端发送状态检测请求; 若检测结果为异常, 通知所述 IP 多媒体子系统的网元释放所述呼 叫。  Establishing a call of the IP multimedia subsystem between the calling terminal and the called terminal; the proxy call session control function entity sends a status detection request to its corresponding terminal; if the detection result is abnormal, notifying the network element of the IP multimedia subsystem Release the call.
2. 根据权利要求 1所述的呼叫管理方法, 其特征在于, 在主叫终端与被叫 终端之间建立 IP多媒体子系统的呼叫包括: 2. The call management method according to claim 1, wherein the establishing a call of the IP multimedia subsystem between the calling terminal and the called terminal comprises:
所述主叫终端向所述被叫终端发送会话请求消息;  The calling terminal sends a session request message to the called terminal;
所述被叫终端根据接收到的所述会话请求消息发送会话请求响应消 息;  The called terminal sends a session request response message according to the received session request message;
所述代理呼叫会话控制功能实体根据所述会话请求响应消息设置检 测时长, 并开始计时, 其中, 所述代理呼叫会话控制功能实体包括主叫 代理呼叫会话控制功能实体和被叫代理呼叫会话控制功能实体;  The proxy call session control function entity sets a detection duration according to the session request response message, and starts timing, where the proxy call session control function entity includes a calling proxy call session control function entity and a called proxy call session control function. Entity
所述主叫终端向所述被叫终端发送会话确认消息。  The calling terminal sends a session confirmation message to the called terminal.
3. 根据权利要求 2所述的呼叫管理方法, 其特征在于, 代理呼叫会话控制 功能实体向其对应的终端发送状态检测请求包括: 所述主叫代理呼叫会话控制功能实体在到达所述检测时长的一半 时, 向所述主叫终端发送能力查询 OPTIONS消息; The call management method according to claim 2, wherein the proxy call session control function entity sends a status detection request to its corresponding terminal, including: the calling proxy call session control function entity arrives at the detection duration Half of the time, sending a capability query OPTIONS message to the calling terminal;
所述被叫代理呼叫会话控制功能实体在到达所述检测时长的一半 时, 向所述被叫终端发送所述 OPTIONS消息。  The called proxy call session control function entity sends the OPTIONS message to the called terminal when it reaches half of the detection duration.
4. 根据权利要求 3所述的呼叫管理方法, 其特征在于, 所述检测结果为异 常包括: The call management method according to claim 3, wherein the detecting result is abnormal:
所述主叫代理呼叫会话控制功能实体在所述检测时长内未收到所述 OPTIONS响应消息。  The calling proxy call session control function entity does not receive the OPTIONS response message within the detection duration.
5. 根据权利要求 3所述的呼叫管理方法, 其特征在于, 所述检测结果为异 常包括: The call management method according to claim 3, wherein the detection result is different Often include:
所述主叫代理呼叫会话控制功能实体收到所述 OPTIONS响应消息, 其中, 所述 OPTIONS响应消息的响应码为 481。  The calling proxy call session control function entity receives the OPTIONS response message, where the response code of the OPTIONS response message is 481.
6. 根据权利要求 1至 5中任一项所述的呼叫管理方法, 其特征在于, 通知 所述 IP多媒体子系统的网元释放所述呼叫包括: The call management method according to any one of claims 1 to 5, wherein the notifying the network element of the IP multimedia subsystem to release the call comprises:
所述主叫代理呼叫会话控制功能实体释放所述呼叫, 并向所述被叫 终端发送结束会话消息;  The calling proxy call session control function entity releases the call and sends an end session message to the called terminal;
所述 IP 多媒体子系统的中间网元与所述被叫终端根据所述结束会 话消息释放所述呼叫。  The intermediate network element of the IP multimedia subsystem and the called terminal release the call according to the end session message.
7. 根据权利要求 3所述的呼叫管理方法, 其特征在于, 还包括: The call management method according to claim 3, further comprising:
若所述主叫代理呼叫会话控制功能实体收到所述 OPTIONS 响应消 息, 且所述 OPTIONS响应消息的响应码不为 481 , 所述主叫代理呼叫会 话控制功能实体重新开始计时。  If the calling proxy call session control function entity receives the OPTIONS response message, and the response code of the OPTIONS response message is not 481, the calling proxy call session control function entity restarts timing.
8. 根据权利要求 3所述的呼叫管理方法, 其特征在于, 所述检测结果为异 常包括: The call management method according to claim 3, wherein the detecting result is abnormal:
所述被叫代理呼叫会话控制功能实体在所述检测时长内未收到来自 所述被叫终端的所述 OPTIONS响应消息。  The called proxy call session control function entity does not receive the OPTIONS response message from the called terminal within the detection duration.
9. 根据权利要求 3所述的呼叫管理方法, 其特征在于, 所述检测结果为异 常包括: 9. The call management method according to claim 3, wherein the detecting result is abnormal:
所述被叫代理呼叫会话控制功能实体收到来自所述被叫终端的所述 OPTIONS响应消息, 且所述 OPTIONS响应消息的响应码为 481。  The called proxy call session control function entity receives the OPTIONS response message from the called terminal, and the response code of the OPTIONS response message is 481.
10. 根据权利要求 1、 2、 3、 8或 9中任一项所述的呼叫管理方法, 其特征在 于, 通知所述 IP多媒体子系统的网元释放所述呼叫包括: The call management method according to any one of claims 1, 2, 3, 8 or 9, wherein the notifying the network element of the IP multimedia subsystem to release the call comprises:
所述被叫代理呼叫会话控制功能实体释放所述呼叫, 并向所述主叫 终端发送结束会话消息;  The called proxy call session control function entity releases the call and sends an end session message to the calling terminal;
所述 IP 多媒体子系统的中间网元与所述主叫终端根据所述结束会 话消息释放所述呼叫。  The intermediate network element of the IP multimedia subsystem and the calling terminal release the call according to the end session message.
11. 居权利要求 10所述的呼叫管理方法, 其特征在于, 还包括: 若所述被叫代理呼叫会话控制功能实体收到所述 OPTIONS 响应消 息, 且所述 OPTIONS响应消息的响应码不为 481 , 所述被叫代理呼叫会 话控制功能实体重新开始计时。 一种用于 IP多媒体子系统的呼叫管理装置, 其特征在于, 包括: 11. The call management method of claim 10, further comprising: If the called proxy call session control function entity receives the OPTIONS response message, and the response code of the OPTIONS response message is not 481, the called proxy call session control function entity restarts timing. A call management apparatus for an IP multimedia subsystem, comprising:
建立模块,用于在主叫终端与被叫终端之间建立 IP多媒体子系统的 呼叫;  Establishing a module for establishing a call of an IP multimedia subsystem between the calling terminal and the called terminal;
检测模块, 用于代理呼叫会话控制功能实体向其对应的终端发送状 态检测请求;  a detecting module, configured to send, by the proxy call session control function entity, a status detection request to its corresponding terminal;
释放模块, 用于当检测结果为异常时, 通知所述 IP多媒体子系统的 网元释放所述呼叫。  And a releasing module, configured to notify the network element of the IP multimedia subsystem to release the call when the detection result is abnormal.
PCT/CN2010/074099 2009-08-12 2010-06-18 Method and apparatus for call management in internet protocol multimedia subsystem WO2011017978A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200910166114.2 2009-08-12
CN200910166114.2A CN101997850B (en) 2009-08-12 2009-08-12 Call management method and device for IP (Internet Protocol) multimedia subsystem

Publications (1)

Publication Number Publication Date
WO2011017978A1 true WO2011017978A1 (en) 2011-02-17

Family

ID=43585928

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2010/074099 WO2011017978A1 (en) 2009-08-12 2010-06-18 Method and apparatus for call management in internet protocol multimedia subsystem

Country Status (2)

Country Link
CN (1) CN101997850B (en)
WO (1) WO2011017978A1 (en)

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2012163021A1 (en) * 2011-10-27 2012-12-06 华为技术有限公司 Method and server for exception handling during call connection
CN102523280B (en) * 2011-12-13 2017-09-15 融创天下(上海)科技发展有限公司 It is a kind of to transmit abnormal detection method, device, server and the system disconnected of control
CN103516685A (en) * 2012-06-25 2014-01-15 中国移动通信集团公司 Method and system for obtaining terminal connecting state in IMS network, and equipment
CN103812762B (en) * 2013-11-27 2017-12-01 大唐移动通信设备有限公司 A kind of method and system for sending instant message
CN103685286A (en) * 2013-12-18 2014-03-26 大唐移动通信设备有限公司 Method and device for releasing session resources
WO2018209709A1 (en) * 2017-05-19 2018-11-22 华为技术有限公司 Method and apparatus for establishing call
CN110768816B (en) * 2018-07-27 2022-04-15 成都鼎桥通信技术有限公司 Multimedia service exception protection method and device
CN109299182A (en) * 2018-11-13 2019-02-01 郑州云海信息技术有限公司 The management method and device of the session connection of database

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100417276C (en) * 2004-05-21 2008-09-03 华为技术有限公司 Call state detecting method

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100461880C (en) * 2005-06-07 2009-02-11 华为技术有限公司 Voice service realizing method based on service triggering
CN100589641C (en) * 2006-07-12 2010-02-10 中兴通讯股份有限公司 A method for preventing call session control function entity from active resource hangup
CN101227704B (en) * 2007-01-19 2011-04-06 华为技术有限公司 System, apparatus and method for switching multi-module terminal field
CN101489242A (en) * 2008-01-18 2009-07-22 华为技术有限公司 Method and apparatus for service recovery

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100417276C (en) * 2004-05-21 2008-09-03 华为技术有限公司 Call state detecting method

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
S. DONOVAN ET AL.: "Session Timers in the Session Initiation Protocol (SIP).", THE INTERNET SOCIETY (2005)., 30 April 2005 (2005-04-30), pages 20 - 25 *

Also Published As

Publication number Publication date
CN101997850B (en) 2014-04-09
CN101997850A (en) 2011-03-30

Similar Documents

Publication Publication Date Title
WO2011017978A1 (en) Method and apparatus for call management in internet protocol multimedia subsystem
EP3051787B1 (en) Ip multimedia subsystem, proxy session control apparatus, and communication control method
US8730917B2 (en) Method and system for realizing single radio voice call continuity
JP5173607B2 (en) Communications system
CN107079230B (en) Method and apparatus for establishing a VoLTE call
WO2016062008A1 (en) Disaster tolerance method, network element, server and storage medium
JP2004535645A (en) Method and system for handling network identified emergency sessions
US9060366B2 (en) Maintaining connectivity during call-setup
EP3563541B1 (en) Push notification enablement for sip-based networks
WO2010051741A1 (en) Method, user device and server for multimedia session transfer
WO2022267933A1 (en) Paging method, terminal, and network side device
WO2012024908A1 (en) Method and system for reporting terminal capability,
JP5299006B2 (en) Session timer activation method and SIP server
US11864265B2 (en) Proxy-call session control function (P-CSCF) restoration
CN106549901B (en) Service triggering method and device
CN102111899B (en) Session keep-alive method and device
WO2011018017A1 (en) Session processing method and device and communication system
WO2012013094A1 (en) Session establishment method and system based on dialog correlation identifier
WO2012071882A1 (en) Session detection method, device and session initiation protocol server
WO2011127790A1 (en) Method and system for keeping single radio voice call continuity session alive
US11632405B2 (en) Proxy-call session control function (P-CSCF) restoration
WO2012130126A1 (en) Switchover control method and system based on ims
WO2012129979A1 (en) Method, system, and device for ring state domain switchover
WO2011032425A1 (en) Method and system for implementing differentiated ringing in call waiting service
WO2007109970A1 (en) Method, system and device for controlling session timer

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 10807923

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 10807923

Country of ref document: EP

Kind code of ref document: A1