WO2012097509A1 - 切换方法和移动管理网元 - Google Patents

切换方法和移动管理网元 Download PDF

Info

Publication number
WO2012097509A1
WO2012097509A1 PCT/CN2011/070391 CN2011070391W WO2012097509A1 WO 2012097509 A1 WO2012097509 A1 WO 2012097509A1 CN 2011070391 W CN2011070391 W CN 2011070391W WO 2012097509 A1 WO2012097509 A1 WO 2012097509A1
Authority
WO
WIPO (PCT)
Prior art keywords
srvcc
network element
mobility management
management network
available
Prior art date
Application number
PCT/CN2011/070391
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 华为技术有限公司
Priority to ES11855931T priority Critical patent/ES2748114T3/es
Priority to JP2013549689A priority patent/JP5655958B2/ja
Priority to EP19186666.4A priority patent/EP3627894B1/en
Priority to EP11855931.9A priority patent/EP2661123B1/en
Priority to CN201180000804.6A priority patent/CN102714831B/zh
Priority to BR112013018552-0A priority patent/BR112013018552B1/pt
Priority to PCT/CN2011/070391 priority patent/WO2012097509A1/zh
Publication of WO2012097509A1 publication Critical patent/WO2012097509A1/zh
Priority to US13/945,026 priority patent/US10582424B2/en
Priority to US16/798,734 priority patent/US11438809B2/en

Links

Classifications

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

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a handover method and a mobility management network element. Background technique
  • Evolved Universal Mobile Telecommunication System Territorial Radio Access Network E-UTRAN
  • EPC Evolved Packet Core Network
  • EPS Evolved Packet System
  • IP Internet Protocol
  • IMS Internet Multimedia Subsystem
  • SRVCC Single Radio Voice Call Continuity
  • GERAN GSM EDGE Radio Access Network
  • UTRAN Terrestrial Radio Access Network
  • CS Circuit Domain
  • PS Switch to 3GPP2 1xCS Packet Switched
  • SRVCC technology also enables switching from UTRAN High Speed Packet Access (HSPA) to GERAN/UTRAN.
  • HSPA High Speed Packet Access
  • the radio access network element only knows the user equipment (User Equipment/Mobile Station; UE/MS, hereinafter collectively referred to as UE) and the mobility management network element (for different wireless communication networks, it may be a mobility management entity (Mobility Management Entity; The MME or the GPRS support GPRS Support Node (SGSN) and other network elements support SRVCC, and the SRVCC can be triggered by the user to use the SRVCC. .
  • UE User Equipment/Mobile Station
  • UE User Equipment/Mobile Station
  • UE User Equipment/Mobile Station
  • SGSN GPRS Support Node
  • SRVCC can be triggered by the user to use the SRVCC.
  • the mobility management network element when the mobility management network element receives the attach request/location update request message sent by the user equipment, the UE has the SRVCC capability, the subscription data sent from the home subscription data server, and the user permission to use the SRVCC and When the mobile management network element is configured to support the SRVCC, the mobility management network element sends an initial context setup request message to the radio access network element to indicate that the radio access network element network element can perform the SRVCC operation.
  • the mobile management network element on the target side cannot correctly know whether the user is allowed to use the SRVCC, so that the target side radio access network element cannot correctly learn whether SRVCC operations can be performed.
  • the target side wireless access element incorrectly triggers the SRVCC handover, which causes the SRVCC handover to fail, which wastes a lot of signaling waste of related interactions; or may cause the SRVCC handover to be performed and the user voice service to be interrupted.
  • the embodiment of the present invention provides a handover method and a mobility management network element, so as to solve the problem that the target-side radio access network element cannot know whether the SRVCC operation can be performed and the SRVCC handover is incorrectly triggered, thereby causing the SRVCC handover failure, which wastes a large amount of correlation.
  • the signaling waste of the interaction, and the possible failure of the SRVCC handover, and the interruption of the user voice service.
  • the embodiment of the invention provides a handover method, including:
  • the target side mobility management network element receives the forwarding redirection request message sent by the source side mobility management network element, where the forwarding redirection request message includes the single channel voice call continuous SRVCC available information; the target side mobility management network element is connected to the target side The incoming network element sends a first request message carrying the SRVCC operation possible information.
  • the embodiment of the invention provides a mobility management network element, including:
  • a receiving module configured to receive a forwarding redirection request message sent by the source side mobility management network element, where the forwarding redirection request message includes a single channel voice call continuous SRVCC available information;
  • a sending module configured to send, to the target side access network element, information about carrying the SRVCC operation First request message.
  • the mobile management network element at the source end indicates whether the target side mobility management network element SRVCC is available by forwarding the redirection request, so that the target side mobility management network element correctly indicates the target side wireless connection.
  • the network element SRVCC is available, so that the target side radio access network element can correctly trigger the SRVCC handover, save the signaling interaction of the network, and ensure the normal use of the user voice service.
  • FIG. 1 is a flowchart of a first embodiment of a handover method provided by the present invention
  • FIG. 2 is a flowchart of a second embodiment of a handover method provided by the present invention.
  • FIG. 3 is a flowchart of a third embodiment of a handover method provided by the present invention.
  • FIG. 4 is a schematic structural diagram of a first embodiment of a mobility management network element according to the present invention. detailed description
  • FIG. 1 is a flowchart of a first embodiment of a handover method according to the present invention. As shown in FIG. 1, the method includes:
  • the target side mobility management network element receives the forwarding redirection sent by the source side mobility management network element. Requesting a message, the forward redirect request message includes a single channel voice call continuous SRVCC available information;
  • the target side mobility management network element sends a first request message carrying the SRVCC operation possibility information to the target side access network element.
  • the source-side mobility management network element and the target-side mobility management network element may be a mobility management device such as an MME or an SGSN, and a source-side radio access network element and a target-side radio access network element. It can be an evolved base station (Evolved Node B; eNodeB), or a radio network controller (RNC).
  • eNodeB evolved Node B
  • RNC radio network controller
  • the source-side mobility management network element receives the handover request message or the redirect request message sent by the source-side radio access network element.
  • the source side mobility management network element needs to inform the target side management network element whether the user is permitted to use the SRVCC, or the SRVCC capability of the UE and whether the user is permitted to use the SRVCC, thereby Enable the target side mobility management network element to enable the SRVCC capability of the UE, whether the user is permitted to use the SRVCC, and whether the target side mobility management network element supports the SRVCC to notify the target side radio access network element, thereby enabling the target side radio access network element Perform the correct SRVCC switching operation.
  • the source side mobility management network element sends a forwarding redirect request to the target side mobility management network element, including
  • the SRVCC available information can be used to indicate that the user SRVCC is available.
  • the SRVCC available information may specifically include: a single channel voice call serial session transmission number (Session Transfer Number for SR-VCC, STN-SR) and a related mobile station international ISDN number (C-MSISDN) At least one of; or, SRVCC permission information, such as SRVCC is Allowed; or SRVCC operation possible information, for example: SRVCC Operation Possible.
  • the user SRVCC available may include: the user license to use the SRVCC.
  • the user SRVCC may also include both the user license to use the SRVCC and the user equipment to have the SRVCC capability.
  • the SRVCC available information can also be used to indicate:
  • the source side mobility management network element SRVCC can
  • the source side mobility management network element S RV CC may be specifically supported by the source side mobility management network element to support SRVCC or support the Sv interface.
  • the target-side mobility management network element After the target-side mobility management network element receives the forwarding redirection request sent by the source-side mobility management network element, the target-side mobility management network element sends a first request message to the target-side radio access network network element, where the first request message may be A handover request message or a redirect request message, where the first request message carries SRVCC operation possible information. Specifically include:
  • the target side mobility management network element may include the SRVCC operation possibility in the first request message sent to the target side radio access network element.
  • the SRVCC Operation Possible the SRVCC operation may indicate that the user SRVCC is available and the target MME SRVCC is available (if the indication is not included, the SRVCC operation is unavailable); or, the target mobile management network element may The SRVCC Operation Possible indication is included in the first request message sent to the target side radio access network element, and the SRVCC operation may indicate that the value is true (TRUE) or 1, indicating that the SRVCC operation is available (if SRVCC) When the value indicated by the operation may be false (FALSE) or 0, it indicates that the SRVCC operation is not available, that is, at least one SRVCC in the user and the target side MME is unavailable.
  • the mobility management network element at the source end indicates whether the target side mobility management network element SRVCC is available by forwarding the redirection request, so that the target side radio access network element can correctly trigger the SRVCC handover, saving the network. Signaling interaction ensures the normal use of voice services.
  • FIG. 2 is a flowchart of a second embodiment of a handover method according to the present invention.
  • This embodiment is described by taking an example of a handover process performed by a UE attached to an E-UTRAN, where the source and destination mobile management network elements are both The MME, the source side and the target side radio access network element are both eNodeBs. It should be noted that this embodiment only provides a specific application scenario of the handover method, but does not limit the embodiment of the present invention.
  • the method includes: S201: A source-side eNodeB decision initiates an S1-based handover (The source eNodeB Decides to initiate an S1 -based handover to the target eNodeB ).
  • the source side eNodeB sends a Handover Required message (ie, a second request message) to the source side MME.
  • a Handover Required message ie, a second request message
  • the source MME sends a Forward Relocation Request message to the target MME.
  • the foregoing forwarding relocation request message includes SRVCC available information, indicating that the user single channel voice call is continuously available (ie, the user SRVCC is available).
  • the content of the user SRVCC can include, but is not limited to, the following methods:
  • SRVCC User licenses use SRVCC; or, user licenses use SRVCC and user equipment has SRVCC capabilities.
  • the above SRVCC available information may also indicate that: the source side mobility management network element SRVCC is available.
  • the source-side mobility management network element SRVCC may be specifically supported by the source-side mobile management network element to support the SRVCC or the Sv interface.
  • the user equipment has the SRVCC capability, and the user equipment may support the S RVCC.
  • SRVCC available information may specifically be used to indicate any of the following:
  • the user SRVCC is available and the source side mobility management network element SRVCC is available;
  • the user license uses SRVCC, the user equipment has SRVCC capability and the source side mobility management network element SRVCC is available.
  • the specific implementation of the foregoing S RVCC information may include, but is not limited to, the following manners: (1)
  • the foregoing SRVCC available information includes: a single channel voice call continuous session transmission number (STN-SR) and an associated mobile station international ISDN number (C- At least one of MSISDN); or, SRVCC permission information, such as SRVCC is Allowed; or SRVCC operation may be information, such as SRVCC Operation Possible.
  • STN-SR single channel voice call continuous session transmission number
  • C- At least one of MSISDN mobile station international ISDN number
  • SRVCC permission information such as SRVCC is Allowed
  • SRVCC operation may be information, such as SRVCC Operation Possible.
  • the specific name of the above information or indication is not limited in this embodiment.
  • the foregoing STN-SR and/or C-MSISDN, or SRVCC permission information, or SRVCC operation possibility information may be used to indicate any one of the foregoing six indication contents, for example, indicating that the user SRVCC is available, or indicating that the user SRVCC is available and the source
  • the side mobility management network element SRVCC is available, or indicates that the user is permitted to use the SRVCC, or indicates that the user is permitted to use the SRVCC and the user equipment has the SRVCC capability, and the like.
  • the foregoing SRVCC available information may further include: SRVCC capability information, such as an SRVCC capability indication, where the SRVCC capability information may be used to indicate that the user equipment has SRVCC capability.
  • SRVCC capability information such as an SRVCC capability indication
  • the specific name of the above information or indication is not limited in this embodiment.
  • the scenario in which the SRVCC capability information is included in the SRVCC available information includes, but is not limited to: the foregoing STN-SR and/or C-MSISDN or SRVCC grant information or the SRVCC operation possibility information indicates that the user permits the use of the SRVCC, and the foregoing SRVCC capability information may indicate the user.
  • the device has SRVCC capabilities.
  • the above STN-SR and/or C-MSISDN or SRVCC grant information or SRVCC operation possible information together with the above SRVCC capability information indicate that the user is permitted to use the SRVCC and that the user equipment has SRVCC capability or the user SRVCC is available.
  • the source MME may obtain the SRVCC available information by using, but not limited to, the following manner:
  • the UE When the UE is attached to the network for the first time, the UE needs to send an attach request to the source MME (Attach)
  • the UE sends a location update request to the source MME (the source MME is the mobile management network element of the target side in the location update process), For example: Tracking Area Update Request (TAU) message.
  • TAU Tracking Area Update Request
  • the UE may carry an SRVCC capability indication in the attach request message/tracking area update request message, for example, the SRVCC capability indication may be included in the attach request message/tracking area. In the "MS Network Capability" cell in the new request message.
  • the source MME may send a location update request to the home subscription data server, and after receiving the location update request, the home subscription data server sends the location update request to the mobility management.
  • the network element returns the user subscription information of the UE. If the user permits the use of the SRVCC (SRVCC subscribed allowed), the user subscription data of the UE will include the STN-SR and the C-MSISDN, that is, the source MME can learn the user from the home subscription data server. License to use SRVCC.
  • the home subscription data server at this time is a Home Subscriber Server (HSS).
  • HSS Home Subscriber Server
  • the source side MME may use the SRVCC according to the user license or the user equipment has the SRVCC capability and the user license uses the SRVCC to know that the user SRVCC is available.
  • the source side MME can learn that the source (MME MME) SRVCC is available according to the configuration information.
  • the target side MME sends a Create Session Request message to the target side serving gateway.
  • the target side MME receives a Create Session Response message sent by the target side serving gateway.
  • the target side MME sends a Handover Request message (ie, a first request message) to the target side eNodeB.
  • a Handover Request message ie, a first request message
  • the foregoing handover request message may include a single channel voice call continuous operation (SRVCC operation possible).
  • the target side MME knows that the user SRVCC is available (ie, the UE permits the use of the SRVCC or the UE to use the SRVCC and the UE has the SRVCC capability), then when the target side MME SRVCC is available (ie, supports the SRVCC), for example, the MME supports the Sv interface to complete the SRVCC handover, then
  • the target MME may include SRVCC operation possibility information in the handover request message sent to the target side eNodeB, indicating that the user SRVCC is available and the target side MME SRVCC is available, and the target side eNodeB may record the SRVCC operation possible information for determining whether SRVCC switching can be triggered.
  • the target side MME may perform the handover request sent to the target side eNodeB.
  • the SRVCC operation possible indicator is included, and the SRVCC operation may indicate that the user SRVCC is available and the target MME SRVCC is available. If the indication is not included, the SRVCC operation is unavailable (ie, the user and the target) At least one SRVCC of the side MME is unavailable; or the target MME may include an SRVCC operation possible indicator in the handover request message sent to the target side eNodeB, if the value of the SRVCC operation may indicate True (TRUE) or 1 is used to indicate that the user SRVCC is available and the target side MME SRVCC is available. If the SRVCC operation may indicate a value of FALSE or 0, it indicates that the SRVCC operation is unavailable (ie, user and At least one SRVCC in the target side MME is unavailable).
  • target 4 MME receives ⁇ : target 4, eNodeB sends handover response (Handover
  • Steps of performing PS HO may include, but are not limited to, creating a temporary data forwarding tunnel, updating uplink and downlink user planes, performing tracking area update, and deleting temporary data forwarding tunnels.
  • the target MME when the target MME sends a UE CONTEXT MODIFICATION REQUEST message to the target side eNodeB, the target MME may also be in the user equipment context modification request message.
  • the SRVCC operation possible information is included, and is not limited to whether the handover request message in the previous step S206 includes the SRVCC operation possibility information.
  • step S206 For the content of the SRVCC operation possible information and the implementation of the foregoing user equipment context modification request message, refer to the description of step S206, and details are not described herein again.
  • FIG. 3 is a flowchart of a third embodiment of a handover method provided by the present invention.
  • This embodiment uses a service radio network subsystem of a UE attached to a UTRAN (High Speed Packet Access (HSPA)). Serving Radio Network Subsystem; SRNS) Redirection (Relocation) is described as an example.
  • the source and destination mobile management NEs are both SGSNs, and the source and destination side radio access network elements are RNC. It should be noted that this embodiment only provides a specific application scenario of the handover method, but does not limit the embodiment of the present invention. As shown in FIG. 3, the method includes:
  • S301 The source side RNC decision initiation service radio network subsystem redirection (SRNS relocation).
  • SRNS relocation The source side RNC decision initiation service radio network subsystem redirection (SRNS relocation).
  • the source side RNC sends a Relocation Required message (ie, a second request message) to the source side SGSN.
  • the source SGSN sends a Forward Relocation Request message to the target SGSN.
  • the foregoing forwarding relocation request message includes SRVCC available information, indicating that the user single channel voice call is continuously available (user SRVCC is available).
  • the specific content of the user SRVCC may include, but is not limited to, the following modes: the user licenses to use the SRVCC; or the user permits the use of the SRVCC and the user equipment has the SRVCC capability.
  • the above SRVCC available information may also indicate that: the source side mobility management network element SRVCC is available.
  • the source-side mobility management network element S RVCC may be specifically supported by the source-side mobility management network element to support the S RVCC or the S V interface.
  • the user equipment has SRVCC capability, and specifically the user equipment supports SRVCC.
  • SRVCC available information may specifically be used to indicate any of the following:
  • the user SRVCC is available and the source side mobility management network element SRVCC is available;
  • SRVCC user license to use SRVCC and source-side mobility management network element SRVCC available
  • SRVCC user license to use SRVCC, user equipment with SRVCC capability and source-side mobility management network element SRVCC available.
  • SRVCC available information may include, but is not limited to, the following manners:
  • the above SRVCC available information includes: Single channel voice call continuous session transmission number (STN-SR) and at least one of the associated mobile station international ISDN number (C-MSISDN); or, SRVCC grant information, such as SRVCC is Allowed; or, SRVCC operation possible information, such as SRVCC operation may indicate (SRVCC Operation Possible ).
  • STN-SR Single channel voice call continuous session transmission number
  • C-MSISDN mobile station international ISDN number
  • SRVCC grant information such as SRVCC is Allowed
  • SRVCC operation possible information such as SRVCC operation may indicate
  • SRVCC Operation Possible The specific name of the above information or indication is not limited in this embodiment.
  • the S RVCC operation possible information may be used to indicate any of the several indication contents listed above, for example, indicating that the user SRVCC is available, or indicating that the user SRVCC is available and the source side mobility management network element SRVCC is available, or indicating that the user is permitted to use the SRVCC. , or indicate that the user is permitted to use SRVCC and the user equipment has SRVCC capabilities and so on.
  • the above SRVCC available information may also include: SRVCC capability information, for example
  • the SRVCC capability indication can be used to indicate that the user equipment has SRVCC capability.
  • the specific name of the above information or indication is not limited in this embodiment.
  • the scenario in which the SRVCC capability information is included in the SRVCC available information includes, but is not limited to: the foregoing STN-SR and/or C-MSISDN or SRVCC grant information or the SRVCC operation possibility information indicates that the user permits the use of the SRVCC, and the foregoing SRVCC capability information may indicate the user.
  • the device has SRVCC capabilities.
  • the above STN-SR and/or C-MSISDN or SRVCC grant information or SRVCC operation possible information and the above SRVCC capability information indicate that the user is permitted to use the SRVCC and that the user equipment has SRVCC capability or the user SRVCC is available.
  • the source side SGSN sends the redirect request message to the target side SGSN, the source side
  • the SGSN can learn the above SRVCC available information by, but not limited to, the following:
  • Update request for example: Routing Area Update (RAU).
  • RAU Routing Area Update
  • the UE may carry an SRVCC capability indication (SRVCC capability) in the attach request message or the routing area update request. Indication), for example, the SRVCC capability indication may be included in an "MS Network Capability" cell in the Attach Request message/Routing Area Update Request message.
  • the source side SGSN may send a location update request to the home subscription data server, and after receiving the location update request, the home subscription data server sends the location update request to the mobile management network.
  • the element returns the user subscription information of the UE. If the user permits the use of SRVCC (SRVCC subscribed allowed), the user subscription data of the UE will include the STN-SR and the C-MSISDN, that is, the source side SGSN can learn the user from the home subscription data server. License to use SRVCC.
  • the home subscription data server may be a home location register (HLR) or an HSS device.
  • the source side SGSN may use the SRVCC according to the user license or the user equipment has
  • SRVCC capabilities and user licenses use SRVCC to know that user SRVCC is available.
  • the source side SGSN can learn that the source (MME MME) SRVCC is available according to the configuration information.
  • the target side SGSN sends a Create Session Request message to the target side serving gateway.
  • S404 and S405 are performed; otherwise, if the target side SGSN uses the Gn/Gp interface, S404 and S405 are not executed.
  • the target side SGSN receives a Create Session Response message sent by the target side service gateway.
  • the target side SGSN sends a Relocation Request message (ie, the first request message) to the target side RNC.
  • the foregoing handover request message may include a single channel voice call continuous operation (SRVCC operation possible).
  • the target side SGSN learns that the user SRVCC is available (ie, the user permits the use of SRVCC or the UE grants the use of SRVCC and the UE has the SRVCC capability), then when the target side SGSN SRVCC is available (ie, supports SRVCC), for example, the SGSN supports the Sv interface to complete the SRVCC handover, then
  • the target side SGSN may include the SRVCC operation possibility in the relocation request message sent to the target side RNC.
  • the target side RNC may record the SRVCC operation possible information for triggering the SRVCC handover.
  • the target side SGSN may include an SRVCC operation possible indicator in the handover request message sent to the target side eNodeB, where the SRVCC operation may indicate that the user SRVCC is available and the target side SGSN SRVCC is available. If the indication is not included, it indicates that the SRVCC operation is unavailable (ie, at least one SRVCC in the user and the target side SGSN is unavailable); or, the target side SGSN may include the SRVCC operation possibility in the handover request message sent to the target side eNodeB.
  • SRVCC operation possible indicator if the value of the SRVCC operation may indicate true (TRUE) or 1, indicating that the user SRVCC is available and the target side SGSN SRVCC is available, if the SRVCC operation may indicate a false value (FALSE) or 0 indicates that the SRVCC operation is not available (ie, at least one SRVCC in the user and the target side SGSN is not available).
  • the target side SGSN receives the target side RNC to send a Relocation Response message.
  • the other steps of performing the SRNS Relocation may include, but are not limited to, updating the uplink and downlink user planes, performing routing area update, and the like.
  • the SRVCC operation possible information may be included in the shared identification message.
  • the time is not limited to whether the handover request message in the previous step S306 contains SRVCC operation possible information.
  • the storage medium may be a magnetic disk, an optical disk, or a read-only storage memory. (Read-Only Memory, ROM) or random access memory (RAM).
  • the mobility management network element includes: a receiving module 1 1 and a sending module 12;
  • the receiving module 11 is configured to receive a forwarding redirection request message sent by the source side mobility management network element, where the forwarding redirection request message includes a single channel voice call continuous SRVCC available information;
  • the sending module 12 is configured to send, to the target side access NE, a first request message that carries the SRVCC operation possible information.
  • the SRVCC available information included in the Forward Redirection Request message received by the receiving module 11 can be used to indicate that the user SRVCC is available.
  • the SRVCC available information included in the forwarding redirection request message received by the receiving module 11 is further used to indicate that the source side mobility management network element SRVCC is available.
  • the user SRVCC is available, including: user license to use SRVCC, or user license to use SRVCC and user equipment to have SRVCC capability.
  • the SRVCC available information included in the forwarding redirection request message received by the receiving module 11 may include:
  • SRVCC may operate with information.
  • the sending module 12 carries the first request message sent by the target side access network element.
  • the SRVCC operation may be used to indicate that the user SRVCC is available and the target side management network element SRVCC is available.
  • the mobile management network element provided by the embodiment of the present invention is the target side mobile management network element involved in the handover method provided by the present invention.
  • the specific implementation process refer to the foregoing method embodiment, and details are not described herein.
  • the mobile management network element at the source end forwards by redirecting The request indicates that the target side mobile management network element SRVCC is available, so that the target side radio access network element can correctly trigger the SRVCC handover, save the signaling interaction of the network, and ensure the normal use of the user voice service.

Landscapes

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

Description

切换方法和移动管理网元
技术领域
本发明涉及通信技术领域， 特别涉及一种切换方法和移动管理网元。 背景技术
演进通用移动通信***陆地无线接入网 （ Evolved Universal Mobile Telecommunication System Territorial Radio Access Network; E-UTRAN ) 和演进分组核心网 （ Evolved Packet Core Network; EPC )构成了演进分组 ***（ Evolved Packet System; EPS )。 演进分组***通常采用互联网协议 ( Internet Protocol; IP ) 多媒体子*** ( IP Multimedia Subsystem; IMS ) 提供语音服务。
由于 E-UTRAN部署初期无法实现全网覆盖， 因此在 E-UTRAN覆盖范 围之外无法提供 IMS语音， 为了保持在 E-UTRAN覆盖边界处的语音呼叫连 续性， 则第三代合作伙伴（ The 3rd Generation Partnership Project; 3GPP ) 定义了单信道语音呼叫连续 （ Single Radio Voice Call Continuity; SRVCC ) 技术， 实现从 E-UTRAN 切换到增强无线接入网络（GSM EDGE Radio Access Network; GERAN ) 或陆地无线接入网 （UMTS Territorial Radio Access Network; UTRAN ) 的电路域 ( Circuite Switching; CS ) , 或切换 到 3GPP2 1xCS的分组交换 ( Packet Switched; PS )到 CS切换。 此外， SRVCC技术还实现从 UTRAN高速分组接入（ High Speed Packet Access, HSPA)切换到 GERAN/UTRAN。其中， 无线接入网网元只有在获知用户设备 ( User Equipment/Mobile Station; UE/MS, 以下统称 UE )和移动管理网元 (对于不同的无线通信网络可以是移动管理实体 （Mobility Management Entity; MME )或月良务通用分组无线技术（ General Packet Radio Service; GPRS ) 支持节点 (Serving GPRS Support Node; SGSN)等网元）都支持 SRVCC,以及用户许可使用 SRVCC的场景下，才能触发执行 SRVCC切换。 现有技术在附着或位置更新流程中， 当移动管理网元接收用户设备发送 的附着请求 /位置更新请求消息获知 UE具有 SRVCC能力、 从归属地签约数 据服务器发送的签约数据获知用户许可使用 SRVCC以及获知该移动管理网 元支持 SRVCC时， 该移动管理网元向无线接入网网元发送初始上下文建立 请求消息， 指示无线接入网元网元可以执行 SRVCC操作。
然而， 现有技术在分组域切换（ Packet Switched Handover; PS HO ) 流程中， 目标侧的移动管理网元无法正确获知用户是否许可使用 SRVCC, 从 而使得目标侧无线接入网网元无法正确获知是否可以执行 SRVCC操作。进而 导致目标侧无线接入元错误触发 SRVCC切换而造成 SRVCC切换失败， 浪费 大量相关交互的信令浪费； 或者， 可能导致无法执行 SRVCC切换， 用户语音 业务的中断。 发明内容
本发明实施例提供了一种切换方法和移动管理网元， 以解决现有技术 目标侧无线接入网网元无法获知是否可以执行 SRVCC操作而错误触发 SRVCC切换而造成 SRVCC切换失败， 浪费大量相关交互的信令浪费， 以及可能导致的 SRVCC切换失败， 用户语音业务中断的问题。
本发明实施例提供一种切换方法， 包括：
目标侧移动管理网元接收源侧移动管理网元发送的转发重定向请求消 息， 所述转发重定向请求消息包含单信道语音呼叫连续 SRVCC可用信息； 所述目标侧移动管理网元向目标侧接入网元发送携带 SRVCC操作可 能信息的第一请求消息。
本发明实施例提供一种移动管理网元， 包括：
接收模块， 用于接收源侧移动管理网元发送的转发重定向请求消息， 所 述转发重定向请求消息包含单信道语音呼叫连续 SRVCC可用信息；
发送模块， 用于向目标侧接入网元发送携带 SRVCC操作可能信息的 第一请求消息。
本发明实施例提供的切换方法和移动管理网元， 源端的移动管理网元通 过转发重定向请求， 指示目标侧移动管理网元 SRVCC是否可用， 使得目标 侧移动管理网元正确指示目标侧无线接入网网元 SRVCC可用， 从而使目标 侧无线接入网网元能够正确触发 SRVCC切换， 节约网络的信令交互， 保证 用户语音业务的正常使用。 附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案， 下面将对实 施例或现有技术描述中所需要使用的附图作一简单地介绍， 显而易见地， 下 面描述中的附图是本发明的一些实施例， 对于本领域普通技术人员来讲， 在 不付出创造性劳动性的前提下， 还可以根据这些附图获得其他的附图。
图 1为本发明提供的切换方法第一实施例的流程图；
图 2为本发明提供的切换方法第二实施例的流程图；
图 3为本发明提供的切换方法第三实施例的流程图；
图 4为本发明提供的移动管理网元第一实施例的结构示意图。 具体实施方式
为使本发明实施例的目的、 技术方案和优点更加清楚， 下面将结合本 发明实施例中的附图， 对本发明实施例中的技术方案进行清楚、 完整地描 述， 显然， 所描述的实施例是本发明一部分实施例， 而不是全部的实施例。 基于本发明中的实施例， 本领域普通技术人员在没有作出创造性劳动前提 下所获得的所有其他实施例， 都属于本发明保护的范围。
图 1为本发明提供的切换方法第一实施例的流程图， 如图 1所示， 该 方法包括：
S101、 目标侧移动管理网元接收源侧移动管理网元发送的转发重定向请 求消息， 该转发重定向请求消息包含单信道语音呼叫连续 SRVCC可用信息；
S102、 目标侧移动管理网元向目标侧接入网元发送携带 SRVCC操作可 能信息的第一请求消息。
其中， 根据用户设备所在网络的不同， 源侧移动管理网元和目标侧移动 管理网元可以为 MME或 SGSN等移动管理设备； 源侧无线接入网网元和目标 侧无线接入网网元可以为演进基站（ Evolved Node B; eNodeB ), 或者无线 网络控制器 ( Radio Network Controller; RNC )等设备。
在切换流程中， 源侧移动管理网元接收到源侧无线接入网网元发送的切 换请求消息或者重定向请求消息后。 为了使目标侧无线接入网网元正确执行 切换操作， 源侧移动管理网元需要告知目标侧管理网元该用户是否许可使用 SRVCC, 或者该 UE的 SRVCC能力以及该用户是否许可使用 SRVCC, 从而 使目标侧移动管理网元能够将 U E的 S R V C C能力、 用户是否许可使用 SRVCC, 以及目标侧移动管理网元是否支持 SRVCC告知目标侧无线接入网 网元， 从而使目标侧无线接入网网元执行正确的 SRVCC切换操作。
源侧移动管理网元向目标侧移动管理网元发送转发的重定向请求中包括
SRVCC可用信息， 该 SRVCC可用信息可以用于指示用户 SRVCC可用。
其中， SRVCC可用信息具体可以包括： 单信道语音呼叫连续会话传输号 码（Session Transfer Number for SR-VCC, STN-SR )和相关移动台国际 ISDN号码 ( Correlation Mobile Subscriber International ISDN Number, C-MSISDN ) 中的至少一个； 或者， SRVCC许可信息， 例如 SRVCC许可指 示（SRVCC is Allowed ); 或者， SRVCC操作可能信息， 例如： SRVCC操作 可能指示（ SRVCC Operation Possible )。
所述用户 SRVCC可用可以包括： 用户许可使用 SRVCC。 或者， 用户 SRVCC可用还可以既包括用户许可使用 SRVCC , 还包括用户设备具有 SRVCC能力。
此外， SRVCC可用信息还可以用于指示： 源侧移动管理网元 SRVCC可 用， 源侧移动管理网元 S RV C C可用具体可以是源侧移动管理网元支持 SRVCC或支持 Sv接口等。
目标侧移动管理网元接收到源侧移动管理网元发送的转发重定向请求 后， 目标侧移动管理网元向目标侧无线接入网网元发送第一请求消息， 该第 一请求消息可以为切换请求消息或重定向请求消息， 该第一请求消息中携带 SRVCC操作可能信息。 具体包括：
如果目标侧移动管理网元支持 SRVCC (即目标侧移动管理网元 SRVCC 可用），则目标侧移动管理网元可以在向目标侧无线接入网网元发送的第一请 求消息中包含 SRVCC操作可能指示 （SRVCC Operation Possible ), 所述 SRVCC操作可能指示用于指示用户 SRVCC可用以及目标侧 MME SRVCC可 用 （若不包含该指示， 则表明 SRVCC操作不可用）； 或者， 则目标侧移动管 理网元可以在向目标侧无线接入网网元发送的第一请求消息中包含 SRVCC 操作可能指示（ SRVCC Operation Possible ), SRVCC操作可能指示的值为 真（TRUE )或 1 , 则表明 SRVCC操作可用 （若 SRVCC操作可能指示的值为 假（FALSE )或 0时， 则表明 SRVCC操作不可用， 即用户和目标侧 MME中的 至少一个 SRVCC不可用。
本实施例提供的切换方法， 源端的移动管理网元通过转发重定向请求， 指示目标侧移动管理网元 SRVCC是否可用，从而使目标侧无线接入网网元能 够正确触发 SRVCC切换， 节约网络的信令交互， 保证用户语音业务的正常使 用。
图 2为本发明提供的切换方法第二实施例的流程图， 本实施例以在 E-UTRAN附着的 UE进行切换处理为例进行说明， 其中， 源侧和目标侧 的移动管理网元均为 MME, 源侧和目标侧的无线接入网网元均为 eNodeB。 需要说明的是， 本实施例仅给出了切换方法的一个具体应用场 景， 但并不以此作为对本发明实施例的限制。 如图 2所示， 该方法包括： S201、 源侧 eNodeB决策发起基于 S1的切换 （The source eNodeB decides to initiate an S1 -based handover to the target eNodeB ) 。
5202、 源侧 eNodeB向源侧 MME发送切换请求 ( Handover Required ) 消息 （即第二请求消息） 。
5203、 源侧 MME向目标侧 MME发送转发重定向请求 （ Forward Relocation Request ) 消息。
其中， 上述转发重定位请求消息中包含 SRVCC可用信息， 指示用户单信 道语音呼叫连续可用 （即用户 SRVCC可用）。 其中， 所述用户 SRVCC可用具 体内容可以包括但不限于以下几种方式：
用户许可使用 SRVCC; 或者， 用户许可使用 SRVCC以及用户设备具有 SRVCC能力。 此外， 上述 SRVCC可用信息还可以指示： 源侧移动管理网元 SRVCC可用。 其中， 上述源侧移动管理网元 SRVCC可用具体可以是源侧移 动管理网元支持 SRVCC或支持 Sv接口等。 其中， 用户设备具有 SRVCC能力 具体可以是用户设备支持 S RVCC。
综上， 上述 SRVCC可用信息具体可以用于指示以下几种内容中的任一 个：
( 1 )、 用户 SRVCC可用；
( 2 )、 用户 SRVCC可用以及源侧移动管理网元 SRVCC可用；
( 3 )、 用户许可使用 SRVCC;
( 4 )、 用户许可使用 SRVCC以及用户设备具有 SRVCC能力；
( 5 )、 用户许可使用 SRVCC以及源侧移动管理网元 SRVCC可用；
( 6 )、 用户许可使用 SRVCC, 用户设备具有 SRVCC能力以及源侧移动 管理网元 SRVCC可用。
其中， 上述 S RVCC可用信息具体实现可以包括但不限于以下方式： ( 1 )上述 SRVCC可用信息中包含： 单信道语音呼叫连续会话传输号码 ( STN-SR )和相关移动台国际 ISDN号码（ C-MSISDN ) 中的至少一个； 或 者， SRVCC许可信息， 例如 SRVCC许可指示（SRVCC is Allowed ); 或者， SRVCC操作可能信息， 例如 SRVCC操作可能指示 （SRVCC Operation Possible )。 其中， 本实施例中不限制上述信息或指示的具体名称。
其中， 上述 STN-SR和 /或 C-MSISDN , 或者 SRVCC许可信息， 或者 SRVCC操作可能信息可以用于指示上述 6种指示内容中的任意一个， 例如指 示用户 SRVCC可用， 或者指示用户 SRVCC可用以及源侧移动管理网元 SRVCC可用， 或者， 指示用户许可使用 SRVCC , 或者指示用户许可使用 SRVCC以及用户设备具有 SRVCC能力等等。
( 2 ) 上述 SRVCC可用信息中还可以包含： SRVCC能力信息， 例如 SRVCC能力指示 （SRVCC capability indication ), 该 SRVCC能力信息可以 用于指示用户设备具有 SRVCC能力。 其中， 本实施例中不限制上述信息或指 示的具体名称。
其中， 上述 SRVCC可用信息中包含 SRVCC能力信息的场景包含但不限 于： 上述 STN-SR和 /或 C-MSISDN或者 SRVCC许可信息或者 SRVCC操作可 能信息指示用户许可使用 SRVCC, 上述 SRVCC能力信息可以指示用户设备 具有 SRVCC能力。 上述 STN-SR和 /或 C-MSISDN或者 SRVCC许可信息或者 SRVCC操作可能信息以及上述 SRVCC能力信息一同指示用户许可使用 SRVCC以及用户设备具有 SRVCC能力或者用户 SRVCC可用。
其中 ,在源侧 MME向目标侧 MME发送该重定向请求消息之前，源侧 MME 可以通过但不限于以下的方式获知上述 SRVCC可用信息：
当 UE第一次附着在网络中时， UE需要向源侧 MME发送附着请求（Attach
Request ) 消息； 或者， 如果 UE已经附着在网络中， 并且 UE位置发生变化， 贝 UE向源侧 MME(该源侧 MME在位置更新流程中为目标侧的移动管理网元 ) 发送位置更新请求， 例如： 跟踪区域更新请求 （Tracking Area Update Request, TAU )消息。 如果 UE具有 SRVCC能力， 则 UE可以在上述附着请 求消息 /跟踪区域更新请求消息中携带 SRVCC能力指示 （SRVCC capability indication ) , 例如该 SRVCC能力指示可以包含在附着请求消息 /跟踪区域更 新请求消息中的" MS Network Capability"信元中。
另外， 当源侧 MME接收到 UE发送的附着请求消息或位置更新请求消息 后， 可以向归属地签约数据服务器发出位置更新请求， 归属地签约数据服务 器收到该位置更新请求后， 向该移动管理网元返回 UE的用户签约信息， 如果 用户许可使用 SRVCC ( SRVCC subscribed allowed ) , 则 UE的用户签约数 据中将包含 STN-SR和 C-MSISDN , 即源侧 MME可以从归属地签约数据服务 器获知用户许可使用 SRVCC。 其中， 此时的归属地签约数据服务器为归属地 用户月良务器 ( Home Subscriber Server; HSS )。
其中， 源侧 MME可以根据用户许可使用 SRVCC或者用户设备具有 SRVCC能力以及用户许可使用 SRVCC获知用户 SRVCC可用。 其中， 源侧 MME可以根据配置信息获知自身 （源侧 MME ) SRVCC可用。
5204、 目标侧 MME向目标侧服务网关发送创建会话请求 （ Create Session Request ) 消息。
5205、 目标侧 MME接收目标侧服务网关发送的创建会话响应 （ Create Session Response ) 消息。
5206、目标侧 MME向目标侧 eNodeB发送切换请求（ Handover Request ) 消息 （即第一请求消息） 。
其中， 上述切换求请求消息中可以包含单信道语音呼叫连续操作可能信 息 ( SRVCC operation possible )。
若目标侧 MME获知用户 SRVCC可用 （即 UE许可使用 SRVCC或者 UE许 可使用 SRVCC以及 UE具有 SRVCC能力 ),则当目标侧 MME SRVCC可用 (即 支持 SRVCC ), 例如该 MME支持 Sv接口完成 SRVCC切换， 那么目标侧 MME 可以在向目标侧 eNodeB发送的切换请求消息中包含 SRVCC操作可能信息， 指示用户 SRVCC可用以及目标侧 MME SRVCC可用， 则该目标侧 eNodeB可 以记录该 SRVCC操作可能信息， 以用于判别是否可以触发 SRVCC切换。
其中， 具体的， 目标侧 MME可以在向目标侧 eNodeB发送的切换请求消 息中包含 SRVCC操作可能指示（SRVCC operation possible indicator ), 所 述 SRVCC操作可能指示用于指示用户 SRVCC可用以及目标侧 MME SRVCC 可用， 若不包含该指示， 则表明 SRVCC操作不可用 （即用户和目标侧 MME 中的至少一个 SRVCC不可用）； 或者， 目标侧 MME可以在向目标侧 eNodeB 发送的切换请求消息中包含 SRVCC操作可能指示 （ SRVCC operation possible indicator ), 若所述 SRVCC操作可能指示的值为真（TRUE )或 1时， 用于指示用户 SRVCC可用以及目标侧 MME SRVCC可用， 若所述 SRVCC操 作可能指示的值为假（FALSE )或 0时， 则表明表明 SRVCC操作不可用 （即 用户和目标侧 MME中的至少一个 SRVCC不可用）。
S207、 目标 4则 MME接^:目标 4则 eNodeB发送切换响应 （ Handover
Response ) 消息。
S208、 执行 PS HO的相关步骤， 可以包括但不限于： 创建临时数据转发 隧道， 更新上行和下行用户面， 执行跟踪区域更新以及删除临时数据转发隧 道等。
此外，在执行步骤 S208中的跟踪区域更新请求流程中，上述目标侧 MME 向上述目标侧 eNodeB发送用户设备上下文修改请求 （ UE CONTEXT MODIFICATION REQUEST )消息时， 还可以在上述用户设备上下文修改请 求消息中包含上述 SRVCC操作可能信息， 此时不限于之前步骤 S206中的切 换请求消息是否包含 SRVCC操作可能信息。
其中，上述用户设备上下文修改请求消息中包含的 SRVCC操作可能信息 的内容以及实现具体可以参见步骤 S206的描述， 此处不再赘述。
图 3为本发明提供的切换方法第三实施例的流程图， 本实施例以在 UTRAN (高速链路分组接入技术（ High Speed Packet Access; HSPA ) ) 附着的 UE的服务无线网络子*** （ Serving Radio Network Subsystem; SRNS ) 重定向 （Relocation ) 的处理为例进行说明， 其中， 源侧和目标 侧的移动管理网元均为 SGSN , 源侧和目标侧的无线接入网网元均为 RNC。 需要说明的是， 本实施例仅给出了切换方法的一个具体应用场景， 但并不以此作为对本发明实施例的限制。 如图 3所示， 该方法包括：
S301、 源侧 RNC决策发起服务无线网络子***重定向 （ SRNS relocation ) 。
S302、 源侧 RNC向源侧 SGSN发送重定向需求（ Relocation Required ) 消息 （即第二请求消息） 。
S303、 源侧 SGSN向目标侧 SGSN发送转发重定向请求 （ Forward Relocation Request ) 消息。
其中， 上述转发重定位请求消息中包含 SRVCC可用信息， 指示用户单信 道语音呼叫连续可用 （用户 SRVCC可用）。 其中， 所述用户 SRVCC可用具体 内容可以包括但不限于以下几种方式： 用户许可使用 SRVCC; 或者， 用户许 可使用 SRVCC以及用户设备具有 SRVCC能力。 此外， 上述 SRVCC可用信息 还可以指示： 源侧移动管理网元 SRVCC可用。 其中， 上述源侧移动管理网元 S RVCC可用具体可以是源侧移动管理网元支持 S RVCC或支持 S V接口等。 其 中， 用户设备具有 SRVCC能力具体可以是用户设备支持 SRVCC。
综上， 上述 SRVCC可用信息具体可以用于指示以下几种内容中的任一 种：
( 1 )、 用户 SRVCC可用；
( 2 )、 用户 SRVCC可用以及源侧移动管理网元 SRVCC可用；
( 3 )用户许可使用 SRVCC;
( 4 )、 用户许可使用 SRVCC以及用户设备具有 SRVCC能力；
( 5 )、 用户许可使用 SRVCC以及源侧移动管理网元 SRVCC可用； ( 6 )、 用户许可使用 SRVCC, 用户设备具有 SRVCC能力以及源侧移动 管理网元 SRVCC可用。
其中， 上述 SRVCC可用信息具体实现可以包括但不限于以下方式：
( 1 )上述 SRVCC可用信息中包含： 单信道语音呼叫连续会话传输号码 ( STN-SR )和相关移动台国际 ISDN号码（C-MSISDN ) 中的至少一个； 或 者， SRVCC许可信息， 例如 SRVCC许可指示（SRVCC is Allowed ); 或者， SRVCC操作可能信息， 例如 SRVCC操作可能指示 （SRVCC Operation Possible )。 其中， 本实施例中不限制上述信息或指示的具体名称。
其中， 上述 STN-SR和 /或 C-MSISDN , 或者 SRVCC许可信息， 或者
S RVCC操作可能信息可以用于指示以上所陈列的几种指示内容中的任意一 个， 例如指示用户 SRVCC可用， 或者指示用户 SRVCC可用以及源侧移动管 理网元 SRVCC可用， 或者， 指示用户许可使用 SRVCC, 或者指示用户许可 使用 SRVCC以及用户设备具有 SRVCC能力等等。
( 2 ) 上述 SRVCC可用信息中还可以包含： SRVCC能力信息， 例如
SRVCC能力指示 （SRVCC capability indication ), 该 SRVCC能力信息可以 用于指示用户设备具有 SRVCC能力。 其中， 本实施例中不限制上述信息或指 示的具体名称。
其中， 上述 SRVCC可用信息中包含 SRVCC能力信息的场景包含但不限 于： 上述 STN-SR和 /或 C-MSISDN或者 SRVCC许可信息或者 SRVCC操作可 能信息指示用户许可使用 SRVCC, 上述 SRVCC能力信息可以指示用户设备 具有 SRVCC能力。 上述 STN-SR和 /或 C-MSISDN或者 SRVCC许可信息或者 SRVCC操作可能信息以及上述 SRVCC能力信息指示用户许可使用 SRVCC 以及用户设备具有 SRVCC能力或者用户 SRVCC可用。
其中， 在源侧 SGSN向目标侧 SGSN发送该重定向请求消息之前， 源侧
SGSN可以通过但不限于以下的方式获知上述 SRVCC可用信息：
当 UE第一次附着在网络中时， UE需要向源侧 SGSN发送附着请求 ( Attach Request )消息； 或者， 如果 UE已经附着在网络中， 并且 UE位置发 生变化， 则 UE向源侧 SGSN发送位置更新请求， 例如： 路由区域更新请求 ( Routing Area Update; RAU )。 如果 UE具有 SRVCC能力， 则 UE可以在附 着请求消息或路由区域更新请求中携带 SRVCC能力指示（ SRVCC capability indication ) , 例如， 该 SRVCC能力指示可以包含在附着请求消息 /路由区域 更新请求消息中的" MS Network Capability"信元中。
另外， 当源侧 SGSN接收到 UE发送的附着请求消息或位置更新请求消息 后， 可以向归属地签约数据服务器发出位置更新请求， 归属地签约数据服务 器收到该位置更新请求后， 向移动管理网元返回 UE的用户签约信息， 如果用 户许可使用 SRVCC ( SRVCC subscribed allowed ) , 则 UE的用户签约数据 中将包含 STN-SR和 C-MSISDN , 即， 源侧 SGSN可以从归属地签约数据服务 器获知用户许可使用 SRVCC。 其中， 归属地签约数据服务器可以为归属地位 置寄存器 ( Home Location Register; HLR )或 HSS等设备。
其中， 源侧 SGSN可以根据用户许可使用 SRVCC或者用户设备具有
SRVCC能力以及用户许可使用 SRVCC获知用户 SRVCC可用。 其中， 源侧 SGSN可以根据配置信息获知自身 （源侧 MME ) SRVCC可用。
5304、 目标侧 SGSN向目标侧服务网关发送创建会话请求 （ Create Session Request ) 消息。
其中， 若目标侧 SGSN使用 S4接口， 则执行 S404和 S405; 否则若目标 侧 SGSN使用 Gn/Gp接口， 则不执行 S404和 S405。
5305、 目标侧 SGSN接收目标侧服务网关发送的创建会话响应 （ Create Session Response ) 消息。
S306、 目标侧 SGSN向目标侧 RNC发送重定向请求 （ Relocation Request ) 消息 (即第一请求消息） 。
其中， 上述切换求请求消息中可以包含单信道语音呼叫连续操作可能信 息 ( SRVCC operation possible )。
若目标侧 SGSN获知用户 SRVCC可用 （即用户许可使用 SRVCC或者 UE 许可使用 SRVCC以及 UE具有 SRVCC能力），则当目标侧 SGSN SRVCC可用 (即支持 SRVCC ), 例如该 SGSN支持 Sv接口完成 SRVCC切换， 那么目标侧 SGSN可以在向目标侧 RNC发送的重定位请求消息中包含 SRVCC操作可能 信息， 指示用户 SRVCC可用以及目标侧 SGSN SRVCC可用， 则该目标侧 RNC可以记录该 SRVCC操作可能信息， 以用于触发 SRVCC切换。
其中， 具体的， 目标侧 SGSN可以在向目标侧 eNodeB发送的切换请求消 息中包含 SRVCC操作可能指示（SRVCC operation possible indicator ), 所 述 SRVCC操作可能指示用于指示用户 SRVCC可用以及目标侧 SGSN SRVCC可用， 若不包含该指示， 则表明 SRVCC操作不可用 （即用户和目标 侧 SGSN中的至少一个 SRVCC不可用）； 或者， 目标侧 SGSN可以在向目标侧 eNodeB发送的切换请求消息中包含 SRVCC操作可能指示 （ SRVCC operation possible indicator ) , 若所述 SRVCC操作可能指示的值为真 ( TRUE )或 1时，用于指示用户 SRVCC可用以及目标侧 SGSN SRVCC可用， 若所述 SRVCC操作可能指示的值为假（ FALSE )或 0时， 则表明表明 SRVCC 操作不可用 （即用户和目标侧 SGSN中的至少一个 SRVCC不可用）。
S307、 目标侧 SGSN接收目标侧 RNC发送重定向响应 （ Relocation Response ) 消息。
S308、 执行 SRNS Relocation的其它步骤， 具体可以包括但不限于： 更 新上行和下行用户面， 执行路由区域更新等。
此外， 在步骤 S308中的执行跟踪区更新请求流程中， 上述目标侧 SGSN 向上述目标侧 RNC发送共有标识（Common ID )消息时， 还可以在上述共有 标识消息中包含上述 SRVCC操作可能信息， 此时不限于之前步骤 S306中的 切换请求消息是否包含 SRVCC操作可能信息。
其中， 上述共有标识消息中包含的 SRVCC操作可能信息的内容以及 实现具体可以参见步骤 S306的描述， 此处不再赘述。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流 程， 是可以通过计算机程序来指令相关的硬件来完成， 所述的程序可存储于 一计算机可读取存储介质中， 该程序在执行时， 可包括如上述各方法的实施 例的流程。 其中， 所述的存储介质可为磁碟、 光盘、 只读存储记忆体 ( Read-Only Memory, ROM )或随机存者 i己忆体（ Random Access Memory, RAM ) 等。
图 4为本发明提供的移动管理网元第一实施例的结构示意图， 如图 4 所示， 该移动管理网元包括： 接收模块 1 1和发送模块 12;
接收模块 11 , 用于接收源侧移动管理网元发送的转发重定向请求消息， 转发重定向请求消息包含单信道语音呼叫连续 SRVCC可用信息；
发送模块 12,用于向目标侧接入网元发送携带 SRVCC操作可能信息的第 一请求消息。
在前一实施例的基础上， 接收模块 11接收的转发重定向请求消息中包含 的 SRVCC可用信息， 可以用于指示用户 SRVCC可用。
进一步的，接收模块 11接收的转发重定向请求消息中包含的 SRVCC可用 信息， 还用于指示源侧移动管理网元 SRVCC可用。
其中， 用户 SRVCC可用， 包括： 用户许可使用 SRVCC, 或用户许可使 用 SRVCC以及用户设备具有 SRVCC能力。
作为一个较佳的实施例， 接收模块 11接收的转发重定向请求消息中包含 的 SRVCC可用信息可以包括：
单信道语音呼叫连续会话传输号码 STN-SR和 /或相关移动台国际 ISDN 号码 C-MSISDN;
或者， SRVCC操作可能信息。
进一步的， 发送模块 12向目标侧接入网元发送的第一请求消息中携带的
SRVCC操作可能信息， 可以用于指示用户 SRVCC可用以及目标侧动管理网 元 SRVCC可用。
本发明实施例提供的移动管理网元， 为本发明提供的切换方法中涉及到 的目标侧侧移动管理网元， 其具体执行过程可参见前述方法实施例， 在此不 再赘述。
本实施例提供的移动管理网元， 源端的移动管理网元通过转发重定向请 求， 指示目标侧移动管理网元 SRVCC是否可用， 从而使目标侧无线接入网网 元能够正确触发 SRVCC切换， 节约网络的信令交互， 保证用户语音业务的正 常使用。
最后应说明的是： 以上实施例仅用以说明本发明的技术方案， 而非对其 限制； 尽管参照前述实施例对本发明进行了详细的说明， 本领域的普通技术 人员应当理解： 其依然可以对前述各实施例所记载的技术方案进行修改， 或 者对其中部分技术特征进行等同替换； 而这些修改或者替换， 并不使相应技 术方案的本质脱离本发明各实施例技术方案的精神和范围。

Claims

权 利 要 求
1、 一种切换方法， 其特征在于， 包括：
目标侧移动管理网元接收源侧移动管理网元发送的转发重定向请求消 息， 所述转发重定向请求消息包含单信道语音呼叫连续 SRVCC可用信息； 所述目标侧移动管理网元向目标侧接入网元发送携带 SRVCC操作可能 信息的第一请求消息。
2、 根据权利要求 1所述的方法， 其特征在于， 所述 SRVCC可用信息用于 指示用户 SRVCC可用。
3、 根据权利要求 1或 2所述的方法， 其特征在于， 所述 SRVCC可用信息 用于指示源侧移动管理网元 SRVCC可用。
4、 根据权利要求 2所述的方法， 其特征在于， 所述用户 SRVCC可用， 包 括： 用户许可使用 SRVCC , 或用户许可使用 SRVCC以及用户设备具有 SRVCC能力。
5、根据权利要求 1所述的方法，其特征在于，所述 SRVCC可用信息包括： 单信道语音呼叫连续会话传输号码 STN-SR和 /或相关移动台国际 ISDN 号码 C-MSISDN;
或者， SRVCC操作可能信息。
6、 根据权利要求 1所述的方法， 其特征在于， 所述 SRVCC操作可能信息 7、 根据权利要求 1所述的方法， 其特征在于， 所述目标侧移动管理网元 接收源侧移动管理网元发送的转发重定向请求消息之前， 进一步包括：
源侧移动管理网元接收源侧无线接入网网元发送的第二请求消息。
8、 一种移动管理网元， 其特征在于， 包括：
接收模块， 用于接收源侧移动管理网元发送的转发重定向请求消息， 所 述转发重定向请求消息包含单信道语音呼叫连续 SRVCC可用信息；
发送模块，用于向目标侧接入网元发送携带 SRVCC操作可能信息的第一 请求消息。
9、 根据权利要求 8所述的移动管理网元， 其特征在于， 所述接收模块接 收的转发重定向请求消息中包含的 SRVCC可用信息用于指示用户 SRVCC可 用。
10、 根据权利要求 8或 9所述的移动管理网元， 其特征在于， 所述接收模 块接收的转发重定向请求消息中包含的 SRVCC可用信息用于指示源侧移动 管理网元 SRVCC可用。
11、 根据权利要求 9所述移动管理网元， 其特征在于， 所述用户 SRVCC 可用， 包括： 用户许可使用 SRVCC, 或用户许可使用 SRVCC以及用户设备 具有 SRVCC能力。
12、根据权利要求 8所述的移动管理网元， 其特征在于， 所述接收模块接 收的转发重定向请求消息中包含的 SRVCC可用信息包括：
单信道语音呼叫连续会话传输号码 STN-SR和 /或相关移动台国际 ISDN 号码 C-MSISDN;
或者， SRVCC操作可能信息。
13、 根据权利要求 8所述的移动管理网元， 其特征在于， 所述发送模 块向目标侧接入网元发送的第一请求消息中携带的 SRVCC操作可能信息 用于指示用户 SRVCC可用以及目标侧动管理网元 SRVCC可用。
PCT/CN2011/070391 2011-01-19 2011-01-19 切换方法和移动管理网元 WO2012097509A1 (zh)

Priority Applications (9)

Application Number Priority Date Filing Date Title
ES11855931T ES2748114T3 (es) 2011-01-19 2011-01-19 Método de traspaso y elemento de red de gestión de movilidad
JP2013549689A JP5655958B2 (ja) 2011-01-19 2011-01-19 ハンドオーバ方法およびモビリティ管理ネットワーク要素
EP19186666.4A EP3627894B1 (en) 2011-01-19 2011-01-19 Handover method, computer readable storage medium, hardware apparatus, system and communication system
EP11855931.9A EP2661123B1 (en) 2011-01-19 2011-01-19 Handover method and mobility management network element
CN201180000804.6A CN102714831B (zh) 2011-01-19 2011-01-19 切换方法和移动管理网元
BR112013018552-0A BR112013018552B1 (pt) 2011-01-19 2011-01-19 Método de transferência de ponto a ponto e elemento de rede de gerenciamento de mobilidade
PCT/CN2011/070391 WO2012097509A1 (zh) 2011-01-19 2011-01-19 切换方法和移动管理网元
US13/945,026 US10582424B2 (en) 2011-01-19 2013-07-18 Handover method and mobility management network element
US16/798,734 US11438809B2 (en) 2011-01-19 2020-02-24 Handover method and mobility management network element

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2011/070391 WO2012097509A1 (zh) 2011-01-19 2011-01-19 切换方法和移动管理网元

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US13/945,026 Continuation US10582424B2 (en) 2011-01-19 2013-07-18 Handover method and mobility management network element

Publications (1)

Publication Number Publication Date
WO2012097509A1 true WO2012097509A1 (zh) 2012-07-26

Family

ID=46515089

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/070391 WO2012097509A1 (zh) 2011-01-19 2011-01-19 切换方法和移动管理网元

Country Status (7)

Country Link
US (2) US10582424B2 (zh)
EP (2) EP2661123B1 (zh)
JP (1) JP5655958B2 (zh)
CN (1) CN102714831B (zh)
BR (1) BR112013018552B1 (zh)
ES (1) ES2748114T3 (zh)
WO (1) WO2012097509A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103249019A (zh) * 2013-04-03 2013-08-14 大唐移动通信设备有限公司 一种单一无线语音呼叫连续性的处理方法和***
CN103404107A (zh) * 2013-06-05 2013-11-20 华为技术有限公司 信息传输方法、信息更改方法及装置
CN103841545A (zh) * 2012-11-27 2014-06-04 华为技术有限公司 一种mme池场景能力信息上报的方法及装置

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2661123B1 (en) * 2011-01-19 2019-08-14 Huawei Technologies Co., Ltd. Handover method and mobility management network element
US20140269611A1 (en) * 2013-03-14 2014-09-18 T-Mobile Usa, Inc. Communication Handovers from Networks Using Unlicensed Spectrum to Circuit-Switched Networks
JP6214770B2 (ja) * 2013-07-25 2017-10-18 華為技術有限公司Ｈｕａｗｅｉ Ｔｅｃｈｎｏｌｏｇｉｅｓ Ｃｏ．，Ｌｔｄ． モバイルネットワーク、サブスクリプションマネージャ、およびユーザ機器を動的に切り換えるための方法
US10299172B2 (en) 2014-02-24 2019-05-21 Intel IP Corporation Circuit switched fallback
JP6280438B2 (ja) * 2014-05-13 2018-02-14 株式会社Ｎｔｔドコモ 無線通信制御方法および無線制御装置
US20160135093A1 (en) * 2014-11-10 2016-05-12 Samsung Electronics Co., Ltd. Apparatus and method for handling single radio voice call continuity handover
CN105792302A (zh) * 2014-12-24 2016-07-20 华为技术有限公司 一种语音业务切换方法及设备
US20170127331A1 (en) * 2015-10-28 2017-05-04 Htc Corporation Device and Method of Handling Communication Failure
US20190230571A1 (en) * 2016-06-30 2019-07-25 Sharp Kabushiki Kaisha Terminal apparatus, control apparatus, and communication control method
CN109792612B (zh) * 2017-04-18 2021-10-22 华为技术有限公司 终端监控信息的同步方法、设备及***
US11792694B2 (en) * 2020-05-29 2023-10-17 T-Mobile Usa, Inc. Packet-switched to circuit-switched handover during VOIP call initiation

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101662756A (zh) * 2008-08-28 2010-03-03 华为技术有限公司 语音连续性呼叫切换的方法、***及移动业务交换中心
CN101848515A (zh) * 2009-03-25 2010-09-29 华为技术有限公司 一种切换方法、通信***及相关设备

Family Cites Families (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090268722A1 (en) * 2008-04-29 2009-10-29 Gallagher Michael D User Equipment and System Architecture for Voice over Long Term Evolution via Generic Access
US8964691B2 (en) * 2008-08-18 2015-02-24 Google Technology Holdings LLC Method and apparatus for inter-technology handoff of a user equipment
US20100135246A1 (en) * 2008-10-15 2010-06-03 Hallentaal Magnus Mobility solution selection for voice over eps
US8543114B2 (en) * 2008-10-15 2013-09-24 Telefonaktiebolaget Lm Ericsson (Publ) Voice over LTE via generic access handover (HO) apparatus and method
WO2010044730A2 (en) * 2008-10-15 2010-04-22 Telefonaktiebolaget L M Ericsson (Publ) Method and apparatus for mobility selection of voice over the evolved packet system
US8824417B2 (en) * 2008-11-10 2014-09-02 Telefonaktiebolaget Lm Ericsson (Publ) Methods and apparatuses for single radio voice call continuity (SRVCC) from CS to LTE
US20110280217A1 (en) * 2008-11-10 2011-11-17 Nicolas Drevon Support of cs domain services over a packet only mobile system
US9042340B2 (en) * 2009-02-10 2015-05-26 Nokia Corporation Method, apparatus and computer program product for transfer of capability support information in a multi-rat environment
US8942660B2 (en) * 2009-06-05 2015-01-27 Qualcomm Incorporated Method and apparatus for performing handover of an emergency call between wireless networks
JP4643734B1 (ja) * 2009-08-12 2011-03-02 株式会社エヌ・ティ・ティ・ドコモ 移動通信システム
ES2738105T3 (es) * 2009-11-09 2020-01-20 Samsung Electronics Co Ltd Procedimiento y sistema de soporte de continuidad de la llamada por radio vídeo única durante un traspaso
US8937926B2 (en) * 2010-04-21 2015-01-20 Lg Electronics Inc. Device and method for performing an rSRVCC procedure
US8971848B2 (en) * 2010-06-24 2015-03-03 Telefonaktiebolaget L M Ericsson (Publ) System and method for managing UE-based network performance measurements
WO2012062488A1 (en) * 2010-11-08 2012-05-18 Nokia Siemens Networks Oy A method for srvcc solution
EP2661123B1 (en) * 2011-01-19 2019-08-14 Huawei Technologies Co., Ltd. Handover method and mobility management network element

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101662756A (zh) * 2008-08-28 2010-03-03 华为技术有限公司 语音连续性呼叫切换的方法、***及移动业务交换中心
CN101848515A (zh) * 2009-03-25 2010-09-29 华为技术有限公司 一种切换方法、通信***及相关设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP2661123A4 *

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103841545A (zh) * 2012-11-27 2014-06-04 华为技术有限公司 一种mme池场景能力信息上报的方法及装置
CN103841545B (zh) * 2012-11-27 2017-12-29 华为技术有限公司 一种mme池场景能力信息上报的方法及装置
CN103249019A (zh) * 2013-04-03 2013-08-14 大唐移动通信设备有限公司 一种单一无线语音呼叫连续性的处理方法和***
CN103249019B (zh) * 2013-04-03 2016-08-17 大唐移动通信设备有限公司 一种单一无线语音呼叫连续性的处理方法和***
CN103404107A (zh) * 2013-06-05 2013-11-20 华为技术有限公司 信息传输方法、信息更改方法及装置
CN103404107B (zh) * 2013-06-05 2016-09-28 华为技术有限公司 信息传输方法、信息更改方法及装置
US10390263B2 (en) 2013-06-05 2019-08-20 Huawei Technologies Co., Ltd. Information transmission method, information modification method, and apparatuses
US11223978B2 (en) 2013-06-05 2022-01-11 Huawei Technologies Co., Ltd. Information transmission method, information modification method, and apparatuses

Also Published As

Publication number Publication date
US10582424B2 (en) 2020-03-03
JP5655958B2 (ja) 2015-01-21
US20130301614A1 (en) 2013-11-14
BR112013018552B1 (pt) 2021-11-16
ES2748114T3 (es) 2020-03-13
US20200196200A1 (en) 2020-06-18
EP2661123B1 (en) 2019-08-14
EP3627894C0 (en) 2024-04-10
EP2661123A1 (en) 2013-11-06
EP3627894A1 (en) 2020-03-25
CN102714831B (zh) 2014-04-02
CN102714831A (zh) 2012-10-03
EP2661123A4 (en) 2014-03-05
EP3627894B1 (en) 2024-04-10
US11438809B2 (en) 2022-09-06
BR112013018552A2 (pt) 2016-11-22
JP2014506741A (ja) 2014-03-17

Similar Documents

Publication Publication Date Title
US11438809B2 (en) Handover method and mobility management network element
US8861496B2 (en) Method and device for detaching user equipment
US8331938B2 (en) Moving user equipment without service interruption
US20100130207A1 (en) Method of handling handover security configuration and related communication device
WO2009100609A1 (zh) 一种单无线信道语音业务连续性的域切换方法
WO2010025602A1 (zh) 紧急业务切换方法
JP6480011B2 (ja) 通信を確立するための方法及び移動無線通信ネットワーク構成要素
WO2011153702A1 (zh) 公众陆地移动网的选择方法、装置及***
WO2011110001A1 (zh) 承载建立方法、***和网关设备
WO2008113283A1 (fr) Procédé et équipement de suivi de signalisation
WO2016176816A1 (zh) 电路域回落的方法、网络设备和***
WO2016054822A1 (zh) Csfb呼叫建立方法及装置
WO2010022611A1 (zh) 语音连续性呼叫切换的方法、***及移动业务交换中心
WO2009149656A1 (zh) 一种实现业务切换的方法、装置及***
JP2012100176A (ja) 移動通信方法及び移動管理ノード
WO2011134334A1 (zh) 反向单待业务连续性的实现方法及***
WO2010108397A1 (zh) 用户管理和状态保持方法、装置及***
EP2882225A1 (en) Suspend method, apparatus and system
WO2017177427A1 (zh) 业务处理方法和相关装置及通信***
KR101451419B1 (ko) 네트워크 천이 방법, 이 방법을 수행하는 기지국 장치 및 이동 단말
WO2013071897A1 (zh) 一种实现反向单待业务连续性的方法和***
WO2014005306A1 (zh) 视频呼叫的反向切换的方法和装置
WO2012089045A1 (zh) 承载修改方法及设备
WO2011110017A1 (zh) 业务处理方法及装置
WO2013013546A1 (zh) 分组交换移动接入网触发媒体重定向的方法及***、mss装置、ncs装置

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 201180000804.6

Country of ref document: CN

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 11855931

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2013549689

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2011855931

Country of ref document: EP

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112013018552

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 112013018552

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20130719