WO2009056059A1 - Procédé, système et dispositif de renvoi automatique d'appel - Google Patents

Procédé, système et dispositif de renvoi automatique d'appel Download PDF

Info

Publication number
WO2009056059A1
WO2009056059A1 PCT/CN2008/072812 CN2008072812W WO2009056059A1 WO 2009056059 A1 WO2009056059 A1 WO 2009056059A1 CN 2008072812 W CN2008072812 W CN 2008072812W WO 2009056059 A1 WO2009056059 A1 WO 2009056059A1
Authority
WO
WIPO (PCT)
Prior art keywords
call
user equipment
message
called user
release
Prior art date
Application number
PCT/CN2008/072812
Other languages
English (en)
French (fr)
Inventor
Shuiping Long
Hui Jin
Original Assignee
Huawei Technologies Co., Ltd.
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 Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Priority to ES08846040T priority Critical patent/ES2425145T3/es
Priority to JP2010530257A priority patent/JP5174178B2/ja
Priority to EP08846040.7A priority patent/EP2207336B1/en
Publication of WO2009056059A1 publication Critical patent/WO2009056059A1/zh
Priority to US12/765,682 priority patent/US20100202447A1/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/54—Arrangements for diverting calls for one subscriber to another predetermined subscriber
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1083—In-session procedures
    • H04L65/1094—Inter-user-equipment sessions transfer or sharing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1083—In-session procedures
    • H04L65/1095—Inter-network session transfer or sharing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1096—Supplementary features, e.g. call forwarding or call holding
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/58—Arrangements for transferring received calls from one subscriber to another; Arrangements affording interim conversations between either the calling or the called party and a third party
    • 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
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1101—Session protocols
    • H04L65/1104—Session initiation protocol [SIP]

Definitions

  • the present invention relates to the field of mobile communications, and in particular, to a method, system and device for call forwarding.
  • CS Mobile Switching
  • IP Multimedia Subsystem IP Multimedia
  • the IMS network can provide higher bandwidth than the CS network and support richer services.
  • the core of IMS is the Serving-Call Session Control Function (S-CSCF) entity and various service servers (Application Server,
  • the S-CSCF is responsible for routing the call request to the correct AS after the condition is met, and the AS performs the business logic, the telephony application server (Telephony Application Server)
  • TAS is one of the business servers. All supplementary services in IMS are controlled by TAS.
  • the IMS network is also a relatively complex network
  • the IMS network will not be deployed in a short period of time. This will inevitably lead to the coexistence of the CS network and the IMS network within a certain period of time.
  • operators need to realize the unification of two service platforms, CS and IMS, and transfer the functions of the CS network service platform to the IMS network. This leads to IMS Centralized Services (ICS).
  • ICS IMS Centralized Services
  • the user carries the voice media to establish an IMS call through the CS network, and the AS in the IMS provides the service for the call, and the CS bearer establishes the UE and the new
  • the CS call between the IMS Call Control Function (ICCF) of the incoming I is implemented, and the service processing logic in the MS C is weakened or removed.
  • media gateway control function is required (Media Gateway Control Function
  • MGCF MGCF
  • VCC Voice Call Control
  • AS can act as a back-to-back user agent (Back-to-Back-User-Agent)
  • the call forwarding service is one of the supplementary services, and the user who sets the service can transfer the received call to the set third party user, and the call forwarding service can include the call offset service, the call forwarding service, and the like. .
  • the call forwarding service is implemented across the CS network and the IMS network
  • the call switching server of the called terminal sends the call request to the called terminal
  • the called terminal performs the call forwarding function and sends the call forwarding function to the called user.
  • the MSC to which the device belongs initiates a transfer request; the MSC to which the called user equipment belongs sends call forwarding information to the call handover server, and carries the UE in the message.
  • the IMRN number is assigned to the MSC to which the called user equipment belongs; the MSC to which the called user equipment belongs uses the IMRN number to send a call request to the call handover server; According to the acquired UE
  • the number of 3 sends a call request to the S-CSCF entity; the S-CSCF entity routes the call request to the TAS according to the iFC, and the TAS acts as a user agent, and sends the call request to the UE through the S-CSCF entity.
  • the embodiment of the present invention provides a method, system, and device for call forwarding, so as to reduce network resource waste caused by call request signaling redundancy in a call flow after a called user performs a call forwarding service.
  • a method of call forwarding the method comprising:
  • a call forwarding system comprising: a call switching server and a TAS;
  • a call switching server configured to: after the called user equipment performs the call forwarding service, release a call signaling connection between the call switching server and the called user equipment, and send a redirect to the telephony application server TAS Business request for third-party user equipment.
  • a call handover server includes: a call transfer information acquisition unit, a release call message sending unit, and a redirect message sending unit;
  • a call forwarding information obtaining unit configured to acquire information about a called user equipment performing a call forwarding service
  • a resource releasing unit configured to acquire, by the call forwarding information acquiring unit, a called user equipment to perform a call forwarding service After the information is obtained, the signaling connection established between the call switching server and the called user equipment is released.
  • the redirecting unit is configured to send, after the call forwarding information obtaining unit acquires the information that the called user equipment performs the call forwarding service, to the TAS to send a service request redirected to the third-party user equipment.
  • FIG. 1 is a flowchart of a first method for call forwarding according to an embodiment of the present invention
  • FIG. 2 is a structural diagram of a system for call forwarding according to an embodiment of the present invention
  • FIG. 3 is a schematic structural diagram of a call switching server according to an embodiment of the present invention.
  • the method provided by the embodiment of the present invention mainly includes: after learning that the called user equipment performs the call forwarding service, releasing the call signaling connection established between the call switching server and the called user equipment, and sending a redirect to the telephony application server TAS.
  • the call switching server can be VCC
  • AS ICCF entity or other server that implements centralized centralized control of CS and IMS network call services, or a server that guarantees call continuity between CS and IMS networks.
  • the method for the call switching server to learn that the called user equipment performs the call forwarding service may include, but is not limited to, the following manner:
  • the second mode after the MSC to which the called user equipment belongs obtains the information of the called user equipment to perform the call forwarding service, the MSC may send a call request to the call handover server, and the call handover server determines whether the MSC is sent to the MSC to which the called user equipment belongs. The call request, if any, determines that the currently placed call is a call transfer service.
  • the call forwarding server may send the call forwarding indication information to the call switching server, so that the call switching server knows that the current call is the call forwarding.
  • Business for example, can switch to a call
  • FIG. 1 is a flowchart of a method for call forwarding according to an embodiment of the present invention.
  • a UE is used.
  • UE 1 is the called party user equipment, located in the CS network
  • UE 1 is the calling party user equipment, located in the IMS network
  • the call forwarding function is set, and the received call can be forwarded to the set third-party user equipment UE.
  • the method may include the following steps:
  • Step 101 UE 2 includes UE
  • the first Invite message of the 1 number sends a call request to the S-CSCF entity.
  • Step 102 The S-CSCF entity routes the first Invite message to the TAS according to the iFC.
  • Step 103 The TAS acts as a user agent, terminates the call request sent by the first Invite message, generates a second Invite message, and sends a call request to the S-CSCF entity by using the second Invite message.
  • Step 104 The S-CSCF entity routes the second Invite message to the VCC AS according to the iFC.
  • Step 105 VCC AS allocates circuit domain routing number to UE 1 of CS network (Circuit Switched domain Routing Number)
  • CSRN CSRN
  • CSRN CSRN
  • terminate the second Invite message generate a third Invite message
  • the AS is one of the call switching servers in the VCC service. In other services, other call switching servers can also be used. For example, in the IMS centralized control service, the ICCF entity can be used.
  • Step 106 The S-CSCF entity routes the call request sent by the third Invite message to the MGCF entity.
  • Step 107 The MGCF entity will receive the initial address message of the third Invite into the CS domain (Initial Address Message)
  • IAM IAM
  • Step 108 The MSC to which the called user equipment belongs converts the received IAM into a setup (Set
  • the call request is sent to the UE 1 by the Set up message.
  • Step 109 After receiving the call request, UE 1 performs a call transfer service.
  • the UE 1 inputs the number of the UE 3, and sends the number of the UE 3 to the MSC to which the called user equipment belongs by using the Disconnect message.
  • the MSC After receiving the Disconnect message, the MSC sends a Release message to the UE 1, the UE
  • the complete message is disconnected from the call request signaling of the MSC. If UE
  • UE 1 Perform a call forwarding function. For example, UE 1 can perform the busy forwarding function to the UE.
  • the MSC of 1 returns the user to determine the user is busy (User Determined User Busy,
  • UDUB UDUB
  • MSCs of UE 1 are referred to as MSCs in the following description of this embodiment.
  • Step 110 After obtaining the information that the UE 1 performs the call forwarding service, the MSC acquires the UE. 2 The set third-party user information, that is, the number of the UE 3, sends a service request for redirecting to the IMS network including the number of the UE 3 to the VCC AS. The service request redirected to the IMS network may be sent through an Initial Detection Points (IDP) message.
  • IDDP Initial Detection Points
  • the MSC may obtain the UE from the UE.
  • the call offset service is performed, and the number of the UE 3 is obtained in the Disconnect message; if the UE 1 performs the busy forwarding function, the MSC can acquire the UE through the UDUB message sent by the UE 1.
  • the subscription information of 1 obtains the third-party user information that UE 1 transfers before busy, that is, the number of UE 3.
  • Step 111 VCC
  • the AS After receiving the service request redirected to the IMS network, the AS learns that the called user equipment performs the call forwarding service and sends a Release call message to the MSC.
  • the called user equipment performs a call transfer service by using a service request redirected to the IMS network
  • the service request redirected to the IMS network may be an IMRN number request.
  • other methods for knowing the called user equipment to perform the call forwarding service may be used.
  • specific parameters may be set in the IDP message for indication, VCC.
  • the GSM service control function (gsmSCF) unit in the AS can learn from the specific parameters of the IDP message that the call is a call transfer service, and the third party user information is the number of the UE 3.
  • gsmSCF GSM service control function
  • the Release cair message sent by the MSC can include the reason for resource release.
  • Step 112 The MSC receives the Release
  • the L message is sent to the MGCF entity.
  • the REL message in this step is a message for instructing to release the network resources occupied by the call setup and call request signaling.
  • Step 113 The MGCF entity converts the REL message of the CS domain into a session initiation protocol according to the resource release reason included in the REL message (Session Initiated Protocol)
  • the release request message is sent to the S-CSCF entity.
  • the converted SIP release request message may be set to different messages according to different resource release reasons. For example, when the resource release reason is a client error, the SIP release request message may be a 4 86 message. 480 message, etc.; when the resource release reason is a server error, the SIP release request message may be a 500 message or the like.
  • Step 114 After receiving the SIP release request message, the S-CSCF entity routes the SIP release request message to the VCC AS according to the iFC.
  • step 112 to step 113 the call request signaling path established in steps 105 to 107 is removed, that is, the network resources occupied by the call request signaling established in steps 105 to 107 are released.
  • the manner of releasing the call signaling connection between the call switching service server and the called user equipment is to send a Release to the MSC to which the called user equipment belongs.
  • the cair message, the call signaling connection is released by the MSC to which the called user equipment belongs; or the call handover service server may actively release the call signaling connection between itself and the called user equipment.
  • Step 115 The VCC AS is based on the UE obtained in step 110
  • the number of 3 generates a service request redirected to the third-party user equipment, and sends the redirect message to the S-CSCF entity.
  • the service request redirected to the third-party user equipment generated in this step may be a 302 message, where the service request may include the number of the UE 3.
  • Step 115 and step 111 by sending a Release to the vMSC
  • the operation of the cair message rejecting the service request redirected to the IMS network can be performed simultaneously. That is, after the V CC AS obtains the call forwarding information, it may send a peer of the Release cair message to the MSC to which the called user equipment belongs, and send a redirect message to the S-CSCF entity; The associated MSC sends a Release call message, and then sends a redirect message to the S-CSCF entity.
  • Step 116 The S-CSCF entity routes the received redirect message to the TAS according to the iFC.
  • step 115 and step 116 the call request signaling path established in step 103 and step 104 is removed, that is, the network resources occupied by the call request signaling established in step 103 and step 104 are released.
  • Step 117 After receiving the redirect message, the TAS, as a user agent, generates a UE including the UE 3 number included in the service request redirected to the third-party user equipment.
  • Step 118 The S-CSCF entity routes the received call request to the UE 3.
  • the S-CSCF entity directly routes the received call request to the UE 3;
  • the S-CSCF entity routes the received call request to the UE.
  • An AM message, and the call request is sent to the vMSC of the UE 3 through the IAM message, by the UE
  • the vMSC of 3 sends the routing request to UE 3. This part is prior art and will not be mentioned here.
  • Step 119 The UE 3 returns an acknowledgement message to the UE 2.
  • the returned acknowledgment message is replied according to the signaling path of the call request.
  • the acknowledgment message may reflect the resource status occupied by the signaling of the current call request.
  • the process is greatly improved.
  • the redundancy of call signaling saves network resources occupied by call signaling.
  • FIG. 2 is a structural diagram of a system for call forwarding according to an embodiment of the present invention. As shown in FIG. 2, the system mainly includes: a call handover server 201 and a TAS 202.
  • the call switching server 201 is configured to: after the called user equipment performs the call forwarding service, release the call signaling connection established between the call switching server and the called user equipment, and send a redirect to the telephony application server T AS. A business request to a third-party user device.
  • the method is configured to receive a service request that is sent by the call switching server 201 and redirected to the third user equipment.
  • the call switching server 201 can be VCC
  • AS ICCF entity or other server that implements centralized centralized control of CS and IMS network call services, or a server that guarantees call continuity between CS and IMS networks.
  • the system may further include: an MSC 203 to which the called user equipment belongs,
  • the MSC 203 to which the called user equipment belongs can be used to receive the Release.
  • a release request REL message is generated, and the REL message is sent.
  • MGCF entity 204 configured to receive the MSC to which the called user equipment belongs
  • the REL message sent by the 203 is converted into a SIP release request message according to the resource release reason included in the REL message, and the SIP release request message is sent to the S-CSCF entity 205.
  • the S-CSCF entity 205 is configured to route the received SIP release request message to the call handover server 301.
  • the call switching server 201 is further configured to send a Release to the MSC to which the called user equipment belongs.
  • the above operation between the S-CSCF entity 205 and the call switching server 201 can release the call connection established between the MSC 203 and the call switching server 201 to which the called user equipment belongs.
  • the S-CSCF entity 205 is further configured to receive a redirect message sent by the call handover server 201, and send the redirect message to the TAS 202.
  • FIG. 3 is a schematic structural diagram of a call switching server 201 according to an embodiment of the present invention.
  • the call switching server may include: a call forwarding information acquiring unit 301, and a release call message sending unit.
  • the call forwarding information obtaining unit 301 is configured to acquire information about the called user equipment performing the call forwarding service.
  • the resource release unit 302 is configured to: after the call forwarding information acquiring unit 301 acquires the information about the call forwarding service performed by the called user equipment, release the signaling connection established between the call forwarding server and the called user equipment. .
  • the redirecting unit 303 is configured to: after the call forwarding information acquiring unit 301 obtains the call forwarding information,
  • the TAS sends a service request redirected to a third-party user device.
  • the resource release unit 302 includes: Release cair message generation module 3021 and Release
  • the cair message sending module 3022 The cair message sending module 3022.
  • the cair message generating module 3021 is configured to generate a Release call message after the call forwarding information obtaining unit 301 acquires the information of the called user equipment to perform the call forwarding service.
  • the Release call message generated by the cair message generating module 3021 As can be seen from the above description, in the technical solution provided by the embodiment of the present invention, after the called user equipment performs the call forwarding service, the call signaling connection established between the call switching server and the called user equipment is released. A service request redirected to a third party user device is sent to the telephony application server TAS. In the call flow after the called user performs the call forwarding service, the call request is no longer through the call handover server, but the signaling connection established between the called user equipment and the call handover server may be released, and the redirect is sent to the TAS. The service request to the third-party user equipment instructs the TAS to send a call request to the third-party user equipment, thereby reducing call request signaling and saving network resources occupied by the call.
  • the MSC to which the called user equipment belongs does not need to participate in the receiving and sending work in the call flow after the called user performs the call forwarding service, thereby reducing the burden on the vMSC.
  • the technical solution provided by the embodiment of the present invention does not need to perform CS and signaling and SIP signaling conversion again in the call flow after the called user performs the call forwarding service, and the call switching server directly passes Sending a redirect message to the TAS indicates that the TAS sends a call request to the third-party user equipment, which reduces the signaling establishment between the calling user equipment and the third-party user equipment, and provides a better service experience for the user.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephonic Communication Services (AREA)

Description

说明书 一种呼叫转移的方法、 系统和设备
[1] 本发明要求于 2007年 10月 25日提交中国专利局、 申请号为 200710165402.7、 发 明名称为"一种呼叫转移的方法、 系统和设备"的中国专利申请的优先权， 其全部 内容通过引用结合在本申请中。
[2] 技术领域
[3] 本发明涉及移动通信领域， 特别涉及一种呼叫转移的方法、 系统和设备。
[4] 发明背景
[5] 目前的移动通信网络以电路交换 （Circuit Service
， CS) 为主， 各运营商基于 CS网络已经建立了比较完善和丰富的业务平台， 其 中移动交换中心 (Mobile Switching
Cente, MSC) 负责呼叫路由和业务逻辑执行， 例如呼叫转移业务。 随着移动通 信技术的不断发展， 出现了基于 IP交换的业务网络， 即 IP多媒体子系统 （IP Multimedia
Subsystem, IMS) 。 IMS网络相对 CS网络能够提供更高的带宽， 支持更丰富的 业务。 IMS的核心是服务呼叫会话功能 （Serving- Call Session Control Function ， S-CSCF) 实体和各种业务服务器 （Application Server,
AS) ， S-CSCF负责在满足条件吋将呼叫请求路由到正确的 AS， 由 AS执行业务 逻辑， 电话应用服务器 (Telephony Application Server
， TAS) 就是其中一种业务服务器， IMS中所有的补充业务都是由 TAS来控制实 现的。
[6] 由于 IMS网络也是一种比较复杂的网络， 因此， IMS网络不会在短吋间内部署 完成， 这就必然会存在一定吋期内 CS网络和 IMS网络共存的局面。 运营商为了 节约建设成本， 需要实现 CS和 IMS两个业务平台的统一， 将 CS网络业务平台的 功能转移到 IMS网络， 这就出现了 IMS集中业务控制技术 （IMS Centralized Services, ICS) 。 在该 ICS业务中， 实现用户 （UE) 通过 CS网络承载语音媒体 来建立 IMS呼叫， 由 IMS中的 AS对呼叫进行业务提供， CS承载通过建立 UE和新 弓 I入的 IMS呼叫控制功能 （ICCF) 之间的 CS呼叫来实现， 同吋， 削弱或去除 MS C中的业务处理逻辑。 在这种技术中， 需要媒体网关控制功能 （Media Gateway Control Function
， MGCF) 实体来实现 CS网络和 IMS网络之间信令和媒体的转换。
[7] 语音呼叫连续性 (Voice Call Continuity
， VCC) 技术是语音呼叫在 CS网络和 IMS网络间转移吋， 保证语音呼叫连续性 的技术， 该技术的核心是 VCC
AS , 所有的呼叫或会话都必须通过 IMS网络的 VCC AS， VCC
AS可以作为背靠背用户代理 （Back-to-Back-User- Agent
， B2BUA) 进行后续的域切换控制。
[8] 呼叫转移业务是补充业务中的一种， 设定该业务的用户可以将接收到的呼叫转 移到设定的第三方用户， 呼叫转移业务可以包含呼叫偏移业务、 呼叫前转业务 等。 现有技术中， 在实现跨 CS网络和 IMS网络的呼叫转移业务吋， 通常被叫终 端的呼叫切换服务器将呼叫请求发送到被叫终端后， 被叫终端执行呼叫转移功 能， 并向被叫用户设备所属的 MSC发起转移请求； 被叫用户设备所属的 MSC向 呼叫切换服务器发送呼叫转移信息， 在该消息中携带 UE
3的号码； 在呼叫切换服务器收到呼叫转移信息后， 为被叫用户设备所属的 MSC 分配 IMRN号码； 被叫用户设备所属的 MSC利用该 IMRN号码向呼叫切换服务器 发送呼叫请求； 由呼叫切换服务器根据获取的 UE
3的号码向 S-CSCF实体发送呼叫请求； 由 S-CSCF实体根据 iFC将呼叫请求路由到 TAS , 由 TAS作为用户代理， 将呼叫请求通过 S-CSCF实体发送至 UE
3， 即在被叫用户 UE
1执行呼叫转移业务后的呼叫流程中， 存在呼叫请求信令的冗余， 造成了网络资 源的浪费。
[9] 发明内容
[10] 本发明实施例提供了一种呼叫转移的方法、 系统和设备， 以便于在被叫用户执 行呼叫转移业务后的呼叫流程中， 减小呼叫请求信令冗余造成的网络资源浪费 [11] 一种呼叫转移的方法， 该方法包括：
[12] 获知被叫用户设备执行呼叫转移业务后， 释放呼叫切换服务器与被叫用户设备 之间建立的呼叫信令连接， 向电话应用服务器 TAS发送重定向到第三方用户设备 的业务请求。
[13] 一种呼叫转移的系统， 该系统包括： 呼叫切换服务器和 TAS;
[14] 呼叫切换服务器， 用于获知被叫用户设备执行呼叫转移业务后， 释放所述呼叫 切换服务器与所述被叫用户设备之间的呼叫信令连接， 向电话应用服务器 TAS发 送重定向到第三方用户设备的业务请求。
[15] 一种呼叫切换服务器， 该呼叫切换服务器包括： 呼叫转移信息获取单元、 释放 呼叫消息发送单元和重定向消息发送单元；
[16] 呼叫转移信息获取单元， 用于获取被叫用户设备执行呼叫转移业务的信息； [17] 资源释放单元， 用于在所述呼叫转移信息获取单元获取到被叫用户设备执行呼 叫转移业务的信息后， 释放自身所在呼叫切换服务器与被叫用户设备之间建立 的信令连接；
[18] 重定向单元， 用于在所述呼叫转移信息获取单元获取到被叫用户设备执行呼叫 转移业务的信息后， 向 TAS发送重定向到第三方用户设备的业务请求。
[19] 由以上技术方案可以看出， 在本发明实施例提供的方法、 系统和设备中， 获知 被叫用户设备执行呼叫转移业务后， 释放呼叫切换服务器与被叫用户设备之间 建立的呼叫信令连接， 向 TAS发送重定向到第三方用户设备的业务请求。 使得在 被叫用户执行呼叫转移业务后的呼叫流程中， 呼叫请求不再通过呼叫切换服务 器， 而是可以释放被叫用户设备与呼叫切换服务器之间建立的信令连接， 通过 向 TAS发送重定向到第三方用户设备的业务请求指示 TAS向第三方用户设备发送 呼叫请求， 从而减少了呼叫请求信令， 节省了呼叫占用的网络资源。
[20] 附图简要说明
[21] 图 1为本发明实施例提供的第一种呼叫转移的方法流程图；
[22] 图 2为本发明实施例提供的呼叫转移的系统结构图；
[23] 图 3为本发明实施例提供的呼叫切换服务器的结构示意图。
[24] 具体实施方式 [25] 为了使本发明的目的、 技术方案和优点更加清楚， 下面结合附图和具体实施例 对本发明进行详细描述。
[26] 本发明实施例提供的方法主要包括： 获知被叫用户设备执行呼叫转移业务后， 释放呼叫切换服务器与被叫用户设备之间建立的呼叫信令连接， 向电话应用服 务器 TAS发送重定向到第三方用户设备的业务请求。
[27] 其中的呼叫切换服务器可以为 VCC
AS、 ICCF实体或其它实现 CS和 IMS网络呼叫业务统一集中控制的服务器， 或保 证 CS和 IMS网络之间呼叫连续性的服务器。
[28] 其中， 呼叫切换服务器获知被叫用户设备执行呼叫转移业务的方法可以包括但 不限于以下方式： 第一种方式： 被叫用户设备所属的 MSC获取到被叫用户设备 执行呼叫转移业务的信息后， 向呼叫切换服务器发送重定向到 IMS网络的业务请 求， 呼叫切换服务器通过该重定向到 IMS网络的业务请求， 获知当前进行的呼叫 为呼叫转移业务的呼叫。 第二种方式： 被叫用户设备所属的 MSC获取到被叫用 户设备执行呼叫转移业务的信息后， 可以向呼叫切换服务器发送呼叫请求， 呼 叫切换服务器判断之前是否向被叫用户设备所属的 MSC发送呼叫请求， 如果有 ， 则判断当前进行的呼叫为呼叫转移业务。 第三种方式： 被叫用户设备所属的 M SC获取到被叫用户设备执行呼叫转移业务的信息后， 可以向呼叫切换服务器发 送呼叫转移指示信息， 使呼叫切换服务器获知当前进行的呼叫为呼叫转移业务 ， 例如， 可以在向呼叫切换
[29] 服务器中发送的消息中设置特定参数携带呼叫转移信息。
[30] 下面结合具体实施例对上述方法进行详细描述， 图 1为本发明实施例提供的第 一种呼叫转移的方法流程图， 在该实施例中， UE
2为主叫方用户设备， 位于 IMS网络， UE 1为被叫方用户设备， 位于 CS网络， UE
1设置了呼叫转移功能， 可以将接收到的呼叫前转至设置的第三方用户设备 UE
3。 如图 1所示， 该方法可以包括以下步骤：
[31] 步骤 101 : UE 2通过包含 UE
1号码的第一 Invite消息向 S-CSCF实体发送呼叫请求。
[32] 步骤 102: S-CSCF实体根据 iFC， 将该第一 Invite消息路由到 TAS。 [33] 步骤 103: TAS作为用户代理， 终结该通过第一 Invite消息发送的呼叫请求， 生 成第二 Invite消息， 通过该第二 Invite消息向 S-CSCF实体发送呼叫请求。
[34] 步骤 104: S-CSCF实体根据 iFC， 将该第二 Invite消息路由到 VCC AS。
[35] 步骤 105: VCC AS为 CS网络的 UE 1分配电路域路由号码 （Circuit Switched domain Routing Number
， CSRN) ， 并作为用户代理， 终结第二 Invite消息， 生成第三 Invite消息， 通过 包含 CSRN的第三 Invite消息向 S-CSCF实体发送呼叫请求。
[36] 其中， VCC
AS是其中一种在 VCC业务中的呼叫切换服务器， 在其它业务中， 还可以釆用其 它呼叫切换服务器， 例如： 在 IMS集中控制业务中， 可以釆用 ICCF实体等。
[37] 步骤 106: S-CSCF实体将通过该第三 Invite消息发送的呼叫请求路由到 MGCF实 体。
[38] 步骤 107: MGCF实体将接收到第三 Invite转换成 CS域的初始地址消息 （Initial Address Message
， IAM) ， 通过该 IAM消息向被叫用户设备所属的 MSC发送呼叫请求。
[39] 步骤 108: 被叫用户设备所属的 MSC将接收到的 IAM转换成建立 （Set
up) 消息， 通过该 Set up消息将呼叫请求发送给 UE 1。
[40] 步骤 109: UE 1接收到该呼叫请求后， 执行呼叫转移业务。
[41] 在该步骤中， 如果 UE 1执行呼叫偏移功能， 则 UE 1输入 UE 3的号码， 将该 UE 3的号码通过 Disconnect消息发送给被叫用户设备所属的 MSC， 被叫用户设备所 属的 MSC收到该 Disconnect消息后， 向 UE 1发送 Release消息， UE
1接收到 Release消息后， 回复 Release
complete消息断幵与 MSC的呼叫请求信令连接。 如果 UE
1执行呼叫前转功能， 例如， UE 1此吋可以执行遇忙前转功能， 向 UE
1的 MSC返回用户决定用户忙 （User Determined User Busy,
UDUB) 消息， 表明 UE 1当前忙。
[42] 为了描述方便， 在该实施例的下述描述中将 UE 1的 MSC均称为 MSC。
[43] 步骤 110: MSC获取到 UE 1执行呼叫转移业务的信息后， 获取 UE 2设置的第三方用户信息， 即 UE 3的号码， 向 VCC AS发送包含 UE 3的号码的重定向到 IMS网络的业务请求。 该重定向到 IMS网络的业务请求可以 通过初始检测点 (initial Detection Points , IDP) 消息发送。
[44] 本步骤中， 如果 UE 1执行了呼叫偏移业务， MSC可以从 UE
1发送的 Disconnect消息获取 UE
1执行了呼叫偏移业务， 并且在该 Disconnect消息中获取 UE 3的号码； 如果 UE 1执行了遇忙前转功能， 则 MSC可以通过 UE 1发送的 UDUB消息获取 UE
1执行了遇忙前转功能， 并从 VLR中获取 UE 1的签约信息， 从 UE
1的签约信息中获取 UE 1遇忙前转吋的第三方用户信息， 即 UE 3的号码。
[45] 以上步骤 101至步骤 110为现有技术中已有的流程。
[46] 步骤 111 : VCC
AS接收到该重定向到 IMS网络的业务请求后， 获知被叫用户设备执行呼叫转移 业务， 向 MSC发送 Release call消息。
[47] 本发明实施例中以通过重定向到 IMS网络的业务请求获知被叫用户设备执行呼 叫转移业务为例进行描述， 该重定向到 IMS网络的业务请求可以是 IMRN号码请 求。 当然也可以使用其它获知被叫用户设备执行呼叫转移业务的方法， 例如， 可以在 IDP消息中设置特定参数进行指示， VCC
AS中的 GSM业务控制功能 （gsmSCF) 单元可以从 IDP消息的特定参数中获知该 呼叫为呼叫转移业务， 其第三方用户信息为 UE 3的号码。
[48] MSC发送的 Release cair消息中可以包含资源释放原因。
[49] 步骤 112: MSC接收到该 Release
cair消息后， 生成包含资源释放原因的 CS域的释放请求 （REL) 消息， 并将该 RE
L消息发送给 MGCF实体。
[50] 本步骤中的 REL消息是用于指示释放呼叫建立吋呼叫请求信令所占用的网络资 源的消息。
[51] 步骤 113: MGCF实体根据 REL消息中包含的资源释放原因， 将 CS域的 REL消 息转换成会话初始协议 （Session Initiated Protocol
， SIP) 释放请求消息发送给 S-CSCF实体。 [52] 本步骤中， 转换后的的 SIP释放请求消息可以根据不同的资源释放原因设置成 不同的消息， 例如， 当资源释放原因为客户端错误吋， SIP释放请求消息可以为 4 86消息、 480消息等； 当资源释放原因为服务器错误吋， SIP释放请求消息可以为 500消息等。
[53] 步骤 114: S-CSCF实体接收到 SIP释放请求消息后， 根据 iFC将该 SIP释放请求消 息路由到 VCC AS。
[54] 在步骤 112至步骤 113之后， 在步骤 105至步骤 107中建立的呼叫请求信令路径被 拆除， 即步骤 105至步骤 107中建立的呼叫请求信令占用的网络资源被释放。
[55] 上述释放呼叫切换业务服务器和被叫用户设备之间呼叫信令连接的方式是通过 向被叫用户设备所属的 MSC发送 Release
cair消息， 由被叫用户设备所属的 MSC释放该呼叫信令连接； 也可以釆用呼切换 业务服务器主动释放其自身与被叫用户设备之间的呼叫信令连接。
[56] 步骤 115: VCC AS根据在步骤 110中获取的 UE
3的号码， 生成重定向到第三方用户设备的业务请求， 并将该重定向消息发送给 S-CSCF实体。
[57] 本步骤中生成的重定向到第三方用户设备的业务请求可以是 302消息， 该业务 请求中可以包含 UE 3的号码。
[58] 步骤 115可以和步骤 111中通过向 vMSC发送 Release
cair消息拒绝重定向到 IMS网络的业务请求的操作可以同吋进行。 也就是说， 在 V CC AS获取到呼叫转移信息后， 可以向被叫用户设备所属的 MSC发送 Release cair消息的同吋， 向 S-CSCF实体发送重定向消息； 也可以先向被叫用户设备所属 的 MSC发送 Release call消息， 再向 S-CSCF实体发送重定向消息。
[59] 步骤 116: S-CSCF实体根据 iFC, 将接收到的重定向消息路由到 TAS。
[60] 步骤 115和步骤 116之后， 在步骤 103和步骤 104中建立的呼叫请求信令路径被拆 除， 即步骤 103和步骤 104中建立的呼叫请求信令占用的网络资源被释放。
[61] 步骤 117: TAS接收到重定向消息后， 作为用户代理， 利用重定向到第三方用 户设备的业务请求中包含的 UE 3号码， 生成包含 UE
3号码的第四 Invite消息， 通过该第四 Invite消息向 S-CSCF实体发送呼叫请求。 [62] 步骤 118: S-CSCF实体将接收到的呼叫请求路由到 UE 3。
[63] 如果 UE
3是 IMS网络的用户设备， 贝 l」S-CSCF实体将接收到的呼叫请求直接路由到 UE 3； 如果 UE
3是 CS网络的用户设备， 贝 l」S-CSCF实体将接收到的呼叫请求路由到 UE
3所属网络的 MGCF实体， MGCF实体将承载该呼叫请求的第四 Invite消息转换为 I
AM消息， 并通过该 IAM消息将呼叫请求发送给 UE 3的 vMSC， 由 UE
3的 vMSC将该路由请求发送给 UE 3。 该部分为现有技术， 在此不再赞述。
[64] 步骤 119: UE 3向 UE 2返回确认消息。
[65] 由于 UE 3向 UE
2返回的确认消息吋按照呼叫请求的信令路径回复的， 该确认消息可以反映出目 前呼叫请求的信令占用的资源状况， 由步骤 119中返回的确认消息可以看出， 使 用该流程大大改善了呼叫信令的冗余状况， 节约了呼叫信令占用的网络资源。
[66] 图 2为本发明实施例提供的呼叫转移的系统结构图， 如图 2所示， 该系统主要包 括： 呼叫切换服务器 201和 TAS 202。
[67] 呼叫切换服务器 201， 用于获知被叫用户设备执行呼叫转移业务后， 释放所述 呼叫切换服务器与被叫用户设备之间建立的呼叫信令连接， 向电话应用服务器 T AS发送重定向到第三方用户设备的业务请求。
[68] TAS
202， 用于接收呼叫切换服务器 201发送的重定向到第三用户设备的业务请求。
[69] 其中， 呼叫切换服务器 201可以为 VCC
AS、 ICCF实体或其它实现 CS和 IMS网络呼叫业务统一集中控制的服务器， 或保 证 CS和 IMS网络之间呼叫连续性的服务器。
[70] 该系统还可以包括： 被叫用户设备所属的 MSC 203、
MGCF实体 204和 S-CSCF实体 205。
[71] 其中， 被叫用户设备所属的 MSC 203， 可以用于接收到 Release
cair消息后生成释放请求 REL消息， 并发送该 REL消息。
[72] MGCF实体 204， 用于接收被叫用户设备所属的 MSC 203发送的 REL消息， 根据该 REL消息中包含的资源释放原因， 将 REL消息转换 成 SIP释放请求消息， 并将该 SIP释放请求消息发送给 S-CSCF实体 205。
[73] S-CSCF实体 205， 用于将接收到的 SIP释放请求消息路由到呼叫切换服务器 301
[74] 呼叫切换服务器 201， 还用于向被叫用户设备所属的 MSC发送 Release
call消息。
[75] 通过被叫用户设备所属的 MSC 203、 MGCF实体 204
、 S-CSCF实体 205和呼叫切换服务器 201之间的上述操作可以释放被叫用户设备 所属的 MSC 203和呼叫切换服务器 201之间建立的呼叫连接。
[76] S-CSCF实体 205， 还可以用于接收呼叫切换服务器 201发送的重定向消息， 将 该重定向消息发送给 TAS 202。
[77] 图 3为本发明实施例提供的呼叫切换服务器 201的结构示意图， 如图 3所示， 该 呼叫切换服务器可以包括： 呼叫转移信息获取单元 301、 释放呼叫消息发送单元
302和重定向消息发送单元 303。
[78] 呼叫转移信息获取单元 301， 用于获取被叫用户设备执行呼叫转移业务的信息
[79] 资源释放单元 302， 用于在呼叫转移信息获取单元 301获取到被叫用户设备执行 呼叫转移业务的信息后， 释放自身所在与呼叫切换服务器与被叫用户设备之间 建立的信令连接。
[80] 重定向单元 303， 用于在呼叫转移信息获取单元 301获取到呼叫转移信息后， 向
TAS发送重定向到第三方用户设备的业务请求。
[81] 其中， 资源释放单元 302包括： Release cair消息生成模块 3021和 Release
cair消息发送模块 3022。
[82] Release
cair消息生成模块 3021， 用于在呼叫转移信息获取单元 301获取到被叫用户设备执 行呼叫转移业务的信息后， 生成 Release call消息。
[83] Release cair消息发送模块 3022， 用于发送 Release
cair消息生成模块 3021生成的所述 Release call消息。 [84] 由以上描述可以看出， 在本发明实施例提供的技术方案中， 获知被叫用户设备 执行呼叫转移业务后， 释放呼叫切换服务器与被叫用户设备之间建立的呼叫信 令连接， 向电话应用服务器 TAS发送重定向到第三方用户设备的业务请求。 使得 在被叫用户执行呼叫转移业务后的呼叫流程中， 呼叫请求不再通过呼叫切换服 务器， 而是可以释放被叫用户设备与呼叫切换服务器之间建立的信令连接， 通 过向 TAS发送重定向到第三方用户设备的业务请求指示 TAS向第三方用户设备发 送呼叫请求， 从而减少了呼叫请求信令， 节省了呼叫占用的网络资源。
[85] 并且， 本发明实施例提供的技术方案， 在被叫用户执行呼叫转移业务后的呼叫 流程中不再需要被叫用户设备所属的 MSC参与接收和发送工作， 减少了 vMSC的 负担。
[86] 更进一步地， 本发明实施例提供的技术方案， 在被叫用户执行呼叫转移业务后 的呼叫流程中不需要再一次进行 CS与信令和 SIP信令的转换， 呼叫切换服务器直 接通过向 TAS发送重定向消息指示 TAS向第三方用户设备发送呼叫请求， 减少了 主叫用户设备与第三方用户设备之间的信令建立吋间， 给用户带来更好的业务 体验。
[87] 以上所述仅为本发明的较佳实施例而已， 并不用以限制本发明， 凡在本发明的 精神和原则之内， 所做的任何修改、 等同替换、 改进等， 均应包含在本发明保 护的范围之内。

Claims

权利要求书
[1] 一种呼叫转移的方法， 其特征在于， 该方法包括：
获知被叫用户设备执行呼叫转移业务后， 释放呼叫切换服务器与所述被叫 用户设备之间的呼叫信令连接， 并向电话应用服务器 TAS发送重定向到第 三方用户设备的业务请求。
[2] 根据权利要求 1所述的方法， 其特征在于， 所述获知被叫用户设备执行呼叫 转移业务包括： 通过被叫用户设备所属的移动交换中心 MSC发送的重定向 到 IP多媒体子系统 IMS网络的业务请求， 获知被叫用户设备执行呼叫转移 业务； 或者，
在针对该被叫用户向被叫用户设备所属的 MSC发送呼叫请求后， 通过接收 到该被叫用户设备所属的 MSC针对所述被叫用户发送的呼叫请求获知所述 被叫用户设备执行呼叫转移业务； 或者，
通过所述被叫用户设备所属的 MSC发送的呼叫转移指示信息获知被叫用户 设备执行呼叫转移业务。
[3] 根据权利要求 1所述的方法， 其特征在于， 所述释放呼叫切换服务器与被叫 用户设备之间的呼叫信令连接包括： 向被叫用户设备所属的 MSC发送释放 呼叫 Release
call消息， 由所述被叫用户设备所属的 MSC释放所述呼叫切换服务器与被叫 用户设备之间的呼叫信令连接。
[4] 根据权利要求 1所述的方法， 其特征在于， 所述释放呼叫切换服务器与被叫 用户设备之间的呼叫信令连接包括： 向被叫用户设备所属的 MSC发送释放 呼叫 Release
call消息， 由呼叫切换服务器释放自身与被叫用户设备之间的呼叫信令连接
[5] 根据权利要求 3所述的方法， 其特征在于， 由所述被叫用户设备所属的 MS
C释放呼叫切换服务器与被叫用户设备之间的呼叫信令连接包括： 所述被叫用户设备所属的 MSC接收到该 Release
cair消息后生成释放请求 REL消息， 并将该 REL消息发送给媒体网关控制功 能 MGCF实体， 所述 MGCF实体根据所述 REL消息中包含的资源释放原因， 将 REL消息转换成会话初始协议 SIP释放请求消息， 并通过服务呼叫会话控 制功能 S-CSCF实体将所述 SIP释放消息路由到呼叫切换服务器。
[6] 根据权利要求 5所述的方法， 其特征在于， 当所述 REL消息中包含的资源释 放原因为客户端错误吋， 所述转换成的 SIP释放请求消息为 486消息或 480消 息；
当所述 REL消息中包含的资源释放原因为服务器错误吋， 所述转换成的 SIP 释放请求消息为 500消息。
[7] 根据权利要求 1所述的方法， 其特征在于， 该方法还包括： 所述 TAS接收到 所述重定向到第三方用户设备的业务请求后， 利用所述重定向到第三方用 户设备的业务请求中包含的第三方用户信息生成 Invite消息， 并将生成的 In vite消息发送给所述第三方用户设备。
[8] 根据权利要求 1所述的方法， 其特征在于， 所述重定向到第三方用户设备的 业务请求包括 301消息或 302消息。
[9] 一种呼叫转移的系统， 其特征在于， 该系统包括： 呼叫切换服务器；
呼叫切换服务器， 用于获知被叫用户设备执行呼叫转移业务后， 释放所述 呼叫切换服务器与所述被叫用户设备之间的呼叫信令连接， 向电话应用服 务器 TAS发送重定向到第三方用户设备的业务请求。
[10] 根据权利要求 9所述的系统， 其特征在于， 该系统还包括： 被叫用户设备所 属的移动交换中心 MSC
， 媒体网关控制功能 MGCF实体和服务呼叫会话控制功能 S-CSCF实体； 被叫用户设备所属的 MSC, 接收到所述呼叫切换服务器发送的 Release cair消息后生成释放请求 REL消息， 并发送所述 REL消息；
MGCF实体， 用于接收所述被叫用户设备所属的 MSC发送的 REL消息， 根 据所述 REL消息中包含的资源释放原因， 将 REL消息转换成 SIP释放请求消 息， 并将该 SIP释放请求消息发送给 S-CSCF实体；
S-CSCF实体， 用于将接收到的 SIP释放请求消息路由到所述呼叫切换服务 器。
[11] 一种呼叫切换服务器， 其特征在于， 所述呼叫切换服务器包括： 呼叫转移信息获取单元， 用于获取被叫用户设备执行呼叫转移业务的信息 资源释放单元， 用于在所述呼叫转移信息获取单元获取到被叫用户设备执 行呼叫转移业务的信息后， 释放自身所在的呼叫切换服务器与被叫用户设 备之间的呼叫信令连接；
重定向单元， 用于在所述呼叫转移信息获取单元获取到被叫用户设备执行 呼叫转移业务的信息后， 向电话应用服务器 TAS发送重定向到第三方用户 设备的业务请求。
[12] 根据权利要求 11所述的呼叫切换服务器， 其特征在于， 所述资源释放单元 包括：
Release
cair消息生成模块， 用于在所述呼叫转移信息获取单元获取到被叫用户设备 执行呼叫转移业务的信息后， 生成 Release call消息；
Release cair消息发送模块， 用于发送所述 Release
call消息生成模块生成的所述 Release cair消息。
PCT/CN2008/072812 2007-10-25 2008-10-24 Procédé, système et dispositif de renvoi automatique d'appel WO2009056059A1 (fr)

Priority Applications (4)

Application Number Priority Date Filing Date Title
ES08846040T ES2425145T3 (es) 2007-10-25 2008-10-24 Método, sistema y dispositivo para la transferencia de llamadas
JP2010530257A JP5174178B2 (ja) 2007-10-25 2008-10-24 着信転送のための方法、システム、およびデバイス
EP08846040.7A EP2207336B1 (en) 2007-10-25 2008-10-24 Method, system and device of call forwarding
US12/765,682 US20100202447A1 (en) 2007-10-25 2010-04-22 Call Transfer Method, System and Device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200710165402.7 2007-10-25
CN2007101654027A CN101420669B (zh) 2007-10-25 2007-10-25 一种呼叫转移的方法、系统和设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US12/765,682 Continuation US20100202447A1 (en) 2007-10-25 2010-04-22 Call Transfer Method, System and Device

Publications (1)

Publication Number Publication Date
WO2009056059A1 true WO2009056059A1 (fr) 2009-05-07

Family

ID=40590561

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2008/072812 WO2009056059A1 (fr) 2007-10-25 2008-10-24 Procédé, système et dispositif de renvoi automatique d'appel

Country Status (7)

Country Link
US (1) US20100202447A1 (zh)
EP (1) EP2207336B1 (zh)
JP (1) JP5174178B2 (zh)
KR (1) KR101078676B1 (zh)
CN (1) CN101420669B (zh)
ES (1) ES2425145T3 (zh)
WO (1) WO2009056059A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102036201A (zh) * 2009-09-28 2011-04-27 中兴通讯股份有限公司 来电提示方法及装置

Families Citing this family (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101420668B (zh) * 2007-10-25 2010-10-13 华为技术有限公司 一种实现呼叫转移的方法、系统和设备
CN102055756B (zh) * 2009-10-27 2015-09-16 中兴通讯股份有限公司 叉簧类业务的处理方法和应用服务器
US8705566B2 (en) * 2010-01-28 2014-04-22 Siemens Enterprise Communications Gmbh & Co. Kg Method and apparatus in which call signaling messages bypass in-transparent switching nodes or networks
CN101820604A (zh) * 2010-05-27 2010-09-01 中兴通讯股份有限公司 呼叫接续方法、装置和系统
CN102595360B (zh) * 2011-01-05 2016-08-03 中兴通讯股份有限公司 呼叫处理方法及系统
CN102104695B (zh) * 2011-02-22 2014-08-20 中兴通讯股份有限公司 一种呼叫业务中实现双方通话随意切换的方法和系统
EP2739024B1 (en) * 2012-11-30 2017-01-04 Alcatel Lucent A method and a module for shifting a call established through a first application server in order to route it through a second application server
CN104010286B (zh) * 2013-02-25 2018-01-02 上海斐讯数据通信技术有限公司 呼叫转移方法及移动终端
US9253317B2 (en) 2013-09-03 2016-02-02 Echostar Technologies L.L.C. System and method to track and log mobile communication device call status when the device is not in possession
KR102049587B1 (ko) * 2013-09-16 2019-11-27 에스케이텔레콤 주식회사 착신망의 어플리케이션 서버 장애 처리를 위한 장치, 이를 위한 방법 및 이 방법이 기록된 컴퓨터 판독 가능한 기록매체
KR102049586B1 (ko) * 2013-10-10 2019-11-27 에스케이텔레콤 주식회사 착신망의 호 처리 기능 장애 처리를 위한 장치, 이를 위한 방법 및 이 방법이 기록된 컴퓨터 판독 가능한 기록매체
CN104661272A (zh) * 2013-11-18 2015-05-27 中兴通讯股份有限公司 呼叫前转/偏转业务的通知/触发方法、装置
JP2017097417A (ja) * 2015-11-18 2017-06-01 アガサ株式会社 臨床研究情報クラウドサービスシステムおよび臨床研究情報クラウドサービス方法
CN105430205A (zh) * 2015-12-30 2016-03-23 魅族科技（中国）有限公司 一种通话方法及通话装置
CN106506885A (zh) * 2016-09-24 2017-03-15 深圳市潮流网络技术有限公司 一种无感知电话转接方法

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20050076531A (ko) * 2004-01-20 2005-07-26 엘지전자 주식회사 휴대단말기의 착신전환 설정장치 및 방법
CN1874379A (zh) * 2006-01-26 2006-12-06 华为技术有限公司 移动通信系统中的呼叫转移方法

Family Cites Families (27)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US159251A (en) * 1875-02-02 Improvement in wheels for vehicles
FI97934C (fi) * 1994-05-04 1997-03-10 Nokia Telecommunications Oy Kutsunsiirtomenetelmä ja -järjestely matkaviestimelle päättyvän puhelun yhteydessä
US5867784A (en) * 1995-07-05 1999-02-02 Telefonaktiebolaget Lm Ericsson Call forwarding in a mobile communication system
JPH0965006A (ja) * 1995-08-25 1997-03-07 Matsushita Electric Ind Co Ltd Ｉｓｄｎ端末装置
US6519454B1 (en) * 1999-12-15 2003-02-11 Lucent Technologies Inc. Apparatus and method providing ubiquitous call transfer of an incoming call to a mobile subscriber unit
US7317787B2 (en) * 2000-11-21 2008-01-08 At&T Knowledge Ventures, L.P. Voice enhancing for advance intelligent network services
US6925082B2 (en) * 2001-02-15 2005-08-02 Lucent Technologies Inc. ATM packet access gateway
US7068598B1 (en) * 2001-02-15 2006-06-27 Lucent Technologies Inc. IP packet access gateway
US6950876B2 (en) * 2001-03-19 2005-09-27 Lucent Technologies Inc. Multiple-protocol home location register and method of use
WO2003001836A1 (en) * 2001-06-20 2003-01-03 Nokia Corporation System, device and method for providing call forwarding in dual subscription mode
EP2276218B1 (en) * 2003-02-19 2015-10-28 Nokia Technologies Oy Routing messages via an IMS system
US7898990B2 (en) * 2003-03-25 2011-03-01 Spyder Navigations L.L.C. Method, system and gateway device for enabling interworking between IP and CS networks
US7283506B2 (en) * 2003-10-13 2007-10-16 Nokia Corporation System and method for releasing sessions at network entities associated with the sessions
US7978683B2 (en) * 2004-04-14 2011-07-12 Alcatel-Lucent Usa Inc. Method of transferring call transition messages between network controllers of different radio technologies
EP1806008B1 (en) * 2004-10-06 2018-06-20 Telecom Italia S.p.A. Method, and related mobile communications system, for providing combinational network services
FR2879062A1 (fr) * 2004-12-06 2006-06-09 France Telecom Procede et systeme de transfert d'appels centralise
US7649862B2 (en) * 2005-05-19 2010-01-19 Alcatel-Lucent Usa Inc. Flexible through-connection process in a mobile switch center when multiple outgoing call legs involved
BRPI0520248A2 (pt) * 2005-05-31 2009-09-15 Ericsson Telefon Ab L M método de processamento de uma chamada telefÈnica, e, dispositivo de comutação
US7809125B2 (en) * 2005-09-01 2010-10-05 Avaya Inc. Method and apparatus for selection of special-purpose gateways
US20070195752A1 (en) * 2006-02-22 2007-08-23 Lucent Technologies Inc. System and method for handling call redirection and multi call destination failures
US8243715B2 (en) * 2006-05-15 2012-08-14 Oracle Israel Ltd. Delivering sip-based call services to circuit-switched terminals
US8180338B1 (en) * 2006-06-14 2012-05-15 Genband Us Llc Selective call anchoring in a multimedia subsystem
US8218528B2 (en) * 2006-07-06 2012-07-10 Cisco Technology, Inc. Gateway providing third party call control
US8600006B2 (en) * 2006-12-27 2013-12-03 Genband Us Llc Voice continuity among user terminals
US7668159B2 (en) * 2007-04-25 2010-02-23 Research In Motion Limited Methods and apparatus for obtaining variable call parameters suitable for use in originating a SIP call via a circuit-switched network from a user equipment device
US8249561B2 (en) * 2007-09-11 2012-08-21 Research In Motion Limited System and method for sharing a SIP communication service identifier
CN101420668B (zh) * 2007-10-25 2010-10-13 华为技术有限公司 一种实现呼叫转移的方法、系统和设备

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20050076531A (ko) * 2004-01-20 2005-07-26 엘지전자 주식회사 휴대단말기의 착신전환 설정장치 및 방법
CN1874379A (zh) * 2006-01-26 2006-12-06 华为技术有限公司 移动通信系统中的呼叫转移方法

Non-Patent Citations (1)

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

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102036201A (zh) * 2009-09-28 2011-04-27 中兴通讯股份有限公司 来电提示方法及装置

Also Published As

Publication number Publication date
EP2207336A1 (en) 2010-07-14
CN101420669A (zh) 2009-04-29
CN101420669B (zh) 2010-08-25
US20100202447A1 (en) 2010-08-12
JP5174178B2 (ja) 2013-04-03
JP2011501583A (ja) 2011-01-06
KR20100061855A (ko) 2010-06-09
ES2425145T3 (es) 2013-10-11
EP2207336A4 (en) 2010-12-22
KR101078676B1 (ko) 2011-11-01
EP2207336B1 (en) 2013-06-05

Similar Documents

Publication Publication Date Title
WO2009056059A1 (fr) Procédé, système et dispositif de renvoi automatique d'appel
EP1920572B1 (en) Multimedia subsystem service control for circuit-switched subsystem calls
US8155084B2 (en) User equipment, call continuity application server, and network handover method
US8325681B2 (en) Call transfer method, system and device
JP5437435B2 (ja) 呼制御方法、回線交換ドメインアダプタ、および端末装置
US20090052438A1 (en) Method, system and device for processing supplementary services
WO2009039688A1 (en) Late call forwarding method in ip multimedia core network subsystem centralized service
WO2009149635A1 (zh) 一种实现显式呼叫转移的方法、设备及移动通信系统
WO2008151481A1 (fr) Procédé pour commander de manière centralisée le service d'implémentation d'appel de terminal dans un sous-système de réseau central multimédia ip
CN101267324B (zh) Ip多媒体子系统业务提供方法和系统
ES2397967T3 (es) Método para realizar la retención de una llamada
US8363645B2 (en) Method for realizing user decision user busy forwarding
WO2011107012A1 (zh) 一种业务控制方法和装置
CN101370176B (zh) 多媒体会话在不同接入网络间转移的方法及装置
WO2009092245A1 (zh) 多媒体会话连续性业务的起呼方法
WO2008151487A1 (fr) Procédé de mise en place d'une fin d'appel dans un service de contrôle centralisé ims

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

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2010530257

Country of ref document: JP

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2008846040

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 20107010223

Country of ref document: KR

Kind code of ref document: A