WO2014008643A1 - 反向语音连续性切换方法、装置及*** - Google Patents
反向语音连续性切换方法、装置及*** Download PDFInfo
- Publication number
- WO2014008643A1 WO2014008643A1 PCT/CN2012/078507 CN2012078507W WO2014008643A1 WO 2014008643 A1 WO2014008643 A1 WO 2014008643A1 CN 2012078507 W CN2012078507 W CN 2012078507W WO 2014008643 A1 WO2014008643 A1 WO 2014008643A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- handover
- rsrvcc
- request message
- switching
- transparent container
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 44
- 238000010295 mobile communication Methods 0.000 claims description 5
- 230000005540 biological transmission Effects 0.000 abstract description 7
- 238000004891 communication Methods 0.000 abstract description 7
- 230000004044 response Effects 0.000 description 12
- 238000010586 diagram Methods 0.000 description 4
- 238000012508 change request Methods 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
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 mobile communications, and in particular, to a rSRVCC (reversed Single Radio Voice Continuity) handover method, apparatus, and system. Background technique
- HSPA High Speed Packet Access
- PS Packet Switch
- VOIP Voice
- IP voice IP voice
- WCDMA Wideband Code Division Multiple Access
- CS Circuit Switch
- the access node in the target HSPA network receives the service of the target HSPA network, that is, the target SGSN (Serving General Packet Radio Service Support Node).
- the target SGSN Serving General Packet Radio Service Support Node.
- the handover request is sent by the node, it is required to determine whether the bearer required to be established by the target SGSN in the handover request is included in a transparent container sent by the access node RNC of the source WCDMA network, and if yes, the target SGSN is established to be established.
- the bearer is to complete the rSRVCC switch, otherwise the bearer is not established.
- the target RNC receives the handover request message (relocation request) sent by the target SGSN
- the target RNC establishes a load and generates a handover command (HANDOVER COMMAND), and the handover command is passed to the source MSC to the source MSC to the source.
- the RNC is ultimately sent to the UE that needs to be handed over.
- the source RNC needs to insert some information of the rSRVCC, such as IP/PORT, in the handover command. If the target RNC performs integrity protection on the handover command, the source RNC can no longer modify the handover command.
- the bearer-switched bearer PS RAB Radio Access Bearer
- PS RAB Radio Access Bearer
- the source RNC needs to insert information such as IP/PORT in the handover command, that is, the source RNC needs to modify the handover command. In this case, the source RNC cannot modify the handover command.
- the technical problem to be solved by the present invention is to provide a method, a device and a system for rSRVCC handover, so as to improve the success rate of rSRVCC handover, ensure continuity of voice data transmission, and improve communication quality.
- an embodiment of the present invention provides an rSRVCC switching method, including:
- the target RNC receives the handover request message sent by the target SGSN;
- Determining that the handover requested by the handover request message is an rSRVCC handover
- rSRVCC handover processing is performed.
- an embodiment of the present invention provides an rSRVCC switching apparatus, including: a receiving module, configured to receive a handover request message sent by a target SGSN;
- the determining module is configured to determine that the handover requested by the handover request message is rSRVCC handover, and the processing module is configured to perform rSRVCC handover processing according to the handover request message.
- the embodiment of the present invention further provides a system for rSRVCC handover, including a source network access node, a source mobile switching center MSC, that is, a source MSC, a target network control node, and a target network access node, where
- the target network access node includes the rSRVCC switching device described above.
- the bearer required to be established by the target SGSN is always established, regardless of whether the bearer is included in the transparent container of the handover request message, and the handover command is not integrity protected, and the packet switching domain is avoided.
- PS RAB lack of bearer
- the impact of the lack of bearer (PS RAB) on the establishment of the access bearer improves the success rate of rSRVCC handover, ensures the continuity of voice data transmission, and improves the communication quality.
- FIG. 1 is a schematic structural diagram of an rSRVCC switching system according to an embodiment of the present invention
- FIG. 2 is a schematic structural diagram of an rSRVCC switching apparatus according to an embodiment of the present invention.
- FIG. 3 is a flowchart of a rSRVCC handover method according to an embodiment of the present invention.
- FIG. 4 is a flowchart of a specific rSRVCC handover method according to an embodiment of the present invention
- FIG. 5 is a flowchart of another specific rSRVCC handover method according to an embodiment of the present invention
- a flowchart of another specific rSRVCC handover method is provided.
- FIG. 7 is a flowchart of another specific rSRVCC handover method according to an embodiment of the present invention
- FIG. 8 is another specific embodiment of the present invention. Flowchart of the rSRVCC handover method. detailed description
- the embodiment of the present invention discloses a system for rSRVCC handover.
- FIG. 1 it is a schematic structural diagram of a system for rSRVCC handover according to an embodiment of the present invention.
- the system includes a source network access node source RNC 1 in a source network.
- the source mobile switching center is the source MSC 2.
- the target network control node of the target network is the target SGSN 3.
- the target network access node is the target RNC 4.
- the target RNC 4 of the target network includes the rSRVCC switching device for the corresponding terminal UE.
- the rSRVCC handover process is completed during the handover from the source network to the target network.
- the source network of the embodiment of the present invention may be a CS network, for example: a WCDMA network; and the target network may be a PS network, for example: an HSPA network.
- the rSRVCC switching device according to the embodiment of the present invention will be described in detail below with reference to FIG. 2, and the rSRVCC switching device described below can be applied to the above system.
- the rSRVCC switching device may be disposed in a target RNC in the foregoing system, where the rSRVCC switching device includes:
- the receiving module 41 is configured to receive a handover request message sent by the target SGSN.
- the determining module 42 is configured to determine that the handover requested by the handover request message is rSRVCC handover, and the processing module 43 is configured to perform rSRVCC handover processing according to the handover request message.
- the target SGSN Upon receiving the mobile switching center handover request (CS to PS HO request) sent by the source MSC (Mobile Switching Center), the target SGSN sends a handover request message to the target RNC (Relocation) Request), the receiving module 41 of the rSRVCC switching device receives the handover request message. Specifically, when the user terminal is handed over, the source RNC connected to the user terminal sends a handover request (Relocation required) to the source MSC, and the source MSC sends the mobile switching center handover to the target SGSN according to the handover request. Request ( CS to PS HO request ).
- the processing module 43 performs special processing of rSRVCC handover according to the handover request message.
- the determining module 42 may include: when determining that the handover requested by the handover request is rSRVCC handover, specifically:
- the first determining unit is configured to determine whether the target SGSN carries the rSRVCC indication in the handover request message, and then determine that the handover requested by the handover request message is rSRVCC handover.
- the first determining unit needs to determine whether the rSRVCC indication is carried in the handover request message.
- the target SGSN when receiving the mobile switching center handover request of the source MSC, adds an rSRVCC indication to the handover request message generated and sent to the target RNC to indicate the request of the current handover request message.
- the switching is rSRVCC switching, so that the first determining unit can notify the processing module 43 to perform rSRVCC switching processing.
- the method may include:
- the second determining unit is configured to determine whether the rSRVCC indication is included in the transparent container included in the handover request message, and determine that the handover requested by the handover request message is rSRVCC handover.
- the second determining unit needs to determine whether the rSRVCC indication is carried in the transparent container included in the handover request message. Specifically, when the user terminal switches, the source RNC generates a transparent container, and the source RNC includes an rSRVCC indication in the generated transparent container to indicate The handover required by the current handover request (Relocation required) is rSRVCC handover, and the transparent container is carried in the handover request (Relocation required), and the mobile switching center handover request and the handover request message are transparently transmitted to the target. RNC. After determining that the transparent container included in the handover request message carries the rSRVCC indication, the second determining unit notifies the processing module 43 to perform rSRVCC handover processing. It should be noted that the transparent container has the full name: source RNC to target RNC transparent container. The transparent container mentioned in the present application has its full name when not described. A transparent container for the source RNC to the target RNC.
- the method may include:
- a third determining unit configured to determine whether a value of an iu instance (i interface instance) parameter carried in the transparent container included in the handover request message is 1, and the transparent container includes a circuit domain bearer (CS RAB ), Then, it is determined that the handover requested by the handover request message is an rSRVCC handover.
- the third determining unit needs to determine the value of the iu instance parameter carried in the transparent container included in the handover request message, and determine whether the transparent container contains the circuit domain bearer.
- the source RNC when the user terminal switches, the source RNC generates a transparent container.
- the transparent container includes a source RNC to target RNC transparent container, and the source RNC carries the circuit domain in the generated device. In the transparent container, and carry the rSRVCC indication in the handover request (Relocation required).
- the source MSC sends the transparent container and the rSRVCC indication to the mobile switching center handover request to the target SGSN, and the target SGSN sets the value of the iu instance parameter in the transparent container according to the rSRVCC indication or directly
- the value of the iu instance parameter is set to 1 to indicate that the handover requested by the current handover request message is rSRVCC handover by the value of the iu instance parameter and the circuit domain bearer.
- the third determining unit is configured to notify the processing module 43 when determining that the value of the iu instance parameter carried in the transparent container included in the handover request message is set to 1, and the transparent container includes the circuit domain bearer. rSRVCC switching processing.
- the method may include:
- a fourth determining unit configured to determine whether the transparent container included in the handover request message carries a circuit domain bearer, and the rSRVCC switching device does not receive the mobile switching center handover request from the target MSC, and determines the handover request message
- the requested switch is rSRVCC switch.
- the existing source RNC to the source MSC occurs when the CS to CS handover occurs in the mobile terminal.
- the source MSC needs to send a mobile switching center handover request to the target MSC, and the target MSC sends a target mobile switching center handover request to the target RNC. Therefore, in this case, the target RNC is received.
- the source MSC sends the mobile switching center handover request directly to the target SGSN, and does not send the request to the target MSC. Therefore, in this case, the target RNC can only receive the handover.
- the handover request message from the target SGSN does not receive the mobile switching center handover request of the target MSC, and then the target RNC can determine that the handover request message sent by the target SGSN requests CS to PS handover.
- rSRVCC switch When the mobile terminal needs to initiate the rSRVCC handover in the CS to PS handover, the source MSC sends the mobile switching center handover request directly to the target
- the method may include:
- a fifth determining unit configured to determine whether the transparent domain container included in the handover request message carries a circuit domain bearer, and the transparent container does not carry the packet switching domain bearer, and determines that the handover requested by the handover request message is rSRVCC Switch.
- the fifth determining unit needs to determine whether the circuit domain bearer and the packet switching domain bearer are carried in the transparent container included in the handover request message. Specifically, when the user terminal needs to perform the CS to PS handover, the source RNC generates a transparent container, where the transparent container includes a source RNC to target RNC transparent container, where the source RNC carries only the circuit domain bearer in the transparent container.
- the switch required to indicate the current handover request is the rSRVCC switch, and the transparent container is carried in the handover request (Relocation required), and the mobile switching center handover request and the handover request message are transparent Pass to the target RNC.
- the fifth determining unit determines that the transparent container included in the handover request message carries the circuit domain bearer CS RAB and does not carry the packet switching domain bearer, and notifies the processing module 43 to perform rSRVCC handover processing.
- the method may include:
- a sixth determining unit configured to determine whether the transparent container included in the handover request message does not carry a security parameter, and the transparent container does not carry a terminal history information (UE history information) parameter, and then determines the handover request message
- the requested handover is an rSRVCC handover
- Determining whether the security parameter included in the transparent request container does not carry the security parameter, and the parameter included in the terminal history information (UE history information) carried in the transparent container is In the UTRAN (Universal Mobile Telecommunications System Terrestrial Radio Access Network) cell information, it is determined that the handover requested by the handover request message is an rSRVCC handover.
- UTRAN Universal Mobile Telecommunications System Terrestrial Radio Access Network
- the sixth judging unit needs to determine whether the transparent container included in the handover request message includes a security parameter, whether the terminal history information parameter is included or the terminal history information parameter includes the terminal mobile information system, and whether the terminal history information parameter includes the universal mobile communication system.
- Terrestrial Radio Access Network UTRAN Cell Information when the user terminal needs to perform CS to PS handover, the source RNC generates a transparent container, where the transparent container includes a source RNC to target RNC transparent container, and the transparent container is carried in the handover request (Relocation required) And the mobile switching center switching request and the handover request message are transparently transmitted to the target RNC.
- the sixth determining unit determines that the transparent container included in the handover request message does not carry the security parameter, and does not carry the terminal history information (UE history information) parameter; or does not carry the security parameter, and the terminal history information (UE).
- the processing module 43 is notified to perform rSRVCC handover processing.
- processing module 43 may specifically include:
- the control unit is configured to control the integrity protection of the handover command.
- the first determination unit, the second determination unit, the third determination unit, the fourth determination unit, the fifth determination unit, and the sixth determination unit determine that the handover requested by the handover request message of the target SGSN is rSRVCC.
- the bearer required to be established by the target SGSN is always established, regardless of whether the bearer is included in a transparent container of the handover request message; and/or, the handover command sent to the source RNC is not integrity protected, so that the source
- the RNC can insert the parameters required by rSRVCC such as IP/PORT (port) in the HANDOVER COMAND to complete the rSRVCC switch.
- the target SGSN carries the rSRVCC handover indication in the handover request, and the target RNC always establishes the bearer required to be established by the target SGSN according to the rSRVCC handover indication, regardless of whether the bearer is included in the transparent container of the handover request message, Moreover, the integrity of the handover command is not protected, and the impact of the bearer switching domain bearer on the establishment of the access bearer is avoided, the success rate of the rSRVCC handover is improved, the continuity of the voice data transmission is ensured, and the communication quality is improved.
- FIG. 3 is a flowchart of a rSRVCC handover method according to an embodiment of the present invention.
- the target RNC in the embodiment of the present invention is a reverse voice switching device shown in FIG. 2.
- the method shown in Figure 3 includes:
- the target RNC receives the handover request message sent by the target SGSN.
- the target SGSN when receiving the mobile switching center handover request sent by the source MSC, the target SGSN sends a handover request message (Relocation request) to the target RNC, so that the target RNC receives the handover request message.
- the source RNC connected to the user terminal sends a handover request (Relocation required) to the source MSC, and the source MSC sends the mobile switching center handover to the target SGSN according to the handover request. request.
- S102 Determine that the handover requested by the handover request message is an rSRVCC handover.
- the S102 may specifically determine, according to the following manner, that the handover requested by the handover request message is an rSRVCC handover:
- the transparent container (such as the transparent RNC to target RNC transparent container of the source RNC to the target RNC, the transparent container generated by the source RNC, transparently transmitted by the target SGSN), the rSRVCC indication included in the handover request message;
- Determining that the parameter iu instance in the transparent container in the handover request message from the target SGSN is set to 1, and includes a circuit domain bearer;
- the transparent request container included in the handover request message (such as the source RNC to the target RNC transparent container source RNC to target RNC transparent container, the transparent container generated by the source RNC, transparently transmitted by the target SGSN) carries the circuit domain bearer, but there is no Receiving a handover request message from the target MSC; or
- the transparent request container included in the handover request message (such as the source RNC to the target RNC transparent container source RNC to target RNC transparent container, the transparent container generated by the source RNC, transparently transmitted by the target SGSN) carries only the circuit domain bearer, Carrying a packet switched domain bearer; or
- the transparent container included in the handover request message (such as the transparent RNC to target RNC transparent container from the source RNC to the target RNC, the transparent container generated by the source RNC, transparently transmitted by the target SGSN) does not include the security parameter, but The handover request sent by the target SGSN includes a security parameter.
- the S103 Perform rSRVCC switching processing according to the handover request message. Specifically, the S103 may be: establishing a bearer that is required to be established by the target SGSN; and/or not performing integrity protection on the handover command.
- the embodiment of the present invention implements the rSRVCC handover indication in the handover request, completes the establishment of the requested access bearer according to the rSRVCC handover indication, and avoids the impact on the establishment of the access bearer due to the lack of the bearer switching domain bearer, and improves the rSRVCC.
- the success rate of handover ensures the continuity of voice data transmission and improves communication quality.
- the target RNC in the embodiment of the present invention is a reverse voice switching device shown in Fig. 2.
- the source RNC initiates a handover request (Relocation required) to the source MSC.
- the source MSC sends a mobile switching center handover request to the target SGSN.
- the target SGSN sends a handover request message (Relocation request) to the target RNC, and carries an rSRVCC indication in the handover request message, where the rSRVCC indication is used to indicate that the target RNC always establishes a bearer that is required to be established by the target SGSN. Regardless of whether the bearer is included in the transparent container of the handover request message; and/or, the handover command sent to the source RNC is not integrity protected, so that the source RNC can insert the IP/PORT in the handover command (HANDOVER COMAND) Wait for the parameters required by rSRVCC to complete the rSRVCC switch;
- the target RNC determines whether the handover requested by the handover request message is an rSRVCC handover. In this embodiment, the target RNC determines that the handover request message carries an rSRVCC indication, and determines a handover requested by the handover request message. For the rSRVCC handover, the rSRVCC handover process is performed, that is, the bearer that is established by the target SGSN is always established, regardless of whether the bearer is included in the transparent container of the handover request message; and/or the control does not switch to the source RNC.
- the command performs integrity protection so that the source RNC can insert the parameters required by rSRVCC such as IP/PORT in the HANDOVER COMAND message and execute 409-413 to complete the rSRVCC switch.
- the target RNC returns a response message to the target SGSN.
- the target SGSN returns a handover response message to the source MSC.
- the source MSC returns a handover command to the source RNC, and the rSRVCC handover is completed.
- the target RNC in the embodiment of the present invention is a reverse voice switching device shown in Fig. 2.
- the source RNC initiates a handover request (Relocation required) to the source MSC, and performs the Carrying the rSRVCC indication in the transparent container included in the change request;
- the source MSC sends a mobile switching center switching request to the target SGSN, where the mobile switching center switching request includes the transparent container.
- the target SGSN sends a handover request message (Relocation request) to the target RNC, where the handover request message includes the transparent container.
- the target RNC determines whether the handover requested by the handover request message is an rSRVCC handover.
- the target RNC determines that the transparent container included in the handover request message carries an rSRVCC indication, and determines the The handover requested by the handover request message is an rSRVCC handover, and the rSRVCC handover process is performed, that is, the bearer that is established by the target SGSN is always established, regardless of whether the bearer is included in a transparent container of the handover request message; and/or, control
- the integrity of the handover command sent to the source RNC is not protected, so that the source RNC can insert the parameters required by the rSRVCC such as IP/PORT in the HANDOVER COMAND message, and execute 509-513 to complete the rSRVCC handover.
- the target RNC returns a response message to the target SGSN.
- the target SGSN returns a handover response message to the source MSC.
- the source MSC returns a handover command to the source RNC, and the rSRVCC handover is completed.
- the target RNC in the embodiment of the present invention is a reverse voice switching device shown in FIG. 2.
- the source RNC initiates a handover request (Relocation required) to the source MSC, and carries an rSRVCC indication in the transparent container included in the handover request.
- the source MSC sends a mobile switching center switching request to the target SGSN, where the mobile switching center switching request includes the transparent container, and carries a circuit domain bearer in the transparent container.
- the target SGSN sends a handover request message (Relocation request) to the target RNC, where the handover request message includes the transparent container, and the value of the iu instance parameter carried in the transparent container is set to 1 according to the rSRVCC indication. ;
- the target RNC determines whether the handover requested by the handover request message is an rSRVCC handover.
- the value of the iu instance parameter carried in the transparent container included in the handover request message is set according to the rSRVCC indication or iu.
- the instance parameter has a value of 1, and the transparent container carries the circuit domain bearer.
- the handover requested by the handover request message is an rSRVCC handover, and the rSRVCC handover process is performed, that is, the bearer that is established by the target SGSN is always established. Regardless of whether the bearer is included in the transparent container of the handover request message; and/or, the control does not cut to the source RNC.
- the command is used for integrity protection, so that the source RNC can insert the parameters required by rSRVCC such as IP/PORT in the HANDOVER COMAND message, and execute 509-513 to complete the rSRVCC switch.
- the target RNC returns a response message to the target SGSN.
- the target SGSN returns a handover response message to the source MSC.
- the source MSC returns a handover command to the source RNC, and the rSRVCC handover is completed.
- the target RNC in the embodiment of the present invention is a reverse voice switching device shown in FIG. 2.
- the source RNC initiates a handover request (Relocation required) to the source MSC, and carries an rSRVCC indication in the transparent container included in the handover request.
- the source MSC sends a mobile switching center switching request to the target SGSN, where the mobile switching center switching request includes the transparent container, and carries a circuit domain bearer in the transparent container.
- the target SGSN sends a handover request message (Relocation request) to the target RNC, where the handover request message includes the transparent container.
- Relocation request a handover request message
- the target RNC determines whether the handover requested by the handover request message is an rSRVCC handover.
- the transparent container included in the handover request message carries a circuit domain bearer and does not receive a mobile switching center from the target MSC.
- the handover requested by the handover request message is an rSRVCC handover, and the rSRVCC handover process is performed, that is, the bearer that is established by the target SGSN is always established, regardless of whether the bearer is included in a transparent container of the handover request message; And/or, the control does not perform integrity protection on the handover command sent to the source RNC, so that the source RNC can insert parameters required by the rSRVCC such as IP/PORT in the HANDOVER COMAND message, and execute 709-713 to complete the rSRVCC handover;
- the target RNC returns a response message to the target SGSN.
- the target SGSN returns a handover response message to the source MSC.
- the source MSC returns a handover command to the source RNC, and the rSRVCC handover is completed.
- the source MSC needs to send a mobile switching center handover request to the target MSC, and the target is The MSC sends a target mobile switching center handover request to the target RNC. Therefore, in this case, the target RNC receives the handover request from the target MSC.
- the source MSC sends the mobile switching center handover request directly to the target SGSN, and does not send the request to the target MSC.
- the target RNC can only receive the handover request message from the target SGSN, and does not receive the mobile switching center handover request of the target MSC. Then, the target RNC can determine that the handover request message sent by the target SGSN is requested by the target RNC. About rSRVCC switching from CS to PS switching.
- the target RNC in the embodiment of the present invention is a reverse voice switching device shown in FIG. 2.
- the source RNC initiates a handover request (Relocation required) to the source MSC, and carries an rSRVCC indication in the transparent container included in the handover request.
- the source MSC sends a mobile switching center switching request to the target SGSN, where the mobile switching center switching request includes the transparent container, and the transparent container carries a circuit domain bearer.
- the target SGSN sends a handover request message (Relocation request) to the target RNC, where the handover request message includes the transparent container.
- Relocation request a handover request message
- the target RNC determines whether the handover requested by the handover request message is an rSRVCC handover.
- the transparent container included in the handover request message carries a circuit domain bearer, and does not carry a packet switched domain bearer.
- the handover requested by the handover request message is an rSRVCC handover, and the rSRVCC handover process is performed, that is, the bearer that is required to be established by the target SGSN is always established, regardless of whether the bearer is included in a transparent container of the handover request message; and/or, control
- the integrity of the handover command sent to the source RNC is not performed, so that the source RNC can insert the parameters required by the rSRVCC such as IP/PORT in the HANDOVER COMAND message to complete the rSRVCC handover.
- the target RNC returns a response message to the target SGSN.
- the target SGSN returns a handover response message to the source MSC.
- the source MSC returns a handover command to the source RNC, and the rSRVCC handover is completed.
- the target RNC in the embodiment of the present invention is a reverse voice switching device shown in Fig. 2.
- the source RNC initiates a handover request (Relocation required) to the source MSC, and includes a transparent container in the switching request.
- the source MSC sends a mobile switching center switching request to the target SGSN, where the mobile switching center switching request includes the transparent container.
- the target SGSN sends a handover request message (Relocation request) to the target RNC, where the handover request message includes the transparent container.
- Relocation request a handover request message
- the target RNC determines whether the handover requested by the handover request message is an rSRVCC handover.
- the transparent container included in the handover request message does not include a security parameter, and does not include a terminal history information (UE history information) parameter, or the transparent container included in the handover request message does not include security.
- a parameter, and the terminal history information (UE history information) parameter included in the transparent container is UTRAN cell information, and the handover requested by the handover request message is rSRVCC handover, and rSRVCC handover processing is performed, that is, execution is always established.
- the target SGSN requires the established bearer regardless of whether the bearer is included in the transparent container of the handover request message; and/or, the control does not perform integrity protection on the handover command sent to the source RNC, so that the source RNC can be in HANDOVER COMAND Insert the parameters required by rSRVCC such as IP/PORT into the message to complete the rSRVCC switch.
- the target RNC returns a response message to the target SGSN.
- the target SGSN returns a handover response message to the source MSC.
- the source MSC returns a handover command to the source RNC, and the rSRVCC handover is completed.
- the target SGSN carries the rSRVCC handover indication in the handover request, and the target RNC always establishes the bearer required to be established by the target SGSN according to the rSRVCC handover indication, regardless of whether the bearer is included in the transparent container of the handover request message, Moreover, the integrity of the handover command is not protected, and the impact of the bearer switching domain bearer on the establishment of the access bearer is avoided, the success rate of the rSRVCC handover is improved, the continuity of the voice data transmission is ensured, and the communication quality is improved.
- the storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).
Landscapes
- Engineering & Computer Science (AREA)
- Multimedia (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
本发明实施例公开了一种rSRVCC切换方法、装置及***,其中,所述方法包括:接收目标SGSN发送的切换请求消息;判断所述切换请求消息所请求的切换为rSRVCC切换;根据所述切换请求消息,进行rSRVCC切换处理。实施本发明实施例,可提高rSRVCC切换的成功率,保证语音数据传输的连续性,提升通信质量。
Description
反向语音连续性切换方法、 装置及*** 技术领域
本发明涉及移动通信领域, 尤其涉及一种 rSRVCC ( reversed Single Radio Voice Continuity, 反向语音连续性)切换方法、 装置及***。 背景技术
HSPA ( High Speed Packet Access , 高速分组接入 ) PS ( Packet switch, 包交 换) 网络能提供高速率、 高质量的数据业务, 能很好地满足用户越来越多的数 据业务需求, VOIP( voice over IP, IP语音)业务可以在 HSPA网络提供。 WCDMA ( Wideband Code Division Multiple Access, 宽带码分多址)可以提供 CS ( Circuit switch, 电路交换 )语音。 如果用户在 WCDMA网络发起语音呼叫, 由于 CS网 络负荷的问题或者用户从 WCDMA网络移动至 HSPA网络, 需要把语音呼叫从 WCDMA网络切换至 HSPA网络, 这种切换即为 rSRVCC ( reversed Single Radio Voice Continuity, 反向语音连续性)。
现有从 WCDMA切换到 HSPA的协议流程中规定:
目标 HSPA网络中的接入节点即目标 RNC ( Radio Network Controller, 无线 网络控制器)在接收到所述目标 HSPA 网络的控制节点即目标 SGSN ( Serving General Packet Radio Service Support Node, 通用分组无线服务的服务支持节点) 发送的切换请求时, 需要判断切换请求中的所述目标 SGSN要求建立的承载是 否包含在源 WCDMA网络的接入节点 RNC发送的透明容器中, 如果包含则建 立所述目标 SGSN要求建立的承载, 以完成 rSRVCC切换, 否则, 不建立该承 载。
另外,在目标 RNC收到目标 SGSN发送的切换请求消息( relocation request ) 后, 目标 RNC会建立 7 载并生成切换命令 ( HANDOVER COMMAND ), 将该 切换命令通过所述目标 SGSN到源 MSC再到源 RNC, 最终要发给需要进行切 换的 UE。 在此过程中源 RNC要在切换命令中*** rSRVCC的一些信息, 例如 IP/PORT等信息, 而如果目标 RNC对切换命令进行了完整性保护, 那么源 RNC 不能再修改切换命令。
在 rSRVCC过程中, 目标 HSPA***的目标 SGSN要求建立的承载即包交 换承载 PS RAB ( Radio Access Bearer, 无线接入承载)很可能不包含在源 WCDMA的 RNC发送的透明容器中,在这种情况下 rSRVCC切换不会成功。 而 且在 rSRVCC切换过程中, 源 RNC需要在切换命令中*** IP/PORT等信息, 也 就是说源 RNC需要修改切换命令, 这种情况下, 源 RNC无法修改切换命令。 这两个问题都会导致 rSRVCC切换失败, 影响语音数据传输的连续性, 降低通 信质量。 发明内容
本发明要解决的技术问题在于, 提供一种 rSRVCC切换的方法、 装置及系 统, 以提高 rSRVCC切换的成功率, 保证语音数据传输的连续性, 提升通信质 量。
为了解决上述技术问题, 一方面, 本发明实施例提供了一种 rSRVCC切换 方法, 包括:
目标 RNC接收目标 SGSN发送的切换请求消息;
判断所述切换请求消息所请求的切换为 rSRVCC切换;
根据所述切换请求消息, 进行 rSRVCC切换处理。
一方面, 本发明实施例提供了一种 rSRVCC切换装置, 其特征在于, 包括: 接收模块, 用于接收目标 SGSN发送的切换请求消息;
判断模块, 用于判断所述切换请求消息所请求的切换为 rSRVCC切换; 处理模块, 用于根据所述切换请求消息, 进行 rSRVCC切换处理。
另一方面, 本发明实施例还提供了一种 rSRVCC切换的***, 包括源网络 接入节点、 源移动交换中心 MSC即源 MSC、 目标网络控制节点、 目标网络接 入节点, 其特征在于, 所述目标网络接入节点包含上述的 rSRVCC切换装置。
实施本发明实施例, 根据 rSRVCC切换指示, 总是建立目标 SGSN要求建 立的承载, 而不管该承载是否包含在切换请求消息的透明容器中, 而且不对切 换命令进行完整性保护, 避免由于包交换域承载( PS RAB ) 的缺失对接入承载 建立的影响, 提高了 rSRVCC切换的成功率, 保证语音数据传输的连续性, 提 升通信质量。
附图说明 例或现有技术描述中所需要使用的附图作筒单地介绍, 显而易见地, 下面描述 中的附图仅仅是本发明的一些实施例, 对于本领域普通技术人员来讲, 在不付 出创造性劳动的前提下, 还可以根据这些附图获得其他的附图。
图 1是本发明实施例提供的 rSRVCC切换***的结构示意图;
图 2为本发明实施例提供的 rSRVCC切换装置的结构示意图;
图 3为本发明实施例提供的 rSRVCC切换方法的流程图;
图 4为本发明实施例提供的其中一种具体的 rSRVCC切换方法的流程图; 图 5为本发明实施例提供的其中另一种具体的 rSRVCC切换方法的流程图; 图 6为本发明实施例提供的其中另一种具体的 rSRVCC切换方法的流程图; 图 7为本发明实施例提供的其中另一种具体的 rSRVCC切换方法的流程图; 图 8为本发明实施例提供的再一种具体的 rSRVCC切换方法的流程图。 具体实施方式
下面将结合本发明实施例中的附图, 对本发明实施例中的技术方案进行清 楚、 完整地描述, 显然, 所描述的实施例仅仅是本发明一部分实施例, 而不是 全部的实施例。 基于本发明中的实施例, 本领域普通技术人员在没有作出创造 性劳动前提下所获得的所有其他实施例, 都属于本发明保护的范围。
本发明实施例公开了一种 rSRVCC切换的***,请参见图 1 ,是本发明实施 例提供的 rSRVCC切换的***的结构组成示意图, 该***包括源网络中的源网 络接入节点源 RNC 1、 源移动交换中心即源 MSC 2、 目标网络的目标网络控制 节点即目标 SGSN 3、 目标网络接入节点即目标 RNC 4, 其中, 目标网络的目标 RNC 4包含 rSRVCC切换装置, 用于相应的终端 UE在从源网络向目标网络切 换过程中, 完成 rSRVCC切换处理。 本发明实施例的源网络可以为 CS网络, 例 如: WCDMA网络; 目标网络可以为 PS网络, 例如: HSPA网络。
下面通过附图 2对本发明实施例提供的 rSRVCC切换装置进行详细介绍, 下述的 rSRVCC切换装置可以应用于上述的***中。
请参见图 2, 为本发明实施例提供的 rSRVCC切换装置的结构示意图; 该
rSRVCC切换装置可设置在上述***中的目标 RNC中, 所述 rSRVCC切换装置 包括:
接收模块 41 , 用于接收目标 SGSN发送的切换请求消息;
判断模块 42, 用于判断所述切换请求消息所请求的切换为 rSRVCC切换; 处理模块 43 , 用于根据所述切换请求消息, 进行 rSRVCC切换处理。
在接收到源 MSC ( Mobile Switching Center, 移动交换中心 )发送的移动交 换中心切换请求即 CS到 PS切换请求( CS to PS HO request )时,所述目标 SGSN 会向目标 RNC发送切换请求消息( Relocation request ) , 所述 rSRVCC切换装置 的所述接收模块 41会接收到所述切换请求消息。 具体的, 在用户终端发生切换 时, 与所述用户终端相连的源 RNC会向所述源 MSC发送切换要求(Relocation required ) , 所述源 MSC根据切换要求向目标 SGSN发送所述移动交换中心切换 请求 ( CS to PS HO request )。
所述判断模块 42在判断该切换请求消息所请求的切换为 rSRVCC切换时, 所述处理模块 43根据所述切换请求消息, 进行 rSRVCC切换的特殊处理。
进一步可选的, 所述判断模块 42在判断切换请求所请求的切换为 rSRVCC 切换时, 具体可以包括:
第一判断单元, 用于判断所述目标 SGSN 在切换请求消息中是否携带 rSRVCC指示, 则判断所述切换请求消息所请求的切换为 rSRVCC切换。
即所述第一判断单元需要判断所述切换请求消息中是否携带有 rSRVCC指 示。 具体的, 所述目标 SGSN在接收到源 MSC的移动交换中心切换请求时, 会 在生成并发送给所述目标 RNC的切换请求消息中,增加一个 rSRVCC指示用于 指示本次切换请求消息所请求的切换为 rSRVCC切换, 以便于所述第一判断单 元能够通知所述处理模块 43进行 rSRVCC切换处理。
进一步可选的, 所述判断模块 42 在判断切换请求所请求的切换是否为 rSRVCC切换时, 具体可以包括:
第二判断单元, 用于判断所述切换请求消息中包含的透明容器中是否携带 rSRVCC指示, 则判断所述切换请求消息所请求的切换为 rSRVCC切换。
即所述第二判断单元需要判断所述切换请求消息中包含的透明容器中是否 携带 rSRVCC指示。 具体的, 在用户终端发生切换时, 所述源 RNC会生成一个 透明容器, 所述源 RNC会在生成的所述透明容器中包含 rSRVCC指示, 以指示
本次切换要求(Relocation required )所要求的切换为 rSRVCC切换, 所述透明 容器会携带在所述切换要求(Relocation required ), 所述移动交换中心切换请求 以及所述切换请求消息中透传至目标 RNC。 所述第二判断单元在判断确定出所 切换请求消息中包含的透明容器中携带有 rSRVCC指示后, 通知所述处理模块 43进行 rSRVCC切换处理。 需要说明的是, 所述的透明容器全名为: 源 RNC到 目标 RNC的透明容器 ( source RNC to target RNC transparent container ), 本申请 中提到的透明容器在未作说明时,其全名均为源 RNC到目标 RNC的透明容器。
进一步可选的, 所述判断模块 42 在判断切换请求所请求的切换是否为 rSRVCC切换时, 具体可以包括:
第三判断单元, 用于判断所述切换请求消息中包含的透明容器中携带的 iu instance ( iu接口实例)参数的值是否为 1 , 而且所述透明容器中包含电路域承 载( CS RAB ), 则判断所述切换请求消息所请求的切换为 rSRVCC切换。
即所述第三判断单元需要判断所述切换请求消息中包含的透明容器中携带 的 iu instance参数的值, 并判断所述透明容器中是否包含电路域承载。 具体的, 在用户终端发生切换时, 所述源 RNC会生成透明容器, 同样, 所述透明容器包 括 source RNC to target RNC transparent container, 所述源 RNC会将电路域 载 携带在所述生成的所述透明容器中, 并在切换要求(Relocation required )中携带 rSRVCC指示。 源 MSC将所述透明容器和所述 rSRVCC指示携带在移动交换中 心切换请求发送给目标 SGSN,目标 SGSN根据所述 rSRVCC指示对所述透明容 器中的 iu instance参数的值进行设置或者直接将所述 iu instance参数的值设置为 1 , 以通过所述 iu instance参数的值以及电路域承载来指示本次切换请求消息所 请求的切换为 rSRVCC切换。 所述第三判断单元在判断确定出所切换请求消息 中包含的透明容器中携带的 iu instance参数的值被设置为 1 , 而且所述透明容器 中包含电路域承载时, 通知所述处理模块 43进行 rSRVCC切换处理。
进一步可选的, 所述判断模块 42 在判断切换请求所请求的切换是否为 rSRVCC切换时, 具体可以包括:
第四判断单元, 用于判断所述切换请求消息中包含的透明容器中是否携带 电路域承载且所述 rSRVCC切换装置没有接收到来自目标 MSC的移动交换中心 切换请求, 则判断所述切换请求消息所请求的切换为 rSRVCC切换。
需要说明的是,现有的在移动终端发生 CS到 CS切换时,源 RNC向源 MSC
发送切换要求后, 源 MSC需要向目标 MSC发送移动交换中心切换请求, 而由 目标 MSC向目标 RNC发送目标侧的移动交换中心切换请求, 因此, 在此情况 下, 所述目标 RNC是会接受到目标 MSC的切换请求的。 而在移动终端在 CS 到 PS切换需要发起 rSRVCC切换时, 源 MSC是直接向目标 SGSN发送移动交 换中心切换请求, 并不会向目标 MSC发送, 因此, 在此情况下, 目标 RNC只 能够接收到来自于目标 SGSN的切换请求消息,并不会接收到目标 MSC的移动 交换中心切换请求, 那么, 目标 RNC即可据此判断出目标 SGSN发送的切换请 求消息所请求的是关于 CS到 PS切换的 rSRVCC切换。
进一步可选的, 所述判断模块 42 在判断切换请求所请求的切换是否为 rSRVCC切换时, 具体可以包括:
第五判断单元, 用于判断所述切换请求消息中包含的透明容器中是否携带 电路域承载, 且所述透明容器中不携带包交换域承载, 则判断该切换请求消息 所请求的切换是 rSRVCC切换。
即所述第五判断单元需要判断所述切换请求消息中包含的透明容器中是否 携带电路域承载和包交换域承载。 具体的, 在用户终端需要进行 CS到 PS切换 时, 所述源 RNC会生成透明容器, 该透明容器包括 source RNC to target RNC transparent container, 所述源 RNC在所述透明容器中仅携带电路域承载, 以指 示本次切换要求(Relocation required )所要求的切换为 rSRVCC切换, 所述透 明容器会携带在所述切换要求(Relocation required ), 所述移动交换中心切换请 求以及所述切换请求消息中透传至目标 RNC。 所述第五判断单元在判断确定出 所切换请求消息中包含的透明容器中携带有电路域承载 CS RAB ,且不携带包交 换域承载, 通知所述处理模块 43进行 rSRVCC切换处理。
进一步可选的, 所述判断模块 42 在判断切换请求所请求的切换是否为 rSRVCC切换时, 具体可以包括:
第六判断单元, 用于判断所述切换请求消息中包含的透明容器中是否不携 带安全参数, 且所述透明容器中不携带终端历史信息( UE history information ) 参数, 则判断该切换请求消息所请求的切换是 rSRVCC切换;
或者
判断所述切换请求消息中包含的透明容器中是否不携带安全参数, 且所述 透明容器中携带的终端历史信息 (UE history information ) 参数中包含的是
UTRAN ( Universal Mobile Telecommunications System Terrestrial Radio Access Network, 通用移动通信***陆地无线接入网)小区信息, 则判断该切换请求消 息所请求的切换是 rSRVCC切换。
即所述第六判断单元需要判断所述切换请求消息中包含的透明容器中是否 包括安全参数, 是否包括终端历史信息参数或者包括终端历史信息参数时所述 终端历史信息参数是否包含通用移动通信***陆地无线接入网 UTRAN 小区信 息。 具体的, 在用户终端需要进行 CS到 PS切换时, 所述源 RNC会生成透明容 器, 所述透明容器包括 source RNC to target RNC transparent container, 所述透明 容器会携带在所述切换要求(Relocation required ), 所述移动交换中心切换请求 以及所述切换请求消息中透传至目标 RNC。 所述第六判断单元在判断确定出所 切换请求消息中包含的透明容器中不携带安全参数,且不携带终端历史信息( UE history information )参数时; 或者不携带安全参数, 且终端历史信息( UE history information )参数中携带的是通用移动通信***陆地无线接入网 UTRAN小区信 息时, 通知所述处理模块 43进行 rSRVCC切换处理。
进一步具体的, 所述处理模块 43具体可以包括:
建立单元, 用于建立所述目标 SGSN要求建立的承载; 和 /或
控制单元, 用于控制不对切换命令进行完整性保护。
即, 在所述第一判断单元、 第二判断单元、 第三判断单元、 第四判断单元、 第五判断单元、 第六判断单元判断出所述目标 SGSN的切换请求消息所请求的 切换为 rSRVCC切换时, 总是建立所述目标 SGSN要求建立的承载, 而不管该 承载是否包含在切换请求消息的透明容器中; 和 /或, 不对发往源 RNC的切换命 令进行完整性保护, 以使得源 RNC能在切换命令 ( HANDOVER COMAND )中 *** IP/PORT (端口)等 rSRVCC需要的参数, 完成 rSRVCC切换。
实施本发明实施例, 目标 SGSN在切换请求中携带 rSRVCC切换指示, 目 标 RNC根据该 rSRVCC切换指示, 总是建立目标 SGSN要求建立的承载, 而不 管该承载是否包含在切换请求消息的透明容器中, 而且不对切换命令进行完整 性保护,避免由于包交换域承载的缺失对接入承载建立的影响,提高了 rSRVCC 切换的成功率, 保证语音数据传输的连续性, 提升通信质量。
下面对本发明实施例提供的一种 rSRVCC切换方法进行详细介绍, 上述附 图 1所示对应的实施例的 rSRVCC切换装置可以应用于下述的方法中。
请参见图 3 , 为本发明实施例提供的 rSRVCC切换方法的流程图; 本发明实 施例中的目标 RNC是一种图 2中所示的反向语音切换装置。 图 3所示的方法包 括:
S101 : 目标 RNC接收目标 SGSN发送的切换请求消息。
具体的,在接收到源 MSC发送的移动交换中心切换请求时,所述目标 SGSN 会向目标 RNC发送切换请求消息 ( Relocation request ), 由此所述目标 RNC接 收到所述切换请求消息。 具体的, 在用户终端发生切换时, 与所述用户终端相 连的源 RNC会向所述源 MSC发送切换要求( Relocation required ),所述源 MSC 根据切换要求向目标 SGSN发送所述移动交换中心切换请求。
S102: 判断所述切换请求消息所请求的切换为 rSRVCC切换。
所述 S102 具体可根据以下方式判断所述切换请求消息所请求的切换为 rSRVCC切换:
判断切换请求消息中包含 rSRVCC指示; 或者
判断所述切换请求消息包含的透明容器(如源 RNC到目标 RNC的透明容 器 source RNC to target RNC transparent container, 由源 RNC生成该透明容器, 由所述目标 SGSN透传) 中包含的 rSRVCC指示; 或者
判断来自所述目标 SGSN的切换请求消息中的透明容器中的参数 iu instance 被设置为 1, 而且包含电路域承载; 或者
判断切换请求消息包含的透明容器(如源 RNC 到目标 RNC 的透明容器 source RNC to target RNC transparent container, 由源 RNC生成该透明容器, 由 所述目标 SGSN透传)中携带电路域承载, 但没有收到来自目标 MSC的切换请 求消息; 或者
判断切换请求消息包含的透明容器(如源 RNC 到目标 RNC 的透明容器 source RNC to target RNC transparent container, 由源 RNC生成该透明容器, 由 所述目标 SGSN透传) 中只携带电路域承载, 不携带包交换域承载; 或者
判断切换请求消息包含的透明容器(如源 RNC 到目标 RNC 的透明容器 source RNC to target RNC transparent container, 由源 RNC生成该透明容器, 由 所述目标 SGSN透传 ) 中不包含安全参数, 而在所述目标 SGSN发送的切换请 求中包含安全参数。
S103: 根据所述切换请求消息, 进行 rSRVCC切换处理。
具体的, 所述 S103可以为: 建立所述目标 SGSN要求建立的承载; 和 /或不 对切换命令进行完整性保护。
实施本发明实施例, 通过在切换请求中携带 rSRVCC 切换指示, 根据该 rSRVCC切换指示完成所请求的接入承载的建立,避免由于包交换域承载的缺失 对接入承载建立的影响, 提高了 rSRVCC切换的成功率, 保证语音数据传输的 连续性, 提升通信质量。
下面列举相应的具体实施例说明上述的 rSRVCC切换方法。
请参见图 4, 下面结合图 4对本发明实施例进行说明。 本发明实施例中的目 标 RNC是一种图 2所示的反向语音切换装置。
401、 源 RNC向源 MSC发起切换要求( Relocation required );
403、 源 MSC向目标 SGSN发送移动交换中心切换请求;
405、 目标 SGSN向目标 RNC发送切换请求消息( Relocation request ), 并 在所述切换请求消息中携带 rSRVCC指示, 所述 rSRVCC指示用于指示所述目 标 RNC总是建立所述目标 SGSN要求建立的承载, 而不管该承载是否包含在切 换请求消息的透明容器中;和 /或,不对发往源 RNC的切换命令进行完整性保护, 以使得源 RNC 能在切换命令 ( HANDOVER COMAND ) 中*** IP/PORT 等 rSRVCC需要的参数, 以完成 rSRVCC切换;
407、 目标 RNC判断所述切换请求消息所请求的切换是否为 rSRVCC切换, 本实施例中, 所述目标 RNC判断出所述切换请求消息中携带 rSRVCC指示, 确 定所述切换请求消息所请求的切换为 rSRVCC切换, 执行 rSRVCC切换处理, 即执行总是建立所述目标 SGSN要求建立的承载, 而不管该承载是否包含在切 换请求消息的透明容器中; 和 /或,控制不对发往源 RNC的切换命令进行完整性 保护, 以使得源 RNC 能在 HANDOVER COMAND 消息中*** IP/PORT 等 rSRVCC需要的参数, 并执行 409-413 , 以完成 rSRVCC切换。
409、 所述目标 RNC向所述目标 SGSN返回应答消息;
411、 所述目标 SGSN向所述源 MSC返回切换应答消息;
413、 所述源 MSC向所述源 RNC返回切换命令, rSRVCC切换完成。
请参见图 5, 下面结合图 5对本发明实施例进行说明。 本发明实施例中的目 标 RNC是一种图 2所示的反向语音切换装置。
501、 源 RNC向源 MSC发起切换要求(Relocation required ), 并在所述切
换要求中包含的透明容器中携带 rSRVCC指示;
503: 源 MSC向目标 SGSN发送移动交换中心切换请求, 所述移动交换中 心切换请求中包含所述透明容器;
505: 目标 SGSN向所述目标 RNC发送切换请求消息( Relocation request ), 所述切换请求消息中包含所述透明容器;
507: 目标 RNC判断所述切换请求消息所请求的切换是否为 rSRVCC切换, 本实施例中, 所述目标 RNC判断出所述切换请求消息中包含的所述透明容器中 携带 rSRVCC指示, 确定所述切换请求消息所请求的切换为 rSRVCC切换, 执 行 rSRVCC切换处理, 即执行总是建立所述目标 SGSN要求建立的承载, 而不 管该承载是否包含在切换请求消息的透明容器中; 和 /或, 控制不对发往源 RNC 的切换命令进行完整性保护, 以使得源 RNC能在 HANDOVER COMAND消息 中*** IP/PORT等 rSRVCC需要的参数,并执行 509-513 ,以完成 rSRVCC切换。
509: 所述目标 RNC向所述目标 SGSN返回应答消息;
511 : 所述目标 SGSN向所述源 MSC返回切换应答消息;
513: 所述源 MSC向所述源 RNC返回切换命令, rSRVCC切换完成。
请参见图 6, 下面结合图 6对本发明实施例进行说明, 本发明实施例中的目 标 RNC是一种图 2所示的反向语音切换装置。
601、 源 RNC向源 MSC发起切换要求(Relocation required ), 并在所述切 换要求中包含的透明容器中携带 rSRVCC指示;
603、 源 MSC向目标 SGSN发送移动交换中心切换请求, 所述移动交换中 心切换请求中包含所述透明容器, 并在所述透明容器中携带电路域承载;
605、 目标 SGSN向所述目标 RNC发送切换请求消息( Relocation request ), 所述切换请求消息中包含所述透明容器, 并根据 rSRVCC指示对所述透明容器 中携带的 iu instance参数的值设置为 1 ;
607、 目标 RNC判断所述切换请求消息所请求的切换是否为 rSRVCC切换, 本实施例中,所述切换请求消息中包含的透明容器中携带的 iu instance参数的值 是根据 rSRVCC指示进行设置或者 iu instance参数的值为 1 , 而且所述透明容器 中携带电路域承载, 所述切换请求消息所请求的切换为 rSRVCC 切换, 执行 rSRVCC切换处理, 即执行总是建立所述目标 SGSN要求建立的承载, 而不管该 承载是否包含在切换请求消息的透明容器中; 和 /或,控制不对发往源 RNC的切
换命令进行完整性保护, 以使得源 RNC能在 HANDOVER COMAND消息中插 入 IP/PORT等 rSRVCC需要的参数, 并执行 509-513 , 以完成 rSRVCC切换
609、 所述目标 RNC向所述目标 SGSN返回应答消息;
611、 所述目标 SGSN向所述源 MSC返回切换应答消息;
613、 所述源 MSC向所述源 RNC返回切换命令, rSRVCC切换完成。
请参见图 7, 下面结合图 7对本发明实施例进行说明, 本发明实施例中的目 标 RNC是一种图 2所示的反向语音切换装置。
701、 源 RNC向源 MSC发起切换要求(Relocation required ), 并在所述切 换要求中包含的透明容器中携带 rSRVCC指示;
703、 源 MSC向目标 SGSN发送移动交换中心切换请求, 所述移动交换中 心切换请求中包含所述透明容器, 并在所述透明容器中携带电路域承载;
705、 目标 SGSN向所述目标 RNC发送切换请求消息( Relocation request ), 所述切换请求消息中包含所述透明容器;
707、 目标 RNC判断所述切换请求消息所请求的切换是否为 rSRVCC切换, 本实施例中, 所述切换请求消息中包含的透明容器中携带电路域承载且没有接 收到来自目标 MSC的移动交换中心切换请求, 所述切换请求消息所请求的切换 为 rSRVCC切换, 执行 rSRVCC切换处理, 即执行总是建立所述目标 SGSN要 求建立的承载, 而不管该承载是否包含在切换请求消息的透明容器中; 和 /或, 控制不对发往源 RNC 的切换命令进行完整性保护, 以使得源 RNC 能在 HANDOVER COMAND消息中*** IP/PORT等 rSRVCC需要的参数, 并执行 709-713 , 以完成 rSRVCC切换;
709、 所述目标 RNC向所述目标 SGSN返回应答消息;
711、 所述目标 SGSN向所述源 MSC返回切换应答消息;
713、 所述源 MSC向所述源 RNC返回切换命令, rSRVCC切换完成。
在本发明实施例中需要说明的是,现有的在移动终端发生 CS到 CS切换时, 源 RNC向源 MSC发送切换要求后, 源 MSC需要向目标 MSC发送移动交换中 心切换请求, 而由目标 MSC向目标 RNC发送目标侧的移动交换中心切换请求, 因此, 在此情况下, 所述目标 RNC是会接受到目标 MSC的切换请求的。 而在 移动终端在 CS到 PS切换需要发起 rSRVCC切换时,源 MSC是直接向目标 SGSN 发送移动交换中心切换请求, 并不会向目标 MSC发送, 因此, 在此情况下, 目
标 RNC只能够接收到来自于目标 SGSN的切换请求消息, 并不会接收到目标 MSC的移动交换中心切换请求, 那么, 目标 RNC即可据此判断出目标 SGSN 发送的切换请求消息所请求的是关于 CS到 PS切换的 rSRVCC切换。
同样请参见图 7, 下面结合图 7对本发明实施例进行说明, 本发明实施例中 的目标 RNC是一种图 2所示的反向语音切换装置。
701、 源 RNC向源 MSC发起切换要求(Relocation required ), 并在所述切 换要求中包含的透明容器中携带 rSRVCC指示;
703、 源 MSC向目标 SGSN发送移动交换中心切换请求, 所述移动交换中 心切换请求中包含所述透明容器, 并所述透明容器中携带电路域承载;
705、 目标 SGSN向所述目标 RNC发送切换请求消息( Relocation request ), 所述切换请求消息中包含所述透明容器;
707、 目标 RNC判断所述切换请求消息所请求的切换是否为 rSRVCC切换, 本实施例中, 所述切换请求消息中包含的透明容器中携带电路域承载, 且不携 带包交换域承载, 所述切换请求消息所请求的切换为 rSRVCC 切换, 执行 rSRVCC切换处理, 即执行总是建立所述目标 SGSN要求建立的承载, 而不管该 承载是否包含在切换请求消息的透明容器中; 和 /或,控制不对发往源 RNC的切 换命令进行完整性保护, 以使得源 RNC能在 HANDOVER COMAND消息中插 入 IP/PORT等 rSRVCC需要的参数, 以完成 rSRVCC切换;
709、 所述目标 RNC向所述目标 SGSN返回应答消息;
711、 所述目标 SGSN向所述源 MSC返回切换应答消息;
713、 所述源 MSC向所述源 RNC返回切换命令, rSRVCC切换完成。
请参见图 8, 下面结合图 8对本发明实施例进行说明。 本发明实施例中的目 标 RNC是一种图 2所示的反向语音切换装置。
801、 源 RNC向源 MSC发起切换要求(Relocation required ), 并在所述切 换要求中包含透明容器;
803、 源 MSC向目标 SGSN发送移动交换中心切换请求, 所述移动交换中 心切换请求中包含所述透明容器;
805、 目标 SGSN向所述目标 RNC发送切换请求消息( Relocation request ), 所述切换请求消息中包含所述透明容器;
807、 目标 RNC判断所述切换请求消息所请求的切换是否为 rSRVCC切换,
本实施例中, 所述切换请求消息中包含的透明容器中不包含安全参数, 且不包 含终端历史信息( UE history information )参数, 或者, 所述切换请求消息中包 含的透明容器中不包含安全参数, 且所述透明容器中包含的终端历史信息 (UE history information )参数中包含的是 UTRAN小区信息, 所述切换请求消息所请 求的切换为 rSRVCC切换, 执行 rSRVCC切换处理, 即执行总是建立所述目标 SGSN要求建立的承载, 而不管该承载是否包含在切换请求消息的透明容器中; 和 /或, 控制不对发往源 RNC的切换命令进行完整性保护, 以使得源 RNC能在 HANDOVER COMAND消息中*** IP/PORT等 rSRVCC需要的参数, 以完成 rSRVCC切换;
809、 所述目标 RNC向所述目标 SGSN返回应答消息;
811、 所述目标 SGSN向所述源 MSC返回切换应答消息;
813、 所述源 MSC向所述源 RNC返回切换命令, rSRVCC切换完成。
实施本发明实施例, 目标 SGSN在切换请求中携带 rSRVCC切换指示, 目 标 RNC根据该 rSRVCC切换指示, 总是建立目标 SGSN要求建立的承载, 而不 管该承载是否包含在切换请求消息的透明容器中, 而且不对切换命令进行完整 性保护,避免由于包交换域承载的缺失对接入承载建立的影响,提高了 rSRVCC 切换的成功率, 保证语音数据传输的连续性, 提升通信质量。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程, 是可以通过计算机程序来指令相关的硬件来完成, 所述的程序可存储于一计算 机可读取存储介质中, 该程序在执行时, 可包括如上述各方法的实施例的流程。 其中, 所述的存储介质可为磁碟、 光盘、 只读存储记忆体(Read-Only Memory, ROM )或随机存储记忆体(Random Access Memory, RAM )等。
以上所揭露的仅为本发明一种较佳实施例而已, 当然不能以此来限定本发 明之权利范围, 因此依本发明权利要求所作的等同变化, 仍属本发明所涵盖的 范围。
Claims
1、 一种反向语音连续性 rSRVCC切换方法, 其特征在于, 包括: 目标无线网络控制器 RNC 接收目标通用分组无线服务的服务支持节点 SGSN发送的切换请求消息;
判断所述切换请求消息所请求的切换为 rSRVCC切换;
根据所述切换请求消息, 进行 rSRVCC切换处理。
2、 如权利要求 1所述的方法, 其特征在于, 所述根据所述切换请求消息, 进行 rSRVCC切换处理包括:
建立所述目标通用分组无线服务的服务支持节点 SGSN要求建立的承载; 和 /或
不对切换命令进行完整性保护。
3、 如权利要求 1所述的方法, 其特征在于, 所述判断所述切换请求消息所 请求的切换为 rSRVCC切换, 包括:
判断所述切换请求消息中携带 rSRVCC指示。
4、 如权利要求 1所述的方法, 其特征在于, 所述判断所述切换请求消息所 请求的切换为 rSRVCC切换中, 包括:
判断所述切换请求消息中包含的透明容器中携带 rSRVCC指示。
5、 如权利要求 1所述的方法, 其特征在于, 所述判断所述切换请求消息所 请求的切换为 rSRVCC切换中, 包括:
判断所述切换请求消息中包含的透明容器中携带的 iu接口实例参数的值为 1 , 而且所述透明容器中包含电路域承载 CS RAB。
6、 如权利要求 1所述的方法, 其特征在于, 所述判断所述切换请求消息所 请求的切换为 rSRVCC切换, 包括:
判断所述切换请求消息中包含的透明容器中携带电路域承载 CS RAB且所 述目标无线网络控制器 RNC没有接收到来自目标移动交换中心 MSC的移动交 换中心切换请求。
7、 如权利要求 1所述的方法, 其特征在于, 所述判断所述切换请求消息所 请求的切换为 rSRVCC切换, 包括:
判断所述切换请求消息中包含的透明容器中携带电路域承载 CS RAB且所 述透明容器不携带包交换域承载 PS RAB。
8、 如权利要求 1所述的方法, 其特征在于, 所述判断所述切换请求消息所 请求的切换为 rSRVCC切换, 包括:
判断所述切换请求消息中包含的透明容器中不包含安全参数, 且所述透明 容器不包含终端历史信息参数;
或者
判断所述切换请求消息中包含的透明容器中不包含安全参数, 且所述透明 容器中包含的终端历史信息参数中包含的是通用移动通信***陆地无线接入网 UTRAN小区信息。
9、 一种反向语音连续性 rSRVCC切换装置, 其特征在于, 包括:
接收模块, 用于接收目标通用分组无线服务的服务支持节点 SGSN发送的 切换请求消息;
判断模块, 用于判断所述切换请求消息所请求的切换为 rSRVCC切换; 处理模块, 用于根据所述切换请求消息, 进行 rSRVCC切换处理。
10、 如权利要求 9所述的装置, 其特征在于, 所述处理模块包括: 建立单元, 用于建立所述目标通用分组无线服务的服务支持节点 SGSN要 求建立的 7 载; 和 /或
控制单元, 用于控制不对切换命令进行完整性保护。
11、 如权利要求 9所述的装置, 其特征在于, 所述判断模块包括: 第一判断单元,用于判断所述目标通用分组无线服务的服务支持节点 SGSN 在切换请求消息中是否携带 rSRVCC指示, 若是, 则判断所述切换请求消息所 请求的切换为 rSRVCC切换。
12、 如权利要求 9所述的装置, 其特征在于, 所述判断模块包括: 第二判断单元, 用于判断所述切换请求消息中包含的透明容器中是否携带 rSRVCC指示, 若是, 则判断所述切换请求消息所请求的切换为 rSRVCC切换。
13、 如权利要求 9所述的装置, 其特征在于, 所述判断模块包括: 第三判断单元, 用于判断所述切换请求消息中包含的透明容器中携带的 iu 接口实例参数的值是否为 1 , 而且所述透明容器中包含电路域承载 CS RAB, 若
是, 则判断所述切换请求消息所请求的切换为 rSRVCC切换。
14、 如权利要求 9所述的装置, 其特征在于, 所述判断模块包括: 第四判断单元, 用于判断所述切换请求消息中包含的透明容器中是否携带 电路域承载 CS RAB且所述 rSRVCC切换装置没有接收到来自目标移动交换中 心 MSC 的移动交换中心切换请求, 则判断所述切换请求消息所请求的切换为 rSRVCC切换。
15、 如权利要求 9所述的装置, 其特征在于, 所述判断模块包括: 第五判断单元, 用于判断所述切换请求消息中包含的透明容器中是否携带 电路域承载 CS RAB, 且所述透明容器中不携带包交换域承载 PS RAB, 则判断 该切换请求消息所请求的切换是 rSRVCC切换。
16、 如权利要求 9所述的装置, 其特征在于, 所述判断模块包括: 第六判断单元, 用于判断所述切换请求消息中包含的透明容器中是否不携 带安全参数, 且所述透明容器中不携带终端历史信息参数, 则判断该切换请求 消息所请求的切换是 rSRVCC切换;
或者
判断所述切换请求消息中包含的透明容器中是否不携带安全参数, 且所述 透明容器中携带的终端历史信息参数中包含的是通用移动通信***陆地无线接 入网 UTRAN小区信息, 则判断该切换请求消息所请求的切换是 rSRVCC切换。
17、一种 rSRVCC切换的***,包括源网络接入节点、源移动交换中心 MSC、 目标网络控制节点、 目标网络接入节点, 其特征在于, 所述目标网络接入节点 包含如权利要求 9-16任一项所述的 rSRVCC切换装置。
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201280001305.3A CN103797853B (zh) | 2012-07-11 | 2012-07-11 | 反向语音连续性切换方法、装置及*** |
PCT/CN2012/078507 WO2014008643A1 (zh) | 2012-07-11 | 2012-07-11 | 反向语音连续性切换方法、装置及*** |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2012/078507 WO2014008643A1 (zh) | 2012-07-11 | 2012-07-11 | 反向语音连续性切换方法、装置及*** |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2014008643A1 true WO2014008643A1 (zh) | 2014-01-16 |
Family
ID=49915320
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2012/078507 WO2014008643A1 (zh) | 2012-07-11 | 2012-07-11 | 反向语音连续性切换方法、装置及*** |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN103797853B (zh) |
WO (1) | WO2014008643A1 (zh) |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102378297A (zh) * | 2010-08-23 | 2012-03-14 | 中兴通讯股份有限公司 | 一种终端能力上报的方法及*** |
WO2012046930A1 (en) * | 2010-10-04 | 2012-04-12 | Lg Electronics Inc. | Device and method for performing an rsrvcc procedure |
Family Cites Families (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2011120181A (ja) * | 2009-12-07 | 2011-06-16 | Ntt Docomo Inc | 移動通信システム及び無線基地局 |
-
2012
- 2012-07-11 CN CN201280001305.3A patent/CN103797853B/zh active Active
- 2012-07-11 WO PCT/CN2012/078507 patent/WO2014008643A1/zh active Application Filing
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102378297A (zh) * | 2010-08-23 | 2012-03-14 | 中兴通讯股份有限公司 | 一种终端能力上报的方法及*** |
WO2012046930A1 (en) * | 2010-10-04 | 2012-04-12 | Lg Electronics Inc. | Device and method for performing an rsrvcc procedure |
Non-Patent Citations (1)
Title |
---|
HUAWEI.: "RAN Impacts of Using Non-DTM Handover Procedure for UTRAN Network.", 3GPP R3-120561., 1 March 2012 (2012-03-01) * |
Also Published As
Publication number | Publication date |
---|---|
CN103797853B (zh) | 2017-06-27 |
CN103797853A (zh) | 2014-05-14 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20200366525A1 (en) | Method, device, and system for controlling tunnel identifier allocation | |
US8532046B2 (en) | Method, system, and device for network handoff | |
US9380496B2 (en) | Method of handover of circuit-switched voice call to packet-switched voice call | |
JP5623630B2 (ja) | ショートメッセージを処理する方法、装置、及びシステム | |
WO2008134986A1 (fr) | Procédé, système et dispositif pour la négociation de fonctions de sécurité | |
WO2012095014A1 (zh) | 核心网设备和家庭基站及其处理lipa连接的方法 | |
WO2013159659A1 (zh) | 网络分流的方法、基站、和终端 | |
RU2677614C1 (ru) | Способ обработки услуги, относящиеся к нему устройство и система | |
US8059592B2 (en) | Access terminal which handles multiple user connections | |
WO2009127155A1 (zh) | 实现本地交换的方法、装置及*** | |
WO2012048656A1 (zh) | Eps***的会话管理过程的重发起方法和设备 | |
WO2014101042A1 (zh) | 基于重定向的电路域回落的通信方法及通信装置 | |
WO2009062392A1 (fr) | Procédé de transfert de système, système de communication et entité pcrf | |
WO2017143755A1 (zh) | 一种网络切换的方法、装置及用户设备 | |
WO2015062065A1 (zh) | 一种与分组数据网络建立连接的装置、设备及方法 | |
WO2015180141A1 (zh) | 一种业务路径变更方法及装置 | |
WO2016045029A1 (zh) | 一种处理电路交换业务的方法及终端 | |
WO2011134408A1 (zh) | 选择性ip数据分流激活的通知及输出方法、***和设备 | |
WO2014008667A1 (zh) | 切换到电路交换域的方法、装置和*** | |
WO2015123945A1 (zh) | 最优路径的建立方法、mme及网关、计算机存储介质 | |
WO2014008643A1 (zh) | 反向语音连续性切换方法、装置及*** | |
WO2020168913A1 (zh) | 切换方法、装置及通信设备 | |
WO2015070425A1 (zh) | 一种电路域回落用户设备识别的方法及设备 | |
WO2008131682A1 (fr) | Procédé, appareil et système de relocalisation de terminal | |
WO2011035557A1 (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: 12881102 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: 12881102 Country of ref document: EP Kind code of ref document: A1 |