WO2017124975A1 - 网络间切换的方法、装置、eMSC及SCC AS - Google Patents

网络间切换的方法、装置、eMSC及SCC AS Download PDF

Info

Publication number
WO2017124975A1
WO2017124975A1 PCT/CN2017/071136 CN2017071136W WO2017124975A1 WO 2017124975 A1 WO2017124975 A1 WO 2017124975A1 CN 2017071136 W CN2017071136 W CN 2017071136W WO 2017124975 A1 WO2017124975 A1 WO 2017124975A1
Authority
WO
WIPO (PCT)
Prior art keywords
msc
terminal
network
emsc
handover
Prior art date
Application number
PCT/CN2017/071136
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 WO2017124975A1 publication Critical patent/WO2017124975A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/14—Reselecting a network or an air interface
    • H04W36/144—Reselecting a network or an air interface over a different radio air interface technology
    • H04W36/1443—Reselecting a network or an air interface over a different radio air interface technology between licensed networks

Definitions

  • the present invention relates to the field of communications, and in particular, to a method, an apparatus, an eMSC, and an SCC AS for inter-network handover.
  • IP Multimedia Subsystem is an IP-based network architecture proposed by the 3rd Generation Partnership Project (3GPP). It has built an open and flexible business environment, supports multimedia applications, and provides 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 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).
  • 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.
  • Prxy-CSCF proxy call session control function
  • I-CSCF query call session control function
  • S-CSCF service call session control function
  • 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, and invokes the service on the AS to implement the service function.
  • An end-to-end device in a session is called a user equipment (User Equipment, UE for short) and is responsible for interacting with users.
  • Some UEs have multiple ways to access the network, including packet switching through 3GPP (Packet Switch, PS for short).
  • the domain access network accesses the network through other non-3GPP PS domains, and can even access the network through a Circuit Switch (CS) domain.
  • CS Circuit Switch
  • SRVCC Single Radio Voice Call Continuity
  • FIG. 1 is a schematic diagram of the architecture of the eSRVCC in the related art.
  • the user equipment UE 101 starts to access the PS access network 103 through a Source Radio Aceess Network (Source RAN).
  • the source radio access network may be a Universal Mobile Telecommunications System (UMTS) or an Evolved UMTS Terrestrial Radio Access Network (E-UTRAN).
  • UMTS Universal Mobile Telecommunications System
  • E-UTRAN Evolved UMTS Terrestrial Radio Access Network
  • the key entity of the PS access network is a Mobility Management Entity (MME) or a GPRS Serving Node (SGSN).
  • MME Mobility Management Entity
  • SGSN GPRS Serving Node
  • the IMS VoIP session is anchored to the Service Centralization and Continuity Application Server (SCC AS).
  • SCC AS Service Centralization and Continuity Application Server
  • the SRVCC switch When the signal of the Source RAN is not good, the SRVCC switch is triggered.
  • the source RAN configures a radio signal threshold. When the threshold is lower, the SRVCC is triggered.
  • the UE switches to the CS access network 110, connects to the Mobile Switching Center (MSC 109), and the MSC connects to the anchor SCC AS.
  • the MSC 109 can be composed of two MSCs, an enhanced MSC (SRVCC) and a Serving MSC.
  • the eMSC acts as an anchor to initiate a handover to the IMS network.
  • the eMSC reserves resources in the CS access network through the Serving MSC, and accesses the UE 101 to the Serving MSC through the CS access network. When there is only one MSC, the MSC is both an eMSC and a Serving MSC.
  • the Serving MSC also has a Visitor Location Register (VLR), which is collectively referred to as the Serving MSC in the following expressions, and does not distinguish between the two.
  • VLR Visitor Location Register
  • the session is also anchored to the Access Transfer Control Function (ATCF) and the Access Transfer Gateway (ATGW), and the UE to the SCC AS session is performed by the UE. Composed to ATCF, and two sessions of ATCF to SCC AS. After the SRVCC handover, the UE to the SCC AS session becomes a UE---Serving MSC---eMSC---ATCF/ATGW---SCC-AS.
  • ATCF Access Transfer Control Function
  • ATGW Access Transfer Gateway
  • the Home Subscriber Server (HSS) and the Home Location Register (HLR) store the subscription information of the user. Described as HSS/HLR, or HSS, or HLR, the following is not different.
  • the SRVCC not only supports the session SRVCC during the call, but also supports the switching of the aerting session and the pre-alerting session on the calling side.
  • 2 is a schematic diagram of time definition of a terminating side SRVCC, an altering SRVCC and a pre-alerting SRVCC in the related art, as shown in FIG. 2,
  • the so-called in-call session SRVCC means that the UE has connected to the remote end and is in a call, whether this SRVCC handover has occurred.
  • Alerting SRVCC means that the UE and the remote end have not connected to the call, and the UE can hear the ringing tone on the calling side. If the UE is on the called side, it starts ringing.
  • Pre-laerting SRVCC means that the UE and the remote end have not yet connected the call, the ringing tone cannot be heard on the calling side, and the called side does not start ringing.
  • FIG. 3 is a flowchart of a single mode service continuity switch of a ringing state session on a terminating side in the related art. As shown in FIG. 3, the process includes the following steps:
  • Step S301 The SCC AS on the called side receives the call request, and the call request is forwarded to the UE.
  • Step S302 The called UE sends a 180 ringing message to the remote end (the intermediate step is omitted);
  • Step S303 The Source RAN finds that the UE signal quality is not good, and needs to switch, and sends a handover request to the MME/SGSN.
  • Step S305 The MME/SGSN sends a PS to CS handover request to the eMSC.
  • Step S306 The eMSC reserves resources to the target radio access network (Target RAN) RNC/BSS; this process may be that the eMSC determines the target Serving MSC to be completed by the Serving MSC.
  • Target RAN target radio access network
  • Step S307 The eMSC sends a handover request response to the MME, indicating that the handover can be performed.
  • Step S308 The MME sends a handover command to the UE through the source radio access network.
  • Step S308a The UE switches to the CS access network, and continues to ring;
  • Step S309 The MSC initiates a session switching request to the anchor SCC AS of the session;
  • Step S307 and step S309 may be in parallel.
  • Step S309a The SCC AS updates the remote end, and the call is still in the ringing state;
  • Step S310 The SCC AS notifies the eMSC that the UE is currently in a ringing state
  • Step S311 The user picks up the phone and picks up the phone
  • Step S312 The UE sends a Connect message to the eMSC.
  • Step S312b on the eMCS, the session becomes an active state
  • Step S313 The eMSC sends a call notification to the SCC AS, and the user connects to the phone;
  • Step S314 The SCC AS updates the remote end.
  • the session state is pre-alerting
  • only the handover on the calling side is supported.
  • the network or the terminal does not support the SRVCC handover in the pre-alerting state
  • the called UE performs the SRVCC handover in the pre-alerting state, the handover failure may occur.
  • the handover will fail even if the network supports aering SRVCC.
  • the CS session ends and the UE returns to the LTE network. At this time, the UE is called again, and the handover failure still occurs. In some cases, the user cannot successfully receive the call.
  • FIG. 4 is a flowchart of a handover failure of a terminating UE in a pre-alerting or aerting state in the related art. As shown in FIG. 4, the user is caught in a situation in which a call cannot be received.
  • Step S401 The SCC AS on the called side receives the call request, and the call request is forwarded to the UE.
  • Step S402 The called UE sends a 183 message to the remote end. (exchange media information of the session);
  • Step S404 The Source RAN finds that the UE signal quality is not good and needs to switch, and sends a handover request.
  • the steps here are the same as steps S303-308 of FIG. 3;
  • Step S405 After the UE switches to the CS domain, the UE initiates the pre-alerting state and considers that the handover fails.
  • Step S406 The UE sends a Disconnect message to the eMSC.
  • Step S407 The eMSC initiates a session transfer to the SCC AS while sending a handover response to the MME in step S404. Since the SCC AS does not support pre-alerting handover, the SCC will notify the eMSC that the handover fails.
  • Step S408 The entire handover fails; when the called UE itself does not support aerting, the process is similar to the above figure. Although step S407 will succeed, after the UE sends a Disconnect in step S406, the eMSC releases the call of the current year to the SCC AS.
  • Step S409 The UE returns to the Source RAN.
  • Step S410 When the UE does not move, the signal coverage does not change. At this time, the call is received again, and steps S401 to 409 are repeated.
  • the called user terminal does not support pre-alerting or SRVCC switching in the aerting state.
  • One way is to upgrade the UE to support the switching of these states.
  • the above-mentioned upgrade terminal scheme is very difficult, and even if the new terminal supports the switching of these states, the already produced UE still has this problem.
  • Another way is that the MME does not initiate handover for the called party under pre-alerting/alerting, but the MME does not understand the state of the IMS layer and cannot limit the occurrence of such handover.
  • the embodiment of the present invention provides a method and a device for processing inter-network handover, an eMSC, and an SCC AS, to at least solve the related art, when the called side is in a ringing state or a pre-ringing state, performing SRVCC switching, and a handover failure occurs.
  • the problem when the called side is in a ringing state or a pre-ringing state, performing SRVCC switching, and a handover failure occurs.
  • a method for processing inter-network handover including: determining that a single mode service continuity SRVCC handover fails when the called terminal is in a ringing state or a pre-ringing state; continuing to be based on the handover Visit the network for final call processing.
  • the SRVCC handover failure includes: receiving a terminal status message sent by the service consistency and continuity server SCC AS, and/or receiving the terminal Determining, by the called terminal, a first connection failure message; determining, according to the terminal status message and/or the first connection failure message, that the SRVCC handover fails.
  • the terminal status message indicates that the called terminal is in a ringing state or a pre-ringing state, and/or is used to determine that the called terminal is in a ringing state or a pre-ringing state, and does not support SRVCC switching. .
  • the method further includes: determining, after the network handover, the target serving mobile switching center S for the terminating call processing. MSC.
  • determining the target S-MSC for the terminal call processing after the network handover comprises: receiving a first network handover request message sent by the mobility management entity MME and/or the GPRS service node SGSN for requesting handover of the network,
  • the first network handover request message carries the identifier information of the MSC for identifying the registration of the called terminal, and the MSC that identifies the identifier information is the target S-MSC.
  • continuing to perform the terminal call processing based on the visited visited network includes at least one of: sending, by the determined target S-MSC, a first session establishment request message for establishing a session to the called terminal. And/or, querying the terminal roaming number from the target S-MSC according to the home location register HLR, or directly querying the terminal roaming number from the target S-MSC; according to the querying the terminal roaming number to the The calling terminal sends a second session establishment request message for establishing a session.
  • the first session establishment request message is a Setup message
  • the second session establishment request message is an initial address message IAM message.
  • the method further includes: sending a second connection failure message to the called terminal.
  • a method for processing inter-network handover comprising: receiving a second network handover request message sent by an enhanced mobile switching center eMSC for requesting network handover; And a network handover request message, where the terminal status message of the called terminal is sent to the eMSC, where the terminal status message is used by the eMSC to continue to perform terminal call processing based on the visited visited network.
  • the second network handover request message is further used to indicate that the eMSC supports a single mode service continuity SRVCC handover when in a ringing state or a pre-ringing state; or the terminal status message indicates the The calling terminal is in a ringing state or a pre-ringing state, and/or is used to determine that the called terminal is in a ringing state or a pre-ringing state, and does not support SRVCC switching.
  • a method for processing inter-network handover including: storing a mobile switching center MSC registered by a called terminal; and transmitting a third to the enhanced mobile switching center eMSC for requesting network switching.
  • the network switch request message where the third network switch request message carries identification information of the MSC for identifying the called terminal registration.
  • the identifier information is used by the eMSC to determine a target for the terminal call processing after the network handover before the single mode service continuity SRVCC handover fails when the called terminal is in a ringing state or a pre-ringing state. Serving the mobile switching center S-MSC.
  • a processing apparatus for inter-network handover including: a first determining module, configured to determine a single mode service continuity SRVCC when the called terminal is in a ringing state or a pre-ringing state The handover fails; the processing module is configured to continue to perform the terminal call processing based on the visited visited network.
  • the first determining module comprises: a first receiving unit, configured to receive a terminal status message sent by the service consistency and continuity server SCC AS, and/or to receive the first connection sent by the called terminal a failure message; the first determining unit is configured to determine that the SRVCC handover fails according to the terminal status message and/or the first connection failure message.
  • the apparatus further comprises: a second determining module, configured to determine a target serving mobile switching center S-MSC for the terminating call processing after the network handover.
  • a second determining module configured to determine a target serving mobile switching center S-MSC for the terminating call processing after the network handover.
  • the second determining module includes: a second receiving unit, configured to receive a first network switching request message sent by the mobility management entity MME and/or the GPRS serving node SGSN for requesting to switch the network, where the The network switching request message carries the identifier information of the MSC for identifying the registration of the called terminal.
  • the second determining unit is configured to determine that the MSC identified by the identifier information is the target S-MSC.
  • the processing module includes at least one of: a first sending unit, configured to send, by the determined target S-MSC, a first session establishment request message for establishing a session to the called terminal; and Or, the second sending unit is configured to query the terminal roaming number from the target S-MSC according to the home location register HLR, or directly query the terminal roaming number from the target S-MSC; The number sends a second session establishment request message for establishing a session to the called terminal.
  • a first sending unit configured to send, by the determined target S-MSC, a first session establishment request message for establishing a session to the called terminal
  • the second sending unit is configured to query the terminal roaming number from the target S-MSC according to the home location register HLR, or directly query the terminal roaming number from the target S-MSC; The number sends a second session establishment request message for establishing a session to the called terminal.
  • the apparatus further comprises: a first sending module, configured to send a second connection failure message to the called terminal.
  • an enhanced mobile switching center eMSC comprising the apparatus of any of the above.
  • an eMSC is provided, the eMSC being the same MSC as the serving mobile switching center S-MSC.
  • a processing apparatus for inter-network handover including: a receiving module, configured to receive a second network handover request message sent by an enhanced mobile switching center eMSC for requesting network handover; a sending module, configured to send, according to the second network switching request message, a terminal status message of the called terminal to the eMSC, where the terminal status message is used by the eMSC to continue to be based on the visited visited network Perform a call processing.
  • a service consistency and continuity server SCC AS is provided, including the apparatus described above.
  • a processing apparatus for inter-network handover including: a storage module configured to store a mobile switching center MSC registered by a called terminal; and a third sending module configured to perform enhanced mobile switching And a third network handover request message sent by the central eMSC for requesting network handover, where the third network handover request message carries identifier information for identifying the MSC that is registered by the called terminal.
  • a mobility management entity MME comprising the apparatus described above.
  • a GPRS Serving Node SGSN including the apparatus described above.
  • the single-mode service continuity SRVCC handover fails; and the terminal call processing is continued based on the visited visited network, and the called party in the related technology is solved.
  • the SRVCC switching is performed, and the switching failure problem occurs, and the SRVCC switching can be successfully established even when the terminal call does not support the ringing state or the pre-ringing state. The effect of the call.
  • FIG. 1 is a schematic structural diagram of an eSRVCC in the related art
  • FIG. 2 is a schematic diagram showing time definitions of a terminating side SRVCC, an altering SRVCC, and a pre-alerting SRVCC in the related art
  • FIG. 3 is a flowchart of a single mode service continuity switching of a ringing state session on a terminating side in the related art
  • FIG. 4 is a flowchart of a handover failure of a terminating UE in a pre-alerting or aerting state in the related art
  • FIG. 5 is a flowchart of a first processing method for inter-network handover according to an embodiment of the present invention
  • FIG. 6 is a flowchart of a second processing method for inter-network handover according to an embodiment of the present invention.
  • FIG. 7 is a flowchart of a third method for processing inter-network handover according to an embodiment of the present invention.
  • FIG. 8 is a flow chart 1 of a terminating side pre-alerting SRVCC according to an embodiment of the present invention.
  • FIG. 9 is a second flowchart of a terminating side pre-alerting SRVCC according to an embodiment of the present invention.
  • FIG. 10 is a flowchart 3 of a terminating side pre-alerting SRVCC according to an embodiment of the present invention.
  • FIG. 11 is a flowchart of a UE initiating a joint attach procedure at an EPC according to an embodiment of the present invention
  • FIG. 12 is a flowchart of an optimized manner of the embodiment shown in FIG. 8 according to an embodiment of the present invention.
  • FIG. 13 is a flowchart of a case where an SRVCC occurs in a UE in an alerting state and the UE does not support aerating SRVCC according to the embodiment shown in FIG. 8 according to an embodiment of the present invention
  • FIG. 14 is a diagram corresponding to the embodiment shown in FIG. 9 when the UE is in the alerting state, according to an embodiment of the present invention.
  • SRVCC and the UE does not support the flowchart in the case of aerting SRVCC;
  • FIG. 15 is a structural block diagram of a processing apparatus 1 for inter-network handover according to an embodiment of the present invention.
  • FIG. 16 is a structural block diagram of a first determining module 152 in a processing device for inter-network handover according to an embodiment of the present invention
  • FIG. 17 is a block diagram 1 of a preferred structure of a processing device 1 for inter-network handover according to an embodiment of the present invention
  • FIG. 18 is a structural block diagram of a second determining module 172 in a processing device for inter-network handover according to an embodiment of the present invention.
  • FIG. 19 is a structural block diagram of a processing module 154 in a processing apparatus for inter-network handover according to an embodiment of the present invention.
  • 20 is a block diagram 2 of a preferred structure of a processing device for inter-network handover according to an embodiment of the present invention
  • 21 is a schematic structural diagram of an enhanced mobile switching center eMSC according to an embodiment of the present invention.
  • FIG. 22 is a structural block diagram of a processing apparatus 2 for inter-network handover according to an embodiment of the present invention.
  • FIG. 23 is a schematic structural diagram of a service consistency and continuity server SCC AS according to an embodiment of the present invention.
  • FIG. 24 is a structural block diagram of a processing apparatus 3 for inter-network handover according to an embodiment of the present invention.
  • FIG. 25 is a structural block diagram of a mobility management entity MME according to an embodiment of the present invention.
  • FIG. 26 is a structural block diagram of a GPRS service node SGSN according to an embodiment of the present invention.
  • FIG. 5 is a flowchart of a method for processing inter-network handover according to an embodiment of the present invention. As shown in FIG. 5, the process includes the following steps:
  • Step S502 determining that the single mode service continuity SRVCC handover fails when the called terminal is in a ringing state or a pre-ringing state;
  • step S504 the terminal call processing is continued based on the visited visited network.
  • the terminal call processing based on the visited visited network is continued, and the ringing is not supported on the called side in relation to the related art.
  • the SRVCC is switched in the state or the pre-ringing state, the call is abandoned, and the terminal cannot receive the call.
  • the terminal call processing is continued based on the visited network, which not only effectively solves the related art, the called side is in the ringing state.
  • the SRVCC In the pre-ringing state, when the SRVCC is switched, the problem of handover failure occurs, and in the case that the SRVCC is switched when the terminal call does not support the ringing state or the pre-ringing state, the call can be successfully established, and the call can be effectively improved. The effect of successful establishment of efficiency.
  • the SRVCC handover failure may be performed from multiple aspects, for example, receiving a terminal status message sent by the service consistency and continuity server SCC AS, and/or receiving The first connection failure message sent to the called terminal; determining the SRVCC handover failure according to the terminal status message and/or the first connection failure message.
  • the terminal status message indicates that the called terminal is in a ringing state or a pre-ringing state, and/or is used to determine that the called terminal is in a ringing state or a pre-ringing state, and does not support SRVCC switching. It should be noted that the foregoing terminal status message may only include status information for indicating the status of the terminal.
  • the terminal when the terminal is in a pre-ringing state, it may directly determine that the terminal does not support SRVCC switching;
  • the status message may also include not only status information for the state in which the terminal is located, but also capability information that directly indicates whether the terminal supports SRVCC handover.
  • the terminal status message is used to determine that the called terminal is in the ringing state or the pre-ringing state, and does not support the SRVCC handover.
  • the method may also adopt multiple modes. For example, in the capability set supported by the called terminal, the terminal is not displayed. When the terminal is in the ringing state or the pre-ringing state, the SRVCC switching is not supported. Through the above message, it can be determined that the called terminal does not support the SRVCC switching in the ringing state or the pre-ringing state.
  • the target serving mobile switching center S-MSC for terminating call processing after the network handover may also be determined. It should be noted that, in different scenarios, the manner of determining the target S-MSC for the terminating call processing is also different.
  • the eMSC determines the target S-MSC through the source S-MSC; and when the MME and/or the SGSN stores the MSC registered by the called terminal, determining that the target S-MSC for the terminal call processing after the network handover includes: receiving the mobile a first network handover request message sent by the management entity MME and/or the GPRS service node SGSN for requesting handover of the network, where the first network handover request message carries identifier information for identifying the MSC registered by the called terminal; The MSC that identifies the identification information is the target S-MSC.
  • the manner of determining the target S-MSC for the terminal call processing is different according to the foregoing manner, and the manner of continuing the terminal call processing based on the visited visited network may be different. For example, at least one of the following may be included: directly passing the determined target S- The MSC sends a first session establishment request message for establishing a session to the called terminal, for example, the first session establishment request message may be a Setup message; and/or, first, query the terminal from the target S-MSC according to the home location register HLR.
  • the method further includes: sending a second connection failure message to the called terminal.
  • sending the second connection failure message to the called terminal the called terminal effectively clears the previously existing session state.
  • FIG. 6 is a flowchart of a second processing method for inter-network handover according to an embodiment of the present invention. As shown in FIG. 6, the process includes the following steps:
  • Step S602 receiving a second network handover request message sent by the enhanced mobile switching center eMSC for requesting network handover;
  • Step S640 sending, according to the second network handover request message, a terminal status message of the called terminal to the eMSC, where
  • the terminal status message is used by the eMSC to continue the terminal call processing based on the visited visited network.
  • the terminal status message indicates that the called terminal is in a ringing state or a pre-ringing state, and/or is used to determine that the called terminal is in a ringing state or a pre-ringing state, and does not support SRVCC switching. It should be noted that the terminal status message may only include status information for indicating the status of the terminal.
  • the terminal when the terminal is in the pre-ringing state, it may directly determine that the terminal does not support the SRVCC handover; of course, the terminal status message It is also possible to include not only status information for the state in which the terminal is located, but also capability information that directly indicates whether the terminal supports SRVCC handover. That is, the terminal status message is used to determine that the called terminal does not support SRVCC handover when it is in a ringing state or a pre-ringing state.
  • the terminal call processing based on the switched visited network is continued, as opposed to In the related art, when the called side does not support the ringing state or the pre-ringing state of the SRVCC, if the call is abandoned, the terminal cannot receive the call, and the terminal call processing is continued based on the visited network, which not only effectively solves the problem.
  • the SRVCC switching is performed, and the handover failure problem occurs, thereby achieving the SRVCC switching when the terminal call does not support the ringing state or the pre-ringing state.
  • the call can be successfully established, and the effect of the successful establishment of the call is effectively improved.
  • the foregoing second network handover request message is further used to indicate that the eMSC supports the single mode service continuity SRVCC handover when the eMSC supports the ringing state or the pre-ringing state.
  • FIG. 7 is a flowchart of a third method for processing inter-network handover according to an embodiment of the present invention. As shown in FIG. 7, the process includes the following steps:
  • Step S702 storing the mobile switching center MSC registered by the called terminal;
  • Step S704 a third network handover request message for requesting network handover is sent to the enhanced mobile switching center eMSC, where the third network handover request message carries identifier information for identifying the MSC registered by the called terminal.
  • the identifier information is used by the eMSC to determine the target serving mobile switching center S for the terminal call processing after the network handover before the single mode service continuity SRVCC handover fails when the called terminal is in the ringing state or the pre-ringing state. - MSC.
  • the terminal call processing is continued based on the visited visited network.
  • the ringing state or the pre-ringing state is not supported on the called side.
  • the terminal call processing is continued based on the visited network, which not only effectively solves the related art, when the called side is in the ringing state or the pre-ringing state.
  • SRVCC handover is performed, the problem of handover failure occurs, and the SRVCC handover can be successfully established when the terminal call does not support the ringing state or the pre-ringing state, and the call can be successfully established, thereby effectively improving the efficiency of successful call establishment. .
  • a method for successfully establishing a call after the SRVCC handover occurs after the terminating UE fails to support the pre-laerting/alerting SRVCC handover is provided.
  • the eMSC session is not released.
  • the eMSC receives the status of the user from the SCC AS (pre-alerting/alerting), and/or receives the disConnect message of the UE, the eMSC knows The switch fails and continues to complete the call in the CS domain.
  • FIG. 8 is a flowchart 1 of a terminating side pre-alerting SRVCC according to an embodiment of the present invention. As shown in FIG. 8, the process includes the following steps:
  • Step S801 The SCC AS on the called side receives the call request, and the call request is forwarded to the UE.
  • Step S802 The called UE sends a 183 message to the remote end.
  • Step S803 The source RAN finds that the UE signal quality is not good, and needs to switch, and sends a handover request to the MME/SGSN.
  • Step S805 The MME/SGSN sends a PS to CS handover request to the eMSC.
  • Step S806 The eMSC reserves resources to the target radio access network (Target RAN) RNC/BSS; this process may be that the eMSC determines the target Serving MSC, which is completed by the Serving MSC.
  • Target RAN target radio access network
  • Step S807 The eMSC sends a handover request response to the MME, indicating that the handover can be performed.
  • Step S808 The MME sends a handover command to the UE through the source radio access network.
  • Step S809 The UE switches to the CS domain, and finds that the pre-alerting switch is not supported.
  • Step S810 The UE sends a Disconnect message, and the message arrives at the eMSC through the Serving MSC. It should be noted that this step is optional. If the eMSC does not receive the message, the eMSC is optional and sends a disconnect to the UE through the S-MSC.
  • Step S811 The eMSC initiates a session switching request to the anchor SCC AS of the session.
  • the eMSC is optional, and carries an indication supporting the terminating Pre-alerting SRVCC;
  • Step S811 and step S807 are parallel, and there is no order relationship.
  • Step S812 The SCC AS updates the remote end
  • Step S813 The SCC AS notifies the eMSC that the UE is currently in the pre-alerting state
  • Step S814 The eMSC sends a Setup to the UE.
  • the message arrives at the UE through the Serving MSC;
  • Step S815 When the user answers, the UE sends a Connect message. The message arrives at the eMSC through the Serving MSC.
  • eMSC and S-MSC can be the same MSC.
  • FIG. 9 is a second flowchart of a terminating side pre-alerting SRVCC according to an embodiment of the present invention. As shown in FIG. 9, the process includes the following steps:
  • Step S901 When the called party user is in the Pre-alerting state, SRVCC switching occurs. The steps are the same as steps S801-808 in Figure 8 above;
  • Step S902 The eMSC initiates a session switching request to the anchor SCC AS of the session.
  • the eMSC is optional, and carries an indication supporting the terminating Pre-alerting SRVCC;
  • Step S903 The SCC AS updates the remote end.
  • Step S904 The SCC AS notifies the eMSC that the UE is currently in the pre-alerting state
  • Step S905 The UE switches to the CS domain, and finds that the pre-alerting switch is not supported.
  • step S902 there is no order relationship between step S902 and step S905.
  • Step S906 The UE sends a Disconnect message, and the message arrives at the eMSC through the Serving MSC. It should be noted that this step is optional. If the eMSC does not receive the message, the eMSC is optional and sends a disconnect to the UE through the S-MSC.
  • Step S907 The eMSC releases the session with the UE;
  • Step S908 The eMSC sends a Routing Query Request (SRI) to the HLR.
  • SRI Routing Query Request
  • Step S609 The HLR queries the Serving MSC for the Proxy Roaming Number (PRN), and the MSC returns the MS Routing Number (MSRN) to the HLR.
  • PRN Proxy Roaming Number
  • MSRN MS Routing Number
  • Step S910 The HLR returns a routing number to the eMSC.
  • Step S911 The eMSC sends an IAM message to the Serving MSC.
  • Step S912 The Serving MSC sends a Setup message to the UE.
  • Step S913 When the user answers, the UE sends a Connect message to the Serving MSC.
  • FIG. 10 is a flowchart 3 of a terminating side pre-alerting SRVCC according to an embodiment of the present invention. As shown in FIG. 10, the process includes the following steps. In this embodiment, the eMSC directly requests a roaming number from the Serving MSC.
  • Step S1001 When the called party user is in the Pre-alerting state, SRVCC switching occurs. The steps are the same as steps S801-808 of FIG. 8;
  • Step S1002 The eMSC initiates a session switching request to the anchor SCC AS of the session.
  • the eMSC is optional, and carries an indication supporting the terminating Pre-alerting SRVCC;
  • Step S1003 The SCC AS updates the remote end
  • Step S1004 The SCC AS notifies the eMSC that the UE is currently in the pre-alerting state
  • Step S1005 The UE switches to the CS domain, and finds that the pre-alerting switch is not supported.
  • step S1002 there is no order relationship between step S1002 and step S1005.
  • Step S1006 The UE sends a Disconnect message, and the message arrives at the eMSC through the Serving MSC. It should be noted that this step is optional. If the eMSC does not receive the message, the eMSC is optional and sends a disconnect to the UE through the S-MSC.
  • Step S1008 The eMSC releases the session with the UE;
  • Step S1009 The eMSC queries the Serving MSC for the roaming number (Provide Roaming Number, PRN for short), and the Serving MSC returns the MS Routing Number (MSRN) to the eMSC.
  • the Serving MSC queries the Serving MSC for the roaming number (Provide Roaming Number, PRN for short), and the Serving MSC returns the MS Routing Number (MSRN) to the eMSC.
  • MSRN MS Routing Number
  • Step S1010 The eMSC sends an IAM message to the Serving MSC.
  • Step S1011 The Serving MSC sends a Setup message to the UE.
  • Step S1012 When the user answers, the UE sends a Connect message to the Serving MSC.
  • FIG. 11 is a flowchart of a UE performing a joint attach procedure on the EPC according to an embodiment of the present invention, as shown in FIG. After the joint registration update, the MME replaces the MSC information registered by the user.
  • Step S1101 The UE initiates an attach request to the MME, requesting to perform a combined attach;
  • Step S1102 The MME initiates an attach procedure to the EPC.
  • Step S1103 The MME initiates a location update request (Location Area Update, LAU for short) to the MSC;
  • Step S1104 The MSC establishes an SGs interface with the MME.
  • Step S1105 The MSC and the HSS/HLR complete the Location Update process of the CS domain, and obtain user subscription data.
  • Step S1106 The MSC sends an LAU accept response to the MME.
  • the MME will save the information of the MSC.
  • the MME selects the saved MSC as the eMSC during the handover process, or sends the saved MSC information to the eMSC in the handover request.
  • the former has no effect on the above process, which is equivalent to the integration of eMSC and Serving MSC.
  • the eMSC can select the received MSC as the Serving MSC.
  • the following is an example.
  • FIG. 12 is a flowchart of an optimization manner of the embodiment shown in FIG. 8 according to an embodiment of the present invention. As shown in FIG. 12, the process includes the following steps:
  • Step S1200 The UE performs a joint attach update on the EPC, and the MME saves the registered MSC2 information.
  • Step S1201 The SCC AS on the called side receives the call request, and the call request is forwarded to the UE.
  • Step S1202 The called UE sends a 183 message to the remote end.
  • Step S1203 The source RAN finds that the UE signal quality is not good, and needs to switch, and sends a handover request to the MME/SGSN.
  • Step S1205 The MME/SGSN sends a PS to CS handover request to the eMSC, where the MSC2 information is carried;
  • Step S1206 The eMSC reserves resources to the target radio access network (Target RAN) RNC/BSS; this process may be that the eMSC determines that the MSC2 is the target Serving MSC and is completed by the Serving MSC.
  • Target RAN target radio access network
  • Step S1207 The eMSC sends a handover request response to the MME, indicating that the handover can be performed.
  • Step S1208 The MME sends a handover command to the UE through the source radio access network.
  • Step S1209 The UE switches to the CS domain, and finds that the pre-alerting switch is not supported.
  • Step S1210 The UE sends a Disconnect message, and the message arrives at the eMSC through the Serving MSC. It should be noted that this step is optional. If the eMSC does not receive the message, the eMSC is optional and sends a disconnect to the UE through the S-MSC.
  • Step S1211 The eMSC initiates a session switching request to the anchor SCC AS of the session.
  • the eMSC is optional, and carries an indication supporting the terminating Pre-alerting SRVCC;
  • Steps S1211 and 1207 can be parallel, with no order relationship.
  • Step S1212 The SCC AS updates the remote end
  • Step S1213 The SCC AS notifies the eMSC that the UE is currently in the pre-alerting state
  • Step S1214 The eMSC sends a Setup to the UE.
  • the message arrives at the UE through the Serving MSC;
  • Step S1215 When the user answers, the UE sends a Connect message. The message arrives at the eMSC through the Serving MSC.
  • eMSC and S-MSC can be the same MSC.
  • the embodiment shown in FIG. 10 can also adopt this optimization mode, and the MME saves the registered MSC information when the joint is attached.
  • the MME saves the registered MSC information when the joint is attached.
  • the saved MSC information is carried.
  • the eMSC reserves resources to the target radio access network (Target RAN) RNC/BSS, the eMSC uses the received MSC as the Serving MSC, and the remaining steps are the same.
  • FIG. 13 is a flowchart of a case where an SRVCC occurs in a UE in an alerting state and the UE does not support aerating SRVCC according to the embodiment shown in FIG. 8 . As shown in FIG. 13 , the process includes the following steps:
  • Step S1300 Optionally, the UE performs joint attach update on the EPC, and the MME saves the registered MSC2 information.
  • Step S1301 The SCC AS on the called side receives the call request, and the call request is forwarded to the UE.
  • Step S1302 The called UE sends a 180 ringing message to the remote end (the intermediate step unrelated to the embodiment is omitted);
  • Step S1303 The source RAN finds that the UE signal quality is not good, and needs to switch, and sends a handover request to the MME/SGSN.
  • Step S1305 The MME/SGSN sends a PS to CS handover request to the eMSC.
  • the MME saves the MSC2 information in step 1000, the MSC2 information is carried in the message.
  • Step S1306 The eMSC reserves resources to the target radio access network (Target RAN) RNC/BSS.
  • Target RAN target radio access network
  • the process may be that the eMSC determines that the MSC2 is the target Serving MSC and is completed by the Serving MSC.
  • Step S1307 The eMSC sends a handover request response to the MME, indicating that the handover can be performed.
  • Step S1308 The MME sends a handover command to the UE through the source radio access network.
  • Step S1309 The UE switches to the CS domain, and finds that the alerting switch is not supported.
  • Step S1310 The UE sends a Disconnect message, and the message arrives at the eMSC through the Serving MSC. It should be noted that this step is optional. If the eMSC does not receive the message, the eMSC is optional and sends a disconnect to the UE through the S-MSC.
  • Step S1311 The eMSC initiates a session switching request to the anchor SCC AS of the session.
  • the eMSC is optional, and carries an indication supporting the terminal call aerting SRVCC/Pre-alerting SRVCC;
  • Step S1311 and step S1307 are parallel, and there is no order relationship.
  • Step S1312 The SCC AS updates the remote end
  • Step S1313 The SCC AS notifies the eMSC that the UE is currently in the alerting state
  • Step S1314 The eMSC sends a Setup to the UE.
  • the message arrives at the UE through the Serving MSC;
  • Step S1315 When the user answers, the UE sends a Connect message. The message arrives at the eMSC through the Serving MSC.
  • eMSC and S-MSC can be the same MSC.
  • FIG. 14 is a flowchart corresponding to the embodiment shown in FIG. 9 when the UE is in the aerting state, the SRVCC occurs, and the UE does not support the aerting SRVCC. As shown in FIG. 14, the process includes the following steps. Steps:
  • Step S1400 Optionally, the UE performs a joint attach update on the EPC, and the MME saves the registered MSC2 information.
  • Step S1401 The SCC AS on the called side receives the call request, and the call request is forwarded to the UE.
  • Step S1402 The called UE sends a 180 ringing message to the remote end (the intermediate step unrelated to this patent is omitted);
  • Step S1403 The source RAN finds that the UE signal quality is not good, and needs to switch, and sends a handover request to the MME/SGSN.
  • Step S1405 The MME/SGSN sends a PS to CS handover request to the eMSC.
  • the MME saves the MSC2 information in step S1400, the MSC2 information is carried in the message.
  • Step S1406 The eMSC reserves resources to the target radio access network (Target RAN) RNC/BSS.
  • Target RAN target radio access network
  • the process may be that the eMSC determines that the MSC2 is the target Serving MSC and is completed by the Serving MSC.
  • Step S1407 The eMSC sends a handover request response to the MME, indicating that the handover can be performed.
  • Step S1408 The MME sends a handover command to the UE through the source radio access network.
  • Step S1409 The UE switches to the CS domain, and finds that the alerting switch is not supported.
  • Step S1410 The UE sends a Disconnect message, and the message arrives at the eMSC through the Serving MSC. It should be noted that this step is optional. If the eMSC does not receive the message, the eMSC is optional and sends a disconnect to the UE through the S-MSC.
  • Step S1411 The eMSC initiates a session switching request to the anchor SCC AS of the session.
  • the eMSC is optional, and carries an indication supporting the terminal call aerting SRVCC/Pre-alerting SRVCC;
  • Steps S1411 and S1407 are parallel, with no order relationship.
  • Step S1412 The SCC AS updates the remote end
  • Step S1413 The SCC AS notifies the eMSC that the UE is currently in the alerting state
  • Step S1414 The eMSC sends a Routing Query Request (SRI) to the HLR.
  • SRI Routing Query Request
  • Step S1415 The HLR queries the Serving MSC for the Roaming Number (PRN), and the Serving MSC returns the MS Routing Number (MSRN) to the HLR.
  • PRN Roaming Number
  • MSRN MS Routing Number
  • Step S1416 The HLR returns a routing number to the eMSC.
  • Step S1417 The eMSC sends an IAM message to the Serving MSC.
  • Step S1418 The Serving MSC sends a Setup message to the UE.
  • Step S1419 When the user answers, the UE sends a Connect message to the Serving MSC.
  • eMSC and S-MSC can be the same MSC. At this time, it becomes the scheme of FIG.
  • the preferred embodiment in the case that the UE is in the alerting state and the UE does not support the aerting SRVCC is similar to that in FIG. 14. The difference is that after the step 1413, the eMSC directly queries the Serving MSC for routing. After receiving the routing number, the number initiates an IAM call request to the Serving MSC. After receiving the IAM message, the Serving MSC initiates a Setup to the UE.
  • eMSC and S-MSC can be the same MSC. At this time, it becomes the scheme of FIG.
  • the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course, by hardware, but in many cases, the former is A better implementation.
  • the technical solution of the embodiments of the present invention may be embodied in the form of a software product in essence or in the form of a software product stored in a storage medium (such as ROM/RAM, magnetic).
  • the disc, the disc includes a number of instructions for causing a terminal device (which may be a cell phone, a computer, a server, or a network device, etc.) to perform the methods of various embodiments of the present invention.
  • a processing device for inter-network handover is also provided.
  • the device is used to implement the foregoing embodiments and preferred embodiments, and details are not described herein.
  • the term "module” may implement a combination of software and/or hardware of a predetermined function.
  • the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.
  • FIG. 15 is a structural block diagram of a processing apparatus 1 for inter-network handover according to an embodiment of the present invention. As shown in FIG. 15, the apparatus includes: a first determining module 152 and a processing module 154, which will be described below.
  • the first determining module 152 is configured to determine that the single mode service continuity SRVCC handover fails when the called terminal is in the ringing state or the pre-ringing state; the processing module 154 is connected to the first determining module 152, and is configured to continue to perform the switching. After the visit to the network for the final call processing.
  • FIG. 16 is a structural block diagram of a first determining module 152 in a processing device for inter-network handover according to an embodiment of the present invention.
  • the first determining module 152 includes: a first receiving unit 162 and a first determining unit 164.
  • the first determining module 152 will be described below.
  • the first receiving unit 162 is configured to receive the terminal status message sent by the service consistency and continuity server SCC AS, and/or receive the first connection failure message sent by the called terminal; the first determining unit 164 is connected to the foregoing The first receiving unit 162 is configured to determine that the SRVCC handover fails according to the terminal status message and/or the first connection failure message.
  • FIG. 17 is a block diagram of a preferred structure of a processing device for inter-network handover according to an embodiment of the present invention. As shown in FIG. 17, the device includes: a second determining module 172, in addition to the structure shown in FIG. The second determination module 172 is described.
  • the second determining module 172 is connected to the first determining module 152, and is configured to determine a target serving mobile switching center S-MSC for terminating call processing after the network switching.
  • FIG. 18 is a structural block diagram of a second determining module 172 in a processing device for inter-network handover according to an embodiment of the present invention.
  • the second determining module 172 includes: a second receiving unit 182 and a second determining unit 184.
  • the second determining module 172 will be described below.
  • the second receiving unit 182 is configured to receive a first network handover request message sent by the mobility management entity MME and/or the GPRS serving node SGSN for requesting to switch the network, where the first network handover request message carries a identifier for identifying the called The identifier information of the MSC registered by the terminal; the second determining unit 184 is connected to the second receiving unit 182, and is configured to determine that the MSC identified by the identifier information is the target S-MSC.
  • FIG. 19 is a structural block diagram of a processing module 154 in a processing device for inter-network handover according to an embodiment of the present invention.
  • the processing module 154 includes at least one of the following: a first sending unit 192 and a second sending unit 194.
  • the processing module 154 will be described below.
  • the first sending unit 192 is configured to send, by using the determined target S-MSC, a first session establishment request message for establishing a session to the called terminal; and/or, the second sending unit 194 is configured to be based on the home location register HLR.
  • the terminal S-MSC queries the terminal roaming number, or directly queries the terminal S-MSC for the terminal roaming number; and sends a second session establishment request message for establishing the session to the called terminal according to the queried terminal roaming number.
  • FIG. 20 is a block diagram of a preferred structure of a processing device for inter-network handover according to an embodiment of the present invention. As shown in FIG. 20, the device includes: a first sending module 202, The first transmitting module 202 is described.
  • the first sending module 202 is connected to the first determining module 152 and the processing module 154, and is configured to send a second connection failure message to the called terminal.
  • FIG. 21 is a schematic structural diagram of an enhanced mobile switching center eMSC according to an embodiment of the present invention. As shown in FIG. 21, the eMSC 212 includes the inter-network switching processing apparatus 214 of any of the above.
  • the eMSC and the serving mobile switching center S-MSC may be the same MSC.
  • FIG. 22 is a structural block diagram of a processing apparatus 2 for inter-network handover according to an embodiment of the present invention. As shown in FIG. 22, the apparatus includes: a receiving module 222 and a second transmitting module 224, which are described below.
  • the receiving module 222 is configured to receive a second network switching request message sent by the enhanced mobile switching center eMSC for requesting network switching, and the second sending module 224 is connected to the receiving module 222, and is configured to perform the second network switching request message according to the second network switching request message. Sending a terminal status message of the called terminal to the eMSC, where the terminal status message is used by the eMSC to continue the terminal call processing based on the visited visited network.
  • the foregoing second network handover request message is further used to determine that the eMSC supports the single mode service continuity SRVCC handover when the eMSC supports the ringing state or the pre-ringing state.
  • FIG. 23 is a schematic structural diagram of a service consistency and continuity server SCC AS according to an embodiment of the present invention. As shown in FIG. 23, the SCC AS 232 includes the inter-network handover processing apparatus 234 of any of the above.
  • FIG. 24 is a structural block diagram of a processing apparatus 3 for inter-network handover according to an embodiment of the present invention. As shown in FIG. The device includes a storage module 242 and a third transmitting module 244, which will be described below.
  • the storage module 242 is configured to store the mobile switching center MSC registered by the called terminal.
  • the third sending module 244 is connected to the storage module 242 and configured to send to the enhanced mobile switching center eMSC a third network for requesting network switching.
  • a handover request message where the third network handover request message carries identifier information for identifying the MSC registered by the called terminal.
  • the identifier information is used by the eMSC to determine the target serving mobile switching center S for the terminal call processing after the network handover before the single mode service continuity SRVCC handover fails when the called terminal is in the ringing state or the pre-ringing state. - MSC.
  • the MME 25 is a structural block diagram of a mobility management entity MME according to an embodiment of the present invention. As shown in FIG. 25, the MME 252 includes the above-described inter-network handover processing device 254.
  • FIG. 26 is a structural block diagram of a GPRS serving node SGSN according to an embodiment of the present invention. As shown in FIG. 26, the SGSN 262 includes the above-described inter-network handover processing apparatus 254.
  • each of the above modules may be implemented by software or hardware.
  • the foregoing may be implemented by, but not limited to, the foregoing modules are all located in the same processor; or, the modules are located in multiple In the processor.
  • Embodiments of the present invention also provide a storage medium.
  • the foregoing storage medium may be configured to store program code for performing the following steps:
  • the storage medium is further arranged to store program code for performing the following steps:
  • the SRVCC handover failure includes:
  • the storage medium is further arranged to store program code for performing the following steps:
  • the terminal status message indicates that the called terminal is in a ringing state or a pre-ringing state, and/or is used to determine that the called terminal is in a ringing state or a pre-ringing state, and does not support SRVCC switching.
  • the storage medium is further arranged to store program code for performing the following steps:
  • the method further includes:
  • the storage medium is further arranged to store program code for performing the following steps:
  • the target S-MSC for determining the terminal call processing after the network handover includes:
  • the storage medium is further arranged to store program code for performing the following steps:
  • the terminal call processing continued to be based on the switched visited network includes at least one of the following:
  • S1 sending, by the determined target S-MSC, a first session establishment request message for establishing a session to the called terminal; and/or, querying the terminal roaming number from the target S-MSC according to the home location register HLR, or directly from the target
  • the S-MSC queries the terminal roaming number; and sends a second session establishment request message for establishing a session to the called terminal according to the queried terminal roaming number.
  • the storage medium is further arranged to store program code for performing the following steps:
  • the first session establishment request message is a Setup message, or the second session establishment request message is an initial address message IAM message.
  • the storage medium is further arranged to store program code for performing the following steps:
  • the method further includes:
  • Embodiments of the present invention also provide a storage medium.
  • the foregoing storage medium may be configured to store program code for performing the following steps:
  • the terminal status message of the called terminal is sent to the eMSC according to the second network handover request message, where the terminal status message is used by the eMSC to continue the terminal call processing based on the visited visited network.
  • the storage medium is further arranged to store program code for performing the following steps:
  • the second network handover request message is further used to indicate that the eMSC supports the single mode service continuity SRVCC handover when the ringing state or the pre-ringing state is supported; or the terminal status message indicates that the called terminal is ringing.
  • the state or pre-ringing state, and/or for determining that the called terminal is in a ringing state or a pre-ringing state, does not support SRVCC switching.
  • Embodiments of the present invention also provide a storage medium.
  • the foregoing storage medium may be configured to store program code for performing the following steps:
  • the third network handover request message carries identifier information for identifying the MSC registered by the called terminal.
  • the storage medium is further arranged to store program code for performing the following steps:
  • the identifier information is used by the eMSC to determine, after the single-mode service continuity SRVCC handover fails, the target service mobile switching center S-MSC after the network handover is performed, before the called terminal is in the ringing state or the pre-ringing state. .
  • the foregoing storage medium may include, but not limited to, a USB flash drive, a Read-Only Memory (ROM), a Random Access Memory (RAM), a mobile hard disk, and a magnetic memory.
  • ROM Read-Only Memory
  • RAM Random Access Memory
  • a mobile hard disk e.g., a hard disk
  • magnetic memory e.g., a hard disk
  • the processor performs, according to the stored program code in the storage medium, that when the called terminal is in a ringing state or a pre-ringing state, the single-mode service continuity SRVCC handover fails; After the visit to the network for the final call processing.
  • the processor performs, according to the stored program code in the storage medium, when determining that the called terminal is in a ringing state or a pre-ringing state, the SRVCC handover failure includes: receiving service consistency and continuity.
  • the processor executes according to the stored program code in the storage medium: the terminal status message indicates that the called terminal is in a ringing state or a pre-ringing state, and/or is used to determine The identification information of the SRVCC handover is not supported when the called terminal is in the ringing state or the pre-ringing state.
  • the processor performs, according to the stored program code in the storage medium, before determining that the called terminal is in a ringing state or a pre-ringing state, before the SRVCC switching fails, the method further includes: determining a network switching.
  • the target serving mobile switching center S-MSC is then used for terminating call processing.
  • the processor performs, according to the stored program code in the storage medium, determining that the target S-MSC for the terminal call processing after the network handover comprises: receiving the mobility management entity MME and/or the GPRS service node.
  • the processor executes according to the stored program code in the storage medium: continuing to perform the terminal call processing based on the switched visited network includes at least one of: passing the determined target S-MSC, Calling the terminal to send a first session establishment request message for establishing a session; and/or, querying the terminal roaming number from the target S-MSC according to the home location register HLR, or directly querying the terminal roaming number from the target S-MSC; The roaming number sends a second session establishment request message for establishing a session to the called terminal.
  • the processor executes, according to the stored program code in the storage medium, that the first session establishment request message is a Setup message, or the second session establishment request message is an initial address message IAM. Message.
  • the processor performs, according to the stored program code in the storage medium, before continuing to perform the terminal call processing based on the visited visited network, further comprising: sending a second connection failure message to the called terminal. .
  • the processor performs, according to the stored program code in the storage medium, receiving a second network handover request message sent by the enhanced mobile switching center eMSC for requesting network handover; switching according to the second network
  • the request message sends a terminal status message of the called terminal to the eMSC, where the terminal status message is used by the eMSC to continue the terminal call processing based on the visited visited network.
  • the processor is executed according to the stored program code in the storage medium: the second network switch request message is further used to indicate that the eMSC supports the ring mode or the pre-ring state, and the single mode service is continuous.
  • the processor executes according to the stored program code in the storage medium:
  • a mobile switching center MSC that is registered by the called terminal; a third network switching request message that is sent to the enhanced mobile switching center eMSC for requesting network switching, where the third network switching request message carries a identifier for identifying the called terminal.
  • Identification information of the MSC the identifier information is used by the eMSC to determine the target service mobile exchange for the terminal call processing after the network switchover before the single mode service continuity SRVCC handover fails when the called terminal is in the ringing state or the pre-ringing state.
  • Center S-MSC Center S-MSC.
  • 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 a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
  • the steps shown or described are performed, 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 single-mode service continuity SRVCC handover fails; and the terminal call processing is continued based on the visited visited network.
  • the SRVCC switching is performed, and the switching failure occurs, thereby achieving the SRVCC switching when the terminal call does not support the ringing state or the pre-ringing state. In this case, the effect of the call can also be successfully established.

Abstract

本发明提供了一种网络间切换的方法、装置、eMSC及SCC AS，其中，该方法包括：确定被叫终端处于振铃状态或振铃前状态时，单模业务连续性SRVCC切换失败；继续基于切换后的拜访网络进行终呼处理，通过本发明，解决了相关技术中被叫侧处于振铃态或振铃前状态时，进行SRVCC切换，会发生切换失败的问题，进而达到了在终呼不支持振铃态或振铃前状态时SRVCC切换的情况下，也能够成功建立呼叫的效果。

Description

网络间切换的方法、装置、eMSC及SCC AS 技术领域
本发明涉及通信领域，具体而言，涉及一种网络间切换的方法、装置、eMSC及SCC AS。
背景技术
网络互联协议(Internet Protocol，简称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)三种类型。
业务层是由一系列应用服务器(Application Server，简称AS)组成，能提供具体业务服务，AS可以是独立的实体，也可以存在于S-CSCF中。
控制层(S-CSCF)根据用户的签约信息控制业务触发，调用AS上的业务，实现业务功能。
会话中的端到端设备称为用户设备(User Equipment，简称UE)，负责与使用者的交互，有的UE具有多种接入网络的方式，包括通过3GPP的分组交换(Packet Switch，简称PS)域接入网络，通过其他非3GPP的PS域接入网络，甚至可以通过电路交换(Circuit Switch，简称CS)域接入网络等。
对于具有多种接入方式的UE而言，如果该UE某时刻只能使用一种接入方式，则其在一种接入方式下正在执行某项业务，比如，通话，当UE移动到其他地方而需要改变其使用的接入方式时，UE和网络能提供某种方式使UE正在执行的业务不被中断，这样的能力我们称之为单模终端业务连续性，简称单模业务连续性(Single Radio Voice Call Continuity，简称SRVCC)。3GPP定义了SRVCC的架构和流程。为了减少切换过程中的延迟，3GPP随后定义了增强型SRVCC(enhanced SRVCC，简称eSRVCC)。
由于本专利要解决的问题同时存在于SRVCC和eSRVCC，并且本专利的解决方案对于SRVCC和eSRVCC是一样的。为简便期间，除了特殊说明之外，下文所述的SRVCC同时指上述的SRVCC和eSRVCC。
图1是相关技术中eSRVCC的架构示意图，如图1所示，用户设备UE101开始通过源无线接入网111(Source Radio Aceess Network，简称Source RAN)接入PS接入网103。该源无线接入网可以是通用移动通讯系统(Universal Mobile Telecommunications System，简称UMTS)，也可以是演进的UMTS无线接入网(Evolved UMTS Terrestrial Radio Access Network，简称E-UTRAN)。PS接入网的关键实体是移动性管理实体(Mobility Management Entity，简称MME)或GPRS服务节点(Serving GPRS Support Node，简称SGSN)。
UE101在Source RAN接入时，IMS VoIP会话会锚定在业务一致与连续性服务器(Service Centralization and Continuity Application Server，简称SCC AS)。会话通过IMS网络连接远端。
当Source RAN的信号不好时，会触发SRVCC切换。Source RAN会配置无线信号阈值，当低于该阈值时，触发SRVCC，UE切换到CS接入网110，连接到移动交换中心(Mobile Switching Center，简称MSC109)，MSC再连向锚点SCC AS。为了灵活部署，MSC109可以由两个MSC组成，增强型MSC(enhanced MSC for SRVCC)和Serving MSC。eMSC作为锚点，向IMS网络发起切换。eMSC通过Serving MSC在CS接入网预留资源，并将UE101通过CS接入网接入Serving MSC。当只有一个MSC时，MSC同时是eMSC和Serving MSC。
Serving MSC上同时还有拜访位置寄存器(Visitor Location Register，简称VLR)，在以下表述中统称Serving MSC，不在区别这两者。
当有eSRVCC时，会话同时还会锚定在接入转移控制功能(Access Transfer Control Function，简称ATCF)和接入转移网关105(Access Transfer Gateway，简称ATGW)，UE到SCC AS的会话，由UE到ATCF，和ATCF到SCC AS的两段会话组成。在SRVCC切换后，UE到SCC AS的会话，变为UE---Serving MSC---eMSC---ATCF/ATGW---SCC-AS组成。
归属签约服务器(Home Subscriber Server，简称HSS)，归属位置寄存器(Home Location Register，简称HLR)保存了用户的签约信息。描述为HSS/HLR，或者HSS，或者HLR，下文并不区别。
SRVCC不仅支持通话中会话SRVCC，也支持振铃态(alerting)会话和主叫侧的振铃前状态(pre-alerting)会话的切换。图2是相关技术中终呼侧SRVCC，altering SRVCC和pre-alerting SRVCC的时间定义示意图，如图2所示，
所谓通话中会话SRVCC是指，UE已经和远端接通了电话，正在通话中，这个是否发生了SRVCC切换。
Alerting SRVCC是指UE和远端尚未接通电话，UE在主叫侧能听到振铃音，如果UE在被叫侧，则开始振铃。
Pre-laerting SRVCC是指UE和远端尚未接通电话，主叫侧尚不能听到振铃音，被叫侧也没有开始振铃。
图3是相关技术中终呼侧，振铃态会话的单模业务连续性切换的流程图，如图3所示，该流程包括如下步骤：
步骤S301：被叫侧的SCC AS收到呼叫请求，呼叫请求转发给UE；
步骤S302：被叫UE向远端发送180振铃消息(中间步骤省略)；
步骤S303：Source RAN发现UE信号质量不好需要切换后，发切换请求给MME/SGSN；
步骤S304：MME/SGSN发现UE有QCI＝1的bearer承载；
步骤S305：MME/SGSN向eMSC发送PS to CS切换请求；
步骤S306：eMSC向目标无线接入网(Target RAN)RNC/BSS预留资源；这个过程可能是eMSC确定目标Serving MSC，通过Serving MSC完成。
步骤S307：eMSC向MME发送切换请求响应，表示可以切换；
步骤S308：MME通过源无线接入网向UE发送切换命令；
步骤S308a：UE切换到CS接入网，并且继续振铃；
步骤S309：MSC向会话的锚点SCC AS发起会话切换请求；
注：步骤S307和步骤S309可以是并行的。
步骤S309a：SCC AS更新远端，此时呼叫还在振铃态；
步骤S310：SCC AS通知eMSC，UE目前在振铃态；
步骤S311：用户摘机接电话；
步骤S312：UE向eMSC发Connect消息；
步骤S312b：eMCS上，会话变成激活态；
步骤S313：eMSC向SCC AS发送呼叫状态通知(call notification)，用户接通电话；
步骤S314：SCC AS更新远端。
如上述相关技术中，当会话状态是pre-alerting时，只支持主叫侧的切换。对于被叫侧，无论网络还是终端都不支持pre-alerting时的SRVCC切换，如果在被叫UE在pre-alerting态发生SRVCC切换，会发生切换失败。
此外，如果被叫终端本身不支持alerting SRVCC状态切换(仅支持通话中SRVCC切换)，即使网络支持alerting SRVCC，切换也会失败。目前SRVCC切换后，CS会话结束，UE会返回到LTE网络。这时候再次呼叫该UE，仍旧会发生切换失败，在某些情形下，导致用户无法成功的收到呼叫。
图4是相关技术中终呼UE在pre-alerting、或者alerting状态时，切换失败的流程图，如图4所示，用户陷入了无法收到呼叫的情况。
步骤S401：被叫侧的SCC AS收到呼叫请求，呼叫请求转发给UE；
步骤S402：被叫UE向远端发送183消息。(交换会话的媒体信息)；
步骤S403：在Source PS接入网，生成QCI＝1的bearer；
步骤S404：Source RAN发现UE信号质量不好需要切换后，发切换请求。此处步骤同图3的步骤S303～308；
步骤S405：UE切换到CS域后，发起在pre-alerting状态，认为切换失败。
步骤S406：UE发Disconnect消息给eMSC；
步骤S407：eMSC在步骤S404中，给MME发切换应答的同时，向SCC AS发起session transfer。由于SCC AS不支持pre-alerting切换，SCC会通知eMSC切换失败。
步骤S408：整个切换失败；当被叫UE本身不支持alerting时，过程和上图类似。虽然步骤S407会成功，但是UE在步骤S406发送Disconnect后，eMSC向SCC AS释放当年的呼叫。
步骤S409：UE回到Source RAN
步骤S410：当UE没有移动，信号覆盖情况没有发生变化。此时，再次收到呼叫，会重复步骤S401～409。
从上述的相关技术中可以看出，被叫用户终端不支持pre-alerting、或者alerting状态的SRVCC切换。一个办法是升级UE去支持这些状态的切换。然而，上述的升级终端方案是非常困难的，即使新的终端支持这些状态的切换，已经生产的UE依旧存在这个问题。另一个办法是MME在pre-alerting/alerting下，对于被叫不发起切换，然而MME不理解IMS层的状态，无法限制这种切换的发生。
因此，在相关技术中，被叫侧处于振铃态或振铃前状态时，进行SRVCC切换，会发生切换失败的问题。
发明内容
本发明实施例提供了一种网络间切换的处理方法、装置、eMSC及SCC AS，以至少解决相关技术中被叫侧处于振铃态或振铃前状态时，进行SRVCC切换，会发生切换失败的问题。
根据本发明实施例的一个方面，提供了一种网络间切换的处理方法，包括：确定被叫终端处于振铃状态或振铃前状态时，单模业务连续性SRVCC切换失败；继续基于切换后的拜访网络进行终呼处理。
优选地，确定所述被叫终端处于振铃状态或振铃前状态时，所述SRVCC切换失败包括：接收到业务一致与连续性服务器SCC AS发送的终端状态消息，和/或，接收到所述被叫终端发送的第一连接失败消息；依据所述终端状态消息和/或所述第一连接失败消息，确定所述SRVCC切换失败。
优选地，所述终端状态消息指示出所述被叫终端处于振铃状态或振铃前状态，和/或用于确定所述被叫终端处于振铃状态或振铃前状态时不支持SRVCC切换。
优选地，在确定所述被叫终端处于振铃状态或振铃前状态时，所述SRVCC切换失败之前，还包括：确定网络切换后用于所述终呼处理的目标服务移动交换中心S-MSC。
优选地，确定网络切换后用于所述终呼处理的所述目标S-MSC包括：接收移动管理实体MME和/或GPRS服务节点SGSN发送的用于请求切换网络的第一网络切换请求消息，其中，所述第一网络切换请求消息中携带有用于标识所述被叫终端注册的MSC的标识信息；确定所述标识信息标识的所述MSC为所述目标S-MSC。
优选地，继续基于切换后的所述拜访网络进行终呼处理包括以下至少之一：通过确定的所述目标S-MSC，向所述被叫终端发送用于建立会话的第一会话建立请求消息；和/或，依据归属位置寄存器HLR从所述目标S-MSC查询终端漫游号码，或者直接从所述目标S-MSC查询所述终端漫游号码；依据查询的所述终端漫游号码向所述被叫终端发送用于建立会话的第二会话建立请求消息。
优选地，所述第一会话建立请求消息为Setup消息，或者，所述第二会话建立请求消息为初始地址消息IAM消息。
优选地，在继续基于切换后的所述拜访网络进行终呼处理之前，还包括：向所述被叫终端发送第二连接失败消息。
根据本发明实施例的另一方面，提供了一种网络间切换的处理方法，包括：接收增强型移动交换中心eMSC发送的用于请求网络切换的第二网络切换请求消息；依据所述第二网络切换请求消息，向所述eMSC发送被叫终端的终端状态消息，其中，所述终端状态消息用于所述eMSC继续基于切换后的所述拜访网络进行终呼处理。
优选地，所述第二网络切换请求消息还用于指示所述eMSC支持处于振铃状态或振铃前状态时，单模业务连续性SRVCC切换；或者，所述终端状态消息指示出所述被叫终端处于振铃状态或振铃前状态，和/或用于确定所述被叫终端处于振铃状态或振铃前状态时不支持SRVCC切换。
根据本发明实施例的一方面，提供了一种网络间切换的处理方法，包括：存储被叫终端注册的移动交换中心MSC；向增强型移动交换中心eMSC发送的用于请求网络切换的第三网络切换请求消息，其中，所述第三网络切换请求消息中携带有用于标识所述被叫终端注册的所述MSC的标识信息。
优选地，所述标识信息用于所述eMSC在所述被叫终端处于振铃状态或振铃前状态时，单模业务连续性SRVCC切换失败之前，确定网络切换后用于终呼处理的目标服务移动交换中心S-MSC。
根据本发明实施例的一方面，提供了一种网络间切换的处理装置，包括：第一确定模块，设置为确定被叫终端处于振铃状态或振铃前状态时，单模业务连续性SRVCC切换失败；处理模块，设置为继续基于切换后的拜访网络进行终呼处理。
优选地，所述第一确定模块包括：第一接收单元，设置为接收到业务一致与连续性服务器SCC AS发送的终端状态消息，和/或，接收到所述被叫终端发送的第一连接失败消息；第一确定单元，设置为依据所述终端状态消息和/或所述第一连接失败消息，确定所述SRVCC切换失败。
优选地，该装置还包括：第二确定模块，设置为确定网络切换后用于所述终呼处理的目标服务移动交换中心S-MSC。
优选地，所述第二确定模块包括：第二接收单元，设置为接收移动管理实体MME和/或GPRS服务节点SGSN发送的用于请求切换网络的第一网络切换请求消息，其中，所述第一网络切换请求消息中携带有用于标识所述被叫终端注册的MSC的标识信息；第二确定单元，设置为确定所述标识信息标识的所述MSC为所述目标S-MSC。
优选地，所述处理模块包括以下至少之一：第一发送单元，设置为通过确定的所述目标S-MSC，向所述被叫终端发送用于建立会话的第一会话建立请求消息；和/或，第二发送单元，设置为依据归属位置寄存器HLR从所述目标S-MSC查询终端漫游号码，或者直接从所述目标S-MSC查询所述终端漫游号码；依据查询的所述终端漫游号码向所述被叫终端发送用于建立会话的第二会话建立请求消息。
优选地，该装置还包括：第一发送模块，设置为向所述被叫终端发送第二连接失败消息。
根据本发明实施例的还一方面，提供了一种增强型移动交换中心eMSC，包括上述任一项所述的装置。
根据本发明实施例的还一方面，提供了一种eMSC，所述eMSC与服务移动交换中心S-MSC为同一个MSC。
根据本发明实施例的一方面，提供了一种网络间切换的处理装置，包括：接收模块，设置为接收增强型移动交换中心eMSC发送的用于请求网络切换的第二网络切换请求消息；第二发送模块，设置为依据所述第二网络切换请求消息，向所述eMSC发送被叫终端的终端状态消息，其中，所述终端状态消息用于所述eMSC继续基于切换后的所述拜访网络进行终呼处理。
根据本发明实施例的另一方面，提供了一种业务一致与连续性服务器SCC AS，包括上述所述的装置。
根据本发明实施例的一方面，提供了一种网络间切换的处理装置，包括：存储模块，设置为存储被叫终端注册的移动交换中心MSC；第三发送模块，设置为向增强型移动交换中心eMSC发送的用于请求网络切换的第三网络切换请求消息，其中，所述第三网络切换请求消息中携带有用于标识所述被叫终端注册的所述MSC的标识信息。
根据本发明实施例的另一方面，提供了一种移动管理实体MME，包括上述所述的装置。
根据本发明实施例的另一方面，提供了一种GPRS服务节点SGSN，包括上述所述的装置。
通过本发明实施例，采用确定被叫终端处于振铃状态或振铃前状态时，单模业务连续性SRVCC切换失败；继续基于切换后的拜访网络进行终呼处理，解决了相关技术中被叫侧处于振铃态或振铃前状态时，进行SRVCC切换，会发生切换失败的问题，进而达到了在终呼不支持振铃态或振铃前状态时SRVCC切换的情况下，也能够成功建立呼叫的效果。
附图说明
此处所说明的附图用来提供对本发明的进一步理解，构成本申请的一部分，本发明的示意性实施例及其说明用于解释本发明，并不构成对本发明的不当限定。在附图中：
图1是相关技术中eSRVCC的架构示意图；
图2是相关技术中终呼侧SRVCC，altering SRVCC和pre-alerting SRVCC的时间定义示意图；
图3是相关技术中终呼侧，振铃态会话的单模业务连续性切换的流程图；
图4是相关技术中终呼UE在pre-alerting、或者alerting状态时，切换失败的流程图；
图5是根据本发明实施例的网络间切换的处理方法一的流程图；
图6是根据本发明实施例的网络间切换的处理方法二的流程图；
图7是根据本发明实施例的网络间切换的处理方法三的流程图；
图8是根据本发明实施例的终呼侧pre-alerting SRVCC的流程图一；
图9是根据本发明实施例的终呼侧pre-alerting SRVCC的流程图二；
图10是根据本发明实施例的终呼侧pre-alerting SRVCC的流程图三；
图11是根据本发明实施例的UE在EPC发起联合附着过程的流程图；
图12是根据本发明实施例的对图8所示实施例的优化方式的流程图；
图13是根据本发明实施例对应于图8所示实施例在UE处于alerting状态下，发生SRVCC，且UE不支持alerting SRVCC情况下的流程图；
图14是根据本发明实施例的对应于图9所示实施例在UE处于alerting状态下，才发生 SRVCC，且UE不支持alerting SRVCC情况下的流程图；
图15是根据本发明实施例的网络间切换的处理装置一的结构框图；
图16是根据本发明实施例的网络间切换的处理装置中第一确定模块152的结构框图；
图17是根据本发明实施例的网络间切换的处理装置一的优选结构框图一；
图18是根据本发明实施例的网络间切换的处理装置中第二确定模块172的结构框图；
图19是根据本发明实施例的网络间切换的处理装置中处理模块154的结构框图；
图20是根据本发明实施例的网络间切换的处理装置一的优选结构框图二；
图21是根据本发明实施例的一种增强型移动交换中心eMSC的结构示意图；
图22是根据本发明实施例的网络间切换的处理装置二的结构框图；
图23是根据本发明实施例的业务一致与连续性服务器SCC AS的结构示意图；
图24是根据本发明实施例的网络间切换的处理装置三的结构框图；
图25是根据本发明实施例的移动管理实体MME的结构框图；
图26是根据本发明实施例的GPRS服务节点SGSN的结构框图。
具体实施方式
下文中将参考附图并结合实施例来详细说明本发明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
需要说明的是，本发明的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
在本实施例中提供了一种网络间切换的处理方法，图5是根据本发明实施例的网络间切换的处理方法一的流程图，如图5所示，该流程包括如下步骤：
步骤S502，确定被叫终端处于振铃状态或振铃前状态时，单模业务连续性SRVCC切换失败；
步骤S504，继续基于切换后的拜访网络进行终呼处理。
通过上述步骤，在确定被叫侧不支持振铃状态或振铃前状态的SRVCC切换时，继续基于切换后的拜访网络进行终呼处理，相对于相关技术中，在被叫侧不支持振铃状态或振铃前状态的SRVCC切换时，对呼叫进行放弃导致终端无法收到呼叫来说，采用继续基于拜访网络进行终呼处理，不仅有效地解决了相关技术中，被叫侧处于振铃态或振铃前状态时，进行SRVCC切换，会发生切换失败的问题，进而达到了在终呼不支持振铃态或振铃前状态时SRVCC切换的情况下，也能够成功建立呼叫，有效提高呼叫成功建立的效率的效果。
在确定被叫终端处于振铃状态或振铃前状态时，SRVCC切换失败可以从多个方面来进行，例如，接收到业务一致与连续性服务器SCC AS发送的终端状态消息，和/或，接收到被叫终端发送的第一连接失败消息；依据终端状态消息和/或第一连接失败消息，确定SRVCC切换失败。该终端状态消息指示出被叫终端处于振铃状态或振铃前状态，和/或用于确定被叫终端处于振铃状态或振铃前状态时不支持SRVCC切换。其中，需要说明的是，上述终端状态消息可以仅仅包括用于标明终端所处状态的状态信息，例如，当终端处于振铃前状态时，则可以直接确定该终端不支持SRVCC切换；当然该终端状态消息也可以不仅仅包括用于终端所处状态的状态信息，还包括直接表明终端是否支持SRVCC切换的能力信息。该终端状态消息用于确定被叫终端处于振铃状态或振铃前状态时不支持SRVCC切换也可以采用多种方式，比如，在该被叫终端所支持的能力集合中，并没有显示该被叫终端支持处于振铃状态或振铃前状态时不支持SRVCC切换；通过上述消息，可以确定被叫终端不支持处于振铃状态或振铃前状态时的SRVCC切换。
优选地，在确定被叫终端处于振铃状态或振铃前状态时，SRVCC切换失败之前，还可以确定网络切换后用于终呼处理的目标服务移动交换中心S-MSC。需要说明的是，当处于不同的场景下，确定该用于终呼处理的目标S-MSC的方式也不同，例如，当MME和/或SGSN没有存储被叫终端注册的MSC的情况下，由eMSC通过源S-MSC来确定目标S-MSC；而当MME和/或SGSN存储有被叫终端注册的MSC的情况下，确定网络切换后用于终呼处理的目标S-MSC包括：接收移动管理实体MME和/或GPRS服务节点SGSN发送的用于请求切换网络的第一网络切换请求消息，其中，第一网络切换请求消息中携带有用于标识被叫终端注册的MSC的标识信息；之后，确定标识信息标识的MSC为目标S-MSC。
基于上述确定用于终呼处理的目标S-MSC的方式不同，继续基于切换后的拜访网络进行终呼处理的方式也可以不同，例如，可以包括以下至少之一：直接通过确定的目标S-MSC，向被叫终端发送用于建立会话的第一会话建立请求消息，例如，该第一会话建立请求消息可以为Setup消息；和/或，先依据归属位置寄存器HLR从目标S-MSC查询终端漫游号码，或者直接从目标S-MSC查询终端漫游号码；之后，依据查询的终端漫游号码向被叫终端发送用于建立会话的第二会话建立请求消息，例如，该第二会话建立请求消息可以为初始地址消息IAM消息，S-MSC在收到IAM消息后，继续向UE发送Setup消息。
需要说明的是，在继续基于切换后的拜访网络进行终呼处理之前，还包括向被叫终端发送第二连接失败消息。通过向被叫终端发送该第二连接失败消息，使得被叫终端有效清除之前已有的会话状态。
图6是根据本发明实施例的网络间切换的处理方法二的流程图，如图6所示，该流程包括如下步骤：
步骤S602，接收增强型移动交换中心eMSC发送的用于请求网络切换的第二网络切换请求消息；
步骤S640，依据第二网络切换请求消息，向eMSC发送被叫终端的终端状态消息，其中， 终端状态消息用于eMSC继续基于切换后的拜访网络进行终呼处理。终端状态消息指示出被叫终端处于振铃状态或振铃前状态，和/或用于确定被叫终端处于振铃状态或振铃前状态时不支持SRVCC切换。需要说明的是，该终端状态消息可以仅仅包括用于标明终端所处状态的状态信息，例如，当终端处于振铃前状态时，则可以直接确定该终端不支持SRVCC切换；当然该终端状态消息也可以不仅仅包括用于终端所处状态的状态信息，还包括直接表明终端是否支持SRVCC切换的能力信息。即该终端状态消息用于确定被叫终端处于振铃状态或振铃前状态时不支持SRVCC切换。
通过上述步骤，通过向eMSC发送被叫终端的终端状态消息，在确定被叫侧不支持振铃状态或振铃前状态的SRVCC切换时，继续基于切换后的拜访网络进行终呼处理，相对于相关技术中，在被叫侧不支持振铃状态或振铃前状态的SRVCC切换时，对呼叫进行放弃导致终端无法收到呼叫来说，采用继续基于拜访网络进行终呼处理，不仅有效地解决了相关技术中，被叫侧处于振铃态或振铃前状态时，进行SRVCC切换，会发生切换失败的问题，进而达到了在终呼不支持振铃态或振铃前状态时SRVCC切换的情况下，也能够成功建立呼叫，有效提高呼叫成功建立的效率的效果。
需要说明的是，上述第二网络切换请求消息还用于指示eMSC支持处于振铃状态或振铃前状态时，单模业务连续性SRVCC切换。
图7是根据本发明实施例的网络间切换的处理方法三的流程图，如图7所示，该流程包括如下步骤：
步骤S702，存储被叫终端注册的移动交换中心MSC；
步骤S704，向增强型移动交换中心eMSC发送的用于请求网络切换的第三网络切换请求消息，其中，第三网络切换请求消息中携带有用于标识被叫终端注册的MSC的标识信息。优选地，该标识信息用于eMSC在被叫终端处于振铃状态或振铃前状态时，单模业务连续性SRVCC切换失败之前，确定网络切换后用于终呼处理的目标服务移动交换中心S-MSC。
通过上述步骤，依据存储的MSC确定被叫终端处于振铃状态或振铃前状态时，SRVCC切换失败后，以及网络切换后用于终呼处理的目标服务移动交换中心S-MSC，以及在确定被叫侧不支持振铃状态或振铃前状态的SRVCC切换时，继续基于切换后的拜访网络进行终呼处理，相对于相关技术中，在被叫侧不支持振铃状态或振铃前状态的SRVCC切换时，对呼叫进行放弃导致终端无法收到呼叫来说，采用继续基于拜访网络进行终呼处理，不仅有效地解决了相关技术中，被叫侧处于振铃态或振铃前状态时，进行SRVCC切换，会发生切换失败的问题，进而达到了在终呼不支持振铃态或振铃前状态时SRVCC切换的情况下，也能够成功建立呼叫，有效提高呼叫成功建立的效率的效果。
为克服相关技术中的不足，在本发明实施例中提供了一种在终呼UE由于不支持pre-laerting/alerting SRVCC切换时，发生SRVCC切换后，仍旧能成功建立呼叫的方法。在本实施例中，在终呼侧，SCC AS发现是per-alerting SRVCC切换时，并不释放eMSC会话。eMSC从SCC AS收到用户的状态后(pre-alerting/alerting)，和/或收到UE的disConnect消息，知道 切换失败，继续在CS域完成呼叫。
下面将结合附图对本发明优选实施方式进行说明。
图8是根据本发明实施例的终呼侧pre-alerting SRVCC的流程图一，如图8所示，该流程包括如下步骤：
步骤S801：被叫侧的SCC AS收到呼叫请求，呼叫请求转发给UE；
步骤S802：被叫UE向远端发送183消息；
步骤S803：Source RAN发现UE信号质量不好需要切换后，发切换请求给MME/SGSN；
步骤S804：MME/SGSN发现UE有QCI＝1的bearer承载；
步骤S805：MME/SGSN向eMSC发送PS to CS切换请求；
步骤S806：eMSC向目标无线接入网(Target RAN)RNC/BSS预留资源；这个过程可能是eMSC确定目标Serving MSC，通过Serving MSC完成。
步骤S807：eMSC向MME发送切换请求响应，表示可以切换；
步骤S808：MME通过源无线接入网向UE发送切换命令；
步骤S809：UE切换到CS域，发现不支持pre-alerting切换；
步骤S810：UE发Disconnect消息，该消息通过Serving MSC到达eMSC；需要说明的是，这个步骤是可选的，如果eMSC没有收到该消息，eMSC可选的，通过S-MSC发disconnect给UE。
步骤S811：eMSC向会话的锚点SCC AS发起会话切换请求。该步骤中，eMSC可选的，携带支持终呼Pre-alerting SRVCC的指示；
注：步骤S811和步骤S807是并行的，没有次序关系。
步骤S812：SCC AS更新远端；
步骤S813：SCC AS通知eMSC，UE目前在pre-alerting态；
步骤S814：eMSC向UE发送Setup。该消息通过Serving MSC到达UE；
步骤S815：当用户接听时，UE发送Connect消息。该消息通过Serving MSC到达eMSC。
注：eMSC和S-MSC可以是同一个MSC。
图9是根据本发明实施例的终呼侧pre-alerting SRVCC的流程图二，如图9所示，该流程包括如下步骤：
步骤S901：被叫侧用户在Pre-alerting状态时，发生SRVCC切换。步骤同上述图8中的步骤S801～808；
步骤S902：eMSC向会话的锚点SCC AS发起会话切换请求。该步骤中，eMSC可选的，携带支持终呼Pre-alerting SRVCC的指示；
步骤S903：SCC AS更新远端；
步骤S904：SCC AS通知eMSC，UE目前在pre-alerting态；
步骤S905：UE切换到CS域，发现不支持pre-alerting切换；
注：如同图8一样，步骤S902和步骤S905之间没有次序关系。
步骤S906：UE发Disconnect消息，该消息通过Serving MSC到达eMSC；需要说明的是，这个步骤是可选的，如果eMSC没有收到该消息，eMSC可选的，通过S-MSC发disconnect给UE。
步骤S907：eMSC释放和UE之间的会话；
步骤S908：eMSC向HLR发送路由查询请求(Sending Routing Information，简称为SRI)；
步骤S609：HLR向Serving MSC查询漫游号码(Provide Roaming Number，简称为PRN)，MSC返回终端路由号码(MS Routing Number，简称为MSRN)给HLR；
步骤S910：HLR向eMSC返回路由号码；
步骤S911：eMSC向Serving MSC发送IAM消息；
步骤S912：Serving MSC向UE发送Setup消息；
步骤S913：当用户接听时，UE发送Connect消息给Serving MSC。
注：eMSC和S-MSC可以是同一个MSC，此时变成图8的方案。
图10是根据本发明实施例的终呼侧pre-alerting SRVCC的流程图三，如图10所示，该流程包括如下步骤，在本实施例中，eMSC直接向Serving MSC请求漫游号码。
步骤S1001：被叫侧用户在Pre-alerting状态时，发生SRVCC切换。步骤同图8步骤S801～808；
步骤S1002：eMSC向会话的锚点SCC AS发起会话切换请求。该步骤中，eMSC可选的，携带支持终呼Pre-alerting SRVCC的指示；
步骤S1003：SCC AS更新远端；
步骤S1004：SCC AS通知eMSC，UE目前在pre-alerting态；
步骤S1005：UE切换到CS域，发现不支持pre-alerting切换；
注：如同图8一样，步骤S1002和步骤S1005之间没有次序关系。
步骤S1006：UE发Disconnect消息，该消息通过Serving MSC到达eMSC。需要说明的是，这个步骤是可选的，如果eMSC没有收到该消息，eMSC可选的，通过S-MSC发disconnect给UE；
步骤S1008：eMSC释放和UE之间的会话；
步骤S1009：eMSC向Serving MSC查询漫游号码(Provide Roaming Number，简称为PRN)，Serving MSC返回终端路由号码(MS Routing Number，简称为MSRN)给eMSC；
步骤S1010：eMSC向Serving MSC发送IAM消息；
步骤S1011：Serving MSC向UE发送Setup消息；
步骤S1012：当用户接听时，UE发送Connect消息给Serving MSC。
注：eMSC和S-MSC可以是同一个MSC，此时变成图8的方案。
需要说明的是，UE在EPC附着的时候，可以发起联合注册更新，图11是根据本发明实施例的UE在EPC发起联合附着过程的流程图，如图11所示。在联合注册更新后，MME其代替用户注册的MSC信息。
步骤S1101：UE向MME发起attach请求，要求做combined attach；
步骤S1102：MME向EPC发起attach过程；
步骤S1103：MME向MSC发起位置更新请求(Location Area Update，简称LAU)；
步骤S1104:MSC建立和MME之间的SGs接口；
步骤S1105：MSC和HSS/HLR完成CS域的Location Update过程，获得用户签约数据；
步骤S1106：MSC向MME发送LAU接受应答。
此时，MME会保存MSC的信息。
作为上述实施例的优化方式，MME在切换过程中，会选择保存的MSC作为eMSC，或者将保存的MSC信息在切换请求中发送给eMSC。前者对上述的流程并没有影响，相当于eMSC和Serving MSC合一了。对于后者，eMSC可以选择收到的MSC作为Serving MSC。下面举例说明。
图12是根据本发明实施例的对图8所示实施例的优化方式的流程图，如图12所示，该流程包括如下步骤：
步骤S1200：UE在EPC做联合附着更新，MME保存了注册的MSC2信息；
步骤S1201：被叫侧的SCC AS收到呼叫请求，呼叫请求转发给UE；
步骤S1202：被叫UE向远端发送183消息；
步骤S1203：Source RAN发现UE信号质量不好需要切换后，发切换请求给MME/SGSN；
步骤S1204：MME/SGSN发现UE有QCI＝1的bearer承载；
步骤S1205：MME/SGSN向eMSC发送PS to CS切换请求，其中携带MSC2信息；
步骤S1206：eMSC向目标无线接入网(Target RAN)RNC/BSS预留资源；这个过程可能是eMSC确定MSC2作为目标Serving MSC，通过Serving MSC完成。
步骤S1207：eMSC向MME发送切换请求响应，表示可以切换；
步骤S1208：MME通过源无线接入网向UE发送切换命令；
步骤S1209：UE切换到CS域，发现不支持pre-alerting切换；
步骤S1210：UE发Disconnect消息，该消息通过Serving MSC到达eMSC。需要说明的是，这个步骤是可选的，如果eMSC没有收到该消息，eMSC可选的，通过S-MSC发disconnect给UE；
步骤S1211：eMSC向会话的锚点SCC AS发起会话切换请求。该步骤中，eMSC可选的，携带支持终呼Pre-alerting SRVCC的指示；
注：步骤S1211和1207可以是并行的，没有次序关系。
步骤S1212：SCC AS更新远端；
步骤S1213：SCC AS通知eMSC，UE目前在pre-alerting态；
步骤S1214：eMSC向UE发送Setup。该消息通过Serving MSC到达UE；
步骤S1215：当用户接听时，UE发送Connect消息。该消息通过Serving MSC到达eMSC。
注：eMSC和S-MSC可以是同一个MSC。
上述是对图8实施例的优化方式。对于图9所示实施例，图10所示实施例，也可以采用这种优化方式，MME保存联合附着时的注册的MSC信息。在图9的步骤S901，图10的步骤S1001中，当MME向eMSC发起PS to CS切换请求时，携带保存的MSC信息。eMSC在向目标无线接入网(Target RAN)RNC/BSS预留资源时，eMSC使用收到的MSC作为Serving MSC，其余步骤都是一样。
需要说明的是，上述实施例及优选实施方式，都是UE不支持pre-alerting SRVCC的场景。当UE仅支持通话中SRVCC，而不支持alerting SRVCC时，上述方式也能适用。
图13是根据本发明实施例对应于图8所示实施例在UE处于alerting状态下，发生SRVCC，且UE不支持alerting SRVCC情况下的流程图，如图13所示，该流程包括如下步骤：
步骤S1300：可选的，UE在EPC做联合附着更新，MME保存了注册的MSC2信息；
步骤S1301：被叫侧的SCC AS收到呼叫请求，呼叫请求转发给UE；
步骤S1302：被叫UE向远端发送180振铃消息(与本实施例无关的中间步骤省略)；
步骤S1303：Source RAN发现UE信号质量不好需要切换后，发切换请求给MME/SGSN；
步骤S1304：MME/SGSN发现UE有QCI＝1的bearer承载；
步骤S1305：MME/SGSN向eMSC发送PS to CS切换请求，可选的，当MME在步骤1000保存了MSC2信息，则在该消息中携带MSC2信息；
步骤S1306：eMSC向目标无线接入网(Target RAN)RNC/BSS预留资源；可选的，当eMSC收到MSC2信息，这个过程可以是eMSC确定MSC2作为目标Serving MSC，通过Serving MSC完成。
步骤S1307：eMSC向MME发送切换请求响应，表示可以切换；
步骤S1308：MME通过源无线接入网向UE发送切换命令；
步骤S1309：UE切换到CS域，发现不支持alerting切换；
步骤S1310：UE发Disconnect消息，该消息通过Serving MSC到达eMSC。需要说明的是，这个步骤是可选的，如果eMSC没有收到该消息，eMSC可选的，通过S-MSC发disconnect给UE；
步骤S1311：eMSC向会话的锚点SCC AS发起会话切换请求。该步骤中，eMSC可选的，携带支持终呼alerting SRVCC/Pre-alerting SRVCC的指示；
注：步骤S1311和步骤S1307是并行的，没有次序关系。
步骤S1312：SCC AS更新远端；
步骤S1313：SCC AS通知eMSC，UE目前在alerting态；
步骤S1314：eMSC向UE发送Setup。该消息通过Serving MSC到达UE；
步骤S1315：当用户接听时，UE发送Connect消息。该消息通过Serving MSC到达eMSC。
注：eMSC和S-MSC可以是同一个MSC。
图14是根据本发明实施例的对应于图9所示实施例在UE处于alerting状态下，才发生SRVCC，且UE不支持alerting SRVCC情况下的流程图，如图14所示，该流程包括如下步骤：
步骤S1400：可选的，UE在EPC做联合附着更新，MME保存了注册的MSC2信息；
步骤S1401：被叫侧的SCC AS收到呼叫请求，呼叫请求转发给UE；
步骤S1402：被叫UE向远端发送180振铃消息(与本专利无关的中间步骤省略)；
步骤S1403：Source RAN发现UE信号质量不好需要切换后，发切换请求给MME/SGSN；
步骤S1404：MME/SGSN发现UE有QCI＝1的bearer承载；
步骤S1405：MME/SGSN向eMSC发送PS to CS切换请求，可选的，当MME在步骤步骤S1400保存了MSC2信息，则在该消息中携带MSC2信息；
步骤S1406：eMSC向目标无线接入网(Target RAN)RNC/BSS预留资源；可选的，当eMSC收到MSC2信息，这个过程可以是eMSC确定MSC2作为目标Serving MSC，通过Serving MSC完成。
步骤S1407：eMSC向MME发送切换请求响应，表示可以切换；
步骤S1408：MME通过源无线接入网向UE发送切换命令；
步骤S1409：UE切换到CS域，发现不支持alerting切换；
步骤S1410：UE发Disconnect消息，该消息通过Serving MSC到达eMSC。需要说明的是，这个步骤是可选的，如果eMSC没有收到该消息，eMSC可选的，通过S-MSC发disconnect给UE；
步骤S1411：eMSC向会话的锚点SCC AS发起会话切换请求。该步骤中，eMSC可选的，携带支持终呼alerting SRVCC/Pre-alerting SRVCC的指示；
注：步骤步骤S1411和步骤S1407是并行的，没有次序关系。
步骤S1412：SCC AS更新远端；
步骤S1413：SCC AS通知eMSC，UE目前在alerting态；
步骤S1414：eMSC向HLR发送路由查询请求(Sending Routing Information，简称SRI)；
步骤S1415：HLR向Serving MSC查询漫游号码(Provide Roaming Number，简称PRN)，Serving MSC返回终端路由号码(MS Routing Number，简称MSRN)给HLR；
步骤S1416：HLR向eMSC返回路由号码；
步骤S1417：eMSC向Serving MSC发送IAM消息；
步骤S1418：Serving MSC向UE发送Setup消息；
步骤S1419：当用户接听时，UE发送Connect消息给Serving MSC。
注：eMSC和S-MSC可以是同一个MSC。此时变成图13的方案。
对应于图10的实施例，在UE处于alerting状态下，才发生SRVCC，且UE不支持alerting SRVCC情况下的优选实施方式，和图14类似，区别是步骤1413后，eMSC直接向Serving MSC查询路由号码，在收到路由号码后，向Serving MSC发起IAM呼叫请求，Serving MSC收到IAM消息后，向UE发起Setup。
注：eMSC和S-MSC可以是同一个MSC。此时变成图13的方案。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本发明实施例的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本发明各个实施例的方法。
在本实施例中还提供了一种网络间切换的处理装置，该装置用于实现上述实施例及优选实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图15是根据本发明实施例的网络间切换的处理装置一的结构框图，如图15所示，该装置包括：第一确定模块152和处理模块154，下面对该装置进行说明。
第一确定模块152，设置为确定被叫终端处于振铃状态或振铃前状态时，单模业务连续性SRVCC切换失败；处理模块154，连接至上述第一确定模块152，设置为继续基于切换后的拜访网络进行终呼处理。
图16是根据本发明实施例的网络间切换的处理装置中第一确定模块152的结构框图，如图16所示，该第一确定模块152包括：第一接收单元162和第一确定单元164，下面对该第一确定模块152进行说明。
第一接收单元162，设置为接收到业务一致与连续性服务器SCC AS发送的终端状态消息，和/或，接收到被叫终端发送的第一连接失败消息；第一确定单元164，连接至上述第一接收单元162，设置为依据终端状态消息和/或第一连接失败消息，确定SRVCC切换失败。
图17是根据本发明实施例的网络间切换的处理装置一的优选结构框图一，如图17所示，该装置除包括图15所示的结构外，还包括：第二确定模块172，下面对该第二确定模块172进行说明。
第二确定模块172，连接至上述第一确定模块152，设置为确定网络切换后用于终呼处理的目标服务移动交换中心S-MSC。
图18是根据本发明实施例的网络间切换的处理装置中第二确定模块172的结构框图，如图18所示，该第二确定模块172包括：第二接收单元182和第二确定单元184，下面对该第二确定模块172进行说明。
第二接收单元182，设置为接收移动管理实体MME和/或GPRS服务节点SGSN发送的用于请求切换网络的第一网络切换请求消息，其中，第一网络切换请求消息中携带有用于标识被叫终端注册的MSC的标识信息；第二确定单元184，连接至上述第二接收单元182，用于确定标识信息标识的MSC为目标S-MSC。
图19是根据本发明实施例的网络间切换的处理装置中处理模块154的结构框图，如图19所示，该处理模块154包括以下至少之一：第一发送单元192、第二发送单元194，下面对该处理模块154进行说明。
第一发送单元192，设置为通过确定的目标S-MSC，向被叫终端发送用于建立会话的第一会话建立请求消息；和/或，第二发送单元194，设置为依据归属位置寄存器HLR从目标S-MSC查询终端漫游号码，或者直接从目标S-MSC查询终端漫游号码；依据查询的终端漫游号码向被叫终端发送用于建立会话的第二会话建立请求消息。
图20是根据本发明实施例的网络间切换的处理装置一的优选结构框图二，如图20所示，该装置除包括图15所示的结构外，还包括：第一发送模块202，下面对该第一发送模块202进行说明。
第一发送模块202，连接至上述第一确定模块152和处理模块154，设置为向被叫终端发送第二连接失败消息。
图21是根据本发明实施例的一种增强型移动交换中心eMSC的结构示意图，如图21所示，该eMSC 212包括上述任一项的网络间切换的处理装置一214。
优选地，该eMSC与服务移动交换中心S-MSC可以为同一个MSC。
图22是根据本发明实施例的网络间切换的处理装置二的结构框图，如图22所示，该装置包括：接收模块222和第二发送模块224，下面对该装置进行说明。
接收模块222，设置为接收增强型移动交换中心eMSC发送的用于请求网络切换的第二网络切换请求消息；第二发送模块224，连接至上述接收模块222，设置为依据第二网络切换请求消息，向eMSC发送被叫终端的终端状态消息，其中，终端状态消息用于eMSC继续基于切换后的拜访网络进行终呼处理。
优选地，上述第二网络切换请求消息还用于确定eMSC支持处于振铃状态或振铃前状态时，单模业务连续性SRVCC切换。
图23是根据本发明实施例的业务一致与连续性服务器SCC AS的结构示意图，如图23所示，该SCC AS 232包括上述任一项的网络间切换的处理装置二234。
图24是根据本发明实施例的网络间切换的处理装置三的结构框图，如图24所示，该装 置包括：存储模块242和第三发送模块244，下面对该装置进行说明。
存储模块242，设置为存储被叫终端注册的移动交换中心MSC；第三发送模块244，连接至上述存储模块242，设置为向增强型移动交换中心eMSC发送的用于请求网络切换的第三网络切换请求消息，其中，第三网络切换请求消息中携带有用于标识被叫终端注册的MSC的标识信息。优选地，该标识信息用于eMSC在被叫终端处于振铃状态或振铃前状态时，单模业务连续性SRVCC切换失败之前，确定网络切换后用于终呼处理的目标服务移动交换中心S-MSC。
图25是根据本发明实施例的移动管理实体MME的结构框图，如图25所示，该MME 252包括上述的网络间切换的处理装置三254。
图26是根据本发明实施例的GPRS服务节点SGSN的结构框图，如图26所示，该SGSN262包括上述的网络间切换的处理装置三254。
需要说明的是，上述各个模块是可以通过软件或硬件来实现的，对于后者，可以通过以下方式实现，但不限于此：上述模块均位于同一处理器中；或者，上述模块分别位于多个处理器中。
本发明的实施例还提供了一种存储介质。可选地，在本实施例中，上述存储介质可以被设置为存储用于执行以下步骤的程序代码：
S1，确定被叫终端处于振铃状态或振铃前状态时，单模业务连续性SRVCC切换失败；
S2，继续基于切换后的拜访网络进行终呼处理。
可选地，存储介质还被设置为存储用于执行以下步骤的程序代码：
确定被叫终端处于振铃状态或振铃前状态时，SRVCC切换失败包括：
S1，接收到业务一致与连续性服务器SCC AS发送的终端状态消息，和/或，接收到被叫终端发送的第一连接失败消息；
S2，依据终端状态消息和/或第一连接失败消息，确定SRVCC切换失败。
可选地，存储介质还被设置为存储用于执行以下步骤的程序代码：
S1，所述终端状态消息指示出所述被叫终端处于振铃状态或振铃前状态，和/或用于确定所述被叫终端处于振铃状态或振铃前状态时不支持SRVCC切换。
可选地，存储介质还被设置为存储用于执行以下步骤的程序代码：
在确定被叫终端处于振铃状态或振铃前状态时，SRVCC切换失败之前，还包括：
S1，确定网络切换后用于终呼处理的目标服务移动交换中心S-MSC。
可选地，存储介质还被设置为存储用于执行以下步骤的程序代码：
确定网络切换后用于终呼处理的目标S-MSC包括：
S1，接收移动管理实体MME和/或GPRS服务节点SGSN发送的用于请求切换网络的第一网络切换请求消息，其中，第一网络切换请求消息中携带有用于标识被叫终端注册的MSC的标识信息；
S2，确定标识信息标识的MSC为目标S-MSC。
可选地，存储介质还被设置为存储用于执行以下步骤的程序代码：
继续基于切换后的拜访网络进行终呼处理包括以下至少之一：
S1，通过确定的目标S-MSC，向被叫终端发送用于建立会话的第一会话建立请求消息；和/或，依据归属位置寄存器HLR从目标S-MSC查询终端漫游号码，或者直接从目标S-MSC查询终端漫游号码；依据查询的终端漫游号码向被叫终端发送用于建立会话的第二会话建立请求消息。
可选地，存储介质还被设置为存储用于执行以下步骤的程序代码：
S1，所述第一会话建立请求消息为Setup消息，或者，所述第二会话建立请求消息为初始地址消息IAM消息。
可选地，存储介质还被设置为存储用于执行以下步骤的程序代码：
在继续基于切换后的拜访网络进行终呼处理之前，还包括：
S1，向被叫终端发送第二连接失败消息。
本发明的实施例还提供了一种存储介质。可选地，在本实施例中，上述存储介质可以被设置为存储用于执行以下步骤的程序代码：
S1，接收增强型移动交换中心eMSC发送的用于请求网络切换的第二网络切换请求消息；
S2，依据第二网络切换请求消息，向eMSC发送被叫终端的终端状态消息，其中，终端状态消息用于eMSC继续基于切换后的拜访网络进行终呼处理。
可选地，存储介质还被设置为存储用于执行以下步骤的程序代码：
S1，第二网络切换请求消息还用于指示eMSC支持处于振铃状态或振铃前状态时，单模业务连续性SRVCC切换；或者，所述终端状态消息指示出所述被叫终端处于振铃状态或振铃前状态，和/或用于确定所述被叫终端处于振铃状态或振铃前状态时不支持SRVCC切换。
本发明的实施例还提供了一种存储介质。可选地，在本实施例中，上述存储介质可以被设置为存储用于执行以下步骤的程序代码：
S1，存储被叫终端注册的移动交换中心MSC；
S2，向增强型移动交换中心eMSC发送的用于请求网络切换的第三网络切换请求消息， 其中，第三网络切换请求消息中携带有用于标识被叫终端注册的MSC的标识信息。
可选地，存储介质还被设置为存储用于执行以下步骤的程序代码：
S1，标识信息用于eMSC在被叫终端处于振铃状态或振铃前状态时，单模业务连续性SRVCC切换失败之前，确定网络切换后用于终呼处理的目标服务移动交换中心S-MSC。
可选地，在本实施例中，上述存储介质可以包括但不限于：U盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、移动硬盘、磁碟或者光盘等各种可以存储程序代码的介质。
可选地，在本实施例中，处理器根据存储介质中已存储的程序代码执行：确定被叫终端处于振铃状态或振铃前状态时，单模业务连续性SRVCC切换失败；继续基于切换后的拜访网络进行终呼处理。
可选地，在本实施例中，处理器根据存储介质中已存储的程序代码执行：确定被叫终端处于振铃状态或振铃前状态时，SRVCC切换失败包括：接收到业务一致与连续性服务器SCC AS发送的终端状态消息，和/或，接收到被叫终端发送的第一连接失败消息；依据终端状态消息和/或第一连接失败消息，确定SRVCC切换失败。
可选地，在本实施例中，处理器根据存储介质中已存储的程序代码执行：该终端状态消息指示出所述被叫终端处于振铃状态或振铃前状态，和/或用于确定被叫终端处于振铃状态或振铃前状态时不支持SRVCC切换的标识信息。
可选地，在本实施例中，处理器根据存储介质中已存储的程序代码执行：在确定被叫终端处于振铃状态或振铃前状态时，SRVCC切换失败之前，还包括：确定网络切换后用于终呼处理的目标服务移动交换中心S-MSC。
可选地，在本实施例中，处理器根据存储介质中已存储的程序代码执行：确定网络切换后用于终呼处理的目标S-MSC包括：接收移动管理实体MME和/或GPRS服务节点SGSN发送的用于请求切换网络的第一网络切换请求消息，其中，第一网络切换请求消息中携带有用于标识被叫终端注册的MSC的标识信息；确定标识信息标识的MSC为目标S-MSC。
可选地，在本实施例中，处理器根据存储介质中已存储的程序代码执行：继续基于切换后的拜访网络进行终呼处理包括以下至少之一：通过确定的目标S-MSC，向被叫终端发送用于建立会话的第一会话建立请求消息；和/或，依据归属位置寄存器HLR从目标S-MSC查询终端漫游号码，或者直接从目标S-MSC查询终端漫游号码；依据查询的终端漫游号码向被叫终端发送用于建立会话的第二会话建立请求消息。
可选地，在本实施例中，处理器根据存储介质中已存储的程序代码执行：所述第一会话建立请求消息为Setup消息，或者，所述第二会话建立请求消息为初始地址消息IAM消息。
可选地，在本实施例中，处理器根据存储介质中已存储的程序代码执行：在继续基于切换后的拜访网络进行终呼处理之前，还包括：向被叫终端发送第二连接失败消息。
可选地，在本实施例中，处理器根据存储介质中已存储的程序代码执行：接收增强型移动交换中心eMSC发送的用于请求网络切换的第二网络切换请求消息；依据第二网络切换请求消息，向eMSC发送被叫终端的终端状态消息，其中，终端状态消息用于eMSC继续基于切换后的拜访网络进行终呼处理。
可选地，在本实施例中，处理器根据存储介质中已存储的程序代码执行：第二网络切换请求消息还用于指示eMSC支持处于振铃状态或振铃前状态时，单模业务连续性SRVCC切换；或者，该终端状态消息指示出所述被叫终端处于振铃状态或振铃前状态，和/或用于确定被叫终端处于振铃状态或振铃前状态时不支持SRVCC切换。
可选地，在本实施例中，处理器根据存储介质中已存储的程序代码执行：
存储被叫终端注册的移动交换中心MSC；向增强型移动交换中心eMSC发送的用于请求网络切换的第三网络切换请求消息，其中，第三网络切换请求消息中携带有用于标识被叫终端注册的MSC的标识信息，标识信息用于eMSC在被叫终端处于振铃状态或振铃前状态时，单模业务连续性SRVCC切换失败之前，确定网络切换后用于终呼处理的目标服务移动交换中心S-MSC。
可选地，本实施例中的具体示例可以参考上述实施例及可选实施方式中所描述的示例，本实施例在此不再赘述。
显然，本领域的技术人员应该明白，上述的本发明的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本发明不限制于任何特定的硬件和软件结合。
以上所述仅为本发明的优选实施例而已，并不用于限制本发明，对于本领域的技术人员来说，本发明可以有各种更改和变化。凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。
工业实用性
如上所述，通过上述实施例及优选实施方式，采用确定被叫终端处于振铃状态或振铃前状态时，单模业务连续性SRVCC切换失败；继续基于切换后的拜访网络进行终呼处理，解决了相关技术中被叫侧处于振铃态或振铃前状态时，进行SRVCC切换，会发生切换失败的问题，进而达到了在终呼不支持振铃态或振铃前状态时SRVCC切换的情况下，也能够成功建立呼叫的效果。

Claims (25)

  1. 一种网络间切换的处理方法，包括：
    确定被叫终端处于振铃状态或振铃前状态时，单模业务连续性SRVCC切换失败；
    继续基于切换后的拜访网络进行终呼处理。
  2. 根据权利要求1所述的方法，其中，确定所述被叫终端处于振铃状态或振铃前状态时，所述SRVCC切换失败包括：
    接收到业务一致与连续性服务器SCC AS发送的终端状态消息，和/或，接收到所述被叫终端发送的第一连接失败消息；
    依据所述终端状态消息和/或所述第一连接失败消息，确定所述SRVCC切换失败。
  3. 根据权利要求2所述的方法，其中，所述终端状态消息指示出所述被叫终端处于振铃状态或振铃前状态，和/或用于确定所述被叫终端处于振铃状态或振铃前状态时不支持SRVCC切换。
  4. 根据权利要求1至3中任一项所述的方法，其中，在确定所述被叫终端处于振铃状态或振铃前状态时，所述SRVCC切换失败之前，还包括：
    确定网络切换后用于所述终呼处理的目标服务移动交换中心S-MSC。
  5. 根据权利要求4所述的方法，其中，确定网络切换后用于所述终呼处理的所述目标S-MSC包括：
    接收移动管理实体MME和/或GPRS服务节点SGSN发送的用于请求切换网络的第一网络切换请求消息，其中，所述第一网络切换请求消息中携带有用于标识所述被叫终端注册的MSC的标识信息；
    确定所述标识信息标识的所述MSC为所述目标S-MSC。
  6. 根据权利要求4所述的方法，其中，继续基于切换后的所述拜访网络进行终呼处理包括以下至少之一：
    通过确定的所述目标S-MSC，向所述被叫终端发送用于建立会话的第一会话建立请求消息；和/或，
    依据归属位置寄存器HLR从所述目标S-MSC查询终端漫游号码，或者直接从所述目标S-MSC查询所述终端漫游号码；依据查询的所述终端漫游号码向所述被叫终端发送用于建立会话的第二会话建立请求消息。
  7. 根据权利要求6所述的方法，其中，所述第一会话建立请求消息为Setup消息，或者，所述第二会话建立请求消息为初始地址消息IAM消息。
  8. 根据权利要求1至3，5至7中任一项所述的方法，其中，在继续基于切换后的所述拜访 网络进行终呼处理之前，还包括：
    向所述被叫终端发送第二连接失败消息。
  9. 一种网络间切换的处理方法，包括：
    接收增强型移动交换中心eMSC发送的用于请求网络切换的第二网络切换请求消息；
    依据所述第二网络切换请求消息，向所述eMSC发送被叫终端的终端状态消息，其中，所述终端状态消息用于所述eMSC继续基于切换后的所述拜访网络进行终呼处理。
  10. 根据权利要求9所述的方法，其中，所述第二网络切换请求消息还用于指示所述eMSC支持处于振铃状态或振铃前状态时，单模业务连续性SRVCC切换；或者，所述终端状态消息指示出所述被叫终端处于振铃状态或振铃前状态，和/或用于确定所述被叫终端处于振铃状态或振铃前状态时不支持SRVCC切换。
  11. 一种网络间切换的处理方法，包括：
    存储被叫终端注册的移动交换中心MSC；
    向增强型移动交换中心eMSC发送的用于请求网络切换的第三网络切换请求消息，其中，所述第三网络切换请求消息中携带有用于标识所述被叫终端注册的所述MSC的标识信息。
  12. 根据权利要求11所述的方法，其中，所述标识信息用于所述eMSC在所述被叫终端处于振铃状态或振铃前状态时，单模业务连续性SRVCC切换失败之前，确定网络切换后用于终呼处理的目标服务移动交换中心S-MSC。
  13. 一种网络间切换的处理装置，包括：
    第一确定模块，设置为确定被叫终端处于振铃状态或振铃前状态时，单模业务连续性SRVCC切换失败；
    处理模块，设置为继续基于切换后的拜访网络进行终呼处理。
  14. 根据权利要求13所述的装置，其中，所述第一确定模块包括：
    第一接收单元，设置为接收到业务一致与连续性服务器SCC AS发送的终端状态消息，和/或，接收到所述被叫终端发送的第一连接失败消息；
    第一确定单元，设置为依据所述终端状态消息和/或所述第一连接失败消息，确定所述SRVCC切换失败。
  15. 根据权利要求13或14所述的装置，其中，还包括：
    第二确定模块，设置为确定网络切换后用于所述终呼处理的目标服务移动交换中心S-MSC。
  16. 根据权利要求15所述的装置，其中，所述第二确定模块包括：
    第二接收单元，设置为接收移动管理实体MME和/或GPRS服务节点SGSN发送的用于请求切换网络的第一网络切换请求消息，其中，所述第一网络切换请求消息中携带有用于标识所述被叫终端注册的MSC的标识信息；
    第二确定单元，设置为确定所述标识信息标识的所述MSC为所述目标S-MSC。
  17. 根据权利要求15所述的装置，其中，所述处理模块包括以下至少之一：
    第一发送单元，设置为通过确定的所述目标S-MSC，向所述被叫终端发送用于建立会话的第一会话建立请求消息；和/或，
    第二发送单元，设置为依据归属位置寄存器HLR从所述目标S-MSC查询终端漫游号码，或者直接从所述目标S-MSC查询所述终端漫游号码；依据查询的所述终端漫游号码向所述被叫终端发送用于建立会话的第二会话建立请求消息。
  18. 根据权利要求13至14，16至17中任一项所述的装置，其中，还包括：
    第一发送模块，设置为向所述被叫终端发送第二连接失败消息。
  19. 一种增强型移动交换中心eMSC，包括权利要求13至18中任一项所述的装置。
  20. 根据权利要求19所述的一种eMSC，所述eMSC与服务移动交换中心S-MSC为同一个MSC。
  21. 一种网络间切换的处理装置，包括：
    接收模块，设置为接收增强型移动交换中心eMSC发送的用于请求网络切换的第二网络切换请求消息；
    第二发送模块，设置为依据所述第二网络切换请求消息，向所述eMSC发送被叫终端的终端状态消息，其中，所述终端状态消息用于所述eMSC继续基于切换后的所述拜访网络进行终呼处理。
  22. 一种业务一致与连续性服务器SCC AS，包括权利要求21所述的装置。
  23. 一种网络间切换的处理装置，包括：
    存储模块，设置为存储被叫终端注册的移动交换中心MSC；
    第三发送模块，设置为向增强型移动交换中心eMSC发送的用于请求网络切换的第三网络切换请求消息，其中，所述第三网络切换请求消息中携带有用于标识所述被叫终端注册的所述MSC的标识信息。
  24. 一种移动管理实体MME，包括权利要求23所述的装置。
  25. 一种GPRS服务节点SGSN，包括权利要求23所述的装置。
PCT/CN2017/071136 2016-01-20 2017-01-13 网络间切换的方法、装置、eMSC及SCC AS WO2017124975A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610038650.4A CN106993318A (zh) 2016-01-20 2016-01-20 网络间切换的方法、装置、eMSC及SCC AS
CN201610038650.4 2016-01-20

Publications (1)

Publication Number Publication Date
WO2017124975A1 true WO2017124975A1 (zh) 2017-07-27

Family

ID=59361467

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/071136 WO2017124975A1 (zh) 2016-01-20 2017-01-13 网络间切换的方法、装置、eMSC及SCC AS

Country Status (2)

Country Link
CN (1) CN106993318A (zh)
WO (1) WO2017124975A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112449385B (zh) * 2019-09-02 2024-03-29 中兴通讯股份有限公司 振铃前双模单待无线语音呼叫连续性的方法及装置
CN114501683A (zh) * 2020-10-23 2022-05-13 华为技术有限公司 呼叫处理方法、装置及存储介质

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101848510A (zh) * 2009-03-27 2010-09-29 中兴通讯股份有限公司 一种实现电路交换域业务的承载切换实现系统及方法
CN101909343A (zh) * 2009-06-05 2010-12-08 华为技术有限公司 一种语音切换方法和装置
CN102131264A (zh) * 2011-04-02 2011-07-20 中兴通讯股份有限公司 振铃态域切换方法及装置
CN102387117A (zh) * 2010-08-26 2012-03-21 中兴通讯股份有限公司 切换振铃态会话的方法和装置
CN102647693A (zh) * 2011-02-18 2012-08-22 中兴通讯股份有限公司 语音业务呼叫连续性实现方法和系统
WO2014124659A1 (en) * 2013-02-12 2014-08-21 Telefonaktiebolaget L M Ericsson (Publ) Technique for transferring a session with changeable session state

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102131263B (zh) * 2011-03-29 2016-08-03 中兴通讯股份有限公司 振铃态域切换的方法、系统及装置
US9526037B2 (en) * 2013-02-04 2016-12-20 Apple Inc. SRVCC handover indication for remote party to voice call

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101848510A (zh) * 2009-03-27 2010-09-29 中兴通讯股份有限公司 一种实现电路交换域业务的承载切换实现系统及方法
CN101909343A (zh) * 2009-06-05 2010-12-08 华为技术有限公司 一种语音切换方法和装置
CN102387117A (zh) * 2010-08-26 2012-03-21 中兴通讯股份有限公司 切换振铃态会话的方法和装置
CN102647693A (zh) * 2011-02-18 2012-08-22 中兴通讯股份有限公司 语音业务呼叫连续性实现方法和系统
CN102131264A (zh) * 2011-04-02 2011-07-20 中兴通讯股份有限公司 振铃态域切换方法及装置
WO2014124659A1 (en) * 2013-02-12 2014-08-21 Telefonaktiebolaget L M Ericsson (Publ) Technique for transferring a session with changeable session state

Also Published As

Publication number Publication date
CN106993318A (zh) 2017-07-28

Similar Documents

Publication Publication Date Title
CN103765844B (zh) 用于选择目标核心网络以便切换终端的语音会话的方法和节点
WO2016107161A1 (zh) 通信方法、用户设备及通信装置
CN101668273B (zh) 一种紧急业务切换方法
EP2549796B1 (en) Method and system for obtaining user equipment ability by user equipment, home subscriber data server and core network element
JP5694348B2 (ja) ハンドオーバー遅延の最適化
US20140177599A1 (en) Method and system for enabling circuit switched fallback service in evolved packet system
CN102763372B (zh) 一种异种网络切换时选择网关方法、装置及系统
JP2017108463A (ja) 進化型パケット・システムにおけるｃｓフォールバックのサポート
WO2019024677A1 (zh) 网络切换的方法、装置及系统
US8675640B2 (en) Method, apparatus, and system for connecting to called terminal
WO2015062468A1 (zh) 一种单一无线语音通话连续性切换的方法、设备及系统
EP3086581B1 (en) Call control device and method for processing user services
CN107517453A (zh) 标识信息、呼叫切换请求的发送方法及装置
WO2017054521A1 (zh) 呼叫请求重定向方法、呼叫请求接续方法及其装置
CN104429124A (zh) 从电路交换网到分组交换网的会话转移
US20130053028A1 (en) Device and method for performing an rsrvcc procedure
EP2485530B1 (en) System and method for switching ringing state session with customized alerting tone
JP5437975B2 (ja) 移動通信方法及び移動管理ノード
WO2010099741A1 (zh) 一种网络选择方法、装置及终端
WO2017124975A1 (zh) 网络间切换的方法、装置、eMSC及SCC AS
WO2016176816A1 (zh) 电路域回落的方法、网络设备和系统
WO2019029228A1 (zh) 语音业务的处理方法及装置、存储介质
CN105828399B (zh) 一种跟踪区更新方法及装置
CN109089289A (zh) 切换到电路交换域的方法和装置
WO2013064105A1 (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: 17741006

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

Country of ref document: EP

Kind code of ref document: A1