WO2013064105A1 - 一种反向单待业务连续性承载切换方法及装置 - Google Patents

一种反向单待业务连续性承载切换方法及装置 Download PDF

Info

Publication number
WO2013064105A1
WO2013064105A1 PCT/CN2012/084030 CN2012084030W WO2013064105A1 WO 2013064105 A1 WO2013064105 A1 WO 2013064105A1 CN 2012084030 W CN2012084030 W CN 2012084030W WO 2013064105 A1 WO2013064105 A1 WO 2013064105A1
Authority
WO
WIPO (PCT)
Prior art keywords
target
rsrvcc
handover
identification information
information
Prior art date
Application number
PCT/CN2012/084030
Other languages
English (en)
French (fr)
Inventor
谢振华
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2013064105A1 publication Critical patent/WO2013064105A1/zh

Links

Classifications

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

Definitions

  • the present invention relates to the field of communications, and in particular, to a reverse single-standby service continuity bearer switching method and apparatus. Background technique
  • IP Multimedia Core Network Subsystem is an IP-based network architecture proposed by the 3rd Generation Partnership Project (3GPP) to build an open and flexible business environment. Multimedia applications can provide users with rich multimedia services.
  • 3GPP 3rd Generation Partnership Project
  • control layer In the IMS service system, the control layer and the service layer are separated.
  • the control layer does not provide specific services, and only provides the necessary triggering, routing, and accounting functions to the service layer.
  • Call Session Control Function The service triggering and control functions in the control layer are completed by the Call Session Control Function (CSCF).
  • Call session control functions are divided into: proxy call session control function (Proxy-CSCF, P-CSCF), query call session control function (Interrogating-CSCF, I-CSCF) and service call session control function (Serving-CSCF, S-referred to as S- CSCF) Three types, of which the primary responsibility is S-CSCF, and the I-CSCF is optional.
  • the service layer is composed of a series of application servers (ASs) that can provide specific service services.
  • ASs application servers
  • the AS can be an independent entity or exist in the S-CSCF.
  • the control layer controls the service trigger according to the subscription information of the user, invokes the service on the AS, and implements the service function.
  • the end-to-end device in the session is called User Equipment (UE), which is responsible for interaction with the user.
  • UE User Equipment
  • Some UEs have multiple ways to access the network, including packet switching (PS) domain through 3GPP. Access the network, access the network through other non-3GPP PS domains, It can even access the network through a Circuit Switch (CS) domain.
  • PS packet switching
  • CS Circuit Switch
  • the CS network is configured with an enhanced mobile switching center (eMSC), and the eMSC provides a Session Initial Protocol (SIP) interface to interact with the IMS network
  • SIP Session Initial Protocol
  • the UE For a UE with multiple access modes, if the UE can only use one access mode at a time, it is performing a call service in the access mode of the 2/3G network, because the call service is at 2/3G.
  • the network is provided by the CS domain.
  • LTE Long Term Evolution
  • HSPA high speed packet access
  • the UE and the network can provide a way for the call service that the UE is performing is not interrupted, because the call service is provided by the PS domain in these networks, and this capability is called a single-standby terminal voice service switching from the CS domain to the PS domain.
  • the continuity of the domain referred to as the reverse Single Radio Voice Call Continuity (RSRVCC), corresponding to the case, if the UE moves from the LTE network or the HSPA network to the 2/3G network, it is called a single Waiting for terminal business continuity, referred to as Single Waiting Business Continuity (SRVCC).
  • RSRVCC reverse Single Radio Voice Call Continuity
  • Figure 1 is a flow chart of the existing reverse single-standby service continuity bearer switching, which describes that a call is established between UE-1 and UE-2, and UE-1 establishes a call through the CS domain of the 2/3G network, so the call is made.
  • the UE-1 is connected to the UE-1 in the media path, and the UE-1 has an active PS service. Therefore, there is an active PS service bearer connection.
  • the UE-1 mobile needs to change its access mode, it is LTE or In the PS domain of HSPA, UE-1 implements a process of reverse single-standby service continuity bearer switching, which includes the following steps:
  • Step 101 The UE-1 establishes a session with the UE-2 through the CS domain and the original network CS domain control entity, that is, the MSC, and the UE-1 also has an active PS service, so there is an active PS service connection;
  • Step 102 UE-1 sends a measurement report to the original network served by the UE-1, and reports the cell signal strength measurement information.
  • Step 103 The base station system of the original network serving the UE-1, such as the BSS or the RNC, determines that the nearby PS target network is more suitable for the UE-1 service according to the signal strength information of each cell in the measurement report, and then determines to perform the handover operation.
  • the base station system of the network sends a CS handover request to the MSC, for example, sends a Handover required message, and carries the target identification information, such as a target cell (cell) identifier, or a target enhanced Node B (eNB) identifier, etc., for identifying the target access.
  • Location information such as a target cell (cell) identifier, or a target enhanced Node B (eNB) identifier, etc.
  • Step 104 The MSC receives the handover request, uses some or all of the information in the target identification information to perform DNS resolution to obtain the address information of the target network control entity, and initiates a CS to PS handover request to the target network control entity, such as the MME or the SGSN. For example, send CS to PS Forward Relocation Request;
  • Step 105 At the same time as step 103, since the UE-1 has an active PS service, the base station system of the original network also sends a PS handover request to the original network data domain control entity, such as the SGSN, for example, sending a Relocation Request message. , carrying the target identification information;
  • the original network data domain control entity such as the SGSN
  • Step 106 The original network data domain control entity uses some or all of the information in the target identification information to perform DNS resolution to obtain the address information of the target network control entity, and sends a handover request to the target network control entity, for example, sending a Forward Relocation Request message;
  • Step 107 The target network control entity combines the information in the two handover requests of step 104 and step 106, and sends a handover request to the target network base station system, such as an eNB or an RNC, for example, sends a Handover Request message, carrying the bearer to be reserved.
  • the target network base station system such as an eNB or an RNC
  • Step 108 The target network base station system reserves resources, and then sends a handover response message, for example, sends a Handover Response message;
  • Step 109 The target network control entity sends a CS to PS handover response to the MSC, for example, sending a CS to PS Forward Relocation Response message.
  • Step 110 The MSC sends a handover command to the original network base station system, such as the RNC or the BSS, and sends a Handover Command message to the interface.
  • Step 111 At the same time as step 109, the target network control entity sends a handover 11 response to the original network data domain control entity, and sends a Forward Relocation Response message to the port;
  • Step 112 The original network data domain control entity sends a handover command to the original network base station system, for example, sending a Handover Command message;
  • Step 113 The original network base station system combines the information in the handover command in step 110 and step 112, and sends a handover command to UE-1, for example, sends a Handover From UTRAN message;
  • Step 114 UE-1 receives the handover command, and modulates to The target network PS domain accesses the target network;
  • Step 115 after the UE-1 accesses the target network, sends a handover notification message to the target network base station system, for example, sends a Handover Notify message;
  • Step 116 The target network base station system sends a handover notification message to the target network control network element.
  • Step 118 The target network serving gateway sends a message for updating the bearer to the data network gateway, for example, sending a Modify Bearer Request message, so as to establish a bearer connection between the target network service gateway and the data network gateway.
  • the IMS media connection 1 is established between UE-1 and UE-2, and the UE-1 and the data network gateway establish a bearer connection through the target network base station system and the target network serving gateway, so that UE-1 and UE-2 can continue.
  • the PS-1 service of UE-1 can continue.
  • step 104 and step 106 reaches the same target network control network element to implement the handover. Therefore, the target network control network element address information obtained through DNS resolution in steps 104 and 106 must be the same, but based on the existing After the MME pool or the SGSN pool is deployed, the assumption is not necessarily true, that is, different addresses may be parsed, and the two handover requests cannot reach the same target network control network element. This causes the switch to fail. Summary of the invention
  • the main purpose of the present invention is to provide a reverse single-standby service continuity bearer switching method and apparatus, which can improve the success rate of reverse single-standby service continuity bearer switching.
  • a reverse single-standby service continuity bearer switching method includes:
  • the base station determines that the measurement report sender has the circuit switched CS service, and carries the target identification information for the reverse single standby service continuity rSRVCC in the handover request sent to the mobile switching center MSC and the original network data domain control entity.
  • the method further includes: the MSC and the original network data domain control entity perform DNS resolution according to part or all of the information of the target identification information for the rSRVCC carried in the handover request, to obtain unique address information.
  • the method further includes: the base station determining that the measurement report sender does not have the CS service, and carrying the target identification information for the PS-only handover or the target identification information for the rSRVCC in the handover request sent to the MSC and the original network data domain control entity.
  • the target identification information for rSRVCC is different from the target identification information for only PS handover.
  • the base station carries the target identifier information for the rSRVCC in the handover request, where the base station selects the target identifier information for the rSRVCC, or constructs the target identifier information for the rSRVCC according to the target index information for the rSRVCC, and then The selected or constructed target identification information for the rSRVCC is carried in the handover request,
  • the base station carries, in the handover request, target identifier information for only PS handover: the base station selects target identifier information for only PS handover, or
  • the target index information of the PS handover is configured for the target identification information of only the PS handover, and the selected or constructed target identification information for only the PS handover is carried in the handover request.
  • a reverse single-standby service continuity bearer switching device includes: a determining module and a sending module; among them,
  • the determining module is configured to determine whether the sender of the measurement report has a CS service; and the sending module is configured to switch to the MSC and the original network data domain control entity when the determining module determines that the measurement report sender has a CS service
  • the request carries the target identification information for rSRVCC.
  • Part or all of the information of the target identification information for the rSRVCC carried in the handover request sent by the sending module is obtained by the MSC and the original network data domain control entity after DNS resolution, and the unique address information is obtained.
  • the sending module is further configured to: when the determining module determines that the measurement report sender does not have a CS service, carry the target identifier information for only the PS handover or the rSRVCC in the handover request sent to the MSC and the original network data domain control entity. Target identification information.
  • the target identification information for rSRVCC carried in the handover request is different from the target identification information for only PS handover.
  • the device further includes a target identification information acquiring module,
  • the sending module carries the target identifier information for the rSRVCC in the handover request, where the target identifier information for the rSRVCC selected or constructed by the target identifier information acquiring module is carried in the handover request;
  • the sending module carries, in the handover request, the target identifier information for the PS-only handover: the target identifier information for the PS-switching only selected or constructed by the target identifier information acquiring module is carried in the handover request;
  • the target identification information acquiring module is configured to select target identification information for rSRVCC, or construct target identification information for rSRVCC according to target index information for rSRVCC; or, select target identification information for only PS handover Or, constructing target identification information for only PS handover according to target index information for only PS handover.
  • the target identification information for the reverse single standby service continuity rSRVCC is carried in the handover request sent to the mobile switching center MSC and the original network data domain control entity.
  • the embodiment of the present invention uses different target identifiers to distinguish different situations, so that the handover request sent by the MSC in the reverse single-standby service continuity bearer switching operation and the handover request sent by the original network data domain control entity can reach the same target network control network.
  • the success of the reverse single-standby service continuity bearer handover is improved, and the success rate of the reverse single-standby service continuity bearer handover is improved.
  • FIG. 1 is a flowchart of an existing reverse single-standby service continuity bearer switching
  • FIG. 1 is a schematic flowchart of a reverse single-standby service continuity bearer switching method according to an embodiment of the present invention
  • FIG. 3 is a schematic structural diagram of a reverse single-standby service continuity bearer switching apparatus according to an embodiment of the present invention
  • FIG. 4 is a flowchart of a reverse single-standby service continuity bearer switching method according to Embodiment 1 of the present invention. detailed description
  • the base station determines that the measurement report sender has a circuit switched CS service, and carries the handover request for the reverse single standby service continuity rSRVCC in the handover request sent to the mobile switching center MSC and the original network data domain control entity.
  • Target identification information is:
  • FIG. 1 is a schematic flowchart of a method for switching a continuous bearer service continuity bearer according to an embodiment of the present invention. As shown in FIG. 2, the method includes:
  • Step 201 The base station determines whether the measurement report sender has a CS service, and if yes, performs step 202; otherwise, performs step 203.
  • Step 202 Carrying in a handover request sent to the MSC and the original network data domain control entity With target identification information for rSRVCC.
  • the MSC and the original network data domain control entity perform DNS resolution according to part or all of the information of the target identifier information for the rSRVCC carried in the handover request, and the unique address information can be obtained.
  • Step 203 Carrying target identification information for only PS handover or target identification information for rSRVCC in the handover request sent to the MSC and the original network data domain control entity.
  • the target identifier information used for the rSRVCC may be the same as or different from the target identifier information used for the PS handover only. If the terminal does not have the CS service, part or all of the information of the target identifier information used for the rSRVCC is used. When the DNS is parsed, multiple address information can be obtained. If the terminal has a CS service, and the target network control network element responsible for the target access location deploys the pool, the target identification information for only the PS handover and the rSRVCC are used. The target identification information must be different, and some or all of the information used in the target identification information of the rSRVCC must be resolved by the DNS to the unique address information.
  • the base station carrying the target identifier information for the rSRVCC in the handover request may be:
  • the base station selects target identification information for the rSRVCC, or constructs target identification information for the rSRVCC according to the target index information for the rSRVCC, and then carries the selected or constructed target identification information for the rSRVCC in the handover request.
  • the base station carrying the target identification information for only the PS handover in the handover request may be: the base station selects target identification information for only PS handover, or is configured to use only PS handover according to target index information for only PS handover.
  • the target identification information is carried in the handover request by the selected or constructed target identification information for only PS handover.
  • the target index information for only the PS handover and the target index information for the rSRVCC may be the same or different. If the terminal does not have the CS service, the target index information for the rSRVCC may be used for the DNS resolution. Get multiple address information, if the terminal has For the CS service, for the case where the pool is deployed, if the target network control NE that is responsible for the target access location belongs to the pool, the target index information for the PS handover only and the target index information for the rSRVCC must be different. The target index information of rSRVCC must be resolved by the DNS to unique address information.
  • the embodiment of the present invention further provides a reverse single-standby service continuity bearer switching device.
  • the device includes: a determining module and a sending module;
  • the determining module is configured to determine whether the sender of the measurement report has a CS service; and the sending module is configured to switch to the MSC and the original network data domain control entity when the determining module determines that the measurement report sender has a CS service
  • the request carries the target identification information for rSRVCC.
  • Part or all of the information of the target identification information for the rSRVCC carried in the handover request sent by the sending module is obtained by the MSC and the original network data domain control entity after DNS resolution, and the unique address information is obtained.
  • the sending module is further configured to: when the determining module determines that the measurement report sender does not have a CS service, carry the target identifier information for only the PS handover or the rSRVCC in the handover request sent to the MSC and the original network data domain control entity. Target identification information.
  • the target identification information for rSRVCC carried in the handover request is different from the target identification information for only PS handover.
  • the device further includes a target identification information acquiring module,
  • the sending module carries the target identifier information for the rSRVCC in the handover request, where the target identifier information for the rSRVCC selected or constructed by the target identifier information acquiring module is carried in the handover request;
  • the sending module carries, in the handover request, the target identifier information for the PS-only handover: the target identifier information that is selected or configured by the target identifier information acquiring module for only the PS handover is carried in the handover request;
  • the target identification information acquiring module is configured to select target identification information for rSRVCC, or construct target identification information for rSRVCC according to target index information for rSRVCC; or, select target identification information for only PS handover Or, constructing target identification information for only PS handover according to target index information for only PS handover.
  • the target index information for the PS switching only is different from the target index information for the rSRVCC.
  • FIG. 4 is a flowchart of a reverse single-standby service continuity bearer switching method according to Embodiment 1 of the present invention.
  • the process describes that the UE-1 has an active PS service, so there is an active PS service connection, and the UE- A call may be established between the UE and the UE-2.
  • the UE-1 can only establish a call through the CS domain of the 2/3G network. Therefore, the UE-1 connected to the UE-1 is a CS media connection.
  • the access mode used by the UE is the PS domain of LTE or HSPA.
  • the process of UE1 implementing the reverse single-standby service continuity bearer switching includes the following steps:
  • Step 401 UE-1 has an active PS service, so there is an active PS service connection, and UE-1 may establish a session with UE-2 through the CS domain and the original network CS domain control entity, that is, the MSC.
  • Step 402 UE-1 sends a measurement report to the original network served by the UE-1, and the cell signal strength measurement information is reported above.
  • Step 403 The base station system of the original network serving the UE-1, such as the BSS or the RNC, determines that the nearby PS target network is more suitable for the UE-1 service according to the signal strength information of each cell in the measurement report, and then determines to perform the handover operation.
  • the network base station system first determines whether the UE-1 has a CS service;
  • Step 404 If the UE-1 has a CS service, the base station system of the original network sends a CS handover request to the MSC, for example, sends a Handover required message, and carries the target identifier information for the rSRVCC, such as a target cell (Cell) identifier. , or target enhanced Node B (eNB) Identification information, etc., used to identify the target access location;
  • the target identifier information for the rSRVCC such as a target cell (Cell) identifier.
  • Cell target cell
  • eNB target enhanced Node B
  • Step 405 The MSC receives the handover request, uses some or all of the information in the target identification information to perform DNS resolution, obtains address information of the target network control entity, and initiates a CS to PS handover request to the target network control entity, such as the MME or the SGSN. For example, send CS to PS Forward Relocation Request;
  • Step 406 UE-1 has an active PS service, so the base station system of the original network also sends a PS handover request to the original network data domain control entity, such as the SGSN, for example, sends a Relocation Request message, carrying the target identification information, if In step 403, it is determined that the UE-1 has no CS service, and the target identifier information may be target identifier information used for only PS handover, or may be target identifier information for rSRVCC, otherwise the target identifier information is target identifier information for rSRVCC. ;
  • Step 407 The original network data domain control entity uses some or all of the information in the target identifier information to perform DNS resolution to obtain address information of the target network control entity, and sends a handover request to the target network control entity, for example, sending a Forward Relocation Request message;
  • the target identification information for the PS-only handover and the target identification information for the rSRVCC may be the same or different. If the UE-1 does not have the CS service, the target identification information for the rSRVCC can be obtained by multiple addresses when used for DNS resolution. Information, if the UE-1 has a CS service, the target identification information for the rSRVCC is used in step 404 and step 406, and the target identification information for the rSRVCC is used when the target network control entity deploys the pool.
  • the target identification information of the PS handover Only the target identification information of the PS handover must be different, wherein some or all of the information for the target identification information of only the PS handover may be parsed by the DNS to obtain a plurality of address information, and part or all of the target identification information for the rSRVCC The information will be parsed by the DNS to the unique address information, so that when the rSRVCC is executed when the UE-1 has the CS service, the steps 405 and 407 will reach the same target network control network element, and when the UE-1 has only the PS service, the target The related functions of the network control network element pool (such as load sharing) can still be utilized.
  • Step 408 If the UE-1 has a CS service, the target network control entity merges the information in the two handover requests of step 405 and step 407. Otherwise, the merge function is not performed, and is sent to the target network base station system, such as an eNB or an RNC.
  • Handover request such as sending a Handover Request message, carrying the bearer information to be reserved;
  • Step 409 The target network base station system reserves resources, and then sends a handover response message, for example, sends a Handover Response message.
  • Step 410 If the UE-1 has a CS service, the target network control entity sends a CS to PS handover response to the MSC, and the CS to PS Forward Relocation Response message is sent by the interface.
  • Step 411 The MSC sends a handover command to the original network base station system, such as the RNC or the BSS, and sends a Handover Command message to the interface.
  • the original network base station system such as the RNC or the BSS
  • Step 412 The target network control entity sends a handover response to the original network data domain control entity, and sends a Forward Relocation Response message to the target network.
  • Step 413 The original network data domain control entity sends a handover command to the original network base station system, for example, sends a Handover Command message.
  • Step 414 If the UE-1 has a CS service, the original network base station system combines the information in the handover command in step 411 and step 413. Otherwise, the merge function is not performed, and a handover command is sent to the UE-1, for example, Handover From UTRAN is sent. Message
  • Steps 415 to 419 are the same as steps 114 to 118 in FIG. 1;
  • the UE-1 and the data network gateway establish a bearer connection through the target network base station system and the target network serving gateway, so that the PS service of the UE-1 can continue, and when the UE-1 has the CS service with the UE-2.
  • IMS media connection 1 can be established between UE-1 and UE-2, and the call between UE-1 and UE-2 can continue.

Landscapes

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

Abstract

本发明公开了一种反向单待业务连续性承载切换方法，包括：基站判定测量报告发送方有电路交换（CS）业务，则在向移动交换中心（MSC）和向原网络数据域控制实体发送的切换请求中携带用于反向单待业务连续性（rSRVCC）的目标标识信息。本发明还相应地公开了一种反向单待业务连续性承载切换装置。本发明通过区分不同情况使用不同目标标识，使得反向单待业务连续性承载切换操作中的MSC发送的切换请求和原网络数据域控制实体发送的切换请求能到达同一个目标网络控制网元，从而能够保证反向单待业务连续性承载切换的成功，提高反向单待业务连续性承载切换的成功率。

Description

一种反向单待业务连续性承载切换方法及装置 技术领域
本发明涉及通信领域， 尤其涉及一种反向单待业务连续性承载切换方 法及装置。 背景技术
IP多媒体子系统（ IP Multimedia Core Network Subsystem, IMS )是由 第三代合作伙伴计划 （ 3rd Generation Partnership Project, 3GPP )提出的一 种基于 IP的网络架构， 构建了一个开放而灵活的业务环境， 支持多媒体应 用， 能够为用户提供丰富的多媒体业务。
在 IMS业务体系中， 控制层和业务层是分离的， 控制层不提供具体业 务， 只向业务层提供必要的触发、 路由、 计费等功能。
控制层中业务触发和控制功能是呼叫会话控制功能 （ Call Session Control Function, CSCF ) 完成的。 呼叫会话控制功能分为： 代理呼叫会话 控制功能 ( Proxy-CSCF , P-CSCF )、 查询呼叫会话控制功能 ( Interrogating-CSCF, I-CSCF )和服务呼叫会话控制功能（ Serving-CSCF, 简称 S-CSCF )三种类型，其中负主要责任的是 S-CSCF, I-CSCF是可选的。
业务层是由一系列应用服务器（Application Server, AS )组成， 能提供 具体业务服务， AS可以是独立的实体， 也可以存在于 S-CSCF中。
控制层（S-CSCF )根据用户的签约信息控制业务触发， 调用 AS上的 业务， 实现业务功能。
会话中的端到端设备称为用户设备 ( User Equipment , UE ), 负责与使 用者的交互， 有的 UE具有多种接入网络的方式， 包括通过 3GPP的包交换 ( Packet Switch, PS )域接入网络， 通过其他非 3GPP的 PS域接入网络， 甚至可以通过电路交换（ Circuit Switch, CS )域接入网络等。
如果 CS网络配置了增强移动交换中心（ enhanced Mobile Switch Center, eMSC ), 由 eMSC提供初始会话协议 ( Session Initial Protocol, SIP )接口来 与 IMS网络交互， 则 IMS网络与 CS网络的交互可以通过 eMSC来实现。
对于具有多种接入方式的 UE而言，如果该 UE某时刻只能使用一种接 入方式， 则其在 2/3G网络的接入方式下正在执行通话业务， 因通话业务在 2/3G网络中由 CS域提供，当 UE移动到其他地方而需要改变其使用的接入 方式为长期演进（Long Term Evolution, LTE ) 网络或高速分组接入（ high speed packet access, HSPA ) 网络接入时， UE和网络能提供某种方式使 UE 正在执行的通话业务不被中断， 因通话业务在这些网络中由 PS域提供， 这 样的能力我们称之为单待终端语音业务从 CS域切换到 PS域的连续性， 简 称反向单待业务连续性 （reverse Single Radio Voice Call Continuity , rSRVCC ),与之相对应的，如果是 UE从 LTE网络或 HSPA网络移动到 2/3G 网络则称之为单待终端业务连续性， 简称为单待业务连续性（SRVCC )。
图 1 为现有的反向单待业务连续性承载切换流程图， 描述了 UE-1 和 UE-2间建立了通话， UE-1是通过 2/3G网络的 CS域建立通话的， 因此通 话媒体路径中连接 UE-1的是一段 CS媒体连接， 同时 UE-1还有活动的 PS 业务， 因此存在活动的 PS业务承载连接， 当 UE-1移动需要改变其使用的 接入方式为 LTE或 HSPA的 PS域， UE-1实现反向单待业务连续性承载切 换的过程， 其包括如下步驟：
步驟 101： UE-1通过 CS域及原网络 CS域控制实体，即 MSC,与 UE-2 建立会话， 同时 UE-1还有活动的 PS业务， 因此存在活动的 PS业务^载连 接；
步驟 102: UE-1 向为其服务的原网络发送测量报告， 以上报小区信号 强度测量信息； 步驟 103: 为 UE-1服务的原网络的基站系统， 比如 BSS或 RNC, 根 据测量报告中各小区信号强度信息判断附近的 PS 目标网络更适合为 UE-1 服务， 于是决定执行切换操作， 原网络的基站系统向 MSC发送 CS切换请 求， 比如发送 Handover required (切换请求）消息， 携带目标标识信息， 比 如目标小区 （ Cell )标识， 或目标增强节点 B ( eNB )标识等用于标识目标 接入位置的信息；
步驟 104: MSC收到切换请求， 使用目标标识信息中的部分或全部信 息进行 DNS解析获得目标网络控制实体的地址信息， 并向目标网络控制实 体，比如 MME或 SGSN,发起 CS到 PS切换请求，比如发送 CS to PS Forward Relocation Request;
步驟 105: 与步驟 103同时， 因 UE-1还有活动的 PS业务， 因此原网 络的基站系统还向原网络数据域控制实体， 比如 SGSN,发送 PS切换请求， 比如发送 Relocation Request (切换请求 ) 消息， 携带目标标识信息；
步驟 106:原网络数据域控制实体使用目标标识信息中的部分或全部信 息进行 DNS解析获得目标网络控制实体的地址信息， 并向目标网络控制实 体发送切换请求， 比如发送 Forward Relocation Request消息；
步驟 107: 目标网络控制实体合并步驟 104和步驟 106的两个切换请求 中的信息， 并向目标网络基站系统， 比如 eNB或 RNC, 发送切换请求， 比 如发送 Handover Request消息， 携带要预留的承载信息；
步驟 108: 目标网络基站系统预留资源， 然后发送切换响应消息， 比如 发送 Handover Response消息；
步驟 109: 目标网络控制实体向 MSC发送 CS到 PS切换响应， 比如发 送 CS to PS Forward Relocation Response消息。
步驟 110: MSC向原网络基站系统， 比如 RNC或 BSS,发送切换命令， t匕^口发送 Handover Command消息、； 步驟 111 : 与步驟 109同时， 目标网络控制实体向原网络数据域控制实 体发送切换 11向应 , t匕^口发送 Forward Relocation Response消息、；
步驟 112: 原网络数据域控制实体向原网络基站系统发送切换命令， 比 如发送 Handover Command消息；
步驟 113:原网络基站系统合并步驟 110和步驟 112中的切换命令中的 信息， 并向 UE- 1发送切换命令， 比如发送 Handover From UTRAN消息； 步驟 114、 UE-1收到切换命令， 调制到目标网络 PS域接入目标网络； 步驟 115、 UE-1接入目标网络后， 向目标网络基站系统发送切换通知 消息， 比如发送 Handover Notify消息；
步驟 116、 目标网络基站系统向目标网络控制网元发送切换通知消息； 步驟 117、 目标网络控制网元更新核心网的承载连接， 比如向目标网服 务网关， 比如 SGW, 发送 Modify Bearer Request消息， 以使目标网络基站 系统与目标网服务网关建立承载连接；
步驟 118： 目标网服务网关向数据网络网关发送更新承载的消息， 比如 发送 Modify Bearer Request消息，以使目标网服务网关与数据网络网关间建 立承载连接；
至此， UE-1与 UE-2间建立起 IMS媒体连接 1 ,且 UE-1与数据网络网 关通过目标网络基站系统和目标网服务网关建立起承载连接， 使 UE-1 与 UE-2能继续通话， UE-1的 PS业务可以继续进行。
步驟 104和步驟 106中的切换请求到达同一个目标网络控制网元， 才 能实现切换， 所以， 步驟 104和步驟 106中通过 DNS解析后获得的目标网 络控制网元地址信息必须相同，但基于现有技术， 当部署了 MME池（MME Pool )或 SGSN池（SGSN Pool )后， 该假设不一定成立， 即可能会解析出 不同的地址， 导致两个切换请求无法到达同一个目标网络控制网元， 从而 导致切换失败。 发明内容
有鉴于此， 本发明的主要目的在于提供一种反向单待业务连续性承载 切换方法及装置， 能够提高反向单待业务连续性承载切换的成功率。
为达到上述目的， 本发明的技术方案是这样实现的：
一种反向单待业务连续性承载切换方法， 包括：
基站判定测量报告发送方有电路交换 CS 业务， 则在向移动交换中心 MSC和向原网络数据域控制实体发送的切换请求中携带用于反向单待业务 连续性 rSRVCC的目标标识信息。
该方法还包括： MSC和原网络数据域控制实体根据所述切换请求中携 带的用于 rSRVCC的目标标识信息的部分或全部信息进行 DNS解析， 得到 唯一地址信息。
该方法还包括： 基站判定测量报告发送方没有 CS业务， 则在向 MSC 和向原网络数据域控制实体发送的切换请求中携带用于只有 PS切换的目标 标识信息或用于 rSRVCC的目标标识信息。
所述用于 rSRVCC的目标标识信息与用于只有 PS切换的目标标识信息 不同。
所述基站在切换请求中携带用于 rSRVCC的目标标识信息为： 所述基站选择用于 rSRVCC的目标标识信息，或者，根据用于 rSRVCC 的目标索引信息构造用于 rSRVCC的目标标识信息， 再将所述选择或构造 的用于 rSRVCC的目标标识信息携带在切换请求中，
所述基站在切换请求中携带用于只有 PS切换的目标标识信息为： 所述基站选择用于只有 PS切换的目标标识信息， 或者， 根据用于只有
PS切换的目标索引信息构造用于只有 PS切换的目标标识信息， 再将所述 选择或构造的用于只有 PS切换的目标标识信息携带在切换请求中，
一种反向单待业务连续性承载切换装置， 包括： 判断模块、 发送模块； 其中，
所述判断模块， 设置为判断测量报告发送方是否有 CS业务； 所述发送模块， 设置为在判断模块判定测量报告发送方有 CS业务时， 在向 MSC和向原网络数据域控制实体发送的切换请求中携带用于 rSRVCC 的目标标识信息。
所述发送模块发送的切换请求中携带的用于 rSRVCC的目标标识信息 的部分或全部信息在 MSC和原网络数据域控制实体进行 DNS解析后， 得 到唯一地址信息。
所述发送模块，还设置为在判断模块判定测量报告发送方没有 CS业务 时，在向 MSC和向原网络数据域控制实体发送的切换请求中携带用于只有 PS切换的目标标识信息或用于 rSRVCC的目标标识信息。
所述切换请求中携带的用于 rSRVCC的目标标识信息与用于只有 PS切 换的目标标识信息不同。
该装置还包括目标标识信息获取模块，
所述发送模块在切换请求中携带用于 rSRVCC的目标标识信息为： 将 目标标识信息获取模块选择或构造的用于 rSRVCC的目标标识信息携带在 切换请求中；
所述发送模块在切换请求中携带用于只有 PS切换的目标标识信息为： 将目标标识信息获取模块选择或构造的用于只有 PS切换的目标标识信息携 带在切换请求中；
所述目标标识信息获取模块， 设置为选择用于 rSRVCC 的目标标识信 息， 或者， 根据用于 rSRVCC的目标索引信息构造用于 rSRVCC的目标标 识信息； 或者， 选择用于只有 PS切换的目标标识信息， 或者， 根据用于只 有 PS切换的目标索引信息构造用于只有 PS切换的目标标识信息。
本发明实施例所述的反向单待业务连续性承载切换方法及装置， 基站 判定测量报告发送方有电路交换 CS业务， 则在向移动交换中心 MSC和向 原网络数据域控制实体发送的切换请求中携带用于反向单待业务连续性 rSRVCC的目标标识信息。本发明实施例通过区分不同情况使用不同目标标 识，使得反向单待业务连续性承载切换操作中的 MSC发送的切换请求和原 网络数据域控制实体发送的切换请求能到达同一个目标网络控制网元， 从 而能够保证反向单待业务连续性承载切换的成功， 提高反向单待业务连续 性承载切换的成功率。 附图说明
图 1为现有的反向单待业务连续性承载切换流程图；
图 1 为本发明实施例一种反向单待业务连续性承载切换方法流程示意 图；
图 3 为本发明实施例一种反向单待业务连续性承载切换装置结构示意 图；
图 4为本发明实施例 1反向单待业务连续性承载切换方法的流程图示 意图。 具体实施方式
本发明的基本思想是： 基站判定测量报告发送方有电路交换 CS业务， 则在向移动交换中心 MSC和向原网络数据域控制实体发送的切换请求中携 带用于反向单待业务连续性 rSRVCC的目标标识信息。
图 1 为本发明实施例一种反向单待业务连续性承载切换方法流程示意 图， 如图 2所示， 该方法包括：
步驟 201 : 基站判断测量报告发送方是否有 CS业务， 如果是， 执行步 驟 202; 否则， 执行步驟 203。
步驟 202: 在向 MSC和向原网络数据域控制实体发送的切换请求中携 带用于 rSRVCC的目标标识信息。
需要说明的是， MSC和原网络数据域控制实体根据所述切换请求中携 带的用于 rSRVCC的目标标识信息的部分或全部信息进行 DNS解析， 可以 得到唯一地址信息。
步驟 203: 在向 MSC和向原网络数据域控制实体发送的切换请求中携 带用于只有 PS切换的目标标识信息或用于 rSRVCC的目标标识信息。
本发明实施例中，用于 rSRVCC的目标标识信息与用于只有 PS切换的 目标标识信息可以相同也可以不同， 如果终端没有 CS业务， 用于 rSRVCC 的目标标识信息的部分或全部信息在被用于 DNS解析时可以得到多个地址 信息， 如果终端有 CS业务，对于负责目标接入位置的目标网络控制网元部 署了 Pool的情况， 则用于只有 PS切换的目标标识信息和用于 rSRVCC的 目标标识信息必须不同， 且用于 rSRVCC的目标标识信息中的部分或全部 信息必须被 DNS解析出唯一地址信息。
本发明实施例中， 基站在切换请求中携带用于 rSRVCC的目标标识信 息可以为：
所述基站选择用于 rSRVCC的目标标识信息，或者，根据用于 rSRVCC 的目标索引信息构造用于 rSRVCC的目标标识信息， 再将所述选择或构造 的用于 rSRVCC的目标标识信息携带在切换请求中，
基站在切换请求中携带用于只有 PS切换的目标标识信息可以为： 所述基站选择用于只有 PS切换的目标标识信息， 或者， 根据用于只有 PS切换的目标索引信息构造用于只有 PS切换的目标标识信息， 再将所述 选择或构造的用于只有 PS切换的目标标识信息携带在切换请求中。
本发明实施例中，用于只有 PS切换的目标索引信息和用于 rSRVCC的 目标索引信息可以相同也可以不同， 如果终端没有 CS业务， 用于 rSRVCC 的目标索引信息在被用于 DNS解析时可以得到多个地址信息， 如果终端有 CS业务，对于部署了 Pool的情况，如果负责目标接入位置的目标网络控制 网元属于 Pool的情况，则用于只有 PS切换的目标索引信息和用于 rSRVCC 的目标索引信息必须不同， 且用于 rSRVCC的目标索引信息必须被 DNS解 析出唯一地址信息。
本发明实施例还相应地提出一种反向单待业务连续性承载切换装置， 如图 3所示， 该装置包括： 判断模块、 发送模块； 其中，
所述判断模块， 设置为判断测量报告发送方是否有 CS业务； 所述发送模块， 设置为在判断模块判定测量报告发送方有 CS业务时， 在向 MSC和向原网络数据域控制实体发送的切换请求中携带用于 rSRVCC 的目标标识信息。
所述发送模块发送的切换请求中携带的用于 rSRVCC的目标标识信息 的部分或全部信息在 MSC和原网络数据域控制实体进行 DNS解析后， 得 到唯一地址信息。
所述发送模块，还设置为在判断模块判定测量报告发送方没有 CS业务 时，在向 MSC和向原网络数据域控制实体发送的切换请求中携带用于只有 PS切换的目标标识信息或用于 rSRVCC的目标标识信息。
所述切换请求中携带的用于 rSRVCC的目标标识信息与用于只有 PS切 换的目标标识信息不同。
该装置还包括目标标识信息获取模块，
所述发送模块在切换请求中携带用于 rSRVCC的目标标识信息为： 将 目标标识信息获取模块选择或构造的用于 rSRVCC的目标标识信息携带在 切换请求中；
所述发送模块在切换请求中携带用于只有 PS切换的目标标识信息为： 将目标标识信息获取模块选择或构造的用于只有 PS切换的目标标识信息携 带在切换请求中； 所述目标标识信息获取模块， 设置为选择用于 rSRVCC 的目标标识信 息， 或者， 根据用于 rSRVCC的目标索引信息构造用于 rSRVCC的目标标 识信息； 或者， 选择用于只有 PS切换的目标标识信息， 或者， 根据用于只 有 PS切换的目标索引信息构造用于只有 PS切换的目标标识信息。 用于只 有 PS切换的目标索引信息与所述用于 rSRVCC的目标索引信息不同。
下面结合具体实施例对本发明的技术方案作进一步详细说明。
实施例 1
图 4为本发明实施例 1反向单待业务连续性承载切换方法的流程图示 意图，该流程描述了 UE-1有活动的 PS业务， 因此存在活动的 PS业务^载 连接， 另外， UE-1和 UE-2间可能建立了通话， UE-1只能通过 2/3G网络 的 CS域建立通话， 因此通话媒体路径中连接 UE-1的是一段 CS媒体连接， 当 UE-1移动需要改变其使用的接入方式为 LTE或 HSPA的 PS域， 参见图 4, UE-1实现反向单待业务连续性承载切换的过程包括如下步驟：
步驟 401、 UE-1有活动的 PS业务， 因此存在活动的 PS业务^载连接， 同时， UE-1可能通过 CS域及原网络 CS域控制实体， 即 MSC, 与 UE-2 建立会话；
步驟 402、 UE-1 向为其服务的原网络发送测量报告， 以上报小区信号 强度测量信息；
步驟 403、 为 UE-1服务的原网络的基站系统， 比如 BSS或 RNC, 根 据测量报告中各小区信号强度信息判断附近的 PS 目标网络更适合为 UE-1 服务， 于是决定执行切换操作， 原网络基站系统先判断 UE-1是否还有 CS 业务；
步驟 404、 若 UE-1有 CS业务， 则原网络的基站系统向 MSC发送 CS 切换请求，比如发送 Handover required (切换请求 )消息，携带用于 rSRVCC 的目标标识信息， 比如目标小区 （Cell )标识， 或目标增强节点 B ( eNB ) 标识等用于标识目标接入位置的信息；
步驟 405、 MSC收到切换请求， 使用目标标识信息中的部分或全部信 息进行 DNS解析获得目标网络控制实体的地址信息， 并向目标网络控制实 体，比如 MME或 SGSN,发起 CS到 PS切换请求，比如发送 CS to PS Forward Relocation Request;
步驟 406、 UE-1有活动的 PS业务， 因此原网络的基站系统还向原网络 数据域控制实体， 比如 SGSN, 发送 PS 切换请求， 比如发送 Relocation Request (切换请求）消息， 携带目标标识信息， 如果步驟 403中判断 UE-1 没有 CS业务， 则目标标识信息可以是用于只有 PS切换的目标标识信息， 也可以是用于 rSRVCC的目标标识信息，否则目标标识信息为用于 rSRVCC 的目标标识信息；
步驟 407、原网络数据域控制实体使用目标标识信息中的部分或全部信 息进行 DNS解析获得目标网络控制实体的地址信息， 并向目标网络控制实 体发送切换请求， 比如发送 Forward Relocation Request消息；
用于只有 PS切换的目标标识信息和用于 rSRVCC的目标标识信息可以 相同也可以不同， 如果 UE-1没有 CS业务， 用于 rSRVCC的目标标识信息 在被用于 DNS解析时可以得到多个地址信息，如果 UE-1有 CS业务，则因 步驟 404和步驟 406中使用了用于 rSRVCC的目标标识信息， 当目标网络 控制实体部署了池的情况下， 用于 rSRVCC的目标标识信息和用于只有 PS 切换的目标标识信息必须不同， 其中， 用于只有 PS切换的目标标识信息中 的部分或全部信息可被 DNS解析出多个地址信息， 而用于 rSRVCC的目标 标识信息中的部分或全部信息会被 DNS解析出唯一地址信息， 从而保证了 在 UE-1有 CS业务时执行 rSRVCC时步驟 405和步驟 407会到达同一个目 标网络控制网元， 而在 UE-1只有 PS业务时 , 目标网络控制网元池的相关 作用 （比如负载分担 )仍能被利用。 步驟 408、 如果 UE-1有 CS业务， 则目标网络控制实体合并步驟 405 和步驟 407 的两个切换请求中的信息， 否则不执行合并功能， 并向目标网 络基站系统，比如 eNB或 RNC,发送切换请求，比如发送 Handover Request 消息， 携带要预留的承载信息；
步驟 409: 目标网络基站系统预留资源， 然后发送切换响应消息， 比如 发送 Handover Response消息；
步驟 410: 如果 UE-1有 CS业务， 则目标网络控制实体向 MSC发送 CS到 PS切换响应， 比 口发送 CS to PS Forward Relocation Response消息。
步驟 411 : MSC向原网络基站系统，比如 RNC或 BSS,发送切换命令， t匕^口发送 Handover Command消息、；
步驟 412: 目标网络控制实体向原网络数据域控制实体发送切换响应， t匕^口发送 Forward Relocation Response消息、；
步驟 413 : 原网络数据域控制实体向原网络基站系统发送切换命令， 比 如发送 Handover Command消息；
步驟 414: 如果 UE-1有 CS业务， 则原网络基站系统合并步驟 411和 步驟 413中的切换命令中的信息， 否则不执行合并功能， 并向 UE-1发送切 换命令， 比如发送 Handover From UTRAN消息；
步驟 415~419、 与图 1中的步驟 114~118相同;
至此， UE- 1与数据网络网关通过目标网络基站系统和目标网服务网关 建立起承载连接， 使 UE-1的 PS业务可以继续进行， 且当 UE-1有与 UE-2 间的 CS业务时， UE-1与 UE-2间能建立起 IMS媒体连接 1 , 是 UE-1与 UE-2间的通话可以继续进行。
当然， 本发明还可有其他多种实施例， 在不背离本发明精神及其实质的 情况下， 熟悉本领域的技术人员当可根据本发明作出各种相应的改变和变 形， 但这些相应的改变和变形都应属于本发明所附的权利要求的保护范围。

Claims

权利要求书
1、 一种反向单待业务连续性承载切换方法， 其中， 该方法包括： 基站判定测量报告发送方有电路交换 CS 业务， 则在向移动交换中心 MSC和向原网络数据域控制实体发送的切换请求中携带用于反向单待业务 连续性 rSRVCC的目标标识信息。
2、 根据权利要求 1所述的方法， 其中， 该方法还包括： MSC和原网络 数据域控制实体根据所述切换请求中携带的用于 rSRVCC的目标标识信息 的部分或全部信息进行 DNS解析， 得到唯一地址信息。
3、 根据权利要求 1所述的方法， 其中， 该方法还包括： 基站判定测量 才艮告发送方没有 CS业务， 则在向 MSC和向原网络数据域控制实体发送的 切换请求中携带用于只有 PS切换的目标标识信息或用于 rSRVCC的目标标 识信息。
4、 根据权利要求 1所述的方法， 其中， 所述用于 rSRVCC的目标标识 信息与用于只有 PS切换的目标标识信息不同。
5、 根据权利要求 1至 4任一项所述的方法， 其中，
所述基站在切换请求中携带用于 rSRVCC的目标标识信息为： 所述基站选择用于 rSRVCC的目标标识信息，或者，根据用于 rSRVCC 的目标索引信息构造用于 rSRVCC的目标标识信息， 再将所述选择或构造 的用于 rSRVCC的目标标识信息携带在切换请求中，
所述基站在切换请求中携带用于只有 PS切换的目标标识信息为： 所述基站选择用于只有 PS切换的目标标识信息， 或者， 根据用于只有
PS切换的目标索引信息构造用于只有 PS切换的目标标识信息， 再将所述 选择或构造的用于只有 PS切换的目标标识信息携带在切换请求中。
6、 一种反向单待业务连续性承载切换装置， 其中， 该装置包括： 判断 模块、 发送模块； 其中， 所述判断模块， 设置为判断测量报告发送方是否有 CS业务； 所述发送模块， 设置为在判断模块判定测量报告发送方有 CS业务时， 在向 MSC和向原网络数据域控制实体发送的切换请求中携带用于 rSRVCC 的目标标识信息。
7、 根据权利要求 6所述的装置， 其中， 所述发送模块发送的切换请求 中携带的用于 rSRVCC的目标标识信息的部分或全部信息在 MSC和原网络 数据域控制实体进行 DNS解析后， 得到唯一地址信息。
8、 根据权利要求 6所述的装置， 其中，
所述发送模块，还设置为在判断模块判定测量报告发送方没有 CS业务 时，在向 MSC和向原网络数据域控制实体发送的切换请求中携带用于只有 PS切换的目标标识信息或用于 rSRVCC的目标标识信息。
9、 根据权利要求 6 所述的装置， 其中， 所述切换请求中携带的用于 rSRVCC的目标标识信息与用于只有 PS切换的目标标识信息不同。
10、 根据权利要求 6至 9任一项所述的装置， 其中， 该装置还包括目 标标识信息获耳 4莫块，
所述发送模块在切换请求中携带用于 rSRVCC的目标标识信息为： 将 目标标识信息获取模块选择或构造的用于 rSRVCC的目标标识信息携带在 切换请求中；
所述发送模块在切换请求中携带用于只有 PS切换的目标标识信息为： 将目标标识信息获取模块选择或构造的用于只有 PS切换的目标标识信息携 带在切换请求中；
所述目标标识信息获取模块， 设置为选择用于 rSRVCC的目标标识信 息， 或者， 根据用于 rSRVCC的目标索引信息构造用于 rSRVCC的目标标 识信息； 或者， 选择用于只有 PS切换的目标标识信息， 或者， 根据用于只 有 PS切换的目标索引信息构造用于只有 PS切换的目标标识信息。
PCT/CN2012/084030 2011-11-04 2012-11-02 一种反向单待业务连续性承载切换方法及装置 WO2013064105A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201110344936.2A CN103096392B (zh) 2011-11-04 2011-11-04 一种反向单待业务连续性承载切换方法及装置
CN201110344936.2 2011-11-04

Publications (1)

Publication Number Publication Date
WO2013064105A1 true WO2013064105A1 (zh) 2013-05-10

Family

ID=48191366

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/084030 WO2013064105A1 (zh) 2011-11-04 2012-11-02 一种反向单待业务连续性承载切换方法及装置

Country Status (2)

Country Link
CN (1) CN103096392B (zh)
WO (1) WO2013064105A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104756548B (zh) * 2014-06-30 2019-03-08 华为技术有限公司 切换方法、基站及移动管理实体
CN106572496A (zh) * 2015-10-09 2017-04-19 中兴通讯股份有限公司 负荷上报及控制方法、eMSC装置、MME装置及通信系统
US11523307B2 (en) 2017-12-13 2022-12-06 Telefonaktiebolaget Lm Ericsson (Publ) Network repository function in 5GC

Citations (3)

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

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101466122B (zh) * 2007-12-18 2010-04-21 华为技术有限公司 一种切换到演进的分组系统网络的方法、系统及装置
GB2467915B (en) * 2009-02-18 2012-05-09 Samsung Electronics Co Ltd Communication method for voice calls
US8937926B2 (en) * 2010-04-21 2015-01-20 Lg Electronics Inc. Device and method for performing an rSRVCC procedure
CN102238673A (zh) * 2010-04-26 2011-11-09 中兴通讯股份有限公司 反向单待业务连续性实现方法及系统

Patent Citations (3)

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

Also Published As

Publication number Publication date
CN103096392A (zh) 2013-05-08
CN103096392B (zh) 2018-07-20

Similar Documents

Publication Publication Date Title
US8180347B2 (en) Domain transferring method for single radio voice call continuity
US9408064B2 (en) Method and system for obtaining user equipment ability by user equipment, home subscriber data server and core network element
JP5694348B2 (ja) ハンドオーバー遅延の最適化
EP2482584B1 (en) Method and system for realizing single radio voice call continuity
WO2010025602A1 (zh) 紧急业务切换方法
JP2009509479A (ja) コールの継続を支援する無線通信方法およびシステム
JP6480011B2 (ja) 通信を確立するための方法及び移動無線通信ネットワーク構成要素
KR20120102771A (ko) 서비스 집중화 및 지속성 애플리케이션 서버(ｓｃｃ ａｓ)에 의해 개시되는 사용자 장치간 이전(ｉｕｔ), 액세스 이전 및 대체를 위한 방법 및 장치
JP5645329B2 (ja) 回線交換ドメインサービスをパケット交換ドメインにハンドオーバする方法及びシステム
WO2012024908A1 (zh) 一种终端能力上报的方法及系统
WO2010022611A1 (zh) 语音连续性呼叫切换的方法、系统及移动业务交换中心
JP2012533199A (ja) セッションの継続性を改善するための方法及びデバイス
EP2330852B1 (en) Method, apparatus and computer program for providing a voice connection to mobile station using Voice over internet protocol
WO2011057568A1 (zh) 一种会话切换的实现方法和系统
WO2011130949A1 (zh) 反向单待业务连续性实现方法及系统
WO2012149866A1 (zh) 单一无线语音呼叫连续性域的切换方法及系统
WO2013064105A1 (zh) 一种反向单待业务连续性承载切换方法及装置
WO2011134334A1 (zh) 反向单待业务连续性的实现方法及系统
WO2014005525A1 (zh) 资源承载的预留方法及系统
WO2011127790A1 (zh) 一种实现单待业务连续性会话保活的方法和系统
WO2011134341A1 (zh) 反向单待业务连续性实现方法及系统
CN102724723B (zh) 基于ims的控制切换方法及系统
WO2011130954A1 (zh) 单待终端业务连续性实现方法和系统
WO2011023054A1 (zh) 一种ip多媒体子系统中多会话能力同步方法及系统
WO2011097966A1 (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: 12845533

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

Country of ref document: EP

Kind code of ref document: A1