WO2011023054A1 - 一种ip多媒体子系统中多会话能力同步方法及系统 - Google Patents

一种ip多媒体子系统中多会话能力同步方法及系统 Download PDF

Info

Publication number
WO2011023054A1
WO2011023054A1 PCT/CN2010/075561 CN2010075561W WO2011023054A1 WO 2011023054 A1 WO2011023054 A1 WO 2011023054A1 CN 2010075561 W CN2010075561 W CN 2010075561W WO 2011023054 A1 WO2011023054 A1 WO 2011023054A1
Authority
WO
WIPO (PCT)
Prior art keywords
session
msc
domain
session transfer
transfer capability
Prior art date
Application number
PCT/CN2010/075561
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 WO2011023054A1 publication Critical patent/WO2011023054A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1016—IP multimedia subsystem [IMS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1083—In-session procedures
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1083—In-session procedures
    • H04L65/1095—Inter-network session transfer or sharing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/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 multi-session capability synchronization method and system in an IP multimedia subsystem.
  • IP Internet Protocol, Network Interconnection Protocol
  • Multimedia Subsystem is an IP-based network architecture proposed by the 3rd Generation Partnership Project (3GPP).
  • 3GPP 3rd Generation Partnership Project
  • IMS IP-based telecommunications network architecture, which is independent of the access technology.
  • packet access networks such as GPRS (General Packet Radio Service) and WLAN (Wireless Local Area Network).
  • WLAN Wireless Local Area Network
  • GSM Global System for Mobile communications
  • UMTS Universal Mobile Telecommunications System
  • Multi-session transfer means that in the IMS domain, a user equipment (UE) establishes a session directly with multiple users. There are one active session and multiple hold state sessions in the session, when the user equipment (UE) is due to network communication quality or other Factor, when transferred to the Circuit Switch (CS) domain, the session is not interrupted, and the technology of continuing multi-session connection is maintained.
  • UE user equipment
  • FIG. 1 shows the system reference framework for IMS multi-session transfer.
  • the entire framework includes User Equipment (UE) 101, Mobile Switch Center (MSC) 102, Media Gateway Control Function (MGCF) 103, and Media Gateway (MGW).
  • S-CSCF Service Continuity Application Server
  • the SC AS 109 provides a multimedia service continuity server, a multimedia service server, and the like, and can provide services such as multimedia service continuity and multimedia services for users.
  • the Switch, abbreviated as PS) domain and the UE-2 and UE-3 terminals have a voice session at the same time, where UE-1 and UE-3 are in an active state, and UE-1 and UE-4 are in a hold state. At this time, UE- 1 Because mobile needs to transfer multiple sessions to the circuit domain, the specific process is as follows:
  • the SC AS and the UE allocate a Transaction Identifier ( ⁇ ) for each session;
  • the UE-1 has multiple sessions, and the UE checks to transfer to the CS domain, and the UE establishes a bearer path to the destination network, and first transfers the activated session.
  • the UE-1 initiates a normal call setup process on the CS network, and sends a call setup request.
  • the called number in the Setup message is set to a statically configured session transfer number (STN) of the UE;
  • STN session transfer number
  • the MSC receives the call setup request, establishes a Session Initial Protocol (SIP) session with the SC AS according to the STN, or triggers the calling Camel process to obtain the IP Multimedia Roaming Number (IMRN) of the SC AS, and Establishing a SIP session with the SC AS according to the IMRN;
  • SIP Session Initial Protocol
  • IMRN IP Multimedia Roaming Number
  • the SC AS receives the session establishment request in step 204, and updates the remotely activated media session access address.
  • the SC AS sends the multi-session information to the MSC by using a response message, where the relationship between the Session Transfer Identifier (STI) and the UI, and the session state are included.
  • STI Session Transfer Identifier
  • the MSC After receiving the response message in step 208, the MSC sends a connection message to the UE-1.
  • the SC AS notifies the UE to release the original PS side session and bearer. 211-214, the MSC receives the response message in step 208, checks if there is a multi-session, uses the STI in the response message, and establishes a session in the hold state to the SC AS; saves the acquired TI information, and associates the session with the session;
  • the UE-1 When the UE-1 initiates the hold of the original active session, the UE-1 sends a hold message to the MSC, carrying the ⁇ that needs to be maintained;
  • the MSC finds an associated session according to the TI in the hold message, and updates the local and remote session media status to Inactive (inactive);
  • the MSC After receiving the update media response message, the MSC sends a hold response message to the UE-1.
  • UE-1 needs to activate the originally held TI2 session, UE-1 sends an activation message to the MSC, and the message includes TI2;
  • the MSC finds an associated session according to the TI2 in the hold message, and updates the local and remote session media status to Active.
  • the SC AS brings multi-session information to the MSC with the following problems:
  • step 208 the MSC Server cannot receive multi-session information, nor can it perform steps 211-214.
  • the UE cannot know that the MSC Server has failed to transfer, and believes that the transfer has succeeded, and will initiate steps 215 and 221, for example, resulting in an operation failure and a low user-risk feeling.
  • the technical problem to be solved by the present invention is to provide a multi-session capability synchronization method and system in an IP multimedia subsystem, so that the UE can perceive the network capability and avoid the handover operation failure.
  • the present invention provides a multi-session capability synchronization method in an IP multimedia subsystem, the method comprising:
  • a Mobile Switching Center or an Enhanced Mobile Switching Center (E-MSC) receives a Session Transfer Request message, Passing its own multi-session transfer capability information to the UE; After receiving the multi-session transfer capability information of the MSC or the E-MSC, the UE performs corresponding processing according to the multi-session transfer capability of the MSC or the E-MSC.
  • MSC Mobile Switching Center
  • E-MSC Enhanced Mobile Switching Center
  • the corresponding processing includes one of the following operations: switching the multi-session to the CS domain, maintaining the multi-session state; switching only the active session to the CS domain, releasing the inactive session; switching only the active session to the CS domain, retaining The inactive session is in the PS domain.
  • the step of performing corresponding processing by the UE according to the multi-session transfer capability of the MSC or the E-MSC includes: if the UE determines that the MSC or the E-MSC supports multi-session transfer, then switches the multi-session to the CS domain, and maintains Multi-session state; and if the UE determines that the MSC or E-MSC does not support multi-session transfer, then only switches the active session to the CS domain, releases the inactive session, or reserves the inactive session in the PS domain.
  • the session transfer request message is a call setup request message initiated by the UE in the circuit domain, or a handover request message sent by the mobility management entity (MME).
  • MME mobility management entity
  • the session transfer request message is a call setup request message initiated by the UE in the circuit domain
  • the MSC or the E-MSC receives the call setup request message
  • the MSC or the E-MSC is notified by a notification message.
  • the multi-session transfer capability information is delivered to the UE.
  • the notification message is a call setup response message or a message dedicated to transmitting multi-session transfer capability information.
  • the MSC or the E-MSC transmits the information of whether the multi-session transfer capability is supported to the MME by using a handover response message. And the MME transmits, by using a handover command, information about whether the MSC or the E-MSC supports the multi-session transfer capability to the UE.
  • the step of transmitting the multi-session transfer capability information of the MSC or the E-MSC to the UE comprises: when the MSC or the E-MSC supports the multi-session transfer, carrying an indication supporting the multi-session transfer capability in the message; MSC or E- When the MSC does not support multi-session transfer, the message carries an indication that does not support the multi-session transfer capability, or does not carry an indication of the multi-session transfer capability in the message.
  • the present invention further provides a multi-session capability synchronization system in an IP multimedia subsystem, which is applied to a service continuity scenario, where the system includes a mobile switching center (MSC) and a user equipment (UE), where:
  • the MSC is configured to, in the process of the UE switching from the packet switched (PS) domain to the circuit switched (CS) domain, after receiving the session transfer request message, transmitting its own multi-session transfer capability information in the session transfer response message. Passed to the UE;
  • the UE is configured to: after obtaining the multi-session transfer capability of the MSC by using the session transfer response message, according to the multi-session transfer capability of the MSC, select the following operations: switch the multi-session to the CS domain, maintain the multi-session state; or switch only the activation Session to the CS domain, release the inactive session; or switch only the active session to the CS domain, leaving the inactive session in the PS domain.
  • the present invention also provides a multi-session capability synchronization system in an IP multimedia subsystem, which is applied to a single channel voice service continuity scenario, the system including an enhanced mobile switching center (E-MSC), mobility a management entity (MME) and a user equipment (UE), wherein: the E-MSC is configured to receive a session transfer request message during handover of the UE from a packet switched (PS) domain to a circuit switched (CS) domain After that, pass the information of the multi-session transfer capability to the MME;
  • E-MSC enhanced mobile switching center
  • MME mobility a management entity
  • UE user equipment
  • the MME is configured to: pass, by using a handover command, information about whether the E-MSC supports multi-session transfer capability to the UE;
  • the UE is configured to: after learning the multi-session transfer capability of the E-MSC, according to the multi-session transfer capability of the E-MSC, select the following operations: switch the multi-session to the CS domain, maintain the multi-session state; or switch only the active session To the CS domain, release the inactive session.
  • the present invention provides a multi-session support capability synchronization technology between an MSC Server and a UE, so that the user can sense the network capability at any time during multi-session handover and make corresponding adjustments.
  • Figure 1 is a reference frame of the IMS centralized service system
  • MSC multi-session transfer process in a business continuity scenario according to an embodiment of the present invention
  • 4 is a flowchart of a scenario in which the MSC Server does not support multi-session transfer and keeps the session retained in the original PS network in the IMS multi-session transfer process of the service continuity scenario according to the embodiment of the present invention
  • 5 is a flowchart of a scenario in which an IMS Server does not support multi-session transfer and an inactive session is released during a service continuity scenario IMS multi-session transfer process according to an embodiment of the present invention
  • FIG. 6 is a reference diagram of a single channel voice service continuity (SRVCC) multi-session handover system
  • FIG. 7 is a flow chart of single channel voice service continuity multi-session handover when the E-MSC supports multi-session handover capability
  • Figure 8 is a flow chart of single channel voice service continuity multi-session switching when the E-MSC does not support multi-session handover capability.
  • the UE and the UE are not synchronized with the multi-session transfer capability, the UE and the UE are
  • the MSC Server call status is inconsistent, which reduces the user experience. Therefore, the idea of the present invention is: When the UE switches from the PS domain to the CS domain, the MSC or E-MSC (Enhanced Mobile Switching Center) receives the session transfer request message. Then, the multi-session transfer capability information is transmitted to the UE. After receiving the multi-session transfer capability information of the MSC or the E-MSC, the UE performs corresponding processing according to the multi-session transfer capability of the MSC or the E-MSC.
  • E-MSC Enhanced Mobile Switching Center
  • the following operations are selected: switching the multi-session to the CS domain, maintaining the multi-session state; or switching only the active session To the CS domain, release the inactive session; or switch only the active session to the CS domain, leaving the inactive session in the PS domain.
  • the multi-session is switched to the CS domain to maintain the multi-session state; otherwise, the UE only switches the active session to the CS domain, releases the inactive session, or retains the inactive session. PS domain.
  • the session transfer request message is a call setup request message initiated by the UE in the circuit domain or a handover request message sent by the mobility management entity (MME).
  • MME mobility management entity
  • the MSC or the E-MSC transmits its multi-session transfer capability to the UE by using a notification message.
  • the notification message may be a call setup request response message or dedicated to sending a multi-session transfer A message that shifts capability information, such as a device message.
  • the MSC or the E-MSC sends the indication of the multi-session transfer capability to the MME by using a handover response message, and the MME passes the handover request message.
  • the handover command sends an indication of the MSC or the E-MSC supporting the multi-session transfer capability to the UE.
  • the multi-session transfer capability information of the MSC or E-MSC can be transmitted to the UE in the following manner:
  • the message carries an indication supporting the multi-session transfer capability
  • the message carries an indication that does not support the multi-session transfer capability, or does not carry the multi-session transfer capability indication in the message.
  • the system implementing the above method includes an MSC and a UE, where:
  • the MSC is configured to, in the process of the UE switching from the PS domain to the CS domain, after receiving the session transfer request message, transmitting the multi-session transfer capability information to the UE in the session transfer response message;
  • the UE is configured to: after obtaining the multi-session transfer capability of the MSC by using the session transfer response message, according to the multi-session transfer capability of the MSC, select the following operations: switch the multi-session to the CS domain, maintain the multi-session state; or switch only the activation Session to the CS domain, release the inactive session; or switch only the active session to the CS domain, leaving the inactive session in the PS domain.
  • the system implementing the above method includes an enhanced mobile switching center (E-MSC), a mobility management entity (MME), and a user equipment (UE), where:
  • E-MSC enhanced mobile switching center
  • MME mobility management entity
  • UE user equipment
  • the E-MSC is configured to: when the UE switches from the PS domain to the CS domain, after receiving the session transfer request message, transmitting the multi-session transfer capability information to the MME;
  • the MME is configured to: pass, by using a handover command, information about whether the E-MSC supports multi-session transfer capability to the UE;
  • the UE is configured to: after learning the multi-session transfer capability of the E-MSC, according to the multi-session transfer capability of the E-MSC, select the following operation: switch the multi-session to the CS domain, and maintain the multi-session state; Or just switch the activation session to the cs domain and release the inactive session.
  • FIG. 3 shows a scenario in which the MSC Server supports multi-session transfer in the IMS multi-session transfer process according to the embodiment of the present invention.
  • the MSC Server receives a call setup request sent by the UE, the called message is a static STN.
  • the MSC Server sends an indication that the MSC Server supports multiple sessions to the UE by using a call response message, and the UE determines whether to retain the multi-session state according to the multi-session transfer indication in the call response message.
  • the SC AS and the UE allocate a Transaction Identifier ( ⁇ ) for each session;
  • the UE has multiple sessions, and the UE needs to be transferred to the CS domain, and the UE establishes a bearer path to the destination network, and first transfers the activated session.
  • the UE initiates a normal call setup process in the CS network, and the called number in the Setup message is set to a session transfer number (STN) that is statically configured by the UE.
  • STN session transfer number
  • the MSC Server receives the call setup request of the UE, and returns.
  • the call answering ie, the call setup request response message
  • the MSC Server brings an indication supporting the multi-session transfer capability to the UE;
  • the MSC Sever may also send an indication of the multi-session transfer capability to the terminal, such as a device message, in other messages dedicated to transmitting the multi-session transfer capability indication.
  • the UE receives the response message, and determines whether the core network supports multi-session transfer. If supported, the multi-session state is reserved.
  • the MSC Server receives the call setup request, that is, the Setup message, establishes a Session Initial Protocol (SIP) session with the SC AS according to the STN, or triggers the calling Camel process to obtain the IP multimedia roaming number of the SC AS (IMRN), and establish a SIP session with the SC AS according to the IMRN;
  • SIP Session Initial Protocol
  • the SC AS receives the session establishment request in step 306, and updates the remotely activated media session access address. 308. Initiate a re-invitation request to the remote UE-2 on the remote activation side to change the remote media access address.
  • the SC AS sends the multi-session information to the MSC server by using a response message, where the relationship between the Session Transfer Identifier (STI) and the UI, and the session state are included.
  • STI Session Transfer Identifier
  • the MSC After receiving the response message in step 310, the MSC sends a connection message to the UE-1.
  • the SC AS notifies the UE to release the original PS side session.
  • the MSC receives the response message in step 310, and checks if a multi-session exists, and uses the STI in the response message to establish a hold session to the SC AS. Save the acquired TI information, and associate the session with the session;
  • FIG. 4 shows a scenario in which the MSC server does not support multi-session transfer and keeps the session in the original PS network in the IMS multi-session transfer process of the embodiment.
  • the MSC Sever does not support multi-session transfer, and the UE keeps the held session in the original PS.
  • the SC AS and the UE allocate a Transaction Identifier ( ⁇ ) for each session;
  • the UE has multiple sessions, and the UE needs to be transferred to the CS domain, and the UE establishes a bearer path to the destination network, and first transfers the activated session.
  • the UE initiates a normal call setup process on the CS network, and the called number in the Setup message is set to a session transfer number (STN) that is statically configured by the UE;
  • STN session transfer number
  • the MSC Server receives the call setup request of the UE and returns the call response (ie, the call setup request response message)
  • the MSC Server if the MSC Server does not support the multi-session transfer, the MSC Server brings the indication that does not support the multi-session transfer capability to the UE or Do not bring the multi-session transfer capability indication to the UE;
  • the MSC Sever may also send an indication of the multi-session transfer capability to the terminal, such as a device message, in other messages dedicated to transmitting the multi-session transfer capability indication. 405.
  • the UE receives the response message, and determines whether the core network supports the multi-session transfer. If the message does not carry the indication or carries the indication that does not support the multi-session transfer capability, the active session is switched to the circuit domain, and the hold session is retained in the original PS domain. ;
  • the MSC Server receives the call setup request, that is, the Setup message, and establishes a Session Initial Protocol (SIP) session between the SC AS and the SC AS, or triggers the calling Camel process to obtain the IP multimedia roaming number of the SC AS (IMRN), and establish a SIP session with the SC AS according to the IMRN;
  • SIP Session Initial Protocol
  • the SC AS receives the session establishment request in step 406, and updates the remotely activated media session access address.
  • the SC AS returns a session response message to the MSC Server, and does not carry multi-session information.
  • the MSC After receiving the response message in step 410, the MSC sends a connection message to the UE-1. 412. The SC AS notifies the UE to update the session on the original PS side.
  • the UE-1 performs a session switching operation between the packet domain and the circuit domain.
  • Example 3
  • FIG. 5 is a scenario in which the MSC server does not support multi-session transfer and the inactive session is released in the IMS multi-session transfer process of the embodiment.
  • the MSC Sever does not support multiple sessions. Transfer, the UE releases the held session.
  • the SC AS and the UE allocate a Transaction Identifier ( ⁇ ) for each session;
  • the UE has multiple sessions, and the UE needs to be transferred to the CS domain, and the UE establishes a bearer path to the destination network, and first transfers the activated session.
  • the UE initiates a normal call setup process on the CS network, and the called number in the Setup message is set to a session transfer number (STN) that is statically configured by the UE;
  • STN session transfer number
  • the MSC Server receives a call setup request of the UE, and returns a call response (ie, call setup).
  • a call response ie, call setup.
  • the MSC Server brings an indication that does not support the multi-session transfer capability to the UE or does not bring the multi-session transfer capability indication to the UE;
  • the MSC Sever may also send an indication of the multi-session transfer capability to the terminal, such as a device message, in other messages dedicated to transmitting the multi-session transfer capability indication.
  • the UE receives the response message, and determines whether the core network supports the multi-session transfer. If not, only the active session is switched to the circuit domain, and the multi-session state is cancelled, that is, the held session is released.
  • the MSC Server receives the call setup request, that is, the Setup message, establishes a Session Initial Protocol (SIP) session with the SC AS according to the STN, or triggers the calling Camel process to obtain the IP multimedia roaming number of the SC AS (IMRN), and establish a SIP session with the SC AS according to the IMRN;
  • SIP Session Initial Protocol
  • the SC AS receives the session establishment request in step 506, and updates the remotely activated media session access address.
  • the SC AS returns a session response message to the MSC Server, and does not carry multi-session information.
  • the MSC After receiving the response message in step 510, the MSC sends a connection message to the UE-1.
  • the SC AS notifies the UE to release the original PS side session.
  • FIG. 6 is a reference diagram of a single channel voice service continuity (SRVCC) multi-session switching system.
  • SRVCC voice service continuity
  • the Evolved Universal Mobile Telecommunication System Radio Access Network can provide higher uplink and downlink rates, lower transmission delays and more reliable wireless transmission.
  • the E-UTRAN includes a network element eNodeB (Evolved NodeB) to provide radio resources for terminal access.
  • eNodeB evolved NodeB
  • Mobility Management Entity is a control plane entity. It is a server that temporarily stores user data. It is responsible for managing and storing UE context (such as UE/user ID, mobility management status, user security parameters, etc.). A temporary identifier is assigned to the user, and the user is responsible for authenticating the user when the UE is camped on the tracking area or the network.
  • the Serving Gateway is a user plane entity responsible for user plane data routing processing.
  • a packet data network gateway (PDN GW or P-GW) provides a gateway function for the UE to access a PDN (Packet Data Network).
  • PDN Packet Data Network
  • the P-GW and the S-GW may be combined in one physical entity.
  • E-MSC Enhanced MSC Server
  • SSRVCC single channel voice service continuity
  • the MSC Server receives the handover request of the MME, if the E-MSC supports the multi-session transfer capability, then E The MSC forwards the indication of the multi-session capability to the UE when the handover response message is returned, and the UE determines whether to retain the multi-session state according to the multi-session support capability in the handover command.
  • the E-UTRAN determines that the call needs to be handed over to the contiguous UTRAN network according to the radio quality report reported by the UE, and sends a handover request to the MME.
  • the MME selects the E-MSC and forwards the handover message to the E-MSC, where the message carries the source. Location information and target location information and an STN obtained by the MME when the user registers;
  • the E-MSC receives the handover message, and selects a target MSC (Target MSC) to perform inter-office handover according to the target cell in the handover message.
  • target MSC Target MSC
  • the Target MSC sends a request to the target UTRAN, assigns the base station ground circuit and the air interface resource, the allocation is completed, and the target UTRAN returns a handover response;
  • the Target MSC receives the base station handover response message, allocates a handover number, and returns a handover response message to the E-MSC.
  • the E-MSC receives the handover response, and establishes a circuit bearer according to the handover number to the Target MSC, and determines whether the E-MSC supports the multi-session. If yes, the multi-session transfer capability indication is carried in the return handover response message to the MME. 709.
  • the MME receives the handover response message, sends a handover command to the UE, and notifies the UE to perform handover, where the message carries an indication that the E-MSC supports the multi-session transfer capability.
  • the UE receives the handover command, and switches the access to the target network, and determines whether the core network supports the multi-session transfer in the handover command. If yes, the multi-session state is reserved on the UE, and multiple sessions are switched to the CS domain.
  • the E-MSC sends a session invitation message to the SC AS of the IMS network to which the user belongs according to the STN brought in the step 703, and carries the E-MSC to support the multi-session transfer capability indication and the calling number.
  • the calling number is STN, and the home network is notified to switch;
  • the UE successfully switches to the target network, and notifies that the network handover is completed;
  • the SC AS receives the session invitation, according to the calling number in the message, if it is determined that the user has multiple calls, switching the active session, sending a session re-invitation message to the remote UE, and updating the remote media;
  • the SC AS sends the multi-session information to the MSC server in the response message, where the SC AS includes the session transfer identifier STI (Session Transfer Identifier) and the corresponding Relationship, and session state;
  • STI Session Transfer Identifier
  • the E-MSC establishes a hold session to the SC AS according to the multi-session information in step 717;
  • UE-1 performs a session switching operation by using ⁇ .
  • Example 5
  • Figure 8 is the single channel voice service continuity when the E-MSC does not support multi-session switching capability.
  • the MSC Server receives the handover request from the MME, if the E-MSC does not support the multi-session handover capability, the E-MSC not indicates the multi-session capability indication when returning the handover response message.
  • the UE is brought to the UE by the handover command, and the UE determines whether to retain the multi-session state according to the multi-session support capability in the handover command.
  • the E-MSC receives the handover response, and establishes a circuit bearer according to the handover number to the Target MSC, and determines whether the E-MSC supports multiple sessions. If not, returns the handover response message to the MME. Carrying an indication that does not support multi-session transfer capability or not carrying a multi-session transfer capability indication;
  • the MME receives the handover response message, and sends a handover command to the UE to notify the UE to perform the handover.
  • the message carries the indication that the E-MSC does not support the multi-session transfer capability, or does not carry the multi-session transfer capability indication.
  • the UE receives the handover command, and switches the access to the target network, and determines, according to the handover command, whether the core network supports multi-session transfer. If not, only the active session is switched, and the multi-session state is cancelled.
  • the E-MSC sends a session invitation message to the SC AS of the IMS network to which the user belongs according to the STN brought in the step 803, and carries the indication that the E-MSC does not support the multi-session transfer capability and the calling number.
  • the called number is STN, and the home network is notified to switch.
  • the UE successfully switches to the target network, and notifies that the network handover is completed;
  • the SC AS receives the session invitation, according to the calling number in the message, if it is determined that the user has multiple calls, switching the active session, sending a session re-invitation message to the remote UE, and updating the remote media;
  • the SC AS does not support the multi-session transfer capability indication according to the E-MSC in step 811, and the SC AS does not bring the multi-session information to the MSC server in the response message.
  • the multi-session capability synchronization method and system in the IP multimedia subsystem provided by the present invention enable the UE to perceive the network capability and avoid the handover operation failure.

Abstract

本发明公开了一种IP多媒体子系统中多会话能力同步方法及系统，使UE能够感知网络能力，避免切换操作失败。所述方法包括：在用户设备（UE）从分组交换（PS）域切换到电路交换（CS）域的过程中，当移动交换中心（MSC）或增强移动交换中心（E-MSC）收到会话转移请求消息后，将自己的多会话转移能力信息传递给所述UE；以及所述UE收到MSC或E-MSC的多会话转移能力信息后，根据MSC或E-MSC的多会话转移能力，进行相应处理。

Description

一种 IP多媒体子系统中多会话能力同步方法及系统
技术领域
本发明涉及通信领域， 尤其涉及一种 IP多媒体子系统中多会话能力同步 方法及系统。
背景技术
IP ( Internet Protocol, 网络互联协议 )多媒体子系统（ IP Multimedia Core Network Subsystem, 简称 IMS )是由第三代合作伙伴计划 3GPP( 3rd Generation Partnership Project )提出的一种基于 IP的网络架构， 其构建了一个开放而灵 活的业务环境， 支持多媒体应用， 并为用户提供丰富的多媒体业务。
IMS 是基于 IP 的电信网络架构， 与接入技术无关， 除了可以为 GPRS ( General Packet Radio Service, 通用分组无线业务 )、 WLAN ( Wireless Local Area Network, 无线局域网） 等分组接入网络提供业务外， 还可以为 GSM ( Global System for Mobile communications, 全球移动通讯系统） 、 UMTS ( Universal Mobile Telecommunications System,统一移动通讯系统 )等移动虫奪 窝网络提供业务。
多会话转移是指在 IMS域中，用户设备（ UE )与多个用户直接建立会话， 这些会话中存在一个激活的会话和多个保持状态会话， 当用户设备（UE ) 因 为网络通讯质量或者其他因素， 转移到电路交换（Circuit Switch, 简称 CS ) 域时， 会话不中断， 继续保持多会话连接的技术。
图 1 示出了 IMS 多会话转移的系统参考框架。 整个框架包括用户设备 ( User Equipment , 简称 UE ) 101、 移动交换中心（ Mobile Switch Center , 简 称 MSC ) 102、 媒体网关控制功能（Media Gateway Control Function, 简称 MGCF ) 103、 媒体网关 （ Media Gateway, 简称 MGW ) 104、 代理呼叫会话 控制功能（ Proxy Call Session Control Function, 简称 P-CSCF ) 105 , 查询呼叫 会话控制功能（ Interrogating Call Session Control Function, 简称 I-CSCF ) 106, 归属用户服务器（Home Subscriber Server, 简称 HSS ) 107、 服务呼叫会话控 制功能（Serving Call Session Control Function, 简称 S-CSCF ) 108、 业务连续 性应用服务器（ Service Continuity Application Server, 简称 SC AS ) 109。
其中 SC AS 109提供包括多媒体业务连续性服务器、 多媒体业务服务器 等， 可为用户提供多媒体业务连续性、 多媒体业务等服务。
图 2是现有技术 IMS多会话转移业务流程图。 UE-1在分组交换（ Packet
Switch, 简称 PS )域与 UE-2和 UE-3两个终端同时存在语音会话， 其中 UE-1 和 UE-3处于激活状态， UE-1和 UE-4处于保持状态， 这时候， UE-1因为移 动需要把多会话转移到电路域， 具体流程如下：
201、 IMS在会话建立的过程中， SC AS和 UE为每个会话分配一个事务 标识 ( Transaction Identifier, 简称 Ή ) ；
202、 UE-1存在多个会话， UE检查需要转移到 CS域， UE向目的网络 建立承载路径， 首先转移激活的会话；
203、 UE-1在 CS网络发起正常的呼叫建立过程， 发送呼叫建立请求， 建 立 （Setup ) 消息中的被叫号码设置为 UE静态配置的会话转移号码（Session Transfer Number, STN ) ；
204、 MSC收到呼叫建立请求， 根据 STN建立与 SC AS之间的会话初始 协议（ Session Initial Protocol, 简称 SIP )会话； 或者触发主叫 Camel流程获 取 SC AS的 IP多媒体漫游号码（ IMRN ) , 并根据 IMRN建立与 SC AS的 SIP会话；
205、 SC AS收到步骤 204中的会话建立请求， 更新远端激活的媒体会话 接入地址；
206、 向远端激活侧的远端 UE-2发起重邀请请求， 更改远端媒体接入地 址；
207、 会话应答；
208、 SC AS通过应答消息把多会话信息带给 MSC, 其中包含会话转移 标识 STI ( Session Transfer Identifier )与 Ή的对应关系， 以及会话状态；
209、 MSC收到步骤 208中的应答消息后， 向 UE-1发送接通消息；
210、 SC AS通知 UE释放原来 PS侧会话和承载； 211-214、 MSC收到步骤 208中的应答消息，检查如果存在多会话， 釆用 应答消息中的 STI, 向 SC AS建立保持状态的会话； 保存获取的 TI信息， 并 关联 Ή和会话；
215、 UE-1发起对原激活会话保持时， UE-1向 MSC发送保持消息， 携 带需要保持的 Ή;
216-219、 MSC根据保持消息中的 TI找到相关联的会话， 并更新本端和 远端会话媒体状态为 Inactive (非激活 ) ；
220、 MSC收到更新媒体应答消息后， 向 UE-1发送保持应答消息；
221、 UE-1需要激活原来被保持的 TI2会话， UE-1向 MSC发送激活消 息， 消息中包含 TI2;
222-225、 MSC根据保持消息中的 TI2找到相关联的会话， 并更新本端和 远端会话媒体状态为 Active (激活 ) 。
根据对上面所描述的流程分析可知， 现有技术中， 多会话的情况下， SC AS把多会话信息带给 MSC存在如下问题：
如果用户漫游到一个不支持多会话转移能力的 MSC 服务器 （MSC
Server )管辖区域， 步骤 208中， MSC Server无法接收多会话信息， 也无法 执行步骤 211-214。 而 UE这时候无法知道 MSC Server转移失败， 还认为已 经转移成功， 将会发起例如步骤 215和 221 , 从而导致操作失败， 降低用户 体-险感受。 发明内容
本发明要解决的技术问题是提供一种 IP多媒体子系统中多会话能力同步 方法及系统， 使 UE能够感知网络能力， 避免切换操作失败。
为解决上述技术问题， 本发明提供了一种 IP多媒体子系统中多会话能力 同步方法， 所述方法包括：
在用户设备 ( UE )从分组交换（ PS )域切换到电路交换（ CS )域的过程 中， 当移动交换中心 （MSC )或增强移动交换中心 （E-MSC )收到会话转移 请求消息后， 将自己的多会话转移能力信息传递给所述 UE; 以及 所述 UE收到 MSC或 E-MSC的多会话转移能力信息后， 根据 MSC或 E-MSC的多会话转移能力， 进行相应处理。
优选地， 所述相应处理包括以下操作中的一种： 将多会话切换至 CS域， 保持多会话状态； 仅切换激活会话至 CS域， 释放非激活会话； 仅切换激活 会话至 CS域， 保留非激活会话在 PS域。
优选地， 所述 UE根据 MSC或 E-MSC的多会话转移能力， 进行相应处 理的步骤包括： 如果所述 UE判断 MSC或 E-MSC支持多会话转移， 则将多 会话切换至 CS域， 保持多会话状态； 以及如果所述 UE判断 MSC或 E-MSC 不支持多会话转移， 则仅切换激活会话至 CS域， 释放非激活会话或者保留 非激活会话在 PS域。
优选地， 所述会话转移请求消息为 UE在电路域发起的呼叫建立请求消 息， 或移动性管理实体（MME )发送的切换请求消息。
优选地， 若所述会话转移请求消息为 UE在电路域发起的呼叫建立请求 消息， 则所述 MSC或 E-MSC收到该呼叫建立请求消息后， 通过通知消息将 所述 MSC或 E-MSC的多会话转移能力信息传递给所述 UE。
优选地， 所述通知消息为呼叫建立应答消息或者专用于发送多会话转移 能力信息的消息。
优选地， 若所述会话转移请求消息为 MME发送的切换请求消息， 则所 述 MSC或 E-MSC收到该切换请求消息后， 将是否支持多会话转移能力的信 息通过切换应答消息传递给 MME,所述 MME通过切换命令将 MSC或 E-MSC 是否支持多会话转移能力的信息传递给 UE。
优选地， 所述向 UE传递 MSC或 E-MSC的多会话转移能力信息的步骤 包括： MSC或 E-MSC支持多会话转移时， 在消息中携带支持多会话转移能 力的指示； MSC或 E-MSC不支持多会话转移时， 在消息中携带不支持多会 话转移能力的指示， 或者在消息中不携带多会话转移能力的指示。
为解决上述技术问题， 本发明还提供了一种 IP多媒体子系统中多会话能 力同步系统， 应用于业务连续性场景， 所述系统包括移动交换中心 （MSC ) 和用户设备 ( UE ) , 其中： 所述 MSC, 设置为在 UE从分组交换（ PS )域切换到电路交换（ CS )域 的过程中， 当收到会话转移请求消息后， 在会话转移应答消息中将自己的多 会话转移能力信息传递给所述 UE;
所述 UE, 设置为在通过会话转移应答消息获知 MSC的多会话转移能力 后， 根据 MSC的多会话转移能力， 选择以下操作： 将多会话切换至 CS域， 保持多会话状态； 或者仅切换激活会话至 CS域， 释放非激活会话； 或者仅 切换激活会话至 CS域， 保留非激活会话在 PS域。
为解决上述技术问题， 本发明还提供了一种 IP多媒体子系统中多会话能 力同步系统， 应用于单信道语音业务连续性场景， 所述系统包括增强移动交 换中心 （E-MSC ) 、 移动性管理实体（MME )和用户设备 ( UE ) , 其中： 所述 E-MSC, 设置为在 UE从分组交换（PS )域切换到电路交换（CS ) 域的过程中， 当收到会话转移请求消息后， 将自己的多会话转移能力信息传 递给 MME;
所述 MME, 设置为通过切换命令将 E-MSC是否支持多会话转移能力的 信息传递给 UE;
所述 UE,设置为在获知 E-MSC的多会话转移能力后，根据 E-MSC的多 会话转移能力， 选择以下操作： 将多会话切换至 CS域， 保持多会话状态； 或者仅切换激活会话至 CS域， 释放非激活会话。
综上所述， 本发明提供一种 MSC Server与 UE间多会话支持能力同步技 术， 使用户在多会话切换的时， 随时感知网络能力， 并作出相应的调整。 附图概述
图 1是 IMS集中业务系统参考框架图；
图 2是现有技术中 IMS多会话转移业务流程图；
图 3是本发明实施例的业务连续性场景 IMS 多会话转移过程中， MSC
Server支持多会话转移的场景的流程图；
图 4是本发明实施例的业务连续性场景 IMS 多会话转移过程中， MSC Server不支持多会话转移， 保持会话被保留在原 PS网络的场景的流程图； 图 5是本发明实施例的业务连续性场景 IMS 多会话转移过程中， MSC Server不支持多会话转移， 非激活会话被释放的场景的流程图；
图 6是单信道语音业务连续性（SRVCC ) 多会话切换系统参考图； 图 7是 E-MSC支持多会话切换能力时单信道语音业务连续性多会话切换 的流程图；
图 8是 E-MSC不支持多会话切换能力时单信道语音业务连续性多会话切 换的流程图。
本发明的较佳实施方式
由于 UE和 MSC Server对多会话转移能力感知不同步从而导致 UE和
MSC Server呼叫状态不一致， 减低了用户体验， 因此， 本发明的构思是： 在 UE从 PS域切换到 CS域的过程中， 当 MSC或 E-MSC (增强移动交换中心） 收到会话转移请求消息后，将自己的多会话转移能力信息传递给所述 UE, 所 述 UE收到 MSC或 E-MSC的多会话转移能力信息后， 根据 MSC或 E-MSC 的多会话转移能力， 进行相应处理。
所述 UE获知 MSC或 E-MSC的多会话转移能力后，根据 MSC或 E-MSC 的多会话转移能力， 选择以下操作： 将多会话切换至 CS域， 保持多会话状 态； 或者仅切换激活会话至 CS域， 释放非激活会话； 或者仅切换激活会话 至 CS域， 保留非激活会话在 PS域。
优选地， 如果 UE判断 MSC或 E-MSC支持多会话转移， 则将多会话切 换至 CS域， 保持多会话状态； 否则 UE仅切换激活会话至 CS域， 释放非激 活会话或者保留非激活会话在原 PS域。
上述会话转移请求消息为 UE在电路域发起的呼叫建立请求消息或移动 性管理实体（MME )发送的切换请求消息。
若所述会话转移请求消息为 UE在电路域发起的呼叫建立请求消息， 所 述 MSC或 E-MSC收到该呼叫建立请求消息后， 通过通知消息将其多会话转 移能力传递给所述 UE。
所述通知消息可以是呼叫建立请求应答消息或者是专用于发送多会话转 移能力信息的消息， 例如装置消息。
若所述会话转移请求消息为 MME发送的切换请求消息， 所述 MSC或 E-MSC收到该切换请求消息后， 将支持多会话转移能力的指示通过切换应答 消息发送给 MME,所述 MME通过切换命令将 MSC或 E-MSC支持多会话转 移能力的指示发送给 UE。
向 UE传递 MSC或 E-MSC的多会话转移能力信息可釆用以下方式：
MSC或 E-MSC支持多会话转移时， 在消息中携带支持多会话转移能力 的指示；
MSC或 E-MSC不支持多会话转移时， 在消息中携带不支持多会话转移 能力的指示， 或者在消息中不携带多会话转移能力指示。
对于业务连续性（SC )场景， 实现上述方法的系统包括 MSC和 UE, 其 中：
所述 MSC,设置为在 UE从 PS域切换到 CS域的过程中， 当收到会话转 移请求消息后， 在会话转移应答消息中将自己的多会话转移能力信息传递给 所述 UE;
所述 UE, 设置为在通过会话转移应答消息获知 MSC的多会话转移能力 后， 根据 MSC的多会话转移能力， 选择以下操作： 将多会话切换至 CS域， 保持多会话状态； 或者仅切换激活会话至 CS域， 释放非激活会话； 或者仅 切换激活会话至 CS域， 保留非激活会话在 PS域。
对于单信道语音业务连续性（SRVCC )场景， 实现上述方法的系统包括 增强移动交换中心（E-MSC )、移动性管理实体（MME )和用户设备（UE ) , 其中：
所述 E-MSC, 设置为在 UE从 PS域切换到 CS域的过程中， 当收到会话 转移请求消息后， 将自己的多会话转移能力信息传递给 MME;
所述 MME, 设置为通过切换命令将 E-MSC是否支持多会话转移能力的 信息传递给 UE;
所述 UE,设置为在获知 E-MSC的多会话转移能力后，根据 E-MSC的多 会话转移能力， 选择以下操作： 将多会话切换至 CS域， 保持多会话状态； 或者仅切换激活会话至 cs域， 释放非激活会话。
下面将结合附图及实施例对本发明的技术方案进行更详细的说明。 实施例 1
图 3示出了本发明实施例的 IMS多会话转移过程中， MSC Server支持多 会话转移的场景， 当 MSC Server收到 UE发过来的呼叫建立请求， 请求消息 中，被叫号码为静态 STN时， MSC Server通过呼叫应答消息，把 MSC Server 支持多会话的指示带给 UE, UE根据呼叫应答消息中多会话转移指示决定是 否保留多会话状态。
301、 IMS在会话建立的过程中， SC AS和 UE为每个会话分配一个事务 标识 ( Transaction Identifier, 简称 Ή ) ；
302、 UE存在多个会话， UE检查需要转移到 CS域， UE向目的网络建 立承载路径， 首先转移激活的会话；
303、 UE在 CS网络发起正常的呼叫建立过程， Setup消息中的被叫号码 设置为 UE静态配置的会话转移号码（ Session Transfer Number, STN ) ； 304、 MSC Server收到 UE的呼叫建立请求， 返回呼叫应答 (即呼叫建立 请求应答消息）的时候， 如果 MSC Server支持多会话转移， MSC Server把支 持多会话转移能力的指示带给 UE;
MSC Sever也可以在其他专用于发送多会话转移能力指示的消息中将多 会话转移能力的指示发送给终端， 例如装置消息。
305、 UE收到应答消息， 判断核心网是否支持多会话转移， 如果支持， 保留多会话状态；
306、 MSC Server收到呼叫建立请求即 Setup消息， 根据 STN建立与 SC AS之间的会话初始协议（ Session Initial Protocol, 简称 SIP )会话； 或者触发 主叫 Camel流程获取 SC AS的 IP多媒体漫游号码（ IMRN ) , 并根据 IMRN 建立与 SC AS的 SIP会话；
307、 SC AS收到步骤 306中的会话建立请求， 更新远端激活的媒体会话 接入地址； 308、 向远端激活侧的远端 UE-2发起重邀请请求， 更改远端媒体接入地 址；
309、 会话应答；
310、 SC AS通过应答消息把多会话信息带给 MSC server, 其中包含会话 转移标识 STI ( Session Transfer Identifier )与 Ή的对应关系， 以及会话状态；
311、 MSC收到步骤 310中的应答消息后， 向 UE-1发送接通消息；
312、 SC AS通知 UE释放原来 PS侧会话；
313-316、 MSC收到步骤 310中的应答消息，检查如果存在多会话， 釆用 应答消息中的 STI, 向 SC AS建立保持状态的会话。 保存获取的 TI信息， 并 关联 Ή和会话；
317、 UE-1通过 Ή进行会话切换操作。 实施例 2
图 4示出了本实施例的 IMS多会话转移过程中， MSC Server不支持多会 话转移， 保持会话被保留在原 PS网络的场景， 与图 3所示实施例相比， 本实 施例中， MSC Sever不支持多会话转移， UE将保持的会话保留在原 PS中。
401、 IMS在会话建立的过程中， SC AS和 UE为每个会话分配一个事务 标识 ( Transaction Identifier, 简称 Ή ) ；
402、 UE存在多个会话， UE检查需要转移到 CS域， UE向目的网络建 立承载路径， 首先转移激活的会话；
403、 UE在 CS网络发起正常的呼叫建立过程， Setup消息中的被叫号码 设置为 UE静态配置的会话转移号码（ Session Transfer Number, STN ) ；
404、 MSC Server收到 UE的呼叫建立请求， 返回呼叫应答 (即呼叫建立 请求应答消息） 的时候， 如果 MSC Server不支持多会话转移， MSC Server 把不支持多会话转移能力的指示带给 UE或者不把多会话转移能力指示带给 UE;
MSC Sever也可以在其他专用于发送多会话转移能力指示的消息中将多 会话转移能力的指示发送给终端， 例如装置消息。 405、 UE收到应答消息， 判断核心网是否支持多会话转移， 如果消息中 没有携带指示或者携带不支持多会话转移能力的指示， 则把激活会话切换到 电路域， 把保持会话保留在原 PS域；
406、 MSC Server收到呼叫建立请求即 Setup消息， 根据 STN建立与 SC AS之间的会话初始协议（ Session Initial Protocol, 简称 SIP )会话； 或者触发 主叫 Camel流程获取 SC AS的 IP多媒体漫游号码（ IMRN ) , 并根据 IMRN 建立与 SC AS的 SIP会话；
407、 SC AS收到步骤 406中的会话建立请求， 更新远端激活的媒体会话 接入地址；
408、 向远端激活侧的远端 UE-2发起重邀请请求， 更改远端媒体接入地 址；
409、 会话应答；
410、 SC AS向 MSC Server返回会话应答消息， 不携带多会话信息；
411、 MSC收到步骤 410中的应答消息后， 向 UE- 1发送接通消息； 412、 SC AS通知 UE更新原来 PS侧的会话；
413、 UE-1在分组域和电路域间进行会话切换操作。 实施例 3
图 5是本实施例的 IMS多会话转移过程中， MSC Server不支持多会话转 移，非激活会话被释放的场景，与图 4所示实施例相比，本实例中， MSC Sever 不支持多会话转移， UE释放保持的会话。
501、 IMS在会话建立的过程中， SC AS和 UE为每个会话分配一个事务 标识 ( Transaction Identifier, 简称 Ή ) ；
502、 UE存在多个会话， UE检查需要转移到 CS域， UE向目的网络建 立承载路径， 首先转移激活的会话；
503、 UE在 CS网络发起正常的呼叫建立过程， Setup消息中的被叫号码 设置为 UE静态配置的会话转移号码（ Session Transfer Number, STN ) ；
504、 MSC Server收到 UE的呼叫建立请求， 返回呼叫应答 (即呼叫建立 请求应答消息） 的时候， 如果 MSC Server不支持多会话转移， MSC Server 把不支持多会话转移能力的指示带给 UE或者不把多会话转移能力指示带给 UE;
MSC Sever也可以在其他专用于发送多会话转移能力指示的消息中将多 会话转移能力的指示发送给终端， 例如装置消息。
505、 UE收到应答消息， 判断核心网是否支持多会话转移， 如果不支持， 仅把激活会话切换到电路域， 取消多会话状态即释放保持的会话；
506、 MSC Server收到呼叫建立请求即 Setup消息， 根据 STN建立与 SC AS之间的会话初始协议（ Session Initial Protocol, 简称 SIP )会话； 或者触发 主叫 Camel流程获取 SC AS的 IP多媒体漫游号码（ IMRN ) , 并根据 IMRN 建立与 SC AS的 SIP会话；
507、 SC AS收到步骤 506中的会话建立请求， 更新远端激活的媒体会话 接入地址；
508、 向远端激活侧的远端 UE-2发起重邀请请求， 更改远端媒体接入地 址；
509、 会话应答；
510、 SC AS向 MSC Server返回会话应答消息， 不携带多会话信息；
511、 MSC收到步骤 510中的应答消息后， 向 UE-1发送接通消息；
512、 SC AS通知 UE释放原来 PS侧会话。
图 6是单信道语音业务连续性（ SRVCC ) 多会话切换系统参考图。
演进的全球移动通信系统无线接入网 （ Evolved Universal Mobile Telecommunication System Radio Access Network, E-UTRAN ) 可以提供更高 的上下行速率， 更低的传输延迟和更加可靠的无线传输。 E-UTRAN中包含网 元 eNodeB (Evolved NodeB, 演进的 NodeB), 为终端的接入提供无线资源。
移动性管理实体 ( Mobility Management Entity, 简称 MME ) , 是一个控 制面实体， 为临时存储用户数据的服务器， 负责管理和存储 UE上下文（比 如 UE/用户标识， 移动性管理状态， 用户安全参数等） ， 为用户分配临时标 识， 当 UE驻扎在该跟踪区域或者该网络时负责对该用户进行鉴权。 服务网关（Serving Gateway, 简称 S-GW ) , 是一个用户面实体， 负责用 户面数据路由处理。
分组数据网网关 （Packet Data Network Gateway, 简称 PDN GW 或 P-GW ) , 提供 UE接入 PDN ( Packet Data Network, 分组数据网） 的网关功 能。 P-GW和 S-GW可能合设在一个物理实体中。
增强移动交换中心 （ Enhanced MSC Server, E-MSC ) , 负责电路域业务 和媒体交换控制， 这里主要用于切换， 支持与 ΜΜΕ间的 Sv口。 实施例 4
图 7是 E-MSC支持多会话切换能力时单信道语音业务连续性（ SRVCC ) 多会话切换流程图， 当 MSC Server收到 MME的切换请求时， 如果 E-MSC 支持多会话转移能力，则 E-MSC在返回切换应答消息时把支持多会话能力的 指示， 通过切换命令带给 UE, UE根据切换命令中的多会话支持能力， 判断 是否保留多会话状态。
701、 同步骤 301和 401 ;
702-703、 E-UTRAN根据 UE上报的无线质量报告， 决定需要把呼叫切 换到邻接的 UTRAN网络， 向 MME发送切换请求， MME选择 E-MSC, 向 E-MSC转发切换消息， 消息中携带源位置信息和目标位置信息和 MME在用 户注册时获取的 STN;
704、 E-MSC收到切换消息，根据切换消息中的目标小区，选择目标 MSC ( Target MSC )进行局间切换；
705-706、 Target MSC向目标 UTRAN发送请求， 指派基站地面电路和空 口资源， 分配完成， 目标 UTRAN返回切换应答；
707、 Target MSC收到基站切换应答消息， 分配切换号码， 向 E-MSC返 回切换应答消息；
708、 E-MSC收到切换应答，根据切换号码向 Target MSC建立电路承载， 判断 E-MSC是否支持多会话， 如果支持， 在向 MME返回切换应答消息中携 带多会话转移能力指示； 709、 MME收到切换应答消息， 向 UE发送切换命令， 通知 UE进行切 换 , 消息中携带 E-MSC支持多会话转移能力的指示；
710、 UE收到切换命令， 把接入切换到目标网络， 判断切换命令中核心 网是否支持多会话转移， 如果支持， 则在 UE上保留多会话状态， 将多会话 均切换到 CS域；
711、 与步骤 708同步， E-MSC根据步骤 703中带过来的 STN, 向用户 归属地 IMS网络的 SC AS发送会话邀请消息， 携带 E-MSC支持多会话转移 能力的指示和主叫号码， 被叫号码为 STN, 通知归属网络进行切换；
712-714、 UE切换到目标网络成功， 通知网络切换完成；
715-716、 SC AS收到会话邀请， 根据消息中的主叫号码， 如果判断该用 户存在多个呼叫， 切换激活状态的会话， 向远端 UE发送会话重邀请消息， 更新远端媒体；
717、 SC AS根据步骤 711中的 E-MSC支持多会话转移能力的指示， SC AS在应答消息中把多会话信息带给 MSC server, 其中包含会话转移标识 STI ( Session Transfer Identifier )与 Ή的对应关系， 以及会话状态；
718-719、 E-MSC根据步骤 717中的多会话信息， 向 SC AS建立保持会 话；
720、 UE-1通过 Ή进行会话切换操作。 实施例 5
图 8 是 E-MSC 不支持多会话切换能力时单信道语音业务连续性
( SRVCC )多会话切换流程图， 当 MSC Server收到 MME的切换请求时， 如 果 E-MSC不支持多会话转移能力， 则 E-MSC在返回切换应答消息时把不支 持多会话能力的指示， 通过切换命令带给 UE, UE根据切换命令中的多会话 支持能力， 判断是否保留多会话状态。
801-807、 同 701-707;
808、 E-MSC收到切换应答，根据切换号码向 Target MSC建立电路承载， 判断 E-MSC是否支持多会话， 如果不支持， 在向 MME返回切换应答消息中 携带不支持多会话转移能力的指示或者不携带多会话转移能力指示；
809、 MME收到切换应答消息， 向 UE发送切换命令， 通知 UE进行切 换， 消息中携带 E-MSC不支持多会话转移能力的指示， 或者不携带多会话转 移能力指示；
810、 UE收到切换命令， 把接入切换到目标网络， 根据切换命令判断核 心网是否支持多会话转移， 如果不支持， 仅切换激活会话， 取消多会话状态；
811、 与步骤 808同步， E-MSC根据步骤 803中带过来的 STN, 向用户 归属地 IMS网络的 SC AS发送会话邀请消息， 携带 E-MSC不支持多会话转 移能力的指示和主叫号码， 被叫号码为 STN, 通知归属网络进行切换；
812-814、 UE切换到目标网络成功， 通知网络切换完成；
815-816、 SC AS收到会话邀请， 根据消息中的主叫号码， 如果判断该用 户存在多个呼叫， 切换激活状态的会话， 向远端 UE发送会话重邀请消息， 更新远端媒体；
817、 SC AS根据步骤 811中的 E-MSC不支持多会话转移能力的指示， SC AS在应答消息中不把多会话信息带给 MSC server。
当然， 本发明还可有其他多种实施例， 在不背离本发明精神及其实质的 但这些相应的改变和变形都应属于本发明所附的权利要求的保护范围。
工业实用性
本发明提供的 IP多媒体子系统中多会话能力同步方法及系统， 使 UE能 够感知网络能力， 避免切换操作失败。

Claims

权 利 要 求 书
1、 一种网络互联协议（IP )多媒体子系统中多会话能力同步方法， 包括： 在用户设备 ( UE )从分组交换（ PS )域切换到电路交换（ CS )域的过程 中， 当移动交换中心 （MSC )或增强移动交换中心 （E-MSC )收到会话转移 请求消息后， 将自己的多会话转移能力信息传递给所述 UE; 以及
所述 UE收到 MSC或 E-MSC的多会话转移能力信息后， 根据 MSC或 E-MSC的多会话转移能力， 进行相应处理。
2、 如权利要求 1所述的方法，其中， 所述相应处理包括以下操作中的一 种：
将多会话切换至 CS域， 保持多会话状态；
仅切换激活会话至 CS域， 释放非激活会话；
仅切换激活会话至 CS域， 保留非激活会话在 PS域。
3、 如权利要求 2所述的方法， 其中，
所述 UE根据 MSC或 E-MSC的多会话转移能力， 进行相应处理的步骤 包括：
如果所述 UE判断 MSC或 E-MSC支持多会话转移， 则将多会话切换至 CS域， 保持多会话状态； 以及
如果所述 UE判断 MSC或 E-MSC不支持多会话转移， 则仅切换激活会 话至 CS域， 释放非激活会话或者保留非激活会话在 PS域。
4、 如权利要求 1或 2或 3所述的方法， 其中，
所述会话转移请求消息为 UE在电路域发起的呼叫建立请求消息， 或移 动性管理实体（MME )发送的切换请求消息。
5、 如权利要求 4所述的方法， 其中，
若所述会话转移请求消息为 UE在电路域发起的呼叫建立请求消息， 则 所述 MSC或 E-MSC收到该呼叫建立请求消息后，通过通知消息将所述 MSC 或 E-MSC的多会话转移能力信息传递给所述 UE。
6、 如权利要求 5所述的方法， 其中， 所述通知消息为呼叫建立应答消息或者专用于发送多会话转移能力信息 的消息。
7、 如权利要求 4所述的方法， 其中，
若所述会话转移请求消息为 MME发送的切换请求消息，则所述 MSC或 E-MSC收到该切换请求消息后， 将是否支持多会话转移能力的信息通过切换 应答消息传递给 MME,所述 MME通过切换命令将 MSC或 E-MSC是否支持 多会话转移能力的信息传递给 UE。
8、 如权利要求 1-3、 5-7中任一项所述的方法， 其中，
所述向 UE传递 MSC或 E-MSC的多会话转移能力信息的步骤包括： MSC或 E-MSC支持多会话转移时， 在消息中携带支持多会话转移能力 的指示； 以及
MSC或 E-MSC不支持多会话转移时， 在消息中携带不支持多会话转移 能力的指示， 或者在消息中不携带多会话转移能力的指示。
9、 一种网络互联协议（IP )多媒体子系统中多会话能力同步系统， 应用 于业务连续性场景， 该系统包括移动交换中心 （MSC )和用户设备 ( UE ) , 其中：
所述 MSC, 设置为在 UE从分组交换（ PS )域切换到电路交换（ CS )域 的过程中， 当收到会话转移请求消息后， 在会话转移应答消息中将自己的多 会话转移能力信息传递给所述 UE;
所述 UE, 设置为在通过会话转移应答消息获知 MSC的多会话转移能力 后， 根据 MSC的多会话转移能力， 选择以下操作： 将多会话切换至 CS域， 保持多会话状态； 或者仅切换激活会话至 CS域， 释放非激活会话； 或者仅 切换激活会话至 CS域， 保留非激活会话在 PS域。
10、 一种网络互联协议（IP ) 多媒体子系统中多会话能力同步系统， 应 用于单信道语音业务连续性场景， 该系统包括增强移动交换中心（E-MSC ) 、 移动性管理实体（MME )和用户设备 ( UE ) , 其中：
所述 E-MSC, 设置为在 UE从分组交换（PS )域切换到电路交换（CS ) 域的过程中， 当收到会话转移请求消息后， 将自己的多会话转移能力信息传 递给 MME;
所述 MME, 设置为通过切换命令将 E-MSC是否支持多会话转移能力的 信息传递给 UE;
所述 UE,设置为在获知 E-MSC的多会话转移能力后，根据 E-MSC的多 会话转移能力， 选择以下操作： 将多会话切换至 CS域， 保持多会话状态； 或者仅切换激活会话至 CS域， 释放非激活会话。
PCT/CN2010/075561 2009-08-28 2010-07-29 一种ip多媒体子系统中多会话能力同步方法及系统 WO2011023054A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200910171593.7A CN102006269B (zh) 2009-08-28 2009-08-28 一种ip多媒体子系统多会话能力同步方法及系统
CN200910171593.7 2009-08-28

Publications (1)

Publication Number Publication Date
WO2011023054A1 true WO2011023054A1 (zh) 2011-03-03

Family

ID=43627237

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2010/075561 WO2011023054A1 (zh) 2009-08-28 2010-07-29 一种ip多媒体子系统中多会话能力同步方法及系统

Country Status (2)

Country Link
CN (1) CN102006269B (zh)
WO (1) WO2011023054A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103079239A (zh) * 2011-10-26 2013-05-01 中兴通讯股份有限公司 双待终端业务连续性实现方法及系统
US10602483B2 (en) * 2014-12-12 2020-03-24 Apple Inc. Mobile terminated IMS calls on devices which support Wi-Fi and cellular radios
CN106488521B (zh) * 2016-09-23 2019-11-19 华为技术有限公司 一种呼叫处理的方法、装置、设备及系统

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101026882A (zh) * 2007-01-17 2007-08-29 华为技术有限公司 一种切换检测装置、会话切换系统及方法
CN101227647A (zh) * 2008-02-05 2008-07-23 中兴通讯股份有限公司 一种保持多媒体会话连续性业务的切换方法
CN101453706A (zh) * 2007-12-04 2009-06-10 华为技术有限公司 一种多媒体呼叫建立方法、系统和装置

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20070108427A (ko) * 2006-02-06 2007-11-12 엘지전자 주식회사 도메인 전환의 제한 방법, 그 단말 및 그 서버
CN101316435B (zh) * 2007-05-31 2012-08-08 华为技术有限公司 呼叫控制的方法和ims的电路交换控制装置及终端设备

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101026882A (zh) * 2007-01-17 2007-08-29 华为技术有限公司 一种切换检测装置、会话切换系统及方法
CN101453706A (zh) * 2007-12-04 2009-06-10 华为技术有限公司 一种多媒体呼叫建立方法、系统和装置
CN101227647A (zh) * 2008-02-05 2008-07-23 中兴通讯股份有限公司 一种保持多媒体会话连续性业务的切换方法

Also Published As

Publication number Publication date
CN102006269B (zh) 2013-10-16
CN102006269A (zh) 2011-04-06

Similar Documents

Publication Publication Date Title
EP3240257B1 (en) A domain transferring method for single radio voice call continuity
US8948127B2 (en) Method, apparatus and computer program for supporting a session identifier in case of a transfer between different radio access networks
EP2957126B1 (en) Synchronizing call states of network component and mobile device at session transfer
JP5694348B2 (ja) ハンドオーバー遅延の最適化
WO2012025007A1 (zh) 终端、hss、及核心网网元获知终端能力的方法和系统
JP2011193504A (ja) コールの継続を支援する無線通信方法およびシステム
WO2010025602A1 (zh) 紧急业务切换方法
US20150382250A1 (en) Technique for transferring a session with changeable session state
US8279832B2 (en) Method, system and device for converting session control signaling
JP6480011B2 (ja) 通信を確立するための方法及び移動無線通信ネットワーク構成要素
WO2012024908A1 (zh) 一种终端能力上报的方法及系统
WO2012041026A1 (zh) 电路交换域业务切换到分组交换域的方法及系统
WO2012149866A1 (zh) 单一无线语音呼叫连续性域的切换方法及系统
WO2011130949A1 (zh) 反向单待业务连续性实现方法及系统
WO2011023054A1 (zh) 一种ip多媒体子系统中多会话能力同步方法及系统
WO2014005525A1 (zh) 资源承载的预留方法及系统
WO2011134341A1 (zh) 反向单待业务连续性实现方法及系统
EP2232735B1 (en) Method and apparatus for inter-technology handoff of a terminating mobile station during an alerting procedure
WO2013064105A1 (zh) 一种反向单待业务连续性承载切换方法及装置
WO2012130126A1 (zh) 基于ims的控制切换方法及系统
WO2010102475A1 (zh) 终端从家庭基站切换到宏蜂窝系统保持会话的方法和系统
WO2017177427A1 (zh) 业务处理方法和相关装置及通信系统
KR101558230B1 (ko) 패킷 스위칭된 도메인으로부터 서킷 스위칭된 도메인으로 호 핸드오버 방법 및 장치
WO2012019532A1 (zh) 一种实现会话锚定的方法和系统
WO2013071897A1 (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: 10811214

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

Country of ref document: EP

Kind code of ref document: A1