WO2012024908A1 - 一种终端能力上报的方法及系统 - Google Patents

一种终端能力上报的方法及系统 Download PDF

Info

Publication number
WO2012024908A1
WO2012024908A1 PCT/CN2011/070495 CN2011070495W WO2012024908A1 WO 2012024908 A1 WO2012024908 A1 WO 2012024908A1 CN 2011070495 W CN2011070495 W CN 2011070495W WO 2012024908 A1 WO2012024908 A1 WO 2012024908A1
Authority
WO
WIPO (PCT)
Prior art keywords
base station
domain
terminal
station system
reverse single
Prior art date
Application number
PCT/CN2011/070495
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 WO2012024908A1 publication Critical patent/WO2012024908A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0022—Control or signalling for completing the hand-off for data sessions of end-to-end connection for transferring data sessions between adjacent core network technologies
    • H04W36/00224—Control or signalling for completing the hand-off for data sessions of end-to-end connection for transferring data sessions between adjacent core network technologies between packet switched [PS] and circuit switched [CS] network technologies, e.g. circuit switched fallback [CSFB]
    • H04W36/00226—Control or signalling for completing the hand-off for data sessions of end-to-end connection for transferring data sessions between adjacent core network technologies between packet switched [PS] and circuit switched [CS] network technologies, e.g. circuit switched fallback [CSFB] wherein the core network technologies comprise IP multimedia system [IMS], e.g. single radio voice call continuity [SRVCC]

Definitions

  • the present invention relates to the field of communications, and in particular, to the field of reverse single-standby service continuity operation in a multimedia protocol of the Internet Protocol (IP).
  • IP Internet Protocol
  • IP Multimedia Core Network Subsystem is an IP-based network architecture proposed by the 3rd Generation Partnership Project (3GPP) to build an open and flexible business environment. Support multimedia applications and provide users with rich multimedia services.
  • 3GPP 3rd Generation Partnership Project
  • control layer In the IMS service system, the control layer and the service layer are separated.
  • the control layer does not provide specific services, and only provides the necessary triggering, routing, and accounting functions to the service layer.
  • the service triggering and control function in the control layer is completed by the Call Session Control Function (CSCF).
  • CSCF Call Session Control Function
  • the call session control functions are divided into: proxy call session control function (Proxy-CSCF, referred to as P-CSCF), query call session control function (Interrogating-CSCF, referred to as I-CSCF) and service call session control function (Serving-CSCF, referred to as S-CSCF) three types, of which the main responsibility is S-CSCF, I-CSCF is optional.
  • the service layer is composed of a series of application servers (ASs), which can provide specific service services.
  • ASs application servers
  • the AS can be an independent entity or exist in the S-CSCF.
  • the control layer controls the service trigger according to the subscription information of the user, invokes the service on the AS, and implements the service function.
  • the end-to-end device in the session is called User Equipment (UE), which is responsible for interaction with users.
  • UE User Equipment
  • Some UEs have multiple ways to access the network, including packet switching through 3GPP (Packet Switch, PS for short).
  • the domain access network can access the network through other non-3GPP PS domains, and can even access the network through a Circuit Switch (CS) domain.
  • CS Circuit Switch
  • the eMSC provides SIP (Session Initial Protocol).
  • SIP Session Initial Protocol
  • the interface interacts with the IMS network, and the interaction between the IMS network and the CS network can be implemented by the eMSC.
  • the UE For a UE with multiple access modes, if the UE can only use one access mode at a certain time, it is performing a call service in the access mode of the 2/3G network, because the call service is at 2/3G.
  • the network is provided by the CS domain.
  • LTE Long Term Evolution
  • HSPA high speed packet access
  • the UE and the network can provide a way for the call service that the UE is performing is not interrupted, because the call service is provided by the PS domain in these networks.
  • rSRVCC reverse single-standby terminal service continuity
  • For single standby business continuity if it is the UE moving from the LTE network or the HSPA network to the 2/3G network, it is called single-standby terminal service continuity, referred to as For single standby business continuity.
  • FIG. 1 is a flow chart of a method for implementing a reverse single-standby service continuity, which describes that a call is established between UE-1 and UE-2, and UE-1 establishes a call through a CS domain of a 2/3G network, so the call is made.
  • the UE-1 is connected to the media path in the media path.
  • the process of UE-1 implementing reverse single-standby service continuity includes the following steps:
  • Step 101 The UE-1 establishes a session with the UE-2 through the CS domain and the original MSC.
  • the target MSC supports the IMS signaling but is not in the signaling path, and the session signaling path passes the service continuity (SC) AS.
  • Step 103 The base station system of the original network serving the UE-1 determines that the nearby PS target network is more suitable for serving the UE-1 according to the signal strength information of each cell in the measurement report, and then determines to perform the handover operation, and the base station system of the original network moves to the original MSC.
  • Sending a handover request such as a Handover Required message;
  • Step 104 The original MSC receives the handover request, initiates an inter-office handover process of the standard CS domain to the target MSC, and the original MSC sends a handover request to the target MSC.
  • Step 105 After step 104, the target MSC receives the handover request from the CS domain, and immediately sends a handover response to the original MSC in the CS domain, and the message arrives at the original MSC;
  • Step 106 The original MSC receives the handover response, and sends a handover command to the base station system of the original network.
  • Step 107 The base station system of the original network sends a handover command to the UE-1, requesting the UE-1 to switch to the target network.
  • Step 108 After receiving the handover command, the UE-1 modulates the access to the target network.
  • Step 109 After the step 104, the target MSC receives the handover request from the CS domain, and initiates a transfer request to the SC AS, for example, initiating an invitation (INVITE) message with the SC AS number as the target, and the message carries the media resource information of the target MSC.
  • INVITE invitation
  • the handover request further carries the handover terminal user association information, where the handover terminal user association information may be the user identification information or the number information of the UE-1, and may be derived by using the International Mobile Subscriber Identity (IMSI) in the received handover request.
  • the SC AS may determine the corresponding end user and the session to be transferred according to the handover terminal user association information.
  • Step 110 After receiving the transfer request, the SC AS determines that the remote update process needs to be initiated, and sends an update request to the UE-2, for example, sending a re-invitation (relNVITE) message, carrying the media resource information obtained in step 109, and the message arrives through the CSCF.
  • UE-2 After receiving the transfer request, the SC AS determines that the remote update process needs to be initiated, and sends an update request to the UE-2, for example, sending a re-invitation (relNVITE) message, carrying the media resource information obtained in step 109, and the message arrives through the CSCF.
  • relNVITE re-invitation
  • Step 111 The UE-2 receives the update request, and responds to the update request, for example, sends a "200 OK" message, and the message carries the media resource information of the UE-2, and the message passes through the CSCF to the SC AS;
  • Step 112 the SC AS responds to the transfer request, for example, sends a "200 OK" message, the message carries the media resource information of UE-2, and the transfer response passes through the CSCF and finally reaches the target MSC;
  • Step 113 After the step 109, the SC AS finds the terminal user identifier of the UE-1 by switching the terminal user association information, and sends the connection establishment message to the UE-1 through the PS domain, for example, sending an INVITE message, and the SC AS requests the Establishing a connection message through the target MSC, for example, setting routing information in the header field of the call message, where the routing information includes the identification information of the target MSC, and if the identification information cannot be used for the transfer request association, the SC AS also establishes the connection message. Carrying the transfer request associated information obtained in step 109;
  • Step 114 Establish a connection message to reach the target MSC, and the target MSC associates the transfer request in step 109 according to the transfer request association information, and forwards the connection establishment message to the UE-1, and the forwarding is established.
  • the connection message carries the media resource information of the target MSC;
  • the forwarded connection establishment message is rejected.
  • the operation of reestablishing the connection establishment message is retried until the The establishment of the connection message is accepted.
  • Step 115 UE-1 receives a connection establishment message, and responds to the establishment connection message, for example, sending "200"
  • the message carries the media resource information of UE-1;
  • Step 116 Establish a connection response message to pass through the target MSC, and the target MSC completes the media negotiation with the UE-1 according to the media resource information therein, and the target MSC forwards the connection establishment response message to the SC AS;
  • the IMS media connection 2 is established between the UE-1 and the target MSC, and the IMS media connection 1 is established between the target MSC and the UE-2.
  • the MSC connects the newly created IMS media connection 2 with the newly established IMS media connection 1 to enable the UE. -1 can continue to talk to UE-2.
  • the original MSC and the target MSC are the same MSC, it is basically the same as the flow of Figure 1, except that the remote update process of steps 110 and 111 is added.
  • the MSC cannot know whether the UE-1 is a UE that supports the reverse single-standby service continuity operation, that is, whether the UE-1 can answer the call of the step 115 without the intervention of the user, and therefore, if the MSC does not support
  • the UE performs the steps of step 106 115, with the result that the UE terminates the session in the target domain due to the inability to establish a connection properly.
  • the MSC should not perform the handover procedure, but should try to keep the UE in the original domain, so as to keep the session as much as possible until it is irreparable.
  • the technical problem to be solved by the present invention is to provide a method and system for reporting terminal capability, and to inform the MSC of the ability of the terminal to support reverse single-standby service continuity, and provide a basis for ensuring the success of the reverse single-standby service continuity operation.
  • the present invention provides a method for reporting terminal capability, including: receiving, by a base station system, information about a terminal supporting reverse single-standby service continuity (rSRVCC); the base station system determining to perform the terminal in circuit switching ( When the session established by the CS domain is switched to the packet switching (PS) domain, a handover request is sent to the mobile switching center (MSC), where the handover request is Carrying information reflecting that the terminal supports reverse single-standby service continuity.
  • rSRVCC reverse single-standby service continuity
  • the terminal obtains an indication of whether to allow execution of the rSRVCC through an IMS signaling interaction procedure, and determines whether to send information supporting the rSRVCC to the base station system according to the indication.
  • the terminal transmits information that supports the reverse single-standby service continuity to the base station system by establishing a process of wirelessly connecting to the base station system or by using a wireless capability message.
  • the handover request sent by the base station system to the MSC includes a target identifier used to locate the MSC location;
  • the information that the base station system carries in the handover request that reflects the continuity of the reverse single-standby service of the terminal includes: adding, by the base station system, a message field to the handover request, to indicate that the CS domain session is switched to a PS domain, or switching the CS domain session and the PS domain service to the PS domain to reflect that the terminal supports reverse single standby service continuity; or the base station system reflects the target identifier in the handover request The terminal supports reverse single standby service continuity.
  • the target identifier includes a location area identifier (LAI) or a radio area identifier (RAI); the base station system reflects that the terminal supports reverse single-standby service continuity by using LAI or RAI included in the target identifier.
  • LAI location area identifier
  • RAI radio area identifier
  • the present invention also provides a terminal capability reporting system, including a base station system and a mobile switching center (MSC), wherein:
  • the base station system is configured to: receive information that the terminal supports reverse single standby service continuity (rSRVCC);
  • the base station system is further configured to: when determining to switch the session established by the terminal in the circuit switched (CS) domain to a packet switching (PS) domain, send a handover request to the MSC, where the handover request carries
  • the terminal supports the information of reverse single-standby service continuity.
  • the above system may also have the following features: Also includes a terminal, wherein: The terminal is configured to: obtain an indication of whether to allow execution of the rSRVCC by using an IMS signaling interaction procedure, and determine, according to the indication, whether to send information supporting the rSRVCC to the base station system.
  • the terminal is configured to: send information that supports the reverse single-standby service continuity to the base station system by establishing a process of wirelessly connecting to the base station system, or by using a wireless capability message.
  • the handover request sent by the base station system to the MSC includes a target identifier used to locate the MSC location;
  • the information that the base station system carries in the handover request that reflects the continuity of the reverse single-standby service of the terminal includes: adding, by the base station system, a message field to the handover request, to indicate that the CS domain session is switched to a PS domain, or switching the CS domain session and the PS domain service to the PS domain to reflect that the terminal supports reverse single standby service continuity; or the base station system reflects the target identifier in the handover request The terminal supports reverse single standby service continuity.
  • the target identifier includes a location area identifier (LAI) or a radio area identifier (RAI); the base station system reflects that the terminal supports reverse single-standby service continuity by using LAI or RAI included in the target identifier.
  • LAI location area identifier
  • RAI radio area identifier
  • the present invention further provides a base station system for reporting terminal capability information, including a receiving module, a processing module, and a sending module that are sequentially connected, where:
  • the receiving module is configured to: receive information that the terminal supports reverse single standby service continuity (rSRVCC), and then send the information to the processing module;
  • rSRVCC reverse single standby service continuity
  • the processing module is configured to: when determining to switch the session established by the terminal in the circuit switched (CS) domain to a packet switching (PS) domain, carrying the handover request to reflect that the terminal supports reverse single standby service continuity Information, and then sending the handover request to the sending module;
  • the sending module is configured to: send a handover request sent by the processing module to a mobile switching center (MSC).
  • MSC mobile switching center
  • the above base station system can also have the following features:
  • the handover request includes a target identifier for locating the MSC location;
  • the processing module is configured to: add a message field to the handover request to indicate that the CS domain session is switched to the PS domain, or CS
  • the domain session and the PS domain service are switched to the PS domain to reflect that the terminal supports reverse single-standby service continuity; or
  • the processing module is configured to: reflect, by the target identifier in the handover request, that the terminal supports reverse single standby service continuity.
  • the above base station system can also have the following features:
  • the target identifier includes a location area identifier (LAI) or a radio area identifier (RAI); the processing module is configured to: reflect, by the LAI or RAI included in the target identifier, that the terminal supports reverse single-standby service Continuity.
  • LAI location area identifier
  • RAI radio area identifier
  • the method and system for reporting the capability of the terminal proposed by the present invention can inform the MSC of the ability of the terminal to support the reversed-waiting service continuity, and provide a basis for ensuring the success of the reverse single-standby service continuity operation.
  • the MSC can determine whether to perform the reverse single-standby service continuity operation according to the capability of the terminal to support the reverse single-standby service continuity, thereby ensuring the correctness of the terminal call service.
  • 1 is a flow chart of a method for implementing a reverse reverse single standby service continuity
  • FIG. 2 is a flowchart of a terminal capability reporting method according to an embodiment of the present invention.
  • FIG. 3 is a flow chart of reverse single-standby switching using the terminal capability reporting method of the present invention.
  • FIG. 4 is a block diagram of a terminal capability reporting system according to an embodiment of the present invention.
  • FIG. 5 is a block diagram of a base station system according to an embodiment of the present invention.
  • FIG. 6 is a base station system for reporting terminal capability information according to an embodiment of the present invention. Preferred embodiment of the invention
  • FIG. 2 the figure shows a method for reporting terminal capability according to an embodiment of the present invention.
  • An effective way to inform the MSC of its ability to support reverse single-standby service continuity provides an important basis for ensuring the success of reverse single-standby business continuity operations.
  • the reverse single-standby service continuity refers to that the terminal switches the session of the CS domain to the PS domain.
  • Step S201 The base station system receives capability information of the terminal supporting reverse single standby service continuity (rSRVCC);
  • the capability information supporting the reverse single-standby service continuity refers to capability information that supports switching the CS session to the PS domain.
  • Step S202 The base station system determines to send a handover request to the MSC when the session established by the terminal in the CS domain is switched to the PS domain, where the handover request carries information that reflects the continuity of the reverse single-standby service supported by the terminal. .
  • the terminal may send information supporting the reverse single-standby service continuity to the base station system by establishing a wireless connection between the base station systems or by using a wireless capability message.
  • the handover request sent by the base station system to the MSC includes a target identifier (Target ID), and the target identifier can be used to locate the target MSC.
  • the information that the base station system carries in the handover request to reflect the continuity of the reverse single-standby service of the terminal includes: the base station system may add a message field to the handover request to indicate that the CS domain session is switched to the PS. The domain, or the CS domain session and the PS domain service are switched to the PS domain, thereby reflecting that the terminal supports reverse single standby service continuity.
  • the base station system may also fully utilize existing fields in the target identifier in the handover request to carry information that the terminal supports reverse single-standby service continuity.
  • an idle field in the target identifier may be selected to carry information that the terminal supports reverse single-standby service continuity; or a location area identifier (LAI) or a wireless area included in the target identifier may be selected.
  • the identifier (RAI) carries information that the terminal supports reverse single-standby service continuity.
  • the MSC After receiving the handover request sent by the base station system, the MSC analyzes and determines information about the continuity of the reverse single-standby service supported by the terminal in the handover request, if the terminal supports reverse The service continuity is sent to the terminal to switch the session to the PS domain. If the terminal does not support the reverse single-standby service continuity, the terminal does not send a handover command to switch the session to the PS domain, that is, the reverse single-standby handover of the terminal is not continued, the terminal Stay in the original CS domain and try to keep the session until it is irreparable, thus maximizing the talk time.
  • the embodiment of the present invention is described in a reverse single-standby handover procedure of the terminal to which the terminal capability reporting method of the present invention is applied, as shown in the figure. 3, the figure describes that UE-1 informs the original base station system of the capability information of its support for reverse single-standby service continuity before establishing a session. After UE-1 establishes a session through the CS domain of the 2/3G network, when UE-1 The mobile station needs to change the PS domain to which the access mode is LTE or HSPA.
  • the original base station system will reflect the process of the UE-1 supporting the reverse single-standby service continuity information to the MSC, where the session establishes a media connection through the original MSC, and
  • the target MSC is not the original MSC, and includes the following steps: Step 301a: UE-1 initiates an attach procedure or a location update process by using the original network, where the process includes establishing a wireless connection with the base station system first, and establishing a wireless connection with the base station system.
  • UE-1 informs the base station system of the capability information supporting the reverse single-standby service continuity, for example, the RRC connection establishment through the resource reservation control (RRC) protocol (RRC Connection Se Tup Complete ) message carrying;
  • RRC resource reservation control
  • Step 301b After the establishment of the wireless connection is complete, the UE-1 initiates an attach request (such as an Attach Request message) or a location update request, which may be, for example, a Radio Area Update (RAU) or a Location Area Update (LAU). Request, Request Message # ⁇ Station System Forwarded to MSC.
  • an attach request such as an Attach Request message
  • a location update request which may be, for example, a Radio Area Update (RAU) or a Location Area Update (LAU).
  • RAU Radio Area Update
  • LAU Location Area Update
  • Step 302 The MSC performs a network side attach process or a location update process.
  • Step 303 After performing the network side attach procedure or the network side location update process, the MSC sends a message to the UE-1 to accept the UE-1 attached message or the location update response.
  • the original base station system sends a corresponding accept message to UE-1.
  • a corresponding accept message For example, an Attach Accept message, or a Radio Area Update Accept (RAU Accept) message or a Location Area Update Accept (LAU Accept) message.
  • RAU Accept Radio Area Update Accept
  • LAU Accept Location Area Update Accept
  • the UE-1 may also initiate a session procedure to establish a wireless connection procedure to inform the base station system of the capability information of the UE-1 supporting reverse single-standby service continuity, UE-1
  • the base station system UE-1 can also be notified to support reverse single-standby service continuity directly through a wireless capability message, such as a CLASSMARK CHANGE message, or an RRC UE Capability Information message.
  • Step 304 After the UE-1 attach or the location update succeeds, the session is initiated in the CS domain, and the session is established.
  • This step 304 is the same as step 101 in FIG. 1;
  • Step 305 UE-1 and UE-2 report the measurement report of the surrounding base station wireless signal to the original base station system during the call.
  • This step 305 is the same as step 102 in FIG. 1;
  • Step 306 After receiving the measurement report, the original base station system determines that the handover operation needs to be performed according to the signal strength and the like in the measurement report, and then sends a handover request to the original MSC, carrying information reflecting that the UE-1 supports the reverse single-standby service continuity;
  • the handover request sent by the base station system to the MSC further includes a target identifier (Target ID), where the target identifier can be used to locate the target MSC.
  • the information that the base station system carries in the handover request to reflect the continuity of the reverse single-standby service of the terminal includes: the base station system may add a message field to the handover request to indicate that the CS domain session is switched. To the PS domain, or switch the CS domain session and the PS domain service to the PS domain, thereby reflecting that the terminal supports reverse single standby service continuity.
  • the base station system may also fully utilize existing fields in the target identifier in the handover request to reflect that the terminal supports reverse single-standby service continuity.
  • a free area of the target identifier may be selected to reflect that the terminal supports reverse single-standby service continuity; and a location area identifier (LAI) or a route area identifier included in the target identifier may also be selected ( RAI), continuity.
  • LAI location area identifier
  • RAI route area identifier
  • Step 307 The original MSC sends a handover request to the target MSC, carrying the information that reflects the continuity of the reverse single-standby service of the UE-1, and the carrying mode is the same as that of the 306;
  • the handover request sent by the base station system to the MSC includes a target identifier (Target ID), where the target identifier is used to identify the location of the target MSC.
  • the original MSC locates the location of the target MSC according to the target identifier in the received handover request, and forwards the handover request thereto;
  • Step 308 The target MSC receives the handover request, and obtains information indicating that UE-1 supports reverse single-standby service continuity, so as to determine that UE-1 has the capability of supporting reverse single-standby service continuity;
  • Step 309 If the UE-1 supports the reverse single standby service continuity, the target MSC sends the original MSC to the original MSC. Send a handover response message;
  • Step 310 The target MSC performs the process of steps 109-114 in FIG. 1 while transmitting the handover response message.
  • Steps 311 to 313 The same as steps 106 to 108 of Fig. 1.
  • Step 314 Same as steps 115 to 116 of FIG.
  • UE-1 switches to the PS domain of the target network and continues to talk to UE-2 in the PS domain of the target network.
  • step 308 when it is determined that the UE-1 supports the capability of the reverse single-standby service continuity, if it is determined that the UE-1 does not support the reverse single-standby service continuity, the handover response message is not returned to the UE-1, and the reverse is ended.
  • the terminal In the single standby handover process, the terminal continues to stay in the CS domain, so as to keep the session as much as possible until it is irreparable, thereby maximizing the talk time.
  • the embodiment of the present invention is described in a reverse single-standby handover procedure of the terminal to which the terminal capability reporting method of the present invention is applied, as shown in the figure. 4.
  • the figure describes that the UE-1 informs the original base station system of its capability information supporting the reverse single-standby service continuity.
  • the UE-1 mobile needs to change the PS domain whose access mode is LTE or HSPA, it is required.
  • the original base station system When the session established by the CS domain of the 2/3G network is switched to the PS domain, the original base station system will reflect the process of the UE-1 supporting the information of the continuity of the reverse single-standby service to the MSC, where the session establishes a media connection through the original MSC. And the target MSC is not the original MSC, and includes the following steps:
  • Step 401 The UE-1 has been attached to the 2/3G access network, and the base station system UE-1 has not been notified to support the rSRVCC.
  • the UE-1 initiates an IMS registration process to the CSCF of the IMS through the original access network, for example, sending IMS signaling.
  • REGISTER message
  • Step 402 The S-CSCF in the CSCF receives the REGISTER message, and returns to agree to the registration, for example, sending a "200 OK" message, and the message may carry an indication of whether the rSRVCC is allowed to be executed;
  • Step 403 The S-CSCF initiates a third-party registration process to the AS, such as a REGISTER message that sends IMS signaling.
  • Step 404 The AS receives the REGISTER message and returns a registration response, such as sending "200 OK". Message
  • Step 405 The AS may notify the UE-1 whether the rSRVCC is allowed to be executed, for example, sending a PUBLISH message or an OPTIONS message to the UE-1 through the CSCF, and carrying an indication of whether to allow rSRVCC to be performed;
  • Step 406 If the UE-1 receives the indication that the rSRVCC is allowed to be executed, the UE directly informs the base station system that the UE-1 supports the rSRVCC, for example, sends a CLASSMARK CHANGE message, or an RRC UE Capability Information message. This step must occur in the step. Before 408;
  • Step 407 UE-1 initiates a session in the CS domain, and establishes a call connection with UE-2; this step is the same as step 101 in FIG.
  • This step can occur after step 402.
  • Steps 408-417 the same as steps 305-314 of FIG. 3;
  • UE-1 switches to the PS domain of the target network and continues to talk to UE-2 in the PS domain of the target network.
  • step 308 when it is determined that the UE-1 supports the capability of the reverse single-standby service continuity, if it is determined that the UE-1 does not support the reverse single-standby service continuity, the handover response message is not returned to the UE-1, and the reverse is ended.
  • the terminal In the single standby handover process, the terminal continues to stay in the CS domain, so as to keep the session as much as possible until it is irreparable, thereby maximizing the talk time.
  • the terminal, the MSC, and the base station system perform signaling interaction with each other, so that the process of the terminal switching the CS session to the PS domain is not limited to the manner shown in FIG.
  • Further improvement to the single-standby handover technology here only the reverse single-standby handover signaling interaction flow shown in FIG. 1 is taken as an example, and after the technical solution of the present invention is used, the reverse is shown with respect to FIG.
  • the beneficial effect of single standby switching can also be applied to the process of performing reverse single-standby handover by using other signaling interaction manners, and providing a decision basis for reverse single-standby handover.
  • the MSC performs reverse single-standby only for terminals that support reverse single-standby service continuity.
  • the embodiment of the present invention further provides a terminal capability reporting system, as shown in FIG. 5, including a terminal, a base station system, and a mobile switching center (MSC), where:
  • the base station system receives information that the terminal supports reverse single standby service continuity (rSRVCC).
  • the base station system determines to send a handover request to the MSC when the terminal establishes a session established in a circuit switched (CS) domain to a packet switched (PS) domain, where the handover request carries a reflection that the terminal supports reverse Information on business continuity.
  • rSRVCC reverse single standby service continuity
  • the terminal transmits information supporting the reverse single-standby service continuity to the base station system by establishing a process of wirelessly connecting to the base station system, or by wireless capability message.
  • the handover request sent by the base station system to the MSC includes a target identifier for locating the location of the MSC.
  • the information that the base station system carries in the handover request that reflects the continuity of the reverse single-standby service of the terminal includes: adding, by the base station system, a message field to the handover request, to indicate that the CS domain session is switched to a PS domain, or switching the CS domain session and the PS domain service to the PS domain, thereby reflecting that the terminal supports reverse single standby service continuity; or the base station system reflects the terminal by using the target identifier in the handover request Support reverse single standby business continuity.
  • the target identifier includes a location area identifier (LAI) or a wireless area identifier (RAI).
  • LAI location area identifier
  • RAI wireless area identifier
  • the embodiment of the present invention further provides a base station system for reporting terminal capability information, as shown in FIG. 6, which includes a receiving module, a processing module, and a sending module that are sequentially connected, where:
  • the receiving module is configured to receive capability information of the terminal supporting reverse single standby service continuity (rSRVCC), and then send the information to the processing module.
  • the processing module is configured to: when the session that is established by the terminal in the circuit switched (CS) domain is switched to a packet switching (PS) domain, carry the handover request to reflect that the terminal supports reverse single standby service continuity The information is then sent to the sending module.
  • CS circuit switched
  • PS packet switching
  • the sending module is configured to send a handover request sent by the processing module to a mobile switching center (MSC).
  • MSC mobile switching center
  • the handover request includes a target identifier for locating the location of the MSC.
  • the processing module adds a message field to the handover request to indicate that the CS domain session is switched to the PS domain, or the CS domain session and the PS domain service are switched to the PS domain, thereby reflecting that the terminal supports the reverse single
  • the service module is configured to reflect the continuity of the reverse single-standby service supported by the terminal by using the target identifier in the handover request.
  • the target identifier includes a location area identifier (LAI) or a wireless area identifier (RAI).
  • LAI location area identifier
  • RAI wireless area identifier
  • the method and system for reporting terminal capability by the present invention can inform the MSC of the ability of the terminal to support reversed-standby service continuity, and provide a basis for ensuring the success of the reverse single-standby service continuity operation.
  • the MSC can determine whether to perform the reverse single-standby service continuity operation according to the capability of the terminal to support the reverse single-standby service continuity, thereby ensuring the correctness of the terminal call service.

Landscapes

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

Description

一种终端能力上报的方法及系统
技术领域
本发明涉及通信领域， 尤其涉及网络互联协议 ( Internet Protocol , 简称 IP ) 多媒体子系统中反向单待业务连续性操作领域。 背景技术
IP多媒体子系统（ IP Multimedia Core Network Subsystem, 简称 IMS )是 由第三代合作伙伴计划（ 3rd Generation Partnership Project, 简称 3GPP )提出 的一种基于 IP的网络架构， 构建了一个开放而灵活的业务环境， 支持多媒体 应用， 能够为用户提供丰富的多媒体业务。
在 IMS业务体系中，控制层和业务层是分离的，控制层不提供具体业务， 只向业务层提供必要的触发、 路由、 计费等功能。
控制层中业务触发和控制功能是呼叫会话控制功能（ Call Session Control Function, 简称 CSCF ) 完成的。 呼叫会话控制功能分为： 代理呼叫会话控制 功能 ( Proxy-CSCF , 简称 P-CSCF ) 、 查询呼叫会话控制功能 ( Interrogating-CSCF,简称 I-CSCF )和服务呼叫会话控制功能（ Serving-CSCF, 简称 S-CSCF )三种类型， 其中负主要责任的是 S-CSCF, I-CSCF是可选的。
业务层是由一系列应用服务器（Application Server, 简称 AS )组成， 能 提供具体业务服务， AS可以是独立的实体， 也可以存在于 S-CSCF中。
控制层（S-CSCF )根据用户的签约信息控制业务触发， 调用 AS上的业 务， 实现业务功能。
会话中的端到端设备称为用户设备（User Equipment, 简称 UE ) , 负责 与使用者的交互，有的 UE具有多种接入网络的方式， 包括通过 3GPP的包交 换（ Packet Switch, 简称 PS )域接入网络， 通过其他非 3GPP的 PS域接入网 络， 甚至可以通过电路交换（Circuit Switch, 简称 CS )域接入网络等。
如果 CS网络配置了增强移动交换中心 （enhanced Mobile Switch Center, 简称 eMSC ) , 由 eMSC提供 SIP ( Session Initial Protocol, 初始会话协议） 接口来与 IMS网络交互， 则 IMS网络与 CS网络的交互可以通过 eMSC来实 现。
对于具有多种接入方式的 UE而言，如果该 UE某时刻只能使用一种接入 方式，则其在 2/3G网络的接入方式下正在执行通话业务， 因通话业务在 2/3G 网络中由 CS域提供，当 UE移动到其他地方而需要改变其使用的接入方式为 长期演进（ Long Term Evolution, LTE )网络或高速分组接入 ( high speed packet access , HSPA ) 网络接入时， UE和网络能提供某种方式使 UE正在执行的 通话业务不被中断， 因通话业务在这些网络中由 PS域提供， 这样的能力我们 称之为反向单待终端业务连续性， 简称反向单待业务连续性（reverse Single Radio Voice Call Continuity, rSRVCC ) , 与之相对应的， 如果是 UE从 LTE 网络或 HSPA网络移动到 2/3G网络则称之为单待终端业务连续性，简称为单 待业务连续性。
图 1是现有的反向单待业务连续性实现方法流程图，描述了 UE-1和 UE-2 间建立了通话， UE-1是通过 2/3G网络的 CS域建立通话的， 因此通话媒体路 径中连接 UE-1的是一段 CS媒体连接， 当 UE-1移动需要改变其使用的接入 方式为 LTE或 HSPA的 PS域，后续会话通过目标 MSC的媒体锚定建立媒体 连接，且目标 MSC不是原 MSC的情况下， UE-1实现反向单待业务连续性的 过程包括如下步骤：
步骤 101 : UE-1通过 CS域及原 MSC与 UE-2建立会话， 目标 MSC支 持 IMS信令但不在信令路径中， 会话信令路径途经业务连续性（SC ) AS; 步骤 102: UE-1向为其服务的原网络发送测量报告， 以上报小区信号强 度测量信息；
步骤 103: 为 UE-1服务的原网络的基站系统根据测量报告中各小区信号 强度信息判断附近的 PS目标网络更适合为 UE-1服务， 于是决定执行切换操 作，原网络的基站系统向原 MSC发送切换请求，比如发送切换请求（ Handover required ) 消息；
步骤 104:原 MSC收到切换请求，向目标 MSC发起标准的 CS域的局间 切换过程， 原 MSC向目标 MSC发送切换请求； 步骤 105: 步骤 104后， 目标 MSC收到来自 CS域的切换请求， 立即向 CS域的原 MSC发送切换响应， 消息到达原 MSC;
步骤 106: 原 MSC收到切换响应， 向原网络的基站系统发送切换命令； 步骤 107: 原网络的基站系统向 UE-1发送切换命令， 要求 UE-1切换到 目标网络；
步骤 108: UE-1收到切换命令后， 调制到目标网络接入；
步骤 109:步骤 104后， 目标 MSC收到来自 CS域的切换请求，向 SC AS 发起转移请求， 比如以 SC AS的号码为目标发起邀请 ( INVITE )消息， 消息 携带目标 MSC的媒体资源信息。
转移请求中还携带切换终端用户关联信息， 其中切换终端用户关联信息 可以是 UE- 1的用户标识信息或号码信息 ,可以通过收到的切换请求中的国际 移动用户识别码（ IMSI )推导出来， SC AS可以根据切换终端用户关联信息 确定对应的终端用户及需要转移的会话。
步骤 110: SC AS收到转移请求后，判断需要发起远端更新流程，向 UE-2 发送更新请求， 比如发送重邀请 ( relNVITE ) 消息， 携带步骤 109中获得的 媒体资源信息， 消息途经 CSCF到达 UE-2;
步骤 111 : UE-2收到更新请求， 响应更新请求， 比如发送 "200 OK" 消 息， 消息携带 UE-2的媒体资源信息， 消息途经 CSCF到达 SC AS;
步骤 112、 SC AS响应转移请求， 比如发送 "200 OK" 消息， 消息中携 带 UE-2的媒体资源信息， 转移响应途经 CSCF最终到达目标 MSC;
步骤 113:在步骤 109之后， SC AS通过切换终端用户关联信息找到 UE-1 的终端用户标识， 以该终端标识通过 PS域向 UE-1发送建立连接消息， 比如 发送 INVITE消息， SC AS要求该建立连接消息途经目标 MSC, 比如在呼叫 消息的头域中设置路由信息，路由信息中包括目标 MSC的标识信息，如果该 标识信息不能用于转移请求关联， 则 SC AS还要在该建立连接消息中携带步 骤 109中获得的转移请求关联信息；
步骤 114: 建立连接消息到达目标 MSC, 目标 MSC根据转移请求关联 信息关联步骤 109中的转移请求， 并转发建立连接消息给 UE-1 , 在转发的建 立连接消息中携带目标 MSC的媒体资源信息；
如果 UE-1此时尚未完成接入目标网络的操作，转发的建立连接消息会被 拒绝， 当目标 MSC收到转发的建立连接消息的拒绝消息后， 重试转发建立连 接消息的操作， 直到该建立连接消息被接受。
步骤 115: UE-1收到建立连接消息，应答该建立连接消息，比如发送 "200
OK" 消息， 消息携带 UE-1的媒体资源信息；
步骤 116: 建立连接应答消息途经目标 MSC, 目标 MSC根据其中的媒 体资源信息完成与 UE-1的媒体协商，目标 MSC转发建立连接应答消息给 SC AS;
至此， UE-1与目标 MSC间建立起 IMS媒体连接 2, 目标 MSC与 UE-2 间建立起 IMS媒体连接 1 , MSC将新建的 IMS媒体连接 2与新建的 IMS媒 体连接 1接起来， 使 UE-1能继续与 UE-2通话。
此例中，如果原 MSC与目标 MSC为同一个 MSC, 则基本与图 1流程相 同， 只是多了步骤 110和 111的远端更新流程。
现有技术中， MSC无法知道 UE-1是否是支持反向单待业务连续性操作 的 UE, 即 UE-1是否能在没有用户的干预下应答步骤 115的呼叫， 因此， 如 果 MSC对于不支持的 UE执行了步骤 106 115的步骤， 其结果是导致 UE在 目标域因无法正确建立连接而使会话终止。 对于这样的 UE, MSC不应该执 行切换过程， 而应尽量使 UE待在原域中， 从而尽量保持会话直到无可挽救。
发明内容
本发明所要解决的技术问题是， 提供一种终端能力上报的方法及系统， 将终端支持反向单待业务连续性的能力告知 MSC, 为确保反向单待业务连续 性操作的成功提供依据。
为了解决上述问题， 本发明提供了一种终端能力上报的方法， 包括： 基站系统接收终端支持反向单待业务连续性（rSRVCC ) 的信息； 所述基站系统决定将所述终端在电路交换（CS )域建立的会话切换到包 交换（PS )域时， 向移动交换中心 （MSC )发送切换请求， 所述切换请求中 携带反映所述终端支持反向单待业务连续性的信息。
上述方法还可具有以下特点：
所述终端通过 IMS信令交互过程获得是否允许执行 rSRVCC的指示， 并 根据所述指示决定是否发送支持 rSRVCC的信息给所述基站系统。
上述方法还可具有以下特点：
所述终端通过建立与基站系统间无线连接的过程，或通过无线能力消息， 将自身支持反向单待业务连续性的信息发送至所述基站系统。
所述基站系统发送给所述 MSC的切换请求中包含用以定位所述 MSC位 置的目标标识；
所述基站系统在所述切换请求中携带反映所述终端支持反向单待业务连 续性的信息包括： 所述基站系统在所述切换请求中增加一消息字段， 以指示 将 CS域会话切换到 PS域， 或将 CS域会话和 PS域业务切换到 PS域， 以反 映所述终端支持反向单待业务连续性； 或者， 所述基站系统以所述切换请求 中的目标标识来反映所述终端支持反向单待业务连续性。
上述方法还可具有以下特点：
所述目标标识中包含位置区域标识（ LAI )或无线区域标识（ RAI ) ； 所述基站系统是以所述目标标识中包含的 LAI或 RAI来反映所述终端支 持反向单待业务连续性。
为了解决上述技术问题， 本发明还提出一种终端能力上报系统， 包含基 站系统和移动交换中心 （MSC ) , 其中：
所述基站系统设置为： 接收终端支持反向单待业务连续性（rSRVCC )的 信息；
所述基站系统还设置为： 决定将所述终端在电路交换（CS )域建立的会 话切换到包交换（PS )域时， 向所述 MSC发送切换请求， 所述切换请求中 携带反映所述终端支持反向单待业务连续性的信息。
上述系统还可具有以下特点： 还包括终端， 其中： 所述终端设置为： 通过 IMS信令交互过程获得是否允许执行 rSRVCC的 指示， 并根据所述指示决定是否发送支持 rSRVCC的信息给所述基站系统。
所述终端设置为： 通过建立与基站系统间无线连接的过程， 或通过无线 能力消息， 将自身支持反向单待业务连续性的信息发送至所述基站系统。
上述系统还可具有以下特点：
所述基站系统发送给所述 MSC的切换请求中包含用以定位所述 MSC位 置的目标标识；
所述基站系统在所述切换请求中携带反映所述终端支持反向单待业务连 续性的信息包括： 所述基站系统在所述切换请求中增加一消息字段， 以指示 将 CS域会话切换到 PS域， 或将 CS域会话和 PS域业务切换到 PS域， 以反 映所述终端支持反向单待业务连续性； 或者， 所述基站系统以所述切换请求 中的目标标识来反映所述终端支持反向单待业务连续性。
上述系统还可具有以下特点：
所述目标标识中包含位置区域标识（ LAI )或无线区域标识（ RAI ) ； 所述基站系统是以所述目标标识中包含的 LAI或 RAI来反映所述终端支 持反向单待业务连续性。
为了解决上述技术问题， 本发明还提出一种上报终端能力信息的基站系 统， 包括依次相连的接收模块、 处理模块和发送模块， 其中：
所述接收模块设置为： 接收终端支持反向单待业务连续性（ rSRVCC )的 信息， 然后将其发送至所述处理模块；
所述处理模块设置为： 在决定将所述终端在电路交换（CS )域建立的会 话切换到包交换（PS )域时， 在切换请求中携带反映所述终端支持反向单待 业务连续性的信息， 然后将所述切换请求发送至所述发送模块；
所述发送模块设置为： 将所述处理模块发送来的切换请求发送至移动交 换中心 （MSC ) 。
上述基站系统还可具有以下特点： 所述切换请求中包含用以定位所述 MSC位置的目标标识； 所述处理模块是设置为： 在所述切换请求中增加一消息字段， 以指示将 CS域会话切换到 PS域， 或将 CS域会话和 PS域业务切换到 PS域， 以反映 所述终端支持反向单待业务连续性； 或者，
所述处理模块是设置为： 以所述切换请求中的目标标识来反映所述终端 支持反向单待业务连续性。
上述基站系统还可具有以下特点：
所述目标标识中包含位置区域标识（ LAI )或无线区域标识（ RAI ) ； 所述处理模块是设置为： 以所述目标标识中包含的 LAI或 RAI来反映所 述终端支持反向单待业务连续性。
釆用本发明提出的终端能力上报的方法及系统， 能够将终端支持反向单 待业务连续性的能力告知 MSC, 为确保反向单待业务连续性操作的成功提供 依据。 MSC则可以根据终端支持反向单待业务连续性的能力来判断是否执行 反向单待业务连续性操作， 从而确保终端呼叫业务的正确性。 附图概述
图 1是现有反向单待业务连续性实现方法流程图；
图 2是本发明实施例一种终端能力上报方法流程图；
图 3是应用本发明终端能力上报方法的反向单待切换流程图；
图 4是本发明实施例一种终端能力上报系统方框图；
图 5是本发明实施例一种基站系统方框图；
图 6是本发明实施例一种上报终端能力信息的基站系统。 本发明的较佳实施方式
下面将结合附图对本发明实施方式做进一步说明。
参见图 2, 该图示出了本发明实施例一种终端能力上报的方法， 提供一 种有效的方式， 令终端将其支持反向单待业务连续性的能力告知 MSC, 为确 保反向单待业务连续性操作的成功提供重要依据。 所述反向单待业务连续性 是指终端将 CS域的会话切换到 PS域。
步骤 S201 : 基站系统接收终端支持反向单待业务连续性（rSRVCC ) 的 能力信息；
所述支持反向单待业务连续性的能力信息是指支持将 CS会话切换到 PS 域的能力信息。
步骤 S202: 所述基站系统决定将所述终端在 CS域建立的会话切换到 PS 域时， 向 MSC发送切换请求， 所述切换请求中携带反映所述终端支持反向单 待业务连续性的信息。
所述终端可以通过建立于基站系统间无线连接的过程或者通过无线能力 消息 , 将其支持反向单待业务连续性的信息发送至所述基站系统。
所述基站系统发送给所述 MSC的切换请求中包含目标标识（ Target ID ) , 所述目标标识可用于定位目标 MSC。 所述基站系统在所述切换请求中携带反 映终端支持反向单待业务连续性的信息包括： 所述基站系统可以在所述切换 请求中增加一消息字段， 以指示将 CS域会话切换到 PS域， 或将 CS域会话 和 PS域业务切换到 PS域， 从而反映所述终端支持反向单待业务连续性。 或 者， 所述基站系统也可以充分利用所述切换请求中的目标标识中的已有字段 来承载所述终端支持反向单待业务连续性的信息。 具体来说， 可以选取所述 目标标识中的一空闲字段来承载所述终端支持反向单待业务连续性的信息； 也可以选取所述目标标识中包含的位置区域标识 （ LAI ) 或无线区域标识 ( RAI )来承载所述终端支持反向单待业务连续性的信息。
所述 MSC在接收到所述基站系统发送来的所述切换请求后，解析判断所 述切换请求中携带的所述终端支持反向单待业务连续性的信息， 如果所述终 端支持反向单待业务连续性，才向所述终端发送将会话切换到 PS域的切换命 令。 如果所述终端不支持反向单待业务连续性， 则不向所述终端发送将会话 切换到 PS域的切换命令， 即， 不再继续执行所述终端的反向单待切换， 所述 终端继续待在原 CS域中， 从而尽量保持会话直到无可挽救， 从而尽量延长 了通话时间。 为了进一步说明本发明对确保终端反向单待切换的正确性做出的贡献， 本发明实施例以一种应用了本发明终端能力上报的方法的终端反向单待切换 过程进行说明， 参见图 3 , 该图描述了 UE-1在建立会话前将其支持反向单待 业务连续性的能力信息告知原基站系统， UE-1通过 2/3G网络的 CS域建立会 话后， 当 UE-1移动需要改变其使用的接入方式为 LTE或 HSPA的 PS域， 原 基站系统将反映 UE-1支持反向单待业务连续性的信息告知 MSC的过程， 其 中会话通过原 MSC建立媒体连接，且目标 MSC不是原 MSC,包括如下步骤： 步骤 301a: UE-1通过原网络发起附着过程或位置更新过程，其中包括先 与基站系统建立无线连接的过程，在与基站系统建立无线连接的过程中 , UE-1 将支持反向单待业务连续性的能力信息告知基站系统， 比如通过资源预留控 制 （ RRC )协议的 RRC连接建立完成（ RRC Connection Setup Complete ) 消 息携带；
步骤 301b:无线连接建立完成后， UE-1发起附着请求（比如 Attach Request 消息）或位置更新请求，可以是例如无线区域更新（ Radio Area Update, RAU ) 或位置区域更新 （ Location Area Update, LAU )请求， 请求消息# ^站系 统转发给 MSC。
步骤 302: MSC执行网络侧附着过程或位置更新过程；
步骤 303: MSC执行完网络侧的附着过程或网络侧位置更新过程后， 向 UE-1发送接受 UE-1的附着的消息或位置更新响应的消息；
根据步骤 301b中 UE-1 向原基站系统发送的请求， 原基站系统向 UE-1 发送相应的接受消息。 比如， 发送附着接受 （Attach Accept ) 消息， 或无线 区域更新接受（ RAU Accept )消息或位置区域更新接受（ LAU Accept )消息。
除了执行附着过程或位置更新过程时建立无线连接外， UE-1还可以发起 会话过程时的建立无线连接过程将 UE-1 支持反向单待业务连续性的能力信 息告诉基站系统， UE-1 还可直接通过无线能力消息， 比如 CLASSMARK CHANGE消息， 或 RRC UE Capability Information消息通知基站系统 UE-1支 持反向单待业务连续性。
步骤 304: UE-1附着或位置更新成功后， 在 CS域发起会话， 建立了与 UE-2的通话连接；
该步骤 304与图 1中的步骤 101相同；
步骤 305: UE-1与 UE-2在通话过程中， UE-1向原基站系统上报了对周 围基站无线信号的测量报告；
该步骤 305与图 1中的步骤 102相同；
步骤 306: 原基站系统收到测量报告后， 根据测量报告中的信号强度等 信息判断需要执行切换操作， 于是向原 MSC发送切换请求， 携带反映 UE-1 支持反向单待业务连续性的信息；
所述基站系统发送给所述 MSC 的切换请求中还包含目标标识 （Target ID ) , 所述目标标识可用于定位目标 MSC。 所述基站系统在所述切换请求中 携带反映所述终端支持反向单待业务连续性的信息包括： 所述基站系统可以 在所述切换请求中增加一消息字段， 以指示将 CS域会话切换到 PS域， 或将 CS域会话和 PS域业务切换到 PS域，从而反映所述终端支持反向单待业务连 续性。 或者， 所述基站系统也可以充分利用所述切换请求中的目标标识中的 已有字段来反映所述终端支持反向单待业务连续性。 具体来说， 可以选取所 述目标标识中的一空闲区域来反映所述终端支持反向单待业务连续性； 也可 以选取所述目标标识中包含的位置区域标识（ LAI )或路由区域标识（ RAI ) , 续性。
步骤 307: 原 MSC向目标 MSC发送切换请求，携带反映 UE-1支持反向 单待业务连续性的信息， 携带方式与 306相同；
所述基站系统发送给所述 MSC的切换请求中包含目标标识（ Target ID ) , 所述目标标识用以标识目标 MSC的位置。 原 MSC是根据接收到的切换请求 中的目标标识定位出目标 MSC的位置， 并向其转发所述切换请求；
步骤 308: 目标 MSC收到所述切换请求， 从中获取反映 UE-1支持反向 单待业务连续性的信息， 从而判断出 UE-1 有支持反向单待业务连续性的能 力；
步骤 309: 如果 UE-1支持反向单待业务连续性， 则目标 MSC向原 MSC 发送切换响应消息；
步骤 310: 目标 MSC在发送切换响应消息的同时， 执行图 1 中的步骤 109-114的过程。
步骤 311~313： 与图 1的步骤 106~108相同。
步骤 314: 与图 1的步骤 115~116相同。
至此， UE-1切换到目标网络的 PS域， 在目标网络的 PS域继续与 UE-2 通话。
步骤 308在判断 UE-1支持反向单待业务连续性的能力信息时，如果判断 出 UE-1不支持反向单待业务连续性， 则不向 UE-1返回切换响应消息， 结束 反向单待切换流程， 所述终端继续待在 CS域中， 从而尽量保持会话直到无 可挽救， 从而尽量延长了通话时间。
为了进一步说明本发明对确保终端反向单待切换的正确性做出的贡献， 本发明实施例以一种应用了本发明终端能力上报的方法的终端反向单待切换 过程进行说明， 参见图 4, 该图描述了 UE-1将其支持反向单待业务连续性的 能力信息告知原基站系统， 当 UE-1移动需要改变其使用的接入方式为 LTE 或 HSPA的 PS域， 从而需要将通过 2/3G网络的 CS域建立的会话切换到 PS 域时， 原基站系统将反映 UE-1支持反向单待业务连续性的信息告知 MSC的 过程， 其中会话通过原 MSC建立媒体连接， 且目标 MSC不是原 MSC, 包括 如下步骤：
步骤 401： UE-1 已经附着到了 2/3G接入网络， 尚未通知基站系统 UE-1 支持 rSRVCC, UE-1通过原接入网络向 IMS的 CSCF发起 IMS的注册过程， 比如发送 IMS信令的 REGISTER消息；
步骤 402: CSCF中的 S-CSCF接收到 REGISTER消息， 返回同意注册， 比如发送 "200 OK" 消息， 消息可携带是否允许执行 rSRVCC的指示；
步骤 403: S-CSCF向 AS发起第三方注册过程， 比如发送 IMS信令的 REGISTER消息；
步骤 404: AS收到 REGISTER消息，返回注册响应， 比如发送 "200 OK" 消息；
步骤 405: AS可以向 UE-1通知是否允许执行 rSRVCC, 比如通过 CSCF 向 UE-1发送 PUBLISH消息或 OPTIONS消息， 携带是否允许执行 rSRVCC 的指示；
步骤 406: UE-1如果收到允许执行 rSRVCC的指示， 则通知直接发送无 线能力消息通知基站系统 UE-1 支持 rSRVCC , 比如发送 CLASSMARK CHANGE消息， 或 RRC UE Capability Information消息， 该步骤必须发生在 步骤 408之前；
步骤 407: UE-1在 CS域发起会话， 建立了与 UE-2的通话连接； 该步骤与图 1中的步骤 101相同。
该步骤可以发生在步骤 402之后。
步骤 408-417: 与图 3的步骤 305-314相同；
至此， UE-1切换到目标网络的 PS域， 在目标网络的 PS域继续与 UE-2 通话。
步骤 308在判断 UE-1支持反向单待业务连续性的能力信息时，如果判断 出 UE-1不支持反向单待业务连续性， 则不向 UE-1返回切换响应消息， 结束 反向单待切换流程， 所述终端继续待在 CS域中， 从而尽量保持会话直到无 可挽救， 从而尽量延长了通话时间。
对于反向单待切换技术而言， 终端、 MSC与基站系统彼此之间进行信令 交互， 使得终端将 CS会话切换到 PS域的流程并不限于图 1所示方式， 为了 说明本发明对于反向单待切换技术所做的进一步完善， 此处仅以图 1所示反 向单待切换信令交互流程为例， 说明釆用了本发明技术方案后， 相对于图 1 所示的反向单待切换的有益效果。 本发明还可以应用至釆用其他信令交互方 式完成反向单待切换的过程， 为反向单待切换提供决策依据， MSC只对支持 反向单待业务连续性的终端执行反向单待切换， 对于不支持反向单待业务连 续性的终端则拒绝切换， 令所述终端继续待在原域中， 从而尽量保持会话直 到无可挽救， 从而尽量延长了通话时间， 避免了对不支持反向单待业务连续 性的终端进行切换会造成终端在目标域无法正确建立连接而使会话终止的问 题， 提高了反向单待切换的成功率。
本发明实施例还提供了一种终端能力上报系统， 如图 5所示， 包含终端、 基站系统和移动交换中心 （MSC ) , 其中：
所述基站系统接收终端支持反向单待业务连续性（rSRVCC )的信息。 所 述基站系统决定将所述终端在电路交换（CS )域建立的会话切换到包交换 ( PS )域时， 向所述 MSC发送切换请求， 所述切换请求中携带反映所述终 端支持反向单待业务连续性的信息。
所述终端通过 IMS信令交互过程获得是否允许执行 rSRVCC的指示， 并 根据所述指示决定是否发送支持 rSRVCC的能力信息给所述基站系统。
终端通过通过建立与基站系统间无线连接的过程， 或者通过无线能力消 息， 将其支持反向单待业务连续性的信息发送至所述基站系统。
所述基站系统发送给所述 MSC的切换请求中包含用以定位所述 MSC位 置的目标标识。
所述基站系统在所述切换请求中携带反映所述终端支持反向单待业务连 续性的信息包括： 所述基站系统在所述切换请求中增加一消息字段， 以指示 将 CS域会话切换到 PS域， 或将 CS域会话和 PS域业务切换到 PS域， 从而 反映所述终端支持反向单待业务连续性； 或者所述基站系统以所述切换请求 中的目标标识来反映所述终端支持反向单待业务连续性。
所述目标标识中包含位置区域标识（ LAI )或无线区域标识（ RAI ) 。 所述基站系统是以所述目标标识中包含的 LAI或 RAI来反映所述终端支 持反向单待业务连续性。
本发明实施例还提供了一种上报终端能力信息的基站系统，如图 6所示， 包括依次相连的接收模块、 处理模块和发送模块， 其中：
所述接收模块， 用以接收终端支持反向单待业务连续性（rSRVCC )的能 力信息， 然后将其发送至所述处理模块。 所述处理模块， 用以在决定将所述终端在电路交换（CS )域建立的会话 切换到包交换（PS )域时， 在切换请求中携带反映所述终端支持反向单待业 务连续性的信息 , 然后将所述切换请求发送至所述发送模块。
所述发送模块， 用以将所述处理模块发送来的切换请求发送至移动交换 中心 （MSC ) 。
所述切换请求中包含用以定位所述 MSC位置的目标标识。
所述处理模块是在所述切换请求中增加一消息字段， 以指示将 CS域会 话切换到 PS域， 或将 CS域会话和 PS域业务切换到 PS域， 从而反映所述终 端支持反向单待业务连续性； 或者， 所述处理模块是以所述切换请求中的目 标标识来反映所述终端支持反向单待业务连续性。
所述目标标识中包含位置区域标识（ LAI )或无线区域标识（ RAI ) 。 所述处理模块是以所述目标标识中包含的 LAI或 RAI来反映所述终端支 持反向单待业务连续性。
当然， 本发明还可有其他多种实施例， 在不背离本发明精神及其实质的 但这些相应的改变和变形都应属于本发明所附的权利要求的保护范围。
工业实用性 釆用本发明提出的终端能力上报的方法及系统， 能够将终端支持反向单 待业务连续性的能力告知 MSC, 为确保反向单待业务连续性操作的成功提供 依据。 MSC则可以根据终端支持反向单待业务连续性的能力来判断是否执行 反向单待业务连续性操作， 从而确保终端呼叫业务的正确性。

Claims

权 利 要 求 书
1、 一种终端能力上报的方法， 包括：
基站系统接收终端支持反向单待业务连续性（rSRVCC ) 的信息； 所述基站系统决定将所述终端在电路交换（CS )域建立的会话切换到包 交换（PS )域时， 向移动交换中心 （MSC )发送切换请求， 所述切换请求中 携带反映所述终端支持反向单待业务连续性的信息。
2、 如权利要求 1所述的方法， 其特征在于， 还包括：
所述终端通过 IMS信令交互过程获得是否允许执行 rSRVCC的指示， 并 根据所述指示决定是否发送支持 rSRVCC的信息给所述基站系统。
3、 如权利要求 1所述的方法， 其中， 所述方法还包括：
所述终端通过建立与基站系统间无线连接的过程，或通过无线能力消息， 将自身支持反向单待业务连续性的信息发送至所述基站系统。
4、 如权利要求 1所述的方法， 其中，
所述基站系统发送给所述 MSC的切换请求中包含用以定位所述 MSC位 置的目标标识；
所述基站系统在所述切换请求中携带反映所述终端支持反向单待业务连 续性的信息包括： 所述基站系统在所述切换请求中增加一消息字段， 以指示 将 CS域会话切换到 PS域， 或将 CS域会话和 PS域业务切换到 PS域， 以反 映所述终端支持反向单待业务连续性； 或者， 所述基站系统以所述切换请求 中的目标标识来反映所述终端支持反向单待业务连续性。
5、 如权利要求 4所述的方法， 其中，
所述目标标识中包含位置区域标识（ LAI )或无线区域标识（ RAI ) ； 所述基站系统是以所述目标标识中包含的 LAI或 RAI来反映所述终端支 持反向单待业务连续性。
6、 一种终端能力上报系统， 包括基站系统和移动交换中心 （MSC ) 其中：
所述基站系统设置为： 接收终端支持反向单待业务连续性（rSRVCC )的 信息；
所述基站系统还设置为： 决定将所述终端在电路交换（CS )域建立的会 话切换到包交换（PS )域时， 向所述 MSC发送切换请求， 所述切换请求中 携带反映所述终端支持反向单待业务连续性的信息。
7、 如权利要求 6所述的系统，其中，所述终端能力上报系统还包括终端： 所述终端设置为： 通过 IMS信令交互过程获得是否允许执行 rSRVCC的 指示， 并根据所述指示决定是否发送支持 rSRVCC的信息给所述基站系统。
8、 如权利要求 6所述的系统，其中，所述终端能力上报系统还包括终端， 其中：
所述终端设置为： 通过建立与基站系统间无线连接的过程， 或通过无线 能力消息，将自身支持反向单待业务连续性的能力信息发送至所述基站系统。
9、 如权利要求 6所述的系统， 其中，
所述基站系统发送给所述 MSC的切换请求中包含用以定位所述 MSC位 置的目标标识；
所述基站系统在所述切换请求中携带反映所述终端支持反向单待业务连 续性的信息包括： 所述基站系统在所述切换请求中增加一消息字段， 以指示 将 CS域会话切换到 PS域， 或将 CS域会话和 PS域业务切换到 PS域， 以反 映所述终端支持反向单待业务连续性； 或者， 所述基站系统以所述切换请求 中的目标标识来反映所述终端支持反向单待业务连续性。
10、 如权利要求 9所述的系统， 其中，
所述目标标识中包含位置区域标识（ LAI )或无线区域标识（ RAI ) ； 所述基站系统是以所述目标标识中包含的 LAI或 RAI来反映所述终端支 持反向单待业务连续性。
11、 一种上报终端能力信息的基站系统， 包括依次相连的接收模块、 处 理模块和发送模块， 其中： 所述接收模块设置为： 接收终端支持反向单待业务连续性（rSRVCC )的 信息， 然后将所述信息发送至所述处理模块；
所述处理模块设置为： 在决定将所述终端在电路交换（CS )域建立的会 话切换到包交换（PS )域时， 在切换请求中携带反映所述终端支持反向单待 业务连续性的信息， 然后将所述切换请求发送至所述发送模块；
所述发送模块设置为： 将所述处理模块发送来的切换请求发送至移动交 换中心 （MSC ) 。
12、 如权利要求 11所述的基站系统， 其中，
所述切换请求中包含用以定位所述 MSC位置的目标标识；
所述处理模块是设置为： 在所述切换请求中增加一消息字段， 以指示将
CS域会话切换到 PS域， 或将 CS域会话和 PS域业务切换到 PS域， 以反映 所述终端支持反向单待业务连续性； 或者，
所述处理模块是设置为： 以所述切换请求中的目标标识来反映所述终端 支持反向单待业务连续性。
13、 如权利要求 12所述的基站系统， 其中，
所述目标标识中包含位置区域标识（ LAI )或无线区域标识（ RAI ) ； 所述处理模块是设置为： 以所述目标标识中包含的 LAI或 RAI来反映所 述终端支持反向单待业务连续性。
PCT/CN2011/070495 2010-08-23 2011-01-21 一种终端能力上报的方法及系统 WO2012024908A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201010262179.XA CN102378297B (zh) 2010-08-23 2010-08-23 一种终端能力上报的方法及系统
CN201010262179.X 2010-08-23

Publications (1)

Publication Number Publication Date
WO2012024908A1 true WO2012024908A1 (zh) 2012-03-01

Family

ID=45722844

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/070495 WO2012024908A1 (zh) 2010-08-23 2011-01-21 一种终端能力上报的方法及系统

Country Status (2)

Country Link
CN (1) CN102378297B (zh)
WO (1) WO2012024908A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110291840A (zh) * 2019-05-13 2019-09-27 北京小米移动软件有限公司 一种连接处理方法、装置和介质
CN113841435A (zh) * 2019-05-16 2021-12-24 株式会社Ntt都科摩 用户装置以及基站装置

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101727963B1 (ko) * 2012-04-11 2017-04-18 노키아 솔루션스 앤드 네트웍스 오와이 네트워크 공유 및 역 단일 무선 음성 호 연속성
US10080162B2 (en) 2012-04-11 2018-09-18 Nokia Solutions And Networks Oy Network sharing and reverse single radio voice call continuity
CN103797853B (zh) * 2012-07-11 2017-06-27 华为技术有限公司 反向语音连续性切换方法、装置及系统
WO2014023032A1 (zh) * 2012-08-10 2014-02-13 华为技术有限公司 获取ue的ps接入能力的方法及网络设备
WO2014059568A1 (zh) * 2012-09-18 2014-04-24 华为技术有限公司 无线通信系统内的切换处理方法及设备
CN103959860A (zh) * 2012-11-13 2014-07-30 华为技术有限公司 一种获取无线接入能力的方法及装置

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101594647A (zh) * 2008-05-28 2009-12-02 华为技术有限公司 一种sr vcc业务切换处理方法及设备
CN101800961A (zh) * 2009-02-09 2010-08-11 华为技术有限公司 保持语音业务连续性的方法、装置及通信系统

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101594647A (zh) * 2008-05-28 2009-12-02 华为技术有限公司 一种sr vcc业务切换处理方法及设备
CN101800961A (zh) * 2009-02-09 2010-08-11 华为技术有限公司 保持语音业务连续性的方法、装置及通信系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"Feasibility Study of Single Radio Voice Call Continuity from UTRAN/GERAN to E-UTRAN/HSPA", 3GPP, TR 23.885 V0.3.0, May 2010 (2010-05-01) *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110291840A (zh) * 2019-05-13 2019-09-27 北京小米移动软件有限公司 一种连接处理方法、装置和介质
CN110291840B (zh) * 2019-05-13 2023-10-31 北京小米移动软件有限公司 一种连接处理方法、装置和介质
CN113841435A (zh) * 2019-05-16 2021-12-24 株式会社Ntt都科摩 用户装置以及基站装置

Also Published As

Publication number Publication date
CN102378297B (zh) 2015-04-01
CN102378297A (zh) 2012-03-14

Similar Documents

Publication Publication Date Title
US8180347B2 (en) Domain transferring method for single radio voice call continuity
US9467907B2 (en) Handover of user-equipment (UE) undetected emergency calls
WO2012024908A1 (zh) 一种终端能力上报的方法及系统
WO2012025007A1 (zh) 终端、hss、及核心网网元获知终端能力的方法和系统
JP5694348B2 (ja) ハンドオーバー遅延の最適化
WO2008046319A1 (fr) Procédé et système pour assurer la continuité d'un appel vocal lors de la gestion d'une affaire urgente
WO2010025602A1 (zh) 紧急业务切换方法
TW201220786A (en) Handling a registration timer to provide service continuity in IMS
US8934454B2 (en) Method and system for switching circuit switch domain service to packet switch domain
US9326302B2 (en) Method and system for implementing reverse single radio voice call continuity
EP2485530B1 (en) System and method for switching ringing state session with customized alerting tone
EP2487958A1 (en) Method and system for realizing session handover
WO2012149866A1 (zh) 单一无线语音呼叫连续性域的切换方法及系统
WO2011134341A1 (zh) 反向单待业务连续性实现方法及系统
WO2011127790A1 (zh) 一种实现单待业务连续性会话保活的方法和系统
CN102724723B (zh) 基于ims的控制切换方法及系统
WO2013064105A1 (zh) 一种反向单待业务连续性承载切换方法及装置
WO2011130954A1 (zh) 单待终端业务连续性实现方法和系统
WO2011023054A1 (zh) 一种ip多媒体子系统中多会话能力同步方法及系统
WO2011015019A1 (zh) 一种多方通话业务连续性的实现方法及系统
WO2012041138A1 (zh) 终呼通过拜访地ims接入点接入的方法及系统
WO2011097966A1 (zh) 一种单模业务连续实现方法和系统
WO2013102393A1 (zh) 一种改进的反向单待业务连续性实现方法和装置
WO2013071897A1 (zh) 一种实现反向单待业务连续性的方法和系统
WO2011017926A1 (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: 11819283

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

Country of ref document: EP

Kind code of ref document: A1