Nothing Special   »   [go: up one dir, main page]

WO2011134341A1 - 反向单待业务连续性实现方法及系统 - Google Patents

反向单待业务连续性实现方法及系统 Download PDF

Info

Publication number
WO2011134341A1
WO2011134341A1 PCT/CN2011/072470 CN2011072470W WO2011134341A1 WO 2011134341 A1 WO2011134341 A1 WO 2011134341A1 CN 2011072470 W CN2011072470 W CN 2011072470W WO 2011134341 A1 WO2011134341 A1 WO 2011134341A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
message
msc
connection
connection establishment
Prior art date
Application number
PCT/CN2011/072470
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 WO2011134341A1 publication Critical patent/WO2011134341A1/zh

Links

Classifications

    • 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]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup

Definitions

  • the present invention relates to the field of communications, and in particular, to a method and system for implementing reverse single-standby service continuity in a multimedia subsystem of IP (Internet Protocol, IP for short).
  • IP Internet Protocol
  • IP Multimedia Core Network Subsystem is an IP-based network architecture proposed by the 3rd Generation Partnership Project (3GPP) to build an open and flexible business environment. Support multimedia applications and provide users with rich multimedia services.
  • 3GPP 3rd Generation Partnership Project
  • control layer In the IMS service system, the control layer and the service layer are separated.
  • the control layer does not provide specific services, and only provides the necessary triggering, routing, and accounting functions to the service layer.
  • the service triggering and control function in the control layer is completed by the Call Session Control Function (CSCF).
  • CSCF Call Session Control Function
  • the call session control functions are divided into: proxy call session control function (Proxy-CSCF, referred to as P-CSCF), query call session control function (Interrogating-CSCF, referred to as I-CSCF) and service call session control function (Serving-CSCF, referred to as S-CSCF) three types, of which the main responsibility is S-CSCF, I-CSCF is optional.
  • the service layer is composed of a series of application servers (ASs), which can provide specific service services.
  • ASs application servers
  • the AS can be an independent entity or exist in the S-CSCF.
  • the control layer controls the service trigger according to the subscription information of the user, invokes the service on the AS, and implements the service function.
  • the end-to-end device in the session is called User Equipment (UE), which is responsible for interaction with users.
  • UE User Equipment
  • Some UEs have multiple ways to access the network, including packet switching through 3GPP (Packet Switch, PS for short).
  • the domain access network can access the network through other non-3GPP PS domains, and can even access the network through a Circuit Switch (CS) domain.
  • CS Circuit Switch
  • the eMSC provides SIP (Session Initial Protocol).
  • SIP Session Initial Protocol
  • the interface interacts with the IMS network, and the interaction between the IMS network and the CS network can be implemented by the eMSC.
  • the UE For a UE with multiple access modes, if the UE can only use one access mode at a certain time, it is performing a call service in the access mode of the 2/3G network, because the call service is at 2/3G.
  • the network is provided by the CS domain.
  • LTE Long Term Evaluation
  • HSPA High Speed Packet Access
  • rSRVCC Reverse Single Radio Voice Call Continuity
  • the handover process When implementing reverse single-standby service continuity, two processes should be included, one is the handover process from the original network to the target network, and the other is the media connection establishment process between the terminal and the remote end.
  • the handover process has a clear implementation process in the industry (as shown in Figure 1), but how to initiate the media connection establishment process between the terminal and the remote has yet to come up with a clear solution.
  • FIG. 1 is a flow chart of the existing reverse single-standby service continuity, which describes that a call is established between UE-1 and UE-2, and UE-1 establishes a call through the CS domain access of the 2/3G network, so the call is made.
  • the process of connecting the UE-1 to the media path is a CS media connection.
  • the process of how the UE-1 switches from the CS domain to the PS domain includes the following steps:
  • Step 101 The UE-1 sends a measurement report to the original network served by the UE-1, where the cell signal strength measurement information is reported.
  • Step 102 The base station system of the original network serving the UE-1 determines that the nearby PS target network is more suitable for serving the UE-1 according to the signal strength information of each cell in the measurement report, and then determines to perform the handover operation, and the base station system of the original network sends the base station system to the MSC.
  • Send a handover request such as sending a Handover required message;
  • Step 103 The MSC sends a handover request to the control entity of the target network, for example, sending a CS to PS Handover Request, where the control entity may be an MME of a Long Term Evolution Network (LTE) or an SGSN of a High Speed Data Access Network (HSPA);
  • Step 104 If the UE-1 has a data service, the base station system of the original network further sends a handover request to the original network data domain control entity (that is, the SGSN), for example, sending a Relocation Required message;
  • LTE Long Term Evolution Network
  • HSPA High Speed Data Access Network
  • the original network data domain control entity sends a handover request to the target network control entity, for example, sending a Forward Relocation Request message;
  • Step 106 The target network control entity sends a handover request to the target network base station system, for example, sending a Handover Request message;
  • Step 107 The target network base station system responds to the handover response message, for example, sends a Handover Request Acknowledge message;
  • Step 108 After receiving the handover response, the target network control entity sends a handover response message to the MSC, for example, sending a CS to PS Handover Response message.
  • Step 109 The MSC sends a handover command to the original network base station system, for example, sending a Handover Command message;
  • Step 110 If the UE-1 has a data service, the target network control entity further sends a handover response to the original network data domain control entity, for example, sending a Forward Relocation Response message; after step 111, step 110, the original network data domain control entity is forwarded to the original The network base station system sends a handover command, such as sending a Relocation Command message;
  • Step 112 The original network base station system sends a handover command to the UE-1, for example, sending a HO from UTRAN/GERAN message.
  • Step 113 UE-1 performs handover, switches to the target network, and then sends an attach request to the control entity of the target network, for example, sends an Attach Request message.
  • Step 114 The target network control entity sends an attach consent message to the UE-1, for example, sending an Attach Accept message.
  • the present invention provides a method for implementing reverse single-standby service continuity, the method comprising:
  • the handover preparation notification step after the current mobile switching center (MSC) receives the handover request from the CS domain, sends a handover preparation notice to the terminal;
  • the terminal after receiving the handover preparation notification, the terminal sends a transfer request to the service continuity application server (SC AS ) through the original network, and carries the media resource information M1 of the terminal;
  • SC AS service continuity application server
  • the terminal In the connection establishment step, the terminal initiates a media connection establishment process between the terminal and the remote end, or triggers the SC AS to initiate a media connection establishment process between the terminal and the remote end.
  • the present invention also provides an implementation system for reverse single-standby service continuity, the system comprising: an MSC and a terminal; wherein the mobile switching center (MSC) includes a handover control module, and the handover control module is configured to: When the MSC is the current MSC, after receiving the handover request from the CS domain, the MSC sends a handover preparation notification to the terminal;
  • MSC mobile switching center
  • the terminal includes a connection establishment control module, and the connection establishment control module is configured to: receive the handover preparation notification, and send the handover preparation notification to the service continuity application server (SC AS) through the original network.
  • SC AS service continuity application server
  • a transfer request where the media resource information M1 of the terminal is carried, and a media connection establishment process between the terminal and the remote end is initiated, or the SC AS is triggered to initiate a media connection establishment process between the terminal and the remote end.
  • the method and system of the present invention initiates a transfer request to the service continuity application server (SC AS ) through the original network through the terminal, and the terminal initiates a media connection establishment process between the terminal and the remote end, or triggers the SC
  • SC AS service continuity application server
  • the AS initiates a media connection establishment process between the terminal and the remote end, so that when the terminal switches from the CS domain to the PS domain, the reverse single-standby service continuity is ensured.
  • 1 is a flow chart of an existing method for implementing reverse single-standby service continuity
  • FIG. 2 is a flowchart of Embodiment 1 of a method for implementing a reverse single-standby service continuity according to the present invention
  • FIG. 3 is a flowchart of Embodiment 2 of a method for implementing a reverse single-standby service continuity according to the present invention
  • 4 is a flowchart of Embodiment 3 of a method for implementing reverse single-standby service continuity according to the present invention
  • FIG. 5 is a flowchart of Embodiment 4 of a method for implementing reverse single-standby service continuity according to the present invention
  • FIG. 7 is a flowchart of Embodiment 6 of a method for implementing reverse single-standby service continuity according to the present invention
  • FIG. 8 is a flowchart of a method for implementing reverse single-standby service continuity according to the present invention
  • schematic diagram Preferred embodiment of the invention
  • the core idea of the present invention is that, by the terminal assistance, the terminal initiates a transfer request to the service continuity application server (SC AS ) through the original network, and the terminal initiates a media connection establishment process between the terminal and the remote end, or triggers the location.
  • the SC AS initiates a media connection establishment process between the terminal and the remote end, so that when the terminal switches from the CS domain to the PS domain, the reverse single-standby service continuity is ensured.
  • the current MSC refers to the MSC participating in the transfer process. If the MSC does not change during the handover process, the MSC is the current MSC according to the present invention; if the MSC needs to switch from the original MSC to the target MSC during the handover, the target MSC is The current MSC referred to in the present invention.
  • the method for implementing the reverse single-standby service continuity of the present invention includes:
  • Step 10 The handover preparation notification step, after the current mobile switching center (MSC) receives the handover request from the CS domain, sends a handover preparation notice to the terminal;
  • MSC current mobile switching center
  • Step 20 The transfer request step, after receiving the handover preparation notification, the terminal sends a transfer request to the service continuity application server (SC AS ) through the original network, and carries the media resource information M1 of the terminal;
  • SC AS service continuity application server
  • Step 30 The connection establishment step, the terminal initiates a media connection establishment process between the terminal and the remote end, or triggers the SC AS to initiate a media connection establishment process between the terminal and the remote end.
  • Embodiments 1, 2, and 5 When the signaling is used to anchor the current MSC, refer to the following Embodiments 1, 2, and 5.
  • the method for establishing the connection establishment is:
  • the SC AS After receiving the transfer request, the SC AS sends the current MSC to the terminal. Send a connection message.
  • the handover preparation notification, the transfer request, and the establishment connection message all carry session association information
  • the current MSC forwards the media resource information of the current MSC to the established connection message forwarded by the terminal;
  • the current MSC After the current MSC receives the message carrying the media resource information of the terminal, the current MSC establishes a media connection with the terminal;
  • the current MSC associates the media connection between the current MSC and the terminal and the media connection between the current MSC and the remote end according to the session association information.
  • the current MSC receives the message of rejecting the establishment of the connection message sent by the terminal, and then retrying to forward the message. Establish a connection message. See Embodiments 1 and 2.
  • connection establishment step after the current MSC receives the handover completion notification sent by the target network control entity, the current MSC forwards the notification to the terminal. Establish a connection message. See example five.
  • the target network control entity sends a handover completion notification in any of the following situations:
  • the current MSC After receiving the handover request from the CS domain, the current MSC sends a handover notification to the target network control entity, where the target network control entity senses that the terminal accesses the target network, and sends a handover completion to the current MSC. Notice; or,
  • the terminal After the terminal completes the handover, the terminal sends a handover completion indication to the target network control entity, and after receiving the indication, the target network control entity sends a handover completion notification to the current MSC.
  • the method for the terminal to trigger the SC AS to initiate the media connection establishment process between the terminal and the remote end is:
  • connection establishment steps include:
  • the SC AS After receiving the transfer request, the SC AS uses the media resource letter in the transfer request
  • the information M1 updates the remote end
  • the SC AS After receiving the message carrying the media resource information M2, the SC AS sends the media resource information M2 through the connection establishment message;
  • the sending message After the terminal receives the connection establishment message, the sending message carries the media resource information M3 of the terminal, and the media resource information M3 is included in the media resource information M1.
  • the SC AS retry to forward the connection establishment message after receiving the message that the terminal rejects the establishment of the connection message. . See example three.
  • connection establishment step the method for the terminal to initiate the media connection establishment process between the terminal and the remote end is:
  • the terminal initiates media connection establishment by using the transfer request, or the terminal sends a media transfer connection by transmitting a second transfer request carrying media resource information on the target network;
  • the SC AS After receiving the transfer request or the second transfer request, the SC AS sends a response message carrying the remote media resource information to the terminal.
  • the MSC may send a handover request to the destination network control entity, or may not send the handover request.
  • Embodiment 1 of a method for implementing reverse single-standby service continuity according to the present invention, which describes that a call is established between UE-1 and UE-2, and UE-1 establishes a call through a CS domain of a 2/3G network. Therefore, the UE-1 connected to the UE-1 is a CS media connection.
  • the UE-1 mobile needs to change the PS domain whose access mode is LTE or HSPA, the subsequent session establishes media through the media anchor of the target MSC.
  • the process in which the UE-1 implements the reverse single-standby service continuity includes the following steps:
  • Step 201 The UE-1 establishes a session with the UE-2 through the CS domain and the MSC, and the MSC supports the IMS signaling, and in the signaling path of the original session, the session signaling path passes through the SC AS; Steps 202 to 203 are the same as steps 101-102 of FIG. 1;
  • Step 204 The MSC receives a handover request from the CS domain, and immediately sends a handover preparation message to the UE-1.
  • the short message SMS
  • the Unstructured Supplementary Service Data USSD
  • Anchoring indication information such as carrying the identification information of the MSC to indicate that the subsequent IMS process requires signaling anchoring (signaling anchor indication) of the MSC, and carrying the indication information of the MSC in the media path (media anchor indication, to indicate The UE's session has been anchored by the MSC. It also carries the session association information, or only the MSC identification information, and the identification information itself can also be used for session association.
  • the target MSC is identified by the username@hostname, where the user The name part can be used for session association.
  • Step 205 After receiving the handover preparation message, the UE-1 may optionally respond to the handover preparation response message, for example, sending the message through the SMS or the USSD, and the message arrives at the MSC through the base station system of the original network;
  • Step 206 After receiving the handover preparation message, the UE-1 sends a transfer request to the SC AS. For example, if the UE has a PS domain available on the original network, the UE may send an INVITE message targeting the SC AS.
  • the USSD sends an INVITE message to the SC AS, where the message carries the media resource information that the UE-1 will use in the target network, such as an IP address, a port number, an encoder information, and the like, and the message further carries the anchor indication information obtained in step 204;
  • the media resource information of the UE-1 in the transfer request sent by the UE-1 may be modified and updated by other network elements on the signaling path in the process of being sent to the SC AS, so that the SC AS receives the
  • the media resource information in the transfer request is no longer the original media resource information, but the media resource information is still the media resource information associated with the UE-1.
  • the media resource information in other embodiments has a similar situation, that is, the media resource information of the sender and the receiver may change, but the object pointed to by the substance does not change.
  • Step 205 may be after step 206, ie, UE-1 sends a handover preparation response message after transmitting the transfer request.
  • Step 207 If the UE-1 has a service in the PS domain of the original network, perform a standard PS to PS handover procedure, and the process is the same as steps 104-109 of FIG. 1;
  • step 204 or step 205 the MSC sends a handover command to the CS domain, and the message arrives at the base station system of the original network;
  • Step 209 The base station system of the original network sends a handover command to the UE-1, requesting the UE-1 to switch to the target network.
  • Step 210 After receiving the handover command, the UE-1 modulates to the target network access.
  • step 206 the SC AS receives the transfer request, and determines that the remote end is not required to be updated according to the media anchor indication in the anchor indication, and thus does not update the remote end;
  • Step 212 the SC AS responds to the transfer request, for example, sends a "200 OK" message to UE-1;
  • the SC AS receives the transfer request, and the SC AS finds the user identifier of the UE-1 by using the calling user information in the transfer request (the calling user information itself may be the user identifier of the UE-1),
  • the user identifier sends a connection establishment message to the UE-1 through the PS domain, for example, sends an INVITE message, and the SC AS requests the connection establishment message to pass through the MSC, for example, setting routing information in the header field of the call message, where the routing information includes the identification information of the MSC.
  • the SC AS further carries the session association information obtained in step 206 in the connection establishment message;
  • Step 214 The connection message is sent to the MSC, and the MSC associates the original session according to the session association information, and forwards the connection establishment message to the UE-1, and carries the media resource information of the MSC in the forwarded connection establishment message;
  • UE-1 does not necessarily access the target network in time. If UE-1 has not completed the operation of accessing the target network at this time, the forwarded connection establishment message will be rejected.
  • the MSC receives the forwarded connection establishment message rejection.
  • the operation of reestablishing the connection message is retried until the connection establishment message step 215, the UE-1 receives the establishment connection message, and responds to the establishment connection message, for example, sends a "200 OK" message, and the message carries the media of UE-1.
  • Step 216 Establish a connection response message passing through the MSC, and the MSC according to the media resource information therein After the media negotiation with the UE-1 is completed, the MSC forwards the connection establishment response message to the SC AS. At this point, the IMS media connection 2 is established between the UE-1 and the MSC, and the MSC connects the newly established IMS media connection 2 with the IMS media of the original session. In turn, UE-1 can continue to talk to UE-2.
  • the anchor indication in step 204 may not carry the identification information of the MSC and the session association information, but increase the media resource information used by the MSC to connect with the UE-1, so the SC AS cannot be established in step 213.
  • the connection message passes through the MSC, and the SC AS carries the obtained media resource information of the obtained MSC for connecting with the UE-1 in the connection establishment message, and then the step 213 does not pass through the MSC to reach the UE-1, and the step 214 is gone, step 215 It is no longer passed through the MSC to the SC AS, and step 216 is gone.
  • Embodiment 3 is a flowchart of Embodiment 2 of a method for implementing reverse single-standby service continuity according to the present invention, which describes that a call is established between UE-1 and UE-2, and UE-1 establishes a call through a CS domain of a 2/3G network. Therefore, the UE-1 connected to the UE-1 is a CS media connection.
  • the UE-1 mobile needs to change the PS domain whose access mode is LTE or HSPA, the subsequent session is anchored by the signaling of the target MSC. If the non-media anchor establishes a media connection, and the target MSC is not the original MSC, the UE-1 and the SC AS interact through the MSC, and the process of the UE-1 implementing the reverse single-standby service continuity includes the following steps:
  • Step 301 The UE-1 establishes a session with the UE-1 through the CS domain and the original MSC, and the target MSC supports the IMS signaling but is not in the signaling path, and the session signaling path passes through the SC AS.
  • Steps 302 to 303 are the same as steps 101 to 102 of FIG. 1;
  • Step 304 The original MSC receives the handover request, initiates an inter-office handover process of the standard CS domain to the target MSC, and the original MSC sends a handover request to the target MSC.
  • Step 305 The target MSC receives the handover request from the CS domain, and immediately sends a handover preparation message to the UE-1.
  • the short message SMS
  • USSD Unstructured Supplementary Service Data
  • the message arrives at the UE-1 through the base station system of the original network, and the message carries the MSC.
  • Anchoring instructions such as The identification information of the carrying MSC also carries the session association information, or only the identification information of the MSC, and the identification information itself can also be used for session association.
  • the target MSC is identified in the form of a username@hostname, where the username part can be used. Session association
  • Step 306 After receiving the handover preparation message, the UE-1 may respond to the handover preparation response message, for example, by using SMS or USSD, and the message arrives at the MSC through the base station system of the original network.
  • Step 307 After receiving the handover preparation message, the UE-1 sends a handover request to the SC AS. For example, if the UE has a PS domain available in the original network, the UE may send an INVITE message targeting the SC AS, if there is no PS domain. If available, the INVITE message can be sent to the SC AS through the USSD.
  • the message carries the media resource information that the UE-1 will use in the target network, such as the IP address, the port number, the encoder information, etc., and the message also carries the anchor obtained in step 305. Instructing information; Step 306 may be after step 307, that is, UE-1 sends a handover preparation response message after transmitting the transfer request.
  • Step 308 If UE-1 has a service in the PS domain of the original network, perform a standard PS to PS handover procedure, and the process is the same as steps 104-109 of FIG. 1;
  • step 305 or step 306 the target MSC sends a handover response to the original MSC of the CS domain, and the message arrives at the original MSC;
  • Step 310 The original MSC sends a handover command to the CS domain, and the message arrives at the base station system of the original network.
  • Step 311 The base station system of the original network sends a handover command to the UE-1, requesting the UE-1 to switch to the target network.
  • Step 312 After receiving the handover command, the UE-1 modulates the access to the target network.
  • the SC AS receives the transfer request, and sends an update request to the UE-2, for example, sends an UPDATE (update) message or a relNVITE (re-invite) message, and the message carries the media resource of the UE-1 obtained in step 307.
  • the content of the media resource information of the UE-1 in step 313 may be different from the format of the media resource information of the UE-1 in step 307. For example, when step 307 uses the USSD to send a transfer request, the content is consistent;
  • Step 314 The update message passes through the CSCF to reach the UE-2, and the UE-2 responds to the update request, for example, sends a "200 OK" message, where the message carries the media resource information of the UE-2;
  • Step 315 optionally, after step 314, the SC AS responds to the transfer request, for example, sends a "200 OK" message to the UE-1;
  • the SG AS receives the update response message, and the SC AS finds the user identifier of the UE-1 by using the calling user information in the transfer request (the calling user information itself may be the user identifier of the UE-1).
  • Sending a connection establishment message to the UE-1 through the PS domain for example, sending an INVITE message
  • the SC AS requests the connection establishment message to pass through the MSC, for example, setting routing information in the header field of the call message, where the routing information includes the identifier of the MSC.
  • the SC AS further carries the session association information obtained in step 307 in the connection establishment message;
  • Step 317 establishing a connection message to the MSC, the MSC associates the original session according to the session association information, and forwards the connection establishment message to the UE-1;
  • UE-1 does not necessarily access the target network in time. If UE-1 has not completed the operation of accessing the target network at this time, the forwarded connection establishment message will be rejected.
  • the MSC receives the forwarded connection establishment message rejection.
  • the operation of reestablishing the connection message is retried until the establishment of the connection message step 318, the UE-1 receives the establishment connection message, and responds to the establishment connection message, for example, sends a "200 OK" message, and the message carries the media of UE-1.
  • the resource information the content of which is included in the media resource information content provided in step 307; Step 319, establishing a connection response message to the SC AS via the MSC and the CSCF;
  • UE-1 establishes an IMS media connection 1 with UE-2, so that UE-1 can continue to talk with UE-2.
  • step 301 the target MSC is also in the signaling path of the original session, and steps 304 and 309 are gone.
  • Embodiment 4 is a flowchart of Embodiment 3 of a method for implementing reverse single-standby service continuity according to the present invention, which describes that a call is established between UE-1 and UE-2, and UE-1 establishes a call through CS domain access, so The UE-1 connected to the UE-1 is a CS media connection.
  • the access mode is the PS domain of LTE or HSPA
  • the target MSC is not in the signaling path of the subsequent session, and the target MSC is not the original MSC
  • the UE-1 and the SC AS directly interact to implement the reverse single-standby service.
  • the process of continuity includes the following steps:
  • Steps 401-404 are the same as 301-304 of FIG. 3;
  • Step 405 The MSC receives the handover request from the CS domain, and immediately sends a handover preparation message to the UE-1, for example, sending a request UE through a short message (SMS) or an Unstructured Supplementary Data Data (USSD). 1 preparing a handover message, the message arrives at UE-1 through the base station system of the original network;
  • SMS short message
  • USSD Unstructured Supplementary Data Data
  • Step 406 After receiving the handover preparation message, the UE-1 may respond to the handover preparation response message, for example, by using SMS or USSD, and the message arrives at the MSC through the base station system of the original network.
  • Step 407 After receiving the handover preparation message, the UE-1 sends a handover request to the SC AS. For example, if the UE has a PS domain available in the original network, the UE may send an INVITE message targeting the SC AS, if there is no PS domain. If available, the INVITE message can be sent to the SC AS through the USSD, and the message carries the media resource information that the UE-1 will use in the target network, such as an IP address, a port number, an encoder information, and the like;
  • Steps 408-415 are the same as steps 308-315 of FIG. 3;
  • the SC AS receives the update response message, and the SC AS finds the user identifier of the UE-1 by using the calling user information in the transfer request (the calling user information itself may be the user identifier of the UE-1).
  • UE-1 does not necessarily access the target network in time. If UE-1 has not completed the operation of accessing the target network at this time, the forwarded connection establishment message will be rejected.
  • the SC AS receives the forwarded connection establishment message. After rejecting the message, retry the operation of establishing the connection message until the connection establishment message is accepted.
  • Step 417 The UE-1 receives the connection establishment message, and responds to the establishment connection message, for example, sends a "200 OK" message, where the message carries the media resource information of the UE-1, and the content thereof is included in the content of the media resource information provided in step 407.
  • step 401 the target MSC is also in the signaling path of the original session, and steps 404 and 409 are gone.
  • Embodiment 4 is a flowchart of Embodiment 4 of a method for implementing reverse single-standby service continuity according to the present invention, which describes that a call is established between UE-1 and UE-2, and UE-1 establishes a call through CS domain access, so The UE-1 connected to the UE-1 is a CS media connection, and the UE-1 and the UE-2 need to establish a media connection without the anchor MSC.
  • the access mode used by the UE-1 needs to be changed to the LTE or HSPA PS.
  • the process of implementing the reverse single-standby service continuity by the UE-1 and the SC AS through one interaction includes the following steps:
  • Step 501 The UE-1 establishes a session with the UE-1 through the CS domain and the original MSC.
  • the target MSC is not in the signaling path, and the session signaling path passes through the SC AS.
  • the UE-1 can use the PS domain to send data in the original network.
  • Step 507 After receiving the handover preparation message, the UE-1 sends a handover request to the SC AS. Because the UE-1 has the PS domain available in the original network, the INVITE message is sent to the SC AS, and the message carries the UE-1.
  • the media resource information to be used in the target network such as an IP address, a port number, an encoder information, etc.; step 508 514, which is the same as 408 to 414 of FIG. 4;
  • step 514 the SC AS receives the update response message, and the SC AS responds to the transfer request, for example, sends a "200 OK" message, and the message carries the media resource information obtained in step 514.
  • the UE-1 may not be connected in time.
  • the transfer response will be rejected (for example, a BYE message is received).
  • the SC AS receives the reject message of the transfer response, it retryes to send the transfer response. The operation until the transfer response is accepted.
  • the IMS media connection 1 is established between UE-1 and UE-2, so that UE-1 can continue to talk with UE-2.
  • the target MSC is also in the signaling path of the original session, and steps 504 and 509 are gone.
  • Embodiment 5 is a flowchart of Embodiment 5 of a method for implementing reverse single-standby service continuity according to the present invention, which describes that a call is established between UE-1 and UE-2, and UE-1 establishes a call through CS domain access, so The UE-1 connected to the UE-1 is a CS media connection, and the UE-1 and the UE-2 need to establish a media connection without the anchor MSC.
  • the access mode used by the UE-1 needs to be changed to the LTE or HSPA PS.
  • the process of implementing reverse single-standby service continuity includes the following steps:
  • Steps 601 to 615 are the same as steps 301 to 315 of FIG. 3;
  • the SC AS receives the update response message, and the SC AS finds the user identifier of the UE-1 by using the calling user information in the transfer request (the calling user information itself may be the user identifier of the UE-1).
  • Sending a connection establishment message to the UE-1 through the PS domain for example, sending an INVITE message
  • the SC AS requests the connection establishment message to pass through the MSC, for example, setting routing information in the header field of the call message, where the routing information includes the identifier of the MSC.
  • the SC AS also carries the session association information obtained in step 307 in the connection establishment message, the message passes through the target MSC, and the target MSC associates the original session according to the session association information, but does not Forward the message immediately;
  • Step 617 UE-1 switches to the target network, and sends a message to the target network control entity to notify that the handover is complete, for example, sending an Attach Request message or a Tracking Area Update carrying an indication switched from the CS domain. a message, or a Service Request message carrying a handover indication;
  • Step 618 The control entity of the target network sends a handover complete notification message to the target MSC, for example, sending a PS to CS Handover Complete Notification message, and the control entity of the target network may determine the target MSC by using the target cell information accessed by the UE-1;
  • Step 619 After receiving the handover completion notification message from the target network control entity, the target MSC forwards the connection establishment message of step 616 to UE-1. Steps 620-621 are the same as steps 318-319 of FIG. 3;
  • UE-1 establishes an IMS media connection 1 with UE-2, so that UE-1 can continue to talk with UE-2.
  • step 617 notifies the UE that the target network control network element CS to PS handover is completed.
  • the MSC may also notify the target network control network element that the CS to PS handover occurs after step 604, so that the target network After the control network element senses that the UE accesses the target network, the target network control network element may perform step 618.
  • step 601 the target MSC is also in the signaling path of the original session, and steps 604 and 609 are gone.
  • FIG. 7 is a flow chart 6 of the method for implementing reverse single-standby service continuity according to the present invention. It describes that a call is established between UE-1 and UE-2, and UE-1 establishes a call through CS domain access, so the call media path The process of connecting UE-1 is a CS media connection. When UE-1 moves, it needs to change the continuity of the reverse reverse single-standby service used by the UE-1, including the following steps:
  • Steps 701 to 715 are the same as 401 to 415 of FIG. 4;
  • Step 716 After UE-1 completes the handover, UE-1 initiates a transfer request in the PS domain of the target network, for example, sending an INVITE message with the identifier of the SC AS as the target, and the message carries the media resource information of the UE-1, and the content of the media resource information In the media resource information content of UE-1 included in step 707, the message passes through the CSCF to reach the SC AS;
  • Step 717 The SC AS receives the transfer request sent by the UE-1, and responds to the transfer request, for example, sends a "200 OK" message, where the message carries the media resource information of the UE-2 obtained in step 714; So far, the UE-1 and the UE -2 establishes IMS media connection 1 so that UE-1 can continue to talk with UE-2.
  • the present invention also provides an implementation system for reverse single-standby service continuity, the system comprising: an MSC and a terminal;
  • the mobile switching center includes a handover control module, and the handover control module is configured to: when the MSC is the current MSC, send a handover preparation notification to the terminal after receiving the handover request from the CS domain;
  • the terminal includes a connection establishment control module, and the connection establishment control module is configured to: receive the handover preparation notification, and send a transfer to the service continuity application server (SC AS) through the original network after receiving the handover preparation notification Requesting, carrying the media resource information M1 of the terminal; and initiating a media connection establishment process between the terminal and the remote end, or triggering the SC AS to initiate a media connection establishment process between the terminal and the remote end .
  • SC AS service continuity application server
  • the system further includes an SC AS, where the SC AS includes a connection establishment control module, and the connection establishment control module is configured to: receive the transfer request, and receive the transfer request Then, a connection establishment message is sent to the terminal through the current MSC.
  • SC AS includes a connection establishment control module
  • the connection establishment control module is configured to: receive the transfer request, and receive the transfer request Then, a connection establishment message is sent to the terminal through the current MSC.
  • the handover preparation notification, the transfer request, and the connection establishment message all carry session association information;
  • the MSC further includes a connection establishment message forwarding module and a connection establishment module, where the establishment connection message forwarding module is configured to: receive Establishing a connection message sent by the SC AS, and forwarding the connection establishment message to the terminal, where the forwarded connection establishment message carries the media resource information of the MSC;
  • the connection establishment module is configured to: receive the terminal to carry After the message of the media resource information, establishing a media connection with the terminal, and associating, according to the session association information, the media connection between the current MSC and the terminal, and the current MSC and the Media connection between the far ends.
  • connection establishment module of the MSC is further configured to retry forwarding the establishment connection message after receiving the message sent by the terminal rejecting the establishment of the connection message.
  • the connection establishment module of the MSC after receiving the handover completion notification sent by the target network control entity, the connection establishment module of the MSC forwards the connection establishment message to the terminal.
  • the system further includes a target network control entity; the handover control module of the MSC is further configured to: after receiving a handover request from the CS domain, send a handover notification to the target network control entity; the target network control entity setting Receiving the switching notification, and, in sensing the After the terminal accesses the target network or receives the handover completion indication sent by the terminal, the current
  • the MSC sends a handover completion notification.
  • the system further includes an SC AS, the SC AS includes a connection establishment control module, and the connection establishment control module is configured to: receive the transfer request, and after receiving the transfer request, The terminal sends a connection establishment message.
  • connection establishment control module of the SC AS is further configured to retry forwarding the establishment connection message after receiving the message sent by the terminal rejecting the connection establishment message.
  • connection establishment control module of the SC AS is further configured to: after receiving the transfer request, update the remote end by using the media resource information M1 in the transfer request; and receive After the message carrying the media resource information M2 is sent to the remote end, the media resource information M2 is sent out through the establishment connection message; the connection establishment control module of the terminal is further configured to: receive the establishment connection message, And after receiving the establishing connection message, sending a message carrying the media resource information M3 of the terminal, where the media resource information M3 is included in the media resource information M1.
  • connection establishment control module of the terminal initiates a media connection establishment process between the terminal and the remote end by: initiating media connection establishment by using the transfer request, or sending on the target network
  • the second transfer request carrying the media resource information initiates the media connection establishment
  • the system further includes an SC AS
  • the SC AS further includes a connection establishment control module
  • the module is configured to: receive the transfer request or the second transfer request And sending, by the terminal, a response message carrying the remote media resource information after receiving the transfer request or the second transfer request.
  • the method and system of the present invention initiates a transfer request to the service continuity application server (SC AS ) through the original network through the terminal, and the terminal initiates media connection establishment between the terminal and the remote end.
  • SC AS service continuity application server

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Description

1811U2428
反向单待业务连续性实现方法及系统
技术领域
本发明涉及通信领域，尤其涉及一种 IP(网络互联协议， Internet Protocol, 简称 IP ) 多媒体子系统中反向单待业务连续性实现方法及系统。
背景技术
IP多媒体子系统（ IP Multimedia Core Network Subsystem, 简称 IMS )是 由第三代合作伙伴计划（ 3rd Generation Partnership Project, 简称 3GPP )提出 的一种基于 IP的网络架构， 构建了一个开放而灵活的业务环境， 支持多媒体 应用， 能够为用户提供丰富的多媒体业务。
在 IMS业务体系中，控制层和业务层是分离的，控制层不提供具体业务， 只向业务层提供必要的触发、 路由、 计费等功能。
控制层中业务触发和控制功能是呼叫会话控制功能（ Call Session Control Function, 简称 CSCF ) 完成的。 呼叫会话控制功能分为： 代理呼叫会话控制 功能 ( Proxy-CSCF , 简称 P-CSCF ) 、 查询呼叫会话控制功能 ( Interrogating-CSCF,简称 I-CSCF )和服务呼叫会话控制功能（ Serving-CSCF, 简称 S-CSCF )三种类型， 其中负主要责任的是 S-CSCF, I-CSCF是可选的。
业务层是由一系列应用服务器（Application Server, 简称 AS )组成， 能 提供具体业务服务， AS可以是独立的实体， 也可以存在于 S-CSCF中。
控制层（S-CSCF )根据用户的签约信息控制业务触发， 调用 AS上的业 务， 实现业务功能。
会话中的端到端设备称为用户设备（User Equipment, 简称 UE ) , 负责 与使用者的交互，有的 UE具有多种接入网络的方式， 包括通过 3GPP的包交 换（ Packet Switch, 简称 PS )域接入网络， 通过其他非 3GPP的 PS域接入网 络， 甚至可以通过电路交换（Circuit Switch, 简称 CS )域接入网络等。
如果 CS网络配置了增强移动交换中心 （enhanced Mobile Switch Center, 简称 eMSC ) , 由 eMSC提供 SIP ( Session Initial Protocol, 初始会话协议） 接口来与 IMS网络交互， 则 IMS网络与 CS网络的交互可以通过 eMSC来实 现。
对于具有多种接入方式的 UE而言，如果该 UE某时刻只能使用一种接入 方式，则其在 2/3G网络的接入方式下正在执行通话业务， 因通话业务在 2/3G 网络中由 CS域提供，当 UE移动到其他地方而需要改变其使用的接入方式为 LTE ( Long Term Evaluation——长期演进） 网络或 HSPA ( High Speed Packet Access——高速分组访问） 网络接入时， UE和网络能提供某种方式使 UE正 在执行的通话业务不被中断， 因通话业务在这些网络中由 PS域提供， 这样的 能力我们称之为反向单待终端业务连续性，简称反向单待业务连续性（ reverse Single Radio Voice Call Continuity—— rSRVCC ) , 与之相对应的， 如果是 UE 从 LTE网络或 HSPA网络移动到 2/3G网络则为正向单待终端业务连续性， 简称为单待业务连续性。
在实现反向单待业务连续性时， 应该包括两个过程， 一个过程是原网络 到目标网络的切换过程， 另一个是终端与远端之间的媒体连接建立过程。 就 目前来说， 切换过程在业界已经有明确的实现流程（如图 1所示） ， 但如何 发起终端与远端之间的媒体连接建立过程还有待提出明确的解决方案。
图 1是现有的反向单待业务连续性流程图， 描述了 UE-1和 UE-2间建立 了通话， UE-1是通过 2/3G网络的 CS域接入建立通话的， 因此通话媒体路径 中连接 UE-1的是一段 CS媒体连接， UE-1发生反向单待业务连续性后， UE-1 如何从 CS域切换到 PS域的过程， 包括如下步骤：
步骤 101、 UE-1向为其服务的原网络发送测量报告， 以上报小区信号强 度测量信息；
步骤 102、为 UE-1服务的原网络的基站系统根据测量报告中各小区信号 强度信息判断附近的 PS目标网络更适合为 UE-1服务， 于是决定执行切换操 作，原网络的基站系统向 MSC发送切换请求，比如发送 Handover required (切 换请求） 消息；
步骤 103、 MSC向目标网络的控制实体发送切换请求，比如发送 CS to PS Handover Request, 该控制实体可以是长期演进网络（ LTE ) 的 MME或高 速数据访问网络（HSPA ) 的 SGSN; 步骤 104、 如果 UE-1还有数据业务， 则原网络的基站系统还会向原网络 数据域控制实体（也即 SGSN )发送切换请求， 比如发送 Relocation Required (切换请求） 消息；
步骤 105、 步骤 104之后， 原网络数据域控制实体向目标网络控制实体 发送切换请求， 比如发送 Forward Relocation Request消息；
步骤 106、 目标网络控制实体向目标网络基站系统发送切换请求， 比如 发送 Handover Request (切换请求 ) 消息；
步骤 107、 目标网络基站系统回应切换响应消息， 比如发送 Handover Request Acknowledge消息；
步骤 108、 目标网络控制实体收到切换响应后， 向 MSC发送切换响应消 息， 比如发送 CS to PS Handover Response消息；
步骤 109、 MSC 向原网络基站系统发送切换命令， 比如发送 Handover Command (切换命令） 消息；
步骤 110、 如果 UE-1还有数据业务， 则目标网络控制实体还会向原网络 数据域控制实体发送切换响应， 比如发送 Forward Relocation Response消息； 步骤 111、 步骤 110之后， 原网络数据域控制实体向原网络基站系统发 送切换命令， 比如发送 Relocation Command消息；
步骤 112、 原网络基站系统向 UE-1发送切换命令， 比如发送 HO from UTRAN/GERAN消息；
步骤 113、 UE-1执行切换， 切换到目标网络中， 然后向目标网络的控制 实体发送附着请求， 比如发送 Attach Request消息；
步骤 114、目标网络控制实体向 UE-1发送附着同意消息，比如发送 Attach Accept消息。 发明内容
本发明的目的是， 提供一种反向单待业务连续性实现方法和系统， 以在 终端从 CS域切换到 PS域时， 实现反向单待业务连续性。 为了解决上述问题， 本发明提供一种反向单待业务连续性的实现方法， 该方法包括：
切换准备通知步骤， 当前移动交换中心 （MSC )收到来自 CS域的切换 请求后， 向终端发送切换准备通知；
转移请求步骤， 所述终端接收所述切换准备通知后， 通过原网络向业务 连续性应用服务器 （SC AS )发送转移请求， 携带所述终端的媒体资源信息 Ml ; 以及
连接建立步骤，所述终端发起所述终端与远端之间的媒体连接建立流程， 或触发所述 SC AS发起所述终端与远端之间的媒体连接建立流程。
本发明还提供了一种反向单待业务连续性的实现系统，该系统包括： MSC 和终端； 其中， 移动交换中心 （MSC ) 包括切换控制模块， 所述切换控制模块设置成： 在所述 MSC为当前 MSC时， 在收到来自 CS域的切换请求后， 向终端发送 切换准备通知；
所述终端包括连接建立控制模块， 所述连接建立控制模块设置成： 接收 所述切换准备通知， 并在接收到所述切换准备通知后， 通过原网络向业务连 续性应用服务器 （SC AS )发送转移请求， 其中携带所述终端的媒体资源信 息 Ml ; 以及发起所述终端与远端之间的媒体连接建立流程， 或触发所述 SC AS发起所述终端与远端之间的媒体连接建立流程。
本发明方法和系统通过终端辅助， 由终端通过原网络向业务连续性应用 服务器 （SC AS )发起转移请求， 且终端发起所述终端与远端之间的媒体连 接建立流程， 或触发所述 SC AS发起所述终端与远端之间的媒体连接建立流 程， 使得终端从 CS域切换到 PS域时， 保证反向单待业务连续性。
附图概述
图 1是现有的反向单待业务连续性实现方法流程图；
图 2是本发明反向单待业务连续性实现方法实施例一的流程图； 图 3是本发明反向单待业务连续性实现方法实施例二的流程图； 图 4是本发明反向单待业务连续性实现方法实施例三的流程图； 图 5是本发明反向单待业务连续性实现方法实施例四的流程图； 图 6是本发明反向单待业务连续性实现方法实施例五的流程图； 图 7是本发明反向单待业务连续性实现方法实施例六的流程图； 图 8是本发明反向单待业务连续性实现方法的流程示意图。 本发明的较佳实施方式
本发明的核心思想是， 通过终端辅助， 由终端通过原网络向业务连续性 应用服务器 （SC AS )发起转移请求， 且终端发起所述终端与远端之间的媒 体连接建立流程， 或触发所述 SC AS发起所述终端与远端之间的媒体连接建 立流程， 使得终端从 CS域切换到 PS域时， 保证反向单待业务连续性。
本发明中当前 MSC指参与转移过程的 MSC,若在切换过程中 MSC不改 变， 该 MSC即本发明所说的当前 MSC; 若切换过程中 MSC需要从原 MSC 切换至目标 MSC, 则目标 MSC即本发明所说的当前 MSC。
如图 8所示， 本发明反向单待业务连续性的实现方法包括：
步骤 10: 切换准备通知步骤， 当前移动交换中心 （MSC )收到来自 CS 域的切换请求后， 向终端发送切换准备通知；
步骤 20: 转移请求步骤， 所述终端接收所述切换准备通知后， 通过原网 络向业务连续性应用服务器 （SC AS )发送转移请求， 携带所述终端的媒体 资源信息 Ml ;
步骤 30: 连接建立步骤， 所述终端发起所述终端与远端之间的媒体连接 建立流程，或触发所述 SC AS发起所述终端与远端之间的媒体连接建立流程。
具体流程参见以下实施例一至六。
信令锚定所述当前 MSC时， 参见以下实施例一、 二、 五， 所述连接建立 流程的方法为：
所述 SC AS接收到所述转移请求后， 通过所述当前 MSC向所述终端发 送建立连接消息。
媒体锚定所述当前 MSC时， 参见以下实施例一：
所述切换准备通知、 所述转移请求及建立连接消息中均携带会话关联信 息；
所述连接建立步骤中，所述当前 MSC向所述终端转发的所述建立连接消 息中携带所述当前 MSC的媒体资源信息；
所述当前 MSC收到所述终端的携带媒体资源信息的消息后，建立与所述 终端之间的媒体连接；
所述当前 MSC根据所述会话关联信息关联所述当前 MSC与所述终端之 间的所述媒体连接和所述当前 MSC与所述远端之间的媒体连接。
信令锚定当前 MSC时，为了保证媒体连接建立成功的一种方式： 连接建 立步骤中，所述当前 MSC收到所述终端发送的拒绝所述建立连接消息的消息 后， 重试转发所述建立连接消息。 参见实施例一、 二。
信令锚定当前 MSC时，为了保证媒体连接建立成功的另一种方式是： 连 接建立步骤中，所述当前 MSC接收到目标网络控制实体发送的切换完成通知 后， 再向所述终端转发所述建立连接消息。 参见实施例五。
所述目标网络控制实体在以下任一情形下发送切换完成通知：
所述当前 MSC收到来自 CS域的切换请求后， 向所述目标网络控制实体 发送切换通知， 所述目标网络控制实体感知所述终端接入到目标网络后， 向 所述当前 MSC发送切换完成通知； 或，
所述终端完成切换后， 向所述目标网络控制实体发送切换完成指示， 所 述目标网络控制实体接收所述指示后， 向所述当前 MSC发送切换完成通知。
信令不锚定当前 MSC时， 参见实施例三， 连接建立步骤中， 所述终端触 发所述 SC AS发起所述终端与远端之间的媒体连接建立流程的方法为：
所述 SC AS接收到所述转移请求后， 向所述终端发送建立连接消息。 参见实施例二、 三及五， 连接建立步骤包括：
所述 SC AS接收到所述转移请求后， 使用所述转移请求中的媒体资源信 息 Ml更新所述远端；
所述 SC AS接收到所述远端的携带媒体资源信息 M2的消息后， 将所述 媒体资源信息 M2通过所述建立连接消息发送出去；
所述终端接收到所述建立连接消息后， 发送消息携带所述终端的媒体资 源信息 M3 , 所述媒体资源信息 M3包含于所述媒体资源信息 Ml中。
信令不锚定当前 MSC时，为了保证媒体连接建立成功，连接建立步骤中， 所述 SC AS收到所述终端发送的拒绝所述建立连接消息的消息后， 重试转发 所述建立连接消息。 参见实施例三。
信令不锚定当前 MSC时， 参见实施例四和六， 连接建立步骤中， 所述终 端发起所述终端与远端之间的媒体连接建立流程的方法为：
所述终端通过所述转移请求发起媒体连接建立， 或， 所述终端在目标网 络发送携带媒体资源信息的第二转移请求发起媒体连接建立；
所述 SC AS接收到所述转移请求或所述第二转移请求后， 向所述终端发 送携带远端的媒体资源信息的响应消息。
下面将结合附图和实施例对本发明进行详细描述。
本发明中 MSC收到来自 CS域的切换请求后， 可以向目的网络控制实体 发送切换请求， 也可以不发送切换请求。
实施例一
图 2是本发明的反向单待业务连续性实现方法实施例一的流程图， 描述 了 UE-1和 UE-2间建立了通话， UE-1是通过 2/3G网络的 CS域建立通话的， 因此通话媒体路径中连接 UE-1的是一段 CS媒体连接， 当 UE-1移动需要改 变其使用的接入方式为 LTE或 HSPA的 PS域，后续会话通过目标 MSC的媒 体锚定建立媒体连接，且目标 MSC是原 MSC的情况下， UE-1实现反向单待 业务连续性的过程包括如下步骤：
步骤 201、 UE-1通过 CS域及 MSC与 UE-2建立会话， MSC支持 IMS 信令， 且在原会话的信令路径中， 会话信令路径途经 SC AS; 步骤 202 ~ 203、 与图 1的步骤 101-102相同；
步骤 204、 MSC收到来自 CS域的切换请求， 立即向 UE-1发送切换准备 消息；
比如通过短消息 （ SMS ) 或非结构化补充数据业务 （Unstructured Supplementary Service Data—— USSD )发送要求 UE-1准备切换的消息， 消息 通过原网络的基站系统到达 UE-1 , 消息中携带 MSC的锚定指示信息， 比如 携带 MSC的标识信息以指示后续 IMS过程需要 MSC的信令锚定（信令锚定 指示） ， 并携带该 MSC在媒体路径中的指示信息 （媒体锚定指示， 以指示 UE的会话已经被 MSC锚定） ， 还携带会话关联信息， 或只带 MSC的标识 信息， 且该标识信息本身也可以用于会话关联， 比如以用户名 @主机名形式 标识目标 MSC, 其中用户名部分可用于会话关联。
步骤 205、 UE-1收到切换准备消息后， 可选地， 可回应切换准备响应消 息， 比如通过 SMS或 USSD发送该消息， 消息通过原网络的基站系统到达 MSC;
步骤 206、 UE-1收到切换准备消息后， 向 SC AS发送转移请求； 比如， 如果 UE在原网络有 PS域可用， 则可发送以 SC AS 为目标的 INVITE (邀请 )消息，如果没有则可通过 USSD向 SC AS发送 INVITE消息， 消息携带 UE-1将在目标网络使用的媒体资源信息， 比如 IP地址、 端口号、 编码器信息等， 消息还携带步骤 204中获得的锚定指示信息；
可理解地， UE-1发送的转移请求中的 UE-1的媒体资源信息在发送给 SC AS的过程中， 可能会被信令路径上的其他网元修改、 更新， 从而导致 SC AS 接收到的转移请求中的媒体资源信息已经不再是原来的媒体资源信息， 但该 媒体资源信息仍然是关联 UE-1的媒体资源信息。 其他实施例中的媒体资源信息均有类似的情形， 即发送端和接收端的媒 体资源信息可能有所变化， 但实质所指向的对象并不改变。
步骤 205可以在步骤 206之后， 即， UE-1在发送出转移请求后再发送切 换准备响应消息。 步骤 207、 如果 UE-1在原网络的 PS域还有业务， 执行标准的 PS到 PS 切换流程， 其过程与图 1的步骤 104~109相同；
步骤 208、 步骤 204或步骤 205之后， MSC向 CS域发送切换命令， 消 息到达原网络的基站系统；
步骤 209、 原网络的基站系统向 UE-1发送切换命令， 要求 UE-1切换到 目标网络；
步骤 210、 UE-1收到切换命令后， 调制到目标网络接入；
步骤 211、 步骤 206后， SC AS收到转移请求， 根据锚定指示中的媒体 锚定指示判断无需更新远端， 于是不更新远端；
步骤 212、 可选地， SC AS响应转移请求， 比如发送 "200 OK" 消息给 UE-1 ;
步骤 213、 步骤 211后， SC AS收到转移请求， SC AS通过转移请求中 的主叫用户信息找到 UE-1的用户标识（主叫用户信息本身就可以是 UE-1的 用户标识） ， 以该用户标识通过 PS域向 UE-1发送建立连接消息， 比如发送 INVITE消息， SC AS要求该建立连接消息途经 MSC, 比如在呼叫消息的头 域中设置路由信息，路由信息中包括 MSC的标识信息，如果该标识信息不能 用于会话关联， 则 SC AS还要在该建立连接消息中携带步骤 206中获得的会 话关联信息；
步骤 214、建立连接消息到达 MSC, MSC根据会话关联信息关联原会话， 并转发建立连接消息给 UE-1 , 在转发的建立连接消息中携带 MSC的媒体资 源信息；
此时， UE-1未必及时的接入了目标网络， 如果 UE-1此时尚未完成接入 目标网络的操作，转发的建立连接消息会被拒绝， 当 MSC收到转发的建立连 接消息的拒绝消息后， 重试转发建立连接消息的操作， 直到该建立连接消息 步骤 215、 UE-1收到建立连接消息，应答该建立连接消息，比如发送" 200 OK" 消息， 消息携带 UE-1的媒体资源信息；
步骤 216、 建立连接应答消息途经 MSC, MSC根据其中的媒体资源信息 完成与 UE-1的媒体协商， MSC转发建立连接应答消息给 SC AS; 至此， UE-1与 MSC间建立起 IMS媒体连接 2, MSC将新建的 IMS媒体 连接 2与原会话的 IMS媒体连接 1接起来， 使 UE-1能继续与 UE-2通话。
本实施例中，步骤 204中的锚定指示可以不携带 MSC的标识信息及会话 关联信息， 但增加携带 MSC的用于与 UE-1相连的媒体资源信息， 于是步骤 213中 SC AS不能要求建立连接消息途经 MSC, SC AS在建立连接消息中携 带获得的 MSC的用于与 UE-1相连的媒体资源信息， 于是步骤 213就不再途 经 MSC到达 UE-1 ,步骤 214就没有了，步骤 215也不再途经 MSC到达 SC AS, 步骤 216就没有了。
实施例二
图 3是本发明的反向单待业务连续性实现方法实施例二的流程图， 描述 了 UE-1和 UE-2间建立了通话， UE-1是通过 2/3G网络的 CS域建立通话的， 因此通话媒体路径中连接 UE-1的是一段 CS媒体连接， 当 UE-1移动需要改 变其使用的接入方式为 LTE或 HSPA的 PS域，后续会话通过目标 MSC的信 令锚定但非媒体锚定建立媒体连接，且目标 MSC不是原 MSC的情况下， UE-1 和 SC AS通过 MSC进行交互， UE-1实现反向单待业务连续性的过程包括如 下步骤：
步骤 301、 UE-1通过 CS域及原 MSC与 UE-1建立会话， 目标 MSC支 持 IMS信令但不在信令路径中， 会话信令路径途经 SC AS;
步骤 302 ~ 303、 与图 1的步骤 101~102相同;
步骤 304、原 MSC收到切换请求，向目标 MSC发起标准的 CS域的局间 切换过程， 原 MSC向目标 MSC发送切换请求；
步骤 305、 目标 MSC收到来自 CS域的切换请求， 立即向 UE-1发送切 换准备消息；
比如通过短消息 （ SMS ) 或非结构化补充数据业务 （Unstructured Supplementary Service Data—— USSD )发送要求 UE-1准备切换的消息， 消息 通过原网络的基站系统到达 UE-1 , 消息中携带 MSC的锚定指示信息， 比如 携带 MSC的标识信息， 还携带会话关联信息， 或只带 MSC的标识信息， 且 该标识信息本身也可以用于会话关联， 比如以用户名 @主机名形式标识目标 MSC, 其中用户名部分可用于会话关联；
步骤 306、 UE-1收到切换准备消息后， 可选地， 可回应切换准备响应消 息， 比如通过 SMS或 USSD发送该消息， 消息通过原网络的基站系统到达 MSC;
步骤 307、 UE-1收到切换准备消息后， 向 SC AS发送转移请求； 比如， 如果 UE在原网络有 PS域可用， 则可发送以 SC AS 为目标的 INVITE (邀请 ) 消息， 如果没有 PS域可用， 则可通过 USSD向 SC AS发送 INVITE消息， 消息携带 UE-1将在目标网络使用的媒体资源信息， 比如 IP地 址、 端口号、 编码器信息等， 消息还携带步骤 305中获得的锚定指示信息； 步骤 306可以在步骤 307之后， 即， UE-1在发送出转移请求后再发送切 换准备响应消息。
步骤 308、 如果 UE-1在原网络的 PS域还有业务， 执行标准的 PS到 PS 切换流程， 其过程与图 1的步骤 104~109相同；
步骤 309、步骤 305或步骤 306之后， 目标 MSC向 CS域的原 MSC发送 切换响应， 消息到达原 MSC;
步骤 310、原 MSC向 CS域发送切换命令， 消息到达原网络的基站系统； 步骤 311、 原网络的基站系统向 UE-1发送切换命令， 要求 UE-1切换到 目标网络；
步骤 312、 UE-1收到切换命令后， 调制到目标网络接入；
步骤 313、 步骤 307后， SC AS收到转移请求， 向 UE-2发送更新请求， 比如发送 UPDATE (更新 )消息或 relNVITE (重邀请 )消息， 消息携带步骤 307中获得的 UE-1的媒体资源信息， 步骤 313中的 UE-1的媒体资源信息与 步骤 307中的 UE-1的媒体资源信息的格式可能不同，比如步骤 307使用 USSD 发送转移请求时， 但内容是一致的；
步骤 314、 更新消息途经 CSCF到达 UE-2, UE-2响应更新请求， 比如发 送 "200 OK" 消息， 消息携带 UE-2的媒体资源信息； 步骤 315、 可选地， 步骤 314后， SC AS响应转移请求， 比如发送 "200 OK" 消息给 UE-1 ;
步骤 316、 步骤 314后， SC AS收到更新响应消息， SC AS通过转移请 求中的主叫用户信息找到 UE-1的用户标识（主叫用户信息本身就可以是 UE-1 的用户标识） ， 以该用户标识通过 PS域向 UE-1发送建立连接消息， 比如发 送 INVITE消息， SC AS要求该建立连接消息途经 MSC, 比如在呼叫消息的 头域中设置路由信息，路由信息中包括 MSC的标识信息，如果该标识信息不 能用于会话关联， 则 SC AS还要在该建立连接消息中携带步骤 307中获得的 会话关联信息；
步骤 317、建立连接消息到达 MSC, MSC根据会话关联信息关联原会话， 并转发建立连接消息给 UE-1；
此时， UE-1未必及时的接入了目标网络， 如果 UE-1此时尚未完成接入 目标网络的操作，转发的建立连接消息会被拒绝， 当 MSC收到转发的建立连 接消息的拒绝消息后， 重试转发建立连接消息的操作， 直到该建立连接消息 步骤 318、 UE-1收到建立连接消息，应答该建立连接消息，比如发送" 200 OK" 消息， 消息携带 UE-1的媒体资源信息， 其内容包含于步骤 307中提供 的媒体资源信息内容中； 步骤 319、 建立连接应答消息途经 MSC和 CSCF到达 SC AS;
至此， UE-1与 UE-2间建立起 IMS媒体连接 1 , 使 UE-1能继续与 UE-2 通话。
此例中， 如果原 MSC与目标 MSC为同一个 MSC, 则步骤 301中， 目标 MSC也在原会话的信令路径中， 且步骤 304与 309就没有了。
实施例三
图 4是本发明的反向单待业务连续性实现方法实施例三的流程图， 描述 了 UE-1和 UE-2间建立了通话， UE-1是通过 CS域接入建立通话的， 因此通 话媒体路径中连接 UE-1的是一段 CS媒体连接， 当 UE-1移动需要改变其使 用的接入方式为 LTE或 HSPA的 PS域， 目标 MSC不在后续会话的信令路径 中， 且目标 MSC不是原 MSC的情况下， UE-1和 SC AS直接进行交互， 实 现反向单待业务连续性的过程包括如下步骤：
步骤 401-404, 与图 3的 301-304相同；
步骤 405、 MSC收到来自 CS域的切换请求， 立即向 UE-1发送切换准备 消息， 比如通过短消息 （SMS ) 或非结构化补充数据业务 （Unstructured Supplementary Service Data—— USSD )发送要求 UE-1准备切换的消息， 消息 通过原网络的基站系统到达 UE-1；
步骤 406、 UE-1收到切换准备消息后， 可选地， 可回应切换准备响应消 息， 比如通过 SMS或 USSD发送该消息， 消息通过原网络的基站系统到达 MSC;
步骤 407、 UE-1收到切换准备消息后， 向 SC AS发送转移请求， 比如， 如果 UE在原网络有 PS域可用，则可发送以 SC AS为目标的 INVITE (邀请 ) 消息， 如果没有 PS域可用， 则可通过 USSD向 SC AS发送 INVITE消息， 消 息携带 UE-1将在目标网络使用的媒体资源信息， 比如 IP地址、 端口号、 编 码器信息等；
步骤 408-415, 与图 3的步骤 308-315相同；
步骤 416、 步骤 414后， SC AS收到更新响应消息， SC AS通过转移请 求中的主叫用户信息找到 UE-1的用户标识（主叫用户信息本身就可以是 UE-1 的用户标识） ， 以该用户标识通过 PS域向 UE-1发送建立连接消息， 比如发 送 INVITE消息， SC AS不要求该建立连接消息途经 MSC;
此时， UE-1未必及时的接入了目标网络， 如果 UE-1此时尚未完成接入 目标网络的操作， 转发的建立连接消息会被拒绝， 当 SC AS收到转发的建立 连接消息的拒绝消息后， 重试转发建立连接消息的操作， 直到该建立连接消 息被接受。
步骤 417、 UE-1收到建立连接消息，应答该建立连接消息，比如发送" 200 OK" 消息， 消息携带 UE-1的媒体资源信息， 其内容包含于步骤 407中提供 的媒体资源信息内容中， 建立连接应答消息途经 CSCF到达 SC AS; 至此， UE-1与 UE-2间建立起 IMS媒体连接 1 , 使 UE-1能继续与 UE-2 通话。
此例中， 如果原 MSC与目标 MSC为同一个 MSC, 则步骤 401中， 目标 MSC也在原会话的信令路径中， 且步骤 404与 409就没有了。
实施例四
图 5是本发明的反向单待业务连续性实现方法实施例四的流程图， 描述 了 UE-1和 UE-2间建立了通话， UE-1是通过 CS域接入建立通话的， 因此通 话媒体路径中连接 UE-1的是一段 CS媒体连接， UE-1和 UE-2无需锚定的 MSC建立媒体连接，当 UE-1移动需要改变其使用的接入方式为 LTE或 HSPA 的 PS域且目标 MSC不是原 MSC的情况下， UE-1和 SC AS通过一次交互， 实现反向单待业务连续性的过程包括如下步骤：
步骤 501、 UE-1通过 CS域及原 MSC与 UE-1建立会话， 目标 MSC不 在信令路径中， 会话信令路径途经 SC AS, UE-1在原网络中可使用其 PS域 发送数据；
步骤 502-506, 与图 4的 402-406相同；
步骤 507、 UE-1收到切换准备消息后， 向 SC AS发送转移请求； 因为 UE-1在原网络有 PS域可用，则发送以 SC AS为目标的 INVITE(邀 请）消息， 消息携带 UE-1将在目标网络使用的媒体资源信息， 比如 IP地址、 端口号、 编码器信息等； 步骤 508 514、 与图 4的 408~414相同；
步骤 515、 步骤 514后， SC AS收到更新响应消息， SC AS响应转移请 求， 比如发送 " 200 OK" 消息， 消息携带步骤 514中获得的媒体资源信息； 此时， UE-1未必及时的接入了目标网络， 如果 UE-1此时尚未完成接入 目标网络的操作， 转移响应会被拒绝（比如收到 BYE消息）， 当 SC AS收到 转移响应的拒绝消息后， 重试发送转移响应的操作， 直到该转移响应被接受。
至此， UE-1与 UE-2间建立起 IMS媒体连接 1 , 使 UE-1能继续与 UE-2 通话。 此例中， 如果原 MSC与目标 MSC为同一个 MSC, 则步骤 501中， 目标 MSC也在原会话的信令路径中， 且步骤 504与 509就没有了。
实施例五
图 6是本发明的反向单待业务连续性实现方法实施例五的流程图， 描述 了 UE-1和 UE-2间建立了通话， UE-1是通过 CS域接入建立通话的， 因此通 话媒体路径中连接 UE-1的是一段 CS媒体连接， UE-1和 UE-2无需锚定的 MSC建立媒体连接，当 UE-1移动需要改变其使用的接入方式为 LTE或 HSPA 的 PS域且目标 MSC不是原 MSC情况下， 实现反向单待业务连续性的过程 包括如下步骤：
步骤 601~615、 与图 3的步骤 301~315相同；
步骤 616、 步骤 614后， SC AS收到更新响应消息， SC AS通过转移请 求中的主叫用户信息找到 UE-1的用户标识（主叫用户信息本身就可以是 UE-1 的用户标识） ， 以该用户标识通过 PS域向 UE-1发送建立连接消息， 比如发 送 INVITE消息， SC AS要求该建立连接消息途经 MSC, 比如在呼叫消息的 头域中设置路由信息，路由信息中包括 MSC的标识信息，如果该标识信息不 能用于会话关联， 则 SC AS还要在该建立连接消息中携带步骤 307中获得的 会话关联信息， 消息途经目标 MSC, 目标 MSC根据会话关联信息关联原会 话， 但不立即转发该消息；
步骤 617、 UE-1切换到目标网络， 向目标网络控制实体发送通知切换完 成的消息， 比如发送携带从 CS域切换过来的指示的 Attach Request (附着请 求） 消息或 Tracking Area Update (路径区域更新） 消息， 或携带切换指示的 Service Request (业务请求） 消息等；
步骤 618、 目标网络的控制实体向目标 MSC发送切换完成通知消息， 比 如发送 PS to CS Handover Complete Notification消息， 目标网络的控制实体可 以通过 UE-1接入的目标小区信息确定目标 MSC;
步骤 619、目标 MSC收到来自目标网络控制实体的切换完成通知消息后， 转发步骤 616的建立连接消息给 UE-1 ; 步骤 620~621、 与图 3的步骤 318~319相同；
至此， UE-1与 UE-2间建立起 IMS媒体连接 1 , 使 UE-1能继续与 UE-2 通话。
此例中， 步骤 617为 UE通知目标网络控制网元 CS到 PS切换完成， 实 际实施中， 也可以在步骤 604后由 MSC通知目标网络控制网元发生了 CS到 PS的切换， 这样当目标网络控制网元感知到 UE接入目标网络后， 目标网络 控制网元就可执行步骤 618。
此例中， 如果原 MSC与目标 MSC为同一个 MSC, 则步骤 601中， 目标 MSC也在原会话的信令路径中， 且步骤 604与 609就没有了。
实施例六
图 7 是本发明的反向单待业务连续性实现方法流程图六， 描述了 UE-1 和 UE-2间建立了通话， UE-1是通过 CS域接入建立通话的， 因此通话媒体 路径中连接 UE-1的是一段 CS媒体连接， 当 UE-1移动需要改变其使用的接 现反向单待业务连续性的过程包括如下步骤：
步骤 701~715、 与图 4的 401~415相同；
步骤 716、 UE-1完成切换后， UE-1在目标网络的 PS域发起转移请求， 比如以 SC AS的标识为目标发送 INVITE消息，消息携带 UE-1的媒体资源信 息， 其媒体资源信息内容包含于步骤 707中的 UE-1的媒体资源信息内容中， 消息途经 CSCF到达 SC AS;
步骤 717、 SC AS收到 UE-1发送的转移请求， 响应该转移请求， 比如发 送 "200 OK" 消息， 消息携带步骤 714中获得的 UE-2的媒体资源信息； 至此， UE-1与 UE-2间建立起 IMS媒体连接 1 , 使 UE-1能继续与 UE-2 通话。
此例中， 如果原 MSC与目标 MSC为同一个 MSC, 则步骤 701中， 目标 MSC也在原会话的信令路径中， 且步骤 704与 709就没有了。 为实现以上方法，本发明还提供了一种反向单待业务连续性的实现系统， 该系统包括： MSC和终端； 其中
移动交换中心 （MSC ) 包括切换控制模块， 该切换控制模块设置成： 在 所述 MSC为当前 MSC时， 在收到来自 CS域的切换请求后， 向终端发送切 换准备通知；
所述终端包括连接建立控制模块， 所述连接建立控制模块设置成： 接收 所述切换准备通知， 并在接收所述切换准备通知后， 通过原网络向业务连续 性应用服务器 （SC AS )发送转移请求， 其中携带所述终端的媒体资源信息 Ml ;以及，发起所述终端与远端之间的媒体连接建立流程，或触发所述 SC AS 发起所述终端与远端之间的媒体连接建立流程。
对应于实施例一、 二、 五， 所述系统还包括 SC AS, 所述 SC AS包括连 接建立控制模块， 该连接建立控制模块设置成： 接收所述转移请求， 并在接 收到所述转移请求后通过当前 MSC向所述终端发送建立连接消息。
对应于实施例一， 所述切换准备通知、 转移请求及建立连接消息中均携 带会话关联信息； 所述 MSC还包括建立连接消息转发模块及连接建立模块， 其中建立连接消息转发模块设置成： 接收所述 SC AS发送的建立连接消息， 并向终端转发所述建立连接消息，转发的建立连接消息中携带所述 MSC的媒 体资源信息； 所述连接建立模块设置成： 接收到所述终端的携带媒体资源信 息的消息后， 建立与所述终端之间的媒体连接， 以及， 根据所述会话关联信 息关联所述当前 MSC与所述终端之间的所述媒体连接和所述当前 MSC与所 述远端之间的媒体连接。
对应于实施例一、二， 所述 MSC的连接建立模块还设置成在收到所述终 端发送的拒绝所述建立连接消息的消息后， 重试转发所述建立连接消息。
对应于实施例五，所述 MSC的连接建立模块在接收到目标网络控制实体 发送的切换完成通知后， 再向所述终端转发所述建立连接消息。
所述系统还包括目标网络控制实体； 所述 MSC 的切换控制模块还设置 成： 在收到来自 CS域的切换请求后， 向所述目标网络控制实体发送切换通 知； 所述目标网络控制实体设置成： 接收所述切换通知， 以及， 在感知所述 终端接入目标网络后或收到所述终端发送的切换完成指示后向所述当前
MSC发送切换完成通知。
对应于实施例三， 所述系统还包括 SC AS, 所述 SC AS包括连接建立控 制模块， 该连接建立控制模块设置成： 接收所述转移请求， 并在接收到所述 转移请求后向所述终端发送建立连接消息。
对应于实施例三， 所述 SC AS的连接建立控制模块还设置成在收到所述 终端发送的拒绝所述建立连接消息的消息后， 重试转发所述建立连接消息。
对应于实施例二、 三及五， 所述 SC AS的连接建立控制模块还设置成： 接收到所述转移请求后， 使用所述转移请求中的媒体资源信息 Ml 更新所述 远端； 以及接收到所述远端的携带媒体资源信息 M2的消息后， 将所述媒体 资源信息 M2通过所述建立连接消息发送出去； 所述终端的连接建立控制模 块还设置成： 接收所述建立连接消息， 以及， 接收到所述建立连接消息后， 发送携带所述终端的媒体资源信息 M3的消息， 所述媒体资源信息 M3 包含 于所述媒体资源信息 Ml中。
对应于实施例四、 六， 所述终端的连接建立控制模块发起所述终端与远 端之间的媒体连接建立流程的方式为：通过所述转移请求发起媒体连接建立， 或者，在目标网络发送携带媒体资源信息的第二转移请求发起媒体连接建立； 所述系统还包括 SC AS, 所述 SC AS还包括连接建立控制模块， 该模块设置 成： 接收所述转移请求或所述第二转移请求， 以及， 在接收到所述转移请求 或所述第二转移请求后向所述终端发送携带远端的媒体资源信息的响应消 息。
当然， 本发明还可有其他多种实施例， 在不背离本发明精神及其实质的 但这些相应的改变和变形都应属于本发明所附的权利要求的保护范围。
工业实用性 与现有技术相比， 本发明方法和系统通过终端辅助， 由终端通过原网络 向业务连续性应用服务器 （SC AS )发起转移请求， 且终端发起所述终端与 远端之间的媒体连接建立流程， 或触发所述 SC AS发起所述终端与远端之间 的媒体连接建立流程， 使得终端从 CS域切换到 PS域时， 保证反向单待业务 连续性。

Claims

权 利 要 求 书
1、 一种反向单待业务连续性的实现方法， 包括：
当前移动交换中心 （MSC )收到来自电路交换（CS )域的切换请求后， 向终端发送切换准备通知；
所述终端接收所述切换准备通知后， 通过原网络向业务连续性应用服务 器（SC AS )发送转移请求， 携带所述终端的媒体资源信息 Ml ; 以及
所述终端发起所述终端与远端之间的媒体连接建立流程，或触发所述 SC AS发起所述终端与远端之间的媒体连接建立流程。
2、 如权利要求 1所述的方法， 其中， 信令锚定所述当前 MSC;
的步骤包括： 所述 SC AS接收到所述转移请求后， 通过所述当前 MSC向所 述终端发送建立连接消息。
3、 如权利要求 2所述的方法， 其中， 媒体锚定所述当前 MSC;
所述切换准备通知、 所述转移请求及建立连接消息中均携带会话关联信 息；
通过所述当前 MSC 向所述终端发送建立连接消息的步骤中， 所述当前 MSC向所述终端转发的建立连接消息中携带所述当前 MSC的媒体资源信息； 所述方法还包括：所述当前 MSC接收所述终端的携带媒体资源信息的应 答消息， 并建立与所述终端之间的媒体连接； 以及
所述当前 MSC根据所述会话关联信息关联所述当前 MSC与所述终端之 间的媒体连接和所述当前 MSC与所述远端之间的媒体连接。
4、 如权利要求 2所述的方法， 还包括： 所述当前 MSC收到所述终端发 送的拒绝所述建立连接消息的消息后， 重试转发所述建立连接消息。
5、 如权利要求 2所述的方法， 其中， 通过所述当前 MSC向所述终端发 送建立连接消息的步骤中，所述当前 MSC接收到目标网络控制实体发送的切 换完成通知后， 再向所述终端转发所述建立连接消息。
6、 如权利要求 5所述的方法， 其中， 所述目标网络控制实体在以下任一 情形下发送切换完成通知：
所述当前 MSC收到来自 CS域的切换请求后， 向所述目标网络控制实体 发送切换通知， 所述目标网络控制实体感知所述终端接入到目标网络后， 向 所述当前 MSC发送切换完成通知； 或者，
所述终端完成切换后， 向所述目标网络控制实体发送切换完成指示， 所 述目标网络控制实体接收所述指示后， 向所述当前 MSC发送切换完成通知。
7、 如权利要求 1所述的方法， 其中， 所述终端触发所述 SC AS发起所 述终端与远端之间的媒体连接建立流程的步骤包括：
所述 SC AS接收到所述转移请求后， 向所述终端发送建立连接消息。
8、 如权利要求 7所述的方法， 其还包括： 所述 SC AS收到所述终端发 送的拒绝所述建立连接消息的消息后， 重试转发所述建立连接消息。
9、 如权利要求 2或 7所述的方法， 还包括：
所述 SC AS接收到所述转移请求后， 使用所述转移请求中的媒体资源信 息 Ml更新所述远端；
所述 SC AS接收到所述远端的携带媒体资源信息 M2的消息后， 将所述 媒体资源信息 M2通过所述建立连接消息发送出去； 以及
所述终端接收到所述建立连接消息后， 发送消息携带所述终端的媒体资 源信息 M3 , 所述媒体资源信息 M3包含于所述媒体资源信息 Ml中。
10、 如权利要求 1所述的方法， 其中， 所述终端发起所述终端与远端之 间的媒体连接建立流程的步骤包括：
所述终端通过所述转移请求发起媒体连接建立流程， 或者， 所述终端在 目标网络发送携带媒体资源信息的第二转移请求发起媒体连接建立流程； 所述方法还包括： 所述 SC AS接收到所述转移请求或所述第二转移请求 后， 向所述终端发送携带远端的媒体资源信息的响应消息。
11、 一种反向单待业务连续性的实现系统， 包括： 移动交换中心（MSC ) 和终端； 其中， 所述 MSC包括切换控制模块， 所述切换控制模块设置成： 在所述 MSC 为当前 MSC时， 在收到来自电路交换（CS )域的切换请求后， 向终端发送 切换准备通知；
所述终端包括连接建立控制模块， 所述连接建立控制模块设置成： 接收 所述切换准备通知， 并在接收到所述切换准备通知后， 通过原网络向业务连 续性应用服务器 （SC AS )发送转移请求， 其中携带所述终端的媒体资源信 息 Ml ; 以及， 发起所述终端与远端之间的媒体连接建立流程， 或触发所述 SC AS发起所述终端与远端之间的媒体连接建立流程。
12、 如权利要求 11所述的系统， 还包括 SC AS, 所述 SC AS包括连接 建立控制模块，所述 SC AS的连接建立控制模块设置成：接收所述转移请求， 并在接收到所述转移请求后通过当前 MSC向所述终端发送建立连接消息。
13、 如权利要求 12所述的系统， 其中， 所述切换准备通知、 转移请求及 建立连接消息中均携带会话关联信息； 所述 MSC还包括建立连接消息转发模块及连接建立模块，所述建立连接 消息转发模块设置成： 接收所述 SC AS发送的建立连接消息， 并向终端转发 所述建立连接消息， 转发的建立连接消息中携带所述 MSC的媒体资源信息； 所述连接建立模块设置成： 接收终端的同意建立连接的应答消息， 该应答消 息中携带所述终端的媒体资源信息， 并在接收到所述应答消息后， 建立与所 述终端之间的媒体连接， 以及，根据所述会话关联信息关联所述 MSC与所述 终端之间的媒体连接和所述 MSC与所述远端之间的媒体连接。
14、 如权利要求 13所述的系统， 其中， 所述 MSC的连接建立模块还设 置成： 在收到所述终端发送的拒绝所述建立连接消息的消息后， 重试转发所 述建立连接消息。
15、 如权利要求 13所述的系统， 其中， 所述 MSC的建立连接消息转发 模块是设置成在接收到目标网络控制实体发送的切换完成通知后， 再向所述 终端转发所述建立连接消息。
16、 如权利要求 15所述的系统， 其中， 所述系统还包括目标网络控制实 体； 所述 MSC的切换控制模块还设置成： 在收到来自 CS域的切换请求后， 向所述目标网络控制实体发送切换通知； 所述目标网络控制实体设置成： 接 收所述切换通知， 以及， 在感知所述终端接入目标网络后或收到所述终端发 送的切换完成指示后向当前 MSC发送切换完成通知。
17、 如权利要求 11所述的系统， 还包括 SC AS, 所述 SC AS包括连接 建立控制模块， 所述 SC AS的连接建立控制模块设置成接收所述转移请求， 并在接收到所述转移请求后向所述终端发送建立连接消息。
18、 如权利要求 17所述的系统， 其中， 所述 SC AS的连接建立控制模 块还设置成在收到所述终端发送的拒绝所述建立连接消息的消息后， 重试转 发所述建立连接消息。
19、 如权利要求 12或 17所述的系统， 其中， 所述 SC AS的连接建立控 制模块还设置成： 接收到所述转移请求后， 使用所述转移请求中的媒体资源 信息 Ml 更新所述远端； 以及， 在接收到所述远端的携带媒体资源信息 M2 的消息后， 将所述媒体资源信息 M2通过所述建立连接消息发送出去； 所述 终端的连接建立控制模块还设置成： 接收所述建立连接消息， 并在接收到所 述建立连接消息后， 发送携带所述终端的媒体资源信息 M3 的消息， 所述媒 体资源信息 M3包含于所述媒体资源信息 Ml中。
20、 如权利要求 11所述的系统， 其中， 所述终端的连接建立控制模块是 设置成通过如下方式发起所述终端与远端之间的媒体连接建立流程： 通过所 述转移请求发起媒体连接建立流程， 或者， 通过目标网络发送携带所述媒体 资源信息 Ml 的第二转移请求发起媒体连接建立流程； 所述系统还包括 SC AS, 所述 SC AS包括连接建立控制模块： 所述 SC AS的连接建立控制模块 设置成： 接收所述转移请求或所述第二转移请求， 以及在接收到所述转移请 求或所述第二转移请求后向所述终端发送携带远端的媒体资源信息的响应消 息。
PCT/CN2011/072470 2010-04-26 2011-04-06 反向单待业务连续性实现方法及系统 WO2011134341A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201010159281.7 2010-04-26
CN2010101592817A CN102238673A (zh) 2010-04-26 2010-04-26 反向单待业务连续性实现方法及系统

Publications (1)

Publication Number Publication Date
WO2011134341A1 true WO2011134341A1 (zh) 2011-11-03

Family

ID=44860853

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/072470 WO2011134341A1 (zh) 2010-04-26 2011-04-06 反向单待业务连续性实现方法及系统

Country Status (2)

Country Link
CN (1) CN102238673A (zh)
WO (1) WO2011134341A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103096392A (zh) * 2011-11-04 2013-05-08 中兴通讯股份有限公司 一种反向单待业务连续性承载切换方法及装置

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103200149A (zh) * 2012-01-04 2013-07-10 中兴通讯股份有限公司 一种反向单待业务连续性实现方法和装置
CN104936262B (zh) * 2014-03-21 2020-02-28 中兴通讯股份有限公司 远端标识的发送、接收方法及装置、传输系统
CN108541031B (zh) * 2017-03-03 2020-07-21 华为技术有限公司 业务切换方法、装置及系统

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101389130A (zh) * 2007-09-13 2009-03-18 华为技术有限公司 一种核心网实体及基于vcc语音呼叫的切换方法

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101389130A (zh) * 2007-09-13 2009-03-18 华为技术有限公司 一种核心网实体及基于vcc语音呼叫的切换方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"Voice Call Continuity between CS and IMS Study", 3GPP TR 23.806 V7.0.0, December 2005 (2005-12-01) *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103096392A (zh) * 2011-11-04 2013-05-08 中兴通讯股份有限公司 一种反向单待业务连续性承载切换方法及装置

Also Published As

Publication number Publication date
CN102238673A (zh) 2011-11-09

Similar Documents

Publication Publication Date Title
US8180347B2 (en) Domain transferring method for single radio voice call continuity
US9467907B2 (en) Handover of user-equipment (UE) undetected emergency calls
JP5694348B2 (ja) ハンドオーバー遅延の最適化
WO2012025007A1 (zh) 终端、hss、及核心网网元获知终端能力的方法和系统
WO2010025602A1 (zh) 紧急业务切换方法
WO2008046319A1 (fr) Procédé et système pour assurer la continuité d'un appel vocal lors de la gestion d'une affaire urgente
WO2011026438A1 (zh) 跨无线接入技术的语音切换方法、设备及网络系统
WO2012024908A1 (zh) 一种终端能力上报的方法及系统
US8934454B2 (en) Method and system for switching circuit switch domain service to packet switch domain
EP2485530B1 (en) System and method for switching ringing state session with customized alerting tone
WO2010091573A1 (zh) 一种紧急业务会话的切换方法及紧急业务系统
WO2011057568A1 (zh) 一种会话切换的实现方法和系统
WO2011127790A1 (zh) 一种实现单待业务连续性会话保活的方法和系统
WO2011130949A1 (zh) 反向单待业务连续性实现方法及系统
WO2011134341A1 (zh) 反向单待业务连续性实现方法及系统
WO2012149866A1 (zh) 单一无线语音呼叫连续性域的切换方法及系统
US20130045743A1 (en) Handover
WO2014005525A1 (zh) 资源承载的预留方法及系统
US20080254771A1 (en) Apparatus and method for performing call setup for domain transfer in mobile communication system
WO2011134334A1 (zh) 反向单待业务连续性的实现方法及系统
WO2011020368A1 (zh) 紧急附着的处理方法、装置和系统
WO2013064105A1 (zh) 一种反向单待业务连续性承载切换方法及装置
WO2012130126A1 (zh) 基于ims的控制切换方法及系统
WO2011023054A1 (zh) 一种ip多媒体子系统中多会话能力同步方法及系统
WO2011130954A1 (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: 11774332

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

Country of ref document: EP

Kind code of ref document: A1