WO2012159483A1 - 语音呼叫处理方法及业务连续性服务器 - Google Patents

语音呼叫处理方法及业务连续性服务器 Download PDF

Info

Publication number
WO2012159483A1
WO2012159483A1 PCT/CN2012/072678 CN2012072678W WO2012159483A1 WO 2012159483 A1 WO2012159483 A1 WO 2012159483A1 CN 2012072678 W CN2012072678 W CN 2012072678W WO 2012159483 A1 WO2012159483 A1 WO 2012159483A1
Authority
WO
WIPO (PCT)
Prior art keywords
media
domain
service continuity
remote
remote end
Prior art date
Application number
PCT/CN2012/072678
Other languages
English (en)
French (fr)
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 WO2012159483A1 publication Critical patent/WO2012159483A1/zh

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/1046—Call controllers; Call servers
    • 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
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0022—Control or signalling for completing the hand-off for data sessions of end-to-end connection for transferring data sessions between adjacent core network technologies
    • H04W36/00224—Control or signalling for completing the hand-off for data sessions of end-to-end connection for transferring data sessions between adjacent core network technologies between packet switched [PS] and circuit switched [CS] network technologies, e.g. circuit switched fallback [CSFB]
    • H04W36/00226—Control or signalling for completing the hand-off for data sessions of end-to-end connection for transferring data sessions between adjacent core network technologies between packet switched [PS] and circuit switched [CS] network technologies, e.g. circuit switched fallback [CSFB] wherein the core network technologies comprise IP multimedia system [IMS], e.g. single radio voice call continuity [SRVCC]

Definitions

  • the present invention relates to the field of communications, and in particular to a voice call processing method and a service continuity server. Background technique
  • IMS IP Multimedia Subsystem
  • IP Multimedia Subsystem IP Multimedia Subsystem
  • 3GPP 3rd Generation Partnership Project
  • SIP Session Initial Protocol
  • Communication is independent of access mode. It can have multiple multimedia service control functions and bearer separation, call and session separation, application and service separation, service and network separation, and mobile network and Internet service integration.
  • VCC Voice Call Continuity refers to maintaining the continuity of voice services when a UE (User Terminal) moves between a network supporting VoIP (Internet Telephony) services and a network that does not support VoIP services.
  • VoIP Internet Telephony
  • the VoIP voice service bearer on the source network will be smoothly switched to the target network CS (circuit switched) domain, and vice versa.
  • VCC can be divided into DRVCC (Dual Radio VCC) and SRVCC (Single Radio VCC).
  • the DRVCC corresponds to the UE of Dual Radio, that is, the UE can support two types of Radio at the same time. Realize the user's voice switching between IMS and CS in the Dual Radio environment.
  • SRVCC implements voice switching between IMS and CS in the environment of Single Radio for wireless users.
  • the SRVCC corresponds to the UE of the Single Radio, that is, the UE can only use one of the 2G/3G Radio and the LTE Radio at the same time.
  • the SR (single radio) requirement is proposed by the terminal manufacturer, and the purpose is to reuse the 2G/ RF and related circuits for 3G, LTE networks.
  • SRVCC a standard flow method for SRVCC ringing state switching called mode is provided in 3GPP.
  • the ringing state domain switching procedure is required, and the offer/answer negotiation (ie, resource negotiation) of the session must be successful before the handover, otherwise the SCC AS (the service continuity server) receives the ringing state domain switching request.
  • the UPDATE message cannot be used to update the media information of the remote (calling client), resulting in unsuccessful domain switching.
  • the status of the media resource status before the handover is not successfully negotiated. In this case, how to ensure the successful completion of the domain handover process is a problem that needs to be solved.
  • the present invention provides a voice call processing method and a service continuity server to solve at least the problem of how to ensure that the domain handover process is successfully completed in the case where the media resource state before the ringing state domain switching is not successfully negotiated.
  • a voice call processing method including: the service continuity server receives a domain handover request sent by the local end, and determines that the initial session ringing media resource state negotiation between the local end and the remote end is unsuccessful. The service continuity server uses the media information carried in the domain switch request sent by the local end to update the remote end.
  • the step of the service continuity server using the media information carried in the domain switching request sent by the local end to update the remote end includes: the service continuity server sends the fake media information to the remote end by using the temporary response message, and completes the remote end.
  • the method further includes: the service continuity server acquiring the media capability information of the remote end, and completing the media resource status negotiation between the local end and the remote end.
  • the method further includes: determining, by the service continuity server, that the local end cancels the response in the CS domain, and releases the call in the PS domain or the IMS domain before the local end.
  • the service continuity server receives the domain switching request sent by the local end, and determines that the initial session ringing media resource state negotiation between the local end and the remote end is unsuccessful, the service continuity server further includes: the service continuity server association local end Distal mouth.
  • a service continuity server including: a determining module, configured to receive a domain switching request sent by the local end, and determine an initial session ringing state of the media resource state negotiation between the local end and the remote end Unsuccessful; update module, set to use the media information carried in the domain switch request sent by the local end to update the remote end.
  • the update module is configured to send the fake media information to the remote end by using the temporary response message to complete the media resource status negotiation of the remote end, wherein the fake media information refers to the service continuity server before carrying the temporary response message.
  • the media information carried in the media message, or the configured media; the update message carries the media information carried in the domain switching request to update the remote end.
  • the service continuity server further includes: a negotiation module, configured to: after the update module updates the remote end, obtain the media capability information of the remote end, and complete the media resource status negotiation between the local end and the remote end.
  • the service continuity server further includes: a release module, configured to: after the negotiation module completes the media resource state negotiation between the local end and the remote end, determine that the local end picks up the response in the CS domain, and releases the local end in the PS domain or the IMS. Domain call.
  • the determining module is further configured to: after receiving the domain switching request sent by the local end, determine that the local end and the far end are associated before the initial session ringing state of the media resource state negotiation is unsuccessful.
  • the service continuity server uses the update remote end carried in the domain switching request sent by the local end, and solves the prior art in the ringing state domain. If the media resource status is not successfully negotiated before the switchover, the problem of the switchover cannot be successfully performed, and the domain switch process can be successfully completed even if the media resource state negotiation is unsuccessful before the domain switchover.
  • FIG. 1 is a flow chart of a 3GPP SRVCC ringing state switching called mode according to the related art
  • FIG. 2 is a flow chart of steps of a voice call processing method according to a first embodiment of the present invention
  • FIG. 4 is a flow chart of a method for a voice call processing method according to a second embodiment of the present invention
  • FIG. 1 is a flow chart of a 3GPP SRVCC ringing state switching called mode according to the related art
  • FIG. 2 is a flow chart of steps of a voice call processing method according to a first embodiment of the present invention
  • FIG. 4 is a flow chart of a method for a voice call processing method according to a second embodiment of the present invention
  • FIG. 1 is a flow chart of a 3GPP SRVCC ringing state switching called mode according to the related art
  • FIG. 2 is a flow chart of steps of a voice call processing method according to a first embodiment of the present invention
  • FIG. 4 is a flow chart of
  • FIG. 4 is a flowchart of a real-time media relay SRVCC ringing state switching called mode according to Embodiment 3 of the present invention; A fourth embodiment of a media real-time conducting DRVCC ringing state switching called mode flow chart; and FIG. 6 is a structural block diagram of a service continuity server according to Embodiment 5 of the present invention.
  • BEST MODE FOR CARRYING OUT THE INVENTION will be described in detail with reference to the accompanying drawings. It should be noted that the embodiments in the present application and the features in the embodiments may be combined with each other without conflict.
  • the SRVCC ringing state domain switching in 3GPP is first introduced. Referring to FIG.
  • the MSC replaces the UE to initiate a ringing state domain switching request in the SRVCC ringing state domain switching process in the 3GPP, and the SCC AS uses the UPDATE message to update the remote end when receiving the domain switching operation request; After the completion, the SCC AS sends an INFO message to notify the MSC of the session information, and carries the handover mode.
  • the MSC sends an INK with a response identifier to notify the SCC AS that the SCC AS determines that the called party has picked up the call. Then send a 200 OK message to the calling party to complete the switching process.
  • Step S1001: 13 ⁇ 4_:6 carries a caller SDP (Session Description Protocol) to initiate a call to the SRVCC user UE_A in the PS (Packet Switched) domain, And UE_A has been anchored to the SCC AS (Business Continuity Server), and UE_A replies with the 180 ringing message with the called SDP.
  • SDP Session Description Protocol
  • Step S1002 The UE_A reports the radio access signal to the E-UTRAN (Evolved Universal Land-Based Radio Access Network), and the E-UTRAN determines to trigger the SRVCC handover (SRVCC handover) to the CS domain according to the radio access signal.
  • the MSC Mobile Switching Center
  • STN-SR Single Radio Session Switching Number
  • UE_A is always ringing.
  • Step S1003 The MSC initiates an initial INVITE session switching request, and carries the Request-URI as an SDP supported by the STN-SR and the P MGW (Media Gateway).
  • Step S1004 The IM CN (IP Multimedia Core Network) forwards the INVITE request of the session handover to the SCC AS.
  • Step S1004a The SCC AS associates the local end with the remote end. Because the initial resource has been negotiated when the primary and the called party are ringing, the SCC AS prepares an update operation for the remote end.
  • Step S1005 The SCC AS sends an UPDATE message to update the remote end, and the segment media SDP indicates that the resource is available.
  • Step S1006 The IM CN forwards the UPDATE message to the terminal UE_B.
  • Step S1008 The IM CN forwards 200 OK to the SCC AS.
  • Step S1009 The SCC AS sends a 183 message with terminal media capability.
  • Step S1010 The IM CN forwards 183 the message to the MSC.
  • Step S1011 The MSC replies to the Prack.
  • Step S1012 The IM CN forwards the Prack to the SCC AS.
  • Step S1013 The SCC AS replies to the PACK 200OK.
  • Step S1014 The IM CN forwards 200 OK to the MSC.
  • Step S1015 The SCC AS sends an INFO message request, including session related information, carries the SCC (Service Continuity Control), the called handover identifier, and the state is ready.
  • SCC Service Continuity Control
  • Step S1016 The IM CN forwards the INK message to the MSC, and the MSC receives the INK message, and determines that the called ringing state is switched according to the content of the message.
  • Step S1017 The MSC replies to the INFO response message 200OK.
  • Step S1018 The IM CN forwards the 200 ⁇ (INFO) message.
  • Step S1019 When the MSC receives the INK message carrying the session related information, the MSC enters a call delivery state.
  • Step SI 020a The called user UE_A answers the number in the CS domain.
  • Step S1021 After receiving the CS Connect message of the called user on the off-hook of the CS, the MSC sends an INFO message with the response session information to the IM CN.
  • Step S1022 The IM CN forwards the INFO message with the response information to the SCC AS.
  • Step S1023 The SCC AS replies to the response 200 OK message of the INFO.
  • Step S1024 The IM CN forwards the 200 OK (INFO) message to the MSC.
  • Step S1025 The SCC AS receives the INFO message, and determines that the called party has picked up the answer, and sends a 200 OK message of the off-hook response.
  • Step S1026 The IM CN forwards the response response message to the calling user UE_B.
  • Step S1027 The calling user UE B replies with an ACK.
  • Step S1028 The IM CN forwards the ACK to the SCC AS.
  • Step S1029 The SCC AS sends a 200 OK (INVITE) response message to inform the MSC that the handover is successful (step S1030: IM CN forwards the 200 OK (INVITE) message to the MSC.
  • step S1031 The MSC sends a CS Connect Ack message to the UE_A, indicating that the handover is successful.
  • S 1032 The MSC replies with an ACK message.
  • Step S1033 The IM CN forwards the ACK to the SCC AS.
  • Steps S1034-S1041 The SCC AS sends CANCEL to release the call originally called in the PS domain.
  • Embodiment 1 Referring to FIG. 2, a flow chart of steps of a voice call processing method according to Embodiment 1 of the present invention.
  • the voice call processing method of this embodiment includes steps S2002 to S2004: Step S2002: Business Continuity Server
  • the domain switch request sent by the local end is received, and the negotiation of the media state of the initial session ringing state of the local end and the remote end is unsuccessful.
  • the service continuity server When the initial session establishment is in the ringing state, the local and remote session offer/answer status is not Successful negotiation, that is, when the negotiation between the local and remote media resources is unsuccessful, the service continuity server, such as SCC AS or VCC AS, does not receive Corresponding negotiation reply information. In this case, the service continuity server can determine whether the media resource status negotiation between the local end and the remote end is successful according to whether the corresponding negotiation reply information is received.
  • the switching center MSC replaces the mobile terminal UE, or the UE initiates a domain switching operation request, and performs a domain switching operation.
  • the service continuity server receives the domain switching request sent by the local end, and determines the initial session ringing state of the local end and the remote end.
  • Step S2004 The service continuity server uses the media information carried in the domain switching request sent by the local end to update the remote end.
  • the service continuity server receives the domain switching request sent by the local end, and determines that the media resource status negotiation is unsuccessful. In this case, the service continuity server uses the domain switching request.
  • the media information is updated remotely.
  • the service continuity server cannot use the UPDATE message to update the media information of the remote end (the calling user), which causes the domain switch to be unsuccessful. .
  • Embodiment 2 Referring to FIG. 3, a flow chart of steps of a voice call processing method according to Embodiment 2 of the present invention is shown.
  • the voice call processing method of this embodiment includes steps S3002 to S3008: Step S3002: When the initial session establishment is in the ringing state, the session offer/answer state is not successfully negotiated.
  • Step S3004 The service continuity server receives the domain handover request, and associates the local end with the remote end.
  • the local end is the called user end
  • the remote end is the called user end.
  • the service continuity server SCC AS or VCC AS obtains the association between the local end and the remote end by acquiring the information of the remote end.
  • Step S3006 The service continuity server sends the media information in the domain handover request INVITE message to the remote end by using an UPDATE (update) message. Specifically, the service continuity server first sends the fake media information to the remote end by using the temporary response message to complete the remote media resource status negotiation.
  • the fake media information in the domain switching request INVITE message is sent by using an UPDATE message.
  • the fake media information may be the media information carried in the message carrying the media before the service continuity server sends the temporary response message, or may be the configured media, but is not limited to the two.
  • the temporary response message is used to carry the fake media information, and the existing message is effectively utilized, and the existing process is not modified too much, which saves the implementation cost and improves the implementation efficiency.
  • the temporary response message may be a 183 message, but is not limited thereto. It should be understood by those skilled in the art that any suitable message may carry the above information and send it to the remote end to complete the remote media resource status negotiation process.
  • Step S3008 The service continuity server determines that the service user (the local called user) has picked up the call in the CS domain, and releases the call of the service user (the called user) in the PS domain or the IMS domain.
  • Embodiment 3 Referring to FIG. 4, a flow chart of a media real-time conduction SRVCC ringing state switching called mode according to Embodiment 3 of the present invention is shown.
  • the handover procedure of this embodiment includes steps S4001 to S4041: Step S4001: UE B carries the calling SDP to initiate a call to the SRVCC user UE_A in the PS domain, and UE_A has been anchored to the SCC AS.
  • Step S4002 The UE A reports the radio access signal to the E-UTRAN, and the E-UTRAN determines to trigger the SRVCC handover to the CS domain according to the radio access signal.
  • the MSC carries the STN-SR to initiate a session switching operation.
  • UE_A is always ringing.
  • Step S4003 The MSC initiates an initial INVITE session switching request, and carries a Request-URI (request information including the uniform resource identifier information) as an STN-SR, and an SDP supported by the MGW.
  • Request-URI request information including the uniform resource identifier information
  • Step S4004 The IM CN forwards the INVITE request of the session switch to the SCC AS.
  • Step S4004a The SCC AS associates the local end with the remote end to perform remote update. In other words, the SCC AS obtains the remote information to associate the local end with the remote end. And, the media resource is updated to the far end. Because the initial resource is not negotiated when the primary and the called are ringing, the SCC AS sends a 183 message with the media information to update the remote end.
  • the remote user refers to the calling user
  • the local user refers to the called user.
  • Step S4004b The SCC AS sends a 183 message carrying the fake media information to the IM CN; the piece of media information indicates that the resource is available.
  • Step S4004 C The IM CN forwards the 183 message of the strip media information to the remote user.
  • Steps S4004d-S4004e The remote user replies to Prack to SCC AS; the SCC AS replies with 200 OK (Prack). Prack is a temporary response message, which is a reply message corresponding to the 183 message.
  • Step S4005 The SCC AS sends an UPDATE (SDP) message to update the remote end.
  • Step S4006 The IM CN forwards the UPDATE (SDP) to the remote user.
  • ', _- Step S4007 Remote response 200 OK (UPDATE&&SDP), carrying the media capabilities of the remote user ⁇
  • Step S4008 The IM CN forwards 200 ⁇ (UPDATE&&SDP) to the SCC AS.
  • Step S4010 The IM CN forwards the 183 message of the stripe media to the MSC.
  • Step S4011 The MSC replies to the Prack.
  • Step S4012 The IM CN forwards the Prack to the SCC AS.
  • Step S4013 The SCC AS replies to the 200 OK of the Prack.
  • Step S4015 The SCC AS sends an INFO (information) message request, including session related information, carries the SCC called handover identifier, and the state is ready. In this step, the status is ready to be that the SCC AS has completed the switching action.
  • Step S4016 The IM CN forwards the INK message to the MSC; the MSC receives the INK) message, and determines that the called ringing state is switched according to the content of the message.
  • Step S4017 The MSC replies to the INFO response message 200OK.
  • Step S4018 The IM CN forwards the 200 ⁇ (INFO) message.
  • Step S4019 When the MSC receives the INK message carrying the session related information, the MSC enters a call delivery state.
  • Step S4020a The called user UE A answers the number in the CS domain and picks up the phone.
  • Step S4020 UE A sends a CS Connect notification MSC C.
  • Step S4021 After receiving the CS Connect message of the called user on the off-hook of the CS, the MSC sends an INFO message with the response session information to the IM CN.
  • Step S4022 The IM CN forwards the INFO message with the response information to the SCC AS.
  • Step S4023 The SCC AS replies to the response 200 OK message of the INFO.
  • Step S4024 The IM CN forwards the 200 OK (INFO) message to the MSC.
  • Step S4025 The SCC AS receives the INFO message, and determines that the called party has answered the call, and sends a 200 OK message of the off-hook response.
  • Step S4026 The IM CN forwards the response response message to the calling user UE_B.
  • Step S4027 The calling user UE_B replies with an ACK.
  • Step S4028 The IM CN forwards the ACK to the SCC AS.
  • Step S4029 The SCC AS sends a 200 OK (INVITE) response message to inform the MSC that the handover is successful.
  • Step S4030 The IM CN forwards the 200 OK (INVITE) message to the MSC.
  • Step S4031 The MSC sends a CS Connect Ack message to the UE_A, indicating that the handover is successful.
  • Step S4032 The MSC replies with an ACK message.
  • Step S4033 The IM CN forwards the ACK to the SCC AS. At this point, the media is carried and the handover process is completed.
  • Steps S4034-S4041 The SCC AS sends CANCEL to release the call that was originally called in the PS domain.
  • the domain switching request message of the SRVCC ringing state domain handover is initiated by the MSC instead of the UE.
  • Embodiment 4 Referring to FIG. 5, a flow chart of a media real-time turn-on DRVCC ringing state switching called mode according to Embodiment 4 of the present invention is shown.
  • the handover procedure of this embodiment includes steps S5001 to S5039: Step S5001: UE B carries the calling SDP to initiate a call to the VCC user UE_A in the IMS domain, and UE A has been anchored to the VCC AS; UE A replies with no A 180 ringing message called SDP; this session is ringing.
  • the service continuity server is a VCC AS.
  • UE A replies with the 180 ringing message without the called SDP, which indicates that the initial media resource status negotiation of the calling party is unsuccessful.
  • Step S5002 The UE_A decides to carry the domain switching operation by carrying the VDN (VCC Domain Transfer Number) in the CS domain due to the weakening of the signal or the preference of the user. The UE_A is directly in the ringing state.
  • Step S5004 The IM CN forwards the INVITE request of the session switch to the VCC AS.
  • Step S5005 The VCC AS associates the local end with the remote end to perform remote update. Because the initial resource is not negotiated when the primary and the called are ringing, the VCC AS sends the 183 message of the fake media information to update the remote end.
  • Step S5006 The VCC AS sends a 183 message carrying the fake media information to the IM CN; the media information indicates that the resource is available.
  • Step S5007 The IM CN forwards the 183 message of the strip media information to the remote user.
  • Step S5009 The VCC AS replies with 200 OK (Prack).
  • Step S5010 The VCC AS sends an UPDATE (SDP) message to update the far end.
  • Step S5011 The IM CN forwards the UPDATE (SDP) to the remote user.
  • Step S5012 The remote end returns 200 OK (UPDATE&&SDP), and carries the media capability information of the remote user.
  • Step S5013 The IM CN forwards 200 OK (UPDATE&&SDP) to the VCC AS.
  • Step S5014 The VCC AS sends a 183 message carrying the SDP to the IM CN; the media information indicates that the resource is available.
  • Step S5015 The IM CN forwards the 183 message of the strip media information to the UE_A terminal in the CS domain.
  • Step S5016 The Prack is replied to the UE_A terminal in the CS domain.
  • Step S5017 The IM CN forwards the Prack to the VCC AS.
  • Step S5018 The VCC AS replies to the PACK 200OK.
  • Step S5019 The IM CN forwards the 200 OK to the UE A terminal in the CS domain, and the step S5020: the UE A sends an INFO message with the response session information to the IM CN.
  • Step S5022 The VCC AS replies to the response of the INFO 200 OK message c
  • Step S5023 The IM CN forwards the 200 OK (INFO) message to the UE A.
  • Step S5024 The VCC AS determines that the local resource negotiation is successful, and sends a 200 OK message of the off-hook response.
  • Step S5025 The IM CN forwards the response response message to the calling user UE B.
  • Step S5026 The calling user UE B replies with an ACK.
  • Step S5027 IM CN forwards ACK to VCC ASc
  • Step S5028 VCC AS sends 200 OK (INVITE) response message
  • Step S5029 IM CN forwards 200 OK (INVITE) message to UE A terminal in CS domain
  • step S5030 UE in CS domain
  • a terminal replies ACK message
  • Step S5031 IM CN forwards ACK to VCC ASc until the media carrying is completed, and the switching flow is completed at the same time;
  • Step S5032-S5039 VCC AS sends CANCEL message to release the original called IMS domain Road call
  • the domain handover request message of the DRVCC ringing state domain handover is initiated by the UE.
  • the handover method of this embodiment even if the media resource state of the primary and called ringing states is not negotiated at the initial time, the domain switching process can be successfully completed.
  • Embodiment 5 Referring to FIG. 6, a structural block diagram of a service continuity server according to Embodiment 5 of the present invention is shown.
  • the service continuity server of this embodiment includes: a determining module 602, configured to receive a domain switching request sent by the local end, and determine that the initial session ringing state of the media resource state negotiation is unsuccessful; the updating module 604, The determining module 602 is configured to: when the determining module determines that the initial session ringing media resource state negotiation of the local end and the remote end is unsuccessful, the media information carried in the domain switching request sent by the local end is used to update the remote end.
  • the update module 604 is configured to send the fake media information to the remote end by using the temporary response message to complete the media resource status negotiation of the remote end, where the fake media information may be carried by the service continuity server before sending the temporary response message.
  • the service continuity server of the embodiment further includes: a negotiation module 606, coupled to the update module 604, configured to acquire the media capability information of the remote end after the update module 604 updates the remote end, and complete the local end and the remote end. Media resource status negotiation.
  • the service continuity server of the embodiment further includes: a release module 608, coupled to the negotiation module 606, configured to determine that the local end is already in the CS domain after the negotiation module 606 completes the media resource status negotiation between the local end and the remote end. Off-hook response, release the local call in the PS domain or IMS domain.
  • the determining module 602 of the service continuity server of the embodiment is further configured to: after receiving the domain switching request sent by the local end, determining that the initial session ringing media resource state negotiation between the local end and the remote end is unsuccessful , associated with the local and remote.
  • the method implemented in this embodiment can refer to the related description in the foregoing related method embodiments, and has the beneficial effects of the foregoing related method embodiments, and details are not described herein again. From the above description, it can be seen that the present invention provides a technical solution for DRVCC and SRVCC domain handover in an IMS network architecture, and in particular, a technical solution of a called flow of a user media real-time conduction mode.
  • the service continuity server updates the remote end by using the media information carried in the domain handover request to complete the negotiation, thereby ensuring the smooth completion of the handover process.
  • the SRVCC ringing state domain switching procedure is also applicable to the domain switching in the DRVCC ringing state, except that the DRVCC domain switching is an operation initiated by the terminal UE. It will be apparent to those skilled in the art that the various modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across multiple computing devices.
  • the computing device 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 and, in some cases, may be different from this
  • the steps shown or described are performed sequentially, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module.
  • 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 spirit and scope of the present invention are intended to be included within the scope of the present invention.

Abstract

本发明公开了一种语音呼叫处理方法及业务连续性服务器，其中，语音呼叫处理方法包括：业务连续性服务器确定本端和远端的初始会话振铃态媒体资源状态协商不成功；业务连续性服务器使用本端发送的域切换请求中所携带的媒体信息去更新远端。通过本发明，实现了即使域切换前媒体资源状态协商不成功时，域切换流程也能够顺利完成。

Description

语音呼叫处理方法及业务连续性服务器 技术领域 本发明涉及通信领域， 具体而言， 涉及一种语音呼叫处理方法及业务连续性服务 器。 背景技术
IMS (IP Multimedia Subsystem, 网际协议多媒体子系统） 是未来多媒体通信的发 展方向，也是下一代网络最为重要的组成部分。它是 3GPP ( Third Generation Partnership Project, 第三代合作伙伴计划）提出的支持 IP多媒体业务的子系统， 其显著特征是采 用了 SIP ( Session Initial Protocol, 会话初始协议） 体系， 通信与接入方式无关， 可以 具备多种多媒体业务控制功能与承载能力分离、 呼叫与会话分离、 应用与服务分离、 业务与网络分离， 以及移动网与因特网业务融合等多种能力。
3GPP中， VCC (Voice Call Continuity, 语音呼叫连续性）是指当 UE (用户终端） 在支持 VoIP (网络电话） 业务的网络和不支持 VoIP业务的网络之间移动时， 保持语 音业务的连续性， 即将在源网络的 VoIP语音业务承载平滑切换到目标网络 CS (电路 交换） 域， 反之亦然。
VCC可以分为 DRVCC (Dual Radio VCC, 双射频 VCC)和 SRVCC ( Single Radio VCC,单射频 VCC)。 DRVCC对应 Dual Radio的 UE，即 UE同时可以支持两种 Radio。 实现用户在 Dual Radio的环境下，在 IMS与 CS之间的语音切换。 SRVCC实现无线用 户在 Single Radio的环境下，在 IMS与 CS之间的语音切换。 SRVCC对应 Single Radio 的 UE， 即 UE只能在同一时间使用 2G/3 G的 Radio、 LTE的 Radio中的一种， SR (单 射频）的需求是终端厂商提出的， 其目的是复用 2G/3G、 LTE网络的射频和相关电路。 对于 SRVCC, 3 GPP中提供了 SRVCC振铃态切换被叫模式的标准流程方法。 在 该方法中， 要求振铃态域切换过程， 必须在切换之前保证会话的 offer/answer协商（即 资源协商） 成功， 否则 SCC AS (业务连续性服务器） 接收到振铃态域切换请求时， 无法使用 UPDATE消息去更新远端 （主叫用户端） 的媒体信息， 导致域切换不成功。 但在实际的切换过程中， 经常会出现切换前媒体资源状态未协商成功的情况， 在这种 情况下如何保证域切换过程的顺利完成， 是需要解决的问题。 发明内容 本发明提供了一种语音呼叫处理方法及业务连续性服务器， 以至少解决上述振铃 态域切换前媒体资源状态未协商成功的情况下，如何保证域切换过程顺利完成的问题。 根据本发明的一个方面， 提供了一种语音呼叫处理方法， 包括： 业务连续性服务 器接收到本端发送的域切换请求， 确定本端和远端的初始会话振铃态媒体资源状态协 商不成功； 业务连续性服务器使用本端发送的域切换请求中所携带的媒体信息去更新 远端。 优选地， 业务连续性服务器使用本端发送的域切换请求中所携带的媒体信息去更 新远端的步骤包括：业务连续性服务器使用临时响应消息携带假媒体信息发送给远端， 完成远端的媒体资源状态协商， 其中， 假媒体信息是指业务连续性服务器在发送临时 响应消息之前上一条携带媒体的消息中所携带的媒体信息， 或者是配置的媒体； 通过 更新消息携带域切换请求中所携带的媒体信息， 去更新远端。 优选地， 在更新远端的步骤之后， 还包括： 业务连续性服务器获取远端的媒体能 力信息， 完成本端和远端的媒体资源状态协商。 优选地， 在完成本端和远端的媒体资源状态协商的步骤之后， 还包括： 业务连续 性服务器确定本端在 CS域摘机应答， 释放本端之前在 PS域或 IMS域的呼叫。 优选地， 在业务连续性服务器接收到本端发送的域切换请求之后， 确定本端和远 端的初始会话振铃态媒体资源状态协商不成功之前， 还包括： 业务连续性服务器关联 本端禾口远端。 根据本发明的另一方面， 提供了一种业务连续性服务器， 包括： 确定模块， 设置 为接收到本端发送的域切换请求， 确定本端和远端的初始会话振铃态媒体资源状态协 商不成功； 更新模块， 设置为使用本端发送的域切换请求中所携带的媒体信息去更新 远端。 优选地， 更新模块， 设置为使用临时响应消息携带假媒体信息发送给远端， 完成 远端的媒体资源状态协商， 其中， 假媒体信息是指业务连续性服务器在发送临时响应 消息之前上一条携带媒体的消息中所携带的媒体信息， 或者是配置的媒体； 通过更新 消息携带域切换请求中所携带的媒体信息， 去更新远端。 优选地， 业务连续性服务器还包括： 协商模块， 设置为在更新模块更新远端之后， 获取远端的媒体能力信息， 完成本端和远端的媒体资源状态协商。 优选地， 业务连续性服务器还包括： 释放模块， 设置为在协商模块完成本端和远 端的媒体资源状态协商之后，确定本端在 CS域摘机应答，释放本端之前在 PS域或 IMS 域的呼叫。 优选地， 确定模块， 还设置为在接收到本端发送的域切换请求之后， 确定本端和 远端的初始会话振铃态媒体资源状态协商不成功之前， 关联本端和远端。 通过本发明， 当振铃态域切换前媒体资源状态协商未成功时， 采用业务连续性服 务器将本端发送的域切换请求中所携带的更新远端， 解决了现有技术在振铃态域切换 前媒体资源状态未协商成功的情况下， 无法成功进行切换的问题， 进而达到了即使域 切换前媒体资源状态协商不成功时， 域切换流程也能够顺利完成的效果。 附图说明 此处所说明的附图用来提供对本发明的进一步理解， 构成本申请的一部分， 本发 明的示意性实施例及其说明用于解释本发明， 并不构成对本发明的不当限定。 在附图 中： 图 1是根据相关技术的 3GPP SRVCC振铃态域切换被叫模式流程图； 图 2是根据本发明实施例一的一种语音呼叫处理方法的步骤流程图； 图 3是根据本发明实施例二的一种语音呼叫处理方法的步骤流程图； 图 4是根据本发明实施例三的一种媒体实时导通 SRVCC振铃态域切换被叫模式 流程图； 图 5是根据本发明实施例四的一种媒体实时导通 DRVCC振铃态域切换被叫模式 流程图； 以及 图 6是根据本发明实施例五的一种业务连续性服务器的结构框图。 具体实施方式 下文中将参考附图并结合实施例来详细说明本发明。 需要说明的是， 在不冲突的 情况下， 本申请中的实施例及实施例中的特征可以相互组合。 为便于理解本发明实施例， 首先对 3GPP中的 SRVCC振铃态域切换作以介绍。 参照图 1， 示出了 3GPP SRVCC振铃态域切换被叫模式流程图。 本实施例示出了 3GPP中的 SRVCC振铃态域切换过程中， MSC代替 UE发起振 铃态域切换的请求操作， SCC AS接收到域切换操作请求时， 使用 UPDATE消息去更 新远端； 媒体协商完成后， SCC AS发送 INFO消息通知 MSC相关会话信息， 并携带 切换模式； 被叫 CS号码摘机时， MSC发送带应答标识的 INK)消息通知 SCC AS, SCC AS判断被叫已经摘机应答， 则发送 200OK消息给主叫， 完成切换过程。具体地， 该流程包括步骤 S1001至步骤 S1041 : 步骤 S1001 : 1¾_：6携带主叫 SDP ( Session Description Protocol, 会话描述协议） 发起呼叫到在 PS (Packet Switched, 分组交换）域中的 SRVCC用户 UE_A， 且 UE_A 已经锚定到 SCC AS (业务连续性服务器）， UE_A回复带被叫 SDP的 180振铃消息。 本步骤表明两端资源已经协商成功， 此会话处于振铃状态。 步骤 S1002: UE_A上报无线接入信号给 E-UTRAN (演进的通用陆基无线接入网）， E-UTRAN根据无线接入信号决定触发 SRVCC handover ( SRVCC切换） 至 CS域。 MSC (移动交换中心）携带 STN-SR (单射频会话切换号码）发起会话切换操作。 UE_A 一直处于振铃状态。 步骤 S1003 : MSC 发起初始 INVITE 会话切换请求， 且携带 Request-URI 为 STN-SR, 禾 P MGW (媒体网关） 支持的 SDP。 步骤 S1004: IM CN (IP多媒体核心网）转发会话切换的 INVITE请求至 SCC AS。 步骤 S1004a: SCC AS将本端与远端进行关联， 因之前主被叫振铃状态时初始资 源已经协商好， 故 SCC AS准备对远端的更新操作。 步骤 S1005: SCC AS发送 UPDATE消息去更新远端， 此段媒体 SDP表示资源可 用。 步骤 S1006: IM CN转发此条 UPDATE消息给终端 UE_B。 步骤 S1007: UE_B回复 200OK, 并携带终端媒体能力。 步骤 S1008: IM CN转发 200OK给 SCC AS。 步骤 S1009: SCC AS发送带终端媒体能力的 183消息。 步骤 S1010: IM CN转发 183消息给 MSC。 步骤 S1011 : MSC回复 Prack。 步骤 S1012: IM CN转发 Prack至 SCC AS。 步骤 S1013 : SCC AS回复 Prack的 200OK。 步骤 S1014: IM CN转发 200OK至 MSC。 步骤 S1015: SCC AS发送 INFO消息请求，包括会话相关信息，携带 SCC ( Service Continuity Control, 业务连续性控制） 被叫切换标识， 且状态已经准备妥当。 步骤 S1016: IM CN转发此 INK)消息给 MSC， MSC接收到 INK)消息， 根据消 息内容判断出为被叫振铃态域切换。 步骤 S1017: MSC回复 INFO的响应消息 200OK。 步骤 S1018: IM CN转发 200ΟΚ (INFO) 消息。 步骤 S1019: MSC接收到携带会话相关信息的 INK)消息时， 进入呼叫传递状态 (Call delivered state )。 步骤 SI 020a: 被叫用户 UE_A在 CS域的号码摘机应答。 步骤 S1020: UE_A发送 CS Connect通知 MSC。 步骤 S1021 : MSC接收被叫用户在 CS摘机的 CS Connect消息后， 发送带应答会 话信息的 INFO消息给 IM CN。 步骤 S1022: IM CN转发此带应答信息的 INFO消息给 SCC AS。 步骤 S1023 : SCC AS回复 INFO的响应 200OK消息。 步骤 S1024: IM CN转发 200OK (INFO) 消息给 MSC。 步骤 S1025: SCC AS接收到 INFO消息， 判断出被叫已经摘机应答， 则发送摘机 应答的 200OK消息。 步骤 S1026: IM CN转发此应答响应消息给主叫用户 UE_B。 步骤 S1027: 主叫用户 UE B回复 ACK。 步骤 S1028: IM CN转发 ACK至 SCC AS。 步骤 S1029: SCC AS发送 200OK (INVITE) 响应消息， 以告知 MSC切换成功( 步骤 S1030: IM CN转发 200OK (INVITE) 消息至 MSC。 步骤 S1031： MSC发送 CS Connect Ack消息给 UE_A， 告知切换成功。 步骤 S 1032： MSC回复 ACK消息。 步骤 S1033 : IM CN转发 ACK至 SCC AS。 步骤 S1034-S1041： SCC AS发送 CANCEL释放原来被叫在 PS域的那路呼叫。 以下， 通过多个实施例对本发明作以介绍。 实施例一 参照图 2， 根据本发明实施例一的一种语音呼叫处理方法的步骤流程图。 本实施例的语音呼叫处理方法包括步骤 S2002至步骤 S2004: 步骤 S2002: 业务连续性服务器接收到本端发送的域切换请求， 确定本端和远端 的初始会话振铃态媒体资源状态协商不成功。 当初始会话建立处于振铃态，本端和远端的会话 offer/answer状态未成功协商， 即 本端和远端的媒体资源状态协商不成功时，业务连续性服务器，如 SCC AS或 VCC AS， 则接收不到相应的协商回复信息。 在这种情况下， 业务连续性服务器能够根据是否接 收到相应的协商回复信息， 来确定本端和远端的媒体资源状态协商是否成功。 当信号衰减时， 可以由移动交换中心 MSC代替移动终端 UE， 或者由 UE自己发 起域切换操作请求， 要求进行域切换操作。 业务连续性服务器接收到本端发送的域切 换请求， 确定本端和远端的初始会话振铃态媒体资源状态协商不成功， 相应地， 进行 步骤 S2004的操作。 步骤 S2004: 业务连续性服务器使用本端发送的域切换请求中所携带的媒体信息 去更新远端。 当信号衰减， 需要进行域切换时， 业务连续性服务器接收到本端发送的域切换请 求， 判断媒体资源状态协商不成功， 在这种情况下， 业务连续性服务器使用域切换请 求中所携带的媒体信息更新远端。 相关技术中，在出现切换前 offer/answer未协商成功时，业务连续性服务器接收到 域切换请求时， 无法使用 UPDATE消息去更新远端 （主叫用户端） 的媒体信息， 导致 域切换不成功。通过本实施例， 当切换前 offer/answer未协商成功时， 业务连续性服务 器使用域切换请求中携带的媒体信息更新远端， 完成协商， 从而保证了即使切换前 offer/answer未协商成功， 切换流程也能顺利完成。 实施例二 参照图 3， 示出了根据本发明实施例二的一种语音呼叫处理方法的步骤流程图。 本实施例的语音呼叫处理方法包括步骤 S3002至步骤 S3008: 步骤 S3002: 初始会话建立处于振铃态时， 会话 offer/answer状态未成功协商。 此 时， 无线接入信号渐弱， 由 MSC代替 UE， 或者由 UE发起域切换请求。 步骤 S3004: 业务连续性服务器收到域切换请求， 关联本端和远端。 本实施例中， 本端为被叫用户端， 远端为主叫用户端。业务连续性服务器 SCC AS 或者 VCC AS通过获取远端的信息， 实现本端和远端的关联。 步骤 S3006: 业务连续性服务器将域切换请求 INVITE 消息中的媒体信息使用 UPDATE (更新） 消息携带发送给远端。 具体地， 业务连续性服务器先使用临时响应消息携带假媒体信息发送给远端， 完 成远端的媒体资源状态协商； 然后， 将域切换请求 INVITE消息中的媒体信息， 使用 UPDATE (更新） 消息发送给远端， 更新远端。 其中， 假媒体信息可以是指业务连续 性服务器在发送临时响应消息之前上一条携带媒体的消息中所携带的媒体信息， 也可 以是配置的媒体， 但不限于此两种。 使用临时响应消息携带假媒体信息， 有效利用了 现有的消息， 不用对现有流程做过多修改， 节约了实现成本， 提高了实现效率。 临时响应消息可以是 183消息， 但不限于此， 本领域技术人员应当明了， 任何适 当的消息， 均可以携带上述信息， 发送给远端， 以完成远端的媒体资源状态协商过程。 步骤 S3008: 业务连续性服务器确定业务用户 （本端被叫用户） 已在 CS域摘机应 答， 释放业务用户 （被叫用户） 之前在 PS域或 IMS域的那路呼叫。 实施例三 参照图 4，示出了根据本发明实施例三的一种媒体实时导通 SRVCC振铃态域切换 被叫模式流程图。 本实施例的切换流程包括步骤 S4001至步骤 S4041 : 步骤 S4001 : UE B携带主叫 SDP发起呼叫到在 PS域中的 SRVCC用户 UE_A， 且 UE_A已经锚定到 SCC AS。 UE A回复未带被叫 SDP的 180振铃消息， 此会话处 于振铃状态。 可以看出， 主被叫振铃状态时初始资源并未协商好。 步骤 S4002: UE A上报无线接入信号给 E-UTRAN, E-UTRAN根据无线接入信 号决定触发 SRVCC handover至 CS域。 MSC携带 STN-SR发起会话切换操作。 UE_A 一直处于振铃状态。 步骤 S4003 : MSC发起初始 INVITE会话切换请求， 且携带 Request-URI (包含统 一资源标识符信息的请求信息） 为 STN-SR, 和 MGW支持的 SDP。 步骤 S4004: IM CN转发会话切换的 INVITE请求至 SCC AS。 步骤 S4004a: SCC AS将本端与远端进行关联， 进行远端更新。 g卩， SCC AS获取远端的信息， 以将本端与远端进行关联。 并且， 对远端进行媒 体资源更新。 因之前主被叫振铃状态时初始资源并未协商好， 故 SCC AS发送带媒体 信息的 183消息更新远端。本实施例中， 远端用户指主叫用户， 本端用户指被叫用户。 步骤 S4004b: SCC AS发送携带假媒体信息的 183消息给 IM CN; 此段媒体信息 表示资源可用。 步骤 S4004C: IM CN转发此条带媒体信息的 183消息给远端用户。 步骤 S4004d-S4004e:远端用户回复 Prack至 SCC AS; SCC AS回复 200OK(Prack)。 Prack为临时响应消息， 是对应于 183消息的回复消息。 步骤 S4005： SCC AS发送 UPDATE ( SDP ) 消息更新远端。 步骤 S4006: IM CN转发 UPDATE ( SDP) 给远端用户。 '、 _- 步骤 S4007: 远端回复 200OK (UPDATE&&SDP), 携带远端用户的媒体能力 ϊ
步骤 S4008: IM CN转发 200ΟΚ (UPDATE&&SDP) 给 SCC AS。 步骤 S4009: SCC AS发送携带 SDP的 183消息给 IM CN; 此段媒体信息表示资 源可用。 步骤 S4010: IM CN转发此条带媒体的 183消息给 MSC。 步骤 S4011 : MSC回复 Prack。 步骤 S4012: IM CN转发 Prack至 SCC AS。 步骤 S4013 : SCC AS回复 Prack的 200OK。 步骤 S4014: IM CN转发 200ΟΚ至 MSC。 步骤 S4015: SCC AS发送 INFO (信息）消息请求，包括会话相关信息，携带 SCC 被叫切换标识， 且状态已经准备妥当。 本步骤中， 状态已经准备妥当是指 SCC AS完成了切换动作。 步骤 S4016: IM CN转发此 INK)消息给 MSC; MSC接收到 INK)消息， 根据消 息内容判断出为被叫振铃态域切换。 步骤 S4017: MSC回复 INFO的响应消息 200OK。 步骤 S4018： IM CN转发 200ΟΚ ( INFO ) 消息。 步骤 S4019: MSC接收到携带会话相关信息的 INK)消息时， 进入呼叫传递状态 (Call delivered state )。 步骤 S4020a: 被叫用户 UE A在 CS域的号码摘机应答。 步骤 S4020: UE A发送 CS Connect通知 MSCC 步骤 S4021 : MSC接收被叫用户在 CS摘机的 CS Connect消息后， 发送带应答会 话信息的 INFO消息给 IM CN。 步骤 S4022: IM CN转发此带应答信息的 INFO消息给 SCC AS。 步骤 S4023： SCC AS回复 INFO的响应 200OK消息。 步骤 S4024: IM CN转发 200OK (INFO) 消息给 MSC。 步骤 S4025: SCC AS接收到 INFO消息， 判断出被叫已经摘机应答， 则发送摘机 应答的 200OK消息。 步骤 S4026: IM CN转发此应答响应消息给主叫用户 UE_B。 步骤 S4027: 主叫用户 UE_B回复 ACK。 步骤 S4028: IM CN转发 ACK至 SCC AS。 步骤 S4029: SCC AS发送 200OK (INVITE) 响应消息， 以告知 MSC切换成功。 步骤 S4030: IM CN转发 200OK (INVITE) 消息至 MSC。 步骤 S4031 : MSC发送 CS Connect Ack消息给 UE_A， 告知切换成功。 步骤 S4032: MSC回复 ACK消息。 步骤 S4033 : IM CN转发 ACK至 SCC AS。 至此媒体携带完成， 同时完成了切换流程。 步骤 S4034-S4041 : SCC AS发送 CANCEL释放原来被叫在 PS域的那路呼叫。 本实施例中， SRVCC振铃态域切换的域切换请求消息由 MSC代替 UE发起。 通 过本实施例的切换方法， 使得即使初始时， 主被叫振铃状态的媒体资源状态未协商好， 域切换过程也能够顺利完成。 实施例四 参照图 5， 示出了根据本发明实施例四的一种媒体实时导通 DRVCC振铃态域切 换被叫模式流程图。 本实施例的切换流程包括步骤 S5001至步骤 S5039: 步骤 S5001 : UE B携带主叫 SDP发起呼叫到在 IMS域中的 VCC用户 UE_A，且 UE A已经锚定到 VCC AS; UE A回复未带被叫 SDP的 180振铃消息； 此会话处于 振铃状态。 本实施例中， 业务连续性服务器为 VCC AS。 UE A回复未带被叫 SDP的 180振 铃消息， 由此说明主被叫初始媒体资源状态协商未成功。 步骤 S5002: UE_A因信号减弱或者个人喜好原因决定在 CS域携带 VDN (VCC Domain Transfer Number, VCC域切换号码）发起域切换操作； UE_A—直处于振铃状 态。 步骤 S5003 : UE A在 CS域发起初始 INVITE会话切换请求，且携带 Request-URI 为 VDN， SDP为 UE终端能力。 步骤 S5004: IM CN转发会话切换的 INVITE请求至 VCC AS。 步骤 S5005: VCC AS将本端与远端进行关联， 进行远端更新， 因之前主被叫振铃 状态时初始资源并未协商好， 故 VCC AS发送假媒体信息的 183消息更新远端。 步骤 S5006: VCC AS发送携带假媒体信息的 183消息给 IM CN; 此段媒体信息 表示资源可用。 步骤 S5007: IM CN转发此条带媒体信息的 183消息给远端用户。 步骤 S5008: 远端用户回复 Prack至 VCC AS。 本实施例中， 远端用户指主叫用户， 本端用户指被叫用户。 步骤 S5009: VCC AS回复 200OK ( Prack )。 步骤 S5010: VCC AS发送 UPDATE ( SDP ) 消息更新远端。 步骤 S5011 : IM CN转发 UPDATE ( SDP) 给远端用户。 步骤 S5012: 远端回复 200OK (UPDATE&&SDP), 携带远端用户的媒体能力信 息。 步骤 S5013 : IM CN转发 200OK (UPDATE&&SDP) 给 VCC AS。 步骤 S5014: VCC AS发送携带 SDP的 183消息给 IM CN; 此段媒体信息表示资 源可用。 步骤 S5015: IM CN转发此条带媒体信息的 183消息给在 CS域的 UE_A终端。 步骤 S5016: 在 CS域的 UE_A终端回复 Prack。 步骤 S5017: IM CN转发 Prack至 VCC AS。 步骤 S5018: VCC AS回复 Prack的 200OK。 步骤 S5019: IM CN转发 200OK至在 CS域的 UE A终端, 步骤 S5020: UE A在 CS摘机应答，发送带应答会话信息的 INFO消息给 IM CN。 步骤 S5021： IM CN转发此带应答信息的 INFO消息给 VCC AS。 步骤 S5022: VCC AS回复 INFO的响应 200OK消息 c 步骤 S5023 : IM CN转发 200OK (INFO) 消息给 UE A。 步骤 S5024: VCC AS判断本端资源协商成功， 则发送摘机应答的 200OK消息 步骤 S5025: IM CN转发此应答响应消息给主叫用户 UE B。 步骤 S5026: 主叫用户 UE B回复 ACK。 步骤 S5027: IM CN转发 ACK至 VCC ASc 步骤 S5028: VCC AS发送 200OK (INVITE) 响应消息 步骤 S5029: IM CN转发 200OK (INVITE) 消息至在 CS域的 UE A终端, 步骤 S5030: 在 CS域的 UE A终端回复 ACK消息 c 步骤 S5031 : IM CN转发 ACK至 VCC ASc 至此媒体携带完成， 同时完成了切换流禾 '王; c 步骤 S5032-S5039: VCC AS发送 CANCEL消息释放原来被叫在 IMS域的那路呼
本实施例中， DRVCC振铃态域切换的域切换请求消息由 UE发起。通过本实施例 的切换方法， 使得即使初始时， 主被叫振铃状态的媒体资源状态未协商好， 域切换过 程也能够顺利完成。 实施例五 参照图 6， 示出了根据本发明实施例五的一种业务连续性服务器的结构框图。 本实施例的业务连续性服务器包括： 确定模块 602， 设置为接收到本端发送的域 切换请求， 确定本端和远端的初始会话振铃态媒体资源状态协商不成功； 更新模块 604， 与确定模块 602耦合， 设置为在所述确定模块确定本端和远端的初始会话振铃态 媒体资源状态协商不成功时， 使用本端发送的域切换请求中所携带的媒体信息去更新 远端 优选地， 更新模块 604设置为使用临时响应消息携带假媒体信息发送给远端， 完 成远端的媒体资源状态协商， 其中， 假媒体信息可以是业务连续性服务器在发送临时 响应消息之前上一条携带媒体的消息中所携带的媒体信息； 也可以是配置的媒体； 但 不限于此两种； 通过更新消息携带域切换请求中所携带的媒体信息， 去更新远端。 优选地， 本实施例的业务连续性服务器还包括： 协商模块 606， 与更新模块 604 耦合， 设置为在更新模块 604更新远端之后， 获取远端的媒体能力信息， 完成本端和 远端的媒体资源状态协商。 优选地， 本实施例的业务连续性服务器还包括： 释放模块 608， 与协商模块 606 耦合， 设置为在协商模块 606完成本端和远端的媒体资源状态协商之后， 确定本端已 在 CS域摘机应答， 释放本端在 PS域或 IMS域的呼叫。 优选地， 本实施例的业务连续性服务器的确定模块 602， 还设置为在接收到本端 发送的域切换请求之后， 确定本端和远端的初始会话振铃态媒体资源状态协商不成功 之前， 关联本端和远端。 本实施例实现的方法可以参照上述相关方法实施例中的相关描述， 并且具有上述 相关方法实施例的有益效果， 在此不再赘述。 从以上的描述中， 可以看出， 本发明提供了一种在 IMS网络架构中， DRVCC以 及 SRVCC域切换的技术方案， 特别是一种用户媒体实时导通模式的被叫流程的技术 方案。 通过本发明的技术方案， 实现了当切换前媒体资源状态协商不成功时， 由业务 连续性服务器使用域切换请求中携带的媒体信息更新远端， 完成协商， 从而保证了切 换流程的顺利完成。 需要说明的是， 本发明实施例中 SRVCC 振铃态域切换流程同样适用于 DRVCC 振铃态时的域切换， 只是 DRVCC域切换是由终端 UE发起的操作。 显然， 本领域的技术人员应该明白， 上述的本发明的各模块或各步骤可以用通用 的计算装置来实现， 它们可以集中在单个的计算装置上， 或者分布在多个计算装置所 组成的网络上， 可选地， 它们可以用计算装置可执行的程序代码来实现， 从而， 可以 将它们存储在存储装置中由计算装置来执行， 并且在某些情况下， 可以以不同于此处 的顺序执行所示出或描述的步骤， 或者将它们分别制作成各个集成电路模块， 或者将 它们中的多个模块或步骤制作成单个集成电路模块来实现。 这样， 本发明不限制于任 何特定的硬件和软件结合。 以上所述仅为本发明的优选实施例而已， 并不用于限制本发明， 对于本领域的技 术人员来说， 本发明可以有各种更改和变化。 凡在本发明的精神和原则之内， 所作的 任何修改、 等同替换、 改进等， 均应包含在本发明的保护范围之内。

Claims

权 利 要 求 书
1. 一种语音呼叫处理方法， 包括：
业务连续性服务器接收到本端发送的域切换请求， 确定所述本端和远端的 初始会话振铃态媒体资源状态协商不成功；
所述业务连续性服务器使用所述本端发送的域切换请求中所携带的媒体信 息去更新所述远端。
2. 根据权利要求 1所述的方法， 其中， 所述业务连续性服务器使用所述本端发送 的域切换请求中所携带的媒体信息去更新所述远端的步骤包括：
所述业务连续性服务器使用临时响应消息携带假媒体信息发送给所述远 端， 完成所述远端的媒体资源状态协商， 其中， 所述假媒体信息是指所述业务 连续性服务器在发送所述临时响应消息之前上一条携带媒体的消息中所携带的 媒体信息， 或者是配置的媒体；
通过更新消息携带所述域切换请求中所携带的媒体信息，去更新所述远端。
3. 根据权利要求 2所述的方法， 其中， 在更新所述远端的步骤之后， 还包括： 所述业务连续性服务器获取所述远端的媒体能力信息， 完成所述本端和所 述远端的媒体资源状态协商。
4. 根据权利要求 3所述的方法， 其中， 在所述完成所述本端和所述远端的媒体资 源状态协商的步骤之后， 还包括：
所述业务连续性服务器确定所述本端在 CS域摘机应答， 释放所述本端之 前在 PS域或 IMS域的呼叫。
5. 根据权利要求 1所述的方法， 其中， 在所述业务连续性服务器接收到本端发送 的域切换请求之后， 确定本端和远端的初始会话振铃态媒体资源状态协商不成 功之前， 还包括：
所述业务连续性服务器关联所述本端和所述远端。
6. 一种业务连续性服务器， 包括：
确定模块， 设置为接收到本端发送的域切换请求， 确定所述本端和远端的 初始会话振铃态媒体资源状态协商不成功； 更新模块， 设置为在所述确定模块确定本端和远端的初始会话振铃态媒体 资源状态协商不成功时， 使用所述本端发送的域切换请求中所携带的媒体信息 去更新所述远端。 根据权利要求 6所述的业务连续性服务器， 其中， 所述更新模块，设置为使用临时响应消息携带假媒体信息发送给所述远端， 完成所述远端的媒体资源状态协商， 其中， 所述假媒体信息是指所述业务连续 性服务器在发送所述临时响应消息之前上一条携带媒体的消息中所携带的媒体 信息， 或者是配置的媒体； 通过更新消息携带所述域切换请求中所携带的媒体 信息， 去更新所述远端。 根据权利要求 7所述的业务连续性服务器， 其中， 还包括： 协商模块， 设置为在所述更新模块更新所述远端之后， 获取所述远端的媒 体能力信息， 完成所述本端和所述远端的媒体资源状态协商。 根据权利要求 8所述的业务连续性服务器， 其中， 还包括： 释放模块， 设置为在所述协商模块完成所述本端和所述远端的媒体资源状 态协商之后，确定所述本端在 CS域摘机应答，释放所述本端之前在 PS域或 IMS 域的呼叫。 根据权利要求 6所述的业务连续性服务器， 其中，
所述确定模块， 还设置为在接收到本端发送的域切换请求之后， 确定本端 和远端的初始会话振铃态媒体资源状态协商不成功之前， 关联所述本端和所述 远端。
PCT/CN2012/072678 2011-05-26 2012-03-21 语音呼叫处理方法及业务连续性服务器 WO2012159483A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201110139463.2 2011-05-26
CN201110139463.2A CN102215478B (zh) 2011-05-26 2011-05-26 语音呼叫处理方法及业务连续性服务器

Publications (1)

Publication Number Publication Date
WO2012159483A1 true WO2012159483A1 (zh) 2012-11-29

Family

ID=44746555

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/072678 WO2012159483A1 (zh) 2011-05-26 2012-03-21 语音呼叫处理方法及业务连续性服务器

Country Status (2)

Country Link
CN (1) CN102215478B (zh)
WO (1) WO2012159483A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102215478B (zh) * 2011-05-26 2016-06-08 中兴通讯股份有限公司 语音呼叫处理方法及业务连续性服务器
US9655019B2 (en) * 2012-10-08 2017-05-16 Samsung Electronics Co., Ltd. Apparatus and method for switching call in mobile communication system
WO2015070420A1 (en) 2013-11-14 2015-05-21 Qualcomm Incorporated Dual radio voice call continuity

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20080018756A (ko) * 2006-08-25 2008-02-28 삼성전자주식회사 음성 호 연속 서비스를 위한 도메인 전환 방법 및 시스템
CN101141794A (zh) * 2006-09-08 2008-03-12 华为技术有限公司 用户设备、语音呼叫连续性应用服务器及网络切换方法
CN101351039A (zh) * 2007-07-20 2009-01-21 华为技术有限公司 实现多媒体呼叫连续性的方法、装置及系统
CN101835121A (zh) * 2009-03-09 2010-09-15 华为技术有限公司 一种对媒体协商进行适配处理的方法、系统和装置
CN102215478A (zh) * 2011-05-26 2011-10-12 中兴通讯股份有限公司 语音呼叫处理方法及业务连续性服务器

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101417494B (zh) * 2008-11-14 2012-02-22 联塑(杭州)机械有限公司 发泡塑料射出成型装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20080018756A (ko) * 2006-08-25 2008-02-28 삼성전자주식회사 음성 호 연속 서비스를 위한 도메인 전환 방법 및 시스템
CN101141794A (zh) * 2006-09-08 2008-03-12 华为技术有限公司 用户设备、语音呼叫连续性应用服务器及网络切换方法
CN101351039A (zh) * 2007-07-20 2009-01-21 华为技术有限公司 实现多媒体呼叫连续性的方法、装置及系统
CN101835121A (zh) * 2009-03-09 2010-09-15 华为技术有限公司 一种对媒体协商进行适配处理的方法、系统和装置
CN102215478A (zh) * 2011-05-26 2011-10-12 中兴通讯股份有限公司 语音呼叫处理方法及业务连续性服务器

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"3GPP Technical Specification Group Core Network and Terminals. 3GPP TS 24.237 V10.2.0: IP Multimedia (IM) Core Network (CN) subsystem and IP Multimedia Subsystem (IMS) Service Continuity", 3GPP, March 2011 (2011-03-01) *

Also Published As

Publication number Publication date
CN102215478A (zh) 2011-10-12
CN102215478B (zh) 2016-06-08

Similar Documents

Publication Publication Date Title
US8918518B2 (en) Access session controller, IP multimedia subsystem and registration and session method thereof
WO2009059559A1 (fr) Procédé de commande d'appel de session multimédia et serveur d'application
CN108781426A (zh) 通信会话注册和辅助请求处理
US8250217B2 (en) System and method for handling session management in a communication system
WO2008083582A1 (fr) Procédé et dispositif de déclenchement de services
WO2008089693A1 (fr) Procédé et système servant à identifier un service de communication
CA2917799C (en) Systems and methods for single radio voice call continuity in a multi-line, multi-device service environment in a communications network
WO2009155824A1 (zh) 一种彩铃、彩像业务的实现方法及系统
EP2472952B1 (en) Method for inter-ue media transfer and application server thereof
US11411899B2 (en) Routing parent and child device calls through a parent telephony application server
WO2012159483A1 (zh) 语音呼叫处理方法及业务连续性服务器
JP2007325191A (ja) 移動体通信システム及びセッション継続方法
US20090248810A1 (en) Systems and methods for querying status of peer-to-peer multimedia connections in communication systems
WO2011023041A1 (zh) 一种指示终端媒体类型的呼叫方法及系统
JP2011049687A (ja) 通信ネットワークシステムとそのｓｉｐ信号中継方法及びｓｉｐアプリケーション・サーバ
US9491203B2 (en) Service based release of a subscriber registrar server from a signalling path in an internet protocol communication network
WO2017000481A1 (zh) 语音通话的拨号方法和装置
JP4854035B2 (ja) Ｉｍｓ／ｍｍｄシステムにおける複数のポリシー制御サーバを用いた呼接続方法及びシステム
WO2011029862A1 (en) Method and system for converting text messages into voice over ip calls from a web interface
EP2723053B1 (en) Transfer inquiry method, application server, service terminal, and system
CN102487495A (zh) Hss异常时实现呼叫的方法及cscf
JP5568348B2 (ja) 通信制御装置及び通信制御システム
JP6234272B2 (ja) アーリーメディアの送信タイミングを制御するセッション制御方法、ｓｉｐサーバ及びプログラム
JP6549523B2 (ja) 要求先端末のオプション機能の非使用を整合する網間制御方法、ｓｉｐサーバ及びプログラム
WO2011134289A1 (zh) 更新用户初始过滤规则的方法及系统

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: 12790302

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: 12790302

Country of ref document: EP

Kind code of ref document: A1