WO2014183703A1 - 呼叫前转/偏转业务的通知/触发方法、装置 - Google Patents
呼叫前转/偏转业务的通知/触发方法、装置 Download PDFInfo
- Publication number
- WO2014183703A1 WO2014183703A1 PCT/CN2014/078460 CN2014078460W WO2014183703A1 WO 2014183703 A1 WO2014183703 A1 WO 2014183703A1 CN 2014078460 W CN2014078460 W CN 2014078460W WO 2014183703 A1 WO2014183703 A1 WO 2014183703A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- message
- called
- service
- call
- busy state
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 62
- 238000010586 diagram Methods 0.000 description 17
- 230000008569 process Effects 0.000 description 11
- 238000004590 computer program Methods 0.000 description 7
- 230000006870 function Effects 0.000 description 5
- 238000012545 processing Methods 0.000 description 5
- 238000004891 communication Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000006855 networking Effects 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- 230000011664 signaling Effects 0.000 description 2
- 230000001960 triggered effect Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 239000013589 supplement Substances 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/54—Presence management, e.g. monitoring or registration for receipt of user log-on information, or the connection status of the users
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/16—Communication-related supplementary services, e.g. call-transfer or call-hold
-
- 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
Definitions
- the present invention relates to the field of communications, and in particular to a notification/trigger method and apparatus for call forwarding/deflection services. Background technique
- the IP Multimedia Subsystem (IMS) network is a multimedia service form developed by the 3GPP, 3rd Generation Partnership Project (3GPP) to adapt to the evolving telecommunications technology and market needs. It is built on top of an IP network and uses IP bearers as a bearer for its control signaling and media transport.
- the IMS uses the Session Initiation Protocol (SIP) as the control signaling, which has the characteristics of separate bearer control and access independence. It has the ability to provide unified multimedia services for users under different networks. It is the evolution direction of the current telecommunication network.
- SIP Session Initiation Protocol
- Figure 1 is a structure of an IMS network, where
- the IMS network can provide the user with a busy call forwarding service (CFB).
- CFB busy call forwarding service
- the IMS network can also provide a user with a call deflection service (CD, Communication Deflection).
- CD Call deflection service
- the called UE sends a 302 Moved Temporarily message, and carries the address of the call deflection party through the Contact header field to supplement the AS of the service. After that, the call is forwarded to the deflecting party.
- the UE under the IMS network may cut the ongoing conversation due to network coverage.
- Switch to the Circuit Switch (CS) network to provide switching services by the Mobile Switch Center Server (MSC Server) under the CS network.
- This process is called SRVCC (Signal Radio Voice Call Continuity) handover.
- Figure 2 is a network structure diagram for performing such switching.
- the UE A 201 is the UE that has the handover;
- the MSC Server 202 is the exchange server where the UE A 201 is switched to the CS network, the server provides the handover service for the UE A 201, and provides the call control function after the handover;
- mobility management An entity (MME, Mobility Management Entity) 203 is a management network element in which the UE A 201 is in a packet switched domain.
- MME Mobility Management Entity
- the UE A 201 resides under the MME 203 before the handover, and is connected to the Serving-Call Session Control Function (S-CSCF) 204 through the IP connection provided by the MME 203.
- S-CSCF Serving-Call Session Control Function
- the MME 203 sends a handover request to the MSC Server 202, and interacts with the MSC Server 202 to complete the handover procedure
- the S-CSCF 204 is the S-CSCF that provides the service for the UE A 201
- the service centralized and continuous application server (SCC AS, Service Centralization and Continuity Application Server) 205 is an AS that provides call continuity services in an IMS network.
- SCC AS Service Centralization and Continuity Application Server
- the SCC AS 205 is responsible for implementing communication between the switched circuit domain session branch and the far end of the call.
- the SCC AS 205 may be combined with a supplementary service AS that provides service logic for the UE, or may be separately configured; the UE B 206 is a remote end that talks with the UE A 201.
- FIG. 3 is a flow of a SRVCC handover performed by a UE in a called ringing state, and includes the following steps:
- the handover decision is made between the UEA and the MME in the ringing, and it is decided to switch to the CS network.
- S302 The MME sends a handover request message to the MSC Server.
- S304 The MME sends a handover command to the UE A, and the UE A starts an access process to the circuit domain.
- S305 At the same time, the MSC Server sends an invite (INVITE) message to the SCC AS, requesting to establish a media connection between the MSC Server and the UE B;
- SIP is generally used between the MSC Server and the SCC AS.
- the message between the SCC AS and the UE B needs to be forwarded by the S-CSCF, which is simplified, and the forwarding process is omitted here.
- the 200 OK message carries the media information of the UE B.
- S308 The SCC AS returns a message 183 to the MSC Server, and then sends an INFO message to the MSC Server.
- the INFO message informs the MSC Server that the current call is in the called ringing state.
- the UE A After completing the circuit domain access, the UE A sends a handover complete message to the MSC Server. Here, after the UE A sends the handover complete message, it indicates that the handover is completed, and the UE A is in the called ringing state in the circuit domain.
- S310 UE A answers the call and sends a connection (CONNECT) message to the MSC Server.
- the MSC Server sends an INFO message to the SCC AS, and notifies the SCC AS that the call has been answered.
- S312 The SCC AS returns a 200 OK message to the MSC Server, completing a session establishment process with the MSC Server;
- the MSC Server sends a CONNECT ACK to the UE A, and the call enters a call state.
- a problem in the related art is that the UE after handover can initiate a CFB or CD service by sending a disconnected (DISCONNECT) message to the MSC in the called ringing state of the circuit domain, and the MSC at this time
- DISCONNECT disconnected
- This limitation causes the switched UE to fail to implement CD and CFB services.
- no effective solution has been proposed yet. Summary of the invention
- an embodiment of the present invention provides a notification/trigger method and apparatus for a call forwarding/deflection service.
- a method for notifying a call forwarding/deflection service including: when a call forwarding service is required, the MSC receives a message that the called UE is carrying the called UE is busy. a first message of the information; sending, to the SCC AS, a second message carrying the information that the called UE is in a busy state, notifying the supplementary service AS to trigger the call forwarding service; or
- the MSC receives the third message that is sent by the called UE and carries the call deflection number.
- the fourth message carrying the call deflection number is sent to the SCC AS, and the supplementary service AS is notified to trigger the call deflection service.
- a method for triggering a call forwarding/deflection service including: when a call forwarding service is required, the SCC AS receives a message that is sent by the MSC and carries the called UE in a busy state. Sending a message to the supplementary service AS indicating that the called UE is in a busy state, notifying the supplementary service AS to trigger the call forwarding service; or, when the call deflection service is required, the SCC AS receives the carried call sent by the MSC A third message of the deflection number; transmitting a fourth message carrying the call deflection number to the supplementary service AS, informing the supplementary service AS to trigger the call deflection service.
- a notification device for a call forwarding/deflection service including: a first receiving module and a first sending module; wherein, the first receiving module is configured to perform call forwarding Receiving, by the called UE, the first message carrying the information that the called UE is in the busy state; the first sending module is configured to send, to the SCC AS, the second information that carries the called UE in the busy state information a message informing the supplementary service AS to trigger the call forwarding service; or
- the device includes: a second receiving module and a second sending module; wherein, the second receiving module is configured to receive the third message carrying the call deflection number when the called UE needs to perform the call deflection service; And sending, to the SCC AS, a fourth message carrying the call deflection number, informing the supplementary service AS to trigger the call deflection service.
- a triggering device for a call forwarding/deflection service including: a first receiving module and a first triggering module; wherein, the first receiving module is configured to perform call forwarding And the first triggering module is configured to send, to the supplementary service AS, a second message indicating that the called UE is in a busy state, to notify the supplementary service, when the service is received, and the first message is sent by the MSC to the supplementary service AS.
- the AS triggers the call forwarding service; or the device includes: a second receiving module and a second triggering module, where the second receiving module is configured to perform the call deflection service, and the receiving MSC sends the first part carrying the call deflection number
- the third triggering module is configured to send a fourth message carrying the call deflection number to the supplementary service AS, and notify the supplementary service AS to trigger the call deflection service.
- a computer storage medium comprising a set of instructions, when executed, causing at least one processor to perform a call forwarding/deflection service as described above
- the notification method or the above-described method of triggering the call forwarding/deflection service is provided.
- the SCC AS sends a message carrying the called UE to the busy status information to the supplementary service AS, or sends a message carrying the call deflection number to the supplementary service AS through the SCC AS, so as to be triggered on the supplementary service AS.
- the service logic of the foregoing service solves the problem that the UE cannot implement CFB and CD services after the SRVCC handover in the prior art.
- FIG. 1 is a structural diagram of an IMS network according to the related art
- FIG. 2 is a network structure diagram of SRVCC handover according to the related art
- FIG. 4 is a flowchart of a method for notifying a call forwarding service according to an embodiment of the present invention
- FIG. 5 is a flowchart of a method for notifying a call deflection service according to an embodiment of the present invention
- FIG. 6 is a SCC AS and an embodiment according to the present invention
- FIG. 7 is a flowchart of triggering an IMS forwarding service after an SRVCC handover occurs when an SCC AS and an AS are jointly set up according to Embodiment 2 of the present invention
- FIG. 8 is a structural block diagram of a notification device for a call forwarding service according to an embodiment of the present invention
- FIG. 9 is a structural block diagram of a triggering device for a call forwarding service according to an embodiment of the present invention
- FIG. 10 is a call deflection service according to an embodiment of the present invention.
- FIG. 11 is a flowchart of a method for triggering a call deflection service according to an embodiment of the present invention
- FIG. 12 is a diagram showing triggering an IMS deflection service after an SRVCC handover occurs when an SCC AS and an AS are separately established according to Embodiment 3 of the present invention; Flow chart
- FIG. 13 is a flowchart of triggering an IMS deflection service after an SRVCC handover occurs when a SCC AS and an AS are jointly set up according to Embodiment 4 of the present invention
- Figure 14 is a block diagram showing the structure of a notification device for a call deflection service according to an embodiment of the present invention
- Figure 15 is a block diagram showing the structure of a triggering device for a call deflection service according to an embodiment of the present invention.
- the embodiment of the invention provides an implementation scheme of a call forwarding service and a call deflection service.
- the solution includes two aspects of a notification method and a trigger method.
- the call forwarding service scheme and the call deflection service according to the embodiment of the present invention are separately described below.
- a method for notifying a call forwarding service includes the following steps:
- Step S402 the MSC receives the first message that is sent by the called UE and carries the information that the called UE is busy.
- the MSC refers to an MSC Server.
- Step S404 The MSC sends a second message carrying the information that the called UE is in the busy state to the SCC AS, and notifies the supplementary service AS to trigger the call forwarding service.
- the MSC receives the first message that is sent by the called UE and carries the information that the called UE is in the busy state, and carries the information that the called UE is busy in the second message and sends the information to the SCC AS to notify the supplementary service.
- the AS triggers the call forwarding service, so that the supplementary service AS triggers the call forwarding service according to the information that the called UE is busy.
- a method for triggering a call forwarding service is further provided. As shown in FIG. 5, the method includes the following steps:
- Step S502 The SCC AS receives a first message that is sent by the MSC and carries the information that the called UE is busy.
- Step S504 Send a second message indicating that the called UE is in a busy state to the supplementary service AS, and notify the supplementary service AS to trigger the call forwarding service.
- the SCC AS receives the first message that is sent by the MSC and carries the information that the called UE is in the busy state, and carries the information that the called UE is busy in the second message and sends the information to the supplementary service AS to notify the supplementary service.
- the AS triggers the call forwarding service, so that the supplementary service AS triggers the call forwarding service according to the information that the called UE is busy.
- FIG. 6 is a flowchart of triggering an IMS call forwarding service after an SRVCC handover occurs when the SCC AS and the supplementary service AS are separately established. Specific steps are as follows:
- S601-S609 is consistent with S301-S309 in FIG. 3;
- S610 UE A is in a busy state, and sends a DISCONNECT message to the MSC Server, where the user is busy;
- the MSC Server sends a goodbye (BYE) or cancels the Cancel message to the SCC AS.
- BYE or Cancel message carries a Reason (Reason) header field, and the type is a SIP status code, and the value is 486.
- the BYE or Cancel message can also carry textual information in XML format to describe that the user is busy.
- the message between the SCC AS and the supplementary service AS is forwarded by the S-CSCF.
- the AS After receiving the 486 Busy Here message, the AS triggers the forwarded service logic, and sends a call 181 call forward (call is being forwarded) to the UE B to notify the UE B that the current call is forwarded;
- the supplementary service AS sends an INVITE message to the UE C to perform forwarding to the UE C.
- Figure 7 shows the process of triggering the IMS forwarding service after the SRVCC handover occurs when the SCC AS and the supplementary service AS are combined. Specific steps are as follows:
- S710 UE A is in a busy state, and sends a DISCONNECT message to the MSC Server, where the reason is that the user is busy;
- the MSC Server sends a BYE and/or a Cancel message to the SCC AS.
- the BYE and/or Cancel message carries a Reason header field of type SIP status code with a value of 486.
- BYE or Cancel messages can also carry textual information in XML format to describe that the user is busy.
- the supplementary service AS After receiving the SCC AS, the supplementary service AS triggers the forwarded service logic, and sends a 181 call is being forwarded to the UE B, and notifies the UE B that the current call is forwarded;
- the SCC AS sends an INVITE message to the UE C to perform forwarding to the UE C.
- the MSC Server that sends the SRVCC handover sends a BYE/Cancel message, carries the specified header field or text format description, and the SCC AS that receives the message is converted into the 486 message used by the CFB, so that the service AS can
- the service logic that triggers the foregoing service solves the problem that the UE cannot implement the CFB service after the SRVCC handover in the prior art.
- FIG. 8 is a schematic structural diagram of a device according to an embodiment of the present invention. As shown in FIG. 8, the device includes: a first receiving module 810 and a first sending module 820;
- the first receiving module 810 is configured to receive a first message that is sent by the called UE and that carries the busy status information of the called UE.
- the first sending module 820 is configured to send, to the SCC AS, a second message carrying the information that the called UE is in the busy state, and notify the supplementary service application server AS to trigger the call forwarding service.
- the first receiving module 810 can be implemented by a receiver in the notification device of the call forwarding service, and the first transmitting module 820 can be implemented by a transmitter in the notification device of the call forwarding service.
- the embodiment of the present invention further provides a triggering device for a call forwarding service, where the device can be used to implement the foregoing triggering method.
- FIG. 9 is a schematic structural diagram of an apparatus according to an embodiment of the present invention. As shown in FIG. 9, the method includes: a first receiving module 910 and a first triggering module 920.
- the first receiving module 910 is configured to receive the carried by the MSC.
- the first triggering module 920 is configured to send a second message indicating that the called UE is in a busy state to the supplementary service AS, and notify the supplementary service AS to trigger the call forwarding service.
- the first receiving module 910 can be implemented by a receiver in the triggering device of the call forwarding service
- the first triggering module 920 can be implemented by a transmitter in the triggering device of the call forwarding service.
- the embodiment of the present invention further provides a notification method for a call deflection service. As shown in FIG. 10, the method includes the following steps:
- Step S1002 The MSC receives the third cancellation carried by the called UE and carries the call deflection number, where the MSC refers to the MSC Server.
- Step S1004 Send a fourth message carrying the call deflection number to the SCC AS, and notify the supplementary service AS to trigger the call deflection service.
- the MSC receives the third message carrying the call deflection number sent by the called UE, and carries the information carrying the call deflection number sent by the called UE in the fourth message and sends the message to the SCC AS to notify the supplementary.
- the service AS triggers the call deflection service, so that the supplementary service AS triggers the call deflection service based on the call deflection number information.
- a triggering method for the call deflection service is correspondingly provided. As shown in FIG. 11, the method includes the following steps:
- Step S1102 The SCC AS receives the third cancellation carried by the MSC and carries the call deflection number.
- Step S1104 Send a fourth message carrying the call deflection number to the supplementary service AS, and notify the supplementary service AS to trigger the call deflection service.
- the SCC AS receives the third message that is sent by the MSC and carries the call forwarding number, and carries the called UE with the call deflection number in the fourth message and sends the message to the supplementary service AS to notify the supplementary service AS to trigger the call deflection service. So that the supplementary service AS triggers the call deflection service based on the call deflection number information.
- Figure 12 shows the flow of triggering the IMS call deflection service after the SRVCC handover occurs when the SCC AS and the supplementary service AS are set up separately.
- the specific steps are as follows (step S1202 to step S1204).
- S1201-S1209 are identical to steps 301-309 in FIG. 3;
- S1210 UE A triggers a call deflection service, and sends a DISCONNECT message to the MSC Server, where the call deflection number is carried;
- the MSC Server sends a BYE and/or Cancel message to the SCC AS, where the XML carrying the call deflection service request and the call deflection number is carried;
- the BYE and Cancel messages also carry the call deflection number.
- the SCC AS After receiving the SCC, the SCC AS converts to a 302 message, carries the call deflection number, and sends the call to the supplementary service AS;
- the 302 message is a 302 MOVED TEMPORARILY message.
- Figure 13 shows the process of triggering the IMS call deflection service after the SRVCC switchover occurs when the SCC AS and the supplementary service AS are combined. The specific steps are as follows:
- S1310 UE A triggers a call deflection service, and sends a DISCONNECT message to the MSC.
- the MSC Server sends a BYE and/or Cancel message to the SCC AS, where the XML carrying the call deflection service request and the call deflection number is carried;
- the BYE and Cancel messages also carry the call deflection number.
- the MSC Server that sends the SRVCC handover sends a BYE/Cancel message, which carries a text format description, and the SCC AS that receives the message is converted into a 302 message used by the CD service, so that the service can be triggered on the service AS.
- the business logic solves the problem that the UE cannot implement the CD service after the SRVCC handover in the prior art.
- An embodiment of the present invention further provides a notification device for a call deflection service, where the device is located
- FIG. 14 is a schematic structural diagram of a device according to an embodiment of the present invention. As shown in FIG. 14, the method includes: a second receiving module 1410 and a second sending module 1420;
- the second receiving module 1410 is configured to receive, by the called UE, a third message that carries the call deflection number;
- the second sending module 1420 is configured to send a fourth message carrying the call deflection number to the SCC AS, to notify the supplementary service AS to trigger the call deflection service.
- the second receiving module 1410 can be implemented by a receiver in the notification device of the call deflection service, and the second transmitting module 1420 can be implemented by a transmitter in the notification device of the call deflection service.
- FIG. 15 is a schematic structural diagram of a device according to an embodiment of the present invention. As shown in FIG. 15, the device includes: a second receiving module 1510 and a second triggering module 1520;
- the second receiving module 1510 is configured to receive, by the MSC, a third message carrying a call deflection number
- the second triggering module 1520 is configured to send a fourth message carrying the call deflection number to the supplementary service AS, and notify the supplementary service AS to trigger the call deflection service.
- the second receiving module 1510 can be implemented by a receiver in the triggering device of the call deflection service, and the second triggering module 1520 can be implemented by a transmitter in the triggering device of the call deflection service.
- notification/trigger device of the call forwarding/deflection service described in the device embodiment corresponds to the foregoing method embodiment, and the specific implementation process has been described in detail in the method embodiment, and is no longer described herein. Narration.
- the embodiment of the present invention optimizes the busy call forwarding and call deflection process after the SRVCC handover in the case of the modification and the least impact on the existing system, and carries the service information of the user in the BYE/Canel message on the AS. Trigger the user's busy transfer and call deflection business logic to meet the user's contracting requirements.
- the problem that the UE cannot implement the call forwarding CFB and the call deflection CD service after the SRVCC handover in the prior art is solved.
- the present invention can take the form of a hardware embodiment, a software embodiment, or a combination of software and hardware aspects.
- the invention can take the form of a computer program product embodied on one or more computer usable storage media (including but not limited to disk storage and optical storage, etc.) in which computer usable program code is embodied.
- the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
- the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
- These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
- the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.
Landscapes
- Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
本发明公开了一种呼叫前转/偏转业务的通知/触发方法,其中通知方法包括:移动交换中心MSC接收被叫用户设备UE发送的携带有所述被叫UE处于忙状态信息的第一消息;向业务集中及连续应用服务器SCC AS发送携带有所述被叫UE处于忙状态信息的第二消息,通知补充业务应用服务器AS触发呼叫前转业务;或者,MSC接收被叫UE发送的携带有呼叫偏转号码的第三消息;向SCC AS发送携带有所述呼叫偏转号码的第四消息,通知所述补充业务AS触发呼叫偏转业务。本发明还提供一种呼叫前转/偏转业务的通知/触发装置。
Description
呼叫前转 /偏转业务的通知 /触发方法、 装置 技术领域
本发明涉及通信领域, 具体而言, 涉及一种呼叫前转 /偏转业务的通知 / 触发方法、 装置。 背景技术
IP多媒体子系统( IMS , IP Multimedia Subsystem ) 网络是第三代移动 通信伙伴计划 ( 3GPP, 3rd Generation Partnership Project )组织为适应不断 发展的电信技术和市场需求, 所发展出来的一种多媒体业务形式, 它构建 在 IP网络之上, 使用 IP承载作为其控制信令和媒体传输的承载通道。 IMS 使用会话初始化协议 ( SIP, Session Initiation Protocol )作为控制信令, 具 备承载控制分离, 接入无关等特点, 具备为不同网络下的用户提供统一多 媒体业务的能力, 是目前电信网络的演化方向。 图 1是 IMS网络的结构, 其中,
IMS 网络可以为用户提供遇忙呼叫前转业务( CFB , Communication Forwarding Busy ), 当用户接收新呼叫时, 如果用户返回当前处于忙状态, 用户设备 ( UE, User Equipment )返回 486消息, 处理补充业务的应用服务 器( AS , Application Server )收到后,将按照用户签约,发送邀请 ( INVITE ) 消息到前转方用户。
IMS 网络还可以为用户提供呼叫偏转业务 ( CD , Communication Deflection ), 当用户接收新呼叫时, 被叫 UE发送 302 Moved Temporarily 消息,并通过 Contact头域携带呼叫偏转方的地址,补充业务的 AS收到后, 将呼叫转发到偏转方。
在 IMS网络下的 UE, 由于网络覆盖的原因,可能将正在进行的对话切
换到电路交换(CS, Circuit Switch ) 网络, 由 CS网络下的移动交换中心服 务器( MSC Server, Mobile Switch Center Server )提供交换服务。 这一过程 称为单频语音连续性(SRVCC, Signal Radio Voice Call Continuity )切换。 图 2是进行这种切换的网络结构图。 其中, UE A 201 是发生切换的 UE; MSC Server 202是 UE A 201切换到 CS网络后所在的交换服务器, 该服务 器为 UE A 201提供切换服务, 并在切换后提供呼叫控制功能; 移动性管理 实体( MME, Mobility Management Entity ) 203是 UE A 201在分组交换域 的管理网元。 UE A 201在切换前, 驻留在 MME 203下, 并通过 MME 203 提供的 IP连接,连接到服务呼叫会话控制功能( S-CSCF, Serving-Call Session Control Function ) 204。 当需要切换到 CS网络时, MME 203发送切换请求 到 MSC Server 202, 并和 MSC Server 202交互完成切换流程; S-CSCF 204 是为 UE A 201提供服务的 S-CSCF; 业务集中及连续应用服务器( SCC AS, Service Centralization and Continuity Application Server ) 205是 IMS网络中 提供呼叫连续性服务的 AS。在切换过程中, SCC AS 205负责实现切换后的 电路域会话分支和呼叫远端之间连通。 SCC AS 205可以和为 UE提供业务 逻辑的补充业务 AS合设, 也可以分开设置; UE B 206是和 UE A 201对话 的远端。
图 3是处于被叫振铃状态的 UE进行 SRVCC切换的流程, 包括如下步 骤:
S301: UE B呼叫 UE A, 通话进入振铃状态;
这里, 振铃中的 UEA和 MME之间进行切换决策, 决定切换到 CS网 络。
S302: MME发送切换请求消息到 MSC Server;
S303: MSC Server在进行切换准备后, 返回切换应答到 MME;
S304: MME发送切换命令到 UE A, UE A开始到电路域的接入过程;
S305: 同时, MSC Server发送邀请(INVITE ) 消息到 SCC AS, 请求 建立 MSC Server到 UE B之间的媒体连接;
这里, MSC Server和 SCC AS之间, 一般采用 SIP。
S306: SCC AS收到后, 发送更新 ( Update ) 消息到 UE B;
这里, SCC AS和 UE B之间的消息需要经过 S-CSCF的转发, 简化起 见, 这里将转发过程省略。
S307: UE B返回 200OK消息;
这里, 200OK消息中携带 UE B的媒体信息。
S308: SCC AS返回 183消息到 MSC Server, 然后发送 INFO消息到 MSC Server;
这里 , INFO消息通知 MSC Server当前呼叫处于被叫振铃状态。
S309: UE A在电路域接入完成后, 发送切换完成消息到 MSC Server; 这里, UE A发送切换完成消息之后, 表明切换完成, UE A处于在电 路域的被叫振铃状态。
S310: UE A接听呼叫, 发送连接( CONNECT ) 消息到 MSC Server;
S311 : MSC Server发送 INFO消息到 SCC AS, 通知 SCC AS呼叫已经 应答;
S312: SCC AS返回 200OK消息到 MSC Server, 完成和 MSC Server 之间的对话建立过程;
S313: MSC Server发送 CONNECT ACK到 UE A ,呼叫进入通话状态。 相关技术中存在的问题是, 切换后的 UE在电路域的被叫振铃状态下, 可以通过发送断开连接( DISCONNECT )消息到 MSC, 发起 CFB或者 CD 业务, 而此时的 MSC, 因为在和 SCC AS之间的对话中, 是客户端一方, 不能按照 IMS的 CFB和 CD业务要求发送 486和 302消息。 这一限制导致 切换后的 UE无法实现 CD和 CFB业务。
针对上述问题, 目前尚未提出有效的解决方案。 发明内容
为解决现有存在的技术问题, 本发明实施例提供了一种呼叫前转 /偏转 业务的通知 /触发方法、 装置。
根据本发明实施例的一个方面, 提供了一种呼叫前转 /偏转业务的通知 方法, 包括: 需要进行呼叫前转业务时, MSC接收被叫 UE发送的携带有 所述被叫 UE处于忙状态信息的第一消息; 向 SCC AS 发送携带有所述被 叫 UE处于忙状态信息的第二消息, 通知补充业务 AS触发呼叫前转业务; 或者,
需要进行呼叫偏转业务时, MSC接收被叫 UE发送的携带有呼叫偏转 号码的第三消息; 向 SCC AS发送携带有所述呼叫偏转号码的第四消息, 通知补充业务 AS触发呼叫偏转业务。
根据本发明实施例的一个方面, 提供了一种呼叫前转 /偏转业务的触发 方法, 包括: 需要进行呼叫前转业务时, SCC AS接收 MSC发送的携带有 被叫 UE处于忙状态信息的第一消息; 向补充业务 AS发送指示所述被叫 UE处于忙状态的第二消息, 通知补充业务 AS触发呼叫前转业务; 或者, 需要进行呼叫偏转业务时, SCC AS接收 MSC发送的携带有呼叫偏转 号码的第三消息; 向补充业务 AS发送携带有呼叫偏转号码的第四消息,通 知补充业务 AS触发呼叫偏转业务。
根据本发明实施例的另一方面, 提供了一种呼叫前转 /偏转业务的通知 装置, 包括: 第一接收模块和第一发送模块; 其中, 第一接收模块, 配置 为需要进行呼叫前转业务时,接收被叫 UE发送的携带有所述被叫 UE处于 忙状态信息的第一消息; 第一发送模块, 配置为向 SCC AS 发送携带有所 述被叫 UE处于忙状态信息的第二消息,通知补充业务 AS触发呼叫前转业 务; 或者,
所述装置包括: 第二接收模块和第二发送模块; 其中, 第二接收模块, 配置为需要进行呼叫偏转业务时 ,接收被叫 UE发送携带有呼叫偏转号码的 第三消息; 第二发送模块, 配置为向 SCC AS 发送携带有所述呼叫偏转号 码的第四消息, 通知补充业务 AS触发呼叫偏转业务。
根据本发明实施例的另一方面, 提供了一种呼叫前转 /偏转业务的触发 装置, 包括: 第一接收模块和第一触发模块; 其中, 第一接收模块, 配置 为需要进行呼叫前转业务时, 接收 MSC发送的携带有被叫 UE处于忙状态 信息的第一消息; 第一触发模块, 配置为向补充业务 AS发送指示所述被叫 UE处于忙状态的第二消息, 通知补充业务 AS触发呼叫前转业务; 或者, 所述装置包括: 第二接收模块和第二触发模块, 其中, 第二接收模块, 配置为需要进行呼叫偏转业务时,接收 MSC发送携带有呼叫偏转号码的第 三消息; 第二触发模块, 配置为向补充业务 AS发送携带有呼叫偏转号码的 第四消息, 通知补充业务 AS触发呼叫偏转业务。
根据本发明实施例的又一方面, 提供了一种计算机存储介质, 所述计 算机存储介质包括一组指令, 当执行所述指令时, 引起至少一个处理器执 行如上述的呼叫前转 /偏转业务的通知方法或上述的呼叫前转 /偏转业务的 触发方法。
通过本发明实施例, 通过 SCC AS向补充业务 AS发送携带被叫 UE处 于忙状态信息的消息, 或者, 通过 SCC AS向补充业务 AS发送携带呼叫偏 转号码的消息,从而在补充业务 AS上能够触发上述业务的业务逻辑,解决 了现有技术在 SRVCC切换之后的 UE无法实现 CFB和 CD业务问题。 附图说明
此处所说明的附图用来提供对本发明的进一步理解, 构成本申请的一 部分, 本发明的示意性实施例及其说明用于解释本发明, 并不构成对本发 明的不当限定。 在附图中:
图 1是根据相关技术的 IMS网络结构图;
图 2是根据相关技术的 SRVCC切换的网络结构图;
图 3是根据相关技术的 SRVCC切换流程图;
图 4是根据本发明实施例的呼叫前转业务的通知方法流程图; 图 5是根据本发明实施例的呼叫偏转业务的通知方法流程图; 图 6是是根据本发明实施例一 SCC AS和 AS分开设立时,发生 SRVCC 切换后触发 IMS前转业务的流程图;
图 7是根据本发明实施例二的 SCC AS和 AS合并设立时,发生 SRVCC 切换后触发 IMS前转业务的流程图;
图 8是根据本发明实施例的呼叫前转业务的通知装置结构框图; 图 9是根据本发明实施例的呼叫前转业务的触发装置结构框图; 图 10是根据本发明实施例的呼叫偏转业务的通知方法流程图; 图 11是根据本发明实施例的呼叫偏转业务的触发方法流程图; 图 12是根据本发明实施例三中 SCC AS和 AS分开设立时,发生 SRVCC 切换后触发 IMS偏转业务的流程图;
图 13是根据本发明实施例四中 SCC AS和 AS合并设立时,发生 SRVCC 切换后触发 IMS偏转业务的流程图;
图 14是根据本发明实施例的呼叫偏转业务的通知装置结构框图; 图 15是根据本发明实施例的呼叫偏转业务的触发装置结构框图。 具体实施方式
需要说明的是, 在不沖突的情况下, 本申请中的实施例及实施例中的 特征可以相互组合。 下面将参考附图并结合实施例来详细说明本发明。
本发明实施例提供了一种呼叫前转业务和呼叫偏转业务的实现方案。 在本发明实施例中, 该方案均包括通知方法和触发方法两个方面。 下面分 别对本发明实施例的呼叫前转业务方案和呼叫偏转业务进行描述。
一、 呼叫前转业务
作为本发明实施例的一个方面, 提供了一种呼叫前转业务的通知方法, 如图 4所示, 包括如下的步骤:
步骤 S402, MSC接收被叫 UE发送的携带有被叫 UE处于忙状态信息 的第一消息;
这里, 所述 MSC是指 MSC Server。
步骤 S404, MSC向 SCC AS发送携带有被叫 UE处于忙状态信息的第 二消息, 通知补充业务 AS触发呼叫前转业务。
通过本发明实施例, MSC接收被叫 UE发送的携带有被叫 UE处于忙 状态信息的第一消息,将被叫 UE处于忙状态的信息携带在第二消息中发送 至 SCC AS, 通知补充业务 AS触发呼叫前转业务, 使得补充业务 AS根据 被叫 UE处于忙状态信息来触发呼叫前转业务。
作为本发明实施例的另一个方面, 对应的还提供了一种呼叫前转业务 的触发方法, 如图 5所示, 包括如下的步骤:
步骤 S502, SCC AS接收 MSC发送的携带有被叫 UE处于忙状态信息 的第一消息;
步骤 S504, 向补充业务 AS发送指示所述被叫 UE处于忙状态的第二 消息, 通知补充业务 AS触发呼叫前转业务。
通过本发明实施例, SCC AS接收 MSC发送的携带有被叫 UE处于忙 状态信息的第一消息,将被叫 UE处于忙状态的信息携带在第二消息中发送 至补充业务 AS, 通知补充业务 AS触发呼叫前转业务, 使得补充业务 AS 根据被叫 UE处于忙状态信息来触发呼叫前转业务。
为了使本发明的技术方案和实现方法更加清楚, 下面将结合优选的实 施例对其实现过程进行详细描述。
实施例一
图 6是 SCC AS和补充业务 AS分开设立时, 发生 SRVCC切换后触发 IMS呼叫前转业务的流程。 具体步骤如下:
S601-S609和图 3中的 S301-S309一致;
S610: UE A处于忙状态, 发送 DISCONNECT消息到 MSC Server, 其 中原因为用户忙;
S611 : MSC Server发送再见(BYE )或者取消 Cancel消息到 SCC AS; 这里, BYE或者 Cancel消息中携带原因 (Reason ) 头域, 类型为 SIP 状态码, 数值为 486。 作为一种替代方法, BYE或者 Cancel消息中也可以 携带 XML格式的文本信息, 描述用户处于忙状态。
S612: SCC AS收到后, 转换为 486这里忙(Busy Here ) 消息发送到 补充业务 AS;
这里, 按照 IMS网络组网要求, SCC AS和补充业务 AS之间的消息, 经过 S-CSCF转发。
S613: 补充业务 AS收到 486 Busy Here消息后,触发前转的业务逻辑, 发送 181呼叫前转( call is being forwarded )到 UE B , 通知 UE B当前呼叫 发生前转;
S614: 同时, 补充业务 AS发送 INVITE消息到 UE C, 进行到 UE C 的前转。
实施例二
图 7是 SCC AS和补充业务 AS合设时, 发生 SRVCC切换后触发 IMS 前转业务的流程。 具体步骤如下:
S701-S709和图 3中的步骤 301-309—致;
S710: UE A处于忙状态, 发送 DISCONNECT消息到 MSC Server, 其 中原因为用户忙;
S711: MSC Server发送 BYE和 /或 Cancel消息到 SCC AS;
这里, BYE和 /或 Cancel消息中携带 Reason头域, 类型为 SIP状态码, 数值为 486。作为一种替代方法, BYE或者 Cancel消息中也可以携带 XML 格式的文本信息, 描述用户处于忙状态。
S712: SCC AS收到后,补充业务 AS触发前转的业务逻辑,发送 181 call is being forwarded到 UE B , 通知 UE B当前呼叫发生前转;
S713: 同时, SCC AS发送 INVITE消息到 UE C,进行到 UE C的前转。 通过本发明上述实施例, 采用在 SRVCC 切换的 MSC Server发送 BYE/Cancel消息中,携带指定头域或者文本格式描述,收到消息的 SCC AS 转换成 CFB所使用 486消息, 从而在业务 AS上能够触发上述业务的业务 逻辑, 解决了现有技术在 SRVCC切换之后的 UE无法实现 CFB业务的问 题。
需要说明的是, 在附图的流程图示出的步骤可以在诸如一组计算机可 执行指令的计算机系统中执行, 并且, 虽然在流程图中示出了逻辑顺序, 但是在某些情况下, 可以以不同于此处的顺序执行所示出或描述的步骤。
本发明实施例还提供了一种呼叫前转业务的通知装置, 该装置位于 MSC中, 该装置可以用于实现上述通知方法。 图 8是根据本发明实施例的 装置结构示意图, 如图 8所示, 该装置包括: 第一接收模块 810和第一发 送模块 820; 其中,
第一接收模块 810, 配置为接收被叫 UE发送的携带有所述被叫 UE处 于忙状态信息的第一消息;
第一发送模块 820,配置为向 SCC AS 发送携带有所述被叫 UE处于忙 状态信息的第二消息, 通知补充业务应用服务器 AS触发呼叫前转业务。
实际应用时, 第一接收模块 810可由呼叫前转业务的通知装置中的接 收机实现, 第一发送模块 820可由呼叫前转业务的通知装置中的发射机实 现。
对应地, 本发明实施例还提供了一种呼叫前转业务的触发装置, 该装 置可以用于实现上述触发方法。 图 9是根据本发明实施例的装置结构示意 图, 如图 9所示, 包括: 第一接收模块 910和第一触发模块 920; 其中, 第一接收模块 910, 配置为接收 MSC发送的携带有被叫 UE处于忙状 态信息的第一消息;
第一触发模块 920, 配置为向补充业务 AS发送指示所述被叫 UE处于 忙状态的第二消息, 通知补充业务 AS触发呼叫前转业务。
实际应用时, 第一接收模块 910可由呼叫前转业务的触发装置中的接 收机实现, 第一触发模块 920可由呼叫前转业务的触发装置中的发射机实 现。
二、 呼叫偏转业务
本发明实施例还提供了一种呼叫偏转业务的通知方法, 如图 10所示, 包括如下的步骤:
步骤 S1002: MSC接收被叫 UE发送的携带有呼叫偏转号码的第三消 这里, 所述 MSC是指 MSC Server。
步骤 S1004: 向 SCC AS 发送携带有所述呼叫偏转号码的第四消息, 通知补充业务 AS触发呼叫偏转业务。
通过本发明实施例, MSC接收被叫 UE发送的携带有呼叫偏转号码的 第三消息,并将被叫 UE发送的携带有呼叫偏转号码的信息携带在第四消息 中发送至 SCC AS,通知补充业务 AS触发呼叫偏转业务,使得补充业务 AS 根据呼叫偏转号码信息来触发呼叫偏转业务。
作为本发明实施例的另一个方面, 对应地还提供了一种呼叫偏转业务 的触发方法, 如图 11所示, 包括如下的步骤:
步骤 S1102: SCC AS接收 MSC发送的携带有呼叫偏转号码的第三消
步骤 S1104: 向补充业务 AS发送携带有呼叫偏转号码的第四消息, 通 知补充业务 AS触发呼叫偏转业务。
通过本发明实施例, SCC AS接收 MSC发送的携带有呼叫偏转号码的 第三消息,将被叫 UE携带呼叫偏转号码携带在第四消息中发送至补充业务 AS,通知补充业务 AS触发呼叫偏转业务,使得补充业务 AS根据呼叫偏转 号码信息来触发呼叫偏转业务。
实施例三
图 12是 SCC AS和补充业务 AS分开设立时,发生 SRVCC切换后触发 IMS呼叫偏转业务的流程。 具体步骤如下 (步骤 S1202至步骤 S1204 )。
S1201-S1209和图 3中的步骤 301-309一致;
S1210: UE A触发呼叫偏转业务, 发送 DISCONNECT 消息到 MSC Server, 其中携带呼叫偏转号码;
S1211 : MSC Server发送 BYE和 /或 Cancel消息到 SCC AS, 其中携带 描述呼叫偏转业务请求和呼叫偏转号码的 XML;
这里, BYE和 Cancel消息中还携带呼叫偏转号码。
S1212: SCC AS收到后, 转换成 302消息, 携带呼叫偏转号码, 发送 到补充业务 AS;
这里, 所述 302消息为 302 临时性移动 (MOVED TEMPORARILY ) 消息。
按照 IMS网络组网要求, SCC AS和补充业务 AS之间的消息, 经过 S-CSCF转发。
S1213:补充业务 AS收到后,进行呼叫偏转业务,发送 181 call is being forwarded到 UE B , 通知 UE B当前呼叫发生偏转。
S1214: 同时, 补充业务 AS发送 INVITE消息到 UE C。
实施例四
图 13是 SCC AS和补充业务 AS合设时,发生 SRVCC切换后触发 IMS 呼叫偏转业务的流程, 具体步骤如下:
S1301-S1309和图 3中的步骤 301-309一致;
S1310: UE A触发呼叫偏转业务, 发送 DISCONNECT消息到 MSC
Server, 其中携带呼叫偏转号码;
S1311: MSC Server发送 BYE和 /或 Cancel消息到 SCC AS, 其中携带 描述呼叫偏转业务请求和呼叫偏转号码的 XML;
这里, BYE和 Cancel消息中还携带呼叫偏转号码。
S1312: SCC AS收到后, 补充业务 AS触发呼叫偏转业务逻辑, 发送
181 call is being forwarded到 UE B , 通知 UE B当前呼叫发生偏转;
S1314: 同时, SCC AS发送 INVITE消息到 UE C。
通过本发明上述实施例, 采用在 SRVCC 切换的 MSC Server发送 BYE/Cancel消息中, 携带文本格式描述, 收到消息的 SCC AS转换成 CD 业务所使用 302消息,从而在业务 AS上能够触发上述业务的业务逻辑,解 决了现有技术在 SRVCC切换之后的 UE无法实现 CD业务的问题。
需要说明的是, 在附图的流程图示出的步骤可以在诸如一组计算机可 执行指令的计算机系统中执行, 并且, 虽然在流程图中示出了逻辑顺序, 但是在某些情况下, 可以以不同于此处的顺序执行所示出或描述的步骤。
本发明实施例还提供了一种呼叫偏转业务的通知装置, 该装置位于
MSC, 该装置可以用于实现上述通知方法。 图 14是根据本发明实施例的装 置结构示意图, 如图 14所示, 包括: 第二接收模块 1410和第二发送模块 1420; 其中,
第二接收模块 1410, 配置为接收被叫 UE发送携带有呼叫偏转号码的 第三消息;
第二发送模块 1420, 配置为向 SCC AS 发送携带有所述呼叫偏转号码 的第四消息, 通知补充业务 AS触发呼叫偏转业务。
实际应用时, 第二接收模块 1410可由呼叫偏转业务的通知装置中的接 收机实现, 第二发送模块 1420可由呼叫偏转业务的通知装置中的发射机实 现。
对应地, 本发明实施例还提供了一种呼叫偏转业务的触发装置, 该装 置可以用于实现上述触发方法。 图 15是根据本发明实施例的装置结构示意 图, 如图 15所示, 该装置包括: 第二接收模块 1510和第二触发模块 1520; 其中,
第二接收模块 1510,配置为接收 MSC发送携带有呼叫偏转号码的第三 消息;
第二触发模块 1520, 配置为向补充业务 AS发送携带有呼叫偏转号码 的第四消息, 通知补充业务 AS触发呼叫偏转业务。
实际应用时, 第二接收模块 1510可由呼叫偏转业务的触发装置中的接 收机实现, 第二触发模块 1520可由呼叫偏转业务的触发装置中的发射机实 现。
需要说明的是, 装置实施例中描述的呼叫前转 /偏转业务的通知 /触发装 置对应于上述的方法实施例, 其具体的实现过程在方法实施例中已经进行 过详细说明, 在此不再赘述。
本发明实施例在对已有系统改动及影响最小的情况下对 SRVCC切换 后的遇忙呼叫前转和呼叫偏转流程做了优化, 通过在 BYE/Canel消息中携 带用户的业务信息,在 AS上触发用户的遇忙转接和呼叫偏转业务逻辑,从 而满足用户的签约要求。
综上所述, 根据本发明的上述实施例, 解决了现有技术在 SRVCC切换 之后的 UE无法实现呼叫前转 CFB和呼叫偏转 CD业务问题。
本领域内的技术人员应明白, 本发明的实施例可提供为方法、 系统、 或计算机程序产品。 因此, 本发明可采用硬件实施例、 软件实施例、 或结 合软件和硬件方面的实施例的形式。 而且, 本发明可采用在一个或多个其 中包含有计算机可用程序代码的计算机可用存储介质 (包括但不限于磁盘 存储器和光学存储器等)上实施的计算机程序产品的形式。
本发明是参照根据本发明实施例的方法、 设备(系统)、 和计算机程序 产品的流程图和 /或方框图来描述的。 应理解可由计算机程序指令实现流程 图和 /或方框图中的每一流程和 /或方框、以及流程图和 /或方框图中的流程和 /或方框的结合。 可提供这些计算机程序指令到通用计算机、 专用计算机、 嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器, 使得 通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现 在流程图一个流程或多个流程和 /或方框图一个方框或多个方框中指定的功 能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理 设备以特定方式工作的计算机可读存储器中, 使得存储在该计算机可读存 储器中的指令产生包括指令装置的制造品, 该指令装置实现在流程图一个 流程或多个流程和 /或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备 上, 使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机 实现的处理, 从而在计算机或其他可编程设备上执行的指令提供用于实现 在流程图一个流程或多个流程和 /或方框图一个方框或多个方框中指定的功 能的步骤。
以上所述仅为本发明的优选实施例而已, 并不用于限制本发明, 对于 本领域的技术人员来说, 本发明可以有各种更改和变化。 凡在本发明的精 神和原则之内, 所作的任何修改、 等同替换、 改进等, 均应包含在本发明 的保护范围之内。
Claims
1、 一种呼叫前转 /偏转业务的通知方法, 包括:
需要进行呼叫前转业务时, 移动交换中心 MSC接收被叫用户设备 UE 发送的携带有所述被叫 UE处于忙状态信息的第一消息;向业务集中及连续 应用服务器 SCC AS 发送携带有所述被叫 UE处于忙状态信息的第二消息, 通知补充业务应用服务器 AS触发呼叫前转业务; 或者,
需要进行呼叫偏转业务时, MSC接收被叫 UE发送的携带有呼叫偏转 号码的第三消息; 向 SCC AS发送携带有所述呼叫偏转号码的第四消息, 通知补充业务 AS触发呼叫偏转业务。
2、 根据权利要求 1所述的方法, 其中, 所述 MSC接收被叫 UE发送 的携带有所述被叫 UE处于忙状态信息的第一消息包括:
所述 MSC接收所述被叫 UE发送的 DISCONNECT消息; 其中, 所述 DISCONNECT消息中指示的原因为所述被叫 UE处于忙状态。
3、 根据权利要求 1所述的方法, 其中, 所述 MSC接收被叫 UE发送 的携带有呼叫偏转号码的第三消息包括:
所述 MSC接收所述被叫 UE发送的 DISCONNECT消息; 其中, 所述 DISCONNECT消息中携带呼叫偏转号码。
4、 根据权利要求 1或 2所述的方法, 其中, 所述向 SCC AS 发送携带 有所述被叫 UE处于忙状态信息的第二消息包括:
向所述 SCC AS发送 BYE消息和 /或 CANECL消息; 其中, 所述 BYE 消息和所述 CANCEL消息中携带所述被叫 UE处于忙状态信息。
5、 根据权利要求 1或 3所述的方法, 其中, 所述向 SCC AS 发送携带 有所述呼叫偏转号码的第四消息包括:
向所述 SCC AS发送 BYE消息和 /或 CANECL消息; 其中,
所述 BYE消息和所述 CANCEL消息中携带所述呼叫偏转号码和 /或文
本信息, 所述文本信息用于描述呼叫偏转业务请求和呼叫偏转号码。
6、才艮据权利要求 4所述的方法,其中,所述 BYE消息和所述 CANCEL 消息中携带所述被叫 UE处于忙状态信息包括以下至少之一:
所述 BYE消息和所述 CANCEL消息中携带原因 REASON头域, 所述 REASON头域的类型为指示所述被叫 UE处于忙状态的 SIP状态码;
所述 BYE消息和所述 CANCEL消息中携带描述所述被叫 UE处于忙状 态的文本信息。
7、 一种呼叫前转 /偏转业务的触发方法, 包括:
需要进行呼叫前转业务时, SCC AS接收 MSC发送的携带有被叫 UE 处于忙状态信息的第一消息; 向补充业务 AS发送指示所述被叫 UE处于忙 状态的第二消息, 通知补充业务 AS触发呼叫前转业务; 或者,
需要进行呼叫偏转业务时, SCC AS接收 MSC发送的携带有呼叫偏转 号码的第三消息; 向补充业务 AS发送携带有呼叫偏转号码的第四消息,通 知补充业务 AS触发呼叫偏转业务。
8、 根据权利要求 7所述的方法, 其中, 所述 SCC AS接收 MSC发送 的携带有被叫 UE处于忙状态信息的第一消息包括:
所述 SCC AS接收 BYE消息和 /或 CANECL消息; 其中,
所述 BYE消息和所述 CANCEL消息中携带所述被叫 UE处于忙状态信
9、 根据权利要求 7所述的方法, 其中, 所述 SCC AS接收 MSC发送 的携带有呼叫偏转号码的第三消息包括:
所述 SCC AS接收 BYE消息和 /或 CANECL消息; 其中,
所述 BYE消息和所述 CANCEL消息中携带呼叫偏转号码和 /或文本信 息, 所述文本信息用于描述呼叫偏转业务请求和呼叫偏转号码。
10、根据权利要求 7或 8所述的方法, 其中, 向补充业务 AS发送指示 所述被叫 UE处于忙状态的第二消息为 486 Busy Here消息。
11、 根据权利要求 7或 9所述的方法, 其中, 向补充业务 AS发送携带 有呼叫偏转号码的第四消息为 302 MOVED TEMPORARILY消息。
12、才艮据权利要求 8所述的方法,其中,所述 BYE消息和所述 CANCEL 消息中携带所述被叫 UE处于忙状态信息包括以下至少之一:
所述 BYE消息和所述 CANCEL消息中携带原因 REASON头域, 所述 REASON头域的类型为指示所述被叫 UE处于忙状态的 SIP状态码;
所述 BYE消息和所述 CANCEL消息中携带描述所述被叫 UE处于忙状 态的文本信息。
13、 一种呼叫前转 /偏转业务的通知装置, 包括: 第一接收模块和第一 发送模块; 其中, 第一接收模块, 配置为需要进行呼叫前转业务时, 接收 被叫 UE发送的携带有所述被叫 UE处于忙状态信息的第一消息;第一发送 模块, 向 SCC AS 发送携带有所述被叫 UE处于忙状态信息的第二消息, 通知补充业务 AS触发呼叫前转业务; 或者,
所述装置包括: 第二接收模块和第二发送模块; 其中, 第二接收模块, 配置为需要进行呼叫偏转业务时 ,接收被叫 UE发送携带有呼叫偏转号码的 第三消息; 第二发模块, 配置为向 SCC AS 发送携带有所述呼叫偏转号码 的第四消息, 通知补充业务 AS触发呼叫偏转业务。
14、 根据权利要求 13所述的装置, 其中, 所述第一接收模块接收被叫 UE发送的携带有所述被叫 UE处于忙状态信息的第一消息包括:
接收所述被叫 UE 发送的 DISCONNECT 消息; 其中, 所述 DISCONNECT消息中指示的原因为所述被叫 UE处于忙状态。
15、 根据权利要求 13所述的装置, 其中, 所述第二接收模块接收被叫 UE发送的携带有呼叫偏转号码的第三消息包括:
接收所述被叫 UE 发送的 DISCONNECT 消息; 其中, 所述 DISCONNECT消息中携带呼叫偏转号码。
16、 根据权利要求 13或 14所述的装置, 其中, 所述第一发送模块向 SCC AS发送携带有所述被叫 UE处于忙状态信息的第二消息包括:
向 SCC AS发送 BYE消息和 /或 CANECL消息; 其中, 所述 BYE消息 和所述 CANCEL消息中携带所述被叫 UE处于忙状态信息。
17、 根据权利要求 13或 15所述的装置, 其中, 所述第二发送模块向 SCC AS发送携带有所述呼叫偏转号码的第四消息包括:
向 SCC AS发送 BYE消息和 /或 CANECL消息; 其中, 所述 BYE消息 和所述 CANCEL消息中携带所述呼叫偏转号码和 /或文本信息,所述文本信 息用于描述呼叫偏转业务请求和呼叫偏转号码。
18、根据权利要求 16所述的装置,其中,所述 BYE消息和所述 CANCEL 消息中携带所述被叫 UE处于忙状态信息包括以下至少之一:
所述 BYE消息和所述 CANCEL消息中携带原因 REASON头域, 所述 REASON头域的类型为指示所述被叫 UE处于忙状态的 SIP状态码;
所述 BYE消息和所述 CANCEL消息中携带描述所述被叫 UE处于忙状 态的文本信息。
19、 一种呼叫前转 /偏转业务的触发装置, 包括: 第一接收模块和第一 触发模块; 其中, 第一接收模块, 配置为需要进行呼叫前转业务时, 接收 MSC发送的携带有被叫 UE处于忙状态信息的第一消息; 第一触发模块, 配置为向补充业务 AS发送指示所述被叫 UE处于忙状态的第二消息,通知 补充业务 AS触发呼叫前转业务; 或者,
所述装置包括: 第二接收模块和第二触发模块; 其中, 第二接收模块, 配置为需要进行呼叫偏转业务时,接收 MSC发送携带有呼叫偏转号码的第
三消息; 第二触发模块, 配置为向补充业务 AS发送携带有呼叫偏转号码的 第四消息, 通知补充业务 AS触发呼叫偏转业务。
20、根据权利要求 19所述的装置, 其中, 所述第一接收模块接收 MSC 发送的携带有被叫 UE处于忙状态信息的第一消息包括:
接收 BYE 消息和 /或 CANECL 消息; 其中, 所述 BYE 消息和所述 CANCEL消息中携带所述被叫 UE处于忙状态信息。
21、根据权利要求 19所述的装置, 其中, 所述第二接收模块接收 MSC 发送的携带有呼叫偏转号码的第三消息包括:
接收 BYE 消息和 /或 CANECL 消息; 其中, 所述 BYE 消息和所述 CANCEL消息中携带呼叫偏转号码和 /或文本信息, 所述文本信息用于描述 呼叫偏转业务请求和呼叫偏转号码。
22、 根据权利要求 19或 20所述的装置, 其中, 所述第一触发模块向 补充业务 AS发送指示所述被叫 UE处于忙状态的第二消息为 486 Busy Here 消息。
23、 根据权利要求 19或 21所述的装置, 其中, 所述第二触发模块向 补充业务 AS 发送携带有呼叫偏转号码的第四消息为 302 MOVED TEMPORARILY消息。
24、根据权利要求 20所述的装置,其中,所述 BYE消息和所述 CANCEL 消息中携带所述被叫 UE处于忙状态信息包括以下至少之一:
所述 BYE消息和所述 CANCEL消息中携带原因 REASON头域, 所述 REASON头域的类型为指示所述被叫 UE处于忙状态的 SIP状态码;
所述 BYE消息和所述 CANCEL消息中携带描述所述被叫 UE处于忙状 态的文本信息。
25、 一种计算机存储介质, 所述计算机存储介质包括一组指令, 当执 行所述指令时, 引起至少一个处理器执行如权利要求 1至 6任一项所述的
呼叫前转 /偏转业务的通知方法或如权利要求 7至 12任一项所述的呼叫前转 /偏转业务的触发方法。
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP14797566.8A EP3073799A4 (en) | 2013-11-18 | 2014-05-26 | METHOD AND DEVICE FOR NOTIFICATION / TRIGGERING / RECONCILIATION SERVICE |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201310578537.1 | 2013-11-18 | ||
CN201310578537.1A CN104661272A (zh) | 2013-11-18 | 2013-11-18 | 呼叫前转/偏转业务的通知/触发方法、装置 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2014183703A1 true WO2014183703A1 (zh) | 2014-11-20 |
Family
ID=51897762
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2014/078460 WO2014183703A1 (zh) | 2013-11-18 | 2014-05-26 | 呼叫前转/偏转业务的通知/触发方法、装置 |
Country Status (3)
Country | Link |
---|---|
EP (1) | EP3073799A4 (zh) |
CN (1) | CN104661272A (zh) |
WO (1) | WO2014183703A1 (zh) |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN110620849B (zh) * | 2019-09-16 | 2020-08-25 | 南京南瑞信息通信科技有限公司 | 一种ims电话终端呼叫记录集中分拣方法及系统 |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101047901A (zh) * | 2007-05-08 | 2007-10-03 | 华为技术有限公司 | 漏话提醒方法、系统和移动业务设备 |
WO2010015203A1 (en) * | 2008-08-08 | 2010-02-11 | Huawei Technologies Co., Ltd. | System and method for enabiling sr-vcc with shared impu |
CN101848434A (zh) * | 2009-03-24 | 2010-09-29 | 华为技术有限公司 | 设备、业务配置管理方法及系统 |
Family Cites Families (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101141794B (zh) * | 2006-09-08 | 2011-06-15 | 华为技术有限公司 | 用户设备、语音呼叫连续性应用服务器及网络切换方法 |
CN101420669B (zh) * | 2007-10-25 | 2010-08-25 | 华为技术有限公司 | 一种呼叫转移的方法、系统和设备 |
CN101626549B (zh) * | 2008-07-07 | 2013-10-09 | 华为技术有限公司 | 多域环境中提供遇忙呼叫完成业务的方法和实体 |
-
2013
- 2013-11-18 CN CN201310578537.1A patent/CN104661272A/zh not_active Withdrawn
-
2014
- 2014-05-26 WO PCT/CN2014/078460 patent/WO2014183703A1/zh active Application Filing
- 2014-05-26 EP EP14797566.8A patent/EP3073799A4/en not_active Withdrawn
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101047901A (zh) * | 2007-05-08 | 2007-10-03 | 华为技术有限公司 | 漏话提醒方法、系统和移动业务设备 |
WO2010015203A1 (en) * | 2008-08-08 | 2010-02-11 | Huawei Technologies Co., Ltd. | System and method for enabiling sr-vcc with shared impu |
CN101848434A (zh) * | 2009-03-24 | 2010-09-29 | 华为技术有限公司 | 设备、业务配置管理方法及系统 |
Non-Patent Citations (1)
Title |
---|
See also references of EP3073799A4 * |
Also Published As
Publication number | Publication date |
---|---|
CN104661272A (zh) | 2015-05-27 |
EP3073799A4 (en) | 2016-11-16 |
EP3073799A1 (en) | 2016-09-28 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP4709217B2 (ja) | ハイブリッド電気通信ネットワークにおけるセッション制御を行う方法及び装置 | |
EP2945406B1 (en) | System and method for sr-vcc of ims emergency sessions | |
JP5174178B2 (ja) | 着信転送のための方法、システム、およびデバイス | |
JP4654834B2 (ja) | 移動通信システム、交換局サーバ、移動端末装置及びそれらに用いるハンドオーバ方法 | |
WO2008034385A1 (fr) | Dispositif utilisateur, serveur d'application de continuité d'appel et procédé de commutation de réseau | |
US20090201922A1 (en) | Method for changing session media, method for establishing a call, and equipment thereof | |
EP2083576A1 (en) | Communication terminal apparatus, communication system and seamless handover method | |
JP6109928B2 (ja) | Drvcc携帯端末のアクセス転送 | |
WO2009012665A1 (fr) | Procédé pour assurer une continuité d'appel multimédia, équipement et système associés | |
CN101448232B (zh) | 紧急呼叫实现方法及系统、用户设备 | |
JP5095759B2 (ja) | 呼制御方法 | |
EP2421218B1 (en) | Session transfer method, apparatus and system thereof | |
CN107172597B (zh) | 宽带集群系统中终端漫游时的组呼切换方法和装置 | |
CN102761917A (zh) | 一种被叫侧发生会话切换的处理方法和as | |
CN102761915B (zh) | 一种主叫侧发生会话切换的处理方法和as | |
WO2009149635A1 (zh) | 一种实现显式呼叫转移的方法、设备及移动通信系统 | |
WO2011057568A1 (zh) | 一种会话切换的实现方法和系统 | |
WO2011038613A1 (zh) | 一种带有彩铃的振铃状态会话的切换系统及方法 | |
CN102238158B (zh) | 反向单待业务连续性的实现方法及系统 | |
WO2014183703A1 (zh) | 呼叫前转/偏转业务的通知/触发方法、装置 | |
JP2011505772A (ja) | 呼の保持を実現する方法および装置 | |
WO2012129979A1 (zh) | 振铃态域切换的方法、系统及装置 | |
CN101119370A (zh) | 应用于ims终端的呼叫管理系统、方法及ims终端 | |
WO2011107012A1 (zh) | 一种业务控制方法和装置 | |
WO2011023054A1 (zh) | 一种ip多媒体子系统中多会话能力同步方法及系统 |
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: 14797566 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
REEP | Request for entry into the european phase |
Ref document number: 2014797566 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2014797566 Country of ref document: EP |